6-4Troubleshooting6.2.2 PROG Mode Does Not Change to RUN Condition:A syntax error or a self-diagnosis error that caused operation to stop has occurred. Solution:Confirm the status in the following procedure.PROCEDURE1. Confirm that the ERROR or ALARM LED is not turned on.2. Use the "Totally Check Project" function under "Debug" in FPWIN GR7 toidentify the syntax error.6.2.3 ALARM LED Turns ON on the CPU Unit Condition:The system watchdog timer has been activated and the operation of controller has beenstopped. Solution:PROCEDURE1. Switch the CPU unit to the PROG. mode, and turn off the power supply andthen on again.If the ALARM LED lights again, there may be a problem with the unit. If theALARM LED goes out after the power supply is turned off and then on again, theproblem may have been caused by noise or another temporary phenomenon.2. Switch to the RUN mode.If ALARM LED turns on after switching to the RUN mode, the program is takingexcessive time. Review and modify the program.3. Check the ambient environment for influence of noise.If there is no problem with the program, there may be a problem in the ambientenvironment. Check the wiring including the earth wiring. In particular, check if theRS-232C wiring is not close to power cables, and if the wiring is shielded.KEY POINTS When the program is to be reviewed, check the following points.Example 1: Is there any infinite loop in the program, resulting from a JPinstruction, LOOP instruction or other instructions that control the programflow?Example 2: Are there multiple interrupt instructions that are beingconsecutively executed?Phone: 800.894.0412 - Fax: 888.723.4773 - Web: www.clrwtr.com - Email: info@clrwtr.com
