XGRIDS Pro Guide™ / Module 7: Advanced PortalCam

Module 7 Quick Field Guide

LCC Scan app controls, control point marking, field quality review, map fusion collection, and connection troubleshooting for the PortalCam.

Section 1

LCC Scan App Controls

LCC Scan is the PortalCam's field control app. It handles scanning, control point marking, real-time preview, and connection management. It does not connect to the L2 Pro or K1 — those devices use LixelGO.

Before Starting a Scan

Confirm connection to the PortalCam via Direct Connect or Bridge Mode before tapping record.
Verify battery level is sufficient for the planned segment. PortalCam provides up to 60 minutes per charge. Plan swaps before battery drops below 20%.
For Map Fusion projects, confirm each planned segment stays under 20 minutes. Segments over 20 minutes cannot be used in Map Fusion.
Confirm project name and naming convention match the rest of the session. Inconsistent names cause fusion failures.

During and After Scanning

Fast green LED flash means the device is saving. Do not power off. When you stop a scan, the device writes the project file immediately. Powering off during save corrupts the data and it is not recoverable.
Use the pause function for brief interruptions only. A pause of a few minutes is generally safe. A pause of 10 or more minutes in a scene where anything has changed (doors opened, people moved) can degrade tracking continuity enough to affect the scan result.
After stopping, review the mobile viewer before leaving the area. Check the coverage tool for red zones. Red means the data in that area is unlikely to produce usable reconstruction, not that it is slightly degraded.

Section 2

Control Point Marking

Marking Procedure in LCC Scan

Approach the target marker and stop with the PortalCam within 1 to 2 meters of it.
Tap the control point button in LCC Scan and enter the exact point name.
Do not power off within 5 seconds of adding a point. The device needs 5 seconds to complete writing the control point data to the project file.
Photograph each control point location with your phone as you mark it. These reference photos let you find the exact position when beginning the next segment that needs to share the same points. A control point named and marked 1.2 meters from where it was in the first segment may still fall within position tolerance, but the photo removes all ambiguity.
Measurement points and control points are different functions in LCC Scan. Control points are used for fusion and accuracy. Measurement points are reference labels only. Do not use measurement points as a substitute for control points in a Map Fusion workflow.

Section 3

Mobile Viewer Field Quality Check

Field Verification Checklist

Open the mobile viewer immediately after each segment ends, before moving to the next area.
Run the coverage analysis tool. Red zones require rescanning before you leave. Do not dismiss red coverage as a display issue — it means the data in that zone will not produce usable reconstruction in LCC Studio.
Check a representative measurement in the viewer to verify tracking quality. A 5-meter corridor reading as 8 meters in the viewer indicates a drift or tracking problem, not a measurement tolerance issue. If readings are significantly off, the segment should be rescanned.
The mobile viewer renders the raw, unprocessed SLAM output, not a final processed model. Some imperfections visible in the viewer may improve after LCC Studio processing. The coverage tool is the authoritative field check, not visual appearance alone.
Confirm battery is above 50% before performing any firmware update. Never begin a firmware update below 50% charge — an interrupted update can corrupt the device firmware and require a factory repair.

Section 4

Map Fusion Collection Strategy

PortalCam Map Fusion Rules

Minimum overlap between adjacent segments: 15 meters. Under 10 meters causes fusion failure. Plan overlap zones of 20 to 30 meters to ensure you have buffer for field conditions.
Complete overlap between segments also causes failure. If one segment's scan path is entirely contained within another segment's path, LCC Studio cannot determine the correct spatial relationship between them. Each segment must have its own unique coverage area in addition to the shared overlap zone.
End segment 1 at least 15 meters inside the planned overlap zone before stopping. Begin segment 2 at least 15 meters before the end point of segment 1 so the first 15 meters of segment 2 cover the same geometry as the last 15 meters of segment 1.
Control point names must match exactly between segments, including capitalization. A point named FP_01 in segment A and fp_01 in segment B will not be recognized as the same point and the connection will fail.
Every segment must connect to at least one adjacent segment through shared control points or RTK. A segment with no connection method cannot be fused and must be rescanned with correct connection points in place.

Section 5

Connection Troubleshooting

Problem

Likely Cause

Fix

LCC Scan cannot find the device

Phone not connected to the PortalCam WiFi network, or wrong connection mode selected

Verify phone WiFi is connected to the PortalCam hotspot. In LCC Scan, select the correct connection mode (Direct Connect or Bridge) and retry.

Connection drops mid-scan

Phone WiFi dropped, hotspot timeout, or distance from device

The PortalCam keeps recording after a connection drop. Re-enable the phone hotspot and reconnect in LCC Scan. The scan data is not lost.

Bridge Mode not working

Router not in range, or device not assigned a correct IP on the local network

Confirm the router is within range of both the phone and the PortalCam. If IP assignment fails, switch to Direct Connect mode for the session.

Live preview is black or frozen

Connection latency, or the scan has not yet started

Wait 10 to 15 seconds after starting the scan for the preview to initialize. If still blank, disconnect and reconnect in LCC Scan without stopping the scan.

Firmware update failing or stuck

Battery below 50%, or unstable connection during update

Charge to above 50% before attempting any firmware update. Maintain a stable connection throughout. Do not switch connection modes during an update.

A connection drop does not stop the scan. The PortalCam records independently of the phone connection. If LCC Scan disconnects mid-scan, the device keeps capturing. Re-establish the connection to resume monitoring, but do not assume the data was lost.

Section 6

Critical Warnings

Data loss Fast green LED flash means saving. Do not power off. The PortalCam writes the project file immediately after stopping a scan. Powering off during save corrupts the project file. The data is not recoverable.
Device damage Never begin a firmware update below 50% battery. A firmware update interrupted by a dead battery can corrupt the device firmware and require a factory repair. Check battery level first, every time.
No recovery Red zones in the coverage tool require rescanning before you leave. Red does not mean slightly degraded data. It means the data in that zone will not produce usable reconstruction in LCC Studio. There is no processing workaround.
Warning Do not power off within 5 seconds of marking a control point. The device needs 5 seconds to write control point data to the project file. A control point added and then immediately followed by power-off will not appear in the project.
Warning Measurement points are not control points. They are reference labels only and cannot be used for Map Fusion connections or accuracy improvement. Only control points (marked via the control point button) function in fusion workflows.
Warning Complete segment overlap causes fusion failure. If one segment's scan path is entirely inside another segment, LCC Studio cannot determine the spatial relationship between them. Every segment must have its own unique coverage area beyond the shared overlap zone.
Warning Control point names are case-sensitive across segments. FP_01 and fp_01 are treated as different points. A mismatched name causes the connection to fail silently — no error is displayed, the segment simply cannot fuse.
Warning A pause of 10 or more minutes can degrade tracking continuity if the scene has changed. Pausing briefly while you move an obstacle is fine. An extended break that allows people to move through the frame or doors to change state risks a tracking failure on resume.

Previous Module 6 Field Guide Next 7.1 LCC Scan App