![Bausch Datacom DinBox RTU M4 Reference Manual Download Page 29](http://html.mh-extra.com/html/bausch-datacom/dinbox-rtu-m4/dinbox-rtu-m4_reference-manual_2711470029.webp)
Modbus communication control
•
Request Retries
Defines the amount of failures after which a
IEC60870-5-104 event, with invalid flag set, will be
sent to the master.
•
Request Delay (ms)
Defines the delay between between the retries.
•
IOA Modbus failed
The RTU keeps track of whether a Modbus error
occurred; if the flag changes from VALID to INVALID,
or from INVALID to VALID an event will be send to the
master indication a Modbus fault.
•
IOA Modbus failed clear
After taking note of a RTU failure of Modbus at the
Master side, a command can (must) be send to the
RTU to reset the flag indicating whether an error has
occurred.
Mapping source
There are two ways to enter the Modbus mapping json file:
1. locally via the Configuration – Modbus – Mapping file
2. remotely via FTP transfer
•
FTP file name
Defines the to-download file name.
•
FTP server IP
Defines the FTP server IP address.
•
FTP server PORT
Defines the FTP server IP PORT.
•
FTP server name
Defines this FTP client user name.
•
FTP server password
Defines this FTP client password.
•
IOA trigger
Defines the IOA of the IEC60870-5-104 command
[TI58] to trigger the FTP download.
•
IOA status
Defines the IOA of the IEC60870-5-104 event to notify
the IEC60870-5-104 if the download was successful
or not.
See next chapter ‘Modbus Configuration’ for how to create this Modbus file.