7.0F IDU Communication Requirements
REVISION HISTORY FOLLOWS ON PAGE 2.
WARNING:
A printed copy of this document may not be the latest revision. It is the responsibility of the user
to ensure that the latest revision is used. The latest revision of this document may be printed from the Chelton
Flight Systems electronic document repository.
THIS DOCUMENT CONTAINS PROPRIETARY INFORMATION OF CHELTON FLIGHT SYSTEMS, A COBHAM AVIONICS AND
SURVEILLANCE COMPANY. NEITHER RECEIPT, NOR POSSESSION THEREOF, CONFERS ANY RIGHT TO REPRODUCE OR USE,
OR DISCLOSE, IN WHOLE OR IN PART, ANY SUCH INFORMATION WITHOUT WRITTEN AUTHORIZATION FROM CHELTON FLIGHT
SYSTEMS.
APPROVAL
AUTHOR
CHECK
QUALITY
COGNIZANT
COGNIZANT
COGNIZANT
RELEASE DATE:
Status
Draft
NAME
Rick Price
Sharmila Durairaj
Damon La Rue
PURPOSE:
This document serves as the
System Requirements Document
for the Communications
Requirements of Chelton Flight
Systems’ Integrated Display Units.
DOCUMENT NUMBER
REV
01-000028-070F
A
Typed signatures indicate approval. Handwritten or electronic
signature approval of this document is on file at S-TEC
Corporation/Chelton Flight Systems.
01-000028-070F
Chelton Flight Systems – Confidential
Page 1 of 104
REVISION RECORD
Rev
A
Notes
1. Replace 7.0E references with 7.0F references.
2. Clarify ARINC429 transmit label 117G SSM requirements.
\cr{EFIS,7.0F,00005}
Modified:
[SYS_COM_271]
See Revision Record in document 01-000028-070E for 7.0E
and previous releases.
01-000028-070F
Chelton Flight Systems – Confidential
Date
See Cover
Sheet
Author
R. Price
Page 2 of 104
TABLE OF CONTENTS
1
SCOPE .......................................................................................................................... 5
1.1
Document Identification and Overview ....................................................................... 5
1.2
Relationship to Other Documents .............................................................................. 5
2
APPLICABLE DOCUMENTS........................................................................................ 6
2.1
Chelton Flight Systems Documents ........................................................................... 6
2.2
Other Documents ....................................................................................................... 6
3
LIST OF ACRONYMS ................................................................................................... 8
4
SYSTEM OVERVIEW ................................................................................................. 10
5
SYSTEM REQUIREMENTS ........................................................................................ 11
5.1
Definitions and Overview .......................................................................................... 11
5.2 IDU Serial Communications ..................................................................................... 11
5.2.1 Intra-System Communications ........................................................................... 12
5.2.2 Inter-System Communications ........................................................................... 20
5.2.3 GPS .................................................................................................................... 23
5.2.4 AHRS .................................................................................................................. 31
5.2.5 ADC .................................................................................................................... 42
5.2.6 Fuel Flow ............................................................................................................ 45
5.2.7 Analog Interface ................................................................................................. 46
5.2.8 NAT Transponder ............................................................................................... 51
5.2.9 Navigation and Flight Plan Data Transmission .................................................. 52
5.2.10 Remote NAV and COM Tuning Data .............................................................. 54
5.2.11 ARINC 429 ...................................................................................................... 57
5.2.12 Goodrich WX-500 ............................................................................................ 70
5.2.13 Ryan TCAD ..................................................................................................... 72
5.2.14 Datalink ............................................................................................................ 74
5.2.15 Chelton Remote Bug Panel............................................................................. 76
5.2.16 HeliSAS Control Panel (HCP) ......................................................................... 80
5.2.17 Remote Keyboard Interface ............................................................................ 81
5.2.18 Weather Radar (IDU-450/680 Only) ............................................................... 82
5.2.19 ARINC 429 Expansion Module (IDU-450/680 Only) ....................................... 97
6
NOTES: ....................................................................................................................... 98
01-000028-070F
Chelton Flight Systems – Confidential
Page 3 of 104
APPENDIX A: STORMSCOPE WX-500 INTERFACE DEVELOPER’S GUIDE ............ 99
APPENDIX B: 9900 SERIES TCAD THIRD PARTY INTERFACE PROTOCOL............ 99
APPENDIX C: WSI INFLIGHT WEATHER INTERFACE CONTROL DOCUMENT ....... 99
APPENDIX D: GDL 90 DATA INTERFACE SPECIFICATION ....................................... 99
APPENDIX E: ALTIMETERS PROTOCOLS SPECIFICATION ...................................... 99
APPENDIX F: SYSTEM REQUIREMENTS DOCUMENT FOR ART 2000/2100 ........... 99
APPENDIX G: ARINC LABEL DETAILED DEFINITIONS ............................................ 100
01-000028-070F
Chelton Flight Systems – Confidential
Page 4 of 104
1
1.1
SCOPE
DOCUMENT IDENTIFICATION AND OVERVIEW
This IDU Communication Requirements Document generically specifies the
communication requirements for Chelton Flight Systems Integrated Display Units,
including IDU-Is, IDU-IIIs, IDU-680s and IDU-450s.
1.2
RELATIONSHIP TO OTHER DOCUMENTS
This document, in conjunction with listed references, is intended to be used to specify the
system requirements for Chelton Flight Systems Integrated Display Units.
01-000028-070F
Chelton Flight Systems – Confidential
Page 5 of 104
2
2.1
APPLICABLE DOCUMENTS
CHELTON FLIGHT SYSTEMS DOCUMENTS
Document Number
01-000021
01-000028-070F
01-000029-070F
01-000030-070F
01-000031-070F
01-000032-070F
01-000033-070F
01-000034-070F
01-000035-070F
01-000036-070F
01-000037-070F
01-000038-070F
01-000040-070F
01-000044
01-000045
01-000050-070F
01-000051-070F
20-000046
43-000122
9464-010
Document Title
IDU-680P System Requirements Document (SYRD)
7.0F IDU Communication Requirements
7.0F IDU SCC Card and Limits Requirements
7.0F IDU PFD Screen Requirements
7.0F IDU MFD Screen Requirements
7.0F IDU TAWS Requirements
7.0F IDU GPS/SBAS Requirements
7.0F IDU Flight Planner Requirements
7.0F IDU Initialization Requirements
7.0F IDU Warning System Requirements
7.0F IDU Menu System Requirements
7.0F IDU Reversionary Mode Requirements
7.0F IDU Agusta 109 Supplemental Requirements
IDU-III System Requirements Document (SYRD)
IDU-450 System Requirements Document (SYRD)
7.0F IDU TH-57D Supplemental Requirements
7.0F IDU Autopilot Interface Requirements
HeliSAS Software Requirements Document
IDU TSO Deviation Document
Weather Radar Module System Requirements Document
(SYRD)
ARINC 429 Expansion Module System Requirements Document
(SYRD)
9465-010
2.2
OTHER DOCUMENTS
Document Number
010-11501-001
06980SYRDXX.PS.AL
560-1058-00
ARINC 429-16
ARINC 453 (Draft 2)
ARINC 708-6
ARINC 735A-1
EIA-232D
EIA-422A
FAA AC 90-80B
FAA AIM
FAA Notice 8110.60
KPN 701-00506-0000
NMEA-0183
No Number
RTCA/DO-229D
TSO-C2d
01-000028-070F
Document Title
APPENDIX A: Stormscope WX-500 Interface Developer’s Guide
APPENDIX E: Altimeters Protocols Specification
APPENDIX D: GDL 90 Data Interface Specification
Mark 33 Digital Information Transfer System (DITS)
Very High Speed Data Bus
Airborne Weather Radar
Traffic Alert and Collision Avoidance System
Interface between Data Terminal Equipment and Data
Electrical Characteristics of Balanced Voltage Digital Interface
Circuits
Approval of Offshore Standard Approach Procedures, Airborne
Radar Approaches, and Helicopter En Route Descent Areas
Aeronautical Information Manual
GPS as a Primary Means of Navigation for Oceanic/Remote
Operations
APPENDIX F: System Requirements Document for ART
2000/2100
National Marine Electronics Association Interface Standard 0183
APPENDIX B: 9900 Series TCAD Third Party Interface Protocol
Minimum Operational Performance Standards for Global
Positioning System/Wide Area Augmentation System Airborne
Equipment
Airspeed Instruments
Chelton Flight Systems – Confidential
Page 6 of 104
Document Number
TSO-C3d
TSO-C4c
TSO-C6e
TSO-C8e
TSO-C10b
TSO-C44c
TSO-C63c
TSO-C106
TSO-C110a
TSO-C113
TSO-C118
TSO-C119b
TSO-145c
TSO-C146c
TSO-C147
WSI-AV300-002
01-000028-070F
Document Title
Turn and Slip Instruments
Bank and Pitch Instruments
Direction Instrument, Magnetic (Gyroscopically Stabilized)
Vertical Velocity Instruments (Rate-of-Climb)
Altimeter, Pressure Actuated, Sensitive Type
Fuel Flowmeters
Airborne Weather and Ground Mapping Pulsed Radars
Air Data Computer
Airborne Passive Thunderstorm Detection Equipment
Airborne Multipurpose Electronic Displays
Traffic Alert and Collision Avoidance System (TCAS) Airborne
Equipment, TCAS I
Traffic Alert and Collision Avoidance System (TCAS) Airborne
Equipment, TCAS II
Airborne Navigation Sensors Using the Global Positioning System
(GPS) Augmented by the Satellite Based Augmentation System
(SBAS)
Stand-Alone Airborne Navigation Equipment Using the Global
Positioning System (GPS) Augmented by the Satellite Based
Augmentation System (WAAS)
Traffic Advisory System (TAS) Airborne Equipment
APPENDIX C: WSI Inflight Weather Interface Control Document
Chelton Flight Systems – Confidential
Page 7 of 104
3
LIST OF ACRONYMS
The following acronyms may appear in this document:
AC
AD
ADF
A-D
ADAHRS
ADC
ADS-B
AFM
AGL
AHRS
AIRMET
AMLCD
ANSI
APV
ARINC
ARP
AS
ATA
ATC
CDI
CDTI
CDR
CFS
CM
COM
CPM
CPU
CR
CRC
DA
D-A
DAICD
DAR
DCN
DEM
DER
DH
DL
DME
DMIR
Advisory Circular
Airworthiness Directive
Automatic Direction Finder
Analog to Digital (converter)
Air Data Attitude Heading Reference System
Air Data Computer
Automatic Dependent Surveillance-Broadcast
Aircraft Flight Manual
Above Ground Level
Attitude Heading Reference System
Airmen’s Meteorological Information
Active Matrix Liquid Crystal Display
American National Standards Institute
Approach with Vertical Guidance
Aeronautical Radio, Inc.
SAE Aerospace Recommended Practice
SAE Aerospace Standard
AT Attachment (hard disk storage interface)
Air Traffic Control
Course Deviation Indicator
Cockpit Display of Traffic Information
Critical Design Review
Chelton Flight Systems
Configuration Management
Communication
Company Project Manager
Central Processing Unit
Change Request
Cyclic Redundancy Check
Decision Altitude
Digital to Analog (converter)
Digital Aeronautical Information CD
Designated Airworthiness Representative
Document Change Notice
Digital Elevation Model
Designated Engineer Representative
Decision Height
Data Link
Distance Measuring Equipment
Designated Manufacturing Inspection
Representative
DO
RTCA Document
DOD
Department of Defense
DOF
Digital Obstruction File
DP
Departure Procedure
DR
Dead Reckoning or Defect Report
DSP
Digital Signal Processing
EFIS
Electronic Flight Instrument System
EGPWS Enhanced Ground Proximity Warning System
EIA
Electronics Industry Association
EICAS
Engine Instrument and Crew Alerting System
ETA
Estimated Time of Arrival
ETE
Estimated Time Enroute
FAA
Federal Aviation Administration
FAF
Final Approach Fix
FAR
Federal Aviation Regulation
FAWP
Final Approach Waypoint - same as FAF
FDE
Fault Detection and Exclusion
FHA
Functional Hazard Analysis
FIFO
"First in, First out"
FIS
Flight Information Service
FIS-B
Flight Information Service-Broadcast
FL
Flight Level
FLTA
Forward Looking Terrain Awareness
FMEA
Fault Mode and Effects Analysis
FMS
Flight Management System
01-000028-070F
FPE
FPM
FSD
FTE
GLS
GND
GNSS
GPH
GPS
GPWS
HAL
HAT
HFOM
HPL
HSI
HUL
IAP
Floating Point Emulation
Feet per Minute
Full Scale Deflection
Flight Technical Error
GNSS Landing System
Ground (potential)
Global Navigation Satellite System
Gallons per Hour
Global Positioning System
Ground Proximity Warning System
Horizontal Alert Limit
Height Above Threshold
Horizontal Figure of Merit
Horizontal Protection Level
Horizontal Situation Indicator
Horizontal Uncertainty Limit
Instrument Approach Procedure, also Initial
Approach Point
IAS
Indicated Airspeed
IAWP
Initial Approach Waypoint - same as IAP
IC
Integrated Circuit
ICAO
International Civil Aviation Organization
ICD
Interface Control Document
ID
Identity or Identification
IDU
Integrated Display Unit
IFR
Instrument Flight Rules
ILS
Instrument Landing System
IM
Inner Marker
IO
Input/Output
IPV
Instrument Procedure with Vertical Guidance
ISR
Interrupt Service Routine
JAD
Jeppesen Aviation Database
JTAG
Joint Test Action Group (IEEE 1149.1 Standard)
K
Kilo=1000
KB
Kilobyte
KIAS
Knots Indicated Airspeed
KT
Knot - Nautical Mile per Hour
KTAS
Knots True Airspeed
LDA
Localizer-type Directional Aid
LED
Light Emitting Diode
LNAV
Lateral Navigation
LOC
Localizer
LRU
Line Replaceable Unit
LSB
Least Significant Bit or Byte
MAHP
Missed Approach Holding Point
MAHWP Missed Approach Holding Waypoint - same as
MAHP
MAP
Missed Approach Point
MASPS Minimum Aviation System Performance Standard
MAWP Missed Approach Waypoint - same as MAP
MB
Megabyte
MDA
Minimum Descent Altitude
MEMS
Micro Electro Mechanical System
MFD
Multifunction Display (an IDU with software for
showing multiple display screens)
MM
Middle Marker
MOPS
Minimum Operational Performance
Standard
MOT
Mark On Target
MSB
Most Significant Bit or Byte
MSL
Mean Sea Level
MSU
Magnetic Sensor Unit
MTBF
Mean Time Between Failures
NACO
National Aeronautical Charting Office
NAS
U.S. National Airspace System
NASA
National Aeronautics and Space Administration
NED
National Elevation Dataset
Chelton Flight Systems – Confidential
Page 8 of 104
NIMA
ND
NDB
NM
NPA
OAT
OBS
OM
OT
PA
PDA
PDR
PFD
National Imagery and Mapping Agency
Navigation Display
Nondirectional Beacon
Nautical Mile
Non-Precision Approach
Outside Air Temperature
Omnibearing Selector
Outer Marker
Other Traffic (Traffic Function)
Proximate Advisory (Traffic Function)
Premature Descent Alert
Preliminary Design Review
Primary Flight Display (the display screen showing
primary instrumentation -- can also refer to the
primary IDU with software that only shows primary
instrumentation)
PFDE
Predictive Fault Detection and Exclusion
PIC
Peripheral Interface Controller
PLI
Pitch Limit Indicator
PN
Part Number
PRAIM Predictive Receiver Autonomous Integrity Monitoring
PSAC
Plan for Software Aspects of Certification
PSCP
Project Specific Certification Plan
PSP
Partnership for Safety Plan
PTN
Problem Tracking Number
QA
Quality Assurance
QFE
Altimeter setting that provides height above
reference point.
QM
Quality Management
QNE
Altimeter setting that provides pressure altitude
readout
QNH
Altimeter setting that provides MSL altitude at a
reporting point
RA
Resolution Advisory (Traffic Function)
RAM
Random Access Memory
RBP
Remote Bug Panel
RMI
Radio Magnetic Indicator
RNAV
Area Navigation
RNP
Required Navigation Performance
RS
EIA Recommended Standard
RTC
Real Time Computing
RTCA
Radio Telephone Commission for Aeronautics
RTD
Resistive Thermal Detector
RTL
Run Time Library
Rx
Receive
SA
Selective Availability
SAE
Society of Automotive Engineers
SAS
Software Accomplishment Summary
SBAS
Satellite Based Augmentation System
SCI
Software Configuration Index
SCMP
Software Configuration Management Plan
SCR
Software Conformity Review
SCS
Software Coding Standards
SDD
Software Design Document
SDP
Software Development Plan
SDS
Software Design Standards
SECI
Software Environment Configuration Index
SIGMET Significant Meteorological Advisory
SMA
Sub-Miniature version A connector
SN
Serial Number
SNI
Serial Number Information
SOI
Stage of Involvement (FAA software audit)
SPR
Software Problem Report
SQA
Software Quality Assurance
SQAP
Software Quality Assurance Plan
SQAR
Software Quality Assurance Representative
SRD
Software Requirements Document
SRS
Software Requirements Standards
SRTM
Shuttle Radar Topographical Mission
SSA
System Safety Assessment
STAR
Standard Terminal Arrival Routes
STC
Supplemental Type Certificate
STP
Software Test Protocol
01-000028-070F
STS
SUA
SV
SVCP
SVP
SVR
SYRD
TA
TAFs
TAS
TAWS
TCAD
TCAS
TERPS
TCH
TD
TFR
TIS
TIS-B
TMS
TQP
TSO
Tx
UART
USGS
UTC
VAL
VFOM
VFR
VHF
VNAV
VOR
VPL
VSI
VTF
VUL
WAAS
WGS84
Software Test Specification
Special Use Airspace
Service Vehicle
Software Verification Cases and Procedures
Software Verification Plan
Software Verification Results
System Requirements Document
Traffic Advisory (Traffic Function)
Terminal Aerodrome Forecasts
Traffic Advisory System
Terrain Awareness and Warning System
Traffic Collision Alert Device
Traffic Collision Alert System
Terminal Instrument Procedures
Threshold Crossing Height
Traffic Display
Temporary Flight Restriction
Traffic Information Service
Traffic information Service-Broadcast
Texas Instruments family of DSP processors
Tool Qualification Plan
Technical Standard Order
Transmit
Universal Asynchronous Receiver-Transmitter
United States Geological Survey
Universal Time Coordinated
Vertical Alert Limit
Vertical Figure of Merit
Visual Flight Rules
Very High Frequency
Vertical Navigation
VHF Omnidirectional Radio
Vertical Protection Level
Vertical Speed Indicator
Vectors to Final
Vertical Uncertainty Limit
Wide Area Augmentation System
World Geodetic System 1984
Chelton Flight Systems – Confidential
Page 9 of 104
4
SYSTEM OVERVIEW
These requirements apply across multiple types of IDUs including the IDU-I, IDU-III, IDU450, and IDU-680P.
Generally, IDUs are part of a complete flight and navigation instrumentation system that
intuitively provides information to a pilot via computer generated screen displays. The
IDUs may be configured as a PFD (a three-dimensional, enhanced situational awareness
Primary Flight Display), an MFD (Multi-Function Display that can be configured to show a
moving map, an HSI, traffic, terrain or weather displays), or a dedicated EICAS (Engine
Indication and Crew Alerting System). A system consists of various discrete digital
sensor modules that communicate with IDUs via RS-232, RS-422 or ARINC 429 serial
data. Each IDU incorporates a high-brightness AMLCD screen, bezel keys, a screen and
keyboard lighting intensity control, rotary selector and enter switches, a central processing
unit, numerous RS-232, RS-422 and ARINC 429 receive and transmit ports, and discrete
IO ports. Because the receive ports of the IDUs are connected to the digital sensor
modules in parallel, each IDU is independent from all other IDUs. The following is a
typical system diagram.
Refer to IDU hardware requirements for details on a particular type of IDU. Where
differences are significant to the communication requirements, differences will be detailed
in this document.
01-000028-070F
Chelton Flight Systems – Confidential
Page 10 of 104
5
5.1
SYSTEM REQUIREMENTS
DEFINITIONS AND OVERVIEW
In this document the word “shall” implies that a requirement is firm and can be tested
against. Other words, such as “is” or “will” are used to describe facts or provide
background material and are not intended to imply the existence of a requirement.
5.2
IDU SERIAL COMMUNICATIONS
Serial communication port usage shall [SYS_COM_024] be as follows:
PORT
COM1 (232)
COM2 (232)
COM3 (232)
COM4 (232)
COM5 (232)
COM6 (232)
COM7 (232)
COM8 (232)
COM9 (422)
COM10 (422)
COM11 (422)
COM12 (422)
COM13 (232)
COM14 (232)
COM15 (232)
COM16 (232)
COM17 (232)
COM18 (232)
COM19 (232)
COM20 (232)
COM21 (429)
COM22 (429)
COM23 (429)
COM24 (429)
COM25 (429)
COM26 (429)
COM27 (429)
COM28 (429)
COM29(429)
COM30(429)
COM31(429)
COM32(429)
COM33(232)
COM34(232)
COM35(232)
COM36(232)
HS #1 (Internal)
HS #2 (Internal)
01-000028-070F
TRANSMIT
GPS1
AHRS1
Datalink/ADS-B
WX-500
TCAD
Analog Interface + NAT Transponder
AHRS2
GPS2
GPS/COM Data + Remote Tune
Remote Bugs Panel
Inter-System Crosslink
Reserved
----Intra-System Transmit
---Configurable
Configurable
Configurable (IDU-III only)
Configurable (IDU-III only)
Configurable (IDU-450/680 only)
Configurable (IDU-450/680 only)
--Configurable (IDU-450/680 Only)
Configurable (IDU-450/680 Only)
--Reserved (IDU-450/680 Only)
Reserved (IDU-450/680 Only)
Reserved (IDU-450/680 Only)
Reserved (IDU-450/680 Only)
Weather Radar Module (IDU-450/680 Only)
ARINC 429 Expansion Module (IDU450/680 Only)
RECEIVE
GPS1
AHRS1
Datalink/ADS-B
WX-500
TCAD
Analog Interface
AHRS2
GPS2
SL-30 NAV (Configurable)
Remote Bugs Panel
Inter-System Crosslink
HeliSAS (Configurable)
ADC1
ADC2
RS-232 Fuel Flow Sensor
Remote Keyboard
Intra-System IDU #1 Receive
Intra-System IDU #2 Receive
Intra-System IDU #3 Receive
Intra-System IDU #4 Receive
Configurable
Configurable
Configurable
Configurable
Configurable
Configurable
Configurable
Configurable
Configurable (IDU-450/680 Only)
Configurable (IDU-450/680 Only)
Configurable (IDU-450/680 Only)
Configurable (IDU-450/680 Only)
Reserved (IDU-450/680 Only)
Reserved (IDU-450/680 Only)
Reserved (IDU-450/680 Only)
Reserved (IDU-450/680 Only)
Weather Radar Module (IDU-450/680 Only)
ARINC 429 Expansion Module (IDU450/680 Only)
Chelton Flight Systems – Confidential
Page 11 of 104
Note that communications between IDUs installed on the same system is referred to as
intra-system communications. In a dual system configuration, the crosslink system to
system communications is referred to as inter-system communications.
5.2.1 Intra-System Communications
The IDUs shall [SYS_COM_001] communicate among themselves via RS-232 to
synchronize and detect IDU failures. Each IDU shall [SYS_COM_002] transmit intra-IDU
communications on COM17. Intra-IDU transmissions shall [SYS_COM_003] be wired to
COM17, COM18, COM19 or COM20. Communications shall [SYS_COM_206] take
place at 57,600 baud, 8 bits, 1 stop bit and no parity.
IDU#0 (single-screen installation only) shall [SYS_COM_097] connect COM17 transmit to
COM17 receive. IDU#1 shall [SYS_COM_005] connect COM17 transmit to COM17
receive. IDU#2 shall [SYS_COM_007] connect COM17 transmit to COM18 receive.
IDU#3 shall [SYS_COM_009] connect COM17 transmit to COM19 receive. IDU#4 shall
[SYS_COM_011] connect COM17 transmit to COM20 receive.
Each IDU shall [SYS_COM_013] be connected to each RS-232 and RS-422 device in
parallel so that each IDU is capable of performing all functions independently of the other
IDUs. Each IDU shall [SYS_COM_014] be capable of making all RS-232 and RS-422
transmissions required by the system interfaces. At any given time, only one IDU shall
[SYS_COM_015] be “transmit enabled” to send RS-232 and RS-422 system
transmissions. By default, IDU#0 (in single-screen installations) or IDU#1 shall
[SYS_COM_016] be “transmit enabled.” If IDU#1 is failed, IDU#2 shall [SYS_COM_017]
be “transmit enabled.” If IDU#1 and IDU#2 are failed and IDU#3 is installed, IDU#3 shall
[SYS_COM_018] be “transmit enabled.” If IDU#1, IDU#2 and IDU#3 are failed and
IDU#4 is installed, IDU#4 shall [SYS_COM_019] be “transmit enabled.” Each IDU shall
[SYS_COM_020] be uniquely identified by the Aircraft Limits to allow automatic failure
detection.
Each IDU shall [SYS_COM_021] be connected to each ARINC 429 source in parallel so
that each IDU is capable of performing all functions independently of the other IDUs.
Each IDU shall [SYS_COM_022] make ARINC 429 transmissions as configured by the
01-000028-070F
Chelton Flight Systems – Confidential
Page 12 of 104
Aircraft Limits settings. However, because the ARINC 429 transmission ports lack a
“transmit enable” feature, ARINC 429 sinks shall [SYS_COM_023] be physically
connected to only one IDU at any given time. This connection may be through hard
wiring to a single IDU or connecting to any one IDU through a selector switch at the option
of the system integrator.
The following intra-system messages are defined:
5.2.1.1 (“$PSACT”) Active Flight Plan Message:
The active flight plan messages shall [SYS_COM_207] synchronize changes in the active
flight plan performed in the menu system of one IDU with all other IDUs. The active flight
plan message shall [SYS_COM_208] be formatted as follows:
Byte #
0–6
7–8
9 – 10
Last 4
Parameter
ID
Waypoint
Number
Total
Waypoints
Waypoint
Type
Name
Freq
VNAV Offset
CRC-32
Type
ASCII Text
Short
Units
N/A
N/A
Description
Packet Identification “$PSACT,”
Waypoint number in this packet
Short
N/A
Total number of waypoints in flight plan
Binary
Structure
Char
Char Array
Long
Short
Unsigned
Long
N/A
Binary waypoint structure for “Waypoint Number”
N/A
N/A
N/A
NM
N/A
Waypoint type for “Waypoint Number”
String name for “Waypoint Number”
Frequency associated with “Waypoint Number”
VNAV offset distance for “Waypoint Number”
CRC-32 of all above bytes excluding CRC-32 bytes.
To completely transmit the active flight plan, the IDU will setup a state machine that
transmits one message at a maximum rate of 10Hz. The following messages are sent to
transfer the active flight plan:
1. Runway message (ref: § 5.2.1.11) for the Active Runway.
2. Runway message (ref: § 5.2.1.11) for the End Runway.
3. Runway message (ref: § 5.2.1.11) for the SID Runway.
4. Runway message (ref: § 5.2.1.11) for the Start Runway.
5. System Setting Update message (ref: § 5.2.1.15).
6. Active Flight Plan messages for each waypoint in the active flight plan.
The intent of transmitting the active flight plan piece-wise is to ensure that there is
bandwidth available for timely intra-system monitor messages (ref: § 5.2.1.9).
01-000028-070F
Chelton Flight Systems – Confidential
Page 13 of 104
5.2.1.2 (“$PSBUG”) RBP Value Change Message:
The RBP value change message shall [SYS_COM_209] be sent by the “transmit
enabled” IDU on the system (Pilot or Co-pilot) that is connected to the RBP. The purpose
is to synchronize changes commanded by the RBP. The “transmit enabled” IDU shall
[SYS_COM_210] be the only keeper of RBP parameters and shall [SYS_COM_211]
send the following message when it detects changes in the RBP parameters:
Byte #
0–6
Parameter
ID
RBP values
Last 4
CRC-32
Type
ASCII Text
Binary
Structure
Unsigned
Long
Units
N/A
N/A
Description
Packet Identification “$PSBUG,”
Binary RBP values structure containing new RBP values.
N/A
CRC-32 of all above bytes excluding CRC-32 bytes.
5.2.1.3 (“$PSCLR”) WX-500 Clear Strikes Message:
The WX-500 clear strikes message shall [SYS_COM_212] synchronize a clear strikes
action performed in the menu system of one IDU with all other IDUs. In response to a
clear strikes message, the receiving IDU shall [SYS_COM_213] clear its displayed strikes
buffer and shall [SYS_COM_214] transmit a “Data Clear” command to the WX-500.
Since only one IDU will be “transmit enabled,” the net effect of this is that only the
“transmit enabled” IDU actually sends the “Data Clear” command to the WX-500. The
WX-500 clear strikes message shall [SYS_COM_215] be formatted as follows:
Byte #
0–6
Parameter
ID
Type
ASCII Text
Units
N/A
Description
Packet Identification “$PSCLR,”
5.2.1.4 (“$PSCPU”) Alive Message:
The alive message shall [SYS_COM_216] be transmitted at 1Hz from each IDU to all
other IDUs for the purpose of detecting IDU failures and properly assigning the “transmit
enabled IDU.” The alive message shall [SYS_COM_217] be formatted as follows:
Byte #
0-6
Parameter
ID
Type
ASCII Text
Units
N/A
Description
Packet Identification “$PSCPU,”
5.2.1.5 (“$PSDEL”) Delete Stored Flight Plan Message:
The delete stored flight plan message shall [SYS_COM_218] synchronize the deletion of
a stored flight plan performed in the menu system of one IDU with all other IDUs. The
delete stored flight plan message shall [SYS_COM_219] be formatted as follows:
Byte #
0-6
Parameter
ID
01-000028-070F
Type
ASCII Text
Units
N/A
Description
Packet Identification “$PSDEL,”
Chelton Flight Systems – Confidential
Page 14 of 104
Byte #
7
Last 4
Parameter
File Name
Length
File Name
CRC-32
Type
Unsigned
Char
ASCII Text
Unsigned
Long
Units
N/A
N/A
N/A
Description
Unsigned character containing length (in characters) of file
name.
File name characters.
CRC-32 of all above bytes excluding CRC-32 bytes.
5.2.1.6 (“$PSLIM”) Aircraft Limitations Message:
The aircraft limitations message shall [SYS_COM_220] be transmitted from Pilot-side
IDU #1 to all other IDUs to synchronize any changes in the aircraft limitations. The
aircraft limitations message shall [SYS_COM_221] be formatted as follows:
Byte #
0-6
Last 4
Parameter
ID
Aircraft
Limitations
Engine
Limitations
Fuel
Limitations
CRC-32
Type
ASCII Text
Binary
Structure
Binary
Structure
Binary
Structure
Unsigned
Long
Units
N/A
N/A
N/A
N/A
N/A
Description
Packet Identification “$PSLIM,”
Binary aircraft limit structure containing current aircraft limit
values in Pilot-side IDU#1 (read from SCC card if available).
Binary engine limit structure containing current engine limit
values in Pilot-side IDU#1 (read from SCC card if available).
Binary fuel limit structure containing current fuel limit values
in Pilot-side IDU#1 (read from SCC card if available).
CRC-32 of all above bytes excluding CRC-32 bytes.
5.2.1.7 (“$PSMNE”) Menu Action End Message:
The menu action end message shall [SYS_COM_222] be transmitted from the IDU
where menu actions are taking place to all other IDUs. It’s purpose is to remove the
“MENU LOCK” flag and allow menu actions to take place on the other IDUs. The aircraft
menu action end message shall [SYS_COM_223] be formatted as follows:
Byte #
0-6
Parameter
ID
Type
ASCII Text
Units
N/A
Description
Packet Identification “$PSMNE,”
5.2.1.8 (“$PSMNU”) Menu Action Message:
The menu action message shall [SYS_COM_224] be transmitted at 10Hz from the IDU
where menu actions are taking place to all other IDUs so long as menus are open. It’s
purpose is to activate the “MENU LOCK” flag and inhibit menu actions from taking place
on the other IDUs. The aircraft menu action message shall [SYS_COM_225] be
formatted as follows:
Byte #
0-6
Parameter
ID
01-000028-070F
Type
ASCII Text
Units
N/A
Description
Packet Identification “$PSMNU,”
Chelton Flight Systems – Confidential
Page 15 of 104
5.2.1.9 (“$PSMON”) Monitor Message:
The monitor message will transmit active critical parameters and an intra-system screen
freshness counter for use by monitoring algorithms. The monitor message will be sent at
5Hz ± 0.5Hz. The monitor message shall [SYS_COM_315] be formatted as follows:
Byte #
0–6
Parameter
ID
Parameters
Type
ASCII Text
Binary
Structure
Units
N/A
N/A
Last 4
CRC-32
Unsigned
Long
N/A
Description
Packet Identification “$PSMON,”
Binary screen parameters structure consisting of the
following parameters that are being used to render the
display:
 Attitude (Pitch and Roll)
 Heading
 Pressure Altitude
 Indicated Airspeed
 Localizer (both inputs)
 Glideslope (both inputs)
 Radar Altitude
 Latitude
 Longitude
 Track
 Groundspeed
 Screen Counter Value
CRC-32 of all above bytes excluding CRC-32 bytes.
Using the monitor message, each IDU shall [SYS_COM_307] compare the parameters it
receives to the parameters that it is using to render its display (miscompare logic
identified in 7.0F IDU Warnings System Requirements § 5.2, Doc. No. 01-000036-070F).
An appropriate caution shall [SYS_COM_308] be triggered in the event of a miscompare
(see IDU Warning System Requirements, Doc. No. 01-000036-070F).
In addition, at every screen refresh, the first and last pixels shall [SYS_COM_309] be
overwritten with an incrementing counter value (0-255) prior to the bit blit to VRAM. After
the bit blit, the colors in the first and last pixel positions of the screen in VRAM shall
[SYS_COM_310] be read back. The colors shall [SYS_COM_311] be compared to the
expected value and will trigger a watchdog reboot if there is a mismatch. The value shall
[SYS_COM_312] also be transmitted to the other screens as the “Screen Counter Value”
parameter in the monitor message. Upon receipt of the monitor message, each screen
will check for a changing value and for staleness. If either check fails, an appropriate
caution will be triggered (see IDU Warning System Requirements, Doc. No. 01-000036070F).
01-000028-070F
Chelton Flight Systems – Confidential
Page 16 of 104
5.2.1.10 (“$PSRC0” and “$PSRC1”) RDR-2XXX Synchronization Message:
The RDR-2XXX synchronization messages shall [SYS_COM_323] originate in the
weather radar talker CPU. The weather radar talker CPU is the lowest numbered
CPU (ref: 01-000029-070F) that is weather radar enabled and alive. These messages
shall [SYS_COM_324] only be sent when:

The aircraft limits weather radar type is configured for Honeywell RDR-2000 or
RDR-2100 (Ref: 01-000029-070F).

The aircraft limits indicate that: (1) dual Radar Control Panels are in use; OR (2)
the IDU is Pilot-Side and a single Radar Control Panel is in use (Ref: 01-000029070F).

A vertical profile mode change has been received from the Radar Control Panel.
The RDR-2XXX messages shall [SYS_COM_350] be formatted as follows:
Byte #
0-6
Parameter
ID
Type
ASCII Text
Units
N/A
Description
Packet Identification “$PSRC0,”. Vertical Profile mode is
turned OFF upon receipt of this message.
Byte #
0-6
Parameter
ID
Type
ASCII Text
Units
N/A
Description
Packet Identification “$PSRC1,”. Vertical Profile mode is
turned ON upon receipt of this message.
5.2.1.11 (“$PSRWY”) Runway Message:
The runway message shall [SYS_COM_313] synchronize changes in designated runway
data for the active flight plan performed in the menu system of one IDU with all other
IDUs.
The runway message shall [SYS_COM_316] be formatted as follows:
Byte #
0–6
7
Parameter
ID
RW Type
Type
ASCII Text
Char
Units
N/A
N/A
Runway
Data
Binary
Structure
N/A
CRC-32
Unsigned
Long
N/A
Last 4
01-000028-070F
Description
Packet Identification “$PSRWY,”
0 = Active Runway
1 = End Runway
2 = SID Runway
3 = Start Runway
Binary runway parameters structure consisting of the
following parameters:
 Runway Corner Latitudes
 Runway Corner Longitudes
 Touchdown Zone Elevation
CRC-32 of all above bytes excluding CRC-32 bytes.
Chelton Flight Systems – Confidential
Page 17 of 104
5.2.1.12 (“$PSSAV”) Save Flight Plan Message:
The save flight plan message shall [SYS_COM_226] transmit flight plan data that is being
saved by the flight planning system of one IDU for storage on all other IDUs. The save
flight plan message shall [SYS_COM_227] be formatted as follows:
Byte #
0–6
7–8
9 – 10
Last 4
Parameter
ID
Waypoint
Number
Total
Waypoints
Waypoint
Type
Name
Freq
VNAV Offset
CRC-32
Type
ASCII Text
Short
Units
N/A
N/A
Description
Packet Identification “$PSSAV,”
Waypoint number in this packet
Short
N/A
Total number of waypoints in flight plan
Binary
Structure
Char
Char Array
Long
Short
Unsigned
Long
N/A
Binary waypoint structure for “Waypoint Number”
N/A
N/A
N/A
NM
N/A
Waypoint type for “Waypoint Number”
String name for “Waypoint Number”
Frequency associated with “Waypoint Number”
VNAV offset distance for “Waypoint Number”
CRC-32 of all above bytes excluding CRC-32 bytes.
To completely transmit the saved flight plan, the IDU will setup a state machine that
transmits one message at a maximum rate of 10Hz. Save flight plan messages for each
waypoint in the saved flight plan will be transmitted in sequence. The intent of
transmitting the saved flight plan piece-wise is to ensure that there is bandwidth available
for timely intra-system monitor messages (ref: § 5.2.1.9).
5.2.1.13 (“$PSTS1”) WX-500 Self-Test Message:
The WX-500 self-test message shall [SYS_COM_228] cause all receiving IDUs to
transmit a “Pilot Initiated Self Test Request” command to the WX-500. Since only one
IDU will be “transmit enabled,” the net effect of this is that only the “transmit enabled” IDU
actually sends the “Pilot Initiated Self Test Request” command to the WX-500. The WX500 self-test message shall [SYS_COM_229] be formatted as follows:
Byte #
0–6
Parameter
ID
Type
ASCII Text
Units
N/A
Description
Packet Identification “$PSTS1,”
5.2.1.14 (“$PSTS2”) Ryan TCAD Self-Test Message:
The Ryan TCAD self-test message shall [SYS_COM_230] cause all receiving IDUs to
transmit a “Diagnostic Request Message” to the TCAD. Since only one IDU will be
“transmit enabled,” the net effect of this is that only the “transmit enabled” IDU actually
sends the “Diagnostic Request Message” to the TCAD. The Ryan TCAD self-test
message shall [SYS_COM_231] be formatted as follows:
01-000028-070F
Chelton Flight Systems – Confidential
Page 18 of 104
Byte #
0–6
Parameter
ID
Type
ASCII Text
Units
N/A
Description
Packet Identification “$PSTS2,”
5.2.1.15 (“$PSUPD”) System Settings Update Message:
The system settings update message shall [SYS_COM_232] be transmitted at 10Hz from
the IDU where menu actions are taking place to all other IDUs so long as menus are
open. It’s purpose is to keep the other IDUs synchronized with the changes to the system
settings. Note that not all parameters are synchronized (i.e., certain parameters remain
independent between screens, see IDU Menu System Requirements, Doc. No. 01000037-070F). The system settings update message shall [SYS_COM_233] be
formatted as follows:
Byte #
0-6
Last 4
Parameter
ID
System
Settings
CRC-32
Type
ASCII Text
Binary
Structure
Unsigned
Long
Units
N/A
N/A
N/A
Description
Packet Identification “$PSUPD,”
Binary system setting structure containing new system
settings.
CRC-32 of all above bytes excluding CRC-32 bytes.
5.2.1.16 (“$PSUSR”) Save User Waypoints Message:
The save user waypoints message shall [SYS_COM_234] transmit user waypoint data
that is being saved by the flight planning system of one IDU for storage on all other IDUs.
The save user waypoints message shall [SYS_COM_235] be formatted as follows:
Byte #
0–6
7–8
9 – 10
Last 4
Parameter
ID
Waypoint
Number
Total
Waypoints
Waypoint
CRC-32
Type
ASCII Text
Short
Units
N/A
N/A
Description
Packet Identification “$PSUSR,”
User waypoint number in this packet
Short
N/A
Total number of user waypoints
Binary
Structure
Unsigned
Long
N/A
Binary navdata structure for “Waypoint Number”
N/A
CRC-32 of all above bytes excluding CRC-32 bytes.
To completely transmit the user waypoints, the IDU will setup a state machine that
transmits one message at a maximum rate of 10Hz. Save user waypoints messages for
each user waypoint will be transmitted in sequence. The intent of transmitting the user
waypoints piece-wise is to ensure that there is bandwidth available for timely intra-system
monitor messages (ref: § 5.2.1.9).
01-000028-070F
Chelton Flight Systems – Confidential
Page 19 of 104
5.2.1.17 (“$PSWXR”) Weather Radar Status Message:
The weather radar status message shall [SYS_COM_351] be transmitted from weather
radar enabled IDUs (ref: 01-000029-070F). This allows weather radar warnings (ref: 01000036-070F) and FAULTS menu weather radar status indications (ref: 01-000037070F) to work correctly on IDUs that are not weather radar enabled (such as the PFD).
The weather radar status message shall [SYS_COM_352] be formatted as follows:
Byte #
0–6
7
Parameter
ID
Status Byte
Type
ASCII Text
Char
Units
N/A
N/A
8 – 11
CRC-32
Unsigned
Long
N/A
Description
Packet Identification “$PSWXR,”
Bitfield with the following meanings:
Bit 0: 1 = Weather Radar Fault Exists
Bit 1: 1 = Weather Radar Communications is Timed Out
Bit 2: 1 = RCP Status Bad
Bit 3: 1 = RCP Commanded Mode is OFF
Bit 4 – 7: Reserved
CRC-32 of all above bytes excluding CRC-32 bytes.
5.2.1.18 (“$PSXLK”) Crosslink Enable Message:
The crosslink enable message shall [SYS_COM_236] cause all the “transmit enabled”
IDU to begin receiving and processing inter-system messages. The message is sent in
response to activation of crosslink synchronization (see IDU Menu System Requirements,
Doc. No. 01-000037-070F). The crosslink enable message shall [SYS_COM_237] be
formatted as follows:
Byte #
0–6
Parameter
ID
Type
ASCII Text
Units
N/A
Description
Packet Identification “$PSXLK,”
5.2.2 Inter-System Communications
In dual system configurations (Pilot and Co-pilot side systems), inter-system
communications shall [SYS_COM_169] take place on COM11 at 57,600 baud, 8 bits, 1
stop bit and no parity. Only the “transmit enabled” IDU in each system shall
[SYS_COM_238] make inter-system transmissions.
The following inter-system messages are defined:
5.2.2.1 (“$PSACT”) Active Flight Plan Message:
The inter-system active flight plan message will ([SYS_COM_239] deleted) be identical to
the intra-system active flight plan message. The inter-system active flight plan message
shall [SYS_COM_240] only be transmitted when crosslink is enabled.
01-000028-070F
Chelton Flight Systems – Confidential
Page 20 of 104
5.2.2.2 (“$PSBUG”) RBP Value Change Message:
The inter-system RBP value change message shall [SYS_COM_241] be identical to the
intra-system RBP value change message. The inter-system RBP value change message
shall [SYS_COM_242] always be transmitted.
5.2.2.3 (“$PSCLR”) WX-500 Clear Strikes Message:
The inter-system WX-500 clear strikes message shall [SYS_COM_243] be identical to
the intra-system WX-500 clear strikes message. The inter-system WX-500 clear strikes
message shall [SYS_COM_244] always be transmitted.
5.2.2.4 (“$PSCPU”) Alive Message:
The inter-system alive message shall [SYS_COM_245] be transmitted at 1Hz for the
purpose of detecting crosslink line failures and determining which sensors are being used
by the opposite-side system. The inter-system alive message shall [SYS_COM_246] be
formatted as follows:
Byte #
0-6
7
8
9
10
11
12 –
15
Parameter
ID
Other Side
ADC
Other Side
AHRS
Other Side
GPS/SBAS
Other Side
NAV Source
Other Side
Radar
Altimeter
CRC-32
Type
ASCII Text
Unsigned
Char
Unsigned
Char
Unsigned
Char
Unsigned
Char
Unsigned
Char
Units
N/A
N/A
Description
Packet Identification “$PSCPU,”
Other side selected ADC, either 1 or 2.
N/A
Other side selected AHRS, either 1 or 2.
N/A
Other side selected GPS/SBAS, either 1 or 2.
N/A
N/A
Other side selected NAV source, either GPS1, GPS2,
VLOC1 or VLOC2.
Other side selected Radar Altimeter, either 1 or 2.
Unsigned
Long
N/A
CRC-32 of all above bytes excluding CRC-32 bytes.
5.2.2.5 (“$PSDEL”) Delete Stored Flight Plan Message:
The inter-system delete stored flight plan message shall [SYS_COM_247] be identical to
the intra-system delete stored flight plan message. The inter-system delete stored flight
plan message shall [SYS_COM_248] always be transmitted.
01-000028-070F
Chelton Flight Systems – Confidential
Page 21 of 104
5.2.2.6 (“$PSLIM”) Aircraft Limitations Message:
The inter-system aircraft limitations message shall [SYS_COM_249] be identical to the
intra-system aircraft limitation message. The inter-system aircraft limitations message
shall [SYS_COM_250] always be transmitted.
5.2.2.7 (“$PSMNE”) Menu Action End Message:
The inter-system menu action end message shall [SYS_COM_251] be identical to the
intra-system menu action end message. The inter-system menu action end message
shall [SYS_COM_252] only be transmitted when crosslink is enabled.
5.2.2.8 (“$PSMNU”) Menu Action Message:
The inter-system menu action message shall [SYS_COM_253] be identical to the intrasystem menu action message. The inter-system menu action message shall
[SYS_COM_254] only be transmitted when crosslink is enabled.
5.2.2.9 (“$PSRC0” and “PSRC1”) RDR-2XXX Synchronization Message:
The RDR-2XXX synchronization messages shall [SYS_COM_325] be identical to the
intra-system RDR-2XXX synchronization message. The inter-system RDR-2XX
synchronization message shall [SYS_COM_326] be transmitted under the following
conditions:

An intra-system RDR-2XXX synchronization message has been received.

The aircraft limits indicate that the IDU is Pilot-Side and that a single Radar Control
Panel is in use (Ref: 01-000029-070F).
5.2.2.10 (“$PSRWY”) Runway Message:
The inter-system runway message will be identical to the intra-system runway message.
The inter-system runway message shall [SYS_COM_314] only be transmitted when
crosslink is enabled.
5.2.2.11 (“$PSSAV”) Save Flight Plan Message:
The inter-system save flight plan message will ([SYS_COM_255] deleted) be identical to
the intra-system save flight plan message. The inter-system save flight plan message
shall [SYS_COM_256] always be transmitted.
01-000028-070F
Chelton Flight Systems – Confidential
Page 22 of 104
5.2.2.12 (“$PSTS1”) WX-500 Self-Test Message:
The inter-system WX-500 self-test message shall [SYS_COM_257] be identical to the
intra-system WX-500 self-test message. The inter-system WX-500 self-test message
shall [SYS_COM_258] always be transmitted.
5.2.2.13 (“$PSTS2”) Ryan TCAD Self-Test Message:
The inter-system Ryan TCAD self-test message shall [SYS_COM_259] be identical to the
intra-system Ryan TCAD self-test message. The inter-system Ryan TCAD self-test
message shall [SYS_COM_260] always be transmitted.
5.2.2.14 (“$PSUPD”) System Settings Update Message:
The inter-system system settings update message shall [SYS_COM_261] be identical to
the intra-system system settings update message. The inter-system system settings
update message shall [SYS_COM_262] only be transmitted when crosslink is enabled.
When crosslink is not enabled, the RBP value change message shall [SYS_COM_305]
be sent instead to keep system bugs synchronized when changed using the EFIS menu
system.
5.2.2.15 (“$PSUSR”) Save User Waypoints Message:
The inter-system save user waypoints message will ([SYS_COM_263] deleted) be
identical to the intra-system save user waypoints message. The inter-system save user
waypoints message shall [SYS_COM_264] always be transmitted.
5.2.2.16 (“$PSXLK”) Crosslink Enable Message:
The inter-system crosslink enable message shall [SYS_COM_265] be identical to the
intra-system crosslink enable message. The inter-system crosslink enable message shall
[SYS_COM_266] always be transmitted.
5.2.3 GPS
Duplex communications between the GPS and the IDU shall [SYS_COM_025] use IDU
COM1 (for GPS1) and IDU COM8 (for GPS2). The IDU shall [SYS_COM_026] interface
with either a Chelton Beta-3 or Spectralux NexNAV GPS/SBAS Receiver certified under
TSO-C145c. The IDU will perform the necessary display and database functions so that
01-000028-070F
Chelton Flight Systems – Confidential
Page 23 of 104
the combination of the receiver and an IDU will meet the requirements for TSO-C146c
and FAA Notice 8110.60.
5.2.3.1 Communication Parameters
The communication standard shall [SYS_COM_027] be RS-232. Data shall
[SYS_COM_028] be transmitted with 8 data bits, 1 stop bit, and no parity.
Transmission speed shall [SYS_COM_029] be 19,200 baud.
5.2.3.2 Packet General Description
Both directions of the interface will conform to a packet structure as shown below.
Each packet shall [SYS_COM_030] start with the two-character sequence <DLE><id>
and shall end [SYS_COM_031] with <DLE><ETX>. <DLE> is the ASCII designation for
the "Data Link Escape" character (10 hex). <ETX> is the ASCII designation for the
"End of TeXt" character (03 hex). <id> is a one-byte packet identification code. The
packet data shall [SYS_COM_032] be any 8-bit value with the one requirement that all
data bytes equal to <DLE> shall be [SYS_COM_033] sent twice.
DLE
id
... data bytes ...
DLE
ETX
The following notes pertain to the packet descriptions:
Byte numbers in the packet descriptions assume that <DLE><DLE> character pairs
have been compressed to a single <DLE> character.
The following data formats are used in the packet descriptions:
BYTE
refers to 8 bit data (unsigned unless otherwise noted).
INTEGER
refers to a 16 bit signed number sent MSByte first.
USHORT
refers to a 16 bit unsigned number sent MSByte first.
ULONG
refers to a 32 bit unsigned number sent MSByte first.
FLOAT
refers to a four-byte floating-point number in the ANSI/IEEE
Standard 754 single (short; 32 bit) real format. The first byte sent
is the sign bit and 7 MSBits of the exponent. The second byte
contains the LSBit of the exponent and the 7 MSBits of the
mantissa. The remaining two bytes complete the mantissa.
DOUBLE
01-000028-070F
refers to an eight byte floating-point number in the ANSI/IEEE
Chelton Flight Systems – Confidential
Page 24 of 104
Standard 754 double (64 bit) real format. The first byte sent is the
sign bit and 7 MSBits of the exponent. The second byte contains
the 4 LSBits of the exponent and the 4 MSBits of the mantissa.
The remaining six bytes complete the mantissa.
5.2.3.3 GPS/SBAS Receiver Navigation Packet Output
The GPS/SBAS receiver shall [SYS_COM_034] transmit the following Navigation data
packet at a minimum rate of 5 Hz:
0
1
2
Byte #
Parameter
DLE (0x10)
0x51
NAV State
Data Type
BYTE
BYTE
BYTE
Units
N/A
N/A
N/A
3–4
Data Validity Flags
USHORT
bit field
5–8
Time of Fix
FLOAT
seconds
9 – 16
17 – 24
25 – 32
GPS Latitude
GPS Longitude
GPS Altitude
DOUBLE
DOUBLE
DOUBLE
radians
radians
meters
33 – 36
UTC Time
FLOAT
seconds
37 – 38
39 – 42
Checksum
GPS North Velocity
USHORT
FLOAT
43 – 46
GPS East Velocity
FLOAT
47 – 50
GPS Vertical
Velocity
FLOAT
N/A
meters/
second
meters/
second
meters/
second
01-000028-070F
Description
Used for synchronization.
Packet identification byte.
1 = DR
2 = 2D Nav, no integrity
3 = 3D Nav, no integrity
4 = RAIM/Alt (aided integrity)
5 = RAIM
6 = SVERROR (trying to exclude)
If bit = 1, data is valid.
bit 0: Time of Fix validity
bit 1: GPS lat/lon validity
bit 2: GPS altitude validity
bit 3: GPS horizontal velocity validity
(north, east)
bit 4: GPS vertical velocity validity
bit 5: UTC validity (time and date)
bit 6: HPLFD validity
bit 7: HPLSBAS validity
bit 8: HFOM validity
bit 9: HUL validity
bit 10: VPLFD validity
bit 11: VPLSBAS validity
bit 12: VFOM validity
bit 13: VUL validity
bit 14: SA Status (1 = ON, 0 = OFF)
bit 15: Approach Area HPL and VPL
validity, only set during LNAV/VNAV
and APV-II/GLS Approach.
Number of seconds since the
beginning of the current UTC day that
position was computed
WGS84 latitude, positive = north
WGS84 longitude, positive = east
Geodetic height above (+) or below (-)
the WGS-84 ellipsoid.
Number of seconds since the
beginning of the current UTC day
Two-byte sum of bytes 0 through 36
positive = north
positive = east
positive = altitude increasing
Chelton Flight Systems – Confidential
Page 25 of 104
Byte #
51 – 54
Parameter
UTC Date
Units
N/A
HPLFD
Data Type
BYTE
BYTE
USHORT
FLOAT
55 – 58
59 – 62
HPLSBAS
FLOAT
meters
63 – 66
HFOM
FLOAT
meters
67 – 70
HUL
FLOAT
meters
71 – 74
VPLFD
FLOAT
meters
75 – 78
VPLSBAS
FLOAT
meters
79 – 82
VFOM
FLOAT
meters
83 – 86
VUL
FLOAT
meters
87-90
Approach Area
HPL
FLOAT
meters
91-94
Approach Area
VPL
FLOAT
meters
95-98
HDOP
FLOAT
N/A
99-102
VDOP
FLOAT
N/A
103-104
Checksum
USHORT
N/A
105
106
DLE (0x10)
ETX (0x03)
BYTE
BYTE
N/A
N/A
01-000028-070F
meters
Description
Day
Month
Year
Horizontal Protection Limit provided by
autonomous fault detection function
(ref: RTCA/DO-229D § 1.7.2). If
valid, HPLFD may be used to display
position uncertainty (ref: RTCA/DO229D § 2.2.1.4.8).
Horizontal Protection Limit based on
SBAS error estimates (ref: RTCA/DO229D § 1.7.2). If valid, HPLSBAS may
be used to display position uncertainty
(ref: RTCA/DO-229D § 2.2.1.4.8).
Horizontal figure of merit: This value is
the 95% accuracy (i.e., 2drms) of the
reported position in the horizontal
dimension
Horizontal Uncertainty Limit based on
measurement inconsistency (ref:
RTCA/DO-229D § 1.7.2).
Vertical Protection Limit provided by
autonomous fault detection function
(ref: RTCA/DO-229D § 1.7.2).
Vertical Protection Limit based on
SBAS error estimates (ref: RTCA/DO229D § 1.7.2).
Vertical Figure Of Merit: This value is
the 95% accuracy (i.e., 2drms) of the
reported position in the vertical
dimension. When valid, this value
may be used for displaying vertical
accuracy (ref: RTCA/DO-229D §
2.2.4.4.9).
Vertical Uncertainty Limit based on
measurement inconsistency (ref:
RTCA/DO-229D § 1.7.2).
Approach Area HPL is computed only
in LNAV/VNAV and APV-II/GLS
Approach. (ref: RTCA/DO-229D).
Approach Area VPL is computed only
in LNAV/VNAV and APV-II/GLS
Approach. (ref: RTCA/DO-229D).
Horizontal Dilution of Precision is
represented in this field. The validity
of HDOP is associated with the validity
of the lat/lon fields. If bit 1 of Byte 3-4
is set to 1, then HDOP is valid.
Vertical Dilution of Precision is
represented in this field. The validity
of VDOP is associated with the validity
of the lat/lon fields. If bit 1 of Byte 3-4
is set to 1, then VDOP is valid.
Two-byte sum of bytes 0 through 86
(excluding extra <DLE> in
<DLE><DLE> pairs).
End of Transmission
End of Transmission
Chelton Flight Systems – Confidential
Page 26 of 104
5.2.3.4 EFIS Status
The EFIS shall [SYS_COM_035] transmit the following EFIS status packet once per
second ±500 msec:
0
1
2
Byte #
Parameter
DLE (0x10)
0x3d
Data Validity Flags
Data Type
BYTE
BYTE
BYTE
Units
N/A
N/A
bit field
3 – 10
Altitude
DOUBLE
meters
11
Flight Mode
BYTE
N/A
12 – 13
Checksum
USHORT
N/A
14
15
DLE (0x10)
ETX (0x03)
BYTE
BYTE
N/A
N/A
Description
Used for synchronization.
Packet identification byte.
If data is valid, bit = 1 (note that at most
one can be valid).
bit 0: Baro-Alt. Validity
bit 1: Pressure Alt Validity
Baro-corrected or pressure altitude as
indicated by validity bits.
1 – Oceanic / Remote
2 – Enroute
3 – Terminal
4 – N.P. Approach
5 – LNAV/VNAV Approach
6 – APV-II/GLS Approach
Two-byte sum of bytes 0 through 11
(excluding extra <DLE> in
<DLE><DLE> pairs).
End of Transmission
End of Transmission
5.2.3.5 GPS/SBAS Receiver Status
The GPS/SBAS receiver shall [SYS_COM_306] transmit the following Status packet at
a rate of 1 hertz (note that not all parameters are used by the EFIS):
0
1
2
Byte #
Parameter
DLE (0x10)
0x5e
Software Version
Data Type
BYTE
BYTE
BYTE
Units
N/A
N/A
N/A
3
229 Status
BYTE
bit field
4
Error Codes (1)
BYTE
bit field
01-000028-070F
Description
Used for synchronization.
Packet identification byte.
Two 4-bit numbers:
Bits 7-4: Major Version
Bits 3-0: Minor Version
The following bits will be set to 0 to
indicate a normal condition and to 1 to
indicate an abnormal condition:
Bit 2: Probable equipment malfunction
or failure (ref: RTCA/DO-229D §§
2.2.2.6.3(b), 2.2.3.6.3(b) and
2.2.4.6.3(b)).
Bit 5: No valid SBAS message
received for 4 seconds or more (ref:
RTCA/DO-229D § 2.2.4.6.3(d)).
Bit 6: Insufficient number of “SBAS
HEALTHY” satellites (ref: RTCA/DO229D § 2.2.4.6.3(e)).
The following bits will be set to 0 to
indicate a normal condition and to 1 to
indicate an abnormal condition:
bit 0: unused
bit 1: Indication of inability to exclude
Chelton Flight Systems – Confidential
Page 27 of 104
Byte #
Parameter
Data Type
Units
5
Error Codes (2)
BYTE
bit field
6-7
Checksum
USHORT
N/A
8
9
DLE (0x10)
ETX (0x03)
BYTE
BYTE
N/A
N/A
Description
position failure within relevant time-toalert
bit 2: Indicates Antenna is open
bit 3: unused
bit 4: Indicates Antenna is short
bit 5: Computed oscillator rate exceeds
6.3 ppm
bit 6: Indicates that the UTC time has
been derived from the GPS time after
applying the UTC corrections.
bit 7: unused.
The following bits will be set to 0 to
indicate a normal condition and to 1 to
indicate an abnormal condition:
bit 0: indicates loss of position for more
than 5 consecutive seconds : Alarm
Condition ( ref: RTCA/DO-229D §
2.1.1.13.2).
bit 1: Battery-powered Real Time Clock
failure
bit 2: Indicates GPS SBAS receiver is
healthy (operating normally)
bit 3: Almanacs not complete and
current in nav data base
bit 4: Indicate RF fault.
bit 5: Indicates fault in EEPROM.
bit 6: Indicates failure of SDRAM.
bit 7: Indicates step error has been
detected in one of the channels.
Two-byte sum of characters 0 through
5 (excluding extra <DLE> in
<DLE><DLE> pairs).
End of Transmission
End of Transmission
5.2.3.6 EFIS Predictive FDE Request
The EFIS shall [SYS_COM_348] transmit the following Predictive FDE Request to the
GPS/SBAS receiver when commanded by the menu system:
0
1
2
Byte #
Parameter
DLE (0x10)
0x74
Prediction Type
Data Type
BYTE
BYTE
BYTE
Units
N/A
N/A
N/A
3–6
7 – 10
11 – 14
15 – 18
Required HAL
PFDE Latitude
PFDE Longitude
PFDE ETA Time
FLOAT
FLOAT
FLOAT
FLOAT
Meters
radians
radians
second
s
19 – 22
PFDE ETA Date
N/A
23 – 26
SV Mask
BYTE
BYTE
USHORT
ULONG
01-000028-070F
bit field
Description
Used for synchronization.
Packet identification byte.
0 = Predict Detection Availability
1 = Predict Exclusion Availability
Required HAL for “Detection Available”
positive = north
positive = east
Number of seconds since the
beginning of the UTC day to run the
prediction on
Day
Month
Year
32 bit value where each bit represents
a satellite. A bit value of 1 means the
Chelton Flight Systems – Confidential
Page 28 of 104
Byte #
Parameter
Data Type
Units
27 – 28
Checksum
USHORT
N/A
29
30
DLE (0x10)
ETX (0x03)
BYTE
BYTE
N/A
N/A
Description
satellite will be deselected in the
prediction. A bit value of 0 means the
satellite will not be deselected in the
prediction. Bits translate to PRN # in
accordance with the following:
Byte 23:
PRN #1 (bit 0) to PRN #8 (bit 7)
Byte 24:
PRN #9 (bit 0) to PRN #16 (bit 7)
Byte 25:
PRN #17 (bit 0) to PRN #24 (bit 7)
Byte 26:
PRN #25 (bit 0) to PRN #32 (bit 7)
Two-byte sum of bytes 0 through 26
(excluding extra <DLE> in
<DLE><DLE> pairs).
End of Transmission
End of Transmission
5.2.3.7 GPS/SBAS Receiver Predictive FDE Response
Upon receipt of the Predictive RAIM Request message, the GPS/SBAS receiver will
respond with 7 Predictive FDE Response messages in the following order:
1. PFDE Requested ETA Time/Date
2. PFDE Requested ETA Time/Date – 5 minutes
3. PFDE Requested ETA Time/Date + 5 minutes
4. PFDE Requested ETA Time/Date – 10 minutes
5. PFDE Requested ETA Time/Date + 10 minutes
6. PFDE Requested ETA Time/Date – 15 minutes
7. PFDE Requested ETA Time/Date + 15 minutes
The PFDE ETA Time and Date in the response message corresponds to the above so
that they can be identified (i.e., only the first message will have the same PFDE ETA
Time and Date as the request – the other messages are adjusted by the given number of
minutes). The EFIS shall [SYS_COM_349] process the GPS/SBAS receiver Predictive
FDE Response messages as follows:
Byte #
0
1
2–5
Parameter
DLE (0x10)
0x75
PFDE Latitude
Data Type
BYTE
BYTE
FLOAT
Units
N/A
N/A
Radians
6–9
PFDE Longitude
FLOAT
Radians
10 – 13
PFDE ETA Time
FLOAT
Seconds
14 – 17
PFDE ETA Date
BYTE
BYTE
N/A
01-000028-070F
Description
Used for synchronization.
Packet identification byte.
Exact match of same parameter in
PFDE Request Message
Exact match of same parameter in
PFDE Request Message
Number of seconds since the
beginning of the UTC day for this
prediction
Day for this prediction
Month for this prediction
Chelton Flight Systems – Confidential
Page 29 of 104
Byte #
Parameter
Data Type
USHORT
ULONG
Units
18 – 21
SV Mask
22
signed
BYTE
N/A
23 – 26
Availability – fault
detection is
available if and
only if predicted
HPL is less than
required HAL in
query.
HPLPFD ETA
FLOAT
meters
27 – 30
VPL PFD ETA
FLOAT
meters
31 – 32
Checksum
USHORT
N/A
33
34
DLE (0x10)
ETX (0x03)
BYTE
BYTE
N/A
N/A
01-000028-070F
N/A
Description
Year for this prediction
Exact match of same parameter in
PFDE Request Message
-1 = Navigation not available
0 = Fault detection not available
1 = Fault detection available
2 = Fault detection available (altitude
input required)
3 = Fault detection with exclusion
available
Predicted horizontal protection level
at ETA. Value set to -1 if predicted
HPL greater than 30 km.
Predicted vertical protection level at
ETA. Value set to -1 if predicted VPL
greater than 30 km.
Two-byte sum of characters 0
through 30 (excluding extra <DLE>
in <DLE><DLE> pairs).
End of Transmission
End of Transmission
Chelton Flight Systems – Confidential
Page 30 of 104
5.2.4 AHRS
Duplex communications between the AHRS and the IDU shall [SYS_COM_039] use
IDU COM2 (for AHRS1) and IDU COM7 (for AHRS2). The AHRS shall
[SYS_COM_040] be a Chelton ADAHRS or a Crossbow Technologies AHRS-500GA
certified under TSO-C3d, C4c and C6d. The IDU will perform the necessary display
functions so that the combination of the AHRS and an IDU will meet the requirements
for TSO-C4c and C6d. AHRS parameters may also be acquired through the ARINC429
bus, in which case installation of an RS-232 AHRS is not required. Future capabilities
may include interfaces to other AHRSs.
The IDU shall [SYS_COM_144] continuously attempt to connect to an AHRS, either the
Chelton ADAHRS or a Crossbow AHRS. If no response is received within two seconds,
the IDU shall [SYS_COM_145] attempt to connect to the other AHRS type.
5.2.4.1 Chelton AHRS
5.2.4.1.1 Chelton AHRS – Flight Mode Communication Parameters
Communications shall [SYS_COM_146] take place at 19,200 baud, 9 bits, no parity, non
return to zero serial protocol using a RS-232 physical interface. The serial protocol shall
[SYS_COM_203] use the 9th bit to identify packet framing. The 9th bit shall
[SYS_COM_204] be set only for the last character of a packet and shall
[SYS_COM_205] be cleared for all other characters. The set 9th bit will uniquely identify
the last character of the packet, regardless of the contents of the lower 8 bits.
5.2.4.1.2 Chelton AHRS to IDU Parameter Packet Description
When in Flight Mode, the Chelton AHRS shall [SYS_COM_172] transmit the following
packet at a rate of 50 Hz:
Byte #
0–1
Parameter
Data Validity
and system
BIT Flags
Data Type
USHORT
bit 0:
bit 1:
bit 2:
bit 3:
bit 4:
01-000028-070F
Description
0 = Indicates Roll, Pitch Angle valid
1 = Indicates Roll, Pitch Angle invalid
0 = Indicates Magnetic Heading valid
1 = Indicates Magnetic Heading invalid
0 = Indicates Roll Rate, Pitch Rate, Yaw Rate valid
1 = Indicates Roll Rate, Pitch Rate, Yaw Rate invalid
0 = Indicates Accelerations valid
1 = Indicates Accelerations invalid
Reserved (Always 0)
Chelton Flight Systems – Confidential
Page 31 of 104
Byte #
Parameter
Data Type
Description
Reserved (Always 0)
Reserved (Always 0)
Reserved (Always 0)
Reserved (Always 0)
Reserved (Always 0)
Reserved (Always 0)
Reserved (Always 0)
Reserved (Always 0)
Reserved (Always 0)
0 = Indicates ADC communications active
1 = Indicates ADC communications inactive
bit 15: 0 = Indicates AHRS passed Power On Self-test
1 = Indicates AHRS failed Power On Self-test
Pitch Angle in 90/32768th of a degree. Range is -32,768 (-90.0°) to
+32,767 (+89.997°). Nose up is positive.
Roll Angle in 180/32768th of a degree. Range is -32,768 (-180.0°) to
+32,767 (+179.995°). Right wing down is positive.
Heading Angle in 180/32768th of a degree. Range is -32,768
(-180.0°) to +32,767 (+179.995°). Headings clockwise from magnetic
North are positive.
Roll Rate in hundredths of a degree per second. Range is -32,768
(-327.68°/sec) to +32,767 (+327.67°/sec). Clockwise rotation is positive.
Pitch Rate in hundredths of a degree per second. Range is
-32,768 (-327.68°/sec) to +32,767 (+327.67°/sec). Nose up rotation is
positive.
Yaw Rate in hundredths of a degree per second. Range is -32,768
(-327.68°/sec) to +32,767 (+327.67°/sec). Increasing heading is positive.
Longitudinal Acceleration in units of 0.001G. Range is -32,768
(-32.768G) to +32,767 (+32.767G). Forward acceleration is positive.
Lateral Acceleration in units of 0.001G. Range is -32,768
(-32.768G) to +32,767 (+32.767G). Right lateral acceleration is positive.
Normal Acceleration in units of 0.001G. Range is -32,768
(-32.768G) to +32,767 (+32.767G). Upward acceleration is positive.
bit 0:
0 = Indicates Rate Sensor 0 OK.
1 = Indicates Rate Sensor 0 hardware fault.
bit 1:
0 = Indicates Rate Sensor 1 OK.
1 = Indicates Rate Sensor 1 hardware fault.
bit 2:
0 = Indicates Rate Sensor 2 OK.
1 = Indicates Rate Sensor 2 hardware fault.
bit 3:
0 = Indicates Accelerometer 0 OK.
1 = Indicates Accelerometer 0 hardware fault.
bit 4:
0 = Indicates Accelerometer 1 OK.
1 = Indicates Accelerometer 1 hardware fault.
bit 5:
0 = Indicates Accelerometer 2 OK.
1 = Indicates Accelerometer 2 hardware fault.
bit 6:
0 = Indicates Magnetometer 0 OK.
1 = Indicates Magnetometer 0 hardware fault.
bit 7:
0 = Indicates Magnetometer 1 OK.
1 = Indicates Magnetometer 1 hardware fault.
bit 8:
0 = Indicates Magnetometer 2 OK.
1 = Indicates Magnetometer 2 hardware fault.
bit 9:
0 = Indicates Airspeed Sensor OK.
1 = Indicates Airspeed Sensor hardware fault.
bit 10: 0 = Indicates Altitude Sensor OK.
1 = Indicates Altitude Sensor hardware fault.
bit 11: 0 = Indicates Total Air Temperature Sensor OK.
1 = Indicates Total Air Temperature Sensor hardware fault.
bit 12: 0 = Indicates Sensor Module at operating temperature
1 = Indicates Sensor Module temperature out of range
bit 5:
bit 6:
bit 7:
bit 8:
bit 9:
bit 10:
bit 11:
bit 12:
bit 13:
bit 14:
2–3
Pitch Angle
INTEGER
4–5
Roll Angle
INTEGER
6–7
Magnetic
Heading
INTEGER
8–9
Roll Rate
INTEGER
10 – 11
Pitch Rate
INTEGER
12 – 13
Yaw Rate
INTEGER
14 – 15
Longitudinal
Acceleration
Lateral
Acceleration
Normal
Acceleration
Hardware
Status
INTEGER
16 – 17
18 – 19
20 – 21
01-000028-070F
INTEGER
INTEGER
USHORT
Chelton Flight Systems – Confidential
Page 32 of 104
Byte #
Parameter
Data Type
22 – 25
Sensor Noise
ULONG
26 – 29
Calibration
Data CRC32
ULONG
30 – 31
Checksum
USHORT
Description
bit 13: 0 = Indicates ADC at operating temperature
1 = Indicates ADC temperature out of range
bit 14: 0 = Indicates MSU at operating temperature
1 = Indicates MSU out of range
bit 15: Reserved (Always 1)
bits 0-1:
Longitudinal Acceleration noise level.
bits 2-3:
Lateral Acceleration noise level.
bits 4-5:
Normal Acceleration noise level.
bits 6-8:
Roll Rate noise level.
bits 9-11:
Pitch Rate noise level.
bits 12-14:
Yaw Rate noise level.
bits 15-17:
X Magnetic field noise level.
bits 18-20:
Y Magnetic field noise level.
bits 21-23:
Z magnetic field noise level.
bits 24-26:
Airspeed noise level.
bits 27-29:
Altitude noise level.
bits 30-31:
Reserved (Always 0).
CRC32 of the Airframe Calibration Data. This is used to validate that the
calibration data stored in the AHRS is the same as the calibration data
stored in the IDU’s SCC card.
Checksum of bytes 0 through 29, calculated as a binary sum of the
unsigned bytes plus the constant 0x5555. Note that the last character of
the packet has the 9th bit set, indicating the end of the packet.
5.2.4.1.3 IDU to Chelton AHRS Aiding Packet Description
The IDU shall [SYS_COM_173] transmit the following packet to the AHRS at a rate of 10
Hz:
Byte #
0
Parameter
Command
Byte
Data Type
BYTE
1
Sensor Data
Status Flags
BYTE
2–3
GPS
Groundspeed
GPS Track
USHORT
4–5
01-000028-070F
INTEGER
Description
0 = Normal Operation
1 = Ignores all communication from the MSU [2]
bit 1:
0 = Normal Operation
1 = Ignores all communication from the ADC [2]
bit 2:
0 = Normal magnetometer slaving
1 = Perform fast-slave to current magnetometer heading[3]
bit 3:
0 = Magnetic heading mode
1 = Free heading mode
bit 4:
Reserved (Always 0)
bit 5:
Reserved (Always 0)
bit 6:
Reserved (Always 0)
bit 7:
Reserved (Always 0)
bit 0:
0 = Indicates GPS data valid and new[1]
1 = Indicates GPS data invalid or old
bit 1:
0 = Indicates TAS/IAS Factor valid
1 = Indicates TAS/IAS Factor invalid
bit 2:
Reserved (Always 0)
bit 3:
Reserved (Always 0)
bit 4:
Reserved (Always 0)
bit 5:
Reserved (Always 0)
bit 6:
Reserved (Always 0)
bit 7:
Reserved (Always 0)
GPS Groundspeed in hundredths of a knot (Knots x 100). Range is 0 (0
KTS) to 65,535 (655.35 KTS)
GPS Track in 180/32768th of a degree (Degrees x 32768/180). Range
is -32,768 (-180.0°) to +32,767 (+179.995°). Tracks clockwise from true
bit 0:
Chelton Flight Systems – Confidential
Page 33 of 104
Byte #
Parameter
6–7
Data Type
USHORT
8–9
TAS/IAS
Factor
Free Mode
Heading
Offset
10 – 11
12 – 13
14-15
Unused
Unused
Checksum
USHORT
USHORT
USHORT
INTEGER
Description
North are positive.
TAS / IAS Factor in 4 / 65,536th units. Range is 0 (Factor of 0.0) to
65,535 (Factor of 3.99994).
Free mode heading offset in 180/32768th of a degree (Degrees x
32768/180). Range is -32,768 (-180.0°) to +32,767 (+179.995°). When
in free mode, this value is added to the internally stored heading to derive
the heading reported by the AHRS. This value is ignored in magnetic
heading mode.
Reserved (Always 0)
Reserved (Always 0)
Checksum of bytes 0 through 13, calculated as the binary sum of the
unsigned bytes, plus the constant 0x5555. Note that the last character of
the packet has the 9th bit set, indicating the end of the packet.
Notes:
1. Since GPS updates are usually received at less than 10Hz, this flag should be set only when new
data from the GPS is being reported for the first time.
2. These bits are checked only in a test version of the ADAHRS code to simulate operation under
failure conditions. Production version of the ADAHRS code ignores these two bits and always
processes communications from the MSU and the ADC if present.
3. When the EFIS user initiates a fast-slave command through the EFIS menu structure, this bit is set
for 5 consecutive transmissions and then returns to zero. The AHRS performs the fast-slave to
currently sensed magnetic fields upon seeing this bit transition from zero to one.
5.2.4.1.4 IDU Ground Mode Communication Parameters
In ground mode, the IDU shall [SYS_COM_185] receive a data package containing
current sensor readings and calibration EEPROM contents; and shall [SYS_COM_186]
transmit a packet containing new calibration EEPROM contents for programming into the
calibration EEPROM. Communications shall [SYS_COM_187] take place at 115,200
baud, 8 data bits, 2 stop bits, and no parity using an RS-232 physical interface.
5.2.4.1.5 IDU Ground Mode Packet Description
Each packet shall [SYS_COM_188] start with the two-character sequence <DLE><STX>
and shall [SYS_COM_189] end with <DLE><ETX>. <DLE> is the ASCII designation for
the "Data Link Escape" character (0x10). <STX> is the ASCII designation for the "Start of
Text" character (0x02). <ETX> is the ASCII designation for the "End of Text" character
(0x03). The packet data shall [SYS_COM_190] be any 8-bit value with the one
requirement that all data bytes equal to <DLE> shall be sent twice.
DLE
STX
... data bytes ...
DLE
ETX
Packets shall [SYS_COM_191] be protected from corruption by use of a checksum on
the data bytes (excluding the checksum bytes and the leading/trailing 2 byte sequences).
01-000028-070F
Chelton Flight Systems – Confidential
Page 34 of 104
The checksum shall [SYS_COM_192] be generated prior to adding <DLE><DLE>
character pairs and shall be checked after compressing <DLE><DLE> character pairs.
The checksum shall [SYS_COM_193] be a CRC32. Byte numbers in the packet
descriptions that follow assume that <DLE><DLE> character pairs have been
compressed to a single <DLE> character.
5.2.4.1.6 Chelton AHRS to IDU Ground Mode Packet Description
In ground mode, the AHRS shall [SYS_COM_174] transmit the following packet at 50Hz,
except when the AHRS is busy programming the calibration EEPROM:
Byte #
Parameter
DLE (0x10)
STX (0x02)
Sensor
Module
Hardware
Status Flags
Data Type
BYTE
BYTE
BYTE
3
Sensor
Module
Data Status
Flags
BYTE
4–5
Rate X
INTEGER
6–7
Rate Y
INTEGER
8–9
Rate Z
INTEGER
10 – 11
Acceleration
X
Acceleration
INTEGER
0
1
2
12 – 13
01-000028-070F
INTEGER
Description
Start of Packet
Start of Packet
bit 0:
0 = Indicates Rate Sensor 0 Valid
1 = Indicates Rate Sensor 0 Hardware Fault
bit 1:
0 = Indicates Rate Sensor 1 Valid
1 = Indicates Rate Sensor 1 Hardware Fault
bit 2:
0 = Indicates Rate Sensor 2 Valid
1 = Indicates Rate Sensor 2 Hardware Fault
bit 3:
0 = Indicates Accelerometer 0 Valid
1 = Indicates Accelerometer 0 Hardware Fault
bit 4:
0 = Indicates Accelerometer 1 Valid
1 = Indicates Accelerometer 1 Hardware Fault
bit 5:
0 = Indicates Accelerometer 2 Valid
1 = Indicates Accelerometer 2 Hardware Fault
bit 6:
0 = Indicates Sensor Module temperature within range
1 = Indicates Sensor Module temperature out of range
bit 7:
0 Indicates the Sensor Module passed power-on self-test.
1 Indicates the Sensor Module failed power-on self-test.
bit 0:
0 = Indicates Rate Sensor data valid
1 = Indicates Rate Sensor data invalid
bit 1:
0 = Indicates Acceleration data valid
1 = Indicates Acceleration data invalid
bit 2:
Reserved (Always 0)
bit 3:
Reserved (Always 0)
bit 4:
Reserved (Always 0)
bit 5:
Reserved (Always 0)
bit 6:
Reserved (Always 0)
bit 7:
1 = Indicates fresh data from the Sensor Module
0 = Indicates no packet received since the last report
Rate along X axis of the Sensor Module in hundredths of degrees
per second. Range is -32,768 (-327.68°/sec) to
+32,767 (+327.67°/sec).
Rate along Y axis of the Sensor Module in hundredths of degrees
per second. Range is -32,768 (-327.68°/sec) to
+32,767 (+327.67°/sec).
Rate along Z axis of the Sensor Module in hundredths of degrees
per second. Range is -32,768 (-327.68°/sec) to
+32,767 (+327.67°/sec).
Acceleration along X axis of the Sensor Module in units of 0.0005
G. Range is -32,768 (-16.3840G) to +32,767 (+16.3835G).
Acceleration along Y axis of the Sensor Module in units of 0.0005
Chelton Flight Systems – Confidential
Page 35 of 104
Byte #
14 – 15
16
Parameter
Y
Acceleration
Z
MSU
Hardware
Status Flags
Data Type
INTEGER
BYTE
17
MSU Data
Status Flags
BYTE
18 – 19
X
Magnetomet
er Output
Y
Magnetomet
er Output
Z
Magnetomet
er Output
X
Acceleromet
er Output
Y
Acceleromet
er Output
ADC Sensor
Hardware
Status Flags
INTEGER
20 – 21
22 – 23
24 – 25
26 – 27
28
Description
G. Range is -32,768 (-16.3840G) to +32,767 (+16.3835G).
Acceleration along Z axis of the Sensor Module in units of 0.0005
G. Range is -32,768 (-16.3840G) to +32,767 (+16.3835G).
bit 0:
0 = Indicates Magnetic Sensor 0 valid
1 = Indicates Magnetic Sensor 0 hardware fault
bit 1:
0 = Indicates Magnetic Sensor 1 valid
1 = Indicates Magnetic Sensor 1 hardware fault
bit 2:
0 = Indicates Magnetic Sensor 2 valid
1 = Indicates Magnetic Sensor 2 hardware fault
bit 3:
0 = Indicates X Accelerometer valid
1 = Indicates X Accelerometer hardware fault
bit 4:
0 = Indicates Y Accelerometer valid
1 = Indicates Y Accelerometer hardware fault
bit 5:
Reserved (Always 0)
bit 6:
0 = Indicates MSU temperature within range
1 = Indicates MSU temperature out of range
bit 7:
0 Indicates the MSU passed power-on self-test.
1 Indicates the MSU failed power-on self-test.
bit 0:
0 = Indicates Magnetometer data valid
1 = Indicates Magnetometer data invalid
bit 1:
0 = Indicates Accelerometer data valid
1 = Indicates Accelerometer data invalid
bit 2:
Reserved (Always 0)
bit 3:
Reserved (Always 0)
bit 4:
Reserved (Always 0)
bit 5:
Reserved (Always 0)
bit 6:
Reserved (Always 0)
bit 7:
1 = Indicates fresh data from the MSU
0 = Indicates no packet received since the last report
X magnetic field component in units of 4 nano-Tesla. Range is
-32768 (-131,072 nano-Tesla) to +32767 (+131,068nano-Tesla).
INTEGER
Y magnetic field component in units of 4 nano-Tesla. Range is
-32768 (-131,072 nano-Tesla) to +32767 (+131,068nano-Tesla).
INTEGER
Z magnetic field component in units of 4 nano-Tesla. Range is
-32768 (-131,072 nano-Tesla) to +32767 (+131,068nano-Tesla).
INTEGER
X acceleration in units of 0.0001G. Range is -32768
(-3.2768G) to +32767 (+3.2767G).
INTEGER
Y acceleration in units of 0.0001G. Range is -32768
(-3.2768G) to +32767 (+3.2767G).
BYTE
bit 0:
bit 1:
bit 2:
bit 3:
bit 4:
bit 5:
01-000028-070F
0 = Indicates Airspeed pressure sensor valid
1 = Indicates Airspeed pressure sensor hardware fault
0 = Indicates Altitude pressure sensor valid
1 = Indicates Altitude pressure sensor hardware fault
0 = Indicates Outside Air Temperature sensor valid
1 = Indicates Outside Air Temperature sensor hardware
fault
Reserved (Always 0)
0 = Indicates Altitude Offset Compensation EEPROM
CRC32 valid
1 = Indicates Altitude Offset Compensation EEPROM
CRC32 invalid
0 = Indicates Airspeed Offset Compensation EEPROM
CRC32 valid
1 = Indicates Airspeed Offset Compensation EEPROM
Chelton Flight Systems – Confidential
Page 36 of 104
Byte #
Parameter
Data Type
29
ADC Sensor
Data Status
Flags
BYTE
30 – 31
Altitude
Correction
Factor
USHORT
32 – 33
Pressure
Altitude
Airspeed
Correction
Factor
USHORT
Indicated
Airspeed
Firmware
Status
USHORT
Sensor
Module To
Airframe
Alignment
MSU To
Airframe
Alignment
MATRIX
78 – 95
MSU Soft
Iron Error
Correction
MATRIX
96 – 101
MSU Hard
Iron Error
Correction
VECTOR
102 - 103
North Offset
INTEGER
104 - 105
East Offset
INTEGER
34 – 35
36 – 37
38 – 41
42 – 59
60 – 77
01-000028-070F
USHORT
ULONG
MATRIX
Description
CRC32 invalid
bit 6:
0 = Indicates ADC temperature within range
1 = Indicates ADC temperature out of range
bit 7:
0 = Indicates ADC passed power-on self test.
1 = Indicates ADC failed power-on self test.
bit 0:
0 = Indicates Airspeed data valid
1 = Indicates Airspeed data invalid
bit 1:
0 = Indicates Altitude data valid
1 = Indicates Altitude data invalid
bit 2:
0 = Indicates Temperature data valid
1 = Indicates Temperature data invalid
bit 3:
Reserved (Always 0)
bit 4:
Reserved (Always 0)
bit 5:
Reserved (Always 0)
bit 6:
Reserved (Always 0)
bit 7:
1 = Indicates fresh data from the ADC
0 = Indicates no packet received since the last report
This is a value in the ADC’s internal units that will need to be
added to the altitude pressure transducer output to force the
current altitude to be 0 feet MSL. A value of 0 means this
parameter is invalid.
Pressure Altitude in feet offset by 1000 (feet + 1000).
Range is 0 (-1000 ft) to 65,535 (64,535 ft).
This is a value in the ADC’s internal units that will need to be
added to the airspeed pressure transducer output to force the
current airspeed to be 0 KIAS. A value of 0 means this parameter
is invalid.
Indicated Airspeed in units of 0.01 KIAS. Range is 0 (0.00KIAS) to
65,535 (655.35 KIAS).
bits 0-5:
Sensor Module firmware release number[1]
bits 6-11:
MSU firmware release number[1]
bits 12-17:
Air Data Computer firmware release number[1]
bits 18-24:
AHRS flight firmware release number
bits 25-31:
AHRS ground firmware release number
A matrix describing the alignment between the Sensor Module and
the airframe. Each element is a non-dimensional constant
between -1.0 and +1.0, multiplied by 32768. Range for each
element is -32768 (-1.0) to +32767 (+0.99997).
A matrix describing the alignment between the MSU and the
airframe. Each element is a non-dimensional constant between 1.0 and +1.0, multiplied by 32768. Range for each element is 32768 (-1.0) to +32767 (+0.99997).
A matrix for the installation specific soft iron error correction. Each
element is a non-dimensional constant between -2.0 and +2.0,
multiplied by 16384. Range for each element is -32768 (-2.0) to
+32767 (+1.99933).
A vector describing the hard iron offsets for the MSU in units of 4
nano-Tesla. Range for each element is -32768 (-131,072 nanoTesla) to +32767 (+131,068nano-Tesla). The Hard Iron Error
Correction is subtracted from the MSU before applying the Soft
Iron Error Correction.
Correction offset value for North heading found during alignment
procedure. Range is -32768 (-20°) to +32767 (+19.9994°). The
AHRS applies a straight line interpolation of the offsets when in
magnetic heading mode.
Correction offset value for East heading found during alignment
procedure. Range is -32768 (-20°) to +32767 (+19.9994°). The
AHRS applies a straight line interpolation of the offsets when in
Chelton Flight Systems – Confidential
Page 37 of 104
Byte #
Parameter
Data Type
Description
magnetic heading mode.
106 - 107 South Offset INTEGER
Correction offset value for South heading found during alignment
procedure. Range is -32768 (-20°) to +32767 (+19.9994°). The
AHRS applies a straight line interpolation of the offsets when in
magnetic heading mode.
108 - 109 West Offset INTEGER
Correction offset value for West heading found during alignment
procedure. Range is -32768 (-20°) to +32767 (+19.9994°). The
AHRS applies a straight line interpolation of the offsets when in
magnetic heading mode.
110 – 111 Airframe
USHORT
bits 0-3: Filter number of Airspeed Filter
Config.
bits 4-7: Filter number of Altitude Filter
bits 8-11:Filter number of VSI Filter
bit 12: ARINC429 SDI bit.
bit 13: ARINC429 Air Data Enable on AHRS port
bit 14: Always 0
bit 15: Always 0
112 - 113 Reserved
USHORT
Reserved for future use, currently always 0
114 - 117 Reported
ULONG
CRC32 of the calibration data, as stored in the calibration
Calibration
EEPROM. This may or may not be the correct CRC32 of the data.
Data
Bytes 42 through 113 represent the actual contents of the
CRC32
calibration EEPROM
118 - 119 Sample No. USHORT
A number that is incremented every sample and rolls from 0xffff to
0. This is intended to detect missing samples in the stored data
stream.
120 - 123 CRC32
ULONG
CRC32 of bytes 2 through 119 of the packet. Note that the
checksum is calculated PRIOR to adding duplicate <DLE>
characters and is checked AFTER removing duplicate <DLE>
characters
124
DLE (0x10)
BYTE
End of Packet
125
ETX (0x03)
BYTE
End of Packet
Notes: [1] A release number of 0x3F indicates that the data is not available.
5.2.4.1.7 IDU to Chelton AHRS Ground Mode Packet Description
The IDU shall [SYS_COM_175] transmit the following packet as needed:
Byte #
0
1
2 – 19
Parameter
DLE (0x10)
STX (0x02)
Sensor Module
To Airframe
Alignment
Data Type
BYTE
BYTE
MATRIX
20 – 37
MSU To
Airframe
Alignment
MATRIX
38 – 55
MSU Soft Iron
Error Correction
MATRIX
56 – 61
MSU Hard Iron
Error Correction
VECTOR
62 – 63
North Offset
INTEGER
01-000028-070F
Description
Start of Packet
Start of Packet
A matrix describing the alignment between the Sensor Module and
the airframe. Each element is a non-dimensional constant between 1.0 and +1.0, multiplied by 32768. Range for each element is -32768
(-1.0) to +32767 (+0.99997).
A matrix describing the alignment between the MSU and the
airframe. Each element is a non-dimensional constant between -1.0
and +1.0, multiplied by 32768. Range for each element is -32768 (1.0) to +32767 (+0.99997).
A matrix for the installation specific soft iron error correction. Each
element is a non-dimensional constant between -2.0 and +2.0,
multiplied by 16384. Range for each element is -32768 (-2.0) to
+32767 (+1.99933).
A vector describing the hard iron offsets for the MSU in units of 4
nano-Tesla. Range for each element is -32768 (-131,072 nanoTesla) to +32767 (+131,068nano-Tesla). The Hard Iron Error
Correction is subtracted from the MSU before applying the Soft Iron
Error Correction.
Correction offset value for North heading found during alignment
Chelton Flight Systems – Confidential
Page 38 of 104
Byte #
Parameter
Data Type
64 – 65
East Offset
INTEGER
66 – 67
South Offset
INTEGER
68 – 69
West Offset
INTEGER
70 – 71
Airframe
Configuration
USHORT
72 – 73
74 – 77
Reserved
CRC32
USHORT
ULONG
78 – 79
USHORT
80 – 81
82 – 85
Offset
Compensation
Reserved
CRC32
86 – 87
Command
USHORT
88 – 91
CRC32
ULONG
92
93
DLE (0x10)
ETX (0x03)
BYTE
BYTE
01-000028-070F
USHORT
ULONG
Description
procedure. Range is -32768 (-20°) to +32767 (+19.9994°). The
AHRS applies a straight line interpolation of the offsets.
Correction offset value for East heading found during alignment
procedure. Range is -32768 (-20°) to +32767 (+19.9994°). The
AHRS applies a straight line interpolation of the offsets.
Correction offset value for South heading found during alignment
procedure. Range is -32768 (-20°) to +32767 (+19.9994°). The
AHRS applies a straight line interpolation of the offsets.
Correction offset value for West heading found during alignment
procedure. Range is -32768 (-20°) to +32767 (+19.9994°). The
AHRS applies a straight line interpolation of the offsets.
bits 0-3:
Filter number of Airspeed Filter
bits 4-7:
Filter number of Altitude Filter
bits 8-11:
Filter number of VSI Filter
bit 12:
ARINC429 SDI bit.
0 = ADAHRS#1.
1 = ADAHRS#2.
bit 13:
ARINC429 Air Data Enable on AHRS port.
0 = Inhibit.
1 = Enable.
bit 14:
Reserved (Always 0)
bit 15:
Reserved (Always 0)
Reserved for future use, currently always 0
CRC32 of bytes 2 through 73 of the packet. Note that the CRC32 is
calculated PRIOR to adding duplicate <DLE> characters and is
checked AFTER removing duplicate <DLE> characters. Besides
being used to validate the contents of this packet, this CRC32 is
reported in the AHRS data packet as the identifier for the calibration
data. This CRC32 is not checked when receiving the packet.
A 16 bit value to be added to calibrated output of the altitude or
airspeed pressure sensor to correct for offset drift.
Reserved for future use, currently always 0
CRC32 of the Offset Compensation EEPROM (bytes 78 to 81 of this
packet). Note that the CRC32 is calculated PRIOR to adding
duplicate <DLE> characters and is checked AFTER removing
duplicate <DLE> characters. This CRC32 is not checked when
receiving the packet.
bit 0:
0 = AHRS Calibration EEPROM should NOT be written
1 = AHRS Calibration EEPROM should be written
bits 1-2: 0 = Offset Compensation EEPROM should NOT be written
1 = Altitude Offset Compensation EEPROM should be
written
2 = Airspeed Offset Compensation EEPROM should be
written
3 = Offset Compensation EEPROM should NOT be written
bits 3-15:Reserved (Always 0)
CRC32 of bytes 2 through 87 of the packet. Note that the checksum
is calculated PRIOR to adding duplicate <DLE> characters and is
checked AFTER removing duplicate <DLE> characters
End Of Packet
End Of Packet
Chelton Flight Systems – Confidential
Page 39 of 104
5.2.4.2 Crossbow AHRS
5.2.4.2.1 Crossbow AHRS Communication Parameters
The communication standard shall [SYS_COM_041] be RS-232. Data shall
[SYS_COM_042] be transmitted with 8 data bits, 1 stop bit, and no parity.
Transmission speed shall [SYS_COM_043] be 9,600 baud.
5.2.4.2.2 Crossbow AHRS to IDU - Parameter Packet Description
The following data formats are used in the packet description:
BYTE
refers to 8 bit data (unsigned unless otherwise noted).
INTEGER
refers to a 16 or 32 bit signed number sent MSByte first.
The AHRS shall [SYS_COM_044] transmit the following data packet at a rate of 25 Hz:
Byte #
0–1
2–3
Parameter
Header
Roll Angle
Type
BYTES
INTEGER
4–5
Pitch Angle
INTEGER
6–7
Heading
INTEGER
8–9
Roll Rate
INTEGER
10 – 11
Pitch Rate
INTEGER
12 – 13
Heading Rate
INTEGER
14 – 15
INTEGER
20 – 21
22 – 23
X
Acceleration
Y
Acceleration
Z
Acceleration
Part Number
BIT
24 – 25
Checksum
INTEGER
16 – 17
18 – 19
INTEGER
INTEGER
INTEGER
INTEGER
Description
Packet Header (byte 0 = 0xAA, byte 1 = 0x55)
Roll Angle in (Degrees x 32768 / 180). Range is -32767 (-180°) to
+32767 (+180°). Right wing down is positive.
Pitch Angle in (Degrees x 32768 / 180). Range is -16383 (-90°) to
+16383 (+90°). Nose up is positive.
Heading Angle in (Degrees x 32768 / 180). Range is -32767 (-180°) to
+32767 (+180°). Headings clockwise from magnetic North are
positive.
Roll Rate in (Degrees / Sec x 32768 / 300). Range is -32767 (300°/sec) to +32767 (+300°/sec). Clockwise rotation is positive.
Pitch Rate in (Degrees / Sec x 32768 / 300). Range is -32767 (300°/sec) to +32767 (+300°/sec). Nose up rotation is positive.
Heading Rate in (Degrees / Sec x 32768 / 300). Range is -32767 (300°/sec) to +32767 (+300°/sec). Increasing heading is positive.
X Axis Acceleration in (G’s x 32768 / 15). Range is -32767 (-15G) to
+32767 (+15G). Acceleration opposite direction of flight is positive.
Y Axis Acceleration in (G’s x 32768 / 15). Range is -32767 (-15G) to
+32767 (+15G). Right lateral acceleration is positive.
Z Axis Acceleration in (G’s x 327678 / 15). Range is -32767 (-15G) to
+32767 (+15G). Acceleration upward is positive.
Part Number.
Built-In-Test value. Unit is ready for flight if bits 0, 1, 9, 10, and 13 are
all 0.
Two-byte sum of characters 2 through 23
The IDU shall [SYS_COM_106] transmit the following unsolicited data packet to the
AHRS at a rate of 1 Hz:
Byte #
0–1
2–5
Parameter
Header
GNSS
Latitude
01-000028-070F
Type
BYTES
INTEGER
Description
Packet Header (byte 0 = 0xAA, byte 1 = 0x55)
GNSS Latitude in ARINC 429 label 110 + 120 units. Range
is ±180°. Negative values represent South. Resolution is 31
bits. Invalid indicated by a value of 0xFFFFFFFF. Multiply
this integer by (180 / 231) to get degrees of GNSS latitude.
Chelton Flight Systems – Confidential
Page 40 of 104
Byte #
6–9
Parameter
GNSS
Longitude
Type
INTEGER
10 – 13
GNSS
Altitude
INTEGER
14 – 15
GNSS
Ground
Speed
INTEGER
16 – 17
GNSS
Track
INTEGER
18 – 19
GNSS
Vertical
Velocity
INTEGER
20 – 21
True
Airspeed
INTEGER
22 – 25
Pressure
Altitude
INTEGER
26 – 27
Barometric
Vertical
Velocity
INTEGER
28 – 29
Magnetic
Variation
INTEGER
30 – 31
Checksum
INTEGER
01-000028-070F
Description
GNSS Longitude in ARINC 429 label 111 + 121 units. Range
is ±180°. Negative values represent West. Resolution is 31
bits. Invalid indicated by a value of 0xFFFFFFFF (note that a
longitude value of W180° is encoded as +180). Multiply this
integer by (180 / 231) to get degrees of GNSS longitude.
GNSS Altitude in ARINC 429 label 076 units. Range is
±131072ft. Resolution is 20 bits. Invalid indicated by a value
of 0xFFFFFFFF. Multiply this integer by (131072/ 220) to get
feet of GNSS altitude.
GNSS Ground Speed in ARINC 429 label 112 units. Range
is 0 - 4096 knots. Resolution is 15 bits. Invalid indicated by a
value of 0xFFFF. Multiply this integer by (4096/ 215) to get
knots GNSS ground speed.
GNSS Track in ARINC 429 label 103 units. Range is ±180°.
Resolution is 15 bits. Invalid indicated by a value of 0xFFFF
(note that a track of 180° is encoded as +180). Multiply this
integer by (180/ 215) to get GNSS track in ° True.
GNSS Vertical Velocity in ARINC 429 label 165 units. Range
is ±32768 feet / min. Resolution is 15 bits. Invalid indicated
by a value of 0xFFFF. Multiply this integer by (32768/ 215) to
get GNSS vertical velocity in feet / min.
True Airspeed in ARINC 429 label 210 units. Range is 0 2048 knots. Resolution is 15 bits. Invalid indicated by a
value of 0xFFFF. Multiply this integer by (2048/ 215) to get
knots true airspeed.
Pressure Altitude in ARINC 429 label 203 units. Range is
±131072ft. Resolution is 17 bits. Invalid indicated by a value
of 0xFFFFFFFF. Multiply this integer by (131072/ 217) to get
feet of pressure altitude.
Instantaneous (G-Force quickened) Barometric Vertical
Velocity in ARINC 429 label 212 units. Range is ±32768 feet
/ min. Resolution is 11 bits. Invalid indicated by a value of
0xFFFF. Multiply this integer by (32768/ 211) to get
instantaneous barometric vertical velocity in feet / min.
Magnetic Variation in ARINC 429 label 147G units. Range is
±180°. Negative values represent Westerly variation.
Resolution is 12 bits. Invalid indicated by a value of 0xFFFF.
Multiply this integer by (180/ 212) to get degrees of magnetic
variation.
Two-byte sum of characters 2 through 29
Chelton Flight Systems – Confidential
Page 41 of 104
5.2.5 ADC
The ADC shall [SYS_COM_045] be either a Chelton ADC or a Shadin Company part
number 962831A-1-S-8 (pulse-type fuel flow sensor), 962831A-2-S-8 (sin wave-type
fuel flow sensor), or 962831A-3-S-8 (DC type fuel flow sensor) certified to TSO-C44c
and C106. Half-duplex communications between the ADC and the IDU shall
[SYS_COM_046] use IDU COM13 (for ADC1) and IDU COM14 (for ADC2). The IDU
will perform the necessary display functions so that the combination of the ADC and an
IDU will meet the requirements for TSO-C2d, C8d, and C10b. ADC parameters may
also be acquired through the ARINCC429 bus, in which case installation of an RS-232
ADC is not required. Future capabilities may include interfaces to other ADCs.
The IDU shall [SYS_COM_149] continuously attempt to connect to an ADC, either the
Chelton ADC or a Shadin ADC. If no response is received within two seconds, the IDU
shall [SYS_COM_150] attempt to connect to the other ADC type.
5.2.5.1 Chelton ADC
5.2.5.1.1 Chelton ADC Communication Parameters
Communications shall [SYS_COM_151] take place at 9,600 baud, 9 bits, no parity, non
return to zero serial protocol using a RS-232 physical interface. The serial protocol shall
[SYS_COM_194] use the 9th bit to identify packet framing. The 9th bit shall
[SYS_COM_195] be set only for the last character of a packet and shall
[SYS_COM_196] be cleared for all other characters. The set 9th bit will uniquely identify
the last character of the packet, regardless of the contents of the lower 8 bits.
5.2.5.1.2 Chelton ADC Packet Description
The ADC shall [SYS_COM_176] transmit the following packet at a rate of 25 Hz:
Byte #
0-1
Parameter
Data Validity
and system
BIT Flags
Data Type
USHORT
bit 0:
bit 1:
bit 2:
bit 3:
bit 4:
bit 5:
bit 6:
bit 7:
01-000028-070F
Description
0 = Indicates Airspeed valid
1 = Indicates Airspeed invalid
0 = Indicates Altitude, Altitude Rate valid
1 = Indicates Altitude, Altitude Rate invalid
0 = Indicates Temperature valid
1 = Indicates Temperature invalid
Reserved (Always 0)
Reserved (Always 0)
Reserved (Always 0)
Reserved (Always 0)
Reserved (Always 0)
Chelton Flight Systems – Confidential
Page 42 of 104
Byte #
Parameter
Data Type
Description
Reserved (Always 0)
Reserved (Always 0)
Reserved (Always 0)
Reserved (Always 0)
Reserved (Always 0)
0 = Indicates ADC is using airframe dependent filters
1 = Indicates ADC is using generic filters. The dynamic
accuracy may be degraded. The static accuracy is not affected.
bit 14: 0 = Indicates ADC is at operating temperature
1 = Indicates ADC is outside its validated calibrated temperature.
Airspeed and altitudes may be inaccurate.
bit 15: 0 = Indicates ADC passed Power On Self-test
1 = Indicates ADC failed Power On Self-test
Indicated Airspeed in hundredths of a knot (Knots x 100). Range is 0 (0
KIAS) to 65,535 (655.35 KIAS).
Pressure Altitude in feet offset by 1000 (feet + 1000). Range is 0
(-1000 ft) to 65,535 (64,535 ft).
Altitude Rate in feet per minute. Range is -32,768fpm to +32,767 fpm.
Temperature in hundredths of a degree Celsius (°C x 100). Range is 32,768 (-327.68°C) to +32.767 (+326.67°C). Valid values are
-100.00°C to +100.00°C
Checksum of bytes 0 through 9, calculated as a binary sum of the
unsigned bytes plus the constant 0x5555. Note that the last character of
the packet has the 9th bit set, indicating the end of the packet.
bit 8:
bit 9:
bit 10:
bit 11:
bit 12:
bit 13:
2–3
4–5
6–7
8–9
10 – 11
Indicated
Airspeed
Pressure
Altitude
Altitude Rate
Total Air
Temperature
USHORT
Checksum
USHORT
USHORT
INTEGER
INTEGER
5.2.5.2 Shadin ADC
5.2.5.2.1 Shadin Communication Parameters
The communication standard shall [SYS_COM_047] be RS-232. Data shall
[SYS_COM_048] be transmitted with 8 data bits, 1 stop bit, and no parity.
Transmission speed shall [SYS_COM_049] be 9,600 baud.
5.2.5.2.2 Shadin Packet Description
The ADC shall [SYS_COM_050] transmit unsolicited data packets at a rate of 4 Hz. In
order to support this transmission rate with available bandwidth, and to minimize
custom programming by Shadin, the packet will be an abbreviated and slightly modified
version of Shadin’s S-Data Format. Each packet shall [SYS_COM_051] be a series of
ASCII message strings. Each packet shall [SYS_COM_052] begin with a start of text
character (<STX> 0x02), shall [SYS_COM_053] include data message strings for fuel
flow and air data parameters, and shall [SYS_COM_054] terminate with a checksum
message and an end of text character (<ETX> 0x03).
Each data message string shall [SYS_COM_055] begin with a two-character,
alphabetic identifier to identify the contents of the message string, shall
01-000028-070F
Chelton Flight Systems – Confidential
Page 43 of 104
[SYS_COM_056] include ASCII numeric or alphanumeric data fields, and shall
[SYS_COM_057] end with a carriage return character (<CR> 0x0d) and a line feed
character (<LF> 0x0a). All ASCII numeric fields shall [SYS_COM_058] be ASCII
decimal, right justified with leading zeroes. Each packet shall [SYS_COM_059] include
message strings for indicated airspeed, pressure altitude, true air temperature, vertical
speed, and system error code. Each packet may include message strings for right
engine fuel flow and left engine fuel flow.
The ADC shall [SYS_COM_060] begin transmitting packets immediately upon start up
to support IDU initialization. As the ADC does not reach full accuracy until reaching
operational temperature, data packets initially transmitted may not meet the accuracy
requirements of TSO-C106. During this warm-up period, the ADC shall
[SYS_COM_061] transmit an error code value of ASCII “001.” A complete data packet
including optional right engine fuel flow and left engine fuel flow shall [SYS_COM_062]
be as follows (d = ASCII decimal digit, s = ASCII sign character):
Message
<STX>
SAddd<CR><LF>
SDsdddd<CR><LF>
SGsdd<CR><LF>
SKsddd<CR><LF>
SMdddd<CR><LF>
SOdddd<CR><LF>
SQddd<CR><LF>
S*ddd<CR><LF>
<ETX>
01-000028-070F
Message Description
Start of Text Character
Indicated Air Speed in Knots
000
= Value Under Range
999
= Value Over Range
Pressure Altitude in Tens of Feet
-9999 = Value Under Range
+9999 = Value Over Range
True Air Temperature in C
-99
= Value Under Range
+99
= Value Over Range
Vertical Speed in Tens of Feet per Minute
-999
= Value Under Range
+999 = Value Over Range
Right Engine Fuel Flow in Tenths of Gallons per Hour
0000 = Value Under Range
9999 = Value Over Range
Left Engine Fuel Flow in Tenths of Gallons per Hour
0000 = Value Under Range
9999 = Value Over Range
Error Code
000
= System OK
001
= Quick Start Warm Up Mode
Checksum: ASCII decimal representation of one byte checksum (discarding carries)
of all characters from <STX> up to and including the <LF> for the SQ message string.
End of Text Character
Chelton Flight Systems – Confidential
Page 44 of 104
5.2.6 Fuel Flow
When an ADC is used that does not provide fuel flow data, a dedicated fuel flow system
may be used. The dedicated fuel flow system shall [SYS_COM_267] be a Shadin
Company part number 962831A-1-S-8 (pulse-type fuel flow sensor), 962831A-2-S-8 (sin
wave-type fuel flow sensor), or 962831A-3-S-8 (DC type fuel flow sensor) certified to
TSO-C44c. Half-duplex communications between the dedicated fuel flow system and the
IDU shall [SYS_COM_268] use IDU COM15. The IDU will perform the necessary display
functions so that the combination of the dedicated fuel flow system will meet the
requirements for TSO-C44c. Air data parameters shall [SYS_COM_269] not be acquired
from the dedicated fuel flow system. Future capabilities may include interfaces to other
fuel flow systems. A complete data packet shall [SYS_COM_293] be as follows (d =
ASCII decimal digit, s = ASCII sign character):
Message
<STX>
SMdddd<CR><LF>
SOdddd<CR><LF>
SQddd<CR><LF>
S*ddd<CR><LF>
<ETX>
01-000028-070F
Message Description
Start of Text Character
Right Engine Fuel Flow in Tenths of Gallons per Hour
0000 = Value Under Range
9999 = Value Over Range
Left Engine Fuel Flow in Tenths of Gallons per Hour
0000 = Value Under Range
9999 = Value Over Range
Error Code
000
= System OK
001
= Quick Start Warm Up Mode
Checksum: ASCII decimal representation of one byte checksum (discarding carries)
of all characters from <STX> up to and including the <LF> for the SQ message string.
End of Text Character
Chelton Flight Systems – Confidential
Page 45 of 104
5.2.7 Analog Interface
The optional analog interface shall [SYS_COM_063] be a Chelton Flight Systems AIU1 or AIU-2. Duplex communications between the analog interface and the IDUs shall
[SYS_COM_064] use COM6.
5.2.7.1 Communication Parameters
The communication standard shall [SYS_COM_065] be RS-232. Data shall
[SYS_COM_066] be transmitted with 8 data bits, 1 stop bit, and no parity.
Transmission speed shall [SYS_COM_067] be 9,600 baud.
5.2.7.2 Packet General Description
Each packet shall [SYS_COM_068] be a series of ASCII characters arranged in a
proprietary NMEA-0183 style format. Each packet shall [SYS_COM_069] begin with a
dollar sign character (<$> 0x24) and packet identifier, shall [SYS_COM_070] include
ASCII data, and shall [SYS_COM_071] terminate with a checksum message and a
carriage return character (<CR> 0x0d). All ASCII numeric fields shall [SYS_COM_072]
be ASCII decimal, right justified with leading zeroes.
5.2.7.3 Continuous Analog Interface Packet Output
The analog interface shall [SYS_COM_073] transmit the following unsolicited data
packet at a rate of 10-20 Hz:
Byte #
0-6
7 - 11
12
13 - 17
18
19 - 23
24
25 - 29
30
31
32
Parameter
ID
VOR A
Radial
Delimiter
VOR B
Radial
Delimiter
LOC A
Deviation
Delimiter
LOC B
Deviation
Delimiter
Marker
Beacon
Type
ASCII Text
ASCII
Decimal
ASCII Text
ASCII
Decimal
ASCII Text
ASCII
Decimal
ASCII Text
ASCII
Decimal
ASCII Text
ASCII Text
Units
N/A
0.1°
Delimiter
ASCII Text
N/A
01-000028-070F
N/A
0.1°
N/A
0.01
Dots
N/A
0.01
Dots
N/A
N/A
Description
Packet Identification for AIU-1 output: “$PSAIU,”
“000.0” = Invalid
“000.1” to “360.0” = VOR A Radial
“,”
“000.0” = Invalid
“000.1” to “360.0” = VOR B Radial
“,”
“-9.99” = Invalid
“-8.00” to “+8.00” = LOC A Deviation (+ = Right)
“,”
“-9.99” = Invalid
“-8.00” to “+8.00” = LOC B Deviation (+ = Right)
“,”
“N” = No Marker Beacon Signal.
“O” = Active Outer Marker Beacon Signal.
“M” = Active Middle Marker Beacon Signal.
“A” = Active Airway/Inner Marker Beacon Signal.
“,”
Chelton Flight Systems – Confidential
Page 46 of 104
Byte #
33 - 37
38
39 - 43
44
45 - 48
49
50 - 54
55
56 - 60
61
62 - 66
67
68 - 75
Parameter
GS A
Deviation
Delimiter
GS B
Deviation
Delimiter
Radar
Altitude
Delimiter
ADF Bearing
Delimiter
FD Lateral
Command
Delimiter
FD Vertical
Command
Delimiter
Binary
Discretes
Type
ASCII
Decimal
ASCII Text
ASCII
Decimal
ASCII Text
ASCII
Decimal
ASCII Text
ASCII
Decimal
ASCII Text
ASCII
Decimal
ASCII Text
ASCII
Decimal
ASCII Text
ASCII
Binary
Units
0.01
Dots
N/A
0.01
Dots
N/A
Feet
N/A
1°C
N/A
0.1°
N/A
0.1°
N/A
0.1°
N/A
“0” or
“1”
76
77 - 80
Delimiter
Temperature
81
82 - 85
Delimiter
SW Version
ASCII Text
ASCII
Decimal
ASCII Text
ASCII Text
86 - 87
Checksum
ASCII Hex
N/A
88
End
ASCII
<CR>
N/A
N/A
Description
“-9.99” = Invalid
“-8.00” to “+8.00” = GS A Deviation (+ = Up)
“,”
“-9.99” = Invalid
“-8.00” to “+8.00” = GS B Deviation (+ = Up)
“,”
“9999” = Invalid
“0000” to “5000” = Radar Altitude
“,”
“000.0” = Invalid
“000.1” to “360.0” = ADF Bearing
“,”
“-99.9” = Invalid
“-60.0” to “+60.0” = FD Lateral (Roll) Command (+ = Right)
“,”
“-99.9” = Invalid
“-30.0” to “+30.0” = FD Vertical (Pitch) Command (+ = Up)
“,”
8 digits where each digit is set to ASCII “0” or “1” depending
upon the state of the binary discrete associated with the
digit. “0” represents a grounded state, “1” represents an
ungrounded state.
“,”
“9999” = Invalid
“-060” to “+100” = °C
“,”
AIU-1: SW Version in format “#.#,”
AIU-1A or AIU-2: “222,”
ASCII Hex value of a 1 byte XOR checksum of bytes 1
through 85.
Carriage return character (0x0d).
5.2.7.4 Continuous Analog Interface Packet Input
The IDU shall [SYS_COM_074] transmit the following unsolicited data packet to the
AIU-1 at a rate of 10-20 Hz:
Byte #
0–6
7 – 10
Parameter
ID
Left Lateral
Deviation
(Fly Left)
Type
ASCII Text
ASCII
Decimal
Units
N/A
-.15
mV
11
12 –
15
Delimiter
Right
Lateral
Deviation
(Fly Right)
ASCII Text
ASCII
Decimal
N/A
+.15
mV
16
17 –
20
Delimiter
Heading
Datum
ASCII Text
ASCII
Decimal
N/A
0.1°
21
Delimiter
ASCII Text
N/A
01-000028-070F
Description
Packet Identification for Chelton IDU Sentence: “$PSAUT,”
Left Lateral Deviation: Range of “0000” to “1000.” Value of
“1000” causes transmission of (-150mV) from Lateral
Deviation Analog Output. If this value is non-zero, the Right
Lateral Deviation must be zero. Ref: 7.0F IDU Autopilot
Interface Requirements doc 01-000051-070F
“,”
Right Lateral Deviation: Range of “0000” to “1000.” Value of
“1000” causes transmission of (+150mV) from Lateral
Deviation Analog Output. If this value is non-zero, the Left
Lateral Deviation must be zero. Ref: 7.0F IDU Autopilot
Interface Requirements doc 01-000051-070F
“,”
Heading Datum: Range of “-900” to “+900” (degrees times
ten). Ref: 7.0F IDU Autopilot Interface Requirements doc 01000051-070F
“,”
Chelton Flight Systems – Confidential
Page 47 of 104
Byte #
22 –
25
Parameter
Course
Datum
Type
ASCII
Decimal
Units
0.1°
26
27
Delimiter
NAV Flag
ASCII Text
ASCII
Binary
N/A
“0” or
“1”
28
29
Delimiter
Glideslope
Select
ASCII Text
ASCII
Binary
N/A
“0” or
“1”
30
31 –
32
33
Delimiter
Checksum
ASCII Text
ASCII Hex
N/A
N/A
End
ASCII
<CR>
Description
Course Datum: Range of “-900” to “+900” (degrees times
ten). Ref: 7.0F IDU Autopilot Interface Requirements doc 01000051-070F
“,”
NAV Flag: Indicates to autopilot whether lateral deviation
signal is valid. ASCII “1” indicates that signal is valid. ASCII
“0” indicates that signal is invalid. Ref: 7.0F IDU Autopilot
Interface Requirements doc 01-000051-070F
“,”
Glideslope Select: Actuates a relay to connect the selected
NAV radio ILS energize, glideslope flag and glideslope
deviation signals to the autopilot. ASCII “0” is the default and
connects the #1 NAV radio signals to the autopilot. ASCII “1”
connects the #2 NAV radio signals to the autopilot.
“,”
ASCII Hex value of a 1 byte XOR checksum of bytes 1
through 30.
Carriage return character (0x0d).
The IDU shall [SYS_COM_270] transmit the following unsolicited data packet to the
AIU-1A or AIU-2 at a rate of 10-20 Hz:
Byte #
Parameter
0–6
ID
7 – 10
Left Lateral
Deviation
(Fly Left)
11
12 –
15
16
17 –
20
21
22 –
25
Delimiter
Right
Lateral
Deviation
(Fly Right)
Delimiter
Down
Vertical
Deviation
(Fly Down)
Delimiter
Up Vertical
Deviation
(Fly Up)
Type
Units
Description
ASCII Text
N/A
Packet Identification for Chelton IDU Sentence: “$PSAU3,”
ASCII
Decimal
-.5 mV
Left Lateral Deviation: Range of “0000” to “1000.” Value of
“1000” causes transmission of (-500mV) from Lateral
Deviation Analog Output. If this value is non-zero, the Right
Lateral Deviation must be zero. Ref: 7.0F IDU Autopilot
Interface Requirements doc 01-000051-070F
ASCII Text
N/A
“,”
ASCII
Decimal
+.5
mV
Right Lateral Deviation: Range of “0000” to “1000.” Value of
“1000” causes transmission of (+500mV) from Lateral
Deviation Analog Output. If this value is non-zero, the Left
Lateral Deviation must be zero. Ref: 7.0F IDU Autopilot
Interface Requirements doc 01-000051-070F
ASCII Text
N/A
“,”
ASCII
Decimal
-.5 mV
ASCII Text
N/A
“,”
ASCII
Decimal
+.5
mV
Up Vertical Deviation: Range of “0000” to “1000.” Value of
“1000” causes transmission of (+500mV) from Vertical
Deviation Analog Output. If this value is non-zero, the Down
Vertical Deviation must be zero. Ref: 7.0F IDU Autopilot
Interface Requirements doc 01-000051-070F
Down Vertical Deviation: Range of “0000” to “1000.” Value
of “1000” causes transmission of (-500mV) from Vertical
Deviation Analog Output. If this value is non-zero, the Up
Vertical Deviation must be zero. Ref: 7.0F IDU Autopilot
Interface Requirements doc 01-000051-070F
26
Delimiter
ASCII Text
N/A
“,”
27 –
30
Heading
Datum
ASCII
Decimal
0.1°
Heading Datum: Range of “-900” to “+900” (degrees times
ten). Ref: 7.0F IDU Autopilot Interface Requirements doc 01000051-070F
01-000028-070F
Chelton Flight Systems – Confidential
Page 48 of 104
Byte #
31
Parameter
Delimiter
32 –
35
Course
Datum
Type
Units
ASCII Text
N/A
“,”
ASCII
Decimal
0.1°
Course Datum: Range of “-900” to “+900” (degrees times
ten). Ref: 7.0F IDU Autopilot Interface Requirements doc 01000051-070F
“,”
36
Delimiter
ASCII Text
N/A
37
NAV Flag
ASCII
Binary
“0” or
“1”
38
Delimiter
ASCII Text
N/A
39
GS Valid
Flag
ASCII
Binary
“0” or
“1”
40
Delimiter
ASCII Text
N/A
41
ILS
Energize
Flag
ASCII
Binary
“0” or
“1”
42
Delimiter
ASCII Text
N/A
43
Glideslope
Select
ASCII
Binary
44
Delimiter
ASCII Text
N/A
Checksum
ASCII Hex
N/A
ASCII
<CR>
45 –
46
47
End
“0” or
“1”
Description
NAV Flag: Indicates to autopilot whether lateral deviation
signal is valid. ASCII “1” indicates that signal is valid. ASCII
“0” indicates that signal is invalid. Ref: 7.0F IDU Autopilot
Interface Requirements doc 01-000051-070F
“,”
GS Valid Flag: Indicates to autopilot whether vertical
deviation signal is valid. ASCII “1” indicates that signal is
valid. ASCII “0” indicates that signal is invalid. Ref: 7.0F IDU
Autopilot Interface Requirements doc 01-000051-070F
“,”
ILS Energize Flag: Indicates to autopilot whether lateral
deviation is a VOR deviation or Localizer deviation. ASCII “1”
indicates Localizer. ASCII “0” indicates VOR. Ref: 7.0F IDU
Autopilot Interface Requirements doc 01-000051-070F
“,”
Glideslope Select: Actuates a relay to connect the selected
NAV radio ILS energize, glideslope flag and glideslope
deviation signals to the autopilot. ASCII “0” is the default and
connects the #1 NAV radio signals to the autopilot. ASCII “1”
connects the #2 NAV radio signals to the autopilot. Note that
this value is only used by AIU-1A variant. This field is
discarded by AIU-2.
“,”
ASCII Hex value of a 1 byte XOR checksum of bytes 1
through 44.
Carriage return character (0x0d).
Heading Datum shall [SYS_COM_099] be calculated according to the following order of
precedence (ref: 7.0F IDU Autopilot Interface Requirements doc 01-000051-070F):
1. If the IDU heading bug is active, the heading datum gives the difference, in
degrees, between current heading and selected heading. Positive degrees
indicate that selected heading is right of current heading.
2. If the IDU heading bug is not active and a navigation route is active, the heading
datum gives roll steering commands, in degrees of bank angle, to the active
navigation route. Positive degrees indicate that a right turn is commanded. The
default intercept angle to the navigation route is 45°. This can be altered by the
user by using the heading bug to activate an “all-angle” intercept feature. In this
01-000028-070F
Chelton Flight Systems – Confidential
Page 49 of 104
mode, the user sets the heading bug to intercept the navigation route at a
desired intercept angle between 0° and 135°. Upon deactivating the heading
bug, the roll steering command will maintain the last set heading until the
aircraft reaches the intercept location.
3. If neither the heading bug nor a navigation route are active, then the heading
datum will put out a 0° command to keep the wings level.
Course Datum shall [SYS_COM_100] give the difference, in degrees, between
current heading and the applicable selected course (ref: 7.0F IDU Autopilot
Interface Requirements doc 01-000051-070F). Maximum difference shall
[SYS_COM_133] be 90°. Differences greater than 90° shall [SYS_COM_134]
result in decreased difference values such that, at 180°, the difference is reported
as 0°. The intent of smoothly reducing the difference values beyond 90° is to mimic
the behavior of a sine wave to enable functioning of autopilot back course modes.
Positive degrees shall [SYS_COM_101] indicate that selected course is right of
current heading. The applicable selected course shall [SYS_COM_102] be
determined by the HSI source parameter and is either: (1) the automatic GPS OBS
setting (if HSI source is GPS and automatic OBS is selected); (2) the manual GPS
OBS setting (if HSI source is GPS and manual OBS is selected); or (3) the VOR
OBS setting (if HSI source is VOR).
01-000028-070F
Chelton Flight Systems – Confidential
Page 50 of 104
5.2.8 NAT Transponder
Communication from the IDUs to the optional NAT Transponder shall [SYS_COM_295]
use COM6.
5.2.8.1 Communication Parameters
The communication standard shall [SYS_COM_296] be RS-232. Data shall
[SYS_COM_297] be transmitted with 8 data bits, 1 stop bit, and no parity.
Transmission speed shall [SYS_COM_298] be 9,600 baud.
5.2.8.2 Packet General Description
Each packet shall [SYS_COM_299] be a series of ASCII characters arranged in a
proprietary Shadin Protocol format as defined in section 2.5 of the Altimeters Protocols
Specification, attached as Appendix E. Each packet shall [SYS_COM_300] begin with
a packet ID, shall [SYS_COM_301] include ASCII data, and shall [SYS_COM_302]
terminate with a checksum message and a carriage return character (<CR> 0x0d). All
ASCII numeric fields shall [SYS_COM_303] be ASCII decimal, right justified with
leading zeroes.
5.2.8.3 Continuous Packet Output
The IDU shall [SYS_COM_304] transmit the following unsolicited data packet at the
rate of 1 Hz:
Byte #
1-3
Parameter
ID
4
Delimiter
5
Sign
6 - 10
Altitude
11
Delimiter
12
Sign
13 -14
15 16
17
Units
N/A
Description
Packet Identification for output: “RMS”
N/A
Space: “ “
N/A
‘+’ (0x2b) or ‘-‘ (0x2d)
Feet
N/A
Altitude in feet, right justified, with leading ASCII
zeros.
‘T’ (0x54)
N/A
‘+’ (0x2b) or ‘-‘ (0x2d)
Sensor
Temperature
Checksum
Type
ASCII
Text
ASCII
Text
ASCII
Text
ASCII
Decimal
ASCII
Text
ASCII
Text
ASCII
Decimal
ASCII Hex
°C
N/A
Temperature in °C, right justified, with leading ASCII
zeros.
ASCII Hex value sum of bytes 1 through 14.
End
ASCII
<CR>
Carriage return character (0x0d).
01-000028-070F
Chelton Flight Systems – Confidential
Page 51 of 104
5.2.9 Navigation and Flight Plan Data Transmission
Type 1 (“ARNAV format”) and Type 2 (“Northstar format”) navigation and flight plan
data shall [SYS_COM_109] be transmitted on COM9.
5.2.9.1 Communication Parameters
The communication standard shall [SYS_COM_110] be RS-422. Data shall
[SYS_COM_111] be transmitted with 8 data bits, 1 stop bit, and no parity. Transmission
speed shall [SYS_COM_112] be 9,600 baud.
5.2.9.2 Packet General Description
The IDU shall [SYS_COM_113] transmit unsolicited data packets at a rate of 0.5 Hz.
Output data shall [SYS_COM_114] have the following format:
<STX><id><dddd><it><id><dddd><it>...<id><dddd><it><ETX>
where:
<STX>
ASCII start of text character (0x02)
<id>
Item Designator
<dddd>
Item Data
<it>
Item Terminator: <CR>
<ETX>
ASCII end of text character (0x03)
Item designators shall [SYS_COM_115] be as follows:
Item
Designator
Item
Format
Field
Width
A
s dd
mmhh
9
B
s ddd
mmhh
10
C
D
E
G
ddd
ddd
ddddd
sdddd
3
3
5
5
I
dddd
4
01-000028-070F
Item Description
Type 1 Data
Present Latitude:
s = sign (N = North, S = South)
dd = degrees
mm = minutes
hh = hundredths of minutes
Present Longitude
s = sign (E = East, W = West)
ddd = degrees
mm = minutes
hh = hundredths of minutes
Magnetic Track in Degrees
Ground Speed in Knots
Distance to active waypoint in tenths of nautical miles
Cross track error in hundredths of nautical miles
s = sign (R = Right of Course, L = Left of Course)
Desired track in tenths of magnetic degrees
Chelton Flight Systems – Confidential
Page 52 of 104
Item
Designator
K
L
Q
Item
Format
ddddd
dddd
sddd
Field
Width
5
4
4
T
NA
9
l
w
dddddd
see
below
6
17
Item Description
Active waypoint identifier (ASCII, left justified)
Bearing to active waypoint in tenths of magnetic degrees
Magnetic Variation in tenths of degrees
s = sign (E = East, W = West)
Marks end of Type 1 data, always dashed (“---------”)
Type 2 Data
Distance to destination in tenths of nautical miles
Flight Plan Data, one item per waypoint (including SUPPRESSed
waypoints) in active flight plan. If no flight plan, transmit “w01[65]----0000000[0x7f]0[\r].”
With the exception of flight plan data and item designators E and L, invalid items shall
[SYS_COM_116] be filled with dashes. Item designators E and L shall
[SYS_COM_135] be filled with zeroes when invalid. Item designator “w” (flight plan
data) shall [SYS_COM_118] have the following format:
Byte
1-2
3
Bit Format
ASCII
xlannnnn
4-8
9
aaaaaaaa
sddddddd
10
xxmmmmmm
11
xhhhhhhh
12
sxxxxxxx
13
dddddddd
14
xxmmmmmm
15
xhhhhhhh
16 – 17
01-000028-070F
Description
Waypoint number (“01” through “32”)
Sequence Number:
x
= undefined
l
= 1 if last waypoint of flight plan
a
= 1 if waypoint is active
nnnnn
= Sequence Number (unsigned binary)
Waypoint identifier (ASCII, left justified)
Latitude sign and degrees:
s
= sign (0 = North, 1 = South)
ddddddd
= Latitude degrees
Note: Value 0x7f indicates that latitude and longitude are invalid.
Latitude minutes:
x
= undefined
mmmmmm
= Latitude minutes
Latitude hundredths of minutes
x
= undefined
hhhhhhh
= Latitude hundredths of minutes
Longitude sign
s
= sign (0 = East, 1 = West)
x
= undefined
Longitude degrees:
dddddddd
= Latitude degrees
Longitude minutes:
x
= undefined
mmmmmm
= Latitude minutes
Longitude hundredths of minutes
x
= undefined
hhhhhhh
= Latitude hundredths of minutes
Two’s complement 16-bit magnetic variation at waypoint in sixteenths of
degrees. Easterly variation is positive. A value of 0x7f in byte 16 indicates
that magnetic variation is invalid.
Chelton Flight Systems – Confidential
Page 53 of 104
5.2.10 Remote NAV and COM Tuning Data
Remote tuning commands for Honeywell KX155A/165A and Garmin SL30/SL40 radios
shall [SYS_COM_123] be transmitted on COM9. The IDU shall [SYS_COM_177] also
receive packets from the Garmin SL30 on COM9.
5.2.10.1 Communication Parameters
The communication standard shall [SYS_COM_124] be RS-422. Data shall
[SYS_COM_125] be transmitted with 8 data bits, 1 stop bit, and no parity.
Transmission speed shall [SYS_COM_126] be 9,600 baud.
5.2.10.2 Transmitted Packet General Description
The IDU shall [SYS_COM_127] transmit unsolicited data packets in response to pilot
menu entries that change a communication or navigation radio frequency. Either a
Honeywell, Garmin, or neither packet shall [SYS_COM_128] be transmitted according
to the aircraft limits settings.
Honeywell packets shall [SYS_COM_129] have the following format:
<STX><id><dddd><it><id><dddd><it>...<id><dddd><it><ETX>
where:
<STX>
ASCII start of text character (0x02)
<id>
Item Designator
<dddd>
Item Data
<it>
Item Terminator: <CR>
<ETX>
ASCII end of text character (0x03)
Item designator shall [SYS_COM_130] be as follows:
Item
Designator
q
01-000028-070F
Item
Format
snfffff
Field
Width
7
Item Description
s = System Type (“1” = COM, “2” = NAV)
n = Radio Number (“1” or “2”)
fffff = Frequency in thousandths of MHz with 100MHz unit dropped
(i.e., 121.225 = “21225”, 117.900 = “17900”)
Chelton Flight Systems – Confidential
Page 54 of 104
The IDU shall [SYS_COM_131] transmit the Garmin packets for the SL-30 radio with
the following format:
Byte #
0-5
Parameter
ID
Units
N/A
Description
Packet Identification for Garmin output: “$PMRRC”
N/A
Frequency
Type
ASCII
Text
ASCII
Text
Binary
6-7
Radio Type
9
Frequency
Binary
KHz
10
Receiver
Function
Checksum
ASCII
Text
ASCII Hex
N/A
“28” = NAV System
“29” = COM System
Hexadecimal desired frequency in MHz. Value is
(desired frequency - 0x30). Range is 118 to 135 MHz.
For example, a value of 117 would be coded as ASCII “E”
or 0x45 (0x45 + 0x30 = 0x75 = 117).
Hexadecimal desired frequency in KHz. Value is (desired
frequency / 25KHz + 0x30). Range is 000 to 975 KHz in
25 KHz steps. For example, a value of 100 would be
coded as ASCII “4” or 0x34 (0x34 - 0x30 = 0x04 = 4 . . . x
25KHz = 100KHz).
“N” = normal; “M” = monitor; “0” = unchanged
8
End
ASCII
<CR><LF>
11 12
13 14
MHz
N/A
One byte message checksum generated by adding
characters 6 through 10, ignoring carry. This value is
converted into two encoded hex characters (0x30 - 0x3f).
Encoded hex consists of 4 bits of data placed in the low
order nibble + 0x30. For example, the one byte value
0x5F would be encoded as two characters with values of
0x35 (“5”) and 0x3f (“?”) respectively.
Carriage return character (0x0d) and line feed character
(0x0a).
The IDU shall [SYS_COM_136] transmit the Garmin packets for the SL-40 radio with
the following format:
Byte #
0-5
Parameter
ID
Units
N/A
Description
Packet Identification for Garmin output: “$PMRRC”
N/A
Frequency
Type
ASCII
Text
ASCII
Text
Binary
6-7
Radio Type
9
Frequency
Binary
KHz
10
Receiver
Function
Checksum
ASCII
Text
ASCII Hex
N/A
“01” = COM System Only – No message generated for
NAV
Hexadecimal desired frequency in MHz. Value is
(desired frequency - 0x30). Range is 118 to 135 MHz.
For example, a value of 117 would be coded as ASCII “E”
or 0x45 (0x45 + 0x30 = 0x75 = 117).
Hexadecimal desired frequency in KHz. Value is (desired
frequency / 25KHz + 0x30). Range is 000 to 975 KHz in
25 KHz steps. For example, a value of 100 would be
coded as ASCII “4” or 0x34 (0x34 - 0x30 = 0x04 = 4 . . . x
25KHz = 100KHz).
“N” = normal; “M” = monitor; “0” = unchanged
8
End
ASCII
<CR><LF>
11 12
13 14
01-000028-070F
MHz
N/A
One byte message checksum generated by adding
characters 6 through 10, ignoring carry. This value is
converted into two encoded hex characters (0x30 - 0x3f).
Encoded hex consists of 4 bits of data placed in the low
order nibble + 0x30. For example, the one byte value
0x5F would be encoded as two characters with values of
0x35 (“5”) and 0x3f (“?”) respectively.
Carriage return character (0x0d) and line feed character
(0x0a).
Chelton Flight Systems – Confidential
Page 55 of 104
5.2.10.3 Received Packet General Description
The IDU shall [SYS_COM_178] receive the following packets from the Garmin SL30:
Byte #
0-5
Parameter
ID
Units
N/A
Message
Identifier
CDI
Deflection
Type
ASCII
Text
ASCII
Text
ASCII
Hex
6–7
10 - 11
GSI
Deflection
ASCII
Hex
N/A
12 – 13
HNAV and
VNAV
Flags
ASCII
Hex
N/A
13 – 14
Checksum
ASCII
Hex
N/A
15 - 16
End
ASCII
<CR><LF>
8-9
N/A
N/A
Description
Packet Identification for Garmin VHF NAV message:
“$PMRRV”
“21” = CDI, GSI, and Related Flags
Indicates the amount of deflection of the CDI needle,
represented as two encoded hex1 digits. The CDI
deflection is a two’s complement signed integer in the
range of -100 to 100. -100 indicates full left deflection, 0
indicates no deflection, and 100 indicates full right
deflection.
Indicates the amount of deflection of the GSI needle,
represented as two encoded hex1 digits. The CDI
deflection is a two’s complement signed integer in the
range of -100 to 100. -100 indicates full deflection
upwards, 0 indicates no deflection, and 100 indicates full
deflection downwards.
Eight bits represented as two encoded hex digits.
Bit 1 (lsb): Back Course Enable (1 = enabled)
Bit 2: Localizer detect (1 = using localizer)
Bit 3: FROM flag (1 = From)2
Bit 4: TO flag (1 = To)
Bit 5: GSI Superflag (1 = valid)
Bit 6: GSI Valid (1 = valid)
Bit 7: NAV Superflag (1 = valid)
Bit 8 (msb): NAV Valid (1 = valid)
One byte message checksum generated by adding
characters 6 through 10, ignoring carry. This value is
converted into two encoded hex characters (0x30 - 0x3f).
Encoded hex consists of 4 bits of data placed in the low
order nibble + 0x30. For example, the one byte value
0x5F would be encoded as two characters with values of
0x35 (“5”) and 0x3f (“?”) respectively.
Carriage return character (0x0d) and line feed character
(0x0a).
Notes:
1. Encoded hex: each character consists of 4 bits of data placed in the low order nibble +30h. For
example, the 8-bit value 5Fh would be encoded as two characters with values of 35h and 3Fh, which
map to the ASCII characters “5” and “?”, respectively.
2. The TO and FROM flag can not both be 1, indicating that they are both valid. They can both be zero,
indicating that neither is valid. This situation will occur whenever the receiver determines that it is within
the “cone of confusion” directly over a VOR, or when no signal is being received.
01-000028-070F
Chelton Flight Systems – Confidential
Page 56 of 104
Byte #
0-5
Parameter
ID
Type
ASCII
Text
ASCII
Text
ASCII
Text
ASCII
Hex
Units
N/A
6–7
8
Message
Identifier
Valid Flag
9 – 12
Bearing
13 – 14
Checksum
ASCII
Hex
N/A
15 – 16
End
ASCII
<CR><LF>
Byte #
0-5
Parameter
ID
Units
N/A
6–7
8
Message
Identifier
Valid Flag
9 – 12
Bearing
Type
ASCII
Text
ASCII
Text
ASCII
Text
ASCII
Hex
13 – 14
Checksum
ASCII
Hex
N/A
15 – 16
End
ASCII
<CR><LF>
N/A
N/A
degrees
N/A
N/A
degrees
Description
Packet Identification for Garmin VHF NAV message:
“$PMRRV”
“23” = Radial From Active VOR
“0” = bearing not valid
“V” = bearing is valid
Bearing to a resolution of 1/10th of a degree.
ddd = three digit bearing in degrees ranging from “000” to
“359”. f = 1/10/th of a degree.
One byte message checksum generated by adding
characters 6 through 10, ignoring carry. This value is
converted into two encoded hex characters (0x30 - 0x3f).
Encoded hex consists of 4 bits of data placed in the low
order nibble + 0x30. For example, the one byte value
0x5F would be encoded as two characters with values of
0x35 (“5”) and 0x3f (“?”) respectively.
Carriage return character (0x0d) and line feed character
(0x0a).
Description
Packet Identification for Garmin VHF NAV message:
“$PMRRV”
“24” = Radial From Standby VOR
“0” = bearing not valid
“V” = bearing is valid
Bearing to a resolution of 1/10th of a degree.
ddd = three digit bearing in degrees ranging from “000” to
“359”. f = 1/10/th of a degree.
One byte message checksum generated by adding
characters 6 through 10, ignoring carry. This value is
converted into two encoded hex characters (0x30 - 0x3f).
Encoded hex consists of 4 bits of data placed in the low
order nibble + 0x30. For example, the one byte value
0x5F would be encoded as two characters with values of
0x35 (“5”) and 0x3f (“?”) respectively.
Carriage return character (0x0d) and line feed character
(0x0a).
5.2.11 ARINC 429
5.2.11.1 Transmitted Labels
The ARINC 429 transmit ports shall [SYS_COM_294] adjust to high speed or low speed
based upon the “ARINC 429 Transmit Speed” setting of the Aircraft Limits. The following
labels shall [SYS_COM_103] be transmitted on one of the COM ports as configured.
The ARINC 429 labels shall [SYS_COM_154] be grouped by source LRU such that only
labels associated with a specified group are transmitted. Groupings shall
01-000028-070F
Chelton Flight Systems – Confidential
Page 57 of 104
[SYS_COM_179] be based upon the “ARINC 429 TX Groupings” setting of the Aircraft
Limits, and multiple groups may be selected at once. The groupings shall
[SYS_COM_271] be as follows:
ADC Labels
162
Density Altitude
Feet
131072
Sig.
bits
16
203
Pressure
Altitude
204
Barometric
Corrected
Altitude
205
Mach Number
BNR
Feet
131072
17
16Hz
BNR
Feet
131072
17
16Hz
BNR
4.096
16
8Hz
206
Computed
Airspeed
BNR
Knots
1024
14
8Hz
210
True
Airspeed
BNR
Knots
2048
15
8Hz
211
Total Air
Temperature
BNR
Deg. C
512
11
2Hz
212
Altitude Rate
BNR
Feet/Min
.
BNR
Deg. C
32768
11
16Hz
512
11
2Hz
BCD
mBar
745-1050
5
8Hz
Set SSM to “No Computed Data” if value out
of range. Set SSM to “No Computed Data” if
pitot pressure in noise range. Set SSM to “No
Computed Data” if outside air temperature
invalid. Set SSM to “Failure Warning” if ADC
is inoperative.
Set SSM to “No Computed Data” if value out
of range. Set SSM to “No Computed Data” if
pitot pressure in noise range. Set SSM to
“Failure Warning” if ADC is inoperative.
Set SSM to “No Computed Data” if value out
of range. Set SSM to “No Computed Data” if
pitot pressure in noise range. Set SSM to “No
Computed Data” if outside air temperature
invalid. Set SSM to “Failure Warning” if ADC
is inoperative.
Set SSM to “No Computed Data” if value out
of range. Set SSM to “No Computed Data” if
outside air temperature invalid. Set SSM to
“Failure Warning” if ADC is inoperative.
Set SSM to “No Computed Data” if value out
of range. Set SSM to “Failure Warning” if ADC
is inoperative.
Set SSM to “No Computed Data” if value out
of range. Set SSM to “No Computed Data” if
outside air temperature invalid. Set SSM to
“Failure Warning” if ADC is inoperative.
No SSM for BCD value.
BCD
In. Hg.
22-31
5
8Hz
No SSM for BCD value.
BCD
mBar
745-1050
5
8Hz
No SSM for BCD value.
BCD
In. Hg.
22-31
5
8Hz
No SSM for BCD value.
213
Static Air
Temperature
234
Barometric
Correction #1
235
Barometric
Correction #1
236
Barometric
Correction #2
237
Barometric
Correction #2
01-000028-070F
Units
Range
Freq.
4Hz
Notes
Set SSM to “No Computed Data” if value out
of range. Set SSM to “Failure Warning” if ADC
is inoperative.
Set SSM to “No Computed Data” if value out
of range. Set SSM to “Failure Warning” if ADC
is inoperative.
Set SSM to “No Computed Data” if value out
of range. Set SSM to “Failure Warning” if ADC
is inoperative.
Chelton Flight Systems – Confidential
Page 58 of 104
AHRS Labels
±180°
320
Magnetic
Heading
324
Pitch Angle
BNR
Degrees
True
BNR
Degrees
Magnetic
BNR
Degrees
Sig.
bits
15
±180°
15
20Hz
Set SSM to “Failure Warning” if there is a
heading failure.
±180°
14
50Hz
325
Roll Angle
BNR
Degrees
±180°
14
50Hz
326
Body Pitch
Rate
327
Body Roll Rate
BNR
°/sec
±128°/se
c
13
50Hz
BNR
°/sec
±128°/se
c
13
50Hz
330
Body Yaw Rate
BNR
°/sec
±128°/se
c
13
50Hz
331
Body X-Axis
Acceleration
332
Body Y-Axis
Acceleration
333
Body Z-Axis
Acceleration
BNR G
±4G
12
50Hz
BNR G
±4G
12
50Hz
BNR G
±4G
12
50Hz
Set SSM to “No Computed Data” if value >
90°. Set SSM to “Failure Warning” if Age of
data is older than 1 second.
Set SSM to “No Computed Data” if value out
of range. Set SSM to “Failure Warning” if Age
of data is older than 1 second.
Set SSM to “No Computed Data” if value out
of range. Set SSM to “Failure Warning” if Age
of data is older than 1 second.
Set SSM to “No Computed Data” if value out
of range. Set SSM to “Failure Warning” if Age
of data is older than 1 second.
Set SSM to “No Computed Data” if value out
of range. Set SSM to “Failure Warning” if Age
of data is older than 1 second.
Set SSM to “No Computed Data” if value out
of range. Set SSM to “Failure Warning” if Age
of data is older than 1 second.
Set SSM to “No Computed Data” if value out
of range. Set SSM to “Failure Warning” if Age
of data is older than 1 second.
Set SSM to “No Computed Data” if value out
of range. Set SSM to “Failure Warning” if Age
of data is older than 1 second.
314
True Heading
AP Labels
Units
Range
Freq.
Notes
4Hz
Set SSM to “Failure Warning” if there is a
heading failure.
100
Selected
Course
BNR
Degrees
Magnetic
±180°
Sig.
bits
12
101
Selected
Heading
BNR
Degrees
Magnetic
±180°
12
4Hz
102
Selected
Altitude
BNR
Feet
65536
16
5Hz
103
Selected
Airspeed
BNR
Knots
512
11
5Hz
104
Selected VSI
BNR
Ft/Min
16384
18 or
16
5Hz
01-000028-070F
Units
Range
Freq.
4Hz
Notes
Internal EFIS parameter, always sent. Set
SSM to “No Computed Data” if value out of
range. Ref: 7.0F IDU Autopilot Interface
Requirements 01-000051-070F.
Internal EFIS parameter, always sent. Set
SSM to “No Computed Data” if value out of
range. Ref: 7.0F IDU Autopilot Interface
Requirements 01-000051-070F.
Internal EFIS parameter, always sent. Set
SSM to “No Computed Data” if value out of
range. Ref: 7.0F IDU Autopilot Interface
Requirements 01-000051-070F.
Internal EFIS parameter, always sent. Set
SSM to “No Computed Data” if value out of
range. Ref: 7.0F IDU Autopilot Interface
Requirements 01-000051-070F.
Set SSM to “No Computed Data” if value out
of range. Set SSM to “Failure Warning” if
GPS or AHRS is inoperative. 18-bit resolution
used if pitch steering output is enabled in
aircraft limits. Otherwise, 16-bit resolution
used. Ref: 7.0F IDU Autopilot Interface
Requirements 01-000051-070F.
Chelton Flight Systems – Confidential
Page 59 of 104
AP Labels
121
Horizontal
Command
Signal
BNR
Degrees
±180°
Sig.
bits
14
122
Vertical
Command
Signal
270
HeliSAS
Discretes
320
Magnetic
Heading
324
Pitch Angle
BNR
Degrees
±180°
12
10Hz
N/A
N/A
N/A
4Hz
BNR
Degrees
Magnetic
BNR
Degrees
±180°
15
20Hz
±180°
14
50Hz
325
Roll Angle
BNR
Degrees
±180°
14
50Hz
EFIS Labels
300
EFIS Mode
Status #1
301
EFIS Mode
Status #2
377
Equipment ID
FPL Labels
074
Flight Plan
Header
075
Active
Waypoint
113
Message
Checksum
125
Greenwich
Mean Time
164
Radio Altitude
01-000028-070F
Units
Units
Range
10Hz
N/A
N/A
Sig.
bits
N/A
N/A
N/A
N/A
5Hz
N/A
N/A
N/A
5Hz
Units
Range
Freq.
Range
BNR
N/A
Sig.
bits
N/A
DSC
N/A
BNR
Notes
Set SSM to “No Computed Data” if value out
of range. Set SSM to “No Computed Data” if
roll steering NCD settings (ref 01-000029070F.doc) is enabled and NAV Source is
VLOC1 or VLOC2 Set SSM to “Failure
Warning” if unable to dead reckon. Ref: 7.0F
IDU Autopilot Interface Requirements 01000051-070F.
Set SSM to “No Computed Data” if target pitch
> 90°. Set SSM to “Failure Warning” if GPS or
AHRS inoperative. Ref: 7.0F IDU Autopilot
Interface Requirements 01-000051-070F.
Always set SSM to “Normal Operation.” See
APPENDIX G: ARINC Label Detailed
Definitions.
Set SSM to “Failure Warning” if there is a
heading failure.
Set SSM to “No Computed Data” if value >
90°. Set SSM to “Failure Warning” if Age of
data is older than 1 second.
Set SSM to “No Computed Data” if value out
of range. Set SSM to “Failure Warning” if Age
of data is older than 1 second.
Freq.
5Hz
Notes
Always set SSM to “Normal Operation”. See
APPENDIX G: ARINC Label Detailed
Definitions.
Always set SSM to “Normal Operation”. See
APPENDIX G: ARINC Label Detailed
Definitions.
Set value to 0x94 (Equipment ID 025 – EFIS)
and SSM to “Normal Operation.”
Freq.
Notes
See
Ref.
Ref: ARINC 429 General Aviation Subset
Gama Publication No. 11, 4th Edition.
N/A
See
Ref.
Ref: ARINC 429 General Aviation Subset
Gama Publication No. 11, 4th Edition.
N/A
21
See
Ref.
Ref: ARINC 429 General Aviation Subset
Gama Publication No. 11, 4th Edition.
BCD
00.00.0 to
23.59.9
5
5Hz
Internal EFIS parameter, always sent.
BNR
Feet
8192
12
4Hz
Set SSM to “No Computed Data” if AGL
altitude is invalid. Set SSM to “No Computed
Data” if value out of range.
Chelton Flight Systems – Confidential
Page 60 of 104
FPL Labels
204
Baro Corrected
Altitude
210
True
Airspeed
BNR
Feet
131072
Sig.
bits
17
BNR
Knots
2048
15
8Hz
260
UTC Date
303
Message
Length/Type/
Number
304
Message
Characters 1-3
305
Message
Characters 4-6
306
Waypoint
Latitude
307
Waypoint
Longitude
310
Present
Position –
Latitude
311
Present
Position –
Longitude
312
Ground Speed
BCD
dd:mm:yy
15
5Hz
BNR
N/A
N/A
See
Ref.
Ref: ARINC 429 General Aviation Subset
Gama Publication No. 11, 4th Edition. Internal
EFIS parameter, always sent.
BNR
N/A
21
See
Ref.
BNR
N/A
21
See
Ref.
BNR
Degrees
±180°
20
See
Ref.
BNR
Degrees
±180°
20
See
Ref.
BNR
Degrees
±180°
20
5Hz
Ref: ARINC 429 General Aviation Subset
Gama Publication No. 11, 4th Edition. Internal
EFIS parameter, always sent.
Ref: ARINC 429 General Aviation Subset
Gama Publication No. 11, 4th Edition. Internal
EFIS parameter, always sent.
Ref: ARINC 429 General Aviation Subset
Gama Publication No. 11, 4th Edition. Internal
EFIS parameter, always sent.
Ref: ARINC 429 General Aviation Subset
Gama Publication No. 11, 4th Edition. Internal
EFIS parameter, always sent.
Set SSM to "No Computed Data" if value out
of range or if HFOM > 16. Set SSM to "Failure
Warning" if GPS is inoperative.
BNR
Degrees
±180°
20
5Hz
Set SSM to "No Computed Data" if value out
of range or if HFOM > 16. Set SSM to "Failure
Warning" if GPS is inoperative.
BNR
Knots
4096
15
20Hz
313
Track Angle
±180°
15
20Hz
±180°
15
4Hz
315
Wind Speed
BNR
Degrees
True
BNR
Degrees
True
BNR
Knots
Set SSM to "No Computed Data" if value out
of range or if HFOM > 16. Set SSM to "Failure
Warning" if GPS is inoperative.
Set SSM to "No Computed Data" if HFOM >
16. Set SSM to "Failure Warning" if GPS is
inoperative.
Set SSM to “Failure Warning” if there is a
heading failure.
256
8
20Hz
316
Wind Direction
BNR
Degrees
±180°
12
20Hz
320
Magnetic
Heading
BNR
Degrees
Magnetic
±180°
15
20Hz
314
True Heading
01-000028-070F
Units
Range
Freq.
16Hz
Notes
Set SSM to “No Computed Data” if value out
of range. Set SSM to “Failure Warning” if ADC
is inoperative.
Set SSM to “No Computed Data” if value out
of range. Set SSM to “No Computed Data” if
pitot pressure in noise range. Set SSM to “No
Computed Data” if outside air temperature
invalid. Set SSM to “Failure Warning” if ADC
is inoperative.
Internal EFIS parameter, always sent.
Set SSM to “No Computed Data” if value out
of range, if pitot pressure in noise range, if
aircraft on ground, or if outside air temperature
invalid. Set SSM to “Failure Warning” if GPS
or AHRS is inoperative.
Set SSM to “No Computed Data” if value out
of range, if pitot pressure in noise range, if
aircraft on ground, or if outside air temperature
invalid. Set SSM to “Failure Warning” if GPS
or AHRS is inoperative.
Set SSM to “Failure Warning” if there is a
heading failure.
Chelton Flight Systems – Confidential
Page 61 of 104
FPL Labels
Units
Range
324
Pitch Angle
BNR
Degrees
±180°
Sig.
bits
14
325
Roll Angle
BNR
Degrees
±180°
14
Freq.
50Hz
50Hz
Notes
Set SSM to “No Computed Data” if value >
90°. Set SSM to “Failure Warning” if Age of
data is older than 1 second.
Set SSM to “No Computed Data” if value out
of range. Set SSM to “Failure Warning” if Age
of data is older than 1 second.
Labels 074, 075, 113, 303, 304, 305, 306, and 307 of the FPL Tx Group shall
[SYS_COM_280] be used to continuously transmit the active flight plan. At the beginning
of each flight plan, the EFIS shall [SYS_COM_281] transmit the Flight Plan Header (label
074) and Active Waypoint (label 075). Following these two introductory labels, each
waypoint in the flight plan shall [SYS_COM_282] be communicated via a group of labels
consisting of labels 113, 303, 304, 305, 306, and 307. There shall [SYS_COM_283] be a
100 msec transmit interval between groups. For label and protocol details see the ARINC
429 General Aviation Subset – GAMA Publication No. 11, 4th Edition.
GPS Labels
Units
114
Desired Track
BNR
Degrees
True
115
Waypoint
Bearing
±180°
Sig.
bits
12
5Hz
BNR
Degrees
True
±180°
12
16Hz
116G
Cross Track
Distance
BNR NM
128
18
16Hz
117G
Vertical
Deviation
BNR
Feet
16384
14
16Hz
125
Greenwich
Mean Time
147
Magnetic
Variation
155
HeliSAS VNAV
Descent Angle
BCD
00.00.0
to
23.59.9
±180°
5
5Hz
12
5Hz
±51.1°
9
5Hz
01-000028-070F
BNR
BNR
Degrees
Range
Freq.
Notes
Internal EFIS parameter, always sent. Set
SSM to “No Computed Data” if value out of
range. Ref: 7.0F IDU Autopilot Interface
Requirements 01-000051-070F.
Set SSM to “No Computed Data” if no
waypoint. Set SSM to “No Computed Data” if
value out of range. Set SSM to “Failure
Warning” if GPS is inoperative.
Set SSM to “No Computed Data” if no
waypoint. Set SSM to “No Computed Data” if
value out of range. Set SSM to “Failure
Warning” if GPS is inoperative. Ref: 7.0F IDU
Autopilot Interface Requirements 01-000051070F.
Set SSM to “No Computed Data” if value out
of range or if VNAV mode is Climb or invalid.
Set SSM to “Failure Warning” if GPS or ADC
are inoperative. Ref: 7.0F IDU Autopilot
Interface Requirements 01-000051-070F.
Internal EFIS parameter, always sent.
Set SSM to “No Computed Data” if value out
of range. Set SSM to “Failure Warning” if
GPS is failed.
Set SSM to “No Computed Data” if value out
of range, VNAV not valid or selected altitude
sub-mode. Set SSM to “Failure Warning” if
GPS or ADC is inoperative. See APPENDIX
G: ARINC Label Detailed Definitions.
Chelton Flight Systems – Confidential
Page 62 of 104
GPS Labels
251
Distance to Go
BNR
NM
4096
Sig.
bits
15
260
UTC Date
310
Present
Position –
Latitude
311
Present
Position –
Longitude
312
Ground Speed
BCD
dd:mm:yy
15
5Hz
BNR
Degrees
±180°
20
5Hz
Set SSM to “No Computed Data” if value > 90°
or if HFOM > 16. Set SSM to “Failure
Warning” if GPS is inoperative.
BNR
Degrees
±180°
20
5Hz
Set SSM to “No Computed Data” if value out
of range or if HFOM > 16. Set SSM to “Failure
Warning” if GPS is inoperative.
BNR
Knots
4096
15
20Hz
313
Track Angle
±180°
15
20Hz
315
Wind Speed
BNR
Degrees
True
BNR
Knots
256
8
20Hz
316
Wind Direction
BNR
Degrees
±180°
12
20Hz
326G
Lateral Scale
Factor
BNR NM
128
15
1Hz
351G
Distance To
Destination
352G
Estimated
Time to
Destination
BNR
NM
32,768
18
2Hz
BNR
Minutes
4096
12
2Hz
Set SSM to “No Computed Data” if value out
of range or if HFOM > 16. Set SSM to “Failure
Warning” if GPS is inoperative.
Set SSM to “No Computed Data” if value out
of range or if HFOM > 16. Set SSM to “Failure
Warning” if GPS is inoperative.
Set SSM to “No Computed Data” if value out
of range, if pitot pressure in noise range, if
aircraft on ground, or if outside air temperature
invalid. Set SSM to “Failure Warning” if GPS
or AHRS is inoperative.
Set SSM to “No Computed Data” if value out
of range, if pitot pressure in noise range, if
aircraft on ground, or if outside air temperature
invalid. Set SSM to “Failure Warning” if GPS
or AHRS is inoperative.
Internal EFIS parameter, always sent. Set
SSM to “No Computed Data” if value out of
range. Ref: 7.0F IDU Autopilot Interface
Requirements 01-000051-070F.
Set SSM to “No Computed Data” if value out
of range. Set SSM to “Failure Warning” if
GPS is inoperative.
Set SSM to “No Computed Data” if value out
of range. Set SSM to “Failure Warning” if
GPS is inoperative.
GPS 743A
Labels
076
Altitude (MSL)
101
Horizontal
Dilution of
Precision
102
Vertical
Dilution of
Precision
01-000028-070F
Units
Units
Range
Range
Freq.
5Hz
BNR
Feet
±131,072
Sig.
bits
20
BNR
N/A
1024
15
5Hz
BNR
N/A
1024
15
5Hz
Notes
Set SSM to “No Computed Data” if no
waypoint. Set SSM to “No Computed Data” if
value out of range. Set SSM to “Failure
Warning” if GPS is inoperative.
Internal EFIS parameter, always sent.
Freq.
5Hz
Notes
Ref: ARINC 743A-4. Set SSM to “No
Computed Data” if value out of range or if
HFOM > 16. Set SSM to “Failure Warning” if
GPS is failed.
Ref: ARINC 743A-4. Set SSM to “No
Computed Data” if value out of range. Set
SSM to “Failure Warning” if GPS is failed.
Ref: ARINC 743A-4. Set SSM to “No
Computed Data” if value out of range. Set
SSM to “Failure Warning” if GPS is failed.
Chelton Flight Systems – Confidential
Page 63 of 104
GPS 743A
Labels
103
Track Angle
±180°
Sig.
bits
15
BNR
Degrees
5Hz
110
Latitude
BNR
Degrees
±180°
20
5Hz
111 Longitude
BNR
Degrees
±180°
20
5Hz
112
Ground Speed
BNR
Knots
4096
15
5Hz
120
Fine Latitude
BNR
Degrees
±0.00017
2°
11
5Hz
121
Fine Longitude
BNR
Degrees
±0.00017
2°
11
5Hz
130
Horizontal
Protection
Level
133
Vertical
Protection
Level
136
Vertical Figure
of Merit
BNR
NM
16
17
5Hz
BNR
Feet
32,768
18
5Hz
BNR
Feet
32,768
18
5Hz
140
UTC Fine
BNR
Seconds
1.0
20
5Hz
147
Magnetic
Variation
150
UTC
BNR
±180°
12
5Hz
BNR
Hr:Min:S
23:59:59
17
1Hz
165
Vertical
Velocity
BNR
Feet/Min
±32,768
15
5Hz
166
N/S Velocity
BNR
Knots
±4096
15
5Hz
174
E/W Velocity
BNR
Knots
±4096
15
5Hz
01-000028-070F
Units
Range
Freq.
Notes
Ref: ARINC 743A-4. Set SSM to "No
Computed Data" if HFOM > 16. Set SSM to
"Failure Warning" if GPS is inoperative.
Ref: ARINC 743A-4. Set SSM to "No
Computed Data" if value out of range or if
HFOM > 16. Set SSM to "Failure Warning" if
GPS is inoperative.
Ref: ARINC 743A-4. Set SSM to "No
Computed Data" if value out of range or if
HFOM > 16. Set SSM to "Failure Warning" if
GPS is inoperative.
Ref: ARINC 743A-4. Set SSM to "No
Computed Data" if value out of range or if
HFOM > 16. Set SSM to "Failure Warning" if
GPS is inoperative.
Ref: ARINC 743A-4. Set SSM to “No
Computed Data” if value out of range or if
HFOM > 16. Set SSM to “Failure Warning” if
GPS is failed.
Ref: ARINC 743A-4. Set SSM to “No
Computed Data” if value out of range or if
HFOM > 16. Set SSM to “Failure Warning” if
GPS is failed.
Ref: ARINC 743A-4. Set SSM to “No
Computed Data” if value out of range or if
HFOM > 16. Set SSM to “Failure Warning” if
GPS is failed.
Ref: ARINC 743A-4. Set SSM to “No
Computed Data” if value out of range or if
HFOM > 16. Set SSM to “Failure Warning” if
GPS is failed.
Ref: ARINC 743A-4. Set SSM to “No
Computed Data” if value out of range or if
HFOM > 16. Set SSM to “Failure Warning” if
GPS is failed.
Ref: ARINC 743A-4. Set SSM to “No
Computed Data” if value out of range. Set
SSM to “Failure Warning” if GPS is failed.
Ref: ARINC 743A-4. Set SSM to “No
Computed Data” if value out of range. Set
SSM to “Failure Warning” if GPS is failed.
Ref: ARINC 743A-4. Set SSM to “No
Computed Data” if internal date is invalid. Set
SSM to “Failure Warning” if GPS is failed.
Ref: ARINC 743A-4. Set SSM to “No
Computed Data” if value out of range or if
HFOM > 16. Set SSM to “Failure Warning” if
GPS is failed.
Ref: ARINC 743A-4. Set SSM to “No
Computed Data” if value out of range or if
HFOM > 16. Set SSM to “Failure Warning” if
GPS is failed.
Ref: ARINC 743A-4. Set SSM to “No
Computed Data” if value out of range or if
HFOM > 16. Set SSM to “Failure Warning” if
GPS is failed.
Chelton Flight Systems – Confidential
Page 64 of 104
GPS 743A
Labels
247 Horizontal
Figure of Merit
Units
260
UTC Date
273
GNSS Sensor
Status
370
GNSS Height
(WGS-84)
NAV Labels
BNR
NM
16
Sig.
bits
18
BCD
dd:mm:yy
15
5Hz
Ref: ARINC 743A-4. Set SSM to “No
Computed Data” if value out of range. Set
SSM to “Failure Warning” if GPS is failed.
Internal EFIS parameter, always sent.
DISC
N/A
N/A
5Hz
SSM always “Normal Operation”.
BNR
Feet
±131,072
20
5Hz
Ref: ARINC 743A-4. Set SSM to “No
Computed Data” if value out of range or if
HFOM > 16. Set SSM to “Failure Warning” if
GPS is failed.
Range
Freq.
5Hz
173
Lateral
Deviation
DDM
±0.4
Sig.
bits
12
174
Glideslope
Deviation
DDM
±0.8
12
20Hz
202G
DME Distance
BNR NM
512
16
8Hz
RADALT
Labels
164
AGL Altitude
Units
Range
Units
Range
BNR
Feet
8192
01-000028-070F
Sig.
bits
12
Notes
Freq.
20Hz
Notes
Set SSM to “Normal Operation” under
following circumstances:
HSI Source = GPS, active waypoint exists and
GPS operative or dead reckoning;
HSI Source = VOR1 and either localizer signal
A or VOR signal A is valid; or
HSI Source = VOR2 and either localizer signal
B or VOR signal B is valid.
Otherwise, set SSM to “No Computed Data.”
Ref: 7.0F IDU Autopilot Interface
Requirements document number 01-000051070F.
Set SSM to “Normal Operation” under
following circumstances:
HSI Source = VOR1 and glideslope signal A is
valid; or
HSI Source = VOR2 and glideslope signal B is
valid.
Otherwise, set SSM to “No Computed Data.”
Ref: 7.0F IDU Autopilot Interface
Requirements document number 01-000051070F.
Set SSM to “Normal Operation” under
following circumstances:
HSI Source = GPS, active waypoint exists and
GPS operative or dead reckoning, DME
distance value is distance to active waypoint;
HSI Source = VOR1 and DME1 value is valid,
DME distance value is DME1; or
HSI Source = VOR2 and DME2 value is valid,
DME distance value is DME2.
Otherwise, set SSM to “No Computed Data” or
“Failure Warning” as appropriate.
Frequency
4Hz
Notes
Set SSM to “No Computed Data” if AGL altitude is
invalid. Set SSM to “No Computed Data” if value out
of range.
Chelton Flight Systems – Confidential
Page 65 of 104
Other ARINC 429 transmit options may be defined in the future. See the Weather Radar
Module section (§ 5.2.18 below) for details on ARINC 429 control messages sent to the
Honeywell RDR-2XXX series weather radar receiver/transmitters.
5.2.11.2 Received Labels
The ARINC 429 receive ports shall [SYS_COM_104] adjust to high speed or low speed
based upon the “ARINC 429 Receive Speed” setting of the Aircraft Limits. Data received
from ARINC 429 shall [SYS_COM_119] supersede data acquired from RS-232 or RS422 sources. Likewise, if an ARINC 429 source becomes invalid, valid data from RS-232
or RS-422 sources shall [SYS_COM_273] be acquired as a backup source with the
exception of the following labels (i.e., fail-over not allowed for the following labels):
1. All labels in the ADC group;
2. Magnetic Heading, Pitch Angle and Roll Angle labels in the AHRS group;
3. All labels in the TCAS group;
4. All labels in the fuel flow group; and
5. All labels in the radar altitude group.
The following labels shall [SYS_COM_105] be received and processed on any ARINC
429 receive port as configured. The ARINC 429 labels shall [SYS_COM_155] be
grouped by source LRU such that only labels associated with a specified group are
received. Groupings shall [SYS_COM_180] be based upon the “ARINC 429 RX
Groupings” setting of the Aircraft Limits, and multiple groups may be specified. The
groupings shall [SYS_COM_272] be as follows:
ADC Labels
203
Pressure
Altitude
206
Computed
Airspeed
BNR
Feet
131072
17
Conversion and
Boundary
Conditions
1, -2000 to 80000
BNR
knots
1024
14
1, 0 to 1024
211
Total Air
Temperature
212
Altitude Rate
BNR
Deg. C
512
11
1, -512 to 512
BNR
ft./min.
32768
11
1, -32768 to
32768
01-000028-070F
Units
Range
Sig.
bits
Notes
On error set to -9999.
A SSM of “No Computed Value”
means that parameter is valid but
below range of sensor. On error set
to previous value.
Convert to °F for EFIS storage. On
error set to -999.
On error set to previous value.
Chelton Flight Systems – Confidential
Page 66 of 104
AHRS Labels
270
AHRS Discrete
320
Magnetic
Heading
324
Pitch Angle
325
Roll Angle
326
Body Pitch
Rate
327
Body Roll Rate
330
Body Yaw Rate
331
X-axis
Acceleration
332
Y-axis
Acceleration
333
Z-axis
Acceleration
TCAS Labels
130
Intruder Range
131
Intruder
Altitude
132
Intruder
Bearing
270
Vertical
Resolution
Advisory
274
Selected
Sensitivity
Level
350
Maintenance
Data
357
RTS/ETX
01-000028-070F
Units
DIS
N/A
19
Conversion and
Boundary
Conditions
N/A
BNR
Degrees
±180°
15
1, -180 to 180
BNR
Degrees
BNR
Degrees
BNR
°/sec
±180°
14
1, -180 to 180
Convert to radians True for EFIS
storage. On error set to previous
value.
On error set to previous value.
±180°
14
PI / 180, -PI to PI
On error set to previous value.
±128°/se
c
13
Nose up rotation is positive.
BNR
°/sec
BNR
°/sec
BNR G
±128°/se
c
±128°/se
c
±4
13
Clockwise rotation is positive.
13
Increasing heading is positive.
12
1, -4 to 4
On error set to previous value.
BNR G
±4
12
1, -4 to 4
On error set to previous value.
BNR G
±4
12
1, -4 to 4
On error set to previous value.
Units
Range
Range
Sig.
bits
Sig.
bits
Notes
Ref: ARINC 705-5.
Conversion and
Boundary
Conditions
Notes
Ref: ARINC 735A-1
Equip. Code 035
Ref: ARINC 735A-1
Equip. Code 035
Ref: ARINC 735A-1
Equip. Code 035
Ref: ARINC 735A-1
Equip. Code 035
Ref: ARINC 735A-1
Equip. Code 035
Ref: ARINC 735A-1
Equip. Code 035
Ref: ARINC 735A-1
Equip. Code 035
Chelton Flight Systems – Confidential
Page 67 of 104
FD Labels
140
Flt. Dir. Roll
141
Flt. Dir. Pitch
142
Flt. Dir.
Fast/Slow
NAV Labels
Units
BNR
Degrees
BNR
Degrees
BNR
Knots
±180°
12
Conversion and
Boundary
Conditions
2, -60.0 to 60.0
±180°
12
2, -30.0 to 30.0
On error set to -99.9
32
12
1, -32.0 to 32.0
On error set to -999. Smoothed
over 5 readings
034
VOR/ILS
Frequency
Discretes
NA
NA
035
DME
Frequency
Discretes
NA
NA
NA
162
ADF Bearing
BNR
Degrees
Relative
BNR
DDM
±180°
12
1, -180 to 180
.4
12
2 / .155,
-5.2 to 5.2
BNR
DDM
.8
12
2 / .175,
-9.2 to 9.2
BNR
NM
512
15
0 to 512
BNR
Degrees
±180°
12
1, -180 to 180
222
VOR Bearing
RADALT
Labels
164
Radio Height
Units
BNR
Feet
DAU Labels
Units
102
Electrical Load
104
Bus Voltage
105
BNR
Amperes
BNR
Volts
BNR
01-000028-070F
Range
Sig.
bits
Conversion and
Boundary
Conditions
NA
173
Localizer
Deviation
174
Glideslope
Deviation
202
DME Distance
Units
Range
Range
8192
Sig.
bits
Sig.
bits
16
Range
Sig.
bits
Conversion and
Boundary
Conditions
1, 0 to 2500
Notes
On error set to -99.9
Notes
Process bit 14 to determine mode.
VOR = 0, LOC = 1. Monitor SDI to
determine whether VOR/LOC A or
B.
Only processed for DME Mode (bits
11, 12 and 13). This is used to
properly interpret data on label 202
(DME distance). SSM is ignored
(ref: ARINC429 § 3.1.3.
On error set to 0. Convert to
between 0 - 360° Magnetic.
On error set to -9.99. Monitor SDI
to determine whether value is
localizer A or B.
On error set to -9.99. Monitor SDI
to determine whether value is
glideslope A or B.
On error set to -9999. Look at label
035 for channel and hold data. Ref:
ARINC709.
On error set to 0. Convert to
between 0 - 360°. Monitor SDI to
determine whether value is VOR A
or B. Marker Beacons also
encoded in label, which are
acquired when SSM is NO or NCD.
Notes
On error set to -9999
256
8
Conversion and
Boundary
Conditions
1, 0 to 256
Notes
128
9
1, 0 to 128
On error set to -9999.
2048
12
1, 0 to 2048
On error set to -9999.
On error set to -9999.
Chelton Flight Systems – Confidential
Page 68 of 104
DAU Labels
Units
Transmission
Oil
Temperature
106
Transmission
Oil Pressure
245
Engine Free
Power Turbine
(NF)
246
Rotor RPM
(NR)
255
Fuel Quantity
316
Engine Oil
Temperature
317
Engine Oil
Pressure
320
Fuel Pressure
336
Engine Torque
344
Ng
345
Inter-Turbine
Temperature
Degrees
Celsius
Range
Sig.
bits
Conversion and
Boundary
Conditions
Notes
BNR
PSI
4096
12
1, 0 to 4096
On error set to -9999.
BNR
%RPM
256
14
1, 0 to 256
On error set to -9999.
BNR
%RPM
256
14
1, 0 to 256
On error set to -9999.
BNR
Gallons
BNR
Degrees
Celsius
BNR
PSI
32768
15
1, 0 to 32768
On error set to -9999.
2048
11
1, 0 to 2048
On error set to -9999.
4096
12
1, 0 to 4096
On error set to -9999.
BNR
PSI
BNR
%
BNR
%RPM
BNR
Degrees
Celsius
4096
12
1, 0 to 4096
On error set to -9999.
256
12
1, 0 to 256
On error set to -9999.
256
14
1, 0 to 256
On error set to -9999.
2048
12
1, 0 to 2048
On error set to -9999.
5.2.11.2.1 User Waypoint Rx Group
The following labels shall [SYS_COM_284] comprise the User Waypoint Rx Group:
User
Waypoint
Labels
074
Data Record
Header
113
Message
Checksum
303
Message
Length/Type/N
umber
304
Message
Characters 1-3
305
Message
Characters 4-6
306
01-000028-070F
Units
Range
Sig.
bits
BNR
N/A
N/A
N/A
Conversion and
Boundary
Conditions
N/A
Notes
BNR
N/A
N/A
N/A
N/A
Ref: ARINC429 General Aviation
Subset – GAMA Publication No. 11.
BNR
N/A
N/A
N/A
N/A
Ref: ARINC429 General Aviation
Subset – GAMA Publication No. 11.
BNR
N/A
N/A
N/A
N/A
Ref: ARINC429 General Aviation
Subset – GAMA Publication No. 11.
BNR
N/A
N/A
N/A
N/A
Ref: ARINC429 General Aviation
Subset – GAMA Publication No. 11.
BNR
±180°
20
1, -180 to 180
Ref: ARINC429 General Aviation
Ref: ARINC429 General Aviation
Subset – GAMA Publication No. 11.
Chelton Flight Systems – Confidential
Page 69 of 104
User
Waypoint
Labels
Waypoint
Latitude
307
Waypoint
Longitude
Units
Range
Sig.
bits
Conversion and
Boundary
Conditions
Subset – GAMA Publication No. 11.
Degrees
BNR
Degrees
Notes
±180°
20
1, -180 to 180
Ref: ARINC429 General Aviation
Subset – GAMA Publication No. 11.
The User Waypoint Rx Group defines a user waypoint, which shall [SYS_COM_285] be
saved in the user waypoint database if the message checksum passes. The message
checksum shall [SYS_COM_286] be checked against a two’s complement sum of the
data bits (11-29) of labels 303, 304, 305, 306, and 307. The data received on labels 303,
304, and 305 shall [SYS_COM_287] only be used for checksum purposes. The EFIS
shall [SYS_COM_288] assign a unique name to each user waypoint received. The prefix
to each user waypoint shall [SYS_COM_289] be “MAP” and the postfix shall
[SYS_COM_290] be a unique number.
5.2.11.2.2 RDR-2XXX Radar Control Panel Rx Group
The following labels shall [SYS_COM_327] comprise the RDR-2XXX Radar Control
Panel Rx Group (see § 5.2.18.3 for usage):
RDR-2XXX
RCP Labels
300
Selected
Switches #1
301
Selected
Switches #2
302
CPU Results
305
Roll Trim and
Tilt
306
Gain
307
Formatted
Switches
Units
Range
Sig.
bits
Conversion and
Boundary
Conditions
Notes
DISC
See APPENDIX G: ARINC Label
Detailed Definitions
DISC
See APPENDIX G: ARINC Label
Detailed Definitions
DISC
See APPENDIX G: ARINC Label
Detailed Definitions
See APPENDIX G: ARINC Label
Detailed Definitions
BNR +
DISC
BNR +
DISC
DISC
See APPENDIX G: ARINC Label
Detailed Definitions
See APPENDIX G: ARINC Label
Detailed Definitions
5.2.12 Goodrich WX-500
The optional Goodrich WX-500 is a certified TSO-C110a remote lightning sensor.
Duplex communications between the WX-500 and the IDUs shall [SYS_COM_085] use
01-000028-070F
Chelton Flight Systems – Confidential
Page 70 of 104
COM4. The IDU will perform the necessary display functions so that the combination of
the WX-500 and an IDU will meet the requirements for TSO-C110a.
5.2.12.1 Communication Parameters
The communication standard shall [SYS_COM_086] be RS-232. Data shall
[SYS_COM_087] be transmitted with 8 data bits, 1 stop bit, and no parity.
Transmission speed shall [SYS_COM_088] be 9,600 baud.
5.2.12.2 Packet General Description
Packets are described in the “Stormscope WX-500 Interface Developer’s Guide”
(Goodrich Document No. 010-11501-001 dated 10/24/1996) attached as Appendix A.
The “transmit enabled” IDU shall [SYS_COM_089] transmit the following packets to the
WX-500:
1. Pilot Initiated Self Test Request (Item Designator “W,” Item Format “T”) when
commanded by the user.
2. Data Clear (Item Designator “C”) when commanded by the user.
3. Heading Update (Item Designator “H”) at 1-second intervals.
IDUs shall [SYS_COM_090] receive and process the following packets from the WX500:
1. Status Message (Item Designator “%I,” System Status “P,” Display Mode “A” or
“E”).
2. Data Clear (Item Designator “%B”).
3. Heading Message (Item Designator “%H”).
4. Strike Message (Item Designator “%S”).
01-000028-070F
Chelton Flight Systems – Confidential
Page 71 of 104
5.2.13 Ryan TCAD
The optional Ryan TCAD will be a 9900 series certified TSO-C147 remote traffic
advisory sensor. Duplex communications between the TCAD and the IDUs shall
[SYS_COM_091] use COM5. The IDU will perform the necessary display functions so
that the combination of the TCAD and an IDU will meet the requirements for TSOC147.
5.2.13.1 Communication Parameters
The communication standard shall [SYS_COM_092] be RS-232. Data shall
[SYS_COM_093] be transmitted with 8 data bits, 1 stop bit, and no parity.
Transmission speed shall [SYS_COM_094] be 9,600 baud.
5.2.13.2 Packet General Description
Packets are described in the “Third Party Interface Protocol” (Ryan International
Corporation document dated 5/28/2002 or later as implemented in 9900B models with
software version 1.10 or greater and all 9900BX models) attached as Appendix B. The
“transmit enabled” IDU shall [SYS_COM_095] transmit the following packets to the
TCAD:
1. Altimeter Setting Message (Message Type “AS”) upon a system altimeter
change or when the TCAD responds with a Link Grant Message (Message Type
“LG”).
2. Link Request Message (Message Type “LR”) at one-second intervals until the
TCAD responds with a Link Grant Message (Message Type “LG”).
3. Heading Update Message (Message Type “HU”) at one-second intervals.
4. Diagnostic Request Message (Message Type “LD”) when commanded by the
user.
5. Ground Elevations Messages (Message Types “SSA” and “SSG”) every ten
seconds.
6. Traffic Request Message (Message Type “TR”) every ten seconds to set traffic
depth to seven targets including Other Traffic targets.
01-000028-070F
Chelton Flight Systems – Confidential
Page 72 of 104
IDUs shall [SYS_COM_096] receive and process the following packets from the TCAD:
1. Diagnostics Message (Message Type “LD”).
2. Link Grant Message (Message Type “LG”).
3. Traffic Data Message (Message Type “TD”).
01-000028-070F
Chelton Flight Systems – Confidential
Page 73 of 104
5.2.14 Datalink
The IDU shall [SYS_COM_156] receive Datalink information on COM3. The datalink
information shall [SYS_COM_181] be from either the WSI InFlight Weather System or
the Garmin GDL 90, depending on the “Datalink Option” setting of the Aircraft Limits.
5.2.14.1 WSI InFlight Weather System
The optional WSI InFlight Weather System will provide a continuous stream of aviation
weather information.
5.2.14.1.1 Communication Parameters
The communication standard shall [SYS_COM_157] be RS-232. Data shall
[SYS_COM_158] be transmitted with 1 start bit, 8 data bits, 1 stop bit, and no parity.
Transmission speed shall [SYS_COM_159] be 38,400 baud.
5.2.14.1.2 Products
The WSI InFlight Weather data signal encodes a package of products which are
updated and transmitted periodically. The IDU shall [SYS_COM_182] receive and
decode the following packets:
Product Code
0x03
0x04
0x05
0x07
0x08
0x0C
0x1F
0x20
0x70
0x92
0x93
Product Name
Textual METAR
Textual TAF
WSI InFlight NOWrad Winter Storm
Mosaic
Echo Tops
Warning Areas (SIGMETS/AIRMETS)
Temporary Flight Restrictions (TFRs)
Canada/Mexico/Caribbean Text METAR
Canada/Mexico/Caribbean Text TAF
Lightning
Upper Air Winds
Upper Air Temps
Update Frequency (minutes)
5
10
5
5
5
5
5
10
5
30
30
For details, refer to Appendix C “WSI InFlight Weather Interface Control Document
(Version 1.2 Revision 6)”.
5.2.14.1.3 Status Message
The IDU shall [SYS_COM_197] request a Receiver Status Message by sending the string
“@S\r\n” to the WSI InFlight Weather System. The WSI InFlight Weather System shall
[SYS_COM_198] respond by sending a status message with the message type of 0x07.
01-000028-070F
Chelton Flight Systems – Confidential
Page 74 of 104
For details, refer to Appendix C “WSI InFlight Weather Interface Control Document
(Version 1.2 Revision 6)”.
5.2.14.2 Garmin GDL 90
The Garmin GDL 90 is an ADS-B Universal Access Transceiver.
5.2.14.2.1 Communication Parameters
The communication standard shall [SYS_COM_161] be RS-422. Data shall
[SYS_COM_162] be transmitted with 1 start bit, 8 data bits, 1 stop bit, and no parity.
Transmission speed shall [SYS_COM_163] be 38,400 baud.
5.2.14.2.2 Packet General Description
The IDU shall [SYS_COM_183] receive and decode the following messages:
Message ID
010
710
2010
Message Name
Heartbeat
Uplink Data
Traffic Report
The IDU shall [SYS_COM_199] transmit the following initialization message:
Message ID
210
Message Name
Initialization
For details, refer to Appendix D “GDL 90 Data Interface Specification”.
01-000028-070F
Chelton Flight Systems – Confidential
Page 75 of 104
5.2.15 Chelton Remote Bug Panel
The Chelton Remote Bug Panel (RBP) provides dedicated controls for setting
frequently used EFIS parameters. Duplex communications between the RBP and the
IDUs shall [SYS_COM_164] use COM10.
5.2.15.1 Communication Parameters
Communications shall [SYS_COM_165] take place at 19,200 baud, 9 bits, no parity,
non return to zero serial protocol using a RS-422 physical interface. The serial protocol
shall [SYS_COM_167] use the 9th bit to identify packet framing. The 9th bit shall
[SYS_COM_200] be set only for the last character of a packet and shall
[SYS_COM_201] be cleared for all other characters. The set 9th bit will uniquely
identify the last character of the packet, regardless of the contents of the lower 8 bits.
5.2.15.2 Packet General Description
The RBP shall [SYS_COM_202] send a status packet to the IDU approximately every 20
milliseconds. This unsolicited RBP status packet is defined in the RBP System
Requirements Document (SYRD) (01-000025).
Key status bits shall [SYS_COM_274] have the following effect:
1. Heading Knob Press: Synchronize heading bug to current heading.
2. Altitude Knob Press: Synchronize target altitude bug to current altitude.
3. Set Knob Press:
a) Function == GPS Course: If a manual GPS Course exist (i.e., not in
automatic OBS), synchronize the GPS Course to current bearing to the
active waypoint.
b) Function == VOR1 Course: Synchronize the VOR1 Course to the current
bearing to the station.
c)
Function == VOR2 Course: Synchronize the VOR2 Course to the current
bearing to the station.
d) Function == Airspeed Bug: Synchronize the Airspeed Bug to current
airspeed.
01-000028-070F
Chelton Flight Systems – Confidential
Page 76 of 104
e) Function == Vertical Speed Bug: Synchronize the Vertical Speed Bug to
current VSI.
f)
Function == Climb Angle Setting: Set the Climb Angle Setting to 3°.
g) Function == Descent Angle Setting: Set the Descent Angle Setting to 3°.
h) Function == Decision Height Bug: Set the Decision Height Bug to 200’ AGL.
i)
Function == Minimum Altitude Bug: Set the Minimum Altitude Bug to current
altitude.
4. Heading LNAV Button Press: Turn OFF the heading bug so that the LNAV submodes is entered. The LNAV button will only be active when the “LNAV” soft tile
appears on the EFIS. Ref: 01-000037-070F.
5. Altitude VNAV Button Press: Turn OFF the target altitude bug so that the VNAV
sub-mode is entered. The VNAV Button will only be active when the “VNAV” soft
tile appears on the EFIS. Ref: 01-000037-070F.
6. Set <BAR> Button Press:
a) Function == GPS Course: Change OBS mode (Manual or Automatic)
b) Function == VOR1 Course: No function.
c)
Function == VOR2 Course: No function.
d) Function == Airspeed Bug: Toggle Airspeed Bug (ON or OFF).
e) Function == Vertical Speed Bug: Toggle Vertical Speed Bug (ON or OFF)
f)
Function == Climb Angle Setting: No function.
g) Function == Descent Angle Setting: No function.
h) Function == Decision Height Bug: Toggle Decision Height Bug (ON or OFF).
i)
Function == Minimum Altitude Bug: Toggle Minimum Altitude Bug (ON or
OFF).
Heading knob rotation shall [SYS_COM_275] increment or decrement the heading bug.
Altitude knob rotation shall [SYS_COM_276] increment or decrement the target altitude
bug. Set knob rotation shall [SYS_COM_277] have the following effect:
1. Function == GPS Course: If a manual GPS Course exist (i.e., not in automatic
OBS), increment or decrement the GPS Course setting.
2. Function == VOR1 Course: Increment or decrement the VOR1 Course setting.
3. Function == VOR2 Course: Increment or decrement the VOR2 Course setting.
4. Function == Airspeed Bug: Increment or decrement the Airspeed Bug setting.
01-000028-070F
Chelton Flight Systems – Confidential
Page 77 of 104
5. Function == Vertical Speed Bug: Increment or decrement the Vertical Speed
Bug setting.
6. Function == Climb Angle Setting: Increment or decrement the Climb Angle
setting.
7. Function == Descent Angle Setting: Increment or decrement the Descent Angle
setting.
8. Function == Decision Height Bug: Increment or decrement the Decision Height
Bug.
9. Function == Minimum Altitude Bug: Increment or decrement the Minimum
Altitude Bug.
Select virtual knob “rotation” shall [SYS_COM_278] scroll through the various possible
functions of the Set knob as follows:

GPS Course

VOR1 Course (only active if aircraft limits indicate VOR receiver is
connected, ref: 01-000029-070F).

VOR2 Course (only active if aircraft limits indicate dual VOR receivers are
connected, ref: 01-000029-070F).

Airspeed Bug

Vertical Speed Bug

Climb Angle Setting

Descent Angle Setting

Decision Height Bug

Minimum Altitude Bug
The IDU shall [SYS_COM_184] send a display packet, with ID 0x00, to the RBP on
each screen refresh. This unsolicited display packet is defined in the RBP System
Requirements Document (SYRD) (01-000025).
The Main Messages and Option Messages sent to the RBP shall [SYS_COM_279]
depend upon the current function of the “Set” knob as follows:
1. Function == GPS Course (EFIS in manual OBS mode):
Main Message = “CRS GPS”
01-000028-070F
Chelton Flight Systems – Confidential
Page 78 of 104
Option Message = “AUTO” if EFIS in manual OBS mode
Option Message = “MAN” if EFIS in automatic OBS mode
2. Function == VOR1 Course:
Main Message = “CRS VOR1”
Option Message = Current VOR1 Course Setting (degrees)
3. Function == VOR2 Course:
Main Message = “CRS VOR2”
Option Message = Current VOR2 Course Setting (degrees)
4. Function == Airspeed Bug:
Main Message = “SPD BUG”
Option Message = “ON” if Airspeed Bug is OFF
Option Message = “OFF” if Airspeed Bug is ON
5. Function == Vertical Speed Bug:
Main Message = “VSI BUG”
Option Message = “ON” if Vertical Speed Bug is OFF
Option Message = “OFF” if Vertical Speed Bug is ON
6. Function == Climb Angle Setting:
Main Message = “CLMB ANG”
Option Message = Current Climb Angle Setting (tenths of a degree)
7. Function == Descent Angle Setting:
Main Message = “DCND ANG”
Option Message = Current Descent Angle Setting (tenths of a degree)
8. Function == Decision Height Bug:
Main Message = “DEC HT”
Option Message = “ON” if Decision Height Bug is OFF
Option Message = “OFF” if Decision Height Bug is ON
9. Function == Minimum Altitude Bug:
Main Message = “MIN ALT”
Option Message = “ON” if Minimum Altitude Bug is OFF
Option Message = “OFF” if Minimum Altitude Bug is ON
01-000028-070F
Chelton Flight Systems – Confidential
Page 79 of 104
5.2.16 HeliSAS Control Panel (HCP)
If HeliSAS is enabled in the system limits (ref: 01-000029-070F), the EFIS shall
[SYS_COM_291] receive the HCP Command Packet from the Flight Control Computer
on COM 12 at 100 Hz. See HeliSAS Software Requirements Document for
communication parameters and general description. The EFIS shall [SYS_COM_353]
process the HCP Command Packet as follows:
Byte #
0
1
2
3
4
Parameter
DLE (0x10)
0x01
Data Length
Lateral Modes
Data Type
BYTE
BYTE
BYTE
BYTE
Longitudinal
Modes and Status
Bits
BYTE
Units
N/A
N/A
N/A
bit field
bit field
Description
Used for synchronization.
Packet identification byte.
For each 2-bit field:
00 = OFF
01 = ARMED
10 = ENGAGED
11 = Note Defined
Fields are as follows:
bits 0-1: SAS Mode
bits 2-3: HDG Mode
bits 4-5: NAV Mode
bits 6-7: BC Mode
For each 2-bit field:
00 = OFF
01 = ARMED
10 = ENGAGED
11 = Note Defined
Fields are as follows:
bits 0-1: ALT Mode
bits 2-3: VRT Mode
5
Status bits
BYTE
bit field
6-7
Checksum
USHORT
N/A
8
9
DLE (0x10)
ETX (0x03)
BYTE
BYTE
N/A
N/A
01-000028-070F
Status bits are as follows:
bit 4: Glideslope Arm Available
bit 5: VNAV Approach Arm Available
bits 6-7: Reserved
Status bits are as follows:
bit 0: NVG Switch Asserted
bit 1: Side in Command (0 = Pilot)
bit 2: HeliSAS Disengage
bit 3: HeliSAS Mode Disengage
bit 4: Glideslope Captured
bit 5: VNAV Approach Captured
bit 6: Track Angle Hold
bit 7: Trim Force Release Pressed
Two-byte sum of characters 0 through
5 (excluding extra <DLE> in
<DLE><DLE> pairs).
End of Transmission
End of Transmission
Chelton Flight Systems – Confidential
Page 80 of 104
5.2.17 Remote Keyboard Interface
A remote keyboard interface will be provided to support future development of a variety
of control panel types. Input-only communications between the remote keyboard and
the IDUs shall [SYS_COM_317] use COM16.
5.2.17.1 Communication Parameters
The communication standard shall [SYS_COM_318] be RS-232. Data shall
[SYS_COM_319] be transmitted with 1 start bit, 8 data bits, 1 stop bit, and no parity.
Transmission speed shall [SYS_COM_320] be 9,600 baud.
5.2.17.2 Packet General Description
The remote keyboard shall [SYS_COM_321] send a packet to the IDU for every key
actuation. Packets shall [SYS_COM_322] have the following five-byte format:
1. Byte 0: One byte formatted as specified in § 5.8.10.4.2 “Keyboard Controller
Outgoing Data Format” of the 01-000045 document (“IDU-450 System Requirements
Document”).
2. Bytes 1-4: Checksum bytes consisting of Byte 0 XOR’d with a target-screen specific
masks as follows:
Target CPU#
0 or 1
2
3
4
01-000028-070F
Byte 1 XOR Mask
0x55
0xAA
0x33
0xCC
Byte 2 XOR Mask
0xAA
0x33
0xCC
0x55
Byte 3 XOR Mask
0x33
0xCC
0x55
0xAA
Chelton Flight Systems – Confidential
Byte 4 XOR Mask
0xCC
0x55
0xAA
0x33
Page 81 of 104
5.2.18 Weather Radar (IDU-450/680 Only)
5.2.18.1 Supported Weather Radar Architectures
The IDU-450 and 680 support weather radar when interfaced with a Weather Radar
Module. The IDU-III does not support weather radar. Supported weather radars must
have an ARINC-453 display bus interface. In all cases, a separate control panel must
be installed. With the exception of the Honeywell RDR-2XXX weather radar series,
these separate control panels interface directly with the weather radar’s
receiver/transmitter unit. In a Honeywell RDR-2XXX installation, single or dual control
panels interface with the IDU and the IDU communicates control information to the
weather radar’s receiver/transmitter unit. This is because in a RDR-2XXX installation,
radar range is controlled by the IDU range knob rather than by a dedicated control on
the control panel. The supported weather radar architectures are depicted below:
Standard ARINC-708, Collins and most Honeywell Digital Radars:
Pilot
Weather Radar
Control Panel
ARINC 429
Control Bus
Pilot-Side MFD
Weather Radar
R/T Unit
CoPilot
Weather Radar
Control Panel
(Optional)
01-000028-070F
ARINC 453
Display Bus
ARINC 429
Control Bus
Chelton Flight Systems – Confidential
CoPilot-Side MFD
Page 82 of 104
Honeywell RDR-2XXX with Single Radar Control Panel:
ARINC 429
Control Bus
Weather Radar
R/T Unit
ARINC 453
Display Bus
ARINC 429
Control Bus
Pilot-Side MFD
ARINC 429
RCP Bus
Crosslink Bus
RCP Parameter
Synch
CoPilot-Side MFD
Weather Radar
Control Panel
ARINC 429
RCP Bus
Honeywell RDR-2XXX with Dual Radar Control Panel:
ARINC 429
Control Bus
Weather Radar
R/T Unit
Pilot-Side MFD
ARINC 429
RCP Bus
Pilot
Weather Radar
Control Panel
ARINC 429
RCP Bus
CoPilot
Weather Radar
Control Panel
ARINC 453
Display Bus
ARINC 429
Control Bus
CoPilot-Side MFD
5.2.18.2 Weather Radar Module
The Weather Radar Module converts the ARINC 453 Display Bus data into high-speed
serial data for use by the IDU, and converts high-speed serial data from the IDU into
low-speed ARINC 429 Control Bus data. Duplex communications between the
Weather Radar Module and the IDU shall [SYS_COM_328] use integrated peripheral
high-speed bus #1.
01-000028-070F
Chelton Flight Systems – Confidential
Page 83 of 104
5.2.18.2.1 Communication Parameters
Communications shall [SYS_COM_329] use logic-level serial data. Data shall
[SYS_COM_330] be transmitted with 1 start bit, 8 data bits, 1 stop bit, and no parity.
Transmission speed shall [SYS_COM_331] be 460,800 baud.
5.2.18.2.2 ARINC 453 Display Bus Packet Description
Upon each successful processing of an ARINC 453 1600-bit display word, the Weather
Radar Module shall [SYS_COM_332] transmit the word in a proprietary run-length
encoded packet to the IDU as specified in the Weather Radar Module SYRD (Doc. No.
9464-010).
Upon receipt of the packet, the IDU shall [SYS_COM_333] decode and process the data.
Data decoding is depended upon the weather radar type selected in the aircraft limits
(Ref: 01-000029-070F). The following labels are defined:
Label 055 (All Architectures):
All weather radar types transmit this label. The IDU shall [SYS_COM_334] process
label 055 as follows:
Bits
1–8
9 – 10
Field
Label
Control Accept
11
Varies
12
Varies
13
Varies
01-000028-070F
Processing and Usage
Octal 055
00b
Do no accept
01b
Control/Display #1 accept
10b
Control/Display #2 accept
11b
All Controls/Displays accept
Note:
For airplanes, #1 is Pilot-Side and #2 is CoPilot-Side.
For rotorcraft, #1 is CoPilot-Side and #2 is Pilot-Side.
ARINC 708-6:
1 = Slave
Collins 800/840:
1 = Slave
Honeywell Primus:
1 = Slave
Honeywell RDR-2XXX: Not Used
Note: MFD provides annunciation of Slave Mode on dedicated radar page.
ARINC 708-6:
Not Used
Collins 800/840:
1 = Autotilt Mode Engaged
Honeywell Primus:
1 = Target (Weather) Alert Detected
Honeywell RDR-2XXX: Not Used
Note: MFD provides annunciation of weather alert through caution
associated with weather display.
ARINC 708-6:
Not Used
Collins 800/840:
Not Used
Honeywell Primus:
1 = REACT Mode Engaged
Honeywell RDR-2XXX: Not Used
Note: MFD provides annunciation of REACT Mode on dedicated radar page.
Chelton Flight Systems – Confidential
Page 84 of 104
Bits
14
Field
Varies
15
Varies
16
Varies
17
Sector Scan
18
Stab Limit
19
Cooling Fault
20
Varies
21
Varies
22
Varies
23
Control Fault
24
Antenna Fault
25
T/R Fault
01-000028-070F
Processing and Usage
ARINC 708-6:
1 = Turbulence Alert Detected
Collins 800/840:
1 = Turbulence Alert Detected
Honeywell Primus:
Not Used
Honeywell RDR-2XXX: Not Used
Note: MFD provides annunciation of turbulence alert through caution
associated with weather display.
ARINC 708-6:
1 = Weather Alert Detected
Collins 800/840:
1 = Weather Alert Detected
Honeywell Primus:
1 = Target (Weather) Alert Mode Engaged
Honeywell RDR-2XXX: 1 = Target (Weather) Alert Mode Engaged
Note: MFD provides annunciation of weather alert through caution
associated with weather display. MFD provides annunciation of Target Alert
Mode on dedicated radar page.
ARINC 708-6:
1 = Anticlutter Mode Engaged
Collins 800/840:
1 = Anticlutter Mode Engaged
Honeywell Primus:
Not Used
Honeywell RDR-2XXX: Not Used
Note: MFD provides annunciation of Anticlutter Mode on dedicated radar
page.
1 = Sector Scan Active
Note: Not used by MFD.
1 = Stability Limit Exceeded
Note: Used by MFD to provide stability limit alert on moving map and
dedicated radar pages.
1 = R/T Cooling Fault Detected
Note: Fault detection used by MFD to determine weather radar failure status
as reflected in weather radar mode annunciators and FAULTS menu.
ARINC 708-6:
1 = Display Fault Detected
Collins 800/840:
1 = Control Bus Fault Detected
Honeywell Primus:
Not Used
Honeywell RDR-2XXX: 1 = Target (Weather) Alert Detected
Note: Fault detection used by MFD to determine weather radar failure status
as reflected in weather radar mode annunciators and FAULTS menu. MFD
provides annunciation of weather alert through caution associated with
weather display.
ARINC 708-6:
1 = Calibration Fault Detected
Collins 800/840:
1 = Calibration Fault Detected
Honeywell Primus:
1 = Air Data Input Fault Detected
Honeywell RDR-2XXX: Not Used
Note: Fault detection used by MFD to determine weather radar failure status
as reflected in weather radar mode annunciators and FAULTS menu.
ARINC 708-6:
1 = Attitude Fault Detected
Collins 800/840:
1 = Attitude Fault Detected
Honeywell Primus:
1 = Attitude Fault Detected
Honeywell RDR-2XXX: 1 = Range Fault Detected
Note: Fault detection used by MFD to determine weather radar failure status
as reflected in weather radar mode annunciators and FAULTS menu.
1 = Control Fault Detected
Note: Fault detection used by MFD to determine weather radar failure status
as reflected in weather radar mode annunciators and FAULTS menu.
1 = Antenna Fault Detected
Note: Used by MFD to provide antenna fault alert on moving map and
dedicated radar pages.
1 = T/R Fault Detected
Note: Fault detection used by MFD to determine weather radar failure status
as reflected in weather radar mode annunciators and FAULTS menu.
Chelton Flight Systems – Confidential
Page 85 of 104
Bits
26
Field
Stabilization
27 -- 29
Mode
30 – 36
Tilt
37 – 42
Gain
43 – 48
Range
49
Varies
01-000028-070F
Processing and Usage
1 = ON
Note: When stabilization if OFF, MFD provides annunciation on dedicated
radar page.
000b STBY (Standby)
001b WX (Weather Only)
010b GMAP (Ground Mapping)
011b ARINC 708-6:
CONT (Contour)
Collins 800/840:
Not Used
Honeywell PRIMUS:
Not Used
Honeywell RDR-2XXX: Not Used
100b TEST
101b ARINC 708-6:
TURB (Turbulence Only)
Collins 800/840:
TURB (Turbulence Only)
Honeywell PRIMUS:
FSTBY (Forced Standby)
Honeywell RDR-2XXX: Not Used
110b ARINC 708-6:
WX/T (Weather + Turbulence)
Collins 800/840:
WX/T (Weather + Turbulence)
Honeywell PRIMUS:
WX/T (Weather + Turbulence)
Honeywell RDR-2XXX: Not Used
111b ARINC 708-6:
Not Used
Collins 800/840:
Target (Weather) Alert Mode Engaged
Honeywell PRIMUS:
Not Used
Honeywell RDR-2XXX: Not Used
Note: MFD provides mode annunciation as “WXR: #####” on moving map
and dedicated radar pages. MFD provides annunciation to Target Alert Mode
on dedicated radar page.
Two’s complement tilt angle with values as follows:
30
+ 0.25°
31
+ 0.50°
32
+ 1.00°
33
+ 2.00°
34
+ 4.00°
35
+ 8.00°
36
-16.00°
Note: MFD provides tilt annunciation on dedicated radar page. When value
is -16°, MFD tilt is annunciated as “AUTO.”
ARINC 708-6:
0x00 = MAX
0x3F = CAL
Others = -( value ) dB
Collins 800/840:
0x00 = MAX
0x3F = CAL
Others = ( 18 – value ) dB
Honeywell Primus:
0x00 = MAX
0x3F = CAL
Others = -( value ) dB
Honeywell RDR-2XXX: 0x00 = MAX
0x3F = CAL
Others = -( value / 2 ) dB
Note: MFD provides gain annunciation on dedicated radar page.
0x00 = 320NM
Others = ( value x 5 ) NM
Note: Range determines the ray length for MFD rendering.
ARINC 708-6:
Not Used
Collins 800/840:
Not Used
Honeywell Primus:
1 = Divide Range by 20
Honeywell RDR-2XXX: Not Used
Note: Used by Honeywell Primus to provide 2.5NM range for AC 90-80B
compliance.
Chelton Flight Systems – Confidential
Page 86 of 104
Bits
50 – 51
Field
Varies
52 – 63
Scan Angle
64
Varies
65 – 70
Varies
71 – 1600
Range Bins
01-000028-070F
Processing and Usage
ARINC 708-6:
Indicator Accept
Collins 800/840:
Indicator Accept
Honeywell Primus:
Indicator Accept
Honeywell RDR-2XXX: Display 3/4 Accept
Note: Not used by MFD. Bits 9 – 10 used instead.
Two’s complement scan angle with values as follows:
52
+ 0.087890625°
53
+ 0.17578125°
54
+ 0.3515625°
55
+ 0.703125°
56
+ 1.40625°
57
+ 2.8125°
58
+ 5.625°
59
+ 11.25°
60
+ 22.5°
61
+ 45°
62
+ 90°
63
-180°
Note: Scan angle determines the ray direction for MFD rendering.
ARINC 708-6:
Not Used
Collins 800/840:
0 = ARINC 708 Data Format
1 = RTA-800 Data Format
Honeywell Primus:
Altitude Compensated Tilt (ACT) Engaged
Honeywell RDR-2XXX: 0 = Strut Switch Closed (Ground)
1 = Strut Switch Open (Air)
Note: For Collins 800/840, this bit must be 0 to accept data. Not used by
MFD in all other cases.
ARINC 708-6:
Range Bins 1 and 2 (see below)
Collins 800/840:
65 = Right Heading Change
66 = Left Heading Change
67 = Stabilization Trim
68 = Range Change Forward
69 = Data Format (0 = 3-bit 1 = 6-bit)
70 = Not used.
Honeywell Primus:
Range Bins 1 and 2 (see below)
Honeywell RDR-2XXX: Range Bins 1 and 2 (see below)
Note: For Collins 800/840, bit 69 must be 0 to accept data (bits 65-68 and 70
are not used). In all other cases, process as range bin data. Due to usage of
the first two range bins, the first two range bins will always be filled with
BLACK when processing data from a Collins 800/840 installation.
3-bit range bin data indicating color as follows:
000b BLACK
001b GREEN
010b YELLOW
011b RED
100b MAGENTA
101b CYAN
110b LT. GRAY
111b WHITE
Note: Used to color ray for MFD rendering.
Chelton Flight Systems – Confidential
Page 87 of 104
The following data acceptance rules shall [SYS_COM_335] be followed for label 055:
1. Weather Radar Type = ARINC 708-6: Data will be accepted so long as:

The control accept parameter (bits 9 – 10) matches the receiving IDU.

The scan angle is within the expected weather radar scan width (ref: 01000029-070F).

A radar fault does not exist. For ARINC 708-6, the following items are
considered radar faults:
a. Cooling Fault (ARINC 453 Label 055 Bit 19);
b. Display Fault (ARINC 453 Label 055 Bit 20);
c. Calibration Fault (ARINC 453 Label 055 Bit 21);
d. Attitude Fault (ARINC 453 Label 055 Bit 22);
e. Control Fault (ARINC 453 Label 055 Bit 23); and
f. TR Fault (ARINC 453 Label 055 Bit 25).
2. Weather Radar Type = Collins 800/840: Data will be accepted so long as:

The control accept parameter (bits 9 – 10) matches the receiving IDU.

The scan angle is within the expected weather radar scan width (ref: 01000029-070F).

A radar fault does not exist. For Collins 800/840, the following items are
considered radar faults:
a. Cooling Fault (ARINC 453 Label 055 Bit 19);
b. Control Bus Fault (ARINC 453 Label 055 Bit 20);
c. Calibration Fault (ARINC 453 Label 055 Bit 21);
d. Attitude Fault (ARINC 453 Label 055 Bit 22);
e. Control Fault (ARINC 453 Label 055 Bit 23); and
f. TR Fault (ARINC 453 Label 055 Bit 25).

The data format bit (bit 64) indicates ARINC 708 format.

The range bin format bit (bit 69) indicates 3-bit format.
3. Weather Radar Type = Honeywell Primus: Data will be accepted so long as:

The control accept parameter (bits 9 – 10) matches the receiving IDU.

The scan angle is within the expected weather radar scan width (ref: 01000029-070F).
01-000028-070F
Chelton Flight Systems – Confidential
Page 88 of 104

A radar fault does not exist. For Honeywell Primus, the following items are
considered radar faults:
a. Cooling Fault (ARINC 453 Label 055 Bit 19);
b. Air Data Fault (ARINC 453 Label 055 Bit 21);
c. Attitude Fault (ARINC 453 Label 055 Bit 22);
d. Control Fault (ARINC 453 Label 055 Bit 23); and
e. TR Fault (ARINC 453 Label 055 Bit 25).
4. Weather Radar Type = Honeywell RDR-2XXX: Data will be accepted so long as:

The commanded mode is not OFF.

Vertical profile mode is not the commanded orientation.

The control accept parameter (bits 9 – 10) matches the receiving IDU. Note
that this check is skipped when the commanded mode is STBY.

The scan angle is within the expected weather radar scan width (ref: 01000029-070F).

A radar fault does not exist. For Honeywell RDR=2XXX, the following items
are considered radar faults:
a. Cooling Fault (ARINC 453 Label 055 Bit 19);
b. Range Fault (ARINC 453 Label 055 Bit 22);
c. Control Fault (ARINC 453 Label 055 Bit 23); and
d. TR Fault (ARINC 453 Label 055 Bit 25).

The radar mode (bits 27 – 29) matches the commanded mode (Label 270
bits 14 – 16, see § 5.2.18.2.3). Note that this check is skipped when the
commanded mode is STBY.

The radar range (bits 43 – 48) matches the commanded range (Label 271
bits 24 – 29, see § 5.2.18.2.3). Note that this check is skipped when the
commanded mode is STBY.

The radar tilt (bits 30 – 36) matches the commanded tilt (Label 270 bits 17 –
23, see § 5.2.18.2.3). Note that for the RDR-2100, this comparison is not
made when in Auto Step Scan mode. Note that this check is skipped when
the commanded mode is STBY.

The radar gain (bits 37 – 42) matches the commanded gain (Label 270 bits
24 – 29, see § 5.2.18.2.3). Note that this check is skipped when the
commanded mode is STBY.
01-000028-070F
Chelton Flight Systems – Confidential
Page 89 of 104
Label 171 (RDR-2XXX Only):
This label shall [SYS_COM_336] only be processed when the aircraft limits specify an
RDR-2XXX weather radar type. See APPENDIX F: System Requirements Document
for ART 2000/2100 page 64 for the label definition. IDU shall [SYS_COM_337]
process label 171 as follows:
Bits
1–8
9 – 10
11 -- 16
Field
Label
Control Accept
Gain
17
Sector Scan
18
Stab Limit
19
Cooling Fault
20
Target Alert
21
22
Not Used
Range Fault
23
Control Fault
24
Antenna Fault
25
T/R Fault
26
Stabilization
01-000028-070F
Processing and Usage
Octal 171
00b
Do no accept
01b
Control/Display #1 accept
10b
Control/Display #2 accept
11b
All Controls/Displays accept
Note:
For airplanes, #1 is Pilot-Side and #2 is CoPilot-Side.
For rotorcraft, #1 is CoPilot-Side and #2 is Pilot-Side.
0x00 = MAX
0x3F = CAL
Others = -( value / 2 ) DB
Note: MFD provides gain annunciation on dedicated radar page.
1 = Sector Scan Active
Note: Not used by MFD.
1 = Stability Limit Exceeded
Note: Used by MFD to provide stability limit alert on moving map and
dedicated radar pages.
1 = R/T Cooling Fault Detected
Note: Fault detection used by MFD to determine weather radar failure status
as reflected in weather radar mode annunciators and FAULTS menu.
1 = Target (Weather) Alert Detected
Note: MFD provides annunciation of weather alert through caution
associated with weather display.
Note: Not used by MFD.
1 = Range Fault Detected
Note: Fault detection used by MFD to determine weather radar failure status
as reflected in weather radar mode annunciators and FAULTS menu.
1 = Control Fault Detected
Note: Fault detection used by MFD to determine weather radar failure status
as reflected in weather radar mode annunciators and FAULTS menu.
1 = Antenna Fault Detected
Note: Fault detection used by MFD to determine weather radar failure status
as reflected in weather radar mode annunciators.
1 = T/R Fault Detected
Note: Fault detection used by MFD to determine weather radar failure status
as reflected in weather radar mode annunciators and FAULTS menu.
1 = ON
Note: When stabilization is OFF, MFD provides annunciation on dedicated
radar page.
Chelton Flight Systems – Confidential
Page 90 of 104
Bits
27 -- 29
Field
Mode
30 – 41
Azimuth
Position
42
43 – 48
Not Used
Range
49
50 – 51
Not Used
Data Accept
52 – 63
Tilt Angle
64
65 – 1600
Tilt Scan
Direction
Range Bins
01-000028-070F
Processing and Usage
000b STBY (Standby)
001b WX (Weather Only)
010b GMAP (Ground Mapping)
011b Not Used
100b TEST
101b Not Used
110b Not Used
111b Not Used
Note: MFD provides mode annunciation as “WXR: #####” on moving map
and dedicated radar pages.
Two’s complement azimuth position (track) with values as follows:
30
+ 0.087890625°
31
+ 0.17578125°
32
+ 0.3515625°
33
+ 0.703125°
34
+ 1.40625°
35
+ 2.8125°
36
+ 5.625°
37
+ 11.25°
38
+ 22.5°
39
+ 45°
40
+ 90°
41
-180°
Note: MFD provides readout of azimuth position when on dedicated radar
page in Vertical Profile mode.
Note: Not used by MFD.
0x00 = 320NM
Others = ( value x 5 ) NM
Note: Range determines the ray length for MFD rendering.
Note: Not used by MFD.
Display 3/4 Accept
Note: Not used by MFD. Bits 9 – 10 used instead.
Two’s complement tilt angle with values as follows:
52
+ 0.087890625°
53
+ 0.17578125°
54
+ 0.3515625°
55
+ 0.703125°
56
+ 1.40625°
57
+ 2.8125°
58
+ 5.625°
59
+ 11.25°
60
+ 22.5°
61
+ 45°
62
+ 90°
63
-180°
Note: Tilt angle determines the ray direction for MFD rendering.
1 = Down
Note: Not used by MFD.
3-bit range bin data indicating color as follows:
000b BLACK
001b GREEN
010b YELLOW
011b RED
100b MAGENTA
101b CYAN
110b LT. GRAY
111b WHITE
Note: Used to color ray for MFD rendering.
Chelton Flight Systems – Confidential
Page 91 of 104
Label 171 data shall [SYS_COM_338] be accepted so long as:

The commanded mode is not OFF.

Vertical profile mode is the commanded orientation.

The control accept parameter (bits 9 – 10) matches the receiving IDU. Note
that this check is skipped when the commanded mode is STBY.

The tilt angle is reasonable.

A radar fault does not exist. For Honeywell RDR=2XXX, the following items
are considered radar faults:
a. Cooling Fault (ARINC 453 Label 055 Bit 19);
b. Range Fault (ARINC 453 Label 055 Bit 22);
c. Control Fault (ARINC 453 Label 055 Bit 23); and
d. TR Fault (ARINC 453 Label 055 Bit 25).

The radar mode (bits 27 – 29) matches the commanded mode (Label 270
bits 14 – 16, see § 5.2.18.2.3). Note that this check is skipped when the
commanded mode is STBY.

The radar range (bits 43 – 48) matches the commanded range (Label 271
bits 24 – 29, see § 5.2.18.2.3). Note that this check is skipped when the
commanded mode is STBY.

The radar azimuth (bits 30 – 41) matches the commanded azimuth (Label
273 bits 13 – 24, see § 5.2.18.2.3). Note that this check is skipped when the
commanded mode is STBY.

The radar gain (bits 37 – 42) matches the commanded gain (Label 270 bits
24 – 29, see § 5.2.18.2.3). Note that this check is skipped when the
commanded mode is STBY.
5.2.18.2.3 ARINC 429 Control Bus Packet Description (RDR-2XXX Only)
The IDU shall [SYS_COM_339] transmit control words in a proprietary packet to the
Weather Radar Module as specified in the Weather Radar Module SYRD (Doc. No.
9464-010).
01-000028-070F
Chelton Flight Systems – Confidential
Page 92 of 104
Upon receipt of the packet, the Weather Radar Module sends the decoded ARINC 429
data to the weather radar. The Control Bus labels shall [SYS_COM_340] be sent at 5Hz
and shall [SYS_COM_341] be formatted (labels 270, 271, 273 and 275) as follows:
Label 270:
Bits
01 – 08
09 – 10
11
12
13
14 – 16
17 -- 23
24 -- 29
30 -- 31
32
Function
Label (Octal 270)
Not Used (Pad Zeroes)
Sector Scan: Fill from RCP Bus Label 307 Bit 11.
Anti-Clutter: Fill from RCP Bus Label 307 Bit 12.
Stabilization: Fill from RCP Bus Label 301 Bit 30.
Weather Radar Mode: Fill from RCP Bus Label 300 Bits 11 – 14 as follows:
Label 300
Label 270
14
13
12
11
16
15
14
OFF
1
1
1
0
0
0
0
STBY 1
1
0
1
0
0
0
TEST 1
0
1
1
1
0
0
ON
0
1
1
1
See Note
Note: Either 001b (WX or WXA) or 010b (GMAP) is sent, depending upon the internally kept
submode selection controlled by RCP button presses transmitted on Label 301.
Tilt: Fill from RCP Bus Label 305 Bits 19 – 26 so long as RCP Bus Label 305 Bit 28 is 1.
Note that for RDR-2XXX, tilt is limited to +/- 15 degrees.
Gain: Fill from RCP Bus Label 306 Bits 11 – 18 so long as RCP Bus Label 306 Bit 27 is 1.
SSM as follows:
Valid Data:
00b
Invalid Data:
01b
Functional Test:
10b
Slave:
11b
Notes:
Invalid Data set when the RCP status is bad. This is defined as any of the following:
 Label 300 not fresh
 Label 301 not fresh
 Label 302 not fresh or indicates and RCP failure
 Label 305 not fresh
 Label 305 Bit 28 is 0
 Label 306 not fresh
 Label 306 Bit 27 is 0
 Label 307 not fresh
Functional Test and Slave not used.
Odd Parity
01-000028-070F
Chelton Flight Systems – Confidential
Page 93 of 104
Label 271:
Bits
01 – 08
09 – 11
12
13 – 18
19 – 23
24 -- 29
30 -- 31
32
Function
Label (Octal 271)
Not Used (Pad Zeroes)
ARL: Fill from the inverse of RCP Bus Label 301 Bit 17.
Roll Trim data. Fill from RCP Bus Label 305 Bits 13 – 18 so long as RCP Bus Label 305 Bit
27 is 1. Note that RCP Bus Label 305 Bits 11 (the LSb) and 12 are ignored.
Not Used (Pad Zeroes)
Range: Sent from internal MFD parameter. Tie to range selection on the dedicated radar
page or moving map page. The following ranges are valid:
29
28
27
26
25
24
5NM
0
0
0
0
0
1
10NM
0
0
0
0
1
0
20NM
0
0
0
1
0
0
40NM
0
0
1
0
0
0
80NM
0
1
0
0
0
0
160NM
1
0
0
0
0
0
240NM
1
1
0
0
0
0
320NM
0
0
0
0
0
0
Note: 5NM and 320NM ranges only sent when RDR-2100 selected in aircraft limits.
SSM as follows:
Valid Data:
00b
Invalid Data:
01b
Functional Test:
10b
Slave:
11b
Notes:
Invalid Data set when the RCP status is bad. This is defined as any of the following:
 Label 300 not fresh
 Label 301 not fresh
 Label 302 not fresh or indicates and RCP failure
 Label 305 not fresh
 Label 305 Bit 28 is 0
 Label 306 not fresh
 Label 306 Bit 27 is 0
 Label 307 not fresh
Functional Test and Slave not used.
Odd Parity
01-000028-070F
Chelton Flight Systems – Confidential
Page 94 of 104
Label 273:
Bits
01 – 08
09 – 10
11
12
13 – 24
Function
Label (Octal 273)
Not Used (Pad Zeroes)
1 = Profile Enable. Value depends upon the internally kept vertical profile selection controlled
by RCP button presses transmitted on Label 301.
Not Used (Pad Zero)
Profile Azimuth Position. Convert from RCP Bus Label 307 Bits 19 – 25 depending upon the
weather radar scan width parameter in the aircraft limits as follows:
Azimuth Position (°) = (Value – 64) * (scan width / 2) / 64
25 – 29
30 -- 31
32
Encode two’s complement azimuth position as follows:
13
+ 0.087890625°
14
+ 0.17578125°
15
+ 0.3515625°
16
+ 0.703125°
17
+ 1.40625°
18
+ 2.8125°
19
+ 5.625°
20
+ 11.25°
21
+ 22.5°
22
+ 45°
23
+ 90°
24
-180°
Not Used (Pad Zeroes)
SSM as follows:
Valid Data:
00b
Invalid Data:
01b
Functional Test:
10b
Slave:
11b
Notes:
Invalid Data set when the RCP status is bad. This is defined as any of the following:
 Label 300 not fresh
 Label 301 not fresh
 Label 302 not fresh or indicates and RCP failure
 Label 305 not fresh
 Label 305 Bit 28 is 0
 Label 306 not fresh
 Label 306 Bit 27 is 0
 Label 307 not fresh
Functional Test and Slave not used.
Odd Parity
01-000028-070F
Chelton Flight Systems – Confidential
Page 95 of 104
Label 275:
Bits
01 – 08
09 – 16
17
18 – 29
30 -- 31
32
Function
Label (Octal 275)
Not Used (Pad Zeroes)
1 = Auto Step Scan
Not Used (Pad Zeroes)
SSM as follows:
Valid Data:
00b
Invalid Data:
01b
Functional Test:
10b
Slave:
11b
Notes:
Invalid Data set when the RCP status is bad. This is defined as any of the following:
 Label 300 not fresh
 Label 301 not fresh
 Label 302 not fresh or indicates and RCP failure
 Label 305 not fresh
 Label 305 Bit 28 is 0
 Label 306 not fresh
 Label 306 Bit 27 is 0
 Label 307 not fresh
Functional Test and Slave not used.
Odd Parity
5.2.18.3 ARINC 429 RCP Bus (RDR-2XXX Only)
RCP Bus labels are received on the ARINC 429 receive port that is configured for the
“RDR-2XXX Radar Control Panel RX Group” (see § 5.2.11.2.2 above) in the aircraft limits
(ref: 01-000029-070F). Data from these label is used to construct the ARINC 429
Control Bus packet (see § 5.2.18.2.3 above). In a single Radar Control Panel installation,
certain parameters will also be sent on intra and inter-system messages to ensure
synchronization (see §§ 5.2.1.10 and 5.2.2.9).
01-000028-070F
Chelton Flight Systems – Confidential
Page 96 of 104
5.2.19 ARINC 429 Expansion Module (IDU-450/680 Only)
The ARINC 429 Expansion Module converts between IDU high-speed serial data and
ARINC 429 messages transmitted to and received from aircraft devices. The ARINC
429 Expansion Module supports four ARINC 429 receiver ports and two ARINC 429
transmit ports. Duplex communications between the ARINC 429 Expansion Module
and the IDU shall [SYS_COM_343] use integrated peripheral high-speed bus #2.
5.2.19.1.1 Communication Parameters
Communications shall [SYS_COM_344] use logic-level serial data. Data shall
[SYS_COM_345] be transmitted with 1 start bit, 8 data bits, 1 stop bit, and no parity.
Transmission speed shall [SYS_COM_346] be 460,800 baud.
5.2.19.1.2 Packet Description
The IDU shall [SYS_COM_347] transmit and receive ARINC 429 words from the ARINC
429 Expansion Module in proprietary packets as specified in the ARINC 429 Expansion
Module SYRD (Doc. No. 9465-010).
01-000028-070F
Chelton Flight Systems – Confidential
Page 97 of 104
6
NOTES:
None.
01-000028-070F
Chelton Flight Systems – Confidential
Page 98 of 104
APPENDIX A: STORMSCOPE WX-500 INTERFACE DEVELOPER’S GUIDE
01011501.pdf
APPENDIX B: 9900 SERIES TCAD THIRD PARTY INTERFACE PROTOCOL
Third Party Interface
Protocol - 20020528.PDF
APPENDIX C: WSI INFLIGHT WEATHER INTERFACE CONTROL DOCUMENT
WSI_ICD_rev_19.pd
f
APPENDIX D: GDL 90 DATA INTERFACE SPECIFICATION
GDL90_Public_ICD_R
evA.pdf
APPENDIX E: ALTIMETERS PROTOCOLS SPECIFICATION
06980syrdxx.ps.al.1
.0.pdf
APPENDIX F: SYSTEM REQUIREMENTS DOCUMENT FOR ART 2000/2100
701-00506-0000.pdf
01-000028-070F
Chelton Flight Systems – Confidential
Page 99 of 104
APPENDIX G: ARINC LABEL DETAILED DEFINITIONS
HeliSAS-E Label 155 definition is as follows:
Bits
01 – 08
09 – 10
11-19
20
21
22
23
24
25
26
27
28
29
30 – 31
32
Function
Label (Octal 155)
SDI (Not Used, Pad 0)
Pad Bits
0.0998046875°/bit
0.199609375°/bit
0.39921875°/bit
0.7984375°/bit
1.596875°/bit
3.19375°/bit
6.3875°/bit
12.775°/bit
25.55°/bit
Sign
SSM (Use BNR Format, 11 = Normal Operation)
Odd Parity
HeliSAS-E Label 270 definition is as follows:
Bits
01 – 08
09 – 10
11 – 25
26
27
28
29
30 – 31
32
Function
Label (Octal 270)
SDI (Pilot Side = 01, Co-Pilot Side = 10)
Reserved
EFIS True North Mode (1 = True North Mode engaged)
GPS Selecte (1 = GPS Selected)
ILS or GPS Approach Enable (1 = Enabled)
Active ADAHRS (0 = ADAHRS#1, 1 = ADAHRS#2)
SSM (Use Discrete Format, 00 = Normal Operation)
Odd Parity
01-000028-070F
Chelton Flight Systems – Confidential
Page 100 of 104
Honeywell EFIS 40/50 Label 300 definition is as follows:
Bits
01 – 08
09 – 10
11
12
13
14 – 19
20 – 21
22
23
24
25
26
27
28
29
30 – 31
32
Function
Label (Octal 300)
SDI (Pad Zeroes)
Selected Sensor Side (0 = Side 1, 1 = Side 2)
NAV Source Key Active Bit (0 = Inactive, 1 = Active)
Precision Approach Mode (0 = Not ILS or MLS, 1 = ILS or MLS)
Selected Sensor:
19
18
17
16
15
14
0
0
0
0
0
0
No Mode
0
0
0
0
0
1
Test
0
0
0
0
1
0
VOR
0
0
0
0
1
1
ADF
0
0
0
1
0
0
TACAN
0
0
0
1
0
1
LOC
0
0
0
1
1
0
MLS
0
0
0
1
1
1
Not Used
0
0
1
0
0
0
NAV
0
0
1
0
0
1
OMEGA
0
0
1
0
1
0
LORAN
0
0
1
0
1
1
Doppler
0
0
1
1
0
0
RNAV
0
0
1
1
0
1
FMS
0
0
1
1
1
0
Cable
0
0
1
1
1
1
Homing
0
1
0
0
0
0
GPS
No other codes defined.
Selected Sensor Side (Output to Autopilot):
21
20
0
1
Side 1
1
0
Side 2
Test Mode (0 = No Test, 1 = Test Mode)
Bearing Source Selected (0 = No Bearing Source Selected, 1 = Bearing Source Selected)
DDM Source Selected (0 = No DDM Source Selected, 1 = DDM (MLS or ILS) Source
Selected)
Waypoint Deviation Processing (0 = No LNAV Source Selected, 1 = LNAV Source Selected)
VNAV (for future use – pad zero)
Vertical Gyro Side (0 = Side 1, 1 = Side 2)
Directional Gyro Side (0 = Side 1, 1 = Side 2)
EFIS Magnetic/True Mode (0 = True Mode, 1 = Magnetic Mode)
SSM (Use BNR Format, 11 = Normal Operation)
Odd Parity
01-000028-070F
Chelton Flight Systems – Confidential
Page 101 of 104
Honeywell EFIS 40/50 Label 301 definition is as follows:
Bits
01 – 08
09 – 10
11
12
13
14
15
16 – 20
21
22
23
24
25
26
27 – 28
29
30 – 31
32
Function
Label (Octal 301)
SDI (Pad Zeroes)
Outer Marker (0 = No Outer Marker Detected, 1 = Outer Marker Detected)
Middle Marker (0 = No Middle Marker Detected, 1 = Middle Marker Detected)
Inner Marker (0 = No Inner Marker Detected, 1 = Inner Marker Detected)
EFIS Mode Change (0 = No Mode Change, 1 = Mode Change)
Note: Upon a mode change, this bit will stay active for 2 transmissions (~1 second).
Backcourse (0 = No Back Course Mode, 1 = Back Course Mode)
NAV Key Button Selection:
20
19
18
17
16
0
0
0
0
0
VOR/LOC/TACAN/RNAV
0
0
0
0
1
TACAN
0
0
0
1
0
FMS
0
0
0
1
1
LORAN
0
0
1
0
0
OMEGA
0
0
1
0
1
GPS
0
0
1
1
0
NAV
0
0
1
1
1
MLS
0
1
0
0
0
ADF
0
1
0
0
1
Doppler
0
1
0
1
0
Cable
0
1
0
1
1
Homing
No other codes defined.
Reversion Mode (0 = Normal, 1 = Reversion)
TCAS Display Active (0 = Traffic Display Off, 1 = Traffic Display On)
High Speed Text Display Active (0 = Not Active, 1 = Active)
Test Mode (0 = No Test, 1 = Test Mode)
Low Speed Text Display Active (0 = Not Active, 1 = Active)
MLS BAZ Mode (0 = No MLS BAZ Mode, 1 = MLS BAZ Mode)
LNAV Mode:
21
20
0
0
RNAV Enroute Mode
0
1
RNAV Approach Mode
1
0
NAV Mode
1
1
ILS Mode
Spare (Pad Zero)
SSM (Use BNR, 11 = Normal Operation)
Odd Parity
01-000028-070F
Chelton Flight Systems – Confidential
Page 102 of 104
Honeywell Radar Control Panel Label 300 definition is as follows:
Bits
01 – 08
09 – 10
11 – 14
15 – 26
27
28 – 31
32
Function
Label (Octal 300)
SDI (Pad Zeroes)
Weather Radar Mode:
14
13
12
1
1
1
1
1
0
1
0
1
0
1
1
Not Used
Auto Tilt (0 = ON 1 = OFF)
Not Used
Odd Parity
11
0
1
1
1
OFF
STBY
TEST
ON (Air Mode) or STBY (Ground Mode)
Honeywell Radar Control Panel Label 301 definition is as follows:
Bits
01 – 08
09 – 10
11
12
13
14
15
16
17
18 – 27
28
29
30
31
32
Function
Label (Octal 301)
SDI (Pad Zeroes)
WX Button (0 = Pressed 1 = Not Pressed)
WXA Button (0 = Pressed 1 = Not Pressed)
Not Used
GND MAP Button (0 = Pressed 1 = Not Pressed)
Not Used
Not Used
ARL (Automatic Range Limit) (0 = ON 1 = OFF)
Not Used
VP Button (0 = Pressed 1 = Not Pressed)
Not Used
Stab Off (0 = Stab OFF 1 = Stab Normal)
Not Used
Odd Parity
Honeywell Radar Control Panel Label 302 definition is as follows:
Bits
01 – 08
09 – 10
11
12
13
14
15
16
17
18 – 31
32
Function
Label (Octal 302)
SDI (Pad Zeroes)
EPROM Sum Flag (0 = Fail 1 = Normal)
RAM Test Flag (0 = Fail 1 = Normal)
ADC Calibration Flag (0 = Fail 1 = Normal)
ALU Test Flag (0 = Fail 1 = Normal)
Execution Flag (0 = Fail 1 = Normal)
Warm Start Flag (0 = Fail 1 = Normal)
Keyboard Data Flag (0 = Fail 1 = Normal)
Not Used
Odd Parity
01-000028-070F
Chelton Flight Systems – Confidential
Page 103 of 104
Honeywell Radar Control Panel Label 305 definition is as follows:
Bits
01 – 08
09 – 10
11 – 18
19 – 26
27
28
29 – 31
32
Function
Label (Octal 305)
SDI (Pad Zeroes)
Roll Trim. 0x00 is full CCW. 0xFF is full CW.
Tilt Knob. 0x00 is full CCW. 0xFF is full CW.
Roll Trim Flag (0 = Fail 1 = Normal)
Tilt Flag (0 = Fail 1 = Normal)
Not Used
Odd Parity
Honeywell Radar Control Panel Label 306 definition is as follows:
Bits
01 – 08
09 – 10
11 – 18
19 – 26
27
28 – 31
32
Function
Label (Octal 306)
SDI (Pad Zeroes)
Gain Knob. 0x00 is full CCW. 0xFF is full CW.
Not Used
Gain Flag (0 = Fail 1 = Normal)
Not Used
Odd Parity
Honeywell Radar Control Panel Label 307 definition is as follows:
Bits
01 – 08
09 – 10
11
12
13 – 18
19 – 25
26 – 31
32
Function
Label (Octal 307)
SDI (Pad Zeroes)
Sector Scan (0 = OFF 1 = ON)
Anti-clutter (0 = OFF 1 = ON)
Not Used
Non-Dimensional Track Position (0 – 127). 0 corresponds to the left-most edge of the lateral
scan volume. 127 corresponds to the right-most edge of the lateral scan volume.
Not Used
Odd Parity
01-000028-070F
Chelton Flight Systems – Confidential
Page 104 of 104