Skip to main content

Blackboxes

The component of the Dronisos systems are recording important information in real time. Contrary to hardware based Blackboxes in planes, the Dronisos system uses a software format. Three types of Blackboxes exists, each having a specific purpose:

  • DCC Blackbox: contains information of the different services and programs running on the DCC computer. This Blackbox type is particularly important if the whole system or a high number of drones had a problem.
  • RTK Base Blackbox: contains information relative to the GPS situation as seen by the RTK Base. This Blackbox type should be sent alongside the DCC Blackboxes, even if the problem wasn't related to GPS.
  • Drone Blackbox: the most common type, contains information gathered by the drone since switched on. Please follow the Alarms and States page to know when to send this type of Blackboxes.

These Blackboxes are to be sent for analysis when something unusual happens.

Prerequisites​

  • An operation laptop
  • To extract a drone Blackbox:
    • one drone
    • one charged battery
    • one USB A to micro-USB B cable
  • To extract a DCC Blackbox:
    • one DCC
    • one RJ45 cable
  • To extract a RTK Base Blackbox:
    • one RTK Base
    • one DCC
    • two RJ45 cables
  • A working internet connection

Preparation​

Multiple types of Blackboxes can be extracted at the same time. For example, to extract both a DCC Blackbox and a Zephyr one, just follow the instructions for both.

Zephyr Blackbox​

If the drone is switched on, perform a hard-reboot. Otherwise, plug the battery in and switch on the drone using the physical button located on the back of the drone. Connect the drone to the operation laptop using the USB cable. Wait a few minutes for the drone to be ready for the Blackbox extraction.

Helios Blackbox​

If the drone is not switched on, plug the battery. If the drone is already switched on, there is no need for a hard-reboot. Connect the drone to the operation laptop using the USB cable. Wait a few minutes for the drone to be ready for the Blackbox extraction.

DCC Blackbox​

If the DCC installation isn't complete, please follow the DCC Installation page. If the DCC isn't switched on, press the power button located on the front panel and wait a few minutes for the server to boot-up. Connect the operation laptop to the switch of the DCC kit using an RJ45 cable.

RTK Base Blackbox​

If the DCC installation isn't complete, please follow the DCC Installation page. If the DCC isn't switched on, press the power button located on the front panel and wait a few minutes for the server to boot-up. Make sure that the RTK Base unit is connected to the DCC switch using an RJ45 cable. Wait a few minutes for the RTK Base to boot-up.

Method​

Blackboxes can be retrieved and sent to the Support team using Loghub, a command-line based tool available on all operator laptops.

On an operator laptop, click on the Loghub icon to launch a terminal.

Loghub Icon

Type the following command to start the retrieval process:

loghub extract

Loghub will ask a series of question:

  1. Username [XXX]:: write your name then confirm with Enter.
  2. Send DCC logs: if Y is answered, Loghub will retrieve the DCC Blackbox. If N is answered, Loghub will skip this Blackbox type.
    • Logs duration to retrieve (in hours)[1]: if Y was answered previously, prompt for the amount of time to include in the Blackbox. You can press Enter to send 1 hour by default or provide a custom value.
  3. Send RTK logs: if Y is answered, Loghub will retrieve the RTK Base Blackbox. If N is answered, Loghub will skip this Blackbox type.
  4. If no drone is connected, Loghub will print Continue without drone blackbox ? [y/N]. Make sure to answer Y if sending other types of Blackboxes.
  5. If a drone is connected, Loghub will automatically print the Blackboxes available to be retrieved. Select the Blackbox number available in the leftmost column. Please make sure that the Blackbox selected is the correct one and that its information are coherent with the flight done (size, data, etc.).
  6. At this step, the user can dra-and-drop files into the terminal for them to be sent alongside the Blackboxes. These can be screenshots for example. Press Enter to confirm or to ignore.
  7. Summary: short text to let the Support and R&D team what the Blackbox is about. This should be as concise as possible. For example Stone Mountain Park - Mobile Fencing.
  8. Issue details: long text to describe in details what happened. Please remember that the more context provided, the better.
  9. Do you want to upload the data now: if Y is answered, Loghub will try to send the Blackbox to our servers over the internet. If this fails or if N is answered, Loghub will automatically store the Blackbox to be sent at a later time.
info

If you chose to send the Blackbox directly and that the upload was successful, Loghub will generate an issue number. Please attach this issue number to any message you may have with the Support team.

info

Only send one DCC or RTK Base Blackbox per incident.

If you chose to not send the data now or if the upload failed, the Blackbox will be stored on the operation laptop. YOu can have a look at stored Blackboxes using the following command:

loghub list

To send these Blackboxes to the remote server, use the following command and wait for the process to end:

loghub sync

Sending blackboxes​