Software Data Loader
(SDL) Subcommittee
Last Update:
January 6, 2012
Co-Chairman - Rod Gates, American Airlines
Co-Chairman - Ted Patmore, Delta Air Lines
APIM 08-005: XML Software Data Loading (pdf, 36K)
APIM 10-008A: Supplement 1 to ARINC Specification 826: Software Data Loading Using CAN Interface (pdf, 170K)
APIM 10-016A: Software Data loading Clarifications to ARINC 615-3 and ARINC 615-4 (pdf, 87K)
APIM 11-008: Central Maintenance Computer (CMC) Standard Electronic Configuration Reporting (pdf, 82K)
Goal: The objective is to develop standards for software data loading. This includes development of a high-speed data loader with high-density storage media. Standards for file format, media type, part numbering and terminology will be developed in a way that can be used for various data loading devices.
Scope: This subcommittee prepares documents for the interfaces between the software data loader and the target hardware. It also prepares standard formats for loadable software airplane parts so that all of the requirements of configuration management of LSAPs may be accomplished.
Benefit: The work of this subcommittee allows common tools to be used for the transfer of LSAPs from the airline to the target hardware, whether it is installed onboard the aircraft or on the test bench.
Go to the Manufacturer's
Code Assignment Information
Current Drafts:
Next Meeting Announcement:
Software
Data Loader (SDL) Subcommittee (pdf, 380K)
February 21-24, 2012; in Stuttgart, Germany
Register On Line
Working Papers:
Strawman for ARINC Project Paper 838: Loadable Software Parts Using XML (pdf, 236K)
Last Meeting Report:
Software
Data Loader (SDL) Subcommittee
October 18-21, 2011; in Simi Valley, California
Associated 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 (pdf, 275K) |
| |
Staff: |
Sam Buckwalter |
| 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 |
| List of Assigned Manufacturer's Codes (MMM) |
| |
Staff: |
Scott L. Smith |
| Reference: |
11-145/ABN-038 |
| Effective: |
October 1, 2011 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 |
