ARINC Advanced Guide

this advanced guide is intended 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 this advanced guide will cover details regarding the way the hargrave arinc specification implements the arinc 825 4 specification this guide contains sub sections for each of the lccs that are implemented normal operating channel (noc) all control and telemetry are broadcast on the noc use one to many identifiers the traditional 14bit arinc 825 data object codes (doc) are broken up into two separate sections following msb 7 bit controller function code (cfc) used for identifying the packet function 7 bit controller identifier (cid) used for identifying controllers and/or controller groups the controller identifier (cid) is the device server identifier (sid) for directed messages or the group identifier (group cid) for broadcast message, which will target a range of sid values server identifiers are pre configured via device settings between 1 127 the multicast sid of 0 will be ignored for motor controllers the function code identifier (fid) is defaulted to 11 engine controls, however this is configurable in device settings noc identifier structure control and telemetry messages all control and telemetry messages are transmitted on the noc details about the control and telemetry message set can be found at the below link node service channel (nsc) all messages implemented on the node service channel use peer to peer can identifiers standard node services the following standard node services are implemented true left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type custom node services the following link details the custom node services that are implemented test and maintenance channel (tmc) all messages implemented on the test and maintenance channel use peer to peer can identifiers periodic health status message (phsm) the periodic health status message (phsm) defined in arinc 825 is broadcast on the test and maintenance channel at 1hz by default, the smt bit is set indicating that this is arinc 825 4 the rate at which the phsm is broadcast can be configured in device settings hargrave protocol tunnel messages to facilitate use of the hargrave configurator with devices operating with arinc a series of tunnel messages have been implemented on the test and maintenance channel the content of these messages is opaque as indicated by the private (pvt) can id bit being set a device will only respond to tunnel messages from the pre configured tunnel fid by default this is the temporary test and maintenance fid of 127 setting the tunnel fid to 0 will disable the tunnel and the device will ignore private messages on the tmc the smt bit will be set depending on the direction of the message