http://ftp.irig106.org/wiki/ 2026-04-21T14:51:56+00:00 http://ftp.irig106.org/wiki/ http://ftp.irig106.org/wiki/_media/wiki:logo.png text/html 2014-05-29T19:40:22+00:00 Anonymous (anonymous@undisclosed.example.com) http://ftp.irig106.org/wiki/ch10_handbook:analog_data?rev=1401392422&do=diff ~~ODT~~ ANALOG DATA Type 0x20, Analog Data, Format 0 Reserved for future use. Type 0x21, Analog Data, Format 1 (Analog Data) Analog Data, Format 1 packets are used to record digitized analog signals. In general, the analog data packet will contain multiple digitized values from multiple analog channels. Digitized signal values can be stored in either a unpacked or packed fashion. Unpacked storage describes a situation in which each sample occupies one 16-bit word with unused bits zero … text/html 2014-05-29T19:34:04+00:00 Anonymous (anonymous@undisclosed.example.com) http://ftp.irig106.org/wiki/ch10_handbook:applicable_documents?rev=1401392044&do=diff ~~ODT~~ APPLICABLE DOCUMENTS Government documents * Range Commanders Council (RCC) Document 106-07, Telemetry Standard. * RCC Document 118-06, Test Methods for Telemetry Systems and Subsystems. * MIL-STD-1553B, Aircraft Internal Time Division Command/Response Multiplex Data Bus, United States (U.S.) Department of Defense ( text/html 2014-05-29T19:41:18+00:00 Anonymous (anonymous@undisclosed.example.com) http://ftp.irig106.org/wiki/ch10_handbook:arinc_429_data?rev=1401392478&do=diff ~~ODT~~ ARINC 429 DATA Type 0x38, ARINC 429 Data, Format 0 (ARINC 429 Data) The ARINC 429 Data, Format 0 packets are used to record data messages from an ARINC 429 data bus. ARINC 429 is a unidirectional data bus that is commonly found on commercial and transport aircraft. Words are 32 bits in length and most messages consist of a single data word. Messages are transmitted at either 12.5 or 100 kbit/s from a transmitting system to one or more receiving systems. The transmitter is always … text/html 2014-05-29T19:36:39+00:00 Anonymous (anonymous@undisclosed.example.com) http://ftp.irig106.org/wiki/ch10_handbook:computer_generated_data?rev=1401392199&do=diff ~~ODT~~ COMPUTER GENERATED DATA Type 0x00, Computer Generated Data, Format 0 Computer Generated Data, Format 0 packets are used to store data generated internally by a recorder. The data packet begins with the CSDW shown in Figure 6-8. The data portion of the data packet is undefined and left to the discretion of the recorder manufacturer. text/html 2014-05-29T19:43:28+00:00 Anonymous (anonymous@undisclosed.example.com) http://ftp.irig106.org/wiki/ch10_handbook:conformance_to_irig_106?rev=1401392608&do=diff ~~ODT~~ CONFORMANCE TO IRIG 106 Chapter 10 of the IRIG 106 standard sets forth requirements for digital recorders. Paragraph 10.3.1 summarizes requirements for a recorder to be considered 100 percent compliant with the standard. A number of features described in Chapter 10 are considered optional. Optional features are not required to be implemented; however, if they are implemented, they must be in accordance with the Chapter 10 standard. text/html 2014-07-16T20:18:33+00:00 Anonymous (anonymous@undisclosed.example.com) http://ftp.irig106.org/wiki/ch10_handbook:data_file_interpretation?rev=1405541913&do=diff ~~ODT~~ DATA FILE INTERPRETATION Overall Data File Organization Chapter 10 data files are organized as a sequential series of data packets. Each data packet can only contain one type of data (i.e. 1553, Pulse Code Modulation (PCM), etc.). Data packets frequently contain multiple individual data messages. text/html 2014-05-29T19:34:37+00:00 Anonymous (anonymous@undisclosed.example.com) http://ftp.irig106.org/wiki/ch10_handbook:data_retrieval?rev=1401392077&do=diff ~~ODT~~ DATA RETRIEVAL Small Computer Systems Interface (SCSI) Protocol Recorded data from a Chapter 10 recorder is retrieved by transferring it to a host computer over one of several interfaces provided by the recorder. Chapter 10 requires that each Removable Memory Module ( text/html 2014-05-29T19:40:40+00:00 Anonymous (anonymous@undisclosed.example.com) http://ftp.irig106.org/wiki/ch10_handbook:discrete_data?rev=1401392440&do=diff ~~ODT~~ DISCRETE DATA Type 0x28, Discrete Data, Format 0 Reserved for future use. ---------- Type 0x29, Discrete Data, Format 1 (Discrete Data) Discrete Data, Format 1 packets are used to record the state of discrete digital signals. In general, the discrete data packet will contain multiple values from multiple discrete events. text/html 2014-05-29T19:42:55+00:00 Anonymous (anonymous@undisclosed.example.com) http://ftp.irig106.org/wiki/ch10_handbook:ethernet_data?rev=1401392575&do=diff ~~ODT~~ ETHERNET DATA Type 0x68, Ethernet Data, Format 0 Ethernet Data, Format 0 packets are used to record Ethernet data frames from an Ethernet network. In general, an Ethernet data packet will contain multiple captured Ethernet data frames. text/html 2014-05-29T19:42:20+00:00 Anonymous (anonymous@undisclosed.example.com) http://ftp.irig106.org/wiki/ch10_handbook:ieee_1394_data?rev=1401392540&do=diff ~~ODT~~ IEEE 1394 DATA Type 0x58, IEEE 1394 Data, Format 0 (IEEE 1394 Transaction) IEEE 1394 Data, Format 0 packets are used to record data messages at the transaction layer of the IEEE 1394 serial data bus. Currently IEEE 1394, IEEE 1995, IEEE 1394a, and text/html 2014-05-29T19:41:49+00:00 Anonymous (anonymous@undisclosed.example.com) http://ftp.irig106.org/wiki/ch10_handbook:image_data?rev=1401392509&do=diff ~~ODT~~ IMAGE DATA Type 0x48, Image Data, Format 0 (Image Data) Image Data, Format 0 packets are used to record digitized video images. The layout of the CSDW is shown in Figure 6-42. The uLength value is the number bytes in each segment. The bIntraPckHdr flag indicated the presence of the intra-packet data header. The uSum value indicates if and how an image is segmented in the data packet. The uPart value indicates which part of a possibly segmented image is contained in the data packe… text/html 2014-05-29T19:40:55+00:00 Anonymous (anonymous@undisclosed.example.com) http://ftp.irig106.org/wiki/ch10_handbook:message_data?rev=1401392455&do=diff ~~ODT~~ MESSAGE DATA Type 0x30, Message Data, Format 0 (Generic Message Data) Message Data packets are used to record data from sources that do not have a defined packet type in the Chapter 10 standard. Examples of this might be the H-009 bus found on older F-15 aircraft or the High Speed Data Bus (HSDB) bus found on older F-16 aircraft. The Chapter 10 standard implies that Message Data packets represent text/html 2014-05-29T19:32:35+00:00 Anonymous (anonymous@undisclosed.example.com) http://ftp.irig106.org/wiki/ch10_handbook:mil-std-1553_data?rev=1401391955&do=diff ~~ODT~~ MIL-STD-1553 DATA Type 0x18, MIL-STD-1553 Data, Format 0 Reserved for future use. ---------- Type 0x19, MIL-STD-1553 Data, Format 1 (MIL-STD-1553B Data) MIL-STD-1553 Data, Format 1 packets are used to record the MIL-STD-1553 message transactions on a bus. In general, the 1553 data packet will contain multiple 1553 messages. text/html 2014-05-29T19:42:35+00:00 Anonymous (anonymous@undisclosed.example.com) http://ftp.irig106.org/wiki/ch10_handbook:parallel_data?rev=1401392555&do=diff ~~ODT~~ PARALLEL DATA Type 0x60, Parallel Data, Format 0 Parallel Data, Format 0 packets are used to record data bits received from a discrete parallel data interface. The number of bits that comprise one data word can range from 2 to 128 bits in length. A parallel data packet can contain multiple parallel data words. text/html 2014-07-16T07:04:54+00:00 Anonymous (anonymous@undisclosed.example.com) http://ftp.irig106.org/wiki/ch10_handbook:pcm_data?rev=1405494294&do=diff ~~ODT~~ PCM DATA Type 0x08, PCM Data, Format 0. Reserved for future use Type 0x09, PCM Data, Format 1 (IRIG 106 Chapter 4/8) PCM Data, Format 1 packets are used to record Pulse Code Modulation (PCM) data frames. PCM data is a serial stream of bits from multiple interleaved data sources. Each data source generally operates at a different data rate and have their digital data interleaved in a fixed, defined fashion. The data from these multiplexed data sources are organized into major fram… text/html 2014-05-29T19:35:41+00:00 Anonymous (anonymous@undisclosed.example.com) http://ftp.irig106.org/wiki/ch10_handbook:recorder_command_and_control?rev=1401392141&do=diff ~~ODT~~ RECORDER COMMAND AND CONTROL Recorders are controlled over a full duplex communications channel. Typically, this channel is either a Recommended Standard 232 (RS-232) or an RS-422 serial communications port. Chapter 10 of IRIG 106 also defines a mechanism which allows control over any of the supported recorder network channels, including Ethernet, Fibre Channel, and text/html 2014-05-29T19:34:21+00:00 Anonymous (anonymous@undisclosed.example.com) http://ftp.irig106.org/wiki/ch10_handbook:recorder_setup_and_configuration?rev=1401392061&do=diff ~~ODT~~ RECORDER SETUP AND CONFIGURATION Chapter 9 of IRIG 106 defines the Telemetry Attributes Transfer Standard (TMATS). Historically, TMATS has been used as a shorthand way of documenting and describing recorded data to facilitate future data interpretation and reduction. In the context of Chapter 10, text/html 2014-05-29T19:33:29+00:00 Anonymous (anonymous@undisclosed.example.com) http://ftp.irig106.org/wiki/ch10_handbook:scope?rev=1401392009&do=diff ~~ODT~~ General The Telemetry Group (TG) of the Range Commanders Council (RCC) developed the Inter-range Instrumentation Group (IRIG) 106 standard for test range telemetry (TM). The primary purpose of the IRIG 106, published as RCC Document 106, Telemetry Standard, is to define a common framework for test range instrumentation to ensure test range interoperability. The text/html 2014-05-29T19:03:33+00:00 Anonymous (anonymous@undisclosed.example.com) http://ftp.irig106.org/wiki/ch10_handbook:start?rev=1401390213&do=diff ~~ODT~~ IRIG 106-07 Chapter 10 Programming Handbook This programming handbook presents the results of work performed by members of the Telemetry Group (TG) under Task TG-83 of the Range Commanders Council (RCC). This document provides information to assist programmers in developing software for use with text/html 2016-09-29T11:51:21+00:00 Anonymous (anonymous@undisclosed.example.com) http://ftp.irig106.org/wiki/ch10_handbook:subchannel_numbering?rev=1475149881&do=diff ~~ODT~~ Subchannel numbering: CH10 vs. TMATS This issue was solved in IRIG106-15 but still has to be considered for recorders conforming to older releases or using older TMATS. The end of the section presents the solution in the 2015 release. Some data types have subchannels and some of these have additional attributes that are described in text/html 2014-05-29T19:39:59+00:00 Anonymous (anonymous@undisclosed.example.com) http://ftp.irig106.org/wiki/ch10_handbook:time_data?rev=1401392399&do=diff ~~ODT~~ TIME DATA Type 0x10, Time Data, Format 0. Reserved for future use Type 0x11, Time Data, Format 1 (IRIG/GPS/RTC) Time is recorded in a data file much like any other data source. The purpose of the Time Data Format 1 packet is to provide a correlation between an external clock source and the recorder internal 10 text/html 2014-05-29T19:42:06+00:00 Anonymous (anonymous@undisclosed.example.com) http://ftp.irig106.org/wiki/ch10_handbook:uart_data?rev=1401392526&do=diff ~~ODT~~ UART DATA Type 0x50, Universal Asynchronous Receiver and Transmitter (UART) Data, Format 0 (UART Data) UART Data, Format 0 packets are used to record character data from an asynchronous serial interface. Generally, the UART data packet will contain multiple buffers of serial data. The Chapter 10 standard has no provisions for specifying how characters will be grouped into blocks of data other than the 100 msec maximum data block time. It is common for recorder vendors to provide a… text/html 2014-05-29T19:41:33+00:00 Anonymous (anonymous@undisclosed.example.com) http://ftp.irig106.org/wiki/ch10_handbook:video_data?rev=1401392493&do=diff ~~ODT~~ VIDEO DATA Type 0x40, Video Data, Format 0 (MPEG-2/H.264 Video) Video Data, Format 0 packets are used to record digitized video and associated audio signals. Format 0 packets are restricted to contain only Moving Picture Experts Group (MPEG