Livox Mid-360 vs M360: Which LiDAR Is Better for Handheld SLAM Scanning?

Building a handheld SLAM scanner means making a dozen hardware decisions, but one of them dominates everything else: which LiDAR sensor sits on top of your rig. Two sensors keep coming up in every forum thread, every robotics Discord, every warehouse-mapping RFP — the Livox Mid-360 and the M360. They share the same basic DNA (905nm wavelength, 200kHz point rate, 360° horizontal FOV, IP67, non-repetitive scanning), but the differences between them matter more than the similarities once you're walking through a building with a LiDAR strapped to a pole.

This comparison is written from the perspective of someone who has built and tested both in actual scanning scenarios — not a lab bench, not a datasheet exercise. We'll go spec-by-spec, then run through four real-world scenarios and look at how each sensor behaves with common SLAM algorithms like FAST-LIO2 and Point-LIO.

Full Specification Comparison

Here's the head-to-head. Everything pulled from the official M360 product manual (Ver 1.4, 2026-02-27) and the Livox Mid-360 specs page on livoxtech.com.

Both sensors use the ICM40609 IMU, which is well-supported by FAST-LIO2 and Point-LIO out of the box. If you've already got a FAST-LIO2 config for one, swapping to the other mostly requires adjusting the extrinsic calibration and point cloud topic — not a rewrite.

Echo Mode: The Biggest Differentiator You're Not Thinking About

Most people comparing these two sensors jump straight to FOV and range numbers. That's a mistake. The echo mode difference is probably the single most impactful factor for handheld scanning quality in mixed indoor environments.

The M360-D variant offers dual echo. This means the sensor fires a single laser pulse and can register returns from both the front surface and whatever's behind it. In practice, you get point returns off a glass door and the wall behind it in one shot. You get returns through light rain, light fog, and dust clouds. You get better data off semi-transparent materials like polyethylene sheeting, acrylic display cases, and polished floors at oblique angles.

The Mid-360 is first-return only. If the laser hits a glass window, you get one return — and it might come from the glass surface (which is often a poor return at 905nm) or from whatever's behind it. The result is inconsistent point density around glass surfaces, which shows up as holes or noisy patches in your point cloud.

If your scanning route includes office buildings with glass conference rooms, warehouse loading docks with roll-up doors, retail spaces with display cases, or any exterior work during light rain, dual echo makes a real, visible difference in your final map quality. It's not a marginal improvement — it's the difference between a clean point cloud and one that needs manual cleanup in CloudCompare.

That said, if you're scanning concrete parking garages, brick buildings, or any environment without transparent or semi-transparent surfaces, dual echo won't help you at all. You're paying for capability you don't need.

Field of View: 70° vs 59° Vertical

Eleven degrees doesn't sound like much until you're walking through a corridor with a handheld rig and looking at what actually gets captured.

The M360's 70° vertical FOV (-10° to +60°) pulls in more ceiling structure and more floor detail per frame than the Mid-360's 59° (-7° to +52°). That lower -10° limit means the M360 sees more of the floor immediately around you, which helps SLAM algorithms maintain good ground plane estimation — particularly on flat concrete floors where floor returns act as a stabilization reference. The +60° upper limit captures more ceiling geometry, which matters in rooms with overhead ductwork, suspended lighting, or mezzanine levels.

With the Mid-360, you might miss the upper portion of tall ceiling features, and the floor returns drop off sooner when walking on uneven terrain. For most corridor scanning, both sensors work fine. For detailed indoor mapping where ceiling and floor features are part of the deliverable, the M360 gives you more to work with.

Blind Zone: 5cm vs 10cm

The M360's 5cm blind zone is half the Mid-360's 10cm. In a handheld context, this matters when you're scanning close to walls, furniture, or equipment racks. Walk down a narrow warehouse aisle with the Mid-360, and there's a 10cm dead zone right around the sensor where nothing gets captured. The M360 pushes that dead zone to 5cm — still present, but narrow enough that you can position the scanner closer to a wall and still capture the wall-to-floor joint.

This shows up most in two places: tight corridors where you want to map both walls in a single pass (the narrower the blind zone, the less gap between your left and right wall coverage), and detailed room scanning where furniture and fixtures are close together.

Detection Range: 40m vs 25m at 10% Reflectivity

This is where the Mid-360 wins clearly. At 10% reflectivity (which covers dark-painted surfaces, weathered concrete, vegetation, and dark asphalt), the Mid-360 reaches 40m compared to the M360's 25m. That 15m difference matters in outdoor scanning — building facades, parking lots, site surveys — where you regularly scan surfaces at 25-40m distance.

For outdoor building facade surveys, the Mid-360 gives you more complete coverage from a single scan position. You capture the full face of a multi-story building without having to walk as close. In large warehouse environments with long sightlines, the extra range means fewer scan positions to cover the same area.

The M360's 50m range at 90% reflectivity is competitive for highly reflective surfaces, but in practice, most real-world scanning targets sit in the 10-30% reflectivity range. Concrete, brick, wood, and dark metals fall squarely in this band.

Weight and Form Factor: 143g Difference

The Mid-360 weighs 265g. The M360 weighs 408g. That's a 143g difference — roughly the weight of a small smartphone.

For handheld scanner rigs, this gap shows up in two ways. First, the total system weight. A typical handheld SLAM rig includes the LiDAR, a compute unit (Jetson Orin Nano, Intel NUC, or similar), batteries, a screen, a handle or pole mount, and cabling. If you're trying to keep the whole thing under 2-3kg for comfortable operation (most commercial handheld scanners hit 1.2-1.8kg total), every 100g matters.

Second, balance. The Mid-360 is smaller (65×65×60mm vs 78×78×81mm), which means the scanning head sits lower on the rig. That changes the center of gravity and affects how the rig feels when you're walking and scanning for 20-30 minutes at a time. The 3DMakerpro Eagle scanner, which uses a Mid-360, keeps the entire unit at 1.5kg including battery — the light sensor is a real part of how they hit that number.

If you're building a lightweight handheld for field work where you're walking all day, the Mid-360's lower weight is a genuine advantage. If you're building a heavier rig with additional sensors (cameras, GNSS, secondary LiDAR), the weight difference becomes less noticeable.

Power Consumption: <4.5W vs 6.5W

The M360 draws less than 4.5W at room temperature. The Mid-360 averages 6.5W, with a catch: when operating in cold environments (-20℃ to 0℃), it enters self-heating mode that can spike to 14W. That's a three-fold increase in power draw.

For a handheld scanner running on batteries, the math is straightforward. Assume a typical handheld rig uses 15-20W total (LiDAR + compute + screen + other sensors). At 4.5W for the LiDAR, you're allocating roughly 23-30% of your power budget to the sensor. At 6.5W, it's 33-43%. Over a 2-hour scan session, that extra 2W translates to roughly 4Wh — which, on a 100Wh battery pack, costs you about 4% of your total runtime. Not enormous on its own, but add in the self-heating spike in cold weather, and the gap widens.

There's also a practical consideration: power supply design. The M360's 12-32V input range is wider than the Mid-360's 9-27V, which means it plays nicely with 24V industrial battery systems and vehicle power without a dedicated converter. The Mid-360's 9V lower limit is better suited for lightweight 3S LiPo packs (11.1V nominal), which is convenient for DIY handheld builds.

Temperature Range: Different Kinds of Tough

The M360 operates from -10℃ to +60℃. The Mid-360 goes from -20℃ to +55℃. Each sensor trades off on a different end.

The Mid-360's -20℃ lower bound is better for cold-weather outdoor scanning — early morning site surveys in winter, cold-storage facility mapping, and work in northern climates. The trade-off is the self-heating power spike mentioned above and the +55℃ upper limit, which is lower than the M360's +60℃. If you're scanning inside a hot warehouse or in direct summer sun where the sensor housing could approach 60℃, the Mid-360 might trigger its thermal protection, while the M360 keeps operating.

The M360's +60℃ upper limit and lack of self-heating mode make it more predictable in hot environments, at the cost of being less useful below -10℃.

Real-World Scanning Scenarios

Specs on paper are one thing. How these sensors actually behave when you're walking through a building is another. Here are four common handheld scanning scenarios and which sensor handles each better.

Scenario 1: Indoor Warehouse Mapping

Typical conditions: 2-15m range, metal shelving, cardboard boxes, concrete floors, glass dock doors, walking pace (~1 m/s), 30-90 minute sessions.

This is where the M360-D (dual echo model) earns its keep. Warehouses are full of glass — dock doors, office windows, display panels, and occasionally glass safety barriers. The dual echo returns from the M360-D give you clean point data on both sides of those surfaces. Combined with the 5cm blind zone, you get better coverage in the narrow gaps between shelving rows where you might only have 50-80cm clearance on either side.

The Mid-360's longer range at 10% reflectivity doesn't help much here — warehouse objects are close, and cardboard boxes at 5m are easy targets for either sensor. But the Mid-360's lighter weight is nice if you're doing 2-3 hour sessions and trying to keep arm fatigue down.

Edge: M360-D for data quality. Mid-360 for operator comfort on long sessions.

Scenario 2: Outdoor Building Facade Survey

Typical conditions: 5-40m range, brick, concrete, glass windows, metal panels, slow walking pace, variable weather, GPS-aided SLAM.

The Mid-360 takes the lead on range. Building facades regularly present dark brick, weathered stucco, or dark metal cladding — all low-reflectivity materials. The Mid-360's 40m reach at 10% reflectivity means you can capture the full height of a 3-4 story building from across the street without having to reposition. With the M360's 25m at 10% reflectivity, you'll need to walk closer, which means more scan positions and more post-processing to merge overlapping coverage.

Glass windows complicate this. The M360-D's dual echo would help with windows, but the range limitation remains. In practice, many teams run the Mid-360 for facade work and accept some noise around glass surfaces, then clean up in post.

If rain is in the forecast, the M360-D's ability to maintain returns in wet conditions could matter — depending on how wet we're talking about. Light drizzle, it handles fine. Heavy rain, neither sensor is going to produce great data.

Edge: Mid-360 for range and weight. M360-D if glass windows are dominant and weather is uncertain.

Scenario 3: Confined Space and Narrow Corridor Scanning

Typical conditions: 0.5-5m range, tight spaces, narrow corridors, mechanical rooms, ship interiors, tunnel sections.

The M360 wins here on two fronts. The 5cm blind zone lets you position the sensor closer to walls without losing coverage in the gap. When you're scanning a 1.2m-wide ship corridor, having a 10cm blind zone on each side means you're losing a significant percentage of your usable cross-section. The wider 70° vertical FOV also captures more ceiling and floor per pass, which matters in mechanical rooms where overhead piping and under-floor cable trays are both part of the survey deliverable.

The Mid-360's 10cm blind zone becomes a real problem when walls are close. You'd need to make multiple passes or reposition more frequently to fill in the gaps.

Edge: M360, clearly. Better blind zone, wider vertical FOV — both matter more in tight spaces.

Scenario 4: Extended Battery-Powered Operations

Typical conditions: 2-3 hours continuous scanning, remote sites without access to mains power, vehicle-based mobile mapping, long-haul corridor surveys.

Power consumption becomes the deciding factor. Over a 3-hour session, the M360's <4.5W draw versus the Mid-360's 6.5W average saves roughly 6Wh. On a compact handheld scanner running a 99Wh battery (the airline carry-on limit for lithium), that 6Wh represents about 6% additional runtime — or a safety margin when you're running close to empty.

In cold environments, the gap widens further. If the Mid-360 enters self-heating mode at 14W, you're burning through battery noticeably faster. The M360, which operates normally down to -10℃ without self-heating, maintains consistent power draw in moderately cold conditions.

The M360's 12-32V input range also helps with power system design. If you're integrating the LiDAR into a vehicle-based mobile mapping system that runs on 24V, the M360 connects directly. The Mid-360's 9-27V range technically covers 24V, but it's close enough to the upper limit to make some power engineers nervous.

Edge: M360 for power efficiency and wide voltage range. Mid-360 for cold-weather operation below -10℃ (at the cost of higher power draw during warm-up).

SLAM Algorithm Compatibility

Both sensors are well-supported by the major open-source SLAM algorithms used in handheld scanning. Here's the current state:

FAST-LIO2: Works with both sensors. The HKU MaRS lab's FAST-LIO2 has mature support for Livox sensors, and the M360's data format is compatible. Both sensors output point clouds that FAST-LIO2 can consume. The ICM40609 IMU in both is the same chip, so IMU integration is straightforward. The LIV-Eye project from HKU MaRS specifically targets the Mid-360 with FAST-LIO2 and demonstrates high-quality handheld mapping.

Point-LIO: Compatible with both. Point-LIO is more computationally efficient than FAST-LIO2 and handles non-repetitive scanning patterns well. If you're running on a lower-power compute unit (like a Jetson Orin Nano), Point-LIO might be the better choice regardless of which sensor you pick.

LIO-Livox: Livox's official SLAM solution. Naturally, it's optimized for the Mid-360. The M360 requires some driver adaptation to work with LIO-Livox, though the community has published workable configs.

One practical note: the M360's dual echo capability generates more data per frame than the Mid-360's single return. In SLAM processing terms, this means slightly higher computational load — not enough to overwhelm a Jetson Orin, but worth knowing if you're running on constrained hardware.

If you're already in the Livox ecosystem (using Livox Viewer, Livox SDK2, Livox ROS drivers), the Mid-360 is plug-and-play. The M360 requires its own driver stack, which SmartBot Parts provides, but it's an extra setup step compared to the Mid-360's extensive community resources.

The Decision Guide

Here's where this all lands based on what you're actually doing:

Choose the M360 (or M360-D) if:

• You scan in environments with glass, transparent materials, or exposure to rain and light fog
• You frequently work in tight corridors, confined spaces, or ship interiors where the 5cm blind zone matters
• You need to capture full ceiling and floor detail (70° vertical FOV)
• You're running extended sessions (2+ hours) on battery power
• You're integrating into a 24V industrial power system
• You need a rated lifespan specification for project planning
• You regularly scan in hot environments above 55℃

Choose the Livox Mid-360 if:

• Weight is a primary concern (lightweight handheld builds, long walking sessions)
• You need maximum range at low reflectivity (outdoor facade surveys, large open spaces)
• You're already invested in the Livox software ecosystem (SDK2, LIO-Livox, Livox ROS drivers)
• You operate in cold environments below -10℃
• You need GPS sync (the Mid-360 supports GPS in addition to PTP)
• You want the lowest-friction setup with the largest open-source community behind you
• You're on a budget and want the widely available retail pricing (~$899-$1,350)

For most handheld scanner builders, the decision comes down to one question: does dual echo matter for your typical scanning environments? If you regularly encounter glass, transparent materials, or wet conditions, the M360-D justifies itself on data quality alone. If you're primarily scanning concrete, brick, and metal surfaces in reasonable weather, the Mid-360's lighter weight and longer range may be the better fit.

Both sensors produce dense, centimeter-accurate point clouds suitable for professional survey deliverables. Neither is a bad choice — they're optimized for different priorities within the same general application space.

© 2026 SmartBotParts. All rights reserved.

M360 specs from product manual Ver 1.4 (2026-02-27). Mid-360 specs from livoxtech.com. Prices vary by region and volume. Always verify with evaluation units before committing to a purchase.