SCDCT2577 REV D 2
GENERAL DESCRIPTION
CT2577 provides the complete protocol for both Remote
Terminal and Bus Controller, supporting all types of message
transfers including all 15 mode codes, with comprehensive
error checking. Error handling of data is not required by the
subsystem.
The low power transceivers are capable of providing the output
voltage required by MIL-STD-1760 and are powered by a +5V
supply.
If sinusoidal (McAir) transceivers are required then the part
number becomes CT2579 This is the only difference between
CT2577 and CT2579
The user interface is pin selectable between 8 and 16 bit for
both VME and MULTIBUS. Addresses are referred to in
hexadecimal format and five bit address fields for simplicity in
correlating to the MIL-STD-1553 commands.
The device contains 3K words of main memory (1K receive,
1K transmit, and 1K broadcast receive).
A FIFO type memory is also provided for storing up to 32
command words (RT) or 32 status responses (BC). Access to
this memory is achieved by reading from location 0 00 00.
Discrete signals are provided to indicate the memory status (i.e.
full or empty). To reduce the processor intervention, the
command / status memory will only store commands that have
associated data.
A 32 word data buffer memory is used to store messages until
validation is complete. Only validated messages are written to
the main memory in a single burst. Data to be transmitted is
transferred from the main RAM to this buffer memory in a
single burst.
An optional 32 word BTL memory buffers the main memory to
the subsystem. This memory ensures data consistency by
“bursting” a message from the BTL memory to the main
memory (write) or from main memory to BTL memory (read)
uninterrupted after which the subsystem has access to this
memory at its leisure. This memory is not used for mode
commands as there is a maximum of only one associated data
word and data inconsistency cannot occur. The BTL memory
may be disabled by hardware or software.
Arbitration between the 1553 data bus and the processor bus is
fully automatic. When the main memory is required to be
accessed by the 1553 data bus, any current subsystem access to
the main RAM is completed first, thus ensuring no data is lost
or corrupted. The time the main memory is accessed by the
1553 data bus equates to 8.5 µS for command or status words,
plus 1 µS (transmit) or 500 nS (receive) for each data word.
The device has an optional RT wrap around capability. When
WRAPEN is active, data received at subaddress 1E (30)
remains stored in the data buffer memory (i.e. not transferred to
main memory). If followed by a transmit from subaddress 1E
the same data will be transmitted.
A self test feature can be enabled by the subsystem in software.
This function will initially set the device to be a Bus Controller
and transmit a message.
This message is received by the Remote Terminal via the
transceivers (online) or bypass the transceivers (offline). The
data and command transmitted by the Bus Controller can be
read back from the Remote Terminal by the subsystem.
There is an option within the device to reduce the response
time in order to conform to other standards such as 1553A and
McAir. In this mode subaddress 1F is allocated a normal
subaddress for both Remote Terminal and Bus Controller with
subaddress 00 being the only subaddress reserved for mode
commands.
Any message may be illegalised by applying an active low on
the NME discrete status input. The Remote Terminal will
respond with the Message Error bit set in the status and not use
the information received.
Configuration as a Remote Terminal and Bus Controller is
achieved by writing to address 1 00 00 and 1 00 01
respectively. The device defaults to Remote Terminal on power
up reset. A discrete signal BCNRT is provided to indicate the
device mode. The option is available for the Remote Terminal
to switch to Bus Control via the mode code Dynamic Bus
Control.
In the Bus Control mode all commands transferred to the
device are error checked and only valid legal commands are
allowed to be transmitted onto the 1553 data bus, any errors are
reported back to the host. Messages received on the 1553 data
bus destined for the host will only be stored in the main
memory once they have been completely validated.
A hardware implementation of the 1760 checksum algorithm
within the device may be enabled for both Remote Terminal
and Bus Controller via signal NENCHK. When transmitting,
the checksum word is inserted in the last word position, and
when receiving, a valid checksum word will generate the signal
NVALCHK as well as an open drain output (STATUS). The
STATUS output may be hard wired to any of the discrete status
inputs (e.g. Service Request), if it is also hard wired to the
input NILLCMD the device will respond to a failed checksum
with the selected status bit set and not use the data (i.e. not
write to main memory).
In addition to the signal NVCR (valid command word
received) which may be used to illegalise commands, a signal
NHDR (header word received) is available to the subsystem for
verification of the 1760 message header.
The RT address lines may be continuously monitored or
latched on RESET as required by 1760. If all six RT address
lines go open circuit the store released signal (STREL) will go
high.
A signal is provided to monitor the internal watchdog timers
for test purposes. A set of pins are available to connect
additional external watchdog timers if so desired.
As well as being able to set the Remote Terminal status bits
discretely they may be written to via the VME/MULTIBUS
interface. These status bits as well as the status of the Block
Transfer Logic and Self Test function may be read back from
the device.
A software write / readable BIT register is available.