11 TROUBLESHOOTING
| Error Code | Error Contents and Cause | Corrective Action | Corres- | |
| ponding | ||||
| (SD0) | 1 | |||
|
|
| CPU | ||
|
|
|
|
| |
| 4202 |
| More than 16 nesting levels are programmed. | Keep nesting levels at 16 or under. |
|
|
|
| A BREAK instruction was executed although no FOR instruction | Read the common error information at a peripheral device, check |
|
| 4203 |
| error step corresponding to its numerical value (program error |
| |
|
| has been executed prior to that. |
| ||
|
|
| location), and correct the problem. |
| |
|
|
|
|
| |
| 4210 |
| The CALL instruction is executed, but there is no subroutine at the |
|
|
|
| specified pointer. | Read the common error information at a peripheral device, check |
| |
|
|
|
| ||
|
|
|
| error step corresponding to its numerical value (program error |
|
| 4211 |
| There was no RET instruction in the executed |
| |
| 4212 |
| The RET instruction was before the FEND instruction in the main | location), and correct the problem. |
|
|
| program. |
|
| |
|
|
|
|
| |
| 4213 |
| More than 16 nesting levels are programmed. | Keep nesting levels at 16 or under. |
|
| 4220 |
| Interrupt input was generated, but no corresponding interrupt |
|
|
|
| pointer was found. |
|
| |
|
|
|
|
| |
| 4221 |
| There was no IRET instruction in the executed interrupt program. |
|
|
| 4223 |
| The IRET instruction was before the FEND instruction in the main |
|
|
|
| program. | Read the common error information at a peripheral device, check |
| |
|
|
|
| ||
|
|
|
| error step corresponding to its numerical value (program error |
|
| 4230 |
| The number of CHK and CHKEND instructions is not equal. |
| |
| 4231 |
| The number of IX and IXEND instructions is not equal. | location), and correct the problem. |
|
|
|
| The configuration of the check conditions for the CHK instruction is |
|
|
| 4235 |
| incorrect. |
|
|
|
| Alternatively, a CHK instruction has been used in a low speed |
|
| |
|
|
|
|
| |
|
|
| execution type program. |
|
|
| 4300 |
| The designation of a | Read the common error information at a peripheral device, check |
|
|
| instruction was wrong. | error step corresponding to its numerical value (program error | QnA | |
|
|
|
| location), and correct the problem. |
|
| 4301 |
| The designation of an AD57/AD58 control instruction was wrong. |
| |
| 4400 |
| No SFCP or SFCPEND instruction in SFC program. | Read common error information at a peripheral device, check error |
|
| 4410 |
| The block number designated by the SFC program exceeds the |
| |
|
| range. | step corresponding to its numerical value (program error location), |
| |
|
|
|
| ||
|
|
|
| and correct the problem. |
|
4411 |
| Block number designations overlap in SFC program. |
| ||
| 4420 |
| A step number designated in an SFC program exceeds 511. |
|
|
| 4421 |
| Total number of steps in all SFC programs exceed the range | Reduce total number of steps to below the maximum. |
|
| 4422 |
| Step number designations overlap in SFC program. | Read common error information at a peripheral device, check error |
|
|
| step corresponding to its numerical value (program error location), |
| ||
|
|
|
| and correct the problem. |
|
| 4500 |
| The numbers of BLOCK and BEND instructions in an SFC program |
|
|
|
| are not equal. |
|
| |
|
|
|
|
| |
| 4501 |
| The configuration of the STEP to TRAN to TSET to SEND |
|
|
|
| instructions in the SFC program is incorrect. | Read common error information at a peripheral device, check error |
| |
|
|
|
| ||
| 4502 |
| There was no STEPI instruction in SFC program block. | step corresponding to its numerical value (program error location), |
|
| 4503 |
| The step designated by the TSET instruction in the SFC program | and correct the problem. |
|
|
| does not exist. |
|
| |
|
|
|
|
| |
| 4504 |
| The step designated by the TAND instruction in the SFC program |
|
|
|
| does not exist. |
|
| |
|
|
|
|
| |
| 4600 |
| The SFC program contains data that cannot be processed. | Read common error information at a peripheral device, check error |
|
| 4601 |
| Exceeds device range that can be designated by the SFC program. | step corresponding to its numerical value (program error location), |
|
| 4602 |
| The START instruction in an SFC program is proceeded by an END | and correct the problem. |
|
|
| instruction. | The program is automatically subjected to an initial start. |
| |
|
|
|
| ||
| 4610 |
| The active step information at presumptive start of an SFC program |
|
|
|
| is incorrect. |
|
| |
|
|
|
|
| |
| 4611 |
|
|
| |
|
| designated for SFC program. |
|
| |
|
|
|
|
| |
| 4620 |
| Startup was executed at a block in the SFC program that was |
|
|
|
| already started up. |
|
| |
|
|
|
|
| |
| 4621 |
| Startup was attempted at a block that does not exist in the SFC | Read common error information at a peripheral device, check error |
|
|
| program. |
| ||
|
|
| step corresponding to its numerical value (program error location), |
| |
|
|
| Startup was executed at a block in the SFC program that was |
| |
| 4630 |
| and correct the problem. |
| |
|
| already started up. |
| ||
|
|
|
|
| |
| 4631 |
| Startup was attempted at a block that does not exist in an SFC |
|
|
|
| program. |
|
| |
|
|
|
|
| |
| 4632 |
| There were too many simultaneous active steps in blocks that can |
|
|
|
| be designated by the SFC program. |
|
| |
|
|
|
|
| |
| 4633 |
| There were too many simultaneous active steps in all blocks that |
|
|
|
| can be designated. |
|
| |
|
|
|
|
| |
| 5000 |
| Program scan time for initial execution type programs exceeds the | Read the error individual information at a peripheral device, check |
|
|
| initial execution WDT time setting designated in the PLC RAS |
| ||
|
|
| parameter. | the numerical value (time) there, and shorten scan time if |
|
| 5001 |
| The program scan time goes over the WDT value set in the | necessary. |
|
|
| parameter PLC RAS parameter. |
|
| |
|
|
|
|
| |
|
|
| (1) The scan time of the program exceeded the constant scan | (1) Review the constant scan setting time. |
|
| 5010 |
| setting time specified in the PC RAS setting parameter. | (2) Review the constant scan time and low speed program |
|
|
| (2) The low speed program execution time specified in the PC RAS | execution time in the parameter so that the margin time of |
| |
|
|
| setting parameter exceeded the margin time of constant scan. | constant scan may be fully reserved. |
|
|
|
| Low speed scan type program scan time goes over the low speed | Read the error individual information at a peripheral device, check |
|
| 5011 |
| the numerical value (time) there, and shorten scan time if |
| |
|
| execution WDT set in the parameter PC RAS settings. |
| ||
|
|
| necessary. |
| |
|
|
|
|
| |
| 6000 |
| The control system and standby system in the redundant system do | Synchronise the programs and parameters of the control system |
|
|
| not have the same programs and parameters. | and standby system. | Q4AR | |
|
|
| |||
| 6010 |
| The operational status of the control system and standby system in | Synchronise the operation statuses of the control system and | |
|
|
| |||
|
| the redundant system is not the same. | standby system. |
| |
|
|
|
|
1 Characters in parentheses ( ) indicate the special register numbers where individual information is being stored.
11 - 34 | 11 - 34 |