The following section lists common tasks and problems that may be encountered when using the CODESYS driver.
Verify the proper license keys are installed
The features and functions available in a node are controlled by the licenses that are installed in the node.
To verify that the CODESYS driver license is installed:
- From the Workbench left pane, expand the node whose
license you want to check, and then select
the Administration icon.
- From the Administration window, select
the Licenses tab.
- Select the appropriate license. Details of the
license appear on the tab.
- View the Features field to identify the device driver.
If you do not see the correct license, or if the license is expired, you must request a license from your license key provider.
For information on how to install a license, refer to System Administration > Licenses.
Unable to define a device for a CODESYS PLC
The CODESYS driver is not part of this node's installation. The CODESYS driver is installed as a separate package, separate from the base product installation.
You may be working with different levels of nodes, each with different levels of support for devices. Ensure that this node's installation is one with support for CODESYS PLCs.
For information on how to add the CODESYS driver package, refer to System Administration > Packages.
Start fails when connecting to a CODESYS PLC
Ensure that the CODESYS PLC is online and powered up. Attempt to ping the IP address of the CODESYS PLC from the node where the driver is installed. This is done from the Workbench's Administration->Diagnostics panel.
If the ping succeeds and the CODESYS device is powered on, then ensure that the node has been added to the access table on the CODESYS PLC.
CODESYS error codes
An overview of the CODESYS error codes are shown below.
| Error Code | Name | Description |
| -1 | RESULT_FAILED | Action erroneous |
| 1 | RESULT_PLC_NOT_CONNECTED | PLC not connected |
| 2 | RESULT_PLC_LOGIN_FAILED | Login to PLC has failed |
| 3 | RESULT_PLC_NO_CYCLIC_LIST_DEFINED | No cyclic list has been found |
| 4 | RESULT_PLCHANDLER_INACTIVE | PLCHandler instance was set inactive |
| 5 | RESULT_LOADING_SY20BOLS_FAILED | Loading of the sY20bols has failed |
| 6 | RESULT_ITF_NOT_SUPPORTED | The defined communication interface is not valid or supported |
| 7 | RESULT_COMM_FATAL | Communication error occurred during the action |
| 8 | RESULT_NO_CONFIGURATION | Wrong or erroneous configuration of the PLCHandler |
| 9 | RESULT_INVALID_PARAMETER | At least one parameter is invalid |
| 10 | RESULT_ITF_FAILED | Communication interface could not be initialized correctly |
| 11 | RESULT_NOT_SUPPORTED | Method not yet supported |
| 12 | RESULT_EXCEPTION | Handled exception in a low layer occurred |
| 13 | RESULT_TIMEOUT | Timeout exceeded |
| 14 | RESULT_STILL_CONNECTED | PLC already connected |
| 15 | RESULT_RECONNECTTHREAD_STILL_ACTIVE | Reconnect thread already active |
| 16 | RESULT_PLC_NOT_CONNECTED_SY20BOLS_LOADED | No connection the PLC, bu sY20bols available offline |
| 17 | RESULT_NO_UPDATE | Asynchronous operation has not yet finished |
| 18 | RESULT_OCX_CONVERSION_FAILED | Error during conversion of values inside the PLCHandler's ActiveX interface occurred |
| 19 | RESULT_TARGETID_MISMATCH | PLC does not match to the passed target id |
| 20 | RESULT_NO_OBJECT | No object found for the required action |
| 21 | RESULT_COMPONENTS_NOT_LOADED | PLCHandler instantiation has failed because of missing components |
| 22 | RESULT_BUSY | Last action still in progress cannot start the required one |
| 23 | RESULT_DISABLED | Feature is disabled by the configuration |
| 24 | RESULT_PLC_FAILED | Communication to the PLC was successful, but the PLC has a bad result |
| 25 | RESULT_INVALID_SYMBOL | Specified symbol does not exist on PLC |
| 26 | RESULT_BUFFER_TOO_SMALL | User provided buffer is too small to store the requested information |
| 27 | RESULT_NO_PROJECT | No project/application is loaded by the PLC, but the called method requires one to be executed |
| 28 | RESULT_FILE_ERROR | Operation failed because of a file access error |
| 29 | RESULT_RETAIN_MISMATCH | Restored retain variables does not match to the project/application on the PLC |
| 30 | RESULT_NO_ACCESS_RIGHTS | Operation was denied by the PLC because of missing access rights |
| 31 | RESULT_DUPLICATE_PLC_NAME | Connect by PLC name failed because there exist several PLCs with the specified name in the PLC network |
| 32 | RESULT_SIZE_MISMATCH | Service does not succeed because of a size mismatch |
| 33 | RESULT_LIST_NO_WRITE_ACCESS | Variable list was defined without flag VARLIST_FLAG_WRITE_ACCESS, but later on used for a write access |
| 34 | RESULT_CONSISTENT_ACCESS_TIMEOUT | PLC was temporarily not able to execute the consistent read or write access because of high CPU load caused by the IEC tasks |
| 35 | RESULT_SYNC_CONSISTENT_ACCESS_DENIED | At least one application on the PLC does not allow synchronized consistent accesses |
| 36 | RESULT_INVALID_ASCII_STRING | Method or PLC expects a string containing only printable 7-bit ASCII characters |
| 37 | RESULT_INVALID_STRING_LENGTH | Provided string does not match length requirements |
| 38 | RESULT_OUTOFMEMORY | Requested amount of memory was not allocated |
| 39 | RESULT_NO_FILE | No file found to process |
| 40 | RESULT_APPLICATION_NOT_IN_STOP | Application is not in Stop but this is required for this operation |
| 41 | RESULT_APPLICATION_NOT_IN_RUN | Application is not in Run but this is required for this operation |
| 42 | RESULT_OPERATIONMODE_NOT_IN_DEBUG | Operation modes is not in Debug but this is required for this operation |
| 43 | RESULT_BACKUP_RESTORE_NOT_SUPPORTED | Backup & Restore is not supported by the configuration of the PLC |
| 44 | RESULT_PLC_INCONSISTENT_STATE | Applications on the PLC are in an inconsistent state |
| 45 | RESULT_PLC_INCOMPATIBLE | The version of the PLC is not compatible with this operation |
| 46 | RESULT_PLC_VERSION_INCOMPATIBLE | The version of the PLC is not compatible with this operation |
| 47 | RESULT_RETAIN_ERROR | Error while handling retains |
| 48 | RESULT_APPLICATIONS_LOAD_ERROR | Application(s) failed to load |
| 49 | RESULT_APPLICATIONS_START_ERROR | Application(s) failed to start |
| 50 | RESULT_FILETRANSFER_ERROR | One or more files were not transferred successfully |
| 51 | RESULT_OPERATION_DENIED | The operation was denied by the PLC |
| 52 | RESULT_FORCES_ACTIVE | Forces are active on the PLC |
| 53 | RESULT_META_VERSION_MISMATCH | Version of meta.info of the backup is not supported |
| 54 | RESULT_PROTOCOL_MISMATCH | The configured protocol is not supported by the PLC |
| 55 | RESULT_USER_ACCESS_DENIED | The configured credentials are not valid |
| 56 | RESULT_CALL_AGAIN | The call should be repeated |