🚀 go-pugleaf

 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.