Page Tree
Other Releases
...
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.
...
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, for example, 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_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 |
| SELECT_PARAMETER_SET | PF4000_1 | SELECT_PARAMETER_SET | Native | Write | Load a new program to the torquetool |
| SELECT_JOB | PF4000_1 | SELECT_JOB | Native | Write | Load a new program to the torquetool |
IDENTIFIER_DOWNLOAD_REQUEST | PF4000_1 | IDENTIFIER_DOWNLOAD_REQUEST | Native | Write | Load a new program to the torquetool |
...
Access Types Configuration
...
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.
...
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.
...
Overview
Content Tools
Tasks