Skip to content
Aero Atoms Docs

Orbit EVO Quickstart Guide

UART Variant Setup

The Orbit EVO UART variant is available in two connector configurations:

  • Type 1: 6-pin JST-GH (GPS/Compass) + separate Safety Switch and Buzzer cables
  • Type 2: 10-pin connector for direct connection to GPS1 port (includes GPS, Compass, Safety Switch, and Buzzer)

Type 1: 6-Pin JST-GH Connector

Connection

  1. Connect the main 6-pin GPS/Compass cable to one of the available serial ports on the flight controller (e.g., SERIAL3/TELEM1, SERIAL4/GPS2, etc.)
  2. Connect the Safety Switch cable (2-pin) to the flight controller’s safety switch port
  3. Connect the Buzzer cable (2-pin) to the flight controller’s buzzer port
  4. Ensure proper pin connections on 6-pin connector:
    • Pin 1: VCC → 5V
    • Pin 2: TX → RX (Flight Controller)
    • Pin 3: RX → TX (Flight Controller)
    • Pin 4: SCL → SCL (I2C)
    • Pin 5: SDA → SDA (I2C)
    • Pin 6: GND → GND

Setting Up with Ardupilot Firmware

Power and Configuration

  1. Power the flight controller and connect it to Mission Planner
  2. Navigate to Config/Tuning > Full Parameter List
  3. Set the following parameters (example using SERIAL3 port):
    • SERIAL3_PROTOCOL: Set to 5 (GPS)
    • SERIAL3_BAUD: Set to 38 (38400 baud) or 115 (115200 baud)
    • GPS_TYPE: Set to 1 (AUTO) or 2 (u-blox)
    • COMPASS_TYPEMASK: Ensure external compass is enabled
    • COMPASS_ORIENT: Set to 0 (None) or adjust based on mounting orientation
    • BRD_SAFETY_DEFLT: Set to 0 (Disabled) if not using safety switch, or 1 (Enabled)

Completing Setup

  1. Click Write Params in Mission Planner after modifying the parameters
  2. Reboot the flight controller to activate the serial GPS
  3. Verify proper connection by checking:
    • Green LED (Power) is solid ON
    • Blue PPS LED starts blinking at 1Hz once GNSS gets a 3D fix
    • Safety LED is Red (Disarmed) - press to arm (Green)
    • Buzzer beeps on power-up and GPS fix acquisition
  4. In Mission Planner, check the Flight Data screen to confirm GPS lock and satellite count

Setting Up with PX4 Firmware

Firmware and Connection

  1. Load the PX4 firmware onto the autopilot
  2. Ensure all three cables are properly connected (GPS, Safety, Buzzer)

Configuration

  1. Connect the flight controller to QGroundControl
  2. Navigate to Vehicle Setup > Parameters
  3. Set the following parameters (example using TELEM2 port):
    • SER_TEL2_BAUD: Set to 38400 or 115200
    • GPS_1_CONFIG: Set to the appropriate serial port number (e.g., 102 for TELEM2)
    • GPS_1_PROTOCOL: Set to 1 (u-blox) or 0 (Auto-Detect)
    • CBRK_IO_SAFETY: Set to 0 to enable safety switch

Completing Setup

  1. Reboot the flight controller to apply the changes
  2. The Orbit EVO will automatically configure and start working once connected
  3. Verify the connection by checking that:
    • The blue PPS LED indicator is blinking at 1Hz once a GNSS fix is obtained
    • Safety LED is Red (Disarmed) - press to arm (Green)
    • Buzzer provides audible feedback
    • GPS status in QGroundControl shows a valid position fix
    • Compass calibration can be performed successfully

Type 2: 10-Pin Direct GPS1 Port Connector

Connection

  1. Connect the single 10-pin connector directly to the flight controller’s GPS1 port
  2. This single cable provides:
    • GPS UART communication
    • Compass I2C communication
    • Safety Switch signal
    • Buzzer signal
    • Power (5V and GND)

10-Pin Pinout (Pixhawk GPS1 Standard)

PinSignalDescription
1VCC5V Power
2TXGPS Transmit
3RXGPS Receive
4SCLI2C Clock (Compass)
5SDAI2C Data (Compass)
6SAFETY_SWSafety Switch Signal
7SAFETY_LEDSafety LED Control
83V3Not used
9BUZZERBuzzer Signal
10GNDGround

Setting Up with Ardupilot Firmware

Power and Configuration

  1. Power the flight controller and connect it to Mission Planner
  2. Navigate to Config/Tuning > Full Parameter List
  3. The GPS1 port is typically auto-configured, but verify these parameters:
    • SERIAL3_PROTOCOL: Should be 5 (GPS) - GPS1 port is usually SERIAL3
    • SERIAL3_BAUD: Set to 38 (38400 baud) or 115 (115200 baud)
    • GPS_TYPE: Set to 1 (AUTO) or 2 (u-blox)
    • COMPASS_TYPEMASK: Ensure external compass is enabled
    • COMPASS_ORIENT: Set to 0 (None) or adjust based on mounting orientation
    • BRD_SAFETY_DEFLT: Set to 1 (Enabled) - safety switch is active

Completing Setup

  1. Click Write Params in Mission Planner after modifying the parameters
  2. Reboot the flight controller
  3. All components should work automatically:
    • GPS and Compass auto-detected
    • Safety switch functional (Red LED = Disarmed)
    • Buzzer active for alerts
  4. Verify in Flight Data screen:
    • GPS lock and satellite count
    • Compass heading displayed
    • Safety switch status indicator

Setting Up with PX4 Firmware

Firmware and Connection

  1. Load the PX4 firmware onto the autopilot
  2. The GPS1 port is auto-configured on most Pixhawk-compatible flight controllers

Configuration

  1. Connect the flight controller to QGroundControl
  2. Navigate to Vehicle Setup > Parameters
  3. Verify or set the following parameters:
    • GPS_1_CONFIG: Should be 0 (GPS1 port) or auto-detected
    • GPS_1_PROTOCOL: Set to 1 (u-blox) or 0 (Auto-Detect)
    • CBRK_IO_SAFETY: Set to 0 to enable safety switch
    • The GPS1 port on PX4 is typically pre-configured at 115200 baud

Completing Setup

  1. Reboot the flight controller to apply the changes
  2. All features should work out-of-the-box:
    • GPS and Compass auto-detected
    • Safety switch operational
    • Buzzer alerts enabled
  3. Verify the connection by checking:
    • GPS status shows valid position fix
    • Compass data available
    • Safety LED: Red = Disarmed, Green = Armed
    • Buzzer sounds on power-up and arming

DroneCAN Variant Setup

Setting Up with Ardupilot Firmware

Connection

  1. Connect the Orbit EVO to the CAN1 or CAN2 port on the flight controller using the 4-pin CAN cable
  2. If multiple CAN devices are used, connect them in a daisy-chain configuration
  3. Ensure the CAN bus is properly terminated (120Ω termination resistors at both ends)

Power and Configuration

  1. Power the flight controller and connect it to Mission Planner
  2. Navigate to Config/Tuning > Full Parameter List
  3. Set the following parameters for CAN1 (or CAN2):
    • CAN_D1_PROTOCOL: Set to 1 (DroneCAN)
    • CAN_P1_DRIVER: Set to 1 (First driver)
    • GPS_TYPE: Set to 9 (DroneCAN)
    • COMPASS_TYPEMASK: Ensure DroneCAN compass is not masked

Node Configuration

The Orbit EVO will automatically:

  • Acquire a unique node ID via dynamic allocation
  • Register GPS, Compass, Safety Switch, and Buzzer services
  • Begin transmitting navigation data

Completing Setup

  1. Click Write Params in Mission Planner after modifying the parameters
  2. Reboot the flight controller
  3. Navigate to Setup > Optional Hardware > DroneCAN/UAVCAN
  4. Click Search to detect the Orbit EVO node
  5. Verify the node appears with:
    • GPS data streaming
    • Compass readings
    • Safety switch status
    • Buzzer operational
  6. Check the Flight Data screen for GPS lock and satellite count

Setting Up with PX4 Firmware

Firmware and Connection

  1. Load the PX4 firmware onto the autopilot
  2. Connect the Orbit EVO to the CAN1 or CAN2 port using the 4-pin CAN cable
  3. Ensure proper CAN bus termination (120Ω resistors)

Configuration

  1. Connect the flight controller to QGroundControl
  2. Navigate to Vehicle Setup > Parameters
  3. Set the following parameters:
    • UAVCAN_ENABLE: Set to 2 (Sensors Automatic Config)
    • UAVCAN_NODE_ID: Auto-assigned (leave default)
    • GPS_1_PROTOCOL: Set to 6 (UAVCAN)

Node Discovery

The Orbit EVO will automatically:

  • Register on the CAN bus
  • Provide GPS, Compass, Safety, and Buzzer services
  • Begin streaming telemetry data

Completing Setup

  1. Reboot the flight controller to apply the changes
  2. The Orbit EVO will be automatically detected and configured
  3. Verify the connection by checking:
    • Node appears in Vehicle Setup > Parameters > UAVCAN
    • GPS status shows valid position fix
    • Compass data is available
    • Safety switch controls arming (Red = Disarmed, Green = Armed)
    • Buzzer provides audible alerts
    • Satellite count is displayed

Connector Type Comparison

FeatureType 1: 6-Pin JSTType 2: 10-Pin GPS1
Cable Count3 cables (GPS + Safety + Buzzer)Single cable
InstallationMore flexible routingCleaner, single-plug
CompatibilityUniversal - any flight controllerPixhawk GPS1 port standard
Ideal ForCustom builds, flexible routingPlug-and-play Pixhawk systems

LED Status Reference

LEDColorStatusMeaning
PowerGreenSolidModule powered
PPSBlue1Hz BlinkGPS 3D fix acquired
SafetyRedSolidVehicle disarmed (safe)
SafetyGreenSolidVehicle armed (ready to fly)

Buzzer Alert Reference

Alert PatternMeaning
Single beep on power-upSystem initialization
Two short beepsGPS fix acquired
Three short beepsArmed confirmation
Continuous toneCritical warning/failsafe
Repeating patternPre-arm check failure

Troubleshooting

No GPS Fix:

  • Check antenna connection
  • Ensure clear sky view
  • Verify correct baud rate (UART) or CAN parameters (DroneCAN)

No Compass Detection:

  • Type 1: Verify I2C wiring (SDA/SCL on pins 4 & 5)
  • Type 2: Check 10-pin connector is fully seated
  • DroneCAN: Check node is detected in CAN device list

Safety Switch Not Working:

  • Type 1: Verify safety switch cable connection to flight controller
  • Type 2: Check pin 6 and 7 connections on 10-pin connector
  • DroneCAN: Check safety switch status in telemetry
  • Ensure safety is enabled in parameters (BRD_SAFETY_DEFLT = 1 or CBRK_IO_SAFETY = 0)

No Buzzer Sounds:

  • Type 1: Verify buzzer cable connection to flight controller buzzer port
  • Type 2: Check pin 9 connection on 10-pin connector
  • DroneCAN: Check CAN bus connection and node status
  • Verify buzzer is not disabled in parameters