Module 6 Quick Field Guide
Camera coloring setup, scan splitting, drone mode parameters, aerial-ground fusion requirements, battery management, and data prep before processing.
Camera Coloring
Camera coloring must be configured before the scan begins. The coloring mode is determined by which software pipeline you are using. The two pipelines require different recording formats and they are not interchangeable.
Using the wrong recording format causes a coloring failure, not degraded output. Timelapse in LCC Studio or normal video in LixelStudio will produce an error or a complete coloring failure. Verify the Insta360 is set to the correct mode before every scan.
- Start the Insta360 first, then tap Go in LixelGO within 5 seconds. If the gap exceeds 5 seconds, synchronization becomes unreliable and color misalignment results.
- Do not block the Insta360 lens or either built-in body camera during scanning. A jacket sleeve, bag strap, or arm held across a camera for an extended period degrades coloring for that portion of the scan.
- Do not point cameras toward the sun or bright windows during scanning. Overexposure from direct light sources corrupts color data for the affected area.
- The scan must run for a minimum of 2 minutes for coloring to process. A scan that ends at 90 seconds does not have sufficient data for the colorization step to complete.
- Before placing Insta360 files into a project, open them in Insta360 Studio to verify: format matches the target pipeline (timelapse vs. normal), duration exceeds 3 minutes, and resolution is 6K.
Battery Management and Scan Splitting
- L2 Pro and K1: up to 90 minutes per charge under standard conditions.
- Cold weather (below 10°C): approximately 72 minutes. Plan battery counts using the 72-minute figure for cold-weather projects.
- Add time for initialization at each segment start (approximately 30 to 45 seconds each), travel between areas, and setup time.
- End scanning before battery level drops below 20%. Below 10% means under 5 minutes of runtime — end immediately.
- Do not power off during save. After tapping Stop, the device writes the project file to the SSD. This takes 30 to 60 seconds. The green LED flashing fast indicates saving is in progress. Powering off during save corrupts the project file and the data is not recoverable.
- Plan split points before battery level drops below 20%. Do not wait until the device is nearly dead.
- Scan past the intended split point by at least 15 meters to create the required overlap zone for Map Fusion.
- Begin the next segment by returning to the overlap zone and scanning at least 15 meters of the previously scanned area before continuing into new coverage.
- Map Fusion limits that apply to all split projects: maximum 10 segments, maximum 200 minutes total, maximum 20 minutes per segment, same device model throughout.
L2 Pro Drone Mode
Drone mode is available on the L2 Pro only. Compatible drones: DJI M300 RTK, M350 RTK, and M400 MTX. The drone provides RTK positioning via its own GNSS system.
- Remove the RTK module from the L2 Pro before mounting. In drone mode, the drone provides RTK. The L2 Pro's own RTK module must be removed before the device is installed in the mounting bracket.
- Mount the L2 Pro in the drone bracket and engage the green safety lock.
- Connect the L2 Pro to the drone via the Type-C power cable.
- Power the drone first. Then power the L2 Pro. When powered through the Type-C cable, the L2 Pro initializes in Drone Mode. If you power the L2 Pro with its own battery first, it initializes in handheld mode and drone positioning will not function correctly.
- Configure settings in LixelGO before takeoff. Verify Drone Mode is active in the app.
- The DJI drone will display a camera obstruction warning during flight. This is expected and does not affect the scan. The L2 Pro body partially covers a downward-facing obstacle avoidance camera. Do not abort the flight for this warning.
Drone Mode Flight Parameters
Aerial-Ground Fusion
Aerial-ground fusion combines drone imagery with ground-level scan data to produce a unified model covering both roof-level and interior geometry. The field collection procedure is the same regardless of which software pipeline is used.
- LCC Scan app version 1.2.0_p1 or higher and firmware version V3.2.3-20251104.144651 or higher are required for the aerial-ground fusion control point button to appear in the interface. If the button is not visible, update both before the site visit.
- Minimum hardware for processing: 16-core CPU, 96 to 128 GB RAM, NVIDIA RTX 4090.
- Aerial data input: 100 to 10,000 drone images.
- Plan for 24 to 48 hours or more of processing time for large sites.
- Place 4 to 5 fusion points distributed evenly across the full extent of the site. Points clustered at one end of the site will not provide adequate geometric constraint across the full project area.
- No part of the project boundary should be more than 50 to 100 meters from the nearest fusion point.
- Fusion points must be visible from both the drone (overhead) and from the ground scan path. Place them in open areas accessible during the ground scan.
- Mark each fusion point during the ground scan using the aerial-ground fusion control point button in LCC Scan.
Data Preparation Checklist
- Keep the original data on device storage until processing is complete and output has been verified. Do not delete device files after copying. Storage is not expensive relative to the cost of a return site visit.
- For Insta360 files, open in Insta360 Studio and verify: recording format matches the target pipeline (timelapse for LixelStudio, normal video for LCC Studio), duration exceeds 3 minutes, resolution is 6K. A timelapse file under 3 minutes will cause LixelStudio to crash during coloring without a useful error message.
- Confirm workstation RAM before processing: LixelStudio requires approximately 2 GB of RAM per minute of scan data. A 30-minute scan requires approximately 60 GB of RAM. A 60-minute scan requires approximately 120 GB.
- For multi-segment projects, organize each segment into its own named folder before importing. Inconsistent folder structure across a large project causes files to reference wrong segments and extends deliverable preparation time significantly.
- If drone data is included, keep it in a clearly labeled separate folder at the same level as the ground segment folders. Name it with a
_Dronesuffix to distinguish it from ground scan segments.
Critical Warnings
- Data loss Do not power off during save. After tapping Stop, the device writes the project file for 30 to 60 seconds. The fast-flashing green LED means save is in progress. Powering off during this window corrupts the project file. The data is not recoverable.
- Coloring failure Using the wrong Insta360 recording mode causes a complete coloring failure. Timelapse for LixelStudio, normal video for LCC Studio. Verify the mode before every scan. The software does not produce degraded output — it fails entirely.
- Warning The Insta360 must be started before LixelGO, within 5 seconds. Starting the scanner first and then scrambling to start the Insta360 produces color misalignment across the entire scan. There is no way to correct this in post-processing.
- Warning A timelapse file under 3 minutes will crash LixelStudio during coloring without a useful error message. Verify duration in Insta360 Studio before placing the file. Minimum 3 minutes. Overall scan minimum for coloring to complete: 2 minutes.
- Warning Remove the RTK module before mounting the L2 Pro on a drone. Leaving the RTK module attached in drone mode causes positioning conflicts between the module and the drone's own GNSS system.
- Warning Power the drone before the L2 Pro in drone mode. Powering the L2 Pro first causes it to initialize in handheld mode, not drone mode. The power sequence must be drone first, then L2 Pro via the Type-C cable.
- Warning The aerial-ground fusion button requires LCC Scan v1.2.0_p1 and firmware V3.2.3 or higher. If either is outdated, the button does not appear in the interface. Verify both versions before the site visit, not during it.
- Warning Flying above 5 m/s or above 50 m altitude degrades point density noticeably. Both values are soft limits — the scanner continues operating, but the resulting data will have gaps and reduced density that cannot be corrected after collection.
©2026 Alpine Reality Capture LLC • XGRIDS Pro Guide™ • Site Disclaimer

