UAVCAN Adapter Node

These allow existing ArduPilot supported peripheral to be adapted to the CAN bus as UAVCAN devices.

../_images/uavcan-node.jpg

They utilize the AP_Periph library to remotely locate existing ArduPilot drivers onto an STMF103 or STMF303 based device, translating UART,SPI, I2C, or GPIO-based peripheral devices supported by ArduPilot into UAVCAN devices on the CAN bus.

GPS adapted to UAVCAN

../_images/uavcan-node-gps.jpg

This provides an easy method to develop integrated UAVCAN peripherals which can be used with ArduPilot or other UAVCAN systems.

Firmware

Firmware is provided in the AP_Periph folder for several UAVCAN devices based on this concept including versions for a typical UAVCAN Adapter Node itself, manufactured by mRobotics.

../_images/mRo-can-node.jpg

The f103-GPS firmware enables its UART interface for GPS and provides I2C compass interface detection. The f103-ADSB firmware enables its UART for ADS-B Receiver attachment instead of GPS. The f103-RangeFinder firmware enables its UART for connection to a Rangefinder.

Schematic

Features

The AP_Periph firmware can be configured to enable a wide range of UAVCAN sensor types. Support is included for:

  • GPS modules (including RTK GPS)
  • Magnetometers (SPI or I2C)
  • Barometers (SPI or I2C)
  • Airspeed sensors (I2C)
  • Rangefinders (UART or I2C)
  • ADSB (Ping ADSB receiver on UART)
  • LEDs (GPIO, I2C or WS2812 serial)
  • Safety LED and Safety Switch
  • Buzzer (tonealarm or simple GPIO)

An AP_Periph UAVCAN firmware supports these UAVCAN features:

  • dynamic or static CAN node allocation
  • firmware upload
  • automatically generated bootloader
  • parameter storage in flash
  • easy bootloader update
  • high resiliance features using watchdog, CRC and board checks
  • firmware update via MissionPlanner or uavcan-gui-tool

Setup

Rangefinder

To use rangefinders, follow the instructions at UAVCAN Setup Advanced to set up the Ardupilot parameters. Using MissionPlanner or UAVCAN Gui, set the parameters on the adaptor node following the instructions for the relevant rangefinder.

Note

The orientation of the rangefinder (RNGFND1_ORIENT) must be set to 0 on the adaptor node.

Note

The RNGFNDx_ADDR Ardupilot parameter must be set to 0.