9 - 19
9 Troubleshooting
NX-series Safety Control Unit User’s Manual (Z930)
9-3 Checking for Errors with the Sysmac Studio
9
9-3-4 Error Descriptions
Communications Errors
Event name Safety Process Data Communications Not Established
Error
Event code 35200000 hex
Meaning Safety process data communications was not established with one or more safety slaves.
Source Depends on where the Sysmac Stu-
dio is connected and the system con-
figuration.
Source details NX Unit Detection timing In DEBUG mode
(STOPPED),
DEBUG mode
(RUN), or RUN
mode
Error attributes Level Minor fault Recovery Automatic recov-
ery 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 safety connection where the error
was detected.
System-defined
variables
Variable Data type Name
None None None
Cause and
correction
Assumed cause Correction Prevention
The communications settings for
safety process data are not correct,
the safety slave is not in the correct
status, etc.
Refer to the error for the safety slave
and correct the problem.
Refer to the errors for the safety
slaves and implement countermea-
sures.
The safety slave for safety process
data communications is not con-
nected.
Make sure the safety slave is con-
nected correctly.
Make sure that all of the safety slaves
to communicate with are connected
before you change the Safety CPU
Unit to DEBUG mode (STOPPED),
DEBUG mode (RUN), or RUN mode
The safety slave set in the NX Unit
Mounting Setting for safety process
data communications is disabled.
Set the disabled safety slaves in the
NX Unit Mounting Setting so that they
do not participate in safety process
data communications and then trans-
fer the data to the Safety CPU Unit.
Set the disabled safety slaves in the
NX Unit Mounting Setting so that they
do not participate in safety process
data communications.
Attached
information
None
Precautions/
Remarks
The relevant Units will maintain the safe states for I/O data with safety connections after an error is detected. However,
when the cause of the error is removed, safety process data communications will recover automatically.