START WITH CONFIDENCE.
CAPTURE. PROCESS. DELIVER.
Your practical XGRIDS reference: from first setup to detailed scanner operation, desktop processing, and advanced capture workflows.
Welcome to Your XGRIDS Guide
Get started with your XGRIDS scanner and build a dependable workflow—from preparing your equipment and capturing a project to processing, checking, and sharing the results. Begin with a small project, then explore the detailed and advanced workflows as you need them.
Start with the shared foundation, then follow the instructions for your scanner and the desktop software you use.
Use the step-by-step procedures, best practices, and quick-reference checklists at your own pace. Keep this guide handy when preparing for a job or checking a setting.
Part 1 — Shared Foundation
1. Understand Your System
What the Scanner Records
Your scanner collects information about the surrounding space. Depending on the device and processing workflow, that information can support point clouds, meshes, and photorealistic 3D Gaussian Splatting models.
Good results depend on suitable equipment, complete coverage, controlled movement, and appropriate processing.
Essential Terms
| Term | Meaning |
|---|---|
| LiDAR | A sensor that measures distances using laser light |
| SLAM | A process that tracks movement while building a map |
| Point cloud | Measured points representing surfaces in three dimensions |
| Mesh | A surface model made from connected polygons |
| 3DGS | A method for creating photorealistic scenes viewed from different positions |
| Loop closure | Revisiting a captured area so the system can recognize it and improve alignment |
| Map fusion | Combining separate captures using a supported workflow |
| Deliverable | The finished file, drawing, model, or viewing experience |
| GNSS | Satellite positioning, including systems such as GPS |
| RTK | Real-time kinematic positioning, which uses correction data during capture |
| PPK | Post-processed kinematic positioning, which calculates corrections after capture |
| GCP | Ground control point: a known reference position used to relate data to a coordinate system |
| POI | Point of interest: a marked location in a capture, which can help identify an area for local enhancement |
| ICP | Iterative closest point: an alignment method for point clouds that are already roughly aligned |
| RMSE | Root mean square error: an error statistic whose meaning depends on the calculation and reference data |
| GPU / VRAM | Graphics processor and its memory, used heavily during photorealistic reconstruction |
Know Which Software You Need
| Application | Main role |
|---|---|
| LixelGO | Field operation for supported K and L series scanners |
| LCC Scan | PortalCam connection and field operation |
| LixelStudio | Supported scanner processing and point-cloud work |
| LCC Studio | Photorealistic reconstruction |
| LCC Model Editor | Model cleanup and refinement |
| LCC Scene Editor | Scene organization, viewpoints, annotations, and presentation |
Use the guide for your exact model. Functions and connection methods vary.
2. Choose the Result Before Capture
Define what you or your client need from the project:
- Point-cloud documentation.
- Measurements or drawings.
- Photorealistic viewing.
- An interactive tour.
- More than one output.
For measurement work, define the required accuracy and checking method before scanning. For visual work, identify the views and details that must look clear.
Keep Three Checks Separate
Coverage: Did you capture the required surfaces?
Visual quality: Is the result clear and useful to view?
Measurement quality: Has the result been checked appropriately for its intended use?
A dense cloud or convincing model does not, by itself, establish accuracy.
3. Prepare Equipment and Software
Before the First Project
- Identify the scanner and accessories.
- Charge batteries and the field phone.
- Check storage and inspect the equipment.
- Install the correct official app.
- Sign in and complete required activation.
- Test the scanner connection.
- Install and open the desktop software.
- Confirm access to the features needed for the project.
Check actual package contents against the supplied packing list. Accessory bundles can differ.
Test the Whole Workflow Once
Before relying on the equipment for a client job, complete a small test capture and confirm that you can transfer, process, and open the result.
Connection Methods
Follow the instructions for the scanner, phone, and firmware combination.
Do not assume that every LixelGO connection requires a phone hotspot. XGRIDS documents different connection methods, including Quick Connect and Direct Connect for the K1.
Official connection guidance ↗
Activation and Versions
Keep a record of the scanner firmware, mobile app, and desktop software versions.
For LixelStudio, basic functions are available without activation; additional core features become available through activation. Complete this before the job.
Computer Preparation
Check the requirements for each application separately.
If you plan to use both desktop workflows, target at least 64 GB RAM for your workstation. Larger projects may need more.
XGRIDS’ LCC Studio documentation gives memory-capacity guidance based on capture duration. These are planning references, not guarantees for every scene.
Official LCC Studio hardware guidance ↗
Requirement discrepancy: XGRIDS’ LixelStudio download page lists 32 GB RAM as basic, while its installation manual lists 64 GB minimum. Confirm the requirement for the release and workload being used.
4. Plan the Capture
Walk the Site First
Identify:
- Required rooms, floors, objects, and exterior areas.
- Access restrictions.
- Starting and finishing locations.
- Connecting corridors and stairs.
- Lighting changes.
- Glass, mirrors, moving objects, and obstructions.
- Surfaces hidden behind equipment or furniture.
For a tour, list the locations visitors should see clearly. Capture those areas from useful viewing positions.
Prepare the Space
Open required passages where permitted, turn on suitable fixed lighting, and keep curtains and other scene elements consistent.
Coordinate with the site contact before moving objects or adjusting the space.
Plan a Connected Route
Use a clear main route with deliberate coverage of adjoining areas. Include recognizable return connections where appropriate.
Do not create separate captures simply because you enter another room. If multiple sessions are necessary, plan their connection method before recording.
Start Small
Choose a manageable, well-lit space with clear features for the first project. For your first project, choose a straightforward space before progressing to tunnels, repetitive warehouses, or complex industrial sites.
5. Capture Good Data
Initialize Correctly
Place the scanner as directed in its model guide. Keep it stationary when required, and wait for the completion prompt before moving.
Use the device’s confirmation rather than adding an assumed waiting period to every model.
Move Smoothly
Keep the cameras and sensors unobstructed. Avoid abrupt swings, rapid turns, and sudden height changes.
Slow down near surfaces, through doorways, around corners, and in difficult lighting.
For 3DGS capture, XGRIDS recommends general movement no faster than 1 m/s, PortalCam no faster than 0.5 m/s, and approximately 0.3 m/s in the listed difficult conditions.
Change viewing position as you move. Rotating in place does not replace multi-angle coverage.
Make Useful Return Connections
Revisit a captured location from a similar viewing direction. Returning to the same floor position while facing elsewhere may not provide the intended match.
Official movement and loop-closure guidance ↗
Indoor Photorealistic Coverage
XGRIDS describes three coverage stages:
- Move around the perimeter while observing across the room.
- Add crossing routes through the central area.
- Supplement missing floor and ceiling views.
Stay within your scanner’s handling limits. Use additional passes to reveal missing surfaces rather than repeating an identical viewpoint.
Official indoor capture guide ↗
Handle Transitions Deliberately
Approach doorways and corners slowly. Maintain surrounding features through the transition.
On stairs, prioritize safe footing and capture landings carefully. Avoid sudden movements intended to capture an extra angle.
Monitor and Respond
Watch available previews, coverage tools, battery status, storage, and warnings.
If something looks wrong, identify the cause while still on site. Do not assume desktop processing will resolve it.
6. Finish, Review, and Protect the Capture
Finish Properly
Use the supported stop control and wait for saving to complete before powering down or changing batteries.
Review Before Leaving
Compare the capture with the required-area list.
Inspect available previews from multiple directions for missing rooms, sparse surfaces, doubled geometry, and broken connections.
A field preview helps identify problems; it does not replace final inspection.
Transfer Complete Projects
Copy the entire original project using the supported transfer method. Preserve its internal files and folders.
Keep separate locations for:
- Original captures.
- Working projects.
- Processing results.
- Final deliverables.
Verify the copy and retain a backup before clearing device storage.
Keep a Short Project Record
Record the scanner, versions, date, areas captured, processing settings, and unusual site conditions.
Part 2 — Scanner Modules
1. PortalCam
Workflow: PortalCam → LCC Scan → LCC Studio → optional editing and presentation.
Getting Started
- Charge and inspect the equipment.
- Enable the phone connections and permissions requested by LCC Scan.
- Connect and activate.
- Choose the capture mode.
- Follow initialization prompts.
- Capture, stop, save, review, and transfer.
Mode Selection
| Mode | Setting |
|---|---|
| NIGHT | Dim ambient lighting |
| INDOOR | Typical indoor lighting |
| NATURE | Outdoor natural lighting |
| PORTRAIT | Reconstruction of a person |
The manual recommends NIGHT for a route that moves from bright areas into a dim corridor and back.
Use the documented press-and-hold app controls for starting and stopping. Check physical-button controls against your installed firmware.
Official PortalCam app guide ↗
Best-practice focus: Slow movement, varied viewpoints, consistent lighting, and deliberate floor and ceiling coverage.
2. Lixel K1 (Discontinued)
Discontinued model: These instructions are retained for customers who already own a K1.
Getting Started
- Prepare batteries, storage, and accessories.
- Connect through the supported LixelGO method.
- Confirm device time.
- Select the actual mounting arrangement.
- Complete initialization.
- Follow a connected route.
- Stop, review, and transfer the complete project.
Check compatibility before choosing desktop processing software.
Best-practice focus: Stable startup, clear sensor views, route continuity, and complete original-data retention.
3. Lixel K2
Getting Started
Select the available mode for the information you need to monitor. Guided and RGB modes provide different display functions.
Remain stationary during the documented initialization countdown and wait for completion.
Where available, use QUAL or Scan Assist to check density and missed areas. These tools do not establish accuracy or finished LCC quality.
After stopping, fast-flashing green indicates saving; wait for solid green.
The directly generated real-time cloud is downsampled. Preserve the full project for LixelStudio processing when the complete point cloud is needed.
Best-practice focus: Choose the monitoring mode deliberately, inspect coverage, and distinguish preview data from processed output.
4. Lixel L2 Pro
Getting Started
- Prepare the device and correct accessories.
- Connect with LixelGO.
- Confirm time, mounting, and required positioning settings.
- Keep the scanner still until initialization completes.
- Capture the planned route.
- Stop and wait for solid green.
- Review available model information.
- Transfer the complete project through the supported USB workflow.
Historical viewing depends on compatible firmware and app versions.
Best-practice focus: Consistent transitions, correct accessory configuration, and version compatibility.
5. Lixel L3
Getting Started
Start with the scanner and base mount on stable, level ground.
Start capture, keep the device still through initialization, then lift and detach the base mount as instructed.
Use the monitoring functions available in the selected mode. Density displays identify sparse coverage rather than proving accuracy.
After stopping, allow both saving and preview generation to finish. Inspect the result on the supported display before leaving.
Best-practice focus: Correct base-mount startup, useful coverage checks, and careful handling.
Part 3 — Desktop Software
1. LixelStudio
Process the Original Capture
Select the complete scanner project directory. Distinguish raw processing from importing an already exported cloud.
Choose Suitable Settings
- Standard: general scenes.
- Robust: greater processing stability.
- Narrow Space: tight, structurally constrained environments.
- Carry method: how the device was actually carried.
Stronger filtering can remove useful structure. Enhancement increases density at a processing cost.
For High-Precision Optimization and Coordinate Transformation, check the available options in your installed build and the current processing instructions.
Inspect Before Editing
Review top, side, and interior views. Use sections to reveal layered surfaces and alignment problems.
Keep an original processed version before cropping or cleanup. Understand that orientation tools can change coordinates.
Official inspection and editing tools ↗
Export for the Recipient
Confirm format, units, coordinates, required attributes, and receiving application.
Check whether the recipient needs only points or additional imagery and project information. Reopen the exported result before delivery.
2. LCC Studio
Prepare Storage
Set project and backup locations before importing. Use supported local storage and sufficient working space.
XGRIDS recommends SSD storage and does not support the documented direct import from OneDrive or NAS.
Check Before Reconstruction
- Confirm the capture and device.
- Choose the reconstruction type.
- Review the trajectory and coarse cloud using Point Cloud Preview.
- Confirm quality settings and available resources.
- Start reconstruction.
Start with Single Model for a single capture project.
Run and Recover
Avoid competing tasks that consume graphics memory. Keep LCC Studio open during reconstruction.
XGRIDS recommends reserving at least twice the capture size in its data-storage directory.
If generation is interrupted, inspect the model card for Continue Generation or Restart Generation. A processing failure does not automatically mean the original capture is lost.
Official reconstruction guide ↗
Review Before Presentation
Inspect important surfaces, connecting areas, and planned viewing positions. Decide whether the issue needs editing, different processing, or additional capture.
3. LCC Model Editor
Begin with a Specific Editing Goal
Examples include removing surrounding content, isolating an object, or adjusting appearance.
- Preserve an original version.
- Understand Open versus Import.
- Refine selections carefully.
- Inspect the selection from several directions.
- Check the selected assets and destination before exporting.
- Reopen the saved output.
Do not scale or reposition spatial data casually.
4. LCC Scene Editor
Make the Scene Easy to Explore
Save a project early. Set an understandable starting position and add a small number of clearly named viewpoints.
Use annotations to explain useful locations or equipment.
Learn the Navigation Controls
Familiarize yourself with roaming, pivot, and avatar modes. Adjust the camera speed and practice returning to the starting position before building your scene.
Preview measurements are temporary and are not saved.
Choose the Right Output
| Action | Purpose |
|---|---|
| Save | Preserve the editing state |
| Export | Create model files |
| Export Project | Package the scene for continued editing or backup |
| Publish | Create an online viewing link |
An exported model file should not be assumed to contain the full editable scene.
Official Scene Editor file guidance ↗
For published work, choose the appropriate access method and test the link as a recipient would. Password-free sharing allows anyone with the link to view.
Part 4 — Everyday Reference
1. Troubleshooting
Identify the stage first:
| Stage | Initial checks |
|---|---|
| Connection | Correct app, permissions, connection method, device discovery |
| Startup | Activation, battery, storage, initialization prompts |
| Capture | Route, movement, coverage, obstructions, warnings |
| Transfer | Complete project, cable, saved state, destination |
| Processing | Compatibility, resources, settings, exact error |
| Viewing | Navigation mode, speed, visibility controls |
| Delivery | Format, included files, access, receiving application |
Change one relevant factor at a time. Keep the original capture.
For support, collect the model, serial number, versions, phone or computer details, exact message, and relevant logs.
2. Your First Project
Use a small connected interior:
- Define the output.
- Prepare equipment and software.
- Walk the site and plan the route.
- Connect and initialize.
- Capture rooms and transitions.
- Stop and review.
- Transfer and back up.
- Process and inspect.
- Edit only what is necessary.
- Export or publish and test the result.
3. Final Checklist
4. Choose Your Next Step
Continue to Part 5 for detailed scanner procedures and Part 6 for desktop instructions. Parts 7–8 cover coordinates, large sites, fusion, enhancement, quality checks, floor plans, and delivery.
Read the shared foundation first, then use the navigation or search to find the procedure you need. Advanced workflow limits are tied to the named model and documentation version.
Part 5 — Detailed Scanner Procedures
1. PortalCam — From Power-On to Transfer
Prepare and Start
- Fit the charged battery in the indicated orientation and confirm that it is fully latched. A visible red latch indicator means it needs attention.
- Put the device on a stable, level surface. Keep its cameras and sensors clear.
- Hold the battery power control for about two seconds to bring the system into standby. The battery control and device control are different buttons.
- Connect through LCC Scan and complete activation if requested. Confirm the device identity, available storage, and recording status.
- Double-press the device control to begin capture. Keep the device stationary through initialization and follow the app and indicator prompts before moving.
- Capture the main route first, then give important objects and viewing areas additional coverage. Keep motion smooth and maintain useful views of nearby structure.
Use status, not a stopwatch: Startup and recording preparation take time. A slow green indicator during preparation is different from a ready or completed-save indication. Confirm the actual app state before lifting the unit.
Stop, Save, and Copy
- Finish in a recognizable area connected to the route. Double-press the device control to stop.
- Let saving finish. Do not disconnect power while the green indicator is flashing; wait for the completed-save state.
- With the scanner in standby, connect the supplied USB 3 cable to the computer. Desktop connection can enter USB mode automatically; manual entry uses a single press, a white indication, then another single press within the indicated window.
- Copy the entire capture project into a named raw-data folder. Keep its images, logs, metadata, and capture files together.
- Confirm that the copy is complete and make a second copy before clearing scanner storage. Exit USB mode before starting another capture.
PortalCam controls, USB and firmware ↗
Battery and Firmware Care
Charge with the specified charger and cable in the documented temperature range. XGRIDS specifies 5–30°C for charging in this manual. Recharge after use, attend promptly to depleted batteries, and recharge stored batteries at least every three months.
Before a firmware update, back up captures, confirm the correct PortalCam package, and have more than 50% battery. Use the app update path where available. For the full-package method, follow the official root-directory and restart instructions exactly; do not interrupt installation.
2. Lixel K1 — Field Procedure (Discontinued)
Discontinued model: This procedure is provided as a reference for existing K1 owners.
Assemble and Connect
- Inspect the battery connection and fit the battery handle using the documented buckle arrangement. Secure the base to the threaded connection.
- Hold power for approximately four seconds. Place the scanner level and stable while it starts.
- Open LixelGO and select the documented connection method for your phone and firmware. Use Quick Connect when supported; follow the exact Wi-Fi prompts rather than assuming every phone needs the same hotspot setup.
- Confirm the serial number, battery, storage, and activation. Open the capture screen before recording.
K1 connection and activation ↗
Record and Finish
Double-press to start, then hold the unit stationary until initialization is complete. Lift and walk smoothly, preserving nearby structure in the sensor view. Deliberately cover transitions and return connections; quick spins and repeated isolated views make an unreliable route.
Double-press to stop. Let the saving indication finish before handling power or removing the battery. For USB transfer, use the documented standby/USB sequence, copy the complete project from the device, and retain the untouched original.
K1 processing choice: Use LixelStudio for supported point-cloud processing and LCC Studio for supported photorealistic reconstruction. Check the software’s device support before selecting fusion or other advanced features. Point-cloud enhancement options also differ from K2 and L-series options.
3. Lixel K2 — Field Procedure
Connect with LixelGO
- Fit the battery and secure the base locking connection. Hold power for about four seconds and place the scanner level.
- In LixelGO, tap Quick Connect, select the intended scanner, and follow the phone’s Wi-Fi prompts. Check that the connected model and serial number match your unit.
- Review firmware, storage, and activation, then select GO to enter the working interface.
- If using hotspot configuration instead, enter the phone’s hotspot details through the documented device setup and confirm both the network and data connection. On iPhone, follow XGRIDS’ hotspot naming and compatibility instructions and stay on the hotspot settings screen until connection succeeds.
Connection recovery: Verify permissions and the selected network first. Bridge and hotspot workflows have their own setup steps; switching methods halfway through without reconfiguring can create confusion.
K2 activation and connection ↗
Initialize, Capture, and Review
Double-press the device control to start recording, or use the supported app action, and remain still through initialization. The manual describes approximately 15 seconds; use the completion prompt as the decision to move. Carry at chest level with the front camera directed toward the intended scene.
Choose Guided or RGB viewing as appropriate. Use the live display to find missing coverage, but treat QUAL as a density aid rather than proof of positional accuracy or final 3DGS quality.
When finished, stop and wait through the fast green saving indication until the ready state returns. Inspect the preview for missing rooms and connections before leaving.
Copy the complete project, including supporting files. The real-time map.las is a reduced field result; process the original project for the full result rather than delivering that preview by default.
Detail Passes for Visual Models
Capture the connected overall space before concentrating on fine detail. For the K2 detail workflow, XGRIDS recommends slower motion near important surfaces, including about 0.5 m/s or less for detail and a 0.5–1 m working distance where practical. Keep the front camera aimed at the subject and vary height deliberately to cover its visible surfaces.
These are K2 route recommendations, not universal working distances for every scanner or environment. Keep a safe route and avoid blocking the sensors with your body.
4. Lixel L2 Pro — Field Procedure
Assemble, Start, and Record
- Open the battery locking lever, seat the battery along its guide, and lock it securely.
- Start the device with the documented power hold. Keep it level on its base during startup.
- Connect using LixelGO, confirm the intended device, and finish activation and project preparation.
- Double-press to begin recording and wait for the initialization-complete prompt before moving. Check the capture mode shown by your firmware.
- Follow a connected route with deliberate overlap, including doorways, stair landings, and exterior/interior transitions.
- Stop recording, confirm the end action if prompted, and wait for saving to finish. Review coverage before dismantling the equipment.
- In standby, enter USB mode using the documented single-press/white-indicator/single-press sequence if required. Copy the complete model project folder.
Measurement Points Need Their Own Checks
The L2 Pro Measure Point workflow has specific firmware and RTK requirements. Where those requirements are met, XGRIDS describes establishing a Fixed solution and an outdoor L-shaped initialization route before entering an area without GNSS.
For that workflow, use the optimized measure_points_latest.csv when available rather than assuming that the real-time measure_points.csv is the final result. The distance traveled since GNSS was lost matters; it is not simply the straight-line depth of a room.
Use the exact initialization and outage limits in the official procedure. Establish independent checks for the required deliverable instead of treating an RTK connection as a general accuracy guarantee.
5. Lixel L3 — Screen and App Procedure
Startup and Capture
- Fit and lock the battery, check the base connection, and keep ventilation clear.
- Hold power for about four seconds. On first connection, use LixelGO Quick Connect, enter GO, and confirm the device-binding prompt on the L3 screen.
- Check Settings → Time Calibration. Use the correct local setting or automatic network time; inspect the result if a VPN affects the detected time zone.
- Place the device level on its base. Start with the documented screen long-press or supported device control and remain stationary until initialization finishes.
- Lift slowly after the completion cue. Use Guided/RGB and Scan Assist to monitor coverage while following the planned route.
- Stop with the screen control or supported button method. Wait through saving, then review the generated preview and recorded projects.
Density is one check: QUAL and Scan Assist help assess coverage and density. They do not independently validate accuracy or promise the finished photorealistic result.
L3 activation and time calibration ↗
Transfer and Updates
Connect the computer while the unit is in standby and confirm USB mode on screen. Copy the whole project, verify the copy, and leave USB mode before scanning again.
Use Settings/Wi-Fi for the supported online update process. If using an offline package, place the correct package in the documented root location and follow the screen prompts after leaving USB mode. Keep power stable throughout.
The documented IP54 rating does not justify immersion or unrestricted wet-weather use. Keep vents free and clean with a dry cloth as instructed. Use the battery hub’s storage function when putting batteries away for an extended period.
Part 6 — Detailed Desktop Workflows
1. LixelStudio — Process a Point-Cloud Project
LixelStudio 4.1.1.0 — Updates and Official Instructions
The official wiki identifies v4.1.1.0 as the October 15, 2026 release. Use the links below for the current manufacturer guidance and check that it matches your installed software.
| Update | Where to find the details |
|---|---|
| Lixel L3 Project Processing and Map Fusion | Processing and fusion ↗ |
| Local enhancement near captured GCPs or POIs | Basic Parameters and Region Selection ↗ |
| Fusion using manually selected overlapping trajectories | Connection status and manual configuration ↗ |
| Ground-point extraction and automatic stockpile boundaries | Volume Calculation ↗ |
| 3D vector drawing and DXF with 3D information | Software overview: 3D Drawing ↗ |
| Outdoor High-Precision Optimization | High-Precision Optimization settings ↗ |
| Panorama, filtering, texture and mesh output | Coloring and Mesh ↗ |
The v4.1.1.0 release notes also report stronger L3 mapping in difficult scenes, lighter mesh textures, improved panorama seams and right-angle filtering, and improved fusion overlaps with mesh generation. Inspect your own results after processing; these improvements do not replace coverage and accuracy checks.
3D Drawing: The wiki overview lists this feature, but does not yet provide a dedicated 3D Drawing procedure in its LixelStudio chapter navigation. The 2D Drawing guide is a separate workflow.
Official software version details ↗
Official LixelStudio downloads and release information ↗
Import the Actual Capture Project
- Work from a verified local copy. Keep a separate untouched raw-data backup.
- Open Project Processing and select the complete project directory copied from the scanner.
- Inspect the preview trajectory in top, front, and side views. Restrict the processing time range only when you intentionally need a subset.
- Select the scene mode and actual carry method. Standard is the general starting point; Robust, Narrow Space, Vehicle, and UAV are specific choices rather than a universal quality ranking.
- Choose an output location and record the settings used. Run the first representative project with a restrained baseline before enabling every enhancement.
Choose Parameters for the Result
Dynamic Object Removal helps with moving people and vehicles. Stronger filtering can also erase thin structures, so check rails, cables, and edges before accepting it. Point Cloud Enhancement increases density and processing demand; it cannot supply surfaces you never captured.
High-Precision Optimization can be used for outdoor projects in v4.1.1.0. Check available options in your installed build when combining processing and coordinate settings.
For color or image deliverables, review visual-pose optimization, low-light image optimization, panorama output, and privacy options. Enable panorama output if you will need structured E57 conversion later.
Enhance Only the Areas You Need
If your capture includes GCPs or POIs (points of interest), open Basic Parameters → Region Selection. Select the required locations, preview them, and set the local enhancement range. Use Reset to return to whole-cloud enhancement. Check fine detail against the baseline result before retaining the change.
Official local enhancement instructions ↗
Inspect Before Export
Open the processed result and examine room connections, loop returns, stairs, thin objects, and cross-sections through walls. Confirm that the chosen time range and output contain the full requested project. Reprocess a comparison when a changed setting has a clear purpose; keep a note of what improved and what was lost.
LixelStudio project processing and parameters ↗
Compatibility Comes Before Reprocessing
Older captures may need an earlier LixelStudio release. The LixelStudio v4.1.1.0 manual specifies firmware 3.0.2 or later for its current workflow and provides a compatibility table for older firmware. Check that table when an old project fails to load; do not modify or discard its supporting files to make it look like a new project.
2. LixelStudio — Clean, Convert, and Deliver
Work on a Copy
Import the processed cloud and identify the data selected in the list before using a tool. Crop unnecessary surroundings with a clipping box or polygon and inspect from several directions. Save a new result so the complete processed cloud remains available.
Use resampling for a lighter deliverable when appropriate. Denoising and smoothing alter the data; compare important edges and details before retaining those changes. Manual Registration uses corresponding features; ICP refines clouds already approximately aligned. A low registration error does not establish project-wide accuracy.
Choose the Export Path
| Required result | Procedure and dependency |
|---|---|
| LAS / LAZ / PLY | Select the cloud, use File → Export, name the output, and reopen it |
| Unstructured E57 | Use the normal point-cloud export; do not promise scan positions or panoramas |
| Structured E57 | Use LAS to E57 with a colorized cloud that already has panorama output and the required pose file |
| RCP | Use LAS to RCP and deliver both the RCP index and its associated data folder |
For georeferenced structured E57, the manual specifies pose_no_offset.csv. Check that the pose file matches the processed project and its coordinate setup.
Point-cloud tools and conversion ↗
Coordinate Display Is Different from Data Transformation
A LAS render offset improves display with large coordinates; it does not rewrite the point-cloud coordinates. Record the actual coordinate reference information with the deliverable. Avoid rotating, scaling, or translating a georeferenced result merely to make the screen view more convenient.
The data-list Delete action can delete project files. Keep the raw backup separate and read the confirmation before proceeding.
3. LCC Studio — Build a Photorealistic Model
Prepare a Reconstruction
- Install the appropriate release, sign in, and check the required license features and supported GPU before a production job.
- Copy complete capture data to a local SSD. Keep active inputs and outputs outside live synchronization folders such as OneDrive and outside network shares.
- Create a new reconstruction from the correct data source. Confirm the detected device, source path, project name, and separate output location.
- Preview the project and choose quality and applicable options deliberately. Estimate disk and memory needs before committing a large dataset.
- Start reconstruction and leave adequate system resources available. Avoid competing GPU-heavy work and interruption during processing.
LCC Studio hardware requirements ↗
Inspect the Result and Resolve Failures
Review the model along the intended visitor path and in difficult transitions. Look for duplicate walls, separated floors, blurry signs, floating fragments, and gaps. A successful processing message means the task completed; it does not confirm that every requirement is met.
For PortalCam data, Layering Optimization is enabled by default in the documented software version. It can improve loop alignment but can also confuse repeated layouts. If structural distortion appears in repetitive rooms or floors, compare a reconstruction with that option disabled.
If processing was interrupted, use the offered continuation/restart option appropriate to the saved task state. Keep the original input intact and capture the exact failure message before changing parameters.
Coordinate check: With invalid RTK, LCC Studio can still create a model while skipping absolute-coordinate conversion. Inspect the coordinate result independently before describing the output as georeferenced.
4. LCC Model Editor — Clean and Refine
Select Carefully Before Removing Content
- Open the model and save a working version. Use Import rather than Open when the intention is to add another model to the current scene.
- Choose the selector that suits the job. The 3D box encloses a volume; rectangle and lasso tools project through the view and can include material behind the visible surface.
- Set the depth limit for projection selection and rotate to check what is selected. Add is the default selection mode; hold Ctrl to subtract and use Ctrl + I to invert.
- Delete only after inspecting the highlighted region. Use Undo immediately if the wrong material disappears. Process large edits in smaller regions when hardware limits appear.
Model Editor selectors and depth ↗
Separate, Clone, and Grade
Use Clone to compare an edit on a copy; Separate extracts a selection as another model. Move, Rotate, Scale, and Align alter spatial relationships, so preserve an unmodified version for measurement or coordinate-dependent delivery.
For color correction, select the whole model or the intended local region, open Color Grading, and make restrained changes. Whole-model and local grading can accumulate; check the combined result. Removing a region from a graded selection resets that removed region’s local grading as documented.
Save and Verify the Intended Scope
Save to the required clean output folder and keep original reconstruction data. Check which assets or regions are selected before exporting: an export may contain only the selected model or merged selected models rather than the complete scene. Reopen the output and check coverage, orientation, and appearance.
5. LCC Scene Editor — Turn a Model into a Client Experience
Create a Saved Scene
Open the model, then save an editable project before building a presentation. Save an editable project so your scene setup is retained between sessions. Keep the project assets together and use Export Project when handing over the editable scene, rather than assuming a model export contains annotations and viewpoints.
Scene Editor file operations ↗
Build Useful Viewpoints
- Move to a clear arrival position with a useful view of the scene.
- Open Viewpoints → Tour, select Add Point, and give the view a client-friendly name.
- Repeat for important rooms or assets. Check the actual view after jumping to each point.
- For a Roaming route, add camera positions in a sensible order and preview the movement. Avoid paths through walls and abrupt transitions.
- Where automatic routes were generated from supported field markers, review and refine them. K1 and L2 Pro do not support that automatic-marker feature in the linked documentation.
Explain What the Client Is Seeing
Use Annotations to place a point on a surface, choose the type, and add a concise title, description, or relevant media/link. Confirm that it points to the correct asset. Annotation creation and visibility are separate controls; use the asset-list visibility icons when hiding individual annotations.
Save the scene and preview it as a visitor. Check the opening view, navigation speed, viewpoint names, annotation media, and any cross-scene links before publishing.
Publishing, model export, and editable project handover are separate deliverables. Select the intended sharing mode and test the published link using the same access method as your recipient. Password-free sharing allows anyone with the link to view; editing a local project does not itself confirm the hosted presentation has updated.
Part 7 — Advanced Capture and Coordinates
1. Plan a Large Site and Multiple Floors
Divide by Connections, Not Just Room Count
Start with the required outputs and identify manageable capture segments. Draw a simple connection diagram: every segment must connect to another segment by the method supported by the chosen software. Record segment names, intended overlap areas, shared point names, and the order of capture.
Use well-lit, distinctive areas for joins. Keep scene arrangements and lighting consistent. A feature-poor corridor, mirror, staircase, or moving crowd is a poor location for the only connection between two large blocks.
For multi-floor work, give landings and floor transitions deliberate coverage and check floor identity in the preview. Repeated floor plans deserve special scrutiny during reconstruction. Keep a floor/segment log so a convincing repeated layout cannot hide a missing level.
Apply the Correct Overlap Rule
| Workflow | XGRIDS requirements |
|---|---|
| LixelStudio point-cloud fusion | At least 15 m overlap; 15–30 m recommended, with mutually visible overlapping paths |
| LCC large-scale capture guide | About 15 m preferred; that guide states a 10 m minimum |
Use the stricter requirement for the workflow you intend to run and plan enough usable overlap to avoid relying on the boundary minimum. These distances are travel-path overlap, not a generic percentage of room floor area.
For large K2 visual capture, the large-scale guide also calls for a trajectory overlap at least every 500 m, or RTK/relative control-point support when that cannot be achieved.
2. Ground Control — Use the Right Type
Survey Control and Visual Fusion Points Have Different Jobs
Survey control relates a point cloud to known coordinates and may support optimization. PortalCam fusion points help connect visual capture segments. Do not use the PortalCam placement tolerance as a surveying tolerance.
For survey-controlled work, agree on the horizontal reference system, units, vertical datum/height type, and checking method before capture. Keep independent checkpoints out of the fitted control set so they can test the result.
| Scanner workflow | Minimum and spacing in the linked manual |
|---|---|
| K2 survey control | At least 3 non-collinear, distributed control points; spacing no more than 50 m |
| L2 Pro survey control | At least 3 non-collinear, distributed control points; spacing no more than 100 m |
| L3 survey control | At least 3 non-collinear, distributed control points; spacing no more than 100 m |
The minimum is not a complete project design. Choose additional control and independent checks to suit geometry, extent, and required accuracy.
Field Naming and Desktop Matching
Create an unambiguous point list. At each point, use the scanner’s documented physical reference and capture action; verify the saved point and its name. Match the names exactly to the reference coordinate file, inspect the matches in the desktop editor, and check delimiter and coordinate-column order before processing.
L3 supports documented ground-tip and wall workflows as well as pole settings. Use the exact procedure for the installed accessory; follow the L3 accessory instructions for wall or pole observations.
3. RTK and PPK — From Field Status to Checked Coordinates
RTK Field Sequence
- Confirm supported GNSS hardware, antenna/accessory setup, corrections access, and the required coordinate systems before going to site.
- Configure the documented correction-service settings. Protect service credentials and confirm that corrections are actually arriving.
- Initialize outdoors with good sky visibility and wait for Fixed before starting the supported absolute-coordinate procedure. Float, Single, or None is not equivalent.
- Follow the model’s posture, initialization route, and GNSS-outage guidance. Track status through the capture rather than checking it only once.
- Retain the GNSS records and field notes with the complete raw project. Check the resulting coordinates against independent observations.
For K2, the linked manual distinguishes not connected, connected but not fixed, and Fixed status. Its continuous GNSS-loss guidance is shorter than L3’s: under 50 m versus under 100 m respectively. Use the model-specific procedure, not a site-wide generic RTK rule.
PPK Preparation and Processing
PPK requires suitable field logging and compatible base/reference observations; it cannot be added afterward to a capture that lacks the necessary data. Confirm the scanner’s supported PPK mode before recording.
In LixelStudio’s documented PPK workflow, open Coordinate Transformation, select PPK Settings for the supported project, load the required observation and navigation files, review the base station coordinates and satellite systems, then calculate. The documented software version requires RINEX 3.0 or later.
Incorrect base coordinates can bias the result even if the calculation completes. Record the reference source and processing settings, review the solution quality, and verify checkpoints.
Height and Coordinate Handover
Ellipsoidal height is different from a project’s orthometric elevation. Confirm the required geoid or height correction and avoid applying it twice. If combining GCP and GNSS, ensure their target systems agree. Record units, projection/zone, datum, vertical reference, and any transformation used in the handover notes.
4. PortalCam Fusion and Enhancement Points
Mark the Intended Operation in the Field
PortalCam uses different point types for map fusion, aerial-ground fusion, and HD Enhancement. Choose the correct type in LCC Scan when adding a point; a generic point name does not replace that setting.
Place the device stably on its opened tripod in an unobstructed, well-lit area with useful texture. Use Add Control Point, select the type, and name it consistently. Capture the surroundings with full directional coverage. Do not power off within five seconds of adding a point.
Map-Fusion Layout
The PortalCam capture guide specifies at least three shared fusion points in an L-shaped arrangement, spaced at least 10 m apart. Across maps, use exactly matching names and repeat the documented approximate position, orientation, and height. The guide describes less than 0.5 m position difference, ±20° direction difference, and about 10 cm height difference; these are visual-fusion placement tolerances.
For aerial-ground work, mark the takeoff location with the correct point type and align the device orientation with the drone camera direction. For HD Enhancement, place the point toward the enhancement subject and begin the associated image sequence as the official procedure specifies.
Part 8 — Advanced Processing and Deliverables
1. Fuse Point Clouds in LixelStudio
LixelStudio v4.1.1.0 supports L3 Project Processing and Map Fusion. This is separate from the LCC Studio photorealistic fusion workflow.
Build and Inspect the Connection Network
- Open Map Fusion and Add Map for each complete capture directory.
- Check each map’s mode, connection data, and overlap. Keep to supported data from the same device type.
- Select the base map or allow automatic selection, then set output and required processing options.
- Review automatically recognized shared points. Confirm that repeated names refer to the same physical connection; correct accidental matches.
- If using manual connection configuration, roughly align the relevant maps and select one valid pair of mutually visible overlapping trajectory sections for each connection.
- Process, then inspect seams, transitions, repeated structures, and independent checks before accepting the merged cloud.
LixelStudio v4.1.1.0 allows up to ten maps per fusion and requires each capture to be under twenty minutes. Coordinate transformation additionally needs a connected network with at least three non-collinear absolute control points across the maps. Check release support before applying these limits to another version.
A merged file is not a validated alignment: Look at sections through the join and inspect areas away from the connection. Preserve the component projects and settings so a suspect segment can be reprocessed.
When no RTK or shared connection points are available, use Connection status → Configure and select suitable overlapping trajectories. This aligns the maps; it does not establish surveyed absolute coordinates. For a textured mesh, review Generate Mesh and its output settings before processing.
2. Fuse Visual Models in LCC Studio
Ground Map Fusion
Choose Map Fusion and add the complete capture segments. Confirm the detected device type, connection plan, model name, and reconstruction settings before running. Inspect each join in the completed model and compare the result against the capture log.
LCC Studio v2.6.0 supports up to ten ground segments with a combined duration no greater than 200 minutes. It requires the same device model; L2 Pro 16- and 32-channel captures cannot be mixed. L3 is not supported for this fusion workflow in v2.6.0. Do not assume that basic reconstruction support means fusion support.
LCC Studio map fusion and device limits ↗
Aerial-Ground Fusion
Plan complementary aerial and ground coverage, including the supported connection/control method, before recording. In Aerial-Ground Fusion, add the ground data and the drone-image directory, then review the device detection and drone RTK toggle.
For LCC Studio v2.6.0, prepare more than 100 and fewer than 10,000 JPG/JPEG images, a common image resolution greater than 1024 × 768, and compatible ground data. L3 is not supported for aerial-ground fusion in v2.6.0. For PortalCam, retain the takeoff/landing images and the associated aerial-ground point data together as instructed.
XGRIDS recommends supported L-series ground RTK with drone RTK. PortalCam can use the documented aerial-ground control-point method with an appropriate non-RTK drone workflow. These are different alignment methods; do not combine them casually.
After processing, check roof-to-façade continuity, ground transitions, duplicate surfaces, and coordinate validity if required.
3. HD Enhancement — Make Important Details Clearer
Capture a Useful Image Sequence
Use HD Enhancement for selected signs, exhibits, logos, and panels that need stronger texture detail. It is a visual refinement step; it does not certify improved measurement accuracy.
Keep one focal length and image resolution throughout a sequence. Do not mix lenses or crop/rescale individual images. Take sharp, well-exposed images with at least 80% adjacent overlap and include views close to the original scanner camera’s position and orientation. Aim for at least twenty continuous images of each area rather than disconnected close-ups.
The HD Enhancement capture guide specifies 20–500 photos for K/L series, and for PortalCam either 20–500 without enhancement points or 20–1,000 with the required points. Confirm reconstruction feature support for the selected model and release before capture.
Screen and Compare
Remove blurred, badly exposed, or obstructed images before using the set. Avoid making reflective, textureless, repetitive, or moving surfaces the main matching area. Keep the original scene arrangement and lighting consistent with the scan.
Retain a baseline reconstruction and compare the enhanced area from several viewpoints. Check for alignment artifacts and transitions to the surrounding model; clearer text in a single view is not enough to accept a distorted result.
4. Quality Assurance and Accuracy Reports
Use Three Separate Acceptance Gates
| Gate | What to inspect | Evidence to retain |
|---|---|---|
| Completeness | Requested rooms, floors, surfaces, and route connections | Scope list, previews, missing-area notes |
| Visual result | Blur, floating fragments, duplicate surfaces, lighting, and visitor paths | Review images and accepted reconstruction/settings |
| Measurement result | Independent dimensions/checkpoints and coordinate agreement | Check observations, residuals, reference systems, report |
Do not use a density display, registration RMSE, or attractive 3DGS scene as a substitute for the measurement gate.
LixelStudio Accuracy Check
For a supported transformed point cloud, open Project Processing → Accuracy Check and load the reference checkpoint file. Confirm its field order and height reference. Use the appropriate automatic target extraction or manually select the corresponding checkpoints, review the matches, then Calculate and export the report.
Automatic extraction requires the specified XGRIDS reflective targets captured with enough points; ordinary features are not interchangeable with those targets. The Accuracy Check procedure requires at least three selected points for the manual procedure.
Review per-point differences and the reported planar/elevation statistics. Investigate outliers rather than silently deleting them. Keep control-fit residuals distinguishable from independent checkpoint performance and state which locations were actually tested.
Accuracy Check tools and report ↗
If a Check Fails
Confirm point identity, reference coordinates, units, height type, and selection before changing processing. If the error is localized, inspect the route and connection there. If it is systematic, inspect coordinate conversion and reference setup. Preserve failed results and notes so the eventual correction is traceable.
5. Floor Plans and Sections
Point-Cloud Drawing in LixelStudio
Select the appropriate cloud and use a suitable section to isolate the required elevation band. Choose the drawing direction and thickness so furniture, ceilings, or multiple floors do not obscure the intended wall lines.
Use snapping and manual drawing tools to trace or refine the result. AI-Extract can propose contours, dimensions, and supported door/window results, but every required opening and junction needs review. Door/window detection is restricted to raw project or post-processed result data in the linked manual.
Save/export the drawing as DXF, reopen it in the receiving CAD application, and confirm units, alignment, layers, and representative dimensions. Keep the source point cloud and the extraction settings with the project.
Stockpile Volumes in LixelStudio
Select the cloud and open Volume Calculation. Inspect the extracted ground points, review or edit the detected stockpile boundary, and check the base plane before calculating. Export the report and retain the inputs and settings. A plausible volume is not proof that the boundary or reference plane is correct.
Official Volume Calculation instructions ↗
3D Drawing and DXF
Use the 3D Drawing workflow when the required vectors must retain their height information. The v4.1.1.0 release notes describe drawing from different perspectives and exporting DXF with 3D information. Check the exported geometry in the receiving CAD application; do not assume an ordinary 2D drawing export preserves elevations.
Official software overview including 3D Drawing ↗
Smart Space Recognition and 3D Layout
This is a separate LCC workflow. Enable Smart Space Recognition during an eligible indoor reconstruction and confirm the required 3D Layout license. In Scene Editor, use the associated floor-plan asset or manually bind the semantic-result folder if needed.
Review and edit walls, doors, windows, and room geometry against the model. Select the 3D Layout asset before exporting JPEG, OBJ, or DXF. Hidden assets are excluded, and the DXF exterior/interior dimension choices affect annotations independently of wall geometry.
Treat automatic geometry as a starting point. Confirm that the exported representation is suitable for the client’s task before describing it as an as-built drawing.
6. Advanced Formats and Downstream Handover
Convert the Right Kind of Data
In LCC Studio’s Converter, add a supported model, choose an available target format and output folder, run conversion, and review each task result. Batch conversion scans the first level of the selected parent folder, so check the task list before starting.
LCC/LCC2 and eligible 3DGS PLY are model formats in this workflow. A file named PLY could instead be a conventional point cloud or mesh and may not be a valid input. 3D Tiles and USD are output-only paths in the documented converter version.
LCC/LCC2 output is listed under the Free license; PLY, 3D Tiles, USD and USDZ require Premium in the linked converter documentation. Feature availability may change with the installed release and entitlement.
Geospatial information can be retained by supported exports when the source contains valid coordinates. Conversion does not establish those coordinates. Reopen the exported data and test placement in the actual downstream application.
LCC Converter paths, licensing and batch behavior ↗
Package a Delivery People Can Use
| Delivery | Include |
|---|---|
| Point-cloud files | Selected format, units/coordinate notes, independent check summary, opening instructions |
| RCP project | RCP index and complete matching data folder |
| Editable visual scene | Exported project and all required model/assets, not just a viewing link |
| Published tour | Tested link, agreed access method, opening/navigation instructions |
| CAD or layout output | DXF/other agreed files, units, source reference, and quality notes |
Keep a delivery manifest with filenames, date, software versions, scope, and known gaps. Test the package from a separate location so missing references do not remain hidden by your working folders.
Application-specific Revit, game-engine, or GIS import settings should be confirmed against that application’s current documentation and the client’s version. Use the XGRIDS export procedures here, then follow the receiving application’s import instructions.
Part 9 — Support and Official Resources
1. Diagnose Problems by Stage
| Symptom | First useful checks | Next decision |
|---|---|---|
| Scanner not discovered | Correct app, device power, permissions, chosen connection mode | Repeat that mode’s official setup before switching methods |
| Capture will not start | Activation, storage, battery, USB state, initialization message | Resolve the indicated readiness issue |
| Missing coverage | Route preview, occlusion, disconnected transitions | Recapture the affected area with a planned connection |
| Duplicate walls / separated floors | Loop connections, repeated layouts, fusion matches | Compare targeted reprocessing; PortalCam may warrant a Layering Optimization comparison |
| Thin objects disappear | Original coverage and filter strength | Compare a weaker filter before adding enhancement |
| Processing runs out of resources | Free disk, RAM/VRAM, local paths, competing tasks | Reduce supported workload or use suitable hardware; preserve the source |
| E57 conversion fails | Structured/unstructured path, colorization, panoramas, correct pose | Satisfy the chosen converter’s inputs |
| Coordinates are wrong | Datum, zone, units, height type, GCP matches, GNSS validity | Verify against independent checks before delivery |
| Model looks fine but client cannot open it | File type, complete dependencies, viewer entitlement/access | Test the actual delivered package or recipient link |
Make a Useful Support Package
Record the exact scanner and serial number, firmware, field app, desktop version, computer/GPU details, full error text, and the step that triggered it. Include a small reproducible project or requested logs through the support channel’s approved method. Keep client data and correction-service credentials out of casual screenshots or public links.
Before updating software to address a problem, retain the original files and a record of the working version. Avoid changing firmware, app, desktop software, and settings simultaneously when trying to identify a cause.
2. Official Sources and Version Notes
Reading This Guide
This True Point Precision customer guide helps you use your XGRIDS scanner and software with confidence. Procedures link to official XGRIDS documentation for additional detail. Follow the instructions and limits for your specific model, accessories, and software release.
For newly released features, check your installed software version and the official release notes before changing your workflow.
| Product or software | Documentation version |
|---|---|
| PortalCam | v1.3.0 |
| Lixel K1 (discontinued) | v2.4.0 |
| Lixel K2 | v1.2.0 |
| Lixel L2 Pro | v2.4.0 |
| Lixel L3 | v1.0.0 |
| LixelStudio | v4.1.1.0 |
| LCC Studio | v2.6.0 |
| LCC Scene Editor | v2.5.0 |
| LCC Model Editor | v1.3.1 |
These are documentation versions. Your scanner firmware and installed software may have different version numbers. Labels, licenses, regional options, and supported devices can differ.
LixelStudio Version and Update References
Current LixelStudio wiki and software version ↗
Processing, local enhancement, and fusion ↗
Volumes and application tools ↗
The LixelStudio links use XGRIDS’ latest documentation route, which can move to a newer release. This guide’s LixelStudio procedures were checked against v4.1.1.0 on November 2, 2026. The links provide current references; the guide text does not update automatically.
Official Starting Points
Scanner and software downloads ↗
Before Your Next Project
- Confirm your scanner model, accessories, and firmware.
- Check your mobile and desktop software versions and required feature access.
- Confirm your computer meets the requirements for the planned project size.
- Define the required output, coordinate reference, and quality checks.
- Test a small capture through to the final output using your chosen setup.
Last updated: November 2, 2026. Check official support and release information before changing a production workflow.
No sections match. Try “PortalCam”, “transfer”, or “LixelStudio”.