[Beta] Flux Desktop App

Flux Desktop App - [Beta] Quick Start Guide

The Flux Desktop App enables SLAM-like alignment and cross-platform support for Fluxscan files, as well as several other small improvements.

New Features/Differences from Flow App

• SLAM-like alignment engine for super sharp scans

Recommended 32GB RAM or higher. Some large scans may need more than this

• Greater OBS file flexibility

  • Can process with only L1/L2 signals, or no OBS file
• More CRS flexibility
• Windows, Mac, Linux support
• Full lidar FOV on Flux H1 and O1 variants

  • Points captured from the full 360 degree FOV of the Hesai and Ouster lidars are used in the generated point cloud for better capture of vertical faces and objects.
• Flight path flexibility

  • Aircraft path is no longer limited to straight mission tracks. Aircraft can be manually piloted in all directions and still produce scans with the desktop app. This is useful for scanning complex objects, vertical faces, and getting in close around obstacles.

Installing

Currently, the Flux Desktop app is a closed beta program. Reach out to [e-mail] if you are interested in joining.

Check your email for a link to download the app

Windows

• Unzip the file
• Navigate to the viewer_cpp-windows-x64/viewer_cpp.exe file
• Double click to open it

  • You may need to agree to 'run anyway' to open the program

Mac

• Open the folder, then drag the app in the Applications folder
• Double click the app in the Applications folder

  • You may need to click 'ok' to allow the app to open

Processing a Fluxscan

Import the file

Set the Obs file source and CRS.

• If Flux was flown with NTRIP was used, this will be selected by default

  • 
  • You can also use an external base station or CORS file. Ensure you have selected the correct coordinates for the base station point and CRS
  • Unlike the Flow app, Obs files with only L1/L2 signals can be used.
  • The Flux Desktop app can also process without a base station file

The scan may have a decrease in global/relative accuracy and sharpness compared to using an OBS file

Device Geometry

• Select the aircraft and isolator type you flew the mission with. This is important for calculating offsets from the GNSS antennas

  

Solver

• Select the Advanced alignment option, Normal works well in the vast majority of cases
• 

The default is to do a Trajectory Solve only, which will not use the SLAM-like alignment feature. We recommend using the Normal advanced alignment

Project Coordinates

• Set as desired. You don't have to specify a coordinate frame unless you want to
• 

GCPs

• GCPs can be imported if desired, but are not required

GCPs are not used to align the map or modify the point cloud, and are only shown as reference

Process

• On the Summary and Process page, click Process and Align
• The progress is shown on the bottom bar

Known issues:

• The estimated processing times given are not accurate
• The Trajectory Solve process may take a few minutes, but the progress bar will remain at 0%. This is normal

View

• Once the process is complete, you can view the scan in the View tab
• Multiple options exist to view and adjust color pallets, color mode, and more

Protip: if your machine can handle it, you can increase the viewable points under the settings>display>point cloud display budget for a more detailed view of the scan