Home
Page
Other Topics
|
|
The
Jentech
Dual E can be configured to support four independent half duplex
interfaces or two independent full duplex interfaces in a single VMEbus
slot providing twice the number of interfaces per chassis when compared
with older NTDS products. These two interfaces independently provide the highest data
throughput and the lowest transfer latency for any of the products
currently available in the market. The Dual E board also
provides the capability to simultaneously drive four AEGIS clocks from a single board.
The same number of Type E interfaces provided by
Jentech use only 1/2 of the chassis space of other NTDS products,
allowing easier expansion of existing systems, and eliminating the need
in many cases for a VMEbus repeater card and additional chassis.
Smaller chassis systems can be used in areas where space considerations
are important. The use of low voltage (3.3v) and ultra-low voltage
(2.5v) components allows the Dual E board to be clocked at much higher
rates, producing the high performance needed to support two interfaces
while still maintaining low power consumption, low noise and minimal
heat dissipation and cooling requirements. Use of FLASH memory on
the Dual E board allows on-board storage of all the firmware and data
needed to reconfigure the board “on-the-fly” for any combination of
operating modes as listed below:
a) |
Up to 2 full duplex interfaces simultaneously |
b) |
Up to 4 half duplex interfaces simultaneously |
c) |
One full duplex
interface and up to 2 half-duplex interfaces simultaneously |
This simple reconfiguration capability also
minimizes the need for spare boards, since a single Dual E board can be
used to replace multiple full or half duplex interface boards.
Much of the hardware and software resources on the
Dual E board are dedicated to giving this product the “look and
feel” of two separate boards. This allows for a true 2-for-1
replacement and helps to provide a seamless transition from older
products. In the past, two boards were synonymous with two
interfaces, but with the advent of the Jentech Dual E board this is no
longer the case. Multiple independent interfaces can now be
supported with a single board product. The independent nature of
these interfaces is supported in part by the features listed below:
FOR USER INSTRUCTION PROCESSING:
- |
2 user command registers (CARs) and associated command chains, one for
each interface |
- |
2 Real-time Clocks (RTCs), one for each interface |
- |
2 Status Registers, one for each interface |
- |
2 sets of I/O chains (IN, OUT, EI, EF), four I/O chains per
interface |
FOR VMEbus HANDLING:
- |
2 VMEbus requester modules, one for each interface |
- |
2 sets of VME request levels(0 - 3), one of four levels separately
selectable for each I/F |
- |
2 sets of VME interrupt levels(1-7), one of seven levels separately
selectable for each I/F |
- |
2 separate 32-bit VME Interrupt Acknowledge Vectors, one for each
interface |
- |
2 separate 32-bit VME Interrupt Request Status Registers, one for each
interface |
- |
8 VME DMA I/O channels, four DMA channels per interface |
- |
Fair mode .v. Prioritized bus request type, each interface separately
selectable |
- |
VME64 Block Mode .v. Standard Mode, each interface separately selectable |
- |
Master .v. Slave Mode, each interface separately selectable |
- |
High Speed Bus controller, provides fast bus acquisition and efficient
use of bandwidth |
FOR NTDS DATA:
- |
3 DSP processors, one for each interface and one for non-NTDS processing |
- |
2 NTDS FPGAs, one for each interface |
- |
2 sets of NTDS I/O buffers (IN, OUT, EI, EF), four per interface |
- |
4 NTDS transceivers, two for each full duplex I/F or one for each half
duplex I/F |
- |
4 sets of analog hardware, two for each full duplex I/F or one for each
half duplex I/F |
- |
4 triax connectors, two for each full duplex I/F or one for each half
duplex I/F |
- |
NTDS interface protocols (SIF, parity, burst), each interface separately
configurable |
A row of LEDs viewable from the front panel report
back GO-NOGO status independently for each of the two Type E interfaces
supported.
Home
Page
Other Topics
|