uLog and uServe — the chassis

The chassis drives, localises and refuses. Everything above it — tours, fleet, lifts — arranges; the chassis is what actually stops in front of an obstacle. That separation is the safety argument of the whole platform and is not to be softened.

Two families: uLog (transport, 80 / 150 / 300) and uServe (service, with a second screen). Both speak the same REST interface; what differs is the superstructure and the capability profile.

For routes and payloads see Fahrgestell. The models of the range with payload, dimensions and the documents per model are on Device range.

Maps, and what is in them

A map has three parts: the occupancy grid (an image), the Carto map (the localisation data), and the overlays — the points, zones and lanes drawn by a human. The third part is where two hours of work per site sit, and it is the part that gets lost.

Overlay taxonomy, as measured

Only values confirmed by an overlay that actually carries them. The published vendor list is wrong about at least one value, so a document naming a number is not evidence.

Points (type):

Value	Meaning	Evidence
7	door control, MAC in deviceId — no lookup needed	real recording with a real MAC
8	door control, obsolete	only on hand-drawn maps, deviceId holds free text
9	charging station; deviceIds carries the serial number of the robot	measured, twice
10	lift point	measured; not in the published list
11	way point / station point	measured and published
36	docking point, tied to a station via dockingPointId	measured and published

Regions (regionType):

Value	Meaning	Evidence
2	slow-driving zone	measured; historically misused as a door area
4	lift area — not a door	measured. The published list calls 4 "automatic door", which would put the door-hold boundary on the wrong polygon
5	door area / area to hold open. A polygon, and it does not coincide with a circle around the door point	measured
1, 8, 12	virtual region, LiDAR-deceiving zone, free space	published only, not measured by us
keep-out	unknown	deliberately an open hole, not a guessed value

Never store a vendor number as if it were meaning

Keep an own zone kind and put the vendor number literally beside it. An unknown number becomes "unknown" — never a guess, never a silent loss. Value 4 is exactly why.

Overlay versions, and how work gets destroyed

The chassis counts an overlays_version up on every change to points and zones. That counter is the only reliable sign that somebody has drawn on the device since a backup was taken.

On 26.08.2026 two maps lost their lift-area polygons because an older backup was written back over them. No error message, no prompt — the loss was noticed when somebody went looking for the polygons. Both maps went down a version, which is the fingerprint of a whole-map replacement rather than a patch.

The rule that follows: never write overlays back over a newer overlays_version. If the archive does not know which version it holds, that is a refusal, not a reason to guess. Not knowing and danger are the same thing here — the opposite rule ("write when in doubt") is exactly what cost those polygons.

Chassis parameters

Speed, acceleration and footprint differ between devices of the same model. Three devices meant to drive the same tour with different speed or clearance parameters produce behaviour that looks like a software fault and is not. Compare them before debugging anything above the chassis.