[sci.electronics] MIL-STD 1553 specs anyone?

dale@lamont.ldgo.columbia.edu (dale chayes) (11/13/90)

Can anyone point me to the specifications for the MIL-STD-1553 
interface? I've run across references to it in the data sheets
for the Harris Manchester encoder/decoder data sheets (Harris
1989 Digital Product Databook (Military.))

Specifically, I'm looking at the HD-6409 and the HD-15530/31 parts
but not for a military application. They were suggested to me for
use in the data link for a bore hole geophysical logging tool.

I'd also be interested in design/application experience with Manchester
encoded data links/telemetery systems.  Also pointers to other 
manufacturers Manchester encoders would be appreciated.

Thanks in advance,
Dale

-- 
Dale Chayes Lamont-Doherty Geological Observatory of Columbia University
Route 9W, Palisades, N.Y.  10964	dale@lamont.ldgo.columbia.edu
voice:	(914) 359-2900 extension 434	fax: (914) 359-6817

jws@thumper.mlb.semi.harris.com (James W. Swonger) (11/13/90)

 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, <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.