6
FUNCTIONS
6.24 Serial Communication Function
6
- 185
1
O
verv
iew
2
Per
fo
rma
nce
S
p
ecifica
tio
n
3
S
equ
en
ce P
ro
g
ra
m
Co
nfig
ura
tio
n a
nd
E
xecut
io
n Co
nd
iti
o
ns
4
I/O N
unb
er
Assig
n
m
e
nt
5
Me
mor
ie
s a
nd
File
s
Ha
nd
led
by CP
U Mo
du
le
6
Func
tions
7
Co
mmu
nic
a
tion
us
in
g
bu
ilt
-i
n E
th
e
rne
t po
rt
s o
f
CP
U mod
u
le
8
Co
mm
un
icatio
n
w
ith
Int
e
lli
ge
nt
Fun
ction
Mo
du
le
(7) Error codes for communication made using serial communication
function
Table6.56 indicates the error codes, error definitions and corrective actions that are
sent from the CPU module to the external device when errors occur during
communication made using the serial communication function.
(Continued on next page)
Table6.56 List of error codes sent from CPU module to external device
Error Code
(Hexadecimal)
Error Item
Error Definition
Corrective Action
4000
H
----
• CPU detected error
(Error that occurred in other than the serial com-
munication function)
• Refer to the Appendices of the QCPU User's Manual
(Hardware Design, Maintenance and Inspection), and take
corrective action.
to
4FFF
H
7153
H
Frame length error
• The length of the received message is outside the
permissible range.
• Reconsider the sent message.
• The number of access points of the message should be
within the permissible range.
7155
H
Unregistered
monitor error
• A monitor request was given before monitor
registration was made.
• Give a monitor request after registering the device to be
monitored.
7164
H
Requested data
error
• The requested data or device specifying method is
in error.
• Check and correct the sent message/requested data of the
device on the other end, and restart communication.
7167
H
Disabled during
RUN
• A write command was specified for the setting of
online change disable.
• Change the setting to online change enable and restart
communication.
7168
H
• The command specified cannot be executed
during RUN.
• Set the CPU module to STOP and restart communication.
716D
H
Monitor registration
error
• The QnA-compatible 3C/4C frame was not used
for monitor registration.
• Perform monitor registration again.
7E40
H
Command error
• The command or sub-command specified does not
exist.
• Check and correct the sent message of the device on the
other end and restart communication.
7E41
H
Data length error
• The number of points specified for random write/
read exceeds the number of points enabled for
communication.
• Check and correct the sent message of the device on the
other end and restart communication.
7E42
H
Data count error
• The requested number of points exceeds the
range of the command.
• Check and correct the sent message of the device on the
other end and restart communication.
7E43
H
Device error
• The device specified does not exist.
• The device specified cannot be specified for the
corresponding command.
• Check and correct the sent message of the device on the
other end and restart communication.
7E47
H
Continuous request
error
• The next request was received before the reply
message was returned.
• Do not give continuous requests from the device on the
other end.
• Match the monitoring time of timer 1 with the time-out period
of the device on the other end.
7E4F
H
Device point count
error
• The number of access points is incorrect.
• Check and correct the sent message of the device on the
other end and restart communication.
7E5F
H
Request destination
module I/O number
error
• The request destination module I/O number is in
error.
• Correct the module I/O number of the data send destination.
7E64
H
Registered point
count range error
• The number of registered points (word/bit) is
outside the range.
• Correct the set value of the registered points (word/bit).
7F01
H
Buffer full error
• The next data was received before completion of
received data processing.
• Perform handshake with the device on the other end, for
example, to increase the sending intervals.
7F21
H
Receive header
section error
• The command (frame) section specified is in error.
• Check and correct the sent message of the device on the
other end and restart communication.
• The ASCII code received cannot be converted into
binary.