Documentation Index

Fetch the complete documentation index at: https://knowledge.emesent.com/llms.txt

Use this file to discover all available pages before exploring further.

Scan data storage

Prev Next

This article describes how the GX1 stores scan data and how to manage capacity across a deployment. The GX1 has 2TB of internal storage, which holds approximately 40 hours of scanning at full camera resolution.

What is it?

The GX1 stores scan data internally during a mission, then offloads it to the kit-included Portable SSD T7 Shield for transfer to a host computer and processing in Aura.

Capacity

How quickly storage fills depends on which sensors are recording.

Sensor combination

Approximate data rate

LiDAR with full camera capture

Up to 50 GB per hour

LiDAR only

Approximately 10 GB per hour

Expand storage with a microSD card

The GX1 has a microSD Card Slot in the Battery Carrier, next to the SIM Card Slot. Insert an exFAT-formatted microSD card to expand storage by up to 2TB, in addition to the 2TB internal SSD.

When a microSD card is installed, the GX1 records scans to the microSD card first.

Why it matters

Storage capacity is the second constraint after battery runtime. Monitoring capacity and offloading data between sessions prevents data loss and downtime.

How it works

Scan data is offloaded over USB-C to the Portable SSD T7 Shield, then transferred to a host computer for processing in Aura.

For the offload procedure, see Offload GX1 scan data. For details on the Portable SSD, see GX1 components and interfaces.

Where storage capacity is shown

Commander shows the storage bar on the scan setup page. Storage notifications also appear on the 3D view during a scan.

As storage approaches full, Commander displays warnings:

Warning

Threshold

Restriction

Low

200 GB remaining

None

Critical

50 GB remaining

Cannot start a new scan until storage is offloaded

Best practices

Do

Don't

Offload scan data between sessions.

Wait for storage to be nearly full before offloading.

Check remaining capacity in Commander before every mission.

Start a long mission without confirming sufficient capacity.

Plan offload time into multi-day deployments.

Treat storage as effectively unlimited.