Skip to content

Radio 2 setup guide

This comprehensive user guide will walk you through setting up, configuring, and using the 3DR Radio 2 (R7002) WiFi HaLow Telemetry Module for your drone or robotic applications.

What You’ll Need
  • 1 Access Point (AP) module - Acts as the main coordinator
  • 1 or more Station (STA) modules - Connect to your drone/robot
  • Computer with web browser
  • Ethernet cable (for AP connection)
  • Serial cables for STA connections
Basic Setup Overview
  1. AP Module: Connect via Ethernet to your computer/network
  2. STA Modules: Connect via serial to your drone/robot autopilot
  3. Configure: Use web interface to set up network parameters
  4. Test: Verify communication between all modules

Access Point (AP) Setup

  1. Power the AP module using either:

    • USB-C cable connected to computer
    • 5V power via the telemetry port (pins 1 and 6)
  2. Connect Ethernet cable:

    • Connect AP’s Ethernet port to your computer’s Ethernet port
    • Or connect to your local network switch
  3. Configure your computer’s network:

    • Windows: Open Network Connections, select your Ethernet adapter, then go to PropertiesInternet Protocol Version 4 (TCP/IPv4). Set the IP address to 192.168.200.250 and the Subnet mask to 255.255.255.0.
    • Linux: First, identify your Ethernet interface name by running:
      Terminal window
      ifconfig
      Replace enx9cebe8922aa8 below with your actual interface name. Then set the static IP and bring up the interface:
      Terminal window
      sudo ip addr flush dev enx9cebe8922aa8
      sudo ip addr add 192.168.200.250/24 dev enx9cebe8922aa8
      sudo ip link set enx9cebe8922aa8 up

Station (STA) Setup

  1. Power each STA module using:

    • USB-C cable, or
    • 5V power via telemetry port
  2. Connect to your autopilot:

    • Use the 6-pin JST-GH connector, or
    • Connect U1TX and U1RX to your autopilot’s telemetry port, and
    • Connect GND and +5V for power

Access the Web Interface

  1. Open your web browser and navigate to
http://192.168.200.1
  1. Login to the interface. If prompted, use default credentials.

  2. Verify the AP is working:

    • Check that the interface loads correctly
    • Note the current firmware version

Configure Network Settings

  1. Navigate to the Settings tab

  2. Set basic parameters:

    • Wi-Fi Mode: Access Point (AP)
    • SSID: 3DR_xxxxxx (or your custom name)
    • Security: WPA2 (recommended) or None for testing
    • Bandwidth: 4MHz (only option available)
    • Channel Frequency: 925 MHz (US) or appropriate for your region
    • DHCP Server: Enabled
  3. Save configuration and wait for reboot

  1. Power on your STA modules
  2. Wait 1-2 minutes for automatic connection
  3. Check AP Stats tab to see connected stations
  4. Note the IP addresses assigned to each STA
AP Stats Dashboard
  1. Access each STA’s web interface at
http://192.168.200.x

Where x is the station’s IP last octet.

  1. Configure STA settings:

    • Wi-Fi Mode: Station (STA)
    • SSID: Same as AP (3DR_xxxxxx)
    • Security: Same as AP
    • Channel Frequency: Same as AP
  2. Save and reboot for each STA

  1. Check AP Stats tab:
    • All STAs should show as “Connected”
    • Note their IP addresses
    • Check signal strength indicators
Dashboard Interface
  1. Test data flow:
    • Send MAVLink data from your autopilot
    • Verify it appears at the AP
    • Check for any error messages
  1. Configure your ground station to connect to the AP
  2. Verify telemetry data flows from drone to ground station
  3. Test command sending from ground station to drone
  1. Power Settings
  • TX Power: Adjust based on range requirements
    • Higher power = longer range, more battery usage
    • Lower power = shorter range, less battery usage
  1. Channel Selection
    • US (FCC): 902-928 MHz range
    • Europe: 863-868 MHz range
    • Choose channels with the least interference in your area
  1. WPA2 Setup

    1. Set a strong password (minimum 8 characters)
    2. Use WPA2-PSK for better security
    3. Avoid WEP (deprecated and insecure)
  2. Network Isolation

    • Enable client isolation if you don’t want STAs to communicate with each other
    • Use VLANs for enterprise deployments
  1. Update firmware to mesh-capable version

  2. Configure mesh parameters:

    • Mesh ID
    • Parent selection criteria
    • Routing protocols
  3. Deploy modules in tree topology

  4. Test mesh connectivity between all nodes

Prerequisites
  • All modules powered on and connected
  • Firmware files for both AP and STA modules
  • Stable network connection
  1. For each STA module:

    • Access web interface: http://192.168.200.x
    • Go to Settings > Firmware Update
    • Upload STA firmware file
    • Wait for reboot and reconnection
  2. Verify all STAs reconnect to the AP

  1. Access AP interface: http://192.168.200.1
  2. Go to Settings > Firmware Update
  3. Upload AP firmware file
  4. Wait for AP reboot (network will be temporarily unavailable)
  1. Check all modules are running new firmware
  2. Test communication between all modules
  3. Verify web interfaces load correctly

Symptoms: STA doesn’t appear in AP Stats

Solutions:

  • Check power and connections
  • Verify SSID and security settings match AP
  • Wait 2-3 minutes for automatic connection
  • Power cycle the STA module

Symptoms: Low signal bars, intermittent connection

Solutions:

  • Increase TX power on both AP and STA
  • Check for physical obstructions
  • Try different channel frequency
  • Reposition modules for better line-of-sight

Symptoms: Can’t access configuration pages

Solutions:

  • Clear browser cache and cookies
  • Try different browser
  • Check network connection settings
  • Verify correct IP address

Symptoms: Upload fails or module becomes unresponsive

Solutions:

  • Verify correct firmware file for module type
  • Check file size (should be ~1MB)
  • Ensure stable network during upload
  • Power cycle and try again

If AP Becomes Unresponsive:

  1. Power cycle the AP module
  2. Wait 3-5 minutes for full reboot
  3. Try accessing http://192.168.200.1 again
  4. Check for error messages in serial output

If STA Won’t Reconnect:

  1. Power cycle the STA module
  2. Wait 2-3 minutes for reconnection
  3. Check AP Stats to see if it appears
  4. Reconfigure if necessary

If Wrong Firmware Uploaded:

  1. Use direct Ethernet connection to access the device
  2. Reconfigure WiFi settings through web interface
  3. Upload correct firmware for the module type
  • Mount modules away from metal objects and antennas
  • Use quality cables for power and data connections
  • Secure connections to prevent vibration damage
  • Test thoroughly before flight operations
  • Plan your network topology before deployment
  • Consider range requirements vs. power consumption
  • Test in your actual environment before critical operations
  • Have backup modules ready for critical applications
  • Regular firmware updates for security and features
  • Monitor signal strength and connection quality
  • Check for physical damage after rough landings
  • Keep configuration backups for quick recovery

Follow these steps to connect your 3DR Radio 2 to QGroundControl (QGC):

  • Power up the AP (Access Point) module and connect it to your host PC via Ethernet or WiFi.
  • Ensure your PC joins the same IP subnet as the AP (e.g., 192.168.200.250).
    • On Linux, you can verify your connection with ip addr or ifconfig.
  • Confirm you can access the AP’s web interface (typically at http://192.168.200.1).

2. Ensure STA Module is Connected to Flight Controller

Section titled “2. Ensure STA Module is Connected to Flight Controller”
  • The STA (Station) module should be connected to your flight controller’s UART telemetry port.
  • Power up the STA module and ensure it joins the AP network.
Section titled “3. Configure QGroundControl Communication Link”
  • Open QGroundControl on your host PC.
  • Go to Application Settings (gear icon) → Comm Links.
  • Edit the existing links or add a new link:
    • You can give the link a custom name for easy identification.
    • Disable all other link types (e.g., Serial, TCP, Bluetooth).
    • Enable only UDP.
    • Set the UDP port to 14550 (default for MAVLink).
    • Optionally, select Automatically Connect on Start so QGroundControl connects as soon as it launches.
    • If needed, you can also enable High Latency mode for long-range or low-bandwidth links.
  • Save and connect.
QGroundControl Communication Link Example
  • QGroundControl should automatically detect the MAVLink stream from the flight controller via the HaLow link.
  • You should see vehicle telemetry and status in QGC.
QGroundControl Connected Example QGroundControl Status Example

Version: 0.1.0 Last Updated: September 2025 Compatible with: 3DR Radio 2 R7002 v2.0 and later