0% found this document useful (0 votes)

3K views224 pages

Atlas Copco Open Protocol 1.6

pdf2

Uploaded by

Cesar Chacon

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

3K views224 pages

Atlas Copco Open Protocol 1.6

pdf2

Uploaded by

Cesar Chacon

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

Revision 10 0 (224)
Contents

Table 79 MID 0221 Digital input no and status ........................................................................................................... 167

Table 80 Example 1 input ........................................................................................................................................... 170
Table 81 Example 1 output ........................................................................................................................................ 170
Table 82 MID 0251 Selector socket data ................................................................................................................... 175
Table 83 MID 0254 Selector green lights ................................................................................................................... 176
Table 84 MID 0254 Selector red lights ....................................................................................................................... 177
Table 85 MID 0262 TLS ST Tool Tag Identity ............................................................................................................ 179
Table 86 MID 0300 Parameter set and histogram type .............................................................................................. 182
Table 87 MID 0301 Histogram data............................................................................................................................ 183
Table 88 MID 501Motor tuning result data ................................................................................................................. 192
Table 89 Variable names for Bolt values .................................................................................................................... 196
Table 90 Measurement values ................................................................................................................................... 196
Table 91 Variable names for step values ................................................................................................................... 199
Table 92 Special values type ..................................................................................................................................... 206
Table 93 Variable names for special values in Station data, MID 0106...................................................................... 207
Table 94 Variable names for special values in Bolt data, MID 0107 .......................................................................... 207
Table 95 Product MID/Revision support ..................................................................................................................... 210
Table 96 Parameters not supported in PF6000 .......................................................................................................... 219
Table 97 Parameters not supported or managed under special conditions in PF6000 .............................................. 219

8 (224) Release 1.4

Revision 10 9836 4415 01
Introduction

1 Introduction
Open Protocol is an interface for building applications for remote control or data subscription of
controllers. It is platform independent and can be implemented on Linux, PLC, printers, and all Windows
platforms for example.
The Open Protocol supports both serial and Ethernet connection.

Figure 1 Open Protocol in the network, example

1.1 Revision history

The changes since release 1.2 revision 14 are:
- Added revision 1, 2 and 3 for MID 0100.
Added revision 3 MID 0105.
- Corrected the header contains Table 1 Station is two digits, correspondening to the rest of the
document, the Spindel ID starts at byte 15 and spare at 17.
- Added revision 4 for MID 0035. Corrected the revision range in MID 0035 and MID 0034
- Correction of Identifier length in MID 151 to 100
- More thoroughly description of MID 0022 concerning the messages exchanges
- Added Revision 3 documentation for MID 32.
- Corrected the description of MID 411.
- Created a Ford special appendix due to DR 2104. Ford special rev 2 of MID11 and MID 61 now
documented 2011-06-09 BJ
- Corrections done to all headers Revision fields from N/A to the real value.
- Added rules for Revision Handling 2011-06-14 /BJ.

9836 4415 01 Release 1.4

Revision 1.2 9 (224)
Introduction

- Updated the revision to 1.3.0 due to new MID revisions created. 2011-06-15
- Clarification of MID 122-123 due to DR2789. Revised to 1.3.2 /BJ. 2011-09-07
- Corrected the MID 33 description due to DR 2917, DR2918. Revised to 1.3.3/BJ. 2011-09-15
- Corrected the MID129 description due to DR2965. Revised to 1.3.4 /BJ 2011-10-03
- Corrected the Ackflag doc. in the headers for all MID subscription messages. DR3009/BJ 2011-
10-11
- Added changes for the new product PowerMACS Press RM 2011-10-20
- Corrections done for MID 0033 Rev. 2 2011-11-14 /BJ Rev. 1.4.2
- Corrections done for MID 65 DR 2941 2011-11-14/ BJ Rev 1.4.3
- Explenation for MID 33 Rev 3 added DR 3057/BJ Rev 1.4.4
- Updating table 73 due to DR 3114/BJ Rev 1.4.5
- Updated rev number to DIM rev number Rev 1.4.6
- New revision 002 for MID 0010/0011 for transmission of number of stages for each Pset/Mset
and a new revision 005 for MID 0040/0041 for transmission of tool model according to W 10.8
DR 3281 Resulting in new document revision 1.5.0 BJ 2012-01-26.
- New revision for the document 1.5.1 Padding for Tool Model in Rev. 5 of MID 41 changed to
spaces BJ W10.8 DR 3281.2012-01-27
- New rev. for document 1.5.2. MID 41 length corrected. BJ 2012-01-27
- New rev. 1.5.3 According to DR 3457 in PF project W10.9
- New release 1.6.0 due to introducing PF6000 product/BJ 2012-09-21.
 New chapter added for data field implementation
 The appendix 6.3 Product MID and revision support table changed to
include PF6000 product.
 In the appendix a table is added for PF6000 parameter support.
 In each MID description tables a column is added for marking of product
parameters support or not.
 The following MID/Revisions has been changed/added:
MID 60/61new revision 7
MID 12/13 new revision 4. See Toyota appendix
MID 25 new revision 2. See Toyota appendix
MID 70/71 new revision 2
New MIDs 500-504 for tool motor tuning

10 (224) Release 1.4

Revision 10 9836 4415 01
Using Open Protocol

1.2 Specification Revision rules

Following rules for document revision handling is stated.
Example: 1.2.3.
The 1 is the Version of the protocol. No compatibility exists between Versions and that means that major
changes has been done in the common communication procedures such as acknowledging, start up etc.
The 2 is the Release of the protocol. On release level the protocol must be backward compatible according
to the rules of new MID Revisions built on earlier MID Revisions. A new Release must hence be
backward compatible on the MID Revision and MID level. A new MID or a new MID Revision created,
due to new functionality being introduced, increase the figure of the Release of the protocol.
The 3 is the Revision of the protocol. The Revision is increased due to corrections done in existing MIDs
and MIDs revisions. These corrections must NOT have influences on the backward compatibility.

9836 441 01 Release 1.4

Revision 10 0 (224)
Introduction

1.3 Terminology
The following terminology is used in this manual.

Term Definition

Controller Open Protocol supports Power Focus, and PowerMACS controllers. See
PF6000 1.5

Table 95 for limitations. PowerMACS classic supports FFCCP. See the

PowerMACS user guide for information.

Integrator Integrator hardware can for example be a PC, PLC, or printer. Integrator
applications use the Open Protocol in the integrator HW.

Message A message consists of three parts; header, data field and message end, as
described in section Message structure. Depending on type of communication,
a package sent or received includes the message and an encapsulation before
and after the message, as described in section Communication.

MID Message ID of the message represented by four digits, for example 0052.
MID 0052 refers to Vehicle ID Number upload. The ID is always included in
the message.

MID revision A MID can have several revisions. If no revision is set, revision 1 is applied. A
MID is usually revised to include more data, thus increasing the length of the
message. MID revisions are added to ensure backwards compatibility.
See for example MID 0052 where revision 2 includes identifier result parts 2,
3 and 4 to the data. If revision 1 is used, this data is not sent. If revision 2 is
used and the controller does not support more than one identifier = revision 1,
then only the VIN-number is sent in revision 1.
See
PF6000 1.5

Table 95 for different product‟s MIDs/Revisions support.

Implementation rule for revisions is that there is not allowed to have revision
gaps. In other words, the supported revisions MUST NOT look like this:
MIDxx/rev1,rev2,rev5 or MIDxx/rev5 only.
If supporting MIDxx/rev5 the implementation must for instance support an
request or subscription on MIDxx/rev 2 and reply with that revision as well.
Especially important to remember at new implementation of the Open

12 (224) Release 1.4

Revision 10 9836 4415 01
Using Open Protocol

Protocol in new products.

Subscribe Subscribe is the term used when the controller sends specific data to the
subscriber or subscribers each time it is generated.

Unsubscribe Unsubscribe is the term used when a subscription is cancelled by the

subscriber. The data will no longer be sent from the controller.

9836 441 01 Release 1.4

Revision 10 0 (224)
Using Open Protocol

2 Using Open Protocol

This section describes the communication structure between the integrator HW and the controller.

Integrator HW Controller

Integrator Application
Communication
Open Protocol Open Protocol
Control data collection
TCP/IP Siemens TCP/IP Siemens
3964R 3964R

RS232 RS232

Figure 2 Communication structure

2.1 Communication
The Open Protocol can be run using Ethernet or serial communication. The Open Protocol is a full duplex
protocol, which means that data can be sent and received at the same time. Every communication partner
must be able to operate a send and receive facility simultaneously.
 Power Focus controller can accept up to 5 connections at a time, shared between serial and Ethernet.
 PowerMACS controller can accept two Ethernet connections per station at a time. There is no support
for serial connection.

2.1.1 Ethernet protocol

The integrator connects to the controller, and the controller accepts the connection. The controller is the
server, and the integrator application is the client. The protocol used is TCP/IP. The default port used for
the communication is 4545.
Note! Ensure that the port is correctly configured in the controller!

2.1.2 Serial protocol

There are two kinds of serial protocol.
 Serial ASCII protocol
 Serial ASCII protocol with 3964R handshake
Note! Ensure that the serial port is correctly configured according to the corresponding serial
protocol used!

9836 4415 01 Release 1.4

Revision 1.2 15 (224)
Using Open Protocol

When running serial communication, the messages are encapsulated according to the protocol used. The
messages within the encapsulation are the same regardless of type of communication.
Figure 3 Serial communication protocol, and Figure 5 Controller sending serial communication protocol
with 3964R handshake, show the encapsulation requirements that must be fulfilled when using serial
communication.

Serial ASCII protocol

 All messages sent from the integrator
to the controller must be stamped with
a 4 ASCII character tag before the Tightening controller Integrator
STX character: BEL (ASCII 0x07
bell) HT (ASCII 0x09 horizontal tab)
BEL (ASCII 0x07) HT (ASCII 0x09). BELHTBELHTSTX<Message>ETX

 All messages must be encapsulated STX<Message>ETX

between STX (ASCII 0x02 Start of
Text) and ETX (ASCII 0x03 End of
Text).

Figure 3 Serial communication protocol

Serial ASCII protocol with 3964 R handshake

All messages exchanged between the controller and the integrator are transferred within the message
frame in accordance with Siemens Procedure 3964R.
The Procedure 3964R is a transfer protocol between two systems A and B. Every time one of the systems
wants to send, the following procedure is initiated.
 request from A to B for data interchange
 data interchange
 end of data interchange
The protocol 3964R allows reliable data as the receiver must first signal to the transmitter that it is ready
to receive (communication setup) and then after data interchange must acknowledge correct reception.
Data integrity is ensured by an additional block check character (BCC).
The block check control is the XOR sum of all the transmitted data bytes. The generation begins with the
first byte of the message and ends after characters DLE (ASCII 0x10 Data Link Escape) and ETX (ASCII
0x03 End of Text).
The description is valid for both cases, when the integrator is the sender and the controller the receiver,
and the opposite. See Figure 4 and Figure 5 Controller sending serial communication protocol with 3964R
handshake.

16 (224) Release 1.4

Revision 10 9836 4415 01
Using Open Protocol

Tightening controller Integrator

STX
Acknowledgement
timeout 2s
DLE

BELHTBELHTSTX<Message>ETXDLEETXBCC

DLE

Figure 4 Integrator sending serial communication protocol with 3964R handshake

Tightening controller Integrator

STX

Acknowledge-
ment timeout
2s DLE
Character delay
STX<Message>ETXDLEETXBCC timeout 100 ms

DLE

Figure 5 Controller sending serial communication protocol with 3964R handshake

The following steps are included when the controller is sending to the integrator.
1. The controller sends the control character STX (ASCII 0x02 start of text) and waits for an
acknowledgment for 2s (acknowledgment timeout = 2s).
2. The integrator responds with the acknowledge character DLE (ASCII 0x10 data link escape) and the
Controller 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, the connection
setup procedure has failed. The connection setup procedure is aborted after a total of 6 unsuccessful
attempts.

9836 441 01 Release 1.4

Revision 10 0 (224)
Using Open Protocol

3. The Controller sends an Open Protocol serial message followed by the characters ETX, DLE, ETX
and BCC as end identifier. The controller then waits for an acknowledgement character from the
integrator.
4. The integrator monitors the incoming time between two characters. The interval between two
characters may not exceed the character delay timeout =100 ms.
5. The integrator sends the control character DLE and the Open Protocol message has been accepted
error free.
If the integrator responds with control character NAK (ASCII 0x15 Negative acknowledgment) or any
other character (apart from DLE) or if the acknowledgment delay time elapses with no answer, then
the transmission is aborted and the controller starts a new connection setup with character STX. The
procedure is aborted and the controller sends a NAK to the integrator after a total of six unsuccessful
attempts.
The following is also applicable:
 If the integrator sends a NAK during transmission, then the controller 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 an STX from the controller in idle state, it answers with DLE. If it receives
any other character than STX in idle state it waits for the character delay time to elapse and then sends
a NAK.
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 controller.
 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 controller. If the BCC is not correct a NAK is sent to the controller. A retry is then
awaited. If it is not possible to receive the message with error free BCC after 6 attempts, the integrator
aborts the reception.

Serial cable loss detection

In order to be able to detect serial cable loss, the controller has a communication timer. This timer is reset
every time it sends or receives a message on the serial line. This strategy to detect cable loss implies that
the client application sends a keep alive before the timer in the controller expires.

An inactivity timeout is suggested to integrator i.e. if no message has been exchanged during
the last 10s, send a keep alive.

In a Power Focus controller, the connection is assumed to be lost and the controller closes the connection
if no messages have been exchanged for 15 seconds, by default. It is possible to remove the need of
sending keep alive to the controller. In this case the controller will not be able to detect the loss of serial
connection or serial cable. This possibility can be used to reduce the load on certain serial devices (PLC,
printers …) which have difficulties to handle full duplex traffic.
In Power Focus, to remove the need of sending keep alive messages using serial connection, uncheck
C331 Serial cable loss detection.

18 (224) Release 1.4

Revision 10 9836 4415 01
Using Open Protocol

Figure 6 Power Focus Open Protocol settings

In some cases after communication lost, the controller may answer to MID 0001
Communication start with MID 0004 Command error Client already connected.

This case must be handled by the client application and should not be considered as a failure.

2.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 detail.

Example
This following example shows MID 0071 Alarm.
 Figure 7 shows the number of the byte above the message.
 Figure 8 shows the same message without the numbers but with the spaces shown.
The spaces must be included according to each message structure.

Figure 7 Message example with byte number

9836 441 01 Release 1.4

Revision 10 0 (224)
Using Open Protocol

00530071 01E404021031042008-09-25:10:14:16NUL

Figure 8 Message example without byte number

2.2.1 Header
The header contains 20 bytes according to Table 1.
Table 1 Header content
Message part Byte Parameter Value
Header 1-4 Length The length is the length of the header plus the data field
excluding the NUL termination.
The header always includes information about the length
of the message. The length is represented by four ASCII
digits („0‟…‟9‟) specifying a range of 0000 to 9999.
The MID is four bytes long and is specified by four ASCII
5-8 MID digits („0‟…‟9‟). The MID describes how to interpret the
message.
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
several versions are available for the same MID. Using
9-11 Revision the revision number the integrator 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 integrator is interested in the initial
revision (revision 1) of the MID, it can send three spaces
as MID revision or 001.
ONLY FOR SUBSCRIPTION 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” message
12 No ack flag
sent by the controller (reliable mode).
If set, the controller will only push out the information
required without waiting for a receive acknowledgement
from the subscriber (unreliable mode).
The station the message is addressed to in the case of
controller with multi-station configuration. The station ID
13-14 Station ID is 2 byte long and is specified by two ASCII digits
(„0‟…‟9‟). One space is considered as station 1 (default
value). Only available if not marked with N/A.
The spindle the message is addressed to in the case
several spindles are connected to the same controller.
The spindle ID is 2 bytes long and is specified by two
15-16 Spindle ID
ASCII digits („0‟…‟9‟). Two spaces are considered as
spindle 1 (default value). Only available if not marked
with N/A. OBS! Is allways 0 for FORD OBS!
17-20 Spare Reserved space in the header for future use.

The Length and MID are padded on the left with zeroes (ASCII 0x30).

20 (224) Release 1.4

Revision 10 9836 4415 01
Using Open Protocol

2.2.2 Data Field

The Data Field is ASCII data representing the data. The data contains a list of parameters depending on
the MID. Each parameter is represented with an ID and the parameter value. Note that the ID always is 2
bytes. The data field can be empty or contain a maximum of 9979 bytes.
Table 2 Data field content
Message part Byte Parameter Value
Data field 21-22 01 Parameter ID (00...99), length two bytes. The parameter
ID is padded on the left with the ASCII characters „0‟.
Parameter value is defined by parameter selection (fixed
number of bytes).
ASCII digits („0‟…‟9‟) or ASCII characters between 0x20
and 0x7F Hex.
If the Parameter value is specified only by ASCII digits,
then the parameter value is padded on the left with the
ASCII characters „0‟.
23 - Parameter 01 value If the Parameter value is specified by ASCII characters,
then the parameter value is padded on the right with
space <SPC> (ASCII character 0x20 Hex).

If the Parameter value is not supported, the whole

parameter field is filled with spaces <SPC> (ASCII
character 0x20 Hex).

n- 02 Parameter 02
n+2- Parameter 02 value Parameter 02 value…
03 Parameter 03
Parameter 02 value Parameter 03 value…

2.2.3 Data field implementation rules

 All the parameters of the data field must be sent.

 The data field of each message is subject to future modifications handled by adding MID
revisions. A new revision can include new parameters or increased length of the data field.
 At implementation of an existing MID with a number of versions all versions must be
supported
 Not supported parameters must be filled with spaces (hex 020). This is specially applicable at
reusing a MID for a new product.
 If the not supported parameters can be determined as never to be supported, a new MID
MUST be defined with these parameters excluded, which in the long run will give a cleaner
interface. To be sent to the Open Protocol comitte.
 All MIDs descriptions that havn’t the colomn “Not supported by” defined, are supposed to
be fully implemented and supported.

9836 441 01 Release 1.4

Revision 10 0 (224)
Using Open Protocol

 All torque and angle values sent in the data part are sent in units Nm and degrees when
nothing else is specified. For degrees one turn represents 360 degrees.

2.2.4 Message End

The message end is empty.
Table 3 Message end content
Message part Byte Parameter Value
Message end 0 Message end All the messages are NUL terminated. The NUL
termination is not included in the message length. In this
manual this is illustrated with NUL, ASCII 0x00.

22 (224) Release 1.4

Revision 10 9836 4415 01
Communication examples

3 Communication examples
This section gives a few examples on communication sessions.

3.1 Establishing contact

This section describes how to set up a communication.

3.1.1 Ethernet connection

Prerequisite: The controller has an IP address and listens to port 4545.

1. The controller listens to port Tightening controller Integrator

4545.

2. The integrator connects to the Port TCP/IP [SYN] connect

controller. 4545

TCP/IP [SYN ACK] accept

3. The controller accepts the
connection.
00200001 [NUL]

4. The integrator sends MID 0001

Communication start. 00570002001 0100010204
03Airbag [NUL]
5. The controller answers
MID 0002 Communication start
acknowledge with Cell ID 0001,
Channel ID 04 and Controller
name Airbag.

Figure 9 Ethernet connection example

9836 441 01 Release 1.4

Revision 10 0 (224)
Communication examples

3.1.2 Serial connection

Prerequisite: The controller and the integrator are connected through a serial cable.

1. The integrator sends Tightening controller Integrator

MID 0001 Communication start.

2. The controller answers BELHTBELHTSTX

MID 0002 Communication start 00200001 NULETX
acknowledge with Cell ID 0001,
Channel ID 04 and Controller
name Airbag. STX00570002001 0100010204
03Airbag [NUL]ETX

Figure 10 Serial connection example

24 (224) Release 1.4

Revision 10 9836 4415 01
Communication examples

3.1.3 Serial connection with 3964R

1. The integrator sends request
for connection with the Tightening controller Integrator
controller.
STX
2. The controller accepts the
request to send. DLE

3. The integrator sends BELHTBELHTSTX

MID 0001 Communication start. 00200001 NULETXBCC

DLE
4. The controller accepts the
communication.
STX
5. The controller sends request to
send on Siemens protocol. DLE

6. The integrator accepts the

communication. STX00570002001 0100010204
03Airbag [NUL]
ETXDLEETXBCC
7. The controller answers
MID 0002 Communication start
DLE
acknowledge with Cell ID 0001,
Channel ID 04 and Controller
name Airbag.
8. The integrator accepts the
message. Figure 11 Serial connection with 3964R, example

3.2 Starting a subscription

The example shows the sequence for MID 0060 Last tightening data subscribe and MID 0061 Last tightening
data upload.

Prerequisite: A communication session is already established. The example shows only the data sent, not
the protocol frames.

9836 441 01 Release 1.4

Revision 10 0 (224)
Communication examples

1. The integrator sends

MID 0060 Last tightening result Tightening controller Integrator
data subscribe. The subscription
is for revision number 6.
00200060006 NUL

2. The controller sends MID 0005

Command accepted. 002400050060 NUL

3. A tightening is performed.
(See arrow in figure.) 05260061006 0101020103Airbag
…….NUL
4. The controller sends
MID 0061 Last tightening result 00200062 NUL
data upload and then waits for
acknowledgement.
The example shows only
parameters 01, 02 and 03 of the
total 55 parameters for Figure 12 Starting a subscription
revision 6. See Table 41 MID
0061 Revision 1.

5. The integrator sends

MID 0062 Last tightening result
data acknowledge.

3.3 Sending a request

This example shows a request for collecting parameter set data.

1. The integrator sends

MID 0012 Parameter set data Tightening controller Integrator
upload request.
The request is sent for parameter
00230012 001NUL
set number 001.

2. The controller sends MID 0013

Parameter set data upload reply. 00840013 0100102pset1
For a description of the 031040305001200
parameters, see Table 12 MID 0600150007001433080036009007201000659NUL
0013 Revision 1
.

Figure 13 Sending a request

26 (224) Release 1.4

Revision 10 9836 4415 01
Message categories

4 Message categories
Most, but not all, messages can be sorted into two main categories. MID 0001 Communication start or
MID 0003 Communication stop, do not belong to any of these categories.

The categories are:

 Request messages
 Event messages

4.1 Request and request reply messages

The integrator sends a request to the controller and the controller responds to the request with a positive or
negative reply. If no answer to the request is received before the response timeout, the integrator should
re-send the request up to three times. After three times, the connection is considered lost and a new
connection must be established.
Some of the request messages are available as Open Protocol commands disable. These commands are
rejected if the digital input Open Protocol commands disable digital input is active. The commands are
marked in Table 4 Available messages. See also section Open Protocol Commands Disabled for more
information.
Example of request and request reply messages:
 The integrator sends MID 0018 Select Parameter set
 The controller answers MID 0005 Command accepted or MID 0004 Command error

4.2 Event Messages

The event messages can be divided into three categories:
 Event subscribe – unsubscribe messages
 Event messages
 Event acknowledge messages

Event subscribe – unsubscribe messages

The subscription is made with the subscribe - unsubscribe message. The subscription can be cancelled at
any time by the integrator by sending an unsubscribe message.

Events messages
The controller can spontaneously send messages to the integrator after an event such as a tightening or an
alarm. This service is only enabled after a subscription event message.

9836 441 01 Release 1.4

Revision 10 0 (224)
Message categories

Event message acknowledge

Events
ID Description

0251 Selector socket info Controller X

0252 Selector socket info acknowledge Integrator X
0253 Selector socket info unsubscribe Integrator X
0254 Selector control green lights Integrator X
0255 Selector control red lights Integrator X
0260 Tool Tag ID request Integrator X
0261 Tool Tag ID subscribe Integrator X
0262 Tool Tag ID Controller X X
0263 Tool Tag ID acknowledge Integrator X
0264 Tool Tag ID unsubscribe Integrator X
0270 Controller reboot request Integrator X X
0300 Histogram upload request Integrator X
0301 Histogram upload reply Controller X
0400 Automatic/Manual mode subscribe Integrator X
0401 Automatic/Manual mode Controller X
0402 Automatic/Manual mode acknowledge Integrator X
0403 Automatic/Manual mode unsubscribe Integrator X
0410 AutoDisable settings request Integrator X
0411 AutoDisable settings reply Controller X
0420 Open protocol commands disabled subscribe Integrator X
0421 Open protocol commands disabled Controller X
0422 Open protocol commands disabled acknowledge Integrator X
0423 Open protocol commands disabled unsubscribe Integrator X
0500 Motor tuning result data subscribe Integrator X
0501 Motor tuning result data Controller X
0502 Motor tuning result data acknowledge Integrator X
0503 Motor tuning result data unsubscribe Integrator X
0504 Motor tuning request Integrator X
8000 Audi emergency status subscribe Integrator X
8001 Audi emergency status Controller X
8002 Audi emergency status acknowledge Integrator X
8003 Audi emergency status unsubscribe Integrator X
9999 Keep alive open protocol communication Integrator X X

32 (224) Release 1.4

Revision 10 9836 4415 01
All messages

5 All messages
The following section describes all the messages in the Open Protocol.
The column “Not supported by” means that the product mentioned is not supporting that specific data
field. See further in chapter 2.2.3 Data fields implementation rules.

5.1 Communication messages

5.1.1 MID 0001 Communication start

This message enables the communication. The controller does not respond to any other command before
this
This telegram can be used for a PowerMACS 4000 system running a press instead of a spindle. A press
system only suports revision 5 and higher of the telegram and will answer with MID 0004, MID revision
unsupported if a subscription is made with a lower revision. See also section 6.1 Notes about press
systems
 Message sent by: Integrator
 Answers: MID 0002 Communication start acknowledge or
MID 0004 Command error, Client already connected or MID revision unsupported

Example: Communication start with call for MID 0002 Communication start acknowledge revision 3.
00200001003 NUL

Message part Parameter Byte Value

Header Length 1-4 0020
MID 5-8 0001
Revision of MID 0002 9-11 Range: 000-005
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field N/A 0 N/A
Message end 21 NUL

9836 441 01 Release 1.4

Revision 10 0 (224)
All messages

5.1.2 MID 0002 Communication start acknowledge

When accepting the communication start the controller sends as reply, a Communication start
acknowledge. This message contains some basic information about the controller, such as cell ID, channel
ID, and name.
 Message sent by: Controller
 Answer: None
Example, revision 1: The connected controller belongs to cell 1, the channel ID is 1 and the name is
Airbag1
00570002 010001020103Airbag1 NUL

Message part Parameter Byte Value

Header Length 1-4 Rev 1: 0057
Rev 2: 0062
Rev 3: 0125
Rev 4: 0163
Rev 5: 0173
MID 5-8 0002
Revision 9-11 Range: 000-005
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field Controller information 21-length See Revisions
Message end Rev 1: 58 NUL
Rev 2: 63
Rev 3: 126
Rev 4: 164
Rev 5: 174

Table 5 MID 0002 Revision 1

Parameter Byte Value Not supported by
Cell ID 21-22 01
23-26 The cell ID is four bytes long specified by four ASCII
digits.
Range: 0000-9999.
Channel ID 27-28 02
29-30 The channel ID is two bytes long specified by two
ASCII digits.
Range: 00-20.
Controller Name 31-32 03
33-57 The controller name is 25 bytes long and specified by
25 ASCII characters.

34 (224) Release 1.4

Revision 10 9836 4415 01
All messages

Table 6 MID 0002 Additions for revision 2

Parameter Byte Value Not supported by
Supplier code 58-59 04 PF6000
60-62 ACT (supplier code for Atlas Copco Tools) specified
by three ASCII characters.

Table 7 MID 0002 Additions for revision 3

Parameter Byte Value Not supported by
Open Protocol version 63-64 05 PF6000
65-83 Open Protocol version. 19 ASCII characters. This
version mirror the IMPLEMENTED version of the
Open Protocol and is hence not the same as the
version of the specification. This is caused by, for
instance, the possibility of implementation done of
only a subset of the protocol.
Controller software version 84-85 06
86-104 The controller software version. 19 ASCII characters.
Tool software version 105-106 07
107-125 The tool software version. 19 ASCII characters.

Table 8 MID 0002 Additions for revision 4

Parameter Byte Value
RBU Type 126-127 08 PF6000
128-151 The RBU Type. 24 ASCII characters.
Controller Serial Number 152-153 09
154-163 The Controller Serial Number. 10 ASCII characters.

9836 441 01 Release 1.4

Revision 10 0 (224)
All messages

Table 9 MID 0002 Additions for revision 5

Parameter Byte Value Not supported by
System type 164-165 10
166-168 The system type of the controler. 3 ASCII digits
Possible values are:
000 = System type not set
001 = Power Focus 4000
002 = PowerMACS 4000
003 = Power Focus 6000
System subtype 169-170 11 PF6000
171-173 The system subtyp. 3 ASCII digits

If no subtype exists it will be set to 000

For a Power Focus 4000 and PF 6000 system the

valid subtypes are:
001 = a normal tightening system

For a PowerMACS 4000 system the valid subtypes

are:
001 = a normal tightening system
002 = a system running presses instead of spindles.

For details about the Press system see section 6.1

Notes about press systems

5.1.3 MID 0003 Communication stop

This message disables the communication. The controller will stop to respond to any commands except for
MID 0001 Communication start after receiving this command.

 Message sent by: Controller:

 Answer: MID 0005 Command accepted

Message part Parameter Byte Value

Header Length 1-4 0020
MID 5-8 0003
Revision 9-11 00-01
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field N/A N/A
Message end 21 NUL

36 (224) Release 1.4

Revision 10 9836 4415 01
All messages

5.2 Request reply messages

5.2.1 MID 0004 Command error

This message is used by the controller when a request for any reason has not been performed. The data
field contains the message ID of the message request that failed as well as an error code.
 Message sent by: Controller:
 Answer: None
Example: The request MID 0018 Select parameter set failed, the parameter set number was not present in
the controller.
00260004 001802NUL

Message part Parameter Byte Value

Header Length 1-4 0026
MID 5-8 0004
Revision 9-11 Range: 000-001
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field MID and error code 21-26 see Table 10 Error code description.
Message end 27 NUL

Table 10 Error code description

ID Description
00 No Error
01 Invalid data
02 Parameter set ID not present
03 Parameter set can not be set.
04 Parameter set 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

9836 441 01 Release 1.4

Revision 10 0 (224)
All messages

ID Description
16 Connection rejected protocol busy
17 Job ID 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
23 Job batch decrement failed
24 Not possible to create Pset
25 Programming control not granted
30 Controller is not a sync Master/station controller
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 ID
54 Tool Tag ID unknown
55 Tool Tag ID subscription already exists
56 Tool Tag ID subscription does not exist
57 Tool Motor tuning failed
58 No alarm present
59 Tool currently in use
60 No histogram available
70 Calibration failed
71 Subscription already exists
72 Subscription does not exists
79 Command failed
80 Audi emergency status subscription exists
81 Audi emergency status subscription does not exist
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
86 The selector socket info subscription already exist
87 The selector socket info subscription does not exist

38 (224) Release 1.4

Revision 10 9836 4415 01
All messages

ID Description
88 The digin info subscription already exist
89 The digin info subscription does not exist
90 Lock at batch done subscription already exist
91 Lock at batch done 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

5.2.2 MID 0005 Command accepted

This message is used by the controller to confirm that the latest request sent by the integrator was
accepted. The data field contains the MID of the request accepted.
 Message sent by: Controller.
 Answer: None.
Example: The request MID 0018 Select parameter set is accepted.

00240005 0018NUL

Message part Parameter Byte Value

Header Length 1-4 0024
MID 5-8 0005
Revision 9-11 Range: 000-001
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field MID accepted 21-24 Four ASCII digits
Message end 25 NUL

9836 441 01 Release 1.4

Revision 10 0 (224)
All messages

5.3 Parameter set messages

5.3.1 MID 0010 Parameter set ID upload request

A request to get the valid parameter set IDs from the controller.
 Message sent by: Integrator
 Answer: MID 0011 Parameter set ID upload reply

Message part Parameter Byte Value

Header Length 1-4 0020
MID 5-8 0010
Revision, MID 0011 9-11 Range: 000-002
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field N/A N/A
Message end 21 NUL

5.3.2 MID 0011 Parameter set ID upload reply

The transmission of all the valid parameter set IDs of the controller. In the revision 000-001 the data field
contains the number of valid parameter sets currently present in the controller, and the ID of each
parameter set present. In revision 2 is the number of stages on each Pset/Mset added.
 Message sent by: Controller
 Answer: None
Example: parameter set 1 and 2 are present in the controller.

00290011 002001002NUL

Message part Parameter Byte Value

Header Length depends on the number of parameter
Length 1-4
sets.
MID 5-8 0011
Revision 9-11 Range: 000-002
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A

40 (224) Release 1.4

Revision 10 9836 4415 01
All messages

Message part Parameter Byte Value

Data field, part 1 The number of
parameter sets in the 21-23 Three ASCII digits. Range: 000-999
controller
Data field, part 2 The ID of each
24-(Npset*3) Three ASCII digits for each parameter set
parameter set present
Message end Length +1 NUL

Table 11 MID 0011 additions for revision 2

Message part Parameter Byte Value

Data field, part 3 Two ASCII digits. Range: 00-99
For a single Pset: 1,2 or more stages.
For a Multistage:
The number of cycles Numb. of Multistage stages (Psets) * (
(24+Npset*3)-
= stages for each Number of Pset stages)
(24+Npset*5)
Pset/Multistage ID Ex. 5 Multistage stages and 1 pset with 1
stage and four Psets with two stages each,
will be (1*1 + 4 *2) = 9 stages in total.

Message end Length +1 NUL

5.3.3 MID 0012 Parameter set data upload request

Request to upload parameter set data from the controller.
 Message sent by: Integrator
 Answer: MID 0013 Parameter set data upload reply, or
MID 0004 Command error, Parameter set not present

Example: Request to upload parameter set data for parameter set 1.

00230012 001NUL

Message part Parameter Byte Value

Header Length 1-4 0023
MID 5-8 0012
Revision, MID 0013 9-11 Range: 000-002
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field Parameter set ID 21-23 Three ASCII digits. Range: 000-999
Message end 24 NUL

9836 441 01 Release 1.4

Revision 10 0 (224)
All messages

Table 11 MID 0012 additions for Revision 3

Message part Parameter Byte Value
Header Length 1-4 0031
MID 5-8 0012
Revision, MID 0013 9-11 Range: 003-004
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field Parameter set ID 21-23 Three ASCII digits. Range: 000-999
Data field Pset file version 24-31 00000000 (special usage see Toyota appendix)
Message end 24 NUL

5.3.4 MID 0013 Parameter set data upload reply

Upload of parameter set data reply. The following tables show the revisions available:
 Table 12 MID 0013 Revision 1
 Table 12 MID 0013 additions for revision 2
 Table 13 MID 0013 Revision 3
 Table 14 MID 0013 Revision 4

 Message sent by: Controller

 Answer: None
Example: Upload parameter set data for parameter set 1 called Airbag 1.
01040013 0100102Airbag1 031040305001200
0600150007001400080036009007201000480NUL

Message part Parameter Byte Value

Header Length 1-4 0104
MID 5-8 0013
Revision 9-11 Range: 000-003
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field Parameter set data 21-104 See Revisions
Message end 105 NUL

Table 12 MID 0013 Revision 1

Parameter Byte Value Not supported by
Parameter set ID 21-22 01
23-25 Three ASCII digits, range 000-999
Parameter set name 26-27 02

42 (224) Release 1.4

Revision 10 9836 4415 01
All messages

Parameter Byte Value Not supported by

28-52 25 ASCII characters. Right padded with space if
name is less than 25 characters.
Rotation direction 53-54 03
55 1=CW, 2=CCW
Batch size 56-57 04 PF6000
58-59 2 ASCII digits, range 00-99
Torque min 60-61 05
62-67 The torque min limit is multiplied by 100 and sent as
an integer
(2 decimals truncated). It is six bytes long and is
specified by six ASCII digits.
Torque max 68-69 06
70-75 The torque max limit is multiplied by 100 and sent as
an integer
(2 decimals truncated. It is six bytes long and is
specified by six ASCII digits.
Torque final target 76-77 07
78-83 The torque final target is multiplied by 100 and sent
as an integer (2 decimals truncated). It is six bytes
long and is specified by six ASCII digits.
Angle min 84-85 08
86-90 The angle min value is five bytes long and is
specified by five ASCII digits. Range: 00000-99999.
Angle max 91-92 09
93-97 The angle max value is five bytes long and is
specified by five ASCII digits. Range: 00000-99999.
Final Angle Target 98-99 10
100-104 The target angle is specified in degrees. 5 ASCII
digits. Range: 00000-99999.

Table 13 MID 0013 additions for revision 2

Parameter Byte Value Not supported by
First Target 105-106 11
107-112 The torque first target is multiplied by 100 and sent
as an integer
(2 decimals truncated). It is six bytes long and is
specified by six ASCII digits.
Start final angle 113-114 12
115-120 The start final angle is the torque to reach the snug
level. The start final angle is multiplied by 100 and
sent as an integer
(2 decimals truncated). It is six bytes long and is
specified by six ASCII digits.

9836 441 01 Release 1.4

Revision 10 0 (224)
All messages

Table 14 MID 0013 Revision 3

Message part Parameter Byte Value

Header Length 1-4 Variable length
MID 5-8 0013
Revision 9-11 003
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field Pset file version 21-28 N/A
Data field Parameter set data 29-variable See Toyota appendix
Message end Variable NUL

Table 15 MID 0013 Revision 4

Message part Parameter Byte Value
Header Length 1-4 Variable length
MID 5-8 0013
Revision 9-11 004
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field Pset file version 21-28 N/A
Data field Parameter set data 29-variable See Toyota appendix
Message end Variable NUL

5.3.5 MID 0014 Parameter set selected subscribe

A subscription for the parameter set selection. Each time a new parameter set is selected the MID 0015
Parameter set selected is sent to the integrator. Note that the immediate response is MID 0005 Command
accepted and MID 0015 Parameter set selected with the current parameter set number selected.

 Message sent by: Integrator

 Answer: MID 0005 Command accepted and MID 0015 Parameter set selected

44 (224) Release 1.4

Revision 10 9836 4415 01
All messages

Message part Parameter Byte Value

Header Length 1-4 0020
MID 5-8 0014
Revision 9-11 Range: 000-001
No Ack flag 12 0=Ack needed, 1=No ack needed
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field N/A 0 N/A
Message end 21 NUL

5.3.6 MID 0015 Parameter set selected

A new parameter set is selected in the controller. The message includes the ID of the parameter set
selected as well as the date and time of the last change in the parameter set settings. This message is also
sent as an immediate response to MID 0014 Parameter set selected subscribe.
 Message sent by: Controller
 Answer: MID 0016 New parameter set selected acknowledge

Message part Parameter Byte Value

Header Length 1-4 0042
MID 5-8 0015
Revision 9-11 Range: 000-001
No Ack flag 12 0=Ack needed, 1=No ack needed
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field Parameter set ID 21-23 Three ASCII digits, range 000-999
Data field Date of last change in
24-42 19 ASCII characters. YYYY-MM-DD:HH:MM:SS
parameter set setting
Message end 43 NUL

9836 441 01 Release 1.4

Revision 10 0 (224)
All messages

5.3.7 MID 0016 Parameter set selected acknowledge

Acknowledgement for a new parameter set selected.
 Message sent by: Integrator
 Answer: None
Message part Parameter Byte Value
Header Length 1-4 0020
MID 5-8 0016
Revision 9-11 Range: 000-001
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field N/A 0 N/A
Message end 21 NUL

5.3.8 MID 0017 Parameter set selected unsubscribe

Reset the subscription for the parameter set selection.
 Message sent by: Integrator
 Answer: MID 0005 Command accepted or
MID 0004 Command error, Parameter set subscription does not exist

Message part Parameter Byte Value

Header Length 1-4 0020
MID 5-8 0017
Revision 9-11 Range: 000-001
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field N/A 0 N/A
Message end 21 NUL

5.3.9 MID 0018 Select Parameter set

Select a parameter set.
 Message sent by: Integrator
 Answer: MID 0005 Command accepted or
MID 0004 Command error, Parameter set can not be set
 Note!
For an PF3000/4000 with Open protocol version 1.2.1 or later, configured with selector accessory
configured with “confirm” or “confirm with ack” the answer will be Command accepted if it is possible for
the operator to select the Pset via choosing the correct socket on the selector.

46 (224) Release 1.4

Revision 10 9836 4415 01
All messages

The Pset will then be automatically selected when the operator chooses the correct socket from the
selector.
Subscription of the currently selected Pset via MID 0014 will show when the operator has selected the
correct Pset.

Message part Parameter Byte Value

Header Length 1-4 0023
MID 5-8 0018
Revision 9-11 Range: 000-001
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field Parameter set ID 21-23 Three ASCII digits, range 000-999
Message end 24 NUL

5.3.10 MID 0019 Set Parameter set batch size

This message gives the possibility to set the batch size of a parameter set at run time.
 Message sent by: Integrator
 Answer: MID 0005 Command accepted or
MID 0004 Command error, Invalid data

Message part Parameter Byte Value

Header Length 1-4 0025
MID 5-8 0019
Revision 9-11 Range: 000-001
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field, part 1 Parameter set ID 21-23 Three ASCII digits, range 000-999
Data field, part 2 Batch size 24-25 Two ASCII digits, range 00-99
Message end 26 NUL

9836 441 01 Release 1.4

Revision 10 0 (224)
All messages

5.3.11 MID 0020 Reset Parameter set batch counter

This message gives the possibility to reset the batch counter of the running parameter set, at run time.
 Message sent by: Integrator
 Answer: MID 0005 Command accepted or
MID 0004 Command error, Invalid data, or Parameter set not running

Message part Parameter Byte Value

Header Length 1-4 0023
MID 5-8 0020
Revision 9-11 Range: 000-001
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field Parameter set ID 21-23 Three ASCII digits, range 000-999
Message end 24 NUL

5.3.12 MID 0021 Lock at batch done subscribe

A subscription for the Lock at batch done relay status.
 Message sent by: Integrator
 Answer: MID 0005 Command accepted or MID 0004 Command error
 Message: MID 0022 relay status immediately after MID 0005 Command accepted

Message part Parameter Byte Value

Header Length 1-4 0020
MID 5-8 00210
Revision 9-11 Range: 000-001
No Ack flag 12 0=Ack needed, 1=No ack needed
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Message end 21 NUL

5.3.13 MID 0022 Lock at batch done upload

This message gives the relay status for Lock at batch done.
 Message sent by: Controller
 Answer: MID 0023 Lock at batch done upload Ack

48 (224) Release 1.4

Revision 10 9836 4415 01
All messages

Message part Parameter Byte Value

Header Length 1-4 0021
MID 5-8 0022
Revision 9-11 Range: 000-001
No Ack flag 12 0=Ack needed, 1=No ack needed
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field Relay status 21 One ASCII digit, range 0-1
Message end 22 NUL

5.3.14 MID 0023 Lock at batch done upload Acknowledge

This message is an acknowledge to MID 0022.
 Message sent by: Integrator
 Answer: MID 0005 Command accepted

Message part Parameter Byte Value

Header Length 1-4 0020
MID 5-8 0023
Revision 9-11 Range: 000-001
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Message end 21 NUL

5.3.15 MID 0024 Lock at batch done unsubscribe

Reset the subscription for Lock at batch done.
 Message sent by: Integrator
 Answer: MID 0005 Command accepted or MID 0004 Command error

Message part Parameter Byte Value

Header Length 1-4 0020
MID 5-8 0024
Revision 9-11 Range: 000-001
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Message end 21 NUL

9836 441 01 Release 1.4

Revision 10 0 (224)
All messages

5.3.16 MID 0025 Parameter user set download request

This message is reserved for Toyota, see Toyota Appendix.

5.4 Job message

5.4.1 MID 0030 Job ID upload request

This is a request for a transmission of all the valid Job IDs of the controller. The result of this command is
a transmission of all the valid Job IDs.
 Message sent by: Integrator.
 Answer: MID 0031 Job ID upload reply

Message part Parameter Byte Value

Header Length 1-4 0020
MID 5-8 0030
Revision, MID 0031 9-11 Range: 000-002
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field N/A 0 N/A
Message end 21 NUL

5.4.2 MID 0031 Job ID upload reply

The transmission of all the valid Job IDs of the controller. The data field contains the number of valid Jobs
currently present in the controller, and the ID of each Job.
 Message sent by: Controller
 Answer: None
Example revision 1: Job 1 and 2 are present in the controller.

00260031001 020102NUL

Example revision 2: Job 1 and 2 are present in the controller.

00290031002 002001002NUL

50 (224) Release 1.4

Revision 10 9836 4415 01
All messages

Message part Parameter Byte Value

Header Revision 1: 2 + no of Jobs x 2
Length 1-4
Revision 2: 4 + no of Jobs x 4
MID 5-8 0031
Revision 9-11 Range: 000-002
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field Number of Jobs and
21-length See Revisions
the ID of each Job
Message end Length +1 NUL

Table 16 MID 0031 Revision 1

Parameter Byte Value
Number of Jobs 21-22 Two ASCII digits, range 00-99.

Job ID of each Job present 23-length Two ASCII digits for each Job. Range: 00-99.
in the controller

Table 17 MID 0031 Revision 2

58 (224) Release 1.4

Revision 10 9836 4415 01
All messages

Parameter Byte Value Not supported by

39-42 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 bytes long. Four ASCII
characters, range 0000-9999.
Time stamp 43-44 06
45-63 Time stamp for the Job info. The time stamp is 19
bytes long and is specified by 19 ASCII characters
YYYY-MM-DD:HH:MM:SS.

9836 441 01 Release 1.4

Revision 10 0 (224)
All messages

Table 25 MID 0035 Job info Revision 2

Table 26 MID 0035 Job info Revision 3

Parameter Byte Value Not supported by
Job current step 66-67 07
68-70 The number of the step currently executed in the job.
3 bytes long, 3 ASCII characters range 000-999. For
PF4000,PF3000 is zero reported.
Job total number of steps 71-72 08
73-75 The total number of steps in the job. 3 bytes long, 3
ASCII characters range 000-999. For
PF4000,PF3000 is zero reported.
Job step type 76-77 09 PF6000
78-79 Job step type = Two ASCII characters, range 00-99
Batch step = 1
Reserved = 2-6
For PF4000,PF3000 is zero reported.

60 (224) Release 1.4

Revision 10 9836 4415 01
All messages

Table 27 MID 0035 Job info Revision 4

Parameter Byte Value Not supported by
Job ID 21-22 01
23-26 The Job ID is specified by four ASCII characters,
range 0000-9999
Job status 27-28 02
29 The Job batch status is specified by one ASCII
character.
0=Job not completed, 1=Job OK, 2=Job NOK, 3=Job
ABORTED
Job batch mode 301-31 03
32 The Job batch mode is the way to count the
tightening in a Job only the OK or both OK and NOK.
One ASCII character
0= only the OK tightenings are counted
1= both the OK and NOK tightenings are counted
Job batch size 33-34 04 PF6000
35-38 This parameter gives the total number of tightening in
the Job. The Job batch size is four bytes long. Four
ASCII characters, range 0000-9999.
Job batch counter 39-40 05 PF6000
41-44 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 bytes long. Four ASCII
characters, range 0000-9999.
Time stamp 45-46 06
47-65 Time stamp for the Job info. The time stamp is 19
bytes long and is specified by 19 ASCII characters
YYYY-MM-DD:HH:MM:SS.
Job current step 66-67 07
68-70 N/A
Job total number of steps 71-72 08
73-75 N/A
Job step type 76-77 09 PF6000
78-79 N/A
Job tightening status 80-81 10 PF6000
82-83 The Job tightening status is specified by two ASCII
character.
0=JobTight OFF, 1=JobTight OK, 2=JobTight NOK,
3=JobTight ABORTED, 4= JobTight INCREMENTED,
5=JobTight DECREMENTED, 6=JobTight
BYPASSED,
7=JobTight RESET BATCH, 8=JobTight
LOOSENING,
9=JobTight FREE BATCH, 10=JobTight JOB
ABORTED

9836 441 01 Release 1.4

Revision 10 0 (224)
All messages

5.4.7 MID 0036 Job info acknowledge

Acknowledgement of a Job info message.
 Message sent by: Integrator
 Answer: None
Message part Parameter Byte Value
Header Length 1-4 0020
MID 5-8 0036
Revision 9-11 Range: 000-004
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field N/A 0 N/A
Message end 21 NUL

5.4.8 MID 0037 Job info unsubscribe

Reset the subscription for a Job info message.
 Message sent by: Integrator
 Answer: MID 0005 Command accepted or
MID 0004 Command error, Job info subscription does not exist

Message part Parameter Byte Value

Header Length 1-4 0020
MID 5-8 0037
Revision 9-11 Range: 000-004
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field N/A N/A
Message end 21 NUL

5.4.9 MID 0038 Select Job

Message to select Job. If the requested ID is not present in the controller, then the command will not be
performed.
 Message sent by: Integrator
 Answer: MID 0005 Command accepted or
MID 0004 Command error, Job can not be set, or Invalid data

62 (224) Release 1.4

Revision 10 9836 4415 01
All messages

Message part Parameter Byte Value

Header Revision 1: 0022
Length 1-4
Revision 2: 0024
MID 5-8 0038
Revision 9-11 Range: 000-002
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field Job ID 21-length See Revisions
Message end Rev 1: 23
NUL
Rev 2: 25

Table 28 MID 0038 Job ID, revision 1

Parameter Byte Value
Job ID 21-22 The Job ID is specified by two ASCII characters. Range: 00-99

Table 29 MID 0038 Job ID, revision 2

Parameter Byte Value
Job ID 21-24 The Job ID is specified by four ASCII characters.
Range: 0000-9999

9836 441 01 Release 1.4

Revision 10 0 (224)
All messages

5.4.10 MID 0039 Job restart

Job restart message.
 Message sent by: Integrator
 Answer: MID 0005 Command accepted or
MID 0004 Command error, Job not running, or Invalid data

Example: Restart Job 1

00220039 01NUL

Message part Parameter Byte Value

Header Length 1-4 0022
MID 5-8 0039
Revision 9-11 Range: 000-002
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field Job ID 21-Length See Revisions
Message end Length+1 NUL

Table 30 MID 0039 Revision 1

Parameter Byte Value
Job ID 21-22 Two ASCII digits for the Job Id. Range: 00-99.

Table 31 MID 0039 Revision 2

Parameter Byte Value
Job ID 21-24 Four ASCII digits for the JobId. Range: 0000-9999.

64 (224) Release 1.4

Revision 10 9836 4415 01
All messages

5.5 Tool messages

5.5.1 MID 0040 Tool data upload request

A request for some of the data stored in the tool. The result of this command is the transmission of the tool
data.
 Message sent by: Integrator
 Answer: MID 0041 Tool data upload reply

Message part Parameter Byte Value

Header Length 1-4 0020
MID 5-8 0040
Revision, MID 0041 9-11 Range: 000-005
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field N/A N/A
Message end 21 NUL

5.5.2 MID 0041 Tool data upload reply

Upload of tool data from the controller.
 Message sent by: Controller
 Answer: None
Example: Tool data

00810041 01C341212 02548796

032001-05-07:13:24:5404670919 NUL

9836 441 01 Release 1.4

Revision 10 0 (224)
All messages

Message part Parameter Byte Value

Header Length 1-4 Revision 1: 0081
Revision 2: 0156
Revision 2 Ford: 0146
Revision 3: 0180
Revision 4: 0184
Revision 5: 0198
MID 5-8 0041
Revision 9-11 Range: 000-005
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field Tool data 21-length See Revisions
Message end N/A Rev 1: 82
NUL
Rev 2: 157

Table 32 MID 0041 Tool data, revision 1

Parameter Byte Value Not supported by
Tool serial number 21-22 01
23-36 14 ASCII characters
Tool number of tightening 37-38 02
39-48 10 ASCII digits. Max 4294967295
Last calibration date 49-50 03
51-69 19 ASCII characters. YYYY-MM-DD:HH:MM:SS
Controller serial number = 70-71 04
Ford. RBU Serial = Normal
72-81 10 ASCII characters

Table 33 MID 0041 Tool data, additions for revision 2

Parameter Byte Value Not supported by
Calibration value 82-83 05
84-89 The tool calibration value is multiplied by 100 and
sent as an integer (2 decimals truncated). Six ASCII
digits.
Last service date 90-91 06
92-110 YYYY-MM-DD:HH:MM:SS
Tightenings since service 111-112 07
113-122 The number of tightenings since last service is
specified by 10 ASCII digits. Max 4294967295.
Tool type 123-124 08
125-126 The tool type is specified by 2 ASCII digits:
00=No Tool, 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=IRC Offline, 10=STB-
tool, 11=QST-tool, 12=STT-tool, 13=STwrench, 14 =
ES-tool

66 (224) Release 1.4

Revision 10 9836 4415 01
All messages

Motor size 127-128 09 PF6000

129-130 The motor size is specified by 2 ASCII digits,
range 00-99.
00 = no motor, 01-99 = motor size xx in Atlas Copco
nomenclature, or motor size = 10xx in Atlas Copco
nomenclature (certain numbers correspond to 2
different motor sizes, for example 62 for both motor
size 62 and motor size 1062)
Open end data 131-132 10 PF6000
133-135 The open end data is specified by 3 ASCII digits.
The first digit represents the “use open end”: 1=true,
0=false.
The second digit indicates the tightening direction:
0=CW, 1=CCW.
The third digit indicates motor rotation: 0=normal,
1=inverted.
Controller software version 136-137 11
138-156 The software version is specified by 19 ASCII
characters.

Table 34 MID 0041 Tool data, additions for revision 3

Parameter Byte Value Not supported by
Tool max torque 157-158 12
159-164 The tool max toque value is multiplied by 100 and
sent as an integer (2 decimals truncated). Six ASCII
digits.
Gear ratio 165-166 13
167-172 The gear ratio value is multiplied by 100 and sent as
an integer (2 decimals truncated). Six ASCII digits.
Tool full speed 173-174 14
175-180 The tool full speed value is multiplied by 100 and sent
as an integer (2 decimals truncated). Six ASCII digits.

Table 35 MID 0041 Tool data, additions for revision 4

Parameter Byte Value Not supported by
Primary tool 181-182 15 PF6000
183-184 Primary tool. The primary tool is two byte-long and
specified by two ASCII digits.
01=Cable (invalid for IRC-controller), 02=IRC-B,
03=IRC-W

Table 36 MID 0041 Tool data, additions for revision 5

Parameter Byte Value Not supported by
Tool model 185-186 16
187-198 12 ASCII characters with padding at the end of the
string if needed. The padding is done spaces.

9836 441 01 Release 1.4

Revision 10 0 (224)
All messages

5.5.3 MID 0042 Disable tool

Disable tool.
 Message sent by: Integrator
 Answer: MID 0005 Command accepted

Message part Parameter Byte Value

Header Length 1-4 0020
MID 5-8 0042
Revision 9-11 Range: 000-001
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field N/A N/A
Message end 21 NUL

5.5.4 MID 0043 Enable tool

Enable tool.
 Message sent by: Integrator
 Answer: MID 0005 Command accepted

Message part Parameter Byte Value

Header Length 1-4 0020
MID 5-8 0043
Revision 9-11 Range: 000-001
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field N/A N/A
Message end 21 NUL

5.5.5 MID 0044 Disconnect tool request

This command is sent by the integrator in order to request the possibility to disconnect the tool from the
controller. The command is rejected if the tool is currently used.
When the command is accepted the operator can disconnect the tool and replace it (hot swap).
 Message sent by: Integrator

68 (224) Release 1.4

Revision 10 9836 4415 01
All messages

 Answer: MID 0005 Command accepted or

MID 0004 Command error, Tool currently in use

Message part Parameter Byte Value

Header Length 1-4 0020
MID 5-8 0044
Revision 9-11 Range: 000-001
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field N/A N/A
Message end 21 NUL

5.5.6 MID 0045 Set calibration value request

This message is sent by the integrator in order to set the calibration value of the tool.
 Message sent by: Integrator
 Answer: MID 0005 Command accepted or
MID 0004 Command error, Calibration failed

Example: Request for setting a calibration value of 35,5 Nm.

00310045 01102003550NUL

Message part Parameter Byte Value

Header Length 1-4 0031
MID 5-8 0045
Revision 9-11 Range: 000-001
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field Calibration data 21-31 See Revisions
Message end 32 NUL

Table 37 MID 0045 Calibration data

9836 441 01 Release 1.4

Revision 10 0 (224)
All messages

Parameter Byte Value

Calibration value Unit 21-22 01
23 The unit in which the calibration value is sent. The calibration
value unit is one byte long and specified by one ASCII digit.
1=Nm, 2=Lbf.ft, 3=Lbf.In, 4=Kpm
Calibration value 24-25 02
26-31 The calibration value is multiplied by 100 and sent as an integer
(2 decimals truncated). The calibration value is six bytes long and
is specified by six ASCII digits.

5.5.7 MID 0046 Set primary tool request

This message is sent by the integrator in order to set tool data.
Warning 1: this MID requires programming control (see 4.3 Programming control).
Warning 2: the new configuration will not be active until the next controller reboot!
 Message sent by: Integrator
 Answer: MID 0005 Command accepted or
MID 0004 Command error, Programming control not granted
or Invalid data (value not supported by controller)

Example: Request for setting primary tool to Cable.

00240046 0101NUL

Message part Parameter Byte Value

Header Length 1-4 0024
MID 5-8 0046
Revision 9-11 Range: 000-001
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field Primary tool 21-24 See Revisions
Message end 25 NUL

Table 38 MID 0046 Primary tool

70 (224) Release 1.4

Revision 10 9836 4415 01
All messages

Parameter Byte Value

Primary tool 21-22 01
23-24 Primary tool. The primary tool is two byte-long and specified by
two ASCII digits.
01=Cable (invalid for IRC-controller), 02=IRC-B, 03=IRC-W

5.6 VIN Messages

5.6.1 MID 0050 Vehicle ID Number download request

This message is replaced by MID 0150. MID 0050 is still supported.

Used by the integrator to send a VIN number to the controller.

 Message sent by: Integrator
 Answer: MID 0005 Command accepted or
MID 0004 Command error, VIN input source not granted

Message part Parameter Byte Value

Header Length 1-4 0045
MID 5-8 0050
Revision 9-11 Range: 000-001
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field VIN number 21-Length Dynamic with max 25 ASCII characters.
Message end Length + 1 NUL

5.6.2 MID 0051 Vehicle ID Number subscribe

This message is used by the integrator 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 2
 Identifier result part 3
 Identifier result part 4
The identifiers are received by the controller from several input sources, for example serial, Ethernet, or
field bus.

9836 441 01 Release 1.4

Revision 10 0 (224)
All messages

In revision 1 of the MID 0052 Vehicle ID Number, only the VIN number is transmitted. In revision 2, all four
possible identifiers are transmitted.
 Message sent by: Integrator
 Answer: MID 0005 Command accepted or
MID 0004 Command error, VIN subscription already exists

Message part Parameter Byte Value

Header Length 1-4 0020
MID 5-8 0051
Revision MID 0052 9-11 Range: 000-002
No Ack flag 12 0=Ack needed, 1=No ack needed
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field N/A N/A
Message end N/A 21 NUL

5.6.3 MID 0052 Vehicle ID Number

Transmission of the current identifiers of the tightening by the 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
 Identifier result part 3
 Identifier result part 4
The identifiers are received by the controller from several input sources, for example serial, Ethernet, or
field bus.
 Message sent by: Controller
 Answer: MID 0053 Vehicle ID Number acknowledge

Message part Parameter Byte Value

Header Revision 1: 0047
Length 1-4
Revision 2: 0128
MID 5-8 0051
Revision 9-11 Range: 000-002
No Ack flag 12 0=Ack needed, 1=No ack needed
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field Identifier data 21-length See Revisions
Message end Rev 1: 48
N/A NUL
Rev 2: 129

Table 39 MID 0052 Identifier data, revision 1

72 (224) Release 1.4

Revision 10 9836 4415 01
All messages

Parameter Byte Value

VIN number 21-22 01
23-47 The VIN number is 25 bytes long and is specified by 25 ASCII
characters.

Table 40 MID 0052 Identifier data, additions for revision 2

Parameter Byte Value
Identifier result part 2 48-49 02
50-74 The identifier result part 2 is 25 bytes long and is specified by 25
ASCII characters.
Identifier result part 3 75-76 03
77-91 The identifier result part 3 is 25 bytes long and is specified by 25
ASCII characters.
Identifier result part 4 92-93 04
94-128 The identifier result part 4 is 25 bytes long and is specified by 25
ASCII characters.

9836 441 01 Release 1.4

Revision 10 0 (224)
All messages

5.6.4 MID 0053 Vehicle ID Number acknowledge

Vehicle ID Number acknowledge.
 Message sent by: Integrator
 Answer: None
Message part Parameter Byte Value
Header Length 1-4 0020
MID 5-8 0053
Revision 9-11 Range: 000-002
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field N/A N/A
Message end N/A 21 NUL

5.6.5 MID 0054 Vehicle ID Number unsubscribe

Reset the subscription for the current tightening identifiers.
 Message sent by: Integrator
 Answer: MID 0005 Command accepted or
MID 0004 Command error, VIN subscription does not exist

Message part Parameter Byte Value

Header Length 1-4 0020
MID 5-8 0054
Revision 9-11 Range: 000-002
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field N/A N/A
Message end N/A 21 NUL

74 (224) Release 1.4

Revision 10 9836 4415 01
All messages

5.7 Tightening result messages

Table 43 MID 0061 Revision 4

Parameter Byte Value Not supported by
Identifier result part 2 420-421 50 PF6000
422-446 The identifier result part 2 is 25 bytes long and is
specified by 25 ASCII characters.
Identifier result part 3 447-448 51 PF6000
449-473 The identifier result part 3 is 25 bytes long and is
specified by 25 ASCII characters.
Identifier result part 4 474-475 52 PF6000
476-500 The identifier result part 4 is 25 bytes long and is
specified by 25 ASCII characters.

Note : The identifier result parts will only be set if the multiple identifier option has been activated in the
controller.

Table 44 MID 0061 Revision 5

Parameter Byte Value Not supported by
Customer tightening error 501-502 53 PF6000

9836 441 01 Release 1.4

Revision 10 0 (224)
All messages

code 503-506 The customer tightening error code is 4 byte long and
is specified by 4 ASCII characters.

Table 45 MID 0061 Revision 6

Parameter Byte Value Not supported by
Prevail Torque compensate 507-508 54 PF6000
value
509-514 The PVT compensate torque value. It is multiplied by
100 and sent as an integer (2 decimals truncated). It
is six bytes long and specified by six ASCII digits.
Tightening error status 2 515-516 55 PF6000
517-526 Bit field, Tightening error bits 2 shows what went
wrong with the tightening.
Bit 1 Drive deactivated
Bit 2 Tool stall
Bit 3 Drive hot
Bit 4 Gradient monitoring high
Bit 5 Gradient monitoring low
Bit 6 Reaction bar failed
Bit 7-32 Reserved

Table 46 MID 0061 Revision 7

Parameter Byte Value Not supported by
Compensated angle 527-528 56
529-535 Thecompensated angle value is multipied by 100 and
sent as an integer. It is seven bytes long and
specified by seven ASCII digits.
FinalAngleDecimal 536-537 57
538-544 The turning angle value is multiplied by 100 and sent
as an integer (2 decimals truncated). It is seven bytes
long and is specified by seven ASCII digits.

Table 47 MID 0061 Revision 998

Parameter Byte Value Not supported by
Number of stages in 527-528 56 PF6000
multistage 529-530 The total number of stages to be run for this
tightening. It is two bytes long and specified by two
ASCII digits.
Number of stage results 531-532 57 PF6000
533-534 Number of run stages. It is two bytes long and
specified by two ASCII digits.
For each completed stage the final torque and the
final angle are reported.
Stage result 535-536 58 PF6000

84 (224) Release 1.4

Revision 10 9836 4415 01
All messages

Parameter Byte Value Not supported by

537- Byte 1-6: The stage torque value. The torque is
+11 x multiplied by 100 and sent as an integer (2 decimals
number truncated). It is six bytes long and specified by six
of stage ASCII digits.
results Byte 7-11: The turning angle stage value in degrees.
Each turn represents 360 degrees. It is five bytes
long and specified by five ASCII digits. Range:
00000-99999.

Table 48 MID 0061 Light, revision 999

Table 51 MID 0065 Revision 3

Parameter Byte Value Not supported by
Torque values Unit 227-228 29
229 The unit in which the torque values are sent. The
torque values unit is one byte long and is specified by
one ASCII digit.
1=Nm, 2=Lbf.ft, 3=Lbf.In, 4=Kpm
5=Kgf.cm, 6=ozf.in, 7=%
Result type 230-231 30
232-233 The result type is two bytes long and specified by two
ASCII digits.
1=Tightening, 2=Loosening, 3=Batch Increment
4=Batch decrement, 5=Bypass parameter set result
6=Abort Job result, 7=Sync tightening,
8=Reference setup

Table 52 MID 0065 Revision 4

Parameter Byte Value Not supported by
Identifier result part 2 234-235 31
236-260 The identifier result part 2 is 25 bytes long and is
specified by 25 ASCII characters.
Identifier result part 3 261-262 32
263-287 The identifier result part 3 is 25 bytes long and is
specified by 25 ASCII characters.

9836 441 01 Release 1.4

Revision 10 0 (224)
All messages

Parameter Byte Value Not supported by

Identifier result part 4 288-289 33
290-314 The identifier result part 4 is 25 bytes long and is
specified by 25 ASCII characters.

Note : The identifier result parts will only be set if the multiple identifier option has been activated in the
controller.
Table 53 MID 0065 Revision 5
Parameter Byte Value Not supported by
Customer tightening error 315-316 34
code
317-320 The customer tightening error code is 4 byte long and
is specified by 4 ASCII characters.

Table 54 MID 0065 Revision 6

Parameter Byte Value Not supported by
Prevail Torque compensate 321-322 35
value
323-328 The PVT compensate torque value. It is multiplied by
100 and sent as an integer (2 decimals truncated). It
is six bytes long and specified by six ASCII digits.
Tightening error status 2 329-330 36
331-340 Bit field, Tightening error bits 2 shows what went
wrong with the tightening.
Bit 1 Drive deactivated
Bit 2 Tool stall
Bit 3 Drive hot
Bit 4 Gradient monitoring high
Bit 5 Gradient monitoring low
Bit 6 Reaction bar failed
Bit 7-32 Reserved

94 (224) Release 1.4

Revision 10 9836 4415 01
All messages

5.8 Alarm messages

5.8.1 MID 0070 Alarm subscribe

A subscription for the alarms that can appear in the controller.
 Message sent by: Integrator
 Answer: MID 0005 Command accepted or
MID 0004 Command error, Alarm subscription already exists

Message part Parameter Byte Value

Header Length 1-4 0020
MID 5-8 0070
Revision 9-11 Range: 000-002
No Ack flag 12 0=Ack needed, 1=No ack needed
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field N/A N/A
Message end N/A 21 NUL

5.8.2 MID 0071 Alarm

An alarm has appeared in the controller. The current alarm is uploaded from the controller to the
integrator.
 Message sent by: Controller
 Answer: MID 0072 Alarm acknowledge

Example: MID 0071. Alarm E404 appeared on June 12, 2008. The controller and the tool have ready
status.

00530071 01E404021031042008-06-02:10:14:26NUL

9836 441 01 Release 1.4

Revision 10 0 (224)
All messages

Message part Parameter Byte Value

Header Length 1-4 0053
MID 5-8 0071
Revision 9-11 Range: 000-002
No Ack flag 12 0=Ack needed, 1=No ack needed
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field Alarm data 21-53 See Revisions
Message end N/A 54 NUL

Table 55 MID 0071 Alarm data revision 0-1

Parameter Byte Value Not supported by
Error code 21-22 01
23-26 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 27-28 02
29 Controller ready status 1=OK, 0=NOK
Tool ready status 30-31 03
32 Tool ready status 1=OK, 0=NOK
Time 33-34 04
35-53 Time stamp for the alarm. 19 ASCII characters.
YYYY-MM-DD:HH:MM:SS

Table 567 MID 0071 Alarm data revision 2

Parameter Byte Value Not supported by
Error code 21-22 01
23-27 The error code is specified by 5 ASCII characters.
The error code
begins with E and is followed by four digits. Example
E1021.
Controller ready status 28-29 02
30 Controller ready status 1=OK, 0=NOK
Tool ready status 31-32 03
33 Tool ready status 1=OK, 0=NOK
Time 34-35 04
36-54 Time stamp for the alarm. 19 ASCII characters.
YYYY-MM-DD:HH:MM:SS

96 (224) Release 1.4

Revision 10 9836 4415 01
All messages

5.8.3 MID 0072 Alarm acknowledge

Acknowledgement for MID 0071 Alarm.
 Message sent by: Integrator
 Answer: None
Message part Parameter Byte Value
Header Length 1-4 0020
MID 5-8 0072
Revision 9-11 Range: 000-002
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field N/A N/A
Message end N/A 21 NUL

9836 441 01 Release 1.4

Revision 10 0 (224)
All messages

5.8.4 MID 0073 Alarm unsubscribe

Reset the subscription for the controller alarms.
 Message sent by: Integrator
 Answer: MID 0005 Command accepted or
MID 0004 Command error, Alarm subscription does not exist

Message part Parameter Byte Value

Header Length 1-4 0020
MID 5-8 0073
Revision 9-11 Range: 000-002
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field N/A N/A
Message end N/A 21 NUL

5.8.5 MID 0074 Alarm acknowledged on controller

The message is sent by the controller to inform the integrator that the current alarm has been
acknowledged.
 Message sent by: Controller
 Answer: MID 0075 Alarm acknowledged on controller acknowledge

Example: MID 0074 Alarm E406 acknowledged on controller.

00240074 E406NUL

Message part Parameter Byte Value

Header Length 1-4 0024
MID 5-8 0074
Revision 9-11 Range: 000-002
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field Error code 21-24 Four ASCII characters
Message end N/A 25 NUL

98 (224) Release 1.4

Revision 10 9836 4415 01
All messages

5.8.6 MID 0075 Alarm acknowledged on controller acknowledge

Acknowledgement of MID 0074 Alarm acknowledged on controller.
 Message sent by: Integrator
 Answer: None
Message part Parameter Byte Value
Header Length 1-4 0020
MID 5-8 0075
Revision 9-11 Range: 000-002
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field N/A N/A
Message end N/A 21 NUL

5.8.7 MID 0076 Alarm status

The alarm status is sent after an accepted subscription of the controller alarms. This message is used to
inform the integrator that an alarm is active on the controller at subscription time.
 Message sent by: Controller
 Answer: MID 0077 Alarm status acknowledge

Example: MID 0076. Alarm E404 is active, the controller and the tool are ready.

00560076 01102E404031041052008-06-02:10:14:26NUL

Message part Parameter Byte Value

Header Length 1-4 0056
MID 5-8 0076
Revision 9-11 Range: 000-001
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field Alarm status data 21-56 See Revisions
Message end 57 NUL

Table 57 MID 0076 Alarm status data

9836 441 01 Release 1.4

Revision 10 0 (224)
All messages

Parameter Byte Value

Alarm status 21-22 01
23 0=no alarm is active, 1=an alarm is currently active
Error code 24-25 02
26-29 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 30-31 03
32 Controller ready status 1=OK, 0=NOK
Tool ready status 33-34 04
35 Tool ready status 1=OK, 0=NOK
Time 36-37 05
38-56 Time stamp for the alarm. 19 ASCII characters.
YYYY-MM-DD:HH:MM:SS

5.8.8 MID 0077 Alarm status acknowledge

Acknowledgement of MID 0076 Alarm Status.
 Message sent by: Integrator
 Answer: None
Message part Parameter Byte Value
Header Length 1-4 0020
MID 5-8 0077
Revision 9-11 Range 000-001
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field N/A N/A
Message end 21 NUL

5.8.9 MID 0078 Acknowledge alarm remotely on controller

The integrator can remotely acknowledge the current alarm on the controller by sending MID 0078. If no
alarm is currently active when the controller receives the command, the command will be rejected.
 Message sent by: Integrator
 Answer: MID 0005 Command accepted or
MID 0004 Command error, No alarm present or
Invalid data

100 (224) Release 1.4

Revision 10 9836 4415 01
All messages

Message part Parameter Byte Value

Header Length 1-4 0020
MID 5-8 0078
Revision 9-11 Range 000-001
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field N/A N/A
Message end 21 NUL

5.9 Time messages

5.9.1 MID 0080 Read time upload request

Read time request.
 Message sent by: Integrator
 Answer: MID 0081 Read time upload reply

Message part Parameter Byte Value

Header Length 1-4 0020
MID 5-8 0080
Revision, MID 0081 9-11 Range 000-001
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field N/A N/A
Message end 21 NUL

9836 441 01 Release 1.4

Revision 10 0 (224)
All messages

5.9.2 MID 0081 Read time upload reply

Time upload reply from the controller.
 Message sent by: Controller
 Answer: None
Message part Parameter Byte Value
Header Length 1-4 0039
MID 5-8 0081
Revision 9-11 Range 000-001
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field Time 21-39 19 ASCII characters: YYYY-MM-DD:HH:MM:SS
Message end 40 NUL

5.9.3 MID 0082 Set Time

Set the time in the controller.
 Message sent by: Integrator
 Answer: MID 0005 Command accepted

Message part Parameter Byte Value

Header Length 1-4 0039
MID 5-8 0082
Revision 9-11 Range 000-001
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field Time 21-39 19 ASCII characters: YYYY-MM-DD:HH:MM:SS
Message end 40 NUL

102 (224) Release 1.4

Revision 10 9836 4415 01
All messages

5.10 Multi-spindle status messages

The multi-spindle messages for Power Focus are always exchanged with a sync Master. For PowerMACS,
these messages are exchanged with the station using the IP address of the station TC.

5.10.1 MID 0090 Multi-spindle status subscribe

A subscription for the multi-spindle status. For Power Focus, the subscription must be addressed to the
sync Master.
 Message sent by: Integrator
 Answer: MID 0005 Command accepted or
MID 0004 Command error, Controller is not a sync master/station controller, or
Multi-spindle status subscription already exists

Message part Parameter Byte Value

Header Length 1-4 0020
MID 5-8 0090
Revision 9-11 Range 000-001
No Ack flag 12 0=Ack needed, 1=No ack needed
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field N/A N/A
Message end 21 NUL

5.10.2 MID 0091 Multi-spindle status

The multi-spindle status is sent after each sync tightening. The multiple status contains the common status
of the multiple as well as the individual status of each spindle.
 Message sent by: Controller
 Answer: MID 0092 Multi-spindle status acknowledge

Example: Multiple status for two spindles. Common status OK, spindle 1 OK, spindle 2 OK.

00670091 01020200012032001-06-02:10:14:26
041050120102041NUL

9836 441 01 Release 1.4

Revision 10 0 (224)
All messages

Message part Parameter Byte Value

Header Length 1-4 37 bytes + (5 x number of spindles)bytes
MID 5-8 0091
Revision 9-11 Range 000-001
No Ack flag 12 0=Ack needed, 1=No ack needed
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field Multi-spindle data 21-length See Revisions
Message end Length +1 NUL

Table 58 MID 0091 Multi-spindle status data

Parameter Byte Value Not supported by
Number of spindles 21-22 01
23-24 Number of spindles running in the multiple. The
number of spindles is two bytes long and specified by
2 ASCII digits,
range 02-10.
Sync tightening ID 25-26 02
27-31 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. It is specified by five ASCII digits. Range:
00000-65535.
Time 32-33 03
34-52 Time stamp. 19 ASCII characters.
YYYY-MM-DD:HH:MM:SS
Sync overall status 33-54 04
35 The status of all the spindles. OK if the individual
status of each spindle is OK, NOK if at least one
spindle status is NOK. One ASCII digit 1=OK,
0=NOK.
Spindle status 36-37 05
38- 5  number of spindles.
Bytes 1-2: The first two bytes specify the spindle
number in the same order as in the sync list. Range
01-99.
Bytes 3-4: The next two bytes are the channel ID of
the spindle. Range 01-20
Byte 5: The fifth byte is the individual overall status of
the tightening of each spindle 0=NOK, 1=OK

104 (224) Release 1.4

Revision 10 9836 4415 01
All messages

5.10.3 MID 0092 Multi-spindle status acknowledge

Multi-spindle status acknowledge.
 Message sent by: Integrator
 Answer: None
Message part Parameter Byte Value
Header Length 1-4 0020
MID 5-8 0092
Revision 9-11 Range 000-001
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field N/A N/A
Message end 21 NUL

5.10.4 MID 0093 Multi-spindle status unsubscribe

Reset the subscription for the multi-spindle status.
 Message sent by: Integrator
 Answer: MID 0005 Command accepted or
MID 0004 Command error, Multi-spindle status subscription does not exist

Message part Parameter Byte Value

Header Length 1-4 0020
MID 5-8 0093
Revision 9-11 Range 000-001
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field N/A N/A
Message end 21 NUL

9836 441 01 Release 1.4

Revision 10 0 (224)
All messages

5.11 Multi-spindle result messages

The multi-spindle messages for Power Focus are always exchanged with a sync Master. For PowerMACS,
these messages are exchanged with the station using the IP address of the station TC.

5.11.1 MID 0100 Multi-spindle result subscribe

A subscription for the multi-spindle status. For Power Focus, the subscription must be addressed to a sync
Master.
This telegram is also used for a PowerMACS 4000 system running a press instead of a spindle. A press
system only suports revision 4 and higher of the telegram and will answer with MID 0004, MID revision
unsupported if a subscription is made with a lower revision. See also section 6.1 Notes about press
systems.
 Message sent by: Integrator
 Answer: MID 0005 Command accepted or
MID 0004 Command error, Controller is not a sync master/station controller,
Multi-spindle result subscription already exists or MID revision unsupported

Message part Parameter Byte Value

Header Length 1-4 0020
MID 5-8 0100
Revision 9-11 Range: 000-004
No Ack flag 12 0=Ack needed, 1=No ack needed
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field Data No. System Rev ≤1: N/A
Rev 2: 21-30 See Revisions
Send only new data Rev 3 and 4: 21-31
Message end Rev ≤1: 21
Rev 2: 31 NUL
Rev 3 and 4: 32

Table 59 MID 0100 Revision 2, 3 and 4

Parameter Revision Byte Value
Data No. System 2 and 3 21-30 Data No System (see MID 0106) is the number for the cycle data
to rewind to. The first cycle data will be the cycle data after this
point.
If the data is not found, or if the value is 0, rewind will be to oldest
possible cycle data.
Send only new data 3 31 Send only new result data.
One ASCII digit 0=FALSE, 1=TRUE.
If TRUE then only the result data stored after that the subscription
is done is sent to the subscriber. Old result data of the unsent
result will not be sent to the subscriber.
This parameter has higher priorities than “Data No. System”. So if

106 (224) Release 1.4

Revision 10 9836 4415 01
All messages

Parameter Revision Byte Value

this is TRUE, value in byte 21-30 is ignored and not preformed.

5.11.2 MID 0101 Multi-spindle result

The multi-spindle result is sent after each sync tightening and if it is subscribed. The multiple result
contains the common status of the multiple as well as the individual tightening result (torque and angle) of
each spindle.
This telegram is also used for PowerMACS systems running a Press. The layout of the telegram is exactly
the same but some of the fields have slightly different definitions. The fields for Torque are used for Force
values and the fields for Angle are used for Stroke values. A press system always use revsion 4 or higher
of the telegram. See also section 6.1 Notes about press systems.
 Message sent by: Controller
 Answer: MID 0102 Multi-spindle result acknowledge

Message part Parameter Byte Value

Header Rev 1 – 3 :174 bytes+(18xnumber of spindles)bytes
Length 1-4
Rev 4: 174 bytes+(18xnumber of spindles)bytes + 5
MID 5-8 0101
Revision 9-11 Range 000-004
No Ack flag 12 0=Ack needed, 1=No ack needed
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field N/A 21-length See Revisions
Message end Length +1 NUL

Table 60 MID 0101 Multi-spindle result data, Revision 1, 2 and 3

Parameter Byte Value Not supported
by
Number of 21-22 01
spindles
23-24 Number of spindles running in the multiple.
The number of spindles is two bytes long
and specified by 2 ASCII digits,
range 01-50.
VIN Number 25-26 02
27-51 The VIN number is 25 bytes long and is
specified by 25 ASCII characters.
Job ID 52-53 03
54-55 The Job ID is two bytes long and specified
by two ASCII digits. Range: 00-99
Parameter set ID 56-57 04
58-60 The parameter set ID is three bytes long
and specified by three ASCII digits.
Range: 000-999.

9836 441 01 Release 1.4

Revision 10 0 (224)
All messages

Parameter Byte Value Not supported

by
Batch size 61-62 05
63-66 This parameter gives the total number of
tightening in the batch. The batch size is
four bytes long and specified by four ASCII
digits. Range: 0000-9999.
Batch counter 67-68 06
69-72 The batch counter information is four bytes
long specifying and specified by four ASCII
digits. Range: 0000-9999.
Batch status 73-74 07
75 The batch status is specified by one ASCII
character.
0=batch NOK (batch not completed),
1=batch OK,
2=batch not used.
Torque Min limit 76-77 08
78-83 The torque min limit in Nm is multiplied by
100 and sent as an integer (2 decimals
truncated). It is six bytes long and is
specified by six ASCII digits.
Torque Max limit 84-85 09
86-91 The torque max limit in Nm is multiplied by
100 and sent as an integer (2 decimals
truncated). It is six bytes long and is
specified by six ASCII digits.
Torque final target 92-93 10
94-99 The torque final target in Nm is multiplied
by 100 and sent as an integer (2 decimals
truncated). It is six bytes long and is
specified by six ASCII digits.
Angle Min 100-101 11
102-106 The angle min value in degrees. Each turn
represents 360 degrees. It is five bytes
long and specified by five ASCII digits.
Range: 00000-99999.
Angle Max 107-108 12
109-113 The angle max value in degrees. Each
turn represents 360 degrees. It is five
bytes long and specified by five ASCII
digits. Range: 00000-99999.
Final Angle 114-115 13
Target 116-120 The target angle value in degrees. Each
turn represents 360 degrees. It is five
bytes long and specified by five ASCII
digits. Range: 00000-99999.
Date/time of last 121-122 14
change in 123-141 Time stamp for the last change in the
parameter set current parameter set settings. It is 19
settings
bytes long and is specified by 19 ASCII
characters (YYYY-MM-DD:HH:MM:SS).

108 (224) Release 1.4

Revision 10 9836 4415 01
All messages

Parameter Byte Value Not supported

by
Time stamp 142-143 15
144-162 Time stamp. 19 ASCII characters
(YYYY-MM-DD:HH:MM:SS).
Sync tightening ID 163-164 16
165-169 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, range
00000-65535.
Sync overall 170-171 17
status
172 The status of all the spindles. OK if the
individual status of each spindle is OK,
NOK if at least one spindle status is NOK.
One ASCII digit 1=OK, 0=NOK.
Spindle status 173-174 18
175 - 18  number of spindles.
175 + 18 x number
of spindles
Bytes 1-2: Spindle number in the
same order as in the
sync list. Range 01-99.
Bytes 3-4: Channel ID of the
spindle. Range 01-20
Byte 5: Individual overall status
of the tightening of each
spindle 0=NOK, 1=OK
Byte 6: Individual torque status
of each spindle. 0=NOK,
1=OK
Byte 7-12: The torque result of each
spindle. The torque in
Nm is multiplied by 100
and sent as an integer (2
decimals truncated). It is
six bytes long and
specified by six ASCII
digits.
Byte 13: Individual angle status of
each spindle. 0=NOK,
1=OK
Byte 14-18: The turning angle value
in degrees for each
spindle. Each turn
represents 360 degrees.
It is five bytes long and
specified by five ASCII
digits. Range: 00000-
99999.

9836 441 01 Release 1.4

Revision 10 0 (224)
All messages

Note: In a PowerMACS system the unit used for torque measurement depends on the unit setting in the
PowerMACS setup. If the setup use Nm that unit is used in the telegram and if the setup use FtLbs the
telegrams also use FtLbs.

Table 61 MID 0101 Multi-spindle result data, Revision 4

Parameter Byte Value Not
supported
by
Number of spindles or 21-22 01
presses 23-24 Number of spindles or presses
running in the multiple. The
number is two bytes long and
specified by 2 ASCII digits,
range 01-50.
VIN Number 25-26 02
27-51 The VIN number is 25 bytes long
and is specified by 25 ASCII
characters.
Job ID 52-53 03
54-55 The Job ID is two bytes long and
specified by two ASCII digits.
Range: 00-99
Parameter set ID 56-57 04
58-60 The parameter set ID is three
bytes long and specified by three
ASCII digits. Range: 000-999.
Batch size 61-62 05
63-66 This parameter gives the total
number of cycles in the batch.
The batch size is four bytes long
and specified by four ASCII digits.
Range: 0000-9999.
Batch counter 67-68 06
69-72 The batch counter information is
four bytes long specifying and
specified by four ASCII digits.
Range: 0000-9999.
Batch status 73-74 07
75 The batch status is specified by
one ASCII character.
0=batch NOK (batch not
completed), 1=batch OK,
2=batch not used.
Torque or Force Min 76-77 08
limit
78-83 The torque or force min limit, see
description of torque and force
values below.
Torque or Force Max 84-85 09

110 (224) Release 1.4

Revision 10 9836 4415 01
All messages

Parameter Byte Value Not

supported
by
limit 86-91 The torque or force max limit, see
description of torque and force
values below.
Torque of Force final 92-93 10
target 94-99 The torque or force final target,
see description of torque and
force values below.
Angle or Stroke Min 100-101 11
limit 102-106 Angle or stroke min limit, see
description of angle and stroke
values below.
Angle or Stroke Max 107-108 12
limit 109-113 The angle or stroke max limit, see
description of angle and stroke
values below.
Final Angle or Stroke 114-115 13
Target 116-120 The target angle or stroke value,
see description of angle and
stroke values below..
Date/time of last 121-122 14
change in parameter 123-141 Time stamp for the last change in
set settings
the current parameter set
settings. It is 19 bytes long and is
specified by 19 ASCII characters
(YYYY-MM-DD:HH:MM:SS).
Time stamp 142-143 15
144-162 Time stamp. 19 ASCII characters
(YYYY-MM-DD:HH:MM:SS).
Sync tightening ID 163-164 16
165-169 The identity is a unique ID for
each sync result.
Each individual result of each
spindle or press is stamped with
this ID.
The ID is incremented after each
sync cycle. 5 ASCII digits, range
00000-65535.
Sync overall status 170-171 17
172 The status of all the spindles or
presses. OK if the individual
status of each spindle or press is
OK, NOK if at least one of them
have status NOK. One ASCII digit
1=OK, 0=NOK.
Spindle or Press status 173-174 18
175 - 18  number of spindles or
175 + 18 x presses
number of

9836 441 01 Release 1.4

Revision 10 0 (224)
All messages

Parameter Byte Value Not

supported
by
spindles Bytes 1-2: Spindle or press number in the same
order as in the sync list. Range 01-99.
Bytes 3-4: Channel ID of the spindle or press.
Range 01-99
Byte 5: Individual overall status of the cycle of
each spindle or press. 0=NOK, 1=OK
Byte 6: Individual torque or force status of each
spindle or press. 0=NOK, 1=OK
Byte 7-12: The torque or force result of each spindle
or press, see description of torque and
force values below.
Byte 13: Individual angle or stroke status of each
spindle or press. 0=NOK, 1=OK
Byte 14-18: The measued angle or stroke value for
each spindle or press, see description of
angle and stroke values below.
System sub type +2 19
+3 The subtype of the system
sending the data. 3 ASCII digits.
Have the same value as the field
System subtype in MID 0002
Communication start
acknowledge.
For a PowerMACS 4000 system it
can have the following values:
001 = a normal tightening system
002 = a system running presses
instead of spindles, see section
6.1 Notes about press systems

If the system subtype is 002 for

Press all the data above is Force
and Stroke instead of Torque and
Angle

Angle values:
Sent with unit degrees. Each turn represents 360 degrees. It is five bytes long and specified by five ASCII
digits. Range: 00000-99999.

Stroke values:
Sent with unit mm. The value is multiplied by 100 and sent as an integer (2 decimals truncated). It is five
bytes long and is specified by five ASCII digits. Range -99.99 – +999.99 mm sent as -9999 – 99999.

Torque values:
The torque is multiplied by 100 and sent as an integer (2 decimals truncated). It is six bytes long and is
specified by six ASCII digits.The unit is Nm.

Force values:
The force is multiplied by 100 and sent as an integer (2 decimals truncated). It is six bytes long and is
specified by six ASCII digits.The unit is kN.

112 (224) Release 1.4

Revision 10 9836 4415 01
All messages

Note: In revision 4 of the telegram a PowerMACS system always use Nm for the torque measurement,
independent of the setting in the PowerMACS setup.The unit of force measurements in a press system is
always kN.

9836 441 01 Release 1.4

Revision 10 0 (224)
All messages

5.11.3 MID 0102 Multi-spindle result acknowledge

Multi-spindle result acknowledge.
 Message sent by: Integrator
 Answer: None
Message part Parameter Byte Value
Header Length 1-4 0020
MID 5-8 0102
Revision 9-11 Range 000-004
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field N/A N/A
Message end 21 NUL

5.11.4 MID 0103 Multi spindle result unsubscribe

Reset the subscription for the multi spindle result.
 Message sent by: Integrator
 Answer: MID 0005 Command accepted or
MID 0004 Command error, Multi spindle result subscription does not exist

Message part Parameter Byte Value

Header Length 1-4 0020
MID 5-8 0103
Revision 9-11 Range 000-004
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field N/A N/A
Message end 21 NUL

114 (224) Release 1.4

Revision 10 9836 4415 01
All messages

5.12 PowerMACS result data

The PowerMACS result data MIDs allow for step data to be sent, as well as most other available
PowerMACS result variables. The intention is also that it should be easy to add any new result variables
without having to change the protocol specification.
The variables that are sent with Open Protocol are selected in the reporter in PowerMACS. The data
needed for the station messages and for the header part of the Bolt messages are always selected. For most
of the remaining data is possible to select if it should be sent or not. All data is listed in the Appendix
PowerMACS data, names for variable identification
The fields Width and Decimals in the reporter are not accessible; the data is always formatted according to
the message specifications.

5.12.1 MID 0105 Last PowerMACS tightening result data subscribe

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).
This telegram is also used for a PowerMACS 4000 system running a press instead of a spindle. A press
system only suports revision 4 and higher of the telegram and will answer with MID 0004, MID revision
unsupported if a subscription is made with a lower revision. See also section 6.1 Notes about press
systems..
 Message sent by: Integrator
 Answer: MID 0005 Command accepted or
MID 0004 Command error, Subscription already exists or MID revision unsupported
Message part Parameter Byte Value
Header Length 1-4 0020
MID 5-8 0105
Revision 9-11 Range: 000-004
No Ack flag 12 0=Ack needed, 1=No ack needed
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field Data No. System Rev ≤1: N/A
Rev 2: 21-30 See Revisions
Send only new data Rev 3 and 4: 21-31
Message end Rev ≤1: 21
Rev 2: 31 NUL
Rev 3 and 4: 32

9836 441 01 Release 1.4

Revision 10 0 (224)
All messages

Table 62 MID 0105 Revision 2, 3 and 4

Parameter Revision Byte Value
Data No System 2-3 21-30 Data No System (see MID 0106) is the system number of the
cycle data to rewind to.
Two ASCII digits 00.
The first cycle data will be the cycle data after this point.
If the data is not found, or if the value is 0, rewind will be to oldest
possible cycle data.
Send only new data 3 31 Send only new result data.
One ASCII digit 0=FALSE, 1=TRUE.
If TRUE then only the result data stored after that the subscription
is done is sent to the subscriber. Old result data of the unsent
result will not be sent to the subscriber.
This parameter has higher priorities than “Data No System”. So if
this is TRUE, value in byte 21-30 is ignored and not preformed.

5.12.2 MID 0106 Last PowerMACS tightening result Station data

This MID contains the station part and some of the Bolt data of the last result data. After this message has
been sent the integrator selects if it also wants to have the Bolt and step data. If this data is requested, then
the integrator sends the message MID 0108 Last PowerMACS tightening result data acknowledge, with the
parameter Bolt Data set to TRUE. If only the station data is wanted the parameter Bolt Data is set to
FALSE.

This telegram is also used for PowerMACS systems running a Press. The layout of the telegram is exactly
the same but some of the fields have slightly different definitions. The fields for Torque are used for Force
values and the fields for Angle are used for Stroke values. A press system also ues different identifiers for
the optional data on bolt and step level. A press system always use revsion 4 or higher of the telegram. See
also section 6.1 Notes about press systems.
Note: All values that are undefined in the results will be sent as all spaces (ASCII 0x20). This will for
instance happen with the Torque Status if no measuring value for Bolt T was available for the tightening.
 Message sent by: Controller
 Answer: MID 0108 Last PowerMACS tightening result data acknowledge

Message part Parameter Byte Value

Header Length 1-4 Maximum 9999
MID 5-8 0106
Revision 9-11 Range 000-004
No Ack flag 12 0=Ack needed, 1=No ack needed
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field Data 21- See descriptions below
Message end Length +1 NUL

Number of special values +2 23
+2 The total number of special values sent in this message. Range
00-99.
+nx This section is repeated Number of special values times. If
number Number of special values=00, this section is not sent.
of Byte 1-20: Variable name. 20 ASCII characters, see
special
Table 93
values
Byte 21-22: Type: 2 ASCII characters, see Table 92.
Byte 23-34: Length: 2 ASCII digits.
Byte 25- : Value: The value of the variable. The format and
length depend on the parameters Type and Length.

Note 1: All fields with strings are left adjusted and padded with spaces. All numerical fields are right
adjusted and padded with 0‟s.
Note 2: In revision 1, 2 and 3 of the telegram the unit used for torque measurement depends on the unit
setting in the PowerMACS setup. If the setup use Nm that unit is used in the telegram and if the setup use
FtLbs the telegrams also use FtLbs.

Table 64 MID 0106 Last tightening result Station data, revison 4

Parameter Byte Value
Total no of messages 21-22 01
23-24 The total number of messages needed to send all Bolt (object)
data for all Bolts. The rest of the messages are of type MID 0107
Last PowerMACS tightening result Bolt data, once for each
Bolt. They are only sent on request from the integrator. 2 ASCII
digits, range 00-99.
Message number 25-26 02
27-28 This parameter is always 01 as this is the first message.
Data No System 29-30 03
31-40 The Data No system is a unique ID for each result within the
system. 10 ASCII digits, max value is 4294967295.
Station No 41-42 04
43-44 The station number within the PowerMACS system. 2 ASCII
digits, range 01-15.
Station Name 45-46 05
47-66 The station name is 20 bytes long and is specified by 20 ASCII
characters.
Time 67-68 06
69-87 Cycle start time for each cycle sent to the control station. The time
is 19 byte long and is specified by 19 ASCII characters (YYYY-
MM-DD:HH:MM:SS)
Mode No 88-89 07
90-91 The mode number used for the cycle. 2 ASCII digits, range 01-50.
If undefined, empty spaces are sent.
Mode Name 92-93 08
94-113 The name of the mode used for the cycle. Specified by 20 ASCII
characters. If undefined, empty spaces are sent.

9836 441 01 Release 1.4

Revision 10 0 (224)
All messages

Parameter Byte Value

Simple status 114-115 09
116 One byte long and is specified by one ASCII digit („0‟ or „1‟).
0=cycle NOK, 1=cycle OK.
PM Status 117-118 10
119 The status of the tightening (pressing), specified by one ASCII
digit.
0=OK, 1=OKR, 2=NOK, 3=TERMNOK.
Wp. Id 120-121 11
122-161 The Wp. Id is 40 bytes long and is specified by 40 ASCII
characters. If undefined, empty spaces are sent.
Number of Bolts or Objects 162-163 12
164-165 The total number of Bolts or Objects in the tightening, 2 ASCII
digits.
The Bolt/Object part in this message (indicated with double table
border) is repeated Number of Bolt times. The parameter
numbers (13-22) are also repeated.

120 (224) Release 1.4

Revision 10 9836 4415 01
All messages

Parameter Byte Value

Ordinal Bolt or Object +2 13
Number
+2 The ordinal Bolt (object) number, the Bolts in the station are
always numbered from 01 to 50. 2 ASCII digits.
Simple Bolt or Object Status +2 14
+1 Specified by one ASCII digit („0‟ or „1‟). 0=cycle NOK, 1=cycle OK.
Torque or Force Status +2 15
+1 Torque or force status of each Bolt or Object, specified by one
ASCII digit
0=Bolt T Low (Object F Low)
1=Bolt T OK (Object F OK)
2=Bolt T High (Object F High)
If undefined, empty spaces are sent.
Angle or Stroke Status +2 16
+1 Angle or stroke status of each Bolt or Object, specified by one
ASCII digit
0=Bolt A Low (Object S Low)
1=Bolt A OK (Object S OK)
2=Bolt A High (Object S High)
If undefined, empty spaces are sent.
Bolt T or Object F +2 17
+7 Sent as 7 ASCII digits formatted as a float.
The value is sent with 4 decimal places, for example 99.9999 or
-9.9999. If the value is larger than 99 the needed number of
decimals are removed to fit the integer part, i.e. 12345.123 is sent
as “12345.1”.
The unit is Nm in a tighetning system and kN in a press system.
If undefined, empty spaces are sent.
Bolt A or Object S +2 18
+7 Sent as 7 ASCII digits, formatted as a float, see description for
Bolt T.
The unit is degrees in a tightening system and mm in a press
system. If undefined, empty spaces are sent.
Bolt T or Object F High Limit +2 19
+7 Sent as 7 ASCII digits, formatted as a float, see description for
Bolt T. The unit is Nm in a tightening system and kN in a press
system. If undefined, empty spaces are sent.
Bolt T or Object F Low Limit +2 20
+7 Sent as 7 ASCII digits, formatted as a float, see description for
Bolt T. The unit is Nm in a tightening system and kN in a press
system. If undefined, empty spaces are sent.
Bolt A or Object S High +2 21
Limit
+7 Sent as 7 ASCII digits, formatted as a float, see description for
Bolt T.
The unit is degrees in a tightening system and mm in a press
system. If undefined, empty spaces are sent.
Bolt A or Object S Low Limit +2 22
+7 Sent as 7 ASCII digits, formatted as a float, see description for
Bolt T. The unit is degrees in a tightening system and mm in a
press system. If undefined, empty spaces are sent.

9836 441 01 Release 1.4

Revision 10 0 (224)
All messages

Parameter Byte Value

Number of special values +2 23
+2 The total number of special values sent in this message. Range
00-99.
+nx This section is repeated Number of special values times. If
number Number of special values=00, this section is not sent.
of Byte 1-20: Variable name. 20 ASCII characters, see
special Table 93
values
Byte 21-22: Type: 2 ASCII characters, see Table 92.
Byte 23-34: Length: 2 ASCII digits.
Byte 25- : Value: The value of the variable. The format and
length depend on the parameters Type and Length.
System sub type +2 24
+3 The subtype of the system sending the data. 3 ASCII characters.
Have the same value as the filed System subtype in MID 0002
Communication start acknowledge.

For a PowerMACS 4000 system it can have the following values:

001 = a normal tightening system
002 = a system running presses instead of spindles, see section
6.1 Notes about press systems

If the system subtype is 002 for Press all the data above is Force
and Stroke instead of Torque and Angle
.
This part follow directly after the last special value. The byte
numbers vary depending on the number of data sent earlier in the
telegram.

Note 1: All fields with strings are left adjusted and padded with spaces. All numerical fields are right
adjusted and padded with 0‟s.
Note 2: In revision 4 of the telegram the unit used for torque measurement are always Nm, independent of
the unit selection in the PowerMACS setup.The unit used for force measurements in a press system is
always kN.

5.12.3 MID 0107 Last PowerMACS tightening result Bolt data

This message contains the cycle data for one Bolt, both Bolt data and step data. It is only sent if the
acknowledgement of the message MID 0106 Last PowerMACS tightening result station data had the
parameter Bolt Data set to TRUE. The next Bolt data is sent if the acknowledgement has the parameter
Bolt Data set to TRUE.
This telegram is also used for PowerMACS systems running a Press. The layout of the telegram is exactly
the same but some of the fields have slightly different definitions. The fields for Torque are used for Force
values and the fields for Angle are used for Stroke values. A press system also ues different identifiers for
the optional data on bolt and step level.A press system always use revsion 4 or higher of the telegram. See
also section 6.1 Notes about press systems.
Note 1: All values in the fixed part that are undefined in the results will be sent as all spaces (ASCII
0x20). This can happen with the Customer Error Code if this function is not activated.

122 (224) Release 1.4

Revision 10 9836 4415 01
All messages

Note 2: The Bolt results and step results are only sent when the value exists in the result. This means, for
example, that if no high limit is programmed for Peak T, then the value Peak T + will not be sent even if
limits for Peak T are defined in the reporter.
 Message sent by: Controller
 Answer: MID 0108 Last PowerMACS tightening result data acknowledge

Message part Parameter Byte Value

Header Length 1-4 Maximum 9999
MID 5-8 0107
Revision 9-11 Range 000-004
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field User data 21- See Revisions
max 220
Message end N/A Length +1 NUL

Table 65 MID 0107 Last tightening result Bolt data, revision 1,2 and 3
Parameter Byte Value
Total no of messages 21-22 01
23-24 The total number of messages needed to send all Bolt data for all
Bolts, including the message MID 0106 Last PowerMACS
tightening result Station data, sent with the station data. One
message MID 0107 Last PowerMACS tightening result Bolt
data is sent for each Bolt.
Message number 25-26 02
27-28 This number counts from 02 to Total no of messages and is
incremented by 1 for each sent message.
The first Bolt message is message number 02, since MID 0106
Last PowerMACS tightening result Station data is number 01.
2 ASCII digits, range 02-99.
Data No System 29-30 03
31-40 The Data No system is a unique ID for each tightening result
within the system. 10 ASCII digits, max value is 4294967295.
Station No 41-42 04
43-44 The station number within the PowerMACS system. 2 ASCII
digits. Range 01-15.
Time 45-46 05
47-55 Cycle start time for each tightening sent to the control station. The
time is 19 byte long and is specified by 19 ASCII characters
(YYYY-MM-DD:HH:MM:SS)
Bolt number 56-57 06
58-61 The user defined Bolt number. 4 ASCII digits, range 0001-9999.
Bolt name 62-63 07
64-83 The name of the Bolt. 20 ASCII characters.
Program name 84-85 08

9836 441 01 Release 1.4

Revision 10 0 (224)
All messages

Parameter Byte Value

86-105 The name of the program that made the tightening, 20 ASCII
characters.
PM status 106-107 09
108 The status of the tightening specified by one ASCII digit.
0=OK, 1=OKR, 2=NOK, 3=TERMNOK.
Errors 109-110 10
111-160 Error codes from the tightening. Formatted in the same way as
the E1 special variable, see description in section 6.2.4.
Customer error code 161-162 11
163-166 Customer specific error code. 4 ASCII characters. If undefined,
empty spaces are sent.
Number of Bolt results 167-168 12
169-170 The total number of Bolt results in the tightening, 2 ASCII digits.
The Bolt result part in this message is repeated “Number of Bolt
results” times.
171- This section is repeated Number of Bolt results times. If Number
of Bolt results=00, this section is not sent.
Byte 1-20: Variable name: 20 ASCII characters, see 6.2.1.
Byte 21-22: Type of the variable. 2 ASCII characters, I[space] for
integers or F[space] for float.
Byte 23-29: Value. The value is sent as a 7 ASCII digits, and the
format depends on the type.
Type = I, the value is formatted like 9999999 or -
999999
Type = F, the value is sent with 4 decimal places,
i.e. it is formatted like 99.9999 or -9.9999. If the
value is larger than 99 the needed number of
decimals are removed to fit the integer part, i.e.
12345.123 is sent as “12345.1”.
The units for torque measurements are Nm and for
angle measurements degrees.
Number of step results +2 13
+3 The total number of step results in the tightening, 3 ASCII digits.
The step result part in this message is repeated “Number of step
results” times.

124 (224) Release 1.4

Revision 10 9836 4415 01
All messages

Parameter Byte Value

For a PowerMACS 4000 system it can have the following values:

001 = a normal tightening system
002 = a system running presses instead of spindles, see section
6.1 Notes about press systems

If the system subtype is 002 for Press all the data above is Force
and Stroke instead of Torque and Angle

Note 1: All fields with strings are left adjusted and padded with spaces. All numerical fields are right
adjusted and padded with 0‟s.
Note 2: In revision 4 of the telegram the unit used for torque measurement are always Nm, independent of
the unit selection in the PowerMACS setup. The unit used for force measurements in a press system is
always kN.

9836 441 01 Release 1.4

Revision 10 0 (224)
All messages

5.12.4 MID 0108 Last PowerMACS tightening result data

acknowledge
If Bolt Data is set to TRUE the next telegram with Bolt data is sent (if there are any left for this tightening).
Otherwise no more Bolt data is sent for this tightening.
If only the station data is wanted Bolt Data must be set to FALSE in the acknowledgement of MID 0106 Last
PowerMACS tightening result Station data.

 Message sent by: Integrator

 Answer: None
Message part Parameter Byte Value
Header Length 1-4 0021
MID 5-8 0108
Revision 9-11 Range 000-004
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field Bolt data 21 Specifies if Bolt data is requested or not. One ASCII
character: 0=false, 1=true.
Message end 22 NUL

5.12.5 MID 0109 Last PowerMACS tightening result data

unsubscribe
Reset the last PowerMACS tightening result subscription for the rundowns result.
 Message sent by: Integrator
 Answer: MID 0005 Command accepted or
MID 0004 Command error, Subscription does not exist

Message part Parameter Byte Value

Header Length 1-4 0020
MID 5-8 0109
Revision 9-11 Range 000-004
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field N/A N/A
Message end 21 NUL

130 (224) Release 1.4

Revision 10 9836 4415 01
All messages

5.13 User interface messages

5.13.1 MID 0110 Display user text on compact

By sending this message the integrator can display a text on the compact display. The text must be
maximum 4 bytes long.
2
The characters that can be displayed are limited due to the hardware
of the compact display. 1 7 3
Each character must fit into seven segments. This means for
6 4
example that it is not possible to display an M on the compact
display.
5
The text will be displayed until next tightening, new parameter set
or Job selection, or alarm code.

 Message sent by: Integrator

 Answer: MID 0005 Command accepted or
MID 0004 Command error, User text could not be displayed

Message part Parameter Byte Value

Header Length 1-4 0024
MID 5-8 0110
Revision 9-11 Range 000-001
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field User text 21-24 Max four characters, right padded with SPC 0x20
Message end 25 NUL

5.13.2 MID 0111 Display user text on graph

By sending this message 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. If a line is shorter than 25 characters it
must be right padded with blanks (SPC 0x20).
The first line is the text header and is in upper character.
 Message sent by: Integrator
 Answer: MID 0005 Command accepted or
MID 0004 Command error, User text could not be displayed

9836 441 01 Release 1.4

Revision 10 0 (224)
All messages

Message part Parameter Byte Value

Header Length 1-4 0137
MID 5-8 0111
Revision 9-11 Range 000-001
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field N/A 21-137 See Table 67
Message end 138 NUL

Table 67 MID 0110 Graphic text display

Parameter Byte Value
Text Duration 21-22 01
23-26 Time for the text to be displayed, in seconds. Four ASCII digits,
range: 0000-9999
Removal condition 27-28 02
29 0= acknowledge or wait expiration time
1= acknowledge
Line 1 (text header) 30-31 03
32-56 25 ASCII characters
Line 2 57-58 04
59-83 25 ASCII characters
Line 3 84-85 05
86-110 25 ASCII characters
Line 4 111-112 06
113-137 25 ASCII characters

5.13.3 MID 0113 Flash green light on tool

By sending this message the integrator can make the green light on the tool flash. The light on the tool will
flash until the operator pushes the tool trigger.
 Message sent by: Integrator
 Answer: MID 0005 Command accepted

132 (224) Release 1.4

Revision 10 9836 4415 01
All messages

Message part Parameter Byte Value

Header Length 1-4 0020
MID 5-8 0113
Revision 9-11 Range 000-001
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field N/A N/A
Message end 21 NUL

5.14 Job messages, advanced

5.14.1 MID 0120 Job line control info subscribe

A subscription for the Job line control information. A message is sent to the integrator when the Job line
control is started, for alert level 1, for alert level 2, or when the Job is finished before the alert level 2 (Job
line control done).
 Message sent by: Integrator
 Answer: MID 0005 Command accepted or
MID 0004 Command error, Job line control info subscription already exists

Message part Parameter Byte Value

Header Length 1-4 0020
MID 5-8 0120
Revision 9-11 Range 000-001
No Ack flag 12 0=Ack needed, 1=No ack needed
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field N/A N/A
Message end 21 NUL

9836 441 01 Release 1.4

Revision 10 0 (224)
All messages

5.14.2 MID 0121 Job line control started

This message tells the integrator that Job Line control start has been set in the controller.
 Message sent by: Controller
 Answer: MID 0125 Job line control info acknowledged

Message part Parameter Byte Value

Header Length 1-4 0020
MID 5-8 0121
Revision 9-11 Range 000-001
No Ack flag 12 0=Ack needed, 1=No ack needed
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field N/A N/A
Message end 21 NUL

5.14.3 MID 0122 Job line control alert 1

This message tells the integrator that, for example, a car has reached 80% of the station and that the Job
line control alert 1 is set in the controller. Only available after a job has been selected.
 Message sent by: Controller
 Answer: MID 0125 Job line control info acknowledged

Message part Parameter Byte Value

Header Length 1-4 0020
MID 5-8 0122
Revision 9-11 Range 000-001
No Ack flag 12 0=Ack needed, 1=No ack needed
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field N/A N/A
Message end 21 NUL

5.14.4 MID 0123 Job line control alert 2

This message tells the integrator that the Job line control alert 2 is set in the controller. Only available after
a job has been selected.
 Message sent by: Controller
 Answer: MID 0125 Job line control info acknowledged

134 (224) Release 1.4

Revision 10 9836 4415 01
All messages

Message part Parameter Byte Value

Header Length 1-4 0020
MID 5-8 0123
Revision 9-11 Range 000-001
No Ack flag 12 0=Ack needed, 1=No ack needed
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field N/A N/A
Message end 21 NUL

5.14.5 MID 0124 Job line control done

This message tells the integrator that the Job has been completed before the alert level 2 was reached.
 Message sent by: Controller
 Answer: MID 0125 Job line control info acknowledged

Message part Parameter Byte Value

Header Length 1-4 0020
MID 5-8 0124
Revision 9-11 Range 000-001
No Ack flag 12 0=Ack needed, 1=No ack needed
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field N/A N/A
Message end 21 NUL

9836 441 01 Release 1.4

Revision 10 0 (224)
All messages

5.14.6 MID 0125 Job line control info acknowledge

Acknowledgement of Job line control info messages MID 0121, 0122, 0123, and 0124.
 Message sent by: Integrator
 Answer: None
Message part Parameter Byte Value
Header Length 1-4 0020
MID 5-8 0125
Revision 9-11 Range 000-001
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field N/A N/A
Message end 21 NUL

5.14.7 MID 0126 Job line control info unsubscribe

Unsubscribe for the Job line control info messages.
 Message sent by: Integrator
 Answer: MID 0005 Command accepted or
MID 0004 Command error, Job line control info subscription does not exist

Message part Parameter Byte Value

Header Length 1-4 0020
MID 5-8 0126
Revision 9-11 Range 000-001
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field N/A N/A
Message end 21 NUL

5.14.8 MID 0127 Abort Job

Abort the current running Job if there is one.
 Message sent by: Integrator
 Answer: MID 0005 Command accepted

136 (224) Release 1.4

Revision 10 9836 4415 01
All messages

Message part Parameter Byte Value

Header Length 1-4 0020
MID 5-8 0127
Revision 9-11 Range 000-001
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field N/A N/A
Message end 21 NUL

5.14.9 MID 0128 Job batch increment

Increment the Job batch if there is a current running Job.
 Message sent by: Integrator
 Answer: MID 0005 Command accepted

Message part Parameter Byte Value

Header Length 1-4 0020
MID 5-8 0128
Revision 9-11 Range 000-001
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field N/A N/A
Message end 21 NUL

5.14.10 MID 0129 Job batch decrement

Decrement the Job batch if there is a current running Job. Two revisions are available for this MID. The
default revision or revision 1 does not contain any argument and always decrement the last tightening
completed in a Job.
The revision 2 contains two parameters; the channel ID and parameter set ID to be decremented.
The MID is always sent to the cell master/reference.
 Message sent by: Integrator
 Answer: MID 0005 Command accepted or
MID 0004 Command error, Job batch decrement failed (only for MID revision 2)

9836 441 01 Release 1.4

Revision 10 0 (224)
All messages

Message part Parameter Byte Value

Header Revision 1: 0020
Length 1-4
Revision 2: 0029
MID 5-8 0129
Revision 9-11 Range: 000-002
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field Channel ID and
21-length See Revisions
parameter set ID
Message end Rev 1: 21
Rev 2: 30

Table 68 MID 0129 Revision 2

Parameter Byte Value
Channel ID 21-22 01
23-24 The channel ID to be decremented. In case of a cell Job each
controller member has a unique channel ID.
Parameter set ID 25-26 02
27-29 The parameter set ID to be decremented in the Job

5.14.11 MID 0130 Job off

Set the controller in Job off mode or reset the Job off mode.
 Message sent by: Integrator
 Answer: MID 0005 Command accepted

Message part Parameter Byte Value

Header Length 1-4 0021
MID 5-8 0130
Revision 9-11 Range: 000-001
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field Job off status is one byte long and specified by one
Data 21 ASCII digit:
0 = set Job off, 1 = reset Job off
Message end 22 NUL

5.14.12 MID 0131 Set Job line control start

The integrator can set the line control start in the controller with this message.

138 (224) Release 1.4

Revision 10 9836 4415 01
All messages

 Message sent by: Integrator

 Answer: MID 0005 Command accepted

Message part Parameter Byte Value

Header Length 1-4 0020
MID 5-8 0131
Revision 9-11 Range 000-001
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field N/A N/A
Message end 21 NUL

5.14.13 MID 0132 Set Job line alert 1

The integrator can set the line control alert 1 in the controller with this message.
 Message sent by: Integrator
 Answer: MID 0005 Command accepted

Message part Parameter Byte Value

Header Length 1-4 0020
MID 5-8 0132
Revision 9-11 Range 000-001
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field N/A N/A
Message end 21 NUL

5.14.14 MID 0133 Set Job line alert 2

The integrator can set the line control alert 2 in the controller with this message.
 Message sent by: Integrator
 Answer: MID 0005 Command accepted

9836 441 01 Release 1.4

Revision 10 0 (224)
All messages

Message part Parameter Byte Value

Header Length 1-4 0020
MID 5-8 0133
Revision 9-11 Range 000-001
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field N/A N/A
Message end 21 NUL

5.14.15 MID 0140 Execute dynamic Job request

The integrator requests a dynamical Job to be executed i.e. the Job sent from the integrator is immediately
executed (if possible) by the controller but not saved in the memory. A dynamical Job lifetime is the time
for the Job to be executed. If the 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 controller. In such case the number of programs in the Job list is limited.
The following revisions are available for this MID.
 Table 69 MID 0140 Dynamic Job data revision 1

 Table 70 MID 0140 Dynamic Job data revision 999.

Revision 999 is equal to revision 1, but for each program in the Job list (parameter ID 04) the batch
counter can be set. With that revision, it is then possible to send a “dynamic Job” not finally completed
and already begun to the controller. The tightening already performed in the Job is assumed to be OK.
 Message sent by: Integrator
 Answer: MID 0005 Command accepted or
MID 0004 Command error, Not possible to execute dynamic Job

Note: 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).

140 (224) Release 1.4

Revision 10 9836 4415 01
All messages

Message part Parameter Byte Value

Header 71 + no of program x N bytes,
Length 1-4
Revision 1: N=15, revision 2: N=18.
MID 5-8 0140
Revision 9-11 Range: 000-001, 999
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field Dynamic Job data 21-length See Revisions
Message end Length +1 NUL

Table 69 MID 0140 Dynamic Job data revision 1

Parameter Byte Value Not supported by
Job ID 21-22 01
23-24 The Job ID is specified by four ASCII characters.
Range: 0000-9999
Job name 25-26 02
27-51 25 ASCII characters.
Number of parameter sets 52-53 03
54-55 The number of parameter sets in the Job list, defined
by two ASCII characters, range 00-99.
Job list 56-57 04
57- A list of parameter sets (N=value from parameter
(57+ “Number of parameter sets”, max 99).
N x 15) Each parameter set is defined by a number of
parameters separated by “:” and terminated by “;” (15
bytes) according to:
[Channel-ID]:[Program-ID]:[AutoSelect]:[BatchSize]
:[Max Coherent NOK];
Channel ID = two ASCII characters, range 00-99
Program ID = parameter set ID or Multistage ID,
three ASCII characters, range 000-999
Auto Select = One ASCII character, 1 or 0, 1=Auto
Next Change,
BatchSize = Two ASCII characters, range 00-99
Max Coherent NOK = Two ASCII characters, range
00-99
Example: 15:045:0:22:02;
Forced order +2 05
+1 One ASCII character:
0=free order, 1=forced order, 2=free and forced
Lock at Job done +2 06
+1 One ASCII character: 0=No, 1=Yes
Tool loosening +2 07
+1 Tool loosening. One ASCII character.
0=Enable, 1=Disable, 2=Enable only on NOK
tightening

9836 441 01 Release 1.4

Revision 10 0 (224)
All messages

Parameter Byte Value Not supported by

Repeat Job +2 08
+1 One ASCII character: 0=No, 1=Yes
Job batch mode/ +2 09
batch count type
+1 The Job batch mode is the way to count the
tightening in a Job; only the OK or both OK and NOK.
One ASCII character.
0=only the OK tightenings are counted
1=both the OK and NOK tightenings are counted
Batch status at increment / +2 10
bypass +1 Batch status after performing an increment or a
bypass parameter set. One ASCII character: 0=OK,
1=NOK
Decrement batch at OK +2 11
loosening
+1 One ASCII character: 0=No, 1=Yes
Max time for first tightening +2 12
+4 Four ASCII digits, range 0000-9999,
0000=not used
Max time to complete Job +2 13
Max time to complete the entire Job.
Five ASCII digits, range 00000-99999, 00000=not
used
Display result at auto select +2 14
+4 Set the time the tightening result is kept on the
display after selecting next parameter set.
Four ASCII digits, range 0000-9999 seconds
1
0000=not used *
Use line control +2 15
+1 One ASCII character: 0=No, 1=Yes
1
Identifier result part 1 +2 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 +2 17
+1 One ASCII character, save result after increment,
bypass.
0=No, 1=Yes
Reset all identifiers at Job +2 18
done +1 One ASCII character: 0=No, 1=Yes
Reserved +2 19
+1 Reserved for Job repair. One ASCII character: 0=E,
1=G

1
For an PF3000/4000 with Open protocol version 1.2.1 or later, this parameter is overridden and “other” is
always selected.

142 (224) Release 1.4

Revision 10 9836 4415 01
All messages

MID 0140 Dynamic Job data revision 999 is equal to revision 1 except for parameter ID 04, Job list.
Table 70 MID 0140 Dynamic Job data revision 999
Parameter Byte Value Not supported by
See revision 1 21-55 See revision 1
Job list 56-57 04
58- A list with up to 99 parameter sets where each
(58 + parameter set is defined by a number of parameters
N x 18) separated by “:” and terminated by “;” (18 bytes)
according to:
[Channel-ID]:[Program-
ID]:[AutoSelect]:[BatchSize]:[Max Coherent
NOK]:[Batch Counter];
Channel ID = two ASCII characters, range 00-99
Program ID = parameter set ID or Multistage ID,
three ASCII characters, range 000-999
Auto Select = One ASCII character, 1 or 0, 1=Auto
Next Change,
BatchSize = Two ASCII characters, range 00-99
Max Coherent NOK = Two ASCII characters, range
00-99
Batch counter = Two ASCII characters, range 00-99
Ex: 15:045:0:22:02:10;
See revision 1 See revision 1

Revision 10 0 (224)
All messages

5.16 I/O Interface

5.16.1 MID 0200 Set externally controlled relays

By using this message the integrator can control 10 relays (externally control relays). The station can set,
reset the relays or make them flashing.
 Message sent by: Integrator
 Answer: MID 0005 Command accepted

Example: Reset relay 1, set relay 2, reset relay 3, flash relay 4, keep relay 5 as it is, reset relay 6, set relay
7, flash relay 8, keep relay 9 as it is, and reset relay 10.

00300200 0102301230NUL
Message part Parameter Byte Value
Header Length 1-4 0030
MID 5-8 0200
Revision 9-11 Range 000-001
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field Relay status 21-30 See Revisions
Message end 31 NUL

Table 72 MID 0200 Relay status revision 1

Parameter Byte Value Not supported by
Status relay 1 21 Set the status for relay 1. The relay status is one byte
long and specified by 1 ASCII digit. Range 0-3.
0=Off (reset), 1=On (set, fast), 2=Flashing, 3=Keep
current status
Status relay 2 22 Set the status for relay 2. The relay status is one byte
long and specified by 1 ASCII digit. Range 0-3.
0=Off (reset), 1=On (set, fast), 2=Flashing, 3=Keep
current status
Status relay 3 23 Set the status for relay 3. The relay status is one byte
long and specified by 1 ASCII digit. Range 0-3.
0=Off (reset), 1=On (set, fast), 2=Flashing, 3=Keep
current status
Status relay 4 24 Set the status for relay 4. The relay status is one byte
long and specified by 1 ASCII digit. Range 0-3.
0=Off (reset), 1=On (set, fast), 2=Flashing, 3=Keep
current status

148 (224) Release 1.4

Revision 10 9836 4415 01
All messages

Parameter Byte Value Not supported by

Status relay 5 25 Set the status for relay 5. The relay status is one byte
long and specified by 1 ASCII digit. Range 0-3.
0=Off (reset), 1=On (set, fast), 2=Flashing, 3=Keep
current status
Status relay 6 26 Set the status for relay 6. The relay status is one byte
long and specified by 1 ASCII digit. Range 0-3.
0=Off (reset), 1=On (set, fast), 2=Flashing, 3=Keep
current status
Status relay 7 27 Set the status for relay 7. The relay status is one byte
long and specified by 1 ASCII digit. Range 0-3.
0=Off (reset), 1=On (set, fast), 2=Flashing, 3=Keep
current status
Status relay 8 28 Set the status for relay 8. The relay status is one byte
long and specified by 1 ASCII digit. Range 0-3.
0=Off (reset), 1=On (set, fast), 2=Flashing, 3=Keep
current status
Status relay 9 29 Set the status for relay 9. The relay status is one byte
long and specified by 1 ASCII digit. Range 0-3.
0=Off (reset), 1=On (set, fast), 2=Flashing, 3=Keep
current status
Status relay 10 30 Set the status for relay 10. The relay status is one
byte long and specified by 1 ASCII digit. Range 0-3.
0=Off (reset), 1=On (set, fast), 2=Flashing, 3=Keep
current status

5.16.2 MID 0210 Status externally monitored inputs subscribe

By using this message the integrator can set a subscription to monitor the status for the eight externally
monitored digital inputs. After the subscription the station will directly receive a status message and then
every time the status of at least one of the inputs has changed.
 Message sent by: Integrator
 Answer: MID 0005 Command accepted or
MID 0004 Command error,
Status externally monitored inputs subscription already exists or
MID 0211 Status externally monitored inputs.

9836 441 01 Release 1.4

Revision 10 0 (224)
All messages

Message part Parameter Byte Value

Header Length 1-4 0020
MID 5-8 0210
Revision 9-11 Range 000-001
No Ack flag 12 0=Ack needed, 1=No ack needed
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field N/A N/A
Message end 21 NUL

5.16.3 MID 0211 Status externally monitored inputs

Status for the eight externally monitored digital inputs. This message is sent to the subscriber every time
the status of at least one of the inputs has changed.
 Message sent by: Controller
 Answer: MID 0212 Status externally monitored inputs acknowledge

Example:

00280211 00100111NUL

Message part Parameter Byte Value

Header Length 1-4 0028
MID 5-8 0211
Revision 9-11 Range 000-001
No Ack flag 12 0=Ack needed, 1=No ack needed
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field DIG/IN status 21-28 See Revisions
Message end 29 NUL

Table 73 MID 0211 Digital input status revision 1

Parameter Byte Value Not supported by
Status DIG/IN 1 21 The DIG/IN status is one byte long and specified by 1
ASCII digits. Range 0-1. 0=Off, 1=On
Status DIG/IN 2 22 The DIG/IN status is one byte long and specified by 1
ASCII digits. Range 0-1. 0=Off, 1=On
Status DIG/IN 3 23 The DIG/IN status is one byte long and specified by 1
ASCII digits. Range 0-1. 0=Off, 1=On
Status DIG/IN 4 24 The DIG/IN status is one byte long and specified by 1
ASCII digits. Range 0-1. 0=Off, 1=On

150 (224) Release 1.4

Revision 10 9836 4415 01
All messages

Parameter Byte Value Not supported by

Status DIG/IN 5 25 The DIG/IN status is one byte long and specified by 1
ASCII digits. Range 0-1. 0=Off, 1=On
Status DIG/IN 6 26 The DIG/IN status is one byte long and specified by 1
ASCII digits. Range 0-1. 0=Off, 1=On
Status DIG/IN 7 27 The DIG/IN status is one byte long and specified by 1
ASCII digits. Range 0-1. 0=Off, 1=On
Status DIG/IN 8 28 The DIG/IN status is one byte long and specified by 1
ASCII digits. Range 0-1. 0=Off, 1=On

5.16.4 MID 0212 Status externally monitored inputs acknowledge

Acknowledgement for the message status Externally monitored inputs upload.
 Message sent by: Integrator
 Answer: None

Message part Parameter Byte Value

Header Length 1-4 0020
MID 5-8 0212
Revision 9-11 Range 000-001
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field N/A N/A
Message end 21 NUL

5.16.5 MID 0213 Status externally monitored inputs unsubscribe

Unsubscribe for the MID 0211 Status externally monitored inputs.
 Message sent by: Integrator
 Answer: MID 0005 Command accepted or
MID 0004 Command error,
Status externally monitored inputs subscription does not exist

9836 441 01 Release 1.4

Revision 10 0 (224)
All messages

Message part Parameter Byte Value

Header Length 1-4 0020
MID 5-8 0213
Revision 9-11 Range 000-001
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field N/A N/A
Message end 21 NUL

5.16.6 MID 0214 IO device status request

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.
 Message sent by: Integrator
 Answer: MID 0215 IO device status or
MID 0004 Command error,
Faulty IO device ID, or IO device not connected
Message part Parameter Byte Value
Header Length 1-4 0022
MID 5-8 0214
Revision, MID 0215 9-11 Range: 000-002
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field Two ASCII characters (00-15) 00=internal device,
Device number 21-22
01-15=I/O expanders
Message end 23 NUL

5.16.7 MID 0215 IO device status reply

This message is sent as an answer to the MID 0214 IO device status request.
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.
 Message sent by: Controller
 Answer: None

152 (224) Release 1.4

Revision 10 9836 4415 01
All messages

Message part Parameter Byte Value

Header Revision 1: 0092
Length 1-4 Revision 2: depends on the number of relays and
digital inputs
MID 5-8 0214
Revision 9-11 Range: 000-002
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field Device number 21- See Revisions
Message end length +1 NUL

See Table 76 for interpretation of relay numbers and digital input numbers. Note that one or two zeros
have to be added in front of the numbers in the list in this MID. For example relay number 13 Job NOK
must be entered as 013.
Table 74 MID 0215 Revision 1
Parameter Byte Value
IO device ID 21-22 01
23-24 The IO device ID specified with two ASCII characters. Range: 00-
99. 00=internal device, 01-15=I/O expanders.
Relay list 25-26 02
27-58 A list of 8 relays for the current device ID. Each relay is specified
by four bytes.
Byte 1-3: Relay number, three ASCII characters, range 000-999
Byte 4: Relay status specified by one ASCII character;
0=reset, 1=set.
Digital Input list 59-60 03
61-92 A list of 8 digital inputs for the current device ID. Each digital input
is specified by four bytes.
Byte 1-3: Digital input number, three ASCII characters,
range 000-999
Byte 4: Digital input status specified by one ASCII character.
0=Low, 1=High

Table 75 MID 0215 Revision 2

Parameter Byte Value
IO device ID 21-22 01
23-24 The IO device number specified with two ASCII characters.
Range: 00-99. 00=internal device, 01-15=I/O expanders.
Number of relays 25-26 02
27-28 Number of relays present on the I/O-device.

9836 441 01 Release 1.4

Revision 10 0 (224)
All messages

Parameter Byte Value

Relay list 29-30 03
2
31- X A list of relays for the current device ID. Each relay is specified by
four bytes.
Byte 1-3: Relay number, three ASCII characters, range 000-999
Byte 4: Relay status specified by one ASCII character;
0=reset, 1=set.
Number of digital inputs X+1-X+2 04
X+3-X+4 Number of digital inputs present on the I/O-device.
Digital Input list X+5-X+6 05
3
X+7-Y A list of digital inputs for the current device ID. Each digital input is
specified by four bytes.
Byte 1-3: Digital input number, three ASCII characters,
range 000-999
Byte 4: Digital input status specified by one ASCII character.
0=Low, 1=High

Table 76 MID 0215 Relay number

Message part Parameter Byte Value

Header Length 1-4 0023
MID 5-8 0224
Revision 9-11 Range 000-001
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field Digital input function 21-23 Three ASCII digits, see Error! Reference source
number not found. and add 0 before the number in the list.
Message end N/A 24 NUL

5.16.17 MID 0225 Reset digital input function

Reset the digital input function with the digital input number. The digital input function numbers are
defined in Error! Reference source not found..
This MID will only affect the digital input functions of tracking type. The digital input functions with the
type flank cannot be reset (for example reset the reset batch digital input function will have no effect).
 Message sent by: Integrator
 Answer: MID 0005 Command accepted or
MID 0004 Command error, Invalid data

Message part Parameter Byte Value

Header Length 1-4 0023
MID 5-8 0225
Revision 9-11 Range 000-001
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field Digital input function 21-23 Three ASCII digits, see Error! Reference source
number not found. and add 0 before the number in the list.
Message end N/A 24 NUL

9836 441 01 Release 1.4

Revision 10 0 (224)
All messages

5.17 PLC user data messages

The automatic/manual mode messages are only available for PowerMACS. This section includes a
description on how the PLC user data messages are defined.
Data sent or received with a message is defined as a string of ASCII HEX characters. A string could look
like “11223344” where the first byte (counted from the start of the PLC area) shall be given the value
0x11 and the second 0x22 and so on. When declaring variables in the PLC that are of width larger than
one byte they are stored in BIG ENDIAN ordering.
Example 1: In the PLC, variables for input and output are setup accordingly:
Table 80 Example 1 input
PLC Variable Addr Data Type
IN_1 %IB 13000 Byte
IN_2 %IW 13001-13002 16Bit Word (int)
IN_3 %ID 13003-13006 32Bit Word (dint)
IN_4 %IB 13007 Byte
Table 81 Example 1 output
PLC Variable Addr Data Type
OUT_1 %QB 13000 Byte
OUT_2 %QW 13001-13002 16Bit Word (int)
OUT_3 %QD 13003-13006 32Bit Word (dint)
OUT_4 %QB 13007 Byte

Both areas occupy 8 bytes each (1 + 2 + 4 +1) and these bytes are assigned to the variables in the
following way:
Input:
13000 13001 13002 13003 13004 13005 13006 13007
IN_1 IN_2 IN_2 IN_3 IN_3 IN_3 IN_3 IN_4
1:st byte in 1:st byte in 2:nd byte in 1:st byte in 2:nd byte in 3:d byte in 4:th byte in 1:st byte in
variable variable variable variable variable variable variable variable

Output:
13000 13001 13002 13003 13004 13005 13006 13007
OUT_1 OUT_2 OUT_2 OUT_3 OUT_3 OUT_3 OUT_3 OUT_4
1:st byte in 1:st byte in 2:nd byte in 1:st byte in 2:nd byte in 3:d byte in 4:th byte in 1:st byte in
variable variable variable variable variable variable variable variable

Example Cases:
The text within quotation marks denotes the data part of the telegram in ASCII HEX.
Case 1: Write to PLC with MID 0240 User data download message.
1. Write variable IN_1 with the value 134 (0x86 ). All other variables zero. “8600000000000000”.
2. Write variable IN_2 with the value 37567 (0x92bf). All other variables zero. “0092bf0000000000”.
3. Write variable IN_3 with value 2000345 (0x1e85d9). All other variables zero. “000000001e85d900”.

170 (224) Release 1.4

Revision 10 9836 4415 01
All messages

4. Write variable IN_3 with value 3000134000 (0xb2d26970). All other variables zero.
“000000b2d2697000”.
5. Write variable IN_4 with value 255 (0xff). All other variables zero. “00000000000000ff”.

Case 2: Read values of PLC variable from MID 0240 User data message.
1. The data“7834fece5678a2b7” is received.
 OUT_1 reads 120 (0x78)
 OUT_2 reads 13566 (0x34fe)
 OUT_3 reads 3461773474 (0xce5678a2)
 OUT_4 reads 183 (0xb7)

5.17.1 MID 0240 User data download

Used by the integrator to send user data input to the PLC.
 Message sent by: Integrator
 Answer: MID 0005 Command accepted or
MID 0004 Command error, Invalid data, or
Controller is not a sync master/station controller

00280240 12345678NUL

Message part Parameter Byte Value

Header Length 1-4 Maximum 0220
MID 5-8 0240
Revision 9-11 Range 000-001
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field User data 21- Minimum 2 and maximum 200 ASCII characters.
max 220
Message end N/A Length +1 NUL

9836 441 01 Release 1.4

Revision 10 0 (224)
All messages

5.17.2 MID 0241 User data subscribe

Subscribe for user data. This command will activate the MID 0242 User data message to be sent when a
change in the user data output has been detected.
 Message sent by: Integrator
 Answer: MID 0005 Command accepted or
MID 0004 Command error, Subscription already exists, or
Controller is not a sync master/station controller

Message part Parameter Byte Value

Header Length 1-4 0020
MID 5-8 0241
Revision 9-11 Range 000-001
No Ack flag 12 0=Ack needed, 1=No ack needed
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field N/A N/A
Message end N/A 21 NUL

5.17.3 MID 0242 User data

This message is sent by the controller to the integrator when a change has been detected in the user data.
 Message sent by: Controller
 Answer: MID 0243 User data acknowledge

Message part Parameter Byte Value

Header Length 1-4 Maximum 0220
MID 5-8 0242
Revision 9-11 Range 000-001
No Ack flag 12 0=Ack needed, 1=No ack needed
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field User data 21- Minimum 2 and maximum 200 ASCII characters.
max 220 See MID 0240 for a description.
Message end N/A Length +1 NUL

172 (224) Release 1.4

Revision 10 9836 4415 01
All messages

5.17.4 MID 0243 User data acknowledge

Acknowledgement of user data.
 Message sent by: Integrator
 Answer: None
Message part Parameter Byte Value
Header Length 1-4 0020
MID 5-8 0243
Revision 9-11 Range 000-001
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field N/A N/A
Message end N/A 21 NUL

5.17.5 MID 0244 User data unsubscribe

Unsubscribe for the user data.
 Message sent by: Integrator
 Answer: MID 0005 Command accepted or
MID 0004 Command error, Subscription already exists

Message part Parameter Byte Value

Header Length 1-4 0020
MID 5-8 0244
Revision 9-11 Range 000-001
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field N/A N/A
Message end N/A 21 NUL

9836 441 01 Release 1.4

Revision 10 0 (224)
All messages

5.18 Selector messages

5.18.1 MID 0250 Selector socket info subscribe

Subscribe for the socket information of all socket selectors (connected to the controller). After
subscription, every time a socket is lifted or put back, MID 0251 is sent to the subscriber with the device
ID of the selector and the current status of each one of the sockets, lifted or not.
 Message sent by: Integrator
 Answer: MID 0005 Command accepted or
MID 0004 Command error, The selector socket info subscription already exists

Message part Parameter Byte Value

Header Length 1-4 0020
MID 5-8 0250
Revision 9-11 Range 000-001
No Ack flag 12 0=Ack needed, 1=No ack needed
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field N/A 21-23 N/A
Message end N/A 21 NUL

5.18.2 MID 0251 Selector socket info

This message is sent each time a socket is lifted or put back in position. This MID contains the device ID
of the selector the information is coming from, the number of sockets of the selector device, and the
current status of each socket (lifted or not lifted).
 Message sent by: Controller
 Answer: MID 0252, Selector socket info acknowledge

Message part Parameter Byte Value

Header Length 1-4 10 + 1 x number of sockets, bytes
MID 5-8 0251
Revision 9-11 Range 000-001
No Ack flag 12 0=Ack needed, 1=No ack needed
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field Socket data 21-length See Table 82
Message end N/A Length +1 NUL

174 (224) Release 1.4

Revision 10 9836 4415 01
All messages

Table 82 MID 0251 Selector socket data

Parameter Byte Value Support
Device ID 21-22 01
23-24 Two ASCII digits corresponding to the selector device
ID.
Range 00-99
Number of sockets 25-26 02
27-28 Two ASCII digits representing the selector‟s number
of sockets. Range 00-99
Socket status 29-30 03
31- 0=socket not lifted
(+1× 1=socket lifted
Number
of
sockets)

5.18.3 MID 0252 Selector socket info acknowledge

Acknowledgement of the MID 0251 Selector socket info.
 Message sent by: Integrator
 Answer: None
Message part Parameter Byte Value
Header Length 1-4 0020
MID 5-8 0252
Revision 9-11 Range 000-001
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field N/A N/A
Message end N/A 21 NUL

5.18.4 MID 0253 Selector socket info unsubscribe

Unsubscribe for the selector socket info. The subscription is reset for all selector devices.
 Message sent by: Integrator
 Answer: MID 0005 Command accepted or
MID 0004 Command error, The selector socket info subscription does not exist

9836 441 01 Release 1.4

Revision 10 0 (224)
All messages

Message part Parameter Byte Value

Header Length 1-4 0020
MID 5-8 0253
Revision 9-11 Range 000-001
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field N/A N/A
Message end N/A 21 NUL

5.18.5 MID 0254 Selector control green lights

This message controls the selector green lights. The green light can be set (steady), reset (off) or flash. A
command must be sent for each one of the selector positions (1-8).
Note: This MID only works when the selector is put in external controlled mode and this is only possible
when the selector is loaded with software 1.20 or later.
 Message sent by: Integrator
 Answer: MID 0005 Command accepted or
MID 0004 Command error, Faulty IO device ID

Message part Parameter Byte Value

Header Length 1-4 0034
MID 5-8 0254
Revision 9-11 Range 000-001
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field Green lights 21-34 See Table 83
Message end N/A 35 NUL

Table 83 MID 0254 Selector green lights

Parameter Byte Value
Device ID 21-22 01
23-24 Two ASCII digits corresponding to the selector device ID.
Range 00-99
Green light 25-26 02
Command selector position 27-34 For each green light, selector position 1-8.
1-8 0=Off, 1=steady, 2=flashing

176 (224) Release 1.4

Revision 10 9836 4415 01
All messages

5.18.6 MID 0255 Selector control red lights

This message controls the selector red lights. The red light can be set (steady), reset (off) or flash. A
command must be sent for each one of the selector positions (1-8).
Note: This MID only works when the selector is put in external controlled mode and this is only possible
when the selector is loaded with software 1.20 or later.
 Message sent by: Integrator
 Answer: MID 0005 Command accepted or
MID 0004 Command error, Faulty IO device ID

Message part Parameter Byte Value

Header Length 1-4 0034
MID 5-8 0255
Revision 9-11 Range 000-001
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field Red lights 21-34 See Table 84
Message end N/A 35 NUL

Table 84 MID 0254 Selector red lights

Parameter Byte Value
Device ID 21-22 01
23-24 Two ASCII digits corresponding to the selector device ID.
Range 00-99
Red light 25-26 02
Command selector position 27-34 For each red light, selector position 1-8.
1-8 0=Off, 1=steady, 2=flashing

9836 441 01 Release 1.4

Revision 10 0 (224)
All messages

5.19 Tool Location System messages

This message group is only applicable if using the Tool Location System (TLS) system.

5.19.1 MID 0260 Tool tag ID request

Used by the integrator to request Tool tag ID information.
 Message sent by: Integrator
 Answer: MID 0262 Tool tag ID or
MID 0004 Command error, Tool tag ID unknown or MID revision unsupported.

Message part Parameter Byte Value

Header Length 1-4 0020
MID 5-8 0260
Revision 9-11 Range 000-001
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field N/A N/A N/A
Message end 21 NUL

5.19.2 MID 0261 Tool tag ID subscribe

Used by the integrator to order a Tool tag ID subscription from the controller.
 Message sent by: Integrator
 Answer: MID 0005 Command accepted or
MID 0004 Command error,
Tool tag ID unknown , Tool tag ID subscription already exist or
MID revision unsupported.

178 (224) Release 1.4

Revision 10 9836 4415 01
All messages

Message part Parameter Byte Value

Header Length 1-4 0020
MID 5-8 0261
Revision 9-11 Range 000-001
No Ack flag 12 0=Ack needed, 1=No ack needed
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field N/A N/A N/A
Message end 21 NUL

5.19.3 MID 0262 Tool tag ID

Used by the controller to send a Tool tag ID to the integrator.
 Message sent by: Controller
 Answer: MID 0263 Tool tag ID acknowledge
 None
Message part Parameter Byte Value
Header Length 1-4 Rev 1: 0030
MID 5-8 0262
Revision 9-11 Range 000-001
No Ack flag 12 0=Ack needed, 1=No ack needed
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field Tool Tag Id Rev 1: 21-30 Rev 1: Table 85
Message end Rev 1: 31 NUL

Table 85 MID 0262 TLS ST Tool Tag Identity

Parameter Byte Value
Tool tag ID 21-22 01
23-30 Tool tag ID.
The ID value has a hexadecimal representation wich should be
interpreted as in the following example.
Example 3200078D -> 50-0-7-141

5.19.4 MID 0263 Tool tag ID acknowledge

Acknowledgement of MID 0262 Tool tag ID.
 Message sent by: Integrator
 Answer: None

9836 441 01 Release 1.4

Revision 10 0 (224)
All messages

Message part Parameter Byte Value

Header Length 1-4 0020
MID 5-8 0263
Revision 9-11 Range 000-001
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field N/A N/A N/A
Message end 21 NUL

5.19.5 MID 0264 Tool tag ID unsubscribe

Used by the integrator to send a Tool tag ID unsubscription to the controller.
 Message sent by: Integrator
 Answer: MID 0005 Command accepted or
MID 0004 Command error,
Tool tag ID subscription does not exist or
MID revision unsupported.

Message part Parameter Byte Value

Header Length 1-4 0020
MID 5-8 0264
Revision 9-11 Range 000-001
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field N/A N/A N/A
Message end 21 NUL

180 (224) Release 1.4

Revision 10 9836 4415 01
All messages

5.20 Controller messages

5.20.1 MID 0270 Controller reboot request

This message causes the controller to reboot after it has accepted the command.
Warning 1: this MID requires programming control (see 4.3 Programming control).
Warning 2: the connection will be lost and will need to be reestablished after controller reboot!
 Message sent by: Integrator
 Answer: MID 0005 Command accepted or
MID 0004 Command error, Programming control not granted

Example: Request for controller reboot.

00200270 NUL

Message part Parameter Byte Value

Header Length 1-4 0020
MID 5-8 0270
Revision of MID 0270 9-11 Range 000-001
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field N/A 0 N/A
Message end 21 NUL

5.21 Statistic messages

5.21.1 MID 0300 Histogram upload request

Request to upload a histogram from the controller for a certain parameter set.
The histogram is calculated with all the tightening results currently present in the controller‟s memory and
within the statistic acceptance window (statistic min and max limits) for the requested parameter set.

9836 441 01 Release 1.4

Revision 10 0 (224)
All messages

 Message sent by: Integrator

 Answer: MID 0301, Histogram upload reply, or
MID 0004 Command error, No histogram available or
Invalid data

Message part Parameter Byte Value

Header Length 1-4 0029
MID 5-8 0300
Revision, MID 0301 9-11 Range 000-001
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field Parameter set and 21-29 See Table 86
histogram type
Message end N/A 30 NUL

Example: Upload torque histogram for parameter set 1.

002903000000 010010200NUL

Table 86 MID 0300 Parameter set and histogram type

5.21.2 MID 0301 Histogram upload reply

Histogram upload reply for the requested parameter set and for the requested histogram type. The
histogram uploaded is made of 9 bars according to Figure 14 Histogram example.
 Message sent by: Controller
 Answer: None

182 (224) Release 1.4

Revision 10 9836 4415 01
All messages

Figure 14 Histogram example

Message part Parameter Byte Value

Header Length 1-4 0107
MID 5-8 0301
Revision 9-11 Range 000-001
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field Histogram data 21-107 See Table 87Table 87 MID 0301
Message end N/A 108 NUL

Table 87 MID 0301 Histogram data

Parameter Byte Value
Parameter set ID 21-22 01
23-25 The parameter set ID of the requested histogram. Three ASCII
digits. Range 000-999
Histogram type 26-27 02
28-29 Histogram type is two bytes long and is specified by two ASCII
digits.
00=Torque
01=Angle
02=Current
03=Prevail torque
04=Self Tap
05=Rundown angle
Sigma histogram 30-31 03
32-37 Sigma for all the tightening 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 bytes long and is specified by
six ASCII digits. Range 000000-999999.
Mean value histogram 38-39 04
(X-bar) 40-45 The mean value for all the tightening results (within the 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
bytes long and is specified by six ASCII digits.
Range 000000-999999.
Class range 46-47 05

9836 441 01 Release 1.4

Revision 10 0 (224)
All messages

Parameter Byte Value

48-53 The class range is equal to 6 sigma / 9.
The class range is multiplied by 100 and sent as an integer (2
decimals truncated). Mean value is six bytes long and is specified
by six ASCII digits. Range 000000-999999.
Bar 1 54-55 06
56-59 Number of tightening in bar 1, four bytes long and specified as
four ASCII digits. Range 0000-9999.
Bar 2 60-61 07
62-65 Number of tightening in bar 2, four bytes long and specified as
four ASCII digits. Range 0000-9999.
66-67 08
Bar 3 68-71 Number of tightening in bar 3, four bytes long and specified as
four ASCII digits. Range 0000-9999.
72-73 09
Bar 4 74-77 Number of tightening in bar 4, four bytes long and specified as
four ASCII digits. Range 0000-9999.
78-79 10
Bar 5 80-83 Number of tightening in bar 5, four bytes long and specified as
four ASCII digits. Range 0000-9999.
84-85 11
Bar 6 86-89 Number of tightening in bar 6, four bytes long and specified as
four ASCII digits. Range 0000-9999.
90-91 12
Bar 7 92-95 Number of tightening in bar 7, four bytes long and specified as
four ASCII digits. Range 0000-9999.
96-97 13
Bar 8 98-101 Number of tightening in bar 8, four bytes long and specified as
four ASCII digits. Range 0000-9999.
102-103 14
Bar 9 104-107 Number of tightening in bar 9, four bytes long and specified as
four ASCII digits. Range 0000-9999.

184 (224) Release 1.4

Revision 10 9836 4415 01
All messages

5.22 Automatic/Manual mode messages

The automatic/manual mode messages are only available for PowerMACS while automatic disable
settings request (MID 410) and reply (MID 411) messages exists both in Power Macs and the Power
Focus controllers.

5.22.1 MID 0400 Automatic/Manual mode subscribe

A subscription for Automatic/Manual mode. When the mode changes the MID 0401 Automatic/Manual
mode upload is sent to the integrator.

After a successful subscription the message MID 0401 Automatic/Manual mode upload with the current
mode status is sent to the integrator.
 Message sent by: Integrator
 Answer: MID 0005 Command accepted or
MID 0004 Command error, Automatic/Manual mode subscribe already exists

Message part Parameter Byte Value

Header Length 1-4 0020
MID 5-8 0400
Revision 9-11 Range 000-001
No Ack flag 12 0=Ack needed, 1=No ack needed
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field N/A N/A
Message end N/A 21 NUL

5.22.2 MID 0401 Automatic/Manual mode

The operation mode in the controller has changed. The message includes the new operational mode of the
controller.
 Message sent by: Controller
 Answer: MID 0402 Automatic/Manual mode acknowledge

9836 441 01 Release 1.4

Revision 10 0 (224)
All messages

Message part Parameter Byte Value

Header Length 1-4 0021
MID 5-8 0401
Revision 9-11 Range 000-001
No Ack flag 12 0=Ack needed, 1=No ack needed
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field Manual/Automatic 21 One ASCII digit.
mode 0=Automatic mode, 1=Manual mode
Message end N/A 22 NUL

5.22.3 MID 0402 Automatic/Manual mode acknowledge

Acknowledgement of automatic/manual mode upload.
 Message sent by: Integrator
 Answer: None
Message part Parameter Byte Value
Header Length 1-4 0020
MID 5-8 0402
Revision 9-11 Range 000-001
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field N/A N/A
Message end N/A 21 NUL

5.22.4 MID 0403 Automatic/Manual mode unsubscribe

Reset the subscription for the automatic/manual mode.
 Message sent by: Integrator
 Answer: MID 0005 Command accepted or
MID 0004 Command error, Automatic/Manual mode subscribe does not exist

186 (224) Release 1.4

Revision 10 9836 4415 01
All messages

Message part Parameter Byte Value

Header Length 1-4 0020
MID 5-8 0403
Revision 9-11 Range 000-001
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field N/A N/A
Message end N/A 21 NUL

5.22.5 MID 0410 AutoDisable settings request

Request for AutoDisable settings. This request is intended to be used while running single parameter sets
with batch and does not provide batch information while running Job.
 Message sent by: Integrator
 Answer: MID 0411 AutoDisable settings reply

Message part Parameter Byte Value

Header Length 1-4 0020
MID 5-8 0410
Revision, MID 0411 9-11 Range 000-001
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field N/A N/A
Message end N/A 21 NUL

5.22.6 MID 0411 AutoDisable settings reply

Information about the setting of AutoDisable tightening in the controller. Also contains information about
the currently running batch.
The settings are reserved for single parameter sets with batch and are not available while running Job.
Power Macs use:
“OKs to disable station” is a parameter in ToolsTalk PowerMACS and specifies the number of cycles
with status OK or OKR that may be run while in Automatic mode before the station is automatically
disabled. It is sent as two ASCII digits, a 0 means the function is not in use.
“Current Batch” is two ASCII digits representing 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.
Power Focus use:

9836 441 01 Release 1.4

Revision 10 0 (224)
All messages

The “Current Batch” contains at which batchcounter value/tightening the parameter set batch was
locked/finished if “batchcount” and “lock at batch ok” parameters in ToolsTalk PF was used, otherwise it
will contain 0 indicating function not used.If “lock at batch ok” parameter was not used the “Current
Batch” is just current.
The “Auto Disable” contains the parameter sets batch size if “batchcount” and “lock at batch ok”
parameters was used indicating that AutoDisable function is used. If “batchcount” or “lock at batch ok”
was not used the “Auto Disable” is 0.
 Message sent by: Controller
 Answer: None
Message part Parameter Byte Value
Header Length 1-4 0020
MID 5-8 0411
Revision 9-11 Range 000-001
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field, part 1 AutoDisable setting 21-22 Two ASCII digits. 00= not used, <> 00=in use
Data field, part 2 Current batch 23-24 Two ASCII digits. Range 00-99. 00=function not
used
Message end N/A 25 NUL

5.23 Open Protocol Commands Disabled

When the Open Protocol commands disable digital input is active, the commands marked in column Open
protocol commands in Table 4 Available messages will be rejected and the message MID 0004 Command
error, Open Protocol commands disabled (Error 92) will be sent.

5.23.1 MID 0420 Open Protocol commands disabled subscribe

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).
 Message sent by: Integrator
 Answer: MID 0005 Command accepted or
MID 0004 Command error, Open Protocol commands disabled
subscription already exists

188 (224) Release 1.4

Revision 10 9836 4415 01
All messages

Message part Parameter Byte Value

Header Length 1-4 0020
MID 5-8 0420
Revision 9-11 Range 000-001
No Ack flag 12 0=Ack needed, 1=No ack needed
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field N/A N/A
Message end N/A 21 NUL

5.23.2 MID 0421 Open Protocol commands disabled

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).
 Message sent by: Controller
 Answer: MID 0422 Open Protocol commands disabled acknowledge

Message part Parameter Byte Value

Header Length 1-4 0021
MID 5-8 0421
Revision 9-11 Range 000-001
No Ack flag 12 0=Ack needed, 1=No ack needed
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field Digital input status 21 1=true, 0=false
Message end N/A 22 NUL

9836 441 01 Release 1.4

Revision 10 0 (224)
All messages

5.23.3 MID 0422 Open Protocol commands disabled acknowledge

Acknowledgement of Open Protocol commands disabled upload.
 Message sent by: Integrator
 Answer: None
Message part Parameter Byte Value
Header Length 1-4 0020
MID 5-8 0422
Revision 9-11 Range 000-001
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field N/A N/A
Message end N/A 21 NUL

5.23.4 MID 0423 Open Protocol commands disabled unsubscribe

Reset the subscription for the Open Protocol commands disabled digital input.
 Message sent by: Integrator
 Answer: MID 0005 Command accepted or
MID 0004 Command error, Open Protocol commands disabled
subscription does not exist

Message part Parameter Byte Value

Header Length 1-4 0020
MID 5-8 0423
Revision 9-11 Range 000-001
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field N/A N/A
Message end N/A 21 NUL

190 (224) Release 1.4

Revision 10 9836 4415 01
All messages

5.24 MID 8000, MID 8001

Reserved for Audi, see Audi Appendix.

5.25 Motor tuning

Subcriptions and commands for the area of motor tuning

5.25.1 MID 0500 Motor tuning result data subscribe

Sets the subscription for the motor tuning result. The result of this command will be the transmission of
the motor tuning result after the motor tuning is performed. The MID revision in the header is used
to subscribe to different revisions of MID 0501 Motor tuning result data upload reply.
 Message sent by: Integrator
 Answer: MID 0004 Command error, Motor Tuning subscription already exists or MID
revision not supported

Message part Parameter Byte Value

Header Length 1-4 0020
MID 5-8 0500
Revision 9-11 Range: 000-001
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field N/A N/A
Message end 21 NUL

5.25.2 MID 0501 Motor tuning result data

Upload the last motor tuning result.
 Message sent by: Controller
 Answer: MID 0502 Motor tuning result data acknowledge

9836 441 01 Release 1.4

Revision 10 0 (224)
All messages

Message part Parameter Byte Value

Header Length 1-4 0023
MID 5-8 0501
Revision of MID 0066 9-11 Range: 0-001.
No Ack flag 12 0=Ack needed, 1=No ack needed
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field Motor Tune data 21-length See table 85
Message end N/A NUL

Table 88 MID 501Motor tuning result data

Parameter Byte Value
MotorTune result 21-22 01
23 The Motor tune status, one ASCII digit : 0 (Motor tune failed) or 1
(Motor tune success)

5.25.3 MID 0502 Motor tuning result data acknowledge

Acknowledgement of motor tuning result data.
 Message sent by: Integrator
 Answer: None

Message part Parameter Byte Value

Header Length 1-4 0020
MID 5-8 0502
Revision 9-11 Range: 001
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field N/A N/A
Message end N/A 21 NUL

192 (224) Release 1.4

Revision 10 9836 4415 01
All messages

5.25.4 MID 503 Motor tuning result data unsubscribe

Reset the motor tuning result subscription.

 Message sent by: Integrator
 Answer: MID 0005 Command accepted or MID 0004 Command error, Motor Tuning result
subscription does not exist
Message part Parameter Byte Value
Header Length 1-4 0020
MID 5-8 0503
Revision 9-11 Range: 0-001
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field N/A N/A
Message end N/A 21 NUL

5.25.5 MID 0504 Motor tuning request

Request the start of the motor tuning
 Message sent by: Integrator
 Answer: MID 0005 Command accepted or
MID 0004 Command error, Tool motor tuning failed

Message part Parameter Byte Value

Header Length 1-4 0020
MID 5-8 0504
Revision 9-11 Range: 000-001
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field N/A N/A
Message end 21 NUL

9836 441 01 Release 1.4

Revision 10 0 (224)
All messages

5.26 Keep alive message

5.26.1 MID 9999 Keep alive message

The integrator sends a keep alive to the controller. The controller should only mirror and return the
received keep alive to the integrator.
The controller has a communication timeout equal to 15s. This means that if no message has been
exchanged between the integrator and the controller for the last 15s, then the controller considers the
connection lost and closes it.
In order to keep the communication alive the integrator must send a keep alive to the controller with a
time interval lower than 15s.
Note: 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.
 Message sent by: Integrator
 Answer: The same message mirrored by the controller.
Message part Parameter Byte Value
Header Length 1-4 0020
MID 5-8 9999
Revision 9-11 Range 000-001
No Ack flag 12 N/A
Station ID 13-14 N/A
Spindle ID 15-16 N/A
Spare 17-20 N/A
Data field N/A N/A
Message end N/A 21 NUL

194 (224) Release 1.4

Revision 10 9836 4415 01
Appendix

6 Appendix

6.1 Notes about press systems

A PowerMACS system can be used to control both spindles and presses.
A press system only supports revision 5 or higher of MID 0001 Communication start. In the answer MID
0002 Communication start acknowledge it will have the field System subtype set to “002” for Press. In
this way it is not possible to connect to a press system „by mistake‟. The integrator must first make the
needed changes to their side before it is possible to connect.
A press system behaves very similar to a tightening system and it uses the same MIDs with the same
definitions. There are however some differences the integrator must be aware of.
 Fields named Spindle or Tool are used for the corresponding values for the Press.
 Whenever the specification talks about “tightening” or “tightenings” the field is instead used for
“pressing” or “pressings”
 Fields normaly used for torque values are used for Force values in Press. The unit used is kN if nothing
else is stated.
 Fields normaly used for angle values are used for Stroke values in Press. The unit used is mm if
nothing else is stated.
 The error codes sent in MID 0071 Alarm have a different defintion in Press, see the PowerMACS Press
user manual for the compleat list of avaliable events.
 MID 0090 Multi-spindle status subscribe is also used for „Multi-press status subscribe‟. In the answer
MID 0091 Multi-spindle status the field Spindle status is used for the presses instead.
 New revisions have been added of MID 0100 Multi-spindle result subscribe and MID 0105 Last
PowerMACS tightening result data subscribe. A Press system only support revision 4 or higher of
these and will answer with MID 0004 Command error, MID revision unsupported if an older revision
is used.
 Most of the variable names used in MID 0106 Last PowerMACS tightening result station data and
MID 0107 Last PowerMACS are different in a Press system.

6.2 PowerMACS data, names for variable identification

This section includes all variables for PowerMACS data handled by the PM result data MIDs in section 0.
All variable names ending with a + or – sign are high and low limits. If the name ends with Cp, Cpk or
Cam it means that it is a statistical value. The first part of the name for limits and statistical values are
always the same as the name of the measurement value. The following sections include:
 Bolt values
 Step values
 Special values in station data
 Special values in Bolt data
 Possible types for special values
 Formatting of error codes

9836 4415 01 Release 1.4

Revision 10 195 (224)
Appendix

Note: The values that need to be interpreted diffrently in a Press system are prefixed with a „P‟ to mark
this. To find the values in the Open Protocol reporter in ToolsTalk PowerMACS you just replace Object
with Bolt, F (for Force) with T (for Torque) and S (for Stroke) with A (for Angle). For example the value
called Object F 2nd in the reporter will be sent with identification „PBolt T 2nd‟. The same rule apply to
both the bolt (object) and step data. If the value can be interpreted in exactly the same way in Press and
Tightening the same identifier is used, without the prefix „P‟ in Press.

In tightening the units are Nm and degrees for torque and angle measurements. The units in press are kN
and mm for force and stroke.

6.2.1 Variable names for Bolt values

The Bolt values available are listed in Table 89 and
Note: The name Spindle No is used in a press system even though it is realy used for the Press No.
Table 90. This list will be extended as new result variables are added to the PowerMACS 4000 system.
Note: The Bolt variables Bolt T and Bolt A with the corresponding limits are only sent in MID 0106 Last
PowerMACS tightening result station data and are not possible to get in MID 0107 Last PowerMACS
tightening result Bolt data.

Note: The name Spindle No is used in a press system even though it is realy used for the Press No
Table 89 Variable names for Bolt values
Tightening system Press system
Spindle No Spindle No
Op Mode Op Mode
Failing Step No Failing Step No
Program No Program No
Bolt A Thresh T PBolt A Thresh T
Program Strategy PProgram Strategy
Mon A Chan PMon A Chan
Mon T Chan PMon T Chan
Con A Chan PCon A Chan
Con T Chan PCon T Chan
Mon Buf 1A PMon Buf 1A
Mon Buf 1T PMon Buf 1T
Mon Buf 2A PMon Buf 2A
Mon Buf 2T PMon Buf 2T
No of Steps No of Steps

Note: The name Spindle No is used in a press system even though it is realy used for the Press No.
Table 90 Measurement values
Tightening system Press system
Bolt T 2nd PBolt T 2nd
Bolt T 2nd + Bolt T 2nd - PBolt T 2nd + PBolt T 2nd -
Bolt T Cp Bolt T Cpk Bolt T Cam PBolt T Cp PBolt T Cpk PBolt T Cam
Bolt T 2nd Cp Bolt T 2nd Cpk Bolt T 2nd Cam PBolt T 2nd Cp PBolt T 2nd Cpk PBolt T 2nd Cam
Bolt A 2nd PBolt A 2nd
Bolt A 2nd + Bolt A 2nd - PBolt A 2nd + PBolt A 2nd -
Bolt A Cp Bolt A Cpk Bolt A Cam PBolt A Cp PBolt A Cpk PBolt A Cam

196 (224) Release 1.4

Revision 10
9836 4415 01
Appendix

Tightening system Press system

Bolt A 2nd Cp Bolt A 2nd Cpk Bolt A 2nd Cam PBolt A 2nd Cp PBolt A 2nd Cpk PBolt A 2nd Cam
Bolt TR1 PBolt TR1
Bolt TR1 2nd PBolt TR1 2nd
Bolt TR1 + Bolt TR1 - PBolt TR1 + PBolt TR1 -
Bolt TR1 2nd + Bolt TR1 2nd - PBolt TR1 2nd + PBolt TR1 2nd -
Bolt TR1 Cp Bolt TR1 Cpk Bolt TR1 Cam PBolt TR1 Cp PBolt TR1 Cpk PBolt TR1 Cam
Bolt TR1 2nd Cp Bolt TR1 2nd Cpk Bolt TR1 2nd Cam PBolt TR1 2nd Cp PBolt TR1 2nd Cpk PBolt TR1 2nd Cam
Bolt TR2 PBolt TR2
Bolt TR2 2nd PBolt TR2 2nd
Bolt TR2 + Bolt TR2 - PBolt TR2 + PBolt TR2 -
Bolt TR2 2nd + Bolt TR2 2nd - PBolt TR2 2nd + PBolt TR2 2nd -
Bolt TR2 Cp Bolt TR2 Cpk Bolt TR2 Cam PBolt TR2 Cp PBolt TR2 Cpk PBolt TR2 Cam
Bolt TR2 2nd Cp Bolt TR2 2nd Cpk Bolt TR2 2nd Cam PBolt TR2 2nd Cp PBolt TR2 2nd Cpk PBolt TR2 2nd Cam
Bolt TR Dev1 PBolt TR Dev1
Bolt TR Dev1 2nd PBolt TR Dev1 2nd
Bolt TR Dev1 + PBolt TR Dev1 +
Bolt TR Dev1 2nd + PBolt TR Dev1 2nd +
Bolt TR Dev1 Cp Bolt TR Dev1 Cpk Bolt TR Dev1 Cam PBolt TR Dev1 Cp PBolt TR Dev1 Cpk PBolt TR Dev1 Cam
PBolt TR Dev1 2d
Bolt TR Dev1 2nd Cp Bolt TR Dev1 2nd Cpk Bolt TR Dev1 2nd Cam PBolt TR Dev1 2d Cp PBolt TR Dev1 2d Cpk Cam
Bolt TR Dev2 PBolt TR Dev2
Bolt TR Dev2 2nd PBolt TR Dev2 2nd
Bolt TR Dev2 + PBolt TR Dev2 +
Bolt TR Dev2 2nd + PBolt TR Dev2 2nd +
Bolt TR Dev2 Cp Bolt TR Dev2 Cpk Bolt TR Dev2 Cam PBolt TR Dev2 Cp PBolt TR Dev2 Cpk PBolt TR Dev2 Cam
PBolt TR Dev2 2d
Bolt TR Dev2 2nd Cp Bolt TR Dev2 2nd Cpk Bolt TR Dev2 2nd Cam PBolt TR Dev2 2d Cp PBolt TR Dev2 2d Cpk Cam
Bolt YP T PBolt YP T
Bolt YP T 2nd PBolt YP T 2nd
Bolt YP T + Bolt YP T - PBolt YP T + PBolt YP T -
Bolt YP T 2nd + Bolt YP T 2nd - PBolt YP T 2nd + PBolt YP T 2nd -
Bolt YP T Cp Bolt YP T Cpk Bolt YP T Cam PBolt YP T Cp PBolt YP T Cpk PBolt YP T Cam
Bolt YP T 2nd Cp Bolt YP T 2nd Cpk Bolt YP T 2nd Cam PBolt YP T 2nd Cp PBolt YP T 2nd Cpk PBolt YP T 2nd Cam
Bolt YP A PBolt YP A
Bolt YP A 2nd PBolt YP A 2nd
Bolt YP A + Bolt YP A - PBolt YP A + PBolt YP A -
Bolt YP A 2nd + Bolt YP A 2nd - PBolt YP A 2nd + PBolt YP A 2nd -
Bolt YP A Cp Bolt YP A Cpk Bolt YP A Cam PBolt YP A Cp PBolt YP A Cpk PBolt YP A Cam
Bolt YP A 2nd Cp Bolt YP A 2nd Cpk Bolt YP A 2nd Cam PBolt YP A 2nd Cp PBolt YP A 2nd Cpk PBolt YP A 2nd Cam
Bolt Max T PBolt Max T
Bolt Max T + Bolt Max T - PBolt Max T + PBolt Max T -
Bolt Max T Cp Bolt Max T Cpk Bolt Max T Cam PBolt Max T Cp PBolt Max T Cpk PBolt Max T Cam
Bolt Min T PBolt Min T
Bolt Min T + Bolt Min T - PBolt Min T + PBolt Min T -
Bolt Min T Cp Bolt Min T Cpk Bolt Min T Cam PBolt Min T Cp PBolt Min T Cpk PBolt Min T Cam
Bolt T try 1 PBolt T try 1
Bolt T try 2 PBolt T try 2
Bolt T try 3 PBolt T try 3
Bolt T try 4 PBolt T try 4

9836 4415 01 Release 1.4

Revision 10 197 (224)
Appendix

Tightening system Press system

Bolt T try 5 PBolt T try 5
Bolt T try 1 + Bolt T try 1 - PBolt T try 1 + PBolt T try 1 -
Bolt T try 2 + Bolt T try 2 - PBolt T try 2 + PBolt T try 2 -
Bolt T try 3 + Bolt T try 3 - PBolt T try 3 + PBolt T try 3 -
Bolt T try 4 + Bolt T try 4 - PBolt T try 4 + PBolt T try 4 -
Bolt T try 5 + Bolt T try 5 - PBolt T try 5 + PBolt T try 5 -
Bolt T try 1 Cp Bolt T try 1 Cpk Bolt T try 1 Cam PBolt T try 1 Cp PBolt T try 1 Cpk PBolt T try 1 Cam
Bolt T try 2 Cp Bolt T try 2 Cpk Bolt T try 2 Cam PBolt T try 2 Cp PBolt T try 2 Cpk PBolt T try 2 Cam
Bolt T try 3 Cp Bolt T try 3 Cpk Bolt T try 3 Cam PBolt T try 3 Cp PBolt T try 3 Cpk PBolt T try 3 Cam
Bolt T try 4 Cp Bolt T try 4 Cpk Bolt T try 4 Cam PBolt T try 4 Cp PBolt T try 4 Cpk PBolt T try 4 Cam
Bolt T try 5 Cp Bolt T try 5 Cpk Bolt T try 5 Cam PBolt T try 5 Cp PBolt T try 5 Cpk PBolt T try 5 Cam
Bolt A try 1 PBolt A try 1
Bolt A try 2 PBolt A try 2
Bolt A try 3 PBolt A try 3
Bolt A try 4 PBolt A try 4
Bolt A try 5 PBolt A try 5
Bolt A try 1 + Bolt A try 1 - PBolt A try 1 + PBolt A try 1 -
Bolt A try 2 + Bolt A try 2 - PBolt A try 2 + PBolt A try 2 -
Bolt A try 3 + Bolt A try 3 - PBolt A try 3 + PBolt A try 3 -
Bolt A try 4 + Bolt A try 4 - PBolt A try 4 + PBolt A try 4 -
Bolt A try 5 + Bolt A try 5 - PBolt A try 5 + PBolt A try 5 -
Bolt A try 1 Cp Bolt A try 1 Cpk Bolt A try 1 Cam PBolt A try 1 Cp PBolt A try 1 Cpk PBolt A try 1 Cam
Bolt A try 2 Cp Bolt A try 2 Cpk Bolt A try 2 Cam PBolt A try 2 Cp PBolt A try 2 Cpk PBolt A try 2 Cam
Bolt A try 3 Cp Bolt A try 3 Cpk Bolt A try 3 Cam PBolt A try 3 Cp PBolt A try 3 Cpk PBolt A try 3 Cam
Bolt A try 4 Cp Bolt A try 4 Cpk Bolt A try 4 Cam PBolt A try 4 Cp PBolt A try 4 Cpk PBolt A try 4 Cam
Bolt A try 5 Cp Bolt A try 5 Cpk Bolt A try 5 Cam PBolt A try 5 Cp PBolt A try 5 Cpk PBolt A try 5 Cam
Bolt AP A PBolt AP A
Bolt AP A + Bolt AP A - PBolt AP A + PBolt AP A -
Bolt AP A Cp Bolt AP A Cpk Bolt AP A Cam PBolt AP A Cp PBolt AP A Cpk PBolt AP A Cam
Bolt PreET PBolt PreET
Bolt PreET 2nd PBolt PreET 2nd
Bolt PreET + Bolt PreET - PBolt PreET + PBolt PreET -
Bolt PreET 2nd + Bolt PreET 2nd - PBolt PreET 2nd + PBolt PreET 2nd -
Bolt PreET Cp Bolt PreET Cpk Bolt PreET Cam PBolt PreET Cp PBolt PreET Cpk PBolt PreET Cam
Bolt PreET 2nd Cp Bolt PreET 2nd Cpk Bolt PreET 2nd Cam PBolt PreET 2nd Cp PBolt PreET 2nd Cpk PBolt PreET 2nd Cam
PBolt CC 01 T
Bolt CC 01 T
...
...
PBolt CC 40 T
Bolt CC 40 T
Bolt CC 41
Bolt CC 41
...
...
Bolt CC 80
Bolt CC 80

PBolt CC 01 T + PBolt CC 01 T -
Bolt CC 01 T + Bolt CC 01 T -
...
...
PBolt CC 40 T + PBolt CC 40 T -
Bolt CC 40 T + Bolt CC 40 T -
Bolt CC 41 + Bolt CC 41 -
Bolt CC 41 + Bolt CC 41 -
...
...
Bolt CC 80 + Bolt CC 80 -
Bolt CC 80 + Bolt CC 80 -
198 (224) Release 1.4
Revision 10
9836 4415 01
Appendix

Tightening system Press system

Step CC 01 T PStep CC 01 T
… …
Step CC 40 T PStep CC 40 T
Step CC 41 Step CC 41
… …
Step CC 80 Step CC 80

6.2.3 Special values in Station and Bolt data

At the moment the following special values are available for Station and Bolt data. This list will be
extended as new result variables are added to the PowerMACS 4000 system.
This section includes a table describing the types of special values and tables listing the special values for
Station and for Bolt data.
The same identifiers of station data are used in both Tightening and Press systems.
Table 92 Special values type

206 (224) Release 1.4

Revision 10
9836 4415 01
Appendix

Type Length Description

I 10 The value is an unsigned integer. Sent as 10 ASCII digits, possible values are 0 to
4294967295.
S Variable The value is a string. Sent as ASCII characters, the length of the data fits the actual
length of the string.
T 19 A time specified by 19 ASCII characters (YYYY-MM-DD:HH:MM:SS)
E1 50 Tightening errors
E2 10 Tightening warnings
E3 3 Compact errors 1
E4 3 Compact errors 2
B 1 A boolean value, one ASCII digit, 0 = FALSE and 1 = TRUE

Table 93 Variable names for special values in Station data, MID 0106
Name Data Type
Total I
Total OK I
Total NOK I
Free Str S
Free No 1 I
Free No 2 I
Free Str 2 S
Free Str 3 S
Data No Station I
Station QO I
Station SA I
Station AB S
ID Res 1 S
ID Res 2 S
ID Res 3 S
ID Res 4 S
ID Res 5 S
ID Res 6 S

Table 94 Variable names for special values in Bolt data, MID 0107
Name Data Type
Total I
Total OK I
Total NOK I
Total Type I
Total Type OK I
Total Type NOK I
RM Errors E1
Warnings E2

9836 4415 01 Release 1.4

Revision 10 207 (224)
Appendix

Name Data Type

Compact Errors E3
Spindle Serial No S
Compact Errors 2 E4
Program Time T
Spindle Name S
Customer error code S
Spindle Art. No S
Sp. total cycles I
Sp. cycl since serv. I
Sp. cycl to serv. I
Spindle Type S
Data Missing B
Errors E1
Step Name S

6.2.4 Formatting of error codes

This section describes the types of error codes.
Note: For error bit definition, see the PowerMACS 4000 manual. A press system have different
definitions of the error bits, see the PowerMACS 4000 Press manual for a definition of these.

Type E1, used for errors and RM errors

This type of error codes consists of 50 bytes. It is formatted like five 10 digit decimal numbers placed side
by side. In each 10 digit number 32 error bits are stored.
Byte 40 - 49 Byte 30 – 39 Byte 20 - 29 Byte 10 – 19 Byte 0 - 9
Integer 4 Integer 3 Integer 2 Integer 1 Integer 0
Error bit 128 - 159 Error bit 96 – 127 Error bit 64 – 95 Error bit 32 – 63 Error bit 0 – 31

Example:
If a tightening gets the errors TR (bit 5), MTH (bit 23), THM (bit 37) and SS (bit 96), the five integers will
be:
Integer 0 = 32 + 8388608 = 8388640
Integer 1 = 32
Integer 2 = 0
Integer 3 = 1
Integer 4 = 0
And the number sent as error code will be:

00000000000000000001000000000000000000320008388640

208 (224) Release 1.4

Revision 10
9836 4415 01
Appendix

Type E2, used for warnings

This type of error codes consists of 10 bytes. It is formatted like one 10 digit decimal number In this
number 32 error bits are stored.
Byte 0 - 9
Integer 0
Error bit 0 – 31

Type E3, used for compact errors

This type of error codes consists of 3 bytes. It is formatted like one 3 digit decimal number. In this number
8 error bits are stored.
Byte 0 – 2
Integer 0
Error bit 0 – 7

Type E4, used for compact errors 2

This type of error codes consists of 3 bytes. It is formatted like one 3 digit decimal number. In this number
8 error bits are stored.
Byte 0 – 2
Integer 0
Error bit 0 – 7

9836 4415 01 Release 1.4

Revision 10 209 (224)
Appendix

6.3 Product MID/Revision support

This section lists MID and MIDs revision supported by products. The Revision figures in the columns set for each product means that the product has
support for all revisions from 0 up to and inclusive the revision figure.
Sign “-“ means that the product hasn‟t support for the MID and Revision.
Sign “p” means partly supported. See Error! Reference source not found.
Note that PowerMACS classic uses FFCCP protocol. See the PowerMACS user guide for more information.
This table is valid for the following releases.
PF4000 W10.9
PF3000 W7.5 SR2
PM4000 10.5.0
PM 5.2.8 * (FFCCP)

PF6000 1.5

Table 95 Product MID/Revision support

PM4000
PF4000
PF3000

PF6000
PM

Product

ID Description Revisions
0001 Communication start 4 4 5 1 5
Communication start 5
0002 acknowledge 4 4 5 2 p
0003 Communication stop 1 1 1 1 1
210 (224) Release 1.4
Revision 10 9836 4415 01
Appendix

PM4000
PF4000
PF3000

PF6000
PM
Product

ID Description Revisions
0004 Command error 1 1 1 1 1
0005 Command accepted 1 1 1 1 1
0010 Parameter set ID upload request 1 1 1 1 1
0011 Parameter set ID upload reply 1 1 1 1 1
Parameter set data upload
0012 request 3 3 - - 4
0013 Parameter set data upload reply 3 3 - - 4
0014 Parameter set selected subscribe 1 1 1 1 1
0015 Parameter set selected 1 1 1 1 1
Parameter set selected
0016 acknowledge 1 1 1 1 1
Parameter set selected
0017 unsubscribe 1 1 1 1 1
0018 Select Parameter set 1 1 1 1 1
0019 Set Parameter set batch size 1 1 - - -
Reset Parameter set batch
0020 counter 1 1 - - -
0021 Lock at batch done subscribe 1 1 - - -
0022 Lock at batch done upload 1 1 - - -
Lock at batch done upload
0023 acknowledge 1 1 - - -
0024 Lock at batch done unsubscribe 1 1 - - -
0025 Download Pset. Toyota Appendix - - - - 2
0030 Job ID upload request 2 2 - - 2
0031 Job ID upload reply 2 2 - - 2
0032 Job data upload request 3 3 3 3 2
0033 Job data upload reply 3 3 3 3 2
9836 4415 01 Release 1.4
Revision 18 211 (224)
Appendix

PM4000
PF4000
PF3000

PF6000
PM
Product

ID Description Revisions
p
0034 Job info subscribe 4 2 - - 4
4
0035 Job info 4 2 - - p
0036 Job info acknowledge 4 2 - - 4
0037 Job info unsubscribe 4 2 - - 4
0038 Select Job 2 2 - - 2
0039 Job restart 2 2 - - 2
0040 Tool data upload request 3 3 1 1 4
4
0041 Tool data upload reply 3 3 1 1 p
0042 Disable tool 1 1 1 1 1
0043 Enable tool 1 1 1 1 1
0044 Disconnect tool request 1 1 - - -
0045 Set calibration value request 1 1 - - 1
0046 Set primary tool request 1 1 - - -
Vehicle ID number download
0050 request 1 1 1 1 1
0051 Vehicle ID number subscribe 2 2 1 1 -
0052 Vehicle ID number 2 2 1 1 -
0053 Vehicle ID number acknowledge 2 2 1 1 -
0054 Vehicle ID number unsubscribe 2 2 1 1 -
6, 6
9 ,
9 9
Last tightening result data 8, 9
0060 subscribe 9 9 - - 7

212 (224) Release 1.4

Revision 10 9836 4415 01
Appendix

PM4000
PF4000
PF3000

PF6000
PM
Product

ID Description Revisions
9
9
6,
9
9 6
9, ,
9 9
9 9 7
0061 Last tightening result data 8 9 - - p
6,
9
9 6
8, ,
9 9
Last tightening result data 9 9
0062 acknowledge 9 9 - - 7
6,
9
9 6
8, ,
9 9
Last tightening result data 9 9
0063 unsubscribe 9 9 - - 7
Old tightening result upload
0064 request 6 6 - - -
0065 Old tightening result upload reply 6 6 - - -
0070 Alarm subscribe 1 1 1 1 1
0071 Alarm 1 1 1 1 2
0072 Alarm acknowledge 1 1 1 1 2
0073 Alarm unsubscribe 1 1 1 1 2

9836 4415 01 Release 1.4

Revision 18 213 (224)
Appendix

PM4000
PF4000
PF3000

PF6000
PM
Product

ID Description Revisions
Alarm acknowledged on
0074 controller 1 1 1 1 2
Alarm acknowledged on
0075 controller acknowledge 1 1 1 1 2
0076 Alarm status 1 1 1 1 -
0077 Alarm status acknowledge 1 1 1 1 -
Acknowledge alarm remotely on
0078 controller 1 1 - - -
0080 Read time upload request 1 1 1 1 1
0081 Read time upload reply 1 1 1 1 1
0082 Set time 1 1 1 1 1
0090 Multi-spindle status subscribe 1 1 1 1 -
0091 Multi-spindle status 1 1 1 1 -
0092 Multi-spindle status acknowledge 1 1 1 1 -
0093 Multi-spindle status unsubscribe 1 1 1 1 -
0100 Multi-spindle result subscribe 1 1 4 1 -
0101 Multi-spindle result 1 1 4 1 -
0102 Multi-spindle result acknowledge 1 1 4 1
0103 Multi-spindle result unsubscribe 1 1 4 1 -
Last PowerMACS tightening
0105 result data subscribe - - 4 - -
Last PowerMACS tightening
0106 result Station data - - 4 - -
Last PowerMACS tightening
0107 result Bolt data - - 4 - -
Last PowerMACS tightening
0108 result data acknowledge - - 4 - -

214 (224) Release 1.4

Revision 10 9836 4415 01
Appendix

PM4000
PF4000
PF3000

PF6000
PM
Product

ID Description Revisions
Last PowerMACS tightening
0109 result data unsubscribe - - 4 - -
0110 Display user text on compact 1 1 - - -
0111 Display user text on graph 1 1 - - -
0113 Flash green light on tool 1 1 - - -
0120 Job line control info subscribe 1 1 - - -
0121 Job line control started 1 1 - - -
0122 Job line control alert 1 1 1 - - -
0123 Job line control alert 2 1 1 - - -
0124 Job line control done 1 1 - - -
0125 Job line control info acknowledge 1 1 - - -
0126 Job line control info unsubscribe 1 1 - - -
0127 Abort Job 1 1 - - 1
0128 Job batch increment 1 1 - - 1
0129 Job batch decrement 2 2 - - 1
0130 Job off 1 1 - - -
0131 Set Job line control start 1 1 - - -
0132 Set Job line control alert 1 1 1 - - -
0133 Set Job line control alert 2 1 1 - - -
1
1, ,
9 9
9 9
0140 Execute dynamic Job request 9 9 - - -
0150 Identifier download request 1 1 - - 1
Multiple identifiers work order
0151 subscribe 1 1 - - -
9836 4415 01 Release 1.4
Revision 18 215 (224)
Appendix

PM4000
PF4000
PF3000

PF6000
PM
Product

ID Description Revisions
0152 Multiple identifiers work order 1 1 - - -
Multiple identifiers work order
0153 acknowledge 1 1 - - -
Multiple Identifiers work order
0154 unsubscribe 1 1 -- -
0155 Bypass identifier 1 1 -- -
0156 Reset latest identifier 1 1 -- -
0157 Reset all identifiers 1 1 -- -
1
0200 Set external controlled relays 1 1 - - p
Status external monitored inputs
0210 subscribe 1 1 - - -
0211 Status external monitored inputs 1 1 - - -
Status external monitored inputs
0212 acknowledge 1 1 - - -
Status external monitored inputs
0213 unsubscribe 1 1 - - -
0214 IO device status request 2 2 - - -
0215 IO device status reply 2 2 - - -
0216 Relay function subscribe 1 1 - - 1
0217 Relay function 1 1 - - 1
0218 Relay function acknowledge 1 1 - - 1
0219 Relay function unsubscribe 1 1 - - 1
0220 Digital input function subscribe 1 1 - - 1
0221 Digital input function 1 1 - - 1
Digital input function
0222 acknowledge 1 1 - - 1
0223 Digin function unsubscribe 1 1 - - 1
216 (224) Release 1.4
Revision 10 9836 4415 01
Appendix

PM4000
PF4000
PF3000

PF6000
PM
Product

ID Description Revisions
0224 Set digital input function 1 1 - - 1
0225 Reset digital input function 1 1 - - 1
0240 User data download - - 1 - -
0241 User data subscribe - - 1 - -
0242 User data - - 1 - -
0243 User data acknowledge - - 1 - -
0244 User data unsubscribe - - 1 - -
1
0250 Selector socket info subscribe 1 1 - - P
1
0251 Selector socket info 1 1 - - P
1
0252 Selector socket info acknowledge 1 1 - - P
1
0253 Selector socket info unsubscribe 1 1 - - p
0254 Selector control green lights 1 1 - - -
0255 Selector control red lights 1 1 - - -
0260 Tool Tag ID request 1 1 - - -
0261 Tool Tag ID subscribe 1 1 - - -
0262 Tool Tag ID 1 1 - - -
0263 Tool Tag ID acknowledge 1 1 - -
0264 Tool Tag ID unsubscribe 1 1 - - -
0270 Controller reboot request 1 1 - -
Automatic/Manual mode
0400 subscribe - - 1 1 -
0401 Automatic/Manual mode - - 1 1 -
0402 Automatic/Manual mode - - 1 1 -
9836 4415 01 Release 1.4
Revision 18 217 (224)
Appendix

PM4000
PF4000
PF3000

PF6000
PM
Product

ID Description Revisions
acknowledge
Automatic/Manual mode
0403 unsubscribe - - 1 1 -
0410 AutoDisable settings request 0 0 0 0 -
0411 AutoDisable settings reply 0 0 0 0 -
Open protocol commands
0420 disabled subscribe 1 1 - - -
Open protocol commands
0421 disabled 1 1 - - -
Open protocol commands
0422 disabled acknowledge 1 1 - - -
Open protocol commands
0423 disabled unsubscribe 1 1 - - -
Motor tuning result data
500 subscribe - - - - 1
501 Motor tuning result data - - - - 1
Motor tuning result data
502 acknowledge - - - - 1
Motor tuning result data
503 unsubscribe - - - - 1
504 Motor tuning request - - - - 1

8000 Audi emergency status subscribe 1 1 - - -

8001 Audi emergency status 1 1 - - -

Audi emergency status
8002 acknowledge 1 1 - - -
8003 Audi emergency status 1 1 - -
218 (224) Release 1.4
Revision 10 9836 4415 01
Appendix

PM4000
PF4000
PF3000

PF6000
PM
Product

ID Description Revisions
unsubscribe -
Keep alive open protocol
9999 communication 0 0 0 0 0

Table 96 Parameters not supported in PF6000

MID MID Rev Parameter
All All Cell Id
13 Parameter set data upload reply 1 Batch size

Table 97 Parameters not supported or managed under special conditions in PF6000

MID MID Rev Parameters/Conditions
2 CommunicationStartAcknowledge 2 Supplier code
2 CommunicationStartAcknowledge 3 Open Protocol version
2 CommunicationStartAcknowledge 4 RBU Type

9836 4415 01 Release 1.4

Revision 18 219 (224)
Appendix

2 CommunicationStartAcknowledge 5 System subtype

33 Job Data 1 Max time for first tightening
33 Job Data 1 Use line control
33 Job Data 1 Repeat Job
33 Job Data 1 Tool loosening
33 Job Data 3 Job List
35 Job Info 1 Job batch size
35 Job Info 1 Job batch counter
35 Job Info 3 Job step type
35 Job Info 4 Job tightening status
41 Tool data upload reply 2 Motor size
41 Tool data upload reply 2 Open end data
41 Tool data upload reply 4 Primary Tool
61 LastTighteningResultDataUploadReply 1 Channel ID
61 LastTighteningResultDataUploadReply 1 VIN Number
61 LastTighteningResultDataUploadReply 1 Date/time of last change in Pset
61 LastTighteningResultDataUploadReply 1 Tightening Id
61 LastTighteningResultDataUploadReply 2 Strategy Options
61 LastTighteningResultDataUploadReply 2 current monitoring status
61 LastTighteningResultDataUploadReply 2 prevail torque monitoring status
61 LastTighteningResultDataUploadReply 2 prevail torque compensate status
61 LastTighteningResultDataUploadReply 2 tightening error status
61 LastTighteningResultDataUploadReply 2 rundown angle
61 LastTighteningResultDataUploadReply 2 current monitoring min
61 LastTighteningResultDataUploadReply 2 current monitoring max
61 LastTighteningResultDataUploadReply 2 current monitoring value
61 LastTighteningResultDataUploadReply 2 selftap torque
61 LastTighteningResultDataUploadReply 2 prevail torque monitoring min
220 (224) Release 1.4
Revision 10 9836 4415 01
Appendix

61 LastTighteningResultDataUploadReply 2 prevail torque monitoring max

61 LastTighteningResultDataUploadReply 2 prevail torque
61 LastTighteningResultDataUploadReply 2 job sequence number
61 LastTighteningResultDataUploadReply 2 sync tightening id
61 LastTighteningResultDataUploadReply 3 Torque values unit (only Nm
today)
61 LastTighteningResultDataUploadReply 3 Result type
61 LastTighteningResultDataUploadReply 4 Identifier result part 2
61 LastTighteningResultDataUploadReply 4 Identifier result part 3
61 LastTighteningResultDataUploadReply 4 Identifier result part 4
61 LastTighteningResultDataUploadReply 5 Customer tightening error code
61 LastTighteningResultDataUploadReply 6 Prevail Torque compensate
value
61 LastTighteningResultDataUploadReply 6 Tightening error status 2
61 LastTighteningResultDataUploadReply 998 Number of stages in multistage
61 LastTighteningResultDataUploadReply 998 Number of stage results
61 LastTighteningResultDataUploadReply 998 Stage result
200 SetExternalControlledRelays 1 With special config on the
controller ; no flashing mode
250 SelectorSocketInfoSubscribe 1 Ok if we have only one socket
selector
251 SelectorSocketInfoUpload 1 Ok if we have only one socket
selector
252 SelectorSocketInfoUploadAcknowledge 1 Ok if we have only one socket
selector
253 SelectorSocketInfoUnsubscribe 1 Ok if we have only one socket
selector

9836 4415 01 Release 1.4

Revision 18 221 (224)
Appendix

222 (224) Release 1.4

Revision 10 9836 4415 01
9836 4415 01
Specification release 1.6
Release 1.4
Revision 10
www.atlascopco.com

OpenProtocol Specification
No ratings yet
OpenProtocol Specification
309 pages
OpenProtocol Specification R 2.16.0
No ratings yet
OpenProtocol Specification R 2.16.0
314 pages
Pf6K VW XML Configuration FW. 2.8.5.39 XML 2.1.R.3.6
No ratings yet
Pf6K VW XML Configuration FW. 2.8.5.39 XML 2.1.R.3.6
54 pages
CimComms Protocol Doc V4 - 37
No ratings yet
CimComms Protocol Doc V4 - 37
90 pages
S530 WideScreen
No ratings yet
S530 WideScreen
64 pages
OpenProtocol W7 7.0
No ratings yet
OpenProtocol W7 7.0
103 pages
OpenProtocol Specification2.7
No ratings yet
OpenProtocol Specification2.7
314 pages
Ethernet Industrial
No ratings yet
Ethernet Industrial
120 pages
Internet of Things 27.01.25
No ratings yet
Internet of Things 27.01.25
140 pages
J1939 Appendix
No ratings yet
J1939 Appendix
76 pages
Sv660n Series
No ratings yet
Sv660n Series
426 pages
Advance Notice June July 2025 16052025
No ratings yet
Advance Notice June July 2025 16052025
27 pages
Ettercorp
No ratings yet
Ettercorp
57 pages
OpenProtocol - Specification - 9836 4415 01 2.5
No ratings yet
OpenProtocol - Specification - 9836 4415 01 2.5
301 pages
Fix Spec
No ratings yet
Fix Spec
84 pages
Power Focus 4000
No ratings yet
Power Focus 4000
428 pages
Open Protocol Specification4
No ratings yet
Open Protocol Specification4
31 pages
OpenProtocol Specification PDF
No ratings yet
OpenProtocol Specification PDF
307 pages
Atlas Copco Open Protocol v75
No ratings yet
Atlas Copco Open Protocol v75
166 pages
AREVA (Courier) Master Protocol
No ratings yet
AREVA (Courier) Master Protocol
27 pages
Transport Layer
No ratings yet
Transport Layer
15 pages
CEA QUIZLET Again
No ratings yet
CEA QUIZLET Again
111 pages
Atlas Copco MT Focus 6000 Open Protocol
No ratings yet
Atlas Copco MT Focus 6000 Open Protocol
30 pages
Open Core Protocol Specification: Release 2.1 OCP-IP Confidential
No ratings yet
Open Core Protocol Specification: Release 2.1 OCP-IP Confidential
240 pages
CNC Centurion 7 Programming Manual 179
No ratings yet
CNC Centurion 7 Programming Manual 179
441 pages
Computer Network Security Protocols and Standards60 PDF
No ratings yet
Computer Network Security Protocols and Standards60 PDF
59 pages
Simatic Net Industrial Wireless Lan Rcoax
No ratings yet
Simatic Net Industrial Wireless Lan Rcoax
68 pages
LinkRunner AT 3000 Product Data Sheet
No ratings yet
LinkRunner AT 3000 Product Data Sheet
5 pages
Al Brooks VIDEO TOMO 1 PDF
No ratings yet
Al Brooks VIDEO TOMO 1 PDF
57 pages
Drager Evita 4 Service Manual
100% (3)
Drager Evita 4 Service Manual
297 pages
Wireless Communications Homework
100% (1)
Wireless Communications Homework
6 pages
Sitscanning and Analysis Tools in Security
No ratings yet
Sitscanning and Analysis Tools in Security
14 pages
OCP IP OpenCoreProtocolSpecification 1.0
No ratings yet
OCP IP OpenCoreProtocolSpecification 1.0
202 pages
Drive Moog
No ratings yet
Drive Moog
148 pages
Web-Based Information Services in Selected Academic Libraries, Nigeria
No ratings yet
Web-Based Information Services in Selected Academic Libraries, Nigeria
14 pages
Ds 401
No ratings yet
Ds 401
111 pages
Copy Experiment 2
No ratings yet
Copy Experiment 2
3 pages
OEB902101 USN9810 V900R001 System Overview-20110914-A - ISSUE1.30
No ratings yet
OEB902101 USN9810 V900R001 System Overview-20110914-A - ISSUE1.30
66 pages
Cambridge IGCSE ™: Computer Science 0478/13
No ratings yet
Cambridge IGCSE ™: Computer Science 0478/13
9 pages
TLE 10 CSS Q2 Summative Test 2 Performance Task 2
No ratings yet
TLE 10 CSS Q2 Summative Test 2 Performance Task 2
2 pages
Restaurant Management System Android Projects
0% (1)
Restaurant Management System Android Projects
7 pages
Chap Quizzes Ccna4 PDF
No ratings yet
Chap Quizzes Ccna4 PDF
16 pages
OpenProtocol - ToolsNet 3.4
100% (3)
OpenProtocol - ToolsNet 3.4
18 pages
Embedded Systems 6. Real-Time Operating Systems: Lothar Thiele
No ratings yet
Embedded Systems 6. Real-Time Operating Systems: Lothar Thiele
27 pages
Quick Start Guide For The Clickshare App
No ratings yet
Quick Start Guide For The Clickshare App
11 pages
Network Range and Speed
No ratings yet
Network Range and Speed
2 pages
ToolsNet 4000 Installation Guide (9836418101)
No ratings yet
ToolsNet 4000 Installation Guide (9836418101)
72 pages
Global 2 IDNS - PLC Commissioning
No ratings yet
Global 2 IDNS - PLC Commissioning
16 pages
Ebook - CANOpen
100% (1)
Ebook - CANOpen
207 pages
Power Focus 6000 Pocket Guide: Release 2.3 Overview of The Power Focus 6000 and Tensor STR System
No ratings yet
Power Focus 6000 Pocket Guide: Release 2.3 Overview of The Power Focus 6000 and Tensor STR System
52 pages
EN - BRAIN QUICK - LTM Line
No ratings yet
EN - BRAIN QUICK - LTM Line
2 pages
896096-25 iTNC530 OEM HSCI PDF
No ratings yet
896096-25 iTNC530 OEM HSCI PDF
112 pages
Module 1 - Introduction To Networking Presentation
No ratings yet
Module 1 - Introduction To Networking Presentation
25 pages
OptiX OSN 1800 V100R003C01SPC300 Release Notes
100% (1)
OptiX OSN 1800 V100R003C01SPC300 Release Notes
62 pages
Zigbee FJFJK FJK
No ratings yet
Zigbee FJFJK FJK
33 pages
CCNA Guide To Networking - Ch6 - Quiz Solutions
No ratings yet
CCNA Guide To Networking - Ch6 - Quiz Solutions
5 pages
QB Alpha Controllers: Performance From Simple Error-Proofing To Line Control
No ratings yet
QB Alpha Controllers: Performance From Simple Error-Proofing To Line Control
8 pages
S300 Laser Scanner Configuration Protocol
No ratings yet
S300 Laser Scanner Configuration Protocol
6 pages
Network Simulation Using Nctuns
No ratings yet
Network Simulation Using Nctuns
7 pages
Pass4sure 312-50v9 Dumps
0% (1)
Pass4sure 312-50v9 Dumps
6 pages
Multi-Bay Battery Charger: Installation Guide
No ratings yet
Multi-Bay Battery Charger: Installation Guide
2 pages
Software-Defined Networking (SDN)
No ratings yet
Software-Defined Networking (SDN)
16 pages
Encoder Incremental Koyo
No ratings yet
Encoder Incremental Koyo
3 pages
FX3U-16CCL-M CC-Link Quick Start Guide
No ratings yet
FX3U-16CCL-M CC-Link Quick Start Guide
27 pages
Heienhain TNC 407: Ncnet 7.0 Settings
No ratings yet
Heienhain TNC 407: Ncnet 7.0 Settings
2 pages
Zambia Telecomms
No ratings yet
Zambia Telecomms
41 pages
SmartPTT Ports
No ratings yet
SmartPTT Ports
1 page
Computer Science
No ratings yet
Computer Science
9 pages
TINY SHIFTS, BIG RESULTS: How Small Habits Shape Who You Become and Transform Your Life: How Small Habits Shape Who You Become and Transform Your Life: How Small Habits Shape Who You Become and Transform Your Life
From Everand
TINY SHIFTS, BIG RESULTS: How Small Habits Shape Who You Become and Transform Your Life: How Small Habits Shape Who You Become and Transform Your Life: How Small Habits Shape Who You Become and Transform Your Life
J.T. Warren
No ratings yet
Mastering Python Advanced Concepts and Practical Applications
From Everand
Mastering Python Advanced Concepts and Practical Applications
Aissa Younes
No ratings yet
The Future of Learning: Revolutionizing Education Through Generative AI: AI Books, #11
From Everand
The Future of Learning: Revolutionizing Education Through Generative AI: AI Books, #11
Mohammad
No ratings yet
Plain JavaScript: Learning the Front-End
From Everand
Plain JavaScript: Learning the Front-End
Roger Beans-Rivet
No ratings yet
The Linux Terminal for Advanced Users - The Command Line Made Easy: First Edition
From Everand
The Linux Terminal for Advanced Users - The Command Line Made Easy: First Edition
Michael Basler
No ratings yet
Unlocking Statistics for the Social Sciences
From Everand
Unlocking Statistics for the Social Sciences
Norma Sinclair
No ratings yet
CAN Bus for Beginners: A Practical Guide to Automotive Networking
From Everand
CAN Bus for Beginners: A Practical Guide to Automotive Networking
Mohamad Charara
No ratings yet
Mastering Windows Automation with AHK 2.0
From Everand
Mastering Windows Automation with AHK 2.0
John Nunez
No ratings yet
The IPhone 12 Pro Photography User Guide: Your Guide For Smartphone Photography For Taking Pictures Like A Pro Even As A Beginner
From Everand
The IPhone 12 Pro Photography User Guide: Your Guide For Smartphone Photography For Taking Pictures Like A Pro Even As A Beginner
Wendy Hills
No ratings yet
Advanced Multiplayer Game Development with Ureal Engine 5: A Comprehensive Guide to C++ Scripting
From Everand
Advanced Multiplayer Game Development with Ureal Engine 5: A Comprehensive Guide to C++ Scripting
Vladimir Kiselev
No ratings yet
Breaking Barriers: S.T.E.M Mentorship in Business
From Everand
Breaking Barriers: S.T.E.M Mentorship in Business
Matthew C. Smith
No ratings yet
Blog Smarter, Not Harder: SEO, Blogging, and AI Strategies to Skyrocket Your Traffic
From Everand
Blog Smarter, Not Harder: SEO, Blogging, and AI Strategies to Skyrocket Your Traffic
Jay Nans
No ratings yet
BlockChain for Beginners
From Everand
BlockChain for Beginners
Matthew Smith
No ratings yet
Human Nature Potential in Nurture
From Everand
Human Nature Potential in Nurture
David L. Hawk
No ratings yet
Cybersecurity for Executives: A Guide to Protecting Your Business
From Everand
Cybersecurity for Executives: A Guide to Protecting Your Business
Matthew C. Smith
No ratings yet
Content Creation Revolution with chatGPT
From Everand
Content Creation Revolution with chatGPT
Maria Cowen
No ratings yet
ChatGPT for Business: Strategies for Success
From Everand
ChatGPT for Business: Strategies for Success
Matthew C. Smith
No ratings yet
Aquaponic Design Plans Everything You Needs to Know: Everything You Need to Know from Backyard to Profitable Business
From Everand
Aquaponic Design Plans Everything You Needs to Know: Everything You Need to Know from Backyard to Profitable Business
David H Dudley
No ratings yet
A Discourse Analysis of 1 Peter
From Everand
A Discourse Analysis of 1 Peter
Ervin Ray Starwalt
No ratings yet
Aquaponics Design Plans, Construction, Operation, and Income: Organic Food
From Everand
Aquaponics Design Plans, Construction, Operation, and Income: Organic Food
David H Dudley
No ratings yet
Osama the Gun
From Everand
Osama the Gun
Norman Spinrad
5/5 (1)
Viral Ipod Video
From Everand
Viral Ipod Video
MUHAMMAD NUR WAHID ANUAR
No ratings yet
Securing ChatGPT: Best Practices for Protecting Sensitive Data in AI Language Models
From Everand
Securing ChatGPT: Best Practices for Protecting Sensitive Data in AI Language Models
Matthew C. Smith
No ratings yet
A To Z of Internet: Everything You Wanted to Know
From Everand
A To Z of Internet: Everything You Wanted to Know
Bittu Kumar
No ratings yet
Gray Hat Hacking the Ethical Hacker's
From Everand
Gray Hat Hacking the Ethical Hacker's
Çağatay Şanlı
5/5 (1)
Intrusion Detection Honeypots
From Everand
Intrusion Detection Honeypots
Chris Sanders
3/5 (2)
10K Blueprint
From Everand
10K Blueprint
Cian O Farrell
5/5 (2)
Kellory the Warlock
From Everand
Kellory the Warlock
Lin Carter
No ratings yet
Software Patterns Made Easy
From Everand
Software Patterns Made Easy
Justice Nanhou
No ratings yet
Web Video Business
From Everand
Web Video Business
MUHAMMAD NUR WAHID ANUAR
No ratings yet