When an error message is displayed (Error code list)
Maintenance/Troubleshooting
1-130
1.6.2 Display-related errors
Common to all Display models
Errors displayed when communication fails
The following error messages are displayed when there is a problem in the communica-
tion with the connected device (PLC, etc.).
• The following error messages are common to all drivers (device/PLC types).
For the specific errors of each device/PLC types, please refer to “GP-Pro EX
Device/PLC Connection Manual”.
Error No.
Error Message
Cause and Solution
Countermeasure
RHxx006 (Driver Name):(Port
Name) Received
data has been parity
error
An error occurred due to a
lack of receiving data.The
cause could be the noise or
loose connection.
Please check the noise sup-
pression and connector’s
insertion. If Memory-Link
method is used, please
check if the Data Length/
Parity Bit of host side and
the display side have the
same settings.
RHxx007 (Node Name):(Port
Name) Received
data has been fram-
ing error
RHxx008 (Driver Name): This
machine does not
have any Ethernet
interface
An error occurred when a
Ethernet-supporting driver is
selected in GP-Pro EX’s
[Device/PLC Settings] but
the data is transferred to the
main unit model which can-
not use Ethernet connection.
Please check if the main
unit model in use supports a
Ethernet connection.If it
does, please check if the
Display Type settings of
GP-Pro EX are correct.
RHxx009 (Driver Name):(Port
Name) Cannot use
the port
An error occurred when two or
more driver types are selected
to an identical COM port.
Please check the port set-
tings in GP-Pro EX’s
[Device/PLC Settings].
RHxx010 (Driver Name): TCP
port number
∗∗∗∗∗
is
overlapped, or it is
not completed to
close the last TCP
connection
TCP port number of the dis-
play unit side is overlapped,
or the device/PLC is reset
during communication.
(1) If TCP port number is
overlapped, allocate dif-
ferent port number.
(2) Reset the main unit.
RHxx011 (Driver Name): Con-
nection was closed
An error occurred in the con-
nection environment during
communication.
Please check if the network
environment is nor-
mal.Please specify the
cause via procedures such
as directly connecting PC,
GP and device/PLC, and
then checking if IP address
is recognized via PING
command.
Continued
