From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,49dfdc6354253834
X-Google-Attributes: gid103376,public
From: "David C. Hoos, Sr." <david.c.hoos.sr@ada95.com>
Subject: Re: Mil-std 1553
Date: 1999/04/10
Message-ID: <TmXapl1g#GA.220@pet.hiwaay.net>#1/1
X-Deja-AN: 464790389
Content-Transfer-Encoding: 7bit
References: <7encug$d1e$1@nnrp1.dejanews.com>
Content-Type: text/plain; charset="iso-8859-1"
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
MIME-Version: 1.0
Newsgroups: comp.lang.ada
Date: 1999-04-10T00:00:00+00:00
List-Id: <comp.lang.ada>


imohammed@mailexcite.com wrote in message
<7encug$d1e$1@nnrp1.dejanews.com>...
>I am trying to write driver for 1553 for VxWorks system.  I was wondering
if
>there is any book or paper available that could be helpful.
>
The first place to consult would be the documentation for the interface
hardware.

This would allow you to write a low-level driver.

But, then, in any system using MIL-STD-1553, there is certain to be some
sort of messaging protocol to be implemented at a higher level to
abstract away the messaging details.