Lens 01 · Vision

Four cameras.
One volume.

Four Time-of-Flight cameras each return their own point cloud. Calibration is what turns four overlapping opinions about the same floor into one volume the planner can trust.

This page shows that calibration, the safety fields built on top of it, and the surfaces that still defeat it.

ToF + dual LiDAR Z-up, floor = XY No floor markers
ToF point cloud calibrationfour cameras, one frame
The perception stack

Three senses,
three different jobs.

It is tempting to describe an AMR as having "360° vision". It does not. It has a safety layer that must not miss, a 3D layer that measures, and a map layer that remembers. They are built by different sensors because they fail differently.

Layer 01 · LiDAR

The safety field

Answers one question: is something in the way right now? Dual 360° scanners build the protective stop and slowdown zones. This layer is what the safety certification is written against, which is why it does not depend on the map being right.

Layer 02 · Time of Flight

The 3D volume

Answers: what shape is in front of me, and how far away is it? Four ToF cameras return dense point clouds across a volume rather than a single plane — low obstacles, overhangs, and the top of a load all become geometry.

Layer 03 · SLAM

The map

Answers: where am I, and how do I get there? Simultaneous localisation and mapping builds a map on day one and then tracks pose inside it. No tape, no reflectors, no floor markers of any kind.

Evidence · calibration

What the four colours are.

The recording at the top of this page is the calibration tool, not a marketing render. Four PLY files are loaded at once — one per ToF camera — and each is drawn in its own colour.

In the session shown, the four frames carry between roughly 11,800 and 19,600 points each. Overlay them without alignment and you get four slightly different opinions about where the floor is. Calibration is the process of aligning them into a single Z-up frame, where the floor is the XY plane and Z points up.

The wireframe box is the reference volume the clouds are aligned and cropped into. Everything the planner receives is inside that box.

The calibration session, as recorded
CameraColour on screenPoints
tofd4_…_1017Cyan19,551
tofd4_…_1018Pink16,177
tofd4_…_8943Lime14,514
tofd4_…_1019Yellow11,807
On the numbers. Point counts are per frame from the recording, not a specification. Density changes with distance, surface angle and what is in the scene — which is exactly why the far corners of a volume get fewer points than the floor in front of the robot.
Evidence · safety fields

The field grows
with the load.

A robot carrying a 1,500 kg pallet that overhangs its chassis is, physically, a bigger robot. The protective field has to be bigger too — otherwise the certification describes a machine that is not the one moving.

Diagram showing a red stop zone and a yellow slow-down zone extending in front of an AMR, with the zones growing when a large load is carried and when speed is higher
Dynamic safety fieldstop zone and slowdown zone scale with speed, load dimension and direction of travel
  • Two zones, not one. A red stop zone and a yellow slowdown zone. The slowdown zone is not decoration — it is what stops the robot braking from full speed every time someone walks past.
  • Speed-dependent. Field length scales with velocity, so a fast move has a long field and a docking approach has a short one.
  • Load-dependent. A load with a large outer dimension widens the field and reduces speed, because the robot's actual swept volume is bigger than its chassis.
  • Direction-dependent. The field follows travel direction rather than sitting symmetrically around the body.
Sensor fit by model

Not every body
carries every sensor.

The platform models and the fork models are equipped differently, because the jobs are different. This is the honest table: what each model actually carries.

Perception fit, platform and fork models
ModelPerception fitPayloadBuilt for
S130LiDAR + ToF60 kgLight tote and bin transport
X13Dual LiDAR 360°600 kgManufacturing line feeding
X22Dual LiDAR + ToF1,000 kgPallet and material transport
X33Dual LiDAR 360°1,500 kgHeavy pallet handling
PX334× LiDAR + ToF1,500 kgHorizontal pallet transport
FX334× LiDAR + photoelectric1,500 kgStacking and retrieval
FX33 Pro4× LiDAR + 2× photoelectric1,500 kgUS edition stacker
CX333× LiDAR + 2× photoelectric1,500 kgCounterbalance operations
The honest part

What it
won't see.

Every sensor here fails on something. These are the conditions that show up in site surveys, what happens when they do, and what we do about them before go-live rather than after.

ConditionWhat happensWhat we do
Glass and mirrorsLiDAR passes through or reflects at the wrong angle; ToF can read a false surfaceMap a keep-out zone, or route the lane away from the glazing
Black mesh and matte black panelsReturns are absorbed, so the surface is sparse or missingPhysical guard or a mapped no-go boundary
Reflective shrink-wrap on loadsMultipath returns put phantom points beside the real palletAcceptance test with the actual load, not a demo box
Forklift tines and cablesToo thin for a reliable return at distanceTraffic rules and crossing design, not sensor tuning
CrowdsEverything works; throughput drops as the robot yields repeatedlySimulate at expected density, not at empty-floor density
Dust, steam, sprayScattered returns thicken the cloud with noiseEnclosure rating and a wash-down plan for the sensors
Direct sunlightInfrared interference degrades ToF rangeToF is an indoor layer. Outdoor lanes are scoped differently
Racking moved overnightThe map no longer matches the floorRemap after layout changes — it is a 20-minute job, not a rebuild

None of this is a reason to avoid the technology. It is a reason to survey the floor before quoting a cycle time. Every row above is something a site visit catches and a brochure does not.

Send us a floor plan.

We will tell you which lanes the sensors handle cleanly, which ones need a keep-out zone, and which ones no AMR should be driving down.