16 - 7
16.2 Troubleshooting
16.2.3 When the ERR. LED is on or flashing
16
TROUBLESHOOTING
16.2.3 When the ERR. LED is on or flashing
The following flowchart shows the procedures to be taken when the ERR. LED on the C 
Controller module turns on or flashes at the time of power-on or operation start or during 
operation of the C Controller system.
 * 1 Specify a correct script file or user program with special care. Specifying an incorrect script file or 
user program may result in unreliable C Controller module operation (an error, communication 
failure, illegal error code return, etc.)
 * 2 For precautions on the functions and script files, refer to the following.
 C Controller Module User's Manual (Utility Operation, Programming)
Figure 16.3 When the ERR. LED is on or flashing
Q12DCCPU-V
Q06CCPU-V-B
No
Yes
In <<Module monitoring>> of C Controller 
setting utility, check the first stop/continue 
error in the system information.
From <<Module monitoring>> of C 
Controller setting utility, open "System 
information" dialog box to display the 
error code help.
Open "Error details" dialog box to see the 
error details and take corrective actions.
Has error occurred?
Consult your local Mitsubishi service 
center or representative, explaining the 
details of the problem.
Is a script file in 
execution?
Is the 7-segment 
LED flashing? 
(For Q06CCPU-V(-B), go to 
No.)
Has error occurred?
Error occurred
No
Yes
End
No
No
Yes
Yes
End
Yes
No
Compile the user program and 
regenerate an execution file according 
to the C Controller module 
specifications.
Does the endian format
of the execution file match the specification 
of your the C Controller 
module?
*2
Is "01" or "02" flashing on the 
7-segment LED display?
No
Yes
Check the battery and if it is dead, 
replace it.
Perform the module initialization 
setting procedure of the hardware 
self-diagnostic function to initialize 
the C Controller module.
Disable the script file execution.
 (                                                          )
Correct the script file/user program.
Check the script file and user program. 
*1*2
Page 16-22, Section 16.2.13