8 - 16                     8 - 16
MELSEC-Q
8   TROUBLESHOOTING
(2)   From monitoring the network status to troubleshooting of a faulty
station
The following flowchart illustrates the procedure for monitoring the status of the
entire network, detecting a faulty station, and then performing troubleshooting for
the applicable station.
The status of the entire network is monitored with GX Developer.
Start troubleshooting
Check the data link status 
of the remote master station 
with GX Developer's  
network diagnostics.
No
(Execute the cyclic transmission)
Yes
No
A
Yes
Check the stations that are 
not executing data linking.
Check the baton pass status 
of the applicable station with 
GX Developer's network 
monitor.
Did a LINK 
PARA ERROR occur 
in the remote master
station's CPU?
No
Is the applicable 
station waiting 
for parameter 
communication? 
(SB54: On?)
No error
Value of SW49?
Is the applicable 
station executing the baton 
pass normally?
Yes
Check that the network 
setting and the installation 
position of the master 
module match. 
Conduct PC diagnostics.
Error
Value 4: The 
remote I/O module 
of the host is faulty.
Check the status of the
remote I/O module of the host.
Is the value of 
the link monitoring time 
parameter sufficient 
for the system?
Value of SW47?
Value 2: Data linking stopped
Problem
Check SB00 to 03 and SW00 
to 04.
Try setting the link monitoring 
time to the maximum value.
Value 1 :
Data linking 
stopped
Check SW4A.
Check the data linking stop 
request station and the 
designation method.
No
Check with SB70 to 72 
and SW70 to 73.
Review the common 
parameters and station 
inherent parameters.
Value 2 : No common 
parameters
Value 3 : Abnormal 
common parameters
Set the common 
parameters.
Is only the 
transient transmission 
used?
B
SW47: Host baton pass status
SW48: Cause of host baton pass interruption
SW49: Cause of host data linking stop
SW54: Parameter information
SW55: Parameter setting status
C
D
Yes
Reexamine the remote 
master station network type. 
Use GX Developer system 
monitor to check whether or 
not the function version of the
master module is Version B. 
Are all the 
stations executing 
data linking 
normally?
Value 1: 
Stop designated
Value 6: 
Communication 
stopped
No problem