Start Here

Two Core Workflows

XGRIDS produces two fundamentally different output types. They cannot be converted between each other after processing.

Running Both Workflows on the Same Project

L3, L2 Pro, and K2 raw data can be processed through LixelStudio, LCC Studio, or both from a single scan session. No special capture settings are needed. Confirm your required deliverables before scanning to ensure your field technique supports both outputs: adequate loop closures, camera data enabled, and sufficient overlap between sessions.

• LixelStudio installed, activated, and tested before the project
• LCC Studio installed and your license tier confirmed for the features you need (Map Fusion and HD Enhancement require Premium)
• Plan for additive processing time from both pipelines

Software

Four applications, two pipelines. Each has a specific, non-interchangeable role. See 2.4 Software Map for the full ecosystem overview.

Which App Goes With Which Device

Processing Time and System Requirements

Both applications are demanding on hardware, and undersized machines fail mid-run rather than simply running slowly. Processing roughly follows a 20 to 30x ratio to scan duration.

Before Your First Real Scan

The complete procedure is in Module 1: Getting Started.

Pre-Field Checklist

• LixelStudio installed, activated, and opened at least once on the processing computer
• LCC Studio installed if 3DGS output is required, with network connectivity available
• Processing computer confirmed against the system requirements (see 1.3 System Requirements)
• LixelGO or LCC Scan installed and signed in on your mobile device
• Scanner batteries fully charged. L2 Pro and K2: about 2 hours from empty. PortalCam: about 90 minutes to full, about 70 minutes to 90 percent
• Scanner storage confirmed. K2: 512 GB internal eMMC. L2 Pro: 1 TB SSD. Budget 60 to 80 GB per hour
• Processing computer storage confirmed. Budget 50 GB per project
• Coordinate system and georeferencing method decided
• NTRIP credentials configured and RTK fix tested (if using RTK). K2 has built-in RTK (UM980). L2 Pro requires the external RTK module to be installed and seated firmly
• GCPs placed, surveyed, CSV prepared. Names match exactly what you will type in LixelGO. Case-sensitive
• Site walkthrough completed: access, hazards, route, GNSS obstructions identified
• Mobile device charged. Power bank packed for sessions over 60 minutes

Decide Your Coordinate Strategy Before You Scan

This cannot be changed after the fact. RTK must be configured before scanning. GCPs must be placed and marked during the scan. See 4.1 When Georeferencing Matters.

GCP Rules for the Field

• L2 Pro: spacing 328 ft (within 100 m of each other). K2: spacing 164 ft (within 50 m of each other). Evenly distributed
• Points cannot be collinear. Three-dimensional distribution required
• CSV names must exactly match LixelGO entries, character for character, including case
• Hold the scanner steady for 5 seconds after marking. Do not jar the device
• After the last GCP, continue scanning for 15 seconds before ending the session

Full GCP procedure: 4.5 Control Point Marking During Scanning.

Field Technique

Post-processing cannot compensate for poor technique. Full reference: Module 3: Field Technique.

Loop Closure

SLAM drift accumulates over distance. The correction mechanism is loop closure: returning to an area you have already scanned so the system can detect the match and distribute the correction across the trajectory.

Initialization

Errors here persist for the entire session. See 3.1 Movement and Posture Fundamentals for the complete procedure.

Walking Speed

Those speeds are the L2 Pro and K2. On the PortalCam, walk no faster than 1.6 ft/s (0.5 m/s) anywhere, and 1.0 ft/s (0.3 m/s) indoors, in dim light, at doorways and around corners.

Standing still does not improve quality. The system needs motion for coverage. Move continuously, slowly where it matters. See 3.3 Transitions.

Device Posture

• Hold vertically at chest to shoulder height. Keep tilt under 20 degrees from vertical on the L2 Pro and under 15 degrees on the K2; keep the PortalCam within -60 to +60 degrees
• In corridors under 6.5 ft (2 m) wide, turn the device sideways so LiDAR captures both walls
• Maintain 1.6 ft (0.5 m) clearance from walls and obstacles
• Rotate your whole body when turning, not just your arms

Route Planning

• Scan backbone corridors first, then branch into rooms. Return to the corridor between each room
• Build midpoint loops into the route, not just a final return to start
• Plan at least 4 loop intersections for complex or narrow environments
• Return to your initialization point at the end of every session
• Corridors or tunnels over 1,000 ft (300 m): break into segments, use Map Fusion
• Never plan a pure out-and-back linear path

Stopping the Scan

Double-tap the power button (both presses within 500 ms). Wait for solid green before touching the device again.

Before Leaving Site

• Solid green confirmed
• LixelGO preview reviewed for coverage gaps
• All control point names confirmed as entered correctly
• Coordinate CSV accessible for processing
• Data transfer plan confirmed

Full post-scan procedure: 1.6 Post-Scan Review and Data Transfer.

Common Early Mistakes

Full troubleshooting: 10.3 Troubleshooting Index.

• Moving during initializationCorrupts the reference frame. Entire session carries that error. Only fix: restart.
• Lifting the scanner before the app confirms initializationKeep the device still at least 15 seconds after the point cloud appears.
• Walking too fastDegrades visual SLAM and reduces point density. The fastest way to produce unusable data in tight spaces.
• Linear routes without loopsDrift accumulates with no correction. No post-processing step fixes this.
• Trusting RTK without verifying Fixed statusRequires Fixed (not Float), more than 10 satellites, 33 ft (over 10 m while Fixed) of movement, and more than 100 valid RTK data points. Verify in LixelGO. See 4.2 RTK Positioning.
• Mismatched GCP namesCSV names must match LixelGO entries exactly, every character. A name mismatch can be corrected after the scan by supplying a new spreadsheet of control point names, so it does not cost a return visit. See 4.5 Control Point Marking.
• Processing with insufficient RAMA 30-minute scan can fail mid-processing on an undersized machine. Confirm your hardware first. See 1.3 System Requirements.
• Running LCC Studio and LixelStudio simultaneouslyBoth consume GPU, RAM, and disk I/O. Run one to completion before starting the other.
• Powering off during saveFast-flashing green = still writing. Wait for solid green. Every time.
• No preview before leaving siteLixelGO shows coverage gaps. Discovering a gap at the office means returning to site.
• Deciding coordinate strategy after the scanRTK must be configured before scanning. GCPs must be marked during the scan. No way to add georeferencing after the fact. See 4.1 When Georeferencing Matters.

Understanding Accuracy

Accuracy in mobile SLAM is not a single number. These specs reflect results achieved with proper technique and, for absolute accuracy, proper georeferencing.

Relative accuracy = internal consistency. Whether dimensions hold across the scan. Achieved through good technique and loop closure. No georeferencing required.

Absolute accuracy = registration to real-world coordinates. Requires RTK, PPK, or surveyed GCPs.

SLAM drift is the primary threat to both. It compounds over distance and is corrected only through loop closure and control points.