User Tools

Site Tools


ch10_handbook:mil-std-1553_data

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
ch10_handbook:mil-std-1553_data [2014/04/13 20:01]
bob
ch10_handbook:mil-std-1553_data [2014/05/29 14:32]
bob
Line 1: Line 1:
 +~~ODT~~
 ===== MIL-STD-1553 DATA ===== ===== MIL-STD-1553 DATA =====
  
Line 5: Line 6:
 Reserved for future use.  Reserved for future use. 
  
 +----
  
 ==== Type 0x19, MIL-STD-1553 Data, Format 1 (MIL-STD-1553B Data) ==== ==== Type 0x19, MIL-STD-1553 Data, Format 1 (MIL-STD-1553B Data) ====
Line 11: Line 13:
 general, the 1553 data packet will contain multiple 1553 messages. ​ general, the 1553 data packet will contain multiple 1553 messages. ​
    
-The layout of the CSDW is shown in Figure 6-21. The uMsgCnt field indicates the +The layout of the CSDW is shown below. The uMsgCnt field indicates the 
 number of messages contained in the data packet. The uTTB field indicates the 1553 message ​ number of messages contained in the data packet. The uTTB field indicates the 1553 message ​
 bit to which the time tag corresponds. ​ bit to which the time tag corresponds. ​
  
-<​code> ​+<​code>​
 struct Su1553F1_ChanSpec ​ struct Su1553F1_ChanSpec ​
     {      { 
Line 31: Line 33:
 The individual 1553 messages follow the CSDW. Each 1553 message has an intra-packet The individual 1553 messages follow the CSDW. Each 1553 message has an intra-packet
 time stamp, an intra-packet header data word, and then the actual 1553 message. The time stamp, an intra-packet header data word, and then the actual 1553 message. The
-layout of the message header is shown in Figure 6-22. The suIntPktTime field is an 8-byte ​+layout of the message header is shown below. The suIntPktTime field is an 8-byte ​
 value. The specific interpretation of this field is determined by packet header flags. This time is  value. The specific interpretation of this field is determined by packet header flags. This time is 
 interpreted as a RTC value as depicted in Figure 6-5 if Secondary Headers are not enabled by  interpreted as a RTC value as depicted in Figure 6-5 if Secondary Headers are not enabled by 
Line 64: Line 66:
 Type 0x19 MIL-STD-1553 Data Format 1 intra-packet header Type 0x19 MIL-STD-1553 Data Format 1 intra-packet header
 </​b></​center></​html> ​ </​b></​center></​html> ​
- 
  
 The amount of data that follows the intra-packet header is variable. The data length in  The amount of data that follows the intra-packet header is variable. The data length in 
Line 76: Line 77:
 Command Word as well as the bRT2RT flag to determine the offsets of the other message ​ Command Word as well as the bRT2RT flag to determine the offsets of the other message ​
 structures such as the Status and Data Word(s). The layouts of the various types of 1553  structures such as the Status and Data Word(s). The layouts of the various types of 1553 
-messages are shown in Figure 6-23 and Figure 6-24. When calculating data word count, be  +messages are shown in the figures below
-careful to take Mode Codes and word count wrap around into account. An algorithm to  +
-determine ​the number of data words in a message is shown in C-like pseudo-code in Figure 6-25.  +
-This algorithm only works for a message with no errors. Otherwise, Block Status Word bits and  +
-the Length Word are used to determine data and status words actually present+
  
- +{{ :​ch10_handbook:​1553_message_word_layout.png?​nolink |}}
-FIXME+
  
 <​html><​center><​b>​ <​html><​center><​b>​
Line 89: Line 85:
 </​b></​center></​html> ​ </​b></​center></​html> ​
  
-FIXME+{{ :​ch10_handbook:​1553_broadcast_word_layout.png?​nolink |}}
  
 <​html><​center><​b>​ <​html><​center><​b>​
 1553 Broadcast message word layout 1553 Broadcast message word layout
 </​b></​center></​html> ​ </​b></​center></​html> ​
 +
 +When calculating data word count, be careful to take Mode Codes and word count wrap around into account. An algorithm to determine the number of data words in a message is shown in C-like pseudo-code below. This algorithm only works for a message with no errors. Otherwise, Block Status Word bits and the Length Word are used to determine data and status words actually present. ​
  
 <​code>​ <​code>​
Line 111: Line 109:
 </​b></​center></​html> ​ </​b></​center></​html> ​
  
 +----
  
 ==== Type 0x1A, MIL-STD-1553 Data, Format 2 (16PP194 Bus) ==== ==== Type 0x1A, MIL-STD-1553 Data, Format 2 (16PP194 Bus) ====
Line 119: Line 118:
 Protocol. A 16PP194 transaction consists of six 32-bit words consisting of a 16PP194 ​ Protocol. A 16PP194 transaction consists of six 32-bit words consisting of a 16PP194 ​
  
-Command, Command Echo, Response, GO/NOGO, GO/NOGO Echo and Status as illustrated ​in  +Command, Command Echo, Response, GO/NOGO, GO/NOGO Echo and Status as illustrated ​below. Multiple transactions may be encoded into the data portion of a single packet.
-Figure 6-26. Multiple transactions may be encoded into the data portion of a single packet.+
  
-FIXME+{{ :​ch10_handbook:​16pp194_message_transaction.png?​nolink |}}
  
 <​html><​center><​b>​ <​html><​center><​b>​
Line 128: Line 126:
 </​b></​center></​html> ​ </​b></​center></​html> ​
  
-The layout of the CSDW is show in Figure 6-27. The 16PP194 packet can contain ​ +The layout of the CSDW is show below. The 16PP194 packet can contain multiple bus transactions. The uMsgCnt field indicates the number of 16PP194 messages in the packet. ​
-multiple bus transactions. The uMsgCnt field indicates the number of 16PP194 messages in the  +
-packet. ​+
    
 <​code> ​ <​code> ​
Line 146: Line 142:
 bits, four sub-address bits, a parity bit, and a sync bit. Only the 24 bits of data, address, and  bits, four sub-address bits, a parity bit, and a sync bit. Only the 24 bits of data, address, and 
 sub-address values are mapped into the 16PP194 recorded data word. Sync and parity bits are not  sub-address values are mapped into the 16PP194 recorded data word. Sync and parity bits are not 
-recorded. The mapping of these bits is shown in Figure 6-28+recorded. The mapping of these bits is shown below.
  
-FIXME+{{ :​ch10_handbook:​16pp194_to_irig_mapping.png?​nolink |}}
  
 <​html><​center><​b>​ <​html><​center><​b>​
Line 154: Line 150:
 </​b></​center></​html> ​ </​b></​center></​html> ​
  
-The layout of the recorded 16PP194 word is shown in Figure 6-29. The uDataWord ​+The layout of the recorded 16PP194 word is shown in below. The uDataWord ​
 field contains the message data. The uRiuSubAddr field is the Remote Interface Unit (RIU)  field contains the message data. The uRiuSubAddr field is the Remote Interface Unit (RIU) 
 sub-address. The uRiuAddr field is the RIU address. The bParityError flag indicates a  sub-address. The uRiuAddr field is the RIU address. The bParityError flag indicates a 
Line 161: Line 157:
 the general range of gap time. The mapping of uGap values to gap time ranges can be found in  the general range of gap time. The mapping of uGap values to gap time ranges can be found in 
 the Chapter 10 standard. The uBusID field indicates the bus on which the message occurred. ​ the Chapter 10 standard. The uBusID field indicates the bus on which the message occurred. ​
-Bus identification can be found in the Chapter 10 standard. The layout of a complete 16PP194  +Bus identification can be found in the Chapter 10 standard.  
-transaction is shown in Figure 6-30.  +
- +
 <​code> ​ <​code> ​
 struct SuSu16PP194_Word ​ struct SuSu16PP194_Word ​
Line 181: Line 176:
 </​b></​center></​html> ​ </​b></​center></​html> ​
  
 +The layout of a complete 16PP194 transaction is shown below. ​
 + 
 <​code> ​ <​code> ​
 struct Su16PP194_Transaction ​ struct Su16PP194_Transaction ​
Line 196: Line 193:
 16PP194 Transaction layout 16PP194 Transaction layout
 </​b></​center></​html> ​ </​b></​center></​html> ​
 +
 +----
  
 ==== Type 0x1B - 0x1F, MIL-STD-1553 Data, Format 3 - Format 7 ==== ==== Type 0x1B - 0x1F, MIL-STD-1553 Data, Format 3 - Format 7 ====
ch10_handbook/mil-std-1553_data.txt · Last modified: 2014/05/29 14:32 by bob