ch10_handbook:subchannel_numbering
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| ch10_handbook:subchannel_numbering [2014/05/15 03:01] – created christianr | ch10_handbook:subchannel_numbering [2016/09/29 06:51] (current) – Described solution for the problem introduced in IRIG 106-15 christianr | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ~~ODT~~ | ||
| ====== Subchannel numbering: CH10 vs. TMATS ====== | ====== 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 TMATS. To map the TMATS attributes to the subchannel, subchannel numbers are used. Depending on the recorder vendor TMATS and CH10 might use different numbers to describe the same subchannel. This sometimes even deviates within vendors (possibly by recorder model / firmware). The data types where conflicts have been seen start their numbering with 0 in CH10 and with 0 or 1 in TMATS. | Some data types have subchannels and some of these have additional attributes that are described in TMATS. To map the TMATS attributes to the subchannel, subchannel numbers are used. Depending on the recorder vendor TMATS and CH10 might use different numbers to describe the same subchannel. This sometimes even deviates within vendors (possibly by recorder model / firmware). The data types where conflicts have been seen start their numbering with 0 in CH10 and with 0 or 1 in TMATS. | ||
| Line 14: | Line 17: | ||
| //Note: Actual problems have been seen on ARINC 429, UART and Ethernet. Problems on Message and CAN data types are expected but not confirmed.// | //Note: Actual problems have been seen on ARINC 429, UART and Ethernet. Problems on Message and CAN data types are expected but not confirmed.// | ||
| + | |||
| + | Since IRIG 106-15 the issue has been solved like this: | ||
| + | CH9 now requires all declared subchannel numbers to start with 1. For analog subchannels the numbers can be defined with the new attribute R-x\AMCN-n-m. | ||
| + | This means a subchannel declared as 1 in CH10 maps to the subchannel 1 in TMATS. For other data types a subchannel 0 in CH10 maps to 1 in TMATS. | ||
| + | |||
ch10_handbook/subchannel_numbering.txt · Last modified: 2016/09/29 06:51 by christianr