Description
The YRC1000 divides the job; instruction data and position data, into separate files to save. This alarm occurs if it detects the inconsistency between the Job instruction and position file. The following are the causes of the inconsistency. Cause 1: Single position data is chained by the plural Job instruction data. (Overlapped chain) Cause 2: Job instruction file chains the unregistered position data. (Unregistered position data chain) Cause 3: Registered position data is not chained.(Unchained position data)
Subcode description
Causes and remedies
| Cause | Remedy |
|---|---|
| Software (malfunction) | 1. After resetting the alarm, perform the following operations. • In management mode, select [Controller Setup]-[Data Mismatch Log] from the main menu to display the Data Mismatch Log screen • Select "Utility" from the drop-down menu and execute [Restore]. If restoration is possible, the occurrence time changes to the restoration time. • Turn the power OFF and back ON, then check mismatch causes 1 and 2 on the data mismatch screen in management mode. Cause 1: Check the file positions. Cause 2: Register the file positions again. For cause 3, there are no items to check after turning the power OFF and back ON. 2. If recovery is not possible with the above procedure, perform the following operations. • Select "Utility" from the drop-down menu and execute [Recheck] |
| Data (abnormal) | 1. Loading data for a different axis configuration causes incorrect system data and a data mismatch. In this case, perform the following operations. • In management mode, select [Controller Setup]-[Data Mismatch Log] from the main menu to display the Data Mismatch Log screen • Select "Utility" from the drop-down menu and execute [Restore] • Load the correct axis configuration data 2. If recovery is not possible with the above procedure, perform the following operations. • Select "Utility" from the drop-down menu and execute [Recheck], then load the correct axis configuration data |
| Other | If the alarm occurs again after implementing the countermeasures, contact our service department and describe the circumstances when CMOS.BIN was saved (operating procedure, etc.). |