ibaLink-VME
Manual
Issue 1.8
7
2
Introduction
The ibaLink-VME interface card is a multi-purpose, bidirectional interface card designed
for use in VMEbus compatible PLCs and computer systems. It may be used for data
acquisition and process monitoring purposes as well as in control system applications,
such as the ibaLogic SoftPLC.
ibaLink-VME is the successor of the ibaLink-SM-128V-i-2o card (also called here SM128)
and completely compatible with the previous functions in 3Mbit mode. In addition ibaLink-
VME offers new functions using the ibaNet protocols 32Mbit and 32Mbit Flex.
Key features of the card include:
1 bidirectional fiber-optic link for inputs/outputs (channel 1)
1 unidirectional fiber-optic link for outputs (channel 2)
ibaNet protocols 3Mbit, 32Mbit and 32Mbit Flex
Flexible data selection and rate setting with 32Mbit Flex
Cascading of up to 15 devices in 32Mbit Flex mode at channel 1
Compatible interface for all ibaFOB cards
Compatible process i/o interface for ibaPADU-8-IO series and ibaNet750-BM series
Block coherent mode
Data exchange between 2 systems in Peer-to-Peer mode (P2P)
The ibaLink-VME can be used in both VME32 and VME64 systems (6U height). 5 V
power supply is required (from VMEbus).
VME specification according to ANSI VITA 1-1994:
Supported addressing modes:
A24
,
A32
,
A40
,
A64
Supported data transfers: 8/16/32 bit (
D08
/
D16
/
D32
/
MD32
)
8/16/32 bit block transfer modes are supported (
BLT
)
64 bit block transfer mode is supported (
MBLT
)
Support for unaligned transfers (
UAT
) and read-modify-write (
RMW
)
The following modes are not supported:
Auto configuration (AutoSlotID)
2eVME/2eSST
The ibaLink-VME is a passive slave board on the VMEbus, i.e. no active master access
on the VMEbus will be performed. The board occupies a 256 kByte address space on
the VMEbus.
Coherent mode
The exchange of VME and fiber optic data happens asynchronously from each other.
This means that blocks of data that are written on the VME side are not necessarily
transported over the fiber optic telegram as one block. There is only some coherence
guaranteed based on the type of write access that was used (byte, word or dword).
