EA-IF-PB1 EA ELEKTRO-AUTOMATIK, EA-IF-PB1 Datasheet - Page 80

• Manufacturer Part Number: EA-IF-PB1
• Description: PSU, INTERFACE, PROFIBUS
• Manufacturer: EA ELEKTRO-AUTOMATIK

Specifications of EA-IF-PB1

• Accessory Type: Interface Cards
• Svhc: No SVHC (18-Jun-2010)
• Applications: Engineering Laboratory And Complex Industrial Application
• Approval Bodies: CE / EN
• Rohs Compliant: Yes
• For Use With: EA Elektro-Automatik PSU
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant

About the interface cards
© 009, Elektro-Automatik GmbH & Co. KG
Example: one slave device is connected in series to the
master and three additional slaves are connected in parallel
to that one slave. Those four devices in parallel have to be
set to  for the value
Also see the figure for another example:
Attention! The position serial=1/parallel=1 is dedicated
to the master and may not be set for a slave unit, which
won’t accept it anyway.
The SIO port also requires a termination if the slave unit is
at the end (one of the two ports is left blank). The termination
is set with this parameter:

= NO
= YES

bus terminate
={1..30}
parallel
Set the position of the device in the system.
serial
No termination.
The SIO is terminated.
and to 1...4 for the value parallel.
Default:
Default:
1
NO
7. Communication with the device
Section 7. does not relate to the text based communi-
cation with SCPI commands at the GPIB card IF-G1 or
the network card IF-E1!
7.1 Terms explained
Telegram: Chain of bytes with varying length. Is either sent
to or received from the device.
Singlecast: Query or simple message to a single unit. If
devices are linked in a chain, like for instance at CAN, this
telegram is received by all units, but only accepted by the
adressed one. Only related to CAN.
Broadcast: Query or simple message to all units. This
means any unit connected to the PC, no matter if by USB,
CAN or RS3, is receiving this message at once. Only
related to CAN.
Multicast: similiar to broadcast, but only for a certain group
of units, addressed by the relocatable identifier (RID). Only
related to CAN.
Object: with its properties it describes the object address
and initiates defined reactions at the target unit.
Message: CAN specific data packet
7.2 Prologue
The communication protocol with its object orientated tele-
gram structure is very complex. It is thus recommended to
use the ready-made LabView components. The integration
into other environments like Visual Basic, C or .NET requires
programming knowledge about the setup and use of hard-
ware interfaces like CAN or USB and the adressing of its
drivers. Here we only explain the structure of the data packet
(the telegram) and not how it is transmitted correctly.
7.3 General notes about the communication
The firmware of the different types of devices is programmed
to consider any circumstances, as far as possible, that may
occur when controlling multiple units at once. Thus it is not
always possible to perform any action at any time and any
state of the device. For example, the data of the function
manager of the series PSI 9000 (see user manual) are
only transmittable in standby state of the unit. Else an error
message would be returned, which is pointing the user to
the fact that the device is not in standby mode.
7.4 About the USB driver
The manufacturer of the USB chip on the IF-U1 card offers
two seperate drivers for Windows 98/ME, which are combi-
ned in one driver for Windows XP/2003/Vista. One of them
is a genuine USB driver, the other one creates a virtual serial
COM port (VCP) for every USB card that is connected. While
using LabView to create custom applications, you need to
choose which driver you want to install on Win98/ME. If the
VCP driver is used and thus the COM port, you need to place
the RS3 communication VI for the USB card. On Windows
XP/000/Vista systems you just need to decide, which dri-
ver to use and select the communication VIs accordingly. It
means is, either the RS3 VI or the USB VI.
By default, the VCP functionality of the combined driver is
enabled.
EN
80