LogoLogo
  • Welcome
  • Vehicle Operation
    • Getting started
    • Auterion Suite
      • Dashboard
      • Fleet Management
        • Vehicles
          • Cloud Features
          • Groups
        • Flights
        • Compliance
      • Manufacturer
        • Service Bulletins
      • Administration
      • User Management
      • Simulations
    • Auterion Mission Control
      • Installation
      • First steps
      • UI Breakdown
        • Navigating between the views
        • Fly View
          • Fly View UI Overview
          • Vehicle status indicator
          • Flight mode selector
          • Quick actions sidebar
          • Connection manager
          • Vehicle Dashboard
          • Flight Map
          • Camera View
          • Monitoring the Flight
          • Flying Manually (RC/Joystick)
          • Flying a Mission
        • Plan View
          • Plan UI Overview
          • Plan tools
            • Mission Menu
            • Waypoint Missions
            • Survey Patterns
              • Area Survey
              • Corridor Scan
          • Mission Summary
          • Mission Editor Tab
            • Start Section
            • Mission Section
            • End Section
            • Extras
          • Terrain visualization
          • GeoFence
          • Rally Points
        • Quick Vehicle Menu
          • Pre-Flight Checklist
          • Connectivity
        • Photo Gallery
        • Settings
        • Pilot Login
      • Useful resources
        • Mission Planning
          • Mission Cloud Sync
          • Terrain Following
          • Import Geo-Awareness data or KML overlays
        • Maps and Custom Overlays
          • Using Offline Maps
          • Importing GeoPDF overlays
        • Track GCS as Smart Asset in Suite
        • Live PX4 Log Streaming
        • Monitor Local Flights with ADS-B
        • GPS Denied Workflow
        • Windows Crash Logs Analysis
        • Screen Recordings
    • Remote Controllers
      • Skynav Remote Controller
        • Installing Mission Control
        • Joystick and Button Mapping
        • Using LTE for Online Maps in the Field
        • Advanced Radio Settings
        • Drop Guards and Chest Strap
        • Unit Serial Number
    • Settings & Maintenance
      • Vehicle Setup
      • WiFi Setup
      • Compass Calibration
      • Safety Setup
      • Joystick Setup
      • Vehicle Web UI
      • Software Update
      • Remote ID
        • How Remote ID works
        • Remote ID indicators in AMC
        • Frequently Asked Questions
    • Precise Flight
  • App development
    • Getting Started
      • Development environment Setup
      • Connecting to a device
      • Application Development
    • App Framework
      • Building your First App
      • Apps API
      • Sensor Data
      • Video Streams
      • Photos
      • Hardware Peripherals
      • Persistent Storage
      • MAVLink
      • Native Docker Compose
      • App Parameters
      • Log App Data to Auterion Suite
        • How to log Time Series Data
        • How to log basic Text Output
      • How to store an App's Binary Data on Skynode
      • User Web Interfaces
      • Build Arguments
      • Debugging apps with SSH
      • Debugging Apps with gdb
      • PX4 Messages in ROS 2
      • DDS / ROS2 Configuration
      • Structuring Applications with Multiple Services
    • Auterion SDK
      • Installation
      • Write Your First App
      • SDK API
      • Flight Mode API
        • Flight Mode API
        • Dynamics in Body Frame
        • Dynamics in Local Frame
        • Go-To in Local Frame
      • System State API
      • Peripheral Actuator Control API
      • Camera API
      • Navigation Input API
        • Global Navigation
        • Local Navigation
      • Visual Tracking API
    • Simulation
      • Virtual Skynode
        • Simulation-Gazebo Reference
        • Simulation-AirSim Reference
        • Connecting from other Computers
        • Resetting Virtual Skynode
        • Multiple Virtual Skynodes on single machine
      • Physical Skynode
    • Resources
      • Cross Compilation - Faster Builds
      • Auterion CLI Reference
      • Troubleshooting
      • App Tutorial
      • Skynode Vision Kit S
        • Set up the Vision Kit
        • Install and test a simple vision app
    • Legacy app workflow
      • App Development
      • MAVLink
      • Using the App Template
      • Example Applications
        • Autopilot Telemetry (C++)
        • Autopilot Telemetry (Python)
        • Photo Gallery
  • Hardware Integration
    • Getting started
      • Required Sensors
      • Wiring Skynode to the Vehicle
      • Actuators Setup
      • Sensors Setup
        • Set Orientations
        • Compass Calibration
        • Gyroscope calibration
        • Accelerometer calibration
        • Level horizon calibration
        • Airspeed calibration
      • Bench Test
      • Tuning
      • Creating Airframe Configurations for APX4
    • Skynode
      • Skynode X
      • Skynode ENT/GOV
      • Skynode X Integration and Development Kit
        • Get Skynode ready
        • Power Skynode
        • Register Skynode
        • Connect Skynode to AMC
        • Sensors and Peripherals
        • Next steps
      • Payloads
        • Generic USB Webcams (UVC)
        • Workswell Wiris Pro
        • Trillium HD40-LV
        • NextVision Gimbals (with TRIP2)
        • Sony Alpha a7R IV
        • Phase One iXM-100
        • Gremsy Gimbals
      • Connectivity
        • USB-C Network Connection
        • WiFi
        • LTE Setup
        • SIYI MK15
        • Microhard Data Link
        • Data Link Wiring
        • Silvus Data Link
        • Doodle Labs Data Link
        • Custom Data Link
        • Ethernet Interface Configuration
      • Skynode LED Meanings
      • Troubleshooting
      • Legacy DSM/DSMX Support
      • Peripherals
        • Power Module
        • 12S Power Module
        • Pixhawk Adapter Board
        • Pixhawk Payload Bus
        • Data Link Module
        • PX4 F9P GPS
        • Freefly RTK GPS
        • Airspeed Sensor
        • LIDAR
        • USB camera
        • See3CAM_24CUG
    • Skynode S
      • Datasheet
      • Interfaces
      • Basic Vehicle Integration
      • Add LTE to Skynode S
      • Skynode S LED status indicator
      • Skynode S flight logs
    • AI Node
      • Datasheet
      • Evaluation Kit
        • Power AI Node
        • Wiring AI Node to Skynode
        • Internet sharing with Skynode
        • Activate AI Node on Suite
      • Dimensions and CAD model
      • Interfaces
      • Connectivity
        • USB Network Connection
        • Serial Debug Connection
        • AI Node as Network Bridge
        • Standalone Internet Access
      • Updating AuterionOS
    • Advanced Airframe Integration
      • Custom power setup
      • Wiring without Breakout Boards
      • Gripper Integration
        • Setting up Payload Delivery with Gripper
      • ESC Calibration
      • Camera Calibration
        • Camera Calibration on a Computer
        • Camera Calibration on Skynode
      • Serial Port Configuration
    • Flight controller customization
      • AMC's Advanced Mode
      • Flight Controller Shell
      • Micro XRCE-DDS
    • AuterionOS Customization
      • OEM Tools Installation
      • Adding SSH keys
      • Changing the Root Password
      • Modifying Environment Variables
      • Pre-install Applications
      • Suite Manufacturer Tools
    • AuterionOS System Guide
      • Introduction
      • Flashing PX4 Binary and Vehicle Config
      • Building and Flashing PX4 Firmware
      • SSH Access
      • Filesystem and partitions
      • Environment Variables Reference
      • Types of AuterionOS Images
      • Mavlink Routing and Endpoints
      • Packaging AuterionOS Image
    • Additional Resources
      • Remote ID
        • How Remote ID works
        • Vehicle Serial Number
        • Communication Diagram
        • Remote ID configuration
        • How Auterion tested
      • Auto-Tuning
  • Release Notes
    • APX4
      • APX4 3.2
        • APX4 3.2.1
      • APX4 3.1
        • APX4 3.1.1
        • APX4 3.1.0
      • APX4 3.0
        • APX4 3.0.8
        • APX4 3.0.5
      • APX4 2.7
        • APX4 2.7.37
        • APX4 2.7.25
        • APX4 2.7.20
        • APX4 2.7.12
        • APX4 2.7.7
        • APX4 2.7.6
      • APX4 2.6
        • APX4 2.6.1
      • APX4 2.5
        • APX4 2.5.14
        • APX4 2.5.13
        • APX4 2.5.8
        • APX4 2.5.7
        • APX4 2.5.5
        • APX4 2.5.4
        • APX4 2.5.0
      • APX4 2.4
        • APX4 2.4.2
        • APX4 2.4.1
      • APX4 2.3
        • APX4 2.3.0
      • APX4 2.2
        • APX4 2.2.2
        • APX4 2.2.0
      • APX4 2.1
        • APX4 2.1.1
        • APX4 2.1.0
      • APX4 2.0
        • APX4 2.0.2
        • APX4 2.0.0
    • AuterionOS
      • AOS for AI Node
        • AI Node AOS 1.1.0
        • AI Node AOS 1.0.2
        • AI Node AOS 1.0.0
        • AI Node AOS 0.7.0
        • AI Node AOS 0.6.1
        • AI Node AOS 0.6.0
        • AI Node AOS 0.5.0
        • AI Node AOS 0.4.0
      • AOS for Skynode
        • AOS 3.7
          • AOS 3.7.14
          • AOS 3.7.9
        • AOS 3.6
          • AOS 3.6.14
        • AOS 3.5
          • AOS 3.5.13
        • AOS 3.3
          • AOS 3.3.9
        • AOS 3.2
          • AOS 3.2.9
        • AOS 2.19
          • AOS 2.19.14
        • AOS 2.15
          • AOS 2.15.10
          • AOS 2.15.7
        • AOS 2.12
          • AOS 2.12.8
        • AOS 2.10
          • AOS 2.10.2
        • AOS 2.8
          • AOS 2.8.1
        • AOS 2.7
          • AOS 2.7.15
        • AOS 2.6
          • AOS 2.6.1
        • AOS 2.5
          • AOS 2.5.14
          • AOS 2.5.13
          • AOS 2.5.8
          • AOS 2.5.7
          • AOS 2.5.5
          • AOS 2.5.4
          • AOS 2.5.0
        • AOS 2.4
          • AOS 2.4.1
        • AOS 2.3
          • AOS 2.3.0
        • AOS 2.2
          • AOS 2.2.2
          • AOS 2.2.0
        • AOS 2.1
          • AOS 2.1.1
          • AOS 2.1.0
        • AOS 2.0
          • AOS 2.0.2
          • AOS 2.0.0
    • Auterion Mission Control
      • AMC 1.34
        • AMC 1.34.19
        • AMC 1.34.14
      • AMC 1.33
        • AMC 1.33.13
      • AMC 1.32
        • AMC 1.32.7
      • AMC 1.30
        • AMC 1.30.17
      • AMC 1.29
        • AMC 1.29.7
      • AMC 1.26
        • AMC 1.26.8
      • AMC 1.22
        • AMC 1.22.3
      • AMC 1.19
        • AMC 1.19.5
      • AMC 1.18
        • AMC 1.18.3-1
        • AMC 1.18.3
      • AMC 1.17
        • AMC 1.17.10
        • AMC 1.17.9
      • AMC 1.15
        • AMC 1.15.0
      • AMC 1.14
        • AMC 1.14.6
        • AMC 1.14.0
      • AMC 1.13
      • AMC 1.12
      • AMC 1.11
      • AMC 1.10
        • AMC 1.10.1
        • AMC 1.10.0
      • AMC 1.9
        • AMC 1.9.1
        • AMC 1.9.0
      • AMC 1.8
    • Hardware
      • Skynode Rev 11 (Jan 2022)
Powered by GitBook
On this page
  • Connector Locations
  • Power Domains and Limits
  • Schematic
  • Connectors
  • Pinouts
  • Telem 1 (J12)
  • GPS 1(J13)
  • CAN 1 (J14)
  • FMU - ESC and Servo (J15)
  • SBUS RC (J16)
  • I2C 1 (J18)
  • SBUS OUT (J22)
  • GPS 2 (J23)
  • SPI (J24)
  • IO - ESC and Servo (J25)
  • Telem 3 (J26)
  • CAN 2 (J27)
  • I2C 2 (J28)
  1. Hardware Integration
  2. Skynode
  3. Peripherals

Pixhawk Adapter Board

Previous12S Power ModuleNextPixhawk Payload Bus

Last updated 4 days ago

The Pixhawk adapter board is used to break out the Skynode flight control interfaces on J3 and J4 to connectors and pinouts compatible to the .

The voltage levels for all signals brought out from the FMU to the Pixhawk Adapter Board are either 5V or 3.3V compliant. Refer to the below to check the voltage levels of specific pins. Exceeding these voltages will permanently damage the Flight Management Unit inside Skynode.

Connector Locations

Power Domains and Limits

Power Rail
Total Current Limit
Powered Connectors

VDD_5V_PERIPH

1.5A

SPI, TELEM3, GPS2, CAN2, I2C2

VDD_5V_HIPOWER

1A

TELEM1

VDD_5V_CAN1_GPS1

0.45A

GPS1, CAN1, I2C1

VDD_5V_SBUS_RC

0.25A

SBUS RC

VDD_SERVO

Must be externally provided!

FMU, IO

Schematic

Connectors

ID

Name

Connector

Description

J11

Primary

Molex Pico-Clasp 5015714007

Connect to Skynode Primary (J4)

J12

Telem 1

JST GH 6-pin

SM06B-GHS-TB

J13

GPS 1

JST GH 10-pin

SM10B-GHS-TB

(until rev 5 included) JST GH 11-pin

SM11B-GHS-TB (from rev 6 included)

Primary GPS with external compass, safety switch and led

J14

CAN 1

JST GH 4-pin

SM04B-GHS-TB

J15

FMU

Pin Header

TSW-108-08-G-T-RA

PWM channels from FMU, input capable

J16

SBUS RC

JST GH 3-pin

SM03B-GHS-TB

SBUS protocol RC input

J18

I2C 1

JST GH 4-pin

SM04B-GHS-TB

ID

Name

Connector

Description

J21

Secondary

Molex Pico-Claspre team is looki 5015714007

Connect to Skynode Secondary (J3)

J22

SBUS OUT

JST GH 3-pin

SM03B-GHS-TB

SBUS output

J23

GPS 2

JST GH 6-pin

SM06B-GHS-TB

Redundant GPS

J24

SPI

JST GH 11-pin

SM11B-GHS-TB

J25

IO

Pin Header

TSW-108-08-G-T-RA

PWM channels from IO

J26

Telem 3

JST GH 6-pin

SM06B-GHS-TB

J27

CAN 2

JST GH 4-pin

SM04B-GHS-TB

J28

I2C 2

JST GH 4-pin

SM04B-GHS-TB

Pinouts

Telem 1 (J12)

Pin

Name

Dir

Lvl

Function

1

VDD_5V_HIPOWER

5V

5V supply for peripherals, max. 1.0A (fused)

2

UART7_TX

OUT

3.3V

Telem 1 TX

3

UART7_RX

IN

3.3V

Telem 1 RX

4

UART7_CTS

IN

3.3V

Telem 1 CTS

5

UART7_RTS

OUT

3.3V

Telem 1 RTS

6

GND

Ground

GPS 1(J13)

Pin

Name

Dir

Lvl

Function

1

VDD_5V_CAN1_GPS1

5V

5V supply for primary GPS and CAN interface

2

USART1_TX

OUT

3.3V

GPS 1 TX

3

USART1_RX

IN

3.3V

GPS 1 RX

4

I2C1_SCL

I/O

3.3V

I2C SCL for external magnetometer

5

I2C1_SDA

I/O

3.3V

I2C SDA for external magnetometer

6

GPS_PPS

IN

3.3V

PPS signal from GPS module

7

FMU_IO_SAFETY_SWITCH_IN

IN

3.3V

Safety switch state input

8

FMU_IO_nSAFETY_SWITCH_LED_OUT

OUT

3.3V

Safety switch led output

9

FMU_VDD_3V3

OUT

3.3V

3.3V supply for peripherals, max 50mA

10

BUZZER_1_INV

OUT

Buzzer output (open drain)

11

GND

Ground

I2C lines are pulled up with 1kΩ in Skynode. External pull up resistors shall not be added.

CAN 1 (J14)

Pin

Name

Dir

Lvl

Function

1

VDD_5V_CAN1_GPS1

5V

5V supply for primary GPS and CAN interface

2

CAN1_P

I/O

CAN-H

FMU CAN 1

3

CAN1_N

I/O

CAN-L

FMU CAN 1

6

GND

Ground

FMU - ESC and Servo (J15)

Pin

Name

Dir

Lvl

PWM/

OneShot

DShot

Shared with PPB

1

FMU_CH1

I/O

3.3V

Yes

Yes

2

FMU_CH2

I/O

3.3V

Yes

Yes

3

FMU_CH3

I/O

3.3V

Yes

Yes

4

FMU_CH4

I/O

3.3V

Yes

Yes

5

FMU_CH5

I/O

3.3V

Yes

Yes

6

FMU_CH6

I/O

3.3V

Yes

Yes

7

FMU_CH7

I/O

3.3V

Yes

Yes

8

FMU_CH8

I/O

3.3V

Yes

Yes

SBUS RC (J16)

Pin

Name

Dir

Lvl

Function

1

VDD_5V_SBUS_RC

5V

5V supply for RC receiver, max 250mA

2

IO_SBUS_INPUT

IN

3.3V

SBUS protocol RC input

3

GND

Ground

I2C 1 (J18)

Pin

Name

Dir

Lvl

Function

1

VDD_5V_CAN1_GPS1

5V

5V supply for primary GPS and CAN interface

2

I2C1_SCL

I/O

3.3V

I2C SCL for external peripherals

3

I2C1_SDA

I/O

3.3V

I2C SDA for external peripherals

6

GND

Ground

I2C lines are pulled up with 1kΩ in Skynode. External pull up resistors shall not be added.

SBUS OUT (J22)

Pin

Name

Dir

Lvl

Function

1

VDD_5V_SBUS_RC

Not connected

2

IO_SBUS_OUTPUT

OUT

3.3V

SBUS protocol output

3

GND

Ground

GPS 2 (J23)

Pin

Name

Dir

Lvl

Function

1

VDD_5V_PERIPH

5V

5V supply for peripherals

2

USART8_TX

OUT

3.3V

GPS 2 TX

3

USART8_RX

IN

3.3V

GPS 2 RX

4

I2C2_SCL

I/O

3.3V

I2C SCL for external magnetometer

5

I2C2_SDA

I/O

3.3V

I2C SDA for external magnetometer

6

GND

Ground

I2C lines are pulled up with 1kΩ in Skynode. External pull up resistors shall not be added.

SPI (J24)

Pin

Name

Dir

Lvl

Function

1

VDD_5V_PERIPH

2

SPI6_SCK

OUT

3.3V

SPI Clock

3

SPI6_MISO

IN

3.3V

SPI MISO

4

SPI6_MOSI

OUT

3.3V

SPI MOSI

5

SPI6_nCS1

OUT

3.3V

Chip select 1

6

NC

7

SPI6_nSYNC

OUT

3.3V

Sync signal

8

SPI6_DRDY1

IN

3.3V

Data ready 1

9

NC

10

SPI6_nRESET

OUT

3.3V

Reset

11

GND

IO - ESC and Servo (J25)

Pin

Name

Dir

Lvl

PWM/

OneShot

DShot

Shared with

PPB

1

IO_CH1

OUT

3.3V

Yes

2

IO_CH2

OUT

3.3V

Yes

3

IO_CH3

OUT

3.3V

Yes

4

IO_CH4

OUT

3.3V

Yes

5

IO_CH5

OUT

3.3V

Yes

6

IO_CH6

OUT

3.3V

Yes

7

IO_CH7

OUT

3.3V

Yes

8

IO_CH8

OUT

3.3V

Yes

Telem 3 (J26)

Pin

Name

Dir

Lvl

Function

1

VDD_5V_PERIPH

5V

5V supply for peripherals

2

USART2_TX

OUT

3.3V

Telem 3 TX

3

USART2_RX

IN

3.3V

Telem 3 RX

4

NC

5

NC

6

GND

Ground

CAN 2 (J27)

Pin

Name

Dir

Lvl

Function

1

VDD_5V_PERIPH

5V

5V supply for peripherals

2

CAN2_P

I/O

CAN-H

FMU CAN 2

3

CAN2_N

I/O

CAN-L

FMU CAN 2

6

GND

Ground

I2C 2 (J28)

Pin

Name

Dir

Lvl

Function

1

VDD_5V_PERIPH

5V

5V supply for peripherals

2

I2C2_SCL

I/O

3.3V

I2C SCL for external peripherals

3

I2C2_SDA

I/O

3.3V

I2C SDA for external peripherals

6

GND

Ground

I2C lines are pulled up with 1kΩ in Skynode. External pull up resistors shall not be added.

Take a look at the for details about the changes.

The highlighted pin 6 was added in rev 6 of the Pixhawk Adapter Board, to ensure compatibility with the PX4 F9P GPS module. For backwards compatibility with the , a custom cable needs to be made.

CAN bus termination on Skynode changed in RC11. Prior to , Skynode has a 120Ω bus termination resistor inside, with no CAN termination on the Pixhawk Adapter Boards (until rev 5 included). This configuration assumed that Skynode was at the end of the bus. Rev 11 and onwards has the 120Ω bus termination resistor on the Pixhawk Adapter Boards (from rev 6 included), without built-in termination inside of Skynode. When designing instead of using the Pixhawk Adapter Boards, usage of 120Ω termination resistors at both ends of the bus is mandatory, following ISO 11898..

CAN bus termination on Skynode changed in RC11. Prior to , Skynode has a 120Ω bus termination resistor inside, with no CAN termination on the Pixhawk Adapter Boards (until rev 5 included). This configuration assumed that Skynode was at the end of the bus. Rev 11 and onwards has the 120Ω bus termination resistor on the Pixhawk Adapter Boards (from rev 6 included), without built-in termination inside of Skynode. When designing instead of using the Pixhawk Adapter Boards, usage of 120Ω termination resistors at both ends of the bus is mandatory, following ISO 11898.

Freefly RTK GPS module
Pixhawk-standard
table
a wire harness
a wire harness
rev 11
rev 11
Skynode Harwdare Revision 11 release notes
169KB
Pixhawk-Adapter-Board_RC05.pdf
pdf
Pixhawk Adapter RC05
181KB
Pixhawk-Adapter-Board_RC06.pdf
pdf
Pixhawk Adapter RC06
407KB
Pixhawk-Adapter-Board_RC07.pdf
pdf
Pixhawk Adapter RC07
1MB
Pixhawk Adapter Board.stl
3D model mockup