ARINC 429 Interface Concepts

Rob58

Rob58

Pre-takeoff checklist
Joined
Feb 20, 2016
Messages
369
Display Name
Display name:
Rob
The ARINC 429 interface seems to be an important component of any modern panel, thus the presence of the Garmin GAD 29B. I'm interested in understanding more about how this interface works, where it is typically used and what functionality it provides. I'm sure we have plenty of gurus here so any and all feedback is appreciated!
 
The ARINC 429 output is the format that modern navigators send steering commands to EFIS screens and auto pilots. It is used to give hsi needles and glideslope needles from GPS and Nav radios. It also gives anticipation of turns in a flight plan. I don’t know details of how the language works, but it’s the only way to get vertical steering and turn anticipation on modern efises and digital auto pilots.
 
Very helpful explanation and the AIM document is perfect (I have yet to read through it). Do I understand correctly that through this interface multiple devices can receive the same data? Thanks
 
Really appreciate all of the feedback - reference documents are very informative resources. Thanks very much!

PS - Martin, really sad that I missed your LOP seminar at OSH. Is this something that you will be posting on your youtube channel?
 
We use Arinc 429 for talking between electronic boxes on every aircraft I've ever worked on. Thats small turboprops up to widebodies. Some examples that I've worked with:
  • the data to draw the flight plan map on the mfd
  • inertial data from the gyros
  • air data from air data computers
  • pilot inputs (sidestick, rudder pedal or yoke/column) to the fly by wire system
  • autopilot commands to the AP servos
Each 429 bus is just 2 wires, so its pretty simple. Each bus has at most 1 transmitter and possibly many receivers. The datagrams are called "labels", much like you'd call what goes over ethernet a "packet". Labels each are assigned a unique ID per bus, I think its 8 bit so 0-255. So for example coming from the air data computers, label 74 might be True Airspeed, label 116 might be Static Pressure, and maybe 206 is Pressure Altitude.

There are a couple reserved fields on each label, parity SSM and SDI. Parity helps tell if the datagram was mangled during transmission. Sometimes for critical stuff we do even more checking than just parity. SSM is a way for the sender to tell you if they are in come kind of built in test mode, or if it can't output a value right now (think of a radio altimiter at cruise altitude), or Norm Op if everything is ok. SDI is used when there are multiple copies of the same data label on a bus. SDI is used to distinguish between them.
 
Z06, these are some great details - thank you. It's not my intention to become an expert, rather to have a solid working understanding of the basics. I'll probably have more questions as I get further into this. Thanks again.
 
You must log in or register to reply here.
Back
Top