Troubleshoot the MELSEC Communication Driver

Code

Description

Possible Causes

Solution

1

Error Connect

IP address or port number is invalid

Check the IP Address and port number.

2

PLC Error or Invalid Memory Address

You may have tried to Read a memory from the PLC (Device) that is not present on that CPU

Check if the address (Device) configured does exist in the PLC

3

Check sum Error

The check sum byte received is not equal to the expected byte

Contact your technical support representative.

4

Protocol Error

The driver received an unexpected message from the device

Contact your technical support representative

0

OK

Communicating without error.

None required.

-15

Timeout waiting for message to start

• Disconnected cables.

• PLC is turned off, in stop mode, or in error mode.

• Wrong station number.

• Wrong parity (for serial communication).

• Wrong RTS/CTS configuration (for serial communication).

• Check cable wiring.

• Check the PLC mode — it must be RUN.

• Check the station number.

• Increase the timeout in the driver's advanced settings.

• Check the RTS/CTS configuration (for serial communication).

-17

Timeout between rx characters.

• PLC in stop or error mode

• Wrong station number

• Wrong parity

• Wrong RTS/CTS configuration settings

• Check the cable wiring

• Check the PLC stat e (it must be RUN)

• Check the station number

• Check the configuration. Review the Communication Parameters section for valid RTS/CTS configurations.

-37

INVALID HEADER

The header field specified in the driver worksheet is invalid

Check the supported header fields and use one of the supported headers

-39

INVALID BLOCK SIZE

Driver sheet is configured with range of addresses greater than the maximum block size. (This can be a single address specified outside of the supported range.)

Check the maximum block size and configure the driver sheet correctly. Specifically, check that the addresses are within the supported range.