EA-IF-R2 EA ELEKTRO-AUTOMATIK, EA-IF-R2 Datasheet - Page 83

• Manufacturer Part Number: EA-IF-R2
• Description: INTERFACE RS232 (EA-PSI/BCI 800 R)
• Manufacturer: EA ELEKTRO-AUTOMATIK

Specifications of EA-IF-R2

• Svhc: No SVHC (18-Jun-2010)
• Accessory Type: Interface Card
• 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

LabView support
© 009, Elektro-Automatik GmbH & Co. KG
Broadcast:
After every broadcast query all bus sharing units can only
answer consecutively. Depending on the bus system, the
baud rate and the number of units, as well as the extra bus
traffic the answers can be delayed more or less. The time is
not specifiable and can only be estimated by the formula bus
sharing units * response time at singlecast. In most cases
the response time will be shorter.
7.10 Message structure IF-G1
The message structure for the text based communication
via a GPIB card is described in section 4.5.7.
7.11 Message structure IF-E1
Via the Ethernet port, the network card is working only with
SCPI commands which are transmitted by VXI11 protocol.
They‘re described in section 4.5.8. Specialty is here that
there are two extra commands that can transport a telegram
in form of the object orientated communication protocol (also
called binary protocol), which we also use. Purpose of the
commands is send objects to the device which don‘t have an
equivalent in the SCPI language. Using the binary telegram
format, the user could for example control, load or save the
function manager feature of a PSI 9000 power supply. In
order to do so, the special commands SYST:DATA:SET and
SYST:DATA:REQ are used. They transport a binary telegram
of this structure:
DL, ON, DATA
Important! All bytes must be seperated by commas.
DATA
the device.
We basically differentiate between telegrams, that only send
values to the device (SYST:DATA:SET) and telegrams that
only request values from the device (SYST:DATA:REQ). See
command list in section 4.5.8.
When sending data to the device, the DL (data length) byte
defines the number of values of DATA. In case the number
of
error is returned.
When requesting something, DL defines the number of
bytes that are expected as response. This is required, be-
cause different device series have different objects (com-
mands). So the user has to take the DL of a certain object
from the object list and use it here. For object lists refer to
section 9.3.
A wrong data length will return an error. Example for the
data length: object 0 is about to be requested. According to
the object lists, object 0 is a string of max. 16 bytes. So the
DL must be 16.
The second value, ON, is the object number. This number
defines the target for the subsequent data. Together they
form a set command.
Via the USB port only the binary protocol (see sections 7.4
to 7.8 and 9.) can be used, like with the other digital cards
IF-U1 und IF-R1.
DATA
is only required when sending a value or values to
bytes does not match the number given by DL, an
7.11.1 Telegram examples
Example 1:
The byte sequence 0x4700 shall be transported to the device
as voltage set value. According to the object list, the voltage
set value for e.g. a PSI 9000 is object 50.
The resulting SCPI command may look like this:
SYST:DATA:SET,50,71,0
Alternatively, the values could be given as hexadecimal:
SYST:DATA:SET#H0,#H3,#H47,#H00
Example 2:
The actual values are going to be requested. This is done by
a request command (REQ). According to object list, object
71 will return the actual values by six bytes. The request
command must thus look like this:
SYST:DATA:REQ6,71
The device will then return six decimal bytes:
67,37,1,17,4,16
Two bytes form a 16 bit value, representing an actual value
in percentage. All six bytes, combined and in hexadecimal
format will turn out like this:
0x435, 0x157F, 0x1810
The order is defined, so the first value is the actual voltage,
the second one the actual current and the third one is the
actual power. For calculation of these percentage values into
real values refer to section 7.7.
EN
83