Skip to content

Troubleshooting

Jump to bottom
Mihir Bala edited this page Aug 18, 2022 · 9 revisions

If the app is not working as expected, please first ensure that you have set up the application properly using the Pre-flight Checklist. If you have done so and are still seeing incorrect behavior, refer to the troubleshooting guide below. Note: all drone-related troubleshooting is aimed at the Parrot Anafi. If you have implemented Steel Eagle for another drone, you may experience different issues.

Cloudlet Issues

TODO: Fill this out @teiszler

Drone Issues

Watch Issues

The watch fails to connect to the drone's access point.

This may happen if too many devices have connected to the drone's access point. The Parrot Anafi only supports two WiFi clients and will block any additional connections. Please check every WiFi-enabled device nearby to validate that there is no more than one additional device connected to the drone before reattempting a connection.

The watch still fails to connect to the drone, even though it is the only device attempting to do so.

Double-check the entered password for errors. If it is correctly entered, restart the drone and try again. It is possible for the drone to enter an invalid WiFi state if it is switched from dongle simulation mode to normal mode.

The watch does not connect to my Gabriel server.

  1. Ensure that the watch has active cellular service and that Mobile Data Always On is enabled in Connection Settings.
  2. Verify that your Gabriel server is publicly hosted and that the IP address and port are set in gradle.properties before building the DroneBrain app.
  3. If this issue still persists, try to turn off WiFi and visit the webserver page through a web browser app. This will reset the DNS cache and hopefully fix the issue.

The watch is not able to request the LTE network interface.

This may occur when the watch's is connected to its paired phone which causes the watch to route cellular connections through the phone. Please shut down the paired phone to prevent this. If the watch is still unable to request the LTE network interface, there may be something wrong with your mobile data plan. Ensure that the watch currently has cellular service and that Mobile Data Always On is enabled in Connection Settings.

The watch disconnects from the commander mid-flight and returns home.

This may happen for a number of reasons. When the drone lands, immediately check what application is running in the foreground.

  1. If you see that Drone Brain is still running and that the watch's cellular service still appears active, please submit an issue on GitHub along with any log data you can gather.
  2. If DroneBrain is not running and the watch functions normally, it is possible that another app forced it into the background. The current version of Drone Brain cannot work as a background process. Please enable Do Not Disturb in General Settings and disable Activities to Detect in Samsung Health Settings to prevent this from happening.
  3. If DroneBrain is not running and the watch is in overheat mode, then the watch likely overheated through heavy use of its LTE link. This is normal and is an unfortunate consequence of using an under-powered device in this role. Try to cool the watch using freezer packs or by keeping it in a shaded area before flying again.
Clone this wiki locally