Torque Tool Ethernet

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.

Documents

Release Notes

6.6.348.0

11/14/2018

Added asynchronous tag packing for LTR_NEWDATA, MS_NEWDATA, ALM_NEWDATA, JOB_NEWDATA, VIN_NEWDATA, PSET_NEWDATA; allowing all tags to be updated together as a set rather than individually. This setting is now enabled by default with new projects.

Added a Combined Tag for all results from LTR _TERRSTATUS Booleans in a single tag.

Added a Combined Tag for all results from OTR _TERR_STATUS Booleans in a single tag.

6.3.273.0

9/27/2017

Increased the maximum channel limit from 100 to 256.

6.2.429.0

6/8/2017

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.

6.1.655.0

6/11/2018

Increased the maximum channel limit from 100 to 256.

6.1.601.0

4/4/2017

Added support for MID 200 (set “external controlled” relays).

Added support for subscribing to external digital inputs, MIDs 210-213.

6.0.2206.0

6/11/2018

Added logic to make LTR_TERR_STATUS2 a bit item and to restrict this address item and LTR_PVT for FEP models since FEP does not explicitly support MID 61 rev 6.

5.21.235.0

6/11/2018

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 display for the wrong device or not display at all.

Fixed a crash that could occur if the driver was expecting an unsolicited packet, but received a solicited packet.

Added support for MIDs 210-213 for subscribing to external digital input status.

Made a tag for each external relay that controls that respective relay instead of having a tag that controls all relays.

Added support for MID 200.

5.21.114.0

3/20/2017

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.

5.20.396.0

5/3/2016

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.

5.15.585.0

7/22/2014

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.

5.13.191.0

10/15/2013

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.

5.8.109.0

2/21/2012

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

5.7.84.0

10/24/2011

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.

5.6.122.0

7/25/2011

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.

5.3.118.0

6/9/2010

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.