XGRIDS Pro Guide™ / Module 2: Hardware Setup

Module 2 Quick Field Guide

The need-to-know numbers and decisions for the field.

Section 1

Device Quick Reference

L3

LiDAR range0.7-120 m (2.3-394 ft)

LiDAR FOV360° × 270°

Scan speed320,000 (16-ch) or 640,000 (32-ch) pts/s

Weight~5.5 lbs with battery

Storage1 TB UFS (built-in)

Battery100 minutes total operating time

Relative accuracy5 mm (0.2 in) at 1 sigma, post-processed, indoor test

Point cloud coloringReal-time, on device

Point cloud outputYes (LixelStudio)

3DGS outputYes (LCC Studio)

Drone modeIn development (DJI Matrice 400)

RTK moduleBuilt-in, survey grade

L2 Pro

LiDAR range120 m (394 ft) or 300 m (984 ft)

LiDAR FOV360° × 270°

Scan speedUp to 640,000 pts/s

Weight3.7 lbs

Storage1 TB SSD (built-in)

Battery~90 min per charge

Relative accuracy≤1 cm (0.4 in) within 100 m (328 ft)

Point cloud coloringPost-processed (LixelStudio)

Point cloud outputYes (LixelStudio)

3DGS outputYes (LCC Studio)

Drone modeYes (DJI M300/M350 RTK)

RTK moduleExternal (optional, removable)

K2

LiDAR range100 m (328 ft) max; 40 m (131 ft) @10%, 70 m (230 ft) @80%

LiDAR FOV360° × 59° (-7° to +52°)

Scan speed~200,000 pts/s

Weight~2.6 lbs

Storage512 GB internal eMMC

Battery~90 min per charge

Relative accuracy≤1 cm (0.4 in) within 10 m (33 ft)

Point cloud coloringReal-time, on device

Point cloud outputYes (LixelStudio)

3DGS outputYes (LCC Studio)

Drone modeNo

RTK moduleBuilt-in (UM980)

PortalCam

LiDAR range30 m (98 ft) @10%; 60 m (197 ft) @90%

LiDAR FOV180° × 180°

Scan speed856,000 pts/s

Weight1.9 lbs without tripod

Storage512 GB eMMC (built-in)

Battery~60 min per charge

Relative accuracy≤2 cm (0.8 in)

Point cloud coloringN/A (3DGS workflow)

Point cloud outputNo

3DGS outputYes (LCC Studio only)

Drone modeNo

RTK moduleNo (basic GPS supported)

L2 Pro Model Variants

Spec

16-120

32-120

32-300

LiDAR channels

Maximum range

120 m (394 ft)

300 m (984 ft)

Scan speed

320,000 pts/s

640,000 pts/s

Tunnels / degraded environments

Challenging

Supported

Building height limit

120 m (394 ft)

180 m (591 ft)

Full specs and the device comparison table: 2.3 Hardware Overview.

Section 2

The Two Output Pipelines

Every project produces one output type or both. The two cannot be converted into each other after processing. Full detail: 2.2 Two Workflows.

Point Cloud (LixelStudio)

License: code tied to the device serial

Devices: L3, L2 Pro, and K2

Use for: BIM, measured deliverables, Revit/AutoCAD/Navisworks, survey, as-built

Export: LAS/LAZ, E57, RCP, PLY, OBJ (with texture)

Dimensions: Yes

3D Gaussian Splat / 3DGS (LCC Studio)

License: Free Edition generates models; Premium Edition adds Map Fusion, Aerial-Ground Fusion, Aerial Reconstruction, HD Enhancement, and Spatial Recognition

Devices: L3, L2 Pro, K2, and PortalCam

Use for: Client walkthroughs, presentations, virtual tours, visual documentation

Export: .lcc and .lcc2 (Free); .ply, .usd, 3D Tiles (Premium)

Dimensions: Reference only, not for engineering use

PortalCam produces 3DGS only. It cannot produce point clouds under any workflow. If the project needs measured deliverables, use an L3, L2 Pro, or K2.

What LCC Studio supports on the K2. XGRIDS lists the K2 for Single Model reconstruction, Map Fusion, and Aerial-Ground Map Fusion, and lists the Lixel K series for HD Enhancement. Those fusion and enhancement modes need Premium. A K2 single scene is bounded by the device capture ceiling and by workstation memory, not by any time limit in the software, so multi-segment 3DGS work does not require a particular device.

Section 3

Software Pairings at a Glance

Application

Role

Works With

LixelGO

Mobile field control: scanning, RTK, GCP marking, real-time preview.

L3, L2 Pro, K2

LCC Scan

Mobile field control for PortalCam: scanning and connection modes.

PortalCam

LixelStudio

Desktop point cloud processing.

L3, L2 Pro, K2

LCC Studio

Desktop 3DGS processing. Free Edition and Premium Edition. Requires NVIDIA GPU.

L3, L2 Pro, K2, PortalCam

System requirements and processing times: 2.4 Software Map.

Section 4

Key Concepts and Accuracy Numbers

Full explanations: 2.1 SLAM vs. Static and 2.5 Critical Basics.

Drift. SLAM position error compounds over distance. You manage it with a clean initialization, loop closures, and control points.
Loop closure. Return to a previously scanned area within 40 degrees of your original viewing angle to trigger a correction. The L3, L2 Pro, and K2 all apply it in real time, visible in the LixelGO preview.
Relative accuracy. Internal geometric consistency. Achieved through technique alone, no RTK or GCPs required.
Absolute accuracy. Real-world coordinate position. Requires RTK, PPK, or GCPs configured before the scan.

Device

Relative accuracy

Absolute accuracy

5 mm (0.2 in) at 1 sigma, post-processed

2 cm (0.8 in) RMSE with RTK, open sky

L2 Pro

≤1 cm (0.4 in) within 100 m (328 ft)

≤3 cm (1.2 in) with RTK or GCPs

≤1 cm (0.4 in) within 10 m (33 ft)

3 cm (1.2 in), max 5 cm (2 in), with RTK

PortalCam

≤2 cm (0.8 in)

3DGS only

Section 5

Decisions You Cannot Undo After the Scan

Most scanning mistakes are recoverable. These are not.

Must Decide Before Scanning

Georeferencing strategy. RTK active before scanning, or GCPs placed and marked during the scan. There is no way to add georeferencing later. Miss it on a project that needs absolute coordinates and the site must be re-scanned.
Output pipeline. L3, L2 Pro, and K2 raw data feeds LixelStudio, LCC Studio, or both from one session. No pre-scan setting is needed, but confirm deliverables first so your technique supports both (loop closures, camera data, overlap). PortalCam goes to LCC Studio only.
Camera coloring. Whether the scanner records camera data is set in LixelGO before scanning and cannot be added later. The color display mode (RGB, elevation, intensity) can still be changed in LixelStudio anytime.
Project naming convention. Inconsistent names across sessions cause fusion failures. Set the convention before the first session of a multi-segment project.

Section 6

Before You Leave Site

End-of-Session Site Checklist

Scan stopped cleanly. The LED reached solid green before the device was powered off.
The project appears in LixelGO or LCC Scan with a reasonable duration and file size for the area covered.
The real-time preview shows no large gaps in areas you walked through.
If RTK was used, the device moved at least 10 m (33 ft) while the status was Fixed, with more than 100 valid RTK-fixed points. Keep continuous unfixed sections to 328 ft (under 100 m) on the L2 Pro and 164 ft (under 50 m) on the K2.
If GCPs were used, all control point names match the coordinate CSV exactly, including capitalization.
If this is a multi-segment project, the overlap zone with the next segment is fully covered and includes at least two loop closures.
A quick walkaround confirms no area was missed that cannot be captured in a follow-up session.

Section 7

Critical Warnings

No recovery Scanning without georeferencing when the client requires absolute coordinates means re-scanning the site. RTK and GCPs must be in place before the first recording starts.
No recovery PortalCam data cannot produce point clouds. If the project needs BIM-ready measured output and you scanned only with a PortalCam, the site must be re-scanned with an L3, L2 Pro, or K2.
Warning Loop closure requires returning within 40 degrees of your original viewing angle. Returning to a room facing the opposite wall is not a loop closure. Drift keeps accumulating.
Warning AMD GPUs are not supported by LCC Studio or LixelStudio. Both need an NVIDIA GPU with CUDA. AMD CPUs (e.g., Ryzen 9) are fully supported and XGRIDS-recommended for LCC Studio. Verify GPU compatibility before installing on a new machine.
Warning LCC Studio Premium is required for Map Fusion, Aerial-Ground Fusion, Aerial Reconstruction, HD Enhancement, Spatial Recognition, and .ply, .usd, and 3D Tiles export. The Free tier covers single-scene generation and .lcc and .lcc2 export. Confirm your license tier before accepting a project that needs a Premium feature.
Warning The K2 maximum LiDAR range is 100 m (328 ft). For tall structures, large open outdoor sites, or tunnels and degraded environments, use the L2 Pro (up to 300 m (984 ft) on the 32-300 model).
Warning 3DGS output is not reliable for dimensional measurement. Do not extract engineering or construction dimensions from a 3DGS model. Use the point cloud workflow for measured output.
Warning No XGRIDS scanner writes NAD83 at capture. The L2 Pro and K2 record WGS84, CGCS2000 and ITRF2008, with geodetic height, and output absolute coordinates directly in WGS84 and CGCS2000 only; the L3's real-time coordinate conversion is WGS84 and CGCS2000 only. NAD83 or another regional datum is a transformation in LixelStudio on every device.

Previous: Module 1 1.7 PortalCam Setup Next 2.1 SLAM vs. Static Scanning