Listing the error codes in the range from 8000 to 8999. These are SRCI app custom alarms.
Alarm list based on MotoPlus app version
v1.1.08xxx
8010 [1]
Alarm 8010 [1] - SRCI [FNC]: SRCI inexistent.
Description:
The SRCI function is inexistent.
Context:
Can occur during startup only.
Remedy:
Update the system software of the controller (YRC1000: >= 4.90).
8010 [2]
Alarm 8010 [2] - SRCI [FNC]: SRCI unlicensed.
Description:
The SRCI function is unlicensed.
Context:
Can occur during startup only.
Remedy:
Contact Yaskawa to purchase the unlicensed function for the controller.
8010 [3]
Alarm 8010 [3] - SRCI [FNC]: SRCI disabled.
Description:
The SRCI function is disabled.
Context:
Can occur during startup only.
Remedy:
Enable the function in maintenance mode of the controller.
8010 [4]
Alarm 8010 [4] - SRCI [FNC]: Ethernet unlicensed.
Description:
The ethernet function is unlicensed.
Context:
Can occur during startup only.
Remedy:
Contact Yaskawa to purchase the unlicensed function for the controller.
8010 [5]
Alarm 8010 [5] - SRCI [FNC]: FTP disabled.
Description:
The FTP function is disabled.
Context:
Can occur during startup only.
Remedy:
Enable the function in maintenance mode of the controller.
8010 [6]
Alarm 8010 [6] - SRCI [FNC]: FTP restricted.
Description:
The FTP function is restricted.
Context:
Can occur during startup only.
Remedy:
Change the FTP function (Level to “STANDARD”; Parameter RS5 to 1;
Parameter RS7 to 2).
8010 [7]
Alarm 8010 [7] - SRCI [FNC]: MotoLgx unlicensed.
Description:
The MotoLogix function is unlicensed.
Context:
Can occur during startup only.
Remedy:
Contact Yaskawa to purchase the unlicensed function for the controller.
8010 [8]
Alarm 8010 [8] - SRCI [FNC]: MotoLgx disabled.
Description:
The MotoLogix function is disabled.
Context:
Can occur during startup only.
Remedy:
Enable the function in maintenance mode of the controller.
8010 [9]
Alarm 8010 [9] - SRCI [FNC]: MotoLgx endianness.
Description:
The MotoLogix function endianness setting is incorrect
Context:
Can occur during startup only.
Remedy:
Change the endianness in MotoLogix setup to little.
8020 [1]
Alarm 8020 [1] - SRCI [COM]: Connection lost.
Description:
The network connection to the PLC is lost.
Context:
Can occur after startup only.
Remedy:
Check the network connection to the PLC.
8020 [2]
Alarm 8020 [2] - SRCI [COM]: Life sign timed out.
Description:
The network life sign timed out.
Context:
Can occur after startup only.
Remedy:
Adapt the network load to the timeout or adapt the timeout to the network
load.
8020 [3]
Alarm 8020 [3] - SRCI [COM]: Sequence timed out.
Description:
The sequence timed out.
Context:
Can occur after startup only.
Remedy:
Reduce the amount of requests from the PLC to the controller.
8030 [1]
Alarm 8030 [1] - SRCI [STA]: Ope. mode “rmt” req.
Description:
The operation mode “remote” is required.
Context:
Can occur after operator interaction (including startup) only.
Remedy:
Switch the operation mode to remote.
8030 [2]
Alarm 8030 [2] - SRCI [STA]: Syn. usr data fail.
Description:
User data status update failed.
Context:
Can occur after operator interaction (including startup) only.
Remedy:
Clear the alarm and switch the operation mode to teach and back to
remote.
8030 [3]
Alarm 8030 [3] - SRCI [STA]: Create frame failed.
Description:
Create controller default user frame failed.
Context:
Can occur after operator interaction (including startup) only.
Remedy:
Clear the alarm and switch the operation mode to teach and back to
remote.
8099
Alarm 8099 - SRCI [INT]: Panic (See log).
Description:
Internal error occurred (Log on USB storage at controller).
Context:
Can occur at any time.
Remedy:
Connect a FAT formatted USB storage to the USB port of the controller and
retry the failed operation. If the operation fails again, log files named
srci_panic_log.txt and/or YRP_LOG.txt will be written to the USB
storage. Please provide a description of the failed operation and the log
files to Yaskawa.
8800
Alarm 8800 - YRP failure: […]
Description:
Internal error occurred (Log unavailable).
Context:
Can occur at any time.
Remedy:
Please provide a description of the failed operation and the alarm message
to Yaskawa.