Mitsubishi Electric Q26UD(E)HCPU User Manual page 435

Error code
Error item
(Hexadecimal)
Redundant
4254
system-related
H
error
Redundant
4255
system-related
H
error
Redundant
4256
system-related
H
error
Redundant
4257
system-related
H
error
Redundant
4258
system-related
H
error
Redundant
4259
system-related
H
error
Redundant
425B
system-related
H
error
Redundant
425C
system-related
H
error
Redundant
425D
system-related
H
error
4270 *1
Data logging
H
4271 *1
Data logging
H
4272 *1
Data logging
H
4273 *1
Data logging
H
4274 *1
Data logging
H
4275 *1
Data logging
H
Error details
The command cannot be executed since an
error was detected in the tracking
communication hardware.
The command cannot be executed since
tracking communication is being prepared.
The command cannot be executed since a time-
out error occurred in tracking communication.
The command cannot be executed since the
host system CPU module is in a watchdog timer
error or CPU module hardware fault status.
Operation mode being changed (from backup
mode to separate mode)
Operation mode is being changed with another
programming tool in the communication route
different from the one currently used.
Although the communication was made via the
intelligent function module mounted on the
extension base unit, the combination of the
connection destination specification (Redundant
CPU specification) and the command is
unsupported.
System switching cannot be made since the
module mounted on the extension base unit is
being replaced online.
Operation mode cannot be changed since the
module mounted on the extension base unit is
being replaced online.
Data logging is being performed (logging, saving
the logging data, completing, on hold, or in error)
with a different memory.
The specified data logging is already being
performed (logging, saving the logging data,
completing, on hold, or in error).
The trigger logging with "Device" specified as a
trigger condition is being performed (logging,
saving the logging data, completing, on hold, or
in error).
The data logging function cannot be executed
because the sampling trace function is being
performed.
Trigger loggings have registered exceeding the
number of trigger loggings collectable in the data
logging buffer.
Auto logging is being performed.
Corrective action
The tracking cable may not be connected correctly,
or the tracking communication hardware of the
CPU module may be faulty. Check the connection
status of the tracking cable.
If the condition is not restored to normal after the
cable connection status is corrected, the possible
cause is the hardware fault of the CPU module.
Tracking communication is being prepared when it
is connected. Execute the operation again after a
while (about 1 second).
The tracking cable may not be connected correctly,
or the tracking communication hardware of the
CPU module may be faulty. Check the connection
status of the tracking cable.
If the condition is not restored to normal after the
cable connection status is corrected, the possible
cause is the hardware fault of the CPU module.
The command cannot be executed since the host
system is in a watchdog timer error or CPU module
hardware fault status. Execute again after
checking the host system status.
Change the operating status of the CPU module
from STOP to RUN with the RUN/STOP switch of
the module whose RUN LED is flashing or by
remote operation, and end the operation mode
change. Then, execute the command again.
Execute again in the same communication route
as the one where the operation mode change was
executed.
Change the combination of the connection
destination specification and the command to the
supported combination.
Switch systems after the online module change
has been completed.
Change the operation mode after the online
module change has been completed.
Register the data logging to the memory where a
data logging is being performed. Alternatively, stop
the data logging being performed and register
again.
Stop the data logging. Alternatively, write, delete,
or register to the setting number where no data
logging is being performed.
Change the trigger condition. Alternatively, stop
the trigger logging being performed (logging,
saving the logging data, completing, on hold, or in
error) with "Device" specified as the trigger
condition, and then register.
Hold the sampling trace to register the data
logging.
• Increase the capacity of the data logging buffer.
• Reduce the number of records set for the trigger
logging.
After the auto logging, replace the SD memory
card and execute again.
APPENDICES
Corresponding
CPU
A
QnPRH
QnPRH
QnPRH
QnPRH
QnPRH
QnPRH
QnPRH
QnPRH
QnPRH
QnUDV
LCPU
QnUDV
LCPU
QnUDV
LCPU
QnUDV
LCPU
QnUDV
LCPU
QnUDV
LCPU
433