When an error message is displayed (Error code list)
Maintenance/Troubleshooting
1-136
RHxx072 (Node Name): Since
a buffer was insuffi-
cient, the read
request was un-
receivable
A read request was made
through sampling, extended
D-script, Pro-Server EX, etc.
to the device in off-scan
mode.
A read request was made
through sampling, extended
D-script, Pro-Server EX, etc.
to the device for which com-
munication scan has been
stopped. Turn OFF the
appropriate bit between
LS9550 and LS9559
*2
and
start the communication scan
of the connected device.
)
GP-Pro EX Reference Man-
ual “7.3 Disconnecting Multi-
ple Connected Devices/
PLCs” (page 7-11)
RHxx073 (Node Name): Since
a buffer was insuffi-
cient, the write
request was un-
receivable
A write request was made
through a script, a touch, Pro-
Server EX, etc. to the device
in off-scan mode.
A write request was made
through a switch, D-script,
extended D-script, Pro-
Server EX, etc. to the device
for which communication
scan has been stopped. Turn
OFF the appropriate bit
between LS9550 and
LS9559
and start the com-
munication scan of the con-
nected device.
)
GP-Pro EX Reference Man-
ual “7.3 Disconnecting Multi-
ple Connected Devices/
PLCs” (page 7-11)
RHxx084 (Node Name): Too
many requests to
write. The request
was ignored.
A write operation was con-
tinued at timing which
exceeds the processing speed
of the communication driver.
Example) When a write oper-
ation to a connected device
set up with a baud rate of
9600 is continued according
to the update timing of the
tag scan counter.
Check if a D-script or other
setting has been specified
which continues writing at
fast speed.
This error may occur when
writing to a device which
communicates at a low
speed such as 9600 bps is
continued with a D-script
using a bit which turns ON/
OFF at fast speed (such as
the LS2038 tag scan
counter).
Continued
Error No.
Error Message
Cause and Solution
Countermeasure