86
Safety Master Function Section 4-4
Resetting a Connection Stopped due to a Communications Error
When I/O communications have stopped in a connection due to a connection
timeout, I/O communications can be restarted in the stopped connection by
turning ON the Communications Reset Flag from the user program or sending
a Communications Restart command from the Network Configurator. If the
Controller communications mode is set to stop all connections after a commu-
nications error, communications cannot be restarted in a specified stopped
connection. In this case, restart communications in all connections.
1. Restarting I/O Communications from the Network Configurator
After connecting online with the Network Configurator, select the Safety
Master, right-click to display the popup menu, and select Monitor to dis-
play the Device Monitor Window. The following window will appear when
the safety connection is selected.
Communications can be restarted in a connection where an error occurred
(evident from the connection status) by selecting that connection and clicking
the Resume Button. If the Resume All Button is clicked, I/O communications
will restart in all Slaves with which communications were stopped.
Stop only the connection
where the error occurred.
Specify this mode to keep safety I/O communications stopped on a connection in which a
safety I/O communications error has occurred. I/O communications will continue for nor-
mal connections.
To restart safety I/O communications for connections in which I/O communications have
been stopped, use the Network Configurator to send a command to restart communica-
tions. It is also possible to write a logic routine in the user program in advance to turn ON
the specified Safety I/O Communications Restart Flag and restart communications with a
specified trigger bit.
Stop all connections Specify this mode to stop safety I/O communications with all safety slaves stopped after
a safety I/O communications error has occurred.
To restart safety I/O communications with the safety slaves after I/O communications
have been stopped, use the Network Configurator to send a command to restart commu-
nications. It is also possible to write a logic routine in the user program in advance to turn
ON all of the Safety I/O Communications Restart Flags and restart communications with
a specified trigger bit.
This function is enabled when safety I/O communications are established with all Safety
Slaves.
Mode after
communications error
Description
To Next Page
Loading...
