EA-IF-E2

Manufacturer Part NumberEA-IF-E2
DescriptionINTERFACE ETHERNET (EA-PSI/BCI800R)
ManufacturerEA ELEKTRO-AUTOMATIK
EA-IF-E2 datasheet
 


Specifications of EA-IF-E2

SvhcNo SVHC (18-Jun-2010)Accessory TypeInterface Card
ApplicationsEngineering Laboratory And Complex Industrial ApplicationApproval BodiesCE / EN
Rohs CompliantYesFor Use WithEA Elektro-Automatik PSU
Lead Free Status / RoHS StatusLead free / RoHS Compliant  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
Page 81
82
Page 82
83
Page 83
84
Page 84
85
Page 85
86
Page 86
87
Page 87
88
Page 88
89
Page 89
90
Page 90
91
92
93
94
95
96
97
98
99
100
101
102
Page 87/102

Download datasheet (2Mb)Embed
PrevNext
Programming
Example 3: Setting the pulse witdh for A (object 90) to 5s.
According to the table above the time range mask is 0x4000.
In combination with the resolution of 10ms for this time range,
a value of 500 (5s : 0.01s), in hex 0x1F4, results. The total
resulting time value then would be 0x41F4.
9.2.2 Tips
I. Detecting a device node (not with GPIB)
If you want to, for example, control a device via USB and
you don‘t know the device‘s node, you could for example
use the broadcast node 0 and query the device class. The
device or the devices will answer with its/their own device
node, that has/have been set at the device(s). The device
node(s) can be furthermore used to control and distinguish
the devices.
II. Remote and standby
The object 54 is used to either activate/deactive the remote
control operation or the input/output of a device. The object
can be used to activate both at once, but it is strongly not
recommended to do so, because setting the input/output re-
quires the remote control operation already being active and
thus would generate an error message. You should rather
activate remote control first with the corresponding bit set in
the control byte and then control the input/output by sending
object 54 a second time with a different control byte. When
deactivating remote control it simply goes vice versa.
It is also useful to read back the state of the device with object
70, in order to check if object 54 has been set correctly
9.2.3 Trouble-shooting
Problem:
The device does not react or respond to com-
mands
Possible causes with USB
• The USB card requires a driver. Check if the driver is in-
stalled correctly and if you can find the card in the Windows
device manager in the section of „USB controllers“.
• The USB driver can be used as genuine USB driver or it
can additionally create a virtual COM port for every USB
card that is connected to the PC, depending on the driver
config. So the USB device can also be used as a RS3
hardware. Using LabView, this only requires to replace the
USB.vi with the RS3.vi.
• The wrong device node (=address) is used to communicate
with the device.
Possible causes with RS232
• You are not using a 1:1 cable for the RS3 card.
• The wrong device node (=address) is used to communicate
with the device.
• Device and PC are configured to different baudrates etc.
• The communication cable is too long for the configured
baudrate (also see section .).
© 009, Elektro-Automatik GmbH & Co. KG
Possible causes with GPIB
• If multiple device are connected to a IEEE bus, one or more
device addresses might be double.
• A wrong syntax is used. For example, an electronic load
does not react to the command OUTP, because it features an
input. Or the command was not valid for the type of device
you tried to contact.
Possible causes with CAN:
• The wrong CAN ID is used. See section 4.3.1 for the cal-
culation of the correct CAN ID.
• Wrong baudrate set or wrong sample point selected (only
at PSI 9000, see user manual)
• The device is located at the end of the bus and is not
terminated
Problem:
Multiple queries were sent, but not all of them
were answered
Cause: The queries have been sent subsequently too fast.
Depending on the communication type and speed and the
execution time of the device, you need to include a certain
latency between two queries.
Rule of thumb: Latency = Transmission time + Execution time
The execution time lies at typ. 5-0ms, depending if there only
was a query or if something has to be set. The transmission
time can be calculated from the baudrate and number of bits
that are sent.
Problem:
Set values and status are not set
Possible causes
• The contacted device is not in remote control mode or
can‘t currently be set to this mode, because it might not
be allowed in this very moment or any other condition for
setting the device into remote control is not fulfilled (also
see section 9.)
• the sent values are wrong (too high, too low) or the stan-
dard value range (0...0x6400 for voltage, current etc.) is
additionally limited by limit values (only at PSI 9000). An
error message is sent in this case.
Problem:
An error message has been returned
Error messages are there to point to where the cause of the
error lies. The table below gives an overview about possible
error codes and their meanings, which can be returned from
the device to the PC. Some errors are caused by erroneous
queries/sendings, others might come unrequestedly from
the device. They serve as hint and for trouble-shooting
purposes.
Error messages are in telegram format, i.e. they are com-
posed of a start delimiter, object number (to identify an error,
0xFF is used as object number) and data field. The data field
contains the error code.
Example: in case you want to set the voltage with object
50 and the device is not in remote control mode, you would
receive the error message C0 07 FF
with device node 7.
EN
09
01 CF from a device
87