Troubleshoot the SOMAC Communication Driver

Code

Description

Possible Causes

Solution

1

PLC not connected

• Lost connection to the PLC due to a hardware failure,such as PLC in error node,or cables issues.

• Wrong Station field configuration.

• Check the Station field configuration,confirming that the IP Addresses for the Gateway (if it is used) and the PLC are correct, as well as the PLC ID number in hexadecimal format.

• Check if the PLC is running and if you can ping it.

2

Login to PLC has failed

Some devices only allow a log-in of one application.

If there is another program connected to the PLC, you need to disconnect it (i.e.,log off). Then you should be able to communicate with the PLC.

3

No cyclic list has been found

Invalid list or no list variables to read.

Internal error related to the PLC Handler functions CycDefineVarList and CycEnterVarAccess.

4

PLCHandler is inactive

PLCHandler instance is not set active.This error happens when you use the INI file option and it is misconfigured.

Properly configure the INI file and the Station field.

5

Loading of the symbols has failed

There is no symbol configuration in the application.

Create the Symbol Configuration accordingly.

6

The defined communication interface is not valid or not supported

The interface is not supported(ARTI,Gateway). This error happens when trying to establish a connection with the PLC.

Check if your SOMAC configuration supports the desired interface(GATEWAY,ARTI, INI file).

7

Communication error occurred during action

• Error while trying to start the communication with the PLC.

• Exceeded number of retries to receive a response from the PLC before throwing a COMM_FATAL. Related to the PLCHanlder PlcConfig Struct.

Check if your PLC is properly configured and reachable.

8

Wrong or erroneous configuration of the PLCHandler

No configuration for this PLCHandler instance (Id unknown).This error happens when trying to establish a connection with the PLC and you are using a INI file that is not properly configured for that PLC instance.

Properly configure the INI file.

9

Invalid parameter

Invalid function parameters (fore.g.NULL).Usually happens when trying to retrieve the Variable Names from the PLC.

Internal error related to the PLCHandler functions GetAllItems, GetItem, and CycEnterVarAccess.

10

Communication interface not resp.Incorrectly installed (e.g.,Gateway Dlls not available)

The interface can’t start successfully (missing interface-dependent DLLs).This error happens when trying to establish a connection with the PLC.

If you are using the Gateway,check to see if it properly installed and running.

11

Method not yet supported resp.implemented

Spare error.

Not applicable.

12

Exception occurred during action

An exception occurred in the underlying interface. This error happens when transferring any application service to the PLC.

Internal driver error related to the PLCHandler function SyncSendService.

13

Timeout time exceeded

Time for the answer on a data package from the PLC exceeded. This could be caused by a wrong Station field configuration or the PLC is unreachable.

• Check the Station field.

• Check if you can have access to the PLC using pinging and testing the TCP/IP ports

14

PLC already connected(at a further::Connect function call)

The driver tried to reconnect to a PLC that is already connected.

Internal error related to the PLCHandler function Connect.

15

Reconnect thread already active

Reconnect thread is still active.This error happens when trying to establish a connection with the PLC.

Internal error related to the PLCHandler function Connect.

16

Symbols available offline

Cannot open connection to the PLC but could load the symbol file offline. This error happens when trying to establish a connection with the PLC.

Internal error related to the PLCHandler function Connect.

17

Asynchronous operation

Asynchronous operation(e.g.,cyclic read of variables)has not yet finished.

Internal PLCHandler error that should never happen on this driver.Contact technical support if this error occurs.

18

ctiveX error

Internal error.

The communication driver does not use this capability of PLCHandler, if you see this error it is probably a problem with the PLCHandler.Please contact technical support.

19

Target ID mismatch

PLC does not match to the passed target ID specified.

Use the programming software to scan the network and find the correct PLC ID

20

Object not found

No object found for the required action(e.g., tried to get an element beyond the end of the list).

Contact technical support.

21

Components not loaded

No object found for the required action(e.g.,tried to get an element beyond the end of the list).

Components required to establish communication are missing. Please contact your supplier to receive the additional files.

22

Busy

Last action still in progress, cannot start the required one

• The driver tried to start a communication task before the previous one was completed.Contact the technical support.

• If you are seeing intermittent communication problems because of this issue, please try increasing the number of retries.

23

Disabled

Driver tried to use the log feature but logging is disabled.

Contact technical support.

50

Invalid type

Results returned by the PLCHandler or specified by the driver are invalid.

Contact technical support.

51

Symbols not found

None of the variables specified match the symbols currently present in the PLC.

• Make sure that your symbols are properly added to the controller.

• Verify if the name specified in the driver work sheet matches the variable name in the PLC.

52

Initialization error

The operating system does not have enough resources for the driver initialization.

Enable the protocol analyzer and run the driver again to retrieve further details.

53

Memory allocation error

• The driver could not allocate memory.

• Internal programming error in the driver.

• Verify the memory available on your device.

• If enough memory is available, contact technical support.

54

Driver is closing

Driver could not be initialized because it is in shutdown process.

Wait for until the driver close and then retry.

55

PLCHandler returned invalid code

PLCHandler function GetLastError returned zero after a read or write failure.

Contact technical support.

0

OK

Communicating without error.

None required.

-15

Time out 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 time out in the driver's advanced settings.

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