DroneEngage FAQ

Find answers to common questions about using DroneEngage with Ardupilot. For additional terms, see de-glossary. Submit new questions via GitHub Issues.

General Questions

I don’t understand many terms used in this wiki.
- Check the DroneEngage & Andruav Glossary for definitions of terms like FCB (Flight Control Board), MAVLink, and JSON.
- For a beginner’s overview, see What is DroneEngage? or Building DroneEngage Code.
I can’t find my Access Code.
- Your Access Code can be easily regenerated from (see Create your Drone-Engage Account Key).
- If still missing, contact support via mohammad.hefny@droneengage.com.
How many drones and Ground Control Stations (GCS) can connect simultaneously?
- Theoretically unlimited, but depends on: - Network quality (e.g., WiFi or GSM-Modem stability). - Data type (e.g., telemetry, video streaming). - Hardware performance (e.g., Raspberry Pi model).
- See Telemetry for optimizing bandwidth with Smart Telemetry.
Does DroneEngage support Raspberry Pi 5?
- Yes, new RPI-Images runs on RPI-5 as well as RPI-4 & RPIZero W2.
- Follow Building DroneEngage Code for compilation steps.
- All DroneEngage modules are compatible with RPI-5’s improved performance.
What hardware do I need for DroneEngage?
- Essential: Raspberry Pi (Zero W, Zero 2 W, 3, 4, or 5), 4G/LTE USB modem or HAT, Ardupilot/PX4 flight controller, DroneEngage account
- Optional: Camera(s), Xbox/PlayStation controller, additional sensors
- Weight considerations: RPI-Zero setup weighs only 42g for telemetry-only, RPI-Zero 2 W with camera weighs 52.2g
- See What is DroneEngage? for complete hardware requirements and examples.
Can I test DroneEngage without a drone?
- Yes! The RPI image includes a built-in simulator for 2 drones.
- Use Start Simulator in the DE APP Management App Management screen.
- Alternatively, use Software-in-the-Loop (SITL) on your computer - see Simulation.
- Simulation is highly recommended before flying long-range missions.

Installation & Updates

How do I update to the latest DroneEngage binaries?
- Recommended: Use the DE APP Management web interface to update modules automatically.
- Manual: Download from cloud.ardupilot.org/downloads/RPI/Latest/.
- READY-IMAGES are always the easiest option.
I updated a module and now it doesn’t work. What happened?
- When modules are updated, they come with fresh default configuration files.
- Your previous settings (account credentials, server URLs) are NOT preserved automatically.
- Solution: Reconfigure the module via the WebAdmin interface, or restore specific fields from your backup.
- See DE APP Management for detailed recovery steps.
Where are my configuration backups stored?
- Module backups (automatic before each update): /home/pi/drone_engage_backups/
- Config file backups (manual via button): /home/pi/drone_engage_config_backups/
- Always click Backup Configuration Files before major updates.
How do I roll back to a previous module version?

Navigate to /home/pi/drone_engage_backups/

Find the backup file (e.g., de_comm_20251203_172630.tar.gz)

Extract it: tar -xzf ~/drone_engage_backups/de_comm_20251203_172630.tar.gz -C /home/pi/drone_engage/

Restart DroneEngage services.

WiFi & Network

How do I connect my RPI to a WiFi network?
- Connect to WIFI DE_ADMIN password **droneengage*
- Access the WebAdmin at https://192.168.9.1:9090 (when connected to the DE_ADMIN AP).
- Go to the WiFi Manager and enter your WiFi SSID and password.
- Click Configure WiFi to connect.
- See DE WiFi Manager for details.
I entered the wrong WiFi password and lost access to my RPI access. How do I recover?
- Remove the SD card from the Raspberry Pi.
- Insert it into a computer and create a file named activate_ap.txt in the boot folder.
- Reinsert the SD card and reboot the RPI.
- The DE_ADMIN Access Point will be enabled automatically.
- Connect to it and reconfigure WiFi with the correct password.
What are the default Access Point credentials?
- SSID: DE_ADMIN
- Password: droneengage
- Access the admin interface at https://192.168.9.1:9090
Can I use both WiFi and a 4G modem at the same time?
- Yes! The system can maintain internet via a GSM/4G modem independently of WiFi settings.
- The AP mode is for local configuration access only and doesn’t provide internet.
- If a GSM modem is installed, the unit stays connected regardless of WiFi/AP mode.

Account & Configuration

How do I set up my DroneEngage account on the RPI?
- Access the WebAdmin interface.
- Go to Account Setup (RPI Administration Tools).
- Enter your Username and Access Code.
- Click Update Config to save.
What is an AirGap server and do I need one?
- An AirGap server is a private DroneEngage server for isolated networks.
- Most users should leave the server as default (cloud.ardupilot.org).
- Only change if you’re running a private server installation.
Which configuration files store my account credentials?
- /home/pi/drone_engage/de_comm/de_comm.config.module.json - Main module
- /home/pi/simulator/sim_de_mavlink_instances/de_comm.1.config.module.json - Simulator 1
- /home/pi/simulator/sim_de_mavlink_instances/de_comm.2.config.module.json - Simulator 2

Service Management

How do I start/stop DroneEngage services?

Via WebAdmin: Use the App Management screen (DE APP Management).

Via Terminal:

sudo systemctl start de_comm    # Start
sudo systemctl stop de_comm     # Stop
sudo systemctl restart de_comm  # Restart

How do I enable DroneEngage to start automatically on boot?
- Via WebAdmin: Click Enable AutoStart DE in App Management.
- Via Terminal: sudo systemctl enable de_comm de_mavlink de_camera
What’s the difference between “Stop DE” and “Disable AutoStart DE”?
- Stop DE - Temporarily stops services; they restart on next reboot.
- Disable AutoStart DE - Permanently prevents services from starting until re-enabled.
How do I apply configuration changes?
- Click Clear DE Caches to remove cached configurations.
- Click Restart DE to restart services with new settings.
- Or simply reboot the RPI.

Troubleshooting

Why is my MAVLink connection failing?
- Ensure correct fcb_connection_uri in de-config-mavlink (UDP or serial port).
- Check TX/RX pins are correctly connected between RPI and FCB.
- Verify the baudrate matches your Flight Control Board settings.
- If using dynamic port detection, ensure dynamic: true is set.

How do I view service logs for debugging?

Via Terminal:

sudo journalctl -u de_comm -n 50      # Last 50 lines
sudo journalctl -u de_comm -f         # Follow live
sudo journalctl -u de_mavlink -b      # Since last boot

Replace de_comm with de_mavlink or de_camera as needed.

How do I check if DroneEngage services are running?
- Via Terminal: sudo systemctl status de_comm , sudo systemctl status de_mavlink , sudo systemctl status de_camera
- Look for active (running) in green.
- Press q to exit the status view.
My RPI is running slow. How do I check system resources?
- Disk space: df -h
- Memory: free -h
- CPU temperature: vcgencmd measure_temp
- Running processes: htop (press q to exit)
How do I clear logs to free up disk space?
- Use Clear Logs in the App Management screen.
- Or via terminal: sudo journalctl --vacuum-time=1d

Telemetry & Video

What is Smart Telemetry, and how do I adjust it?
- Smart Telemetry reduces bandwidth by filtering non-critical data, ideal for slower networks.
- Adjust levels (0–3) in de_mavlink.config.module.json (see de-config-mavlink). - Level 0: No optimization (full data). - Level 3: Maximum optimization (minimal data, slower GCS updates).
How do I enable/disable the camera?
- Via WebAdmin: Use Enable RPI-CAM / Disable RPI-CAM in App Management.
- Via Terminal: sudo systemctl start de_camera or sudo systemctl stop de_camera

File Management

Where are DroneEngage modules installed?
- All modules are in /home/pi/drone_engage/
- List them with: ls ~/drone_engage
How do I access configuration files?
- Use the Navigator in WebAdmin (Drone Engage RPI Image Tools - Navigator) for easy file browsing.
- Or use the Terminal (Drone Engage RPI Image Tools - Terminal) for direct access.
- Config files are in each module folder (e.g., ~/drone_engage/de_comm/de_comm.config.module.json).
How do I manually run a module for debugging?
- First stop the service: sudo systemctl stop de_comm
- Then run manually:
```
cd ~/drone_engage/de_comm
sudo ./de_comm.so
```

Contributing

How do I contribute to the wiki or report issues?
- Edit content by submitting pull requests to github.com/DroneEngage/droneengage_ap_wiki (see Contributing to the DroneEngage Wiki).
- Report issues or suggest FAQs via GitHub Issues.
Can I build DroneEngage from source code?
- Yes! Both droneengage_communication and droneengage_mavlink can be compiled from source.
- Follow Building DroneEngage Code for complete build instructions.
- Supports DEBUG and RELEASE builds with automatic version management.
- Compatible with RPI-4, RPI-5, and Linux laptops/VMs.
How do I generate Debian packages for DroneEngage?
- After building from source, navigate to the build directory: cd ~/de_code/droneengage_communication/build
- Run: cpack -G DEB to generate .deb packages
- Install with: sudo dpkg -i de-communicator-pro-*.deb or sudo dpkg -i de-mavlink-plugin-*.deb
- Packages install to $HOME/drone_engage/ with proper dependencies.
What are the current version numbers for DroneEngage modules?
- droneengage_communication: 3.10.1.x (auto-incremented on RELEASE builds)
- droneengage_mavlink: 5.6.8.x (auto-incremented on RELEASE builds)
- Version format: MAJOR.MINOR.BUGFIX.BUILD
- Use ./build.sh RELEASE to increment BUILD number.
What are the main DroneEngage modules and their purposes?
- de_comm: Communication module - handles server connectivity and inter-module communication
- de_mavlink: MAVLink protocol handler - communicates with flight controllers
- de_camera: Camera streaming module - manages video feeds and recording
- de_rpi_gpio: Raspberry Pi GPIO control - hardware pin management
- de_tracking: Object tracking module - visual tracking capabilities
- de_sdr: Software Defined Radio module - radio communication features
How does DroneEngage differ from the original Andruav?
- DroneEngage is the Linux-based successor to Android-based Andruav
- Designed for dedicated companion computers (Raspberry Pi) vs mobile phones
- More robust architecture for enterprise and long-range operations
- Enhanced modular design with better hardware integration
- Improved fleet management and swarm capabilities
What safety features does DroneEngage provide?
- RC Blocking: Field pilot with physical transmitter can override all remote commands
- TX Freeze: Locks current throttle/control positions for long-range flights
- Independent Geo-Fencing: Works alongside or instead of FCB’s built-in geo-fence
- Read-Only Mode: Prevents any remote control when monitoring-only is needed
What types of drones does DroneEngage support?
- Compatible with Ardupilot and PX4-based vehicles
- Supports Copter, Plane, Rover, and Sub vehicles
- Works with any FCB that supports MAVLink protocol
- Compatible with popular boards: Pixhawk, Cube, Kakute, OBAL, and others
How do I connect different types of flight controllers?
- Serial Connection: Use fcb_connection_uri with type: “serial”, port: “/dev/ttyUSB0”, baudrate: 115200
- UDP Connection: Use fcb_connection_uri with type: “udp”, ip: “0.0.0.0”, port: 14551
- Dynamic Port Detection: Add dynamic: true to auto-detect USB ports from /dev/ttyUSB0-10
- Ensure TX/RX pins are correctly connected between RPI and FCB
- See de-config-mavlink for detailed configuration examples.
What is the DataBus and how does it work?
- DataBus is DroneEngage’s internal UDP-based communication protocol
- Allows modules to exchange data efficiently using publisher/subscriber pattern
- Supports automatic message chunking for large data transfers
- Enables modular architecture with independent module communication
Can I use DroneEngage for swarm operations?
- Yes! DroneEngage supports hierarchical swarm formations
- Control multiple drones from a single interface
- Synchronized missions with leader and follower roles
- Advanced fleet management capabilities
- See DroneEngage SWARM for swarm development details.