Page Tree
Other Releases
...
Implementation DLL: T.ProtocolDriver.TorqueTool.dll
PLC types supported: PF4000 and PF6000
Protocol supported: Open Protocol from Atlas Copco
...
...
Note: If you have more than one channel, each must use a different port.
...
Station syntax: <IP Address>;<Port>
Where:
...
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 |
---|---|---|---|---|
COMM_START | PF4000_1 | COMM_START | Native | Read |
KEEP_ALIVE | PF4000_1 | KEEP_ALIVE | Native | Read |
LTR_PSETNAME | PF4000_1 | LTR_PSETNAME | Native | Read |
LTR_TIGHTSTAT | PF4000_1 | LTR_TIGHTSTAT | Native | Read |
LTR_TIME | PF4000_1 | LTR_TIME | Native | Read |
LTR_TORQUE | PF4000_1 | LTR_TORQUE | Native | Read |
SELECT_PARAMETER_SET | PF4000_1 | SELECT_PARAMETER_SET | Native | Write |
SELECT_JOB | PF4000_1 | SELECT_JOB | Native | Write |
IDENTIFIER_DOWNLOAD_REQUEST | PF4000_1 | IDENTIFIER_DOWNLOAD_REQUEST | Native | Write |
...
...
WriteEventEnabled = true
WriteEvent = Changed
...
...
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.
...
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.
...