9.
Troubleshooting
Fieldbus Communication
232
RCP6S
9.3 Gateway Alarm
9.3.1 Gateway Alarm Codes
The alarm codes are read into ALMC1 to128 (b7 to b0) in Gateway Status Signal 0.
[Refer to 3.4.2 Gateway Control Signals (Common for all operation modes).]
(Note) The alarm code shown on Gateway Parameter Setting Tool is applied with “8” on the top
of the alarm codes listed below. (Example) If the alarm code is 43, it will be shown as 843.
Alarm
Code
Alarm Name
Cause/Treatment
4A
(84A)
Real Time Clock
Operation Stop Detection
Cause
: Clock data has lost.
The clock data can be remained for approximately 10 days
after the power to the controller is turned OFF.
Treatment : Have the clock setting done from the Gateway Parameter
Setting Tool again.
4B
(84B)
Real Time Clock Access
Error
Cause
: It is an internal error of RCP6S GW. The clock data failed to
be acquired internally.
Treatment : Turn the power OFF and reboot. If the same error occurs
again, please contact IAI.
50
(850)
Fieldbus Communication
Error
(ERR-C)
Cause
: It is a Fieldbus link error. If the flip-flop is set in Gateway
Parameter Setting Tool during this error, the actuator is
stopped in the condition of the error and any command is
ignored until it receives a release signal.
Treatment : Check the settings for Fieldbus (node addresses,
communication speed, etc.) and wiring layout.
60
(860)
Master-Slave Axes
Communication Error
(ERR-T)
Cause
: It is an error of RCP6S GW. The communication with the
driver board to connect each axis of the actuators was not
able to be established.
Treatment : It is concerned that there is an error in the connector
insertion (connector is not inserted till it hits the end) or line
breakage on the cable.
61
(861)
Master-Slave Axes
Communication Internal
Error
(Sending)
Cause
: It is a communication error of RCP6S GW. It is concerned
that there is an error in the connector insertion (connector
is not inserted till it hits the end) or line breakage on the
cable..
Treatment : It is concerned that there is an error in the connector
insertion (connector is not inserted till it hits the end) or line
breakage on the cable.
62
(862)
Master-Slave Axes
Communication Internal
Error
(Receiving)
Cause
: It is a communication error of RCP6S GW. The
communication with the actuator built-in controller could not
be established.
Treatment : It is concerned that there is an error in the connector
insertion (connector is not inserted till it hits the end) or line
breakage on the cable.
6A
(86A)
Driver Board Operation
Pattern Error
Cause
: Operation modes which cannot be used together are indicated.
Treatment : Set the operation modes again on Gateway Parameter
Setting Tool.
80
(880)
GW Parameter Error
Cause
: There is an error in Gateway parameters.
Treatment : Check the settings such as the number of connected axes
and operation mode on Gateway Parameter Setting Tool.
81
(881)
Parameter Check Sum
Error
Cause
: There is a possibility that the memory data inside RCP6S
GW has destroyed.
Treatment : Establish all the settings again on Gateway Parameter
Setting Tool or write the backup data if it exists.
9C
(89C)
Fieldbus Module Not
Detected
Cause
: Communication board for Fieldbus was not detected.
1) Communication board is not inserted.
2) Malfunction of communication board
Treatment : Turn the power OFF and reboot. If the same error occurs
again, please contact IAI.
ME0349-4B
Summary of Contents for RCM-P6AC
Page 2: ......
Page 9: ...Fieldbus Communication RCP6S ME0349 4B ...
Page 32: ...Fieldbus Communication 20 RCP6S ME0349 4B ...
Page 86: ...2 Wiring Fieldbus Communication 74 RCP6S ME0349 4B ...
Page 178: ...3 Operation Fieldbus Communication 166 RCP6S ME0349 4B ...
Page 184: ...4 Vibration Suppress Control Function Fieldbus Communication 172 RCP6S ME0349 4B ...
Page 192: ...6 Power saving Function Fieldbus Communication 180 RCP6S ME0349 4B ...
Page 196: ...7 Absolute Reset Fieldbus Communication 184 RCP6S ME0349 4B ...
Page 284: ......
Page 285: ......