User manual

5 Detailed descriptions of the eldbus coupler | Modbus TCP eldbus coupler UR20-FBC-MOD-TCP
71Manual u-remote1432790000/08/12.2015
0x2800 – 0x287F Reference list
Each module identier is made up of 4 bytes (2 registers)
(see the overview of module IDs on page 66). If a 1 is set in
register 1132, the reference list must be identical to the cur-
rent module list before the data exchange can begin.
0x2A00 – 0x2A7F Current module list
Each module identier is made up of 4 bytes (2 registers)
(see the Overview of module IDs). The modules that were
connected when the coupler was started are entered here.
To simplify conguration, the current module list can be cop-
ied into the reference list.
0x2B00 – 0x2B7F Module offsets of process data
For each module there are two registers reserved to indicate
the offset between the start address within the packed pro-
cess data and the address 0x0000: The rst register indi-
cates the bit-offset of the outputs, the second one indicates
the bit-offset of the inputs. Thus, it is possible to use these
information directly for the access to coils or Descrete Inputs.
Converting the address syntax is necessary for a register-
wise access (see table “Implemented modbus functions”).
In case there are no outputs or inputs, the register entry is
0xFFFF.
Example: For an arrangement of coupler,
UR20-4AI-RTD-DIAG, UR20-1CNT-100-1DO, UR20-16DO-P
the six registers 0x2B00 to 0x2B05 deliver the values
0xFFFF 0x0000 | 0x8000 0x0040 | 0x8050 0xFFFF.
Since the rst module has not outputs and the last mod-
ule has no inputs, the entry of the respective registers is
0xFFFF. The value 0x8050 indicates that the access to the
rst output of the UR20-16DO-P can be realised via address
0x8050, bit0. The value 0x0040 indicates, that the rst
input of the UR20-1CNT-100-1DO is accessible via the ad-
dress 0x0040, bit0.
0x8000 – 0x87FF Process data inputs
For each module a data length of 64 bytes (32 registers) is
reserved.
Example: Module 3 starts at address 0x8040.
0x9000 – 0x97FF Process data outputs
For each module a data length of 64 bytes (32 registers) is
reserved.
Example: Module 3 starts at address 0x9040.
0xA000 – 0xA7FF Diagnostics
For each module a diagnostics data length of 64 bytes (32
registers) is reserved.
Example: Module 3 starts at address 0xA040.
In case of a diagnostics message, the 47 bytes of the mod-
ule diagnosis are entered here from the corresponding tables
(see the table of diagnostic data in the corresponding mod-
ule description in the module chapter).
If a 1 is set in register 0x1134, reading out the correspond-
ing diagnosis results in a conrmation of the alarm.
0xB000 – 0xB7FF Prozess alarms
For each module a process alarm data length of 64 bytes (32
registers) is reserved.
Example: Module 3 starts at address 0xB040.
In case of a process alarm, the 4 bytes of the module are
entered here from the corresponding table (see the table of
process alarms in the corresponding module description in
the module chapter).
0xC000 –0xC7FF Parameters (Firmware version 01.xx.xx)
For each module a parameter data length of 32 registers is
reserved. The modules can be parameterised via the web
server (s.Chapter10).
0xC000 –0xFFFF Parameters (Firmware version 02.00.00
or higher)
For each module a parameter data length of 256 registers is
reserved. Example: Module 3 starts with address 0xC200.
The modules can be parameterised via the web server
(s.Chapter10) or via the Modbus master.
One register is assigned to each module parameter with a
size of max. 16 bit. 32bit parameters use two subsequent
registers (consider Motorola format!). The sequence of
parameters as well as the optional values are listed in the
parameter tables of the individual module descriptions (s.
Chapter6).
Example: Parameter 8 of module 3 has the address 0xC207
(provided that there is no 32 bit parameter prior to it in the
same module).
Examples for 32 bit parameters are “Period duration“ of the
pulse width modulation modules and „End value“ of the
counter modules.