Troubleshooting Index

LixelGO or LCC Scan cannot find the device, or repeatedly drops the connection.

• Confirm Location Services, Hotspot, and Bluetooth are all enabled on the phone.
• In hotspot settings: disable hidden network (SSID must be visible), disable WiFi 6 protocol, and turn off any active VPN.
• Verify the hotspot password contains only simple alphanumeric characters. Special characters cause silent failures.
• If still failing, switch the hotspot band to 5 GHz if supported by your device and phone.
• LixelGO must be at a currently supported version. Earlier versions cannot connect reliably via either WiFi or USB. If you are on an old version, update before scanning.

RTK status will not progress to Fixed, or drops after Fix is achieved.

• Confirm LixelGO shows more than 10 satellites before beginning the scan.
• After RTK status reads Fixed, walk at least 33 ft (10 m) before beginning the scan path. RTK data collected during the initial fix period is often insufficient for processing.
• Keep the RTK antenna tilt within 20 degrees during movement. Exceeding this invalidates the RTK fix record even when the LED remains green.
• K2 note: K2 has built-in UM980 RTK (no external module). Antenna tilt management still applies to the device orientation as a whole.

Tracking confidence dropped during scanning, or the device flagged drift in the field.

• Stop the scan, reduce walking speed, and rescan the affected area with closer attention to loop closures.
• In featureless environments (long blank corridors, large open spaces), add ground control points to anchor the trajectory.
• If tracking dropped while transitioning between very different lighting conditions, slow down through the transition or use supplemental lighting to reduce the contrast jump.

Mobile viewer shows red coverage zones after the scan completed.

• Red zones in the coverage analysis tool require rescanning before leaving the site.
• Identify the cause (skipped area, walking too fast, too far from surfaces) and rescan that section with corrected technique.
• Recheck the coverage tool after the rescan. The data captured at the original walk does not become usable in processing.

LixelStudio reports SLAM optimization failed or processing stopped with a drift error.

• Enable Robust Mode and reprocess. Robust Mode recovers many scans that standard processing cannot complete, but may reduce absolute accuracy slightly.
• If Robust Mode fails, review the processing report. It identifies the specific location and likely cause of the drift.
• If the drift was caused by an identifiable segment (a long featureless corridor, an abrupt environment change), use Advanced Settings to set the mapping end time before the drift point. The earlier portion may be processable.
• If processing still fails after these steps, the data from the drifted portion cannot be recovered. Escalate Contact XGRIDS and submit poses.csv from the project folder for collection pose verification.

LixelStudio coloring step fails or produces blank output.

• Confirm LixelStudio is at v4.0 or later. v4.0 introduced photo-realistic coloring; earlier versions have known coloring limitations.
• For L2 Pro projects, verify the panoramic video captured during the scan transferred completely from the device. A missing or corrupted video file produces blank coloring.
• K2 note: K2 produces real-time true-color point clouds during scanning. Coloring is not a separate post-processing step on K2.
• Confirm the workstation has sufficient free disk space (at least 2x the project size), is not set to sleep during processing, and has no other memory-intensive applications running.
• Confirm the GPU is not a GTX 10-series or older. LixelStudio coloring requires CUDA 11.6 or higher, which 10-series hardware does not support. Update GPU drivers to the latest version from NVIDIA directly.
• If none of the above applies: Escalate Contact XGRIDS technical support.

Map Fusion fails or produces a misaligned result.

• Verify that each scan session was processed individually and successfully before attempting fusion.
• If using RTK: confirm both sessions have valid RTK data. A session with RTK invalid cannot fuse with an RTK-valid session.
• If using control points: control point names must be identical across sessions, case-sensitive. A control point named "CP1" and one named "cp1" will not match.
• Confirm the scans have adequate physical overlap. Sessions that only share a doorway or a narrow corridor connection are borderline. Sessions that share 65 ft (20 m) or more of common path are reliable.
• K2 note: K2 Map Fusion is supported in LixelStudio v4.0 (with K2 firmware v2.4.1 or later), but NOT in LCC Studio v1.13. If you are fusing K2 data, you must use LixelStudio.

Processing hangs, sleeps, or repeatedly stalls on the workstation.

• Go to Windows Settings, System, Power and Battery, Screen and Sleep. Set both Screen and Sleep options to Never.
• Open Task Manager and end any background processes not required for processing. Close browsers, communication apps, and cloud sync services during long processing runs.
• Restart the processing job. Do not pause and resume mid-job.

Processed point cloud shows drift or trajectory bending.

• Reprocess with Robust Mode enabled. This corrects many mild drift cases.
• If Robust Mode does not resolve it, the scan path needs to be modified. Shorter scan segments with more frequent loop closures reduce the likelihood of drift accumulating.
• For areas where drift consistently occurs (long corridors, featureless rooms), add ground control points during field collection. This anchors the trajectory and prevents drift accumulation.

Color is misaligned with point cloud geometry.

• Confirm the correct panoramic video file is linked to the project. The video timestamp must correspond to the scan session.
• Check that the time-sync calibration was performed before the scan. If it was not, the color offset is unfixable in post-processing.
• If colors are present but washed out or too dark, the issue is video exposure. This is a field issue, not a processing fix. Future scans should avoid strong direct light sources or dark interiors without supplemental lighting.

3DGS output (LCC Studio) is blurry or has missing geometry.

• Confirm the panoramic camera data matches the collected point cloud project and is stored at the correct path.
• Inspect the camera lens. On the L2 Pro, the button on the panoramic camera must face outward. A reversed lens produces permanently blurred output.
• Confirm the lens is not blocked by RTK cables, a case, or debris.
• Review the scan path. Single-direction linear paths produce insufficient multi-angle material for reconstruction. The scan must include S-patterns, spirals, and multiple passes from different angles.
• Update LCC Studio and the Viewer to the latest version. Reconstruction algorithms have improved significantly across recent releases.

LAS or LAZ export fails silently or produces an empty file.

• Shorten the LAS filename to 20 characters or fewer. This is the most common cause and is not shown as an error message.
• For E57 export: if the data has no absolute coordinates, use pose.csv. If the data has absolute coordinates (RTK or GCP), use pose_no_offset.csv. Selecting the wrong file produces a failed or empty export without a clear error.

LixelStudio crashes on launch or fails OpenGL initialization.

• Update the Visual C++ Redistributable libraries from Microsoft. Search for "latest supported vc redist" on the Microsoft support site.
• Update the NVIDIA GPU driver. LixelStudio does not support AMD graphics cards.
• Open the LixelStudio installation directory and run contextinfo.exe. Confirm the OpenGL version is 4.0 or higher. If it is lower, a GPU driver update or hardware change is required.
• Disable Core Isolation in Windows Security settings. This setting can block OpenGL initialization on some configurations.