Torque Tool Ethernet

Licensing starts at $452.00
torque tool ethernet demo download

Product Overview

The Torque Tool Ethernet driver and KEPServerEX connectivity platform provide an easy and reliable way to connect Torque Tools to OPC client applications, including HMI, SCADA, Historian, MES, ERP, and countless custom applications. The driver was designed to work with all devices supporting the Torque Tool Open Protocol.



  • Has the ability to gather and monitor Job, Tool, and Alarm data (plus numerous other command sets)
  • Supports unsolicited data on specific command sets
  • Supports Disable Tool On Last Tightening Result (LTR)
  • Supports Revision Number for Last Tightening Result (LTR) 1-5, 9999
  • Supports Revision Number for Old Tightening Result (OTR)1-4
  • Supports Revision Number for Vehicle Identification (VIN) 1,2


  • Ford Ethernet Protocol (FEP)
  • Torque Tool Open Ethernet

Supported Devices

  • Any Device Supporting Torque Tool Open Protocol
  • Atlas Copco Power Focus 3000 with W5 or W7 Software
  • Atlas Copco Power Focus 3100 with W5 or W7 Software
  • Atlas Copco Power Focus 4000 with W5 or W7 Software
  • Stanley QPM Nutrunners E Series
  • Stanley QPM Nutrunners EA Series

Available Languages

  • English

Application Support

  • DDE Format CF_Text and AdvancedDDE
  • NIO Interface for iFIX
  • OPC .NET Service (OPC .NET) Version 1.00
  • OPC Alarms and Events (OPC AE) Version 1.10
  • OPC Data Access (OPC DA) Versions 1.0a, 2.0, 2.05a, and 3.0
  • OPC Unified Architecture (OPC UA) Version 1.02
  • SuiteLink and FastDDE for Wonderware

Release Notes


  • Increased the maximum channel limit from 100 to 256.



  • Fixed an issue where the driver would not process incoming unsolicited messages if multiple messages were received before the driver checked the receive buffer.
  • Fixed an issue in device diagnostics where unsolicited messages would either display for the wrong device or not display at all.
  • Added support for bit addresses to LTR_TERR_STATUS2. Previously, this was included in the help file, but was not supported by the address parser.



  • Added support for MID 200 (set “external controlled” relays).
  • Added support for subscribing to external digital inputs, MIDs 210-213.


  • Added support for MID 200 (Set “external controlled” Relays). These addresses are write only and support the integer value range of 0-3. An example address for relay 1 is: STATUS_RELAY_1.



  • Added support for revision 6 of MID 61, which relates to the Prevail Torque Compensate for the Last Tightening Results command set.
  • Added support for using an asterisk as a pad character for the transaction header for the FEP model type.



  • Prevented the driver from immediately closing the socket connection when there is no client reference for a device. Instead, the driver will wait for the next Keep Alive before closing the socket.
  • Fixed an issue where the driver would not refresh the TCP socket if either the IP Address or port was changed and the Connection Timeout setting was modified.
  • Fixed an issue where the driver could stop receiving packets due a timeout.
  • Fixed a threading issue that could cause a channel to stop communicating.


  • Resolved an issue where the driver would not send a start command before reissuing the last command (on a retry attempt) if the socket was closed.
  • Fixed an issue where the driver refreshed the TCP socket when the Connection Timeout setting was modified.
  • Fixed an issue where the driver closed the TCP socket on the "WSAEWOULDBLOCK" error code, which is a Windows socket error code.


Fixed an issue where the driver continuously attempted to reconnect if a device responded with "Client Already Connected".


  • Fixed an issue where the driver was not correctly updating or invalidating certain internal driver tags. This prevented the server from providing timely updates to AsynchIO2/AsynchIO3 read requests and prevented the driver from providing correct last tightening results due to invalid status of the LTR_NEWDATA bit.


  • Added support for the Ford Ethernet Protocol (FEP) variation of Open Protocol. The driver now supports two models: Open Protocol and FEP.
  • Resolved an issue where the driver could prematurely post device not responding messages when a client is initially connecting to the server.


  • A new setting was added under the Device Properties page to set the error state when a device fails to respond to writes or subscription requests.

Featured Suites

What Is a Driver?

KEPServerEX is more than an OPC server—it's a connectivity platform for industrial automation and IoT. Simply download KEPServerEX, and then select from Kepware's library of more than 150 device drivers, client drivers, and advanced plug-ins to fit the communication requirements unique to your industrial control system.

A driver is a software component that enables KEPServerEX to meet the connectivity requirements of a specific device, system, or other data source. The driver handles all proprietary communications to the data source for KEPServerEX; the client interfaces handle all supported OPC, proprietary, and open standards connectivity to applications that monitor or control the devices.

Drivers may be licensed individually or in suites. Additional drivers can be licensed on demand as connectivity needs evolve.

Purchasing Information

Torque Tool Ethernet


Pay an annual fee to use the software. Support & Maintenance is included.


© PTC Inc. All Rights Reserved.