uGo — operator surface, technician page and kiosk¶
uGo is what a person at the customer site sees. It runs on the tablet of the robot, in six languages, and it is the only thing that may be visible after switching on — see Kiosk mode.
Three surfaces, three audiences, one server.
| Surface | For whom | Reachable |
|---|---|---|
| Operator surface | staff at the device | on the tablet, no login |
| Technician page | service | over the network, behind the technician password |
| Second screen | passers-by | outward-facing display of the uServe |
The technician page¶
Twenty-five sections, and the design principle is worth stating because it explains what is deliberately missing: everything that can be undone lives here, everything irreversible lives in the console. Switching off, resetting the occupancy grid and the hard wheel reset are not on this page, and that is not an oversight.
What it covers today: state, maps, map archive, setting the pose, points, zones, recordings, passwords, device, superstructures, time, raw overlays, driving, map recording, second screen, playlist, files, lift and people, idle image, u-IoT, logs, services.
What it does not cover yet: the fleet, chassis parameters, and wireless configuration. Fleet is the notable gap — the whole of Fleet is invisible to the technician today.
The server interface¶
Everything the surfaces do goes through /api/** on the device. Reading is
open on the local network; writing requires a session, and the technician
functions require the technician role — an operator who is signed in is not a
technician.
For routes and payloads see uGo server.
Tours¶
A tour is a list of stops. Per stop: coordinates, a name, an optional heading, a wait time, and whether the device waits for a confirmation. Per tour: endless loop, pause between rounds, and whether to drive to the charging station at the end.
Two settings decide how a tour behaves in a fleet, and both are frequently misjudged: the wait time per stop and the pause between rounds. Neither is a fleet setting, both look like one from the outside.
Faces and the idle image¶
The device shows a face. Which one is a configuration, and delivering a device with the default image is the most visible way to look unfinished. The idle image must not push itself in front of the technician page — that has happened and is a fault, not a feature.