User manual

5 Detailed descriptions of the eldbus coupler | Modbus TCP eldbus coupler UR20-FBC-MOD-TCP
68 1432790000/08/12.2015Manual u-remote
0x1018 – 0x101B Collective diagnostics message for I/O
modules
If a diagnostic alarm is activated (register 0x1134) and there
is a diagnostic message for a module, it is indicated here
with a set bit. A module’s slot position corresponds to its
position in the 64-bit data eld (minus passive modules with-
out slot recognition). Example: 0x0000 0000 0000 0002 =
There is a diagnostic alarm for module 2.
Reading the module’s diagnostic memory (0xAXXX) con-
rms the diagnosis and resets the corresponding bit. In
case of multiple diagnoses for one module, only the most
up-to-date diagnosis is displayed. The next diagnostic is then
placed in a wait loop and only becomes active once the cur-
rent one has been conrmed.
0x101C – 0x101F Collective process alarm message for the
I/O modules
If a process alarm is activated (register 0x1133) and there
is an alarm for a module, this is indicated here with a set bit.
A module’s slot position corresponds to its position in the
64-bit data eld (minus passive modules without slot rec-
ognition). Example: 0x0000 0000 0000 0002 = There is a
process alarm for module 2.
Reading the module’s process alarm memory (0xBXXX)
conrms the alarm and resets the corresponding bit. In case
of multiple process alarms for one module, only the latest
alarm is displayed. The next alarm is then placed in a wait
loop and only becomes active once the current one has been
conrmed.
0x1028 – 0x102F Module status
The module status (2 bits per module) of each detected
module is displayed in the corresponding bit position of the
128bits.
00 Valid data from this module
01 Invalid data, faulty module
10 Invalid data, incorrect module
11 Invalid data, missing module
There is no differentiation between fully functional modules
and empty slots (both status “0 0”). Please check the refer-
ence list (0x1132) or read the number of entries in the cur-
rent module list (0x27FE) to make sure that all modules have
been detected.
0x1030 MODBUS DATA EXCHANGE watchdog, current
time
Amount of time (input value
*
10ms) still remaining on the
active watchdog to monitor the exchange of process data.
If a 0 is read, the watchdog has expired and must be re-
started.
If 0xFFFF is read, the watchdog is deactivated.
0x1120 Status Modbus watchdog, predened time
In this register, the watchdog is activated/deactivated and
the watchdog time is set. Process data can be exchanged
as long as the watchdog is deactivated or it is activated and
still running. But it is accepted only after a watchdog reset
to the current time. The length is calculated with the input
value
*
10ms. Entering 0 deactivates the watchdog.
0x1121 Data exchange Modbus watchdog
Reset Register
If Bit 0 in this register is set, the predened time is loaded
into the watchdog time (watchdog reset). To continue the
process data exchange with activated watchdog this bit has
to be set during each watchdog cycle within the dened
time.
If Bit 8 in this register is set, an expired watchdog (value 0 in
register 0x1030) is reactivated.
0x1122 Lock force mode on web server
In default setting the force mode can be enabled via the web
server (after Login). The force mode can be locked by writ-
ing the double word „LOCK“ (0x4C4F, 0x434B). Writing of
„FREE“ (0x4652, 0x4545) will unlock the force mode again.