Event name
FSoE Master Connection Not Established Error
Event code
35200001 hex
Meaning
FSoE communications were not established with the FSoE slave.
Source
Depends on where the Sysmac
Studio is connected and the sys-
tem configuration.
Source details
NX Unit
Detection tim-
ing
In DEBUG
mode (STOP-
PED), DEBUG
mode (RUN),
or RUN mode
Error attrib-
utes
Level
Minor fault
Recovery
Automatic re-
covery when
cause of error
is removed
Log category
System
Effects
User program
Continues.
Operation
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.
System-de-
fined varia-
bles
Variable
Data type
Name
None
None
None
Cause and
correction
Assumed cause
Correction
Prevention
The FSoE communications set-
tings are not correct, the FSoE
slave is not in the correct status,
etc.
Refer to the error for the FSoE
slave and correct the problem.
Refer to the errors for the FSoE
slaves and implement counter-
measures.
The FSoE slave for FSoE com-
munications is not connected.
Make sure the FSoE slave is
connected correctly.
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.
The FSoE slave set in the NX
Unit Mounting Setting for FSoE
communications is disabled.
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.
Set the disabled FSoE slaves in
the NX Unit Mounting Setting so
that they do not participate in
FSoE communications.
The version of the FSoE slave to
be communicated is older than
the configured version.
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.
Keep the version of the FSoE
slave in the project consistent
with the version of the FSoE
slave to be communicated.
Attached in-
formation
None
Precautions/
Remarks
The relevant Units will maintain the safe states for I/O data with FSoE connections after an error is de-
tected. However, when the cause of the error is removed, FSoE communications will recover automati-
cally.
12 Troubleshooting
12 - 34
NX-series Safety Control Unit User's Manual (Z930)
Summary of Contents for NX-SIH400
Page 4: ...Introduction 2 NX series Safety Control Unit User s Manual Z930 ...
Page 46: ...Revision History 44 NX series Safety Control Unit User s Manual Z930 ...
Page 108: ...2 Specifications 2 42 NX series Safety Control Unit User s Manual Z930 ...
Page 132: ...3 Installation and Wiring 3 24 NX series Safety Control Unit User s Manual Z930 ...
Page 148: ...4 Safety Control Unit Operation 4 16 NX series Safety Control Unit User s Manual Z930 ...
Page 216: ...5 System Configuration and Setup 5 44 NX series Safety Control Unit User s Manual Z930 ...
Page 306: ...6 Programming 6 90 NX series Safety Control Unit User s Manual Z930 ...
Page 390: ...8 Calculating Safety Reaction Times 8 12 NX series Safety Control Unit User s Manual Z930 ...
Page 412: ...11 Safety Data Logging 11 10 NX series Safety Control Unit User s Manual Z930 ...
Page 504: ...12 Troubleshooting 12 92 NX series Safety Control Unit User s Manual Z930 ...
Page 554: ...l I O Map Settings Appendices A 42 NX series Safety Control Unit User s Manual Z930 ...
Page 623: ...I Index I 1 NX series Safety Control Unit User s Manual Z930 I ...
Page 625: ......