|
AEEC Technical Application Bulletins
Clarifications to Supplement 2 of ARINC Specification 665 |
|
Staff: |
Roy Oishi |
Reference: |
08-002/ABN-019 |
Effective: |
January 4, 2008 Until Rescinded |
Summary:
The purpose of this TAB is to clarify particular issues for new loadable software parts being built per ARINC 665-2 formats. This TAB is not intended to invalidate existing loadable software parts. In general, the preferred interpretation is that which is documented in ARINC 665-3.
|
Submit Feedback for this bulletin |
Cyclic Redundancy Codes (CRC) Test Cases |
|
Staff: |
Roy Oishi |
Reference: |
05-054/ABN-03 |
Effective: |
March 4, 2005 - Indefinite |
Summary:
ARINC Report 665, Loadable Software Standards, Section 4.0 defines the
use of Cyclic Redundancy Codes (CRC), also known as Cyclic Redundancy
Checks.
ARINC Report 665-3, Section 4.2.9, CRC Examples refers to Appendix
K, which provides guidance on the calculation of loadable software part
CRCs. Appendix K provides an orientation to, instructions for and
examples of Loadable Software CRCs and references sample files and
corresponding CRCs provided in electronic code formats in this Technical
Application Bulletin (TAB). |
Submit Feedback for this bulletin |
Discrete
Input/Output Impedance of ARINC Characteristics |
|
Staff: |
Roy Oishi |
Reference: |
04-171/ABN-001 |
Effective: |
August 6, 2004 - Indefinite |
Summary:
This Technical Application Bulletin provides guidance to
avionics manufacturers and aircraft systems integrators
for attaining proper operation when interfacing discrete
signal outputs from one avionics set with discrete signal
inputs of other avionics. Some newer avionics are configured
with discrete outputs that include short circuit protection.
Such equipment will fault when working into large capacitive
loads. Guidelines are provided herein for attaining interoperability. |
Submit
Feedback for this bulletin |
Information on the Comparison of AEEC Procedures with Other Standards Bodies |
|
Staff: |
Roy Oishi |
Reference: |
05-069/ABN-04 |
Effective: |
N/A |
Summary:
This report was prepared in answer to questions by some AEEC members
about how AEEC procedures contrast with other standards setting bodies. It
compares the methods used by AEEC to develop consensus documents for
publication as ARINC Standards with three other standards bodies: IEEE,
AIAA, and SAE. In addition, the requirements for acceptance as American
National Standards, administered by ANSI, are also compared.
This report is offered for information only. There is no intent to make any
modifications to existing AEEC procedures in order to conform to ANSI
requirements. |
Submit Feedback for this bulletin |
IP Addresses Used Onboard Aircraft |
|
Staff: |
Roy Oishi |
Reference: |
09-003/ABN-026 |
Effective: |
December 2008 Until Superceded |
Summary:
ARINC 664 Aircraft Data Network Part 4: Internet-based Address Structure and Assigned Numbers, identifies IP address ranges for various domains onboard the aircraft. This TAB collects known IP address assignments for various aircraft and ground system implementations in order to reduce conflicts among the various systems connected to the onboard IP network.
|
Submit Feedback for this bulletin |
List of Assigned Manufacturer's Codes (MMM) |
|
Staff: |
Scott L. Smith |
Reference: |
10-072/ABN-033 |
Effective: |
May 7, 2010 Until Superceded |
Summary:
ARINC Report 665, Loadable Software Standards, Section 2.0 defines the use of Manufacturer’s Codes, known as MMM Codes. ARINC Report 665-3, Attachment 1 refers to this Technical Application Bulletin (TAB) for the list of assigned MMM Codes. |
Submit Feedback for this bulletin |
Security Use Cases |
|
Staff: |
Roy T. Oishi |
Reference: |
08-205/ABN-023 |
Effective: |
June 2008 to
December 2009 |
Abstract:
This TAB documents various security scenarios which are intended to
ultimately be included in a security guidance document. |
Submit Feedback for this bulletin |
Software Data Loading, Networking and Security |
|
Staff: |
Roy T. Oishi |
Reference: |
06-111/ABN-012 |
Effective: |
March 1, 2006 to
December 31, 2007 |
Abstract:
This TAB was synthesized from a number of email threads exchanged in late 2005. ARINC Report 615A: Software Data Loader Using Ethernet Interface covers software data loading over Ethernet. However, certain basic assumptions were made about the network over which the SDL protocol would operate. This TAB highlights those assumptions and described some of the premises behind them and some considerations for the future. |
Submit Feedback for this bulletin |
UML Model and Data Sample Files for ARINC Specification 816 |
|
Staff: |
Sam Buckwalter |
Reference: |
06-014/ABN-09 |
Effective: |
January 19, 2006 - Open |
Abstract:
ARINC Specification 816: Embedded interchange Format for Airport Mapping Database, Section 3.0 and 4.0 define the schema for the airport mapping database. Section 5.0 provides a virtual airport data sample in the ARINC 816 coding. In this bulletin this information is provided digitally. It can be used to design ARINC 816-compliant data conversion software and to review the airport data sample in detail. |
Submit Feedback for this bulletin |
|
Staff Contact
Paul Prisaznuk
Industry Activities Staff
pjp@arinc.com
410.266.4113
|