OpenProtocol W7 7.0

User Manual
PowerFocus
Open Protocol 7.0
Version 34 / 20th March 2007
By Atlas Copco Tools

th
Power Focus Open Protocol 7.0 User Manual Version 34 / 20 March 2006
1. REVISIONS .............................................................................................................................................................5
2. TERMINOLOGY ....................................................................................................................................................6
3. POWER FOCUS OPEN PROTOCOL ..................................................................................................................7

3.1 COMMUNICATION .................................................................................................................................................7
3.1.1 Ethernet protocol .........................................................................................................................................7
3.1.2 Serial protocol .............................................................................................................................................7
3.1.2.3 Serial cable loss detection ON with keep alive .......................................................................................10
3.1.2.4 Serial cable loss detection OFF, keep alive not needed .........................................................................10
3.2 MESSAGE STRUCTURE ........................................................................................................................................11
3.3 HEADER .............................................................................................................................................................11
3.4 DATA FIELD........................................................................................................................................................11
3.5 MESSAGE END....................................................................................................................................................12
4. AVAILABLE MESSAGES ...................................................................................................................................13
5. COMMUNICATION ............................................................................................................................................16
5.1 REQUEST / RESPONSE TELEGRAM .......................................................................................................................16
5.2 EVENT TELEGRAM .............................................................................................................................................17
5.3 COMMUNICATION TELEGRAM .............................................................................................................................19
5.3.1 Communication start (MID = 0001) ..........................................................................................................19
5.3.2 Communication start acknowledge (MID = 0002) ....................................................................................19
5.3.3 Communication stop (MID = 0003)...........................................................................................................21
5.4 REQUEST ANSWER ..............................................................................................................................................22
5.4.1 Command error (MID = 0004)..................................................................................................................22
5.4.2 Command accepted (MID = 0005) ............................................................................................................24
5.5 PARAMETER SET TELEGRAMS .............................................................................................................................25
5.5.1 Parameter set number upload request (MID = 0010) ...............................................................................25
5.5.2 Parameter set numbers upload reply (MID = 0011) .................................................................................25
5.5.3 Parameter set data upload request (MID = 0012) ...................................................................................26
5.5.4 Parameter set data upload reply (MID = 0013)........................................................................................27
5.5.5 Parameter set “selected” subscribe (MID = 0014)...................................................................................28
5.5.6 Parameter set selected (MID = 0015) .......................................................................................................28
5.5.7 Parameter set selected acknowledge (MID = 0016)..................................................................................28
5.5.8 Parameter set “selected” unsubscribe (MID = 0017)...............................................................................29
5.5.9 Select Parameter set (MID = 0018)...........................................................................................................29
5.5.10 Set Parameter Set batch size (MID = 0019) ............................................................................................30
5.5.11 Reset Parameter Set batch counter (MID = 0020) ..................................................................................30
5.6 JOB TELEGRAM ...................................................................................................................................................31
5.6.1 Job numbers upload request (MID = 0030) ..............................................................................................31
5.6.2 Job numbers upload reply (MID = 0031)..................................................................................................31
5.6.3 Job data upload request (MID = 0032) .....................................................................................................32
5.6.4 Job data upload reply (MID = 0033) ........................................................................................................33
5.6.5 Job “info” subscribe (MID =0034) ...........................................................................................................34
5.6.6 Job “info” (MID = 0035) ..........................................................................................................................35
5.6.7 Job “info” acknowledge (MID = 0036) ....................................................................................................35
5.6.8 Job “info” unsubscribe (MID = 0037) ......................................................................................................36
5.6.9 Select Job in POWER FOCUS (MID = 0038) ...........................................................................................37
5.6.10 Job restart (MID = 0039) ........................................................................................................................37
5.7 TOOL TELEGRAM ................................................................................................................................................38
5.7.1 Tool data upload request (MID = 0040) ...................................................................................................38
5.7.2 Tool data upload (MID = 0041) ................................................................................................................38
5.7.3 Disable tool (MID = 0042) ........................................................................................................................40
5.7.4 Enable tool (MID = 0043) .........................................................................................................................40
5.7.5 Disconnect tool request (MID = 0044)......................................................................................................40
5.7.6 Set calibration value request (MID = 0045)..............................................................................................41
5.8 VIN TELEGRAM ..................................................................................................................................................42
5.8.1 Vehicle Id Number download request (MID = 0050) retired ....................................................................42
Page 2(103)
th
5.8.2 Vehicle Id Number upload subscribe (MID = 0051) .................................................................................42

5.8.3 Vehicle Id Number upload (MID = 0052) .................................................................................................43
5.8.4 Vehicle Id Number upload acknowledge (MID = 0053)............................................................................43
5.8.5 Vehicle Id Number upload unsubscribe (MID = 0054) .............................................................................44
5.9 TIGHTENING RESULT TELEGRAM.........................................................................................................................45
5.9.1 Last tightening result data subscribe (MID = 0060) .................................................................................45
5.9.2 Last tightening result data upload reply (MID = 0061) ............................................................................45
5.9.3 Last tightening result data acknowledge (MID = 0062)............................................................................52
5.9.4 Last tightening result data unsubscribe (MID = 0063) .............................................................................52
5.9.5 Old tightening result upload request (MID = 0064)..................................................................................53
5.9.6 Old tightening result reply (MID = 0065) .................................................................................................54
5.10 ALARM TELEGRAM ...........................................................................................................................................58
5.10.1 Alarm subscribe (MID = 0070) ...............................................................................................................58
5.10.2 Alarm Upload reply (MID = 0071)..........................................................................................................58
5.10.3 Alarm upload acknowledge (MID = 0072)..............................................................................................59
5.10.4 Alarm unsubscribe (MID = 0073) ...........................................................................................................59
5.10.5 Alarm acknowledged on torque controller (MID = 0074).......................................................................59
5.10.6 Alarm acknowledged on torque controller ack (MID = 0075) ................................................................60
5.10.7 Alarm status (MID = 0076) .....................................................................................................................60
5.10.8 Alarm status acknowledge (MID = 0077)................................................................................................61
5.10.9 Acknowledge alarm remotely on torque controller (MID = 0078).........................................................61
5.11 TIME TELEGRAM...............................................................................................................................................62
5.11.1 Read time upload request (MID = 0080).................................................................................................62
5.11.2 Time upload reply (MID = 0081) ............................................................................................................62
5.11.3 Set Time in Torque Controller (MID = 0082)..........................................................................................62
5.12 MULTI SPINDLE STATUS TELEGRAM ..................................................................................................................63
5.12.1 Multi spindle status (MID = 0090) ..........................................................................................................63
5.12.2 Multi spindle status upload (MID = 0091) ..............................................................................................63
5.12.3 Multi spindle status upload acknowledge (MID = 0092) ........................................................................64
5.12.4 Multi spindle status unsubscribe (MID = 0093) ......................................................................................64
5.13 MULTI SPINDLE RESULT TELEGRAM ..................................................................................................................65
5.13.1 Multi spindle result subscribe (MID = 0100) ..........................................................................................65
5.13.2 Multi spindle result upload (MID = 0101) ..............................................................................................65
5.13.3 Multi spindle result upload acknowledge (MID = 0102).........................................................................67
5.13.4 Multi spindle result unsubscribe (MID = 0103) ......................................................................................67
5.14 USER INTERFACE TELEGRAM ............................................................................................................................68
5.14.1 Display user text on compact (MID = 110) .............................................................................................68
5.14.2 Display user text on graph (MID = 111) .................................................................................................68
5.14.3 Flash green light on tool (MID = 113) ....................................................................................................69
5.15 JOB TELEGRAM ADVANCED ..............................................................................................................................70
5.15.1 Job line control info subscribe (MID = 0120) .........................................................................................70
5.15.2 Job line control started (MID = 0121) ....................................................................................................70
5.15.3 Job line control alert 1 (MID = 0122).....................................................................................................70
5.15.4 Job line control alert 2 (MID = 0123).....................................................................................................71
5.15.5 Job line control done (MID = 0124)........................................................................................................71
5.15.6 Job line control info acknowledge (MID = 0125) ...................................................................................71
5.15.7 Job line control info unsubscribe (MID = 0126) .....................................................................................72
5.15.8 Abort Job (MID = 0127)..........................................................................................................................73
5.15.9 Job batch increment (MID = 0128) .........................................................................................................73
5.15.10 Job batch decrement (MID = 0129) ......................................................................................................73
5.15.11 Job off (MID = 130)...............................................................................................................................74
5.15.12 Execute dynamic job request (MID = 140)............................................................................................75
5.8 Multiple Identifiers telegram ........................................................................................................................77
5.8.1 Identifier download request (MID = 0150) ...............................................................................................77
5.8.2 Multiple Identifiers work order upload subscribe (MID = 0151)..............................................................77
5.8.3 Multiple Identifiers work order upload (MID = 0152) ..............................................................................78
5.8.4 Multiple Identifiers work order upload acknowledge (MID = 0153) ........................................................79
5.8.5 Multiple Identifiers work order upload unsubscribe (MID = 0154)..........................................................79
5.8.6 Bypass Identifier (MID = 0155).................................................................................................................80
5.8.7 Reset latest Identifier (MID = 0156)..........................................................................................................80
Page 3(103)
th
5.8.8 Reset all Identifiers (MID = 0157).............................................................................................................80

5.16 I/O INTERFACE .................................................................................................................................................81
5.16.1 Set “external controlled” relays (MID = 200) ........................................................................................81
5.16.2 Status “external monitored inputs” subscribe (MID = 0210) .................................................................82
5.16.3 Status “external monitored inputs” upload (MID = 211) .......................................................................82
5.16.4 Status “external monitored inputs” upload acknowledge (MID = 212)..................................................83
5.16.5 Status “external monitored inputs” unsubscribe (MID = 213) ...............................................................83
5.16.6 IO device status request (MID = 0214) ...................................................................................................84
5.16.7 IO device status (MID = 0215) ................................................................................................................85
5.16.8 Relay function subscribe (MID = 0216) ..................................................................................................92
5.16.9 Relay function upload (MID = 0217) ......................................................................................................93
5.16.10 Relay function upload acknowledge (MID = 0218)...............................................................................93
5.16.11 Relay function unsubscribe (MID = 0219) ............................................................................................94
5.17 STATISTIC TELEGRAMS .....................................................................................................................................95
5.17.1 Histogram upload request (MID = 0300)................................................................................................95
5.17.2 Histogram upload request reply (MID = 0301).......................................................................................96
5.18 AUTOMATIC/MANUAL MODE TELEGRAM (ONLY FOR POWERMACS).................................................................97
5.18.1 Automatic/Manual mode subscribe (MID = 0400) ..................................................................................97
5.18.2 Automatic/Manual mode upload (MID = 0401) ......................................................................................97
5.18.3 Automatic/Manual mode upload acknowledge (MID = 0402) ................................................................97
5.18.4 Automatic/Manual mode unsubscribe (MID = 0403) ..............................................................................98
5.18.5 AutoDisable settings request (MID = 0410) ............................................................................................98
5.18.6 AutoDisable settings reply (MID = 0411) ...............................................................................................98
5.19 OPEN PROTOCOL COMMANDS DISABLED .........................................................................................................99
5.19.1 Open protocol commands disabled subscribe (MID = 0420)................................................................100
5.19.2 Open protocol commands disabled upload (MID = 0421)....................................................................100
5.19.3 Open protocol commands disabled upload acknowledge (MID = 0422) ..............................................100
5.19.4 Open protocol commands disabled unsubscribe (MID = 0423)............................................................101
5.20 KEEP ALIVE TELEGRAM ..................................................................................................................................102
5.20.1 Keep alive message (MID = 9999) ........................................................................................................102
6. COMMUNICATION FLOW CHART EXAMPLE .........................................................................................103
6.1 Establish a connection and set result subscription .....................................................................................103
Page 4(103)
th
1. Revisions
Rev. Date Revised by Detailed description
1 June 28, 2001 LM Initial revision
2 Sept 12, 2001 LM Job MIDs added
3 Sept 14, 2001 LM Serial communication
4 Nov 2, 2001 LM MID 0019, 0020, 0038 added
5 Nov 23, 2001 LM MID 34, 35, 36, 37 changed
6 Dec 14, 2001 LM Added time stamp in MID 35
7 Jan 14, 2002 LM MID 90, 91, 92, 93 added
8 Feb 12, 2002 LM Answer to MID 003
9 Feb 15, 2002 LM Serial communication with 3964R handshake
10 Feb 19, 2002 LM New MID 100, 101, 102, 103
11 Mar 22, 2002 LM MID 41 corrected
12 Aug 05, 2002 LM MID 113 added
13 Aug 17, 2002 LM MID 110, 111, 120-129, 200 added
14 Feb 5, 2003 AM MID 33 defined (job data upload reply)
Added MID 214, 215 (IO device status)
5.5.5, 5.5.6 updated
Header added to document
Minor errors corrected
15 Feb 10, 2003 LM MID revision introduced
New revision of MID 61, 65
16 May 11, 2003 LM Several client session allowed at the same time (max
5).
New feature MID 64, possible to get the last tightening
result by requesting tightening Id zero.
New error code “client already connected”
17 June 09, 2003 LM MID 300, 301 added
18 August 10, 2003 LM MID 130 job off added, MID 44 added
19 September LM New MID revision for MID 61, 65,
19,2003 New MID revision for MID2
I/O tables updated
20 Mars 10, 2004 LM MID 78 added
21 June 10, 2004 LM Ack flag introduced in header.
Added support for Multiple Identifiers
MID.
New MID revision for MID 61, 65 with multiple result
identifier part.
Serial cable loss detection explained
22 Oct 24, 2004 LM MID 61 revision 5 added
MID 61 light (less than 128 bytes), MID revision 999
I/O tables updated
23 Feb 24, 2005 LM Strategy field updated in MID 61 and 65 (Home
position added).
24 Aug 2, 2005 LM Minor corrections
25 Sept 16, 2005 LM MID 45 added
26 Jan 24, 2006 LM Manual discrepancies fixed
Description of MID 130 Job Off was inverted
MID 61 rev 3 Torque values unit corrected wrong
index
27 Jan 30, 2006 MLN Chapter 5.1.18, Open protocol commands disabled,
MID 420-423
Command error codes 92-94.
Page 5(103)
th
MID 65: Pulsor parameters added (Strategy, Torque

value unit, Result type) Added strategy Yield control.
28 Feb 1, 2006 MLN Added Table 44 Open protocol commands.
29 Feb 7, 2006 MLN Added revision 3 MID 0002.
Added revision 2 MID 0041.
Added 5.18 Automatic/Manual mode telegram.
Added MID 0216, 0217, 0218,0219 Relay function.
30 Feb 13, 2006 MLN Edited length of MIDs with more than one revision.
I/O tables updated.
31 Feb 15, 2006 MLN Changed data length of tool sw version MID 2, rev 3.
Updated Relay function MIDs.
32 Mar 31, 2006 MLN Updated text in 5.16.8
33 Nov 07, 2006 LM Added MID 140, Execute dynamic Job
34 Mar 20, 2007 LM Added MID 215 revision 2
The PowerFocus Open Protocol 7.0 version 34, dated 20th of March
2007, is compatible with the PowerFocus SW-versions 7.0 and later.
2. Terminology
Subscribe :
Unsubscribe :
MID:
Message Id of the telegram
Page 6(103)
th
3. POWER FOCUS Open Protocol
3.1 Communication
The POWER FOCUS open protocol can be run using Ethernet or serial communication. The
POWER FOCUS open protocol is a FULL DUPLEX protocol, this means that data can be
exchanged between the POWER FOCUS and its partner in both direction simultaneously. In
FULL DUPLEX operation, therefore, data can be sent and received at the same time. Every
communication partner must be able to operate a send and receive facility simultaneously.
3.1.1 Ethernet protocol
The station computer connects itself to the torque controller, and the torque controller accepts
the connection. The torque controller is the server and the station computer the client.
The torque controller can accepts up to 5 connections at a time.
The protocol used is TCP/IP. The port used for the communication is 4545.
3.1.2 Serial protocol
3.1.2.1 Serial ASCII protocol on serial 2 or serial 1
The serial communication is available both on serial 1 and 2 of the POWER FOCUS,
When running serial communication, all the messages exchanged between the POWER
FOCUS and the station computer are the same as for Ethernet communication BUT must be
encapsulated between STX (ASCII 0x02) and ETX (ASCII 0x03).
Furthermore all the messages sent from the station computer to the POWER FOCUS must
be stamped with a tag before the STX character. The tag is constituted with 4 ASCII
characters following each other : BEL (ASCII 0x07) HT (ASCII 0x09) BEL (ASCII 0x07) HT
(ASCII 0x09).
In order to detect RS232 cable disconnection the POWER FOCUS has a communication
timeout equal to 15s i.e. if no message has been exchanged between the integrator and the
POWER FOCUS since the last 15s, the POWER FOCUS considers the connection as lost and
close it.
In order to keep the communication alive the integrator must send a keep alive to the POWER
FOCUS with a time interval lower than 15s.
Notice:
An inactivity timeout is suggested to integrator i.e. if no message has been exchanged during
the last 5s or 10s, send a keep alive.
3.1.2.2 Serial ASCII protocol with 3964 R handshake on serial 1
The protocol is the same as the ASCII serial open protocol (see upper “Serial ASCII protocol on
serial 2 or serial 1) but all messages exchanged between the POWER FOCUS and the
integrator is transferred within the telegram frame in accordance with Procedure 3964R.
The Procedure 3964R is a transfer protocol between two systems A and B. Every time one of
the systems wants to send something the following procedure is initiated:
- request from A to B for data interchange

- data interchange
Page 7(103)
th
- end of data interchange.
The protocol 3964R allows reliable data transfer by virtue of the fact that the receiver must first
signal to the transmitter that it is ready to receive (connection setup) and then after data
interchange must acknowledge correct reception. Data integrity is insured by an additional
block check character BCC.
The block check control is the EXORing of all the transmitted data bytes. The generation
begins with the first byte of the telegram and ends after characters DLE (ASCII 0x10 Data Link
Escape) and ETX (ASCII 0x03 End of Text).
POWER FOCUS sends
POWER FOCUS Integrator
STX
Acknowledgment
timeout 2s DLE
”Command start ack” followed STX00570002 Data /0 ETX DLE ETX BCC
with DLE, ETX, BCC
DLE
Fig 1: POWER FOCUS sends Command start acknowledge
Page 8(103)
th
POWER FOCUS receives
STX
Acknowledgment
timeout 2s
”Command start ” followed with DLE
DLE, ETX, BCC
BEL HT BEL HT STX 00200001 /0 ETX DLE ETX BCC
DLE
Fig 2: POWER FOCUS receives Command start
The POWER FOCUS sends the control character STX (ASCII 0x02 Start of Text) to setup the
connection and waits for an acknowledgment for 2s (acknowledgment timeout = 2s). If the
integrator responds with the acknowledge character DLE the POWER FOCUS reverts to
transmit mode. If the integrator responds with control character NAK (ASCII 0x15 Negative
acknowledgment) or any other control character (apart from DLE) or if the acknowledgment
delay time elapses, it means that the connection setup procedure has failed. The connection
setup procedure is aborted after a total of 6 unsuccessful attempts.
If the connection setup is successful, the POWER FOCUS sends the Open Protocol serial
command followed by the characters DLE, ETX and BCC as end identifier. The integrator
monitors the incoming time between two characters. The interval between two characters may
not exceed the character delay timeout =100 ms.
The POWER FOCUS then waits for an acknowledgement character from the integrator. If the
integrator sends the control character DLE within the acknowledgment delay time, the open
protocol telegram has been accepted error free.
If the integrator responds with control character NAK or any other character (apart from DLE),
or if the acknowledgment delay time elapses with no answer the transmission is aborted and
the POWER FOCUS starts a new connection setup with character STX. The procedure is
aborted and the POWER FOCUS sends a NAK to the integrator after a total of 6 unsuccessful
attempts.
If the integrator sends a NAK during transmission, the POWER FOCUS aborts the transmission
and repeats it in the manner described above. In the case of any other character the integrator
waits for the character delay time to elapse and then sends a NAK.
If the integrator receives a STX from the POWER FOCUS in idle state, it answers with DLE. If it
receives any other character any STX in Idle state it waits for the character delay time to elapse
and then sends a NAK.
Page 9(103)
th
After each character, the next character is awaited during the character delay time =100ms. If
the character delay time elapses without new reception a NAK is sent to the POWER FOCUS.
If the integrator detects the character string DLE ETX BCC, it terminates reception. It then
compares the BCC with the internally generated one. If the BCC is correct and no error
reception has occurred it sends a DLE to the POWER FOCUS. If the BCC is not correct a NAK
is sent to the POWER FOCUS. A retry is then awaited. If it is not possible to receive the
telegram with error free BCC after 6 attempts, the integrator aborts the reception.
What was described above can be applied to the case where the integrator is the sender and
the POWER FOCUS the receiver.
3.1.2.3 Serial cable loss detection ON with keep alive
In order to be able to detect serial cable loss, the tightening controller has a communication
timer. This timer (15 s) is reset every time it sends or receives a message on the serial line.
If no messages have been exchanged since 15 seconds, the connection is assumed to be lost
and the tightening controller close the connection. This strategy to detect cable loss implies that
the client application sends a keep alive before the timer in the tightening controller expires.
3.1.2.4 Serial cable loss detection OFF, keep alive not needed
In option, it is possible to get rid of the need of sending keep alive to the tightening controller. In
this case the controller will not be able to detect the loss of serial connection or serial cable.
But this possibility may be useful to reduce the load on certain serial devices (PLC, printers …)
which have difficulties to cope with full duplex traffic.
To get rid of the need of sending keep alive using serial connection, uncheck C452 Serial cable
loss detection.
Special Note:
In some cases, after communication lost, the tightening controller may answer to a
“Communication start” with a “Command Error (MID = 0004) / client already connected”.
This case, must be handled by the client application and may not be considered as a failure.
Page 10(103)
th
3.2 Message structure
All information sent over the communication links is ASCII format.

A message consists of three parts, header, data field and message end. The sections below
describe each part in greater details.
Header Data Field Message End

Length MID Rev Spare …. NUL
(ASCII 0x0)
20 bytes
3.3 Header
The header contains 20 bytes.
Table 1
Part Bytes Comment
Length 4 The header always contains the length of the telegram. The length is
four ASCII digits long (‘0’…’9’) specifying a range of 0000 to 9999.
The length is the length of the header plus the data field exclusive the
NULL termination.
MID 4 The MID is four byte long and is specified by four ASCII digits
(‘0’…’9’). The MID describes how to interpret the sent telegram.
Revision 3 The revision of the MID is specified by three ASCII digits (‘0’…’9’).
The MID revision is unique per MID and is used in case where
several versions are available for the same MID. Using the
revision number the station computer can subscribe or ask for
different versions of the same MID. By default the MID revision
number is three spaces (revision 1 of the MID). So, if the station
computer is interested in the initial revision (revision 1) of the
MID, it can send three spaces as MID revision or 001.
No Ack Flag 1 ONLY FOR SUBSCRIPTIONS MIDs.
The No Ack Flag is used when setting a subscription. If the No
Ack flag is not set in a subscription it means that the subscriber
will acknowledge each “push” telegram sent by the torque
controller (reliable mode).
If set, the torque controller will only push out the information
required without waiting for a receive acknowledgement from
the subscriber (unreliable mode).
Spare 8 Reserved space in the header for future use.
Special Note:
The Length and MID are padded on the left with zeroes (ASCII 0x30).
3.4 Data Field
The specific data format depends on the actual command.
Data Field ASCII data representing the data.

The data contains a list of parameters.
Page 11(103)
th
Each parameter is represented with the following structure (if nothing else is mentioned):
Id Parameter Value
Id Parameter id (“00”..”99”), length two bytes.

The parameter id is padded on the left with the ASCII characters ‘0’.
Parameter Value Parameter value is defined by parameter selection (fixed number of

bytes).
If the Parameter value is only specified by ASCII digits the parameter value is padded on the
left with the ASCII characters ‘0’.
If the Parameter value is specified by ASCII characters (taken between 0x20 and 0x7F Hex),
the parameter value is padded on the right with space <SPC> (ASCII character 0x20 Hex).
Special Notes:
All the parameters of the data field should be sent.
The data field of each message is subject to future modifications, new parameters may be
added and by the way the length of the data field could increase.
3.5 Message End
All the telegrams are NULL terminated. The NULL termination is not included in the message
length.
Page 12(103)
th
4. Available Messages
Table 2
MID Description
0001 Communication start
0002 Communication start acknowledge
0003 Communication stop
0004 Command error
0005 Command accepted
0010 Parameter set numbers upload request
0011 Parameter set numbers upload reply
0012 Parameter set data upload request
0013 Parameter set data upload reply
0014 Parameter set “selected” subscribe
0015 Parameter set “selected”
0016 Parameter set “selected” acknowledge
0017 Parameter set “selected” unsubscribe
0018 Select Parameter set
0019 Set Parameter set batch size
0020 Reset Parameter set batch size
0030 Job numbers upload request
0031 Job numbers upload reply
0032 Job data upload request
0033 Job data upload reply
0034 Job “info” subscribe
0035 Job “info”
0036 Job “info” acknowledge
0037 Job “info” unsubscribe”
0038 Select Job
0039 Job restart
0040 Tool data upload request
0041 Tool data upload reply
0042 Disable tool
0043 Enable tool
0044 Disconnect tool
0045 Set calibration value request
0050 Vehicle Id Number download request
0051 Vehicle Id Number upload subscribe
0052 Vehicle Id Number upload
0053 Vehicle Id Number upload acknowledge
0054 Vehicle Id Number upload unsubscribe
0060 Last tightening result data subscribe
0061 Last tightening result data upload
0062 Last tightening result data acknowledge
0063 Last tightening result data unsubscribe
0064 Old tightening result upload request
0065 Old tightening result reply
0070 Alarm subscribe
0071 Alarm Upload
0072 Alarm Upload acknowledge
Page 13(103)
th
0073 Alarm Unsubscribe

0074 Alarm Acknowledged on torque controller
0075 Alarm Acknowledged Ack
0076 Alarm Status
0077 Alarm Status acknowledge
0078 Acknowledge alarm remotely on torque controller
0080 Read time upload request
0081 Time upload reply
0082 Set Time in the Torque Controller
0090 Multi spindle status subscribe
0091 Multi spindle status upload
0092 Multi spindle status upload acknowledge
0093 Multi spindle status unsubscribe
0100 Multi spindle result subscribe
0101 Multi spindle result upload
0102 Multi spindle result upload acknowledge
0103 Multi spindle result unsubscribe
0110 Display user text on compact
0111 Display user text on graph
0113 Flash green light on tool
0120 Job line control info subscribe
0121 Job line control started
0122 Job line control alert 1
0124 Job line control done
0125 Job line control info acknowledge
0126 Job line control info unsubscribe
0127 Abort job
0128 Job batch increment
0129 Job batch decrement
0130 Job off
0140 Execute dynamic Job
0150 Identifier download request
0151 Multiple Identifiers work order upload subscribe
0152 Multiple Identifiers work order upload
0153 Multiple Identifiers work order upload acknowledge
0154 Multiple Identifiers work order upload unsubscribe
0155 Bypass Identifier
0156 Reset latest Identifier
0157 Reset all Identifier
0200 Set “external controlled” relays
0210 Status “external monitored inputs” subscribe
0211 Status “external monitored inputs” upload
0212 Status “external monitored inputs” upload acknowledge
0213 Status “external monitored inputs” unsubscribe
0214 IO device status request
0215 IO device status
0216 Relay function subscribe
0217 Relay function upload
0218 Relay function upload acknowledge
0219 Relay function unsubscribe
Page 14(103)
th
0300 Histogram upload request

0301 Histogram upload request reply
0400 Automatic/Manual mode subscribe
0401 Automatic/Manual mode upload
0402 Automatic/Manual mode upload acknowledge
0403 Automatic/Manual mode unsubscribe
0410 AutoDisable settings request
0411 AutoDisable settings reply
0420 Open protocol commands disabled subscribe
0421 Open protocol commands disabled upload
0422 Open protocol commands disabled upload acknowledge
0423 Open protocol commands disabled unsubscribe
8000 Reserved
8001 Reserved
8002 Reserved
8003 Reserved
9999 Keep alive message
Special Note:
Before any changes made in the MID list all concerned parties must be contacted.
Page 15(103)
th
5. Communication
The protocol can be split in two parts a “Request / Response” part, and an “Event” part which
could be describe as follow.
5.1 Request / Response telegram
The station computer sends a command to the torque controller (select Pset …). The torque
controller will always answer to this command with a positive or a negative reply (Command
accepted or Command Error).
If no answer to the request is received before the response timeout, the station computer
should re-send the request up to three times. After three times, the connection is considered as
lost and a new connection must be established.
Table 3
MID Request telegram from Station computer

0010 Parameter set numbers upload request
0012 Parameter set data upload request
0030 Job numbers upload request
0032 Job data upload request
0038 Select Job
0039 Job restart
0040 Tool data upload request
0042 Disable tool
0043 Enable tool
0064 Old tightening result upload request
0080 Read time upload request
0127 Abort job
0130 Job off
0214 IO device status request
0300 Histogram upload request
0410 AutoDisable settings request
Page 16(103)
th
5.2 Event Telegram
The torque controller can spontaneously send telegrams to the station computer after an event
(such as a rundown, an alarm …) for that event telegrams are used. This services are only
enabled by the torque controller after a request (subscription) from the station computer.
Table 4
MID Event telegram
0015 Parameter set “selected”
0035 Job “info”
0052 Vehicle Id Number upload
0061 Last tightening result data upload
0071 Alarm Upload
0074 Alarm Acknowledged on torque controller
0076 Alarm Status
0091 Multi spindle status upload
0092 Multi spindle result upload
0121 Job line control started
0124 Job line control done
0152 Multiple Identifiers work order upload
0211 Status “external monitored inputs” upload
0217 Relay function upload
0401 Automatic/Manual mode upload
0421 Open protocol commands disabled upload
The subscription is made with the Request / Response telegram. The subscription can be
cancelled at any time by the station computer by sending an unsubscribe telegram.
Table 5
MID Event telegram subscribe / unsubscribe from the Station computer
0014 Parameter set “selected” subscribe
0017 Parameter set “selected” unsubscribe
0034 Job “info” subscribe
0037 Job “info” unsubscribe”
0051 Vehicle Id Number upload subscribe
0054 Vehicle Id Number upload unsubscribe
0060 Last tightening result data subscribe
0063 Last tightening result data unsubscribe
0070 Alarm subscribe
0073 Alarm Unsubscribe
0090 Multi spindle status subscribe
0093 Multi spindle status unsubscribe
0100 Multi spindle result subscribe
0101 Multi spindle result unsubscribe
0120 Job line control info subscribe
0126 Job line control info unsubscribe
0151 Multiple Identifiers work order upload subscribe
0154 Multiple Identifiers work order upload unsubscribe
Page 17(103)
th
0210 Status “external monitored inputs” subscribe

0213 Status “external monitored inputs” unsubscribe
0216 Relay function subscribe
0219 Relay function unsubscribe
0400 Automatic/Manual mode subscribe
0403 Automatic/Manual mode unsubscribe
0420 Open protocol commands disabled subscribe
0423 Open protocol commands disabled unsubscribe
The station computer should acknowledge the event telegrams by sending the corresponding
acknowledge MID (see Table 6). If no acknowledge is received before the response timeout the
torque controller will re-send the telegram up to three times. After three times the torque
controller will consider the connection as lost.
Table 6
MID Event telegram acknowledge from the Station computer

0016 Parameter set “selected” acknowledge
0036 Job “info” acknowledge
0053 Vehicle Id Number upload acknowledge
0062 Last tightening result data acknowledge
0072 Alarm acknowledge
0092 Multi spindle status upload acknowledge
0102 Multi spindle result upload acknowledge
0125 Job line control info acknowledge
0153 Multiple Identifiers work order upload acknowledge
0212 Status “external monitored inputs” upload acknowledge
0218 Relay function upload acknowledge
0402 Automatic/Manual mode upload acknowledge
0422 Open protocol commands disabled upload acknowledge
Page 18(103)
th
5.3 Communication telegram
5.3.1 Communication start (MID = 0001)

0020 0001 Rev Spare …. NUL
(ASCII 0x0)
20 bytes 0 bytes
Enables the command link. The torque controller will not respond to any other commands
before this. The torque controller answers with a command error “Already connected” if the link
has already been enabled.
Possible answers Communication start acknowledge (MID = 0002)

Command Error (MID = 0004)
“Client already connected”
Sent by Station computer.
5.3.2 Communication start acknowledge (MID = 0002)

Length 0002 Rev Spare Data NUL
(ASCII 0x0)
20 bytes
When accepting the communication the torque controller sends as reply, a Communication
start acknowledge. This message contains some basic information about the torque controller
which accept the connection (cluster number, channel number, torque controller Name)
The length of MID 2 revision 1 is 57 bytes (37 bytes of data + 20 bytes header).
Table 7 MID 0002 revision 1
Parameter Id Bytes Comment

Cell Id 01 4 The cell number (cluster number). Is four byte long specifying a range of 0000 to
9999 and is specified by four ASCII digits (‘0’….’9’).
Channel Id 02 2 The channel Id is two byte long specifying a range of 00 to 20 and is specified by
two ASCII digits (‘0’….’9’).
Controller Name 03 25 The torque controller name is 25 byte long and is specified by 25 ASCII characters
taken between 0x20 and 0x7F Hex. (X25).
Page 19(103)
th

Supplier code 04 3 ACT (supplier code for Atlas Copco Tools POWER FOCUS)

Supplier code 04 3 ACT (supplier code for Atlas Copco Tools POWER FOCUS)
Open protocol version 05 19 Open protocol version.
PF Software version 09 19 The software version is specified by 19 ASCII characters.
Tool Software version 07 19 The software version is specified by 19 ASCII characters.
Possible answers No
Sent by the torque controller.
Example revision 1:

0057 0002 Rev Spare 010001020103controller1 NUL
(ASCII 0x0)
20 bytes 37 bytes
Page 20(103)
th
5.3.3 Communication stop (MID = 0003)

0020 0003 Rev Spare … NUL
(ASCII 0x0)
20 bytes 0 bytes
Disables the command link. The torque controller will stop to respond to any commands (except
for “Communication start” MID = 0001) after receiving this command.
Possible answers Command accepted (MID = 0005).
Page 21(103)
th
5.4 Request answer
5.4.1 Command error (MID = 0004)
This message is used by the torque controller when a request for one reason could not have
been performed. The data field contains the message Id of the telegram request that failed as
well as an error code.

0026 0004 Rev Spare MID Error NUL
(ASCII 0x0)
20 bytes 6 bytes
MID Message Id of the request rejected.
Error Error code (“00”..”99”), two bytes. See Error! Reference source not
found..
Page 22(103)
th
Table 10
Error Description
“01” Invalid data.
“02” Pset number not present
“03” Pset can not be set.
“04” Pset not running
“06” VIN upload subscription already exists
“07” VIN upload subscription does not exists
“08” VIN input source not granted
“09” Last tightening result subscription already exists
“10” Last tightening result subscription does not exist
“11” Alarm subscription already exists
“12” Alarm subscription does not exist
“13” Parameter set selection subscription already exists
“14” Parameter set selection subscription does not exist
“15” Tightening Id requested not found
“16” Connection rejected protocol busy
“17” Job number not present
“18” Job info subscription already exists
“19” Job info subscription does not exist
“20” Job can not be set
“21” Job not running
“22” Not possible to execute dynamic Job request
“30” Controller is not a sync Master
“31” Multi spindle status subscription already exists
“32” Multi spindle status subscription does not exist
“33” Multi spindle result subscription already exists
“34” Multi spindle result subscription does not exist
“40” Job line control info subscription already exists
“41” Job line control info subscription does not exist
“42” Identifier input source not granted
“43” Multiple identifiers work order subscription already exists
“44” Multiple identifiers work order subscription does not exist
“50” Status “external monitored inputs” subscription already exists
“51” Status “external monitored inputs” subscription does not exist
“52” IO device not connected
“53” Faulty IO device number
“58” No alarm present
“59” Tool currently in use
“60” No histogram available
“70” Calibration failed
“80” Reserved
“81” Reserved
“82” Automatic/Manual mode subscribe already exist
“83” Automatic/Manual mode subscribe does not exist
“84” The relay function subscription already exists
“85” The relay function subscription does not exist
“92” Open protocol commands disabled
“93” “Open protocol commands disabled ” subscription already
exists
“94” “Open protocol commands disabled” subscription does not
exist
“95” Reject request, PowerMACS is in manual mode
“96” Client already connected
“97” MID revision unsupported
“98” Controller internal request timeout
“99” Unknown MID
Page 23(103)
th
Possible answers None.
Example:
The request Select Pset (MID = 0018) failed, the Pset number was not present in the torque
controller.

0026 0004 Rev Spare 001802 NUL
(ASCII 0x0)
20 bytes 6 bytes
5.4.2 Command accepted (MID = 0005)
This message is used by the torque controller to confirm that the last request sent by the
station computer was accepted. The data field contains the MID of the request accepted.

0024 0005 Rev Spare MID NUL
(ASCII 0x0)
20 bytes 4 bytes
Possible answers None.
Example:
The request Select Pset (MID = 0018) is accepted.

0024 0004 Rev Spare 0018 NUL
(ASCII 0x0)
20 bytes 4 bytes
Page 24(103)
th
5.5 Parameter set telegrams
5.5.1 Parameter set number upload request (MID = 0010)

0020 0010 Rev Spare … NUL
(ASCII 0x0)
20 bytes 0 bytes
A request for all the valid Parameter set number of the torque controller. The result of this
command will be the transmission of all the valid Pset number of the torque controller
(Parameter set numbers upload reply MID = 0011)
Possible answers Parameter set numbers upload reply (MID = 00011).
5.5.2 Parameter set numbers upload reply (MID = 0011)
The transmission of all the valid Pset numbers of the torque controller. The data field contains
the number of valid pset currently present in the torque controller, and the number of each Pset
present.

Length 0011 Rev Spare Nbr of valid … NUL
Pset (ASCII 0x0)
20 bytes 3 bytes 3 bytes × Number
of valid Pset
Nbr of valid Pset : number of pset present in the torque controller specified by 3 bytes
(max 999).
Each Pset number is three byte long and is specified by three ASCII digits (‘0’….’9’).
Possible answers No
Used by the torque controller.
Example :
Pset 1 and 2 are presents in the torque controller

0029 0011 Rev Spare 002 001002 NUL
(ASCII 0x0)
29 bytes 3 bytes 6 bytes
Page 25(103)
th
5.5.3 Parameter set data upload request (MID = 0012)

0023 0012 Rev Spare Pset Number NUL
(ASCII 0x0)
20 bytes 3 bytes
Request to upload a parameter set data from the torque controller.
Pset Number Parameter set number, is three byte long and is specified by three ASCII
digits (‘0’….’9’)..
Possible answers Parameter set data upload reply (MID = 0013)

or
Command error (MID = 0004)
“Pset number not present ”
Used by Station computer.
Example :
Upload Pset data request for Pset number 1.

0023 0012 Rev Spare 001 NUL
(ASCII 0x0)
20 bytes 3 bytes
Page 26(103)
th
5.5.4 Parameter set data upload reply (MID = 0013)

0104 0013 Rev Spare Data NUL
(ASCII 0x0)
20 bytes 84 bytes
Upload of parameter set data reply.
Table 11
Pset id 01 3 ASCII digits. Range 0-999
Pset name 02 25 ASCII character Fill with SPC if Pset Name size < 25
Rotation direction 03 1 ASCII digit 1. CW
2. CCW
Batch size 04 2 ASCII digit Range 0-99
Torque min 05 6 ASCII digits The torque min limit is multiplied by 100 and sent
as an integer (2 decimals truncated).
Torque max 06 6 ASCII digits The torque max limit is multiplied by 100 and sent
as an integer (2 decimals truncated
Torque final target 07 6 ASCII digits The torque final target is multiplied by 100 and
sent as an integer (2 decimals truncated).
Angle min 08 5 ASCII digits The angle min value has a specified range
between 0 and 99999.
Angle max 09 5 ASCII digits The angle max value is five byte long and is
specified by five ASCII digits (‘0’….’9’).
Final Angle Target 10 5 ASCII digits The target angle has a specified range between 0
and 99999. The target angle is specified in
degrees.
Possible answers No
Sent by the torque controller
Example :
Upload Pset data for Pset number 1.

0104 0013 Rev Spare 0100102pset1 NUL
0310403050012000600150007001400080036009007201000480 (ASCII 0x0)
20 bytes 84 bytes
Page 27(103)
th
5.5.5 Parameter set “selected” subscribe (MID = 0014)

0020 0014 Rev No Ack Spare NUL
(ASCII 0x0)
20 bytes 0 bytes
A subscription for the Pset selection. A message (Parameter set selected MID = 0015) is sent
to the station computer each time a new Pset is selected. Note that the message as well is sent
after the answer (Command accepted MID = 0005) is sent, as an immediate response to the
subscribe message.
Possible answers Command accepted (MID = 0005)

Or
“Parameter set selection subscription already exists”
5.5.6 Parameter set selected (MID = 0015)

0042 0015 Rev Spare Pset YYYY-MM-DD:HH:MM:SS NUL
Nbr Date of last change in Pset setting (ASCII 0x0)
20 bytes 22 bytes
A new Pset is selected in the torque controller.

The telegram contains the number of the last pset selected as well as the date/time of the last
change done in the Pset settings. This message is also sent as an immediate response to the
subscription for the Pset selection (MID = 0014).
Possible answers New Pset selected Acknowledge (MID = 0016)
Example:

0042 0015 Rev Spare 001 2001-06-30:20:34:12 NUL
(ASCII 0x0)
20 bytes 22 bytes
5.5.7 Parameter set selected acknowledge (MID = 0016)

0020 0016 Rev Spare NUL
(ASCII 0x0)
20 bytes 0 bytes
Acknowledge for a New Pset selected.
Possible answers No
Page 28(103)
th
5.5.8 Parameter set “selected” unsubscribe (MID = 0017)

(ASCII 0x0)
20 bytes 0 bytes
Reset the subscription for the Pset selection.

Or
“Parameter set selection subscription does not exist”
5.5.9 Select Parameter set (MID = 0018)

(ASCII 0x0)
20 bytes 3 bytes
Pset Number Parameter set number represented by 3 ASCII digits (range 000 to 999).

or

“pset can not be set”
Sent by Station computer
Page 29(103)
th
5.5.10 Set Parameter Set batch size (MID = 0019)

0025 0019 Rev Spare Pset Batch size NUL
Number (ASCII 0x0)
20 bytes 5 bytes
This telegram gives the possibility to set the batch size of a parameter set in run time.
Batch Size Size of the parameter set batch represented by 2 ASCII digits
(range 00-99)

Or
“Invalid data”
5.5.11 Reset Parameter Set batch counter (MID = 0020)

(ASCII 0x0)
20 bytes 3 bytes
This telegram gives the possibility to reset the batch counter of the running parameter set in
run time.

Or
“Invalid data”
“Pset not running”
Page 30(103)
th
5.6 Job telegram
5.6.1 Job numbers upload request (MID = 0030)

(ASCII 0x0)
20 bytes 0 bytes
A request for all the valid Job numbers of the POWER FOCUS. The result of this command will
be the transmission of all the valid Job numbers of the POWER FOCUS (Job numbers upload
reply
MID = 0031)
Possible answers Job numbers upload reply (MID = 0031).
5.6.2 Job numbers upload reply (MID = 0031)

Length 0031 Rev Spare Nbr of … NUL
valid Job (ASCII 0x0)
number
20 bytes 2 bytes 2 bytes × Number of
valid Job
The transmission of all the valid Job numbers of the POWER FOCUS
Each Job number is two bytes long and is specified by three Ascii digits (‘0’….’9’). Range
(‘00’…’99’).
Possible answers No
Sent by The torque controller.
Example :
Job 1 and 2 are presents in the POWER FOCUS

26 0031 Rev Spare 02 0102 NUL
(ASCII 0x0)
20 bytes 2 bytes 2 bytes × Number of
valid Job
Page 31(103)
th
5.6.3 Job data upload request (MID = 0032)

0022 0032 Rev Spare Job Nbr NUL
(ASCII 0x0)
20 bytes 2 bytes
Request to upload the data from a specific Job from the POWER FOCUS.
Job Nbr Job Nbr is two bytes long and is specified by two Ascii digits (‘0’….’9’)
Possible answers “ Job data upload “ (MID = 0033)”

or
“Command error (MID = 0004)
“Job Nbr not present ”
Example :
00220032 01
Page 32(103)
th
5.6.4 Job data upload reply (MID = 0033)

0033 Rev Spare Data NUL
(ASCII 0x0)
20 bytes 71 + no of psets x 12 bytes
The job data reply is sent as a reply to the Job data request (MID = 0032).
Table 12
Job number 01 2 The job number (JobId) is specified by two ASCII characters. Range 0-99
Job name 02 25 Job name
Forced order 03 1 One ASCII character
0 – free order
1 – forced order
2 – free and forced
Maxtime for first 04 4 0-9999 seconds defined by four ASCII characters
tightening 0 = not used
Maxtime to complete job 05 5 0-99999 seconds defined by five ASCII characters
0 = not used
Job batch mode/ 06 1 The job batch mode is the way to count the bolt in a job; only the OK or both OK
batch count type and NOK.
One ASCII character
0 -> only the OK bolts are counted
1 -> both the OK and NOK bolts are counted
Lock at job done 07 1 One ASCII character
0 – No
1 – Yes
Use line control 08 1 One ASCII character
0 – No
1 – Yes
Repeat job 09 1 One ASCII character
0 – No
1 – Yes
Tool loosening 10 1 Tool loosening. One ASCII character.
0 – Enable
1 – Disable
2 – Enable only on NOK tightening
Reserved 11 1 Reserved for job repair. One ASCII character.
0–E
1–G
Number of psets 12 2 The number of psets in the job list, defined by two ASCII characters
Job list 13 N x 12 A list with up to 30 Psets where each Pset is defined by a number of parameters
separated by “:” and terminated by “;” (12 bytes) according to:
[PF-id]:[Type-ID]:[AutoValue]:[BatchSize];
PF-id = ChannelID, 0-99, two ASCII characters

Type ID = Pset ID or Multistage ID, three ASCII characters
Auto Value = 1 or 0, 1 for Auto Next Change, one ASCII character
BatchSize = 0-99, two ASCII characters
Ex: 15:011:0:22;
Possible answers No
Sent by The torque controller.
Page 33(103)
th
5.6.5 Job “info” subscribe (MID =0034)

(ASCII 0x0)
20 bytes 0 bytes
A subscription for the Job “info”. A message is sent to the station computer when a new Job is
selected (Job “info” MID = 0035)) and after each rundown performed during the job.

Or
“Job info subscription already exists”
Page 34(103)
th
5.6.6 Job “info” (MID = 0035)

(ASCII 0x0)
20 bytes 43 bytes
The job info subscriber will receive a job info telegram after a job has been selected and after
each rundown performed in the job. The job info consists of the number of the currently running
job, the job status, the job batch mode, the job batch size and the job batch counter.
Data ASCII data representing the parameter set data.

Table 13
Job number 01 2 The job number is specified by 2 ASCII characters Range 0-99
Job status 02 1 The job batch status is specified by one ASCII character.
0 job batch not completed / 1 job batch OK / 2 job batch NOK.
Job batch mode 03 1 The job batch mode is the way to count the bolt in a job only the OK or both OK
and NOK.
The job batch mode is specified by one ASCII character
0 -> only the OK bolts are counted
1 -> both the OK and NOK bolts are counted
Job batch size 04 4 This parameter gives the total number of tightening in the job. The job batch size
is four byte long specifying a range of 0000 to 9999.
Job batch counter 05 4 This parameter gives the current value of the job batch counter. The job is
completed when the job batch counter is equal to the Job batch size. The job
batch counter is four byte long specifying a range of 0000 to 9999.
Time stamp 06 19 Time stamp for the job info sent to the control station. The time stamp is 19 byte
long and is specified by 19 ASCII characters (YYYY-MM-DD:HH:MM:SS).
Possible answers Job info Acknowledge (MID = 0036)
Sent by The torque controller
Example:
00630035 0101020030040008050003062001-12-01:20:12:45
5.6.7 Job “info” acknowledge (MID = 0036)

(ASCII 0x0)
20 bytes 0 bytes
Acknowledge for a Job “info”.
Possible answers No
Page 35(103)
th
5.6.8 Job “info” unsubscribe (MID = 0037)

(ASCII 0x0)
20 bytes 0 bytes
Reset the subscription for the Job info telegram.

Or
“Job “info” subscription does not exist”
Page 36(103)
th
5.6.9 Select Job in POWER FOCUS (MID = 0038)

0022 0038 Rev Spare Job Number NUL
(ASCII 0x0)
20 bytes 2 bytes
Job number Job number represented by 2 Ascii digits (range 00 to 99).

or
(“Job can not be set”)
(“Invalid data”)
Sent by Integrator
5.6.10 Job restart (MID = 0039)

0022 0039 Rev Spare Job Number NUL
(ASCII 0x0)
20 bytes 2 bytes
Job number Job number represented by 2 Ascii digits (range 00 to 99).

or
(“Job not running”)
(“Invalid data”)
Sent by Integrator
Example:
00220039 01
Page 37(103)
th
5.7 Tool telegram
5.7.1 Tool data upload request (MID = 0040)

(ASCII 0x0)
20 bytes 0 bytes
A request for some data stored in the tool. The result of this command will be the transmission
of the tool data.
Possible answers Tool data upload reply (MID = 0041).
5.7.2 Tool data upload (MID = 0041)

(ASCII 0x0)
20 bytes
Upload of tool data from the torque controller.
Data data representing the parameter set data.

ASCII

Tool serial number 01 14 The Tool serial number is specified by 14 ASCII characters
Tool number of tightening 02 10 The Tool number of tightening is specified by 10 ASCII digits. Max 4294967295
Last calibration date 03 19 YYYY-MM-DD:HH:MM:SS
Controller Serial Number 04 10 The controller serial number is specified by 10 ASCII characters
Page 38(103)
th

Tool number of tightening 02 10 The Tool number of tightening is specified by 10 ASCII digits. Max 4294967295
Last calibration date 03 19 YYYY-MM-DD:HH:MM:SS
Controller Serial Number 04 10 The controller serial number is specified by 10 ASCII characters
Calibration value 05 6 The tool calibration value is multiplied by 100 and sent as an integer (2 decimals
truncated).
Last service date 06 19 YYYY-MM-DD:HH:MM:SS
Tightenings since service 07 10 The number of tightenings since last service is specified by 10 ASCII digits. Max
4294967295
Tool type 08 2 The tool type is specified by 2 ASCII digit:
01: S-tool, 02: DS-tool, 03: Ref. transducer, 04: ST-tool , 05: EP-tool,
06: ETX-tool, 07: SL-tool, 08: DL-tool, 09: Bensor(offline), 10: Bensor(online),
11: QST-tool
Motor size 09 2 The motor size is specified by 2 ASCII digits. (00-99)
Open end data 10 3 The open end data is specified by 3 ASCII digits (0 or 1). The first digit represents
the “use open end” (1 if true, 0 if false). The second digit indicates the tightening
direction 0: CW 1: CCW. The third digit indicates motor rotation 0: normal
1:inverted.
PF Software version 11 19 The software version is specified by 19 ASCII characters.
Example MID 0041 revision 1:

0081 0041 Rev Spare 01C341212 02548796 032001-05-07:13:24:5404670919 NUL
(ASCII 0x0)
20 bytes 61 bytes
Page 39(103)
th
5.7.3 Disable tool (MID = 0042)

(ASCII 0x0)
20 bytes 0 bytes
Disable tool
5.7.4 Enable tool (MID = 0043)

(ASCII 0x0)
20 bytes 0 bytes
Enable tool
5.7.5 Disconnect tool request (MID = 0044)

(ASCII 0x0)
20 bytes 0 bytes
This command is sent by the station computer in order to request the possibility to unmount the
tool on the torque controller. The command will be rejected if the tool is currently used.
When the command is accepted the worker can loose the tool and replace it (hot swap).

“ Tool currently in use”
Page 40(103)
th
5.7.6 Set calibration value request (MID = 0045)

(ASCII 0x0)
20 bytes 11 bytes
This command is sent by the station computer in order to request to set the calibration value of
the tool.
Data data representing the parameter set data.

ASCII
Table 16

calibration value Unit 01 1 The unit in which the calibration value is sent. The calibration value unit is one
byte long specifying a range of 0 to 9 and is specified by two ASCII digits
(‘0’….’9’).
1. Nm
2. Lbf.ft
3. Lbf.In
4. Kpm
Calibration value 02 6 The calibration value is multiplied by 100 and sent as an integer (2 decimals
truncated). The calibration value is six byte long and is specified by six ASCII
digits (‘0’….’9’, ‘.’).
Example MID 0045:

0031 0045 Rev Spare 01102003550 NUL
(ASCII 0x0)
20 bytes 11 bytes

“Calibration failed”
Page 41(103)
th
5.8 VIN telegram
5.8.1 Vehicle Id Number download request (MID = 0050) retired
Still supported but replaced by MID=0150

0045 0050 Rev Spare VIN NUL
(ASCII 0x0)
20 bytes 25 bytes
Used by the station computer to send a VIN number to the torque controller.
The VIN number is represented by max 25 ASCII characters. If the VIN number length is lower
than 25 characters, the VIN number field is filled with space SPC

or
“VIN input source not granted”
5.8.2 Vehicle Id Number upload subscribe (MID = 0051)

(ASCII 0x0)
20 bytes 0 bytes
This telegram is used by the station computer to set a subscription for the current identifiers of
the tightening result. The tightening result can be stamped with up to four identifiers:
- VIN number
- Identifier result part A
- Identifier result part B
- Identifier result part C
Those identifiers could have been received by the torque controller from several input sources
(serial, Ethernet, field bus…).
In the revision 1 of the MID only the VIN number is transmitted. In revision 2, all four possible
identifiers are transmitted.

Or
“VIN upload subscription already exists”
Page 42(103)
th
5.8.3 Vehicle Id Number upload (MID = 0052)

(ASCII 0x0)
20 bytes
Transmission of the current identifiers of the tightening by the torque controller to the
subscriber.
The tightening result can be stamped with up to four identifiers:
- VIN number (Identifier result part 1)

- Identifier result part 2
Those identifiers could have been received by the torque controller from several input sources
(serial, Ethernet, field bus…).
Table 17, MID 0052 revision 1

VIN number No 25 The VIN number is 25 byte long and is specified by 25 ASCII characters taken
between 0x20 and 0x7F Hex.

VIN number 01 25 The VIN number is 25 byte long and is specified by 25 ASCII characters taken
Identifier result part 2 02 25 The identifier result part 2 is 25 byte long and is specified by 25 ASCII characters
taken between 0x20 and 0x7F Hex.
Possible answers Vehicle Id Number upload acknowledge (MID = 0053)
5.8.4 Vehicle Id Number upload acknowledge (MID = 0053)

(ASCII 0x0)
20 bytes 0 bytes
Vehicle Id Number upload acknowledge.
Page 43(103)
th
Possible answers No
5.8.5 Vehicle Id Number upload unsubscribe (MID = 0054)

(ASCII 0x0)
20 bytes 0 bytes
Reset the subscription for the barcode (VIN) received by the torque controller.

Or
“VIN upload subscription does not exists”
Page 44(103)
th
5.9 Tightening result telegram
5.9.1 Last tightening result data subscribe (MID = 0060)

(ASCII 0x0)
20 bytes 0 bytes
Set the subscription for the rundowns result. The result of this command will be the
transmission of the rundown result after the tightening is performed (push function). The MID
revision in the header is used to subscribe to different revisions of MID = 0061.

Or
“Last tightening result subscription already exists”
“MID revision not supported”
5.9.2 Last tightening result data upload reply (MID = 0061)

(ASCII 0x0)
20 bytes
Upload last tightening result. Six revisions are available for this MID.
The six revisions are presented in the following tables :

Table 24, MID 0061 light (121<128 bytes) revision 999
The MID 61 revision 999 is 121 bytes (101 bytes of data + 20 bytes header).
Page 45(103)
th

Cell Id 01 4 The cell number (cluster number) is four byte long specifying a range of 0000 to 9999 and is
specified by four ASCII digits (‘0’….’9’).
Channel Id 02 2 The channel Id is two byte long specifying a range of 00 to 20 and is specified by two ASCII
digits (‘0’….’9’).
Torque controller 03 25 The torque controller name is 25 byte long and is specified by 25 ASCII characters taken
Name between 0x20 and 0x7F Hex.
VIN Number 04 25 The VIN number is 25 byte long and is specified by 25 ASCII characters taken between 0x20
and 0x7F Hex.
Job Number 05 2 This is the job number that is currently run (JobId), this information is sent with each tightening
result. The job number is two bytes long specifying a range of 00 to 99 and is specified by two
ASCII digits (‘0’….’9’).
Pset number 06 3 This is the pset number that is run (psetId), this information is sent with each tightening result.
The pset number is three byte long specifying a range of 000 to 999 and is specified by three
Batch Size 07 4 This parameter gives the total number of tightening in the batch. The batch size is four byte
long specifying a range of 0000 to 9999.
08 4 This is the batch counter, this information is sent with each tightening result. The batch counter
Batch counter number is four byte long specifying a range of 0000 to 9999 and is specified by four ASCII
digits (‘0’….’9’).
Tightening Status 09 1 The tightening status is one byte long and is specified by one ASCII digit (‘0’ or ‘1’). Zero
corresponds to tightening NOK, one corresponds to tightening OK.
Torque status 10 1 0. Low / 1. OK / 2 .High
Angle status 11 1 0. Low / 1. OK / 2 .High
Torque Min limit 12 6 The torque min limit is sent with each tightening result. The torque min limit is multiplied by 100
and sent as an integer (2 decimals truncated). The torque min limit is six byte long and is
specified by six ASCII digits (‘0’….’9’, ‘.’).
Torque Max limit 13 6 The torque max limit is sent with each tightening result. The torque max limit is multiplied by
100 and sent as an integer (2 decimals truncated). The torque max limit is six byte long and is
Torque final target 14 6 The torque final target is sent with each tightening result. The torque final target is multiplied by
100 and sent as an integer (2 decimals truncated). The torque final target is six byte long and is
Torque 15 6 The torque value is sent with each tightening result. The torque is multiplied by 100 and sent as
an integer (2 decimals truncated). The torque is six byte long and is specified by six ASCII
digits
(‘0’….’9’, ‘.’).
Angle Min 16 5 The angle min value in degrees is sent with each tightening result, each turn represents 360
degrees. The angle min value has a specified range between 0 and 99999. The angle min
value is five byte long and is specified by five ASCII digits (‘0’….’9’).
Angle Max 17 5 The angle max value in degrees is sent with each tightening result, each turn represents 360
degrees. The angle max value has a specified range between 0 and 99999. The angle max
Final Angle 18 5 The target angle value in degrees is sent with each tightening result, each turn represents 360
Target degrees. The target angle has a specified range between 0 and 99999. The target angle is five
byte long and is specified by five ASCII digits (‘0’….’9’).
Angle 19 5 The turning angle value in degrees is sent with each tightening result, each turn represents 360
degrees. The turning angle has a specified range between 0 and 99999. The turning angle is
five byte long and is specified by five ASCII digits (‘0’….’9’).
Time stamp 20 19 Time stamp for each tightening sent to the control station. The time stamp is 19 byte long and
is specified by 19 ASCII characters (YYYY-MM-DD:HH:MM:SS).
Date/time of last 21 19 Time stamp for the last change in the current pset settings. The time stamp is 19 byte long and
change in Pset is specified by 19 ASCII characters (YYYY-MM-DD:HH:MM:SS).
settings
Batch status 22 1 The batch status is specified by one ASCII character.
0 batch NOK (batch not completed) / 1 batch OK / 2 batch not used.
Tightening Id 23 10 The tightening Id is a unique Id for each tightening result. The tightening Id is incremented after
each rundown. 10 ASCII digits. Max 4294967295
Possible answers Last tightening result Acknowledge (MID =0062)
Page 46(103)
th

Cell Id 01 4 The cell number (cluster number) is four byte long specifying a range of 0000 to 9999 and is
Channel Id 02 2 The channel Id is two byte long specifying a range of 00 to 20 and is specified by two ASCII
digits (‘0’….’9’).
Torque controller 03 25 The torque controller name is 25 byte long and is specified by 25 ASCII characters taken
Name between 0x20 and 0x7F Hex.
and 0x7F Hex.
Strategy 07 2 The strategy currently run by the torque controller. The strategy is two bytes long specifying a
range of 00 to 99 and is specified by two ASCII digits (‘0’….’9’).
The corresponding strategies are :
1. Torque control
2. Torque control / angle monitoring
3. Torque control / angle control AND
4. Angle control / torque monitoring
5. DS control
6. DS control torque monitoring
7. Reverse angle
8. Reverse torque
9. Click wrench
10. Rotate spindle forward
11. Torque control angle control OR
12. Rotate spindle reverse
13. Home position
14. EP Monitoring
15. Reserved
99. No strategy
Strategy options 08 5 Bit 0 (value 1) Torque
Bit 1 (value 2) Angle
Bit 2 (value 4) Batch
Bit 3 (value 8) PVT Monitoring
Bit 4 (value 16) PVT Compensate
Bit 5 (value 32) Selftap
Bit 6 (value 64) Rundown
Bit 7 (value 128) CM
Bit 8 (value 256) DS control
Bit 9 (value 512) Click Wrench
Bit 10 (value 1024) RBW Monitoring
digits (‘0’….’9’).
Rundown angle 15 1 0. Low / 1. OK / 2 .High
status
Current Monitoring 16 1 0. Low / 1. OK / 2 .High
Status
Selftap status 17 1 0. Low / 1. OK / 2 .High
Prevail Torque 18 1 0. Low / 1. OK / 2 .High
monitoring status
compensate status
Page 47(103)
th

Tightening error status 20 10 Bit field, Tightening error bits shows what went wrong with the tightening.
Bit 1 Rundown angle max shut off
Bit 2 Rundown angle min shut off
Bit 3 Torque max shut off
Bit 4 Angle max shut off
Bit 5 Selftap torque max shut off
Bit 6 Selftap torque min shut off
Bit 7 Prevail torque max shut off
Bit 8 Prevail torque min shut off
Bit 9 Prevail torque compensate overflow
Bit 10 Current monitoring max shut off
Bit 11 Post view torque min torque shut off
Bit 12 Post view torque max torque shut off
Bit 13 Post view torque Angle too small
Bit 14 Trigger Lost
Bit 15 Torque Less Than Target
Bit 16 Tool Hot
Bit 17 Multistage Abort
Bit 18 Rehit
Bit 19 DS Measure Failed
Bit 20 Current Limit Reached
Bit 21 EndTime out Shutoff
Bit 22 Remove fastener limit exceeded
Bit 23 Disable drive
Bit 24-32 Reserved
Torque Min limit 21 6 The torque min limit is sent with each tightening result. The torque min limit is multiplied by 100
and sent as an integer (2 decimals truncated). The torque min limit is six byte long and is
Torque Max limit 22 6 The torque max limit is sent with each tightening result. The torque max limit is multiplied by
100 and sent as an integer (2 decimals truncated). The torque max limit is six byte long and is
Torque final target 23 6 The torque final target is sent with each tightening result. The torque final target is multiplied by
100 and sent as an integer (2 decimals truncated). The torque final target is six byte long and is
digits (‘0’….’9’, ‘.’).
Angle Min 25 5 The angle min value in degrees is sent with each tightening result, each turn represents 360
degrees. The angle min value has a specified range between 0 and 99999. The angle min
Angle Max 26 5 The angle max value in degrees is sent with each tightening result, each turn represents 360
degrees. The angle max value has a specified range between 0 and 99999. The angle max
Final Angle 27 5 The target angle value in degrees is sent with each tightening result, each turn represents 360
Target degrees. The target angle has a specified range between 0 and 99999. The target angle is five
byte long and is specified by five ASCII digits (‘0’….’9’).
Rundown angle Min 29 5 The rundown angle min value in degrees is sent with each tightening result, each turn
represents 360 degrees. The rundown angle min value has a specified range between 0 and
99999. The rundown angle min value is five byte long and is specified by five ASCII digits
(‘0’….’9’).
Rundown angle Max 30 5 The rundown angle max value in degrees is sent with each tightening result, each turn
represents 360 degrees. The angle max value has a specified range between 0 and 99999. The
rundown angle max value is five byte long and is specified by five ASCII digits (‘0’….’9’).
Rundown angle 31 5 The rundown angle value reached in degrees is sent with each tightening result, each turn
represents 360 degrees. The turning angle has a specified range between 0 and 99999. The
turning angle is five byte long and is specified by five ASCII digits (‘0’….’9’).
Current Monitoring Min 32 3 The current monitoring min limit in percent is sent with each tightening result. The current
monitoring min limit has a specified range between 0 and 999. The current monitoring Min limit
is three byte long and is specified by three ASCII digits (‘0’….’9’).
Current Monitoring Max 33 3 The current monitoring max limit in percent is sent with each tightening result. The current
monitoring max limit has a specified range between 0 and 999. The current monitoring Max limit
is three byte long and is specified by three ASCII digits (‘0’….’9’).
Current Monitoring 34 3 The current monitoring value in percent is sent with each tightening result. The current
Value monitoring value has a specified range between 0 and 999. The current monitoring value is
three byte long and is specified by three ASCII digits (‘0’….’9’).
Page 48(103)
th

Selftap min 35 6 The selftap min limit is sent with each tightening result. The selftap min limit is multiplied by 100
and sent as an integer (2 decimals truncated). The selftap min limit is six byte long and is
Selftap max 36 6 The selftap max limit is sent with each tightening result. The selftap max limit is multiplied by
100 and sent as an integer (2 decimals truncated). The selftap max limit is six byte long and is
Selftap torque 37 6 The selftap torque is sent with each tightening result. The selftap torque is multiplied by 100
and sent as an integer (2 decimals truncated). The torque is six byte long and is specified by six
ASCII digits (‘0’….’9’, ‘.’).
Prevail torque 38 6 The PVTmin limit is sent with each tightening result. The PVT min limit is multiplied by 100 and
monitoring min sent as an integer (2 decimals truncated). The PVT min limit is six byte long and is specified by
six ASCII digits (‘0’….’9’, ‘.’).
Prevail torque 39 6 The PVT max limit is sent with each tightening result. The PVT max limit is multiplied by 100
monitoring max and sent as an integer (2 decimals truncated). The PVT max limit is six byte long and is
Prevail torque 40 6 The prevail torque value is sent with each tightening result. The prevail torque is multiplied by
100 and sent as an integer (2 decimals truncated). The prevail torque is six byte long and is
Job sequence number 42 5 The job sequence number is unique for each job. All tightenings performed in the same job are
stamped with the same job sequence number. The job sequence number is specified by five
ASCII digits (‘0’….’9’, ‘.’). Range 0-65 535
Sync tightening Id 43 5 The sync tightening Id is a unique Id for each sync tightening result.
Each individual result of each spindle is stamped with this Id.
The tightening Id is incremented after each sync tightening. 5 ASCII digits. Max 65 535.
Date/time of last 46 19 Time stamp for the last change in the current pset settings. The time stamp is 19 byte long and
change in Pset settings is specified by 19 ASCII characters (YYYY-MM-DD:HH:MM:SS).

Same as revision 2 but extended with fields 47, 48 and 49 see below :

Parameter set Name 47 25 The parameter set name is 25 byte long and is specified by 25 ASCII characters taken between
0x20 and 0x7F Hex.
Torque values Unit 48 1 The unit in which the torque values are sent. The torque values unit is one byte long specifying
a range of 0 to 9 and is specified by two ASCII digits (‘0’….’9’).
1. Nm
2. Lbf.ft
3. Lbf.In
4. Kpm
5. Kgf.cm
6. ozf.in
7. % (only pulsor)
Result type 49 2 The result type is the type the telegram result define as below
1. tightening
2. loosening
3. Batch Increment
4. Batch decrement
5. Bypass pset result
6. Abort job result
7. sync tightening
8. Reference setup (only pulsor)
Page 49(103)
th


Identifier result part 2 50 25 The identifier result part 2 is 25 byte long and is specified by 25 ASCII characters taken
Special Note :
The identifier result parts will only be set if the multiple identifier option has been activated in
the torque controller.

Same as revision 4 but extended with fields 53 see below :

Customer tightening 53 4 The customer tightening error code is 4 byte long and is specified by 4 ASCII characters taken
error code between 0x20 and 0x7F Hex.
Example MID 61 revision 1:

0231 0061 Rev Spare 010001020103air bag 04 NUL
050006003070000080000090100111120008401300140014001200 (ASCII 0x0)
150007391600000170999918000001900000202001-06-
02:09:54:09212001-05-29:12:34:3322123345675
20 bytes 211 bytes
Page 50(103)
th
Table 24, MID 0061 light (121<128 bytes) revision 999

VIN Number __ 25 The VIN number is 25 byte long and is specified by 25 ASCII characters taken between 0x20
and 0x7F Hex.
Job Number __ 2 This is the job number that is currently run (JobId), this information is sent with each tightening
Pset number __ 3 This is the pset number that is run (psetId), this information is sent with each tightening result.
Batch Size __ 4 This parameter gives the total number of tightening in the batch. The batch size is four byte
__ 4 This is the batch counter, this information is sent with each tightening result. The batch counter
digits (‘0’….’9’).
Batch status __ 1 The batch status is specified by one ASCII character.
Tightening Status __ 1 The tightening status is one byte long and is specified by one ASCII digit (‘0’ or ‘1’). Zero
Torque status __ 1 0. Low / 1. OK / 2 .High
Angle status __ 1 0. Low / 1. OK / 2 .High
Torque __ 6 The torque value is sent with each tightening result. The torque is multiplied by 100 and sent as
digits (‘0’….’9’, ‘.’).
Angle __ 5 The turning angle value in degrees is sent with each tightening result, each turn represents 360
Time stamp __ 19 Time stamp for each tightening sent to the control station. The time stamp is 19 byte long and
Date/time of last __ 19 Time stamp for the last change in the current pset settings. The time stamp is 19 byte long and
change in Pset is specified by 19 ASCII characters (YYYY-MM-DD:HH:MM:SS).
settings
Tightening Id __ 10 The tightening Id is a unique Id for each tightening result. The tightening Id is incremented after
Special Note :
The MID 61 light revision 999 is intended to be used by station computers with limited receiving
capability (small receive buffer). In order to limit the size of the MID 61 as much as possible the
parameter Ids usually sent in the telegram have been removed.
Page 51(103)
th
5.9.3 Last tightening result data acknowledge (MID = 0062)

(ASCII 0x0)
20 bytes 0 bytes
Last tightening result data acknowledge.
Possible answers No
5.9.4 Last tightening result data unsubscribe (MID = 0063)

(ASCII 0x0)
20 bytes 0 bytes
Reset the last tightening result subscription for the rundowns result.

Or
“ Last tightening result subscription does not exist”
Page 52(103)
th
5.9.5 Old tightening result upload request (MID = 0064)

0030 0064 Rev Spare Tightening Id NUL
(ASCII 0x0)
20 bytes 10 bytes
This telegram is a request to upload a special rundown result from the torque controller. The
result wanted is specified by its unique Id (tightening Id). This telegram can be useful after
a failure of the network in order to retrieve the missing result during the communication
interruption (the station computer can see the missing results by always comparing the last
tightening ids of the two last received rundowns packets (parameter 23 in the result telegram).
Requesting tightening Id zero is the same as requesting the latest rundown performed.
Possible answers Old tightening result reply (MID = 0065)

Or
“Tightening Id requested not found”
“MID revision not supported”
Page 53(103)
th
5.9.6 Old tightening result reply (MID = 0065)

(ASCII 0x0)
20 bytes
Old tightening upload. Four revisions are available for this MID.
The four revisions are presented in the following tables :


and 0x7F Hex.
digits (‘0’….’9’).
Torque status 06 1 0. Low / 1. OK / 2. High
Angle status 07 1 0. Low / 1. OK / 2. High
digits
(‘0’….’9’, ‘.’).
SPC current batch not completed / 0 batch NOK / 1 batch OK / 2 batch not used.
Possible answers No
Page 54(103)
th

and 0x7F Hex.
Strategy 05 2 The strategy currently run by the torque controller. The strategy is two bytes long specifying a
range of 00 to 99 and is specified by two ASCII digits (‘0’….’9’).
The corresponding strategies are :
1. Torque control
2. Torque control / angle monitoring
3. Torque control / angle control AND
4. Angle control / torque monitoring
5. DS control
6. DS control torque monitoring
7. Reverse angle
8. Reverse torque
9. Click wrench
10. Rotate spindle forward
11. Torque control angle control OR
12. Rotate spindle reverse
13. Home position
14. EP monitoring (pulsor)
15. Reserved
99. No strategy
Strategy options 06 5 Bit 0 (value 1) Torque
Bit 1 (value 2) Angle
Bit 2 (value 4) Batch
Bit 3 (value 8) PVT Monitoring
Bit 4 (value 16) PVT Compensate
Bit 5 (value 32) Selftap
Bit 6 (value 64) Rundown
Bit 7 (value 128) CM
Bit 8 (value 256) DS control
Bit 9 (value 512) Click Wrench
Bit 10 (value 1024) RBW Monitoring
digits (‘0’….’9’).
SPC current batch not completed / 0 batch NOK / 1 batch OK / 2 batch not used.
Rundown angle 13 1 0. Low / 1. OK / 2 .High
status
Current Monitoring 14 1 0. Low / 1. OK / 2 .High
Status
Selftap status 15 1 0. Low / 1. OK / 2 .High
monitoring status
compensate status
Page 55(103)
th

Tightening error status 18 10 Bit field, Tightening error bits shows what went wrong with the tightening.
Bit 1 Rundown angle max shut off
Bit 2 Rundown angle min shut off
Bit 3 Torque max shut off
Bit 4 Angle max shut off
Bit 5 Selftap torque max shut off
Bit 6 Selftap torque min shut off
Bit 7 Prevail torque max shut off
Bit 8 Prevail torque min shut off
Bit 9 Prevail torque compensate overflow
Bit 10 Current monitoring max shut off
Bit 11 Post view torque min torque shut off
Bit 12 Post view torque max torque shut off
Bit 13 Post view torque Angle too small
Bit 14 Trigger Lost
Bit 15 Torque Less Than Target
Bit 16 Tool Hot
Bit 17 Multistage Abort
Bit 18 Rehit
Bit 19 DS Measure Failed
Bit 20 Current Limit Reached
Bit 21 EndTime out Shutoff
Bit 22 Remove fastener limit exceeded
Bit 23 Disable drive
Bit 24-32 Reserved
digits (‘0’….’9’, ‘.’).
Rundown angle 21 5 The rundown angle value reached in degrees is sent with each tightening result, each turn
represents 360 degrees. The turning angle has a specified range between 0 and 99999. The
turning angle is five byte long and is specified by five ASCII digits (‘0’….’9’).
Current Monitoring 22 3 The current monitoring value in percent is sent with each tightening result. The current
Value monitoring value has a specified range between 0 and 999. The current monitoring value is
three byte long and is specified by three ASCII digits (‘0’….’9’).
Selftap torque 23 6 The selftap torque is sent with each tightening result. The selftap torque is multiplied by 100
and sent as an integer (2 decimals truncated). The torque is six byte long and is specified by six
ASCII digits (‘0’….’9’, ‘.’).
Prevail torque 24 6 The selftap torque value is sent with each tightening result. The selftap torque is multiplied by
100 and sent as an integer (2 decimals truncated). The selftap torque is six byte long and is
Job sequence number 25 5 The job sequence number is unique for each job. All tightening performed in the same job are
stamped with the same job sequence number. The job sequence number is specified by five
ASCII digits (‘0’….’9’, ‘.’). Range 0-65 535
Page 56(103)
th
Same as revision 2 but extended with fields 29 and 30 see below :

Torque values Unit 29 1 The unit in which the torque values are sent. The torque values unit is one byte long specifying
a range of 0 to 9 and is specified by two ASCII digits (‘0’….’9’).
1. Nm
2. Lbf.ft
3. Lbf.In
4. Kpm
5. Kgf.cm
6. Ozf.In
7. % (only pulsor)
Result type 30 2 The result type is the type the telegram result define as below :
1. tightening
2. loosening
3. Batch Increment
4. Batch decrement
5. Bypass pset result
6. Abort job result
7. Sync tightening
8. Reference setup (only pulsor)


Special Note :
The identifier result parts will only be set if the multiple identifier option has been activated in
the torque controller.
Possible answers No
Example revision 1:

Length 0065 Rev Spare 01456789 02AIRBAG NUL
0300104002050060070080014670900046 (ASCII 0x0)
102001-04-22:14:54:34142112
20 bytes bytes
Page 57(103)
th
5.10 Alarm telegram
5.10.1 Alarm subscribe (MID = 0070)

(ASCII 0x0)
20 bytes 0 bytes
A subscription for the alarms that can pop up on the torque controller

Or
“Alarm subscription already exists”
5.10.2 Alarm Upload reply (MID = 0071)

(ASCII 0x0)
20 bytes 33 bytes
An alarm has popped up on the torque controller. The current alarm is uploaded by the torque
controller to the station computer.
Table 29

Error code 01 4 The error code is specified by 4 ASCII characters / The error code begins with E
and is followed by three digits. Example E851
Controller ready status 02 1 Controller ready status 1 OK 0 NOK
Tool ready status 03 1 Tool ready status 1 OK 0 NOK
Time 04 19 YYYY-MM-DD:HH:MM:SS
Possible answers No
Example:

0043 0071 Rev Spare 01E404021031042001-06- NUL
02:10:14:26 (ASCII 0x0)
20 bytes 23 bytes
Page 58(103)
th
5.10.3 Alarm upload acknowledge (MID = 0072)

(ASCII 0x0)
20 bytes 0 bytes
Acknowledgement for MID 71 “Alarm Upload Reply”.
Possible answers No
5.10.4 Alarm unsubscribe (MID = 0073)

(ASCII 0x0)
20 bytes 0 bytes
Reset the subscription for the torque controller alarms.

Or
“Alarm subscription does not exist”
5.10.5 Alarm acknowledged on torque controller (MID = 0074)

0020 0074 Rev Spare Error Code NUL
(ASCII 0x0)
20 bytes 4 bytes
This telegram is sent by the torque controller to inform the station computer that the current
alarm has been acknowledged.
Possible answers Alarm acknowledged on torque controller ack (MID = 0075)

Sent by Torque controller.
Example:

0020 0074 Rev Spare E406 NUL
(ASCII 0x0)
20 bytes 4 bytes
Page 59(103)
th
5.10.6 Alarm acknowledged on torque controller ack (MID = 0075)

(ASCII 0x0)
20 bytes 0 bytes
Acknowledgment for MID 74 “Alarm acknowledged on torque controller”.
Possible answers No
5.10.7 Alarm status (MID = 0076)

(ASCII 0x0)
20 bytes 36 bytes
The alarm status is sent after an accepted subscription for the torque controller alarms.
The aim of the alarm status is to eventually inform the station computer that an alarm is
currently active on the controller at connection.
Table 30

Alarm Status 01 1 0 if no alarm is active / 1 if an alarm is currently active
Error code 02 4 The error code is specified by 4 ASCII characters. The error code begins with E
and is followed by three digits.
Controller ready status 03 1 Controller ready status 1 OK 0 NOK
Tool ready status 04 1 Tool ready status 1 OK 0 NOK
Possible answers Alarm status acknowledge (MID = 0077)
Example:

0056 0076 Rev Spare 01102E404031041052001-06- NUL
02:10:14:26 (ASCII 0x0)
20 bytes 23 bytes
Page 60(103)
th
5.10.8 Alarm status acknowledge (MID = 0077)

(ASCII 0x0)
20 bytes 0 bytes
Acknowledgment for MID 76 “Alarm status”.
Possible answers No
Sent by the station computer.
5.10.9 Acknowledge alarm remotely on torque controller (MID = 0078)

(ASCII 0x0)
20 bytes 0 bytes
The station computer can remotely acknowledge the current alarm on the torque controller by
sending MID 78. If no alarm is currently active when the torque controller receives the
command, the command will be rejected with a “Command Error, No alarm present”.

Or
“No alarm present”
“Invalid data”
Page 61(103)
th
5.11 Time telegram
5.11.1 Read time upload request (MID = 0080)

(ASCII 0x0)
20 bytes 0 bytes
Read time request.
Possible answers Time upload reply (MID = 0081)
5.11.2 Time upload reply (MID = 0081)

0039 0081 Rev Spare YYYY-MM- NUL
DD:HH:MM:SS (ASCII 0x0)
20 bytes 19 bytes
Time upload reply from the torque controller.
Possible answers No
5.11.3 Set Time in Torque Controller (MID = 0082)

0039 0082 Rev Spare YYYY-MM- NUL
DD:HH:MM:SS (ASCII 0x0)
20 bytes 19 bytes
Set the time in the torque controller.
Page 62(103)
th
5.12 Multi spindle status telegram
5.12.1 Multi spindle status (MID = 0090)

(ASCII 0x0)
20 bytes 0 bytes
A subscription for the multi spindle status (synch application). The subscription can only be
addressed to a sync Master.

Or
“Controller is not a sync Master”
“Multi spindle status subscription already exists”
5.12.2 Multi spindle status upload (MID = 0091)

(ASCII 0x0)
20 bytes 37 + 5 × number of spindles Bytes
The multi spindle status is sent from the “sync master” to the station computer after each sync
tightening. The multiple status contains the common status of the multiple as well as the
individual status of each spindle (in the sync list order).
Table 31

Number of spindles 01 2 Number of spindles running in the multiple, a maximum of 10 spindles can be
synchronized . The number of spindles is two bytes long and specified by 2 ASCII
digits range 2-10.
The tightening Id is incremented after each sync tightening. 5 ASCII digits.
Max 65 535.
Sync overall status 04 1 The common status of all the spindles OK if the individual status of each spindle is
OK, NOK if at least one spindle status is NOK. The sync overall status is specified
by one ASCII digit 1 = OK, 0 = NOK.
Spindle status 05 5 Bytes 1-2 The first two bytes specify the spindle number range 01-10 (same
× order as in the sync list)
Number Bytes 3-4 The next two bytes (three and four) are the channel Id of the spindle
of range 01 to 20
spindles
Byte 5 The fifth byte is the individual overall status of the rundown of each
spindle 0 = NOK / 1 = OK
Possible answers Multi spindle status acknowledge (MID = 0092)
Page 63(103)
th
Example:
Multiple status for two spindles. Common status OK, spindle 1 OK, spindle 2 OK.

0067 0091 Rev Spare 01020200012032001-06- NUL
02:10:14:26041050120102041 (ASCII 0x0)
20 bytes 47 bytes
5.12.3 Multi spindle status upload acknowledge (MID = 0092)

(ASCII 0x0)
20 bytes 0 bytes
Multi spindle status acknowledge.
Possible answers No
5.12.4 Multi spindle status unsubscribe (MID = 0093)

(ASCII 0x0)
20 bytes 0 bytes
Reset the subscription for the multi spindle status.

Or
“Multi spindle status subscription does not exist”
Page 64(103)
th
5.13 Multi spindle result telegram
5.13.1 Multi spindle result subscribe (MID = 0100)

(ASCII 0x0)
20 bytes 0 bytes
A subscription for the multi spindle status (synch application). The subscription can only be
addressed to a sync Master.

Or
“Controller is not a sync Master”
“Multi spindle result subscription already exists”
5.13.2 Multi spindle result upload (MID = 0101)

(ASCII 0x0)
20 bytes 154 + 18 × number of spindles bytes
The multi spindle result is sent from the “sync master” to the station computer after each sync
tightening. The multiple spindle result contains the common status of the multiple as well as the
tightening result of each spindle (torque and angle) of each spindle (in the sync list order).
Page 65(103)
th
Table 32

Number of spindles 01 2 Number of spindles running in the multiple, a maximum of 10 spindles can be
synchronized . The number of spindles is two bytes long and specified by 2 ASCII digits
range 2-10.
VIN Number 02 25 The VIN number is 25 byte long and is specified by 25 ASCII characters taken between
0x20 and 0x7F Hex.
Job Number 03 2 This is the job number that is currently run (JobId). The job number is two bytes long
specifying a range of 00 to 99 and is specified by two ASCII digits (‘0’….’9’).
Pset number 04 3 This is the pset number that is run (psetId). The pset number is three byte long specifying
a range of 000 to 999 and is specified by three ASCII digits (‘0’….’9’).
Batch Size 05 4 This parameter gives the total number of tightening in the batch. The batch size is four
byte long specifying a range of 0000 to 9999.
Batch counter 06 4 The batch counter number is four byte long specifying a range of 0000 to 9999 and is

Torque Min limit 08 6 The torque min limit is multiplied by 100 and sent as an integer (2 decimals truncated).
The torque min limit is six byte long and is specified by six ASCII digits (‘0’….’9’, ‘.’).
Torque Max limit 09 6 The torque max limit is multiplied by 100 and sent as an integer (2 decimals truncated).
The torque max limit is six byte long and is specified by six ASCII digits (‘0’….’9’, ‘.’).
Torque final target 10 6 The torque final target is multiplied by 100 and sent as an integer (2 decimals truncated).
The torque final target is six byte long and is specified by six ASCII digits (‘0’….’9’, ‘.’).
Angle Min 11 5 The angle min value in degrees, each turn represents 360 degrees. The angle min value
has a specified range between 0 and 99999. The angle min value is five byte long and is
Angle Max 12 5 The angle max value in degrees each turn represents 360 degrees. The angle max value
has a specified range between 0 and 99999. The angle max value is five byte long and is
Final Angle 13 5 The target angle value in degrees each turn represents 360 degrees. The target angle
Target has a specified range between 0 and 99999. The target angle is five byte long and is
Date/time of last change 14 19 Time stamp for for the last change in the current pset settings. The time stamp is 19 byte
in Pset settings long and is specified by 19 ASCII characters (YYYY-MM-DD:HH:MM:SS).
Sync overall status 17 1 The common status of all the spindles OK if the individual status of each spindle is OK,
NOK if at least one spindle status is NOK. The sync overall status is specified by one
ASCII digit 1 = OK, 0 = NOK.
Spindle status 18 18 Bytes 1-2 The first two bytes specify the spindle number range 01-10 (same order as
× in the sync list)
Number Bytes 3-4 channel Id of the spindle range 01 to 20
of
spindles Byte 5 Individual overall status of the rundown of each spindle
0= NOK / 1=OK
Byte 6 Individual torque status of each spindle
0. Low / 1. OK / 2 .High
Bytes 7-12 The torque result of each spindle. The torque is multiplied by 100 and sent
as an integer (2 decimals truncated). The torque is six byte long and is
Byte 13 Individual angle status of each spindle
0. Low / 1. OK / 2 .High
Byte 14-18 The turning angle value in degrees is sent for each spindle, each turn
represents 360 degrees. The turning angle has a specified range between
0 and 99999. The turning angle is five byte long and is specified by five
Possible answers Multi spindle result acknowledge (MID = 0102)
Page 66(103)
th
5.13.3 Multi spindle result upload acknowledge (MID = 0102)

(ASCII 0x0)
20 bytes 0 bytes
Multi spindle result acknowledge.
Possible answers No
5.13.4 Multi spindle result unsubscribe (MID = 0103)

(ASCII 0x0)
20 bytes 0 bytes
Reset the subscription for the multi spindle status.

Or
“Multi spindle result subscription does not exist”
Page 67(103)
th
5.14 User interface telegram
5.14.1 Display user text on compact (MID = 110)

0024 0110 Rev Spare User text max 4 NUL
characters (ASCII 0x0)
20 bytes 4 bytes
By sending this telegram the integrator can display a text on the compact display. The text must
be maximum 4 bytes long (if the text is less than 4 characters or digits long pad with space
SPC 0x20).
The character that can be displayed are limited due to hardware of the compact display.
Each character must fit in seven segments :
1 7 3
6 4
This means for example that it is not possible to display a M on the compact display.
The text will be displayed until next tightening, new Pset or Job selection, or event code.

Or
“User text could not be displayed”
5.14.2 Display user text on graph (MID = 111)

(ASCII 0x0)
20 bytes 117 bytes
By sending this telegram the integrator can display a text on the graphic display. The user can
furthermore set the time for the text to be displayed and if the text should be acknowledged by
the operator or not.
The text is divided into four lines with 25 ASCII characters each.
The first line is the text header and is in upper character.
If a line is shorter than 25 characters it must be padded with blanks (SPC 0x20) on the right.
Page 68(103)
th
Table 33

Text Duration 01 4 Time for the text to be displayed in seconds. Range 0-9999
Removal condition 02 1 0. OK to continue or wait
1. OK to continue (the text must be acknowledged parameter 1 text duration
ignored)
Line 1 (text header) 03 25 25 ASCII characters taken between 0x20 and 0x7F Hex.
Line 2 04 25 25 ASCII characters taken between 0x20 and 0x7F Hex.

Or
“User text could not be displayed”
5.14.3 Flash green light on tool (MID = 113)

(ASCII 0x0)
20 bytes 0 bytes
By sending this telegram the integrator can make the green light on the tool flash. The light on
the tool will flash until the operator push the tool trigger.
Page 69(103)
th
5.15 Job telegram advanced
5.15.1 Job line control info subscribe (MID = 0120)

(ASCII 0x0)
20 bytes 0 bytes
A subscription for the for the job line control information. A telegram is sent to the integrator
when the Job line control is started, for alert level 1 (80 %), for alert level 2 or when the job is
finished before the alert level 2 (Job line control done).

Or
“Job line control info subscription already exists”
5.15.2 Job line control started (MID = 0121)

(ASCII 0x0)
20 bytes 0 bytes
This telegram tells the integrator that Job Line control start has been set in the POWER
FOCUS.
Possible answers Job line control info acknowledged (MID = 0125)
Sent by Torque controller
5.15.3 Job line control alert 1 (MID = 0122)

(ASCII 0x0)
20 bytes 0 bytes
This telegram tells the integrator that the car has reached 80% of the station and that the Job
line control alert 1 is set in the POWER FOCUS.
Page 70(103)
th
5.15.4 Job line control alert 2 (MID = 0123)

(ASCII 0x0)
20 bytes 0 bytes
This telegram tells the integrator that the Job line control alert 2 is set in the POWER FOCUS.
5.15.5 Job line control done (MID = 0124)

(ASCII 0x0)
20 bytes 0 bytes
This telegram tells the integrator that the job has been completed before the alert level 2 was
reached.
5.15.6 Job line control info acknowledge (MID = 0125)

(ASCII 0x0)
20 bytes 0 bytes
Acknowledge for Job line control info telegrams MID 0121, 0122, 0123, 0124.
Possible answers No
Page 71(103)
th
5.15.7 Job line control info unsubscribe (MID = 0126)

(ASCII 0x0)
20 bytes 0 bytes
Unsubscribe for the Job line control info telegram.

Or
“ Job line control info subscription does not exist”
Page 72(103)
th
5.15.8 Abort Job (MID = 0127)

(ASCII 0x0)
20 bytes 0 bytes
Abort the current running job if there is one.
5.15.9 Job batch increment (MID = 0128)

(ASCII 0x0)
20 bytes 0 bytes
Increment the job batch if there is a current running job.
5.15.10 Job batch decrement (MID = 0129)

(ASCII 0x0)
20 bytes 0 bytes
Decrement the job batch if there is a current running job.
Page 73(103)
th
5.15.11 Job off (MID = 130)

0021 0130 Rev Spare Job off status NUL
(ASCII 0x0)
20 bytes 1 bytes
Set the torque controller computer in job off mode or reset the job off mode.
Job Off status Job off status is one byte long and is specified by one ASCII digit
0 = set job off, 1 = reset job off
Page 74(103)
th
5.15.12 Execute dynamic job request (MID = 140)

0140 Spare NUL
(ASCII 0x0)
20 bytes 71 + no of program x 15 bytes
The station computer requests a dynamical job to be executed i.e. the job sent from the station
computer is immediately executed (if possible) by the torque controller but not saved in the
memory. A dynamical job lifetime is the time for the job to be executed. If the torque controller
is powered off before the completion of the job, the dynamical job is lost.
Do note the limitation when sending this message on a serial connection due to the size of the
read buffer (256 bytes) in the torque controller. In such case the number of psets in the job list
is limited.
Possible answers Possible answers Command accepted (MID = 0005)

Or
“Not possible to execute dynamic job”
A more detailed description of the error i.e. faulty job select source or job
in off mode will be received, if an alarm subscription has been made (MID
0070).
Page 75(103)
th
Table 34

Job number 01 4 The job number (JobId) is specified by four ASCII characters. Range 0-9999
Job name 02 25 Job name
Number of psets 03 2 The number of psets in the job list, defined by two ASCII characters
Job list 04 N x 15 A list with up to 99 Psets where each Pset is defined by a number of parameters
separated by “:” and terminated by “;” ( 15 bytes) according to:
[Channel-ID]:[Program-ID]:[Auto Select]:[Batch Size]:[Max Coherent NOK];
Channel-ID = ChannelID, 0-99, two ASCII characters
Program-ID = Pset ID or Multistage ID, three ASCII characters
Auto Select = 1 or 0, 1 for Auto Next Change, one ASCII character
Batch Size = 0-99, two ASCII characters
Max Coherent NOK = 0-99, two ASCII characters
Ex: 15:045:0:22:2;
Forced order 05 1 Sets the job to forced or free order. One ASCII character
0 – free order
1 – forced order
2 – free and forced
Lock at job done 06 1 One ASCII character
0 – No
1 – Yes
tool loosening 07 1 tool loosening. One ASCII character.
0 – Enable
1 – Disable
2 – Enable only on NOK tightening
Repeat job 08 1 One ASCII character
0 – No
1 – Yes
Job batch mode/ 09 1 The job batch mode is the way to count the bolt in a job; only the OK or both OK
batch count type and NOK.
One ASCII character
0 – only the OK bolts are counted
1 – both the OK and NOK bolts are counted
Batch status at 10 1 Batch status after performing an increment or a bypass Pset
increment / bypass One ASCII character
0 – OK
1 – NOK
Decrement Batch at OK 11 1 One ASCII character
loosening 0 – No
1 – Yes
Maxtime for first 12 4 Maxtime to complete the first tightening of the Job
tightening 0-9999 seconds defined by four ASCII characters
0 – not used
Maxtime to complete job 13 5 Maxtime to complete the entire Job
0-99999 seconds defined by five ASCII characters
0 – not used
Display result at 14 4 Set the time the tightening result is kept on the display after selecting next Pset
autoselect 0-9999 seconds defined by four ASCII characters
0 – not used
Use line control 15 1 One ASCII character
0 – No
1 – Yes
Identifier result part 1 16 1 One ASCII character
0 – job VIN number, save the identifier that triggered in identifier result part 1
1 – other
Result of non tightenings 17 1 One ASCII character, save result after increment, bypass ...
0 – No
1 – Yes
Reset all identifiers at Job 18 1 One ASCII character
done 0 – No
1 – Yes
Reserved 19 1 Reserved for job repair. One ASCII character.
0–E
1–G
Page 76(103)
th
5.8 Multiple Identifiers telegram
5.8.1 Identifier download request (MID = 0150)

0150 Rev Spare Identifier NUL
(ASCII 0x0)
20 bytes Max 100 bytes
Used by the station computer to send an identifier to the torque controller. The identifier could
be or can include a VIN number or a result part number.
The identifier number is represented by max 100 ASCII characters. The length of the telegram is
the sum of the header length and the identifier length.

or
“Identifier input source not granted”
5.8.2 Multiple Identifiers work order upload subscribe (MID = 0151)

(ASCII 0x0)
20 bytes 0 bytes
This telegram is used by the station computer to set a subscription for the identifiers received
and accepted by the torque controller during the identifier work order. Those identifiers could
have been received by the torque controller from several input sources (serial, Ethernet, field
bus…).

Or
“Multiple identifiers work order upload subscription already exists”
Page 77(103)
th
5.8.3 Multiple Identifiers work order upload (MID = 0152)

(ASCII 0x0)
20 bytes
Transmission of the identifier work order status by the torque controller to the subscriber.
The identifier work order contains the status of the max four identifiers parts that could be
present in a work order.
Table 35

First Identifier in work 01 30 Byte 1 Identifier type number, i.e. type 1, 2, 3, or 4
order Byte 2-3 Included in work order, 0 = No, 1 = Yes
Byte 4-5 Status in work order, 0 = Not accepted

1 = Accepted
2 = Bypassed
3 = Reset
Byte 6-30 The identifier is 25 byte long and is specified by 25 ASCII characters
Second Identifier in work 02 30 Byte 1 Identifier type number, i.e. type 1, 2, 3, or 4

1 = Accepted
2 = Bypassed
3 = Reset
Third Identifier in work 03 30 Byte 1 Identifier type number, i.e. type 1, 2, 3, or 4

1 = Accepted
2 = Bypassed
3 = Reset
Fourth Identifier in work 04 30 Byte 1 Identifier type number, i.e. type 1, 2, 3, or 4

1 = Accepted
2 = Bypassed
3 = Reset
Possible answers Multiple identifiers work order upload acknowledge (MID = 0153)
Page 78(103)
th
5.8.4 Multiple Identifiers work order upload acknowledge (MID = 0153)

(ASCII 0x0)
20 bytes 0 bytes
Multiple identifiers work order upload acknowledge.
Possible answers No
5.8.5 Multiple Identifiers work order upload unsubscribe (MID = 0154)

(ASCII 0x0)
20 bytes 0 bytes
Reset the subscription for the multiple identifiers work order.

Or
“Multiple identifiers work order upload subscription does not exists”
Page 79(103)
th
5.8.6 Bypass Identifier (MID = 0155)

(ASCII 0x0)
20 bytes 0 bytes
This telegram is used by the station computer to bypass the next identifier expected in the work
order.
5.8.7 Reset latest Identifier (MID = 0156)

(ASCII 0x0)
20 bytes 0 bytes
This telegram is used by the station computer to reset the latest identifier or bypassed identifier
in the work order.
5.8.8 Reset all Identifiers (MID = 0157)

(ASCII 0x0)
20 bytes 0 bytes
This telegram is used by the station computer to reset all the identifiers in the current work
order.
Page 80(103)
th
5.16 I/O interface
5.16.1 Set “external controlled” relays (MID = 200)

(ASCII 0x0)
20 bytes 10 bytes
By using this telegram the station computer can control 10 relays (external control relays). The
station can set, reset the relays and make them flashing.
Table 36
Parameter Bytes Comment
Status relay 1 1 Set the status for relay 1. The relay status is one byte long and specified by 1
ASCII digits range 0-3.
0 = Off, 1 = On (fast), 2 = Flashing, 3 = Do not care (keep the same status)
Example:

0030 0200 Rev Spare 0102301230 NUL
(ASCII 0x0)
20 bytes 10 bytes
Reset relay 1, set relay 2, reset relay 3, flash relay 4, keep relay 5 as it is ….
Page 81(103)
th
5.16.2 Status “external monitored inputs” subscribe (MID = 0210)

(ASCII 0x0)
20 bytes 0 bytes
By using this telegram the station computer can set a subscription to monitor the status for the
8 “external monitored digital inputs”. After the subscription the station will receive a telegram
every time the status of at least one of the 8 inputs has changed.

Or
“Status “external monitored inputs” subscription already exists”
5.16.3 Status “external monitored inputs” upload (MID = 211)

(ASCII 0x0)
20 bytes 8 bytes
Status for the 8 “external monitored digital inputs”. This telegram is sent to the subscriber every
time the status of at least one of the 8 inputs has changed.
Possible answers Status “external monitored inputs” upload acknowledge (MID = 212)
Sent by POWER FOCUS.
Table 37
Parameter Bytes Comment
Status DIG/IN 1 1 The DIG/IN status is one byte long and specified by 1 ASCII digits range 0-1.
0 = Off, 1 = On
0 = Off, 1 = On
0 = Off, 1 = On
0 = Off, 1 = On
0 = Off, 1 = On
0 = Off, 1 = On
0 = Off, 1 = On
0 = Off, 1 = On
Page 82(103)
th
Example:

0028 0211 Rev Spare 00100111 NUL
(ASCII 0x0)
20 bytes 8 bytes
5.16.4 Status “external monitored inputs” upload acknowledge (MID = 212)

(ASCII 0x0)
20 bytes 0 bytes
Acknowledgement for the telegram status “external monitored inputs” upload.
Possible answers No
5.16.5 Status “external monitored inputs” unsubscribe (MID = 213)

(ASCII 0x0)
20 bytes 0 bytes
Unsubscribe for the “Status “external monitored inputs”.

Or
“Status “external monitored inputs” subscription does not exist”
Page 83(103)
th
5.16.6 IO device status request (MID = 0214)

(ASCII 0x0)
20 bytes 2 bytes
Request for the status of the relays and digital inputs at a device, e.g. an I/O expander. The
device is specified by a device number with two ASCII characters (00-15). Device number 0
denotes the internal device and 1 to 15 the I/O expanders.
Possible answers IO device status (MID = 0215)

Or
“Faulty IO device number”
“IO device not connected”
Page 84(103)
th
5.16.7 IO device status (MID = 0215)

(ASCII 0x0)
20 bytes Revisions dependant
This message is sent as an answer to the IO device status request (MID = 00214).
MID 0215 revision 1, should only be used to get the status of IO devices with max 8
relays/digital inputs.
For external I/O devices each list contain up to 8 relays/digital inputs. For the internal device the
lists contain up to 4 relays/digital inputs and the remaining 4 will be empty.
MID 0215 revision 2, can be used to get the status of all types of IO devices with up to 48
relays/digital inputs.
Possible answers No

IO device number 01 2 The IO device number specified with two ASCII characters.
Relay list 02 32 A list of 8 relays for the current device number each with a relay number specified
by three ASCII characters (000-999) followed by the relay status specified by one
ASCII character; 0 – reset, 1 – set.
Digital Input list 03 32 A list of 8 digital inputs for the current device number each with a digital input
number specified by three ASCII characters (000-999) followed by its status
specified by one ASCII character; 0 – low, 1 – high.

IO device number 01 2 The IO device number specified with two ASCII characters.
Number of relays 02 2 Number of relays present on the IO device
Relay list 03 4× A list of relays for the current device number. Each relay number is specified by
Number three ASCII characters (000-999) followed by the relay status specified by one
of relays ASCII character; 0 – reset, 1 – set.
Number of digital inputs 04 2 Number of digital inputs present on the IO device
Digital Input list 05 4× A list of digital inputs for the current device number. Each digital input number is
Number specified by three ASCII characters (000-999) followed by its status specified by
of digital one ASCII character; 0 – low, 1 – high.
inputs
Example:
For I/O device 8, relays 11, 22, 33, 44 are reset and 55, 66, 77, 88 are set and digital inputs 11,
22, 33, 44 are high and 55, 66, 77, 88 are low.

0092 0215 Rev Spare 01080201100220033004400551066107710881 NUL
0301110221033104410550066007700880 (ASCII 0x0)
20 bytes 72 bytes
Page 85(103)
th
See Table 40,Table 41 for how to interpret the relay numbers and digital input numbers i.e.
what function they map to, e.g. relay number 2 denotes OK.
Table 40
Relay number Relay function Tracking event
00 Off
01 OK
02 NOK
03 Low
04 High
05 Low Torque
06 High Torque
07 Low angle
08 High angle
09 Cycle complete
10 Alarm Yes
11 Batch NxOK Yes
12 Job OK Yes
13 Job NOK Yes
14 Job running Yes
15 Reserved Yes
16 Reserved Yes
17 Not used
18 POWER FOCUS ready Yes
19 Tool ready Yes
20 Tool start switch Yes
21 Dir. switch = CW Yes
22 Dir. switch = CCW Yes
23 Tightening direction CCW Yes
24 Tool tightening Yes
25 Tool loosening Yes
26 Tool running Yes
27 Tool running CW Yes
28 Tool running CCW Yes
29 Statistic alarm Yes
30 Tool locked Yes
31 Received identifier
32 Running pset bit 0 Yes
36 Running job bit 0 Yes
40 Not used
41 Not used
42 Not used
43 Not used
44 Line control OK
45 Line control alert 1
47 Service indicator Yes
48 Fieldbus relay 1 Yes
52 Tool red light Yes
53 Tool green light Yes
54 Tool yellow light Yes
55 Reserved Yes
56 Reserved Yes
57 Reserved Yes
58 Reserved Yes
Page 86(103)
th

67 Sync OK
68 Sync NOK
69 Sync spindle 1 OK
70 Sync spindle 1 NOK
89 Reserved Yes
90 Reserved
91 Line Control Start Yes
92 Job Aborted Yes
93 External controlled 1
103 ToolsNet connection lost Yes
104 OpenProtocol connection lost Yes
105 FieldBus Offline Yes
106 Home position Yes
107 Batch NOK Yes
108 Selected Channel in Job Yes
109 Safe to disconnect tool Yes
112 Calibration Alarm Yes
113 Cycle start
114 Low current
115 High current
116 Low PVT monitoring
117 High PVT monitoring
118 Low PVT selftap
119 High PVT selftap
120 Low rundown angle
121 High rundown angle
122 Identifier identified
123 Identifier type 1 received
Page 87(103)
th

127 Reserved
128 Reserved
129 Ring button ack.
130 DigIn controlled 1 Yes
134 Fieldbus carried signals disabled Yes
135 Illuminator Yes
136 New Pset selected
137 New Job selected
138 Job OFF relay Yes
139 Logic relay 1 Yes
143 Max coherent NOK reached Yes
144 Batch done Yes
145 Start trigger active Yes
146 Reserved Yes
150-250 Reserved
251 Completed Batch bit 0 Yes
258 Reserved Yes
259 Remaining Batch bit 0 Yes
266 Reserved Yes
267 Reserved Yes
268 Reserved Yes
269 Reserved Yes
270 Reserved Yes
271 Reserved
272 Reserved Yes
273 Reserved Yes
274 Reserved Yes
275 Open protocol commands disabled Yes
276 Cycle abort
277 Effective loosening
284 Lock at batch done Yes
285 Reserved
286 Reserved
287 Battery low Yes
288 Battery empty Yes
289 Tool connected Yes
290 No tool connected Yes
291 Reserved Yes
292 Reserved Yes
Page 88(103)
th

293 Function button Yes
294 Rehit
295 Tightening disabled Yes
296 Loosening disabled Yes
297 Positioning disabled Yes
298 Motortuning disabled Yes
299 Open End tuning disabled Yes
300 Tracking disabled Yes
301 Reserved Yes
302 Automatic mode Yes
303 PLUS Emergency mode Yes
304 Wear indicator Yes
Page 89(103)
th
Table 41
DigIN number DigIN function
00 Off
01 Reset batch
02 Unlock tool
03 Tool disable n.o.
04 Tool disable n.c.
05 Tool tightening disable
06 Tool loosening disable
07 Remote start puls
08 Remote start cont.
09 Tool start loosening
10 Batch increment
11 Bypass pset
12 Abort job
13 Job off
14 Pset toggle
15 Reset relays
16 Pset select bit 0
20 Job select bit 0
21 Job select bit 1
22 Job select bit 2
23 Job select bit 3
24 Reserved
25 Reserved
26 Reserved
27 Reserved
28 Line control start
31 Ack error message
32 Fieldbus digin 1
33 Fieldbus digin 2
34 Fieldbus digin 3
35 Fieldbus digin 4
36 Flash tool green light
37 Reserved
38 Reserved
39 Reserved
40 Reserved
41 Reserved
42 Reserved
43 Reserved
44 Reserved
49 Job select bit 4
50 Job select bit 5
51 Job select bit 6
52 Job select bit 7
53 Batch decrement
54 Job restart
55 End of cycle
56 Reserved
57 Reserved
58 Reserved
59 Reserved
60 Reserved
61 Reserved
62 Click wrench 1
63 Click wrench 2
64 Click wrench 3
65 Click wrench 4
66 ID Card
Page 90(103)
th
DigIN number DigIN function

67 Reserved
68 External monitored 1
76 Select next Pset
77 Select previous Pset
78 Reserved
79 Timer enable tool
80 Master unlock tool
81 ST Scan request
82 Disconnect tool
83 Job select bit 8
85 Request ST scan
86 Reset Nok counter
90 Set home position
91 DigOut monitored 1
95 Disable ST Scanner
96 Disable fieldbus carried signals
97 Toggle CW/CCW
98 Toggle CW/CCW for next run
99 Set CCW
100 Reserved
101 Reserved
102 Reserved
103 Reserved
104 Open protocol commands disable
105 Logic digIn 1
106 Logic digIn 2
107 Logic digIn 3
108 Logic digIn 4
109 Logic digIn 5
110 Logic digIn 6
111 Logic digIn 7
112 Logic digIn 8
113 Logic digIn 9
114 Logic digIn 10
115 Reserved
116 Reserved
117 Reserved
118 Reserved
119 Reserved
120 Forced CCW once
121 Forced CCW toggle
122 Forced CW once
123 Forced CW toggle
124 Reserved
125 Reserved
126 Reserved
127 Reserved
Page 91(103)
th
5.16.8 Relay function subscribe (MID = 0216)

0023 0216 Rev No Spare Relay no NUL
Ack (ASCII 0x0)
20 bytes 3 bytes
Subscribe for one single relay function. The data field consists of three ASCII digits, the relay
number, which corresponds to the specific relay function. The relay numbers can be found in
Table 40 above. At a subscription of a tracking event (Table 40), MID 217 “Relay function
upload” immediately returns the current relay status to the subscriber.
MID 216 can only subscribe for one single relay function at a time, but still, Open protocol
supports keeping several relay function subscriptions simultaneously.

Or
“The relay function subscription already exist”
Page 92(103)
th
5.16.9 Relay function upload (MID = 0217)

0028 0217 Rev Spare Relay no and status NUL
(ASCII 0x0)
20 bytes 8 bytes
Upload of one specific relay function’s status. The data field consists of 4 bytes specified below:

Relay no 01 3 Three ASCII digits corresponding to a relay function. (Table 40)
Relay function 02 1 One ASCII digit representing the relay function status: 1 if active 0 if not active.
status
For tracking event functions (see Table 40 above) MID 217, Relay function upload, is sent each
time the relay’s status is changed. For relay functions which are not tracking events, the upload
is sent only when the relay is set high, i.e. the data field “Relay function status” will always be 1
for such functions.
Possible answers Relay function upload acknowledge (MID = 0218)
5.16.10 Relay function upload acknowledge (MID = 0218)

(ASCII 0x0)
20 bytes 0 bytes
Acknowledge for the relay function upload.
Possible answers No
Page 93(103)
th
5.16.11 Relay function unsubscribe (MID = 0219)

0023 0219 Rev Spare RelayNo NUL
(ASCII 0x0)
20 bytes 3 bytes
Unsubscribe for a single relay functions. The data field consists of three ASCII digits, the relay
number, which corresponds to the specific relay function. The relay numbers can be found in
Table 40 above.

Or
“The relay function subscription does NOT exist”
Page 94(103)
th
5.17 Statistic telegrams
5.17.1 Histogram upload request (MID = 0300)

(ASCII 0x0)
20 bytes 9 bytes
Request to upload an histogram from the torque controller for a certain parameter set.
The histogram is calculated with all the rundown results currently present in the torque
controller’s memory and within the statistic acceptance window (statistic min and max limits)
for the requested parameter set.
Table 42

Pset number 01 3 ASCII digits. Range 0-999, the Pset number of the requested
histogram
Histogram type 02 2 ASCII digits Histogram type is two bytes long and is specified
by two ASCII digits (‘0’….’9’).
00. Torque
01. Angle
02. Current
03. Prevail torque
04. Self Tap
05. Rundown angle
Possible answers Histogram upload reply (MID = 0301)

or
“No histogram available”
“Invalid data”
Example :
Upload torque histogram for parameter set 1

0029 0300 Rev Spare 010010201 NUL
(ASCII 0x0)
20 bytes 9 bytes
Page 95(103)
th
5.17.2 Histogram upload request reply (MID = 0301)

0107 0301 Rev Spare Histogram data NUL
(ASCII 0x0)
20 bytes Bytes
Histogram upload reply for the requested parameter set and for the requested histogram type.
The histogram uploaded is made of 9 bars see picture below:
Table 43
Pset number 01 3 ASCII digits. Range 0-999, the Pset number of the requested
histogram
Histogram type 02 2 ASCII digits Histogram type is two bytes long and is specified by
00. Torque
01. Angle
02. Current
03. Prevail torque
04. Self Tap
05. Rundown angle
Sigma histogram 03 6 ASCII digits Sigma for all the rundown results (within the statistic
acceptance window) currently present in the memory
for the parameter set requested. Sigma is multiplied
by 100 and sent as an integer (2 decimals truncated).
Sigma is six byte long and is specified by six ASCII
digits (‘0’….’9’, ‘.’).
Mean value histogram 04 6 ASCII digits The mean value for all the rundown results (within the
(X-bar) statistic acceptance window) currently present in the
memory for the parameter set requested. The mean
value is multiplied by 100 and sent as an integer (2
decimals truncated). Mean value is six byte long and
is specified by six ASCII digits (‘0’….’9’, ‘.’).
Class range 05 6 ASCII digits The class range is equal to 6 sigma / 9.’
The is multiplied by 100 and sent as an integer (2
decimals truncated). Mean value is six byte long and
is specified by six ASCII digits (‘0’….’9’, ‘.’).
Bar 1 06 4 ASCII digits Number of rundown in bar 1, four bytes long and
specified as four ASCII digits (‘0’….’9’, ‘.’).
Page 96(103)
th
5.18 Automatic/Manual mode telegram (only for PowerMacs)
5.18.1 Automatic/Manual mode subscribe (MID = 0400)

(ASCII 0x0)
20 bytes 0 bytes
A subscription for Automatic/Manual mode. A message is sent to the station computer when the
mode changes (Automatic/Manual mode upload MID = 0401).
After a successful subscription the message Automatic/Manual mode upload MID = 0401 with
the current mode status is sent to the station computer.

Or
“Automatic/Manual mode subscribe already exist”
5.18.2 Automatic/Manual mode upload (MID = 0401)

0021 0401 Rev Spare Manual/Automatic mode NUL
(ASCII 0x0)
20 bytes 1 byte
The operation mode in the torque controller has changed.

The telegram contains the new operation mode that the torque controller has entered.
The Manual/Automatic mode is one ASCII digit (‘0’….’9’) that represents the operation mode.
‘0’ = Automatic mode
‘1’ = Manual mode
Possible answers Automatic/Manual mode upload acknowledge (MID = 0402)
5.18.3 Automatic/Manual mode upload acknowledge (MID = 0402)

(ASCII 0x0)
20 bytes 0 bytes
Acknowledge for a Automatic/Manual mode upload.
Possible answers No
Page 97(103)
th
5.18.4 Automatic/Manual mode unsubscribe (MID = 0403)

(ASCII 0x0)
20 bytes 0 bytes
Reset the subscription for the Automatic/Manual mode.

Or
“Automatic/Manual mode subscribe does not exist”
5.18.5 AutoDisable settings request (MID = 0410)

(ASCII 0x0)
20 bytes 0 bytes
Request for AutoDisable settings.
Possible answers AutoDisable settings reply (MID = 0411)
5.18.6 AutoDisable settings reply (MID = 0411)

0024 0411 Rev Spare Auto Disable setting Current Batch NUL
(ASCII 0x0)
20 bytes 4 bytes
Information about the setting of AutoDisable in the Torque Controller. Also contains information
about the currently running batch.
The Auto Disable setting is two ASCII digits (‘00’….’99’) that corresponds to the setting of “OKs
to disable station” in PowerMACS.
If the value is 0 the function “OKs to disable station” is not used.
Current Batch is two ASCII digits (‘00’….’99’) that represents the number of OK cycles that
have been run in the current batch. If the value is 0 no batch is running at the moment.
Possible answers none
Page 98(103)
th
5.19 Open Protocol Commands Disabled
When the “Open protocol commands disable” digital input is active, the station computer is
disabled from sending command telegrams to the torque controller. If a command telegram is
sent anyway, the torque controller answers by sending Command Error (MID 0004) “Open
protocol commands disabled” (Error 92). All open protocol commands can be found in the table
below.
Table 44 Open protocol commands
MID Request telegram from Station computer

0038 Select Job
0039 Job restart
0042 Disable tool
0043 Enable tool
0127 Abort job
0130 Job off
0410 AutoDisable settings request (PowerMacs only)
Page 99(103)
th
5.19.1 Open protocol commands disabled subscribe (MID = 0420)

0020 0420 Rev No Spare NUL
Ack (ASCII 0x0)
20 bytes 0 bytes
Set the subscription for the “open protocol commands disable” digital input. This command will
result in transmission of the open protocol commands disable input status. When a subscription
is set the “open protocol commands disable” digital input status is once uploaded (MID 0421)
automatically. Thereafter, the status is uploaded each time the digital input status changes
(push function).

Or
“Open protocol commands disabled subscription already exists”
5.19.2 Open protocol commands disabled upload (MID = 0421)

(ASCII 0x0)
20 bytes 1 byte
Upload the status of the “open protocol commands disable” digital input. The data upload
consists of one byte delivering the digital input status. The status is uploaded each time the
“open protocol commands disable” digital input changes (push function).
Data: 01 if true, 00 if false.
Possible answers Open protocol commands disabled acknowledge (MID 0422)
5.19.3 Open protocol commands disabled upload acknowledge (MID = 0422)

(ASCII 0x0)
20 bytes 0 bytes
Open protocol commands disabled upload acknowledge.
Possible answers No
Page 100(103)
th
5.19.4 Open protocol commands disabled unsubscribe (MID = 0423)

(ASCII 0x0)
20 bytes 0 bytes
Reset the subscription for “open protocol commands disable” digital input.

Or
“ Open protocol commands disabled subscription does not exist”
Page 101(103)
th
5.20 Keep alive telegram
5.20.1 Keep alive message (MID = 9999)

(ASCII 0x0)
20 bytes 0 bytes
The station computer sends a keep alive to the torque controller

The torque controller should only mirror and return the received keep alive to the station
computer.
The torque controller has a communication timeout equal to 15s i.e. if no message has been
exchanged between the integrator and the POWER FOCUS since the last 15s, the POWER
FOCUS considers the connection as lost and close it.
In order to keep the communication alive the integrator must send a keep alive to the POWER
FOCUS with a time interval lower than 15s.
Notice:
An inactivity timeout is suggested to integrator i.e. if no message has been exchanged (sent or
received) during the last 10s, send a keep alive.
Possible answers Same message mirrored by the torque controller.
Page 102(103)
th
6. Communication flow chart example
The following chapter describes how the integrator should proceed to establish a session with
the POWER FOCUS and set its subscriptions.
6.1 Establish a connection and set result subscription
”Communication Start ” MID = 0001
Wait for answer
”Communication Start ACK ” MID = 0002
”Last result data subscribe ” MID = 0060
Wait for answer
Command accepted (MID = 0005)
Tightening
performed
Last tightening result data upload reply (MID = 0061)
Wait for Ack
Last tightening result data acknowledge (MID = 0062)
Tightening
performed
Last tightening result data upload reply (MID = 0061)
…..
Page 103(103)

OpenProtocol W7 7.0

Uploaded by

Copyright:

Available Formats

OpenProtocol W7 7.0

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

OpenProtocol W7 7.0

Uploaded by

Copyright:

Available Formats

User Manual

By Atlas Copco Tools

3. POWER FOCUS OPEN PROTOCOL ..................................................................................................................7

5.8.2 Vehicle Id Number upload subscribe (MID = 0051) .................................................................................42

5.8.8 Reset all Identifiers (MID = 0157).............................................................................................................80

MID 65: Pulsor parameters added (Strategy, Torque

3. POWER FOCUS Open Protocol

3.1.1 Ethernet protocol

3.1.2 Serial protocol

3.1.2.1 Serial ASCII protocol on serial 2 or serial 1

3.1.2.2 Serial ASCII protocol with 3964 R handshake on serial 1

- request from A to B for data interchange

- end of data interchange.

POWER FOCUS sends

POWER FOCUS Integrator

Fig 1: POWER FOCUS sends Command start acknowledge

POWER FOCUS receives

POWER FOCUS Integrator

BEL HT BEL HT STX 00200001 /0 ETX DLE ETX BCC

Fig 2: POWER FOCUS receives Command start

3.1.2.3 Serial cable loss detection ON with keep alive

3.2 Message structure

All information sent over the communication links is ASCII format.

Header Data Field Message End

The header contains 20 bytes.

3.4 Data Field

The specific data format depends on the actual command.

Data Field ASCII data representing the data.

Id Parameter id (“00”..”99”), length two bytes.

Parameter Value Parameter value is defined by parameter selection (fixed number of

All the parameters of the data field should be sent.

3.5 Message End

0073 Alarm Unsubscribe

0300 Histogram upload request

5.1 Request / Response telegram

MID Request telegram from Station computer

5.2 Event Telegram

0210 Status “external monitored inputs” subscribe

MID Event telegram acknowledge from the Station computer

5.3 Communication telegram

5.3.1 Communication start (MID = 0001)

Header Data Field Message End

Possible answers Communication start acknowledge (MID = 0002)

Sent by Station computer.

5.3.2 Communication start acknowledge (MID = 0002)

Header Data Field Message End

Table 7 MID 0002 revision 1

Parameter Id Bytes Comment

Table 8 MID 0002 revision 2

Parameter Id Bytes Comment

Table 9 MID 0002 revision 3

Parameter Id Bytes Comment

Sent by the torque controller.

Header Data Field Message End

5.3.3 Communication stop (MID = 0003)

Header Data Field Message End

Possible answers Command accepted (MID = 0005).

Sent by Station computer.