Does the SP’ACE include a mechanism to ensure against the possibility of a “babbling terminal”?
A. In compliance with MIL-STD-1553B, the SP’ACE and all of our other 1553 products include a transmitter timeout circuit. That is, they include a circuit that operates independently from the encoder/transmitter to automatically shut down the transmitter if it attempts to transmit longer than the longest allowable transmission time of 660 µs. For the SP’ACE, the timeout value is 668 µs. If the transmitter timer (sometimes called a watchdog timer) times out, it will: (1) shut down the Manchester encoder circuit; and (2) bring the TX_INH (transmit inhibit) inputs to the CH. A or CH. B transmitter to logic “1”, which shuts down the 1553 transmitter. Q. We have an application for the BU-61582 SP’ACE, involving both RT and Monitor modes. When the SP’ACE is in Monitor mode, we need very high assurance that the SP’ACE will never attempt to transmit on the 1553 bus. What do you suggest? A. The recommended configuration is for us to supply you with a version of the BU-61582 SP’ACE product that i
Related Questions
- If a customer checks the "Response Requested" block is there any mechanism in place to ensure that the customer leaves contact information for the service provider?
- Since GSA has no direct access to an agencys Task Orders, what mechanism does GSA have to ensure contractors are accurately reporting their 03FAC task orders?
- What is the locking mechanism employed to ensure users do not modify each others data?
