330
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.3 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
43
(843)
Absolute Battery Charge
Voltage Drop
Cause
: The voltage of the absolute battery charger has dropped.
Treatment : Check the voltage of the 24V DC power supply.
Check the wire layout between the absolute battery box
and MCON controller.
48
(848)
Decrease in Fan
Revolution
Cause
: The fan rotation speed has decreased for the cooling fan
on the main unit.
Treatment : It is considered that it is the end of the product life of the fan
(approximately 3 years). Replace the fan.
49
(849)
Time Notification Error
Cause
: It is an internal communication error of MCON. The clock
data transfer from Gateway board to the driver board has
failed.
Treatment : Turn the power OFF and reboot. If the same error occurs
again, please contact IAI.
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 MCON. 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 internal error of MCON. The communication with the
driver board to connect each axis of the actuators was not
able to be established.
Treatment : It is considered that the driver board is not inserted or there is a
failure in the connection (connector is not inserted deep enough).
61
(861)
Slave Axis Communication
Internal Error (Sending)
Cause
: It is an internal error of MCON. The communication with the
driver board to connect each axis of the actuators was not
able to be established.
Treatment : Turn the power OFF and reboot. If the same error occurs
again, please contact IAI.
62
(862)
Slave Axis Communication
Internal Error (Receiving)
Cause
: It is an internal error of MCON. The communication with the
driver board to connect each axis of the actuators was not
able to be established.
Treatment : Turn the power OFF and reboot. If the same error occurs
again, please contact IAI.
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.
Chapter 9
Troubleshooting
Summary of Contents for MCON-C
Page 1: ...MCON C CG Controller Instruction Manual Fourth Edition ...
Page 2: ......
Page 48: ...38 Chapter 1 Specifications Check ...
Page 268: ...258 3 10 Fieldbus Status LEDs ...
Page 274: ...264 Chapter 4 Vibration Suppress Control Function ...
Page 278: ...268 Chapter 5 Collision Detection Feature ...
Page 284: ...274 Chapter 6 Power saving Function ...
Page 292: ...282 Chapter 7 Absolute Reset and Absolute Battery ...
Page 358: ...348 Chapter 9 Troubleshooting ...
Page 474: ...Chapter 10 Appendix 464 ...
Page 478: ......
Page 479: ......