Omron NX-SL3300 User Manual page 446

12 Troubleshooting
Event name FSoE Master Connection Not Established Error
Meaning FSoE communications were not established with the FSoE slave.
Source Depends on where the Sysmac
Studio is connected and the sys-
tem configuration.
Error attrib- Level
utes
Effects User program
System-de- Variable
fined varia-
None
bles
Cause and Assumed cause
correction
The FSoE communications set-
tings are not correct, the FSoE
slave is not in the correct status,
etc.
The FSoE slave for FSoE com-
munications is not connected.
The FSoE slave set in the NX
Unit Mounting Setting for FSoE
communications is disabled.
The version of the FSoE slave to
be communicated is older than
the configured version.
Attached in- None
formation
Precautions/ The relevant Units will maintain the safe states for I/O data with FSoE connections after an error is de-
Remarks tected. However, when the cause of the error is removed, FSoE communications will recover automati-
cally.
12 - 34
Source details NX Unit
Minor fault Recovery
Continues. Operation
Data type
None
Correction
Refer to the error for the FSoE
slave and correct the problem.
Make sure the FSoE slave is
connected correctly.
Set the disabled FSoE slaves in
the NX Unit Mounting Setting so
that they do not participate in
FSoE communications and then
transfer the data to the Safety
CPU Unit.
Change the version of the FSoE
slave in the project to the version
of the FSoE to be communicat-
ed, and then transfer the setting
to the Safety CPU Unit again. Or,
replace to a Unit that has a new-
er version than the Unit that is
set with the FSoE salve to be
communicated.
Event code 35200001 hex
Detection tim-
ing
Automatic re- Log category
covery when
cause of error
is removed
The Unit continues to operate, but the safe states
are used for the I/O data of the safety connection
where the error was detected.
Name
None
Prevention
Refer to the errors for the FSoE
slaves and implement counter-
measures.
Make sure that all of the FSoE
slaves to communicate with are
connected before you change
the Safety CPU Unit to DEBUG
mode (STOPPED), DEBUG
mode (RUN), or RUN mode.
Set the disabled FSoE slaves in
the NX Unit Mounting Setting so
that they do not participate in
FSoE communications.
Keep the version of the FSoE
slave in the project consistent
with the version of the FSoE
slave to be communicated.
NX-series Safety Control Unit User's Manual (Z930)
In DEBUG
mode (STOP-
PED), DEBUG
mode (RUN),
or RUN mode
System