TorqueTool

Summary Information

Communication Driver Name: TorqueTool

Current Version: 1.0.0.0

Implementation DLL: T.ProtocolDriver.TorqueTool.dll

PLC types supported: PF4000, PF6000 and PF8

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
PF8

Settings

AcceptUnsolicited = true

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

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:

TagName	Node	Address	DataType	AccessType	Description
COMM_START	PF4000_1	COMM_START	Native	Read	Start Communication
KEEP_ALIVE	PF4000_1	KEEP_ALIVE	Native	Read	Keep Alive to mantain comm online
LTR_REPLY	PF4000_1	LTR_REPLY	Native	Read	It returns a detailed string containing information about the equipment.
LTR_PSETNAME	PF4000_1	LTR_PSETNAME	Native	Read	Project name.
LTR_TIGHTSTAT	PF4000_1	LTR_TIGHTSTAT	Native	Read	Torque status.
LTR_TIME	PF4000_1	LTR_TIME	Native	Read	Date and time the torque was done.
LTR_TORQUE	PF4000_1	LTR_TORQUE	Native	Read	Torque value.
MID_ALARM	PF4000_1	MID_ALARM	Native	Read	An alarm message indicating possible errors.
SELECT_PARAMETER_SET	PF4000_1	SELECT_PARAMETER_SET	Native	Write	Load a new program to the torquetool. Uses the ID of the program (Three ASCII characters, range 000-999).
SELECT_JOB	PF4000_1	SELECT_JOB	Native	Write	Load a new program to the torquetool. Uses the ID of the program (Four ASCII characters, range: 0000-9999).
IDENTIFIER_DOWNLOAD_REQUEST	PF4000_1	IDENTIFIER_DOWNLOAD_REQUEST	Native	Write	Load a new program to the torquetool. Uses the name of the program (Max 25 ASCII characters).

At least one LTR_<Command> and the MID_ALARM must be configured. <Command> can be any of the commands listed above.

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.

Monitoring Communication Status

For monitoring if the connection is great in real time, you can check the quality of the "COMM_START" tag, it should be 192 if everything is fine, any other value indicate an error in communication (check the TraceWindow for logs, refeer to Troubleshoot section).

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.