Torque Tool Ethernet驱动 - Kepware OPC Server 中国区总代理、合作伙伴

Torque Tool Ethernet

产品概览

下载试用

Torque Tool Ethernet 驱动程序和 KEPServerEX 连接平台提供了一种用于将扭矩工具连接到 OPC 客户端应用程序（包括 HMI、SCADA、Historian、MES、ERP 以及无数自定义应用程序）的简单可靠的方法。此驱动旨在与支持扭矩工具开放协议的所有设备协同工作。

搜索 KEPServerEX 产品

支持与维护

联系销售人员

询价或售前咨询

电话：4006 139 938 / 021-5102 8348
电子邮件：

资源

性能
协议
支持的设备
可用语言
应用程序支持
发行说明
相关硬件产品
特色套件

性能

能够收集并监控作业、工具和警报数据（以及大量其他命令集）
支持特定工具集采用主动数据
支持最后紧固结果 (LTR) 禁用工具
支持最后紧固结果 (LTR) 修订版本号 1-5、9999
支持旧紧固结果 (OTR) 修订版本号 1-4
支持车辆识别 (VIN) 修订版本号 1、2

协议

Ford Ethernet Protocol (FEP)
Torque Tool Open Ethernet

支持的设备

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

可用语言

英语

应用程序支持

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

发行说明

6.3.273.0

2017/9/27

最大通道数上限从 100 增加到 256.

6.2

2017/6/8

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.601.0

2017/4/4

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

5.21.114.0

2017/3/20

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

2016/5/3

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

2014/7/22

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

2013/10/15

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

2012/2/21

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

5.7.84.0

2011/10/24

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

2011/7/25

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

2010/6/9

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.

特色套件

Manufacturing Suite

什么是驱动？

KEPServerEX 不仅是 OPC 服务器，它还是一种适用于工业自动化和 IoT 的连接平台。只需下载 KEPServerEX，然后从包含 150 多种设备驱动、客户端驱动和高级插件的 Kepware 库中选择，以便适合您工业控制系统的独特通信要求。

驱动是一种软件组件，能够使 KEPServerEX 满足某个特定设备、系统或其他数据源的连接要求。此驱动处理 KEPServerEX 与数据源进行的所有专属通信；客户端接口处理通向监控或控制设备的应用程序的所有连接，包括支持的 OPC 连接、专属连接和开放式标准连接。

驱动可以单独或以套件形式获得授权许可。随着连接需求的发展，可以按需对其他驱动进行许可。