Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!rutgers!soleil!mlb.semi.harris.com!thumper.mlb.semi.harris.com!jws From: jws@thumper.mlb.semi.harris.com (James W. Swonger) Newsgroups: sci.electronics Subject: Re: MIL-STD 1553 specs anyone? Keywords: interface specification MIL-STD-1553 Message-ID: <1990Nov13.134540.13761@mlb.semi.harris.com> Date: 13 Nov 90 13:45:40 GMT References: <2938@lamont.ldgo.columbia.edu> Sender: news@mlb.semi.harris.com Organization: Harris Semiconductor, Melbourne FL Lines: 22 Nntp-Posting-Host: thumper.mlb.semi.harris.com MIL-STD-1553 is a government (military) document specifying in EXTREME detail the characteristics of the data communications standard - pysical, electrical, protocols, all that wonderful stuff. If you are just putting a data source down the hole, I think that the 1553 standard is massive overkill. A full 1553 implementation requires intelligence of some sort at both ends. A lot of handshaking and message passing goes on even to send one data word; like - I'm sending data, OK, send data, here comes the data, , did you get the data, yeah I got the data... If the data flow is one-way then a true 1553 controller will probably be disturbed by the lack of handshaking. There are also a number of bus activity protocols to be adhered to like time between messages, number of data words in a row, etc. If you're after just the encoding (I assume for error rejection mostly) then brewing up a link might not be so bad - but you can probably do as well with a simpler system unless you expect extreme noise.