TRD- V1.2-ADR.pdf

Airborne Data Recorder Technical Requirements Document

(TRD)

Version Date: 11 June 2010

Document Identifier: Airborne Data Recorder V1.2 TRD.doc

Version: 1.2

Prepared By:

846 TSS/TSI

Eglin, AFB, FL 32542

850-882-2537 berard@eglin.af.mil

Airborne Data Recorder TRD V1.2

Contents

1.0 Introduction

1.1 Purpose

1.2 Scope

1.3 References

1.3.1 Key Acronyms

1.3.2 Key Documents

2.0 Descriptions

2.1 ADR Terms and Definitions

2.2 ADR Hardware Configurations

2.3 ADR Software

3.0 ADR Standardization Requirements

3.1 Recorder Firmware Configuration

3.2 Operational Requirements

3.3 Data Types and Packetization

4.0 ADR Input/Output Requirements

4.1 Time Input

4.2 Time Output

4.3 PCM Input

4.4 Mil-Std-1553 Input

4.5 16PP194 Input

4.6 Video/Audio Input

4.7 Ethernet Input

4.8 Analog Audio Input

5.0 ADR Operational Requirements

5.1 Operational Modes

5.2 Discrete Command and Control

5.3 Data Security

5.4 ADR Configuration

5.5 Input Recording

5.6 Internal or External RMM

5.7 Internal RMM

5.8 External Remote RMM

5.9 Time Sources and Synchronization

5.10 ADR Event Packet Types

5.11 CH10 Publish

5.12 MIL-STD-1553 Data Filtering

5.13 MIL-STD-1553 Record Control

5.14 DVR Firmware Transfer File

6.0 ADR Serial Interface Requirements

6.2 ADR threshold IRIG-106-09 Chapter 6 serial command requirements

7.0 ADR Life Cycle

8.0Physical Characteristics

9.0Electromagnetic Interference and Compatibility

10.0Aircraft Power Interface

11.0Design and Construction

Revision Record

REVISION

DATE

REVISION

NUMBER

BRIEF SUMMARY OF CHANGES

05/06/09 1.0 Initial Release TRD.

06/11/10 1.2 1.3.2 Removed IADS Reference

2.2 -b Corrected PCM Requirement

2.2 -d Removed Remote Media Requirement. Corrected continuous data rate requirement

3.2.5 No Computer Generated data, format 0, user defined

packets are allowed as specified by section 3.3.2 of this TRD.

3.2.9 Corrected block size to 512 Bytes

3.3-c Added Video Data, Format 0, MPEG-2/H.264 Video

4.1 Removed requirement for IRIG A

4.3 Corrected minimum PCM bit rate to 100 Kbs. Added RS-422

termination requirement

4.6.14 Removed Requirement

5.1 Added statement that NO batteries are allowed

5.2 Added req for additional input discretes (EVENT)

5.2.8 Removed figure

5.3 Clarified DECLASSIFY command

5.4 Clarified requirement for ADR configuration source

5.5 Added RMM record capacity requirement. removed unpacked

requirement.

5.6 Added RMM record capacity requirement

5.8 Clarified minimum and maximum separation of RMM

5.9 Removed MIL-STD-1553 Synchronization requirement

6.0 Corrected Serial .IRIG106 command syntax

10.1 Added max current requirement, any configuration

1.0 Introduction

1.1 Purpose

The purpose of this Technical Requirements Document (TRD) is to provide the functional and technical specifications for an IRIG106-07 or later compliant Airborne Data Recorder (ADR). This system will be utilized by the 46th Test Wing (TW), Air Armament Center (AAC), Eglin AFB in support of Department of Defense (DoD) developmental and operational flight test requirements related to a variety of weapon systems.

1.2 Scope

This TRD establishes requirements for performance, development, and test an ADR. The terms “threshold” and “objective” are in bold type, followed immediately by the stated requirement. Threshold requirements are the minimum required to be provided.

Objective requirements are defined as the ultimate goal, and depend on technology advancements. Additional information (sometimes stated in directive terms) is considered amplifying data.

The term “Shall” is used to dictate the provision of a functional capability; to denote something that is required.

The term “Will” is used as a statement of fact; to cite items that the operational environment is to provide to the capability being specified.

1.3 References

This section contains a list of reference material used by this TRD.

1.3.1 Key Acronyms

The following acronyms and definitions are used within this document.

BIT Built In Test CSV Comma Separated Value DTF Data Transfer File GUI Graphical User Interface IAW In Accordance With ICD Interface Control Document IRIG Inter-Range Instrumentation Group LED Light Emitting Diodes ORF Original Recording File PCM Pulse Code Modulation PPM Parts Per Million RCC Range Commanders Council RCF Recorder Configuration File RMM Removable Memory Module RTC Relative Time Counter SCSI Small Computer Systems Interface TG Telemetry Group TRD Technical Requirements Document TMATS Telemetry Attributes Transfer Standard XML eXtensible Markup Language

1.3.2 Key Documents

The documents listed in this section, hereunder, form a part of this specification to the extent invoked by specific reference in other paragraphs of this specification. In the event of conflict between the documents referenced below and the contents of this specification, the content of this specification shall be considered a superseding requirement.

RCC IRIG 106-07, -09

Telemetry Standards

Chapter 4 PCM Standard

Chapter 6 Digital Cassette Helical Scan Recorder/Reproducer, Multiplexer/Demultiplexer, Tape Cassette, and Recorder Control and Command Mnemonics Standards

Chapter 8 Digital Data Bus Acquisition Formatting Standard

Chapter 9 Telemetry Attributes Transfer Standard

Chapter 10 Digital Recording Standard

DoD Standards

MIL-E-5400

14 May 90

General Specification for Airborne Electronic Equipment

AFSSI 5020

20 Aug 96

Air Force System Security Instruction

MIL-STD-130

Rev. M, 2 Dec 05

DOD Standard Practice, Identification Marking of U.S. Military Property

MIL-STD-461

Rev E 20 Aug 99

Requirements for the Control of Electromagnetic Interference Characteristics of Subsystems and Equipment

MIL-STD-704

Rev A, Notice 1 11 Apr 73

Characteristics and Utilization of Electric Power

MIL-STD-810

Rev F, 01 Jan 00

Environmental Test Methods

MIL-STD-1472

Rev B, Notice 2, & Notice 1, 10 May 78

Human Engineering Design Criteria for Military Systems, Equipment and Facilities

MIL-STD-1553

Rev B, Notice 1

12 Feb 80

Aircraft Internal Time Division

Command/Response Multiplex Data Bus

IEEE Standards

1394B-2002 High Performance Serial Bus – Amendment 2

802.3-2005 LAN/MAN CSMA/CD Access Method

EIA Standards

RS-232C Serial Interface

RS-170

Rev A

National Television Standards Committee (NTSC)

ICD’s

March 7 2007 IADS Interface Document

2.0 Descriptions

2.1 ADR Terms and Definitions

The following are ADR terms and definitions which will be used throughout this TRD that are not defined by the IRIG106 Chapter 10 standard section 10.2:

1. “IRIG106”: refers to the IRIG106-07 or later released standard followed by the applicable chapter reference. A specific release version of IRIG106 will be used where that versions contain the specified functionality required.

2. “Mbps”: Mega-bits per second.

3. “MBps”: Mega-Bytes per second.

4. “Record” or “Recording”: record an ORF from recorder inputs.

5. “CH10 Publish or “CH10 Publishing”: Ethernet data broadcast which complies with IRIG106 Chapter 10 section 10.3.11.

2.2 ADR Hardware Configurations

1. Four (4) separate hardware configurations will be specified in this document.

The requirements for will follow in later sections. Below are the overall descriptions for each configuration:

a. Configuration #1 (300 Mbps Continuous Sustained Data Rate). The ADR shall be less than or equal to 7.5 inches wide, 10 inches long, and 4.5 inches tall, exclusive of connectors, control knobs, eject mechanism, and memory access door.

Data Type Number of Channels

Data Rate Mega-Bits Per Second

(Mbps)

Bit Sync

RS-422

Input

TTL

Input

Video

Overlay Audio

IRIG Time 1

PCM 8 160 X X X

MIL-STD-1553 8 6.4

Video 8 32 X 2

Ethernet 1 10-100

Remote Media 1

b. Configuration #2 (160 Mbps Continuous Sustained Data Rate). The ADR shall be less than 6 inches wide, 8.5 inches long, and 4.5 inches tall, exclusive of connectors, control knobs, eject mechanism, and memory access door.

of Channels

Data Rate Mega-Bits Per Second

(Mbps)

Bit Sync

RS-422

Input

TTL

Input

Video

Overlay Audio

IRIG Time 1

PCM 2 40 X X

MIL-STD-1553 8 6.4

Video 3 32 X 2

16 PP164 1 1

c. Configuration #3 (700 Mbps Continuous Sustained Data Rate). The ADR shall be less than or equal to 4.5 inches wide, 6 inches long, and 3.5 inches tall, exclusive of connectors, control knobs, eject mechanism, and memory access door.

of Channels

Data Rate Mega-Bits Per Second

(Mbps)

Bit Sync

RS-422

Input

TTL

Input

Video

Overlay Audio

IRIG Time 1

Video 2 8 X 2

Ethernet 2 10-1000

d. Configuration #4 (120 Mbps Continuous Sustained Data Rate). The ADR shall be less than 6 inches wide, 6.5 inches long, and 5 inches tall, exclusive of connectors, control knobs, eject mechanism, and memory access door.

of Channels

Data Rate Mega-Bits Per Second

(Mbps)

Bit Sync

RS-422

Input

TTL

Input

Video Overlay

Audio

IRIG Time 1

MIL-STD-1553 4 3.2

Video 4 16 X 2

2.3 ADR Software

1. The ADR will be provided with setup record generation software application.

The software application will be Microsoft Windows based and provide documentation of any TMATS V-Spec or “V” group attributes generated by the software application.

3.0 ADR Standardization Requirements

3.1 Recorder Firmware Configuration

1. As a threshold the ADR shall have only one (1) firmware configuration which shall be IRIG106 Chapter 10. It is not permissible for the firmware to be provided within the ADR that allows the recorder to be configured or operate in a mode other than IRIG106 Chapter 10.

2. As a threshold the ADR shall have software utility provided to configure, upload and/or communicate with the ADR to only have commands or features related to the IRIG106 Chapter 10 standard.

a. As an objective the ADR shall allow firmware updates from the RMM as denoted by this TRD

3.2 Operational Requirements

1. As a threshold ADR hardware configuration shall have a modular architecture and shall be provided with software configurable electronics. System configurations are defined in section 2.2 of this document.

2. As a threshold the ADR shall meet the compliancy requirements IAW IRIG106 Chapter 10 section 10.3.1.1.

3. As a threshold the ADR shall provide recorder configuration IAW IRIG106 Chapter 10 section 10.3.2.

4. As a threshold the ADR shall provide an IEEE-1394B download port interface IAW IRIG106 Chapter 10 section 10.4.2.

a. As an objective the ADR shall provide an Ethernet download port interface IAW IRIG106 Chapter 10 section 10.4.3.

5. As a threshold any processing performed on the stored data by the ADR (e.g., for the purposes of internal system management, error detection and correction (EDAC), physical frame formatting, etc.) shall NOT be part of the data file or stored in any part of the storage media. No Computer Generated data, format 0, user defined packets are allowed as specified by section 3.3.2 of this TRD.

6. As a threshold the ADR shall provide an internal RMM. The RMM interface shall be IAW IRIG106 Chapter 10 section 10.9. The directory and files structures presented at the interface shall be IAW IRIG106 Chapter 10 section 10.5. It is NOT acceptable for the RMM to mount as a Windows volume or for the RMM firmware to allow for reconfiguration as a Windows volume.

7. As a threshold the ADR RMM shall operate from a 12 VDC, 1 Amp IEEE- 1394B 9 pin bilingual connector interface. It is NOT acceptable to augment power with use of multiple IEEE-1394B ports or a separate power port.

8. As a threshold the ADR shall provide RMM recorded data access the same IEEE-1394B 9 pin bilingual connector interface in section 3.2.6 of this document. It is NOT acceptable for any other RMM interface/data access port to be provided (USB, eSATA, Ethernet, etc).

9. As a threshold the ADR shall provide a recorded data block size of 512K bytes.

The 512K block sized shall be IAW IRIG106 Chapter 10 section 10.5, table 10.2 “Block Size” directory.

10. As a threshold Logical Address 0 or media block 0 as presented at the RMM interface shall be IAW IRIG106 Chapter 10 section 10.5.2 and shall be filled with 0xFF.

11. As a threshold the ADR shall provide file table entries IAW IRIG106 Chapter 10 section 10.3.7.

12. As a threshold the ADR shall be configured from a RCF IAW IRIG106-09 Chapter 9. Any and all TMATS V-Spec or “V” group attributes contained in an ADR TMATS RCF shall be defined in this document or an ICD provided with the ADR.

13. As a threshold the ADR shall provide Data Streaming Transport IAW IRIG106 Chapter 10 section 10.3.11.

3.3 Data Types and Packetization

1. As a threshold the ADR per the configurations defined in section 2.2 of this document shall record the following data types and shall be encapsulated IAW IRIG106 Chapter 10 section 10.6:

a. Configuration 1:

i. Computer Generated Data, Format 1, Setup Record

ii. Computer Generated Data, Format 2, Recording Events

iii. Computer Generated Data, Format 3, Recording Indexes

iv. Time Data, Format 1, IRIG/GPS/RTC

v. PCM Data, Format 1, IRIG106 Chapter 4/8

vi. MIL-STD-1553, Format 1, Mil-Std-1553B Data

vii. Video Data, Format 0, MPEG-2/H.264 Video

viii. Ethernet Data, Format 0, Ethernet Data

b. Configuration 2:

i. Computer Generated Data, Format 1, Setup Record

ii. Computer Generated Data, Format 2, Recording Events

iii. Computer Generated Data, Format 3, Recording Indexes

iv. Time Data, Format 1, IRIG/GPS/RTC

v. PCM Data, Format 1, IRIG106 Chapter 4/8

vi. MIL-STD-1553, Format 1, Mil-Std-1553B Data

vii. MIL-STD-1553, Format 1, 16PP194 Bus

viii. Video Data, Format 0, MPEG-2/H.264 Video

ix. Ethernet Data, Format 0, Ethernet Data

c. Configuration 3

ii. Computer Generated Data, Format 2, Recording Events

iii. Computer Generated Data, Format 3, Recording Indexes

iv. Video Data, Format 0, MPEG-2/H.264 Video

v. Time Data, Format 1, IRIG/GPS/RTC

vi. Ethernet Data, Format 0, Ethernet Data

d. Configuration 4

ii. Computer Generated Data, Format 2, Recording Events

iii. Computer Generated Data, Format 3, Recording Indexes

iv. Time Data, Format 1, IRIG/GPS/RTC

v. MIL-STD-1553, Format 1, Mil-Std-1553B Data

vi. Video Data, Format 0, MPEG-2/H.264 Video

vii. Ethernet Data, Format 0, Ethernet Data

2. As a threshold ADR recorded data shall NOT contain Computer Generated Data, Format 0, User Defined packets.

3. As a threshold ADR packet trailers shall NOT contain filler except to complete byte alignment within a packet. Filler shall not exceed four 8 bit bytes.

4. As a threshold ADR Computer Generated Data, Format 3, Recording Indexes shall use time indexing and contain an index entry for each Time Data, Format 1, IRIG/GPS/RTC packet. No other index entry shall be provided for any other data type except for Computer Generated Data, Format 2, Recording Events.

4.0 ADR Input/Output Requirements

4.1 Time Input

1. As a threshold the ADR shall provide one (1) time input channel. Time input shall be concurrent with each PCM input channels.

2. As a threshold the ADR shall synchronize to an external AC modulated IRIG-B or -G input IAW IRIG200-04.

a. As an objective requirement the ADR shall accept an external 1 PPS input.

b. As an objective the ADR shall synchronize to a GPS UTC time source.

The source shall be a GRS internal GPS receiver.

3. As a threshold the ADR shall support the following signal characteristics for time channel input:

Input Signal Amplitude Modulated IRIG-A, -B, or -G

IAW IRIG200-04

Input Levels 0.2 to 10Vpp

Input Termination / Coupling 620Ω / AC (Capacitor)

Input Over Voltage Protection ±11V

Input Synchronization Accuracy IRIG-B < 10 Microseconds

IRIG-G < 1 Microsecond

Table 4.1 – Time Input Signal Requirements

4.2 Time Output

1. As an objective the ADR shall provide one (1) IRIG-B AC modulated time output. NOTE: 3:1 modulation ratio and 3 Vpp into a 75 ohm load capability.

2. As an objective the ADR shall support the following signal characteristics for the time channel output:

Output Signal Amplitude Modulated IRIG B IAW

IRIG200-04

Output Levels 0.5 to 10Vpp

Output Termination / Coupling 620Ω / AC (Capacitor)

Output Over Voltage Protection ±15V

Output Synchronization Accuracy IRIG-B <1 ms

Stability and Drift of the Internal Time Code with No Signal

Stability: +10 ppm

Drift: + 5 ppm per year

Table 4.2.1 – Time Output Signal Requirements

3. As an objective the ADR shall output time data to the accuracy of the IRIG time format.

4.3 PCM Input

1. As a threshold the ADR shall provide PCM input channels IAW with configurations as defined in section 2.2 of this document. Each PCM channel shall have a minimum sustained PCM data rate of one hundred kilo bits per second (100 Kbps) and a maximum sustained PCM data rate of twenty million bits per second (20 Mbps). The PCM inputs shall be concurrent with the Time input channel.

2. As a threshold the ADR shall provide NRZ-L and RNRZ-L 15 forward and reverse input for each channel IAW IRIG106 Chapter 4.

a. As an objective the ADR shall provide a bit synchronizer input to each channel.

3. As a threshold the ADR shall provide differential RS-422 and single ended TTL for each PCM input channel.

4. As a threshold the ADR shall provide selection of differential RS-422 or single ended TTL for each PCM input channel. A 120 ohm termination shall be provided for RS-422 inputs.

4.4 Mil-Std-1553 Input

1. As a threshold the ADR shall provide MIL-STD-1553 input channels IAW with configurations as defined in section 2.2 of this document.

2. As a threshold the ADR shall provide internal isolation transformers to allow for transformer coupled aircraft bus interface, 18-27 Vpp for RT and 0.86-27 Vpp.

4.5 16PP194 Input

1. As a threshold the ADR shall provide 16PP194 input channels IAW with configurations as defined in section 2.2 of this document.

2. As a threshold the ADR shall provide internal isolation transformers to allow for transformer coupled aircraft bus interface, 18-27 Vpp for RT and 0.86-27 Vpp.

4.6 Video/Audio Input

1. As a threshold the ADR shall provide video/audio input channels IAW with configurations as defined in section 2.2 of this document.

2. As a threshold the ADR shall provide be compatible with Electronic Industries Alliance (EIA) RS-170 monochrome, National Television Standards Committee (NTSC) composite and S-Video signals.

3. As a threshold the ADR video input channel characteristics shall be IAW table 4.6.1:

RS-170

1.0 Vp-p Nominal (+3.0 dB max (1.4 Vp-p max)

-6.0 dB min (0.5 Vp-p min), 75 ohm, Negative sync

S-Video Luminance

1.0 Vp-p (Y) Nominal (+3.0 dB max (1.4 Vp-p max)

-6.0 dB min (0.5 V p-p min)

S-Video Chrominance

0.3 Vp-p Nominal (+3.0 dB max (0.43 Vp-p max)

-6.0 dB min (0.15 Vp-p min), 75 ohm (Color Burst)

NTSC

1.0 Vp-p Nominal (+3.0 dB max (1.4 Vp-p max)

-6.0 dB min (0.5 Vp-p min), 75 ohm, Negative sync)

Table 4.6.1 – Video Input Signal Requirements

4. As a threshold video pixel resolution shall be a minimum of 640 x 480.

5. As a threshold video compression shall not result in loss of video quality.

6. As a threshold video quality shall be equivalent or better than that recorded on existing 8mm tape recording systems.

7. As a threshold video shall be compressed IAW MPEG-2 Main Profile at Main Level (MP@ML).

8. As an objective the ADR system time shall be overlaid on the recorded data for each video channel formatted as DDD HH:MM:SS.TTT where DDD is the Julian day of the year from 1 to 366, HH is the hour in the day from 0 to 23, MM is the minute in the hour from 0 to 59, SS is the second in the minute from 0 to 59, and TTT is the millisecond in the second from 0 to 999.

9. As an objective character overlay selection shall be provided as black on transparent background, white on transparent background, black on white, and white on black.

10. As an objective the horizontal (X) and vertical (Y) location of the overlaid time on the recorded video frames shall be separately configurable for each video channel.

11. As an objective the normal character color (white) and the normal background color (black) shall reverse to black characters on white background for one second and then return to the normal white characters on a black background when any event (discrete or MIL-STD- 1553) has been generated.

12. As an objective the DDD and TTT characters shall be optionally removed allowing more viewing area.

13. As an objective the character size shall be no greater than 12 pixels wide (horizontal) by 17 lines high (vertical). No more than two pixels should be allotted on either side denoting background edge.

14. As an objective video that is played back shall contain the same overlay time as that made in the recording.

15. As an objective video overlay shall be configured using IRIG106-09 Chapter 9 Video Data Type Attributes in the RCF:

Table 4.6.2 – Video Overlay TMATS Attributes

16. As an objective overlay time accuracy shall be coincident with ADR system time.

17. As a threshold each video channel shall provide for a single analog audio input IAW IRIG106 Chapter 10 section 10.6.5.2.

18. As an objective the analog audio channel shall be mapped to any video channel regardless if video channel has been enabled. The channel mapping ID shall be the same as the channel ID and mapping of audio-video channels shall be configured using IRIG106-09 Chapter 9 Video Data Type Attributes in the RCF.

Table 4.6.3 – Analog Audio Channel Mapping TMATS Attributes

19. As a threshold the analog audio input interface is defined in section 4.8 of this document.

20. As a threshold audio input characteristics (Table 4) shall be compatible with the aircraft intercom system. The input impedance of the audio input shall be 10K ohms.

4.7 Ethernet Input

1. As an objective the ADR shall provide 1000baseT Ethernet interface for

IRIG106 Chapter10 Publishing.

4.8 Analog Audio Input

1. As an objective the ADR shall provide two independent audio input channels. The ADR shall allow each audio input channel to be independently mapped to any input video channel as a separate audio stream within the MPEG-2 stream.

2. As a threshold ADR analog audio inputs shall generate their own analog packets IAW IRIG106 Chapter 10 section 10.6.5.

3. As a threshold ADR analog audio inputs shall be as follows:

Sign Signal Type Analog, Balanced Differential

Volt Voltage Level 1.0 Vp-p (0 Min - 10 Vp-p Max)

Maximum Voltage 10 Vpp

Freq Frequency Response 300 Hz to 6 KHz

Sign Signal to Noise Ratio Greater than 40 dB

5.0 ADR Operational Requirements

5.1 Operational Modes

1. As a threshold the ADR shall be in OFF-mode when no power is applied. The ADR shall be in ON-mode after application of power.

2. As a threshold the ADR shall provide the ability to start and stop recording in the ON mode. If recorder power is removed while in the ON mode, the recorder shall initiate a soft power down. No loss of data shall be encountered on a soft power down to include meeting IRIG106 Chapter 10 time packet interval requirements and Recording Index packet requirements. As a threshold no batteries are permitted.

3. As a threshold the ADR shall withstand a 50 millisecond power interruption period without loss of function or data.

4. As a threshold the ADR BIT shall consist of ADR start-up BIT, periodic, and initiated BIT. BIT shall detect 90 percent of all failures or out-of-tolerance conditions and isolate 90 percent of all detected failures to the ADR. False BIT detection or reporting shall be less than one in 1500 flight hours. BIT shall not be affected by normal system transients, power turn-off or turn-on, and shall not indicate a BIT failure for transient out-of-tolerance conditions. BIT results shall be reported via MIL-STD-1553 data bus. The ADR shall provide an indication of BIT status on the ADR. The indicator shall be a light emitting diode or other solid state device.

5. As a threshold a Start-up BIT shall automatically execute upon application of power to the ADR. Normal operation of the ADR is not required during start-up BIT. Start-up BIT execution time shall not exceed 30 seconds. The ADR shall initiate start-up BIT upon insertion of the RMM if power is present.

a. As a threshold a Periodic BIT shall periodically execute during operation of the ADR. The ADR shall be fully functional during execution of periodic BIT.

b. As a threshold Initiated BIT shall execute upon command via MIL- STD-1553 message. Normal operation of the ADR during initiated BIT is not required. Initiated BIT shall provide fault detection and fault isolation capability equivalent to that of start-up BIT and periodic BIT to the maximum extent possible.

6. As a threshold the ADR shall be fully operational after 60 seconds upon power application to include BIT.

7. As a threshold the ADR warm-up time at temperatures down to -40°C shall not exceed 5 minutes.

8. As an objective the ADR shall provide two LED’s; a Fault Indicator LED and a Record Indicator LED. These LED indicators shall meet MIL-STD-3009 requirements for night vision compatible lighting.

a. As an objective the ADR to be configurable allowing for indicator lights to flash at 0.5Hz rate during unit initialization.

5.2 Discrete Command and Control

1. As a threshold the ADR provide discrete input and outputs IAW IRIG106

Chapter 10 section 10.7. Discrete inputs/outputs other than those specified in IRIG-106 Chapter 10 will be defined by this TRD. The following table is a list of the required discrete inputs and outputs:

Name User Function

Event Input Activated by a momentary switch:

0.55 Volts or less for minimum duration of 10 milliseconds.

Enable Input Activated by a momentary switch:

0.55 Volts or less for minimum duration of 100 milliseconds.

Record Input

Activated by toggle switch:

Normally closed position 0.55 Volts or less. This discrete shall command the ADR to start recording. The ADR shall remain in this mode until such time as the switch is set to normally open position. This shall provide same functionality as the .RECORD command.

Erase Input

Activated by momentary switch:

0.55 Volts or less, minimum duration of 100 milliseconds.

This discrete shall command the ADR to erase recorded data and directory memory provided the enable switch is also activated. This shall provide same functionality as the .ERASE command.

Record Output A Record indication (ON) shall be active low 0.55 volts or less. A Non-Record indication (OFF) shall be an open circuit.

Current limit of 60 milliamps required.

Fault Output A Fault indication (ON) shall be 0.55 volts or less. A Non- Fault indication (OFF) shall be an open circuit. Current limit of 60 milliamps required.

Erase Output An Erase indication (ON) shall be 0.55 volts or less. A Non- Erase indication (OFF) shall be an open circuit. Current limit of 60 milliamps required.

2. As a threshold a Recording Event packet IAW IRIG106 Chapter 10 section

10.6.7.3 shall be generated from a valid discrete input.

a. As a threshold the first event (event 0) shall be reserved for the external recorder discrete as defined in the ADR configuration setup record IAW IRIG106-09 Chapter 9 “Recording Event Definition” attributes and “Recording Event” attributes. The external ADR discrete event name and description shall be user defined.

b. As a threshold the event driven by an external ADR discrete shall be compliant with Computer Generated Data Packets, Format 1 Setup Records packet and shall have the Event Type (R-x\EV\T-n) set to External - ‘E’.

c. As a threshold the second event (event 1) + N shall be defined in the Recorder configuration setup record IAW IRIG106-09 Chapter 9.

“Recording Event Definition” attributes and “Recording Event” attributes shall be reserved for MIL-STD-1553 .EVENT commands as described in this TRD.

3. As a threshold the “Record” input discrete shall overwritten by a .STOP command.

4. As a threshold the ADR RMM directory shall be erased within 1 second of “Erase” input discrete.

5. As a threshold the ADR shall start recording within 1 second of “Record” input discrete.

6. As a threshold the Fault indicator LED shall flash at a 0.5 second rate during ADR initialization.

7. As a threshold the ADR Record indicator LED shall at a 0.5 second rate during recorder initialization.

8. As a threshold the ADR discrete output (Fault, Erase, Record) shall provide a path to ground when active true.

Figure Removed

9. As a threshold ADR record output indicator state conditions; fault shall be indicated for the following conditions:

Recorder Status LED Indicator State

Recorder Initialization Flash at 0.5 Hz

Fault Indicator ON Record indication (OFF), open circuit.

Record and No Fault Record indication (ON), 0.55 volts or less

10. As a threshold ADR fault output indicator state conditions; fault shall be indicated for the following conditions:

Recorder Status LED Indicator State

Recorder Initialization Flash at 0.5 Hz

Media not installed Fault indication (ON), 0.55 volts or less

Media Full Fault indication (ON), 0.55 volts or less

Media Not Recognized Fault indication (ON), 0.55 volts or less

Not able to Record Fault indication (ON), 0.55 volts or less

No Media Errors and recorder able to record data

Fault indication (OFF), open circuit.

11. As a threshold ADR erase output indicator state conditions; erase shall be indicated for the following conditions:

Recorder Status Indicator State

Recorder Initialization Flash at 0.5 Hz

Media Is Erased Erase indication (ON), 0.55 volts or less

Media is in Record Erase indication (OFF), open circuit.

Media has one or more files Erase indication (OFF), open circuit

Media Initializes and has no files

Erase indication (ON), 0.55 volts or less

5.3 Data Security

1. As a threshold the ADR shall store all classified data on the RMM, such that the ADR is not classified when the RMM is removed. For security purposes, there shall be no nonvolatile memory resident in the ADR that can be written to by the ADR processor(s). Read-only or write-protected memory for program storage is acceptable, however ADR software or firmware associated with data file formatting must be able to be installed/changed at field level by DoD personnel.

2. As a threshold the ADR shall erase the RMM IAW IRIG106 Chapter 10 section

10.8 and section 10.9.

3. As a threshold the RMM shall be erased within 1 second of the .ERASE command allowing for new files to be generated.

4. As a threshold a .DECLASSIFY command shall cause the recorder to issue a .SANITIZE command to the RMM IAW IRIG106-09 Chapter 10 section 10.9.12.3.

5. As a threshold the ADR manufacturer shall provide an RMM with known bad memory blocks to allow for validation of sanitization command. Documentation must be provided for memory type and manufacturer specification. A threshold requirement is for the ADR RMM to support the mandatory RMM commands IAW IRIG-106-09 Chapter 10 section 10.9.7 and section 10.12.

6. As a threshold once the declassification process has been initiated and a loss of power has occurred, the ADR and/or RMM shall continue the sanitization.

7. As an objective the setup record shall be appended with (G:\COM) recorder serial number, firmware version of ADR, firmware version of RMM.

5.4 ADR Configuration

1. As a threshold the ADR shall be configured with an IRIG106-09 Chapter 9 TMATS RCF from either the recorder serial commands (.SETUP & .TMATS) or from the ADR RMM.

2. As a threshold the ADR setup source shall be configured IAW IRIG106-09 TMATS attributes

5.5 Input Recording

1. As a threshold the ADR shall provide Recording to a ORF on one (1) or more RMM’s containing the following IRIG106-09 Chapter 10 data types and channel counts as defined in section 2.2.1a-d of this document:

a. Configuration #1 (300 Mbps Continuous Sustained Data Rate) maximum RMM volume of 64Gbytes:

i. Computer Generated Data Packets Format 1, Setup Records.

Setup record format shall be ASCII.

ii. One (1) channel of Time Data Packets, Format 1 (IRIG/GPS/RTC) from the time input as defined in section 4.1 of this document. Time format shall be IRIG-B or IRIG-G.

iii. Eight (8) channels of PCM Data Packets Format 1 (IRIG 106 Chapter 4 and 8) in packed, unpacked or throughput mode from any selected or all PCM inputs as defined in section 4.2 of this document. It is permissible to provide either 16 bit or 32 bit alignment IAW IRIG-106 Chapter 10.

iv. Eight (8) channels of MIL-STD-1553 Bus Data Packets, Format 1 (MIL-STD-1553B Bus Data) from any selected or all MIL- STD-1553 inputs as defined in section 4.4 of this document.

v. Eight (8) channels of Video Packets, Format 0 (MPEG-2/H.264) from any selected or all NTSC inputs as defined in section 4.X of this document. Payload type shall be MPEG-2 MP@ML.

vi. One (1) channel of Ethernet Data Packets, Format 0 from the Ethernet input as defined in section 4.X of this document.

vii. If enabled in the setup record Computer Generated Data Packets Format 2, Recording Event. At a minimum an index shall be created for each time packet and event packet. The Recording index type shall be time. The index time value shall be the time packet source type interval (IRIG-B or IRIG-G).

viii. If enabled in the setup record Computer Generated Data Packets Format 3, Recording Index. The supported event packet types shall be as defined in section 5 of this document.

b. Configuration #2 (160 Mbps Continuous Sustained Data Rate) maximum RMM volume of 64Gbytes:

i. Computer Generated Data Packets Format 1, Setup Records.

Setup record format shall be ASCII.

ii. One (1) channel of Time Data Packets, Format 1 (IRIG/GPS/RTC) from the time input as defined in section 4.1 of this document. Time format shall be IRIG-B or IRIG-G.

iii. Two (2) channels of PCM Data Packets Format 1 (IRIG 106 Chapter 4 and 8) in packed, unpacked or throughput mode from any selected or all PCM inputs as defined in section 4.2 of this document.

iv. Eight (8) channels of MIL-STD-1553 Bus Data Packets, Format 1 (MIL-STD-1553B Bus Data) from any selected or all MIL- STD-1553 inputs as defined in section 4.4 of this document.

v. One (1) channel of MIL-STD-1553 Bus Data Packets, Format 2 (Bus 16PP194 Weapons Bus Data) from the 16PP194 input as defined in section 4.5 of this document.

vi. Three (3) channels of Video Packets, Format 0 (MPEG-2/H.264) from any selected or all NTSC inputs as defined in section 4.X of this document. Payload type shall be MPEG-2 MP@ML.

vii. One (1) channel of Ethernet Data Packets, Format 0 from the Ethernet input as defined in section 4.X of this document.

viii. If enabled in the setup record Computer Generated Data Packets Format 2, Recording Event. At a minimum an index shall be created for each time packet and event packet. The Recording index type shall be time. The index time value shall be the time packet source type interval (IRIG-B or IRIG-G).

ix. If enabled in the setup record Computer Generated Data Packets Format 3, Recording Index. The supported event packet types shall be as defined in section 5 of this document.

c. Configuration #3 (700 Mbps Continuous Sustained Data Rate) maximum RMM volume of 220Gbytes:

i. Computer Generated Data Packets Format 1, Setup Records.

Setup record format shall be ASCII.

ii. One (1) channel of Time Data Packets, Format 1 (IRIG/GPS/RTC) from the time input as defined in section 4.1 of this document. Time format shall be IRIG-B or IRIG-G.

iii. Two (2) channels of Video Packets, Format 0 (MPEG-2/H.264) from any selected or all NTSC inputs as defined in section 4.X of this document. Payload type shall be MPEG-2 MP@ML.

iv. Two (2) channels of Ethernet Data Packets, Format 0 from the Ethernet input as defined in section 4.X of this document.

v. If enabled in the setup record Computer Generated Data Packets Format 3, Recording Index. The supported event packet types shall be as defined in section 5 of this document.

d. Configuration #4 (200 Mbps Continuous Sustained Data Rate) maximum RMM volume of 64Gbytes:

i. Computer Generated Data Packets Format 1, Setup Records.

Setup record format shall be ASCII.

ii. One (1) channel of Time Data Packets, Format 1 (IRIG/GPS/RTC) from the time input as defined in section 4.1 of this document. Time format shall be IRIG-B or IRIG-G.

iii. Eight (8) channels of MIL-STD-1553 Bus Data Packets, Format 1 (MIL-STD-1553B Bus Data) from any selected or all MIL- STD-1553 inputs as defined in section 4.4 of this document.

iv. Six (6) channels of Video Packets, Format 0 (MPEG-2/H.264) from any selected or all NTSC inputs as defined in section 4.X of this document. Payload type shall be MPEG-2 MP@ML.

v. One (1) channel of Ethernet Data Packets, Format 0 from the Ethernet input as defined in section 4.X of this document.

vi. If enabled in the setup record Computer Generated Data Packets Format 2, Recording Event. At a minimum an index shall be created for each time packet and event packet. The Recording index type shall be time. The index time value shall be the time packet source type interval (IRIG-B or IRIG-G).

vii. If enabled in the setup record Computer Generated Data Packets Format 3, Recording Index. The supported event packet types shall be as defined in section 5 of this document.

2. As a threshold the ADR shall provide IRIG106 Chapter 10 RTC time tagging of recorded data to within 100 microseconds of external IRIG-B time input.

3. As a threshold the ADR shall provide IRIG106 Chapter 10 RTC time tagging of recorded data to within 1 microsecond of external IRIG-G time input.

4. As a threshold PCM channel alignment (channel to channel) shall be equal to or less than 1 micro seconds.

5. As a threshold MIL-STD-1553 channel alignment (channel to channel) shall be equal to or less than 20 micro seconds.

6. As a threshold Video/Audio channel alignment (channel to channel) shall be equal to or less than 100 mseconds.

7. As a threshold 16PP194 channel alignment (channel to channel) shall be equal to or less than 20 micro seconds.

8. As a threshold Ethernet channel alignment (channel to channel) shall be equal to or less than 20 micro seconds.

5.6 Internal or External RMM

1. As a threshold the ADR RMM shall be designed for compliant operation as a Class II IEEE-1394 device, 45 Watts (8-30VDC). It is not permissible to utilize an external power supply or multiple IEEE-1394B 9 pin bi-lingual connectors for RMM power.

2. As a threshold the ADR RMM shall operate from a 12VDC (1 Amp maximum) source provided by COTS IEEE-1394B interface cards. The power shall be provided to the RMM via an IEEE-1394B 9 pin bi-lingual connector.

a. As a threshold the ADR RMM shall interface to a Microsoft Windows based host computing platform via an IEEE-1394B interface. The IEEE- 1394B interface shall allow any compliant IRIG106 Chapter 10 host computing platform to process data directly from the ADR RMM.

b. As a threshold the data transfer rate from the ADR RMM to host computing platform shall be equal to or greater than fifty (50) MBps.

c. As a threshold the ADR RMM shall accept commands from the host computing platform IAW IRIG106 Chapter 10 section 10.9.

3. As a threshold the ADR RMM shall contain an oscillator providing time of day with “keep alive” provisions, minimum of twenty four (24) hours. No batteries shall be used. Oscillator accuracy shall be within four (4) PPM over the full temperature range of the ADR. Setting of time will be IAW IRIG106 Chapter 10 section 10.9.

4. As a threshold the ADR RMM recorded data capacity shall be sufficient to record an aggregate minimum data rate of three hundred (300) mega bits/sec for four (4) hours. A Threshold is for the following RMM storage capacity to be provided for each configuration.

a. Configuration #1 : 64 Gbytes

b. Configuration #2 : 64 Gbytes

c. Configuration #3 : 220 Gbytes

d. Configuration #4 : 64 Gbytes

5. As a threshold the ADR RMM file, directory, block size, and interface file structure shall be IAW IRIG106 Chapter 10 section 10.5, section 10.6 and section 10.11.

6. As a threshold the ADR RMM connector and control functionality shall be IAW IRIG106 Chapter 10 section 10.9.

7. As a threshold the ADR RMM logical address zero (0) or block zero (0) shall not be written to and is RESERVED. This block shall be filled with all 0x00 or 0xFF.

8. As a threshold the ADR RMM shall be “Hot Swappable” while in the ADR.

The RMM shall be removable without having to first shut down power to the

ADR.

9. As a threshold the maximum ADR RMM data transfer error rate shall be 10e-12.

10. As a threshold the ADR RMM IEEE-1394B 9 pin bi-lingual interface connector shall facilitate data download IAW IRIG106 Chapter 10 section 10.9.5 without requiring a separate connector for power.

11. As a threshold the ADR RMM shall be no larger than seven (7.0”) inches by three and one half inches (3.5”) by one and one half inches (1.5”).

12. As a threshold the ADR RMM shall have two restraints, either of which prevents the ejection of the RMM from the ADR internal or remote receptacle if the other restraint fails. It is not acceptable a door over the RMM receptacle to serve as any one of the two RMM restraints. A door shall be used for environmental protection only.

13. As a threshold the ADR RMM shall not be recognized nor mounted as a Microsoft Windows volume. It shall be recognized as a physical media device via the IEEE-1394B interface only.

5.7 Internal RMM

1. As a threshold the ADR shall provide an internal RMM.

2. As a threshold the internal RMM shall be installed in the ADR and shall be accessible within the constraints of the current videotape cassette recording systems.

5.8 External Remote RMM

1. As an objective the ADR shall provide an external remote RMM.

a. The ADR shall provide an IEEE-1394B connector interface for an external remote RMM. The requirement is for an external remote RMM to be utilized from a distance of 1-50 feet. The electrical and signal protocol interface shall be compliant with IEEE-1394B standard.

b. The IEEE-1394B interface to the external remote RMM shall support minimum data rate of four hundred (400) Mbps and a maximum of eight hundred (800) Mbps.

c. The IEEE-1394B speed shall be selectable. Selection of IEEE-1394B speed shall be accomplished by IRIG106 Chapter 10 section 10.6 Computer Generated Data Packets Format 1 Setup Record and specifications provided by this TRD.

d. Use of an external RMM shall be provided using IRIG106-09 Chapter 9 Recorder-Reproducer Attributes in the RCF as follows:

i. The ADR RMM location shall be configured using IRIG106-09 Chapter 9 Recorder-Reproducer Attributes in the RCF as follows:

Figure 5.8.1. ADR External RMM Attributes

e. The ADR shall provide a discrete input (GND) indicating external media is present.

f. The ADR shall provide a discrete input (GND) indicating external media is locked.

g. In order to support the S400 data rate at distances up to 50 feet, the ADR shall provide an inline disconnect in the cable between the ADR and the RMM. It is a requirement that the IEEE 1394B electrical interfaces contain a long-line transceiver interface module equivalent to the one shown in Figure 5.8.2.

Figure 5.8.2. IEEE-1394B Lone-Line Transceiver

5.9 Time Sources and Synchronization

1. As a threshold requirement the ADR shall have an external AC modulated IRIG- B or IRIG-G input. The time input is defined in section 4.1 of this document.

a. As an objective requirement the ADR shall have an external AC modulated IRIG-B and/or IRIG-G output. The time output is defined in section 4.3 of this document.

2. As a threshold the ADR shall have the capability to synchronize from external AC modulated IRIG input signal or from the ADR RMM.

a. As an objective the ADR shall synchronize from MIL-STD-1553 bus message data as defined in section 5 of this document. As a threshold the timing accuracy shall be 1 millisecond.

3. As a threshold the ADR selection of primary time shall be accomplished from IRIG106 Chapter 10 section 10.6 Computer Generated Data Packets Format 1 Setup Record. The source designated as primary, if time is valid, shall be used.

If the primary time source time is not valid, and use of a secondary time source is enabled, the ADR RMM shall be used as the secondary source until the primary time becomes valid.

a. As a threshold the ADR shall be configured from both the IRIG106 Chapter 9 Time Data Type Attributes and the following time sync “V- Spec” or “V” group attributes which are not contained within IRIG106 Chapter 9 TMATS. This attribute is specific to the requirements of the

ADR.

b. ADR time synchronization source shall be configured using IRIG106-09 Chapter 9 Recorder-Reproducer Attributes in the RCF as follows:

Figure 5.9.3. ADR Time Synchronization V-Spec TMATS Attributes

4. As an objective the ADR shall time synchronize to the three monitored (MT mode) MIL-STD-1553 bus messages when enabled on the channel.

a. ADR MIL-STD-1553 time synchronization source shall be configured using IRIG106-09 Chapter 9 Recorder-Reproducer Attributes in the RCF as follows:

5.10 ADR Event Packet Types

1. As a threshold requirement the ADR shall provide events packets from the discrete event command as defined in section 5.2 of this document.

a. As an objective the ADR shall provide data driven event packets from the MIL-STD-1553 channels. ADR configuration of MIL-STD-1553 data driven events shall IAW IRIG106 Chapter 10 section 10.6.7.3 and be configured using IRIG106-09 Chapter 9 Recording Event Attributes in the RCF.

5.11 CH10 Publish

1. As a threshold requirement the ADR shall provide CH10 Publish to the Ethernet interface defined in section 4.7 of this document.

5.12 MIL-STD-1553 Data Filtering

1. As an objective the ADR shall permit any message of any channel to be omitted from being recorded, selection of such messages to be accomplished by IRIG106 Chapter 9 MIL-STD-1553 Data Type Attributes in the RCF as follows:

5.13 MIL-STD-1553 Record Control

1. As an objective the ADR shall provide recording control via a MIL-STD-1553 bus. The setup for control shall be configured using IRIG106-09 Chapter 9 Video Data Type Attributes in the RCF as follows:

5.14 DVR Firmware Transfer File. As a threshold the ADR

operational system firmware loading shall be provided via the RMM.

5.14.1 Recorder Firmware File Location. When an operational system firmware loading transfer to a recorder is made, a binary file will be used. The RMM shall contain a “Directory” and one “Directory Block File Entry” IAW IRIG 106-07 Chapter 10 paragraph 10.5.2.

5.14.2 Directory Block Format. All Directory Block Format fields shall be IAW IRIG 106-07 Chapter 10 table 10-2. The field “n File Entries” value shall be 1.

5.14.3 Directory Entry Format. All Directory Entry Format fields shall be IAW IRIG 106-07 Chapter 10 table 10-3. The field “Time Type” value shall be 0x01. The field “Name” value shall be:

recorder_firmware_file_xxxxxx where xxxxx is replaced by a vendor-specific configuration number for the file. This will notify the recorder to load the Recorder Firmware File to update the operational system.

5.14.4 Recorder Firmware File Structure. The Recorder Firmware Transfer File structure will be a single binary file. Its content format is not controlled by this standard.

5.14.5 Recorder Firmware File Erasure. The Recorder Firmware File shall not be removed from the RMM until an Erase command is issued to prepare the RMM for data recording.

5.15 DVR File Table Entry. As a threshold the ADR shall

provide file table entries IAW IRIG 106-07 Chapter 10 section 10.3.7, section 10.5 table 10-2 and table 10-3.

5.16 DVR and RMM Declassification/Sanitization

Requirements. As a threshold the RMM shall provide for sanitization of media IAW IRIG 106-09.

6.0 ADR Serial Interface Requirements. A threshold requirement is for the ADR to provide for two serial ports that can be configured as serial RS- 232 or differential RS-422 interface.

6.1 A threshold requirement is for the recorder to be controlled IAW IRIG 106-07 Chapter 6 and meet additional requirement of this TRD.

6.2 ADR threshold IRIG-106-09 Chapter 6 serial command requirements

.BIT Runs all of the built‐in‐tests

.CRITICAL [n [mask] ] Specify and view masks that determine which of the .HEALTH status bits are critical warnings

.DATE [start‐date] Specify setting or displaying date from recording device

.DECLASSIFY Secure erases the recording media

.DISMOUNT Unloads the recording media

.ERASE Erases the recording media

.EVENT [text string] Display event table or add event to event table

.FILES Displays information about each recorded file

.HEALTH [feature] Display detailed status of the recorder system

.HELP Displays table of dot" commands "

.IRIG106

Returns supported version number of IRIG‐106 Recorder Command and Control Mnemonics

.MEDIA Displays media usage summary

.MOUNT Powers and enables the recording media

.RECORD [filename] Starts a recording at the current end of data

.RESET Perform software initiated system reset

.SETUP [n] Displays or selects 1 of 16 (0…15) pre‐ programmed data recording formats

6.1 ADR threshold serial commands required that are not in IRIG-106 Chapter 6.

.STATUS Displays the current system status

.TMATS {mode} [n] Write, Read, Save, or Get TMATS file

.STOP [mode] Stops the current recording, playback, or both

.TIME [start‐time] Displays or sets the internal system time

.TMATS VERSION Returns TMATS file G\RN: attribute

.TMATS CHKSUM Returns TMATS file checksum

.VERSION Returns recorder firmware version

.FILES NUM Returns number of files recorded

7.0 ADR Life Cycle

7.1 As a threshold the ADR shall have a useful life of not less than 20 years under any combination of operating and storage conditions, where the operational service life has not been exceeded.

7.2 As a threshold the ADR shall have an operational life of not less than 4,000 flight hours or 6,000 total operating hours. Operational service life is defined as the total operating time between the start of operation and wear out. Wear out is defined as the point where overhaul or repair costs exceed one-half of the replacement cost of the equipment.

8.0Physical Characteristics

8.1 As a threshold the ADR shall not be pressurized.

8.2 As a threshold the ADR shall be capable of transport by air, rail or truck using normal protective packaging. As prepared and packaged for delivery or shipment, the equipment shall be capable of storage in a sheltered environment for 24 months.

8.2 As a threshold the ADR shall have a predicted Mean-Time-Between-Failure (MTBF) of greater than 2000 hours. The COTS media shall have a predicted MTBF of greater than 10,000 hours. COTS media failure is defined as the memory capacity failing below 90 percent of delivered capacity.

8.3 As a threshold the ADR shall be maintained using a two-level maintenance philosophy (Organizational and Depot with depot being the Original Equipment Manufacturer (OEM)). The equipment shall have a maximum organizational level Mean-Time-to-Repair (MTTR) of 1.0 hour.