IRIG106wiki

This programming handbook presents the results of work performed by members of the Telemetry Group (TG) under Task TG-110 of the Range Commanders Council (RCC) to update the original handbook to reflect additions and changes to the standard made since its release.

IRIG 106-09 was released in April of 2009 with primarily clarifications and additional definitions for existing commands. No new data types were added with this release although the TELNET protocol was introduced as a new interface type for ground-based recorders. In addition, a number of changes were made to support XML TMATS for use in configuring the recorder.

IRIG 106-13 was released in June of 2013 with two new data types (CAN BUS and AFDX) plus a new sub-type to support Dynamic Image Packets. A complete list of changes to this version can be found under IRIG 106-13 Changes. A number of updates were also made to TMATS (IRIG 106-13 Chapter 9) related to Chapter 10 with a complete list found under IRIG 106-13 TMATS Changes.

The primary goal of this document is to provide updates to the original where additional clarification is needed or where new information needs to be added. The sections below address both of these cases.

RECORDER COMMAND AND CONTROL

• Network Control

IRIG 106-09 added the ability to issue Chapter 6 commands via a TELNET interface. It does not specify how this interface is to be configured nor does it provide any specific commands for that purpose.

It was decided during an Recorder Vendor Working Group telecon to push CR031 into an appendix of the next release of the programmer's handbook. The work on this was submitted by Christian Rueck of Data Bus Tools GmbH. The XML below presents one example of a file definition based on this concept.

<?xml version="1.0" encoding="UTF-8"?>
<cns:ch10 xmlns:cns="http://www.example.org/XMLCH10Mapping" 
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:noNamespaceSchemaLocation="XMLCH10Mapping.xsd" 
  xsi:schemaLocation="http://www.example.org/XMLCH10Mapping XMLCH10Mapping.xsd">
 
<!-- Include some predefined TMATS file -->
    <cns:Packet ChannelID="0" RTC="0" DataType="TMATS">
        <cns:TMATSData Ch10Version="106-13">
            <cns:IncludeFile>c:\someFile.tma</cns:IncludeFile>
        </cns:TMATSData>
    </cns:Packet>
 
<!-- Create a first time packets -->
    <cns:Packet ChannelID="1" RTC="0" DataType="Time Format 1">
        <cns:TimeData>
            <cns:TimeDataContent Time="11:23:12.000" Date="2012-11-23"/>
        </cns:TimeData>
    </cns:Packet>
 
<!-- Define further time packets relative to first-->
    <cns:Packet ChannelID="1" RTC="c+10000000" DataType="Time Format 1">
        <cns:TimeData>
            <cns:TimeDataRelativeContent Offset="1000000000"/>
        </cns:TimeData>
    </cns:Packet>
 
<!-- Further attributes could be defined but are optional-->
    <cns:Packet ChannelID="1" RTC="c+10000000" ChecksumType="CRC16" 
      DataType="Time Format 1" DataTypeVersion="106-13">
        <cns:TimeData MonthYearAvailable="True" LeapYear="True" TimeFormat="IRIG B" TimeSource="External">
            <cns:TimeDataRelativeContent Offset="1000000000"/>
        </cns:TimeData>
        </cns:Packet>
 
<!-- Errors can be introduced-->
    <cns:Packet ChannelID="1" RTC="c+10000000" DataType="Time Format 1" DataLength="+2" 
      PacketLength="27" HeaderCRC="+0001" DataOverflow="True" SequenceNumber="+5" DataCRC="1234">
        <cns:GenericData>
            <cns:Bytes>0F 12 31 EF 6B</cns:Bytes>
        </cns:GenericData>
    </cns:Packet>
 
<!-- Packets can have secondary headers-->
    <cns:Packet ChannelID="1" RTC="c+10000000" DataType="Time Format 1" SecondaryHeaderPresent="True">
        <cns:SecondaryHeader Time="11:23:12.000" Date="2012-11-23"/>
        <cns:TimeData>
            <cns:TimeDataRelativeContent Offset="1000000000"/>
        </cns:TimeData>
    </cns:Packet>
 
<!-- Secondary headers can have errors too-->
    <cns:Packet ChannelID="1" RTC="c+10000000" DataType="Time Format 1" SecondaryHeaderPresent="True">
        <cns:SecondaryHeader ERTC="+0" CRC="-0001" Filler="3E 2F"/>
        <cns:TimeData>
            <cns:TimeDataRelativeContent Offset="1000000000"/>
        </cns:TimeData>
    </cns:Packet>
 
<!-- raw data like packet flags and CSDW can be defined as a base an modified by further options -->
    <cns:Packet ChannelID="1" RTC="c+10000000" DataType="Time Format 1" PacketFlags="3F" 
      DataOverflow="True" SecondaryHeaderTimeFormat="Chapter 4 Binary">
        <cns:TimeData CSDW="31e5893C" LeapYear="True" TimeSource="Internal From RMM">
            <cns:TimeDataRelativeContent Offset="1000000000"/>
        </cns:TimeData>
    </cns:Packet>
 
<!-- Arbitrary data can be added between packets-->
    <cns:Words>e37F 212B</cns:Words>
    <cns:Bytes>7F</cns:Bytes>
 
<!-- New packet types can be created-->
    <cns:Packet ChannelID="12" RTC="333" DataTypeRaw="8F">
        <cns:GenericData>
            <cns:Bytes>3F 77</cns:Bytes>
        </cns:GenericData>
    </cns:Packet>
 
<!-- Structured definition for specific packet types is available -->
    <cns:Packet ChannelID="15" RTC="p+300" DataType="1553 Format 1">
        <cns:MilbusData>
 
            <cns:MilbusMessage RTC="+20">
                <cns:Words>453E 12FD</cns:Words>
            </cns:MilbusMessage>
 
            <cns:MilbusMessage RTC="+20" RTRTTransfer="True" ResponseTimeOut="True">
                <cns:Words>453E 12FD</cns:Words>
            </cns:MilbusMessage>
 
<!-- Any data can be inserted in between -->
            <cns:Bytes>3F 21</cns:Bytes>
 
            <cns:MilbusMessage RTC="+20">
                <cns:Words>453E 12FD</cns:Words>
            </cns:MilbusMessage>
 
        </cns:MilbusData>
    </cns:Packet>
    <cns:Bytes>3F</cns:Bytes>
 
</cns:ch10>