Mitsubishi Electric MELSEC Q Series User Manual page 427

Return value
*1
(HEX)
-28150 Device access error during data link stop
(920A ) • .RX/RY/RWw/RWr was accessed when the own station was not transmitting data.
H
-28151 Abnormal data reception error
(9209 ) • An incorrect response data was received.
H
-28155 SRAM write error
(9205 ) • Battery backup RAM writing failed.
H
-28158 WDT error
(9202 ) • Watchdog timer (WDT) error occurred.
H
-28410 Target CPU busy error
(9106 ) • Target CPU is busy.
H
-28412 Target CPU unsupported error
(9104 ) • An unsupported request was sent to the target CPU.
H
-28413 Target CPU down error
(9103 ) • Check the operating status of the target CPU and trouble shoot the error.
H
-28414 Target CPU abnormal start error
(9102 ) • A request was sent to the CPU which was not operating normally.
H
-28415 Target CPU critical error
(9101 ) • A request was sent to the CPU where a critical error occurred.
H
-28416 Target CPU not mounted error
(9100 ) • A request was processed for the CPU No. to which no CPU module is installed.
H
Target module busy error
-28622 • Target module is busy.
(9032 ) • The channel specified for "Channel used by the own station" or "Target station
H
channel" is being used by another instruction.
Function unsupported error
• Processing was executed for the module that does not support the block data
-28624 assurance per station function.
(9030 ) • Processing was executed for the module where the block data assurance per
H
station function was not activated.
• Own CPU does not control the specified module.
-28625 Intelligent function module offline error
(902F ) • Intelligent function module was accessed while offline.
H
-28626 Control data error
(902E ) • The specified control data is out of range.
H
Transient unsupported error
-28627 • A transient request cannot be executed via the specified communication path and
(902D ) target. (With CC-Link communication, when the station No. of the own station was
H
"64", other station was specified.)
Pointer address error (pointer address is invalid.)
-28628
• The address of a short type pointer is not a multiple of 2.
(902C )
H
• The address of a long type pointer is not a multiple of 4.
-28629 WDT not running error
(902B ) • WDT was reset when WDT was started up.
H
-28630 WDT startup error
(902A ) • WDT was started up while WDT was running.
H
Buffer access range error
-28631
• The specified offset is out of range.
(9029 )
H
• The specified offset plus size is out of range.
I/O No. error
-28632 • The specified I/O No. is out of range.
(9028 ) • The module is not mounted on the specified I/O No., or the specified module
H
cannot be accessed.
-28633 Non-controlled module read error
(9027 ) • Reading from a non-controlled module is not allowed.
H
-28634 Intelligent function module down error
(9026 ) • There is a problem in the intelligent function module.
H
-28635 Intelligent function module error
(9025 ) • The intelligent function module is not mounted on the accessed slot.
H
-28636 Control bus error
(9024 ) • Control bus error occurred.
H
Error description Corrective action
• Check the specified device start number and size, or the device range of
the parameter on the master station.
• Restart the data link.
(Writing/reading data will be performed even when this error occurs.
However, the data are not guaranteed.)
Check if there is an error in the target CPU, CC-Link module, or
MELSECNET/H module. If the status is normal, try again.
Change the C Controller module if the error persists.
Reset the C Controller system.
• Add a program to wait until the processing is completed or to retry.
• Increase the timeout value in the user program.
Change the target CPU No. in the user program.
Check the operating status of the target CPU and trouble shoot the error.
• Check if the target CPU is mounted properly.
• Change the target CPU No. specified in the user program.
Add a program to wait until the processing is completed or to retry.
• Check the version to see if the target module supports the block data
assurance per station function.
• Check if the block data assurance per station setting is enabled for the
target module in Setting/monitoring tools for the C Controller module.
• Check if the control CPU of the specified module is own CPU.
Check the mode state of the intelligent function module and access the
module while online.
Check the user program, and correct the control data setting.
• Check a communication path and target which supports the transient
request.
• Change the station No. of the own station.
Check the pointer type and address (cast, structure alignment, etc.).
Start the WDT and then reset WDT.
Stop WDT and then restart WDT.
• Check the offset.
• Check the buffer size.
• Check the offset plus size.
Check the I/O No.
• Clear "Enable online module change with another CPU" selection in the
multiple CPU setting.
• Check if the control CPU of the specified module is own CPU (C
Controller module).
• Check if the intelligent function module is mounted properly.
• Replace the intelligent function module or base unit.
• Check the I/O No.
• Check if the intelligent function module is mounted properly.
• Check if there is an error in CPU 1 in the multiple CPU system.
• Check if the intelligent function module is mounted properly.
• Replace the intelligent function module or base unit.
APPENDICES
A
425