
2.3 Gateway Unit Alarm Causes and Countermeasures
C2-5
ME0384-4A
M
ai
nt
ena
nc
e
Sec
tion
C
ha
pt
er
2
Tr
oubl
es
hoot
in
g
2.3 Gateway Unit Alarm Causes and Countermeasures
Causes and countermeasures of individual alarms
The alarm codes will be read out in gateway status signal 0 ALMC1 ~ 128 (b0 ~ b7).
For details, refer to "Specifications Section Chapter 3, 3.7 Address Configuration (page A3-30)".
(Note) Alarm codes displayed on the gateway parameter configuration tool have "8" added at the
beginning of the alarm codes listed below. (Example) If the alarm code is 43, it will be
displayed as 843.
Alarm
code
Alarm name
Causes/countermeasures
4A
(84A)
Real-time clock
vibration stop detection
Cause: Time data was lost.
Time data can be retained for about 10 days after turning
gateway unit power OFF.
Countermeasure: Set the time again from the gateway parameter.
4B
(84B)
Real-time clock
access error
Cause: RCON internal error. Retrieval of internal time data failed.
Countermeasure: Reboot the power. If it occurs again, contact IAI.
4C
(84C)
Estimated life of backup
capacitor for calendar
function exceeded
Cause: Gateway interior capacitor capacitance has dropped by 50%.
Countermeasure: Replace the gateway body as soon as possible.
50
(850)
Field network
communication error
(ERR-C)
Cause: Field network link error. If a latch is set with the gateway
parameter configuration tool while this error is generated,
actuator operation will stop in error status and commands will
be ignored until the cancel signal is received.
Countermeasure: Check field network settings (node address,
communication speed, etc.), wiring, etc.
60
(860)
Dependent axis
communication error
(ERR-T)
Cause: RCON internal communication error. Communication failure
with driver unit connecting actuator axes.
Countermeasure: Driver unit may not be inserted, mounting may be
faulty (connector not fully inserted), etc.
61
(861)
Dependent axis internal
communication error
(transmission)
Cause: RCON internal communication error. Communication failure
with driver unit connecting actuator axes.
Countermeasure: Reboot the power. If it occurs again, contact IAI.
62
(862)
Dependent axis internal
communication error
(reception)
Cause: RCON internal communication error. Communication failure
with driver unit connecting actuator axes.
Countermeasure: Reboot the power. If it occurs again, contact IAI.
Содержание Rcon
Страница 12: ...ME0384 4A ...
Страница 32: ...Actuator Coordinate System Intro 20 ME0384 4A ...
Страница 42: ...1 3 General Specifications A1 9 ME0384 4A Specifications Section Chapter 1 RCON Overview ...
Страница 45: ...ME0384 4A ...
Страница 291: ...ME0384 4A ...
Страница 323: ...ME0384 4A ...
Страница 384: ...1 3 Startup Procedure B1 9 ME0384 4A Startup Section Chapter 1 Overview ...
Страница 420: ...3 6 Precautions B3 15 ME0384 4A Startup Section Chapter 3 Absolute Reset ...
Страница 588: ...6 2 Various Functions B6 81 ME0384 4A Startup Section ...
Страница 606: ...1 5 Predictive Maintenance Function C1 17 ME0384 4A Maintenance Section Chapter 1 Maintenance and Inspection ...
Страница 644: ...2 5 Causes and countermeasures for ELECYLINDER alarms C2 37 ME0384 4A Maintenance Section Chapter 2 Troubleshooting ...
Страница 662: ...1 1 Conforming to safety category D1 17 ME0384 4A Appendix Chapter 1 Conforming to Safety Category ...
Страница 837: ......
Страница 838: ......