Troubleshooting
Solutions for common Lixel K2 issues
Troubleshooting
Quick solutions for common Lixel K2 issues.
Power and Battery
Device Won't Power On
- Check the battery β is it clipped in fully?
- Charge the battery β try a full charge
- Clean the contacts β check the power interface for dirt or damage
- Cross-test β try the second battery to isolate device vs. battery
Never power on the device with less than 5% battery β it can damage the mainboard. Recent firmware prevents startup under low battery automatically.
Battery Shows 0% or Won't Charge
- Check that the charger, cable, and outlet work β cross-test with the other battery
- Inspect the battery and device interfaces for damage or debris
- Restart the device, exit the app, and re-pair
- If one battery charges fine and the other doesn't, replace the faulty battery; if neither works, contact support with your device serial number
Battery Care
- Fully charge batteries after each day of use
- Recharge a fully depleted battery within 3 days β deep-discharge damage is irreversible and not covered under warranty
- Top up stored batteries at least every 3 months
- Expected lifespan: 300β500 charge cycles before capacity drops to 70β80%
Connectivity
LixelGO Won't Connect
- Update LixelGO to the latest version
- On your phone, enable Location services, hotspot, and Bluetooth
- In hotspot settings: make the SSID visible and turn off any VPN
- Use a simple alphanumeric hotspot password; try the 5 GHz band
- If the device gets an IP in the wrong format (X.X.1.X), restart your phone's hotspot or reboot the phone
Phone Can't Find the Device
- Try the Wi-Fi list on another phone to isolate the issue
- In LixelGO: Settings β Device Region β Connect Device, select the device's Bluetooth ID and region, then restart the device and reconnect
"Device Signal Lost" During Scanning
- Check for Wi-Fi interference (the device keeps scanning fine when not connected to the app)
- Try switching the hotspot to 5 GHz, or use Flash Connect Mode
- Keep the phone within range and prevent the screen from sleeping
Data Transfer Issues (USB)
- Clean the USB port and use a certified cable β avoid hubs and adapters
- Restart both the device and the computer
- Temporarily disable antivirus software during large copies
- Use a file-verification tool (e.g., TeraCopy) to confirm copy integrity
- Tablets are not supported for data transfer β use a computer
RTK Issues
The K2's RTK is built in, so there is no external module to reseat β most RTK problems are configuration or network related.
Reading the Status Indicators in LixelGO
| RTK | NTRIP | Meaning | Fix |
|---|---|---|---|
| π΄ | π΄ | RTK not initialized | Power-cycle the device and try again |
| π’ | π΄ | NTRIP network not connected | Check phone internet; verify your CORS account isn't expired; try a different mount point / node |
| π’ | π’ but 0 satellites | GNSS fault (in open sky) | Power-cycle; if it persists, contact support |
"RTK Invalid" Reported During Processing
Even if the RTK indicator was green during capture:
- Confirm LixelGO showed 10+ satellites and a Fixed status
- After fixing, walk more than 10 meters before relying on the trajectory
- Keep the device tilt within 20Β° while moving
Scanning Issues
"Record-Only Mode" Warning
The environment is too degraded (featureless, repetitive, or extremely narrow) for live SLAM display. Data is still being saved.
- Stop recording as soon as practical β never continue more than 20 minutes in this mode
- Post-process with Robust Mode enabled
- If processing still reports "too few effective points" or "trajectory drift," adjust the mapping end time in the project's advanced settings to trim the drifted portion
Poor Point Cloud Quality
| Symptom | Cause | Solution |
|---|---|---|
| Sparse points | Moving too fast | Slow down (β€1.2 m/s) |
| Gaps in data | Incomplete coverage | More overlap, multiple angles |
| Noisy surfaces | Reflective materials or moisture on the LiDAR cover | Avoid direct specular surfaces; dry the cover |
| Poor color | Bad lighting or dirty lenses | Add light; clean camera lenses |
| Drift / layering | Degraded scene, fast turns | Robust Mode; slower, smoother movement |
App Shows "Device not in activatable region" (or status 316aa)
The device's serial number is region-locked and doesn't match its current location, app version, or an active VPN:
- Disable any VPN on your phone
- Make sure you installed the correct regional version of LixelGO
- Contact your sales representative to resolve region restrictions
Device Bound by Another User
- Log out of the current account in the app and log back in
- Device bindings cannot be transferred by unbinding β the account is linked to activation and warranty records. Contact support if you need help with account access.
Software Issues
LixelStudio License Activation Failed
- Verify the serial number is complete and typed exactly (watch for 0/O and 1/l) β retrieve the full SN via LixelGO
- Ensure the computer is online with correct system time (offline activation is available via the XGRIDS license-file page)
- Loan/demo units do not qualify for license activation
- If a valid, unused code still fails, contact support β do not burn a second code
LixelStudio Won't Launch or Shows a Blank Window
- Don't run it over remote-desktop software or on a virtual machine / server β both are unsupported
- Install the latest Microsoft Visual C++ redistributable (fixes
combase.dll/MSVCP140_1d.dllerrors) - Update your NVIDIA driver β AMD and Intel GPUs are not supported
- Verify OpenGL 4.0+ support
- Set the app to High Performance in Windows graphics settings
Processing Fails, Times Out, or Runs Out of Memory
- Recommended workstation: 64 GB+ RAM, NVIDIA RTX GPU with 12 GB+ VRAM (24 GB for complex projects), 1 TB+ free SSD space
- Reserve at least 5Γ the project folder size in free disk space; don't store projects on the C: drive
- Set Windows power settings to never sleep, and close other memory-heavy applications
- If your computer has two discrete GPUs, disable one β LCC does not support multi-GPU operation
LCC Reconstruction Failures
| Error | Cause | Fix |
|---|---|---|
| 0x34041002 | Program components removed by antivirus | Reinstall/repair LCC; whitelist it in your antivirus |
| 0x34040100 | Corrupt or incomplete project copy | Re-copy the project from the device and verify completeness |
| 0x34040104 | Device didn't move >1 m after initialization, or too few HD photos | Rescan with proper initialization; HD photo sets need 20+ photos with 85%+ overlap |
Also note: LCC needs scans longer than 1 minute (3+ minutes if LixelStudio post-processing is also planned).
LCC Can't Log In ("Network is not available")
Corporate firewalls must allow https://*.xgrids.com (at minimum https://api-gw.xgrids.com) on port 443.
Physical Damage
- Do not attempt repairs
- Document the damage with photos
- Contact support with your warranty card info
Contact Support
If issues persist:
- Email: support@splatlabs.ai
- Include: Serial number, a description, and a short video of the fault if possible
- Attach: Screenshots, error reports, or log files if relevant
- Response time: Usually within 24 hours