Software Data Loader
January 26, 2016
Co-Chairman - Rod Gates, American Airlines
Co-Chairman - Ted Patmore, Delta Air Lines
APIM 10-016B: Software Data loading Clarifications to ARINC 615-3 and ARINC 615-4 (pdf, 164K)
APIM 13-007: Standards for Shop Loading LRUs (pdf, 194K)
APIM 15-003: Supplement 4 to ARINC 665 Loadable Software Parts (pdf, 53K)
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
Draft 4 of Supplement 4 to ARINC Report 665: Loadable Software Standards
Draft 1 of Project Paper 844: Guidance for Target Hardware Design, Part 1, Airborne High Speed Data Loader (ARINC Report 615-3)
Draft 2 of Project Paper 844: Guidance for Target Hardware Design, Part 2, Airborne High Speed Data Loader (ARINC Report 615-4)
Next Meeting Announcement:
Software Data Loader (SDL) Subcommittee (pdf, 308K)
February 24-26, 2016, in Phoenix, Arizona
Register On Line
Strawman for ARINC Project Paper 8XX:: Guidance for Supplying Off-Aircraft Component Software Loading Specification Requirements (pdf, 299K)
XML Support Files:
Last Meeting Report:
Data Loader (SDL) Subcommittee
October 6-9, 2015, in North Reading, Massachusetts
Associated Technical Application Bulletins:
|Cyclic Redundancy Codes (CRC) Test Cases
||Scott L. Smith
||March 15, 2013 - Indefinite
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