Product Overview
The hard part of 3D avoidance is not the LiDAR — it is the algorithm: how point clouds are parsed, which points count as obstacles, and under what conditions an alarm fires. We built that part as a module that can be delivered on its own, which gives the same capability three different ways to buy.
Algorithm only, integrated into your own controller — the right fit when you have an algorithm or embedded team and want to develop on top of it. Radar plus algorithm, which removes the radar-selection work but still leaves integration to you. Or the full set with the algorithm pre-installed in an edge adapter box: power it on and it outputs alarm signals, with no environment to deploy and no algorithm to configure.
If the site already runs a compatible 3D radar, the adapter alone is enough — no need to replace the whole unit. Customers who want to go live quickly without touching code should take the full set, which is also the most cost-effective way to buy.
Three ways to buy
One 3D avoidance algorithm, delivered in the form that fits your engineering capability
- 3D avoidance algorithm (integrable into your controller)
- Algorithm notes and interface documentation
- Support during integration
- 3D radar
- 3D avoidance algorithm
- Commissioning support
- 3D radar
- 3D avoidance algorithm
- Edge-computing adapter box (algorithm pre-installed)
- Configuration software
Key Features
How It Works
vs. traditional 3D avoidance solutions
The difference in 3D avoidance: who writes the algorithm and where the compute runs
| Item | Traditional | Adapter box |
|---|---|---|
| Algorithm | Built by customer, slow & costly | Built-in, zero coding |
| Compute | Host/IPC — costly & complex | Edge computing on the adapter, on-site |
| Upgrade | Hard, usually replace unit | Adapter only, plug & play |
| Deployment | Long, item-by-item | Short, configure and go |
| Output | Raw point cloud, needs dev | Direct alarm / control signals |
| Purchasing | Bundle only | Algorithm / radar+algorithm / full set |
vs. other avoidance approaches
Adapter + 3D LiDAR imaging vs ultrasonic, IR, vision, 2D radar and mmWave
| Approach | Limitation | Our advantage |
|---|---|---|
| Ultrasonic | No angle resolution, short range, crosstalk, weather-sensitive | True 3D cloud, precise ranging, anti-crosstalk, robust in complex scenes |
| IR / light grid | Switch output only, no range or 3D profile; beams may interfere if not installed carefully | Continuous range + 3D profile, zoned & graded alerts |
| Camera (vision) | Depends on light & compute, degrades in dark/backlight/fog | Active sensing all-weather, edge compute saves power |
| 2D LiDAR | One plane only, misses height/hanging/ledges | Hemispheric 3D coverage, detects high/low obstacles and ledges |
| mmWave | Low angular resolution, weak on non-metal/low-reflectance targets | Dense cloud stably detects small low-reflectance targets |
Specifications
For reference only; the final product datasheet prevails
Scenarios
Installation & Usage Notes
- Mount the adapter close by, clear of obstructions, dust build-up and strong vibration
- Connect radar and adapter with the standard interface; confirm the supply is within DC 9–36 V before powering up
- Calibrate against the site coordinate system on first power-up, then move on to zone configuration
- Draw 3D guard zones in the bundled software, leaving a sensible margin at the boundary
- Tune sensitivity, alarm delay and output logic per working condition
- Save separate profiles for different vehicles or stations and switch between them
- Verify zone boundaries with static targets first
- Then re-test false positives and misses along the real motion path
- Confirm the linkage to audible alarms and E-stop before acceptance
Interested in the 3D Obstacle Avoidance LiDAR?
Call us for selection, quotations and technical support