Connection Mode Troubleshooting
Most LCC Scan connection failures have one specific cause and one specific fix. Working the right sequence gets you connected without burning time on steps that cannot help.
The Three Connection Modes
Knowing which mode you are in tells you which failures are possible. Two of the three are wireless and share the same failure modes. The third bypasses wireless entirely.
Wireless range is 65.6 ft (20 m). Before troubleshooting anything else, stand next to the device. Range and obstruction account for a share of failures that look like software problems, and the manual is explicit that the phone should be close to the PortalCam during connection.
Direct Connect Will Not Find the Device
- Confirm the device is on and out of startup. Solid green is standby and ready. Slow blue flash means it is still starting. No LED means it is off.
- Stand next to the device. Distance and walls first, everything else second.
- Confirm the phone hotspot is on. In Direct Connect the PortalCam joins the hotspot. With hotspot off, nothing else matters.
- Confirm Bluetooth is on. LCC Scan discovers the device over Bluetooth before handing off to WiFi.
- Check app permissions. Location, Bluetooth, and Local Network all need to be granted. A single missing permission blocks the connection and the app does not always say which.
- Look for a WiFi network beginning with PCAM in the phone's own WiFi list. This is the diagnostic fork. If the network is visible there but LCC Scan cannot find the device, you have a permission or app problem, not a hardware one. If the network is not visible at all, continue to the next item.
- Change Device Region in app settings. The PortalCam broadcasts on region-specific WiFi channels. A device that has moved between regions can broadcast on a channel your phone does not scan, which makes the network invisible. Setting the region to your current location resolves it.
- Confirm the app is current. An outdated LCC Scan build is worth ruling out before escalating.
Hotspot Naming
The PortalCam parses your hotspot name and password. Special characters, emoji, and very long names cause failures that look identical to every other connection problem and respond to nothing except simplifying the credentials.
- Short name, letters and numbers only. No spaces, hyphens, underscores, or symbols.
- Simple password, 8 to 12 alphanumeric characters.
- If it connected before and stopped after a phone update, check whether the update reset your hotspot name to the phone's model name. Those often contain characters the device cannot parse.
Bridge Mode Will Not Connect
Bridge Mode needs both devices on the same network on the same frequency band. Most failures here are one of three things.
- Same network and same band. A phone on the 5 GHz band and a PortalCam on the 2.4 GHz band of the same router look like the same network and cannot talk to each other. This is the most common Bridge Mode failure.
- Client isolation. Many corporate, hotel, and public networks block devices on the network from reaching each other. If isolation is on, Bridge Mode cannot work on that network and no setting on your end changes it. Switch to Direct Connect.
- Ask the site before you rely on it. On a client network, confirm with facilities or IT that device-to-device traffic is permitted before planning a job around Bridge Mode.
When a site network is uncooperative, stop fighting it. Direct Connect needs nothing from the building. Bridge Mode is a convenience, not a requirement, and a locked-down corporate network is not a problem you can solve from the app.
The Connection Drops Mid-Scan
The scan does not stop. The PortalCam records to its own internal storage and keeps capturing when the phone falls out of range. What you lose is the live preview, the ability to add control points, and the ability to stop cleanly from the app.
Walk back into range and reconnect. The session resumes with the scan still running and the data intact. Do not power the device off and do not assume the segment is lost.
If you cannot reconnect, stop the scan at the device. Double-press the device button on the body to end the segment, then wait for the fast green flash to finish before touching anything. Powering off instead of stopping properly corrupts the project file, and that data is not recoverable.
One consequence worth planning around: if the drop happens before you have marked the control points for a Map Fusion seam, you cannot add them from the app until you reconnect. Mark control points while the connection is solid rather than saving them for the end of the segment.
Firmware Updates
Battery above 50 percent, every time, no exceptions. An update interrupted by a dead battery can corrupt the firmware and send the device back for factory repair. The LED alternates red and green throughout. Do not power off, do not move the device, do not drop the connection.
Small Updates: Through the App
- Confirm the battery is above 50 percent. Check it in the device status panel.
- Connect in LCC Scan and open the device information screen. If an update is available it appears here, and the app prompts you when one exists.
- Start the update and leave the device alone. Red and green alternating means it is running.
- Wait for solid green. That is the finish signal. Nothing before it is.
Large Updates: Over USB
Updates larger than 1 GB cannot install through the app. If the app shows no update but you know one was released, this is why.
- Download the firmware from the XGRIDS website to your computer.
- Put the device into USB mode and connect it with the included USB 3.0 cable. The LED turns solid blue.
- Copy the firmware file to the device root directory. Not into a subfolder.
- Power the device off, then restart it. The upgrade begins automatically on restart. Wait for solid green before disconnecting.
Do this before you travel. A large update needs a computer, a cable, and a download. None of that is convenient on a client site, and control point marking will not work correctly on outdated firmware.
When To Call Us
If the sequences above have not resolved it, stop troubleshooting and get in touch. Collecting these four things first turns a multi-day exchange into a single reply.
- Device serial number, from the device status panel in LCC Scan or the device body.
- Phone model and operating system version, exactly. Connection problems are frequently phone-specific.
- What you were doing and when it failed. Connecting, mid-scan, during an update, and the approximate time.
- The app logs. In LCC Scan, open App Settings and use Logs to share the error log. This is the file that tells us what actually happened.
We are your first call, not XGRIDS. As your dealer we can resolve most issues directly and escalate to XGRIDS engineering with the diagnostic detail already attached when it needs to go further. Going direct usually costs you a round trip.
Module 7 complete. Ready to process your PortalCam data?
Continue to Module 9: LCC Studio©2026 Alpine Reality Capture LLC • XGRIDS Pro Guide™ • Site Disclaimer