Mitsubishi Electric MELSEC iQ-R Series User Manual page 168

Error Log
Error logs are displayed in red characters.
The following table shows the details of error messages.
■Programmable controller CPU error messages
Message
READ_ERR(error code)
WRITE_ERR(error code)
Assignment invalid
Response monitoring timeout
■SECS error messages
Message
DM reception error
DM sending error
CM sending error
Sending DM creation failed (1)
Sending DM creation failed (2)
DM sending failure
Secondary request timeout
Reception data format error
Data length invalid
Incorrect format
Incorrect device ID
Undefined SF code
Data error
Full SECS queue
Full reception queue
Transmission Queue Full
Full multi-transaction queue
Message discarded because no
communication has been established
Message discarded because it is out
of spool scope
Message discarded due to full spool
7 BASIC FUNCTIONS
166
7.17 Log Output
Description
Data was not read.
Data was not written.
An area not defined in device assignments was specified in
an item storage register, etc.
There was no programmable controller CPU response (OFF)
to a SECS/GEM communication software trigger notification
(ON) within the response monitoring timer setting, causing the
trigger to be forcibly turned OFF.
Description
Reception error
DM was not sent.
CM sending error
Initialization failed.
Creation failed.
Sending failure
After reception of a primary message, no secondary sending
request trigger was detected within the response monitoring
timer setting.
The reception data includes an incorrect SECS header.
Reception error (too long)
Incorrect format
Incorrect device ID
Undefined SF code
Reception data error
A memory acquisition error occurred when creating a
reception data storage buffer
Full reception queue
Transmission Queue Full
The multi-transaction queue for sending is full.
The requested sending message was discarded because
communication has not been established.
A non-spooled sending message requested during spooling
was discarded.
A spooled sending message requested during spooling was
discarded because the spool is full.
Notes
An error code is added at the end of the message.
An error code is added at the end of the message.

When a handshake is specified for the reception
notification trigger, SECS error notification, etc.
Notes
• HSMS: Data with unknown communication level
*1
• SECS1: Checksum error
• SECS2: Full-queue error


CPU reset is recommended.
This error also applies to the register read error,
which is often caused by an incorrect register
assignment setting.
The SECS/GEM communication software may be
under load.
This error is not output for a secondary reception
notification handshake timeout.

S9F11 sending
S9F7 sending, the message received from the host
is different from the one configured in terms of item
type, list structure, or data length.
S9F1 sending
S9F3/F5 sending, a message is regarded as an
undefined message if the reception notification
trigger option is not selected in the Message
Property window.
This error also applies to the register write error,
which is often caused by an incorrect register
assignment setting.
The CPU must be reset.
This error may also occur even for single
transactions when the software continuously
receives the same message and fails to establish
handshaking.
• This error may also occur even for multi-
transactions if sending processing is delayed due
to too much load.
• No spooling is available.

An attempt was made to send a message other than
S1F13 before communication was established.

• The spool must be transferred or discarded.
• This error is not output during overwriting.