10.7 Device Specifications
Side-by-side comparison of the L2 Pro, K2, and PortalCam, complete specification tables for each device, legacy reference, and the processing workstation requirements for both software pipelines.
Choosing Between the Three
Every row below is a decision point that changes what you can deliver. Output type, georeferencing, and mount options are the three that most often decide whether a device can do a job at all. The full specification tables follow.
The two duration rows are different facts that happen to share their numbers. Maximum single capture is a firmware limit: recording stops there whatever the power situation. Runtime per battery is how long a charge lasts. They coincide because the hardware was engineered that way, not because either one is a sensible scan length. Neither is a scan target, and on most workstations the reconstruction memory in Section 6 will bind long before either.
No XGRIDS scanner can resume a scan from a breakpoint. If a scan stops for any reason, that recording is closed and the next scan is a new segment. Recovery is Map Fusion, not resumption, and Map Fusion needs overlap you must have already captured. Plan segment boundaries before you start rather than discovering one mid-scan.
Lixel L2 Pro
The L2 Pro ships in three configurations differentiated by LiDAR channel count and working range. The sensor, camera, accuracy, and physical specifications are identical across all three. The differences are scan speed and working range only.
L2 Pro 16/120
Channels: 16
Working range: 0.5 m to 120 m (1.6 ft to 394 ft)
Scan speed: 320,000 pts/s
Entry configuration. Sufficient for most AEC use cases with building heights under 394 ft (120 m).
L2 Pro 32/120
Channels: 32
Working range: 0.5 m to 120 m (1.6 ft to 394 ft)
Scan speed: 640,000 pts/s
Higher point density than 16/120. Recommended configuration for most professional use. Best scan efficiency of the three models.
L2 Pro 32/300
Channels: 32
Working range: 0.5 m to 300 m (1.6 ft to 984 ft)
Scan speed: 640,000 pts/s
Extended range for tall structures and large outdoor environments. Better drift management than 120 m models at distance. Building height support up to approximately 590 ft (180 m).
Reading the output format rows across devices. XGRIDS publishes output at two different levels of detail. The L2 Pro sheet lists what the device itself writes (.las and .jpg); the K2 sheet lists what the full pipeline produces, including mesh, 3DGS, 3D Tiles and USD. Both devices feed LixelStudio and LCC Studio, so both reach the same export set. The K2 row below is longer because its source document is more complete, not because the K2 outputs more than the L2 Pro.
Conditions attached to the L2 Pro accuracy figures. Absolute accuracy assumes no continuous RTK or GCP disconnection longer than 328 ft (100 m). Relative accuracy applies between two points less than 328 ft (100 m) apart. Repeat accuracy assumes two RTK-enabled scans with no disconnection. Point cloud thickness is measured within 33 ft (10 m) of the walking path. A figure quoted without its condition is not the figure XGRIDS published.
Storage planning for L2 Pro. The 1 TB internal SSD holds approximately 12 to 16 hours of raw scan data at 60 to 80 GB per hour of scanning. Offload data to a processing workstation after each project. The SSD is not swappable; the only offload method is USB 3.1 Gen2 data transfer in USB mode or via the LixelGO app.
Lixel K2
The K2 is XGRIDS' second-generation handheld scanner. It replaces the previous handheld in current production with extended range, real-time true-color point cloud rendering, and built-in RTK. The K2 ships ready for georeferenced scanning without any external module. K2 is handheld only; it does not support backpack, vehicle, or drone mounts.
Guided Mode and RGB Mode are a pre-scan choice you cannot reverse. Selecting RGB Mode gives you real-time true colour but removes the Scan Assist System and the Scan Quality view, which are the only in-field checks on coverage density. Selecting Guided Mode keeps those checks but shows elevation or quality colouring rather than true colour. If nobody is reviewing coverage on site, use Guided Mode and check the Scan Quality view before leaving. Use RGB Mode when a client is watching the screen or when true-colour confirmation matters more than a coverage check.
K2 reconstruction modes in LCC Studio. The K2 supports single-scene reconstruction, Map Fusion with up to 10 sub-scenes per run, and Aerial-Ground Map Fusion. Single-scene length is bounded by the 90-minute device capture ceiling and by the memory available on the processing workstation; LCC Studio itself imposes no time limit. Aerial-Ground Map Fusion requires the ground scan data, the drone imagery, and the takeoff and landing point photos together, and reconstruction cannot start if any one of the three is missing. See Module 9 for the full processing workflow.
Two figures for K2 absolute accuracy, and both come from XGRIDS. The published specification sheet states 3 cm RMSE. The dealer New Product Introduction states 3 cm with a 5 cm maximum, on both the real-time and post-processed tables. The rows above carry the fuller dealer figure because it is the one that matters when a client holds you to a tolerance. Quote 3 cm as the specification and plan for up to 5 cm on demanding work. All absolute figures assume open sky, no multipath, good satellite geometry, and favourable atmospheric conditions.
Storage planning for K2. The 512 GB internal eMMC holds approximately 6 to 8 hours of raw scan data. Internal storage is not field-swappable. Offload data to a processing workstation after each project via USB 3.1 Gen2 or LixelGO.
PortalCam
The PortalCam pairs a 96-channel LiDAR with 180 by 180 degree coverage and a four-camera array whose combined fisheye field exceeds a full sphere, optimized for close-range, high-fidelity indoor capture. It outputs 3D Gaussian Splat models through LCC Studio only. Point cloud output is not supported. It does not produce absolute georeferenced coordinates.
IP rating note. XGRIDS has not published an IP rating for the PortalCam. Treat the device as unrated. Do not expose it to rain, high humidity, or dusty environments, and do not assume it matches the other scanners, which are rated IP54.
Direct sunlight. The PortalCam operating temperature range applies in indirect sunlight only. Do not scan in direct sun for extended periods, and do not leave the device in direct sun between segments. Heat soak in an enclosed vehicle or on an exposed rooftop will exceed the rated range well before ambient air temperature does.
What the PortalCam geometry figures mean. The relative and repeat figures above describe internal geometric consistency within a reconstruction. They are not a measurement tolerance and they are not an absolute accuracy specification, because the PortalCam produces no georeferenced output. Do not quote them in a proposal or a scope of work. If a client needs a number they can hold you to, the job needs an L2 Pro or a K2.
Segment planning across batteries. Three separate numbers bound a PortalCam job and they are easy to run together. The firmware stops a recording at 60 minutes. A battery lasts about 60 minutes of continuous scanning. XGRIDS capture guidance is 30 minutes or less per capture, which is the number that should drive your plan and is what makes at least two segments per battery achievable. Fusion adds its own two caps: 10 segments and 200 minutes combined. Reconstruction memory climbs with scan length on top of all of it, so a working segment length well below 30 minutes is the practical target. See 7.4 PortalCam Map Fusion.
Lixel K1 (Legacy)
The K1 is no longer in production. The K2 replaces it in current shipments. K1 specifications are retained here for existing K1 owners. K1 firmware updates and LixelStudio and LCC Studio support continue.
Legacy storage planning. The 256 GB internal card holds approximately 3 to 4 hours of raw scan data and is not user-replaceable, so a full day of scanning is managed by offloading rather than by swapping cards. Transfer completed projects to the workstation between site visits and confirm the transfer before clearing anything from the device.
Processing Computer Requirements
Both pipelines are Windows only and both require an NVIDIA GPU. The specifications below are the published requirements for each application. Buy or build against the workflow you actually run, because Map Fusion and Aerial-Ground Fusion demand more than single-scene reconstruction does.
LixelStudio
Point cloud processing. Free with hardware.
LCC Studio
3D Gaussian Splatting reconstruction. Subscription-priced.
Map Fusion and Aerial-Ground Fusion
Multi-segment stitching and high-compute reconstruction need more than the recommended single-scene configuration. Running fusion below these thresholds produces out-of-memory failures and incomplete fusion outputs.
Memory and Scan Length
Memory is what limits a single reconstruction on a real workstation. Neither the battery nor the device capture ceiling is the operative constraint, and there is no software ceiling at all: LCC Studio imposes no time-based rejection and no built-in timer, so it will accept and attempt a scan far larger than the machine can finish.
The software predicts the failure before it happens, if you read the estimate. LCC Studio estimates memory demand from the uploaded data and displays it before the run. A red Estimated Memory reading means the job is too large for this machine, and the fix at that point is to drop Reconstruction Quality to Standard, add memory, or split the capture. Committing past a red estimate ends in an out-of-memory failure with nothing to recover. The error code and the workflow are on 9.2 Single Scene Processing.
Alpine working target: 12 to 15 minutes per segment. The table above is the ceiling, not the plan. A failed reconstruction on a 45-minute scene costs a day and cannot be partially recovered, and reconstruction time scales with scan length at roughly 20 minutes of processing per minute of capture. Planning at 12 to 15 minutes leaves room for unexpected coverage without approaching either limit. XGRIDS makes the same point from the field side: it does not recommend capturing a full-length dataset in one session on any hardware, because a single fault inside a long capture can cost the entire dataset.
Disk Headroom
Configurations that will not work, whatever the specification. Neither application runs on a virtual machine, on Windows Server, on Linux, or on macOS. Neither uses more than one GPU: multi-GPU parallel processing is not supported and the software selects a single GPU automatically, so a second card adds nothing to processing. AMD and Intel graphics cards are unsupported with no workaround, though AMD processors are fully supported and appear in the recommended configurations above. The NVIDIA card must be RTX 20 series or above with CUDA 11.6 or above, running driver version 580 or above. Older 10-series cards are to be avoided regardless of memory size. Project data must be processed from a local internal disk: external drives, USB flash drives, and network paths are a documented cause of post-processing crashes.
Laptops. XGRIDS publishes no laptop-specific configuration, and the published guidance is to use a desktop for large datasets because laptops thermal-throttle under sustained load and can crash mid-reconstruction. A laptop that meets the LCC Studio basic GPU and memory figures above will process short scans. For production work on large projects, multi-segment fusion, or aerial-ground fusion, specify a desktop.
Check current XGRIDS product documentation at xgrids.com before purchasing hardware, as specifications change between product revisions.
©2026 Alpine Reality Capture LLC • XGRIDS Pro Guide™ • Site Disclaimer