Omron R88D-1SN01H-ECT, Руководство пользователя

Страница: 624 / 828

12 Troubleshooting
12 - 24 AC Servomotors/Servo Drives 1S-series with Built-in EtherCAT® Communications User’s Manual (I586)
62 00 Control Right
Release
Error Communications
between the Sysmac
Studio and Servo Drive
were interrupted while a
specific function was
used from the Sysmac
Studio.
This error is detected
when the FFT, test run,
or control output check
function is used. The USB cable or Eth-
erCAT cable was dis-
connected during the
connection with the Sys-
mac Studio. Connect the USB cable or Ether-
CAT cable between the Servo Drive
and the computer that controls the
Servo Drive if it is disconnected.
There is excessive
noise. Take noise countermeasures for the
USB cable or EtherCAT cable.
A command sent from
the Sysmac Studio was
not sent to the Servo
Drive because the com-
puter was in a busy
state or the like. Finish other applications to reduce
the processing load of the com-
puter.
70 00 Safety
Parameter
Error Safety process data communications were not
established with the Safety CPU Unit because an
incorrect parameter was received.
Check whether the connected
safety slave model matches the
safety slave model that is set from
the Sysmac Studio, and correct it.
01 Safety Com-
munications
Setting Error Safety process data
communications were
not established with the
Safety CPU Unit
because of an incorrect
communications setting. The watchdog time was
set incorrectly. If the watchdog time of the safety
process data communications set-
ting was set to a value inappropri-
ate for the communications cycle or
the configuration, correct it, and
transfer the setting to the Safety
CPU Unit.
The processing was not
completed within the
watchdog time because
communications were
not established due to
the noise. If there is no improvement after you
performed noise countermeasures,
set the longer watchdog time, and
transfer the setting to the Safety
CPU Unit.
02 FSoE Slave
Address
Error Safety process data communications were not
established with the Safety CPU Unit because of
an incorrect FSoE slave address. Perform the FSoE Slave Address
Clear for the Servo Drive.
03 Safety Frame
Error Safety process data
communications were
not established with the
Safety CPU Unit
because an incorrect
frame was received. An incorrect frame was
received in safety pro-
cess data communica-
tions. The Servo Drive model does not
match the safety slave model that is
sent from the safety master.
Check the connection configuration
and configure it correctly.
There is excessive
noise. Take noise countermeasures.
04 Safety Com-
munications
Timeout A communications time-
out occurred in safety
process data communi-
cations with the Safety
CPU Unit. A setting is not correct.
The setting of the safety
task period of the Safety
CPU Unit is too short. Increase the safety task period of
the Safety CPU Unit and then trans-
fer the settings to the Safety CPU
Unit.
There is excessive
noise. Take noise countermeasures.
The Safety CPU Unit or
safety slave entered a
status where it could not
continue safety process
data communications. Check the status of the Safety CPU
Unit or safety slave.
Error No.
Name Cause Measures
Main
(hex)
Sub
(hex)