Files
PX4-Autopilot/docs/en/dronecan/ark_flow_mr.md
Jacob Dahl 0524a374d9 fix(drivers/uavcannode): make CANNODE_NODE_ID the sole node ID policy (#27644)
* fix(drivers/uavcannode): make CANNODE_NODE_ID the sole node ID policy

The startup bootloader_app_shared_write() never reached the bootloader:
it only accepts App-signed data and invalidates the shared region on
every boot. The only consumer was uavcannode itself on a restart
without a reset (nsh stop/start), where the persisted bus_speed=0 made
the CAN driver init fail and left the node off the bus. The bootloader
learns our node ID exclusively through the firmware update handoff in
cb_beginfirmware_update, which already carries the static ID.

CANNODE_NODE_ID now overrides the bootloader handoff only when nonzero,
so the default (0) reuses the ID the bootloader already allocated
instead of running allocation a second time. The handoff is ignored
unless it carries a valid bitrate, healing regions poisoned by firmware
that wrote bus_speed=0. Max is 125 because 126/127 are reserved for
debug tools by DroneCAN convention, matching UAVCAN_NODE_ID.

Signed-off-by: Jacob Dahl <dahl.jakejacob@gmail.com>

* fix(drivers/uavcannode): harden bootloader handoff validation

Invalidate the shared region whenever it was read valid, not only when
the handoff is accepted, so stale data cannot linger on boards whose
bootloader never invalidates it. Require a plausible bitrate (the
CANNODE_BITRATE minimum) rather than nonzero: the canbootloader alt-app
update path can hand off bus_speed = CAN_UNDEFINED (999). Reword the
invalid-param error, which claimed dynamic allocation while keeping the
bootloader handoff.

Signed-off-by: Jacob Dahl <dahl.jakejacob@gmail.com>

---------

Signed-off-by: Jacob Dahl <dahl.jakejacob@gmail.com>
2026-07-16 20:43:22 -06:00

7.3 KiB

ARK Flow MR

ARK Flow MR ("Mid Range") is an open source DroneCAN optical flow, distance sensor, and IMU module. It is the next generation of the Ark Flow, designed for mid-range applications.

ARK Flow MR

Where to Buy

Order this module from:

Hardware Specifications

  • Open Source Schematic and BOM
  • Sensors
    • PixArt PAA3905 Optical Flow Sensor
      • Auto detection of challenging conditions, such as checker boards, stripes, glossy surface and yawing
      • Wide working range from 80mm up to infinity
      • Automatic switching of Operation Mode
      • 40mW IR LED built onto board for improved low light operation
    • Broadcom AFBR-S50LX85D Time-of-Flight Distance Sensor
      • Laser Opening Angle of 2° x 2°
      • Typical distance range up to 50m
      • Operation in up to 200 kilolux ambient light
      • Works well on all surface conditions
  • Invensense IIM-42653 6-Axis IMU
  • Two Pixhawk Standard CAN Connectors (4 Pin JST GH)
  • Pixhawk Standard Debug Connector (6 Pin JST SH)
  • Software controlled built-in CAN termination resistor via node parameter (CANNODE_TERM)
  • Small Form Factor
    • 3cm x 3cm x 1.4cm
  • LED Indicators
  • USA Built

Hardware Setup

Wiring

The ARK Flow MR is connected to the CAN bus using a Pixhawk standard 4 pin JST GH cable. For more information, refer to the CAN Wiring instructions.

Mounting

The recommended mounting orientation is with the connectors on the board pointing towards back of vehicle, as shown in the following picture.

ARK Flow MR align with Pixhawk

This corresponds to the default value (0) of the parameter SENS_FLOW_ROT. Change the parameter appropriately if using a different orientation.

The sensor can be mounted anywhere on the frame, but you will need to specify the focal point position, relative to vehicle centre of gravity, during PX4 configuration.

Firmware Setup

ARK Flow MR runs the PX4 DroneCAN Firmware. As such, it supports firmware update over the CAN bus and dynamic node allocation.

ARK Flow MR boards ship with recent firmware pre-installed, but if you want to build and flash the latest firmware yourself see PX4 DroneCAN Firmware > Building the Firmware.

  • Firmware target: ark_can-flow-mr_default
  • Bootloader target: ark_can-flow-mr_canbootloader

Flight Controller Setup

::: info The Ark Flow MR will not boot if there is no SD card in the flight controller when powered on. :::

Enable DroneCAN

The steps are:

Once enabled, the module will be detected on boot. Flow data should arrive at 100Hz. Distance sensor data should arrive at 40Hz.

DroneCAN configuration in PX4 is explained in more detail in DroneCAN > Enabling DroneCAN.

PX4 Configuration

You need to set the EKF optical flow parameters to enable fusing optical flow measurements for velocity calculation, set necessary DroneCAN parameters, and define offsets if the sensor is not centred within the vehicle.

Set the following parameters in QGroundControl:

Ark Flow MR Configuration

You may need to configure the following parameters on the ARK Flow MR itself:

Parameter Description
CANNODE_NODE_ID CAN node ID (0 for dynamic allocation). If set to 0 (default), dynamic node allocation is used. Set to 1-125 to use a static node ID.
CANNODE_TERM CAN built-in bus termination.

LED Meanings

  • Blinking green is normal operation
  • Rapid blinking blue and red is firmware update

If you see a solid red LED there is an error and you should check the following:

  • Make sure the flight controller has an SD card installed.
  • Make sure the Ark Flow MR has ark_can-flow-mr_canbootloader installed prior to flashing ark_can-flow-mr_default.
  • Remove binaries from the root and ufw directories of the SD card and try to build and flash again.

Video

PX4 holding position using the ARK Flow MR sensor for velocity estimation (in Position Mode).

See Also