359
Part 3 Maintenance
Code Alarm
name
Cause/action
0E8 Phase-A/B
open
detection
0E9 Phase-A
open
detection
(RPCON only)
0EA Phase-B
open
detection
(RPCON only)
Encoder signals cannot be detected correctly.
Cause:
[1] Loose or disconnected encoder-relay cable connector
[2] Piano switch 4 of the simple absolute R unit is set incorrectly.
[3] If a RA10C actuator is combined with other actuator, the combination of
encoder cables is wrong.
Action:
[1] Check the connector for looseness or disconnection.
[2] Check the piano switch setting by referring to 4.2.
[3] Check the model number of the encoder cable (cable between the simple
absolute unit and actuator).
Note) The following model numbers apply only to the RCP2 series:
Cable model number for RA10C actuator:
CB-RFA-*
For other actuator:
CB-RCP2-*
0F0
Driver logic error
(RACON only)
Cause:
An excessive load, unmatched parameter (motor type), noise and faulty
controller are suspected, among others.
Action:
Please contact IAI.
0F4
Unmatched PCB This controller uses a different motor drive circuit depending on the motor capacity, and
thus adopts a different printed circuit board (PCB) appropriate for each motor capacity.
For this reason, whether the motor type set by the applicable manufacturer’s parameter
matches the circuit board is checked in the initialization process after startup.
This alarm indicates that the two do not match.
Cause:
The parameter was not input correctly or the correct circuit board was not
assembled.
Action:
Should this error occur, please contact IAI.
0F5 Nonvolatile
memory write
verification error
When data has been written to the nonvolatile memory, the written data is read again to
check (verify) if it matches the original data.
This alarm indicates that the two data do not match.
Cause: [1]
Faulty
nonvolatile
memory
[2] The memory has been rewritten more than 100,000 times.
(As a guide, the nominal rewrite limit of the nonvolatile memory is around
100,000 times.)
Action:
If the alarm generates again after reconnecting the power, please contact IAI.
0F6 Nonvolatile
memory write
timeout
This error indicates that response was not received within the specified time after data
was written to the nonvolatile memory.
Cause: [1]
Faulty
nonvolatile
memory
[2] The memory has been rewritten more than 100,000 times.
(As a guide, the nominal rewrite limit of the nonvolatile memory is around
100,000 times.)
Action:
If the alarm generates again after reconnecting the power, please contact IAI.
0F8 Damaged
nonvolatile
memory
Abnormal data was detected during the nonvolatile memory check after startup.
Cause: [1]
Faulty
nonvolatile
memory
[2] The memory has been rewritten more than 100,000 times.
(As a guide, the nominal rewrite limit of the nonvolatile memory is around
100,000 times.)
Action:
If the alarm generates again after reconnecting the power, please contact IAI.
0FA
CPU error
The CPU is not operating properly.
Cause: [1]
Faulty
CPU
[2] Malfunction due to noise
Action:
If the alarm generates again after reconnecting the power, please contact IAI.
Summary of Contents for RoboNet
Page 1: ...Operation Manual Forth Edition ROBONET ...
Page 257: ...237 Part 2 Startup Chapter X Installed face down X Installed face up ...
Page 354: ...334 ...
Page 395: ...375 ...
Page 396: ...376 ...
Page 397: ...377 ...