Case / container completeness
Look down on a package or carrier and compare its 3D profile with the taught model.
Measure depth across an entire scene for completeness, dimensions, level, depalletising and robot guidance. O3D uses PMD time-of-flight technology to calculate a distance value for every pixel, giving the machine real 3D geometry rather than a conventional 2D image alone.

O3D is strongest where a 2D image cannot reliably answer the question because the machine needs the distance or geometry of the scene.
Look down on a package or carrier and compare its 3D profile with the taught model.
Calculate height and geometry for parcels, goods or material-handling decisions.
Measure fill level or limit conditions in suitable bins, silos and hoppers.
Use depth data to identify the top layer and support controlled removal of boxes.
Determine object location / geometry for robot gripping applications.
Use shape, height and volume to classify objects where 2D appearance is insufficient.
O3D illuminates the scene with modulated infrared light and calculates time-of-flight per image point. The sensor therefore produces depth information without relying on triangulation or a moving scan.
These values describe the current O3D3 PMD platform. Exact interfaces, outputs and housing details remain order-number dependent.
Use the depth image for built-in application wizards or advanced user-defined models in ifm Vision Assistant.
The field of view, smallest height difference, surface reflectivity, ambient light, working distance, object motion and required application output determine whether O3D is suitable.
Both use 3D perception, but they solve different system-level problems.
| Requirement | O3D | O3R |
|---|---|---|
| Fixed machine inspection / dimensioning | Strong fit | Usually unnecessary complexity |
| Built-in completeness / level / depalletising workflow | Strong fit | Custom platform route |
| Several synchronised cameras | Separate sensors | Native multi-camera platform |
| AMR / AGV perception | Limited system role | Primary O3R use case |
| Run own ROS / Docker / GPU algorithms | No | Yes, on VPU |