2.4 Software Map
Four applications. Two pipelines. Each has a specific, non-interchangeable role. Knowing which software connects to which device, and what it can and cannot do, prevents the most common setup errors before they happen.
The Four Applications
The XGRIDS software ecosystem consists of two field apps (one per device family) and two desktop processing applications (one per output pipeline). None of these are interchangeable. Using the wrong app with a device results in a connection failure. Processing data through the wrong desktop application produces either an error or an output that does not match the project requirement.
LixelGO
iOS and Android. Connects to the L2 Pro and K1 via WiFi. Controls scanning start and stop, displays a real-time point cloud preview during the session, manages control point marking, and configures RTK and NTRIP settings. This is the operator's primary field interface for both LiDAR devices. It does not process data.
Android: 8 GB RAM, Snapdragon 865 or equivalent, Android 10 or later
iOS: A12 Bionic or later, 4 GB or more RAM, iOS 17.5 or later recommended
Both: Bluetooth 5.0 or later, WiFi 5 or later, personal hotspot capability required for RTK/NTRIP
LCC Scan
iOS and Android. The PortalCam's dedicated field control app. Not interchangeable with LixelGO. Controls PortalCam scanning, displays a real-time quality preview, manages control point marking during the session, and monitors device status. If you own a PortalCam, this is your field app. If you own a K1 or L2 Pro, LixelGO is your field app.
Direct Connect via phone hotspot: most reliable mode, recommended for all scanning sessions
Bridge mode via shared WiFi network: available but more susceptible to interference
LixelStudio
Windows 10/11 desktop application. Processes L2 Pro and K1 raw data into point clouds. Handles SLAM trajectory optimization, RTK and PPK coordinate transformation, ground control point application, map fusion for multi-session projects, and export to LAS, LAZ, E57, OBJ (with texture), and RCP. AMD GPUs are not supported. Requires NVIDIA GPU.
CPU: Intel i7 11th generation or equivalent, 6 or more cores
GPU: NVIDIA RTX 3060 12 GB minimum (AMD not supported)
RAM: 32 GB minimum (supports approximately 15 minutes of scan); 64 GB recommended for standard workflows
Storage: 1 TB SSD minimum. Install path must not contain spaces or non-ASCII characters
OS: Windows 10 or Windows 11
LCC Studio
Windows 10/11 desktop application. Processes L2 Pro, K1, and PortalCam data into 3D Gaussian Splat models. Requires NVIDIA GPU with CUDA. AMD GPUs are completely unsupported with no available workaround. Supports single scene, map fusion, and aerial-ground fusion reconstruction modes. Exported formats include LCC, PLY, OBJ (without texture), USDZ, and 3D Tiles.
CPU: Intel i7 8700K or equivalent, any mainstream processor from 2017 or later
GPU: NVIDIA RTX 2080 Ti (11 GB) or RTX 3060 (12 GB) minimum (AMD not supported, CUDA mandatory)
RAM: 64 GB minimum
NVIDIA driver: version 520.0 or later required
OS: Windows 10 or Windows 11
Device and Software Pairing
Every device has a specific field app and a specific set of processing options. The PortalCam's path is entirely separate from the L2 Pro and K1 path from the first moment of connection through the final processed output.
Processing Hardware: What Matters and Why
LixelStudio: RAM Is the Constraint
LixelStudio holds the entire scan trajectory in memory during SLAM optimization. This means your available RAM directly determines the maximum scan duration you can process in a single session. Attempting to process a scan longer than your RAM supports will cause a mid-run failure.
Projects requiring scans longer than your RAM supports must be broken into shorter segments and joined using Map Fusion. See Module 5: Map Fusion for the complete planning and processing workflow.
GPU performance in LixelStudio scales processing speed, with an improvement of approximately 30 to 40 percent when moving from a 6-core to an 8-core CPU. The RTX 3060 12 GB is the stated minimum. 24 GB VRAM supports datasets of 200 million points or more.
LCC Studio: GPU Is the Constraint
LCC Studio is a GPU-dominant workload. CUDA is mandatory. AMD GPUs are completely unsupported with no workaround. Processing speed and the maximum output quality are both determined by your GPU's VRAM.
For Map Fusion and Aerial-Ground Fusion projects in LCC Studio, XGRIDS recommends a 16-core processor, 96 to 128 GB RAM, and an RTX 4090 for optimal performance. These are more demanding workloads than single-scene reconstruction.
For large models with a total scan duration of 150 minutes or more, 96 to 128 GB of RAM is recommended in LCC Studio. If RAM is insufficient, use Medium Quality or Standard Quality processing settings to reduce the risk of failure. High or Ultra quality settings on underpowered hardware will likely fail mid-process.
Mobile Device Requirements
LixelGO and LCC Scan both run on iOS and Android. The connection between the field app and the scanner is WiFi. For RTK and NTRIP configuration, the phone must be capable of providing a personal hotspot.
- Android: 8 GB RAM minimum, Snapdragon 865 or equivalent, Android 10 or later
- iOS: A12 Bionic chip or later, 4 GB RAM or more, iOS 17.5 or later recommended
- Both platforms require Bluetooth 5.0 or later and WiFi 5 or later
- Personal hotspot capability is required when using RTK with an NTRIP correction service
- Charge or carry a power bank for sessions exceeding 60 minutes. The field app must remain active throughout the scan
Processing Time Expectations
Processing is not fast. Build realistic time into every project schedule. Running either software on underpowered hardware extends these estimates significantly and increases the risk of failure.
These ratios are based on recommended hardware configurations. Processing on minimum-spec hardware will take longer. Higher quality settings in LCC Studio extend processing time beyond these estimates. Draft quality is significantly faster and appropriate for preview purposes.
LCC Studio's first launch after installation compiles CUDA kernels, which takes 2 to 5 minutes. This is a one-time process per installation.
©2026 Alpine Reality Capture LLC • XGRIDS Pro Guide™