GRRS v1 0 ATP.pdf

Ground Recorder and Reconstruction System Acceptance Test Plan (ATP)

Version Date: 07/01/2010

Document Identifier: Ground Recorder and Reconstruction System V1.0 ATP.doc

Version: 1.0

GRS Name:____________________________________

GRS Manufacturer:_____________________________

ATP Date: _____________________________________

Prepared By:

846 TSS/TSI

Eglin, AFB, FL 32542

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

Ground Recorder and Reconstruction System ATP V1.0

Contents

1.0 Introduction

1.1 Purpose

1.2 Scope

1.3 References

1.3.1 Key Acronyms

1.3.2 Key Documents

1.4 Terms and Definitions

2.0 Test Operations and Execution

2.1 Conduction Guidelines

2.2 Test Sequence

2.3 Test Scoring

2.3 Unit Under Test Representative

2.4 Re-testing

2.5 Test Equipment

2.6 Test Files

2.7 TSID PCM

3.0 GRS Hardware Testing Requirements

3.1 Mechanical

3.2 Electrical

3.3 Operator

3.4 Data

4.0 GRS Input/Output Testing Requirements

4.1 Time Input

4.2 Time Output

4.3 PCM Input

4.4 PCM Output

5.0 GRS Operational Requirements Testing

5.1 COTS Media Interface and Access

5.2 RMM Interface and Access

5.3 Tape Media Interface and Access

5.4 Input Recording Tests

5.4.1 Max RS-422 PCM/IRIG-B

5.4.2 Min TTL PCM/IRIG-B

5.4.3 Max RS-422 PCM/IRIG-G

5.4.4 Throughput NRZ-L PCM/IRIG-B

5.4.5 Mixed RNRZ-L PCM/IRIG-B

5.4.6 Mixed R/NRZ-L PCM/IRIG-B TMATS

5.4.7 Chapter 10 Publish

5.4.8 Channel Recovery (Packed)

5.5 Output Reconstruction Tests

5.5.1 RMM PCM/IRIG-B/Setup Record

5.5.2 COTS Media PCM/IRIG-B/Setup Record

5.5.3 Tape Media PCM/IRIG-B/Setup Record

5.5.4 RMM PCM/IRIG-G/Ext TMATS

5.5.5 COTS Media PCM/IRIG-B/Bit Rate Change

5.5.6 Publisher PCM/IRIG-B/Setup Record

5.5.7 Remote Interface

Revision Record

REVISION

DATE

REVISION

NUMBER

BRIEF SUMMARY OF CHANGES

07/05/10 1.0 Release ATP.

1.0 Introduction

1.1 Purpose

The purpose of this Acceptance Test Plan (ATP) is for determining if a Ground Recorder and Reconstruction System (GRS) meet the requirements and specifications stated in the GRS Technical Requirements Document (TRD).

1.2 Scope

This document establishes test steps and procedures and pass/fail criteria for each specific requirement stated in the GRS TRD. Also go/no-go criteria will be defined where critical requirements and or specification must be met to continue ATP operations.

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.

The United States Air Force / Air Force Material Command / 46th Test Wing / 846th Test Support Squadron / Flight Test Instrumentation Development, hereinafter referenced as the “test conductor” shall perform and conduct all ATP operations, executions and documentation. Any deviations and decisions related to this ATP shall be will be made by the test conductor and will be final.

1.3 References

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

1.3.1 Key Acronyms

The following acronyms and definitions are used within this document.

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 MRF Modified Recording File ORF Original Recording File PCM Pulse Code Modulation 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 UUT Unit Under Test 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

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

ICD’s

TRD’s

June 7 2010 V1.2 Ground Recorder and Reconstruction System Technical Requirements Document

1.4 Terms and Definitions

The following are GRS terms and definitions which will be used throughout this ATP:

1. “IRIG106”: refers to the IRIG106-07 and -09 released standards followed by the applicable chapter reference.

2. “Reconstruct” or “Reconstruction”: reconstruct the data contained within the defined packets during playback to their original timing and signal characteristics:

a. Output PCM channel data to TTL or differential signals.

b. Output Time channel data to IRIG-A, -B, or -G amplitude modulated signal.

3. “Record” or “Recording”: record an ORF from PCM and IRIG time inputs.

4. “Archival” or “Archive”: produce a DTF on Tape Media or a mounted NTFS volume on the GRS from one (1) or more ORF’s on a RMM or one (1) or more ORF’s and or MRF’s from a mounted NTFS volume on the GRS.

5. “Retrieval” or “Retrieve”: produce one (1) or more ORF’s and or MRF’s from a DTF on Tape Media or a mounted NTFS volume on the GRS.

6. “COTS Media”: any recording media (such as hard disks, solid state drives, RAID, and JBOD) that is ready-made and available for sale to the general public and is NTFS formatted.

7. “COTS Media Interface”: any recording COTS Media interface (such as PATA, SATA, SCSI, IEEE-1394, USB, Ethernet) that is ready-made and available for sale to the general public.

8. “Tape Media”: a tape cartridge from an AIT-3 tape device which contains a DTF and has a SCSI interface.

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

2.0 Test Operations and Execution

2.1 Conduction Guidelines

1. All “threshold” requirement tests are PASS/FAIL. This ATP contains optional tests for specific “objective” requirements within the TRD. All “objective” requirement tests are PASS/FAIL/NA, where NA indicates that the “objective” requirement is Not Applicable or not supported by the GRS UUT. Mandatory tests for each “threshold” requirement stated in the TRD will be defined.

2.2 Test Sequence

1. Each test will be performed in the order presented within this ATP. The GRS UUT ATP will not be complete until each threshold test has been executed. Only tests for objective requirements may be skipped.

2. ATP execution will continue until all steps have been completed regardless of PASS/FAIL result. ATP operations and execution will be terminated by the test conductor if a “NO-GO” criterion is concluded, the GRS UUT is unable to continue, or as otherwise directed by the test conductor.

3. Any deviations during the execution of this ATP due to errors or ambiguities in the test steps, TRD references, limitations or failure of test equipment, or circumstances outside of the TRD or ATP will be at the sole discretion of the test conductor. Any and all deviations from this ATP will be documented by the test conductor.

2.3 Test Scoring

1. The ATP contains GO/NO-GO criteria and they will be specifically noted within the sections and steps of this document. If the test conductor determines a “NO-GO” criterion has been met then all GRS UUT ATP operations and execution will be terminated at that time. A “NO-GO” means that the ATP cannot be executed due to missing capability provided and inability to conduct the test.

2. Each threshold test will be scored as PASS/FAIL. Each objective test will be scored as “PASS”, “FAIL”, or “NA”, where “NA” indicates that the test was skipped or is not supported by the GRS UUT.

3. If a GRS UUT fails to pass a test, the problem will be identified by the GRS UUT representative and the test conductor. Due to time constraints, the test conductor will determine whether corrective actions as presented by the GRS UUT representative will be performed. Failed test(s) will be repeated if corrective action is performed. The test conductor will also determine whether to continue ATP execution or wait for the corrective action to be completed.

a. On-site hardware, firmware and or software modifications, replacements or repairs will not be allowed during ATP operations and execution.

4. At the completion of the GRS ATP the test conductor will sign the test data sheets to Confirm the information on the sheets is accurate. A Test Report, which will summarize the results of the test, will be recorded and logged. The test data sheets will be attached to the Test Report.

5. The final ATP score will be “PASS” if all threshold tests are scored as “PASS”. The final ATP score will be “FAIL” if any threshold tests are scored as “FAIL”.

2.3 Unit Under Test Representative

1. Participation by one (1) GRS UUT representative will be permitted during ATP operations and execution under the following conditions:

a. The UUT representative may be asked to perform tasks on behalf of the test conductor. In this case, only the action requested by the test conductor is to be performed.

b. The representative may not interfere with, or interrupt the testing process at any time.

2.4 Re-testing

1. Failure of any threshold test by the GRS UUT will result in the test conductor determining if and when a re-test will be allowed. If the GRS is to be retested, it will be retested against the ATP in its entirety. Retesting only previously failed tests will not be permitted.

2.5 Test Equipment

1. The following table contains a list of major test equipment that will be utilized in the operations and execution of this ATP:

Name Description Manufacture Data Validation PC Process & Validate Recorded Data Dell IRIG106 Chapter 10 Subscribe PC Process & Validate Recorded Data Dell

IRIG106 Chapter 10 Publish PC Process & Validate Recorded Data Dell

Firewire Cable Provide Connection from RMM to PC NitroAV METS 201 Generate Time, PCM, Mil-Std-1553, SDS

METS 231 Generate Time, PCM, Mil-Std-1553, Video, UART, Ethernet Data SDS

DACS Data Archiving and Conversion SDS CMDP Video Display USAF/AFMC PCM Comparator PCM Channel Alignments USAF/AFMC

CH10 Validator Validate Recorded Data for IRIG106 Chapter 10 Compliancy SDS

Manzanita MPEG2 Analyzer Manzanita

Packet Viewer IRIG-106 Chapter 10 Packet Display John Douglas Associates

Winhex Hexadecimal Display Winhex

2.6 Test Files

1. The following tables describe the Test files that will be used during the testing process.

Each Test Procedure that requires that a file be opened from RMM, Tape, or COTS Media shall reference one or more of the following files. Note that the following file list only describes the file content. Each of the files herein will be located each data source listed (RMM, AIT-3 Tape, Local Media ORF, Local Media DTF, Network Broadcast source, etc. IAW IRIG106 Chapter 10).

2. The GRS is required to provide the capability of selecting any of the available PCM channels for replay/reconstruction. The applicable channels for the GRS are shaded.

Test File 1: “File0001.ch10”

Purpose: Core GRS Requirements; (1) Channel Time and Selectable (4) Channels

PCM.

Channel Data Recorded

Time Input #1 IRIG-B

PCM Input #1 METS Format 1 @ 20Mbps.

Packed Mode.

PCM Input #2 METS Format 3 @ 20Mbps.

Packed Mode.

PCM Input #3 METS Format 2 @ 5Mbps.

Packed Mode.

PCM Input #4 METS Format 4 @ 5Mbps.

Packed Mode.

PCM Input #5 METS Format 1 @ 20Mbps.

Throughput Mode.

PCM Input #6 METS Format 3 @ 20Mbps.

Throughput Mode.

PCM Input #7 METS Format 2 @ 500Kbps.

Throughput Mode.

PCM Input #8 METS Format 4 @ 1Mbps.

Throughput Mode.

MIL-STD-1553 Input #1 METS Multi-Message 1

MIL-STD-1553 Input #2 METS Multi-Message 1

MIL-STD-1553 Input #3 METS Multi-Message 1

MIL-STD-1553 Input #4 METS Multi-Message 1

MIL-STD-1553 Input #5 METS Multi-Message 2

MIL-STD-1553 Input #6 METS Multi-Message 2

MIL-STD-1553 Input #7 METS Multi-Message 2

MIL-STD-1553 Input #8 METS Multi-Message 2

Video Input #1 NTSC Video recorded in Video Format 0 packets.

Video Input #2 NTSC Video recorded in Video Format 0 packets.

Video Input #3 NTSC Video recorded in Video Format 0 packets.

Video Input #4 NTSC Video recorded in Video Format 0 packets.

Video Input #5 NTSC Video recorded in Video Format 0 packets.

Video Input #6 NTSC Video recorded in Video Format 0 packets.

Video Input #7 NTSC Video recorded in Video Format 0 packets.

Video Input #8 NTSC Video recorded in Video Format 0 packets.

Test File 2: “File0002.ch10”

Purpose: All PCM Types; Chapter 4 PCM, Chapter 8 PCM, H009, “TSID” PCM.

Channel Data Recorded

Time Input #1 IRIG-B

PCM Input #1 METS Format 2 @ 20Mbps.

Packed Mode.

PCM Input #2 Chapter 8 PCM, METS Multi-Message 1 messages @ 9Mbps.

Packed Mode.

PCM Input #3 H009 PCM @ 4Mbps.

Packed Mode.

PCM Input #4 “TSID” PCM @ 12Mbps.

Packed Mode.

PCM Input #5 METS Format 2 @ 20Mbps.

Throughput Mode.

PCM Input #6 Chapter 8 PCM, METS Multi-Message 1 messages @ 9Mbps.

Throughput Mode.

PCM Input #7 H009 PCM @ 4Mbps.

Throughput Mode.

PCM Input #8 “TSID” PCM @ 12Mbps.

Throughput Mode.

MIL-STD-1553 Input #1 METS Multi-Message 1

MIL-STD-1553 Input #2 METS Multi-Message 1

MIL-STD-1553 Input #3 METS Multi-Message 1

MIL-STD-1553 Input #4 METS Multi-Message 1

MIL-STD-1553 Input #5 METS Multi-Message 2

MIL-STD-1553 Input #6 METS Multi-Message 2

MIL-STD-1553 Input #7 METS Multi-Message 2

MIL-STD-1553 Input #8 METS Multi-Message 2

Video Input #1 NTSC Video recorded in Video Format 0 packets.

Video Input #2 NTSC Video recorded in Video Format 0 packets.

Video Input #3 NTSC Video recorded in Video Format 0 packets.

Video Input #4 NTSC Video recorded in Video Format 0 packets.

Test File 3: “File0003.ch10”

Purpose: IRIG-G time input; Chapter 4 PCM, Chapter 8 PCM, H009 PCM.

Channel Data Recorded

Time Input #1 IRIG-G

PCM Input #1 METS Format 2 @ 20Mbps.

Packed Mode.

PCM Input #2 Chapter 8 PCM, METS Multi-Message 1 messages @ 9Mbps.

Packed Mode.

PCM Input #3 H009 PCM @ 4Mbps.

Packed Mode.

PCM Input #4 “TSID” PCM @ 12Mbps.

Packed Mode.

Test File 4: “File0004.ch10”

Purpose: Oversampled PCM; Chapter 4 PCM.

Channel Data Recorded

Time Input #1 IRIG-G

PCM Input #1 METS Format 1 @ 1Mbps.

Packed Mode.

PCM Input #2 METS Format 2 @ 5Mbps.

Packed Mode.

PCM Input #3 METS Format 1 @ 10Mbps (5Mbps oversample @10Mbps).

Packed Mode.

PCM Input #4 METS Format 1 @ 20Mbps.

Packed Mode.

2.7 TSID PCM

1. The following defines the “TSID PCM” format:

a. The PCM bit rate shall be 12 million bits per second (12 mbps) and the frame sync pattern shall be 0xfe6b2840.

b. The PCM frame consists of one hundred ninety nine thousand four hundred eighty eight (199,488) bits divided into sixteen (16) twelve thousand four hundred sixty eight (12,468) bit sub frames. See table below:

c. Yellow Cells (I): “Sub frame ID”; Eight (8) bits with one (1) sample per sub frame.

d. Yellow Cells (S): “Sync”; Sixteen (16) bit words sampled two (2) times per sub frame. A total of thirty two (32) bits per sub frame.

3.0 GRS Hardware Testing Requirements

This section contains GRS hardware testing requirements. These tests will be observational, physical, electrical and mechanical that will verify if the GRS UUT is capable of continuing onto the next section of this ATP.

3.1 Mechanical

TRD

Section Requirement Test Procedure Result

3.1.1 Threshold: GRS self-

contained rack mountable unit mechanical interface and external GRS user interface mechanical interface for display, keyboard and mouse unit.

Observation: Confirm the maximum depth of rackmount unit is (30) inches.

Confirm the mechanical interface if utilized for the external GRS user interface is no larger than (1)U EIA for display, keyboard and mouse unit.

3.1.2 Threshold: GRS self-

contained standalone desktop does not have any mechanical requirements.

Not Applicable.

3.2 Electrical

TRD

Section Requirement Test Procedure Result

3.2.2 GO/NO-GO

Threshold: GRS rated input power and AC power draw.

Observation: Confirm GRS input power is (100-240)V AC at (50-60)Hz.

Confirm maximum AC power draw is (10) amps or less.

3.2.3 & 3.4.4

GO/NO-GO

Threshold: GRS Ethernet interface.

Observation: Confirm (1) 1000base T Ethernet port with RJ45 connector.

3.2.4 & 3.4.3

GO/NO-GO

Threshold: GRS IEEE- 1394B interface.

Observation: Confirm at least (1) IEEE-1394B 9-pin bilingual powered interface.

Confirm power output on each IEEE-1394 interface is capable of continuously supplying power at (12) volts, (1) amp (12 Watts).

3.3 Operator

TRD

Section Requirement Test Procedure Result

3.3.1 GO/NO-GO

Threshold: GRS operator interface shall consist of a GUI for local operations.

Test: Apply power and startup GRS.

Observation: Confirm that local operation is provided via a GUI.

3.3.2 GO/NO-GO

Threshold: GRS operator interface shall consist of a Microsoft Windows GUI for remote operations.

Test: Apply power and startup GRS remote operations host computer.

Observation: Confirm that remote operation is provided via a Microsoft Windows GUI.

3.3.3 GO/NO-GO

Threshold: GRS operator interface software application program for remote operations shall be capable of being installed on and executed from a Microsoft XP Professional 32 bit host operating system.

Test 1: Install the GRS software application program for remote operations on a PC with Windows XP Professional 32-bit operating system from provided installation media.

Observation: Confirm that the installation completed without errors.

Test 2: Execute the GRS software application program for remote operations.

Observation: Confirm that the software started properly without errors.

3.3.4 & 3.3.6

GO/NO-GO

Threshold: GRS operator interface software application program for remote operations shall be capable of being installed on and executed from a Microsoft XP Professional 64 bit host operating system.

GRS operator interface software application program for remote operations shall be capable of installation and execution from an Administrator account.

Test 1: From an administrator account install the GRS software application program for remote operations on a PC with Windows XP Professional 64-bit operating system from provided installation media.

Observation: Confirm that the installation completed without errors.

Test 2: From an administrator account execute the GRS software application program for remote operations.

3.3.5 & 3.3.6

GO/NO-GO

Threshold: GRS operator interface software application program for remote operations shall be capable of being installed on and executed from a

Test 1: From an administrator account install the GRS software application program for remote operations on a PC with Microsoft Vista Ultimate 32-bit operating system from provided installation media.

Observation: Confirm that the installation completed

TRD

Section Requirement Test Procedure Result

Microsoft Vista Ultimate 32 bit or 64 bit host operating system.

GRS operator interface software application program for remote operations shall be capable of installation and execution from an Administrator account.

Test 2: From an administrator account execute the GRS software application program for remote operations.

Observation: Confirm that the software started properly without errors.

Test 3: From an administrator account install the GRS software application program for remote operations on a PC with Microsoft Vista Ultimate 64-bit operating system from provided installation media.

Observation: Confirm that the installation completed without errors.

Test 4: From an administrator account execute the GRS software application program for remote operations.

Observation: Confirm that the software started properly without errors.

3.3.5.a & 3.3.6

Objective: GRS operator interface software application program for remote operations shall be capable of being installed on and executed from Microsoft Windows 7 Ultimate 32 bit and 64 bit host operating systems.

GRS operator interface software application program for remote operations shall be capable of installation and execution from an Administrator account.

Test 1: From an administrator account install the GRS software application program for remote operations on a PC with Microsoft Windows 7 Ultimate 32-bit operating system from provided installation media.

Observation: Confirm that the installation completed without errors.

Test 2: From an administrator account execute the GRS software application program for remote operations.

Observation: Confirm that the software started properly without errors.

Test 3: From an administrator account install the GRS software application program for remote operations on a PC with Microsoft Windows 7 Ultimate 64-bit operating system from provided installation media.

Observation: Confirm that the installation completed without errors.

Test 4: From an administrator account execute the GRS software application program for remote operations.

3.3.7 Threshold: GRS operator

interface software application program for remote operations shall provided on-line software application program operations and help manual files. These shall be suitable for printing to hardcopy.

Observation: Confirm that on-line help file or files are shown for the operator to read.

Confirm operations manual and help files are suitable for printing by sending to a printer and using printouts during the ATP as a reference.

TRD

Section Requirement Test Procedure Result

3.3.8 GO/NO-GO

Threshold: GRS system shall provide manuals to include GRS wiring interface diagrams and connector pin-outs.

Observation: Confirm hardware systems manuals/files include wiring interface diagrams and connector pin-outs for all GRS hardware interfaces.

Annotate the operating system that will be used for the remainder of this test:

3.4 Data

TRD

Section Requirement Test Procedure Result

3.4.1 Threshold: GRS data

interface shall provide a minimum of two (2) removable internal COTS Media Microsoft Windows NTFS formatted drives.

Each internal COTS Media drive shall have a minimum capacity of 500GB and a COTS Media Interface.

Observation: Confirm (2) or more removable COTS media each with a minimum (500) GB capacity.

Confirm COTS media interface for each COTS media.

GO/NO-GO

Confirm each removable drive is formatted as Microsoft Windows NTFS.

3.4.2 GO/NO-GO

Threshold: GRS data interface shall provide one

(1) AIT-3 Tape Drive with a SCSI interface.

Observation: Confirm SCSI interface to (1) AIT-3 tape drive.

3.4.3 GO/NO-GO

Threshold: GRS IEEE- 1394B interface.

Observation: Confirm at least (1) IEEE-1394B 9-pin bilingual powered interface.

Confirm power output on each IEEE-1394 interface is capable of continuously supplying power at (12) volts, (1) amp (12 Watts).

3.4.4 GO/NO-GO

Threshold: GRS Ethernet interface.

Observation: Confirm (1) 1000base T Ethernet port with RJ45 connector.

4.0 GRS Input/Output Testing Requirements

This section contains GRS input/output testing requirements. These tests will be observational, physical, electrical and mechanical that will verify if the GRS UUT is capable of continuing onto the next section of this ATP.

4.1 Time Input

TRD

Section Requirement Test Procedure Result

4.1.1 GO/NO-GO

Threshold: GRS shall provide one (1) time input channel. Time input shall be concurrent with each PCM input channel.

Observation: Confirm (1) time input channel.

Time input concurrency with PCM input channels will be tested in section 5.4.

4.1.2 GO/NO-GO

Threshold: GRS shall synchronize to an external AC modulated IRIG A, B or G input IAW IRIG200-04.

Observation: Using Product manual and/or Help files, Confirm time input channel synchronizes to an external AC modulated IRIG-A, B or G input signal IAW

IRIG200-04.

IRIG time synchronization will be tested in section 5.4.

4.1.3 Threshold: GRS time input

signal characteristics.

Input Signal Amplitude Modulated IRIG A, B or G IAW IRIG200-04

Input Levels 0.2 to 10Vpp

Input Termination / Coupling 75Ω / AC (Capacitor)

Input Over Voltage Protection ±11V

Input Synchronization Accuracy

IRIG-A < 1 Microsecond IRIG-B < 10 Microseconds IRIG-G < 1 Microsecond

4.1.4 Threshold: GRS BNC time

input connector. Observation: Confirm time input uses a BNC connector.

4.2 Time Output

TRD

Section Requirement Test Procedure Result

4.2.1 GO/NO-GO

Threshold: GRS shall provide one (1) time output channel. Time output shall be concurrent with each PCM output channel.

Observation: Confirm (1) time output channel. Time output shall be concurrent with each PCM output channel.

Time output concurrency with PCM output channels will be tested in section 5.5.

TRD

Section Requirement Test Procedure Result

4.2.2 GO/NO-GO

Threshold: GRS shall produce an external AC modulated IRIG-B output IAW IRIG200-04 from recorded data Replay.

Observation: Using Product manual and/or Help files, Confirm time output channel generates an external AC modulated IRIG-B output signal IAW IRIG200-04 from recorded data replay.

IRIG time code output from recorded data replay will be tested in section 5.5.

4.2.3 Threshold: GRS Time

output signal characteristics.

Input Signal Amplitude Modulated IRIG B

IAW IRIG200-04

Input Levels Any fixed level between 0.5 to 10Vpp

Input Termination / Coupling 75Ω / AC (Capacitor)

Input Over Voltage Protection ±15V

Input Synchronization Accuracy

IRIG-A < 1 Microsecond IRIG-B < 10 Microseconds IRIG-G < 1 Microsecond

Stability and Drift of the Internal Time Code with No Signal

Stability: +10 ppm Drift: + 5 ppm per year

4.2.4 Threshold: GRS

reproduced time accuracy to IRIG-B format.

Observation: Confirm time output channel reproduces time accuracy to the IRIG-B format IAW IRIG200-04 from recorded data replay.

IRIG-B time accuracy reconstruction will be tested in section 5.5.

4.2.5 Threshold: GRS BNC time

output connector. Observation: Confirm time output uses a BNC connector.

4.3 PCM Input

TRD

Section Requirement Test Procedure Result

4.3.1 GO/NO-GO

Threshold: GRS shall provide (4) PCM input channels each with a minimum sustained PCM data rate of (100) Kbps and a maximum sustained PCM data rate of (20) Mbps. The PCM inputs shall be concurrent with the Time input channel.

Observation: Confirm GRS contains (4) PCM input channels.

PCM minimum and maximum bit rates and concurrency with the time input channel will be tested in section 5.4.

4.3.2.a Objective: GRS shall provide a bit synchronizer input to each channel.

Observation: Using product manual and/or help files to Confirm each PCM input channel has a bit synchronizer.

4.3.3 GO/NO-GO

Threshold : GRS shall provide differential RS-422 and single ended TTL for each PCM input channel.

The differential RS-422 connectors with 120 Ω shall be tri-axial (Trumpeter 70/370 or equivalent) and TTL connectors shall be BNC with 75Ω termination.

Observation: Confirm both RS-422 and single ended TTL inputs exist for each PCM input channel on the PCM and IRIG time input and output device.

Confirm TTL inputs connectors are BNC connectors with 75Ω termination and RS-422 input connectors are tri-axial.

4.3.4 GO/NO-GO

provide selection of differential RS-422 or single ended TTL for each PCM input channel.

Observation: Confirm operator method/procedure to software select or hardware configure between TTL or RS-422 inputs on each PCM input channel.

4.4 PCM Output

TRD

Section Requirement Test Procedure Result

4.4.1 GO/NO-GO

Threshold: GRS shall provide (4) PCM output channels each capable of a minimum sustained PCM data rate of (100) kbps and a maximum sustained PCM data rate of (20) Mbps. The PCM outputs shall be concurrent with the Time output channel.

Observation: Confirm PCM and IRIG time input and output device contains (4) PCM outputs.

Minimum and maximum bit rates will be tested in

4.4.2 Threshold: GRS shall

provide (1) PCM programmable simulator for each PCM output channel that can be externally or internally routed to the GRS PCM input channels.

Test:

1. Connect GRS PCM simulator outputs to test bench PCM inputs.

2. Via GRS local GUI configure PCM simulators as follows:

Ch TYPE SOURCE Data Rate

1 NRZ-L METS FMT 1 20Mbps

2 NRZ-L METS FMT 2 5Mbps

3 NRZ-L TSID 12Mbps

4 NRZ-L METS FMT 1 500kbps

3. Configure PCM simulators for external routing to simulator outputs.

4. Start GRS PCM simulators.

a. Confirm the PCM data and clock output signals are present and correct on each GRS PCM simulator channel.

b. Confirm there are no PCM errors from the simulator channels.

5. Stop the PCM simulators.

6. Configure PCM simulators for internal routing to input PCM channels.

7. Configure GRS time input channel using the

GRS local GUI for IRIG-B input.

8. Configure GRS PCM input channels using the

GRS local GUI for PCM inputs IAW table in step 2.

9. Start PCM simulator outputs.

a. Observation: Confirm IRIG time

TRD

Section Requirement Test Procedure Result format and lock status and time data via the GRS local GUI display.

10. Name recording file “simPCM_irigB.ch10”.

11. Place GRS into record and record for (10) minutes.

a. Observation: Confirm there are no errors and PCM status via the GRS local GUI display.

b. Confirm PCM channels are locked.

12. After (10) minutes stop GRS recording.

a. Observation: Using the PacketViewer confirm recording file on COTS media contains the proper setup record packet, time packets, PCM packets for each channel, indexes packets and event packets.

b. Process the recording file with DACS and confirm compliance with no errors.

c. Confirm RTC time tagging of PCM data is within (10) microseconds of IRIG-B time input.

d. Confirm RTC time tagging of PCM data is within (1) microsecond of all other PCM channels.

4.4.3 GO/NO-GO

Threshold: GRS shall provide a NRZ-L output for each channel with corresponding (0) degree clock from (100) kbps and a maximum sustained PCM data rate of (20) Mbps.

NRZ-L outputs and (0) degrees clock will be tested in

4.4.4 GO/NO-GO

Threshold : GRS shall provide a differential RS-422 and single ended TTL for each PCM output channel.

The differential RS-422 connectors shall be tri-axial (Trumpeter 70/370 or equivalent) and TTL connectors shall be BNC.

Observation: Confirm both RS-422 and single ended TTL outputs exist for each PCM output channel on the GRS PCM and IRIG time input and output device.

Confirm TTL inputs use BNC connectors and RS-422 inputs use tri-axial connectors.

TRD

Section Requirement Test Procedure Result

4.4.5 GO/NO-GO

Threshold: GRS shall provide selection of differential RS-422 or single ended TTL for each PCM output channel.

Observation: Confirm operator method to select between using TTL or RS-422 outputs on each PCM output channel.

4.4.6 Threshold: GRS PCM

output bit rate accuracy and stability during any period of desired data shall not differ from the specified nominal rate by more than (0.1) percent of the nominal rate.

PCM output bit rate accuracy will be tested in section 5.5.

4.4.7 Threshold: GRS PCM

output jitter shall not exceed + (0.1) of a bit interval referenced to the expected transition time with no jitter.

The expected transition time shall be based on the measured average bit period as determined during the immediate preceding (1000) bits.

PCM output jitter will be tested in section 5.5.

5.0 GRS Operational Requirements Testing

This section contains GRS software testing requirements. These tests will be observational and physical, that will Confirm if the GRS UUT is capable of meeting operational requirements.

5.1 COTS Media Interface and Access

NOTE: Steps and tests in section 5.1 can be combined with steps and tests in section 5.5.

TRD

Section Requirement Test Procedure Result

5.1.1 GO/NO-GO

Threshold: GRS GUI shall provide access to COTS Media and selection of one

(1) ORF or MRF for Reconstruction.

Test:

1. From the GRS local GUI open an ORF from COTS media.

a. Observation: Confirm that the file opened correctly.

2. Close the data file and attempt to open an ORF from an attached USB hard drive.

a. Observation: Confirm that the file opened correctly.

Repeat steps 1-2 using an MRF in place of the ORF.

Observation: Confirm that the application provides a GUI for COTS media selection of an ORF or MRF.

5.1.2 GO/NO-GO

Threshold: GRS GUI shall provide access to COTS Media and selection of one

(1) DTF.

Threshold: GRS GUI shall present the directory volumes and files contained within the DTF.

Threshold: GRS GUI shall provide selection of any ORF or MRF contained within the DTF.

Test:

1. From the GRS local GUI open a DTF from a local hard drive.

a. Observation: Confirm that the GRS local GUI presents the directory volumes and file contained within the DTF that was opened in step 1.

2. Open an ORF or MRF file contained within the

DTF.

a. Observation: Confirm that the file was loaded into the GRS local GUI for replay.

3. Perform any required setup to begin replay.

4. Start replay.

a. Observation: Confirm that time display is updating as expected and electrical signals from time and PCM outputs.

Repeat steps 1-4 using a DTF located on a USB hard drive.

5.2 RMM Interface and Access

NOTE: Steps and tests in section 5.2 can be combined with steps and tests in sections 5.5.

TRD

Section Requirement Test Procedure Result

5.2.1

5.2.2

5.2.3

GO/NO-GO

Threshold: GRS local GUI shall provide access to an RMM for Replay and support a block size of 512 bytes per block.

Threshold: GRS local GUI shall present the directory volumes and files contained within the RMM.

Threshold: GRS local GUI shall provide selection of any ORF contained within the RMM for Replay.

Test:

1. Attach an RMM that uses 512 byte blocks to the GRS’s IEEE-1394B port.

2. Open the RMM via the GRS local GUI interface.

a. Observation: Confirm that the GRS local

GUI presents the directory volumes and file contained within the RMM.

3. Open an ORF contained within the RMM.

a. Observation: Confirm that the file was loaded into the GRS local GUI for replay.

4. Perform any required setup to begin replay.

5. Start replay.

a. Observation: Confirm that time display is updating as expected and electrical signals from time and PCM outputs.

5.3 Tape Media Interface and Access

NOTE: Steps and tests in section 5.3 can be combined with steps and tests in section 5.5.

TRD

Section Requirement Test Procedure Result

5.3.1

5.3.2

5.3.3

GO/NO-GO

Threshold: GRS local GUI shall provide access to Tape Media for Replay and support a block size of 32K (32,768) bytes per block.

Threshold: GRS local GUI shall present the directory volumes and files contained within the DTF.

Threshold: GRS local GUI shall provide selection of any ORF or MRF contained within the DTF for Replay.

Test:

1. Insert an AIT-3 Tape with block size of 32K that contains a DTF into the GRS’s AIT-3 Tape Drive.

2. Open the Tape via the GRS local GUI interface.

a. Observation: Confirm that the GRS local

GUI presents the directory volumes and file contained within the DTF that is on the Tape.

3. Open an ORF or MRF contained within the DTF on the tape.

a. Observation: Confirm that the file was loaded into the GRS local GUI for replay.

6. Perform any required setup to begin replay.

7. Start replay.

a. Observation: Confirm that time display is updating as expected and electrical signals from time and PCM outputs.

NOTE: The total bandwidth of the ORF or MRF on the Tape must be less than that of the tape drive itself.

5.4 Input Recording Tests

5.4.1 Max RS-422 PCM/IRIG-B

TRD

Section Requirement Test Procedure Result

5.4.1

5.4.2

5.4.5

5.4.6

5.4.7

5.4.9

Threshold: GRS shall provide Recording to a compliant IRIG106 Chapter 10 section 10.11 ORF on COTS Media containing the following IRIG106 Chapter 10 data types:

Computer Generated Data Packets Format 1, Setup Record.

Time Data Packets Format 1.

PCM Packets Format 1 (IRIG106 Chapter 4/8).

Computer Generated Data Packets Format 2, Recording Index.

Computer Generated Data Packets Format 3, Recording Event.

Threshold: GRS shall provide IRIG106 Chapter 10 section 10.6 RTC time tagging of recorded PCM data to within 10 microseconds or less from external IRIG-B time input.

Threshold: GRS shall provide IRIG106-09 Chapter 10 section 10.6 RTC time tagging of recorded PCM data to within 1 microsecond or less from external IRIG-G time input.

Threshold: GRS shall provide IRIG106 Chapter 10 section 10.6 RTC time tagging of recorded PCM data to within 1 microsecond or less from all PCM input channels.

Threshold: GRS shall provide an IRIG time input channel setup GUI. The operator GUI interface at a

Test:

13. Connect GRS time and PCM inputs to test bench time and PCM outputs.

14. Configure test bench METS time channel for

IRIG-B.

15. Configure test bench METS PCM channels as follows:

Ch TYPE SOURCE Data Rate

INPUT

Packed

NRZ-L

METS FMT 1 20 Mbps RS-422

Packed

NRZ-L

METS FMT 2 20 Mbps RS-422

Packed

NRZ-L

METS FMT 3 20 Mbps RS-422

Packed

NRZ-L

METS FMT 4 20 Mbps RS-422

16. Configure GRS time input channel using the GRS local GUI for IRIG-B input.

17. Configure GRS PCM input channels using the GRS local GUI for PCM inputs IAW table in step 2.

18. Start METS output.

e. Observation: Confirm IRIG time format and lock status and time data via the GRS local GUI display.

19. Name recording file “maxPCM_RS422_irigB.ch10”.

20. Place GRS into record and record for (10) minutes.

f. Observation: Confirm there are no errors and PCM status via the GRS local GUI display.

g. Confirm PCM channels are locked.

21. During recording from the GRS local GUI create an event at 2 minutes, 4 minutes, 6 minutes and 8 minutes.

22. After (10) minutes stop GRS recording.

TRD

Section Requirement Test Procedure Result minimum shall provide setup and configuration applicable to the GRS time input channel.

Threshold: GRS shall provide a PCM input channel setup GUI. The operator GUI interface at a minimum shall provide setup and configuration applicable to the GRS PCM input channels.

h. Observation: Using the PacketViewer confirm recording file on COTS media contains the proper setup record packet, time packets, PCM packets for each channel, indexes packets and event packets.

i. Process the recording file with DACS and confirm compliance with no errors.

j. Confirm RTC time tagging of PCM data is within (10) microseconds of IRIG-B time input.

k. Confirm RTC time tagging of PCM data is within (1) microsecond of all other PCM channels.

5.4.2 Min TTL PCM/IRIG-B

TRD

Section Requirement Test Procedure Result

5.4.1

5.4.2

5.4.5

5.4.6

5.4.7

5.4.9

Threshold: GRS shall provide Recording to a compliant IRIG106 Chapter 10 section 10.11 ORF on COTS Media containing the following IRIG106 Chapter 10 data types:

Computer Generated Data Packets Format 1, Setup Record.

Time Data Packets Format 1.

PCM Packets Format 1 (IRIG106 Chapter 4/8).

Computer Generated Data Packets Format 2, Recording Index.

Computer Generated Data Packets Format 3, Recording Event.

Threshold: GRS shall provide IRIG106 Chapter 10 section 10.6 RTC time tagging of recorded PCM data to within 10 microseconds or less from external IRIG-B time input.

Threshold: GRS shall provide IRIG106-09 Chapter 10 section 10.6 RTC time tagging of recorded PCM data to within 1 microsecond or less from external IRIG-G time input.

Threshold: GRS shall provide IRIG106 Chapter 10 section 10.6 RTC time tagging of recorded PCM data to within 1 microsecond or less from all PCM input channels.

Threshold: GRS shall provide an IRIG time input channel setup GUI. The operator GUI interface at a minimum shall provide setup and configuration applicable

Test:

1. Connect GRS time and PCM inputs to test bench time and PCM outputs.

2. Configure test bench METS time channel for

IRIG-B.

3. Configure test bench METS PCM channels as follows:

Ch TYPE SOURCE Data Rate INPUT

Packed

NRZ-L

METS FMT 1 100 Kbps TTL

Packed

NRZ-L

METS FMT 2 10Mbps TTL

Packed

NRZ-L

METS FMT 1 20Mbps TTL

Packed

NRZ-L

TSID 13.3Mbps TTL

4. Configure GRS time input channel using the GRS local GUI for IRIG-B input.

5. Configure GRS PCM input channels using the GRS local GUI for PCM inputs IAW table in step 2.

6. Start METS output.

a. Observation: Confirm IRIG time format and lock status and time data via the GRS local GUI display.

7. Name recording file “minPCM_irigB_TTL.ch10”.

8. Place GRS into record and record for (10) minutes.

a. Observation: Confirm there are no errors and PCM status via the GRS local GUI display.

b. Confirm PCM channels are locked.

9. During recording from the GRS local GUI create an event at 2 minutes, 4 minutes, 6 minutes and 8 minutes.

10. After (10) minutes stop GRS recording.

a. Observation: Using the PacketViewer confirm recording file on COTS media contains the proper setup record packet, TRD

Section Requirement Test Procedure Result to the GRS time input channel.

Threshold: GRS shall provide a PCM input channel setup GUI. The operator GUI interface at a minimum shall provide setup and configuration applicable to the GRS PCM input channels.

time packets, PCM packets for each channel, indexes packets and event packets.

b. Process the recording file with DACS and confirm compliance with no errors.

c. Confirm RTC time tagging of PCM data is within (10) microseconds of IRIG-B time input.

d. Confirm RTC time tagging of PCM data

5.4.3 Max RS-422 PCM/IRIG-G

TRD

Section Requirement Test Procedure Result

5.4.1

5.4.4

5.4.5

5.4.6

5.4.7

5.4.9

Threshold: GRS shall provide Recording to a compliant IRIG106 Chapter 10 section 10.11 ORF on COTS Media containing the following IRIG106 Chapter 10 data types:

Computer Generated Data Packets Format 1, Setup Record.

Time Data Packets Format 1.

PCM Packets Format 1 (IRIG106 Chapter 4/8).

Computer Generated Data Packets Format 2, Recording Index.

Computer Generated Data Packets Format 3, Recording Event.

Threshold: GRS shall provide IRIG106-09 Chapter 10 section 10.6 RTC time tagging of recorded PCM data to within 1 microsecond or less from external IRIG-G time input.

Threshold: GRS shall provide IRIG106 Chapter 10 section 10.6 RTC time tagging of recorded PCM data to within 1 microsecond or less from all PCM input channels.

Threshold: GRS shall provide an IRIG time input channel setup GUI. The operator GUI interface at a minimum shall provide setup and configuration applicable to the GRS time input channel.

Threshold: GRS shall provide a PCM input channel setup GUI. The operator GUI interface at a minimum shall provide setup

Test:

1. Connect GRS time and PCM inputs to test bench time and PCM outputs.

2. Configure test bench METS time channel for

IRIG-G.

3. Configure test bench METS PCM channels as follows:

Ch TYPE SOURCE Data Rate

INPUT

Packed

NRZ-L

METS FMT 1 20 Mbps RS-422

Packed

NRZ-L

TSID 20 Mbps RS-422

Packed

NRZ-L

TSID 20 Mbps RS-422

Packed

NRZ-L

METS FMT 3 20 Mbps RS-422

4. Configure GRS time input channel using the GRS local GUI for IRIG-G input.

5. Configure GRS PCM input channels using the GRS local GUI for PCM inputs IAW table in step 2.

6. Start METS output.

a. Observation: Confirm IRIG time format and lock status and time data via the GRS local GUI display.

7. Name recording file “maxPCM_irigG_RS422.ch10”.

8. Place GRS into record and record for (10) minutes.

a. Observation: Confirm there are no errors and PCM status via the GRS local GUI display.

b. Confirm PCM channels are locked.

9. During recording from the GRS local GUI create an event at 2 minutes, 4 minutes, 6 minutes and 8 minutes.

10. After (10) minutes stop GRS recording.

a. Observation: Using the PacketViewer

TRD

Section Requirement Test Procedure Result and configuration applicable to the GRS PCM input channels.

contains the proper setup record packet, time packets, PCM packets for each channel, indexes packets and event packets.

b. Process the recording file with DACS and confirm compliance with no errors.

c. Confirm RTC time tagging of PCM data is within (1) microseconds of IRIG-G time input.

d. Confirm RTC time tagging of PCM data

5.4.4 Throughput NRZ-L PCM/IRIG-B

TRD

Section Requirement Test Procedure Result

5.4.1

5.4.2

5.4.5

5.4.6

5.4.7

5.4.9

Threshold: GRS shall provide Recording to a compliant IRIG106 Chapter 10 section 10.11 ORF on COTS Media containing the following IRIG106 Chapter 10 data types:

Computer Generated Data Packets Format 1, Setup Record.

Time Data Packets Format 1.

PCM Packets Format 1 (IRIG106 Chapter 4/8).

Computer Generated Data Packets Format 2, Recording Index.

Computer Generated Data Packets Format 3, Recording Event.

Threshold: GRS shall provide IRIG106 Chapter 10 section 10.6 RTC time tagging of recorded PCM data to within 10 microseconds or less from external IRIG-B time input.

Threshold: GRS shall provide IRIG106-09 Chapter 10 section 10.6 RTC time tagging of recorded PCM data to within 1 microsecond or less from external IRIG-G time input.

Threshold: GRS shall provide IRIG106 Chapter 10 section 10.6 RTC time tagging of recorded PCM data to within 1 microsecond or less from all PCM input channels.

Threshold: GRS shall provide an IRIG time input channel setup GUI. The operator GUI interface at a minimum shall provide setup and configuration applicable

Test:

1. Connect GRS time and PCM inputs to test bench time and PCM outputs.

2. Configure test bench METS time channel for

IRIG-B.

3. Configure test bench METS PCM channels as follows:

Ch TYPE SOURCE Data Rate INPUT

Throughput

NRZ-L

METS FMT 1 20Mbps RS-422

Throughput

NRZ-L

METS FMT 2 500 Kbps RS-422

Throughput

NRZ-L

METS FMT 3 20Mbps RS-422

Throughput

NRZ-L

METS FMT 4 20Mbps RS-422

4. Configure GRS time input channel using the GRS local GUI for IRIG-B input.

5. Configure GRS PCM input channels using the GRS local GUI for PCM inputs IAW table in step 2.

6. Start METS output.

a. Observation: Confirm IRIG time format and lock status and time data via the GRS local GUI display.

7. Name recording file “TP_PCM_irigB.ch10”.

8. Place GRS into record and record for (10) minutes.

a. Observation: Confirm there are no errors and PCM status via the GRS local GUI display.

b. Confirm PCM channels are locked.

9. During recording from the GRS local GUI create an event at 2 minutes, 4 minutes, 6 minutes and 8 minutes.

10. After (10) minutes stop GRS recording.

a. Observation: Using the PacketViewer confirm recording file on COTS media time packets, PCM packets for each

TRD

Section Requirement Test Procedure Result to the GRS time input channel.

Threshold: GRS shall provide a PCM input channel setup GUI. The operator GUI interface at a minimum shall provide setup and configuration applicable to the GRS PCM input channels.

channel, indexes packets and event packets.

b. Process the recording file with DACS and confirm compliance with no errors.

c. Confirm RTC time tagging of PCM data is within (10) microseconds of IRIG-B time input.

d. Confirm RTC time tagging of PCM data

5.4.5 Mixed RNRZ-L PCM/IRIG-B

TRD

Section Requirement Test Procedure Result

5.4.1

5.4.2

5.4.5

5.4.6

5.4.7

5.4.9

Threshold: GRS shall provide Recording to a compliant IRIG106 Chapter 10 section 10.11 ORF on COTS Media containing the following IRIG106 Chapter 10 data types:

Computer Generated Data Packets Format 1, Setup Record.

Time Data Packets Format 1.

PCM Packets Format 1 (IRIG106 Chapter 4/8).

Computer Generated Data Packets Format 2, Recording Index.

Computer Generated Data Packets Format 3, Recording Event.

Threshold: GRS shall provide IRIG106 Chapter 10 section 10.6 RTC time tagging of recorded PCM data to within 10 microseconds or less from external IRIG-B time input.

Threshold: GRS shall provide IRIG106-09 Chapter 10 section 10.6 RTC time tagging of recorded PCM data to within 1 microsecond or less from external IRIG-G time input.

Threshold: GRS shall provide IRIG106 Chapter 10 section 10.6 RTC time tagging of recorded PCM data to within 1 microsecond or less from all PCM input channels.

Threshold: GRS shall provide an IRIG time input channel setup GUI. The operator GUI interface at a minimum shall provide setup and configuration applicable

Test:

1. Connect GRS time and PCM inputs to test bench time and PCM outputs.

2. Configure test bench METS time channel for

IRIG-B.

3. Configure test bench METS PCM channels as follows:

Ch TYPE SOURCE Data Rate INPUT

Packed

NRZ-L

METS FMT 1 20Mbps RS-422

Packed

RNRZ-L

METS FMT 2 500Kbps RS-422

Packed

RNRZ-L

METS FMT 3 1Mbps RS-422

Packed

RNRZ-L

TSID 10Mbps RS-422

4. Configure GRS time input channel using the GRS local GUI for IRIG-B input.

5. Configure GRS PCM input channels using the GRS local GUI for PCM inputs IAW table in step 2.

6. Start METS output.

a. Observation: Confirm IRIG time format and lock status and time data via the GRS local GUI display.

7. Name recording file “mixedPCM_RNRZ_irigB.ch10”.

8. Place GRS into record and record for (10) minutes.

a. Observation: Confirm there are no errors and PCM status via the GRS local GUI display.

b. Confirm PCM channels are locked.

9. During recording from the GRS local GUI create an event at 2 minutes, 4 minutes, 6 minutes and 8 minutes.

10. After (10) minutes stop GRS recording.

a. Observation: Using the PacketViewer

TRD

Section Requirement Test Procedure Result to the GRS time input channel.

Threshold: GRS shall provide a PCM input channel setup GUI. The operator GUI interface at a minimum shall provide setup and configuration applicable to the GRS PCM input channels.

time packets, PCM packets for each channel, indexes packets and event packets.

b. Process the recording file with DACS and confirm compliance with no errors.

c. Confirm RTC time tagging of PCM data is within (10) microseconds of IRIG-B time input.

d. Confirm RTC time tagging of PCM data

5.4.6 Mixed R/NRZ-L PCM/IRIG-B TMATS

TRD

Section Requirement Test Procedure Result

5.4.1

5.4.2

5.4.5

5.4.6

5.4.7

5.4.8

5.4.9

Threshold: GRS shall provide Recording to a compliant IRIG106 Chapter 10 section 10.11 ORF on COTS Media containing the following IRIG106 Chapter 10 data types:

Computer Generated Data Packets Format 1, Setup Record.

Time Data Packets Format 1.

PCM Packets Format 1 (IRIG106 Chapter 4/8).

Computer Generated Data Packets Format 2, Recording Index.

Computer Generated Data Packets Format 3, Recording Event.

Threshold: GRS shall provide IRIG106 Chapter 10 section 10.6 RTC time tagging of recorded PCM data to within 10 microseconds or less from external IRIG-B time input.

Threshold: GRS shall provide IRIG106-09 Chapter 10 section 10.6 RTC time tagging of recorded PCM data to within 1 microsecond or less from external IRIG-G time input.

Threshold: GRS shall provide IRIG106 Chapter 10 section 10.6 RTC time tagging of recorded PCM data to within 1 microsecond or less from all PCM input channels.

Threshold: GRS shall provide an IRIG time input channel setup GUI. The operator GUI interface at a minimum shall provide setup and configuration applicable

Test:

1. Connect GRS time and PCM inputs to test bench time and PCM outputs.

2.…