Drone Mapping FAQs

Frequently asked questions about our sUAS based drone mapping solutions, including our Loki system.

1. Why does Publisher Client create copies on my local drive?

The Publisher Client will create local copies of files when they are published to Reckon. Once the publishing process is complete, the local copies can be deleted.

2. Which Loki MEP interface workflow should I use?

Please refer to the ASPSuite User Guide, a user should select the Loki MEP interface workflow that best suits the drone being used.
Inspire 2 -> DJI SD Cable
Phantom 4 Pro -> DJI USB Cable
M200/M210 -> DJI USB Cable
M200v2 -> DJI SD Cable
M600 -> DSLR Cable
Wired X4S camera -> DSLR Cable
Phantom 4 RTK -> DJI P4 RTK (PPK)
For additional assistance, please refer to our Loki FAQ.

3. What signals does the provided Loki antenna receive?

The provided Loki antenna receives L1/L2 GPS and GLONASS signals.
For additional assistance, please refer to our Loki FAQ.

4. How much storage space does Loki have?

Loki has 1GB of external storage space to accumulate SBF files. Older SBF files will not be overwritten as new ones are created, so it is good practice to delete unwanted files from your Loki unit. Users often think their SBF files are not being recorded, when the problem is disk space. If you perform a flight and do not see an SBF file, delete some older files and then cycle the Loki power. The missing files should be visible after the power cycle.
For additional assistance, please refer to our Loki FAQ.

5. What is the maximum distance I can fly Loki from the base station?

We recommend flying within 12 miles (20 km) of the base station to get the best results.
For additional assistance, please refer to our Loki FAQ.

6. What is the workflow for the ASPSuite to manage multiple flights in a project?

When you fly a mission that requires multiple batteries and powering the drone (and Loki) on and off, you will have independent files for each flight.
Flight 1 – Images, Loki file, DAT file
Flight 2 – Images, Loki file, DAT file
In ASPSuite, create a new ASP Project and name the first flight “Flight 1”, or something like that. For the second flight select “Add flight to an existing project” and name it “Flight 2”, or something like that. Your ASP project will be subdivided into folders based on your chosen flight names, but each flight will need to be processed individually.
For additional assistance, please refer to our Loki FAQ.

7. On the LOKI, what is the green button?

The green button turns the Loki on and off manually. After Loki is securely installed and you are prepared for flight, power on Loki manually by pressing and holding the green On/Off button until Loki powers on. The aircraft should be powered on only after Loki is powered on. A new SBF file is created each time
Loki is powered on, and ends when Loki is powered off by holding the button down until the status LED’s turn off. So, for each flight, Loki should be powered on manually before the aircraft, and powered off manually upon landing. Loki will not power off automatically when powered on manually. Periodically, check to make sure that the Loki internal storage is not full. Please view the Loki User Guide for additional operational info.
For additional assistance, please refer to our Loki FAQ.

8. How important is it to keep the orientation values (Omega, Phi, Kappa) for the cameras when processing Loki data in PhotoScan/Metashape? We are importing the images.txt values into Pix4D/Metashape. When the document is imported, the orientation values are deleted. Are there any significant consequences either way?

The orientation values are not needed as Metashape, etc., will calculate these values during processing.


AirGon Support has written 155 articles