AScan X1 Troubleshooting: Common SLAM Scanning Issues
Mobile SLAM scanning issues typically fall into six categories: cumulative point cloud drift from loop closure failure, GNSS signal loss affecting absolute georeferencing, poor scan coverage from inconsistent walking speed, data storage or transfer interruptions, camera exposure problems in low-light environments, and multi-scan registration misalignment during post-processing. Most of these issues trace back to scanning technique or environmental conditions rather than hardware faults, and can be corrected in the field or during processing in APEKS-CORE.
- 1. Why SLAM Scanning Issues Differ from GNSS/Total Station Errors
- 2. Problem 1: Cumulative Point Cloud Drift
- 3. Problem 2: GNSS Signal Loss Affecting Georeferencing
- 4. Problem 3: Inconsistent Scan Coverage
- 5. Problem 4: Data Storage or Transfer Interruption
- 6. Problem 5: Poor Image Quality in Low Light
- 7. Problem 6: Multi-Scan Registration Misalignment
- 8. Quick Reference Diagnosis Table
- 9. FAQ
1. Why SLAM Scanning Issues Differ from GNSS/Total Station Errors
Troubleshooting traditional survey equipment is highly localized. GNSS receiver faults are typically tied to satellite signal blockage or base station data-link interruptions. Total station errors are usually related to optical alignment, prism constants, or leveling calibration.
SLAM (Simultaneous Localization and Mapping) systems like the AScan X1 operate on a fundamentally different principle. Because the device continuously captures data while in motion, spatial errors accumulate over time and path length rather than occurring as an instantaneous single-point error. Understanding this continuous accumulation framework is the critical first step in diagnosing and resolving mobile 3D scanning issues.
2. Problem 1: Cumulative Point Cloud Drift
Symptom: After a long scanning path, the end of the point cloud shows obvious misalignment with the starting point. You may notice "ghosting" where the same physical object appears twice in slightly different positions within the point cloud.
Cause: SLAM systems rely on continuous environmental feature matching for localization. Over long distances and extended time, tiny calculation errors naturally accumulate. This drift becomes highly visible in long, unidirectional straight scans that lack "Loop Closures" (returning to previously mapped areas to mathematically anchor the path).
Fix: Plan your scanning trajectory to form closed loops — returning to your starting point or intentionally crossing over already-scanned areas. This enables the APEKS-CORE post-processing software to perform multi-scan registration and execute loop closure algorithms, correcting the accumulated drift. Always avoid ultra-long, one-way straight-line scanning without intersecting paths.
3. Problem 2: GNSS Signal Loss Affecting Georeferencing
Symptom: The overall geometry and shape of the outdoor point cloud look correct, but the absolute coordinate position deviates significantly from its real-world geographic location when imported into CAD or GIS software.
Cause: The AScan X1 utilizes its integrated 1408-channel GNSS antenna to provide an absolute geographic coordinate reference for the point cloud. In signal-denied environments like dense forests, urban canyons, or indoor transitions, GNSS positioning accuracy drops, which compromises the overall absolute georeferencing accuracy of the scan.
Fix: When operating in environments with restricted satellite signals, utilize an RTK + Ground Control Point (GCP) joint adjustment workflow in APEKS-CORE. By measuring physical targets with an RTK rover prior to scanning, you can manually correct the absolute coordinate accuracy using known control points during post-processing, eliminating the reliance on real-time GNSS data in denied zones.
4. Problem 3: Inconsistent Scan Coverage
Symptom: The processed point cloud exhibits sparse data density or visible "holes," particularly in room corners, high ceiling areas, or locations where the operator turned around.
Cause: This is generally an operator technique issue rather than hardware failure. Walking too quickly, turning the device too sharply, or failing to account for the 40-line LiDAR's 360°×59° field of view blind spots results in insufficient sampling density in specific areas.
Fix: Maintain a smooth, steady walking pace. When navigating corners or turning around, slow down and pause briefly to allow the scanner to capture maximum environmental detail. In highly confined or exceptionally tall spaces, deliberately adjust your holding angle and perform sweeping motions to ensure critical blind spots are swept by the laser multiple times.
5. Problem 4: Data Storage or Transfer Interruption
Symptom: The device unexpectedly stops recording during a mission, or data files become corrupted/interrupted when exporting via the USB 3.0 connection.
Cause: The built-in 256GB SSD storage has reached capacity, or the device experienced a sudden power loss during a long scan, resulting in an incomplete file write operation.
Fix: Always verify that you have sufficient storage space before beginning large scanning missions, and make it a habit to regularly export and clear processed data. Additionally, monitor power levels via APEKS-LIVE. The 47.52Wh battery supports approximately 2.5 hours of continuous operation — plan your mission durations accordingly and avoid running the unit until complete battery depletion to ensure safe file closure.
6. Problem 5: Poor Image Quality in Low Light
Symptom: The colorized point cloud output exhibits distorted colors, significant visual noise, or complete blackouts in dimly lit areas.
Cause: While the LiDAR sensor operates perfectly in total darkness, the three 2MP global-shutter cameras require adequate ambient light to capture texture data. Underexposure in low-light environments directly degrades the accuracy of point cloud colorization.
Fix: When scanning in extremely dark environments such as deep tunnels, utility basements, or unlit mine shafts, introduce temporary external lighting to improve camera imaging quality. Note that pure geometric point cloud data and structural measurements are completely unaffected by darkness; only the RGB color texture overlay is impacted.
7. Problem 6: Multi-Scan Registration Misalignment
Symptom: When merging multiple independent scans into a single project within APEKS-CORE, the stitched boundaries show noticeable misalignment, or overlapping zones fail to snap together correctly.
Cause: The independent scans lack sufficient overlapping features, or the physical environment changed between the different scanning sessions (e.g., vehicles were moved, doors were opened/closed). This causes the feature-matching algorithms to fail when seeking reliable registration reference points.
Fix: Ensure that there is at least a 30% scene overlap between any independent scans you intend to merge. Furthermore, try to execute all related scanning sessions within the same continuous timeframe to prevent environmental state changes from confusing the registration algorithms.
8. Quick Reference Diagnosis Table
| Symptom | Root Cause | First Action |
|---|---|---|
| Point cloud shows "ghosting" at path end | Cumulative drift | Plan loop-closure path, re-process in APEKS-CORE |
| Correct shape, wrong absolute position | GNSS signal loss | Use RTK + GCP joint adjustment |
| Sparse data in corners/high areas | Inconsistent coverage | Slow down at turns, adjust holding angle |
| Scan stops or file corrupts | Storage/transfer interruption | Check storage space and battery before long scans |
| Color noise in dark areas | Low-light camera exposure | Add temporary lighting for color accuracy |
| Scans don't align when merged | Insufficient overlap | Ensure 30%+ overlap between related scans |
9. FAQ
Why does my point cloud show misalignment at the end of a long scan?
This is cumulative point cloud drift. SLAM systems continuously calculate movement based on environmental features, and tiny errors build up over distance. To fix this, always plan your scanning route to include closed loops, allowing the post-processing software to correct the accumulated error.
Can GNSS signal loss be corrected after scanning is complete?
Yes. If real-time GNSS is lost in signal-denied zones, you can use Ground Control Points (GCPs) measured with a traditional RTK rover. During post-processing in APEKS-CORE, you can perform a joint adjustment to anchor the point cloud to these precise coordinates.
How much overlap is needed between multiple scans for proper registration?
You should maintain a minimum of 30% scene overlap between independent scanning missions. This provides the feature-matching algorithms in the software with enough shared geometry to securely stitch the distinct point clouds together.
Does low light affect the accuracy of the point cloud geometry?
No. The LiDAR sensor calculates distances using laser pulses, which work perfectly in total darkness. Low light only affects the global-shutter cameras, which means the resulting point cloud will have poor colorization, but the actual structural measurements will remain highly accurate.
KNOW THE FIX BEFORE THE SCAN GOES WRONG.
AScan X1 pairs 40-line LiDAR with RTK-enhanced GNSS positioning — most scanning issues trace back to technique, not hardware. Contact us for field workflow guidance.
Send an Inquiry → WhatsApp Us →