The Hargrave ARINC825 Protocol implements a set of functions to control Hargrave Technologies devices over CAN Bus. This protocol is compliant with the ARINC825-4 specification (2018) on CAN 2.0B systems.

This documentation is specifically for the Hargrave ARINC825-4 V1 protocol; compatibility across versions is not guaranteed, please consult the correct documentation for the version of Hargrave ARINC825 on your device.

CAN interfaces need to be compliant with CAN 2.0B with 29-bit extended identifiers. All commands and ids are specified through the 29bit extended CAN identifier. The CAN data is truncated to the length of the payload.

All CAN frame payloads are a maximum of 8-bytes. If fewer than 8 bytes are specified for the payload then the payload should be truncated to that length.

All nodes on the CAN bus must have a unique 7-bit Server ID (SID), from 1 - 127, to be uniquely addressed.

To use ARINC825 on a supported device ensure that the CAN Protocol setting is set to ‘ARINC825’. The device ARINC SID must be set to a unique value for each device on the bus. Telemetry rates should also be configured to system requirements. All other ARINC settings can remain at default values. Advanced users should consult the documentation specific to their product for a complete list of configuration options and their functions.

For users that are unfamiliar with the ARINC 825 specification and wish to implement the Hargrave ARINC 825 message set in a CAN 2.0B system, refer to the below basic guide.

For users that are already familiar with the ARINC 825 specification and wish to integrate a Hargrave Device into an existing ARINC 825 CAN 2.0B system, refer to the below advanced guide

Control and Telemetry handling within the Hargrave ARINC 825 message set can be found below.

The Hargrave ARINC 825 message set includes a series of custom node services for device configuration and configuration validation, as shown in the below page.

Hargrave ARINC Home