(b)
The types of software installed in a component on one airplane can be different than the types of software installed in the component on a different airplane. 1) A component on the list can have some hardware part numbers
that are approved for software installation and other hardware part numbers that are not approved for software installation. An example of this is the flight data acquisition unit.
2) Refer to airline part number records to find software part numbers for applicable components.
(c)
Data transfer times are approximate times in minutes for software installed from disks with a data loader. Data transfers can fail, and failure of the data transfer will increase the total time necessary for software installation. Data transfer times are supplied only as an aid to help you schedule work.
(d)
The times given are for the installation of one piece of software into one component. 1) If a component has more than one piece of software, then
you must add the time for each piece to find the total data transfer time for the component.
2) If a system has more than one of a given component, and software is to be installed in each one, you must multiply the time given in the table by the total number of components to find the total data transfer time for the system. a) For example, if a left and a right component are
installed on the airplane, you must multiply the time given in the table by two to find the total data transfer time for the two components.
EFFECTIVITYùùùùùùùùùùùùùùùùùùùùùùùùùùùùùù. ú
20-15-11
ALL ú ú 01 Page 202 ú Mar 12/00
BOEING PROPRIETARY - Copyright (C) - Unpublished Work - See title page for details.
A
737-300/400/500MAINTENANCE MANUAL
b) Some systems can cross-load software between components. Usually it is faster to cross-load software than to install software with a data loader. The Flight Management Computer System (FMCS)is an example of a system that can cross-load.
EFFECTIVITYùùùùùùùùùùùùùùùùùùùùùùùùùùùùùù. ú
20-15-11
ALL ú ú 01 Page 203 ú Mar 12/00
BOEING PROPRIETARY - Copyright (C) - Unpublished Work - See title page for details.
A
737-300/400/500MAINTENANCE MANUAL
~.............................................................................. | Table 201 | ................................................................................
| | | | Data |
| AMM | | | Transfer |
|Chapter| | | Time (in |
|Section| Component | Software | Minutes) |
................................................................................ |23-27 |ACARS Management Unit (MU) |OPS | 2 to 16 | | |(some units) |DB | 1 to 15 | ................................................................................ |23-27 |ACARS Multi-Purpose Display Unit |OPS *[1] | 3 to 6 | | |(MIDU) (Allied Signal) | | | ................................................................................ |23-37 |Digital Interface Unit |Airshow DB | 3 to 15 | | |(Passenger Flight Information | | | | |Display System) | | | ................................................................................ |31-24 |Flight Data Acquisition Unit |DFDAU Mandatory (OPS) | 5 to 32 | | |(FDAU) (some units) | *[2] | | | | |ACMS Monitoring (OPS) | 3 to 20 | | | | *[2] | | ................................................................................ |31-24 |Optical Quick Access Recorder | OPS *[3] | 30 | | |(QAR) (Teledyne) | | | ................................................................................ |34-22 |EFIS Symbol Generator |OPS | 5 to 16 | | |(-402 and subsequent) | | | ................................................................................ |34-61 |Flight Management Computer (FMC) |OPS | 10 to 30 | | | |OPC | 1 to 3 | | | |NAV DB | 3 to 45 | | | |ACARS Datalink *[4] | 3 to 15 | | | |Perf Defaults *[4] | 3 to 15 | | | |QRH Takeoff Speeds *[4] | 3 to 15 |
EFFECTIVITYùùùùùùùùùùùùùùùùùùùùùùùùùùùùùù. ú
20-15-11
ALL ú ú 01 Page 204 ú Mar 12/00
中國航空網 www.k6050.com
航空翻譯 www.aviation.cn
本文鏈接地址：737-300 400 500 AMM 飛機維護手冊 STANDARD PRACTICES(86)
