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