The Abaco Systems / SBS / Bit 3 Model 85154556 A32/D32 VMEbus Adapter connects two VMEbus systems to enable high-speed inter-system data sharing and resource access. This adapter allows each connected system to directly address resources on the remote VMEbus as local memory, facilitating transparent data, I/O command, and interrupt transfer between chassis. The adapter supports random access reads and writes to the remote bus, enabling one system to operate as a coprocessor or primary bus controller in the peer chassis.
Technical Specifications
• Model Number: 85154556 (Related Part Numbers: 85154538, BIOS Part Number 85154596)
• Manufacturer: Abaco Systems / SBS / Bit 3
• Primary Function: VMEbus-to-VMEbus interconnection adapter
• Address Support: A32/D32 addressing; compatible with A16, A24, A32, A64 addressing modes
• Data Transfer Modes: D32 data width; supports D8, D16, D32, D64 data sizes
• Transfer Types: Block Transfer (BLT), Read-Modify-Write (RMW), Unaligned Address Transfer (UAT)
• Bus Arbitration: SGL, PRI, RRS arbiters supported
• Release Types: ROAK, ROR, RORA, RWD
• Standards Compliance: VME-32 and VME-64
• Data Integrity: Parity protection on address, control, and data lines
• Form Factor: 6U VMEbus module
• Shipping Weight: ~3 lbs
– Key Features
• Random access read/write cycles to remote VMEbus resources
• Transparent inter-system addressing without protocol conversion
• Direct data, command, and interrupt transfer between VMEbus domains
• Dual-role operation: coprocessor or bus controller configuration
• Parity-protected address, control, and data integrity
– Typical Applications
• Multi-chassis VMEbus system integration
• Distributed computing architectures with shared memory access
• Coprocessor and controller configurations in VME-based platforms
• System expansion requiring inter-VMEbus resource sharing
– Compatibility & Integration
The adapter integrates with additional interconnect adapters to support star and daisy-chain topologies across multiple VMEbus systems. Compatible with systems requiring VME-32 and VME-64 compliance.
