Atlas Copco driver troubleshooting

The features and functions available in a node are controlled by the licenses that are installed in the node.

To verify that the Atlas Copco driver license is installed:

1. From the Workbench left pane, expand the node whose license you want to check, and then select the Administration icon.
2. From the Administration window, select the Licenses tab.
3. Select the appropriate license. Details of the license appear on the tab.
4. View the Features column 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.

The Atlas Copco driver is not part of this node's installation. The Atlas Copco driver is installed as a 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 is the one with support for Atlas Copco controllers.

For information on how to add the Atlas Copco driver package, refer to System Administration > Packages.

The Atlas Copco controller needs to be configured using the either the Atlas Copco Tool Talk Power Focus software or the Atlas Copco PowerMACS WinTC Gold software. The complete description of this configuration is beyond the scope of this documentation.

Ensure that the IP address in the network settings is correctly configured for your network setup. There may be cross subnet issues depending on how the PLCs were configured.

Ensure that the correct port value has been entered. The default Open Protocol port for an Atlas Copco controller is 4545.

Try using the Ping function on the Workbench Administration panel, Diagnostics tab for your node to see if that level of communication is successful.

Heartbeat messages between the Atlas Copco driver and the physical Atlas Copco controller are needed to maintain the ethernet connection. The controller will break the connection if there is no communication from the driver after 15 seconds. During definition time a value is specified in the Keep Alive field, which is used as a basis to send a heartbeat message to the controller. The driver will attempt to send this heartbeat message as close to this value as possible, but there are times where the message may be sent one or two seconds later than the value specified in the Keep Alive field. This will only be a problem if your Keep Alive value is greater than 12. If you find that your device becomes disabled because it did not communicate with the controller and the Keep Alive value in the device definition is larger than 12, change this to a value of 10. 

Atlas Copco controllers support many different protocols, such as ModBus or Ethernet/IP. The Atlas Copco driver communicates to the controller using the Open Protocol. Attempting to communicate to a controller that is defined to use a FieldBus protocol will prevent the Atlas Copco device from starting. Ensure that the None option is selected for the FieldBus setting in the Ethernet Connections definition for the controller that is being monitored.

If the SetVIN trigger action fails with an external status code of 8 (VIN input source not granted), this indicates that the Atlas Copco controller has not been configured to accept changes from external sources. This must be done from the ToolsTalk software on the Identifier window. In the image below, the Identifier button has been outlined in red. Clicking on this button displays the Identifier pop-up window. By default the Input source field has a setting of Off. This needs to be set to Ethernet/Serial, which will allow the SetVIN trigger action to complete successfully. This field can also be set to Scanner & Ethernet/Serial to allow input from either a scanner or through the SetVIN trigger action.

This section describes the error codes that you might encounter when using the Atlas Copco driver.

These error codes are available from the Devices window in the Extended Status column. The error codes are also referenced in the Exceptions Log. Note that these error codes are not the error codes displayed on the front of the Atlas Copco controller.

When the system experiences an abnormal condition (such as a device failure, disconnect from a controller, or software error), an error code and extended error code are recorded in the Exceptions Log.

In the Devices window, the Status column will always be a generic error code that can tell you if the error is a communication error, a data error, or some other internal device error. The Extended Status column provides the error code from the driver. These error codes can be basic runtime error codes or specific to the Atlas Copco driver.