10.3 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 (the SSID must be visible), disable WiFi 6 protocol, and turn off any active VPN.
• Verify the hotspot name and password contain only simple alphanumeric characters. Special characters and spaces cause silent failures.
• If still failing, switch the hotspot band to 5 GHz if both the phone and the device support it.
• Confirm the app is at a currently supported version. Older releases cannot connect reliably over either WiFi or USB.
• If the phone cannot create a hotspot at all, use Bridge Mode: put the phone and the scanner on the same existing network with internet access.

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 fix record even when the LED remains green.
• Keep any continuous unfixed section under 328 ft (100 m) on the L2 Pro. XGRIDS publishes no separate K2 figure; keep K2 unfixed sections short relative to its shorter range.
• K2 note: the K2 has built-in UM980 RTK with no external module, so tilt management applies to the orientation of the whole device.

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 such as long blank corridors and 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 add supplemental lighting to reduce the contrast jump.
• Note that no XGRIDS scanner can pause a scan. If you need to break here, stop the segment cleanly and plan to rejoin the parts with Map Fusion.

The PortalCam mobile viewer shows a red model quality indicator after a scan.

• The indicator is analysed automatically after each scan: green is excellent, yellow is good, red is poor. Red means the segment is unlikely to reconstruct usably, not that it is slightly degraded.
• Rescan before leaving the area. Identify the cause first: a skipped zone, walking too fast, or working too far from surfaces.
• Work at about an arm's length from surfaces, with a hard floor of 1.6 ft (0.5 m), and back off to about 3.3 ft (1 m) from highly reflective surfaces.
• Re-check the indicator after the rescan. Data captured on the original walk does not become usable in processing.

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

• Switch the Mode dropdown from Standard to Robust and reprocess. The Mode dropdown is on the Project Settings panel of the Project Processing dialog. Robust recovers many scans that Standard cannot complete.
• If Robust succeeds, review the trajectory in the preview and verify output quality before delivery.
• If Robust also fails, review the processing report, which identifies the location and likely cause of the drift.
• If processing still fails, the drifted portion cannot be recovered and the area must be rescanned. Escalate Contact us with poses.csv from the project folder for collection pose verification before committing to a return visit.

LixelStudio coloring step fails or produces blank output.

• Confirm LixelStudio is current. Recent releases introduced photo-realistic coloring; older releases 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: the K2 produces real-time true-color point clouds during scanning, so coloring is not a separate post-processing step.
• Confirm the workstation has free disk space of at least twice the project size, is not set to sleep during processing, and has no other memory-intensive applications running.
• Coloring is reported to require CUDA 11.6 or later, which rules out GTX 10-series and older hardware. Both published LixelStudio configurations already exceed that floor, so this affects only machines below the published minimum. Update GPU drivers from NVIDIA directly.
• If none of the above applies: Escalate

Map Fusion fails or produces a misaligned result.

• Verify that each segment was processed individually and successfully before attempting fusion.
• If using RTK: RTK data must be valid for every project in the fusion. A segment with invalid RTK cannot fuse with an RTK-valid segment.
• If using control points: names must be identical across segments, including capitalization. "CP1" and "cp1" will not match. Names must also not be reused for different physical locations across projects.
• Confirm adequate physical overlap. The minimum is 50 ft (15 m) of shared geometry, with 50 to 100 ft (15 to 30 m) recommended. Segments sharing only a doorway or a narrow corridor are borderline.
• Confirm no segment sits entirely inside another. Complete overlap prevents the algorithm from determining the spatial relationship.
• All segments must come from the same device model, and 16-channel and 32-channel L2 Pro units cannot be fused together.
• Pipeline note: both pipelines support the K2. LixelStudio Map Fusion covers the L2 Pro and K2 with current firmware; LCC Studio Map Fusion covers the L2 Pro, K2, and PortalCam. The per-segment limits differ, so size the job against the pipeline that will process it. See 10.2 FAQ.

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

• Open Windows Settings, System, Power and Battery, Screen and Sleep. Set both Screen and Sleep to Never before starting. A sleep or hibernate event during SLAM optimization corrupts the run.
• Open Task Manager and end background processes not required for processing. Close browsers, communication apps, and cloud sync services during long runs.
• Restart the job from import. LixelStudio has no processing pause, so there is no resume point to return to. Its only pause is on the Remote Transmission point cloud stream, which is unrelated to a processing run.
• Confirm the workstation meets the published minimum: 64 GB of memory at both configuration tiers. A 32 GB machine is below specification regardless of CPU and GPU.

Processed point cloud shows drift or trajectory bending.

• Reprocess with the Mode dropdown set to Robust. This corrects many mild drift cases.
• If Robust does not resolve it, the scan path needs to change. Shorter segments with more frequent loop closures reduce drift accumulation.
• An effective loop means returning to scanned geometry facing within roughly 40 degrees of the original line of sight. Returning to the same spot facing the opposite way does not close the loop.
• For areas where drift consistently occurs, such as long corridors and featureless rooms, add ground control points during field collection to anchor the trajectory.

Color is misaligned with point cloud geometry.

• Confirm the correct panoramic video file is linked to the project and that its timestamp corresponds to the scan session.
• Check that time-sync calibration was performed before the scan. If it was not, the color offset cannot be fixed in post-processing.
• Walking speed above 3.3 ft/s (1 m/s) captures camera frames and LiDAR points at slightly different moments, producing color bleed at surface transitions.
• If colors are present but washed out or too dark, the cause is exposure during capture, not processing. Avoid strong direct light sources and unlit interiors without supplemental lighting.
• K2 note: real-time true-color rendering happens during scanning, so K2 misalignment is a scan-time issue rather than a video-file or processing issue.

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

• Confirm the camera data matches the collected point cloud project and is stored at the correct path.
• Inspect and clean every lens before the scan. Fingerprints and dust degrade texture across the whole model and cannot be corrected in processing.
• Confirm no lens was blocked by cables, a case, or debris during capture.
• Review the scan path. Single-direction linear passes produce insufficient multi-angle material. The scan needs S-patterns, multiple heights, and repeat passes from different angles.
• Update LCC Studio and the Viewer. Reconstruction algorithms have improved substantially across recent releases.

I need to stop mid-scan and continue afterward.

• There is no pause on any XGRIDS scanner. The PortalCam offers start and stop only, and stopping ends the segment and writes the project file.
• Plan the break as a segment boundary instead. Reach a location with strong surrounding geometry, capture the overlap, mark the shared control points, then stop cleanly.
• Rejoin the parts in LCC Studio with Map Fusion: up to 10 segments, up to 35 minutes each, 200 minutes combined.
• Do not remove the battery to stop a scan. The battery button is the power button, and pulling power during the save write corrupts the project file.

A control point I marked never appeared in LCC Studio.

• The device needs 5 seconds after Add to finish writing the control point. Powering off or pulling the battery inside that window loses the point while the scan data survives.
• Confirm the LCC Scan app and device firmware are current. On older builds the control point button does not behave as documented.
• Check the name. Matching across segments is case-sensitive, and a name reused for a different physical location will not behave as expected.
• Confirm you selected a fusion marker type. A POI is a reference label only and carries no alignment function.

The LCC Scan connection dropped during a scan.

• A connection drop does not stop the scan. The PortalCam records to its own internal storage and continues capturing.
• Bring the phone back into range and reconnect to resume monitoring. Do not assume the data was lost.
• Wireless range to the app is about 66 ft (20 m). Plan route breaks around that distance on large floorplates.
• If connection failures persist after a change of location, set Device Region in the app.

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

• Shorten the filename to 20 characters or fewer. This is the most common cause and produces no error message.
• For E57 export: use pose.csv when the data has no absolute coordinates, and pose_no_offset.csv when it has RTK or GCP absolute coordinates. The wrong choice produces a failed or unusable export with no clear error.

LixelStudio crashes on launch or fails OpenGL initialization.

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