Torque Tool Ethernet Manual
Torque Tool Ethernet Manual
Table of Contents
Torque Tool Ethernet Driver 1
Table of Contents 2
Overview 4
Setup 4
Channel Properties — General 5
Channel Properties — Ethernet Communications 6
Channel Properties — Write Optimizations 6
Channel Properties — Advanced 7
Device Properties — General 8
Operating Mode 9
Device Properties — Scan Mode 9
Device Properties — Timing 10
Device Properties — Communications Parameters 11
Device Properties — Settings 12
Device Properties — Redundancy 13
Optimizing Communications 14
Address Descriptions 15
Message IDs 16
www. ptc.com
3 Torq u e Tool Eth ern et Driver
Error Descriptions 44
Address <address> is out of range for the specified device or register. 45
Array size is out of range for address <address>. 45
Array support is not available for the specified address: <address>. 45
Data type <type> is not valid for device address <address>. 45
Device address <address> contains a syntax error. 45
Device address <address> is read only. 46
Unable to bind to adapter: <adapter name>. Connect failed. 46
Winsock initialization failed (OS error = <error>). 46
Winsock shut down failed (OS error = <error>). 46
Winsock V1.1 or higher must be installed to use the driver. 47
Device <device name> failed to connect. 47
Device <device name> is not responding. 47
Unable to read tag <tag name>: Device <device name> encountered a parsing error. 48
Unable to read tag <tag name>: Device <device name> received an error response (Error <error
code>). 48
Unable to read unsolicited packed data group: Device <device name> received an error response
(Error <error code>). 48
Unable to write tag <tag name>: Device <device name> encountered a parsing error. 49
Unable to write tag <tag name>: Device <device name> received an error response (Error <error
code>). 49
Unable to write tag <tag name>: Device <device name> received invalid data for write. 49
Unable to write to <address> on device <device name>. 50
Error Codes 50
Index 54
www. ptc.com
4 Torq u e Tool Eth ern et Driver
CONTENTS
Overview
What is the Torque Tool Ethernet Driver?
Set up
How do I configure a device for use with this driver?
Overview
The Torque Tool Ethernet Driver provides a reliable way to connect Torque Tool Ethernet devices to OPC Cli-
ent applications; including HMI, SCADA, Historian, MES, ERP, and countless custom applications. It is inten-
ded to work with all devices supporting the Torque Tool Open Protocol.
Set up
Supported Devices
The Torque Tool Ethernet Driver is designed to work with any device that supports the Torque Tool Open Pro-
tocol. The driver has been tested with the Stanley QA Alpha Controller and the Atlas Copco Power Focus.
www. ptc.com
Torque Tool Ethernet Driver 5
Identification
N am e: Specify the user-defined identity of this channel. In each server project, each channel name must be
unique. Although names can be up to 256 characters, some client applications have a limited display window
when browsing the OPC server's tag space. The channel name is part of the OPC browser information. The
property is required for creating a channel.
For information on reserved characters, refer to "How To... Properly Name a Channel, Device, Tag, and Tag
Group" in the server help.
Driver: Specify the protocol / driver for this channel. This property specifies the device driver that was selec-
ted during channel creation. It is a disabled setting in the channel properties. The property is required for cre-
ating a channel.
N ote: With the server's online full-time operation, these properties can be changed at any time. This
includes changing the channel name to prevent clients from registering data with the server. If a client has
already acquired an item from the server before the channel name is changed, the items are unaffected. If,
after the channel name has been changed, the client application releases the item and attempts to re-
acquire using the old channel name, the item is not accepted. With this in mind, changes to the properties
should not be made once a large client application has been developed. Utilize proper user role and priv-
ilege management to prevent operators from changing properties or accessing server features.
Diagnostics
Diagnostics Capture: When enabled, this option makes the channel's diagnostic information available to
OPC applications. Because the server's diagnostic features require a minimal amount of overhead pro-
cessing, it is recommended that they be utilized when needed and disabled when not. The default is dis-
abled.
N ote: This property is not available if the driver does not support diagnostics.
For more information, refer to "Communication Diagnostics" and "Statistics Tags" in the server help.
www. ptc.com
6 Torq u e Tool Eth ern et Driver
Ethernet Settings
N etwork Adapter: Specify the network adapter to bind. When left blank or Default is selected, the oper-
ating system selects the default adapter.
Write Optimizations
Optim ization Method: Controls how write data is passed to the underlying communications driver. The
options are:
l Write All Values for All Tags: This option forces the server to attempt to write every value to the
controller. In this mode, the server continues to gather write requests and add them to the server's
internal write queue. The server processes the write queue and attempts to empty it by writing data
to the device as quickly as possible. This mode ensures that everything written from the client applic-
ations is sent to the target device. This mode should be selected if the write operation order or the
write item's content must uniquely be seen at the target device.
l Write Only Latest Value for N on-Boolean Tags: Many consecutive writes to the same value can
accumulate in the write queue due to the time required to actually send the data to the device. If the
server updates a write value that has already been placed in the write queue, far fewer writes are
needed to reach the same final output value. In this way, no extra writes accumulate in the server's
queue. When the user stops moving the slide switch, the value in the device is at the correct value at
virtually the same time. As the mode states, any value that is not a Boolean value is updated in the
server's internal write queue and sent to the device at the next possible opportunity. This can greatly
improve the application performance.
N ote: This option does not attempt to optimize writes to Boolean values. It allows users to optimize
the operation of HMI data without causing problems with Boolean operations, such as a momentary
push button.
www. ptc.com
Torque Tool Ethernet Driver 7
l Write Only Latest Value for All Tags: This option takes the theory behind the second optimization
mode and applies it to all tags. It is especially useful if the application only needs to send the latest
value to the device. This mode optimizes all writes by updating the tags currently in the write queue
before they are sent. This is the default mode.
Duty Cycle: is used to control the ratio of write to read operations. The ratio is always based on one read for
every one to ten writes. The duty cycle is set to ten by default, meaning that ten writes occur for each read
operation. Although the application is performing a large number of continuous writes, it must be ensured
that read data is still given time to process. A setting of one results in one read operation for every write
operation. If there are no write operations to perform, reads are processed continuously. This allows optim-
ization for applications with continuous writes versus a more balanced back and forth data flow.
N ote: It is recommended that the application be characterized for compatibility with the write optimization
enhancements before being used in a production environment.
N on-N orm alized Float Handling: A non-normalized value is defined as Infinity, Not-a-Number (NaN), or as
a Denormalized Number. The default is Replace with Zero. Drivers that have native float handling may
default to Unmodified. Non-normalized float handling allows users to specify how a driver handles non-nor-
malized IEEE-754 floating point data. Descriptions of the options are as follows:
l Replace with Zero: This option allows a driver to replace non-normalized IEEE-754 floating point val-
ues with zero before being transferred to clients.
l Unm odified: This option allows a driver to transfer IEEE-754 denormalized, normalized, non-num-
ber, and infinity values to clients without any conversion or changes.
N ote: This property is not available if the driver does not support floating point values or if it only supports
the option that is displayed. According to the channel's float normalization setting, only real-time driver tags
(such as values and arrays) are subject to float normalization. For example, EFM data is not affected by this
setting.
For more information on the floating point values, refer to "How To ... Work with Non-Normalized Floating
Point Values" in the server help.
Inter-Device Delay: Specify the amount of time the communications channel waits to send new requests to
the next device after data is received from the current device on the same channel. Zero (0) disables the
delay.
N ote: This property is not available for all drivers, models, and dependent settings.
www. ptc.com
8 Torq u e Tool Eth ern et Driver
Identification
N am e: Specify the name of the device. It is a logical user-defined name that can be up to 256 characters
long, and may be used on multiple channels.
N ote: Although descriptive names are generally a good idea, some OPC client applications may have a
limited display window when browsing the OPC server's tag space. The device name and channel name
become part of the browse tree information as well. Within an OPC client, the combination of channel name
and device name would appear as "ChannelName.DeviceName".
For more information, refer to "How To... Properly Name a Channel, Device, Tag, and Tag Group" in server
help.
Channel Assignm ent: Specify the user-defined name of the channel to which this device currently belongs.
Model: Specify the type of device that is associated with this ID. The contents of the drop-down menu
depends on the type of communications driver being used. Models that are not supported by a driver are dis-
abled. If the communications driver supports multiple device models, the model selection can only be
changed when there are no client applications connected to the device.
N ote: If the communication driver supports multiple models, users should try to match the model selec-
tion to the physical device. If the device is not represented in the drop-down menu, select a model that con-
forms closest to the target device. Some drivers support a model selection called "Open," which allows users
to communicate without knowing the specific details of the target device. For more information, refer to the
driver help documentation.
ID: Specify the device's driver-specific station or node. The type of ID entered depends on the com-
munications driver being used. For many communication drivers, the ID is a numeric value. Drivers that sup-
port a Numeric ID provide users with the option to enter a numeric value whose format can be changed to
suit the needs of the application or the characteristics of the selected communications driver. The format is
set by the driver by default. Options include Decimal, Octal, and Hexadecimal.
N ote: If the driver is Ethernet-based or supports an unconventional station or node name, the device's
TCP/IP address may be used as the device ID. TCP/IP addresses consist of four values that are separated by
periods, with each value in the range of 0 to 255. Some device IDs are string based. There may be additional
www. ptc.com
Torque Tool Ethernet Driver 9
properties to configure within the ID field, depending on the driver. For more information, refer to the driver's
help documentation.
Operating M ode
Data Collection: This property controls the device's active state. Although device communications are
enabled by default, this property can be used to disable a physical device. Communications are not attemp-
ted when a device is disabled. From a client standpoint, the data is marked as invalid and write operations
are not accepted. This property can be changed at any time through this property or the device system tags.
Sim ulated: Place the device into or out of Simulation Mode. In this mode, the driver does not attempt to
communicate with the physical device, but the server continues to return valid OPC data. Simulated stops
physical communications with the device, but allows OPC data to be returned to the OPC client as valid data.
While in Simulation Mode, the server treats all device data as reflective: whatever is written to the simulated
device is read back and each OPC item is treated individually. The item's memory map is based on the group
Update Rate. The data is not saved if the server removes the item (such as when the server is reinitialized).
The default is No.
N otes:
1. This System tag (_Simulated) is read only and cannot be written to for runtime protection. The System
tag allows this property to be monitored from the client.
2. In Simulation mode, the item's memory map is based on client update rate(s) (Group Update Rate for
OPC clients or Scan Rate for native and DDE interfaces). This means that two clients that reference
the same item with different update rates return different data.
Simulation Mode is for test and simulation purposes only. It should never be used in a production envir-
onment.
Scan Mode: Specify how tags in the device are scanned for updates sent to subscribing clients. Descriptions
of the options are:
l Respect Client-Specified Scan Rate: This mode uses the scan rate requested by the client.
l Request Data N o Faster than Scan Rate: This mode specifies the value set as the maximum scan
rate. The valid range is 10 to 99999990 milliseconds. The default is 1000 milliseconds.
N ote: When the server has an active client and items for the device and the scan rate value is
www. ptc.com
10 Torq u e Tool Eth ern et Driver
increased, the changes take effect immediately. When the scan rate value is decreased, the changes
do not take effect until all client applications have been disconnected.
l Request All Data at Scan Rate: This mode forces tags to be scanned at the specified rate for sub-
scribed clients. The valid range is 10 to 99999990 milliseconds. The default is 1000 milliseconds.
l Do N ot Scan, Dem and Poll Only: This mode does not periodically poll tags that belong to the
device nor perform a read to get an item's initial value once it becomes active. It is the client's
responsibility to poll for updates, either by writing to the _DemandPoll tag or by issuing explicit device
reads for individual items. For more information, refer to "Device Demand Poll" in server help.
l Respect Tag-Specified Scan Rate: This mode forces static tags to be scanned at the rate specified
in their static configuration tag properties. Dynamic tags are scanned at the client-specified scan
rate.
Initial Updates from Cache: When enabled, this option allows the server to provide the first updates for
newly activated tag references from stored (cached) data. Cache updates can only be provided when the
new item reference shares the same address, scan rate, data type, client access, and scaling properties. A
device read is used for the initial update for the first client reference only. The default is disabled; any time a
client activates a tag reference the server attempts to read the initial value from the device.
Communications Timeouts
Connect Tim eout: This property (which is used primarily by Ethernet based drivers) controls the amount of
time required to establish a socket connection to a remote device. The device's connection time often takes
longer than normal communications requests to that same device. The valid range is 1 to 30 seconds. The
default is typically 3 seconds, but can vary depending on the driver's specific nature. If this setting is not sup-
ported by the driver, it is disabled.
N ote: Due to the nature of UDP connections, the connection timeout setting is not applicable when com-
municating via UDP.
Request Tim eout: Specify an interval used by all drivers to determine how long the driver waits for a
response from the target device to complete. The valid range is 50 to 9,999,999 milliseconds (167.6667
minutes). The default is usually 1000 milliseconds, but can vary depending on the driver. The default timeout
for most serial drivers is based on a baud rate of 9600 baud or better. When using a driver at lower baud
rates, increase the timeout to compensate for the increased time required to acquire data.
Attem pts Before Tim eout: Specify how many times the driver issues a communications request before con-
sidering the request to have failed and the device to be in error. The valid range is 1 to 10. The default is
www. ptc.com
Torque Tool Ethernet Driver 11
typically 3, but can vary depending on the driver's specific nature. The number of attempts configured for an
application depends largely on the communications environment. This property applies to both connection
attempts and request attempts.
Timing
Inter-Request Delay: Specify how long the driver waits before sending the next request to the target
device. It overrides the normal polling frequency of tags associated with the device, as well as one-time
reads and writes. This delay can be useful when dealing with devices with slow turnaround times and in
cases where network load is a concern. Configuring a delay for a device affects communications with all
other devices on the channel. It is recommended that users separate any device that requires an inter-
request delay to a separate channel if possible. Other communications properties (such as communication
serialization) can extend this delay. The valid range is 0 to 300,000 milliseconds; however, some drivers may
limit the maximum value due to a function of their particular design. The default is 0, which indicates no
delay between requests with the target device.
N ote: Not all drivers support Inter-Request Delay. This setting does not appear if it is not available.
Ethernet Parameters
Port N um ber: Specify the port number that the driver will use when connecting to the device. The valid
range is 0 to 65535. For Open Protocol, the default setting is 4545. For FEP, the default setting is 9001.
Set Error State for All DN Rs: When enabled, the driver will set the error state if the device does not
respond (DNR) to writes or subscription requests. The driver will always set the error state if the device does
not respond to reads. The default setting is disabled.
Keep-Alive Parameters
Poll Tim e: Specify the amount of time of inactivity before the driver will send a Keep Alive message to the
device. The valid range is 1 to 15 seconds. The default setting is 10 seconds.
Caution: If the Keep Alive interval is set to a value greater than 10 seconds, the driver may post "Device
Not Responding" messages to the Event Log. This is because the device closes the connection.
Reply Tim eout: Specify the amount of time that the driver will wait for a response from a Keep Alive mes-
sage. The valid range is 100 to 30000 milliseconds. The default setting is 1000 milliseconds (1 second).
Fail After: Specify the number of times that the driver will attempt to send a Keep Alive message before con-
sidering it to have failed. The valid range is 1 to 10. The default setting is 3.
www. ptc.com
12 Torq u e Tool Eth ern et Driver
N ote: The FEP model does not support message revisions, and will disable these options.
M essage Revisions
Alarm : Specify the revision number for alarm messages. Supported values are 0 to 3, with 0 as the default.
This affects MIDs 0070 through 0078.
Com m unication: Specify the revision number for communication messages. Supported values are 0 to 6,
with 0 as the default. This affects MIDs 0001 and 0002.
Job Data: Specify the revision number for job data messages. Supported values are 0 to 3, with 0 as the
default. This affects MIDs 0032 and 0033.
Job Info: Specify the revision number for job info messages. Supported values are 0 to 4, with 0 as the
default. This affects MIDs 0034 through 0037.
Job State: Specify the revision number for job ID upload, job select, and job restart messages. Supported val-
ues are 0 to 2, with 0 as the default. This affects MIDs 0030, 0031, 0038, and 0039.
Last Tightening: Specify the revision number for the last tightening results messages. Supported values
are 0 to 5 and 999 (for low-bandwidth version), with 0 as the default. This affects MIDs 0060 through 0063.
Old Tightening: Specify the revision number for the old tightening results messages. Supported values are
0 to 7, with 0 as the default. This affects MIDs 0064 and 0065.
Selector Lights: Specify the revision number for the selector control light messages. Supported values are 0
to 2, with 0 as the default. This affects MIDs 0254 and 0255.
Tool Data: Specify the revision number for the tool data results messages. Supported values are 0 to 5, with
0 as the default. This affects MIDs 0040 and 0041.
www. ptc.com
Torque Tool Ethernet Driver 13
VIN : Specify the revision number for the vehicle identification number (VIN) messages. Supported values are
0 to 2, with 0 as the default. This affects MIDs 0051 through 0054.
Options
Disable Tool On LTR: When enabled, the driver will disable the tool whenever a last tightening results (LTR)
message is received. This ensures that no LTR data is overwritten before the system has had time to pro-
cess it. The default setting is disabled.
Revision Form at: Specify how the driver should format the revision number for commands that use the
default revision (revision 0). By default, when the driver sends a revision 0 message it leaves the revision
number blank. Some devices do not support this and require the revision number to be explicitly set. Setting
this to Zero or One forces the driver to use 0 or 1 for the revision number in the message.
Use Generic Subscribe: Newer devices may only support subscribing using the Generic Subscribe MID 8.
Enabling this property changes the driver to use MID 8 when subscribing data updates.
Use Unsolicited Data Packing: Specify if the driver should update all tags for a given command set at once
or update those tags individually at their specified scan rate.
www. ptc.com
14 Torq u e Tool Eth ern et Driver
This server refers to communications protocols like Torque Tool Ethernet as a channel. Each channel
defined in the application represents a separate path of execution in the server. Once a channel has been
defined, a series of devices must then be defined under that channel. Each of these devices represents a
single Torque Tool controller from which data will be collected. While this approach to defining the applic-
ation will provide a high level of performance, it won't take full advantage of the Torque Tool Ethernet Driver
or the network. An example of how the application may appear when configured using a single channel is
shown below.
Each device appears under a single channel. In this configuration, the driver must
move from one device to the next as quickly as possible to gather information at an
effective rate. As more devices are added or more information is requested from a
single device, the overall update rate begins to suffer.
If the Torque Tool Ethernet Driver could only define one single channel, the example shown above would be
the only option available; however, the driver can define up to 256 channels. Using multiple channels dis-
tributes the data collection workload by simultaneously issuing multiple requests to the network. An example
of how the same application may appear when configured using multiple channels to improve performance
is shown below.
Each device has now been defined under its own channel. In this configuration, a
single path of execution is dedicated to the task of gathering data from each
device. If the application has 256 or fewer devices, it can be optimized exactly how
it is shown here.
The performance will improve even if the application has more devices. While
fewer devices may be ideal, the application will still benefit from additional chan-
nels. Although by spreading the device load across all channels will cause the
server to move from device to device again, it can now do so with far less devices
to process on a single channel.
N ote: Some devices support only one Ethernet connection. For these devices, only one channel and device
should be configured.
www. ptc.com
Torque Tool Ethernet Driver 15
* These types are not used natively, but are supported through conversion.
N ote: All non-variable tags used in the driver have a fixed data type. Therefore, it is recommended that
users allow the driver to use the default data type for the point.
Im portant: Bits are 0-based, with 0 being the LSB. Array indices are 1-based, with 1 being the first item.
Unsolicited Data
Some of the command sets are sent unsolicited by the device. These command sets will not have data avail-
able until the device sends the data to the driver. All unsolicited command sets have a NEWDATA item,
which will be set to 1 when new data arrives. Users may then clear this flag back to 0 by writing any value to
it.
M essage Revisions
Some commands have multiple message revisions which hardware may support. Some items are only avail-
able for certain message revisions. These items have been marked as being available in a certain message
revision. For example, an item marked with (Rev 2) is only available in message revision 2 or later. Some
messages also have a low-bandwidth version available and will be marked appropriately.
Variable Data
Instead of adding revisions to allow for more information to be sent, the Open Protocol specification sup-
ports Variable Data fields. These are dynamic results where any number of values are returned. Each Vari-
able Data field contains the information needed to describe that piece of data and can be uniquely identified
by specifying the Message ID (MID), the Parameter ID (PID), and the Step number. To allow access to these
values, the format of the tag addresses needs to be “MID”.”PID”.”Step”.Unit; where Step and Unit are
optional. If Unit is specified, the Unit value is returned as a numeric value that corresponds to different unit
www. ptc.com
16 Torq u e Tool Eth ern et Driver
types (as defined in the Open Protocol specification). For example, to get the Final Torque on a MT Focus
6000, the tag address might be ‘1202.30237’. To get the units of that value, use this tag address:
‘1202.30237.Unit’. There are common PID values and there are PID values that are specific to the device.
Refer to the Open Protocol specification and the device specific specification for more information.
Protocols
The Torque Tool Ethernet Driver supports the Open Protocol model and the Ford Ethernet Protocol (FEP)
model. Each protocol supports a set of commands that have one or more items available for addressing. Not
all command sets are supported for each model. For more information, select a link from the list below.
Alarm
Aut o-Disable Set t ings
Flash
Ident ifiers
Job Info
Job N umber Dat a
Job Dat a
Last Tight ening Result s
M ult i Spindle Result s
Old Tight ening Result s
Operat ion Result
Paramet er Set Dat a
Paramet er Set N umbers
Paramet er Set Select ed
Select or M essages
Time
Tool Dat a
VIN
M essage IDs
For more information on the Message IDs (MIDs) supported by each device model, refer to the table below.
www. ptc.com
Torque Tool Ethernet Driver 17
www. ptc.com
18 Torq u e Tool Eth ern et Driver
* Only supports MID Revision 1 as indicated in Revision 4.62 of the FEP specification.
* * Unlike Open protocol, FEP does not use batch size, batch counter, and batch status parameters.
www. ptc.com
Torque Tool Ethernet Driver 19
* The ALARM_STATUS flag is valid on an initial connection to the device. Any subsequent alarm messages
after the initial update set the quality of the tag to "Bad" because the status is no longer provided by the
device.
www. ptc.com
20 Torq u e Tool Eth ern et Driver
0 = Automatic Mode
1 = Manual Mode
AM_ Boolean Read/Write New data flag. Set to 1 when new data arrives. Write a 0 to 0-1
NEWDATA this flag to clear it.
www. ptc.com
Torque Tool Ethernet Driver 21
www. ptc.com
22 Torq u e Tool Eth ern et Driver
www. ptc.com
Torque Tool Ethernet Driver 23
JOB_JOBNUM uses MID 38 (Select Job) to set the current job, JOB_RESTART uses MID 39 (Job restart) to
restart a job, JOB_ABORT uses MID 127 (Abort job) to abort the current job. All other tags use MID 34 (Job
info subscribe) to subscribe to job info. The device sends job info to the server using MID 35 (Job info), which
is responded to with MID 36 (Job info acknowledge). If the device supports 4-digit Job IDs, revision 2 or higher
must be used.
N ote: Some command set items also have alias names. In the table below, the alias name will be listed
beneath the item where applicable.
www. ptc.com
24 Torq u e Tool Eth ern et Driver
www. ptc.com
Torque Tool Ethernet Driver 25
www. ptc.com
26 Torq u e Tool Eth ern et Driver
* This item requires an array index or bit index. The valid array / bit index range is 1 to 99.
* This item requires an array index or bit index. The valid array / bit index range is 1 to 9999.
www. ptc.com
Torque Tool Ethernet Driver 27
www. ptc.com
28 Torq u e Tool Eth ern et Driver
www. ptc.com
Torque Tool Ethernet Driver 29
www. ptc.com
30 Torq u e Tool Eth ern et Driver
www. ptc.com
Torque Tool Ethernet Driver 31
N ote: Any commands that require special revisions (such as 2, 3, and so forth) are not supported by the
FEP Protocol model.
www. ptc.com
32 Torq u e Tool Eth ern et Driver
* Although this was not supported by the Open protocol, the Torque Tool Ethernet Driver supports this fea-
ture. This feature is supported by prefixing the Address Item with the Spindle number delimited by a ':' (e.g.
01:VIN_VIN). For the Open protocol, the spindle data is ignored.
* * This item requires an array index. The maximum array index is given by MS_Number.
www. ptc.com
Torque Tool Ethernet Driver 33
set use MID 64 (Old tightening result upload request) for requesting the item data, which is replied to with
MID 65 (Old tightening result upload reply).
www. ptc.com
34 Torq u e Tool Eth ern et Driver
www. ptc.com
Torque Tool Ethernet Driver 35
1 = Nm
2 = Lbf.ft
3 = Lbf.In
4 = Kpm
OTR_RTYPE Word, Short Read Only (Rev 3) Result type 1-7
1 = Tightening
2 = Loosening
www. ptc.com
36 Torq u e Tool Eth ern et Driver
N ote: Any commands that require special revisions (such as 2, 3, and so forth) are not supported by the
FEP Protocol model.
www. ptc.com
Torque Tool Ethernet Driver 37
For more information, request the model-specific document(s) for the open protocol implementations from the
Atlas Copco website (https://www.atlascopco.com).
N ote: Some command set items also have alias names. In the table below, the alias name will be listed
beneath the item where applicable.
www. ptc.com
38 Torq u e Tool Eth ern et Driver
N ote: Some command set items also have alias names. In the table below, the alias name will be listed
beneath the item where applicable.
N ote: Some command set items also have alias names. In the table below, the alias name will be listed
beneath the item where applicable.
Dat a Dat a
It em Access Descript ion
Type Range
PSET_ Word, Read/Write ID number of the last parameter set selected. Users 0-999
www. ptc.com
Torque Tool Ethernet Driver 39
Dat a Dat a
It em Access Descript ion
Type Range
may also write a parameter set number to this item
APP_NUMBER Short
to select a parameter set.
PSET_
LASTCHANGE 19 char-
String Read Only Time of last change in PSet setting
APP_ acters
LASTCHANGE
PSET_
NEWDATA New data flag. Set to 1 when new data arrives. Write
Boolean Read/Write 0-1
APP_ a 0 to this flag to clear it.
NEWDATA
Use this item to set the batch size for a particular
parameter set. The format of the string is:
3 = 20
PSET_
Word, Writing a parameter set number to this item will reset
RESETBC Write Only 0-999
Short the batch counter for that parameter set
APP_RESETBC
N ote: The Program Messages command set is currently only supported on the Power Focas 6000.
See Also:
Refer to the Open Protocol Specification for exact details on what the device accepts
See Appendix for examples
www. ptc.com
40 Torq u e Tool Eth ern et Driver
* * Depending on the Controller setup, PSET ID can be interpreted as an Identifier or an Index. Please refer to
the Open Protocol Specification for exact details on how the device behaves in these scenarios.
Dat a Dat a
It em Access Descript ion
Type Range
SELECTOR_ Word, Read
The ID of the selector device. 0-99
DEVICE_ID Short Only
SELECTOR_
Word, Read
NUM_ The number of sockets on the selector device. 0-99
Short Only
SOCKETS
SELECTOR_ The status of the socket:
Read
SOCKET_ Boolean* 0 = socket not lifted 0-1
Only
STATUS 1 = socket lifted
SELECTOR_ String Write Use this item to set the lights on the selector socket 102 char-
GREEN_ Only device. The format of the string is: acters
LIGHTS DEVICEID = LIGHTDATA
SELECTOR_ Device ID:
RED_ 0-99
LIGHTS Where DEVICEID is the device ID of the selector socket
and LIGHTDATA is a list of values for each socket in Light Data:
order. Those values can be:
0 = Off (Rev 0,1) 8
1 = Steady characters
2 = Flashing
www. ptc.com
Torque Tool Ethernet Driver 41
Dat a Dat a
It em Access Descript ion
Type Range
(Rev 2) 1-
For example, to turn off the first two socket lights and set 99 char-
the last two sockets to flashing on a selector with a device acters
ID of 2 the value would be:
2=00220000 (Rev 0,1)
2=0022 (Rev 2)
* This item requires an array index or bit index. The valid array / bit index range is 1 to 99.
www. ptc.com
42 Torq u e Tool Eth ern et Driver
www. ptc.com
Torque Tool Ethernet Driver 43
N ote: Any commands that require special revisions (such as 2, 3, and so forth) are not supported by the
FEP Protocol model.
www. ptc.com
44 Torq u e Tool Eth ern et Driver
Ethernet Errors
Unable t o bind t o adapt er: <adapt er name>. Connect failed.
Winsock init ializat ion failed (OS Error = <error code>).
Winsock shut down failed (OS Error = <error code>).
Winsock V1.1 or higher must be inst alled t o use t he driver.
Runtime Errors
Device <device name> failed t o connect .
Device <device name> is not responding.
Unable t o read t ag <t ag name>: Device <device name> encount ered a parsing error.
Unable t o read t ag <t ag name>: Device <device name> received an error response (Error
<error code>).
Unable t o read unsolicit ed packed dat a group: Device <device name> received an error
response (Error <error code>).
Unable t o writ e t ag <t ag name>: Device <device name> encount ered a parsing error.
Unable t o writ e t ag <t ag name>: Device <device name> received an error response (Error
<error code>).
Unable t o writ e t ag <t ag name>: Device <device name> received invalid dat a for writ e.
Unable t o writ e t o <address> on device <device name>.
Error Codes
Error Codes
www. ptc.com
Torque Tool Ethernet Driver 45
Possible Cause:
A tag address that has been specified statically references a location that is beyond the range of supported
locations for the device.
Solution:
Verify that the address is correct; if it is not, re-enter it in the client application.
Possible Cause:
A tag address that has been specified statically is requesting an array size that is too large for the address
type or block size of the driver.
Solution:
Re-enter the address in the client application to specify a smaller value for the array or a different starting
point.
Possible Cause:
A tag address that has been specified statically contains an array reference for an address type that doesn't
support arrays.
Solution:
Re-enter the address in the client application to remove the array reference or correct the address type.
Dat a t ype <t ype> is not valid for device address <address>.
Error Type:
Warning
Possible Cause:
A tag address that has been specified statically has been assigned an invalid data type.
Solution:
Modify the requested data type in the client application.
www. ptc.com
46 Torq u e Tool Eth ern et Driver
Warning
Possible Cause:
An invalid tag address has been specified in a dynamic request.
Solution:
Re-enter the address in the client application.
Possible Cause:
A tag address that has been specified statically has a requested access mode that is not compatible with
what the device supports for that address.
Solution:
Change the access mode in the client application.
Possible Cause:
The specified adapter is not working properly or is not installed correctly.
Solution:
Make sure that the correct Ethernet adapter is chosen, and verify that it is functioning properly.
OS
Indicat ion Possible Solut ion
Error
10091 Indicates that the underlying network subsystem is Wait a few seconds and restart the driver.
not ready for network communication.
10067 Limit on the number of tasks supported by the Win- Close one or more applications that may
dows Sockets implementation has been reached. be using Winsock and restart the driver.
Possible Cause:
Indicates that Winsock encountered a problem when shutting down.
www. ptc.com
Torque Tool Ethernet Driver 47
Possible Cause:
The version number of the Winsock DLL found on the system is less than 1.1.
Solution:
Upgrade Winsock to version 1.1 or higher.
Possible Cause:
1. The device is offline.
Solution:
1. Verify that the device is online.
Possible Cause:
1. The device does not support the specified command set.
2. The response from the device took longer to receive than the amount of time specified in the
"Request Timeout" device property.
5. The device cannot answer the request within the allotted time.
Solution:
1. Verify that the device is online.
2. Increase the Request Timeout property so that the entire response can be handled.
www. ptc.com
48 Torq u e Tool Eth ern et Driver
4. Increase the timeout value to allow the device more time to respond.
Unable t o read t ag <t ag nam e>: Device <device nam e> encount ered a pars-
ing error.
Error Type:
Warning
Possible Cause:
1. The device supports a different command set version than standard.
Solution:
Use channel diagnostics to verify that the received packet is in the correct format.
Unable t o read t ag <t ag nam e>: Device <device nam e> received an error
response (Error <error code>).
Error Type:
Warning
Possible Cause:
1. The device does not support the specified command set.
Solution:
Look up the error code.
See Also:
Error Codes
Unable t o read unsolicit ed packed dat a group: Device <device nam e>
received an error response (Error <error code>).
Error Type:
Warning
Possible Cause:
An unsolicited message hasn’t been received for the requested data group.
Solution:
After receiving an unsolicited message for the requested data group, the reads will no longer fail.
www. ptc.com
Torque Tool Ethernet Driver 49
See Also:
Error Codes
Unable t o writ e t ag <t ag nam e>: Device <device nam e> encount ered a
parsing error.
Error Type:
Warning
Possible Cause:
1. The device supports a different command set version than standard.
Solution:
Use channel diagnostics to verify that the received packet is in the correct format.
Unable t o writ e t ag <t ag nam e>: Device <device nam e> received an error
response (Error <error code>).
Error Type:
Warning
Possible Cause:
1. The device does not support the specified command set.
Solution:
Look up the error code.
See Also:
Error Codes
Unable t o writ e t ag <t ag nam e>: Device <device nam e> received invalid
dat a for writ e.
Error Type:
Warning
Possible Cause:
The data that was written to a tag was not in the proper format.
Solution:
View the information for the named tag to learn the proper format for data writes.
www. ptc.com
50 Torq u e Tool Eth ern et Driver
Possible Cause:
1. The named device may not be connected to the network.
2. The named device may have been assigned an incorrect Network ID.
Solution:
1. Check the hardware network connections.
2. Verify that the Network ID given to the named device matches that of the actual device.
Error Codes
www. ptc.com
Torque Tool Ethernet Driver 51
www. ptc.com
52 Torq u e Tool Eth ern et Driver
00360006001000000000250100207YYYY201
where:
YYYY = PSET ID
For example, to read the program with PSET ID 3, write the following string to the PSET_PROGRAM_READ tag:
003600060010000000002501002070003201
where:
AAAA = Total length
YYYY = PSET ID
XXXX = Length of the program
The program must then be added to the header for a complete payload. For example, the following will write
a simple program to PSET ID 12:
16542500002000000000201001010000040100000000012001601{"changeState":2,"re-
vision":43,"id":{"value":
[207,5,207,152,224,99,74,44,136,52,224,208,238,183,216,17]},"versionId":{"value":
{"value":[135,165,107,190,250,248,69,229,136,225,236,201,21,253,42,64]}},"user-
":"ExternalwebHMI","timestamp":{"value":1557216299},"-
name":"Program","descr":"","indexId":
{"value":5},"threadDirection":1,"tighteningType":2,"operationMode":1,"looseningId":
{"value":[67,154,12,156,38,192,77,122,190,129,177,188,221,140,194,196]},"steps":
[{"internalNumber":1,"stepNumber":0,"nextInternalNumber":2,"stepPath":1,"type":10},
{"intern-
alNum-
ber-
":2,"stepNum-
ber":1,"nextInternalNumber":10,"stepPath":1,"type":13,"stepTightenToAngle":
{"motorControlSpeedRamp":
{"speedTar-
get":60,"ac-
celeration":500,"speedRampType":1},"brake":true,"angleTarget":80,"speedRampChanges":
www. ptc.com
Torque Tool Ethernet Driver 53
[],"brakeConfig":{"brakeType":1,"configErgoStop":{"isBrakeRamp-
timeAdaptive":true,"rampTime":200}}}},{"intern-
alNum-
ber":10,"stepNumber":9,"nextInternalNumber":10,"stepPath":1,"type":11}],"syncPoints":
[],"programRestrictions":[{"internalNumber":7,"type":2,"timeHigh":
{"timeLimitHigh":30}},{"internalNumber":8,"type":1,"torqueHigh":{"torqueLim-
itHigh":10}}],"stepMonitors":[{"intern-
alNumber":3,"startInternalStepNumber":2,"type":2,"peakTorque":{}},
{"internalNumber":4,"startInternalStepNumber":2,"type":6,"angle":{"stopCondi-
tion":2}}],"stepRestrictions":[{"intern-
alNumber":5,"startInternalStepNumber":2,"type":3,"timeHigh":{"timeLimitHigh":5}},
{"internalNumber":6,"startInternalStepNumber":2,"type":1,"torqueHigh":{"torqueLim-
itHigh":10}}],"programMonitors":[{"internalNumber":9,"type":1,"angle":{"enabled":-
false,"stopCondition":2}}]}
Troubleshooting
l The maximum program size that can be handled with these calls is 9967 bytes since the maximum
protocol message size has to be specified by a 4-digit number. This is a limitation imposed by the
Open Protocol. If a program has a length longer than 9967 bytes then the device does not respond to
the program read requests.
l Subscribing to MID 2501 updates are not supported through the server. The header for PSET_
PROGRAM_READ must specify MID 6 or MID 2501 depending on the model and firmware of the
device. MID 8 (Generic Subscribe) is not supported for this message.
l When writing to either PSET_PROGRAM_READ or PSET_PROGRAM_WRITE and an error occurs with
response “Error 1” this usually means the payload is not correct. Verify the lengths are correct and
check with the device appendix documentation to verify the payload is in the correct format.
l When writing to the PSET_PROGRAM_WRITE tag and an error occurs with response “Error 79” this usu-
ally means that the JSON Program Definition within the message payload was invalid.
www. ptc.com
54 Torq u e Tool Eth ern et Driver
Index
1201.OPERATION_TYPE 36
1201.RESULT_DATA_ID 37
1201.RESULT_STATUS 37
1201.TIME 37
1202.OBJECT_ID 37
1202.RESULT_DATA_ID 37
AD_BATCH 19
AD_SETTING 19
Address <address> is out of range for the specified device or register. 45
Address Descriptions 15
ALARM_C_READY 19
ALARM_ERROR 19
ALARM_NEWDATA 19
ALARM_STATUS 19
ALARM_T_HEALTH 19
ALARM_T_READY 19
ALARM_TEXT 19
ALARM_TIME 19
AM_MODE 19
AM_NEWDATA 20
APP_BSIZE 39
APP_LASTCHANGE 39
APP_NEWDATA 39
APP_NUMBER 39
APP_RESETBC 39
APPD_AMAX 38
APPD_AMIN 38
APPD_ATARG 38
APPD_BSIZE 37
APPD_DIR 37
APPD_ID 37
www. ptc.com
Torque Tool Ethernet Driver 55
APPD_NAME 37
APPD_TMAX 37
APPD_TMIN 37
APPD_TTARG 38
APPN_COUNT 38
APPN_ID 38
Array size is out of range for address <address>. 45
Array support is not available for the specified address: <address>. 45
Attempts Before Timeout 11
Channel Assignment 8
COMM_CELL_ID 20
COMM_CHANNEL_ID 20
COMM_CLIENT_ID 20
COMM_CONTROL_NAME 20
COMM_CONTROL_SER_NUM 20
COMM_CONTROL_SOFT_VER 20
COMM_LINK_SUPPORT 20
COMM_PROTOCOL_VERSION 20
COMM_RBU_TYPE 20
COMM_SEO_NUM_SUPPORT 20
COMM_STATION_ID 20
COMM_STATION_NAME 20
COMM_SUPPLIER_CODE 20
COMM_SYS_SUBTYPE 20
COMM_SYS_TYPE 21
COMM_TOOL_SOFT_VER 21
Command Set: Alarm 18, 36
Command Set: Auto-Disable Settings 19
Command Set: Communication 20
Command Set: Flash 21
Command Set: Identifiers 21
Command Set: IO Interface 22
Command Set: Job Data 24
Command Set: Job Info 23
Command Set: Job Number Data 26
Command Set: Last Tightening Results 26
www. ptc.com
56 Torq u e Tool Eth ern et Driver
Data Collection 9
Data type <type> is not valid for device address <address>. 45
Data Types Description 15
Device <device name> failed to connect. 47
Device <device name> is not responding. 47
Device address <address> contains a syntax error. 45
Device address <address> is read only. 46
Do Not Scan, Demand Poll Only 10
Driver 8
Error Codes 50
Error Descriptions 44
Event Log Messages 44
FLASH 21
www. ptc.com
Torque Tool Ethernet Driver 57
General 8
Help Contents 4
ID 8
ID_BYPASS 21
ID_DOWNLOAD 21
ID_RESET 21
ID_RESETALL 21
Identification 8
Initial Updates from Cache 10
Inter-Request Delay 11
JOB_ABORT 24
JOB_BATCH_INCREMENT 24
JOB_BCOUNT 23
JOB_BMODE 23
JOB_BSIZE 23
JOB_JOBNUMLINK_LINKNUM 23
JOB_NEWDATA 24
JOB_RESTART 24
JOB_SCOUNT 24
JOB_STATUS 23
JOB_STEP 23
JOB_STYPE 24
JOB_TIME 23
JOB_TSTATUS 24
JOBDATA_BATCH_MODE 25
JOBDATA_FORCED_ORDER 24
JOBDATA_JOBID 24
www. ptc.com
58 Torq u e Tool Eth ern et Driver
JOBDATA_LINE_CONTROL 25
JOBDATA_LOCK_ON_DONE 25
JOBDATA_MAX_COMPLETION_TIME 25
JOBDATA_MAX_FIRST_TIGHTENING_TIME 25
JOBDATA_NAME 24
JOBDATA_PARAMETER_AUTO_VALUE 25
JOBDATA_PARAMETER_BATCH_SIZE 25
JOBDATA_PARAMETER_CHANNEL_ID 25
JOBDATA_PARAMETER_COUNT 25
JOBDATA_PARAMETER_SOCKET 25
JOBDATA_PARAMETER_STEP_NAME 25
JOBDATA_PARAMETER_STEP_TYPE 25
JOBDATA_PARAMETER_TYPE_ID 25
JOBDATA_REPEAT_JOB 25
JOBDATA_TOOL_LOOSENING 25
JOBDATA_TOOL_RESERVED 25
JOBN_COUNT 26
JOBN_ID 26
LINK_ABORT 24
LINK_BCOUNT 23
LINK_BMODE 23
LINK_BSIZE 23
LINK_NEWDATA 24
LINK_RESTART 24
LINK_STATUS 23
LINK_TIME 23
LINKN_COUNT 26
LINKN_ID 26
LTR_ANGLE_MAX 27
LTR_ANGLE_MIN 27
LTR_ANGLE_STATUS 27
LTR_ANGLE_TARGET 27
LTR_ANGLE_VALUE 27
LTR_BATCH_COUNTER 26
LTR_BATCH_SIZE 26
LTR_BATCH_STATUS 27
www. ptc.com
Torque Tool Ethernet Driver 59
LTR_CELL_ID 26
LTR_CHAN_ID 26
LTR_CHANGETIME 27
LTR_CM_MAX 30
LTR_CM_MIN 30
LTR_CM_VALUE 30
LTR_CMON_STATUS 28
LTR_CUSTOM_ERR 31
LTR_ID 27
LTR_IDR2 31
LTR_IDR3 31
LTR_IDR4 31
LTR_JOB 26
LTR_JOB_SEQ_NUM 30
LTR_NEWDATA 31
LTR_PSET 26
LTR_PSET_NAME 30
LTR_PT 30
LTR_PTC_STATUS 28
LTR_PTM_MAX 30
LTR_PTM_MIN 30
LTR_PTM_STATUS 28
LTR_PVT 28
LTR_RDA_MAX 30
LTR_RDA_MIN 30
LTR_RDA_STATUS 28
LTR_RDA_VALUE 30
LTR_RESULT_TYPE 30
LTR_SERIAL_NUM 30
LTR_ST_MAX 30
LTR_ST_MIN 30
LTR_ST_STATUS 28
LTR_ST_TORQUE 30
LTR_STID 30
LTR_STRAT_OPT 28
LTR_STRATEGY 27
LTR_TC_NAME 26
LTR_TERR_STATUS 28
LTR_TERR_STATUS_COMBINED 29
www. ptc.com
60 Torq u e Tool Eth ern et Driver
LTR_TERR_STATUS2 29
LTR_TERR_STATUS2_COMBINED 29
LTR_TIGHT_STATUS 27
LTR_TIMESTAMP 27
LTR_TORQUE_MAX 27
LTR_TORQUE_MIN 27
LTR_TORQUE_STATUS 27
LTR_TORQUE_TARGET 27
LTR_TORQUE_VALUE 27
LTR_UNITS 30
LTR_VIN 26
Message IDs 16
MID 2501 53
MID_ID 22
MID_IN_ORDER 22
MID_NEWDATA 22
MID_STATUS 22
MID_TYPE 21
Model 8
MS_AMAX 32
MS_AMIN 32
MS_ATARG 32
MS_BCOUNT 31
MS_BSIZE 31
MS_BSTATUS 31
MS_CHANGETIME 32
MS_JOBNUM 31
MS_NEWDATA 32
MS_NUMBER 31
MS_PSET 31
MS_SYNCID 32
MS_SYNCSTAT 32
MS_TIME 32
MS_TMAX 31
MS_TMIN 31
MS_TTARG 31
www. ptc.com
Torque Tool Ethernet Driver 61
MS_VIN 31
Name 8
Operating Mode 9
Optimizing Communications 14
OTR_ANGLE 33
OTR_ANGSTAT 33
OTR_BATSTAT 33
OTR_BCOUNT 33
OTR_BSIZE 34
OTR_CMSTAT 34
OTR_CMVALUE 35
OTR_CUSTOM_ERR 36
OTR_ID 33
OTR_ID2 36
OTR_ID3 36
OTR_ID4 36
OTR_JOBNUM 33
OTR_JOBSEQ 35
OTR_PSET 33
OTR_PTCSTAT 34
OTR_PTMSTAT 34
OTR_PTORQUE 35
OTR_PVT 36
OTR_RANGLE 35
OTR_RASTAT 34
OTR_RTYPE 35
OTR_SERIAL 35
OTR_STATION_ID 36
OTR_STATION_NAM 36
OTR_STID 35
OTR_STORQUE 35
OTR_STRATEGY 33
www. ptc.com
62 Torq u e Tool Eth ern et Driver
OTR_STROPT 34
OTR_STSTAT 34
OTR_TERR_STATUS2 36
OTR_TERR_STATUS2_COMBINED 36
OTR_TERRSTAT 34
OTR_TERRSTAT_COMBINED 35
OTR_TIGHTSTAT 33
OTR_TIME 33
OTR_TORQSTAT 33
OTR_TORQUE 33
OTR_TVUNIT 35
OTR_VIN 33
Overview 4
Program Messages 52
PSD_AMAX 38
PSD_ATARG 38
PSD_BSIZE 37
PSD_DIR 37
PSD_ID 37
PSD_NAME 37
PSD_TMAX 37
PSD_TMIN 37
PSD_TTARG 38
PSET_BSIZE 39
PSET_LASTCHANGE 39
PSET_NEWDATA 39
PSET_NUMBER 38
PSET_PROGRAM_READ 39, 52
PSET_PROGRAM_RESPONSE_ALL 40
PSET_PROGRAM_RESPONSE_BODY 40
PSET_PROGRAM_RESPONSE_HEADER 40
PSET_PROGRAM_WRITE 39
PSET_RESETBC 39
PSN_COUNT 38
PSN_ID 38
www. ptc.com
Torque Tool Ethernet Driver 63
Redundancy 13
RELAY_FUNCTION.# 22
Request Timeout 10
RESET_DIGITAL_INPUT 22
Respect Tag-Specified Scan Rate 10
Scan Mode 9
SELECTOR_DEVICE_ID 40
SELECTOR_GREEN_LIGHTS 40
SELECTOR_NUM_SOCKETS 40
SELECTOR_RED_LIGHTS 40
SELECTOR_SOCKET_STATUS 40
SET_DIGITAL_INPUT 22
Settings 12
Setup 4
Simulated 9
SPD_ANGLE 32
SPD_ASTATUS 32
SPD_CHAN 32
SPD_NUM 32
SPD_STATUS 32
SPD_TORQUE 32
SPD_TSTATUS 32
STATUS_DIGIN_# 23
STATUS_RELAY_# 22
www. ptc.com
64 Torq u e Tool Eth ern et Driver
TOOLDATA_CSERIAL 41
TOOLDATA_FWV1 43
TOOLDATA_FWV2 43
TOOLDATA_GEAR_RATIO 41
TOOLDATA_LAST_SERV_DATE 41
TOOLDATA_LCD 41
TOOLDATA_MOTOR_SIZE 42
TOOLDATA_NT 42
TOOLDATA_OPEN_END_DATA 42
TOOLDATA_PRIMARY_TOOL 42
TOOLDATA_TFULL_SPEED 42
TOOLDATA_TIGHT_SINCE_SERV 42
TOOLDATA_TMAX_TORQUE 42
TOOLDATA_TMODEL 42
TOOLDATA_TSERIAL 42
TOOLDATA_TTYPE 42
VIN_NEWDATA 43
VIN_VIN 43
VIN_VIN2 43
VIN_VIN3 43
VIN_VIN4 43
www. ptc.com
Torque Tool Ethernet Driver 65
www. ptc.com