The Torque Open Protocol driver (or Torque-OP) on the IoT Gateway is able to communicate with devices that support the Atlas Copco Open Protocol specification.
While Atlas Copco was the company that created this standard, many manufacturers support this standard protocol. This driver has been tested with torque controllers from:
- Atlas Copco
- Ingersoll Rand
- Stanley-Black & Decker
To determine if your torque controller supports this protocol, refer to your product's manual or contact your sales or distribution representative.
The Torque-OP driver supports the following functions:
- Sending an "Enable Tool" command to the controller.
- Sending a "Disable Tool" command to the controller.
- Sending a "Set Parameter Set ID" command to the controller.
- Sending a "Set Job ID" command to the controller.
- Receiving a "Tool Status" message from the controller that indicates if the controller is enabled or disabled.
- Receiving a "Tightening Event" message from the controller that includes information about the last tightening event such as torque, angle, and whether all of the measurements were in range.
The Torque Open Protocol Driver is available with limited functionality in Gateway v1.1.0 and later.
Support for selecting a port in the configuration menu, requesting a Parameter Set, and receiving Extended Tightening Data are available in Gateway v1.3.2 and later.
Using the Driver
This driver requires the use of an IoT Gateway. To use the driver, you must first configure the Torque-OP driver on the IoT Gateway and then create a Tulip App that uses this connection.
Enable the Driver on your IoT Gateway
First, ensure that your Torque Controller is connected to the same network as your IoT Gateway. The IoT Gateway will create a connection to your torque controller over the network.
Then, access the Gateway Portal's Driver Configuration Page and select the "Torque-OP" Driver menu.
Here, you must specify the IP address and port of your Torque Controller's Open Protocol server.
If you have questions about how to enable the Torque Open Protocol server on your torque controller, please refer to your product's manual or contact your sales or distribution representative.
Create a Tulip App
The next step is to create a Tulip app that uses this driver.
Create an app and then use triggers to interact with the driver.
There are two types of trigger events that this driver supports.
The first type is a command to send information to the Torque Controller. These commands are sent in a Trigger Action. You can see the supported event types in the image below.
- "Run Device Function" "Torque Tool Open Protocol" (select the action)
Each command will then prompt you for the necessary information related to that command.
The second type of trigger event is to receive data from the torque controller. These triggers are only available as "Step Triggers" in the "When" clause. Note the options below:
- "device" "Torque Tool Open Protocol" outputs as "this station" "with events"...
Here, the "Tightening Data" event will include the torque value and whether or not the torque measurement was within the acceptable range.
The "Extended Tightening Data" event includes much more information, but might not be applicable for all use cases.
For both events, the Device Output is then available within the Trigger to be used in a variety of situations. In the image below, there is a trigger that uses one property of the Device Output immediately and also stores the Device Output for later retrieval.
A short video walkthrough is included below.