Talk:MIL-STD-1553

message: Thanks for adding the links --redstucco 09:29, 1 December 2005 (UTC)
thread_title: Untitled

message: Could the author take a look and fix it up?
"Messages consists of one or more 16-bit words (command, data or status)...."
I believe this section needs to have some ambiguity removed.
The "message" consists of 20 bit times:  three bit/clock times for sychronization and to indicate of the type of word contained in the data bit times (command, data, or status), followed by sixteen  bit/clock times for a 16 bit word, and finally a parity bit.
 
The first three bit times are the only ones allowed to hold a constant voltage level for one and one half bit times.   The voltage transition in the middle of the first three bit times (1½ clock clycles)starts the timing for self synchonization of the data bits at the receiving end.  The direction of transition (low to high) or (high to low) indicates the type of word to follow (command, data, or status).  
The remaining 17 bits are required to make a voltage transition within one bit/clock time.  If there is a change in a data bit from one to zero (10) or vice versa (01), the transition between polarities happens in the middle of the bit time.  If a one is followed by a one (11), or if a zero is followed by a zero (00), the transition happens at the biggining of the bit time. 
The direction of the voltage transition (high to low or low to high) durring the last 17 bit times is a function of the current bit value and the preceeding bit.  The initial voltage transition direction is a function of the last transition of the sychronization signal and the value of the first bit. 
If the transmitted data stays all zeros (0000000000000000) or all ones (1111111111111111), the resulting signal durring the 16 bit/clock times will be a square wave that is the same frequency as the clock (a full cycle in each bit time).  A data pattern of alternating ones and zeros (1010101010101010) or (0101010101010101) will produce a square wave one half the clock frequency. 
The parity bit follows the same rules as the data bits.
This can be better understood by a carefull reading of MIL-STD-1553B or by seeing the diagram under Manchester line code[] here[[http://upload.wikimedia.org/wikipedia/commons/thumb/9/90/Manchester_encoding_both_conventions.svg/650px-Manchester_encoding_both_conventions.svg.png. 
]]
207.5.226.145 01:59, 6 January 2007 (UTC)
replies: text: I've replaced the offending image with Figure 1 from the standard, and ammended the text to suit. This article still needs loads of work, though. Graham.Fountain | Talk 10:37, 20 May 2012 (UTC)
thread_title:  Bus controller paragraph is jumbled up 

message: Would like to see something on 1553C.  —Preceding unsigned comment added by 192.91.173.36 (talk) 20:27, 17 July 2008 (UTC)
thread_title:  1553C (1553B Notice 5) 

message: Refer to the following snipits from the Bus Protocol section:
Issue #1
...This means during the RT to RT transfer, communication is done via the Bus Controller. The data is first written into the buffer of the RT who initiates the communication (e.g. RT1). The Bus controller reads the data from the RT1 buffer and writes it into the destination RT buffer (RT2).
...and...
5. RT to RT Transfer. The Bus Controller sends out a Receive data command followed by a Transmit data command. The transmitting Terminal sends a Status Word followed by 1 to 32 data words to the Receiving RT. The receiving Terminal then sends its Status Word. 
   The first paragraph indicates that RTs can never talk directly to each other.  The second section (#5) indicates that as long as the BC initiates the transfer between two RTs, the data is transferred directly from RT1 to RT2.
Which is it?  — Preceding unsigned comment added by 98.233.45.116 (talk) 20:13, 30 September 2011 (UTC)
thread_title:  Conflict in Bus Protocol section 

message: as now
http://en.wikipedia.org/wiki/STANAG_3910
redirect to MIL-STD-1553, suggesting this is the same as
http://en.wikipedia.org/wiki/MIL-STD-1773#Physical_layer
but the two optical standards are not the same.
I.E. EfaBus/STANAG_3910 20 Mbps optical bus is different than MIL-STD-1773
Probably need a dedicated article like in .de Wiki:
http://de.wikipedia.org/wiki/Stanag_3910  — Preceding unsigned comment added by Efa (talk • contribs) 09:08, 10 May 2012 (UTC)
replies: text: How can we break the redirection?--Efa (talk) 09:58, 14 May 2012 (UTC)
thread_title:  Stanag 3910 

message: Hello fellow Wikipedians,
I have just added archive links to  on MIL-STD-1553. Please take a moment to review my edit. If necessary, add  after the link to keep me from modifying it. Alternatively, you can add  to keep me off the page altogether. I made the following changes:
*Added archive https://web.archive.org/20130313162407/http://www.saabgroup.com:80/en/Air/Gripen-Fighter-System/Gripen/Gripen/Technical-specifications/ to http://www.saabgroup.com/en/Air/Gripen-Fighter-System/Gripen/Gripen/Technical-specifications/
*Added archive https://web.archive.org/20090206112407/http://assist.daps.dla.mil:80/quicksearch/basic_profile.cfm?ident_number=275874 to http://assist.daps.dla.mil/quicksearch/basic_profile.cfm?ident_number=275874
When you have finished reviewing my changes, please set the checked parameter below to true to let others know.
Cheers.—cyberbot IITalk to my owner:Online 05:23, 10 January 2016 (UTC)
thread_title:  External links modified 

message: Hello fellow Wikipedians,
I have just added archive links to  on MIL-STD-1553. Please take a moment to review my edit. If necessary, add  after the link to keep me from modifying it. Alternatively, you can add  to keep me off the page altogether. I made the following changes:
*Added archive http://web.archive.org/web/20090206112407/http://assist.daps.dla.mil:80/quicksearch/basic_profile.cfm?ident_number=275874 to http://assist.daps.dla.mil/quicksearch/basic_profile.cfm?ident_number=275874
*Added archive http://web.archive.org/web/20120205092101/http://assist.daps.dla.mil/quicksearch/basic_profile.cfm?ident_number=36973 to https://assist.daps.dla.mil/quicksearch/basic_profile.cfm?ident_number=36973
When you have finished reviewing my changes, please set the checked parameter below to true or failed to let others know (documentation at ).
Cheers.—cyberbot IITalk to my owner:Online 00:46, 29 February 2016 (UTC)
thread_title:  External links modified 

message: Hello fellow Wikipedians,
I have just added archive links to  on MIL-STD-1553. Please take a moment to review my edit. If necessary, add  after the link to keep me from modifying it. Alternatively, you can add  to keep me off the page altogether. I made the following changes:
*Added archive http://web.archive.org/web/20090206112407/http://assist.daps.dla.mil:80/quicksearch/basic_profile.cfm?ident_number=275874 to http://assist.daps.dla.mil/quicksearch/basic_profile.cfm?ident_number=275874
When you have finished reviewing my changes, please set the checked parameter below to true or failed to let others know (documentation at ).
Cheers.—cyberbot IITalk to my owner:Online 02:30, 21 March 2016 (UTC)
thread_title:  External links modified 

message: Hello fellow Wikipedians,
I have just modified one external link on MIL-STD-1553. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
*Added archive https://web.archive.org/web/20140714174407/http://www.adas.fr/cartes-digibusus.htm to http://www.adas.fr/cartes-digibusus.htm
When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.
Cheers.—InternetArchiveBot (Report bug) 16:32, 10 January 2018 (UTC)
thread_title:  External links modified