Filter
Top Products
10 - 34 10 - 34
MELSEC-Q
10 TROUBLESHOOTING
Symptom Cause Corrective action MC
Bidirectional
Non
procedure
• An error was generated
on the MELSECNET/ H,
MELSECNET/10.
• The local station CPU
on the MELSECNET/H,
MELSECNET/10
generated an error.
• Check the error contents from the state of SB
and SW related to the MELSECNET/H,
MELSECNET/10 with the GX Developer
monitor, etc. and perform the checks and take
the corrective action described in the
MELSECNET/H, MELSECNET/10 reference
manual.
• Module installation
address designation
during communications
with intelligent function
module is incorrect.
• Change the transmit message designation data.
• Stop the CPU and restart data communications.
• Communication error
signal "C/N" turned on.
• A command that cannot
be transmitted during
RUN (sequence
program, parameters,
etc.) was transmitted, or
"Disable write during
RUN" is set.
• Set the "Enable/disable write during RUN"
switch to "Enable" by command.
10.3.7 Troubleshooting when communication error "P/S" generates
Symptom Cause Corrective action MC
Bidirectional
Non
procedure
• Data does not match the
parity bit setting.
• Check the Q series C24 and external device
data format and match the settings.
• Sum check codes do not
match.
• Check if the sum check code transmitted from
the external device is correct. (Recalculate)
• Communication error
signal "P/S" turned on.
• When CH1 and CH2 are
used in the linked mode,
the cable is not
connected to one of the
interface.
• When using CH1 and CH2 independently, check
that the Q series C24 is not in the linked mode.
• When using CH1 and CH2 in the linked mode,
also connect the cable to both of the interfaces.
Note
• If the cable is not connected to one of the
interfaces when CH1 and CH2 are used in
the linked mode, noise may enter and the
data may be destroyed and "Data cannot be
decoded" or "Communications error cause"
may occur.