![IAI MSCON Instruction Manual Download Page 296](http://html.mh-extra.com/html/iai/mscon/mscon_instruction-manual_603988296.webp)
Chapter
8 T
roubleshooting
288
8.3 Alarm
8.3.1 Gateway Alarm Codes
The alarm codes are read into b7 to b0 in Gateway Status Signal 0.
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
42
(842)
Driver Board
Shutdown Signal
Detection
Cause
: An alarm that in the level indicated Parameter No. 157 Drive
Cutoff Alarm Level has occurred (on the driver board).
Treatment : Cancel the alarm occurred on the driver board.
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 MSCON. 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 MSCON 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 MSCON. 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 MSCON. 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). Please check it.
6A
(86A)
Driver Board
Operation Pattern
Error
Cause
: There are mode that cannot exist together in the operation
modes of each axis.
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 MSCON has
destroyed.
Treatment : Establish all the settings again on Gateway Parameter Setting
Tool or write the backup data if it exists.
90
(890)
Driver Board Mount
Error
Cause
: The number of axes (number of driver boards) set in Gateway
Parameter Setting Tool does not match with the number of the
actually connected axes.
Treatment : Match the numbers of the axes.
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.
ME0306-2A
Summary of Contents for MSCON
Page 1: ...MSCON Controller Instruction Manual Second Edition ...
Page 2: ......
Page 4: ...ME0306 2A ...
Page 8: ...ME0306 2A ...
Page 20: ...12 ME0306 2A ...
Page 28: ...20 ME0306 2A ...
Page 46: ...Chapter 1 Specifications Check 38 ME0306 2A ...
Page 240: ...3 11 Gateway status LED 232 ME0306 2A ...
Page 246: ...Chapter 4 Vibration Suppress Control Function 238 ME0306 2A ...
Page 290: ...Chapter 7 Parameter 282 ME0306 2A ...
Page 310: ...Chapter 8 Troubleshooting 302 ME0306 2A ...
Page 354: ...Chapter 9 Appendix 346 ME0306 2A ...
Page 358: ......
Page 359: ......