- No category
advertisement
10 TROUBLESHOOTING
MELSEC-Q
10.2 Error Code Tables
The following shows the error codes, error contents, and corrective action for errors that are generated during communication between the Q series C24 and an external device.
The signal name in the following table indicates the CH side LED on status or communication error status that is stored into buffer memory address 201
H
/202
H
when an error occurs.
The CH side LED on status and communication error status can be confirmed by GX
Developer's System monitor or GX Configurator-SC. (Refer to Section 10.1.1.)
For errors without a corresponding signal name entered to errors generated with the
MC protocol communication, “NAK” comes on.
10.2.1 Error code table
The following shows the error codes, error contents, and corrective action for errors generated during communication using MC protocol (excluding A compatible 1C frame), non procedure protocol, and bidirectional protocol.
(" " in the table is the error code when the target CPU is not a Q/QnACPU.)
Error code
(Hexadecimal)
Error
Error Contents
Signal name
Corrective action
MC
Protocol
Non
Procedure
Bidirectional
3E8
H to
3FFF
H
4000
H to
4FFF
H
7101
H
7102
H
—
—
System error
(Error detected by the CPU)
(Error detected by the CPU)
•
The OS of the Q series C24 detected some error.
7103
H
PLC access error
•
Cannot communicate with the Q series C24 CPU.
—
—
—
C/N
•
See Troubleshooting of the
QCPU (Q mode) maintenance and inspection user's manual and take corrective action.
•
See Appendix of the QCPU (Q mode) maintenance and inspection user's manual
(details) and take corrective action.
( 1)
•
Make the watchdog timer (timer
1) time longer.
•
Check if the CPU can communicate in communication protocol No. "F".
7104
H to
7116
H
7140
H
System error
•
The OS of the Q series C24 detected some error.
Request data error
System error
Device name error
•
Number of request points exceeds the range for the command.
•
A word device was designated in a bit units command.
•
The last device No. exceeds the range.
Given device last No. > Designated head device
No. + Designated number of points
•
The OS of the Q series C24 detected some error.
•
A device that cannot be designated by the given command was designated.
— ( 1)
PRO
•
Check and correct the external device transmit message and restart data communications.
7141
H
7142
H
7143
H
7144
H
7145
H
7146
H
7147
H
Device No. error
•
The head device No. is out of range.
Monitor data write error
Monitor PLC No.
error
Monitor CPU model name error
•
Monitoring was requested before the device to be monitored was written.
•
The written PLC No. and PLC No. in the monitor request are different.
•
The written CPU model name and the CPU monitor name in the monitor request are different.
Written number of monitoring points overrun error
•
The written number of monitoring points exceeds the designated range.
—
PRO
PRO
PRO
( 1)
•
Check and correct the external device transmit message and restart data communications.
•
Check and correct the external device transmit message and restart data communications.
•
Write the device to be monitored before issuing a monitor request.
C/N
•
Rewrite the monitor data.
C/N
•
Rewrite the monitor data.
PRO
•
Check and correct the external device transmit message and restart data communications.
10 - 15 10 - 15
10 TROUBLESHOOTING
MELSEC-Q
Error code
(Hexadecimal)
Error
Error Contents
7148
H
7149
714A
H
H
Extension R block
No. error
System error
Cannot execute a command during
RUN
•
A nonexistent extension file register block No. was designated.
•
A block No. being used as an extension comment area, sampling trace area, or status latch area was designated.
•
The OS of the Q series C24 detected some error.
•
A write command was designated when "Disable write during RUN" was set.
•
Parameter or sequence program was written during
RUN.
714B
H to
714D
H
System error
•
The OS of the Q series C24 detected some error.
Signal name
—
C/N
( 1)
•
Change the setting to "Enable write during RUN" and restart data communications.
•
Stop the CPU and restart data communications.
( 1)
Corrective action
PRO
•
Correct the designated block
No. and restart data communications.
—
714E
H
Monitor network
No. error
7150
H
System error
7151
H
PLC No.
designation error
7152
H
System error
•
The written monitor network No. and the monitor request network No. are different.
•
The OS of the Q series C24 detected some error.
•
A PLC No. other than "FF" or "0 to 64(00
H
to 40
H
)" was designated.
•
The OS of the Q series C24 detected some error.
7153
H
Frame length error
•
The received message length has exceeded the allowable range.
7154
7155
7156
H
H
H
System error
Unwritten monitor data error
System error
•
The OS of the Q series C24 detected some error.
•
Monitoring was requested before monitor data was written.
•
The OS of the Q series C24 detected some error.
7160
H
PLC access error
•
CPU model name cannot be confirmed.
C/N
—
C/N
—
CHn
ERR.
—
PRO
—
C/N
•
Check and correct the other station access valid module No.
in the network parameters.
•
Rewrite the monitor data.
( 1)
•
Check and correct the external device transmit message and restart data communications.
( 1)
•
Review the transmission message.
•
Correct the message format so the number of access points is within the allowable range.
( 1)
•
Write the device to be monitored before issuing a monitor request.
( 1)
•
If there is an error in the CPU, remove the CPU error and restart data communications.
7161
H to
7163
H
System error
•
The OS of the Q series C24 detected some error.
— ( 1)
7164
H
Request error
7166
7167
7168
H
H
H
System error
Cannot execute a command during
RUN
•
The OS of the Q series C24 detected some error.
•
A write command was designated when "Disable write during RUN" was set.
•
A command that cannot be executed during RUN was designated.
7169
H
CPU error
•
Either the request or the device designation method is wrong.
•
Cannot communicate normally with the CPU.
—
C/N
C/N
C/N
•
Check the transmission message/request from the external device, make the necessary corrections, and send again.
( 1)
•
Change the setting to "Enable write during RUN" and restart data communications.
•
Stop the CPU and restart data communications.
•
If there is an error in the CPU, remove the CPU error and restart data communications.
716A
H to
716C
H
716D
H
716E
H
System error
•
The OS of the Q series C24 detected some error.
Monitor data write error
•
Monitor data was not written using QnA compatible
2C/3C/4C frame.
•
Monitor data was not written using A compatible 1C frame.
—
PRO
PRO
( 1)
•
Rewrite monitor data.
MC
Protocol
Non
Procedure
Bidirectional
10 - 16 10 - 16
10 TROUBLESHOOTING
MELSEC-Q
Error code
(Hexadecimal)
Error
Error Contents
Signal name
Corrective action
MC
Protocol
Non
Procedure
Bidirectional
716F
H
Device error
7170
H
•
A nonexistent device was designated.
•
Device that cannot be specified by the corresponding command was designated.
•
Number of access points exceeded the range.
PRO
PRO
•
Check and correct the external device transmit message and restart data communications.
7171
H
7172
H
7173
H
A compatible 1C frame error
Monitor data write error
•
A device that cannot be designated was designated.
PRO
•
Written number of monitoring points is incorrect. For example, [0] was designated.
PRO
•
Monitor data was written for a CPU other than a
Q/QnACPU using QnA compatible 2C/3C/4C frame.
PRO
•
Check and correct the external device transmit message and restart data communications.
•
Write the monitor data and use the A compatible 1C frame to a
CPU other than a Q/QnACPU.
7E00
H to
7E05
H
System error
•
The OS of the Q series C24 detected some error.
— ( 1)
7E06
H
Buffer memory address setting error
•
Transmit/receive buffer memory addresses are in the special applications area.
•
Change the buffer memory addresses so that they are outside the special applications area.
7E07
H to
7E0A
H
System error
•
The OS of the Q series C24 detected some error.
— ( 1)
7E40
H
Command error
7E41
H
Data length error
7E42
H
Error count error
7E43
H
Device error
7E44
H
7E46
H
System error
7E47
H
Timer 1 time-out error
•
A nonexistent command or subcommand was designated.
•
A data length exceeding the number of points that can communicate during random read/write was designated.
•
Number of requested points exceeds the range for the command.
•
A nonexistent device was designated.
•
Device that cannot be specified by the corresponding command was designated.
•
A response message was not returned within the response monitoring time (timer 1) monitoring time.
•
The OS of the Q series C24 detected some error.
Continuous request error
•
The next request was received before a response message was returned for the preceding request.
PRO
PRO
PRO
PRO
C/N
—
PRO
•
Check and correct the external device transmit message and restart data communications.
•
Check and correct the external device transmit message and restart data communications.
•
Check and correct the external device transmit message and restart data communications.
•
Check and correct the external device transmit message and restart data communications.
•
Make the timer 1 monitoring time longer.
•
When accessing another station's CPU, check if the routing parameters match.
( 1)
•
Do not issue continuous requests from the external device.
•
Set the timer 1 monitoring time to the external device time-out time.
7E48
H to
7E4C
H
System error
•
The OS of the Q series C24 detected some error.
— ( 1)
7E4D
H
7E4E
H
System error
7E4F
H
7E50
H
7E51
H
Error during data transmission
Device point count error
•
Access point count is incorrect.
User frame No.
designation error
Unwritten user frame error
•
Mode switching was executed during data transmission.
•
The OS of the Q series C24 detected some error.
CHn
ERR.
•
A user frame No. outside the range was designated.
PRO
•
An unwritten user frame No. was designated.
—
PRO
PRO
•
Make arrangements between the target device and PLC CPU so that mode switching is not executed during data transmission.
( 1)
•
Check and correct the external device transmit message and restart data communications.
•
Check and correct the external device transmit message and restart data communications.
•
Recheck the frame No..
•
Write the frame beforehand.
•
Change the frame No. and restart data communications.
•
Recheck the frame No..
10 - 17 10 - 17
10 TROUBLESHOOTING
MELSEC-Q
Error code
(Hexadecimal)
Error
Error Contents
Signal name
Corrective action
MC
Protocol
Non
Procedure
Bidirectional
7E52
H
User frame overwrite error
•
A written frame No. overwrite request was issued.
PRO
•
Change the write destination to an unwritten frame No.
•
When overwriting, delete the given No. beforehand.
7E53
H
7E54
H
7E55
H
User frame access data error
Modification allowed error
•
A nonexistent command was designated in a subcommand.
•
Byte count exceeding the number of bytes that can be requested was designated.
•
Flash ROM write allow/prohibit designation from GX
Configurator-SC is set to OFF.
•
At the switch setting on GX Developer, modification allowed switch was set to OFF.
User frame data error
7E56
H
System error
7E57
H
7E58
H
7E59
H
Flash ROM write error
Mode modification error
•
There was an error in the mode No. or transmission specification designated contents when changing the mode.
Flash ROM write count over limit error
•
There is an error in the user frame variable data.
•
The OS of the Q series C24 detected some error.
•
Cannot write to Flash ROM normally.
•
Flash ROM written 1,000 times
PRO
PRO
PRO
—
PRO
PRO
—
•
Check and correct the external device transmit message and restart data communications.
•
Set to ON at GX Configurator-
SC.
•
Set to ON at GX Developer.
•
Check and correct the external device transmit message and restart data communications.
( 1)
•
Re-execute the write operation.
If the error is generated again, replace the module.
•
Check and correct the contents of the external device transmit message and restart data communications.
•
Recheck the switch setting on the Q series C24.
•
Review the program.
•
Rewrite the flash ROM area
(address: 2401
H
) of the buffer memory to 0 and restart data communications.
•
Correct the I/O number of the module to which data is sent.
•
Cancel the PLC CPU monitoring and perform the PLC CPU monitoring registration again.
•
Correct the setting value of the cycle time units.
7E5F
H
7E60
H
7E61
H
7E62
H
7E63
H
7E64
H
7E65
H
7E66
H
7E67
H
7E68
H
7E69
H
I/O number error on requested module
Device monitoring duplicate registration error
Cycle time units range error
•
•
•
I/O number of requested module is incorrect.
PLC CPU monitoring registration was performed twice.
Setting value of cycle time units is out of range.
PLC CPU monitoring function error
•
Setting value of PLC CPU monitoring function is out of range.
Transmission measure setting error
Registration point range error
•
•
Setting of transmission measure of the PLC CPU monitoring is incorrect.
Registration point (word/bit) is out of range.
PLC CPU abnormal monitoring number error
•
Setting value of the PLC CPU abnormal monitoring is out of range.
Monitoring condition error of monitoring device
•
Setting value of transmission condition is out of range.
CPU abnormal monitoring setting value error
Transmission condition range error of monitoring device
CPU abnormal monitoring setting value error
•
•
•
Setting value (fixed value) of CPU abnormal monitoring is out of range.
Setting value of transmission condition (condition agreement transmission) is out of range.
Setting value (fixed value) of CPU abnormal monitoring is out of range.
—
—
—
—
—
—
—
—
—
—
—
•
Correct the setting value of the
PLC CPU monitoring function.
•
Correct the setting value of the transmission measure.
•
Correct the setting value of the registration point (word/byte)
•
Correct the setting value of the
PLC CPU abnormal monitoring.
•
Correct the setting value of the transmission condition.
•
Correct the setting value (fixed value) of the CPU abnormal monitoring.
•
Correct the setting value of the transmission condition
(condition agreement transmission).
•
Correct the setting value (fixed value) of the CPU abnormal monitoring.
10 - 18 10 - 18
10 TROUBLESHOOTING
MELSEC-Q
Error code
(Hexadecimal)
Error
Error Contents
Signal name
Corrective action
7E6A
7E70
H
7E6B
7E6C
H
H
7E6D
H
CPU abnormal monitoring setting value error
7E6E
H
System error
7E6F
H
•
Setting value (fixed value) of CPU abnormal monitoring is out of range.
•
The OS of the Q series C24 detected some error.
Modem connection error
•
Modem is connected to an incorrect channel.
H
Monitoring device read point range error
CPU error
•
Read point of monitoring device is out of range.
•
The communication with the CPU could not be performed normally.
—
—
—
—
—
—
C/N
•
Correct the setting value of the read point of the monitoring device.
•
Correct the setting value (fixed value) of the CPU abnormal monitoring.
( 1)
•
Correct the C
H
to which notification is sent.
•
If there is an error in the CPU, eliminate the error on the CPU side and communicate again.
7E81
H to
7E8E
H
7EC1
H
7EC2
H
System error
•
The OS of the Q series C24 detected some error.
— ( 1)
7EC3
7EC4
7EC5
7F21
7F22
7F23
H
H
H
Double send request error
Transmission data count error
Transmission/ receipt buffer setting error
Flash ROM access error
•
•
A send request was performed while another send request was being processed.
Data larger than the transmit buffer size was transmitted.
•
Transmission/receipt buffer settings out of range.
•
Write to Flash ROM was requested when the setting modification enable/disable switch in the GX
Developer was set to OFF.
7EC6
7F00
7F01
H
H
H
Flash ROM access error
•
There is an error in the Flash ROM read/write request contents.
System error
Buffer full error
•
The OS of the Q series C24 detected some error.
•
The next data was received before processing of the previous data was completed.
•
Multiple requests was simultaneously issued for one channel.
7F02
H to
7F06
H
System error
•
The OS of the Q series C24 detected some error.
•
An ASCII code that cannot be converted to binary code was received.
7F20
H
ASCII BIN conversion error
•
An odd number of bytes of data was received during data communications using ASCII conversion.
BIN
H
H
H
Receive header area error
Command error
MC protocol message error
•
There is an error in the command (frame) part.
•
An ASCII code that cannot be converted to binary code was received.
•
A nonexistent command or device was designated.
•
The remote password length is wrong.
•
There is no data (ETX, CR-LF, etc.) following the character area, or designation was incorrect.
—
—
(
(
•
Interlock (handshake) the send requests.
•
Make the transmission data count smaller than the transmit buffer size.
•
Make the non procedure protocol transmit buffer size larger.
•
Designate the first address and size of transmission/receipt buffer in the free area range of the user.
•
When writing to Flash ROM, set switch shown left of the given interface to ON and restart the
Q series C24.
•
Check the read/write request data and designate the correct data.
•
•
1)
Increase the transmission time by performing handshake with the external device, etc.
Perform handshake with the request source external device.
1)
•
Check and correct the external device transmit message and restart data communications.
PRO
•
When communicating using
ASCII BIN conversion, always transmit the data in even number bytes units.
PRO
PRO
PRO
•
Check and correct the external device transmit message and restart data communications.
•
Check and correct the external device transmit message and restart data communications.
•
Check and correct the external device transmit message and restart data communications.
MC
Protocol
Non
Procedure
Bidirectional
10 - 19 10 - 19
10 TROUBLESHOOTING
MELSEC-Q
Error code
(Hexadecimal)
Error
Error Contents
Signal name
Corrective action
7F42
H
7F50
H to
7F54
H
7F60
H to
7F66
H
7F24
7F25
7F26
7F30
7F31
7F32
7F40
7F41
H
H
H
H
H
H
H
H
Sum check error
Data length error
Command error
System error
Simultaneous transmission error
System error
Time-out error
•
•
The sum check calculated by the Q series C24 and the received sum check are not the same.
The length of the received data exceeds the receive area size.
•
Another command was received before an unlock processing while the remote password is registered.
•
The OS of the Q series C24 detected some error.
•
•
•
•
•
The Q series C24 and an external device started transmitting simultaneously.
The OS of the Q series C24 detected some error.
No reception watchdog timer (timer 0) time-out occurred.
Response watchdog timer (timer 1) time-out occurred.
Transmit watchdog timer (timer 2) time-out occurred.
P/S
CHn
ERR.
CHn
ERR.
—
—
PRO
•
Recheck the external device sum check.
•
Correct the "data length" that is transmitted from the external device.
•
Change the "word/byte units" set by the Q series C24 to byte units.
•
Increase the receiving area of the Q series C24.
•
Perform the communication after the unlock processing is normally completed.
( 1)
•
Process by agreement with the external device.
•
When necessary, change the simultaneous transmission data valid/invalid designation setting by GX Configurator-SC. (buffer memory addresses 9B
H
/13B
H
)
( 1)
•
Check if data was dropped from the receive data.
•
Check if DTR control, etc.
interrupted reception.
•
Check the status of the message transmission destination and restart data communications, as required.
•
Check if DTR control, etc.
interrupted transmission.
System error
•
The OS of the Q series C24 detected some error.
— ( 1)
7F67
7F68
H
H
Overrun error
Framing error
•
•
•
The Q series C24 received the next data before it completed receive processing of the previous data.
Data does not match the stop bit setting.
A malfunction occurred in the network because the power source of the partner station was on or off.
•
Noise occurs in the network.
•
When the multidrop was connected, data was transmitted simultaneously by multiple devices.
SIO
SIO
•
Decrease the data transmission rate and restart data communications.
•
Check whether a temporary stop has occurred in the station in which the Q series C24 is installed. (For the QCPU this can be checked using special register
SD1005.) If a temporary stop has occurred, remove its cause.
•
Match the Q series C24 and external device settings.
•
Clear the error information according to the error information initialization request
(YE/YF).
In addition, when communicating data with the non procedure protocol, execute the INPUT instruction, and read and discard the unnecessary data.
•
Measure the noise.
•
When connecting the multidrop, remove the interlock so that data will not be transmitted simultaneously by multiple devices.
MC
Protocol
Non
Procedure
Bidirectional
10 - 20 10 - 20
10 TROUBLESHOOTING
MELSEC-Q
Error code
(Hexadecimal)
Error
Error Contents
Signal name
Corrective action
7F9E
H
7FA0
H to
7FA3
H
7FA8
H
7FAA
H to
7FAD
H
7FAF
H to
7FB2
H
7FB5
H
7FB6
H
7FB8
H to
7FBC
H
7F91
H to
7F96
H
7F98
H to
7F9A
H
7F9D
H
7FC0
H to
7FC4
H
System error
7F69
7F6A
7F6B
H
H
H
Parity error
Buffer full error
CD signal control error
7F6C
H
Transmission error
•
•
•
•
Data does not match the parity bit setting.
A malfunction occurred in the network because the power source of the partner station was on or off.
Noise occurs in the network.
When the multidrop was connected, data was transmitted simultaneously by multiple devices.
•
OS receive buffer overflowed and receive data was skipped.
•
Data was received when CD signal is OFF when
•
"CD terminal check enabled" was designated.
Data cannot be sent because the line is not connected.
P/S
SIO
CHn
ERR.
CHn
ERR.
•
Match the Q series C24 and external device settings.
•
Clear the error information according to the error information initialization request
(YE/YF).
In addition, when communicating data with the non procedure protocol, execute the INPUT instruction, and read and discard the unnecessary data.
•
Measure the noise.
•
When connecting the multidrop, remove the interlock so that data will not be transmitted simultaneously by multiple devices.
•
Use DTR and DC control and perform data communications so that the buffer does not become full. (Perform RS
⋅
CS control when the modem function is used.)
•
If the Read Request signal was turned ON, execute read immediately.
•
Recheck the CD signal control of the external device.
(Send while the CD signal is ON.)
•
Set "no CD terminal checking" and perform communication.
•
Transmit data after line connection processing on the interface side that uses the modem function.
•
The OS of the Q series C24 detected some error.
— ( 1)
MC
Protocol
Non
Procedure
Bidirectional
10 - 21 10 - 21
10 TROUBLESHOOTING
MELSEC-Q
Error code
(Hexadecimal)
7FC9
H to
7FCF
H
7FE6
H
Error
System error
Error Contents
•
The OS of the Q series C24 detected some error.
Signal name
( 1)
Corrective action
7FF8
H
7FFF
H
B000
H to
BFFF
H
C000
H to
CFFF
H
F000
H to
FFFF
H
7FE7
H
Processing disabled
•
Remote passwords do not match.
•
The remote password is not registered.
•
The remote password processing command was received on the interface side where the modem function is not used.
•
The GX Developer connection is selected in the communication protocol setting on the corresponding CH.
7FE8
H
•
The number of remote password disagreements exceeded the value designated at the address
200D
H
.
7FEF
H
Switch setting error
•
There is an error in the switch setting by the GX
Developer
7FF0
H
Dedicated instructions simultaneous execution error
•
Executed dedicated instructions simultaneously.
7FF1
7FF2
H
H
Control data error
Communication protocol setting error
•
Setting value is incorrect.
•
Setting value is out of range.
•
Instruction cannot be executed with the current communication protocol.
7FF3
H to
7FF4
H
System error
•
The OS of the Q series C24 detected some error.
7FF5
H
Processing canceled due to mode switching/transmiss ion sequence initialization
•
The processing was canceled due to mode switching or receive data clear executed during the processing.
7FF7
H
Simultaneous access error
•
Multiple external devices accessed a remote station on the same network at the same time.
CHn
ERR.
CHn
ERR.
CHn
ERR.
•
Check the remote password and communicate again.
•
A remote password processing command is not necessary when a remote password is not registered.
•
Perform a remote password unlock processing through GX
Developer. Alternatively, change the communication protocol setting of the corresponding CH to the MC protocol.
•
Clear the storage area of the cumulative number of abnormal completions of unlock processing
(address: 22FC
H
) to 0.
•
Write CPU to the parameter and reboot after correcting the setting value for the switch.
—
(
•
•
•
•
Do not use dedicated instructions simultaneously.
Correct the setting value in the control data.
Correct the setting value of the communication protocol.
1)
Do not execute mode switching/receive data clear during any processing.
System error
•
•
•
•
The OS of the Q series C24 detected some error.
Errors detected by the CC-Link module
Errors detected by the Ethernet module
Errors detected by the MELSECNET/H,
MELSECNET/10 network system
—
—
—
•
Multiple external devices must not access a remote station on the same network at the same time.
( 1)
•
Take corrective action by referring to the CC-Link
Master/Local Module User's
Manual.
•
Take corrective action by referring to the Ethernet
Interface Module User's Manual.
•
Take corrective action by referring to MELSECNET/H,
MELSECNET/10 network system reference manual.
MC
Protocol
Non
Procedure
Bidirectional
10 - 22 10 - 22
10 TROUBLESHOOTING
MELSEC-Q
1 Take corrective action in the following procedure.
1) Check whether the Q series C24, power supply module and CPU module are mounted correctly on the base unit.
2) Check whether the operating environment of the Q series C24 is within the general specifications range of the CPU module.
3) Check whether the power supply capacity is sufficient or not.
4) Check whether the hardware of the Q series C24, CPU module and base unit are normal according to the manuals of the corresponding modules.
If any module is faulty, please contact your local Mitsubishi service center or representative for repair.
5) If the problem cannot be solved through the above steps, please consult your local Mitsubishi service center or representative, explaining a detailed description of the problem.
10 - 23 10 - 23
10 TROUBLESHOOTING
MELSEC-Q
10.2.2 A compatible 1C frame communications error code table
Error code
(Hexadecimal)
00
H
01
H
02
H
03
H
04
H
05
H
06
H
07
H
08
H
10
H
11
H
12
H
21
H
42
H
Error
The following table lists the error code, error contents, and corrective action for errors generated during A compatible 1C frame communications.
Error Contents
Signal name
Corrective action
MC
Protocol
Non
Procedure
Bidirectional
Disable during
RUN
Parity error
Sum check error
Protocol error
Framing error
Overrun error
Character area error
Character error
PLC access error
PLC No. error
Mode error
Special function module designation error
Special function module bus error
•
A write command was designated when "Disable write during RUN" was set.
•
Parameter or sequence program was written during
•
•
•
•
•
•
RUN.
The data does not match the parity bit setting.
•
The sum check calculated by the Q series C24 and the transmitted sum check are not the same.
Received message that is different from the control procedure with the communication protocol setting.
The PLC No. is not "FF", or a station No. set in the network parameters.
An error was detected upon access to the PLC
CPU.
A special function module does not exist at the specified position.
An error was detected upon access to a special function module at the specified position.
C/N
P/S
P/S
PRO
SIO
SIO
•
Change the setting to "Enable write during RUN" and restart data communications.
•
Stop the CPU and restart data communications.
•
Match the Q series C24 and external device settings.
•
Check the external device sum check.
•
Check and correct the external device transmit message and restart data communications.
•
Match the Q series C24 and external device settings.
•
Decrease the transmission rate and restart data communications.
•
The data does not match the stop bit setting.
•
The next data was received before the Q series C24 received all the preceding data.
•
Designation method error in part of a message.
•
A command that does not exist was designated.
•
The number of processing points is outside the range for the command.
•
A device that does not exist was designated.
•
Received data that cannot be used.
•
The CPU cannot communicate with the Q series
C24.
PRO
PRO
C/N
•
Check and correct the external device transmit message and restart data transmission.
C/N
—
C/N
C/N
•
Replace the CPU with a CPU that can communicate with the Q series C24.
•
Check and correct the external device transmit message and restart data communications.
•
Send again.
•
Conduct individual station recovery test and check the Q series C24.
•
Check and correct the external device transmit message and restart data communications.
•
Check the error and take corrective action according to the manual of the corresponding module.
Other errors
POINT
•
If an error occurs during A compatible 1C frame communications, the Q series C24 adds a 2-character error code (00
H
to 10
H
, 42
H
) to the "NAK" code and returns the
"NAK" code to the external device and stores the error code (equivalent to QnA compatible 2C/3C/4C frame error code) to buffer memory address 25A
H
(CH1) or
26A
H
(CH2).
The exact error contents can be checked by reading the value stored to the buffer memory.
See Section 10.2.1 for a detailed description of the error codes.
10 - 24 10 - 24
10 TROUBLESHOOTING
MELSEC-Q
10.2.3 Error code list while modem function is used
The following describes the error codes, contents and corrective actions for errors
(including errors at the abnormal completion) that may occur while the Q series C24 modem function is used.
The error codes for the modem function are stored in the modem function error code storage area (address : 221
H
(545)) of the buffer memory.
The reference pages listed in the table below are found in the User's Manual
(Application).
Error code
(Hexadecimal)
Error
Error Contents
Signal name
Corrective action
7FD0
7FD1
7FD2
7FD3
7FD4
7FD5
7FD6
7FD7
7FD8
7FD9
7FDA
7FDB
7FDC
7FDD
7FDE
H
H
H
H
H
H
H
H
H
H
H
H
H
H
H
Modern function error
Modern function error
There is an error in the designation of the notification execution.
There is an error in the designation of the number of connection retries.
There is an error in the designation of the connection retry interval.
There is an error in the initialization/connection timeout designation.
There is an error in the designation of the number of initialization retries.
There is an error in the designation of the data number for initialization.
There is an error in the data for connection designated by the data number for connection.
System error The OS of the Q series C24 detected some error.
External destination is connected to network or modem has not been initialized.
There is an error in the designation of the data number for connection.
There is an error in the designation of the GX
Developer connection.
There is an error in the data for connection designated by the data number for connection.
A connection time-out error occurred.
Connection to the modem/TA was unsuccessful, or the modem/TA is not connected.
CHn
ERR.
CHn
ERR.
Set 0 to 1 to the notification execution designation.
Set the number of connection retries in the range of 1 to 5.
Set the connection retry interval in the range of 90 to 300 (s).
Set the initialization/connection time- out in the range of 1 to 60 (s).
Set the number of initialization retries in the range of 1 to 5.
Designate the registered data number for initialization, or 0.
Recheck the pager receiver designation.
Recheck the dialing number of the external line.
( 1)
After the modem has been initialized, connect to the network if the external destination is not connected to the network or report it.
Designate a registered number for the data for connection.
Set 0 to 1 to the GX Developer connection designation.
Recheck the waiting time for the notification-message part of the message transmission.
•
Recheck the telephone number in the data for connection.
•
Check if the destination is ready for a connection.
•
Recheck the set value of the connection time-out.
•
Recheck the initialization command.
•
Check if there is any problem with the modem/TA by seeing the operation manual of the modem/TA.
•
Connect the modem/TA to the Q series
C24.
•
Check the connection cable by seeing the operation manual of the modem/TA.
7FDF
H
7FE0
H
Modem connection channel number is not designated.
Designated value of modem connection channel is incorrect.
Set 1 to 2 to the modem connection channel designation.
Reference section
Section 3.3.6
Section 3.3.6
Section 3.4.5
Section 3.4.4
Section 3.4.6
Section 3.4.7
Section 3.3.6
Section 3.4.6
Section 3.3.6
Section 3.4.4
Section 3.3.6
Section 3.4.3
Section 3.4.4
—
Section 3.3.6
10 - 25 10 - 25
10 TROUBLESHOOTING
MELSEC-Q
Error code
(Hexadecimal)
7FE1
H
7FE2
H
Modern function error
7FE3
H
7FE4
H
7FE5
H
7FE8
H
7FE9
H
Error
There is an error in the designation of the user frame number.
There is an error in the designation of the output head pointer.
Callback denial exceeded the value designated at the address 2002
H
Error Contents
There is an error in the designation of the output frame number.
There is an error in the designation of the number of registered data bytes.
There is an error in the data for connection.
There is an error in the designation of the nocommunication interval time.
The number of remote password mismatch exceeded the value designated at the address 200D
H
.
Signal name
Corrective action
CHn
ERR.
•
Recheck the user frame number.
•
Designate the registered user frame number.
•
Register the designated data for initialization.
•
Designate the output head pointer in the range of 1 to 100.
•
Designate the position (n-th position) where the data for initialization number is designated.
•
Designate the data for initialization number at the designated position
(n-th position).
Designate a registered data for initialization number within the range of the designated number of outputs from the location of the output head pointer.
•
Designate the data for initialization in the range of 1 to 78.
•
Designate 80 for the data for connection.
•
Recheck the message length of the message for notification.
•
Designate the no-communication interval time in the range of 0 to 120.
•
Clear the storage area of the
Accumulated count of unlock process abnormal completion (address: 22FC
H
) to 0.
•
Clear the storage area of the callback denial accumulated count (address:
22F1
H
) to 0.
Reference section
Section 3.4.3
Section 3.4.4
Section 3.4.5
Section 3.4.5
Section 3.4.3
Section 3.4.4
Section 3.4.4
Section 3.3.6
Section 3.3.3
Section 3.3.4
1 Take corrective action in the following procedure.
1) Check whether the Q series C24, power supply module and CPU module are mounted correctly on the base unit.
2) Check whether the operating environment of the Q series C24 is within the general specifications range of the CPU module.
3) Check whether the power supply capacity is sufficient or not.
4) Check whether the hardware of the Q series C24, CPU module and base unit are normal according to the manuals of the corresponding modules.
If any module is faulty, please contact your local Mitsubishi service center or representative for repair.
5) If the problem cannot be solved through the above steps, please consult your local Mitsubishi service center or representative, explaining a detailed description of the problem.
10 - 26 10 - 26
advertisement
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Related manuals
advertisement
Table of contents
- 3 SAFETY PRECAUTIONS
- 7 REVISIONS
- 9 INTRODUCTION
- 9 CONTENTS
- 17 About Manuals
- 17 Conformation to the EMC Directive and Low Voltage Instruction
- 18 The Manual's Use and Structure
- 21 About The Generic Terms and Abbreviations
- 23 Definitions and Descriptions of Terminology
- 25 Product Configuration
- 26 1 OVERVIEW
- 26 1.1 Overview of the Serial Communication Module
- 27 1.2 Features of the Serial Communication Module
- 35 1.3 About Added/Changed Functions in Function Version B
- 37 2 SYSTEM CONFIGURATION AND AVAILABLE FUNCTIONS
- 37 2.1 Applicable Systems
- 39 2.2 Combinations of PLC CPU and External Device, and Available Functions
- 42 2.3 For Use in Multiple CPU System
- 43 2.4 For Use with Q00J/Q00/Q01CPU
- 44 2.5 For Use at MELSECNET/H Remote I/O Station
- 48 2.6 Checking the Function Version, Serial No., and Software Version
- 51 3 SPECIFICATIONS
- 51 3.1 Performance Specifications
- 53 3.2 RS-232 Interface Specification
- 53 3.2.1 RS-232 connector specifications
- 55 3.2.2 RS-232 cable specification
- 56 3.3 RS-422/485 Interface Specifications
- 56 3.3.1 RS-422/485 terminal block specifications
- 57 3.3.2 RS-422/485 cable specifications
- 58 3.3.3 Precautions when transferring data using RS-422/485 circuit
- 61 3.4 Serial Communication Module Function List
- 62 3.5 Dedicated Instruction List
- 63 3.6 Utility Package (GX Configurator-SC) Function List
- 64 3.7 List of GX Developer Setting Items for Serial Communication Modules
- 65 3.8 List of Input/Output Signals for the PLC CPU
- 67 3.9 List of Applications and Assignments of the Buffer Memory
- 82 4 SETTINGS AND PROCEDURES PRIOR TO OPERATION
- 82 4.1 Handling Precautions
- 83 4.2 Settings and Procedures Prior to Operation
- 84 4.3 Part Names and Functions
- 86 4.4 External Wiring
- 87 4.4.1 Connecting the RS-232 interface (full-duplex communications)
- 89 4.4.2 Connecting the RS-422/485 interface
- 93 4.5 Settings for GX Developer
- 93 4.5.1 I/O assignment settings
- 94 4.5.2 Switch settings for I/O and intelligent functional module
- 101 4.5.3 The Intelligent function module interrupt pointer setting
- 103 4.6 Settings with the Utility Package (GX Configurator-SC)
- 106 4.7 Individual Station Test
- 106 4.7.1 ROM/RAM/switch tests
- 109 4.7.2 Individual station loopback test
- 111 4.8 Loopback Test
- 113 4.9 Maintenance and Inspection
- 113 4.9.1 Maintenance and inspection
- 114 4.9.2 When mounting/dismounting the module
- 115 5 DATA COMMUNICATION USING THE MELSEC COMMUNICATION PROTOCOL
- 115 5.1 Data Communication Functions
- 115 5.1.1 Accessing the PLC CPUs using the MC protocol
- 116 5.1.2 Message format and control procedure for data communication
- 116 5.1.3 PLC CPU setting for performing data communication
- 117 5.1.4 Support of multiple CPU system or redundant system
- 118 5.1.5 Support for the QCPU remote password function
- 120 5.2 Utilizing the MX Component
- 121 6 DATA COMMUNICATION USING THE NON PROCEDURE PROTOCOL
- 122 6.1 Data Reception from the External Device
- 122 6.1.1 Receiving methods
- 126 6.1.2 The receive area and the received data list
- 131 6.1.3 Sequence program for data reception
- 134 6.1.4 Receive data clear
- 137 6.1.5 How to detect reception errors
- 140 6.1.6 Received data count and receive complete code settings
- 142 6.2 Sending Data to the External Device
- 142 6.2.1 Transmission methods
- 143 6.2.2 Arrangement and contents of the transmission area and the transmission data
- 145 6.2.3 Sequence program for transmission data
- 148 6.2.4 How to detect transmission errors
- 150 6.3 Data Communications Precautions
- 152 7 DATA COMMUNICATION USING THE BIDIRECTIONAL PROTOCOL
- 153 7.1 Data Reception from the External Device
- 153 7.1.1 Receiving methods
- 155 7.1.2 Arrangement and contents of the receive area and the receive data
- 161 7.1.3 Sequence program for data reception
- 164 7.1.4 How to detect reception errors
- 165 7.1.5 Receive data clear
- 166 7.2 Sending Data to the External Device
- 166 7.2.1 Transmission methods
- 167 7.2.2 Arrangement and contents of the transmission area and the transmission data
- 170 7.2.3 Sequence program for data transmission
- 173 7.2.4 How to detect transmission errors
- 175 7.3 Processing when Simultaneous Transmission Performed During Full-Duplex Communications
- 175 7.3.1 Processing when simultaneous transmissions occur
- 176 7.3.2 Communication data processing when simultaneous transmissions occur
- 178 7.4 Data Communications Precautions
- 180 8 UTILITY PACKAGE (GX Configurator-SC)
- 181 8.1 Functions Available with Utility Package
- 182 8.2 Installing and Uninstalling Utility Package
- 182 8.2.1 Usage precautions
- 184 8.2.2 Operating environment
- 185 8.3 Explanation of Utility Package Operation
- 185 8.3.1 Operation overview
- 189 8.3.2 Starting the intelligent function module utility (displaying the [select parameter setting module] screen)
- 192 8.3.3 Performing common utility operations
- 195 8.4 System Registration to Flash ROM
- 197 8.4.1 User frame registration
- 198 8.4.2 Data for modem initialization registration
- 199 8.4.3 Data for modem connection registration
- 200 8.4.4 Modem function system setting/registration
- 201 8.4.5 Transmission control and others system setting
- 203 8.4.6 MC protocol system setting
- 204 8.4.7 Non procedure system setting
- 205 8.4.8 Bidirectional system setting
- 206 8.4.9 PLC CPU monitoring system setting
- 208 8.4.10 Transmission user frame No. designation system setting
- 209 8.4.11 Resetting the buffer memory/flash ROM setting values to the default values
- 209 8.4.12 Flash ROM write allow/prohibit setting
- 210 8.5 Auto Refresh Setting
- 211 8.6 Monitor/Test
- 212 8.6.1 X · Y monitor/test
- 213 8.6.2 Modem function monitor/test
- 216 8.6.3 Transmission control and others monitor/test
- 218 8.6.4 MC protocol monitor
- 220 8.6.5 Non procedure monitor/test
- 222 8.6.6 Bidirectional monitor
- 223 8.6.7 PLC CPU monitoring monitor
- 225 8.6.8 Transmission user frame No. designation monitor
- 226 8.6.9 Monitor/test others
- 228 8.6.10 Display LED off and communication error information/error code initialization
- 230 8.7 Non Procedure Protocol Receive Data Clear
- 231 9 DEDICATED INSTRUCTIONS
- 231 9.1 Dedicated Instruction List
- 232 9.2 ONDEMAND Instruction
- 235 9.3 OUTPUT Instruction
- 238 9.4 INPUT Instruction
- 241 9.5 BIDOUT Instruction
- 244 9.6 BIDIN Instruction
- 247 9.7 SPBUSY Instruction
- 249 9.8 CSET (Receive data clear)
- 252 10 TROUBLESHOOTING
- 252 10.1 Checking the Status of the Serial Communication Module
- 252 10.1.1 Checking the LED ON status, communications error status, and switch setting status of the serial communication module
- 257 10.1.2 Initializing error information of the serial communication module
- 260 10.1.3 Reading the RS-232 control signal status
- 261 10.1.4 Reading the data communication status (Transmission sequence status)
- 262 10.1.5 Reading the switch setting status
- 264 10.1.6 How to read the current operation status
- 266 10.2 Error Code Tables
- 266 10.2.1 Error code table
- 275 10.2.2 A compatible 1C frame communications error code table
- 276 10.2.3 Error code list while modem function is used
- 278 10.3 Troubleshooting by Symptom
- 280 10.3.1 Troubleshooting when "RUN" LED is turned OFF
- 281 10.3.2 Troubleshooting when "RD" LED does not blink even though an external device is transmitting a message
- 282 10.3.3 Troubleshooting when the Q series C24 does not return a response message even though an external device ...
- 283 10.3.4 Troubleshooting when an external device transmitted a message and "RD" LED blinked, but the Read Request signal ...
- 284 10.3.5 Troubleshooting when communication error "NAK" generates
- 284 10.3.6 Troubleshooting when communication error "C/N" generates
- 285 10.3.7 Troubleshooting when communication error "P/S" generates
- 286 10.3.8 Troubleshooting when communication error "PRO." generates
- 287 10.3.9 Troubleshooting when communication error "SIO" generates
- 288 10.3.10 Troubleshooting when communication error "CH1 ERR.", "CH2 ERR." generate
- 289 10.3.11 Troubleshooting when communications is intermittently established and lost
- 290 10.3.12 Troubleshooting when data that cannot be decoded is transmitted and received
- 291 10.3.13 Troubleshooting when it is unclear whether the communication error cause is in the Q series C24 or an external device
- 292 10.3.14 Troubleshooting when data cannot be communicated via modem
- 293 10.3.15 Troubleshooting when data cannot be communicated with the ISDN sub-address
- 293 10.3.16 Troubleshooting when constant cycle transmission does not operate normally
- 293 10.3.17 Troubleshooting when condition agreement transmission does not operate normally
- 293 10.3.18 Troubleshooting when data cannot be received by an interrupt program
- 293 10.3.19 Troubleshooting when data cannot be written to Flash ROM
- 294 10.3.20 Troubleshooting when the "ERR" LED is lit
- 295 APPENDIX
- 295 Appendix 1 Functional Improvements of the Q Series C24
- 295 Appendix 1.1 Comparison of the Functions of Q Series C24/GX Configurator-SC
- 299 Appendix 1.2 Precautions when Updating the Module from Function Version A to B
- 300 Appendix 2 QnA/A Series Module
- 300 Appendix 2.1 Functional Comparison with the Q series C24 and the QnA/A Series Modules
- 302 Appendix 2.2 Using Programs Designed for the QC24 (N) and Installing the Q Series C24 into Existing Systems
- 302 Appendix 2.2.1 Using programs designed for the QC24 (N)
- 303 Appendix 2.2.2 Installing on existing systems
- 304 Appendix 2.3 Using Programs Designed for the Computer Link Module and Installing the Q Series C24 into Existing Systems
- 304 Appendix 2.3.1 Using programs designed for the computer link module
- 307 Appendix 2.3.2 Installing the Q series C24 into existing systems
- 308 Appendix 3 Processing Time
- 311 Appendix 4 ASCII-Code Table
- 312 Appendix 5 External Dimensions
- 314 Appendix 6 Example of Connection when a Converter is Used
- 317 Appendix 7 Communication Support Tool (MX Component)
- 317 Appendix 7.1 Overview of MX Component
- 320 Appendix 7.2 Usage Procedure of MX Component
- 324 Appendix 8 Example of Clear Process Program for Receive Data
- 326 Appendix 9 Program Examples for Using Q Series C24 at MELSECNET/H Remote I/O Station
- 326 Appendix 9.1 System configuration and program conditions
- 328 Appendix 9.2 When accessing buffer memory using sequence program
- 329 Appendix 9.3 When sending on-demand data
- 331 Appendix 9.4 When receiving data using nonprocedural or bidirectional protocol
- 333 Appendix 9.5 When sending data using nonprocedural or bidirectional protocol
- 335 Appendix 9.6 When clearing received data
- 337 Appendix 9.7 When sending data using user frames
- 340 Appendix 9.8 When performing initial setting
- 342 Appendix 9.9 When registering user frame
- 344 Appendix 9.10 When reading user frame
- 346 Appendix 9.11 When deleting user frame
- 348 Appendix 9.12 When changing the communication protocol and transmission setting
- 351 Appendix 10 Setting Value Recording Sheet
- 353 INDEX
- 355 WARRANTY