27 TROUBLESHOOTING
27.4 Error Code List
483
27
7F20H ASCIIBIN
conversion error
• When the nonprocedural
or bidirectional protocol is
used, an ASCII code that
cannot be converted to
binary code was received.
• When the nonprocedural
or bidirectional protocol is
used, an odd number of
bytes of data was
received during data
communications using
ASCII BIN conversion.
PRO • Check and correct the
transmission message from
the target device and restart
data communications.
• When the nonprocedural or
bidirectional protocol is used
and data is communicated
using ASCII BIN
conversion, be sure to send
data in units of even bytes.
• When data is received by
Conversion Variable of the
predefined protocol
function, the data
corresponding to the
Conversion Variable
cannot be converted to
binary numbers.
• When data is received by
a Check code (ASCII
hexadecimal or ASCII
decimal) of the predefined
protocol function, the data
corresponding to the
check code cannot be
converted to binary
numbers.
PRO ■If the predefined protocol was
edited, check if the following
values match the packet format
of the target device:
• Conversion, sign character,
number of decimals, delimiter,
number of digit for conversion
variable
• Code type and data length of
check code
7F21H Receive header
area error
• The command (frame)
part designation has an
error.
• An ASCII code that
cannot be converted to
binary code was received.
PRO • Check and correct the
transmission message from
the target device and restart
data communications.
7F22H Command error • A nonexistent command,
subcommand, or device
was designated.
• The remote password
length is incorrect.
PRO • Check and correct the
transmission message from
the target device and restart
data communications.
7F23H MC protocol
message error
• There is no data (ETX,
CR-LF, etc.) following the
character area, or the
designation was incorrect.
PRO • Check and correct the
transmission message from
the target device and restart
data communications.
7F24H Sum check error • The sum check code
calculated does not match
the sum check code
received.
• The horizontal parity code
calculated does not match
the horizontal parity code
received.
• The calculated check
code does not match the
received check code.
P/S • Review the sum check code of
the target device.
• Review the horizontal parity
code of the target device.
• Review CRC-16 of the target
device.
■If the predefined protocol was
edited, check if the following
values match the packet format
of the target device:
• Processing method or code
type of the check code
• Data length
• Data flow
•
Complement calculation
• Calculating range
Error code
(hexadecima
l)
Error Description Signal
name
Corrective action Protocol
MC Nonpr
ocedu
ral
Bidire
ctiona
l
Prede
fined