10.2 FAQ

L2 Pro: Campus-scale coverage, 1 TB SSD, 3 cm RMSE absolute accuracy with RTK. Runs on LixelStudio (point cloud) and LCC Studio (3DGS).

K1: Single-building scale, 256 GB swappable TF card. Same dual-software pipeline as L2 Pro, lighter and more compact.

PortalCam: Highest visual fidelity. 96 LiDAR channels, 512 GB eMMC. LCC Studio only. Cannot produce point clouds or georeferenced output.

Full comparison: 10.7 Device Specifications.

No. The L2 Pro and K1 are rated IP54 (protected against light splashes, not sustained rain). The PortalCam does not have a formal IP rating. Do not expose the PortalCam to rain, moisture, or dusty environments.

Beyond hardware risk, raindrops cause laser refraction that introduces noise and can corrupt SLAM tracking. Data from rainy sessions is rarely recoverable. Water damage is not covered under warranty.

L2 Pro and K1: -20 to 50 degrees C (-4 to 122 degrees F). PortalCam: -20 to 45 degrees C.

Cold weather reduces battery runtime by approximately 20% below 5 degrees C. Add one extra battery. Do not attempt startup below 5% battery: this can damage the mainboard. Firmware V3.0+ prevents startup under low battery automatically.

Runtime: L2 Pro and K1: ~90 min. PortalCam: ~60 min. Cold weather reduces by ~20%.

Lifespan: 300 to 500 charge cycles before capacity drops to 70 to 80%.

Storage: Fully charge after each day of use. If unused, recharge within 3 months. If critically low, recharge within 3 days or irreversible damage occurs (not covered under warranty). Store cool and dry.

Yes, through Map Fusion. Scan in segments up to 20 minutes, swap batteries, and stitch segments in post-processing. Supports up to 10 segments / 200 minutes combined. Segments must overlap by 50 to 100 ft (15 to 30 m). All segments from the same device type. Plan break points before scanning.

Target 12 to 15 minutes per segment. Maximum 20 minutes. This applies to all scanning, not only Map Fusion projects.

Longer scans (up to ~35 min) can process as standalone segments but require proportionally more RAM (~2 GB per minute), take significantly longer, and carry higher failure risk. See 6.2 Scan Splitting.

Both LixelStudio and LCC Studio require Windows 10/11 and an NVIDIA GPU. AMD GPUs are completely unsupported for both applications.

LixelStudio (point clouds, free with hardware):

• GPU: NVIDIA RTX 3060 (12 GB) minimum
• CPU: Intel i7 11th gen or equivalent, 6+ cores
• RAM: 64 GB recommended (supports segments up to ~30 min)
• Storage: 1 TB SSD

LCC Studio (3DGS, $2,500/year Premium):

• GPU: NVIDIA RTX 2080 Ti (11 GB) or RTX 3060 (12 GB) minimum. RTX 4090 for production throughput. NVIDIA driver 520.0+ required. CUDA mandatory.
• CPU: Intel i7 8700K or AMD Ryzen 7 1700X or equivalent
• RAM: 64 GB minimum. 96 to 128 GB for projects at or above 150 minutes total.
• Storage: 1 TB SSD. LCC Studio writes substantial intermediate data; running out of space corrupts the project.

A workstation built for LCC Studio runs LixelStudio without issue. Full details: LixelStudio System Requirements and LCC Studio System Requirements.

Stop the scan cleanly in LixelGO. Do not power off while "Project saving..." is displayed.

Swap the card: Power off completely (no hot plugging). Insert a formatted spare. Create a new project and overlap the end of the previous segment by 50+ ft (15+ m). Stitch with Map Fusion.

Transfer and reuse: Remove the card, transfer to workstation via card reader, reformat in LixelGO before reinserting.

The 256 GB card holds ~3 to 4 hours at 60 to 80 GB/hour. Carry a labeled spare for full-day projects.

LixelGO (L2 Pro/K1): Android 8 GB RAM minimum, Snapdragon 8 series preferred. iOS A12 Bionic or later.

LCC Scan (PortalCam): Android 8 GB RAM minimum. iOS 17.5+ recommended. Bluetooth 5.0 and WiFi 5 required.

Both apps need personal hotspot capability for RTK/NTRIP. Use simple hotspot names (no special characters or spaces).

LixelStudio (free with hardware) produces point clouds for Revit, AutoCAD, Navisworks, and GIS. Use it when the deliverable requires measurement, BIM modeling, or survey output.

LCC Studio ($2,500/year Premium) produces 3DGS models for presentations, virtual tours, and web sharing. Use it when the client needs a visual experience.

On L2 Pro and K1 projects, the same raw data feeds both pipelines. No special scan settings needed. The PortalCam connects to LCC Studio only.

The website-downloaded version requires network for: creating models, starting processing, uploading data, and creating share links.

Viewing does not require network. Use View mode to open previously generated models offline. All functions except publishing work without connectivity.

For fully offline environments, the standalone LCC Viewer V1.10.0 opens local .lcc files with no network, no login, and no server communication. See the LCC Viewer FAQ below.

Yes. The standalone LCC Viewer V1.10.0 opens local .lcc files with no registration, login, or network. Download from xgrids.com.

Limitations: Files must be on the local disk (no network drives). One model per viewer window (multiple windows supported). Cannot merge models. V1.10.0 is the final version.

For multiple models in one window, use View mode in LCC Studio instead.

No. LCC Studio requires NVIDIA with CUDA. LixelStudio also requires NVIDIA. AMD GPUs are completely unsupported for both applications with no workaround.

Yes. Minimum laptop GPU: RTX 3080 Ti (16 GB) or RTX 4080 Ti (16 GB). Less VRAM fails on medium and large scans.

Desktops outperform laptops on sustained loads due to thermal throttling. For production work, multi-segment fusion, or aerial-ground fusion, a desktop with RTX 4090 is recommended. Windows only.

Multi-GPU is available only on the LCC Studio Linux Server version, not Windows desktop. Contact your XGRIDS sales representative for the private deployment solution.

Three codes per device. Each binds to a specific machine and cannot be unbound. Contact your XGRIDS sales manager for additional or temporary codes.

No. These are fundamentally different data structures. Neither can be converted to the other after processing.

If both outputs are needed, run both pipelines from the same raw scan data. Do not discard raw data until both are processed and verified.

Portability simplifies the lighting model so the output runs on mobile devices and web browsers. Reduces file size 30 to 50%.

Enable: Web sharing, mobile viewing, WebGL embedding, or sending to clients without high-end hardware.

Disable: Maximum visual realism on a workstation, or when USDZ export is needed.

Cannot be changed after processing without restarting reconstruction.

LiDAR works in darkness (generates its own light). Point cloud geometry is valid. However, cameras need ambient light for color data. In complete darkness, 3DGS output is unusable.

Bring portable lighting, reduce speed to 0.5 m/s or slower, and increase scan passes.

No. SLAM requires continuous motion. After the 30-second initialization, move continuously. Standing still wastes time without adding data.

No. RTK is required only when the deliverable needs absolute coordinates tied to a real-world system. For interior documentation, BIM from a single session, or facility management without georeferencing, SLAM without RTK is sufficient.

For exterior work, multi-session campus projects, or geospatial integration, RTK or GCPs are required. See 10.8 Accuracy Reference.

• Multipath interference. Nearby structures or canopy reflect signals. Move to open area and wait 2 to 3 minutes. Persistent drops mean GCPs are needed for that section.
• NTRIP connection drop. Verify hotspot name has no special characters. Confirm NTRIP credentials in LixelGO.
• Insufficient satellites. Need 10+ valid. Walk to more open position.
• Antenna tilt. Must stay within 20 degrees of vertical during movement.

After upload, verify valid data count exceeds 100 in LixelStudio RTK panel. See 4.2 RTK Positioning.

Caused by light contrast during transitions. Camera exposure adjusts mid-frame, producing blur the reconstruction cannot resolve.

Processing: Enable Exposure Optimization in LCC Studio. Set PPR to Normal.

Field: Turn sideways through doorways. Turn on all interior lights. Slow to 0.5 m/s before each threshold.

Firmware V3.0+ auto-saves on critical low battery. On older firmware, unexpected shutdown can corrupt the project file.

Stop and save properly at 15 to 20% battery. Do not wait for automatic shutdown.

The scanner operates in sunlight, but camera quality is significantly better on overcast days. Direct sun creates harsh shadows that reduce coloring quality.

Best: midday on cloudy days. If sun is unavoidable, scan early morning or late afternoon and plan multiple passes from different directions.

One segment per floor, under 20 minutes each. Scan stairwells with ascending and descending passes. Loop at each landing. Place GCPs on each floor within the same control network. Stitch with Map Fusion (up to 10 segments / 200 minutes). See Module 5.

Start in an area with rich features: furnished rooms, structured intersections, equipment areas. Avoid featureless corridors or areas with moving objects. SLAM needs strong feature matching during initialization.

Place control points near distinctive geometry (furniture clusters, equipment panels, column intersections). A control point in a plain corridor relies entirely on the marker with no corroborating geometry.

Most common causes in order:

• Insufficient RAM. LixelStudio needs ~2 GB per minute of scan. 64 GB recommended for standard workflows.
• Project on the C: drive. Write to a dedicated data SSD, not the system drive.
• Insufficient disk space. Need 2 to 3x raw data size in free space.
• Other applications running. Close browsers and office software before processing.
• Version mismatch. LixelStudio 2.4.5 or earlier with firmware 1.4+ causes failures. Update both.

For "LIO Drift" errors, enable Robust Mode. See 10.4 Error Messages.

No. This is normal. The SLAM phase can hold at 5.1% for 30 minutes or more before advancing. This is the most common processing concern reported by new users.

Environments with repetitive geometry (data centers, warehouses, long symmetric corridors, parking structures) take the longest because the algorithm has fewer unique features to differentiate.

Do not close LCC Studio, restart the project, or shut down the workstation. Interrupting forces a complete restart from 0%. If the application has not crashed and the system is responsive, processing is still active. Let it run.

On recommended hardware (RTX 3070+, 64 GB RAM):

• LixelStudio: 20 to 30x scan duration. 10-min scan = 3 to 5 hours.
• LCC Studio (Standard): ~20 min per 1 min of scan. 10-min scan = ~3.3 hours.
• HD Enhancement: Add 50 to 100% to base time.
• Map Fusion (10 segments): Several hours. Plan overnight.
• Aerial-Ground Fusion: 24 to 48+ hours.

RTX 4090 processes 3 to 4x faster than RTX 3060 for LCC Studio. See 10.9 Estimating.

Standard is the correct starting point for all production work. It balances visual quality, processing time, and VRAM usage. Use it for first-attempt processing on every project.

Slow produces higher visual fidelity but requires significantly more VRAM and processing time. Use it for final deliverables where maximum quality justifies the cost. On underpowered hardware, Slow quality may fail mid-process due to VRAM overflow.

Fast is for previews only. It processes quickly but produces noticeably lower visual quality.

Quality cannot be changed after processing without restarting reconstruction from scratch.

Not recommended. Each consumes significant GPU, RAM, and disk I/O. Running both simultaneously may cause failures or crashes.

Process one pipeline to completion before starting the other, or use two separate machines. Both can be installed on the same computer; the restriction is on simultaneous processing jobs.

Yes, if: overlap areas exist, GCPs are present, and the scene remained relatively static between sessions. Changes (moved furniture, construction activity) cause blurring or ghosting.

Use the same firmware version for all segments. Partial replacement is not supported. To replace one segment, re-collect it and reprocess all segments together.

SLAM optimization exceeded the maximum time. Usually caused by high-complexity data (repetitive features, long corridors, difficult lighting). Solutions: break into shorter segments, enable Robust Mode, add control points, or review scanning technique.

SLAM tracking failure with accumulated trajectory error. Work through in order:

• Enable Robust Mode and reprocess. Resolves majority of drift artifacts without returning to site.
• Check loop closures. Long linear corridors without returns produce progressive drift.
• Check scan speed. Above 1 m/s in repetitive environments degrades SLAM confidence.
• Add GCPs in poor-structure areas. White rooms, mirrors, featureless corridors.

If Robust Mode does not resolve it and technique was correct, rescan the segment.

Three causes in order:

• Insufficient overlap. Need 50+ ft (15+ m) of shared geometry. Under 33 ft (10 m) causes failure.
• Internal drift in one segment. Reprocess with Robust Mode. If unresolved, recollect.
• Control point name mismatch. Must match exactly including case. "CP1" and "cp1" do not connect.

See 5.6 Troubleshooting Fusion.

• Camera sync issue. Verify correct video coloring option and complete file transfer.
• Inconsistent lighting. Lights switching on/off or large window exposure shifts during scan.
• Speed too high. Above 1 m/s creates temporal offset between camera frames and LiDAR.

See 10.8 Accuracy Reference.

LCC Studio includes a measurement tool, but results are approximate and vary with model quality. This feature is experimental.

Best technique: Capture from multiple angles. Switch to Pivot mode. Align camera straight-on to measurement plane. Enable Pro Measurement Mode. Keep one X/Y/Z axis at 0.

Even with correct technique, these are not survey-grade. For measured deliverables, use LixelStudio point cloud output.

Use LCC Studio's one-click web publish. Process the model, click Publish, and share the URL. The recipient opens it in any modern browser on desktop or mobile. No app install, no account, no software required.

Set Portability On before processing to optimize file size for web and mobile viewing. LCC format files are 70 to 90% smaller than PLY, which is what makes browser streaming practical.

For clients with restricted network environments, export the .lcc file and send it directly. They can view it in the free LCC Viewer with no network or login required.

Ask what software they use before you scan.

• Revit (BIM): RCP or E57 via Recap
• Navisworks / AutoCAD: RCP or E57
• ArcGIS / QGIS: LAZ with georeferenced coordinates
• 3DGS visualization / web: LCC (smallest) or PLY (broadest compatibility)
• Unreal / Unity: LCC via SDK, or PLY via plugins
• Cesium / WebGIS: 3D Tiles (requires absolute coordinates, under 4M Gaussian points)
• NVIDIA Omniverse: USDZ (firmware 3.0+, single-scene, Portability Off)

See 10.6 Platforms.

Yes. Requires Spatial Recognition enabled during LCC Studio processing (Premium only). Also requires a separate authorization code from your XGRIDS sales representative. Supports Revit 2025 and 2026 only. See 9.6 LCC Revit Plugin.

LiDAR cover: Included cloth, wipe gently in one direction. Small dust generally does not affect performance. Isopropyl alcohol is acceptable.

Camera lenses: Clean before every scan session. Dirty lenses directly degrade color and 3DGS quality.

Device body: No alcohol on aluminum (causes paint damage). Dry or lightly damp cloth only.

L2 Pro / K1: through LixelGO. PortalCam: through LCC Scan. Check for updates before every major project. Keep LixelStudio and firmware versions matched (2.4.5 or earlier with firmware 1.4+ causes failures). Never interrupt a firmware update. See 10.5 Firmware Updates.

Format through LixelGO (L2 Pro/K1) or LCC Scan (PortalCam). Do not use Windows or macOS disk utilities. Verify all data has transferred before formatting. The operation is irreversible.

XGRIDS Technical Support: xgrids.com/intl/technical-support or your authorized reseller. Have the device serial number ready.

Alpine Reality Capture clients: alpinerealitycapture.com or call (801) 824-6162.