Software Data Loader (SDL) Subcommittee

Last Update: July 2, 2009

Chairman - Ted Patmore, Delta Air Lines
APIM: 08-005 XML Software Data Loading (pdf, 36K)
APIM: 08-006 Security of Software Parts (pdf, 30K)

---

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.

---

AEEC General Session (October 2008) Update:

AEEC adopted the following document:

ARINC Specification 826: Software Data Loader Using CAN Interface

Go to the Manufacturer's Code Assignment Information

Current Drafts:

Next Meeting Announcement:

Working Papers:

Last Meeting Report:

Software Data Loader (SDL) Subcommittee
June 17-19, 2009; Portland, Oregon

Associated Technical Application Bulletins:

List of Assigned Manufacturer's Codes (MMM)
	Staff:	Scott L. Smith
	Reference:	09-064/ABN-027
	Effective:	May 6, 2009 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

---

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

---