TorqueTool

Summary Information

Communication Driver Name: TorqueTool

Current Version: 1.0.0.0

Implementation DLL: T.ProtocolDriver.TorqueTool.dll

PLC types supported: PF4000 and PF6000

Protocol supported: Open Protocol from Atlas Copco

Channel Configuration

Protocol Options

Model: Select the model of your tool, it will impact in how the messages will be read. The options are:

• PF4000
• PF6000

Settings

AcceptUnsolicited = true

Note: If you have more than one channel, each must use a different port.

Node Configuration

Station syntax: <IP Address>;<Port>

Where:

• <IP Address> = IP address of the device in the network
• <Port> = Port of the device

Point Configuration

The syntax for the address is: <MID Name>

The possible MID values, are presented in the table below:

Access Types Configuration

Read

For the reading AccessType these are the setting necesary:

ReadEnabled = Always

ReadPoolingRate = (The protocol documentation recommends 7 seconds)

AcceptUnsolicited = true

Write

Standard setting is recommended.

WriteEventEnabled = true

WriteEvent = Changed

Communication Flow

COMM_START

Before any other message is sent, this protocol requires a communication start message. Therefore, the use of the address "COMM_START" is mandatory.

KEEP_ALIVE

To maintain an active connection with the tool, this protocol requires sending a keep-alive message every X seconds (7 seconds is recommended). If no response is received within 15 seconds, the connection will automatically be closed. As such, the use of "KEEP_ALIVE" is also mandatory.

Subscription

For all other events, a subscription will be sent based on the configuration you specified in the Points table, targeting the corresponding MID. When the event occurs—such as a torque being applied by the tool—you will receive an unsolicited message with the relevant data.

Flow

All the logic for sending the "COMM_START" message first, then the subscription, and continuously sending "KEEP_ALIVE" messages is already handled by the protocol.
You don’t need to worry about implementing this logic yourself—just make sure these points are defined in the table.

Troubleshoot

The status of the driver's execution can be observed through the diagnostic tools, which are:

• Trace window
• Property Watch
• Module Information

The above tools indicate if the operations have succeeded or have failed. A status of 0 (zero) means communication is successful. Negative values indicate internal driver errors, and positive values indicate protocol error codes.