UCANS32K1 family CAN node boards

This GitBook provides the technical details of the NXP RDDRONE-UCANS32K1 famly of CAN-FD and CAN-SIC boards with UAVCAN protocol support, as well as reference software and examples.

Also take a look at some of our other Gitbooks:

This GitBook is still a work in progress!

Note that the UCANS32K1SIC is the preferred board to use. The UCANS32K1SCT (Secure) is more advanced and will require accessing secure documentation from NXP DocStore to take advantage of the capability of the CAN PHYs

See also the NXP Mobile Robotics Community for questions and answers about all our mobile robotics reference designs. There is also thread for questions about UCANS32K148 and UCANS32K1SIC .

What are the UCANS32K1 node boards?

UCANS32K146 and UCANS32K1SIC development boards are general purpose CAN node reference designs. They can be used for any purpose, however specific software has been provided for drones, rovers and other small (autonomous) vehicles. This software allows it to act as a bridge between a CAN bus (with UAVCAN) and I2C, SPI, UART, GPIO or any other pin function of the S32K146 MCU (80 MHz ARM Cortex-M4F, ASIL-B compliant). This allows sensors, actuators and other peripherals to be controlled by other devices on the same CAN bus, such as the RDDRONE-FMUK66 flight management unit reference design.

The relevant part numbers are:

  • KIT-UCANS32K1SIC (complete development kit with two UCANS32KSIC boards, a debugger and an adapter board - everything you need to get started!)

  • UCANS32K1SIC (a single UCANS32K146 board, CAN cable and termination network board)

  • KIT-UCANS32K146 (complete development kit with two UCANS32K146 boards, a debugger and an adapter board - everything you need to get started!)

  • UCANS32K146-01 (a single UCANS32K146 board, without additional debugger)

Use cases

Possible use cases are:

  1. PWM output for motor controllers or servos

    • Relieves the FMU of creating RC-PWM signals

    • Can report information about the motors back to the FMU

  2. Battery management systems (also have a look at our BMS772 reference design!)

    • Report power consumption, state of charge, battery health and other faults to the FMU

  3. GPS

    • Allows for more than one GPS to be connected to the FMU by communicating GPS info over CAN

  4. Sensors

    • Airspeed/pressure sensors can report information to the FMU over CAN

  5. And many more

    • Remote lights, arming/safety switches, and really any other peripheral which needs to communicate with the FMU can be connected to the UCANS32K146 development board.

Board specifications

  • NXP S32K146 Automotive MCU (80 MHz ARM Cortex-M4F, ASIL-B compliant)

  • Dual NXP TJA1044 CAN transceivers

  • NXP EdgeLock SE050 secure element with NFC interface (with external antenna, not included)

  • One (UCANK1S32K146) or Two (UCANS32KSIC) RC-PWM pin header with optional external power input

  • Through-hole solder pads (for 0.100" pin headers) that expose SPI, I2C and UART. Can also be remapped to other pin functions (GPIO, ADC, timer, ...)

  • 5V power input; the board can be powered from the 4-pin JST-GH CAN connectors or the 2-pin power input header. There is an optional power input for the RC-PWM header as well specifically for 3 pin connected PWM devices such as high power RC servos.

More information is available on the NXP website.

Hardware designs and example software

The hardware schematics and board layout for UCANS32K146 are available on this GitBook and on the NXP website. We encourage you to create your own designs based on our UCANS32K146 board!

We do not only provide hardware designs, there is also plenty of example software available. There are multiple options to use the UAVCAN protocol. We have also worked with the Apache NuttX and PX4 Autopilot communities to enable their open source software projects on the UCANS32K146.

Additional designs and example software might be made available in the future.

Contribute to this GitBook

We would really like to receive your feedback regarding this GitBook. It is synchronized to a Git repository on GitHub, so you can just open an issue. If you want to contribute you can also open a pull request. The pages are written using an extended version of Markdown, so it should be pretty straightforward to add sections or even complete pages!

Last updated