A friend of mine works on logistics automation projects, and he's currently designing an autonomous forklift system for a major e-commerce warehouse. They'd been using MID-360 all along and recently switched to M360. We got to talking, and he walked me through the headaches he ran into during the selection process.
Some context first. This warehouse has three things going for it: tightly packed shelving, people walking around constantly, and a few outdoor loading areas. When they were running MID-360, they kept running into the same problems.
Low obstacles right next to the shelves went undetected
The biggest headache was stuff like pallet fragments that fell off shelves, or small tools left on the floor. The MID-360 has a 10cm blind zone, meaning anything within 10cm directly below the sensor is invisible. So when a forklift squeezed through a shelf aisle and there was a 5cm-high obstacle on the ground, it'd just drive straight into it.
After switching to M360, the blind zone dropped to 5cm. Same shelf aisle, same 5cm obstacle — now the forklift could see it. My friend said the change was immediate. They used to send someone to pick up damaged goods once a week. Now it basically never happens.
Rainy days at the outdoor loading docks were sketchy
Several of their loading areas are outdoors. When it rained, the MID-360's point cloud quality took a noticeable hit. Single-return LiDAR struggles in rain — it either flags raindrops as obstacles or loses the real obstacle signals entirely.
They tried M360's dual-return version, which punches through raindrops and sees what's behind them. My friend told me that under identical rain conditions, M360 reliably identified pallet stacks and people in the loading zone, while MID-360 generated massive noise — sometimes it just stopped working altogether.
Power draw was eating into runtime
The forklifts were designed for 8 hours of runtime on a charge. With MID-360, they had to recharge midway through a shift. After switching to M360 (under 4.5W power draw), the same battery now lasts 12 hours. My friend said this saved them the cost of building an extra charging station, plus the downtime of swapping batteries mid-shift.
More flexible mounting options
M360's input voltage range is 12–32V, noticeably wider than MID-360's 9–27V. Some of their forklift power supplies sit right at 24V, and with MID-360 the voltage margin was too tight for comfort. M360 handled it without issues. It's a small detail, but in real deployments it matters.
Three months in, the numbers speak
After three months of operation, my friend shared some hard data:
- Obstacle detection success rate: from 92% to 98%
- Rainy-day downtime: from 2–3 hours per day to under 30 minutes
- Runtime per charge: from 8 hours to 12 hours
- System fault rate: dropped by 40%
The biggest change, he said, was the sense of safety among the warehouse workers. People used to be nervous around the forklifts. Now they barely notice them. The robots just handle it.
What this taught me about LiDAR selection
From this case, I'd say there are four things that actually matter when you're choosing a sensor:
- Blind zone size: In dense warehouses, the difference between 5cm and 10cm is huge. It directly affects safety.
- Environmental resilience: Dual-return vs single-return is night and day in rain and fog.
- Power consumption: It affects charging infrastructure costs and deployment complexity.
- Voltage compatibility: Power supply issues are easy to overlook until you're on-site trying to make things work.
I'm not saying MID-360 is a bad sensor. For clean indoor environments with plenty of space, its lightweight form factor and longer detection range still have real value. But in genuinely complex industrial settings, M360's edge in these details becomes hard to ignore.
If your project involves dense storage, mixed indoor-outdoor zones, and fussy power setups, M360 is probably the safer bet. If it's a straightforward indoor material handling setup, MID-360 gets the job done just fine.
*Based on a real-world project case. Specification data sourced from smartbotparts.com public information.