User's Manual
Table Of Contents
- T3CAS_Section_5
- 5 Adjustment/Test
- 1. General
- 2. Equipment
- 3. Initial Harness Checkout (New Installations Only)
- 4. System Self-Tests
- 5. Return-to-Service Test
- 6. Operational Software Loading Using an ARINC 615A Portable Data Loader or Compact Flash Card
- 7. Downloading Information from the TP3PCAS Using a CF Card
- 1. Obtain a New or Blank Compact Flash (CF) card.
- 2. Copy to the New or Blank CF card the appropriate ‘Header File’
- a) Header files are files copied to the New or Blank CF card that will instruct the computer unit what is desired to be downloaded.
- b) Header files needed to download Maintenance Data, Event Data and CRC Part Numbers can be obtained from ACSS Customer Services at +1-623-445-7070 or crc.acss@l-3com.com.
- 3. For downloading Maintenance Data, Event Data or CRC Part Numbers the aircraft does not need to be in an on-ground configuration.
- 4. Apply power to the computer unit.
- 5. Insert the CF card.
- 6. For ACSS part numbers 9005000-10000, -10101, -10202, and -10204 the DATA STATUS LED will UblinkU green once; this indicates the unit recognized that a CF card was inserted.
- 7. For ACSS part numbers 9005000-11203, -11801 and -55801 the DATA STATUS LED will UblinkU green while reading the header file and performing the action defined in the header file.
- 8. Flight Data Recording
- 1. T3CAS part numbers 9005000-10000, -10101, -10202, and -10204 only support FAT16 CF card formatting. T3CAS part numbers 9005000-11203, -11801 and -55801 support both FAT16 and FAT32 CF card formatting.
- B. Flight Data
- 1. Obtain a New or Blank CF Card.
- 2. Copy to the New or Blank CF Card the Appropriate Header File.
- 3. Header files are files copied to the New or Blank CF card that will instruct the computer unit what is desired to be downloaded.
- 4. For Flight Data Recording, the aircraft does not need to be in an on-ground configuration.
- 5. Apply power to the computer unit.
- 6. Insert the CF card.
- B. Flight Data
- 9. Downloaded Maintenance Data, Event Data And Flight Data May Be Sent To ACSS Customer Services For Analysis
- 5 Adjustment/Test
- T3CAS_Section_6
- T3CAS_Section_7
- 7 Maintenance Practices
- 1. General
- 2. Equipment and Materials
- 3. Procedure for the TP3PCAS Computer Unit
- 4. Procedure for the APM (Not applicable for part numbers 9005000-10000, -10101, -10202, -10204, or -11203)
- 5. Procedure for the Directional Antenna
- 6. Procedure for the Omnidirectional Antenna (Applicable to part numbers 9005000-11203, -11801 and -55801)
- 7. Procedure for the Control Panel
- 8. Procedure for the VSI/TRA Display
- 9. Instructions for Continued Airworthiness, FAR Part 25.1529
- 7 Maintenance Practices
- T3CAS_Section_8
- T3CAS_Section_9
- T3CAS_Section_10
- T3CAS_Appendix_A
SYSTEM DESCRIPTION AND INSTALLATION MANUAL
T
3
CAS/Part No.9005000
A. TAWS/RWS/XPDR/DO-260B Data Configuration
(1) ASDB
The ASDB is a field loadable database that customizes the T
3
CAS operation for
a specific aircraft. The ASDB defines the Input/Output definition for the specific
aircraft type and the aircraft climb performance data to support of the TAWS
functionality. The ASDB file is produced with a unique part number and can be
uploaded to the APM via the RS-232 port or from a Compact Flash card. Part
numbers 9005000-10000, -10101, -10202, -10204, and -11203 do not support
the use of an APM.
NOTE:
It is the responsibility of the installer to ensure that the correct ASDB is
loaded into the T
3
CAS system during aircraft installation. Contact
ACSS to determine the applicable ASDB for a particular installation
configuration (i.e., B737-400 with FMS, GPS, AHRS, etc.)
The ASDB I/O Database contains specific information needed to perform the I/O
functionality for the specific aircraft type. The I/O tables define the following types
of information for processing system inputs and outputs:
● Physical mapping between external systems and T
3
CAS inputs and outputs.
Example, GPS #1 is connected to ARINC 429 Input Bus #5.
● Types of data or information which is processed by the input or generated by
the output. Example: GPS#1 has the following ARINC 429 labels: 100, 101,
etc.
● Input or output timing characteristics such as time-out periods or output
rates. Example: Label 100 must be received every 2 seconds for it to be
valid.
● Data processing characteristics which define specific types of processing
which may be performed on each input or output. This includes an example
of the following types of options:
- Method of storage (single or ping-pong buffer)
- Digital filter option (low-pass filter received data with a specified cut-off
frequency based on parameters in the tables)
- Extrapolation option (extrapolate data at a given interval based on
previous samples received)
- Sequence number option (example, process 310 Latitude and 311
Longitude as a pair)
- Push-button option (look for a transition from 0 to 1 in the data)
● Conversion code and parameters which specify how to process the data.
Examples:
- Decode Label 310 as a BNR (binary) number with a MSB of 90
degrees.
- Multiply analog radio altitude voltage by a parameter (scale factor) to
get feet.
4-94
04 Nov 2014
34-45-29
Pub. No. 8600200-001, Revision 004
Use or disclosure of information on this page is subject to the restrictions in the proprietary notice of this document.