The IRIG 106 standards body the RCC (Range Commanders Council) requested proposals for a mapping between XML language and CH10 files with their change request CR031. Data Bus Tools made a proposal for a specification and provided an implementation integrated in FLIDAS. The specification is official part of the RCC's "IRIG 106 Chapter 10 Programmers Handbook" (RCC document 123-16) in Appendix P/Q since August 2016 (moved to appendix Q/R in RCC 123-20).
The specification can be downloaded from:
The intention of this specification is to have a way to define IRIG 106 chapter 10 files for testing purposes in a readable XML format. This would allow tools to convert between XML and CH10 back and forth. The focus of XML is readability and not memory efficiency or processing efficiency. Therefore the area of application for this specification is the generation of smaller test files (although nothing technically prevents to have large files).
The conversion from XML to CH10 opens these opportunities for example:
The conversion from CH10 to XML opens these opportunities for example:
There are several downloads of samples, conversion software and documents below. Some of them belong to the official published specification version 0.3.1. However the RCC only updates thes documents about every four years.
We as the sole developer of the current official specification and the only available implemetation (as far as known) enhance the specification independent of the current four year release cycles of the RCC's document so we might do changes to the format that are incompatible to the released format. There is no guarantee that these will be included in further official RCC documents. But since this technology is new there should be room to evolve when new use cases appear. If you actively use it for your testing and rely on it you should consider keeping downloads of a proper release of the free FLIDAS version for your XML format version. If you use a commercial version you can still use this functionality with the free version. Please let us know new use cases and requirements for this functionality and we will check if it can be supported.
So far (FLIDAS Version 4.10, XML CH10 mapping specification version 0.3.7) all changes are extensions in a way that XML files following the RCC specification can still be processed. However if you convert CH10 files to XML features of the FLIDAS extended format might appear in some cases.
The downloads below are marked to be for the official (0.3.1) or extended version (0.3.7.).
If you have no XML editor yet and you don't want to use a simple text editor, you can download this manual how to set up a free XML environment for editing CH10 XML files.
The downloads below are available as XML file and as resulting converted CH10 file. You can also create the CH10 file yourself using the prototype FLIDAS plug-in below. Be aware that some of the XML files create corrupted CH10 files by intention or have incomplete TMATS setup.
|Description||XML download||CH10 download|
|Shows how data for ARINC 429 can be defined in a structured way||Arinc429.xml||Arinc429.ch10|
|Shows how data for MIL-STD 1553 can be defined in a structured way||mil1553.xml||mil1553.ch10|
|Shows how data for UART can be defined in a structured way||UART.xml||UART.ch10||Shows the definition of Packets not yet supported by the XML to CH10 mapping in a raw data definition. Contains definitions for CH10 CAN Bus and DATaRec4 CAN bus definition||CANBus.xml||CANBus.ch10|
|Shows a NMEA 0183 GPS definition using structured UART message definition||NMEA0183.xml||NMEA0183.ch10|
|Shows how specific elements of packet decoding can be tested. Here the RTC wraps from the highest value to 0 and you can check how your CH10 software reacts on it (this is no unrealistic case since RTC has no defined starting value)||RTCWrap.xml||RTCWrap.ch10|
|Shows many other features of the XML to CH10 mapping. The created file contains a lot of intentional errors like arbitrary data inserted between packets, checksum and sequence errors etc. It also shows things like relative packet time definition and other concepts explained above||
example.tma is a TMATS file included by the XML file and must be stored in the same directory.
The free FLIDAS version includes an implementation for conversion in both directions. You can also use the free software to inspect the results immediately. The basic commercial version can provide more details on the converted data as it offers further low level access to all CH10 properties and also verifies the file format to some extent. Also it offers some options on the generated XML code (improves maintainability for different use scenarios).
You will find the downloadable software and the manual for the extended version on the FLIDAS product page. The manual includes a short description of the implementation in the chapter 4.22.
If you require downloads for the old, official version you can download it below, but also see the system requirements and installation instructions on the website for the current FLIDAS download:
|This is the old version for official specification!|
Download the recent, extended FLIDAS version here.
|Download||File size||MD5 checksum|
|FLIDAS 3.6.0 for Windows for 32 bit Java||38838119||76fb0f68a7f7cc9389b5718d666bb99c|
|FLIDAS 3.6.0 for Windows for 64 bit Java||38843054||bd23531f835e09f17f78c035415e1fdd|