The architecture of this range of PCI cards enables a user to quickly design modules
to suite any data acquisition requirement. There are two base card formats. The half
length PCI interface card accommodates up to two user installable modules. The full
length PCI interface card can accommodate up to four user installable modules.
Each module is supported on the base card by eight 4-byte wide cyclic memory buffers.
Each cyclic buffer is 1024 words (4-byte) deep. Typical modules available from Sycos
include interfaces to ARINC-429. Each module can be designed to support up to 8 Receive
or 8 Transmit channels.
The base card has been designed to provide configuration registers that allow the
- Automatically identify the base card and its revision status
- Automatically identify which, if any, modules are fitted to the base card and their
- Identify connector cables connected to the card
- Assign address space for the card's data buffer memory and registers. (Plug-in
- Control and monitor the PCI bus interface to the card
- Read card interrupt configuration as assigned by the POST software as it initialises
and configures the system
The base card design supports the resident interface modules with:
- Up to 32 Cyclic Data Buffers, each with a capacity for 1k x 4 byte words
- Each module may have up to 8 channels, each with its own Cyclic Data Buffer
- Direct access to the Cyclic Data Buffer Read / Write Pointers
- PCI interrupts on Module Events
- Direct access to Module registers and application memory
- Interface compatible with PCI Local bus Specification, revision 2.1, June 1995
The card is designed to be used in a "Plug-in and Play" environment which is made
possible, not only by the choice of PCI interface, but also by the provision of various
identification and module present registers. These include:
- Device ID
- Vendor ID
- Subsystem ID
- Subsystem Vendor ID
- Module Present
- Connector ID / Present
- Module ID
Using these registers the host can detect the presence of the card, its resident
modules and its connector, determine if this is consistent with system requirements
and respond accordingly by configuring the system or reporting system deficiencies.
The cards do not require any specific hardware configuration other than fitting the
correct modules and connectors. Any errors in the fitting of Modules and connectors
can easily be detected by the software and appropriate warnings reported.