Skip to content

Commit a1a977d

Browse files
oliverHwurzburg
authored andcommitted
Micro CAN node docs
Add Beyond Robotix CAN node
1 parent 81793df commit a1a977d

File tree

3 files changed

+17
-13
lines changed

3 files changed

+17
-13
lines changed

common/source/docs/common-uavcan-adapter-node.rst

Lines changed: 16 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -16,21 +16,8 @@ These nodes allow existing ArduPilot supported peripherals to be adapted to the
1616

1717
They utilize the `AP_Periph <https://github.com/ArduPilot/ardupilot/tree/master/Tools/AP_Periph>`__ library to use existing ArduPilot drivers on a supported hardware board. Translating UART, SPI, I2C, or GPIO-based peripheral devices supported by ArduPilot into DroneCAN devices on the CAN bus or MSP.
1818

19-
For example, a serial GPS adapted to DroneCAN:
20-
21-
.. image:: ../../../images/uavcan-node-gps.jpg
22-
:width: 450px
23-
2419
This provides an easy method to develop integrated DroneCAN peripherals which can be used with ArduPilot or other systems that support DroneCAN.
2520

26-
The first adapter was manufactured by `mRobotics <https://store.mrobotics.io/product-p/mro10042.htm>`__, is shown below, and provides socketed outputs for a UART+I2C and another I2C connection, and solder pads for a second UART, SPI bus, GPIOs, and ADC inputs.
27-
28-
.. image:: ../../../images/mRo-can-node.jpg
29-
30-
The first generation was based on the f103 processor, while the current generation uses an f303 for more memory, allowing more peripheral options to be accommodated simultaneously in the firmware. The L431 processor is now supported, as well as any ArduPilot compatible autopilot can be adapted for use as a DroneCAN Adapter Node.
31-
32-
Developers might find the :ref:`AP_Periph section <dev:ap-peripheral-landing-page>` of the dev docs useful for more details about creating AP_Periph nodes.
33-
3421
Features
3522
========
3623
The AP_Periph DroneCAN firmware can be configured to enable a wide range of
@@ -62,6 +49,10 @@ The AP_Periph DroneCAN firmware supports these DroneCAN features:
6249
- High resilience features using watchdog, CRC, and board checks
6350
- Firmware update via MissionPlanner or DroneCAN-gui-tool
6451

52+
Developers
53+
========
54+
Developers might find the :ref:`AP_Periph section <dev:ap-peripheral-landing-page>` of the dev docs useful for more details about creating AP_Periph nodes.
55+
6556
Firmware
6657
========
6758
`Firmware <https://firmware.ardupilot.org/AP_Periph/>`__ is provided in the AP_Periph folder for supported DroneCAN devices as well as the conversion of some autopilots to DroneCAN adapter use. Currently, the following firmware is pre-built, but the code allows for easy customization. Firmware can be installed using either :ref:`DroneCAN GUI<common-uavcan-gui>` or :ref:`MissionPlanner SLCAN <planner:dronecan-uavcan-slcan>` when the device is attached to a DroneCAN port on an autopilot and the autopilot has that port enabled. See :ref:`common-uavcan-setup-advanced`. Since the size of all the ArduPilot driver libraries would exceed the smaller processors, several variations, supporting different peripheral sets, are provided.
@@ -129,9 +120,21 @@ DroneCAN Adapter Nodes
129120
Several devices are manufactured specifically for use as general-purpose adapter nodes:
130121

131122
- :ref:`ARK CANnode <common-ark-can-node>`
123+
- `Beyond Robotix Node <https://beyond-robotix.gitbook.io/docs/can-node-system>`_
132124
- `MatekL431 DroneCAN Adapter Node <http://www.mateksys.com/?portfolio=can-l431>`_
133125
- :ref:`mRo DroneCAN Adapter Node <common-mro-uavcan-adapter-node>`
134126

127+
128+
History
129+
======================
130+
131+
The first adapter was manufactured by `mRobotics <https://store.mrobotics.io/product-p/mro10042.htm>`__, is shown below, and provides socketed outputs for a UART+I2C and another I2C connection, and solder pads for a second UART, SPI bus, GPIOs, and ADC inputs.
132+
133+
.. image:: ../../../images/mRo-can-node.jpg
134+
135+
The first generation was based on the f103 processor, while the current generation uses an f303 for more memory, allowing more peripheral options to be accommodated simultaneously in the firmware. The L431 processor is now supported, as well as any ArduPilot compatible autopilot can be adapted for use as a DroneCAN Adapter Node.
136+
137+
135138
.. toctree::
136139
:hidden:
137140

common/source/docs/common-uavcan-peripherals.rst

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -48,6 +48,7 @@ Adapter Nodes
4848
:maxdepth: 1
4949

5050
ARK CANnode <common-ark-can-node>
51+
Beyond Robotix Node <https://beyond-robotix.gitbook.io/docs/can-node-system>
5152
Matek DroneCAN Adapter Node <https://www.mateksys.com/?portfolio=can-l431>
5253
mRo KitCAN CAN/DroneCAN Adapter Node+Compass+Baro <common-mro-kitcan>
5354
mRo DroneCAN Adapter Node <common-mro-uavcan-adapter-node>

images/uavcan-node.jpg

74.7 KB
Loading

0 commit comments

Comments
 (0)