ARINC REPORT – Page 6 OMS DESCRIPTION OMS Architecture The OMS should consist of the following equipment:?. Buy ARINC DESIGN GUIDANCE FOR ONBOARD MAINTENANCE SYSTEM from SAI Global. Avionics maintenance practices continue to improve through On-Board Maintenance System (OMS) recording. This standard defines the OMS.
|Published (Last):||18 January 2012|
|PDF File Size:||4.89 Mb|
|ePub File Size:||14.80 Mb|
|Price:||Free* [*Free Regsitration Required]|
Additional BITE tests at power-up should be used in order to meet integrity requirements when continuous monitoring is not practical. The CMC will also initiate automatic aricn within the member system by means of test request message s to the member system.
Faults should not be stored during this phase. Active – System is currently monitoring the fault and believes the fault aribc. Loading of this memory should be accomplished through a standard software loader or through the OMS control panel keyboard.
ARINC – Wikipedia
This technique reduces the amount of data that needs to be transmitted on the bus, and the amount of text that needs to be stored in member systems. If the time cycle information is not available, the member system should transmit a null value, as defined by the following ASN. This should explain any features of the OMS operation or user interaction which may not 6244 obvious to a user. Each airline either uses this data as provided or supplements it to meet its own needs.
Type characteristic defines the characteristic per section 6. Fault tolerance is the built-in capability of a system or LRU to continue to perform its required functions with a specified number of faults. Tags of this class are used by developers of other standards to uniquely identify a type within arinf particular application.
This class is presently not used for OMS communications. They should be tagged with the information that a power interruption has occurred. A typical fault-tolerant system status page should display the actual health status of the system. These events may be due to design errors, software errors, real but unusual events or misunderstanding of system design and operation.
Sufficient protection should be provided to preclude inadvertent alteration of this software.
The need for special ground support equipment should be minimized. For specialized communication applications, such as that required for OMS, the services of the intermediate layers may not be required.
This should be considered in the areas of degree of automation, design for ease of selection of required tests, minimization of aricn ground support equipment, and personnel safety provisions.
Fault detection should be accomplished by continuous operational monitors to the greatest extent aric.
Onboard Maintenance Systems for Modern Aviation
Archived from the original PDF on LSB 7 6 5 4 3 2 1 Number of octets in length Length, as unsigned integer 8 significant bits? The CMC should translate the codes received from the various member systems, consolidate the data, and display clear English messages to the maintenance technician.
Typical candidates for service reports are engine oil quantity, hydraulic quantity, oxygen system, tire pressures, and others. This should arincc used for reporting multiple faults when no additional information is to be attached, as it minimizes bus loading. Specific ground tests, such as LRU replacement verification tests, operational tests, system functional tests, or alignment and rigging.
Encoding for the universal types used in the OMS protocol should be as given in the following sections. A description of one possible architecture for an OMS is also included in the document. These are sometimes essential troubleshooting aides when diagnosing wiring or other unusual problems. Associated with this arjnc quantity is the difficulty in providing accurate and timely information when required.
The LRUs ainc transmitting acknowledgment see attachment 2 section 1. The time interval from selecting Go Around e. If the boolean is xrinc, the transmitting system should set all bits to one. Message identifier names must begin with an uppercase letter. Tags of this class are used with types which need be identified only within a very specific, aeinc context. Some OMS wordstrings e. Failure indication or flight-deck effect, if any Failed function Failed LRU, part number and serial number, or interface A machine user e.
The discussions in this attachment are made for the case dual CMC configuration is applied. Currently two kinds of implementations are identified as follows: A period of time could span the event, or occur totally before or after the event.
Included with this data should be: It also provides for more consistent screen formats from one system to another. Examples of fault history packing to blocks are shown below. This means that it should be possible to adapt a protocol developed for one bus to other buses with little or no change in the upper layers.