Skip to content

Acceptance — the list before the truck

Worked through at the device, by a person, with the device switched on. Not from memory and not from a build report.

For IT, technicians and integration partners

Technical reference for IT departments, URG technicians and trained partners. It is not written as operating instructions for end users.

Function

Check Expected
Power on, hands off our application appears, no desktop at any moment
Pull the plug during operation, plug back in comes up again, no dialogue, no lost configuration
Every screen edge swiped no system bar, no notifications
Application killed restarts by itself
Drive a tour with two stops reaches both, log clean
Emergency stop pressed device stops, page shows it, release works
Charging run finds the station, docks, charges
Language switch all six surface languages, nothing falls out of the layout
Technician page over the network reachable, password required
Sound and face as configured, not the default image

At the customer site — after mapping, before handover

Added 15.10.2026 after a commissioning at a customer site. Worked through at the customer site, with the customer's map active and somebody next to the robot with the emergency stop in reach.

Check Expected
Every barrier, railing and staircase in the driving area, driven past at walking speed the robot recognises it and keeps its distance. If it does not recognise it reliably — observed with a pedestrian barrier made of tubes with an open space below — do not hand over the robot for that area and report it to support
Undersides of stairs and parts that overhang the driving area the robot does not drive underneath; otherwise as above
Robot switched on, standing on its charging station, no job stays on the station, does not turn and does not drive off. If it turns or drives off without a job: switch it off, do not operate it, report it to support with a video
Call buttons, if ordered tests T1 to T8 passed with a real press, see Call buttons with light — commissioning

The uGo map tool does not create keep-out zones: their identification at the device is not verified (see uGo server). A barrier that the robot does not recognise is therefore not secured by a zone drawn in uGo.

Fault and service: support@unitedrobotics.group.

Fleet, if the site has more than one device

Check Expected
All devices report members = number of devices, on every device
One master the same serial number everywhere
Nobody on "alone" —
Discarded packets zero
Two devices to the same point one waits or gives way; no contact

The acceptance rule is the CEO's and has no tolerance: the fleet test passes only if the robots do not collide with each other. "Almost" does not count.

Data hygiene before packing

Check Expected
Map archive only maps of the receiving customer
Tour history test tours removed
Log no other customer's name in it
Accounts no internal account left on the device
Cloud assignment correct customer node
Reset secret in the password manager, tied to the serial number

Papers

Serial number, certificate expiry, customer node, fleet key set yes/no, software version, date, name of the technician. One page, and it stays with us — the customer gets the handover protocol, not our internal sheet.

Beim Kunden — nach der Kartierung, vor der Übergabe

Ergänzt am 15.10.2026 nach einer Inbetriebnahme beim Kunden. Abgearbeitet beim Kunden, mit aktiver Kundenkarte und einer Person beim Roboter, Not-Halt in Reichweite.

Prüfung Erwartet
Jede Absperrung, jedes Geländer und jede Treppe im Fahrbereich in Schrittgeschwindigkeit abfahren der Roboter erkennt sie und hält Abstand. Erkennt er sie nicht sicher — beobachtet an einer Fußgängerabsperrung aus Rohren mit offenem Raum darunter —, den Roboter für diesen Bereich nicht übergeben und an den Support melden
Unterseiten von Treppen und Teile, die in den Fahrbereich ragen der Roboter fährt nicht darunter; sonst wie oben
Roboter eingeschaltet auf seiner Ladestation, kein Auftrag bleibt auf der Station stehen, dreht sich nicht und fährt nicht los. Dreht er sich oder fährt er ohne Auftrag los: ausschalten, nicht betreiben, mit Video an den Support melden
Ruftaster, falls bestellt Tests T1 bis T8 mit echtem Druck bestanden, siehe Ruftaster mit Leuchte — Inbetriebnahme

Das Kartenwerkzeug von uGo legt keine Sperrzonen an: ihre Kennung am Gerät ist nicht belegt (siehe uGo-Server). Eine Absperrung, die der Roboter nicht erkennt, ist deshalb nicht durch eine in uGo gezeichnete Zone gesichert.

Störung und Service: support@unitedrobotics.group.