Table of Contents
Advertisement
6.5.4
Accessing the parameter data
With the first start-up modules, which were parameterizable, operate with their default parameters.
If you want to change parameters the Ethernet coupler respectively the corresponding modules may
be parameterized via the integrated web server, see 6.4.1 Web server, p. 40.
Here by means of the corresponding Modbus/TCP-Slot parameter may be viewed and changed.
Parametrization is only possible in the Commissioning state.
NOTICE
More information: 6.2 Operating modes, p. 37.
6.5.5
Accessing diagnostics data
If configured ricos FLEX modules provide interrupt data on failure.
As soon as one or more modules report an interrupt, the interrupt data of the appropriate slot loca-
tion is received and acknowledged by the Ethernet coupler. After that the bit assigned to the Mod-
bus/TCP Slot is set in the internal alarm information image and the corresponding interrupt data are
stored.
Please note that automatic acknowledgement (AutoAcknowledge) is always activated in the Ether-
NOTICE
net coupler. This means that received interrupts are immediately acknowledged by the ricos FLEX
bus. This can overwrite older interrupt data of the same module.
Here you have to ensure a corresponding temporary storage.
In ricos FLEX we distinguish between hardware interrupt and diagnostic interrupt.
To distinguish there is a 64bit wide field (bit 0 = Modbus/TCP Slot 1 to bit 63 = Modbus/TCP Slot 64)
in the diagnostic image each for hardware and diagnostics interrupt. Then for each slot 16byte hard-
ware interrupt data or 32byte diagnostics interrupt data are following.
To acknowledge the diagnostics and hardware interrupt status may be write accessed. The alarm
data may only be read.
Address
4001h ... 4040h
4001h ... 4200h
4001h ... 4008h
4009h ... 4010h
41F8h ... 4200h
5001h ... 5040h
5001h ... 5400h
5001h ... 5010h
5011h ... 5020h
53F0h ... 5400h
Wieland Electric GmbH | BA001269 | 09/2021 (Rev. A)
Function code
Access
01h
Bit access to hardware interrupt state:
02h
4001h: Hardware interrupt state Modbus/TCP Slot 1
05h
...
4040h: Hardware interrupt state Modbus/TCP Slot 64
04h
Word access to hardware interrupt data 4001h ... 4008h:
17h
Modbus/TCP Slot 1
0Fh
...
41F8h ... 4200h: Modbus/TCP Slot 64
04h
16byte hardware interrupt data Modbus/TCP Slot 1
04h
16byte hardware interrupt data Modbus/TCP Slot 2
04h
16byte hardware interrupt data Modbus/TCP Slot 64
01h
Bit access to diagnostics interrupt state:
02h
5001h: Diagnostics interrupt state Modbus/TCP Slot 1
05h
...
5040h: Diagnostics interrupt state Modbus/TCP Slot 64
04h
Word access to diagnostics interrupt state:
17h
5001h ... 5010h: Diagnostics interrupt state Modbus/TCP
0Fh
Slot 1
...
53F0h ... 5400h: Diagnostics interrupt state Modbus/TCP
Slot 64
04h
32 byte diagnostics data from Modbus/TCP Slot 1
04h
32 byte diagnostics data from Modbus/TCP Slot 2
04h
32 byte diagnostics data from Modbus/TCP Slot 64
Deployment
48
Advertisement
Table of Contents
