Lenze i550

12.13.4 Monitoring
The response to the missing Modbus messages, conguraon errors and inialisaon errors
can be congured via the following parameters.
The parameters for seng network monitoring funcons are described below.
Parameter
Address Name / seng range / [default seng] Info
0x23B1:010
(P510.10)
Modbus -TCP/IP sengs: Ethernet me-out
(MBTCP sengs: Ethernet meout)
0 ... [10] ... 65535 s
•
From version 04.00
Seng of the maximum permissible me-out of the TCP communica-
on.
When the specied monitoring me has elapsed, the response set in
0x2859:007 (P515.07) is triggered in the inverter.
0x23B6:001
(P514.01)
Time-out monitoring: Time-out me
(MBTCP t-out mon: Time-out me)
0.0 ... [2.0] ... 300.0 s
•
From version 04.00
Monitoring is acve if the rst valid write command arrives at the Mod-
bus master. Each further valid write/read message resets the watchdog
mer.
Monitoring responds if within the me set here no valid message has
been received by the Modbus master.
0x23B6:002
(P514.02)
Time-out monitoring: Keep alive me-out me
(MBTCP t-out mon: Keep al t-out)
0.0 ... [2.0] ... 300.0 s
•
From version 04.00
Monitoring is acve aer a valid value is wrien into the keep alive reg-
ister 0x23B6:005 (P514.05) via the Modbus for the rst me.
Keep alive monitoring responds if no value (range 1 ... 65535) has been
wrien into the keep alive register within the me 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 acve aer a value has
been wrien into the keep alive register for the rst me.
In order to prevent that me-out monitoring for the keep alive register
responds, the keep alive register must be wrien as follows:
•
With a value of 1 ... 65535 and
•
an interval that is shorter than the me set in 0x23B6:002 (P514.02).
0x2859:003
(P515.03)
Modbus TCP/IP monitoring: Conguraon error
(MBTCP monitoring: Cong error)
•
From version 04.00
Selecon of the response triggered by the recepon of invalid congura-
on data.
Associated error code:
•
33414 | 0x8286 - Network: PDO mapping error
0 No response
4Error types ^ 611
1 Warning
2 Trouble
3 Fault
0x2859:004
(P515.04)
Modbus TCP/IP monitoring: Inialisaon error
(MBTCP monitoring: Init error)
•
From version 04.00
Selecon of the response triggered by the occurrence of an error during
the inialisaon of the network component.
Associated error code:
•
33170 | 0x8192 - Network: inialisaon error
0 No response
4Error types ^ 611
1 Warning
2 Trouble
3 Fault
0x2859:007
(P515.07)
Modbus TCP/IP monitoring: Fault reacon by me-out
Network
(MBTCP monitoring: React t-out netw)
•
From version 04.00
If monitoring detects a me-out of the TCP communicaon with an exist-
ing TCP connecon, the error response to be selected with this parame-
ter occurs.
The maximum permissible me-out of the TCP communicaon is dened
in 0x23B1:010 (P510.10).
Associated error code:
•
33044 | 0x8114 - Network: overall communicaon meout
0 No response
4Error types ^ 611
1 Warning
2 Trouble
3 Fault
Conguring the network
Modbus TCP
Monitoring
439