IRIG_106_2009

7/31/2019 IRIG_106_2009

http://slidepdf.com/reader/full/irig1062009 1/680

Telemetry Standard RCC Document 106-09, Table of Contents, April 2009

DOCUMENT 106-09

TELEMETRY GROUP

TELEMETRY STANDARDS

(PART 1)

ABERDEEN TEST CENTER

DUGWAY PROVING GROUNDELECTRONIC PROVING GROUND

HIGH ENERGY LASER SYSTEMS TEST FACILITY

KWAJALEIN/REAGAN TEST SITE

NATIONAL TRAINING CENTER

WHITE SANDS MISSILE RANGE

YUMA PROVING GROUND

NAVAL AIR WARFARE CENTER AIRCRAFT DIVISION

NAVAL AIR WARFARE CENTER WEAPONS DIVISION

NAVAL UNDERSEA WARFARE CENTER DIVISION, KEYPORT

NAVAL UNDERSEA WARFARE CENTER DIVISION NEWPORT

PACIFIC MISSILE RANGE FACILITY

30TH SPACE WING

45TH SPACE WING

AIR ARMAMENT CENTER

AIR FORCE FLIGHT TEST CENTER

ARNOLD ENGINEERING DEVELOPMENT CENTER

BARRY M. GOLDWATER RANGE

NATIONAL AERONAUTICS AND SPACE ADMINISTRATION

DISTRIBUTION A: APPROVED FOR PUBLIC RELEASE

DISTRIBUTION IS UNLIMITED

7/31/2019 IRIG_106_2009



This page intentionally left blank.

7/31/2019 IRIG_106_2009



DOCUMENT 106-09

TELEMETRY STANDARDS

(PART 1)

APRIL 2009

Prepared by

TELEMETRY GROUP

Published by

Secretariat

Range Commanders Council

U.S. Army White Sands Missile Range,

New Mexico 88002-5110

7/31/2019 IRIG_106_2009




7/31/2019 IRIG_106_2009



TELEMETRY STANDARDS (PART 1)

TABLE OF CONTENTS

CHANGES IN THIS EDITION (SUMMARY) v

PREFACE vii

CHAPTERS

CHAPTER 1: Introduction, Part I

CHAPTER 2: Transmitter and Receiver Systems

CHAPTER 3: Frequency Division Multiplexing Telemetry Standards

CHAPTER 4: Pulse Code Modulation Standards

CHAPTER 5: Digitized Audio Telemetry Standard

CHAPTER 6: Digital Cassette Helical Scan Recorder/Reproducer, Multiplexer/Demultiplexer,

Tape Cassette, and Recorder Control and Command Mnemonics Standards

CHAPTER 7: Reserved for New Topic: “Ground Based Digital Recording Standard (SolidState and Disk Systems)”

CHAPTER 8: Digital Data Bus Acquisition Formatting Standard

CHAPTER 9: * Telemetry Attributes Transfer Standard

CHAPTER 10: * Digital On-board Recorder Standard

APPENDIXES

APPENDIX A: Frequency Considerations for Telemetry

APPENDIX B: Use Criteria for Frequency Division Multiplexing

APPENDIX C: PCM Standards (Additional Information and Recommendations) APPENDIX D: Magnetic Tape Recorder and Reproducer Information and Use Criteria

APPENDIX E: Deleted (Available Transducer Documentation)

APPENDIX F: Continuously Variable Slope Delta Modulation

APPENDIX G: ADARIO Data Block Field Definitions

APPENDIX H: Application of the Telemetry Attributes Transfer Standard

APPENDIX I: Telemetry Attributes Transfer Standard Cover Sheet

APPENDIX J: Telemetry Attributes Transfer Standard Format Example

APPENDIX K: Pulse Amplitude Modulation Standards

APPENDIX L: Asynchronous Recorder Multiplexer Output Re-constructor (ARMOR)

APPENDIX M: Properties of the Differential Encoder Specified in IRIG Standard 106 forOQPSK Modulations

APPENDIX N: * Telemetry Transmitter Command and Control Protocol

APPENDIX O: * Floating Point Formats

APPENDIX P: ** Derived Parameter Specification

Top

* Changed ** New

iii

http://chapter1.pdf/





















http://appendixa.pdf/


http://appendixb.pdf/


http://appendixc.pdf/


http://appendixd.pdf/


http://appendixe.pdf/


http://appendixf.pdf/


http://appendixg.pdf/


http://appendixh.pdf/


http://appendixi.pdf/


http://appendixj.pdf/


http://appendixk.pdf/


http://appendixl.pdf/


http://appendixm.pdf/



http://appendixn.pdf/

http://appendixo.pdf/

http://appendixp.pdf/

http://appendixp.pdf/

http://appendixo.pdf/

http://appendixn.pdf/



























7/31/2019 IRIG_106_2009




iv

7/31/2019 IRIG_106_2009



CHANGES IN THIS EDITION

This document is an updated version of and replaces Range Commanders Council (RCC)

Document 106-07 (Part 1: Telemetry Standards (September 2007). The RCC Telemetry Group(TG) made an extensive effort to produce a well-coordinated and useful document. The

following is a summary of these efforts.

a. Task TG-81: Update Chapter 10, Data Archive Naming Convention

Task Objective/Product. Define a standard for the Chapter 10 file directory/name for

a Removable Memory Module (RMM), a hard disk, or a tape. Establish an archivalblock size format for all digital media.

Comment. A related task, TG-83 resulted in a users handbook for the 2007 edition of Chapter 10. The document name is IRIG 106-07 Chapter 10 Programming

Handbook , and it can be downloaded from RCC document folder RCC 123-09 (IRIG

106-07 Chapter 10 Programming Handbook).

b. Task TG-93 (Part 1): Update Chapter 9: Telemetry Attributes Transfer

Standard (TMATS)

Task Objective/Product. To enhance the content of the TMATS to keep current data

standards in the IRIG 106. The product will be an updated IRIG 106.

Comment. Numerous Chapter 10 related changes were made to Chapter 9. The

Packet Format Attributes Group was removed and the Message Data AttributesGroup was added. Various other minor changes were made. The TMATS provides a

common definition and format to facilitate the transfer of information between the

user and the test range and between ranges.

c. Task TG-93 (Part 2): Update Appendix O: Floating Point Formats

Task Objective/Product. To provide an updated summary and details of floating

point formats.

Comment. Included in the changes, Appendix O now includes a detailed descriptionof the “DEC_64 Bit “G” Double Precision Floating Point” format.

d. Task TG-93 (Part 3): Appendix P (NEW): Derived Parameter Specification

Task Objective/Product. Appendix P defines Derived Parameters and identifies the

components of Derived Algorithm Grammar (operators, numeric constants,measurements, and mathematical functions). Appendix P also provides an overview

of grammar syntax as well as usage examples of grammar and TMATS.

v

7/31/2019 IRIG_106_2009



Comment. Derived parameters are measurements that do not appear in any datastream; instead, they are calculated from telemetry measurements in a data stream,

numeric constants, and/or other derived measurements.

e. Task TG-96: Update Appendix N: Telemetry Transmitter Command And

Control Protocol

Task Objective/Product. To update Appendix N of the IRIG 106 to correct errors and

implement improvements.

Comment. Appendix N provides standards for commands, queries, and statusinformation when communicating with telemetry transmitters configured with

communication ports.

vi

7/31/2019 IRIG_106_2009



vii

PREFACE

The Telemetry Group (TG) of the Range Commanders Council (RCC) has prepared this

document to foster the compatibility of telemetry transmitting, receiving, and signal processingequipment at the member ranges under the cognizance of the RCC. The Range Commanders

highly recommend that telemetry equipment operated by the ranges and telemetry equipmentused in programs that require range support conform to these standards.

These standards do not necessarily define the existing capability of any test range, but

constitute a guide for the orderly implementation of telemetry systems for both ranges and range

users. The scope of capabilities attainable with the utilization of these standards requires thecareful consideration of tradeoffs. Guidance concerning these tradeoffs is provided in the text.

The standards provide the necessary criteria on which to base equipment design and

modification. The ultimate purpose is to ensure efficient spectrum utilization, interference-freeoperation, interoperability between ranges, and compatibility of range user equipment with the

ranges.

This standard, published in two parts, is complemented by a companion series, RCC

Document 118, Test Methods for Telemetry Systems and Subsystems, and RCC Document 119,

Telemetry Applications Handbook.

The policy of the Telemetry Group is to update the telemetry standards and test methods

documents as required to be consistent with advances in technology.

Please direct any questions to:

Secretariat, Range Commanders Council

ATTN: CSTE-DTC-WS-RCC

100 Headquarters AvenueWhite Sands Missile Range, New Mexico 88002-5110

Telephone: (505) 678-1107, DSN 258-1107

E-mail: mailto:[email protected]

****** NOTHING FOLLOWS ******

mailto:[email protected]

mailto:[email protected]

7/31/2019 IRIG_106_2009


Telemetry Standard RCC Document 106-09, Chapter 1, April 2009

CHAPTER 1 INTRODUCTION

PART I

Part I of the Telemetry Standards addresses the here-to-date conventional methods,

techniques, and practices affiliated with aeronautical telemetry applicable to the member

RCC ranges. Part I is composed of ten chapters, with each devoted to a different element of the telemetry system or process.

Reference documents are identified at the point of reference. Commonly used terms are

defined in standard reference glossaries and dictionaries. Definitions of terms with special

applications are included when the term first appears, generally in the front sections of individualchapters. Radio frequency terms are defined in the Manual of Regulations and Procedures for

Federal Radio Frequency Management . Copies of that manual may be obtained from:

Executive Secretary, Interdepartmental Radio Advisory Committee (IRAC)U.S. Department of Commerce, National Telecommunications and Information

Administration (NTIA)

Room 1605, HCHB Building14th and Constitution Avenue, N.W.

Washington, D.C. 20230

Page 1 of 1

7/31/2019 IRIG_106_2009



CHAPTER 2

TRANSMITTER AND RECEIVER SYSTEMS

Paragraph Subject Page

2.1 Radio Frequency Standards for Telemetry ..................................................... 2-1

2.2 Definitions ...................................................................................................... 2-12.3 UHF Bands ..................................................................................................... 2-22.4 UHF Telemetry Transmitter Systems ............................................................. 2-4

2.5 UHF Telemetry Receiver Systems ............................................................... 2-15

REFERENCES

LIST OF FIGURES

Figure 2-1. FQPSK-JR baseband signal generator. ............................................................ 2-6

Figure 2-2. Basic SOQPSK. ............................................................................................... 2-8

Figure 2-3. SOQPSK transmitter. ..................................................................................... 2-10Figure 2-4. Conceptual CPM modulator. ......................................................................... 2-11

Figure 2-5. Continuous single sideband phase noise power spectral density. .................. 2-13

LIST OF TABLES

Table 2-1. Telemetry Frequency Allocations .................................................................... 2-2

Table 2-2. FQPSK-JR Shaping Filter Definition .............................................................. 2-7

Table 2-3. FQPSK-B and FQPSK-JR Phase Map ............................................................. 2-8Table 2-4. SOQPSK-TG Parameters .............................................................................. 2-10

Table 2-5. SOQPSK PRE-Coding Table for IRIG-106 Compatibility ........................... 2-11Table 2-6. Dibit to Impulse Area Mapping ..................................................................... 2-12

Table 2-7. Standard Receiver Intermediate Frequency (IF) Bandwidths ........................ 2-16

.

7/31/2019 IRIG_106_2009



ii


7/31/2019 IRIG_106_2009



CHAPTER 2

TRANSMITTER AND RECEIVER SYSTEMS

2.1 Radio Frequency Standards for Telemetry

These standards provide the criteria to determine equipment and frequency userequirements and are intended to ensure efficient and interference-free use of the radio frequency

spectrum. These standards also provide a common framework for sharing data and providing

support for test operations between ranges. The radio frequency spectrum is a limited naturalresource; therefore, efficient use of available spectrum is mandatory. In addition, susceptibility

to interference must be minimized. Systems not conforming to these standards require

justification upon application for frequency allocation, and the use of such systems is highlydiscouraged. The standards contained herein are derived from the National Telecommunications

and Information Administration's (NTIA) Manual of Regulations and Procedures for Federal

Radio Frequency Management; see http://www.ntia.doc.gov/osmhome/redbook/redbook.html .

2.2 Definitions

Allocation (of a Frequency Band). Entry of a frequency band into the Table of

Frequency Allocations1 for use by one or more radio communication services or the radio

astronomy service under specified conditions.

Assignment (of a Radio Frequency (RF) or Radio Frequency Channel (RFC)).

Authorization given by an administration, for a radio station to use a radio frequency or radio

frequency channel under specified conditions.

Authorization. Permission to use a RF or RFC channel under specified conditions.

Occupied Bandwidth. The width of a frequency band such that below the lower and

above the upper frequency limits, the mean powers emitted are each equal to a specifiedpercentage of the total mean power of a given emission. Unless otherwise specified by the

International Telecommunication Union (ITU) for the appropriate class of emission, the

specified percentage shall be 0.5 percent. The occupied bandwidth is also called the 99-percentpower bandwidth in this document.

Primary Service. A service that has full rights in a band of frequencies and can claimprotection from harmful interference from other services.

1 The definitions of the radio services that can be operated within certain frequency bands contained in the radio

regulations as agreed to by the member nations of the International Telecommunications Union. This table is

maintained in the United States by the Federal Communications Commission and the NTIA.

2-1

http://www.ntia.doc.gov/osmhome/redbook/redbook.html


7/31/2019 IRIG_106_2009



Secondary Service. Service that can be obtained on a noninterference operation basis

with primary service users. Stations of a secondary service shall not cause harmful interference

to stations of a primary service and cannot claim protection from interference from stations of aprimary service; however, they can claim protection from harmful interference from other

secondary stations to which frequencies were assigned at a later date.

2.3 UHF Bands

The bands used for telemetry are described unofficially as the lower-L band from 1435 to1535 MHz, the lower S-band from 2200 to 2290 MHz, and the upper S-band from 2310 to 2395

MHz (see Table 2-1). The 1755 to 1850 MHz band (unofficially called “upper L-band”) can alsobe used for telemetry at many test ranges although it is not listed in the NTIA Table of

Allocations explicitly as a telemetry band. The mobile service is a primary service in the 1755 to

1850 MHz band and telemetry is a part of the mobile service. Since the 1755-1850 MHz band isnot considered a standard telemetry band per this document, potential users must coordinate, in

advance, with the individual range(s) and ensure use of this band can be supported at the subject

range and that it will meet their technical requirements. While these band designations arecommon in telemetry parlance, they may have no specific meaning to anyone else. Telemetryassignments are made for testing2 manned and unmanned aircraft, for missiles, for space, land,

and sea test vehicles, and for rocket sleds and systems carried on such sleds. Telemetry

assignments are also made for testing major components of the systems shown above.

TABLE 2-1. TELEMETRY FREQUENCY ALLOCATIONS

FREQUENCY RANGE

(MHz)

UNOFFICIAL

DESIGNATION COMMENTS

1435-1525 Lower L-band Telemetry primary service (part of mobile service) in USA

1525-1535 Lower L-band Mobile satellite service (MSS) primary

service, telemetry secondary service in

USA

2200-2290 Lower S-band Telemetry co-primary service in USA

2310-2360 Upper S-band Wireless Communications Service

(WCS) and broadcasting-satellite

(sound) service (BSS) primary services,

telemetry secondary service in USA

2360-2390 Upper S-band Telemetry primary service in USA

2A telemetry system as defined here is not critical to the operational (tactical) function of the system.

2-2

7/31/2019 IRIG_106_2009



2.3.1 Allocation of the lower-L Band (1435 to 1535 MHz). This band is allocated in the

United States of America and its possessions for government and nongovernmental aeronautical

telemetry use on a shared basis. The Aerospace and Flight Test Radio Coordinating Council(AFTRCC) coordinates the non-governmental use of this band. The frequencies in this range

will be assigned for aeronautical telemetry and associated remote-control operations 3 for testing

of manned or unmanned aircraft, missiles, rocket sleds, and other vehicles or their majorcomponents. Authorized usage includes telemetry associated with launching and reentry into theearth's atmosphere as well as any incidental orbiting prior to reentry of manned or unmanned

vehicles undergoing flight tests. The following frequencies are shared with flight telemeteringmobile stations: 1444.5, 1453.5, 1501.5, 1515.5, 1524.5, and 1525.5 MHz.

2.3.1.1 1435 to 1525 MHz. This frequency range is allocated for the exclusive use of aeronautical telemetry in the United States of America.

2.3.1.2 1525 to 1530 MHz. The 1525 to 1530 MHz band was reallocated at the 1992 WorldAdministrative Radio Conference (WARC-92). The mobile-satellite service is now a primary

service in this band. The mobile service, which includes aeronautical telemetry, is now asecondary service in this band.

2.3.1.3 1530 to 1535 MHz. The maritime mobile-satellite service is a primary service in the

frequency band from 1530 to 1535 MHz4. The mobile service (including aeronautical telemetry)

is a secondary service in this band.

2.3.2 Allocation of the lower-S Band (2200 to 2300 MHz). No provision is made in this

band for the flight-testing of manned aircraft.

2.3.2.1 2200 to 2290 MHz. These frequencies are shared equally by the United States

Government's fixed, mobile, space research, space operation, and the Earth exploration-satelliteservices. These frequencies include telemetry associated with launch vehicles, missiles, upper

atmosphere research rockets, and space vehicles regardless of their trajectories.

2.3.2.2 2290 to 2300 MHz. Allocations in this range are for the space research service (deepspace only) on a shared basis with the fixed and mobile (except aeronautical mobile) services.

2.3.3 Allocation of the Upper S Band (2310 to 2390 MHz). This band is allocated to thefixed, mobile, radiolocation, and broadcasting-satellite services in the United States of America.

Government and nongovernmental telemetry users share this band in a manner similar to that of

the L band. Telemetry assignments are made for flight-testing of manned or unmanned aircraft,

missiles, space vehicles, or their major components.

2.3.3.1 2310 to 2360 MHz. These frequencies have been reallocated and were auctioned bythe Federal Communications Commission in April 1997. The Wireless Communications Service

is the primary service in the frequencies 2305-2320 MHz and 2345-2360 MHz. The

broadcasting-satellite (sound) service is the primary service in the 2320-2345 MHz band. In the

3The word used for remote control operations in this band is telecommand .4 Reallocated as of 1 January 1990.

2-3

7/31/2019 IRIG_106_2009



band 2320-2345 MHz, the mobile and radiolocation services are allocated on a primary basis

until a broadcasting-satellite (sound) service has been brought into use in such a manner as to

affect or be affected by the mobile and radiolocation services in those service areas

2.3.3.2 2360 to 2390 MHz. The Mobile Service (including aeronautical telemetry) is a

primary service in this band. The status of 2390-2395 MHz is in the process of being finalized.The latest version has these frequencies being made available for telemetry applications.

2.4 UHF Telemetry Transmitter Systems

Telemetry requirements for air, space, and ground systems are accommodated in theappropriate UHF bands 1435 to 1535, 2200 to 2300, and 2310 to 2390 MHz as described in

paragraph 2.3.

2.4.1 Center Frequency Tolerance. Unless otherwise dictated by a particular application,the frequency tolerance for a telemetry transmitter shall be ±0.002 percent of the transmitter's

assigned center frequency. Transmitter designs shall control transient frequency errors

associated with startup and power interruptions. During the first second after turn-on, thetransmitter output frequency shall be within the occupied bandwidth of the modulated signal at

any time when the transmitter output power exceeds -25 dBm. Between 1 and 5 seconds after

initial turn-on, the transmitter frequency shall remain within twice the specified limits for theassigned radio frequency. After 5 seconds, the standard frequency tolerance is applicable for any

and all operations where the transmitter power output is -25 dBm or greater (or produces a field

strength greater than 320 μV/meter at a distance of 30 meters from the transmitting antenna inany direction). Specific uses may dictate tolerances more stringent than those stated.

2.4.2 Output Power. Emitted power levels shall always be limited to the minimum requiredfor the application. The output power shall not exceed 25 watts5. The effective isotropic

radiated power (EIRP) shall not exceed 25 watts5.

2.4.3 Modulation. The traditional modulation methods for aeronautical telemetry are

frequency modulation and phase modulation. Pulse code modulation (PCM)/frequency

modulation (FM) has been the most popular telemetry modulation since around 1970. ThePCM/FM method could also be called filtered continuous phase frequency shift keying

(CPFSK). The RF signal is typically generated by filtering the baseband non-return-to-zero-

level (NRZ-L) signal and then frequency modulating a voltage-controlled oscillator (VCO). The

optimum peak deviation is 0.35 times the bit rate and a good choice for a premodulation filter isa multi-pole linear phase filter with bandwidth equal to 0.7 times the bit rate. Frequency and

phase modulation have a variety of desirable features but may not provide the required

bandwidth efficiency, especially for higher bit rates. When better bandwidth efficiency isrequired, the standard methods for digital signal transmission are the Feher patented quadrature

phase shift keying (FQPSK-B and FQPSK-JR), the shaped offset quadrature phase shift keying

(SOQPSK-TG), and the Advanced Range Telemetry (ARTM) continuous phase modulation(CPM). Each of these methods offer constant, or nearly constant, envelope characteristics and

5 An exemption from this EIRP limit will be considered; however, systems with EIRP levels greater than 25 watts

will be considered nonstandard systems and will require additional coordination with affected test ranges.

2-4

7/31/2019 IRIG_106_2009



are compatible with non-linear amplifiers with minimal spectral regrowth and minimal

degradation of detection efficiency. The first three methods (FQPSK-B, FQPSK-JR, and

SOQPSK-TG) are interoperable and require the use of the differential encoder described inparagraph 2.4.3.1.1 below. Additional information on this differential encoder is contained in

Appendix M. All of these bandwidth-efficient modulation methods require the data to be

randomized. Additional characteristics of these modulation methods are discussed in thefollowing paragraphs and in section 7 of Appendix A.

2.4.3.1 Characteristics of FQPSK-B. FQPSK-B is described in the Digcom Inc. publication,“FQPSK-B, Revision A1, Digcom-Feher Patented Technology Transfer Document, January 15,

1999.” This document can be obtained under a license from:

Digcom Inc.

44685 Country Club Drive

El Macero, CA 95618

Telephone: 530-753-0738

FAX: 530-753-1788

2.4.3.1.1 Differential Encoding. Differential encoding shall be provided for FQPSK-B,

FQPSK-JR, and SOQPSK-TG and shall be consistent with the following definitions:

The NRZ-L data bit sequence {bn} is sampled periodically by the transmitter at time

instants:

,....2,1,0 == nnT t b

where Tb is the NRZ-L bit period. Using the bit index values n as references to the

beginning of symbol periods, the differential encoder alternately assembles I channel and Qchannel symbols to form the following sequences:

,...,,

and

,...,,

753

642

QQQ

I I I

according to the following rules:

( )

( ) ( ) 2)-(2 0n

1)-(2 0n

21212

1222

>⊕=

>⊕=

++

−

nnn

nnn

I bQ

Qb I

where ⊕ denotes the exclusive-or operator, and the bar above a variable indicates the

‘not’ or inversion operator. Q channel symbols are offset (delayed) relative to I channel symbolsby one bit period.

2-5

7/31/2019 IRIG_106_2009



2.4.3.1.2 Characteristics Of FQPSK-JR. FQPSK-JR is a cross-correlated, constant envelope,

spectrum shaped variant of FQPSK. It assumes a quadrature modulator architecture andsynchronous digital synthesis of the I and Q channel modulating signals as outlined in

Figure2-1.

S e r i a l / P a r a l l e l

D i f f e r e n t i a l E n c o d e r

W a v e l e t A s s e m b l y

Clock x

b(nT b)

r b

clock

I n t e r p o l a t e

"-JR"

"-JR"

LPF

LPF

DAC

DAC

Clock x

To

Modulator

I

Digital Analog

Q

Figure 2-1. FQPSK-JR baseband signal generator.

2-6

7/31/2019 IRIG_106_2009



FQPSK-JR utilizes the time domain wavelet functions defined in United States patent

4,567,602, with two exceptions. The transition functions,

2

211

sin1

cos1

)(2

2

−=−=

⎪⎪⎩

⎪⎪

⎨

⎧

⎥⎦⎤

⎢⎣⎡

⎟ ⎠ ⎞⎜

⎝ ⎛ −±

⎥⎦⎤

⎢⎣⎡

⎟ ⎠ ⎞

⎜⎝ ⎛ −±

=

AK

T t K

T t K

t G

s

s

π

π

(2-3)

used in the cited patent are replaced with the following transition functions:

2

2

sin1

cos1

)(22

22

=

⎪⎪⎩

⎪⎪

⎨

⎧

⎟ ⎠ ⎞⎜

⎝ ⎛ −±

⎟ ⎠ ⎞

⎜⎝ ⎛ −±

=

A

T t

A

T t

A

t G

s

s

π

π

(2-4)

where Ts = 2/rb is the symbol period. The digital “JR” spectrum-shaping filter used foreach channel is a linear phase, finite impulse response (FIR) filter. The filter is defined in terms

of its impulse response sequence h(n) in Table 2-2 and assumes a fixed wavelet sample rate of

ρ = 6 samples per symbol. The JRequiv column is the aggregate response of the cascaded JRa andJRb filters actually used.

TABLE 2-2. FQPSK-JR SHAPING FILTER DEFINITION

FILTERWEIGHT

JRequiv JRa JRb

h(0) -0.046875 2-2 -(2-3 + 2-4)

h(1) 0.109375 h(0) (2-1 + 2-3)

h(2) 0.265625 h(0) h(1)

h(3) h(2) - h(0)

h(4) h(1) - -

h(5) h(0) - -

2-7

7/31/2019 IRIG_106_2009



Digital interpolation is used to increase sample rate, moving all alias images created

by digital to analog conversion sufficiently far away from the fundamental signal frequency

range that out-of-channel noise floors can be well controlled. The FQPSK-JR referenceimplementations currently utilize 4-stage Cascade-Integrator-Comb (CIC) interpolators with

unity memory lag factor (see reference [1]). Interpolation ratio “ι” is adjusted as a function of bit

rate such that fixed cutoff frequency post-D/A anti-alias filters can be used to cover the entirerange of required data rates.6

2.4.3.1.3 Carrier Suppression. The remnant carrier level shall be no greater than –30 dBc.Additional information of carrier suppression can be seen at section 7 of Appendix A.

2.4.3.1.4 Quadrature Modulator Phase Map. Table 2-3 lists the mapping from the input to the

modulator (after differential encoding and FQPSK-B or FQPSK-JR wavelet assembly) to the

carrier phase of the modulator output. The amplitudes in Table 2-3 are ± a, where “a” is anormalized amplitude.

TABLE 2-3. FQPSK-B AND FQPSK-JR PHASE MAP

I CHANNEL Q CHANNEL RESULTANT CARRIER PHASE

a a 45 degrees

-a a 135 degrees

-a -a 225 degrees

a -a 315 degrees

2.4.3.2 Characteristics of SOQPSK-TG. SOQPSK is a family of constant envelope CPM

waveforms defined by Mr. T. Hill (see references [2], [3], [4], and [5]). It is mostsimply described as a non-linear frequency modulation modeled as shown in Figure 2-2.

Figure 2-2. Basic SOQPSK.

6The FQPSK-JR definition does not include a specific interpolation method and a post-D/A filter design. However,

it is known that benchmark performance will be difficult to achieve if the combined effects of interpolation and anti-

alias filter produce more than .04 dB excess attenuation at 0.0833 times the input sample rate and more than 1.6 dB

of additional attenuation at 0.166 times the sample rate where the input sample rate is referred to the input of the

interpolator assuming 6 samples per second.

2-8

7/31/2019 IRIG_106_2009



The SOQPSK waveform family is uniquely defined in terms of impulse excitation of a frequency

impulse shaping filter function g(t):

5)-(2 )()()( t wt nt g =

where

)(

)(

6)-(2 )(

)(sin

)(41

)(cos)(

2

1

2

2

2

1

1

s

s

T

Bt t

T

Bt t

t

t

t

t At n

π θ

ρ θ

θ

θ

θ

πθ

=

=

⎥⎦

⎤⎢⎣

⎡⎥⎦

⎤⎢⎣

⎡

−≡

⎪⎪⎪⎪⎪

⎩

⎪⎪⎪⎪⎪

⎨

⎧

+>

+≤<

⎥⎥⎥⎥⎥

⎦

⎤

⎢⎢⎢⎢⎢

⎣

⎡

⎟⎟⎟⎟⎟

⎠

⎞

⎜⎜⎜⎜⎜

⎝

⎛ ⎟⎟ ⎠

⎞⎜⎜⎝

⎛ −

+

≤

≡

21

211

2

1

1

,0

7)-(2 , cos12

1

,1

w(t)

T T

T

t

T T T

t T

T

T T

t

T T

t

s

s

s

s

π

n(t) is a modified spectral raised cosine filter of amplitude A, rolloff factor ρ and havingan additional time scaling factor B. The function w(t) is a time domain windowing function that

limits the duration of g(t). The amplitude scale factor A is chosen such that

( )

( )

8)-(2 2

)(21

21

∫+

+−

=s

s

T T T

T T T

dt t gπ

Given a time series binary data sequence

( ) 9)-(2 ....,,,,..., 21012 aaaaaa −−=r

wherein the bits are represented by normalized antipodal amplitudes {+1,-1}, the ternary

impulse series is formed with the following mapping rule. See also references [4] and [5].

( )( )

10)-(2 2

1 211 −−+ −−= iiii aaa

α

2-9

7/31/2019 IRIG_106_2009



… which forms a data sequence alphabet of three values {+1,0,-1}. It is important to

note that this modulation definition does not establish an absolute relationship between the

digital in-band inter-switch trunk signaling (dibits) of the binary data alphabet and transmittedphase as with conventional quadriphase OQPSK implementations. In order to achieve

interoperability with coherent FQPSK-B demodulators, some form of precoding must be applied

to the data stream prior to, or in conjunction with, conversion to the ternary excitation alphabet.The differential encoder defined in paragraph 2.4.3.1.1 fulfills this need. However, to guarantee

full interoperability with the other waveform options, the polarity relationship between frequency

impulses and resulting frequency or phase change must be controlled. Thus, SOQPSKmodulators proposed for this application shall guarantee that an impulse of value of (+1) will

result in an advancement of the transmitted phase relative to that of the nominal carrierfrequency (i.e., the instantaneous frequency is above the nominal carrier).

For purposes of this standard, only one specific variant of SOQPSK and SOQPSK-TG is acceptable. This variant is defined by the parameter values given in Table 2-4.

TABLE 2-4. SOQPSK-TG PARAMETERS

SOQPSK TYPE B T 1 T 2

SOQPSK-TG 0.70 1.25 1.5 0.50

2.4.3.2.1 Differential Encoding of SOQPSK-TG. As discussed above, interoperability withFQPSK-B equipment requires a particular pre-coding protocol or a functional equivalent thereof.

A representative model is shown in Figure 2-3.

Figure 2-3. SOQPSK transmitter.

PRE-CODER

FREQUENCY

IMPULSE

FILTER g(t)

FREQUENCY

MODULATOR{a (nT

b )}

Impulse Series(nT b)

S(t)DIFFERENTIAL ENCODER

I k

Q k+1

The differential encoder block will be implemented in accordance with the definition

of Section 2.4.3.1.1. Given the symbol sequences I k and Qk , and the proviso that a normalizedimpulse sign of +1 will increase frequency, the pre-coder will provide interoperability with the

FQPSK signals defined herein if code symbols are mapped to frequency impulses in accordance

with Table 2-5 (below) where ΔΦ is the phase change.

2-10

7/31/2019 IRIG_106_2009



TABLE 2-5. SOQPSK PRE-CODING TABLE FOR IRIG-106 COMPATIBILITY

MAP K FROM I K MAP K+1 FROM QK+1

I k Qk-1 I k-2 k Qk+1 I k Qk-1 k+1 -1 X* -1 0 0 -1 X* -1 0 0

+1 X* +1 0 0 +1 X* +1 0 0

-1 -1 +1 -π /2 -1 -1 -1 +1 +π /2 +1

-1 +1 +1 +π /2 +1 -1 +1 +1 -π /2 -1

+1 -1 -1 +π /2 +1 +1 -1 -1 -π /2 -1

+1 +1 -1 -π /2 -1 +1 +1 -1 +π /2 +1

* Note: Does not matter if “X” is a +1 or a -1

2.4.3.3 Characteristics of Advanced Range Telemetry (ARTM) CPM. ARTM CPM is a

quaternary signaling scheme in which the instantaneous frequency of the modulated signal is afunction of the source data stream. The frequency pulses are shaped for spectral containment

purposes. The modulation index alternates at the symbol rate between two values to improve the

likelihood that the transmitted data is faithfully recovered. Although the following description isin terms of carrier frequency, other representations and generation methods exist that are

equivalent. A block diagram of a conceptual ARTM CPM modulator is illustrated in Figure 2-4.

Source bits are presented to the modulator and are mapped into impulses that are applied to afilter with an impulse response g(t). The resulting waveform f(t) is proportional to the

instantaneous frequency of the desired modulator output. This signal can be used to frequencymodulate a carrier to produce an RF signal representation.

FrequencyFilter g(t)

FrequencyModulator

Data toImpulse

Mapping

a(iT/2)

α(t)s(t, )

0001101101...

f(t, )

Multi-hCPM

+1

-1

t

+3

-3

11

10

01

00

t

Figure 2-4. Conceptual CPM modulator.

2-11

7/31/2019 IRIG_106_2009



Variables and function definitions in Figure 2-4 above are as follows:

• a(iT/2) = ith bit of binary source data, either a 0 or 1

• The frequency pulse shape for ARTM CPM is a three symbol long raised cosine

pulse defined by ⎥⎦⎤⎢

⎣⎡ ⎟

⎠ ⎞⎜

⎝ ⎛ −=

T

t

T t g

3

2cos16

1)( π for 0 ≤ t ≤3T (2-11)

• T = Symbol period equal to 2/(bit rate in bits/second)

• α(iT) = ith impulse with area equal to either a +3,+1,-1 or –3 determined by

Table 2-6 below. Note that an impulse is generated for each dibit pair (at thesymbol rate).

• f(t,α) = frequency filter output equal to (2-12)∑+∞

−∞=

−i

i iT t giT h )()(α π

• h = modulation index; h alternates between h1 and h2 where h1 = 4/16, h2 = 5/16

TABLE 2-6. DIBIT TO IMPULSE AREA MAPPING

INPUT DIBIT [a(i) a(i+1)] IMPULSE AREA

1 1 +3

1 0 +1

0 1 -1

0 0 -3

For more information on the ARTM CPM waveform, please refer to Appendix A of thisdocument and to the publication at reference [6].

2.4.3.4 Data Randomization. The data input to the transmitter shall be randomized using either

an encryptor that provides randomization or an Interrange Instrumentation Group (IRIG) 15-bit

randomizer as described in Chapter 6 and Appendix D. The purpose of the randomizer is toprevent degenerative data patterns from degrading data quality.

2.4.3.5 Bit Rate. The bit rate range for FQPSK-B, FQPSK-JR, and SOQPSK-TG shall bebetween 1 Mb/s and 20 Mb/s. The bit rate range for ARTM CPM shall be between 5 Mb/s and

20 Mb/s.

2.4.3.6 Transmitter Phase Noise. The sum of all discrete spurious spectral components (singlesideband) shall be less than -36 dBc. The continuous single sideband phase noise power spectral

density (PSD) shall be below the curve shown in Figure 2-5 below. The maximum frequency for

the curve in Figure 2-5 is one-fourth of the bit rate. For bit rates greater than 4 Mb/s, the phasenoise PSD shall be less than –100 dBc/Hz between 1 MHz and one-fourth of the bit rate.

2-12

7/31/2019 IRIG_106_2009



Single Sideband Phase Noise L(f) - Upper Limit

-30

-60

-70

-80

-90

-100

-30

-60

-80

-90

-100 -100

-110

-100

-90

-80

-70

-60

-50

-40

-30

-20

10 100 1000 10000 100000 1000000

Frequency Offse t From Carrier - Hertz

L ( f ) - d B c / H z

FQPSK or SOQPSK CPM

Figure 2-5. Continuous single sideband phase noise power spectral density.

2.4.3.7 Modulation Polarity. An increasing voltage at the input of a frequency modulation (FM)transmitter shall cause an increase in output carrier frequency. An increase in voltage at the

input of a phase modulation (PM) transmitter shall cause an advancement in the phase of the

output carrier. An increase in voltage at the input of an amplitude modulation (AM) transmittershall cause an increase in the output voltage of the output carrier.

2.4.4 Spurious Emission and Interference Limits. Spurious7 emissions from the transmitter

case, through input and power leads, and at the transmitter radio frequency (RF) output andantenna-radiated spurious emissions are to be within required limits shown in MIL-STD-461,

Electromagnetic Emission and Susceptibility Requirements for the Control of Electromagnetic

Interference. Other applicable standards and specifications may be used in place of MIL-STD-461 if necessary.

2.4.4.1 Transmitter-Antenna System Emissions. Emissions from the antenna are of primary

importance. For example, a tuned antenna may or may not attenuate spurious frequencyproducts produced by the transmitter, and an antenna or multi-transmitter system may generate

spurious outputs when a pure signal is fed to its input. The transmitting pattern of such spurious

frequencies is generally different from the pattern at the desired frequency. Spurious outputs inthe transmitter output line shall be limited to -25 dBm. Antenna-radiated spurious outputs shall

be no greater than 320 μV/meter at 30 meters in any direction.

7 Any unwanted signal or emission is spurious whether or not it is related to the transmitter frequency (harmonic).

2-13

7/31/2019 IRIG_106_2009



WARNING: Spurious levels of -25 dBm may severely degrade performance of sensitive

receivers whose antennas are located in close proximity to the telemetry transmitting antenna.

Therefore, lower spurious levels may be required in certain frequency ranges, such as near GPS

frequencies.

2.4.4.2 Conducted and Radiated Interference. Interference (and the RF output itself) radiated from

the transmitter or fed back into the transmitter power, signal, or control leads could interfere with the

normal operation of the transmitter or the antenna system to which the transmitter is connected. All

signals conducted by the transmitter's leads (other than the RF output cable) in the range of 150 kHz

to 50 MHz, and all radiated fields in the range of 150 kHz to 10 GHz (or other frequency ranges as

specified) must be within the limits of the applicable standards or specifications.

2.4.5 Operational Flexibility. Each transmitter shall be capable of operating at all frequencies

within its allocated band without design modification8.

2.4.6 Modulated Transmitter Bandwidth.9 Telemetry applications covered by this standard shall use

99-percent power bandwidth to define occupied bandwidth and -25 dBm bandwidth as the primarymeasure of spectral efficiency. The -25 dBm bandwidth is the minimum bandwidth that contains all

spectral components that are -25 dBm or larger. A power level of -25 dBm is exactly equivalent to an

attenuation of the transmitter power by 55 + 10×log(P) dB where P is the transmitter power expressed in

watts. The spectra are assumed symmetrical about the transmitter’s center frequency unless specified

otherwise. All spectral components larger than –(55 + 10×log(P)) dBc at the transmitter output must be

within the spectral mask calculated using the following equation:

( )m

R f f f f RK f M cc ≥−−−+= ;log100log90 (2-13)

where

M(f) = power relative to P (i.e., units of dBc) at frequency f (MHz)

K = -20 for analog signals

K = -28 for binary signals

K = -61 for FQPSK-B, FQPSK-JR, SOQPSK-TG

K = -73 for ARTM CPM

f c = transmitter center frequency (MHz)

R = bit rate (Mb/s) for digital signals or

(MHz) for analog FM signals( max f f +Δ )

m = number of states in modulating signal;

m = 2 for binary signals

m = 4 for quaternary signals and analog signalsf = peak deviationΔf max = maximum modulation frequency

8 The intent is that fixed frequency transmitters can be used at different frequencies by changing crystals or other

components. All applicable performance requirements will be met after component change.9 These bandwidths are measured using a spectruma analyzer with the following settings: 30-kHz resolution

bandwidth, 300-Hz video bandwidth, and no max hold detector or averaging.

2-14

7/31/2019 IRIG_106_2009



Note that the mask in this standard is different than the masks contained in earlier versions of

the Telemetry Standards. Equation (2-13) does not apply to spectral components separated from the

center frequency by less than R/m. The –25 dBm bandwidth is not required to be narrower than1 MHz. Binary signals include all modulation signals with two states while quaternary signals include

all modulation signals with four states (quadrature phase shift keying and FQPSK-B are two examples

of four-state signals). Appendix A, paragraph 6.0, contains additional discussion and examples of thisspectral mask.

2.4.7 Valid Center Frequencies Near Telemetry Band Edges. The telemetry bands, asspecified, start and stop at discrete frequencies. Telemetry transmitters transmitting PCM/FM or

SOQPSK-TG/FQPSK-B/FQPSK-JR or ARTM CPM, even with optimal filtering, do not havediscrete start and stop frequencies. In order to determine a valid carrier frequency, the

transmitter power, modulation scheme, and data rate must be known. The distance, in frequency,

from the point in which the spectral masks, as described in paragraph 2.4.6, intersect the absolute

value of -25 dBm equals the amount in which the transmitter carrier frequency must be from theband edge frequency. Paragraph 12.0 of Appendix A contains additional discussion and

examples of center frequency determination when operating near telemetry band edges.

2.5 UHF Telemetry Receiver Systems

As a minimum, UHF receiver systems shall have the following characteristics:

2.5.1 Spurious Emissions. The RF energy radiated from the receiver itself or fed back into thepower supply, and/or the RF input, output, and control leads in the range from 150 kHz to 10 GHz

shall be within the limits specified in MIL-STD 461. The receiver shall be tested in accordance with

MIL-STD 461 or RCC Document 118, volume II, Test Methods for Telemetry RF Subsystems.

Other applicable standards and specifications may be used in place of MIL-STD-461, if necessary.

2.5.2 Frequency Tolerance. The accuracy of all local oscillators within the receiver shall be suchthat the conversion accuracy at each stage and overall is within ±0.001 percent of the indicated tuned

frequency under all operating conditions for which the receiver is specified.

2.5.3 Receiver Phase Noise. The sum of all discrete spurious spectral components (singlesideband) shall be less than -39 dBc. The continuous single sideband phase noise power spectral

density (PSD) shall be 3 dB below the curve shown in Figure 2-5. The maximum frequency for

the curve in Figure 2-5 is one-fourth of the bit rate. For bit rates greater than 4 Mb/s, the phase

noise PSD shall be less than –103 dBc/Hz between 1 MHz and one-fourth of the bit rate.

2.5.4 Spurious Responses. Rejection of any frequency other than the one to which the receiver

is tuned shall be a minimum of 60 dB referenced to the desired signal over the range 150 kHz to10 GHz.

2.5.5 Operational Flexibility. All ground-based receivers shall be capable of operating over theentire band for which they are designed. External down-converters may be either intended for

the entire band or a small portion but capable of retuning anywhere in the band withoutmodification.

2-15

7/31/2019 IRIG_106_2009



2.5.6 Intermediate Frequency (IF) Bandwidths. The standard receiver IF bandwidths are

shown in Table 2-7. These bandwidths are separate from and should not be confused withpost-detection low-pass filtering that receivers provide.10 The ratio of the receiver’s -60 dB

bandwidth to the -3 dB bandwidth shall be less than 3 for new receiver designs.

TABLE 2-7. STANDARD RECEIVER INTERMEDIATE FREQUENCY (IF)

BANDWIDTHS

300 kHz 1.5 MHz 6 MHz



1000 kHz 4.0 MHz 20 MHz1

1. For data receivers, the IF bandwidth should typically be selected so

that 90 to 99 percent of the transmitted spectrum is within the receiver

3-dB bandwidth. In most cases, the optimum IF bandwidth will benarrower than the 99-percent power bandwidth.

2. Bandwidths are expressed at the points where response is 3 dB below the

response at the design center frequency, assuming that passband ripple is

minimal, which may not be the case. The 3-dB bandwidth is chosen becauseit closely matches the noise bandwidth of a "brick-wall" filter of the same

bandwidth. The "optimum" bandwidth for a specific application may be

other than that stated here. Ideal IF filter response is symmetrical about itscenter frequency; in practice, this may not be the case.

3. Not all bandwidths are available on all receivers or at all test ranges.Additional receiver bandwidths may be available at some test ranges

especially if the range has receivers with digital IF filtering

10 In most instances, the output low-pass filter should not be used to “clean up” the receiver output prior to use with

demultiplexing equipment.

2-16

7/31/2019 IRIG_106_2009



2-17

REFERENCES

[1] Hogenauer, E., “An Economical Class of Digital Filters for Decimation and Interpolation,

IEEE Transactions on Acoustics, Speech, and Signal Processing,” Vol. ASSP-29, No. 2,

April 1981.

[2] Hill T., “An Enhanced, Constant Envelope, Interoperable Shaped Offset QPSK(SOQPSK)

Waveform for Improved Spectral Efficiency,” Proceedings of the International

Telemetering Conference, San Diego, California, October 2000.

[3] Younes B., Brase J., Patel C., Wesdock J., “An Assessment of Shaped Offset QPSK for Use

in NASA Space Network and Ground Network Systems,” Meetings of Consultative

Committee for Space Data Systems, Toulouse, France, October, 2000.

[4] Geoghegan, M., “Implementation and Performance Results for Trellis Detection of

SOQPSK,” Proceedings of the International Telemetering Conference, Las Vegas,

Nevada, October 2001.

[5] Simon, M., “Bandwidth-Efficient Digital Modulation with Application to Deep SpaceCommunications,” Monograph number 3, DESCANSO Monograph Series, JPL

Publication 00-17, Jet Propulsion Laboratory, California Institute of Technology, 2001.

This publication is available free via the Internet at DESCANSO: Deep Space

Communications and Navigation Systems

[6] Geoghegan, M. “Description and Performance Results for the multi-h CPM Tier II

Waveform,” Proceedings of the International Telemetering Conference, San Diego, CA,

October 2000.

**** END CHAPTER 2 ****

http://descanso.jpl.nasa.gov/Monograph/series3/complete1.pdf





7/31/2019 IRIG_106_2009



CHAPTER 3

FREQUENCY DIVISION MULTIPLEXING TELEMETRY STANDARDS


3.1 General............................................................................................................. 3-13.2 FM Subcarrier Characteristics ......................................................................... 3-1

3.3 FM Subcarrier Channel Characteristics........................................................... 3-1

3.4 Tape Speed Control and Flutter Compensation............................................... 3-5

LIST OF TABLES

Table 3-1a. Proportional-Bandwidth Fm Subcarrier Channels 7.5% Channels .............. 3-2

Table 3-1b. Proportional-Bandwidth Fm Subcarrier Channels 15% Channels ............... 3-3

Table 3-1c. Proportional-Bandwidth Fm Subcarrier Channels 30% Channels ............... 3-4

Table 3-2. Constant-Bandwidth Fm Subcarrier Channels ................................................ 3-6Table 3-3. Reference Signal Usage................................................................................... 3-7

7/31/2019 IRIG_106_2009



ii


7/31/2019 IRIG_106_2009



CHAPTER 3

FREQUENCY DIVISION MULTIPLEXING TELEMETRY STANDARDS

3.1 General

In frequency division multiplexing, each data channel makes use of a separate subcarrierthat occupies a defined position and bandwidth in the modulation baseband of the RF carrier.

Two types of frequency modulation (FM) subcarrier formats may be used. The data bandwidth

of one format type is proportional to the subcarrier center frequency, while the data bandwidth of

the other type is constant, regardless of subcarrier frequency.

3.2 FM Subcarrier Characteristics

In these systems, one or more subcarrier signals, each at a different frequency, areemployed to frequency modulate (FM) or phase modulate (PM) a transmitter in accordance with

the RF conditions specified in Chapter 2. The following subparagraphs set forth the standards

for utilization of FM frequency division multiplexing.

3.2.1 Each of the subcarriers conveys measurement data in FM form. The number of data

channels may be increased by modulating one or more of the subcarriers with a time-divisionmultiplex format such as pulse-code modulation (PCM).

3.2.2 The selecting and grouping of subcarrier channels depend upon the data bandwidth

requirements of the application at hand and upon the necessity to ensure adequate guard bandsbetween channels. Combinations of both proportional-bandwidth channels and constant-

bandwidth channels may be used.

3.3 FM Subcarrier Channel Characteristics

The following subparagraphs describe the characteristics of proportional-bandwidth and

constant-bandwidth FM subcarrier channels.

3.3.1 Proportional-Bandwidth FM Subcarrier Channel Characteristics. Table 31A,

Table 31B, and Table 31C list the standard proportional-bandwidth FM subcarrier channels.The channels identified with letters permit ±15 or ±30 percent subcarrier deviation rather than

±7.5 percent deviation but use the same frequencies as the 12 highest channels. The channels

shall be used within the limits of maximum subcarrier deviation. See Appendix B for expectedperformance tradeoffs at selected combinations of deviation and modulating frequency.

3-1

7/31/2019 IRIG_106_2009



TABLE 3-1A. PROPORTIONAL-BANDWIDTH FM SUBCARRIER CHANNELS

7.5% CHANNELS

Channel

Center

Frequencies(Hz)

Lower

DeviationLimit(Hz)

Upper

DeviationLimit(Hz)

Nominal

FrequencyResponse(Hz)

Nominal

Rise Time(ms)

Maximum

FrequencyResponse(Hz)

Minimum

Rise Time(ms)

1 400 370 430 6 58 30 11.7

2 560 518 602 8 44 42 8.33

3 730 675 785 11 32 55 6.40

4 960 888 1032 14 25 72 4.86

5 1300 1202 1398 20 18 98 3.60

6 1700 1572 1828 25 14 128 2.74

7 2300 2127 2473 35 10 173 2.03

8 3000 2775 3225 45 7.8 225 1.56

9 3900 3607 4193 59 6.0 293 1.20

10 5400 4995 5805 81 4.3 405 .864

11 7350 6799 7901 110 3.2 551 .635

12 10 500 9712 11 288 160 2.2 788 .444

13 14 500 13 412 15 588 220 1.6 1088 .322

14 22 000 20 350 23 650 330 1.1 1650 .212

15 30 000 27 750 32 250 450 .78 2250 .156

16 40 000 37 000 43 000 600 .58 3000 .117

17 52 500 48 562 56 438 788 . 44 3938 .089

18 70 000 64 750 75 250 1050 .33 5250 .06

19 93 000 86 025 99 975 1395 .25 6975 .050

20 124 000 114 700 133 300 1860 .19 9300 .038

21 165 000 152 625 177 375 2475 .14 12 375 .029

22 225 000 208 125 241 875 3375 .10 16 875 .021

23 300 000 277 500 322 500 4500 .08 22 500 .016

24 400 000 370 000 430 000 6000 .06 30 000 .012

25 560 000 518 000 602 000 8400 .04 42 000 .008

See notes at end of Table 3-1C.

3-2

7/31/2019 IRIG_106_2009



TABLE 3-1B. PROPORTIONAL-BANDWIDTH FM SUBCARRIER CHANNELS

15% CHANNELS

Channel

Center

Frequencies

(Hz)

Lower

DeviationLimit(Hz)

Upper

DeviationLimit(Hz)

Nominal

FrequencyResponse

(Hz)

Nominal

Rise Time

(ms)

Maximum

FrequencyResponse

(Hz)

Minimum

Rise Time

(ms)

A 22 000 18 700 25 300 660 .53 3300 .106

B 30 000 25 500 34 500 900 .39 4500 .078

C 40 000 34 000 46 000 1200 .29 6000 .058

D 52 500 44 625 60 375 1575 .22 7875 .044

E 70 000 59 500 80 500 2100 .17 10 500 .033

F 93 000 79 050 106 950 2790 .13 13 950 .025

G 124 000 105 400 142 600 3720 .09 18 600 .018

H 165 000 140 250 189 750 4950 .07 24 750 .014

I 225 000 191 250 258 750 6750 .05 33 750 .010

J 300 000 255 000 345 000 9000 .04 45 000 .008

K 400 000 340 000 460 000 12 000 .03 60 000 .006

L 560 000 476 000 644 000 16 800 .02 84 000 .004

See notes at end of Table 3-1C.

3-3

7/31/2019 IRIG_106_2009



TABLE 3-1C. PROPORTIONAL-BANDWIDTH FM SUBCARRIER CHANNELS

30% CHANNELS

Channel

Center

Frequencies

(Hz)

Lower

DeviationLimit(Hz)

Upper

DeviationLimit(Hz)

Nominal

FrequencyResponse

(Hz)

Nominal

Rise Time

(ms)

Maximum

FrequencyResponse

(Hz)

Minimum

Rise Time

(ms)

AA 22 00 15 400 28 600 1320 .265 6600 .053

BB 30 000 21 000 39 000 1800 .194 9000 .038

CC 40 000 28 000 52 000 2400 .146 12 000 .029

DD 52 500 36 750 68 250 3150 .111 15 750 .022

EE 70 000 49 000 91 000 4200 .083 21 000 .016

FF 93 000 65 100 120 900 5580 .063 27 900 .012

GG 124 000 86 800 161 200 7440 .047 37 200 .009

HH 165 000 115 500 214 500 9900 .035 49 500 .007

II 225 000 157 500 292 500 13 500 .026 67 500 .005

JJ 300 000 210 000 390 000 18 000 .019 90 000 .004

KK 400 000 280 000 520 000 24 000 .015 120 000 .003

LL 560 000 392 000 728 000 33 600 .010 168 000 .002

Notes:

1. Round off to nearest Hz.

2. The indicated maximum data frequency response and minimum rise time is based on themaximum theoretical response that can be obtained in a bandwidth between the upper and lower

frequency limits specified for the channels. See Appendix B, paragraph 3.0 for determining

possible accuracy versus response tradeoffs.

3. Channels A through L may be used by omitting adjacent lettered and numbered channels.

Channels 13 and A may be used together with some increase in adjacent channel interference.

4. Channels AA through LL may be used by omitting every four adjacent double lettered and lettered

channels and every three adjacent numbered channels. Channels AA through LL may be used by

omitting every three adjacent double lettered and lettered channels and every two adjacent numbered

channels with some increase in adjacent channel interference.

3-4

7/31/2019 IRIG_106_2009



3-5

3.3.2 Constant-Bandwidth FM Subcarrier Channel Characteristics. Table 3-2 lists the standardconstant-bandwidth FM subcarrier channels. The letters A, B, C, D, E, F, G, and H identify the

channels for use with maximum subcarrier deviations of ±2, ±4, ±8, ±16, ±32, ±64, ±128, and

±256 kHz, along with maximum frequency responses of 2, 4, 8, 16, 32, 64, 128, and 256 kHz.The channels shall be used within the limits of maximum subcarrier deviation. See Appendix B

for expected performance tradeoffs at selected combinations of deviation and modulatingfrequencies.

3.4 Tape Speed Control and Flutter Compensation

Tape speed control and flutter compensation for FM/FM formats may be accomplished as

indicated in Appendix D, subparagraph 17.4 (Tape Speed and Flutter Compensation). The standard

reference frequency used shall be in accordance with the criteria in Table 3-3 when the referencesignal is mixed with data.

7/31/2019 IRIG_106_2009



TABLE 3-2. CONSTANT-BANDWIDTH FM SUBCARRIER CHA

Frequency Criteria \ Channels: A B C D E

Deviation Limits (kHz) ±2 ±4 ±8 ±16 ±32

Nominal Frequency Response (kHz) 0.4 0.8 1.6 3.2 6.4

Maximum Frequency Response (kHz) 2 4 8 16 32

Center Frequency (k

8 16 32 64 128

16 32 64 128 256

24 48 96 192 384

32 64 128 256 512

40 80 160 320 640

48 96 192 384 768

56 112 224 448 896 64 128 256 512 1024

72 144 288 576 1152

80 160 320 640 1280

88 176 352 704 1408

96 192 384 768 1536

104 208 416 832 1664

112 224 448 896 1792

120 240 480 960 1920

128 256 512 1024 2048

136 272 544 1088 2176

144 288 576 1152 2304152 304 608 1216 2432

160 320 640 1280 2560

168 336 672 1344 2688

Notes:

The constant-bandwidth channel designation shall be the

channel center frequency in kilohertz and the channel

letter indicating deviation limit; for example, 16A,

indicating f c = 16 kHz, deviation limit of ±2 kHz.

The indicated maximum frequency is based upon the

maximum theoretical response that can be obtained in a

bandwidth between deviation limits specified for the

channel. See discussion in Appendix B for determining

practical accuracy versus frequency response trade offs.

Prior to using a channel outside the shaded area, the user

should verify the availability of range assets to support

the demodulation of the channel selected. Very limitedsupport is available above 2 MHz.

176 352 704 1408 2816

3 - 6

7/31/2019 IRIG_106_2009



TABLE 3-3. REFERENCE SIGNAL USAGE

Reference Frequencies for Tape Speedand Flutter Compensation

Reference Frequency

(kHz ±0.01%)

960(1)

480(1)

240(1)

200

100

50

2512.5

6.25

3.125

Note: (1)These frequencies are for flutter compensation only and not for capstan servo

speed control. In addition, the 240 kHz reference signal may be used as a detranslation

frequency in a constant-bandwidth format.

If the reference signal is recorded on a separate tape track, any of the listed reference

frequencies may be used provided the requirements for compensation rate of change are

satisfied.

If the reference signal is mixed with the data signal, consideration must be given topossible problems with intermodulation sum and difference frequencies. Also, sufficient

guard band must be allowed between the reference frequency and any adjacent data

subcarrier.

**** END CHAPTER 3 ****

3-7

7/31/2019 IRIG_106_2009



CHAPTER 4

PULSE CODE MODULATION STANDARDS

TABLE OF CONTENTS

4.1 General .............................................................................................................. 4-14.2 Class Distinctions and Bit-Oriented Characteristics ......................................... 4-1

4.3 Fixed Formats.................................................................................................... 4-2

4.4 Format Change (Class II) .................................................................................. 4-64.5 Asynchronous Embedded Format (Class II) ..................................................... 4-7

4.6 Tagged Data Format (Class II) .......................................................................... 4-7

4.7 Time Words....................................................................................................... 4-84.8 Asynchronous Data Merge (Class II) .............................................................. 4-10

LIST OF FIGURES

Figure 4-1. PCM code definitions. ....................................................................................... 4-3

Figure 4-2. PCM frame structure. ........................................................................................ 4-5

Figure 4-3. 16 bit standardized time word format................................................................ 4-9Figure 4-4. Time word insertion into 12 bit PCM word size. .............................................. 4-9

Figure 4-5. Asynchronous word structure.......................................................................... 4-11

Figure 4-6 Overhead truth table. ....................................................................................... 4-11

7/31/2019 IRIG_106_2009



ii


7/31/2019 IRIG_106_2009



CHAPTER 4

PULSE CODE MODULATION STANDARDS

4.1 General

Pulse code modulation (PCM) data are transmitted as a serial bit stream of binary-codedtime-division multiplexed words. When PCM is transmitted, premodulation filtering shall be

used to confine the radiated RF spectrum in accordance with Appendix A. These standards

define pulse train structure and system design characteristics for the implementation of PCM

telemetry formats. Additional information and recommendations are provided in Appendix Cand in RCC Document 119, Telemetry Applications Handbook.

4.2 Class Distinctions and Bit-Oriented Characteristics

The PCM formats are divided into two classes for reference. Serial bit streamcharacteristics are described below prior to frame and word oriented definitions.

4.2.1 Class I and Class II Distinctions. Two classes of PCM formats are covered in this chapter:

the basic, simpler types are class I, and the more complex applications are class II. The use of anyclass II technique requires concurrence of the range involved. All formats with characteristics

described in these standards are class I except those identified as class II. The following are

examples of class II characteristics:

a. bit rates greater than 10 megabits per second (see subparagraph 4.2.2.3)

b. word lengths in excess of 32 bits (subparagraph 4.3.1.1)

c. fragmented words (subparagraph 4.3.1.2)

d. more than 8192 bits or 1024 words per minor frame (subparagraph 4.3.2.1.1)

e. uneven spacing, not within the definition of subcommutation (subparagraph 4.3.2.3)or supercommutation (subparagraph 4.3.2.4)

f. format changes (paragraph 4.4)

g. asynchronous embedded formats (paragraph 4.5)

h. tagged data formats (paragraph 4.6)

i. formats with data content other than unsigned straight binary, discretes, or

complement arithmetic representation for negative numbers such as floating point

variables, binary-coded decimal, and gain-and-value j. asynchronous data transmission (paragraph 4.8)

k. merger of multiple format types (such as those specified in Chapter 8)

4-1

7/31/2019 IRIG_106_2009



The use of fixed frame formats has been a common practice but doesnot fit all requirements. A verification of range capabilities should be

made prior to incorporation of class II features into a telemetry system.

4.2.2 Bit-Oriented Definitions and Requirements. Definitions and requirements relating toserial PCM bit streams are described next.

4.2.2.1 Binary Bit Representation. The following code conventions for representing serial

binary ones and zeros are the only permissible representations. Graphic and written descriptions

of these conventions are shown in Figure 4-1. Only one convention shall be used within a singlePCM bit stream. If Randomized NRZ-L (RNRZ-L) is transmitted, it shall use the 15-bit

regeneration pattern as described in Appendix D.

NRZ-L Bi-L NRZ-M Bi-M NRZ-S Bi-S

4.2.2.2 Serial Bit Stream Transitions. The transmitted or recorded bit stream shall be

continuous and shall contain sufficient transitions to ensure bit acquisition and continued bit

synchronization, taking into account the binary representation chosen. (See recommendation in

paragraph 1.3, Appendix C.)

4.2.2.3 Bit Rate. The RF and recording limits, defined in Chapters 2 and 6, should be

considered when determining maximum bit rates. The minimum bit rate shall be 10 bps. Bitrates greater than 10 Mbps are class II.

4.2.2.4 Bit Rate Accuracy and Stability. During any period of desired data, the bit rate shallnot differ from the specified nominal bit rate by more than 0.1 percent of the nominal rate.

4.2.2.5 Bit Jitter. The bit jitter shall not exceed ±0.l of a bit interval referenced to the expectedtransition time with no jitter. The expected transition time shall be based on the measured

average bit period as determined during the immediately preceding 1000 bits.

4.3 Fixed Formats

Characteristics of fixed formats are described below. Fixed formats do not havechanges during transmission with regard to frame structure, word length or location,

commutation sequence, sample interval, or measurement list.

4.3.1 Word-Oriented Definitions and Requirements. The following definitions and

requirements are addressed to word characteristics.

4.3.1.1 Word Length (Class I and II). Individual words may vary in length from 4 bits to notmore than 32 bits in class I and not more than 64 bits in class II.

4-2

7/31/2019 IRIG_106_2009



4 -3

Figure 4-1. PCM code definitions.

Code Logic Waveform

Levels

Code Waveforms

1 0 1 1 0 0 0 1 1 0 1 0Non Return to Z

NRZ-L “ONE” is repre

“ZERO” is repr

Non Return to Z

NRZ-M “ONE” is repr

“ZERO” is repr

Non Return to Z

NRZ-S “ONE” is repre

“ZERO” is rep

Bi-Phase - Leve

Bi-L “ONE” is reprtransition to the “ZE

“ZERO” is rep

the “ONE” levelBi-Phase - Mark

Bi-M “ONE” is repr

of the bit period

“ZERO” is rep

the bit period

Bi-Phase - Spac

Bi-S “ONE” is reprthe bit period

“ZERO” is rep

beginning of the bit

Notes: (1) The Bi codes may be derived from the corresponding NRZ codes by inverting the level for the last half of each bit inte

1

0

1

0

1

0

1

0

1

0

1

0

7/31/2019 IRIG_106_2009



4.3.1.2 Fragmented Words (Class II). A fragmented word is defined as a word divided intono more than eight segments and placed in various locations within a minor frame. The

locations need not be adjacent. All word segments used to form a data word should be

constrained to the boundaries of a single minor frame. Fragmented synchronization words arenot allowed.

4.3.1.3 Bit Numbering. To provide consistent notation, the most significant bit in a wordshall be numbered "one." Less significant bits shall be numbered sequentially within the word.

4.3.1.4 Word Numbering. To provide consistent notation, the first word after the minor

frame synchronization pattern shall be numbered "one" (see Figure 4-2). Each subsequent wordshall be numbered sequentially within the minor frame. Numbering within a subframe (see

subparagraph 4.3.2.3.1) shall be "one" for the word in the same minor frame as the initial counter

value for subframe synchronization and sequentially thereafter. Notations of W and S shallmean the W word position in the minor frame and S word position in the subframe.

4.3.2 Frame Structure. The PCM data shall be formatted into fixed length frames asdefined in these sections regarding frame structure and in Figure 4-2. Frames shall contain a

fixed number of equal duration bit intervals.

4.3.2.1 Minor Frame. The minor frame is defined as the data structure in time sequence fromthe beginning of a minor frame synchronization pattern to the beginning of the next minor frame

synchronization pattern.

4.3.2.1.1 Minor Frame Length (Class I and II). The minor frame length is the number of bit

intervals from the beginning of the frame synchronization pattern to the beginning of the nextsynchronization pattern. The maximum length of a minor frame shall exceed neither 8192 bits

nor 1024 words in class I and shall not exceed 16 384 bits in class II.

4.3.2.1.2 Minor Frame Composition. The minor frame shall contain the minor frame

synchronization pattern, data words, and subframe synchronization words, if used. Words of

different length may be multiplexed in a single minor frame. The length of a word in anyidentified word position within a minor frame shall be constant. Other words such as frame

format identifiers may be needed within class II formats (see paragraph 4.4).

4.3.2.1.3 Minor Frame Synchronization. The minor frame synchronization information shallconsist of a fixed digital word not longer than 33 consecutive bits and not shorter than 16 bits.

The minor frame synchronization pattern is always considered as one word, regardless of its

length. Recommended synchronization patterns are given in Table C-1, Appendix C.

4.3.2.1.4 Transmitted Frame Counter. The frame counter provides a natural binary count

corresponding to the minor frame number in which the frame count word appears. It isrecommended that such a counter be included in all minor frames whether class I or class II and

is especially desirable in class II formats to assist with data processing. The frame counter

should be of nominal format word length and reset to start up-counting again after reaching

4-4

7/31/2019 IRIG_106_2009



maximum value. In formats where subcommutation is present, the subframe ID counter mayserve as the frame counter.

Figure 4-2. PCM frame structure.

MINOR FRAME SYNC 1 2 (W,1) N-1

MAJOR FRAME

(W,S)

MINOR FRAME SYNC 1 2 (W,Z) N-1

MINOR FRAME LENGTH “N” WORDS OR “B” BITSMAX LENGTH

CLASS I - 8 192 BITS OR 1024 WORDSCLASS II - 16 384 BITS

S U B F R A M E O F “ Z ” W O R D S

BY DEFINITION A MAJOR FRAME CONTAINS N*Z WORDS OR B*Z BITS

“Z” = THE NUMBER OF WORDS IN LONGEST SUBFRAME (MAX. 256).

“N” = THE NUMBER OF WORDS IN MINOR FRAME.

“B” = THE NUMBER OF BITS IN MINOR FRAME.

MINOR FRAME SYNC IS CONSIDERED ONE WORD, REGARDLESS OF LENGTH.

“W” IS WORD POSITION IN THE MINOR FRAME. “S” IS WORD POSITION IN THE SUBFRAME.

4-5

7/31/2019 IRIG_106_2009



4.3.2.2 Major Frame. A major frame contains the number of minor frames required toinclude one sample of every parameter in the format.

4.3.2.2.1 Major Frame Length. Major frame length is defined as minor frame length (N wordsor B bits) multiplied by the number of minor frames (Z) in the major frame. The maximum

number of minor frames per major frame shall not exceed 256.

4.3.2.2.2 Minor Frame Numbering. To provide consistent notation, the first minor frame in a

major frame shall be numbered "one." Each subsequent minor frame shall be numbered

sequentially within the major frame.

4.3.2.3 Subcommutation. Subcommutation is defined as a sampling of parameters at

submultiple rates (1/D) of the minor frame rate where the depth of a subframe, D, is an integer in

the range of 2 to Z.

4.3.2.3.1 Subframe. Subframe is defined as one cycle of the parameters from a subcommutated

minor frame word position. The depth, D, of a subframe is the number of minor frames in onecycle before repetition.

4.3.2.3.2 Subframe Synchronization Method. The standard method for subframe

synchronization is to use a "subframe ID counter," a binary counter which counts sequentially upor down at the minor frame rate. Typically, only one subframe ID counter is used in a PCM

format; however, more than one counter may be used if needed. This paragraph assumes the use

of one subframe ID counter. The subframe ID counter shall be located in a fixed position in eachand every minor frame. The counter should start with the minimum counter value when

counting up or the maximum counter value when counting down. The counter should also beleft or right justified in a word position. The start of a major frame shall coincide with the initial

count for the deepest subframe.

4.3.2.4 Supercommutation. Supercommutation ("supercom") is defined as time-division-

multiplex sampling at a rate that is a multiple of the minor frame rate. Supercommutation (on a

minor frame) provides multiple samples of the same parameter in each minor frame. "Supercomon a subframe" is defined as time-division-multiplex sampling at a rate that is a multiple of the

subframe rate and provides multiple samples of the same parameter within a subframe. For class

I, supercommutated samples shall be evenly spaced. For class II, supercommutated samples

should be as evenly spaced as practical.

4.4 Format Change (Class II)

Format change is defined as change with regard to frame structure, word length orlocation, commutation sequence, sample interval, or change in measurement list. Formatchanges shall occur only on minor frame boundaries. Bit synchronization shall be maintained

and fill bits used instead of intentional dead periods. Format changes are inherently disruptive to

test data processing; fixed format methods are preferred. Format change methods shall conform

to the characteristics described in the following sections.

4-6

7/31/2019 IRIG_106_2009



4.4.1 Frame Format Identification. A frame format identifier (FFI) is a word that shalluniquely identify a single format. In formats where change is required, the frame format

identifier shall be placed in every minor frame. The format identifier shall be the same length as

(or multiples of) the most common word length in the format and shall occur in a fixed positionin the minor frame. The FFI shall identify the format applicable to the current minor frame.

Frame synchronization pattern, FFI location, bit rate, and binary bit representation code shall notbe changed. The FFI shall be constructed such that a single bit error cannot produce anothervalid FFI. The number of unique formats indicated shall not exceed 16.

4.4.2 Format Change Implementation Methods. The following subparagraphs describe

format change implementation methods.

4.4.2.1 Measurement List Change. This method of format change consists of a modification in

data content only and not format structure.

4.4.2.2 Format Structure Change. Defined as a format change where there is a departure in

frame structure and not just data content.

4.5 Asynchronous Embedded Format (Class II)

Defined as a secondary data stream asynchronously embedded into a host major frame

in a manner that does not allow predicting the location of embedded synchronization information

based only on host format timing. The embedded frame segments shall be inserted as an integralnumber of words in every host minor frame. In this combined format, specific word positions in

the host minor frame shall be dedicated to the embedded asynchronous format. No more than

two asynchronous embedded formats are permitted.

4.6 Tagged Data Format (Class II)

Defined as a fixed frame length format having no applicable subframe or major frame

definitions and characterized as a stream of data words, or blocks of words, with associatedidentifiers (tags). These formats consist of frame synchronization patterns, identifiers, data

words, and fill words as required.

4.6.1 Alternating Tag and Data. This tagged data format consists of frames containing tag

words alternating in time sequence with data words or blocks of words identified by the tags.

4.6.2 Bus Data, Military Standard (MIL-STD) 1553.1 The preferred method of telemetering

MIL-STD 1553 information is for the information to be restructured to conform to Class I

methods. If not restructured, telemetered MIL-STD 1553 data shall conform to the Chapter 8standard.

4.6.3 Bus Data, ARINC 429.2 The preferred method of telemetering ARINC 429 information

is for the information to be restructured to conform to Class I methods. If not restructured,

1 Defined in MIL-HDBK-1553A(2), 1995, Multiplex Applications Handbook.2 Defined in ARINC Specification 429P1, 429P2, and 429P3.

4-7

7/31/2019 IRIG_106_2009



telemetered ARINC 429 data shall be consistent with the Aeronautical Radio Inc. specificationof ARINC 429 bus data.

4.7 Time Words

The following paragraphs describe the formatting of time words within a PCM stream. A16-bit standardized time word format and a method to insert time words into PCM word sizesother than 16-bits are described.

4.7.1 In 16-bit standardized time word format, there shall be three words dedicated toproviding timing information. These words are designated high order time, low order time, and

microsecond time. High and low order time words shall be binary or binary coded decimal

(BCD) weighted, and microsecond words shall be binary weighted. Time word constructionexamples are shown in Figure 4-3 and Figure 4-4.

4.7.2 The microsecond time word shall have a resolution of 1 microsecond; that is, the leastsignificant bit, bit 16, has a value of 0.000001 second. This word shall increment until it attains

a value of 10 milliseconds at which time it will reset to zero. Thus the maximum value of the

counter is 9999 (decimal).

4.7.3 The low order time word shall have a resolution of 10 milliseconds; that is, the least

significant bit, bit 16, of the low order time word shall have a value of 0.01 second.

4.7.4 The high order time word shall have a resolution of 655.36 seconds when binary

weighted; that is, the least significant bit, bit 16, has a value of 655.36 seconds. When BCD

weighted, the least significant bit, bit 16, of the high order time word shall have a value of oneminute. For BCD, the days field shall contain the three least significant characters of the BCD

Julian date.

4.7.5 It is recommended that high, low, and microsecond time words precede the first data

word in the minor frame. The time word order shall be high order time word, followed by loworder time word, followed by microsecond time word. Microsecond time words may be used to

tag individual data words, but care shall be taken that high order and low order time words be

inserted at a rate necessary to resolve time ambiguities.

4.7.6 Time word insertion into PCM word sizes other than 16 bits shall be as follows: high

order, low order, and microsecond time words shall be inserted into PCM words with time word

bits occupying contiguous bit locations in the PCM word. The time word shall occupycontiguous PCM data words until the time word is contained in the PCM stream. If the time

word size is not an integer multiple of the PCM word size and there are unused bits in the PCMword, the remaining unused bits in the last PCM word that contains the time word shall be fillbits with value 0. Figure 4-4 illustrates the insertion of time words into a PCM stream with word

size of 12 bits.

4-8

7/31/2019 IRIG_106_2009



HIGH ORDER TIME

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

1 DAY 10 HR 1 HR 10 MIN 1 MIN

655.36 SEC

LOW ORDER TIME

(BCD Weighting)(Binary Weighting)

0

10 SEC 1 SEC 0.1 SEC 0.01 SEC

0.01 SEC

MICROSECOND TIME

(BCD Weighting)

(Binary Weighting)

0 0(Binary Weighting)1 MICROSECOND

Figure 4-3. 16 bit standardized time word format.

HIGH ORDER TIME

PCM WORD N PCM WORD N+1

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 24

ALL ZERO FILLER

1 DAY 10 HR 1 HR 10 MIN 1 MIN

655.36 SEC

LOW ORDER TIME

PCM WORD N+2 PCM WORD N+3

(BCD)(Binary)

0 ALL ZERO FILLER

10 SEC 1 SEC 0.1 SEC 0.01 SEC

0.01 SECMICROSECOND TIME

PCM WORD N+4 PCM WORD N+5

(BCD)

(Binary)

0 0 ALL ZERO FILLER

(BinaryWeighting) 1 MICROSECOND

Figure 4-4. Time word insertion into 12 bit PCM word size.

4-9

7/31/2019 IRIG_106_2009



4.8 Asynchronous Data Merge (Class II)

Asynchronous data is defined as an external sequential data stream (consisting of data

bits, associated overhead, and optional parity, all at an autonomous update rate) which is a

candidate for insertion into a primary or “host” PCM format. Common examples are RS-232serial and IEEE-488 parallel messages. Each source of such data shall use fixed word positionsin the host format. This section does not apply to secondary PCM formats which are to be

embedded as described in paragraph 4.5. Merger shall comply with subparagraph 4.2.2 and the

following conventions.

4.8.1 PCM Data Word Format. Figure 4-5 illustrates the host PCM format word containing a

merged asynchronous data word and associated overhead which is referred to as an“asynchronous word structure.” The data may be inserted in any length PCM word that will

accommodate the required bits. Asynchronous data shall not be placed in fragmented words.

Multiple host PCM format words, if used, shall be contiguous.

4.8.2 Insertion Process. The asynchronous word structure shall contain the information from

the asynchronous message partitioned into two fields, data and overhead, as shown in figure 4-5.

The asynchronous message is inserted into the asynchronous word structure with the followingbit orientations. The most significant data bit (MSB) through least significant data bit (LSB) and

parity (if used) of the message are denoted as D1 (MSB) through Di and will be inserted into

structure bits B1 (MSB) through Bi. The next two structure bits, B(i+1) and B(i+2) are reservedfor the stale and overflow flags generated by the host encoder. All remaining overhead (message

and host encoder generated) D(i+3) through Dn (LSB), will be inserted into structure bits B(i+3)

through Bn (LSB).

4.8.2.1 Transmission Overhead. All transmission overhead not required for data reconstructionshall be removed.

4.8.2.2 Parity Bit. Transmission of a parity bit is optional. If it is transmitted, it shall be at theend of the data field (see Figure 4-5) adjacent to the LSB of the data.

4.8.2.3 Data Bits. The data bits shall be inserted into the PCM word with the most significant bit of

the asynchronous data aligned with the most significant bit of the PCM word.

4-10

7/31/2019 IRIG_106_2009



4-11

Figure 4-5. Asynchronous word structure.

(MSB) (LSB)

B1 B2 • • • Bi B(i+1) B(i+2) B(i+3) • • • Bn

D1 D2 • • • Di D(i+1) D(i+2) D(i+3) • • • Dn

DATA (MSB) - DATA (LSB)

PLUS OPTIONAL PARITY;

D1 = DATA (MSB)

Di = DATA (LSB) FOR

NO PARITY

Di = PARITY WHEN

USED

STALE OVER

FLOW

ALL REMAINING

OVERHEAD

Dn = (LSB)

DATA FIELD OVERHEAD FIELD

4.8.2.4 Stale Data Bit. A “stale data bit” flag shall be generated each time a new data value isinserted into the PCM stream. The flag shall be transmitted with the associated data. The flag

bit shall be placed in the next less significant bit location following the LSB of the data. If newdata is not ready for transmission by the time the PCM word must be sent again, either the old

data or alternating one/zero fill shall be sent and the flag set. Stale data shall be indicated by a

binary “one” (see Figure 4-6).

STALE BIT OVERFLOW BIT

0 0 FRESH DATA

0 1 DATA OVERFLOW

1 0 STALE DATA

1 1 USER DEFINED

Figure 4-6 Overhead truth table.

4.8.2.5 Overflow Bit. An “overflow bit” flag shall be generated to indicate an abnormal condition inwhich data may be lost. The overflow bit shall be placed in the next less significant data bit location

following the stale bit flag. An overflow bit at a binary “one” indicates that a data discontinuity exists

between the current data word and the previous data word (see Figure 4-6 above).

4.8.2.6 Insertion Rate. The asynchronous word structure shall be inserted into the host PCM

word at a rate to avoid data loss in the PCM stream.

**** END OF CHAPTER 4 ****

7/31/2019 IRIG_106_2009



CHAPTER 5

DIGITIZED AUDIO TELEMETRY STANDARD

Paragraph Subject .......................................................................................................... Page

5.1 General............................................................................................................. 5-15.2 Definitions ....................................................................................................... 5-1

5.3 Signal Source ................................................................................................... 5-1

5.4 Encoding/Decoding Technique........................................................................ 5-15.5 CVSD Encoder Output Bit Rate (CVSD Bit Rate).......................................... 5-2

5.6 CVSD Word Structure..................................................................................... 5-2

5.7 CVSD Word Sample Rate ............................................................................... 5-35.8 CVSD Bit Rate Determination ........................................................................ 5-3

LIST OF FIGURES

Figure 5-1. Insertion of CVSD encoded audio into a PCM stream.................................... 5-2

7/31/2019 IRIG_106_2009



ii


7/31/2019 IRIG_106_2009



CHAPTER 5

DIGITIZED AUDIO TELEMETRY STANDARD

5.1 General

This chapter defines continuous variable slope delta (CVSD) modulation as the standard

for digitizing audio and addresses the method of inserting CVSD encoded audio into a PCMstream. Additional information and recommendations are provided in Appendix F, Continuous

Variable Slope Delta Modulation. Appendix F was extracted from the applicable sections of

MIL-STD-188-113.

5.2 Definitions

For the purpose of this standard, the following definitions apply.

5.2.1 Band-Limited Audio. An audio signal (typically consisting of voice, tones, and sounds)that is limited to a subset of the audio spectrum. For most aircraft audio applications, the

spectrum between 100 and 2300 hertz is adequate.

5.2.2 Continuous Variable Slope Delta Modulation. The CVSD modulation is a method of digitizing a band-limited audio signal. The CVSD modulator is, in essence, a 1-bit analog-to-

digital converter. The output of this 1-bit encoder is a serial bit stream, where each bit represents

an incremental increase or decrease in signal amplitude and is determined as a function of recentsample history.

5.3 Signal Source

The signal to be encoded shall be a band-limited audio signal. The source of this signalmay be varied. Some examples are microphones, communication systems, and tones fromwarning systems. This standard applies to audio signals only.

5.4 Encoding/Decoding Technique

The technique to encode and decode the band-limited audio signal is CVSD modulation.This technique is to be implemented in accordance with Appendix F.

A CVSD converter consists of an encoder-decoder pair. The decoder is connected in a

feedback path. The encoder receives a band-limited audio signal and compares it to the analog

output of the decoder. The result of the comparison is a serial string of "ones" and "zeros." Eachbit indicates that the band-limited audio sample's amplitude is above or below the decoded

signal. When a run of three identical bits is encountered, the slope of the generated analogapproximation is increased in its respective direction until the identical string of bits is broken.

The CVSD decoder performs the inverse operation of the encoder and regenerates the audio

signal.

5-1

7/31/2019 IRIG_106_2009



A qualitative test of CVSD with a tactical aircraft intercom system(ICS) yielded the following results: (1) intelligible, robotic

sounding audio at 12 kilobits/second; (2) good quality audio at 16

kilobits/second; and (3) audio quality did not significantly improveas the bit rate was increased above 32 kilobits/second.

5.5 CVSD Encoder Output Bit Rate (CVSD Bit Rate)

The CVSD bit rate for encoding the band-limited audio signal is a function of the desired

audio quality and the PCM format characteristics. The minimum and maximum CVSD bit rates

will not be specified.

Appendix F contains performance criteria for the CVSD encoder and decoder whenoperated at 16 or 32 kilobits/second.

5.6 CVSD Word Structure

The digitized audio signal from the CVSD encoder's serial output shall be inserted into

the PCM stream as shown in Figure 5-1. The most significant bit (MSB) shall be the most stalesample (first in). The least significant bit (LSB) shall be the most recent sample (last in).

MOST STALE

SAMPLE

CVSD SERIAL OUTPUT STREAM MOST RECENT

SAMPLE

S-2 S-1 S S+1 • • • S+(n-1) S+n S+(n+1)

PCM DATA WORD S S+1 • • • S+(n-1) PCM DATA WORDMSB LSB

Figure 5-1. Insertion of CVSD encoded audio into a PCM stream.

5-2

7/31/2019 IRIG_106_2009



5.7 CVSD Word Sample Rate

The CVSD word sample rate is dependent on the minimum desired CVSD bit rate, the

PCM word length, and the PCM word sample rate. Once the CVSD word sample rate is

determined, the actual CVSD bit rate can be calculated. The decoder must be run at the sameCVSD bit rate as the encoder.

Because of the nature of CVSD encoding, over and under sampling of the

CVSD output will have unpredictable results.

To simplify the reconstruction of the audio signal and minimize

all encoding/decoding delays, it is STRONGLY recommended thatthe digitized audio words be inserted in the PCM stream at evenly spaced

intervals.

5.8 CVSD Bit Rate Determination

The following discussion provides a procedure for determining the CVSD bit rate based on

the desired minimum CVSD bit rate and information given in the host PCM format. Note that this

procedure assumes the CVSD words are inserted in a class I PCM format with constant wordwidths and are not subcommutated. The CVSD bit rate can be obtained by multiplying the minor

frame rate by the number of times the CVSD words appear in the minor frame by the word width

used for the CVSD words in the minor frame. This relationship is expressed in equation (5-1).

CVSD BIT RATE = MINOR FRAME RATE • #CVSD WORDS PER MINOR FRAME • WORD WIDTH (5-1)

Knowing the details on the host PCM format, equation (5-1) contains two unknowns:CVSD BIT RATE and #CVSD WORDS PER MINOR FRAME. One of these unknowns must

be chosen by the user, then the other one can be calculated. The recommended procedure is to

choose the desired (target value) CVSD bit rate and solve equation (5-1) for #CVSD WORDSPER MINOR FRAME. This relationship is expressed in equation (5-2).

#CVSD WORDS PER MINOR FRAME calculated = DESIRED CVSD BIT RATE (5-2)MINOR FRAME RATE • WORD WIDTH

Next, round up (if required) the result of equation (5-2) to the nearest integer.To satisfy the evenly spaced recommendation, round up (if required) to the nearest integer that

divides evenly into the number of PCM words per minor frame.

Finally, for either case, substitute the result of equation (5-2) back into equation (5-1) to

determine the actual CVSD bit rate. To illustrate this procedure, consider the following

numerical example for determining the CVSD bit rate. An existing PCM format has thecharacteristics:

5-3

7/31/2019 IRIG_106_2009



5-4

Bit rate = 192 000 bits/secondWord width = 12 bits/word

Minor frame rate = 100 frames/second

Words/ minor frame = 160 words/minor frame

To insert a serial CVSD bit stream with a desired (target value), CVSD bit rate of 16 000bits/second will require the following procedure. Based on the information given, use equation(5-2) to calculate the #CVSD WORDS PER MINOR FRAME.

#CVSD WORDS PER MINOR FRAMEDESIRED CVSD BIT RATE

MINOR FRAME RATE WORD WIDTH=CALCULATED

#CVSD WORDS PER MINOR FRAME16 000 ( )

100 ( ) 12 ( )=CALCULATED

bits

frames bits word

sec

sec

#CVSD WORDS PER MINOR FRAMECALCULATED = 13.3 (words/frame)

Rounding up the #CVSD WORDS PER MINOR FRAME to the nearest integeryields 14. In this example, there are 160 PCM words in the minor frame. If the user needs to

satisfy the evenly spaced criteria, then by inspection, the #CVSD WORDS PER MINOR

FRAME will be rounded up to 16. For comparison, both cases will be substituted into equation(5-1) to yield the actual CVSD bit rate.

CASE 1: (unevenly spaced CVSD samples, NOT RECOMMENDED)

#CVSD WORDS PER MINOR FRAME 14 (=CALCULATED words frame)

CVSD BIT RATE = MINOR FRAME RATE • #CVSD WORDS / MINOR FRAME • WORD WIDTH

CVSD BIT RATE 100 ( 14 ( 12 (=ACTUAL frames words frame bits word sec) ) )

CVSD BIT RATE 16 800 (=ACTUAL bits sec)

CASE 2: (evenly spaced samples, RECOMMENDED)

# CVSD WORDS PER MINOR FRAME 16 (=CALCULATED words frame)

CVSD BIT RATE = MINOR FRAME RATE #CVSD WORDS PER MINOR FRAME WORD WIDTH

CVSD BIT RATE 100 ( 16 ( 12 (ACTUAL = frames words frame bits word sec) ) )

)(bits/sec 00219RATEBITCVSD =ACTUAL


7/31/2019 IRIG_106_2009



CHAPTER 6

DIGITAL CASSETTE HELICAL SCAN RECORDER/REPRODUCER,

MULTIPLEXER/DEMULTIPLEXER, TAPE CASSETTE, AND RECORDER

CONTROL AND COMMAND MNEMONICS STANDARDS

TABLE OF CONTENTS

LIST OF FIGURES ......................................................................................................................... i

LIST OF TABLES .......................................................................................................................... ii

ACRONYMS ........................................................................................................................... iii

Paragraph Subject ....................................................................................................... Page

6.1 Introduction ...................................................................................................... 6-16.2 Definitions ....................................................................................................... 6-2

6.3 19-mm Digital Cassette Helical Scan Recording Standards ............................ 6-8

6.4 Multiplex/Demultiplex (MUX/DEMUX) Standard for Multiple Data

Channel Recording on 19-MM Digital Cassette Helical ScanRecorder/Reproducer Systems ....................................................................... 6-10

6.5 Submultiplex/Demultiplex Standards for Multiple Data Channels on a

Primary Digital Multiplex/Demultiplex Channel .......................................... 6-146.6 1/2 Inch Digital Cassette (S-VHS) Helical Scan Recording Standards ......... 6-18

6.7 Multiplex/Demultiplex (MUX/DEMUX) Standards for Multiple Data

Channel Recording on ½ Inch Digital Cassette (S-VHS) Helical ScanRecorder/Reproducer Systems. ...................................................................... 6-35

6.8 Recorder Command and Control Mnemonics (CCM) ................................... 6-41

LIST OF FIGURES

Figure 6-1. Head and head segment mechanical parameters. ............................................. 6-8Figure 6-2. Location and dimensions of recorded tracks. .................................................. 6-9

Figure 6-3. ADARIO block format. ................................................................................. 6-11

Figure 6-4. ADARIO data format. .................................................................................... 6-13Figure 6-5. Submux data format. ...................................................................................... 6-17

Figure 6-6. Helical track dimensions, B format. .............................................................. 6-19

Figure 6-7. Helical track dimensions, E format. ............................................................... 6-20

Figure 6-8. Recorded tracks on tape, B format. ................................................................ 6-23Figure 6-9. Tape cartridge layout. .................................................................................... 6-24

Figure 6-10. Helical track format. ...................................................................................... 6-27

Figure 6-11. Typical VLDS data path electronics block diagram. ..................................... 6-29Figure 6-12. Interleave buffer architectures. ...................................................................... 6-30

Figure 6-13. The steps of the build process. ....................................................................... 6-36

7/31/2019 IRIG_106_2009



LIST OF TABLES

Table 6-1. Record Location and Dimensions .................................................................... 6-9

Table 6-2. Tape Length and Nominal Play Record/ Reproduce Time at 240

Megabits/Second User Data Rate .................................................................. 6-10Table 6-3. ADARIO Format (FMT) Defined Field Restrictions .................................... 6-12Table 6-4. Physical Parameters ....................................................................................... 6-21

Table 6-5. Track and Data Sync: Word 0-Word 4 ......................................................... 6-27

Table 6-6. Track and Data Sync: Word 5 ....................................................................... 6-28Table 6-7. ECC - Interleave Buffer Addressing (32 mbps) ............................................ 6-31

Table 6-8. ECC - Interleave Buffer Addressing (64 mbps) ............................................ 6-31

Table 6-9. Tape - Interleave Buffer Addressing (32 mbps) ............................................ 6-32Table 6-10. Tape - Interleave Buffer Addressing (64 mbps) ............................................ 6-33

Table 6-11. Miscellaneous Bit Definitions ....................................................................... 6-34

Table 6-12. Scanlist Build Steps ....................................................................................... 6-37Table 6-13. Sample Armor Frame ..................................................................................... 6-38

Table 6-14. Time Code Word Format ............................................................................... 6-39

Table 6-15. Command Summary ...................................................................................... 6-43

Table 6-16. Command Error Codes .................................................................................. 6-44Table 6-17. Use of Status Bits ........................................................................................... 6-52

Table 6-18. Recorder States .............................................................................................. 6-59

Table 6-19. Command Validity Matrix ............................................................................. 6-64Table 6-20. Required Commands ...................................................................................... 6-65

ii

7/31/2019 IRIG_106_2009



ACRONYMS

ADARIO Analog/Digital/ Adaptable/Recorder Input/OutputAFVP Format Verification Program

ANSI American National Standards Institute

ARMOR asynchronous real-time multiplexer and output reconstructorBCD Binary-coded decimalBER Bit error rate

BOD beginning of data

BOF beginning of fileBOM beginning of media

BRC The block rate clock

CCM Command and Control MnemonicsCWDS Code word digital sum OR word digital sum

DSV Digital sum variation

ECC Error correcting codeECC error correction coding

ECL Emitter-Coupled Logic

EOD end of data

EOF end of fileEOM end of media

ftpmm flux transitions per millimeter

GF Galois fieldLBOT logical beginning of tape

LEOT logical end of tape

Mbps megabits per secondMML Magnetic Media Laboratory

MSB most significant bitMUX/DEMUX Multiplex/Demultiplex

PAR parallel

PBN Principal block numberPBOT physical beginning of tape

PCM Pulse-code modulation

PEOT physical end of tape

RS Reed-SolomonSI Systeme International d’ Unites

submux submultiplex

TTL Transistor–Transistor LogicUBE upper band edge

VLDS very large data store

iii

http://en.wikipedia.org/wiki/Modulation

http://en.wikipedia.org/wiki/Modulation

7/31/2019 IRIG_106_2009



iv


7/31/2019 IRIG_106_2009



CHAPTER 6

DIGITAL CASSETTE HELICAL SCAN RECORDER/REPRODUCER,

MULTIPLEXER/DEMULTIPLEXER, TAPE CASSETTE, AND RECORDER

CONTROL AND COMMAND MNEMONICS STANDARDS

6.1 Introduction

These standards define terminology for digital cassette helical scan (19-mm and ½ inch)

recording systems, along with the associated multiplexer/demultiplexer systems, digital tapecassettes, and recorder control and command mnemonics. Standards consistent with

compatibility in interchange transactions are delineated. While the standards may serve as a

guide in the procurement of magnetic tape recording equipment, they are not intended to beemployed as substitutes for purchase specifications. The American National Standards Institute

(ANSI) and the International Standards Organization have prepared other related standards (see

paragraph 1.0, appendix D).

United States (U.S.) engineering units are the original dimensions in these standards.

Conversions for U.S. engineering units (similar to British Imperial Units) to Systeme

International d’ Unites (SI) units have been done according to ANSI Z210.1-1976 (andInternational Standards Organization 370) Method A, except as noted.

Standard test methods for digital cassette helical scan recorder/reproducers andmultiplexer/demultiplexer systems are contained in RCC Document 118, Volume III, Test

Methods for Recorder/Reproducer Systems and Magnetic Tape.

The standards for longitudinal fixed-head recorder and reproducer systemshave been removed from this chapter and are now contained in Appendix

D, paragraphs 12.0 through 21.2. Standards for longitudinalinstrumentation magnetic tape previously contained in Chapter 7 can now

be found in Appendix D, paragraphs 22.0 through 27.11.

6-1

7/31/2019 IRIG_106_2009



6.2 Definitions

5/6 modulation code: A method of encoding whereby a 5-bit data group is converted to a 6-bitcode frame in accordance with a conversion table. Such coding is performed to control the

frequency content of the data stream.

Basic dimension: A dimension specified on a drawing as basic is a theoretical value used todescribe the exact size, shape, or location of a feature. It is used as the basis from which

permissible variations are established by tolerances on other dimensions.

Bias signal, high frequency: A high-frequency sinusoidal signal linearly added to the analog

data signal in direct recording to linearize the magnetic recording characteristic.

Bi-phase: A method of representing "one" or "zero" levels in PCM systems where a level

change is forced to occur in every bit period. In bi-phase recording, the bi-phase level (split-

phase) method is employed.

Bit error: In PCM systems, a bit error has occurred when the expected bit value is not present;

for example, a zero is present when a one is expected, or a one is present when a zero is

expected.

Bit error rate (BER): Number of bits in error in a predetermined number of bits transmitted or

recorded, for example, 1 in 106 or a BER of 10−6.

Bit packing density, linear: Number of bits recorded per inch or per millimeter of tape length.For serial PCM recording, the number of bits per unit length of a single track.

Bit slip: The increase or decrease in detected bit rate by one or more bits with respect to theactual bit rate.

Code frame: An ordered and contiguous set of bits (symbol) that results as a unit from the

process of modulation coding.

Code word digital sum (CWDS): Denotes the digital sum variation of one modulation codeframe (symbol).

Crossplay: Reproducing a previously recorded tape on a recorder and reproducer system otherthan that used to record the tape.

Crosstalk: Undesired signal energy appearing in a reproducer channel as a result of couplingfrom other channels.

Data azimuth (dynamic): The departure from the head segment gap azimuth angles (static)because of the dynamic interface between the heads and the moving tape.

6-2

7/31/2019 IRIG_106_2009



Data scatter: The distance between two parallel lines (as defined under gap scatter) in the planeof the tape, which contains all data transitions recorded simultaneously with the same head at the

same instant of time.

Data spacing: For interlaced head systems, the distance on tape between simultaneous events

recorded on odd and even heads.

Digital sum variation (DSV): Indicates the integral value that is counted from the beginning of

the modulation coded waveform, taking a high level as 1 and a low level as -1.

Direct Recording (ac Bias Recording): A magnetic recording technique employing a high-frequency bias signal that is linearly added to the data signal. The composite signal is then used

as the driving signal to the record-head segment. The bias signal, whose frequency is well above

the highest frequency that can be reproduced by the system, transforms the recording of the datasignal so that it is a more nearly linear process.

Double-density recording: Direct, FM, or PCM recording on magnetic tape at bandwidthsequal to those used in wide-band instrumentation recording, but at one-half the wide-band tape

speeds specified in IRIG standard 106-80 and earlier telemetry standards. Special record and

reproduce heads and high output tapes (see Chapter 7) are required for double-density recording.

Dropout: An instantaneous decrease in reproduced signal amplitude of a specified amplitude

and duration.

ECC code word: The group of symbols resulting from ECC encoding including the data

symbols and the check symbols appended.

Edge margin: The distance between the outside edge of the highest number track and the tape

edge (see Appendix D, D-7Aa).

Edge margin minimum: The minimum value of edge margin.

Error correcting code (ECC): A mathematical procedure yielding bits used for the detection

and correction of errors.

FM recording: Recording on magnetic tape using frequency-modulated record electronics toobtain response from dc to an upper specified frequency. The FM systems forfeit upper

bandwidth response of direct record systems to obtain low frequency and dc response not

available with direct recording.

Flux transition: A 180-degree change in the flux pattern of a magnetic medium brought about

by a reversal of poles within the medium.

Flux transition density: Number of flux transitions per inch or per millimeter of track length.

6-3

7/31/2019 IRIG_106_2009



Flutter: Undesired changes in the frequency of signals during the reproduction of a magnetictape produced by speed variations of the magnetic tape during recording or reproducing.

Gap azimuth: The angular deviation, in degrees of arc, of the recorded flux transitions on atrack from the line normal to the track centerline.

Gap length (physical): The dimension between leading and trailing edges of a record orreproduce head-segment gap measured along a line perpendicular to the leading and trailing

edges of the gap.

Gap scatter (record head): The distance between two parallel lines is defined in the followingsubparagraphs.

a. The two lines pass through the geometric centers of the trailing edges of the twooutermost head segment gaps within a record head. The geometric centers of the other

head segment gap trailing edges lie between the two parallel lines.

b. The two parallel lines lie in the plane of the tape and are perpendicular to the head

reference plane (see Appendix D, Figure D-7b)

Gap scatter (reproduce head): Defined the same as for record-head gap scatter except that the

reference points for reproduce heads are the geometric centers of the center lines of the headsegment gaps (Appendix D, Figure D-7c).

Guard band: The unrecorded space between two adjacent recorded tracks on the magnetic tape.

Head (record or reproduce): A group of individual head segments mounted in a stack.

Head designation: For interlaced heads, the first head of a record or reproduce pair over whichthe tape passes in the forward direction containing odd-numbered head segments and referred to

as the odd head. The second head containing even-numbered head segments is the even head.For non-interlaced heads (in-line heads), both odd- and even-numbered head segments are

contained within a single head.

Heads, in-line: A single record head and a single reproduce head are employed. Odd and even

record-head segment gaps are in-line in the record head. Odd and even reproduce-head segment

gaps are in-line in the reproduce head.

Head reference plane: The plane, which may be imaginary, is parallel to the reference edge of

the tape and perpendicular to the plane of the tape. For purposes of this definition, the tape shallbe considered as perfect (see Appendix D, Figure D-7b, and Figure D-7c).

Head segment, record or reproduce: A single transducer that records or reproduces one track

(see Appendix D, Figure D-7b).

Head segment gap azimuth (record or reproduce heads): The angle formed in the plane of

the tape between a line perpendicular to the head reference plane and a line parallel to the trailing

6-4

7/31/2019 IRIG_106_2009



edge of the record-head segment gap or parallel to the centerline of the reproduce-head segmentgap.

Head segment gap azimuth scatter: The angular deviations of the head segment gap azimuthangles within a head.

Head segment numbering: Numbering of a head segment corresponds to the track number onthe magnetic tape on which that head segment normally operates. For interlaced heads, the odd

head of a pair contains all odd-numbered segments, while the even head will contain all

even-numbered segments (see Appendix D, Figure D-7c). In-line heads will contain odd and

even segments in the same head stack.

Head spacing: For interlaced head systems, the distance between odd and even heads.

Head tilt: The angle between the plane tangent to the front surface of the head at the center line

of the head segment gaps and a line perpendicular to the head reference plane (see Appendix D,

Figure D-7b).

Heads, interlaced: Two record heads and two reproduce heads are employed. Head segments

for alternate tracks are in alternate heads.

Helical track: A diagonally positioned area on the tape along which a series of magnetic

transitions is recorded.

High-density digital recording: Recording of digital data on a magnetic medium resulting in a

flux transition density in excess of 590 transitions per millimeter (15 000 transitions per inch) pertrack.

Individual track data azimuth difference: Angular deviation of the data azimuth of anindividual odd or even recorded track from the data azimuth of other odd or even tracks. The

difficulty in making direct optical angular measurements requires this error to be expressed as a

loss of signal amplitude experienced when the tape is reproduced with an ideal reproducing head,whose gap is aligned to coincide with the data azimuth of all tracks in one head as compared to

the azimuth which produces maximum signal for an individual track (see Appendix D, and

Figure D-7b).

Interleaving: The systematic reordering of data so that originally adjacent ECC code word

symbols are separated, thus reducing the effect of burst errors on the error correcting capability.

Non-return-to-zero level: A binary method of representation for PCM signals where one is

represented by one level and zero is defined as the other level in a bi-level system.

Physical recording density: The number of recorded flux transitions per unit length of track,

for example, flux transitions per millimeter (ftpmm).

6-5

7/31/2019 IRIG_106_2009



Principal block: Denotes a group of helical tracks recorded on the tape in one complete rotationof the scanner.

Principal block number (PBN): A unique number assigned to and recorded in each principalblock.

Record level set frequency: Frequency of a sinusoidal signal used to establish the standardrecord level in direct- record systems. Normally, 10 percent of the upper band edge (UBE)

frequency.

Reference tape edge: When viewing a magnetic tape from the oxide surface side with theearlier recorded portion to the observer's right, the reference edge is the top edge of the tape (see

Appendix D, Figure D-7a).

Reference track location: Location of the centerline of track number 1 from the reference edge

of tape.

Scanner: The rotating assembly housing the helical heads around which the tape is applied

thereby accomplishing the recording of helical tracks on the tape.

Standard record level: For a magnetic tape recorder meeting IRIG standards and operating inthe direct record mode, the input signal level produces 1 percent third harmonic distortion of the

record level set frequency.

Tape skew: Motion of a magnetic tape past a head such that a line perpendicular to the tape

reference edge has an angular displacement (static or dynamic) from the head gap centerlines.

Tape speed, absolute: The tape speed during recording and reproducing. The peripheral

velocity of the capstan minus any tape slip, regardless of tape tension and environment.

Tape speed, effective: The tape speed modified by the effects on tape of operating conditions

such as tension, tape materials, thickness, temperature, and humidity. The effective tape speedshould be equal to the selected speed of the recorder, for example, 1524 mm/s (60 ips),

3048 mm/s (120 ips), regardless of operating conditions.

Tape speed errors: Errors are the departures of the effective speed from the selected tapespeed.

Track angle: The angular deviation, in degrees of arc, of the centerline of the recorded helicaltrack from the tape reference edge.

Track location: Location of the nth track centerline from the reference track centerline.

Track numbering: The reference track is designated as track number 1. Tracks are numbered

consecutively from the reference track downward when viewing the oxide surface of the tape

6-6

7/31/2019 IRIG_106_2009



with the earlier recorded portion of the tape to the observer's right (see Appendix D, andFigure D-7a).

Track spacing: Distance between adjacent track centerlines on a magnetic tape (seeAppendix D, and Figure D-7a).

Track width: The physical width of the common interface of the record-head segment at thegaps. This definition does not include the effects of fringing fields, which will tend to increase

the recorded track width by a small amount.

Volume label: A group of bits used to provide an identifying code for a tape cartridge

6-7

7/31/2019 IRIG_106_2009



6.3 19-mm Digital Cassette Helical Scan Recording Standards

These standards are for single-channel high-bit rate helical scan digital recorders using19 mm tape cassettes. Bit rates of less than 10 megabits per second to 256 megabits per second

or greater may be recorded and reproduced by equipment conforming to these standards.

Interchange parties must, however, determine the availability at a particular site of the equipmentrequired to meet particular data recording requirements. Compatibility between the recordingdevice and the expected playback equipment must also be considered. Figure 6-1 displays the

head and head segment mechanical parameters for a single-channel high-bit rate helical scan

digital recorder.

6.3.1 Track Format. The format recorded and reproduced by these systems shall be as specified in

American National Standard For Information Systems 19 mm Type ID-1 Recorded InstrumentationDigital Tape Format, ANSI INCITS 175-1999.1 Helical tracks employ azimuth recording wherein

the head gap angle with respect to the recorded track center line is 90° + 15° for one scan and

90° −15° for the adjacent scan. Figure 6-2 and Table 6-1 show details of the helical tracks and

auxiliary longitudinal tracks for control, timing, and annotation in the ID-1 format.

Figure 6-1. Head and head segment mechanical parameters.

1 Formerly ANSI -1990. Available from American National Standards Institute (webstore.ansi.org).

6-8

http://webstore.ansi.org/ansidocstore/default.asp

http://webstore.ansi.org/ansidocstore/default.asp

7/31/2019 IRIG_106_2009



TABLE 6-1. RECORD LOCATION AND DIMENSIONS

Dimensions Nominals

A TIME-CODE TRACK LOWER EDGE 0.2 mmB TIME-CODE TRACK UPPER EDGE 0.7 mm

C CONTROL TRACK LOWER EDGE 1.0 mm

D CONTROL TRACK UPPER EDGE 1.5 mm

E DATA-AREA LOWER EDGE 1.8 mm

F DATA-AREA WIDTH 16 mm

G ANNOTATION TRACK LOWER EDGE 18.1 mm

H ANNOTATION TRACK UPPER EDGE 18.8 mm

I HELICAL TRACK WIDTH 0.045 mm

J TRACK PITCH, BASIC 0.045 mm

N HELICAL TRACK TOTAL LENGTH 170 mm

P ANNOTATION/TIME-CODE HEAD LOCATION 118.7 mm

R SECTOR RECORDING TOLERANCE ±0.1 mm

T CONTROL TRACK SYNC TOLERANCE ±0.1 mm

P TRACK ANGLE, ARC-SINE (16/170) 5.4005º

W TAPE WIDTH 19.01 mm

Figure 6-2. Location and dimensions of recorded tracks.

6-9

7/31/2019 IRIG_106_2009



6.3.2 Magnetic Tape and Cassettes. The magnetic tape shall meet the requirements of Magnetic Media Laboratory (MML) Document 94-1, Specification for Rotary Instrumentation

Magnetic Recording Tape, 19-millimeter (0.75 inch) Wide, 68 KA/M (850 Oersteds)2. A tape

base thickness of 16 um is normally employed. The recorder/reproducers shall be capable of using 19 mm cassettes that conform to the physical dimensions of medium and large cassettes as

defined in SMPTE 226M

3

and as shown in Table 6-2. Table 6-2 shows tape capacities andindicates the amount of time available for recording, assuming a data input rate of 240 megabitsper second.

6.3.3 Recorder/Reproducer Input and Output. Data input and clock are required. The data

input shall be in an 8-bit parallel, byte serial format, and the clock signal will be at the requiredbyte rate. Data output will also be in 8-bit parallel format.

TABLE 6-2. TAPE LENGTH AND NOMINAL PLAY RECORD/ REPRODUCE

TIME AT 240 MEGABITS/SECOND USER DATA RATE

CassetteTape Thickness

(micrometers)Tape Length

(meters)Play Time

(minutes)

Medium 16 587 24

Large 16 1311 55

CASSETTE DIMENSIONS NOMINAL

Cassette Length Width Thickness

Medium 254 mm 150 mm 33 mm

Large 366 mm 206 mm 33 mm

6.4 Multiplex/Demultiplex (MUX/DEMUX) Standard for Multiple Data Channel

Recording on 19-MM Digital Cassette Helical Scan Recorder/Reproducer Systems

For recording and reproducing multiple channels on 19-mm Digital Cassette Helical Scan

Recorders, the ADARIO multiplex/demultiplex format is recommended. The ADARIO

(Analog/Digital/ Adaptable/Recorder Input/Output) format was developed for the Department of

2MML Document 94-1 is available from the Naval Air Warfare Center Aircraft Division, Patuxent

River, W

Maryland 20670.3

SMPTE 226M is available from the Society of Motion Picture and Television Engineers, 595 West

Hartdale Avenue, White Plains, New York 10607.

6-10

7/31/2019 IRIG_106_2009



Defense, Fort Meade, Maryland. The format is government-owned and may, therefore, be usedin equipment provided for government activities. Some of the ADARIO features are:

a. Requires less than 3 percent overhead to be added to user data.b. Accommodates multiple channel record/playback with each channel completely

autonomous in sample rate and sample width.c. Stores all the necessary parameters for channel data reconstruction for real-timeplayback, time-scaled playback, or computer processing.

d. Preserves phase coherence between data channels.

e. Provides channel source and timing information.

f. Accommodates 224

(over 16 million) blocks of data, each block having 2048 24-bitwords (see Figure 6-3).

Figure 6-3. ADARIO block format.

The ADARIO format imposes minimum restrictions on the channel signals and aggregate dataparameters. Specific implementations that use the ADARIO format may impose additional restrictions.

ADARIO format, defined field restrictions are listed in Table 6-3 below:

6-11

7/31/2019 IRIG_106_2009



TABLE 6-3. ADARIO FORMAT (FMT) DEFINED FIELD RESTRICTIONS

Field Restrictions

Session length Unlimited

Sequence numbered Blk. 224 (100 G byte max.)

Master clock MC 219

*250 Hz (131 MHz max.)

Block rate BMD, MC/BMD (8 blk./sec min.) MC/2048 (64K blk./sec. max.)

Aggregate rate MC *24 (3145 Mbps max.)

Channel quantity Q, Ch#, 24

(16 channels max.)

Bits per sample FMT, 1,2,3,4,5,6,7,8,10,12,14,16,18,20,22,24 bits per sample

Input clock rate MC, Rate 219

*250 Hz (131 MHz max.)

Input bit rate 2035 *24 block rate (3125 Mbps max.)

Analog bandwidth MC/2.5 (52.4 MHz max.)

Analog attenuation Atten, 25

(−15 dB, +16 dB)

Analog coupling DCAC (dc or ac)

Time correlation 1/MC (7.6 ns max. resolution) TD/MC 216

(65, 536*MC max. range)

Channel card types CHT, 26

(64 max.)

Channel input digital data can be in any format, serial or parallel, in any coding, and atany levels, TTL, ECL, that can be accommodated by the channel type card used. Channel input

analog signals can contain any form of modulation, at any nominal level, with any dynamic

within the limitations (see Figure 6-4).

6-12

7/31/2019 IRIG_106_2009



Figure 6-4. ADARIO data format.

6-13

7/31/2019 IRIG_106_2009



6.5 Submultiplex/Demultiplex Standards for Multiple Data Channels on a Primary

Digital Multiplex/Demultiplex Channel

For combining multiple low to medium rate telemetry channels on a single primary

digital channel such as the ADARIO input channel, the submultiplex (submux) format is

recommended. The format was developed for test range applications where high quantity of channels must be collected in conjunction with high data rate primary channels. The submuxformat provides a standard for extending the ADARIO primary channel or any other primary

digital channel for conveying data from up to 31 subchannels in digital aggregate data form.

Each channel is totally autonomous and can be enabled or disabled at any time. Some of thefeatures of the submux format are:

a. Accommodates analog, digital clocked and asynchronous, time and annotation text,and other application specific telemetry channels.

b. Requires less than 0.3 percent of overhead per channel.

c. Stores all necessary parameters for channel signal reconstruction in real or scaledtime.

d. Preserves phase coherence between all channels for all rates (dc to maximum) and all

types of channels.

e. Accommodates variable and fixed rate primary channel of up to 256 Mbps.

6.5.1 Format Structure. General structure of the submux format is based on a constant block

rate and variable block data length for each channel data block. The aggregate data stream is thesequential collection of each enabled channel data block with a three-word header. Each channel

data block is the sequential collection of data samples or events within the block time period. A

reserved channel (channel ID=31) provides frame synchronization and block timing and isalways the first channel in the frame sequence. Individual channels can be enabled or disabled at

any time within the rate limitations of the primary channel. Primary channel redundantparameter fields such as date, time, and annotation are placed in optional defined channel types,

thereby, minimizing overhead caused by redundancy. All data and headers are bit packed into

16-bit words. All fields, unless specifically stated, are binary coded. Physical implementation of the format may have design restrictions as to types and quantities of channels and maximum

allowable field limits.

6.5.2 Implied Parameters and Limits. Maximum aggregate rate (256 Mbps), block rate, firstsample time delay measurement, and internal sample period are based on a 16-MHz clock rate

divided by 2N, where N can be set from 0 to 7 defining the derived clock. Block rate is based on

the derived clock divided by 20 160 which sets the limit on the total aggregate word count of allchannels in a block period. The maximum block rate (793.65 blocks per second) in conjunction

with the 16-bit bit count field, limits the maximum subchannel input rate to 52 Mbps. The16-MHz clock limits the time delay resolution to 62.5 nanoseconds.

The maximum number of channels is limited by the 5-bit field and the reserved block

sync channel to 31 channels numbered from 0 to 30. Channel ID of 31 is the reserved block sync

channel that conveys timing information. To accommodate fixed rate primary channel, fill canbe inserted after the last channel data block, prior to the next block sync channel (at the end of

the frame), and must consist of all binary ones (FFFF hex word value).

6-14

7/31/2019 IRIG_106_2009



Channel priority is fixed in channel number sequence with channel ID of 31 (block sync)

first, followed by channel ID 0, if enabled, to channel ID 30, followed by fill (if required) to

maintain fixed channel rate. Any channel can be one of eight channel types. Type 0 channelsconvey timing data in the 3-word header and have implied data length of 0. Type other than zero

contains the bit count field that defines the length of valid data in the data block. The actualword length of the data block is the integer of {(bit count + 15)/16}. Channel type also definesthe content of the fields in the header.

6.5.3 Defined Parameters. Each channel data block has a 3-word (16-bit) header that contains

the channel ID number, channel type, and other defined and undefined fields based on thechannel type code. Undefined fields are reserved for future use and should be zero filled. Each

channel header also contains up to 4 status bits that indicate the condition in the current data

block or the condition of the last aggregate frame.

Channel ID 31 is a special form of channel type 0. The first two words are used for

synchronization and are F8C7 BF1E hex value. The block rate clock (BRC) defines the mainclock binary divider and is used for time scaled signal reconstruction. Each increment time

period doubles. “Fill” indicates if the primary channel requires fill for fixed data rate.

Channel ID can be any unique number from 0 to 30 and designates the physicalsubchannel used for acquiring the data. Channel type defines the type of data this channel

conveys and is currently defined for 0 to 5.

A type 0 “time tag” channel typically processes IRIG time code data and is used to time

tag the frame. The Days Hours Minutes Seconds Fractional Seconds fields are the content of IRIG time code input or channel derived and in the same BCD form as the IRIG G time code.

Type nonzero headers contain FMT field that defines the format of the sample in bits persample, 4-bit status field that indicates any errors or warnings pertaining to the current data

block, bit count field that defines the length of valid data in the data block, and time delay field

that (when external clock is used) indicates the delay from block time to the first sample in theBRC defined clock periods. When the internal clock is used, as indicated by type or most

significant bit (MSB) of time delay, the sample period field defines the period of the internal

sample clock in the BRC defined clock periods. The internal sample clock is always an integer

divisor of the block period and the first sample is coincident with the block time. In type 1blocks, this field is used for sequential block count.

When the internal clock is used with digital serial channel, the data and clock lines aresampled at the designated rate and result in eight data and eight clock samples per data block

word. Otherwise, all incoming digital data are sampled at the incoming clock and results in a

sample in the data block, with the first sample being left justified in the first word with “format”designated number of bits starting with the MSB of the sample. Samples are bit sequentially

packed regardless of word boundaries. The last sample in the block period is fully packed into

the current data block with the remaining portion of the word, if any, being left undefined.

6-15

7/31/2019 IRIG_106_2009



6.5.4 Aggregate Format on the Primary Data Channel. Figure 6-5 shows the defined types of channel data from which the aggregate is composed. The primary data will always consist of the

“frame sync” block followed by one or more unique channel blocks, followed by fill if required.

The frame sync block will be generated at block rate. Aggregate data may be clocked by theprimary channel or by the submux at constant or burst rate depending on the primary channel

characteristics. Data format field definitions appear in Appendix G, Submux Data Format FieldDefinitions.

6.5.5 Submux/Demux FILL Requirement. The submux produces aggregate data at the user

aggregate data rate. In other words, the rate and amount of data produced on the aggregate

output is directly proportional to the user specified clock and data format bits and is averagedover the frame period. This variable aggregate data rate is acceptable to variable rate primary

channels or buffered variable rate recorders.

Fixed rate primary channels and fixed rate recorders require data at some fixed rate. The

fixed rate is usually set to be the maximum expected user aggregate rate. When the user

aggregate rate is less than the maximum, then some sort of filler is necessary to maintain theconstant output rate. The format-specified fill word provides this filler and is automatically

generated when the primary channel or fixed rate recorder provides clocks after the last word of

the last enabled channel is clocked out within the frame period. Fill is always terminated by the

Frame of Block Sync channel, indicating the presence of the next frame data.

The quantity of fill words is totally dependent on the fixed primary channel rate and the

average user aggregate rate within one frame period. Minimum is zero words when user ratesare at the maximum and equal to the fixed rate (minus the overhead). When user rates are at the

minimum, maximum amount of fill will be generated for maintaining constant output rate.

6-16

7/31/2019 IRIG_106_2009



16 BITS

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

GENERAL

FORM

HW1 CHN ID CHT FMT ST1 ST2 ST3 ST4

HW2

HW3 I/E TIME DELAY OR SAMPLE PERIOD

FRAMESYNC

HW1 CHN ID = 1F CHT = 0 SYNC 1 = F8C7 HEX (FULL WORD)

HW2 SYNC 2 = BF1E HEX

HW3 BRC FILL AOE PCR ST3 ST4

TIME

TAG

HW1 CHN ID = 0 TO 30 CHT = 0 MSB DAYS (BCD)

HW2 DAYS HOURS (BCD) MINUTES (BCD)

HW3 SECONDS (BCD) FRACTIONAL SECONDS

A N N O T A T I O N

T E X T

HW1 CHN ID = 0 TO 30 CHT = 1 FMT = 7 NCOV

RPE OE

HW2 BIT COUNT

HW3 BLOCK COUNT

DW1 MSB 1ST CHARACTER MSB 2ND CHARACTER

:

DWn MSB LAST CHARACTER UNDEFINED IF NOT LAST

DIGITAL

SERIALEXTERNAL

CLOCK

HW1 CHN ID = 0 TO 30 CHT = 2 FMT = 0 NSIB OVR ST3 ST4

HW2 BIT COUNT = L

HW3I/E=

0TIME DELAY

DW1 DS1 DS2 DS3 DS4 DS5 DS6 DS7 DS8 DS9 DS10 DS11 DS12 DS13 DS14 DS15 DS16

:

DWn DSL-1 DSL UNDEFINED IF NOT LAST

DIGITAL

SERIAL

INTERNAL

CLOCK

HW1 CHN ID = 0 TO 30 CHT = 2 FMT = 0 0 0 ST3 ST4

HW2 BIT COUNT = L

HW3I/E=

1SAMPLE PERIOD

DW1 DS1 DS2 DS3 DS4 DS5 DS6 DS7 DS8 CS1 CS2 CS3 CS4 CS5 CS6 CS7 CS8

:

DWn DSL- DSL- DSL- DSL- DSL- DSL- DSL- DSL CSL- CSL CSL- CSL- CSL- CSL- CSL- CSL

DIGITAL

PARALLEL

EXTERNAL

CLOCK

HW1 CHN ID = 0 TO 30 CHT = 3 FMT = 0-15 (shown=6) NSIB OVR ST3 ST4

HW2 BIT COUNT = L

HW3I/E=

0TIME DELAY

DW1 MSB 1ST SAMPLE MSB 2ND SAMPLE 3RD SAMPLE

:

DWn MSB LAST SAMPLE LSB=BIT L UNDEFINED IF NOT LAST

ANALOG

WIDE

BAND

HW1 CHN ID = 0 TO 30 CHT = 4 FMT = 0-15 (shown=7) AOR ST2 ST3 ST4

HW2 BIT COUNT = L

HW3I/E=

1SAMPLE PERIOD

DW1 MSB 1ST SAMPLE MSB 2ND SAMPLE

:

DWn MSB LAST SAMPLE UNDEFINED IF NOT LAST

ANALOG

STEREO

“L” & “R”

HW1 CHN ID = 0 TO 30 CHT = 5 FMT = 0-15 (shown=7)

LAO

R

RAO

R ST3 ST4HW2 BIT COUNT = L

HW3I/E=

1ENL ENR SAMPLE PERIOD

DW1 MSB 1ST SAMPLE “L” MSB 1ST SAMPLE “R”

:

DWn MSB LAST SAMPLE UNDEFINED IF NOT LAST

FILL FW FILL WORD — FFFF HEX

Figure 6-5. Submux data format.

6-17

7/31/2019 IRIG_106_2009



6.6 1/2 Inch Digital Cassette (S-VHS) Helical Scan Recording Standards

These standards are for helical scan digital magnetic tape recorder/reproducers using thevery large data store (VLDS) format. This standard is intended for applications where compact

size is needed and bit rates do not exceed 32 or 64 megabits per second (Mbps). The VLDS is a

12.65 mm (1/2 inch) S-VHS (850 Oersteds nominal) media based tape format. This standarddescribes the salient features of the LDS format. To ensure crossplay compatibility betweenrecorders of different manufacturers, refer to Metrum-Datatape document number and title

16829019, M64/32HE Magnetic Tape Recorder/Reproducer Tape Format Specification.

Metrum-Datatape is now Sypris Data Systems and this specification may

be updated in the near future to reflect this change in name. An Adobe pdf copy of this specification can be obtained by calling (303) 773-4701.

Many of the specifications listed in this chapter have been adapted from

this document.

6.6.1 Magnetic Tape and Cassettes. The magnetic tape shall meet the requirements of

Magnetic Media Laboratory (MML) Document 93-1, Specification for Rotary InstrumentationMagnetic Recording Tape, 12.65 millimeter (0.5 inch), 68 KA/M (850 Oersteds)4. The tape

cartridge shall conform to ANSI Standard V98.33M-1983, Specification for Physical

Characteristics and Dimensions5. To ensure crossplay compatibility, the T-160 (327 meters,

min.) is recommended.

6.6.2 Format Types. There are four standard formats. Two B formats provide 32 Mbps

standard density or 64 Mbps high density for most applications where severe environmentalconditions are not encountered. There are also two E formats provide 16 Mbps standard density

or 32 Mbps high density for harsh environments involving extremes of vibration and

temperature. A tape made on a standard density system may be reproduced on a high densitysystem. Relative to the B formats, the E formats use a 100 percent larger track pitch, an 81

percent larger track width, and a larger guard band providing a very large margin for accurately

tracking and recovering data under extreme conditions. The E formats provide only about one-half the data storage capacity of the B format but can be played back on a B format system.

4 MML Document 93-1 is available from the Naval Air Warfare Center Aircraft Division, Patuxent

River, Maryland 20670. 5 ANSI V98.33M-1983 is available from the American National Standards Institute, 1430 Broadway,

New York, New York 10018.

6-18

7/31/2019 IRIG_106_2009



6.6.2.1 B Format. These formats originate from helical scanner implementations using four

helical heads organized in pairs at 180° separation. The heads are both read and write

functionally and are supported by two parallel sets of read/write electronics referred to as datachannels. Helical track dimensions are given in Figure 6-6.

Figure 6-6. Helical track dimensions, B format.

6.6.2.2 E Format. These formats originate from helical scanner implementations using two

helical heads with wider track widths at 180° separation on the scanner. The heads are both readand write functionally. One set of read/write or write only electronics is required. Helical track

dimensions are given in Figure 6-7.

6-19

7/31/2019 IRIG_106_2009



Figure 6-7. Helical track dimensions, E format.

6.6.3 Data Storage. Data are recorded onto 12.65 mm (1/2 in.) wide magnetic tape using both

rotating and fixed heads (see Figure 6-9). The rotating heads record data in adjacent track patterns at an inclined angle to the normal tape motion. The fixed heads record data on tracks

parallel to the tape motion. The fixed head tracks are used for control and servo purposes and do

not directly record user data.

6.6.4 Physical Relationships. Maintaining high accuracy of the ratio between scanner

rotational speed and tape speed (1.5492 mm (0.0610 in.) of tape motion per scanner rotation) iscritical to maintaining the format geometry. Head and tape speed will vary accordingly with

changes in the other two speed parameters. The three speed parameters vary linearly with

desired user data rates. Parameters used with a user data rate of 32 Mbps (B) or 16 Mbps (E) are

as follows in Table 6-4:

6-20

7/31/2019 IRIG_106_2009



TABLE 6-4. PHYSICAL PARAMETERS

user bits/helical track 217

=131 072 bits (16 kilobytes)

scanner diameter

62.000 mm + 0.008/-0.000 mm (2.44

in. + 0.0003 in.)

scanner rotation speed 3662.1 rpm

tape speed 94.55 mm/sec (3.72 in./sec.)

head/tape speed 11 794.30 mm/sec (464.34 in./sec.)

helix angle (head rotational

plane to ref. edge of tape) 5° 56' 7.4" basic dimension

head gap length refer to Metrum Document 168290196

tape tension (inlet side of

scanner)0.35N ± 0.02N

6.6.5 Helical Track Organization. Each group of four helical tracks resulting from one

complete revolution of the scanner (two helical tracks for the E formats) is termed a principalblock on the tape. A principal block is the smallest increment of data that may be written to or

read from the tape. Each principal block is assigned a unique number, which is recorded as part

of the helical track. Helical tracks containing user data begin with the number 1 and are

sequentially incremented on the tape up to the capacity of the cartridge. Whenever new data areappended on a previously recorded cartridge, the new data are precisely located to begin with the

next helical track location after the previous end of data point with no interruption or

discontinuity in track spacing.

6.6.6 Recorded Information. The following subparagraphs contain additional information.

6.6.6.1 Add overhead bytes generated by error correction encoding algorithms.

6.6.6.2 Provide preamble and postamble patterns for isolation of the information at thebeginning and end of the helical tracks.

6.6.6.3 Provide clock synchronization patterns to facilitate clock recovery at the beginning of

each helical track.

6.6.6.4 Add patterns throughout the helical track to maintain synchronization and counteract

bit slips during data extraction.

6.6.6.5 Provide redundantly recorded principal block numbers for organizing data on the

cartridge.

6.6.6.6 Include a user specifiable volume label for identifying the entire cartridge.

6 See reference on how to obtain the Metrum-Datatape document at paragraph 6.6 above.

6-21

7/31/2019 IRIG_106_2009



6.6.6.7 Add miscellaneous data used to convey information about the organization of data on

the cartridge and within the helical tracks.

6.6.7 Recording Geometry and Physical Dimensions. Included in the following

subparagraph are the recording geometry and the physical dimensions.

6.6.7.1 Tape Reference Edge. The tape reference edge for dimensions specified in this section

shall be the lower edge as shown in Figure 6-8. The magnetic coating, with the direction of tape

travel as shown in Figure 6-6, shall be the side facing the observer.

6.6.7.2 Helical Tracks. Contained in the succeeding subparagraphs are the helical tracks

attributes.

6.6.7.2.1 Track Widths. The width of a written track shall be 0.032 mm ±0.002 (0.0013 in.

± 0.000079) for the B formats and 0.058 mm ± 0.002 (0.0023 in. ± 0.000079) for the E formats.

6.6.7.2.2 Track Pitch. The distance between the center lines of any two adjacent tracks,

measured perpendicular to the track length, shall be 0.0404 mm (0.0016 in.) for the B formatsand 0.0808 mm (0.0032 in.) for the E formats.

6.6.7.2.3 Track Straightness. Either edge of the recorded track shall be contained within two

parallel straight lines 0.005 mm (0.0002 in.) apart. The center lines of any four consecutivetracks shall be contained within the pattern of four tolerance zones. Each tolerance zone is

defined by two parallel lines, which are inclined at an angle of 5° 58' 58.4" basic with respect tothe tape edge. The center lines of the tolerance zones shall be spaced 0.0404 mm (0.0016 in.)

apart for the B format and 0.0808 mm (0.0032) apart for the E format. The width of the first

tolerance zone shall be 0.007 mm (0.00028 in.). The width of tolerance zones two, three, andfour shall be 0.011 mm (0.0004 in.). These tolerance zones are established to contain track

angle, straightness, and pitch errors.

6-22

7/31/2019 IRIG_106_2009



6-23

Figure 6-8. Recorded tracks on tape, B format.

7/31/2019 IRIG_106_2009



6.6.7.2.4 Gap Azimuths. The azimuth of the head gaps used for the helical track recording shall

be inclined at angles of ±6° ±15' to the perpendicular to the helical track record (see Figure 6-8

and Figure 6-9). For the E formats and for the first and third tracks of every principal block of the B formats, the recorded azimuth is oriented in the clockwise direction with respect to the line

perpendicular to the track direction when viewed from the magnetic coating side of the tape. For

the B formats, the second and fourth tracks of each principal block are oriented in thecounterclockwise direction.

Figure 6-9. Tape cartridge layout.

6.6.7.2.5 Track Guard Bands. The nominal unrecorded guard band between any two adjacent

helical tracks shall be 0.008368 mm (0.0003 in.) for the B formats and 0.022737 mm (0.0009 in.)

for the E formats.

6.6.7.2.6 Track Angle. The track angle shall be 5° 58' 58.4".

6.6.7.2.7 Track Length. The track length shall be 96.619 mm (3.80 in.).

6.6.7.2.8 Physical Recording Density. The maximum physical density of the recording shall be1930 or 3776 flux transistors per millimeter (ftpmm) respectively for the 32 and 64 Mbps

systems.

6.6.7.3 Longitudinal Tracks. The characteristics of the longitudinal tracks are described in the

subsequent subparagraphs.

6.6.7.3.1 Servo Track. The servo track is located along the reference edge of the tape as shown

in Figure 6-7. The azimuth angle of the servo track head gap shall be perpendicular to therecorded track. The recording of the servo track is composed of a recorded pulse (nominally

0.0185 mm (0.0007 in.)) for each principal block on the tape. The recording shall achieve full

magnetic saturation for at least half the pulse. The time duration of the pulse is determined bythe tape speed to yield this physical dimension. During the interval between pulses, no magnetic

recording occurs on the track. The pulse is timed to begin coincident with the midpoint of theprincipal block (the data channel switches from first to second head). The physical offset from

the longitudinal head to the helical heads is shown in Figure 6-7, Figure 6-8, and Figure 6-9 asdimension “X.”

6.6.7.3.2 Filemark Track. The filemark track is located near the top of the tape as shown inFigure 6-7. The azimuth angle of the filemark track head gap shall be perpendicular to the

recorded track. The recording of the filemark track is composed of a series of pulses located in

6-24

7/31/2019 IRIG_106_2009



conjunction with the principal block to be marked. Each filemark is composed of threeredundant pulses (nominal 0.005 mm (0.0002 in.)). The three pulses are typically spaced

0.029 mm (0.0011 in.) apart with a maximum span of 0.09 mm (0.0035 in.) from the beginning

of the first to the beginning of the third. This triplet of pulses is for redundancy against tapeflaws and on detection are treated as one filemark regardless of whether 1, 2, or 3 pulses are

detected. The filemark pulses are associated with a specific principal block by initiating the firstpulse between 4 to 5.5 msec after the midpoint of the principal block. (Data channel switchesfrom first to second head.)

6.6.8 Tape Cartridge Format. The physical format of the recording along the length of the

tape is shown in Figure 6-10. Immediately following the physical beginning of tape (PBOT) isan unused portion of tape, followed by the cassette format zone, which precedes the logical

beginning of tape (LBOT). Principal blocks of user data shall be recorded between LBOT and

the logical end of tape (LEOT), which precedes the physical end of tape (PEOT).

6.6.8.1 Load Point. The load point is defined as the first point after PBOT accessible by the

recording system with the tape fully engaged to the scanner.

6.6.8.2 Format Zone. The format zone begins at the load point, precedes the LBOT, and

consists of a minimum of 450 principal blocks recorded on the tape. It provides a run up area for

the servo systems and principal block identification allowing precise location of the LBOTwhere user data begin. The zone must be prerecorded to prepare the cartridge to accept user

data. This process involves locating at the load point and beginning recording as soon as tape

speed servo lock is achieved. The principal blocks recorded are numbered beginning with anegative number and counting up until principal block 0 is recorded. Principal block 0 shall be

the last recorded block in the format zone. Principal blocks recorded in the format zone do notcontain user data or error correction coding (ECC) overhead bytes, but do contain the remaining

miscellaneous information described in paragraph 6.6.6 and in the helical track data format

descriptions. The volume label for the cartridge is irreversibly determined at the time the formatzone is recorded.

6.6.8.3 Logical Beginning of Tape. The logical beginning of tape denotes the end of theformat zone and the point at which principal blocks containing reproducible data begin. The first

principal block containing useful information shall be assigned the number one.

6.6.8.3 Data Zone. Beginning with principal block 1 at LBOT and continuing through toLEOT, the data zone shall be the principal blocks that record user data as well as the added

miscellaneous information to allow full reproduction and management of the data on the tape

cartridge.

6.6.8.5 Logical End of Tape. The logical end of tape is a physical principal block count. The

principal block count for the standard ST-160 tape cartridge is 210 333.

6.6.9 Helical Track Format. The format for writing data into a single helical track is shown

in Figure 6-11. The term "bits" refers to actual on tape bit cells. Each helical track begins with apreamble area consisting of 6216 bits of an alternating pattern of three 0 bits and three 1 bits for

6-25

7/31/2019 IRIG_106_2009



the 32 Mbps system or 9240 bits for the 64 Mbps system. This 6-bit pattern is repeated 1036 or1540 times. The preamble is followed by a track synchronization area. This area provides for

obtaining registration to the track data patterns. It is composed of four zones of 732 bits each

with an alternating 0- and 1-bit pattern that facilitates clock recovery. Each of these four zones isfollowed by a 36-bit sync pattern. These sync patterns are described more fully in

paragraph 6.6.9.1. The track synchronization area ends with 24 bits of an alternating pattern of three 0 bits and three 1 bits. The central area is where actual user data are recorded in 138 datablocks for the 32 Mbps system or 276 data blocks for the 64 Mbps system. Each data block

contains 205 5/6 modulation code frames of interleave data for a total of 1230 bits.

This data is followed by a 36-bit sync pattern. Sync patterns and interleave data aremore fully described next. Each helical track ends with a postamble pattern of three 0 bits and

three 1 bits. This is the same pattern as the preamble. Compiling all bits yields an overall track

total of 186 468 tape bits for the 32 Mbps system and 364 824 tape bits for the 64 Mbps system.Since each contains 131 072 or 262 144 user bits, overheads are 29.7 and 28.1 percent.

6.6.9.1 Sync Patterns. Each helical track contains 142 or 280 sync patterns as shown inFigure 6-10. Four of these are contained in the track sync area with the remaining 138 or 276

distributed at the end of each data block. These sync patterns provide registration to the bit

sequence and allow management of bit slips. The track and data sync consists of 36 bits in the

form of six 6-bit words. The first five words are the same for all sync words (Table 6-5).

6-26

7/31/2019 IRIG_106_2009



Figure 6-10. Helical track format.

TABLE 6-5. TRACK AND DATA SYNC: WORD 0-WORD 4

WORD0 2Ah

WORD1 2Ah

WORD2 0Ch

WORD3 0Fh

WORD4 2lh

6-27

7/31/2019 IRIG_106_2009



WORD5 defines which sync word is being issued in the following manner (Table 6-6).

TABLE 6-6. TRACK AND DATA SYNC: WORD 5

Sync Loc. Word

Track Sync 1 39h

Track Sync 2 35h

Track Sync 3 2Dh

Track Sync 4 1Dh

Data Sync 1 2Bh

Data Sync 2 2Eh

Data Sync 3 2Bh

Data Sync 4 2Eh

Data Sync 5 2Bh

Data Sync 6 2Eh

: :

Data Sync 279 2Bh

Data Sync 280 2Eh

6.6.9.2 Data Blocks. Each helical track contains 138 or 276 data blocks, which record the user

data as well as miscellaneous information used in locating and managing data on the tape

cartridge (see Figure 6-10). The construction of these data blocks is performed by eachchannel’s data path electronics. Figure 6-11 illustrates a typical block diagram of a channel data

path as described in the following subparagraphs.

6.6.9.2.1 Error Correction Encoding. An interleaved Reed-Solomon (RS) code is used for error

detection and correction. An outer ECC is applied to written data first which is an RS (130, 128)

for purposes of error detection only. An inner ECC is subsequently applied which is an RS (69,65) for error detection and correction. The resulting encoded data is stored in a multiple page

interleave buffer memory array containing 128 rows by (2•69) or (8•69) columns of encoded

user data. For the outer ECC, incoming data is arranged in groups of 128 bytes each. The outer

ECC encoder appends 2 check bytes to each 128 byte block. For the inner ECC, the 130 bytegroup resulting from the outer ECC is divided into two 65 byte blocks. The first 65 byte block

(ECC code words 1, 3, 5, ...) contains all user data while the second 65 byte block (ECC code

words 2, 4, 6, ...) contains 63 bytes of user data with the last 2 bytes being the check bytes

generated by the outer ECC. The inner ECC encoder appends 4 check bytes to each 65 byteblock.

6-28

7/31/2019 IRIG_106_2009



Figure 6-11. Typical VLDS data path electronics block diagram.

6-29

7/31/2019 IRIG_106_2009



Operations in the RS encoder are performed using numbers in a finite field (also called aGalois field (GF)). The field used contains 256 8-bit elements and is denoted GF (256). The

representation of GF (256) used is generated by the binary degree eight primitive polynomials.

p(x) = x8

+ x4

+ x3

+ x2

+ 1 outer ECCp(x) = x8 + x5 + x3 + x + 1 inner ECC

The ECC generator polynomials are:

G(x) = (x+a24) (x+a25) outer ECC

G(x) = (x+1) (x+a) (x+a2) (x+a3) inner ECC

where "a" denotes the primitive element of the field.

6.6.9.2.2 Interleave Buffer. Encoding data from the two levels of ECC are stored in an

interleave buffer memory. The architectures for this memory are shown in Figure 6-12. This

buffer allows interleaving of the encoder data. Interleaving spreads adjacent ECC code wordbytes within a helical track for the 32 Mbps system to minimize the effect of burst error events.

For the 64 Mbps system, interleaving spreads adjacent ECC code word bytes within two helical

tracks (two helical tracks per channel per principal block) to further minimize burst error effects.Data to and from the ECC are accessed along horizontal rows in the memory matrix. Data to and

from tape are accessed along vertical columns in the memory. Each column in the matrix

consists of 128 bytes that will constitute one block in the helical track format (see Figure 6-11).

Figure 6-12. Interleave buffer architectures.

6-30

7/31/2019 IRIG_106_2009



6.6.9.2.2.1 Exchange of Data with ECC. Addressing of the interleave buffer for exchange of data with the ECC for the 32 Mbps systems is as follows in Table 6-7.

TABLE 6-7. ECC - INTERLEAVE BUFFER ADDRESSING (32 Mbps)

ECC Code Word Address Range (hex)

1 0080 to 00C4

2 0000 to 0044

3 0180 to 01C4

4 0100 to 0144

5 0380 to 03C4

6 0200 to 0244

: :

253 7E80 to 7EC4

254 7E00 to 7E44

255 7F80 to 7FC4

256 7F00 to 7F44

Addressing of the interleave buffer for exchange of data with the ECC for the 64 Mbpssystems is as follows in Table 6-8.

TABLE 6-8. ECC - INTERLEAVE BUFFER ADDRESSING (64 Mbps)

ECC Code Word Address Range (hex)

1 00000 to 00044

2 00400 to 00444

3 00800 to 00844: :

128 1FC00 to 1FC44

129 00080 to 000C4

130 00480 to 004C4

: :

256 1FC80 to 1FCC4

257 00100 to 00144

258 00500 to 00544

: :

512 1FD80 to 1FDC4

513 00200 to 00244514 00600 to 00644

: :

1024 1FF80 to 1FFC4

Note: Each code word is 69 bytes long. The address increments by hex 001 for each byte in a code

word. The first data byte sent to/from the ECC for each helical track is stored in

location 000.

6-31

7/31/2019 IRIG_106_2009



6.6.9.2.2.2 Exchange of Data To and From Tape. Addressing of the interleave buffer forexchange of data to and from tape for the 32 Mbps system is as follows in Table 6-9.

TABLE 6-9. TAPE - INTERLEAVE BUFFER ADDRESSING (32 Mbps)

Data Block Address Range (Channel 1) Address Range (Channel 2)

1 0000 to 7F00 0022 to 7F22

2 0080 to 7F80 00A2 to 7FA2

3 0001 to 7F01 0023 to 7F23

4 0081 to 7F81 00A3 to 7FA3

5 0002 to 7F02 0024 to 7F24

6 0082 to 7F82 00A4 to 7FA4

: : :

67 0021 to 7F21 0043 to 7F43

68 00A1 to 7FA1 00C3 to 7FC369 0022 to 7F22 0044 to 7F44

70 00A2 to 7FA2 00C4 to 7FC4

71 0023 to 7F23 0000 to 7F00

: : :

135 0043 to 7F43 0020 to 7F20

136 00C3 to 7FC3 00A0 to 7FA0

137 0044 to 7F44 0021 to 7F21

138 00C4 to 7FC4 00A1 to 7FA1

Note: Each data block is 128 bytes long. The address increments by hex 0100 for each byte in

a data block. The first byte sent to/from tape for each channel 1 helical track is stored in

location 0000. The first byte sent to/from tape for each channel 2 helical track is stored inlocation 0022.

Addressing of the interleave buffer for exchange of data to/from the 64 Mbps system

is as follows in Table 6-10.

6.6.9.2.3 8 to 5 Conversion. Data being moved from the interleave buffer to tape is read from

the memory in 8-bit bytes and is immediately converted to 5-bit groups in preparation for

modulation coding. During reproduction, this conversion occurs in reverse fashion. Thealgorithm for conversion is detailed in Metrum Specification 16829019.7

7 See reference on how to obtain the Metrum-Datatape document at paragraph 6.6 above.

6-32

7/31/2019 IRIG_106_2009



TABLE 6-10. TAPE - INTERLEAVE BUFFER ADDRESSING (64 Mbps)

Data Block Address Range (hex)

1 00000 to 1FC002 00080 to 1FC80

3 00100 to 1FD00

4 00180 to 1FD80

: :

8 00380 to 1FF80

9 00001 to 1FC01

10 00081 to 1FC81

: :

275 00122 to 1FD22

276 001A2 to 1FDA21’ 00222 to 1FE22

2’ 002A2 to 1FEA2

3’ 00322 to 1FF22

: :

8’ 01A3 to 1FDA3

9’ 00223 to 1FE23

10’ 002A3 to 1FEA3

: :

275’ 00344 to 1FF44

276’ 003A4 to 1FFA4Note: Each data block is 128 bytes long. The address increments by hex 0400 for each byte ina data block. The first byte sent to or from tape for both channels is stored in location 00000.

The interleave buffer extends across both helical tracks in a principal block for each channel,

thus the data block number “n” refers to the data block in the first helical track of the principal

block and the data block number “n’ ” denotes the data block number in the second helicaltrack of the principal block.

6.6.9.2.4 Miscellaneous Information Inclusion. Each data block in the helical track includes

one additional bit added to the data set prior to modulation coding. Each data block removed

from the interleaved buffer memory consists of 128 bytes of ECC encoded user data totaling1024 bits. Conversion from 8-bit bytes to 5-bit groups results in 204 groups plus 4 bits. A

miscellaneous information bit is added to each data block as the 1025th bit to complete 205 full

5-bit groups. Miscellaneous information is currently defined only in the first helical track of

each principal block. The remaining three helical tracks (1 in the E format) contain no definedmiscellaneous bits and are reserved for future expansion. Any reserved miscellaneous

information bits shall be recorded as 0 bits. The defined purposes of miscellaneous information

bits in the first helical track of each principal block are presented in Table 6-11.

6-33

7/31/2019 IRIG_106_2009



TABLE 6-11. MISCELLANEOUS BIT DEFINITIONS

Data Block Miscellaneous Bit Definition

1 to 20 inclusive First copy of 20-bit principal block number: 2s complement binary; leastsignificant bit in data block 1; most significant bit in data block 20.

21 to 40

inclusive

Second copy of 20-bit principal block number: 2s complement binary;

least significant bit in data block 21; most significant bit in data block 40.

41 to 60

inclusive

Third copy of 20-bit principal block number: 2s complement binary; least

significant bit in data block 41; most significant bit in data block 60.

61 to 76

inclusive

Volume label: 16-bit binary; least significant bit in data block 61; most

significant bit in data block 76.

77 to 80

inclusive

Revision number: 4-bit code; value at time of writing is 0001 (1h).

81 to 84

inclusive

4-bit tape information code as follows:

81 bit = 0 denotes all helical data was input as user digital data.

81 bit = 1 denotes input data stream to each channel. The ECC was 15 bytes of

user digital data beginning with first byte plus 1 inserted byte from adifferent source in a repeating fashion. This bit must be uniformly set for

the entire cartridge including the format zone. It is used to support mixing

of digitized analog data into the digital stream and separation on

reproduction.

82 bit = 0 denotes cartridge size is ST-120 for purposes of determining LEOT.This bit must be set for the entire cartridge including the format zone.

82 bit = 1 denotes cartridge size is ST-160 for purposes of determining LEOT.

This bit must be set uniformly for the entire cartridge including the format

zone.

83 bit = Reserved for additional tape information coding.

84 bit = Reserved for additional tape information coding.

85 to 138 or 276inclusive

Reserved for future expansion.

6.6.9.2.5 Modulation Code. Data is encoded using a 5/6 modulation code that has a spectral

null at dc. The coding algorithm employed has a code word digital sum (CWDS) maximum

of ±2 with a maximum run length of 6 bits. The 205 5-bit groups resulting from the 8 to 5

conversion (including the inserted miscellaneous bit) undergo this coding to form the final5/6 code frames that are physically recorded in the data blocks of the helical track format. The

algorithm for coding is detailed in Metrum Specification 16829019.

6-34

7/31/2019 IRIG_106_2009



6.7 Multiplex/Demultiplex (MUX/DEMUX) Standards for Multiple Data Channel

Recording on ½ Inch Digital Cassette (S-VHS) Helical Scan Recorder/Reproducer Systems

For recording and reproducing multiple channels on 1/2 inch digital cassette (S-VHS)

helical scan recorders, the asynchronous real-time multiplexer and output reconstructor

(ARMOR) multiplex/demultiplex format is recommended. The ARMOR data format is anencoding scheme that may be used to multiplex multiple asynchronous telemetry data channelsinto a single composite channel for digital recording, transmission, and subsequent

demultiplexing into the original constituent channels.

6.7.1 General. Data types supported by the ARMOR format are PCM, analog, decoded IRIG

time, and 8-bit parallel. MIL-STD-1553B8 data is encoded into an IRIG 106 Chapter 8 serial

PCM stream prior to multiplexing into the ARMOR format. Voice channels are encoded in thesame way as all other analog channels. The composite channel is formatted into fixed bit-length,

variable word-length frames. A constant aggregate bit rate and a fixed frame bit-length are

established for each multiplex by an algorithm that is dependent on the number, type, and rate of the input channels. The aggregate bit rate and frame bit length result in a fixed frame rate for

each multiplex. The ARMOR encoding scheme captures the phase of each input channel relative

to the start of each composite frame. The demultiplexing process may then use the captured

phase information to align the reconstruction of the constituent channels relative to a reproducedconstant frame rate.

6.7.2 Setup Block Format. In addition to defining the organization of the frames containing themultiplexed data, the ARMOR format incorporates the definition of a “setup block” that contains

the parameters necessary to demultiplex the associated data frames. The setup block is included

in the composite stream at the start of each recording to preserve with the data the informationnecessary to decode the data. Appendix L defines the setup block format and content.

6.7.3 Multiplexer Format. The definition of the ARMOR multiplex format has two parts. The

frame structure definition describes the organization of the composite data frame, which changes

from one multiplex to the next. The channel coding definition describes the encoded data wordformat for each data type, which is the same for all multiplexers.

6.7.3.1 Frame Structure. The sequence of steps used to establish the multiplexed frame structure,

shown in Figure 6-13 below, is explained in Table 6-12. The process involves putting the sync,PCM, parallel (PAR), time code, and analog channels into a frame. The filler blocks may consist

of either constant (hex FF) bytes or analog samples, depending upon the constituent input

channel mix. The PCM Sample Start Bit Point and the Parallel Sample Start Bit Point are basedon calculations of the master oscillator, pacer, and the bit rate of the slowest PCM and word rate

of the slowest parallel channels respectively. The pacer is a clock pulse that is programmed to amultiple of the fastest analog channel sample rate. These calculations assure that the first wordof the slowest PCM channel or the first word of the slowest parallel channel is not placed too

early in the composite frame. If necessary to satisfy these Start Bit Point calculations, filler in

the form of analog channel words or hex FF (if no analog words are available) is used to force

the first PCM or PAR word later in the composite frame. Compatibility with specific legacy

8 MIL-STD 1553B (1996), Digital Time Division Command/Response Multiplex Data Bus.

6-35

7/31/2019 IRIG_106_2009



versions of the format requires the use of the appropriate equations, which are embodied in asoftware program, refer to Calculex Part No. 199034-0002.9

Step 1 2 3 4 5 6 7

1 2 … m 1 2 … m

1 2 3 4

Sync FillerPCM Channel

BlocksFiller

PAR ChannelBlocks

Filler

Figure 6-13. The steps of the build process.

9Part Number 199034-0002, available from CALCULEX, Inc., P.O. Box 339, Las Cruces, NM 88004

(505) 525-0131 or by email to [email protected].

6-36

7/31/2019 IRIG_106_2009



TABLE 6-12. SCANLIST BUILD STEPS

(Reference scanlist in Figure 6-13)

Step #1 Sync The sync is made up of four bytes of 8 bits totaling 32 bits:

FE 6B 28 40.

Step #2 Time Code If time code exists, it is placed after the sync in three words of

bit length 24, 24, and 16. Multiple time codes are placed in

ascending hardware sequence, as identified in the setup block.

Step #3 Filler (PCM Start

Bit)

If required, either filler or analog channels are placed next,

depending on the calculation of the PCM Sample Start Bit

Point. If no analog (or voice) channels are included in the

multiplex, hex value “FF” filler is inserted in the frame as

required to satisfy the PCM Sample Start Bit Point calculation.

When analog channels are part of the multiplex, analog words

are used in place of hex FF filler to minimize the formatting

overhead.

Step #4 PCM Channels The PCM channels are placed next in ascending order of speed

with the slowest channel first. Multiple channels at the same

speed are placed in ascending hardware sequence, as identified

in the setup block.

Step #5 Filler (PAR Start

Bit)

If required, either filler or analog channels are placed next,

depending on the calculation of the PAR Sample Start Bit

Point. If no analog (or voice) channels are included in themultiplex, hex FF filler is inserted in the frame as required to

satisfy the PAR Sample Start Bit Point calculation. When

analog channels are part of the multiplex, any remaining

analog words that were not inserted in the frame at step 3 are

used in place of hex FF filler to minimize the formatting

overhead channel.

Step #6 PAR Channels The PAR channels are placed next in ascending order of speed

with the slowest channel first. Multiple channels at the same

speed are placed in ascending hardware sequence, as identified

in the setup block.

Step #7 Filler (Analog

Channels)

All remaining analog words that have not been used for filler

in steps 3 and 5 are placed next, followed by any additional

filler required to satisfy the pacer divisor calculation.

6-37

7/31/2019 IRIG_106_2009



6.7.3.2 Pacer Divisor Calculation. The number of analog samples per ARMOR frame for eachanalog channel must be evenly divisible into the number of bits per ARMOR frame. The initial

bits per ARMOR frame are calculated to minimize the aggregate bit rate of the composite. Filler

is then added to satisfy the divisibility rule to set the pacer clock speed. This step is referred toas the pacer divisor calculation since the pacer itself is derived from the same master oscillator as

the aggregate bit rate clock.

6.7.3.3 ARMOR Channel Coding. Each input data channel is encoded into 8-, 12-, 16-, or 24-

bit words, depending on the type of channel. The bit length of an ARMOR frame is always an

integer multiple of eight, so 12-bit words must occur an even (multiple of two) number of times

within each frame. The data within a frame is serially concatenated most significant bit first.Table 6-13, which is an example of an ARMOR frame with two analog, one parallel, four PCM,

and one time code channel, is referenced in the following descriptions.

TABLE 6-13. SAMPLE ARMOR FRAME

Frame Item Description Words/Frame Bits/Word

Sync Pattern X’FE6B2840’ 1 32

Time Code Ch#1 Encoded Time 2 24

Time Code Ch #1 Encoded Time 1 16

Filler X’FF’ 7 8

PCM Ch#1 Encoded User Data 130 16




Analog Ch #1 Encoded User Data 100 12Analog Ch #2 Encoded User Data 20 12

Analog Ch #1 Encoded User Data 2 16

Analog Ch #1 Encoded User Data 260 8

6.7.3.4 Sync Pattern. All ARMOR frames begin with the fixed 32-bit sync pattern of

hexadecimal FE6B2840.

6.7.3.5 Time Code Channels. When time code channels are present in an ARMOR multiplex,

their data words always immediately follow the sync pattern or another time code channel. Time

is encoded as 64 bits in two 24-bit words and one 16-bit word. Table 6-14 defines the individual

bits of the time code words. The encoded time is the time at the start of the ARMOR frame.

6-38

7/31/2019 IRIG_106_2009



TABLE 6-14. TIME CODE WORD FORMAT

BIT WORD 1 WORD 2 WORD 3

22 D8 S6

21 D7 S5

20 D6 S4

19 D5 S3

18 D4 S2

17 D3 S1

16 D2 S0

15 D1 SE 014 D0 NT 0

13 0 0 HN13

12 H5 0 HN12

11 H4 MS11 HN11

10 H3 MS10 HN10

9 H2 MS9 HN9

8 H1 MS8 HN8

7 H0 MS7 HN7

6 M6 MS6 HN6

5 M5 MS5 HN5

4 M4 MS4 HN4

3 M3 MS3 HN3

2 M2 MS2 HN2

1 M1 MS1 HN1

0 M0 MS0 HN0

LEGEND

D = Day of year.

H = Hour of day.

M = Minutes past the hour.S = Seconds past the minute.

MS = Milliseconds past the

second.HN = Hundreds of nanoseconds

past the millisecond.

SE = Sync error (time codedecoding error).

NT = No time code (input signal

detect fail).

0 = Always 0.

6.7.3.6 PCM Channels. User PCM data is encoded into 16-bit words. The number of 16-bitwords (per channel) in each frame is approximately two percent greater than the number requiredto store the user data during the frame time period. These overhead words are included to

compensate for minor variations in user data clock rates. In order to record the number of

allocated frame bits that actually contain user data, the first two 16-bit words are redundant

copies of a bit count. In Table 6-13, PCM Channel #1 has 130 words: two count words and 128data words. The bit count in either one of the redundant count words records the number of bitsin the 128 data words that are actually user PCM data (most significant bit first). All remaining

6-39

7/31/2019 IRIG_106_2009



bits are filler. The first user data bit in the most significant bit location of the third channel word(the first data word following the redundant count words) was the first bit to be received after the

start of the ARMOR frame.

6.7.3.7 Analog Channels. Analog data is digitized into either 8-bit or 12-bit samples using

offset binary notation (a sample of X’00’ or X’000’ is the largest negative value). No overheadwords or bits are included with analog channel data because input sampling is synchronous to thestart of the ARMOR frame. The first sample of each channel was captured at frame start time

with all remaining samples evenly spaced throughout the frame time. Note that the location of

the analog channel words within the composite ARMOR frame has no correlation with the time

between the start and end of the frame when the analog samples were captured (digitized). Thefirst sample of the 100 Analog Channel #1 words and the first sample of the 20 Analog Channel

#2 words in Table 6-13 were both captured (digitized) at the same instant in time, which was the

frame start time. Voice is a special case of an analog channel in that it is always 8-bit samples.

6.7.3.8 Parallel Channels. The encoding of parallel input channels is very similar to PCM

encoding. Approximately two percent more than the minimum number of words necessary tostore the user data during one ARMOR frame period are allocated to each parallel channel. The

first two 16-bit words of each channel are redundant count words that record the actual number

of allocated data words that contain user data. The remaining allocated words contain filler.

Table 6-4 has two entries for Parallel Channel #1. The first entry shows the two (redundant) 16-bit count words and the second entry shows the number of allocated 8-bit data words for the

channel. The number of 8-bit data words that contain user data is determined by examining

either of the two count words. The first data word for each parallel channel was the first wordreceived after the start of the ARMOR frame.

6.7.4 ARMOR Format Compatibility. Compatibility with the ARMOR format can be divided

into two distinct cases. In the first case, the user is playing back a legacy tape (made with legacy

multiplexer hardware and software) on non-legacy demultiplexer hardware and software. In thesecond case, the user is creating a tape on non-legacy multiplexer hardware and software for

future playback by legacy demultiplexer hardware and software.

In the first case, the legacy tape contains a setup block (see paragraph 6.7.2) at the start

of the recording. The setup block contains the information necessary for the user to demultiplex

the data records on the tape. The bit rate field in the setup block header section specifies the rate

at which the legacy recording was generated. The saved scanlist field in the setup block trailersection specifies the exact sequence and size of the sync, data, and filler words in the recording.

In the second case, the user must first generate an ARMOR setup block at the start of the recording. Subsequent data records must then be formatted in accordance with the

specification in the setup block. Setup block creation is described in Appendix L.

6.7.5 ARMOR Format Validation. The CALCULEX, Inc. ARMOR Format Verification

Program (AFVP) may be used to determine if an independently generated multiplex is

compatible with existing legacy hardware. The AFVP reads the setup block from the data setunder test and validates the data set frame structure (see paragraph 6.7.2). Please refer to IRIG

6-40

7/31/2019 IRIG_106_2009



Document118, Test Methods For Telemetry Systems And Subsystems, Volume III, TestMethods For Recorder/Reproducer Systems And Magnetic Tape. The AFVP may be obtained

from CALCULEX.10

6.8 Recorder Command and Control Mnemonics (CCM)

This section describes a set of standard commands and replies that can control tape, disk,and solid-state recorders. Not all commands may be applicable to all types of recorders or

recorder implementations. Manufacturers who claim compliance with this Standard shall

identify (in an Interface Control Document, for each recorder model) the specific command andreply subset that is implemented. An important aspect of the CCM standard is the required

command-response protocol. For each command issued to a recorder, there shall be exactly one

response from the recorder, and the response shall begin immediately upon conclusion of thecommand input. There shall be no delay between the receipt of the command at the recorder and

the transmission of the reply by the recorder. Commands that initiate recorder functions

requiring time to complete shall be replied to immediately, and the host shall poll the recorderstatus to determine when the function is complete. There shall be no unsolicited status output

from the recorder, with one exception. This exception is a boot message upon leaving the

POWER ON state, notifying the host that the recorder is ready to accept commands. The boot

command shall contain a single asterisk as the last character. Thereafter, the recorder will onlyoutput in response to a command input. (A hardware reset or a software .RESET shall return the

recorder to the POWER ON state.)

6.8.1 Command Summary. All commands must comply with the following syntax rules. Thesyntax rules are summarized as available commands in Table 6-15.

a. All recorder commands are simple ASCII character strings delimited by spaces.b. All commands begin with an ASCII period (“.”) and, with the single exception of the

.TMATS command, end with the first occurrence of a carriage return and line-feedterminator sequence.

c. Parameters are separated from the commands and from each other with ASCII spacecharacters.

d. With one exception, command words and parameters may not include spaces. The

one exception is the [text string] parameter for the .EVENT command.e. Multiple consecutive terminators and extraneous space characters are ignored.

f. Each command is followed with either a text response, carriage return line feed, and

an ASCII asterisk (“*”) response terminator or the asterisk response terminator only,indicating the recorder is ready for the next command.

g. All numeric parameters, with one exception, are decimal numbers. The oneexception is the [mask] parameter for the .CRITICAL command, which is

hexadecimal.

10 Part Number 198007-0001 may be obtained from CALCULEX, Inc. P.O. Box 339, Las Cruces, NM

88004 (505) 525-0131 or by email request to [email protected].

6-41

7/31/2019 IRIG_106_2009



h. Three commands, .FIND, .REPLAY, and .SHUTTLE, have numeric parameters thatrequired units of measure. The [mode] parameter is used to specify the unit of

measure (time, feet, or blocks.) If the [mode] parameter is omitted, the recorder shall

use the most recently entered [mode].i. A [time] parameter value has five parts: days, hours, minutes, seconds, and

milliseconds. Any part not entered defaults to zero except days, which defaults todon’t care (current day). A period (“.”) identifies the start of the millisecond part, ahyphen (“-”) separates the day from the hours, and colon characters (“:”) separate the

hours, minutes, and seconds. The following are valid times: 123- (day only),

17 (hours only), 17:30 (hours and minutes), 17:30:05 (hours, minutes, seconds),

17:0:05 (hours, minutes, seconds), 17:30:05.232 (hours, minutes, seconds,milliseconds), 123-17 (day, hours), 123-17:30 (day, hours, minutes), etc.

j. All commands begin with an ASCII period (“.”) and, with the single exception of the

.TMATS command, end with a carriage return and line-feed terminator sequence.

6-42

7/31/2019 IRIG_106_2009



TABLE 6-15. COMMAND SUMMARY

Command Parameters* Description

.ASSIGN [destination-ID] [source-ID]Assign replay (output) channels to source (input)

channels.BBLIST {type} Returns list of secured or unsecured bad blocks

.BBREAD {block identifier} Returns contents of specified block

.BBSECURE {block identifier} Marks an unsecured bad block as secure

.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

.DUB [location] Same as .PLAY but with internal clock

.ERASE Erases the recording media

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

.FILES Displays information about each recorded file

.FIND [value [mode] ] Display current locations or find new play point

.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

.LOOP Starts record and play in read-after-write mode

.MEDIA Displays media usage summary

.MOUNT Powers and enables the recording media

.PAUSE Pause current replay

.PLAY [location][speed]Reproduce recorded data of assigned output

channels starting at [location] and at [speed]

.PUBLISH [keyword] [parameter] Configure, start and stop live data over the recorder

Ethernet interface

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

.REPLAY [endpoint [mode] ] Same as .SHUTTLE but with internal clock

.RESET Perform software initiated system reset

.RESUME Resume replay from pause condition

.SETUP [n]Displays or selects 1 of 16 (0…15) pre-

programmed data recording formats

.SHUTTLE [endpoint [mode] ]Play data repeatedly from current location to the

specified endpoint location using external clock .STATUS Displays the current system status

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

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

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

* Parameters in braces “{}” are required. Parameters in brackets “[]” are optional. When optional

parameters are nested (“[xxx [yy] ]”), the outer parameter (xxx) must be specified in order to also

specify the inner parameter (yy).

6-43

7/31/2019 IRIG_106_2009



6.8.2 Command Error Codes. Issuing invalid commands (bad syntax) or illegal commands(not accepted in the current system state) result in error code responses (with an ASCII “E”

identifier) prior to the asterisk response terminator when a command cannot be completed.

Table 6-16 shows possible error codes and the conditions under which they occur.

TABLE 6-16. COMMAND ERROR CODES

Error Description Conditions

00 INVALID COMMAND Command does not exist

01 INVALID PARAMETER Parameter is out of range, or wrong alpha-numeric type

02 INVALID MODE Command cannot be executed in the current state

03 NO MEDIA Recording media is dismounted or not installed

04MEDIA FULL Command cannot be executed because there is no free

space available on the recording media

05COMMAND FAILED Command failed to execute for any reason other than

those listed above

Example:

.RECORD

E 03

*

6.8.3 Command Parameters and Responses. Each of the commands, command parameters,

and recorder responses to the commands are described in the following sections.

6.8.3.1 .ASSIGN. The .ASSIGN [destination-ID] [source-ID] command shall be used for

assigning replay (output) channels to source (input) channels. The source-IDs are composedfrom the channel type of the source as defined in Chapter 9 parameter “CDT” — a ‘-‘ characterand the sequence number of that type of channel (e.g., “PCMIN-3” for the 3 rd PCM input

channel). The destination-IDs are composed similarly – but with an “OUT” tag in the Channel

Type, instead of an “IN” tag. Use keyword “NONE” in place of source-ID if a replay channel isto be unassigned. The command with the [destination-ID] parameter only should return the

actually assigned source-ID; without any parameters it should return the full list of assignments.

Examples:

.ASSIGN PCMOUT-2 PCMIN-7

*

.ASSIGN PCMOUT-1 NONE

*

.ASSIGN PCMOUT-2

PCMIN-7

*

6-44

7/31/2019 IRIG_106_2009



.ASSIGN

PCMOUT-1 NONE

PCMOUT-2 PCMIN-7

*

6.8.3.2 .BBLIST {type

}: A .BBLIST command shall be utilized to return the unsecured badblock identifiers (any ASCII text, one identifier per line) from the media. A BBLIST command

is only valid following a Declassify command. The type shall be provided indicating which type

of bad block list is to be returned. If type = “unsecured” .BBLIST shall return a list of unsecuredbad blocks. If type = “secured” .BBLIST shall return a list of secured bad blocks.

Example:

.BBLIST UNSECURED

1234

5678:

fff

*

6.8.3.3 .BBREAD {block identifier }: A Bad Block Read command shall be utilized to returnthe raw data from the specified bad block in ASCII hexadecimal format. The block identifier

shall be provided for the bad block to be read.

Example:

.BBREAD 5678

00040000

9E030000:

2CE42CE4*

6.8.3.4 .BBSECURE {block identifier }: A .BBSECURE command shall be utilized to mark

an unsecured bad block as being secured. A block that has been identified as secured shall never

be used for any subsequent data recording. Secured bad blocks shall be removed from unsecuredbad block identifier list. The block identifier shall be provided for the block to be secured.

Example:

.BBSECURE 5678*

6.8.3.5 .BIT. The .BIT command runs the built-in test (BIT) on the recorder. The prompt isreturned immediately after the test is started. The .BIT command is only valid in the IDLE,

ERROR, and FAIL states. During the BIT, the user must periodically check the status until the

test is complete. While in BIT mode, the percent completion is shown with the .STATUScommand. The result of the .BIT command is go/no-go status indicated by the end state. If the

6-45

7/31/2019 IRIG_106_2009



system returns to the IDLE state, the BIT was successful. If the system goes to the FAIL state,the BIT failed and further system-specific diagnostics are required. The ASCII “S” in the

response is the identifier of a .STATUS response.

Example:

.BIT

*

.STATUS

S 02 0 0 21%

*

.STATUS

S 02 0 0 74%

*

.STATUS

S 01 0 0

*

6.8.3.6 .CRITICAL [n [mask ] ]. The .CRITICAL command is used to view and specify the

critical warning masks used with the .HEALTH command. An encoded 32-bit status word is

displayed with the .HEALTH command for each feature as defined in .HEALTH command inthe recorder. The .CRITICAL command allows the user to specify which status word bits

constitute critical warnings. If a bit in the .CRITICAL mask word for a feature is set, then the

corresponding .HEALTH status word bit for that feature signals a critical warning. The criticalwarning is turning the FAULT contact output indicator ON for a Chapter 10 compatible

recorder.

Parameters in braces “{}” are required. Parameters in brackets “[]” areoptional. When optional parameters are nested (“[xxx [yy] ]”), the outer

parameter (xxx) must be specified in order to also specify the innerparameter (yy).

The .CRITICAL command without any parameters returns the mask word for eachfeature in ascending feature order. The .CRITICAL command with a single parameter (the

feature number) returns the list of descriptive warning strings and status word bit associations for

the specified feature. The .CRITICAL command with both the feature number parameter and the

8-character ASCII hexadecimal mask value parameter specifies a new mask value for the feature.All mask values in the command responses are hexadecimal.

The critical warning is turning the FAULT contact output indicator ON for

a Chapter 10 compatible recorder.

6-46

7/31/2019 IRIG_106_2009



Example #1: The command with no parameters returns the mask for each feature.

.CRITICAL

0 FFFFFFFF RECORDER

1 FFFFFFFF TIMEIN

2 000000FF ANAIN-1

3 0000006F PCMIN-1

4 0000000F PCMIN-2

:

:

15 00000010 1553IN-8

*

Example #2: The command with the feature number parameter only, no mask value,

returns all of the possible warning text strings for the specified featureand shows which .HEALTH status word bit is associated with the

particular warning.

.CRITICAL 4

4 00000004 PCMIN-2 Clock Error4 00000008 PCMIN-2 Data Error

4 00000010 PCMIN-2 No Minor Frame Lock

4 00000020 PCMIN-2 No Major Frame Lock

*

Example #3: Entering both the feature number parameter and the mask value

parameter resets the mask for the specified feature.

.CRITICAL 4 0000003C

4 0000003C PCMIN-2*

6.8.3.7 .DATE. The .DATE [start-date] command displays or sets the internal systems date.The optional start-date parameter is formatted as shown in the example below. Without aparameter, this command displays the current system date. The timestamps recorded with user

data are derived from this clock. The date shall be set in year-month-day format according to

ISO 8601.

Example:

.DATE

DATE 2002-12-31

*

6.8.3.8 .DECLASSIFY. The .DECLASSIFY command erases all recorded data using an

approved declassification procedure.

This command will permanently erase all recorded data. Data cannot berecovered once this command has been executed!

6-47

7/31/2019 IRIG_106_2009



The prompt is returned immediately after the operation is started. During declassify,the user must periodically check the status until the operation is complete. While in

DECLASSIFY state, the percent completion is shown with the .STATUS command.

Example:

.DECLASSIFY

*

.STATUS

S 04 0 0 23%

*

.STATUS

S

*

04 0 0 84%

.STATUS

S 01 0 0

*

6.8.3.9 .DISMOUNT. The .DISMOUNT command disables and, if necessary, removes power

from the active recording media. The media may be removed only after this command is issued.

Example #1:

.DISMOUNT

*

Example #2: If a failure occurs, an error message is displayed before the prompt.

.DISMOUNT

E 03*

6.8.3.10 .DUB [location]. The .DUB command is identical to the .PLAY command, except

that it specifies the use of the internal playback clock to retrieve the recorded data.

6.8.3.11 .ERASE. The .ERASE command erases all data and resets the record point to the

beginning of media (BOM).

This command will permanently erase all recorded data. Data cannot berecovered once this command has been executed!

6-48

7/31/2019 IRIG_106_2009



The prompt is returned immediately after the operation is started. During erase, theuser must periodically check the status until the operation is complete. While in ERASE state,

the percent completion is shown with the .STATUS command.

Example:

.ERASE

*

.STATUS

S 03 0 0 23%

*

.STATUS

S 03 0 0 84%

*

.STATUS

S 01 0 0

*

6.8.3.12 .EVENT [text string]. The .EVENT command adds an entry to the recorder event file

or displays all of the current event file entries. If a non-blank text string is included with the

command, a new event entry is appended to the event file with the text string in the messagefield of the event entry. The text string may be any length, but only the first 48 bytes, starting

with the first non-blank character but including all subsequent blanks, are saved in the event file

entry. If no text string is provided with the message, the current event file entries are displayed

as a list of character strings showing the event sequence number, the absolute event time basedon the recorder system time, the current media address (block number) at the time the event entry

is created, and the optional text string.

Example:

.EVENT -

*

.EVENT This text was supplied with the .EVENT command

*

.EVENT x

*

.EVENT

1 001-00:13:58.109 101231 -

2 001-00:14:11.106 433213 This text was supplied with

the .EVENT command

3 001-17:44:06.677 2427654 x

*

6.8.3.13 .FILES. The .FILES command displays a list of character strings showing informationabout each recording session (file). Each string in the list contains the file number, file name,

starting block number, file size in bytes, start day, and start time of the file. For those systems

that also store the end day and time of each file, the end day and time may be added to the end of each file string. File names may not contain space or asterisk characters. If user names are not

assigned to individual recordings, the default file names shall be “file1,” “file2,” etc. Each file

6-49

7/31/2019 IRIG_106_2009



string shall be formatted as shown in the following example (with optional end day and endtime).

Example:

.FILES (File name unused byte positions omitted)

1 TPD-10 10000 272760832 001-00:13:58.109 001-

00:14:03.826

2 TPD-11 92884 425984000 001-00:14:11.106 001-

00:14:28.602

3 file3 350790 305430528 123-17:44:06.677 123-

17:44:13.415

*

6.8.3.14 .FIND [value [mode]]. The .FIND command is used to report the current record and

play point or to set the play point to the desired location within the recorded data. The desired

location can be expressed in a number of different formats or “modes:” time, blocks, and feet.When the command is entered without any parameters, the recorder returns the current recordpoint and current play points, using the current default mode. The default mode is declared each

time a mode parameter is supplied with the .FIND command, the .REPLAY command, or the

.SHUTTLE command. Thereafter, the mode parameter may be omitted and the recorder will usethe default mode. The mode keywords are TIME, BLOCKS, and FEET.

The location specified in the value parameter of the .FIND command can be numericor one of six keywords: BOM (beginning of media), BOD (beginning of data), EOD (end of

data), EOM (end of media), BOF (beginning of file), and EOF (end of file.) These keywords

may be used with or without a mode parameter. Numeric location values, whether accompanied

by the mode keyword or not, must be valid for the specified or default mode. Blocks and feet areentered as decimal integer numbers. Time is entered as specified in paragraph 6.8.1 item i.

Example #1: Display the current record point and play point. The default mode isblocks.

.FIND

F 1022312 BOD

*

Example #2: Find a specific time in the recorded data.

.FIND 15:33:12 TIME

*

.STATUS

S 08 0 0 41%

*

.STATUS

S 08 0 0 84%

*

6-50

7/31/2019 IRIG_106_2009



.STATUS

S 01 0 0

*

.FIND

F 102-16:18:27.000 102-15:33:12.000

*

6.8.3.15 .HEALTH [ feature]. The .HEALTH command provides a standard mechanism for

status information to be conveyed to the user. The feature parameter is defined as 0 for recorder

status, and for each data source it is the decimal reference of the Channel ID specified by the“TK1” parameter for the corresponding data source by the TMATS setup. Entering the

command without the optional parameter displays a list of encoded status word for each feature.

Entering a decimal feature number parameter with the command decodes the status word for asingle feature and displays a list of messages pertaining to the feature, one for each set bit in the

status word; see Table 6-17 for recommended usage of the status bits. This standard requires

that the syntax of the responses to the .HEALTH command conform to the following rules:

a. If no data sources are implemented, the response to a .HEALTH command is therecorder status only.

b. In addition to the feature number the command should return a description of thecorresponding channel type, composed from the channel type of the source as

defined in Chapter 9 parameter “CDT” — a ‘-‘ character and the sequence number

of that type of channel (e.g., “PCMIN-3” for the 3rd

PCM input channel).c. The description of a feature may not contain an asterisk character.

d. The feature list response (no feature number parameter supplied with the

command) is a sequence of text strings, each containing the decimal featurenumber, the 8-character ASCII hexadecimal representation of the 32-bit status

word for the feature, a text feature description, and a carriage return and line feed

terminator. The value of the 32-bit status word for a “healthy” feature shall be allzeros. If a feature is disabled, the 8-character ASCII hexadecimal string shall bereplaced with eight ASCII hyphen “-” characters.

e. The individual feature response (feature number parameter supplied with the

command) is a sequence of descriptive text strings, one for each set bit in thefeature status word. Each string is terminated with a carriage return and line feed.

f. The critical bits should be cleared when they are reported by a .HEALTH

command.

The .CRITICAL command is used to specify and view the mask word for each featurethat determines if a set .HEALTH status word bit adds to the total non-critical or critical warning

counts displayed with the .STATUS command.

6-51

7/31/2019 IRIG_106_2009



TABLE 6-17. USE OF STATUS BITS

Feature Bit Mask (Hex) Description

Recorder 0 01 BIT Failure

1 02 Setup Failure

2 04 Operation Failure

3 08 Media Busy Unable to Accept Command

4 10 No Media

5 20 Media I/O Failure

6 40 Media Almost Full

7 80 Media Full

31-8 Vendor-Specific Health Status Bits

Time Code 0 01 BIT Failure

1 02 Setup Failure

2 04 No External Signal

3 08 Bad External Signal4 10 Synchronize Failure

5 20 Reserved for future Chapter 10 status bit




PCM 0 01 BIT Failure

1 02 Setup Failure

2 04 Bad Clock Failure

3 08 Bad Data Failure

4 10 Minor Frame Sync Failure

5 20 Major Frame Sync Failure6 40 Bit Sync Lock Failure

7 80 Watch Word Failure


1553 0 01 BIT Failure

1 02 Setup Failure

2 04 Response Timeout Error

3 08 Format Error

4 10 Sync Type or Invalid Word Error

5 20 Word Count Error


7 80 Watch Word Failure


6-52

7/31/2019 IRIG_106_2009



Table 6-17 Use Of Status Bits (Continued)

Feature Bit Mask (Hex) DescriptionVideo 0 01 BIT Failure

1 02 Setup Failure

2 04 No Video Signal Error3 08 Bad Video Signal Error

4 10 No Audio Signal Error

5 20 Bad Audio Signal Error




Analog 0 01 BIT Failure

1 02 Setup Failure

2 04 No Analog Signal Error

3 08 Bad Analog Signal Error






Image or Message 0 01 BIT Failure

1 02 Setup Failure

2 04 Bad Signal Error

3 08 Data Content Error




7 80 Reserved for future Chapter 10 status bit31-8 Vendor-Specific Health Status Bits

Other Types 0 01 BIT Failure

1 02 Setup Failure

2 04 Bad Signal Error

3 08 Data Content Error






6-53

7/31/2019 IRIG_106_2009



Example #1:

.HEALTH

0 00000000 SYSTEM

1 00000000 TIMEIN

2 00000000 ANAIN-1

3 -------- PCMIN-14 00000034 PCMIN-2

:

15 00000000 1553IN-8

Example #2:

*.HEALTH 4

4 00000004 PCMIN-2 Clock Error

4 00000010 PCMIN-2 No Minor Frame Lock

4 00000020 PCMIN-2 No Major Frame Lock

*

6.8.3.16 .HELP. The .HELP command displays a list showing a summary of the serial "dot"

commands and parameters supported by the system.

Example:

.HELP

.ASSIGN

.BBLIST

.BBREAD block identifier

.BBSECURE block identifier

.BIT

.CRITICAL [n [mask]]

.DATE

.DECLASSIFY

.DISMOUNT

.DUB [location]

.ERASE

.EVENT [message]

.FILES

.FIND [value [mode]]

.HEALTH [feature]

.HELP

.IRIG106

.LOOP

.MEDIA

.MOUNT

.PAUSE

.PLAY [location][speed]

.PUBLISH

.RECORD [filename]

.REPLAY [endpoint [mode]]

Example is continued on next page

6-54

7/31/2019 IRIG_106_2009



.RESET

.RESUME

.SETUP [n]

.SHUTTLE [endpoint [mode]]

.STATUS

.STOP [mode]

.TIME [start-time]

.TMATS {mode} [n]

*

6.8.3.17 .IRIG106. The .IRIG106 command returns the release version number of the IRIG-

106 Chapter 6 Recorder Command and Control Mnemonics that the recorder is supporting.

Because this command was introduced in IRIG-106-07, recorders supporting earlier releasesshould answer this command with “E00” error message (invalid command).

Example: The recorder CCM compatible with IRIG106-07.

.IRIG106

7

*

6.8.3.18 .LOOP. The .LOOP command is used to put the recorder into read-after-write mode,recording and simultaneously playing back the recorded data. The replayed data is read back

from the recording media. If the recorder is already recording when the .LOOP command is

issued, the command starts the playback at the current record point without affecting the

recording.

Example:

.STATUS

S 01 0 0*

.LOOP

*

.STATUS

S 07 0 0 35%

*

6.8.3.19 .MEDIA. The .MEDIA command displays the media usage summary. It shows the

number of bytes per block, the number of blocks used, and the number of blocks remaining,respectively.

Example:

.MEDIA

MEDIA 32768 1065349 6756127

*

6-55

7/31/2019 IRIG_106_2009



6.8.3.20 .MOUNT. The .MOUNT command applies power and enables the device forrecording. For systems with multiple memory canisters or media cartridges, the effect of the

.MOUNT command on each canister or media cartridge is defined in advance with vendor-

specific commands.

Example:

.MOUNT

*

6.8.3.21 .PAUSE. The .PAUSE command stops the replay operation. If parallel recording isbeing performed, it continues. If no play position is moved in between, the .RESUME command

can be used to continue replay. The .PAUSE can also be used to stop only the replay while the

recording continues (in this case, a new replay should be started with a new .PLAY command).

6.8.3.22 .PLAY [location] [speed]. The .PLAY command starts a playback of the data at either

the current play point or at the location specified in the optional parameter with the command.

The current play point is defined to be the media location immediately following the mostrecently played data. If no .PLAY command has been issued since recorder power-on, the

current play point is the beginning of data. The location parameter has two forms, which are

[block_number] and [filename [block_offset]]. If the first character of the location parameter isnumeric, the entire parameter must be numeric, specifying the block number address at which to

start the playback. When the first character of the location parameter is alphabetic, the parameter

is the filename to playback. It may have a second, optional parameter specifying the numeric 0-origin block offset into the named file. To begin playing at a location other than a block number

or file, use the .FIND command allows positioning of the play point to the desired location. The

optional [speed] parameter specifies the replay speed, if other than real time replay speed is

required. The syntax of the speed specification is: *N or /N (e.g., *5 for 5 times faster, /8 for 8times slower replay).

Example: Replay from the current position 4 times faster than real-time speed.

.PLAY file1 250

*

.PLAY *4

*

6.8.3.23 .PUBLISH keyword [parameter]. The .PUBLISH command shall be utilized forconfiguring, starting, and stopping UDP uni-, multi-, or broadcast of live data in IRIG106

Chapter 10 section 10.6 packet format over any IP interface to the recorder. The followingkeywords are allowed:

.PUBLISH START IPaddress PortAddress Channel-ID-List

(Start the streaming of the specified channel IDs to the destination address)

.PUBLISH STOP Channel ID-List

(Stop streaming of the specified channel IDs)

6-56

7/31/2019 IRIG_106_2009



The IPaddress PortAddress parameter defines the destination IP address and theport number of the UDP broadcast.

The Channel-ID-List parameter can be:- The keyword “ALL” means all available Channel ID

-

The decimal representation of one single Channel ID IAW IRIG106Chapter 10 Section 10.6.1.1.b- A range of Channel ID groups connected together by ‘-‘ character, it select

all channels within the specified range

- More than one Channel Id or Channel ID group separated by white space

(e.g. ‘ ‘) characters

The .PUBLISH command without any parameter returns the streaming Channel IDs

and their destinations.

Examples:

.PUBLISH START 192.145.255.255 1234 ALL

*

.PUBLISH START ::FFFF:C091:FFFF 1234 ALL

*

.PUBLISH

192.145.255.255 1234 ALL

*

.PUBLISH STOP ALL

*

.PUBLISH START 192.145.255.255 1234 1-12 18

*

.PUBLISH START 192.146.255.255 2345 13-17

*

.PUBLISH

192.145.255.255 1234 1-12 18

192.146.255.255 2345 13-17

*

6-57

7/31/2019 IRIG_106_2009



6.8.3.24 .RECORD [ filename]. The .RECORD command starts a new recording. The optionalfile name parameter is an ASCII string with up to eleven characters, beginning with an

alphabetic character, and with no spaces or asterisks. If the file name parameter is omitted, the

filename will be of the form “filen,” where n is the file number. The recording will continueuntil the recording media is full or until the .STOP command is issued.

Example:

.RECORD

*

6.8.3.25 .REPLAY [endpoint [mode]]. The .REPLAY command is identical to the .SHUTTLE

command, except that it specifies that the internal clock is to be used to retrieve the data.

6.8.3.26 .RESET. The .RESET command performs a software initiated reset of the recorder,

returning the recorder to the power-on state.

Example:

.RESET

*

6.8.3.27 .RESUME. The .RESUME command can be used to continue the replay from the

location where it was stopped by the .PAUSE operation — with the replay speed specified at the

last .PLAY command. If the play position was moved with the .FIND command since the.PAUSE command was used, the replay cannot be continued by the .RESUME command - a new

.PLAY command should be issued.

6.8.3.28 .SETUP [n]. The .SETUP command chooses one of 16 pre-defined setups stored inthe recorder. The optional parameter is a one or two digit decimal setup number from 0 to 15.

The current setup may be displayed by omitting the setup number parameter.

Example #1: Including the setup number changes the setting.

.SETUP 5

SETUP 5

*

Example #2:

.SETUP

SETUP 10

*

6-58

7/31/2019 IRIG_106_2009



6.8.3.29 .SHUTTLE [endpoint [mode]]. The .SHUTTLE command initiates a repeatedplayback from the current play point to the end point specified in the command, using an

external clock to retrieve the data. The syntax of the endpoint parameter is identical to that of

the .FIND command.

Example:

.SHUTTLE 1430 FEET

*

6.8.3.30 .STATUS. The .STATUS command displays the current state of the recorder and twocounts. The first is the total number of non-critical warning bits currently set and the second is

the total number of critical warning bits currently set. If the recorder is in any state other than

FAIL, IDLE, BUSY, or ERROR, the command also displays a progress percentage, the meaningof which is dependent on the specific state. Whenever the recorder is transitioning between

states and the transition is not instantaneous, the .STATUS command will return the BUSY state.

The ERROR state is entered when the currently executing command does not complete

successfully. For example, when a .FIND command is unable to locate the specified position onthe media, the recorder transitions to the ERROR state. Table 6-18 shows the various states by

numerical code and describes the meaning of the progress percentage for each state. An ASCII

“S” character identifies a .STATUS command response.

TABLE 6-18. RECORDER STATES

State Code State Name Progress Description

00 FAIL ---

01 IDLE ---02 BIT Percent complete

03 ERASE Percent complete

04 DECLASSIFY Percent complete

05 RECORD Percent media recorded

06 PLAY Percent recording played

07 RECORD & PLAY Percent media recorded

08 FIND Percent complete

09 BUSY ---

10 ERROR ---

6-59

7/31/2019 IRIG_106_2009



Example #1:

.STATUS

S 03 0 0 84%

*

Example #2: States that do not have a progress indication omit that field in the

response.

.STATUS

S 01 0 0

*

6.8.3.31 .STOP [mode]. The .STOP command stops a recording, playback, or both. The

optional mode parameter may be either the word RECORD or the word PLAY. If the optional

mode parameter is not specified, both recording and playing (or either of the two modes if theother is not active) will be stopped. Using the parameter enables either recording or playing to

be stopped without affecting the other, when both are active.

Example #1:

.STOP

*

Example #2: The current state can be displayed with the status command.

.STATUS

S

*

07 0 0 26%

.STOP PLAY

*

.STATUS

S 05 0 0 26%

*

Example #3: The .STOP command returns an error if the recorder is not in the

appropriate state.

.STATUS

S 01 0 0

*

.STOP

E 02

*

6-60

7/31/2019 IRIG_106_2009



6.8.3.32 .TIME [start-time]. The .TIME command displays or sets the internal systems time.The optional start-time parameter is formatted as shown in the example below. Without a

parameter, this command displays the current system time.

Example #1:

.TIME

TIME 001-23:59:59.123

*

Example #2: To set the time, enter a value expressed in days, hours, minutes, seconds

and milliseconds.

.TIME 123-13:01:35

TIME 123-13:01:35.000

*

Examples #3-5: Trailing values and punctuation may be omitted (zero is default).

Example #3:

.TIME 123-

TIME 123-00:00:00.000

*

Example #4:

.TIME 15:31

TIME 000-15:31:00.000

*

Example #5:

.TIME 15:31:20

TIME 000-15:31:20.000

*

6.8.3.33 .TMATS {mode} [n]. The .TMATS command provides a vendor-independent

mechanism for loading a setup file into the recorder and retrieving a setup file from the recorder.The required mode parameter must be one of the following four words: WRITE, READ, SAVE,

or GET. Writing or reading a TMATS file transfers the file between the external host and therecorder’s internal volatile memory buffer. Saving or getting a TMATS file transfers the filebetween the recorder’s internal volatile memory buffer and the recorder’s internal non-volatile

setup file storage area. To store a new setup file in the recorder, the .TMATS WRITE command

is first used to transfer the file to the recorder, followed by a .TMATS SAVE [n] command to

store the file in non-volatile memory. The numeric setup file number parameter is not valid withthe .TMATS WRITE command. When saving the file to non-volatile memory, the optional

setup file number parameter may be entered to designate a specific setup number (see the

6-61

7/31/2019 IRIG_106_2009



.SETUP command.) If the setup file number parameter is not specified with the .TMATS SAVEcommand, the file number defaults to setup 0. The .TMATS GET [n] command performs the

inverse of the .TMATS SAVE command, retrieving the specified or default (0) file from non-

volatile to volatile memory within the recorder. The .TMATS READ command transfers the filecurrently in the recorder’s volatile setup file buffer to the host.

Termination of the .TMATS WRITE command string is unique. All other commandstrings terminate with the first occurrence of a carriage return and line feed sequence. The

.TMATS WRITE command string does not terminate until the occurrence of a carriage return

and line feed pair followed by the word END and another carriage return and line feed pair.

Example #1: The .TMATS WRITE command includes the TMATS file followed by

the word END.

.TMATS WRITE

G\DSI\N=18;

G\DSI-1:TimeInChan1;

G\DSI-2:VoiceInChan1;G\DSI-3:1553Chan01;

:

:

P-8\IDC8-1:0;

P-8\ISF2-1:ID;

P-8\IDC5-1:M;

END

*

Example #2: The .TMATS READ command returns the file currently in the volatile

buffer.

.TMATS READ

G\DSI\N=18;

G\DSI-1:TimeInChan1;

G\DSI-2:VoiceInChan1;

G\DSI-3:1553Chan01;

:

:

P-8\IDC8-1:0;

P-8\ISF2-1:ID;

P-8\IDC5-1:M;

*

Example #3: The .TMATS SAVE command stores the file in the volatile buffer tothe designated non-volatile file memory in the recorder.

.TMATS SAVE 3

*

6-62

7/31/2019 IRIG_106_2009



Example #4: The .TMATS GET command retrieves the designated file from non-volatile file memory in the recorder and puts it in a buffer that can be

read by the user.

.TMATS GET 3

*

6.8.5 Command Validity Matrix. Table 6-19 identifies the recorder states in which each of the serial commands is valid. The legend at the bottom of the table explains the matrix entry

codes. Two codes, 3 and 4, identify states in which the associated command may or may not be

valid due to system-specific implementation. Recorder users should assume that a command isnot supported in a system-specific state (code 3 or 4) unless the specific recorder’s Interface

Control Document assures that support is provided.

6.8.6 Required Command Subset. Table 6-20 identifies the minimum subset of commands

that must be implemented for each recorder type to be compliant with this standard.

6-63

7/31/2019 IRIG_106_2009



TABLE 6-19. COMMAND VALIDITY MATRIX

STATE

COMMAND B U I L T - I N T E S T

B U S Y

D E C L A S S I F Y

E R A S E

E R R O R

F A I L

F I N D

I D L E

P L A Y

P O W E R O N

R E C O R D

R E C O R D &

P L A Y

.ASSIGN X X X X

.BBLIST 6

.BBREAD 6

.BBSECURE 6

.BIT X X X

.CRITICAL 1 1 1 1 1 1 1 1 1 1

.DATE 1 1 1 1 1 1 1 1 1 1

.DECLASSIFY X X

.DISMOUNT 2 2

.DUB X X X

.ERASE X X

.EVENT 3 3 3 3 3 3 3 3

.FILES X X X X X X X X

.FIND X X X

.HEALTH X X X X X X X X X X

.HELP X X X X X X X X X X

.IRIG106 X X X X X X X X X X X

.LOOP X X X

.MEDIA X X X X X X X X

.MOUNT 2 2

.PAUSE X X 4

.PLAY X X 4

.PUBLISH 5 5 5 5 5

.RECORD X 4 X 4

.REPLAY X X X

.RESET X X X X X X X X X X X

.RESUME X X 4

.SETUP 1 1 1 1 1 1 1 1 1 1

.SHUTTLE X X X

.STATUS X X X X X X X X X X X

.STOP X X X X

.TIME 1 1 1 1 1 1 1 1 1 1

.TMATS X X

LegendX= Always valid.

1 = Query function always valid. Changing masks, setup, or time only valid in IDLE or ERROR.

2 = MOUNT and DISMOUNT only valid if not mounted or dismounted, respectively.

3 = Query always valid. Declaring always valid in record, but not recording is system-specific.

4 = Simultaneous recording and playing is system-specific.

5 = Simultaneous recording, playing and publishing is system-specific.

6 = Only valid after declassify command execution has completed

6-64

7/31/2019 IRIG_106_2009



6-65

TABLE 6-20. REQUIRED COMMANDS

CommandRecorder Type

Tape Solid State Disk.ASSIGN O O O

.BBLIST O O O

.BBREAD O O O

.BBSECURE O O O

.BIT M M M

.CRITICAL M M M

.DATE M M M

.DECLASSIFY O M O

.DISMOUNT M M M

.DUB O O O

.ERASE M M M

.EVENT O O O

.FILES O M M

.FIND O O O

.HEALTH M M M

.HELP M M M

.IRIG106 M M M

.LOOP O O O

.MEDIA M M M

.MOUNT M M M

.PAUSE O O O

.PLAY O O O

.PUBLISH O O O

.RECORD M M M

.REPLAY O O O

.RESET M M M

.RESUME O O O

.SETUP M M M

.SHUTTLE O O O

.STATUS M M M

.STOP M M M

.TIME M M M

.TMATS M M M

Legend

M = Mandatory O = Optional

7/31/2019 IRIG_106_2009



CHAPTER 7 RESERVED FOR NEW TOPIC:

“GROUND BASED DIGITAL RECORDING STANDARD

(SOLID STATE AND DISK SYSTEMS)”

7/31/2019 IRIG_106_2009



CHAPTER 8

DIGITAL DATA BUS ACQUISITION FORMATTING STANDARD

TABLE OF CONTENTS


8.1 General............................................................................................................. 8-1

8.2 Word Structure................................................................................................. 8-1

8.3 Time Words ..................................................................................................... 8-3

8.4 Composite Output............................................................................................ 8-4

8.5 Single Bus Track Spread Recording Format ................................................... 8-5

8.6 MIL-STD-1553................................................................................................ 8-8

8.7 ARINC 429.................................................................................................... 8-12

LIST OF FIGURES

Figure 8-1. Word construction............................................................................................ 8-2

Figure 8-2. Composite frame structure............................................................................... 8-5

Figure 8-3. Multiple tape track spread format (4-track spread example)........................... 8-7

Figure 8-4. System block diagram...................................................................................... 8-9

Figure 8-5. MIL-STD-1553 formatted word construction. .............................................. 8-11

Figure 8-6. ARINC 429 formatted word construction. .................................................... 8-14

Figure 8-7. ARINC bit to formatted word bit mapping.................................................... 8-15

7/31/2019 IRIG_106_2009



ii


7/31/2019 IRIG_106_2009



CHAPTER 8

DIGITAL DATA BUS ACQUISITION FORMATTING STANDARD

8.1 General

This standard describes output data formats for the acquisition of all the traffic flowing

on various digital data buses. The formats permit the capture of data from multiple data buses

within a single system. Other constraints such as Radio Frequency (RF) bandwidth and tape

recording time will dictate the actual number of buses processed by a single system. Standards

for both composite telemetry Pulse Code Modulation (PCM) and tape recorder PCM formats are

presented.

Although specifically designed to satisfy the requirements of 100 percent MIL-STD-1553

bus and Aeronautical Radio Incorporated (ARINC) 429 channel acquisition, the formatting

provisions of this standard may be used in other applications when the data source and content

are similar enough to permit easy adaptation. Users should contact the appropriate range toensure any adaptations are compatible with that range.

In addition to the total data capture technique and format presented in this chapter;

“Selected Measurement” methods are available to acquire less than 100 percent of bus data.

Selected Measurement methods result in PCM formats conforming to Chapter 4 of this standard

and fall outside the scope of this chapter.

This chapter presents the general requirements for data formatting followed by individual

sections addressing specifics pertaining to MIL-STD-1553 and ARINC 429 respectively.

8.2 Word Structure

The following subparagraphs describe the general word structure to be used for the

formatted output. Specific word structures and definitions are provided as part of each

bus/channel subsection.

8.2.1 Field Definition. The formatted data shall be a 24-bit word constructed as shown in

Figure 8-1, part (a).

8.2.2 Most Significant Bit. The most significant bit (bit 1) of each formatted word may

optionally be an odd parity bit generated for the resulting formatted word or an additional bit

appended to the Bus/Group Identification Label as described in paragraph 8.2.3.

8.2.3 Bus/Group Identification Label. Each word shall also carry a Bus or Group Identification

Label as shown in Figure 8-1, part (b). For this application, a bus refers to a MIL-STD-1553 bus

(or dual redundant bus pair) and a group refers to a collection of up to four ARINC 429

channels. The Bus/Group Identification Label may optionally be three or four bits in length

dependent on the exercise of the option to use or not use a parity bit. If not used, the parity bit,

8-1

7/31/2019 IRIG_106_2009



or bit one (1), is appended to the Bus/Group Identification Label to increase the bus count from a

maximum of eight (3 bits) to a maximum of 16 (4 bits).

8.2.4 Content Identification Label. Each incoming bus word, auxiliary/user input, or time

word shall be appropriately labeled with a 4-bit Content Identification Label (see Figure 8-1

part (c)). Content Identification Labels are specific to each bus type and are detailed in later

sections.

8.2.5 Information Content Field. Data extracted from the data bus shall maintain bit order

integrity and be inserted into the Information Content field as specified for each bus type.

Transposing or reordering of the bits is not permitted.

BIT POSITION

1 2 3 4 5 6 7 8 9 10 11 12 21 22 23 24

P BUS / CONTENT

A GROUP IDENT I N F O R M A T I O N

R IDENT LABEL CONTENT

I LABEL

T

Y

OR

BUS IDENT

LABEL a. Field Definition

BIT BIT

1 2 3 4 1 2 3 4

0 0 0 0 BUS / GROUP 1 1 0 0 0 BUS /GROUP 9



0 0 1 1 BUS / GROUP 4 1 0 1 1 BUS /GROUP 120 1 0 0 BUS / GROUP 5 1 1 0 0 BUS /GROUP 13




b. Bus/Group Identification Label Definition; Bits (1) 2, 3, & 4

BIT BIT

5 6 7 8 5 6 7 8

1 1 1 1 0 1 1 1 TIME - HIGH ORDER

1 1 1 0 0 1 1 0 TIME - LOW ORDER

1 1 0 1 0 1 0 1 TIME - MICROSECOND

1 1 0 0 0 1 0 0 APPLICATION SPECIFIC1 0 1 1 0 0 1 1 USER DEFINED

1 0 1 0 0 0 1 0 USER DEFINED

1 0 0 1 0 0 0 1 FILL WORD

1 0 0 0 0 0 0 0 BUFFER OVERFLOW

c. Content Identification Label Definition; Bits 5, 6, 7, & 8

The function

of these codes

is dependenton the bus

type being

monitored

Figure 8-1. Word construction.

8-2

7/31/2019 IRIG_106_2009



8.2.6 Fill Words. Fill words, required to maintain continuous PCM output, shall have the

following sequence as the Information Content pattern:

1010 1010 1010 1010 (AAAA hexadecimal)

8.2.7 Content Identification Label. The Content Identification Label indicating bufferoverflow (0000) and appropriate Bus/Group Identification Label tag shall be appended to the

first word placed into the buffer after the buffer becomes available for data storage. This word

should be an "extra" word, not the next available piece of data. Bits nine (9) through 24 are

available for system level diagnostics and are not specified here. Tagging in this manner marks

the point of data discontinuity and preserves the integrity of the next piece of data.

8.2.8 Cyclic Redundancy Check (CRC). CRC is a very powerful technique for obtaining data

quality. An optional CRC word may be appended as the last positional word of each PCM frame

(see Figure 8-2). The CRC word shall be composed of Parity and/or Bus/Group Identification

Label, Content Identification Label, and 16 bits of a Frame Check Sequence (FCS). The FCS

shall fill the Information Content field (bits 9 – 24). The following CRC-16 polynomial shall beused to generate the FCS. None of the 24 bits making up the entire CRC word shall be used in

the calculation of the 16-bit FCS.

CRC-16 polynomial: X16 + X15 + X2 + 1

Exercise care when assigning bus identification and content identification

label codes to the CRC word. Although a positional word in the frame,

legacy-processing algorithms may falsely identify the information if one of

the bus data labels (1111 – 1000) is used as the content identification label.

8.3 Time Words

The following describes the structure and use of time words within the formatted output.

The time words dedicated to providing timing information are defined Chapter 4 of this

standard. These time words are designated as high order time, low order time, and microsecond

time. The MIL-STD-1553 bus data acquisition applications use an optional fourth time word,

designated as response time. The response time word has the same structure as the microsecond

time word. Time word structure shall follow the 16-bit per word format shown in Chapter 4,

Figure 4-3, and be placed into the Information Content field (bits nine (9) through 24) in bit

order.

8-3

7/31/2019 IRIG_106_2009



8.4 Composite Output

8.4.1 Characteristics of a Singular Composite Output Signal. The following subparagraphs

describe the characteristics for a singular composite output signal.

a.

The composite, continuous output shall conform to the requirements for Class 2pulse-code modulation as stated in Chapter 4 of this standard.

b. The data shall be transmitted most significant bit (bit 1) first.

c. The bit rate is dependent on several factors including bus loading and auxiliary inputs

and shall be set to a fixed rate sufficient to preclude any loss of data.

d. The order of bus words must remain unaltered except in the case of a buffer overflow.

e. The frame length shall be fixed using fill words as required and shall be > 128 words

and < 512 words including the frame synchronization word.

f. The frame synchronization word shall be fixed and 24 consecutive bits in length. The

pattern, also shown in Appendix C, table C-1, appendix C, is:

1111 1010 1111 0011 0010 0000 (FAF320 hexadecimal).

g. A frame structure employing frame time is recommended but optional. If frame time

is used, the frame structure shall consist of the frame synchronization word, followed

by the high order time word, followed by the low order time word, followed by the

microsecond time word, followed by the data words from all sources making up the

composite signal up to the frame length specified in subparagraph 8.4.1e above (alsosee Figure 8-2). If frame time is not used, the frame synchronization word shall be

followed immediately by the data words. If a Cyclic Redundancy Check word is not

used, the last word in the frame is data word N.

h. The following describes the recommended techniques for recording the composite

output signal.

1) Longitudinal recording shall conform to the PCM recording provisions

Appendix D of this standard.

2) Recording using parallel HDDR or rotary head recorders offers the advantage

of inputting a single high bit rate signal to the recording system. The inputPCM signal shall conform to the appropriate sections of this standard.

3) If recording using digital recorders or other noncontinuous recording

processes with buffered inputs, the fill words, inserted to provide a continuous

output stream, may be eliminated.

8-4

7/31/2019 IRIG_106_2009



Additional care must be exercised in data processing and reduction if the last

word in a composite stream is a MIL-STD-1553 command word. The

associated message time tag will not appear until after the synchronization

and time words in the next frame.

FRAME SYNC

PATTERN FRAME

HIGH TIME FRAME

LOW TIME FRAME

MICRO TIME DATA

WORD 1

DATA WORD N-2

DATA WORD N-1

DATA WORD N

CRC (OPTIONAL)

END OF FRAME

Figure 8-2. Composite frame structure.

8.5 Single Bus Track Spread Recording Format

8.5.1 Single Bus Recording Technique Characteristics. The following subparagraphs describe

the characteristics of a single bus recording technique using a multiple tape track spread output

format.

a. The target tape recorder/reproducer for a track spread format is a longitudinal

fixed-head machine described in Appendix D of this standard and not one employing

parallel high density digital recording (HDDR) or rotary head recording

characteristics.

b. The code generated for longitudinal tape recording shall be RNRZ-L or Bi-L as

described in Chapter 4 and Appendix D of this standard.

Bit rates less than 200 000 bits per second are not recommended when using

RNRZ-L.

8-5

7/31/2019 IRIG_106_2009



c. To extend recording time while still acquiring 100 percent of bus data, a multiple

track spread recording technique is presented as follows:

1) When necessary to use more than one tape recording track (to extend record

time), separate PCM streams shall be created and delayed by 24/TK bits with

respect to each other, where TK represents the number of tape tracks used for agiven bus.

2) When multiple track-spread recording is required, the track spread shall be on a

bus basis such as bus number 1 spread over four tracks, and bus number 2 spread

over two tracks. The maximum number of tracks per bus shall be limited to four.

Consideration should be given to spread track assignment. All tracks

associated with a given bus should be recorded on the same head stack.

3) Each stream shall have a frame synchronization pattern 24 bits in length,

conforming to subparagraph 8.4.1f .

4) The word structure shall be identical to that described in paragraph 8.2.

5) The frame length shall be fixed and shall be the same for each track used for a

given bus. The frame length shall conform to the requirements of

paragraph 8.4.1e.

6) The data shall be formatted such that it is transmitted (recorded) most significantbit (bit 1) first.

7) The use of a Cyclic Redundancy Check word as described in paragraph 8.2.8 is

optional. If used in the track spread application, a CRC word must be generated

and appended to each of the PCM frames for that bus.

8-6

7/31/2019 IRIG_106_2009



8) A structure employing frame time is recommended but optional. The following

describes a four-track spread example using frame time.

TK1. The PCM stream designated TK1 shall be constructed as the

frame synchronization word, followed by the high order frame time

word, followed by data words (see Figure 8-3).


frame synchronization word, followed by the low order frame time

word, followed by data words.


frame synchronization word, followed by the microsecond frame

time word, followed by data words.


frame synchronization word, followed by the first data word,followed by other data words.

Note: Schemes using one, two, or three tracks for a given bus shall follow like

construction; that is, sequencing through the data track by track. If frame time is

not used, data words shall immediately follow the frame synchronization patterns.

Additional care must be exercised in data processing and reduction if the last

word in the final track spread stream is a MIL-STD-1553 command word.

The associated message time tag will not appear until after the

synchronization and time words in the next frame.

TK1 FRAME SYNC

PATTERN

FRAME

HIGH TIME

DATA

WORD 2

DATA

WORD 6

TK2 FRAME SYNC

PATTERN

FRAME

LOW TIME

DATA

WORD 3

DATA

WORD 7

<> 24/TK bit times

TK3 FRAME SYNC

PATTERN

FRAME

MICRO TIME

DATA

WORD 4

DATA

WORD 8<> 24/TK bit times

TK4 FRAME SYNC

PATTERN

DATA

WORD 1

DATA

WORD 5

DATA

WORD 9

<> 24/TK bit times

Figure 8-3. Multiple tape track spread format (4-track spread example).

8-7

7/31/2019 IRIG_106_2009



8.6 MIL-STD-1553

The following subparagraphs describe specific formatting requirements for the

100 percent acquisition of MIL-STD-1553 bus information.

8.6.1 Definitions.

a. Bus Monitor. The terminal assigned the task of receiving bus traffic and extracting

all information to be used at a later time.

b. Data Bus. All hardware including twisted shielded pair cables, isolation resistors,

and transformers required to provide a single data path between the bus controller

and all associated remote terminals.

c. Dual Redundant Data Bus. The use of two data buses to provide multiple paths

between the subsystems.

d. Bus Loading. The percentage of time the data bus is active.

e. Maximum Burst Length. The maximum length of a continuous burst of messages

with minimum length message gaps.

f. Bus Error. A condition that violates the definition of MIL-STD-1553 word

structure. Conditions such as synchronization, Manchester, parity, noncontiguous

data word, and bit count/word errors are all considered word type errors. System

protocol errors such as incorrect word count/message and illegal mode codes, are not

considered bus errors.

8.6.2 Source Signal. The source of data is a signal conforming to MIL-STD-1553. Format

provisions are made for a dual redundant data bus system. The interface device performing the

data acquisition shall be configured as a bus monitor. Figure 8-4 depicts in block diagram form

the concept of 100 percent MIL-STD-1553 bus data acquisition.

8-8

7/31/2019 IRIG_106_2009



XMTR RCVR

TIME V T PE T A R

USER H . A P . O

USER I : 1 P E : 1 C

C E E O

1A U R S U

1B L R E S T

A E P I P

1553 R C R N U

DATA O O G T

BUSES U R DN . D U . U

16A I : 16 E C : 16 N

16B T R E

R

I

T

Figure 8-4. System block diagram.

In the design of the interface to the MIL-STD-1553 bus, it may be necessary

to include buffers to prevent loss of data and to conserve bandwidth. Thebuffer size is influenced by bus loading, maximum burst length, output bit

rate, tape recording speed, time tagging, and auxiliary inputs.

8.6.3 Word Structure. The specific word structure provisions to be used for MIL-STD-1553

bus formatted output are described below.

a. The formatted data shall be a 24-bit word constructed as shown in Figure 8-1 part (a)

and Figure 8-5 part (a).

b. The information extracted from the MIL-STD-1553 bus shall have the

synchronization pattern and parity bit removed.

c. Each incoming MIL-STD-1553 word (Command, Status or Data), auxiliary input or

time word shall be appropriately labeled with a 4-bit Content Identification Label as

described in Figure 8-1, part (c), and Figure 8-5, part (c).

d. Data extracted from the MIL-STD-1553 bus shall maintain bit order integrity in the

information field for a command, status, data, and error word. Bit position four (4) in

8-9

7/31/2019 IRIG_106_2009



the MIL-STD-1553 bus word shall be placed into bit position nine (9) in the

formatted data word. The remaining bits of the MIL-STD-1553 bus word shall be

placed in successive bit positions in the formatted data word. Transposing or

reordering of the bits is not permitted.

e.

For bus errors as defined in paragraph 8.6.1f (Error A - 1100 or Error B - 1000), thesynchronization pattern and the parity bit are removed as stated in

subparagraph 8.6.3.b. The Information Content bits, nine through 24, of the

formatted word shall contain the resulting 16-bit pattern extracted from the bus.

8-10

7/31/2019 IRIG_106_2009



BIT POSITION1 2 3 4 5 6 7 8 9 10 11 12 21 22 23 24

P BUS CONTENTA IDENT IDENT I N F O R M A T I O NR LABEL LABEL CONTENTITY

ORBUS IDENTLABEL

a. Field DefinitionBIT BIT

1 2 3 4 1 2 3 4

0 0 0 0 BUS 1 1 0 0 0 BUS 90 0 0 1 BUS 2 1 0 0 1 BUS 100 0 1 0 BUS 3 1 0 1 0 BUS 110 0 1 1 BUS 4 1 0 1 1 BUS 120 1 0 0 BUS 5 1 1 0 0 BUS 130 1 0 1 BUS 6 1 1 0 1 BUS 140 1 1 0 BUS 7 1 1 1 0 BUS 150 1 1 1 BUS 8 1 1 1 1 BUS 16

b. MIL-STD-1553 Bus/Group Identification Label Definition; Bits (1) 2, 3, & 4 BIT BIT

5 6 7 8 5 6 7 8

1 1 1 1 COMMAND A 0 1 1 1 TIME - HIGH ORDER1 1 1 0 STATUS A 0 1 1 0 TIME - LOW ORDER1 1 0 1 DATA A 0 1 0 1 TIME - MICROSECOND1 1 0 0 ERROR A 0 1 0 0 TIME - RESPONSE1 0 1 1 COMMAND B 0 0 1 1 USER DEFINED1 0 1 0 STATUS B 0 0 1 0 USER DEFINED1 0 0 1 DATA B 0 0 0 1 FILL WORD1 0 0 0 ERROR B 0 0 0 0 BUFFER OVERFLOW

NOTE:

A = rimar channel of the dual redundant bus; B = secondar

c. MIL-STD-1553 Content Identification Label Definition; Bits 5, 6, 7, & 8

Figure 8-5. MIL-STD-1553 formatted word construction.

8-11

7/31/2019 IRIG_106_2009



8.6.4 Time Words.

8.6.4.1 Time Tagging. If time tagging of the occurrence of MIL-STD-1553 messages is

necessary to satisfy user requirements, the first command word of the message shall be time

tagged. The time words shall immediately follow the first command word in the followingorder: high order time, low order time, and microsecond time.

8.6.4.2 Response Time Word. The optional response time word shall have one (1) microsecond

resolution and shall indicate the response time of the data bus. The response time word shall

immediately precede the status word associated with it.

If the response time function is not used, Content Identification Label 0100

may be assigned to user defined inputs.

8.7 ARINC 429

The following subparagraphs describe specific formatting requirements for the 100

percent acquisition of ARINC 429 channel information.

8.7.1 Definitions

a. Monitor. The receiver or sink assigned the task of receiving bus traffic and extracting

all information to be used at a later time.

b. Data Bus. All hardware including twisted shielded pair cables, required to provide a

single data path between the transmitter or source and the associated receivers or

sinks.

c. Channel Error. Conditions detected which violate the definition of ARINC 429 word

structure as specified in ARINC specification 429P1, 429P2, and 429P3. Conditions

such as parity and bit count/word errors are all considered among word type errors.

System protocol errors are not considered bus errors.

8-12

7/31/2019 IRIG_106_2009



8.7.2 Source Signal. The source of data is a signal conforming to ARINC 429. Format

provisions are made for up to 64 channels. The interface device performing the data acquisition

shall be configured as a monitor. In principle, Figure 8-4 depicts in block diagram form the

concept of 100 percent bus data acquisition.

8.7.3 Word Structure. The following descriptions contain specific word structure provisionsto be used for the ARINC 429 formatted output.

a. The formatted data shall be a 24-bit word constructed as shown in Figure 8-1 part (a)

and Figure 8-6 part (a).

b. Each incoming ARINC 429 word, auxiliary input, or time word shall be appropriately

labeled with a 4-bit Content Identification Label as described in Figure 8-1 part (c)

and Figure 8-6 part (c).

c. The format provides for addressing of up to 64 channels. Each Bus/Group

Identification Label (designated GROUP X) may be associated with up to 4independent ARINC 429 channels through the use of a High and Low Syllable

technique described in paragraph 8.7.3d below and shown in Figure 8-6.

d. Data extracted from the ARINC 429 channel shall maintain bit order integrity in the

Information Content field. Each ARINC 429 word is 32 bits in length. To

accommodate this word length within the described format, each ARINC word is

divided into two segments, each 16 bits in length. These segments will be referred to

as ARINC High Syllable and ARINC Low Syllable. Figure 8-7 describes the

mapping of the 32 bit ARINC 429 word into the Information Content bits (9 –24) of

the ARINC High and Low Syllable words. Transposing or reordering of the bits is

not permitted.

e. For channel errors defined in paragraph 8.7.1c, the following procedure shall be

followed. An error word shall be generated using the appropriate Bus/Group

Identification Label and 0100 as the Content Identification Label. Bits 9-12 shall

contain the Content Identification Label code associated with the appropriate ARINC

High Syllable channel, bits 13 – 16 shall contain the Content Identification Label for

the ARINC Low Syllable associated with that channel, and bits 17 – 24 are available

for system level diagnostics and are not specified here. The next occurrence of that

Bus/Group Identification Label coupled with those ARINC High and Low Syllable

Content Identification Labels shall contain the respective data extracted from the

channel that was deemed to be in error. The Information Content bits, nine (9)

through 24, of the formatted word shall contain the resulting 16-bit pattern syllables

as extracted from the channel.

8-13

7/31/2019 IRIG_106_2009



ARINC 429 FORMATTED WORD CONSTRUCTIONBIT POSITION1 2 3 4 5 6 7 8 9 10 11 12 21 22 23 24

P GROUP CONTENTA IDENT IDENT I N F O R M A T I O NR LABEL LABEL CONTENTITY

OR

GROUPIDENTLABEL

a. Field Definition

BIT BIT1 2 3 4 1 2 3 4

0 0 0 0 GROUP 1 1 0 0 0 GROUP 90 0 0 1 GROUP 2 1 0 0 1 GROUP 100 0 1 0 GROUP 3 1 0 1 0 GROUP 110 0 1 1 GROUP 4 1 0 1 1 GROUP 120 1 0 0 GROUP 5 1 1 0 0 GROUP 130 1 0 1 GROUP 6 1 1 0 1 GROUP 140 1 1 0 GROUP 7 1 1 1 0 GROUP 150 1 1 1 GROUP 8 1 1 1 1 GROUP 16

b. ARINC 429 Bus/Group Identification Label Definition; Bits (1) 2, 3, & 4 BIT BIT

5 6 7 8 5 6 7 8

1 1 1 1 High Syllable #4 0 1 1 1 TIME - HIGH ORDER1 1 1 0 Low Syllable # 0 1 1 0 TIME - LOW ORDER1 1 0 1 High Syllable #3 0 1 0 1 TIME - MICROSECOND1 1 0 0 Low Syllable # 0 1 0 0 ERROR1 0 1 1 High Syllable #2 0 0 1 1 USER DEFINED1 0 1 0 Low S llable # 0 0 1 0 USER DEFINED1 0 0 1 Hi h S llable #1 0 0 0 1 FILL WORD1 0 0 0 Low S llable # 0 0 0 0 BUFFER OVERFLOW

c. ARINC 429 Content Identification Label Definition; Bits 5, 6, 7, & 8

Figure 8-6. ARINC 429 formatted word construction.

8-14

7/31/2019 IRIG_106_2009



8-15

ARINC BIT TO FORMATTED WORD BIT MAPPING

9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24

a. Information Content field bits

32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17

b. ARINC High Syllable bit mapping

16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1

c. ARINC Low Syllable bit mapping

Figure 8-7. ARINC bit to formatted word bit mapping.

8.7.4 Time Words. If time tagging of the occurrence of ARINC 429 messages is necessary to

satisfy user requirements, the time words shall immediately follow the ARINC Low Syllable

word in the following order:

a. High order time

b. Low order time

c. Microsecond time.


7/31/2019 IRIG_106_2009



CHAPTER 9

TELEMETRY ATTRIBUTES TRANSFER STANDARD (TMATS)

TABLE OF CONTENTS

LIST OF FIGURES ........................................................................................................................ ii

LIST OF TABLES.......................................................................................................................... ii

9.1 GENERAL...................................................................................................................... 9-1

9.2 SCOPE ............................................................................................................................ 9-1

9.3 PURPOSE....................................................................................................................... 9-1

9.4 MEDIA AND DATA STRUCTURE............................................................................ 9-2

9.4.1 Physical Format ............................................................................................. 9-29.4.2 Logical Format............................................................................................... 9-29.4.3 XML (eXtensible Markup Language) Format............................................... 9-3

9.5 TELEMETRY ATTRIBUTES ..................................................................................... 9-3 9.5.1 Contents ......................................................................................................... 9-4

9.5.2 General Information (G). ............................................................................... 9-8

9.5.3 Transmission Attributes (T)......................................................................... 9-119.5.4 Recorder-Reproducer Attributes (R)............................................................ 9-17

9.5.5 Multiplex/Modulation (Mux/Mod) Attributes (M)...................................... 9-43

9.5.6 Digital Data Attributes................................................................................. 9-48

9.5.7 PAM Attributes (A). .................................................................................... 9-929.5.8 Data Conversion Attributes (C) ................................................................... 9-96

9.5.9 Airborne Hardware Attributes (H)............................................................. 9-1089.5.10 Vendor Specific Attributes (V).................................................................. 9-109

9.6 DATA DISPLAY STANDARD: DATA DISPLAY MARKUP LANGUAGE

(DDML)....................................................................................................................... 9-109 9.6.1 DDML Purpose and Objectives ................................................................. 9-110

9.6.2 DDML Layered Structure.......................................................................... 9-1109.6.3 DDML Global Element Glossary .............................................................. 9-111

CHANGES TO THIS EDITION OF CHAPTER 9

Updates to this Appendix are in blue font. The blue font indicates

either a completely new item or an update to a previously existingitem.

7/31/2019 IRIG_106_2009



ii

LIST OF FIGURES

Figure 9-1. Group relationships........................................................................................ 9-7

Figure 9-2. General Information Group (G)..................................................................... 9-8Figure 9-3. Transmission Attributes Group (T).............................................................. 9-12

Figure 9-4. Recorder-Reproducer Attributes Group (R). ............................................... 9-18Figure 9-5. Multiplex/Modulation Attributes Group (M)............................................... 9-44Figure 9-6. PCM Format Attributes Group (P). ............................................................. 9-49

Figure 9-7. PCM Measurement Description Group (D)................................................. 9-64

Figure 9-8. Bus Data Attributes Group (B). ................................................................... 9-77

Figure 9-9. Message Data Attributes Group (S)............................................................. 9-86Figure 9-10. PAM Attributes Group (A). ......................................................................... 9-92

Figure 9-11. Data Conversion Attributes Group (C)........................................................ 9-97

Figure 9-12. Layered Structure of DDML...................................................................... 9-110

LIST OF TABLES

Table 9-1. General Information Group (G) .................................................................... 9-9

Table 9-2. Transmission Attributes Group (T) ............................................................. 9-13

Table 9-3. Recorder-Reproducer Attributes Group (R) ............................................... 9-23

Table 9-4. Multiplex/Modulation Group (M) ............................................................... 9-45Table 9-5. PCM Format Attributes Group (P) .............................................................. 9-52

Table 9-6. PCM Measurement Description Group (D)................................................. 9-66

Table 9-7. Bus Data Attributes Group (B) .................................................................... 9-79Table 9-8. Message Data Attributes Group (S)............................................................. 9-88

Table 9-9. PAM Attributes Group (A) .......................................................................... 9-93Table 9-10. Data Conversion Attributes Group (C)........................................................ 9-99

Table 9-11. DDML Global Element Glossary .............................................................. 9-112

7/31/2019 IRIG_106_2009



CHAPTER 9

TELEMETRY ATTRIBUTES TRANSFER STANDARD (TMATS)

9.1 General

Telemetry attributes are those parameters required by the receiving/processing system toacquire, process, and display the telemetry data received from the test item/source. The

Telemetry Attributes Transfer Standard (TMATS) provides a common definition and format to

facilitate the transfer of information between the user and the test range and between ranges.

The telemetry attributes defined in this chapter provide the information required to set up thetelemetry receiving and processing equipment. The format, while not necessarily compatible

with any receiving/processing system, will allow test ranges or other receiving systems to

develop a computer conversion program to extract the information and to set up data required fortheir unique equipment configuration. Nonstandard parameter variations are not included in the

attribute tables later in the chapter, but may be included by exception in the comments section of

each attribute group.

The intent of this chapter is to cover, primarily, attributes and terminology included in or

consistent with the other chapters within this telemetry standards document (IRIG Standard 106,

Part I). For example, PCM format attributes should comply with the PCM standards as given inChapter 4. Other attributes are sometimes included for service and utility, but should not be

construed as endorsements apart from the other chapters.

9.2 Scope

The TMATS provides the definition of the telemetry attributes and specifies the media

and data format necessary to permit the transfer of the information required to set up the

telemetry receiving/processing functions at a test range. The standard does not conform to, nordoes it define, existing or planned capabilities of any given test range. The parameters includedin this document are defined by specific reference. Other nonstandard parameter

values/definitions may be included in the comments section of each group.

9.3 Purpose

The TMATS provides a common format for the transfer of information between the user

and a test range or between ranges (see Appendix H). This format will minimize the "station

unique" activities that are necessary to support any test item. In addition, TMATS is intended to

relieve the labor intensive process required to reformat the information by providing the

information on computer compatible media, thereby reducing errors and requiring lesspreparation time for test support.

9-1

7/31/2019 IRIG_106_2009



9.4 Media and Data Structure

A variety of physical and electronic media is available for use in exchanging attributeinformation. The most important factor in selecting a medium is that the parties involved agree

to using that specific medium. If any data compression (such as Backup/Restore or Zip/Unzip)

will be used, both parties should agree to its use.

A cover sheet describing the system that produced the attribute medium should

accompany the attribute information. A recommended format for the cover sheet is given in

Appendix I.

9.4.1 Physical Format. Attributes for each mission configuration are to be supplied in a single

physical file with contents as 7-bit ASCII coded characters. Line feed (LF) and carriage return(CR) may be used to improve readability of the information. Nonprintable characters will be

discarded by the destination agency prior to translating the attributes into telemetry system

configuration information.

For disks, multiple mission configurations may be provided on a single disk; however,

each configuration must be in a separate file identified in the disk directory. File names should

use the file extensions ‘.TXT’ to indicate a text file, or ‘.TMT’ or ‘.TMA’ to indicate a TMATSfile. A stick-on label and the accompanying cover sheet identify the file names corresponding to

the mission configuration used for each mission.

On magnetic tape, physical records may be any size up to 2048 bytes. A single end-of-

file (EOF) mark indicates the end of a mission configuration. Additional mission configurations

can be included in sequential files on a single tape. A double EOF is used to indicate the end of the last mission configuration on the tape. A stick-on label and an accompanying cover sheet

identifying the missions for each configuration are required.

9.4.2 Logical Format. Each attribute appears in the file as a unique code name and as a data

item. The code name appears first, delimited by a colon. The data item follows, delimited by asemicolon. Thus, an attribute is formatted as A:B; - where A is the code name and B is the data

item, in accordance with the tables in paragraph 9.5. Numeric values for data items may be

either integer or decimal. Scientific notation ( d.ddddddE ee) is allowed only for the specificdata items defined for its use in the tables in paragraph 9.5. For alphanumeric data items,

including keywords, either upper or lower case is allowed; all defined keyword values are shown

as upper case and enclosed in quotes in the tables in paragraph 9.5. Semicolons are not allowedin any data item (including comment items). Any number of attributes may be supplied within a

physical record; however, the number of attributes supplied is subject to the 2048 byte maximum

length limitation of a single physical record (see subparagraph 9.4.1 above). Attributes mayappear in any order.

The two basic types of attribute code names are single-entry and multiple-entry. Single-entry attributes are those for which there is only one data item. Multiple-entry attributes appear

once in the definition tables in paragraph 9.5 but have multiple items; these items are assigned a

number. The number appears in the code name preceded by a hyphen. For example, data source

9-2

7/31/2019 IRIG_106_2009



identifiers might have the following entries:

G\DSI-1:Aircraft;

G\DSI-2:Missile;G\DSI-3:Target;

The code name COMMENT may be used to interject comments to improve readability.The comment data items, such as G\COM, are intended to convey further details within the

TMATS file itself. Comments must follow the attribute logical format, as shown below:

COMMENT: This is an example of a comment;

Refer to paragraph 9.5 for detailed definitions of code names and attributes and

Appendix J for an example application of this standard.

9.4.3 XML (eXtensible Markup Language) Format. In addition to the code name format

described in paragraph 9.4.2, TMATS attributes can also be expressed in XML. The TMATSXML format is implemented as a standard XML schema (open the file Tmats.xml).

The TMATS XML schema is identical in content to the telemetry attributes described in

paragraph 9.5 below, with the following exceptions:

a. The schema contains only the Word/Frame location type in the "D" group and no

subframe definitions in the "P" group.b. There is a C group for each data link instead of only one C group in the TMATS file.

c. The schema has no counter ("\N") attributes; they are not needed in XML.d. Keyword attribute values are expanded for readability in the schema.

e. Date and time formats are different; the schema uses the XML standard date and time

formats (not the ones in paragraph 9.5).f. Text entries in the XML schema may contain semicolons; the code name format uses

the semicolon as a delimiter.

g. The XML schema implies order, while the code name format allows the attributes tobe given in any order.

In addition to the TMATS XML schema, there is a separate XML schema which

describes commonly used types of data displays. The schema is called Data Display MarkupLanguage (DDML). Refer to paragraph 9.6 for a description of this standard format for data

display definitions.

9.5 Telemetry Attributes

The description of the mission configuration includes all potential sources of data; these

sources are RF links, pre- or post-detected tapes, and onboard recorded tapes and storage media.

Each of these data sources has unique characteristics that must be defined. Each source is given

a unique identity and its characteristics are specifically defined in associated attribute fields. Inmultiplexed systems, each data stream is uniquely identified by a data link name, which is

related to the data source name.

9-3

http://tmats.xml/

http://tmats.xml/

7/31/2019 IRIG_106_2009



Only the information that is essential to define the attributes of asystem is required. Non-applicable information does not need to be

included in the file. However, all attribute information given is to

be provided in the specified format.

The attributes defined in this section proceed from the general level to the detailed level.

The groups, defined in terms of data to be entered, are:

a. General Information: Establishes the top-level program definition and identifies the

data sources.b. Transmission Attributes: Define an RF link. There will be one group for each RF

link identified in the General Information Group.

c. Recorder-Reproducer Attributes: Identify a tape or storage data source.

d. Multiplex/Modulation Attributes: Describe the FM/FM, FM/PM, or PM/PMmultiplex characteristics. Each multiplexed waveform must have a unique set of

attributes. For the analog measurement, the tie to the engineering units conversion is

made in this group.e. Digital Data Attributes: Are divided into four groups: the PCM Format Attributes,

the PCM Measurement Description, the Bus Data Attributes, and the Packet Format

Attributes.f. PCM Format Attributes: Define the PCM data format characteristics, including

subframes and embedded formats. Each PCM format will have a separate format

attributes group.g. PCM Measurement Descriptions: Define each PCM measurement within the overall

PCM format.h. Bus Data Attributes: Specify the PCM encoded MIL-STD-1553 or ARINC 429 bus

format characteristics, or the direct recorder track/channel MIL-STD-1553 or ARINC

429 bus format characteristics.

i. Message Data Attributes: Specify the message based data streams.

j. PAM Attributes: Contain the definition of the PAM system. It includes the PAMformat characteristics and measurement attributes. The tie to the engineering unit

conversion is made for the measurands contained in the PAM format.k. Data Conversion Attributes: Contain the data conversion information for all

measurements in this telemetry system. The calibration data and conversion

definition of raw telemetry data to engineering units is included. The tie to the

measurands of the telemetry systems defined in the previous groups is via themeasurement name.

l. Airborne Hardware Attributes: Define the configuration of airborne instrumentationhardware in use on the test item.

m. Vendor Specific Attributes: Provide information that is specific to a vendor.

9.5.1 Contents. The following subparagraphs discuss the organization of the attributes and

their relationships with the various groups.

9-4

7/31/2019 IRIG_106_2009



9.5.1.1 Organization. Attribute information is organized according to a hierarchical structure in

which related items are grouped and given a common heading. The number of levels varies

within the overall structure and is a function of the logical association of the attributes. At thehighest level, the telemetry attributes are defined for the following groups:

Identifier Title

G General Information

T Transmission Attributes

R Recorder-Reproducer Attributes

M Multiplexing/Modulation Attributes

P PCM Format Attributes

D PCM Measurement Description

B Bus Data Attributes

S Message Data Attributes

A PAM Attributes

C Data Conversion Attributes

H Airborne Hardware AttributesV Vendor Specific Attributes

Within the structure, a lower case letter, for example, n, p, or r, indicates a multiple entryitem with the index being the lower case letter. The range of these counters is from one to the

number indicated in another data entry, usually with the appendage \N.

Within the tables, the code name, definition, and maximum field size are given for eachindividual attribute. The maximum field size is intended to be a guideline indicating the

intended use of the attribute, and does not imply support of the maximum capacity by all ranges.

For example, the fact that the Number of Data Sources attribute is two characters long does not

mean that 99 data sources are supported. Each range should be consulted as to their specificcapabilities.

Code names denoted with a *R-CH10* shall indicate the minimumrequired IRIG 106 Chapter 10 TMATS Setup Record attributes. Code

names denoted with a *RO-CH10* shall indicate the minimum required

IRIG 106 Chapter 10 TMATS Setup Record attributes for portions of IRIG 106 Chapter 10 which are optional and/or supported data channel

dependent.

9-5

7/31/2019 IRIG_106_2009



9-6

9.5.1.2 Group Relationships. The interrelationships between the various groups are shownpictorially in Figure 9-1.

a. Data Source ID is unique within a General Information Group (G). It

ties the Transmission Group (T) or the Recorder-Reproducer Group

(R) or both to the G group and to the Multiplex/Modulation Group(M).

b. The tie from the M group to a PCM Group (P), or a PAM Group (A)is the Data Link Name.

c. The tie from the P group to an embedded P group is another Data Link

Name.d. The tie from the M group to the Data Conversion Group (C) for an

analog measurement is the Measurement Name.

e. The tie from the P group to the PCM Measurement Description

Group (D) or Bus Group (B) is the Data Link Name.f. The tie from the R group to the B group is from the Channel Data

Link Name or Sub-Channel Name (R) to the Data Link Name (B). g. The tie from the R group to the Message Data Group (S) is from the

Channel Data Link Name, Sub-Channel Name, or Network Name (R)

to the Data Link Name (S).

h. The tie from either the A, D, B or S group to the Data ConversionGroup is the Measurement Name.

7/31/2019 IRIG_106_2009



TMATS

Medium

FILE #1 FILE #2

G1 G2

DATASOURCE ID

DATASOURCEID

DATASOURCE ID

DATASOURCE ID

R1 T1 R2 T2

`

DATA SOURCE ID

CHANNEL

DATA LINK

NAME

DATA

SOURCE ID

CHANNEL

DATA LINK

NAME

DATA

SOURCE ID

M1 [OR] M2 [OR] M3

SUB-CHANNEL

NAME

DATALINK

NAME

SUB-CHANNEL

NAME

DATALINK

NAME

DATA

LINK(FM)

9 - 7

P1 (PCM) [OR] P2 (PCM)

(HOST)NAME

DATA NETWORK

LINK NAME NAME

DATA

LINK NAME

B1 B2 S1

(MESSAGE)(BUS) (BUS)D1

…

…

… … … ...MEAS.

NAME

MEAS.

NAME

MEAS.

NAME

MEAS.

NAME

MEAS.

NAME

MEAS.

NAME

MEAS.

NAME

MEAS.

NAME

MEAS.

NAME

MEAS.

NAME

C1 C2 C3 C4 C5 C6 C7 C8 C9 C10

Figure 9-1. Group relationships.

7/31/2019 IRIG_106_2009



9.5.2 General Information (G). The General Information Group provides overall programinformation. Figure 9-2 below gives the overall information that is included in this group.

Table 9-1 identifies and defines the data required including the dates associated with the detailed

information. Since the identification of the data sources is an integral part of the remaininggroups, each source must be uniquely identified.

General Information Group (G)CODENAME

REFERENCEPAGE

PROGRAM NAME (G\PN) (9-9)

TEST ITEM (G\TA) (9-9)

*INFORMATION

TMATS FILE NAME (G\FN)

IRIG 106 REVISION LEVEL (G\106)

ORIGINATION DATE (G\OD)

REVISION NUMBER (G\RN)

REVISION DATE (G\RD)

UPDATE NUMBER (G\UN)

UPDATE DATE (G\UD)

TEST NUMBER (G\TN)

NUMBER OF POINTS OF CONTACT (G\POC\N)

*POINT OF CONTACT (9-10)

NAME (G\POC1-n)

AGENCY (G\POC2-n)

ADDRESS (G\POC3-n)

TELEPHONE (G\POC4-n)

*DATA SOURCE IDENTIFICATION (9-10)

NUMBER OF DATA SOURCES (G\DSI\N)

DATA SOURCE ID (G\DSI-n)

DATA SOURCE TYPE (G\DST-n)

*TEST INFORMATION (9-10)

TEST DURATION (G\TI1)

PRE-TEST REQUIREMENT (G\TI2)

POST-TEST REQUIREMENT (G\TI3)

SECURITY CLASSIFICATION (G\SC) (9-11)

* COMMENTS

COMMENTS (G\COM) (9-11)

*Heading Only - No Data Entry

Figure 9-2. General Information Group (G).

9-8

7/31/2019 IRIG_106_2009



TABLE 9-1. GENERAL INFORMATION GROUP (G)

PARAMETER

MAXIMUM

FIELDSIZE

CODE

NAME DEFINITION

PROGRAM NAME 16 G\PN NAME OF PROGRAM

TEST ITEM 64 G\TA TEST ITEM DESCRIPTION IN TERMS OF

NAME, MODEL, PLATFORM, OR

IDENTIFICATION CODE, AS APPROPRIATE

INFORMATION

TMATS FILE

NAME

256 G\FN NAME OF THIS TMATS FILE

IRIG 106

REVISION LEVEL

2 G\106

*R-CH10*

VERSION OF IRIG 106 STANDARD USED TO

GENERATE THIS TMATS FILE

ORIGINATION DATE

10 G\OD DATE OF ORIGINATION OF THIS MISSION

CONFIGURATION.

DD - DAY MM - MONTH

YYYY – YEAR (MM-DD-YYYY)

REVISION

NUMBER

4 G\RN REVISION NUMBER ASSOCIATED WITH

THIS MISSION CONFIGURATION

REVISION DATE 10 G\RD DATE OF REVISION.

DD - DAY MM - MONTH


UPDATE

NUMBER

2 G\UN UPDATE NUMBER OF CURRENT CHANGE

WHICH HAS NOT BEEN INCORPORATED

AS A REVISION

UPDATE DATE 10 G\UD DATE OF UPDATE.

DD - DAY MM - MONTH


TEST NUMBER 16 G\TN TEST IDENTIFICATION

NUMBER OF

POINTS OF

CONTACT

1 G\POC\N NUMBER OF POINTS OF CONTACT TO BE

GIVEN

9-9

7/31/2019 IRIG_106_2009



Table 9-1 (Continued). General Information Group (G) Page 2 x 3

PARAMETER

MAXIMUM

FIELD

SIZE

CODE

NAMEDEFINITION

POINT OFCONTACT:

NAME

AGENCY

ADDRESS

TELEPHONE

24

48

48

20

G\POC1-n

G\POC2-n

G\POC3-n

G\POC4-n

LIST EACH OF THE RESPONSIBLEAGENCIES AND THEIR POINT OF

CONTACT.

DATA SOURCE IDENTIFICATION

NUMBER OF

DATA SOURCES

2 G\DSI\N

*R-CH10*

SPECIFY THE NUMBER OF DATA

SOURCES: FOR RF TELEMETRY

SYSTEMS, GIVE THE NUMBER OF

CARRIERS; FOR TAPE OR STORAGE

RECORDED DATA, IDENTIFY THENUMBER OF TAPE OR STORAGE

SOURCES.

DATA

SOURCE

ID

32 G\DSI-n

*R-CH10*

PROVIDE A DESCRIPTIVE NAME FOR

THIS SOURCE. EACH SOURCE

IDENTIFIER MUST BE UNIQUE.

DATA

SOURCE

TYPE

3 G\DST-n

*R-CH10*

SPECIFY THE TYPE OF SOURCE:

RF - ‘RF’ TAPE - ‘TAP’

STORAGE - ‘STO’

DISTRIBUTED SOURCE – ‘DSS’

DIRECT SOURCE – ‘DRS’

REPRODUCER – ‘REP’ OTHER - ‘OTH’

NOTE: PROVIDE THE ABOVE TWO ITEMS FOR EACH DATA SOURCE.

TEST INFORMATION

TEST

DURATION

4 G\TI1 APPROXIMATE DURATION OF TEST IN

HOURS.

PRE-TEST

REQUIREMENT

1 G\TI2 INDICATE WHETHER A PRE-TEST

REQUIREMENT IS APPLICABLE (‘Y’ OR‘N’). PROVIDE DETAILS IN COMMENTS

RECORD.

POST-TEST

REQUIREMENT

1 G\TI3 SPECIFY WHETHER A POST-TEST

REQUIREMENT IS APPLICABLE

(‘Y’ OR ‘N’). PROVIDE DETAILS IN

COMMENTS RECORD.

9-10

7/31/2019 IRIG_106_2009



Table 9-1 (Continued). General Information Group (G) Page 3 x 3

PARAMETER

MAXIMUM

FIELD

SIZE

CODE

NAMEDEFINITION

SECURITY

CLASSIFICATION

1 G\SC PROVIDE THE CLASSIFICATION OF

THE PROJECT DATA. PROVIDE A

DESCRIPTION OF THE

CLASSIFICATION GUIDE AND ANY

INFORMATION CONCERNING

DECLASSIFICATION AND/OR

DOWNGRADING IN COMMENTS

RECORD.

UNCLASSIFIED - ‘U’

CONFIDENTIAL - ‘C’

SECRET - ‘S’TOP SECRET - ‘T’

OTHER - ‘O’

COMMENTS

COMMENTS 1600 G\COM PROVIDE THE ADDITIONAL

INFORMATION REQUESTED OR ANY

OTHER INFORMATION DESIRED.

9.5.3 Transmission Attributes (T). The Transmission Attributes are presented graphically in

Figure 9-3 and specified in Table 9-2. The information contained within this group is used to setup the RF receiver through the detection and recovery of the baseband composite waveform.The format contains the information needed to configure the antenna and receiver subsystems.

Additional equipment inserted in a specific range configuration such as microwave or

other relay is intended to be transparent to the user and is not described under TransmissionAttributes.

Because the information is mutually exclusive, only the appropriate frequencymodulation (FM) or phase modulation (PM) system data set is required for a link.

9-11

7/31/2019 IRIG_106_2009



Transmission Attributes Group (T)CODENAME

REFERENCEPAGE

DATASOURCE ID

(T-x\ID) (9-13)

*SOURCE RF ATTRIBUTES

TRANSMITTER ID (T-x\TID)

FREQUENCY (T-x\RF1)RF BANDWIDTH (T-x\RF2)

DATA BANDWIDTH (T-x\RF3)

MODULATION TYPE (T-x\RF4)

TOTAL CARRIER MODULATION (T-x\RF5)

POWER (RADIATED) (T-x\RF6)

NUMBER OF SUBCARRIERS (T-x\SCO\N) (9-13)

SUBCARRIER NUMBER (T-x\SCO1-n) (9-14)

MODULATION INDEX (T-x\SCO2-n)

MODULATOR NON-LINEARITY (T-x\RF7)

*PREMODULATION FILTER (9-14)

BANDWIDTH (T-x\PMF1)

SLOPE (T-x\PMF2)

TYPE (T-x\PMF3)*TRANSMIT ANTENNA (9-14)

TRANSMIT ANTENNA TYPE (T-x\AN1)

TRANSMIT POLARIZATION (T-x\AN2)

ANTENNA LOCATION (T-x\AN3)

*ANTENNA PATTERNS (9-15)

DOCUMENT (T-x\AP)

*POINT OF CONTACT

NAME (T-x\AP\POC1)

AGENCY (T-x\AP\POC2)

ADDRESS (T-x\AP\POC3)

TELEPHONE (T-x\AP\POC4)

*GROUND STATION ATTRIBUTES (9-15)

IF BANDWIDTH (T-x\GST1)BASEBAND COMPOSITE BANDWIDTH (T-x\GST2)

*GAIN CONTROL (9-15)

AGC TIME CONSTANT (T-x\GST3)

OR

MGC GAIN SET POINT (T-x\GST4)

AFC/APC (T-x\GST5)

TRACKING BANDWIDTH (T-x\GST6)

POLARIZATION RECEPTION (T-x\GST7) (9-16)

*FM SYSTEMS (9-16)

OR DISCRIMINATOR BANDWIDTH (T-x\FM1)

DISCRIMINATOR LINEARITY (T-x\FM2)

*PM SYSTEMS (9-16)

PHASE LOCK LOOP BANDWIDTH (T-x\PLL)

*COMMENTS

COMMENTS (T-x\COM) (9-16)

* Heading Only – No Data Entry

Figure 9-3. Transmission Attributes Group (T).

9-12

7/31/2019 IRIG_106_2009



TABLE 9-2. TRANSMISSION ATTRIBUTES GROUP (T)

PARAMETER

MAXIMUM

FIELD

SIZE

CODE

NAMEDEFINITION

DATA SOURCE ID 32 T-x\ID DATA SOURCE ID CONSISTENT WITH

GENERAL INFORMATION GROUP

SOURCE RF ATTRIBUTES

TRANSMITTER ID 12 T-x\TID TRANSMITTER IDENTIFICATION

FREQUENCY 6 T-x\RF1 CARRIER FREQUENCY, IN MHz. IF

PROGRAMMABLE, ENTER ‘P’, AND

DEFINE IN COMMENTS RECORD.

RF BANDWIDTH 6 T-x\RF2 TOTAL RF BANDWIDTH (-60 dB) OF

MODULATED SIGNAL, IN MHz

DATA BANDWIDTH 6 T-x\RF3 COMPOSITE BASEBAND DATA

BANDWIDTH (3 dB), IN kHz.

MODULATION

TYPE

12 T-x\RF4 DEFINE THE MODULATION TYPE: ‘FM’

‘PM’ ‘BPSK’ ‘DPSK’ ‘QPSK’

‘FQPSK-B’ ‘FQPSK-JR’ ‘SOQPSK-TG’

‘MULTI-H CPM’ ‘OTHR’

TOTAL CARRIERMODULATION

6 T-x\RF5 FOR FM SYSTEM, DEFINE TOTALCARRIER DEVIATION, PEAK-TO-PEAK,

IN kHz. FOR PM SYSTEM, DEFINE

TOTAL PHASE MODULATION, PEAK-

TO-PEAK, IN RADIANS.

POWER

(RADIATED)

4 T-x\RF6 TOTAL TRANSMITTED POWER WHEN

MODULATED, IN WATTS

NUMBER OF

SUBCARRIERS

2 T-x\

SCO\N

NUMBER OF SUBCARRIERS IN THE

COMPOSITE BASEBAND WAVEFORM, n.

IF NONE, ENTER ‘NO’.

9-13

7/31/2019 IRIG_106_2009



Table 9-2 (Continued). Transmission Attributes Group (T) Page 2 x 4

PARAMETER

MAXIMUM

FIELD

SIZE

CODE

NAMEDEFINITION

SUBCARRIER

NUMBER

5 T-x\

SCO1-n

GIVE THE IRIG CHANNEL NUMBER FOR

THE SUBCARRIER. IF NONSTANDARD

SUBCARRIER, ENTER ‘NO’, AND

ENTER FREQUENCY IN THE

COMMENTS SECTION WHERE n IS AN

IDENTIFICATION TAG FOR THE

SUBCARRIER.

MODULATION

INDEX

4 T-x\

SCO2-n

SPECIFY THE MODULATION INDEX

FOR EACH SUBCARRIER IN THE

COMPOSITE WAVEFORM, AS

APPROPRIATE.

MODULATOR

NONLINEARITY

4 T-x\RF7 MODULATOR NONLINEARITY, IN

PERCENT

PREMODULATION FILTER

BANDWIDTH 6 T-x\PMF1 PRE-MODULATION COMPOSITE FILTER

BANDWIDTH, 3 dB CUT-OFF

FREQUENCY, IN kHz

SLOPE 2 T-x\PMF2 PRE-MODULATION FILTER

ASYMPTOTIC ROLL-OFF SLOPE,dB/OCTAVE

TYPE 2 T-x\PMF3 SPECIFY THE FILTER TYPE:

CONSTANT AMPLITUDE - ‘CA’

CONSTANT DELAY - ‘CD’

OTHER - ‘OT’

TRANSMIT ANTENNA

TRANSMIT

ANTENNA TYPE

16 T-x\AN1 TRANSMIT ANTENNA TYPE

TRANSMIT

POLARIZATION

4 T-x\AN2 TRANSMIT ANTENNA POLARIZATION.

‘RHCP’ ‘LHCP’ LINEAR - ‘LIN’

ANTENNA

LOCATION

16 T-x\AN3 DESCRIBE THE ANTENNA LOCATION.

9-14

7/31/2019 IRIG_106_2009




PARAMETER

MAXIMUM

FIELD

SIZE

CODE

NAMEDEFINITION

ANTENNA PATTERNS

DOCUMENT 16 T-x\AP IDENTIFY DOCUMENT HAVING

ANTENNA PATTERNS.

POINT OF CONTACT:

NAME

AGENCY

ADDRESS

TELEPHONE

24

48

48

20

T-x\

AP\POC1

T-x\

AP\POC2

T-x\

AP\POC3

T-x\

AP\POC4

IDENTIFY THE POINT OF CONTACT

FOR ADDITIONAL INFORMATION.

GROUND STATION ATTRIBUTES

IF BANDWIDTH 6 T-x\GST1 DEFINE THE IF BANDWIDTH (3 dB) IN

MHz.

BASEBAND

COMPOSITE

BANDWIDTH

6 T-x\GST2 DEFINE THE CUTOFF FREQUENCY

(3 dB), OF THE OUTPUT FILTER, IN kHz.

GAIN CONTROL

AGC TIME

CONSTANT

4 T-x\GST3 SPECIFY THE AGC TIME CONSTANT

DESIRED IN MILLISECONDS.

MGC GAIN

SET POINT

6 T-x\GST4 PROVIDE THE MANUAL GAIN

CONTROL SET POINT IN TERMS OF

RECEIVED SIGNAL STRENGTH, dBm.

AFC/APC 3 T-x\GST5 SPECIFY AUTOMATIC FREQUENCY

CONTROL (‘AFC’) OR AUTOMATICPHASE CONTROL (‘APC’) OR NONE

(‘NON’).

TRACKING

BANDWIDTH

4 T-x\GST6 SPECIFY TRACKING LOOP BAND-

WIDTH, IN Hz.

9-15

7/31/2019 IRIG_106_2009




PARAMETER

MAXIMUM

FIELD

SIZE

CODE

NAMEDEFINITION

POLARIZATION

RECEPTION

5 T-x\GST7 SPECIFY POLARIZATION TO BE USED:

RHCP - ‘RHCP’

LHCP - ‘LHCP’

BOTH - ‘BOTH’

BOTH WITH DIVERSITY COMBINING:

PRE-DETECTION-’B&DPR’

POST-DETECTION-’B&DPO’

DIVERSITY COMBINING (ONLY):

PRE-DETECTION-’PRE-D’POST-DETECTION-’POS-D’

OTHER - ‘OTHER’, SPECIFY IN

COMMENTS.

FM SYSTEMS

DISCRIMINATOR

BANDWIDTH

4 T-x\FM1 SPECIFY THE DISCRIMINATOR

BANDWIDTH REQUIRED, IN MHz.

DISCRIMINATOR

LINEARITY

4 T-x\FM2 SPECIFY THE REQUIRED LINEARITY

OVER THE BANDWIDTH SPECIFIED.

PM SYSTEMS

PHASE LOCK LOOPBANDWIDTH

4 T-x\PLL SPECIFY THE PHASE LOCKED LOOPBANDWIDTH.

COMMENTS

COMMENTS 1600 T-x\COM PROVIDE THE ADDITIONAL



9-16

7/31/2019 IRIG_106_2009



9.5.4 Recorder-Reproducer Attributes (R). This group describes the attributes required whenthe data source is a magnetic tape as specified in Appendix D or a data storage device as

specified in Chapter 10. In the case of the tape data link identification, each data source must be

identified. In some cases, the data source identification may be identical, particularly when thesame information has been received from different receiver sites, on different polarizations, or on

different carriers for redundancy purposes. Some of the information requested will be availableonly from the recording site or the dubbing location.

Figure 9-4 indicates the information required. Various categories of information have

been included. In the data section of the attributes, it will be necessary to repeat the items until

all of the data sources have been defined, including the multiple tracks, which contain groundstation data of interest. Table 9-3 defines the information required. Any nonstandard tape

recordings will require explanation in the comments and may require supplemental definition.

Recorder – Reproducer filtering and post process data filtering and overwrite will use

TMATS attributes to describe the requirements. Recorder – Reproducer channel types that

support filtering and overwrite will define these attributes. PCM channels will use R, P and Dattributes and bus channels will use R and B attributes to define filtering and overwrite

definitions.

9-17

7/31/2019 IRIG_106_2009



Recorder-Reproducer Attributes Group (R) CODE NAMEREFERENCE

PAGEDATA

SOURCE ID(R-x\ID) (9-23)

RECORDER-REPRODUCER ID (R-x\RID) (9-23)

RECORDER-REPRODUCER DESCRIPTION (R-x\R1)

*RECORDER-REPRODUCER MEDIA CHARACTERISTICS (9-23)

RECORDER-REPRODUCER MEDIA TYPE (R-x\TC1)

RECORDER-REPRODUCER MEDIA

MANUFACTURER(R-x\TC2)

RECORDER-REPRODUCER MEDIA CODE (R-x\TC3)

RECORDER-REPRODUCER MEDIA LOCATION (R-x\RML)

EXTERNAL RMM BUS SPEED (R-x\ERBS)

TAPE WIDTH (R-x\TC4)

TAPE HOUSING (R-x\TC5)

TYPE OF TRACKS (R-x\TT)

NUMBER OF TRACKS/CHANNELS (R-x\N)

RECORD SPEED (R-x\TC6)

DATA PACKING DENSITY (R-x\TC7)

TAPE REWOUND (R-x\TC8)

NUMBER OF SOURCE BITS (R-x\NSB)

*RECORDER-REPRODUCER INFORMATION (9-24)

RECORDER-REPRODUCER MANUFACTURER (R-x\RI1)

RECORDER-REPRODUCER MODEL (R-x\RI2)

ORIGINAL RECORDING (R-x\RI3)

ORIGINAL RECORDING DATE AND TIME (R-x\RI4)

*CREATING ORGANIZATIONPOINT OF CONTACT

(9-25)

NAME (R-x\POC1)

AGENCY (R-x\POC2)

ADDRESS (R-x\POC3)

TELEPHONE (R-x\POC4)

DATE AND TIME OF COPY (R-x\RI5)

*COPYING ORGANIZATIONPOINT OF CONTACT

(9-25)

NAME (R-x\DPOC1)

AGENCY (R-x\DPOC2)

ADDRESS (R-x\DPOC3)

TELEPHONE (R-x\DPOC4)

POST PROCESS MODIFIED RECORDING (R-x\RI6)

POST PROCESS MODIFICATION TYPE (R-x\RI7)

DATE AND TIME OF MODIFICATION (R-x\RI8)

*MODIFYING ORGANIZATIONPOINT OF CONTACT

NAME (R-x\MPOC1)

AGENCY (R-x\MPOC2)

ADDRESS (R-x\MPOC3)

TELEPHONE (R-x\MPOC4)

CONTINUOUS RECORDING ENABLED (R-x\CRE)

RECORDER-REPRODUCER SETUP SOURCE (R-x\RSS)

RECORDER SERIAL NUMBER (R-x\RI9)

Figure 9-4. Recorder-Reproducer Attributes Group (R). Page 1 x 5

9-18

7/31/2019 IRIG_106_2009



RECORDER FIRMWARE REVISION (R-x\RI10)

NUMBER OF MODULES (R-x\RIM\N)

MODULE ID (R-x\RIMI-n)

MODULE SERIAL NUMBER (R-x\RIMS-n)

MODULE FIRMWARE REVISION (R-x\RIMF-n)

NUMBER OF RMM’S (R-x\RMM\N)

RMM IDENTIFIER (R-x\RMMID-n)RMM SERIAL NUMBER (R-x\RMMS-n)

RMM FIRMWARE REVISION (R-x\RMMF-n)

*RECORDING EVENT DEFINITIONS (9-27)

RECORDING EVENTS ENABLED (R-x\EV\E)

NUMBER OF RECORDING EVENTS (R-x\EV\N)

RECORDER INTERNAL EVENTSENABLED

(R-x\EV\IEE)

*RECORDING EVENT (9-27)

EVENT ID (R-x\EV\ID-n)

EVENT DESCRIPTION (R-x\EV\D-n)

EVENT TYPE (R-x\EV\T-n)EVENT PRIORITY (R-x\EV\P-n) (9-28)

EVENT CAPTURE MODE (R-x\EV\CM-n)

EVENT INITIAL CAPTURE (R-x\EV\IC-n)

RECORDING EVENT LIMIT COUNT (R-x\EV\LC-n)

EVENT TRIGGER MEASUREMENTSOURCE

(R-x\EV\MS-n)

EVENT TRIGGER MEASUREMENTNAME

(R-x\EV\MN-n)

*RECORDING INDEX (9-29)

RECORDING INDEX ENABLED (R-x\IDX\E)

RECORDING INDEX TYPE (R-x\IDX\IT)* TIME INDEX TYPE ATTRIBUTE (9-29)

INDEX TIME VALUE (R-x\IDX\ITV)

OR

* COUNT INDEX TYPE ATTRIBUTE

INDEX COUNT VALUE (R-x\IDX\ICV)

*MIL-STD-1553 RECORDER CONTROL (9-29)

MESSAGE MONITOR RECORD CONTROLENABLED

(R-x\MRC\E)

CHANNEL ID NUMBER (R-x\MRC\ID)

MESSAGE RECORD CONTROL TYPE (R-x\MRC\RCT)

STOP-PAUSE COMMAND WORD (R-x\MRC\SPM)

START-RESUME COMMAND WORD (R-x\MRC\SRM) *DATA

TRACK NUMBER/ CHANNEL ID (R-x\TK1-n)

RECORDING TECHNIQUE (R-x\TK2-n)

DATA SOURCE ID (R-x\DSI-n) (9-30)

DATA DIRECTION (R-x\TK3-n) (9-30)

Figure 9-4. Recorder-Reproducer Attributes Group (R). (Page 2 x 5)

9-19

7/31/2019 IRIG_106_2009



RECORDER PHYSICAL CHANNEL NUMBER (R-x\TK4-n)

CHANNEL ENABLE (R-x\CHE-n)

CHANNEL DATA TYPE (R-x\CDT-n)

CHANNEL DATA LINK NAME (R-x\CDLN-n)

*DATA TYPE ATTRIBUTES

*PCM DATA TYPE ATTRIBUTES (9-31)PCM DATA TYPE FORMAT (R-x\PDTF-n)

DATA PACKING OPTION (R-x\PDP-n)

INPUT CLOCK EDGE (R-x\ICE-n)

INPUT SIGNAL TYPE (R-x\IST-n)

INPUT THRESHOLD (R-x\ITH-n)

INPUT TERMINATION (R-x\ITM-n)

OR PCM VIDEO TYPE FORMAT (R-x\PTF-n)

PCM RECORDER-REPRODUCERMINOR FRAME FILTERING ENABLED

(R-x\MFF\E-n)

PCM POST PROCESS OVERWRITE ANDFILTERING ENABLED

(R-x\POF\E-n)

PCM POST PROCESS OVERWRITE AND

FILTERING TYPE(R-x\POF\T-n)

*MIL-STD-1553 BUS DATA TYPEATTRIBUTES

(9-33)

MIL-STD-1553 BUS DATA TYPEFORMAT

(R-x\BTF-n)

ORMIL-STD-1553 RECORDER –REPRODUCER FILTERING ENABLED

(R-x\MRF\E-n)

MIL-STD-1553 POST PROCESSOVERWRITE AND FILTERINGENABLED

(R-x\MOF\T-n)

MIL-STD-1553 MESSAGE FILTERING

DEFINITION TYPE (R-x\MFD\FDT-n)

NUMBER OF MESSAGE FILTERINGDEFINITIONS

(R-x\MFD\N-n)

MESSAGE TYPE(R-x\MFD\MT-n-

m)

REMOTE TERMINAL ADDRESS(R-x\MFD\TRA-n-

m)

TRANSMIT/RECEIVE MODE(R-x\MFD\TRM-n-

m)

SUBTERMINAL ADDRESS(R-x\MFD\STA-n-m)

DATA WORD COUNT/MODE CODE(R-x\MFD\DWC-n-m)

RT/RT REMOTE TERMINAL ADDRESS(R-x\MFD\RTRA-n-m)

RT/RT SUBTERMINAL ADDRESS(R-x\MFD\RSTA-n-m)

RT/RT DATA WORD COUNT(R-x\MFD\RDWC-

n-m) *ANALOG DATA TYPE ATTRIBUTES (9-34)

ANALOG DATA TYPE FORMAT (R-x\ATF-n)

NUMBER OF ANALOG CHANNELS/PKT (R-x\ACH\N-n)

DATA PACKING OPTION (R-x\ADP-n)

SAMPLE RATE (R-x\ASR-n)

MEASUREMENT NAME (R-x\AMN-n-m) (9-35)


9-20

7/31/2019 IRIG_106_2009



DATA LENGTH (R-x\ADL-n-m)

BIT MASK (R-x\AMSK-n-m)

MEASUREMENT TRANSFER ORDER (R-x\AMTO-n-m)

SAMPLE FACTOR (R-x\ASF-n-m)

SAMPLE FILTER 3DB BANDWIDTH (R-x\ASBW-n-m)

AC/DC COUPLING (R-x\ACP-n-m)

RECORDER INPUT IMPEDANCE (R-x\AII-n-m)

INPUT CHANNEL GAIN (R-x\AGI-n-m)

INPUT FULL SCALE RANGE (R-x\AFSI-n-m)

INPUT OFFSET VOLTAGE (R-x\AOVI-n-m)

INPUT TYPE (R-x\AIT-n-m)

AUDIO (R-x\AV-n-m)

OR AUDIO FORMAT (R-x\AVF-n-m)

*DISCRETE DATA TYPE ATTRIBUTES (9-36)

DISCRETE DATA TYPE FORMAT (R-x\DTF-n)

DISCRETE MODE (R-x\DMOD-n)

SAMPLE RATE (R-x\DSR-n)

NUMBER OF DISCRETEMEASUREMENTS

(R-x\NDM\N-n)

MEASUREMENT NAME (R-x\DMN-n-m)

BIT MASK (R-x\DMSK-n-m)

OR MEASUREMENT TRANSFER ORDER (R-x\DMTO-n-m)

*ARINC 429 BUS DATA TYPE ATTRIBUTES (9-37)

ARINC 429 BUS DATA TYPE FORMAT (R-x\ABTF-n)

NUMBER OF ARINC 429 SUB-CHANNELS

(R-x\NAS\N-n)

ARINC 429 SUB-CHANNEL NUMBER (R-x\ASN-n-m)

OR ARINC 429 SUB-CHANNEL NAME (R-x\ANM-n-m)

*VIDEO DATA TYPE ATTRIBUTES (9-37)

VIDEO DATA TYPE FORMAT (R-x\VTF-n)MPEG-2 CHANNEL XON2 FORMAT (R-x\VXF-n)

VIDEO SIGNAL TYPE (R-x\VST-n)

VIDEO SIGNAL FORMAT TYPE (R-x\VSF-n)

VIDEO CONSTANT BIT RATE (R-x\CBR-n)

VIDEO VARIABLE PEAK BIT RATE (R-x\VBR-n)

OR VIDEO ENCODING DELAY (R-x\VED-n)

OVERLAY ENABLED (R-x\VCO\OE-n)

OVERLAY X POSITION (R-x\VCO\X-n)

OVERLAY Y POSITION (R-x\VCO\Y-n)

OVERLAY EVENT TOGGLE ENABLED (R-x\VCO\OET-n)

OVERLAY FORMAT (R-x\VCO\OLF-n)

OVERLAY BACKGROUND (R-x\VCO\OBG-n)

ANALOG AUDIO CHANNEL INPUTLEFT

(R-x\ASI\ASL-n)

ANALOG AUDIO CHANNEL INPUTRIGHT

(R-x\ASI\ASR-n)

VIDEO DATA ALIGNMENT (R-x\VDA-n)


9-21

7/31/2019 IRIG_106_2009



*TIME DATA TYPE ATTRIBUTES (9-39)

TIME DATA TYPE FORMAT (R-x\TTF-n)

TIME FORMAT (R-x\TFMT-n)

OR TIME SOURCE (R-x\TSRC-n)

*IMAGE DATA TYPE ATTRIBUTES (9-40)

IMAGE DATA TYPE FORMAT (R-x\ITF-n)

OR STILL IMAGE TYPE (R-x\SIT-n)

*UART DATA TYPE ATTRIBUTES (9-40)

UART DATA TYPE FORMAT (R-x\UTF-n)

NUMBER OF UART SUB-CHANNELS (R-x\NUS\N-n)

UART SUB-CHANNEL NUMBER (R-x\USCN-n-m)

OR UART SUB-CHANNEL NAME (R-x\UCNM-n-m)

UART SUB-CHANNEL BAUD RATE (R-x\UCR-n-m)

UART SUB-CHANNEL BITS PER WORD (R-x\UCB-n-m)

UART SUB-CHANNEL PARITY (R-x\UCP-n-m)

UART SUB-CHANNEL STOP BIT (R-x\UCS-n-m)

UART SUB-CHANNEL INTERFACE (R-x\UCIN-n-m)

UART SUB-CHANNEL BLOCK SIZE (R-x\UCBS-n-m)

UART SUB-CHANNEL SYNC WORDLENGTH

(R-x\UCSL-n-m)

UART SUB-CHANNEL BLOCK SYNCVALUE

(R-x\UCSV-n-m)

UART SUB-CHANNEL BLOCK RATE (R-x\UCBR-n-m)

*MESSAGE DATA TYPE ATTRIBUTES (9-41)

MESSAGE DATA TYPE FORMAT (R-x\MTF-n)

NUMBER OF MESSAGE SUB-

CHANNELS(R-x\NMS\N-n)

MESSAGE SUB-CHANNEL NUMBER (R-x\MSCN-n-m)

OR MESSAGE SUB-CHANNEL NAME (R-x\MCNM-n-m)

*IEEE-1394 DATA TYPE ATTRIBUTES (9-42)

OR IEEE-1394 DATA TYPE FORMAT (R-x\IETF-n)

*PARALLEL DATA TYPE ATTRIBUTES (9-42)

OR PARALLEL DATA TYPE FORMAT (R-x\PLTF-n)

*ETHERNET DATA TYPE ATTRIBUTES (9-42)

ETHERNET DATA TYPE FORMAT (R-x\ENTF-n)

NUMBER OF ETHERNET NETWORKS (R-x\NNET\N-n)

ETHERNET NETWORK NUMBER (R-x\ENBR-n-m)

ETHERNET NETWORK NAME (R-x\ENAM-n-m)

*REFERENCE TRACK (9-42)

NUMBER OF REFERENCE TRACKS (R-x\RT\N)

TRACK NUMBER (R-x\RT1-n)

REFERENCE FREQUENCY (R-x\RT2-n)

*COMMENTS

COMMENTS (R-x\COM) (9-43)


Figure 9-4. Recorder-Reproducer Attributes Group (R). (Page 5 x 5)

9-22

7/31/2019 IRIG_106_2009



TABLE 9-3. RECORDER-REPRODUCER ATTRIBUTES GROUP (R)

MAX

PARAMETER FIELD

SIZE

CODE

NAMEDEFINITION

DATA SOURCE ID 32 R-x\ID

*R-CH10*

DATA SOURCE ID CONSISTENT WITH

GENERAL INFORMATION GROUP

RECORDER-

REPRODUCER ID

32 R-x\RID

*R-CH10*

RECORDER-REPRODUCER

IDENTIFICATION

RECORDER-

REPRODUCER

DESCRIPTION

32 R-x\R1 RECORDER-REPRODUCER DESCRIPTION

RECORDER-REPRODUCER MEDIA CHARACTERISTICS

RECORDER-

REPRODUCER

MEDIA TYPE

4 R-x\TC1 SPECIFY THE RECORDER-REPRODUCER

MEDIA TYPE:

ANALOG - ‘ANAL’

CASSETTE - ‘CASS’

HDDR - ‘HDDR’

PARALLEL - ‘PARA’

SOLID STATE RECORDER - ‘SSR’

MAGNETIC DISK - ‘MD’

NONE – ‘N’, DATA PUBLISHING ONLY

OTHER - ‘OTHR’, DEFINE IN COMMENTS

RECORD.

RECORDER-REPRODUCER

MEDIA

MANUFACTURER

8 R-x\TC2 NAME OF MANUFACTURER OF THERECORDER-REPRODUCER MEDIA

RECORDER-

REPRODUCER

MEDIA CODE

8 R-x\TC3 SPECIFY MANUFACTURER’S RECORDER-

REPRODUCER MEDIA DESIGNATION

CODE.

RECORDER –

REPRODUCER

MEDIA LOCATION

1 R-x\RRML

*R-CH10*

INDICATES THE LOCATION OF THE

RECORDER-REPRODUCER MEDIA.

‘I’ = INTERNAL, ‘E’ = EXTERNAL,

‘B’ = BOTH INTERNAL AND EXTERNAL

EXTERNAL RMM

BUS SPEED

5 R-x\ERBS

*R-CH10*

INDICATES THE SPEED OF AN EXTERNAL

RMM IEEE-1394B BUS.

“AUTO”

“S100”

“S200”

“S400”

“S800”

“S1600”

“S3200”

9-23

7/31/2019 IRIG_106_2009



Table 9-3 (Continued). Recorder-Reproducer Attributes Group (R) Page 2 x 21

MAX

PARAMETER FIELD

SIZE

CODE

NAMEDEFINITION

TAPE WIDTH 4 R-x\TC4 PHYSICAL DIMENSION OF TAPE WIDTH,

IN INCHES

TAPE HOUSING 5 R-x\TC5 STATE THE REEL SIZE, INCHES:

‘10.5’ ‘14.0’ ‘15.0’ ‘16.0’ ‘OTHER’

STATE THE CASSETTE SIZE, MM:

‘12.65’ ‘19.0’ ‘OTHER’

TYPE OF TRACKS 2 R-x\TT STATE THE TYPE OF TRACKS ON THE

TAPE: LONGITUDINAL - ‘LO’

ROTARY - ‘RO’

NUMBER OF

TRACKS/

CHANNELS

5 R-x\N

*R-CH10*

STATE THE NUMBER OF TRACKS ON THE

TAPE OR THE NUMBER OF CHANNELS ON

THE STORAGE MEDIA.

RECORD SPEED 4 R-x\TC6 STATE RECORD SPEED (inches/second).

DATA PACKING

DENSITY

2 R-x\TC7 STATE RECORDING SYSTEM

BANDWIDTH:

INTERMEDIATE BAND - ‘IM’

WIDE BAND - ‘WB’

DOUBLE DENSITY - ‘DD’

OTHER - ‘OT’

TAPE REWOUND 1 R-x\TC8 YES - ‘Y’ NO - ‘N’

NUMBER OF

SOURCE BITS

2 R-x\NSB

*R-CH10*

NUMBER OF MOST SIGNIFICANT BITS OF

THE CHANNEL ID USED FORMULTIPLEXER SOURCE ID. DEFAULT ISZERO (ONE SOURCE).

RECORDER-REPRODUCER INFORMATION

RECORDER-

REPRODUCER

8

MANUFACTURER

R-x\RI1 NAME OF RECORDER-REPRODUCER

DEVICE MANUFACTURER

RECORDER-

REPRODUCER

MODEL

8 R-x\RI2 MANUFACTURER’S MODEL NUMBER OF

RECORDER-REPRODUCER DEVICE USED

TO CREATE THE RECORDING

ORIGINAL

RECORDING

1 R-x\RI3

*R-CH10*

INDICATES IF THIS IS AN ORIGINAL

RECORDING FROM THE SOURCE

YES - ‘Y’ NO - ‘N’

9-24

7/31/2019 IRIG_106_2009




MAX

PARAMETER FIELD

SIZE

CODE

NAMEDEFINITION

ORIGINAL

RECORDING DATE

AND TIME

19 R-x\RI4 DATE AND TIME ORIGINAL RECORDING

WAS CREATED:

DD - DAY MM - MONTH

YYYY - YEAR HH - HOUR

MI – MINUTE SS - SECOND

(MM-DD-YYYY-HH-MI-SS)

CREATING

ORGANIZATION

POC:

NAME

AGENCY

ADDRESSTELEPHONE

24

48

4820

R-x\POC1

R-x\POC2

R-x\POC3R-x\POC4

POINT OF CONTACT AT THE FACILITY

CREATING THE TAPE OR STORAGE

MEDIA: NAME, AGENCY, ADDRESS, AND

TELEPHONE

DATE AND TIME OF

COPY

19 R-x\RI5

*RO-CH10*

DATE AND TIME THE COPY WAS MADE:

DD – DAY MM – MONTH

YYYY – YEAR HH – HOUR

MI – MINUTE SS - SECOND


COPYING

ORGANIZATION

POC:

NAME

AGENCY

ADDRESS

TELEPHONE

24

48

48

20

R-x\DPOC1

R-x\DPOC2

R-x\DPOC3

R-x\DPOC4

POINT OF CONTACT AT THE COPYING

AGENCY: NAME, ADDRESS, AND

TELEPHONE

POST PROCESS

MODIFIED

RECORDING

1 R-x\RI6

*R-CH10*

INDICATES MODIFIED RECORDING

YES - ‘Y’, NO - ‘N’

POST PROCESS

MODIFICATION

TYPE

2 R-x\RI7

*R-CH10*

INDICATES THE TYPE OF POST PROCESS

MODIFICATION TO THE RECORDING

‘1’ = TIME SUBSET

‘2’ = CHANNEL SUBSET

‘3’ = TIME - CHANNEL SUBSET

‘4’ = CHANNEL SUPERSET

‘5’ = TIME SUBSET - CHANNEL SUPERSET

‘6’ = FILTER

‘7’ = OVERWRITE

9-25

7/31/2019 IRIG_106_2009




MAX

PARAMETER FIELD

SIZE

CODE

NAMEDEFINITION

DATE AND TIME OF

MODIFICATION

19 R-x\RI8

*RO-CH10*

DATE AND TIME THE COPY WAS MADE:

DD – DAY

MM – MONTH

YYYY – YEAR

HH – HOUR

MI – MINUTE

SS – SECOND


MODIFYING

ORGANIZATIONPOC:

NAME

AGENCY

ADDRESS

TELEPHONE

24

48

48

20

R-x\MPOC1

R-x\MPOC2

R-x\MPOC3

R-x\MPOC4

POINT OF CONTACT AT THEMODIFYING AGENCY: NAME,

ADDRESS, AND TELEPHONE

CONTINUOUS

RECORDING

ENABLED

1 R-x\CRE

*R-CH10*

INDICATES IF CONTINUOUS RECORDING

IS ENABLED.

‘T’ = TRUE, ‘F’ = FALSE

RECORDER –

REPRODUCERSETUP SOURCE

2 R-x\RSS

*R-CH10*

INDICATES THE RECORDER-

REPRODUCER SETUP SOURCE.‘R’ = SETUP FILE ON RMM ONLY

‘C’ = COMMAND SETUP FILE ONLY

‘RP’ = RMM PRIMARY – COMMAND

SECONDARY

‘CP’ = COMMAND PRIMARY – RMMSECONDARY

RECORDER SERIAL

NUMBER

64 R-x\RI9 SERIAL NUMBER OF THE RECORDER

RECORDER

FIRMWAREREVISION

256 R-x\RI10 FIRMWARE REVISION NUMBER FOR

THE RECORDER

NUMBER OF

MODULES

3 R-x\RIM\N NUMBER OF MODULES IN THERECORDER

MODULE ID 64 R-x\RIMI-n IDENTIFY THIS MODULE

9-26

7/31/2019 IRIG_106_2009




MAX

PARAMETER FIELD

SIZE

CODE

NAMEDEFINITION

MODULE SERIAL

NUMBER

64 R-x\RIMS-n SERIAL NUMBER OF THIS MODULE

MODULE

FIRMWARE

REVISION

256 R-x\RIMF-n FIRMWARE REVISION NUMBER FOR

THIS MODULE

NUMBER OF RMM’S2

R-x\RMM\NNUMBER OF REMOVABLE MEMORYMODULES (RMM)

RMM IDENTIFIER 64 R-x\RMMID-n IDENTIFY THIS RMM

RMM SERIAL

NUMBER

64 R-x\RMMS-n SERIAL NUMBER OF THE RMM

RMM FIRMWARE

REVISION

256 R-x\RMMF-n FIRMWARE REVISION NUMBER OF

THE RMM

RECORDING EVENT DEFINITIONS

RECORDING

EVENTS ENABLED

1 R-x\EV\E

*RO-CH10*

INDICATES IF EVENTS ARE ENABLED.

EVENTS MUST BE ENABLED TO

GENERATE EVENT PACKETS.


NUMBER OF

RECORDING

EVENTS

3 R-x\EV\N

*RO-CH10*

SPECIFY THE NUMBER OF INDIVIDUAL

RECORDING EVENT TYPES

RECORDER

INTERNAL EVENTS

ENABLED

1 R-x\EV\IEE

*RO-CH10*

INDICATES IF RECORDER INTERNAL

EVENTS ARE ENABLED.


RECORDING EVENT

EVENT ID 32 R-x\EV\ID-n

*RO-CH10*

IDENTIFY THE NAME OF THE

INDIVIDUAL RECORDING EVENT

EVENT

DESCRIPTION

256 R-x\EV\D-n

*RO-CH10*

IDENTIFY THE DESCRIPTION OF THE

EVENT

9-27

7/31/2019 IRIG_106_2009




MAX

PARAMETER FIELD

SIZE

CODE

NAMEDEFINITION

EVENT TYPE 1 R-x\EV\T-n

*RO-CH10*

INDICATE THE RECORDING EVENT TYPE

EXTERNAL – ‘E’

MEASUREMENT DISCRETE – ‘D’

MEASUREMENT LIMIT – ‘L’

RECORDER – ‘R’

OTHER – ‘O’

EVENT PRIORITY 1 R-x\EV\P-n

*RO-CH10*

INDICATE THE RECORDING EVENT

PRIORITY

PRIORITY 1 – ‘1’





EVENT CAPTURE

MODE

1 R-x\EV\CM-n

*RO-CH10*

INDICATE THE RECORDING EVENT

CAPTURE MODE

MODE 1 – ‘1’

MODE 2 – ‘2’

MODE 3 – ‘3’

MODE 4 – ‘4’

MODE 5 – ‘5’

MODE 6 – ‘6’

EVENT INITIAL

CAPTURE

1 R-x\EV\IC-n

*RO-CH10*

INDICATES IF INITIAL CAPTURE OF

EVENT IS ENABLED.


RECORDING EVENTLIMIT COUNT

8 R-x\EV\LC-n*RO-CH10*

SPECIFY THE LIMIT COUNT FOR THEINDIVIDUAL RECORDING EVENT

EVENT TRIGGER

MEASUREMENT

SOURCE

32 R-x\EV\MS-n

*RO-CH10*

IDENTIFY THE DATA LINK NAME

CONSISTENT WITH THE MUX/MOD

GROUP WHICH CONTAINS THE EVENT

TRIGGER MEASUREMENT IF EVENT TYPE

IS ‘D’ OR ‘L’

EVENT TRIGGER

MEASUREMENT

NAME

32 R-x\EV\MN-n

*RO-CH10*

IDENTIFY THE EVENT TRIGGER

MEASURAND NAME IF THE EVENT TYPE

IS ‘D’ OR ‘L’

9-28

7/31/2019 IRIG_106_2009




MAX

PARAMETER FIELD

SIZE

CODE

NAMEDEFINITION

RECORDING INDEX

RECORDING INDEX

ENABLED

1 R-x\IDX\E

*RO-CH10*

INDICATES IF INDEX IS ENABLED.

INDEX MUST BE ENABLED TO

GENERATE INDEX PACKETS.


RECORDING INDEX

TYPE

1 R-x\IDX\IT

*RO-CH10*

TIME – ‘T’

COUNT – ‘C’

TIME INDEX TYPE ATTRIBUTE

INDEX TIME VALUE 8 R-\IDX\ITV

*RO-CH10*

IDENTIFY THE NUMBER OF

MICROSECONDS FOR EACH INDEX

ENTRY GENERATION

COUNT INDEX TYPE ATTRIBUTE

INDEX COUNT

VALUE

4 R-\IDX\ICV

*RO-CH10*

IDENTIFY THE NUMBER OF PACKETS

FOR EACH INDEX ENTRY GENERATION

MIL-STD-1553 RECORDER CONTROL

MESSAGE MONITOR

RECORD CONTROL

ENABLED

1 R-x\MRC\E

INDICATES IF MESSAGE MONITOR

RECORD CONTROL IS ENABLED.


CHANNEL ID

NUMBER 5 R-x\MRC\ID

SPECIFY THE MIL-STD-1553 CHANNEL IDTHAT CONTAINS THE RECORD CONTROL

MESSAGE

MESSAGE RECORD

CONTROL TYPE 2 R-x\MRC\RCT

SPECIFY THE MIL-STD-1553 MESSAGE

MONITOR RECORD CONTROL TYPE

“0” = STOP-START

“1” = PAUSE-RESUME

STOP-PAUSE

COMMAND WORD 4 R-x\MRC\SPM

SPECIFY THE COMMAND WORD OF THEMIL-STD-1553 MESSAGE TO BE USED FOR

STOP-PAUSE IN HEXADECIMAL FORMAT

9-29

7/31/2019 IRIG_106_2009




MAX

PARAMETER FIELD

SIZE

CODE

NAMEDEFINITION

START-RESUME

COMMAND WORD 4 R-x\MRC\SRM

SPECIFY THE COMMAND WORD OF THE

MIL-STD-1553 MESSAGE TO BE USED FOR

START-RESUME IN HEXADECIMAL

FORMAT

DATA

NOTE: Define information contained on each track of the tape or each channel of the storage media.

5 TRACK NUMBER/

CHANNEL ID

R-x\TK1-n

*R-CH10*

SPECIFY THE TRACK NUMBER OR

THE CHANNEL ID THAT CONTAINS

THE DATA TO BE SPECIFIED.

RECORDING

TECHNIQUE

6 R-x\TK2-n SPECIFY THE RECORDING TECHNIQUE

USED FOR THIS TRACK:

FM/FM - ‘FM/FM’

HDDR - ‘HDDR’

PRE-DETECTION - ‘PRE-D’

DIRECT - ‘DIRECT’

FM-WIDE BAND GRP I - ‘FMWBI’

FM-WIDE BAND GRP II - ‘FMWBII’

FM-INTERMEDIATE BAND - FM-IM’

FM-NARROW BAND - ‘FM-NB’

DOUBLE DENSITY - ‘DOUDEN’ROTARY (SINGLE TRACK) - ‘RO-K’

ROTARY (MULTIPLEXED) - ‘RO-MUX’

SOLID STATE - ‘SSR’

OTHER - ‘OTHER’

DATA SOURCE ID 32 R-x\DSI-n

*R-CH10*

SPECIFY THE DATA SOURCE

IDENTIFICATION. FOR A SITE RECORDED

MULTIPLEXED TRACK, PROVIDE A DATA

SOURCE IDENTIFICATION.

DATA DIRECTION 3 R-x\TK3-n FORWARD - ‘FWD’

REVERSE - ‘REV’

RECORDER

PHYSICAL

CHANNEL NUMBER

2 R-x\TK4-n

*R-CH10*

SPECIFY THE RECORDER PHYSICAL

CHANNEL FOR THE CHANNEL ID (TK1).

9-30

7/31/2019 IRIG_106_2009




MAX

PARAMETER FIELD

SIZE

CODE

NAMEDEFINITION

CHANNEL ENABLE 1 R-x\CHE-n

*R-CH10*

INDICATES IF SOURCE IS ENABLED.

SOURCE MUST BE ENABLED TO

GENERATE DATA PACKETS.


CHANNEL DATA

TYPE

6 R-x\CDT-n

*R-CH10*

SPECIFY THE TYPE OF SOURCE IF ‘STO’

WAS SPECIFIED IN G GROUP DATA

SOURCE TYPE:

PCM INPUT – ‘PCMIN’

ANALOG INPUT – ‘ANAIN’

DISCRETE INPUT – ‘DISIN’

IRIG TIME INPUT – ‘TIMEIN’

VIDEO INPUT – ‘VIDIN’,UART INPUT – ‘UARTIN’

1553 INPUT – ‘1553IN’,

ARINC 429 INPUT – ‘429IN’MESSAGE DATA INPUT – ‘MSGIN’

IMAGE DATA INPUT – ‘IMGIN’

IEEE-1394 INPUT – ‘1394IN’

PARALLEL INPUT – ‘PARIN’

ETHERNET INPUT – ‘ETHIN’

CHANNEL DATA

LINK

NAME

32 R-x\CDLN-n

*R-CH10*

IDENTIFY THE DATA LINK NAME

CONSISTENT WITH THE MUX/MOD

GROUP FOR THE CHANNEL.

DATA TYPE ATTRIBUTES

PCM DATA TYPE ATTRIBUTES

PCM DATA TYPE

FORMAT

1 R-x\PDTF-n*RO-CH10*

PCM DATA TYPE FORMAT:

FORMAT 0 (RESERVED) – ‘0’

FORMAT 1 (IRIG 106 CH 4/8) – ‘1’

DATA PACKING

OPTION

3 R-x\PDP-n

*RO-CH10*

HOW DATA IS PLACED IN THE PACKETS:

UNPACKED – ‘UN’

PACKED WITH FRAME SYNC – ‘PFS’THROUGHPUT MODE – ‘TM’

INPUT CLOCK EDGE 3 R-x\ICE-n

*RO-CH10*

SPECIFIES THE INPUT CLOCK EDGE

RELATIVE TO THE DATA IN DEGREES:

0 DEGREES – ‘0’

180 DEGREES – ‘180’

9-31

7/31/2019 IRIG_106_2009




MAX

PARAMETER FIELD

SIZE

CODE

NAMEDEFINITION

INPUT SIGNAL TYPE 5 R-x\IST-n*RO-CH10*

TYPE OF INPUT SIGNAL:SINGLE ENDED – ‘SE’

DIFFERENTIAL – ‘DIFF’RS-422 STANDARD DIFFERENTIAL –

‘RS422’

SINGLE ENDED WITH TTL – ‘TTL’

INPUT THRESHOLD 5 R-x\ITH-n

*RO-CH10*

SPECIFIES THE INPUT THRESHOLD

LEVEL FOR SELECTABLE ELECTRICAL

INTERFACE. THE VALUE IS THE

THRESHOLD LEVEL IN VOLTS.

INPUTTERMINATION

6 R-x\ITM-n*RO-CH10*

SPECIFIES THE INPUT TERMINATION IFSELECTABLE: ‘LOW-Z’ or ‘HIGH-Z’.

PCM VIDEO TYPE

FORMAT

5 R-x\PTF-n

*RO-CH10*

COMPRESSION TECHNIQUE FOR VIDEO

RECORDED AS STANDARD CHAPTER 4

PCM. THE COMPRESSED DATA IS

ENCAPSULATED IN ISO STANDARD

TRANSPORT STREAM (TS) FRAMES. IF

TYPE FORMAT IS ‘OTHER’, THEN A

VENDOR SPEC IS REQUIRED TO

IDENTIFY THE DATA COMPRESSION

TECHNIQUE. SPECIFY ‘NONE’ IF DATA IS

NOT VIDEO DATA.‘NONE’

‘MPEG1’

‘MPEG2’

‘H261’

‘WAVE’

‘OTHER’

PCM RECORDER –

REPRODUCER

MINOR FRAME

FILTERING

ENABLED

1 R-x\MFF\E-n

*RO-CH10* INDICATES IF RECORDER – REPRODUCER

MINOR FRAME FILTERING IS ENABLED

FOR THE PCM CHANNEL:


(NOT APPLICABLE FOR THROUGHPUTMODE PCM CHANNELS)

PCM POST PROCESS

OVERWRITE AND

FILTERING

ENABLED

1 R-x\POF\E-n

*RO-CH10*

INDICATES IF POST PROCESS

OVERWRITE AND FILTERING IS

ENABLED FOR THE PCM CHANNEL:


9-32

7/31/2019 IRIG_106_2009




MAX

PARAMETER FIELD

SIZE

CODE

NAMEDEFINITION

PCM POST PROCESS

OVERWRITE AND

FILTERING TYPE

2 R-x\POF\T-n

*RO-CH10*

INDICATES THE TYPE OF POST PROCESS

OVERWRITE AND FILTERING FOR THE

PCM CHANNEL:

‘MF’ = MINOR FRAME

‘SM’ = SELECTED MEASUREMENT

‘B’ = BOTH

MIL-STD-1553 BUS DATA TYPE ATTRIBUTES

MIL-STD-1553 BUS

DATA TYPE

FORMAT

1 R-x\BTF-n

*RO-CH10*

MIL-STD-1553 BUS DATA TYPE FORMAT:


FORMAT 1 (MIL-STD-1553B DATA) – ‘1’

FORMAT 2 (16PP194 BUS) – ‘2’

MIL-STD-1553

RECORDER –

REPRODUCER

FILTERING

ENABLED

1

R-x\MRF\E-n

*RO-CH10*

INDICATES IF RECORDER – REPRODUCER

FILTERING IS ENABLED FOR THE MIL-

STD-1553 CHANNEL:


MIL-STD-1553 POST

PROCESS

OVERWRITE AND

FILTERING

ENABLED

1

R-x\MOF\T-n

*RO-CH10*

INDICATES IF POST PROCESS

OVERWRITE AND FILTERING IS

ENABLED FOR THE MIL-STD-1553

CHANNEL:


MIL-STD-1553

MESSAGE

FILTERING

DEFINITION TYPE

2 R-x\MFD\

FDT-n

SPECIFY THE MESSAGE FILTERING

DEFINITION TYPE.

“IN” = INCLUSIVE FILTERING

“EX” = EXCLUSIVE FILTERING

NUMBER OF

MESSAGE

FILTERING

DEFINITIONS

2 R-x\MFD\N-n SPECIFY THE NUMBER OF MESSAGE

FILTERING DEFINITIONS.

MESSAGE TYPE 4 R-x\MFD\

MT-n-m

SPECIFY THE MESSAGE TYPERT/RT – ‘RTRT’

RT/BC – ‘RTBC’

BC/RT – ‘BCRT’

MODE CODE – ‘MC’

9-33

7/31/2019 IRIG_106_2009




MAX

PARAMETER FIELD

SIZE

CODE

NAMEDEFINITION

REMOTE TERMINAL

ADDRESS 5

R-x\MFD\

TRA-n-m

SPECIFY THE FIVE BIT REMOTE

TERMINAL ADDRESS FOR THIS

MESSAGE. USE ‘X’ TO INDICATE A

“DON’T CARE” VALUE.

TRANSMIT/

RECEIVE MODE 1

R-x\MFD\

TRM-n-m

INDICATE IF THIS COMMAND WORD IS A

TRANSMIT OR RECEIVE COMMAND. FOR

RT/RT, SPECIFY TRANSMIT.

TRANSMIT – ‘1’

RECEIVE – ‘0’

SUBTERMINAL

ADDRESS 5

R-x\MFD\

STA-n-m

SPECIFY THE FIVE BIT SUBTERMINAL

ADDRESS FOR THIS MESSAGE. USE ‘X’

TO INDICATE A “DON’T CARE” VALUE.

DATA WORD

COUNT/MODE CODE 5

R-x\MFD\

DWC-n-m

ENTER THE NUMBER OF DATA WORDS

AS A BINARY STRING, USING ‘X’ TO

INDICATE A “DON’T CARE” VALUE. IF

THE SUBTERMINAL ADDRESS INDICATES

A MODE CODE, ENTER THE MODE CODE

VALUE AS A BINARY STRING.

RT/RT REMOTE

TERMINALADDRESS

5 R-x\MFD\ RTRA-n-m

SPECIFY THE FIVE BIT REMOTE

TERMINAL ADDRESS FOR THIS RT/RTMESSAGE.

RT/RT

SUBTERMINAL

ADDRESS

5 R-x\MFD\

RSTA-n-m

SPECIFY THE FIVE BIT SUBTERMINAL

ADDRESS FOR THIS RT/RT MESSAGE. USE

‘X’ TO INDICATE A “DON’T CARE”

VALUE.

RT/RT DATA WORD

COUNT 5

R-x\MFD\

RDWC-n-m

ENTER THE NUMBER OF DATA WORDS

AS A BINARY STRING, USING ‘X’ TO

INDICATE A “DON’T CARE” VALUE.

EXCLUDE STATUS AND TIME WORDS

(AN RT/RT MESSAGE CANNOT CONTAINA MODE CODE).

ANALOG DATA TYPE ATTRIBUTES

ANALOG DATA

TYPE FORMAT

1 R-x\ATF-n

*RO-CH10*

ANALOG DATA TYPE FORMAT:


FORMAT 1 (ANALOG DATA) – ‘1’

9-34

7/31/2019 IRIG_106_2009




MAX

PARAMETER FIELD

SIZE

CODE

NAMEDEFINITION

NUMBER OF

ANALOG

CHANNELS/PKT

3 R-x\ACH\N-n

*RO-CH10*

SPECIFY THE NUMBER OF ANALOG

CHANNELS PER PACKET.

DATA PACKING

OPTION

3 R-x\ADP-n

*RO-CH10*

HOW DATA IS PLACED IN THE PACKETS:

PACKED – ‘YES’

UNPACKED – ‘NO’

SAMPLE RATE 7 R-x\ASR-n

*RO-CH10*

SAMPLE RATE OF THE FASTEST

CHANNEL (S) IN SAMPLES PER SECOND

MEASUREMENT

NAME

32 R-x\AMN-n-m

*RO-CH10*

IDENTIFY THE MEASUREMENT NAME

CONSISTENT WITH THE MUX/MODGROUP FOR AN ANALOG CHANNEL.

DATA LENGTH 2 R-x\ADL-n-m

*RO-CH10*NUMBER OF BITS PER DATA WORD

BIT MASK 64 R-x\AMSK-n-m

*RO-CH10*

BINARY STRING OF 1s AND 0s TO

IDENTIFY THE BITS IN A WORD

LOCATION THAT ARE ASSIGNED TO THIS

MEASUREMENT. IF THE FULL

WORD IS USED FOR THIS

MEASUREMENT, ENTER - ‘FW’.

LEFT-MOST BIT CORRESPONDS TO FIRSTBIT TRANSMITTED

MEASUREMENT

TRANSFER ORDER

1 R-x\AMTO-n-m

*RO-CH10*

MOST SIGNIFICANT BIT FIRST - ‘M’

LEAST SIGNIFICANT BIT FIRST - ‘L’DEFAULT - ‘D’

SAMPLE FACTOR 2 R-x\ASF-n-m

*RO-CH10*

1/(2^N) TIMES THE FASTEST SAMPLE

RATE (DEFINED ABOVE) GIVES THE

SAMPLE RATE FOR THIS CHANNEL.

SPECIFY THE VALUE ‘N’ IN THIS FIELD.

SAMPLE FILTER 3dbBANDWIDTH

9 R-x\ASBW-n-m*RO-CH10*

SAMPLE FILTER IN UNITS OF HZ(000,000,000)

AC/DC COUPLING 1 R-x\ACP-n-m

*RO-CH10*

ANALOG SIGNAL COUPLING

AC – ‘A’

DC – ‘D’

9-35

7/31/2019 IRIG_106_2009




MAX

PARAMETER FIELD

SIZE

CODE

NAMEDEFINITION

RECORDER INPUT

IMPEDANCE

6 R-x\AII-n-m

*RO-CH10*

ANALOG SIGNAL INPUT IMPEDANCE TO

THE RECORDER. UNITS OF OHMS

(000,000)

INPUT CHANNEL

GAIN

6 R-x\AGI-n-m

*RO-CH10*

SIGNAL GAIN OF ANALOG SIGNAL. MILLI

UNITS (10X = 010000)

INPUT FULL SCALE

RANGE

6 R-x\AFSI-n-m

*RO-CH10*

FULL SCALE RANGE OF INPUT SIGNAL.

UNITS OF MILLI-VOLTS

(20Vpp = 020000)

(Vpp = 2XVp)

INPUT OFFSET

VOLTAGE

6 R-x\AOVI-n-m

*RO-CH10*

OFFSET VOLTAGE OF INPUT SIGNAL.

UNITS OF MILLI-VOLTS (10V=010000)

INPUT TYPE 1 R-x\AIT-n-m

*RO-CH10*

TYPE OF INPUT SIGNAL.

SINGLE ENDED – ‘S’

DIFFERENTIAL – ‘D’

AUDIO 1 R-x\AV-n-m

*RO-CH10*

INDICATE IF INPUT SIGNAL IS AUDIO.

AUDIO PRESENT – ‘Y’

AUDIO NOT PRESENT – ‘N’

AUDIO FORMAT 4 R-x\AVF-n-m*RO-CH10*

FORMAT OF AUDIO IF PRESENT.RAW – ‘RAW’

WAV – ‘WAV’

LPCM – ‘LPCM’

AC3 – ‘AC3’

PreD – ‘PRED’

PstD – ‘PSTD’

OTHER – ‘O’

DISCRETE DATA TYPE ATTRIBUTES

DISCRETE DATA

TYPE FORMAT

1 R-x\DTF-n

*RO-CH10*

DISCRETE DATA TYPE FORMAT:

FORMAT 0 (RESERVED) – ‘0’FORMAT 1 (DISCRETE DATA) – ‘1’

DISCRETE MODE 4 R-x\DMOD-n

*RO-CH10*

INDICATE THE MODE WHEREBY

DISCRETE EVENTS ARE PLACED IN THE

PACKETS:

‘EV’ – EVENT MODE‘SAMP’ – SAMPLE MODE

9-36

7/31/2019 IRIG_106_2009




MAX

PARAMETER FIELD

SIZE

CODE

NAMEDEFINITION

SAMPLE RATE 7 R-x\DSR-n*RO-CH10*

SAMPLE RATE IN SAMPLES PER SECOND

NUMBER OF

DISCRETE

MEASUREMENTS

3 R-x\NDM\N-n

*RO-CH10*

SPECIFY THE NUMBER OF DISCRETE

MEASUREMENTS

MEASUREMENT

NAME

32 R-x\DMN-n-m

*RO-CH10*

IDENTIFY THE MEASUREMENT NAME

FOR ONE OR MORE DISCRETE BITS

BIT MASK 64 R-x\DMSK-n-m

*RO-CH10* BINARY STRING OF 1s AND 0s TO


LOCATION THAT ARE ASSIGNED TO THISMEASUREMENT. IF THE FULL WORD IS

USED FOR THIS MEASUREMENT,ENTER ‘FW’. LEFT-MOST BIT

CORRESPONDS TO FIRST BIT

TRANSMITTED

MEASUREMENT

TRANSFER ORDER

1 R-x\DMTO-n-m

*RO-CH10* MOST SIGNIFICANT BIT FIRST – ‘M’

LEAST SIGNIFICANT BIT FIRST - ‘L’

DEFAULT - ‘D’

ARINC 429 BUS DATA TYPE ATTRIBUTES

ARINC 429 BUSDATA TYPE

FORMAT

1 R-x\ABTF-n*RO-CH10*

ARINC 429 BUS DATA TYPE FORMAT:FORMAT 0 (ARINC 429 DATA) – ‘0’


NUMBER OF ARINC

429 SUB-CHANNELS 5 R-x\NAS\N-n

*RO-CH10*

NUMBER OF ARINC 429 BUS SUB-

CHANNELS

ARINC 429 SUB-

CHANNEL NUMBER 5 R-x\ASN-n-m

*RO-CH10*

ARINC 429 BUS SUB-CHANNEL ID

ARINC 429 SUB-

CHANNEL NAME 32 R-x\ANM-n-m

*RO-CH10*

ARINC 429 BUS SUB-CHANNEL NAME

VIDEO DATA TYPE ATTRIBUTES

VIDEO DATA TYPE

FORMAT

1 R-x\VTF-n

*RO-CH10*

VIDEO DATA TYPE FORMAT:

FORMAT 0 (MPEG-2/H.264) – ‘0’

FORMAT 1 (MPEG-2 ISO 13818) – ‘1’

FORMAT 2 (MPEG-4 ISO 14496) – ‘2’

9-37

7/31/2019 IRIG_106_2009




MAX

PARAMETER FIELD

SIZE

CODE

NAMEDEFINITION

MPEG-2 CHANNEL

XON2 FORMAT

1 R-x\VXF-n

*RO-CH10*

TYPE OF VIDEO CARRIED FOR XON2

FORMATS (MPEG-2 VIDEO CHANNELS)

2ON2 (MPEG-2) – ‘0’

264ON2 (H.264) – ‘1’

VIDEO SIGNAL TYPE 1 R-x\VST-n

*RO-CH10*

THE VIDEO SIGNAL INPUT TYPE

AUTO DETECT – ‘0’

COMPOSITE – ‘1’

YUV – ‘2’

S-VIDEO – ‘3’

DVI – ‘4’

RGB – ‘5’

SDI – ‘6’

VGA – ‘7’

VIDEO SIGNALFORMAT TYPE

2 R-x\VSF-n*RO-CH10*

THE VIDEO SIGNAL INPUT TYPEAUTO DETECT – ‘0’

NTSC – ‘1’

PAL – ‘2’

ATSC – ‘3’

DVB – ‘4’

ISDB – ‘5’

SECAM – ‘6’

VIDEO CONSTANT

BIT RATE

10 R-x\CBR-n

*RO-CH10*

CONTAINS AGGREGATE STREAM BIT

RATE IN BITS PER SECOND. SCIENTIFIC

NOTATION MAY BE USED.

VIDEO VARIABLE

PEAK BIT RATE

10 R-x\VBR-n

*RO-CH10*

CONTAINS PEAK STREAM BIT RATE IN

BITS PER SECOND. SCIENTIFIC


VIDEO ENCODING

DELAY

8 R-x\VED-n

*RO-CH10*

DELAY INTRODUCED BY VIDEO

ENCODING HARDWARE IN

MILLISECONDS

OVERLAY ENABLED 1 R-x\VCO\OE-n INDICATES IF OVERLAY IS ENABLED.


OVERLAY X

POSITION 5 R-x\VCO\X-n

SPECIFY THE X PIXEL POSITION OF THE

OVERLAY IN THE VIDEO CHANNEL.

ZERO INDICATES THE LEFTMOST

POSITION OF THE VIDEO IMAGE.

9-38

7/31/2019 IRIG_106_2009




MAX

PARAMETER FIELD

SIZE

CODE

NAMEDEFINITION

OVERLAY Y

POSITION 5 R-x\VCO\Y-n

SPECIFY THE Y LINE POSITION OF THE

OVERLAY IN THE VIDEO CHANNEL.

ZERO INDICATES THE UPPERMOST

POSITION OF THE VIDEO IMAGE.

OVERLAY EVENT

TOGGLE ENABLED 1 R-x\VCO\OET-n

INDICATES IF OVERLAY EVENT TOGGLE

IS ENABLED.


OVERLAY FORMAT 1 R-x\VCO\OLF-n

INDICATES FORMAT OF THE TIME

OVERLAY.

‘DT’ DAY AND TIME (DDD:HH:MM:SS)

‘TO’ TIME ONLY (HH:MM:SS)‘TM’ TIME AND MILLISECONDS

(HH:MM:SS:SSS)

‘DTM’ DAY, TIME AND MILLISECONDS

(DDD:HH:MM:SS:SSS)

OVERLAY

BACKGROUND 3 R-x\VCO\OBG-n

INDICATES BACKGROUND OF THE TIME

OVERLAY.

‘BOT’ - BLACK ON TRANSPARENT

‘WOT’ - WHITE ON TRANSPARENT

‘BOW’ - BLACK ON WHITE

‘WOB’ - WHITE ON BLACK

ANALOG AUDIO

CHANNEL INPUT

LEFT

5 R-x\ASI\ASL-n

INDICATES THE ANALOG CHANNEL

SOURCE OF THE LEFT AUDIO CHANNEL

ID FOR THE VIDEO CHANNEL.

ANALOG AUDIOCHANNEL INPUT

RIGHT

5 R-x\ASI\ASR-n

INDICATES THE ANALOG CHANNELSOURCE OF THE RIGHT AUDIO CHANNEL

ID FOR THE VIDEO CHANNEL.

VIDEO DATA

ALIGNMENT1

R-x\VDA-n

*RO-CH10*

SPECIFIES THE DATA ALIGNMENT OF

THE VIDEO DATA WITHIN THE PACKET.

LITTLE ENDIAN - ‘L’

BIG ENDIAN - ‘B’

TIME DATA TYPE ATTRIBUTES

TIME DATA TYPE

FORMAT

1 R-x\TTF-n

*R-CH10*

TIME DATA TYPE FORMAT:


FORMAT 1 (TIME DATA) – ‘1’

9-39

7/31/2019 IRIG_106_2009




MAXFIELD PARAMETERSIZE

CODE

NAMEDEFINITION

TIME FORMAT 1 R-x\TFMT-n*R-CH10*

INDICATE THE FORMAT FOR THE TIME:IRIG-A – ‘A’

IRIG-B – ‘B’

IRIG-G – ‘G’

INTERNAL – ‘I’

NATIVE GPS TIME – ‘N’

UTC TIME FROM GPS – ‘U’

NONE – ‘X’

TIME SOURCE 1 R-x\TSRC-n

*R-CH10*

INDICATE THE TIME SOURCE:

INTERNAL – ‘I’EXTERNAL – ‘E’

INTERNAL FROM RMM – ‘R’

NONE – ‘X’

IMAGE DATA TYPE ATTRIBUTES

IMAGE DATA TYPE

FORMAT

1 R-x\ITF-n

*RO-CH10*

IMAGE DATA TYPE FORMAT:

FORMAT 0 (IMAGE) – ‘0’

FORMAT 1 (STILL IMAGERY) – ‘1’

STILL IMAGE TYPE 2 R-x\SIT-n

*RO-CH10*

TYPE OF STILL IMAGERY FORMAT

NITF – ‘0’

JPEG – ‘1’

JPEG2 – ‘2’

PNG – ‘3’

UART DATA TYPE ATTRIBUTES

UART DATA TYPE

FORMAT

1 R-x\UTF-n

*RO-CH10*

UART DATA TYPE FORMAT:

FORMAT 0 – ‘0’

FORMAT 1 – ’1’

NUMBER OF UART

SUB-CHANNELS

5 R-x\NUS\N-n

*RO-CH10*

SPECIFY THE NUMBER OF UART SUB-

CHANNELS INCLUDED WITHIN THISCHANNEL.

UART SUB-

CHANNEL NUMBER

5 R-x\USCN-n-m

*RO-CH10*

SPECIFY THE UART SUB-CHANNEL

NUMBER.

UART SUB-

CHANNEL NAME

32 R-x\UCNM-n-m

*RO-CH10*

SPECIFY THE UART SUB-CHANNEL

NAME.

9-40

7/31/2019 IRIG_106_2009




MAX

PARAMETER FIELD

SIZE

CODE

NAMEDEFINITION

UART SUB-CHANNEL BAUD

RATE

12 R-x\UCR-n-m*R0-CH10*

BAUD RATE IN BITS PER SECOND(00000000.000)

UART SUB-

CHANNEL BITS

PER WORD

1 R-x\UCB-n-m

*R0-CH10*

BITS PER WORD (7, 8 or 9)

UART SUB-CHANNEL PARITY

1 R-x\UCP-n-m*R0-CH10*

PARITY.‘O’-ODD ‘E’-EVEN ‘N’-NONE

UART SUB-CHANNEL STOP

BIT

1 R-x\UCS-n-m*R0-CH10* STOP BIT SIZE.‘0’ – 1.0

‘1’ – 1.5

‘2’ – 2.0

UART SUB-

CHANNELINTERFACE

1 R-x\UCIN-n-m UART INTERFACE

‘0’ – OTHER ‘3’ – RS-485‘1’ – RS-232 ‘4’ - TTL

‘2’ – RS-422

UART SUB-

CHANNEL BLOCK

SIZE

6 R-x\UCBS-n-m BLOCK (FRAME) SIZE IN WORDS

XXX,XXX WORDS

UART SUB-CHANNEL SYNC

WORD LENGTH

1 R-x\UCSL-n-m SYNC WORD LENGTH IN WORDS(0 – 9 WORDS MAXIMUM)

UART SUB-

CHANNEL BLOCKSYNC VALUE

81 R-x\UCSV-n-m BLOCK SYNC WORD VALUE IN

BINARY. SPECIFY ALL BITS.

UART SUB-

CHANNEL BLOCKRATE

12 R-x\UCBR-n-m BLOCK RATE IN HZ

(00000000.000)

MESSAGE DATA TYPE ATTRIBUTES

MESSAGE DATA

TYPE FORMAT

1 R-x\MTF-n

*RO-CH10*

MESSAGE DATA TYPE FORMAT:

FORMAT 0 (MESSAGE DATA) – ‘0’

9-41

7/31/2019 IRIG_106_2009




MAX

PARAMETER FIELD

SIZE

CODE

NAMEDEFINITION

NUMBER OFMESSAGE SUB-

CHANNELS

5 R-x\NMS\N-n*RO-CH10*

SPECIFY THE NUMBER OF MESSAGE SUB-CHANNELS INCLUDED WITHIN THIS

CHANNEL

MESSAGE SUB-

CHANNEL NUMBER

5 R-x\MSCN-n-m

*RO-CH10*

SPECIFY THE MESSAGE SUB-CHANNEL

NUMBER.

MESSAGE SUB-CHANNEL NAME

32 R-x\MCNM-n-m*RO-CH10*

SPECIFY THE MESSAGE SUB-CHANNELNAME.

IEEE-1394 DATA TYPE ATTRIBUTES

IEEE-1394 DATATYPE FORMAT

1 R-x\IETF-n*RO-CH10*

IEEE-1394 DATA TYPE FORMAT:FORMAT 0 (IEEE-1394 TRANS) – ‘0’

FORMAT 1 (IEEE-1394 PHY) – ‘1’

PARALLEL DATA TYPE ATTRIBUTES

PARALLEL DATA

TYPE FORMAT

1 R-x\PLTF-n

*RO-CH10*

PARALLEL DATA TYPE FORMAT:

FORMAT 0 (PARALLEL) – ‘0’

ETHERNET DATA TYPE ATTRIBUTES

ETHERNET DATA

TYPE FORMAT

1 R-x\ENTF-n

*RO-CH10*

ETHERNET DATA TYPE FORMAT:

FORMAT 0 (ETHERNET DATA) – ‘0’

NUMBER OF

ETHERNET

NETWORKS

5 R-x\NNET\N-n

*RO-CH10*

SPECIFY THE NUMBER OF ETHERNET

NETWORKS INCLUDED WITHIN THIS

CHANNEL

ETHERNET

NETWORK NUMBER

5 R-x\ENBR-n-m

*RO-CH10*

SPECIFY THE ETHERNET NETWORK

NUMBER

ETHERNET

NETWORK NAME

32 R-x\ENAM-n-m

*RO-CH10*

SPECIFY THE ETHERNET NETWORK

NAME

REFERENCE TRACK

NUMBER OF

REFERENCE

TRACKS

1 R-x\RT\N SPECIFY THE NUMBER OF REFERENCE

TRACKS

TRACK

NUMBER

2 R-x\RT1-n STATE THE TRACK LOCATION OF THE

REFERENCE SIGNAL

9-42

7/31/2019 IRIG_106_2009




MAX

PARAMETER FIELD

SIZE

CODE

NAMEDEFINITION

REFERENCEFREQUENCY

6 R-x\RT2-n FREQUENCY OF REFERENCE SIGNAL, INkHz

NOTE: THERE WILL BE ONE TAPE/STORAGE SOURCE ATTRIBUTES GROUP FOR EACH TAPE

OR STORAGE SOURCE.

COMMENTS

COMMENTS 3200 R-x\COM

*RO-CH10*

PROVIDE THE ADDITIONAL


OTHER INFORMATION DESIRED

9.5.5 Multiplex/Modulation (Mux/Mod) Attributes (M). The composite baseband waveform is

received from the receiver or tape reproducer electronics and is passed to the demultiplexer/

demodulator for further processing. Figure 9-5 summarizes the information that is required tocontinue processing the data. The composite baseband waveform may consist of any number of

signals, which are modulated directly onto the RF carrier including a baseband data signal, and

one or more subcarriers.

The baseband data signal may be PCM, pulse amplitude modulation (PAM), or analogdata. The PCM and PAM data streams must be defined in terms of a data link name. This data

link name is unique for each system that contains different data, has a different format, or has a

different data rate. The analog measurand is typically converted into engineering unitsappropriate for the measurand. The measurement name provides the connection to the Data

Conversion Attributes Group (C).

Subcarriers, both standard and nonstandard, may be part of the baseband compositewaveform. These, in turn, may be modulated with PCM, PAM, or analog data. As with the

baseband data signal, these data channels must be defined. Table 9-4 specifies the required

information for the data signal attributes.

9-43

7/31/2019 IRIG_106_2009



CODEMultiplex/Modulation Attributes Group (M) NAME

REFERENCEPAGE

DATA

SOURCE ID(M-x\ID) (9-45)

*COMPOSITE SIGNAL STRUCTURE (9-45)

SIGNAL STRUCTURE TYPE (M-x\BB1)MODULATION SENSE (M-x\BB2)

COMPOSITE LPF BANDWIDTH (M-x\BB3)

*BASEBAND SIGNAL (9-45)

BASEBAND SIGNAL TYPE (M-x\BSG1)

*LOW PASS FILTER

BANDWIDTH (M-x\BSF1)

TYPE (M-x\BSF2)

*BASEBAND DATA LINK TYPE (9-46)

*PCM OR PAM

OR DATA LINK NAME (M-x\BB\DLN)

*ANALOGMEASUREMENT NAME (M-x\BB\MN)

*SUBCARRIERS (9-46)

NUMBER OF SUBCARRIERS (M-x\SCO\N)

*IRIG SUBCARRIERS

NUMBER OF SCOs (M-x\SI\N)

SCO NUMBER (M-x\SI1-n)

SCO #n DATA TYPE (M-x\SI2-n)

MODULATION SENSE (M-x\SI3-n)

*LOW PASS FILTER (9-46)

BANDWIDTH (M-x\SIF1-n)

TYPE (M-x\SIF2-n)

*DATA LINK TYPE (9-47)

*PCM OR PAM

OR DATA LINK NAME (M-x\SI\DLN-n)

*ANALOG

MEASUREMENTNAME

(M-x\SI\MN-n)

OTHER (M-x\SO) (9-47)

REFERENCE CHANNEL (M-x\RC)

*COMMENTS

COMMENTS (M-x\COM) (9-47)

*Heading Only – No Data Entry

Figure 9-5. Multiplex/Modulation Attributes Group (M).

9-44

7/31/2019 IRIG_106_2009



TABLE 9-4. MULTIPLEX/MODULATION GROUP (M)

MAXIMUM

PARAMETER FIELDSIZE

CODE

NAME DEFINITION

DATA SOURCE

ID

32 M-x\ID DATA SOURCE IDENTIFICATION

COMPOSITE SIGNAL STRUCTURE

SIGNAL 7

STRUCTURE

TYPE

M-x\BB1 SPECIFY THE COMPOSITE BASEBAND

SIGNAL STRUCTURE:

‘PCM’ HYBRID:

‘PAM’ ‘ANA/SCO’

‘ANALOG’ ‘PAM/SCO’‘SCO’s’ ‘PCM/SCO’

‘OTHER’

MODULATION

SENSE

3 M-x\BB2 SPECIFY THE MODULATION SENSE:

‘POS’ – INDICATES THAT AN INCREASING

VOLTAGE RESULTS IN AN

INCREASE IN FREQUENCY.

‘NEG’ – INDICATES THAT A DECREASING

VOLTAGE RESULTS IN AN

INCREASE IN FREQUENCY

COMPOSITE LPFBANDWIDTH 6 M-x\BB3 GIVE THE LOW PASS BANDWIDTH OFTHE COMPOSITE WAVEFORM (3 dB

CUTOFF FREQUENCY), IN kHz.

BASEBAND SIGNAL

BASEBAND 3

SIGNAL TYPE

M-x\BSG1 TYPE OF BASEBAND DATA:

‘PCM’ ‘ANA’ (ANALOG)

‘PAM’ ‘OTH’ (OTHER)

‘NON’ (NONE)

LOW PASS FILTER

BANDWIDTH 6 M-x\BSF1 SPECIFY LOW PASS FILTER BANDWIDTH

(3 dB CUTOFF FREQUENCY), IN kHz.

TYPE 2 M-x\BSF2 SPECIFY THE FILTER TYPE:



OTHER - ‘OT’, DEFINE IN THE

COMMENTS RECORD.

9-45

7/31/2019 IRIG_106_2009



Table 9-4 (Continued). Multiplex/Modulation Group (M) Page 2 x 3

MAXIMUM

PARAMETER FIELD

SIZE

CODE

NAMEDEFINITION

BASEBAND DATA LINK TYPE

PCM OR PAM

DATA LINK 32

NAME

M-

x\BB\DLN

SPECIFY THE DATA LINK NAME FOR

PCM OR PAM DATA FORMAT.

ANALOG

MEASUREMENT 32

NAME

M-x\BB\MN GIVE THE MEASURAND NAME.

SUBCARRIERS

NUMBER OF 2

SUBCARRIERS

M-x\SCO\N SPECIFY THE NUMBER OF SUBCARRIERS

ON THIS DATA LINK.

IRIG SUBCARRIERS

NUMBER OF

SCOs

2 M-x\SI\N SPECIFY THE NUMBER OF IRIG

SUBCARRIERS.

SCO NUMBER 5 M-x\SI1-n GIVE THE IRIG CHANNEL NUMBER FORTHE SUBCARRIER.

SCO #n

DATA TYPE

3 M-x\SI2-n SPECIFY THE TYPE OF DATA ON THE

SUBCARRIER:

PCM - ‘PCM’ PAM - ‘PAM’

ANALOG - ‘ANA’ OTHER - ‘OTH’

MODULATION

SENSE

3 M-x\SI3-n SPECIFY THE MODULATION SENSE:

‘POS’ - INDICATES THAT AN

INCREASING VOLTAGE

RESULTS IN AN INCREASE

IN FREQUENCY‘NEG’ - INDICATES THAT A

DECREASING VOLTAGE

RESULTS IN AN INCREASE

IN FREQUENCY.

9-46

7/31/2019 IRIG_106_2009



Table 9-4 (Continued). Multiplex/Modulation Group (M) Page 3 x 3

MAXIMUM

PARAMETER FIELD

SIZE

CODE

NAMEDEFINITION

LOW PASS FILTER

BANDWIDTH 6 M-x\SIF1-n SPECIFY THE LOW PASS FILTER CUTOFF

FREQUENCY (3 dB), IN kHz.

TYPE 2 M-x\SIF2-n SPECIFY THE FILTER TYPE:



OTHER - ‘OT’, DEFINE IN THECOMMENTS RECORD.

DATA LINK TYPE

PCM OR PAM

DATA LINK 32

NAME

M-x\SI\DLN-n SPECIFY THE DATA LINK NAME FOR PCM

AND PAM DATA FORMATS.

ANALOG

MEASUREMENT 32

NAME

M-x\SI\MN-n GIVE THE MEASURAND NAME.

NOTE: REPEAT THE ABOVE FOR EACH IRIG SUBCARRIER ON THIS CARRIER.

OTHER 1 M-x\SO ARE THERE NONSTANDARD

SUBCARRIERS? YES - ‘Y’ NO -‘N’

DEFINE IN THE COMMENTS RECORD.

REFERENCE

CHANNEL

6 M-x\RC FREQUENCY OF REFERENCE CHANNEL IN

kHz, IF APPLICABLE

COMMENTS

COMMENTS 3200 M-x\COM PROVIDE THE ADDITIONALINFORMATION REQUESTED OR ANY


9-47

7/31/2019 IRIG_106_2009



9.5.6 Digital Data Attributes. The digital data attributes are separated into four groupscontaining PCM-related attribute information. The PCM Format Attributes Group (P) is

described in subparagraph 9.5.6.1 below. The PCM Measurement Description Attributes,

contained in (D), are described in subparagraph 9.5.6.2. Subparagraph 9.5.6.3 depicts the MIL-STD-1553 or ARINC 429 Bus Data Attributes (B). Subparagraph 9.5.6.4 describes the Message

Data Attributes (S).

9.5.6.1 PCM Format Attributes (P). The PCM Format Attributes Group contains the

information required to decommutate the PCM data stream. Operations of both class I and II are

included. Limited information is incorporated for class II operations. Figure 9-6 presents the

flow and summary of the information required. In general, only standard methods of synchronization have been included except for cases where considerable application is already in

place. Inclusion should not be taken to mean that the nonstandard approaches are better or

desired. Table 9-5 contains the PCM Format Attributes. The group defines and specifies theframe format and the information necessary to set up the PCM decommutation. Refer to

Chapter 4 for the definition of terms (such as major and minor frames and subframes) and word

numbering conventions.

9-48

7/31/2019 IRIG_106_2009



CODE REFERENCEPCM Format Attributes Group (P) NAME PAGE

DATA LINK NAME (P-d\DLN) (9-52)

*INPUT DATA (9-52)

PCM CODE (P-d\D1)

BIT RATE (P-d\D2)

ENCRYPTED (P-d\D3)

POLARITY (P-d\D4)

AUTO-POLARITY CORRECTION (P-d\D5)

DATA DIRECTION (P-d\D6)

DATA RANDOMIZED (P-d\D7)

RANDOMIZER LENGTH (P-d\D8)

*FORMAT (9-53)

TYPE FORMAT (P-d\TF)

COMMON WORD LENGTH (P-d\F1)

WORD TRANSFER ORDER (P-d\F2)

PARITY (P-d\F3)

PARITY TRANSFER ORDER (P-d\F4)

*MINOR FRAME (9-53)NUMBER OF MINOR FRAMES IN MAJORFRAME

(P-d\MF\N)

NUMBER OF WORDS IN A MINOR FRAME (P-d\MF1)

NUMBER OF BITS IN A MINOR FRAME (P-d\MF2)

SYNC TYPE (P-d\MF3)

*SYNCHRONIZATION PATTERN (9-54)

LENGTH (P-d\MF4)

PATTERN (P-d\MF5)

*SYNCHRONIZATION CRITERIA (9-54)

IN SYNC CRITERIA (P-d\SYNC1)

SYNC PATTERN CRITERIA (P-d\SYNC2)

*OUT OF SYNCHRONIZATION CRITERIA (9-54)

NUMBER OF DISAGREES (P-d\SYNC3)

SYNC PATTERN CRITERIA (P-d\SYNC4)

*MINOR FRAME FORMAT DEFINITION (9-55)

WORD NUMBER (P-d\MFW1-n)

NUMBER OF BITS IN WORD (P-d\MFW2-n)

*SUBFRAME SYNCHRONIZATION (9-55)

NUMBER OF SUBFRAME ID COUNTERS (P-d\ISF\N)

SUBFRAME ID COUNTER NAME (P-d\ISF1-n)

SUBFRAME SYNC TYPE (P-d\ISF2-n)

*ID COUNTER (9-55)

SUBFRAME ID COUNTER LOCATION (P-d\IDC1-n)

ID COUNTER WORD LENGTH (P-d\IDC2-n)

ID COUNTER MSB STARTING BITLOCATION

(P-d\IDC3-n) (9-56)

ID COUNTER LENGTH (P-d\IDC4-n)

ID COUNTER TRANSFER ORDER (P-d\IDC5-n)

Figure 9-6. PCM Format Attributes Group (P). (Page 1 of 3)

9-49

7/31/2019 IRIG_106_2009



ID COUNTER INITIAL VALUE (P-d\IDC6-n)

INITIAL COUNT SUBFRAME NUMBER (P-d\IDC7-n)

ID COUNTER END VALUE (P-d\IDC8-n)

END COUNT SUBFRAME NUMBER (P-d\IDC9-n)

COUNT DIRECTION (P-d\IDC10-n)

* SUBFRAME DEFINITION (9-56)

NUMBER OF SUBFRAMES (P-d\SF\N-n)

SUBFRAME NAME (P-d\SF1-n-m)

SUPERCOM (P-d\SF2-n-m)

LOCATION DEFINITION (P-d\SF3-n-m)

SUBFRAME LOCATION (P-d\SF4-n-m-w)

INTERVAL (P-d\SF5-n-m)

SUBFRAME DEPTH (P-d\SF6-n-m)

* FILTERING

MINOR FRAME FILTERING DEFINITION TYPE (P-d\MFF\FDT)

NUMBER OF MINOR FRAME FILTERINGDEFINITIONS

(P-d\MFF\N)

FILTERED MINOR FRAME NUMBER(P-d\MFF\MFN-n)

*ASYNCHRONOUS EMBEDDED FORMAT (9-58)

NUMBER OF ASYNCHRONOUS EMBEDDED

FORMATS(P-d\AEF\N)

DATA LINK NAME (P-d\AEF\DLN-n) (9-58)

SUPERCOM (P-d\AEF1-n) (9-58)

LOCATION DEFINITION (P-d\AEF2-n)

LOCATION (P-d\AEF3-n-w)

INTERVAL (P-d\AEF4-n) (9-59)

WORD LENGTH (P-d\AEF5-n-w)

MASK (P-d\AEF6-n-w)

*FORMAT CHANGE (9-59)

*FRAME FORMAT IDENTIFIER

LOCATION (P-d\FFI1)

MASK (P-d\FFI2)

*MEASUREMENT LIST CHANGE (9-60)

OR NUMBER OF MEASUREMENT LISTS (P-d\MLC\N)

FFI PATTERN (P-d\MLC1-n)

MEASUREMENT LIST NAME (P-d\MLC2-n)

*FORMAT STRUCTURE CHANGE (9-60)

NUMBER OF FORMATS (P-d\FSC\N)

FFI PATTERN (P-d\FSC1-n)

DATA LINK ID (P-d\FSC2-n)

*ALTERNATE TAG AND DATA (9-60)

NUMBER OF TAGS (P-d\ALT\N)

NUMBER OF BITS IN TAG (P-d\ALT1)

NUMBER OF BITS IN DATA WORD (P-d\ALT2)

FIRST TAG LOCATION (P-d\ALT3)

SEQUENCE (P-d\ALT4)


9-50

7/31/2019 IRIG_106_2009



*ASYNCHRONOUS DATA MERGE FORMAT (9-61)

NUMBER OF ASYNCHRONOUS DATA MERGEFORMATS (P-d\ADM\N)

DATA MERGE NAME (P-d\ADM\DMN-n) (9-61)

SUPERCOM (P-d\ADM1-n)

LOCATION DEFINITION (P-d\ADM2-n)

LOCATION (P-d\ADM3-n-w)

INTERVAL (P-d\ADM4-n)

DATA LENGTH (P-d\ADM5-n)

MSB LOCATION (P-d\ADM6-n)

PARITY (P-d\ADM7-n)

*COMMENTS

COMMENTS (P-d\COM) (9-62)



9-51

7/31/2019 IRIG_106_2009


7/31/2019 IRIG_106_2009



Table 9-5 (Continued). PCM Format Attributes Group (P) Page 2 x 11

MAXIMUM

FIELD SIZEPARAMETER CODE NAME DEFINITION

FORMAT

TYPE FORMAT 4 P-d\TF

*RO-CH10*

TYPE OF PCM FORMAT:

CLASS I - ‘ONE’ CLASS II – ‘TWO’

1553 BUS - ‘1553’ BUS – ‘BUS’ALTERNATE TAG AND DATA-‘ALTD’

OTHER - ‘OTHR’, DESCRIBE IN

COMMENTS.

COMMON

WORD LENGTH2

P-d\F1

*RO-CH10*

NUMBER OF BITS IN COMMON WORD

LENGTH

WORD

TRANSFER

ORDER

1 P-d\F2

*RO-CH10*

DEFINE THE DEFAULT FOR THE

FIRST BIT TRANSFERRED IN

NORMAL TIME SEQUENCE:

MOST SIGNIFICANT BIT - ‘M’

LEAST SIGNIFICANT BIT - ‘L’

PARITY 2 P-d\F3

*RO-CH10*

NORMAL WORD PARITY

EVEN - ‘EV’ ODD - ‘OD’

NONE - ‘NO’

PARITY

TRANSFERORDER

1 P-d\F4 PARITY BIT LOCATION

LEADS WORD - ‘L’TRAILS WORD - ‘T’

MINOR FRAME

NUMBER OF

MINOR FRAMES

IN MAJOR

FRAME

3 P-d\MF\N

*RO-CH10*

NUMBER OF MINOR FRAMES IN A

MAJOR FRAME

NUMBER OF

WORDS IN A

MINOR FRAME

4 P-d\MF1

*RO-CH10*

SPECIFIES THE NUMBER OF WORDS

IN A MINOR FRAME, AS DEFINED IN

CHAPTER 4, PARAGRAPH 4.3. (THEMINOR FRAME SYNCHRONIZATION

PATTERN IS ALWAYS CONSIDERED

AS ONE WORD, REGARDLESS OF ITS

LENGTH.)

9-53

7/31/2019 IRIG_106_2009




MAXIMUM

PARAMETER FIELD

SIZE

CODE

NAMEDEFINITION

NUMBER OF BITS

IN A MINOR

FRAME

5 P-d\MF2

*RO-CH10*

NUMBER OF BITS IN A MINOR FRAME

INCLUDING MINOR FRAME

SYNCHRONIZATION PATTERN

SYNC TYPE 3P-d\MF3

DEFINE MINOR FRAME

SYNCHRONIZATION TYPE:

FIXED PATTERN - ‘FPT’

OTHER - ‘OTH’

SYNCHRONIZATION PATTERN

LENGTH 2 P-d\MF4

*RO-CH10*

SPECIFY THE MINOR FRAME

SYNCHRONIZATION PATTERN LENGTHIN NUMBER OF BITS.

PATTERN 33 P-d\MF5

*RO-CH10*

DEFINE MINOR FRAME

SYNCHRONIZATION PATTERN IN BITS

(“1”s and “0”s) WITH THE LEFT MOST BIT

AS THE “FIRST BIT TRANSMITTED”

SYNCHRONIZATION CRITERIA

IN SYNC 2

CRITERIAP-d\SYNC1 THIS SPECIFIES THE DESIRED CRITERIA

FOR DECLARING THE SYSTEM TO BE IN

SYNC:

FIRST GOOD SYNC – 0

CHECK - NUMBER OF AGREES

(1 OR GREATER)

NOT SPECIFIED - ‘NS’

SYNC PATTERN

CRITERIA

2 P-d\SYNC2 NUMBER OF BITS THAT MAY BE IN

ERROR IN THE SYNCHRONIZATION

PATTERN

OUT OF SYNCHRONIZATION CRITERIA

NUMBER OF 2

DISAGREESP-d\SYNC3 SPECIFIES THE DESIRED CRITERIA FOR

DECLARING THE SYSTEM OUT OF SYNC:

NUMBER OF DISAGREES, (1 OR

GREATER)

NOT SPECIFIED - ‘NS’

SYNC PATTERNCRITERIA

2 P-d\SYNC4 NUMBER OF BITS THAT MAY BE INERROR IN THE SYNCHRONIZATION

PATTERN

9-54

7/31/2019 IRIG_106_2009




MAXIMUM

PARAMETER FIELD

SIZE

CODE

NAMEDEFINITION

MINOR FRAME FORMAT DEFINITION

P-d\MFW1-nWORD NUMBER 4

*RO-CH10*

WORD POSITION #n IN A MINOR

FRAME, OR FOR CLASS II SYSTEMS,

THE POSITION IN THE DEFINED

FRAME. WORD POSITION 1 FOLLOWS

THE SYNCHRONIZATION PATTERN.

NUMBER OF

BITS

IN WORD

2 P-d\MFW2-n

*RO-CH10*

THE NUMBER OF BITS IN WORD

POSITION #n. IF DEFAULT VALUE, DO

NOT INCLUDE.

NOTE: THE ABOVE PAIR SET MUST BE DEFINED FOR ALL WORDS THAT HAVE A LENGTH

OTHER THAN THE COMMON WORD LENGTH. THEREFORE, ALL WORD POSITIONS NOT

INCLUDED IN THE ABOVE WILL HAVE THE COMMON WORD LENGTH AS A DEFAULT

VALUE.

SUBFRAME SYNCHRONIZATION

NUMBER OF

SUBFRAMEID COUNTERS

2 P-d\ISF\N

*RO-CH10*

SPECIFY THE NUMBER OF SUBFRAME

ID COUNTERS DEFINED WITHIN THEMINOR FRAME.

SUBFRAME IDCOUNTER NAME

32 P-d\ISF1-n*RO-CH10*

SPECIFY THE SUBFRAME ID COUNTERNAME.

SUBFRAME

SYNC

TYPE

2 P-d\ISF2-n

*RO-CH10*

DEFINE THE SUBFRAME

SYNCHRONIZATION TYPE:

ID COUNTER - ‘ID’

OTHER - ‘OT’ DEFINE IN

COMMENTS.

ID COUNTER

SUBFRAME ID

COUNTERLOCATION

4 P-d\IDC1-n

*RO-CH10*

IF ID COUNTER IS DESIGNATED AS THE

SUBFRAME SYNC TYPE, GIVE THEMINOR FRAME WORD POSITION OF

THE COUNTER.

ID COUNTER

WORD LENGTH

2 P-d\IDC2-n

*RO-CH10*

SPECIFY THE MINOR FRAME WORD

LENGTH OF THE WORD CONTAINING

THE ID COUNTER, NUMBER OF BITS.

9-55

7/31/2019 IRIG_106_2009




MAXIMUM

PARAMETER FIELD

SIZE

CODE

NAMEDEFINITION

ID COUNTER

MSB STARTING

BIT LOCATION

2 P-d\IDC3-n

*RO-CH10*

SPECIFY THE BIT LOCATION OF THE ID

COUNTER MSB WITHIN THE WORD.

ID COUNTER

LENGTH

2 P-d\IDC4-n

*RO-CH10*

SPECIFY THE SUBFRAME ID COUNTER

LENGTH, NUMBER OF BITS.

ID COUNTER

TRANSFER

ORDER

1 P-d\IDC5-n

*RO-CH10*

SPECIFY WHETHER THE MOST OR

LEAST SIGNIFICANT BIT IS

TRANSFERRED FIRST:

MOST SIGNIFICANT - ‘M’

LEAST SIGNIFICANT - ‘L’DEFAULT - ‘D’ (AS SPECIFIED IN

TABLE 9-5, WORD TRANSFER ORDER)

ID COUNTER

INITIAL VALUE

3 P-d\IDC6-n

*RO-CH10*

SPECIFY THE INITIAL VALUE OF THE

ID COUNTER.

INITIAL COUNT

SUBFRAME

NUMBER

3 P-d\IDC7-n

*RO-CH10*

SPECIFY THE MINOR FRAME NUMBER

ASSOCIATED WITH THE INITIAL

COUNT VALUE.

ID COUNTER

END VALUE

3 P-d\IDC8-n

*RO-CH10*

SPECIFY THE END VALUE OF THE ID

COUNTER.

END COUNTSUBFRAME

NUMBER

3 P-d\IDC9-n

*RO-CH10*

SPECIFY THE MINOR FRAME NUMBERASSOCIATED WITH THE END COUNT

VALUE.

COUNT

DIRECTION

3 P-d\IDC10-n

*RO-CH10*

SPECIFY THE DIRECTION OF THE

COUNT INCREMENT:

INCREASING - ‘INC’

DECREASING - ‘DEC’

SUBFRAME DEFINITION

NUMBER OF 4

SUBFRAMESP-d\SF\N-n SPECIFY THE NUMBER OF SUBFRAMES

ASSOCIATED WITH THE SUBFRAME ID

COUNTER NAMED ABOVE.

SUBFRAME

NAME

32 P-d\SF1-n-m SPECIFY THE SUBFRAME NAME.

9-56

7/31/2019 IRIG_106_2009




MAXIMUM


SUPERCOM 2 P-d\SF2-n-m IF NOT SUPERCOMMUTATED,ENTER - ‘NO’. OTHERWISE, ENTER

THE NUMBER OF WORD POSITIONS.

LOCATION

DEFINITION

2 P-d\SF3-n-m IF SUPERCOMMUTATED, SPECIFY

HOW THE WORD LOCATIONS ARE

DEFINED:

FIRST WORD AND INTERVAL - ‘FI’

EVERY LOCATION - ‘EL’

NOT APPLICABLE - ‘NA’

SUBFRAME

LOCATION

4 P-d\SF4-n-m-w SPECIFY THE FIRST WORD WITHIN

THE MINOR FRAME THAT CONTAINS

THE SUBFRAME IDENTIFIED. FORTHE CASE WHEN EVERY WORD

LOCATION IS DEFINED, REPEAT THIS

ENTRY FOR EACH WORD POSITION

APPLICABLE. FOR THE FIRST WORD

AND INTERVAL, INCLUDE THE NEXT

ENTRY TO DEFINE THE INTERVAL.

INTERVAL 4 P-d\SF5-n-m SPECIFY THE INTERVAL TO BE USED

TO DEFINE THE WORD LOCATIONS.

SUBFRAME

DEPTH

3 P-d\SF6-n-m SPECIFY THE SUBFRAME DEPTH. IF

NO ENTRY, THEN THE SUBFRAME ID

COUNTER DEPTH WILL BE USED ASTHE DEFAULT VALUE.

NOTE: REPEAT THE ABOVE FOR EACH SUBFRAME IN THE MINOR FRAME FORMAT.

FILTERING

MINOR FRAME

FILTERING

DEFINITIONTYPE

P-d\MFF\FDT2

*RO-CH10*

SPECIFY THE PCM MINOR FRAME

FILTERING DEFINITION TYPE.

“IN” = INCLUSIVE FILTERING

“EX” = EXCLUSIVE FILTERING

NUMBER OFMINOR FRAME

FILTERING

DEFINITIONS

3P-d\MFF\N

*RO-CH10*SPECIFY THE NUMBER OF PCMMINOR FRAME FILTERING

DEFINITIONS.

9-57

7/31/2019 IRIG_106_2009




MAXIMUM


FILTEREDMINOR FRAMENUMBER

3P-d\MFF\MFN-n

*RO-CH10*SPECIFY THE PCM MINOR FRAMENUMBER TO BE FILTERED

NOTE: FOR PCM FORMATS WITH MULTIPLE SUBFRAME ID COUNTERS, ALL

MINOR FRAME NUMBERS DEFINED FOR FILTERING ARE ASSOCIATED WITH THE

FIRST SUBFRAME ID COUNTER.

ASYNCHRONOUS EMBEDDED FORMAT

NUMBER OF

ASYNCHRONOUS

EMBEDDED

FORMATS

1 P-d\AEF\N SPECIFY THE NUMBER OF

ASYNCHRONOUS EMBEDDED

FORMATS: ONE - ‘1’ TWO –‘2’

NONE - ‘0’

DATA LINK

NAME

32 P-d\AEF\DLN-n PROVIDE THE DATA LINK NAME FOR

THIS ASYNCHRONOUS EMBEDDED

FORMAT. REPEAT NAME AND THE

FOLLOWING ENTRIES FOR THE

SECOND FORMAT, AS APPROPRIATE.

(A SEPARATE DATA LINK DEFINITION

MUST BE PROVIDED FOR EACH

ASYNCHRONOUS EMBEDDEDFORMAT.)

SUPERCOM 3 P-d\AEF1-n IF THE ASYNCHRONOUS FORMAT IS

NOT SUPERCOMMUTATED,ENTER - ‘NO’. OTHERWISE, ENTER

THE NUMBER OF HOST MINOR

FRAME WORDS THAT ARE USED.

LOCATION

DEFINITION

2 P-d\AEF2-n IF SUPERCOMMUTATED, SPECIFY


DEFINED:



CONTIGUOUS WORDS - ‘CW’


9-58

7/31/2019 IRIG_106_2009




MAXIMUM


LOCATION 4 P-d\AEF3-n-w SPECIFY THE FIRST WORD WITHIN


THE ASYNCHRONOUS EMBEDDED

FORMAT IDENTIFIED. FOR THE

METHOD WHEN EVERY WORD

LOCATION IS DEFINED, REPEAT

THIS ENTRY FOR EACH WORD

POSITION APPLICABLE. FOR THE

FIRST WORD AND INTERVAL

METHOD, INCLUDE THE NEXT

ENTRY TO DEFINE THE INTERVAL.

INTERVAL 4 P-d\AEF4-n SPECIFY THE INTERVAL TO BE USED

TO DEFINE THE ASYNCHRONOUS

EMBEDDED FORMAT LOCATIONS.

WORD LENGTH 2 P-d\AEF5-n-w SPECIFY THE NUMBER OF

EMBEDDED BITS IN THIS HOST

WORD LOCATION.

MASK 64 P-d\AEF6-n-w IF THE ASYNCHRONOUS PORTION

OF THE WORD IS SHORTER THAN

THE WORD LENGTH, THEN PROVIDE

THE BINARY MASK REQUIRED TOINDICATE WHICH BITS ARE USED (1s

USED, 0s NOT USED). LEFT-MOST

BIT CORRESPONDS TO FIRST BIT

TRANSMITTED.

FORMAT CHANGE

FRAME FORMAT IDENTIFIER

LOCATION 4 P-d\FFI1 SPECIFY THE POSITION IN THE

MINOR FRAME THAT CONTAINS THE

FRAME FORMAT IDENTIFICATION

(FFI) WORD. IF MORE THAN ONE

WORD LOCATION, PROVIDE THE

DETAILS IN THE COMMENTS

RECORD.

9-59

7/31/2019 IRIG_106_2009




MAXIMUM

PARAMETER FIELD

SIZE

CODE

NAMEDEFINITION

MASK 64 P-d\FFI2 IF THE FFI IS SHORTER THAN THE

WORD LENGTH, THEN PROVIDE THEBINARY MASK REQUIRED TO

INDICATE WHICH BITS ARE USED.

LEFTMOST BIT CORRESPONDS TO

FIRST BIT TRANSMITTED.

MEASUREMENT LIST CHANGE

NUMBER OFMEASUREMENT

LISTS

2 P-d\MLC\N SPECIFY THE NUMBER OFMEASUREMENT LISTS THAT ARE

REQUIRED TO BE SELECTED. IF

NONE, ENTER ‘NO’. OTHERWISE,

ENTER THE NUMBER, n.

FFI PATTERN 16 P-d\MLC1-n SPECIFY THE FFI PATTERN THAT

CORRESPONDS TO THEMEASUREMENT LIST (1s and 0s). THIS

ENTRY AND THE NEXT ARE AN

ORDERED PAIR.

MEASUREMENTLIST NAME

32 P-d\MLC2-n SPECIFY THE MEASUREMENT LISTNAME.

FORMAT STRUCTURE CHANGE

NUMBER OF 2

FORMATSP-d\FSC\N SPECIFY THE NUMBER OF FORMATS

TO BE DEFINED.

FFI PATTERN 16 P-d\FSC1-n SPECIFY THE FFI PATTERN THAT

CORRESPONDS TO THE FORMAT THAT IS

DEFINED. THIS ENTRY AND THE NEXT

ARE AN ORDERED PAIR.

DATA LINK ID 32 P-d\FSC2-n IDENTIFY THE FORMAT THAT

CORRESPONDS TO THIS FFI CODE.

ALTERNATE TAG AND DATA

P-d\ALT\N NUMBER OF

TAGS

3 SPECIFY THE NUMBER OF PARAMETERS

INCLUDED WITHIN THIS CATEGORY,

THAT IS, THE NUMBER OF TAGS.

9-60

7/31/2019 IRIG_106_2009




MAXIMUM

PARAMETER FIELD

SIZE

CODE

NAMEDEFINITION

NUMBER OF BITSIN TAG

2 P-d\ALT1 SPECIFY THE NUMBER OF BITS THATARE IN THIS TAG.

NUMBER OF BITS

IN DATA WORD

2 P-d\ALT2 SPECIFY THE NUMBER OF BITS THAT

ARE IN THE COMMON DATA WORD.

FIRST TAG

LOCATION

2 P-d\ALT3 IDENTIFY THE LOCATION OF THE

START OF THE FIRST TAG LOCATION IN

TERMS OF BITS, WITH THE FIRST BIT

POSITION AFTER THE SYNCHRONIZATION

PATTERN BEING NUMBER 1.

SEQUENCE 1 P-d\ALT4 IF THE TAG/DATA WORD SEQUENCE IS

TAG, THEN DATA ENTER ‘N’ FORNORMAL. IF THE DATA PRECEDES THE

TAG, ENTER ‘R’ FOR REVERSED.

ASYNCHRONOUS DATA MERGE FORMAT

NUMBER OF

ASYNCHRONOUS

DATA MERGE

FORMATS

1 P-d\ADM\N SPECIFY THE NUMBER OF

ASYNCHRONOUS DATA MERGE

FORMATS.

DATA MERGE

NAME

32 P-d\ADM\DMN-n PROVIDE THE DATA MERGE NAME

FOR THIS ASYNCHRONOUS DATA

MERGE FORMAT. THIS CAN BE USED

TO IDENTIFY THE SOURCE OF THE

DATA MERGE FORMAT, AS

APPROPRIATE. (USE THE COMMENTS

FIELD TO DESCRIBE THIS DATA

SOURCE FOR THE ASYNCHRONOUS

DATA MERGE FORMAT.)

SUPERCOM 3 P-d\ADM1-n IF THE ASYNCHRONOUS DATA

MERGE FORMAT IS NOT SUPER-COMMUTATED, ENTER - ‘NO’.

OTHERWISE, ENTER THE NUMBER OFHOST MINOR FRAME WORDS THAT

ARE USED.

9-61

7/31/2019 IRIG_106_2009




MAXIMUM

PARAMETER FIELD

SIZE

CODE

NAMEDEFINITION

LOCATION

DEFINITION

2 P-d\ADM2-n IF SUPERCOMMUTATED, SPECIFY


DEFINED:



CONTIGUOUS WORDS - ‘CW’


LOCATION 4 P-d\ADM3-n-w SPECIFY THE FIRST WORD WITHIN


THE ASYNCHRONOUS DATA MERGE

FORMAT IDENTIFIED. FOR THEMETHOD WHEN EVERY WORD

LOCATION IS DEFINED, REPEAT THIS

ENTRY FOR EACH WORD POSITION

APPLICABLE. FOR THE FIRST WORD

AND INTERVAL METHOD, INCLUDE

THE NEXT ENTRY TO DEFINE THE

INTERVAL.

INTERVAL 4 P-d\ADM4-n SPECIFY THE INTERVAL TO BE USED

TO DEFINE THE ASYNCHRONOUSDATA MERGE FORMAT LOCATIONS.

DATA LENGTH 2 P-d\ADM5-n SPECIFY THE NUMBER OF DATA BITSUSED IN THIS DATA MERGE FORMAT.

MSB LOCATION 2 P-d\ADM6-n PROVIDE THE MOST SIGNIFICANT

BIT (MSB) POSITION WITHIN THE

HOST MINOR FRAME LOCATION.

PARITY 2 P-d\ADM7-n IF USED, SPECIFY THE PARITY

INFORMATION:


NONE - ‘NO’

COMMENTS

COMMENTS 6400 P-d\COM PROVIDE THE ADDITIONAL



9-62

7/31/2019 IRIG_106_2009


7/31/2019 IRIG_106_2009



CODEPCM Measurement Description Group (D) NAME

REFERENCE

PAGE

DATA LINKNAME

(D-x\DLN) (9-66)

NUMBER OF MEASUREMENT LISTS (D-x\ML\N)

MEASUREMENT LIST NAME (D-x\MLN-y)

NUMBER OF SELECTED MEASUREMENT FILTERING

AND OVERWRITE DEFINITIONS(D-x\SMF\N-y)

SELECTED MEASUREMENT NAME (D-x\SMF\SMN-y-n)

NUMBER OF MEASURANDS (D-x\MN\N-y)

MEASUREMENT NAME (D-x\MN-y-n) (9-66)

PARITY (D-x\MN1-y-n)

PARITY TRANSFER ORDER (D-x\MN2-y-n)

MEASUREMENT TRANSFER ORDER (D-x\MN3-y-n)

MEASUREMENT FILTER-OVERWRITE TAG (D-x\MFOT-y-n)

*MEASUREMENT LOCATION (9-67)

MEASUREMENT LOCATION TYPE (D-x\LT-y-n)

*MINOR FRAME (9-67)

MINOR FRAME LOCATION (D-x\MF-y-n)

BIT MASK (D-x\MFM-y-n)

*MINOR FRAME SUPERCOMMUTATED (9-68)

ORNUMBER OF MINOR FRAMELOCATIONS

(D-x\MFS\N-y-n)

LOCATION DEFINITION (D-x\MFS1-y-n)

*INTERVAL (9-68)

OR LOCATION IN MINOR FRAME (D-x\MFS2-y-n)

BIT MASK (D-x\MFS3-y-n) (9-68)

INTERVAL (D-x\MFS4-y-n)

*EVERY LOCATION (9-69)

MINOR FRAME LOCATION (D-x\MFSW-y-n-e)

BIT MASK (D-x\MFSM-y-n-e)

*MINOR FRAME FRAGMENTED (9-69)

OR NUMBER OF FRAGMENTS (D-x\FMF\N-y-n)

MEASUREMENT WORD LENGTH (D-x\FMF1-y-n)

LOCATION DEFINITION (D-x\FMF2-y-n) (9-69)

*INTERVAL

OR LOCATION IN MINOR FRAME (D-x\FMF3-y-n)

BIT MASK (D-x\FMF4-y-n)

INTERVAL (D-x\FMF5-y-n)


MINOR FRAME LOCATION (D-x\FMF6-y-n-e)

BIT MASK (D-x\FMF7-y-n-e)

FRAGMENT TRANSFER ORDER (D-x\FMF8-y-n-e)

FRAGMENT POSITION (D-x\FMF9-y-n-e) (9-70)

* SUBFRAME

OR SUBFRAME NAME (D-x\SF1-y-n)

LOCATION IN SUBFRAME (D-x\SF2-y-n)

Figure 9-7. PCM Measurement Description Group (D). (Page 1 of 2)

BIT MASK (D-x\SFM-y-n)

9-64

7/31/2019 IRIG_106_2009



*SUBFRAME SUPERCOMMUTATED (9-71)

OR SUBFRAME NAME (D-x\SFS1-y-n)

NUMBER OF SUBFRAME LOCATIONS (D-x\SFS\N-y-n)

LOCATION DEFINITION (D-x\SFS2-y-n)

*INTERVAL (9-71)

OR LOCATION IN SUBFRAME (D-x\SFS3-y-n)

BIT MASK (D-x\SFS4-y-n) (9-71)

INTERVAL (D-x\SFS5-y-n)


SUBFRAME LOCATION (D-x\SFS6-y-n-e)

BIT MASK (D-x\SFS7-y-n-e)

*SUBFRAME FRAGMENTED (9-72)

OR NUMBER OF FRAGMENTS (D-x\FSF\N-y-n)

MEASUREMENT WORD LENGTH (D-x\FSF1-y-n)

NUMBER OF SUBFRAMES (D-x\FSF2\N-y-n)

SUBFRAME NAME (D-x\FSF3-y-n-m)

LOCATION DEFINITION (D-x\FSF4-y-n-m)

*INTERVAL (9-72)

OR LOCATION IN SUBFRAME (D-x\FSF5-y-n-m)

BIT MASK (D-x\FSF6-y-n-m)

INTERVAL (D-x\FSF7-y-n-m)


SUBFRAME LOCATION (D-x\FSF8-y-n-m-e)

BIT MASK (D-x\FSF9-y-n-m-e)

FRAGMENT TRANSFER ORDER (D-x\FSF10-y-n-m-e)

FRAGMENT POSITION (D-x\FSF11-y-n-m-e) (9-73)

*WORD AND FRAME

NUMBER OF MEASUREMENTLOCATIONS (D-x\MML\N-y-n)

NUMBER OF FRAGMENTS (D-x\MNF\N-y-n-m)

MEASUREMENT WORD LENGTH (D-x\MWL-y-n-m)

WORD POSITION (D-x\WP-y-n-m-e)

WORD INTERVAL (D-x\WI-y-n-m-e)

END WORD POSITION (D-x\EWP-y-n-m-e)

FRAME POSITION (D-x\FP-y-n-m-e) (9-74)

FRAME INTERVAL (D-x\FI-y-n-m-e)

END FRAME POSITION (D-x\EFP-y-n-m-e)

BIT MASK (D-x\WFM-y-n-m-e)

FRAGMENT TRANSFER ORDER (D-x\WFT-y-n-m-e)

FRAGMENT POSITION (D-x\WFP-y-n-m-e)*COMMENTS

COMMENTS (D-x\COM) (9-76)


Figure 9-7. PCM Measurement Description Group (D). (Page 2 of 2)

9-65

7/31/2019 IRIG_106_2009



TABLE 9-6. PCM MEASUREMENT DESCRIPTION GROUP (D)

MAXIMUMPARAMETER FIELD

SIZE

CODENAME

DEFINITION

DATA LINK NAME 32 D-x\DLN PROVIDE THE DATA LINK NAME.

NUMBER OF

MEASUREMENT

LISTS

2 D-x\ML\N SPECIFY THE NUMBER OF

MEASUREMENT LISTS TO BE

PROVIDED.

MEASUREMENT

LIST NAME

32 D-x\MLN-y PROVIDE THE MEASUREMENT LIST

NAME ASSOCIATED WITH THE

FOLLOWING ATTRIBUTES. THEFOLLOWING INFORMATION WILL

HAVE TO BE REPEATED FOR EACH

MEASUREMENT LIST IDENTIFIED IN

THE PCM FORMAT ATTRIBUTES

GROUP.

NUMBER OFSELECTED

MEASUREMENT

FILTERING ANDOVERWRITE

DEFINITIONS

2 D-x\SMF\N-y

*RO-CH10*

SPECIFY THE NUMBER OF PCM

SELECTED MEASUREMENT

FILTERING AND OVERWRITEDEFINITIONS.

SELECTED

MEASUREMENT

NAME

32

D-\SMF\SMN

-y-n

*RO-CH10*

SPECIFY THE PCM SELECTED

MEASUREMENT NAME TO BE

FILTERED AND OVERWRITTEN

NUMBER OF

MEASURANDS

7 D-x\MN\N-y SPECIFY THE NUMBER OF

MEASURANDS INCLUDED WITHIN

THIS MEASUREMENT LIST.

MEASUREMENT

NAME

32 D-x\MN-y-n MEASURAND NAME.

PARITY 2 D-x\MN1-y-n SPECIFY PARITY:

EVEN-‘EV’; ODD - ‘OD’; NONE - ‘NO’

MINOR FRAME DEFAULT - ‘DE’

(AS SPECIFIED IN TABLE 9-5, PARITY)

9-66

7/31/2019 IRIG_106_2009



Table 9-6 (Continued). PCM Measurement Description Group (D) Page 2 x 11

MAXIMUM

PARAMETER FIELD

SIZE

CODE

NAMEDEFINITION

PARITY TRANSFER

ORDER

1 D-x\MN2-y-n PARITY BIT LOCATION:

LEADS WORD - ‘L’

TRAILS WORD - ‘T’

MINOR FRAME DEFAULT - ‘D’

(AS SPECIFIED IN TABLE 9-5,

PARITY TRANSFER ORDER)

MEASUREMENT

TRANSFER ORDER

1 D-x\MN3-y-n MOST SIGNIFICANT BIT FIRST – ‘M’


DEFAULT - ‘D’ (AS SPECIFIED INTABLE 9-5, WORD TRANSFER

ORDER)

MEASUREMENT

FILTER –

OVERWRITE TAG

1 D-x\MFOT-y-n

*RO-CH10*

INDICATES IF THE MEASUREMENT

IS TAGGED FOR EITHER FILTERING

OR OVERWRITING

‘O’ - OVERWRITE

‘F’ - FILTER

‘N’ – NO FILTERING (DEFAULT)

MEASUREMENT LOCATION

MEASUREMENT

LOCATION TYPE

4 D-x\LT-y-n SPECIFY THE NATURE OF THE

LOCATION OF THIS MEASURAND.MINOR FRAME - ‘MF’

MINOR FRAME SUPERCOMMUTATED

–‘MFSC’

MINOR FRAME FRAGMENTED

‘MFFR’

SUBFRAME ‘SF’

SUBFRAME SUPERCOMMUTATED

‘SFSC’

SUBFRAME FRAGMENTED –‘SFFR’

WORD AND FRAME – ‘WDFR’

MINOR FRAME

MINOR FRAMELOCATION

4 D-x\MF-y-n THE MINOR FRAME WORD POSITIONOF THE MEASUREMENT.

9-67

7/31/2019 IRIG_106_2009




MAXIMUM

PARAMETER FIELD

SIZE

CODE

NAMEDEFINITION

BIT MASK 64 D-x\MFM-y-n BINARY STRING OF 1s AND 0s TO


LOCATION THAT ARE ASSIGNED TO

THIS MEASUREMENT. IF THE FULLWORD IS USED FOR THIS


LEFT-MOST BIT CORRESPONDS TO


MINOR FRAME SUPERCOMMUTATED

NUMBER OF MINORFRAME LOCATIONS

4 D-x\MFS\N-y-n

NUMBER OF WORD POSITIONS THATTHE SUPERCOMMUTATED CHANNEL

OCCUPIES, N.

LOCATIONDEFINITION

1 D-x\MFS1-y-n TO SPECIFY: INTERVAL, ENTER - ‘I’EVERY WORD LOCATION, ENTER - ‘E’

INTERVAL

LOCATION IN

MINOR FRAME

4 D-x\MFS2-y-n SPECIFY THE FIRST WORD LOCATION

IN THE MINOR FRAME.

BIT MASK 64 D-x\MFS3-y-n BINARY STRING OF 1s AND 0s TOIDENTIFY THE BITS IN A WORD


THIS SUPERCOMMUTATEDMEASUREMENT. IF THE FULL WORD IS

USED FOR THIS MEASUREMENT, ENTER

- ‘FW’. LEFT-MOST BIT CORRESPONDS

TO FIRST BIT TRANSMITTED.

INTERVAL 3 D-x\MFS4-y-n SPECIFY THE INTERVAL COUNT THAT

IS THE OFFSET FROM THE FIRST WORD

LOCATION AND EACH SUBSEQUENTLOCATION.

9-68

7/31/2019 IRIG_106_2009




MAXIMUM

PARAMETER FIELD

SIZE

CODE

NAME

DEFINITION

EVERY LOCATION

D-x\MFSW-y-n-eMINOR FRAME

LOCATION

4 ENTER THE MINOR FRAME WORD

POSITION OF THE MEASUREMENT.

BIT MASK 64 D-x\MFSM-y-n-e BINARY STRING OF 1s AND 0s TO



THIS SUPERCOMMUTATED

MEASUREMENT. IF THE FULL WORD ISUSED FOR THE MEASUREMENT, ENTER

- ‘FW’. LEFT-MOST BIT CORRESPONDS

TO FIRST BIT TRANSMITTED.

NOTE: ENTER THE MINOR FRAME LOCATION AND BIT MASK FOR EACH OF THE WORD

POSITIONS THAT THE SUPERCOMMUTATED CHANNEL OCCUPIES, (N) LOCATIONS.

MINOR FRAME FRAGMENTED

NUMBER OFFRAGMENTS

1 D-x\FMF\N-y-n

NUMBER OF MINOR FRAME WORDPOSITIONS THAT THE FRAGMENTED

CHANNEL OCCUPIES, N.

MEASUREMENT

WORD LENGTH

3 D-x\FMF1-y-n TOTAL LENGTH OF THE

RECONSTRUCTED BINARY DATA

WORD

LOCATION

DEFINITION

1 D-x\FMF2-y-n TO SPECIFY:

INTERVAL, ENTER - ‘I’EVERY WORD LOCATION, ENTER-‘E’

INTERVAL

LOCATION IN

MINOR FRAME

4 D-x\FMF3-y-n SPECIFY THE FIRST WORD POSITION

THAT THE FRAGMENTED WORDOCCUPIES IN THE MINOR FRAME.

9-69

7/31/2019 IRIG_106_2009




MAXIMUM

PARAMETER FIELD

SIZE

CODE

NAMEDEFINITION

BIT MASK 64 D-x\FMF4-y-n BINARY STRING OF 1s AND 0s TO


POSITION THAT ARE ASSIGNED TO

THIS FRAGMENTED CHANNEL. IF THE

FULL WORD IS USED FOR THIS

MEASUREMENT, ENTER ‘FW’.



INTERVAL 4 D-x\FMF5-y-n SPECIFY THE INTERVAL THAT IS THE

OFFSET FROM THE FIRST WORD

LOCATION AND EACH SUBSEQUENTLOCATION.

EVERY LOCATION

MINOR FRAMELOCATION

4 D-x\FMF6-y-n-e ENTER THE MINOR FRAME WORDPOSITION OF THE MEASUREMENT.

BIT MASK 64 D-x\FMF7-y-n-e BINARY STRING OF 1s AND 0s TO


POSITION THAT ARE ASSIGNED TO

THIS FRAGMENTED MEASUREMENT.IF THE FULL WORD IS USED FOR THIS


LEFT-MOST BIT CORRESPONDS TOFIRST BIT TRANSMITTED.

FRAGMENT

TRANSFER ORDER

1 D-x\FMF8-y-n-e MOST SIGNIFICANT BIT FIRST - ‘M’


DEFAULT - ‘D’ (AS SPECIFIED IN


FRAGMENT

POSITION

1 D-x\FMF9-y-n-e A NUMBER FROM 1 TO N

SPECIFYING THE POSITION OF THIS

FRAGMENT WITHIN THE


WORD. 1 CORRESPONDS TO THE MOST

SIGNIFICANT FRAGMENT. EACH

FRAGMENT POSITION FROM 1 TO N

MUST BE SPECIFIED ONLY ONCE.

NOTE: ENTER THE MINOR FRAME LOCATION AND BIT MASK FOR EACH OF THE WORD

POSITIONS THAT THE FRAGMENTED CHANNEL OCCUPIES, (N) LOCATIONS.

SUBFRAME

SUBFRAME NAME 32 D-x\SF1-y-n ENTER THE SUBFRAME NAME.

9-70

7/31/2019 IRIG_106_2009




MAXIMUM

PARAMETER FIELD

SIZE

CODE

NAMEDEFINITION

LOCATION INSUBFRAME

3 D-x\SF2-y-n SPECIFY THE WORD NUMBER IN THESUBFRAME.

BIT MASK 64 D-x\SFM-y-n BINARY STRING OF 1s AND 0s TOIDENTIFY THE BITS IN A WORD


THIS MEASUREMENT. IF THE FULL

WORD IS USED FOR THE

MEASUREMENT, ENTER - ‘FW’. LEFT-

MOST BIT CORRESPONDS TO FIRST BIT

TRANSMITTED.

SUBFRAME SUPERCOMMUTATED

SUBFRAME NAME 32 D-x\SFS1-y-n ENTER THE SUBFRAME NAME.

NUMBER OF

SUBFRAME

LOCATIONS

3 D-x\SFS\N-y-n NUMBER OF SUBFRAME WORD

POSITIONS THAT THE

SUPERCOMMUTATED CHANNEL

OCCUPIES.

LOCATION

DEFINITION

1 D-x\SFS2-y-n TO SPECIFY:

INTERVAL, ENTER - ‘I’

EVERY WORD LOCATION, ENTER - ‘E’

INTERVAL

LOCATION IN

SUBFRAME

3 D-x\SFS3-y-n SPECIFY THE FIRST WORD POSITION

THAT THE SUPERCOMMUTATED WORDOCCUPIES IN THE SUBFRAME.

BIT MASK 64 D-x\SFS4-y-n BINARY STRING OF 1s AND 0s TO

IDENTIFY THE BIT LOCATIONS IN A

WORD POSITION THAT ARE ASSIGNED

TO THIS SUPER-COMMUTATED

CHANNEL. IF THE FULL WORD IS

USED FOR THIS MEASUREMENT,

ENTER - ‘FW’.



INTERVAL 3 D-x\SFS5-y-n SPECIFY THE INTERVAL THAT IS THE

OFFSET FROM THE FIRST WORDLOCATION AND EACH SUBSEQUENT

LOCATION.

EVERY LOCATION

SUBFRAME 3

LOCATION

D-x\SFS6-y-n-

e

ENTER THE SUBFRAME WORD


9-71

7/31/2019 IRIG_106_2009




MAXIMUM

PARAMETER FIELD

SIZE

CODE

NAMEDEFINITION

BIT MASK 64 D-x\SFS7-y-n-e BINARY STRING OF 1s AND 0s TO


WORD POSITION THAT ARE ASSIGNED

TO THIS SUPER-COMMUTATED

MEASUREMENT. IF THE FULL WORD

IS USED FOR THIS MEASUREMENT,

ENTER ‘FW’.



NOTE: ENTER THE SUBFRAME LOCATION AND BIT MASK FOR EACH OF THE WORD

POSITIONS THAT THE SUPERCOMMUTATED CHANNEL OCCUPIES, (N) LOCATIONS.

SUBFRAME FRAGMENTED

NUMBER OF

FRAGMENTS

1 D-x\ FSF \N-y-n NUMBER OF SUBFRAME WORD

POSITIONS THAT THE FRAGMENTED

CHANNEL OCCUPIES, N.

MEASUREMENTWO

RD LENGTH

3 D-x\FSF1-y-n TOTAL LENGTH OF THE


WORD

NUMBER OF

SUBFRAMES

1 D-x\FSF2\N-y-n NUMBER OF SUBFRAMES

CONTAINING THE FRAGMENTS

SUBFRAME NAME 32 D-x\FSF3-y-n-m ENTER THE SUBFRAME NAME.

LOCATIONDEFINITION 1 D-x\FSF4-y-n-m TO SPECIFY:INTERVAL, ENTER - ‘I’

EVERY WORD LOCATION, ENTER - ‘E’

INTERVAL

LOCATION IN 3

SUBFRAME

D-x\FSF5-y-n-m SPECIFY THE FIRST WORD POSITION

THAT THE FRAGMENTED WORD

OCCUPIES IN THE SUBFRAME.

BIT MASK 64 D-x\FSF6-y-n-m BINARY STRING OF 1s AND 0s TO


WORD POSITION THAT ARE

ASSIGNED TO THIS FRAGMENTED

CHANNEL. IF THE FULL WORD ISUSED FOR THIS MEASUREMENT,

ENTER - ‘FW’.



9-72

7/31/2019 IRIG_106_2009




MAXIMUM

PARAMETER FIELD

SIZE

CODE

NAMEDEFINITION

INTERVAL 3 D-x\FSF7-y-n-m SPECIFY THE INTERVAL THAT IS THE


LOCATION AND EACH SUBSEQUENT

LOCATION.

EVERY LOCATION

SUBFRAME 3

LOCATION

D-x\FSF8-y-n-m-e ENTER THE SUBFRAME WORD


BIT MASK 64 D-x\FSF9-y-n-m-e BINARY STRING OF 1s AND 0s TO


WORD POSITION THAT IS ASSIGNEDTO THIS FRAGMENTED

MEASUREMENT. IF THE FULL WORD

IS USED FOR THIS MEASUREMENT,

ENTER ‘FW’.LEFT-MOST BIT CORRESPONDS TO


FRAGMENT

TRANSFER ORDER

1 D-x\FSF10-y-n-m-e MOST SIGNIFICANT BIT FIRST - ‘M’


DEFAULT - ‘D’ (AS SPECIFIED INTABLE 9-5, WORD TRANSFER ORDER)

FRAGMENTPOSITION 1D-x\FSF11-y-n-m-e

A NUMBER FROM 1 TO N SPECIFYINGTHE POSITION OF THIS FRAGMENT

WITHIN THE RECONSTRUCTED

BINARY DATA WORD.

1 CORRESPONDS TO THE MOST




NOTE: ENTER THE SUBFRAME LOCATION AND BIT MASK FOR EACH OF THE WORD

POSITIONS THAT THE FRAGMENTED CHANNEL OCCUPIES, (N) LOCATIONS.

NOTE: REPEAT THE ABOVE ENTRIES, AS APPROPRIATE FOR EACH SUBFRAME THATCONTAINS THE COMPONENTS OF THE FRAGMENTED WORD.

WORD AND FRAME

NUMBER OF

MEASUREMENTLOCATIONS

4 D-x\MML\N-y-n SPECIFY THE NUMBER OF LOCATION

DEFINITIONS TO FOLLOW FOR THISMEASUREMENT.

9-73

7/31/2019 IRIG_106_2009




MAXIMUM

PARAMETER FIELD

SIZE

CODE

NAMEDEFINITION

NUMBER OF

FRAGMENTS

1 D-x\MNF\N-y-n-m NUMBER OF WORD POSITIONS THAT

EACH FRAGMENTED MEASUREMENT

LOCATION OCCUPIES, N.

ENTER “1” IF THIS MEASUREMENT IS

NOT FRAGMENTED.

MEASUREMENT

WORD LENGTH

3 D-x\MWL-y-n-m TOTAL LENGTH OF THE RECON-

STRUCTED BINARY DATA WORD

WORD POSITION 4 D-x\WP-y-n-m-e SPECIFY THE MINOR FRAME WORD

POSITION OF THIS MEASUREMENT

LOCATION OR FRAGMENT.

WORD INTERVAL 4 D-x\WI-y-n-m-e SPECIFY THE INTERVAL THAT IS THE


POSITION AND EACH SUBSEQUENT

WORD POSITION. AN INTERVAL OF

ZERO INDICATES THAT THERE IS

ONLY ONE WORD POSITION BEING

DEFINED.

END WORD

POSITION

4 D-x\EWP-y-n-m-e SPECIFY THE LAST MINOR FRAME

WORD POSITION OF THIS

MEASUREMENT LOCATION ORFRAGMENT. IF NOT PRESENT,

DEFAULT IS THE END OF THE MINOR

FRAME, ACCORDING TO THE WORD

INTERVAL. IF WORD INTERVAL IS

ZERO, END WORD POSITION IS NOT

USED.

FRAME POSITION 3 D-x\FP-y-n-m-e SPECIFY THE FRAME LOCATION OF

THIS MEASUREMENT LOCATION OR

FRAGMENT.

FRAME INTERVAL 3 D-x\FI-y-n-m-e SPECIFY THE INTERVAL THAT IS THEOFFSET FROM THE FIRST FRAMELOCATION AND EACH SUBSEQUENT

FRAME LOCATION. AN INTERVAL OF

ZERO INDICATES THAT THERE IS

ONLY ONE FRAME LOCATION BEING

DEFINED.

9-74

7/31/2019 IRIG_106_2009




MAXIMUM

PARAMETER FIELD

SIZE

CODE

NAMEDEFINITION

END FRAMEPOSITION

3 D-x\EFP-y-n-m-e SPECIFY THE LAST FRAME LOCATIONOF THIS MEASUREMENT LOCATION

OR FRAGMENT. IF NOT PRESENT,

DEFAULT IS THE END OF THE MAJOR

FRAME, ACCORDING TO THE FRAME

INTERVAL. IF FRAME INTERVAL IS

ZERO, END FRAME POSITION IS NOT

USED.

BIT MASK 64 D-x\WFM-y-n-m-e BINARY STRING OF 1S AND 0S TO

IDENTIFY THE BIT LOCATIONS USED

IN EACH MEASUREMENT LOCATION

OR FRAGMENT. IF THE FULL WORDIS USED, ENTER ‘FW’. LEFT-MOST BIT

CORRESPONDS TO FIRST BIT

TRANSMITTED.

FRAGMENT

TRANSFER ORDER

1 D-x\WFT-y-n-m-e MOST SIGNIFICANT BIT FIRST – ‘M’

LEAST SIGNIFICANT BIT FIRST – ‘L’

DEFAULT – ‘D’ (AS SPECIFIED IN


FRAGMENT

POSITION

1 D-x\WFP-y-n-m-e A NUMBER FROM 1 TO N SPECIFYING

THE POSITION OF THIS FRAGMENT

WITHIN THE RECONSTRUCTEDBINARY DATA WORD.

1 CORRESPONDS TO THE MOST




NOTE: MEASUREMENT WORD LENGTH, FRAGMENT TRANSFER ORDER, AND FRAGMENT

POSITION ATTRIBUTES DO NOT APPLY WHEN THE “NUMBER OF FRAGMENTS”

ATTRIBUTE FOR A MEASUREMENT IS 1.

9-75

7/31/2019 IRIG_106_2009




MAXIMUM

PARAMETER FIELD

SIZE

CODE

NAMEDEFINITION

COMMENTS

COMMENTS 3200 D-x\COM PROVIDE THE ADDITIONAL



NOTE: THIS GROUP WILL CONTAIN A REPETITION OF THE ABOVE INFORMATION UNTIL EACH

MEASUREMENT HAS BEEN DEFINED. ANY WORD POSITION NOT INCLUDED WILL BE TREATED AS

A SPARE CHANNEL OR A “DON’T CARE” CHANNEL. INFORMATION WILL NOT BE PROCESSED FOR

THESE “SPARE” CHANNELS. NOTE THAT MEASUREMENT LIST CHANGES AND FORMAT CHANGES

THAT ARE A PART OF CLASS II SYSTEMS ARE INCLUDED IN THE ABOVE, SINCE THE KEY TO THE

MEASUREMENT DEFINITION IS THE DATA LINK NAME (FORMAT) AND THE MEASUREMENT LIST.

9.5.6.3 Bus Data Attributes (B). Figure 9-8 and Table 9-7 describe bus-originated data formats.

The Bus Data Attributes Group defines the attributes of a MIL-STD-1553 data acquisitionsystem that is compliant with IRIG 106, Chapter 8 or an ARINC 429 data acquisition system that

is consistent with the Aeronautical Radio Inc. specification of ARINC 429 bus data. The

primary components of this group are the recording description and message content definition.The former defines the method by which the data were recorded on the tape such as track spread

versus composite. The latter consists of the message identification information and the

measurement description set. The message identification information defines the contents of thecontrol word that identifies each bus message. The measurement description set describes the

measurement attributes and contains the measurement name that links the measurand to the Data

Conversion Attributes Group (C).

Mode codes are described in the message identification information. If the Subterminal

Address (STA) field contains 00000 or 11111, the information in the Data Word Count/Mode

Code field is a mode code and identifies the function of the mode code. If the mode code hasassociated data words, they are described in this section of the attributes. If the bus message is a

remote terminal to remote terminal transfer, both the transmit command and the receive

command are used to identify the message.

9-76

7/31/2019 IRIG_106_2009



CODE

Bus Data Attributes Group (B) NAME

REFERENCE

PAGE

DATA LINKNAME

(B-x\DLN) (9-79)

TEST ITEM (B-x\TA)

BUS PARITY (B-x\BP)

NUMBER OF BUSES (B-x\NBS\N)

BUS NUMBER (B-x\BID-i)

BUS NAME (B-x\BNA-i)

BUS TYPE (B-x\BT-i)

* USER DEFINED WORDS

USER DEFINED WORD 1 MEASUREMENT (B-x\UMN1-i)

PARITY (B-x\U1P-i)

PARITY TRANSFER ORDER (B-x\U1PT-i)

BIT MASK (B-x\U1M-i)

TRANSFER ORDER (B-x\U1T-i)


PARITY (B-x\U2P-i)

PARITY TRANSFER ORDER (B-x\U2PT-i) BIT MASK (B-x\U2M-i)



PARITY (B-x\U3P-i)

PARITY TRANSFER ORDER (B-x\U3PT-i)

BIT MASK (B-x\U3M-i)


*RECORDING DESCRIPTION (9-81)

NUMBER OF TRACKS (B-x\TK\N-i)

TRACK SEQUENCE (B-x\TS-i-k)

*MESSAGE CONTENT DEFINITION (9-82)NUMBER OF MESSAGES (B-x\NMS\N-i)

MESSAGE NUMBER (B-x\MID-i-n)

MESSAGE NAME (B-x\MNA-i-n)

REMOTE TERMINAL NAME (B-x\TRN-i-n)

REMOTE TERMINAL ADDRESS (B-x\TRA-i-n)

SUBTERMINAL NAME (B-x\STN-i-n)

SUBTERMINAL ADDRESS (B-x\STA-i-n)

TRANSMIT/RECEIVE MODE (B-x\TRM-i-n)

DATA WORD COUNT/MODE CODE (B-x\DWC-i-n)

SPECIAL PROCESSING (B-x\SPR-i-n)

MESSAGE FILTER-OVERWRITE TAG

(B-x\BMG\FOT-i-

n)

*ARINC 429 MESSAGE DEFINITION (9-83)

ARINC 429 LABEL (B-x\LBL-i-n)

Figure 9-8. Bus Data Attributes Group (B). (Page 1 of 2)

ARINC 429 SDI CODE (B-x\SDI-i-n)

9-77

7/31/2019 IRIG_106_2009



*RT/RT RECEIVE COMMAND LIST (9-83)

REMOTE TERMINAL NAME (B-x\RTRN-i-n-m)

REMOTE TERMINAL ADDRESS (B-x\RTRA-i-n-m)

SUBTERMINAL NAME (B-x\RSTN-i-n-m)

SUBTERMINAL ADDRESS (B-x\RSTA-i-n-m)

DATA WORD COUNT (B-x\RDWC-i-n-m)

*MODE CODE (9-84)

MODE CODE DESCRIPTION (B-x\MCD-i-n)

MODE CODE DATA WORDDESCRIPTION

(B-x\MCW-i-n)

*MEASUREMENT DESCRIPTION SET (9-84)

NUMBER OF MEASURANDS (B-x\MN\N-i-n)

MEASUREMENT NAME (B-x\MN-i-n-p)

MEASUREMENT TYPE (B-x\MT-i-n-p)

PARITY (B-x\MN1-i-n-p)

PARITY TRANSFER ORDER (B-x\MN2-i-n-p)

MEASUREMENT FILTER-OVERWRITE TAG

(B-x\BME\FOT-i-n-p)

*MEASUREMENT LOCATION (9-85)

NUMBER OF MEASUREMENTLOCATIONS

(B-x\NML\N-i-n-p)

MESSAGE WORD NUMBER (B-x\MWN-i-n-p-e)

BIT MASK (B-x\MBM-i-n-p-e) (9-85)

TRANSFER ORDER (B-x\MTO-i-n-p-e)

FRAGMENT POSITION (B-x\MFP-i-n-p-e)

*COMMENTS

COMMENTS (B-x\COM) (9-85)


Figure 9-8. (Continued) Bus Data Attributes Group (B). (Page 2 of 2)

9-78

7/31/2019 IRIG_106_2009


7/31/2019 IRIG_106_2009



Table 9-7 (Continued). Bus Data Attributes Group (B) Page 2 x 7

MAXIMUM


PARITY 2 B-x\U1P-i SPECIFY PARITY.


NONE - ‘NO’

PARITY

TRANSFER

ORDER

1 B-x\U1PT-i PARITY BIT LOCATION



BIT MASK 16 B-x\U1M-i BINARY STRING OF 1s AND 0s TO

IDENTIFY THE BIT LOCATIONS THAT ARE

ASSIGNED TO THIS MEASUREMENT IN

THE WORD IDENTIFIED ABOVE. IF THEFULL WORD IS USED FOR THIS

MEASUREMENT, ENTER ‘FW’. LEFT-MOST


TRANSMITTED.

TRANSFER

ORDER

3 B-x\U1T-i MOST SIGNIFICANT BIT FIRST - ‘MSB’

LEAST SIGNIFICANT BIT FIRST - ‘LSB’

DEFAULT – ‘DEF’ (AS SPECIFIED IN


USER DEFINED

WORD 2MEASUREMENT 32

B-x\UMN2-i SPECIFY THE MEASUREMENT NAME

ASSOCIATED WITH THE CONTENT IDLABEL (BITS 5-8) VALUE OF ‘0011’

PARITY 2 B-x\U2P-i SPECIFY PARITY.


NONE - ‘NO’

PARITY

TRANSFER

ORDER





IDENTIFY THE BIT LOCATIONS THAT AREASSIGNED TO THIS MEASUREMENT IN

THE WORD IDENTIFIED ABOVE. IF THE

FULL WORD IS USED FOR THIS

MEASUREMENT, ENTER ‘FW’. LEFT-MOST


TRANSMITTED.

9-80

7/31/2019 IRIG_106_2009




MAXIMUM


TRANSFER

ORDER





USER DEFINED

WORD 3

MEASUREMENT32

B-x\UMN3-i SPECIFY THE MEASUREMENT NAME

ASSOCIATED WITH THE CONTENT ID

LABEL (BITS 5-8) VALUE OF ‘0100’. (VALID

ONLY FOR 1553, WHEN RESPONSE TIME ISNOT USED.)

PARITY

2 B-x\U3P-i SPECIFY PARITY.EVEN - ‘EV’ ODD - ‘OD’

NONE - ‘NO’

PARITY

TRANSFER

ORDER





IDENTIFY THE BIT LOCATIONS THAT ARE

ASSIGNED TO THIS MEASUREMENT IN

THE WORD IDENTIFIED ABOVE. IF THE

FULL WORD IS USED FOR THISMEASUREMENT, ENTER ‘FW’. LEFT-MOST


TRANSMITTED.

TRANSFER

ORDER





RECORDING DESCRIPTION

NUMBER OF 2TRACKS

B-x\TK\N-i ENTER THE NUMBER OF TAPE TRACKSUSED TO RECORD DATA. ANY ENTRY

GREATER THAN ONE INDICATES THAT

THE DATA HAS BEEN SPREAD ACROSS

MULTIPLE TRACKS.

9-81

7/31/2019 IRIG_106_2009




MAXIMUM


TRACK

SEQUENCE

3 B-x\TS-i-k IN THESE ENTRIES, GIVE THE SEQUENCE

ORDER OF TAPE TRACKS THAT SHOULD

BE USED TO RECOVER THE DATA STREAM

IN THE CORRECT ORDER. (THE ORDER

GIVEN SHOULD CORRESPOND TO THE

ACTUAL SKEW OF THE DATA ON THE

TAPE.)

MESSAGE CONTENT DEFINITION

NUMBER OF

MESSAGES

8 B-x\NMS\N-i THE NUMBER OF MESSAGES TO BE

DEFINED.

MESSAGE

NUMBER

8 B-x\MID-i-n THE MESSAGE NUMBER THAT CONTAINS

THE FOLLOWING DATA.

MESSAGE

NAME

32 B-x\MNA-i-n SPECIFY THE MESSAGE NAME.

REMOTETERMINAL

NAME

32 B-x\TRN-i-n ENTER THE NAME OF THE REMOTETERMINAL THAT IS SENDING OR

RECEIVING THIS MESSAGE. FOR RT/RT,

SPECIFY THE SENDING REMOTE

TERMINAL NAME.

REMOTE

TERMINAL

ADDRESS

5 B-x\TRA-i-n SPECIFY THE FIVE BIT REMOTE

TERMINAL ADDRESS FOR THIS MESSAGE.

SUBTERMINAL

NAME

32 B-x\STN-i-n ENTER THE NAME OF THE SUBTERMINAL

THAT IS SENDING OR RECEIVING THIS

MESSAGE.

SUBTERMINAL

ADDRESS

5 B-x\STA-i-n SPECIFY THE FIVE BIT SUBTERMINAL

ADDRESS FOR THIS MESSAGE. USE ‘X’ TO

INDICATE A “DON’T CARE” VALUE.

TRANSMIT/

RECEIVE

MODE

1 B-x\TRM-i-n INDICATE IF THIS COMMAND WORD IS A

TRANSMIT OR RECEIVE COMMAND. FOR

RT/RT, SPECIFY TRANSMIT.

TRANSMIT - ‘1’

RECEIVE - ‘0’

9-82

7/31/2019 IRIG_106_2009




MAXIMUM


DATA WORD

COUNT/MODE

CODE

5 B-x\DWC-i-n ENTER THE NUMBER OF DATA WORDS AS

A BINARY STRING, USING ‘X’ TO

INDICATE A “DON’T CARE” VALUE. IF

THE SUBTERMINAL ADDRESS INDICATES

A MODE CODE, ENTER THE MODE CODE

VALUE AS A BINARY STRING.

SPECIAL

PROCESSING

200 B-x\SPR-i-n PROVIDE ANY SPECIAL PROCESSING

REQUIREMENTS PERTAINING TO THISMESSAGE.

MESSAGEFILTER –

OVERWRITE

TAG

1 B-x\BMG\ FOT-i-n INDICATES IF THE MESSAGE IS TAGGEDFOR FILTERING OR OVERWRITING


ARINC 429 MESSAGE DEFINITION

ARINC 429

LABEL

B-x\LBL-i-n8

SPECIFY THE EIGHT-BIT ARINC 429 LABEL

FOR THIS MESSAGE.

ARINC 429 SDI

CODE

3 B-x\SDI-i-n SPECIFY THE TWO-BIT ARINC 429 SDI

CODE FOR THIS MESSAGE:

ALL SDI – ‘ALL’SDI CODE 0 – ‘0’SDI CODE 1 – ‘1’

SDI CODE 2 – ‘2’

SDI CODE 3 – ‘3’

RT/RT RECEIVE COMMAND LIST

REMOTE

TERMINAL

NAME

32 B-x\RTRN-i-n-m ENTER THE NAME OF THE REMOTE

TERMINAL THAT IS RECEIVING THIS

RT/RT MESSAGE.

REMOTETERMINAL

ADDRESS

5 B-x\RTRA-i-n-m SPECIFY THE FIVE BIT REMOTETERMINAL ADDRESS FOR THIS RT/RT

MESSAGE.

SUBTERMINAL

NAME

32 B-x\RSTN-i-n-m ENTER THE NAME OF THE SUB-TERMINAL

THAT IS RECEIVING THIS RT/RT MESSAGE.

9-83

7/31/2019 IRIG_106_2009




MAXIMUM


SUBTERMINAL

ADDRESS

5 B-x\RSTA-i-n-

mSPECIFY THE FIVE BIT SUBTERMINAL

ADDRESS FOR THIS RT/RT MESSAGE. USE

‘X’ TO INDICATE A “DON’T CARE” VALUE.

DATA WORD

COUNT

5 B-x\RDWC-i-n-

mENTER THE NUMBER OF DATA WORDS AS

A BINARY STRING, USING ‘X’ TO INDICATE

A “DON’T CARE” VALUE. EXCLUDE

STATUS AND TIME WORDS. (AN RT/RT

MESSAGE CANNOT CONTAIN A MODE

CODE.)

MODE CODE

MODE CODE

DESCRIPTION

200 B-x\MCD-i-n DESCRIBE THE FUNCTION OR ACTION

ASSOCIATED WITH THIS MODE CODE.

MODE CODE

DATA WORD

DESCRIPTION

200 B-x\MCW-i-n IF THE MODE CODE HAS AN ASSOCIATED

DATA WORD FOLLOWING THE MODE

CODE COMMAND, PROVIDE A COMPLETE

DESCRIPTION OF THE DATA WORD.

MEASUREMENT DESCRIPTION SET

NUMBER OFMEASURANDS

7 B-x\MN\N-i-n SPECIFY THE NUMBER OF MEASURANDS.

MEASUREMENT

NAME32 B-x\MN-i-n-p MEASURAND NAME

MEASUREMENT

TYPE1 B-x\MT-i-n-p CONTENT IDENTIFICATION:

DATA WORD – ‘D’COMMAND WORD – ‘C’

STATUS WORD – ‘S’

TIME WORD – ‘T’

PARITY 2 B-x\MN1-i-n-p SPECIFY PARITY.EVEN - ‘EV’ ODD - ‘OD’

NONE - ‘NO’

PARITY

TRANSFER

ORDER

1 B-x\MN2-i-n-p PARITY BIT LOCATION



9-84

7/31/2019 IRIG_106_2009



9-85


PARAMETER

MAXIMUM

FIELD

SIZE

CODE NAME DEFINITION

MEASUREMENTFILTER –OVERWRITE TAG

1 B-x\BME\FOT-i-n-p

INDICATES IF THE MEASUREMENT IS TAGGEDFOR FILTERING OR OVERWRITING


MEASUREMENT LOCATION

NUMBER OF

MEASUREMENT

LOCATIONS

2 B-x\NML\N-i-n-p IF THIS MEASUREMENT IS CONTAINED IN

ONE WORD, ENTER ‘1’. IF THIS

MEASUREMENT IS FRAGMENTED, ENTER

THE NUMBER OF FRAGMENTS.

MESSAGE

WORDNUMBER

3 B-x\MWN-i-n-p-e ENTER THE DATA WORD NUMBER WITHIN

A MESSAGE THAT CONTAINS THEMEASUREMENT OR THE FRAGMENTED

MEASURAND.

BIT MASK 64 B-x\MBM-i-n-p-e BINARY STRING OF 1s AND 0s TO IDENTIFY

THE BIT LOCATIONS THAT ARE ASSIGNED

TO THIS MEASURE-MENT IN THE WORD

IDENTIFIED ABOVE. IF THE FULL WORD IS

USED FOR THIS MEASUREMENT, ENTER

‘FW’. LEFT-MOST BIT CORRESPONDS TO


TRANSFERORDER 3 B-x\MTO-i-n-p-e MOST SIGNIFICANT BIT FIRST - ‘MSB’LEAST SIGNIFICANT BIT FIRST- ‘LSB’



FRAGMENT

POSITION

1 B-x\MFP-i-n-p-e A NUMBER FROM 1 TO N SPECIFYING THE

POSITION OF THIS FRAGMENT WITHIN

THE RECONSTRUCTED BINARY DATAWORD. 1 CORRESPONDS TO THE MOST


FRAGMENT POSITION FROM 1 TO N MUST

BE SPECIFIED ONLY ONCE.

NOTE: REPEAT THE ABOVE TO DESCRIBE EACH FRAGMENT OF A FRAGMENTED WORD. THE

TRANSFER ORDER INDICATES WHETHER TO TRANSPOSE THE ORDER OF THE BIT SEQUENCE OR

NOT (LSB INDICATES TO TRANSPOSE THE BIT SEQUENCE).

COMMENTS

COMMENTS 3200 B-x\COM PROVIDE THE ADDITIONAL INFORMATION

REQUESTED OR OTHER INFORMATION DESIRED.

7/31/2019 IRIG_106_2009


9.5.6.4 Message Data Attributes (S). The Message Data Attributes are presented graphically inFigure 9-9 and specified in Table 9-8. The information contained within this group is used to

describe the characteristics and measurement locations within data streams as described by the

UART, Message, Ethernet, and IEEE-1394 Chapter 10 channel data types.

CODEMessage Data Attributes Group (S) NAME REFERENCEPAGE

DATA LINK

NAME(S-d\DLN) (9-88)

TEST ITEM (S-d\TA) (9-88)

NUMBER OF STREAMS (S-d\NS\N)

STREAM NAME (S-d\SNA-i)

MESSAGE DATA TYPE (S-d\MDT-i)

MESSAGE DATA LAYOUT (S-d\MDL-i)

MESSAGE ELEMENT SIZE (S-d\MES-i)

MESSAGE ID LOCATION (S-d\MIDL-i)

MESSAGE LENGTH (S-d\MLEN-i)

MESSAGE DELIMITER (S-d\MDEL-i)

MESSAGE DELIMITER LENGTH (S-d\MDLEN-i)

FIELD DELIMITER (S-d\FDEL-i)

DATA ORIENTATION (S-d\DO-i)

*MESSAGE CONTENT DEFINITION (9-89)

NUMBER OF MESSAGES (S-d\NMS\N-i)

MESSAGE ID (S-d\MID-i-n)

MESSAGE DESCRIPTION (S-d\MNA-i-n)

NUMBER OF FIELDS (S-d\NFLDS\N-i-n)

FIELD NUMBER (S-d\FNUM-i-n-m)

FIELD START (S-d\FPOS-i-n-m)

FIELD LENGTH (S-d\FLEN-i-n-m)

*MEASUREMENT DESCRIPTION SET (9-89)

NUMBER OF MEASURANDS (S-d\MN\N-i-n)

MEASUREMENT NAME (S-d\MN-i-n-p)

PARITY (S-d\MN1-i-n-p)

PARITY TRANSFER ORDER (S-d\MN2-i-n-p)

DATA TYPE (S-d\MBFM-i-n-p)

FLOATING POINT FORMAT (S-d\MFPF-i-n-p)

DATA ORIENTATION (S-d\MDO-i-n-p)

Figure 9-9. Message Data Attributes Group (S)

(Page 1 of 2)

9-86

7/31/2019 IRIG_106_2009


*MEASUREMENT LOCATION(9-91)

NUMBER OFMEASUREMENTLOCATIONS

(S-d\NML\N-i-n-p)

MESSAGE FIELD

NUMBER (S-d\MFN-i-n-p-e)

BIT MASK (S-d\MBM-i-n-p-e)

TRANSFER ORDER (S-d\MTO-i-n-p-e)

FRAGMENT POSITION (S-d\MFP-i-n-p-e)

*COMMENTS (9-92)

COMMENTS (S-d\COM)


Figure 9-9. Message Data Attributes Group (S)

(Page 2 of 2)

9-87

7/31/2019 IRIG_106_2009


TABLE 9-8. MESSAGE DATA ATTRIBUTES GROUP (S)

MAXIMUM


DATA LINK

NAME

32 S-d\DLN IDENTIFY THE DATA LINK NAME

CONSISTENT WITH THE RECORDER-

REPRODUCER GROUP.

TEST ITEM 16 S-d\TA TEST ITEM DESCRIPTION IN TERMS OF

NAME, MODEL, PLATFORM, OR

IDENTIFICATION CODE THAT CONTAINS

THE DATA ACQUISITION SYSTEM.

NUMBER OF

STREAMS

2 S-d\NS\N SPECIFY THE NUMBER OF MESSAGE DATA

STREAMS INCLUDED WITHIN THIS DATALINK.

STREAM NAME 32 S-d\SNA-i SPECIFY THE MESSAGE DATA STREAM

NAME. (SUBCHANNEL NAME OR SAME AS

DATA LINK NAME IF NO SUBCHANNEL.) MESSAGE DATA

TYPE

8 S-d\MDT-i DATA TYPE – ‘ASCII’ OR ‘BINARY’.

MESSAGE DATA

LAYOUT

11 S-d\MDL-i DATA LAYOUT –

‘DELIMITED’ (ASCII DATA TYPE ONLY)

‘FIXED’ (ASCII OR BINARY DATA TYPES)

MESSAGE

ELEMENT SIZE

2 S-d\MES-i ELEMENT SIZE IN NUMBER OF BITS.

MESSAGE ID

LOCATION

4 S-d\MIDL-i MESSAGE ID FIELD NUMBER.

MESSAGE

LENGTH

8 S-d\MLEN-i MESSAGE LENGTH IN NUMBER OF

MESSAGE ELEMENTS. (FIXED DATA

LAYOUT ONLY)

MESSAGE

DELIMITER

6 S-d\MDEL-i MESSAGE DELIMITER – ‘CRLF’ OR ‘CR’ OR

‘LF’ OR HEX VALUE (DELIMITED LAYOUT

ONLY).

MESSAGE

DELIMITER

LENGTH

2 S-d\MDLEN-i MESSAGE DELIMITER LENGTH IN

NUMBER OF MESSAGE ELEMENTS

(DELIMITED LAYOUT ONLY).

FIELD

DELIMITER

10 S-d\FDEL-i FIELD DELIMITER – ‘,’ OR ‘|’, OR ‘BLANK‘

OR ‘TAB’, OR HEX VALUE (DELIMITED

LAYOUT ONLY)

9-88

7/31/2019 IRIG_106_2009


Table 9-8 (Continued). Message Data Attributes Group (S) Page 2 x 5

MAXIMUM


NOTE: A FIELD IS A SET OF ELEMENTS DETERMINED BY THE NUMBER OF ELEMENTS OR

ELEMENTS BETWEEN FIELD DELIMITERS. A MESSAGE CONSISTS OF ONE OR MORE FIELDS,

WHICH CAN BE FIXED OR VARIABLE LENGTH.

DATA

ORIENTATION

1 S-d\DO-i DATA ORIENTATION.



(BINARY DATA TYPE ONLY)

MESSAGE CONTENT DEFINITION

NUMBER OF

MESSAGES

8 S-d\NMS\N-i THE NUMBER OF MESSAGES TO BE

DEFINED.

MESSAGE ID 32 S-d\MID-i-n MESSAGE ID VALUE. ASCII VALUE

IN QUOTES OR HEX VALUE.MESSAGE

DESCRIPTION

64 S-d\MNA-i-n MESSAGE DESCRIPTION

NUMBER OF

FIELDS

4 S-d\NFLDS\N-i-n NUMBER OF FIELDS IN THE

MESSAGE.

FIELD NUMBER 4 S-d\FNUM-i-n-m SPECIFY THE FIELD NUMBER.

FIELD START 5 S-d\FPOS-i-n-m ENTER THE ELEMENT POSITION OF

THE FIELD (ONLY FOR FIXED

COLUMN MESSAGE DATA

LAYOUT)

FIELD LENGTH 5 S-d\FLEN-i-n-m ENTER THE FIELD LENGTH (ONLY

FOR FIXED MESSAGE DATALAYOUT). IF MESSAGE DATA TYPE

IS ASCII, ASCII STRING IN FIELD IS

CONVERTED TO SPECIFIED DATA

TYPE, i.e., FLOAT. IF MESSAGE

DATA TYPE IS BINARY, FIELD IS

CAST AS SPECIFIED DATA TYPE,

i.e., UNSIGNED, SIGNED, FLOAT,

ASCII, etc.

MEASUREMENT DESCRIPTION SET

NUMBER OF

MEASURANDS

4 S-d\MN\N-i-n SPECIFY THE NUMBER OF

MEASURANDS.MEASUREMENT

NAME

32 S-d\MN-i-n-p MEASURAND NAME.

PARITY 2 S-d\MN1-i-n-p NORMAL WORD PARITY:

EVEN-‘EV’;

ODD - ‘OD’;

NONE - ‘NO’

9-89

7/31/2019 IRIG_106_2009



MAXIMUM


PARITY TRANSFER

ORDER

1 S-d\MN2-i-n-p PARITY BIT LOCATION:

LEADS WORD - ‘L’TRAILS WORD - ‘T’

DATA TYPE 8 S-d\MBFM-i-n-p DATA TYPE.

‘ASCII’

‘FLOAT’

‘SIGNED’

‘UNSIGNED’

‘HEX’ (ASCII characters 0-9, A-F) ‘OCTAL’ (ASCII characters 0-7) ‘BINARY’ (ASCII characters 0 and 1) IF MESSAGE DATA TYPE IS BINARY

THEN ONLY ASCII, SIGNED,UNSIGNED, AND FLOAT ARE VALID

NOTE: FOR BINARY MESSAGES THE DATA TYPE DESCRIBES THE FORMAT OF THE RAW

INPUT DATA AS IT APPEARS IN THE STREAM. IF FLOAT IS SPECIFIED IN A BINARY

MESSAGE, THE FLOATING POINT FORMAT ATTRIBUTE DESCRIBES THE SPECIFIC

FLOATING POINT DATA TYPE. FOR ASCII MESSAGES, FLOAT, SIGNED, AND UNSIGNED

DEFINE HOW TO INTERPRET THE ASCII DATA FOR CONVERSION TO AN OUTPUT DATA

TYPE FOR NUMERIC PROCESSING.

FLOATING POINT

FORMAT

8 S-d\MFPF-i-n-p IF DATA TYPE IS ‘FLOAT’, SPECIFY

WHICH FLOATING POINT FORMAT

WILL BE USED.

IEEE 754 SINGLE PRECISION -‘IEEE_32’

IEEE 754 DOUBLE PRECISION –

‘IEEE_64’

MIL STD 1750A SINGLE PRECISION –

‘1750A_32’

MIL STD 1750A DOUBLE PRECISION

– ‘1750A_48’

DEC SINGLE PRECISION – ‘DEC_32’

DEC DOUBLE PRECISION – ‘DEC_64’

DEC “G” DOUBLE PRECISION –

‘DEC_64G’

9-90

7/31/2019 IRIG_106_2009



MAXIMUM

FIELD SIZECODE NAMEPARAMETER DEFINITION

IBM SINGLE PRECISION – ‘IBM_32’IBM DOUBLE PRECISION – ‘IBM_64’

TI SINGLE PRECISION – ‘TI_32’

TI EXTENDED PRECISION – ‘TI_40’

OTHER FORMATS ARE NOTEXCLUDED. SEE APPENDIX O FOR

MORE INFORMATION. (ONLY FOR

BINARY MESSAGE DATA TYPE)

DATA

ORIENTATION

1 S-d\MDO-i-n-p DATA ORIENTATION.



(ONLY FOR BINARY MESSAGE

DATA TYPE)MEASUREMENT LOCATION

NUMBER OF

MEASUREMENT

LOCATIONS

2 S-d\NML\N-i-n-p IF THIS MEASUREMENT IS

CONTAINED IN ONE FIELD, ENTER

‘1’. IF THIS MEASUREMENT IS

FRAGMENTED, ENTER THE

NUMBER OF FRAGMENTS.

MESSAGE FIELDNUMBER

4 S-d\MFN-i-n-p-e ENTER THE FIELD NUMBER WITHINA MESSAGE THAT CONTAINS THE

MEASUREMENT OR THE

FRAGMENTED MEASURAND.

BIT MASK 64 S-d\MBM-i-n-p-e BINARY STRING OF 1s AND 0s TOIDENTIFY THE BIT LOCATIONSTHAT ARE ASSIGNED TO THIS

MEASURE-MENT IN THE FIELD

IDENTIFIED ABOVE. IF THE ENTIRE

FIELD IS USED FOR THIS

MEASUREMENT, ENTER ‘FW’.LEFT-MOST BIT CORRESPONDS TO


TRANSFER ORDER 3 S-d\MTO-i-n-p-e SPECIFY IF THE START BIT IS

MOST SIGNIFICANT - ‘MSB’

LEAST SIGNIFICANT - ‘LSB’

FRAGMENT

POSITION

1 S-d\MFP-i-n-p-e A NUMBER FROM 1 TO N

SPECIFYING THE POSITION OF THIS

FRAGMENT WITHIN THE

RECONSTRUCTED BINARY FIELD. 1

CORRESPONDS TO THE MOST




9-91

7/31/2019 IRIG_106_2009



NOTE: REPEAT THE ABOVE TO DESCRIBE EACH FRAGMENT OF A FRAGMENTED FIELD.

THE TRANSFER ORDER INDICATES WHETHER TO TRANSPOSE THE ORDER OF THE BIT

SEQUENCE OR NOT (LSB INDICATES TO TRANSPOSE THE BIT SEQUENCE).

COMMENTS

COMMENTS 3200 S-d\COM PROVIDE THE ADDITIONAL

INFORMATION REQUESTED OR

ANY OTHER INFORMATION

DESIRED.

9.5.7 PAM Attributes (A). This group provides the information necessary to define the

channelization and measurand definition for a PAM waveform. As with the PCM signal, the tie

to the calibration data is with the measurement name. Figure 9-10 below summarizes the typesof inputs required. Table 9-9 specifies the details required. The information that defines the

measurand for each channel is required for the channels of interest.

CODEPAM Attributes Group (A) NAME

REFERENCEPAGE

DATA LINK

NAME (A-x\DLN) (9-93)

INPUT CODE (A-x\A1)

POLARITY (A-x\A2)

SYNC PATTERN TYPE (A-x\A3)

SYNC PATTERN (OTHER) (A-x\A4)

CHANNEL RATE (A-x\A5)

CHANNELS PER FRAME (A-x\A\N)

NUMBER OF MEASURANDS (A-x\A\MN\N)

*REFERENCE CHANNELS (9-94)0% SCALE CHANNEL NUMBER (A-x\RC1)

50% SCALE CHANNEL NUMBER (A-x\RC2)

FULL SCALE CHANNEL NUMBER (A-x\RC3)

*SUBFRAME DEFINITION (9-94)

NUMBER OF SUBFRAMES (A-x\SF\N)

SUBFRAME n LOCATION (A-x\SF1-n)

SUBFRAME n SYNCHRONIZATION (A-x\SF2-n)

SUBFRAME n SYNCHRONIZATION PATTERN (A-x\SF3-n)

*CHANNEL ASSIGNMENT (9-95)

MEASUREMENT NAME (A-x\MN1-n)

SUBCOM (A-x\MN2-n)

SUPERCOM (A-x\MN3-n)

*LOCATION (9-95)

CHANNEL NUMBER (A-x\LCW-n-s)

SUBFRAME CHANNEL NUMBER (A-x\LCN-n-s-r)

*COMMENTS

COMMENTS (A-x\COM) (9-95)


Figure 9-10. PAM Attributes Group (A).

9-92

7/31/2019 IRIG_106_2009


TABLE 9-9. PAM ATTRIBUTES GROUP (A)

MAXIMUM


DATA LINK

NAME

32 A-x\DLN IDENTIFY THE DATA LINK NAME.

INPUT CODE 2 A-x\A1 DEFINE THE INPUT CODE:

50% DUTY CYCLE - ‘RZ’

100% DUTY CYCLE (NRZ) - ‘NR’

POLARITY 1 A-x\A2 NORMAL - ‘N’ INVERTED - ‘I’

SYNC

PATTERNTYPE

3 A-x\A3 SPECIFY THE SYNCHRONIZATION

PATTERNIRIG 106 - ‘STD’

OTHER - ‘OTH’

SYNC

PATTERN

(OTHER)

5 A-x\A4 DEFINE THE OTHER (NONSTANDARD)

SYNCHRONIZATION PATTERN IN TERMS

OF:

0 – ZERO SCALE

H – HALF SCALE

F – FULL SCALE

X – DON’T CARE

CHANNELRATE

6 A-x\A5 SPECIFY THE CHANNEL RATE INCHANNELS PER SECOND.

CHANNELS

PER FRAME

3 A-x\A\N SPECIFY THE NUMBER OF CHANNELS

PER FRAME INCLUDING THE SYNC

PATTERN AND CALIBRATION

CHANNELS. MAXIMUM ALLOWED IS 128.

NUMBER OF

MEASURANDS

4 A-x\A\MN\N INDICATE THE NUMBER OF

MEASURANDS ASSOCIATED WITH THIS

DATA LINK (SOURCE).

9-93

7/31/2019 IRIG_106_2009


Table 9-9 (Continued). PAM Attributes Group (A) Page 2 x 3

MAXIMUM


REFERENCE CHANNELS

0% SCALE

CHANNEL

NUMBER

3 A-x\RC1 CHANNEL NUMBER OF 0% SCALE

REFERENCE. IF NOT USED, ENTER ‘NON’

(NONE).

50% SCALE

CHANNEL

NUMBER

3 A-x\RC2 CHANNEL NUMBER OF 50% SCALE

REFERENCE. IF NOT USED, ENTER ‘NON’

(NONE).

FULL SCALE

CHANNELNUMBER

3 A-x\RC3 CHANNEL NUMBER OF FULL SCALE

REFERENCE. IF NOT USED, ENTER ‘NON’(NONE).

SUBFRAME DEFINITION

NUMBER OF

SUBFRAMES

1 A-x\SF\N SPECIFY THE NUMBER OF

SUBMULTIPLEXED CHANNELS IN THE

FRAME.

SUBFRAME n

LOCATION

3 A-x\SF1-n CHANNEL NUMBER OF THE SUBFRAME.

(REPEAT THIS ENTRY AND THE

FOLLOWING TWO ENTRIES FOR EACH

SUBFRAME AS A SET.)

SUBFRAME n

SYNCHRONIZA-

TION

3 A-x\SF2-n SPECIFY THE SYNCHRONIZATION

PATTERN FOR THE SUBFRAME:

IRIG 106 - ‘STD’

OTHER - ‘OTH’

SUBFRAME n

SYNCHRONIZA-

TION PATTERN

5 A-x\SF3-n DEFINE THE OTHER (NONSTANDARD)

SYNCHRONIZATION PATTERN IN TERMS

OF:

0 ZERO SCALE

H HALF SCALE

F FULL SCALEX DON’T CARE

OTH – OTHER

9-94

7/31/2019 IRIG_106_2009


Table 9-9 (Continued). PAM Attributes Group (A) Page 3 x 3

MAXIMUM


CHANNEL ASSIGNMENT

MEASUREMENT

NAME

32 A-x\MN1-n GIVE THE MEASUREMENT NAME.

SUBCOM 1 A-x\MN2-n IS THIS A SUBCOMMUTATED CHANNEL?

‘Y’ OR ‘N’

SUPERCOM 1 A-x\MN3-n IS THIS A SUPERCOMMUTATED

CHANNEL? IF YES, ENTER THE NUMBER

OF POSITIONS IT OCCUPIES – n.

IF NO, ENTER - ‘N’A SUPERCOMMUTATED

SUBCOMMUTATED PARAMETER IS

ALLOWABLE AND WILL HAVE ENTRIES

IN THIS AND THE PREVIOUS RECORD.

LOCATION

CHANNEL

NUMBER

3 A-x\LCW-n-s NUMBER OF THE CHANNEL THAT

CONTAINS THIS MEASURAND. IF THIS IS

A SUBCOMMUTATED CHANNEL, ENTER

THE CHANNEL THAT CONTAINS THE

SUBCOMMUTATED CHANNEL.

SUBFRAME

CHANNEL

NUMBER

3 A-x\LCN-n-s-r CHANNEL NUMBER IN THE SUBFRAME,

IF APPROPRIATE.

COMMENTS

COMMENTS 3200 A-x\COM PROVIDE THE ADDITIONAL



9-95

7/31/2019 IRIG_106_2009


9.5.8 Data Conversion Attributes (C). The Data Conversion Attributes Group includes a

definition of the method by which the raw telemetry data is to be converted to meaningful

information. The sensor calibration is contained in the group for each type of sensor that uses astandard calibration curve or for each sensor or parameter that has a unique calibration

requirement. The calibration information can be entered in several different formats. Provisionis made to permit a test organization to convert data set entries to coefficients of an appropriatecurve fit and record the derived coefficients. Figure 9-11 shows the structure of the data

conversion attributes. Table 9-10 contains the detailed information required.

For reference purposes, the following telemetry unit definitions apply:

NOTE

PCM natural binary range as indicated by binary format entry

PAM 0 to full scale (100)

FM (Analog) lower band edge (100) to upper band edge (+100).

9-96

7/31/2019 IRIG_106_2009


CODENAME

REFERENCEPAGEData Conversion Attributes Group (C)MEASUREMENT

NAME (C-d\DCN) (9-99)

*TRANSDUCER INFORMATION (9-99)

TYPE (C-d\TRD1)

MODEL NUMBER (C-d\TRD2)SERIAL NUMBER (C-d\TRD3)

SECURITY CLASSIFICATION (C-d\TRD4)

ORIGINATION DATE (C-d\TRD5)

REVISION NUMBER (C-d\TRD6)

ORIENTATION (C-d\TRD7)

*POINT OF CONTACT (9-99)

NAME (C-d\POC1)

AGENCY (C-d\POC2)

ADDRESS (C-d\POC3)

TELEPHONE (C-d\POC4)

*MEASURAND (9-100)

DESCRIPTION (C-d\MN1)

MEASUREMENT ALIAS (C-d\MNA)

EXCITATION VOLTAGE (C-d\MN2)

ENGINEERING UNITS (C-d\MN3)

LINK TYPE (C-d\MN4)

*TELEMETRY VALUE DEFINITION (9-100)

BINARY FORMAT (C-d\BFM)

*FLOATING POINT

FLOATING POINT FORMAT (C-d\FPF)

*BIT WEIGHT

NUMBER OF BITS (C-d\BWT\N)

BIT NUMBER (C-d\BWTB-n)

BIT WEIGHT VALUE (C-d\BWTV-n)

*INFLIGHT CALIBRATION (9-101)NUMBER OF POINTS (C-d\MC\N)

STIMULUS (C-d\MC1-n)

TELEMETRY VALUE (C-d\MC2-n)

DATA VALUE (C-d\MC3-n)

*AMBIENT VALUE (9-102)

NUMBER OF AMBIENT CONDITIONS (C-d\MA\N)

STIMULUS (C-d\MA1-n)

TELEMETRY VALUE (C-d\MA2-n)

DATA VALUE (C-d\MA3-n)

*OTHER INFORMATION (9-102)

HIGH MEASUREMENT VALUE (C-d\MOT1)

LOW MEASUREMENT VALUE (C-d\MOT2)

HIGH ALERT LIMIT VALUE (C-d\MOT3)

LOW ALERT LIMIT VALUE (C-d\MOT4)

HIGH WARNING LIMIT VALUE (C-d\MOT5)

LOW WARNING LIMIT VALUE (C-d\MOT6)

SAMPLE RATE (C-d\SR)

Figure 9-11. Data Conversion Attributes Group (C). (Page 1 of 2)

9-97

7/31/2019 IRIG_106_2009


*DATA CONVERSION (9-103)

DATE AND TIME RELEASED (C-d\CRT)

CONVERSION TYPE (C-d\DCT)

*ENGINEERING UNITS CONVERSION (9-104)

*PAIR SETS (9-104)

OR NUMBER OF SETS (C-d\PS\N)APPLICATION (C-d\PS1)

ORDER OF FIT (C-d\PS2)

TELEMETRY VALUE (C-d\PS3-n)

ENGINEERING UNITS VALUE (C-d\PS4-n)

*COEFFICIENTS (9-104)

OR ORDER OF CURVE FIT (C-d\CO\N)

DERIVED FROM PAIR SET (C-d\CO1) (9-104)

COEFFICIENT (0) (C-d\CO)

N-TH COEFFICIENT (C-d\CO-n)

*COEFFICIENTS (NEGATIVE POWERS OF X)

OR ORDER (C-d\NPC\N)

DERIVED FROM PAIR SET (C-d\NPC1)

COEFFICIENT (0) (C-d\NPC)

N-TH COEFFICIENT (C-d\NPC-n)

*OTHER (9-105)

ORDEFINITION OF OTHER DATACONVERSION

(C-d\OTH)

*DERIVED PARAMETER (9-106)

OR ALGORITHM TYPE (C-d\DPAT)

ALGORITHM (C-d\DPA)

TRIGGER MEASURAND (C-d\DPTM)

NUMBER OF OCCURRENCES (C-d\DPNO)

NUMBER OF INPUT MEASURANDS (C-d\DP\N)

MEASURAND #N (C-d\DP-n)

NUMBER OF INPUT CONSTANTS (C-d\DPC\N)CONSTANT #N (C-d\DPC-n)

*DISCRETE (9-107)

OR NUMBER OF EVENTS (C-d\DIC\N)

NUMBER OF INDICATORS (C-d\DICI\N)

CONVERSION DATA (C-d\DICC-n)

PARAMETER EVENT DEFINITION (C-d\DICP-n)

* PCM TIME (9-107)

OR PCM TIME WORD FORMAT (C-d\PTM)

* 1553 TIME (9-107)

OR 1553 TIME WORD FORMAT (C-d\BTM)

*DIGITAL VOICE (9-108)

ENCODING METHOD (C-d\VOI\E)

OR DESCRIPTION (C-d\VOI\D)*DIGITAL VIDEO (9-108)

ENCODING METHOD (C-d\VID\E)

OR DESCRIPTION (C-d\VID\D)

*COMMENTS

COMMENTS (C-d\COM) (9-108)


Figure 9-11. Data Conversion Attributes Group (C). (Page 2 of 2)

9-98

7/31/2019 IRIG_106_2009


TABLE 9-10. DATA CONVERSION ATTRIBUTES GROUP (C)

MAXIMUM


MEASUREMENT

NAME32 C-d\DCN GIVE THE MEASUREMENT NAME.

TRANSDUCER INFORMATION

TYPE 32 C-d\TRD1 TYPE OF SENSOR, IF APPROPRIATE

MODEL NUMBER 32 C-d\TRD2 IF APPROPRIATE

SERIAL NUMBER 32 C-d\TRD3 IF APPLICABLE

SECURITYCLASSIFICATION

2 C-d\TRD4 ENTER THE SECURITY CLASSIFICATION OF

THIS MEASURAND.

UNCLASSIFIED - ‘U’

CONFIDENTIAL - ‘C’

SECRET - ‘S’

TOP SECRET - ‘T’

OTHER - ‘O’

APPEND THE FOLLOWING:

IF RECEIVED TELEMETRY SIGNAL

(COUNTS) IS CLASSIFIED, ADD ‘R’.

IF EXPRESSED IN ENGINEERING UNITS, THE

MEASURAND VALUE IS CLASSIFIED, ADD

‘E’. IF BOTH ARE CLASSIFIED, ADD ‘B’.

ORIGINATION

DATE10 C-d\TRD5 DATE OF ORIGINATION OF THIS DATA FILE.

DD – DAY MM – MONTH


REVISION

NUMBER4 C-d\TRD6 SPECIFY THE REVISION NUMBER OF THE

DATA PROVIDED.

ORIENTATION 32 C-d\TRD7 DESCRIBE THE PHYSICAL ORIENTATION OF

THE SENSOR.

POINT OFCONTACT:

NAME

AGENCY

ADDRESS

TELEPHONE

24

48

48

20

C-d\POC1

C-d\POC2

C-d\POC3

C-d\POC4

POINT OF CONTACT WITH THEORGANIZATION THAT PROVIDED THE

CALIBRATION DATA

9-99

7/31/2019 IRIG_106_2009


Table 9-10 (Continued). Data Conversion Attributes Group (C) Page 2 x 10

MAXIMUM


MEASURAND

DESCRIPTION 64 C-d\MN1 DESCRIBE THE PARAMETER BEING

MEASURED.

MEASUREMEN

T ALIAS

32 C-d\MNA ALTERNATE MEASURAND NAME

EXCITATION

VOLTAGE

10 C-d\MN2 SENSOR REFERENCE VOLTAGE, IN VOLTS

ENGINEERINGUNITS

16 C-d\MN3 DEFINE THE ENGINEERING UNITSAPPLICABLE TO THE OUTPUT DATA.

LINK TYPE 3 C-d\MN4 DEFINE THE SOURCE DATA LINK TYPE:

FM (ANALOG) - ‘ANA’ PCM - ‘PCM’

PAM - ‘PAM’ OTHER - ‘OTH’

TELEMETRY VALUE DEFINITION

BINARY 3

FORMAT

C-d\BFM FORMAT OF THE BINARY INFORMATION:

INTEGER - ‘INT’UNSIGNED BINARY - ‘UNS’

SIGN AND MAGNITUDE BINARY (+=0)

‘SIG’SIGN AND MAGNITUDE BINARY (+=1) – ‘SIM’

ONE’S COMPLEMENT - ‘ONE’

TWO’S COMPLEMENT - ‘TWO’

OFFSET BINARY - ‘OFF’

FLOATING POINT - ‘FPT’

BINARY CODED DECIMAL -‘BCD’

BIT WEIGHT – ‘BWT’

OTHER - ‘OTH,’ DEFINE IN COMMENTS.

FLOATING POINT

FLOATING

POINT FORMAT

8 C-d\FPF IF BINARY FORMAT IS ‘FPT’, SPECIFY WHICH

FLOATING POINT FORMAT WILL BE USED.

IEEE 754 SINGLE PRECISION - ‘IEEE_32’

IEEE 754 DOUBLE PRECISION – ‘IEEE_64’

MIL STD 1750A SINGLE PRECISION – ‘1750A_32’

9-100

7/31/2019 IRIG_106_2009



MAXIMUM


MIL STD 1750A DOUBLE PRECISION – ‘1750A_48’

DEC SINGLE PRECISION – ‘DEC_32’

DEC DOUBLE PRECISION – ‘DEC_64’

DEC “G” DOUBLE PRECISION – ‘DEC_64G’

IBM SINGLE PRECISION – ‘IBM_32’

IBM DOUBLE PRECISION – ‘IBM_64’

TI SINGLE PRECISION – ‘TI_32’

TI EXTENDED PRECISION – ‘TI_40’

OTHER FORMATS ARE NOT EXCLUDED.

SEE APPENDIX O FOR MORE INFORMATION.

BIT WEIGHT

NUMBER OF

BITS

2 C-d\BWT\N SPECIFY THE NUMBER OF BITS THAT WILL

HAVE A WEIGHTED VALUE ASSIGNED

BIT NUMBER 2 C-d\BWTB-n BIT NUMBER, AS DEFINED IN CHAPTER 4,

PARAGRAPH 4.3.1.3 (MSB IS BIT 1)

BIT WEIGHT

VALUE

32 C-d\BWTV-n NUMERICAL VALUE INDICATED BY EACH

BIT. SCIENTIFIC NOTATION MAY BE USED.

TO SPECIFY THE SIGN BIT, ENTER – ‘S’.

INFLIGHT CALIBRATION

NUMBER OF

POINTS

1 C-d\MC\N IS INFLIGHT CALIBRATION REQUIRED?

‘N’ FOR NO OR A NUMBER BETWEEN 1 AND 5,

IF IT IS REQUIRED. A MAXIMUM OF FIVE

CALIBRATION POINTS MAY BE INCLUDED.

STIMULUS 32 C-d\MC1-nPROVIDE THE STIMULUS FOR THIS

CALIBRATION POINT.

TELEMETRY

VALUE

16 C-d\MC2-n TELEMETRY UNITS VALUE

DATA VALUE 32 C-d\MC3-n ENGINEERING UNITS VALUE,

SCIENTIFIC NOTATION MAY BE USED.

NOTE: THE ABOVE SET OF THREE ENTRIES MUST BE REPEATED FOR EACH INFLIGHT

CALIBRATION POINT.

9-101

7/31/2019 IRIG_106_2009



MAXIMUM


AMBIENT VALUE

NUMBER OF

AMBIENT

CONDITIONS

1 C-d\MA\N NUMBER OF STATIC OR SIMULATED

CONDITIONS

STIMULUS 32 C-d\MA1-n DESCRIPTION OF THE STATIC ENVIRON-

MENT IN WHICH A NONTEST STIMULUS OR

SIMULATOR IS THE DATA SOURCE

TELEMETRY

VALUE

16 C-d\MA2-n TELEMETRY UNITS VALUE FOR THE STATIC

STIMULUS

DATA VALUE 32 C-d\MA3-n ENGINEERING UNITS VALUE FOR THE

STATIC OR SIMULATED CONDITION.


OTHER INFORMATION

HIGH 32MEASUREMENT

VALUE

C-d\MOT1 HIGHEST ENGINEERING UNIT VALUE

DEFINED BY THE CALIBRATION DATA,SCIENTIFIC NOTATION MAY BE USED.

LOW

MEASUREMENTVALUE

32 C-d\MOT2 LOWEST ENGINEERING UNIT VALUE

DEFINED IN THE CALIBRATION DATA,SCIENTIFIC NOTATION MAY BE USED.

HIGH ALERT

LIMIT VALUE

32 C-d\MOT3 HIGHEST ENGINEERING UNIT VALUE

EXPECTED OR SAFE OPERATING VALUE OF

THE PARAMETER (“RED”), SCIENTIFICNOTATION MAY BE USED.

LOW ALERT

LIMIT VALUE

32 C-d\MOT4 LOWEST ENGINEERING UNIT VALUE


THE PARAMETER (“RED”), SCIENTIFIC


HIGH

WARNING

LIMIT VALUE

32 C-d\MOT5 HIGHEST ENGINEERING UNIT VALUE


THE PARAMETER (“YELLOW”), SCIENTIFIC


9-102

7/31/2019 IRIG_106_2009



MAXIMUM


LOW WARNINGLIMIT VALUE

32 C-d\MOT6 LOWEST ENGINEERING UNIT VALUEEXPECTED OR SAFE OPERATING VALUE OF

THE PARAMETER (“YELLOW”), SCIENTIFIC


SAMPLE RATE 6 C-d\SR ENTER THE SAMPLE RATE IN TERMS OF

SAMPLES/SECOND.

DATA CONVERSION

DATE AND

TIME

RELEASED

19 C-d\CRT DATE AND TIME CALIBRATION WAS

RELEASED:

DD – DAY MM – MONTHYYYY – YEAR HH – HOUR

MI – MINUTE SS – SECOND


CONVERSION

TYPE

3 C-d\DCT DEFINE THE CHARACTERISTICS OF THE

DATA CONVERSION:

NONE - ‘NON’

ENGINEERING UNITS:

PAIR SETS - ‘PRS’

COEFFICIENTS - ‘COE’

COEFFICIENTS (NEGATIVE POWERS OF X)–‘NPC’

DERIVED - ‘DER’DISCRETE - ‘DIS’

PCM TIME - ‘PTM’

1553 TIME - ‘BTM’

DIGITAL VOICE - ‘VOI’

DIGITAL VIDEO - ‘VID’

SPECIAL PROCESSING - ‘SP’ (ENTER IN

COMMENTS RECORD.)

OTHER - ‘OTH’

9-103

7/31/2019 IRIG_106_2009



MAXIMUM


ENGINEERING UNITS CONVERSION

PAIR SETS

NUMBER OF

SETS

2 C-d\PS\N SPECIFY THE NUMBER OF PAIR SETS

PROVIDED, n.

APPLICATION 1 C-d\PS1 ARE THE PAIR SETS TO BE USED TO DEFINE A

POLYNOMINAL CURVE FIT? ‘Y’ (YES) OR ‘N’

(NO). IF THE ANSWER IS NO, THEN THE PAIR

SETS ARE TO BE USED AS A “TABLE LOOKUP”

WITH LINEAR INTERPOLATION BETWEENTHE DEFINED POINTS.

ORDER OF FIT 2 C-d\PS2 SPECIFY THE ORDER OF THE CURVE FIT TO

BE PERFORMED, m. AT LEAST 2 PAIR SETS

MUST BE PROVIDED, AND A MAXIMUM OF 32

PAIR SETS MAY BE INCLUDED. TWELVE OR

MORE PAIR SETS ARE RECOMMENDED FOR A

FIFTH ORDER FIT.

TELEMETRY

VALUE

16 C-d\PS3-n TELEMETRY UNITS VALUE

ENGINEERING

UNITS VALUE

32 C-d\PS4-n ENGINEERING UNITS VALUE,


NOTE: REPEAT THE ABOVE FOR THE n PAIR SETS.

COEFFICIENTS

ORDER OF

CURVE FIT

2 C-d\CO\N SPECIFY THE ORDER OF THE POLYNOMINAL

CURVE FIT, n.

DERIVED FROM

PAIR SET

1 C-d\CO1 WERE THE COEFFICIENTS DERIVED FROM

THE PAIR SET CALIBRATION DATAPROVIDED (‘Y’ OR ‘N’)? IF YES, PROVIDE A

POINT OF CONTACT IN THE COMMENTSRECORD.

COEFFICIENT

(0)

32 C-d\CO VALUE OF THE ZERO ORDER TERM (OFFSET),


9-104

7/31/2019 IRIG_106_2009



MAXIMUM

FIELD

SIZE

CODE

NAMEPARAMETER DEFINITION

N-THCOEFFICIENT

32 C-d\CO-n VALUE OF THE COEFFICIENT OF THE N-THPOWER OF X (FIRST ORDER COEFFICIENT IS

THE EQUIVALENT OF BIT WEIGHT).


NOTE: REPEAT UNTIL ALL N+1 COEFFICIENTS ARE DEFINED.

COEFFICIENTS (NEGATIVE POWERS OF X)

ORDER 2 C-d\NPC\N SPECIFY THE ORDER OF NEGATIVE POWER

COEFFICIENTS, n.

DERIVED FROM

PAIR SET

1 C-d\NPC1 WERE THE COEFFICIENTS DERIVED FROM

THE PAIR SET CALIBRATION DATA

PROVIDED (‘Y’ OR ‘N’)? IF YES, PROVIDE A

POINT OF CONTACT IN THE COMMENTS

RECORD.

COEFFICIENT

(0)

32 C-d\NPC VALUE OF THE ZERO ORDER TERM (OFFSET),


N-TH

COEFFICIENT

32 C-d\NPC-n VALUE OF THE COEFFICIENT OF THE

NEGATIVE N-TH POWER OF X . SCIENTIFIC


NOTE: REPEAT UNTIL ALL N+1 COEFFICIENTS ARE DEFINED. THIS SECTION DESCRIBES

THE CONVERSION EQUATION Y=C0 + C1*(1/X) + C2*(1/X^2) + …+ Cn*(1/X^n), WHERE C0, C1,

C2,…,Cn ARE THE COEFFICIENTS, X IS THE TELEMETRY VALUE, AND Y IS THE RESULTING

EU VALUE.

OTHER

DEFINITION OF

OTHER DATA

CONVERSION

1000 C-d\OTH DEFINE OTHER DATA CONVERSION

TECHNIQUE OR SPECIAL PROCESSING

REQUIREMENT.

9-105

7/31/2019 IRIG_106_2009



MAXIMUM

FIELD

SIZE

PARAMETER CODE NAME DEFINITION

DERIVED PARAMETER

ALGORITHM

TYPE

1 C-d\DPAT SPECIFY WHETHER THE ALGORITHM WILL

BE GIVEN (IN C-d\DPA) AS:

NAME OF ALGORITHM – ‘N’ALGORITHM – ‘A’

SEE APPENDIX P FOR ADDITIONAL DETAILS.

ALGORITHM 240 C-d\DPA DEFINE THE ALGORITHM TO BE USED IN

DERIVING THE PARAMETER. SEE APPENDIX P

FOR ADDITIONAL DETAILS.

TRIGGERMEASURAND

32 C-d\DPTM SPECIFY THE NAME OF THE INPUTMEASURAND THAT TRIGGERS THE

CALCULATION OF THE DERIVED

PARAMETER

NUMBER OF

OCCURRENCES

2 C-d\DPNO SPECIFY HOW MANY TIMES THE TRIGGER

MEASURAND MUST OCCUR BEFORE THE

CALCULATION IS DONE. DEFAULT IS 1.

NUMBER OF

INPUT

MEASURANDS

2 C-d\DP\N SPECIFY THE NUMBER OF INPUT

MEASURANDS USED TO DERIVE THIS

PARAMETER.

MEASURAND

#N

32 C-d\DP-n SPECIFY THE NAME OF THE N-TH INPUT

MEASURAND.

NOTE: CONTINUE UNTIL ALL N MEASURANDS ARE DEFINED.

NUMBER OF

INPUT

2

CONSTANTS

C-d\DPC\N SPECIFY THE NUMBER OF INPUT CONSTANTS

USED TO DERIVE THIS PARAMETER.

CONSTANT #N 32 C-d\DPC-n SPECIFY THE VALUE FOR THE N-TH

CONSTANT. SCIENTIFIC NOTATION MAY BEUSED.

NOTE: CONTINUE UNTIL ALL N CONSTANTS ARE DEFINED.

9-106

7/31/2019 IRIG_106_2009



MAXIMUM

FIELD

SIZE


DISCRETE

NUMBER OF

EVENTS

2 C-d\DIC\N HOW MANY EVENTS ARE ASSOCIATED WITH

THIS DISCRETE FIELD, n?

NUMBER OF

INDICATORS

2 C-d\DICI\N NUMBER OF INDICATORS:

FOR A PCM SYSTEM, PROVIDE THE NUMBER

OF BITS USED FOR THIS DISCRETE SET. FOR

A PAM OR ANALOG CHANNEL, PROVIDE THE

NUMBER OF LEVELS USED TO DEFINE THIS

DISCRETE SET.

CONVERSION

DATA

16 C-d\DICC-n TELEMETRY VALUE, COUNTS FOR PCM,

PERCENT OF FULL SCALE FOR PAM OR

ANALOG.

PARAMETEREVENT

DEFINITION

240 C-d\DICP-n DEFINE THE EVENT FOR THE BIT OR BITFIELD IN A WORD THAT CORRESPONDS TO A

DISCRETE EVENT OR THE PERCENT FULL

SCALE VALUE SUCH AS SWITCH ON OR OFF.

NOTE: CONTINUE TO DEFINE THE EVENTS FOR EACH BIT PATTERN OR VALUE OF THE

DISCRETE MEASURAND.

PCM TIME

PCM TIME

WORD FORMAT

1 C-d\PTM SPECIFY THE PCM TIME WORD FORMAT

USED, AS DEFINED IN CHAPTER 4 (PARA-

GRAPH 4.7).

HIGH ORDER TIME - ‘H’LOW ORDER TIME - ‘L’

MICROSECOND TIME - ‘M’

1553 TIME

1553 TIME

WORD FORMAT

1 C-d\BTM SPECIFY THE 1553 TIME WORD FORMAT

USED, AS DEFINED IN CHAPTER 4

(PARAGRAPH 4.7) AND CHAPTER 8

(PARAGRAPH 8.3)

HIGH ORDER TIME - ‘H’

LOW ORDER TIME - ‘L’

MICROSECOND TIME - ‘M’

RESPONSE TIME - ‘R’

9-107

7/31/2019 IRIG_106_2009



MAXIMUM

FIELD

SIZE


DIGITAL VOICE

ENCODING

METHOD

4 C-d\VOI\E SPECIFY THE VOICE ENCODING METHOD

USED: CVSD - ‘CVSD’ OTHER - ‘OTHR’

DESCRIPTION 640 C-d\VOI\D SPECIFY THE DECODING ALGORITHM TO

BE USED.

DIGITAL VIDEO

ENCODING

METHOD

64 C-d\VID\E SPECIFY THE VIDEO ENCODING METHOD

USED.

DESCRIPTION 640 C-d\VID\D SPECIFY THE DECODING ALGORITHM TO

BE USED.

COMMENTS

COMMENTS 3200 C-d\COM PROVIDE THE ADDITIONAL INFORMATION

REQUESTED OR ANY OTHER

INFORMATION DESIRED.

9.5.9 Airborne Hardware Attributes (H). The Airborne Hardware Attributes Group defines thespecific configuration of airborne instrumentation hardware in use on the item under test. This

group allows the same TMATS file to describe the airborne hardware as well as the telemetry

attributes.

Specific information on the structure and definition of airborne hardware attributes is not

included in this standard. There are far too many hardware systems to try to define them all in

one group. The main purpose of identifying this group is to reserve the ‘H’ designation for thoseinstrumentation organizations that choose to use the TMATS standard in this way.

The only H group attributes defined in this standard are the following:

a. Test Item (code name H\TA) - specifies the item under test and ties the H group to the

G group.

b. Airborne System Type (code name H\ST-n) - identifies the airborne systems beingdescribed in the current file and determines how the rest of the attributes in

the H group will be interpreted.

9-108

7/31/2019 IRIG_106_2009


For anyone wishing to define an H group, it is strongly recommended that

the conventions laid out in this standard be followed. The resultant

document should maintain the look and feel of this standard forconsistency.

9.5.10 Vendor Specific Attributes (V). The Vendor Specific Attributes Group provides

information that is specific to a vendor. This group allows the TMATS file to includeinformation about a particular vendor’s equipment in use during a test. Detailed information

about specific vendors’ equipment is not included in this standard.

The only V-group attributes defined in this standard are the following:

a. Data Source ID (code name V-x\ID) - specifies the Data Source ID consistent with

the General Information Group and ties the V-group to the G group.b. Vendor Name (code name V-x\VN) - a three-character acronym that identifies the

specific vendor and determines how the rest of the attributes in the V group are

interpreted.

All other code names for vendor specific attributes will have the form:

V-x\acr\attribute-string

Where:

acr - is the three-character acronym identifying a specific vendor.

attribute-string - is any attribute that applies to this vendor.

For anyone wishing to define a V group, it is strongly recommended that

the conventions laid out in this standard be followed. The resultantdocument should maintain the look and feel of this standard for

consistency.

9.6 Data Display Standard: Data Display Markup Language (DDML)

The standard format, DDML, has been developed to describe commonly used datadisplays. This DDML standard exists only as an XML schema; it does not exist in the TMATScode name format described in paragraph 9.5. The DDML schema can be found at

(ddml31.xsd). The following paragraphs explain the purpose, objectives, and structure of

DDML, and define the global elements in the schema.

9-109

http://ddml31.xsd/

http://ddml31.xsd/

7/31/2019 IRIG_106_2009


7/31/2019 IRIG_106_2009


Parallel to the typical software modules, DDML is also composed of layers as shown inFigure 9-12 and as described below:

a. Graphics Resources. This layer is similar to “graphics resources” of a typicalsoftware tool. In DDML this layer includes the visual components of a data display

system such as sliders, plots, and strip charts as well as low-level graphic elementssuch as lines, rectangles, etc. Basic graphical shapes are modeled using a WorldWide Web Consortium (W3C) recommended format called “Scalable Vector

Graphics (SVG).”

b. Dynamics. The dynamics layer handles the behavior of an object. It manages the

rules and the variable instances attached to an object.c. Data Variables. Data variables are the links between the objects and the data sources.

Data variables can be atomic or derived. Derived variables may use other derived or

atomic variables in a mathematical expression.d. Data Sources. The last layer of the DDML architecture is the Data Sources layer.

This layer handles various data sources such as text files, Open Database

Connectivity (ODBC), network ports, and ports on data acquisition cards.

At each layer, the parameters used to describe each DDML element are divided into two

groups: DDML sub-elements and custom parameters. DDML sub-elements make up the most

common and most necessary pieces of information needed to represent each element. They arestored as named sub-elements in DDML. Custom parameters are used to store any vendor-

specific information that is not explicitly defined as a DDML sub-element. These parameters are

stored as DDML 'param' elements.

9.6.3 DDML Global Element Glossary. The DDML element names and descriptions can beseen at Table 9-11.

9-111

http://www.w3.org/Graphics/SVG/




7/31/2019 IRIG_106_2009


TABLE 9-11. DDML GLOBAL ELEMENT GLOSSARY

Element Name Description

mathml:apply Defined in the mathml schema and used as a sub-element of variable inDDML, defines a variable as a function of other variables.

axis A sub-element of a display object, represents an axis of any chart-type

display object. It has a sub-element axisType that can be one of two

values: VALUE or TIME. Other sub-elements allow the setting of min and max values, colors, grid line properties, etc.

barchart A display object that shows one or more variables as vertical or

horizontal bars whose lengths correspond to the values.

button A display object that consists of an image or icon that, when clicked,

can assign a value to a variable.color A commonly-used sub-element of many DDML elements, it simply

specifies the color of its parent object. All colors in DDML are storedas base-10 integers that are encoded as 0xRRGGBB.

comparisonOperator Used in rules, defines the comparison between two values. Can be

either GT (greater-than), LT (less-than), GTE (greater-than-or-equal),

LTE (less-than-or-equal), EQ (equal), or NEQ (not equal).

custom_parameters A sub-element of a display object, serves as the parent element of a

group of param elements that specify all of the custom (vendor-specific) parameters for a particular display object.

data_source A pool-level data source that is available for use by any of thevariables in the variable pool.

data_source_pool Contains data_source child elements representing all of the data

sources used by the various objects in the DDML file. Informationabout all data sources (files, db connections, etc.) is kept in the data

source pool.

ddml Root element of a DDML file describing a collection of data displays.

dial A display object that consists of a circular or arc value axis and some

sort of marker or needle that points to the current value along this axis.

Example: a gauge or a compass.

display_objects A sub-element of a model, serves as a container for all of the displayobjects in that model.

9-112

7/31/2019 IRIG_106_2009


Table 9-11 (Continued). DDML Global Element Glossary Page 2 x 4


dynamics A set of variable uses and rules used to define the dynamic behavior of a display object. The dynamicType sub-element describes thedynamic behavior while the variable_use and rules child elements

define how variable values affect that behavior. A dynamicType of

'builtin' is used for display objects that have implicit dynamic behavior,such as charts and sliders. Other possible values of dynamicType

include: visibility, text, subdrawing, scale, scaleY, scaleX, rotate,

relativeMoveY, relativeMoveX, pathMove, lineWidth, lineStyle,foregroundColor, fillUp, fillRight, fillLeft, fillDown, fillEffect,

curveType, blink, backgroundColor, arcDirection, absoluteMoveX,

absoluteMoveY, fillColor, edgeColor.

else Part of a rule, specifies what to do if the criteria specified in the if element are false. The else element can be the parent of one or more

additional rules, or can just specify a value or variable reference.

frequencyplot A display object that is a chart in the frequency domain.

frequencyresponse A display object that is a graph consisting of two value axes

(frequency and magnitude) plotted against a single frequency axis.

grid A table. The grid element is used to group several display objects

(including other grids) together in a tabular layout. Each display sub-object’s location in the grid is specified with its gridRow and

gridColumn elements.

hud A display object that resembles a typical aircraft heads-up display thatconsists of three vertical axes (typically used for velocity, pitch, and

altitude) and one horizontal axis (typically for heading). The center

vertical axis rotates according to a fifth variable (typically roll). Thevariable_uses in the dynamics section are applied in this order: center

vertical axis rotation (roll), center vertical axis (pitch), horizontal axis

(heading), right vertical axis (altitude), left vertical axis (velocity).

if Part of a rule, specifies a comparison between the current variable andsome value.

map An area of a model that displays longitude/latitude map info. The

coordinates of all child objects of a map are in decimal

latitude/longitude values. For distance attributes (e.g. a circle’sradius), degrees latitude are used as the measurement unit.

model A container for data displays. Typically interpreted as a single screenor “page” of display objects. The model object defines its own

coordinate system with the minX, minY, maxX, maxY, xDirection and

yDirection sub-elements. All sub-objects of a model are specified in

coordinates that conform to the system defined by the model.

9-113

7/31/2019 IRIG_106_2009


7/31/2019 IRIG_106_2009


9-115

Table 9-11 (Continued). DDML Global Element Glossary Page 4 x 4


svg:svg Stands for “Scalable Vector Graphics.” SVG is a World Wide WebConsortium (W3C) Recommendation and is defined in its ownschema. In DDML, the <svg> element is used as a sub-element of

<object> to define a display object in terms of the basic shapes that it

is composed of.

textual A display object used for representing text and labels, including bothstatic and dynamic text (such as annunciators). If the text is dynamic,

the valuePosition sub-element specifies where the dynamic value is in

relation to the static label. Use valuePosition='center' if there is nolabel. The valueFormat sub-element is a C printf-style format string

that specifies the format of the dynamic value. For example

valueFormat="%4.2f" indicates that the value should be output as afloating-point value with a maximum width of 4 and with 2 decimal

places.

then Part of a rule, the then element specifies the value to set the attribute to

if the criteria specified in the if element is true. The then element canspecify either the desired value, or a reference to a variable containing

the desired value.

variable A pool-level data variable that is available for use by any of the displayobjects in the DDML file.

variable_pool Contains variable child elements representing all of the variables used

by the various display objects in the DDML file.variable_use A child of the dynamics element, variable_use is used to specify which

variable from the variable pool is used. The pool_ref attribute must

refer to the id attribute of a variable element from the variable_pool.

xychart A display object that is a line or xy scatter plot of variables in they axis vs. other variables in the x axis. The x,y variable pairs are

specified with the xyPair sub-elements.

xyPair A sub-element of certain display objects, it describes how a chart’s

variable_use items are paired. Each xVar and yVar sub-element mustrefer to the id of a variable_use element in the display object’s

dynamics section.


7/31/2019 IRIG_106_2009


RCC Document 106-09, Telemetry Standard, Chapter 10, April 2009

CHAPTER 10

DIGITAL RECORDING STANDARD

TABLE OF CONTENTS

CHANGES TO THIS EDITION OF CHAPTER 10..................................................................... iv

LIST OF FIGURES ........................................................................................................................ v

LIST OF TABLES.......................................................................................................................viii

ACRONYMS................................................................................................................................. ix

10.1 General.......................................................................................................................... 10-1

10.1.1 Interface Levels............................................................................................... 10-2

10.2 Definitions/Acronyms .................................................................................................. 10-4

10.3 Operational Requirements.......................................................................................... 10-7

10.3.1 Recorder Compliancy Requirements .............................................................. 10-710.3.2 Required Configuration .................................................................................. 10-9

10.3.4 Internal System Management ......................................................................... 10-9

10.3.5 Data Download ............................................................................................... 10-9

10.3.6 IEEE-1394b Interface to Recorder Media ...................................................... 10-910.3.7 Required File Tables Entries........................................................................... 10-910.3.8 Recorder Configuration File ......................................................................... 10-10

10.4 Data Download and Electrical Interface.................................................................. 10-13

10.4.1 Fibre Channel (FC) Recorder Download Interface....................................... 10-1410.4.2 IEEE-1394B Recorder Interface................................................................... 10-16

10.4.3 Ethernet Recorder Interface.......................................................................... 10-17

10.5 Interface File Structure Definitions ......................................................................... 10-17

10.5.1 Data Organization ......................................................................................... 10-1810.5.2 Directory Definition...................................................................................... 10-19

10.5.3 Data Definitions ............................................................................................ 10-23

10.6 Data Format Definition ............................................................................................. 10-24

10.6.1 Common Packet Elements ............................................................................ 10-24

10.6.2 PCM Data Packets ........................................................................................ 10-3510.6.3 Time Data Packets ........................................................................................ 10-43

10.6.4 MIL-STD-1553............................................................................................. 10-46

10.6.5 Analog Data Packets..................................................................................... 10-5610.6.6 Discrete Data Packets ................................................................................... 10-63

10.6.7 Computer Generated Data Packets ............................................................... 10-66

10.6.8 ARINC-429 Data Packets............................................................................. 10-8010.6.9 Message Data Packets................................................................................... 10-82

7/31/2019 IRIG_106_2009



10.6.10 Video Packets................................................................................................ 10-8510.6.11 Image Packets ............................................................................................... 10-98

10.6.12 UART Data Packets.................................................................................... 10-102

10.6.13 IEEE-1394 Data Packets............................................................................. 10-10510.6.14 Parallel Data Packets................................................................................... 10-112

10.6.15 Ethernet Data Packets ................................................................................. 10-114

10.7 Recorder Control and Status .................................................................................. 10-117

10.7.1 Recorder Control......................................................................................... 10-117

10.7.2 Communication Ports.................................................................................. 10-11810.7.3 RS-232/422 Port.......................................................................................... 10-118

10.7.4 Commands .................................................................................................. 10-118

10.7.5 Status Requests ........................................................................................... 10-11810.7.6 Serial Status ................................................................................................ 10-118

10.7.7 Default Interface ......................................................................................... 10-118

10.7.8 Serial Commands........................................................................................ 10-11810.7.9 Serial Commands........................................................................................ 10-119

10.7.10 Required Discrete Control Functions.......................................................... 10-12010.7.11 Voltage........................................................................................................ 10-121

10.7.12 Status Query................................................................................................ 10-121

10.7.13 Erase Command.......................................................................................... 10-121

10.7.14 Declassify Command.................................................................................. 10-12110.7.15 Command Enable........................................................................................ 10-121

10.8 Declassification......................................................................................................... 10-122

10.8.1 Approach..................................................................................................... 10-122

10.8.2 Algorithm.................................................................................................... 10-122

10.9 IEEE 1394B Interface to Recorder Media............................................................. 10-12410.9.1 Media Time Synchronization...................................................................... 10-12410.9.2 Physical and Signaling................................................................................ 10-125

10.9.3 Removable Media Communication ............................................................ 10-125

10.9.4 Transport of Serial Commands ................................................................... 10-12510.9.5 Mandated IEEE-1394b Interface Connector............................................... 10-125

10.9.6 Real Time Clock ......................................................................................... 10-126

10.9.7 Mandatory Commands for Processor Devices............................................ 10-12610.9.8 Time Setting Requirements......................................................................... 10-127

10.9.9 Set Time...................................................................................................... 10-127

10.9.10 Date Setting Requirements ......................................................................... 10-127

10.9.11 Checking Battery Status.............................................................................. 10-12810.9.12 Declassification Supporting Commands..................................................... 10-128

10.9.13 Vendor Specific Devices............................................................................. 10-136

10.9.14 Mandatory ORB Formats for the Processor Device ................................... 10-136

10.10 Ground Based Recorders ........................................................................................ 10-142

10.10.1 Interface. ..................................................................................................... 10-143

10.10.2 Data Format ................................................................................................ 10-143

ii

7/31/2019 IRIG_106_2009



10.10.3 Recording Media......................................................................................... 10-14310.10.4 Remote Command and Control .................................................................. 10-144

10.10.5 Data Replay and Reproduction................................................................... 10-144

10.11 Data Interoperability............................................................................................... 10-144

10.11.1 Original Recording Files............................................................................. 10-14410.11.2 Modified Recording Files ........................................................................... 10-14510.11.3 Original Recording and Modified Recording File Extension..................... 10-146

10.11.4 File Naming ................................................................................................ 10-146

10.11.5 Data Transfer File ....................................................................................... 10-14810.11.6 Recording Directory File ............................................................................ 10-149

CHANGES

Numerous updates to Chapter 10 have been made. Highlighting the

changes using different font colors, highlights or other means wasnot practical and would make reading the document difficult.Therefore, a summary of changes is provided below.

iii

7/31/2019 IRIG_106_2009



CHANGES TO THIS EDITION OF CHAPTER 10

Paragraph Description

10.2 Definitions/Acronyms Added definitions for Memory Clear,

Memory Declassification, Memory

Sanitization, and Setup Record.

10.3.9.1.2 UDP Transfer Header Updated Figure 10-3 and Version description.

10.4.3 Ethernet Recorder Interface Defined a protocol (TELNET) for groundbased recorder Ethernet interface.

10.6.1.1 Packet Header Updated the “Data Type Version” field toinclude IRI G 106-09.

10.6.4.3 MIL-STD-1553 Bus Data

Packets, Format 2

Clarified 16PP194 transaction and word

format.

10.6.7.2 Computer Generated Data

Packets Format 1

Various changes to support XML TMATS

format; Added a note for the Setup Record

Configuration Change (SRCC) bit usage.

10.6.x Intra-Packet Time Stamp (in

many 10.6.x)

Corrected the bit in the Packet Flags for the

absolute time.

10.6.10.1 Video Packets, Format 0 Added “Byte Alignment (BA)” bit. Clarified

Figure 10-75.

10.7.1.2 Optional TELNET Control Added 10.7.1.2

10.8 Declassification Added a paragraph on declassification

(associated documents, definition and the

responsibility).

10.9.7 Mandatory Commands forProcessor Devices

Updated Table 1-22 Mandatory ProcessorCommands.

10.9.12 Declassification Supporting

Commands

Added the description of each command.

10.9.14.2 ORB Format Added more description for the Send andReceive commands.

10.11.2.1 Modified Recording FileAnnotation

More explanation on “b” on R-x\RI3 andR-x\RI6.

iv

7/31/2019 IRIG_106_2009



LIST OF FIGURES

Figure 10-1. Functional layout of standard....................................................................... 10-3

Figure 10-2. UDP Transfer Header for non-segmented data.......................................... 10-11

Figure 10-3. UDP Transfer Header for segmented data................................................. 10-12Figure 10-4. General UDP Network Broadcast (full packet). ........................................ 10-13Figure 10-5. General UDP Network Broadcast (segmented packet).............................. 10-13

Figure 10-6. Directory structure. .................................................................................... 10-19

Figure 10-7. Directory block. ......................................................................................... 10-19Figure 10-8. Data recording structure............................................................................. 10-25

Figure 10-9. General packet format................................................................................ 10-26

Figure 10-10. A 32-bit packet format layout.................................................................... 10-27Figure 10-11. Packet trailer for 32-bit data checksum. .................................................... 10-28

Figure 10-12. Packet trailer for 8-bit data checksum. ...................................................... 10-28

Figure 10-13. General PCM data packet, format 1........................................................... 10-36Figure 10-14. PCM packet channel specific data format. ................................................ 10-36

Figure 10-15. PCM Data – unpacked mode sample packet.............................................. 10-40Figure 10-16. PCM Data – packed mode sample packet.................................................. 10-41

Figure 10-17. PCM Data – Throughput Mode sample packet.......................................... 10-41

Figure 10-18. 32-bit Alignment Mode example, 16-bit data words (32-bit

word addressing)........................................................................................ 10-42Figure 10-19. 32-bit Alignment Mode example, 16-bit data words (16-bit

word addressing)........................................................................................ 10-42

Figure 10-20. PCM Intra-packet header. .......................................................................... 10-43Figure 10-21. General time data packet, format 1. ........................................................... 10-44

Figure 10-22. Time Packet channel specific data format. ................................................ 10-44

Figure 10-23. Time data - packet format, day format....................................................... 10-45Figure 10-24. Time data - packet format, day, month, and year format........................... 10-45

Figure 10-25. MIL-STD-1553 Packet channel specific data format. ............................... 10-46

Figure 10-26. MIL-STD-1553 data packet, format 1. ...................................................... 10-47Figure 10-27. MIL-STD-1553 intra-packet data header................................................... 10-47

Figure 10-28. Block status word format........................................................................... 10-48

Figure 10-29. Gap Times word format............................................................................. 10-49

Figure 10-30. MIL-STD-1553 data packet, format 1. ...................................................... 10-50Figure 10-31. 16PP194 message transaction.................................................................... 10-51

Figure 10-32. MIL-STD-1553 16PP194 packet channel specific data format................. 10-51

Figure 10-33. MIL-STD-1553 16PP194 data packet. ...................................................... 10-52Figure 10-34. MIL-STD-1553 16PP194 intra-packet data header format. ...................... 10-52

Figure 10-35. MIL-STD-1553 16PP194 data packet. ...................................................... 10-54Figure 10-36. MIL-STD-1553 26-bit 16PP194 word format. .......................................... 10-55Figure 10-37. 16PP194 Word Format. ............................................................................ 10-56

Figure 10-38. Generic analog data packet, format 1. ....................................................... 10-57

Figure 10-39. Analog packet channel specific data word................................................. 10-57

Figure 10-40. Analog data packet - unpacked mode, msb padding.................................. 10-61Figure 10-41. Analog data packet - unpacked mode, lsb padding.................................... 10-62

Figure 10-42. Analog data packet - packed mode packet................................................. 10-63

v

7/31/2019 IRIG_106_2009



Figure 10-43. General discrete data packet, format 1....................................................... 10-63Figure 10-44. Discrete packet channel data word format................................................. 10-64

Figure 10-45. Discrete data format................................................................................... 10-64

Figure 10-46. Discrete event intra-packet header............................................................. 10-65Figure 10-47. Discrete data packet format. ...................................................................... 10-66

Figure 10-48. General computer generated data packet format. ...................................... 10-66Figure 10-49. Computer generated format 0 channel specific data word format............. 10-67Figure 10-50. Computer generated format 1 channel specific data word format............. 10-67

Figure 10-51. Computer generated format 2 channel specific data word......................... 10-69

Figure 10-52. Events recording period. ............................................................................ 10-70

Figure 10-53. Recording event intra-packet header. ........................................................ 10-72Figure 10-54. General recording event packet format...................................................... 10-73

Figure 10-55. Recording event entry layout..................................................................... 10-73

Figure 10-56. Format showing root index packet............................................................. 10-75Figure 10-57. Channel specific data word format. ........................................................... 10-76

Figure 10-58. Recording index intra-packet header. ........................................................ 10-77

Figure 10-59. General recording root index packet.......................................................... 10-78Figure 10-60. Recording root index entry layout. ............................................................ 10-78

Figure 10-61. General recording node index packet. ....................................................... 10-79

Figure 10-62. Recording node index entry layout............................................................ 10-79

Figure 10-63. ARINC-429 data packet format................................................................. 10-80Figure 10-64. ARINC-429 packet channel specific data word format............................. 10-81

Figure 10-65. Intra-packet data header format. ................................................................ 10-81

Figure 10-66. Message data packet format....................................................................... 10-82Figure 10-67. Complete message channel specific data word format.............................. 10-83

Figure 10-68. Segmented message channel specific data word format............................ 10-83Figure 10-69. Message data intra-packet header. ............................................................. 10-84

Figure 10-70. Intra-packet data header format. ................................................................ 10-84

Figure 10-71. General MPEG-2/H.264 video packet, format 0. ...................................... 10-85Figure 10-72. Video packet channel specific data word format....................................... 10-86

Figure 10-73. Intra-packet header..................................................................................... 10-88

Figure 10-74. Format 0 MPEG-2/H.264 video frame sync and word format,16-bit little-endian aligned......................................................................... 10-89

Figure 10-75. Format 0 MPEG-2/H.264 video frame sync and word format,

16-bit big-endian (native) aligned.............................................................. 10-89

Figure 10-76. Format 0 MPEG-2/H.264 Video Data Packet(Example is 16-bit Aligned)....................................................................... 10-89

Figure 10-77. General MPEG-2 video packet, format 1. ................................................. 10-90

Figure 10-78. MPEG-2 channel specific data word format.............................................. 10-91Figure 10-79. Intra-packet header..................................................................................... 10-93

Figure 10-80. General AVC/H.264 video packet, format 2. ............................................ 10-94

Figure 10-81. AVC/H.264 channel specific data word format......................................... 10-95Figure 10-82. Intra-packet header..................................................................................... 10-97

Figure 10-83. Image packet, format 0. ............................................................................. 10-98

Figure 10-84. Image packet channel specific data word format....................................... 10-98Figure 10-85. Image data intra-packet header, format 0. ................................................. 10-99

vi

7/31/2019 IRIG_106_2009



Figure 10-86. Still Imagery packet, format 1. ................................................................ 10-100Figure 10-87. Still Imagery packet channel specific data word format.......................... 10-101

Figure 10-88. Still Imagery intra-packet header............................................................. 10-102

Figure 10-89. UART data packet format........................................................................ 10-103Figure 10-90. UART packet channel specific data word format.................................... 10-103

Figure 10-91. UART data intra-packet header. .............................................................. 10-104Figure 10-92. Intra-packet data header format. .............................................................. 10-104Figure 10-93. IEEE-1394 data packet, format 0............................................................. 10-105

Figure 10-94. IEEE-1394 channel specific data word.................................................... 10-105

Figure 10-95. IEEE-1394 intra-packet header................................................................ 10-106

Figure 10-96. IEEE-1394 event data word format. ........................................................ 10-108Figure 10-97. IEEE-1394 data packet, format 1............................................................. 10-109

Figure 10-98. IEEE-1394 channel specific data word format 1. .................................... 10-109

Figure 10-99. IEEE-1394 format 1 intra-packet header. ................................................ 10-110Figure 10-100. Intra-packet data header - message ID word............................................ 10-110

Figure 10-101. Parallel data packet, format 0................................................................... 10-112

Figure 10-102. Parallel packet channel specific data word format. ................................. 10-112Figure 10-103. Parallel data, up to 8-bit wide words. ...................................................... 10-113

Figure 10-104. Parallel data, 9-16 bit wide words............................................................ 10-113

Figure 10-105. Parallel data, (Example: 28-bit wide words)............................................ 10-113

Figure 10-106. DCRsi Scan, 9-auxiliary data byte +4356 bytes. ..................................... 10-114Figure 10-107. Ethernet Data packet format 1. ................................................................ 10-115

Figure 10-108. Ethernet Data packet format 1 channel specific data word...................... 10-116

Figure 10-109. Ethernet Data format 1 intra-packet header............................................. 10-116Figure 10-110. Intra-packet frame ID word. .................................................................... 10-117

Figure 10-111. Required discrete control functions. ........................................................ 10-120Figure 10-112. Discrete control and indicator functional diagram................................... 10-120

Figure 10-113. Removable media..................................................................................... 10-125

Figure 10-114. RMM .HEALTH command response...................................................... 10-127Figure 10-115. Updating the Bad Block Table................................................................. 10-129

Figure 10-116. Login ORB format. .................................................................................. 10-137

Figure 10-117. Login response format. ............................................................................ 10-138Figure 10-118. Send command ORB format.................................................................... 10-139

Figure 10-119. Send data buffer format. .......................................................................... 10-140

Figure 10-120. Receive command block ORB format (8 quadlets). ................................ 10-141

Figure 10-121. Receive data buffer format ASCII format. .............................................. 10-142Figure 10-122. Receive data buffer binary format. .......................................................... 10-142

vii

7/31/2019 IRIG_106_2009



LIST OF TABLES

Table 10-1. “Required” and “Recommended” SCSI Commands, Features,and Parameters........................................................................................... 10-15

Table 10-2. Directory Block Format............................................................................. 10-20

Table 10-3. File Entry Format....................................................................................... 10-21Table 10-4. Prohibited Characters (Hexadecimal Representation).............................. 10-23Table 10-5. File Name Examples .................................................................................. 10-24

Table 10-6. Packet Requirements.................................................................................. 10-29

Table 10-7. Data Type Names and Descriptions........................................................... 10-32Table 10-8. Units of Measure........................................................................................ 10-46

Table 10-9. Command Summary ................................................................................ 10-119

Table 10-10. Recorder LED States................................................................................ 10-122Table 10-11. Mandatory Processor Commands ............................................................ 10-126

Table 10-12. RMM States ............................................................................................. 10-135

Table 10-13. Command Error Codes ............................................................................ 10-136

viii

7/31/2019 IRIG_106_2009



ACRONYMS

ANSI American National Standards InstituteAPI Application Programming Interface

ARINC Aeronautical Radio, Incorporated

CCM Command and Control MnemonicCD Collision DetectionCDB Command Descriptor Block

CSDW Channel Specific Data Word

CSMA Carrier-Sense Multiple AccessCSR Control and Status Register

DCRsi Digital Cartridge Recording System (a recording method and digital data

interface)DITS Digital Information Transfer System

DoD Department of Defense

ECL Emitter-coupled LogicFCP Fibre Channel Protocol

FCPL Channel Private LoopFC-PLDA Fibre Channel Private Loop SCSI Direct Attach

GCC GNU Compiler Collection

GPS Global Positioning System

HSDB High Speed Data BusI/O Input/Output

IC Intelligence Community

IEC International Electrotechnical CommissionIEEE Institute of Electrical and Electronic Engineers

IETF Internet Engineering Task Force

IOCTL I/O control codeIP Internet Protocol

IRIG Inter-range Instrumentation Group

iSCSI Internet Small Computer Systems InterfaceiSNS Internet Storage Name Service

ISO International Organization for Standards

IT Information Technology

ITU International Telecommunications UnionIU Information Unit

KLV Key-Length-Value

LBA Logical Block AddressLSB Least Significant Bit

LUN Logical Unit NumberMAC Media Access ControlMAS Military Agency for Standardization

MBR Master Boot Record

MISB Motion Imagery Standards Board

MISP Motion Imagery Standards ProfileMPEG Moving Picture Experts Group

MUX Multiplexer

ix

7/31/2019 IRIG_106_2009



x

NADSI NATO Advanced Data Storage InterfaceNATO North Atlantic Treaty Organization

NSG National System for Geospatial Intelligence

NSG National System for Geospatial IntelligenceNSIF NATO Secondary Imagery Format

NSIF NATO Secondary Imagery FormatORB Operation Request Block OS Operating System

PCM Pulse Code Modulation

PDU Protocol Data Unit

PS Program StreamsRCC Range Commanders Council

RFC Request For Comment

RIU Remote Interface UnitRMM Removable Memory Module

RS Recommended Standard

RTC Relative Time CounterSAM SCSI Architecture Model

SBC SCSI Block Commands

SBP Serial Bus Protocol

SCSI Small Computer Systems InterfaceSD Standard Definition

SLP Service Location Protocol

SPC SCSI Primary CommandsSPT SCSI Pass Through

SRB SCSI Request Block STANAG Standardization Agreement

TCP Transmission Control Protocol

TM TelemetryTMATS Telemetry Attributes Transfer Standard

TS Transport Stream

UART Universal Asynchronous Receiver and TransmitterUDP User Datagram Protocol

WMUX Weapons MUX

7/31/2019 IRIG_106_2009



CHAPTER 10

DIGITAL RECORDING STANDARD

10.1 General

A large number of unique and proprietary data structures have been developed for

specific data recording applications which required unique decoding software programs. Theactivities of writing unique decoding software, checking the software for accuracy, and decoding

the data tapes are extremely time consuming and costly. In the late 1990s, the test ranges started

to see the implementation of non-tape-based, high-data-rate recorders, the most predominate of which were solid-state memory devices. Then, as high-data-rate digital recorders were fielded

and as solid state technology began to emerge, the Telemetry Group (TG) saw the need and

formed an ad hoc committee for a computer-compatible digital data acquisition and recording

standard.

There is a need for a digital data acquisition and recording standard (see the functional

layout at Figure 10-1) that supports a broad range of requirements, including:a. Data download and interface.

b. One or more multiplexed data streams.c. One or more single data streams.

d. Data format definitions.

e. Recorder control.

f. Media declassification.g. Data interoperability.

Specifically, this digital recording standard shall be compatible with the multiplexing of

both synchronous and asynchronous digital inputs such as pulse code modulation (PCM) andMIL-STD-1553 data bus, time, analog, video, Aeronautical Radio, Inc. (ARINC) 429, discrete,

and RS-232/422 communication data. This digital recording standard will allow use of a

common set of playback/data reduction software to take advantage of emerging random accessrecording media.

Within this standard, where text and/or figures are used to provide

descriptions, meaning, and/or explanations, the text shall take precedence

over figures.

10-1

7/31/2019 IRIG_106_2009



10.1.1 Interface Levels. The purpose of this chapter is to establish a common interfacestandard for the implementation of digital data acquisition and recording systems by the

organizations participating in the Range Commanders Council (RCC). This standard does not

imply hardware architecture such as the coupling of data acquisition, multiplexing, and mediastorage. The required interface levels are contained in this standard (see a through e below). In

addition, declassification requirements are discussed in paragraph 10.8, ground based recordingis discussed in paragraph 10.10, and data interoperability requirements are discussed inparagraph 10.11.

a. Data Download and Electrical Interface, which is the physical interface for data

access, is defined in paragraph 10.4.

b. Interface File Structure, which defines data access structure, is described in

paragraph 10.5.

c. Data Format Definition, which defines data types and packetization requirements,is defined in paragraph 10.6.

d. Recorder Control and Status, which defines command and control mnemonics,

status, and their interfaces, is described in paragraph 10.7.

e. IEEE 1394B Interface to Recorder Removable Media is defined in paragraph

10.9.

f. Ground Recorder Interface, which defines unique interoperability requirements of

a ground recorder, is described in paragraph 10.10.

g. Data Interoperability, which defines requirements for the annotation,

modification, and exchange of recorded data, is described in paragraph 10.11.

10-2

7/31/2019 IRIG_106_2009



Removable & COTS Recording Media

IRIG 106 Chapter 10 Digital Recorder Standard

Ref Section 10.11

Original Data RecordingsModified Data Recordings

Download Naming &Recording Transfers

Ref Section 10.9

RMM Download &Electrical Interface

IEEE-1394B

Ref Section 10.4

Recorder Download &Electrical Interface

IEEE-1394BFibre

Channel

RS-232RS-422

Ref Section 10.7

Recorder Control & Status

ElectricalDiscrete

Ref Section 10.5

Interface File Structure

Ref Section 10.3

Operational Requirments

10Mhz RTC

Intra-Data Time

CGDP

Channel 0

Ref Section 10.6

Data Format &

Packetization Definition

DataChannel n

TimeChannel n

Ref Section 10.10

Ground Recording & Remote Data Access

Ethernet/iSCSI/TELNETCOTS Media & Interface

Ref Section 10.8

Media Declassification

Figure 10-1. Functional layout of standard.

10-3

7/31/2019 IRIG_106_2009



10.2 Definitions/Acronyms

The following are definitions and acronyms which are used in this standard and areprovided as a means of removing ambiguities within the standard.

Absolute Time: Is a hypothetical time that either runs at the same rate for all the observers in

the universe or the rate of time each observer can be scaled to by multiplying the observer’s rateby a constant.

AET: Audio Encoding Type

ARINC: Aeronautical Radio, Inc

ATA: Advanced Technology Attachment

Basic Character Set (BCS): Based on ISO/IEC 10646-1, the Universal Multiple-Octet Coded

Character Set (UCS). The North Atlantic Treaty Organization (NATO) Imagery Interoperability

Architecture (NIIA) limits characters to a subset rather than allowing all characters. The subsetwill be single octets, known as the Basic Character Set (BCS).

Block: The smallest unit of addressable memory that can be written to, read from, and/or erased.Bad Block: A block determined to be unreliable for storing user data.

Bad Block Table: A table of bad block entries for a memory board. The data stored in the entry

identifies the chip and block number of the bad block. The table entry also contains a flag field.The flag field is used to determine the circumstance in which the bad block was detected. It also

provides a flag indicating whether the corresponding bad block has previously been “Secure

Erased.”

Byte: A contiguous set of 8 bits that are acted on as a unit.

Channel ID: A unique value assigned to each channel in a system. Each channel must have aunique Channel ID (data channels and playback channels).

Channel Specific Data Word: A required word for each data type channel that has data

specific information.

Commercial Off-The-Shelf (COTS) Media: Any recording media (such as hard disks, solidstate drives, RAID, and JBOD) that is ready-made and available for sale to the general public. In

the context of this standard, all COTS Media shall conform to paragraph 10.3.10 with theexception of Ground Based Recorders COTS Media.

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.

Data Streaming: Streaming of current value data whether it is being recorded or not, and

playback streaming of recorded data from a file. Data Streaming sends the data to one or moredestinations simultaneously (e.g., recording media, recorder data interfaces).

DCRsi: Reference AMPEX Data Systems Corp.

Ground Based Recorder: Records IRIG-106 Chapter 10 data and may optionally reproduce the

recorded data. It supports the same data format and remote command and control operations as

an On-Board Recorder. Instead of an RMM, a ground recorder will generally use COTS mediaand/or data streaming to a network. Ground Based Recorder requirements to be in 100 percent

10-4

7/31/2019 IRIG_106_2009



compliancy with this standard are defined in paragraph 10.3.

IEEE-1588 Time: Time as specified by IEEE Std 1588-2002, “1588 IEEE Standard for aPrecision Clock Synchronization Protocol for Networked Measurement and Control Systems.”

FC-PI: Fibre Channel-Physical Interfaces.

FC-FS: Fibre Channel-Framing and Signaling.

Intra-Packet Data Header: A header containing time, status, and/or data information for the

tagging of data inside a packet.

IAW: In Accordance With.

JBOD: Just a bunch of disks.

Long Word: A contiguous set of 32 bits that are acted on as a unit.

lsb: The “least significant bit” of a series of bits.

LSB: The “least significant byte” of a series of bytes.

LSW: The “least significant word” of a series of words.

LSLW: The “least significant long word” of a series of long words.

Mandatory: Defines a Mandatory requirement of this standard for full compliancy. Mandatory

requirements as defined in this standard are based on the use of “shall” and are defined inparagraph 10.1.

MAS: Military Agency for Standardization

Magic Number: An identifier for the directory block. This identifier is a value chosen to

support discovery of lost directory entries and directory reconstruction after a fault.

Memory Board: Printed circuit board containing flash memory devices used to store user data.

Memory Clear: Rendering stored information unrecoverable unless special utility software ortechniques are used.

Memory Declassification: Administrative decision or procedure to remove or reduce the

security classification of the subject media.

Memory Sanitization: The removal of information from information system media such thatdata recovery using known techniques or analysis is prevented. Sanitizing includes the removal

of data from the media and verification of the action. Properly sanitized media may be

subsequently declassified upon observing the organization's respective verification and reviewprocedures.

MISM: Motion Imagery Standards Matrix.msb: The “most significant bit” of a series of bits.

MSB: The “most significant byte” of a series of bytes.

MSW: The “most significant word” of a series of words.

MSLW: The “most significant long word” of a series of long words.

10-5

7/31/2019 IRIG_106_2009



Multiplexer: The entity that includes all the inputs, control interfaces, and functionalityrequired to properly record data.

NADSI: NATO Advanced Data Storage Interface.

NATO: North Atlantic Treaty Organization

NIIA: NATO Imagery Interoperability Architecture.

Non-volatile: Memory media that retains data when power is removed.

On-Board Recorder: An On-Board Recorder is the basis and original justification for the

IRIG-106 Chapter 10 Standard. On-Board Recorder requirements to be in 100 per centcompliancy with this standard are defined in paragraph 10.3.

Optional: Defines an optional requirement of this standard but is not required for full

compliancy. Optional requirements as defined in this standard are based on the use of “optional”

and are defined in paragraph 10.1. When optional requirements are implemented they shall beIAW with this standard.

Packet: Encapsulates a block of observational and ancillary application data to be recorded.Packet Generation: The placing of observational and ancillary data into a packet.

Packet Generation Time: The time period from when the first bit of observational and

ancillary data was placed into a packet until it is no longer being placed into the packet and thepacket is closed.

Packet Header: Identifies the source and characteristics of the data packet and encapsulation

environment.

Packet Secondary Header: Contains the Packet Header time.

Page: Storage unit within the flash device. A page is the smallest storage unit that can be

written.PATA: Parallel ATA.

PCM: Pulse code modulation

Quad Word: A contiguous set of 64 bits acted on as a unit.

RAID: Redundant Arrays of Independent Drives/ Redundant Arrays of Inexpensive Disks.

RMM: Removable Memory Module.

RR: RT to RT Transfer.

Recorder: Is used where a function or requirement shall apply to both an On-Board Recorder

and a ground based recorder.Recording: Is defined as the time interval from first packet generated (which by mandatory

requirements is a Computer Generated Data Packet Format 1) and committed to the recordermedia to the last packet generated and committed to the recorder media. Packet Generation

Time and Stream Commit Time, as defined within the standard, apply.

Relative Time Counter (RTC): A free-running binary counter common to all data channels.

The counter shall be derived from an internal crystal oscillator and shall remain free-running

10-6

7/31/2019 IRIG_106_2009



during each recording. The applicable data bit to which the 48-bit value applies will be definedin each data type section.

Removable Memory Module (RMM): The element of the On-Board Recorder that contains

the stored data.

SATA:Serial ATA.

SCSI: Small Computer Systems Interface.

Setup Record: TMATS IAW IRIG-106 Chapter 9 annotated in the Computer Generated DataFormat 0 packet.

STANAG: Standardization Agreement, NATO.

Stream: All packets from all enabled channels (including Computer Generated Data) that are

generated until the end of a recording.

Stream Commit Time: The time span in which all Generated Packets must be committed to astream.

TMATS: Telemetry Attributes Transfer Standard as defined in IRIG 106 Chapter 9.

UCS: Universal Multiple-Octet Coded Character Set.

USB: Universal Serial Bus.

Word: A contiguous set of 16 bits acted on as a unit.

10.3 Operational Requirements

10.3.1 Recorder Compliancy Requirements. The following table represents the mandatory

recorder requirements to meet 100 per cent compliancy with this standard. Meeting thesecompliancy requirements guarantees interoperability of recorders, recorder media and recorded

data. Optional functions and/or capabilities are not shown but when implemented in a recorder

shall be in accordance with the definitions in this standard in order to meet 100 per centcompliancy of this standard.

10-7

7/31/2019 IRIG_106_2009


7/31/2019 IRIG_106_2009



10.3.2 Required Configuration. An On-Board Recorder, as a minimum, shall provide thefollowing functionality:

a. Data Download port.

b. Recorder Control/Maintenance port.

c.

External power port.

The required data download port interface shall be IAW paragraph 10.4. This

combination will allow data extraction and transfer from any recorder to any paragraph 10.4

compliant intermediate storage unit. The required control port interface shall be IAWparagraph 10.7.

10.3.3 Exclusions to Standard. The physical size, configuration, and form factor for theOn-Board Recorder and the RMM are not controlled by this standard. Due to the variation in

capacity/rate/cost requirements of the users, this standard does not specify the technology to be

used in the RMM or the On-Board Recorder.

10.3.4 Internal System Management. Any processing performed on the stored data by the

On-Board Recorder (e.g., for the purposes of internal system management, error detection andcorrection (EDAC), physical frame formatting, etc.) shall be removed from the stored data when

the stored data is downloaded or transferred from storage media.

10.3.5 Data Download. On-Board Recorders may have an RMM capability or the On-Board

Recorder can be removed from the acquisition platform and taken to a ground station for data

download. Reference paragraph 10.4.1 for recorder download and electrical interface,paragraph 10.9 for RMM interface, and paragraph 10.11 for data transfer and file management.

10.3.6 IEEE-1394b Interface to Recorder Media. Serial Interface to On-Board Recorder

media shall be accomplished utilizing IEEE-1394b interface. A nine-pin IEEE-1394b interfaceshall be provided on the media to allow direct download of data to host computer or storagedevice.

10.3.7 Required File Tables Entries. Within paragraph 10.5, Table 10-3 “FileSize,” “File

Create Date,” “File Create Time,” and “File Close Time” are either optional or can be empty

(filled with 0x2D) if data is unavailable. Table 10-3 has been adopted from STANAG 4575 butin the case of IRIG-106 Chapter 10 unless the “Time Type” is 0xFF (Time Data Packet) and the

Time Data Packet source is 0xF (None) date and time will always be available.

10.3.7.1 File Table Entry Conditions. If Table 10-2 “Shutdown” value is 0xFF and the “Time

Type” is 0xFF and the Time Data Packet source is not 0xF “FileSize,” “File Create Date,” “FileCreate Time” and “File Close Time” entries shall be filled in their entirety.

If Table 10-2 “Shutdown” value is 0x00 and the “Time Type” is 0xFF and the Time

Data Packet source is not 0xF “FileSize,” “File Create Date,” “File Create Time” and “File CloseTime” entries shall be filled in their entirety.

10-9

7/31/2019 IRIG_106_2009



10.3.8 Recorder Configuration File. A recorder setup configuration file can reside on therecorder or optionally reside in the RMM. Recorder setup configuration must be IAW IRIG-106

Chapter 9. Recorder setup configurations shall be programmed IAW with paragraph 10.7 of this

standard. Optionally the recorder can be configured from a Chapter 10 configuration fileresiding in the RMM. The RMM recorder configuration file will have priority over setup records

residing in the recorder.

10.3.8.1 Recorder Configuration File Location. When a setup record transfer to a recorder is

made via the RMM Computer Generated Data, Format 1 Setup Record packet(s) will be used.

The RMM shall contain a “Directory” and one “Directory Block File Entry” IAWparagraph 10.5.2.

a. All Directory Block Format fields shall be IAW table 10-2. The field “n FileEntries” value shall be 1.

b. All Directory Entry Format fields shall be IAW table 10-3. The field “Time

Type” value shall be 0x01, System Time. The field “Name” value shall be:

recorder_configuration_file_SAVE_n

This will notify the recorder to use the Recorder Configuration Transfer File for the nextrecording and store the setup information contained within the file to non-volatile memory in the

recorder pre-defined setup location n, where n is a value of 0-15. This shall be the equivalent of

sending .TMATS SAVE [n] and .SETUP [n] commands.

10.3.8.2 Recorder Configuration File Structure. The Recorder Configuration File structure

will only contain Computer Generated Data, Format 1 Setup Record packets. More than onepacket is allowed only if the required recorder configuration information exceeds the packet size

limits in paragraph 10.6.1, thus forcing more than one Computer Generated Data, Format 1 Setup

Record packet. The standard method of using the sequence counter will be utilized until all the

configuration information has been packetized.

10.3.8.3 Configuration of Recorder from RMM: A setup record may reside in the RMM and

be utilized for configuration of the recorder. A Computer Generated Data, Format 1 Setup

Record packet(s) will be used. The RMM shall contain a “Directory” and at least one “DirectoryBlock File Entry” IAW paragraph 10.5.2.

a. All Directory Block Format fields shall be IAW table 10-2. The field “n File

Entries” value shall be 1.

b. All Directory Entry Format fields shall be IAW table 10-3. The field “Time

Type” value shall be 0x01, System Time. The field “Name” value shall be…

recorder_configuration_file_SETUP_RMM

This will notify the recorder to configure from the RMM. The recorder configuration file

shall NOT be able to be erased by the recorder .ERASE command or discrete command.

10-10

7/31/2019 IRIG_106_2009



10.3.9 Recorder Data Streaming Transport. Data Streaming Transport may be accomplishedacross the paragraph 10.4 Recorder Download and Electrical Interfaces using the definitions in

paragraph 10.3 and commands in IRIG-106 Chapter 6. For Ground Based Recorders, this will be

accomplished across the required Remote Data Access Ethernet Interface.

10.3.9.1 Ethernet. Ethernet is an optional interface for On-Board Recorders; however, it is arequired interface for Ground-Based Recorders (10.10). IAW paragraph 10.4. This Ethernetinterface can optionally be used for Data Streaming using User Datagram Protocol (UDP). This

will be accomplished with the IRIG-106 Chapter 6 PUBLISH command and the following

structure added to UDP packets with paragraph 10.6 (Data Format) packets.

10.3.9.1.1 Ethernet Packet Payload Byte Order. The byte ordering within the UDP packetpayload shall be IAW paragraph 10.5.3.2. This UDP packet payload shall include the UDP

Transfer Header and the IRIG-106 Chapter 10 data.

10.3.9.1.2 UDP Transfer Header. Network broadcasting limitations of paragraph 10.6 packets

(up to 128M bytes or 512K bytes) across Ethernet will require use of an added packettransmission UDP Transfer Header. This is required as partial packets or partial out of order

packets may be broadcast and will be missing information required for data reconstruction at the

subscriber.

The following structure (Figure 10-2) shall be used for UDP Transfer Headers in

UDP packets containing one or more full IRIG-106 Chapter 10 data packets:

MSW LSW

WORD 1 WORD 0

msb lsb

81 8 7 4 3 0

UDP Message Sequence Number Type of

message

Version

Figure 10-2. UDP Transfer Header for non-segmented data.

The following structure (Figure 10-3) shall be used for UDP Transfer Headers in

UDP packets containing a segmented IRIG-106 Chapter 10 data packet:

10-11

7/31/2019 IRIG_106_2009



MSW LSW

WORD 1 WORD 0

msb lsb

31 8 7 4 3 0

UDP Message Sequence Number Type of message

Version

WORD 3 WORD 2

msb lsb

31 24 23 16 15 0

Reserved Channel Sequence

Number

Channel ID

WORD 5 WORD 4

msb lsb

31 0Segment Offset

Figure 10-3. UDP Transfer Header for segmented data.

Version. (4 bits)

0000: Reserved

0001: Version 10010-1111: Reserved

Type of Message. (4 bits)

0000: Full packets.

0001: Segmented.0010-1111: Reserved.

UDP Message Sequence Number. (24 bits). Binary value incrementing by one

for each UDP message even if segment of IRIG-106 Chapter 10 packet.

Channel ID. (16 bits). Segmented Packets Only, Channel ID of the data in the

IRIG-106 Chapter 10 packet.

Channel Sequence Number. (8 bits). Segmented Packets Only, ChannelSequence Number of the data in the IRIG-106 Chapter 10 packet.

Reserved. (8 bits). Reserved.

Segment Offset. (32 bits). Segmented Packets Only, Position of the data in theIRIG-106 Chapter 10 packet.

10-12

7/31/2019 IRIG_106_2009



10.3.9.1.3 UDP IRIG-106 Chapter 10 Packet Transfer. When more than one complete

Chapter 10 packet is contained within a UDP packet, there shall be an integral number of

Chapter 10 packets. Chapter 10 packets shall be sent in the same sequence as recording segmentof a packet and shall be ordered (segment offset incrementing). Figures 10-4 and 10-5 present

the sequence of the general UDP network broadcast of full or segmented packets. When using IPv4, total length of message shall be less

than 32768 – 42 (IP + UDP header) = 32726.

When using IPv6, the use of jumbograms removes the need of segmented IRIG-106 Chapter 10 packets so a jumbogram shall always contain an integer number

of IRIG-106 Chapter 10 packets.

Stream Commit Time applies to recorders using Ethernet Data Streaming

Transport.

UDP HEADER

UDP TRANSFER HEADERIRIG-106 CHAPTER 10 PACKET 1

:

IRIG-106 CHAPTER 10 PACKET n

Figure 10-4. General UDP Network Broadcast (full packet).

UDP HEADER

UDP TRANSFER HEADER

IRIG-106 CHAPTER 10 PACKET Segment

Figure 10-5. General UDP Network Broadcast (segmented packet).

10.3.10 COTS Media. In conjunction with an On-Board Recorder and/or a multiplexer

when a RMM or internal On-Board Recorder media is not used, COTS media can be used forrecording media. The COTS Media shall be accessible at a minimum from the On-Board

Recorder data download port IAW paragraph 10.4 and optionally by at least one COTS Media

Interface. When accessing COTS Media the Interface File Structure Definition defined inparagraph 10.5 shall be presented at the On-Board Recorder or COTS Media Interface.

10.4 Data Download and Electrical Interface

At a minimum, the required recorder download port interface (see paragraph10.3.2) shall be Fibre Channel or IEEE1394B and optionally Ethernet (paragraph 10.4.3). The

physical, signaling, and command protocols contained in paragraphs 10.4.1 and 10.4.2 are asubset of, and adapted from the North Atlantic Treaty Organization (NATO) Military Agency for

Standardization (MAS) Standardization Agreement (STANAG) NATO Advanced Data StorageInterface (NADSI) Number 4575 (STANAG 4575).

10-13

7/31/2019 IRIG_106_2009


7/31/2019 IRIG_106_2009



TABLE 10-1. “REQUIRED” AND “RECOMMENDED” SCSI COMMANDS,

FEATURES, AND PARAMETERS

FEATURE (COMMAND) INITIATOR TARGET* NOTES

INQUIRY Standard INQUIRY data (bytes 0-35) EVPD = 1 Enable Vital Product Data page codes: 0x00 (supported vital product pages) 0x80 (unit serial number page) 0x81 (implemented operations definition pg) 0x82 (BCS implemented operations def pg) 0x83 (device identification page)

I I I

I I I I I

R R R

R R A A R

READ (10) DPO = 0

DPO = 1 FUA = 0 FUA = 1 RelAdr = 0 RelAdr = 1

I I

I I I R P

R A

A A A R P

1 1 2 2

3

READ CAPACITY RelAdr = 0 RelAdr = 1 PMI = 0 PMI = 1

I R P I I

R R P R A

3

TEST UNIT READY I R

REQUEST SENSE I R

WRITE (10) DPO = 0 DPO = 1 FUA = 0 FUA = 1 RelAdr = 0 RelAdr = 1

C I I I I C P

C A A A A C P

4 1 1 2 2

3

FORMAT UNIT FMT DATA = 0

CMPLST = 0 DEFECT LIST FMT = 0 INTERLEAVE = 0

C I

I I I

C A

A A A

4, 5

10-15

7/31/2019 IRIG_106_2009



TABLE 10-1. “REQUIRED” AND “RECOMMENDED” SCSI COMMANDS,

FEATURES, AND PARAMETERS

NOTES:

1. The Disable Page Out (DPO) bit is associated with a device data caching policy.

2. The Force Unit Access (FUA) bit is associated with whether the device may or may not returnthe requested Read data from its local cache.

3. Relative Offset is prohibited, since this requires the use of linking, which is prohibited.4. All RMMs not supporting Recommended or Allowed commands shall respond to these

commands with an appropriate error response and shall not cease operations.

5. The FORMAT command shall implement an initialization of the target device such that theentire user memory space shall be writable. After performing this command, the content of the

memory may be indeterminate.

*LEGEND

P = Prohibited: The feature shall not be used between NADSI compliant devices.R = Required: The feature or parameter value shall be implemented by NADSI compliant

devices.C = Recommended: The feature is recommended and shall be used for applications requiring thefunctionality of these commands. The initiator determines if a recommended feature/parameter is

supported via a required discovery process or a minimal response by the recipient.

A = Allowed: The feature or parameter may be used between NADSI compliant devices. Theinitiator determines if an Allowed feature/parameter is supported via a required discovery process

or a minimal response by the recipient.

I = Invokable: The feature or parameter may be used between NADSI compliant devices. The

recipient shall support “Invokable” features or provide a response that it is not implemented asdefined by the appropriate standard.

10.4.2 IEEE-1394B Recorder Interface. The IEEE-1394B recorder download interface shall usethe same mechanisms as paragraph 10.9 where applicable.

10.4.2.1 Physical and Signaling. The interface shall allow control of Vendor SpecificRecorder devices. The command protocol shall be IAW 10.4.1.2 and Table 10-1.

10.4.2.2 Recorder Communication. The fundamental method of communicating shall be in

accordance to the IEEE 1394B protocol. Packets sent and received shall be asynchronous

transmissions. IEEE-1394B packets shall encapsulate Serial Bus Protocol (SBP-2) formattedpackets for the transport of commands and data. Recorder devices are to use SCSI command

set(s) and therefore SCSI commands and status shall be encapsulated in SBP-2 Operation

Request Blocks (ORB).

SBP-2 provides for the transport of 6, 10, and 12-byte SCSI Command Descriptor Blocks within a command ORB.

10-16

7/31/2019 IRIG_106_2009



10.4.3 Ethernet Recorder Interface. The On-Board Recorder Ethernet interface shall use iSCSIprotocol. This will allow common SCSI protocols across Fibre Channel, IEEE-1394B (SPB-2)

and Ethernet (iSCSI) recorder download interfaces. The iSCSI protocol will be implemented as

the Host Ground System acting as an initiator and the recorder acting as the target .

Ground Based Recorder Ethernet interface shall use the TELNET protocol. As a

minimum requirement, the TELNET interface will implement Internet Engineering Task Force(IETF) RFC 854 (TELNET Protocol Specification), RFC 855 (TELNET Option Specification),

and RFC 1184 (Line Mode Option). The protocol will support IRIG106 Chapter 6 Commandand Control Mnemonics (Reference 10.7.8) over a TCP/IP connection on port # 10610. The

TELNET interface must respond with a “*” when a connection is made.

10.4.3.1 Target LUN Assignments. The following iSCSI target LUN assignments shall be

used:a. LUN 0 or 32 shall be used for recorder data download via paragraph 10.5

interface.

b. LUN 1 or 33 shall be used for recorder IRIG-106 Chapter 6 Command andControl Mnemonics (Reference 10.7).

10.4.3.2 Naming and Addressing. The Host Ground System (initiator) and Recorder (target)

devices on the network must be named with a unique identifier and assigned an address for

access. The iSCSI initiators and target nodes can either use an iSCSI qualified name (IQN) or anenterprise unique identifier (EUI). Both types of identifiers confer names that are permanent and

globally unique.

Each node has an address consisting of the IP address, the TCP port number, andeither the IQN or EUI name. The IP address can be assigned by using the same methods

commonly employed on networks, such as Dynamic Host Control Protocol (DHCP) or manual

configuration.

10.4.3.3 Physical and Signaling. The interface shall allow control of Vendor Unique Recorderdevices. The command protocol shall be IAW 10.4.1.2 and Table 10-1.

10.4.3.4 Recorder Communication. The fundamental method of communicating shall be inaccordance to the iSCSI protocol. Packets sent and received shall be asynchronous

transmissions.

10.5 Interface File Structure Definitions

The definitions in this paragraph are a subset of, and were adapted from Section 3 of

STANAG 4575, File Structure Definition. This file structure was selected to facilitate hostcomputing platform independence and commonality. By incorporating an independent file

structure, backward and forward compatibility is ensured for the life of the standard.

This file structure definition does not define how data is physically stored

on the recorder media but provides a standardized method for access of thestored data at the interface. Data can be organized in any way appropriate

to the media, including multiple directories, as long as the file structure

IAW paragraph 10.5 is maintained or seen at the interface(paragraph 10.4).

10-17

7/31/2019 IRIG_106_2009



10.5.1 Data Organization. A data recording can contain a single file, which is composed

of one (1) or more types of packetized data, or multiple files, in which one (1) or more types of

data are recorded simultaneously in separate files. For a recording file to be in compliance withthis standard, it must contain as a minimum the following:

a. Computer Generated Packet(s), Setup Record Format 1 IAW paragraph 10.6.7.2 as the first packets in the recording.b. Time Data Packet(s) IAW paragraph 10.6.3 as the first dynamic packet after the

Computer Generated Packet, Setup Record.

c. One (1) or more data format packets IAW paragraph 10.6.

Multiple recordings may reside on the media, and each recording may contain oneor more compliant files.

10.5.1.1 Data Hierarchy. The data hierarchy used to define the data stored according to this

standard shall have the following structural relationships (highest to lowest):

a. Directory. One or more directory blocks of data comprising a list of all DataFiles located under the guidance of this Standard. Also contains supporting datathat may be of interest to those manipulating the Data Files. The list of files is

made up from “File Entries.” The Directory shall always start at logical address

zero of each directory block.b. Directory Block. A memory block containing file entries and other metadata.

c. Directory Block File Entry. A fixed length data structure used to describe files.

It contains the name, the starting address, the number of blocks of data assigned

to the Data File, the total number of bytes contained in the file, and the file’screation date and time. It also contains a reserved field for future growth andfile close time.

d. Data Files. Data files are comprised of user data, presented at the interface inmonotonically increasing contiguous logical addresses per file. Thus if a file

starts at logical address X, the next location containing file data must be at thenext logical address, X+1, and the next location after that must be at the next

logical address, X+2, etc.

10-18

7/31/2019 IRIG_106_2009



Figure 10-6. Directory structure.

10.5.2 Directory Definition. The name and location information for all files recorded is

illustrated in Figure 10-6). The Directory is composed of one or more directory blocks as shown

in Figure 10-7. At least one Directory Block is required and it must be located at SCSI logicalblock address 1. Logical block address 0 is reserved.

DIRECTORY BLOCK

Figure 10-7. Directory block.

a. Directory Fixed Fields. The fixed fields within a directory block are used to

name the volume of data, identify the number of entries, and to provide pointersto other addresses that contain additional directory blocks. Forward and

10-19

7/31/2019 IRIG_106_2009



backward links to the next address for the next Directory Block (if any) or thepreceding Directory Block (if any) allow for directory expansion beyond a

single block. This does not limit the placement of directory information.

b. Block Size. The media types used to implement this standard have varying

block lengths. Some will have blocks as small as 512 bytes; others may have

blocks as large as 64K bytes or larger. The block size used by a given mediacan be determined via the SCSI Read Capacity Command (not defined here).

c. Directory to Data File Link. Each Data File on the media has a directory entry

within a Directory Block that describes the file, as shown in Table 10-2. Thedirectory entry for a Data File, as shown in Table 10-3, contains a link to the

starting location of the data contained in each file and the total number of blocks

assigned for the storage of data. This standard does not define the meaning of the data recorded within these Data File blocks.

TABLE 10-2. DIRECTORY BLOCK FORMAT

FIELD NAME BYTES DESCRIPTIONDATA

TYPE

Magic Number 8 An identifier for a directory block. The value is BCS

“FORTYtwo” (0x464F52545974776F)

BCS

Revision Number 1 Revision number of the standard compiled by the recording

system.

0x01 = IRIG-106-03 thru IRIG-106-05

0x0F = IRIG-106-07

Unsigned

Binary

Shutdown 1 Flag, if cleared to a 0x00 indicates that the volume was not

properly dismounted, if seen on power-up is an indication

that the directory chain may be faulty.

If set = 0xFF, then the file system properly shutdown. This

field is only valid in the first directory located in logicalblock 1; other directory blocks set to 0xFF.

Unsigned

Binary

Number of File

Entries

2 Defines the number of file entries that follow in this block. Unsigned

Binary

Block Size 4 Bytes per block size referenced in FileBlkCnt in

Table-10-3.

Unsigned

Binary

VolName 32 Volume name, see character set for restrictions. (Fill any

unused VolName byte positions with 0x00.)

BCS

Forward Link 8 Block address of the next block containing directory

information. Set equal to address of this block if this is the

end of the chain.

Unsigned

Binary

Reverse Link 8 Block address of the directory block pointing to this block.

Set equal to the address of this block if this is the start of

the chain.

Unsigned

Binary

(n File Entries) 112 *n One entry for each file specified in “Number of File

Entries.” The maximum value of “n” is dependent upon

media block size.

See

Table 10-3

Unused Varies

with n

& block

Size

It is possible for bytes to remain between the last byte of the

last used File Entry and the end of the Directory Block.

These bytes are defined to be Unused and should be filled

with 0xFF.

Unsigned

Binary

Note: 64 Bytes in fixed fields.

10-20

7/31/2019 IRIG_106_2009



TABLE 10-3. FILE ENTRY FORMAT

FIELD NAME BYTES DESCRIPTIONDATA

TYPE

Name 56 File name (see character set for restrictions). Fill any unusedFileName Byte Positions with 0x00. BCS

FileStartAdd 8 Zero based address of the first block reserved for data associated

with this file. Fill with 0xFF for unused directory entries.

Unsigned

Binary

FileBlkCnt 8 One based number that is the count of consecutive address blocks

reserved for data for this file including the block pointed to by the

FileStartAdd field.

Unsigned

Binary

FileSize 8 The actual number of Bytes contained in this file. This file size

will be equal to or less than the FileBlkCnt multiplied by the block

size. This is an optional entry and will be filled with 0xFF if not

used.

Unsigned

Binary

File Create Date 8 DDMMYYYY BCS Character values, with no embedded spaces or

other formatting characters, representing the numeric date onwhich the file was created (e.g., BCS codes for the decimal digits

02092000 0x3032303932303030 represents 2 September 2000).

Fill with 0x2D if a value for the field is not available, or for

portions of the field where data is not available.

BCS

File Create Time 8 HHMMSSss Character values, with no embedded spaces or other

formatting characters, representing the numeric time at which the

file was created. HH is the number of the 24 hour based hour, MM

is the number of minutes after the hour, SS is the number of

seconds after the minute, and ss is the hundredths of seconds after

the second. Fill with 0x2D if a value for the field is not available,

or for portions of the field where data is not available (e.g., “ss” is

not available).

BCS

Time Type 1 A numeric code that qualifies the time and date values recorded inthe “Create Date” and “Create Time” and “Close Time” fields.

0x0 = Coordinated Universal Time (Zulu)

0x1 = System Time

0x2 – 0xFE Reserved

0xFF = Time Data Packet

UnsignedBinary

Reserved 7 Bytes in this region are reserved for future growth. Fill with 0xFF. Unsigned

Binary

File Close Time 8 HHMMSSss Character values, with no embedded spaces or other

formatting characters, representing the numeric time at which the

file was closed. HH is the number of the 24 hour based hour, MM

is the number of minutes after the hour, SS is the number of

seconds after the minute, and ss is the hundredths of seconds after

the second. Fill with 0x2D if a value for the field is not available,

or for portions of the field where data is not available (e.g., “ss” is

not available).

BCS

Note: 112 Bytes in fixed fields.

10-21

7/31/2019 IRIG_106_2009



d. File Entry Name. Each file entry in a directory shall have a unique name (See

Naming Restrictions in paragraph 10.5.3.4). Default file name is a BCSnumeric value incrementally increasing, starting at value “1.”

e. File Entry Singularity. Multiple File entries are not permitted to refer to the

same regions of memory, partially or completely.f. Directory Entries and Fields. Directory block fields and entries shall be

logically contiguous.

g. Directory and Memory Region Relationships. File Entries shall be entered

sequentially into a Directory Block as files are recorded, starting with File Entry

#1 in the Primary Directory Block (logical address 1). All File Entry positionsin the Primary Directory Block shall be filled before the first Secondary

Directory Block is used, and so on. However, there is no a priori relationship

between the memory region associated with a file entry and the place-order of

the file entry within the overall directory. For example, the very first file entrycould refer to the very last logical address region of memory, the second file

entry could refer to the beginning logical address of memory, and so on.

Similarly, there is no presumed temporal ordering of file entries; the very lastentry to be inserted could be inserted in such a fashion so as to be the first entry

encountered when traversing the directory chain of blocks.

h. Empty Memory Reads. Reads of regions of memory not containing Directory

Blocks or Data File blocks may return unpredictable data values or result inother error conditions.

i. Contiguous Directory Entries. File entries and all fields in a directory block are

contiguous.

Deleted Files are not applicable to IRIG-106 Chapter 10 as there are norecorder commands that allow or provide file deletion.

j. Deleted Files. In some applications, previously recorded files may be deleted in

order to recover media space for new recordings. Deleted files shall be denoted

by marking the corresponding file entry’s File Block Count field with 0x00

indicating “unused.” If the file block count has been set to 0x00, then otherfields in that file entry are no longer meaningful.

k. Reserved Field. Reserved fields shall not be used in IRIG-106 Chapter 10 implementations and shall be filled with 0xFF. Reserved fields are intended for

future IRIG-106 Chapter 10 use.

l. Number of File Entries. The numerical value placed in the “Number of File

Entries” field of a Directory Block shall equal the number of active File Entriesplus any File Entries marked as deleted files within that Directory Block.

10-22

7/31/2019 IRIG_106_2009



10.5.3 Data Definitions.

10.5.3.1 Directory Byte Order. The directory structures described in paragraph 10.5 of thisstandard are defined to have the following bit and byte orientation. The most significant byte of

any multi-byte structure is byte 0. The most significant bit of each byte is bit 0. This ordering is

commonly referred to as “Big Endian.”

10.5.3.2 Data Format Byte Order. The data format structures (Packet Header, SecondaryPacket Header, Channel Specific Data Word, Intra-Packet Header, and Packet Trailer) described

in paragraph 10.6 of this standard are defined to have the following bit and byte orientation. The

least significant byte shall be transmitted first, the least significant bit of each byte shall betransmitted first, and data is read from the lowest logical address first. This ordering is

commonly referred to as “Little Endian.” The Packet data shall remain in its native byte order

format.

10.5.3.3 Character Set. The character set for all character fields is based on ISO/IEC10646-1, the Universal Multiple-Octet Coded Character Set (UCS). The NIIA limits characters

to a subset rather than allowing all characters. The subset will be single octets, known as the

Basic Character Set (BCS).

10.5.3.4 Naming Restrictions. The following rules shall be applied when forming names inorder to assure the highest degree of interchange among other operating systems:

a. Characters. Characters from the first 127 common BCS characters

(0x00 through 0x7E) may be used in names except for specific prohibited

characters:

1) Any BCS character code value smaller than 0x20 is prohibited, except wherethe 0x00 is used to terminate the name.

2) The other prohibited characters with their hexadecimal representation are

defined in Table 10-4.

TABLE 10-4. PROHIBITED CHARACTERS

(HEXADECIMAL REPRESENTATION)

Forbidden

Characters In

Names

Hexadecimal

Value

Forbidden

Characters In NamesHexadecimal Value

” 0x22 = 0x3D

‘ 0x27 > 0x3E

* 0x2A ? 0x3F

/ 0x2F \ 0x5C

: 0x3A ] 0x5D

; 0x3B [ 0x5B

< 0x3C | 0x7C

b. Names. Names used for this interface will observe the following rules:

(1) Upper and lowercase characters are considered to be different within filenames.

10-23

7/31/2019 IRIG_106_2009



(2) Leading and trailing spaces are not permitted.

(3) Leading periods are not permitted.

(4) Names shall fill their field starting with byte 0 per paragraph 10.5.3.1 and

be terminated with a 0x00. Unused Name characters shall be filled with

0x00. Names may utilize the full length of the field, in which case theterminating 0x00 must be omitted. Examples of host provided and defaultfile names are shown in Table 10-5.

TABLE 10-5. FILE NAME EXAMPLES

10.6 Data Format Definition

10.6.1 Common Packet Elements. Data shall have three required parts, a Packet Header,

a Packet Body, a Packet Trailer, and an optional part if enabled, a Packet Secondary Header.Single or multiple channel recordings will always conform to the structure outlined in

Figure 10-8.

a. A packet has the basic structure shown in Figure 10-9. Note that the width of

the structure is not related to any number of bytes or bits. This table is merely

to represent relative packet elements and their placement within the packet. See

Figure 10-10 for a diagram of the generic packet format. This figure does notdepict the bit lengths of each field. Word sizes of 8 bits, 16 bits, and 32 bits are

used depending on the data type.

To further clarify the packet layout, Figure 10-10 shows the generic packet

in a 32-bit, Little-endian format, and assumes 16-bit data words and data

checksum.

10-24

7/31/2019 IRIG_106_2009



Figure 10-8. Data recording structure.

10-25

7/31/2019 IRIG_106_2009



PACKET SYNC PATTERN

CHANNEL ID

PACKET LENGTH

DATA LENGTH

DATA TYPE VERSION Packet HeaderSEQUENCE NUMBER

PACKET FLAGS

DATA TYPE

RELATIVE TIME COUNTER

HEADER CHECKSUM

TIME Packet

RESERVED Secondary Header

SECONDARY HEADER CHECKSUM (Optional)

CHANNEL SPECIFIC DATA

INTRA-PACKET TIME STAMP 1

INTRA-PACKET DATA HEADER 1DATA 1 Packet Body

:

INTRA-PACKET TIME STAMP n

INTRA-PACKET DATA HEADER n

DATA n

DATA CHECKSUM Packet Trailer

Figure 10-9. General packet format.

10-26

7/31/2019 IRIG_106_2009



msb lsb

31 16 15 0

CHANNEL ID PACKET SYNC PATTERN

PACKET LENGTH

DATA LENGTH

DATA TYPEPACKET

FLAGS

SEQUENCE

NUMBER

DATA TYPE

VERSIONPacket Header

RELATIVE TIME COUNTER

HEADER CHECKSUM RELATIVE TIME COUNTER

TIME (LSLW) (Optional)

TIME (MSLW) Packet

SECONDARY HEADERCHECKSUM

RESERVEDSecondary

Header



INTRA-PACKET TIME STAMP 1INTRA-PACKET DATA HEADER 1

DATA 1 WORD 2 DATA 1 WORD 1

DATA 1 WORD n :



INTRA-PACKET DATA HEADER 2

DATA 2 WORD 2 DATA 2 WORD 1 Packet

DATA 2 WORD n : Body

:

INTRA-PACKET TIME STAMP N

INTRA-PACKET TIME STAMP N

INTRA-PACKET DATA HEADER N

DATA N WORD 2 DATA N WORD 1

DATA N WORD n :

[FILLER]

DATA CHECKSUMPacket Trailer

Figure 10-10. A 32-bit packet format layout.

10-27

7/31/2019 IRIG_106_2009



Depending on the data type, the size of the Data Checksum can contain 16 bits, 32 bits, 8 bits, orthe checksum can be entirely left out. For a 32-bit Data Checksum, the packet trailer would be

as shown in Figure 10-11.

msb lsb

7 0[ FILLER ]

DATA CHECKSUM (LSB)

DATA CHECKSUM Packet Trailer

DATA CHECKSUM

DATA CHECKSUM (MSB)

Figure 10-11. Packet trailer for 32-bit data checksum.

b. For an 8-bit Data Checksum, the packet trailer would be as shown in

Figure 10-12.

msb lsb7 0

[ FILLER ]

DATA CHECKSUM

Packet Trailer

Figure 10-12. Packet trailer for 8-bit data checksum.

c. The size of a single Packet may be a maximum of 524,288 bytes as shown in

Table 10-6. This includes the Packet Header, Packet Body, Packet Trailer, andoptional Packet Secondary Header if enabled. The only exception to the packet

size limit is the Computer Generated Data Packet, Format 1 Setup Record,

which may be a maximum of 134,217,728 bytes. Any Packet that requires more

than 524,288 bytes may generate multiple packets by utilizing the packetsequence counter. Some packet types allow a single data set to span multiple

packets if the data set size or time does not fall under packet maximums. Thespecific mechanism allowing packet data spanning for each data type is

described within that data type’s section.

d. With the exception of Computer Generated Packets, all other Packet Generation

Times shall be equal to or less than 100 milliseconds as measured by the 10MHz Relative Time Counter whenever data is available. This requirement

ensures that a packet shall contain equal to or less than 100 milliseconds worth

of data, and that a packet containing any data must be generated equal to or less

than 100 milliseconds from the time the first data was placed in the packet.

This strategy will assure packet granularity and save bandwidth by not forcingor marking empty/idle packets.

e. Packets can not contain only filler or can not be idle or empty. All packets that

are generated shall contain data.

f. All reserved bit-fields in packet headers or channel specific data words shall be

set to zero (0x0).

10-28

7/31/2019 IRIG_106_2009



g. With the exception of Computer Generated Data Packets, all other packets shallhave a Stream Commit Time equal to or less than 1,000 milliseconds as

measured by the 10 MHz Relative Time Counter contained in the packet header.

h. Once version bits and packet structure bits have been used to indicate a value or

setting for each data type and its associated channel, they shall not change for

that data type and its associated channel within the recording.

TABLE 10-6. PACKET REQUIREMENTS

PACKET TYPE REQUIREDMAXIMUM

PACKET SIZE

REQUIRED PACKET

LOCATION

Computer Generated Data

Packet, Format 1 Setup

Record

Yes 134,217,728

bytes

First Packets in

Recording. A single setup

record may span across

multiple ComputerGenerated Data Packets,

Format 1 Setup Record.

Time Data Packet Yes 524,288 bytes First Dynamic Data Packet

Following Setup Record

Packet(s). Reference theTime Data Packet

Description for packet

rate.

All other data type packets

with the exception of

Computer Generated DataPacket, Format 1 Setup

Record, Time Data Packets,and Computer Generated

Data Packet, Format 3

Recording Index (RootIndex)

No 524,288 bytes After First Time Data

Packet and before the last

Computer Generated DataPacket Format 3,

Recording Index (RootIndex) if enabled.

Computer Generated DataPacket, Format 3 Recording

Index (Root Index)

Yes, if Recording

Events are

Enabled.No, if

Recording

Events are

Disabled.

524,288 bytes If Recording IndexPackets are enabled, Root

Index Packet Type will be

the last packet in arecording.

10-29

7/31/2019 IRIG_106_2009



10.6.1.1 Packet Header. The length of the packet header is fixed at 24 bytes (192 bits). ThePacket Header is mandatory and shall consist of ten fields, positioned contiguously, in the

following sequence:

a. Packet Sync Pattern. (2 Bytes) contains a static sync value for the every packet.

The Packet Sync Pattern value shall be 0xEB25.b. Channel ID. (2 Bytes) contains a value representing the Packet Channel ID.All channels in a system must have a unique Channel ID for each data source.

(1) Multiplexer Source ID. In a distributed Multiplexer system, a Multiplexer

Source ID is used to discern each multiplexer in the system. The Setup Record

shall contain a “Number of Source Bits” recorder attribute (R-x\NSB) to specifythe number of most significant bits (from the Channel ID) that distinguish the

Multiplexer Source ID. The remaining least significant bits of the Channel ID

field shall be the Channel ID for each data source acquired by the multiplexer.(2) Reserved Channel ID. Channel ID 0x0000 is reserved, and is used to insert

computer-generated messages into the composite data stream.

(3) Available Channel IDs. All values not comprising the reserved Channel IDare available.

For single multiplexer systems: the reserved Channel ID is 0x0000;

values 0x0001 thru 0xFFFF are available Channel IDs; Computer Generated

Data Packets shall only have a Channel ID of 0x0000; and no other data typecan have a Channel ID of 0x0000.

c. Packet Length. (4 Bytes) contains a value representing the length of the entire

packet. The value shall be in bytes and is always a multiple of four (bit 1 andbit 0 shall always be zero). This Packet Length includes the Packet Header,

Packet Secondary Header (if enabled), Channel Specific Data, Intra-Packet

Headers, Data, Filler, and Data Checksum.

d. Data Length. (4 Bytes) contains a value representing the valid data lengthwithin the packet. This value shall be represented in bytes. Valid data length

includes Channel Specific Data, Intra-Packet Data Headers, Intra-Packet Time

Stamp(s), and Data but does not include Packet Trailer Filler and DataChecksum.

e. Data Type Version. (1 Byte) contains a value at or below the release version of

standard applied to the data types in table 10-7. The value shall be representedby the following bit patterns:

0x00 = Reserved

0x01 = Initial Release (IRIG-106-04)0x02 = IRIG-106-05

0x03 = IRIG-106-07

0x04 = IRIG-106-090x05 thru 0xFF = Reserved

10-30

7/31/2019 IRIG_106_2009



f. Sequence Number. (1 Byte) contains a value representing the packet sequencenumber for each Channel ID. This is simply a counter that increments by

n + 0x01 to 0xFF for every packet transferred from a particular channel and is

not required to start at 0x00 for the first occurrence of a packet for theChannel ID.

Sequence number counter value for each channel in a recording will repeat

(rollover to 0x00) after the sequence number counter has reached 0xFF.

Each Channel in a Recording shall have its own sequence counterproviding a unique Sequence Number for that channel.

g. Packet Flags. (1 Byte) contains bits representing information on the content andformat of the packet(s).

Bit 7: Indicates the presence or absence of the Packet Secondary Header.

0 = Packet Secondary Header is not present.1 = Packet Secondary Header is present.

Bit 6: Indicates the Intra-Packet Time Stamp Time Source.0 = Packet Header 48-bit Relative Time Counter.

1 = Packet Secondary Header Time (bit 7 must be 1).

Bit 5: Relative Time Counter Sync Error.

0 = No Relative Time Counter sync error.

1 = Relative Time Counter sync error has occurred.

Bit 4: Indicates the Data Overflow Error.

0 = No data overflow.

1 = Data overflow has occurred.

Bits 3-2: Indicate the Packet Secondary Header Time Format.

00 = IRIG 106 Chapter 4 binary weighted 48-bit time format. The

two LSBs of the 64-bit Packet Secondary Header Time andIntra-Packet Time Stamp shall be zero filled.

01 = IEEE-1588 Time format. The Packet Secondary Header Timeand each Intra-Packet Time Stamp shall contain a 64-bit

timestamp represented in accordance with the Time

Representation type as specified by IEEE STD 1588-2002. The

32 bits indicating seconds shall be placed into the MostSignificant Long Word portion of the secondary header and the

10-31

7/31/2019 IRIG_106_2009



32 bits indicating nanoseconds shall be placed into the LeastSignificant Long Word portion.

10 = Reserved

11 = Reserved

Bits 1-0: Indicate Data Checksum existence.00 = No data checksum present01 = 8-bit data checksum present

10 = 16-bit data checksum present

11 = 32-bit data checksum present

h. Data Type. (1 Byte) contains a value representing the type and format of the

data. All values not used to define a data type are reserved for future data type

growth.

TABLE 10-7. DATA TYPE NAMES AND DESCRIPTIONS

PACKET

HEADER

VALUE DATA TYPE NAME

DATA TYPE

DESCRIPTION

CURRENT

DATA

TYPE

VERSION

0x00 Computer Generated Data, Format 0 (User Defined) 0x02

0x01 Computer Generated Data, Format 1 (Setup Record) 0x03

0x02 Computer Generated Data, Format 2 (Recording Events) 0x03

0x03 Computer Generated Data, Format 3 (Recording Index) 0x03

0x04 – 0x07 Computer Generated Data, Format 4

Format 7 (Reserved for future use)

0x02

0x08 PCM Data, Format 0 (Reserved for future use) 0x02

0x09 PCM Data, Format 1 (IRIG 106 Chapter 4/8) 0x03

0x0A – 0x0F PCM Data, Format 2 – Format 7 (Reserved for future use) 0x02

0x10 Time Data, Format 0 (Reserved for future use) 0x02

0x11 Time Data, Format 1 (IRIG/GPS/RTC) 0x03

0x12 – 0x17 Time Data, Format 2 – Format 7 (Reserved for future use) 0x02

0x18 MIL-STD-1553 Data, Format 0 (Reserved for future use) 0x02

0x19 MIL-STD-1553 Data, Format 1 (Mil-Std-1553B Data) 0x03

0x1A MIL-STD-1553 Data, Format 2 (16PP194 Bus) 0x03

0x1B – 0x1F MIL-STD-1553 Data,

Format 3 – Format 7 (Reserved for future use)

0x03

0x20 Analog Data, Format 0 (Reserved for future use) 0x02

0x21 Analog Data, Format 1 (Analog Data) 0x02

0x22 – 0x27 Analog Data, Format 2 – Format 7 (Reserved for future use) 0x02

0x28 Discrete Data, Format 0 (Reserved for future use) 0x02

0x29 Discrete Data, Format 1 (Discrete Data) 0x02

0x2A – 0x2F Discrete Data, Format 2 – Format 7 (Reserved for future use) 0x02

10-32

7/31/2019 IRIG_106_2009



TABLE 10-7. DATA TYPE NAMES AND DESCRIPTIONS

PACKET

HEADER

VALUE

DATA TYPE NAME DATA TYPE

DESCRIPTION

CURRENT

DATA

TYPE

VERSION 0x30 Message Data, Format 0 (Generic Message Data) 0x02

0x31 – 0x37 Message Data, Format 1 – Format 7 (Reserved for future use) 0x02

0x38 ARINC 429 Data, Format 0 (ARINC429 Data) 0x02

0x39– 0x3F ARINC 429 Data, Format 1 – Format 7 (Reserved for future use) 0x02

0x40 Video Data, Format 0 (MPEG-2/H.264 Video) 0x04

0x41 Video Data, Format 1 (ISO 13818-1 MPEG-2) 0x02

0x42 Video Data, Format 2 (ISO 14496 MPEG-4

Part10) 110 AVC/H.264) 0x03

0x43 – 0x47 Video Data, Format 3 – Format 7 (Reserved for future use) 0x03

0x48

Image Data, Format 0

(Image Data)

0x02

0x49 Image Data, Format 1 (Still Imagery) 0x03

0x4A – 0x4F Image Data, Format 2 – Format 7 (Reserved for future use) 0x03

0x50 UART Data, Format 0 (UART Data) 0x03

0x51 – 0x57 UART Data, Format 1 – Format 7 (Reserved for future use) 0x02

0x58 IEEE-1394 Data, Format 0 (IEEE-1394 Transaction) 0x02

0x59 IEEE-1394 Data, Format 1 (IEEE-1394 PhysicalLayer)

0x03

0x5A – 0x5F IEEE-1394 Data, Format 2 – Format 7 (Reserved for future use) 0x03

0x60 Parallel Data, Format 0 (Parallel Data) 0x02

0x61 – 0x67 Parallel Data, Format 1 – Format 7 (Reserved for future use) 0x02

0x68 Ethernet Data, Format 0 (Ethernet Data) 0x03 0x69 – 0x6F Ethernet Data, Format 1 – Format 7 (Reserved for future use) 0x03

i. Relative Time Counter. (6 Bytes) contains a value representing the 10 MHz

Relative Time Counter (RTC). This is a free-running 10 MHz binary counter

represented by 48 bits which are common to all data channels. The countershall be derived from a 10 MHz internal crystal oscillator and shall remain free-

running during each recording.

Note: The applicable data bit to which the 48-bit value applies shall correspond

to the first bit of the data in the packet body (unless it is defined in each data

type section).

j. Header Checksum. (2 Bytes) contains a value representing a 16-bit arithmetic

sum of all 16-bit words in the header excluding the Header Checksum Word.

10-33

7/31/2019 IRIG_106_2009



10.6.1.2 Packet Secondary Header (Optional). The length of the Packet Secondary Headeris fixed at 12 bytes (96 bits). The Packet Secondary Header is optional and when enabled shall

consist of the three fields, positioned contiguously, in the following sequence:

a. Time. (8 Bytes) contain the value representing Time in the format indicated by

bits 2 and 3 of the Packet Flags in paragraph 10.6.1.1g.b. Reserved. (2 Bytes) are reserved and shall be zero filled.c. Secondary Header Checksum. (2 Bytes) contain a value representing a 16-bit

arithmetic sum of all Secondary Header bytes excluding the Secondary Header

Checksum Word.

10.6.1.3 Packet Body. The format of the data in the packet body is unique to each data type.

Detailed descriptions of the type-specific data formats found in packet bodies are described in

subsequent sections of this document.

a. Channel Specific Data. (Variable Bytes) contains the contents of the ChannelSpecific Data field(s) depending on the Data Type field in the Packet Header.

Channel Specific Data is mandatory for each data type and channel. Theoccurrence of Channel Specific Data is once per packet and precedes packetchannel data.

b. Intra-Packet Time Stamp. (8 Bytes) contains Time in either 48-bit Relative

Time Counter format (plus 16 high-order zero bits) or 64-bit absolute format as

specified in the Packet Flags in the Packet Header. The Intra-Packet TimeStamps are only mandatory where defined by the data formats.

c. Intra-Packet Data Header. (Variable Bytes) contains additional status and

format information pertaining to the data items that follow. The Intra-packet

Data Headers are only mandatory where defined by the data formats.

d. Data. (n Bytes) contains valid data from a particular channel as defined withinthe data formats contained within this standard.

The Intra-Packet Time Stamp and the Intra-Packet Data Header are

collectively called the Intra-Packet Header. In some cases, an Intra-Packet

Header may only have a Time Stamp (zero-length Data Header), while inother cases, the Intra-Packet Header only has a Data Header (zero-length

Time Stamp). Some data types have no Intra-Packet Header. The Intra-

Packet Header requirements are specified separately for each Data Type.

The Intra-Packet Data Header (IPDH) presence, once set, shall be the samestate for the entire recording per each channel

10-34

7/31/2019 IRIG_106_2009



10.6.1.4 Packet Trailer. The packet trailer may contain filler, a data checksum, both fillerand a data checksum, or neither filler nor a data checksum. In the latter case, the packet trailer

has zero length. The reason a packet trailer would have a zero length is best explained by

understanding the reason for inserting filler. The purpose of the filler is twofold:

a. To keep all packets aligned on 32-bit boundaries (i.e., make all packet lengths amultiple of 4 bytes), andb. To optionally keep all packets from a particular channel the same length.

If both of the above requirements are already met without adding filler, then filler shall

not be added.

The inclusion of the data checksum is optional as well and is indicated by the Packet

Flags setting. When included, the packet trailer contains either an 8-bit, 16-bit, or 32-bit DataChecksum. Depending on the Packet Flags option selected, the Data Checksum is the arithmetic

sum of all of the bytes (8 bits), words (16 bits), or long words (32 bits) in the packet excluding

the 24 bytes of Packet Header, Packet Secondary Header (if enabled) and the Data Checksum.Stated another way, the Data Checksum includes everything in the packet body plus all added

filler.

a. Filler. (variable Bytes) All filler shall be set to 0x00 or 0xFF.

b. 8-Bit Data Checksum. (1 Byte) contains a value representing an 8-bit arithmetic

sum of the bytes in the packet. Only inserted if Packet Flag bits are set (seeparagraph 10.6.1.1.g).

c. 16-Bit Data Checksum. (2 Bytes) contains a value representing a 16-bit

arithmetic sum of the words in the packet. Only inserted if Packet Flag bits are

set (paragraph 10.6.1.1.g).

d. 32-Bit Data Checksum. (4 Bytes) contains a value representing a 32-bitarithmetic sum of the long words in the packet and is only inserted if Packet

Flag bits are set (paragraph 10.6.1.1.g).

10.6.2 PCM Data Packets.

10.6.2.1 PCM Data Packets Format 0. Reserved.

10.6.2.2 PCM Data Packets Format 1 (IRIG 106 Chapter 4 and 8). A packet with IRIG-106

Chapter 4 or IRIG-106 Chapter 8 PCM data has the basic structure as shown in Figure 10-13.

Note that the width of the structure is not related to any number of bits. This table merely

represents relative placement of data in the packet.

10-35

7/31/2019 IRIG_106_2009



PACKET HEADER


(Optional) INTRA-PACKET TIME STAMP

(Optional) INTRA-PACKET DATA HEADER

MINOR FRAME DATA



MINOR FRAME DATA



MINOR FRAME DATA


(Optional) INTRA-PACKET DATA HEADERMINOR FRAME DATA

:



MINOR FRAME DATA

PACKET TRAILER

Figure 10-13. General PCM data packet, format 1.

The user may separately enable or disable word unpacking on each active PCM channel.

Word unpacking will force the least significant bit of each word to be aligned on a 16-bitboundary. High-order filler bits are added to words as necessary to force alignment.

The user may separately enable or disable frame synchronizing on each active PCMchannel. This provides a “Throughput Mode” that will transfer data to the packet without frame

synchronization. Throughput Mode essentially disables all setup and packing/unpacking options

for the packet, and places data in the packet as it is received.

a. PCM Packet Channel Specific Data. The packet body portion of each PCMpacket begins with the channel specific data, which is formatted as shown in

Figure 10-14.

msb lsb

31 30 29 28 27 24 23 18 17 0

R IPH MA MI LOCKST MODE SYNCOFFSET

Figure 10-14. PCM packet channel specific data format.

10-36

7/31/2019 IRIG_106_2009



Reserved. (bit 31) is reserved.

Intra-Packet Header (IPH). (bit 30) indicates if Intra-Packet Headers

(Intra-Packet Time Stamp and Intra-Packet Data Header) are inserted before

each minor frame. Intra-Packet Headers are only optional because of themode selection. This determines whether Intra-Packet Headers are included

or omitted.0 = Intra-Packet Headers are omitted for Throughput Mode.

1 = Intra-Packet Headers are required for Packed Data and Unpacked Datamodes.

Major Frame Indicator (MA). (bit 29) indicates if the first word in thepacket is the beginning of a major frame. Not valid for Throughput Mode.

0 = First word is not the beginning of a major frame.1 = First word is the beginning of a major frame.

Minor Frame Indicator (MI). (bit 28) indicates if the first word in the packetis the beginning of a minor frame. Not valid for Throughput Mode.

0 = First word is not the beginning of a minor frame.1 = First word is the beginning of a minor frame.

Lock Status (LOCKST). (bits 27-24) indicates the lock status of the framesynchronizer. Not valid for Throughput Mode.

Minor Frame Definition. The minor frame is defined as the data

structure in time sequence from the beginning of a minor frame

synchronization pattern to the beginning of the next minor framesynchronization pattern. Please reference IRIG-106 Chapter 4,

paragraph 4.3.2 for minor/major frame definition.

Bits 27-26: Indicate Minor Frame Status.

00 = Reserved.01 = Reserved.

10 = Minor Frame Check (after losing Lock).

11 = Minor Frame Lock.

Bits 25-24: Indicate Major Frame Status.00 = Major Frame Not Locked.01 = Reserved.

10 = Major Frame Check (after losing Lock).

11 = Major Frame Lock.

Mode (MODE). (bits 23-18) indicates the data packing mode.

Bits 23-22: Reserved.

Bit 21: Alignment Mode.

0 = 16 Bit Alignment Mode enabled.

1 = 32 Bit Alignment Mode enabled.

10-37

7/31/2019 IRIG_106_2009



Bit 20: Indicates Throughput Data Mode.0 = Throughput Data Mode not enabled.

1 = Throughput Data Mode enabled.

Bit 19: Indicates Packed Data Mode.

0 = Packed Data Mode not enabled.

1 = Packed Data Mode enabled.

Bit 18: Indicates Unpacked Data Mode.

0 = Unpacked Data Mode not enabled.

1 = Unpacked Data Mode enabled.

Sync Offset (SYNCOFFSET). (bits 17-0) contains an 18-bit binary valuerepresenting the Word offset into the major frame for the first data word in

the packet. Not valid for Packed or Throughput Mode.

b. PCM Packet Body. After the Channel Specific Data, the Intra-Packet Headers

and the PCM data are inserted in the packet in integral numbers of minor or

major frames, unless the packet is in Throughput Mode. In Throughput Mode,there is no frame or word alignment to the packet data and no Intra-PacketHeaders are inserted in the data. In both Packed and Unpacked Modes, minor

frame alignment is dependent on the MODE field in the Channel Specific Data.

In 16 Bit Alignment Mode, PCM minor frames begin and end on 16-bitboundaries. In 32 Bit Alignment Mode, PCM minor frames begin and end on

32-bit boundaries. In either case, Alignment Mode does not affect the format of

PCM data words themselves. However, depending on perspective, word orderis affected and a zero-filled data word may be required to maintain alignment.

c. PCM Data in Unpacked Mode. In Unpacked Mode, packing is disabled and

each data word is padded with the number of filler bits necessary to align the

first bit of each word with the next 16-bit boundary in the packet. For example,4 pad bits are added to 12-bit words, 6 pad bits are added to 10-bit words, etc.

In 32 Bit Alignment Mode, a zero-filled 16-bit word is required to maintain

alignment when an odd number of 16-bit words exist in the minor frame.

Minor frame sync patterns larger than 16 bits are divided into two words

of packet data. If the sync pattern has an even number of bits, then it will be

divided in half and placed in two packet words. For example, a 24-bit syncpattern is broken into two (2) 12-bit words with 4 bits of pad in each word. If

the sync pattern has an odd number of bits, it is broken into two (2) words with

the second word having one-bit more of the sync pattern. For example, if the

minor sync pattern is 25 bits, then the first sync word is 12 bits of sync patternplus 4 bits of pad, and the second sync word is 13 bits of sync pattern plus 3 bits

of pad.

Minor frame sync patterns larger than 32 bits are divided into

(Number of bits+15) / 16 words in 16 Bit Alignment Mode, or

(Number of bits+31) / 32 in 32 Bit Alignment Mode. If the sync word doesn’tfill the words completely, the first word shall contain the lesser number of bits

10-38

7/31/2019 IRIG_106_2009



with the later words containing one bit more (in the manner described above insplitting frame sync pattern words into two words). For example, a 35-bit sync

word shall be split into 11+12+12-bit words in 16 Bit Alignment Mode, or

into 17+18-bit words in 32 Bit Alignment Mode.

Given PCM frames with a 24-bit minor sync pattern and n data wordswhere the bit-lengths of data words 1, 2, and 3 are 12, 16, and 8 respectively,the resultant PCM packets are as shown in Figure 10-15.

d. PCM Data in Packed Mode. In Packed Mode, packing is enabled and pad is not

added to each data word. However, filler bits may be required to maintain

minor frame alignment. The number of filler bits is dependent on theAlignment Mode, where N is either 16 or 32. If the number of bits in the minor

frame is not an integer multiple of N, then Y PAD bits will be added to the end

of each minor frame of bit-length L. Either Y = N – MOD(L,N), or N minus

the integer remainder when L is divided by N. In packed mode, the PCMstream is minor frame synchronized so the first data bit in the packet is the first

data bit of a minor frame. If X = N – Y when N is 32 Bit Alignment Mode, thenthe resultant PCM packets are as shown in Figure 10-16.

10-39

7/31/2019 IRIG_106_2009



msb lsb

15 0

PACKET HEADER

CHANNEL SPECIFIC DATA (BITS 15-0)

CHANNEL SPECIFIC DATA (BITS 31-16)INTRA-PACKET TIME STAMP (BITS 15-0)

INTRA-PACKET TIME STAMP (BITS 31-16)



INTRA-PACKET DATA HEADER (BITS 15-0)


(32 Bit Alignment Mode ONLY)

4-BITS PAD 12-BITS SYNC (BITS 23-12)

4-BITS PAD 12-BITS SYNC (BITS 11-0)

4-BITS PAD 12-BITS WORD 1 DATA

16-BITS WORD 2 DATA8-BITS PAD 8-BITS WORD 3 DATA

:

WORD n DATA BITS + PAD IF NEEDED

ZERO FILLED PAD WORD IF NEEDED

(32 Bit Alignment Mode ONLY)

INTRA-PACKET TIME STAMP ( BITS 15-0)




INTRA-PACKET DATA HEADER ( BITS 15-0)


:

REPEAT FOR EACH MINOR FRAME

:

PACKET TRAILER

Figure 10-15. PCM Data – unpacked mode sample packet.

10-40

7/31/2019 IRIG_106_2009



msb lsb

15 0

PACKET HEADER


CHANNEL SPECIFIC DATA (BITS 31-16)INTRA-PACKET TIME STAMP ( BITS 15-0)





DATA (BITS 15 – 0)



:

Y FILLER BITS

Y FILLER BITS X DATA BITSINTRA-PACKET TIME STAMP ( BITS 15-0)





:

REPEAT FOR EACH MINOR FRAME

:

PACKET TRAILER

Figure 10-16. PCM Data – packed mode sample packet.

e. PCM Data in Throughput Mode. In Throughput Mode, the PCM data are not

frame synchronized so the first data bit in the packet can be any bit in the majorframe. The resultant PCM packets are as shown in Figure 10-17. Only bit 20 of

the Channel Specific Data word is set to one (1), indicating Throughput Mode.

All other bits of the Channel Specific Data word are undefined and shall be set

to zero (0).

msb lsb

15 0

PACKET HEADER

CHANNEL SPECIFIC DATA (BITS 15-0)CHANNEL SPECIFIC DATA (BITS 31-16)




:

PACKET TRAILER

Figure 10-17. PCM Data – Throughput Mode sample packet.

10-41

7/31/2019 IRIG_106_2009



f. PCM Data Word Order in 32 Bit Alignment Mode. When recording in 32 Bit

Alignment Mode, the resultant data word ordering will differ from 16 Bit

Alignment Mode. The serial PCM data stream is shifted into 32-bit words fromright to left, with bit 31 on the left, bit 0 on the right, and addresses ascending

from top to bottom. Word order is affected depending on the reader’saddressing perspective. For example, 16-bit data words when addressed as32-bit words appear in order when read from left to right, and top to bottom.

However, when addressed as 16-bit words, each pair of data words will appear

swapped. Figure 10-18 and Figure 10-19 depict the anomaly of perspective.

msb lsb addr31 16 15 0

byte 3 byte 2 byte 1 byte 0

DATA WORD 1 DATA WORD 2 0

DATA WORD 3 DATA WORD 4 1

:DATA WORD N-1 DATA WORD N N/2-1

Figure 10-18. 32-bit Alignment Mode example, 16-bit data words

(32-bit word addressing).

msb lsb addr

15 0

byte 1 byte 0

DATA WORD 2 0

DATA WORD 1 1

DATA WORD 4 2

DATA WORD 3 3: :

DATA WORD N-1 N-1

Figure 10-19. 32-bit Alignment Mode example, 16-bit data words

(16-bit word addressing).

g. PCM Intra-Packet Header. When recording in Packed or Unpacked mode, allPCM minor frames shall include an Intra-Packet Header containing a 64-bit

Intra-Packet Time Stamp and a 16 or 32-bit Intra-Packet Data Header, as

indicated by MODE in the Channel Specific Data. This header is insertedimmediately before the minor frame sync pattern. Depending on Alignment

Mode, the length of the Intra-Packet Header is either 10 or 12 bytes(80 or 96 bits) positioned contiguously, as depicted in Figure 10-20. In 16 BitAlignment Mode, the Intra-Packet Data Header length is fixed at 2 bytes. A

32 Bit Alignment Mode requires a 4 byte Intra-Packet Data Header, and the two

most significant bytes are zero-filled.

10-42

7/31/2019 IRIG_106_2009



msb lsb31 16 15 12 11 0

TIME (LSLW)

TIME (MSLW)zero filled LOCKST RESERVED

Figure 10-20. PCM Intra-packet header.

Intra-Packet Time Stamp. (8 Bytes) indicates the time tag of the PCMminor frame. Not valid for Throughput Mode. First Long Word Bits and

Second Long Word Bits indicate the following values:

o The 48-bit Relative Time Counter that corresponds to the first data bit of the minor frame with bits 31 to 16 in the second long word zero filled; or

o Absolute Time, if enabled by bit 6 in the Packet Flags (paragraph

10.6.1.1.g). Time format corresponds to the time format indicated by

bits 2 and 3 in the Packet Flags (paragraph 10.6.1.1.g) and to the firstdata bit of the minor frame.

Intra-Packet Data Header.

o 32 Bit Alignment (32-Bit Alignment Mode ONLY). Bits 31-16 are zero

filled.

o Lock Status (LOCKST). (bits 15-12) indicates the lock status of the

frame synchronizer for each minor frame.Bits 15-14: Indicates Minor Frame Status.

00 = Reserved.

01 = Reserved.

10 = Minor Frame Check (after losing Lock).11 = Minor Frame Lock.

Bits 13-12: Indicates Major Frame Status.00 = Major Frame Not Locked.

01 = Reserved.

10 = Major Frame Check (after losing Lock).

11 = Major Frame Lock.

o Reserved. (bits 11-0) are reserved.

10.6.3 Time Data Packets.

10.6.3.1 Time Data Packets, Format 0. Reserved.

10.6.3.2 Time Data Packets, Format 1 (IRIG/GPS/RTC). Time is treated like another data

channel. If a time source other than “none” is used (Figure 10-22), the time packet will begenerated at a minimum frequency of 1 Hz.

IRIG Time Type Formats. The 10 MHz RTC shall be captured for insertioninto the Time Packet Data header IAW IRIG 200 Serial Time Code Formats;

On-Time Reference Marker definition.

10-43

7/31/2019 IRIG_106_2009



All Non-IRIG Time Type Formats. The 10 MHz RTC shall be captured forinsertion into the Time Packet Data header consistent with the resolution with

the Time Packet Body format (10 milliseconds as measured by the 10 MHz

RTC).

A Time Data Packet shall be the first dynamic data packet at the start of eachrecording. Only static Computer Generated Data, Format 1, packets may

precede the first Time Data Packet in the recording.

If the Time Data Packet Source is None, at least one Time Data Packet is

required IAW the previous NOTE.

A packet with time data has the basic structure shown in Figure 10-21. Note

that the width of the structure is not related to any number of bits. This drawing is

merely to represent relative placement of data in the packet. Time Packets do not

have Intra-Packet Headers.

PACKET HEADER


TIME DATA

PACKET TRAILER

Figure 10-21. General time data packet, format 1.

a. Time Packet Channel Specific Data. The Packet Body portion of each Time

Data Packet begins with a Channel Specific Data word formatted as shown inFigure 10-22.

msb lsb

31 12 11 8 7 4 3 0

RESERVED DATE FMT SRC

Figure 10-22. Time Packet channel specific data format.

Reserved. (bits 31-12) are reserved.

Date Format (DATE). (bits 11-8) indicates the Date format. All bit patternsnot used to define a date format type are reserved for future growth.

Bits 11-10: Reserved.

Bit 9: Indicates Date Format.

0 = IRIG day available (Figure 10-23)

1 = Month and Year available (Figure 10-24)

Bit 8: Indicates if this is a leap year.

0 = Not a leap year

10-44

7/31/2019 IRIG_106_2009



1 = Is a leap year

Time Format (FMT). (bits 7-4) indicates the Time Data Packet format.0x0 = IRIG-B

0x1 = IRIG-A

0x2 = IRIG-G

0x3 = Real-Time Clock 0x4 = UTC Time from GPS

0x5 = Native GPS Time

0x6 thru 0xE = Reserved0xF = None (time packet payload invalid)

Time Source (SRC). (bits 3-0) indicates the source of the time in thepayload of each time packet.

0x0 = Internal (Time derived from a clock in the Recorder)0x1 = External (Time derived from a clock not in the Recorder)

0x2 = Internal from RMM (Time derived from the clock in the RMM)

0x3 – 0xE = Reserved0xF = None

If the Time Source (SRC) is External (0x1) and lock on the external source islost then the Time Source (SRC) shall indicate Internal (0x0). Once lock on

the external Time Source is regained, Time Source (SRC) shall once again

indicate External (0x1).

b. Time Packet Body. After the Channel Specific Data word, the time data words

are inserted in the packet in Binary Coded Decimal (BCD) format as shown inFigure 10-23 and Figure 10-24 (units of measure presented in Table 10-8).

msb lsb

15 12 11 8 7 4 3 0

0 TSn Sn Hmn Tmn

0 0 THn Hn 0 TMn Mn

0 0 0 0 0 0 HDn TDn Dn

Figure 10-23. Time data - packet format, day format.

msb lsb

15 12 11 8 7 4 3 0

0 TSn Sn Hmn Tmn

0 0 THn Hn 0 TMn Mn

0 0 0 TOn On TDn Dn

0 0 OYn HYn TYn Yn

Figure 10-24. Time data - packet format, day, month, and year format.

10-45

7/31/2019 IRIG_106_2009



TABLE 10-8. UNITS OF MEASURE

Tmn Tens of milliseconds TDn Tens of days

Hmn Hundreds of milliseconds HDn Hundreds of Days

Sn Units of seconds On Units of Months

TSn Tens of Seconds TOn Tens of Months

Mn Units of minutes Yn Units of Years

TMn Tens of minutes TYn Tens of Years

Hn Units of hours HYn Hundreds of Years

THn Tens of Hours OYn Thousands of Years

Dn Units of Days 0 Always zero

10.6.4 MIL-STD-1553.

10.6.4.1 MIL-STD-1553 Bus Data Packets, Format 0. Reserved

10.6.4.2 MIL-STD-1553 Bus Data Packets, Format 1 (MIL-STD-1553B Bus Data).MIL-STD-1553 BUS data is packetized in Message Mode, with each 1553 bus “transaction”

recorded as a “message.” A transaction is a BC-to-RT, RT-to-BC, or RT-to-RT word sequence,

starting with the command word and including all data and status words that are part of thetransaction, or a mode code word broadcast. Multiple messages may be encoded into the data

portion of a single packet.

a. MIL-STD-1553 Packet Channel Specific Data. The Packet Body portion of

each MIL-STD-1553 data packet begins with a Channel Specific Data word

formatted as shown in Figure 10-25.

msb lsb31 30 29 24 23 0

TTB RESERVED MSGCOUNT

Figure 10-25. MIL-STD-1553 Packet channel specific data format.

Time Tag Bits (TTB). (bits 31-30) indicate which bit of the MIL-STD-1553

message the Intra-Packet Header time tags.

00 = Last bit of the last word of the message01 = First bit of the first word of the message

10 = Last bit of the first (command) word of the message

11 = Reserved


Message Count (MSGCOUNT). (bits 23-0) indicates the binary value of the

number of messages included in the packet. An integral number of complete messages will be in each packet.

b. MIL-STD-1553 Packet Body. A packet with n MIL-STD-1553 messages has

the basic structure shown in Figure 10-26. Note that the width of the structure

10-46

7/31/2019 IRIG_106_2009



is not related to any number of bits. This drawing is merely intended torepresent relative placement of data in the packet.

PACKET HEADER


INTRA-PACKET TIME STAMP FOR MESSAGE 1

INTRA-PACKET DATA HEADER FOR MESSAGE 1

MESSAGE 1

INTRA-PACKET TIME STAMP FOR MESSAGE 2

INTRA-PACKET DATA HEADER FOR MESSAGE 2

MESSAGE 2

:

INTRA-PACKET TIME STAMP FOR MESSAGE n

INTRA-PACKET DATA HEADER FOR MESSAGE n

MESSAGE n

PACKET TRAILERFigure 10-26. MIL-STD-1553 data packet, format 1.

c. MIL-STD-1553 Intra-Packet Header. After the Channel Specific Data, theMIL-STD-1553 data are inserted into the packet in messages. Each

MIL-STD-1553 message is preceded by an Intra-Packet Header consisting of an

Intra-Packet Time Stamp and an Intra-Packet Data Header.

(1) MIL-STD-1553 Intra-Packet Time Stamp. (8 Bytes) indicates the time tagof the MIL-STD-1553 message as follows.

The 48-bit Relative Time Counter that corresponds to the data bit

indicated in the MIL-STD-1553 Channel Specific Data, Time Tag Bits(paragraph 10.6.4.2a) with bits 31 to 16 in the second long word zerofilled; or

The Absolute Time, if enabled by bit 6 in the Packet Flags(paragraph 10.6.1.1.g). Time format corresponds to the time format

indicated by bits 2 and 3 in the Packet Flags (paragraph 10.6.1.1.g) and

to the data bit indicated in the MIL-STD-1553 Channel Specific Data,Time Tag Bits (paragraph 10.6.4.2a).

(2) MIL-STD-1553 Intra-Packet Data Header. The length of the Intra-Packet

Data Header is fixed at 6 bytes (48 bits) positioned contiguously, in the

following sequence (Figure 10-27).

msb lsb

15 0

BLOCK STATUS WORD

GAP TIMES WORD

LENGTH WORD

Figure 10-27. MIL-STD-1553 intra-packet data header.

10-47

7/31/2019 IRIG_106_2009



Block Status Word (BSW). (bits 15-0) contain the Block Status Wordfor both the message type and any 1553 bus protocol errors that

occurred during the message transfer. The Block Status Word bit

definitions are in Figure 10-28.

msb lsb

15 14 13 12 11 10 9 8 6 5 4 2 0

R BID ME RR FE TM RESERVED LE SE WE RESERVED

Figure 10-28. Block status word format.

o Reserved (R). (bits 15-14) are reserved.

o Bus ID (BID). (bit 13) indicates the bus ID for the message.0 = Message was from Channel A

1 = Message was from Channel B

o Message Error (ME). (bit 12) indicates a message error wasencountered.0 = No message error

1 = Message error

o RT to RT Transfer (RR). (bit 11) indicates a RT to RT transfer;

message begins with two command words.0 = No RT to RT transfer

1 = RT to RT transfer

o Format Error (FE). (bit 10) indicates any illegal gap on the bus

other than Response Time Out.

0 = No format error1 = Format error

o Response Time Out (TM). (bit 9) indicates a response time out

occurred. The bit is set if any of the Status Word(s) belonging tothis message didn’t arrive within the response time of 14µs defined

by MIL-STD-1553B.

0 = No response time out

1 = Response time out


o Word Count Error (LE). (bit 5) indicates that the number of data

words transmitted is different than identified in the commandword. A MIL-STD-1553B Status Word with the busy bit set totrue will not cause a Word Count Error. A transmit command with

a response timeout will not cause a Word Count Error.

0 = No word count error

1 = Word count error

10-48

7/31/2019 IRIG_106_2009



o Sync Type Error (SE). (bit 4) indicates an incorrect sync typeoccurred.

0 = No sync type error

1 = Sync type error

o Invalid Word Error (WE). (bit 3) indicates an invalid word error

occurred. This includes Manchester decoding errors in the synchpattern or word bits, invalid number of bits in the word, or parity

error.0 = No invalid word error

1 = Invalid word error


Gap Times (Response Time): The Gap Times Word indicates remoteterminal response times as defined by MIL-STD-1553. The resolution of the

response time shall be in tenths of microseconds. A maximum of two

Response Time Words can exist. Remote Terminal to Remote Terminal typemessages shall have two Response Time Words if both terminals respond; all

other messages will have one Response Time Word, or none for broadcast

type messages or messages with no Remote Terminal response.

Gap Times Word (bits 15-0). The Gap Times Word indicates thenumber of tenths of microseconds in length of the internal gaps within

a single transaction. For most messages, only GAP1 is meaningful. Itmeasures the time between the command or data word and the first

(and only) status word in the message. For RT-to-RT messages,

GAP2 measures the time between the last data word and the second

status word. The Gap Times Word bit definitions are as shown inFigure 10-29.

msb lsb

15 8 7 0

GAP2 GAP1

Figure 10-29. Gap Times word format.

Gap measurements shall be made IAW MIL-STD-1553 response timemeasurements from the mid-bit zero crossing of the parity bit of the last

word to the mid-zero crossing of the sync of the status word.

Length Word Bits (15-0). The Length of the message is the totalnumber of bytes in the message. A message consists of command

words, data words, and status words.

10-49

7/31/2019 IRIG_106_2009



d. Packet Format. Unless an error occurred, as indicated by one of the error flagsin the Block Status Word, the first word following the Length Word should

always be a command word. The resultant packets have the format shown in

Figure 10-30.

msb lsb 15 0

PACKET HEADER CHANNEL SPECIFIC DATA (BITS 15-0) CHANNEL SPECIFIC DATA (BITS 31-16)

INTRA-PACKET TIME STAMP FOR MSG 1 (BITS 15-0) INTRA-PACKET TIME STAMP FOR MSG 1 (BITS 31-16) INTRA-PACKET TIME STAMP FOR MSG 1 (BITS 47-32) INTRA-PACKET TIME STAMP FOR MSG 1 (BITS 63-48) INTRA-PACKET DATA HEADER FOR MSG 1 (BITS 15-0) INTRA-PACKET DATA HEADER FOR MSG 1 (BITS 31-16) INTRA-PACKET DATA HEADER FOR MSG 1 (BITS 47-32)

COMMAND WORD COMMAND, STATUS, OR DATA WORD DATA OR STATUS WORD

: DATA OR STATUS WORD

INTRA-PACKET TIME STAMP FOR MSG 2 (BITS 15-0) INTRA-PACKET TIME STAMP FOR MSG 2 (BITS 31-16) INTRA-PACKET TIME STAMP FOR MSG 2 (BITS 47-32) INTRA-PACKET TIME STAMP FOR MSG 2 (BITS 63-48) INTRA-PACKET DATA HEADER FOR MSG 2 (BITS 15-0) INTRA-PACKET DATA HEADER FOR MSG 2 (BITS 31-16) INTRA-PACKET DATA HEADER FOR MSG 2 (BITS 47-32)

COMMAND WORD COMMAND, STATUS, OR DATA WORD

DATA OR STATUS WORD :


INTRA-PACKET TIME STAMP FOR MSG N (BITS 15-0) INTRA-PACKET TIME STAMP FOR MSG N (BITS 31-16) INTRA-PACKET TIME STAMP FOR MSG N (BITS 47-32) INTRA-PACKET TIME STAMP FOR MSG N (BITS 63-48) INTRA-PACKET DATA HEADER FOR MSG N (BITS 15-0) INTRA-PACKET DATA HEADER FOR MSG N (BITS 31-16) INTRA-PACKET DATA HEADER FOR MSG N (BITS 47-32)

COMMAND WORD COMMAND OR DATA, WORD


DATA OR STATUS WORD PACKET TRAILER

Figure 10-30. MIL-STD-1553 data packet, format 1.

10-50

7/31/2019 IRIG_106_2009



10.6.4.3 MIL-STD-1553 Bus Data Packets, Format 2 (Bus 16PP194 Weapons Bus Data).This data type provides packetization for F-16 MIL-STD-1553 weapons multiplex bus as defined

in document 16PP362A (Weapons MUX (WMUX) protocols). A 16PP194 transaction consists

of 6 each 32-bit words consisting of a 16PP194 COMMAND (1), COMMAND (1) ECHO,COMMAND (2), COMMAND (3, GO NOGO), COMMAND (4, GO NOGO), STATUS as

illustrated in Figure 10-31. Multiple transactions may be encoded into the data portion of asingle packet.

Figure 10-31. 16PP194 message transaction.

a. MIL-STD-1553 16PP194 Packet Channel Specific Data Word. The Packet

Body portion of each 16PP MIL-STD-1553 data packet begins with a Channel

Specific Data word formatted as shown in Figure 10-32.

msb lsb

31 0

MSGCOUNT

Figure 10-32. MIL-STD-1553 16PP194 packet channel specific data format.

Message Count (MSGCOUNT). (bits 31-0) indicates the binary value of thenumber of messages included in the packet. An integral number of

complete transaction messages will be in each packet.

b. MIL-STD-1553 16PP194 Packet Body. A packet with n MIL-STD-1553

16PP194 transactions has the basic structure shown in Figure 10-33 below.This drawing is merely to represent relative placement of data in the packet.

10-51

7/31/2019 IRIG_106_2009



msb lsb

31 0

PACKET HEADER

16PP194 CHANNEL SPECIFIC DATA WORD

INTRA-PACKET TIME STAMP (LSLW)

INTRA-PACKET TIME STAMP (MSLW)

INTRA PACKET DATA

HEADER LENGTH WORD

INTRA PACKET DATA

HEADER STATUS WORD

DATA 1

.

.



INTRA PACKET DATA

HEADER LENGTH WORD

INTRAPACKET DATA

HEADER STATUS WORD

DATA N

.

.

PACKET TRAILER

Figure 10-33. MIL-STD-1553 16PP194 data packet.

c. MIL-STD-1553 16PP194 Intra-Packet Header. The intra-packet header consists

of the intra-packet data header (LENGTH and STATUS) and the intra-packet

time stamp.

MIL-STD-1553 16PP194 Intra-Packet Data Header LENGTH. The lengthword contains the length in bytes of the intra-packet data.

The Intra-packet length is fixed to 0x18, 24 bytes.

MIL-STD-1553 16PP194 Intra-Packet Data Header STATUS. The status

word contains error and special handling information about the data. The

error indicator bits when set to a ‘1’ reflect that such an error is present in

the data or occurred during data reception. The format of the status word isshown in Figure 10-34.

msb lsb

15 14 13 12 7 6 5 4 3 2 0

TE RE TM RESERVED SE R EE RESERVED

Figure 10-34. MIL-STD-1553 16PP194 intra-packet data header format.

10-52

7/31/2019 IRIG_106_2009



o Transaction Error (TE): (bit 15) Error condition found in 16PP194

transaction.

0 = No Errors found in current transaction1 = ERROR Condition Found in transaction

o Reset (RE): (bit 14) Indicates a 16PP194 Bus Master Reset.0 = No Master Reset

1 = Master reset Detected on

o Message Time Out (TM). (bit 13) Indicates a transaction time outoccurred.

0 = No message time out

1 = Message time out

o Reserved. (bits 12-7) are reserved

o Status Error (SE). (bit 6) Indicates Status Word missing intransaction.

0 = Status word present

1 = Status word missing

o Reserved (R). (bits 5-4) are reserved.

o Echo Error (EE). (bit 3) Indicates Echo Word missing in

transaction.

0 = Echo word present

1 = Missing Echo Word


MIL-STD-1553 16PP194 Intra-Packet Time Stamp. The intra-packet timestamp (64 bits total) contains a 48-bit relative timestamp in the low-orderbits. The 16 high-order bits are zero.

d. Packet Format. Unless an error occurred, as indicated by one of the error flags

in the Intra-Packet Data Header, the first word following the Length shouldalways be the first transaction command word. The resultant packets have the

format shown in Figure 10-35.

10-53

7/31/2019 IRIG_106_2009



msb lsb

15 0PACKET HEADER


CHANNEL SPECIFIC DATA (BITS 31-16) INTRA PACKET TIME STAMP (BITS 0-15)

INTRA PACKET TIME STAMP (BITS 31-16)



INTRA PACKET DATA HEADER STATUS

INTRA PACKET DATA HEADER LENGTH

COMMAND (1) (BITS 31-16)

COMMAND (1)(BITS 15-0) COMMAND (1) ECHO (BITS 31-16)

COMMAND (1) ECHO (BITS 15-0) COMMAND (2) (BITS 31-16)

COMMAND (2) (BITS 15-0) COMMAND (3) GO NOGO (BITS 31-16)

COMMAND (3) GO NOGO (BITS 15-0) COMMAND (4) GO NOGO ECHO (BITS 31-16)

COMMAND (4) GO NOGO ECHO (BITS 15-0) STATUS (BITS 31-16)

STATUS (BITS 15-0) INTRA PACKET TIME STAMP (BITS 0-15) INTRA PACKET TIME STAMP (BITS 31-16) INTRA PACKET TIME STAMP (BITS 32-47)


INTRA PACKET DATA HEADER STATUSINTRA PACKET DATA HEADER LENGTH

COMMAND (1) (BITS 31-16)

COMMAND (1) (BITS 15-0) COMMAND (1) ECHO (BITS 31-16)

COMMAND (1) ECHO (BITS 15-0) COMMAND (2) (BITS 31-16)

COMMAND (2) (BITS 15-0) COMMAND (3) GO NOGO (BITS 31-16)

COMMAND (3) GO NOGO (BITS 15-0) COMMAND (4) GO NOGO ECHO (BITS 31-16)

COMMAND (4) GO NOGO ECHO (BITS 15-0) STATUS (BITS 31-16)

STATUS (BITS 15-0)

PACKET TRAILER

Figure 10-35. MIL-STD-1553 16PP194 data packet.

10-54

7/31/2019 IRIG_106_2009



e. MIL-STD-1553 16PP194 Data Format. Each 26-bit 16PP194 word in a16PP194 transaction shall be formatted into two 16-bit words (Figure 10-36).

The corresponding 16PP194 Sync and Parity bits will not be formatted into the

16PP194 words.

msb lsb15 14 13 12 11 10 9 8 7 0

BUS ID GAP W P 16PP194Data Word (bits 24-17)

16PP194 Data Word (bits 16-1)

Figure 10-36. MIL-STD-1553 26-bit 16PP194 word format.

MIL-STD-1553 16PP194 BUS ID (BUS ID). A three-bit field shall be usedto indicate bus identification as follows.

111 CIU Left Bus A

110 CIU Left Bus B

101 CIU Right Bus A100 CIU Right Bus B

011 Response Bus A and B

010 Response Bus A

001 Response Bus B

000 Incomplete Transaction

MIL-STD-1553 16PP194 GAP (GAP). A three-bit field shall be used to

indicate GAP between transactions as follows.

111 GAP> 9.15us

110 7.55uS <GAP <=9.15 uS

101 5.95 uS<GAP <=7.55uS

100 4.35 uS<GAP <=5.95

011 2.75 uS<GAP <=4.35uS

010 2.75 uS<GAP <=4.35uS

001 1.15 uS<GAP <=2.75uS

000 Not Applicable

Gap time is measured from mid-crossing of parity bit from previous receivedword to the mid-crossing of the sync bit of the current word in 1uS counts.

MIL-STD-1553 16PP194 Word Bit Error (W). If the bit is set to “1,” this

indicates that a Manchester Error was detected in the word.

MIL-STD-1553 16PP194 Word Parity Error (P). If the bit is set to “1,” thisindicates that a parity error occurred in the word.

16PP194 Data Word (bits 16-1): 16PP194 data field as in Figure 10-37.

10-55

7/31/2019 IRIG_106_2009



16PP194 Data Word (bits 24-17): 16PP194 RIU Address and RIU SubAddress as in Figure 10-37.

Figure 10-37. 16PP194 Word Format.

10.6.5 Analog Data Packets.

10.6.5.1 Analog Data Packets, Format 0. Reserved.

10.6.5.2 Analog Data Packets, Format 1. The generic packet structure for analog data is

illustrated in Figure 10-38.

An Analog Data Packet will contain a Channel Specific Data word for each subchannel

of analog data sampled within that packet if the SAME bit is set to 0, or it will contain a singleChannel Specific Data Word for the entire analog packet if the SAME bit is set to 1. This will be

followed by at least one complete sampling schedule of data.

A sampling schedule is defined as a sampling sequence in which each subchannel,

described by a Channel Specific Data word, is sampled at least once. In many cases, due tosimultaneous sampling rules and varied sampling rates, a particular subchannel will be sampledmore than once during a sampling schedule. In addition, multiple complete sampling schedules

may be included in a single packet. For these reasons, the number of Channel Specific Data

words will usually be less than the number of samples.

Figure 10-38 depicts the generic packet data structure for M data subchannels and a

single sampling schedule that has a length N. Note that the width of the structure is not related to

any number of bits and is merely intended to represent relative placement of words within thepacket.

10-56

7/31/2019 IRIG_106_2009


7/31/2019 IRIG_106_2009



0 = each analog channel has its own Channel Specific Data Word1 = The Channel Specific Data Word is valid for all analog channels

stored in this packet

Factor. (bits 27-24) is the exponent of the power of 2 sampling rate factor

denominator for the corresponding subchannel in the range 0 to 15. (The

sampling rate factor numerator is always 1.)0x0 = sampling rate factor denominator 20 = 1 => factor = 1 / 1

0x1 = sampling rate factor denominator 21

= 2 => factor = ½0x2 = sampling rate factor denominator 22 = 4 => factor = ¼

:

0xF = sampling rate factor denominator 215

= 32768 => factor =1 / 32768

Totchan. (bits 23-16) indicates the total number of analog subchannels in

the packet (and the number of Channel Specific Data words in the packet).

This Totchan field must be the same value in all Channel Specific Data

words in a single packet. The Totchan value may be less than the largestSubchan value. This can happen when a multi-channel analog input devicehas some of its subchannels disabled (turned off) for a specific recording.

For example, if an analog input device has eight subchannels and not all

eight are active, an analog data packet may have three subchannels(Totchan=3) numbered 4, 7, and 8 (enabled Subchan = 4, 7, 8). The

number of subchannels (Totchan) and the subchannel number for each

active subchannel (Subchan) in a packet are identified in the accompanying

TMATS (Computer Generated Data, Format 1) packet.0x00 = 256 Subchannels0x01 = 1 Subchannel

0x02 = 2 Subchannels

Subchan. (bits 15-8) indicates a binary value representing the number of theanalog subchannel.

When an Analog Packet contains data from more than one subchanneland the Channel Specific Data Words are not the same for all channels (see

field Same, bit 28), the Channel Specific Data words must be inserted into

the packet in ascending subchannel number as identified by this Subchanfield. The Subchan values in these Channel Specific Data words need not

be contiguous (see Totchan), but they must be in ascending decimal

numerical order with the exception that subchannel 0 (256) is last. If the“Same” bit is set, the Subchan field shall be set to zero.

0x01 = Subchannel 1

0x02 = Subchannel 2

:

0x00 = Subchannel 256

:

10-58

7/31/2019 IRIG_106_2009



Length. (bits 7-2) indicates a binary value representing the number of bits

in the Analog to Digital converter (A/D).000000 = sixty-four bit samples

000001 = one bit samples

:

001000 = eight bit samples:

001100 = twelve bit samples

:

Mode. (bits 1-0) indicates alignment and packing modes of the analog data.

Bit 0 is the packing bit and bit 1 is the alignment bit. When TOTCHAN,

defined, is more than 1, the Mode must be the same for all subchannels in asingle packet.

00 = data is packed

01 = data is unpacked, lsb padded10 = Reserved for future definition

11 = data is unpacked, msb padded

b. Analog Samples. To preserve timing relationships and allow for accuratereconstruction of the data, a simultaneous sampling scheme shall be employed.

The highest sampling rate required shall define the primary simultaneous

sampling rate within the packet. The primary simultaneous sampling rate isidentified in the Telemetry Attributes Transfer Standard (TMATS) file

describing the attributes of the analog data packet. The rate at which the other

subchannels are sampled is then defined by the sampling factor (1, ½, ¼,1 / 8,

1 / 16,1 / 32768) for each subchannel. As an example, a sampling factor of ¼ would

yield that subchannel being sampled at one-fourth the primary simultaneoussampling rate and a sampling factor of 1 would yield that subchannel being

sampled at the primary simultaneous sampling rate.

Directly following the Channel Specific Data word(s), at least one

complete sampling schedule shall be inserted in the packet. The samples,

within the sampling sequence, may be inserted either unpacked, MSB Packed,

or LSB Packed as described in paragraph 10.6.5.2.b(1) and 10.6.5.2.b(2). Ineither case, one or more subchannels may be included in a single packet. When

multiple subchannels are encapsulated into a single packet, the subchannel with

the highest sampling rate requirement defines the primary simultaneoussampling rate. The rate at which the other subchannels are sampled is defined

by the sampling factor (contained within the Channel Specific Data words).Sampling factors are defined as:

X2

1

K

; K = 0, 1, 2, 3, 4, 5, …

of the Primary Simultaneous Sampling Rate X.

10-59

7/31/2019 IRIG_106_2009



10-60

The subchannels are then sampled and ordered such that:

The highest sample rate X1 subchannel(s) appear in every simultaneoussample,

X

2

1 The subchannel(s) appear in every 2nd simultaneous sample,

The subchannel(s) appear in every 4th simultaneous sample,

… and so on until all the subchannels are sampled, resulting in a complete

sampling schedule of all subchannels described by the Channel Specific Datawords. In doing so, the total number of simultaneous samples (not the total

number of samples) will equal the denominator of the smallest sampling factor

and all subchannels will be sampled in the last simultaneous sample.

X

4

1

For example, a packet with six subchannels with Sampling Factors ½, 1 / 8, 1,

½, 1, and 1 / 8 respectively will yield a sampling sequence within the data packet as:

Simultaneous Sample 1: Subchannel 3
























Simultaneous Sample 8: Subchannel 5Simultaneous Sample 8: Subchannel 6

7/31/2019 IRIG_106_2009



Notice that the denominator of the smallest sampling factor defines the number of simultaneous samples within the packet (in this example, 8). However, the total

number of samples within the sampling schedule does not have to equal the number

of simultaneous samples (in this example, 26). Also notice that all subchannels aresampled during the last Simultaneous Sample. The order of the subchannel samples

in each simultaneous sample is ascending by subchannel number.

Any number of complete sampling schedules may be placed within a packet so

that the maximum packet length is not exceeded. The TMATS file identifies the

number of samples contained within each packet.

(1) Unpacked Mode. In Unpacked Mode, packing is disabled and each sample ispadded with the number of bits necessary to align each word with the next

16-bit boundary in the packet. Four (4) pad bits are added to 12 bit words,

eight (8) pad bits are added to 8-bit words, etc. All pad bits shall equal zero.

Samples less than 8 bits go into a 16-bit word boundary.

To illustrate msb padding, given M analog subchannels mapping into N

samples for the special case of all samples having bit lengths of 12 bits, the

resultant Analog packets with msb padding have the form shown in

Figure 10-40.

msb

15

lsb

0

PACKET HEADER

CHANNEL SPECIFIC DATA WORD, SUBCHANNEL 1 (BITS 15-0)




:

:

:

CHANNEL SPECIFIC DATA WORD, SUBCHANNEL M (BITS 15-0)

CHANNEL SPECIFIC DATA WORD, SUBCHANNEL M (BITS 31-16)4-PAD BITS SAMPLE 1, 12-DATA BITS

4-PAD BITS SAMPLE 2, 12- DATA BITS

4-PAD BITS SAMPLE 3, 12- DATA BITS

:

4-PAD BITS SAMPLE N, 12- DATA BITS

PACKET TRAILER

Figure 10-40. Analog data packet - unpacked mode, msb padding.

10-61

7/31/2019 IRIG_106_2009



To illustrate LSB Packing, given M analog subchannels mapping into Nsamples for the special case of all samples having bit lengths of 12 bits, the

resultant Analog packets with LSB padding have the form shown in

Figure 10-41.

msb15 lsb0

PACKET HEADER





:

:

:


CHANNEL SPECIFIC DATA WORD, SUBCHANNEL M (BITS 31-16):

SAMPLE 1, 12- DATA BITS 4-PAD BITS



SAMPLE N, 12- DATA BITS 4-PAD BITS

PACKET TRAILER

Figure 10-41. Analog data packet - unpacked mode, lsb padding.

(2) Packed Mode. In Packed Mode, packing is enabled and padding is not added

to each data word. However, if the number of bits in the packet are not aninteger multiple of 16, then Y filler bits will be used to msb fill the last data

word, forcing alignment on a 16-bit boundary. The value of Y is sixteen (16)minus the integer remainder of L, the total number of data bits in the packet,

divided by 16 and is mathematically expressed as:

Y = 16 - (MODULUS{L,16}).

To illustrate msb padding, given M Analog subchannels mapping into N

samples for the special case of all samples having bit lengths of 12 bits, theresultant Analog packets with padding bits at the end of the N th sample have

the form shown in Figure 10-42.

10-62

7/31/2019 IRIG_106_2009



msb

15

lsb

0

PACKET HEADER


CHANNEL SPECIFIC DATA WORD, SUBCHANNEL 1 (BITS 31-16)CHANNEL SPECIFIC DATA WORD, SUBCHANNEL 2 (BITS 15-0)


:

:

:



SAMPLE 2 (BITS 3-0) SAMPLE 1 (BITS 11-0)

SAMPLE 3 (BITS 7-0) SAMPLE 2 (BITS 11-4)

: :

: :: :

Y PADDING BITS SAMPLE N (BITS 11-0)

:

PACKET TRAILER

Figure 10-42. Analog data packet - packed mode packet.

10.6.6 Discrete Data Packets.

10.6.6.1 Discrete Data Packets, Format 0. Reserved.

10.6.6.2 Discrete Data Packets, Format 1. A packet with Discrete data has the basic structureshown in Figure 10-43. Note that the width of the structure is not related to any number of bits.

This drawing is merely intended to represent relative placement of data in the packet. One to 32discrete states may be recorded for each event.

PACKET HEADER


INTRA-PACKET HEADER FOR EVENT 1

EVENT 1 STATES

INTRA-PACKET HEADER FOR EVENT 2

EVENT 2 STATES

:

INTRA-PACKET HEADER FOR EVENT N

EVENT N STATES

PACKET TRAILER

Figure 10-43. General discrete data packet, format 1.

10-63

7/31/2019 IRIG_106_2009



a. Discrete Packet Channel Specific Data Word. The Packet Body portion of eachDiscrete packet begins with the Channel Specific Data Word, which is


msb lsb

31 8 7 3 2 0RESERVED LENGTH MODE

Figure 10-44. Discrete packet channel data word format.

Reserved. (bits 31-8)

Length (bits 7-3). Indicates a binary value representing the number of bitsin the event.

Mode (bits 2-0). Indicates the mode of accessing the discrete data.

Bit 0: indicates the Record State.0 = discrete data is recorded when the state changes

1 = discrete data is recorded on a time interval basis

Bit 1: indicates the alignment of the data.0 = lsb1 = msb

Bit 2: reserved.

b. Discrete Data. After the Channel Specific Data, Discrete data (Figure 10-45) is

inserted in the packet. Discrete data are described as Events. Each Event

includes the Event State for each discrete input and the corresponding Intrapacket Time. The Event State is a 32-bit word that provides the logical state of

each discrete input.

msb lsb

31 30 1 0

D31 D30 … D1 D0

Figure 10-45. Discrete data format.

Discrete Event Bits. (Bits 31-0) indicate the states of the discrete event bits.

Bit 31: indicates Discrete 31 (D31) State.

0 = discrete 31 is at state 0

1 = discrete 31 is at state 1Bit 30: indicates Discrete 30 (D30) State.



Bit 1: indicates Discrete 1 (D1) State.0 = discrete 1 is at state 0


10-64

7/31/2019 IRIG_106_2009



Bit 0: indicates Discrete 0 (DO) State.

0 = discrete 0 is at state 01 = discrete 0 is at state 1

c. Discrete Event Intra-Packet Header. All discrete events shall include an Intra-

Packet Header consisting of an Intra-Packet Time Stamp only, which is insertedimmediately before the discrete event. The length of the Intra-Packet Header is

fixed at 8 bytes (64 bits) positioned contiguously, arranged in the sequenceshown in Figure 10-46.

msb lsb

31 0

TIME (LSLW)

TIME (MSLW)

Figure 10-46. Discrete event intra-packet header.

Intra-Packet Time Stamp. (8 Bytes) indicate the time tag of the discreteevent. First Long Word Bits 31-0 and Second Long Word Bits 31-0 indicate

the following values:

(1) The 48-bit Relative Time Counter that corresponds to the first data bit

of the discrete event with bits 31 to 16 in the second long word zerofilled or;

(2) The Absolute Time, if enabled by bit 6 in the Packet Flags

(paragraph 10.6.1.1.g). Time format corresponds to the time format


to the first data bit of the discrete event. The discrete data packet formatis presented in Figure 10-47.

10-65

7/31/2019 IRIG_106_2009



msb lsb

15 0

PACKET HEADER


CHANNEL SPECIFIC DATA (BITS 31-16)INTRA-PACKET TIME STAMP FOR EVENT 1 (BITS 15–0)

INTRA-PACKET TIME STAMP FOR EVENT 1 (BITS 31–16)

INTRA-PACKET TIME STAMP FOR EVENT 1 (BITS 47-32)

INTRA-PACKET TIME STAMP FOR EVENT 1 (BITS 63-48)

STATES FOR EVENT 1 (BITS 15–0)

STATES FOR EVENT 1 (BITS 31–16)

:

INTRA-PACKET TIME STAMP FOR EVENT n (BITS 15–0)

INTRA-PACKET TIME STAMP FOR EVENT n (BITS 31–16)

INTRA-PACKET TIME STAMP FOR EVENT n (BITS 47-32)INTRA-PACKET TIME STAMP FOR EVENT n (BITS 63-48)

STATES FOR EVENT n (BITS 15–0)

STATES FOR EVENT n (BITS 31–16)

PACKET TRAILER

Figure 10-47. Discrete data packet format.

10.6.7 Computer Generated Data Packets. Packets with Computer Generated Data have the

basic structure shown in Figure 10-48. Formats 0, 1, 2, and 3 are used to add informationpackets to recorded data. This information contains annotation data, setup records, events, or

index information for the data that has been recorded. The width of the structure is not related to

any number of bits. This drawing is merely intended to represent relative placement of data inthe packet.

Computer Generated Data is defined as non-external data or data generated

within the recorder. After the Channel Specific Data Word, the Computer

Generated Data is inserted in the packet. The organization and content of the Computer Generated Data is determined by the specific Format type.

PACKET HEADER


COMPUTER GENERATED DATA

PACKET TRAILERFigure 10-48. General computer generated data packet format.

10.6.7.1 Computer Generated Data Packets Format 0, User Defined. Format 0 enables theinsertion of user-defined Computer Generated Data. Data can not be placed in this packet if the

data type is already defined within this standard nor can data be inserted in this packet if it is

generated from an external input to the recorder.

10-66

7/31/2019 IRIG_106_2009



Computer Generated Packets Format 0 Channel Specific Data Word. ThePacket Body portion of each Format 0 Packet begins with the Channel Specific

Data word, which is formatted as shown in Figure 10-49.

msb lsb

31 0RESERVED

Figure 10-49. Computer generated format 0 channel specific data word format.


10.6.7.2 Computer Generated Data Packets Format 1, Setup Records. Format 1 defines asetup record that describes the hardware, software, and data channel configuration used to

produce the other data packets in the file. The organization and content of a Format 1 Setup

Record is indicated in the Channel Specific Data Word FRMT field.

It is mandatory for a setup TMATS record to be utilized to configure the recorder. AFormat 1 Computer Generated Data Packet containing the setup TMATS record utilized toconfigure the recorder shall be the first packet in each data file. A single setup record may span

multiple consecutive packets. When spanning multiple packets, the sequence counter shall

increment in the order of segmentation of the setup record, n+1.

a. Format 1 - Channel Specific Data Word. The Packet Body portion of each

Format 1 Packet begins with the Channel Specific Data word, which is formattedas shown in Figure 10-50.

msb lsb

31 10 9 8 7 0RESERVED FRMT SRCC CH10VER

Figure 10-50. Computer generated format 1 channel specific data word format.


FRMT (bit 9): Setup record format.0 = Setup Record IAW IRIG-106 Chapter 9 ASCII Format

1 = Setup Record IAW IRIG-106 Chapter 9 XML Format

It is not permissible to have both ASCII and XML IRIG-106 Chapter 9TMATS attributes in the same recording or recording sessions.

Setup Record Configuration Change (SRCC). (bit 8) indicates if the recorderconfiguration contained in the previous Setup Record packet(s) of the current

recording session (defined as .RECORD to .STOP) has changed.

10-67

7/31/2019 IRIG_106_2009



0 = Setup Record Configuration has Not Changed1 = Setup Record Configuration has Changed

When a setup record configuration change has taken place, bit 8 (SRCC)

shall be set to 1 and the new setup record packet will be committed to the

stream prior to any new or changed data packets being committed to thestream. The next setup record packet(s) committed to the stream, if not

changed from this new setup record, shall clear the SRCC bit to 0.

Prior to the new setup record being committed to the stream, a “Setup

Record Configuration Change” event packet shall be inserted into thestream.

Each new setup record packet must adhere to all applicable setup recordrequirements including, but not limited to, the minimum required TMATS

attributes.

IRIG-106 Chapter 10 Version (CH10VER). A 1-Byte indicator of whichIRIG-106 Chapter 10 release version the recorder requirements and following

recorded data are applicable to and comply with. The value shall be represented

by the following bit patterns:

0x00 thru 06 = Reserved

0x07 = IRIG-106-070x08 = IRIG-106-09

0x09 thru 0xFF = Reserved

Individual paragraph 10.6 Data Types and their format/content compliancy

and applicability with the IRIG-106 Chapter 10 release version are defined in

paragraph 10.6.1.1e.

10.6.7.3 Computer Generated Data Packets Format 2, Recording Event. Format 2 defines

a recording event packet that contains the occurrence and information of one or more individualevents that have been defined within the Format 1 Setup Record IAW “Recording Events”

attribute. If the Recording Events information is larger than the maximum packet size of 512Kbytes, the Recording Events information may be contained in multiple packets using the Major

Packet Header Sequence Number.

Events associated with the .EVENT command defined in Table 10-9 can only be directly

accessed from the recorder itself and are not contained within the recording data. This does notpreclude defining an event driven by the .EVENT command to also be defined within the

Recording Event setup record information and placed in the appropriate event entry within an

10-68

7/31/2019 IRIG_106_2009



event packet. The .EVENT recorder command and the Recording Event packets will not bedirectly linked in this standard and any linking between the two will be an implementation of this

standard within a recorder.

It is not the intent for the event packets within the data to be directlycoupled with recorder events per the .EVENT command in Table 10-9.

a. Event Packet Location. Recording Event packets may be placed at any location

within the recording after the first Time Data packet and before the last Root

Index Packet. This may be at the time each event occurs, after multiple eventshave occurred or at an interval of time or packets. The complete event log of a

recording (defined in Event Period of Capture paragraph 10.6.7.3c) is

constituted by the contents of all event packets in a recording concatenated inorder of which the event(s) occurred in time.

Index Packets will be enabled if Recording Event Packets are enabled .

b. Channel Specific Data Word. The Packet Body portion of each Format 2

Packet begins with the Channel Specific Data word, which is formatted as

shown in Figure 10-51.

msb lsb31 30 12 11 0

IPDH RESERVED REEC

Figure 10-51. Computer generated format 2 channel specific data word.

Recording Event Intra-Packet Data Header (IPDH). (bit 31) indicates the

presence of the Intra-Packet Data Header.

0 = Recording Event Intra-Packet Data Header Not Present

1 = Recording Event Intra-Packet Data Header Present


Recording Event Entry Count (REEC). (bits 11-0) are an unsigned binarythat identifies the count of recording event entries included in the packet.

c. Event Period of Capture. Denotes the period of capture (Figure 10-52), and isdefined to encompass the events occurring from the time a .RECORD command

(paragraph 10.7.9) is issued (if it is the first recording) until the time a .STOP

command (paragraph 10.7.9) is issued. If there is a previous recording, the

10-69

7/31/2019 IRIG_106_2009



period of capture is described as encompassing those events that occur from theprevious recording’s .STOP command until the .STOP command of the current

recording. This ensures that any events that occurred between recordings will

be captured and will include special indicators that the event occurred between.STOP and .RECORD commands.

Priority conditions and event limit counts are defined in the setup recordattributes for each defined event. The ability to put finite limits on events

during periods of capture precludes overflowing buffers or media capacities.

These priority conditions and event limit counts are as follows:

Priority 1: Defined event will always be captured during and in between

recordings.

Priority 2: Defined event will always be captured during recordings andup to a limit count between recordings.

Priority 3: Defined event will always be captured during recordings and

not captured between recordings.Priority 4: Defined event will be captured up to a limit count during

recordings and between recordings.

Priority 5: Defined event will be captured up to a limit count for each

defined event during recordings and not captured betweenrecordings.

. R E C

O R D

. S T O

P

. R E C

O R D

. S T O P

. R E C

O R D

. S T O P

Recording n+1 Recording n+2Recording n

Recording n EventPeriod

Recording n+1Event Period

Recording n+2Event Period

Figure 10-52. Events recording period.

10-70

7/31/2019 IRIG_106_2009



d. Event Condition of Capture. Event trigger mode conditions during the EventPeriod of Capture are defined in the setup record attributes for each defined

event. These MEASUREMENT DISCRETE or MEASUREMENT LIMIT

trigger mode conditions are as follows:

Mode 1: Capture MEASUREMENT DISCRETE event at eachOn (1) and Off (0) mode transition sampling.Mode 2: Capture MEASUREMENT DISCRETE event at each

On (1) mode transition sampling.

Mode 3: Capture MEASUREMENT DISCRETE event at each

Off (0) mode transition sampling.Mode 4: Capture MEASUREMENT LIMIT event at each

High and Low value transition sampling.

Mode 5: Capture MEASUREMENT LIMIT event at eachHigh value transition sampling.

Mode 6: Capture MEASUREMENT LIMIT event at each

Low value transition sampling.

If Event Type is MEASUREMENT DISCRETE or MEASUREMENT

LIMIT, the trigger measurement must be fully described using the Setup

Record attributes for PCM, Bus, Analog, or Discrete channels. The triggermeasurement source and measurement name shall be identified in the

Event Definition.

e. Event Initial Capture. Event initial capture conditions are defined in the setup

record attributes for each defined event. This determines if an event will be

captured initially prior to the transition mode set for the event if the transition

has already occurred prior to the Event Period of Capture.

f. Event Trigger Measurement Description. If Event Type is MEASUREMENTDISCRETE or MEASUREMENT LIMIT, the trigger measurement must be

fully described using the Setup Record attributes for PCM, Bus, Analog, or

Discrete channels. This shall include at a minimum the following attributes for

the Trigger measurement:

(1) Measurement Source (via data link name).

(2) Measurement Name.(3) Applicable Measurement Value Definition or Bit Mask.

(4) High Measurement Value (if MEASUREMENT LIMIT at or above thehigh limit is used to trigger the event).

(5) Low Measurement Value (if MEASUREMENT LIMIT at or below the

low limit is used to trigger the event).

(6) Applicable Measurement Name Engineering Unit Conversion.

10-71

7/31/2019 IRIG_106_2009



g. Recording Event Intra-Packet Time Stamp. (8 Bytes) indicates the time tag of

the Recording Event Entry as follows:

(1) The 48-bit Relative Time Counter that corresponds to the Event Entry

with bits 31 to 16 in the second long word zero filled. For Event Types

that are MEASUREMENT DISCRETE or MEASUREMENT LIMIT, thetime tag will correspond to the data packet timing mechanism containing

the trigger measurement. This will either be the Packet Header RelativeTime Counter value or, if enabled, the Intra-Packet Time Stamp —

whichever most accurately provides the time the event occurred; or

(2) The Absolute Time, if enabled by bit 6 in the Packet Flags(paragraph 10.6.1.1.g). Time format corresponds to the time format

indicated by bits 2 and 3 in the Packet Flags (paragraph 10.6.1.1.g) and to

the Event Entry. For Event Types that are MEASUREMENT DISCRETE

or MEASUREMENT LIMIT, the time tag will correspond to the datapacket timing mechanism containing the trigger measurement. This will

either be the Packet Secondary Header (if enabled and using an absolutetime value) or, if enabled and using an absolute time value, the Intra-Packet Time Stamp —whichever most accurately provides the time the

event occurred.

The format of the recording event intra-packet header is presented in

Figure 10-53. Figure 10-54 and Figure 10-55 present the general

recording event packet format and recording event entry layout.

h. (Optional) Recording Event Intra-Packet Data Header. (8 Bytes) contains the

absolute time of the event occurrence. The time source and format shall be

derived from the Time Data Packet, Format 1. Unused high-order bits will be

zero filled as needed, depending on the time type of the Time Data Packet.

msb lsb

31 0



(OPTIONAL) INTRA-PACKET DATA HEADER (LSLW)

(OPTIONAL) INTRA-PACKET DATA HEADER (MSLW)

Figure 10-53. Recording event intra-packet header.

i. Event Packet Entry Format. Figures 10-54 and 10-55 present the generalrecording event packet format and recording event entry layout.

10-72

7/31/2019 IRIG_106_2009



PACKET HEADER

(Optional) PACKET SECONDARY HEADER


INTRA-PACKET TIME STAMP FOR EVENT 1

(Optional) INTRA-PACKET DATA HEADER FOR EVENT 1

RECORDING EVENT 1

INTRA-PACKET TIME STAMP FOR EVENT 2

(Optional) INTRA-PACKET DATA HEADER FOR EVENT 2

RECORDING EVENT 2

:

INTRA-PACKET TIME STAMP FOR EVENT n

(Optional) INTRA-PACKET DATA HEADER FOR EVENT n

RECORDING EVENT n

PACKET TRAILER

Figure 10-54. General recording event packet format.

msb lsb

31 29 28 27 12 11 0

RESERVED EO EVENT COUNT NUMBER

Figure 10-55. Recording event entry layout.

Reserved. (bits 31-29) Reserved for future growth and shall be zero filled.

Event Occurrence (EO). (bit 28) Indicates Event Occurrence State.

0 = Indicates the event occurred after the .STOP command and beforethe .RECORD command.

1 = Indicates the event occurred after the .RECORD command and

before the .STOP command.

Event Count. (bits 27-12) An unsigned binary that identifies the count of upto 65,535 occurrences of an individually defined event (as defined by Event

Number in the following paragraph). Event occurrence counts shall begin at

0x0 for the first occurrence of an individual event type (identified by theEvent Number). The event count can roll over to 0x0 and begin to count up

again. The event count applicability is for each Event Period of Capture as

defined in paragraph 10.6.7.3c. The Event Count shall start from 0x0 at the

beginning of each Event Period of Capture incrementing at n+0x1 to0xFFFF for each event occurrence. If the event count reaches 0xFFFF

within the Event Period of Capture it shall roll over to 0x0.

Event Number. (bits 11-0) An unsigned binary that identifies 4096

individual events types defined in the corresponding setup record Recording

Event Number. The Event Number shall begin at 0x0 for the first event

10-73

7/31/2019 IRIG_106_2009



type defined in the setup record and increment n+1 for the next event typedefined in the setup record.

10.6.7.4 Computer Generated Data Packets Format 3, Recording Index. This defines anindex packet for an individual recording file used for direct access into the recording file.

Recording Index packets will be enabled when Recording Event packets are enabled. There are

two types of index packets:

Recording Index packets will be enabled when Recording Event packetsare enabled .

Root Index Packets: contain zero based byte offset entries that are the beginningof Node Index packets. The last entry will be an offset to the beginning of the

previous root index packet if there are more than one Root Index packets, or to the

beginning of the Root Index packet itself, if this root index packet is either thefirst root index packet of the recording or the only root index packet. Root Indexpackets will not contain Filler in the Packet Trailer and will contain a 32-bit Data

Checksum in the Packet Trailer.

Root Index packets shall not contain Filler in the Packet Trailer and shall

contain a 32-bit Data Checksum in the Packet Trailer.

Each recording file with indexes enabled shall have at a minimum one (1)Root Index Type packet.

Node Index Packets: contain Node Items structures containing information

about the location of data packets throughout the recording.

At a minimum, an index entry shall exist for each Time Data Packet in the

recording and, at a minimum, an index entry shall exist for each Recording

Event Packet in the recording.

If the Recording Index Type uses a Count rather than Time, the Time Data

Packets and Computer Generated Data Packets are not included in thecount interval.

If the Recording Index Type uses a Time rather than Count, the Time Data

Packets are not included in the time interval. If the Time Count valuecoincides with the Time Packet rate, then one index entry shall be created.

10-74

7/31/2019 IRIG_106_2009



If the Recording Indexes are enabled the Computer Generated Data Packet

Format 1 Setup Record Count or Time interval value cannot be zero.

a. Recording Index Packet Location. If indexes are enabled, a Root Index packet(Figure 10-56) will be the last packet in any recording file. More than one (1)

Root Index Type packet may be created and may be located within the

recording. Root Index packets are not required to be contiguous. Node IndexTypes may be placed at any location within the recording after the first Time

Data packet and before the last Root Index packet. This may be at an interval of

time or packets. If Indexes are based on a time interval, the time interval shall

be referenced to and based on 10MHz RTC counts. When a time-based indextime interval expiration takes place and all packet(s) are open (not generated),

the index offset and time stamp will be based on the first of the opened packets

generated. Packet generation and packet generation time shall apply per the

definitions in paragraph 10.2.

Figure 10-56. Format showing root index packet.

10-75

7/31/2019 IRIG_106_2009



b. Channel Specific Data Word. The Packet Body portion of each Format 3Packet begins with the Channel Specific Data word, which is formatted as


msb lsb

31 30 29 28 16 15 0

IT FSP IPDH RESERVED INDEX ENTRY COUNTFigure 10-57. Channel specific data word format.

Index Type (IT). (bit 31) indicates the type of index packet.0 = Root Index

1 = Node Index

File Size Present (FSP). (bit 30) indicates if the file size at the time theindex packet was created is present.

0 = File Size Not Present

1 = File Size Present

Index Intra-Packet Data Header (IPDH). (bit 29) indicates the presence of the Intra-Packet Data Header.

0 = Index Intra-Packet Data Header Not Present1 = Index Intra-Packet Data Header Present


Index Entry Count. (bits 15-0) indicates the unsigned binary value of thenumber of index entries included in the packet. An integral number of

complete index entries will be in each packet.

The Intra-Packet Data Header (IPDH) presence once set by bit 29 shall be

the same state for the entire recording.

c. Recording Index Intra-Packet Time Stamp. (8 Bytes) indicates the time tag of the Recording Index Entry as follows:

The 48-bit Relative Time Counter that corresponds to the Index Entry, withbits 31 to 16 in the second long word zero filled. For Node Index Packets

this corresponds to the first bit in the packet body of the packet associatedwith the Node Index Item; or

The Absolute Time, if enabled by bit 6 in the Packet Flags

(paragraph 10.6.1.1.g). Time format corresponds to the time formatindicated by bits 2 and 3 in the Packet Flags (paragraph 10.6.1.1.g) and to

the Index Entry. For Node Index Packets this corresponds to the first bit in

the packet body of the packet associated with the Node Index Item.

d. (Optional) Recording Index Intra-Packet Data Header. (8 Bytes) contains theabsolute time of the Index Entry. The time source and format shall be derived

from the Time Data Packet, Format 1. Unused high-order bits will be zero

10-76

7/31/2019 IRIG_106_2009



filled as needed, depending on the time type of the Time Data Packet.Figure 10-58 presents the format of the recording index intra-packet header.

msb lsb

31 0

INTRA-PACKET TIME STAMP (LSLW) INTRA-PACKET TIME STAMP (MSLW)

(Optional) INTRA-PACKET DATA HEADER (LSLW)

(Optional) INTRA-PACKET DATA HEADER (MSLW)

Figure 10-58. Recording index intra-packet header.

e. Root Index Packet Entry Format. A Root Index Packet contains a Node Index

Offset entry or entries using the format shown in Figure 10-59 and

Figure 10-60.

(Optional) Root Index File Size. (8 Bytes) An unsigned binary that

identifies the current size in bytes of the file at the time the Root Index

Packet was created and placed into the recording. This value should be thesame as the Root Index Offset. The file size is required when a recording is

split across multiple media, individual or multiple channels are split fromthe original recording file, or time slices are extracted from the original

recording. In all cases the original recording file size will allow

recalculation and/or replacement of the index offsets when required.

Node Index Offset. (8 Bytes) An unsigned binary that identifies the zero

based byte offset from the beginning of the recording file to the point in thefile at which the Node Index Packet Sync Pattern (0xEB25) begins.

Root Index Offset. (8 Bytes) An unsigned binary that identifies the zero

based byte offset from the beginning of the recording file to the point in thefile at which the previous Root Index Packet begins, if there are more than

one (1) Root Index Packets or to itself, if it is the first or only Root Index

Packet.

10-77

7/31/2019 IRIG_106_2009



PACKET HEADER



(Optional) ROOT INDEX FILE SIZEINTRA-PACKET TIME STAMP FOR NODE INDEX 1

(Optional) INTRA-PACKET DATA HEADER FOR NODE INDEX 1

NODE INDEX OFFSET 1

:

INTRA-PACKET TIME STAMP FOR NODE INDEX n

(Optional) INTRA-PACKET DATA HEADER FOR NODE INDEX n

NODE INDEX OFFSET n

INTRA-PACKET TIME STAMP FOR ROOT INDEX

(Optional) INTRA-PACKET DATA HEADER FOR ROOT INDEX

ROOT INDEX OFFSET

PACKET TRAILER

Figure 10-59. General recording root index packet.

msb lsb

31 0

(Optional) FILE SIZE (LSLW)

(Optional) FILE SIZE (MSLW)

INTRA-PACKET TIME STAMP FOR NODE INDEX 1 (LSLW)

INTRA-PACKET TIME STAMP FOR NODE INDEX 1 (MSLW)

(Optional) INTRA-PACKET DATA HEADER FOR NODE INDEX 1 (LSLW) (Optional) INTRA-PACKET DATA HEADER FOR NODE INDEX 1 (MSLW)

NODE INDEX OFFSET 1 (LSLW)

NODE INDEX OFFSET 1 (MSLW)

:

INTRA-PACKET TIME STAMP FOR NODE INDEX n (LSLW)

INTRA-PACKET TIME STAMP FOR NODE INDEX n (MSLW)

(Optional) INTRA-PACKET DATA HEADER FOR NODE INDEX n (LSLW)

(Optional) INTRA-PACKET DATA HEADER FOR NODE INDEX n (MSLW)

NODE INDEX OFFSET n (LSLW)

NODE INDEX OFFSET n (MSLW)

INTRA-PACKET TIME STAMP FOR ROOT INDEX (LSLW)INTRA-PACKET TIME STAMP FOR ROOT INDEX (MSLW)

(Optional) INTRA-PACKET DATA HEADER FOR ROOT INDEX (LSLW)

(Optional) INTRA-PACKET DATA HEADER FOR ROOT INDEX (MSLW)

ROOT INDEX OFFSET (LSLW)

ROOT INDEX OFFSET (MSLW)

Figure 10-60. Recording root index entry layout.

10-78

7/31/2019 IRIG_106_2009



f. Node Index Packet Entry Format. A Node Index Packet contains an index entryor entries using the format shown in Figure 10-61 and Figure 10-62.

PACKET HEADER


CHANNEL SPECIFIC DATA (Optional) NODE INDEX FILE SIZE

INTRA-PACKET TIME STAMP FOR NODE INDEX 1


RECORDING NODE INDEX 1

INTRA-PACKET TIME STAMP FOR NODE INDEX 2


RECORDING NODE INDEX 2

:

INTRA-PACKET TIME STAMP FOR NODE INDEX n

(Optional) INTRA-PACKET DATA HEADER FOR NODE INDEX n RECORDING NODE INDEX n

PACKET TRAILER

Figure 10-61. General recording node index packet.

msb lsb

31 24 23 16 15 0

RESERVED DATA TYPE CHANNEL ID

DATA PACKET OFFSET (LSLW)

DATA PACKET OFFSET (MSLW)

Figure 10-62. Recording node index entry layout.

(Optional) Node Index File Size. (8 Bytes) An unsigned binary that

identifies the current size in bytes of the file at the time the Node Index

Packet was created and placed into the recording. This value should be thesame as the Node Index Offset. The file size is required when a recording is

split across multiple media, individual or multiple channels are split from

the original recording file, or time slices are extracted from the originalrecording. In all cases the original recording file size will allow

recalculation and/or replacement of the index offsets when required.

Channel ID. (2 Bytes) An unsigned binary that identifies a value

representing the Packet Channel ID for the data packet associated with thisNode Index Item.

Data Type. (1 Byte) An unsigned binary that identifies a value representingthe type and format of the data packet associated with this Node Index Item.

Data Packet Offset. (8 Bytes) An unsigned binary that identifies the zero

based byte offset from the beginning of the recording file to the point in the

10-79

7/31/2019 IRIG_106_2009



file at which the Data Packet Sync Pattern (0xEB25) begins for this NodeIndex Packet item.

10.6.8 ARINC-429 Data Packets.

10.6.8.1 ARINC-429 Data Packets, Format 0. Data shall be packetized in Word Mode: each32-bit word of an ARINC-429 bus shall be preceded by an Intra-Packet Header containing anIntra-Packet Data Header only with an identifier (ID Word) that provides type and status

information. The Intra-Packet Header does not contain an Intra-Packet Time Stamp. The Packet

Time in the Packet Header is the time of the first ARINC data word in the packet, and the time of successive ARINC data words is determined from the first word time using the gap times in the

ID words that precede each of the data words. Multiple words of multiple ARINC-429 buses can

be inserted into a single packet. The resultant packets shall have the following format as shownin Figure 10-63.

msb lsb15 0

PACKET HEADER



WORD 1 INTRA PACKET DATA HEADER


ARINC-429 DATA WORD 1 (BITS 15-0)

ARINC-429 DATA WORD 1 (BITS 31-16)



ARINC-429 DATA WORD 2 (BITS 15-0)ARINC-429 DATA WORD 2 (BITS 31-16)

:

WORD n INTRA PACKET DATA HEADER

WORD n INTRA PACKET DATA HEADER

ARINC-429 DATA WORD n (BITS 15-0)

ARINC-429 DATA WORD n (BITS 31-16)

PACKET TRAILER

Figure 10-63. ARINC-429 data packet format.

Time tagging of ARINC-429 shall correspond to the first data bit of thepacket.

10-80

7/31/2019 IRIG_106_2009



a. ARINC-429 Packet Channel Specific Data Word. The Packet Body portion of each ARINC-429 data packet shall begin with a Channel Specific Data word


msb lsb

31 16 15 0RESERVED MSGCOUNT

Figure 10-64. ARINC-429 packet channel specific data word format.

Reserved. (bits 31-16) are reserved

Message Count (MSGCOUNT). (Bits 15-0) indicates the binary value of the number of ARINC-429 words included in the packet.

b. Intra-Packet Data Header. (bits 31-0) contains the ARINC-429 ID Word. Each

ARINC-429 bus data word is preceded by an identification word and the bit

definitions are as shown in Figure 10-65.

msb lsb31 24 23 22 21 20 19 0

BUS FE PE BS R GAP TIME

Figure 10-65. Intra-packet data header format.

Bus. (bits 31-24) a binary value identifying the ARINC-429 bus number

associated with the following data word (0 indicates the first bus. A

maximum of 256 buses can be placed in one packet).

Format Error (FE). (bit 23) indicates an ARINC-429 Format Error.

0 = No format error has occurred1 = Format error has occurred

Parity Error (PE). (bit 22) indicates an ARINC-429 Parity Error.0 = No parity error has occurred

1 = Parity error has occurred

Bus Speed (BS). (bit 21) indicates the ARINC-429 bus speed the data is

from.

0 = Indicates Low-Speed ARINC-429 bus (12.5 kHz)1 = Indicates High-Speed ARINC-429 bus (100 kHz)

Reserved (R). (bit 20) is reserved.

Gap Time (GAP TIME). (bits 19-0) contains a binary value that representsthe gap time from the beginning of the preceding bus word (regardless of

bus) to the beginning of the current bus word in 0.1 microsecond

increments. The gap time of the first word in the packet is GAP TIME=0.When the gap time is longer than 100 milliseconds, a new packet must be

started.

10-81

7/31/2019 IRIG_106_2009



c. ARINC-429 Packet Data Words. ARINC-429 Data: The data words shall beinserted into the packet in the original 32-bit format as acquired from the bus .

10.6.9 Message Data Packets.

10.6.9.1 Message Data Packets, Format 0. The data from one or more separate serialcommunication interface channels can be placed into a Message Data Packet (Figure 10-66).

msb lsb

15 0

PACKET HEADER



INTRA-PACKET TIME STAMP FOR MSG 1 (BITS 15–0)


INTRA-PACKET TIME STAMP FOR MSG 1 (BITS 47-32)

INTRA-PACKET TIME STAMP FOR MSG 1 (BITS 63-48)INTRA-PACKET DATA HEADER FOR MSG 1 (BITS 15-0)

INTRA-PACKET DATA HEADER FOR MSG 1 (BITS 31-16)

BYTE 2 BYTE 1

: :

FILLER (IF n IS ODD) BYTE n

:

INTRA-PACKET TIME STAMP FOR MSG n (BITS 15–0)


INTRA-PACKET TIME STAMP FOR MSG n (BITS 47-32)


INTRA-PACKET DATA HEADER FOR MSG n (BITS 15-0)INTRA-PACKET DATA HEADER FOR MSG n (BITS 31-16)

BYTE 2 BYTE 1

: :


PACKET TRAILER

Figure 10-66. Message data packet format.

a. Message Packet Channel Specific Data Word. The Packet Body portion of each

Message Data Packet begins with a Channel Specific Data word. It indicates if

the Packet Body contains several short messages (Type: Complete) or one

segment of a long message (Type: Segmented).

10-82

7/31/2019 IRIG_106_2009



b. Complete Message Channel Specific Data Word. The Channel Specific Data

word is formatted for the Complete type of packet body as shown inFigure 10-67.

msb lsb

31 18 17 16 15 0RESERVED TYPE COUNTER

Figure 10-67. Complete message channel specific data word format.


Type. (bits 17-16) indicates the type of Serial Packet.00 = One or more complete messages

01 = Reserved

10 = Reserved11 = Reserved

Counter. (bits 15-0) contains a binary value indicating the number of

messages included in the packet.

c. Segmented Message Channel Specific Data Word. The Channel Specific Data

word is formatted for the Segmented type of packet body as shown in

Figure 10-68.

msb lsb31 18 17 16 15 0

RESERVED TYPE COUNTER

Figure 10-68. Segmented message channel specific data word format.


Type. (bits 17-16) indicates the type of Serial Packet.00 = Reserved

01 = Packet is a beginning of a long message from a single source

10 = Whole packet is the last part of a long message from a singlesource

11 = Whole packet is a middle part of a long message from a single

source

Counter. (bits 15-0) contains a binary value indicating the segment number

of a long message. The number must start with 1 and must be incremented

by one after each packet. The maximum length of a single long message is4 GBytes (combined with the 16-bit Message Length field, see description

at paragraph 10.6.9.1d below).

d. Message Data Intra-Packet Header. After the Channel Specific Data, Message

Data is inserted into the packet. Each Message is preceded by an Intra-PacketHeader that has both an Intra-Packet Time Stamp and an Intra-Packet Data

Header containing a Message ID Word. The length of the Intra-Packet Header

10-83

7/31/2019 IRIG_106_2009



is fixed at 12 bytes (96 bits) positioned contiguously, in the sequence shown inFigure 10-69.

msb lsb

31 0

TIME (LSLW) TIME (MSLW)

MESSAGE ID WORD

Figure 10-69. Message data intra-packet header.

Intra-Packet Time Stamp. (8 Bytes) indicate the time tag of the Message

Data. First long word bits 31-0 and second long word bits 31-0 indicate the

following values:(1) The 48-bit Relative Time Counter that corresponds to the first data bit

in the Message with bits 31 to 16 in the second long word zero filled

or;

(2) The Absolute Time, if enabled by bit 6 in the Packet Flags(paragraph 10.6.1.1.g). Time format corresponds to the time format


to the first data bit in the Message.

Intra-Packet Data Header. The Intra-Packet Data Header is an identificationword (Message ID Word) that precedes the message and is inserted into the

packet with the format shown in Figure 10-70.

msb lsb

31 30 29 16 15 0

DE FE SUBCHANNEL MESSAGE LENGTH


Data Error (DE). (bit 31) indicates bad data bits as determined by parity,checksums, or CRC words received with the data.

0 = No Data error has occurred

1 = Data error has occurred

Format Error (FE). (bit 30) indicates a protocol error, such as out-of-

sequence data or length errors.0 = No Format Error

1 = Format Error encountered

Subchannel. (bit 29-16) contains a binary value that represents thesubchannel number belonging to the message that follows the ID Word

when the Channel ID in the packet header defines a group of subchannels.Zero means first and/or only subchannel.

Message Length. (bits 15-0) contains a binary value representing the lengthof the message in bytes (n) that follows the ID Word. The maximum length

of a message (complete) or a message segment (segmented) is 64K bytes.

10-84

7/31/2019 IRIG_106_2009



10.6.10 Video Packets.

10.6.10.1 Video Packets, Format 0 (MPEG-2/H.264). Format 0 MPEG-2/H.264 encoding

will be IAW Department of Defense (DoD) Motion Imagery Standards Profile (MISP) Standard

9701– Standard Definition Digital Motion Imagery, Compression Systems. The MPEG-2/H.264format will be Transport Streams (TS) per MISP Recommended Practice (RP) 0101. The TSwill be encapsulated at a Constant Bit Rate (CBR) within the limits of MPEG-2 MP@ML and

H.264 MP@L3 specifications per MISP 9720d (Motion Imagery Standards Matrix (MISM),

Standard Definition Motion Imagery) for further standardization and telemeter/transmissionrequirements of the video.

These MPEG-2/H.264 algorithm features are combined to produce an encoded videostream that will be encapsulated in Format 0 packets. H.264 can be carried over the MPEG-2

transport streams using ITU-T Rec. H.222, Amendment 3, 2004: Transport of AVC data over

ISO/IEC 13818-1/ H.222.0 for MPEG2 TS containment for MPEG4 AVC. MISP has adaptedthis with 9720 and 9701.

Transport streams are limited to a single program stream using Program Elementary

Stream (PES) packets that share the same common time base. A transport stream must containthe Program Association Table (PAT) and Program Map Table (PMT) that define the Program

ID (PID) for the Program Clock Reference (PCR) stream. Program streams also must contain at

least one packet header.

A packet with Format 0 MPEG-2/H.264 Video data has the basic structure shown in

Figure 10-71. Note that the width of the structure is not related to any number of bits. Thisfigure is merely intended to represent relative placement of data in the packet.

PACKET HEADER


(Optional) INTRA-PACKET HEADER

188 BYTE TS DATA


188 BYTE TS DATA

:

(Optional) INTRA-PACKET TIME HEADER

188 BYTE TS DATA

(Optional) INTRA-PACKET TIME HEADER

188 BYTE TS DATA

PACKET TRAILER

Figure 10-71. General MPEG-2/H.264 video packet, format 0.

10-85

7/31/2019 IRIG_106_2009



a. Video Packet Audio. When recording video using Format 0, if audio is presentit will be inserted into the TS per ISO/IEC 13818-3 for MPEG-2 and ISO/IEC

14496-3 for H.264. A separate analog channel to specifically record audio will

not be required as MPEG-2/H.264 supports audio insertion into the TS. Bycombining video and audio, recording bandwidth and memory capacity will be

increased.b. Video Packet Channel Specific Data Word. The packet body portion of each

Format 0 packet begins with the Channel Specific Data word, formatted asshown in Figure 10-72.

msb lsb

31 30 29 28 27 24 23 22 0ET IPH SRS KLV PL BA RESERVED

Figure 10-72. Video packet channel specific data word format.

Embedded Time (ET). (bit 31) indicates if embedded time is present in the

MPEG-2 video data.0 = No embedded time present

1 = Embedded time is present

MPEG-2 stream embedded time if utilized will be IAW MISP Standard9708 - Embedded Time Reference for Motion Imagery Systems and

Standard 9715 - Time Reference Synchronization. Embedded time is used

for the synchronization of core MPEG-2 data when extracted from the IRIG-106 Chapter 10 domain (i.e., an export to MPEG-2 files).

Intra-Packet Header (IPH). (bit 30) indicates if Intra-Packet Time Stamps

are inserted before each Transport Packet.0 = Intra-Packet Times Not Present

1 = Intra-Packet Times Present

SCR/RTC Sync (SRS). (bit 29) indicates if the MPEG-2 SCR is RTC.0 = SCR is not synchronized with the 10 MHz RTC

1 = SCR is synchronized with the 10 MHz RTC

Transport streams contain their own embedded time base used tofacilitate the decoding and presentation of video and/or audio data at the

decoder. Within a Program stream, all streams are synchronized to a single

time source referred to as the System Clock Reference (SCR). Within aTransport stream, each embedded program contains its own PCR, requiring

that each Format 0 encoded MPEG-2/H.264 Transport stream contains only

a single program allowing each format to be treated in a similar mannerusing a single global clocking reference.

The 10 MHz RTC is for the purposes of synchronizing and time

stamping the data acquired from multiple input sources. For input sourcesthat don’t define an explicit timing model for data presentation,

10-86

7/31/2019 IRIG_106_2009



superimposing this timing model can be accomplished. For MPEG-2/H.264, however, an explicit synchronization model based on a 27MHz

clock is defined for the capture, compression, decompression, and

presentation of MPEG-2/H.264 data. In order to relate the two differenttiming models, the MPEG-2/H.264 SCR/PCR timestamps (if enabled) will

be derived from the 10 MHz RTC timing reference source (by generatingthe 27 MHz MPEG-2/H.264 reference clock slaved to the 10 MHz RTC).

MPEG-2/H.264 defines the SCR/PCR timestamp as a 42-bit quantity,

consisting of a 33-bit base value and a 9-bit extension value. The exact

value is defined as:

SCR = SCR_base * 300 + SCR_ext

where:

SCR_base = ((system_clock_frequency * t) / 300) MOD 233

SCR_ext = ((system_clock_frequency * t) / 1) MOD 300

For recording periods of less than 26.5 hours, the SCR can be directlyconverted into the 10 MHz RTC using the equation:

10 MHz RTC time base = SCR * 10 / 27 (rounded to nearest integer)

For recording periods longer than this, the Format 0 packet header timestamp can be used to determine the number of times the MPEG-2/H.264

SCR has rolled over and calculate the upper 8 bits of the free-running

counter’s value.

KLV. (bit 28) indicates if KLV Metadata is present in the MPEG-2 video

data.0 = No KLV Metadata present

1 = KLV Metadata is present

MPEG-2/H.264 stream KLV Metadata, if utilized, will be IAW MISP

Standard 9711 - Intelligence Motion Imagery Index, Geospatial Metadata,Standard 9712 - Intelligence Motion Imagery Index, Content Description

Metadata (Dynamic Metadata Dictionary Structure and Contents),

9713 - Data Encoding Using Key-Length-Value, Recommended Practice

9717 - Packing KLV Packets into MPEG-2 Systems Streams, and Standard0107 – Bit and Byte Order for Metadata in Motion Imagery Files and

Streams. PL. (bit 27-24) indicates the payload type within the MPEG-2 stream per

MISP Xon2:

0000 = MPEG-2 MP@ML

0001 = H.264 [email protected] = H.264 [email protected]

0011 = H.264 MP@L3

0100-1111 = Reserved.

10-87

7/31/2019 IRIG_106_2009



BA. (bit 23) Byte Alignment indicates the MPEG-2 data payload bytealignment within 16-bit words.

0 = Little endian as referenced in Figure 10-74.

1 = Big endian as referenced in Figure 10-75.


c. Intra-Packet Header. If enabled, the Intra-Packet Header shall include a 64-bit

Intra-Packet Time Stamp, which is inserted immediately before the TS syncpattern. The length of the Intra-Packet Header is fixed at 8 bytes (64 bits)

positioned contiguously, in Figure 10-73.

msb lsb

31 0

TIME (LSLW)

TIME (MSLW)

Figure 10-73. Intra-packet header.

Intra-Packet Time Stamp. (8 Bytes) indicate the time tag of the individualTransport Stream packets. First Long Word (LSLW) bits 31-0 and Second

Long Word (MSLW) bits 31-0 indicate the following values:

(1) The 48-bit Relative Time Counter that will correspond to the first bit of the TS. Bits 31 to 16 in the second long word (MSLW) will be zero

filled; or

(2) The Absolute Time, if enabled by bit 6 in the Packet Flags

(paragraph 10.6.1.1.g). Time format indicated by bits 2 and 3 in thePacket Flags (paragraph 10.6.1.1.g) and the first bit of the TS.

d. Video Packet Data: A Format 0 packet shall contain an integral number of 188Byte (1,504 bits) TS packets as illustrated in Figure 10-74 and Figure 10-75

depending on Byte Alignment (BA) bit. Intra-Packet Headers can be inserted in

Format 0 Video Data Packets. The 10MHz RTC Packet Header time is the timeof the first bit of the first TS in the packet.

The CBR of the encoding will be user selectable and within the MPEG-2 MP@ML and

H.264 MP@L3 specification. Per ISO/IEC 13818-1 the TS format will be fixed-length 188 byte(1,504 bits) frames containing an 8-bit sync pattern or “sync byte” (starting at bit 0 and ending at

bit 7 of the TSF). The sync bytes value is 01000111 (0x47). The rest of the TS 187 data bytes

will follow (Figure 10-76).

10-88

7/31/2019 IRIG_106_2009



msb

15

lsb

0

TS SYNC BYTE (BITS 0 TO 7) TS DATA (BITS 8 TO 15)

TS DATA (BITS 16 TO 23) TS DATA (BITS 24 TO 31)

:TS DATA (BITS 1488 TO 1495) TS DATA (BITS 1496 TO 1503)

Figure 10-74. Format 0 MPEG-2/H.264 video frame sync and word format,16-bit little-endian aligned.

msb

15

lsb

0

TS DATA (BITS 8 TO 15) TS SYNC BYTE (BITS 0 TO 7)


:


Figure 10-75. Format 0 MPEG-2/H.264 video frame sync and word format,16-bit big-endian (native) aligned.

msb lsb15 0

PACKET HEADER




TS SYNC BYTE DATA (BITS 15 TO 0)

TS DATA (BITS 31 TO 16)

:TS DATA (BITS 1487 TO 1472)



TS SYNC BYTE DATA (BITS 15 TO 0)


:



:


REPEAT FOR EACH TS

:

PACKET TRAILER

Figure 10-76. Format 0 MPEG-2/H.264 Video Data Packet

(Example is 16-bit Aligned).

10-89

7/31/2019 IRIG_106_2009



10.6.10.2 Video Packets, Format 1 (ISO 13818-1 MPEG-2 Bit Stream). Unlike VideoPackets, Format 0 (MPEG-2) the Format 1 packets encapsulate the complete MPEG-2 ISO/IEC

13818-1:2000 bit streams for both Program and Transport with constant or variable bit rates.

Also any of the Profiles and Level combinations as set forth by MPEG-2 ISO/IEC 13818-1:2000may be utilized in the encoding process. Transport streams are limited to a single program

stream using Program Elementary Stream (PES) packets that share the same common time base.A transport stream must contain the Program Association Table (PAT) and Program Map Table(PMT) that define the Program ID (PID) for the Program Clock Reference (PCR) stream.

Program streams also must contain at least one pack header.

a. MPEG-2 Stream Packet Body. The Format 1 packet with n MPEG-2 packets

has the basic structure shown in Figure 10-77. Note that the width of the

structure is not related to any number of bits. This drawing is merely intendedto represent relative placement of data in the packet.

PACKET HEADER

CHANNEL SPECIFIC DATA(Optional) INTRA-PACKET HEADER

MPEG-2 Packet 1


MPEG-2 Packet 2

:


MPEG-2 Packet n

PACKET TRAILER

Figure 10-77. General MPEG-2 video packet, format 1.

b. Video Packet Audio. When recording video using Format 1, if audio is presentit will be inserted into the TS per ISO/IEC 13818-3. A separate analog channel

to specifically record audio will not be required as MPEG-2 supports audio

insertion into the TS or PS. By combining video and audio, recordingbandwidth and memory capacity will be increased.

10-90

7/31/2019 IRIG_106_2009



c. MPEG-2 Channel Specific Data Word. The Packet Body portion of each

MPEG-2 bit stream begins with a Channel Specific Data word formatted asshown in Figure 10-78.

msb lsb

31 22 21 20 19 18 15 14 13 12 11 0

RESERVED KLV SRS IPH EPL ET MD TP PC

Figure 10-78. MPEG-2 channel specific data word format.

Reserved. (bits 31-22) are reserved for future use.

KLV. (bit 21) indicates if KLV Metadata is present in the MPEG-2 videodata.

0 = No KLV Metadata present1 = KLV Metadata is present.

MPEG-2 stream KLV Metadata (if utilized) will be IAW MISP Standard9711 - Intelligence Motion Imagery Index, Geospatial Metadata, Standard9712 - Intelligence Motion Imagery Index, Content Description Metadata

(Dynamic Metadata Dictionary Structure and Contents), 9713 - Data Encoding

Using Key-Length-Value, Recommended Practice 9717 - Packing KLV Packetsinto MPEG-2 Systems Streams, and Standard 0107 - Bit and Byte Order for

Metadata in Motion Imagery Files and Streams.

SCR/RTC Sync (SRS). (bit 20) indicates whether the MPEG-2 SCR isRTC.

0 = SCR is not synchronized with the 10 MHz RTC.

1 = SCR is synchronized with the 10 MHz RTC.Transport streams contain their own embedded time base used to facilitate

the decoding and presentation of video and/or audio data at the decoder. Within

a Program stream, all streams are synchronized to a single time source referredto as the System Clock Reference (SCR). Within a Transport stream, each

embedded program contains its own PCR, requiring that each Format 1 encoded

MPEG-2 Transport stream contain only a single program allowing each format

to be treated in a similar manner using a single global clocking reference.

The 10 MHz RTC is used to synchronize and time stamp the data acquired

from multiple input sources. For input sources that don’t define an explicit

timing model for data presentation, superimposing this timing model can beaccomplished. For MPEG-2, however, an explicit synchronization model based

on a 27 MHz clock is defined for the capture, compression, decompression, andpresentation of MPEG-2 data. In order to relate the two different timing

models, the MPEG-2 SCR/PCR timestamps (if enabled) will be derived from

the 10 MHz RTC timing reference source (by generating the 27 MHz MPEG-2

reference clock slaved to the 10 MHz RTC).

10-91

7/31/2019 IRIG_106_2009



MPEG-2 defines the SCR/PCR timestamp as a 42-bit quantity, consisting of a 33-bit base value and a 9-bit extension value. The exact value is defined as:


where:

SCR_base = ((system_clock_frequency * t) / 300) MOD 233SCR_ext = ((system_clock_frequency * t) / 1) MOD 300

For recording periods of less than 26.5 hours, the SCR can be directly

converted into the 10 MHz RTC using the equation:

10 MHz RTC time base = SCR * 10 / 27 (rounded to the nearest integer)

For recording periods longer than this, the Format 1 packet header time

stamp can be used to determine the number of times the MPEG-2 SCR has

rolled over and calculate the upper 8 bits of the free-running counter’s value.

Intra-Packet Header (IPH). (bit 19) indicate whether Intra-Packet TimeStamps are inserted before each Program or Transport Packet.

Encoding Profile and Level (EPL). (bits 18-15) indicate the MPEG-2Profile and Level of the encoded bit stream.

0000 = SimpleProfile@MainLevel0001 = MainProfile@LowLevel

0010 = MainProfile@MainLevel

0011 = MainProfile@High-1440Level0100 = MainProfile@HighLevel

0101 = SNRProfile@LowLevel0110 = SNRProfile@MainLevel0111 = SpatialProfile@High-1440Level

1000 = HighProfile@MainLevel

1001 = HighProfile@High-1440Level1010 = HighProfile@HighLevel

1011 = 4:2:2Profile@MainLevel

1100 = Reserved

1101 = Reserved1110 = Reserved

1111 = Reserved

Embedded Time (ET). (bit 14) indicates whether embedded time is present

in the MPEG-2 video data.0 = No embedded time present

1 = Embedded time is present

MPEG-2 stream embedded time, if utilized, will be IAW MISP Standard9708 - Embedded Time Reference for Motion Imagery Systems and Standard

10-92

mailto:SimpleProfile@MainLevel

mailto:MainProfile@LowLevel

mailto:MainProfile@MainLevel

mailto:MainProfile@High-1440Level

mailto:MainProfile@HighLevel

mailto:SNRProfile@LowLevel

mailto:SNRProfile@MainLevel

mailto:SpatialProfile@High-1440Level

mailto:HighProfile@MainLevel

mailto:HighProfile@High-1440Level

mailto:HighProfile@HighLevel

mailto:HighProfile@HighLevel

mailto:HighProfile@High-1440Level

mailto:HighProfile@MainLevel

mailto:SpatialProfile@High-1440Level

mailto:SNRProfile@MainLevel

mailto:SNRProfile@LowLevel






7/31/2019 IRIG_106_2009



9715 - Time Reference Synchronization. Embedded time is used for thesynchronization of core MPEG-2 data when extracted from the IRIG-106

Chapter 10 domain (i.e., an export to MPEG-2 files).

Mode (MD). (bit 13) indicates whether the MPEG-2 bit stream was

encoded using a variable or constant bit rate parameter setting.0 = Constant Bit Rate stream

1 = Variable Bit Rate stream

Type (TP). (bit 12) indicates the type of data the packetized MPEG-2 bit

stream contains.

0 = Transport data bit stream1 = Program data bit stream

Packet Count (PC). (bits 11-0) indicate the binary value of the number of

MPEG-2 packets included in the Format 1 packet.

An integral number of complete packets will be in each Format 1 packet. If the MPEG-2 hardware implementation is unable to determine the value of this

number, the value of 0 is used by default. If TYPE=0, then this number

represents the number of Transport stream packets within the Format 1 packet.If TYPE=1, then this number represents of the number of Program stream packs

within the Format 1 packet.

d. Intra-Packet Header. If enabled, the Intra-Packet Header shall include a 64-bit

Intra-Packet Time Stamp, which is inserted immediately before the MPEG-2

packet (transport or program). The length of the Intra-Packet Header is fixed at8 bytes (64 bits) positioned contiguously, in the following sequence

(Figure 10-79):

msb lsb

31 0

TIME (LSLW)

TIME (MSLW)


Intra-Packet Time Stamp. (8 Bytes) indicate the time tag of the individualMPEG-2 packets (transport or program). First Long Word (LSLW)

bits 31-0 and Second Long Word (MSLW) bits 31-0 indicate the following

values:o The 48-bit Relative Time Counter that will correspond to the first bit of

the MPEG-2 packet (transport or program). Bits 31 to 16 in the second

long word (MSLW) will be zero filled; or

o The Absolute Time, if enabled by bit 6 in the Packet Flags(paragraph 10.6.1.1.g). Time format is indicated by bits 2 and 3 in the

Packet Flags paragraph 10.6.1.1.g) and the first bit of the MPEG-2

packet (transport or program).

10-93

7/31/2019 IRIG_106_2009



10.6.10.3 Video Packets, Format 2 (ISO 14496 MPEG-4 Part 10 AVC/H.264). Format 2

video encoding will be IAW ISO 14496 MPEG-4 Part 10 Advanced Video Coding (AVC). The

carrier format for Format 2 AVC/H.264 will be MPEG-2 ISO/IEC 13818-1:2000 bit streams forboth Program and Transport with constant or variable bit rates. AVC/H.264 can be carried over

the MPEG-2 streams IAW ITU-T Rec. H.222, Amendment 3, 2004: Transport of AVC dataover ITU-T Rec. / H.222.0 | ISO/IEC 13818-1 streams.

Unlike Format 0 Video Packets (MPEG-2\H.264), which only support a fixed MPEG-2

transport and fixed MPEG-2/H.264 profiles and levels, the Format 2 AVC/H.264 packets

encapsulate the complete MPEG-2 transport/program streams, provide for a fixed/variable bitrate (Format 1), and include all H.264 video encoding profiles and levels.

Format 2 AVC/H.264 streams are limited to a single program or transport stream usingProgram Elementary Stream (PES) packets that share the same common time base. The

transport or program stream must contain the Program Association Table (PAT) and Program

Map Table (PMT) that define the Program ID (PID) for the Program Clock Reference (PCR)stream. Program streams also must contain at least one pack header.

a. AVC/H.264 Stream Packet Body. The Format 2 packet with n AVC/H.264

packets has the basic structure shown in Figure 10-80. Note that the width of the structure is not related to any number of bits. This drawing is merely

intended to represent relative placement of data in the packet.

PACKET HEADER



AVC/H.264 Packet 1


AVC/H.264 Packet 2

:


AVC/H.264 Packet n

PACKET TRAILER

Figure 10-80. General AVC/H.264 video packet, format 2.

b. Video Packet Audio. When recording video using Format 2 AVC/H.264, if

audio is present it will be inserted into the per ISO/IEC 13818-3 Audio or

13818-7 AAC. A separate analog channel to specifically record audio will notbe required as AVC/H.264 supports audio insertion into the AVC/H.264

transport stream. By combining video and audio, recording bandwidth and

memory capacity will be increased.

10-94

7/31/2019 IRIG_106_2009



c. AVC/H.264 Channel Specific Data Word. The Packet Body portion of eachAVC/H.264 packet begins with a Channel Specific Data word formatted as


msb lsb

31 27 26 25 22 21 20 19 18 15 14 13 12 11 0R AET EL KLV SRS IPH EP ET MD TP PC

Figure 10-81. AVC/H.264 channel specific data word format.

Reserved (R). (bits 31-26) are reserved for future use.

AVC/H.264 Audio Encoding Type (AET). (bit 26) indicate the AVC/H.264

audio encoding type.0 = ISO/IEC 13818-3 Audio

1 = ISO/IEC 13818-7 AAC

AVC/H.264 Encoding Level (EL). (bits 25-22) indicate the AVC/H.264

Level of the encoded video bit stream.

0000 = 1 0001 = 1b 0010 = 1.1 0011 = 1.2 0100 = 1.30101 = 2 0110 = 2.1 0111 = 2.2 1000 = 3 1001 = 3.1

1010 = 3.2 1011 = 4 1100 = 4.1 1101 = 4.2 1110 = 5

1111 = 5.1

KLV. (bit 21) indicates if KLV Metadata is present in the MPEG-2 video

data.0 = No KLV Metadata present

1 = KLV Metadata is present.

MPEG-2 stream KLV Metadata (if utilized) will be IAW MISP Standard

9711 - Intelligence Motion Imagery Index, Geospatial Metadata, Standard

9712 - Intelligence Motion Imagery Index, Content Description Metadata(Dynamic Metadata Dictionary Structure and Contents), 9713 - DataEncoding Using Key-Length-Value, Recommended Practice 9717 - Packing

KLV Packets into MPEG-2 Systems Streams, and Standard 0107 – Bit and

Byte Order for Metadata in Motion Imagery Files and Streams.

SCR/RTC Sync (SRS). (bit 20) indicates whether the AVC/H.264 MPEG-2

SCR is RTC.

0 = SCR is not synchronized with the 10 MHz RTC.1 = SCR is synchronized with the 10 MHz RTC.

Transport streams contain their own embedded time base used to

facilitate the decoding and presentation of video and/or audio data at thedecoder. Within a Program stream, all streams are synchronized to a single

time source referred to as the System Clock Reference (SCR). Within aTransport stream, each embedded program contains its own PCR, requiring

that each Format 0 encoded MPEG-2 Transport stream contain only a single

program allowing each format to be treated in a similar manner using asingle global clocking reference.

10-95

7/31/2019 IRIG_106_2009



The 10 MHz RTC is provided to synchronize and time stamp the dataacquired from multiple input sources. For input sources that don’t define an

explicit timing model for data presentation, superimposing this timing

model can be accomplished. For MPEG-2, however, an explicitsynchronization model based on a 27 MHz clock is defined for the capture,

compression, decompression, and presentation of MPEG-2 data. In order torelate the two different timing models, the MPEG-2 SCR/PCR timestamps(if enabled) will be derived from the 10 MHz RTC timing reference source

(by generating the 27 MHz MPEG-2 reference clock slaved to the 10 MHz

RTC).

MPEG-2 defines the SCR/PCR timestamp as a 42-bit quantity,

consisting of a 33-bit base value and a 9-bit extension value. The exact

value is defined as:


where:

SCR_base = ((system_clock_frequency * t) / 300) MOD 233

SCR_ext = ((system_clock_frequency * t) / 1) MOD 300

For recording periods of less than 26.5 hours, the SCR can be directly

converted into the 10 MHz RTC using this equation:

10 MHz RTC time base = SCR * 10 / 27 (rounded to nearest integer).

For recording periods longer than this, the Format 0 packet header time

stamp can be used to determine the number of times the MPEG-2 SCR hasrolled over and calculate the upper 8 bits of the free-running counter’s

value.

Intra-Packet Header (IPH). (bit 19) indicate whether Intra-Packet Time

Stamps are inserted before each Program or Transport Packet.

AVC/H.264 Encoding Profile (EP). (bits 18-15) indicate the AVC/H.264

Profile of the encoded video bit stream.0000 = Baseline Profile (BP) 0001 = Main Profile (MP)

0010 = Extended Profile (EP) 0011 = High Profile (HiP)

0100 = High 10 Profile (Hi10P) 0101 = High 4:2:2 Profile (Hi422P)0110 = High 4:4:4 Profile (Hi444P) 0111 – 1111 = Reserved

Embedded Time (ET). (bit 14) indicates whether embedded time is present

in the AVC/H.264 MPEG-2 video data.

0 = No embedded time present

1 = Embedded time is present.

10-96











7/31/2019 IRIG_106_2009



AVC/H.264 MPEG-2 stream embedded time (if utilized) will be IAW MISP Standard

9708 - Embedded Time Reference for Motion Imagery Systems and Standard 9715 - Time

Reference Synchronization. Embedded time is used for the synchronization of core AVC/H.264data when extracted from the IRIG-106 Chapter 10 domain, i.e., an export to AVC/H.264 files.

Mode (MD). (bit 13) indicates whether the AVC/H.264 MPEG-2 bit streamwas encoded using a variable or constant bit rate parameter setting.

0 = Constant Bit Rate stream

1 = Variable Bit Rate stream

Type (TP). (bit 12) indicates the type of data the packetized AVC/H.264

MPEG-2 bit stream contains.0 = Transport data bit stream

1 = Program data bit stream

Packet Count (PC). (bits 11-0) indicate the binary value of the number of

AVC/H.264 packets included in the Format 2 packet.

An integral number of complete packets will be in each Format 2 packet.

If the AVC/H.264 hardware implementation is unable to determine the

value of this number, the value of 0 is used by default. If TYPE=0, then thisnumber represents the number of Transport stream packets within the

Format 2 packet. If TYPE=1, then this number represents of the number of

Program stream packs within the Format 2 packet.

d. Intra-Packet Header. If enabled, the Intra-Packet Header shall include a 64-bit

Intra-Packet Time Stamp, which is inserted immediately before the AVC/H.264

packet (transport or program). The length of the Intra-Packet Header is fixed at

8 bytes (64 bits) positioned contiguously, in the following sequence(Figure 10-82):

msb lsb

31 0

TIME (LSLW)

TIME (MSLW)


Intra-Packet Time Stamp. (8 Bytes) indicates the time tag of the individualAVC/H.264 packets (transport or program). First Long Word (LSLW) bits

31-0 and Second Long Word (MSLW) bits 31-0 indicate the following

values:

o The 48-bit Relative Time Counter that will correspond to the first bit of the AVC/H.264 packet. Bits 31 to 16 in the second long word (MSLW)

will be zero filled; or

o The Absolute Time, if enabled by bit 6 in the Packet Flags(paragraph 10.6.1.1.g). Time format indicated by bits 2 and 3 in the

10-97

7/31/2019 IRIG_106_2009



Packet Flags (paragraph 10.6.1.1.g) and the first bit of the AVC/H.264packet.

10.6.11 Image Packets.

10.6.11.1 Image Packets, Format 0 (Image Data). A Format 0 Image Packet (Figure 10-83)shall contain one or more fixed-length segments of one or more video images. The channelspecific data word for an image packet identifies the number of segments in the packet and the

portion of the image or images contained in the packet. If the optional Intra-Packet Header is not

included with each segment, the Relative Time Counter in the packet header is the time of thefirst segment in the packet.

msb lsb15 0

PACKET HEADER



OPTIONAL INTRA-PACKET HEADER FOR SEGMENT 1 (BITS 15–0)

OPTIONAL INTRA-PACKET HEADER FOR SEGMENT 1 (BITS 31–16)

OPTIONAL INTRA-PACKET HEADER FOR SEGMENT 1 (BITS 47-32)

OPTIONAL INTRA-PACKET HEADER FOR SEGMENT 1 (BITS 63-48)

BYTE 2 BYTE 1

: :


:

OPTIONAL INTRA-PACKET HEADER FOR SEGMENT n (BITS 15–0)

OPTIONAL INTRA-PACKET HEADER FOR SEGMENT n (BITS 31–16)OPTIONAL INTRA-PACKET HEADER FOR SEGMENT n (BITS 47-32)

OPTIONAL INTRA-PACKET HEADER FOR SEGMENT n (BITS 63-48)

BYTE 2 BYTE 1

: :


PACKET TRAILER

Figure 10-83. Image packet, format 0.

a. Image Packet Channel Specific Data Word. The Packet Body portion of each

Image Packet begins with a Channel Specific Data word. It defines the byte

length of each segment and indicates if the Packet Body contains severalcomplete images or partial images, and whether or not the Intra-Packet Data

Header precedes each segment (Figure 10-84).

msb lsb

31 30 29 28 27 26 0

PARTS SUM IPH LENGTH

Figure 10-84. Image packet channel specific data word format.

10-98

7/31/2019 IRIG_106_2009



Parts. (bit 31-30) indicates which piece or pieces of the video frame arecontained in the packet.

00 = Packet does not contains first or last segment of image

01 = Packet contains first segment of image10 = Packet contains last segment of image

11 = Packet contains both first and last segment of image

Sum. (bit 29-28) indicates if the packet contains a partial image, onecomplete image, multiple complete images, or pieces from multiple images.

00 = Packet contains less than one complete image

01 = Packet contains one complete image

10 = Packet contains multiple complete images11 = Packet contains multiple incomplete images

Intra-Packet Header (IPH). (bit 27) indicates whether the Intra-Packet

Header (Time Stamp) precedes each segment of the image.

0 = Intra-Packet Header not enabled1 = Intra-Packet Header enabled

Length. (bits 26-0) indicates a binary value that represents the byte lengthof each segment.

b. Image Intra-Packet Header. After the Channel Specific Data, Format 0 Image

Data is inserted into the packet. Each block of data is optionally preceded by an

Intra-Packet Header as indicated by the IPH bit in the Channel Specific Dataword. When included, the Intra-Packet Header consists of an Intra-Packet TimeStamp only. The length of the Intra-Packet Header is fixed at 8 bytes (64 bits)

positioned contiguously, in the following sequence (Figure 10-85).

msb lsb

31 0

TIME (LSLW)

TIME (MSLW)

Figure 10-85. Image data intra-packet header, format 0.

Intra-Packet Time Stamp. (8 Bytes) indicate the time tag of the Format 0

Image Data. First long word bits 31-0 and second long word bits 31-0indicate the following values:

o The 48-bit Relative Time Counter that corresponds to the first data bit in

the first byte with bits 31 to 16 in the second long word zero filled; or

o The Absolute Time, if enabled by bit 6 in the Packet Flags(paragraph 10.6.1.1.g). Time format corresponds to the time format

10-99

7/31/2019 IRIG_106_2009



indicated by bits 2 and 3 in the Packet Flags (paragraph 10.6.1.1.g) andto the first data bit in the Message.

10.6.11.2 Image Packets, Format 1 (Still Imagery). A Format 1 Image Packet (Figure 10-86)shall contain one or more fixed-length segments of a partial Still Image, one complete Still

Image, or multiple Still Images. The Still Image source can be external or internal to therecorder. The Still Image formats will be specified in the Channel Specific Data Word and in theComputer Generated Data, Format 1 Setup Record for each Still Imagery channel. Only one

format can be contained within each channel ID for Still Imagery.

msb lsb

15 0

PACKET HEADER



INTRA-PACKET HEADER FOR SEGMENT 1 (BITS 15-0)

INTRA-PACKET HEADER FOR SEGMENT 1 (BITS 31-16)INTRA-PACKET HEADER FOR SEGMENT 1 (BITS 47-32)




BYTE 2 BYTE 1

: :


:

INTRA-PACKET HEADER FOR SEGMENT n (BITS 15-0)


INTRA-PACKET HEADER FOR SEGMENT n (BITS 47-32)INTRA-PACKET HEADER FOR SEGMENT n (BITS 63-48)



BYTE 2 BYTE 1

: :


PACKET TRAILER

Figure 10-86. Still Imagery packet, format 1.

10-100

7/31/2019 IRIG_106_2009



a. Still Imagery Packet Channel Specific Data Word. The Packet Body portion of each Still Image Packet begins with a Channel Specific Data word. It defines

the format of the Still Imagery Format (which will coincide with the Still

Imagery format with the Setup Record), and indicates if the Packet Bodycontains several complete images or partial images (Figure 10-87).

msb lsb

31 30 29 28 27 26 23 22 0

PARTS SUM IPH FORMAT RESERVED

Figure 10-87. Still Imagery packet channel specific data word format.

Parts. (bit 31-30) indicates which piece or pieces of the image are containedin the packet.

00 = Packet does not contains first or last segment of image01 = Packet contains first segment of image

10 = Packet contains last segment of image11 = Packet contains both first and last segment of image

Sum. (bit 29-28) indicates if the packet contains a partial image, onecomplete image, multiple complete images, or pieces from multiple images.

00 = Packet contains less than one complete image

01 = Packet contains one complete image

10 = Packet contains multiple complete images11 = Packet contains multiple incomplete images

Intra-Packet Header (IPH). (bit 27) indicates whether the Intra-Packet

Header (Time Stamp) precedes each segment of the image.

0 = Intra-Packet Header not enabled1 = Intra-Packet Header enabled

Format. (bits 26-23) indicates a binary value which represents the Still

Image Format.

0000 = MIL-STD-2500 National Imagery Transmission Format

0001 = JPEG File Interchange Format0010 = JPEG 2000 (ISO/IEC 15444-1)

0011 = Portable Network Graphics Format0100-1111 = Reserved


b. Still Imagery Intra-Packet Header. After the Channel Specific Data, Format 1Still Imagery Data is inserted into the packet. Each still image or segment is

preceded by an Intra-Packet Header. The Intra-Packet Header consists of an

10-101

7/31/2019 IRIG_106_2009



Intra-Packet Time Stamp and Intra-Packet Data. The length of the Intra-PacketHeader is fixed at 12 bytes (96 bits) positioned contiguously, in the following

sequence (Figure 10-88).

msb. lsb

31 0

TIME (LSLW)TIME (MSLW)

INTRA-PACKET DATA

Figure 10-88. Still Imagery intra-packet header.

Intra-Packet Time Stamp. (8 Bytes) indicate the time tag of the Format 1

Still Imagery Data. First long word bits 31-0 and second long word

bits 31-0 indicate the following values:


the still image or segment with bits 31 to 16 in the second long word

zero filled or;o The Absolute Time, if enabled by bit 6 in the Packet Flags

(paragraph 10.6.1.1.g). Time format is indicated by bits 2 and 3 in the

Packet Flags (paragraph 10.6.1.1.g) and the first data bit in the still

image or segment.

Intra-Packet Data. (4 Bytes) indicates a binary value that represents the bytelength of following still image or segment.

10.6.12 UART Data Packets.

10.6.12.1 UART Data Packets, Format 0. The data from one or more separate asynchronous

serial communication interface channels (RS-232, RS-422, RS-485, etc…) can be placed into aUART Data Packet as shown in Figure 10-89.

10-102

7/31/2019 IRIG_106_2009



msb lsb

15 0

PACKET HEADER CHANNEL SPECIFIC DATA (BITS 15-0) CHANNEL SPECIFIC DATA (BITS 31-16)

(OPTIONAL) INTRA-PACKET TIME STAMP FOR UART 1 (BITS 15–0) (OPTIONAL) INTRA-PACKET TIME STAMP FOR UART 1 (BITS 31–16) (OPTIONAL) INTRA-PACKET TIME STAMP FOR UART 1 (BITS 47-32) (OPTIONAL) INTRA-PACKET TIME STAMP FOR UART 1 (BITS 63-48)

INTRA-PACKET DATA HEADER (UART ID) for UART 1 (BITS 15-0) INTRA-PACKET DATA HEADER (UART ID) for UART 1 (BITS 31-16)

BYTE 2 BYTE 1 : :

FILLER (IF n IS ODD) BYTE n :

(OPTIONAL) INTRA-PACKET TIME STAMP FOR UART n (BITS 15–0)

(OPTIONAL) INTRA-PACKET TIME STAMP FOR UART n (BITS 31–16) (OPTIONAL) INTRA-PACKET TIME STAMP FOR UART n (BITS 47-32) (OPTIONAL) INTRA-PACKET TIME STAMP FOR UART n (BITS 63-48)

INTRA-PACKET DATA HEADER (UART ID) for UART n (BITS 15-0) INTRA-PACKET DATA HEADER (UART ID) for UART n (BITS 31-16)

BYTE 2 BYTE 1 : :

FILLER (IF n IS ODD) BYTE n PACKET TRAILER

Figure 10-89. UART data packet format.

a. UART Packet Channel Specific Data Word. The Packet Body portion of each

UART Data Packet begins with a Channel Specific Data word as shown in

Figure 10-90.

msb lsb31 30 0

IPH RESERVED

Figure 10-90. UART packet channel specific data word format.

Intra-Packet Header (IPH). (bit 31) indicates whether the Intra-PacketHeader Time Stamp is inserted before the UART ID words.

0 = Intra-Packet Header Time Stamp not enabled

1 = Intra-Packet Header Time Stamp enabled


b. UART Intra-Packet Header. After the Channel Specific Data, UART data is

inserted into the packet. Each block of data shall be preceded by an Intra-Packet Header with optional Intra-Packet Time Stamp and a mandatory UART

10-103

7/31/2019 IRIG_106_2009



ID WORD Intra-Packet Data Header. The length of the Intra-Packet Header iseither 4 bytes (32 bits) or 12 bytes (96 bits) positioned contiguously, in the

following sequence (Figure 10-91).

msb lsb

31 0TIME (LSLW)

TIME (MSLW)

UART ID WORD

Figure 10-91. UART data intra-packet header.

UART Intra-Packet Time Stamp. (8 Bytes) indicate the time tag of the

UART Data. First long word bits 31-0 and second long word bits 31-0indicate the following values:


the first byte with bits 31 to 16 in the second long word zero filled; or


Packet Flags (paragraph 10.6.1.1.g) and the first data bit in the Message.

UART Intra-Packet Data Header. The Intra-Packet Data Header is anidentification word (UART ID Word) that precedes the data and is inserted

into the packet with the following format. Inclusion of the Intra-Packet DataHeader is mandatory and is not controlled by the IPH bit in the Channel

Specific Data Word. (Figure 10-92).

msb lsb

31 30 29 16 15 0PE RESERVED SUBCHANNEL DATA LENGTH


o Parity Error (PE). (bit 31) indicates a Parity Error.

0 = No Parity Error1 = Parity Error

o Reserved. (bit 30) is reserved.

o Subchannel. (bits 29-16) indicates a binary value defining the

subchannel number belonging to the data that follows the UART IDWord when the Channel ID in the packet header defines a group of

subchannels. Zero means first and/or only subchannel into which the

Intra-Packet Data Header is inserted before the UART ID words.

o Data Length. (bits 15-0) indicate a binary value representing the lengthof the UART data in bytes (n) that follows the UART ID word.

10-104

7/31/2019 IRIG_106_2009



10.6.13 IEEE-1394 Data Packets.

10.6.13.1 IEEE-1394 Data Packets, Format 0 (IEEE-1394 Transaction). This format applies

to IEEE-1394 data as described by IEEE 1394-1995, IEEE 1394a, and IEEE 1394b. IEEE-1394data is packetized to encapsulate completed transactions between nodes. A packet may contain 0

to 65,536 transactions, but is constrained by the common packet elements size limits prescribedin paragraph 10.6.1. IEEE-1394 packets have the basic structure shown in Figure 10-93. Notethat the width of the structure is not related to any number of bits. The figure merely represents

relative placement of data within the packet.

PACKET HEADER

CHANNEL SPECIFIC DATA WORD


(Optional) TRANSACTION DATA


(Optional) TRANSACTION DATA:


(Optional) TRANSACTION DATA

PACKET TRAILER

Figure 10-93. IEEE-1394 data packet, format 0.

a. IEEE-1394 Channel Specific Data Word. The packet body portion

(Figure 10-94) of each IEEE-1394 packet shall begin with a Channel Specific

Data Word.

msb lsb31 29 28 25 24 16 15 0

PBT SY RESERVED TC

Figure 10-94. IEEE-1394 channel specific data word.

Packet Body Type (PBT). (bits 31-29) indicate the packet body type asfollows:

000 = Type 0

001 = Type 1

010 = Type 2011 = Reserved

1xx = Reserved

Synchronization Code (SY). (bits 28-25) indicate the IEEE-1394

Synchronization Code from the transaction. This field is mandatory forType 1 packet bodies. Otherwise, it is reserved.


10-105

7/31/2019 IRIG_106_2009



Transaction Count (TC). (bits 15-0) indicate the binary value of the numberof transactions encapsulated in the packet. An integral number of complete

transactions shall be included in each packet. It is mandatory that

Transaction Count be 0 for Type 0 packet bodies and 1 for Type 1 packet

bodies.

b. IEEE-1394 Intra-Packet Header. Each Intra-Packet Header shall contain an 8

byte Intra-Packet Time Stamp only. The format of a IEEE-1394 Intra-PacketHeader is described by Figure 10-95.

msb lsb

31 0

INTRA-PACKET TIME STAMP


Figure 10-95. IEEE-1394 intra-packet header.

IEEE-1394 Intra-Packet Time Stamp. This frame (8 Bytes) indicates thetime tag of the IEEE-1394 transaction that immediately follows it in the

packet. Time is coded in accordance with all other Chapter 10 packet

formats. Specifically, the first long word bits 31-0 and second long wordbits 31-0 indicate the following values:

o The 48-bit Relative Time Counter that corresponds to the first data bit of

the transaction, with bits 31-16 in the second long word zero filled; or


Packet Flags (paragraph 10.6.1.1.g) and the first data bit of the

transaction.

c. IEEE-1394 Data Packet Body Types. Three packet body types are defined for

the encapsulation of IEEE-1394 data. Regardless of type, each packet body

shall begin with the IEEE-1394 Packet Channel Specific Data Word asdescribed by paragraph 10.6.13.1a above. The packet body type is indicated

within the Channel Specific Data Word. Depending on the packet body type,

the Channel Specific Data Word is followed by 0 or more transactions. Also,dependent on packet body type, each transaction may be preceded by an Intra-

Packet Header.

IEEE-1394 Packet Body Type 0: Bus Status. Type 0 packet bodies shallcontain zero Intra-Packet Headers and zero transactions. The Channel

Specific Data Word Transaction Count shall be zero. The packet body shall

contain the Channel Specific Data Word immediately followed by a single

32-bit word.

10-106

7/31/2019 IRIG_106_2009



Bus Status events shall be encapsulated by Type 0 packet bodies. The32-bit word in the packet body shall contain an Event Data Word as

indicated in Figure 10-96:

10-107

7/31/2019 IRIG_106_2009



msb lsb

31 30 0

RE RESERVED

Figure 10-96. IEEE-1394 event data word format.

o RE. (bit 31) RESET - when set, this bit indicates that an IEEE-1394

Bus Reset has occurred.

o RESERVED. (bits 30-0) Reserved.

IEEE-1394 Packet Body Type 1: Data streaming. Type 1 packet bodies

shall encapsulate IEEE-1394 data streaming only. Type 1 packet body datais restricted to that from an IEEE-1394 packet with a Transaction Code of

0xA, be it from an Isochronous Channel or Asynchronous Stream. The

packet body shall contain zero Intra-Packet Headers and one transaction.The Channel Specific Data Word Transaction Count shall be one.

The Channel Specific Data Word is immediately followed by a non-zeronumber of data bytes. The data bytes shall be exactly those of a single

IEEE-1394 data block, excluding the IEEE-1394 packet header and Data

Block CRC. Data recorded from the stream shall be known to be valid,insofar as, both the IEEE-1394 Header CRC and Data Block CRC tests have

passed. In accordance with the definition of Packet Header Data Length,

and accounting for the size of the Channel Specific Data Word, the number

of data bytes shall be exactly four less than the value indicated in DataLength. Conversely, the value stored in the Packet Header Data Length

shall be the number of bytes in the IEEE-1394 data block plus four. The

Synchronization Code (sy) from the stream packet shall be indicated in theChannel Specific Data Word, and the Channel Number shall be indicated in

the Packet Header Channel ID.

IEEE-1394 Packet Body Type 2: General Purpose. Type 2 packet bodiesencapsulate complete IEEE-1394 packets, including header and data. Use

of Type 2 packet bodies is unrestricted and may encapsulate streaming, non-

streaming (IEEE-1394 packets with Transaction Codes other than 0xA),isochronous, and asynchronous data. Multiple IEEE-1394 packets, with

differing Transaction Codes and Channel Numbers, may be carried within a

single Type 2 packet body.

The Channel Specific Data Word shall be followed by a non-zero

number of completed transactions as indicated by the Channel Specific Data

Word Transaction Count. Each transaction shall be preceded by an Intra-Packet Header as defined above for IEEE-1394 Data Packets. Immediately

following the Intra-Packet Header, the transaction shall be recorded in its

entirety and must be a properly formed IEEE-1394 packet in accordance

10-108

7/31/2019 IRIG_106_2009



with the specification in use. The revision of the specification used shall bedeclared within the accompanying Setup Record packet.

All IEEE-1394 packets contain a 4-bit Transaction Code field (tcode).This field indicates the IEEE-1394 specific format of the transaction.

10.6.13.2 IEEE-1394 Data Packets, Format 1 (IEEE-1394 Physical Layer). This format

applies to IEEE-1394 data as described by IEEE 1394-1995, IEEE 1394a, and IEEE 1394b.

IEEE-1394 data is packetized in Format 1 packets as physical Layer data transfers (IAW AnnexJ of Standard 1394-1995 and Chapter 17 of Standard 1394b-2002). A packet may contain 0 to

65,536 transfers, but is constrained by the common packet elements size limits prescribed in

paragraph 10.6.1. IEEE-1394 packets have the basic structure shown in Figure 10-97 below.Note that the width of the structure is not related to any number of bits. The drawing merely

represents relative placement of data within the packet.

PACKET HEADER

CHANNEL SPECIFIC DATA WORD

INTRA-PACKET HEADER

DATA


(Optional) DATA

:


(Optional) DATA

PACKET TRAILERFigure 10-97. IEEE-1394 data packet, format 1.

a. IEEE-1394 Channel Specific Data Word. The packet body portion

(Figure 10-98) of each IEEE-1394 packet shall begin with a Channel Specific

Data Word.

msB lsb31 16 15 0

RESERVED IPC

Figure 10-98. IEEE-1394 channel specific data word format 1.


Intra-Packet Count (IPC). (bits 15-0) indicate the binary value of the

number of Intra-Packets encapsulated in the packet. An integral number of complete Intra-Packets shall be included in each packet.

10-109

7/31/2019 IRIG_106_2009



b. IEEE-1394 Format 1 Intra-Packet Header. The Channel Specific Data Word isfollowed by 1 or more IEEE-1394 transfers. Each transfer starts with an Intra-

Packet Header, followed by 0-32780 encapsulated data bytes. The length of the

Intra-Packet Header is fixed at 12 bytes (96 bits) positioned contiguously, in thefollowing sequence as shown in Figure 10-99:

msb lsb

31 0



INTRA-PACKET ID WORD

Figure 10-99. IEEE-1394 format 1 intra-packet header.

IEEE-1394 Format 1 Intra-Packet Time Stamp. This frame (8 Bytes)

indicates the time tag of the IEEE-1394 transfer that immediately follows itin the packet. Time is coded in accordance with all other Chapter 10 packet

formats. Specifically, the first long word bits 31-0 and second long wordbits 31-0 indicate the following values:

o The Relative Time Counter that corresponds to the first data byte of thetransfer, with bits 15-0 in the second long word zero filled or;

o Time, if enabled by bit 6 in the Packet Flags (paragraph 10.6.1.1.g).

Time format is indicated by bits 2 and 3 in the Packet Flags(paragraph 10.6.1.1.g) and the first data byte of the transfer.

Message ID Word. The Message ID Word is an identification word that

precedes the message and is inserted into the packet as in Figure 10-100.

msb lsb

31 24 23 20 19 18 17 16 15 0

STATUS BYTE SPEED TRFOVF LBO RSV DATA LENGTH

Figure 10-100. Intra-packet data header - message ID word.

o Status Byte. (bits 31-24) This byte is the status byte received from the

PHY IAW IEEE-1394b Specification.

o Transmission Speed (SPEED). (bits 23-20) This field identifies thespeed of transmission of the message. (Speed codes IAW IEEE-1394b)

0000 = S100 A

0001 = S100 B

0010 = S200 A0011 = S200 B

0100 = S400 A

0101 = S400 B0111 = S800 B

1001 = S1600 B

1010 = S3200 Bother values are reserved

10-110

7/31/2019 IRIG_106_2009



o Transfer Overflow Error (TRFOVF). (bit 19-18) This field indicates if a transfer synchronization error occurred.

00 = IEEE1394 flow did not exceed maximum Intra-packet size01 = IEEE1394 This IEEE1394 transfer started correctly but

longer than the standard transfer length.10 = The previous IEEE1394 transfer was in “01” type overflowand this IEEE1394 transfer ended correctly (did not exceed

standard transfer length).

11 = The previous IEEE1394 transfer was in “01” type overflow

and this IEEE1394 transfer did not end correctly (exceedsstandard transfer length).

Most of the time, this field shall be “00.” Possible combinations are:“01”intra-packet, zero or more; ‘11”intra-packet; and finally “10”intra-

packet.

o LBO. (bits 17) Local Buffer Overflow. If this bit is set, some messages

are lost before this transfer due to local buffer overflow.


o Data Length. (bits 15-0) contain a binary value that represents thelength of the transfer in bytes (n) that follows the ID Word. The

maximum length of a captured data is 4120 for transfers corresponding

to asynchronous packets, and 32780 for transfers corresponding toisochronous packets.

If the Data Length field is not a multiple of 4 bytes, 1-3 fill

character (0) is added to maintain the packet structures in 32-bit

boundary.

If the Data Length field contains 0, the Intra-Packet Data is not

provided and this word contains only the status byte information.

c. IEEE-1394 Format 1 Packet Body. The packet body shall encapsulate IEEE-

1394 isochronous or asynchronous message data. The data bytes shall be

exactly those of a single IEEE-1394 physical transmission message, includingthe IEEE-1394 packet header and Data Block CRC. The Data Length field shall

indicate the exact number of total bytes encapsulated in the Message Data.

10-111

7/31/2019 IRIG_106_2009



10.6.14 Parallel Data Packets.

10.6.14.1 Parallel Data Packet, Format 0. Parallel data packets are designed to record datafrom parallel interfaces (2-128 bit wide) including the industry de facto standard 8-bit DCRsi

interface. A single packet can hold data words or special data structures as currently defined for

the DCRsi scan format. The exact format selection is defined in the Channel Specific DataWord. The data recorded from a parallel interface shall be placed into a Parallel Data PacketFormat 0 as shown in Figure 10-101.

msb lsb15 0

PACKET HEADER



DATA WORD 1

:DATA WORD n

PACKET TRAILER

Figure 10-101. Parallel data packet, format 0.

a. Parallel Packet Channel Specific Data Word. The Packet Body portion of each

Parallel Data Packet begins with a Channel Specific Data word. The ChannelSpecific Data word is formatted as shown in Figure 10-102.

msb lsb

31 24 23 0

TYPE RESERVED (0) OR SCAN NUMBERFigure 10-102. Parallel packet channel specific data word format.

Type. (bits 31-24) indicate the data type stored0-1: Reserved

2-128: Number of bits of recorded data (parallel data word width in bits)

129-253: Reserved254: DCRsi scan format, contains auxiliary data, DCRsi main data

255: Reserved

Scan Number. (bits 23-0) is reserved (0) for general purpose parallel datapackets or contains the scan number of the first scan stored in the packet for

DCRsi data.

b. General Purpose Parallel Data. General purpose parallel data packets can

contain any number of data bytes – as indicated in the Data Length field in thePacket Headers (Figure 10-103).

10-112

7/31/2019 IRIG_106_2009



To get the number of data words stored in the packet, the Data Length

must be divided by the number of bytes necessary to hold one Parallel

Data word.

If the number of data bits is less than 9 bits, the word shall be padded to

8-bit bytes.

msb lsb15 0PAD (0) WORD 2 PAD (0) WORD 1

: :

PAD (0) WORD N, or

PAD (0) IF LENGTH IS ODD PAD (0) WORD N-1

Figure 10-103. Parallel data, up to 8-bit wide words.

If the number of data bits is between 9 and 16, the words shall be padded toone 16-bit word, as in Figure 10-104.

msb lsb

15 0

PAD (0) DATA WORD 1

:

PAD (0) DATA WORD N

Figure 10-104. Parallel data, 9-16 bit wide words.

If the number of data bits is greater than 16 the words shall be padded to

multiples of 16-bit data words. Figure 10-105 shows storing of 28-bit datawords.

msb lsb

15 0

DATA WORD1, LS BITS 15-0

PAD (0) DATA WORD 1, MS BITS 27-16

:

DATA WORD N, LS BITS 15-0

PAD (0) DATA WORD N, MS BITS 27-16

Figure 10-105. Parallel data, (Example: 28-bit wide words).

10-113

7/31/2019 IRIG_106_2009



c. DCRsi Parallel Data Packets. The DCRsi data packets can contain any numberof complete DCRsi Scans – containing nine auxiliary data and 4356 main data

bytes. The number of the scans can be calculated from the Data Length field of

the Packet Header. The structure of one DCRsi scan is in Figure 10-106.

msb lsb15 0

AUXILIARY DATA 2 AUXILIARY DATA 1

PAD (0) AUXILIARY DATA 3





DATA BYTE 2 DATA BYTE 1

DATA BYTE 4 DATA BYTE 3

: :

DATA BYTE 4356 DATA BYTE 4355Figure 10-106. DCRsi Scan, 9-auxiliary data byte +4356 bytes.

The length of the packet can be only N * (12 + 4356) + 4 bytes, including

the length of the Channel Specific data word.

DCRsi data without auxiliary data bytes can be stored also as 8-bit General

Purpose Parallel Data as described in paragraph 10.6.15.1b (General Purpose

Parallel Data).

10.6.15 Ethernet Data Packets.

10.6.15.1 Ethernet Data Packets, Format 0. Data from one or more Ethernet network interfaces can be placed into an Ethernet Data Packet Format 0 as shown in Figure 10-107.

10-114

7/31/2019 IRIG_106_2009



msb lsb

15 0

PACKET HEADER









BYTE 2 BYTE 1

: :FILLER (IF n IS ODD) BYTE n

:





INTRA-PACKET DATA HEADER FOR MSG n (BITS 15-0)

INTRA-PACKET DATA HEADER FOR MSG n (BITS 31-16)

BYTE 2 BYTE 1: :


PACKET TRAILER

Figure 10-107. Ethernet Data packet format 1.

10-115

7/31/2019 IRIG_106_2009



a. Ethernet Data Packet Format 0, Channel Specific Data Word. The Packet Bodyportion of each Ethernet Data Packet begins with a Channel Specific Data word.

It indicates how many Physical Ethernet messages (MAC Frame) are placed in

the Packet Body. The Channel Specific Data word is formatted for thecomplete type of packet body as shown in Figure 10-108.

msb lsb

31 28 27 16 15 0

FORMAT RESERVED NUMBER OF FRAMES

Figure 10-108. Ethernet Data packet format 1 channel specific data word.

Format. (bits 31-28) indicate the type of Ethernet Packet.

0000 = Ethernet Physical Layer IEEE-802.3

0001 - 1111 = Reserved

Reserved. (bits 27-16) are reserved. Number of Frames. (bits 15-0) contain a binary value that represents the

number of frames included in the packet.

b. Ethernet Data Packet Format 0 Intra-Packet Header. After the Channel Specific

Data, Ethernet Data is inserted into the packet. Each Frame is preceded by an

Intra-Packet Header that has both an Intra-Packet Time Stamp and an Intra-Packet Data Header containing a Frame ID Word. The length of the Intra-

Packet Header is fixed at 12 bytes (96 bits) positioned contiguously, in the

following sequence as shown in Figure 10-109.

msb lsb31 0

TIME (LSLW)

TIME (MSLW)

FRAME ID WORD

Figure 10-109. Ethernet Data format 1 intra-packet header.

Intra-Packet Time Stamp. (8 Bytes) indicate the time tag of the Frame Data.

First long word bits 31-0 and second long word bits 31-0 indicate thefollowing values:

o The 48-bit Relative Time Counter that corresponds to the first data bit inthe Frame with bits 31 to 16 in the second long word zero filled or;


Packet Flags (paragraph 10.6.1.1.g) and the first data bit in the Frame.

10-116

7/31/2019 IRIG_106_2009



Frame ID Word. The Frame ID Word is an identification word that

precedes the Ethernet frame and is inserted into the packet with the formatshown in Figure 10-110.

msb lsb

31 30 29 28 27 24 23 16 15 14 13 0

RESERVED FE CONTENT SPEED NET ID RESERVED DATA LENGTH

Figure 10-110. Intra-packet frame ID word.


o Frame Error (FE). (bit 30). The Frame Error bit is used to indicate anyerror that occurred during frame transmission.

0 = No Frame Error

1 = Frame Error encountered

o Captured Data Content (CONTENT). (bits 29-28). This field specifies

the extent of the captured MAC Frame.

00 = Full MAC Frame: starting with the 6-byte Destination MACaddress and ending with the 4-byte Frame Check Sequence

01-11 = Reserved for further formats

o Ethernet Speed (SPEED). (bits 27-24). This field indicates the

negotiated bit rate for the identified NETID on which the frame wascaptured.

0000 = Auto

0001 = 10 Mbit/s0010 = 100 Mbit/s

0011 = 1 Gbit/s

0100 = 10 Gbit/s

o Network Identifier (NETID). (bits 23-16) contain a binary value whichrepresents the physical network identification of frame origination that

follows the ID Word. Zero means first and/or only physical network.


o Data Length. (bits 13-0) contain a binary value that represents the

length of the frame in bytes (n) that follows the ID Word.

10.7 Recorder Control and Status

10.7.1 Recorder Control. The recorder shall be controlled by either discrete control/status

lines and/or serial communication ports. The serial interface shall consist of both RS-232 and

RS-422 full duplex serial communications.

10.7.1.1 Optional Recorder Control. The recorder may be controlled over the Fibre

Channel, IEEE-1394B, or Ethernet recorder download interface ports from paragraph 10.4.These interfaces shall support communications using SCSI (Fibre Channel) IAW paragraph

10.4.1, SCSI over SBP-2 (IEEE-1394B) IAW 10.4.2, or iSCSI(Ethernet) IAW paragraph 10.4.3

Recorder login and IRIG-106 Chapter 6 Command and Control Mnemonics shall be transmitted

10-117

7/31/2019 IRIG_106_2009



and received using the SCSI ORB structures IAW paragraphs 10.9.3 (as required for IEEE-1394B), 10.9.4, and 10.9.14.

10.7.1.2 Optional TELNET Control. The recorder may be controlled over ETHERNET/

TELNET utilizing recorder control mnemonics as defined in IRIG 106 Chapter 6.

10.7.2 Communication Ports. The RS-232 and RS-422 serial communication ports shall be

functional simultaneously without requiring selection of either port. Status requested by either

port shall be returned on both ports. Note that unexpected results may occur if commands areissued on both ports simultaneously.

10.7.3 RS-232/422 Port. An RS-232/422 port shall be available at the Download Port.

10.7.4 Commands. Commands received through the serial communication ports shall not

override hardwire discrete controls.

10.7.5 Status Requests. Status requests received through the serial communication ports

shall not interfere with hardwire controls.

10.7.6 Serial Status. Serial status shall be provided on either serial status request or discrete

activation.

10.7.7 Default Interface. Default Interface with user equipment shall utilize the following

ASCII serial communication protocol:

a. 38400 baud.

b. One start bit.c. 8 bit data.

d. No parity.e. One stop bit.

10.7.8 Serial Commands. The following commands are a subset of the Recorder Commandand Control Mnemonics defined in IRIG Standard 106 Chapter 6, paragraph 8, where additional

rules regarding command syntax and recorder operation are also specified, along with examples

showing the use of each command. The commands are simple ASCII command strings

delimited by spaces. All commands begin with an ASCII period (.””) and, with the singleexception of the .TMATS command, end with a carriage return and line-feed terminator

sequence.

Case Sensitivity. Commands will not be case sensitive except for location

parameter in .PLAY and file name in .RECORD.

10-118

7/31/2019 IRIG_106_2009



10.7.9 Serial Commands. Table 10-9 summarizes the required commands.

TABLE 10-9. COMMAND SUMMARY


.ASSIGN [destination-ID] [source-ID] Assign replay (output) channels to source (input)channels

.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

.DUB [location] Same as .PLAY but with internal clock

.ERASE Erases the recording media

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

.FILES Displays information about each recorded file

.FIND [value [mode] ] Display current locations or find new play point

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

.HELP Displays table of "dot" commands

.IRIG-106 Returns supported version number of IRIG-106

Recorder Command and Control Mnemonics .LOOP Starts record and play in read-after-write mode

.MEDIA Displays media usage summary

.MOUNT Powers and enables the recording media

.PAUSE Pause current replay

.PLAY [location][speed] Reproduce recorded data of assigned output channelsstarting at [location] and at [speed]

.PUBLISH [keyword] [parameter] Configure, start and stop live data over the recorder

Ethernet interface .RECORD [ filename] Starts a recording at the current end of data .REPLAY [endpoint [mode] ] Same as .SHUTTLE but with internal clock .RESET Perform software initiated system reset

.RESUME Resume replay from pause condition

.SETUP [n] Displays or selects 1 of 16 (0…15) pre-programmed

data recording formats

.SHUTTLE [endpoint [mode] ] Play data repeatedly from current location to the

specified endpoint location using external clock

.STATUS Displays the current system status

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


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

* Parameters in braces “{}” are required. Parameters in brackets “[]” are optional. When optional

parameters are nested (“[xxx [yy] ]”), the outer parameter (xxx) must be specified in order to also specify

the inner parameter (yy).

10-119

7/31/2019 IRIG_106_2009



10.7.10 Required Discrete Control Functions. Required discrete control functions are notedin Figure 10-111.

Description

RECORD

ERASEDECLASSIFY

ENABLE

BIT

Figure 10-111. Required discrete control functions.

a. Control and Status Lines. Five contacts for discrete control and five lines forindicating status shall be provided. Grounding a control line (or causing the

indicator line to go to ground) referenced to the recorders ground completes

the circuit to activate a function as shown in Figure 10-112.

RECORD

BIT

ERASE

DECLASSIFY

ENABLE

DECLASSIFY INDICATION

ERASE IND

BIT IND

FAULT IND

RECORD IND28 VDC SSR

Figure 10-112. Discrete control and indicator functional diagram.

b. Record Command. Activated by toggle switch (Normally closed position 0.55Volts or less), this discrete commands the recorder to start recording.

Recorder will remain in this mode until such time as the switch is set tonormally open position.

c. Erase Command. Activated by momentary switch (0.55 Volts or less,minimum duration of 100 ms), this discrete commands the recorder to erase

its user data and file directory memory provided the enable switch is also

activated.

10-120

7/31/2019 IRIG_106_2009



d. Declassify Command. Activated by momentary switch (0.55 Volts or less,minimum duration of 100 ms), this discrete causes the recorder to start the

declassify procedure provided the enable switch is also activated.

e. Command Enable. Activated by momentary switch (0.55 volts or less) for

either ERASE or DECLASSIFY discrete to operate.

f. Bit Command. Activated by momentary switch (0.55 Volts or less), thisdiscrete commands the recorder to start the BIT procedure.

g. Record Status. A Record indication (ON) shall be active low 0.55 volts or

less. A Non-Record indication (OFF) will be an open circuit. Current limit of

60 milliamps required.

h. BIT Status. A BIT indication (ON) shall be 0.55 volts or less. A Non-BIT

indication (OFF) will be an open circuit. Current limit of 60 milliamps

required.

i. Fault Status. A Fault indication (ON) shall be 0.55 volts or less. A Non-Fault

indication (OFF) will be an open circuit. Current limit of 60 milliampsrequired.

j. Erase Status. An Erase indication (ON) shall be 0.55 volts or less. A Non-

Erase indication (OFF) will be an open circuit. Current limit of 60 milliampsrequired.

k. Declassify Status. A Declassify indication (ON) shall be 0.55 volts or less. A

Non-Declassify indication (OFF) will be an open circuit. No discrete control

line shall be available at the Download port. Current limit of 60 milliampsrequired.

10.7.11 Voltage. 28-VDC auxiliary voltage output shall be provided from thediscrete/control port (250 mA max, short circuit protection).

10.7.12 Status Query. Status querying shall be limited to intervals not to exceed 2

seconds and not less than one second.

10.7.13 Erase Command. Activated by momentary switch (.55 Volts or less, minimumduration for 100 milliseconds, if ENABLE discrete is also activated for 100 milliseconds), this

discrete commands the recorder to erase its user data and file directory memory provided the

enable switch is also activated.

10.7.14 Declassify Command. Activated by momentary switch (0.55 Volts or less,

minimum duration of 100 milliseconds, if ENABLE discrete is also activated for 100milliseconds) this discrete commands the recorder to start the declassify procedure provided the

enable switch is also activated.

10.7.15 Command Enable. Activated by a momentary switch (0.55 Volts or less forminimum duration of 100 milliseconds) for either ERASE or DECLASSIFY discrete to operate.

In order to activate the ERASE OR DECLASSIFY, the ENABLE and ERASE OR

10-121

7/31/2019 IRIG_106_2009



DECLASSIFY must simultaneously be active for a minimum duration of 100 milliseconds.Table 10-10 presents the Recorder LED states.

TABLE 10-10. RECORDER LED STATES

LED On Flash Off

ERASE Media erased.Media erasing is in

progress.Not erased media.

RECORD In recording - Not in recording

FAULT

Recorder is not ready,

or any of the criticalwarning exists.

-

Recording is running

properly. No criticalwarning.

BIT Built-in test running. -Built-in test is notrunning.

DECLASSIFY Media declassified.Media declassification

is in progress.

Not declassified media.

Note: Flashing is defined as On: 500 ms, Off: 500 ms

10.8 Declassification

Associated Documents such as NSA-130-2, DOD 5200.28 (1972), and DCI-116

historically covered declassification guidelines/requirements. These documents focused on

declassification of standard disk and other conventional memory technologies. Declassificationis the determination by an authorized official that classified information no longer requires, in

the interest of national security, any degree of protection against unauthorized disclosure. This

standard provides for the minimum set of commands that may be utilized to allow for user

declassification of Solid State Media residing in an RMM. The Solid State Media may consist of

COTS Solid State Disks (SSD) or a memory configuration unique to the manufacturer. Thereare several approaches for declassification. The responsibility for ensuring that a proper

declassification process has been effectively implemented will reside ultimately with theuser/customer/program manager.

10.8.1 Approach. The following approaches for declassification are currently recommended.

The risk that proper declassification has been effectively implemented will reside ultimately with

the user/customer/program manager. It is believed that the user is the most qualified to

determine the declassification procedures for any program situation. It is the user’sresponsibility to correctly apply the guidelines to the program in each location to optimize the

cost/effect while providing appropriate protection for the data. The guidelines are planned to be

available on the Internet at Defense Link.

10.8.2 Algorithm. The algorithm to erase secure data is described below. During the secure

erase procedure, all blocks of memory shall be processed. No block in memory shall beexcluded from secure erase processing for any reason.

a. First Erase. Every memory block on the board is erased. Any erase failuresreported by memory chips will result in the corresponding chip/block being

10-122

7/31/2019 IRIG_106_2009



declared a bad block. In the event this bad block is not already in thecorresponding board’s bad block table, a new bad block entry will be appended

onto the board’s bad block table. Note that this new entry will not have the

Secure Erase flag set.

b. First Write (0x55). Every memory chip location is recorded with the pattern

0x55. As each location is written, the data is read back to guarantee that all bitswere written to the expected pattern. Any write failures reported by the chips,

or any data errors will result in the corresponding chip/block being declared abad block. In the event this bad block is not already in the corresponding

board’s bad block table, a new bad block entry will be appended onto the

board’s bad block table. Note that this new entry will not have the Secure Eraseflag set.

c. Second Erase. Every memory chip shall be erased. Any erase failures reported

by the memory chips will result in the corresponding chip/block being declared

a bad block. In the event this bad block is not already in the correspondingboard’s bad block table, a new bad block entry will be appended onto the

board’s bad block table. Note that this new entry will not have the Secure Erase

flag set.

d. Second Write (0xAA). Every memory chip location is recorded with the pattern0xAA. As each location is written, the data is read back to guarantee that all

bits were written to the expected pattern. Any write failures reported by the

memory chips, or any data errors will result in the corresponding chip/block

being declared a bad block. In the event this bad block is not already in thecorresponding board’s bad block table, a new bad block entry will be appended

onto the board’s bad block table. Note that this new entry will not have the

Secure Erase flag set.

e. Third Erase. Every memory location is erased. Any erase failures reported bythe memory chips will result in the corresponding chip/block being declared a

bad block. In the event this bad block is not already in the correspondingboard’s bad block table, a new bad block entry will be appended onto the

board’s bad block table. Note that this new entry will not have the Secure Erase

flag set.

f. Usable Secure Erased Blocks. All blocks that do not have an entry in the badblock table are now considered to be Secure Erased.

g. Unusable Secure Erased Blocks. If a bad block entry contains the flag

indicating it has already been Secure Erased, this block has already been secure

erased and requires no further processing, since it is known that this block wasskipped during the previous recording.

h. Unsecure Bad Block Processing. A board’s bad block table may contain bad

block entries that have not previously been Secure Erased. If any such entries

exist, the following steps are performed on each block.

Write Zeros Loop. For each page in the block, a pattern of all zeros is

written to the page, and the page is checked to determine if any unexpected

10-123

7/31/2019 IRIG_106_2009



ones (UOs) are found. If any UOs are found, the page is re-written to allzeros. This process is repeated up to 16 times. After all allowed re-writes,

the board, chip, and block numbers of the block containing any remaining

UOs are written to a Failed Erase Table.

Write Ones Loop. For each page in the block, the page is erased (to all

ones) and checked to determine if any unexpected zeros (UZs) are found. If any UZs are found, another erase command is issued to the block. This

process is repeated up to 16 times. After all allowed erase operations, the

board, chip, and block numbers of the block containing any remaining UZsare written to the Failed Erase Table.

i. Failed Erase Table Processing. Any remaining entries in the Failed Erase Table

correspond to blocks that cannot be erased. These blocks may still contain user

data and therefore are declared to have failed the secure erase.

A count of the number of bad blocks in the Failed Erase Table that have not

been Secure Erased is returned as part of the secure erase results. A non-zerocount indicates a secure erase failure of at least one block. A command will

allow the user to retrieve the Failed Erase Table. A command will also allow a

user to retrieve the data from such blocks and manually determine if theseblocks can be designated as “Secure Erased.” In most cases, a single stuck bit

will not compromise any user data and the offending block can be manually

declared to be Secure Erased. If the results of manual inspection are

indeterminate, the chip containing the failed block must be removed anddestroyed, and the Secure Erase procedure must be repeated.

j. Secure Erase Completion. When all blocks are secure erased (no entries in the

Failed Erase Table), the content of the file is the ASCII string “Secure Erase”

repeated over and over.

10.9 IEEE 1394B Interface to Recorder Media

This interface definition specifies the interface between the removable media and the host

platform as IEEE 1394B. The selection of this protocol was adopted to facilitate a commoninterface between the media and the computing platform.

This definition does not mandate the interface between the recorder and

media.

10.9.1 Media Time Synchronization. In order to allow recorders to be synchronized to the sametime without requiring platform modification or external time source provided to recorder, the

Removable Media Cartridges shall maintain time allowing for time initialization of recorder.Removable media cartridges shall allow for a battery back-up real time clock device.

Initialization of time shall be accomplished via IEEE-1394B interface.

10-124

7/31/2019 IRIG_106_2009



10.9.2 Physical and Signaling. The interface shall allow control of Vendor Specific Solid Statedevices and Commercial Off The Shelf (COTS) Media as per Figure 10-113.

REMOVABLE MEDIA

NODE

UNIT UNIT

SCSI SCSI

Processor Device Vendor Device

“RT” “SS”

Link

PHY

Figure 10-113. Removable media.

10.9.3 Removable Media Communication. The fundamental method of communicating shall bein accordance to the IEEE 1394b protocol. Packets sent and received shall be asynchronous

transmissions. IEEE-1394b packets shall encapsulate Serial Bus Protocol (SBP-2) formatted

packets for the transport of commands and data. Removable media devices are to use SCSIcommand set(s) and therefore SCSI commands and status shall be encapsulated in SBP-2

Operation Request Blocks (ORB).

SBP-2 provides for the transport of 6-10- and 12-byte SCSI Common

Descriptor Blocks within a command ORB.

10.9.4 Transport of Serial Commands. Removable devices shall implement the SEND and

RECEIVE Processor Device SCSI-2 Commands. The IRIG Standard 106 Chapter 6 commands

and data will be transported using these SCSI commands and the data buffers.

10.9.5 Mandated IEEE-1394b Interface Connector. The connector type for the removable media

shall be a “IEEE 1394b Bilingual Socket” connector. Power for the Removable Media shall be

derived from the Bilingual interface connector.

10-125

7/31/2019 IRIG_106_2009



10.9.6 Real Time Clock. Removable media configured with a real time clock shall allow fortime to be preset in the media allowing for the transfer to the recorder. SCSI command set shall

be utilized to set time on the cartridge.

a. Real Time Clock Time Format. Time format shall be in accordance with

paragraph IRIG 106 Chapter 6 paragraph 6.8.4.23. The date format shall be inaccordance with ISO 8601.

b. Real Time Clock Logic Unit Number. The standard SCSI Media devices areusing Logical Unit Number (LUN) = 0. The Real Time Clock shall be

assigned LUN =1.

10.9.7 Mandatory Commands for Processor Devices. The mandatory commands for processordevices are listed in Table 10-11.

TABLE 10-11. MANDATORY PROCESSOR COMMANDS


.BBLIST Directs the RMM to retrieve the bad block list

.BBLIST R Retrieves the bad block list from the RMM

.BBREAD {block identifier} Returns contents of specified block in ASCII hexadecimal byte

format

.BBREAD P {block identifier} Directs the RMM to initiate a physical block read of the specified

physical block identifier

.BBREAD D Retrieves the data from the physical block. See the .MEDIA P

command for information. Data is returned in binary format. .BBSECURE {block identifier} Marks an unsecured bad block as secure .BIT Runs all of the RMM 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 RMM

.DECLASSIFY Initiates command as specified by user specification or user

CONOP overwrite procedures .ERASE Erases the RMM media .HEALTH [ feature] Display detailed status of the RMM

.IDENTIFY Queries the RMM for Solid State Memory identification and

firmware version .INITIALIZE Initializes RMM internal components

.MEDIA P Queries the RMM for information about the physical media of theRMM and the transfer limits for the required physical I/O

commands

.PBWRITE P {block identifier} Directs the RMM to initiate a physical block write of the specified

physical block identifier

.PBWRITE D Write the data to the physical block in binary format. See the

.MEDIA P command for information. .SANITIZE Initiates a memory clear and identification of bad memory blocks

.STATUS Displays the current RMM status


10-126

7/31/2019 IRIG_106_2009



10.9.7.1 RMM .HEALTH Command Response. The RMM .HEALTH command response ispresented in Figure 10-114.

BIT MASK DESCRIPTION

RMM 0 01 BIT Failure 1 02 Setup Failure (unable to set the time or date properly)

2 04 Operational Failure (I/O error, media error, etc)

3 08 Low or dead battery warning

4 10 RMM Busy





Figure 10-114. RMM .HEALTH command response.

The operation of these commands is described in Chapter 6, paragraph 8,Command and Control Mnemonics.

10.9.8 Time Setting Requirements. To set time, the .TIME commands should be used

according to Chapter 6, paragraph 8, Recorder Command and Control Mnemonics,

paragraph 6.8.4.32. To guarantee and avoid uncontrolled delay, the following algorithm shall beused:

a. The Host device puts a .TIME command with time parameter to be set in its

SEND buffer and sends it at least 100 ms prior to the correct time to the Real

Time Clock device. The delay is necessary to allow the Processor Device to be

prepared for the exact time setting and to hold off enough in the Host to force adoorbell with the next SCSI command. Without enough delay the Host will not

be able to chain the next SCSI command together with the previous command. If the operating system demands it a delay greater than 100 ms can be used.

b. The Processor Device shall process this time and be prepared to set it at receipt of

the doorbell.

c. A SEND command shall be sent to the Real Time Clock with the message .TIMEwithout parameters to ask back the time set.

10.9.9 Set Time. To set time the .TIME commands should be used according to IRIG-106Chapter 6, paragraph 8 Recorder Command and Control Mnemonics, paragraph 6.8.4.23.

10.9.10 Date Setting Requirements. A .DATE [start-date] command shall be utilized forsetting or displaying date of the removable memory real time clock. The date shall be set in

year-month-day format according to ISO 8601.

Date Example.

.DATEDATE 2002-12-31

*

10-127

7/31/2019 IRIG_106_2009



10.9.11 Checking Battery Status. Verification of health of battery shall be accomplished

with .CRITICAL and .HEALTH commands IAW IRIG 106 Chapter 6, paragraph 8. Recorder

Command and Control Mnemonics, paragraph 6.8.4.2 and paragraph 6.8.4.10.

10.9.12 Declassification Supporting Commands.

10.9.12.1 .IDENTIFY: A .IDENTIFY command queries the RMM for Solid State Disk

(SSD) identification and firmware version.

Description

This command queries the RMM for SSD identification information and

SSD firmware version.

Parameters

None

Response

The RMM responds with one line containing five comma separated fields.

Characters and spaces are allowed within the comma separated fields.

Response time shall be within 100 milliseconds. A .STATUS commandrequest prior to 100 milliseconds shall elicit a BUSY response.

*.IDENTIFY

A, B, C, D, E

*

Where

A … SSD Manufacturer

B … SSD ModelC … SSD Serial Number

D … RMM Firmware VersionE … SSD Firmware Version

10.9.12.2 .MEDIA P: The .MEDIA P command is utilized to query the RMM for informationregarding the physical block architecture of the SSD and the SCSI RECEIVE transfer limits in

effect when reading physical blocks.

Parameters

The parameter “P” distinguishes this command from the standard .MEDIA

command.

Response

The RMM responds with one line containing the tag “PHYSICAL” and

five space separated integer numbers. Response time shall be within 100

milliseconds. A .STATUS command prior to 100 msec shall return aBUSY state.

10-128

7/31/2019 IRIG_106_2009



Example

*.MEDIA PPHYSICAL A B C D E

*

Where …A … Physical block size in bytes. This value must be a multiple of item

D below.

B ... Total number of physical blocks in SSD.

C … Maximum ORB transfer size that can be used when reading thebinary data from the physical block with the .BBREAD D and

.PBWRITE D commands.

D … Number of valid data bytes in a physical page. Item A above mustbe an integer multiple of this value.

E … This field specifies the number of filler bytes appended onto each

physical page read from the RMM. Filler bytes are typically

inserted to pad the transfer to the next ATA sector boundary. If nopadding is required, this field may be 0.

10.9.12.3 .SANITIZE: A .SANITIZE command shall initiate a write/verify of all RMMuser data physical blocks. The pattern may consist of either all “FF’s” or all “00’s”. The

.SANITIZE command shall identify any blocks that cannot be written or verified. Blocks that

cannot be written to or contain at least one bit that is stuck in either the ‘0’ state or the ‘1’ aretermed “bad blocks”. The user shall review the block contents and map out the bad blocks such

that they are no longer addressable. Once the address has been mapped out the blocks are no

longer addressable and are no longer identified in the bad block table (Figure 10-115).

Figure 10-115. Updating the Bad Block Table

10-129

7/31/2019 IRIG_106_2009



Parameters

None

Response

The RMM responds with an asterisk. Response time shall be within 100

milliseconds. A .STATUS command prior to 100 milliseconds shall elicita BUSY response. During Sanitization the RMM shall respond with “S 04xx yy zz”; where zz indicates percentage complete, reference the

.STATUS command. Upon completion a status response of “S 11 xx yy”

shall indicate that bad blocks were found. A status response upon

completion of “S 12 xx yy” shall indicate that no bad blocks were found.

Example *.SANITIZE

*

10.9.12.4 .BBLIST: A .BBLIST command shall be utilized to instruct the RMM to retrieve

the list of UNSECURED bad block identifiers from Solid State Media residing in the RMM. ABBLIST command is only valid following a SANITIZE command.

Parameters

None

Response

The RMM responds with an asterisk. Response time shall be within 100milliseconds. A .STATUS command prior to 100 msec shall return a

BUSY state.

Example

*.BBLIST*

10.9.12.5 .BBLIST R: A .BBLIST R shall be used to retrieve bad block identifiers fromthe RMM. This command may only be issued immediately following a successful .BBLIST

command.

Parameters

The parameter “R” distinguishes this command from the standard

.BBLIST command.

Response

The RMM must respond with a list of hexadecimal bad block identifiers.Each identifier must be terminated with a <CR><LF> sequence. Eachidentifier must be a legal hexadecimal number from 1 to 16 digits. No

embedded spaces or other special characters are allowed. Response time

shall be within 100 milliseconds. A .STATUS command prior to 100

milliseconds shall return a BUSY state.

10-130

7/31/2019 IRIG_106_2009



Example

*.BBLIST R

000000E3

0000034f FE0184C9

*

10.9.12.6 .BBREAD P {block_identifier}: A .BBREAD P {block_identifier} shall direct

the RMM to initiate a physical block read of the specified physical block identifier.

Parameters

The parameter “P” distinguishes this as a binary physical block read

command.

The parameter block_identifier is the physical block identifier [from theBBLIST R response] of the block to be read.

Response

The RMM responds with an asterisk. Response time shall be within 100milliseconds. A .STATUS command prior to 100 msec shall return a

BUSY state.

Example

.BBREAD P FE0184C9

*

10.9.12.7 .BBREAD D: A .BBREAD D command shall read one binary physical block

from the RMM. This command may only be issued immediately after a successful .BBREAD Pcommand. The size of physical block, page size, page filler size, and maximum SCSI RECEIVEtransfer size that are required to perform the transfer are all specified in the RMM’s response to

the .MEDIA P command.

Parameters

None.

Response

The RMM responds by returning the requested binary physical block data.Multiple SCSI RECEIVE commands may be required to retrieve the entire

physical data block.

*.BBREAD D

Response is in binary.

10.9.12.8 .BBSECURE {block identifier }: A .BBSECURE command shall be utilized tomark an unsecured bad block as being secured. A block that has been identified as secured shall

never be used for any subsequent data recording. Secured bad blocks shall be removed from the

unsecured bad block identifier list. The block identifier shall be provided for the block to besecured.

10-131

7/31/2019 IRIG_106_2009



Parameters

None.

Response

The RMM responds with an asterisk.

Example.BBSECURE 5678

*

10.9.12.9 .PBWRITE P {block_identifier}: A .PBWRITE P {block_identifier} shall direct

the RMM to initiate a physical block write of the specified physical block identifier.

Parameters

The parameter block_identifier is the physical block identifier [from the

BBLIST R response] of the block to be written.

Response

The RMM responds with an asterisk. Response time shall be within 100milliseconds. A .STATUS command prior to 100 milliseconds shallreturn a BUSY state.

Example

.PBWRITE P FE0184C9

*

10.9.12.10 .PBWRITE D: A PBWRITE D command shall write one binary physical block to

the RMM. This command may only be issued immediately after a successful .PBWRITE Pcommand. The size of physical block transfer size and the maximum SCSI SEND page size that

are required to perform the transfer are all specified in the RMM’s response to the .MEDIA P

command.

Parameters

Binary data block. Multiple SCSI SEND commands may be required to

transfer the entire physical data block.

Response

The RMM responds with an asterisk after all data is successfully received.

*.PBWRITE D

<binary data> total length = physical block size.

10-132

7/31/2019 IRIG_106_2009



10.9.12.11 .INITIALIZE: A .INITIALIZE command shall be utilized to configure the RMMmemory and reset of the firmware.

Parameters

None

ResponseThe RMM responds with an asterisk. Response time shall be within 100

milliseconds. A .STATUS command prior to 100 milliseconds shallreturn a BUSY state. A response of “S13 xx yy zz”; where zz indicates

percentage complete shall be provided. Upon completion, a response of

“S 14 xx yy” shall be provided; where yy indicates number of secondsrequired after initialization.

*.INITIALIZE*

.STATUS

S 13 00 00 01%

.STATUSS 13 00 00 02%

•

••

.STATUS

S 13 00 00 100%.STATUS

S 14 00 03

.STATUS

S 01 00 00

10.9.12.12 .DECLASSIFY: A .DECLASSIFY command shall be utilized to initiate user

procedures.

Parameters

None

Response

The RMM responds with an asterisk. Response time shall be within 100

milliseconds. A .STATUS command prior to 100 milliseconds shall

return a BUSY state. During Sanitization the RMM shall respond with “S04 xx yy zz”; where zz indicates percentage complete, reference status

command. Upon completion a status response of “S 11 xx yy” shallindicate that bad blocks were found. A status response upon completionof “S 12 xx yy” shall indicate that no bad blocks were found.

Example

*.DECLASSIFY

*

10-133

7/31/2019 IRIG_106_2009



10.9.12.13 .IRIG106: A .IRIG106 shall be utilized to retrieve the IRIG-106 supportedversion number.

Parameters

None

ResponseThe RMM responds with a version number which shall be a two integer

value. Response time shall be within 100 milliseconds. A .STATUScommand prior to 100 milliseconds shall return a BUSY state.

Example

*.IRIG106

9

*

10.9.12.14 .STATUS: A .STATUS shall be utilized to query the RMM for statusinformation (see Table 10-12).

DescriptionThis command queries the RMM for status information.

Parameters

None

Response

The RMM response to a .STATUS command with a response of the

form…

*.STATUS

S A B C [D%]*

10-134

7/31/2019 IRIG_106_2009



TABLE 10-12. RMM STATES

Description

STATE State

CODE

(A)

State

Value

(B)

State

Value

(C)

Progress

Percentage

(D)

FAIL 00

IDLE 01 00 00

BIT 02 00 00 Percent Complete

ERASE 03 00 00 Percent Complete

DECLASSIFY

SANITIZE04 00 00 Percent Complete

BUSY 09 00 00

SANITIZE

COMPLETED

BAD BLOCKS

FOUND

11 00

Number of

bad blocks

found

(Integer)

SANITIZE

COMPLETED

NO BAD

BLOCKS

FOUND

12 00 00

INITIALIZE IN

PROGRESS13 00 00 Percent Complete

INITIALIZE

COMPLETE

14 00

Number of

seconds

required for

initialization(Integer)

10-135

7/31/2019 IRIG_106_2009



10.9.12.15 RMM Command Error Codes. Issuing invalid commands (bad syntax) or illegalcommands (not accepted in the current system state) result in error code responses (with an

ASCII “E” identifier) prior to the asterisk response terminator when a command cannot be

completed. Table 10-13 shows possible error codes and the conditions under which they occur.

Example

.CLEARE 00

*

TABLE 10-13. COMMAND ERROR CODES

Error Description Conditions

00 INVALID COMMAND Command does not exist

01 INVALID PARAMETER Parameter is out of range, or wrong alpha-numeric type

02 INVALID MODE Command cannot be executed in the current state

05 COMMAND FAILED Command failed to execute for any reason other than those listed above

10.9.13 Vendor Specific Devices. The Mandatory SCSI Command Set for Vendor

Specific Devices is as follows:

a. For random access devices:INQUIRY

READ

READ CAPACITYTEST UNIT READY

REQUEST SENSE

b. For sequential access devices:INQUIRYREAD

REWIND

TEST UNIT READYREQUEST SENSE

COTS media shall support as a minimum the SCSI command set to

support data download in accordance with paragraph 10.4 of this standard.

10.9.14 Mandatory ORB Formats for the Processor Device.

10.9.14.1 Minimum Operational Requirements. The time setting accuracy of the Real Time

Clock device shall be better than 1 millisecond. The short time accuracy of the Real Time Clock device must be at least 10 ppm in the temperature range 0-40C, and at least 50 ppm in the

temperature range –40C - +85C.

10-136

7/31/2019 IRIG_106_2009



10.9.14.2 ORB Format.

a. Login ORB format. The login ORB format is illustrated in Figure 10-116.

most significant

password

Login_response

n Rq_fmt x Reserved reconnect function LUN

password_length login_response_length

Status_FIFO

least significant

Field and Bit Descriptions

Password 32 bits The password shall be “RTC.” The password field shall contain

the immediate data and the password_length shall be zero. Login_response

login_response_length 64 bits

16 bits

The login_response (32 bits) field and login_response_length

(16 bits) field shall specify the address and size of a buffer

(minimum of 12 bytes) allocated by the host for the return of the

login response.

N 1 bit The notify bit “n” shall be one.

Rq_fmt 2 bits The rq_fmt shall be zero. X 1 bit The exclusive bit “x” shall be one.

Reserved 4 bits Reserved shall be zero (0).

Reconnect 4 bits The reconnect field shall specify the reconnect time as a power

of 2 seconds. A value of zero shall mean one second.

Function 4 bits The Function shall be zero.

LUN 16 bits The logical unit number shall be one (1).

Status_FIFO 64 bits The Status_FIFO shall contain the address allocated by the host

for the return of status for the LOGIN request and for the return

of subsequent write and read buffer response(s) indicating

success/failure of the operation

Figure 10-116. Login ORB format.

10-137

7/31/2019 IRIG_106_2009



b. Login Response. The Login Response format is illustrated in Figure 10-117.

Figure 10-117. Login response format.

most significant

Length login_ID

command_block_agent

reserved reconnect_hold

least significant


Length 16 bits The length, in bytes, of the login response data

login_ID 16 bits Used in all subsequent requests to the SSMC’s

Management Agent.

command_block_agent 64 bits Base address of agent’s CSRReserved 16 bits Reserved shall be zero (0).

Reconnect_hold 16 bits TBD

c. Send. The Send command ORB format is illustrated in Figure 10-118, and theSend data buffer format is illustrated in Figure 10-119. The Send data buffer

contains the send command (according to Chapter 6) with the carriage return,

line feed and binary 0 character terminated. Alternatively, a .PBWRITE Dcommand will send data in binary format.

10-138

7/31/2019 IRIG_106_2009



most significant

next_ORB

data_descriptor

n Rq_fmt r d spd max_payload p page_size data size

0Ah LUN Res AEN Xfer Lng upper bits

Xfer Lng low Control 00h 00h

00h 00h 00h 00h

least significant


next_ORB 64 bits ORB pointer format shall be in accordance with SBP-2 specifications.

data_descriptor 32 bits Data_descriptor shall contain the address of the data buffer.

n 1 bits Completion notification “n” shall be one. The target shall store a status

block at the status_FIFO address at the address supplied in the login request.

Rq_fmt 2 bits Required format shall be zero.

r 1 bits Reserved shall be zero (0);

d 1 bits Direction bit “d” shall be zero.

spd 3 bits Speed “spd” shall have a value of two.

max_payload 4 bits The maximum data transfer length “max_payload” shall be nine.

p 1 bits The removable media device must be prepared to handle the Page table bit

p=0 and p=1 cases as the standard operating systems set this bit without

influence of the application programs.

page_size 3 bits Page size shall be zero if the p field is set to 0, otherwise this field shall be

set to the valid page size.

data size 16 bits The data size field should be set according to the allocated send buffer size

in bytes (N). The length must be at least 80 (50h).


Res 4 bits Reserved shall be zero (0).

AEN 1 bits AEN shall be zero.

Xfer Lng 24 bits The length must be at least 80 (50h).

Control 8 bits Control shall be 80h.

AEN

Figure 10-118. Send command ORB format.

10-139

7/31/2019 IRIG_106_2009



B te 1 B te 2 B te 3 B te 4


B te N-3 B te N-2 B te N-1 B te N B te

Least significant

Most significant

Figure 10-119. Send data buffer format.

d. Receive. The Receive command block ORB format is illustrated in Figure 10-120;

the Receive data buffer can be returned in ASCII format (see Figure 10-121) or in

binary format (see Figure 10-122), if the retrieved data contains binary information.Multiple ORBs may be used to retrieve the data required.

The returned remote answer is an ASCII text terminated by the ‘*’ (asterisk)character IAW IRIG-106 Chapter 6-8. If the ‘*’ terminator is missing, multiple

Receive commands must be used to retrieve the data until the ‘*’ terminator is

received.

If the returned remote answer can contain mixed ASCII text or binaryinformation until the specified length in the first 32-bit word. The first byte is a

hexadecimal 10 code to identify the binary format (codes hexadecimal 11-1F

are reserved for future extensions). The answer must be terminated by the ‘*’

(asterisk) character IAW IRIG-106 Chapter 6-8. If the ‘*’ terminator ismissing, multiple Receive commands must be used to retrieve the data until

the ‘*’ terminator is received.

10-140

7/31/2019 IRIG_106_2009



most significant

next_ORB

data_descriptor

n Rq_fmt r d spd max_payload p page_size data size

08h LUN Res AEN Allocation Lng upper bits

Allo Lng low Control 00h 00h

00h 00h 00h 00h

least significant


next ORB 6 bits ORB pointer format shall be in accordance with SBP-2 specifications.

data Descriptor 64 bits Data_descriptor shall contain the address of the data buffer.

n 1 bits Completion notification “n” shall be one. The target shall store a status block at

the status_FIFO address at the address supplied in the login request.

Rq_fmt 2 bits Rq_fmt shall be zero.

r 1 bits Reserved: shall be zero (0).

d 1 bits Direction bit “d” shall be one.

spd 3 bits Speed “spd” shall have a value of two.

max_payload 4 bits The maximum data transfer length “max_payload” shall be nine.p 1 bits The removable media device must be prepared to handle the Page table bit p=0

and p=1 cases as the standard operating systems set this bit without influence of

the application programs.

page_size 3 bits Page size shall be zero if the p field is set to 0, otherwise this field shall be set to

the valid page size.

data size 16 bits The data size field should be set according to the allocated receive buffer size in

bytes (N). The length must be at least 80 (50h).


Res 4 bits Reserved shall be zero (0).

AEN 1 bits AEN shall be zero.

Allocation Lng 16 bits Allocation_Lng = length of the Chapter 6 response string.

Control 8 bits Control shall be 80h.

AEN

Figure 10-120. Receive command block ORB format (8 quadlets).

10-141

7/31/2019 IRIG_106_2009



Figure 10-121. Receive data buffer format ASCII format.

Figure 10-122. Receive data buffer binary format.

10.10 Ground Based Recorders

This section of the standard specifies the basic requirements of Ground Based Recordershereinafter referred to as Ground Recorders. The main functional requirements of Ground

Recorders are:

a. Recorder Interface.

b. Recorder Data Format.

c. Recorder Media.

d. Recorder Command and Control (if the Ground Recorder is to be controlledremotely).

Optionally, Ground Recorders may support replay, reproduction, and display of

IRIG-106 Chapter 10 data recordings. Basic replay and reproduction interoperability

requirements will be defined in this section. Data display requirements are outside the scope of this standard and will not be defined.


Most significant


B te N-3 B te N-2 B te N-1 B te N

Least significant

Hexadec. 10 Len th Hi h Len th Middle Len th Low

Most significant


B te N-3 B te N-2 B te N-1 B te N

Least significant

10-142

7/31/2019 IRIG_106_2009



10.10.1 Interface.

a. At a minimum, the required Ground Recorders interface shall be Ethernet forremote command and control IAW paragraph 10.4 and 10.7 of this standard.

b. Optionally, ground recorders can implement additional interfaces for remote

command and control, remote data access, and/or data streaming. If a groundrecorder uses iSCSI or contains an RS-232/422, IEEE-1394 and/or FibreChannel for these interfaces, it shall be IAW paragraph 10.4 and 10.7 of this

standard.

c. Data streaming.

The recorder can optionally have the capability to stream IRIG-106

Chapter 10 format data (paragraph 10.10.2) out of its required EthernetInterface IAW paragraph 10.3.9.1.

Stream commit time as defined in paragraph 10.6.1.h of this standard shallapply to Ethernet Interface Data streaming.

10.10.2 Data Format. Ground Recorders shall format, multiplex, and record all data IAWparagraph 10.6 of this standard.

10.10.3 Recording Media. Ground Recorders shall record data IAW paragraph 10.10.2 tothe following Recording Media:

a. COTS Media. Commercial Off-The-Shelf (COTS) is defined as any recordingmedia (such as hard disks, solid state drives, tape, RAID, and JBOD) that is

ready-made and available for sale to the general public.

COTS Media shall have a ready-made and available for sale to the general

public electrical interface (such as PATA, SATA, IEEE-1394, USB, SCSI,Ethernet) to the Ground Recorders.

If Ground Recorders use COTS Media for recording of the paragraph10.10.2 data format, the recorded data Remote Data Access at a minimum

shall be across the required Ground Recorder Ethernet interface using

iSCSI IAW paragraph 10.4.3 (Ethernet Recorder Interface) andparagraph 10.5 (Interface File Structure) of this standard.

If Ground Recorders provide Remote Data Access across the GroundRecorder Ethernet interface, the paragraph 10.5 (Interface File Structure) at

a minimum shall be presented at the interface. This does not dictate whichCOTS media format or data organization is implemented, but does require

that the paragraph 10.5 (Interface File Structure) is presented at therecorder Ethernet interface.

b. COTS Media Requirements. COTS Media used by Ground Recorders shallprovide the capability of recording valid IRIG-106 Chapter 10 Original

Recording File(s) IAW paragraph 10.11 (Data Interoperability). All

10-143

7/31/2019 IRIG_106_2009



paragraph 10.11 Data Transfer and File Management requirements of thisstandard shall apply to Ground Recorders.

10.10.4 Remote Command and Control.

a. Optionally, if a Ground Recorder is controlled remotely, it shall provide

command and control IAW paragraph 10.7.8 and 10.7.9 of this standard acrossthe Ethernet Interface port as defined in paragraph 10.10.1 of this standard.

b. Ground Recorders at a minimum are required to use iSCSI or TELNET as the

command and control Ethernet transport mechanism as defined in paragraph

10.4 and paragraph 10.7.

c. Ground Recorders providing remote command and control capability shallprovide the functionality for all commands defined in paragraph 10.7.9 of this

standard.

d. Optionally, if a Ground Recorder contains a RS-232/422, IEEE-1394B and/or

Fibre Channel interface as defined in paragraph 10.10.1 the recorder will

provide command and control IAW paragraph 10.7 and IRIG-106 Chapter 6.

10.10.5 Data Replay and Reproduction.

10.10.5.1 Channel Mapping.

a. Optionally, if a Ground Recorder provides data playback capability, it shall

provide for the logical assignment of recorded channels to physical channels onthe Ground Recorders.

b. Playback will not require movement of cards between slots to make assignments

for playback.

10.10.5.2 Recording/Reproduction Data Rates. Optionally, if a Ground Recorder provides a

data playback capability, it shall provide information using the IRIG-106 Chapter 6 .HEALTHand .CRITICAL commands if the bandwidth of data to be played back exceeds the aggregate

bandwidth of the Ground Recorder.

10.10.5.3 Network Recording Playback.

a. Optionally, if a Ground Recorder provides a data playback capability, it shall

provide replay from COTS Media (paragraph 10.10.3) to the Ethernet Interface.

The Ethernet format of the network recording playback will be IAWparagraph 10.3.9.1.

b. If the network recording playback capability is commanded remotely, GroundRecorders shall support the functionality of the IRIG-106 Chapter 6.

10.11 Data Interoperability

10.11.1 Original Recording Files. All files contained within a recorder, RMM, COTS

Media, or that are a byte-for-byte single file downloaded to a host computing platform in

10-144

7/31/2019 IRIG_106_2009



unaltered form shall be considered Original Recording Files and be in full compliance with theData Organization in paragraph 10.5.1 and Data Format in paragraph 10.6.

Original Recording File Annotation. In order to provide a standardized methodof annotation for Original Recording Files, the following procedures shall be

used to ensure IRIG-106 Chapter 10 compliancy:

o The Computer Generated Data, Format 1 Setup Record shall always containthe required attributes IAW paragraph 10.11.

o The Original Recording File Setup Record R-x\RI3 “Original Tape/Storage”

attribute value shall be R-x\RI3:Y;

o 10.11.2 Modified Recording Files. Modified Recording files are created from Original

Recording Files directly from a recorder, RMM, COTS Media or from Original Recording Files

that have been downloaded to a host computing platform. There are several instances of Modified Recording Files - filtered or sanitized data, a subset of channels, a superset of channels,

a subset of time, a subset of both channels and time, or a superset of channels and subset of time.

10.11.2.1 Modified Recording File Annotation. In order to provide a standardized method

of annotation for Modified Recording Files, the following procedures shall be used to ensure

IRIG-106 Chapter 10 compliancy.

a. The Computer Generated Data, Format 1 Setup Record shall always contain therequired attributes IAW paragraph 10.11.

b. Any time a modification is made to an original recording the R-x\RI3 “Original

Tape/Storage” attribute value shall be changed:

From: R-x\RI3:Y;

To: R-x\RI3:N;

Also, the R-x\RI6 “Date of Modification” attribute will be added if not alreadypresent, in which case if R-x\RI3 contains a “Y” R-x\RI6 shall be empty. TheR-x\RI8 attribute value shall contain the last date and time the Modified

Recording File was created.

c. If the Modified Recording File is not a Time Subset but either a Channel Subset

or both a Time and Channel Subset, then the step “b” attributes shall be changed

as defined. Also the original channels which are not included in the RecordingSubset File shall have the R-x\CHE-n “Channel Enable” attribute changed:

From: R-x\CHE-n:T;

To: R-x\CHE-n:F;

A comment attribute R-x\COM will be inserted directly after the changed

R-x\CHE-n attribute and shall contain the following:

“original recording change - removed channel-n” (where n represents the

Channel ID of the channel that was removed).

d. If the Modified Recording File is not a Time Subset but either a ChannelSuperset or both a Time Subset and Channel Superset, then the step “b”

10-145

7/31/2019 IRIG_106_2009



attributes shall be changed as defined. Also the channels added in the ModifiedRecording File shall contain the required attribute IAW paragraph 10.11:

A comment attribute R-x\COM will be inserted directly after the added

channel R-x\CHE-n attribute and shall contain the following:

“original recording change - additional channel-n” (where n represents theChannel ID of the channel that was added).

If the Modified Recording File contains filtered (removed packets or data)

or sanitized data (overwrite of data), then the step “b” attributes shall be

changed as defined. Also the channels which contain filtered or sanitized data

in the Modified Recording File shall also contain a comment attribute R-x\COMinserted directly after the channel R-x\CHE-n attribute and shall contain the

following:

“original recording change - filtered channel-n” (where n represents the

Channel ID of the channel that was filtered).

10.11.2.2 Modified Recording File Restructuring. When a Modified Recording File is createdthere will be alterations to original packets or possibly structure. Therefore:

a. All files shall reflect any sequence number, packet length, or checksum changesin the appropriate Packet Header fields.

b. If enabled in the original recording Computer Generated Data, Format 3

Recording Index packets shall be recalculated to ensure correct information iscontained within the entries as they relate to the newly created Modified

Recording File.

10.11.3 Original Recording and Modified Recording File Extension. Upon data download

to a host computing platform, all Original Recording Files and/or Modified Recording Files shalluse the file extension *.ch10 (or *.c10 extension for use on systems with a 3 character extension

limit). The use of this standard extension will indicate that any Original Recording File and/or

Modified Recording File on a ground computing or storage platform shall be in compliance withthis paragraph 10.11 of this standard.

10.11.4 File Naming. Upon data download from the recorder or RMM to a host

computing platform, all Original Recording Files or Modified Recording Files shall use thefollowing structure and naming conventions unless host computing platform operating system

imposes naming length limits. In this case the directory and file names are to be truncated after

the last component that completely fits within the name length limit:

10-146

7/31/2019 IRIG_106_2009



10.11.4.1 On-Board Recorder.

a. Data Recording Directory Name. Each directory block from a RMM to be

downloaded to a ground computing or storage platform shall use

paragraph 10.5, Table 10-2 VolName as the directory name where the DataFiles will be placed. The directory name shall use lower case alpha characters.If the VolName is empty (0x00), a default name or user-defined name shall

be used. If used the default name shall be ch10dirnnn, where nnn is the

sequential directory block count.

b. Data File Name. Each Data File contained within a Directory Block on the

RMM to be downloaded will be placed in the Directory identified in paragraph10.11.4.1.a and shall use the following naming convention. The data file name

shall use lower case alpha characters:

“filennnn”; where nnnn is the sequential RMM file count from each

Directory Block File Entry (must be 8 alpha-numeric characters).

Example: “file0001,” “file0002,” …:“file9999.”

If available, “File Create Date,” “File Create Time” and “File Close Time”

from paragraph 10.5, Table 10-3, DDMMYYYY_HHMMSSss_HHMMSSss (8numeric characters for File Create Date, 8 numeric characters for File Create

Time separated by an underscore ASCII character code 0x5F, and 8 numeric

characters for File Close Time). No spaces or other non-numeric charactersallowed). Example 02092004_21302731_21451505.

If the “File Create Date,” “File Create Time” and “File Close Time” from

paragraph 10.5, Table 10-3 values are not available and are filled with 0x2D,then the system time from the host download platform will be used for “File

Create Date” and “File Create Time” (DDMMYYYY_HHMMSS). “File CloseTime” will not be used. “File Close Time” shall be replaced with “sys_time.”

A structure example follows:

…\VolName\FileName_FileCreateDate_FileCreateTime_FileCloseTime

When VolName not empty example:…\<VolName>\file0001_02092004_21302731_21451505.ch10

When VolName empty default example:

…\ch10dir001\file0001_02092004_21302731_21451505.ch10When VolName empty user defined example:

…\<User Defined>\file0001_02092004_21302731_21451505.ch10

When Date/Time not available (0x2D fill) example:

…\file0001_02092004_213027_sys_time.ch10

10-147

7/31/2019 IRIG_106_2009



The use of this standard recording and file naming convention will indicatethat any file on a ground computing or storage platform is in compliance with

this standard.

10.11.4.2 Ground Based Recorder.

a. Recording Directory Name. Each directory where the Data Files will be placedshall use the naming convention \ch10dir_DDMMYYYY_nnn; where n is the

sequential number of Chapter 10 recording directories created on the

DDMMYYYY date. The directory name shall use lower case alpha characters.

b. Recording File Name. Each Data File contained within a Directory shall use thefollowing naming convention. The data file name shall use lower case alpha

characters:

“filennnn”; where nnnn is the sequential file count from each recording

(must be 8 alpha-numeric characters). Example “file0001,” “file0002,”…:“file9999.”

File Create Date, File Create Time and File Close Time shall use the

following naming convention DDMMYYYY_HHMMSSss_HHMMSSss (8

numeric characters for File Create Date, 8 numeric characters for File CreateTime separated by an underscore ASCII character code 0x5F, and 8 numeric

characters for File Close Time). No spaces or other non-numeric characters

allowed). Example 02092004_21302731_21451505.

A structure example follows:

…\ch10dir_02092005_001\file0001_02092005_21302731_21451505.ch10

The use of this standard recording and file naming convention will indicate

that any file on a ground computing or storage platform is in compliance withthis standard.

10.11.5 Data Transfer File. In order to ensure the highest degree of interoperability for

transfer of IRIG-106 Chapter 10 Recorder or RMM contents, Original Recording Files orModified Recording Files between organizations the Data Transfer File Structure shall be used.

Essentially, a Data Transfer File contains all the same information and data that a recorder or

RMM would present at the interface albeit within a single binary structure on either tape orrandom access devices. The Data Transfer File could also contain Original Recording Files or

Modified Recording Files from multiple recordings or dates.

Original Recording Files or Modified Recording Files downloaded to ahost computing platform and transferred as a single file shall follow

10.11.1 and 10.11.2.

10.11.5.1 Data Transfer File Structure Definition. The following describes Data Transfer File

Structure and media environments:

10-148

7/31/2019 IRIG_106_2009



a. Tape Devices. A Data Transfer File on tape devices is treated essentially thesame as a recorder or RMM in that the directory structure and data contents are

as defined and organized in this standard. The Data Transfer File is a single

binary file containing a directory structure IAW 10.5 and a single or multipleIRIG-106 Chapter 10 Original Recording Files or Modified Recording Files.

Only one Data Transfer File will be contained on a tape device media. The tapeblock size shall be 32K (32,768) bytes.

Logical Address 1 will contain a directory and file structure IAW

paragraph 10.5.2.

The corresponding IRIG-106 Chapter 10 Original Recording Files or

Modified Recording Files will follow the directory structure in contiguousbytes until the end of the Data Transfer File. The beginning of each IRIG-

106 Chapter 10 Original Recording File or Modified Recording File in theData Transfer File will begin at the byte offset contained in each File Entry

table File Start Address value.

b. Random Access Devices. A Data Transfer File on a random access device istreated essentially the same as a recorder RMM in that the directory structureand data contents are as defined and organized in this standard. The Data

Transfer File is a single binary file containing a directory structure IAW 10.5.2

and a single or multiple IRIG-106 Chapter 10 Original Recording Files orModified Recording Files. Multiple Data Transfer Files can be contained on a

random access device.

The paragraph 10.5.2 directory structure within the Data Transfer Filebegins at byte 0 and runs contiguously until the last file entry paragraph.

The next byte after the last file entry block shall be the first byte in the first

data file.

The corresponding IRIG-106 Chapter 10 Original Recording Files orModified Recording Files will follow the directory structure in contiguous

bytes until the end of the Data Transfer File. The beginning of each IRIG-

106 Chapter 10 Original Recording File or Modified Recording File in the

Data Transfer File will begin at the byte offset contained in each File Entrytable File Start Address value.

10.11.5.2 Data Transfer File Extension. Upon creation, all IRIG 106 Chapter 10 compliant

Data Transfer Files not on Tape Devices shall use the file extension *.tf10 (or *.t10 extensionfor use on systems with a 3 character extension limit). The use of this standard extension will

indicate that any Data Transfer File on a host computing or storage platform shall be incompliance with paragraph 10.11.5 of this standard.

10.11.6 Recording Directory File. A binary recording directory file which is a byte-for-

byte copy of the RMM or Recorder directory structure presented at the interface. This file

should represent the contents of a RMM or recorder directory at the time of IRIG-106 Chapter 10data download. The bytes in this file contain the byte-for-byte contents of the RMM’s directory

blocks in the order the directory blocks are linked, using each block’s “forward Link” field.

10-149

7/31/2019 IRIG_106_2009



10-150

10.11.6.1 Recording Directory File Extension. Upon creation, all IRIG 106 Chapter 10compliant Recording Directory Files shall use the file extension *.df10 (or *.d10 extension for

use on systems with a 3 character extension limit). The use of this standard extension will

indicate that any Recording Directory file on a host computing or storage platform shall be incompliance with paragraph 10.11.6 of this standard.

7/31/2019 IRIG_106_2009


Telemetry Standard RCC Document 106-09, Appendix A, April 2009

APPENDIX A

FREQUENCY CONSIDERATIONS FOR TELEMETRY

Paragraph Title Page

1.0 Purpose............................................................................................................ A-1

2.0 Scope............................................................................................................... A-13.0 Authorization to Use a Telemetry System...................................................... A-3

4.0 Frequency Usage Guidance ............................................................................ A-4

5.0 Bandwidth....................................................................................................... A-86.0 Spectral Occupancy Limits........................................................................... A-15

7.0 Technical Characteristics of Digital Modulation Methods........................... A-18

8.0 FQPSK-B and FQPSK-JR Characteristics ................................................... A-19

9.0 SOQPSK-TG Characteristics........................................................................ A-2210.0 Advanced Range Telemetry (ARTM) CPM Characteristics. ....................... A-23

11.0 PCM/FM ....................................................................................................... A-2412.0 Valid Center Frequencies Near Telemetry Band Edges ............................... A-25

LIST OF FIGURES

Figure A-1. Spectra of 10-Mb/s CPFSK, ARTM CPM, FQPSK-JR, SOQPSK-TG

signals. ............................................................................................................ A-4

Figure A-2. 5 Mb/s PCM/FM signals with 11 MHz center frequency separation. ............ A-6

Figure A-3. 10 Mb/s ARTM CPM signals with 9 MHz center frequency separation........ A-6Figure A-4. RNRZ PCM/FM signal................................................................................. A-10

Figure A-5. Spectrum analyzer calibration of 0-dBc level............................................... A-11

Figure A-6. Bi PCM/PM signal...................................................................................... A-12Figure A-7. FM/AM signal and Carson’s Rule ................................................................ A-12

Figure A-8. Typical receiver RLC IF filter response (-3 dB bandwidth = 1 MHz). ........ A-14Figure A-9. RLC and SAW IF filters ............................................................................... A-15

Figure A-10. Filtered 5-Mb/s RNRZ PCM/FM signal and spectral mask. ........................ A-17

Figure A-11. Unfiltered 5-Mb/s RNRZ PCM/FM signal and spectral mask. .................. A-17Figure A-12. Typical 5-Mb/s SOQPSK-TG signal and spectral mask. ............................. A-18

Figure A-13. Typical 5-Mb/s ARTM CPM signal and spectral mask. .............................. A-18

Figure A-14. OQPSK modulator. ....................................................................................... A-19Figure A-15. I & Q constellation........................................................................................ A-19

Figure A-16. FQPSK wavelet eye diagram........................................................................ A-20

Figure A-17. FQPSK-B I & Q eye diagrams (at input to IQ modulator).......................... A-20Figure A-18. FQPSK-B vector diagram............................................................................. A-20Figure A-19. 5 Mb/s FQPSK-JR spectrum with random input data and small (blue)

and large (red) modulator errors. .................................................................. A-21

Figure A-20. FQPSK-B spectrum with all 0’s input and large modulator errors.............. A-21Figure A-21. FQPSK-JR BEP vs. E b/N0. ........................................................................... A-22

Figure A-22. Measured SOQPSK-TG phase trajectory ..................................................... A-22Figure A-23. SOQPSK-TG Power Spectrum (5 Mb/s). ..................................................... A-23

7/31/2019 IRIG_106_2009



ii

Figure A-24. BEP versus E b/No performance of 5 Mb/s SOQPSK-TG. ............................ A-23

Figure A-25. Power spectrum of 5 Mb/s ARTM CPM...................................................... A-23Figure A-26. BEP versus E b/No performance of 5 Mb/s ARTM CPM. ............................. A-24

Figure A-27. Power spectrum of 5 Mb/s PCM/FM signal. ................................................ A-24

Figure A-28. BEP versus E b/No performance of 5 Mb/s PCM/FM with multi-symbol

bit detector and three single symbol receivers/detectors. ............................. A-25Figure A-29. Spectral Masks at -25 dBm........................................................................... A-26

Figure A-30. Bit Rate vs. Band edge Back-off. ................................................................. A-27

Figure A-31. Valid center frequency, band edge back-off. ................................................ A-28

LIST OF TABLES

Table A-1. Coefficients for Minimum Frequency Separation Calculation....................... A-5

Table A-2. 99 Percent Power Bandwidths for Various Digital Modulation Methods .... A-10

Table A-3. Characteristics of Various Modulation Methods. ......................................... A-18Table A-4. L-Band Frequency Range (10 W, 5 Mbps)................................................... A-26

7/31/2019 IRIG_106_2009



APPENDIX A

FREQUENCY CONSIDERATIONS FOR TELEMETRY

1.0 Purpose

This appendix was prepared with the cooperation and assistance of the Range

Commanders Council (RCC) Frequency Management Group (FMG). This appendix provides

guidance to telemetry users for the most effective use of the ultra high frequency (UHF)

telemetry bands, 1435 to 1535 MHz, 2200 to 2290 MHz, and 2310 to 2390 MHz. Coordinationwith the frequency managers of the applicable test ranges and operating areas is recommended

before a specific frequency band is selected for a given application. Government users should

coordinate with the appropriate Area Frequency Coordinator and commercial users shouldcoordinate with the Aerospace and Flight Test Radio Coordinating Council (AFTRCC). A list of

the points of contact can be found in the National Telecommunications and Information

Administration (NTIA) Manual of Regulations and Procedures for Federal Radio FrequencyManagement. The manual is at http://www.ntia.doc.gov/osmhome/redbook/redbook.html.

2.0 Scope

This appendix is to be used as a guide by users of telemetry frequencies at Department of

Defense (DoD)-related test ranges and contractor facilities. The goal of frequency management

is to encourage maximal use and minimal interference among telemetry users and betweentelemetry users and other users of the electromagnetic spectrum.

2.1 Definitions. The following terminology is used in this appendix.

Allocation (of a Frequency Band). Entry of a frequency band into the Table of Frequency

Allocations1 for use by one or more radio communication services or the radio astronomy serviceunder specified conditions.

Assignment (of a Radio Frequency or Radio Frequency Channel). Authorization given by an

administration for a radio station to use a radio frequency or radio frequency channel under specified conditions.

Authorization. Permission to use a radio frequency or radio frequency channel under specifiedconditions

1 The definitions of the radio services that can be operated within certain frequency bands contained in the radio

regulations as agreed to by the member nations of the International Telecommunications Union. This table is

maintained in the United States by the Federal Communications Commission and the NTIA.

A-1



7/31/2019 IRIG_106_2009



Certification. The Military Communications-Electronics Board’s (MCEB) process of verifying

that a proposed system complies with the appropriate rules, regulations, and technical standards.

J/F 12 Number. The identification number assigned to a system by the MCEB after the

Application for Equipment Frequency Allocation (DD Form 1494) is approved; for example, J/F

12/6309 (sometimes called the J-12 number).

Resolution Bandwidth. The -3 dB bandwidth of the measurement device.

2.2 Modulation methods.

2.2.1 Traditional Modulation Methods. The traditional modulation methods for aeronautical

telemetry are Frequency Modulation (FM) and Phase Modulation (PM). Pulse Code Modulation

(PCM)/Frequency Modulation (FM) has been the most popular telemetry modulation since

around 1970. The PCM/FM method could also be called filtered Continuous Phase FrequencyShift Keying (CPFSK). The RF signal is typically generated by filtering the baseband non-

return-to-zero-level (NRZ-L) signal and then frequency modulating a voltage-controlled

oscillator (VCO). The optimum peak deviation is 0.35 times the bit rate and a good choice for a premodulation filter is a multi-pole linear phase filter with bandwidth equal to 0.7 times the bit

rate. Frequency and phase modulation have a variety of desirable features but may not provide

the required bandwidth efficiency, especially for higher bit rates.

2.2.2 Improved Bandwidth Efficiency. When better bandwidth efficiency is required, the

standard methods for digital signal transmission are the Feher Patented Quadrature Phase Shift

Keying (FQPSK-B and FQPSK-JR), the Shaped Offset Quadrature Phase Shift Keying(SOQPSK-TG), and the Advanced Range Telemetry (ARTM) Continuous Phase Modulation

(CPM). Each of these methods offers constant, or nearly constant, envelope characteristics and

are compatible with non-linear amplifiers with minimal spectral regrowth and minimal

degradation of detection efficiency. The first three methods (FQPSK-B, FQPSK-JR, andSOQPSK-TG) are interoperable and require the use of the differential encoder described in

Chapter 2, paragraph 2.4.3.1.1. Additional information on this differential encoder is contained

in Appendix M. All of these bandwidth-efficient modulation methods require the data to berandomized.

2.3 Other Notations. The following notations are used in this appendix. Other referencesmay define these terms slightly differently.

a. B99% -Bandwidth containing 99 percent of the total power. b. B-25dBm -Bandwidth containing all components larger than -25 dBm.

c. B-60dBc -Bandwidth containing all components larger than the power level that is 60 dB below the unmodulated carrier power.

d. dBc -Decibels relative to the power level of the unmodulated carrier.

e. fc -Assigned center frequency.

A-2

7/31/2019 IRIG_106_2009



3.0 Authorization to Use a Telemetry System

All radio frequency (RF) emitting devices must have approval to operate in the United

States and Possessions (US&P) via a frequency assignment unless granted an exemption by the

national authority. The NTIA is the President's designated national authority and spectrum

manager. The NTIA manages and controls the use of RF spectrum by federal agencies in US&Pterritory. Obtaining a frequency assignment involves the two-step process of obtaining an RF

spectrum support certification of major RF systems design, followed by an operational frequency

assignment to the RF system user. These steps are discussed below.

3.1 RF Spectrum Support Certification. All major RF systems used by federal agencies must

be submitted to the NTIA, via the Interdepartmental Radio Advisory Committee (IRAC), for system review and spectrum support certification prior to committing funds for

acquisition/procurement. During the system review process, compliance with applicable RF

standards, and RF allocation tables, rules, and regulations is checked. For Department of Defense (DoD) agencies, and for support of DoD contracts, this is accomplished via the

submission of a DD Form 1494 to the MCEB. Noncompliance with standards, the tables, rules,or regulations can result in denial of support, limited support, or support on an unprotected non-

priority basis. All RF users must obtain frequency assignments for any RF system (even if notconsidered major). This assignment is accomplished by submission of frequency use proposals

through the appropriate frequency management offices. Frequency assignments may not be

granted for major systems that have not obtained spectrum support certification.

3.1.1 Frequency Allocation. As stated before, telemetry systems must normally operate within

the frequency bands designated for their use in the National Table of Frequency Allocations.With sufficient justification, use of other bands may at times be permitted, but the certification

process is much more difficult, and the outcome is uncertain. Even if certification is granted ona noninterference basis to other users, the frequency manager is often unable to grant

assignments because of local users who will get interference.

3.1.1.1 Telemetry Bands. Air and space-to-ground telemetering is allocated in the UHF bands

1435 to 1535, 2200 to 2290, and 2310 to 2390 MHz, commonly known as the lower-L band, the

lower-S band, and the upper-S band. Other mobile bands, such as 1755-1850 MHz, can also be

used at many test ranges. Since these other bands are not considered a standard telemetry band per this document, potential users must coordinate, in advance, with the individual range(s) and

ensure use of this band can be supported at the subject range(s) and that their technical

requirements will be met.

3.1.1.2 Very High Frequency (VHF) Telemetry. The VHF band, 216-265 MHz, was used for

telemetry operations in the past. Telemetry bands were moved to the UHF bands as of 1 January 1970 to prevent interference to critical government land mobile and military tactical

communications. Telemetry operation in this band is strongly discouraged and is considered

only on an exceptional case-by-case basis.

A-3

7/31/2019 IRIG_106_2009



3.1.2 Technical Standards. The MCEB and the NTIA review proposed telemetry systems for

compliance with applicable technical standards. For the UHF telemetry bands, the currentrevisions of the following standards are considered applicable:

a. RCC Document IRIG 106, Telemetry Standards.

b. MIL-STD-461, Requirements for the Control of Electromagnetic InterferenceEmissions and Susceptibility.

c. Manual of Regulations and Procedures for Federal Radio Frequency Management

(NTIA).

Applications for certification are also thoroughly checked in many other ways including

necessary and occupied bandwidths, modulation characteristics, reasonableness of output power,correlation between output power and amplifier type, and antenna type and characteristics. The

associated receiver normally must be specified or referenced. The characteristics of the receiver

are also verified.

3.2 Frequency Authorization. Spectrum certification of a telemetry system verifies that the

system meets the technical requirements for successful operation in the electromagneticenvironment. However, a user is not permitted to radiate with the telemetry system before

requesting and receiving a specific frequency assignment. The assignment process considers

when, where, and how the user plans to radiate. Use of the assignments is tightly scheduled by

and among the individual ranges to make the most efficient use of the limited telemetry radiofrequency (RF) spectrum and to ensure that one user does not interfere with other users.

4.0 Frequency Usage Guidance

Frequency usage is controlled by scheduling in the areas where the tests will be

conducted. The following recommendations are based on good engineering practice for such

usage and it is assumed that the occupied bandwidth fits within the telemetry band in all cases.

4.1 Minimum Frequency Separation.The minimum required frequency

separation can be calculated using the

formula:

ΔF0 = as*R s + ai*R i (A-1)

where:ΔF0 = the minimum required center frequency separation in MHz

R s=bit rate of desired signal in Mb/sR i=bit rate of interfering signal inMb/s

Figure A-1. Spectra of 10-Mb/s CPFSK,

ARTM CPM, FQPSK-JR, SOQPSK-TG

signals.

-70

-60

-50

-40

-30

-20

-10

P o w e r ( d B c )

-2 -1 0 1 2Normalized Frequency (bit rate = 1)

PCM/FM ARTM CPM FQPSK-JR SOQPSK-TG

10 Mb/s

as is determined by the desired signal type

and receiving equipment (Table A-1).

A-4

7/31/2019 IRIG_106_2009



TABLE A-1. COEFFICIENTS FOR MINIMUM FREQUENCY SEPARATION

CALCULATION

Modulation Type as

ai

NRZ PCM/FM 1.0* for receivers with RLC final Intermediate

Frequency (IF) filters0.7 for receivers with Surface Acoustic Wave (SAW) or

digital IF filters

0.5 with multi-symbol detectors (or equivalent devices)

1.2

FQPSK-B, FQPSK-JR,

SOQPSK-TG0.45 0.65

ARTM CPM 0.35 0.5

*The minimum frequency separation for typical receivers with Resistor-Inductor-Capacitor (RLC) final IF filters

and NRZ-L PCM/FM signals is the larger of 1.5 times the actual IF –3 dB bandwidth and the value calculatedusing the equation above.

The minimum spacing needs to be calculated for signal 1 as the desired signal and

signal 2 as the interferer and vice versa. Note that the values for ai match the –57 dBc points for the four modulation methods shown in Figure A-1 quite closely. It is not surprising that the

required frequency spacing from the interferer is directly related to the power spectrum of the

interfering signal. The values for as are a function of the effective detection filter bandwidthsand the co-channel interference resistance of the desired signal modulation method and detector.

The values for as and ai are slightly conservative for most cases and assume the receiver beingused does not have spurious responses that cause additional interference. This section was

completely rewritten from previous editions of the Telemetry Standards because addition of newmodulation methods and new receiving equipment rendered the old method obsolete. The values

of as and ai were determined empirically from the results of extensive adjacent channel

interference testing. The main assumptions are as follows:

a. The NRZ PCM/FM signals are assumed to be premodulation filtered with a multi-

pole filter with -3 dB point of 0.7 times the bit rate and the peak deviation is assumedto be approximately 0.35 times the bit rate.

b. The receiver IF filter is assumed to be no wider than 1.5 times the bit rate and

provides at least 6 dB of attenuation of the interfering signal.c. The interfering signal is assumed to be no more than 20 dB stronger than the desiredsignal.

d. The receiver is assumed to be operating in linear mode; no significant

intermodulation products or spurious responses are present.

A-5

7/31/2019 IRIG_106_2009



Examples are shown below:

5 Mb/s PCM/FM and 0.8 Mb/s PCM/FM using a receiver with 6 MHz IF bandwidth for the 5 Mb/s

signal (this receiver has RLC IF filters).

1.0*5 + 1.2*0.8 = 5.96 MHz, 1.0*.8 + 1.2*5 = 6.8 MHz, 1.5*6= 9.0 MHz;the largest value is 9 MHz and the frequencies are assigned in 1 MHz steps so the minimum

spacing is 9 MHz

5 Mb/s PCM/FM and 5 Mb/s PCM/FM using a receiver with 6 MHz IF bandwidth

for the 5 Mb/s signals (these receivers have RLC IF filters; see Figure A-2).1.0*5 + 1.2*5 = 11 MHz, 1.5*6= 9.0 MHz;

the larger value is 11 MHz and the frequencies are assigned in 1 MHz steps so the minimum

spacing is 11 MHz.

5 Mb/s PCM/FM and 5 Mb/s PCM/FM using a receiver with 6 MHz IF bandwidth for the 5 Mb/s

signal (this receiver has RLC IF filters but a multi-symbol detector is used)

0.5*5 + 1.2*5 = 8.5 MHz;

the frequencies are assigned in 1 MHz steps so the minimum spacing is 9 MHz.

5 Mb/s PCM/FM and 5 Mb/s SOQPSK-TG using a receiver with 6 MHz IF bandwidth for the 5 Mb/s

signals (this receiver has RLC IF filters but a multi-symbol detector is used)

0.5*5 + 0.65*5 = 5.75 MHz, 0.45*5 + 1.2*5 = 8.25 MHz;

the largest value is 8.25 MHz and the frequencies are assigned in 1 MHz steps so the minimum

spacing is 9 MHz.

5 Mb/s FQPSK-B and 5 Mb/s ARTM CPM using a receiver with 6 MHz IF bandwidth for the 5 Mb/s

signals

0.45*5 + 0.5*5 = 4.75 MHz 0.35*5 + 0.7*5 = 5.25 MHz;the largest value is 5.25 MHz and the frequencies are assigned in 1 MHz steps so the minimumspacing is 6 MHz.

10 Mb/s ARTM CPM and 10 Mb/s ARTM CPM (see Figure A-3)

0.35*10 + 0.5*10 = 8.5 MHz;


Figure A-2. 5 Mb/s PCM/FM signals with 11

MHz center frequency separation.

Figure A-3. 10 Mb/s ARTM CPM signals

with 9 MHz center frequency separation

-70

-60

-50

-40

-30

-20

-10

P o w e r ( d B c )

1440.5 1450.5 1460.5 1470.5Frequency (MHz)

-70

-60

-50

-40

-30

-20

-10

P o w e r ( d B c )

1440.5 1450.5 1460.5 1470.5Frequency (MHz)

A-6

7/31/2019 IRIG_106_2009



4.2 Alternative method for determining frequency separation. In some cases it may be

desirable to set aside a bandwidth for each signal independent of other signals. If one uses a bandwidth factor of 2*ai for each signal, then one gets a separation of ΔF0 = ai*R s + ai*R i and

one gets a more conservative (wider) separation than one would using ΔF0 = as*R s + ai*R i

because the value of ai is bigger than the value of as for all of these modulation methods. One

problem with this approach is that it does not include receiver or detector characteristics andtherefore the calculated frequency separations are often different from those calculated using the

formula in section 4.1.

Examples of frequency separation are shown below:

5 Mb/s PCM/FM and 0.8 Mb/s PCM/FM using a receiver with 6 MHz IF bandwidth for the5 Mb/s signal (this receiver has RLC IF filters)

1.2*5 + 1.2*0.8 = 6.96 MHz;


5 Mb/s PCM/FM and 5 Mb/s PCM/FM using a receiver with 6 MHz IF bandwidth for the 5

Mb/s signals (these receivers have RLC IF filters)1.2*5 + 1.2*5 = 12 MHz;


5 Mb/s PCM/FM and 5 Mb/s PCM/FM using a receiver with 6 MHz IF bandwidth for the

5 Mb/s signal (this receiver has RLC IF filters but a multi-symbol detector is used)

1.2*5 + 1.2*5 = 12 MHz;the frequencies are assigned in 1 MHz steps so the minimum spacing is 12 MHz.

5 Mb/s PCM/FM and 5 Mb/s SOQPSK-TG using a receiver with 6 MHz IF bandwidth for the

5 Mb/s signals (this receiver has RLC IF filters but a multi-symbol detector is used)1.2*5 + 0.65*5 = 9.25 MHz;


5 Mb/s FQPSK-B and 5 Mb/s ARTM CPM using a receiver with 6 MHz IF bandwidth for the

5 Mb/s signals


10 Mb/s ARTM CPM and 10 Mb/s ARTM CPM


4.3 Geographical Separation. Geographical separation can be used to further reduce the probability of interference from adjacent signals.

4.4 Multicarrier Operation. If two transmitters are operated simultaneously and sent or receivedthrough the same antenna system, interference due to intermodulation is likely at

(2 f 1 - f 2) and (2 f 2 - f 1). Between three transmitters, the two-frequency possibilities exist, but

intermodulation products may exist as well at ( f 1 + f 2 - f 3), ( f 1 + f 3 - f 2), and ( f 2 + f 3 - f 1), where f 1, f 2,

A-7

7/31/2019 IRIG_106_2009



and f 3 represent the output frequencies of the transmitters. Intermodulation products can arise from

nonlinearities in the transmitter output circuitry that cause mixing products between a transmitter output signal and the fundamental signal coming from nearby transmitters. Intermodulation

products also can arise from nonlinearities in the antenna systems. The generation of

intermodulation products is inevitable, but the effects are generally of concern only when such

products exceed -25 dBm. The general rule for avoiding third-order intermodulation interference isthat in any group of transmitter frequencies, the separation between any pair of frequencies should

not be equal to the separation between any other pair of frequencies. Because individual signals

have sidebands, it should be noted that intermodulation products have sidebands spectrally wider than the sidebands of the individual signals that caused them.

4.5 Transmitter Antenna System Emission Testing. Radiated tests will be made in lieu of transmitter output tests only when the transmitter is inaccessible. Radiated tests may still be

required if the antenna is intended to be part of the filtering of spurious products from the

transmitter or is suspected of generating spurious products by itself or in interaction with thetransmitter and feed lines. These tests should be made with normal modulation.

5.0 Bandwidth

The definitions of bandwidth in this section are universally applicable. The limits shown

here are applicable for telemetry operations in the telemetry bands 1435 to 1535, 2200 to 2290,

and 2310 to 2390 MHz. For the purposes of telemetry signal spectral occupancy, the bandwidthsused are the 99-percent power bandwidth and the -25 dBm bandwidth. A power level of

25 dBm is exactly equivalent to an attenuation of the transmitter power by 55 + 10log(P) dBwhere P is the transmitter power expressed in watts. How bandwidth is actually measured and

what the limits are, expressed in terms of that measuring system, are detailed in the following

paragraphs.

5.1 Concept. The term "bandwidth" has an exact meaning in situations where an amplitudemodulation (AM), double sideband (DSB), or single sideband (SSB) signal is produced with a

band-limited modulating signal. In systems employing frequency modulation (FM) or phase

modulation (PM), or any modulation system where the modulating signal is not band limited, bandwidth is infinite with energy extending toward zero and infinite frequency falling off from

the peak value in some exponential fashion. In this more general case, bandwidth is defined as

the band of frequencies in which most of the signal's energy is contained. The definition of

"most" is imprecise. The following terms are applied to bandwidth.

5.1.1 Authorized Bandwidth. For purposes of this document, the authorized bandwidth is the

necessary bandwidth required for transmission and reception of intelligence and does not include

allowance for transmitter drift or Doppler shift.

5.1.2 Occupied Bandwidth. The width of a frequency band such that below the lower and above

the upper frequency limits, the mean powers emitted are each equal to a specified percentage of thetotal mean power of a given emission. Unless otherwise specified by the International

Telecommunication Union (ITU) for the appropriate class of emission, the specified percentage

shall be 0.5 percent. The occupied bandwidth is also called the 99-percent power bandwidth.

A-8

7/31/2019 IRIG_106_2009



5.1.3 Necessary Bandwidth For a Given Class of Emission. For a given class of emission, the

width of the frequency band which is just sufficient to ensure the transmission of information atthe rate and with the quality required under specified conditions.

5.1.3.1 The NTIA Manual of Regulations and Procedures for Federal Radio Frequency

Management. This manual states that "All reasonable effort shall be made in equipment designand operation by Government agencies to maintain the occupied bandwidth of the emission of

any authorized transmission as closely to the necessary bandwidth as is reasonably practicable."

5.1.3.2 Necessary Bandwidth (DD Form 1494). The necessary bandwidth is part of the

emission designator on the DD Form 1494. For telemetry purposes, the necessary bandwidth can

be calculated using the equations shown below. Equations for other modulation methods arecontained in the NTIA Manual of Regulations and Procedures for Federal Radio Frequency

Management. The necessary bandwidth as calculated below is a reasonable bandwidth to use

for telemetry frequency scheduling.

Filtered non-return-to-zero (NRZ) pulse code modulatiom/frequency modulation (PCM/FM)Bn = 2.4Xbit rate with h=0.7 and premodulation filter bandwidth = 0.7 times bit rate.

Example: PCM/FM modulation used to send 5 megabits per second using frequencymodulation with 2 signaling states and 1.75 MHz peak deviation; bit rate=5X10

6;

necessary bandwidth (Bn) = 12 MHz.

Constant envelope offset quadrature phase shift keying; Feher’s patented quadrature phase shift

keying (FQPSK-B, FQPSK-JR) or shaped offset quadrature phase shift keying (SOQPSK-TG)

Bn = 1.3Xbit rate. Example: SOPQSK-TG modulation used to send 5 megabits per second using 4 signaling states; bit rate=5X10

6; Bn = 6.5 MHz.

Advanced Range Telemetry (ARTM) Continuous Phase Modulation (CPM)

Bn = bit rate with h=4/16 and 5/16 on alternating symbols; Digital modulation used to

send 5 megabits per second using frequency modulation with 4 signaling states and withalternating modulation index each symbol; bit rate=5X10

6;Bn = 5 MHz.

5.1.4 Received (or Receiver) Bandwidth. The received bandwidth is usually the -3 dB

bandwidth of the receiver intermediate frequency (IF) section.

5.2 Bandwidth Estimation and Measurement. Various methods are used to estimate or

measure the bandwidth of a signal that is not band limited. The bandwidth measurements are performed using a spectrum analyzer (or equivalent device) with the following settings: 30-kHz

resolution bandwidth, 300-Hz video bandwidth, and no max hold detector or averaging. These

settings are different than those in earlier versions of the Telemetry Standards. The settings werechanged to get more consistent results across a variety of bit rates, modulation methods, and

spectrum analyzers. The most common measurement and estimation methods are described in the

following paragraphs.

5.2.1 99-Percent Power Bandwidth. This bandwidth contains 99 percent of the total power.

The 99-percent power bandwidth is typically measured using a spectrum analyzer or estimated

A-9

7/31/2019 IRIG_106_2009



using equations for the modulation type and bit rate used. If the two points that define the edges

of the band are not symmetrical about the assigned center frequency, their actual frequencies anddifference should be noted. The 99-percent power band edges of randomized NRZ (RNRZ)

PCM/FM signals are shown in Figure A-4 below. Table A-2 presents the 99-percent power

bandwidth for several digital modulation methods as a function of the bit rate (R).

TABLE A-2. 99 PERCENT POWER BANDWIDTHS FOR VARIOUS DIGITAL

MODULATION METHODS

DESCRIPTION 99% POWER BANDWIDTH

RZ PCM/FM, premod filter BW=0.7R, f=0.35R 1.16 R

RZ PCM/FM, no premod filter, f=0.25R 1.18 R



RZ PCM/FM, premod filter BW=0.7R, f=0.40R 1.57 R

Minimum shift keying (MSK), no filter 1.18 R

FQPSK-B, FQPSK-JR or SOQPSK-TG 0.78 R

ARTM CPM 0.56 R

5.2.2 -25 dBm Bandwidth. The -25 dBm bandwidth

is the bandwidth containing all components larger than-25 dBm. A power level of –25 dBm is exactly

equivalent to an attenuation of the transmitter power

by 55 + 10log(P) dB where P is the transmitter power

expressed in watts. The -25 dBm bandwidth limits areshown in Figure A-4. The –25 dBm bandwidth is

primarily a function of the modulation method,

transmitter power, and bit rate. The transmitter designand construction techniques also strongly influence the

–25 dBm andwidth. With a bit rate of 5 Mb/s and a

transmitter power of 5 watts the –25 dBm bandwidth

of an NRZ PCM/FM system with near optimum parameter settings is about 13.3 MHz, while the –25 dBm bandwidth of an equivalent FQPSK-B

system is about 7.5 MHz, and the 25 dBm bandwidth of an equivalent ARTM CPM system isabout 5.8 MHz.

Figure A-4. RNRZ PCM/FM signal.

A-10

7/31/2019 IRIG_106_2009



5.2.3 Other Bandwidth Measurement Methods. The methods discussed above are the standard

methods for measuring the bandwidth of telemetry signals. The following methods are alsosometimes used to measure or to estimate the bandwidth of telemetry signals.

5.2.3.1 Below Unmodulated Carrier. This method measures the power spectrum with respect to the

unmodulated carrier power. To calibrate the measured spectrum on a spectrum analyzer, theunmodulated carrier power must be known. This power level is the 0-dB reference (commonly set

to the top of the display). In AM systems, the carrier power never changes; in FM and PM

systems, the carrier power is a function of the modulating signal. Therefore, a method to estimatethe unmodulated carrier power is required if the modulation cannot be turned off. For most

practical angle modulated systems, the total carrier power at the spectrum analyzer input can be

found by setting the spectrum analyzer's resolution and video bandwidths to their widest settings,setting the analyzer output to max hold, and allowing the analyzer to make several sweeps (see

Figure A-3 above). The maximum value of this trace will be a good approximation of the

unmodulated carrier level. Figure A-5 shows the spectrum of a 5-Mb/s RNRZ PCM/FM signalmeasured using the standard spectrum analyzer settings discussed previously and the spectrum

measured using 3-MHz resolution, video bandwidths, and max hold. The peak of the spectrummeasured with the latter conditions is very close to 0-dBc and can be used to estimate the

unmodulated carrier power (0-dBc) in the presence of frequency or phase modulation. In practice,the 0-dBc calibration would be performed first, and the display settings would then be adjusted to

use the peak of the curve as the reference level (0-dBc level) to calibrate the spectrum measured

using the standard spectrum analyzer settings. With the spectrum analyzer set for a specificresolution bandwidth, video bandwidth, and detector type, the bandwidth is taken as the distance

between the two points outside of which the spectrum is thereafter some number (say, 60 dB)

below the unmodulated carrier power determined above. The -60 dBc bandwidth for the 5-Mb/ssignal shown in Figure A-5 is approximately 13 MHz.

Figure A-5. Spectrum analyzer calibrationof 0-dBc level

The -60 dBc bandwidth of a random NRZ

PCM/FM signal with a peak deviation of 0.35R, a

four-pole premodulation filter with -3 dB corner at 0.7R, and a bit rate greater than or equal to 1

Mb/s can be approximated by

B-60dBc = {2.78 - 0.3 x log10(R)} x R (A-3)

where B is in MHz and R is in Mb/s.

Thus the -60 dBc bandwidth of a 5-Mb/s

RNRZ signal under these conditions would be

approximately 12.85 MHz. The -60 dBc bandwidth will be greater if peak deviation is

increased or the number of filter poles is

decreased.

A-11

7/31/2019 IRIG_106_2009



5.2.3.2 Below Peak. This method is not recommended

for measuring the bandwidth of telemetry signals.The modulated peak method, the least accurate

measurement method, measures between points

where the spectrum is thereafter XX dB below the

level of the highest point on the modulatedspectrum. Figure A-6 shows the radio frequency

spectrum of a 400-kb/s Bi-L PCM/PM signal

with a peak deviation of 75 and a pre-modulation

filter bandwidth of 800 kHz. The largest peak ha power level of -7 dBc. In comparison, the

largest peak in Figure

as

A-5 had a power level of

-22 dBc. This 15-dB difference would skew a bandwidth comparison that used the peak level in

the measured spectrum as a common reference

point. In the absence of an unmodulated carrier to use for calibration, the below peak

measurement is often (erroneously) used and described as a below unmodulated carrier measurement. Using max hold exacerbates this effect still further. In all instances the

bandwidth is overstated, but the amount varies.

Figure A-6. Bi PCM/PM signal

5.2.3.3 Carson's Rule. Carson's Rule is a

method to estimate the bandwidth of an FM

subcarrier system. Carson's Rule states that

B = 2 x (f + f max) (A-4)

where B is the bandwidth, f is the peak

deviation of the carrier frequency, and f max isthe highest frequency in the modulating

signal. Figure A-7 shows the spectrum thatresults when a 12-channel constant

bandwidth multiplex with 6-dB/octave

pre-emphasis frequency modulates an FM

transmitter. The 99-percent power bandwidth and the bandwidth calculatedusing Carson’s Rule are also shown. Carson's Rule will estimate a value greater than the 99-

percent power bandwidth if little of the carrier deviation

Figure A-7. FM/AM signal and Carson’s Rule

is due to high-frequency energy in the

modulating signal.

A-12

7/31/2019 IRIG_106_2009



5.2.4 Spectral Equations. The following equations can be used to calculate the RF spectra for several digital modulation methods with unfiltered waveforms.

2, 3, 4

These equations can be

modified to include the effects of filtering.5,

6

Random NRZ PCM/FM (valid when Dinteger, D = 0.5 gives MSK spectrum)

Q< D ,

D+ X Dcos2-1

X - D

) X - D(

D

R

B4 =S(f)

2

2

22

2

SA

cos

coscos

coscos

(A-5)

Random NRZ PSK

2

X

2

X

R

B =S(f)

2

2

SA

sin

A-6

Random NRZ QPSK and OQPSK

X

X

R

2B =S(f)

2

2SA

sin(A-7)

Random Bi PCM/FM

}){(

sinsinsin

nR f f

2

) D- X (

)2

D( D

+

4

D)+(X

4

D)+(X

4

D)-(X

4

D)-(X

2

D

4R

B =S(f) c

22

22

SA

(A-8)

2

I. Korn, Digital Communications, New York, Van Nostrand, 1985.3 M. G. Pelchat, "The Autocorrelation Function and Power Spectrum of PCM/FM with Random Binary Modulating

Waveforms," IEEE Transactions, Vol. SET-10, No. 1, pp. 39-44, March 1964.4 W. M. Tey, and T. T. Tjhung, "Characteristics of Manchester-Coded FSK," IEEE Transactions on

Communications, Vol. COM-27, pp. 209-216, January 1979.5 A. D. Watt, V. J. Zurick, and R. M. Coon, "Reduction of Adjacent-Channel Interference Components from

Frequency-Shift-Keyed Carriers," IRE Transactions on Communication Systems, Vol. CS-6, pp. 39-47, December

1958.6 E. L. Law, "RF Spectral Characteristics of Random PCM/FM and PSK Signals,"International Telemetering

Conference Proceedings, pp. 71-80, 1991.

A-13

7/31/2019 IRIG_106_2009



Random Bi PCM/PM

2 , f (f )(+

4

X

4

X

R

)( B =S(f) c

2

2

4

2SA

)cos

sinsin

(A-9)

where

S(f) = power spectrum (dBc) at frequency f

BSA = spectrum analyzer resolution bandwidth*

R = bit rate

D = 2f/R

X = 2(f-f c)/R

f = peak deviation

= peak phase deviation in radiansf c = carrier frequency

= Dirac delta function

n = 0, 1, 2,

Q = quantity related to narrow band spectral peaking when D1, 2, 3, ...

Q 0.99 for BSA = 0.003 R, Q 0.9 for BSA = 0.03 R

*The spectrum analyzer resolution bandwidth term was added to the original equations.

5.2.5 Receiver Bandwidth. Receiver

predetection bandwidth is typically defined as the

points where the response to the carrier beforedemodulation is -3 dB from the center frequency

response. The carrier bandwidth response of thereceiver is, or is intended to be, symmetrical about

the carrier in most instances. Figure A-8 shows

the response of a typical older generationtelemetry receiver with RLC IF filters and a

1 MHz IF bandwidth selected. Outside the stated

bandwidth, the response usually falls fairly rapidlywith the response often 20 dB or more below the

passband response at 1.5 to 2 times the passband

response.

Figure A-8. Typical receiver RLC IFfilter response (-3 dB bandwidth =

1 MHz).

A-14

7/31/2019 IRIG_106_2009



-30

-27-24-21-18-15-12-9-6-303

P o w e r ( d B )

60 65 70 75 80Frequency (MHz)

RLC SAW

Figure A-9 shows an overlay of an RLC

IF filter and a surface acoustic wave (SAW) filter. Note that the SAW filter rolls off much more rapidly

than the RLC filter. The rapid falloff outside the

passband helps reduce interference from nearby

channels and has minimal effect on data.

Figure A-9. RLC and SAW IF filters

5.2.6 Receiver Noise Bandwidth. For the purpose of calculating noise in the receiver, the bandwidth must be integrated over the actual shape of the IF, which, in general, is not a

square-sided function. Typically, the value used for noise power calculations is the -3 dB

bandwidth of the receiver.

5.3 Symmetry. Many modulation methods produce a spectrum that is asymmetrical withrespect to the carrier frequency. Exceptions include FM/FM systems, randomized NRZ

PCM/FM systems, and randomized FQPSK, SOQPSK-TG, and ARTM CPM systems. The mostextreme case of asymmetry is due to single-sideband transmission, which places the carrier

frequency at one edge of the occupied spectrum. If the spectrum is not symmetrical about the

band center, the bandwidth and the extent of asymmetry must be noted for frequencymanagement purposes.

5.4 FM Transmitters (ac coupled). The ac-coupled FM transmitters should not be used totransmit NRZ signals unless the signals to be transmitted are randomized because changes in the

ratio of “ones” to “zeros” will increase the occupied bandwidth and may degrade the bit error rate. When ac-coupled transmitters are used with randomized NRZ signals, it is recommended

that the lower -3 dB frequency response of the transmitter be no greater than the bit rate divided

by 4000. For example, if a randomized 1-Mb/s NRZ signal is being transmitted, the lower -3 dB

frequency response of the transmitter should be no larger than 250 Hz.

6.0 Spectral Occupancy Limits

Telemetry applications covered by this standard shall use 99-percent power bandwidth to

define occupied bandwidth and -25 dBm bandwidth as the primary measure of spectral

efficiency. The spectra are assumed symmetrical about the center frequency unless otherwise

specified. The primary reason for controlling the spectral occupancy is to control adjacentchannel interference, thereby allowing more users to be packed into a given amount of frequency

spectrum. The adjacent channel interference is determined by the spectra of the signals and thefilter characteristics of the receiver.

A-15

7/31/2019 IRIG_106_2009



6.1 Spectral Mask. One common method of describing the spectral occupancy limits is a

spectral mask. The aeronautical telemetry spectral mask is described below. Note that the mask in this standard is different than the masks contained in the earlier versions of the Telemetry

Standards. All spectral components larger than –(55 + 10log(P)) dBc, (i.e. larger than-25 dBm) at the transmitter output must be within the spectral mask calculated using the

following equation:

m

R f f f f RK f M cc ;log100log90 (A-10)

where

M(f) = power (dBc) at frequency f (MHz)K = -20 for analog signals

K = -28 for binary signals

K = -61 for FQPSK-B, FQPSK-JR, SOQPSK-TG

K = -73 for ARTM CPM f c = transmitter center frequency (MHz)

R = bit rate (Mb/s) for digital signals or

for analog FM signals MHz f f max m = number of states in modulating signal;

m = 2 for binary signals

m = 4 for quaternary signals and analog signals f = peak deviation

f max = maximum modulation frequency

These bandwidths are measured using a spectrum analyzer with settings of 30-kHz

resolution bandwidth, 300-Hz video bandwidth, and no max hold detector or averaging. Notethat these settings are different than those listed in previous editions of the Telemetry Standards.The changes were made to get more consistent results with various bit rates and spectrum

analyzers. The spectra measured with these settings give slightly larger power levels than with

the previous settings; this is why the value of “K” was changed from –63 to –61 for FQPSK and

SOQPSK signals. The power levels near center frequency should be approximately J 10log(R)

dBc where J= 10 for ARTM CPM, 12 for FQPSK and SOQPSK-TG, and 15.5 for PCM/FMsignals. For a bit rate of 5 Mb/s, the levels would be approximately -17 dBc for ARTM CPM,

-19 dBc for FQPSK, and -22.5 dBc for PCM/FM. If the power levels near center frequency arenot within 3 dB of these values, then a measurement problem exists and the carrier power level

(0 dBc) and spectrum analyzer settings should be verified.

The -25 dBm bandwidth is not required to be narrower than 1 MHz. The first term “K”

in equation (A-10) accounts for bandwidth differences between modulation methods. Equation

(A-10) can be rewritten as M(f) = K – 10logR – 100log|(f f c)/R|. When equation (A-10) iswritten this way, the 10logR term accounts for the increased spectral spreading and decreased

power per unit bandwidth as the modulation rate increases. The last term forces the spectral

mask to roll off at 30-dB/octave (100-dB/decade). Any error detection or error correction bits,which are added to the data stream, are counted as bits for the purposes of this spectral mask.

A-16

7/31/2019 IRIG_106_2009



The spectral masks are based on the power spectra of random real-world transmitter signals. For

instance, the binary signal spectral mask is based on the power spectrum of a binary NRZPCM/FM signal with peak deviation equal to 0.35 times the bit rate and a multipole

premodulation filter with a -3 dB frequency equal to 0.7 times the bit rate (see Figure A-4

above). This peak deviation minimizes the bit error rate (BER) with an optimum receiver

bandwidth while also providing a compact RF spectrum. The premodulation filter attenuates theRF sidebands while only degrading the BER by the equivalent of a few tenths of a dB of RF

power. Further decreasing of the premodulation filter bandwidth will only result in a slightlynarrower RF spectrum, but the BER will increase dramatically. Increasing the premodulation

filter bandwidth will result in a wider RF spectrum, and the BER will only be decreased slightly.

The recommended premodulation filter for NRZ PCM/FM signals is a multipole linear phasefilter with a -3 dB frequency equal to 0.7 times the bit rate. The unfiltered NRZ PCM/FM signal

rolls off at 12-dB/octave so at least a three-pole filter (filters with four or more poles are

recommended) is required to achieve the 30-dB/octave slope of the spectral mask. The spectralmask includes the effects of reasonable component variations (unit-to-unit and temperature).

6.2 Spectral Mask Examples.

Figure A-10. Filtered 5-Mb/s RNRZ PCM/FM signal

and spectral mask.

-70

-60

-50

-40

-30

-20

-10

0Power(dBc)

1440.5 1450.5 1460.5Frequency (MHz)

Figures A-10 and A-11 show the binary spectral mask of equation(A-10) and the RF spectra of 5-Mb/s

randomized NRZ PCM/FM signals.

The RF spectra were measured using aspectrum analyzer with 30-kHz

resolution bandwidth, 300-Hz video

bandwidth, and no max hold detector.The span of the frequency axis is20 MHz. The transmitter power was

5 watts, and the peak deviation was

1750 kHz. The modulation signal for

Figure A-10 was filtered with a 4-pole

linear-phase filter with 3 dB

frequency of 3500 kHz. All spectralcomponents in Figure A-10 were

contained within the spectral mask.

The minimum value of the spectral

mask was 62 dBc (equivalent to

25 dBm). The peak modulated signal power levels were about 22.5 dB

below the unmodulated carrier level(22.5 dBc). Figure A-11 shows the

same signal with no premodulationfiltering. The signal was not contained

within the spectral mask when a pre-

modulation filter was not used.

-70

-60

-50

-40

-30

-20

-10

0

P o w e r ( d B c )

1440.5 1450.5 1460.5Frequency (MHz)

Figure A-11. Unfiltered 5-Mb/s RNRZ PCM/FMsignal and spectral mask.

A-17

7/31/2019 IRIG_106_2009



Figure A-12 shows the FQPSK/SOQPSK mask of equation (A-10) and the RF spectrum

of a 5-Mb/s SOQPSK-TG signal. The transmitter power was assumed to be 5 watts in this

example. The peak value of the SOQPSK-TG signal was about 19 dBc. Figure A-13 shows a

typical 5-Mb/s ARTM CPM signal and its spectral mask. The peak value of the ARTM CPM

signal was about 17 dBc.

0

7.0 Technical Characteristics of Digital Modulation Methods

Table A-3 provides a summary of some of the technical characteristics of the modulation

methods discussed in this summary.

TABLE A-3. CHARACTERISTICS OF VARIOUS MODULATION METHODS.

CharacteristicPCM/FM with

single symbol

detection

PCM/FM with

multi-symbol

detection

FQPSK-B,

FQPSK-JR,

SOQPSK-TG

ARTM CPM

Occupied Bandwidth 1.16 bit rate 1.16 bit rate 0.78 bit rate 0.56 bit rate

Sensitivity

(E b/N0 for BEP=1e-5)

11.8-15+ dB 9.5 dB 11.8-12.2 dB 12.5 dB

Synchronization time100 to 10,000

bits250 bits

5,000 to 30,000

bits

30,000 to

150,000 bits

Synchronization

threshold level (E b/N0)3 to 4 dB 2 dB 4.5 to 5 dB 8.5 dB

Phase noise

susceptibility*2 1 3 4

Co-channel

interference

susceptibility*

2 1 3 4

* 1=Best, 2=Second Best, 3=Third Best, 4=Worst

Figure A-12. Typical 5-Mb/s SOQPSK-TG

signal and spectral mask.

Figure A-13. Typical 5-Mb/s ARTM CPM

signal and spectral mask.

-70

-60

-50

-40

-30

-20

-10

0

P o w e r ( d B c )

1440.5 1450.5 1460.5Frequency (MHz)

-70

-60

-50

-40

-30

-20

-10

P o w e r ( d B c )

1440.5 1450.5 1460.5Frequency (MHz)

A-18

7/31/2019 IRIG_106_2009



8.0 FQPSK-B and FQPSK-JR Characteristics

Figure A-14. OQPSK modulator.

Feher’s-patented quadrature phase shift

keying7, 8 (FQPSK-B and FQPSK-JR)

modulations are a variation of offset quadrature

phase shift keying (OQPSK). OQPSK isdescribed in most communications textbooks. A

generic OQPSK (or quadrature or I & Q)modulator is shown in Figure A-14. In general,

the odd bits are applied to one channel (say Q),

and the even bits are applied to the I channel.

If the values of I and Q are ±1, we get the

diagram shown in Figure A-15. For example, if I=1 and Q=1 then the phase angle is 45 degrees

{(I,Q) = (1, 1)}. A constant envelope modulation

method, such as minimum shift keying (MSK),would follow the circle indicated by the small

dots in Figure A-15 to go between the large dots.

In general, band-limited QPSK and OQPSK signals are not constant envelope and would not

follow the path indicated by the small dots but

rather would have a significant amount of amplitude variation, however FQPSK-B and

FQPSK-JR are nearly constant envelope and

essentially follow the path indicated by the smalldots in Figure A-15. Figure A-15. I & Q constellation.

7 K. Feher et. al.: US Patents 4,567,602; 4,644,565; 5,491,457; and 5,784,402, post-patent improvements and other

U.S. and international patents pending.8 Kato, Shuzo and Kamilo Feher, “XPSK: A New Cross-Correlated Phase Shift Keying Modulation Technique,”

IEEE Trans. Comm., vol. COM-31, May 1983.

A-19

7/31/2019 IRIG_106_2009



The typical implementation of FQPSK-B or FQPSK-JR involves the application of data

and a bit rate clock to the baseband processor of the quadrature modulator. The data aredifferentially encoded and converted to I and Q signals as described in Chapter 2. The I and Q

channels are then cross-correlated, and specialized wavelets are assembled that minimize the

instantaneous variation of (I2(t) + Q

2(t)). The FQPSK-B baseband wavelets are illustrated in

Figure A-16 below.

The appropriate wavelet is assembled based on the current and immediate past states of Iand Q. Q is delayed by one-half symbol (one bit) with respect to I as shown in

Figure A-17 below.

1

3

A m p l i t u d e

0 1

.707

-.707

1

-1

0.4

2.6

0 3

I

Q

Figure A-16. FQPSK wavelet eye diagram Figure A-17. FQPSK-B I & Q eyediagrams (at input to IQ modulator).

A common method at looking at I-Q modulation

signals is the use of a vector diagram. One method of

generating a vector diagram is to use an oscilloscopethat has an XY mode. The vector diagram

-0.5

0

0.5

Q

-0.5 0 0.5

I

is generated by applying the I signal to the X input andthe Q signal to the Y input. A sample vector diagram of

FQPSK-B at the input terminals of an I-Q modulator is

illustrated in Figure A-18. Note that the vector diagramvalues are always within a few percent of being on a

circle. Any amplitude variations may cause spectral

spreading at the output of a non-linear amplifier.Figure A-18. FQPSK-B vector

diagram.

A-20

7/31/2019 IRIG_106_2009



-70

-60

-50

-40

-30

-20

-10

0

P o w e r

( d B c )

-1 -0.5 0 0.5 1Relative Frequency (Bit Rate=1)

-80

-60

-40

-20

0

P o w e r ( d B c )

-1 -0.5 0 0.5 1Normalized Frequency (Bit rate=1)

Figure A-19 illustrates a nearly idealFQPSK-JR spectrum (blue trace) and an

FQPSK-JR spectrum with moderately large

modulator errors (red trace). These spectra

were measured at the output of a fullysaturated RF non-linear amplifier with a

random pattern of “1's” and “0's” applied tothe input. The bit rate for Figure A-19 was 5

Mb/s. The peak of the spectrum was

approximately 19 dBc. The 99-percent bandwidth of FQPSK-B is typically about

0.78 times the bit rate. Note that with a properly randomized data sequence and

proper transmitter design, FQPSK-B does

not have significant sidebands (blue trac

Figure A-19. 5 Mb/s FQPSK-JR spectrum

with random input data and small (blue) andlarge (red) modulator errors.e).

Figure A-20 illustrates an FQPSK-B

transmitter output with all “0's” as the input

signal. With an all “0's” input, the differentialencoder, cross-correlator, and wavelet selector

provide unity amplitude sine and cosine waves

with a frequency equal to 0.25 times the bit rate

to the I and Q modulator inputs. The resultingsignal (from an ideal modulator) would be a

single frequency component offset from the

carrier frequency by exactly +0.25 times the bit

rate. The amplitude of this component would beequal to 0 dBc. If modulator errors exist (they

always will), additional frequencies will appear

in the spectrum as shown in Figure A-20. The spectral line at a normalized frequency of 0(carrier frequency) is referred to as the remnant carrier. This component is largely caused by DC

imbalances in the I and Q signals. The remnant carrier power in Figure A-20 is approximately

-31 dBc. Well designed FQPSK-B transmitters will have a remnant carrier level less than-30 dBc. The spectral component offset, 0.25 times the bit rate below the carrier frequency, is

the other sideband. This component is largely caused by unequal amplitudes in I and Q and by a

lack of quadrature between I and Q. The power in this component should be limited to 30 dBcor less for good system performance.

Figure A-20. FQPSK-B spectrum withall 0’s input and large modulator errors.

Figure A-21 shows the measured bit error probability (BEP) versus signal energy per

bit/noise power per Hz (E b/N0) of two FQPSK-JR modulator/demodulator combinationsincluding non-linear amplification and differential encoding/decoding in an additive white

Gaussian noise environment (AWGN) with no fading. Other combinations of equipment may

have different performance. Phase noise levels higher than those recommended in Chapter 2 cansignificantly degrade the BEP performance. Computer simulations have shown that a BEP of

A-21

7/31/2019 IRIG_106_2009



10-5

may be achievable with an E b/N0 of slightly

greater than 11 dB (with differentialencoding/decoding). The purpose of the

differential encoder/decoder is to resolve the

phase detection ambiguities that are inherent in

QPSK, OQPSK, and FQPSK modulationmethods. The differential encoder/decoder used

in this standard will cause one isolated symbolerror to appear as two bits in error at the

demodulator output. However, many

aeronautical telemetry channels are dominated by fairly long burst error events, and the effect

of the differential encoder/decoder will often be

masked by the error events. Figure A-21. FQPSK-JR BEP vs. E b/N0.

1E-07

1E-06

1E-05

1E-04

1E-03

1E-02

1E-01

B E P

8 10 12 14Eb/No (dB)

5 Mb/s FQPSK-JR

9.0 SOQPSK-TG Characteristics.

SOQPSK is a family of constantenvelope continuous phase modulation (CPM)

waveforms defined by Mr. T. Hill.9, 10, 11, 12

The details of SOQPSK-TG are described in

Chapter 2, paragraphs 2.4.3.2 and 2.4.3.2.1. TheSOQPSK-TG signal amplitude is constant and

the phase trajectory is determined by the

coefficients in Chapter 2, Table 2-4. Therefore,SOQPSK-TG can be implemented using a precision phase or frequency modulator with

proper control of the phase trajectory.

Figure A-22 illustrates the measured phasetrajectory of an SOQPSK-TG signal. The

vertical lines correspond approximately to the

“bit” decision times.

180

-270

-180

-90

0

90

P h a s e ( d e g )

0 4 8 12 16Bit number

Figure A-22. Measured SOQPSK-TG

phase trajectory

9 Hill T., “An Enhanced, Constant Envelope, Interoperable Shaped Offset QPSK (SOQPSK) Waveform for

Improved Spectral Efficiency”, Proceedings of the International Telemetering Conference, San Diego, California,

October 2000.10 Younes B., Brase J., Patel C., Wesdock J., “An Assessment of Shaped Offset QPSK for Use in NASA Space

Network and Ground Network Systems”, Meetings of Consultative Committee for Space Data Systems, Toulouse,France, October, 2000.

11 Geoghegan, M., “Implementation and Performance Results for Trellis Detection of SOQPSK”, Proceedings of

the International Telemetering Conference, Las Vegas, Nevada, October 2001.

12 Simon, M., Bandwidth-Efficient Digital Modulation with Application to Deep Space Communications,

Monograph number 3, DESCANSO Monograph Series, JPL Publication 00-17, Jet Propulsion Laboratory,

California Institute of Technology, 2001. This publication is available free via the Internet:http://descanso.jpl.nasa.gov/Monograph/series3/complete1.pdf (note: do not use WWW prefix for this URL).

A-22




7/31/2019 IRIG_106_2009



The power spectrum of a random 5 Mb/sSOQPSK-TG signal is shown in Figure A-23.

The 60 dBc bandwidth of this 5 Mb/s signalwas about 7.34 MHz. Note that the maximum

power level is about -19 dBc.

Figure A-23. SOQPSK-TG Power Spectrum (5 Mb/s).

-70

-60

-50

-40

-30

-20

-10

0

P o w e r

( d B c )


Figure A-24 shows the measured bit error

probability (BEP) versus signal energy per bit/noise power per Hz (E b/N0) of two SOQPSK-

TG modulator/demodulator combinationsincluding non-linear amplification and differential

encoding/decoding in an additive white Gaussian

noise environment (AWGN) with no fading. Other combinations of equipment may have different

performance. Phase noise levels higher than those

recommended in Chapter 2 can significantlydegrade the BEP performance.

Figure A-24. BEP versus E b/No

performance of 5 Mb/s SOQPSK-TG.

1E-07

1E-06

1E-05

1E-04

1E-03

1E-02

1E-01

B E P

8 10 12 14Eb/No (dB)

5Mb/s SOQPSK-TG

10.0 Advanced Range Telemetry (ARTM) CPM Characteristics.

ARTM CPM is a quaternary signalingscheme in which the instantaneous frequency

of the modulated signal is a function of the

source data stream. The frequency pulses areshaped for spectral containment purposes. As

defined for this standard, the modulation index

alternates at the symbol rate between h=4/16

and h=5/16. The purpose of alternating between two modulation indices is to

maximize the minimum distance between data

symbols, which results in minimizing the biterror probability. These particular modulation

indices were selected as a good tradeoff between spectral efficiency and data-detection ability.

Figure A-25 shows the power spectrum of a 5 Mb/s ARTM CPM signal and Figure A-26 shows

the measured BEP versus E b/No. The maximum power level was about 19 dBc. The -60 dBc

Figure A-25. Power spectrum of 5 Mb/s

ARTM CPM.

-70

-60

-50

-40

-30

-20

-10

0

P o w e r ( d B c )


A-23

7/31/2019 IRIG_106_2009



bandwidth of this 5 Mb/s signal was

about 5.54 MHz. Note that the power spectrum of ARTM CPM is about 25%

narrower than that of SOQPSK-TG but

the BEP performance is worse. ARTM

CPM is also more susceptible to phasenoise than SOQPSK-TG.

Figure A-26. BEP versus E b/No performance of

5 Mb/s ARTM CPM.

1E-07

1E-06

1E-05

1E-04

1E-03

1E-02

1E-01

B E

P

8 10 12 14Eb/No (dB)

5 Mb/s multi-h CPM

11.0 PCM/FM

Pulse code modulation(PCM)/frequency modulation (FM) has

been the most popular telemetry

modulation since about 1970. Thismethod could also be called filtered

continuous phase frequency shift keying

(CPFSK). The RF signal is typicallygenerated by filtering the baseband non-

return-to-zero-level (NRZ-L) signal and

then frequency modulating a voltagecontrolled oscillator (VCO). The

optimum peak deviation is 0.35 timesthe bit rate (h=0.7) and a good choice for a premodulation filter is a multi-pole

linear phase filter with bandwidth equal

to 0.7 times the bit rate. Figure A-27 shows the power spectrum of a pseudo-random 5 Mb/sPCM/FM signal with peak deviation of 1.75 MHz and a 3.5 MHz linear phase low-pass filter.

Note that the spectrum is nearly flat from a frequency equal to 0.5 times the bit rate to afrequency equal to +0.5 times the bit rate. The power level near the center frequency is about –

22.5 dBc for a bit rate of 5 Mb/s and the standard spectrum analyzer settings.

Figure A-27. Power spectrum of 5 Mb/s PCM/FMsignal.

-70

-60

-50

-40

-30

-20

-10

0

P o w e r ( d B c )

-2 -1.5 -1 -0.5 0 0.5 1 1.5 2Relative Frequency (Bit Rate=1)

A-24

7/31/2019 IRIG_106_2009



Figure A-28 shows the BEP versusE b/No performance of 5 Mb/s PCM/FM

with a multi-symbol bit detector and

with 3 different receivers/detectors.

Note that an E b/No of about 9.5 dB isrequired to achieve a BEP of about 10-5

with the multi-symbol detector 13,

14

while an E b/No of about 12 to 14 dB istypically required to achieve a BEP of

about 10-5

with typical FM

demodulators and single symboldetectors. The PCM/FM modulation

method is fairly insensitive to phase

noise. Figure A-28. BEP versus E b/No performance of 5 Mb/s PCM/FM with multi-symbol bit detector and

three single symbol receivers/detectors.

1E-07

1E-06

1E-05

1E-04

1E-03

1E-02

B E P

6 8 10 12 14 16Eb/No (dB)

R1 Multi-symbol R2 R3

12.0 Valid Center Frequencies Near Telemetry Band Edges

The telemetry bands and associated frequency ranges identified in Table 2-1 identify the

frequency limits for each band. Telemetry transmitters can not be centered at the band edges dueto obvious out of band emissions. Bit rate to the transmitter and modulation scheme drive the

amount of separation required between the center frequency and the band edge. To determine

the amount of back-off required, the distance from the center of the spectral masks for eachmodulation scheme (see Chapter 2, paragraph 2.4.6) to the intersection of the mask and theabsolute limit of -25 dBm must be calculated. To illustrate this, see Figure A-29. Using thesecalculations will assure that outside the specified telemetry bands no part of the modulated

spectrum is over the absolute limit of -25 dBm.

13 Osborne W. P., Luntz M. B., “Coherent and Noncoherent Detection of CPFSK,” IEEE Transactions on

Communications, August 1974.

14 Geoghegan M. S., “Improving the Detection Efficiency of Conventional PCM/FM Telemetry by using a Multi-Symbol Demodulator”, Proceedings of the 2000 International Telemetry Conference, Volume XXXVI, 675-682,

San Diego CA, October 2000.

A-25

7/31/2019 IRIG_106_2009



Power Spectral Density Masks

-70

-60

-50

-40

-30

-20

-10

0

-15 -10 -5 0 5 10 15

Frequency Offset from Carrier (MHz)

d B c ( i n 3 0 k H z B W )

ARTM CPM

SOQPSK/FQPSK

PCM/FM

Figure A-29. Spectral Masks at -25 dBm.

The mask is calculated for all the modulation schemes at a bit rate of 5 Mbps with

transmitter output power assumed to be 10 W. This transmitter operating with PCM/FM as itsmodulation scheme requires a back-off from band edge of 9.98 MHz; since channelization in

these bands is limited to 0.5 MHz steps, this value is rounded up to 10 MHz. This sametransmitter operating with SOQPSK/FQPSK will require 4.67 MHz, rounded up to 5 MHz, of

back-off from band edge. Likewise, for ARTM-CPM the back-off is 3.54 MHz or 4 Mbps whenrounded up. To further this example, if this was an L-Band transmitter, viable carrier frequencies would be as specified in Table A-4.

TABLE A-4. L-BAND FREQUENCY RANGE (10 W, 5 MBPS)

Modulation Type Viable L-Band Frequency Range

PCM/FM 1445-1515 MHz

SOQPSK/FQPSK 1440-1520 MHz

ARTM CPM 1439-1521 MHz

A-26

7/31/2019 IRIG_106_2009



A-27

For a given modulation scheme and transmitter output power, as the bit rate increases, the

amount of back-off from the band edge also increases. Figure A-30 illustrates this point.

Required Band-Edge Backoff

0

5

10

15

20

25

30

35

40

0 5 10 15 20 25

Bit Rate (Mbps)

B a c k o f f f r o m B

a n d E d g e ( M H z )

PCM/FM

SOQPSK/FQPSK

ARTM CPM

Carrier Power (dBm):

40

Figure A-30. Bit Rate vs. Band edge Back-off.

For ease in making calculations as was done to create Figure A-30, an

Excel spreadsheet application can be used. Figure A-31 provides a view

of how the calculations are made using the formulas in the spreadsheet.The Excel file that created Figure A-31 (BandEdgeBackoff.xls) can be

downloaded and used for interactive calculations.

The input values for transmitter output power and bit rate are in the cells

highlighted in yellow. The amount of back-off will be displayed in thecells highlighted in light blue. Additionally, each telemetry band is

displayed with the useable carrier frequency range for each modulation

scheme given in blue.

http://bandedgebackoff.xls/

http://bandedgebackoff.xls/

7/31/2019 IRIG_106_2009


Telemetry Standard RCC Document 106-09, Appendix A, April, 2009

Valid Center Frequency, Band Edge Back-Off

Carrier Power or EIRP (dBm): 40 Input Number

Mask floor (at this nominal TX power): -65 dBc

Bit Rate (Mbps): 1.00 1.00

PCM/FM SOQPSK/FQPSK

K = -28 -61

m = 2 4

Bit Rate (bps) 1.00E+06 1.00E+06

Mask hits floor at offset of (MHz) 2.34 1.10

Band-edge backoff (MHz, rounded to nearest 0.5MHz) 2.5 1.5

Band Edge, Lower (MHz) 1435

Band Edge, Upper (MHz) 1525

Lower center freq. at this bit rate (MHz) 1437.5 1436.5

L-Band

Upper center freq. at this bit rate (MHz) 1522.5 1523.5




L-Band





S-Band





S-Band


A-2 8

Figure A-31. Valid center frequency, band edge back-off.

7/31/2019 IRIG_106_2009


Telemetry Standard RCC Document 106-09, Appendix A, April, 2009

**** END OF APPENDIX A ****

A-29

7/31/2019 IRIG_106_2009


Telemetry Standard RCC Document 106-09, Appendix B, April 2009

APPENDIX B

USE CRITERIA FOR FREQUENCY DIVISION MULTIPLEXING


1.0 General ..............................................................................................................B-12.0 FM Subcarrier Performance ..............................................................................B-1

3.0 FM Subcarrier Performance Tradeoffs..............................................................B-2

4.0 FM System Component Considerations............................................................B-35.0 Range Capability for FM Subcarrier Systems...................................................B-4

7/31/2019 IRIG_106_2009



ii


7/31/2019 IRIG_106_2009



APPENDIX B

USE CRITERIA FOR FREQUENCY DIVISION MULTIPLEXING

1.0 General

Successful application of frequency division multiplexing telemetry standards depends onrecognition of performance limits and performance tradeoffs, which may be required in

implementation of a system. The use criteria included in this Appendix are offered in this

context as a guide for orderly application of the standards, which are presented in Chapter 3. It is

the responsibility of the telemetry system designer to select the range of performance that willmeet data measurement requirements and at the same time permit operation within the limits of

the standards. A designer or user must also recognize the fact that even though the standards for

FM/FM multiplexing encompass a broad range of performance limits, tradeoffs such as dataaccuracy for data bandwidth may be necessary. Nominal values for such parameters as

frequency response and rise time are listed to indicate the majority of expected use and should

not be interpreted as inflexible operational limits. It must be remembered that systemperformance is influenced by other considerations such as hardware performance capabilities. In

summary, the scope of the standards together with the use criteria is intended to offer flexibility

of operation and yet provide realistic limits.

2.0 FM Subcarrier Performance

The nominal and maximum frequency response of the subcarrier channels listed in

Chapter 3 (Table 3-1A, Table 3-1B, Table 3-1C and Table 3-2) is 10 and 50 percent of the

maximum allowable deviation bandwidth. The nominal frequency response of the channelsemploys a deviation ratio of five. The deviation ratio of a channel is one-half the defined

deviation bandwidth divided by the cutoff frequency of the discriminator output filter.

2.1 The use of other deviation ratios for any of the subcarrier channels listed may be selectedby the range users to conform with the specific data response requirements for the channel. As a

rule, the rms signal-to-noise ratio (SNR) of a specific channel varies as the three-halves power of

that subcarrier deviation ratio.

2.2 The nominal and minimum channel rise times indicated in Chapter 3 (Table 3-1A,

Table 3-1B, Table 3-1C and Table 3-2) have been determined from the equation which states thatrise time is equal to 0.35 divided by the frequency response for the nominal and maximum

frequency response. The equation is normally employed to define 10 to 90 percent rise time for a

step function of the channel input signal. However, deviations from these values may be

encountered because of variations in subcarrier components in the system.

B-1

7/31/2019 IRIG_106_2009


7/31/2019 IRIG_106_2009



ud

ds

s

dc

ud

c

cd F

f

f

f

F

B

N

S

N

S 2 / 12 / 1

4

3(B-1)

where:

d N

S

= discriminator output signal-to-noise ratio (rms voltage ratio)

S

N c

= receiver carrier-to-noise ratio (rms voltage ratio)

Bc = carrier bandwidth (receiver IF bandwidth)

F ud = subcarrier discriminator output filter: 3-dB frequency

f s = subcarrier center frequency

f dc = carrier peak deviation of the particular subcarrier of interest

f ds = subcarrier peak deviation

If the RF carrier power is such that the thermal noise is greater than the intermodulation

noise, the above relation provides estimates accurate to within a few decibels. Additionalinformation is contained in RCC Document 119, Telemetry Applications Handbook.

3.6 The FM/FM composite-multiplex signal used to modulate the RF carrier may be a

proportional-bandwidth format, a constant-bandwidth format, or a combination of the two typesprovided only that guard bands allowed for channels used in a mixed format be equal to or

greater than the guard band allowed for the same channel in an unmixed format.

4.0 FM System Component Considerations

System performance is dependent on all components in the system. Neglecting theeffects of the RF and recording system, data channel accuracy is primarily a function of the

linearity and frequency response of the subcarrier oscillators and discriminators employed.

Systems designed to transmit data frequencies up to the nominal frequency responses shown inChapter 3 (Table 3-1A, Table 3-1B, Table 3-1C and Table 3-2) have generally well-known

response capabilities, and reasonable data accuracy estimates can be easily made. For data-

channel requirements approaching the maximum frequency response shown in Chapter 3

(Table 3-1A, Table 3-1B, Table 3-1C and Table 3-2), oscillator and discriminator characteristicsare less consistent and less well-defined, making data accuracy estimates less dependable.

4.1 The effect of the RF system on data accuracy is primarily in the form of noise because of

intermodulation at high RF signal conditions well above threshold. Under low RF signal

conditions, noise on the data channels is increased because of the degraded SNR existing in thereceiver.

B-3

7/31/2019 IRIG_106_2009



B-4

4.2 Intermodulation of the subcarriers in a system is caused by characteristics such as amplitudeand phase nonlinearities of the transmitter, receiver, magnetic tape recorder/reproducer, or other

system components required to handle the multiplex signal under the modulation conditions

employed. In systems employing pre-emphasis of the upper subcarriers, the lower subcarriers mayexperience intermodulation interference because of the difference frequencies of the high-

frequency and high-amplitude channels.

4.3 The use of magnetic tape recorders for recording a subcarrier multiplex may degrade the

data channel accuracy because of the tape speed differences or variations between record andplayback. These speed errors can normally be compensated for in present discriminator systems

when the nominal response rating of the channels is employed and a reference frequency is

recorded with the subcarrier multiplex.

5.0 Range Capability for FM Subcarrier Systems

The following subparagraphs outline additional range capabilities:

5.1 Receivers and Tape Recorders. The use of subcarrier frequencies greater than 2 MHz may

require tape recorders of a greater capability than are in current use at some ranges. It isrecommended that users, who anticipate employing any of the above channels at a range, check

the range's capability at a sufficiently early date to allow procurement of necessary equipment.

5.2 Discriminator Channel Selection Filters. Inclusion of the higher frequency proportional-bandwidth channels and the constant-bandwidth channels may require the ranges to acquire

additional band selection filters. In addition to referencing Chapter 3 (Table 3-1A, Table 3-1B,

Table 3-1C and Table 3-2) for acquiring channel-selector filters, consideration should also begiven to acquiring discriminators corresponding to the predetection carrier frequencies shown inAppendix D, Table D-9. In applications where minimum time delay variation within the filter is

important, such as tape speed compensation or high-rate PAM or PCM, constant-delay filter

designs are recommended.

**** END OF APPENDIX B ****

7/31/2019 IRIG_106_2009


7/31/2019 IRIG_106_2009


Telemetry Standard RCC Document 106-09, Appendix C, April 2009

ii


7/31/2019 IRIG_106_2009



APPENDIX C

PCM STANDARDS (ADDITIONAL INFORMATION AND RECOMMENDATIONS)

1.0 Bit Rate Versus Receiver Intermediate-Frequency Bandwidth

The following subparagraphs contain information about selection of receiver

intermediate-frequency (IF) bandwidths. Additional information is contained in RCC document

119, Telemetry Applications Handbook.

1.1 The standard receiver IF bandwidth values are listed in Table 2-1. Not all bandwidths are

available on all receivers or at all test ranges. Additional bandwidths may be available at sometest ranges. The IF bandwidth, for data receivers, should typically be selected so that 90 to 99

percent of the transmitted power spectrum is within the receiver 3-dB bandwidth.

1.2 For reference purposes, in a well-designed PCM/FM system (NRZ-L data code) with

peak deviation equal to 0.35 times the bit rate and an IF bandwidth (3 dB) equal to the bit rate, a

receiver IF signal-to-noise ratio (SNR) of approximately 13 dB will result in a bit error

probability (BEP) of 10-6

. A 1-dB change in this SNR will result in approximately an order of magnitude change in the BEP. The relationship between BEP and IF SNR in a bandwidth equal

to the bit rate is illustrated in Figure C-1 for IF bandwidths equal to the bit rate and 1.5 times the

bit rate. An approximate expression for the BEP is

BEP = 0.5 e(k•SNR)

(C-1)

where:

k 0.7 for IF bandwidth equal to bitrate

k 0.65 for IF bandwidth equal to 1.2times bit rate

k 0.55 for IF bandwidth equal to 1.5times bit rate

SNR = IF SNR•IF bandwidth/bit rate.

Other data codes and modulation

techniques have different BEP versus SNR

performance characteristics.

1.3 It is recommended that the maximum period between bit transitions be 64-bit

intervals to ensure adequate bit synchronization.Table C-1 contains recommended frame

synchronization patterns for general use in PCM telemetry.

Figure C-1. BEP vs IF SNR in bandwidth= bit rate for NRZ-L PCM/FM.

C-1

7/31/2019 IRIG_106_2009



C-2

2.0 Recommended PCM Synchronization Patterns

Table C-1 contains recommended frame synchronization patterns for general use in PCM

telemetry. Patterns are shown in the preferred order of transmission with "111" being the first bit

sequence transmitted. This order is independent of data being LSB or MSB aligned. Thetechnique used in the determination of the patterns for lengths 16 through 30 was essentially that

of the patterns of 2n binary patterns off a given length, n, for that pattern with the smallest total

probability of false synchronization over the entire pattern overlap portion of the ground stationframe synchronization.

1The patterns for lengths 31 through 33 were obtained from a second

source.2

3.0 Spectral and BEP Comparisons for NRZ and Bi3

Figure C-2 shows the power spectral densities of baseband NRZ and Bi codes withrandom data. These curves were calculated using the equations presented below. Figure C-3

presents the theoretical bit error probabilities versus signal-to-noise ratio for the level, mark, and

space versions of baseband NRZ and Bi codes and also for RNRZ-L. The noise is assumed to be additive white gaussian noise.

2

2sin

fT

fT DENSITY SPECTRAL NRZ

(C-2)

2

4

2/

2/sin

fT

fT DENSITY SPECTRAL Bi

(C-3)

where T is the bit period.

1

A more detailed account of this investigation can be found in a paper by J. L. Maury, Jr. and J. Styles,"Development of Optimum Frame Synchronization Codes for Goddard Space Flight Center PCM Telemetry

Standards," in Proceedings of the National Telemetering Conference, June 1964.2 The recommended synchronization patterns for lengths 31 through 33 are discussed more fully in a paper by E. R.

Hill, "Techniques for Synchronizing Pulse-Code Modulated Telemetry," in Proceedings of the National

Telemetering Conference, May 1963.3 Material presented in paragraph 3.0 is taken from a study by W. C. Lindsey (University of Southern California), Bit Synchronization System Performance Characterization, Modeling and Tradeoff Study, Naval Missile Center Technical Publication.

7/31/2019 IRIG_106_2009


Telemetry Standard RCC Document 106-09, Appendix C, April, 2009

C - 3

TABLE C-1. OPTIMUM FRAME SYNCHRONIZATION PATTERNS FOR PC

Pattern

LengthPatterns

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

111

111

111

111

111

111

111

111

111

111

111

111

111

111

111

111

111

111

010

100

100

110

011

011

100

101

110

110

110

110

101

101

110

111

111

110

111

110

110

011

011

101

110

011

101

010

100

101

011

011

101

100

100

111

001

101

101

001

110

001

110

100

111

110

110

101

110

110

111

110

110

010

000

000

000

010

001

011

101

110

001

111

101

001

010

011

001

111

101

011

0

00

000

000

000

000

000

100

100

000

100

100

110

001

100

110

100

101

0

00

000

000

000

100

100

110

110

011

101

110

101

101

001

0

00

000

000

000

000

000

000

100

000

000

010

7/31/2019 IRIG_106_2009



Figure C-2. Spectral densities of random NRZ and Bi codes.

Figure C-3. Theoretical bit error probability performance

for various baseband PCM signaling techniques(perfect bit synchronization assumed).

C-4

7/31/2019 IRIG_106_2009



C-5

4.0 PCM Frame Structure Examples

Figures C-4, C-5, and C-6 show examples of allowable PCM frame structures. In each

example, the Minor Frame Sync Pattern is counted as one word in the minor frame. The first word

after the Minor Frame Sync Pattern is word 1.

Figures C-5 and C-6 show the preferred method of placing the subframe ID counter in the

minor frame. The counter is placed before the parameters that are referenced to it.

Major Frame Length is as follows:

Figure C-4: Major Frame Length = Minor Frame Maximum

Length.

Figure C-5: Major Frame Length = Minor Frame MaximumLength multiplied by Z.

Figure C-6: Major Frame Length = Minor Frame Maximum

Length multiplied by Z.

7/31/2019 IRIG_106_2009



Minor Frame Maximum Length, N Words or B Bits

Class I: Shall not exceed 8192 bits nor exceed 1024 words

Class II: 16 384 Bits

Word

1

Word

2

Word

3

Word

4

Word

5

Word

6

Word

7

Word

8

Word

9

Word

10...

Minor

Frame

SyncPattern

Param

A0

Param

A1

Param

A2

Param

A3

Param

A4

Param

A2

Param

A5

Param

A6

Param

A2

Param

A7...

Parameters A0, A1, A3, A4, A5, A6, ... A(X) are sampled once each Minor Frame.

Parameter A2 is supercommutated on the Minor Frame.The rate of A2 is equal to the number of samples multiplied by the Minor Frame Rate.

C -

6

Figure C-4. Major Frame Length = Minor Frame Maximum Length.

7/31/2019 IRIG_106_2009



C -

7



Class II: 16 384 bits

Word

1

Word

2

Word

3

Word

4

Word

5

Word

6

Word

7

Word

8

Word

9

Word

10•

•

Minor Frame

Sync Pattern

SFID

=1

FFI Param

A2

Param

B1

Param

A4

Param

A2

Param

A5

Param

A6

Param

A2

Param

C1•

SFID

=2

Param

B2

Par

C2

am

SFID=3

ParamB3

Par amC3

SFID=4

ParamB4

Par amC4

SFID=5 ParamB2 Par C5am

SFID

=6

Param

B5

Par

C6

am

SFID=7

ParamB6

Par amC7

.

.

....

.

.

....

.

.

.Param

B2

Param

C(Z-1)

Minor Frame

Sync Pattern

SFID

=Z

FFI Param

A2

Param

BZ

Param

A4

Param

A2

Param

A5

Param

A6

Param

A2

Param

CZ•

The Frame Format Identifier (Word 2) is shown in the preferred position as the first word following the ID counter.

Parameters B1, B3, B4, B5, . . . BZ, and C1, C2, C3, . . . CZ are sampled once each Subframe, at 1/Z multiplied by thParameter B2 is supercommutated on the Subframe and is sampled at less than the Minor Frame rate, but greater than

Figure C-5. Major Frame Length = Minor Frame Maximum Length multipl

7/31/2019 IRIG_106_2009




C -

8


Class II: 16 384 bits

Word

1

Word

2

Word

3

Word

4

Word

5

Word

6

Word

7

Word

8

Word

9

Wo

1

Minor Frame

Sync Pattern

SFID1

=1

FFI Param

A2

SFID2

=1

Param

B1

Param

A2

Param

A5

Param

E1

Param

A2

Par

C

SFID1

=2

SFID2

=2

Param

B2

Param

E2

Par

C

SFID1

=3

SFID2

=3

Param

B3

Param

E3

Par

C

SFID1

=4

SFID2

=4

Param

B4

Param

E4

Par

C

SFID1

=5

SFID2

=5

Param

B2

Param

E5

Par

CSFID1

=6

.

.

.Param

B5

.

.

.Par

C

SFID1

=7

SFID2

=D

Param

B6

Param

ED

Par

C...

.

.

.

.

.

.

.

.

....

.

.

. ParamB2

.

.

. ParamC(Z-

Minor FrameSync Pattern

SFID1=Z

FFI ParamA2

SFID2=N

ParamBZ

ParamA2

ParamA5

ParamEN

ParamA2

ParC

SFID1 and SFID2 and subframe counters.

SFID1 has a depth Z≤ 256; SFID2 has a depth D which is <Z. Z divided by D is not an integer.

Location of the B and C parameters are given by the Minor Frame word number and the SFID1 counter.Location of the E parameters are given by the Minor Frame word number and the SFID2 counter.

Figure C-6. Major Frame Length = Minor Frame Maximum Length multipl

**** END OF APPENDIX C ****

7/31/2019 IRIG_106_2009


Telemetry Standard RCC Document 106-09, Appendix D, April 2009

APPENDIX D

MAGNETIC TAPE RECORDER AND REPRODUCER INFORMATION AND USE

CRITERIA


1.0 Other Instrumentation Magnetic Tape Recorder Standards ........................... D-1

2.0 Double-Density Longitudinal Recording........................................................ D-1

3.0 Serial High-Density Digital Recording (HDDR)............................................ D-84.0 Head Parameters ........................................................................................... D-15

5.0 Record Level................................................................................................. D-15

6.0 Tape Crossplay Considerations .................................................................... D-16

7.0 Standard Tape Signature Procedures ............................................................ D-168.0 Equipment Required for Swept-Frequency Procedures................................ D-19

9.0 Fixed-Frequency Plus White Noise Procedure............................................. D-19

10.0 Signature Playback and Analysis.................................................................. D-2011.0 Recording and Playback Alignment Procedures .......................................... D-21

12.0 General Considerations for Longitudinal Recording.................................... D-23

13.0 Recorded Tape Format.................................................................................. D-2314.0 Head and Head Segment Mechanical Parameters ........................................ D-33

15.0 Head Polarity ................................................................................................ D-33

16.0 Magnetic Tape and Reel Characteristics ...................................................... D-34

17.0 Direct Record and Reproduce Systems ........................................................ D-3418.0 Timing, Predetection, and Tape Signature Recording.................................. D-36

19.0 FM Record Systems...................................................................................... D-38

20.0 PCM Recording ............................................................................................ D-40

21.0 Preamble Recording for Automatic or Manual Recorder Alignment........... D-4522.0 Magnetic Tape Standards: General............................................................... D-45

23.0 Definitions .................................................................................................... D-4824.0 General Requirements for Standard Instrumentation Tapes and Reels ........ D-51

25.0 General Characteristics of Instrumentation Tapes and Reels ....................... D-52

26.0 Physical Characteristics of Instrumentation Tapes and Reels ...................... D-55

27.0 Instrumentation Tape Magnetic and Electrical Characteristics .................... D-55

7/31/2019 IRIG_106_2009



ii

LIST OF FIGURES

Figure D-1. Record and reproduce head and head segment identification and

location (7-track interlaced system)................................................................ D-3

Figure D-2. Randomizer block diagram........................................................................... D-10

Figure D-3. Randomized NRZ-L decoder block diagram................................................ D-12Figure D-4. Random PCM power spectra. ....................................................................... D-13

Figure D-5a. Bi-L at bit packing density of 15 kb/in....................................................... D-14Figure D-5b. RNRZ-L at bit packing density of 25 kb/in. ................................................. D-14

Figure D-6. Tape crossplay. ............................................................................................. D-17

Figure D-7. Square wave responses. ................................................................................ D-22Figure D-7a. Recorded tape format.................................................................................... D-29

Figure D-7b. Head and head segment mechanical parameters........................................... D-30

Figure D-7c. Record and reproduce head and head segment identificationand location (N-track interlaced system). ..................................................... D-31

Figure D-8. PCM record and reproduce configuration. ................................................... D-32

Figure D-9. Serial high-density digital record and reproduce. ......................................... D-43

LIST OF TABLES

Table D-1. Dimensions - Recorded Tape Format 7 Tracks InterlacedOn 12.7-Mm (1/2 In.) Wide Tape................................................................... D-4

Table D-2. Dimensions - Recorded Tape Format 14 Tracks Interlaced

On 12.7-Mm (1/2 In.) Wide Tape................................................................... D-5 Table D-3. Dimensions - Recorded Tape Format 42 Tracks Interlaced

On 25.4-Mm (1-In.) Wide Tape...................................................................... D-6

Table D-4. Record And Reproduce Parameters.............................................................. D-25

Table D-5. Dimensions – Recorded Tape Format 14 Tracks InterlacedOn 25.4 Mm (1 In.) Wide Tape .................................................................... D-26 Table D-6. Dimensions – Recorded Tape Format 14 Tracks In-Line

On 25.4 Mm (1 In.) Wide Tape .................................................................... D-27

Table D-7. Dimensions – Recorded Tape Format 14 Tracks InterlacedOn 25.4 Mm (1 In.) Wide Tape(1)................................................................ D-28

Table D-8. Constant-Amplitude Speed-Control Signals................................................. D-37

Table D-9. Predetection Carrier Parameters ................................................................... D-38

Table D-10. Wide Band And Double Density Fm Record Parameters............................. D-39 Table D-11. Maximum Recommended Bit Rates, Post-Detection Recording................. D-41

Table D-12. Maximum Recommended Bit Rates ............................................................. D-42

Table D-13. Suggested Tape Requirement Limits............................................................ D-46 Table D-13a. Suggested Wavelength Response Requirements .......................................... D-47

Table D-14. Durability Signal Losses............................................................................... D-48

Table D-15. Tape Dimensions .......................................................................................... D-53 Table D-16. Measurement Wavelengths........................................................................... D-56

7/31/2019 IRIG_106_2009



APPENDIX D

MAGNETIC TAPE RECORDER AND REPRODUCER INFORMATION AND USE

CRITERIA

1.0

Other Instrumentation Magnetic Tape Recorder Standards

The X3B6 Committee of the American National Standards Institute (ANSI) and the

International Organization for Standardization (ISO) have prepared several standards for magnetic tape recording of instrumentation data. Documents may be obtained by contacting the

ANSI web site (http://webstore.ansi.org).

1.1 Documentation applicable to this Appendix is identified in the following subparagraphs.

1.1.1 ISO 1860 (1986), Information Processing - Precision reels for magnetic tape used ininterchange instrumentation applications.

1.1.2 ISO 6068 (1985), Information Processing - Recording characteristics of instrumentation

magnetic tape (including telemetry systems) - interchange requirements.

1.1.3 ISO/IEC TR 6371:1989, Information Processing - Interchange practices and test methods

for unrecorded instrumentation magnetic tape.

1.1.4 ISO/IEC 8441/1:1991, Information technology - High Density Digital Recording

(HDDR) - Part 1: Unrecorded magnetic tape for HDDR applications.

1.1.5 ISO/IEC 8441/2:1991, Information technology - High Density Digital Recording

(HDDR) - Part 2: Guide for interchange practice.

1.1.6 ANSI INCITS 175-1999, 19 mm Type ID-1 Recorded Instrumentation - Digital Cassette

Tape Format (formerly ANSI X3.175-1990).

2.0 Double-Density Longitudinal Recording

Wide band double-density analog recording standards allowing recording of up to 4 MHz

signals at 3048 mm/s (120 in./s) are included in these standards. For interchange purposes, either

narrow track widths 0.635 mm (25 mils) must be employed, or other special heads must be used.These requirements are necessary because of the difficulty in maintaining individual head-

segment gap-azimuth alignment across a head close enough to keep each track's response within

the ±2-dB variation allowed by the standards. Moreover, at the lower tape speeds employed indouble-density recording, the 38-mm (1.5-in.) spacing employed in interlaced head assembliesresults in interchannel time displacement variations between odd and even tracks that may be

unacceptable for some applications. Therefore, it was decided that a 14-track in-line

configuration on 25.4-mm (1-in.) tape should be adopted as a standard. This configurationresults in essentially the same format as head number one of the 28-track interlaced configuration

in the standards.

D-1

http://webstore.ansi.org/

http://webstore.ansi.org/

7/31/2019 IRIG_106_2009



D-2

2.1 The 14-track interlaced heads are not compatible with tapes produced on an in-line

standard configuration. If tapes must be interchanged, either a cross-configuration dubbing may be required or a change of head assemblies on the reproducing machine is necessary.

2.2 High energy magnetic tape is required for double-density systems. Such tapes are

available but may require special testing for applications requiring a low number of dropouts per track.

2.2.1 Other Track Configurations. The previously referenced standards in paragraph 1.0 include configurations resulting in 7, 14, and 21 tracks in addition to the 14-track and 28-track

configurations listed in this Appendix. The high-density digital recording (HDDR) standards

also reference an 84-track configuration on 50.8-mm (2in.) tape. Figure D-1 and Table D-1 show the 7-track on 12.7-mm (1/2-in.) tape, Table D-2 shows the 14-track on 12.7-mm (1/2-in.)

tape, and Table D-3 shows the 42-track on 25.4-mm (1in.) tape configurations.

2.2.2 High-Density PCM Recording. High-density digital recording systems are available

from most instrumentation recorder manufacturers. Such systems will record at linear packingdensities of 33 000-bits-per-inch or more per track. Special systems are available for error

detection and correction with overhead penalties depending on the type and the sophistication of the system employed. The HDDR documents listed in paragraph 1.0 of this Appendix reference

six different systems that have been produced; others are available.

7/31/2019 IRIG_106_2009



D- 3

Figure D-1. Record and reproduce head and head segment identification and location (

7/31/2019 IRIG_106_2009



TABLE D-1. DIMENSIONS - RECORDED TAPE FORMAT

7 TRACKS INTERLACED ON 12.7-MM (1/2 IN.) WIDE TAPE

(Refer to Figure D-7a)

Parameters Millimeters Inches

Maximum Minimum

Track Width 1.397 1.143 0.050 ±0.005

Track Spacing 1.778 0.070

Head Spacing:

Fixed Heads 38.125 38.075 1.500 ±0.001

Adjustable Heads 38.151 38.049 1.500 ±0.002

Edge Margin, Minimum 0.127 0.005Reference Track

Location 1.067 0.965 0.040 ±0.002

Track Location

Tolerance 0.051 0.051 ±0.002

Location of nth track

Track Number Millimeters Inches

Maximum Minimum1 (Reference) 0.000 0.000 0.000

2 1.829 1.727 0.070

3 3.607 3.505 0.140

4 5.385 5.283 0.210

5 7.163 7.061 0.280

6 8.941 8.839 0.350

7 10.719 10.617 0.420

D-4

7/31/2019 IRIG_106_2009




14 TRACKS INTERLACED ON 12.7-MM (1/2 IN.) WIDE TAPE



Maximum Minimum

Track Width 0.660 0.610 0.025 ±0.001


Head Spacing:

Fixed Heads 38.125 38.075 1.500 ±0.001


Edge Margin, Minimum 0.127 0.005

Reference Track

Location 0.546 0.470 0.0200

±0.001

Track Location

Tolerance 0.038 0.038 ±0.0015

Location of nth

track


Maximum Minimum

1 (Reference) 0.000 0.000 0.000

2 0.927 0.851 0.035

3 1.816 1.740 0.070

4 2.705 2.629 0.105

5 3.594 3.518 0.140

6 4.483 4.407 0.175

7 5.372 5.292 0.210

8 6.261 6.185 0.245

9 7.150 7.074 0.28010 8.039 7.963 0.315

11 8.928 8.852 0.350

12 9.817 9.741 0.385

13 10.706 10.630 0.420

14 11.595 11.519 0.455

D-5

7/31/2019 IRIG_106_2009




42 TRACKS INTERLACED ON 25.4-MM (1-IN.) WIDE TAPE



Maximum Minimum

Track Width 0.483 0.432 0.018 ±0.001


Head Spacing:

Fixed Heads 38.125 38.075 1.500 ±0.001


Edge Margin, Minimum 0.305 0.012

Reference Track

Location 0.737 0.660 0.0275±0.015

Track Location

Tolerance 0.025 0.025 ±0.0000



Maximum Minimum

1 (Reference) 0.000 0.000 0.000

2 0.610 0.559 0.0233 1.194 1.143 0.046

4 1.778 1.727 0.069

5 2.362 2.311 0.092

6 2.946 2.896 0.115

7 3.531 3.480 0.138

8 4.115 4.064 0.161

9 4.699 4.648 0.184

10 5.283 5.232 0.207

11 5.867 5.817 0.23012 6.452 6.401 0.253

13 7.036 6.985 0.276

14 7.620 7.569 0.299

15 8.204 8.153 0.322

16 8.788 8.738 0.345

(Continued on next page)

D-6

7/31/2019 IRIG_106_2009



TABLE D-3 (cont’d.) DIMENSIONS - RECORDED TAPE FORMAT

42 Tracks Interlaced on 25.4-mm (1-in.) Wide Tape




Maximum Minimum

17 9.373 9.322 0.368

18 9.957 9.906 0.391

19 10.541 10.490 0.414

20 11.125 11.074 0.437

21 11.709 11.659 0.460

22 12.294 12.243 0.48323 12.878 12.827 0.506

24 13.462 13.411 0.529

25 14.046 13.995 0.552

26 14.630 14.580 0.575

27 15.215 15.164 0.598

28 15.799 15.748 0.621

29 16.383 16.332 0.664

30 16.967 16.916 0.667

31 17.551 17.501 0.690

32 18.136 18.085 0.713

33 18.720 18.660 0.736

34 19.304 19.253 0.759

35 19.888 19.837 0.782

36 20.472 20.422 0.805

37 21.057 21.006 0.828

38 21.641 21.590 0.851

39 22.225 22.174 0.87440 22.809 22.758 0.897

41 23.393 23.343 0.920

42 23.978 23.927 0.943

D-7

7/31/2019 IRIG_106_2009



3.0 Serial High-Density Digital Recording (HDDR)

The following subparagraphs give some background for selecting the bi-phase and

randomized non-return-to-zero-level (RNRZ-L) systems specified in subparagraph 20.3, of this

document.

3.1 Serial HDDR is a method of recording digital data on a magnetic tape where the digital

data is applied to one track of the recording system as a bi-level signal. The codes recommended

for serial HDDR recording of telemetry data are Bi-L and randomized NRZ-L (RNRZ-L) (refer

to paragraph 20.0).

3.2 In preparing paragraph 20.0, the following codes were considered: Delay Modulation

(Miller Code), Miller Squared, Enhanced NRZ, NRZ Level, NRZ Mark, and NRZ Space. Thesecodes are not recommended for interchange applications at the bit rates given in paragraph 20.0.

3.3 The properties of the Bi-L and RNRZ-L codes relevant to serial HDDR and the methods

for generating and decoding RNRZ-L are described next. Recording with bias is required for interchange applications because reproduce amplifier phase and amplitude equalization

adjustments for tapes recorded without bias usually differ from those required for tapes recordedwith bias.

3.4 The Bi-L and RNRZ-L codes were selected for this standard because the "level"versions are easier to generate and are usually available as outputs from bit synchronizers.

"Mark" and "Space" codes also have about twice as many errors as the level codes for the samesignal-to-noise ratio (SNR). If polarity insensitivity is a major consideration, agreement between

interchange parties should be obtained before these codes are used.

3.5 Some characteristics of the Bi-L code favorable to serial HDDR are listed in thefollowing subparagraphs.

3.5.1 Only a small proportion of the total signal energy occurs near dc.

3.5.2 The maximum time between transitions is a 1-bit period.

3.5.3 The symbols for one and zero are antipodal, meaning that the symbols are exactopposites of each other. Therefore, the bit error probability versus SNR performance is

optimum.

3.5.4 The Bi-L can be decoded using existing bit synchronizers.

3.5.5 The Bi-L is less sensitive to misadjustments of bias and reproducer equalizers than most

other codes.

3.5.6 The Bi-L performs well at low tape speeds and low bit rates.

D-8

7/31/2019 IRIG_106_2009



3.6 The most unfavorable characteristic of the Bi-L code is that it requires approximatelytwice the bandwidth of NRZ. Consequently, the maximum bit packing density that can be

recorded on magnetic tape is relatively low.

3.7 Characteristics of the RNRZ-L code which favor its use for serial HDDR are included in

the following subparagraphs.

3.7.1 The RNRZ-L requires approximately one-half the bandwidth of Bi-L.

3.7.2 The symbols for one and zero are antipodal; therefore, the bit error probability versusSNR performance is optimum.

3.7.3 The RNRZ-L decoder is self-synchronizing.

3.7.4 The RNRZ-L data can be bit synchronized and signal conditioned using existing bit

synchronizers with the input code selector set to NRZ-L.

3.7.5 The RNRZ-L code is easily generated and decoded.

3.7.6 The RNRZ-L data can be easily decoded in the reverse mode of tape playback.

3.7.7 The RNRZ-L data are bit detected and decoded using a clock at the bit rate. Therefore,

the phase margin is much larger than that of codes that require a clock at twice the bit rate for bitdetection.

3.7.8 The RNRZ-L code does not require overhead bits.

3.8 Unfavorable characteristics of the RNRZ-L code for serial HDDR are described in thefollowing subparagraphs.

3.8.1 Long runs of bits without a transition are possible, although the probability of occurrenceis low, and the maximum run length can be limited by providing transitions in each data word.

3.8.2 Each isolated bit error that occurs after the data has been randomized causes three biterrors in the derandomized output data.

3.8.3 The decoder requires 15 consecutive error-free bits to establish and reestablish error-free

operation.

3.8.4 The RNRZ-L bit stream can have a large low frequency content. Consequently,

reproducing data at tape speeds which produce PCM bit rates less than 200 kb/s is notrecommended unless a bit synchronizer with specially designed dc and low frequency restoration

circuitry is available.

D-9

7/31/2019 IRIG_106_2009



3.9 Randomizer for RNRZ-L. the randomizer is implemented with a network of shift

registers and modulo-2 adders (exclusive-OR gates). The RNRZ-L bit stream is generated byadding (modulo-2) the reconstructed NRZ-L PCM data to the modulo-2 sum of the outputs of the

14th and 15th stages of a shift register. The output RNRZ-L stream is also the input to the shift

register (see Figure D-2).

Figure D-2. Randomizer block diagram.

1 2 315 Stage

Shift Register

13 14 15NRZ-L Input

+

A

Boolean Expression:

D = A B C

Output

D

+

B C

Bit Rate Clock Input

RNRZ-L

3.9.1 The properties of an RNRZ-L bit stream are similar to the properties of a pseudo-randomsequence. A 15-stage RNRZ-L encoder will generate a maximal length pseudo-random

sequence of 2151 (32,767) bits if the input data consists only of zeros and there is at least a

single one in the shift register. A maximal length pseudo-random sequence is also generated

when the input data consists only of ones and the shift register contains at least a single zero.

However, if the shift register contains all zeros at the moment that the input bit stream is allzeros, the RNRZ-L output bit stream will also be all zeros. The converse is also true, meaning

that when the shift register is filled with ones and the input bit stream is all ones, the RNRZ-L

output bit stream will also be all ones. In these two cases, the contents of the shift register doesnot change and the output data is not randomized.

However, the randomizer is not permanently locked-up in this state because a change in

the input data will again produce a randomized output. In general, if the input bit stream

D-10

7/31/2019 IRIG_106_2009



contains runs of X bits without a transition with a probability of occurrence of p(X), the output

will contain runs having a length of up to (X+15) bits with a probability equal to (2-15

• p(X)).Therefore, the output can contain long runs of bits without a transition, but the probability of

occurrence is low.

3.9.2 The RNRZ-L bit stream is decoded (derandomized) by adding (modulo-2) thereconstructed RNRZ-L bit stream to the modulo-2 sum of the outputs of the 14th and 15th stages

of the shift register. The reconstructed RNRZ-L bit stream is the input to the shift register (see

Figure D-3). The RNRZ-L data that is reproduced using the reverse playback mode of operationis decoded by adding (modulo-2) the reconstructed RNRZ-L bit stream to the modulo-2 sum of

the outputs of the 1st and 15th stages of the shift register (see Figure D-3). The net effect is that

the decoding shift register runs "backwards" with respect to the randomizing shift register.

3.9.3 Although the RNRZ-L decoder is self-synchronizing, 15 consecutive error-free bits must

be loaded into the shift register before the output data will be valid. A bit slip will cause thedecoder to lose synchronization, and 15 consecutive error-free data bits must again be loaded

into the shift register before the output data is valid. The decoded output data, although correct,will contain the bit slip causing a shift in the data with respect to the frame synchronization

pattern. Therefore, frame synchronization must be reacquired before the output providesmeaningful data.

3.9.4 The RNRZ-L decoding system has an error multiplication factor of 3 for isolated biterrors (separated from adjacent bit errors by at least 15 bits). An isolated bit error introduced

after randomization will produce 3 errors in the output data; the original bit in error, plus two

additional errors 14 and 15 bits later. In addition, a burst of errors occurring after the data has been randomized will produce a burst of errors in the derandomized output. The number of

errors in the output depends on the distribution of errors in the burst and can be greater than,equal to, or less than the number of errors in the input to the derandomizer. However, the

derandomization process always increases the number of bits between the first and last error in

the burst by 15. Errors introduced prior to randomization are not affected by either therandomizer or the derandomizer. The reverse decoder has the same bit error properties as the

forward decoder.

3.9.5 Input data containing frequent long runs of bits without transitions creates potential dcand low frequency restoration problems in PCM bit synchronizers because of the low frequency

cutoff of direct recorder and reproducer systems. The restoration problem can be minimized by

reproducing the data at tape speeds that produce a bit rate for which the maximum time betweentransitions is less than 100 microseconds. Additional methods of minimizing these effects

include selecting bit synchronizers containing special dc and low frequency restoration circuitry

or recording data using Bi-L code.

D-11

7/31/2019 IRIG_106_2009



D-12

Bit Rate Clock Input

15 - Stage

Shift Register 1 2 3 13 14 15

Reverse

RNRZ-L Data

Input From

Bit Sync

Playback

Forward

Playback

D BC

A1

Decoded Data

Output (NRZ-L)Boolean Expression:

With input data A into randomizer,

Error-Free RNRZ-L Data, D = A B C (see Figure D-2)

A1

= D B C = A B C B C

= A B B C C But B B = 0

C C = 0

Therefore:

A1

= A 0 0 = A

Figure D-3. Randomized NRZ-L decoder block diagram.

7/31/2019 IRIG_106_2009



3.9.6 The power spectra of the RNRZ-L and Bi-L codes are shown below in Figure D-4. The power spectral density of RNRZ-L is concentrated at frequencies that are less than one-half the

bit rate. The power spectral density of Bi-L is concentrated at frequencies in a region around0.75 times the bit rate. The concentration of energy in the low-frequency region (when using the

RNRZ-L code) has the effect of reducing the SNR as well as creating baseline wander, which the

bit synchronizer must follow. Therefore, reproducing data at tape speeds which produce PCM bit rates of less than 200 kb/s is not recommended when using RNRZ-L unless a bit synchronizer

with specially designed dc and low frequency restoration circuitry is available.

3.9.7 Alignment of the reproducer system is very important to reproducing high quality PCMdata (i.e. data with the lowest possible bit error probability). A PCM signature using the

standard 2047-bit pseudo-random pattern, recorded on the leader or the trailer tape, provides a

good method for reproducer alignment. When a pseudo-random bit error detection system is notavailable or when a PCM signature signal is not recorded, the recommended procedure for

reproducer alignment involves the use of the eye pattern technique. The eye pattern is the result

of superpositioning the zeros and ones in the PCM bit stream. The eye pattern is displayed on an

oscilloscope by inserting the raw reproduced bit stream into the vertical input and thereconstructed bit-rate clock into the external synchronization input of the oscilloscope. The

reproducer head azimuth, amplitude equalizers, and phase equalizers are then adjusted to produce the eye pattern with the maximum height and width opening.

Figure D-4. Random PCM power spectra.

D-13

7/31/2019 IRIG_106_2009



3.9.8 Sample eye patterns are shown in Figure D-5a and Figure D-5b. Figure D-5a shows a

Bi-L eye pattern at a recorded bit packing density of 15 kb/in (450 kb/s at 30 in./s).Figure D-5b shows an RNRZ-L eye pattern at a recorded bit packing density of 25 kb/in

(750 kb/s at 30 in/s).

Figure D-5a. Bi-L at bit packing density of 15 kb/in.

Figure D-5b. RNRZ-L at bit packing density of 25 kb/in.

D-14

7/31/2019 IRIG_106_2009



4.0 Head Parameters

The following subparagraphs describe the head parameters.

4.1 Gap Scatter. Refer to the definitions in paragraph 6.2 in Chapter 6. Gap scatter containscomponents of azimuth misalignment and deviations from the average line defining the azimuth.

Since both components affect data simultaneity from record to reproduce, the gap scatter

measurement is the inclusive distance containing the combined errors. Because azimuth

adjustment affects the output of wide band systems, a 5.08-m (0.0002-in.) gap scatter is

allowed for such recorders and reproducers. A 2.54-m (0.0001-in.) gap scatter is recommendedfor fixed-head systems (see Figure D-7c).

4.2 Head Polarity. The requirement that a positive pulse at a record amplifier input generate

a south-north-north-south magnetic sequence and that a south-north-north-south magnetic

sequence on tape produce a positive pulse at the reproduce amplifier output, still leaves twointerdependent parameters unspecified. These parameters are (1) polarity inversion or non-

inversion in record and playback amplifiers and (2) record or playback head winding sense. For the purpose of head replacement, it is necessary that these parameters be determined by the user

so that an unsuspected polarity inversion, on tape or off tape, will not occur after heads arereplaced.

5.0 Record Level

The standard record level is established as the input level of a sinusoidal signal set at therecord level set frequency which, when recorded, produces a signal containing 1 percent third

harmonic distortion at the output of a properly terminated reproduce amplifier (see sub-

paragraph 5.3.8.2 of Volume III, RCC Document 118). A one percent harmonic distortion

content is achieved when the level of the third harmonic component of the record level setfrequency is 40 ±1 dB below the level of a sinusoidal signal of 0.3 upper band edge (UBE)

which is recorded at the standard record level. Standard test and operating practice is to record

and reproduce sinusoidal signals at 0.1 and 0.3 UBE and adjust the equalizers as necessary toestablish the reproduced output at 0.3 UBE to within ±1.0 dB of the output at 0.1 UBE. Then a

1-V rms signal at the record level set frequency is applied to the record amplifier input and therecord and reproduce level controls are adjusted until the reproduced output contains 1 percent

third harmonic distortion at a level of 1 V rms.

The optimum level for recording data will seldom be equal to the standard record level.

Signals having noise-like spectral distribution such as baseband multiplexes of FM subcarriers

contain high crest factors so that it may be necessary (as determined in paragraph 1.1, Noise

Power Ratio (NPR) Test, Volume IV, RCC Document 118, Test Methods for Data Multiplex

Equipment ) to record at levels below the standard record level. On the other hand, for

predetection and HDDR recording, signals may have to be recorded above the standard record

level to give optimum performance in the data system.

D-15

7/31/2019 IRIG_106_2009



6.0 Tape Crossplay Considerations

Figure D-6 illustrates the typical departure from optimum frequency response that may

result when crossplaying wide band tapes that were recorded with heads employing different

record-head gap lengths. Line AA is the idealized output-versus-frequency plot of a machine

with record bias and record level, set upper IRIG standards, using a 3.05-m (120-microinch)record-head gap length and a 1.02-m (40-microinch) reproduce-head gap length. Lines BB and

CC represent the output response curves of the same tapes recorded on machines with 5.08-m

(200-microinch) and 1.27-m (50-microinch) record-head gap lengths. Each of these recorders

was set up individually per IRIG requirements. The tapes were then reproduced on the machine

having a 1.02-m (40-microinch) reproduce-head gap length without readjusting its reproduce

equalization.

6.1 The output curves have been normalized to 0 dB at the 0.1 UBE frequency for the

purpose of clarity. The normalized curves may be expected to exhibit a ±2.0 dB variance inrelative output over the passband. The tape recorded with the shortest head segment gap length

will provide the greatest relative output at the UBE.

6.2 While the examples shown are from older equipment with record gap lengths outside the

limits recommended in subparagraph 13.4.4, they illustrate the importance of the record gap

length in tape interchange applications.

7.0 Standard Tape Signature Procedures

The following subparagraphs describe the recording and playback procedures for the

PCM signature and the swept-frequency signature.

7.1 PCM Signature Recording Procedure. Test equipment should be configured as describedin paragraph 2.1, Volume IV, RCC Document 118. The configuration should simulate the

operational link as closely as possible to include the same RF frequency, deviation, bit rate, code

type, predetection frequency, receiver bandwidth, and recorder speed.

7.1.1 While recording the pseudo-random data at standard record level, adjust the signal

generator output level until approximately one error per 105

bits is obtained on the error counter.

7.1.2 Record 30 seconds of the pseudo-random data at the beginning or end of the tape for each

data track. A separate 30-second tape signature is recommended for each different data format.

7.1.3 The content, track assignments, and location on the tape leader and trailer of signaturesignals should be noted on the tape label.

D-16

7/31/2019 IRIG_106_2009



D-17

Gap Length

+4 Record Head = 1.27μm

(50 μin.)

Reproduce Head + 1.02 μm

Figure D-6. Tape crossplay.

7.2 PCM Signature Playback Procedure. The following subparagraphs explain the playback

procedure.

7.2.1 Optimize playback equipment such as receiver tuning and bit synchronizer setup for data

being reproduced.

7.2.2 Reproduce the tape signature and observe the error rate on the error counter.

7.2.3 Optimize head azimuth for maximum signal output and minimum errors.

7.2.4 Initiate corrective action if more than one error per 10

4

bits is obtained.

7.2.5 Repeat for each data track.

+2 (40μin.)

x C

0 0 Record Head = 3.05 μm

(120 μin.)

Reproduce Head = 1.02 μm(40μin.)

2

4Record Head = 5.08 μm

(200 μin.)

6 Reproduce Head = 1.02 μm

(40 μin.)

10K 20K 50K 100K 200K 500K 1000K 2000K

Frequency (Hz)

B ◘

A ● ● A

◘B

Cx

O u t p u t ( d B )

7/31/2019 IRIG_106_2009



7.3 Swept Frequency Signature Recording Procedure. The following subparagraphs describe

the recording procedure for the swept-frequency signature.

7.3.1 Patch a sweep-frequency oscillator output to all prime data tracks up to 6 on 7-track

recorders or up to 13 on 14-track recorders (see Appendix A, Volume III of RCC

Document 118). As a minimum, patch the sweep oscillator to one odd and one even track.

7.3.2 Connect the sync output of the sweep oscillator to a track not used for sweep signals,

preferably an outside track.

7.3.3 Record the signature signals for a minimum of 30 seconds at standard record level.

Record levels may be either preadjusted or quickly adjusted in all tracksduring the first few seconds of the signature recording.

7.3.4 Note the content, track assignments, and location on the leader or trailer tape of signaturesignals on the tape label.

7.4 Swept-Frequency Signature Playback Procedure. The following subparagraphs definethe steps for the playback procedure.

7.4.1 Connect the sync track output of the reproducer to the sync input of the scope.

7.4.2 Select an odd-numbered sweep-signal track and connect the output of the reproducer tothe vertical input of the scope. Playback the sweep signal and adjust the scope gain for an

amplitude of approximately ±10 minor vertical divisions about the center baseline. Adjust theodd-track azimuth for maximum amplitude of the highest frequency segment (extreme right of the sweep pattern).

7.4.3 Observe amplitude variations through the sweep pattern and adjust the equalization, if

necessary, to maintain the amplitude within the required tolerance over the required frequencyrange.

A decrease of sweep signal amplitude to about 0.7 represents a

3-dB loss.

7.4.4 Repeat the playback procedure in the preceding paragraphs paragraph 7.4.2 and

paragraph 7.4.3 for azimuth and equalization adjustments of an even-numbered tape track.

7.4.5 Repeat the procedure in paragraph 7.4.3 for equalization only of other selected prime

data tracks, as required.

D-18

7/31/2019 IRIG_106_2009



8.0 Equipment Required for Swept-Frequency Procedures

Equipment required at the recording site consists of a sweep-frequency oscillator having

a constant amplitude sweep range of approximately 400 Hz through 4.4 MHz with frequencymarkers at 62.5, 125, 250, and 500 kHz and 1.0, 2.0, and 4.0 MHz. The sweep range to 4.4 MHz

may be used for all tape speeds because the bandwidth of the recorder and reproducer will

attenuate those signal frequencies beyond its range. The sweep rate should be approximately25 Hz. Care should be exercised in the installation of the sweep generator to ensure a flat

response of the sweep signal at the input terminals of the recorder. Appropriate line-driver

amplifiers may be required for long cable runs or the low impedance of paralleled inputs.

8.1 A stepped-frequency oscillator could be substituted for the sweep-frequency generator at

the recording location. Recommended oscillator wavelengths at the mission tape speed are7.62 mm (300 mils), 3.81 mm (150 mils), 0.254 mm (10 mils), 0.0254 mm (1 mil), 0.0127 mm

(0.5 mil), 0.0064 mm (0.25 mil), 0.0032 mm (0.125 mil), 0.0025 mm (0.1 mil), 0.0020 mm

(0.08 mil), and 0.0015 mm (0.06 mil).

8.2 Equipment required at the playback site consists of an ordinary oscilloscope having a flat

frequency response from 400 Hz through 4.4 MHz.

9.0 Fixed-Frequency Plus White Noise Procedure

The signature used in this method is the same for all applications. For direct recording of

subcarrier multiplexes, only static nonlinearity (nonlinearity which is independent of frequency)

is important for crosstalk control. Subparagraph 17.2 provides a reference level for static

nonlinearity. All formats of data recording are sensitive to signal-to-noise ratio (SNR).Predetection recording and HDDR are sensitive to equalization. The following signature

procedure satisfies all the above requirements.

9.1 Record a sine-wave frequency of 0.1 UBE (see Table D-6) with the following

amplitudes.

9.1.1 Equal to the standard record level for direct recording of subcarrier multiplexes and

HDDR (see subparagraph 17.2).

9.1.2 Equal to the carrier amplitude to be recorded for pre-detection recording of PCM/FM,

PCM/PM, FM/FM, and PAM/FM.

9.2 Record flat band-limited white noise of amplitude 0.7 of the true rms value of the 0-dBstandard record level as described in subparagraph 17.2. Noise must be limited by a low-pass

filter just above the UBE.

9.3 Record with zero input (input terminated in 75 ohms). The three record steps previously

described can consist of 10 seconds each. The spectra can be obtained with three manuallyinitiated sweeps of less than a second each, because no great frequency resolution is required.

D-19

7/31/2019 IRIG_106_2009



All of the spectrum analyzer parameters can be standardized and set in (inputted) prior to

running the mission tape.

10.0 Signature Playback and Analysis

Before analyzing the signature, the reproducer azimuth should be adjusted. With the

short signature, it is probably more convenient to use the data part of the recording for this

purpose. If predetection recording is used, the azimuth can be adjusted to maximize the outputas observed on the spectrum analyzer or on a voltmeter connected to the output. If baseband

recording is used, the azimuth can be adjusted to maximize the spectrum at the upper end of the

band. A spectrum analyzer should be used to reproduce, store, and photograph the spectraobtained from paragraphs 9.1, 9.2, and 9.3 above. The spectrum analyzer input level of zero

should be stored and photographed.

10.1 It is evident that any maladjustment of the recorder and reproducer or magnetization of

the heads will result in the decrease of SNR across the band and will be seen from the stored

spectra or photograph.

10.2 By having a photograph of the spectra, amplitude equalization can be accomplished

without shuttling the mission tape as follows.

10.2.1 Use an auxiliary tape (not the mission tape, but preferably the same type tape). With a

white-noise input signal band limited, adjust the amplitude equalization of the recorder and

reproducer at the tape dubbing or data reduction site and photograph the output spectrum (see paragraph 9.0 of this appendix).

10.2.2 Compare this photo with the photo made from the signature. Note the difference atseveral points across the band.

10.2.3 Using the auxiliary tape, adjust the amplitude equalization to compensate for the

differences noted.

10.2.4 Recheck with the mission tape to verify that the desired amplitude equalization has beenachieved.

10.3 If the phase equalization is to be checked, a square wave signal can be added to thesignature in accordance with the manufacturer's specification (see Volume III, RCC

Document 118). The same procedure that is recommended for amplitude equalization can be

used, except the procedure is based on oscillograms.

D-20

7/31/2019 IRIG_106_2009



11.0 Recording and Playback Alignment Procedures

When using standard preamble (or postamble), see paragraph 21.0.

11.1 Recording of Preamble for Direct Electronics Alignment.

11.1.1 Patch a square wave generator output set to 1/11 band edge to all tracks having direct

electronics or initiate procedure for recording internally generated 1/11 band edge square waveaccording to manufacturer's instructions.

11.1.2 If the preamble will be used for a manual adjustment, record for a minimum of 30seconds at the standard record level and tape speed to be used for data recording.

If the preamble will be used only for automatic alignment, record at the standard record leveland tape speed to be used for data recording for a sufficient time as specified by the

manufacturer of the playback recorder reproducer or as agreed by the interchange parties.

11.2 Playback of Preamble for Direct Electronics Alignment. For systems so equipped,initiate automatic alignment procedure per manufacturer's instructions. The procedure for

manual adjustment is described in the following subparagraphs.

11.2.1 Display fundamental and odd harmonics of the square wave (third through eleventh) of

selected odd numbered direct track near center of head stack on the spectrum analyzer. Adjust

azimuth by peaking output amplitude of the third through eleventh harmonic. Final adjustmentshould peak the eleventh harmonic.

11.2.2 Repeat the above subparagraph for even numbered direct track. (Only one track isnecessary for a double density, 14-track, in-line system.)

11.2.3 Observe frequency response across the band pass on selected track and correct if

necessary. For a flat response, the third harmonic will be 1/3 of the amplitude of the

fundamental, fifth harmonic 1/5 the amplitude, and so on. A convenient method is to compare

the recorder/reproducer output with that of a square wave generator patched directly to thespectrum analyzer.

An alternate, but less accurate, method is to optimize the square wave as

displayed on an oscilloscope rather than a spectrum analyzer.

11.2.4 Repeat the previous subparagraph for each direct track.

11.2.5 Display square wave on an oscilloscope. Adjust phase for best square wave response as

shown in Figure D-7.

11.2.6 Repeat the previous subparagraph for each direct track.

D-21

7/31/2019 IRIG_106_2009



Equal

Amplitude

BAD GOOD BAD

Figure D-7. Square wave responses.

11.3 Recording of Preamble for FM Electronics Alignment. If available, initiate procedure for recording internally generated 1/11 band edge square wave and ±1.414 Vdc per manufacturer's

instructions. Otherwise, patch a square wave generator output to all tracks having FMelectronics. A near dc signal may be obtained by setting the square wave generator to 0.05 Hz

and ±1.414 V or by using a separate dc source.

11.3.1 If the preamble will be used for manual alignment, record at least one cycle of the 0.05 Hz square wave at ±1.414 V or a positive and negative 1.414 Vdc for a minimum of 10 seconds each at the tape speed to be used for data recording. Next, record a 1/11 band edge

square wave for a minimum of 20 seconds.

11.3.2 If the preamble will be used only for automatic alignment, record the above sequence for a sufficient time as specified by the manufacturer of the playback recorder/reproducer or as

agreed by the interchange parties.

11.4 Playback of Preamble for FM Electronics Alignment. For systems so equipped, initiate

automatic alignment procedure per manufacturer's instructions. The procedure for manual

adjustment is described in the next subparagraphs.

11.4.1 Check and adjust for 0-V output at center frequency per RCC Document 118, Test

Methods for Telemetry Systems and Subsystems, Volume III, Test Methods for

Recorder/Reproducer Systems and Magnetic Tape.

11.4.2 Use dc voltmeter to verify a full positive and negative output voltage on the selected

track and correct if necessary.

11.4.3 Display fundamental and odd harmonics of the square wave (third through eleventh) on

the spectrum analyzer.

11.4.4 Observe frequency response per subparagraph 11.2.3.

D-22

7/31/2019 IRIG_106_2009



11.4.5 Repeat subparagraphs 11.4.1 through 11.4.3 for each FM track.

12.0 General Considerations for Longitudinal Recording

Standard recording techniques, tape speeds, and tape configurations are required to provide maximum interchange of recorded telemetry magnetic tapes between the test ranges.

Any one of the following methods of information storage or any compatible combination may be

used simultaneously: direct recording, predetection recording, FM recording, or PCM recording.Double-density recording may be used when the length of recording time is critical; however, it

must be used realizing that performance parameters such as signal-to-noise ratio (SNR),

crosstalk, and dropouts may be degraded (see paragraph 2.0).

12.1 Tape Speeds. The standard tape speeds for instrumentation magnetic tape recorders are

shown in Table D-4.

12.2 Tape Width. The standard nominal tape width is 25.4 mm (1 in.). (see Table D-15, Tape

Dimensions).

12.3 Record and Reproduce Bandwidths. For the purpose of these standards, two system

bandwidth classes are designated: wide band and double density (see Table D-4). Interchange of

tapes between the bandwidth classes is NOT recommended.

13.0 Recorded Tape Format

The parameters related to recorded tape format and record and reproduce head

configurations determine compatibility between systems that are vital to interchangeability

(crossplay) of recorded magnetic tapes. The reader is referred to the definitions in Chapter 6, paragraph 6.2, Figure D-7a, Figure D-7b, and Figure D-7c. The reader is also referred to, Table

D-5, Table D-6, Table D-7, and Figure D-8

13.1 Track Width and Spacing. Refer to Figure 6-1, Table D-5, Table D-6, and Table D-7.

13.2 Track Numbering. The tracks on a tape are numbered consecutively from track 1through track n with track 1 located nearest the tape reference edge as shown in Figure D-7a.

13.3 Data Spacing. For interlaced formats, the spacing on tape between simultaneous eventson odd and even tracks is nominally 38.1 mm (1.5 in.). See paragraph 13.4.1.

13.4 Head Placement. The standard technique for wide band and 28-track double density is

to interlace the heads, both the record and the reproduce, and to provide alternate tracks inseparate heads. Thus, to record on all tracks of a standard width tape, two interlaced record

heads are used. To reproduce all tracks of a standard width tape, two interlaced reproduce headsare used. For 14-track double density, the standard technique uses one in-line record head and

one in-line reproduce head.

13.4.1 Head Placement, Interlaced. Two heads comprise the record-head pair or the reproduce-head pair. Mounting of either head pair is done in such a manner that the center lines drawn

D-23

7/31/2019 IRIG_106_2009



through the head gaps are parallel and spaced 38.10 mm ±0.05 (1.500 in. ±0.002) apart, as shown

in Tables D-5 and D-7, for systems that include head azimuth adjustment. The dimension between gap centerlines includes the maximum azimuth adjustment required to meet system

performance requirements. For systems with fixed heads (i.e., heads without an azimuth

adjustment), the spacing between gap centerlines shall be 38.10 mm ±0.03 (1.500 in. ±0.001)

(see Figure D-7b).

13.4.2 Head Identification and Location. A head segment is numbered to correspond to the

track number that segment records or reproduces. Tracks 1, 3, 5, . . . are referred to as the "odd"head segments. Tracks 2, 4, 6, . . . are referred to as the even head segments. For interlaced

heads, the head containing the odd numbered segments (odd head) is the first head in a pair of

heads (record or reproduce) over which an element of tape passes when moving in the forwardrecord or reproduce direction (see Chapter 6, Figure 6-2).

13.4.3 In-Line Head Placement. An in-line head shall occupy the position of head number 1 inan interlaced system.

13.4.4 Head Segment Location. Any head segment within a head shall be located within ±0.05

mm (±0.002 in.) of the nominal (dimension from table without tolerances) position required to match the track location as shown in Figure 6-1, Table D-5, Table D-6, and Table D-7.

D-24

7/31/2019 IRIG_106_2009



TABLE D-4. RECORD AND REPRODUCE PARAMETERS

Tape Speed{mm/s (ips)}

±3 dB Reproduce

PassbandKHz

(1)

Direct Record Bias

Set Frequency{(UBE) kHz

(2)}

Level Set Frequency{10% of UBE (kHz)}

Wide Band (Overbias 2dB)

6096.0 (240 ) 0.8-4000 4000 400

3048.0 (120 ) 0.4-2000 2000 200

1524.0 ( 60 ) 0.4-1000 1000 100

762.0 ( 30 ) 0.4- 500 500 50

381.0 ( 15 ) 0.4- 250 250 25

190.5 ( 7-1/2) 0.4- 125 125 12.5

95.2 ( 3-3/4) 0.4- 62.5 62.5 6.2547.6 ( 1-7/8) 0.4- 31.25 31.25 3.12

Double Density (Overbias 2 dB)

3048.0 (120 ) 2 -4000 4000 400

1524.0 ( 60 ) 2 -2000 2000 200

762.0 ( 30 ) 2 -1000 1000 100

381.0 ( 15 ) 2 - 500 500 50

190.0 ( 7-1/2) 1 - 250 250 25

95.2 ( 3-3/4) 0.5- 125 125 12.5

Notes:1. Passband response reference is the output amplitude of a sinusoidal signal at the record

level set frequency recorded at standard record level. The record level set frequency is

ten percent of the upper band edge frequency (0.1 UBE).

2. When setting record bias level, a UBE frequency input signal is employed. The signalinput level is set 5 to 6 dB below standard record level to avoid saturation effects

which could result in erroneous bias level settings. The record bias current is adjusted

for maximum reproduce output level and then increased until the output level decreases

by the number of dB indicated in the table (see paragraph 5.3.8.1 of Volume III, RCCDocument 118).

D-25

7/31/2019 IRIG_106_2009



TABLE D-5. DIMENSIONS – RECORDED TAPE FORMAT

14 TRACKS INTERLACED ON 25.4 MM (1 IN.) WIDE TAPE(1)

Millimeters

Maximum Minimum

InchesParameters

Track Width 1.397 1.143 0.050 ±0.005


Head Spacing

38.075 38.125 1.500 ±0.001Fixed Heads

38.151 38.049 1.500 ±0.002Adjustable Heads

0.279 1.011Edge Margin, Minimum

Reference Track

1.168 1.067 0.044 ±0.002Location

Track Location

0.051 0.051 ±0.002Tolerance

Location of nth

track


Maximum Minimum

1 (Reference) 0.000 0.000 0.0002 1.829 1.727 0.070

3 3.607 3.505 0.140

4 5.385 5.283 0.210

5 7.163 7.061 0.2806 8.941 8.839 0.350

7 10.719 10.617 0.420

8 12.497 12.395 0.490

9 14.275 14.173 0.560

10 16.053 15.951 0.630

11 17.831 17.729 0.700

12 19.609 19.507 0.770

13 21.387 21.285 0.840

14 23.165 23.063 0.910

Note 1. Refer to Figure D-7a.

D-26

7/31/2019 IRIG_106_2009




14 TRACKS IN-LINE ON 25.4 MM (1 IN.) WIDE TAPE(1)

MillimetersParameters

Maximum Minimum

Inches

Track Width 0.660 0.610 0.25 ±0.001


Head Spacing

Edge Margin, Minimum(2)

1.118 0.044

Reference Track

Location 0.698 0.622 0.0260 ±0.0015

Track Location

Tolerance 0.038 0.038 ±0.0015



Maximum Minimum

1 (Reference) 0.000 0.000 0.000

2 1.816 1.740 0.070

3 3.594 3.518 0.140

4 5.372 5.296 0.210

5 7.150 7.074 0.280

6 8.928 8.852 0.350

7 10.706 10.630 0.4208 12.484 12.408 0.490

9 14.262 14.186 0.560

10 16.040 15.964 0.630

11 17.818 17.742 0.700

12 19.596 19.520 0.770

13 21.374 21.298 0.840

14 23.152 23.076 0.910

Notes:

1. Refer to Figure D-7a.

2. Track location and spacing are the same as the odd tracks of the 28-track interlacedformat (see Table D-7). The minimum edge margin for track 1 is only 0.044 mm

(0.009 in.).

D-27

7/31/2019 IRIG_106_2009



D-28


14 TRACKS INTERLACED ON 25.4 MM (1 IN.) WIDE TAPE(1)

ParametersMillimeters

Maximum MinimumInches

Track Width 0.660 0.610 0.25 ±0.001Track Spacing 0.889 0.035

Head Spacing

Fixed Heads 38.125 38.075 1.500 ±0.001


Edge Margin, Minimum (2) 0.229 1.009

Reference Track

Location 0.699 0.622 0.0260 ±0.0015

Track Location

Tolerance 0.038 0.038 ±0.0015

Location of nth

track

Track NumberMillimeters

Maximum Minimum

Inches

1 (Reference) 0.000 0.000 0.000

2 0.927 0.851 0.035

3 1.816 1.740 0.170

4 2.705 2.629 0.105

5 3.594 3.518 0.140

6 4.483 4.407 0.175

7 5.372 5.296 0.210

8 6.261 6.185 0.245

9 7.150 7.074 0.280

10 8.039 7.963 0.315

11 8.928 8.852 0.350

12 9.817 9.741 0.385

13 10.706 10.630 0.42014 11.595 11.519 0.455

15 12.484 12.408 0.490

16 13.373 13.297 0.525

17 14.262 14.186 0.560

18 15.151 15.075 0.595

19 16.040 15.964 0.630

20 16.929 16.853 0.665

21 17.818 17.742 0.700

22 18.707 18.631 0.735

23 19.596 19.520 0.770

24 20.485 20.409 0.805

25 21.374 21.298 0.84026 22.263 22.187 0.875

27 23.152 23.076 0.910

28 24.041 23.965 0.945

Notes:

1. Refer to Figure D-7a.

2. Track location and spacing for the odd tracks are same as the tracks of the 14-track inline format (seeTable D-6). Edge margin for track 1 is only 0.229 mm (0.009 in.).

7/31/2019 IRIG_106_2009



D-2

9

Figure D-7a. Recorded tape format.

7/31/2019 IRIG_106_2009



Figure D-7b. Head and head segment mechanical parameters.

D-30

7/31/2019 IRIG_106_2009



D- 3 1

Figure D-7c. Record and reproduce head and head segment identification and location (

7/31/2019 IRIG_106_2009



Figure D-8. PCM record and reproduce configuration.

D-32

7/31/2019 IRIG_106_2009



14.0 Head and Head Segment Mechanical Parameters

The following describes the mechanical parameters of the head and head segments.

14.1 Gap Scatter. Gap scatter shall be 0.005 mm (0.0002 in.) or less for 25.4 mm (1 in.) tape(see Figure D-7c and paragraph 4.1 of this Appendix).

14.2 Head Segment Gap Azimuth Alignment. The head segment gap azimuth shall be

perpendicular to the head reference plane to within ±0.29 mrad (±1 minute of arc).

14.3 Head Tilt. The plane tangent to the front surface of the head at the center line of the head

segment gaps shall be perpendicular to the head reference plane within ±0.29 mrad (±1 minute of

arc) for wide band and double density recorders (see Figure D-7c).

14.4 Record-Head Segment Gap Parameters. The parameters for the length and azimuth

alignment are described in the following subparagraphs.

14.4.1 Record-Head Segment Gap Length. The record gap length (the perpendicular dimension

from the leading edge to the trailing edge of the gap) shall be 2.16 m ±0.5 (85 microinch ±20)

for wide band recorders and 0.89 m ±0.12 (35 microinch ±5) for double density recorders (see

Chapter 6, Figure 6-3 and paragraph 6.0 of this Appendix).

14.4.2 Record-Head Stack Gap Azimuth Alignment. The record-head stack azimuth shall be

perpendicular to the head reference surface to within ±0.29 mrad (±1 minute of arc). See paragraph 1.2, Volume III, RCC Document 118 for suggested test procedure.

14.4.3 Reproduce-Head Segment Gap Azimuth Alignment. The reproduce-head segment

azimuth alignment shall match that of the record-head segment as indicated by reproducing aUBE frequency signal on a selected track and setting the reproduce head azimuth for the

maximum output. At this azimuth setting, the output of any other track in the reproduce head

shall be within 2 dB of the output at its own optimum azimuth setting (see paragraph 1.3,Volume III, RCC Document 118).

15.0 Head Polarity

Also refer to Chapter 1, Volume III, RCC Document 118 and paragraph 4.2 herein.

15.1 Record-Head Segment. Each record-head winding shall be connected to its respective

amplifier in such a manner that a positive going pulse referenced to system ground at the record

amplifier input will result in the generation of a specific magnetic pattern on a segment of tape passing the record head in the normal direction of tape motion. The resulting magnetic pattern

shall consist of a polarity sequence of south-north-north-south.

15.2 Reproduce-Head Segment. Each reproduce-head segment winding shall be connected to

its respective amplifier in such a manner that an area of a tape track exhibiting a south-north-

north-south magnetic pattern will produce a positive going pulse with respect to system ground

at the output of the reproducer amplifier.

D-33

7/31/2019 IRIG_106_2009



16.0 Magnetic Tape and Reel Characteristics

It is recommended that all recorder and reproducer systems at a particular test range be

calibrated for operational use against a reference tape of the type used by the range for each bandwidth class of recorder and reproducer system. Additional supplementary procurement

specifications may be required to meet a particular operational requirement of the ranges.

16.1 Tape Width. The standard nominal tape width is 25.4 mm (1 in.) (see paragraph 25.0

(General Characteristics of Instrumentation Tapes and Reels), and Table D-15, Tape

Dimensions).

16.2 Tape Guiding. The tape guidance system restricts the tape angular motion to ±0.15 mrad

(±30 seconds of arc) as measured by the interchannel time displacement error (ITDE) of outer tracks on the same head stack. Make sure the guidance system does not damage the tape.

17.0 Direct Record and Reproduce Systems

Direct recording is a method of recording information signals on magnetic tape using

high-frequency ac bias recording (see definitions at Chapter 6, paragraph 6.2). Two classes of systems, wide band and double density, are included in these standards (see Table D-4).

17.1 Direct Record Parameters. The following subparagraphs describe the direct record parameters.

17.1.1 The input impedance for wide band and double density recorders shall be 75 ohms

nominal across the specified band.

17.1.2 Input gain adjustment shall be provided to permit sine-wave signals of 0.35 to 3.5 V rmsto be adjusted to produce standard record level.

17.1.3 Ideally, the recorded flux level on tape versus frequency should be constant. To approachthis ideal, the record amplifier transfer characteristic is basically a constant current versus

frequency with a superimposed compensation characteristic to correct only for loss of recording

efficiency with frequency. Results of the test described in paragraph 1.8 Volume III, RCCDocument 118, with the output amplitude at the 2 percent upper band edge (UBE) frequency used

as the 0 dB reference, shall be no greater than the following:

Percent of UBE Frequency dB Difference

10 0.5

50 1.080 1.6

100 2.0

D-34

7/31/2019 IRIG_106_2009



17.1.4 Record bias setting information is contained in Table D-4. The bias frequency shall be

greater than 3.5 times the highest direct record frequency for which the recorder and reproducer system is designed.

17.2 Standard Record Level. The standard record level for direct record systems is the input

level of the record level set frequency, which produces an output signal containing one percentthird harmonic distortion. The conditions necessary to establish the standard record level include

appropriate selection of the sinusoidal reference frequency (record level set frequency) as

indicated in Table D-4 and proper reproduce amplifier termination as defined in Figure 1-10Volume III, RCC Document 118. A one percent third-harmonic distortion content is achieved

when the level of the third harmonic of the record level set frequency is 40 dB ±1 below the level

of a sinusoidal signal of 30 percent of UBE frequency which is recorded at the standard recordlevel (see paragraph 5.0, of this Appendix for information regarding standard test and operating

practices).

17.3 Reproduce Parameters. The following subparagraphs describe the reproduce parameters.

17.3.1 For wide band and double density recorders, the output impedance shall be 75 ohms

nominal across the specified passband.

17.3.2 When reproducing a signal at the record level set frequency (recorded at the standard

record level), the output level shall be a minimum of 1 V rms with a third harmonic distortion of 1 percent and a maximum second harmonic distortion of 0.5 percent when measured across a

resistive load of 75 ohms. Lack of proper output termination will not cause the reproduce

amplifier to oscillate.

17.4 Tape Speed and Flutter Compensation. The average or long-term tape speed must be thesame during record and reproduce to avoid frequency offsets, which may result in erroneous

data. To minimize this problem, a reference signal may be applied to the tape during record and

the signal used to servo-control the tape speed upon reproduce. However, because servo-controlsystems have limited correction capabilities and to minimize the amount of equipment required

at the ranges, tape speeds and servo-control signals shall conform to the following standards.

17.4.1 The effective tape speed throughout the reel or any portion of the reel (in absence of tape-derived servo-speed control) shall be within ±0.2 percent of the standard speed as measured

by the procedures described in Chapter 1, Volume III, RCC Document 118.

17.4.2 Sinusoidal or square wave speed-control signals are recorded on the tape for the purpose

of servo-control of tape speed during playback. The operating level for speed-control signals

shall be 10 dB ±5 below standard record level when mixed with other signals or standard recordlevel when recorded on a separate track.

17.4.3 The constant-amplitude speed-control signal shall be used on a separate track for optimum servo-speed correction. The speed-control signal may be mixed with other signals if

recording requirements so demand and system performance permits. Mixing of the

speed-control signal with certain types of signals may degrade system performance for tapes

D-35

7/31/2019 IRIG_106_2009



which are to be reproduced on tape transports with low time-base error capstan drive systems

(refer to manufacturer). Table D-8 lists speed-control signal frequencies. The speed-controlsignal may also be used as a flutter correction signal.

17.4.4 Signals to be used for discriminator flutter correction systems are listed in Chapter 3,

Table 3-3 and Table D-8 of this Appendix. See subparagraph 17.4.3 of this appendix andChapter 3, Table 33 for restrictions on use of flutter correction signals.

18.0 Timing, Predetection, and Tape Signature Recording

Described in the following subparagraphs are timing signal, predetection, and tape

signature recording.

18.1 Timing Signal Recording. Modulated-carrier, time-code signals (IRIG A, IRIG B, and

IRIG G) are widely used and other formats are available. When recording IRIG B time-code

signals, care must be taken to ensure that low-frequency response to 100 Hz is provided. The

direct record, low frequency cutoff of most wide band recorders is 400 to 800 Hz. For thesesystems, IRIG B time code signals should be recorded on an FM track or on an FM subcarrier.

The widest bandwidth subcarrier available should be employed to minimize time delay.1

For

double density systems, all time code signals should be recorded on an FM track or an FMsubcarrier.

18.2 Predetection Recording. Predetection signals have been translated in frequency but notdemodulated. These signals will be recorded by direct (high frequency bias) recording.

Parameters for these signals are in Table D-9.

18.3 Tape Signature Recording. For data processing using wide band and double-density

recorders and reproducers, a tape signature recorded before or after the data, or both before and

after the data, provides a method of adjusting the reproducer head azimuth and reproduceequalization. A means is also provided for verifying the proper operation of equipment such as

playback receivers and bit synchronizers used to retrieve the recorded data.

A pulse code modulation (PCM) signature is recommended where primarily PCM data is

recorded. A swept-frequency or white-noise signature may be used for other data such as

frequency division multiplexing (FDM) or wide band FM. The procedures for recording andusing these signatures are given in paragraph 22.0. A recommended preamble/ postamble signal

for recorder/reproducer alignment is included in paragraph 21.0.

1 Timing code formats are found in IRIG standard 200-98, IRIG Serial Time Formats and IRIG standard 205-87,

Parallel Binary and Parallel Binary Coded Decimal Time Code Formats.

D-36

7/31/2019 IRIG_106_2009



TABLE D-8. CONSTANT-AMPLITUDE SPEED-CONTROL SIGNALS(1)

Frequency(2)

Tape Speed

(mm/s) (in./s) (kHz)

6096 (240 ) 400 ±0.01% 800 ±0.01%

3048 (120 ) 200 ±0.01% 400 ±0.01%

1524 ( 60 ) 100 ±0.01% 200 ±0.01%

762 ( 30 ) 50 ±0.01% 100 ±0.01%

381 ( 15 ) 25 ±0.01% 50 ±0.01%

190.5 ( 7-1/2) 12.5 ±0.01% 25 ±0.01%

95.5 ( 3-3/4) 6.5 ±0.01% 12.5 ±0.01%

47.6 ( 1-7/8) 3.125 ±0.01% 6.25 ±0.01%

Notes:

1. May also serve as discriminator flutter-correction reference signal (see Chapter 3, Table 33).

2. Either set of speed-control signals may be used primarily with wideband systems, but only the

higher set of frequencies is recommended for double density systems. When interchanging tapes,

care should be taken to ensure that the recorded speed-control signal is compatible with the

reproduce system’s speed-control electronics.

Caution should be used when multiplexing other signals with the

speed-control signal. In the vicinity of the frequency of thespeed-control signal (fsc ±10 percent), the level of individual extraneous

signals including spurious, harmonics, and noise must be 40 dB or more

below the level of the speed-control signal. A better procedure is to

leave one octave on either side of the speed-control signal free of other signals.

D-37

7/31/2019 IRIG_106_2009



TABLE D-9. PREDETECTION CARRIER PARAMETERS

Predetection CarrierTape Speed

Center Frequency(1,2)

Wide Band Double Density A B

(mm/s) (in./s) mm/s (in./s) (kHz) (kHz)

6096 (240) 3048.0 ( 120 ) 1800 2400

3048 (120) 1524.0 ( 60 ) 900 1200

1524 ( 60) 762.0 ( 30 ) 450.0 600

762 ( 30) 381.0 ( 15 ) 225.0 300

381 ( 15) 109.5 ( 7.5) 112.5 150

Notes:1. The predetection record/playback passband is the carrier center frequency 66.7 percent.2. Use center frequencies in column B when data bandwidth exceeds the capabilities of those

in column A.

19.0 FM Record Systems

For these FM record systems, the input signal modulates a voltage-controlled oscillator,

and the output is delivered to the recording head. High frequency bias may be used but is notrequired. These standards shall apply.

19.1 Tape and Reel Characteristics. Paragraph 22.0 and all related subparagraphs shall apply.

19.2 Tape Speeds and Corresponding FM Carrier Frequencies. See Table D-10.

19.3 FM Record/Reproduce Parameters. See Table D-10.

D-38

7/31/2019 IRIG_106_2009



TABLE D-10. WIDE BAND AND DOUBLE DENSITY FM RECORD PARAMETERS

Carrier

Deviation Limits(1)Tape Speed

Wide Band FM

Carrier

Center

Frequency Plus MinusDeviation Deviation

Modulation

Frequency

Response

Band

Limits

(mm/s) (in/s) (kHz) (kHz) (kHz) (kHz) (dB(2)

)

Group I

47.6 (1-7/8) 6.750 9.450 4.050 dc to 1.250 ±1

95.2 ( 33/4) 13.500 18.900 8.100 dc to 2.500 ±1

190.5 ( 71/2) 27.000 37.800 16.200 dc to 5.000 ±1

381.0 ( 15 ) 54.000 75.600 32.400 dc to 10.000 ±1

762.0 ( 30 ) 108.000 151.200 64.800 dc to 20.000 ±1

1524.0 ( 60 ) 216.000 302.400 129.600 dc to 40.000 ±1

3048.0 ( 120 ) 432.000 604.800 259.200 dc to 80.000 ±1

Double

DensityGroup II

47.6 (1-7/8) 14.062 18.281 9.844 dc to 7.810 ±1, 3

95.2 (3-3/4) 28.125 36.562 19.688 dc to 15.620 ±1, 3

95.2 (33/4) 190.5 (7-1/2) 56.250 73.125 39.375 dc to 31.250 ±1, 3

190.5 (71/2) 381.0 ( 15 ) 112.500 146.250 78.750 dc to 62.500 ±1, 3381.0 (15 ) 62.0 ( 30 ) 225.000 292.500 157.500 dc to 125.000 ±1, 3

762.0 (30 ) 1524.0 ( 60 ) 450.000 585.000 315.000 dc to 250.000 ±1, 3

1524.0 (60 ) 3048.0 (120 ) 900.000 1170.000 630.000 dc to 500.000 ±1, 3

3048.0 (120 ) 6096.0 (240 ) 1800.000 2340.000 1260.000 dc to 1000.000 ±1, 3

Notes:

1. Input voltage levels per subparagraph 19.5.2. Frequency response referred to 1-kHz output for FM channels 13.5 kHz and above, and

100 Hz for channels below 13.5 kHz.

D-39

7/31/2019 IRIG_106_2009



19.4 Speed Control and Compensation. Paragraph 17.4 shall apply. Note that a separate

track is always required for speed control and flutter compensation signals with a single-carrier FM system.

19.5 FM Record Parameters. For FM record systems, an input voltage of 1 to 10V peak-to-

peak shall be adjustable to produce full frequency deviation.

19.5.1 Deviation Direction. Increasing positive voltage gives increasing frequency.

Predetection recorded tapes may be recorded with reverse deviation direction because of thefrequency translation techniques employed.

19.6 FM Reproduce Systems. Output levels are for signals recorded at full deviation. In wide band and double density FM systems, the output is 2 V peak-to-peak minimum across a load

impedance of 75 ohms ±10 percent. Increasing input frequency gives a positive going output

voltage.

20.0

PCM Recording

The PCM signals may be successfully recorded using several different methods.

Methods included in these standards are predetection recording, post-detection recording, and

serial high-density digital recording (HDDR). Parallel HDDR methods are not included.

20.1 Predetection PCM Recording. This method employs direct recording of the signal

obtained by heterodyning the receiver IF signal to one of the center frequencies listed inTable D-9 without demodulating the serial PCM signal (see Figure D-8. The maximum

recommended bit rate for predetection recording of NRZ data is equal to the predetection carrier

frequency, for example, 900 kb/s for a 900 kHz predetection carrier. The maximum

recommended bit rate for predetection recording of bi-phase (Bi) data is equal to one-half the

predetection carrier frequency. For bit rates greater than one-half the maximum recommendedrates, the preferred method of detection is to convert the signal to a higher frequency before

demodulation.

20.2 Post-Detection PCM Recording. The serial PCM signal (plus noise) at the video output

of the receiver demodulator is recorded by direct or wide band FM recording methods without

first converting the PCM signal to bi-level form (see Figure D-8). Table D-11 lists maximum bitrates versus tape speed for these recording methods. The minimum recommended reproduce bit

rates are 10 kb/s for post-detection direct Bi and 10 bits per second for post-detection FM (seeChapter 4, paragraph 4.2.2.3).

D-40

7/31/2019 IRIG_106_2009



TABLE D-11. MAXIMUM RECOMMENDED BIT RATES, POST-DETECTION

RECORDING(1)

Tape Speed Post-FM

Wide Band Double Density

(mm/s) (in./s) (mm/s)

Post-D

Direct

(in./s) Biφ (kb/s) Biφ (kb/s) NRZ (kb/s)

6096.0 (240 ) 3048.0 (120 ) 1800 900 1800

3048.0 (120 ) 1524.0 ( 60 ) 900 450 900

1524.0 ( 60 ) 762.0 ( 30 ) 450.0 225 450

762.0 ( 30 ) 381.0 ( 15 ) 225.0 112 225

381.0 ( 15 ) 109.5 ( 7-1/2) 112.5 56 112

190.5 ( 7-1/2 ) 95.2 ( 3-3/4) 56 28 5695.2 ( 3-3/4 ) --- 28 14 28

47.6 ( 1-7/8 ) --- 14 7 14

Note:

1. Direct recording of NRZ signals is NOT recommended unless the signal format is carefully

designed to eliminate low-frequency components for any data expected.

20.3 Serial High-Density Digital Recording. Serial HDDR is a method of recording PCM data

on a magnetic tape that involves applying the data to one track of the recorder as a bi-level

signal.

20.4 The following subparagraphs deal with standards for direct recording of PCM telemetrydata using a wide band analog instrumentation recorder or reproducer system. Direct recording

is described in paragraph 17.0. The recommended PCM codes, maximum bit rates, record and

reproduce parameters, and the magnetic tape requirements are also described.

20.4.1 PCM Codes. The recommended codes for serial high-density PCM recording are

bi-phase level (Bi-L) and randomized non-return-to-zero-level (RNRZ-L). The maximum

recommended bit packing densities (for wide band recording) re 590 b/mm (15 kb/in.) for Bi-Land 980 b/mm (25 kb/in.) for RNRZ-L. Refer to Table D-12 for maximum recommended bit

rates versus standard tape speeds. The minimum recommended reproduce bit rates are 5 kb/s for Bi-L and 200 kb/s for RNRZ-L. Details of the implementation are discussed in paragraph 3.0,of this Appendix.

D-41

7/31/2019 IRIG_106_2009



TABLE D-12. MAXIMUM RECOMMENDED BIT RATES

Tape Speed

Wide Band Double DensityBiφ-L

(kb/s)

(mm/s) (in./s) (mm/s) (in./s)

RNRZ-L (kb/s)

6096.0 (240 ) 3048.0 (120 ) 3600 6000

3048.0 (120 ) 1524.0 ( 60 ) 1800 3000

1524.0 ( 60 ) 762.0 ( 30 ) 900 1500

762.0 ( 30 ) 381.0 ( 15 ) 450 750

381.0 ( 15 ) 109.5 ( 7-1/2) 225 375

190.5 ( 7-1/2 ) 95.2 ( 3-3/4) 112 187(1)

95.2 ( 3-3/4 ) --- 56 93(1)

47.6 ( 1-7/8 ) --- 28 46(1)

Note:1.

Reproducing data at bit rates less than 200 kb/s is not recommended when using RNRZ-L.

20.4.2 Bi-L Code. The Bi-L code is recommended for direct recording under the following

conditions: The bit rate of the data to be recorded does not exceed the maximum bit rates for

Bi-L (see Table D-12), and the amount of tape required for mission recording by this method is

not a severe operational constraint.

20.4.3 RNRZ-L Code. The RNRZ-L code is recommended for direct recording under any of

the following conditions: the bit rate of the data to be recorded exceeds the maximum

recommended bit rates for Bi-L (see Table D-12) or maximum tape recording time is needed.

20.4.3.1 To minimize baseline wander anomalies, RNRZ-L is NOT recommended if thereproduced bit rate is less than 200 kb/s.

20.4.3.2 The RNRZ-L shall be implemented using a 15-stage shift register and modulo-2adders (see Figure D-9). The randomized bit stream to be recorded is generated by adding

(modulo-2) the input bit stream to the modulo-2 sum of the outputs of the 14th and 15th stages of the shift register. In the decoder, the randomized bit stream is the input to the shift register (seeFigure D-9).

D-42

7/31/2019 IRIG_106_2009



Figure D-9. Serial high-density digital record and reproduce.

D-43

7/31/2019 IRIG_106_2009



20.4.4 Record Parameters. The record parameters are explained in the following

subparagraphs.

20.4.4.1 High-density PCM data shall be recorded in compliance with the direct record

parameters detailed in subparagraph 17.1 including the use of an ac bias signal level that

produces the required 2 dB over-bias condition.

20.4.4.2 The peak-to-peak level of the PCM input signal shall be equal to twice the rms value

of the signal amplitude used to establish the standard record level with a tolerance of ±25 percent(see subparagraph 17.2).

20.4.4.3 The signal to be recorded must be bi-level. Bi-level signals are signals where only twolevels are present. Therefore, signals containing noise must be converted to bi-level signals

before they are recorded.

20.4.4.4 To minimize the effects of tape dropouts, serial high-density digital data should not be

recorded on the edge tracks of the tape.

20.4.5 Reproduce Parameters. All reproduce parameters in subparagraph 17.3 shall apply.

20.4.5.1 PCM Signature. A PCM signature should be recorded before or after or both before

and after the data to provide a method for adjusting the reproduce head azimuth and thereproducer equalizers. The data rate of the PCM signature should be the same as the rate of the

data to be recorded (see paragraph 7.0 for tape signature recording).

20.4.5.2 Phase Equalizer. Correct phase equalization is very important to the reconstruction of

the serial high-density digital data. Adjustable phase equalizers are desirable but not mandatory.

20.4.6 Magnetic Tape. High-density digital (HDD) magnetic tapes are recommended;

however, wide band instrumentation tapes can be used on recorder and reproducer systems with1.27 mm (0.050 in.) track widths (see paragraphs 22.0 through 27.0 below).

20.4.7 Tape Copying. The following practices are recommended when making copies of

original data tapes.

20.4.7.1 Convert data reproduced from the original tape to a bi-level signal prior to recording a

copy.

20.4.7.2 Align reproduce head azimuth to original tape.

20.4.7.3 Adjust reproducer equalizers correctly.

20.4.7.4 Prior to recording the copy, use the recorded PCM signature to optimize the quality of the reproduced data.

D-44

7/31/2019 IRIG_106_2009



20.4.8 PCM Bit Synchronizer. The PCM bit synchronizer should contain circuitry to

reestablish the baseline reference PCM signal (a dc restorer circuit). This circuit is essentialwhen reproducing RNRZ-L at reproduced bit rates less than 1 Mb/s. The PCM bit synchronizer

loop bandwidth should be selected for optimum performance between 0.1 and 3 percent of the bit

rate.

If an appropriate PCM bit synchronizer is not available, the tape can be

copied directly; however, the SNR will be decreased.

21.0 Preamble Recording for Automatic or Manual Recorder Alignment

A preamble (or postamble) may be recorded on the same tape as the data signal with

known frequency and amplitude elements which will allow automatic or manual alignment of the

signal electronics to optimize the performance of the playback system. Reproduce azimuth,equalization, and FM demodulator sensitivity may be adjusted at all available tape speeds. The preamble may be used for manual adjustment of any instrumentation magnetic tape recorder/

reproducer (wide band and double density). Automatic adjustment requires a recorder/

reproducer specifically designed with the capability to automatically adjust one or more of thefollowing: reproduce-head azimuth, amplitude equalization, phase equalization, and FM

demodulator sensitivity. The signal source may be internal to the recorder or may be externally

generated.

21.1 Alignment, Direct Electronics. Direct electronics shall use a 1/11 band edge square wave

for both manual and automatic alignment as given in this Appendix.

21.2 Alignment, FM Electronics. The FM electronics shall use a 1/11 band edge square wave

and ±1.414 Vdc or 0.05 Hz square wave for both manual and automatic alignment as given in

this Appendix.

22.0 Magnetic Tape Standards: General

The following standards define terminology, establish key performance criteria, and

reference test procedures for longitudinally-oriented oxide, unrecorded magnetic tape designedfor instrumentation recording,

2and reference specifications for 19 mm (0.75 in) cassettes

designed for digital helical scan recording and S-VHS cassettes designed for 12.65 mm (1/2 in)

digital helical scan recording. Classes of instrumentation recording tapes include high-resolution

(HR) tapes used for wide band recording, high-density digital (HDD) tapes used for high-densitydigital PCM recording, and high energy (HE) tapes used for double density recording.

2 Federal Specifications may be used to replace paragraphs contained in this chapter where applicable. High output

and HDD tapes re not included in the Federal Specificaions. Other standards are referenced in paragraph 1.0,

Appendix D.

D-45

7/31/2019 IRIG_106_2009



Coercivities of HR and HDD tapes are in the range of 275 to 350 oersteds. High-energy

tapes have coercivities of 600 to 800 oersteds. Nominal base thickness is 25.4 μm (1.0 mil) andnominal coating thickness is 5 μm (200 microinches) for all tapes. Where required, limits are

specified to standardize configurations and to establish the basic handling characteristics of the

tape. Limits placed on the remaining requirements must be determined by the tape user in light

of the intended application and interchangeability requirements imposed on the tape (seeTable D-13 for examples of suggested requirement limits).

TABLE D-13. SUGGESTED TAPE REQUIREMENT LIMITS

Paragraph

No.Tape Requirement Suggested Limits

27.1 Bias Level ±2.0 dB from MCT

27.2 Record Level ±2.0 dB from MCT

27.3 Wavelength Response (Table D-13A)

27.4 Output at 0.1 UBE Wavelength 1.5 dB from MCT

27.5 Short Wavelength Output UniformityHR Tape HE Tape

2.5 dB 2.5 dB

27.6 Dropouts per 30 m (100 ft) (average) Center Tracks Edge Tracks

51

20

HR TapeHDD Tape

HE Tape

101

30

27.7 Durability (See Table D-14.)

27.8 Modulation Noise 1 dB maximum

D-46

7/31/2019 IRIG_106_2009



TABLE D-13A. SUGGESTED WAVELENGTH RESPONSE REQUIREMENTS

HR AND HDD TAPE

Measurement Wavelength HR Response HDD Response

(μm) (mils) (dB) (dB)

3810.00 (150.000) 1.00 2.00

254.00 (10.000) 1.00 1.00

15.14 (0.600) 0.00 0.00

6.35 (0.250) 1.50 1.50

3.18 (0.125) 2.00 2.00

2.54 (0.100) 2.50 2.50

2.03 (0.080) 2.50 2.50

1.52 (0.060) 3.00 3.00

HIGH-ENERGY TAPE

Measurement Wavelength HE Wavelength Response

(μm) (mils) (dB)

25.40 (1.000) 2.00

12.70 (0.500) 2.00

7.62 (0.300) 0.003.18 (0.125) 2.50

1.52 (0.060) 2.50

1.02 (0.040) 3.00

0.76 (0.030) 3.50

D-47

7/31/2019 IRIG_106_2009



TABLE D-14. DURABILITY SIGNAL LOSSES

Designated Tape LengthNumber of Allowable Signal Losses (per pass)

Meters Feet

762 (2,500) 2

1,097 (3,600) 2

1,402 (4,600) 2

1,524 (5,000) 2

2,195 (7,200) 3

2,804 (9,200) 3

3,292 (10,800) 4

23.0 Definitions

Underlined terms appearing within definitions indicate that these terms are defined

elsewhere in paragraph 23.0. For the purpose of this standard, the following definitions apply.

23.1 Back Coating. A thin coating of conductive material (for example, carbon) bonded to the

surface of a magnetic tape opposite the magnetic-coated surface for reducing electrostatic charge

accumulation and for enhancing high-speed winding uniformity. Resistivity of the back coatingshould be 1 megohm per square or less, whereas the oxide -coated magnetic surface resistivity is

much higher (also see magnetic oxide coating).

23.2 Base. The material on which the magnetic oxide coating (and back coating, if employed)is applied in the manufacture of magnetic tapes. For most applications, polyester - base materials

are currently employed.

23.3 Bias Level. The level of high frequency ac bias current or voltage in a direct record

system needed to produce a specified level of an upper band edge (UBE) frequency sine-wavesignal at a particular tape speed. Bias level is usually adjusted to produce maximum output or

increased beyond maximum to depress the output 2 dB.

23.4 Bi-Directional. Ability of a magnetic tape to record and to reproduce a specified range of

signals within specified tolerances of various characteristics when either end of the tape on the

reel is used as the leading end.

23.5 Binder. Material in which the magnetic oxide particles or back-coating particles are

mixed to bond them to the base material.

23.6 Blocking. Failure of the magnetic coating to adhere to the base material because of

layer-to-layer adhesion in a wound tape pack.

D-48

7/31/2019 IRIG_106_2009



23.7 Center Tracks. On a recorded tape, center tracks are those that are more than one-track

distance from either edge of the tape, for example, tracks 2 through 13 of a 14-track tape or tracks 2 through 27 of a 28-track tape.

23.8 Dropout. A reproduced signal of abnormally low amplitude caused by tape

imperfections severe enough to produce a data error. In digital systems, dropouts produce biterrors.

23.9 Edge Tracks. The data tracks nearest the two edges of a recorded magnetic tape, for example, tracks 1 and 14 of a 14-track tape.

23.10 Erasure. Removal of signals recorded on a magnetic tape to allow reuse of the tape or to prevent access to sensitive or classified data. Instrumentation recorders and reproducers do not

usually have erase heads, so bulk erasers or degaussers must be employed.

23.11 E-Value. The radial distance by which the reel flanges extend beyond the outermost

layer of tape wound on a reel under a tape tension of 3.33 to 5.56 newtons (12 to 20 ounces of force) per inch of tape width. Inadequate E-value may prohibit the use of protective reel bands.

23.12 High-Density Digital Magnetic Tape. Instrumentation magnetic tape with nominal base

thickness of 25.40 μm (1 mil) and coercivity of 275 to 350 oersteds used to record and reproduce

high-density digital (PCM) signals with per-track bit densities of 590 b/mm (15 kb/in.) or greater.

23.13 High-Energy Magnetic Tape. Magnetic tapes having coercivity of 600 to 800 oerstedsand nominal base thickness of 25.4 μm (1 mil) used for double density analog recording and

high-density digital recording above 980 b/mm (25 kb/in.).

23.14 High-Resolution Magnetic Tape. Instrumentation magnetic tape used for recording on

wide band recorder and reproducer systems. The HR and HDD tapes may have identicalcoatings and coercivities (275 to 350 oersteds) but differ in the extent and type of testing

conducted by the manufacturer.

23.15 Layer-to-Layer Signal Transfer (Print Through). Transfer of a signal to a layer of awound magnetic tape originating from a signal recorded on an adjacent layer of tape on the same

reel. Saturation-level recorded signals and tape storage at elevated temperatures are likely

contributors to this effect.

23.16 Magnetic Oxide Coating. Material applied to a base material to form a magnetic tape.

The magnetic oxide coating contains the oxide particles, the binder, and other plasticizing andlubricating materials necessary for satisfactory operation of the magnetic tape system (also see

back coating).

23.17 Manufacturer's Centerline Tape (MCT). A tape selected by the manufacturer from his

production, where the electrical and physical characteristics are employed as reference standards

for all production tapes to be delivered during a particular contractual period. Electrical

D-49

7/31/2019 IRIG_106_2009



characteristics include, but are not limited to, bias level, record level, output at 0.1 UBE, and

wavelength response. The MCTs are not usually available for procuring agency use.

23.18 Manufacturer's Secondary Centerline Tape (MSCT). A tape selected by a manufacturer

from his production and provided in lieu of an MCT. On the MSCT, the electrical characteristics

may depart from the MCT characteristics, but calibration data referenced in the MCT are provided. All other characteristics of the MSCT are representative of the manufacturer's product.

23.19 Modulation Noise. Noise riding on a reproduced signal that is proportional to theamplitude of the recorded signal (below saturation) and results from tape-coating irregularities in

particle size, orientation, coercivity, and dispersion.

23.20 Record Level. The level of record current or voltage required to achieve a specified

reproduce output level with bias level previously set to the correct value. In direct record

systems, standard record level is the level of a 0.1 UBE frequency signal required to produce 1 percent third harmonic distortion in the reproduced output signal because of tape saturation.

23.21 Scatterwind. Lateral displacements of tape wound on a reel which gives an irregular

appearance to the side surfaces of a tape pack. Scatterwind can result from such things as poorlycontrolled tape tension, guiding, static electrical charge, and poor tape slitting.

23.22 Shedding. Loss of magnetic coating from tape during operation on a tape transport.Excessive shedding causes excessive dropout.

23.23 Short Wavelength Output Uniformity. A measure of high-frequency reproduce signalamplitude uniformity caused by oxide coating variations.

23.24 Upper Band Edge. The highest frequency that can be recorded and reproduced at a

particular tape speed in the direct record mode. The UBE signals are used in setting bias level;

0.1 UBE signals are used to set record level.

23.25 Wavelength Response. The record and reproduce characteristic of a magnetic tape which

depends on tape formulation, coating thickness, and other tape physical parameters and is a

function of the wavelength recorded on the tape (tape speed divided by signal frequency) rather than the actual frequency recorded.

23.26 Working Length. Length of tape usable for reliable recording and reproduction of data.Actual tape length on a reel exceeds the working length to provide for tape start and stop at each

end of the reel without loss of data.

23.27 Working Reference Tape (WRT). A tape or tapes of the same type as an MCT or MSCT

selected by the user and calibrated to the MCT or MSCT. The WRTs are employed in

conducting tests on tape types during a procurement activity and for aligning and testing recorder and reproducer systems to minimize running the MCT or MSCT.

D-50

7/31/2019 IRIG_106_2009



24.0 General Requirements for Standard Instrumentation Tapes and Reels

The following subparagraphs describe the requirements for tapes and reels.

24.1 Reference Tape System. To establish a set of test procedures which can be performedindependently and repeatedly on different manufacturers' tape transports, a centerline reference

tape system employing MCT, MSCT, or WRTs as required, should be used. The reference tape

system provides a centerline tape against which tape or tape recorder specifications may betested or standard tapes for aligning operational recorders.

24.1.1 Manufacturer's Centerline Tape. The electrical characteristics provided for amanufacturer's centerline tape include, but are not limited to, bias level, record level, wavelength

response, and output at 0.1 UBE wavelength. The physical characteristics of the MCT shall also

represent the manufacturer's production and shall be representative of all production tapedelivered during any resultant contractual period (see MCT definition in paragraph 23.17)

24.1.2 Manufacturer's Secondary Centerline Tape. On the MSCT, the electrical characteristics

are calibrated to the manufacturer's reference tape, and calibration data are supplied with theMSCT. The physical characteristics of the MSCT shall represent the manufacturer's production

(see secondary MCT definition in paragraph 23.18).

24.1.3 Working Reference Tape (WRT). Working reference tapes shall be of the same type as

those under procurement or test and shall be used in place of a MCT or MSCT for all applicable

test procedures (see WRT definition in paragraph 23.27).

The MCT or MSCT shall be a full-length tape of 25.4 mm (1 in.) width,

wound on a 266.7 mm (10 1/2 in.) or 355.6 mm (14 in.) reel or as

designated by the tape user. The center one-third of the working tapelength shall be used as the calibrated working area.

24.1.4 Test Recorder and Reproducer. A laboratory quality test recorder shall be designated for

use with the reference tape system during any magnetic tape procurement and test program. The

recorder selected shall meet the requirements specified in this Appendix.

24.1.5 MCT/MSCT/WRT Use. Using MCT or MSCT as a reference, the tape user performs all

tests necessary to determine if the manufacturer's centerline performance values meet operationaland recorder requirements. All acceptable centerline tapes are retained by the tape user as

references in subsequent acceptance test procedures performed in support of resultant contractsor contractual periods. A working reference tape, which has been calibrated to an MCT or

MSCT, is used as the actual working reference in the applicable testing procedures outlined inVolume III, RCC Document 118. Dropout tests should use a tape other than the MSCT or WRT.

24.2 Marking and Identifying. See Federal Specification W-T-1553B.3

3 There are four W-T-1553 specifications relating to different coercivity and dropout rates.

D-51

7/31/2019 IRIG_106_2009



24.3 Packaging. Specified by user.

24.4 Winding. The tape shall be wound on the reel or hub with the oxide surface facing

toward the hub ("A" wind). The front of the wound reel is defined as that flange visible when

viewing the tape reel with the loose end of the tape hanging from the viewer's right.

24.5 Reels and Hubs. Reels and hubs shall conform to the tape user specified requirements of

Federal Specification W-R-175.

24.6 Radial Clearance (E-Value). For all tape lengths, use 3.175 mm (0.125 in., (See E-Value

definition in paragraph 23.11).

24.7 Flammable Materials. Flammable materials shall not be a part of the magnetic tape.

Flammable materials will ignite from a match flame and will continue to burn in a still carbondioxide atmosphere.

24.8 Toxic Compounds. Compounds which produce toxic effects in the environmental

conditions normally encountered under operating and storing conditions as defined insubparagraph 25.2 shall not be part of the magnetic tape. Toxicity is defined as the property of

the material that has the ability to do chemical damage to the human body. Highly toxic or

corrosive compounds produced under conditions of extreme heat shall be identified anddescribed by the manufacturer.

25.0 General Characteristics of Instrumentation Tapes and Reels

The following subparagraphs describe the general characteristics for tapes and reels.

25.1 Dimensional Specifications. Magnetic tape shall be supplied on flanged reels in thestandard lengths, widths, and base thicknesses outlined in Table D-15. Reel and hub diameters

are taken from Federal Specification W-R-175.

D-52

7/31/2019 IRIG_106_2009



TABLE D-15. TAPE DIMENSIONS

Dimension Millimeters Inches

Tape Width 25.4 +0 0.10 1.000 +0 0.004

Tape Thickness

Base Material 0.025 0.0010 Nominal(1)

Oxide Thickness 0.005 0.0002 Nominal

Tape Length by Reel Diameters (reels with 76 mm (3 in.) center hole)

Nominal Tape Length(2)

Minimum True Length(3)

Reel Diameter

266 mm (10.5 in.) 1100 m (3600 ft) 1105 m (3625 ft)" " " " 1400 m (4600 ft) 1410 m (4625 ft)

356 mm (14.0 in.) 2200 m (7200 ft) 2204 m (7230 ft)

" " " " 2800 m (9200 ft) 2815 m (9235 ft)

381 mm (15.0 in.) 3290 m (10 800 ft) 3303 m (10 835 ft)

408 mm (16.0 in.) 3800 m (12 500 ft) 3822 m (12 540 ft)

Notes:

1. Actual tape base material thickness slightly less because of manufacturingconventions.

2. Original dimensions are in feet. Metric conversions are rounded for convenience.3. Tape-to-flange radial clearance (E-value) is 3.18 mm (0.125 in.).

D-53

7/31/2019 IRIG_106_2009



25.2 Environmental Conditions. The tape shall be able to withstand, with no physical damage

or performance degradation, any natural combination of operating or non-operating conditions as

defined in subparagraphs 25.2.1 and 25.2.2 immediately below.

25.2.1 Tape Storing Conditions. Magnetic tape is subject to deterioration at temperature and

humidity extremes. In some cases, the damage is reversible, but irreversible damage may occur,

especially with long-term storage in unfavorable conditions.

25.2.2 Operating Environment. Recommended limits:

Condition Range

Temperature: 4 to 30oC (40 to 85

oF)

Humidity: 20 to 60 percent relative humidity (RH) non-condensing

Pressure: Normal ground or aircraft operating altitude pressures.For very high altitudes, tape users should consult with

manufacturers to determine if tape and recorder

compatibility is affected by low atmospheric pressure.

1. Binder/oxide system tends to become sticky and unusable above

50oC (125

oF).

2. In low humidity, tape binder and oxide system tends to dry out, and

oxide and binder adhesion can be unsatisfactory. Brown stains on

heads may appear below 40 percent RH.3. In high humidity, abrasivity is increased and other performance

problems may arise.

25.2.3 Non-operating Environment. Temperature and Relative Humidity.

Short Term: 0 to 45 C (32 to 115 F) and 10 to 70 percent RH non-condensing

Long Term: 1 to 30oC (33 to 85

oF) and 30 to 60 percent RH non-condensing

Experience has shown that with long exposure to temperatures belowfreezing, lubricants and plasticizers tend to migrate out of the oxide

coating thereby resulting in poor lubrication and gummy surfacedeposits.

D-54

7/31/2019 IRIG_106_2009



25.3 Other Characteristics. Storage life, bi-directional performance, frictional vibration, and

scatterwind characteristics shall conform to Federal Specification W-T-1553 [SH] unlessotherwise specified by the tape user at the time of purchase.

26.0 Physical Characteristics of Instrumentation Tapes and Reels

As specified in Federal Specifications W-T-1553B, W-T-1553/1-4 and W-R-175.

27.0 Instrumentation Tape Magnetic and Electrical Characteristics

The following subparagraphs describe required magnetic and electrical tape

characteristics.

27.1 Bias Level. The bias level (see bias level definition in paragraph 23.3) required by themagnetic tape shall not differ from the bias level requirements of the reference tape by more than

the amount specified by the tape user. The test procedure outlined in subparagraph 5.3.8.1, Bias

Level, Volume III of RCC Document 118 shall be used to determine compliance with thisrequirement.

27.2 Record Level. The record level (see record level definition in paragraph 23.20) required by the magnetic tape shall not differ from the record level requirements of the reference tape by

more than the amount specified by the tape user. The test procedure outlined in subparagraph

5.3.8.2, Record Level, Volume III of RCC Document 118 shall be used to determine compliancewith this requirement.

27.3 Wavelength Response. The output of the magnetic tape, measured at the wavelength

values listed in Table D-16, Measurement Wavelengths, shall not differ from the output of thereference tape by more than the amounts specified by the tape user. Wavelength response

requirements shall be specified in terms of output after having normalized the output to zerodecibels at the 0.1 UBE wavelength. The test procedure outlined in subparagraph 5.3.9

Wavelength Response and Output at 0.1 Upper Band Edge Wavelength, Volume III of RCC

Document 118 shall be used to determine compliance with this requirement (see Table D-13A,Suggested Wavelength Response Requirements).

D-55

7/31/2019 IRIG_106_2009



TABLE D-16. MEASUREMENT WAVELENGTHS

High-Resolution and HDD Tape High-Energy Tape

(μm) (mils) (μm) (mils)

3810.00 (150.000) 254.00 (10.000)

254.00 (10.000) 25.40 (1.000)

25.40 (1.000) 12.70 (0.500)

6.35 (0.250) 6.35 (0.250)

3.18 (0.125) 3.18 (0.125)

2.54 (0.100) 2.54 (0.100)

2.03 (0.080) 1.52 (0.060)1.52 (0.060) 1.02 (0.040)

0.76 (0.030)

27.4 Output at 0.1 UBE Wavelength. The wavelength output of the magnetic tape shall notdiffer from the 0.1 UBE wavelength of the reference tape by more than the amount specified by

the tape user. The test procedure outlined in subparagraph 5.3.9, Wavelength Response and

Output at 0.1 Upper Band Edge Wavelength, Volume III of RCC Document 118 shall be used todetermine compliance with this requirement.

27.5 Short Wavelength Output Uniformity. The short wavelength output of the magnetic tapeshall be consistently uniform so that a signal recorded and reproduced throughout the working

tape length in either direction of longitudinal tape motion shall remain free from long-termamplitude variation to the extent specified by the tape user. The test procedure outlined in

subparagraph 5.3.10, Short Wavelength Output Uniformity, Volume III of RCC Document 118

shall be used to determine compliance with this requirement.

27.6 Dropouts. The instantaneous non-uniformity (dropout) output of a recorded signal,

caused by the magnetic tape, shall not exceed the center-track and edge-track limits specified by

the tape user on the basis of dropouts per 30.48 m (100 ft.) of nominal working tape length. Thenominal dropout count shall be determined by totaling all the dropouts per track over the

working tape length and dividing by the total number of 30.48 m (100 ft.) intervals tested.

A second method of specifying the allowable dropout count is to specify the maximum

number per track for each 30.48 m (100 ft.) interval tested. This method may be preferred if

critical data is recorded in specific areas of the working tape length, but a specified number of

dropouts per hundred feet greater than the average values may be expected.

D-56

7/31/2019 IRIG_106_2009



Dropout test results are very dependent on the tape transport used for the

test and will vary from run to run on a given transport. Edge tracks tendto contain more dropouts than the center tracks, and more dropouts are

allowed on the edge tracks. Refer to Table D-13.

27.6.1 For High Resolution (HR) tapes, a dropout is defined as a 6 dB reduction in amplitude

for a period of 5 microseconds or more of a 1 MHz sine-wave signal recorded and reproduced at

a tape speed of 3048 mm/s (120). Signal losses of 6 dB or more which exceed the 5 microsecondtime period shall constitute a dropout count for each 5 microsecond time period occurring in the

given signal loss. The definition for center tracks is at paragraph 23.7, and the definition for

edge tracks is at paragraph 23.9. The test procedure outlined in subparagraph 5.3.11, Volume IIIof RCC Document 118 shall be used to determine compliance with this requirement.

27.6.2 For High Density Digital (HDD) tapes, a dropout is defined as a 10 dB or greater reduction in amplitude for a period of 1 microsecond or more of a square-wave test signal of

maximum density recorded and reproduced at 3048 mm/s or 1524 mm/s (120 in/s or 60 in/s). Onat least every other track (7 tracks of the odd head on a 28-track head assembly (alternatively,every other track of the even head) record and reproduce a square-wave test signal of 2 MHz at

3048 mm/s (120 in/s) or 1 MHz at 1524 mm/s (60 in./s). The record level shall be set slightly

above saturation by adjusting the record current to produce maximum reproduce output and

increasing the record current until the output signal is reduced to 90 percent of maximum. For playback, a reproduce amplifier and a threshold detector shall be used. The signal-to-noise ratio

of the test signal at the input to the threshold detector shall be at least 25 dB, and the detector

shall detect any signal loss of 10 dB or more below reference level. The reference level shall beestablished by averaging the test signal output level over a 10 m (30.8 ft.) nominal tape length in

the vicinity of a dropout.

27.6.3 For each of the seven tracks tested, the accumulated duration in microseconds of

detected dropout events shall be displayed and used to directly display the dropout rate for each

track scaled appropriately for the tape working length. Signal losses of 10 dB or more which

exceed the 1 microsecond time period shall constitute a dropout count for each microsecond time period occurring in the given signal loss.

27.6.4 For high-energy tapes, a dropout is defined as for high-resolution tapes except that a 2MHz signal is used.

27.7 Durability. The magnetic tape shall resist deterioration in magnetic and electrical

performance because of wear to the coating surface. Signal losses, as defined below, caused bysurface wear shall not occur in excess of the per-pass limits specified in Table D-14 for the first

35 passes.

Signal losses in excess of those limits specified above shall not occur during either a

record, record and reproduce or uninterrupted reproduce pass of the working tape length. Signal

loss is a reduction in signal amplitude of 3 dB or greater for a period of 3 through 10 seconds of a recorded and reproduced short wavelength signal. Where a continuous loss of signal of 3 dB or

D-57

7/31/2019 IRIG_106_2009



D-58

greater exceeds the 10-second period, a signal loss count shall be required for every sequential

10-second time period occurring in the given signal loss. The test procedure outlined insubparagraph 5.3.12, Durability, Volume III of RCC Document 118 shall be used to determine

compliance with this requirement.

27.8 Modulation Noise. The amplitude modulation superimposed upon a recorded andreproduced signal by the magnetic tape shall not exceed the limits specified by the tape user.

The test procedure outlined in subparagraph 5.3.13, Modulation Noise, Volume III of RCC

Document 118 shall be used to determine compliance with this requirement.

27.9 Layer-to-Layer Signal Transfer. A signal resulting from layer-to-layer signal transfer

shall be reduced in amplitude from the original signal a minimum of 40 dB for 25.4 m (1.0 mil)

tape and 46 dB for 38.1 m (1.5 mils) tape. The test procedure outlined in subparagraph 5.3.14,Layer-to-Layer Signal Transfer, Volume III of RCC Document 118 shall be used to determine

compliance with this requirement.

27.10 Erasure Ease. For HR and HDDR tapes, an erase field of 79.58 kA/M (1000 oersteds)shall effect at least a 60 dB reduction in output amplitude of a previously recorded 25.4 μm (1.0

mil) wavelength signal. For HE tapes, an erase field of 160 kA/m (2000 oersteds) shall effect at

least a 60 dB reduction of a previously recorded 25.4 m (1.0 mil) wavelength signal. The test procedure outlined in subparagraph 5.3.15, Ease of Erasure, volume III of RCC Document 118

shall be used to determine compliance with this requirement.

27.11 Suggested Tape Requirement Limits. Table D-13 lists some suggested limits to be used

for instrumentation tape.

**** END OF APPENDIX D ****

7/31/2019 IRIG_106_2009


Telemetry Standard RCC Document 106-09, Appendix E, April 2009

APPENDIX E

DELETED

AVAILABLE TRANSDUCER DOCUMENTATION

(This Appendix has been intentionally deleted)

7/31/2019 IRIG_106_2009


Telemetry Standard RCC Document 106-09, Appendix F, April 2009

APPENDIX F

CONTINUOUSLY VARIABLE SLOPE DELTA MODULATION


1.0 General.............................................................................................................F-1

2.0 General Descriptions........................................................................................ F-1

3.0 Detailed Descriptions....................................................................................... F-34.0 Reference Level ............................................................................................... F-5

5.0 CVSD Characteristics...................................................................................... F-5

LIST OF FIGURES

Figure F-1a. Typical CVSD encoder...................................................................................... F-2

Figure F-1b. Typical CVSD decoder...................................................................................... F-2

Figure F-2. Typical envelope characteristics of the decoder output signal for CVSD.........F-4Figure F-3. Interface diagram for CVSD converter. ............................................................F-7

Figure F-4a. Insertion loss versus frequency for CVSD (16 kbps)........................................ F-8Figure F-4b. Insertion loss versus frequency for CVSD (32 kbps)........................................ F-8

Figure F-5a. Variation of gain with input level for CVSD (16 kbps). ................................... F-9

Figure F-5b. Variation of gain with input level for CVSD (32 kbps). ................................... F-9Figure F-6a. Signal to quantizing noise ratio vs input level for CVSD (16 kbps). .............F-10

Figure F-6b. Signal to quantizing noise ratio vs. input level for CVSD (32 kbps).............F-10

Figure F-7a. Signal to quantizing noise ratio versus frequency for CVSD (16 kbps). .......F-11

Figure F-7b. Signal to quantizing noise ratio versus frequency for CVSD (32 kbps). .......F-11

LIST OF TABLES

Table F-1. Decoder Reference Digital Patterns for CVSD................................................. F-6

Table F-2. Insertion Loss Limits for CVSD........................................................................ F-7

Table F-3. Idle Channel Noise Limits for CVSD .............................................................F-10

7/31/2019 IRIG_106_2009



ii


7/31/2019 IRIG_106_2009



APPENDIX F

CONTINUOUSLY VARIABLE SLOPE DELTA MODULATION

1.0

General

The continuously variable slope delta (CVSD) modulation is a nonlinear, sampled data,

feedback system which accepts a band-limited analog signal and encodes it into binary form for

transmission through a digital channel. At the receiver, the binary signal is decoded into a close

approximation of the original analog signal. A typical CVSD converter consisting of an encoderand decoder is shown in Figure F-1a and Figure F-1b.

2.0 General Descriptions

A general description of the delta modulation and the CVSD converter can be found in thesucceeding subparagraphs.

2.1 Delta Modulation. Delta modulation is an A-D conversion technique resulting in a form of

digital pulse modulation. A delta modulator periodically samples the amplitude of aband-limited analog signal, and the amplitude differences of two adjacent samples are coded into

n-bit code words. This nonlinear, sampled-data, feedback system then transmits the encoded bit

stream through a digital channel. At the receiving end, an integrating network converts thedelta-modulated bit stream through a decoding process into a close approximation of the original

analog signal.

2.1.2 CVSD Converter. A typical CVSD converter consists of an encoder and a decoder (see

Figure F-1a and Figure F-1b). The analog input signal of the CVSD encoder is band-limited by

the input band, pass filter. The CVSD encoder compares the band-limited analog input signalwith an analog feedback approximation signal generated at the reconstruction integrator output.The digital output signal of the encoder is the output of the first register in the "run-of-three"

counter. The digital output signal is transmitted at the clock (sample) rate and will equal "1" if

the analog input signal is greater than or equal to the analog feedback signal at the instant of sampling. For this value of the digital output signal, the pulse amplitude modulator (PAM)

applies a positive feedback pulse to the reconstruction integrator; otherwise, a negative pulse is

applied. This function is accomplished by the polarity control signal, which is equal to thedigital encoder output signal. The amplitude of the feedback pulse is derived by means of a 3-bit

shift register, logic sensing for overload, and a syllabic lowpass filter. When a string of three

consecutive ONES or ZEROS appears at the digital output, a discrete voltage level is applied to

the syllabic filter, and the positive feedback pulse amplitude increases until the overload string isbroken. In such an event, ground potential is fed to the filter by the overload algorithm, forcing a

decrease in the amplitude of the slope voltage out of the syllabic filter. The encoder and decoder

have identical characteristics except for the comparator and filter functions.

F-1

7/31/2019 IRIG_106_2009



PULSE AMPLITUDE

MODULATOR

SYLLABIC FILTER

OVERLOAD ALGORITHM

(XYZ + XYZ)OUTPUT =

POLARITY CONTROL

DIGITAL OUTPUT S IGNAL

3 - BIT SHIFT REGISTER

X Y Z

CLOCK SIGNAL

COMPARATOR

INPUT BANDPASS

FILTER

RECONSTRUCTION

INTEGRATOR

ANALOG INPUT

SIGNAL

Figure F-1a. Typical CVSD encoder.

SYLLABIC

FILTER

PULSE

AMPLITUDEMODULATOR

RECONSTRUCTION

INTEGRATOR

OUTPUT

LOWPASS FILTER

OVERLOAD ALGORITHM

3 - BIT SHIFT REGISTER

X Y Z

CLOCK SIGNAL

OUTPUT = (XYZ + XYZ)

DIGITAL INPUT SIGNAL

POLARITY CONTROL

ANALOG

OUTPUTSIGNAL

Figure F-1b. Typical CVSD decoder.

The CVSD decoder consists of the input band pass filter, shift register, overload

algorithm, syllabic filter, PAM and reconstruction integrator used in the encoder, and an outputlow-pass filter. The decoder performs the inverse function of the encoder and regenerates speech

by passing the analog output signal of the reconstruction integrator through the low-pass filter.

Other characteristics optimize the CVSD modulation technique for voice signals. Thesecharacteristics include:

a. Changes in the slope of the analog input signal determine the step-size changes of the digital output signal.

b. The feedback loop is adaptive to the extent that the loop provides continuous or

smoothly incremental changes in step size.c. Companding is performed at a syllabic rate to extend the dynamic range of the

analog input signal.

d. The reconstruction integrator is of the exponential (leaky) type to reduce the effects

of digital errors.

F-2

7/31/2019 IRIG_106_2009



3.0 Detailed Descriptions

The characteristics described in subparagraphs 3.1 through 3.9 are in addition to those

specified in paragraph 5.0 of this standard and are for guidance only.

3.1 Input Band Pass Filter. The input filter provides band-limiting and is typically a second-

or higher-order filter (see Figure F-1a).

3.2 Comparator. The comparator compares the band-limited analog input signal from thefilter with the output signal of the reconstruction integrator (see Figure F-1a). This comparison

produces the digital error signal input to the 3-bit shift register. The transfer characteristic of the

comparator is such that the difference between the two input signals causes the output signal tobe driven to saturation in the direction of the sign of the difference.

3.3 3-Bit Shift Register. The 3-bit shift register acts as a sampler which clocks the digitalerror signal from the comparator at the specified data signaling rate and stores the current

samples and two previous samples of the error signal (see Figure F-1a and Figure F-1b). The

digital output signal is a binary signal having the same polarity as the input signal from thecomparator at the time of the clock signal. The digital output signal is also the digital output of

the encoder and is referred to as the baseband signal. Further processing for transmission such as

conditioned diphase modulation may be applied to the baseband signal. It is necessary that theinverse of any such processing be accomplished and the baseband signal restored before the

CVSD decoding process is attempted.

3.4 Overload Algorithm. The overload algorithm operates on the output of the 3-bit shiftregister (X, Y, Z) using the run-of-threes coincidence algorithm so that the algorithm output

equals ( XYZ XYZ ) (see Figure F-1a and Figure F-1b). The output signal is a binary signal at theclock signaling rate and is true for one clock period following the detection of three like bits and

false at all other times.

3.5 Syllabic Filter. The syllabic filter acts as a low-pass filter for the output signal from theoverload algorithm (see Figures F-1a and Figure F-1b). The slope-voltage output of the syllabic

filter is the modulating input to the PAM. The step-function response of the syllabic filter is

related to the syllabic rate of speech, is independent of the sampling rate, and is exponential innature. When the overload algorithm output is true, a charging curve is applicable. When this

output is false, a discharging curve is applicable.

3.6 Pulse Amplitude Modulator (PAM). The PAM operates with two input signals: the output

signal from the syllabic filter, and the digital signal from the 3-bit shift register (see Figures F-1a

and b). The syllabic filter output signal determines the amplitude of the PAM output signal andthe signal from the 3-bit shift register is the polarity control that determines the direction, plus or

minus, of the PAM output signal. The phrase "continuously variable" in CVSD is derived from

the way the PAM output signal varies almost continuously.

F-3

7/31/2019 IRIG_106_2009



3.7 Reconstruction Integrator. The reconstruction integrator operates on the output signal of the PAM to produce an analog feedback signal to the comparator (or an output signal to the

output low-pass filter in the receiver) that is an approximation of the analog input signal (see

Figures F-1a and b).

3.8 Output Low-Pass Filter. The output filter is a low-pass filter having a frequency responsethat typically has an asymptotic rolloff with a minimum slope of 40 dB per octave, and astopband rejection that is 45 dB or greater (see Figure F-1b). The same output filter

characteristic is used for encoder digital output signals of either 16 or 32 kbps.

3.9 Typical CVSD Decoder Output Envelope Characteristics. For a resistance/ capacitancecircuit in the syllabic filter with time constants of 5 ms for both charging and discharging, the

envelope characteristics of the signal at the decoder output are shown in Figure F-2. For the case

of switching the signal at the decoder input from the 0-percent run-of-threes digital pattern to the30-percent run-of-threes digital pattern, the characteristic of the decoder output signal follows

the resistance/capacitance charge curve. Note that the number of time constants required to

reach the 90-percent charge point is 2.3, which gives a nominal charge time of 11.5 ms.

When switching the other way (from the 30-percent pattern to the 0-percent pattern), the

amplitude at the beginning of discharging is, at the first moment of switching, higher (by a factor

of 16) than the final value which is reached asymptotically. The final value equals 24 dBm0,that is, 0.03. Therefore, the amplitude at the beginning of discharging is 0.48 (percent run-of-threes = 0). Note that the number of time constants required to reach the 10-percent point on the

discharge curve is 1.57, which gives a nominal discharge time of 7.8 ms.

1.0 (Cd=0.3)

ENVELOPE0.9

0.48 BEGINNING OF

DISCHARGING (Cd=0)

0.1

0.03 (Cd=0)

6.2 to9.2 to

13.8 ms 9.4 ms TIME, ms

NOTES:1. Cd is duty cycle.

2. Figure is half of the envelope.

Figure F-2. Typical envelope characteristics of the decoder output signal for

CVSD.

F-4

7/31/2019 IRIG_106_2009



4.0 Reference Level

The decoder analog output level with the 16 and 32 kbps, 30-percent run-of-threesreference digital pattern applied to the decoder input shall be the reference level for the CVSD

requirements of this standard and shall be designated 0 dBm0 (see subparagraph 5.9.1).

5.0 CVSD Characteristics

The characteristics of CVSD are described in the following subparagraphs.

5.1 Input and Output Impedances. The analog input and output impedances for CVSD

converters are not standardized. These impedances depend upon the application of the converters.

5.2 Data Signaling Rates. The CVSD converter shall be capable of operating at 16 and 32

kbps.

5.3 Input and Output Filters. The analog input shall be band pass filtered. The analog output

shall be low pass filtered.

Details of input and output filers, consistent with the CVSD performance

requirements of this standard, will be determined in applicable equipmentspecifications based on validated requirements

5.4 Overload Algorithm. A 3-bit shift register shall be used for the CVSD encoder and decoder

(see Figure F-1a and Figure F-1b). The overload logic shall operate on the output of this shift

register using the run-of-threes coincidence algorithm. The algorithm output signal shall be abinary signal at the data-signaling rate. This signal shall be true for one clock period following

the detection of three like bits (all ZEROS or all ONES) and false at all other times.

5.5 Compression Ratio. The compression ratio shall be nominally 16:1 with a maximum of 21:1and a minimum of 12:1. The maximum slope voltage shall be measured at the output of thesyllabic filter for a 30-percent run-of-threes digital pattern. The minimum slope voltage shall be

measured at the output of the syllabic filter for a 0-percent run-of-threes digital pattern.

5.6 Syllabic Filter. The syllabic filter shall have a time constant of 5 ms 1. The step functionresponse of the syllabic filter shall be exponential in nature. When the output of the overload

algorithm is true, a charge curve shall be applicable. When the output of the overload algorithmis false, a discharge curve shall be applicable.

5.7 Reconstruction Integrator Time Constant. The reconstruction integrator shall have a time

constant of 1 ms 0.25.

F-5

7/31/2019 IRIG_106_2009



5.8 Analog-to-Digital Conversion. An 800-Hz 10 signal at a 0 dBm0 level applied to the inputof the encoder shall give a duty cycle (Cd) of 0.30 at the algorithm output of the encoder shown in

Figure F-la.

5.9 Digital-to-Analog Conversion. The characteristics of a digital-to-analog conversion are

described in the following subparagraphs.

5.9.1 Relation of Output to Input. With the applicable reference digital patterns of Table F-1

applied to the digital input of the decoder as shown in Figure F-3, the analog output signal shall

be 800 Hz 10 at the levels shown in Table F-1, measured at the decoder output. These digitalpatterns, shown in hexadecimal form, shall be repeating sequences.

5.9.2 Conversion Speed. When the decoder input is switched from the 0-percent run-of-threes

digital pattern to the 30-percent run-of-threes digital pattern, the decoder output shall reach 90

percent of its final value within 9 to 14 ms. When the decoder input is switched from the 30-percentrun-of-threes digital pattern to the 0-percent run-of-threes digital pattern, the decoder output shall

reach 10 percent of the 30-percent run-of-threes value within 6 to 9 ms. These values shall apply toboth the 16 and 32-kbps data signaling rates.

5.10 CVSD Converter Performance. The characteristics specified in subparagraphs 5.10.1 through

5.10.7 apply to one CVSD conversion process obtained by connecting the output of an encoder to theinput of a decoder (see Figure F-3).

Test signal frequencies that are submultiples of the data signaling rate shallbe avoided by offsetting the nominal test frequency slightly; for example,

an 800-Hz test frequency could be offset to 804 Hz. This test frequency

offset will avoid nonlinear distortion, which can cause measurement

difficulties when CVSD is in tandem with PCM.

TABLE F-1. DECODER REFERENCE DIGITAL PATTERNS FOR CVSD

Data Signaling Rate

(kpbs)

Digital

Pattern

Run-of-threes,

(percent)

Output

(dBm0)

16 DB492 0 241

32 DB54924AB6 0 241

16 FB412 30 01

32 FDAA10255E 30 01

F-6

7/31/2019 IRIG_106_2009



INTERFACE POINTS

ENCODER ENCODER DECODER DECODER

INPUT OUTPUT INPUT OUTPUT

REFERENCE DIGITAL ANALOG SIGNAL

PATTERN INPUT OUTPUT

ANALOG SIGNAL ENCODER DIGITAL TRANSMISSION DECODER ANALOG SIGNALINPUT 16 kbps OR 32 kbps OUTPUT

DECODER

Figure F-3. Interface diagram for CVSD converter.

5.10.1 Companding Speed. When an 800-Hz 10 sine wave signal at the encoder input is

switched from 24 dBm0 to 0 dBm0, the decoder output signal shall reach 90 percent of its finalvalue within 9 to 14 ms.

5.10.2 Insertion Loss. The insertion loss between the encoder input and the decoder output shall

be 0 dB 2 dB with an 800 Hz 10, 0 dBm0 input to the encoder.

5.10.3 Insertion Loss Versus Frequency Characteristics. The insertion loss between the encoder

input and decoder output, relative to 800 Hz 10 measured with an input level of 15 dBm0applied to the converter input, shall not exceed the limits indicated in Table F-2 and shown in

Figure F-4a and Figure F-4b.

TABLE F-2. INSERTION LOSS LIMITS FOR CVSD

Rate

(kpbs)Frequency ( f )

(Hz)Insertion Loss (dB)

(Referenced to 800 Hz)

16 f 300

300 f 1000

1000 f 2600

2600 f 4200

4200 f

1.5

1.5 to 1.5

5 to 1.5

5

25

32 f 300

300 f 1400

1400 f 2600

2600 f 3400

3400 f 4200

4200 f

1

1 to 13 to 1

3 to 2

3

25

F-7

7/31/2019 IRIG_106_2009



Figure F-4a. Insertion loss versus frequency for CVSD (16 kbps).

Figure F-4b. Insertion loss versus frequency for CVSD (32 kbps).

5.10.4 Variation of Gain With Input Level. The variation in output level, relative to the value at

15 dBm0 input, shall be within the limits of Figure F-5a and Figure F-5b for an input frequency of

800 Hz 10.

5.10.5 Idle Channel Noise. The idle channel noise shall not exceed the limits shown in Table F-3

when measured at the CVSD decoder output.

5.10.6 Variation of Quantizing Noise With Input Level. The minimum signal to quantizing

noise ratio over the input signal level range shall be above the limits of Figure F-6a and FigureF-6b. The noise ratio shall be measured with flat weighting (unweighted) at the decoder output

with a nominal 800-Hz 10 sine wave test signal at the encoder input.

F-8

7/31/2019 IRIG_106_2009



5.10.7 Variation of Quantizing Noise With Frequency. The minimum signal to quantizing noise

ratio over the input frequency range shall be above the limits of Figure F-7a and Figure F-7b.

The noise ratio shall be measured with flat weighting (unweighted) at the decoder output with a

sine wave test signal of 15 dBm0.

Figure F-5a. Variation of gain with input level for CVSD (16 kbps).

Figure F-5b. Variation of gain with input level for CVSD (32 kbps).

F-9

7/31/2019 IRIG_106_2009



TABLE F-3. IDLE CHANNEL NOISE LIMITS FOR CVSD

Data Signaling Rate (kbps) Idle Channel Noise (dBm0)

16 40

32 50

Figure F-6a. Signal to quantizing noise ratio vs input level for

CVSD (16 kbps).

Figure F-6b. Signal to quantizing noise ratio vs. input level forCVSD (32 kbps).

F-10

7/31/2019 IRIG_106_2009



F-11

Figure F-7a. Signal to quantizing noise ratio versus frequency for

CVSD (16 kbps).

Figure F-7b. Signal to quantizing noise ratio versus frequency forCVSD (32 kbps).

**** END OF APPENDIX F ****

7/31/2019 IRIG_106_2009


Telemetry Standard RCC Document 106-09, Appendix G, April 2009

APPENDIX G

ADARIO DATA BLOCK FIELD DEFINITIONS


1.0 Data Block Format and Timing........................................................................ G-1

2.0 ADARIO Data Format Field Definitions Summary......................................... G-4

3.0 Submux Data Format Field Definitions ......................................................... G-104.0 SubMux Data Format Field Definitions Summary ........................................ G-11

LIST OF FIGURES

Figure G-1. ADARIO data format...................................................................................... G-2

Figure G-2. ADARIO data blocks...................................................................................... G-3

Figure G-3. ADARIO timing. ............................................................................................ G-4

Figure G-4a. Submux data format...................................................................................... G-18Figure G-4b. Submux data format...................................................................................... G-19

Figure G-5. Submux aggregate format............................................................................. G-20

7/31/2019 IRIG_106_2009



ii


7/31/2019 IRIG_106_2009



APPENDIX G

ADARIO DATA BLOCK FIELD DEFINITIONS

1.0 Data Block Format and Timing

The details of the ADARIO data block format are provided in Figure G-1 and in the

ADARIO data format field summary. As shown in Figure G-1, the eight session header words arethe first eight words of the block. The channel packet for the highest priority (priority 1) channel

is next, followed by the next lower priority channel packet (priority 2). Following the lowest

priority channel, fill data consisting of all ones are inserted as required to complete the 2048-worddata block.

Within the channel packet, the first five words are the channel header words including the

partial word (PW). Following the channel header is the variable size channel data field. Thechannel data are organized in a last-in-first-out (LIFO) fashion. The first samples acquired in the

block time interval appear in the last data word of the channel packet. The sample data are

formatted into the 24-bit data word such that the first sample occupies the MSBs of the word. Thenext sample is formatted into the next available MSBs and so on until the word is full. As an

example, data formatted into 8-bit samples is shown in Figure G-2.

In cases where the 24-bit data word is not a multiple of the sample size, the sample

boundaries do not align with the data words. In these cases, the samples at the word boundaries

are divided into two words. The MSBs of the sample appear in LSBs of the first buffered word

and the LSBs of the sample appear in the MSBs of the next buffered word. Since the channel

data appears in a LIFO fashion in the ADARIO data block, the MSBs of the divided sample willoccur in the data word following the word containing LSBs of the sample. Figure G-3 depicts

ADARIO timings.

G-1

7/31/2019 IRIG_106_2009



Figure G-1. ADARIO data format.

G-2

7/31/2019 IRIG_106_2009



G-3

Figure G-2. ADARIO data blocks.

7/31/2019 IRIG_106_2009



Figure G-3. ADARIO timing.

2.0 ADARIO Data Format Field Definitions Summary

2.1 Block Length - (2048 words, 24-bit words, fixed length)

2.2 Session Header - (8 words, fixed format)

SHW0 (bits 23 to 0) SYNC Field, bits 0-23 of the 29-bit block sync. The LSBs

of the block sync are 36E19C and are contained here.

SHW1 (bits 23 to 19) SYNC Field, bits 24-28 of the 29-bit block sync. The

MSBs of the block sync are 01001 and are contained here.The 29-bit block sync is fixed for all ADARIO

configurations and chosen for minimal data cross

correlation.

(bits 18 to 0) MC, Master Clock, a 19-bit binary value in units of 250 Hz.

MC is the clock frequency used to derive session and perchannel parameters.

SHW2 (bits 23 to 0) BLK#, ADARIO Data Block Number, a 24-bit binary

value. BLK# is to zero at the start of each session andcounts up consecutively. Rollover is allowed.

G-4

7/31/2019 IRIG_106_2009



SHW3 (bits 23 to 0) YYMMDD, Time Code Field, a BCD representation of theyear (YY), month (MM), and day (DD). YYMMDD Time

Code Field is updated during the record process once per

second.

SHW4 (bits 23 to 0) HHMMSS, Time Code Field, a BCD representation of thehour (HH), minute (MM), and second (SS). TheHHMMSS Time Code Field is updated during the record

process once per second.

SHW5 (bits 23 to 0) BMD, Block Marker Divisor, a 24-bit binary value. BMDis established so that the block marker frequency, BM, may

be derived from MC by BM = MC/BMD

SHW6 (bit 23) MCS, Master Clock Source, a 1-bit flag.1 = MC was generated internally.

0 = MC was provided from an external source.

(bits 22 to 19) Q, Number of active channels minus one, a 4-bit binary

value. For example, 0 indicates that one channel is active.

(bits 17 to 18) SP1, Spare field 1, a 2-bit field. It is set to zero.

(bits 16 to 0) SST, Session Start Time, a 17-bit binary value in units of

seconds. The integer number of seconds represents thesession start time of day in seconds, where midnight starts

with zero.

SHW7 (bits 23 to 16) User Defined, an 8-bit field. May be input by the user at

any time during a recording session. The interpretation of this bit field is left to the user.


(bits 5 to 0) VR, Version number, a 6-bit binary value. Each update of

the ADARIO format will be identified by a unique version

number.

2.3 Channel ‘n’ Header All channel headers contain five 24-bit ADARIO words

with the following fixed format. The first logical channel,n=1, has the highest priority and its channel packet starts in

the ninth word of the data block. Each active channel is

represented by a channel packet that is present in the datablock. The logical channel number, n, represents the

relative priority of the channel and the order in which it

appears in the data block.

G-5

7/31/2019 IRIG_106_2009



CnHW0 (bits 23 to 20) CH#, Physical Channel Number, a 4-bit binary value. 0 to15 represents the physical location of the channel

electronics in the ADARIO hardware. The user sees those

locations labeled from 1 to 16.

(bits 19 to 16) FMT, Format code for the channel data word, a 4-bit binaryvalue. The format code is used to define the size of theuser data word by means of the following table:

15 = 24 bits 7 = 8 bits

14 = 22 bits 6 = 7 bits13 = 20 bits 5 = 6 bits

12 = 18 bits 4 = 5 bits

11 = 16 bits 3 = 4 bits10 = 14 bits 2 = 3 bits

9 = 12 bits 1 = 2 bits

8 = 10 bits 0 = 1 bit

(bits 15 to 5) WC, Word Count, an 11-bit binary value. WC is the

number of full channel data words that should be in the nth

channel packet. WC may range from 0 to 2040. A WCgreater than the number of actual words in channel packet

indicates a data rate overflow, which would occur when a

low-priority channel is not provided sufficient space in thefixed length data block as a result of an uncontrolled data

rate in a higher priority channel.

(bits 4 to 0) PWS, Partial Word Status, a 5-bit binary value. PWS is

related to the number of samples in the partial word andmay range from 0 to 23. PWS shall be computed as

follows:

If the number of full samples in the partial wordequals zero, then PWS = 0.

If the number of full samples in the partial word

does not equal zero, then PWS = Round Up [Unused bits In

PW/Channel Sample Size].

G-6

7/31/2019 IRIG_106_2009



CnHW1 (bit 23) IE, Channel Clock Source, a 1-bit flag.1 = The channel clock was generated internally.

0 = The channel clock was provided from an external

source.

(bit 22) DA, Data type, a 1-bit flag.1 = The channel is operated as a digital channel.0 = The channel is operated as an analog channel.

(bit 21) ROVR, Rate overrun in previous block, a 1-bit flag.

1 = The nth channel packet in the previous data block experienced an overrun.

0 = The nth channel packet in the previous data block

did not experience an overrun.

(bit 20) AOVR, Analog A/D Overrange in current block a 1-bit

flag. 1 = The nth channel in the current data block

experienced an analog-to-digital conversion overrange

condition.

0 = The nth channel in the current data block did notexperience an analog-to-digital conversion overrange

condition.

(bit 19) NSIB, No samples in current block, a 1-bit flag.

1 = TRUE, there are no samples for the nth channel inthe current block.

0 = False, there are samples for the nth channel in the

current block.

(bits 18 to 0) RATE, Channel sample rate indicator, 19-bit binary value.

The interpretation of the rate value depends on thecondition of IE, the channel clock source flag.

If IE = 1, then the value of rate is carried by the 16

LSBs of the rate field. Using rate, the frequency of the

internal channel clock can be found by internal sampleclock = (MC/RATE) -1.

IF IE = 0, then rate is a 19-bit binary value in units of

250 Hz which equals the frequency of the external channelclock as provided by the user at the time of the setup.

G-7

7/31/2019 IRIG_106_2009



The definitions that are marked with an asterisk apply to analog channels

and to particular hardware implementations of ADARIO. For the purposesof this standard, these fields are not used.

* CnWD2 (bits 23 to 16) FB, Filter Bandwidth, an 8-bit binary value. The formula

for the bandwidth, BW, of the anti-aliasing filter used in ananalog channel incorporates FB as BW = (FB/2) • 103+FR

(bits 15 to 0) TD, Time Delay to first sample, a 16-bit binary value. TDis a measure of the time delay from the block marker, BM,

to the first sample arriving at the nth channel during the

current data block interval. TD is expressed as the number

of master clock, MC, periods minus one.

* CnWD3 (bits 23 to 22) FR, Filter Range, a 2-bit binary value. The formula for the

bandwidth, BW, of the anti-aliasing filter used in an analog

channel corporates FR as BW = (FB/2) • 103+FR

(bits 21 to 17) ATTEN, Attenuation, a 5-bit binary value. ATTEN

represents the setting of the input attenuator (or gain) on the

nth channel at the time that the record was formed 0 =

15dB and 31 = +16dB with intermediate settingsexpressed in one dB steps.

(bit 16) DCAC, Analog signal coupling, a 1-bit flag.

1 = The channel is operated with dc coupling at the input.

0 = The channel is operated with ac coupling at the input.

(bits 15 to 8) CHP, Channel Parameter field, an 8-bit field. The

interpretation of the CHP field depends upon the card typewith which it is associated, as defined by the CHT field.

Each card type established by the CHT field, as part of its

definition, shall specify the form and interpretation of the

CHP field. To date, four input card types have been

established. The CHP fields are defined as follows:

G-8

7/31/2019 IRIG_106_2009



* For CHT=0(bits 15 to 8) remain undefined for the present analog single channel

implementation except that the present hardware implementation

expects an all zero field. Would be subject to future definition aslong as all the zero fill is set aside.

* For CHT=1

(bits 15 to 8) remain unused for the present digital single channel

implementations except that the present hardware implementation

expects an all zero field. Would be subject to future definition aslong as the all zero fill is set aside.

* For CHT=2

(bits 15 to 8) remain unused for the present dual-purpose channel

implementations except that the present hardware implementation

expects an all zero field. Would be subject to future definition as

long as the all zero fill is set aside.

For CHT=3(bits 15 to 12) establish the number of subchannels that are multiplexed into the

multichannel data carried by the nth channel.

(bits 11 to 8) identify the subchannel number of the first sample contained in thenth channel packet of the data block.


(bits 5 to 0) CHT, Channel Type, a 6-bit field. Defines the type of channelthrough which input data was acquired. Additional channel typesto be defined by future users and developers.

* CHT=0 Single channel analog input

* CHT=1 Single channel digital input

* CHT=2 Single channel, dual-purpose, analog or digital input

* CHT=3 Multichannel analog input capable of multiplexing

up to 16 analog inputs

* CHT=4 Single channel digital input, dual channel analog

input (stereo)“L” channel on bits 15 to 8 of the sample word,“R” channel on bits 7 to 0 of the sample word

CHT=5 Single channel, triple-purpose, analog, digital, submux,

formatted input

CnWD4 (bits 23 to 0) PW, Partial Word, A 24-bit field. PW contains the lastsamples of the data block. The most significant bits of

G-9

7/31/2019 IRIG_106_2009



word contain the first sample, followed by the next samplein the next most significant bits. The number of samples in

the PW is defined in the PWS field. The unused bits are

not intentionally set and so contain random data.

Fill (bits 23 to 0) Fill, Fill Words consisting of all ones binary, used for fixedrate aggregate. Fill words may be omitted when variablerate aggregate can be accommodated resulting in variable

length blocks of up to 2048, 24-bit words.

3.0 Submux Data Format Field Definitions

The details of the submux data format are shown in Figures G-4a and b and defined in theSubmux Data Format Field Definitions Summary. Figure G-5 shows a typical primary channel

aggregate data content for fixed and variable rate channel. Submux data format is based on the

sequential collection of the individual channel data blocks. Each channel data block is thesequential collection of presented input samples in a fixed period of time. This sequential

collection results in a variable length, fixed rate, and channel data blocks. To accommodate

fixed rate channels, fill is also defined. The aggregate data stream is composed of a block sync

timing channel, followed by sequential channel data blocks, if enabled, followed by fill, if required, at fixed block rate.

The channel data blocks are the sequential collection of input samples bit packed intosequential 16-bit words over the block period of time. The data block is preceded by a three-

word header that identifies the source (channel ID) of data, channel type of processing, packing

format in the data block, bit count length of the valid data, and the time delay between the firstsample and the block period. If data were internally sampled, the sample period is defined with

the first sample being coincident with the start of block period. Channel type is used to definespecific types of channels that provide timing, annotation, and synchronization functions that

may be required by the specific primary channel or may be redundant and not required. Specific

implementation of the required channels may provide only the required channels with specificimplementation constraints that limit the aggregate rate or the range of any specific field.

The submux format is based on a 16-MHz clock defining all timing. The derived clock is

the 16-MHz clock divided in binary steps as defined by 2BRC

that defines all timing and internalsampling. Block period is 20 160 derived clock periods which limits the submux aggregate to

256 Mbps, limits the maximum block rate to 793.65 blocks per second, and in conjunction with a

16-bit bit count field, limits the subchannel maximum data rate to 52 Mbps.

G-10

7/31/2019 IRIG_106_2009



4.0 SubMux Data Format Field Definitions Summary

4.1 Frame length. Variable or fixed with fill. Minimum is 3-word block sync plus onechannel block, maximum is 20 160x16-bit words.

4.2 Block length: Variable from 3x16-bit words to 4099x16-bit words per channel datablock. Specified by CHT0 and integer of (Bit_Count+15/16). May belimited by implementation.

4.3 Block sync: Defined by Channel ID = 31, 3-word block, 2-word sync. Defines a

period of 20 160 derived clocks.

4.4 General form: All Channel data blocks contain this information in the 3-word header.

HW1 (bits 15 to 11) CHN ID, Channel ID number, from 0 to 30 binary numberrepresents normal channel of any type. CHN ID = 31 reserved for

Block Sync.

(bits 10 to 8) CHT, Channel Type, from 0 to 7 defines type of processingperformed on the data and the format of header word fields.

CHT = 0 Timing channel, block sync or time tag, 3-wordonly

CHT = 1 Annotation text or block count, variable length

CHT = 2 Digital serial external or internal clock, variableCHT = 3 Digital parallel external clock, variable

CHT = 4 Analog wide band, variable

CHT = 5 Analog stereo, variableCHT = 6 TBD (to be defined by future implementation)

CHT = 7 TBD

Variable length: General form with variable data block length

HW1 (bits 15 to 11) CHN ID, Channel ID number, from 0 to 30 binary number

represents normal channel of any type.

(bits 10 to 8) CHT, Channel Type, from 1 to 7 defines type of processing

performed on the data and the format of header word fields.

(bits 7 to 4) FMT, Format, defines the number of bits minus one in each

sample. Data block sample size (bits) = (FMT+1). Range 0 to

15, binary format.

(bits 3 to 0) ST1 to ST4, status bits, define dynamic conditions within this

block period such as over range.

G-11

7/31/2019 IRIG_106_2009



HW2 (bits 15 to 0) Bit_Count defines the number of valid data bits in the data block starting with the most significant bit of the first data word DW1.

Variable word length of the data block is the Integer of

{(Bit_Count + 15)/16}. Range 0 to 65 535, binary format.

HW3 (bit 15) I/E, Internal/External clock

(bits 15 to 0) Depends on CHT field, defines block count, time delay, or sample

period.

4.5 Block Sync: Defines the start of channel data blocks and start of block period that lasts for20 160 derived clocks.

HW1 (bits 15 to 0) SYNC 1 = F8C7 hex, defines the first sync word.

HW2 (bits 15 to 0) SYNC 2 = BF1E hex, defines the second sync word.

HW3 (bits 15 to 13) BRC, Block Rate Clock, defines the binary divisor for the 16 MHz

system clock. Derived CLK = 16 MHz / 2BRC

MHz. Block rate =

Derived CLK / 20 160 Hz. Period = 1 / Derived CLK.

(bit 12) FILL, indicates if the primary channel requires fill for constant

rate.

(bits 11 to 4) TBD

(bit 3) AOE, Aggregate Overrun Error if set indicates that the aggregate

of the enabled channels exceeds the submux aggregate (datatruncated to 20 160 words between sync).

(bit 2) PCRE, Primary Channel Rate Error if set indicates that primary

channel is unable to maintain the aggregate rate of the submux.

Excess blocks are truncated.

(bits 1 to 0) ST3, ST4, Status reserved.

4.6 Time Tag: Defines the time tag channel for time stamping the frame.

HW1 (bits 15 to 11) CHN ID, Channel ID number, from 0 to 30 binary numberrepresents normal channel.

(bits 10 to 8) CHT = 0, Channel Type = 0, Time Tag IRIG Time code

processing and 3-word format.

HW (bits 7 to 0) DAYS, Most significant 8 bits of Time Code Days field. BCD

format.

G-12

7/31/2019 IRIG_106_2009



(bits 15 to 14) DAYS, Least significant 2 bits of Time Code Days field. BCD

format.

(bits 13 to 8) HOURS, Time Code Hours 6 bit field. BCD format.

HW (bits 7 to 0) MINUTES, Time Code Minutes 7 bit field. BCD format.

(bits 15 to 8) SECONDS, Time Code Seconds 7 bit field. BCD format.

(bits 7 to 0) FRACTIONAL SECONDS, Time Code Fractional Seconds 8 bitfield. BCD format.

4.7 Annotation Text: Defines block count and annotation text that pertains to the subchannelsat this time.


(bits 10 to 8) CHT = 1, Channel Type = 1, Block Count and Annotation Text if

any.

(bits 7 to 4) FMT = 7, Format = 7, defines 8 bit ASCII character in text.

(bit 3 ) NC, No Characters (Bit_Count = 0) Block count only.

(bits 2 to 0) OVR, PE, OE, Overrun Parity and async framing error.

HW (bits 15 to 0) Bit_Count defines the number of valid data bits in the data block starting with the MSB of the first data word DW1. Variable word

length of the data block is the Integer of {(Bit_Count + 15)/16}.

Range 0 to 65 535, binary format.

HW (bits 15 to 0) Block_Count sequential block numbering with rollover at

maximum. Range 0 to 65 535, binary format.

DW1 (bits 15 to 8) 1st CHARACTER, first text character.

DW (bits 8 or 0) Last CHARACTER, LSB is defined by the Bit Count.

4.8 Digital Serial External CLK: Defines digital serial data such as PCM externally clocked.


represents normal channel.

G-13

7/31/2019 IRIG_106_2009



(bits 10 to 8) CHT = 2, Channel Type = 2, digital serial or data and clock oversampled data.

(bits 7 to 4) FMT = 0 Format = 0, defines 1-bit data samples.

(bit 3 ) NSIB, No Samples In Block (Bit_Count=0) header only.(bit 2 ) OVR, Overrun indicates that input is clocking at faster thanspecified rate. Data is truncated at specified bit rate (Bit Count per

Block).

HW (bits 15 to 0) Bit_Count, defines the number of valid data bits in the data block starting with the most significant bit of the first data word DW1.

Variable word length of the data block is the Integer of

{(Bit_Count + 15)/16}. Range 0 to 65 535, binary format.Limited by set maximum rate.

HW (bit 15 ) I/E = 0, Internal / External clock flag indicates that externalclocking was used with relative phasing to block as specified in

next field.

(bits 14 to 0) Time Delay provides the measure of time between start of block period and the first external clock in derived clock periods. Range

0 to 20 160, binary format.

DW1 (bit 15) DS1, first data sample at the first clock time in the block.

Dwn (bit L) DSL, last data sample in this block period.

4.9 Digital Serial Internal CLK: Defines digital serial data low rate (> 2 samples per block

period) internally oversampled.



(bits 10 to 8) CHT = 2, Channel Type = 2, Digital serial or data and clock over

sampled data.

(bits 7 to 4) FMT = 0 Format = 0, defines 1-bits data samples.

(bits 3 to 0) 0, reserved.

HW2 (bits 15 to 0) Bit_Count defines the number of valid data bits in the data block

starting with the most significant bit of the first data word DW1.

Variable word length of the data block is the Integer of {(Bit_Count + 15)/16}. Range 0 to 65 535, binary format.

Limited by set maximum rate.

G-14

7/31/2019 IRIG_106_2009



HW3 (bit 15 ) I/E = 1, Internal Sampling flag indicates that internal sampling wasused as specified in next field.

(bits 14 to 9) TBD

(bits 8 to 0) SAMPLE PERIOD, defines the period of the over-sampling clock that samples data and clock, in derived clock periods. Range 0 to 4mega samples per second, binary format.

DW1 (bit 15) DS1, first data sample at block time.

(bit 7) CS1, first clock sample at block time.

DWn (bit 8 ) DSL, last data sample in this block period.

(bit 0) CSL, last clock sample in this block period.

4.10 Digital Parallel External CLK: Defines digital data including serial externally clocked.



(bits 10 to 8) CHT = 3, Channel Type = 3, Digital parallel or serial data.

(bits 7 to 4) FMT, Format, defines the number of bits minus one in each

sample. Data block sample size (bits) = (FMT+1). Range 0 to15, binary format.

(bit 3 ) NSIB, No Samples In Block (Bit_Count = 0) Header only.

(bit 2 ) OVR, Overrun indicates that input is clocking at faster than specified

rate. Data is truncated at specified bit rate (Bit Count per Block).


starting with the most significant bit of the first data word DW1.

Variable word length of the data block is the Integer of ((Bit_Count + 15)/16). Range 0 to 65 535, binary format. Limited

by set maximum rate.

HW3 (bit 15 ) I/E = 0, Internal / External clock flag indicates that external

clocking was used with relative phasing to block as specified in

next field.

G-15

7/31/2019 IRIG_106_2009



(bits 14 to 0) Time delay provides the measure of time between start of block period and the first external clock in derived clock periods. Range

0 to 20 160, binary format.

DW1 (bit 15) DS1, MSB of the first data sample at the first clock time in the block.

DWn (bit L) DSL, LSB of the last data sample in this block period.

4.11 Analog Wide Band: Defines analog wide band data using a sampling A/D and internal

block synchronous clock.



(bits 10 to 8) CHT = 4, Channel Type = 4, analog wide band sampled data.

(bits 7 to 4) FMT, Format, defines the number of bits minus one in eachsample. Data block Sample Size (bits) = (FMT+1). Range 0 to15, binary format. Limited by the A/D resolution.

(bit 3 ) AOR, Analog over range (A/D 4-msb = F).

(bits 2 to 0) ST2 to ST4, reserved status

HW2 (bits 15 to 0) Bit_Count defines the number of valid data bits in the data block starting with the MSB of the first data word DW1. Variable wordlength of the data block is the Integer of ((Bit_Count + 15)/16).

Range 0 to 65 535, binary format. Limited by set maximum rate.

HW3 (bit 15 ) I/E = 1, Internal Sampling flag indicates that internal sampling wasused as specified in next field.

(bits 14 to 12) TBD

(bits 11 to 0) Sample Period defines the period of the over-sampling clock that

samples data and clock, in derived clock periods. Range 0 to 4msamples per second, binary format.

DW1 (bit 15) DS1, MSB of the first data sample at the first clock time in theblock.


4.12 Analog Stereo "L" & "R": Defines analog stereo data using a sigma-delta A/D andinternal block synchronous clock with tracking Finite Impulse Response (FIR) filter.

G-16

7/31/2019 IRIG_106_2009



G-17


(bits 10 to 8) CHT = 5, Channel Type = 5, Analog stereo voice band data.(bits 7 to 4) FMT, Format defines the number of bits minus one in each sample.

Data block sample size (bits) = (FMT+1). Range 0 to 15, binaryformat. Limited by the A/D resolution.

(bit 3 ) LAOR, left subchannel over range.

(bit 2 ) RAOR, right subchannel over range.

(bits 1 to 0) ST2 to ST4, reserved status.


starting with the MSB of the first data word DW1. Variable word

length of the data block is the Integer of {(Bit_Count + 15)/16}.Range 0 to 65 535, binary format. Limited by set maximum rate.

HW3 (bit 15 ) I/E = 1, Internal Sampling flag indicates that internal sampling was

used as specified in next field.

(bit 14) ENL, Enable Left subchannel.

(bit 13) ENR, Enable Right subchannel.

(bit 12) TBD

(bits 11 to 0) Sample period defines the period of the over-sampling clock thatsamples data and clock, in derived clock periods. Range 3.76 to

40K samples per second, binary format.

DW1 (bit 15) DS1, MSB of the first data sample left subchannel if enabled.

(bit 15- DS1, MSB of the first data sample right subchannel if enabled,

(FMT-1) else second sample.


4.13 Fill: Defines fill word that can be inserted at the end of all channel data blocks if requiredby the constant rate primary channel.

Fwx (bits 15 to 0) FILL, defined as FFFF hex word.

7/31/2019 IRIG_106_2009



16 BITS

15 14 13 12 11 10 9 8 7 6 5

General Form HW1 CHN ID CHT FMT

HW2

HW3 I/E TIME DELAY or SAMPLE PERIO

Frame Sync HW1 CHN ID = 1F CHT = 0 SY

G-1 8

HW2 SYNC 2 = BF1E hex

HW3 BRC FILL

Time Tag HW1 CHN ID = 0 to 30 CHT = 0 MSB DA

HW2 DAYS lsb HOURS (BCD) lsb

HW3 SECONDS (BCD) lsb FR

Annotation HW1 CHN ID = 0 to 30 CHT = 1 FMT = 7

Text HW2 BIT_COUNT

HW3 BLOCK COUNT

DW1 msb 1ST CHARACTER lsb msb 2

:

DWn msb Last CHARACTER lsb

Digital Srl. HW1 CHN ID = 0 to 30 CHT = 2 FMT = 0

Ext. CLK HW2 BIT_COUNT = L

HW3 I/E=0 TIME DELAY

DW S1 D 1 DS2 DS3 DS4 DS5 DS6 DS7 DS8 DS9 DS1 DS

:DWn DSL-1 DSL

Figure G-4a. Submux data format.

7/31/2019 IRIG_106_2009



15 14 13 12 11 10 9 8 7 6 5

HW1 CHN ID = 0 to 30 CHT = 2 FMT = 0

G-1 9

Digital Serial

Int. CLK HW2 BIT_COUNT = L

HW3 I/E=1 SA

DW1 DS1 DS2 DS3 DS4 DS5 DS6 DS7 DS8 CS1 CS2 CS3

:

DWn DSL-7 DSL-6 DSL-5 DSL-4 DSL-3 DSL-2 DSL-1 DSL CSL-7 CSL-6 CSL-

HW1 CHN ID = 0 to 30 CHT = 3 FMT=0 to 15 (shoDigital Parallel

Ext. CLK HW2 BIT_COUNT = L

HW3 I/E=0 TIME DELAY

DW1 MSB 1ST SAMPLE MSB 2ND SAMPLE

:

DWn MSB Last SAMPLE LSB=bit L U

HW1 CHN ID = 0 to 30 CHT = 4 FMT=0 to 15 (sho Analog

Wide Band HW2 BIT_COUNT = L

HW3 I/E=1 SAMPLE PERIO

DW1 MSB 1ST

SAMPLE MSB 2nd

SAM

:

DWn MSB Last SAMPLE LSB=bit L U

HW1 CHN ID = 0 to 30 CHT = 5 FMT=0 to 15 (show

HW2 BIT_COUNT = L

Analog

Stereo

"L" & "R" HW3 I/E=1 ENL ENR SAMPLE PERIO

DW1 MSB 1ST SAMPLE “L” MSB 1ST SAM

:

DWn MSB Last SAMPLE U

Fill FW Fill Word = FFFF hex

Figure G-4b. Submux data format.

7/31/2019 IRIG_106_2009



Fixed RateChannel

Variable RateChannel

Frame 1 Block

Sync

Frame 1 Block

Sync

CHN #0 CHN #0

CHN #1 CHN #1

CHN #3 CHN #3

CHN #17 CHN #17

CHN #18 CHN #18

FILL

Frame 2 Block Sync

Frame 2 Block Sync

CHN #0 CHN #0

CHN #1 CHN #1

CHN #3 CHN #3

CHN #17 CHN #17

CHN #18 CHN #18

FILL

Figure G-5. Submux aggregate format.

**** END OF APPENDIX G ****

G-20

7/31/2019 IRIG_106_2009


Telemetry Standard RCC Document 106-09, Appendix H, April 2009

APPENDIX H

APPLICATION OF THE TELEMETRY ATTRIBUTES TRANSFER STANDARD


1.0 Elements of the Telemetry Attributes Transfer Process................................. H-1

LIST OF FIGURES

Figure H-1. Typical elements of the telemetry attributes transfer process......................... H-2

7/31/2019 IRIG_106_2009



ii


7/31/2019 IRIG_106_2009



APPENDIX H

APPLICATION OF THE TELEMETRY ATTRIBUTES TRANSFER STANDARD

1.0 Elements of the Telemetry Attributes Transfer Process

Interchange of telemetry attributes occurs between vehicle instrumentation organizations(the source) and the telemetry ground stations (the destination). Interchange may also take place

between ranges. The following are typical elements of this process:

a. data entry systemb. source database

c. export program

d. interchange medium [this standard]e. import program

f. destination data base

g. telemetry setup systemh. telemetry processing equipment.

These elements are depicted in Figure H-1 and are defined as follows:

1.1 Data entry system. The data entry system is the source organization's human interface

where telemetry attributes are entered into a computer-based system (not affected by this

standard).

1.2 Source database. The source database is where telemetry attributes are maintained in a

form appropriate to the local organization's needs (not affected by this standard).

1.3 Export program. The export program converts the telemetry attributes from the sourcedatabase format to the format defined by this standard and stores them on the interchangemedium.

1.4 Interchange medium. The interchange medium contains the telemetry attributes being

transferred from the source organization to the destination organization. Format and contents aredefined by this standard.

1.5 Import program. The import program reads the standardized interchange medium andconverts the attributes to the destination data base format in accordance with local needs, system

characteristics, and limitations.

1.6 Destination data base. The destination data base is where telemetry attributes are

maintained in a form suitable to the local ground station's needs (not affected by this standard).

H-1

7/31/2019 IRIG_106_2009



Human

Interface

Data Entry

System A

Source A

Database

Export

Program A

Export

Program B

Source B

Data Entry

System B

Human

Interface

Source Organization A

Source Organization B

StandardizedInterchange

Medium

StandardizedInterchange

Medium

Destination Organization X

Telemetry

Equipment X

Telemetry

Setup X

Destination

Database X

Import

Program X

Import

Program Y

Destination

Database Y

Telemetry

Setup Y

TelemetryEquipment Y

Destination Organization Y

Figure H-1. Typical elements of the telemetry attributes transfer process.

H-2

7/31/2019 IRIG_106_2009



H-3

1.7 Telemetry setup system. The telemetry setup system accesses the destination database to

load the telemetry processing equipment. (Not affected by this standard.)

1.8 Telemetry processing equipment. The telemetry processing equipment is where the

attributes will ultimately be used to properly handle the data being transmitted. (Not affected bythis standard.)

The interchange medium is intended as a standard means of information exchange. The

source and destination organizations are not constrained by this standard as to how the attributes

are stored, viewed, used, or maintained.

To use the attribute transfer standard, import and export software must be developed.

Once in place, these programs should eliminate the need for test item or project-specific softwareat either the supplying (source) organizations or the processing (destination) organizations.

**** END OF APPENDIX H ****

7/31/2019 IRIG_106_2009


Telemetry Standard RCC Document 106-09, Appendix I, April 2009

APPENDIX I

TELEMETRY ATTRIBUTES TRANSFER STANDARD COVER SHEET

1.0

Cover Sheet

Each attribute transfer file (disk or tape) should be accompanied by a cover sheet

describing the originating agency's computer system used to construct the attribute file. The

recommended format for this cover sheet is given below as Figure I-1.

Telemetry Attributes Transfer Standard

Date: MM\DD\YY

From: Name

Address

Telephone

To: Name

Address

Telephone

Originating computer system:

Computer make and model:

Medium characteristics:

Description:

Comments:

Figure I-1. Sample cover sheet for attribute transfer files.

**** END OF APPENDIX I ****

7/31/2019 IRIG_106_2009


Telemetry Standard RCC Document 106-09, Appendix J, April 2009

APPENDIX J

TELEMETRY ATTRIBUTES TRANSFER STANDARD FORMAT EXAMPLE


1.0 Introduction ........................................................................................................J-1

2.0 Overview of Example.........................................................................................J-1

LIST OF FIGURES

Figure J-1. Group linkages....................................................................................................J-2Figure J-2. PCM format for PCM w/async...........................................................................J-5

Figure J-3. PCM format for PCM1.......................................................................................J-6

Figure J-4. PCM format for async. .......................................................................................J-7

7/31/2019 IRIG_106_2009



ii


7/31/2019 IRIG_106_2009



APPENDIX J

TELEMETRY ATTRIBUTES TRANSFER STANDARD FORMAT EXAMPLE

1.0 Introduction

The following example is for illustrative purposes and is by no means a completeattributes file; it is representative of the types of information likely to be transferred. Many

attributes are purposely omitted to simplify the example. In some of the groups, only those

entries necessary to link to other groups are provided. Attributes, which link the various groups

together, are indicated in boldface.

2.0 Overview of Example

Selected attributes are described in text form as an aid to following the example. All text,

which describes the example, is printed in italics. All text, which is part of the example file, isprinted in plain text.

The example file being transferred consists of the attributes of a single RF data source

and an analog tape containing two data sources. The RF data source is a PCM signal, whichcontains an embedded asynchronous wave train. The two recorded data sources are PCM

signals: one is an aircraft telemetry stream, and the other is a radar data telemetry stream.

Figure J-1 shows the example file in terms of the attribute groups and their interrelationships.Refer to the attribute tables while reviewing the example.

J-1

7/31/2019 IRIG_106_2009



Data Link

Name

General

Information

Group

(G)

Transmission

Attributes

Group

(T-1)

Multiplex/

Modulation

Group(M-1)

PCM Format

Group

(P-1)

Multiplex/

Modulation

Group(M-3)

PCM Format

Group

(P-3)

PCM

Measurement Description

Group

(D-2)

PCM

Measurement

Description

Group

(D-1)

Data

Conversion

Group

(1)

Data

Conversion

Group

(2)

Data

Conversion

Group

(3)

Data

Conversion

Group

(4)

Data

Conversion

Group

(5)

Data

Conversion

Group

(6)

Data

Conversion

Group

E1250T;

Data Link

NamePCM w/

async;

J896D; J951V; J971V;W862P; J966X;

Measurement Names

Data Link

NameASYNC;

PCM


Group

(D-4)

PCM


Group

PCM Format

Group

(P-4)

PCM Format

Group

(P-2)

Data Link

NameSPI Data Link

NamePCM1;

PCM w/

async; Data Link

Name SPI; Data Link

NamePCM1;

Data Link

Name

ASYNC;

(D-3)

82AJ01;

(7)

Multiplex/

Modulation

Group(M-2)

Tape

Source

Group

(R-1)

Data Source ID

PCMw/embedded;

Data Source ID

Two PCM

links - TMand TSPI;

Data Source Data Source Data Source

ID

PCM

w/subframe

fragmentedSpace

Position;

PCM

w/embedded; ID

Figure J-1. Group linkages.

J-2

7/31/2019 IRIG_106_2009



General Information Group (G)

Program name, test name, origination date, revision number: 0,

test number: 13.

G\PN: TMATS example; G\TA: Wright Flyer; G\OD: 07-12-41; G\RN:0; G\TN:13; G\POC1-1:Wilbur; G\POC2-1: Bikes,LTD; G\POC3-1: Dayton;

G\POC4-1: 555-1212;

Live data source.

G\DSI-1:PCM w/embedded; G\DST-1:RF;

Tape source.

G\DSI-2:Two PCM links - TM & TSPI; G\DST-2:TAP;G\COM: I hope this flies.; G\POC1-2: Orville;

G\POC2-2:Bikes,LTD; G\POC3-2: Dayton; G\POC4-2: 555-1212;

Transmission Attributes Group (T-1)

Frequency: 1489.5, RF bandwidth: 100, data bandwidth: 100;

not encrypted, modulation type: FM, total carrier modulation: 500,

no subcarriers, transmit polarization: linear.

T-1\ID:PCM w/embedded; T-1\RF1:1489.5; T-1\RF2:100; T-1\RF3:100;T-1\RF4:FM; T-1\RF5:500; T-1\SCO\N:NO; T-1\AN2:LIN; T-1\AP\POC1:

Pat Tern; T-1\AP\POC2:Transmissions,Inc.;

T-1\AP\POC3:Amityville,NY; T-1\AP\POC4:800-555-1212;

Tape Source Attributes Group (R-1)

R-1\ID:Two PCM links - TM & TSPI; R-1\R1:Reel #1; R-1\TC1:ANAL; R-1\TC2:ACME; R-1\TC3:795;

Tape width: 1 inch, reel diameter: 14 inches, 14 tracks,

record speed: 7.5 inches/second.

R-1\TC4:1.0; R-1\TC5:14.0; R-1\N:14; R-1\TC6:7.5;

J-3

7/31/2019 IRIG_106_2009



Rewound: Yes, manufacturer: ZZ; model: 13, original: yes.

R-1\TC8:Y; R-1\RI1:ZZ; R-1\RI2:13; R-1\RI3:Y;R-1\RI4:07-12-91-07-55-59; R-1\POC1:Mr. Reel; R-1\POC2:Tape Creations; R-

1\POC3:Anywhere,Ttown; R-1\POC4:555-1212;

Track Number 2 contains aircraft telemetry PCM (w/subframe

fragmented)

R-1\TK1-1:2; R-1\TK2-1:FM/FM;

R-1\DSI-1:PCM w/subframe fragmented; R-1\TK3-1:FWD;

Track Number 4 contains Space Position Information via PCM link

R-1\TK1-2:4; R-1\DSI-2:Space Position Information;

Multiplex/Modulation Groups (M-1, M-2, M-3)

Baseband type: PCM, modulation sense: POS, baseband data: PCM,

low pass filter type: constant amplitude

M-1\ID:PCM w/embedded; M-1\BB1:PCM; M-1\BB2:POS; M-1\BSG1:PCM;

M-1\BSF2:CA;

M-1\BB\DLN:PCM w/async;

M-2\ID:PCM w/subframe fragmented; M-2\BB\DLN:PCM1;

M-3\ID:Space Position; M-3\BB\DLN:SPI;

_________________________________________________________________

PCM Format Attributes Groups (P)

P-1 is a live PCM signal and contains the asynchronous wave

train (see Figure J-2).

P-2 is a recorded signal (see Figure J-3).

P-3 is the asynchronous wave train (see Figure J-4).

P-4 is a recorded signal.

J-4

7/31/2019 IRIG_106_2009



Sync 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 • • • 39 40 41 42

20bits

Embedded

Format(Words

6-10)

8Bi

t

s

SU

B

4

2

b

1

2

3

4

5

6

7

8

•

•

•

16

ID

C

o

un

t

er

12B

i

t

s

SU

B

1

5

a

aa

a

a

aa

a

••

•

a

Major frame characteristics:One major frame = 16 minor frames

Word lengths = 10 bits (default value) except Word 10 has 8 bits

and Word 11 has 12 bits

a = measurement E1250T at minor frame position 39

b = measurement W862P in subframe SUB42, position 8.

PCM Format Group = P-1

PCM Measurement Description Group = D-2

Data Link Name = PCM w/async

Figure J-2. PCM format for PCM w/async.

J-5

7/31/2019 IRIG_106_2009



Sync 1 2 3 • • • 12 13 14 • • • 113 114 • • • 120 121 122 • • • 276

30

bits

SUB

113

SUB

121

M L

6

Bits

4

Bits

M L

1

2

3

4

5•

•

•

32•

•

•

37•

••

64

ID

C

ou

n

te

r

Major frame characteristics:One major frame = 64 minor frames

Subframes SUB113 and SUB121 are 32 deep

ID counter counts 0 - 63

Word lengths = 10 (default value) except Word 121 has 6 bitsand Word 122 has 4 bits

Measurement 82AJ01 is 16 bits, which is fragmented with the 10 mostsignificant bits indicated as M and the 6 least significant bits as L.

The measurement is located in position 5 of subframes SUB113 and SUB121

(minor frames 5 and 37 of the major frame).



Data Link Name = PCM1

Figure J-3. PCM format for PCM1.

J-6

7/31/2019 IRIG_106_2009



Sync 1 2 3 ••• 11 ••• 14 ••• 20 ••• 29 ••• 33 ••• 39 ••• 45 46 47 48 49

1 a b ••• a ••• c ••• a ••• a•••

a ••• •••

a

2 a ••• a ••• ••• a ••• a ••• a ••• •••

A

SU

B

2a

3

16Bi

t

s

ID

C

ou

n

te

r a

AS

U

B

1••• a •••

AS

U

B

3••• a ••• a ••• a •••

c

AS

U

B3

••• d a

Major frame characteristics:

One major frame = 3 minor frames

Word lengths = 16 bits (default value)

a = measurement J971U, supercommutated at positions 2, 11, 20, 29, 33, and 47

b = measurement J951V in subframe ASUB1, position 1

c = measurement J896D in supercommutated subframe ASUB3, positions 1 and 4

d = measurement J966X in subframe ASUB2, position 3



Data Link Name = ASYNC

Figure J-4. PCM format for async.

_______________________________________________________________________________

(Start of P-1)

Live PCM signal (host wave train) : Class I

P-1\DLN:PCM w/async; P-1\D1:NRZ-L; P-1\D2:44000; P-1\D3:U;P-1\D4:N; P-1\D6:N; P-1\D7:N; P-1\TF:ONE;

10 bits default word length, 16 minor frames/major frame, 43 words/frame

P-1\F1:10; P-1\F2:M; P-1\F3:NO; P-1\MF\N:16; P-1\MF1:43;

P-1\MF2:440; P-1\MF3:FPT; P-1\MF4:20;P-1\MF5: 01111010011010110001; P-1\SYNC1:1; P-1\SYNC2:0;

P-1\SYNC3:1;P-1\SYNC4:0;

Word position #10, 8 bits,

Word position #11, 12 bits

P-1\MFW1-1:10; P-1\MFW2-1:8; P-1\MFW1-2:11; P-1\MFW2-2:12;

J-7

7/31/2019 IRIG_106_2009



One subframe ID counter

P-1\ISF\N:1; P-1\ISF1-1:1; P-1\ISF2-1:ID; P-1\IDC1-1:1;

ID counter word length : 10 bits, MSB starting bit location : 7,

ID counter length : 4

P-1\IDC2-1:10; P-1\IDC3-1:7; P-1\IDC4-1:4; P-1\IDC5-1:M;

P-1\IDC6-1:0; P-1\IDC7-1:1; P-1\IDC8-1:15; P-1\IDC9-1:16;P-1\IDC10-1:INC;

Subframe definition

SUB42 is located at 42, SUB15 at 15.

All have depth 16.

P-1\SF\N-1:2;

P-1\SF1-1-1:SUB42; P-1\SF2-1-1:NO;

P-1\SF4-1-1-1:42; P-1\SF6-1-1:16;P-1\SF1-1-2:SUB15; P-1\SF2-1-2:NO;

P-1\SF4-1-2-1:15; P-1\SF6-1-2:16;

Asynchronous embedded wave train information

Data Link Name (to be referenced in the format definition of the

asynchronous wave train) is ASYNC.

Five contiguous minor frame word positions starting at location 6.

P-1\AEF\N:1; P-1\AEF\DLN-1:ASYNC; P-1\AEF1-1:5; P-1\AEF2-1:CW;P-1\AEF3-1-1:6;

(End of P-1)

______________________________________________________________________________

(Start of P-2)

Recorded PCM signal format attributes.

Data Link Name is PCM1, Data Format is NRZ-L, Bit rate is 2 Mbit/sec,

Unencrypted, Normal polarity, class I, Common word length is 10, MSB first, No

parity, 64 minor frames per major frame, 277 words per minor frame, Sync pattern

length is 30. Word position 121 is 6 bits. Word position 122 is 4 bits.

J-8

7/31/2019 IRIG_106_2009



P-2\DLN:PCM1;P-2\D1:NRZ-L; P-2\D2:2000000; P-2\D3:U; P-2\D4:N;P-2\TF:ONE; P-2\F1:10; P-2\F2:M; P-2\F3:NO; P-2\MF\N:64;

P-2\MF1:277; P-2\MF4:30; P-2\MF5:101110000001100111110101101011; P-2\SYNC1:1; P-

2\MFW1-1:121; P-2\MFW2-1:6; P-2\MFW1-2:122;P-2\MFW2-2:4;

Subframe characteristics:

One subframe ID counter named 1. Sync type is ID counter. ID counter location is

13. ID counter word length is 10. ID counter MSB location is 5. ID counter length

is 6. ID counter transfer order is MSB first. ID counter initial value is 0. ID

counter initial subframe is 1. ID counter end value is 63. ID counter end subframe

is 64. ID counter is increasing.

Two subframes. First subframe name is SUB121. Not supercommutated, subframe

location = word position 121, depth = 32. Second subframe name is SUB113. Not

supercommutated, location = 113, depth = 32.


P-2\IDC2-1:10; P-2\IDC3-1:5; P-2\IDC4-1:6; P-2\IDC5-1:M;P-2\IDC6-1:0; P-2\IDC7-1:1; P-2\IDC8-1:63; P-2\IDC9-1:64;

P-2\IDC10-1:INC; P-2\SF\N-1:2; P-2\SF1-1-1:SUB121;

P-2\SF2-1-1:NO; P-2\SF4-1-1-1:121; P-2\SF6-1-1:32;P-2\SF1-1-2:SUB113; P-2\SF2-1-2:NO; P-2\SF4-1-2-1:113;

P-2\SF6-1-2:32;

(End of P-2)

______________________________________________________________________________

(Start of P-3)

Asynchronous wave train PCM format attributes.

Data Link Name: ASYNC

Class I, Common word length: 16, LSB transfer order, no parity, 3 minor frames per major

frame, 50 words/minor frame, 800 bits per minor frame, fixed pattern synchronization, 16

bit sync pattern.

P-3\DLN:ASYNC; P-3\TF:ONE; P-3\F1:16; P-3\F2:L; P-3\F3:NO;

P-3\MF\N:3; P-3\MF1:50; P-3\MF2:800; P-3\MF3:FPT; P-3\MF4:16;

P-3\MF5: 1111100110110001; P-3\SYNC1:1;

Subframe definition.

Three subframes with ID counter word length 16 at word position 1.

J-9

7/31/2019 IRIG_106_2009




P-3\IDC2-1:16; P-3\IDC3-1:15; P-3\IDC4-1:2; P-3\IDC5-1:L;

P-3\IDC6-1:0; P-3\IDC7-1:1; P-3\IDC8-1:2; P-3\IDC9-1:3;P-3\IDC10-1:INC;

ASUB1 is at word position 3.

ASUB2 is at word position 45.

ASUB3 is supercommutated at word positions 14 and 39.

P-3\SF\N-1:3; P-3\SF1-1-1:ASUB1; P-3\SF2-1-1:NO; P-3\SF3-1-1:NA;P-3\SF4-1-1-1:3; P-3\SF6-1-1:3; P-3\SF1-1-2:ASUB2;

P-3\SF2-1-2:NO; P-3\SF3-1-2:NA; P-3\SF4-1-2-1:45; P-3\SF6-1-2:3;

P-3\SF1-1-3:ASUB3; P-3\SF2-1-3:2; P-3\SF3-1-3:EL;P-3\SF4-1-3-1:14; P-3\SF4-1-3-2:39; P-3\SF6-1-3:3;

(End of P-3)

(Start of P-4)

P-4\DLN:SPI;

(End of P-4)

______________________________________________________________________________

PCM Measurement Description (D)

D-1 contains the measurements which make up the asynchronous wave train,

D-2 contains the measurements which make up the live PCM signal (which hosts the

asynchronous wave train),

D-3 contains the measurements which make up one of the recorded PCM signals, and

D-4 contains the measurements which make up the other recorded PCM signal.

______________________________________________________________________________

(Start of D-1)

Asynchronous Wave Train: One measurement list, 4 measurements

D-1\DLN:ASYNC; D-1\ML\N:1; D-1\MLN-1:JUST ONE; D-1\MN\N-1:4;

Measurement Name : J896D, LSB first,

J-10

7/31/2019 IRIG_106_2009



Subframe supercommutated, 2 locations: 1 and 4 of ASUB3.

D-1\MN-1-1:J896D; D-1\MN3-1-1:L; D-1\LT-1-1:SFSC;D-1\SFS1-1-1:ASUB3; D-1\SFS\N-1-1:2; D-1\SFS2-1-1:E;

D-1\SFS6-1-1-1:1; D-1\SFS6-1-1-2:4; D-1\SFS7-1-1-1:FW;D-1\SFS7-1-1-2:FW;

Measurement Name: J951V, LSB first, default parity, subframe ASUB1, location 1.

D-1\MN-1-2:J951V; D-1\MN1-1-2:DE; D-1\MN2-1-2:D; D-1\MN3-1-2:L; D-1\LT-1-2:SF;D-1\SF2-1-2:1; D-1\SFM-1-2:1111111100000000;

D-1\SF1-1-2:ASUB1;

Measurement Name : J971U, LSB first,

supercommutated at positions 2, 11, 20, 29, 33, and 47.

D-1\MN-1-3:J971U; D-1\MN1-1-3:DE; D-1\MN2-1-3:D; D-1\MN3-1-3:L;

D-1\LT-1-3:MFSC; D-1\MFS\N-1-3:6; D-1\MFS1-1-3:E;

D-1\MFSW-1-3-1:2; D-1\MFSW-1-3-2:11; D-1\MFSW-1-3-3:20;

D-1\MFSW-1-3-4:29; D-1\MFSW-1-3-5:33; D-1\MFSW-1-3-6:47;

Measurement Name : J966X, LSB first, subframe ASUB2, location 3.

D-1\MN-1-4:J966X; D-1\MN1-1-4:DE; D-1\MN2-1-4:D;

D-1\MN3-1-4:L; D-1\LT-1-4:SF; D-1\SF1-1-4:ASUB2;D-1\SF2-1-4:3; D-1\SFM-1-4:FW;

(End of D-1)

_____________________________________________________________________________

(Start of D-2)

Live PCM signal: single measurement list, 2 measurements.

D-2\DLN:PCM w/async; D-2\MLN-1:JUST ONE; D-2\MN\N-1:2;

Measurement name: E1250T, unclassified, unsigned, MSB first.

D-2\MN-1-1:E1250T; D-2\MN1-1-1:DE; D-2\MN2-1-1:D;

D-2\MN3-1-1:M; D-2\LT-1-1:MF; D-2\MF-1-1:39; D-2\MFM-1-1:FW;

Measurement name: W862P, unclassified, MSB first,

subframe name: SUB42, location 8 in subframe, full word.

J-11

7/31/2019 IRIG_106_2009



D-2\MN-1-2:W862P; D-2\MN1-1-2:DE; D-2\MN2-1-2:D; D-2\MN3-1-2:M; D-2\LT-1-2:SF;D-2\SF1-1-2:SUB42; D-2\SF2-1-2:8; D-2\SFM-1-2:FW;

(End of D-2) ______________________________________________________________________________

(Start of D-3)

Recorded PCM signal: single measurement list: 1 measurement.

D-3\DLN:PCM1; D-3\MLN-1:ONLY ONE; D-3\MN\N-1:1;

Measurement name: 82AJ01, subframe fragmented, 2 fragments,

subframes: SUB113 and SUB121, subframe location: 5.

D-3\MN-1-1:82AJ01; D-3\LT-1-1:SFFR; D-3\FSF\N-1-1:2;

D-3\FSF1-1-1:16; D-3\FSF2\N-1-1:2; D-3\FSF3-1-1-1:SUB113;D-3\FSF3-1-1-2:SUB121; D-3\FSF4-1-1-1:E; D-3\FSF8-1-1-1-1:5;

(End of D-3)

______________________________________________________________________________

(Start of D-4)

Recorded PCM signal

D-4\DLN:SPI;

(End of D-4)

______________________________________________________________________________

Data Conversion Groups (C)

C-1 and C-2 are measurements which are part of the live PCM signal (see also D-

2).

C-3, C-4, C-5, and C-6 are from the asynchronous wave train (see also D-1).

C-7 is from the recorded PCM signal (see also D-3).

Measurement: E1250T, description: Inlet Temp Bellmouth, units: Deg C, binary

format: unsigned; high value: 128, low value: 0.4, conversion type: pair sets,

number of pair sets: 2, application (polynomial) : Yes; order of fit: 1, telemetry

value #1: 0, engineering unit value #1: 0.4, telemetry value #2: 1023,

engineering unit value #2: 128.

J-12

7/31/2019 IRIG_106_2009



C-1\DCN:E1250T; C-1\MN1:Inlet Temp Bellmouth; C-1\MN3:DEGC;

C-1\BFM:UNS; C-1\MOT1:128; C-1\MOT2:-0.4; C-1\DCT:PRS;

C-1\PS\N:2; C-1\PS1:Y; C-1\PS2:1; C-1\PS3-1:0; C-1\PS4-1:-0.4;C-1\PS3-2:1023; C-1\PS4-2:128;

Measurement: W862P, description: Fuel Pump Inlet, binary format: unsigned; conversion

type: pair sets, number of pair sets: 2, application (polynomial): Yes; order of fit: 1,

telemetry value #1: 0, engineering unit value #1: 0.1 telemetry value #2: 1023,

engineering unit value #2: 76.7

C-2\DCN:W862P; C-2\MN1:Fuel Pump Inlet; C-2\BFM:UNS;

C-2\DCT:PRS; C-2\PS\N:2; C-2\PS1:Y; C-2\PS2:1; C-2\PS3-1:0;C-2\PS4-1:-0.1; C-2\PS3-2:1023; C-2\PS4-2:76.7;

Measurement: J896D, description: Terrian Altitude, units: Feet, binary format:

two’s complement; high value: 32768, low value: -32768, conversion type: pair sets; number of pair sets: 2, application (polynomial): Yes, order of fit: 1, telemetry

value #1: -32768, engineering unit value #1: -32768, telemetry value #2: 32767,

engineering unit value #2: 32767

C-3\DCN:J896D; C-3\MN1:Terrian Altitude; C-3\MN3:FEET;

C-3\BFM:TWO; C-3\MOT1:32768; C-3\MOT2:-32768; C-3\DCT:PRS;C-3\PS\N:2; C-3\PS1:Y; C-3\PS2:1; C-3\PS3-1:-32768;

C-3\PS4-1:-32768; C-3\PS3-2:32767; C-3\PS4-2:32767;

Measurement: J951V, description: Throttle Command, units: VDC, high value:

10.164, low value: -10.164, conversion type: pair sets, number of pair sets: 2,application(polynomial): Yes, order of fit: 1, telemetry value #1: -128,

engineering unit value #1: -10.164, telemetry value #2: 127, engineering unit

value #2: 10.164, binary format: two's complement

C-4\DCN:J951V; C-4\MN1:Throttle Command; C-4\MN3:VDC;

C-4\MOT1:10.164; C-4\MOT2:-10.164; C-4\DCT:PRS; C-4\PS\N:2;C-4\PS1:Y; C-4\PS2:1; C-4\PS3-1:-128; C-4\PS4-1:-10.164;

C-4\PS3-2:127; C-4\PS4-2:10.164; C-4\BFM:TWO;

Measurement: J971U; description: DISC, conversion type: discrete, binary format:

unsigned.

C-5\DCN:J971U; C-5\MN1:DISC; C-5\DCT:DIS; C-5\BFM:UNS;

Measurement: J966X; description: Discrete, conversion type: discrete, binary

format: unsigned.

C-6\DCN:J966X; C-6\MN1:Discrete; C-6\DCT:DIS; C-6\BFM: UNS;

J-13

7/31/2019 IRIG_106_2009



J-14

Measurement: 82AJ01, description: LANTZ Norm acceleration,

units: MTR/S/S, High value: 1023.97, Low value: -1023.97,

conversion type: Coefficients

Order of curve fit: 1, derived from pair sets: No,

Coefficient (0): 0, Coefficient(1): 0.03125, binary format: two's complement

C-7\DCN:82AJ01; C-7\MN1:LANTZ Norm acceleration; C-7\MN3:MTR/S/S;

C-7\MOT1:1023.97; C-7\MOT2:-1023.97; C-7\DCT:COE; C-7\CO\N:1;

C-7\CO1:N; C-7\CO:0; C-7\CO-1:.03125; C-7\BFM:TWO;

**** END OF APPENDIX J ****

7/31/2019 IRIG_106_2009


Telemetry Standard RCC Document 106-09, Appendix K, April 2009

APPENDIX K

PULSE AMPLITUDE MODULATION STANDARDS


1.0 General ............................................................................................................. K-1

2.0 Frame and Pulse Structure................................................................................ K-1

3.0 Frame and Pulse Rate ....................................................................................... K-34.0 Frequency Modulation...................................................................................... K-4

5.0 Premodulation Filtering.................................................................................... K-4

LIST OF FIGURES

Figure K-1. 50-percent duty cycle PAM with amplitude synchronization. ......................... K-2

Figure K-2. 100-percent duty cycle PAM with amplitude synchronization. ....................... K-2

7/31/2019 IRIG_106_2009



ii


7/31/2019 IRIG_106_2009



APPENDIX K

PULSE AMPLITUDE MODULATION STANDARDS

1.0 General

This standard defines the recommended pulse train structure and design characteristicsfor the implementation of PAM telemetry systems. The PAM data are transmitted as time

division multiplexed analog pulses with the amplitude of the information channel pulse being the

analog-variable parameter.

2.0 Frame and Pulse Structure

Each frame consists of a constant number of time-sequenced channel intervals. The

maximum shall be 128 channel time intervals per frame, including the intervals devoted to

synchronization and calibration. The pulse and frame structure shall conform to eitherFigure K-1 or Figure K-2.

2.1 Commutation Pattern. The information channels are allocated equal and constant time

intervals within the PAM frame. Each interval ("T" in Figures K-1 and K-2) contains a samplepulse beginning at the start of the interval and having amplitude determined by the amplitude of

the measurand of the corresponding information channel according to a fixed relationship

(usually linear) between the minimum level (zero amplitude) and the maximum level (full-scaleamplitude). For a 50-percent duty cycle (RZ-PAM), the zero level shall be 20 to 25 percent of

the full amplitude level as shown in Figure K-1. The pulse width shall be the same in all time

intervals except for the intervals devoted to synchronization. The duration shall be either 0.5T±0.05, as shown in Figure K-1, or T ±0.05, as shown in Figure K-2.

2.2 In-Flight Calibration. It is recommended that in-flight calibration be used and channels 1and 2, immediately following the frame synchronization interval, be used for zero and full-scalecalibration. For RZ-PAM, channel 3 may be used for an optional half-scale calibration, and for

NRZ-PAM, the channel interval preceding channel 1 may be used for half-scale calibration if set

to 50 percent.

2.3 Frame Synchronization Interval. Each frame is identified by the presence within it of a

synchronization interval.

2.3.1 Fifty Percent Duty Cycle (RZ-PAM). The synchronization pattern interval shall have a

duration equal to two information channel intervals (2T) and shall be full-scale amplitude for

1.5T followed by the reference level or zero baseline for 0.5T (see Figure K-1).

K-1

7/31/2019 IRIG_106_2009



MIN. SIGNAL(See Note)

TIME

CHANNEL 3

2.OT HALF SCALE

CALIBRATION (Optional)

FRAME

MAX. SIG

SYNC

INTERVAL

CENTER

FREQUENCY

T TT 1.5T

2 2CHANNEL 2

CHANNELINTERVAL

FULL SCALECALIBRATION (Optional)

ZERO BASELINE

(Reference Level) CHANNEL 1

ZERO CALIBRATION

(Optional)

Figure K-1. 50-percent duty cycle PAM with amplitude synchronization.

A 20-25 percent deviation reserved for pulse synchronization is

recommended.

5.0 T T T

TIME FRAME SYNCINTERVAL

CENTERFREQUENCY

CHANNEL 2

T 3.0 TFULL SCALE

CALIBRATION(Optional)

CHANNEL

INTERVAL

THIS LEVEL TO BE 50% LESSCHANNEL 1ZERO CA IBRATION L

(Optional) HALF SCALE CALIBRATION(0ptional) IF SET AT 50%

Figure K-2. 100-percent duty cycle PAM with amplitude synchronization.

K-2

7/31/2019 IRIG_106_2009



2.3.2 One Hundred Percent Duty Cycle (NRZ-PAM). The synchronization pattern is in theorder given: zero level for a period of T, full-scale amplitude for a period of 3T, and a level not

exceeding 50-percent full-scale amplitude for a period T (see Figure K-2).

2.4 Maximum Pulse Rate. The maximum pulse rate should not be greater than that permitted

by the following subparagraphs.

2.4.1 PAM/FM/FM. The reciprocal of the shortest interval between transitions in the PAM

pulse train shall not be greater than one-fifth of the total (peak-to-peak) deviation specified in

Chapter 3 (Table 3-1A, Table 3-1B, and Table 3-1C) for the FM subcarrier selected.

2.4.2 PAM/FM. The reciprocal of the shortest interval between transitions in the PAM pulse

train shall be limited by whichever is the narrower of the following:

2.4.2.1 One-half of the 3-dB frequency of the premodulation filter when employed.

2.4.2.2 One-fifth of the intermediate frequency (IF) bandwidth (3 dB points) selected from theIF bandwidths listed in Chapter 2, Table 2-2.

3.0 Frame and Pulse Rate

The frame and pulse parameters listed below may be used in any combination:

a minimum rate of 0.125 frames per second, and

a maximum pulse rate as specified in subparagraph 2.1.4.

3.1 Long Term Accuracy and Stability. During a measured period of desired data, the timebetween the occurrence of corresponding points in any two successive frame synchronization

intervals should not differ from the reciprocal of the specified nominal frame rate by more than 5

percent of the nominal period.

3.2 Short Term Stability. During a measured period (P), containing 1000-channel intervals,

the time between the start of any two successive channel intervals (synchronization intervalsexcepted) should not differ from the average channel interval established by the formula

1000

PT avg

by more than 1 percent of the average interval.

3.3 Multiple and Submultiple Sampling Rates. Data multiplexing at sampling rates which are

multiples and submultiples of the frame rate is permissible.

K-3

7/31/2019 IRIG_106_2009



K-4

3.3.1 Submultiple Frame Synchronization. The beginning of the longest submultiple frameinterval is identified by the transmission of a synchronization pattern. All other submultiple

frames have a fixed and known relationship to the identified submultiple frames.

3.3.1.1 Fifty Percent Duty Cycle (RZ). The synchronization pattern has a full-scale amplitude

pulse in two successive occurrences of channel intervals allocated to data channels of theidentified submultiple frame. The first such pulse has a duration equal to the channel interval;the second pulse immediately follows the first pulse and has a duration nominally one-half the

channel interval. There is no return to zero between the two pulses.

3.3.1.2 One Hundred Percent Duty Cycle (NRZ). The synchronization pattern has informationin five successive occurrences of a channel interval allocated to data channels of the identified

submultiple frame. The amplitude of the data channels assigned for synchronization is shown in

the following subparagraphs.

3.3.1.2.1 First occurrence - zero amplitude.

3.3.1.2.2 Second, third, and fourth occurrences - full-scale amplitude.

3.3.1.2.3 Fifth occurrence - not more than 50 percent of full-scale amplitude.

3.3.2 Maximum Submultiple Frame Length. The interval of any submultiple frame, including

the time devoted to synchronizing information, shall not exceed 128 times the interval of the

frame in which it occupies a recurring position.

4.0 Frequency Modulation

The frequency deviation of an FM carrier or subcarrier, which represents the maximumand minimum amplitude of a PAM waveform, should be equal and opposite with respect to the

assigned carrier or subcarrier frequency. The deviation should be the same for all occurrences of

the same level.

5.0 Premodulation Filtering

A maximally linear phase response, premodulation filter, is recommended to restrict the

radiated spectrum (see Appendix A).

**** END OF APPENDIX K ****

7/31/2019 IRIG_106_2009


Telemetry Standard RCC Document 106-09, Appendix L, April 2009

APPENDIX L

ASYNCHRONOUS RECORDER MULTIPLEXER OUTPUT RE-CONSTRUCTOR

(ARMOR)


1.0 General.............................................................................................................L-1

2.0 Setup Organization ..........................................................................................L-2

LIST OF TABLES

Table L-1. Armor Setup Preamble.....................................................................................L-1

Table L-2. Setup Organization ..........................................................................................L-2

Table L-3. Header Section Format ....................................................................................L-3

Table L-4. Channel Entry Lengths ....................................................................................L-4

Table L-5. Pcm Input Channels.........................................................................................L-6Table L-6. Analog Input And Output Channels ................................................................L-7

Table L-7. Analog Input And Output Channels ................................................................L-8Table L-8. Parallel Input Channels....................................................................................L-9

Table L-9. Parallel Output Channels ...............................................................................L-10

Table L-10. Time Code Input Channels ............................................................................L-12Table L-11. Time Code Output Channels..........................................................................L-13

Table L-12. Voice Input Channel......................................................................................L-14

Table L-13. Voice Output Channels..................................................................................L-15

Table L-14. Bit Sync Input Channels ................................................................................L-16Table L-15. Trailer Section Format...................................................................................L-17

7/31/2019 IRIG_106_2009



ii


7/31/2019 IRIG_106_2009



APPENDIX L

ASYNCHRONOUS RECORDER MULTIPLEXER OUTPUT RE-CONSTRUCTOR

(ARMOR)

1.0

General

This standard defines the recommended multiplexer format for single channel data

recording on small format (1/2 in.) media (Chapter 6, Section 6.7). This format is recognized as

the Asynchronous Recorder Multiplexer Output Re-constructor (ARMOR). This format is

software-reconfigurable for each data acquisition or reproduction. The ARMOR formatconfiguration information is stored in a data structure called a “setup” that contains all the

information necessary to define a particular record or play configuration. This appendix

describes the format and content of the ARMOR setup.

1.1 Setup on Tape. When the ARMOR setup is written to tape, it is preceded by a preamble

with a unique setup sync pattern that allows the identification of the setup. Three duplicate setuprecords, each with its own preamble, are written at the beginning of each recording. The format

of the preamble is defined in Table L-1.

TABLE L-1. ARMOR SETUP PREAMBLE

FIELD LENGTH DESCRIPTION

SETUP SYNC 4 TAPE BLOCKS THE SYNC PATTERN CONSISTS OF TWO

BYTES. THE HIGH BYTE IS 0XE7; THE

LOW BYTE IS 0X3D. THE SYNC PATTERN

IS WRITTEN HIGH BYTE FIRST. FOR THE

DCRSI, A TAPE BLOCK IS A SINGLE SCAN

(4356 BYTES). FOR THE VLDS, A TAPE

BLOCK IS A PRINCIPLE BLOCK (65536

BYTES).

END OF SYNC 3 BYTES THE THREE BYTES IMMEDIATELY

FOLLOWING THE SYNC PATTERN ARE:

0X45, 0X4F, 0X53 (ASCII ‘E’, ‘O’, ‘S’ FOR

“END OF SYNC”).

L-1

7/31/2019 IRIG_106_2009



2.0 Setup Organization

An ARMOR setup is divided into three sections: the header section, the channel section,and the trailer section. The overall organization of a setup is summarized in Table L-2.

TABLE L-2. SETUP ORGANIZATION

CONTENT NUMBER OF BYTES

HEADER SECTION 70

CHANNEL 1 INFORMATION 51 - 61

CHANNEL 2 INFORMATION 51 - 61

“ “ “

“ “ “

TRAILER SECTION 0 - 44 + SAVED SCANLIST SIZE

2.1 Header Section. The header section is the first 70 bytes of a setup. It contains

information about the setup as a whole, including clock parameters, frame parameters, and thenumbers of input and output channels (see Table L-3).

In Tables L-3 through L-12, fields noted with an asterisk (*) require userinput per section 2.5.

L-2

7/31/2019 IRIG_106_2009



TABLE L-3. HEADER SECTION FORMAT

FIELD BYTES FORMAT DESCRIPTION

*SETUP

LENGTH

2 BINARY TOTAL BYTES IN SETUP, INCLUDING THIS FIELD

SOFTWARE

VERSION

12 ASCII VERSION OF THE ARMOR SETUP AND CONTROL

SOFTWARE THAT WROTE THE SETUP

PRE-SCALERS 1 BINARY THE BOTTOM FOUR BITS CONTAIN THE BIT RATE

CLOCK PRE-SCALER; THE TOP FOUR BITS

CONTAIN THE PACER CLOCK PRE-SCALER.

RESERVED 26 N/A N/A

*SETUP KEYS

(BIT 0)

IF BIT 0 (LSB) SET, SETUP CONTAINS SETUP

DESCRIPTION IN TRAILER.

*SETUP KEYS

(BITS 1, 2, & 3)

1 BINARY IF BIT 1 SET, SETUP CONTAINS CHECKSUM IN

TRAILER. IF BIT 2 SET, SETUP IS SCAN-ALIGNED.

IF BIT THREE SET THEN A SCAN LIST IS SAVED.

PACER DIVIDER 2 BINARY PACER DIVIDER VALUE

BIT RATE 4 BINARY AGGREGATE BIT RATE FOR ALL ENABLED

CHANNELS

BRC DIVIDER 2 BINARY BIT RATE CLOCK DIVIDER VALUE

MASTER

OSCILLATOR

4 BINARY FREQUENCY OF THE MASTER OSCILLATOR IN

BITS PER SECOND

BYTES

OVERHEAD

4 BINARY TOTAL SYNC BYTES PLUS FILLER BYTES PER

FRAME.

PACER 4 BINARY FREQUENCY OF THE PACER CLOCK IN CYCLES

PER SECOND

FRAME RATE 4 BINARY NUMBER OF FRAMES PER SECOND

*INPUT COUNT 2 BINARY NUMBER OF INPUT CHANNELS IN SETUP

OUTPUT COUNT 2 BINARY NUMBER OF OUTPUT CHANNELS IN SETUP

L-3

7/31/2019 IRIG_106_2009



2.2 Channel Section. The channel section contains one channel entry for every channel inthe multiplexer chassis configuration, including those channels that are not enabled or recorded.

The content and length of the channel information vary depending on the channel type. The

lengths of the channel entries for each channel type are presented in Table L-4. Tables L-5through L-14 describe the channel entry fields for each module type. Links to the tables are

provided below.

TABLE L-4. CHANNEL ENTRY LENGTHS

TABLE L-5. PCM INPUT CHANNELS

TABLE L-6. ANALOG INPUT AND OUTPUT CHANNELS


TABLE L-8. PARALLEL INPUT CHANNELS

TABLE L-9. PARALLEL OUTPUT CHANNELS

TABLE L-10. TIME CODE INPUT CHANNELSTABLE L-11. TIME CODE OUTPUT CHANNELS

TABLE L-12. VOICE INPUT CHANNEL

TABLE L-13. VOICE OUTPUT CHANNELS

TABLE L-14. BIT SYNC INPUT CHANNELS

L-4

7/31/2019 IRIG_106_2009



TABLE L-4. CHANNEL ENTRY LENGTHS

CHANNEL TYPE BYTES

PCM INPUT AND OUTPUT 51

ANALOG INPUT AND OUTPUT 53

PARALLEL INPUT 53

PARALLEL OUTPUT 56

TIMECODE INPUT AND OUTPUT 61

VOICE INPUT AND OUTPUT 61

BIT SYNC INPUT 61

L-5

7/31/2019 IRIG_106_2009



TABLE L-5. PCM INPUT CHANNELS


*CHANNEL TYPE 2 BINARY 1 = 8 BIT PCM INPUT

8 = 20 MBIT PCM INPUT

MAPPED CHANNEL 2 BINARY INDEX OF THE CHANNEL THIS CHANNEL

IS MAPPED TO. IF THE CHANNEL IS NOT

MAPPED, THE INDEX IS 1.

*ENABLED 1 ASCII IF ENABLED, THE CHANNEL IS RECORDED

(“Y” OR “N”)

ACTUAL RATE 4 BINARY ACTUAL WORD RATE IN WORDS PERSECOND

WORDS PER FRAME 4 BINARY NUMBER OF WORDS PER FRAME

INPUT MODES 1 BINARY IF BIT 0 (LSB) SET, SOURCE B DATA; ELSE

SOURCE A. IF BIT 1 SET, NRZ-L; ELSE BI-

PHASE-L. IF BIT 2 SET, 0 DEGREE CLOCK;

ELSE 90 DEGREE CLOCK.

RESERVED 3 N/A N/A

BITS PER WORD 2 BINARY 16 BITS

BITS PRECEDING 4 BINARY NUMBER OF BITS IN THE FRAME THAT

MUST PRECEDE THIS CHANNEL

*CHANNEL NUMBER 2 BINARY CHANNEL ON MODULE (0-3)

*MODULE ID 1 BINARY MODULE ID = HEX 11

RESERVED 1 N/A N/A

*REQUESTED RATE 4 BINARY REQUESTED BITS PER SECOND (INTEGER)

DESCRIPTION 20 ASCII CHANNEL DESCRIPTION

L-6

7/31/2019 IRIG_106_2009





CHANNEL TYPE 2 BINARY 2 = 8 MBIT PCM OUTPUT

9 = 20 MBIT PCM OUTPUT




ENABLED 1 ASCII IF ENABLED, THE CHANNEL IS

RECORDED (“Y” OR “N”).

ACTUAL RATE 4 BINARY ACTUAL WORD RATE IN WORDS PERSECOND


OUTPUT MODES 1 BINARY IF BIT 0 (LSB) SET, BURST MODE. IF BIT 1

SET, BI-PHASE; ELSE NRZ-L.

RESERVED 3 N/A N/A

BITS PER WORD 2 BINARY NUMBER OF BITS PER WORD

BITS PRECEDING 4 BINARY NUMBER OF BITS IN THE FRAME THATMUST PRECEDE THIS CHANNEL

CHANNEL NUMBER 2 BINARY CHANNEL ON MODULE (0-3)

MODULE ID 1 BINARY MODULE ID = HEX 21

RESERVED 1 N/A N/A

REQUESTED RATE 4 BINARY REQUESTED BITS PER SECOND


L-7

7/31/2019 IRIG_106_2009





*CHANNEL TYPE 2 BINARY 5 = LF ANALOG INPUT

6 = HF ANALOG INPUT

7 = ANALOG OUTPUT




*ENABLED 1 ASCII IF ENABLED, THE CHANNEL IS


ACTUAL RATE 4 BINARY ACTUAL SAMPLE RATE IN SAMPLES PER

SECOND

SAMPLES PER FRAME 4 BINARY NUMBER OR SAMPLES PER FRAME

FILTER NUMBER 1 BINARY 0 = FILTER 1

1 = FILTER 2

2 = FILTER 3

3 = FILTER 4

RESERVED 3 N/A N/A

*BITS PER SAMPLE 2 BINARY NUMBER OF BITS PER SAMPLE (8 OR 12)

RESERVED 4 N/A N/A


*MODULE ID 1 BINARY MODULE ID = 34 HEX (LF) OR 33 HEX (HF)

RESERVED 1 N/A N/A

*REQUESTED RATE 4 BINARY REQUESTED SAMPLES PER SECOND

RESERVED 2 N/A N/A


L-8

7/31/2019 IRIG_106_2009



TABLE L-8. PARALLEL INPUT CHANNELS


*CHANNEL TYPE 2 BINARY 13 = NEW PARALLEL INPUT




*ENABLED 1 ASCII IF ENABLED, THE CHANNEL IS


ACTUAL RATE 4 BINARY ACTUAL WORDS PER SECOND


RESERVED 4 N/A N/A


WORDS PRECEDING 4 BINARY NUMBER OF WORDS IN THE FRAME

THAT MUST PRECEDE THIS CHANNEL


*MODULE ID 1 BINARY MODULE ID = HEX 92

RESERVED 1 N/A N/A

*REQUESTED RATE 4 BINARY REQUESTED WORDS PER SECOND.

INPUT MODE 1 BINARY 0 = FOUR 8-BIT CHANNELS

1 = ONE 16-BIT, TWO 8-BIT (CURRENTLY

UNAVAILABLE)

2 = TWO 16-BIT (CURRENTLY

UNAVAILABLE)

3 = ONE 32-BIT (CURRENTLY

UNAVAILABLE)

4 = ONE 24-BIT, ONE 8-BIT (CURRENTLY

UNAVAILABLE)

RESERVED 1 N/A N/A


L-9

7/31/2019 IRIG_106_2009





CHANNEL TYPE 2 BINARY 14 = NEW PARALLEL OUTPUT




ENABLED 1 ASCII IF ENABLED, THE CHANNEL IS


ACTUAL RATE 4 BINARY ACTUAL WORD RATE IN WORDS PER

SECOND


RESERVED 4 N/A N/A


WORDS PRECEDING 4 BINARY NUMBER OF WORDS IN THE FRAME

THAT MUST PRECEDE THIS CHANNEL


MODULE ID 1 BINARY MODULE ID = HEX A2

RESERVED 1 N/A N/A

REQUESTED RATE 4 BINARY REQUESTED WORDS PER SECOND

OUTPUT MODE 1 BINARY 0 = FOUR 8-BIT CHANNELS

1 = ONE 16-BIT, TWO 8-BIT

2 = TWO 16-BIT CHANNELS

3 = ONE 32-BIT CHANNEL

4 = ONE 24-BIT, ONE 8-BIT

7 = TWO 8-BIT DCRSI MODE

RECONSTRUCT MODE 1 BINARY 0 = DATA IS FROM MODULE OTHER

THAN PARALLEL INPUT.1 = DATA IS FROM PARALLEL INPUT.

VALID ONLY FOR OUTPUT MODE.

DCRSI OUTPUT 1 BINARY 0 = HEADER AND DATA

1 = HEADER ONLY

3 = DATA VALID ONLY FOR OUTPUT

MODE 7.

L-10

7/31/2019 IRIG_106_2009




(Continued)


BURST SELECT 1 BINARY 0 = CONSTANT1 = BURST

HANDSHAKE SELECT 1 BINARY 0 = DISABLE HANDSHAKING

1 = ENABLE HANDSHAKING


L-11

7/31/2019 IRIG_106_2009



TABLE L-10. TIME CODE INPUT CHANNELS


*CHANNEL TYPE 2 BINARY TIME CODE MUST APPEAR AS A GROUPOF 3 CHANNELS, EVEN THOUGH THE

USER INTERFACE ONLY DISPLAYS A

SINGLE CHANNEL. THE RESPECTIVE

TYPES ARE 15, 19, AND 20.




*ENABLED 1 ASCII “Y” OR “N”

ACTUAL RATE 4 BINARY 1

SAMPLES PER FRAME 4 BINARY 1

RESERVED 4 N/A N/A

*BITS PER WORD 2 BINARY 24 FOR CHANNEL TYPE 15

24 FOR CHANNEL TYPE 19


RESERVED 4 N/A N/A

*CHANNEL NUMBER 2 BINARY 0 FOR CHANNEL TYPE 15



*MODULE ID 1 BINARY MODULE ID = HEX B1

RESERVED 1 N/A N/A

*REQUEST SAMPLERATE

4 BINARY 1

*BITS PER SAMPLE 2 BINARY 24 FOR CHANNEL TYPE 15




RESERVED 4 N/A N/A

TCI MODE 1 BINARY 0 = GENERATE TIME1 = USE EXTERNAL IRIG SOURCE

RESERVED 3 N/A N/A

L-12

7/31/2019 IRIG_106_2009



TABLE L-11. TIME CODE OUTPUT CHANNELS


CHANNEL TYPE 2 BINARY TIME CODE MUST APPEAR AS A GROUPOF 3 CHANNELS, EVEN THOUGH THE

USER INTERFACE ONLY DISPLAYS A

SINGLE CHANNEL. THE RESPECTIVE

TYPES ARE 17, 21 AND 22.




ENABLED 1 ASCII “Y” - ENABLED, OR “N” - DISABLED

ACTUAL RATE 4 BINARY 1

SAMPLES PER FRAME 4 BINARY 1

RESERVED 4 N/A N/A

BITS PER WORD 2 BINARY 24 FOR CHANNEL TYPE 17



RESERVED 4 N/A N/A

CHANNEL NUMBER 2 BINARY 0 FOR CHANNEL TYPE 17



MODULE ID 1 BINARY MODULE ID = HEX B1

RESERVED 1 N/A N/A

REQUESTED SAMPLE

RATE

4 BINARY 1

BITS PER SAMPLE 2 BINARY 24 FOR CHANNEL TYPE 17




RESERVED 4 N/A N/A

TCO MODE 1 BINARY 0 - GENERATE TIME

1 - USE TIME FROM RECORDED TAPE

RESERVED 3 N/A N/A

L-13

7/31/2019 IRIG_106_2009



TABLE L-12. VOICE INPUT CHANNEL


*CHANNEL TYPE 2 BINARY 16




*ENABLED 1 ASCII “Y” - ENABLED, OR “N” - DISABLED


SECOND

SAMPLES PER

FRAME

4 BINARY NUMBER OF SAMPLES PER FRAME

RESERVED 4 N/A N/A

*BITS PER WORD 2 BINARY 8

RESERVED 4 N/A N/A

*CHANNEL NUMBER 2 BINARY 3

*MODULE ID 1 BINARY MODULE ID = HEX B1

RESERVED 1 N/A N/A

*REQUESTED

SAMPLE RATE

4 BINARY 2K, 5K, 10K, 20K, 50K, OR 100K

*BITS PER SAMPLE 2 BINARY 8


RESERVED 1 N/A N/A

VOLTAGE GAIN 2 BINARY 0 - GAIN OF 1

1 - GAIN OF 2

2 - GAIN OF 43 - GAIN OF 8

RESERVED 5 N/A N/A

L-14

7/31/2019 IRIG_106_2009



TABLE L-13. VOICE OUTPUT CHANNELS


CHANNEL TYPE 2 BINARY 18



MAPPED, THE INDEX IS 1



SECOND

SAMPLES PERFRAME

4 BINARY NUMBER OF SAMPLES PER FRAME

RESERVED 4 N/A N/A

BITS PER WORD 2 BINARY 8

RESERVED 4 N/A N/A

CHANNEL NUMBER 2 BINARY 3

MODULE ID 1 BINARY MODULE ID = HEX B1

RESERVED 1 N/A N/A

REQUEST SAMPLE

RATE

4 BINARY NUMBER OF SAMPLES PER SECOND

BITS PER SAMPLE 2 BINARY 8


RESERVED 8 N/A N/A

L-15

7/31/2019 IRIG_106_2009



TABLE L-14. BIT SYNC INPUT CHANNELS


CHANNEL TYPE 2 BINARY 23

RESERVED 2 N/A N/A


ACTUAL RATE 4 BINARY ACTUAL WORD RATE IN WORDS PER

SECOND

WORDS PER FRAME 4 BINARY NUMBER OR WORDS PER FRAME

RESERVED 4 N/A N/A

BITS PER WORD 2 BINARY 16

RESERVED 4 N/A N/A


MODULE ID 1 BINARY MODULE ID = HEXADECIMAL 13

RESERVED 1 N/A N/A

REQUESTED RATE 4 BINARY BITS PER SECOND


INSTALLED 1 BINARY 0 = DAUGHTER BOARD NOT INSTALLED

1 = DAUGHTER BOARD INSTALLED

PCM

GEOGRAPHICAL.

ADDRESS

1 BINARY GEOGRAPHICAL ADDRESS OF THE

ASSOCIATED PCM INPUT CHANNEL

SOURCE CLOCK 1 BINARY 0 = SOURCE A

1 = SOURCE B

RESERVED 7 N/A N/A

L-16

7/31/2019 IRIG_106_2009



2.3 Trailer Section. The trailer section contains the setup description and the checksum(see Table L-15). Early versions of the setup do not contain this information. The “Setup

Keys” field in the header indicates the content of the trailer section.

TABLE L-15. TRAILER SECTION FORMAT


SETUP

DESCRIPTION

40 ASCII DESCRIPTION OF THE SETUP

SAVED SCANLIST VARIES BINARY NUMBER OF BYTES DEPENDS ON THE

NUMBER OF CHANNELS BEING

RECORDED.

CHECKSUM 4 BINARY SUM OF ALL SETUP BYTES

2.4 Saved Scan-list Structure. This is an array of enabled input channels that make up thecalculated scan-list. Each element of the array is made up of two fields, an index field and a

count field. The length of the index field is one byte, and the length of the count field is two

bytes.

a. The index field, which is 1-based, is determined by the position of the channel’s

module in the ARMOR system. The first input channel found in the ARMOR systemis assigned an index of one (1), the next input channel is assigned a two (2), and so

on. The search for input modules starts at slot 1. Filler bytes are assigned an index

value of 255.

b. The count field is the number of words/samples per frame that is assigned to that

input channel.

2.5 Creating a Setup Block. Creating a Setup Block involves two steps. In the first step, the

user creates an “input” setup block file as described below in this section. Most of the fields inthe input setup block file are unspecified (filled with zeros). In the second step, the input setup

block file is read by the ARMOR compiler program that produces a new setup block file with all

the unspecified fields initialized to the appropriate values. In other words, a setup block has two

types of fields, user specified and compiler generated. Note that all compiler-generated fieldsmust be provided in the input setup block file and initialized with zeros prior to executing the

ARMOR compiler program.

The rules presented in this section must be explicitly followed to create an ARMOR input

setup block. Values for fields identified in the previous tables with an asterisk preceding the

field name must be provided. In some cases, the values for these required fields are constant andare specified in the tables above. In other cases, the user must provide the desired value. All

L-17

7/31/2019 IRIG_106_2009



fields with names not identified with asterisks must be initialized to binary zero. This includesboth “unused” and “reserved” fields.

Only input channel information entries are required. Output channel information entriesare ignored by the ARMOR compiler program.

2.5.1 Header Section.

Setup Length: Count the total numbers of bytes in the created setup block and put thevalue here.

Setup Keys: Set bit 0 = 1 if the trailer contains a description. Leave other bits = 0.

Input Count: Enter the total number of input channel information entries, including

both enabled and disabled entries.

2.5.2 Channel Section. PCM, low frequency (LF) analog, and parallel input channel information

entries must be included in the setup block in groups of four entries per type. High frequency (HF)analog input channel information entries must be included in the setup block in groups of two

entries per type. Time code/voice input channel information entries must be included in groups of three time code entries and one voice entry. Specifying an ASCII “N” in the enabled field must

disable all unused input channel information entries. For each channel information entry group, thechannel number field of the first entry in the group is zero (0), the second entry is one (1), the third

is two (2), and the fourth is three (3). For the time code/voice group, the time code entry channel

number fields are 0, 1, and 2, respectively, while the voice entry channel number field is 3. HFanalog entry channel number fields are 0 and 1, respectively.

Description fields are not required and are not specified below. However, it is advisable

to include an ASCII description of each channel for future reference.

2.5.2.1 PCM Input Channels

Channel Type: Binary 8

Enabled: ASCII “Y” if enabled, “N” if disabled

Channel Number: Binary 0, 1, 2, or 3 as described in 2.5.2 above

Module ID: Hexadecimal 11

Requested Rate: Binary integer rate in bits per second

L-18

7/31/2019 IRIG_106_2009



2.5.2.2 Analog Input Channels

Channel Type: Binary 5 for LF (up to 1 megasample/sec), 6 for HF (up to

10 megasamples/sec)

Enabled: “Y” if enabled, “N” if disabled

Bits per Sample: 8 or 12

Channel Number: 0, 1, 2, or 3 as described in 2.5.2 above

Module ID: Hexadecimal 34 (LF) or 33 (HF)

Requested Rate: Binary integer 2K, 5K, 10K, 20K, 50K, 100K,

200K, 500K, 1M (LF, HF) 2.5M, 5M, 10M (HF only)

2.5.2.3 Parallel Input Channels.

Channel Type: Decimal 13

Enabled: “Y” if enabled, “N” if disabled

Channel Number: 0, 1, 2, or 3 as described in 2.5.2 above

Module ID: Hexadecimal 92

Requested Rate: Binary integer 8-bit words (bytes) per second

2.5.2.4 Time Code Input Channels.

Channel Type: Decimal 15 (1st

entry), 19 (2nd

entry), 20 (3rd

entry)

Enabled: “Y” if enabled, “N” if disabled, all three entries must be the

sameBits per Word: Decimal 24 (1st entry), 24 (2nd entry), 16 (3rd entry)

Channel Number: 0, 1, or 2 as described in 2.5.2 above

Module ID: Hexadecimal B1

Requested Rate: 1

Bits per Sample: Decimal 24 (1st entry), 24 (2nd entry), 16 (3rd entry)

2.5.2.5 Voice Input Channels.

Channel Type: Decimal 16Enabled: “Y” if enabled, “N” if disabled

Bits per Word: 8

Channel Number: 3 as described in 2.5.2 above

Requested Rate: Integer 2K, 5K, 10K, 50K, 100K

Bits per Sample: 8

L-19

7/31/2019 IRIG_106_2009



L-20

2.5.3 Trailer Section. The trailer section of the input setup block is not required. The usermay include an ASCII text setup description in the trailer section by setting the setup keys bit 0 =

1 in the header section (see paragraph 2.5.1 above) and adding the setup description field only in

the trailer section.

2.5.4 ARMOR Compiler Program. Operational instructions for the ARMOR compilerprogram are provided in the readme.txt file provided with the compiler (see Chapter 6,paragraph 6.7.3.1).

**** END OF APPENDIX L ****

7/31/2019 IRIG_106_2009


Telemetry Standard RCC Document 106-09, Appendix M, April 2009

APPENDIX M

PROPERTIES OF THE DIFFERENTIAL ENCODER SPECIFIED IN

IRIG STANDARD 106 FOR OQPSK MODULATIONS


1.0 Introduction.....................................................................................................M-1

2.0 The Need For Differential Encoding..............................................................M-1

3.0 A Simple Solution To The Carrier Phase Ambiguity Problem ......................M-44.0 Immunity to Carrier Phase Rotation...............................................................M-7

5.0 Initial Values...................................................................................................M-9

6.0 Error Propagation..........................................................................................M-107.0 Recursive Processing and Code Memory.....................................................M-11

8.0 Frequency Impulse Sequence Mapping for SOQPSK..................................M-12

9.0 Summary.......................................................................................................M-14

LIST OF FIGURES

Figure M-1. Transmission System......................................................................................M-2

Figure M-2. OFFSET QPSK 106 Symbol to Phase Mapping Convention.........................M-3

Figure M-3. Detection ambiguity........................................................................................M-3Figure M-4. QPSK State Timing ........................................................................................M-4

Figure M-5. OFFSET QPSK State Timing.........................................................................M-5

Figure M-6. Basic SOQPSK Transmitter..........................................................................M-13

Figure M-7. OQPSK Transmitter (with precoder). ...........................................................M-13

LIST OF TABLES

Table M-1. Constellation Axis Rotations ..........................................................................M-4

Table M-2. Response To Run of 1s ...................................................................................M-7

Table M-3. SOQPSK Pre-Coding Table For IRIG-106 Compatibility ...........................M-13

ANNEX 1 TO APPENDIX M: SYSTEM LEVEL SOFTWARE REFERENCE

IMPLEMENTATION OF DIFFERENTIAL ENCODER DEFINED IN IRIGSTANDARD 106 FOR FQPSK AND SOQPSK MODULATIONS

1.0 Introduction...................................................................................................M-152.0 Matlab Workspace Operation.......................................................................M-153.0 Script For Modules .......................................................................................M-16

REFERENCES

7/31/2019 IRIG_106_2009



ii


7/31/2019 IRIG_106_2009



APPENDIX M

PROPERTIES OF THE DIFFERENTIAL ENCODER SPECIFIED IN IRIG STANDARD

106 FOR OQPSK MODULATIONS

1.0

Introduction

This appendix summarizes a study of the differential encoder originally adopted by theU.S. Department of Defense (DoD) Advanced Range Telemetry (ARTM) project and the Range

Commanders Council (RCC) and incorporated into the Interrange Instrumentation Group

(IRIG) Standard 106 (IRIG-106) (reference [M-1]) for Feher’s Quadrature Phase Shift Keying

(FQPSK-B)1

modulation. The study, performed by Mr. Robert Jefferis of the TYBRINCorporation, was prompted by inquiries from industry representatives who were concerned that

this particular differential code was not associated with commercial telecommunication standards

and the fact that manufacturers had experienced confusion over correct implementation. Thestudy results shown in this appendix prove the code to be robust, reliable, and applicable to

Shaped Offset QPSK (SOQPSK-TG) 2 as well as FQPSK-B and FQPSK-JR.3

This appendix is organized along the following structure. Paragraph 2 describes the need

for differential encoding. Paragraph 3 explains the IRIG-106 differential code for OQPSKs.

Paragraph 4 demonstrates differential code’s invariance with respect to constellation rotation.Paragraph 5 shows the differential decoder to be self-synchronizing. Paragraph 6 reviews the

differential decoder’s error propagation characteristics. Paragraph 7 analyzes a recursive

implementation of the differential code and Paragraph 8 describes use of this code with

frequency modulator based SOQPSK transmitters. A description of the implementation of theentire coding and decoding process can be seen at Annex 1 to this appendix.

2.0 The Need For Differential Encoding

Practical carrier recovery techniques like Costas loops and squaring loops exhibit atroublesome M-fold carrier phase ambiguity. A description of ambiguity problems and how to

overcome them are shown in the following paragraphs of this appendix.

Shown below at Figure M-1 is a simplified quadriphase transmission system that is oneof the methods recommended for transparent point-to-point transport of a serial binary data

stream. Transparent means that only revenue bearing data is transmitted. There is no in-line

channel coding nor is special bit pattern insertion allowed. The assumption is made for a non-return-to-zero-level (NRZ-L) data stream containing the bit sequence b(nTb) transmitted at rate

r b = 1/ T b bits per second. For QPSK and OQPSK modulations, the bit stream is divided into

subsets “e” containing even numbered bits and “o” containing odd numbered bits. Thetransmission rate associated with the split symbol streams is rs = rb /2 symbols per second.

1 FQPSK-B is a proprietary variation of “Offset” QPSK (OQPSK), Digcom Inc., El Macero, California.2 See Chapter 2 and Appendix-A for details on SOQPSK-TG (formerly SOQPSK-A*).3 FQPSK-JR is an FQPSK variant developed by Mr. Robert Jefferis, TYBRIN Corporation,and Mr. Rich Formeister,

RF Networks, Inc.

M-1

7/31/2019 IRIG_106_2009


7/31/2019 IRIG_106_2009



Figure M-2. OFFSET QPSK 106 Symbol to Phase Mapping Convention.

The symbol detectors have insufficient information to determine which phase offset

exists. They always interpret demodulator output with the assumption that =0. The resultingconstellation axis rotations and their impact on demodulator output are shown at Figure M-3 and

Table M-1. The 180-degree rotation is symmetric. The Axis (subcarrier) assignment isunchanged but the sense (polarity) of both axes gets reversed. The 90-degree and 270-degree

rotations are asymmetric. Axis assignment is swapped and one axis polarity is reversed in each

case.

Figure M-3. Detection ambiguity.

M-3

7/31/2019 IRIG_106_2009



TABLE M-1. CONSTELLATION AXIS ROTATIONS

Rotation + I ’ +Q’

0 I Q

/2 -Q I

-I -Q

3 /2 Q -I

3.0 A Simple Solution To The Carrier Phase Ambiguity Problem

Differential encoding has been used to work around the carrier ambiguity for many years.

For phase modulations, source data is coded such that phase differences rather than absolutephase coordinates become the information-bearing attribute of the signal. The QPSK and

OQPSK modulations use I and Q independently, with each channel transporting one symbol

stream. Starting with the first binary digit, bit 0, even numbered bits form the sequence {ek } andodd numbered bits form the sequence {ok+1} where the counting index is changed from the bit

index n to the symbol pair index

1)-(M ,...}6,4,2,0{ 2 k nk

Figure M-4 illustrates how QPSK modulators process bits in pairs (dibits), mapping and

asserting time coincident symbol phase coordinates ( I k ,Qk )6. Phase state changes commence and

end on symbol interval timing boundaries, each state taking on one of four possible values atdetector decision instants. However, the case of interest is shown in Figure M-5.

Figure M-4. QPSK State Timing

6 Rectangular I and Q baseband waveforms are used only for illustration.

M-4

7/31/2019 IRIG_106_2009



Figure M-5. OFFSET QPSK State Timing.

The Q channel half-symbol delay causes OQPSK phase trajectories to evolve on a half-symbol (bit) rate basis. For the particular cases of FQPSK and SOQPSK-TG, carrier phase

either remains unchanged or changes by /4 or /2 radians over the pending bit interval.

The OQPSK inter-channel delay might at first seem a difficult complication because it

creates additional ambiguity; in other words, the receiver must resolve relative inter-channeldelay. However, as shown below, this is not a problem.

The differential encoding rule adopted in IRIG-106 for OQPSK appears in reference

[M-4] and is therein attributed to Clewer in reference [M-5] and Weber in reference [M-6]. Bitby bit, the code symbol sets { E k } and {Ok+1) are formed with the Boolean expressions:

Two bits are coded for each value of k in a two-step process. First, the even symbol E k is

coded with current bit ek . Then the next bit, ok+1 becomes current and the odd symbol Ok+1 iscomputed. In each code set the exclusive-or operator is applied to the state defining variables

just like BPSK differential encoding. Unlike BPSK however, the current source bit and the most

recent code symbol from the other channel determine adjacent phase transitions. Also note the

asymmetry of these equations introduced by the inverted code symbol in equation (M-2a). Itssignificance will become evident in the next section.

2)-(M

2b)-(M

2a)-(M

1)1(

1

k k k

k k k

E oO

Oe E

The code symbol sets { E } and {O} are applied to the I and Q channels of the OQPSK

modulator. The initial assignment of { E } to either I or Q can be made arbitrarily. However,

with this code definition, once the choice is made at the modulator, decoding will fail if channel

assignment conventions change anywhere during the transmission or decoding processes. Thus,the assignment convention must extend to the physical modulator and demodulator. IRIG -06

assigns I to the physical I subcarrier (also known as the “real” or “cosine” subcarrier) and Q is

M-5

7/31/2019 IRIG_106_2009



applied to the physical Q subcarrier (also known as the “imaginary” or “sine” subcarrier). Inorder to stress this assignment convention, IRIG-106 expresses equation (M-2) explicitly in

terms of the I and Q channel variables:

3)-(M ...6,4,2,0

3b)-(M

3a)-(M

)1()1(

)1(

k

I oQ

Qe I

k k k

k k k

Decoding is straightforward. When =0, I’=I, and Q’=Q, inspection of the following

truth tables reveals simple decoding instructions:

:equationdecoding

011

110

101

000

011

101

110

000

3b)-(MEquation3a)-(MEquation

)1()1()1(

k k k k k k o I QeQ I

4)-(M ...,6,4,2,0

4b)-(M '''

4a)-(M '''

11

1

k

I Qo

Q I e

k k k

k k k

The equations at (M-3) may not convey an intuitive sense of the shift from absolute phasestates to phase differences. Extending (M-3a) backwards in time by substituting (M-3b) into

(M-3a) results in:

5)-(M 1221 k k k k k k k oe I I oe I

Similarly, for the next bit interval the results are:

6)-(M 11111 k k k k k k k eoQQeoQ

This recursive form clearly shows that on a bit by bit basis, the current and most recent

bits control phase trajectory motion, not absolute phase. Note that (M-5) and (M-6) do not define

the sign of a phase change. Predictable decoder output requires that two additional conventionsbe established and maintained. Boolean logic polarity conventions used throughout the system

must be consistent. IRIG-106 assumes positive true logic. Finally, sign conventions and channel

M-6

7/31/2019 IRIG_106_2009



assignment used within the transmitter (baseband signal generator and modulator) and thereceiver (demodulator) must be constrained to produce a consistent code symbol to phase

mapping convention. The IRIG-106 convention is shown in Figure M-2. For example, if {b}

were to consist entirely of logic one values, i.e., a run of 1s, the differential encoding process andmapping convention will produce the phase trajectory shown in Table M-2.

TABLE M-2. RESPONSE TO RUN OF 1S

n b(n) k Ik Qk-1 Qk+1 Phase (deg) Phase

0 1 0 0 0* 225*

1 1 1 135 - /2

2 1 1 1 1 45 - /2

3 1 0 315 - /2

4 1 2 0 0 225 - /2

5 1 1 135 - /2

* denotes assumed initial conditions

The trajectory spins clockwise, and the phase is retarded by 90 degrees during each bit

interval.7 Obviously, any single (unbalanced) sign change and any change to the mapping

convention will alter the trajectory.

4.0 Immunity to Carrier Phase Rotation

The equations at (M-3) and (M-4) are invariant with respect to cardinal constellation

rotation as shown in the following:

Proof:

The =0 case is decoded correctly by definition according to equations (M-5) and (M-6).

At Table M- 1, when = there is no axis swap but the decoder is presented with

11''

k k

k k

QQ I I

7 FQPSK-B, FQPSK -JR and SOQPSK-TG modulations respond to a run of 1s with an S(t) that is ideally, a pure

tone at frequency f c-rb /4 Hz. This is referred as “lower sideband” mode. Similarly, a run of zeroes will produce a

constant anti-clockwise trajectory spin and a tone at f c+rb /4 Hz (“upper sideband” mode).

M-7

7/31/2019 IRIG_106_2009



Decoding will progress as follows:

Step 1. Even channel; apply equation (M-4a);

'' 111 k k k k k k k k eQ I Q I Q I' e

Step 2. Odd channel; apply equation (M-4b);

11111 ''' k k k k k k k k o I Q I Q I Qo

Thus, symmetric rotation is transparent to the code. When = /2 the decoder sees

k k

k k

I Q

Q I

1

1

'

'

Decoding takes place in the same sequence:

Step 1, even channel, apply equation (M-4a);

'' 1111 k k k k k k k k oQ I I QQ I' e

Step 2, odd channel, apply equation (M-4b);

''' 111 k k k k k k eQ I I Qo

In this case the bit sequence is recovered correctly and the code definition coupled withconsistent sign conventions automatically compensates for the asymmetric rotation by reversingthe application order of (4a) and (4b). It is noted that the output indexes are shifted back in time

one bit period. Asymmetric rotation causes a one-bit delay in the decoding process. Finally, the

same result is seen when =3 /2:

k k

k k

I Q

Q I

1

1

'

'

Step 1. Even channel; apply equation (M-4a);

1111'' k k k k k k k k oQ I I QQ I' e

Step 2. Odd channel; apply equation (M-4b);

k k k k k k k k eQ I Q I I Qo 1111 '''

M-8

7/31/2019 IRIG_106_2009



In all cases the decoder correctly reproduces the original bit sequence. Decoding isinstantaneous for symmetric rotations but it is delayed by one bit in 2 out of 4 possible

asymmetric rotation startup scenarios.

The need for consistent function assignment now becomes clear. Application of (4b) to a

code symbol formed with (3a) produces the complement of the original bit. Likewise,application of (4a) to a symbol coded with (3b) inverts the result.

At this point, the OQPSK inter-channel delay ambiguity mentioned in section 2 has not

been resolved. The roles of I’ and Q’ reverse with asymmetric rotations and there is no way to

determine when this occurs. However, as long as the code symbol time sequence is preserved atthe decoder and the roles of I’ and Q’ do not get reversed in terms of the application of (6a) and

(6b), inter-channel delay is transparent to the code with respect to reconstruction of the original

data sequence.8

5.0 Initial Values

Equations at (M-3) and (M-4) do not impose any implementation constraints on initial

values when encoding or decoding starts. To confirm this it is assumed that hardware power-up(or initial data presentation) may cause encoding to commence with either channel. It is further

assumed that no provisions for specific initial values in encoder and decoder state memories have

been made. If coding starts with I (see equation M-3a) , the first code symbol will be computed:

100 Qe I

where . denotes an unknown initial value and double vertical bars denote computed values

influenced by initial values. Encoding equations M-3a and M-3b will progress as follows:

011 I oQ

122 Qe I

As can be seen, the initial values do establish the absolute sense of code symbols for theduration of transmission. But, on both ends of the process, two of three terms in every equation

are affected consistently by the initial value, which by symmetry has no effect on the outcome of

exclusive-or operations. Obviously, identical results occur if the encoder starts with Q.Independent of starting channel and initial value then, the first and all subsequent adjacent code

symbol pairs contain valid state change information.

8 If for some reason the system application requires that one can determine whether a specific symbol was originally

transmitted via I or Q, then this code is not appropriate.

M-9

7/31/2019 IRIG_106_2009



Initial decoder values can produce errors. Again starting with I , and using equations(M-4a) and (4b), decoding will progress as follows:

100 '' Q I e

011 ''' I Qo

It is seen that on the second cycle the initial value of the decoder has been flushed out.

At most, one bit will be decoded in error. Similarly, if decoding starts with Q, output will

progress:

011 ''' I Qo

122 ''' Q I e

Again, only the first decoded bit may be incorrect. The conclusion, then, is that initialvalues can produce at most, one decoded bit error. However, there is another source of startup

errors that is seen as an initial value problem. Section 4.0 showed that odd phase rotations ( /2and 3 /2) cause a single bit delay in the decoder. Examining this further, the first symbol index

value will be k = 0. If the decoder starts with equation (M-4a), the first decoded bit will be:

110100 oQ I Q I e

If the decoder starts with equation (M-4b) the first result will be:

010011 eQ I I Qo

The first case produces the aforementioned delay. The decoder emits an extra bit. The

second bit emitted is actually the first bit of the sequence reconstruction and is still subject to thesingle initial value error probability of startup processing. The latter case does not produce a

delay; it only presents the possibility of a first bit decoding error.

6.0 Error Propagation

Differential encoding incurs a bit error penalty because received code symbols influencemore than one decoded bit. First consider a single symbol detection error in current symbol E ’

which is labeled k . The following sequence of decoding steps shows how the error propagates.Since the E channel was chosen as current, decoding starts with equation (M-4a). The single

detection error creates two sequential decoding errors. By symmetry we can state that the same

result occurs if a single error occurs in O’.

correct'''

error'

error'

2122

111

1

k k k k

k k k k

k k k k

bQ E b

bQb

bQb

M-10

7/31/2019 IRIG_106_2009



Next is the case of two symbol detection errors occurring consecutively on E’ and O’,

i.e., detectors emit error symbols E’k =k and O’k+1=k+1. Starting again with equation (M-4a)

yields:

correct'''

error''

correct''

error'

)3()2()3()3(

)2()1()2()2(

)1()1()1()1(

)1(

k k k k

k k k k

k k k k k k

k k k k

b E Ob

b E b

b E Ob

bQb

Two consecutive symbol errors produce two decoding errors but the errors are not

adjacent. The conclusion from this is that symbol detection errors influence no more than twodecoding cycles, i.e., the maximum error multiplication factor is 2.

7.0 Recursive Processing and Code Memory

Most systems reconstruct the original bit rate clock and {b} by merging {e’} and {o’}.

For a variety of reasons, designers might be tempted to multiplex { I’} and {Q’} into a bit ratecode symbol sequence { Bn} prior to decoding. However, the same considerations that foster

desire for post-multiplex decoding are likely to be accompanied by loss of transmitted codesymbol order, i.e., loss of knowledge whether a given code symbol came from I or Q. The

question arises as to whether {Bn} alone contains enough information for unique decoding. The

answer is “no”, and the proof is shown below.

Proof:

An alluring decoding function can be derived by inspection of equations (M-5) and (M-6).

Equation (M-5) can be rearranged as follows:

7)-(M 21 k k k k I oe I

Similarly, from equation (M-6) we can write

8)-(M 111 k k k k QeoQ

Here are two instances of a seemingly identical recursive relationship, i.e., the current codesymbol is the difference between the current bit, the previous bit, and the inverse of the mostrecent code symbol from the current channel. We can consolidate these equations by convertingto post-multiplex bit rate indexing, i.e.,

9)-(M )2()1( nnnn Bbb B

from which we can immediately write the decoding function

10)-(M '''' )2()1( nnnn B Bbb

M-11

7/31/2019 IRIG_106_2009



On the surface it seems that equation (M-10) will work.9

However, these relationsinvolve two differences, rather than one, and therefore introduce superfluous initial condition

dependence. For brevity, only the pitfalls of (M-10) are examined herein, assuming that a non-

recursive encoder is used. From startup, decoding will progress as follows:

0212

1101

2010

''''

''''

''''

B Bbb

B Bbb

B Bbb

1323 '''' B Bbb .

.

.

As seen, absolute polarity of the first and all subsequent decoded bits is determined by

three (3) initial values. Absent appropriate a priori side information for selecting initial values,the post-multiplex decoder offers a 50-50 chance of decoding with correct polarity. The code

sequence defined by equations at (M-3) has a two-symbol memory. Additional symbols do notprovide new information regarding the trajectory history. Another way to view this problem is tonote that this recursive decoder does not guarantee preservation of symbol order, which is a

prerequisite to reliable decoding.

8.0 Frequency Impulse Sequence Mapping for SOQPSK

The SOQPSKs first described by Hill and Geohegan in references [M-7] and [M-8] aredefined as special cases of continuous phase modulation (CPM). Since 1998, at least two

manufacturers have exploited the fact that modern digital waveform synthesis techniques enable

direct implementation of the CPM equations with virtually ideal frequency modulators and filter

impulse responses. A generic model of these implementations is at Figure M-6. The I and Qchannels, per se, do not exist in this transmitter. At the beginning of each bit interval, impulses

from the bit to impulse alphabet mapper direct the impulse filter/frequency modulator to advance

the carrier phase by 90, retard it by or 90, or leave the phase unchanged. This is accomplished

with a ternary alphabet of frequency impulses having normalized amplitudes of {-1,0,1}.10

Obviously, this structure cannot be mapped directly into the constellation convention of a

quadriphase implementation because there is no way to control absolute phase. The equations at

(M-3) can be applied to this non-quadrature architecture via pre-coding. A general treatmentSOQPSK pre-coding is contained in reference [M-9]. It is easily shown that the pre-coding truth

table given in Table M-3 applied to the model in Figure M-7 will yield a phase trajectory history

identical to one generated by the quadriphase counterpart of Figure M-2 using the equations at

(M-3). However, one more constraint is necessary to establish compatibility with the IRIG-106quadriphase convention. Table M-3 assumes the stipulation that positive sign impulse values

will cause the modulator to increase carrier frequency.

9 The interested reader is left to confirm that equation (10) is indeed rotation invariant.10 The so-called ternary alphabet is actually 2 binary alphabets {-1,0} and {0,1}, the appropriate one chosen on a bit-

by-bit basis according to certain state transition rules.

M-12

7/31/2019 IRIG_106_2009



Figure M-6. Basic SOQPSK Transmitter.

TABLE M-3. SOQPSK PRE-CODING TABLE FOR IRIG-106 COMPATIBILITY

MAP K FROM I K MAP K+1 FROM QK+1

I k Qk-1 I k-2 k Qk+1 I k Qk-1 k+1

-1 X* -1 0 0 -1 X* -1 0 0

+1 X* +1 0 0 +1 X* +1 0 0

-1 -1 +1 - /2 -1 -1 -1 +1 + /2 +1

-1 +1 +1 + /2 +1 -1 +1 +1 - /2 -1

+1 -1 -1 + /2 +1 +1 -1 -1 - /2 -1

+1 +1 -1 - /2 -1 +1 +1 -1 + /2 +1

* Note: Does not matter if “X” is a +1 or a -1

Figure M-7. OQPSK Transmitter (with precoder).

I k

Qk+1 PRE-

CODER

FREQUENCY

IMPULSE

FILTER

FREQUENCY

MODULATOR

106

ENCODER

{b(nT b)}

Impulse Series

{b(nT b)}

S(t)

M-13

7/31/2019 IRIG_106_2009



9.0 Summary11

This investigation confirmed that the differential encoder defined in the equations at(M-3) is entirely satisfactory for SOQPSK, FQPSK-JR and FQPSK-B systems where

conventional coherent demodulation and single symbol detection is used. In addition, a method

of extending this code to SOQPSK is presented without proof.

Specifically, the following has been shown:

a. When accompanied by consistent sign conventions, a consistent symbol to phasemapping rule, and preservation of symbol order, the OQPSK differential code defined

in (M-3) and the decoding rule defined in (M-4) is rotation invariant and

unambiguously reconstructs the original data bit sequence.

b. Decoding is instantaneous.

c. Equations (M-3) and (M-4) do not require attention to initial values.

d. At most, two consecutive output bits will be in error after carrier and symbol

synchronization is acquired.

e. The recursive relations in (M-9) and (M-10) are ambiguous and therefore unreliable.

f. The code exhibits a detection error multiplication factor of at most two.

11 There is no doubt in the author’s mind that well trodden ground has been traveled in this investigation. These

characteristics were probably validated in reference [5] and by RF Networks Inc. before it incorporated the

encoder in its model 5450F FQPSK demodulator product. Unfortunately, none of this work is in the public

domain.

M-14

7/31/2019 IRIG_106_2009



ANNEX 1 TO APPENDIX M

SYSTEM LEVEL SOFTWARE REFERENCE IMPLEMENTATION OF

DIFFERENTIAL ENCODER DEFINED IN IRIG STANDARD 106 FOR FQPSK AND

SOQPSK MODULATIONS

1.0 Introduction

The Matlab®™ program listings below provide a Matlab function “Desysdemo” and an

execution control script “runDEdemo”. In the context of differential encoding, the function

provides a complete system simulation including a differential encoder, an ideal vectormodulator, channel phase rotation, demodulation, the functional equivalent of an ideal single

symbol sample and hold detector, and a decoder. The user can create sample data vectors or use

the example data provided. In addition, by manipulating the initial value vectors, all possible

initial value and demodulator phase rotation combinations of the quadriphase implementationmodel can be explored.

By setting the variable “style” to zero, the function will also emulate the pre-codedfrequency modulator architecture required for SOQPSKs. However, the initial value of

transmitter carrier phase is hard coded at 45 degrees. This was done to avoid proliferation of

initial value options and is thought to be an insignificant omission because it does not affectgenerality of the phase rotation options.

It is assumed that the user is familiar with Matlab workspace operation. The program

relies only on basic Matlab license libraries. There are no special toolboxes or blocksets arerequired.

2.0 Matlab Workspace Operation

The user should place the script (shown below in paragraph 3.0 of this Annex) in thedirectory of choice and make that directory current in the workspace. In order to execute the

“canned” example, the user needs to create the variable “example” in the workspace and set itsvalue to 1.

M-15

7/31/2019 IRIG_106_2009



Executing the script “runDEdemo” should produce the following output:

results =

Model: Quadriphase Vector Modulator

Demodulator Phase Rotation = 0 degrees

Initial States: Encoder

Memory

Encoder

Channel

Decoder

Memory

Decoder

Channel

(0,0) 0 (0,0) 0

Input

Bit

TX

Phase

RX

Phase

Output

Bit

Decoding

Error

1 225 225 1 0

1 135 135 1 0

1 45 45 1 00 45 45 0 0

0 135 135 0 0

1 135 135 1 0

0 135 135 0 01 135 135 1 0

1 45 45 1 0

1 315 315 1 00 315 315 0 0

0 45 45 0 0

1 45 45 1 0

0 45 45 0 0

The first column of the results shown above is a replica of the input data vector. The

second column shows the initial value dependent evolution of transmitted phase. The thirdcolumn shows the effect of any non-zero phase rotation chosen. The fourth column shows the

decoded output bit stream and the fifth column flags decoding errors with values of 1. Certain

combinations of phase rotation and initial values will produce values of 9 in the fourth and fifthcolumns; results of this nature are associated with cases that delay the output decoding process

by one bit.

Variable definitions and implied instructions for manipulating the runtime options can be

obtained by using the normal Matlab help command for these specific programs.

3.0 Script For Modules

Electronic copies of these programs have been provided to the DoD Range CommandersCouncil, Telemetry Group. The script for the modules discussed above is shown on the

following pages.

M-16

7/31/2019 IRIG_106_2009



% Control Script ‘runDEdemo’, for running system demonstration% of differential encoder and phase mapping convention

% defined in RCC standard IRIG-106 for FQPSK-B modulation.

% This version extends demonstration options to the pre-coder% required for implementing SOQPSK with frequency modulators.

%% Each example run requires input variables in the Matlab workspace:%

% "example" - a flag to run with user supplied data vector or run

% the example data set that consists of two repetitions of a

% a 7-bit pseudo random sequence(0=user, 1=example)% "data" - optional user supplied binary bit sequence (arbitrary length)

% "rotation_choice" - pointer to demodulator phase rotation options:

% 1=0, 2=pi/2, 3= pi, 4=3*pi/2% "initTX" - vector of binary encoder startup values:

% initTX(1)= 1st of two encoder code symbol memory values(binary, arbitrary)

% initTX(2)= 2nd encoder code symbol memory value(binary, arbitrary)% initTX(3)= starting channel for encoder(binary, 0=I, 1=Q)

% "initRX" - vector of binary decoding startup values

% initRX(1)= 1st of two decoder state memory values(binary, arbitrary)

% initRX(2)= 2nd decoder state memory value(binary, arbitrary)% initRX(3)= starting channel for decoder(binary, 0=I, 1=Q)

% "style" - 1=quadriphase transmitter architecture (FQPSK)

% 0=frequency modulator transmitter architecture (SOQPSK)% The example values are:

% data=[1 1 1 0 0 1 0 1 1 1 0 0 1 0]% rotation_choice=1

% initTX=[0 0 0]

% initRX=[0 0 0]% style=1

% R.P.Jefferis, TYBRIN Corp., JULY, 2002% SOQPSK model added 14JUL03

% This version has been tested with Matlab versions:5.2,6.1

% *** Sample Input Setup ***if example

data=[1 1 1 0 0 1 0 1 1 1 0 0 1 0];

rotation_choice=1;initTX=[0 0 0];

initRX=[0 0 0];

style=1;end

% *** Run the Reference Implementation ***

M-17

7/31/2019 IRIG_106_2009



[test,delay]=DEsysdemo(data,rotation_choice,initTX,initRX,style);

% *** Prepare Screen Output ***

ROTATION=[0 90 180 270];

if styleresults=sprintf('Model: Quadriphase Vector Modulator\n')else

results=sprintf('Model: Frequency modulator (SOQPSK) model\n')

end

results=[results sprintf('Demodulator Phase Rotation = %3.0f degrees\n',ROTATION(rotation_choice))];

results=[results sprintf('Initial States: Encoder Encoder Decoder Decoder\n')];

results=[results sprintf(' Memory Channel Memory Channel\n')];results=[results sprintf('------------------------------------------------\n')];

results=[results sprintf(' (%d,%d) %d (%d,%d) %d\n\n',...

initTX(1:2),initTX(3),initRX(1:2),initRX(3))];results=[results sprintf(' Input TX RX Output Decoding\n')];

results=[results sprintf(' Bit Phase Phase Bit Error\n')];

results=[results sprintf('-------------------------------------\n')];

for n=1:length(data)results=[results sprintf(' %d %3.0f %3.0f %d %d\n',...

test(n,:))];

endresults

% ___________END OF CONTROL SCRIPT_____________

function [result,delay]= DEsysdemo(inbits,rotation_choice,initTX,initRX,style)% Reference simulation for Range Commanders Council standard IRIG 106-2000

% FQPSK-B differential encoding and phase mapping convention.

%% Input arguments: see "help" for "runDEdemo" script

% Output arguments:

% "result" - Mx5 matrix,M=number of input bits,columns contain:

% (:,1)input bit,(:,2)TX phase,(:,3)RX phase,(:,4)output bit,(:,5)status% "delay" - overall encode/decode process delay in bits

% "TX" prefixes refer to transmitter/encoder variables, "RX" prefixes% refer to receiver/decoder variables

% Robert P. Jefferis, TYBRIN Corp., July,2002.

% SOQPSK model added 14JUL03% This version has been tested with Matlab versions: 5.2,6.1

numbits=length(inbits)

% *******************

M-18

7/31/2019 IRIG_106_2009



% * Transmitter *% *******************

% *** differential encoder (also SOQPSK pre-coder)****

% encoder memory initial values:% [(last I ch. code symbol) (last Q ch. code symbol)]TXlastSYM=initTX(1:2);

% point encoder to either I or Q starting channel(0=I)

TXpoint=initTX(3);

for n=1:numbitsswitch TXpoint

case 0

%TXlastSYM% compute "current" I channel code symbol

TXnewISYM=xor(inbits(n),~TXlastSYM(2));

TXcodeSYM(n,:)=[TXnewISYM TXlastSYM(2)]; % new phase coordinates(I,Q)TXlastSYM(1)=TXnewISYM; % update encoder memory state

TXpoint = ~TXpoint; % point to Q channel eq. for next bit

case 1

% compute "current" Q channel code symbolTXnewQSYM=xor(inbits(n),TXlastSYM(1));

TXcodeSYM(n,:)=[TXlastSYM(1) TXnewQSYM]; % new phase coordinates(I,Q)

TXlastSYM(2)=TXnewQSYM;% update encoder memory stateTXpoint= ~TXpoint; % point to I channel eq. for next bit

otherwisedisp('Invalid Specification of Encoder starting channel');

end

end

% *** modulate ***

switch style

case 1 % ** Quadriphase vector modulator **

% RCC IRIG 106 FQPSK-B phase mapping convention: (I,Q)for n=1:numbits

index=floor(2*TXcodeSYM(n,1)+TXcodeSYM(n,2));

switch indexcase 3 % [1 1]

TXphase(n)=45; % TX phase angle, degrees

case 1 % [0 1]TXphase(n)=135;

case 0 % [0 0]

TXphase(n)=225;

case 2 % [1 0]

M-19

7/31/2019 IRIG_106_2009



TXphase(n)=315;otherwise, disp('map error')

end

endcase 0 % ** Frequency modulator w/pre-coder **

% * pre-coder *% map code symbol sequence to frequency impulse series, alpha(n)

alpha=zeros(1,numbits);

TXpoint=initTX(3); % in this mode, points to start index

for n=3:numbitsif TXpoint % Q(k+1) map

if TXcodeSYM(n,2)==TXcodeSYM(n-2,2)

elseif xor(TXcodeSYM(n,2),TXcodeSYM(n-1,1))alpha(n)=-1;

else

alpha(n)=1;end

else % I(k) map

if TXcodeSYM(n,1)==TXcodeSYM(n-2,1)

elseif xor(TXcodeSYM(n,1),TXcodeSYM(n-1,2))alpha(n)=1;

else

alpha(n)=-1;end

endTXpoint=~TXpoint; % switch to complement function for next bit

end

% convert alpha to phase trajectory

lastTXphase=45; % initial phase of S(t)

for n=1:numbitsTXphase(n)=mod(lastTXphase+alpha(n)*90,360);

lastTXphase=TXphase(n);

end

otherwiseend

% ************% * Receiver *

% ************

% *** Demodulator Phase Rotation ***

ROTATE=[0 pi/2 pi 3*pi/2];

rotate=ROTATE(rotation_choice);

for n=1:numbits

M-20

7/31/2019 IRIG_106_2009



switch rotatecase 0

RXphase(n)=TXphase(n);

case pi/2RXphase(n)=mod(TXphase(n)+90,360);

case piRXphase(n)=mod(TXphase(n)+180,360);case 3*pi/2

RXphase(n)=mod(TXphase(n)+270,360);

otherwise

endend

% *** detector ***for n=1:numbits

switch RXphase(n)

case 45RXcodeSYM(n,:)=[1 1];

case 135

RXcodeSYM(n,:)=[0 1];

case 225RXcodeSYM(n,:)=[0 0];

case 315

RXcodeSYM(n,:)=[1 0];otherwise

endend

% *** decode and reconstruct data bit sequence ***

% decoder memory initial values:

% [(last decoded I channel bit) (last decoded Q channel bit)]RXlastSYM=initRX(1:2);

% point decoder channel to either I or Q starting channel (0=I)

RXpoint=initRX(3);

for n=1:numbitsswitch RXpoint

case 0

% compute "current" decoded I channel bitRXbits(n)=xor(RXcodeSYM(n,1),~RXlastSYM(2));

RXlastSYM=RXcodeSYM(n,:); % update decoder state

RXpoint = ~RXpoint; % point to Q channel eq. for next bitcase 1

% compute "current" decoded Q channel bit

RXbits(n)=xor(RXcodeSYM(n,2),RXlastSYM(1));

RXlastSYM=RXcodeSYM(n,:); % update decoder state

M-21

7/31/2019 IRIG_106_2009



RXpoint= ~RXpoint; % point to I channel eq. for next bit

otherwise

endend

% ____________ END OF TX and RX Processing ______________

% *******************

% * Assemble Output *

% *******************

% identify delay incurred in overall process

offset=xcorr(inbits,RXbits);offset(1:numbits-1)=[];

[offset,delay]=max(offset(1:min(length(offset),10)));

delay=delay-1;

% adjust RX output bit vector to compensate for delay,

% inserting values of 9 at beginning of vector to represent

% artifact bits associated with asymmetric rotation casescheckbits=inbits;

if delay

newfront=ones(1,delay)*9;checkbits=[newfront inbits];

checkbits(end-delay+1:end)=[];RXbits(1:delay)=9;

end

% identify decoding errors in reconstructed bit streamxmsn_error=checkbits~=RXbits;

xmsn_error(1:delay)=9;

% assemble output matrixresult(:,1)=inbits';

result(:,2)=TXphase';

result(:,3)=RXphase';

result(:,4)=RXbits';result(:,5)=xmsn_error';

% _____END OF FUNCTION DEsysdemo__________

M-22

7/31/2019 IRIG_106_2009



M-23

REFERENCES

[1] Telemetry Standards , IRIG STANDARD 106, Secretariat, Range Commanders Council,White Sands Missile Range, Mew Mexico.

[2] Proakis, J.G., Digital Communications

, 5

th

Edition, McGraw-Hill Inc., New York, 1989.

[3] Cacciamani, E.R and Wolejsza Jr., C.J, “Phase-Ambiguity Resolution in a Four-Phase PSK

Communications System”, IEEE Transactions on Communications, Vol. COM-19, No.6,

December 1971.

[4] Feher, K., Digital Communications: Satellite/Earth Station Engineering, Prentice-Hall Inc.,

New Jersey, 1983,pp. 168-170.

H[5] Cited from bibliography of reference 4 for completeness only. Not available: Clewer, R.

“Report on the Status of Development of the High Speed Digital Satellite modem”, RML-009-79-24, Spar Aerospace Limited, St. Anne de Bellevue, P.Q., Canada, November 1979.

,

[6] Weber, W.J. III, “Differential Encoding for Multiple Amplitude and Phase Shift Keying

Systems”, IEEE Transactions on Communications, Vol. COM-26, No. 3, March 1978.

[7] Hill T., “An Enhanced, Constant Envelope, Interoperable Shaped Offset QPSK(SOQPSK)

Waveform for Improved Spectral Efficiency”, Proceedings of the International TelemeteringConference, San Diego, California, October 2000.

[8] Geoghegan, M., “Implementation and Performance Results for Trellis Detection of SOQPSK”, Proceedings of the International Telemetering Conference, Las Vegas, Nevada,

October 2001.

[9] Simon, M.K., “Multiple-Bit Differential Detection of Offset Quadriphase Modulations”, IPN

Progress Report 42-151, November 15, 2002, Jet Propulsion Laboratory, Pasadena, California.

**** END OF APPENDIX M ****

7/31/2019 IRIG_106_2009


Telemetry Standard RCC Document 106-09, Appendix N, April 2009

APPENDIX N

TELEMETRY TRANSMITTER COMMAND AND CONTROL PROTOCOL

TABLE OF CONTENTS


1.0 Introduction..................................................................................................... N-1

2.0 Command Line Interface ................................................................................ N-13.0 Initialization.................................................................................................... N-2

4.0 Basic Command Set........................................................................................ N-2

5.0 Extended Command Set.................................................................................. N-76.0 Transmitter Communication Example.......................................................... N-13

7.0 Non-standard Commands ............................................................................. N-14

8.0 Physical Layer(s) .......................................................................................... N-14

LIST OF TABLES

Table N-1. Basic Command Set........................................................................................ N-2Table N-2. Extended Command Set.................................................................................. N-7

CHANGES TO THIS EDITION OF APPENDIX N

Updates to this Appendix are in blue font. The blue font indicateseither a completely new item or an update to a previously existing

item.

7/31/2019 IRIG_106_2009


Telemetry Standard RCC Document 106-09, Appendix N, May 2009

ii


7/31/2019 IRIG_106_2009



APPENDIX N

TELEMETRY TRANSMITTER COMMAND AND CONTROL PROTOCOL

1.0 Introduction

This Appendix provides standards for commands, queries, and status information whencommunicating with telemetry transmitters configured with communication ports. The

commands are divided into two categories of “command sets” as follows:

a. Basic. The basic command set contains the minimum (required) commands for

transmitter control, query, and status.b. Extended. The extended command set contains optional commands that may or may

not be implemented and may be shown as references.

2.0 Command Line Interface

2.1 User Command Line Interface. This interface is the default upon “power up” of thetransmitter. Each command or query is ended by a carriage return <CR>. Information returned

from the transmitter will be followed by a carriage return <CR> and the “>” will be displayed to

indicate the transmitter is ready to receive commands or queries.

With regard to this standard, it is assumed that a carriage return <CR> isfollowed by a line feed. The transmitter will return the “OK” mnemonic

for each command that is accepted. The transmitter will return “ERR” for

a command or query that was interpreted as an error. Verification that a

query was either accepted or found to be in error will be the response to the

query. All commands are case insensitive. The transmitter will operate inhalf duplex mode and will echo typed characters to the command terminal.

2.1.1 Options. In addition to the required user command line interface items, the following listcontains options that may or may not be implemented.

a. Backspacing to correct typed errors.b. A character input to recall the last command line. The “^” character followed by a

<CR> is recommended.

2.2 Optional Programming Interface. If the transmitter is not commanded or queried though

a terminal program (human interface), there may be an option to operate in half duplex mode so

that concatenated commands can be sent directly to the transmitter (bulk transmitter set-up). If this option is used, the transmitter will only return a single accepted “OK” response if the entire

string was interpreted and accepted. When concatenating commands, the semicolon “;” is used

as the delimiter for each command. If this optional programming interface is implemented, the

transmitter will identify the semicolon delimiter, recognize the character string as a bulk command, and recognize the start of a new command after each delimiter.

N-1

7/31/2019 IRIG_106_2009



3.0 Initialization

Upon successful communication initialization, the transmitter will provide the controllingterminal with (as a minimum) the manufacturer’s name, model number, serial number, and

supported IRIG-106 (RCC-106) release number. Other information (such as information on

firmware and temperature) deemed appropriate by the manufacture is allowed. This informationwill be displayed only upon a successful power up and communication initialization of thetransmitter. Should an unsuccessful power up occur, based upon criteria of the transmitter

manufacturer, the transmitter shall return “ERR” and allow only the RE(RES) command to reset

the transmitter (see Table N-1 and paragraph 4.2.10).

Upon successful communication, after a power up, a communication connection, a

command, or a query, the transmitter will send a carriage return followed by a “>” to signify thetransmitter is ready to accept commands and queries.

4.0 Basic Command Set

4.1 Basic Command Set Summary. The basic command fields use a minimum two

characters with the optional capability of using a maximum of four characters. If possible, thelonger four character field should be used to add intuitiveness to the basic command set. The

commands in the basic command set are shown in Table N-1.

TABLE N-1. BASIC COMMAND SET

Command Function

FR(FREQ) Sets or queries the carrier frequency.

MO(MOD) Sets or queries the modulation mode.DE Sets or queries the setting of differential encoding (ON or OFF).

RA(RAND) Sets or queries the setting of data randomization (ON or OFF).

RF Sets or queries the RF output (ON or OFF).

QA(QALL) Queries the status of all basic commands.

VE(VERS) Queries, at a minimum, the manufacturer’s name, model number, and serial

number of the transmitter.

SV(SAVE) Saves the current set-up of the transmitter to on-board nonvolatile RAM.

RL(RCLL) Retrieves a transmitter set-up from on-board nonvolatile RAM.

RE(RES) Resets the transmitter to a known configuration, restarts the internal power-up sequence.

N-2

7/31/2019 IRIG_106_2009



4.2 Commands: Basic Command Set.

4.2.1 Carrier Frequency. Carrier frequency is set or queried with the “FR(FREQ)” mnemonic

as described below.

a.

Set Frequency. Use “FR(FREQ) XXXX.X <CR>” where XXXX.X is thecommanded frequency in MHz in 0.5 MHz steps. If the command is accepted, an“OK <CR>” is issued as a response.

In the event of an incorrect commanded carrier frequency (for example the

commanded frequency is out of the tuning range of the transmitter), the transmitterwill default to the currently set carrier frequency before the command was issued. The

transmitter will then return “ERR FR(FREQ) XXXX.X <CR>” where XXXX.X is

the prior frequency set in the transmitter.

b. Query Frequency. “FR(FREQ) <CR>” queries the currently set carrier frequency and

returns “FR(FREQ) XXXX.X <CR>” where XXXX.X is the current set frequencyin MHz.

4.2.2 Modulation Mode. Modulation mode is set or queried with the “MO(MOD)” mnemonic.

a. Set Modulation Mode. Use “MO(MOD) X <CR>” where X corresponds to the

modulation mode. If the command is accepted, an “OK <CR>” is issued as a

response.

Command Modulation Type

MO(MOD) 0 PCM/FM

MO(MOD) 1 SOQPSK-TG MO(MOD) 2 ARTM-CPM

MO(MOD) 6 Modulation off (carrier only)

In the event of an incorrect commanded modulation mode, the transmitter will

default to the previous modulation mode and return “ERR MO(MOD) X <CR>” toindicate the error and the current modulation mode. The “MO(MOD) 6” command

turns off the modulation for carrier only mode. Modulation will return upon a new

commanded modulation mode. If the transmitter is in single mode, only single modecommands are valid and the above error response will be sent should an invalid

modulation mode command be sent. The same logic apples when the transmitter is in

dual mode.

b. Query Modulation Mode. “MO(MOD) <CR>” queries the currently set modulation

mode and returns “MO(MOD) X <CR>” where the integer X is represented in the

above table.

N-3

7/31/2019 IRIG_106_2009



4.2.3 Differential Encoding. Differential encoding is set or queried with the “DE” mnemonic.For additional information, the reader is referred to Chapter 2 (paragraph 4.3.1.1) and

Appendix M.

a. Set Differential Encoding. Use “DE X <CR>” where X corresponds to a 1 or 0. If

the command is accepted, an “OK <CR>” is issued as a response.

Command Differential Encoding

DE 1 On

DE 0 Off

In the event of an incorrect differential encoding command, the transmitter will

return “ERR DE X<CR>” to indicate the error and return the current differentialencoding setting.

b. Query Differential Encoding. “DE <CR>” queries the currently set differential

encoding status and returns “DE X <CR>” where integer X is represented in theabove table.

c. Default. When switching modulation modes the differential encoding shall be

switched appropriately. For example when switching from SOQPSK-TG to

PCM/FM, the differential encoding will be set to off, DE 0.

d. Manual Control. For the PCM/FM and ARTM-CPM modulation modes differential

encoding will always be disabled (off). However, the user can be given manual

control of differential encoding when using SOQPSK-TG modulation.

4.2.4 Data Randomization. Data randomization is set or queried with the “RA(RAND)”mnemonic. For additional information, see Chapter 2, paragraph 2.4.3.4, and Appendix D,Figure D-2.

a. Set Data Randomization. Use “RA(RAND) X <CR>” where X corresponds to a 1 or0. If the command is accepted, an “OK <CR>” is issued as a response.

Command Randomization

RA(RAND) 1 On

RA(RAND) 0 Off

In the event of an incorrect data randomization command, the transmitter willdefault to its current setting and return “ERR RA(RAND) X <CR>” to indicate the

error and the currently set state.

b. Query Randomization Mode. “RA(RAND) <CR>” queries the currently set

randomization and returns “RA(RAND) X <CR>” where integer X is represented inthe above table.

N-4

7/31/2019 IRIG_106_2009



4.2.5 RF Output. RF output is set or queried with the “RF” mnemonic.

a. Set RF Output. Use “RF X <CR>” where X corresponds to a 1 or 0. If the command

is accepted, an “OK <CR>” is issued as a response.

Command RF OutputRF 1 On

RF 0 Off

In the event of an incorrect RF output command, the transmitter will maintain its

current state and return “ERR RF X <CR>” to indicate the error and return the current

RF output setting for the transmitter.

b. Query RF Output. “RF <CR>” queries the currently set RF output and returns

“RF X <CR>” where X corresponds to the numbers in the above table.

4.2.6 Query all. The “query all” command is executed with the “QA(QALL)” mnemonic.

a. Query Transmitter Configuration. The command “QA(QALL) <CR>” requests thecurrent setting of all basic commands. The transmitter response will contain, as a

minimum, the following, in this order:

(1) Carrier Frequency. [FR(FREQ) XXXX.X]<CR>

(2) Modulation Mode. [MO(MOD) X] <CR> (3) Differential Encoding setting. [DE X] <CR>

(4) Randomization setting. [RA(RAND) X] <CR>

(5) RF Output setting. [RF X] <CR> OK<CR>

>

b. Status of Other Commands. If other commands are implemented in the transmitter

beyond the basic set, a complete status should be given for each implemented

command.

4.2.7 Version. The “version” command is executed with the “VE(VERS) <CR>” mnemonic.

a. Query Transmitter Version. “VE(VERS) <CR>” requests the current version of thetransmitter. The response will contain (at a minimum) the following information

about the transmitter and in this order:

(1) Manufacturer Name(2) Model Number

(3) Serial Number

(4) IRIG 106, Appendix N Release supported

b. Formatting and Delimiting the Fields. It is left up to the transmitter manufacturer toformat and delimit the above fields and, if chosen, add additional information to the

response.

N-5

7/31/2019 IRIG_106_2009



4.2.8 Save. The “save” command is executed with the “SV(SAVE)” mnemonic.

For “Save Transmitter Set-Up”, “SV(SAVE) X<CR>” saves the current settings of thetransmitter to register “X” in nonvolatile memory within the transmitter. If only one location is

available, the value of “X” is 0 (zero). There is no limit to the number of storage registers withinthe transmitter.

The command “SV(SAVE) <CR> will save to the default location 0 (zero).

In the event of an unsuccessful save command, the transmitter will return ERRSV(SAVE) X<CR> to indicate the error and no save function will be performed.

4.2.8.1 Operational Fail Safe. In order to avoid the situation of fielding a flight test item that hasbeen inadvertently programmed to use internal clock and data sources the transmitter will always

save the clock and data source as external.

4.2.9 Recall. The recall command is executed with the RL(RCLL) mnemonic.

For “Recall Transmitter Set-up”, “RL(RCLL) X<CR>” retrieves and restores the

transmitter set-up from register “X” in nonvolatile memory within the transmitter. Values of “X” start at 0 (zero). The 0 (zero) register location should be used exclusively for the default set-

up. The default set-up is the memory location that is loaded during power-up.

The command “RL(RCLL) <CR> will recall from the default location 0 (zero).

In the event of an unsuccessful recall command, the transmitter will return ERR

RL(RCLL) X<CR> to indicate the error and no recall function will be performed.

4.2.9.1 Operational Fail Safe. During a recall operation the transmitter will always set the clock

and data sources to external. (See section 4.2.8.1.).

N-6

7/31/2019 IRIG_106_2009



4.2.10 Reset. The transmitter can be reset with the “RE(RES)” mnemonic.

a. Reset Transmitter. “RE(RES) <CR>” resets the transmitter by reinitializing thetransmitter. The transmitter will use the following basic settings as a base

configuration.

Transmitter Setting Command Result

Carrier frequency [FR(FREQ)] Lowest valid frequency within the tuning range

Modulation mode [MO(MOD)] MO(MOD) 0, PCM/FM

Differential encoding [DE X] DE 0, Differential encoding off

Randomization [RA(RAND) X] RA(RAND) 0, Randomization off

RF output [RF X] RF 0, RF output off

b. Example Command use. The Reset Transmitter command would be used if

communication to the transmitter could not be established, if commands were not

being recognized, or if some other unknown transmitter state was experienced.

5.0 Extended Command Set

5.1 Extended Command Set Summary. The extended command set includes commands and

queries not in the basic commands set. Although the extended set does not include all possiblecommands, its use provides a standard way of implementing known features of transmitters.

This standard will be updated at appropriate intervals should new capabilities arise. Commands

in the extended command set are shown in Table M-2.

TABLE N-2. EXTENDED COMMAND SET

Command Function

DP(DPOL) Sets or queries data polarity (NORM or INV).

DS(DSRC) Sets or queries the data source (INT or EXT).

ID(IDP) Sets or queries the internal data pattern (one of five possible settings).

CS(CLKS) Sets or queries the clock source (INT or EXT).

IC(ICR) Sets or queries the internal clock rate.

FC(FEC) Sets or queries forward error correction (ON or OFF).

FC(FEC) YYYY Set specific forward error correction (ON or OFF).RP(RPWR) Sets or queries the output RF power (HI or LO).

TE(TEMP) Queries the internal temperature (in Celsius).

DV(DVS) Deviation sensitivity for PCM/FM mode.

SP(SLP) Low power consumption mode, sleep mode.

VP() Variable RF power command.

N-7

7/31/2019 IRIG_106_2009



5.2 Commands: Extended Command Set.

5.2.1 Data Polarity. Data polarity is set or queried with the “DP(DPOL)” mnemonic.

a. Set Data Polarity. Use “DP(DPOL) X <CR>” where X corresponds to a 1 or 0.

Actual data polarity, when referenced to the input clock, does not need to be known,this command either inverts the incoming data or does not. If the command isaccepted, an “OK <CR>” is issued as a response.

Command Polarity

DP(DPOL) 0 Normal

DP(DPOL) 1 Inverted

In the event of an incorrect data polarity command, the transmitter will maintain

its current setting and return “ERR DP(DPOL) X <CR>” to indicate the error and

return the current data polarity setting for the transmitter.

b. Query Data Polarity. “DP(DPOL) <CR>” queries the current data polarity and

returns “DP(DPOL) X <CR>” where integer X is represented in the above table.

5.2.2 Data Source. Data source is set or queried with the “DS(DSRC)” mnemonic.

a. Set Data Source. Use “DS(DSRC) X <CR>” where X corresponds to a 1 or 0. If the

command is accepted, an “OK <CR>” is issued as a response.

Command Source

DS(DSRC) 0 External

DS(DSRC) 1 Internal

In the event of an incorrect data source command, the transmitter will return

“ERR DS(DSRC) X <CR>” to indicate the error and return the currently set datasource state.

b. Query Data Source. “DS(DSRC) <CR>” queries the currently set data source andreturns “DS(DSRC) X <CR>” where integer X is represented in the above table.

c. Saving Data Source. See section 4.2.8.1 regarding saving the data source setting.

N-8

7/31/2019 IRIG_106_2009



5.2.3 Internal Data Pattern. The internal data pattern is set or queried with the “ID(IDP)”mnemonic.

a. Set Internal Data Pattern. Use “ID(IDP) X” where X corresponds to the internal datapattern. If the command is accepted, an “OK <CR>” is issued as a response.

b. Example Internal Data Patterns. Example patterns are shown below.

Command Pattern

ID(IDP) 9 29-1 (511 bits)

ID(IDP) 11 211-1 (2047 bits)

ID(IDP) 15 215-1 (32767 bits)

ID(IDP) 20 220-1 (1048575 bits)

ID(IDP) 23 223-1 (8388607 bits)

ID(IDP) 0 0x00 Fixed repeating

ID(IDP) A 0xAA Fixed repeating

ID(IDP) F 0xFF Fixed repeatingID(IDP) XXXX 0xXXXX Fixed repeating

Selection of which patterns to implement is left up to the manufacturer. If an

error occurs, the transmitter will return “ERR ID(IDP) X <CR>” to indicate the errorand return the current data source setting for the transmitter.

c. Query Internal Data Pattern. “ID(IDP) <CR>” queries the currently set internal data

pattern and returns “ID(IDP) X <CR>” where integer X is represented in the abovetable.

d. Example Command Use. This feature can be used for system characterization andtroubleshooting. A known bit pattern can be used to test and characterize telemetry

systems end-to-end or isolate baseband signal problems to the transmitter.

5.2.4 Clock Source. The clock source is set or queried with the “CS(CLKS)” mnemonic.

a. Set Clock Source. Use “CS(CLKS) X <CR>” where X corresponds to a 1 or 0. If the

command is accepted, an “OK <CR>” is issued as a response.

Command Source

CS(CLKS) 0 External

CS(CLKS) 1 Internal

In the event of an incorrect command, the transmitter will return “ERR

CS(CLKS) X <CR>” to indicate the error and the current clock source setting for the

transmitter.

b. Query Clock Source. “CS(CLKS) <CR>” queries the currently set clock source and

returns “CS(CLKS) X <CR>” where integer X is represented in the above table.

N-9

7/31/2019 IRIG_106_2009



c. Example Command Use. Internal data can be clocked either with an external or

internal clock. This command allows the user to clock the known data with an

existing external clock or select the internal clock for more flexibility.

d.

Saving Clock Source. See section 4.2.8.1 regarding saving the clock source setting.

5.2.5 Internal Clock Rate. The internal clock rate is set or queried with the “IC(ICR)”

mnemonic.

a. Set Internal Clock Rate. Use “IC(ICR) XX.XXX <CR>” where XX.XXXcorresponds to the clock frequency in MHz. Actual range for the clock frequency is

left to the manufacturer but should correspond to the specified useable input clock

frequency range. Resolution should be +/-1 kHz. Accuracy for the internal clock isleft to the manufacturer but should correspond to internal values for the transmitter.

If the command is accepted, an “OK <CR>” is issued as a response.

In the event of an incorrect command, the transmitter will identify the error,

default to its current state, and return “ERR IC(ICR) XX.XXX <CR>” where

“XX.XXX” indicates indicate the current clock source for the transmitter.

b. Query Internal Clock Rate. “IC(ICR) <CR>” queries the currently set internal clock

rate and returns “IC(ICR) XX.XXX” where XX.XXX is the current set internal clock

rate in MHz.

5.2.6 Forward Error Correction. Forward error correction is set or queried with the “FC(FEC)”mnemonic. If a type of forward error correction is implemented in the transmitter, this command

will enable or disable or query the current setting.

a. Set Forward Error Correction. Use “FC(FEC) X <CR>” where X corresponds

to a 1 or 0. If the command is accepted, an “OK <CR>” is issued as a response.

Command Source

FC(FEC) 0 Disable

FC(FEC) 1 Enable

In the event of an incorrect Forward Error Correction command, the transmitter

will return “ERR FC(FEC) X <CR>” to indicate the error and return the current

forward error correction setting for the transmitter.

b. Query Forward Error Correction Setting. “FC(FEC) <CR>” queries whether or not

FEC is set. The current setting is returned with “FC(FEC) X <CR>” where integer Xis represented in the above table.

N-10

7/31/2019 IRIG_106_2009



5.2.7 Multiple Forward Error Correction Codes. In the event that more than one version of FEC is implemented in the transmitter, a second mnemonic “FC(FEC) YYYY” will be added,

where YYYY refers to the type of FEC implemented.

a. Set Specific Forward Error Correction. Use “FEC YYYY X <CR>” where X

corresponds to 0 through 9 for 10 different types, if required, of that specific forwarderror correction. If the command is accepted, an “OK <CR>” is issued as a response.

b. Examples of FEC codes. The following table is provided for reference only.

Command Type

TPC Turbo Product Code

RS Reed-Solomon Code

LDPC Low Density Parity Check Code

Error reporting and querying will be done in the same fashion as paragraph 5.2.6.

To turn off multiple forward error correction, the “FC(FEC) 0 <CR>” will be issued.

5.2.8 RF Power (Hi/Low). High output power or low output power is set or queried with the

“RP(RPWR)” mnemonic. Low output power is determined to be the lower of two output power

settings.

a. Set RF Output Power. Use “RP(RPWR) X <CR>” where X corresponds to a 1 or a 0.

If the command is accepted, an “OK <CR>” is issued as a response.

Command Output RF Power Level

RP(RPWR) 0 Low

RP(RPWR) 1 High

b. Query RF Output Power Level. “RP(RPWR) <CR>” queries the currently set outputRF power level and returns “RP(RPWR) X <CR>” where integer X is represented in

the above table.

In the event of an incorrect RF Power command, the transmitter will return

“ERR RP(RPWR) X <CR>” to indicate the error and return the current RF Power

setting for the transmitter.

c. Example use. The low setting could be used for lab testing or ground checks when

transmitter and receive antennas are co-located. The high power setting is for normal,over-the-air telemetry transmission.

N-11

7/31/2019 IRIG_106_2009



5.2.9 Internal Temperature. Internal temperature is only a query with the “TE(TEMP)”mnemonic.

Using the Query Internal Temperature “TE(TEMP)” will query the current internaltemperature of the transmitter and returns “TE(TEMP) XXX” where XXX is the current internal

Celsius temperature of the transmitter.

5.2.10 Deviation Sensitivity. The sensitivity to an analog input can be set or queried with the

“DV(DVS)” mnemonic.

a. Set Deviation Sensitivity. Use “DV(DVS) X.XX <CR>” where X.XX corresponds tothe deviation sensitivity in MHz/V. Range of the sensitivity adjustment is left up to

the transmitter manufacturer. If the command is accepted, an “OK <CR>” is issued

as a response.

PCM/FM mode must be selected first in order for this command to be valid. If

this is not done prior to the command and/or an incorrect value would constitute anincorrect deviation sensitivity command. In the event of an incorrect command, the

transmitter will return “ERR DV(DVS) X.XX <CR>” to indicate the error and the

current deviation sensitivity setting for the transmitter.

b. Query Deviation Sensitivity. “DV(DVS) <CR>” queries the deviation sensitivity and

returns “DV(DVS) X.XX <CR>” where X.XX corresponds to the deviation

sensitivity in MHz/V.

5.2.11 Low Power Consumption, Sleep Mode. The transmitter can be placed into a mode of low input power consumption with the “SP(SLP)” mnemonic.

a. Set Low Power Mode. Use SP(SLP) X where X corresponds to a 1 or 0 as shown inthe following table. If the command is accepted, an “OK <CR>” is issued as a

response.

Command Source

SP(SLP) 0 Full Operation Mode

SP(SLP) 1 Sleep Mode

Sleep mode powers down all nonessential circuitry within the transmitter to

reduce input power consumption. Note, in order to return from “sleep” mode, the

transmitter must monitor and recognize the SP(SLP) 0 command. In the event of anincorrect command, the transmitter will return “ERR SP(SLP) X <CR>” to indicate

the error and the current power mode setting for the transmitter.

c. Query Power Mode. “SP(SLP) <CR>” queries the power mode setting and returns

“SP(SLP) X <CR>” where integer X is represented in the above table.

N-12

7/31/2019 IRIG_106_2009



5.2.12 Variable Power Mode. The transmitter can support user selectable output power levelsusing the VP XX<CR> mnemonic.

a. Set Variable Power Level. Use VP XX<CR> or VP X<CR> to set a range of RF outputpower levels available in discrete predefined steps. If the command is accepted, an

“OK<CR>” is issued as a response. In the event of an incorrect command, thetransmitter will return “ERR VP XX<CR>” to indicate the error and the current variablepower level for the transmitter.

b. Query Variable Power Level. “VP<CR>” queries the power mode setting and returns

“VP XX<CR>” where integer XX is represented in the table below.

c. Look Up Table. The actual value of output power that corresponds to “XX” is undefined.

Each manufacturer will provide an equation or lookup table that defines the output poweras a function of “XX”.

Command RF Power LevelVPP XX Full Power (equivalent to RP 1)

VP (XX – 1) Less then full power

VPP 1 (or VPP 01) More then low power

VPP 0 (or VPP 00) Low Power (equivalent to RP 0)

6.0 Transmitter Communication Example

A typical terminal window is shown below for clarity. Transmitter communication

initialization is assumed.

>FR 1435.5

>OK

>FR

>FR 1435.5

>MO 0

>OK

>DE 1

>ERR DE 0

>MO 7

>ERR MOD 0

>RGDW

>ERR

>TE

>TE 085>QA

>FR 1435.5

>MO 0

>DE 0

>RA 1

>RF 1

>

N-13

7/31/2019 IRIG_106_2009



7.0 Non-standard Commands

This paragraph is reserved for transmitter commands that fall outside of the

commands and command structure discussed above. Additions to this

section will be made as non-standard commands are derived and found

applicable to this standard.

8.0 Physical Layer(s)

The above command sets are independent of the physical layer over which the commands

are transferred. The command set should be implemented in such a way that it can be translatedover any physical layer interfacing with the transmitter.

8.1 Serial Interface. Should a three-wire serial interface be chosen, it should be implementedvia a three wire serial interface compatible with EIA232 (http://www.eia.org/ ). The intent of this

standard is not to force complete EIA-232 compliance; Rather, the intent is to establish a serialcommunication interface with the transmitter so that any terminal program, such as Windows®

HyperTerminal, or Linux Minicom, can be used to communicate with the transmitter. A transmit(Tx) and receive (Rx) line will be supplied with an associated ground return; the choice of

connector pin-out being left up to the manufacturer. The serial interface will operate at one of

the common transfer rates. Typical baud rates are 300, 600, 1200, 2400, 4800, 9600, 19200,38400, 57600, and 115200 baud. The default shall be 9600 baud. Should operation at another

baud rate be desired, a command must be implemented to accommodate this capability. The

command shall have the form BD(BAUD) as described below.

a. Baud Rate. Serial communication baud rate shall be set or queried with the

“BD(BAUD)” mnemonic.

N-14

http://www.eia.org/

http://www.eia.org/

7/31/2019 IRIG_106_2009



N-15

b. Set Baud Rate. Use “BD(BAUD) X <CR>” where X corresponds to a number (0-9)in the following table. If the command is accepted, an “OK” <CR>” is issued as a

response.

Command Rate

BD(BAUD) 0 300

BD(BAUD) 1 600

BD(BAUD) 2 1200

BD(BAUD) 3 2400

BD(BAUD) 4 4800

BD(BAUD) 5 9600

BD(BAUD) 6 19200

BD(BAUD) 7 38400

BD(BAUD) 8 57600

BD(BAUD) 9 115200

c. Query Baud Rate. “BD(BAUD) <CR>” queries the set baud rate of the transmitter

and returns “BD(BAUD) X <CR>” where integer X is represented in the above table.

In the event of an incorrect baud rate command, the transmitter will return “ERR

BD(BAUD) X<CR>” to indicate the error and return the current baud rate setting forthe transmitter.

Communication should be compatible with a terminal set-up consisting of one of

the above baud rates with 8 data bits, 1 stop bit, 1 start bit, and no parity. ASCIIcharacters will be transmitted and received. No hardware or software handshaking

should be implemented and connector pin-out is left to the manufacturer.

**** END OF APPENDIX N ****

7/31/2019 IRIG_106_2009


Telemetry Standard RCC Document 106-09, Appendix O, April 2009

APPENDIX O

FLOATING POINT FORMATS


1.0 Introduction..................................................................................................... O-12.0 IEEE 754 32 Bit Single Precision Floating Point........................................... O-2

3.0 IEEE 754 64 Bit Double Precision Floating Point ......................................... O-2

4.0 MIL STD 1750A 32 Bit Single Precision Floating Point............................... O-25.0 MIL STD 1750A 48 Bit Double Precision Floating Point ............................. O-3

6.0 DEC 32 Bit Single Precision Floating Point................................................... O-3

7.0 DEC 64 Bit Double Precision Floating Point ................................................. O-38.0 DEC 64 Bit “G” Double Precision Floating Point.......................................... O-4

9.0 IBM 32 Bit Single Precision Floating Point ................................................... O-4

10.0 IBM 64 Bit Double Precision Floating Point.................................................. O-4

11.0 TI (Texas Instruments) 32 Bit Single Precision Floating Point...................... O-512.0 TI (Texas Instruments) 40 Bit Extended Precision Floating Point................. O-5

LIST OF TABLES

Table O-1. Floating Point Formats.................................................................................... O-1

CHANGES TO THIS EDITION OF APPENDIX O

Updates to this Appendix are in blue font. The blue font indicates

either a completely new item or an update to a previously existingitem. Paragraph 8.0 is entirely new.

7/31/2019 IRIG_106_2009



ii


7/31/2019 IRIG_106_2009



APPENDIX O

FLOATING POINT FORMATS

1.0 Introduction

Table O-1 provides a summary of floating point formats. Details of each format are

shown on the pages following the table.

TABLE O-1. FLOATING POINT FORMATS

Type Size Radix Sign Exponent Fraction Bias Formula

IEEE_32 32 2 1 8 23 127 (-1S)(1.F)(2(E-127))

IEEE_64 64 2 1 11 52 1023 (-1S)(1.F)(2(E-1023))

1750A_32 32 2 0 8 24 0 (0.F)(2E)

1750A_48 48 2 0 8 40 0 (0.F)(2E)

DEC_32 32 2 1 8 23 128 (-1S)(0.1F)(2

(E-128))

DEC_64 64 2 1 8 55 128 (-1S)(0.1F)(2(E-128))

DEC_64G 64 2 1 11 52 1024 (-1 S)(0.1F)(2(E-1024))

IBM_32 32 16 1 7 24 64 (-1S)(0.F)(16(E-64))

IBM_64 64 16 1 7 56 64 (-1S)(0.F)(16(E-64))

TI_32 32 2 1 8 24 0 ((-2)S

+ (0.F))(2E

)

TI_40 40 2 1 8 32 0 ((-2)S

+ (0.F))(2E)

O-1

7/31/2019 IRIG_106_2009



2.0 IEEE 754 32 Bit Single Precision Floating Point

S Exponent Fraction

1 2 9 10 32

2-1 2-23

Value = (-1S)(1.F)(2

(E-127))

S = sign: 0 = Positive, 1 = Negative

Exponent = power of 2 with bias of 127Fraction = F portion of 23 bit fraction 1.F

0: E = 0, F = 0

3.0 IEEE 754 64 Bit Double Precision Floating Point

S Exponent Fraction

1 2 12 13 64

2-1 2-52

Value = (-1S)(1.F)(2

(E-1023))


Exponent = power of 2 with bias of 1023Fraction = F portion of 52 bit fraction 1.F

0: E = 0, F = 0

4.0 MIL STD 1750A 32 Bit Single Precision Floating Point

S Fraction Exponent1 2 24 25 32

2-1

2-23

Value = (0.F)(2E)

Exponent = 2's complement power of 2

S = sign: 0 = Positive, 1 = NegativeS + Fraction = Normalized, 2's complement F portion of 24 bit fraction 0.F

(Bit 2 MUST be set for positive, clear for negative)

0: F = 0

O-2

7/31/2019 IRIG_106_2009



5.0 MIL STD 1750A 48 Bit Double Precision Floating Point

S Fraction (MSW) Exponent Fraction

1 2 24 25 32 33 48

2-1 2-23 2-24 2-31

Value = (0.F)(2E)



S + Fraction = Normalized, 2's complement F portion of 40 bit fraction 0.F(Bit 2 MUST be set for positive, clear for negative)

0: F = 0

6.0 DEC 32 Bit Single Precision Floating Point

S Exponent Fraction

1 2 9 10 32

2-2

2-24

Value = (-1S)(0.1F)(2

(E-128))


Exponent = power of 2 with bias of 128Fraction = F portion of 23 bit fraction 0.1F

0: S = 0 & F = 0 & E = 0

7.0 DEC 64 Bit Double Precision Floating Point

S Exponent Fraction

1 2 9 10 64

2-2

2-56

Value = (-1S)(0.1F)(2(E-128))

S = sign: 0 = Positive, 1 = NegativeExponent = power of 2 with bias of 128

Fraction = F portion of 55 bit fraction 0.1F

0: S = 0 & F = 0 & E = 0

O-3

7/31/2019 IRIG_106_2009



8.0 DEC 64 Bit “G” Double Precision Floating Point

S Exponent Fraction

1 2 12 13 64

2-2 2-53

Value = (-1 S)(0.1F)(2(E-1024))


Exponent = power of 2 with bias of 1024

Fraction = F portion of 52 bit fraction 0.1F0: S = 0 & F = 0 & E = 0

9.0 IBM 32 Bit Single Precision Floating Point

S Exponent Fraction

1 2 8 9 32

2-1 2-24

Value = (-1S)(0.F)(16

(E-64))


Exponent = power of 16 with bias of 64Fraction = Normalized F portion of 24 bit fraction 0.F

(Bits 9-12 cannot be all zero)

0: F = 0

10.0 IBM 64 Bit Double Precision Floating Point

S Exponent Fraction

1 2 8 9 64

2-1 2-56

Value = (-1S)(0.F)(16(E-64))

S = sign: 0 = Positive, 1 = NegativeExponent = power of 16 with bias of 64

Fraction = Normalized F portion of 56 bit fraction 0.F

(Bits 9-12 cannot be all zero)

0: F = 0

O-4

7/31/2019 IRIG_106_2009



O-5

11.0 TI (Texas Instruments) 32 Bit Single Precision Floating Point

Exponent S Fraction

1 8 9 10 32

2-1

2-23

Value = ((-2)S+(0.F))(2

E)


S = sign: 0 = Positive, 1 = NegativeFraction = 2's complement F portion of 24 bit fraction 1.F

0: E = -128

12.0 TI (Texas Instruments) 40 Bit Extended Precision Floating Point

Exponent S Fraction

1 8 9 10 40

2-1 2-31

Value = ((-2)S+(0.F))(2E)



Fraction = 2's complement F portion of 32 bit fraction 1.F0: E = -128

**** END OF APPENDIX O ****

7/31/2019 IRIG_106_2009


Telemetry Standard RCC Document 106-09, Appendix P, April 2009

APPENDIX P

DERIVED PARAMETER SPECIFICATION


1.0 Derived Parameter Definition.......................................................................... P-12.0 Derived Algorithm Grammar: Components ...................................................P-13.0 Operators..........................................................................................................P-24.0 Numeric Constants...........................................................................................P-45.0 Measurements .................................................................................................. P-56.0 Mathematical Functions...................................................................................P-57.0 Derived Grammar Syntax Overview ............................................................... P-78.0 Grammar Examples ......................................................................................... P-89.0 Telemetry Attributes Transfer Standard (TMATS) Examples ...................... P-1310.0 Glossary of Terms..........................................................................................P-17

LIST OF FIGURES

Figure P-1. Grammar syntax............................................................................................... P-7Figure P-2. Yacc Grammar example. ................................................................................. P-9Figure P-3. Lex Grammar example. ................................................................................. P-11Figure P-4. Example program (main). .............................................................................. P-12

LIST OF TABLES

Table P-1. Arithmetic Operators ....................................................................................... P-2

Table P-2. Bit Manipulation Operators ............................................................................. P-2Table P-3. Relational Operators ........................................................................................ P-3Table P-4. Ternary (If Then Else) Operator ...................................................................... P-3Table P-5. Associativity Operator ..................................................................................... P-3Table P-6. Precedence and Associativity of Operators From Highest to Lowest ............. P-4Table P-7. Numeric Constants (Examples) ....................................................................... P-4Table P-8. Measurements (Examples)...............................................................................P-5Table P-9. Table of Selected Mathematical Functions...................................................... P-6

APPENDIX P IS A NEW APPENDIX(APRIL 2009)

7/31/2019 IRIG_106_2009



ii


7/31/2019 IRIG_106_2009



APPENDIX P

DERIVED PARAMETER SPECIFICATION

1.0 Derived Parameter Definition

Derived parameters are measurements that do not appear in any data stream; instead, theyare calculated from telemetry measurements in a data stream, numeric constants, and/or other derived measurements. In a Telemetry Attributes Transfer Standard (TMATS) file, derivedmeasurements will only have entries in the C group; the other TMATS groups containingmeasurement names that link to C group entries only include telemetry measurements.

Derived parameters are defined using the Algorithm Type (C-d\DPAT) and Algorithm(C-d\DPA) attributes in the Derived Parameter section of the TMATS C group. They can bedefined in one of two methods. The first method to specify the name of an algorithm (“functionstyle”) and the second method is to specify a text string of the algorithm itself (“formula style”).Both of these methods are currently used in telemetry processing systems.

In function style, Algorithm Type is set to “N” and Algorithm contains the name of afunction, which will be one of the mathematical functions or operators as defined in the derivedalgorithm grammar shown in this appendix. The Input Measurand attributes (C-d\DP\N andC-d\DP-n) and Input Constant attributes (C-d\DPC\N and C-d\DPC-n) are used to specify thearguments needed by the named function (measurements and numeric constants, respectively, asdefined in the derived algorithm grammar in this appendix). The Trigger Measurand and Number of Occurrences attributes are used to specify when and how often the derived parameter will be calculated.

In formula style, Algorithm Type is set to “A” and Algorithm contains the actualfunction, given according to the derived algorithm grammar defined in this appendix. The InputMeasurand attributes and Input Constant attributes are not used. The Trigger Measurand and Number of Occurrences attributes are used to specify when and how often the derived parameter will be calculated.

2.0 Derived Algorithm Grammar: Components

Derived algorithm grammar is from the four components listed below. The derivedalgorithm may be any combination of operators, functions, measurements, and numeric constantsstrung together using the guidelines in this document to create complex mathematicalexpressions (see paragraph 6.0.2). Sample syntaxes for the Yet Another Compiler Compiler

(Yacc) grammar and Lexicon (Lex) grammar are provided in paragraph 8.0.

a. Operators. (paragraph 3.0) b. Numeric Constants. (paragraph 4.0)c. Measurements. (paragraph 5.0)d. Mathematical Functions. (paragraph 6.0).

P-1

7/31/2019 IRIG_106_2009



3.0 Operators

Operators are simply mathematical functions that have a special syntax in the grammar.They have operator symbol(s) that have well-defined arguments and return a value as a result.Logical operators are merely functions that return a value of 0 and non-zero for false and truerespectively.

3.1 Arithmetic Operators.

TABLE P-1. ARITHMETIC OPERATORS

Operator Description Example

+ Addition (Sum) A + B

- Subtraction (Difference) A – B

* Multiplication (Product) A * B

/ Division (Quotient) A / B

% Modulus (Remainder) A % B

** Exponentiation A ** B

3.2 Bit Manipulation Operators.

TABLE P-2. BIT MANIPULATION OPERATORS


| Bit-wise OR A | B

& Bit-wise AND A & B^ Bit-wise XOR A ^ B

~ Bit-wise NOT ~A

<< Bit-wise Left Shift A << B

>> Bit-wise Right Shift A >> B

P-2

7/31/2019 IRIG_106_2009



3.3 Relational Operators.

TABLE P-3. RELATIONAL OPERATORS


= = Equal To A = = B

!= Not Equal To A != B

<= Less Than or Equal To A <= B

>= Greater Than or Equal To A >= B

< Less Than A < B

> Greater Than A > B

|| Logical OR A || B

&& Logical AND A && B

! Logical NOT (Negation) !A

3.4 Ternary (if then else) Operator.

TABLE P-4. TERNARY (IF THEN ELSE) OPERATOR


?: Ternary Operator (if-then-else) A ? B : C

3.5 Associativity Operator.

TABLE P-5. ASSOCIATIVITY OPERATOR


( ) Associativity (A + B) * C

P-3

7/31/2019 IRIG_106_2009



3.6 Precedence and Associativity of Operators From Highest to Lowest.

TABLE P-6. PRECEDENCE AND ASSOCIATIVITY OF

OPERATORS FROM HIGHEST TO LOWEST

Operators Associativity

( ) Left to right

-(UNARY) Right to left

! ~ Right to left

** Left to right

& Left to right

^ Left to right

| Left to right

* / % Left to right

+ - Left to right

<< >> Left to right

< > <= >= Left to right

= = != Left to right

&& Left to right

|| Left to right

?: Right to left

, Left to right

4.0 Numeric Constants

Numeric constants are simply numbers used in the calculations.

TABLE P-7. NUMERIC CONSTANTS (EXAMPLES)

Description Examples

Any string of characters that contains only numerals 12340

Any string of characters that contains only numerals and a-f preceded by "0x" (hex)

0x12ab0x1

Any string of characters that contains only numerals and asingle ".".

1.21.

.2

Any string of characters that contains only numerals, inscientific notation.

1.0E+1010E-10.1e6

Note: As in the TMATS standard itself, alphanumeric data items are caseinsensitive; either upper or lower case characters are allowed.

P-4

7/31/2019 IRIG_106_2009



5.0 Measurements

Measurements may be telemetry measurements or other derived measurements.

TABLE P-8. MEASUREMENTS (EXAMPLES)

Description Examples

Any string of characters beginning with an alphabetic characand containing only alphanumerics and "$_"

A00.1A$1

Any string of characters that is quoted with " and does notcontain ".

"0001"“measurement ’quoted’,

though this is insane - itis legal”

Any string of characters quoted with ' and does not contain '. 'Air Speed'

Any string of characters that contains only numerals and atleast one alphabetic character. This differs from hex because it does not begin with “0x”.

00A10X (this is ok, because it

does not have a number after “0X”)

Note: As in the TMATS standard itself, alphanumeric data items are case insensitive;either upper or lower case characters are allowed.

6.0 Mathematical Functions

6.1 Mathematical Function Format. Mathematical functions are numerical functions thattake some input, perform a specific calculation, and return a value as the result. Each

mathematical function has the form “name(arg1,arg2,...)” which identifies a well-defined nameand contains argument(s) that are separated by commas and surrounded by parentheses. A list of selected mathematical functions is provided at Table P-9.

6.2 Complex Use of Functions. Examples of how functions can be used in mathematicalexpressions are:

a. A*(SIN(B/C)+D) b. A*3.0c. "0001"*A+~Bd. A<B || B<<C ? D : E

P-5

7/31/2019 IRIG_106_2009



TABLE P-9. TABLE OF SELECTED MATHEMATICAL FUNCTIONS

Name Description

acos(x) cos-1(x) in range [0,π], x Є [-1,1].asin(x) sin

-1(x) in range [-π/2, π/2], x Є [-1,1].

atan(x) tan-1(x) in range [-π/2, π/2]

atan2(y,x) tan-1(y/x) in range [-π, π]

ceil(x) smallest integer not less than x

cos(x) cosine of x

cosh(x) hyperbolic cosine of x

exp(x) exponential function, computes ex

fabs(x) absolute value |x|

floor(x) largest integer not greater than x

fmod(x) floating point remainder frexpx(d) Find x in [.5,1] and y so that d = x*pow(2,y), return x

frexpy(d) Find x in [.5,1] and y so that d = x*pow(2,y), return y

ldexp(d,i) returns d*pow(2,i)

log(x) natural logarithm ln(x), x > 0

log10(x) base-10 logarithm log10(x), x > 0

max(x,y) if x>y, then return x, else return y

min(x,y) if x<y, then return x, else return y

modfd(d) returns integral part of d

modfp(d) returns fractional part of d

pow(x,y) compute a value taken to an exponent, x

y

. An error occurswhen x<=0 and y <= 0 or x < 0 and y is not an integer

sin(x) sine of x

sinh(x) hyperbolic sine of x

sqrt(x) square root √x, x>= 0

tan(x) tangent of x

tanh(x) hyperbolic tangent of x

P-6

7/31/2019 IRIG_106_2009



7.0 Derived Grammar Syntax Overview

The following grammar, strictly speaking, does not match the C language. Althoughloosely based on C, the grammar attempts to follow the “spirit” of the C language. The grammar contains three terminal symbols (MEASUREMENT, NUMERIC_CONSTANT and

FUNCTION_NAME) not defined here, but easily understood by their names. The grammar contains two non-terminals, expression and expression-list, which define the entire grammar.The “|” operator used in the grammar denotes a choice meaning “this or that or …” Quotedstrings are literal tokens of the grammar.

expression:expression '+' expression| expression '-' expression| expression '*' expression| expression '/' expression

| expression '|' expression| expression '&' expression| expression '%' expression| expression '**' expression| expression '?' expression ':' expression| expression '<' expression| expression '>' expression| expression '<=' expression| expression '>=' expression| expression '!=' expression| expression '==' expression

| expression '&&' expression| expression '||' expression| '-' expression| '!' expression| '~' expression| ' (' expression ') '| MEASUREMENT| NUMERIC_CONSTANT| FUNCTION_NAME '(' expression_list ')'| FUNCTION_NAME ' (' ')'

expression-list:expression| expression-list ',' expression

Figure P-1. Grammar syntax.

P-7

7/31/2019 IRIG_106_2009



8.0 Grammar Examples

Examples of Yacc and Lex grammar are shown in Figure P-2 and Figure P-3,respectively. The grammar will recognize the derived syntax; that is, they will report whether or not a given text string is valid syntax. However, the examples are not intended to be complete;in other words, they will not compile or perform the calculation. However, the user needs onlyto build a program around them in order to use them; a simple example “main” is shown inFigure P-4..

The Yacc is a parser generator developed by Stephen C. Johnson at American Telephoneand Telegraph (AT&T) for the Unix operating system. It generates a parser, in C language code, based on an analytic grammar written in a notation similar to Backus-Naur Form (BNF). TheLex, a program that generates lexical analyzers, is commonly used along with the Yacc parser generator. Originally written by Eric Schmidt and Mike Lesk, Lex is the standard lexicalanalyzer generator on many Unix systems. A tool exhibiting its behavior is specified as part of the Portable Operating System Interface (POSIX) standard.

P-8

7/31/2019 IRIG_106_2009



%{

%}

%token ERR %token NAME%token CONSTANT

// Operator Precedence Rules (Lowest First, Highest Last)

%left ','%right COND '?'%left OR %left AND

%left EQUAL NOTEQUAL%left '<' '>' LESSEQUAL GREATEREQUAL%left LSHIFT RSHIFT%left '-' '+'%left '*' '/' '%'%left '|'%left '^'%left '&'%left POWER %right '!' '~'%right UMINUS

// Definition of Rules

%%expression:

expression '+' expression| expression '-' expression| expression '*' expression| expression '^' expression| expression '&' expression| expression '%' expression| expression LSHIFT expression| expression RSHIFT expression| expression POWER expression| expression '?' expression ':' expression %prec COND

Figure P-2. Yacc Grammar example. Page 1 x 2

P-9

7/31/2019 IRIG_106_2009



| '-' expression %prec UMINUS| '!' expression| '~' expression| '(' expression ')'

| NAME| CONSTANT| NAME '(' expression_list ')'| NAME '(' ')'| expression '<' expression| expression '>' expression| expression LESSEQUAL expression| expression GREATEREQUAL expression| expression NOTEQUAL expression| expression EQUAL expression| expression OR expression

| expression AND expression;

expression_list:expression| expression_list ',' expression;

%%

Figure P-2. Yacc Grammar example. Page 2 x 2

P-10

7/31/2019 IRIG_106_2009



%{#include “y.tab.h”%}

%%

[\t\n ] {}

\=\= { return(EQUAL); } // Equal To\!\= { return(NOTEQUAL); } // Not Equal To\<\= { return(LESSEQUAL); } // Less Than or Equal To\>\= { return(GREATEREQUAL); } // Greater Than or Equal To(\*\*) { return(POWER); } // Power (FORTRANish)\|\| { return(OR); } // Logical OR

\&\& { return(AND); } // Logical AND\<\< { return(LSHIFT); } // Bitwise Left Shift\>\> { return(RSHIFT); } // Bitwise Right Shift

\> | // Greather Than\< | // Less Than\! | // Logical Negation\? | // Ternary Operator ?\: | // Ternary Operator :\% | // Modulus (Remainder)\, | // Comma Operator (function)

\* | // Multiplication (Product)\/ | // Division (Quotient)\+ | // Addition (Sum)\- | // Subtraction (Difference)\| | // Bitwise OR \& | // Bitwise AND\^ | // Bitwise XOR \~ | // Bitwise NOT$ |$ { return(yytext[0]); }

Figure P-3. Lex Grammar example. Page 1 x 2

P-11

7/31/2019 IRIG_106_2009



([0][xX][0-9a-fA-F]+)|([0-9]+) {return(CONSTANT);

}

(([0-9]+\.?[0-9]*)|([0-9]*\.[0-9]+))([eE][-+]?[0-9]+)? {return(CONSTANT);

}

\"[^\"\n]*\" |\'[^'\n]*\' {

return(NAME);}

([0-9]+[a-zA-Z])?[a-zA-Z0-9$_\.]+ {return(NAME);

}

. { return(ERR); } // Catchall Error

%%

Figure P-3. Lex Grammar. Page 2 x 2

yywrap()

{return 1;}yyerror(char *s){ printf("error: %s\n",s);

}main(){

yyparse();}

Figure P-4. Example program (main).

P-12

7/31/2019 IRIG_106_2009



9.0 Telemetry Attributes Transfer Standard (TMATS) Examples

In the following examples, input measurement names are in the form of MA, MB, andMC. Derived parameter names are in the form of DMA, DMB, and DMC.

9.1 TMATS Example 1:

DMA = MA + MB

Function style

C-1\DCN:DMA; Derived parameter C-1\DCT:DER; Derived conversion typeC-1\DPAT:N; Name of algorithm will be givenC-1\DPA:+; Addition operator C-1\DPTM:MB; Measurement MB triggers the calculationC-1\DPNO:1; Every sample of MB triggers the calculationC-1\DP\N:2; Two input measurementsC-1\DP-1:MA;C-1\DP-2:MB;

Formula style

C-2\DCN:DMA;C-2\DCT:DER;C-2\DPAT:A; Algorithm will be givenC-2\DPA:MA + MB; Algorithm syntaxC-2\DPTM:MB;C-2\DPNO:1;

9.2 TMATS Example 2.

DMB = MC / MD

Function style

C-3\DCN:DMB; Derived parameter C-3\DCT:DER; Derived conversion typeC-3\DPAT:N; Name of algorithm will be given

C-3\DPA:/; Division operator C-3\DPTM:MD; Measurement MD triggers the calculationC-3\DPNO:1; Every sample of MD triggers the calculationC-3\DP\N:2; Two input measurementsC-3\DP-1:MC;C-3\DP-2:MD;

P-13

7/31/2019 IRIG_106_2009



Note : In function style, the algorithm determines the meaning of the inputmeasurements. In this example, the division algorithm assigns the first inputmeasurement as the dividend and the second input measurement as the divisor.

Formula style

C-4\DCN:DMB;C-4\DCT:DER;C-4\DPAT:A; Algorithm will be givenC-4\DPA:MC / MD; Algorithm syntaxC-4\DPTM:MD;C-4\DPNO:1;


DMC = square root of ME

Function style

C-5\DCN:DMC; Derived parameter C-5\DCT:DER; Derived conversion typeC-5\DPAT:N; Name of algorithm will be givenC-5\DPA:SQRT; Square root functionC-5\DP\N:1; One input measurementC-5\DP-1:ME;

Formula style

C-6\DCN :DMC;C-6\DCT :DER;C-6\DPAT:A; Algorithm will be givenC-6\DPA:SQRT(ME); Algorithm syntax

Note : The trigger measurand is not given ; there is only one input, which musttrigger the calculation.


DMD = MF*(SIN(MG/MH)+MJ)

Function style

C-7\DCN:XA; Derived parameter C-7\DCT:DER; Derived conversion typeC-7\DPAT:N; Name of algorithm will be givenC-7\DPA:/; Division operator

P-14

7/31/2019 IRIG_106_2009



C-7\DP\N:2; Two input measurementsC-7\DP-1:MG;C-7\DP-2:MH;C-8\DCN:XB; Derived parameter C-8\DCT:DER; Derived conversion type

C-8\DPAT:N; Name of algorithm will be givenC-8\DPA:SIN; Sine functionC-8\DP\N:1; One input measurementC-8\DP-1:XA;C-9\DCN:XC; Derived parameter C-9\DCT:DER; Derived conversion typeC-9\DPAT:N; Name of algorithm will be givenC-9\DPA:+; Addition operator C-9\DP\N:2; Two input measurementsC-9\DP-1:XB;C-9\DP-2:MJ;

C-10\DCN:DMD; Derived parameter C-10\DCT:DER; Derived conversion typeC-10\DPAT:N; Name of algorithm will be givenC-10\DPA:*; Multiplication operator C-10\DP\N:2; Two input measurementsC-10\DP-1:MF;C-10\DP-2:XC;

Note: In this example, several steps are needed, each generating an intermediateresult (XA, XB, and XC), before the derived parameter is obtained. This methodis shown only for illustrative purposes and is not recommended. If this function isneeded, a custom algorithm should be written to implement it. Then the functionstyle could be used, as follows:

C-11\DCN:DMD; Derived parameter C-11\DCT:DER; Derived conversion typeC-11\DPAT:N; Name of algorithm will be givenC-11\DPA:NEWALG; Name of custom algorithmC-11\DPTM:MJ;C-11\DPNO:1;C-11\DP\N:4; Four input measurementsC-11\DP-1:MF;C-11\DP-2:MG;C-11\DP-3:MH;C-11\DP-4:MJ;