Monitoring

The parameters for setting network monitoring functions are described below.
 
Parameter
Address
Name / setting range / [default setting]
Information
0x23B1:010
(P510.10)
Modbus -TCP/IP settings: Ethernet time-out
(MBTCP settings: Ethernet timeout)
0 ... [10] ... 65535 s
–
From version 04.00
 
Setting of the maximum permissible time-out of the TCP communication.
When the specified monitoring time has elapsed, the response set in 0x2859:007 (P515.07) is triggered in the inverter.
0x23B6:001
(P514.01)
Time-out monitoring: Time-out time
(MBTCP t-out mon: Time-out time)
0.0 ... [2.0] ... 300.0 s
–
From version 04.00
 
Monitoring is active if the first valid write command arrives at the Modbus client. Each further valid write/read message resets the watchdog timer.
Monitoring responds if within the time set here no valid message has been received by the Modbus client.
0x23B6:002
(P514.02)
Time-out monitoring: Keep alive time-out time
(MBTCP t-out mon: Keep al t-out)
0.0 ... [2.0] ... 300.0 s
–
From version 04.00
 
Monitoring is active after a valid value is written into the keep alive register 0x23B6:005 (P514.05) via the Modbus for the first time.
Keep alive monitoring responds if no value (range 1 ... 65535) has been written into the keep alive register within the time set here.
0x23B6:005
(P514.05)
Time-out monitoring: Keep alive register
(MBTCP t-out mon: Keep al register)
0 ... [0] ... 65535
–
From version 04.00
 
Time-out monitoring of the keep alive register is active after a value has been written into the keep alive register for the first time.
In order to prevent that time-out monitoring for the keep alive register responds, the keep alive register must be written as follows:
–
With a value of 1 ... 65535 and
 
–
an interval that is shorter than the time set in 0x23B6:002 (P514.02).
 
0x2859:003
(P515.03)
Modbus TCP/IP monitoring: Configuration error
(MBTCP monitoring: Config error)
–
From version 04.00
 
Selection of the response triggered by the reception of invalid configuration data.
Associated event ID:
–
33414 | 0x8286 - Network - PDO mapping error
 
0
No response
1
Warning
2
Trouble
3
Fault
0x2859:004
(P515.04)
Modbus TCP/IP monitoring: Initialisation error
(MBTCP monitoring: Init error)
–
From version 04.00
 
Selection of the response triggered by the occurrence of an error during the initialisation of the network component.
Associated event ID:
–
33170 | 0x8192 - Network - Initialization error
 
0
No response
1
Warning
2
Trouble
3
Fault
0x2859:007
(P515.07)
Modbus TCP/IP monitoring: Fault response to network timeout
(MBTCP monitoring: Resp netw t-out)
–
From version 04.00
 
If monitoring detects a time-out of the TCP communication with an existing TCP connection, the error response to be selected with this parameter occurs.
The maximum permissible time-out of the TCP communication is defined in 0x23B1:010 (P510.10).
Associated event ID:
–
33044 | 0x8114 - Network - Overall communication time-out
 
0
No response
1
Warning
2
Trouble
3
Fault
0x2859:008
(P515.08)
Modbus TCP/IP monitoring: Fault response to master timeout
(MBTCP monitoring: Resp mast t-out)
–
From version 04.00
 
Selection of the response if within the time set in 0x23B6:001 (P514.01) no valid message has arrived at the Modbus client.
Associated event ID:
–
33046 | 0x8116 - Modbus TCP master time-out
 
0
No response
1
Warning
2
Trouble
3
Fault
0x2859:009
(P515.09)
Modbus TCP/IP monitoring: Fault response to keep alive timeout
(MBTCP monitoring: Resp t-out kp-al)
–
From version 04.00
 
Selection of the response if within the time set in 0x23B6:002 (P514.02) no valid message has been written into the keep alive register.
Associated event ID:
–
33047 | 0x8117 - Modbus TCP Keep Alive time-out
 
0
No response
1
Warning
2
Trouble
3
Fault