4x50 EtherNetIP.190129.1v4: User manual
WWW.EILERSEN.COM
Version: 2020-11-24, rev.: 1v4
Page: 8
3.1.2 Input data (LcSignal, Normal operation, AS=0)
This chapter describes the input data when the
Actual Value Selector
(
AS
) is
set to
0
during normal operation.
The 26 input data bytes (from the 4x50 unit) are structured like this:
Lc
Register
Lc
Status(0)
Lc
Data(0)
Lc
Status(3)
Lc
Data(3)
0
1
2
3
4 5 6 7
20
21
22 23 24 25
LcRegister
is a word (two bytes) that constitutes a bit register for indication
of expected load cells. Hence bit 0-3 will be ON, if the corresponding load cell
address (LC1-LC4) was expected to be connected.
LcRegister
is always trans-
ferred in
16 bit unsigned integer
format.
In addition the
LcRegister
also contains the
Actual Value Selector
(
AS
) as
previously described above in the
. The
AS
is located in the
same bit positions (bit 8-11) in the input data as in the output data.
Furthermore bit 15 will be always ON, while bit 14 will toggle ON and OFF with
1hz (=500ms ON, 500ms OFF).
LcStatus(X)
is a word (two bytes) that constitute a register containing the
actual status for load cell
X
.
LcStatus(X)
is always transferred in
16 bit un-
signed integer
format. During normal operation this register will be 0, but if
an error occurs some bits in the register will be set resulting in an error code.
A description of the different error codes can be found in
LcData(X)
is a double word (four bytes) constituting a register, which during
normal operation (
AS
=0) contains the
LcSignal(X)
. The
LcSignal(X)
is the
actual weight signal from load cell
X
in
32 bit signed integer
format. Note
that the
LcSignal(X)
value is only valid if the corresponding
LcStatus(X)
register is 0 indicating no error present. Also note the
LcSignal(x)
transferred
during normal operation is filtered and scaled using the selected DIP switch
settings (
SWE
) as described below.
Since only status and weight for the load cells are transmitted in the telegram,
functions such as status handling, calculation of system weight(s), zeroing and
calibration
must
be implemented on the EtherNetIP master. Please refer to
for an explanation on how this typically can be
done.
