Mitsubishi Electric MELSEC Q Series User Manual page 419

Hide thumbs Also See for MELSEC Q Series:
Table of Contents

Advertisement

Error
Error
Error message
code
information
3150
DUPLICAT.NET.NO.
Parameter No.
3300
SP.PARA.ERROR
Parameter No.
3301
SP.PARA.ERROR
Parameter No.
3302
SP.PARA.ERROR
Parameter No.
3303
SP.PARA.ERROR
Parameter No.
SYSTEM WDT
Time
5000
ERROR
(set value: ms)
Time
5001
USER WDT ERROR
(set value: ms)
LED status
CPU
operation
RUN
ERR.
status
*4
Off
Flashing
Stop
*4
Off
Flashing
Stop
*4
Off
Flashing
Stop
*4
Off
Flashing
Stop
*4
Off
Flashing
Stop
Off
Flashing
Stop
Off
Flashing
Stop
Error details and cause
• When the CC-Link IE Field Network is
used, the network number set in the
network parameter and the switch setting
is duplicated.
• No network parameter and switch setting
are configured, or the CC-Link IE Field
Network
• module with an incorrect switch setting is
mounted.
The start I/O No. of an intelligent function
module set in Setting/monitoring tools for
the C Controller module differs from the
actual I/O No.
The refresh parameter of an intelligent
function module is outside the range, or the
refresh range exceeded the file register
capacity.
An intelligent function parameter is not
normal. Check the parameter setting.
In the multiple CPU system, the parameter
setting was performed for an intelligent
function module controlled by another CPU.
The system watchdog timer controlled by
the system detected an error, or an error
occurred in the system software.
• The time set for the system watchdog
timer is too short.
• A task of high CPU utilization is running.
• A program that will cause an error in the
*5
memory, stack, etc. was executed.
• An operation that increase the CPU
utilization by the system task (restarting
user CPU, and writing parameter from
the setting/monitoring tools for the C
Controller module) was executed.
• At a stop error occurrence, the station
using block data assurance per station of
the network was accessed.
• CPU module drives recklessly or it
breaks down. (Malfunction by noise etc.
and Hardware error)
Since the WDT reset was not executed
within the user WDT setting time, the USER
WDT (watchdog timer) controlled by the
system detected an error. Or, an error
occurred in the user program.
• The user WDT setting time is too short.
• A task of high CPU utilization is running.
• A program that will cause an error in the
memory, stack, etc. was executed.
• It debugged while online connection with
*5
CW Workbench.
• The command was executed from Shell
*5
for debugging.
*5
• Functions that increase the CPU
utilization by system tasks are used:
•Mount/unmount of SD memory card
•Mount/unmount of CompactFlash card
•Ethernet communication
•NFS server communication
APPENDICES
Corrective action
• Check the parameter setting.
• Configure the network parameters and
the switch settings, and then write
network parameters and the switch
settings to the module.
Check the parameter setting.
• Delete the parameter setting of the
intelligent function module controlled by
another CPU.
• Change it to the parameter setting of the
intelligent function module that the host
CPU controls.
• Restart the C Controller module
• Increase the system WDT time value in
System settings of Setting/monitoring
tools for the C Controller module.
• Decrease the CPU utilization of the task,
or disable the task operation.
*5
• Check the user program.
• Taking into account the system task CPU
utilization, sufficiently prolong the system
WDT setting time.
• Take a preventive measure against
noise.
• Check that the C Controller module is
securely installed in the base unit and
the ambient environment is within the
general specification range.
• Review the user program not to access
to the station that is used block data
assurance per station of the network at a
stop error occurrence.
If the error occurs even after the above
checks, check the modules and replace a
faulty module.
• Restart the C Controller module
• Increase the user WDT time.
• Decrease the CPU utilization of the task,
or disable the task operation.
• Check the user program.
• Check the command executed from
*5
Shell.
• Taking into account the system task CPU
utilization, sufficiently prolong the system
*5
WDT setting time.
If the error occurs even after the above
checks, check the modules and replace a
faulty module.
417
A

Advertisement

Table of Contents
loading

Table of Contents