# ToolsTalk 2 (2.26)

## Software

# Introduction

In this section, you can find the basic information about the product and also the formatting conventions used in the topics.

# General Description

ToolsTalk 2 is ready to take your line management to the next level. The client-server-based software solution provides quick and easy configuration, as well as complete visibility and traceability to your entire line structure. Built on a state-of-the-art user experience and with an extended number of unique features, ToolsTalk 2 allows you to delegate additional features at any time to respective stations, through the embedded simple Functionality Management System (FMS). ToolsTalk 2 gives quality control in complex production systems and increase uptime in production critical operations.

# Conventions

To enhance user understanding, certain formatting conventions are used throughout this document. The formatting conventions used are listed below.

User Guide Conventions
Element | Notation | Description | Output
--- | --- | --- | ---
General emphasis | In the Program workspace. | To make certain text elements stand out, or to highlight. | Text in Bold
Graphical User Interface (GUI) items | Select the Function button. | Any reference to items found on screen in the GUI (for example, command buttons, icon names and field names). | Text in Bold
Graphical User Interface (GUI) Path > | Generally, on the top of the GUI. | Navigation aid which keeps track of the location in the GUI. | For example: Controller > Program > Edit
User input | Enter a Description for the program. | Any text input by the user. | Text in Bold
File names | Enter a File Name for the export. | Files either exported from, or imported into the system. | Text in Bold Italic
Variable and parameter names | Enter a Name for the export. | Variable and parameter names (not values). | Text in Italic
Variable and parameter values | Enter a VALUE for the export. | Variable and parameter values. | Text in BOLD CAPS
System output | Client.Domain.Models.ExportImportConfiguration | Any text output by the system. | Text in Monospace
External links | https://servaid.atlascopco.com www.atlascopco.com https://webbox.atlascopco.com/webbox/dimdrw | Links to external sites that have information connected to the document or subject content. These could include: Technical Product Data Dimensional Drawings Accessories Product Specific Information | Selectable text to external sites
Internal documentation links |  | Relevant Information - links to information which is directly related to the current topic and needs to be considered for certain configurations that are made. In this Section - links to all the topics within the section, which can be useful when understanding a feature, or configuration. If available, these links will be presented below the text. | Selectable text to internal content

# Liabilities and Warnings

# General Data Protection Regulation (GDPR)

This product offers the possibility to process personal identifiable information such as system user name, role and IP-address. The purpose of this processing capability could be to enhance quality control through traceability and proper access management.

If you decide to process personal data you need to be aware of and comply with relevant personal data protection rules, including, in the EU the GDPR as well as other applicable laws, directives and regulations. Atlas Copco can in no way be held liable for any use made by you of the product.

# Liability

Many events in the operating environment may affect the tightening process and shall require a validation of results. In compliance with applicable standards and/or regulations, we hereby require you to check the installed torque and rotational direction after any event that can influence the tightening result. Examples of such events include but are not limited to:

- initial installation of the tooling system

- change of part batch, bolt, screw batch, tool, software, configuration or environment

- change of air- or electrical connections

- change in line ergonomics, process, quality procedures or practices

- changing of operator

- any other change that influences the result of the tightening process

The check should:

- Ensure that the joint conditions have not changed due to events of influence.

- Be done after initial installation, maintenance or repair of the equipment.

- Occur at least once per shift or at another suitable frequency.

# General Data Protection Regulation (GDPR)

This product offers the possibility to process personal identifiable information such as system user name, role and IP-address. The purpose of this processing capability could be to enhance quality control through traceability and proper access management.

If you decide to process personal data you need to be aware of and comply with relevant personal data protection rules, including, in the EU the GDPR as well as other applicable laws, directives and regulations. Atlas Copco can in no way be held liable for any use made by you of the product.

# Revision History

ToolsTalk 2 Software version | Revision Date | Changes
--- | --- | ---
2.26 | 12/2025 | UPDATED content Prerequisites for Installation Compatibility Matrix Installation Overview Upgrading ToolsTalk 2 Installation Conditions Upgrading Process Description Installing the Client Application Installing the Client by Using ServerClickOnce NEW content Activated Joint Id - 225 Joint Id Result - 31046
2.25 | 04/2025 | UPDATED content Event Codes Open End in Open Position - 89 Updating Controller Software Working with the Virtual Station Tab Controller Fieldbus Mapping a Signal Configuration to One or More Virtual Fieldbuses Creating a Virtual Fieldbus Upgrading ToolsTalk 2 Prerequisites for Installation Compatibility Matrix Approval Statuses Fieldbus Sizes NEW content Ready to Operate For the Step Monitors page for Power Focus 6000 and Power Focus 8 and the Step Monitors page for FlexSystem and Synchronized tightening, the following steps are added: AZP - Adjust to Zero Position BA - Backlash Angle BM - Backlash Angle Measurement ZC - Zero Crossing
2.24 | 10/2024 | UPDATED content Working with the System Administration Tab: removed "External Links". Prerequisites for Installation and Installing the ToolsTalk Server Application: ports 22 and 80 can be changed during installation. The list of ports is updated. Information on how to enable HTTPS is added. To install ToolsTalk 2 version 2.24, .NET 8 is now required. Changes are made in Installation Overview, Prerequisites for Installation, and Installation Conditions. Some terms are changed, especially regarding "dual transducer" and to how transducers are referred. For example, instead of "primary angle" and "secondary angle", we now use "Angle" and "Angle 2", respectively. Upgrading ToolsTalk 2 contains all information about upgrade paths. The information was previously found in two different pages. Upgrading Process Description contains clarifications regarding versions, the Installation Configurator, and HTTPS-related settings that were introduced with ToolsTalk 2 v2.24 (Enable HTTPS and Server Authentication Certificate). Compatibility Matrix is updated with version 2.24 information. Installing the Client Application is updated with Enable HTTPS information. Installing the Client by Using ServerClickOnce is updated with Enable HTTPS information. NEW content Cyber Security Security List of Third-Party Licenses Controller Fieldbus For the Configuration for PF6000 and PF8 section, the following pages are added: Controller Fieldbus Prerequisites to Using Controller Fieldbus Creating a Controller Fieldbus Configuration Creating a Signal Configuration in the Controller Fieldbus Creating a Virtual Fieldbus Mapping a Signal Configuration to One or More Virtual Fieldbuses Mapping a Virtual Station to a Virtual Fieldbus Changing the Controller Offset For the Configuration for FlexSystem and Synchronized tightening section, the following pages are added: Controller Fieldbus Prerequisites to Using Controller Fieldbus Creating a Controller Fieldbus Configuration Creating a Signal Configuration in the Controller Fieldbus Creating a Virtual Fieldbus Mapping a Signal Configuration to One or More Virtual Fieldbuses Mapping a Virtual Station to a Virtual Fieldbus Changing the Controller Offset
2.22 | 03/2024 | UPDATED content Installing the Client by Using ServerClickOnceupdated regarding certificates Acyclic Result Itemsupdated with more detailded information Controller is Not Connecting to ToolsTalk 2updated Known InstallShield issueis the new title of the old section called Known Issues FMS - Uninstalling. Minor changes done in text. ToolsTalk Server does not Startupdated Logs to Include in Support Issuesupdated Installing the Station Setup Applicationupdated Handling Resultsupdated Controllersupdated with a new controller symbol Copying and pasting for tightening program updated in several sections of the User Guide Copying and pasting tightening programs (Configuration for PF600 and PF8), Copying and Pasting tightening programs (Configuration for FlexSystem and Synchronized Tightening), Tightening Program Library - Copying and Pasting Reference link added about rules for exporting and importing in Importing a Tightening Program and Importing a Multistep Program Copying and pasting for Batch Sequences and Sources updated in several sections of the User Guide Copying and pasting Batch Sequences and Sources (Configuration for PF600 and PF8), Copying and Pasting Batch sequences, Sync modes and Sources (Configuration for FlexSystem and Synchronized Tightening), All occurences of gear ratio changed to 100. All occurences of StepSync changed to Synchronized tightening or controller as applicable. NEW content Stopping error codesadded to Reference section. DELETED content Installation Pre-Requisites removed Known Upgrade Issues with Different ToolsTalk2 version removed ToolsTalk 2.13.4 with Atlas Copco Data Communication removed Toolstalk server does not Write to the Database ToolsTalk 2 is Not Connecting to Atlas Copco Data Communication Limitations
2.21 | 06/2023 | UPDATED content Migration to .NET6 done Changes done in Program Approval ToolsControl supported NEW content Upgrading ToolsTalk 2 from 2.20 to 2.21 added in Toolstalk 2 Installation and upgrade DELETED content The chapter "Enabling Microsoft MSMQ Server" removed and other information regarding MSMQ removed.
2.20 | 01/2023 | UPDATED content: Licences overview updated. Functionality Management System Definitions updated. The copy and paste instructions for Tightening programs, Batch sequences, Source Batch/Source Tightening and Sync modes replaced by a general instruction for Copy and Paste in TT2. Links and reference updated in RabbitMQ Overview. Installing OpenJDK made external Event codes updated
2.19 | 06/2022 | UPDATED content: Several limitations for StepSync are removed. General software improvements
2.18 | 01/2022 | NEW content: In multistep: Program Monitor: Time Program Restriction: Angle and Time In multistep: Step Type: Torque Calibration Step Monitor: Current and Torque Calibration. Step Restriction: Current. Extended logging Remote logging Open end configuration for PF6000 and PF8. Custom section folder implemented in Functionality Management System. IXB Tool Configuration - Vibrator New signals UPDATED content: General software improvements
2.17.1 | 09/2021 | NEW content: PF8 controllers are supported. Managing External links in System Administration tab. More filtering options in Tightening program tab. Possibility to delete the old configuration files when exporting controller configuration. More filtering options in Results tab. Information for RabbitMQ is added. UPDATED content: General software improvements
2.17 | 06/2021 | NEW content: PF6000 I/O Hub device is supported. Possible to export program details to .csv format from Controller tab, System Administration tab and Library tab. In multistep, more hold conditions are supported for Step Wait. In multistep, angle control processes is added for Step Restriction RT. In multistep for StepSync, signal for wait type is supported for SteySync. In multistep for StepSync, parameter Angle Window is added for Step Restriction RH. FlexSystem I/O Hub device is supported. Step Wait: Signal is supported for wait type. More hold conditions are supported. Optional parameter Program Start is added in Tightening Program Properties. Parameter Angle Window is added for Step Restriction RH. Angle control processes is added for Step Restriction RT. UPDATED content: Validating the ACDC Exchange Server Settings using a Server client and ClickOnce Server client Signal lists Event code list General software improvements DELETED content: Four step tightening strategy

Relevant Information

- Working with synchronized tightening

# System Overview

A manufacturing system may consist of the functional blocks in the figure:

A | Factory network. | H | Controller factory port: connected to the factory network.
B | ACDC: for storing tightening results and for statistical analysis. | I | Power Focus 6000 controller: used with handheld tools.
C | ToolsTalk 2 server: for configuration and parameter settings for controllers and IxB tools. | J | Handheld battery tool: uses a wireless connection to the controller.
D | Industrial PC (IPC): can be used as client terminal to the ToolsTalk 2 and ToolsNet servers. | K | PF6 Flex controller: used with fixtured tools.
E | Portable computer connected to the factory network: can be used as client terminal to the ToolsTalk 2 and ToolsNet servers. | L | IxB handheld battery tool: uses a wireless connection to the factory network.
F | Service computer: can be connected to the service port of a controller or an IxB tool. | M | The internet cloud.
G | Controller service port: can be used to connect a service computer. | N | Atlas Copco Licensing Portal (ACLP): located at Atlas Copco and provides support to licensed functionality in the Functional Management System (FMS).

In this Section

- Software Structure
- Configuration Options

# Software Structure

Global icons
Icon | Description
--- | ---
| The ToolsTalk 2 system user administration. Selection of language, temperature, controller event notifications and torque units.
| The Information icon shows the following: ToolsTalk 2 Software version. ToolsTalk 2 License type. ToolsTalk 2 Virtual Station information. Liability notice
| Selecting the Help icon opens the User Guide Selection window. Select the controller for which you need the user guide in the Tools Talk 2 User Guide for: drop-down list. The user will be navigated to the relevant user guide for that particular version of the software.
| Plant Structure Within the plant structure workspace, individual controllers are selected. The workspace is divided into several icons. The menus under each icon are used for configuration of data and parameter settings. The icons differ from the controller interface and the web interface but are very similar in the partitioning and the configurations that can be made under each.
| Tightening Program When selected, the workspace shows a list of existing tightening programs. Selecting an individual program opens the different menus to configure and set parameters for the selected tightening program.
| Batch Sequence When selected, the workspace shows a list of existing batch sequences. Selecting an individual batch sequence opens the different menus to configure and set parameters for the selected batch sequence.
| Sync Mode The icon is only available on controllers with parallel multistep capabilities. The workspace is used to configure and set parameters for all the synchronized multistep tightening programs.
| Sources The workspace is used to configure and set parameters for scanners. The workspace is used to configure how identifiers are used to select the next task.
| Configurations When selected, the workspace shows a list of existing configurations. The menus where to configure and set parameters vary depending on selected type of device: Operator Panel. Stacklight. Indicatorbox. General Virtual Station. Tool Configuration. Scanner. Socket Selector. I/O Expander. Internal I/O signals.
| Tools The workspace is used to display which tools are connected to the controller and to see and set tool maintenance intervals and calibration data.
| Virtual Stations When selected, the workspace shows a list of existing Virtual Stations. Selecting an individual Virtual Station opens the different menus to configure and set parameters for the following: Assign a tool to the Virtual Station. Assign accessories and select accessory configurations. Assign a task to the Virtual Station either manually or configure how external signals are used to assign the task. Enable communication protocols to factory management systems. View the fieldbus mapping, if it is used.
| Controller Information Controller hardware and software modules included in the controller.
| Fieldbus and SoftPLC The workspace is used to configure the Fieldbus and SoftPLC settings.
| Settings Controller preferences. Tool alarm settings. Controller network connections. Controller time and date configurations. Event code configuration.
| Results Displays the latest tightening results of a selected controller. Results can be shown in a table format or in graphical trace format.
| Events Displays the latest tightening events for a selected controller. Define what events to display in the event configurations in settings .
| Statistics Presents Statistical Process Control data from statistical calculations in terms of charts.
| Libraries Includes submenus for managing library templates that can be reused amongst controllers.
| Controller Library A library of controller configurations. It is very useful in Station Setup mode which provides a ToolsTalk 2 functionality on a single laptop computer without the need of a server installation.
| Program Templates Library This library contains multistep programs saved as templates to use when creating a new multistep program. Editing a multistep program template will not affect multistep programs based on that template.
| Tightening Program Library A library of tightening programs. It is possible to copy an existing tightening program to the library. Editing a tightening program in the library will affect all controllers that subscribe to the tightening program.
| Configurations Library A library of configurations for Virtual Stations, devices and accessories. It is possible to copy an existing configuration to the library. Editing a library configuration will affect all controllers that subscribe to the configuration.
| Fieldbus Library A library of fieldbus configurations. It is possible to copy an existing fieldbus configuration to the library. Editing a fieldbus configuration will affect all controllers that subscribe to the fieldbus configuration.
| Settings Library A library for Event configurations that can be distributed to other controllers. The events can be created here or in Settings Events and added to the library. Editing an Event configuration will affect all controllers that subscribe to the configuration.
| Sync mode library A library that contains sync mode templates that can be used to create and modify sync mode configurations and distribute them to multiple controllers.
| System Administration Includes functions for software update, import/export of configuration parameters, program approval, task scheduling and the functionality management system.
| Controller Software and Data Management Manages controller software through the ToolsTalk 2 server.
| Scheduled Export and Import Schedules repetitive tasks that affect one or many controllers and that are executed by the ToolsTalk 2 server.
| User Groups Manages different user groups and the user group rights to folders, controllers and configurations.
| Functionality Management System (FMS) Manages licensed controller functionality through the ToolsTalk 2 server.
| Program Approval Manages approvals for tightening and loosening programs.
| Push The push indicator is shown when configurations have been made to any controller in ToolsTalk 2. Configurations and parameter changes are copied to the controller via the Push function.

The controller icons differ from the controller GUI and the web GUI but are very similar in the partitioning and the configurations that can be made under each icon.

After a successful start of ToolsTalk 2 this view below is displayed, containing the icons described above:

Navigation overview

A | Left side menu bar | C | System menu bar
B | Plant structure workspace | D | Controller workspace

The controller workspace area displays different content, depending on the selected icon or menu.

# Configuration Options

The configuration and setting up of a controller can be done in the following ways:

- Controller GUI: This is applicable to Power Focus 6000 controllers which have a touchscreen. A controller can be configured regardless whether it is connected to the network or not.

- Web GUI: A PC can be directly connected to the controller service port or if the controller is connected to the network and its IP address is known, it can be accessed from a computer anywhere on the network. One controller at a time can be accessed. For a Power Focus 6000, the web-GUI has the same icons as the controller GUI. For a FlexController, the icons are slightly different. All controllers might have icons that could be unique to them.

- ToolsTalk 2 GUI: If the controller is connected to a ToolsTalk 2 server, a ToolsTalk 2 client (PC) can access all connected controllers through the ToolsTalk 2 GUI. Both Power Focus 6000 controllers and FlexControllers can be accessed. The GUI uses a full PC screen and has different partitioning and a different icon, but provides the same functionality.

- ToolsTalk 2 GUI in Station Setup mode: Provides a ToolsTalk 2 interface on a PC without a server installation. The PC is connected to the controller service port and provides access to one controller at a time.

# License Introduction

Licenses for controller features are managed through the Functionality Management System (FMS). FMS allows users to change controller functions to their specific needs through a dynamic licensing scheme.

Licenses can be obtained for individual features or collections of features and can be deployed across multiple Virtual Stations. The licenses can be returned to a license pool when they are no longer required. Licenses can be obtained through the Atlas Copco License Portal (ACLP). Licenses can be downloaded from the ACLP and managed/distributed through ToolsTalk, or can be stored on a FMS Portable (USB drive) to be inserted into the controller.

The creation and management of a customer account in the ACLP is not covered in this documentation. Contact your local Atlas Copco representative for more information.

# Licenses Overview

Configuration of features governed by licenses can be done even in the absence of an installed license. For example configuration of tightening programs and configuration of Multistep programs. Assigning these features to a tool or virtual station is also possible. Running the feature without a valid license, however, will require the installation of the appropriate license.

License enforcement is performed at two stages: assignment and runtime (trigger pressed). If a feature for which no license is installed is assigned to a Virtual Station, a red exclamation mark will appear at the Virtual Station View in ToolsTalk 2. The controller GUI will also show a warning triangle at the tool or task section (depending on what is missing). If a feature for which no license is installed is started (i.e. trigger pressed), an event will be presented to the user informing the user of which license is missing. It will not be possible to proceed without a correct license installed.

Running an unlicensed feature will, in most cases, result in a locked tool.

Many features and functions in the controller require a license in order to be assigned and used by a virtual station. There are four types of licenses:

## Virtual Station Type

Fixed collection of features bundled together in a single package. The Virtual Station Type determines, among other things, what tools can be run, how many programs and sequences can be used, which tightening strategies are available, and the type of reporting that can be done. The features contained in each Virtual Station Type are features that often are used in conjunction with each other, or which have internal dependencies that require the presence of other features in the package. Virtual Station Types are assigned in their entirety to a virtual station. The virtual station can then make use of all features contained in the Virtual Station Type. In order to be able to perform tightenings, a Virtual Station has to be assigned a Virtual Station Type license. Depending on the license type, various tightening options will be enabled or blocked.

## Sync Functionality Type

Works in the same way as described in Virtual Station Type but used for fixtured systems. To be able to run several tools on a virtual station each tool need a sync functionality license.

## Virtual Station Feature

Individual features which can complement Virtual Station Types. A lot of features can be purchased as a single license.

## Controller Feature

Features that are controller-wide. These are features which are assigned to a controller and once assigned can be used by all virtual stations on that controller.

# License Levels

## Line Licenser, Line Configurator and Line Manager

These three versions are all client-server based installations of ToolsTalk 2, but with different feature sets. Line Licenser is the smallest package in which ToolsTalk 2 enters on a clean installation, when neither of the other licenses have been installed. When ToolsTalk 2 has the status Line Licenser, all Line Manager and Line Configurator functionality will be visible, but a warning message will appear every time the user tries to use the included features.

ToolsTalk 2 will only remove, unlink, or delete data created in Line Manager, if a downgrade is initiated. This could happen for example when downgrading to a Line Configurator license, or if the trial period of the Line Manager license has expired.

## Station Setup

This is a version of ToolsTalk 2 where all the components are located locally on the computer, giving a one-to-one connection. Station Setup runs without an SQL server database connection and has a built-in limit that enables only one connected controller at a time. Note, a valid license is required to use Station Setup, otherwise a warning message will be displayed.

An unlicensed Station Setup can have one virtual station and this will be validated against the License Server.

## License Functionality

Symbol | Description
--- | ---
X | Full functionality.
X¹ | Connect, disconnect, and restart enabled.
X² | Push is enabled if changes are made.
X³ | Custom sections, restart, and right-click functionality enabled.
X⁴ | Only Database maintenance enabled.
X⁵ | Read access only, program export enabled.
X6 | ToolsTalk 2 Station Setup can only access controller results that are created while Station Setup is connected to the controller, i.e. the controller is online.

License Functionality Matrix
| Line Licenser | Line Configurator | Station Setup Licensed | Line Manager
--- | --- | --- | --- | ---
Plant Structure |  |  |  |
Right-click - Add new controller | X | X | X | X
Right-click functionality | X¹ | X | X | X
History on program configuration |  |  |  | X
Tightening Program | X⁵ | X | X | X
Batch Sequence | X⁵ | X | X | X
Sources | X⁵ | X | X | X
Configurations | X⁵ | X | X | X
Tools | X⁵ | X | X | X
Virtual Stations | X⁵ | X | X | X
Controller | X⁵ | X | X | X
Settings | X⁵ | X | X | X
Fieldbus | X² | X | X | X
SoftPLC |  | X | X | X
Results |  | X | X6 | X
Events | X | X | X | X
Library |  |  |  |
Tightening Program |  |  |  | X
Configurations |  |  |  | X
Fieldbus |  |  |  | X
Settings |  |  |  | X
Program Templates |  |  |  | X
Controller Configuration |  | X | X | X
System Administration |  |  |  |
Controller Software & Data Management |  | X³ | X³ | X
Scheduled Task | X⁴ | X⁴ | X⁴ | X
Functionality Management System (FMS) | X | X | X | X
User Groups |  |  |  | X
Program Approval |  |  |  | X

# Supported Tools

Tools supported by a Virtual Station may vary depending on the Virtual Station type on the controller.

Supported Tools | BatchControl | JointControl | StationControl | CriticalControl | ProcessControl
--- | --- | --- | --- | --- | ---
BCP / BCV | X | - | - | - | -
TensorSB | - | X | X | - | -
TensorSL | - | - | X | X | X
TBP | - | - | X | X | X
TensorST | - | - | X | X | X
TensorSTR | - | - | X | X | X
SRB | - | - | X | X | X
TensorSTB | - | - | X | X | X
STWrench | - | - | X | X | X
TensorES | - | X | X | - | -
TensorSR | - | - | X | X | X
QST (Fixtured spindle) | - | - | X | X | X
TBPS | - | X | X | - | -
MWR-S (Mechatronic Wrench Signal) | - | - | - | - | -
MWR-T (Mechatronic Wrench Torque) | X | X | X | X | -
MWR-TA (Mechatronic Wrench Torque Angle) | - | - | X | X | X
External tool | X | X | X | X | X
ITB-A | - | - | X | X | X
ICB-A | - | - | X | X | X
ITB-P | - | - | X | X | X

# Security

This page lists ToolsTalk 2 user-guide contents that are related to cyber security.

- Cyber Security

## Enabling HTTPS for ToolsTalk 2

- Upgrading Process Description

- Installing the ToolsTalk Server Application

- Installing the Client by Using ServerClickOnce

- Installing the Client Application

Relevant Information

- List of Third-Party Licenses

# Installation and Upgrade

In this section, you can find information to help with the initial installation of the product, or upgrading from one version to another.

# Installation Overview and Requirements

# Cyber Security

WARNING

Risk of system control loss and exposure of proprietary data

- Do not install the product with a direct interface or connection to a Public Network outside the control of the user of this product, as for example Internet.

- Make sure that systems connected to the product are under your full control. Make sure that these interfaces and systems are protected by security firewall(s) with relevant and appropriate physical and digital authentication, access control and other necessary security measures applied in the product's environment, for example digital network, to securely access and operate the product.

- The product shall be isolated from those parts of the network(s) that are not designed or required for the product.

# Compatibility Matrix

All versions of ToolsTalk 2 software are backwards compatible unless stated otherwise

ToolsTalk2 | PF6 FlexSystem | PF6000 | PF6000 Synchronized tightening | Atlas Copco Data Communication Version | IXB | PF8 | PF8 Synchronized tightening | Tools Control
--- | --- | --- | --- | --- | --- | --- | --- | ---
2.3 | N/A | 2.0, 2.1, 2.1.1, 2.3 | N/A | N/A | N/A | N/A | N/A | N/A
2.4 | N/A | 2.4 | N/A | N/A | N/A | N/A | N/A | N/A
2.5 | 1.2 | 2.4 | N/A | N/A | N/A | N/A | N/A | N/A
2.6 | 1.2 | 2.5 | N/A | N/A | N/A | N/A | N/A | N/A
2.7 | 1.3 | 2.6 | N/A | N/A | N/A | N/A | N/A | N/A
2.7.1 | 1.3.1 | 2.6 | N/A | N/A | N/A | N/A | N/A | N/A
2.8 | 1.3.1 | 2.7 | N/A | N/A | N/A | N/A | N/A | N/A
2.9 | 2.0 | 2.7 | N/A | N/A | N/A | N/A | N/A | N/A
2.11 | 2.1 | 2.8 | N/A | N/A | N/A | N/A | N/A | N/A
2.12 | 3.0 | 3.0 | 3.0 | N/A | N/A | N/A | N/A | N/A
2.13 | 3.1 | 3.1.1 | 3.1.1 | 1.7 | N/A | N/A | N/A | N/A
2.14 | 3.3 | 3.3 | 3.3 | 1.9 | 3.3 | N/A | N/A | N/A
2.15 | 3.4 | 3.4 | 3.4 | 1.11 | 3.4 | N/A | N/A | N/A
2.16 | 3.5 | 3.5 | 3.5 | 1.13 | 3.5 | 3.5 | 3.5 | N/A
2.17 | 3.6 | 3.6 | 3.6 | 2.1.3 | 3.6 | 3.6 | 3.6 | N/A
2.18 | 3.7 | 3.7 | 3.7 | 2.2.2 | 3.7 | 3.7 | 3.7 | N/A
2.19 | 3.8 | 3.8 | 3.8 | 2.4 | 3.8 | 3.8 | 3.8 | N/A
2.20 | 3.9 | 3.9 | 3.9 | 2.5 | 3.9 | 3.9 | 3.9 | N/A
2.21 | 3.10 | 3.10 | 3.10 | 3.0 | 3.10 | 3.10 | 3.10 | 3.6–3.10
2.22 | 3.11 | 3.11 | 3.11 | 3.0 | 3.11 | 3.11 | 3.11 | 3.6–3.11
2.24 | 3.13 | 3.13 | 3.13 | 3.4 | 3.13 | 3.13 | 3.13 | 3.6–3.13
2.25 | 3.14 | 3.14 | 3.14 | 3.5 | 3.14 | 3.14 | 3.14 | 3.6–3.14

ToolsTalk 2 can run with higher versions of Atlas Copco Data Communication. The Atlas Copco Data Communication version mentioned in the matrix is to be considered as the lowest version the ToolsTalk 2 software is compatible with.

# Installation Overview

## Before Installing or Upgrading

It is not recommended to have both a Station Setup and a Client-Server installation on the same computer. Make sure to uninstall and clear the computer from the components of the unwanted installation.

The Microsoft SQL database, the ToolsTalk 2 server application and the ToolsTalk 2 client application, can all be installed on the same computer.

## Server Installation

Step | To do | Check
--- | --- | ---
1 | Check that administrator rights are available for the computer upon which the application is to be installed. | ░░
2 | Check that administrator rights are available for the computer upon which the client application is to be installed. | ░░
3 | Check that Computers and programs are available according to the listed Prerequisites. | ░░
4 | Check that installation of the 64-bit Microsoft SQL database according to the listed Prerequisites is completed. | ░░
5 | An executable file is available for the server application. | ░░
6 | An executable file is available for the client application. | ░░
7 | Atlas Copco Data Communication (ACDC) is installed and running and is compatible with the current version of ToolsTalk 2 (only for versions of ToolsTalk 2 from 2.13 onwards). Please see the Atlas Copco Data Communication Installation User Guide. | ░░

## Station Setup Installation

Step | To do | Check
--- | --- | ---
1 | Check that administrator rights are available for the computer upon which the application is to be installed. | ░░
2 | Check that computers and programs are available according to the listed Prerequisites. | ░░
3 | An executable file is available for the Station Setup application. | ░░

## Infrastructure

Step | To do | Check
--- | --- | ---
1 | Decide on server type (virtual or physical). | ░░
2 | Decide on database location (local or remote). | ░░
3 | Decide on authentication type (none or Windows Active Directory). | ░░
4 | Verify that amount of RAM on application server is sufficient. See Prerequisites for Installation | ░░
5 | Verify that disk space for database is sufficient. See Prerequisites for Installation | ░░

## Installation

Step | To do | Check
--- | --- | ---
6 | Windows Server 2019 or higher installed on application server. | ░░
7 | Ports are open on servers. See Software Installation and select individual installation type to see port information. | ░░
8 | SQL Server 2019 or higher. | ░░
9 | .NET 8 | ░░
10 | Read through the Installation and Upgradeof the ToolsTalk 2 User Guide (latest version). | ░░
11 | Install and Configure JAVA. See Installing and Configuring JAVA. | ░░
12 | Install the latest version of the Atlas Copco Data Communication (ACDC). See Atlas Copco Data Communication Installation User Guide. | ░░
13 | Install the latest version of ToolsTalk 2, see Software Installation. | ░░
14 | Start services. | ░░

## Configuration

Step | To do | Check
--- | --- | ---
15 | Upload the license file. See Functionality Management System (FMS) | ░░
16 | Configure a database maintenance scheduled task. See Database Maintenance | ░░

## Upgrade (Client/Server and ClickOnce)

Step | To do | Check
--- | --- | ---
1 | Make sure the ToolsTalk 2 service is running. | ░░
2 | If you do not want to change the installation configurations, select Save in the installation configurator. | ░░

Relevant Information

- Installation and Upgrade

# Prerequisites for Installation

## Database Requirements

All controller data and configurations are stored in the database catalog. The database is a standard 64-bit Microsoft SQL database.

The installation of a Microsoft SQL database is not described in this document. It is recommended to follow standard installation instructions.

- If the SQL database is not located on the same network as the ToolsTalk 2 application server, firewalls may need to be configured to allow traffic between the database server and the ToolsTalk 2 application server.

- The IP address of the Atlas Copco Data Communication server must be entered into every controller that is connected to ToolsTalk 2

- The server address that hosts the ToolsTalk 2 application must be known by the client PC if a remote connection is being used.

Mandatory when installing the Microsoft SQL database

- 64-bit Microsoft SQL Server

- Authentication mode: both Microsoft SQL server authentication and Windows authentication

Recommended when installing the Microsoft SQL database

- Install SQL Server Management Studio

- Enable the default instances.

## Other Requirements

The ToolsTalk 2 ecosystem requires the following functions to be in place:

64-bit is required for client, server, Station Setup and ClickOnce.

The ToolsTalk 2 server and PC client software require .NET 8.

Computer requirements
Area | Category | Minimum Requirement | Comments
--- | --- | --- | ---
a If fewer than 150 controllers are connected, use 4 physical CPU cores. If more than 150 controllers are connected, use 8 physical CPU cores.
Server software requirements | Database | SQL Server 2019, or later version SQL express 2019, or later version (Compatible but not recommended) | The database can be located locally on the same machine, or installed on a remote database server.
Java | Oracle Java SE 17 or OpenJDK 17 | 64-bit version
.NET 8 | SDK 8.0.204 (×64) | TT2 Server
SDK 8.0.204 (×64) and SDK 8.0.204 (×86) | TT2 Client and TT2 StationSetup
Server hardware requirements | Processor | Intel XEON Dual processor, 2.3 GHz or highera | This specification is only meant to give an indication of the performance needed.
Memory (RAM) | 64 GB | This specification is only meant to give an indication of the performance needed.
Disk space | 100 GB | Note that the database will grow over time. Configurations and configuration changes are stored to the database. More controllers will also add more info to the database.
PC client requirements | Operating system | Windows 11 |
.NET 8 | SDK 8.0.204 (×64) and SDK 8.0.204 (×86) |
User rights | Database access | System administrator access or similar | Users performing the installation, must also have admin rights to create users in the database.
Windows access | Administrator account | Needed in order to install the application and its dependencies.

## Ports

Make sure that the following ports can be reached through the network. A company IT department can usually verify that the ports can be reached through the network.

- 22 (only applicable for the server when SoftPLC is used or required)

- 80 (only applicable for the server)

- 7070

- 9016 (HubPort or a custom port number)

- 9101 (or a custom port number)

If port 80 is changed to a different value, the change must also be made on all connected controllers.

Port 80 can only be changed during the server installation.

## License Requirements

An Atlas Copco license server is needed when the Functional Management System (FMS) is being used for licensed Feature items.

The license server is included in the server installation file. For correct installation the JAVA_HOME system variable must have a correct path and point at the 64-bit Java installation.

The FMS can only be used in a client-server installation and is not applicable in a Station Setup installation.

# Installation Architecture

## Client/Server and ClickOnce

## StationSetup

In this Section

- Installation Options Client/Server and ClickOnce
- Installation and Upgrades

# Installation Options Client/Server and ClickOnce

## Client, Server and ACDC separate

## Server and ACDC on same server

# Installation and Upgrades

# Installation Types

ToolsTalk 2 has four different executables corresponding to four different execution strategies.

- Client

- Server

- Server and ClickOnce Client

- Standalone Station Setup

As common feature, all of the setups are Microsoft standard MSI executables produced with InstallShield software.

# Installation Conditions

InstallShield MSI executables has preconditions before the execution depending on the type of installer package. These conditions are listed as follows:

- .NET 8

- Java installation and configuration set up in system

Requirement and Check | Client | Server | Server and ClickOnce | Station Setup
--- | --- | --- | --- | ---
.NET 8 | X | X | X | X
Java Installation Check | - | X | X | -

If InstallShield cannot find these components on the installed machine then it shall inform user and notify about the missing components. Setup cannot continue without the above software dependencies missing, installers shall inform user and stop the set up.

# Installation Process Description

## InstallShield

All InstallShield MSI executables will add the ToolsTalk 2 executables in predefined folder location which defaults to Program Files\Atlas Copco folder and inside a new folder associated with setup type listed in the section Installation Types

Necessary registry settings shall be put into system to identify the existing installations for upgrades. A database shall not be created immediately but it shall be created after the Installation Configurator execution.

After installation is completed successfully on the machine, final step is to execute the Installation Configurator.

Feature & Script | Client | Server | Server and ClickOnce | Station Setup
--- | --- | --- | --- | ---
Install Client Assemblies | x | - | x | x
Install Server Assemblies | - | x | x | x
Install FMS Assemblies & Start Services | - | x | x | -
Install Installation Configurator Assemblies | x | x | x | x
Install ClickOnce Application | - | - | x | -
Certificate Registrations | - | - | x | -
Installation Configurator Execution | x | x | x | x
ACDC Common Components | - | - | - | x
ToolsTalk 2 Station Setup Specific Database Operations | - | - | - | x

ToolsTalk 2 Station Setup database operations involve creating necessary database operations for both ToolsTalk 2 and Atlas Copco Data Communication.

## Installation Configurator

After the installation step, the Installation Configurator will start automatically and the user can configure the ToolsTalk 2 software. It’s also possible to start configurator later through Windows Start Menu to change the settings and configurations.

Relevant Information

- Installation and Upgrades

# Upgrading Process Description

## Upgrade Definition

New versions of the existing ToolsTalk 2 installations on computer shall search for existing installations and decide if the installation should act like an upgrade or fresh installation. MSI specific rule set shall be executed to decide if the installation is an upgrade or fresh installation.

Through version numbers it can be determined if an upgrade is a Major upgrade or Minor upgrade

Example: 2.21.2 to 2.21.3 is a Minor upgrade but 2.21 to 2.22 is a Major upgrade. This difference is only important for database upgrade operations. During Minor upgrades database upgrade is not necessary so operation shall not occur.

## InstallShield

As common in all installation types mentioned in section in, Installation Types assemblies in system shall be upgraded with newer versions.

Depending on installation type, the following operations shall be performed in addition to updating assemblies:

- FMS Uninstall and Re-install (see section Installation Process Description to see which setup type installs FMS assemblies)

- Database migration (during Server and ServerClickOnce installation)

## Database Migration

During installation of Server and ServerClickOnce packages, Database migration operation shall start to upgrade the database of ToolsTalk 2 application. This operation is only executed during Major upgrades.

## Installation Configurator

Modification of following configurations are enabled by installation configurator:

- ToolsTalk 2 SQL database settings

  - SQL server address

  - ToolsTalk 2 database name

  - Database installation

- ToolsTalk 2 server settings

  - Authentication mode

  - Active directory to be used by Windows authentication

  - ToolsTalk 2 server address

  - ToolsTalk 2 server web application port

  - Enable HTTPS

  - Server Authentication Certificate

  - Controller port

  - Setting for converting service URL to IP address

  - Power Focus Web Server: alternative port

  - ClickOnce: certificate (optional)

- ToolsTalk 2 backup settings

  - Controller backup folder

- ACDC settings

  - ACDC server address

  - ACDC WebAPI port

  - ACDC SignalR port

  - Exchange Server settings

    - Validate

    - Use ACDC Configuration

- FMS settings

  - Get host ID Information

  - Default host ID

  - List of available host IDs

  - Active host ID

  - Update Active host ID

  - Last used active host ID

  - Possibility to change active host ID

Some of above settings and configurations may not be available for different versions of ToolsTalk 2.

When user modifies the configuration, the modification is applied by selecting the Save button. When saving the configurations, the Installation Configurator will

1. Update related config files with new values

2. Store a copy of all settings locally in a file named Storage

3. Start ToolsTalk 2 server to get the new configuration changes

At startup, the installation configurator always compares the configuration stored in storage file and config files exists at installation folder. If they differ, then it asks the user to choose which one should be loaded in installation configurator. When you select the Save button, both storage and config files in installation folder will get the same settings and configuration.

Relevant Information

- Installation and Upgrades

# Installing ToolsTalk 2

This Installation Guide will help you to install the ClickOnce application, Server, Client or Station Setup and help you to set up an SQL server, configure Atlas Copco Data Communication, and install JAVA .

The guide is laid out to show the different stages of an installation and in which order they need to be done.

In this Section

- Installation Sequence
- Installing Atlas Copco Data Communication
- Installing and Configuring JAVA
- Software Installation
- Installation Validation

# Installation Sequence

The installation sequence for any of the ToolsTalk 2 applications should be as follows:

1. Make sure all the computer and database requirements are met before installation.

2. Install the Microsoft SQL server.

   Refer to https://docs.microsoft.com/en-us/sql/database-engine/install-windows/install-sql-server?view=sql-server-ver15 for the correct installation procedures.

3. Install Atlas Copco Data Communication if applicable.

   Refer to the Atlas Copco Data Communication Installation guide for further information.

4. Install the required ToolsTalk 2 application.

5. Deploy the ToolsTalk 2 application if installing the ToolsTalk 2 client application or run the application from the start menu and create shortcuts if required.

6. License the ToolsTalk 2 application so you get the right features you subscribed to.

# Installing Atlas Copco Data Communication

Refer to the Atlas Copco Installation Guide and install the Atlas Copco Data Communication application.

# Installing and Configuring JAVA

1. Download and Install JAVA.

2. Navigate in Windows to Control Panel\System and Security\System and then select Advanced system settings.

3. Select Environment Variables...

4. In System variables, select New...

5. In the New System Variable dialog, input JAVA_HOME in the Variable name field. Use the Browse directory option and find the JAVA installation folder.

   Select OK to continue.

6. JAVA_HOME will now be added to the System Variables section, as seen in the image below.

   Select OK to continue.

# Software Installation

# ToolsTalk2 Configuration Window

With the ToolsTalk 2 configuration, it is possible to finish the installation of the ToolsTalk 2 software first and then configure the different installation parameters. The ToolsTalk 2 configuration for each installation type is available as a shortcut in the start menu after the installation and so it can be accessed anytime to make changes to the installation parameters.

# Default Installation Locations

Default Folder Locations
Installation | Default Location | Remarks
--- | --- | ---
ToolsTalk 2 Server | C:\Program Files\Atlas Copco\ToolsTalk Server\ | Can be changed to a desired location by the user
ToolsTalk 2 ClickOnce | C:\Program Files\Atlas Copco\ToolsTalk ClickOnce\ | Can be changed to a desired location by the user
ToolsTalk 2 Client | C:\Program Files (x86)\Atlas Copco\ToolsTalk Client\ | Can be changed to a desired location by the user
ToolsTalk 2 StationSetup | C:\Program Files (x86)\Atlas Copco\ToolsTalk StationSetup\ | Can be changed to a desired location by the user
AtlasCopco FMS | C:\ProgramData\AtlasCopcoFMS\ | The default path should not be changed!
Flexera Logs | C:\Windows\ServiceProfiles\NetworkService\Flexnetls\acopco\logs | The default path should not be changed!

# Installing the ToolsTalk Server Application

Before you begin with the ToolsTalk 2 server installation, make sure all the requirements are met as described in section Before Installing or Upgrading.

Before installing the Server Application, make sure that the Atlas Copco Data Communication (ACDC) installed and running is compatible with the current version of the ToolsTalk 2 (only for versions of from 2.13 onwards). Please see the Atlas Copco Data Communication Installation User Guide.

1. Place the executable file ToolsTalkServer<xxx>.exe in a desired folder on your computer. The <xxx> represents the version of the file.

2. Double-click on the executable file.

3. Select Yes to Do you want to allow this app to make changes to your device?

4. Select Next in the Atlas Copco Tools Talk Server - InstallShield Wizard window to continue.

5. Read and then select I accept the terms in the license agreement. Select Next to continue.

   Select Print if you would like to print the license agreement.

6. Select Change... to install the application in a different location. The default location is C:\Program Files\Atlas Copco\ToolsTalk Server\

   Select Next to continue.

7. Select Install to finish the installation.

8. Select Finish to complete the installation and the ToolsTalk 2 Configuration window opens up or the User Access Control dialog from Windows may be prompted.

9. If Windows prompts the User Access Control dialog requesting permission, Select Yes to Do you want to allow this app to make changes to your device?

   When the installation is completed, the ToolsTalk 2 Configuration window opens up.

   If an error occurs during installation, a step is unclear, or a parameter name or value is unclear, look for more information in the Troubleshooting section.

10. Enter the parameters in the FMS tab. Select Get Host ID Information to start the FMS and get the Host ID.

    If you want to change the Host ID, select from the Host IDs drop-down list and select Update Active Host ID to update the Active Host ID if needed.

11. Enter the parameters in the Database Settings tab.

    When the parameters in the SQL Server Address and/or Database name are added/updated, it is saved automatically.

12. Enter the parameters, User name and Password in the Database Credentials and select Test Connection.

    The User name and Password should be the same as used for the Microsoft SQL Server installation.

    If you select Test Connection, the configurator checks if the provided username and password are correct. If Test Connection fails, an error “Database connection test failed, see log file for details!” appears.

13. Select Install Database.

    Upon successful installation of the database, the message Database creation succeed is displayed.

14. Enter the parameters in the Server Settings tab.

    To enable HTTPS for the Web API in ToolsTalk 2 Server and ClickOnce, select Enable HTTPS and select a certificate from Local Machine Certificate Store > Personal on the Windows machine where ToolsTalk Server is installed. The certificate must be set up before Atlas Copco Data Communication Service is installed. The certificate will not automatically be generated. The certificate must include the Server Authentication purpose.

15. Enter the parameters in the ACDC Settings tab.

16. Select Save and the Status tab is displayed.

    When performing an installation for the first time, If you select the Status tab before entering all the parameters in the FMS, Database Settings and Server Settings tabs, the status are greyed out and an error "Installation Incomplete. Finish the installation to view the status" is displayed.

## FMS

Installing the ToolsTalk Server application is dependent on the FMS service for licensing. FMS services uses system identifiers, called Host ID, for identification and setting licenses. The features available in ToolsTalk 2 are tied to a Host ID used by a particular client and this value is registered on the Atlas Copco license portal. If you want to change the Host ID, the new Host ID must be registered on the Atlas Copco license portal by replacing the old Host ID and this will then move all the features tied to the old Host ID to the new Host ID.

This functionality allows you to read a list of Host IDs used in the past, the currently used active Host ID and the default Host ID and also allows you to change the active Host ID as required to suit network interfacing requirements.

Select Get Host ID Information to get the active Host ID being used.

FMS Settings
Parameters | Description
--- | ---
Default Host ID | Default Host ID which is registered. Default Host ID can be any available Host ID on the machine. It is usually the first Host ID in the list of Host IDs'
Host IDs | List of available Host IDs available on a particular machine depending on the different network interfaces.
Active Host ID | Current Host ID which is active and is being used. Default Host ID is overwritten by Active Host ID if it is specified
Last Used Active Host ID | Indicates which was the last Active Host ID used.

To change the active Host ID:

1. Select the required Host ID from the Host IDs drop-down.

   This is now also reflected in the Active Host ID field.

2. Select Update Active Host ID.

3. Select Save.

The active Host ID is now changed and the FMS services can be restarted for the new settings to be applied.

## Server Settings Parameters

Server Settings Parameters
Parameters | Description
--- | ---
Authentication Mode | The authentication mode used to verify user authority. Select Windows (Active directory) or None.
Active Directory Group | Only visible if the Authentication Mode selected is Windows. Specifies what active directory group a user must be member of. Example: Must always be in the format DOMAINNAME\GROUPNAME If the Authentication Mode selected is Windows, then you can test if active directory group is correct and if the user account you would like to use belongs to the active directory group. Enter the Active Directory Group and select Test AD Group. Enter the User Account and select Test, to verify the active directory group and the group name. An error message is displayed if the user has entered a wrong domain name or wrong group name or both. An error is also displayed if the entered domain name and group name are correct but the user account entered does not belong to that active directory group. An information message is displayed if the test was successful.
Server Address | IP or Hostname of the ToolsTalk 2 Server.
Web Application Port | Communication port for ToolsTalk 2. Select Test Tools Talk Server to check if the ToolsTalk 2 server is up and running. This functionality tests and verifies if the Server Address and the Web Application Port entered is working correctly. If the ToolsTalk 2 server is up and running, an information message appears to indicate that the test succeeded and if there is any issue with ToolsTalk 2 server, an error message is displayed with some more information in the log file.
Controller Port | Port 9016 is used as the default controller port. If using the port 9016, make sure this port is open and you can connect to it, else the application will not work. Port 80 is used when the function Connect/disconnect/add controller is used from ToolsTalk 2 to interact with a controller. If you enter a controller port that is not the same as the configured controller port on Atlas Copco Data Communication, a warning is displayed. Make sure that the controller port on ToolsTalk 2 and Atlas Copco Data Communication is the same. Port 80 can be changed during installation. For more information, see Prerequisites for Installation.

Make sure that the controller port you enter is open and is possible to connect to!

Backup
Parameters | Description
--- | ---
Controller Backup Folder | Specifies a folder where the backup for the controllers will be located.

The Active Directory Group and Controller Backup Folder are empty by default.

## ACDC Settings

ACDC Communication Settings
Parameters | Description
--- | ---
Server Address | IP or Hostname of the Atlas Copco Data Communication server
Web API Port | Port for Web API

## Validating the ACDC Exchange Server Settings

The parameters of the exchange server settings should be the same on both Atlas Copco Data Communication and ToolsTalk 2. It is possible to verify if the parameters are the same by using the Validate option in the ACDC Settings tab.

1. Enter the parameters in the Exchange Server Settings field.

2. Select Validate.

   If the parameters entered as correct the validation is successful.

   If the parameters entered are not the same as present in Atlas Copco Data Communication, then an error "The configured value is not equal to the corresponding ACDC value" is displayed.

3. Select Use ACDC Configuration if the validation failed.

   This will replace the incorrect parameters in the ToolsTalk 2 exchange server configuration with the parameters present in the ACDC configuration.

Exchange Server Settings
Parameters | Description
--- | ---
Exchange server topic name | The topic name of the exchange server used for communication between Atlas Copco Data Communication and ToolsTalk 2
Exchange server address | IP address of the exchange server.
Exchange server port | Port of the exchange server.
Exchange server username | Username used to access the exchange server.
Exchange server password | Password for the exchange server.

## Database Installation Settings

Database Settings Parameters
Parameters | Description
--- | ---
SQL Server Address | IP or Hostname of the SQL Server The Microsoft Windows Defender Firewall will prevent connections through the network to SQL Server. Therefore, it is required to configure SQL Server to accept connections by using TCP/IP. This setting can be modified in section SQL Server Configuration Manager in Windows Computer Management. Computer Management -> SQL Server Configuration Manager -> SQL Server Network Configuration -> Protocols for MSSQLSERVER -> TCP/IP -> Enabled
Database Name | The Database/Catalog used by ToolsTalk 2. The database will be created during database installation if not already existing.

Database Credentials
Parameters | Description
--- | ---
User name | The username of a database user with the credentials to create databases/catalogs. Usually the system administrator credential.
Password | Enter the password. Usually the system administrator credential

Installation
Parameters | Description
--- | ---
Manual Script | Specifies whether or not the database has been manually created. If this box is checked, ToolsTalk 2 expects that you have already created the SQL catalogue and the default user manually. The entered User Name and Password will be the default credentials that connects to the SQL server and are stored in clear text in the configuration files. This setting should be only used if you have created the database catalogue and user yourself.

The ToolsTalk 2 application is available in the start menu.

## Status

Parameters | Description
--- | ---
Refresh | Refreshes the status view and updates with the latest status of the services involved.
Start | Start a service for the first time.
Stop | Stops the service.
Restart | Restarts a stopped service.

If the Atlas Copco Data Communication is installed in a different server compared to ToolsTalk 2, it is not possible to view or modify the status of the Atlas Copco Data Communication service.

Relevant Information

- Compatibility Matrix
- Troubleshooting - Internal

# Installing the Client Application

Before you begin with the ToolsTalk 2 client installation, make sure all the requirements are met as described in section Before Installing or Upgrading.

1. Place the executable file ToolsTalkClientxxx>.exe in a desired folder on your computer. The <xxx> represents the version of the file.

2. Double-click on the executable file.

3. Select Yes to Do you want to allow this app to make changes to your device?

4. Select Yes in the Atlas Copco Tools Talk Server - InstallShield Wizard window to continue.

5. Read and then select I accept the terms in the license agreement. Select Next to continue.

   Select Print if you would like to print the license agreement.

6. Select Change... to install the application in a different location. The default location is C:\Program Files (x86)\Atlas Copco\ToolsTalk Client\

   Select Next to continue.

7. Select Install to finish the installation.

8. Select Finish to complete the installation.

   If an error occurs during installation, a step is unclear, or a parameter name or value is unclear, look for more information in the Troubleshooting section.

   When the installation is completed, the ToolsTalk 2 Configuration window opens up.

9. Enter the parameters in the Client Settings and select Save.

   Server Settings
   Parameters | Description
   --- | ---
   Authentication Mode | The authentication mode used to verify user authority. Select Windows (Active directory) or None.
   Prompt For Windows Credentials | When the checkbox is selected, ToolsTalk 2 asks for Microsoft domain credentials. When the checkbox is not selected, ToolsTalk 2 uses the user credentials of the user that is currently signed in to Windows.
   Server Address | IP or Hostname of the ToolsTalk 2 Server.
   Web Application Port | Communication port for ToolsTalk 2. Select Test Tools Talk Server to check if the ToolsTalk 2 server is up and running. This functionality tests and verifies if the Server Address and the Web Application Port entered is working correctly. If the ToolsTalk 2 server is up and running, an information message appears to indicate that the test succeeded and if there is any issue with ToolsTalk 2 server, an error message is displayed with some more information in the log file.
   Enable HTTPS | HTTPS communication between the client and ToolsTalk Server is enabled by selecting Enable HTTPS. This feature requires HTTPS to be enabled in ToolsTalk Server. For more information on how to set up HTTPS communication in ToolsTalk Server, see Installing the ToolsTalk Server Application. If HTTPS is enabled in ToolsTalk Server and ClickOnce clients are used, these clients will automatically be configured to use HTTPS.
   Convert Service URL to IP Address | On or Off. When On is selected, if a hostname is used in the address, it is converted to an IP address.

The ToolsTalk 2 application is installed and a shortcut available on the desktop.

# Installing the Client by Using ServerClickOnce

Important notice about releases before 2.21.3:

The certificate used for signing ClickOnce installers has expired in these releases. Existing server/client installations will continue to work, but when installing new clients, "Unknown Publisher" will be shown in a warning dialog. If your system only allows installation of applications signed with trusted certificates, new clients cannot be installed. To solve these issues, upgrade to release 2.21.3 or later and assign a trusted certificate. The clients must be re-installed after upgrading. See "ClickOnce Client" below for more information.

Installing the Client

1. Save the executable file ToolsTalkServerClickOnce<xxx>.exe in a desired folder on your computer. The <xxx> represents the version of the file.

2. Double-click on the executable file.

3. Select Yes to Do you want to allow this app to make changes to your device?

4. Select Next in the Atlas Copco Tools Talk Server ClickOnce - InstallShield Wizard window to continue.

5. Read and then select I accept the terms in the license agreement. Select Next to continue.

   Select Print if you would like to print the license agreement.

6. Select Change... to install the application in a different location. The default location is C:\Program Files\Atlas Copco\ToolsTalk ClickOnce\

   Select Next to continue.

7. Select Install to finish the installation.

8. Select Finish to complete the installation and the ToolsTalk 2 Configuration window opens up or the User Access Control dialog from Windows may be prompted.

9. If Windows prompts the User Access Control dialog requesting permission, Select Yes to Do you want to allow this app to make changes to your device?

   When the installation is completed, the ToolsTalk 2 Configuration window opens up.

   If an error occurs during installation, a step is unclear, or a parameter name or value is unclear, look for more information in the Troubleshooting section.

10. Enter the parameters in the FMS tab. Select Get Host ID Information to start the FMS and get the Host ID.

    If you want to change the Host ID, select from the Host IDs drop-down list and select Update Active Host ID to update the Active Host ID if needed.

11. Enter the parameters in the Database Settings tab.

    When the parameters in the SQL Server Address and/or Database name are added/updated, it is saved automatically.

12. Enter the parameters, User name and Password in the Database Credentials and select Test Connection.

    The User name and Password should be the same as used for the Microsoft SQL Server installation.

    If you select Test Connection, the configurator checks if the provided username and password are correct. If Test Connection fails, an error “Database connection test failed, see log file for details!” appears.

13. Select Install Database.

    Upon successful installation of the database, the message Database creation succeed is displayed.

14. Enter the parameters in the Server Settings tab.

15. Enter the parameters in the ACDC Settings tab.

16. Select Save and the Status tab is displayed.

    When performing an installation for the first time, If you select the Status tab before entering all the parameters in the FMS, Database Settings and Server Settings tabs, the status are greyed out and an error "Installation Incomplete. Finish the installation to view the status" is displayed.

## FMS

Installing the ToolsTalk Server application is dependent on the FMS service for licensing. FMS services uses system identifiers, called Host ID, for identification and setting licenses. The features available in ToolsTalk 2 are tied to a Host ID used by a particular client and this value is registered on the Atlas Copco license portal. If you want to change the Host ID, the new Host ID must be registered on the Atlas Copco license portal by replacing the old Host ID and this will then move all the features tied to the old Host ID to the new Host ID.

This functionality allows you to read a list of Host IDs used in the past, the currently used active Host ID and the default Host ID and also allows you to change the active Host ID as required to suit network interfacing requirements.

Select Get Host ID Information to get the active Host ID being used.

FMS Settings
Parameters | Description
--- | ---
Default Host ID | Default Host ID which is registered. Default Host ID can be any available Host ID on the machine. It is usually the first Host ID in the list of Host IDs'
Host IDs | List of available Host IDs available on a particular machine depending on the different network interfaces.
Active Host ID | Current Host ID which is active and is being used. Default Host ID is overwritten by Active Host ID if it is specified
Last Used Active Host ID | Indicates which was the last Active Host ID used.

To change the active Host ID:

1. Select the required Host ID from the Host IDs drop-down.

   This is now also reflected in the Active Host ID field.

2. Select Update Active Host ID.

3. Select Save.

The active Host ID is now changed and the FMS services can be restarted for the new settings to be applied.

## Database Settings

Database Settings Parameters
Parameters | Description
--- | ---
SQL Server Address | IP or Hostname of the SQL Server The Microsoft Windows Defender Firewall will prevent connections through the network to SQL Server. Therefore, it is required to configure SQL Server to accept connections by using TCP/IP. This setting can be modified in section SQL Server Configuration Manager in Windows Computer Management. Computer Management -> SQL Server Configuration Manager -> SQL Server Network Configuration -> Protocols for MSSQLSERVER -> TCP/IP -> Enabled
Database Name | The Database/Catalog used by ToolsTalk 2. The database will be created during database installation if not already existing.

Database Credentials
Parameters | Description
--- | ---
User name | The username of a database user with the credentials to create databases/catalogs. Usually the system administrator credential.
Password | Enter the password. Usually the system administrator credential

Installation
Parameters | Description
--- | ---
Manual Script | Specifies whether or not the database has been manually created. If this box is checked, ToolsTalk 2 expects that you have already created the SQL catalog and the default user manually. The entered User Name and Password will be the default credentials that connects to the SQL server and are stored in clear text in the configuration files. This setting should be only used if you have created the database catalog and user yourself.

## Server Settings

Server Settings Parameters
Parameters | Description
--- | ---
Authentication Mode | The authentication mode used to verify user authority. Select Windows (Active directory) or None. If None is selected, Authentication Mode is not enabled. If you want to enable Authentication Mode after installation, you need to uninstall clients for each user before changing the setting in ToolsTalk 2 Configuration window. Remember to resign the clients before reinstalling the clients again.
Active Directory Group | Only visible if the Authentication Mode selected is Windows. Specifies what active directory group a user must be member of. Example: Must always be in the format DOMAINNAME\GROUPNAME If the Authentication Mode selected is Windows, then you can test if active directory group is correct and if the user account you would like to use belongs to the active directory group. Enter the Active Directory Group and select Test AD Group. Enter the User Account and select Test, to verify the active directory group and the group name. An error message is displayed if the user has entered a wrong domain name or wrong group name or both. An error is also displayed if the entered domain name and group name are correct but the user account entered does not belong to that active directory group. An information message is displayed if the test was successful.
Prompt For Windows Credentials | When the checkbox is selected, ToolsTalk 2 asks for Microsoft domain credentials. When the checkbox is not selected, ToolsTalk 2 uses the user credentials of the user that is currently signed in to Windows.
Server Address | IP or Hostname of the ToolsTalk 2 Server. Select in the drop-down between the addresses saved in the server or enter a new address.
Web Application Port | Communication port for ToolsTalk 2. Select Test Tools Talk Server to check if the ToolsTalk 2 server is up and running. This functionality tests and verifies if the Server Address and the Web Application Port entered is working correctly. If the ToolsTalk 2 server is up and running, an information message appears to indicate that the test succeeded and if there is any issue with ToolsTalk 2 server, an error message is displayed with some more information in the log file.
Enable HTTPS | For ClickOnce clients, HTTPS communication between the client and ToolsTalk Server is enabled in ToolsTalk Server. For information on how to set up HTTPS communication in ToolsTalk Server, see Installing the ToolsTalk Server Application.
Controller Port | Port 9016 is used as the default controller port. If using the port 9016, make sure this port is open and you can connect to it, else the application will not work. Port 80 is used when the function Connect/disconnect/add controller is used from ToolsTalk 2 to interact with a controller. If you enter a controller port that is not the same as the configured controller port on Atlas Copco Data Communication, a warning is displayed. Make sure that the controller port on ToolsTalk 2 and Atlas Copco Data Communication is the same.
Convert Service URL to IP Address | On or Off. When On is selected, if a hostname is used in the address, it is converted to an IP address.

Make sure that the controller port you enter is open and is possible to connect to.

Backup
Parameters | Description
--- | ---
Controller Backup Folder | Specifies a folder where the backup for the controllers will be located.

The Active Directory Group and Controller Backup Folder are empty by default.

ACDC Communication Settings
Parameters | Description
--- | ---
Server Address | IP or Hostname of the Atlas Copco Data Communication server
Web API Port | Port for Web API

## Validating the ACDC Exchange Server Settings

The parameters of the exchange server settings should be the same on both Atlas Copco Data Communication and ToolsTalk 2. It is possible to verify if the parameters are the same by using the Validate option in the ACDC Settings tab.

1. Enter the parameters in the Exchange Server Settings field.

2. Select Validate.

   If the parameters entered as correct the validation is successful.

   If the parameters entered are not the same as present in Atlas Copco Data Communication, then an error "The configured value is not equal to the corresponding ACDC value" is displayed.

3. Select Use ACDC Configuration if the validation failed.

   This will replace the incorrect parameters in the ToolsTalk 2 exchange server configuration with the parameters present in the ACDC configuration.

Exchange Server Settings
Parameters | Description
--- | ---
Exchange server topic name | The topic name of the exchange server used for communication between Atlas Copco Data Communication and ToolsTalk 2
Exchange server address | IP address of the exchange server.
Exchange server port | Port of the exchange server.
Exchange server username | Username used to access the exchange server.
Exchange server password | Password for the exchange server.

The link to the ClickOnce Client link is available to copy and send to users to download the ClickOnce Client.

ClickOnce Client
Parameters | Description
--- | ---
Certificate Password (2.21.3+): | If a custom certificate is specified, the certificate password is specified here. Optionally specify a password protected PFX certificate, to use for signing the ClickOnce client files. By specifying a certificate trusted by your system, no warning will be shown during client installation and the installation will work also on systems that prevent installation of applications without trusted signatures. If you do not assign a certificate, you can use a self-signed certificate from Atlas Copco instead (untrusted).We recommend to use a trusted custom certificate. We advise you to specify the same certificate when upgrading to a new version, since changing certificate will require the clients to be re-installed.
Copy Link | Copies the link to the ClickOnce Client.
Sign | Can be used to sign into the ClickOnce Client if needed and the link to the ClickOnce Client will be available again.

## Status

Parameters | Description
--- | ---
Refresh | Refreshes the status view and updates with the latest status of the services involved.
Start | Start a service for the first time.
Stop | Stops the service.
Restart | Restarts a stopped service.

If the Atlas Copco Data Communication is installed in a different server compared to ToolsTalk 2, it is not possible to view or modify the status of the Atlas Copco Data Communication service.

## Deploying the Client On a Remote Machine

1. Browse to the server, via web browser, by using the link:

   http://<FULL COMPUTER NAME>:<PORT NUMBER>/deploym

   Replace <FULL COMPUTER NAME> and <PORT NUMBER>.

   Make sure that the <FULL COMPUTER NAME> is exactly the same as on which the server and database are located. If Full Computer Name [TOOLSE277256.ATLASCOPCO.COM] or Computer Name [TOOLSE277256] is set, then a DNS server must exist and be set in the controller, otherwise it is not possible to add controllers to the ToolsTalk 2 environment.

2. Save the executable file ToolsTalk.Client.WPF.Desktop.application on your computer.

3. Double-click on the executable file, or select Open if prompted.

4. ToolsTalk 2 client opens with the latest version installed.

The ToolsTalk 2 client will always open with the latest server version by using ClickOnce.

## Deploying the Client on Local Machine

- If ClickOnce was installed in the default folder, navigate to “C:\Program Files (x86)\Atlas Copco\ToolsTalk ClickOnce\ClientDeploy” and double click on ToolsTalk.Client.WPF.Desktop Application manifest file to deploy the client.

Once the installation is completed, the ToolsTalk 2 icon is created on the desktop.

# Installing the Station Setup Application

The condensed Station Setup installation has full controller configuration functionality, but also some limitations:

- The entire installation has a smaller footprint and is installed on a portable computer.

- Only one physical controller can be managed at a time.

- The computer is connected to the service port of the controller to avoid interruption of normal activity.

## Applications

The typical application for this mode of operation can be the following:

- A controller can be accessed using ToolsTalk 2 without connecting to a network but instead using the service port of the controller.

- Offline configuration of controllers using the controller library features. The configuration file can later be transferred to a real controller for verification.

- An easy export of a controller configuration that is very helpful in debugging tasks.

Before you begin with the ToolsTalk 2 Station Setup installation, make sure all the requirements are met as described in section Before installing or Upgrading.

1. Save the executable file ToolsTalkStationSetup<xxx>.exe in a desired folder on your computer. The <xxx> represents the version of the file.

2. Double-click on the executable file.

3. Select Yes on Do you want to allow this app to make changes to your device?

4. Select Next in the Atlas Copco Tools Talk Server - InstallShield Wizard window to continue.

5. Read and then select I accept the terms in the license agreement. Select Next to continue.

   Select Print if you would like to print the license agreement.

6. Select Change... to install the application in a different location. The default location is C:\Program Files (x86)\Atlas Copco\ToolsTalk StationSetup\

   Select Next to continue.

7. Select Install to finish the installation.

8. A shortcut of the ToolsTalk2 application will appear on the desktop.

9. Enter the parameters in the Server Settings tab and select Save.

Make sure that the controller port you enter is open and is possible to connect to!

The ToolsTalk 2 application is available in the start menu.

In this Section

- Station Setup Connection

# Station Setup Connection

A computer with a Station Setup of ToolsTalk 2 can be connected to a controller through the network or directly to the service port.

## Network Connection

The ToolsTalk 2 server connection address in the controller must be directed to this computer. This is done via the controller GUI or the controller web GUI.

Only one controller at a time can be connected to a computer with a ToolsTalk 2 Station Setup. If an online controller is connected to the ToolsTalk 2 Station Setup computer, subsequent connection attempts from other controllers will be ignored.

## Controller Service Port Connection

The controller service port can be used to connect a controller to ToolsTalk 2 when the PC with ToolsTalk 2 is not allowed to be connected to the network. For example, an Atlas Copco - or external - service technician visits a factory and the external computer is not allowed to be connected to the factory network.

If a computer is connected to the service port of the controller, the controller acts as a DHCP server and provides an IP address to the computer. This address must be entered in the controller server connection address field for the ToolsTalk 2 connection.

# File Comparison

The configurator stores a copy of all configuration settings as an .xml file called Storage. The file helps in identifying manual changes in the product configuration .xml files. If the product configuration .xml files have been modified, then when you start the configurator, the File Comparison window opens, where you can choose between options Use Storage Files or Use Configuration Files.

# SoftPLC Configurator Installation

To be able to use the SoftPLC functionality in a controller, the SoftPLC Configurator must be installed on the computer where a ToolsTalk 2 Client is installed.

1. Insert a USB device or similar, containing the MultiProg551_Atlas_Installation.

2. Double-click on Installation.bat in MultiProg551_Atlas_Installation, the installation starts.

3. Open the ToolsTalk client when the installation is completed (no restart required).

4. In the ToolsTalk 2 client, go to the Fieldbus and SoftPLC tab. Select the SoftPLC configuration section and in the General SoftPLC Settings, set SoftPLC to On.

Relevant Information

- Pushing Configurations to a Controller

# Installation Validation

# Validating Windows System Services

To verify that background programs and services have started correctly, perform the following check:

1. Select the Windows Search button.

2. Type services in the Search windows entry box.

3. Scroll down and verify that the Atlas Copco Industrial Technique Host for ToolsTalk has started.

   This indicates that the ToolsTalk 2 server application is running.

4. Scroll down and verify that the FlexNet License server - acopco has started.

   This indicates that the license server application for the functional management system is running.

# Validating the Client-Server Installation

After successful installation of the client-server version of the ToolsTalk 2 application, a controller is needed for a complete system test.

- The server computer must be connected to the network.

- The client computer must be connected to the network.

- The controller must be connected to the network and configured to communicate with the server computer.

- Check that Atlas Copco Data Communication service is started.

The server and client may be installed on the same computer.

- For configuration and starting the controller please refer to the controller user guide.

- For configuration, starting and navigating in the ToolsTalk 2 GUI, please refer to the ToolsTalk 2 user guide.

If the ToolsTalk 2 client is installed, the application can be started in the following way:

- Select the Windows Start menu and locate the ToolsTalk 2 folder.

- Select the ToolsTalk 2 icon to launch the application.

Relevant Information

- Getting started

# Validating the Station Setup Installation

If the ToolsTalk 2 Station Setup is installed, the application can be started in the following way:

- Select the Windows Start menu and locate the ToolsTalk 2 folder.

- Select the ToolsTalk 2 icon to launch the application.

The ToolsTalk 2 Station Setup application cannot execute if a ToolsTalk 2 client application or a ToolsTalk 2 server application is installed. They can easily be removed by executing their respective installation programs and choose the Remove option in the Program maintenance window.

The Getting started section in the ToolsTalk 2 user guide describes the windows and the window navigation.

The GUI for a ToolsTalk 2 Station Setup application is slightly different if there is no controller connected. Please refer to the information under the library icon and the controller library icon in the configuration manual.

# Validating the License Service

This validation process is only applicable for Client, Server and ClickOnce application installations and is not valid for a Station Setup installation.

When the ToolsTalk 2 installation is complete, you will need to check that the license service is ready upon startup.

1. Open a web browser, browse to the following two pages and complete the steps:

   - http://”ip-address:port"/api/1.0/health - This page should have the “connectionCheck” : “success”, if not you will need to restart the Flexera service. In some cases more than one restart may be required.

   - http://”ip-address:port"/api/1.0/hostids - If this page is empty you will need to restart the Flexera service. In some cases more than one restart may be required.

This validation process is not applicable for a Station Setup installation

# Uninstalling the Software

Each one of the modules (Client, Server, Station Setup) can be uninstalled as follows:

- Using the windows control panel / Programs and features to select and uninstall the desired programs and modules.

For some modules it may be necessary to restart the computer for the changes to take effect.

# Upgrading ToolsTalk 2

If you are planning to upgrade from a ToolsTalk 2 version that is earlier than 2.21, follow the steps below and also make sure that Atlas Copco Data Communication (ACDC) is version 2.5 or later.

Before the upgrade is started:

- Make sure that the ToolsTalk 2 server is running.

- Back up the ToolsTalk 2 database.

- Make sure that .NET 8 is installed.

After the upgrade has finished, install ToolsTalk 2 clients, version 2.25.

# Installation

# Installing OpenJDK

1. Download OpenJDK

2. Extract the Zip file into a folder, for example: C:\Program Files\Java\. A OpenJDK folder is created and the bin folder is a sub-folder in the main folder.

3. Select Control Panel and navigate to System Properties.

4. Select Advanced and then, Environment Variables.

5. Add the location of the bin folder created during the OpenJDK installation to the PATH variable in the System Variables window.

   Example: C:\WINDOWS\system32;C:\WINDOWS;"C:\ProgramFiles\Java\”OpenJDK_FOLDER”\bin"

6. Select New in the System Variables window.

7. Enter Variable name as JAVA_HOME.

8. Enter the Variable value as the installation path of the OpenJDK (without the bin sub-folder).

9. Select OK.

10. Select Apply changes.

11. Open Command Prompt and enter java -version and check if it prints the newly installed OpenJDK.

    It is also possible to point JAVA_HOME to the folder of your OpenJDK installations and then set the PATH variable to %JAVA_HOME%\bin. So when the OpenJDK needs to be changed, only the JAVA_HOME variable can be changed and the PATH can be left as is.

    If JAVA is already installed and you want to change to OpenJDK, uninstall java from Add or remove programs. License server needs to be reinstalled. Go to FMS folder in cmd propt, run flexnetls.bat -uninstall and then flexnetls.bat -install.

# Configuration

In this section, you can find detailed information about how to create, modify, and verify product settings.

# Getting started

# Starting

If the ToolsTalk 2 client is installed, the application can be started:

1. Select the Windows Start menu, open All programs and scroll down to ToolsTalk 2.

2. Open the folder and select ToolsTalk 2 to launch the application.

# Controllers

## Controller Types

Apart from the controllers that are supported and configurable using ToolsTalk 2, there is the capability to show other controller types in the Controller List and some limited information about these. The controllers which aren't configurable can launch the relevant software through ToolsTalk 2, where they can be further configured.

The controller type ToolsControl is based on a PF8 controller, without any hardware. ToolsControl is a virtual controller with a collection of applications that operate in a Docker cluster with no need to use Fieldbus, SoftPLC, Internal I/O, Scanners and so further. ToolsControl makes it possible to set up a system without installing and configuring a complete cloud-like environment separately. The ToolsControl system includes tightening controllers that are created on-demand and managed by the ToolsControl Portal and the other services.

The different controller types are represented with an icon in the All Controllers list.

Controller Icon | Controller Type | Compatible Software
--- | --- | ---
| ToolsControl | ToolsTalk 2
| Power Focus 8 Synchronized tightening | ToolsTalk 2
| Power Focus 8 | ToolsTalk 2
| Power Focus XC | ToolsTalk 2
| Power Focus 6000 | ToolsTalk 2
| PF6 Flex System | ToolsTalk 2
| Power Focus 6000 Synchronized tightening | ToolsTalk 2
| Power Focus 4000 | ToolsTalkPF
| Power Macs 4000 | ToolsTalkPM
| IXB | ToolsTalk 2
| STR Wrench | Tools Talk 2

## Controller Information

The following is an example of the information that a Power Focus 4000, or a Power Macs 4000 controller can display. An Unsupported Controller will not display this information..

- Application Boot Software Version

- Controller Serial Number

- Protocol Version

- RBU Serial Number

- RBU Type

- Software version

## Tool Information

The information below is displayed under Tools in ToolsTalk 2. What will be shown here is configured in the respective controller software.

- Identifier

- Serial Number

- Model Type

- Service Date

- Calibration Date

- Tightening Count

- Tool Type

- Tightenings Since Service

- Application Code Version

- Boot Code Version

To receive tool information, the controllers will need to be connected to ACDC. For further information please see the ToolsTalk 2 documentation.

In this Section

- Adding Controllers
- Managing the Controller List

# Adding Controllers

Controllers connected to ToolsTalk 2 may be visible in the Plant structure .

The plant structure view is empty if no controllers are connected to ToolsTalk 2, or if user rights do not allow access to folders or controllers.

ToolsControl is added to ToolsTalk2 through the ToolsControl portal.

1. Select Plant structure and then right-click anywhere in the upper area of the controller list. Alternatively, select System administration, then in the Controller software & data management tab right-click in the left-side menu workspace area. Choose Add new controller. The Connect controller dialog window opens.

2. Enter the IP address, or the DNS name of the controller. The IP address of the ToolsTalk 2 server will be pre-populated.

3. Select Connect and select Close once the Controller online message is displayed.

## Connection Status

- If you enter the IP address of an already connected controller in the Connect controller window, the message Controller already connected and online is displayed.

- The message Waiting for controller to come online is displayed while the connection is being established.

- The message Controller online is displayed when the connection to the controller is established.

- The message ToolsTalk failed to connect to controller. Please verify IP address/DNS name is displayed if the connection failed.

A controller can also be connected to the ToolsTalk 2 application via the web GUI or controller GUI.

This procedure is described in the controller specific documentation.

# Managing the Controller List

The Plant structure workspace default view displays All controllers. The All controllers view contains all the controllers currently connected to the ToolsTalk 2 server, regardless of whether they are online or offline. Custom Sections is a subsection of All Controllers ordered into folders.

## Selecting a Custom Sections folder

On the top of the controller list, click the options button, and select Custom Sections and then select the appropriate folder.

## Selecting a Controller

1. In the left side menu bar, select Plant structure .

2. Scroll down to the relevant controller and select it by clicking on the name field .

   The selected controller is highlighted. A controller with an online status constantly updates the ToolsTalk 2 application.

Offline controller names are struck-through.

A controller in offline status may display old and outdated information if changes have been made through another controller interface other than ToolsTalk 2.

It is possible for several ToolsTalk 2 users to access the same controller. If an attempt is made to select a controller, which is already selected by another ToolsTalk 2 user, a modal dialog box is displayed with the following warning message:

Other users are currently active in the system. Parameter values may be changed without notice.

Select OK to close the dialog box and to continue.

## Searching for Controllers

In the Plant structure workspace there is a field for searching for controllers in the controller list.

In the search field, enter at least two letters of the controller name.

It is possible to search for the controller name or type.

## Remote Controller Restart

In certain circumstances it may be required to make a complete power on reset (POR) of the controller.

The following describes how to make a remote POR from ToolsTalk 2:

1. In the left side menu bar, select Plant structure .

2. Right-click on the selected controller and select Restart in the shortcut menu

3. Confirm or cancel the controller restart operation in the modal window dialog. The controller will first go offline before it gets back online.

   This operation may take a few minutes.

   While this is in progress, it is possible to perform other tasks in ToolsTalk 2.

It is only possible to make a remote restart on a controller that is online and connected to the ToolsTalk 2 application server. Offline controller names are struck-through.

# Saving Changes in Parameters and Configurations

When a controller has a status of On-line, it automatically updates ToolsTalk 2 if any changes are made in the web GUI or in the controller GUI.

Any changes made in ToolsTalk 2 are automatically saved but are not copied to the controller. A Push copies changes to the controller and is executed by an active command.

A push indicator is displayed beside the controller name in the plant structure workspace to indicate that configuration changes have been made in ToolsTalk 2 but not yet copied to the controller.

A push can be made in several ways:

- Select the Push indicator icon next to the controller name in the controller list.

- Click the Push command button in the system menu bar to start copying changes from ToolsTalk 2 to one or more controllers. A shortcut menu opens to select affected controllers

- Right click on a controller name in the plant structure workspace and select the Push command button in the shortcut menu. Changes are copied from ToolsTalk 2 to the one selected controller.

It is not possible to make a Push to a controller which has a status of Off-line.

# Managing the Workspace Windows

The workspace for plant structure and reports both involve the selection of a single controller for further work. The workspace can be minimized or maximized to increase the space for the controller workspace by either, dragging as described and shown in the image below, or by selecting the Plant structure icon .

## Minimizing and Maximizing the Workspace View

1. Place the cursor on the line between the two workspace areas. The cursor shape changes from a white arrow to the shape of a horizontal double sided arrow.

2. Click-hold-drag and the border line between the two workspace area can be moved. The workspace can be maximized by moving the window border all the way to the left-side menu, or maximized by moving the window border to the right-side menu.

## Filtering and Sorting the Data Grid

The data grid columns in the workspace windows can be sorted and filtered.

1. Select a column header to access the sort and filter function.

2. To sort the list, select Sort list to arrange the list into ascending, descending, or default order.

3. To filter the list, select the check boxes to filter what is to be displayed. Select Clear filter to return to the default view.

## Search Functionality

It is possible to search for a specific content in the tabs in the Plant structure , Libraries and the System Administration tabs. This functionality is not available for the Scheduled Task and User Groups tabs in the System Administration tab.

1. Navigate to the main workspace of the particular tab where the data grid is displayed.

2. Enter the parameter you would like to search against in the Search bar seen in the top left corner of the workspace.

   The list narrows down, based on the parameters selected. For example, if you enter the parameter "Event", only the rows that contain the word "Event" is displayed.

## Multi-Sorting Functionality

It is possible to sort the data grid columns in an ascending or descending order (for example, based on index,alphabetical order and time and date and so on) and assign a priority for which column gets sorted first, second and so on.

1. Navigate to the main workspace of the particular tab where the data grid is displayed.

2. Select the present at the end of the header row of the data grid workspace.

3. Select the check box by the column name which you would like to first be sorted and then select the direction arrow to indicate if it should be ascending or descending. The arrow pointing up indicates ascending and the arrow pointing down indicates a descending order .

   For example, if you select Last Changed first, then the priority number 1 appears next to it and if you had selected the arrow pointing up, then the data in column Last Changed will be displayed with the latest time and date on the topmost row. The other columns will change the display order based on this selection. If another column is selected to be sorted next, then the priority number for that column will be displayed as 2 and the data in the column with priority 2 will be sorted based on the direction arrow after the data in column with priority 1 has been sorted and continues similarly for further columns selected.

4. To remove or change the priority of the columns, deselect the check boxes and/or make the selection again.

# User Interface - Workspace With Controller Overview

After selecting a controller and selecting a controller menu icon, the controller workspace can show the following information.

Controller workspace overview

A | A selected controller in the Plant structure workspace
B | Controller name in the controller workspace. The name is identical to the selected controller name in the Plant structure
C | Name of the selected controller menu icon
D | List of configurations with overview information in the controller workspace
E | Controller menu icons
F | A row of command buttons in the controller workspace. The type of command buttons vary depending on the controller menu icon selected
G | Selected controller menu icon. Highlighted with a yellow border

The workspace overview shows either a list of configurations or shows menus with parameter values. If a list of configurations is shown, the next level, the Menu level is accessed by a double-click on a configuration name.

In the overview, a warning icon or an error icon will show when there is a warning or an error of the configuration. If there are both warnings and errors, only error icon will show.

# Configuration for PF6000 and PF8

# Quality Integrated Fastening Accessories (QIF)

The QIF (Quality Integrated Fastening) is a series of accessories used for communication between a controller and operator. The configuration of QIF accessories is available in the Configurations section .

# Working with the Tightening Program Tab

Viewing the list of Tightening Programs

1. Select a controller in the Plant structure workspace .

2. On the toolbar, select Tightening program .

   The Tightening program overview shows a list of tightening programs.

The list has the following columns:

List of tightening programs
Column | Description
--- | ---
Check box | Select a tightening program by marking a check box.
Name | Name of the tightening program. A Push indicator can be visible in adjacent to the name indicating that changes have been made, but not yet pushed to the controller.
Strategy | The tightening strategy selected for the tightening program.
Description | Description of the tightening program as described in the Properties field of each tightening program.
Library Link | Indicates if the program is linked to a Global tightening program in the tightening program library.
Target | The final tightening target is either expressed as a torque value or as an angle value.
Last changed | Last changes made, expressed in ToolsTalk 2 time.
Changed by | Indicates which user made the last changes.
Controller updated | Last changes pushed to a controller, expressed in controller time.
Controller updated by | Indicates which user made the last push to the controller.
Approval status | Approval status of the tightening or loosening program

The field Changed by can be a registered ToolsTalk 2 user, as it is done via the ToolsTalk 2 GUI.

The field Controller updated by can be a registered ToolsTalk 2 user, via the web-GUI or via the controller-GUI.

The following columns can be filtered by texts in the search box: Name, Strategy, Description, Target and Changed by.

Command buttons in the tightening workspace
Command | Description
--- | ---
Add | Creates a new tightening program.
Manage | Add to library: Converts a Local tightening program into a Global tightening program. Unlink: Converts a Global tightening program into a Local tightening program: Compare: Compares two selected tightening programs. These must have the same strategy. Export: Exports a selected tightening program. File format is *.json Export to csv: (not available for mutistep) Exports selected tightening program(s). File format is *.csv Delete: Removes selected tightening program(s) from the list. Send for approval: Approve or Reject tightening in the Program Approval tab. Approve: Approves the tightening directly in this configuration view. An approved non-global (Library) tightening program remains editable on controller screen or web HMI. So the program is therefore editable outside of TT2. When using this functionality it is recommended to close the web HMI. Reset to draft: Changes the approval status to Draft.

In this Section

- Tightening Strategies
- Step Configuration Stages
- Creating a Tightening Program
- Tightening Program Configuration - General Parameters
- Importing a Tightening Program
- Deleting a Tightening Program
- Copying and pasting tightening programs
- Global Tightening Program
- Comparing Tightening Programs
- Approval Statuses

# Tightening Strategies

By selecting the tightening strategy it is possible to choose the method for applying clamping force (or preload) to the joint. Different joints require different strategies for how to apply the desired clamping force and to minimize unwanted in-service effects.

The tightening strategies require a target which is either a Target torque or a Target angle value and the selection options depend on the strategy and on the tool. All other parameters can be configured to optimize the tightening.

Parameter | Description | Default value
--- | --- | ---
Strategy | Available tightening strategies. TurboTight: No additional tightening behaviour is used as default. Only target values are used. Quick step: Adds an initial tightening step to reduce preload scatter. Two step: Adds a pause between the first and final tightening step to further counteract short-term relaxation effects. Three step: Tightens to a defined First torque value, then loosens the screw and immediately re-tightens it to Target torque. Rotate: Rotates the spindle a specified speed and angle. Wrench - production: Tightening strategy used only for the STwrench tool. Wrench - quality: Tightening strategy used only for the STwrench tool. TensorPulse: Tightening strategy used for a tool with pulsing capability. A pulsing tool can produce higher target torque. Has only the option to have a target torque Impulse - single step: Tightening strategy used for a tool with pulsing capability. A pulsing tool can produce higher target torque. Has only the option to have a target torque | TurboTight
Target type | Defines the type of the target value in the final step. Target torque: The tightening aims towards the specified target value when performing the final step. Target angle: The tightening aims towards the specified target value when performing the final step. |
Target torque | Defines the target torque of the tightening of the final step. |
Target angle | Defines the target angle of the tightening of the final step. |

Controller features, such as the Low Reaction Tightening Strategies and controller-wide functions among others, require licenses distributed through the Functionality Management System (FMS). Whereas configuration of features is possible without specific licenses, the assignment and use of those features will require the correct license to be installed on the controller. Please refer to Licenses (FMS) for more detailed information on licenses.

Relevant Information

- Current Monitoring

In this Section

- TurboTight
- Quick Step
- Two Step
- Three Step
- External Result
- Pulsing Tool Strategies
- Trigger Lost
- STwrench Strategies
- Multistep Tightening Strategy

# TurboTight

TurboTight is the default tightening strategy and it is designed to perform a very fast and ergonomic tightening based on the tool’s maximum speed (Tool max speed). This strategy requires only the Target torque to be set to perform the tightening. Depending on the joint properties, for example if the joint is very stiff or very soft, a different tightening strategy might be needed.

If the TurboTight strategy gives unwanted results, a tip is to look at how the Rundown complete is set. A Rundown complete set too high could give the TurboTight strategy too little time to work on the necessary calculations in the Tightening step and result in an overshoot. The objective should be to set the Rundown complete as close to snug as possible.

A Rundown speed set too high could also cause the TurboTight to have too little time to work on the necessary calculations in the Tightening step, resulting in an overshoot. This is even more important if the joint is very stiff.

The table below lists all the parameters for the Turbotight tightening strategy. Some parameters are mandatory, some are optional and some are conditional.

The conditional parameters are not shown in the configuration menu if the condition is not valid, this is also the case when certain functions are disabled.

Parameters for TurboTight tightening
Parameter name | Condition | Description | Default value
--- | --- | --- | ---
Target Torque |  | Defines the target torque of the final step of the tightening. |
Residual torque correlation factor |  | A tuning factor that compensates between the dynamic torque, measured by the tool, and the residual torque needed for the correct clamping force. This is expressed in percentage. | 100 %
Torque limits |  | Selected by radio buttons. Torque values for max and min can be Automatically or Manually selected. |
Torque min | Torque limits = Manual | Torque value for the lower limit. | 95% of target torque
Torque max | Torque limits = Manual | Torque value for the upper limit. | 120% of target torque
Angle limits |  | Angle limits is selected from a shortcut menu. Off: No angle limit monitoring. From rundown complete: The monitoring window is set from when the Rundown complete torque is reached. From torque: The monitoring window is set from when the specific torque value is reached. |
Final angle monitoring torque | Angle limits = from torque | Torque value from when the angle limits are monitored. |
Angle min | Angle limits = on | Angle value lower limit | 90°
Angle max | Angle limits = on | Angle value upper limit | 720°
Time min | Angle limits = on | Minimum time for the step Range 0 - 99999 ms | 0
Time max | Angle limits = on | Maximum time for the step Range 1 - 99999 ms | 40 ms
Measure torque at |  | Selected from a shortcut menu: Max torque value: Measures the highest torque value during the tightening. Value at peak angle: Measures the torque value at the highest angle value. Shutoff: Measures the torque value before starting the stop stage. |
Torque compensation |  | Selected from a shortcut menu: On: Compensating the final torque value with the measured torque during rundown at the torque compensation point. Off: No torque compensation value is applied. | Off
Torque compensation point | Torque compensation = On | The torque compensation point is set by referring back to a specified angle from Rundown complete. | 45°
Measure angle to | Angle limits = on | Selected from a shortcut menu: Value at peak torque: Measures the angle value at the maximum torque during the tightening. Max angle value: Measures the maximum angle value during the tightening. Shutoff:Measures the angle value before starting the stop stage. |
Premature torque loss detection time |  | From rundown complete, the program may start the tightening with an increase in torque. If the tool detects a decrease in torque within this time frame, a slip-off is reported If the socket slips of the screw head and the measured torque decreases below Rundown complete within the specified time, the tightening is aborted and premature torque loss is reported. | 200 ms

The tool limits menu under the tool icon provides information about maximum tool limits. Tool type and limits also affects loosening strategies and parameters that are associated with a tightening program.

For example, a pulsating SR31 tool has a much higher torque value than a normal tool, when using a TurboTight strategy. The TurboLoosening must be properly configured in order to be able to loosen a screw.

# Quick Step

Quick step is a tightening strategy used to reduce the joint’s preload scatter by adding an initial step with a given torque and speed, and then reducing the target speed in the final step.

Quick step tightening strategy

The table below lists all the parameters for the Quick step tightening strategy. Some parameters are mandatory, some are optional and some are conditional.

The conditional parameters are not shown in the configuration menu if the condition is not valid, this is also the case when certain functions are disabled.

Parameters for a torque value as the final target

Parameters for Quick step tightening and Final target = torque.
Parameter name | Condition | Description | Default value
--- | --- | --- | ---
Target |  | Torque or Angle can be selected from a shortcut menu. |
First torque | Target = torque |  |
First speed |  | First speed can be Automatically or Manually selected. |
First speed | First speed = manual | Specifies the tools speed during the first step. |
Target speed |  | Target speed can be Automatically or Manually selected. |
Target speed | Target speed = manual | Specifies the tools speed during the final step. |
Target Torque |  | Defines the target torque of the final step of the tightening. |
Torque limits |  | Torque values for max and min can be Automatically or Manually selected. |
Torque min | Torque limits = Manual | Torque value for the lower limit. | 95% of target torque
Torque max | Torque limits = Manual | Torque value for the upper limit. | 120% of target torque
Angle limits |  | Angle limits is selected from a shortcut menu. Off: No angle limit monitoring. From rundown complete: The monitoring window is set from when the Rundown complete torque value is reached. From first torque: The monitoring window is set from when the First torque value is reached. From torque: The monitoring window is set from when the specific torque value is reached. |
Final angle monitoring torque | Angle limits = from torque | Torque value from when the angle limits are monitored. |
Angle min | Angle limits = on | Angle value lower limit. | 324°
Angle max | Angle limits = on | Angle value upper limit. | 396°
Time min | Angle limits = on | Minimum time for the stage. Range 0 - 99999 ms | 0 ms
Time max | Angle limits = on | Maximum time for the stage. Range 1 - 99999 ms | 1000 ms
Measure torque at |  | Max torque value: Measures the highest torque value during the tightening. Value at peak angle: Measures the torque value at the highest angle value. Shutoff: Measures the torque value before starting the stop stage. |
Torque compensation |  | On: Compensating the final torque value with the measured torque during rundown at the torque compensation point. Off: No torque compensation value is applied. | Off
Torque compensation point | Torque compensation = On | The torque compensation point is set by referring back to a specified angle from Rundown complete. | 45°
Measure angle to | Angle limits = on | Value at peak torque: Measures the angle value at the maximum torque during the tightening. Max angle value: Measures the maximum angle value during the tightening. Shutoff: Measures the angle value before starting the stop stage. |
Premature torque loss detection time |  |  | 200 ms
Current monitoring |  | On: The current monitoring is enabled. Off: The current monitoring is disabled. The current monitor is used as a redundancy check for the measured torque to give reasonable confidence that torque readings are accurate. |
Shutoff current high limit. | Current monitor = On | The current value must be above 0 and below tool maximum current. |
Shutoff current low limit | Current monitor = On | The current value must be above 0 and below the current high limit. |

The table below lists all the parameters for the Quick step tightening strategy. Some parameters are mandatory, some are optional and some are conditional.

The conditional parameters are not shown in the configuration menu if the condition is not valid, this is also the case when certain functions are disabled.

Parameters for an angle value as the final target

Parameters for Quick step tightening with Final target = angle.
Parameter name | Condition | Description | Default value
--- | --- | --- | ---
Target |  | Torque or Angle can be selected from a shortcut menu. |
First torque | Target = angle |  |
First speed |  | First speed can be Automatically or Manually selected. |
First speed | First speed = manual | Specifies the tools speed during the first step. |
Target speed |  | Target speed can be Automatically or Manually selected. |
Target speed | Target speed = manual | Specifies the tools speed during the final step |
Torque min |  | Torque value for the lower limit. | 95% of target torque
Torque max |  | Torque value for the upper limit. | 120% of target torque
Target angle |  | Target value for the final step. |
Angle limits |  | Auto: Set automatically by the algorithm. Manual: The limits are set manually. |
Angle min | Angle limits = Manual | Angle value lower limit | 324°
Angle max | Angle limits = Manual | Angle value upper limit | 396°
Time min | Angle limits = Manual | Minimum time for the stage Range 0 - 99999 ms | 0 ms
Time max | Angle limits = Manual | Maximum time for the stage Range 1 - 99999 ms | 1000 ms
Measure torque at |  | Max torque value: Measures the highest torque value during the tightening. Value at peak angle: Measures the torque value at the highest angle value. Shutoff: Measures the torque value before starting the stop stage. |
Torque compensation |  | On: Compensating the final torque value with the measured torque during rundown at the torque compensation point. Off: No torque compensation value is applied. | Off
Torque compensation point | Torque compensation = On | The torque compensation point is set by referring back to a specified angle from Rundown complete. | 45°
Premature torque loss detection time |  |  | 200 ms
Current monitoring |  | On: The current monitoring is enabled. Off: The current monitoring is disabled. The current monitor is used as a redundancy check for the measured torque to give reasonable confidence that torque readings are accurate. |
Shutoff current high limit | Current monitoring = On | The current value must be above 0 and below tool maximum current. |
Shutoff current low limit | Current monitoring = On | The current value must be above 0 and below the current high limit. |

# Two Step

The Two step strategy is very similar to the Quick step strategy except that it adds a small time delay between the first step and the final step, to further counteract short-term relaxation effects in the joint.

Tightening strategy two step

When the First target is reached, the tool makes an immediate stop for a specified time before it continues with the final step. The First torque value and the Pause time should be chosen to improve ergonomics for hand-held tools.

The table below lists all the parameters for the Two step tightening strategy. Some parameters are mandatory, some are optional and some are conditional.

The conditional parameters are not shown in the configuration menu if the condition is not valid, this is also the case when certain functions are disabled.

Parameters for a torque value as the final target.

Parameters for Two step tightening with Final target = torque.
Parameter name | Condition | Description | Default value
--- | --- | --- | ---
Target |  | Torque or Angle can be selected from a shortcut menu |
First torque | Target = torque |  |
First speed |  | Selected by radio buttons. First speed can be Automatically or Manually selected |
First speed | First speed = manual | Specifies the tools speed during the first step |
Target speed |  | Selected by radio buttons. Target speed can be Automatically or Manually selected |
Target speed | Target speed = manual | Specifies the tools speed during the final step |
Pause time | Strategy = Two step | Time between first and final step | 50 ms
Target Torque |  | Defines the target torque of the final step of the tightening |
Torque limits |  | Selected by radio buttons. Torque values for max and min can be Automatically or Manually selected |
Torque min | Torque limits = Manual | Torque value for the lower limit | 95% of target torque
Torque max | Torque limits = Manual | Torque value for the upper limit | 120% of target torque
Angle limits |  | Angle limits is activated through a shortcut menu. Off: No angle limit monitoring. From rundown complete: The monitoring window is set from when the Rundown complete torque is reached. From first torque: The monitoring window is set from when the First torque is reached. From torque: The monitoring window is set from when the specific torque value is reached. |
Final angle monitoring torque | Angle limits = from torque | Torque value from when the angle limits are monitored |
Angle min | Angle limits = on | Angle value lower limit | 324°
Angle max | Angle limits = on | Angle value upper limit | 396°
Time min | Angle limits = on | Minimum time for the stage Range 0 - 99999 ms | 0 ms
Time max | Angle limits = on | Maximum time for the stage Range 1 - 99999 ms | 1000 ms
Measure torque at |  | Selected from a shortcut menu: Max torque value: Measures the highest torque value during the tightening. Value at peak angle: Measures the torque value at the highest angle value. Shutoff: Measures the torque value before starting the stop stage. |
Torque compensation |  | Selected from a shortcut menu: On: Compensating the final torque value with the measured torque during rundown at the torque compensation point. Off: No torque compensation value is applied. | Off
Torque compensation point | Torque compensation = On | The torque compensation point is set by referring back to a specified angle from Rundown complete. | 45°
Measure angle to | Angle limits = on | Selected from a shortcut menu: Value at peak torque: Measures the angle value at the maximum torque during the tightening. Max angle value: Measures the maximum angle value during the tightening. Shutoff:Measures the angle value before starting the stop stage. |
Premature torque loss detection time |  |  | 200 ms
Current monitoring |  | Selected from a shortcut menu: On: The current monitoring is enabled. Off: The current monitoring is disabled. The current monitor is used as a redundancy check for the measured torque to give reasonable confidence that torque readings are accurate. |
Shutoff current high limit. | Current monitor = On | The current value must be above 0 and below tool maximum current. |
Shutoff current low limit. | Current monitor = On | The current value must be above 0 and below the current high limit. |

The table below lists all the parameters for the Two step tightening strategy. Some parameters are mandatory, some are optional and some are conditional.

The conditional parameters are not shown in the configuration menu if the condition is not valid, this is also the case when certain functions are disabled.

Parameters for an angle value as the final target.

Parameters for Two step tightening with Final target = angle.
Parameter name | Condition | Description | Default value
--- | --- | --- | ---
Target |  | Torque or Angle can be selected from a shortcut menu |
First torque | Target = angle |  |
First speed |  | Selected by radio buttons. First speed can be Automatically or Manually selected |
First speed | First speed = manual | Specifies the tools speed during the first step |
Target speed |  | Selected by radio buttons. Target speed can be Automatically or Manually selected |
Target speed | Target speed = manual | Specifies the tools speed during the final step |
Pause time | Strategy = Two step | Time between first and final step | 50 ms
Torque min |  | Torque value for the lower limit | 95% of target torque
Torque max |  | Torque value for the upper limit | 120% of target torque
Target angle |  | Target value for the final step |
Angle limits |  | Angle limits is activated a through shortcut menu. Auto: Set automatically by the algorithm. Manual: The limits are set manually. |
Angle min | Angle limits = Manual | Angle value lower limit | 324°
Angle max | Angle limits = Manual | Angle value upper limit | 396°
Time min | Angle limits = Manual | Minimum time for the stage Range 0 - 99999 ms | 0 ms
Time max | Angle limits = Manual | Maximum time for the stage Range 1 - 99999 ms | 1000 ms
Measure torque at |  | Selected from a shortcut menu: Max torque value: Measures the highest torque value during the tightening. Value at peak angle: Measures the torque value at the highest angle value. Shutoff: Measures the torque value before starting the stop stage. |
Torque compensation |  | Selected from a shortcut menu: On: Compensating the final torque value with the measured torque during rundown at the torque compensation point. Off: No torque compensation value is applied. | Off
Torque compensation point | Torque compensation = On | The torque compensation point is set by referring back to a specified angle from Rundown complete. | 45°
Premature torque loss detection time |  |  | 200 ms
Current monitoring |  | Selected from a shortcut menu: On: The current monitoring is enabled. Off: The current monitoring is disabled. The current monitor is used as a redundancy check for the measured torque to give reasonable confidence that torque readings are accurate. |
Shutoff current high limit. | Current monitor = On | The current value must be above 0 and below tool maximum current. |
Shutoff current low limit. | Current monitor = On | The current value must be above 0 and below the current high limit. |

# Three Step

The Three step strategy adds a loosening step between the first step and the final step, to overcome short-term relaxation effects due to embedment, and reduce preload scatter. This is sometimes used to condition the joint. This can be useful in, for example, joints with many adjoining surfaces and will have a greater effect on new parts than on reused ones, due to the smoothing of surfaces, which reduces embedment.

Conditioning the joint is done by tightening the first step to a given torque, First torque, and then releasing the load by turning the nut a specified Conditioning angle and then re-tightening the nut to its Target torque.

Tightening strategy three step

The table below lists all the parameters for the Three step tightening strategy. Some parameters are mandatory, some are optional and some are conditional.

The conditional parameters are not shown in the configuration menu if the condition is not valid, this is also the case when certain functions are disabled.

The table below is valid for Final target = Torque.

When the First target is reached and the conditioning step is entered, the tool makes an immediate stop and reverse before it continues with the final step. This conditioning step may need to be fine-tuned to improve ergonomics for hand-held tools.

Parameters for a torque value as the final target.

Parameters for Three-step tightening with Final target = torque.
Parameter name | Condition | Description | Default value
--- | --- | --- | ---
Target |  | Torque or Angle can be selected from a shortcut menu |
First torque | Target = torque |  |
First speed |  | Selected by radio buttons. First speed can be Automatically or Manually selected |
First speed | First speed = manual | Specifies the tools speed during the first step |
Conditioning angle | Strategy = Three step | Angle to turn the socket backwards during the conditioning step | 180°
Conditioning speed | Strategy = Three step | Target speed for the backwards rotation during the conditioning step | 345 rpm
Target speed |  | Selected by radio buttons. Target speed can be Automatically or Manually selected |
Target speed | Target speed = manual | Specifies the tools speed during the final step |
Target Torque |  | Defines the target torque of the final step of the tightening |
Torque limits |  | Selected by radio buttons. Torque values for max and min can be Automatically or Manually selected |
Torque min | Torque limits = Manual | Torque value for the lower limit | 95% of target torque
Torque max | Torque limits = Manual | Torque value for the upper limit | 120% of target torque
Angle limits |  | Angle limits is activated through shortcut menu. Off: No angle limit monitoring. From rundown complete: The monitoring window is set from when the Rundown complete torque is reached. From first torque: The monitoring window is set from when the First torque is reached. From torque: The monitoring window is set from when the specific torque value is reached. |
Final angle monitoring torque | Angle limits = from torque | Torque value from when the angle limits are monitored |
Angle min | Angle limits = on | Angle value lower limit | 324°
Angle max | Angle limits = on | Angle value upper limit | 396°
Time min | Angle limits = on | Minimum time for the step Range 0 - 99999 ms | 0 ms
Time max | Angle limits = on | Maximum time for the step Range 1 - 99999 ms | 1000 ms
Measure torque at |  | Selected from a shortcut menu: Max torque value: Measures the highest torque value during the tightening. Value at peak angle: Measures the torque value at the highest angle value. Shutoff: Measures the torque value before starting the stop step. |
Torque compensation |  | Selected from a shortcut menu: On: Compensating the final torque value with the measured torque during rundown at the torque compensation point. Off: No torque compensation value is applied. | Off
Torque compensation point | Torque compensation = On | The torque compensation point is set by referring back to a specified angle from Rundown complete. | 45°
Measure angle to | Angle limits = on Or final target = angle | Selected from a shortcut menu: Value at peak torque: Measures the angle value at the maximum torque during the tightening. Max angle value: Measures the maximum angle value during the tightening. Shutoff:Measures the angle value before starting the stop step. |
Premature torque loss detection time |  |  | 200 ms
Current monitoring |  | Selected from a shortcut menu: On: The current monitoring is enabled. Off: The current monitoring is disabled. The current monitor is used as a redundancy check for the measured torque to give reasonable confidence that torque readings are accurate. |
Shutoff current high limit. | Current monitor = On | The current value must be above 0 and below tool maximum current. |
Shutoff current low limit. | Current monitor = On | The current value must be above 0 and below the current high limit. |

The table below lists all the parameters for the Three step tightening strategy. Some parameters are mandatory, some are optional and some are conditional.

The conditional parameters are not shown in the configuration menu if the condition is not valid, this is also the case when certain functions are disabled.

Parameters for a torque value as the final target.

Parameters for Three-step tightening with Final target = angle.
Parameter name | Condition | Description | Default value
--- | --- | --- | ---
Target |  | Torque or Angle can be selected from a shortcut menu |
First torque | Target = angle |  |
First speed |  | Selected by radio buttons. First speed can be Automatically or Manually selected |
First speed | First speed = manual | Specifies the tools speed during the first step |
Conditioning angle | Strategy = Three step | Angle to turn the socket in reverse during the conditioning step | 180°
Conditioning speed | Strategy = Three step | Target speed for the reverse rotation during the conditioning step | 345 rpm
Target speed |  | Selected by radio buttons. Target speed can be Automatically or Manually selected |
Target speed | Target speed = manual | Specifies the tools speed during the final step |
Torque min |  | Torque value for the lower limit | 95% of target torque
Torque max |  | Torque value for the upper limit | 120% of target torque
Target angle |  | Target value for the final step |
Angle limits |  | Angle limits is activated through shortcut menu. Auto: Set automatically by the algorithm. Manual: The limits are set manually. |
Angle min | Angle limits = Manual | Angle value lower limit | 324°
Angle max | Angle limits = Manual | Angle value upper limit | 396°
Time min | Angle limits = Manual | Minimum time for the step Range 0 - 99999 ms | 0 ms
Time max | Angle limits = Manual | Maximum time for the step Range 1 - 99999 ms | 1000 ms
Measure torque at |  | Selected from a shortcut menu: Max torque value: Measures the highest torque value during the tightening. Value at peak angle: Measures the torque value at the highest angle value. Shutoff: Measures the torque value before starting the stop step. |
Torque compensation |  | Selected from a shortcut menu: On: Compensating the final torque value with the measured torque during rundown at the torque compensation point. Off: No torque compensation value is applied. | Off
Torque compensation point | Torque compensation = On | The torque compensation point is set by referring back to a specified angle from Rundown complete. | 45°
Premature torque loss detection time |  |  | 200 ms
Current monitoring |  | Selected from a shortcut menu: On: The current monitoring is enabled. Off: The current monitoring is disabled. The current monitor is used as a redundancy check for the measured torque to give reasonable confidence that torque readings are accurate. |
Shutoff current high limit. | Current monitor = On | The current value must be above 0 and below tool maximum current. |
Shutoff current low limit. | Current monitor = On | The current value must be above 0 and below the current high limit. |

# External Result

External result is a strategy used when an OK tightening is indicated by an external digital signal (and not by torque or angle values measured during tightening). This external signal can be provided through any means that can provide a digital signal into the Power Focus 6000 (e.g through the I/O bus).

When the signal is sent, the Result view will show the value of the Target parameter provided in the tightening program (specified torque value, angle value, or text string). These (torque and angle) values do not represent actual measured values, but only inserted text.

1. Select a controller in the Plant structure workspace .

2. Go to Tightening .

   The Tightening workspace shows a list of tightening programs.

3. Double-click on the name of a tightening program to configure the tightening program to be an external result strategy or create a new external result strategy by selecting the Add command button.

Parameter | Description | Default value
--- | --- | ---
Torque <Target torque> | Numerical value for desired displayed target torque value. A signal could for example come from a Click Wrench and display <Target torque>. | 0.00
Angle <Target angle> | Numerical value for desired displayed target angle value. A signal could for example come from a Click Wrench and display <Target angle>. | 360°
Text | Alphanumerical string for desired displayed text. For example: "Oil has been changed". |

The External result is being logged and will end up in Live result view and in Historical results.

In order to use External OK, the Virtual Station must use the tightening program External Result strategy as an assigned task and also a tool to be assigned to the Virtual Station. The tool can be either a physical tool or a virtual external tool.

Relevant Information

- Configuring the External Results Without Tool Connected
- Setting Up an External Tool

In this Section

- Results from External Tools

# Results from External Tools

It is possible to report results from an external tool or application not connected to the controller. This feature provides the possibility to define an external tool which can be defined as a logical or virtual tool which uses the tightening strategy External result and assign it to a virtual station in place of a real tool.

In this Section

- Setting Up an External Tool
- Configuring the External Results Without Tool Connected

# Setting Up an External Tool

1. Select a controller in the Plant structure window .

2. Go to Settings .

   The workspace area displays the Settings menus.

3. Select Add in the External Tool menu and set Enabled to On.

   Setting Enabled to Off, disconnects the external tool without deleting it and can be enabled when required.

   It is possible to create up to 10 External Tool configurations per controller.

   Enter the Model, Serial number and the Description of the external tool.

   The Serial Number is a mandatory parameter and the maximum number of characters allowed is 32.

   To delete the external tool, select the checkbox External Tool Configuration and select Delete.

4. Push changes and the external tool will be visible in the Tool tab and also in the controller.

Relevant Information

- Pushing Configurations to a Controller

# Configuring the External Results Without Tool Connected

1. In the Plant structure workspace select a controller .

2. Select the Virtual Station tab .

3. Select the external tool in the Tool menu.

4. Assign the task with the external result strategy to the virtual station the Task menu and push changes .

Relevant Information

- Assigning a Task to a Virtual Station
- Assigning a Tool to a Virtual Station
- Pushing Configurations to a Controller

# Pulsing Tool Strategies

The strategy can be selected if the controller software version supports the tightening program. Pulsing tools can achieve a higher torque compared to normal rotating tools.

In this Section

- Pulse Tightening Program
- Pulse Tightening with Direct Driven Electrical Tools
- Tightening using the TensorPulse Program

# Pulse Tightening Program

## Start

During the start step, the tool rotates in a speed mode without any pulsing.

Parameter name | Description
--- | ---
Soft start | Enables setting of the tool’s speed, angle and maximum torque to facilitate the bolt entering the thread. Selected by radio buttons. Off: Soft start is turned off. On: Soft start is turned on.
Speed | Defines the speed during the soft start.
Time | Defines the Soft start duration.
Angle | Defines the target angle to turn the spindle for the bolt to enter the thread.
Torque max | Defines the upper torque limit during the soft start. If Torque max is exceeded, the tightening is considered NOK.
Rehit detection | Early: Terminates the tightening immediately when an already tightened screw/bolt is detected. The tightening will be considered as NOK. Requires that Soft start is activated. Complete: Even though an already tightened screw/bolt is detected, the tightening is not terminated until all tightening steps have been executed. The tightening will be considered as NOK. To make a rehit detection when Soft start is not activated, the Rehit detection Complete option must be selected. Rehit detection Complete will not terminate the tightening until all tightening steps have been executed. The tightening will be considered a rehit if the speed fails to reach half the rundown speed, a rehit error is then indicated. Off: No rehit detection will be performed. Combination Soft start = Off and Rehit = Early is not allowed.
Positive | The TrueAngle compensation can detect tool rotation and make angle compensations within the set limits.
Negative | The TrueAngle compensation can detect tool rotation and make angle compensations within the set limits.
Use attachment tuning | Attachment tuning is selected by radio buttons.
Gear ratio | Socket rotation speed = Tool speed / gear ratio.
Efficiency tuning | For example 0.9 means 10% efficiency loss.

## Rundown

During rundown, the tool can use either speed mode, with a constant motor speed, or pulse mode. The selection is made depending on the encountered torque and the given torque limits within the configuration.

Parameter name | Description
--- | ---
High-speed rundown | The rundown step can be done in high-speed in order to minimize the time, without overshooting. This is achieved by letting the tool run at a higher speed for a specified angle length. When the angle has been reached, the speed will change to the lower speed specified in Rundown speed parameter. Only available for SRB tools. Length: Default 3600°, max 99999° Speed: Tool max speed must be higher than Rundown speed (rpm).
Rundown speed | Rundown speed can be set to either Max or Manual. If Rundown speed is set to Manual; enter the tool speed in rpm.
Rundown angle limits | Off: Rundown angle limits is turned off. From Trigger: Rundown angle limits is turned On. The system starts to monitor the tightening angle as soon as the tool trigger is pressed and reports if angle limits are violated. From torque: Rundown angle limits is turned On. The system starts to monitor the tightening angle from the specified torque value and reports if angle limits are violated.
Rundown angle monitoring torque | Torque value from where Rundown angle limits are set.
Angle min | Angle value for lower angle limit from starting point.
Angle max | Angle value for upper angle limit from starting point.
Time min | Minimum time for the step.
Time max | Maximum time for the step.
Rundown pulse limits | Selected from a shortcut menu: Off: Rundown pulse limits is turned off. From Trigger: Rundown pulse limits is turned On. The system starts to monitor the pulses as soon as the tool trigger is pressed and reports if the pulse limits are violated. From torque: Rundown pulse limits is turned On. The system starts to monitor the pulses from the specified torque value and reports if the pulse limits are violated.
Rundown pulse monitoring torque | Torque value from where the Rundown pulse limits monitor starts. The value must be set to a value greater than Continuous max torque.
Pulses min | Minimum number of pulses to reach the Rundown complete torque value.
Pulses max | Maximum number of pulses to reach the Rundown complete torque value.
Rundown complete torque | Defines the torque value for when snug is reached and the rundown is completed. The program proceeds with the tightening and starts with pulse mode, if not already done so during rundown.

## Tightening

Parameter name | Description
--- | ---
Target torque | Final target torque for the tightening.
Pulse Energy | The Pulse energy delivered in the action pulse expressed in a percentage of the maximum energy that the tool can deliver in each pulse.
Reaction force tuning factor | The energy delivered by the tool expressed in a percentage value. The reaction force tuning factor is based on the action energy and results in a comfortable reaction.
Residual torque correlation factor | The term Residual torque correlation factor is similar to a calibration and adjusts between the dynamic torque, measured in the electrical tool, and the residual torque, measured by a control tool.
Torque limits | Limits can be Automatically or Manually selected.
Torque min | Minimum torque for the step.
Torque max | Maximum torque for the step.
Angle limits | Off:Angle limits is turned off. From Rundown complete: Angle limits is turned On. The system starts to monitor the tightening angle as soon as Rundown complete is reached and reports if angle limits are violated. From torque: Rundown angle limits is turned On. The system starts to monitor the tightening angle from the specified torque value and reports if angle limits are violated.
Rundown angle monitoring torque | Torque value from where Rundown angle limits monitoring starts.
Angle min | Angle value for lower angle limit from the starting point.
Angle max | Angle value for the upper angle limit from starting point.
Time min | Minimum time for the step.
Time max | Maximum time for the step.
Pulse limits | Off: No pulse limit monitoring. From rundown complete: The monitoring starts when the Rundown complete torque is reached. From torque: The monitoring starts when the specific torque value is reached.
Final pulse monitoring torque | Torque value from when the pulse limits are monitored.
Pulses min | Minimum number of pulses to reach the final target.
Pulses max | Maximum number of pulses to reach the final target.
Premature torque loss detection time | A constant increase in torque is assumed when moving from rundown to tightening. A socket slip off, or a broken screw head can cause the torque to decrease. This may be detected in a monitoring window.

# Pulse Tightening with Direct Driven Electrical Tools

The principle below is applicable for direct driven electrical tools. It is applicable to the Atlas Copco SRB series of tools.

The pulse tightening uses a technique of pulsing the electrical current in the motor and has two distinct features:

- An action current that adds positive torque in the tightening direction.

- A reaction current that creates a comfort reaction by applying a reverse torque.

Pulse tightening principle

A | Action pulse to apply tightening force.
B | Reaction pulse for comfort

The figure shows the general principle of a current pulse tightening strategy. The detailed curve depends on the tool type and the tightening algorithm.

The pulse period consists of two phases as shown in the figure with an action current and a reaction current. Each action pulse adds torque to the tightening until the final target is reached. Each reaction pulse creates a counterforce that provides a comfortable reaction.

The energy level of the action phase and the reaction phase are configurable parameters. The combination of these two parameters creates an efficient tightening combined with operator comfort.

# Tightening using the TensorPulse Program

The principle below is applicable for direct driven electrical tool. It is applicable to the Atlas Copco SRB series of tools.

After each pulse period the resulting torque in the screw is increased. After a series of pulses, the final torque target is reached.

TensorPulse with maximum pulse energy

A | Maximum positive energy in pulse N
B | Maximum positive energy in pulse N+1
C | Increase in energy (torque)

The energy level in the action phase and reaction phase are user configurable parameters. The combination of these two parameters creates an efficient tightening combined with operator comfort. It is possible to set the amount of energy in the two phases as a percentage of the maximum energy that can be delivered in each period:

- Pulse energy; The amount of energy that is applied to each positive pulse as a percentage of the maximum energy that can be applied in the pulse period. The value is between 10-100%.

- Reaction force retention factor; The amount of energy that is applied to each reactive pulse as a percentage of the maximum energy that can be applied in the pulse period. The value is between 0-75%.

TensorPulse with reduced positive pulse energy

A | Reduced positive energy in pulse N
B | Reduced positive energy in pulse N+1
C | Resulting curve for torque build up using maximum pulse energy.
D | Resulting curve for torque build up using reduced pulse energy.

- A small Pulse energy (reduced energy) requires more pulses to reach the target torque as the torque is increased in smaller steps. Smaller steps provides better accuracy to terminate the tightening when the target is reached. Smaller pulses decrease tool movement and increases operator comfort.

- A correctly tuned Reaction force retention factor will create the desired operator comfort. If the factor is too high the operator feels a clockwise rotation of the tool. If the factor is too low, the operator feels a counter clockwise rotation of the tool.

- In an ideal configuration, the reaction energy does not create any loosening force. If the amount of pulses to reach the target value increases, the value is set too high and a small loosening occurs at each pulse.

The optimum values for the Pulse energy and the Reaction force retention factor need to be tuned for optimum performance of the tool and for best operator comfort.

# Trigger Lost

In the Step Configuration window of the program tightening stage, NOK on trigger lost switch controls whether or not it is allowed to release the tool trigger before the target condition has been reached. The setting can be set to On or Off. Below is a description of the two states.

Switch setting | Description
--- | ---
On | Releasing the trigger before reaching the target condition will result in a NOK tightening.
Off | Releasing the trigger before reaching the target condition will result in an OK tightening as long as all other conditions have been met.

The default behavior is that premature trigger release shall not be allowed.

Availability

The NOK on trigger lost is available in the following tightening strategies: Rotate, Quick Step, Two Step, Three Step and Impulse - single Step.

For the tightening strategies Rotate, Quick Step, Two Step and Three Step, Trigger Lost setting is only available when the Target of the program is set to Angle (not Torque).

# STwrench Strategies

# STwrench introduction

The STwrench is a torque wrench that can be used both for production and for quality control. Configurations of parameters can be made via the controller or via ToolsTalk 2.

The STwrench can be connected to a controller using a wireless connection. The STwrench can be configured through the controller GUI, the web GUI or the ToolsTalk 2 GUI.

The STwrench is configured in the Tightening section and uses the same workspace and menus as the other tightening strategies.

The STwrench has a Rapid Backup Unit (RBU). The RBU defines the wrench function and stores the tightening programs. The controller supports the RBU of the type Production.

The STwrench End-fitting tool (socket) contains a RFID TAG with a programmable number. The wrench uses this number to automatically recognize the tool and which program can be used. The RFID TAG also stores the torque and angle correction coefficients.

The STwrench has several programs for production tightening and for quality control. More details about the programs, strategies and the parameters are given in the STwrench user guide.

The STwrench can only support tightening programs which are supported by the tool, that is, Wrench-production and Wrench-quality.

Controller features, such as the Low Reaction Tightening Strategies and controller-wide functions among others, require licenses distributed through the Functionality Management System (FMS). Whereas configuration of features is possible without specific licenses, the assignment and use of those features will require the correct license to be installed on the controller. Please refer to Licenses (FMS) for more detailed information on licenses.

# STwrench Start Step Parameters

The parameters shown in the tables are available if one of the STwrench strategies are used. There are several combinations of strategies. Some of the parameters are only available for certain strategies and may not be visible in other strategies.

Parameter rules are automatically checked. If a violation occurs, the error indicator is displayed beside the incorrect parameters. Select the error indicator to display more information about the error.

Switching between strategies can result in the error indicator being shown. This indicates that the chosen combination is invalid, and needs to be corrected.

For more information about the STwrench, see the STwrench User Guide (printed matter number 9836 4134 01).

Parameters in the STwrench start step
Parameter name | Condition | Description | Default value
--- | --- | --- | ---
Tag number |  | On: after enabling TAG Check switch (Configurations > Tool Configuration > TAG Check > On), a correct TAG number is required to run the tightening program. Off: The TAG number is not checked. | Off
Required tag number | Tag number = On | The required TAG number for this tightening program. | 1
Rehit detection |  | The parameter options are: Complete or Off . | Off
Torque correction coefficient |  | In certain cases extensions may be needed to fit the application. In this case the wrench measurement must be compensated to show a correct value. For more information about to calculate the correction coefficient, see the STwrench User Guide (printed matter number 9836 4134 01). The parameter is stored in the RFID TAG in the End-fitting tool. | 1.0
Angle correction |  | In certain cases extensions may be needed to fit the application. In this case the wrench measurement must be compensated to show a correct value. To calculate the correction coefficient, please refer to the STwrench user guide. The parameter is stored in the RFID TAG in the End-fitting tool. | 0°

NOTICE

The correction coefficients alter the STwrench measurement. It may cause an improper reading. Before making any corrections, refer to the latest version of the STwrench User Guide (printed matter number 9836 4134 01).

# STwrench Rundown Step Parameters

The parameters shown in the tables are available if one of the STwrench strategies are used. There are several combinations of strategies. Some of the parameters are only available for certain strategies and may not be visible in other strategies.

Parameter rules are automatically checked. If a violation occurs, the error indicator is displayed beside the incorrect parameters. Select the error indicator to display more information about the error.

Switching between strategies can result in the error indicator being shown. This indicates that the chosen combination is invalid, and needs to be corrected.

For more information about the STwrench, see the STwrench User Guide (printed matter number 9836 4134 01).

Rundown complete is in the STwrench documentation defined as Cycle start , this is when the tightening step begins.

Parameters in the STwrench rundown step
Parameter name | Description | Default value
--- | --- | ---
Rundown complete torque | Definition of the Rundown complete point | Depends on the smarthead minload (usually 5% of nominal torque) in Nm
Ratchet time |  | 5000 ms

# STwrench Tightening Step Parameters

The parameters shown in the tables are available if one of the STwrench strategies are used. There are several combinations of strategies. Some of the parameters are only available for certain strategies and may not be visible in other strategies.

Parameter rules are automatically checked. If a violation occurs, the error indicator is displayed beside the incorrect parameters. Select the error indicator to display more information about the error.

Switching between strategies can result in the error indicator being shown. This indicates that the chosen combination is invalid, and needs to be corrected.

For more information about the STwrench, see the STwrench User Guide (printed matter number 9836 4134 01).

Parameters in the STwrench tightening step
Parameter name | Condition | Description | Default value
--- | --- | --- | ---
Target |  | Select the target from the drop-down menu. The parameter options are: Torque, Angle, Torque or Angle. | Torque
Target Torque |  | Defines the target torque for tightening step. | 0 Nm
Target Angle | Target = Angle | Defines the target angle for tightening step. | 360°
Torque limits | Target = Torque | Selection made by a switch. Auto or Manually position. |
Torque min | Torque limits = Manual | Torque value for the lower limit | 0 Nm
Torque max | Torque limits = Manual | Torque value for the upper limit | 0 Nm
Angle limits | Target = Angle | Selected from a drop-down menu. The parameter options are: Auto or Manually. Angle values for max and min can be or selected |
Angle limits | Target = Torque | Selected from a drop-down menu. The parameter options are: Off: No angle limit monitoring. From rundown complete: The monitoring window is set from when the Rundown complete torque is reached. From torque: The monitoring window is set from when the specific torque value is reached. |
Final angle monitoring torque |  | Torque value from when the angle limits are monitored | 18.75 Nm
Angle min | Angle limits = on or manually | Angle value lower limit | 324°
Angle max | Angle limits = on or manually | Angle value upper limit | 396°
Angle search limit | Angle limits = manually |  |
Measure torque at |  | Selected from a drop-down menu. The parameter options are: Max torque value Value at peak angle |
NOK on final less than target |  | Selection made by a switch. On or Off position. | Off
Change bolt limit |  |  | 50 Nm

Parameters in the STwrench tightening step if the strategy is Wrench - Production, and PVT compensate with snug
Parameter name | Condition | Description | Default value
--- | --- | --- | ---
Torque compensation point | Torque compensation = On |  | 0°
PCT distance | Torque compensation = On |  | 360°
PVT interval | Torque compensation = On |  | 180°
Delay monitoring | Torque compensation = On |  | 0°
Torque min | Torque compensation = On | Torque value for the lower limit | 1 Nm
Torque max | Torque compensation = On | Torque value for the upper limit | 20 Nm
Compensation value | Torque compensation = On | Selected from a drop-down menu. The parameter options are: Average torque Peak torque |

# STwrench Stop Step Parameters

The parameters shown in the tables are available if one of the STwrench strategies are used. There are several combinations of strategies. Some of the parameters are only available for certain strategies and may not be visible in other strategies.

Parameter rules are automatically checked. If a violation occurs, the error indicator is displayed beside the incorrect parameters. Select the error indicator to display more information about the error.

Switching between strategies can result in the error indicator being shown. This indicates that the chosen combination is invalid, and needs to be corrected.

For more information about the STwrench, see the STwrench User Guide (printed matter number 9836 4134 01).

Parameters in the STwrench loosening step
Parameter name | Condition | Description | Default value
--- | --- | --- | ---
End cycle time |  | It is applied when torque goes below the cycle start and gets to the third percentage value set on the STwrench LEDs. | 100 ms

# STwrench Loosening

The parameters shown in the tables are available if one of the STwrench strategies are used. There are several combinations of strategies. Some of the parameters are only available for certain strategies and may not be visible in other strategies.

Parameter rules are automatically checked. If a violation occurs, the error indicator is displayed beside the incorrect parameters. Select the error indicator to display more information about the error.

Switching between strategies can result in the error indicator being shown. This indicates that the chosen combination is invalid, and needs to be corrected.

For more information about the STwrench, see the STwrench User Guide (printed matter number 9836 4134 01).

Parameters in the STwrench loosening step
Parameter name | Condition | Description | Default value
--- | --- | --- | ---
Loosening limit |  | If this parameter is set to a value greater than 0, Power Focus checks if a negative torque exceeding this value is applied during the tightening. In that case, the overall status of the tightening is marked as Not OK. This function is started when the wrench reaches the Cycle Start (before starting the tightening, a loosening is allowed and does not produce results). This function is used to detect unwanted loosening at the end of a tightening (for instance, when the wrench is disengaged from the joint). | 0 Nm

# Multistep Tightening Strategy

A Multistep tightening is a tightening done in several steps. The number of steps and the type of the steps vary depending on the tightening to be done. A Multistep tightening program is highly configurable, including monitoring functions and restrictions. A total of ten steps can be added to a Multistep program.

Restrictions are used to make sure the tightening stops if something unexpected occurs. These restrictions could, for example, test that a maximum set torque is not reached or that a part of the multistep tightening does not take too long to run. Every step can have up to four restrictions each. Each step has mandatory step restrictions and optional step restrictions. The mandatory restrictions are included when dragging a new step to the multistep program.

Monitors are used to verify that the tightening was made according to the specification. This can be, for example, angle limits or torque limits. Every step can have up to eight monitors each. Each step has mandatory step monitors and optional step monitors. The mandatory monitors are included when dragging a new step to the multistep program.

WARNING

Risk of injury

A change in the configuration of the tightening program may cause unexpected torque, rotational direction, or speed in the system(s) where the tightening program is currently in use. This could result in severe bodily injury and/or property damage.

- Check the tightening program configurations after adding a new program or after applying changes to an existing program.

Controller features, such as the Low Reaction Tightening Strategies and controller-wide functions among others, require licenses distributed through the Functionality Management System (FMS). Whereas configuration of features is possible without specific licenses, the assignment and use of those features will require the correct license to be installed on the controller. Please refer to Licenses (FMS) for more detailed information on licenses.

In this Section

- Tightening Program Menu
- Properties Sub-Tab
- Adding a Multistep Program
- Tightening Editor

# Tightening Program Menu

Each row in the list represents one multistep tightening program.

Header | Description
--- | ---
Check box | Used for selecting a specific tightening program.
Name | A user-defined name.
Strategy | Selected strategy for the tightening program.
Library link | Linked to global library Yes/No.
Target |
Last changed | Time expressed in ToolsTalk 2 time.
Changed by | Tightening program changed by <user>
Controller updated | Controller updated, expressed in controller time.
Controller updated by | Controller updated by <user>
Approval status | Approval status of the tightening or loosening program

Tightening program workspace command buttons
Command | Description
--- | ---
Add | New. Creates a new tightening program. Import. Import a tightening program. File format is *.json
Manage | Add to library: Converts a Local tightening program into a Global tightening program. Unlink: Converts a Global tightening program into a Local tightening program. Compare: Compares two selected tightening programs. These must have the same strategy. Export. Exports a selected tightening program. File format is *.json Delete. Removes selected tightening program(s) from the list.

# Properties Sub-Tab

## Properties

Parameter | Description
--- | ---
Name | A user-defined name for the multistep program.
Description | Description of the multistep program.

Parameter | Description
--- | ---
Type | Tightening or loosening.
Thread direction | Clockwise (CW) or counter clockwise (CCW) rotational direction.
Loosening program | Select an existing loosening program to connect to the tightening program.
Program Start | The multistep tightening program starts when the torque passes the trigger torque value (Nm) for the first time, in order to avoid starting the program by accident.
Program End Torque | Gives the torque value that stops a multistep tightening. The signal 168 - Program End is true when, after a multistep tightening Program End Torque has reached, and Program End Timeout has elapsed. Default value for Program End Torque is Tool max torque * 0.03.
Program End Timeout | Gives the time value (in seconds) that stops a multistep tightening. The signal 168 - Program End is true when, after a multistep tightening Program End Torque has reached, and Program End Timeout has elapsed. Default value for Program End Timeout is 0 seconds.
True Angle Compensation | Certain tools can detect and measure the tool rotation during tightening. If the tool is rotated during tightening, the angle measurement may be corrupted. This may lead to a faulty tightening if the tool movement is too great. For variations within specified limits, the controller can compensate these rotations and make a correct tightening. This is an additional Licensed Feature, available per Virtual Station.

## Trace Configuration

The trace configuration can be done on program level or for each step. The default configuration is set on the program level and can be overridden in each step as needed.

Here, enabling this function allows the configuration to be done on program level.

Parameter | Description
--- | ---
Enabled | On: Enables the trace resolution configuration on program level. Off: The trace recording is done with the same resolution for the whole tightening. In this case, the trace points are evenly distributed in time over the whole tightening. For each time slot (0.25 ms) two values (the minimum and the maximum measured value) are displayed in the trace. The maximum number of samples in this format is 2000.
Sample Type | Sample Time: specifies how often samples should be stored in the trace by specifying a sample time in ms. Sample Angle: specifies how often samples should be stored in the trace by specifying a sample in deg.
Sample Time | Choose the sample time from the drop-down list (0.25 - 1000 ms)
Sample Angle | Choose the sample angle from the drop-down list (0.25 - 20 degree)

## Program Restrictions

Parameter | Description
--- | ---
Maximum Time Limit | Set amount in seconds. This restriction checks the total time for the tightening and if it exceeds the Time High limit the tool is stopped immediately. The time is measured from the start of the program.
Maximum Torque Limit | This restriction checks the torque and if the measured torque exceeds the Torque High limit the tool is stopped immediately.

Angle
Parameter | Description
--- | ---
Enabled | Turn angle restriction On or Off for the entire program. This restriction checks that the angle is within the specified angle limits.
Active in steps | Sets a range of steps this restriction is valid for: If no start step is specified, this restriction will start at program start. If no end step is specified, this restriction will stop at the last step of the program.
Trigger torque | Sets the value of the trigger torque at which the this restriction shall start.
High limit | Sets angle restriction (program) higher limit.

Time
Parameter | Description
--- | ---
Enabled | Turn time restriction On or Off for the entire program. This restriction checks that the time is within the specified time limits.
Active in steps | Sets a range of steps this restriction is valid for: If no start step is specified, this restriction will start at program start. If no end step is specified, this restriction will stop at the last step of the program.
Trigger torque | Sets the value of the trigger torque at which this restriction shall start.
High limit | Sets time restriction (program) higher limit.

## Program Monitors

Angle
Parameter | Description
--- | ---
Enabled | Turn angle monitoring On or Off for the entire program. This monitor checks that the angle is within the specified limits.
Active in steps | Sets a range of steps this monitor is valid for: If no start step is specified, this monitor will start at program start. If no end step is specified, this monitor will stop at the last step of the program.
Type | Type of angle monitoring: Peak Angle: the highest angle reached during the monitor. Angle at Peak Torque: the angle at the point where the highest torque was reached during the monitor. Shut Off Angle: the angle at the shut-off point of the step. Angle at End: the angle at the end of the monitor, including the brake, if active.
Trigger torque | Sets the value of the trigger torque at which this monitor shall start.
Low limit | Sets angle monitoring (program) lower limit.
High limit | Sets angle monitoring (program) higher limit.

Torque
Parameter | Description
--- | ---
Enabled | Turn Torque monitoring On or Off for the entire program. This monitor checks that the torque is within the specified limits.
Active in steps | Sets a range of steps this monitor is valid for: If no start step is specified, this monitor will start at program start. If no end step is specified, this monitor will stop at the last step of the program.
Type | Type of angle monitoring: Peak Torque: the highest torque reached during the monitor. Shut Off Torque: the torque at the shut-off point of the step.
Low limit | Sets torque monitoring (program) lower limit.
High limit | Sets torque monitoring (program) higher limit.

Time
Parameter | Description
--- | ---
Enabled | Turn time monitoring On or Off for the entire program. This monitor checks that the time is within the specified limits.
Active in steps | Sets a range of steps this monitor is valid for: If no start step is specified, this monitor will start at program start. If no end step is specified, this monitor will stop at the last step of the program.
Trigger torque | Sets the value of the trigger torque at which this monitor shall start.
Low limit | Sets time monitoring (program) lower limit.
High limit | Sets time monitoring (program) higher limit.

## Validation

During the configuration of tightening programs, the entered values are compared with the tool capability values to prevent parameters being outside the selected limits. User-defined maximum values are useful if many different tools are being used.

Parameter | Description
--- | ---
Validate against tool values | Use On to set Max Torque and Max Speed manually, or select a specific tool in order to validate against the selected tool's values. When a specific tool is selected, the steps and monitors not supported by the specific tool are indicated by a yellow triangle.
Max Torque | The maximum limit used in the validation. This is expressed in a numeric torque value.
Max speed | The maximum limit used in the validation. This is expressed in a numeric rpm value.

## Attachment Tuning

Attachment tuning gives the possibility to compensate for front attachments on the tool. The compensation can be made for each tightening program.

An operator can hot swap attachments and then select a tightening program tuned for that specific attachment.

Parameter | Description
--- | ---
Use Attachment Tuning | Yes or No
Gear Ratio | The Attachment gear ratio is needed to compensate the angle. Minimum: 0.5 Maximum: 100 Socket rotation speed = Tool speed / gear ratio
Efficiency Tuning | Attachment gear ratio combined with the Efficiency tuning is needed to compensate the torque. Minimum: 0.5 Maximum: 1.0 For example 0.9 means 10% efficiency loss.

## Reporters

This enables the user to choose which values (from monitors/restrictions) shall be shown as final values. Click Add to choose a result reporter to be tied to a program monitor/restriction value.

Parameter | Description
--- | ---
Reporter | Select a result reporter.
Producer | Select which monitor/restriction produces the value.
Value | Select which value to show from the selected producer.

# Adding a Multistep Program

1. Select the Add button. The Create new Tightening program dialog window opens.

2. Enter tightening program name, index number (only valid for tightenings), operation mode and select tightening strategy Multistep. The tightening program will be issued with the next sequential number in the list of programs, if no active selection of the index is made.

3. Select the Add button.

   The multistep has two sub-tabs Properties, where the different parameters of the program can be entered and Tightening editor, where a program can be created.

# Tightening Editor

## Buttons

Name | Description
--- | ---
Display | Repair - Show or hide the repair area. Terminate - Show or hide the terminate area. Monitor - Show or hide the step monitors. Restriction - Show or hide the step restrictions. Direction Arrow - Show or hide the direction arrow. Display DropArea Help - Show or hide the DropArea help.
Zoom in | Zooms in on the tightening program.
Zoom out | Zooms out from the tightening program.
Fit to screen | Fits the whole tightening program to the drag and drop area.
Delete | Deletes the selected item.

## Repair Area

The steps in the repair area show the repair path to be followed if the status at a synchronization point is NOK.

A repair path always starts and ends at a synchronization point. Where the repair path should re-enter the tightening path is flexible, but the repair path must always go back towards the beginning of the program.

Only one repair path can start in each synchronization point, but several repair paths may end at the same synchronization point.

The number of steps to run in the repair path can be between 1 and 3.

It is not possible to define a repair path from the start of the program.

Example: Repair paths

A | Repair path from the first synchronization point to the start of the program.
B | Repair path from the third synchronization point to the second synchronization point.

## Tightening Area

The tightening area includes the tightening path, i.e., the steps and synchronization points in the multistep tightening program excluding repair and termination paths.

## Number of Tightening Steps, Restrictions and Monitors Allowed

| Number of Steps Allowed | Number of restrictions Allowed | Number of monitors Allowed
--- | --- | --- | ---
PF6000/PF8 | 16 | 8 | 8
PF6000/PF8 Step Sync | 25 (excluding syncpoints and repair- and termination paths) | 8 | 8
Flex | 25 (excluding syncpoints and repair- and termination paths) | 8 | 8
IxB | 16 | 5 | 8

## Terminate Area

The steps in the terminate area shows the terminate path followed if the status at a synchronization point is fatal. After the termination path is done the tightening is ended. A termination path always starts at a synchronization point. Only one termination path can start in each synchronization point.

The number of steps to run in the termination path can be between one and three.

It is always possible to terminate from all synchronization points. If no termination path is defined, the program will go directly to the end without running any other steps.

Example: Termination path

A | Termination path from the first synchronization point to the end of the program.
B | Termination path from the third synchronization point to the end of the program.

## Configuration

1. Select on the step, restriction or monitor and click on Configuration at the bottom of the screen to open the Configuration field. To select multiple steps, use Ctrl.

   The Configuration field contains different parameters for the steps, monitors and restrictions based on which step, monitor or restriction is selected in the repair area.

2. Enter the required parameters.

   To delete a monitor or restriction, select Delete which is present in that field.

## Using speed shifts

You can define 1-5 angle triggers or torque triggers during a step, where the speed will shift.

The speed shifts can be added in the Configuration field.

Within one step, all the speed shift triggers are based on the same property, i.e. either torque or angle. They cannot be mixed within one step.

To add a speed shift:

1. In the dialog box of a step that can have speed shifts, click Add speed shift and choose an angle range or a torque range. The Speed Shift Angle/Torque fields open.

2. Add values according to the table below.

Parameter | Description
--- | ---
Angle/Torque trigger | Must be > 0.
Speed | Must be > 0.
Speed ramp type | Hard or soft.

The Torque triggers and Angle triggers must be less than the step target, depending on the type of the step and the trigger type.

The Torque trigger and Torque speed also validate against the Max torque and Max speed of the tool. A warning or error indicator occurs whenever the Speed Shift settings exceed either the tool max values or step max values.

It is possible to push the settings to the controller when a tightening program has a warning, but not when a tightening program has an error(fault) indicator.

## Tool Box

The Tool box includes:

- Steps

- Monitors

- Restrictions

- Result Reporters

- Templates

## Drag and drop area shortcut keys

Shortcut key | Description
--- | ---
Space bar + cursor | Move Drag and drop area.

## Drag and drop area functions

Function |  | Description
--- | --- | ---
Add step |  | Grab a step in the Tool box. Drag the step to the desired position. Possible positions are indicated by a light blue indication arrow.
___________ | __________________________ | _________________
Mark a step |  | Click on a step to mark it.
___________ | __________________________ | _________________
Move a step |  | To move a step, click on the step and hold the button pressed while moving.
___________ | __________________________ | _________________
Copy step |  | To copy a step, click the Ctrl button and drag and drop the step.
___________ | __________________________ | _________________
Add repair path |  | Place the step above the synchronization point from where the repair part should start.
___________ | __________________________ | _________________
Add repair step | OR | Place a step in the Repair area to add a repair step. Possible positions are indicated by a light blue indication arrow. or Place the step above the synchronization point from where the repair part starts. The step is then placed before the first step in the repair path.
___________ | __________________________ | _________________
Add terminate path |  | Place the step below the synchronization point from where the termination part should start.
___________ | __________________________ | _________________
Add terminate step | OR | Place a step in the Terminate area to add a terminate step. Possible positions are indicated by a light blue indication arrow. or Place the step below the synchronization point from where the termination part starts. The step is then placed before the first step in the termination path.
___________ | __________________________ | _________________
Move endpoint for repair path. |  | Click the small arrow to move the endpoint of the repair path.
___________ | __________________________ | _________________
Add restriction and monitor |  | Grab a restriction or a monitor in the Tool box. Drag the restriction or monitor to desired step. Possible steps to add a restriction or monitor to, are indicated by changing to a lighter blue color.
___________ | __________________________ | _________________
Forbidden placement |  | A red arrow indicates that it is not possible to place a step.

In this Section

- Tightening Steps
- Step Monitors
- Step Restrictions
- Deleting a Multistep Program
- STB Tools and Multistep
- Result Reporters
- Multistep Template

# Tightening Steps

The availability of tightening steps, monitors and restrictions depends on the license installed on the controller.

## General Parameters

The following step parameters are common for many of the step types. The parameters are set in the step properties window which is displayed when selecting a step in the tightening program.

Parameter | Description
--- | ---
Name | Name of the step.
Rotational direction | Each of the tightening steps can run either forward, that is to make a tightening, or reverse, to loosen the screw slightly. The arrows indicate this direction. Many of the tightening steps have a direction hard-coded to forward, for example Tighten to Angle, or Tighten to Torque. Steps such as Loosen to Angle or Loosen to Torque have their direction automatically set to reverse. The reverse setting is not allowed for tools configured with Gear Front Attachment (GFA) of type open end. The tightening direction of the tightening program must be the same as the tightening direction of the open end tool for a tightening to be allowed to be run. It is possible to assign a loosening program to a tightening program for an open end tool, but if the direction switch is set to run the loosening program, the tool will be locked.
Step category | For each step, there is an option to choose a step category. By selecting step category, the NOK tightenings will be listed in the event result view with related detailed status together with the corresponding multistep error information. If no selection is made, the detailed status will be set to uncategorized multistep error. The related detailed status can be customized.
Angle window | A joint is considered Hard if the screw is tightened to its full torque and it rotates 30 degrees (or less) after it has been tightened to its snug point. A Soft joint rotates 720 degrees or more after it has been tightened to its snug point. The hardness parameter defines the Angle Window for the gradient calculation. The harder the joint - the smaller the angle window.
Speed Ramp / Acceleration (only available in ToolsTalk 2) | For most of the steps it is possible to specify how the acceleration to the target speed should be achieved. Three different settings are possible; Hard, Soft and Manual. The acceleration defined will be used whenever a step is started. Regardless whether the tool is already running with speed at the beginning of the step, the ramp will be used to accelerate to the target speed of the step. This will be the case even if the speed at the start of the step is higher, or lower than the target speed.
Speed ramp - Hard and Soft mode | Hard: 2000 rpm/s (Speed Ramp between 1000 and 10000 rpm/s is a Hard acceleration.) Soft: 500 rpm/s (Speed Ramp between 200 and 1000 rpm/s is a Soft acceleration.)
Speed ramp - Manual mode | Speed: Default value: 60 rpm Minimum limit: > 0 Maximum limit: ≤ Tool Max Speed Acceleration: Default value: 500 rpm/s Minimum limit: > 0 Maximum limit: ≤ Tool Max Acceleration
Using speed shifts | 1−5 angle triggers or torque triggers can be defined during a step, where the speed will shift. Within one step, all the speed shift triggers are based on the same property, that is either torque or angle. They cannot be mixed within one step. The Torque triggers and Angle triggers must be less than the step target, depending on the type of the step and the trigger type. The Torque trigger and Torque speed also validate against the Max torque and Max speed of the tool. A warning or error indicator occurs whenever the Speed Shift settings exceed either the tool max values, or step max values. The Torque triggers and Angle triggers must be less than the step target, depending on the type of the step and the trigger type. The Torque trigger and Torque speed also validate against the Max torque and Max speed of the tool. A warning or error indicator occurs whenever the Speed Shift settings exceed either the tool max values, or step max values. It is possible to push the settings to the tool when a tightening program has a warning, but not when a tightening program has an error (fault) indicator. The speed shifts can be added in the Configuration field. To add a speed shift: In the dialog box of a step that can have speed shifts, select Add speed shift. Then, select an angle range or a torque range. The Speed Shift Angle/Torque fields open. Add values according to the table below: Angle/Torque trigger: Must be > 0 Speed: Must be > 0 Speed ramp type: Hard or soft
Brake type | The braking behavior of a multistep tightening program can be controlled at two possible locations in the program: in a step preceding a reversal of direction of the tightening, and/or at the final step of the tightening program. At other locations in the tightening program, the braking parameters will not be available in the step's general settings. Braking can be set to either Ergo stop or Inertia. Inertia will brake the tool completely, while Ergo stop will allow for a more ergonomic slowing down of the tightening. Inertia has no additional parameters. Ergo stop parameters: Adaptive brake: Set the Adaptive Brake to On or Off Ramp time: Only available when Adaptive Brake is set to Off. Insert time in ms.
Exclude in MCT mode | The Exclude in MCT mode option can be turned on for steps in a Multistep program. When using the MCT mode for a Multistep program, steps with Exclude in MCT mode turned on will be excluded. Setting the Exclude in MCT mode option to on in such a way that there is no break before a wait step or direction switch will result in an error in runtime when in MCT mode. Termination Paths and Repair paths are ignored on fixtured systems, i.e. if they are triggered the tightening will be marked as NOK MC tightening. MCT mode is only to be used when testing. Make sure MCT mode is disabled before returning the tool to the production line.

The following tightening steps are not supported for tools configured with Gear Front Attachment (GFA) of type open end:

- A - Tighten to Angle / Loosen to Angle

- TrR - Loosen to Trigger Release

- T - Tighten to Torque / Loosen to Torque

- E - Engage

- SR - Socket Release

- DT - Tighten to DynaTork

- TPT - TensorPulse Tighten to Torque / Loosen to Torque

- IT - Impulse Tighten to Torque / Loosen to Torque

- IA - Impulse Tighten to Angle / Loosen to Angle

- AP - Adaptive Pulse

- ITrR - Impulse Loosen to Trigger Release

## Trace Settings

When the trace configuration is enabled on the program level, the trace resolution can be configured on step level. The setting for Trace Setting defines how the sampling should be done on each specific step.

Parameter | Description
--- | ---
Trace Setting | Program: Use the settings as defined on program level. Manual: The trace sample type from the program level will be used, that is, Time or Angle. Using a different sample rate will override the setting on the program level.
Sample Time | Choose the sample time from the drop-down list (0.25 - 1000 ms)
Sample Angle | Choose the sample angle from the drop-down list (0.25 - 20 degree)

With this trace recording the sample rates will not be the same in all the steps, instead the sample rate depends on the configuration in each step. This means the trace is divided into one trace for each step.

The maximum number of samples in a trace is 4096.

If a tightening produce more than 4096 values a down-sampling will take place. This is done by removing every second trace sample from the whole tightening and when continue the recording with half the resolution. This process will be repeated every time the 4096 sample limit is reached.

If more than 2048 in total was recorded, this process will result in a trace between 2048 and 4096 samples.

If the limit if 4096 samples is reached the configured trace sample times will no longer be followed. Instead the sample times will be doubled or quadrupled etc., depending on how many times the down sampling has taken place. Since all steps are down sampled the relation between the steps will still be the same though. If a step was configured with double sample time compared to another step, this will still be the case in the final trace regardless how many times a down-sampling has occurred.

Trace channel | Note
--- | ---
Torque | Available for all tools equipped with a torque transducer
Angle | Available for all tools
Torque Second | Only available for tools with two torque transducers
Angle Second | Only available for tools with two angle transducers
Current | Available for all tools
Gradient | Available if some step/restriction/monitor produces the gradient values

Available tools for each system type
Power Focus 6000 / Power Focus 8 | Power Focus 6000 Synchronized tightening / Power Focus 8 Synchronized tightening | Flex | IxB
--- | --- | --- | ---
ST | ST | QST | IxB
STR | STR |  |
SL | QST |  |
QST |  |  |
STB |  |  |
IxB |  |  |
Power Focus Connect |  |  |
XB |  |  |

Tightening Steps
Tools
Search

# A – Tighten to Angle / Loosen to Angle

Tools
ES STR SL ST SR QST STB IXB

A – Tighten to Angle

This step runs the tool until the target angle is reached. The target angle is measured from the start of the step.

A – Loosen to Angle

This step runs the tool with the speed n in the backward direction until the angle target is reached. The target angle is measured from the start of the step.

This step is not supported for tools configured with Gear Front Attachment (GFA) of type open end.

Parameters

Parameter | Description
--- | ---
Target angle | The angle target. Must be > 0.
Speed | Default: 60 rpm.
Speed ramp type | Hard, soft, or manual. Default: Hard. If you select Manual, the Speed ramp field opens.
Speed ramp | If Speed ramp type is Manual, this field opens. Default: 500 rpm/s.
Brake (Valid only for Power Focus 6000 Synchronized tightening, Power Focus 8 Synchronized tightening and Flex). | If On the tool will be stopped when the target is reached. If Off the program goes directly to the next step without stopping the tool.

Point and click on image to see more information:

A | Target Angle

## Microvideo

A - Tighten to Angle / Loosen to Angle

# C - Clutch

Tools
BCV BCP

This step will run the tool with the programmed Speed in forward direction until the Clutch has been released. When the tool has reported the release of the Clutch the step will finish with OK status.

A tightening program using the Clutch step cannot have any other step assigned.

This step is only valid for the Clutch tools BCV-RE and BCP-RE.

Parameter | Description
--- | ---
Speed Control | One Speed or Two Speed
Final Speed | Sets the final speed of the program [rpm]
Speed Ramp | Switch where speed ramp can be chosen [Hard, Soft]
Rehit | Rehit detection set to On or Off
Rehit angle | Sets the rehit angle [°]

# CL - Clutch Loosening

Tools
BCV BCP

This step will run the tool with the programmed speed in reverse direction until the tool trigger is released.

A loosening program using the Clutch step can not have any other step assigned.

This step is only valid for the Clutch tools BCV-RE and BCP-RE.

Parameter | Description
--- | ---
Final | Sets the speed of the program [rpm]

# DI – Run Until Digital Input

Tools
ES STR SL ST SR QST

This steps runs the tool, in the direction defined by parameter Direction, until the input specified by Digital Input goes high or low depending on the value of Stop Condition.

Parameter | Description
--- | ---
Direction | Forward, or Backward
Digital Input | One of the following local digital inputs on the controller can be selected: Local DI 1 Local DI 2 Local DI 3 Local DI 4
Brake (Valid only for Power Focus 6000 Synchronized tightening, Power Focus 8 Synchronized tightening and Flex). | If On the tool will be stopped when the target is reached. If Off the program goes directly to the next step without stopping the tool.
Stop Condition | Falling edge: The steps runs until a falling edge is detected after step start. Rising edge: The steps runs until a rising edge is detected after step start. Any edge: The step runs until a falling or a rising edge is detected after step start. Low: The step runs until low value is detected. High: The step runs until high value is detected.
Speed (rpm) | Default: 60 rpm.
Speed ramp type | Hard, soft, or manual. Default: Hard. If you select Manual, the Speed ramp field opens.
Speed ramp | Available if Speed ramp type is Manual. Default: 500 rpm/s.

## Microvideo

DI - Run Until Digital Input

# DT – Tighten to DynaTork

Tools
ES STR SL ST SR QST STB IXB

This step is not supported for tools configured with Gear Front Attachment (GFA) of type open end.

This step runs the tool with speed n in the forward direction until the Target torque is reached. The tool will then hold the current constant at the DynaTork Percentage of Target torque during the DynaTork time.

To avoid overheating of the tool, it is strongly recommended to never run DynaTork to more than 40% of the maximum torque of the tool.

Parameter | Description
--- | ---
Target torque | The torque target. Must be > 0.
DynaTork Time | The time DynaTork will be active.
DynaTork Percentage | The percentage of Torque target.
Speed ramp type | Hard, soft, or manual. Default: Hard. If you select Manual, the Speed ramp field opens.
Speed ramp | If Speed ramp type is Manual, this field opens. Default: 500 rpm/s.
Speed (rpm) | Default: 60 rpm.
Brake (Valid only for Power Focus 6000 Synchronized tightening, Power Focus 8 Synchronized tightening and Flex). | If On the tool will be stopped when the target is reached. If Off the program goes directly to the next step without stopping the tool.

Point and click on image to see more information:

A | Target Torque
B | Torque level retained during DynaTork Time
C | Percentage of Ts
D | Percentage of Ts
E | Torque level retained during DynaTork Time
F | DynaTork Time

## Microvideo

DT - Tighten to DynaTork

# E - Engage

Tools
ES STR SL ST SR QST IXB

This step is not supported for tools configured with Gear Front Attachment (GFA) of type open end.

This step runs the tool in both directions until the socket engages the screw. The step continues until Target torque or Target angle is reached, provided that Continue if not Engaged is set to Yes. If Target Angle is reached in any direction, the direction is reversed. Limit the search iterations by entering Max Engage Attempts. If Target Torque is reached in any direction the step will finish with OK status.

## Microvideo

E- Engage

# Ext - External Result

Tools
ES STR SL ST SR QST STB IXB BCP BCV External Tool

External result is a strategy used when an OK tightening is indicated by an external digital signal (and not by torque or angle values measured during tightening). This external signal can be provided through any means that can provide a digital signal into the controller (e.g through the I/O bus).

When the signal is sent, the result view (logged data) will show the value of the Target parameter provided in the tightening program (specified torque value, angle value, or text string). These (torque and angle) values do not represent actual measured values, but only inserted text.

Parameter | Description
--- | ---
Torque <Target torque> | Numerical value for desired displayed target torque value. A signal could for example come from a Click Wrench and display <Target torque>.
Angle <Target angle> | Numerical value for desired displayed target angle value. A signal could for example come from a Click Wrench and display <Target angle>.
Text | Alphanumerical string for desired displayed text. For example: "Oil has been changed".

# MWR - Mechatronic Wrench

Tools
MWR

Mechatronic Wrench is a specialized step that can be used only in conjunction with the Mechatronic Wrench (MWR).

This step cannot be used in combination with other steps. No restrictions can be used with this step. By default, the step has three monitors: Peak Torque, Angle, and Click.

Parameter | Description
--- | ---
Loosening limit | Numerical value for negative torque (i.e. torque in the loosening direction) at which point the tightening result is marked as NOK (False direction of tightening (loosen)); in Nm.
Tool Size | Numerical value for the specific length of the end fitting tool installed on the MWR-TA; in mm.
Tool Bend | Numerical value for the end fitting tool installed on the MWR-TA; in °/Nm.
Rehit Angle Window | Numerical value for the angle for determining if the screw was already tightened if the torque is reached; in °.
Max Angular Rate | Numerical value for the max rate at which the screw can be tightened; in °/s.

# RD – Rundown

Tools
ES STR SL ST SR QST IXB

Rundown step is the part of the tightening from when the screw enters the thread until just before the screw head touches the underlying surface and snug point is reached. The torque required during rundown does not contribute to any clamping force.

This step runs the tool with the speed in the forward direction, and depending on the Rundown Type, Torque or Snug the step behavior is as follows:

Rundown Type: To Torque: The step stops when the specified target torque is found.

Rundown Type: To Snug: The snug gradient calculation starts at the specified torque trigger level Tt. If no torque trigger is set the gradient calculation is started at the start of the step.

The slope calculation is made between two angle points Ad degrees apart and is calculated as: (Tn – Tn-1) / (An – An-1) and as soon as two slopes after each other are larger than TSLOPE the snug point is found.

Parameter | Description
--- | ---
Rundown type | To Torque or To Snug.
Target torque | Default: "not set". Must be > 0.
Speed | Default: 60 rpm. Must be > 0.
Speed ramp type | Hard, soft, or manual. Default: Hard. If you select Manual, the Speed ramp field opens.
Speed ramp | If Speed ramp type is Manual, this field opens. Default: 500 rpm/s.
Trigger Torque | If Rundown type is To Snug, the Trigger torque field is displayed. Default: "not set". Must be > 0.
Delta Angle | If Rundown type is To Snug, the Delta angle field is displayed. Default: "0". Must be > 0.
Torque Rate | If Rundown type is To Snug, the Torque rate field is displayed. Default: "0". Must be > 0.
Brake (Valid only for Power Focus 6000 Synchronized tightening, Power Focus 8 Synchronized tightening and Flex). | If On the tool will be stopped when the target is reached. If Off the program goes directly to the next step without stopping the tool.

Point and click on image to see more information:

A | Snug Point
B | Angle Delta
C | Torque Slope
D | Torque Target
E | Torque Trigger

# SR - Socket Release

Tools
ES STR SL ST SR QST STB IXB

This step is not supported for tools configured with Gear Front Attachment (GFA) of type open end.

This step runs the tool with speed n in the backward direction until the target angle is reached. The target angle is measured from the start of the step.

This step is only allowed to use as the last step in the tightening path of a multistep tightening program. However, it is possible to add a sync point after this step.

Parameter | Description
--- | ---
Target angle | The angle target. Default: 3 degrees, must be > 0
Speed ramp type | Hard, soft, or manual. Default: Hard. If you select Manual, the Speed ramp field opens.
Speed ramp | If Speed ramp type is Manual, this field opens. Default: 500 rpm/s.
Speed | Default: 60 rpm.

# SZP - Set Zero Position

Tools
ES STR SL ST SR QST

The step Set Zero Position sends out the signal set zero position to the tool. The position is repeated once every 360 degrees.

With the steps Loosen to Zero Position or Tighten to Zero Position it is possible to return the tool to zero position.

This step does not have any parameters.

The zero position is a specific position stored with either a “Set Zero Position” step or the signal “Set Zero Position”. The position is repeated once every 360 degrees.

# T - Tighten to Torque / Loosen to Torque

Tools
ES STR SL ST SR QST STB IXB

T – Tighten to Torque

This step runs the tool with the programmed speed in forward direction until the target torque is reached.

Parameter | Description
--- | ---
Target torque | The torque target. Must be > 0.
Speed ramp type | Hard, soft, or manual. Default: Hard. If you select Manual, the Speed ramp field opens.
Speed | Default: 60 rpm. Must be > 0.
Speed ramp | If Speed ramp type is Manual, this field opens. Default: 500 rpm/s.
Brake (Valid only for Power Focus 6000 Synchronized tightening, Power Focus 8 Synchronized tightening and Flex). | If On the tool will be stopped when the target is reached. If Off the program goes directly to the next step without stopping the tool.

## Microvideo

T - Tighten to Torque

T – Loosen to Torque

This step is not supported for tools configured with Gear Front Attachment (GFA) of type open end.

This step runs the tool with the speed in the backward direction. For the step to be active, the torque must first exceed 110 % of the Target torque. The Target torque should be set to a positive value. After reaching the target torque, the step runs until the torque drops below the target torque.

Parameter | Description
--- | ---
Target torque | The torque target. Must be > 0.
Speed ramp type | Hard, soft, or manual. Default: Hard. If you select Manual, the Speed ramp field opens.
Speed | Default: 60 rpm. Must be > 0.
Speed ramp | If Speed ramp type is Manual, this field opens. Default: 500 rpm/s.
Brake (Valid only for Power Focus 6000 Synchronized tightening, Power Focus 8 Synchronized tightening and Flex). | If On the tool will be stopped when the target is reached. If Off the program goes directly to the next step without stopping the tool.

Point and click on image to see more information:

A | Target Torque

# T&A – Tighten to Torque and Angle

Tools
ES STR SL ST SR QST STB IXB

This tightening step runs the tool with the given speed in the forward direction until both the target torque and the target angle are reached.

The torque measurement starts at the beginning of the step.
If the torque trigger is NOT set, the angle measurement starts at the beginning of the step.
If the torque trigger is set, the angle measurement starts when the torque trigger is reached.

The step ends when:
Measured Torque >= Target Torque (Ts)
AND
(Measured Angle - Angle Measured at Torque Trigger) >= Target Angle (As).

Parameter | Description
--- | ---
Target torque (Ts) | Default value: 0. Must be > 0 and <= Tool Max Torque.
Target angle (As) | Default value: 0. Must be > 0.
Torque Trigger (Tt) | Default value: NOT set. Must be > 0 and < Target torque (Ts).
Speed (n) | Default: 60 rpm. Must be > 0 and <= Tool Max Speed.
Speed ramp type | Hard, soft, or manual. Default: Hard. If you select Manual, Speed ramp type opens automatically.
Brake (Valid only for Power Focus 6000 Synchronized tightening, Power Focus 8 Synchronized tightening and Flex). | If On the tool will be stopped when the target is reached. If Off the program goes directly to the next step without stopping the tool.

Point and click on image to see more information:
Tightening to Torque AND Angle, without Torque Trigger set

A | Target Torque
B | Target Angle

Point and click on image to see more information:
Tightening to Torque AND Angle, with Torque Trigger set

A | Target Torque
B | Torque Trigger
C | Target Angle

# T|A – Tighten to Torque or Angle

Tools
ES STR SL ST SR QST STB IXB

This tightening step runs the tool with the given speed in the forward direction until either the target torque or the target angle is reached.

The torque measurement starts at the beginning of the step.
If the torque trigger is NOT set, the angle measurement starts at the beginning of the step.
If the torque trigger is set, the angle measurement starts when the torque trigger is reached.

The step ends when:
Measured Torque >= Target Torque (Ts)
OR
(Measured Angle - Angle Measured at Torque Trigger) >= Target Angle (As).

Parameter | Description
--- | ---
Target torque (Ts) | Default value: 0. Must be > 0 and <= Tool Max Torque.
Target angle (As) | Default value: 0. Must be > 0.
Torque Trigger (Tt) | Default value: NOT set. Must be > 0 and < Target torque (Ts).
Speed (n) | Default: 60 rpm. Must be > 0 and <= Tool Max Speed.
Speed ramp type | Hard, soft, or manual. Default: Hard. If you select Manual, Speed ramp type opens automatically.
Brake (Valid only for Power Focus 6000 Synchronized tightening, Power Focus 8 Synchronized tightening and Flex). | If On the tool will be stopped when the target is reached. If Off the program goes directly to the next step without stopping the tool.

Point and click on image to see more information:
Tightening to Torque OR Angle, without Torque Trigger set

A | Target Torque
B | Target Angle

Point and click on image to see more information:
Tighten to Torque OR Angle, with Torque Trigger set

A | Target Torque
B | Torque Trigger
C | Target Angle

# T+A – Tighten to Torque Plus Angle

Tools
ES STR SL ST SR QST STB IXB

This step runs the tool until the target torque is reached. From this point it continues to run an additional target angle.

Parameter | Description
--- | ---
Target torque | The torque target. Must be > 0.
Target angle | The angle target. Must be > 0.
Speed ramp type | Hard, soft, or manual. Default: Hard. If you select Manual, the Speed ramp field opens.
Speed ramp | If Speed ramp type is Manual, this field opens. Default: 500 rpm/s.
Speed | Default: 60 rpm.
Brake (Valid only for Power Focus 6000 Synchronized tightening, Power Focus 8 Synchronized tightening and Flex). | If On the tool will be stopped when the target is reached. If Off the program goes directly to the next step without stopping the tool.

Point and click on image to see more information:

A | Target Torque
B | Target Angle

# TC - Torque Calibration

Tools
QST

This step is only supported for multiple transducer tools.

The Torque Calibration step runs the tool with the specified speed in the forward direction until the torque target is reached.

Parameter | Description
--- | ---
Target torque | Must be > 0.
Speed | Must be > 0. Default: 60 rpm.
Transducer | Torque or Torque 2. Default: Torque. Set to Torque 2 in order to calibrate the front transducer.
Adaptive brake (Valid only for Power Focus 6000 Synchronized tightening, Power Focus 8 Synchronized tightening and Flex). | If On the tool will be stopped when the target is reached. If Off the program goes directly to the next step without stopping the tool.

# ThCT – Thread Cutting to Torque

Tools
ES STR SL ST SR QST STB IXB

The Thread Cutting to Torque function enables tightening where the Rundown torque required is greater than the Rundown complete torque, for example when tightening thin layers of metal using self-threading (or self-tapping) screws. The tool runs in forward direction until the Thread Cutting Angle (Aw) is reached. The thread cutting angle window is measured from when the torque passes Thread Cut Trigger Torque (Ttc) for the first time. From the point where Thread cutting angle is reached, the step continues to run until the Target Torque (Tt) is reached.

Parameter | Description
--- | ---
Target torque | Must be > 0.
Thread Cutting Angle Window | Default: 0. Must be > 0.
Trigger Torque | The angle measurement starts at this trigger.
Speed | Default: 60 rpm. Must be > 0.
Speed ramp type | Hard, soft, or manual. Default: Hard. If you select Manual, the Speed ramp field opens.
Brake (Valid only for Power Focus 6000 Synchronized tightening, Power Focus 8 Synchronized tightening and Flex). | If On the tool will be stopped when the target is reached. If Off the program goes directly to the next step without stopping the tool.

Point and click on image to see more information:

A | Target Torque
B | Torque Trigger
C | Thread Cutting Angle Window

# TPT - TensorPulse Tighten to Torque / Loosen to Torque

Tools
STR IXB

Before using TensorPulse tightening/loosening step, it is mandatory that the following license type is installed on the controller:

- Low Reaction Strategies

TensorPulse is valid only for the following tools: ETV-STR61-100-13, ETV-STR61-70-13, ETV-STR61-50-10, ITB-P.

This step is not supported for tools configured with Gear Front Attachment (GFA) of type open end or closed end.

TensorPulse Tighten to Torque

This step generates tightening pulses in the forward direction, until the torque target is reached.

TensorPulse Loosen to Torque

This step generates tightening pulses in the backward direction, until torque is below torque target.

If running TensorPulse tightening/loosening step, use the necessary PulseDrive socket/adapter.
If TensorPulse tightening/loosening step runs without the PulseDrive socket/adapter, all the tightenings are NOK. The step error “PulseDrive socket/adapter not detected” shows for no PulseDrive socket/adapter.

Parameter | Description
--- | ---
Torque Target - Ts | Torque Target must range from 0 through the maximum torque of the tool.
Pulse Energy - Pe | Pulse Energy is used to control the amount of energy/current in each pulse. Pulse Energy must range from 10% through 100 %. By default, it is set to 100%.
Reaction Force Tuning Factor | Reaction Force Tuning Factor is used to tune the reaction force when running TensorPulse step. It is the power that moves the tool in the opposite direction after each pulse. High tuning factor makes high reaction force and high pulse frequency; low tuning factor makes low reaction force and low pulse frequency. Reaction Force Tuning Factor must range from 0 through 100 %. By default, it is set to 40%.

In the trace, the angle reversal means that the tool rotates backward to enable pulsing, but the bolt head does not necessarily rotate backward because of the PulseDrive socket/adapter.

# TrR – Loosen to Trigger Release

Tools
ES STR SL ST SR STB IXB

This step is not supported for tools configured with Gear Front Attachment (GFA) of type open end.

This step runs in the backward direction until the tool trigger is released (loosen). It can only be used as a last step in a program.

For STB tools, this step is only applicable for loosening programs.

Parameter | Description
--- | ---
Speed | Numerical value for rotation speed; in rpm.
Speed Ramp Type | List of options where speed ramp can be chosen [Hard, Soft, Manual]

# TTTR – Tighten to Trigger Release

Tools
ES STR SL ST SR STB IXB

This step runs until the tool trigger is released (tighten). It can only be used as a last step in a tightening program.

Parameter | Description
--- | ---
Speed | Numerical value for rotation speed; in rpm.
Speed Ramp Type | List of options where speed ramp can be chosen [Hard, Soft, Manual]

# W – Wait

Tools
ES STR SL ST SR QST STB IXB

In this step the tool waits until the Wait Type condition is fulfilled. The tool does not rotate while waiting, but Hold condition can be specified.

Parameter | Description
--- | ---
Wait Type | Time: Wait specified time. Signal (valid only for Power Focus 6000 Synchronized tightening): Wait until a rising edge on the signal Continue Step is received.
Wait Time | Number of seconds the tool will stand still - valid only when Time is selected for Wait Type.
Hold Condition | No hold: The tool is waiting without running. Hold torque: While waiting the tool strives to hold the torque it had when entering the step. Hold position: While waiting the tool strives to hold the position it had when entering the step.

# WP - Wrench Production

Tools
STwrench

Strategy used for the quality test of the tightening performed with the STwrench.

Parameter | Description
--- | ---
Control Strategy | The Wrench Production step type can be configured with the following control strategies. Torque: This strategy guides the operator is reaching the desired target torque. Angle: This strategy guides the operator is reaching the desired target angle. Torque or Angle: This strategy guides the operator is reaching the desired target angle or desired target torque. Torque and Angle: This strategy guides the operator in tightening a bolt until both target torque and angle have been reached. Yield Point: With this strategy, the STwrench detects the yield point automatically. The torque limits specify the range in which the result is OK. Target angle specifies how far beyond the yield point the user may tighten. Loose: This strategy is used to loosen a tightened screw. PVT compensate with snug: This strategy guides the operator in reaching the desired target torque for joints with prevailing torque, when the prevailing torque level is higher than the final target.

Based on the control strategy selected, a combination of some of the parameters listed below will be displayed.

Parameters | Description
--- | ---
Target Torque | Defines the target torque for tightening step.
Measure torque at | Specifies where the torque will be measured. Choose between Peak torque or Peak angle. Peak torque: The torque value will be set to the peak torque value. Peak Angle : The torque value will be set to the torque measured at the peak angle.
Angle search limit | This is an offset that is used to the set the torque result value for a tightening. Measure torque at must be set to Peak Angle for this parameter to be available.
Ratchet time | Numerical value for ratchet time which is by default 5000 ms. This allows the operator to release the torque for a while and recharge during the tightening operation. If the Ratchet time is exceeded the result of the tightening is marked as NOK with the reason "Tightening timeout".
End cycle time | Numerical value in ms to indicate the end cycle time. Applied when torque goes below the rundown complete
Torque correction coefficient | The parameter is used to correct the torque reading when using an extension or torque multiplier on the wrench. Default value is 1.
Angle correction | The parameter is used to correct the angle reading when using an extension or torque multiplier on the wrench. Default value is 0.
Target Angle | Defines the target angle for tightening step.
Rehit detection | On or Off. Rehit detection can be used to determine when a tightening is a rehit based on the angle limit setting. Angle limit for rehit is enabled if Rehit direction is set to On.
Linear slope coefficient | Linear slope coefficient characterizes the joint stiffness in the linear part of the curve, as torque/angle slope in the Nm/Deg measurement unit.
Compensate value | Choose between Average torque and Peak torque. The Compensate value specifies how the PVT will be calculated. Average torque - The PVT will be based on an average calculated using the following: Delay monitoring PVT interval PVT distance Prevailing torque min Prevailing torque max Peak torque - The PVT will be based on the peak value measured before snug was detected.
Torque Compensation | This parameter sets if the system compensates for the prevailing torque. If set to On, the system subtracts the prevailing torque from the peak torque before it reports the final torque. If set to Off, the system reports the peak torque as measured.
Delay monitoring | PVT calculation will not start before this window has been passed, starts at tightening start.
PVT interval | Sets how many degrees the PVT window shall be calculated for, start from the PVT distance point.
PVT distance | Sets how many degrees prior to snug the system shall start the PVT window.
Prevailing torque min | Prevailing torque minimum limit.
Prevailing torque max | Prevailing torque maximum limit

## Microvideo

WP - Wrench Production

# WQ - Wrench Quality

Tools
STwrench

Strategy used for the quality test of the tightening performed with the STwrench.

Parameter | Description
--- | ---
Control Strategy | The Wrench Quality strategy can be configured with the following control strategies. Residual Torque/Time: This strategy analyzes the torque trace as a function of time. The operator shall execute this operation with a single, steady, movement. The wrench automatically recognizes the breakaway and residual point. Residual Torque/Angle: This strategy evaluates the residual torque on a joint, looking for the residual point of the Torque/Angle trace. Residual Torque/Peak: This strategy evaluates the residual torque on a joint as the peak torque necessary to rotate the bolt further. Loose and Retighten: This strategy loosens a bolt and retightens it back to its original position Yield Point: With this strategy the wrench detects the yield point automatically. Target Angle specifies how far beyond the yield point the user may tighten.

Based on the control strategy selected, a combination of some of the parameters listed below will be displayed.

Parameters | Description
--- | ---
Ratchet time | Numerical value for ratchet time which is by default 5000 ms. This allows the operator to release the torque for a while and recharge during the tightening operation. If the Ratchet time is exceeded the result of the tightening is marked as NOK with the reason "Tightening timeout".
Torque correction coefficient | The parameter is used to correct the torque reading when using an extension or torque multiplier on the wrench. Default value is 1.
Angle correction | The parameter is used to correct the angle reading when using an extension or torque multiplier on the wrench. Default value is 0.
Target Angle | Defines the target angle for tightening step.
Rehit detection | On or Off. Rehit detection can be used to determine when a tightening is a rehit based on the angle limit setting. Angle limit for rehit is enabled if Rehit direction is set to On.
Linear slope coefficient | Linear slope coefficient characterizes the joint stiffness in the linear part of the curve, as torque/angle slope in the Nm/Deg measurement unit.

# Y – Tighten to Yield

Tools
ES STR SL ST SR QST IXB

This strategy runs the tool with the speed in the forward direction until the yield point is detected. The yield point is found by monitoring the torque gradient from the point where the torque goes above the Trigger Torque level, calculated based on Torque and Angle distance measurements. The Angle distance parameter is set according to the specified hardness of the joint.

Set the Gradient angle window (for hard joint, for soft joint or for manually setting of the Angle window). If Manual is selected, the Angle Window must be set. A joint is considered Hard if the screw is tightened to its full torque and it rotates 30 degrees or less after it has been tightened to its snug point. A Soft joint rotates 720 degrees or more after it has been tightened to its snug point. The hardness parameter defines the Angle Window for the gradient calculation. The harder the joint - the smaller the angle window.

Parameter | Description
--- | ---
Gradient Angle Window | Specifies Angle Window: For Hard Joint: Angle Window = 1 deg. For Soft Joint: Angle Window = 20 deg. Manual: Manually set Angle Window.
Angle Window | Available when Gradient Angle Window is set to Manual. Must be > 0 and <= 100.
Trigger Torque | The angle measurement starts at this trigger. Must be >= 0 and < Tool MaxTorque.
Damping | Frequency in which the gradient is being calculated. Must be > 0 and < 100 and < Angle window.
Yield Point Percentage | Must be >= 20 %
Speed | Default: 60 rpm. Must be > 0.
Speed ramp type | Hard, soft, or manual. Default: Hard. If you select Manual, the Speed ramp field opens.
Torque Filter Type | The type of the filter: None: No filtering of the torque is used. The raw values are used as-is in the gradient calculation. Five-point: The torque value used in the calculation are filtered using a sliding average filter over 5 torque samples. Low pass: The torque values is filtered with a simple discrete Infinite Impulse Response filter. Sliding Average: The torque values used in the calculation are filtered using a sliding average filter over a Number of Samples specified by the use.
Cut-off Frequency | Needs to be specified when Torque Filter Type is set to Low pass: 20 Hz 40 Hz 90 Hz 200 Hz 600 Hz
Number of Samples | Needs to be specified when Torque Filter Type is set to Sliding Average: 2 4 6 8 16 32
Brake (Valid only for Power Focus 6000 Synchronized tightening, Power Focus 8 Synchronized tightening and Flex). | If On the tool will be stopped when the target is reached. If Off the program goes directly to the next step without stopping the tool.

Point and click on image to see more information:

A | Peak Gradient
B | Yield Point
C | Shut-off Point
D | Angle Distance
E | Torque Trigger

# YM2 - Tighten to Yield: Method 2

Tools
QST

This step runs the tool with the specified speed in the forward direction until the yield point is detected.

Search for the yield point starts when the torque has reached Tt. The average of the torque over Af degrees is calculated. This procedure is repeated N rs times.

A reference slope is calculated with linear regression over the N rs points. After that, new average values are continuously calculated over A f degrees.

The actual slope is calculated with linear regression over the last N s average points. The yield point is reached when the slope is less than Py % of the reference slope.

Parameter | Description
--- | ---
Target torque | Must be > 0.
Filter angle | Default: 1. Must be > 0.
Number of samples | Default: 6. Must be >=4.
Number pf samples, reference | Default: 6. Must be >=4.
Yield point percentage | Default: 90%. Must be >20%.
Speed | Default: 60 rpm. Must be > 0.
Speed ramp type | Hard, soft, or manual. Default: Hard. If you select Manual, the Speed ramp field opens.
Speed ramp | If Speed ramp type is Manual, this field opens. Default: 500 rpm/s.
Brake (Valid only for Power Focus 6000 Synchronized tightening, Power Focus 8 Synchronized tightening and Flex). | If On the tool will be stopped when the target is reached. If Off the program goes directly to the next step without stopping the tool.

Point and click on image to see more information:

A | Torque Trigger
B | Number of samples, ref
C | Actual Slope
D | Number of samples
E | Reference Slope
F | Filter Angle

# ZP - Loosen to Zero Position

Tools
ES STR SL ST SR QST

This step runs the tool with the speed (N) in the backward direction until it reaches the zero position. If the total angle to rotate to reach the zero position is less than the minimum angle (Am) degree the rotation will continue for one more revolution, 360 degrees.

The zero position is a specific position stored with either a “Set Zero Position” step or the signal “Set Zero Position”. The position is repeated once every 360 degrees.

Parameters

Parameter | Description
--- | ---
Minimum Angle | Minimum Angle (Am) [°]
Speed | Rotation speed (N) [rpm]. Default value 60 rpm.

# ZP - Tighten to Zero Position

Tools
ES STR SL ST SR QST

This step runs the tool with the speed (N) in the forward direction until it reaches the zero position. If the total angle to rotate to reach the zero position is less than the minimum angle (Am) degree the rotation will continue for one more revolution, 360 degrees.

The zero position is a specific position stored with either a “Set Zero Position” step or the signal “Set Zero Position”. The position is repeated once every 360 degrees.

Parameters

Parameter | Description
--- | ---
Minimum Angle | Minimum Angle (Am) [°]
Speed | Rotation speed (N) [rpm]. Default value 60 rpm

# Step Monitors

The availability of tightening steps, monitors and restrictions depends on the license installed on the controller.

The step monitors are used to verify that the tightening was achieved according to the specification, for example, angle limits or torque. Each step has mandatory step monitors and optional step monitors. The mandatory monitors are included when dragging a new step to the multistep program. The optional monitors are flexible and can be placed as needed in the multistep program. Every step can have up to eight monitors each.

The following monitors are automatically added to every step that is added to the multistep tightening program.

Default step monitors
Step Monitor | Applicable steps
--- | ---
Angle | All
Peak Torque | All

Available tools for each system type
Power Focus 6000 / Power Focus 8 | Power Focus 6000 Synchronized tightening / Power Focus 8 Synchronized tightening | Flex | IxB
--- | --- | --- | ---
ST | ST | QST | IxB
STR | STR |  |
SL | QST |  |
QST |  |  |
STB |  |  |
IxB |  |  |
Power Focus Connect |  |  |
XB |  |  |

Step Monitors
Tools
Search

# A - Angle

Tools
ES STR SL ST SR QST STB IXB MWR-TA

This step monitor measures the maximum angle reached during the monitor and checks that it is between High limit and Low limit.

The angle measurement starts at the start of the monitor or, if specified, at the point where the torque passes Trigger torque for the first time during the monitor.

Parameter | Description | Default value
--- | --- | ---
Stop condition | It specifies where the angle measurement ends: End End point used: the angle at the end of the monitor. Peak Torque End point used: the angle at the point where the highest torque is reached during the monitor. Shut Off End point used: the angle at the shut off point of the step. Peak End point used: the highest angle reached during the monitor. | Shut Off
Trigger torque | The angle measurement starts at this trigger. Minimum limit: must be >= 0 Maximum limit: must be < Tool Max Torque | Not set
Low Limit | Lowest acceptable angle. Minimum limit: must be >= 0 Maximum limit: must be < 9 999 999 and < High Limit | Not set
High Limit | Highest acceptable angle. Minimum limit: Must be > 0 and > Low Limit Maximum limit: must be < 9 999 999 | Not set

## Result Values

- Angle Measured: the angle measured by the monitor.

Point and click on image to see more information:
Step Monitor Angle - Stop condition End

A | Shut-off point | D | Angle high limit
B | Torque trigger | E | Measured angle
C | Angle low limit | F | Step

Point and click on image to see more information:
Step Monitor Angle - Stop condition Peak Torque

A | Peak torque | E | Angle high limit
B | Shut-off point | F | Measured angle
C | Torque trigger | G | Step
D | Angle low limit |  |

Point and click on image to see more information:
Step Monitor Angle, Stop condition Shut Off

A | Shut-off point | D | Angle high limit
B | Torque trigger | E | Measured angle
C | Angle low limit | F | Step

Point and click on image to see more information:
Step Monitor Angle - without Torque Trigger and with stop condition Peak

A | Shut-off point | D | Measured angle
B | Angle low limit | E | Step n-1
C | Angle high limit | F | Step n

# AZP - Adjust to Zero Position

Tools
QST

This monitor is used to return to the true Zero Crossing position, measured in the Zero Crossing monitor earlier in the program. Backlash angle is used if measured earlier in the program

Parameter | Description
--- | ---
Low Speed | Speed used when Slowdown Distance is reached. Must be < Speed and > 0.
ZeroPosition Adjustment | Target position from Zero Crossing value. Must be > -9,999,000 and < 9,999,999.
Slowdown Distance | Degrees before target in which the Low Speed will be used. Must be >= 0 and < 9,999,999.
Speed | Default: 60 rpm. Must be < Tool max speed.
Speed Ramp Type | Hard, Soft or Manual. Default: Hard. If you select Manual, the Speed Ramp field opens.

# BA - Backlash Angle

Tools
QST

This monitor monitors the backlash angle of the socket. Used with the Backlash Angle Measurement step.

Parameter | Description
--- | ---
High Limit | Maximum angle limit. Must be < 9,999,999.

# BM - Backlash Angle Measurement

Tools
QST

This monitor measures the backlash in the socket. The resulting angle is used in calculations in the Adjust to Zero Position monitor.

Parameter | Description
--- | ---
Direction | The direction in which the measurement ends.
Target Torque | The torque target. Must be >= 0.
Speed | Default: 60 rpm. Must be >= 0.
Speed Ramp Type | Hard, Soft or Manual. Default: Hard. If you select Manual, the Speed Ramp field opens.

# C - Current

Tools
ES STR SL ST SR QST STB IXB

This monitor measures the actual current at any point after the torque passes Torque Trigger. The result will be the first peak or low value, that made the monitor NOK. In case of OK, the result will be the last measured current value. If the torque trigger is never reached during the monitor it will end with NOK status and no measurement value.

Parameter | Description
--- | ---
Torque Trigger | Must be >= 0 and < Tool Max Torque.
Low limit | Lowest acceptable current.
High limit | Highest acceptable current.

# Cl - Click

Tools
MWR-T MWR-TA

This step monitor is not available for IxB tools.

Monitor to enable click torque and click angle results. This monitor has no settings, and can only be used with the MWR step.

# LD - Loosening Detection

Tools
STwrench

This step monitor is only available for STwrench tools

This monitor can be used to check the torque and direction to see if a loosening is attempted when using the Wrench Production step strategy for an STwrench. If the applied torque is above the value set for Loosening Limit in the direction opposite to the configured thread direction of the program, the result shall be reported as NOK.

# MT - Mean Torque

Tools
ES STR SL ST SR QST IXB

This monitor measures the average torque during the monitor and checks the calculated value is within the limits.

Parameter | Description
--- | ---
Type | Specifies start condition: Step Start: The measurement starts from step start and ends at the shut-off point. Torque Trigger: The measurement starts at the point where the torque passes Torque Trigger for the first time. It ends at the shut-off point. Angle Trigger: The measurement starts at the point where the angle is Angle Trigger, measured from the optional Trigger Torque, is reached. Without Trigger Torque, the Angle Trigger is measured from the start of the step. It ends at the shut-off point Angle Window: Measures during an Angle Window. The window starts at the point where the torque passes Trigger Torque for the first time plus an angle offset, Angle Trigger. Time Interval: Measures during the last Time Interval seconds of the tightening.
Torque Trigger | Available when Type is set to Trigger Torque, Angle Trigger or Angle Window. Must be >= 0 and < Tool Max Torque.
Angle Trigger | Available when Type is set to Angle Trigger or Angle Window. Must be > 0.
Angle Window | Available when Type is set to Angle Window. Must be > 0.
Time Interval | Available when Type is set to Time Interval. Must be > 0.
Low Limit | Lowest acceptable torque.
High Limit | Highest acceptable torque.

# PC - Pulse Count

Tools
STR

This step monitor is only available for the following tools:

- ETV-STR61-100-13

- ETV-STR61-70-13

- ETV-STR61-50-10

Before using the Pulse Count step monitor, the Low Reaction Strategies license must be installed on the controller.

This monitor measures the number of pulses and confirms if it is between the pulse count low limit and pulse count high limit.
If the torque trigger level is set, the check starts as soon as the measured torque is above the torque trigger level.

If running a tightening step with Pulse Count step monitor, use the necessary PulseDrive socket/adapter.
If the tightening step runs without the PulseDrive socket/adapter, all the tightenings are NOK. The step error “PulseDrive socket/adapter not detected” shows for no PulseDrive socket/adapter.

Parameter | Description
--- | ---
Pulse Count High Limit - n+ | The Pulse Count limits are used to determine if the measured number of pulses is OK or NOK. The measured number of pulses is OK if it is between the pulse count low limit and pulse count high limit. The measured number of pulses is NOK if: It is higher than the pulse count high limit. It is lower than the pulse count low limit. The trigger torque level is not reached. Pulse count high limit must range from 1 through 9999999. It must be greater than or equal to the pulse count low limit. Pulse Count High Limit text box can be empty.
Pulse Count Low Limit - n- | The Pulse Count limits are used to determine if the measured number of pulses is OK or NOK. The measured number of pulses is OK if it is between the pulse count low limit and pulse count high limit. The measured number of pulses is NOK if: It is higher than the pulse count high limit. It is lower than the pulse count low limit. The trigger torque level is not reached. Pulse Count Low Limit must range from 1 through 9999999. It must be lower than or equal to the Pulse Count High Limit. Pulse Count Low Limit text box can be empty.
Torque Trigger - Tt | Torque Trigger must range from 0 through the maximum torque of the tool. Torque Trigger text box can be empty.

# PrT - Prevailing Torque

Tools
ES STR SL ST SR QST STB IXB

The monitor calculates the prevailing torque value in the Window Length and checks that it is between the Torque limits. The Angle Window starts at the angle degrees set in Start Angle in reverse direction from the shut-off point. This then spans for the angle degrees set in Angle Window Length in reverse direction. If Start Angle is left blank the angle window starts at the shut-off point. The calculated prevailing torque value is the mean or peak torque value (depending on the parameter set by the user) during the Window Length. The calculated value is saved as result data Prevailing Torque Measured. If Torque compensation is set to On, the Prevailing Torque Measured will be subtracted from all torque result values in consecutive steps. Any previously calculated prevailing torque compensation values will no longer be subtracted from torque result values. If Torque compensation is set to Off, no subtraction will be made in consecutive steps.

If the total angle of the step is less than the Start Angle plus Window Length, then the monitor will report NOK.

Prevailing torque can be measured as an average of measured values, or at peak torque. To choose between these two modes, set the Use Value parameter to either Mean torque (for average values), or Peak torque (for peak value).

Parameter | Description
--- | ---
Torque Compensation | On or off.
Start Angle | Must be > 0
Window length | Must be >= 0
Low Limit | Must be > 0
High Limit | Must be >= 0
Use value | Mean torque (for average values), or Peak torque (for peak value).

# PT - Peak Torque

Tools
ES STR SL ST SR QST STB IXB MWR-TA MWR-T

This step monitor measures the maximum torque reached during the monitor, including any over shoot, and checks that it is between High limit and Low limit.

Parameter | Description
--- | ---
Low Limit | Lowest acceptable torque.
High Limit | Highest acceptable torque.

# PTCA - Post Thread Cut Angle

Tools
ES STR SL ST SR QST STB IXB

This step monitor measures the maximum angle reached during the monitor and checks that it is between High limit and Low limit.

The Trigger Torque level is ignored until the end of the Thread cut angle window is reached. After that, the angle measuring starts as soon as the measured torque is above Trigger Torque.

Parameter | Description | Default value
--- | --- | ---
Stop condition | It specifies where the angle measurement ends: End End point used: the angle at the end of the monitor. Peak Torque End point used: the angle at the point where the highest torque was reached during the monitor. Shut Off End point used: the angle at the shut off point of the step. Peak End point used: the highest angle reached during the monitor. | Shut Off
Trigger torque | The angle measurement starts at this trigger. Minimum limit: must be >= 0 Maximum limit: must be < Tool Max Torque | 0
Low Limit | Lowest acceptable angle. Minimum limit: must be >= 0 Maximum limit: must be < 9 999 999 and < High Limit | Not set
High Limit | Highest acceptable angle. Minimum limit: Must be > 0 and > Low Limit Maximum limit: must be < 9 999 999 | Not set
Thread cut trigger torque | Minimum limit: must be >= 0 Maximum limit: must be < Tool Max Torque | Not set
Thread cut angle window | Minimum limit: must be >= 0 Maximum limit: must be < 9 999 999 | 0

## Result Values

- Angle Measured: the angle measured by the monitor.

Point and click on image to see more information:
Step Monitor - Post Thread Cut Angle

A | Shut-off point | E | Angle low limit
B | Torque trigger | F | Angle high limit
C | Torque trigger thread cut | G | Measured angle
D | Thread cut angle window |  |

# PTCPT - Post Thread Cut Peak Torque

Tools
ES STR SL ST SR QST STB IXB

Measures the maximum torque achieved during the monitoring, including any over-shoot, and checks that it is between the Torque limits. All torque values are ignored until the end of the Thread cut angle window has been reached.

Parameter | Description
--- | ---
Thread cut trigger torque | Must be >= 0
Thread cutting angle window | Must be > 0
Low Limit | Must be >= 0
High Limit | Must be > 0 Must be > Low limit

# PVTH - Post View Torque High

Tools
ES STR SL ST SR QST STB IXB

This monitor checks that all torque values in the Angle Window Length are below the High limit.

The Angle Window starts at the angle degrees set in Start Angle in reverse direction from the shut-off point. This then spans for the angle degrees set in Angle Window Length in reverse direction. If Start Angle is left blank, the Angle Window starts at the shut-off point. The torque values used in the monitor are based on the mean torque value, calculated over Number of Samples. If the total angle of the step is less than Start Angle plus Angle Window Length the monitor will report NOK.

Parameter | Description
--- | ---
Start Angle | Must be >= 0
Window length | Must be > 0
Number of samples | Minimum value =1 Maximum value = 80
High Limit | Highest acceptable torque.

# PVTL - Post View Torque Low

Tools
ES STR SL ST SR QST STB IXB

Same as monitor Post View Torque High, but this monitor checks that all torque values in the Angle Window Length are above Low Limit instead.

Parameter | Description
--- | ---
Start Angle | Must be >= 0
Window length | Must be > 0
Number of samples | Minimum value =1 Maximum value = 80
Low Limit | Lowest acceptable torque.

# SOC - Shut Off Current

Tools
ES STR SL ST SR QST STB IXB

The shut off point is the point where the step reaches its target. The current is measured at the shut off point and checked to be between High limit and Low limit .

Parameter | Description
--- | ---
Low Limit | Lowest acceptable current.
High Limit | Highest acceptable current.

# SOT - Shut Off Torque

Tools
ES STR SL ST SR QST STB IXB

The shut off point is the point where the step reaches its target. The torque is measured at the shut off point and checked to be between High limit and Low limit.

Parameter | Description
--- | ---
Low Limit | Lowest acceptable torque.
High Limit | Highest acceptable torque.

# SSD - Stick Slip Detection

Tools
ES STR SL ST SR QST IXB

This step monitor detects and reports stick slip effects during a step. The detection is done by counting the number of times the torque falls below the Trigger Level. If the number of times is larger than Maximum Number of Oscillations then the stick slip error is reported. The monitor operates in two different modes, Dynamic or Fixed. The difference between the modes is the way that the Trigger level is calculated.

Dynamic Torque: Trigger Level is dynamically calculated as Peak Torque Percentage of the current max torque, which has been achieved so far during the monitoring. The monitoring is started as soon as the torque passes the Trigger Torque.

Fixed Torque: Trigger Level is the fixed Trigger Torque specified by the user. In this mode the percentage is not needed.

If the torque never reaches the Trigger Torque then the monitoring is not started, this will result in status NOK.

Parameter | Description
--- | ---
Type | Specifies what type of Stick slip detection that will be done in the monitor Stick Slip detection. Default: Dynamic torque.
Peak Torque Percentage | Default: 80%, Must be >=10 and < 100.
Trigger Torque | Default: 5, Must be >= 0 and < Tool max torque.
Maximum Number of Oscillations | Default: 5, Must be >= 3 and <20.

# TAW - Torque in Angle Window

Tools
ES STR SL ST SR QST STB IXB

This monitor checks that all torque values in the angle window are within the torque limits.

Parameter | Description
--- | ---
Trigger Torque | Must be >= 0
Start Angle | Must be > 0
Window Length | Must be <= 0
Low Limit | Must be >= 0
High Limit | Must be > 0 Must be > Low limit
NOK if window is passed | If set to Yes, status of this monitor is NOK if the end of angle window is not reached.

# TC - Torque Calibration

Tools
QST

This step monitor is only available for tools equipped with multiple transducers.

The Torque Calibration monitor checks if the maximum torque reached is within the torque limits.

Parameter | Description
--- | ---
Transducer type | Torque or Torque 2 Set to Torque 2 for the front transducer of the tool.
Low limit | Must be >= 0
High limit | Must be > 0 Must be > Low limit

# TG - Torque Gradient

Tools
ES STR SL ST SR QST IXB

This monitor checks that the gradient is within the limit.

Parameter | Description
--- | ---
Gradient Angle Window | Specifies Angle Window: For Hard Joint: Angle Window = 1 deg. For Soft Joint: Angle Window = 20 deg. Manual: Manually set Angle Window.
Angle Window | Available when Gradient Angle Window is set to Manual. Must be > 0 and <= 100.
End Point Check | If set to Yes, only the gradient measured at the shut off point of the step is checked to be within the limits.
Trigger Torque | The angle measurement starts at this trigger. Must be > 0 and < Tool MaxTorque.
Damping | Frequency in which the gradient is being calculated. Must be > 0 and < 100 and < Angle window.
Low Limit | Lowest acceptable torque gradient. Must be >= -100.
High Limit | Highest acceptable torque gradient. Must be > -100 and > Low limit.
Torque Filter Type | The type of the filter: None: No filtering of the torque is used. The raw values are used as-is in the gradient calculation. Five-point: The torque value used in the calculation are filtered using a sliding average filter over 5 torque samples. Low pass: The torque values is filtered with a simple discrete Infinite Impulse Response filter. Sliding Average: The torque values used in the calculation are filtered using a sliding average filter over a Number of Samples specified by the use.
Cut-off Frequency | Needs to be specified when Torque Filter Type is set to Low pass: 20 Hz 40 Hz 90 Hz 200 Hz 600 Hz
Number of Samples | Needs to be specified when Torque Filter Type is set to Sliding Average: 2 4 6 8 16 32
Angle Offset | Available when End Point Check is set to No. Specifies the degrees that the calculation of the gradient start after the trigger torque is passed for the first time.

# Ti - Time

Tools
ES STR SL ST SR QST STB IXB

Measures the elapsed time during the monitor and checks that it is between the time limits. The time measurement starts at the start of the monitor and, if the Trigger Torque is specified, at the point where the torque passes Trigger Torque for the first time during the monitor.

Parameter | Description
--- | ---
Trigger Torque | Must be >= 0 and < Tool max torque.
Low Limit | Must be >= 0
High Limit | Must be > 0 Must be > Low limit

# TRD - Torque Rate and Deviation

Tools
ES STR SL ST SR QST IXB

This step monitor measures and checks the torque rate, i.e. the ratio of torque vs. angle. The calculated torque rate is checked if it is within the torque rate limits defined by High Limit and Low Limit.

Parameter | Description
--- | ---
Trigger Torque | Torque of the angle start point.
Start Point Angle | When Start point angle has been measured from Trigger torque the measuring of the torque starts.
End Point Angle | Angle point where the measuring of the torque is stopped.
End Point Torque | Torque where the measuring of the torque is stopped.
Low Limit | Lowest acceptable torque.
High Limit | Highest acceptable torque.
Limit | Must be > 0

# YA - Angle from Yield

Tools
ES STR SL ST SR QST IXB

This monitor measures the peak angle reached from the yield point and checks that the peak angle is within the limit.

Parameter | Description
--- | ---
Gradient Angle Window | Specifies Angle Window: For Hard Joint: Angle Window = 1 deg. For Soft Joint: Angle Window = 20 deg. Manual: Manually set Angle Window.
Angle Window | Available when Gradient Angle Window is set to Manual. Must be > 0 and <= 100.
Yield Point Percentage | Must be >= 20 %
Trigger Torque | The angle measurement starts at this trigger. Must be > 0 and < Tool MaxTorque.
Damping | Frequency in which the gradient is being calculated. Must be > 0 and < 100 and < Angle window.
Low Limit | Lowest acceptable angle. Must be >= 0
High Limit | Highest acceptable angle. Must be > 0
Torque Filter Type | The type of the filter: None: No filtering of the torque is used. The raw values are used as-is in the gradient calculation. Five-point: The torque value used in the calculation are filtered using a sliding average filter over 5 torque samples. Low pass: The torque values is filtered with a simple discrete Infinite Impulse Response filter. Sliding Average: The torque values used in the calculation are filtered using a sliding average filter over a Number of Samples specified by the use.
Cut-off Frequency | Needs to be specified when Torque Filter Type is set to Low pass: 20 Hz 40 Hz 90 Hz 200 Hz 600 Hz
Number of Samples | Needs to be specified when Torque Filter Type is set to Sliding Average: 2 4 6 8 16 32

# ZC - Zero Crossing

Tools
QST

This monitor calculates the true start of a spring compression.

Parameter | Description
--- | ---
Trigger Torque | Torque value from where the monitor starts. Must be < End Point Torque.
End Point Torque | Torque value for stop measuring. Must be > Trigger Torque.
Start Point Angle | Angle value from where the monitor starts. Must be < End point angle.
End Point Angle | Angle value for stop measuring. Must be > Start point angle.
Torque Rate Limit High | Maximum torque rate. Must be > Torque Rate Limit Low and < 999.
Torque Rate Limit Low | Minimum torque rate. Must be < 999 and < Torque Rate Limit High.

# Step Restrictions

The availability of tightening steps, monitors and restrictions depends on the license installed on the controller.

To make sure the tightening stops if something unexpected happens, it is possible to add step restrictions to the multistep tightening program. These restrictions could, for example, test that a maximum torque is not reached or that a part of the multistep tightening does not take too long to run. Each step has its own set of mandatory step restrictions and optional step restrictions. The mandatory restrictions are included when dragging a new step to the multistep program. All steps can have up to four restrictions each.

For synchronized tightening in Power Focus 6000 and Power Focus 8, it is possible to use synchronization points in the tightening program. When any condition that is set for a restriction is met, the tool will be stopped immediately and the program jumps to the next synchronization point (only valid when using synchronized tightening in Power Focus 6000, Power Focus 8, and Flex), or the end of the program. In controllers without synchronized tightening the tool is stopped immediately and the program jumps to the end of the program.

For Flex only:

For each restriction, select Repairable = Yes to allow retry when tightening stops.

The following restrictions are automatically added to every step that is added to the multistep tightening program.

Default step restrictions
Step Restriction | Applicable steps
--- | ---
Maximum Time | All except External Result and MWR
Maximum Torque | Tighten to Angle Tighten to Torque+Angle Turbo Loosening Wait Socket release Run until Digital Input Tighten to Trigger Release TensorPulse Impulse
Maximum Angle | Tighten to Torque TurboTight Turbo Loosening Tighten to DynaTork Wait Run until Digital Input Loosen to Torque Thread Cutting to Torque Rundown Tighten to Yield Pulsing Rundown Snug TensorPulse

Available tools for each system type
Power Focus 6000 / Power Focus 8 | Power Focus 6000 Synchronized tightening / Power Focus 8 Synchronized tightening | Flex | IxB
--- | --- | --- | ---
ST | ST | QST | IxB
STR | STR |  |
SL | QST |  |
QST |  |  |
STB |  |  |
IxB |  |  |
Power Focus Connect |  |  |
XB |  |  |

Step Restrictions
Tools
Search

# A - Maximum Angle

Tools
ES STR SL ST SR QST STB IXB

This restriction measures the angle. If the measured angle reaches the Maximum Limit, the tool is stopped immediately. The angle is measured from the start of the restriction or, if specified, from the point where the torque passes Trigger Torque for the first time during the restriction.

Parameter | Description
--- | ---
Trigger Torque | If specified, this is the torque from where the angle is measured.
Maximum Limit | If this limit is reached the tool is stopped immediately.

# C - Current

Tools
ES STR SL ST SR QST STB IXB

This step restriction is not supported for Power Focus XC.

This restriction checks the actual current where torque passes Torque Trigger. If the actual current exceeds the limits, the tool will be stopped immediately and the tightening program will jump to the next synchronization point or the end of the program. The result will be the first peak or low value, that made the monitor NOK. In case of OK, the result will be the last measured current value. If the torque trigger is never reached during the restriction it will end with status OK.

Parameter | Description
--- | ---
Torque Trigger | Must be >= 0 and < Tool Max Torque.
Low limit | Lowest acceptable current.
High limit | Highest acceptable current.

# CTh - Cross Thread

Tools
ES STR SL ST SR QST STB IXB

This restriction checks the angle from the point where torque passes Start torque (T1) to the point where the torque passes End torque (T2). If the angle measured from Start torque (T1) is higher than Maximum limit (Amax), the tool is stopped immediately.

When the torque passes End torque (T2), the measured angle is checked against the limit Minimum limit (Amin). If the angle is lower than this limit, the tool is stopped immediately.

Parameter | Description | In illustration
--- | --- | ---
Start Torque | Must be <=0. | T1
End Torque | Must be <=0. | T2
Minimum Limit | The low angle limit. | Amin
Maximum Limit | The high angle limit. | Amax

# PCH - Pulse Count High

Tools
STR IXB

This restriction is only available for the following tools:

- ETV-STR61-100-13

- ETV-STR61-70-13

- ETV-STR61-50-10

- ITB-P

Before using the Pulse Count restriction, the Low Reaction Strategies license must be installed on the controller.

This restriction gives a limit to the number of pulses, and makes sure that those are below the specified pulse count high limit.
If the measured number of pulses is higher than the pulse count high limit, the tool is stopped immediately and the program goes to the next synchronization point or the end of the program.
If the torque trigger level is set, the check starts as soon as the measured torque is above the torque trigger level.

If running a tightening step with Pulse Count High step restriction, use the necessary PulseDrive socket/adapter.
If the tightening step runs without the PulseDrive socket/adapter, all the tightenings are NOK. The step error “PulseDrive socket/adapter not detected” shows for no PulseDrive socket/adapter.

Parameter | Description
--- | ---
Pulse Count High Limit - n+ | Pulse count high limit must range from 1 through 9999999. Pulse Count High Limit text box can be empty.
Torque Trigger - Tt | Torque Trigger must range from 0 through the maximum torque of the tool. Torque Trigger text box can be empty.

# Rh - Rehit

Tools
ES STR SL ST SR QST STB IXB

This restriction checks the torque. If the measured torque exceeds the Detection Torque, the tool is stopped immediately and the program jumps to the next synchronization point (for Power Focus 6000 Synchronized tightening and Power Focus 8 Synchronized tightening), or the end of the program.

It is only possible to add step Rehit restriction to the first step of the multistep tightening program. Once the Rehit restriction has been added to the first step it shall not be possible to move the step to any other position within the tightening program. The Rehit restriction has to be deleted from the first step in order to move it to other position in the tightening program.

Parameter | Description
--- | ---
Detection Torque | If the measured torque exceeds the Detection Torque, the tool is stopped immediately and the program jumps to the next synchronization point (for Power Focus 6000 Synchronized tightening and Power Focus 8 Synchronized tightening), or the end of the program. Must be greater than zero.
Angle Window | The angle window is measured from the start of the step. If no Angle Window is set, the restriction is active during the whole step.

# RT - Rescinding Torque

Tools
ES STR SL ST SR QST STB IXB

This restriction checks the torque. If the measured torque drops below the condition of the restriction the tool is stopped immediately and the program jumps to the next synchronization point (for Power Focus 6000 Synchronized Tightening and Power Focus 8 Synchronized Tightening), or the end of the program.

- Torque control processes
  The restriction condition is the measured torque. For the restriction to be active the torque must first exceed 110 % of the Rescinding Torque Limit.

- Angle control processes
  This restriction checks the maximum torque reached during the restriction. For the restriction to be active the torque must first exceed the Trigger Torque.

Torque control processes
Parameter | Description
--- | ---
Rescinding torque limit | Default: 10 Nm. Must be > 0.

Angle control processes (valid only for Power Focus 6000 Synchronized tightening and Power Focus 8 Synchronized tightening)
Parameter | Description
--- | ---
Trigger Torque | Must be > 0.
Peak torque percentage | Default: 95. Must be >= 50.
Rescinding torque time | Default: 20. Must be >= 5 and <= 500.
Rescinding Torque Angle | Must be > 0.

Cable tools have the option to select Rescinding Torque for Angle. This restriction is controlled by two parameters: Peak Torque Percentage and Rescending Torque Time. Percentage sets the downward deviation from the last peak torque, and Rescending Torque Time sets the duration (between 5 and 500 ms) of that deviation. Only when both conditions (equal to or lower than the indicated percentage for the set duration) are met, will the program be interrupted and jump to the end.

# T - Maximum Torque

Tools
ES STR SL ST SR QST STB IXB

This restriction checks the torque. If the measured torque exceeds the Maximum limit, the tool is stopped immediately.

Parameter | Description
--- | ---
Maximum Limit | If the torque reaches this specified limit the tool is stopped immediately.

# TAW - Torque in Angle Window

Tools
ES STR SL ST SR QST STB IXB

This restriction checks that the measured torque in the Angle Window Length is between the Torque limits. If the measured torque is outside the limits the tool is stopped immediately and the program jumps to the end. The Angle Window Length starts at the Start Angle from the point that the torque first passed the Trigger Torque. If Trigger Torque is not set, then the Start Angle begins at the start of the restriction.

If the end of the Angle Window Length is not reached, the status of the restriction is NOK.

Parameter | Description
--- | ---
Trigger Torque | Must be >= 0
Start Angle | Must be >= 0
Window Length | Must be >0
Minimum Limit | Must be >= 0
Maximum Limit | Must be <= Minimum limit

# TCD - Torque vs Current Deviation

Tools
ES STR SL ST SR QST IXB

This restriction verifies that all current measurements converted to the corresponding torque are, at most, the Maximum deviation away from the actual torque measured with the torque transducer. The restriction starts when the torque reaches Trigger Torque for the first time during the step and is active until the step reaches its target.

If Trigger Torque is never reached, the monitor will report OK.

Parameter | Description
--- | ---
Trigger Torque | Must be >= 0
Maximum Deviation | Default: 1, Must be > 0

# TG - Torque Gradient

Tools
ES STR SL ST SR QST IXB

This restriction checks the gradient and if it is outside the limits the tool is stopped immediately and the program jumps to the end of the program.

Parameter | Description
--- | ---
Gradient Angle Window | Specifies Angle Window: For Hard Joint: Angle Window = 1 deg. For Soft Joint: Angle Window = 20 deg. Manual: Manually set Angle Window.
Angle Window | Available when Gradient Angle Window is set to Manual. Must be > 0 and <= 100.
Trigger Torque | Must be > 0 and < Tool MaxTorque.
Damping | Frequency in which the gradient is being calculated. Must be > 0 and < 100 and < Angle window.
Minimum Limit | Must be >= -100.
Maximum Limit | Must be > -100 and > Low limit.
Torque Filter Type | The type of the filter: None: No filtering of the torque is used. The raw values are used as-is in the gradient calculation. Five-point: The torque value used in the calculation are filtered using a sliding average filter over 5 torque samples. Low pass: The torque values is filtered with a simple discrete Infinite Impulse Response filter. Sliding Average: The torque values used in the calculation are filtered using a sliding average filter over a Number of Samples specified by the use.
Cut-off Frequency | Needs to be specified when Torque Filter Type is set to Low pass: 20 Hz 40 Hz 90 Hz 200 Hz 600 Hz
Number of Samples | Needs to be specified when Torque Filter Type is set to Sliding Average: 2 4 6 8 16 32

# Ti - Maximum Time

Tools
ES STR SL ST SR QST STB IXB

This restriction checks the time. If Maximum Limit is reached, the tool is stopped immediately.

Parameter | Description
--- | ---
Maximum Limit | If this time is elapsed, the tool is stopped immediately.

# Deleting a Multistep Program

1. For each Multistep program to be deleted, mark the check box in the leftmost column in the workspace area.

2. Select the Manage command button, then Delete from the drop-down list.

3. The selected Multistep program(s) are removed and the list is updated.

# STB Tools and Multistep

Due to the wireless nature of STB tools, some multistep functions and behaviors may differ. Besides the general limitations listed here, descriptions of multistep functions will be additional information on STB tools where necessary.

## Program Validation

All tightening programs will be validated for compatibility with STB tools before the program is downloaded to the tool. If the chosen tightening program is not compatible with the tool, the tool will be locked. When this error occurs, it will trigger event 5030, "Configuration complexity exceeded".

To unlock the tool, reduce the complexity of the tightening program, or choose a different tightening program altogether.

# Result Reporters

The result reporters makes it possible to extract specific values of selected producer from the result. The result reporters belong to a step but has to be tied to the monitor/restriction which they read the values from. Only monitors or restrictions located in the same step as the result reporter can be selected. A result reporter is added to a step using drag and drop (in the same way as monitors and restrictions). Each result reporter is responsible for reporting a specific result value, for example, Rundown Angle, Final Torque, Prevailing Torque.

It is possible to tie a result reporter to:

- Program monitors

- Step monitors

- Step restrictions

Each result reporter defines a final value type:

- Final Angle

- Final Torque

- Prevailing Torque

- Self-tap Torque

- Current

- Rundown Angle

- Number of Pulses

## General Parameters

Parameter | Description
--- | ---
Producer | Specifies which monitor/restriction produces the value.
Value | Specifies which value to show from the selected producer.

Limitations:

- It is only possible to add a result reporter on a monitor/restriction belonging to a step in main path or a program monitor/program restriction.

- There may exist several reporters on a step if they are of different type.

- There may exist a result reporter of, for example, type final angle on every step and program monitor angle.

- For those monitor/restrictions that have more than one result value, it is possible to add more than one result reporter if the result reporters are of different types.

- There may not exist several result reporters of the same type on a step or on a program monitor/restriction.

- There is only one result reported for each possible final value type.

Rules:

- The internal number of a result item has to be the same as for the corresponding result reporter.

- The internal number of a monitor/restriction result has to be the same as the internal number of the monitor/restriction in the configuration.

- The step results has to be ordered according to the order of execution. The first executed step has to be first.

Possible values reported by a result reporter if present in the monitor/restriction/step:

- The monitors/restrictions measured value (as float or integer)

- The monitors/restrictions high and low limits

- Status

- Torque trigger and angle trigger

- Angle target and torque target (read from the step)

Possible values for status:

- Low

- OK

- High

- Other

- NotSet

The target values do not belong to any step monitor so the target values are taken from the step that the monitor belongs to.

# Multistep Template

All created templates are visible in the tab Templates, when creating a multistep program. A template can be inserted (drag-and-drop) and act as a base to build the new multistep program on.

A template can only be dragged into the multistep program when steps have not yet been added. After dragging the template to the multistep program, steps may then be added.

The template itself will not be affected when modifying a multistep tightening program since the template is copied, and not linked to the program.

Create multistep program templates in Library > Program templates.

Relevant Information

- Program Templates
- Pushing Configurations to a Controller

# Step Configuration Stages

The controller tightening programs need parameters to be set in order to execute the programs. Selecting a Strategy and either the Target torque or Target angle are mandatory. Other settings are optional. It is also possible to monitor the tightening as it progresses by adding limits within which the torque or angle rotation must remain.

The tightening procedure is divided into four stages: Start, Rundown, Tightening and Stop.

Typical tightening curve

The figure is typical of how tightenings are described. The curves represent how speed, torque and angle vary over time. All tightening strategies are represented in this way. Parameters, monitors and limits are also shown in detailed figures.

A task is defined from the time a trigger is pressed until the tightening target is reached, or an error occurs.

A combination of a tightening strategy together with specific parameter settings forms a tightening program.

The user can create many different tightening programs, and one of them is selected at runtime.

In this Section

- True Angle Compensation
- Current Monitoring
- Start Stage
- Rundown Stage
- Stop Stage
- Loosening a Screw
- Stage Parameter Descriptions

# True Angle Compensation

Certain tools can detect and measure the tool rotation during tightening. If the tool is rotated during tightening, the angle measurement may be corrupted. This may lead to a faulty tightening if the tool movement is too great. For variations within specified limits, the controller can compensate these rotations and make a correct tightening.

This is an additional Licensed Feature, available per Virtual Station.

If the tool rotation is outside specified limits during the tightening, the tightening is aborted and NOK is reported. Additional information reports Tool movement exceeded.

True angle compensation limits
Parameter | Description | Default
--- | --- | ---
Negative angle limit | Defines the maximum negative rotation of the tool. If the value is exceeded the tightening is terminated and an error is reported. This is expressed in a numeric angle value. | Enabled, value set to -30 degree
Positive angle limit | Defines the maximum positive rotation of the tool. If the value is exceeded the tightening is terminated and an error is reported. This is expressed in a numeric angle value. | Enabled, value set to +30 degree

STB tools do not have the capability to measure the tool movement. If the True angle compensation is set to On, the error message Invalid Tightening Program will be displayed together with the additional information Feature not supported by the tool.

# Current Monitoring

Current monitoring provides extra security to monitor the tightening torque and is a complement to the torque sensor within the tool.

At final target torque, the rotor current is measured and converted to a torque value. If the calculated torque is within 10% of the measured torque, the tightening is considered to be OK.

Current monitoring
Parameter | Description | Default
--- | --- | ---
Current monitoring | Switch with On - Off position Off: Current monitoring is disabled and the tool torque is measured by the torque sensor. On: the current is measured at final torque target and converted to a torque value. The calculated torque is compared to the measured torque. If the difference is within 10%, the tightening is considered to be ok. | Off

# Start Stage

The Start stage initiates the tightening, enables socket and thread finding.

Parameter name | Condition | Description
--- | --- | ---
Soft start |  | Enables setting of the tool’s speed, angle and maximum torque to facilitate the threading. Off: Soft start is turned off. On: Soft start is turned on.
Speed | Soft start = On | Defines the speed during Soft start.
Angle | Soft start = On | Defines the target angle to turn the spindle for the bolt to enter the thread.
Torque max | Soft start = On | Defines the upper torque limit during Soft start. If Torque max is exceeded, the tightening is aborted and an error message is shown. The tightening will be considered NOK.
Positive | True angle | Defines the maximum positive rotation of the tool. If the value is exceeded, the tightening is terminated and an error is reported. This is expressed in a numeric angle value.
Negative | True angle | Defines the maximum negative rotation of the tool. If the value is exceeded, the tightening is terminated and an error is reported. This is expressed in a numeric angle value.

# Rundown Stage

# Rundown Introduction

Rundown step is the part of the tightening from when the screw enters the thread until just before the screw head touches the underlying surface and snug is reached. The torque required during rundown does not contribute to any clamping force.

Function | Condition | Description
--- | --- | ---
Self tap | Optional | Is used for self-threading screws.
Rundown speed | Selectable |
Rundown torque limits | Optional | Monitors the torque and checks that values are within limits.
Rundown angle limits | Optional | Monitors the angle and checks that values are within limits. When this feature is enabled, the Time monitor is automatically enabled.
Post view torque | Optional | Used to monitor torque peaks. Can be switched On or Off.
Rundown complete torque | Mandatory | Final target value for rundown. When the torque is achieved, the program may move on to tightening.

# Rundown Selftap, Thread Cutting To Torque

The Selftap - Thread cutting to torque function enables tightening where the rundown torque required is greater than the Rundown complete torque, for example when tightening thin layers of metal using self-threading (or selftapping) screws. The selftap window starts when the torque value reaches SelftapTorqueMin/2. The torque must exceed SelftapTorqueMin, but not exceed Selftap-Torque-Max, during the angle window.

Rundown with a self tap screw

Parameter name | Description | Default value
--- | --- | ---
Selftap | Off: Selftap is turned off. On: Selftap is turned on. | Off
Length | Defines the angle to turn the socket during Self-tap. Measured from the end of the Start step. | 360°
Speed | Defines the speed during Selftap | 35 rpm
Torque min | Torque value for lower Selftap limit. | 0 Nm
Torque max | Torque value for upper Selftap limit. | Tool max torque

# Rundown Torque Limits

The friction between the screw and joint varies. This can cause the torque needed to run a screw down a thread, before engagement with the joint surface takes place, to vary as well. These effects could be, for example, hole interference, prevailing torque or varying lubrication.

Monitoring the rundown torque is useful when running down a lock nut or screw that has a plastic insert in the threads to help the fastener resist vibration. This will require a higher torque, known as prevailing torque, to overcome the interference.

Rundown torque limits

Parameter name | Description | Default value
--- | --- | ---
Rundown torque limits | Off: Rundown torque limits is turned off. On: Rundown torque limits is turned on. | Off
Offset | Angle offset before the Angle interval begins. | 0°
Length | Angle defining the Rundown torque limit section. | 360°
Torque min | Torque value for lower Rundown torque limit. | 0 Nm
Torque max | Torque value for upper Rundown torque limit. | 4.75 Nm

# Rundown Angle Limits

By monitoring the angle of rotation during rundown, errors such as screws with incorrect thread size or length are detected. For example, threads that are too long would require a greater turning angle for the screw to reach snug.

This option can be used if the target for the step is an angle value.

Parameter name | Condition | Description | Default value
--- | --- | --- | ---
Rundown angle limits |  | Off: Rundown angle limits is turned off. From Trigger: Rundown angle limits is turned On. The system starts to monitor the tightening angle as soon as the tool trigger is pressed and reports if angle limits are violated. From torque: Rundown angle limits is turned On. The system starts to monitor the tightening angle from the specified torque value and reports if angle limits are violated. | Off
Rundown angle monitoring torque | Rundown angle monitoring torque = From torque | Torque value from where Rundown angle limits are set. | 2.50 Nm
Angle min | Rundown angle limits = On | Angle value for lower angle limit from starting point. | 100°
Angle max | Rundown angle limits = On | Angle value for upper angle limit from starting point. | 1000°
Time min | Rundown angle limits = On | Minimum time for the step. | 10 ms
Time max | Rundown angle limits = On | Maximum time for the step. | 5000 ms

# Post View Torque

Some joints have a torque peak prior to Rundown complete. Post view torque makes it possible to monitor torque values during two specified angular intervals. The interval starts are defined as an angle prior to Rundown complete and torque is then monitored for a specified angular interval.

Post view torque is therefore similar to Rundown torque limits except that the maximum and minimum limits can be positioned independently of each other and can differ in length to better control the outcome of the rundown.

Monitoring the rundown post view torque is an option and controlled by a switch

Rundown post view torque

Post view torque parameters
Parameter name | Condition | Description | Default value
--- | --- | --- | ---
Post view torque |  | Post view torque is selected from a shortcut menu. Off: Post view torque is turned off. On: Post view torque is turned on. | Off
Torque min | Post view torque = On | Torque value for lower Post view torque limit. | 4 Nm
Torque min offset | Post view torque = On | Angle offset before the Post view torque min interval begins. | 720°
Torque min length | Post view torque = On | Angle length defining the Post view torque min section | 90°
Torque max | Post view torque = On | Torque value for upper Post view torque limit. |
Torque max offset | Post view torque = On | Angle offset before the Post view torque max interval begins. | 360°
Torque max length | Post view torque = On | Angle length defining the Post view torque max section | 90°
Compensate value | Post view torque = On | The Compensate value is selected fro a shortcut menu. Off: Peak torque On: Average torque |

# Rundown Parameters

All rundown parameters
Parameter name | Condition | Description | Default value
--- | --- | --- | ---
Self-tap |  | Self-tap is activated through a switch Off: Self-tap is turned off. On: Self-tap is turned on. | Off
Length | Self-tap = On | Defines the angle to turn the socket during Self-tap. Measured from the end of the Start step. | 360°
Speed | Self-tap = On | Defines the speed during Self-tap |
Torque min | Self-tap = On | Torque value for lower Self-tap limit. | 0 Nm
Torque max | Self-tap = On | Torque value for upper Self-tap limit. | Tool max torque
Rundown torque limits |  | Rundown torque limits is activated through a switch Off: Rundown torque limits is turned off. On: Rundown torque limits is turned on. | Off
Offset | Rundown torque limits = On | Angle offset before the Angle interval begins. | 0°
Length | Rundown torque limits = On | Angle defining the Rundown torque limit section. | 360°
Torque min | Rundown torque limits = On | Torque value for lower Rundown torque limit. | 0 Nm
Torque max | Rundown torque limits = On | Torque value for upper Rundown torque limit. | % of target torque
Rundown angle limits |  | Rundown angle limits is selected from a shortcut menu. Off: Rundown angle limits is turned off. From Trigger: Rundown angle limits is turned On. The system starts to monitor the tightening angle as soon as the tool trigger is pressed and reports if angle limits are violated. From torque: Rundown angle limits is turned On. The system starts to monitor the tightening angle from the specified torque value and reports if angle limits are violated. | Off
Rundown angle monitoring torque | Rundown angle monitoring torque = From torque | Torque value from where Rundown angle limits are set |
Angle min | Rundown angle limits = On | Angle value for lower angle limit from starting point | 100°
Angle max | Rundown angle limits = On | Angle value for upper angle limit from starting point | 1000°
Time min | Rundown angle limits = On | Minimum time for the step | 10 ms
Time max | Rundown angle limits = On | Maximum time for the step | 5000 ms
Post view torque |  | Post view torque is activated through a switch Off: Post view torque is turned off. On: Post view torque is turned on. | Off
Torque min | Post view torque = On | Torque value for lower Post view torque limit. |
Torque min offset | Post view torque = On | Angle offset before the Post view torque min interval begins. | 720°
Torque min length | Post view torque = On | Angle length defining the Post view torque min section | 90°
Torque max | Post view torque = On | Torque value for upper Post view torque limit. |
Torque max offset | Post view torque = On | Angle offset before the Post view torque max interval begins. | 360°
Torque max length | Post view torque = On | Angle length defining the Post view torque max section | 90°
Compensate value | Post view torque = On | The Compensate value is selected from a shortcut menu. |
Rundown complete torque |  | Defines the torque value for when snug is reached and the rundown is completed. The program can then move on to tightening the screw. Rundown complete must be less than First torque in multi-step strategies or Target torque in the TurboTight strategy. | 0°

# Time Monitoring

Time monitoring is available for most tightening strategies, but has some variations:

- Time monitoring is not available for the Rotate strategy.

- Time monitoring is available for the Rundown stage.

- Time monitoring is available for the Final tightening step of the tightening stage.

- Time monitoring is used in conjunction with angle monitoring. When angle monitoring is enabled or the final target is an angle value, time monitoring is available.

If the time limits are violated during either stage, the tightening is terminated. The NOK detailed reason result is set accordingly.

In this Section

- Detailed NOK reason

# Detailed NOK reason

Parameters for NOK detailed reason
NOK reason | Description
--- | ---
Rundown time high | The measured time from the activation time until rundown complete is higher than the time maximum limit.
Rundown time low | The measured time from the activation time until rundown complete is lower than the time minimum limit.
Final tightening time high | The measured time from the activation time until the tightening target reached is higher than the time maximum limit
Final time tightening low | The measured time from the activation time until the tightening target reached is lower than the time minimum limit

# Stop Stage

The stop stage terminates the tightening so that the socket can be released.

Soft stop causes the tightening to stop in a more ergonomic fashion. It is desirable for the tool not to stop within the time interval of 50-300 ms, as this is known to make it feel like an uncomfortable stop.

Parameter | Description | Default value
--- | --- | ---
Soft stop | Turns the Soft stop on or off. Off: No Soft stop is used. On: Soft stop is activated. When target torque is reached, the tools speed is immediately decreased to 75%. Then the speed is decreased to zero in at most 40 ms. | Off

# Loosening a Screw

By setting the loosening parameters, you can control the behavior of a loosening for a specific tightening program. Specify the loosening speed and torque to ensure that the screw is unscrewed as desired, so that the screw thread does not break, regardless of what tool is used.

A loosening is considered OK when Run-up torque is reached. Depending on variations in screw length, the system cannot determine when the screw has been run up completely. The operator will need to proceed with the loosening until it is considered finished.

The loosening is divided into normal loosening and TurboLoosening. The selection is made automatically based on tool capability and on the selected tightening strategy. TurboTight can achieve a much higher target torque and thus a normal loosening strategy is not sufficient. The TurboLoosening uses a pulsing strategy and is selected automatically, depending on whether the tool can support this.

Loosening

Loosening steps
Parameter name | Description
--- | ---
Start | Run at slow speed. If the measured torque is below the detection torque, go to the run-up step.
Loosening | For normal loosening: Run att slow speed until the measured torque is below the run-up torque, then proceed to the run-up step For Turboloosening: Loosen the screw by using as many pulses as needed until the measured torque is below the run-up torque, then proceed to the run-up step
Run-up | Run the tool at the loosening speed, as long as desired.

Loosening parameters
Parameter name | Description | Default value
--- | --- | ---
Loosening enabled | Selected by radio buttons. Off: Loosening is disabled. On: Loosening is enabled and additional parameters can be configured. | On
Detection torque | Selected by radio buttons. Auto: The value is set based on the tool type and the tool capability. On:The value is set manually. | 7% ToolMaxTorque
Detection torque | The minimum torque required to begin performing a loosening operation and produce a loosening result. | 3.5 Nm
Run-up torque | Selected by radio buttons. Auto: The value is set based on the tool type and the tool capability. On:The value is set manually. |
Run-up torque | When the torque falls below Run-up torque, the loosening is considered to be OK. Depending on variations in screw length, the system cannot determine when the screw has been run up completely. This is for the operator to decide. | 3.5% ToolMaxTorque

# Stage Parameter Descriptions

# Target Torque Limits

By setting the Target torque limits, it is possible to discard a tightening should the torque result not fall within the specified torque limits. A torque set too high can cause the bolt to deform, break, or even strip the thread as a result of passing the yield point. Not enough torque can result in the clamping force not being sufficient to withstand the forces for which the joint is designed.

Target torque limits

# Target Angle Limits

With Target angle limits set, it is possible to monitor whether the nut is turned to the desired angle during the tightening.

Target angle limits

# Torque Compensation

The graphical representation is used in the documentation to describe the configuration setting and the interpretation of the parameter values. The graphs are not used in the GUI of the controller or ToolsTalk 2.

By using torque compensation, the actual clamping force applied to the joint can be better determined and the scatter in the applied clamping force can be reduced.

The torque compensation point is set by referring back to a specified angle from Rundown complete and calculating a value for the torque used during rundown. This is then compensated for when creating the preload in the bolt by adding the torque value calculated in the torque compensation point to the Target torque.

Parameter | Description
--- | ---
Torque compensation | Enables adjustment of the Target torque used in the rundown stage. Off: No compensation is made. On: Manually sets the Torque compensation point.

A | Start stage
B | Rundown stage
C | First step of the Tightening stage
D | Final step of the Tightening stage
E | Stop stage
F | Final tightening target torque
G | Torque over time curve
H | Torque compensation value (torque)
J | Torque compensation reference point (angle)
K | Rundown complete target torque
L | First tightening target torque

The optional torque compensation parameter is found in the first tightening step in the tightening stage, but the measurement is done in the rundown stage. If enabled, the following happens:

- A torque value is measured at a defined angle before rundown complete.

- The measured value is defined as the torque compensation value.

- The tightening continues into the first tightening step.

- All the following torque values, like for example a target torque or an angle monitoring torque, are compensated with the addition of the torque compensation value.

# Residual Torque Correlation Factor

The term Residual torque correlation factor is similar to a calibration and adjusts between the dynamic torque, measured in the electrical tool, and the residual torque, measured by a control tool.

The Residual torque correlation factor is available for all tools running the TurboTight strategy and the TensoPulse tightening strategy. It is also available for the battery pulse tools that are supported by the controller.

When using a Residual torque correlation factor that differs from 100, the reported Final torque is no longer the dynamic torque measured by the tool transducer.

The dynamic torque measurement uses an internal torque transducer that constantly measures the torque. When the target torque is reached, the tool stops and the result is evaluated and reported. The measured final torque in the transducer is affected by the joint condition, the tool speed, gears and sockets.

The residual torque is measured after the tightening is completed. It is the torque needed to continue or restart the tightening to a higher level. The residual torque is determining the clamping force in the joint.

A dynamic torque measurement is highly repetitive but may differ between tool type and tool speed. | A handheld calibrated torque wrench provides high accuracy measuring the residual torque but has higher variations due to joint relaxation, torque decay, friction or operator technique.

The Residual torque correlation factor is a compensation between the dynamic torque and the residual torque. The factor should be determined by conducting tests. The selected tightening program is performed a few times and the dynamic torque is recorded. The tightenings are also manually measured to determine the residual torque.

The Residual torque correlation factor can be calculated by dividing a residual torque by a dynamic torque. TheResidual torque correlation factor is presented as percent and is by default 100%. This means the reported dynamic torque value has not been modified.

Parameters | Function
--- | ---
Target torque | The tool target torque set for the tightening using the TurboTight strategy.
Final dynamic torque | The final torque reported as the result of the performed tightening.
Dynamic torque | The dynamic torque measured by a reference transducer.
Residual torque | The desired residual torque that ensures the desired clamping force.
Residual torque correlation factor | The compensation factor between residual torque and dynamic torque

An example of how torque tuning can be used:

The TurboTight strategy is selected. The joint shall be tightened to 12 Nm to reach the desired clamping force. The following set up is made:

Example settings | Value | Function
--- | --- | ---
Target torque | 12 Nm | The programmed desired target torque in the controller
Residual torque correlation factor | 100 | The compensation factor between residual torque and dynamic torque

A number of tightenings are made. After each tightening the joint is checked with a calibrated torque wrench. The average is calculated and the following result has been found:

Initial parameters and results | Value | Function
--- | --- | ---
Target torque | 12 Nm | The programmed target torque in the controller.
Final torque | 12 Nm | The final torque reported as the result of the performed tightening.
Dynamic torque | 12 Nm | The uncompensated measured torque from the tool transducer.
Residual torque | 10 Nm | The residual torque measured with a calibrated torque wrench or other test tool.
Residual torque correlation factor | 100 % | The compensation factor between residual torque and dynamic torque

The testing shows that the residual torque is too low to produce the desired clamp force. The Residual torque correlation factor is calculated to 0.83, which is 83 %. An adjustment of the tuning factor is made and the following result is obtained.

Final parameters and results | Value | Function
--- | --- | ---
Target torque | 12 Nm | The programmed target torque in the controller.
Final torque | 12 Nm | The final torque reported as the result of the performed tightening.
Dynamic torque | 14.5 Nm | The uncompensated measured torque from the tool transducer.
Residual torque | 12 Nm | The desired residual torque that ensures the desired clamping force.
Residual torque correlation factor | 83 % | The compensation factor between residual torque and dynamic torque.

What this shows is that we need to tighten a bit more than the specified target, to compensate for differences and to reach the desired torque in the joint.

It is important that the correlation is made with the same tool type and parameter configuration that will be used in production.

# Premature Torque Loss Detection

The tightening program moves from rundown to tightening when the screw head is snug and the torque increases rapidly. This point is refereed to as the Rundown torque and is defined by reaching the set torque value.

For a correct tightening, it is assumed that the torque increases. If the torque decreases, the following may be assumed:

- The socket slips of the screw head while the tool trigger is still pressed. The tool detects rapid decrease in torque and continues to rotate according to its speed setting.

- The screw breaks while the tool trigger is still pressed. The tool detects rapid decrease in torque and continues to rotate according to its speed setting.

If a decrease in torque is detected at this stage, proceed with the following:

1. Save the last torque value before a decrease is detected.

2. Start a detection timer.

3. Continue the tightening and measure the torque.

   - If the torque builds up and reaches the saved level and continues to build according to the tightening program within the set time period, then continue normally with the tightening

   - If the torque loss continues until the end of the set time period, the tightening is considered NOK.

If the tool detects the torque loss, it continues to spin freely as long as the tool trigger is pressed. The tightening is terminated when the operator releases the trigger and result is reported with detailed NOK reason = premature torque loss detected.

# Creating a Tightening Program

If the list is empty, then no tightening programs have been created. Start by creating a new tightening program:

1. In the Plant structure area, select a controller.

2. Go to Tightening program .

   The Tightening program overview displays a list of available tightening programs.

3. Select Add. The Create new Tightening Program window is displayed.

4. To create a new tightening program, enter the parameters described in the table below .

5. Select Add. The window closes and the workspace shows the configuration menu where more parameters must be added.

Create new tightening program parameters
Parameter | Description
--- | ---
Name | Issue the tightening program with a name in the parameter entry field.
Index (Tightening program number) | The first free index number is given by default, but any other free number can be assigned to the tightening program. The index number can not be changed at a later stage. Enter an optional index number in the parameter entry field.
Strategy | Select tightening strategy from the shortcut menu.
Control strategy | Select from the shortcut menu. Only applicable to certain strategies.
Target | Select to which final target the tightening shall be performed. Select from the shortcut menu.
Target | Enter the target value(s) in torque and/or degrees for the tightening step.

The available strategies depend on the IAM module and the controller software license.

# Tightening Program Configuration - General Parameters

The Tightening program configuration menu contains some general parameters that are not directly part of the tightening program. These are described below:

All the parameters for a tightening program are entered and edited in the Step configuration menu.

1. Select a controller in the Plant structure workspace .

2. Select the Tightening program tab.

   The Tightening program overview shows a list of tightening programs.

3. Double-click the name of one of the tightening programs in order to view and/or configure it.

The step configuration menu has two tabs: Tightening and Loosening.

Menu control | Description
--- | ---
| Collapse the Properties menu. This provides better screen utilization.
| Expand the Properties menu. This provides access to all the configurations.

Parameter | Description | Default value
--- | --- | ---
Name | It is recommended to issue the tightening program with a unique name. The index number is created when the tightening is created and is fixed. The lowest available number is assigned to the program when it is created. | Program
Description | An optional description of the tightening program. |
Strategy | The available options depend on the controller software and license version. |
Direction | Thread direction defines the tightening direction of the spindle to clockwise (CW) or counterclockwise (CCW). The rotation of the spindle will always be in this direction, except during the loosening step used in the Three step strategy. | CW
Rehit detection | Early: Terminates the tightening immediately when an already tightened screw/bolt is detected. The tightening will be considered as NOK. Requires that Soft start is activated. Complete: Even though an already tightened screw/bolt is detected, the tightening is not terminated until all tightening stages have been executed. The tightening will be considered as NOK. To make a rehit detection when Soft start is not used, the Rehit detection Complete option must be selected. Rehit detection Complete will not terminate the tightening until all tightening stages have been executed. The tightening will be considered a rehit if the speed fails to reach half of the rundown speed, a rehit error is then indicated. Off: No rehit detection will be performed. Combination Soft start = Off and Rehit = Early is not allowed | Early
Current monitoring | Current monitoring provides extra security to monitor the tightening torque. This is a complement to the torque sensor in the tool. On: At final target torque, the rotor current is measured and converted to a torque value. If the calculated torque is within 10% of the measured torque, the tightening is considered to be OK. Off: Current monitoring is disabled and the tool torque is measured by the torque sensor. |
True angle compensation | Certain tools can detect and measure the tool rotation during tightening. If the tool is rotated during tightening, the angle measurement may be corrupted. This may lead to a faulty tightening if the tool movement is too large. For variations within specified limits, the controller can compensate these rotations and make a correct tightening. This is an additional Licensed Feature, available per Virtual Station. | Off
Negative angle limit | Active if True angle compensation is set to ON Defines the maximum negative rotation of the tool. If the value is exceeded the tightening is terminated and an error is reported. This is expressed in a numeric angle value. | 30 degrees
Positive angle limit | Active if True angle compensation is set to ON Defines the maximum positive rotation of the tool. If the value is exceeded the tightening is terminated and an error is reported. This is expressed in a numeric angle value. | 30 degrees
Attachment tuning enabled | Attachment tuning gives the possibility to compensate for front attachments on the tool. The compensation can be made for each tightening program. An operator can hot swap attachments and then select a tightening program tuned for that specific attachment. Attachment tuning is available for all conventional strategies, excluding the STwrench. Attachment tuning requires some special steps that are described separately. | No

## Validation

During the configuration of tightening programs, the entered values are compared with the tool capability values to prevent parameters being outside of the selected limits. User defined maximum values are useful if many different tools are being used.

If Validate against tool values is set to Off, these values are ignored, and the validations are made according to the maximum tool capability.

If Validate against tool values is set to On, then It shall be possible to choose a tool to validate the Tightening program(s) against from all the connected tools. The tool to validate against is done per client, giving the operator the possibility to validate against different tools from different clients.

Parameter | Description | Default value
--- | --- | ---
Tool |  | Manual
Max Torque | The maximum limit used in the validation. Can be selected to any value but it is recommended to use the actual tool value. This is expressed in a numeric torque value. |
Max speed | The maximum limit used in the validation. Can be selected to any value but it is recommended to use the actual tool value. This is expressed in a numeric rpm value. |

A controller may have several virtual stations including tools that have different capabilities. The User defined values can be selected per each tightening program.

## History

Tightening program history stores the last ten user changes. Select any stored version in order to see the parameter details. Activate the selected version by clicking Replace. To print all stored parameter history details of the selected tightening program, select History > Report > Print.

## Print

Select the Print button to open a shortcut window that displays all the current tightening program configurations and the parameter values. This window can be sent to a printer.

To print a stored tightening program, select a program in History and select the Report tab.

## Tightening program validation

The ToolsTalk 2 application automatically compares the entered parameters with the parameter rules and the optional tool capabilities. If the validation detects any errors then these are reported together with an error description.

Some parameters have a default value when a new program is created. It may happen that tightening rules are violated and that the Error Indicator appears.

The Error indicator symbol.

The location of Error indicator points towards the faulty parameter. Let the pointer hover over the Error indicator, a pop-up field explains which rule is violated. In the case of an error, change the parameter. When the parameter is correct the Error indicator will disappear.

Relevant Information

- Attachment Tuning
- Reverting Controller Configurations
- True Angle Compensation

In this Section

- Tightening Program History
- Attachment Tuning

# Tightening Program History

ToolsTalk 2 keeps track of the last ten changes that have been made to a tightening program and pushed to the controller:

- A printed report with all original tightening program parameter settings and the changes made.

- A printed report with all current tightening program parameter settings.

- A list of revision history for the tightening program. It is possible to quickly change to a previously tightening program parameter setting by selecting the desired version and clicking the Replace command button.

The revision history is created when a Push command is executed and the controller is updated from ToolsTalk 2.

1. Select a controller in the Plant structure workspace .

2. Select the Tightening program icon .

3. Double-click on a tightening program in order to open the tightening program configuration workspace.

4. Select the History command button.

   The Managing Tightening Program History pop-up window opens.

Viewing a previous tightening program

1. Select the Changes tab.

   The left side of the window shows a list of revision histories.

2. Click one row to select a revision.

   The right side of the window shows a detailed list of the configuration parameters.

   It is possible to compare two tightening program revisions. After selecting the first tightening program, hold the Control (Ctrl) button on the keyboard and select a second tightening program. The right side window then shows both settings. It is possible to show all parameters, or only the parameters that differ by selecting the Show only changes box.

3. When done, select the Close command button.

   The pop-up window closes.

Comparing two stored tightening programs

1. Select the Changes tab.

   The left side of the window shows a list of revision histories.

2. Select two tightening programs from the stored tightening programs.

   A comparison between the two selected tightening programs will be displayed in the column to the right.

3. Select the Close command button.

   The pop-up window closes.

Switching to a previous tightening program

1. Select the Changes tab.

   The left side of the window shows a list of revision histories.

2. Click one row to select a revision.

   The right side of the window shows a detailed list of the configuration parameters.

3. Select the Replace command button.

4. Select the Close command button.

   The pop-up window closes.

Printing a tightening program history report

1. Select the Report tab.

2. Select the Print command button.

   The print dialog window opens for printing.

3. When done, Select the Close command button.

   The pop-up window closes.

The printed report contains a complete list of all configurations and parameter values. In addition to this, it lists all the revisions and the changes made in each of the revisions. This provides a complete history of what has been done in the Tightening program. The time stamp shows when changes were made, or when a push was done from ToolsTalk 2.

Relevant Information

- Pushing Configurations to a Controller

# Attachment Tuning

Attachment tuning gives the possibility to compensate for front attachments on the tool. The compensation can be made for each tightening program.

An operator can hot swap an attachment and then select a tightening program tuned for that specific attachment.

Attachment tuning is available for all conventional strategies, excluding the STwrench.

1. Select a controller in the Plant structure workspace .

2. Select Tightening program .

   The Tightening program overview shows a list of tightening programs.

3. Double-click the name of one of the tightening programs in order to view, or configure the program.

4. Select Attachment tuning enabled Yes or No in the Properties menu.

   If this feature is disabled, the remaining parameters are invisible.

5. Go to the Step configuration menu and to the Start stage.

6. Select Use attachment tuning Yes or No.

   If this feature is switched to Yes, the tuning factors are visible and can be edited.

The tuning parameters are:

- Attachment gear ratio

- Efficiency tuning

Parameters for Attachment tuning
Attachment tuning | Description | Default
--- | --- | ---
Attachment gear ratio | The Attachment gear ratio is needed to compensate the angle. Minimum: 0.5 Maximum: 100 Socket rotation speed = Tool speed / gear ratio | 1.0
Efficiency tuning | Attachment gear ratio combined with the Efficiency tuning is needed to compensate the torque. Minimum: 0.5 Maximum: 1.0 For example 0.9 means 10% efficiency loss. | 1.0

CAUTION; The attachment gear ratio affects the tool speed and in turn, may affect the safety limits.

# Importing a Tightening Program

A previously exported Tightening Program can be imported in a ToolsTalk 2 installation.

The same rules as for copy and paste of tightening programs are applicable for export and import for tightening programs, refer to Copying and pasting tightening programs

1. In the Plant structure area, select a controller.

2. Go to the Tightening program tab.

   The Tightening Program overview displays a list of available tightening programs.

3. Select ADD. In the Create new Tightening Program dialog, select the Import tab.

4. Select Open file and locate the desired import file. The file must have the format json. Select ADD.

   The imported Tightening Program is added to the list in the Tightening Program workspace.

# Deleting a Tightening Program

1. Select the corresponding check box for each tightening program which is to be deleted.

2. Select Manage and then select Delete.

   The list in the tightening program overview is updated.

# Copying and pasting tightening programs

It is possible to copy and paste tightening programs. The following rules applies for hand-held controllers (PF8, PF6000, STRW, PFXC, IXB and ToolsControl):

- Copy and paste can be done on the same controller.

- It is possible to copy and paste between different hand-held controller types and versions.

- It is possible to copy and paste from an older controller version to an newer one but not possible to copy and paste from a newer controller version to an older one.

Validation errors that may occur that need to be corrected if copy and paste is done between different controller types.

A copy of a tightening program always includes everything, as for example attached or associated programs and links.

Copying and pasting

1. Select a controller in the plant structure.

2. Select Tightening Program. The workspace area shows all the available programs.

3. Right-click on a single row or select check boxes for several rows, right click and select Copy.

4. To paste the copy into the same controller, right-click anywhere in the empty workspace area and select paste. The copy is added to the first available position in the existing list.

   If there is no space in the list for the copy, the whole operation will fail.

   To paste the copy into another controller; select a controller in the plant structure and then select the applicable workspace. Right-click in the workspace and select paste.

   It is also possible to paste a copy into the Program Templates library workspace.

5. Double-click the pasted copy to open and modify it.

# Global Tightening Program

A tightening program can be either Local or Global. If a tightening program is global, it is indicated with a Yes in the Library link column in the list of tightening programs.

In some documentation and in older GUI versions, the word tightening program may be substituted with the word Pset.

A Local tightening program is valid for a single controller.

Viewing the list of Tightening Programs

1. Select a controller in the Plant structure workspace .

2. On the toolbar, select Tightening program .

   The Tightening program overview shows a list of tightening programs.

A Local tightening program can only be edited via the Tightening program tab.

A Local tightening program is not visible in the Tightening program library .

A Global tightening program is valid for multiple controllers subscribing to the tightening program. If a Global tightening program is distributed to a controller, the controller will gray out the program so it cannot be modified, when using traditional strategies such as CATLA. When using multistep strategies, the program can still be edited but it will be overwritten if changes are made in ToolsTalk 2. The Global tightening programs are located in the tightening program library.

Accessing the Library

1. Select Library in the left-side menu bar.

2. Select Tightening program library in the top menu bar.

   The Tightening program library shows a list of global tightening programs.

If a controller subscribes to a Global tightening program, it is visible in Tightening program , but editing is prohibited.

A Global tightening program can only be edited via the Tightening program library .

In this Section

- Converting a Local Tightening Program into a Global Tightening Program
- Converting a Global Tightening Program into a Local Tightening Program

# Converting a Local Tightening Program into a Global Tightening Program

1. In the list of local tightening programs, choose the program to convert by selecting the check box in the leftmost column.

2. Select Manage.

3. Select Add to library.

4. Select Create in the dialog window to copy the local tightening program to the library, this action will also close the window.

5. Clear the check box in the leftmost column.

The Library link column is marked with Yes for the selected tightening program.

ToolsTalk 2 can distinguish between a local and global tightening program, although the controller itself has no knowledge of this. Therefore it is important to specify the action in ToolsTalk 2 if a tightening program is changed via either the controller GUI, or the web GUI. This action is defined in the distribution of a global tightening program in the tightening program library.

# Converting a Global Tightening Program into a Local Tightening Program

1. In the list of local tightening programs, choose the program to convert by selecting the check box in the leftmost column.

2. Select Manage.

3. Select Unlink.

4. Clear the check box in the leftmost column.

The Library link column is now empty for the selected tightening program.

# Comparing Tightening Programs

It is possible to make a quick comparison between two tightening programs, when configured to the same strategy.

Viewing the list of Tightening Programs

1. Select a controller in the Plant structure workspace .

2. On the toolbar, select Tightening program .

   The Tightening program overview shows a list of tightening programs.

Comparing two of the tightening programs shown in the list of programs

1. In the leftmost column, select the corresponding check boxes for both the tightening programs to be compared.

2. Select the Manage command button, and then select Compare.

If the two selected tightening programs do not have the same strategy, the comparison is not permitted.

The workspace displays a list of parameters for the two selected tightening programs. In the upper left corner the check box Show only differences can be selected to display only the parameters which differ.

# Approval Statuses

Status | Description
--- | ---
Approved | The program is approved and may be used on the controller. The program will be read-only.
Draft | The program is being changed/optimized. The program can be sent for approval once it is finalized. The program will be editable.

All programs can be used irrespective of the approval statuses. Approval statuses do not affect operational function of any programs.

Once a program enters the approval workflow, it will always have a status.

# Working with the Batch Sequence Tab

A Batch Sequence task is selected in a Virtual Station Task configuration, or by an external input source.

The tightening order can either follow a fixed scheme, or be left to the operator to decide in a free-order scheme. In either case, the sockets or signals can be used to communicate between the controller and the operator.

- A Batch consists of one tightening program, which is repeated a number of times.

- A Batch Sequence is an ordered set of batches, when the operation requires a combination of batches/tightening programs.

1. Select a controller in the Plant structure .

2. Go to Batch Sequence .

The columns contain the following information:

Batch sequence information
Column | Description
--- | ---
Name | Each Batch Sequence name starts with an index number. The following characters can be changed to any user defined name.
Description | The description of the batch sequence.
Last changed | Expressed in ToolsTalk 2 time.
Last changed by | Configuration data last changed by <user>.
Controller updated | Expressed in controller time.
Controller updated by | Controller updated by <user>.

The field Changed by and Controller updated by can be a registered ToolsTalk 2 user, created in the ToolsTalk 2 interface.

Command | Description
--- | ---
Manage | Export: Exports the Batch Sequence in .json format. Delete: Removes selected Batch Sequence from the list. Mark the check box for one or more batch sequences and select Manage, and then Delete from the drop-down list. The selected Batch Sequences are removed and the list is updated. The list of configurations will show irregularities in the index number scheme when a configuration is deleted. Index numbers do not change. Adding a new configuration will attempt to find the lowest free index position for a configuration.
Add | Create or Import a new Batch Sequence.

The Batch Sequence name consists of an index number combined with optional characters. The index position cannot be changed. A new configuration is given lowest possible available index number. The index number is important when using sources and identifier numbers to be part of the task selection process.

In this Section

- Batch Sequence Configuration Workspace
- Batch Sequence Configuration Menu
- Adding a New Batch to a Batch Sequence
- Copying and pasting Batch Sequences and Sources
- Exporting a Batch Sequence
- Importing a Batch Sequence
- Deleting a Batch in a Batch Sequence

# Batch Sequence Configuration Workspace

The Batch Sequence configuration workspace shows the details of a single batch sequence with the following configuration menus:

- Basic settings, with configuration name and description.

- General settings, controlling the flow and order of tightenings.

- Sequence configuration, creates the batch sequence from individual tightening programs.

Viewing the Batch Sequence menus

1. Select a controller in the Plant Structure workspace .

2. Select Batch Sequence in the menu bar.

3. Double-click on the Name of the desired batch sequence to display the menus.

# Batch Sequence Configuration Menu

The options in the Properties menu are as follows:

Parameter name | Description
--- | ---
Name | Default name Batch sequence. This can be edited.
Description | The optional description issued for the batch sequence.
Lock tool on batch sequence complete | On: The tool is locked when the batch sequence is completed. Off: The tool remains unlocked when the batch sequence is completed.
Free order | No: The batches within the sequence are executed in the order listed by the index number. If sockets have been specified, the system will prompt for the next socket when the batch is to be performed. Yes: The tightenings and the batches within the sequence can be executed in any order. The operator must indicate to the system which batch is to be executed by using the Socket selector bits, these act as identifier numbers.
Increment on NOK | No: The batch counter is not incremented if the tightening fails (NOK). Yes: The batch counter is incremented if the tightening fails (NOK).
Max consecutive NOK | Max consecutive NOK is defined as the maximum allowed number of consecutive failed tightenings in a batch. If the value is reached, the event Too many NOK tightenings (4020) is displayed.
Decrement on loosening | Never: The batch counter is not decremented when a loosening is performed. This is the default value. Always: The batch counter is decremented when a loosening is performed. When last tightening OK: If the preceding tightening was OK, the batch counter is decremented when a loosening is performed.
Sequence abort time | On: The selected batch sequence will be aborted within a specified time limit. When you select On, the Abort time field opens. Off: The selected batch sequence cannot be aborted.
Abort time | The number of seconds during which the selected batch sequence will be aborted. Allowed range is between 1 s to 1600 s.

A batch sequence is completed (and the tool may be locked) when either:

- All tightenings have been completed with an OK or NOK result.

- The Abort sequence signal terminates the task. Unperformed tightenings are reported with NOK result.

In the Sequence configuration menu, the different batches are combined into a batch sequence. A batch consists of one single tightening program that is repeated a number of times.

Each row in the Sequence configuration menu represents one single batch.

Workspace options
Column | Description
--- | ---
| Check box.
Batch | Batch index number (order number within the sequence).
Tightening program | Drop-down menu. Select tightening program for this batch.
Batch size | The number of tightenings the batch will consist of.
Identifier number | An externally generated identifier number or a Socket selector position translated into an identifier number. Using fixed order tightening, the operator is guided to pick the correct socket. Using free order tightening, the corresponding batch is selected when the operator picks a socket.

Relevant Information

- Pushing Configurations to a Controller

# Adding a New Batch to a Batch Sequence

1. In the Plant structure , select a controller from the list.

2. On the menu bar, select the Batch Sequence tab . The workspace displays a list of batch sequences.

3. Select the Add command button in the Sequence configuration menu. The To create a new Batch Sequence window opens.

4. Issue the Batch Sequence with a name, and then select ADD.

5. Select the relevant parameters in the Properties.

6. Select a Tightening Program for the batch in Sequence Configuration.

7. Enter the Batch Size (the number of tightenings the batch will consist of).

8. Enter an optional Identifier Number.

The new Batch Sequence will be issued the first free position in the sequence list. If there are no free slots it will be placed at the bottom of the list and assigned the lowest available index number. It is not possible to change the index number to rearrange the batch tightening order.

# Copying and pasting Batch Sequences and Sources

It is possible to copy and paste:

- Batch Sequences

- Source Batches and Source Tightenings

The following rules apply:

- It can be done on the same controller

- It can be done between controllers of the same type that runs the same software version.

A copy of a batch sequence or source always includes everything as for example attached or associated programs and modes and links.

Example: A copy of a Source Batch > The paste creates a new Source batch with a new Batch Sequence and a Program linked to the new Source Batch.

Copying and pasting

1. Select a controller in the plant structure

2. SelectBatch Sequence or Sources. The workspace area shows all the available programs.

3. Right-click on a single row or select check boxes for several rows, right click and select Copy.

4. To paste the copy into the same controller, right-click anywhere in the empty workspace area and select paste. The copy is added to the first available position in the existing list.

   If there is no space in the list for the copy, the whole operation will fail.

   To paste the copy into another controller; select a controller in the plant structure and then select the applicable workspace. Right-click in the workspace and select paste.

   It is also possible to paste a copy into the Program Templates library workspace.

5. Double-click the pasted copy to open and modify it.

# Exporting a Batch Sequence

A Batch Sequence can be exported from one controller and imported to another.

Export and Import are only possible if they are performed on the same controller, or different controllers running the same software version and controller type.

When you export an existing batch sequence, any programs and modes associated with the batch sequence are also exported. These configurations are only copies and can be changed as per requirements.

1. In the Plant structure , select a controller from the list.

2. On the menu bar, select the Batch Sequence tab . The workspace displays a list of all the current batch sequences.

3. Select the check box of the Batch Sequence to be exported.

4. Select Manage, and then choose Export from the drop-down menu.

   A browser window opens for saving the export file.

5. The default file name is <BatchSequenceName>.json, the exported file can be given any name with the *.json extension.
   Select Save.

# Importing a Batch Sequence

A Batch Sequence can be exported from one controller and imported to another.

Export and Import are only possible if they are performed on the same controller, or different controllers running the same software version and controller type.

When you import an existing batch sequence, any programs and modes associated with the batch sequence are also imported. These configurations are only copies and can be changed as per requirements.

1. In the Plant structure , select a controller from the list.

2. On the menu bar, select the Batch Sequence tab. The workspace area shows a list of all the current batch sequences.

3. Select the Add command button and select Import.

4. Select Open File and browse to select the relevant .json file.

5. Select Add.

If there are no available slots, then the Batch Sequence will be added to the bottom of the list and assigned the lowest available index number. It is not possible to change the index number to rearrange the order.

# Deleting a Batch in a Batch Sequence

1. In Batch Sequence , select the check box for the batch to be deleted. Selecting the check box enables the MANAGE command button function.

2. Select the MANAGE command button, and then select Delete from the drop-down list. The selected batches are removed from the list.

When a batch is deleted from the batch sequence, the index sequence is compressed and updated, leaving no gaps. The index number of the deleted batch sequence will be assigned automatically to the next sequence that is created.

# Working with the Configurations Tab

Scanners, Stacklights and Tools are just some of the examples of device types that are connected to the controller via the I/O bus. Multiple devices can be connected to the I/O bus and each type of device has its own set of configuration parameters. Before operation, the configurations must be assigned to a Virtual Station.

## Viewing Existing Configurations

1. Select a controller in the Plant structure .

2. Select the Configurations tab in the menu bar.

   The workspace area shows a list of all the current configurations.

3. Double-click on a row in the workspace list to view details of the selected configuration.

   The workspace area shows the configuration menus where it is possible to configure the selected device.

   Configuration overview list
   Column | Description
   --- | ---
   Check box | Select to get access to the Manage command button list.
   Description | Description of the configuration
   Name | Shows the name of the controller template.
   Type | Type of configuration set-up.
   Library link | Displays Yes if there is a library link for the configuration.
   Last changed | Last changes made, expressed in ToolsTalk 2 time.
   Changed by | Last changes made, by <user>
   Controller updated | Last changes made, expressed in controller time.
   Controller updated by | Last update of the controller made, by <user>

   The list can be sorted by clicking in the header of each column.

In this Section

- Adding a Configuration
- Importing a Configuration
- Deleting a Configuration
- Accessory Components
- Configuration Types

# Adding a Configuration

1. In Configurations , select ADD. The Create new configuration dialog window opens.

2. Select type of device from the drop-down list, and then select ADD

3. In the Properties menu, type in a configuration name and a description.

Depending on selected type of device, each configuration has their own set of input and output signals. How to configure each type of device is described separately.

Relevant Information

- General Virtual Station
- Indicatorbox

# Importing a Configuration

1. In Configurations , select Add. The Create new configuration dialog window opens.

2. Select the Import tab.

3. Select Open file.

   A browser window opens for reading the import file.

4. Select the desired import file. The file must be in the format <configuration_name>.json. Select Open.

5. Select Add in the dialog window.

# Deleting a Configuration

1. In Configurations , select the check box for the configuration to be deleted. Selecting the check box enables the MANAGE command button function.

2. Select MANAGE and then select Delete from the drop-down menu.

The selected configurations are removed from the list.

A configuration can only be deleted when it is not assigned to a Virtual Station.

# Accessory Components

The different accessory types have different functionality and various types of lamps, buttons, sirens and switches.

Component name | Description
--- | ---
Stacklight lamp | A stacklight component that is associated with an output signal that can have one of the following functions: Lamp Rotating lamp Siren
Lamp | A component associated with an output signal with a light. The on-time of the light can be defined. The light can be set to fixed or flashing.
Button | A component associated with an output signal with a light and an input signal with a push button
Key switch | The component is associated with an input signal. A component with a removable key. It can be inserted and the switch can be turned in one direction. The input is active if the key is turned.
Two-way key switch | The component is associated with two input signals. A component with a removable key. It can be inserted and the switch can be turned in two directions. The inputs are active if the key is turned.
One-way switch | The component is associated with an input signal. A component with a rotation switch. It can be inserted and the switch can be turned in one direction. The input is active if the switch is turned.
Two-way switch | The component is associated with two input signals. A component with a rotation switch. It can be inserted and the switch can be turned in two directions. The inputs are active if the switch is turned.
Buzzer | A component associated with an output signal. If the output signal is active, a buzzing sound is emitted. The on-time of the buzzer can be defined. The buzzer sound can be set to fixed or intermittent.
Digital Input | A component or terminal, associated with a digital input signal.
Digital Output | A component or terminal, associated with a digital output signal.
Operator panel display | The operator panel display is a two digit display that can show the following: Batch count; displays the current position inside a batch Remaining batch; Shows the remaining tightenings in a batch Selected Tightening programs identity Selected batch sequence identity
Operator panel soft selector | The two way rotation switch also has a two digit display. The display shows the current batch within a batch sequence. Clockwise rotation; Moves to the next batch in a batch sequence. Counter clockwise rotation; Moves to the previous batch in a batch sequence. The display shows the current batch within a batch sequence.

Signal configuration

A | Component type (input) | B | Component identifier
C | Component type selection | D | Signal selection from a drop-down list
E | Component type (output) | F | Component type (input and output)
G | Output signal duration selection | H | Output signal duration time
I | Output signal flash selection On or Off switch | J | Input signal selection from a drop-down list

The selection of signals in the drop-down menu depends on the selected component.

In this Section

- Output Signal Configuration
- Input Signal Configuration
- Input and Output Combination

# Output Signal Configuration

An Output Signal can be mapped to a lamp, a stacklight, a siren, a buzzer or a terminal connector. The signal is valid during a programmable duration, or until the next tightening starts.

All the different accessories show where and how an output signal can be mapped.

## Mapping an output signal to a position:

1. Select a component or a position.

2. Select a Signal from the drop-down menu.

3. Set the Duration switch to Time or to Next tightening.

4. If Time is selected, a parameter entry box is displayed. Enter the duration of the output signal in seconds.

5. Set the Pulsating position switch to On for a flashing or intermittent signal, or to Off for a steady signal.

If the position is a stacklight, a Rotating option is also possible.

# Input Signal Configuration

An input signal can be mapped to a button, switch or a terminal connector. The signals are continuously sampled by the controller.

Event input signals trigger the controller. One example is to press a push button and then release it.

State input signals are active as long as the signal is present. One example is a key switch. Another example is to press a push button and keep it pressed.

All the different accessories show where and how an input signal can be mapped.

## Mapping an input signal to a position:

1. Select a component or a position.

2. Select a Signal from the drop-down menu.

Certain components, for example two-way switches, may be configured with two input signals.

# Input and Output Combination

Certain components, like a push-button, may be mapped with both an Output Signal (lamp) and an Input Signal (button). The output signal is valid during a programmable duration or until the next tightening starts. The input signal is continuously sampled by the controller.

All the different accessories show where and how an output signal can be mapped.

## Mapping an output signal to a position:

1. Select a component or a position.

2. Select a component type from the drop-down menu. The following selections and parameter entry boxes, depend on the selected component type.

3. Select an Output Signal from the drop-down menu.

4. Set the Duration switch to Time or to Next tightening.

5. If Time is selected, a parameter entry box appears. Enter the duration of the output signal in seconds.

6. Set the Pulsating position switch to On for a flashing or intermittent signal, or to Off for a steady signal.

7. Select an Input Signal from the drop-down menu.

# Configuration Types

# Internal I/O

The controller has two screw terminals located on the inside. They can be used to connect digital input and output signals.

All the digital input signals and the digital output signals that are listed in the Reference section can be routed to the internal I/O terminals.

For electrical specification and connections, see the controller documentation.

How to assign an accessory configuration to a Virtual Station is described in the Virtual Station section.

Relevant Information

- Adding an accessory to a Virtual Station
- Unassigning an Accessory from a Virtual Station

# I/O Expander

The I/O expander is connected to the I/O bus and provides an extension to connect digital input and output signals. Multiple expanders can be connected. Read the I/O expander documentation for address configuration and specifications of connections.

The following device types can be selected:

- I/O Hub: 8 channels

- I/O Expander: 16 channels

How to assign an accessory configuration to a Virtual Station is described in the Virtual Station section.

Relevant Information

- Adding an accessory to a Virtual Station
- Unassigning an Accessory from a Virtual Station

# Operator Panel

The Operator Panel is connected to the I/O bus and provides a configurable digital communication link between an operator and the controller. Lamps, buttons, buzzers and switches are used in the communication. Read the operator panel documentation for address configuration and specifications of connections.

How to assign an accessory configuration to a Virtual Station is described in the Virtual Station section.

Relevant Information

- Adding an accessory to a Virtual Station
- Unassigning an Accessory from a Virtual Station

# Socket Selector

# Viewing/Editing or Creating a Socket Selector Configuration

The Socket Selector is connected to the I/O and assists the operator in selecting the correct socket for the tightening procedure.

Viewing/Editing a Socket Selector Configuration

1. Select a controller in the Plant Structure .

2. Go to Configurations .

   The workspace area displays a list of created configurations for the selected controller.

3. Double-click on the name of the selected Socket Selector configuration in order to view or edit the configuration.

Creating a Socket Selector Configuration

1. In Configurations , selectAdd.

2. The Create new configuration dialog window is displayed. Choose Socket Selector form the drop-down list, and then select Add.

3. In the Properties area of the menu, enter a configuration name and description.

4. In the Socket Selector Configuration, choose Control type Auto or External.

5. For each socket position that should be active, select the check box .

6. For each socket position that should be inactive, clear the check box.

7. To add or remove a group of four sockets, select either Add or Remove.

Up to 32 socket selector positions can be used.

More information on how a configuration is addressed and assigned to a Virtual Station is given in the Virtual Station section .

# Socket Selector Control Switch

The Control switch has two positions:

Position | Description
--- | ---
Auto | The controller controls the LED lamps on the Socket Selector, which guide the operator to the correct socket selection.
External | The controller has no control of the socket selector. All functionality of the LED lamps is controlled by an external control system through the Open Protocol communication or by the Fieldbus module.

# Stacklight

The Stacklight provides long distance visual communication from the controller to the operator. In addition to the lights, the accessory can be equipped with a button, key switch, buzzer and I/O connections.

The Stacklight is connected to the controller using the I/O bus. Multiple accessories can be connected on the I/O bus. Read the Stacklight documentation for address configuration and specifications of the connections.

How to assign an accessory configuration to a Virtual Station is described under the Virtual Station icon .

# Scanner

The Scanner is an accessory, it is installed directly to the controller via a USB cable.

In the Scanner configuration it is possible to configure the Pass through as On or Off. As default the configuration is Off. When Pass through is activated (set to On), the scanned barcode information is sent to either SoftPLC, or Fieldbus for decoding.

1. In the Plant structure workspace , select a controller.

2. In the tab menu bar in the workspace area, select the Configurations icon .

   The workspace area displays a list of configurations.

3. Double-click on a configuration row that has Scanner in the Type column.

   Alternatively, select Add to create a new scanner configuration.

Scanner options
Parameter | Description
--- | ---
Name | Optional name for the configuration
Description | Optional configuration description
Pass through = On | The scanned barcode is sent to either SoftPLC, or Fieldbus to be decoded
Pass through = Off | The scanned barcode is decoded in the controller

# Indicatorbox

The Indicatorbox is a flexible display indicator used to display status signals from the controller. The display is equipped with 20 dual color LEDs, these are mounted in a square with five LEDs at each side.

In this Section

- Configuring the Indicatorbox

# Configuring the Indicatorbox

Adding an LED configuration

1. Select Indicatorbox in the Configurations menu.

2. To add an LED click on the Add button.

3. Select LED letter in the Position box according to the illustration.

4. Select signal for red and green LED.

To remove an LED, select the LED and click on the DELETE button.

# Tool Configuration

# Tool Configuration - Properties Menu

The Tool configuration should be given a unique name. An optional description field is also available.

The accessory configuration list displays all configurations in an alphabetical order

To view or edit a tool configuration menu:

1. Select a controller in the Plant structure workspace .

2. Select the Configurations icon in the menu bar.

   The workspace area shows a list of all the current accessory configurations.

3. Double-click on the name of the selected Tool configuration.

   The workspace area shows the details of the current configuration and is divided into different menus, one for each topic.

4. Enter a configuration name and a description in the Properties menu.

5. Select a tool type from the Filter by tool type drop-down menu.

   As the number of tools grows, the number of menus grows as well. To increase the visual comfort in the workspace, it is possible to filter menus and only show what is relevant for one selected tool type. The filter is set in the Properties menu. If No tool is selected, all the possible tool configuration parameters are displayed.

# Tool Configuration - General Configuration

Inactivity timeout | Description
--- | ---
On | Only valid for battery tools. In order to save battery time there is an option to automatically turn off the tool after a certain time of inactivity. Enter a value between 1-1440 minutes.
Off | The tool will not be turned off due to inactivity.

Front LED | Description
--- | ---
Front LED enabled | Wireless tools: Off - Tool Front LED will always be off. On - Front LED is lit when the tool trigger is pressed, plus time set in Front LED duration starting at trigger release. Cable tools: The front LED is lit for 10 seconds after the tool trigger has been pressed.
Front LED duration | Wireless tools: Front LED duration in seconds, starting when the tool trigger is released.

Use Start source to set how to start the tool.

Start source | Description
--- | ---
Trigger only | Press the tool trigger to start the tightening.
Trigger OR Push | Press the tool trigger or push the tool against the joint to start the tightening.
Trigger AND Push | Press the tool trigger and push the tool against the joint to start the tightening.
Push only | Push the tool against the joint to start the tightening.
Digital input | Using an external digital input signal to trigger the start of the tightening.
Safety trigger | Applicable only on tools that have two triggers. The two triggers must be pressed simultaneously to start a tightening or loosening. Both triggers must be released between consecutive tightenings.

Use Trace start to set how to start the tightening trace.

Trace start | Description
--- | ---
Off | No data tracing.
Trigger pressed | Data tracing of the tightening process starts as soon as the trigger is pressed.
Rundown complete | Data tracing of the tightening process starts when the Rundown complete is detected.

The Start request switch defines the action when communication between tool and controller is lost.

Start request enables the requirement of having a connection between the tool and the controller, for all battery tools. This to make sure that the tool is always up to date with tightening program or batch settings, and with other settings on the controller, when performing tightenings.

When Start request is set to On, the tool becomes locked if the controller connection is lost. This means that if the tool loses connection in the middle of a tightening or a batch sequence, the tool will finish the ongoing tightening and then stop. The tool will be locked until the connection is re-established.

Start request | Description
--- | ---
On | The current Tightening program is finished and subsequent tightenings are stopped when the connection is lost between the controller and the tool.
Off | Current Tightening program or Batch can be finished even if the connection is lost between controller and tool.

The TAG number is the RFID TAG which is used to identify the end-fitting tool in the STwrench. The following options are available:

TAG check | Description
--- | ---
On | Check the TAG number of the End-fitting tool (socket). The TAG number must be identical to the number in the Tightening program configuration.
Off | No TAG checking is done.

TAG selection | Description
--- | ---
On | Use the TAG number of the End-fitting tool (socket) to select a batch in a batch sequence. The TAG number must be written into the identifier number field in the Sequence configuration menu in the batch sequence section .
Off | The TAG value is not used to select a batch.

Lock tool on memory full gives the tool the possibility to perform tightenings even when the tool memory is full. This means that the tightenings performed when the tool memory is full will never be reported to the controller.

Lock tool on memory full | Description
--- | ---
On | The tool will be locked from further tightening operations when the tool memory is full. In order to resume tightening operations the tool has to reestablish connection to the controller and send the tightening results that have been stored in the tool memory.
Off | The tool will continue to perform tightenings even when the tool memory is full.

# Tool Configuration - Direction Switch

The Direction Switch on the tool can be configured to trigger one input signal when quickly switched from clockwise (CW) to counter clockwise (CCW) and back, or vice versa.

1. Select a controller in the Plant structure workspace .

2. Select the Configurations icon in the menu bar.

   The workspace area shows a list of all the current accessory configurations.

3. Double-click on the name of the selected Tool configuration.

4. In the Direction Switch field, select the required signal from the Input drop-down list.

# Tool Configuration - Function Button

Use the tool's Function Button to control up to six of the available input signals. The buttons have three possible condition states that are combined with the two possible states of the direction switch.

Function button states | Direction switch states
--- | ---
Pressed | CW
Single push | CW
Double push | CW
Pressed | CCW
Single push | CCW
Double push | CCW

Two configurable parameters controls the push time.

Parameter | Description | Default value
--- | --- | ---
Push detection interval (ms) | For single push: the maximum push time (in milliseconds) between the button being pressed and the button being released. | 300 ms
Next push interval (ms) | For double push: the maximum time (in milliseconds) between the button being released after the first push, and the button being pressed again. | 300 ms

# Tool Configuration - Tool LEDs

The tool LED's can be used to signal different messages to the operator.

Configuring the LEDs

1. Select a controller in the Plant structure workspace .

2. Select the Configurations icon in the top-side menu bar in the workspace area.

   The workspace area displays a list of configurations.

3. Double-click on a configuration row that has Tool configuration in the Type column.

   Alternatively, select Add to create a new configuration.

   The workspace shows all the tool configuration menus.

4. Perform the relevant configurations. The configurations are auto saved in ToolsTalk 2.

## The tool LEDs have the following features

- The front LED illuminates the work area and can be used to indicate the result status for supported tools.

- The blue LED is part of the tool LEDs or as part of the EHMI or RHMI for supported tools. An output signal can be connected to the blue LED.

- The status LEDs consist of a red, a yellow, and a green ring or a segmented multicolor ring on specific pistol tools. Output signals can be connected to the status LEDs.

- A result indicator configures how the tool LEDs are lit to indicate tightening results status and the duration of this indication in supported tools.

An output signal can be of the type event or state.

A state signal is active as long as the output signal is active.

An event signal is active during the configured time range.

## Blue LED

The blue LED can be configured with an event or state output signal. The signal status would be displayed with a steady light.

To configure the blue LED

- Select a signal to connect with the blue LED.

- Optional: set the duration of an event signal.

The blue LED is replaced by or complemented with a blue indication on the EHMI or RHMI for specific tools types.

## Result Indicator

The result indicator configures how the tool LEDs are lit to indicate tightening results status and the duration of this indication.

The configuration affects the front LED and status LED result indication on supported tools. This includes pattern and duration. If pattern is set to Off, the result indication will not be used, even if Front LED is set to On in the Tool Configuration view.

Front LED must be set to On in the Tool Configuration view to use front LED result indication on supported tools.

Front LED supports the green and red color. Patterns that use the color yellow will not display yellow on the front LED.

Result indicator signals
Signal | Description
--- | ---
Off | No LEDs are activated after the tightening, regardless of the result.
Green | The green light always turns on when a tightening operation is OK.
Red:high:yellow:low | If the tightening is terminated incorrectly (NOK); a red LED indicates that the final value is too high, or a yellow LED indicates that the value is too low. Red and yellow can be lit simultaneously (e.g. in case of too high torque, and too low angle).
Red:high(prio):yellow:low | If the tightening is terminated incorrectly (NOK); a red LED indicates that the final value is too high, or a yellow LED indicates that the value is too low. Red and yellow cannot be lit simultaneously. Only red is lit in case of simultaneous high and low values.
Red:NOK:yellow:low | A red LED indicates that the tightening is terminated incorrectly (NOK). An additional yellow LED can indicate if the value is too low.
Red:NOK | A red LED indicates that the tightening is terminated incorrectly (NOK). No additional LEDs are shown.

## Status LEDs

The status LEDs consist of LEDs in three colors: red, yellow, and green. Each light can be steady or flashing. This offers a total of six different signals that can be connected to the status LEDs.

To configure the status LEDs

- For each color and function, steady or flashing, select an output signal from the shortcut menu.

- Optional: set the duration of an event signal.

Status LED signals and result indications can not simultaneously be displayed on the tool. The following conditions apply:

- A LED is turned on by a configured signal only when no tightening is ongoing and when the controlling output signal is activated.

- A LED is turned off when the next tightening is started, even if the configured duration hasn’t been reached for an event type signal or the controlling output signal hasn’t been deactivated for a state type signal.

- A result indication on the status LEDs will be deactivated if an update, activated or deactivated, is made to a configured signal.

## Duration

The duration decides for how long the result indication will be lit after the trigger is released.

Parameter | Description
--- | ---
To next tightening | The blue LED, the status LEDs, and the result indication are on until the next tightening is started.
Time | The blue LED is on for the configured duration after activation. The status LEDs are on for the configured duration after activation or until the start of the next tightening. The result indication is on for the configured duration after the trigger is released or until the start of the next tightening.

# Tool Configuration - Buzzer

The Buzzer can be configured to emit different sounds. Output signals can be mapped to each of the signals and provides an audio interface to the operator.

The Buzzer is located on the tool and is configured as a tool accessory.

Command | Description
--- | ---
Add | Add a new sound configuration to the table.
Delete | Remove one or more selected sound configurations.

Up to 20 different signals can be mapped to a sound and each sound can have its own characteristic profile, with parameters described in the table below.

Parameter | Description
--- | ---
Check box | Selects a row in the table.
Signal | Select a signal that triggers the sound.
Frequency | Exact frequency in Hz.
Time on | Time (in ms) that the buzzer emits a sound.
Time off | Time (in ms) that the buzzer is quiet.
Repetition | Number of times the buzzer repeats the on/off sequence.
Volume | The buzzer volume, in percentage of max volume.
Priority | 10 different priority levels are available for the sounds where one (1) is the highest priority level. Default priority level is five.

For two simultaneous signals, the signal with highest priority overrides the other signal.

A buzzer signal runs until termination and is not interrupted by a higher prioritized signal.

# Configuring the Tool Accessory Bus

The optional tool accessories can be factory installed or be installed at a later stage. The accessories are connected to a Tool Accessory Bus. They have small displays as outputs, and buttons as inputs. The functionality is configured from the controller GUI, the web GUI or the ToolsTalk 2 GUI.

The hardware installation of a tool accessory is described in the accessory documentation and in the tool's specific documentation. The configuration parameters that can be accessed from ToolsTalk 2 are described in this documentation.

1. Select a controller in the Plant structure workspace .

2. Select the Configurations icon in the top-side menu bar in the workspace area.

   The workspace area displays a list of configurations.

3. Double-click on a configuration row that has Tool configuration in the Type column.

   Alternatively, select Add to create a new tool configuration.

4. Double-click on a configuration to open the selected configuration menu.

   The Accessory bus menu shows the possible accessories that can be configured.

5. Double-click on the selected type to open a shortcut window for the configuration.

Accessory bus configurations
Type | Description
--- | ---
ST selector | A small display and buttons; used to select tasks or programs according to the configuration.
TLS tag | Tool Location System tag; used to provide output signaling to the operator.
EHMI | A small display and buttons; used to select tasks or programs according to the configuration.
Scanner | Installed on the tool and connected to the tool accessory bus. It has one function button that activates the Scanner.

In this Section

- Configuring the Tool Location System Tag (TLS)
- Configuring the Extended Human Machine Interface (EHMI)
- Configuring the ST Selector

# Configuring the Tool Location System Tag (TLS)

The Tool Location System (TLS) tag, is a tool accessory. The TLS tag is installed on the tool and connected to the tool accessory bus. The TLS tag is part of the Ubisense positioning system and is handled independently from the controller. In addition to the positioning, the TLS tag can be used to provide information to the operator. Selected output signals can generate different LED light combinations.

1. Select a controller in the Plant structure workspace .

2. Select the Configurations icon in the top-side menu bar in the workspace area.

   The workspace area displays a list of configurations.

3. Double-click on a configuration row that has Tool configuration in the Type column.

   Alternatively, click the Add command button to create a new Tool Configuration.

4. Double-click on the TLS Tag in the Accessory bus menu, to open a shortcut window for the configuration.

5. Make the selected configurations. The configurations are auto-saved in ToolsTalk 2.

Tool location system configuration menu

A | Check box | B | Table header row
C | Table row, with shortcut menus | D | Command button
E | Command button |  |

TLS tag menu command buttons
Command | Description
--- | ---
Add | Add a new configuration to the table.
Delete | Remove one or more selected configurations.
Close | Close the shortcut menu.

Up to 10 different output signals can be mapped to a light priority.

TLS tag configuration parameters
Parameter | Description
--- | ---
Check box | Select a row in the table.
Signal | Select a signal from a shortcut menu, that triggers the LED light. For a signal of the type Event, select the duration of the signal.
Color | Select a color for the LED.
Priority | 10 different priority levels are available for the sounds where one (1) is the highest priority level. Default priority level is five (5).

If there are two simultaneous signals, the signal with the highest priority takes precedence. When two signals with the same priority trigger the LED, the first signal received takes precedence.

An output signal can be of type Event or of type State.

A state signal is active as long as the state is active.

An event signal is active during programmable time.

# Configuring the Extended Human Machine Interface (EHMI)

The EHMI is a tool accessory. It is installed on the tool and connected to the tool accessory bus. It has a graphical display, three function buttons and an optional scanner. The display is a subset of the controller GUI with the possibility to select tightening programs, batch sequences etc. Through the function buttons, the operator can interact with the controller.

In the EHMI configuration, it is possible to configure whether the function buttons should be set to On or Off.

1. Select a controller in the Plant structure workspace .

2. Select the Configurations icon in the top menu bar.

   The workspace area displays a list of configurations.

3. Double-click on a configuration row that has Tool configuration in the Type column.

   Alternatively, select Add to create a new Tool configuration.

4. Double-click on the EHMI in the Accessory bus menu, to open a shortcut window for the configuration.

5. Make the selected configuration. The configurations are auto-saved in ToolsTalk 2.

EHMI buttons
Parameter | Description
--- | ---
Function buttons = On | The buttons have full functionality to configure settings within the visible menus.
Function buttons = Off | The function buttons can only be used to acknowledge a necessary dialog on the EHMI

# Configuring the ST Selector

The ST Selector is a tool accessory. It is installed on the tool and connected to the tool accessory bus. It has a small display, two input buttons and output LEDs.

1. Select a controller in the Plant structure workspace .

2. Select the Configurations icon in the top-side menu bar in the workspace area.

   The workspace area displays a list of configurations.

3. Double-click on a configuration row that has Tool configuration in the Type column.

   Alternatively, select the Add command button to create a new configuration.

   The workspace shows all the tool configuration menus.

4. Double-click on the ST selector in the Accessory bus menu, to open a shortcut window for the configuration.

5. Make the selected configurations. The configurations are auto-saved in ToolsTalk 2.

## Display

The display can show one piece of information at a time and has five different messages that roll in the display with a configurable display time.

ST selector display.
Parameter | Description
--- | ---
Switch time | Select the time to display one message before the next message is displayed.
Page | For each page 1-4, select a message from the shortcut menu that is to appear in the display for the duration of the switch time.

## Buttons

The two buttons can be configured to act upon the displayed information and can be used to step through the listed items.

ST selector buttons
Parameter | Description
--- | ---
Left button | Select one action from the shortcut menu.
Right button | Select one action from the shortcut menu.

## Status LEDs

The status LEDs can be activated or deactivated.

ST selector status LEDs
Parameter | Description
--- | ---
Enable result LEDs | Select the desired On or Off radio button.
Enable extra LEDs | Select the desired On or Off radio button.

The result LEDs which are red, green and yellow, show the same information as the main tools LEDs.

The two extra LEDs can show Batch OK and Batch sequence OK. Both these LEDs are automatically turned off at the next tightening.

# Configuration of the Open End

Before using an open end tool, make sure that the tool head and tool body have been assembled and configured correctly. If not, the tool can run in the wrong direction and the mechanical stop in the open-end head may be damaged.

After performing a tightening with an open end tool, it is possible to let the open end tool getting to the opening position again through the open end configuration.

Configure the open end strategies and settings through the HMI (Human Machine Interface).

The open end configuration is applicable only to cable tools, IXB tools, and STB tools.
The open end configuration is not applicable to Flex and to synchronized tightening.

## Open End Configuration

Open End Settings
Settings | Description
--- | ---
Automatic Positioning | After performing a tightening with an open end tool, it is possible to let the open end tool getting to the opening position again automatically. A toggle key turns the Automatic Positioning On or Off: On: if enabled, after the tightening, when the open end tool is lifted up, the open end tool gets to the opening position again automatically. The operator must hold down the tool trigger during the full process (tightening + Automatic Positioning). If the operator releases the tool trigger before that the Automatic Positioning is completed, the open end tool will get back to the opening position through the selected Positioning Strategy. Off: default value. If disabled, after the tightening, when the open end tool is lifted up, the open end tool does not get to the opening position again automatically. When the open end tool is lifted up, the operator must release the tool trigger. To let the open end tool getting to the opening position again, the operator must hold down the tool trigger again during the full Automatic Positioning. Automatic Positioning is applicable only to Multistep tightening programs. Automatic Positioning is applicable only to cable tools and IXB tools.
Positioning Strategy | Select the Positioning Strategy to let the open end tool getting back to the opening position after the tightening. Forward: default value. The open end tool turns forward - in the same direction of the tightening direction - to the opening position. Reverse: the open end tool turns reverse - in the opposite direction of the tightening direction - to the opening position. Reverse Torque Based: the open end tool gets to the opening position through a slow reverse rotation that is done by reversing slowly and monitoring the torque. Forward Fast Start: the open end tool gets to the opening position as quick as possible. We recommend to use Reverse Torque Based and Forward Fast Start strategies for open end tools with swiveling front part. Reverse Torque Based and Forward Fast Start strategies are applicable only to cable tools and IXB tools. If the Positioning Strategy of the STB tools is Reverse Torque Based or Forward Fast Start, the default Positioning Strategy would run automatically. For Reverse Torque Based, the default Positioning Strategy is Reverse. For Forward Fast Start, the default Positioning Strategy is Forward.
Positioning Speed | Positioning Speed defines how quickly the tool should get to the opening position. Positioning Speed is expressed as the percentage (%) of the open end tool maximum speed. The operator can enter a Positioning Speed value which ranges from 5% through 100%. By default, the Positioning Speed is set to 38%.

# Tool Configuration - Vibrator

Tools equipped with a vibrator can be configured to emit vibrations for different signals.

The vibrator is configured by assigning a vibration pattern to a signal selected from a list. A vibration signal can have a priority between 1 and 10, where 1 is the highest priority and 10 the lowest. By default a signal and vibration have the priority 5.

A vibration signal runs until termination unless it is interrupted by a signal with higher priority.

1. Select a controller in the Plant structure workspace .

2. Select the Configurations icon in the top-side menu bar in the workspace area.

   The workspace area displays a list of configurations.

3. Double-click on a configuration row that has Tool configuration in the Type column.

   Alternatively, select Add to create a new tool configuration.

4. Double-click on a configuration to open the selected configuration menu.

   The Vibrator menu shows if an IXB tool is connected.

5. Set the parameters as applicable:

   Parameter | Description
   --- | ---
   Signal | Select a signal to assign a vibration pattern.
   Priority | 10 different priority levels are available for the vibrations where 1 is the highest priority level. Default priority level is 5.
   On Time | Time (in ms) that the tool emits vibrations.
   Off Time | Time (in ms) that the vibrator is quiet.
   Repeats | Number of times the vibrator repeats the on/off sequence.

# General Virtual Station

Adding a General Virtual Station

1. In the Plant structure workspace , select a controller.

2. In the tab menu bar in the workspace area, select the Configurations icon .

   The workspace area displays a list of configurations.

3. Double-click on a configuration row that has General Virtual Station in the Type column.

   Alternatively, select Add to create a new General Virtual Station configuration .

Properties
Parameter | Description
--- | ---
Name | Optional name for the configuration
Description | Optional configuration description

The non-tightening results can either be reported unfiltered (default), or configured to report a selection of the results. Up to 16 General Virtual Station configurations can be created.

Non-tightening results affected:

- Loosening

- Batch increment

- Batch decrement

- Reset batch

- Bypass tightening program

- Abort batch sequence

- Abort not started sequence

- Reset batch sequence

Relevant Information

- Assigning a General Virtual Station Configuration
- Global Configurations Library - Creating a Global Configuration From An Existing
- Pushing Configurations to a Controller
- Working with the Configurations Tab

In this Section

- Enabling and Disabling the Tightening Settings
- Configuring Live Result Settings

# Enabling and Disabling the Tightening Settings

The General Virtual Station configuration contains a tightening section, which is used to set parameters for Disable tightening and Disable loosening.

1. Select a controller in the Plant structure .

2. Go to the Configurations tab in the menu bar.

   The workspace area displays the available Configurations.

3. Double-click on an existing General Virtual Station to configure, or select Add to create a new one to configure.

4. Make the relevant selections in the Tightening Settings parameters, according to the information in the tables below.

## Unlock tool on loosening settings

Parameter Value | Description
--- | ---
Off | A disabled tool will remain disabled regardless of the loosening status.
On OK | A disabled tool will be unlocked after an OK loosening has been done.
Always | A disabled tool will be unlocked as soon as a loosening has been done, regardless of the loosening status.

## Disable loosening settings

To make sure that a bolt cannot be loosen by mistake there is a function called disable loosening. There are four disable loosening settings:

Settings | Description
--- | ---
Off | Loosening is always enabled. It is always possible to loosen a bolt.
On OK tightening | Loosening is disabled after an OK tightening. It is not possible to loosen a correct tightened bolt.
On NOK tightening | Loosening is disabled after an NOK tightening. It is not possible to loosen a not correct tightened bolt.
Always | Loosening is always disabled. It is not possible to loosen a bolt.

These settings are valid during the execution of a task. Loosening enables and disables depending on the setting and the status of the last tightening. For a new task the start state for disable loosening is set as follows:

Settings | Start state for new task
--- | ---
Off | Loosening enabled. It is possible to loosen a bolt.
On OK Tightening | Loosening disabled. It is not possible to loosen a bolt.
On NOK Tightening | Loosening disabled. It is not possible to loosen a bolt.
Always | Loosening disabled. It is not possible to loosen a bolt.

The start state applies whenever a new task is assigned to a Virtual station or when a task starts again. The start state can differ depending on the type of task, described as follows.

Tightening program and Sync mode

Enable and disable of loosening follows the disable loosening setting and is set to the status of the last tightening.

Batch Sequence

During a batch sequence the enable or disable of loosening follows the disable loosening setting and is set to the status of the last tightening. This also applies when a batch goes to the next one within a batch sequence. If a batch sequence starts again, the loosening is enabled or disabled according to the start state for a new task.

Source Batch

Enable and disable of loosening follow the same procedure as described in Batch sequence. If an ongoing source batch starts again or if a new one is selected, the loosening is enabled or disabled according to the start state for new task.

Source Tightening (No batch control)

During a batch, enable and disable is set according to the status of the last tightening. If another program is selected, enable and disable is set according to the start state for new task. If any change of program, tool or socket is done, enable and disable is set according to the start state for new task.

Multispindle tightening

Enable and disable of loosening always follows the status of the last tightening. This is also applicable for a new sync mode.

## Disable tightening settings

To make sure that an operator does not tighten a bolt by mistake there is a function called disable tightening. There are four disable tightening settings:

Settings | Description
--- | ---
Off | Tightening is always enabled. It is always possible to tighten a bolt.
On OK tightening | Tightening is disabled after an OK tightening. It is not possible to tighten a correct tightened bolt.
On NOK tightening | Tightening is disabled after an NOK tightening. It is not possible to tighten a not correct tightened bolt.
Always | Tightening is always disabled. It is not possible to tighten a bolt.

These settings are valid during the execution of a task. Tightening enables and disables depending on the setting and the status of the last tightening. For a new task the start state for disable tightening is set as follows:

Settings | Start state for new task
--- | ---
Off | Tightening enabled
On OK Tightening | Tightening enabled
On NOK Tightening | Tightening enabled
Always | Tightening disabled

The start state applies whenever a new task is assigned to a Virtual station or when the task starts again. The start state can differ depending on the type of task, as described in the Disable Loosening settings section.

## Allowing a disabled tool to unlock after loosening

1. In the configuration used by the tool (set in the Virtual Station the tool is connected to), set the Unlock tool on loosening to On OK or Always.

   To enable the setting above, the following conditions need to be met:

   1. The Disable loosening parameter cannot be set to Off or Always.

   2. The Disable loosening value cannot be set to the same value as the Disable tightening.

   3. The tightening program used must have loosening enabled.

When the tool is locked for either tightening or loosening due to a disable state, it can be unlocked with one of the following input signals:

- Master_Unlock

- Unlock_Tool_On_Disable

This input signal can be sent to the controller either from an accessory, from a programable tool accessory, or from the Fieldbus unit.

Relevant Information

- Pushing Configurations to a Controller

# Configuring Live Result Settings

The Live Result Settings window allows a user to define if Prevailing torque compensation value is shown in live results section of the controller and if prevailing torque compensation value is part of the final torque result or not.

1. Select a controller in the Plant structure .

2. Go to the Configurations tab in the menu bar.

   The workspace area displays the available Configurations.

3. Double-click on an existing General Virtual Station to configure, or select Add to create a new one to configure.

4. In the Live Result Settings window, set the relevant switches to ON or OFF depending on the wanted results.

   If the Show PrT Compensation Value switch is set to ON, the Live Results window in the controller displays the PrT compensation value.

   If the Show Torque with PrT Compensation switch is set to ON, the Live Results window in the controller displays the final torque with the PrT compensation included.

   Setting the switches in the Live Result Settings window to either ON or OFF has no impact unless:

   - The multistep program has a tightening step including a Prevailing Torque step monitor with the Compensation switch set to ON.

   The Live Result window of the controller shows how the results are displayed. Refer to the respective controller User guide for more information on how the results are displayed depending on if Show PrT Compensation Value and Show Torque with PrT Compensation is set to ON or OFF

# Working with the Controller Information Tab

The menus in the Controller Information tab provide information about a single selected controller.

## Viewing the Controller Information menus:

1. Select a controller in the Plant structure workspace .

2. Go to theController tab.

   The workspace area displays the Controller menus.

In the Controller workspace, the following menus are shown:

Controller information
Menu | Functionality
--- | ---
Controller information | Provides general information about the controller and the IAM module. If the controller sends information or a configuration that is not valid, then an exception along with the parameters affected is displayed as an error message.
Licenses | Provides information about the different license types which have been issued to the controller.
Software | Provides information about the software configuration of the controller.
Hardware | Provides information about the hardware configuration of the controller.
Export / Import | Provides export of controller results and configurations, and import of controller configurations. A dialog box appears to for file location.
Health | Monitors and records environmental parameters and system health parameters.

The information displayed is for information only. No setting of parameters is possible in the menus.

In this Section

- Controller Information and IAM Menu
- Software Menu
- Licenses
- Hardware Configuration
- Export and Import
- Automated Backup
- System Health Monitor
- Server Connection Status

# Controller Information and IAM Menu

The Intelligent Application Module (IAM) is located on the inside of the controller door. It contains the controller program, configuration parameters and stored results.

The IAM module can easily be removed and moved into another controller, which then will behave exactly as the previous controller.

## Viewing the Controller information Menus and Current Configurations

1. Select a controller in the Plant structure .

2. Go to Controller .

   The workspace area displays the Controller menus.

Controller model information
Menu | Functionality
--- | ---
Model | Provides general information about the type of controller.
Serial number | Provides information about the serial number of the controller.
Service Ethernet port | Provides information about the IP address of the service port. Through this port a service engineer can access the controller without being connected to the factory network.

Controller IAM information
Menu | Functionality
--- | ---
Type | Atlas Copco provides different IAM types with different functionality.
Customer key | Is an identifier for application-specific or customer-specific configurations.
Serial number | Provides information about the serial number of the IAM module.

# Software Menu

1. Select a controller in the Plant structure workspace .

2. Go to Controller .

   The workspace area displays the Controller menus.

Controller software version
Menu | Functionality
--- | ---
Current version | The main active working software.
Stored version | A stored inactive software.

It is possible to switch between installed software versions and this has two advantages:

- Controller software can be loaded to controllers in parallel to normal operation. If several controllers are to be updated, a switch can then be made very quickly on all controllers at the same time.

- If a software upgrade results in unexpected results, a switch to the previous version is a quick back-up fix.

Relevant Information

- Introduction to Controller Software and Data Management
- Switching Controller Software
- Updating Controller Software

# Licenses

This field displays the available license types and features that have been issued to the controller.

# Hardware Configuration

This menu provides information about the system hardware configuration.

1. Select a controller in the Plant structure workspace .

2. Go to Controller .

   The workspace area displays the Controller menus.

For a Power Focus 6000 the menu is named Hardware. The information lists the different hardware modules that make up the controller.

For each module, the following data is provided:

- Serial number

- Article number

- Hardware revision number

For more controller hardware descriptions, please look into the Power Focus 6000 documentation.

For a FlexController the menu is named Channels. The information lists the different hardware drives and tools that make up the controller.

# Export and Import

The export and import function is used to export the events and tightening results accessible in the Results menu for analysis in external programs, as well as allowing transfer of tightening program, batch, and controller configurations between controllers.

The command Export can be used for the following reasons:

- Exporting tightening results and events for further processing.

- Exporting log files for debug assistance from an Atlas Copco service engineer.

- Exporting the entire controller configuration that can be used to copy the configuration to another controller.

- Comparing two exported configurations to see differences.

Exporting Controller Information

1. Select a controller in the Plant structure .

2. Go to Controller .

   The workspace area displays the Controller menu.

3. Click the Export button to export one of the following:

   Parameter | Description
   --- | ---
   Export | Exports all controller information.
   Export Configuration | Exports settings and configurations.
   Export Tool Log | Exports logs (tightenings and hardware information) from connected tools. Available for SRB, TBP, STB and QST-M. The export consists of atlas_tool_i.zip and ExportInfo.txt

4. Select the location for saving the export file, click OK.

Importing Controller Information

1. Select a controller in the Plant structure .

2. Go to Controller .

   The workspace area displays the Controller menu.

3. To import controller configurations, click the Import command button.

4. Click Open file. Select the file to import.

   The import file must be a previously exported file.

   When using the import function, all settings for tightening program, batch, accessories, and controller are replaced by the settings from the import file. However, settings for network, PIN, and results and events are not imported.

# Automated Backup

The Automated Backup window enables or disables sFTP export.

By default, Enable sFTP export switch is set to OFF.
When turning ON Enable sFTP export switch, an export file is created 10 minutes after the last configuration change.
If Enable sFTP export switch is set to ON on system startup, an export file is automatically created within 2-3 minutes. The export file is created within 2-3 minutes to reflect changes that might have been done before the system was shutdown.

The old Backup file is deleted before the new Backup file is available.

The data in the exported file include all configurations and settings of the controller.

The sFTP users can retrieve the exported file stored in the following directory of the system: /Export/<export file name>.

A system supporting sFTP is needed.

To retrieve the file sFTP users do not need to use any password.

The username for sFTP users is as follows:

Username | autoexport

# System Health Monitor

The equipment health monitor regularly measures parameters and stores them.

1. Select a controller in the Plant structure workspace .

2. Go to Controller .

   The workspace area displays the Controller menus.

   The Health menu displays environmental data and system health information.

Controller health monitor
Information | Value | Description
--- | --- | ---
Refresh command button | Degree C or F | Reads information from the controller and displays the latest result.
Controller temperature | Degree C or F | Latest temperature recording expressed in month/day/year hour:minute:second.
Battery status | OK/NOK | Monitors the memory and real time clock battery in the controller computer board. Status message NOK, means the battery needs to be changed as soon as possible to avoid loss of data or wrong results. Latest recording expressed in month/day/year hour:minute:second.
History command button |  | Provides a list of monitor readings.

# Server Connection Status

The server connection status shows the connection status of the server. Currently, only the server that is connected to ToolsNet is available.

1. Select a controller in the Plant structure workspace .

2. Go to Controller .

   The workspace area displays the Controller menus.

   The Server Connection Status menu displays the status of server.

Server Connection Status
Information | Description
--- | ---
Refresh command button | Reads information from the controller and displays the latest information.
Configuration | Shows if the configuration is enabled on the controller. To enable the configuration, configure Server connections in Settings on the controller.
Connection | Shows the status of the connections to the server: OK / NOK
Server message | Message from the server.

# Working with the Fieldbus and SoftPLC Tab

The Fieldbus and SoftPLC are located in the Fieldbus and SoftPLC tab, when a single controller has been selected in the Plant structure .

A fieldbus is a communication link between a factory management system (fieldbus master) and a remote node (fieldbus subordinate). A node can be complex, like a controller, but may also be a simple unit, like a sensor or a valve.

The Fieldbus and SoftPLC tab is divided into four sections:

- Overview configuration

- Fieldbus configuration

- Acyclic Data configuration - Only available for Synchronized tightening.

- SoftPLC configuration

Relevant Information

- Fieldbus Requirements

In this Section

- Overview Configuration Tab
- Fieldbus Overview
- Fieldbus Requirements
- SoftPLC Overview
- SoftPLC Requirements
- Fieldbus Configuration Tab
- SoftPLC Configuration Tab
- Controller Fieldbus

# Overview Configuration Tab

# Fieldbus settings

The Connection status can show the following status messages:

Status | Description
--- | ---
Fieldbus_Online | The fieldbus module is online. The communication between the controller and the fieldbus master is active.
Fieldbus_Offline | The fieldbus module is offline. The communication between the controller and the fieldbus master is not active.
Fieldbus_NoModuleInstalled | No fieldbus module is detected in the controller.
Fieldbus_NotConfigured | A fieldbus module is detected in the controller but the module is not configured.
Fieldbus_Initializing | A fieldbus status during reset or as a result when global parameters have been changed. This is a temporary status until a steady status is displayed.

The fieldbus status can also show errors:

Error Code | Description | Action
--- | --- | ---
Fieldbus_ModuleMismatch | Supported module. Parameter mismatch detected. | Contact Atlas Copco to read error log.
Fieldbus_UnsupportedModuleInstalled | Unsupported fieldbus module. | Contact Atlas Copco to read error log.
Fieldbus_ConfiguredModuleNot Installed | Configuration data created. No module detected. | Contact Atlas Copco to read error log.
Fieldbus_Unexpectedconfigurationerror | Mismatch between controller and ToolsTalk 2. | Contact Atlas Copco to read error log.

Changing some global parameters like frame size, fieldbus module address, will cause the fieldbus module to reset.

1. Select a controller in the Plant structure workspace .

2. Select Fieldbus in the Home screen then select the Overview sub-tab.

3. In Fieldbus settings select Fieldbus type from the drop-down menu.

4. Enter the size in bytes of the entire Frame size for both the receive and transmit direction. The value must be an even integer number.

5. Enter the fieldbus type specific parameters.

Relevant Information

- Pushing Configurations to a Controller

In this Section

- Fieldbus Parameters General
- Fieldbus parameters for ProfinetIO and ProfinetIO M40
- Fieldbus parameters for EtherNet/IP and EtherNet/IP M40
- Fieldbus parameters for DeviceNet
- Fieldbus parameters for Profibus
- Fieldbus parameters for CC Link
- Fieldbus parameters for CC Link IE

# Fieldbus Parameters General

Field | Description | Default value
--- | --- | ---
Fieldbus type | Select the fieldbus type from drop-down menu: (For PF8 controllers, only M40 modules are supported.) DeviceNet EtherNet/IP ProfinetIO Profibus CC Link CC Link IE | Undefined
Update interval | Set how often a Process Data Frame should be sent. The value is expressed in milliseconds. Minimum value is 100 ms. |
Lock tool when fieldbus offline | Selection switch On-Off. Determines the action taken by the controller if the fieldbus module loses communication with the fieldbus master (PLC). | Off
Read result handshake | Selection switch On-Off. When turned On, the setting will affect all virtual stations. The signal Read Result Handshake has to be mapped in the fieldbus configuration. Any results produced when there are no results to acknowledge will immediately be sent to the PLC. Results to acknowledge will be put in a queue and when acknowledged it will be cleared and the next result in the queue is sent. The time between the cleared result and the next result in the queue is dependent on the cycle time for the fieldbus set in the general fieldbus settings. If the setting is changed, or if the fieldbus mapping for the virtual station is changed, the results still in the queue will be flushed and not sent to the PLC. | Off
Set by network | Selection switch On-Off. Determines how the fieldbus module communication is configured. On: Communication parameters set automatically in the fieldbus module. Parameters are determined by the network during the initial connection with the far end station. Off: Communication parameters must be entered during the configuration. | Off
Sync on task selected |  | Off
Byte order Cyclic Data | Select which order of bytes is used for the cyclic data: Set by network Intel (little) Motorola (big) | Set by network
To controller | Total receive Process Data Frame. The frame size is a combination of all the virtual station receive frames. The size is expressed in number of bytes. |
From controller | Total transmit Process Data Frame. The frame size is a combination of all the virtual station transmit frames. The size is expressed in number of bytes. |

# Fieldbus parameters for ProfinetIO and ProfinetIO M40

The table below only lists specific parameters for ProfinetIO. For the general parameters, see Fieldbus Parameters General.

Field | Description | Default value
--- | --- | ---
Device name | Name of the device |
Fieldbus node IP address | Format is 0.0.0.0 |
Subnet mask | Format is 0.0.0.0 |
Gateway | Format is 0.0.0.0 |
Max ADI size | Not valid for M40. Choose between the different application data instance sizes to be set as a maximum. Data consistency is only guaranteed for data mapped over one single ADI, that is, if the data to be sent is larger, or broken over two ADIs, data consistency cannot be guaranteed. Setting a maximum ADI size, which is equal to the sent data type size and mapped correctly to the total frame size will guarantee data consistency. The maximum data size to use for sending cyclic data, which must match the data size used in the Fieldbus master. Max size ADIs will be used until less than that size remains to map. For example, If Max ADI size is set as 8 bytes, then that will be used for mapping until less than 8 bytes remain, then 4, 2, 1 bytes will be used to transfer the rest of the data. |

The parameter Device name identifies the fieldbus module on the PROFINET and uses the syntax described in RFC 5890.

Relevant Information

- Fieldbus Parameters General
- Fieldbus Parameters General

# Fieldbus parameters for EtherNet/IP and EtherNet/IP M40

The table below only lists specific parameters for EtherNet/IP. For the general parameters, see Fieldbus Parameters General.

Field | Description | Default value
--- | --- | ---
Fieldbus node IP address | Format is 0.0.0.0 |
Subnet mask | Format is 0.0.0.0 |
Gateway | Format is 0.0.0.0 |

Relevant Information

- Fieldbus Parameters General
- Fieldbus Parameters General

# Fieldbus parameters for DeviceNet

The table below only lists specific parameters for DeviceNet. For the general parameters, see Fieldbus Parameters General.

Field | Description | Default value
--- | --- | ---
Fieldbus node address |  |
Baud rate | Speed of the communication link. Select speed from the drop-down menu. 125 kbps; 250 kbps; 500 kbps, Automatic. | Automatic
Connection mode | Select the type of communication between the fieldbus master (PLC) and the subordinate controller. Select from a drop-down menu: Polled Bitstrobe Change of state | Polled

Relevant Information

- Fieldbus Parameters General
- Fieldbus Parameters General

# Fieldbus parameters for Profibus

The table below only lists specific parameters for Profibus. For the general parameters, see Fieldbus Parameters General.

Field | Description | Default value
--- | --- | ---
Sync on task selected | If enabled the fieldbus frame shall be Re-synced at task changes |
Extended mode | Chooses between the backward compatible152 bytes data mode and the 368 bytes data mode: On: 368 bytes data mode. Off: 152 bytes data mode. |
Fieldbus node address |  |
Max ADI size | Not valid for M40. Choose between the different application data instance sizes to be set as a maximum. Data consistency is only guaranteed for data mapped over one single ADI, that is, if the data to be sent is larger, or broken over two ADIs, data consistency cannot be guaranteed. Setting a maximum ADI size, which is equal to the sent data type size and mapped correctly to the total frame size will guarantee data consistency. The maximum data size to use for sending cyclic data, which must match the data size used in the Fieldbus master. Max size ADIs will be used until less than that size remains to map. For example, If Max ADI size is set as 8 bytes, then that will be used for mapping until less than 8 bytes remain, then 4, 2, 1 bytes will be used to transfer the rest of the data. |

Relevant Information

- Fieldbus Parameters General
- Fieldbus Parameters General

# Fieldbus parameters for CC Link

The table below only lists specific parameters for CC Link. For the general parameters, see Fieldbus Parameters General.

Field | Description | Default value
--- | --- | ---
Baud rate | Speed of the communication link. Select speed from the drop-down menu. 156 kbps; 625 kbps; 2500 kbps; 5 Mbps; 10 Mbps. | 156 kbps
Fieldbus node address | A unique address for each separate unit within the network |
Version | Version 1: By default, the module automatically calculates the required number of Occupied Stations based on the mapped Process Data. Version 2: By implementing the Network Settings in the CC-Link, it is possible to customize the implementation for CC-Link Version 2 and use larger data sizes through Extension Cycles. |
Occupied stations | A parameter setting which is dependent on which Version has been chosen. This is used in combination with the Extension Cycles parameter. |
Extension cycles | Parameter setting used for sending larger data sizes, used in combination with the Version and Occupied Station parameters. |

Relevant Information

- Fieldbus Parameters General
- Fieldbus Parameters General

# Fieldbus parameters for CC Link IE

The table below only lists specific parameters for CC Link IE. For the general parameters, see Fieldbus Parameters General.

Field | Description | Default value
--- | --- | ---
Station number | Each device on the network must be assigned a unique Station Number. |
Network number | The network can be segmented into several parts, each with a unique network number that is used for addressing. |

Relevant Information

- Fieldbus Parameters General
- Fieldbus Parameters General

# SoftPLC settings

## Size

The inbound and outbound size allotted in the fieldbus for the PLC can be set in the To controller and From controller fields.

If the fieldbus for the PLC is not configured, the framesize will display 0 for both inbound and outbound size.

## Offset

The order between fieldbus maps can be changed manually and the spacing between fieldbus maps can be controlled. Both of these two functions are controlled by the Offset parameter. This value defines the starting position of a fieldbus map in the Process Data Frame array.

In this Section

- Changing the Offset

# Changing the Offset

1. In the To Controller section, type the offset of the fieldbus map within the Process Data Frame.

2. In the From Controller section, type the offset of the fieldbus map within the Process Data Frame.

Validation is done automatically. If the new offset value is accepted, it is shown in black text. If the value is not accepted an error message is shown in red text which provides information about which offset rule that is violated.

The start address must be an even number.

# Fieldbus Virtual Station Mapping Configuration

A virtual station in a controller and the fieldbus master communicate by exchanging a fieldbus map between each other.

One or more fieldbus maps are combined into a Process Data Frame, which is sent on the physical communication link between the controller and the fieldbus master.

Fieldbus Virtual Station Mapping Configuration
Column | Function
--- | ---
Check box | Select or deselect a mapping.
Virtual station | Name of virtual station.
Fieldbus configuration | The fieldbus map.
To/From controller offset | Starting point of the fieldbus map within the Process Data Frame.

Relevant Information

- Pushing Configurations to a Controller

# Viewing a Fieldbus Map assigned to a Virtual Station

To view how a fieldbus map is assigned to a virtual station:

1. Select a controller in the Plant structure workspace .

2. Select the Fieldbus and SoftPLC tab then select the Overview sub-tab.

The Fieldbus Virtual Station Mapping Configuration menu displays a list of fieldbus maps, and to which virtual station they are assigned. The To Controller Offset column points to the address in the Process Data Frame where the fieldbus map starts.

# Assigning a Fieldbus Map to a Virtual Station

Assigning a fieldbus map to a virtual station and placing it into the Process Data Frame:

1. Select a controller in the Plant structure workspace .

2. Select the Fieldbus and SoftPLC tab then select theOverview sub-tab.

3. Select Add in the Fieldbus Virtual Station Mapping Configuration menu.

   The Add fieldbus mapping dialog window opens.

4. Select a Virtual station.

5. Select a Fieldbus configuration.

6. Select Add, the dialog window closes and the configuration is added.

7. Repeat steps 3-6 as many times as needed.

Fieldbus maps are placed into the Process Data Frame in the order that they are assigned to a virtual station, or at the lowest possible entry point where the Fieldbus map can fit.

# Automatic Placement of Items in the Fieldbus Map

Items are placed automatically in the Fieldbus map. It is possible to change the order later by editing the Fieldbus window.

The following methods are used:

- Items are placed in the order in which they are added to in the Fieldbus map, within the Fieldbus virtual station mapping configuration menu in Fieldbus and SoftPLC .

- An item is placed at the lowest possible location with regards to byte, bit and length position.

- If the item cannot fit in between existing items, the next free position in the array is tried.

- If an item is deleted from the Fieldbus map, a gap will be created. When a new item is added, the placement algorithm will try to fill the gap.

- If ToolsTalk 2 detects any violation of the placement rules. An error indicator will appear and indicate the error location. By placing the mouse cursor over the error indicator, more information about the rule violation is displayed.

# Automatic Placement of Fieldbus Maps in the Process Data Frame

A Fieldbus map is placed automatically in the Process Data Frame when it is assigned to a virtual station. It is possible to change the order later by editing the Offset position in the Fieldbus virtual station mapping configuraiton menu in the Fieldbus and SoftPLC tab.

The following methods are used:

- A Fieldbus map is placed in the order in which they are assigned to in the Process Data Frame.

- Each map starts with an Offset value from the beginning of the frame.

- A map is placed at the lowest possible location, just above the previous map or with offset zero for the first map.

- If a map is deleted from the Process Data Frame, a gap will be created. When a new map is assigned to a virtual station, the placement rule will try to fill the gap.

- If the map cannot fit in between existing maps, then the next free position in the array is tried.

The offset value may be changed manually in the Settings window. Care must be taken that Fieldbus maps do not overlap.

If ToolsTalk 2 detects any violation to the placement rules, an error indicator will appear beside the offset parameter. This indicates that maps overlap or that the map is outside the boundary. This may be corrected by changing the offset value.

A | Starting position of first Fieldbus map in the Process Data Frame; Offset = zero
B | Starting position of a Fieldbus map in the Process Data Frame; Expressed as an offset from the beginning of the PDF
C | Size of a Fieldbus map
D | Fieldbus map
E | Size of the Process Data Frame
F | Error example; Blue map overlaps starting position of “green” map
G | Map size
H | Starting position of “blue” map
J | Process Data Frame
K | First map in the Process Data Frame; Offset address is zero

# Fieldbus Overview

A typical factory management control system that uses fieldbus communication can look like the figure below when it communicates with a controller.

Fieldbus communication system

A | Fieldbus master (PLC) | B | Frame header
C | User data to and from several virtual stations inside the Process Data Frame | D | Virtual station
E | Controller vith multiple virtual stations |  |

A fieldbus master, normally a PLC, exchanges information with a number of remote nodes which are called fieldbus subordinates. The master communicates with one subordinate at a time. The master transmits a frame to the subordinate and receives another frame in response.

The PLC transmits data to a anybus module which then communicates to the controller that may contain identification data, task selection information and other signals.

A controller sends responses to the PLC through the anybus module that may contain event signals, status signals, tightening results and other signals.

The update frequencies of the process data may differ. The update frequency between the controller and the anybus module is around 100Hz and the update frequency between the anybus module and the PLC is around 500Hz.

The physical transmission link depends on the selected fieldbus type. A transmission consists of a Frame Header, containing address information, and a Process Data Frame, which contains all the data.

If the controller supports virtual stations, it is important to direct the correct information to each virtual station. The Process Data Frame may contain one or more Fieldbus maps, one for each virtual station.

In this Section

- Fieldbus Configuration Parameters
- Fieldbus Definitions

# Fieldbus Configuration Parameters

An item is placed into the Fieldbus Map by defining the position of the least significant bit. This position is identified by a byte number and a bit number.

Item position
Information | Description
--- | ---
Starting byte | The byte number in which the least significant byte of the item is located. A numeric number in the range from zero to size minus one. The numbering starts from zero (0). The least significant byte or bit is number 0.
Starting bit | The bit number in which the least significant bit of the item is located. Starting from the previous selected starting byte. A numeric number in the range from zero to seven. The numbering starts from zero (0). The least significant byte or bit is number 0.
Length | A numeric value representing the number of bits in the item.
Range | Information only. Provides information of minimum length, the maximum length and the default length of the selected item.
Converter | A drop-down list of available signal converters. This is used if the SoftPLC has any requirements on how items are represented in a digital format.

The item converters are used to convert items between different data types.

Item converters
Information | Description
--- | ---
Boolean inversion | Inverts the digital signal from active high (1) to active low (0).
Fixed-point |

# Fieldbus Definitions

An Item is a digital signal. It can for example be signals, as they are described in the controller reference section:

- A single bit of information, like Tightening OK.

- Several bits of information, like an Event code.

An Item can be several bits of information representing a counter value, an identification number or a tightening result.

An Item can be a string of characters.

Fieldbus items
Information | Description
--- | ---
Fieldbus Item | Boolean: The signal can be a simple boolean expression, occupying one single bit position. Examples are digital IO signals.
Integer: The data occupies one or more bits of data in the array.
Character or string: The signal can be a alphanumeric character string, occupying one or several byte positions.

Fieldbus definitions
Information | Description
--- | ---
Fieldbus Map | An array of data. The Size must be an even number of bytes. The fieldbus map is created in the Fieldbus window in the Fieldbus menu. Fieldbus items are placed in the fieldbus map to create a unique array for the master-subordinate communication. Items are placed into the array by defining the starting position and the length, expressed in number of bits.
Process Data Frame | An array of data. The size must be an even number of bytes. The Process Data Frame is created in the Fieldbus window in the Fieldbus menu. Fieldbus maps are placed into the Process Data Frame when they are assigned to a Virtual Station. The position of the map within the frame is defined by the Offset, which is calculated from the beginning of the frame.
Fieldbus Configuration | Fieldbus mapping configurations are done in the Fieldbus window in the Fieldbus menu. Configuration parameters consist of both common parameters and type specific parameters. A list of parameter entry boxes are displayed after the fieldbus type has been selected.

Filedbus item positions
Information | Description
--- | ---
Offset | A pointer variable. The signal can be a simple boolean expression, occupying one single bit position. Examples are digital IO signals.
Starting Byte | A pointer variable. Points to a byte within the fieldbus map that contains the LSB of an item.
Starting Bit | A pointer variable. Points to a bit in the previously defined byte within the fieldbus map that contains the LSB of an item.
Item Length | A size variable expressed in a number of bits.
LSB | Least Significant Bit or Byte.

Name | Description
--- | ---
Fieldbus Transmission | A datagram sent over the network. The transmitting node combines a Frame Header, containing address information, with a Process Data Frame that is sent to the network. The receiving node detects its address in the Frame Header and retrieves the Process Data Frame.
Frame Header | Network address information and other data to ensure an error free transmission over the network
Fieldbus Master | Typically a PLC that initiates the communication to a fieldbus subordinate. The master transmits a data frame and receives another frame from the subordinate.
Fieldbus Subordinate | A remote node responding to a transmission from a fieldbus master. When the subordinate detects a transmission, it receives a frame and responds by sending another frame in return to the sender.

# Fieldbus Requirements

For correct fieldbus communication, the following installations and configurations must be made. This is done in the Fieldbus and SoftPLC tab.

- A fieldbus module is installed on the controller.

- Common fieldbus parameters set in the menus in the Overview sub - tab.

- Signal configurations are created in the Fieldbus sub-tab, which are then mapped in the Fieldbus Virtual Station Mapping Configuration menu in the Overview sub - tab.

- Items mapped into fieldbus maps in the Signal Configuration menu, located in the Fieldbus sub - tab.

- Fieldbus maps assigned to virtual stations and placed into the Process Data Frame in the menus in the Fieldbus and SoftPLC tab.

# SoftPLC Overview

The SoftPLC is used to customize the behavior of the controller, sending and receiving fieldbus data, or exchanging I/O signals to and from the external SoftPLC. The external SoftPLC is used for control of machinery on assembly lines. Configuration and programming is done through a third party software called MultiProg, integrated with ToolsTalk 2, though running in a process of its own. The SoftPLC is found in the Fieldbus and SoftPLC tab and is visible for controllers supporting this function either by license and/or capability.

Controller features, such as the Low Reaction Tightening Strategies and controller-wide functions among others, require licenses distributed through the Functionality Management System (FMS). Whereas configuration of features is possible without specific licenses, the assignment and use of those features will require the correct license to be installed on the controller. Please refer to Licenses (FMS) for more detailed information on licenses.

Relevant Information

- Pushing Configurations to a Controller

# SoftPLC Requirements

- The external SoftPLC configuration program, MULTIPROG 5.51 must be installed on the same computer as the ToolsTalk 2 client.

- The SoftPLC must be set to On in the General SoftPLC settings, in order to run SoftPLC programs. On is indicated with status Running or stopped in the SoftPLC Status column. When in running mode, the SoftPLC process is active and ready to start or stop a SoftPLC program from Multiprog. A running SoftPLC program updates its values every 100 ms.

- If a fieldbus is be used via SoftPLC:
  Byte allocation for inbound and outbound SoftPLC signals can be done in the SoftPLC Settings section. This is located in the Overview sub-tab in the Fieldbus and SoftPLC tab.
  If there already is a SoftPLC project for the controller, select the Fieldbus and SoftPLC tab and then select the SoftPLC sub-tab. In the Project area, select Open to open the Multiprog. Update SoftPLC framesize in fieldbus by selecting the Update button. Do this to see the Fieldbus settings that are updated in Multiprog.

## Multiprog

Multiprog is the application where the actual SotPLC program is created and edited. When creating an initial project for a controller, variables and function blocks are created depending on the current setup of the controller and its capabilities. The templates will serve as a basic suggestion which can be further adjusted.

# Fieldbus Configuration Tab

1. Select a controller in the Plant structure window .

2. Select the Fieldbus and SoftPLC tab in the menu bar.

   Select the Fieldbus sub-tab to show the list of maps or to create a new fieldbus map.

Column | Description
--- | ---
| Check box.
Name | Name: Shows the name of the map. The name is identical for both the receive map and the transmit map.
Size to | The size of the receive map to a virtual station. The value must be an even number of bytes.
Size from | The size of the transmit map from a virtual station. The value must be an even number of bytes.
Library link | Linked to global library Yes/No.
Last changed | When were the last changes made, expressed in ToolsTalk 2 time.
Changed by | Who made the last changes.
Controller updated | Controller updated, expressed in controller time.
Controller updated by | Who updated the controller.

In this Section

- Creating a New Fieldbus Map
- Importing a Fieldbus Map
- Deleting a Fieldbus Map
- Creating a Fieldbus Signal Configuration
- Editing or Viewing an Item in the Fieldbus Map
- Deleting Items From the Fieldbus Map
- Exporting a Fieldbus Map

# Creating a New Fieldbus Map

1. Select a controller in the Plant structure window .

2. Select the Fieldbus and SoftPLC tab in the menu bar.

   Select the Fieldbus sub-tab to show the list of maps.

3. Select Add to create a new fieldbus configuration or double-click to edit an existing one.

   The Create new fieldbus configuration dialog window opens.

4. Select the New tab.

5. Issue the configuration with a name.

6. Enter the Size to controller parameter. This is the receive size of the data frame to a virtual station, expressed in number of bytes. This value must be an even number.

7. Enter the Size from controller parameter. This is the transmit size of the data frame from a virtual station, expressed in number of bytes. This value must be an even number.

   The transmit frame and the receive frame may have different size.

8. Select Add to continue with the configuration by adding items to the setup.

The map size entered can not be larger than the Process Data Frame.

Relevant Information

- Creating a Fieldbus Signal Configuration

# Importing a Fieldbus Map

A previously exported fieldbus map can be reused as a template and be imported to a controller.

1. Select a controller in the Plant structure window .

2. Select the Fieldbus and SoftPLC tab in the menu bar.

   Select the Fieldbus sub-tab to show the list of maps.

3. Select Add.

   The Create new fieldbus configuration dialog window opens.

4. Select the Import tab to reuse a existing map.

5. Select the Open file command button to open a browser window.

6. Select a file. The file type must be a JSON file. (*.json).

7. Select Open. The browser window closes.

8. Select Add to import the file. This action will also close the pop-up window and the list of maps is updated.

# Deleting a Fieldbus Map

1. Select a controller in the Plant structure window .

2. Select the Fieldbus and SoftPLC tab in the menu bar.

   Select the Fieldbus sub-tab to show the list of maps.

3. For each fieldbus map to be deleted, select the check box in the leftmost column in the fieldbus workspace. Select Manage, then Delete from the drop-down list.

The list of maps is updated.

# Creating a Fieldbus Signal Configuration

In this area, you can create a new fieldbus signal configuration from the controller or to the controller.

1. Select a controller in the Plant structure window .

2. Select the Fieldbus and SoftPLC tab in the menu bar.

   Select the Fieldbus sub-tab to show a list of maps.

3. Double-click on the name of a map to view it or select Add to create a new one.

   The workspace shows the configuration menus.

4. Select the To Controller tab or the From Controller tab in Fieldbus configuration menu.

5. Select Add.

   The Create signal configuration dialog window opens.

6. Select the item name in the list to select the item.

7. Set the item starting position by typing the BYTE number in which the least significant BIT is located.

8. Set the item starting position by typing the BIT in which the least significant BIT is located.

9. Set the Length of the item, expressed in number of bits.

10. Select an optional Converter value from the drop-down menu.

11. Select Add.

12. Repeat step 6-11 for every item to be added.

13. Select Close to terminate the adding operation and to close the dialog window.

If the item is not placed manually into the map, ToolsTalk 2 will try to place the item at the lowest possible position. It is possible to later move the item within the map.

# Editing or Viewing an Item in the Fieldbus Map

1. Select a controller in the Plant structure window .

2. Select the Fieldbus and SoftPLC tab in the menu bar.

   Select the Fieldbus sub-tab to show a list of maps.

3. Double-click on the name of the selected map.

   The workspace shows the configuration menus.

4. Select either the To Controller tab, or the From Controller tab in Fieldbus configuration menu.

5. Double-click the item name in the map table in the Fieldbus configuration menu.

   The Edit item dialog window opens.

6. Edit the item starting position by typing the BYTE number in which the least significant BIT is located.

7. Edit the item starting position by typing the BIT in which the least significant BIT is located.

8. Edit the Length of the item, expressed in number of bits.

9. Edit an optional Converter value from the drop-down menu.

10. Select OK to confirm any changes and to close the dialog window.

The Fieldbus configuration menu is updated in both the map and in the table.

# Deleting Items From the Fieldbus Map

1. Select a controller in the Plant structure window .

2. Select the Fieldbus and SoftPLC tab in the menu bar.

   Select the Fieldbus sub-tab to show a list of maps.

3. Double-click on the name of the selected map.

   The workspace shows the configuration menus.

4. Select the To Controller tab or the From Controller tab in Fieldbus configuration menu.

5. For each item to be deleted from the map, select the check box in the leftmost position in the table of items in the Fieldbus configuration menu.

6. Select Delete .

The Fieldbus configuration menu is updated in both the map and in the table.

# Exporting a Fieldbus Map

The Fieldbus map defines how signal items are placed into the communication frame that is used between a virtual station and a remote location. This map can be exported as a template and be imported and reused by another controller.

1. Select a controller in the Plant structure window .

2. Select the Fieldbus and SoftPLC tab in the menu bar.

   Select the Fieldbus sub-tab to show the workspace and a list of maps.

3. In the leftmost column in the fieldbus workspace, select the check box for the fieldbus map to be exported, and then select Manage followed by Export from the drop-down list.

4. Browse to the desired location and select Save.

The map will be saved as a JSON file (*.json). The exported file can be imported to a different controller.

# SoftPLC Configuration Tab

# Creating a New SoftPLC Project

Select Create New to create a new SoftPLC project. This project will use a basic template as a starting point. This template includes all functions available in Multiprog.

The created and edited project is continuously saved to the local disc when the project is built and stored in Documents > Mp Temp. At ToolsTalk 2 SoftPLC startup, when clicking OPEN, the stored data project is uploaded and used if the SoftPLC project has not been saved to the ToolsTalk 2 server. Then editing can continue.

1. Select Create New. The Multiprog opens automatically.

2. Edit the SoftPLC program in Multiprog and give the project a Name and Description in ToolsTalk 2.

   Add virtual station mappings with I/O signal configurations by selecting Update project virtual stations.

   Add Fieldbus data by selecting Update project fieldbus framesize.

   The fieldbus frame size must be configured to contain a special SoftPLC input/output part to be able to send and receive fieldbus data directly to/from the SoftPLC.

3. Select SAVE to check in the edited project to the ToolsTalk 2 server.

4. Push the changes to the controller.

# Importing a SoftPLC Project Template

New SoftPLC projects can be created from an existing project template. The templates will serve as a basic suggestion which can be further adjusted. The selected project template is then copied, as to not overwrite the original project.

1. Select Import Project and select an existing SoftPLC project.

2. Edit SoftPLC project in the Multiprog.

   Add virtual station mappings with I/O signal configurations by selecting Update in Project Virtual stations.

   Add Fieldbus data by selecting Update in SoftPLC framesize in fieldbus.

3. Select Save to check in the edited project to the ToolsTalk 2 server.

4. Push the changes to the controller.

Select Update in Project Virtual Stations and the SoftPLC virtual station mappings are added or updated to the SoftPLC project, if not already included in the project.

# Creating SoftPLC User Data

The SoftPLC can interact with protocol adapters through a dedicated part of the shared memory.

1. Select Add in the GENERAL SOFTPLC SETTINGS field.

2. In the Create SoftPLC user data window, choose the relevant protocol from the drop-down.

3. Fill in the TO SOFTPLC and FROM SOFTPLC address fields.

4. Select Add.

5. Select SoftPLC ON or OFF.

   - On: If the SoftPLC process is lost the tool will be locked from performing any tightenings.

   - Off: If the SoftPLC process is lost the tool will still be able to perform tightenings.

# Creating SoftPLC Signal Configurations

Interaction between accessories and the SoftPLC is done through exchanging I/O signals.

1. Select Add in the SoftPLC Signal Configurations field to see the list with all supported I/O signals connected to this controller.

2. Clear the irrelevant signals in order to exclude them from the SoftPLC signal configuration (all signals are selected by default).

3. Name the signal configuration list.

The created signal configuration is then available as an option to select from the drop-down list when mapping the signal configurations to the virtual station.

The signals that are not included in a signal configuration (not checked), will still be visible in the SoftPLC configurator Multiprog, but crossed out.

# Controller Fieldbus

ToolsTalk 2 version 2.24 introduces Controller Fieldbus, which differs from a Fieldbus in one way: Controller Fieldbus is intended for controller-wide use and is shared by all Virtual Stations in a controller. Controller Fieldbus lets many Virtual Stations use the same incoming signal. This reduces the amount of required bandwidth, when compared with Fieldbus.

Controller Fieldbus provides a built-in signal-mapping feature by using Virtual Fieldbus. The purpose of Virtual Fieldbus is to map individual signal configurations into logical groups of signal configurations. Virtual Fieldbus provides a point from where Virtual Stations are mapped to signal configurations. A signal configuration can be mapped to many Virtual Fieldbuses, which lets Virtual Stations share the same signal configurations.

In this Section

- Prerequisites to Using Controller Fieldbus
- Creating a Controller Fieldbus Configuration
- Creating a Signal Configuration in the Controller Fieldbus
- Creating a Virtual Fieldbus
- Mapping a Signal Configuration to One or More Virtual Fieldbuses
- Mapping a Virtual Station to a Virtual Fieldbus

# Prerequisites to Using Controller Fieldbus

These prerequisites must be fulfilled to use Controller Fieldbus:

- ToolsTalk 2 version 2.24 or later

- Controller software version 3.13 or later

# Creating a Controller Fieldbus Configuration

1. Select a controller in the Plant structure workspace.

2. Select the Fieldbus and SoftPLC tab then select the Controller Fieldbus sub-tab.

3. Select Add.

   The Create new fieldbus configuration window comes into view.

4. Enter a Name for the new Controller Fieldbus configuration.

5. Enter a Size to controller number. This is the receive size of the data frame to a Virtual Station, expressed in the number of bytes. This value must be an even number.

6. Enter a Size from controller number. This is the transmit size of the data frame from a Virtual Station, expressed in the number of bytes. This value must be an even number.

7. Select Add.

A new Controller Fieldbus configuration is created and displayed.

# Creating a Signal Configuration in the Controller Fieldbus

1. Select a controller in the Plant structure workspace.

2. Select the Fieldbus and SoftPLC tab then select the Controller Fieldbus sub-tab.

3. Select the Controller Fieldbus instance.

4. To add a signal configuration to the Controller Fieldbus, select Add...

   The Create signal configuration window comes into view.

5. Select a signal.

6. Enter data for the signal configuration byte, bit, and length.

7. Select Add.

8. Select Close.

A signal configuration is created.

At this step, red exclamation marks appear next to the signal configuration. This is because the signal configuration is not yet mapped to a Virtual Fieldbus.

# Creating a Virtual Fieldbus

1. Select a controller in the Plant structure workspace.

2. Select the Fieldbus and SoftPLC tab then select the Controller Fieldbus sub-tab.

3. Double-click the fieldbus configuration to which you want to add a Virtual Fieldbus.

4. To add a Virtual Fieldbus to the Controller Fieldbus, select Add... in the Virtual Fieldbus section.

   The Create Virtual Fieldbus window comes into view.

5. Enter a name and select Tab on the physical keyboard.

6. Select Add.

7. Select Close.

A Virtual Fieldbus is created.

At this step, a red exclamation mark appears next to the Virtual Fieldbus. This is because signal configurations are not yet mapped to the Virtual Fieldbus.

# Mapping a Signal Configuration to One or More Virtual Fieldbuses

1. Select a controller in the Plant structure workspace.

2. Select the Fieldbus and SoftPLC tab then select the Controller Fieldbus sub-tab.

3. Double-click the fieldbus configuration to which you want to map a signal configuration.

4. In the Controller Fieldbus view, locate a signal configuration in the data frame. Right-click the signal configuration and select Map to Virtual Fieldbus.

   The Map signal to Virtual Fieldbus window comes into view.

5. Select the Virtual Fieldbuses to which the signal configuration will be mapped.

6. Select Map.

   The signal configuration is mapped to one or more Virtual Fieldbuses.

7. Select Close.

In the Controller Fieldbus view, select a Virtual Fieldbus to see the signal configurations that are connected to the Virtual Fieldbus. The signal configurations are displayed in green color.

# Mapping a Virtual Station to a Virtual Fieldbus

Make sure that the fieldbus size is large enough to contain the Controller Fieldbus that you want to use. Configure these settings in the Size section.

To map a Virtual Station to a Virtual Fieldbus, the Virtual Station mapping mode must be set to Many-to-one.

When the Virtual Station mapping mode is changed an eventual existing Virtual Station mapping configuration is deleted. A deleted mapping can not be restored.

1. Select a controller in the Plant structure workspace.

2. Select the Fieldbus and SoftPLC tab then select the Overview sub-tab.

3. In the Virtual Station mapping configuration section, select a Controller Fieldbus configuration.

4. Enter offsets to/from the controller to plan the fieldbus distribution.

   The offset is graphically displayed in the Fieldbus Distribution section.

5. In the Mappings section, select Add...

6. Select a Virtual Station.

7. Select a Virtual Fieldbus.

8. Select Add.

9. Select Close.

The Fieldbus mapping is seen both in the Overview sub-tab and in the Virtual Station tab. Select the Virtual Station tab to verify the mapping in the Fieldbus Mapping section.

# Working with the Settings Tab

# Preferences

The settings menu contains a preferences section, which is used to select language, torque units and PIN protection of the controller interface.

To set controller preferences:

1. Select a controller in the Plant structure .

2. Go to Settings .

   The workspace area displays the Settings menus.

Parameters for controller preference:

Parameter | Description | Default
--- | --- | ---
Torque unit | Selects the unit in which torque measurement results shall be displayed for this controller in the controller GUI or web GUI. | Nm
Temperature unit | Selects the unit in which temperature measurement results shall be displayed for this controller in the controller GUI or web GUI. | Celsius
Language | Selects the display language for the controller in the controller GUI and web GUI. | English
Startup screen | Selects the controller startup screen at system start. | Home screen
Access via factory port | On/Off. Enables (On) or disables (Off) the communication with the controller. | On
Use PIN | A PIN can be enabled for this controller when accessed through the controller GUI or webHMI (factory network). PIN only applies to users accessing Controller through its GUI or webHMI. User is not locked out from ToolsTalk 2 or from working with (configuring and pushing configuration) the controller from ToolsTalk 2 because of the activated PIN. On: User accessing the controller must use PIN code in order to get write access to the controller. Off: No PIN code is required for user to get write access to the controller. | Off
Use PIN for Service Port | A PIN can be enabled for the controller when accessed through the service port. On: User accessing the controller must use PIN code in order to get write access to the controller. Off: No PIN code is required for user to get write access to the controller. Use PIN for Service Port is enabled only when the Use PIN is set to On. Use PIN for Service Port uses the same Pin codes configured and Inactivity timeout as user going through the factory network. | Off
Pin codes | Select a 4 digit PIN code per added user. Enable/disable user PINs. |
Inactivity timeout | The controller GUI or web GUI is automatically locked after an inactivity timeout. Minimum value is 20s. | 120 s

The Pin codes and the Inactivity timeout are enabled for editing even when the Use PIN is set to Off.

Relevant Information

- Pushing Configurations to a Controller

In this Section

- PIN Settings
- Tool Service Alarms

# PIN Settings

Using a PIN prevents unauthorized usage of the controller or accidental changes. It is possible to have one or many different PIN configurations on the controller and one of the ways of configuring is through the ToolsTalk 2 Software. Users can decide whether or not to activate one or several PIN configurations at the same time. A maximum of ten users can be added to the controller, each with their own PIN.

Each PIN configuration has a PIN code, a user name, a switch for enabling or disabling the user/PIN, and a list of available configurations that the user can access.

When PIN is enabled and the screen is locked, a locked padlock icon is shown at the upper-right corner of the GUI. The user can access and make changes only to the selected configuration(s) without entering any PIN code, and browse the unselected configurations with read-only access only. The unselected configurations are greyed out or disabled.

The screen lock goes automatically on after a certain time of inactivity, configurable by the user.
The minimum value of the inactivity time is 20 sec and the maximum value is 600 sec. The inactivity time is configurable and applies to all PIN configurations.

After a system startup, the controller is locked if the PIN is turned on, regardless of the current inactivity time.

When PIN is activated, a PIN code is required when accessing the controller via:

- The controller GUI

- The web GUI

In this Section

- Configuring the PIN
- Accessing the Controller When Locked By PIN
- PIN Code for Station Setup

# Configuring the PIN

1. Go to the Settings menu, set Use PIN to On.

2. Select PIN CODES.

## Adding PIN Codes for New Users

1. Select Add in the Pin codes dialog window.

2. Enter the username in the Name field.

3. Enter the PIN in the Set PIN field to set the PIN for the user and repeat the same PIN in the Repeat PIN field . The PIN must be a four-digit number in the range 0000–9999.

   The PIN in both fields (Set PIN and Repeat PIN) need to match.

4. select the Enabled check box to enable the PIN code for that user.

   When PIN is enabled, the controller is locked automatically after the configured inactivity time.

   To disable a PIN, clear the Enabled check box for that user.

## Deleting a User/PIN

- In the list of users, mark the check box for each user PIN to delete and select the Delete button.

## Setting Controller User Access

It is possible to configure the enabled PIN code for different functions and features of the controller for a specific user.

1. Select Edit User Group to configure the PIN code for different features for that user.

   The Set Controller User Access window opens up and the top level sections (in a folder format) contain all the features related to it. Select the downward arrow to expand and see all the features available in that section.

   Read access is by default assigned to all users for all the features and programs.

2. Select the check box under the Create & Delete column, against the features for which access needs to be provided for the user.

   Create & Delete provides full write access to the user.

   If you select the check box against the top folder, all the features in that folder also get selected. To de-select a specific feature, expand and clear the check box . If all the features in a folder are not selected then the Check box displays a Dash (-) instead of an X mark.

3. Select Save.

4. Push changes on the controller to enable the PIN configurations.

If a new user with different permissions is added in the controller GUI, then the new user is also visible in the Pin codes dialog window. Select Edit User Group in order to see or modify the access rights for that user.

# Accessing the Controller When Locked By PIN

When accessing the controller with PIN enabled, a prompt asking for the PIN will appear. This is the case whether the controller is accessed via the web GUI, or the controller GUI.

# PIN Code for Station Setup

For a station set up application, if a PIN is enabled on a controller, then it is required to enter the PIN code when accessing the ToolsTalk 2 software for that controller. A dialog window requesting a PIN code is displayed when the user tries to access a controller which has a PIN enabled.

- Enter the PIN in the Enter PIN (Controller PIN) dialog window.

Once the PIN is authenticated, the user can access all the enabled configurations. But if you log off from the current session, it is required to enter the PIN again.

# Tool Service Alarms

The settings menu contains a tool section, which is used to select tool alarms for Service indicator alarm, Tool lock after service alarm and Show calibration alarm

Setting Tool Alarms

1. Select a controller in the Plant structure .

2. Go to Settings .

   The workspace area displays the Settings menus.

Tool alarm parameters
Parameter | Description | Default | Location
--- | --- | --- | ---
Service indicator alarm | Selected in a switch. Turn the alarm On or Off. The alarm is triggered when the service interval is reached. | Off |
Tool lock after service alarm | Selected in a switch. Lock the tool when the service interval is reached. | Off |
Show calibration alarm | Selected in a switch. Triggers the calibration alarm if the tool has not been calibrated within the specified time. Last calibration date can be seen in the Tool menu. Default interval is one year but can be changed from the controller GUI or web GUI. | Off |
Enable oil level supervision |  | Off |
Lock on oil level empty alarm |  | Off |

# Server Connections

# Controller Communication with the License Server

Functionality can be added temporarily or permanently to a controller through the Functionality Management System. The added functionality is managed by a license server. It can be accessed through the controller GUI, the web GUI, or the ToolsTalk 2 GUI.

The address to the server must be configured, this is done in the controller Settings .

To set the communication between the controller and the license server:

1. Select a controller in the Plant structure .

2. Go to theSettings tab.

   The workspace area displays the Settings menus.

3. In the License Server menu, enable or disable the communication by setting the switch to the desired position.

4. If the communication is enabled, set the Server host address.

5. If the communication is enabled, set the Server port number.

6. Click the Sync button to synchronize the functionality management between the controller and the license server.

License server parameters
Parameter | Description | Default | Comment
--- | --- | --- | ---
License server enabled | Enables or disables communication to the license server. | Off |
Server host | The IP address of the server. |  |
Server port | Port number of the server. |  |
Sync | Command button. Synchronizes the licenses with the license server. |  | Visible when the communication is enabled.

The Sync command forces a synchronization between the controller and the license server. Synchronization shall normally occur automatically on a regular basis if the controller is in normal communication with the server. The command button may be used if synchronization has not been performed on a regular basis.

Relevant Information

- Pushing Configurations to a Controller

# Controller Communication with the ToolsNet Server

A controller always sends tightening results to ToolsTalk 2. A controller can also send the results to ToolsNet 8 for further processing. The address to the ToolsNet 8 server must be configured in the controller.

To set the communication between the controller and the ToolsNet server:

1. Select a controller in the Plant structure .

2. Go to Settings .

   The workspace area displays the Settings menus.

3. Go to ToolsNet, enable or disable the communication with the ToolsNet server.

4. If the communication is enabled, set the IP address and port number of the server.

License server parameters
Parameter | Description | Default | Comment
--- | --- | --- | ---
ToolsNet enabled | Enables/Disables communication to the server. | Off |
Server host | ToolsNet server IP address. |  | Communication enabled.
Server port | ToolsNet server port. |  | Communication enabled.

Relevant Information

- Pushing Configurations to a Controller

# Configuring the Remote Logging Connection

To connect a controller to a remote logging server, configure and activate the remote logging settings on the controller:

1. Select a controller in the Plant structure .

2. Go to Settings .

   The workspace area displays the Settings menus.

3. On the Remote Logging section, configure the following parameters:

   Field | Description
   --- | ---
   On/Off | Enables/Disables communication with the remote logging server
   Protocol | Selects TCP or UDP protocol
   Server host | Remote logging server IP address
   Server port | Remote logging server port

4. Select the applicable log level(s) for each facility:

   Log level | SysLog classification
   --- | ---
   Error | Alert, Critical, Emergency, Error
   Warning | Warning
   Info | Informational, Notice

5. Select Set to apply the configurations on the controller.

# Controller Date and Time

Each controller must have the date and time programmed for accurate reporting.

1. Select a controller in the Plant structure workspace .

2. Go to the Settings tab.

   The workspace area displays the General settings menus.

3. Select the source for the time reference.

4. Enter additional parameters, depending on the selected time source.

5. Select the controller's local time zone from the Time zone shortcut menu.

To achieve best time accuracy and stability it is recommended to use the NTP server that can communicate with all controllers.

The time source is selected from a shortcut menu, and can be one of the following:

- Manually enter time and date into the controller. This can be done through all GUI interfaces.

- Using the standardized Network Time Protocol (NTP). A server distributes time references to connected controllers. It is possible to configure up to two different NTP servers.

- Using the ToolsNet server as the time reference, if the controller is connected and online to the ToolsNet server. When using ToolsNet as the time reference it is important that the server and the controller are set to the same time zone, even if they are in separate time zones.

To add and configure Date and time:

Controller time setting
Parameter | Condition | Description
--- | --- | ---
Source |  | The selection is made from a shortcut menu. Select the method to configure a controller time and date.
Time zone |  | The selection is made from a shortcut menu. Select the time zone in which the controller is located.
Time | Source = Manual | Enter a time in the format Hours:Minutes:Seconds.
Date | Source = Manual | Enter a date from the calendar symbol.
SET command button | Source = Manual | Sends the entered date and time to the controller. To be able to execute this command, the controller must be online.
ADD command button | Source = NTP | Add an additional NTP server address.
DELETE command button | Source = NTP | Delete the selected NTP server address.
NTP server | Source = NTP | Enter the IP address of the NTP server.

# Events Menu

Events are operational states and other pieces of information, for example errors, reported to the operator. All events can be configured and have different severity.

Event type | Function
--- | ---
Display | Events can be informative and are displayed for a short duration of time on the controller screen.
Log | Events can be informative and are displayed for a short duration of time on the controller screen and are also written to the log file. These will be displayed in the Events tab.
Acknowledge | Events that must be acknowledged by the operator. To acknowledge an event, the operator must press a button on an accessory, tap the controller touch screen or acknowledge the event through the web-GUI.

The event configuration determines how every event signals is treated.

Controller settings - events

A | Events search window | B | Events list

All available events are listed in the chapter References. Events have two categories:

- Standard events are defined by Atlas Copco and are available in every deliverable.

- Custom events are implemented by Atlas Copco on customer request and are only valid and available for specific customers.

Relevant Information

- Pushing Configurations to a Controller

In this Section

- Event Configuration
- Adding Events to the Library

# Event Configuration

Configuring event handling:

1. Select a controller in the Plant structure workspace .

2. Go to the Settings tab and select Events.

3. Search for a specific event using the search window or expand the sections by selecting them and scrolling through the Events to find the desired event codes.

4. Select or deselect one or more of the following:

   - Acknowledge, if the event is to be displayed and acknowledged by the operator.

   - Log, if the event is to be displayed, written to the log file and shown in the Events tab.

   - Display, if the event is to be displayed on a screen.

   The Details field can be used to add comments.

5. When ready, push the changes to the specific controller.

6. Repeat steps 3 - 5 for every controller that shall be configured.

Event code numbers 0000-7999 are standard events.

Event code numbers 8000-9999 are customer-specific events.

Relevant Information

- Adding Events to the Library
- Pushing Configurations to a Controller

# Adding Events to the Library

1. Select Settings , then in the Events configuration tab select Manage. Choose Add to Library from the drop-down list.

2. The Create global configuration dialog window opens containing two configuration options:

   - Auto revert, set as default.

   - Unlink

3. Select Create, the event configuration is now locked and visible in the Global Event Library.

Updating global events through the GUI
Action | Result
--- | ---
Auto revert | Updating the events through the controller GUI or the web GUI are ignored, if the program is marked as a global event in ToolsTalk 2. The update is made and sent back to ToolsTalk 2 where the change is recognized but not acknowledged. The original global event program is then immediately pushed back to the controller.
Unlink | Updating the events through the controller GUI or the web GUI causes the program to change from a global event to a local event, in the affected controller. The update is made and sent to ToolsTalk 2 where the change is recognized. As a result the event is immediately removed from the distribution list to the controller.

The selection of auto revert or unlink must be made when a global event is configured for distribution to a controller. The selection cannot be changed at a later stage.

# Extended Logging

Logs can be automatically created and stored. These logs can be configured to include extended logging using log groups.

The default setting for a log group is off. To enable a log group:

1. Select a controller in the Plant structure .

2. Go to Settings and select Extended Logging tab.

3. On the Log Groups window, select the group(s) that you want to enable.

4. Select SET.

## Reset Log Groups

It is possible to reset all log groups to their default settings.

1. Select a controller in the Plant structure .

2. Go to Settings and select Extended Logging tab.

3. On the Reset Log Groups window, select Reset.

## Persistent Log Groups

The log groups resets to their default setting at every reboot. To prevent resetting use persistent log groups.

1. Select a controller in the Plant structure .

2. Go to Settings and select Extended Logging tab.

3. On the Keep Selection after Restart window, set Persistent to ON.

# Working with the Sources Tab

Controller features, such as the Low Reaction Tightening Strategies and controller-wide functions among others, require licenses distributed through the Functionality Management System (FMS). Whereas configuration of features is possible without specific licenses, the assignment and use of those features will require the correct license to be installed on the controller. Please refer to Licenses (FMS) for more detailed information on licenses.

The selection of a task is done in the Task menu in the Virtual station configuration workspace.

External signals used as tasks for tightenings are configured in the Sources tab. Sources are accessories, or similar, connected to a virtual station. Two types of source tasks are available:

- Source Tightening task

- Source Batch task

Source Tightening is used to select a single tightening program.

Source Batch is used to select a batch sequence, a series of tightening programs.

Relevant Information

- Assigning a Task to a Virtual Station

In this Section

- Source Tightening Overview
- Creating a Source Tightening
- Creating a Source Batch
- Significant Positions
- Copying and pasting Batch Sequences and Sources
- Exporting a Source Batch or a Source Tightening
- Importing a Source Batch or a Source Tightening

# Source Tightening Overview

The tightening menu shows a list of Source Batch and Source Tightening configurations. Separate lists can be linked to a Virtual Station by going to the Virtual Station in question, and in the Task properties selecting Choose. There, a Source can be chosen as a task. Source tightenings link a specific tightening program to an identifier number. When the identifier number is sent to the controller, the linked program will run over and over until a different signal is sent ..

Parameter name | Description
--- | ---
Name | The name issued to the Source Tightening.
Description | The description of the Source Tightening.
Lock tool on batch sequence complete | On: The tool is locked when the batch sequence is completed. Off: The tool remains unlocked when the batch sequence is completed.
Socket selector | Control: When set to Control, an external source selects a tightening program by requesting an identifier number. The identifier number is linked to a corresponding socket in the socket selector, and by lifting the socket the tightening program is selected Confirm: In Confirm mode, the socket selector cannot be used as a controlling source. In this mode identifier numbers are linked to both a tightening program and a specific socket (indicated in an additional column in the list). When an identifier number is requested (by an external signal), the corresponding socket is prompted in the socket selector and the tightening program is activated when the operator lifts the socket (other sockets are disabled). If no socket is specified (that is, set to 0 in the Socket column), the tightening program is activated directly and the socket status is ignored.
Increment on NOK | On: The batch will advance even if a NOK tightening is performed. Off : Set Max consecutive NOK for the tightening. The batch will only advance if a successful tightening is performed.
Max consecutive NOK | Set the number of consecutive NOK results to be allowed. If the value is set to 0, then there is no check performed for NOK tightenings. When reaching max consecutive NOK's, the controller locks the tool and the sequence execution is halted.
Batch control | Select how the source tightening is to be executed. Internal: Configure how many times a source tightening should be repeated. External: Configure how many times a source tightening should be executed by using Open protocol or Fieldbus. Any configuration change clears the source tightening to start over from a clean and known state (the batch count in the batch will be reset to 0). Ongoing tightenings are able to finish before the changes take effect.

Command | Description
--- | ---
Add | Adds a new row with lowest identifier available.
Delete | Removes selected tightening program from the list. Select the tightening program by selecting the corresponding check box.

Relevant Information

- Assigning a Task to a Virtual Station

# Creating a Source Tightening

1. Select a controller in the Plant structure workspace .

2. Go to the Sources tab.

3. Select Add, the Create new source configuration dialog window opens. Choose Tightening from the drop-down menu then select Add.

4. Issue the Source Tightening with a name.

5. Select the correct Socket selector (Control or Confirm, depending on what is required).

6. Set the number of Max consecutive NOK results to be allowed. If the value is set to 0, then there is no check performed for NOK tightenings. When reaching max consecutive NOK's, the controller locks the tool and the sequence execution is halted.

7. Select which Batch Control is to be used from the drop-down menu.

   Internal batch control: Configure how many times a source tightening should be repeated.

   External batch control: Configure how many times a source tightening should be executed by using Open protocol or Fieldbus. Any configuration change clears the source tightening so to start over from a clean and known state (the batch count in the batch will be reset to 0). Ongoing tightenings are able to finish before the changes take effect.

8. By default, only one editable Identifier number will be available when creating a new Source Tightening. Select Add to add more.

9. Give every item an identifier number

   If a socket selector is used, the identifier numbers will correspond to the positions in the socket selector. For example, Identifier number 1 corresponds to socket number 1 in the socket selector.

10. Choose a tightening program to link to each identifier number by selecting Program and choosing from the list of tightening programs.

# Creating a Source Batch

1. Select a controller in the Plant structure workspace .

2. Go to the Sources tab.

3. Select Add, the Create new source configuration dialog window opens. Choose Batch from the drop-down menu then select Add.

4. Issue the Source Batch with a name

5. Set the Abort on new identifier to Yes if scanning a new identifier string should abort the previous scan.

6. Select the Identifier method (String for text, or Number for numerical strings).

7. Set Free order to On if the strings can be scanned in any order.

   Identifier strings can be made up of up to 4 different strings. When free order is set to No, the strings need to be scanned in a specific order for the system to recognize the string.

   An error may occur when Free order is set to On, and the lengths of the different strings are duplicated. The scanned sequence will then not activate a tightening program. To remedy this error, set Free order to Off, or adjust the string lengths.

8. Issue the string a Name and enter the length of the string. (For further information on concatenating strings, see Relevant Information in the User Guide).

9. Significant positions - the relevant positions in the string. (For further information on Significant Positions, see Relevant Information in the User Guide).

10. Saved positions - which positions are to be logged by the system. (For further information about Saved Positions, see Relevant Information in the User Guide).

11. Indicate which strings (in the String contains column) should be linked to which Batch sequence (in the Activates column). Select Add to add more strings.

Wildcards can be used when typing the "string contains". The wildcard(s) can be used at any position in the string. No Batch sequence is activated in case of an ambiguous matching result.

The wildcard is a . (period)

The Abort on new identifier controls how a second signal should be interpreted when a batch sequence has been activated and is ongoing.

If identifier numbers are used in the Batch sequence configuration , the input signal or the socket selector can be used to select a batch within a batch sequence.

The controller can be configured to select a batch sequence with input signal based on either an identifier number or an identifier string.

Relevant Information

- Assigning a Task to a Virtual Station
- Combining Identifier Strings
- Configuring Significant Positions to Read in Barcode String
- Saved Positions

# Significant Positions

Significant positions are used to specify which characters in the barcode string to read when putting together the string to match with your pre-defined string. The number of significant positions must match the number of characters in the pre-defined strings.

In this Section

- Configuring Significant Positions to Read in Barcode String
- Combining Identifier Strings
- Saved Positions

# Configuring Significant Positions to Read in Barcode String

The positions in the barcode string are associated with a number between 1 and 1024. The first position of the string is 1 and the last is 1024.

The significant positions must be specified following the rules described in the table below. Barcode strings:
Description | Significant positions | Valid configuration | Barcode string to match with pre-defined string
--- | --- | --- | ---
Significant positions in order | 1,2,3,7,8 | Ok | ABCGH
Significant positions in optional order | 7,1,2,3,8 | Ok | GABCH
Range of numbers | 1–3,7-8 | Ok | ABCGH

# Combining Identifier Strings

The identifier string that is used for matching is a combination of up to four strings from a factory management system or up to four scanner inputs that need to be combined into one string.

The Add and Delete command buttons manage how many strings are combined. The following parameters are available:

Parameters for combining identifier strings
Parameter | Description
--- | ---
Check box | Select an entry if it is to be deleted.
Name | The string must be given a name.
Length | The length of the string must be known and must be entered. This is important to be able to combine the correct string identifier.
Significant positions | The comma-separated positions or ranges (separated by hyphen) in the combined string that are used for matching.
Saved positions | The comma-separated positions or ranges in the strings that will be saved in the result.

If more than one identifier string is to be used, perform the following steps:

1. Press the Add command button to create a new entry in the table.

2. Issue the string a name.

3. Enter the length of the string.

4. Repeat steps 1-3 for every string to be added. Up to four strings can be combined.

The Start-End parameters in each row define the individual string positions in the combined string identifier that is used in the next step of the matching process.

The first part in the task selection process using an identifier string as an input, is to define which positions in the string that are to be activated:

- Enter the significant positions, to define which positions in the identifier string will be used for matching. The positions must be either comma-separated, or by range.

# Saved Positions

Saved positions is a field where the user can indicate which parts of each string used in the Source Batch will be saved, and how they will be represented in the log. In this field, indicate the positions in the string that need to be saved. Positions can constitute only parts of the entire string. If the field is left empty, the entire (concatenated) string will be saved. The table below shows some examples of saved position combinations.

Saved position values are comma-separated (without spaces), and ranges are indicated using a hyphen.

Identifier string | Positions
--- | ---
String 1: 1234567 | 1-7
String 2: abcdef | 8-13
String 3: GHIJKL | 14-19
String 4: 890 | 20-22

Saved position examples
Saved positions | Saved results
--- | ---
(empty) | 1234567abcdefGHIJKL890
1-3,9,11,15,20-22 | 123bdH890
8-12,1-7,19,20-21 will be changed automatically to: 1-12,19-21 | 1234567abcdeL89

# Copying and pasting Batch Sequences and Sources

It is possible to copy and paste:

- Batch Sequences

- Source Batches and Source Tightenings

The following rules apply:

- It can be done on the same controller

- It can be done between controllers of the same type that runs the same software version.

A copy of a batch sequence or source always includes everything as for example attached or associated programs and modes and links.

Example: A copy of a Source Batch > The paste creates a new Source batch with a new Batch Sequence and a Program linked to the new Source Batch.

Copying and pasting

1. Select a controller in the plant structure

2. SelectBatch Sequence or Sources. The workspace area shows all the available programs.

3. Right-click on a single row or select check boxes for several rows, right click and select Copy.

4. To paste the copy into the same controller, right-click anywhere in the empty workspace area and select paste. The copy is added to the first available position in the existing list.

   If there is no space in the list for the copy, the whole operation will fail.

   To paste the copy into another controller; select a controller in the plant structure and then select the applicable workspace. Right-click in the workspace and select paste.

   It is also possible to paste a copy into the Program Templates library workspace.

5. Double-click the pasted copy to open and modify it.

# Exporting a Source Batch or a Source Tightening

A Source batch or Source tightening can be exported from one controller and imported to another.

Export and Import are only possible if they are performed on the same controller, or different controllers of the same type and running the same software version.

When you export an existing Source batch or a Source tightening, any programs and modes associated with the tightening or batch sequence are also exported. These configurations are only copies and can be changed as per requirements.

1. In the Plant structure , select a controller from the list.

2. On the menu bar, select the Sources tab . The workspace displays a list of all the current Source batches and Source tightenings.

3. Select the check box of the Source batch or tightening to be exported.

4. Select Manage, and then choose Export from the drop-down menu.

   A browser window opens for saving the export file.

5. The default file name is <SourceBatch>.json or <SourceTightening>.json , the exported file can be given any name with the *.json extension.
   Select Save.

# Importing a Source Batch or a Source Tightening

A Source batch or Source tightening can be exported from one controller and imported to another.

Export and Import are only possible if they are performed on the same controller, or different controllers of the same type and running the same software version.

When you import an existing Source batch or a Source tightening, any programs and modes associated with the tightening or batch sequence are also imported. These configurations are only copies and can be changed as per requirements.

1. In the Plant structure , select a controller from the list.

2. On the menu bar, select the Sources tab . The workspace area shows a list of all the current Source batches and Source tightenings.

3. Select the Add command button and select Import.

4. Select Open File and browse to select the relevant .json file.

5. Select Add.

   The new Source batch or Source Tightening will be issued the first free position in the sequence list. If there are no free slots it will be placed at the bottom of the list and assigned the lowest available index number. It is not possible to change the index number.

# Working with the Tools Tab

On the Tools tab , a list of tools connected to the controller is displayed. The menus displayed will differ between the controllers for fixtured tools, and the controllers for handheld tools, providing detailed information about the connected tools.

In the menu Settings, tool alarms can be set. Trigger points for these alarms are taken from the Tool menu.

## Viewing the tool menu

1. Select a controller in the Plant structure workspace .

2. Go to the Tool tab.

   A list of tools connected to the controller is displayed.

3. Double-click on one of the tools in the table for more detailed information and to access the Service Settings.

How to connect a tool or how to make a wireless pairing is described in the controller manual.

Tool table columns
Column | Description
--- | ---
Tool type | Describes the type of the tool.
Model | A detailed model number of the tool.
Serial number | The serial number of the tool.
MAC address | The MAC address is only visible if the tool has got a MAC address.
Software version | The software version of the tool.
Max torque | The maximum torque value the tool can produce.
Max torque with TurboTight | The maximum torque value the tool can produce when using the TurboTight strategy. Applicable only to certain tools.
Max torque with TensorPulse | The maximum torque value the tool can produce when using the TensorPulse strategy. Applicable only to certain tools.
Max speed | The maximum rotation speed of the tool.
Next calibration | Date for the next calibration of the tool.
Virtual station | The name of the virtual station to which the tool is connected.

General information

The menu is valid for a controller that supports fixtured tools or handheld tools.

General tool information
Information | Description
--- | ---
Model | Tool model denomination.
Serial number | Tool serial number.
MAC address | The MAC address is only visible if the tools has got a MAC address.
Product number | The same as ordering number.
Software version | Tool software version number.

If the tool is an STwrench, the following information is displayed:

STwrench general tool information
Information | Description
--- | ---
Model | Tool model denomination.
Serial number | Tool serial number.
STwrench serial number | Tool serial number.
Software version | Tool software version number.
Radio module software version | Software version number.

The general tool information is provided by the tool itself to the controller and to ToolsTalk 2.

Limits

The menu is valid for a controller that supports fixtured tools or handheld tools.

Tool limit information
Information | Description
--- | ---
Gear ratio | The ratio of the angular velocity of the input gear to the angular velocity of the output gear.
Max Torque | The maximum torque the tool can use for a tightening.
Max Torque with Tensor Pulse | The maximum torque the tool can use for a tightening using the TensorPulse strategy. Applicable only to certain tools.
Max Torque with TurboTight | The maximum torque the tool can use for a tightening using the TurboTight strategy. Only applicable for SR31 tools.
Max speed | The maximum rotation speed of the tool.

The tool limit information is provided by the tool itself to the controller and to ToolsTalk 2.

If the tool is a STwrench, the following information is available:

Tool limit information for STwrench
Information | Description
--- | ---
Max Torque | The maximum torque the tool can use for a tightening or loosening.
Min Torque | The minimum torque the tool can use for a tightening or loosening.

Connection

Connection to the controller and to which virtual station it is assigned.

Calibration / Torque adjustment factor

The menu is valid for a controller that supports fixtured tools or handheld tools and is used to control how well a tool corresponds to a reference transducer and how to adjust differences.

The calibration value is stored in the tool's memory and is used to adjust the torque value given by the tool’s torque transducer so that the correct torque value is displayed on the controller. The controller displays last calibration date.

Tool calibration is carried out at the controller and uses a torque reference transducer. This process is described in the Power Focus 6000 manual.

Store the new calibration value in the tool's memory by entering the calculated value in the Calibration value parameter entry box, and then click Set.

Tool calibration information
Parameter | Description
--- | ---
Last calibrated | Date for last calibration.
Calibration value | Enter the measured and calculated value into the parameter entry box.
Next calibration | Due date for next calibration.
Set | Stores the entered values.

If the tool is a TBP, the following information is displayed:

TBP Torque adjustment factor
Parameter | Description
--- | ---
Last calibrated | Date for last calibration.
Torque adjustment factor | Enter the torque adjustment factor in %.
Set | Stores the entered values.

If the tool is a STwrench, the following information is displayed:

STwrench calibration information
Parameter | Description
--- | ---
Transducer calibration date | Date for last calibration.
Gyro calibration date | Date for last calibration.
Calibration alarm date |

Maintenance

The tool stores a service interval number and counts how many tightenings that can be performed before the next tool maintenance or service should be performed.

Tool maintenance information
Parameter | Description
--- | ---
Last service | Date and time when last service was performed. The last service date is set at the repair workshop. The Last service date is set to current date and time when the Reset button is pressed.
Total tightenings at service | The Total tightenings at service is the total number of tightenings performed by the tool since it was first used. This value is updated at service, and will remain the same until the next service.
Remaining tightenings | Total number of tightenings left until the service interval is reached.
Service interval | Number of tightenings to be performed before the next service. Can be set in multiples of 10 000.
Service interval pulses | pulse tools only] Number of pulses to be performed before the next service. Can be set in multiples of 10 000.
Remaining pulses | [pulse tools only] Total number of pulses left until the service interval is reached.
Reset service counter/data | The Reset command resets the counter and sets the Last service date to the current date. For TBP tools the oil status will also be reset.
Set | The command stores the value entered in the Service interval parameter entry field and adjusts the value to a multiple of 10 000.

Tool TAG information

This tool information is only available if the tool type is an STwrench.

STwrench tool information
Parameter | Description
--- | ---
TAG id | The programmable RFID TAG identification number that is programmed into the End-fitting tool (Socket).
Torque correction coefficient | In certain cases, extensions may be needed to fit the application. In this case the wrench measurement must be compensated to show a correct value. To calculate the correction coefficient, please refer to the STwrench user guide, printed matter nr 9836 4134 01 edition 2.12. The parameter is stored in the RFID TAG in the End-fitting tool.
Angle correction coefficient | In certain cases, extensions may be needed to fit the application. In this case the wrench measurement must be compensated to show a correct value. To calculate the correction coefficient, please refer to the STwrench user guide, printed matter nr 9836 4134 01 edition 2.12. The parameter is stored in the RFID TAG in the End-fitting tool.
Nominal torque | The smartHEAD of the STwrench contains the torque transducer and defines the wrench’s nominal torque, please refer to the STwrench user guide, printed matter nr 9836 4134 01 edition 2.12.

NOTICE

The correction coefficients alter the STwrench measurement. It may cause an improper reading. Before making any corrections, refer to the latest version of the STwrench User Guide (printed matter number 9836 4134 01).

Battery

The menu is available for battery tools. Shows battery information and battery health status.

Parameter | Description
--- | ---
State of charge (0-4) | The more charged, the higher the number.
State of health (0-2) | The better the health, the higher the number.

Health

The menu provides data from environmental monitors. The equipment measures parameters regularly and stores them.

Tool health monitor
Parameter | Description | Value
--- | --- | ---
Refresh | Command button: read tool value. |
History | Command button: History window opens to display latest temperature readings. |
Tool motor temperature | Latest temperature recording expressed in month/day/year hours:minutes:seconds. | Degree C or F
Tool electronics temperature | Latest temperature recording expressed in month/day/year hours:minutes:seconds. | Degree C or F
Tool pulse unit temperature | Latest temperature recording expressed in month/day/year hours:minutes:seconds. | Degree C or F

In this Section

- Handheld Tool Configuration
- Tools - QA calibration

# Handheld Tool Configuration

Handheld tools can have both standard functions, and accessory functions that provide signaling between an operator and the controller. The type of tool functions available depends on the tool model. In Tool configuration the signals are assigned to different functions.

A configuration is assigned to a tool and a tool is assigned to a virtual station.

This is described in the Configurations tab.

A | Tool accessory
B | LED ring
C | Blue LED on top
D | Function button
E | Direction ring
F | Battery
G | Tool trigger

The following tool configuration parameters are available:

- Blue led; a visual output signal.

- Buzzer; an audio output signal that can produce different audio signals.

- Direction switch; An input signal.

- Function button; in a combination with the direction ring, six different input signals can be produced.

- Tool accessory bus; different accessories can be configured with both input and output signals.

- Tool LEDs; A ring of tool LEDs can be used to provide different output signals.

In addition, the tool configuration also defines how the tool is started and when tightening traces are recorded.

## Viewing or Editing a Tool Configuration Menu:

1. Select a controller in the Plant structure workspace .

2. Select the Configurations tab in the Menu bar.

   The workspace area displays the current accessory configurations.

3. Add a new configuration or double-click on an existing configuration with the type being a tool configuration.

4. Add the necessary configurations. The parameters are described in each section.

The tool configuration is divided into the following menus:

Menu | Description
--- | ---
Properties | Configuration name and description and a tool type filter.
General | General parameters for the tool.
Buzzer | Output signal definitions for different tone signals.
Direction switch | The direction switch is used as an input signal.
Function button | The functional button together with the direction switch generates several different input signals.
Tool LEDs | Output signal definitions for different LED signals.
Accessory bus | Configuration of tool accessories.

As the number of tools grows, the number of menus will grow as well. To increase the visual comfort in the workspace, it is possible to filter menus and only show what is relevant for one selected tool type. The filter is set in the Properties menu.

# Tools - QA calibration

External tool configuration

Option | Function
Enable | ON: Enables the external tool configuration option OFF: Disables the external tool configuration option.
Virtual station | Connect the relevant Virtual station.
Connection type | Connect via TCP port or Connect via COM port.
TCP port | Visible when Connection type TCP port is selected. Shows the TCP port, pre-populated.
COM port | Visible when Connection type COM port is selected. Shows a drop-down list with the available COM ports.

# Working with the Virtual Station Tab

The Virtual Station tab is located in the controller menu bar when a controller has been selected in the Plant structure

A virtual station is a software abstraction of a controller. Within one controller it is possible to create several virtual stations. Each virtual station behaves like a controller. The various configurations can be assigned to virtual stations as needed.

It is possible to select a task, assign accessory configurations, assign a tool, monitor and manipulate incoming and outgoing signals via diagnostics and set communication protocol parameters from the virtual station menu. The virtual station icon is available for both a FlexController and a Power Focus 6000.

Controller features, such as the Low Reaction Tightening Strategies and controller-wide functions among others, require licenses distributed through the Functionality Management System (FMS). Whereas configuration of features is possible without specific licenses, the assignment and use of those features will require the correct license to be installed on the controller. Please refer to Licenses (FMS) for more detailed information on licenses.

In this Section

- Virtual Station Overview
- Assigning License Types and Features to a Virtual Station
- Assigning a Tool to a Virtual Station
- Assigning a Task to a Virtual Station
- Assigning Accessories to a Virtual Station
- Assigning a General Virtual Station Configuration
- Tool Configuration in a Virtual Station
- Virtual Station - Properties
- Fieldbus Mapping in a Virtual Station
- Virtual Station - Protocols
- Virtual Station - Diagnostics
- Virtual Station - Manual mode

# Virtual Station Overview

To open the Virtual station workspace and view the list of virtual stations:

1. Select a controller in the Plant structure workspace .

2. Select the Virtual station tab in the menu bar.

   The workspace area displays a list of virtual stations in the controller. The list is empty if no virtual stations have been created.

Virtual station workspace information
Column | Description
--- | ---
Check box | Selects a virtual station.
Name | Shows the name of the virtual station.
Description | Description of the virtual station.
Changed by | Which user that made changes
Controller updated | Last time the controller was updated
Controller updated by | Which user that has updated the controller

Virtual station workspace command buttons
Command | Description
--- | ---
Add | Creates a new virtual station. Newly created virtual station needs to be pushed to controller to get full functionality.
Delete | Removes the selected virtual stations from the list.

To access the virtual station configuration menu:

## Navigating to Virtual station configuration

1. In the Plant structure workspace select a controller .

2. Select the Virtual Station tab .
   The virtual station overview shows a list of virtual stations for the selected controller. The list is empty if no virtual stations have been created.

3. Double-click on a virtual station to open an existing configuration, or click Add to create a new virtual station configuration.

The following menus are displayed:

Workspace information
Menu | Description
--- | ---
Properties | Issues the configuration a name and description. Optional.
Protocols | Activation and configuration of external communication protocols.
Tool | Assigns a tool to the virtual station.
Tool configuration | Assigns a tool configuration to the virtual station.
Fieldbus mapping | Displays a fieldbus mapping if it is configured and assigned to the controller. This field is information only. The actual fieldbus mapping and configuration is done in theFieldbus and SoftPLC tab.
Task | Assigns a task to the virtual station or configures how a source signal selects the task to be performed.
Accessories | Assigns an accessory configuration and an address to an accessory and assigns the combination to a virtual station.
General | Used when assigning a General Virtual Station.
Manual Mode | Used to configure the Manual Mode function.
Licenses | Used for assigning and removing licenses and features to a virtual station.

For a FlexController, only the Properties, Fieldbus mapping and Task menus are available.

Relevant Information

- Pushing Configurations to a Controller

# Assigning License Types and Features to a Virtual Station

In the Virtual Station area licenses can be assigned to specific Virtual Stations. Select a controller from the Plant Structure then select the Virtual Station tab. A list containing the different virtual stations is displayed.

Assigning a Virtual Station Type

1. Double-click on the row to be configured.

2. In Licenses configuration, select Virtual Station Type.

3. Select one of the following options:

   - Change to change the current type, a dialog window opens containing the available types.

   - Remove to remove the current type.

   - Choose to add a new type. Choose the type and select OK.

Assigning Virtual Station Features

1. Double-click on the row to be configured.

2. In Licenses configuration, select Virtual Station Features.

3. Select one of the following options:

   - Add to add a new feature, a dialog window opens containing the available features . Choose the feature and select OK.

   - Remove to remove the current type.

# Assigning a Tool to a Virtual Station

The Tool menu is used to assign a tool to the virtual station and provides information about the assigned tool.

Tool menu information
Function | Description
--- | ---
Model | Currently assigned tool to the virtual station.
Max torque | Information only shown if a tool is connected to the controller and assigned to the virtual station.
Software version | Information only shown if a tool is connected to the controller and assigned to the virtual station.
Serial number | Information only shown if a tool is connected to the controller and assigned to the virtual station.
MAC address | Information only shown if a tool with a MAC address is connected to the controller and assigned to the virtual station.
Product number | Information only shown if a tool with a specified product number is connected to the controller and assigned to the virtual station.
Unassign | Command button. Unassign a tool from the virtual station.
Choose | Command button. Change the tool, or assign a new tool to the virtual station. A pop-up window opens for the tool selection task.

- A cable tool is connected to the controller via an electrical cable. A controller can have one cable tool connected.

- A battery tool can be connected in three different ways:

  - Bluetooth - Using direct communication

  - WLAN (Ad-Hoc mode) - Using direct communication

  - Infrastructure mode - Using indirect communication within the plant's own network, via access points

Please see the specific Tool's Manual when configuring the communication settings.

Change tool pop-up window information and configuration fields
Function | Description
--- | ---
Wireless tool serial number | It is possible to assign a wireless tool to the virtual station that is not yet connected to the controller. A wireless tool is identified by its serial number, which can be entered in the data entry field. Wireless pairing, the process of connecting a wireless tool to a controller is described in the controller documentation.
STB, SRB, TBP or STwrench | Select the desired tool type for a new wireless tool.
Choose | Command button. Executes all the selections.
Close | Closes the pop-up window without any changes.
List of tools | The list contains all wireless tools currently connected to the controller. The virtual station column indicates if a tool is already assigned to a virtual station. If a cable tool is connected to the controller, it is also included in the list.

## Navigating to Virtual station configuration

1. In the Plant structure workspace select a controller .

2. Select the Virtual Station tab .
   The virtual station overview shows a list of virtual stations for the selected controller. The list is empty if no virtual stations have been created.

3. Double-click on a virtual station to open an existing configuration, or click Add to create a new virtual station configuration.

## Assigning a Tool

1. Select Choose in the Tool menu.

2. Select one tool from the list in the tool table, or type the serial number of a wireless tool that should be connected to the controller.

3. If a serial number is entered, select whether the wireless tool is an STB, SRB, TBP or an STwrench tool.

4. Enter Product number for the tool. This field is optional.

5. Select Choose.

6. Update the controller via the Push function.

It is important to assign both a tool and a tool configuration to a virtual station. Tool configurations are created in the Configuration section .

Relevant Information

- Pushing Configurations to a Controller
- Tool Configuration in a Virtual Station

# Assigning a Task to a Virtual Station

The Task menu in theVirtual station workspace is used to select and assign tasks.

The menu is available for both a Power Focus 6000 and a FlexController, but the functionality is different.

Task menu information
Function | Description
--- | ---
Name | Currently assigned task to the virtual station. The field is empty if no task is selected. Pressing the trigger will result in the event number 4025 No Tightening program selected . An error indicator can appear beside the name . The tightening program is not correctly configured and cannot be used.
Unassign | Command button. Deselects any task from the virtual station.
Choose | Command button. Change the task manually or configure external sources to select a task. The Choose task pop-up window opens to configure the task selection.

Virtual station - Assigning a task

A | Choose task pop-up window. | B | Selection tabs. Tightening program Batch sequence Sources
C | List of available tasks: Tightening program: The same list as shown under the tightening icon Batch sequence: The same list as shown under the batch sequence icon Sources: The same list as shown under the sources icon | D | Command button Choose. Command button Close.

## Navigating to Virtual station configuration

1. In the Plant structure workspace select a controller .

2. Select the Virtual Station tab .
   The virtual station overview shows a list of virtual stations for the selected controller. The list is empty if no virtual stations have been created.

3. Double-click on a virtual station to open an existing configuration, or click Add to create a new virtual station configuration.

## Assigning a Task

1. Select Choose in the Task menu.

   The Choose task pop-up window appears.

2. Select one tab and select one item from the list:

   - Tightening program: Select from a list of tightening programs available in the controller.

   - Batch: Select from a list of batch sequences available in the controller.

   - Sources: Select from a list of source tasks available in the controller.

   For fixtured tools using the FlexController, only Sources is available and only one line - Multi Spindle Tightening, can be selected.

3. Select Choose. The Choose task pop-up window is closed.

   The Close button closes the pop-up window without making any changes.

4. Update the controller via the Push function.

The name field is updated in the Task menu.

The task selection using sources and identifier numbers and identifier strings to select a task is described in detail in the documentation for the sources configuration.

Relevant Information

- Pushing Configurations to a Controller

# Assigning Accessories to a Virtual Station

This menu is only valid for a controller that supports a handheld tool.

A controller may have several accessories connected through a CAN bus. Each accessory must have a unique address on the bus within the range 1-15. It is possible to assign several accessories to a virtual station.

An accessory must have an accessory configuration assigned to it, before it is possible to assign the accessory to the virtual station.

To view the current accessory assignment to a virtual station:

## Navigating to Virtual station configuration

1. In the Plant structure workspace select a controller .

2. Select the Virtual Station tab .
   The virtual station overview shows a list of virtual stations for the selected controller. The list is empty if no virtual stations have been created.

3. Double-click on a virtual station to open an existing configuration, or click Add to create a new virtual station configuration.

Accessories menu information
Function | Description
--- | ---
Check box | Selects an accessory configuration that can be unassigned from the virtual station.
Name | Name of the configuration assigned to the accessory.
Type | Type of accessory.
CAN node | The CAN address of the accessory.
Serial number | The serial number of the accessory.
Status | Can be either: Connected. Assigned but not connected.

The CAN node column shows the used addresses which can not be used when new accessories are connected. An assignment for a socket selector can include multiple addresses.

For socket selectors the order of the CAN nodes is important. The lowest position in the first socket selector is the first position in the assignment.

Accessory menu command buttons
Function | Description
--- | ---
Unassign | The selected accessory is unassigned from the virtual station. The accessory remains connected to the controller.
Choose | Adds a new accessory. The Accessories pop-up window opens.
Diagnose | Monitoring of I/O signal behavior and possibility to force signals to a desired state between controller internal logic and the accessory.

Relevant Information

- Pushing Configurations to a Controller

In this Section

- Adding an accessory to a Virtual Station
- Unassigning an Accessory from a Virtual Station
- Configuring I/O

# Adding an accessory to a Virtual Station

The selected accessory must have a unique and valid CAN bus address. An accessory configuration is assigned to an accessory and the accessory is assigned to a virtual station.

## Navigating to Virtual station configuration

1. In the Plant structure workspace select a controller .

2. Select the Virtual Station tab .
   The virtual station overview shows a list of virtual stations for the selected controller. The list is empty if no virtual stations have been created.

3. Double-click on a virtual station to open an existing configuration, or click Add to create a new virtual station configuration.

To assign an accessory to the virtual station:

1. Select the Choose button in the Accessories menu to open up the Accessories pop-up window.

2. Select an accessory type from one of the tabs.

3. Check to select a configuration in the list of Configurations.

4. Check to select an address in the list of Available CAN nodes.

   It is possible to connect several socket selectors to a controller. Each of the socket selectors have a unique CAN address. It is possible to assign one configuration to all socket selectors. The CAN node order becomes important to define the sockets in the correct order. The socket selector that has the lowest order position must be selected first, followed by rising order.

5. Select the Choose button and add one of the accessory options.

6. Repeat the procedure for each accessory that is to be assigned to the virtual station.

7. Select the Cancel button to close the pop-up window.

   The Accessories menu is updated and shows new assigned configurations.

An accessory address is set by a rotary switch on the accessory. See detailed product information documents for the accessory. Accessory address range is between 1 and 15.

Relevant Information

- Pushing Configurations to a Controller

# Unassigning an Accessory from a Virtual Station

To unassign an accessory configuration and remove the connection to a virtual station, perform the following steps:

## Navigating to Virtual station configuration

1. In the Plant structure workspace select a controller .

2. Select the Virtual Station tab .
   The virtual station overview shows a list of virtual stations for the selected controller. The list is empty if no virtual stations have been created.

3. Double-click on a virtual station to open an existing configuration, or click Add to create a new virtual station configuration.

4. Mark the check box of the accessory configurations that is to be unassigned in the Accessories menu.

5. Select the Unassign command button in the Accessories menu.

6. To update the controller with any changes, select the Push changes command button .

The list in the accessory menu will be updated.

Relevant Information

- Pushing Configurations to a Controller

# Configuring I/O

I/O Diagnostics is used to troubleshoot external hardware and to test configuration. The operator is able to troubleshoot a station that is not behaving correctly. A station's behavior is not only defined by its software, hardware and configuration, but the combined state of all its inputs and outputs. Therefore it is often helpful to get an overview of input and output states. This can for example aid in finding the following problems:

- Hardware malfunctions in the accessories (lamps/cables/buttons etc.)

- Suspicion that inputs are not properly received from surrounding systems.

- Suspicion that outputs are not properly sent to surrounding systems.

To access the I/O diagnose function:

1. Select a controller in the Plant structure workspace .

2. Select virtual station in the Menu bar of the controller workspace.

   The workspace area displays a list of virtual stations in the controller. The list is empty if no virtual stations have been created.

3. Double-click on a virtual station name to open an existing virtual station configuration or click Add to create a new one.

4. The workspace shows the menus, including Accessories assigned to that specific virtual station.

5. Select the check box for the device to be diagnosed. The device has to be in status Connected.

6. Select Diagnose.

The I/O diagnostics function provides the possibility to Monitor the incoming and outgoing signals, sent to and received from the selected device. It is also possible to manipulate the information via Forced mode.

I/O diagnostics can be used from:

- Controller GUI

- Web GUI

- ToolsTalk

I/O diagnostics view

Diagnostics mode | Activate Monitor mode or Forced mode. Monitor mode: In monitoring mode it is possible to see status of all configured fields in the incoming and outgoing signals, sent to and received from the device. Whenever there is a change in a signal, the view is updated. Forced mode: When in forced mode, the signals are frozen in their current state and will be possible to manipulate from the client. The operator can now activate and deactivate signals individually. The change of signal value in forced mode is immediately propagated to the controller. When leaving forced mode all forced signals will be set to their actual values, that is, the values they would have had if no forcing had been performed.
Component | The column Component lists the parts of the device where to connect the incoming/outgoing signals.
Signal | List of signals configured for the selected device. If no signal is configured, the field displays the text "None".

Only one diagnostics session can be active at a time and only one device at a time can be in diagnostics state. If the diagnostics is already in use, an information message is shown on the screen.

# Assigning a General Virtual Station Configuration

## Navigating to Virtual station configuration

1. In the Plant structure workspace select a controller .

2. Select the Virtual Station tab .
   The virtual station overview shows a list of virtual stations for the selected controller. The list is empty if no virtual stations have been created.

3. Double-click on a virtual station to open an existing configuration, or click Add to create a new virtual station configuration.

## To assign a General configuration to the virtual station

1. In the virtual station configuration workspace, go to the General area.

2. Select Change. In the pop-up window: The listed General configurations are the ones added in Configurations .

3. Select one of the general configurations and select the Change button.

   The General menu is updated with the selected general configuration.

Only unassigned general virtual station configurations can be deleted.

Relevant Information

- Pushing Configurations to a Controller
- Working with the Configurations Tab

# Tool Configuration in a Virtual Station

This menu is only visible for a Power Focus 6000 using handheld tools.

A tool may have several configurations of the tool accessories. Tool accessories are for example the LED’s, push buttons, buzzers and direction rings. Digital I/O signals can be configured to interact with the operator. The tool accessory configuration is made in the Configurations menu .

Virtual station - Tool configuration menu information
Function | Description
--- | ---
Name | Name of the tool configuration.
Tool type | The Tool type filter can be used to show configurations for selected tools. The filter is set when tool accessories are configured in Configurations .
Description | The optional tool configuration description field.
Change | Assigns the selected tool configuration to the tool assigned to the selected virtual station.
Close | Closes the pop-up window without saving any changes.
| The list of configurations can be sorted alphabetically. Click on the arrow to change the sorting direction.

## Navigating to Virtual station configuration

1. In the Plant structure workspace select a controller .

2. Select the Virtual Station tab .
   The virtual station overview shows a list of virtual stations for the selected controller. The list is empty if no virtual stations have been created.

3. Double-click on a virtual station to open an existing configuration, or click Add to create a new virtual station configuration.

:

## Selecting a Tool Configuration

1. Select Change in the Tool configuration menu.

   The Select tool configuration pop-up window appears, listing the available tool configurations.

2. Select one row of tool configurations and select Change in the pop-up window.

   The Select tool configuration pop-up window disappears.

   The Tool configuration menu shows the selected configuration name.

If a tool filter is used in the tool accessory configuration AND a tool is connected and assigned to the virtual station, the Tool type column shows only relevant configurations, and the list is reduced to selectable configurations.

If no tool is assigned to the virtual station or no tool filter is used, all tool configurations are shown in the list.

Relevant Information

- Pushing Configurations to a Controller

# Virtual Station - Properties

A virtual station must have a name. This is configured in the Properties menu. The default name is Virtual station <index nr>. An optional description field is also available.

If the name field is left blank, a red error indicator is displayed .

# Fieldbus Mapping in a Virtual Station

A controller may have one Fieldbus communication module installed. This communication module serves all the virtual stations. The Fieldbus mapping menu shows which fieldbus configuration is mapped to the controller. Fieldbus is configured and the configurations are assigned and mapped in Fieldbus and SoftPLC

In this Section

- Fieldbus Diagnostics

# Fieldbus Diagnostics

To access the Fieldbus mapping diagnose function:

1. Select a controller in the Plant structure workspace .

2. Go to Virtual Station .

   The workspace area displays a list of virtual stations in the controller. The list is empty if no virtual stations have been created.

3. Double-click on a virtual station name to open an existing configuration or select Add to create a new virtual station configuration.

4. The workspace shows the menu, including mapped fieldbus.

5. Click the Diagnose button to enter the Fieldbus diagnose function.

The fieldbus diagnostics function provides the possibility to Monitor the incoming and outgoing signals, sent to and received from the fieldbus. It is also possible to manipulate the information, compose and send frames, via Forced mode. Fieldbus diagnostics can be used from:

- Controller GUI

- Web GUI

- ToolsTalk

Fieldbus diagnostics - forced mode

Diagnostics mode | Activate Monitor mode or Forced mode. Monitor mode: In monitoring mode it is possible to see the status of all configured fields in the incoming and outgoing frames, sent to and received from the fieldbus. Whenever there is a change in any of the bits of a received frame, the view is updated. Forced mode: When entering forced mode, the data will freeze in its current state, the frame is locked. In forced mode it is possible to activate and deactivate signals manually, or enter values and force them on one or more signals. This is possible on the incoming frame, the outgoing frame, or both.
Boolean converter | Switch between System view and Bus view. The converter makes it possible to invert the signals sent to or received from the fieldbus.
Type | Type of signal.
Byte | Location in frame.
Bit | Location in frame.
Length | Length of signal in frame.
Name | Name of signal.
Has converter | Has converter is Yes if any converter is configured. If Yes, the converter can be used to invert the signal. If No, the converter is not applicable.
Value | The Value column shows a list of signals and their values. The value of each signal in the incoming and outgoing frame is seen in the following formats: boolean, integer or string, depending on type. The values are editable in Forced mode. It is possible to change one signal, a few signals or all signals in the same frame. After changing the values, click Send frame button for the new frame to be pushed to the controller and for the new values to be applied. When leaving diagnostics mode, all values are reverted to as they were in the last saved frame of incoming and outgoing signals.

Only one diagnostics session can be active at a time. If the diagnostics is already in use, an information message is shown on the screen.

# Virtual Station - Protocols

The Protocols menu may contain one or more implemented communication protocols and their parameter settings. The availability of protocols depends on the IAM license.

Some communication protocols are configured in the Protocols menu.

In this Section

- Open Protocol

# Open Protocol

## Configuring Open Protocol

1. In the Plant structure workspace select a controller.

2. Select the Virtual Station tab .
   The virtual station overview shows a list of virtual stations for the selected controller. The list is empty if no virtual stations have been created.

3. Double-click on a virtual station to open an existing configuration, or select Add to create a new virtual station configuration.

4. Select Configure in the Protocols menu.

- The virtual station Open protocol configuration switch allows a user to enable or to disable Open protocol communication between a virtual station and the integrator, which is part of the factory control equipment.

  The Open protocol uses the same factory ethernet connection on the controller that is used for configuration or for delivering tightening results.

  Each virtual station is uniquely identified by a port number. For each virtual station using the open protocol, a port number must be entered in the Port field.

- If the open protocol is used to select the task, the Disconnect setting controls the actions to be taken when the communication between the virtual station and the client is lost:

  - None: If the system loses connection towards the Open Protocol client, no action will be taken and any selected task will be able to continue with normal operation.

  - Unassign task: If the system loses the connection towards the Open Protocol the selected task will be deselected, the tool will not be locked

    - If an open protocol error occurs, the current tightening is finished and the task ends. The current task is deselected from the virtual station.

    - If a communication error occurs, the current tightening is finished and the task ends. The current task is aborted but not deselected from the virtual station.

  - Lock tool active high: If the system loses connection towards the Open Protocol the tool will be locked.

    - When the Open Protocol connection is restored, the tool will remain locked. In order to resume normal operation the tool has to be unlocked using MID 0043 (Enable tool) or IO signal Master unlock.

    - The task will not be deselected when Lock tool option has been selected.

  - Always lock tool: If the system loses connection towards the Open Protocol the tool will be locked, regardless whether the used task is selected via Open Protocol or not.

    - When the Open Protocol connection is restored, the Tightening program and Sequence task have to be selected to resume normal operation.

    - When the Open Protocol connection is restored the tool will remain locked. In order to resume normal operation the tool has to be unlocked using MID 0043 (Enable tool) or IO signal Master unlock

- The legacy counter setting counts all tightenings in a sequence and outputs that number to secondary systems. To enable this setting, set Use legacy counter to On.

- SoftPLC Index is used to map where in the shared memory the Open Protocol commands are to be written. The default value is 1 but it is possible to enter values 1 to 6.

As the default value for SoftPLC Index is always 1 and no check is made to see if it is in use, there is a possibility that you may have configured the system so that the same index is configured several times when adding Virtual stations. In this case the Soft PLC will not be able to determine from which Virtual Station the incoming MID is originating from.

# Virtual Station - Diagnostics

The diagnostics are available for both I/O and Fieldbus configurations.

- For I/O diagnostics, for further information, see Relevant Information in the User Guide.

- For fieldbus diagnostics, for further information, see Relevant Information in the User Guide.

Relevant Information

- Configuring I/O
- Fieldbus Diagnostics

In this Section

- Digital Signal Diagnostics
- Normal Operations
- Monitor Digital Signals
- Force Digital Signals

# Digital Signal Diagnostics

During deployment and during troubleshooting of a controller, a diagnostic tool is very helpful. It is available for the analysis under the Info tag for a device configuration or a fieldbus mapping in the Virtual station menu.

The controller can operate in normal mode or in diagnostics mode. In normal mode the digital input and output signals operate normally and are routed between the internal controller logic and to an external accessory or a connector.

The diagnostics mode is divided into monitor mode and forced mode. In the monitor mode signals operate normally, but provide live monitoring of the signal behavior. In forced mode the connection between the controller internal logic and the external accessory is opened and the input and output signals can be forced to a desired state.

It is possible to diagnose digital signals for one device or one fieldbus at a time.

# Normal Operations

In normal operations mode external input signals are passed to the internal controller logic and controller output signals are passed to an external target, without any intervention from the diagnostics module.

A | Controller internal state machine and logic functions
B | Digital output signal path
C | Digital input signal path
D | Diagnostics module

# Monitor Digital Signals

In the diagnostics mode all signals passed to and from the controller internal logic can be monitored. A signal tap is connected in the diagnostics module and the signal states are displayed on the web GUI or the controller GUI.

A | Controller internal state machine and logic functions
B | Digital output signal path
C | Digital input signal path
D | Diagnostics module
E | User interface
F | Output signal tap
G | Input signal tap

# Force Digital Signals

In the diagnostics mode all signals passed to and from the controller internal logic can be forced to a desired state. The signal lines are opened in the diagnostics module. From the user interface both input and output signals can be forced to steady states. The user interface is either the web GUI or the controller GUI.

While signals are forced, the controller operates normally. When leaving the diagnostics mode and the forced mode all signals are set to the current operating state of the controller. This may lead to a change-of-state for digital outputs, which can create unwanted actions.

A | Controller internal state machine and logic functions
B | Digital output signal path
C | Digital input signal path
D | Diagnostics module
E | User interface
F | Forced output signal insertion point
G | Forced input signal insertion point

# Virtual Station - Manual mode

Manual mode for Virtual Stations is used for performing tasks while the tool is in locked mode. In cases where the tool is locked for a certain reason (for example, because the tool is outside its TLS footprint) there still may be a need to perform certain tasks with the tool, such as performing emergency work. By configuring manual mode for the Virtual Station, users can determine what signals are sent when entering manual mode (Entering signals), what task can be performed while in manual mode (Secondary task), and what signals are sent when leaving manual mode (Leaving signals).

Since desired scenarios can vary between different users (that is, which signals to send upon entry and exit and what task to perform), manual mode is fully configurable for each Virtual Station.

In this Section

- Configuring Manual Mode
- Triggering Manual Mode

# Configuring Manual Mode

Configuration consists of three elements: entering signals, leaving signals and secondary task (note that by primary task is meant the "automatic" task that is assigned to the virtual station under Task). If no secondary task is selected, the primary task will be run.

1. Go to the Virtual station menu, select the virtual station to configure, and then under Manual Mode, select Configure.

2. In the Manual mode configuration screen, set the secondary Task. This determines which task should be run when in manual mode.

   The same tasks (tightening, batch sequence, source) can be set for the secondary task as for the primary task.

3. Set the entering signals to be sent by selecting the Add button.

4. Set the leaving signals to be sent by selecting the Add button.

There is a limit set to 99 signals to be sent for entering and leaving.

The parameters for entering and leaving signals are the same.

Relevant Information

- Pushing Configurations to a Controller
- Triggering Manual Mode

# Triggering Manual Mode

Manual Mode can be activated by a switch or an external system. For example (indicated below), a key switch on an operator panel can be configured to activate manual mode.

1. Go to the Configurations menu and choose Operator panel .

2. In the configuration window, go to the position [A,B,C,D,E,F,G,I] to configure and in the list, choose One way key switch.

3. Select on the Turn signal list. In the list, choose Manual mode.

4. Close the window.

If the user needs to be notified that Manual mode has been entered or left, then events 4070 and 4071 have to be configured, respectively. This is done in Settings - Events.

Relevant Information

- Configuring Manual Mode
- Events Menu
- Pushing Configurations to a Controller

# Configuration for FlexSystem and Synchronized tightening

# Working with synchronized tightening

For Power Focus 6000 and PF8 controllers it is possible to connect several controllers together and run synchronized tightenings. The first controller in the configuration is called the Sync Reference and handles all the tightening and data reporting. Up to 5 additional controllers can be connected to the Sync reference through cable and are called Sync Members. Their only function is to control the tools.

## Sync Reference

The Sync Reference is the brain in the system. It controls:

- the tightening settings

- the data reporting

- the configuration of the complete system

- the connection to Tools Talk and ToolsNet

Accessories and field buses are connected directly to the Sync Reference.

## Sync Member

The Sync Member works as a drive without any extra functionality. The IT part does not run and it is not possible to connect any external accessories or protocols to the Sync Member. Each Sync Member has an assigned channel number (2-64). The channel number is used to:

- identify a connected tool and drive within the Hardware Layout Configuration in ToolsTalk 2.

- produce result reports.

- identify faulty parts in error events.

## Tightenings

It is only possible to run Multistep tightening programs. To synchronize tightenings between each tool, synchronization points are used. At these points, the tools wait for each other before continuing with the next step in the tightening program. A tightening program can contain up to 25 steps (synchronization points not included). No repair or termination paths are allowed.

Controller features, such as the Low Reaction Tightening Strategies and controller-wide functions among others, require licenses distributed through the Functionality Management System (FMS). Whereas configuration of features is possible without specific licenses, the assignment and use of those features will require the correct license to be installed on the controller. Please refer to Licenses (FMS) for more detailed information on licenses.

# Working with the Hardware Configuration Tab

Offline programming of a Hardware Layout Configuration is made in the Controller Template Library.

## Configuration Area

In the configuration area, you can either create a layout from scratch or update the existing layout extracted from your controller.

Buttons
Extract | Updates the hardware layout configuration according to the hardware connected to the controller.
Zoom in | Zooms in on the layout. (Ctrl + mouse wheel forward)
Zoom out | Zooms out on the layout. (Ctrl + mouse wheel backward)
Fit to screen | Reverts the layout back to a default size.
Delete | Deletes the selected item.

## Creating Hardware Layout

A new installation of the system does not contain any previous hardware layout configurations. Each time you connect ToolsTalk 2 to a controller, the Hardware layout Configuration is empty. You will need to either create a new configuration, or extract the current controller hardware setup.

To create a hardware layout:

- For FlexSystem, start with a carrier (3-slot or 6-slot) from Tool Box. For the sequence of the channel number, it is recommended to use 6-slot carriers first. For any system with more than two FlexCarriers, start hardware configuration with a 6-slot FlexCarrier.

- For Synchronized tightening system, start with a Sync Reference controller from the Tool Box.

Drag a FlexCarrier or a Sync Reference controller to the Drop here area and drop it. Indicators are displayed. You can point to a symbol to get a tooltip .

Drag other products from Tool Box to a target place. When pointing to a target place with a product, the target place will change color:

- Red: invalid drop

- Blue: valid drop

You can move, copy and remove a single product or a carrier with all its products.

- To move, click and drag the product.

- To copy, press Ctrl and drag the product.

- To delete, choose the product, or hold Ctrl and select many, and then press Delete. A FlexCarrier containing the FlexController can only be deleted when it is the single remaining carrier. A Sync Reference controller with connected Sync Members and tools can only be deleted when it is the single remaining product, or when all other products are deleted simultaneously.

After creation, push the changes to the controller. The hardware deployment status will change after validation.

## Extracting a hardware layout configuration

If the Hardware Layout Configuration is empty, a current controller setup can be extracted by using the Extract button.

1. Select Extract, the Extract Hardware Configuration dialog box opens.

2. Select OK to extract the current configuration.

After extracting, push the changes to the controller in order to receive status and health. The hardware deployment status will change after validation.

The Extract function is not available when creating a Hardware Layout Configuration as a Template.

## Status

When the controller is connected and online, and the hardware layout configuration is in sync with the controller, ToolsTalk 2 will start to receive notifications of changes in the hardware deployment status. Once notified, ToolsTalk 2 will ask the controller for the Hardware measurement data.

To see detailed deployment status and measurement data:

1. Select the product in the configuration area. Multiple products can be selected by pressing Ctrl and select.

2. Click on the Status bar to expand the window.

Tips:

- The height of panel can be increased by dragging the top border.

- To get the latest measurement data, click Refresh.

- The details of Health status can be expanded. Select Show only NOK to only view the data with NOK result.

Tool configuration

For each tool, it is possible to select a tool configuration from a list containing all available tool configurations. By default, no mapping of Tool Configuration is made. It is possible to run tools that are not mapped to a tool configuration. In this case, the controller will use an internally created default Tool Configuration without any of the multiple transducer functionality enabled.

Inhibit mode

If there is something wrong with the channel (Drive or tool), inhibit mode can be set to continue using your hardware:

- False: Channel is running OK.

- Report OK: Channel is disabled and reports OK in result.

- Report NOK: Channel is disabled and reports NOK in result.

- Report No Result: Channel is disabled and do not show up in the result.

Symbols

Symbols indicate status of each product. You can always point to each indicator to get a tooltip.

| Warning
| Not expected
| OK
| Empty
| Wrong type
| Missing

In this Section

- Tool Box for Synchronized tightening
- Tool Box for FlexSystem
- Channel Numbering

# Tool Box for Synchronized tightening

## Controllers

There are two types of controllers:

- PF6000/PF8 Sync Reference

- PF6000/PF8 Sync Member

A maximum of 63 Sync Member controllers can be added to a hardware layout configuration. The Sync Reference controller is always the first, the Sync Member controllers and tools need to be added after this.

## Tool Box

The Tool Box contains the two controller types and all the tools which are supported. There is a drop-down list to be able to filter on specific tool types.

Only the supported tools, seen in the table below, can be added to the Hardware Layout Configuration from the Tool Box. Unsupported tools connected to a Synchronized tightening controller will be displayed with a Tool not supported icon in the Hardware Layout Configuration. These tools will be shown in ToolsTalk 2 in their current position within the Synchronized tightening configuration and this position cannot be changed in the Hardware Layout Configuration workspace. If the unsupported tool is deleted from this workspace, the user can Push the configuration to the controller to add the tool before continuing with the Hardware Layout Configuration setup.

The tools can only be added to a controller that doesn't already have a tool connected.

Tool Family | Supported Models
Tensor STR | ETV, ETD, ETP
Tensor ST | ETV, ETD, ETP
Tensor SL | ETV, ETD, ETP, ETF
Tensor SR | ETV, ETD, ETP
QST | All

# Tool Box for FlexSystem

The toolbox contains all valid products for the controller version.

Carrier

There are two types of carriers:

- 3-slot

- 6-slot

You can have maximum 11 carriers in your configuration. The carrier with controller is always the first carrier. All the carriers need to be dropped after the first carrier.

Controller

The controller can only be added to the first slot of the first carrier. It is not possible to add the Controller product to any other slots in the system.

Drive

The drive can be placed in all free slots except the first carrier’s first slot or slot with channel number 65. See section on channel numbering for further information.

You can have maximum 64 drives in your configuration.

Blank

The blank can be placed in all free slots except the first slot of any carrier.

Fan

The fan product can only be dropped at the top of a carrier. A 3-carrier has one fan module and a 6-carrier has two fan modules.

E-Stop

There are three different types of E-Stop:

- E-Stop ASM

- E-Stop Entry

- E-Stop ByPass

The first two E-Stops can only be dropped in the configuration’s first carrier. All other carriers can only have an E-Stop ByPass.

Tool

The Flex system can only add QST tools. The tool can only be dropped on a Drive that does not have a tool connected.

# Channel Numbering

When a system is powered up a channel number (also named drive index) will be assigned to each FlexDrive. The drive index is dependent of which FlexCarrier and where in the FlexCarrier the FlexDrive is mounted.

Example: Channel numbering

Carrier 1 | Slot 1 | Slot 2 | Slot 3 | Slot 4 | Slot 5 | Slot 6
Controller | Drive | Drive | Drive | Drive | Drive
Drive index | - | 2 | 3 | 4 | 5 | 6

Carrier 2 | Slot 1 | Slot 2 | Slot 3 |  |  |
Drive | Drive | Drive |  |  |
Drive index | 7 | 8 | 9 |  |  |

# Working with the Tightening Program Tab

Viewing the list of Tightening Programs

1. Select a controller in the Plant structure workspace .

2. On the toolbar, select Tightening program .

   The Tightening program overview shows a list of tightening programs.

The list has the following columns:

List of tightening programs
Column | Description
--- | ---
Check box | Select a tightening program by marking a check box.
Name | Name of the tightening program. A Push indicator can be visible in adjacent to the name indicating that changes have been made, but not yet pushed to the controller.
Strategy | The tightening strategy selected for the tightening program.
Description | Description of the tightening program as described in the Properties field of each tightening program.
Library Link | Indicates if the program is linked to a Global tightening program in the tightening program library.
Target | The final tightening target is either expressed as a torque value or as an angle value.
Last changed | Last changes made, expressed in ToolsTalk 2 time.
Changed by | Indicates which user made the last changes.
Controller updated | Last changes pushed to a controller, expressed in controller time.
Controller updated by | Indicates which user made the last push to the controller.
Approval status | Approval status of the tightening or loosening program

The field Changed by can be a registered ToolsTalk 2 user, as it is done via the ToolsTalk 2 GUI.

The field Controller updated by can be a registered ToolsTalk 2 user, via the web-GUI or via the controller-GUI.

The following columns can be filtered by texts in the search box: Name, Strategy, Description, Target and Changed by.

Command buttons in the tightening workspace
Command | Description
--- | ---
Add | Creates a new tightening program.
Manage | Add to library: Converts a Local tightening program into a Global tightening program. Unlink: Converts a Global tightening program into a Local tightening program: Compare: Compares two selected tightening programs. These must have the same strategy. Export: Exports a selected tightening program. File format is *.json Export to csv: (not available for mutistep) Exports selected tightening program(s). File format is *.csv Delete: Removes selected tightening program(s) from the list. Send for approval: Approve or Reject tightening in the Program Approval tab. Approve: Approves the tightening directly in this configuration view. An approved non-global (Library) tightening program remains editable on controller screen or web HMI. So the program is therefore editable outside of TT2. When using this functionality it is recommended to close the web HMI. Reset to draft: Changes the approval status to Draft.

In this Section

- Tightening Program Menu
- Multistep Tightening Introduction
- Adding a Multistep Program
- Copying and Pasting tightening programs
- Importing a Multistep Program
- Deleting a Multistep Program
- Comparing Multistep Tightening Programs
- Global Tightening Program
- Tightening Editor
- Multistep Tightening Program Properties
- Approval Statuses

# Tightening Program Menu

Each row in the list represents one multistep tightening program.

Header | Description
--- | ---
Check box | Used for selecting a specific tightening program.
Name | A user-defined name.
Strategy | Selected strategy for the tightening program.
Library link | Linked to global library Yes/No.
Target |
Last changed | Time expressed in ToolsTalk 2 time.
Changed by | Tightening program changed by <user>
Controller updated | Controller updated, expressed in controller time.
Controller updated by | Controller updated by <user>
Approval status | Approval status of the tightening or loosening program

Tightening program workspace command buttons
Command | Description
--- | ---
Add | New. Creates a new tightening program. Import. Import a tightening program. File format is *.json
Manage | Add to library: Converts a Local tightening program into a Global tightening program. Unlink: Converts a Global tightening program into a Local tightening program. Compare: Compares two selected tightening programs. These must have the same strategy. Export. Exports a selected tightening program. File format is *.json Delete. Removes selected tightening program(s) from the list.

# Multistep Tightening Introduction

A multistep tightening is a tightening done in several steps. The number of steps and the type of the steps vary depending on the tightening to be done.

Often a multistep tightening is run with many tools in parallel, for example, to tighten the five bolts holding a wheel on a car. To make sure the tightening is done properly all the tools must run synchronized so they reach the same torque at roughly the same time.

To make sure this synchronization happens, the multistep program uses synchronization points. At a synchronization points each tool stop. When all of the tools have reached the synchronization point the tools continue with the next step until they reach the next synchronization point.

The number of steps between the synchronization points is flexible and could vary from 1 to 10. It is not necessary for the multistep programs running on different tools to have the same number of steps between the synchronization points. A multistep tightening program is highly configurable and the actual layout of different multistep programs can vary wildly.

Example: Multistep tightening program

Pos |
A | Step 1 and 2 engage the tool on the bolt.
B | A fast rundown is made with step 3.
C | Step 4 and 5 run the actual tightening
D | Step 6 is used to release the socket from the bolt.

Restrictions
Restrictions are used to make sure the tightening stops if something unexpected occurs. These restrictions could, for example, test that a maximum set torque is not reached or that a part of the multistep tightening does not take too long to run. Every step can have up to four restrictions each.

Monitors
Monitors are used to verify that the tightening was made according to the specification. This can be, for example, angle limits or torque limits. Every step can have up to four monitors each.

Sync mode
With sync mode it is possible to run different tightening programs on different tools at the same time. The main function of the sync mode is to define the tools that shall be included in a synchronized tightening and specify the tightening program each tool shall run.

Reject management
If something goes wrong in a tightening program the program can either do a repair or the program is terminated.

The reject management works like this, when all tools have reached a synchronization point the status of each tool and the total status is evaluated. If all channels at the synchronization point are OK the program continues with the next step. If something is NOK the program will repair or terminate according the set action.

In this Section

- Tightening Program History

# Tightening Program History

ToolsTalk 2 keeps track of the last ten changes that have been made to a tightening program and pushed to the controller:

- A printed report with all original tightening program parameter settings and the changes made.

- A printed report with all current tightening program parameter settings.

- A list of revision history for the tightening program. It is possible to quickly change to a previously tightening program parameter setting by selecting the desired version and clicking the Replace command button.

The revision history is created when a Push command is executed and the controller is updated from ToolsTalk 2.

1. Select a controller in the Plant structure workspace .

2. Select the Tightening program icon .

3. Double-click on a tightening program in order to open the tightening program configuration workspace.

4. Select the History command button.

   The Managing Tightening Program History pop-up window opens.

Viewing a previous tightening program

1. Select the Changes tab.

   The left side of the window shows a list of revision histories.

2. Click one row to select a revision.

   The right side of the window shows a detailed list of the configuration parameters.

   It is possible to compare two tightening program revisions. After selecting the first tightening program, hold the Control (Ctrl) button on the keyboard and select a second tightening program. The right side window then shows both settings. It is possible to show all parameters, or only the parameters that differ by selecting the Show only changes box.

3. When done, select the Close command button.

   The pop-up window closes.

Comparing two stored tightening programs

1. Select the Changes tab.

   The left side of the window shows a list of revision histories.

2. Select two tightening programs from the stored tightening programs.

   A comparison between the two selected tightening programs will be displayed in the column to the right.

3. Select the Close command button.

   The pop-up window closes.

Switching to a previous tightening program

1. Select the Changes tab.

   The left side of the window shows a list of revision histories.

2. Click one row to select a revision.

   The right side of the window shows a detailed list of the configuration parameters.

3. Select the Replace command button.

4. Select the Close command button.

   The pop-up window closes.

Printing a tightening program history report

1. Select the Report tab.

2. Select the Print command button.

   The print dialog window opens for printing.

3. When done, Select the Close command button.

   The pop-up window closes.

The printed report contains a complete list of all configurations and parameter values. In addition to this, it lists all the revisions and the changes made in each of the revisions. This provides a complete history of what has been done in the Tightening program. The time stamp shows when changes were made, or when a push was done from ToolsTalk 2.

Relevant Information

- Pushing Configurations to a Controller

# Adding a Multistep Program

1. Select the Add button. The Create new Tightening program dialog window opens.

2. Enter tightening program name, index number (only valid for tightenings), and select tightening strategy Multistep. The tightening program will be issued with the next sequential number in the list of programs, if no active selection of the index is made.

3. Select the Add button.

# Copying and Pasting tightening programs

It is possible to copy and paste tightening programs. The following rules applies for controllers in the fixtured family (FlexSystem, PF8 Synchronized tightening and PF6000 Synchronized tightening):

- Copy and paste can be done on the same controller.

- Copy and paste can be done between fixtured controller types from version 3.8 and above.

- It is not possible to copy and paste from a newer controller to an older version.

Validation errors that need to be corrected may occur if copy and paste is done between different controller types.

A copy of a tightening program always includes everything as for example attached or associated programs and links.

Examples:

A copy of a tightening program with a loosening program attached > The paste create a tightening program and a loosening program attached.

Copying and pasting

1. Select a controller in the plant structure.

2. Select Tightening Program. The workspace area shows all the available programs or sequences.

3. Right-click on a single row or select check boxes for several rows, right click and select Copy.

4. To paste the copy into the same controller, right-click anywhere in the empty workspace area and select paste. The copy is added to the first available position in the existing list.

   If there is no space in the list for the copy, the whole operation will fail.

   To paste the copy into another controller; select a controller in the plant structure and then select the applicable workspace. Right-click in the workspace and select paste.

   It is also possible to paste a copy into the Program Templates library workspace.

5. Double-click the pasted copy to open and modify it.

# Importing a Multistep Program

The same rules as for copy and paste of tightening programs are applicable for export and import for multistep programs, refer to Copying and Pasting tightening programs

1. Select the Add button. The Create new Tightening program dialog window opens.

2. Select the Import tab.

3. Select Open file and select the file from the desired location. The file must have the format <template_name>.json. Select Open.

# Deleting a Multistep Program

1. For each Multistep program to be deleted, mark the check box in the leftmost column in the workspace area.

2. Select the Manage command button, then Delete from the drop-down list.

3. The selected Multistep program(s) are removed and the list is updated.

# Comparing Multistep Tightening Programs

In Tightening Programs, two different Multistep Programs can be compared.

1. Go to the Tightening Program tab , in the list of programs select the corresponding check boxes of the Tightening Programs to be compared.

   Only Multistep Programs with the same operation mode can be compared, Tightenings with Tightenings and Loosenings with Loosenings.

2. Select the Manage command button, and then select Compare.

   The workspace displays graphical images of the actual Multistep Program Steps, and in the Compare area, the parameters for the two selected tightening programs are shown.

3. In the Compare window, the specific parameter values that differ will be displayed in red. Select the check box Show only differences to display only the parameter values that differ. The Properties and Steps sections which include parameters that differ will be marked with a blue indicator.

It is not possible to edit the two Multistep Programs that are being compared and configuration errors or warnings will not be shown.

# Global Tightening Program

A tightening program can be either Local or Global. If a tightening program is global, it is indicated with a Yes in the Library link column in the list of tightening programs.

A Local tightening program is valid for a single controller.

Viewing the list of Tightening Programs

1. Select a controller in the Plant structure workspace .

2. On the toolbar, select Tightening program .

   The Tightening program overview shows a list of tightening programs.

A Local tightening program can only be edited via the Tightening program tab.

A Local tightening program is not visible in the Tightening program library .

A Global tightening program is valid for multiple controllers subscribing to the tightening program. The Global tightening programs are located in the tightening program library.

Accessing the Library

1. Select Library in the left-side menu bar.

2. Select Tightening program library in the top menu bar.

   The Tightening program library shows a list of global tightening programs.

If a controller subscribes to a Global tightening program, it is visible in Tightening program , but editing is prohibited.

A Global tightening program can only be edited via the Tightening program library .

# Tightening Editor

## Buttons

Name | Description
--- | ---
Display | Repair - Show or hide the repair area. Terminate - Show or hide the terminate area. Monitor - Show or hide the step monitors. Restriction - Show or hide the step restrictions. Direction Arrow - Show or hide the direction arrow. Display DropArea Help - Show or hide the DropArea help.
Zoom in | Zooms in on the tightening program.
Zoom out | Zooms out from the tightening program.
Fit to screen | Fits the whole tightening program to the drag and drop area.
Delete | Deletes the selected item.

## Repair Area

The steps in the repair area show the repair path to be followed if the status at a synchronization point is NOK.

A repair path always starts and ends at a synchronization point. Where the repair path should re-enter the tightening path is flexible, but the repair path must always go back towards the beginning of the program.

Only one repair path can start in each synchronization point, but several repair paths may end at the same synchronization point.

The number of steps to run in the repair path can be between 1 and 3.

It is not possible to define a repair path from the start of the program.

Example: Repair paths

A | Repair path from the first synchronization point to the start of the program.
B | Repair path from the third synchronization point to the second synchronization point.

## Tightening Area

The tightening area includes the tightening path, i.e., the steps and synchronization points in the multistep tightening program excluding repair and termination paths.

## Number of Tightening Steps, Restrictions and Monitors Allowed

| Number of Steps Allowed | Number of restrictions Allowed | Number of monitors Allowed
--- | --- | --- | ---
PF6000/PF8 | 16 | 8 | 8
PF6000/PF8 Step Sync | 25 (excluding syncpoints and repair- and termination paths) | 8 | 8
Flex | 25 (excluding syncpoints and repair- and termination paths) | 8 | 8
IxB | 16 | 5 | 8

## Terminate Area

The steps in the terminate area shows the terminate path followed if the status at a synchronization point is fatal. After the termination path is done the tightening is ended. A termination path always starts at a synchronization point. Only one termination path can start in each synchronization point.

The number of steps to run in the termination path can be between one and three.

It is always possible to terminate from all synchronization points. If no termination path is defined, the program will go directly to the end without running any other steps.

Example: Termination path

A | Termination path from the first synchronization point to the end of the program.
B | Termination path from the third synchronization point to the end of the program.

## Configuration

1. Select on the step, restriction or monitor and click on Configuration at the bottom of the screen to open the Configuration field. To select multiple steps, use Ctrl.

   The Configuration field contains different parameters for the steps, monitors and restrictions based on which step, monitor or restriction is selected in the repair area.

2. Enter the required parameters.

   To delete a monitor or restriction, select Delete which is present in that field.

## Using speed shifts

You can define 1-5 angle triggers or torque triggers during a step, where the speed will shift.

The speed shifts can be added in the Configuration field.

Within one step, all the speed shift triggers are based on the same property, i.e. either torque or angle. They cannot be mixed within one step.

To add a speed shift:

1. In the dialog box of a step that can have speed shifts, click Add speed shift and choose an angle range or a torque range. The Speed Shift Angle/Torque fields open.

2. Add values according to the table below.

Parameter | Description
--- | ---
Angle/Torque trigger | Must be > 0.
Speed | Must be > 0.
Speed ramp type | Hard or soft.

The Torque triggers and Angle triggers must be less than the step target, depending on the type of the step and the trigger type.

The Torque trigger and Torque speed also validate against the Max torque and Max speed of the tool. A warning or error indicator occurs whenever the Speed Shift settings exceed either the tool max values or step max values.

It is possible to push the settings to the controller when a tightening program has a warning, but not when a tightening program has an error(fault) indicator.

## Tool Box

The Tool box includes:

- Steps: including Sync point and Utilities

- Monitors

- Restrictions

- Result Reporters

- Templates

## Drag and drop area shortcut keys

Shortcut key | Description
--- | ---
Space bar + cursor | Move Drag and drop area.

## Drag and drop area functions

Function |  | Description
--- | --- | ---
Add step |  | Grab a step in the Tool box. Drag the step to the desired position. Possible positions are indicated by a light blue indication arrow.
___________ | __________________________ | _________________
Mark a step |  | Click on a step to mark it.
___________ | __________________________ | _________________
Move a step |  | To move a step, click on the step and hold the button pressed while moving.
___________ | __________________________ | _________________
Copy step |  | To copy a step, click the Ctrl button and drag and drop the step.
___________ | __________________________ | _________________
Add repair path |  | Place the step above the synchronization point from where the repair part should start.
___________ | __________________________ | _________________
Add repair step | OR | Place a step in the Repair area to add a repair step. Possible positions are indicated by a light blue indication arrow. or Place the step above the synchronization point from where the repair part starts. The step is then placed before the first step in the repair path.
___________ | __________________________ | _________________
Add terminate path |  | Place the step below the synchronization point from where the termination part should start.
___________ | __________________________ | _________________
Add terminate step | OR | Place a step in the Terminate area to add a terminate step. Possible positions are indicated by a light blue indication arrow. or Place the step below the synchronization point from where the termination part starts. The step is then placed before the first step in the termination path.
___________ | __________________________ | _________________
Move endpoint for repair path. |  | Click the small arrow to move the endpoint of the repair path.
___________ | __________________________ | _________________
Add restriction and monitor |  | Grab a restriction or a monitor in the Tool box. Drag the restriction or monitor to desired step. Possible steps to add a restriction or monitor to, are indicated by changing to a lighter blue color.
___________ | __________________________ | _________________
Forbidden placement |  | A red arrow indicates that it is not possible to place a step.

In this Section

- Tightening Steps
- Step Monitors
- Step Restrictions
- Sync Point
- Utilities
- Result Reporters
- Multistep Template

# Tightening Steps

The availability of tightening steps, monitors and restrictions depends on the license installed on the controller.

## General Parameters

The following step parameters are common for many of the step types. The parameters are set in the step properties window which is displayed when selecting a step in the tightening program.

Parameter | Description
--- | ---
Name | Name of the step.
Rotational direction | Each of the tightening steps can run either forward, that is to make a tightening, or reverse, to loosen the screw slightly. The arrows indicate this direction. Many of the tightening steps have a direction hard-coded to forward, for example Tighten to Angle, or Tighten to Torque. Steps such as Loosen to Angle or Loosen to Torque have their direction automatically set to reverse. The reverse setting is not allowed for tools configured with Gear Front Attachment (GFA) of type open end. The tightening direction of the tightening program must be the same as the tightening direction of the open end tool for a tightening to be allowed to be run. It is possible to assign a loosening program to a tightening program for an open end tool, but if the direction switch is set to run the loosening program, the tool will be locked.
Step category | For each step, there is an option to choose a step category. By selecting step category, the NOK tightenings will be listed in the event result view with related detailed status together with the corresponding multistep error information. If no selection is made, the detailed status will be set to uncategorized multistep error. The related detailed status can be customized.
Angle window | A joint is considered Hard if the screw is tightened to its full torque and it rotates 30 degrees (or less) after it has been tightened to its snug point. A Soft joint rotates 720 degrees or more after it has been tightened to its snug point. The hardness parameter defines the Angle Window for the gradient calculation. The harder the joint - the smaller the angle window.
Speed Ramp / Acceleration (only available in ToolsTalk 2) | For most of the steps it is possible to specify how the acceleration to the target speed should be achieved. Three different settings are possible; Hard, Soft and Manual. The acceleration defined will be used whenever a step is started. Regardless whether the tool is already running with speed at the beginning of the step, the ramp will be used to accelerate to the target speed of the step. This will be the case even if the speed at the start of the step is higher, or lower than the target speed.
Speed ramp - Hard and Soft mode | Hard: 2000 rpm/s (Speed Ramp between 1000 and 10000 rpm/s is a Hard acceleration.) Soft: 500 rpm/s (Speed Ramp between 200 and 1000 rpm/s is a Soft acceleration.)
Speed ramp - Manual mode | Speed: Default value: 60 rpm Minimum limit: > 0 Maximum limit: ≤ Tool Max Speed Acceleration: Default value: 500 rpm/s Minimum limit: > 0 Maximum limit: ≤ Tool Max Acceleration
Using speed shifts | 1−5 angle triggers or torque triggers can be defined during a step, where the speed will shift. Within one step, all the speed shift triggers are based on the same property, that is either torque or angle. They cannot be mixed within one step. The Torque triggers and Angle triggers must be less than the step target, depending on the type of the step and the trigger type. The Torque trigger and Torque speed also validate against the Max torque and Max speed of the tool. A warning or error indicator occurs whenever the Speed Shift settings exceed either the tool max values, or step max values. The Torque triggers and Angle triggers must be less than the step target, depending on the type of the step and the trigger type. The Torque trigger and Torque speed also validate against the Max torque and Max speed of the tool. A warning or error indicator occurs whenever the Speed Shift settings exceed either the tool max values, or step max values. It is possible to push the settings to the tool when a tightening program has a warning, but not when a tightening program has an error (fault) indicator. The speed shifts can be added in the Configuration field. To add a speed shift: In the dialog box of a step that can have speed shifts, select Add speed shift. Then, select an angle range or a torque range. The Speed Shift Angle/Torque fields open. Add values according to the table below: Angle/Torque trigger: Must be > 0 Speed: Must be > 0 Speed ramp type: Hard or soft
Brake type | The braking behavior of a multistep tightening program can be controlled at two possible locations in the program: in a step preceding a reversal of direction of the tightening, and/or at the final step of the tightening program. At other locations in the tightening program, the braking parameters will not be available in the step's general settings. Braking can be set to either Ergo stop or Inertia. Inertia will brake the tool completely, while Ergo stop will allow for a more ergonomic slowing down of the tightening. Inertia has no additional parameters. Ergo stop parameters: Adaptive brake: Set the Adaptive Brake to On or Off Ramp time: Only available when Adaptive Brake is set to Off. Insert time in ms.
Exclude in MCT mode | The Exclude in MCT mode option can be turned on for steps in a Multistep program. When using the MCT mode for a Multistep program, steps with Exclude in MCT mode turned on will be excluded. Setting the Exclude in MCT mode option to on in such a way that there is no break before a wait step or direction switch will result in an error in runtime when in MCT mode. Termination Paths and Repair paths are ignored on fixtured systems, i.e. if they are triggered the tightening will be marked as NOK MC tightening. MCT mode is only to be used when testing. Make sure MCT mode is disabled before returning the tool to the production line.

The following tightening steps are not supported for tools configured with Gear Front Attachment (GFA) of type open end:

- A - Tighten to Angle / Loosen to Angle

- TrR - Loosen to Trigger Release

- T - Tighten to Torque / Loosen to Torque

- E - Engage

- SR - Socket Release

- DT - Tighten to DynaTork

- TPT - TensorPulse Tighten to Torque / Loosen to Torque

- IT - Impulse Tighten to Torque / Loosen to Torque

- IA - Impulse Tighten to Angle / Loosen to Angle

- AP - Adaptive Pulse

- ITrR - Impulse Loosen to Trigger Release

## Trace Settings

When the trace configuration is enabled on the program level, the trace resolution can be configured on step level. The setting for Trace Setting defines how the sampling should be done on each specific step.

Parameter | Description
--- | ---
Trace Setting | Program: Use the settings as defined on program level. Manual: The trace sample type from the program level will be used, that is, Time or Angle. Using a different sample rate will override the setting on the program level.
Sample Time | Choose the sample time from the drop-down list (0.25 - 1000 ms)
Sample Angle | Choose the sample angle from the drop-down list (0.25 - 20 degree)

With this trace recording the sample rates will not be the same in all the steps, instead the sample rate depends on the configuration in each step. This means the trace is divided into one trace for each step.

The maximum number of samples in a trace is 4096.

If a tightening produce more than 4096 values a down-sampling will take place. This is done by removing every second trace sample from the whole tightening and when continue the recording with half the resolution. This process will be repeated every time the 4096 sample limit is reached.

If more than 2048 in total was recorded, this process will result in a trace between 2048 and 4096 samples.

If the limit if 4096 samples is reached the configured trace sample times will no longer be followed. Instead the sample times will be doubled or quadrupled etc., depending on how many times the down sampling has taken place. Since all steps are down sampled the relation between the steps will still be the same though. If a step was configured with double sample time compared to another step, this will still be the case in the final trace regardless how many times a down-sampling has occurred.

Trace channel | Note
--- | ---
Torque | Available for all tools equipped with a torque transducer
Angle | Available for all tools
Torque Second | Only available for tools with two torque transducers
Angle Second | Only available for tools with two angle transducers
Current | Available for all tools
Gradient | Available if some step/restriction/monitor produces the gradient values

Available tools for each system type
Power Focus 6000 / Power Focus 8 | Power Focus 6000 Synchronized tightening / Power Focus 8 Synchronized tightening | Flex | IxB
--- | --- | --- | ---
ST | ST | QST | IxB
STR | STR |  |
SL | QST |  |
QST |  |  |
STB |  |  |
IxB |  |  |
Power Focus Connect |  |  |
XB |  |  |

Tightening Steps
Tools
Search

# A – Tighten to Angle / Loosen to Angle

Tools
ES STR SL ST SR QST STB IXB

A – Tighten to Angle

This step runs the tool until the target angle is reached. The target angle is measured from the start of the step.

A – Loosen to Angle

This step runs the tool with the speed n in the backward direction until the angle target is reached. The target angle is measured from the start of the step.

This step is not supported for tools configured with Gear Front Attachment (GFA) of type open end.

Parameters

Parameter | Description
--- | ---
Target angle | The angle target. Must be > 0.
Speed | Default: 60 rpm.
Speed ramp type | Hard, soft, or manual. Default: Hard. If you select Manual, the Speed ramp field opens.
Speed ramp | If Speed ramp type is Manual, this field opens. Default: 500 rpm/s.
Brake (Valid only for Power Focus 6000 Synchronized tightening, Power Focus 8 Synchronized tightening and Flex). | If On the tool will be stopped when the target is reached. If Off the program goes directly to the next step without stopping the tool.

Point and click on image to see more information:

A | Target Angle

## Microvideo

A - Tighten to Angle / Loosen to Angle

# DI – Run Until Digital Input

Tools
ES STR SL ST SR QST

This steps runs the tool, in the direction defined by parameter Direction, until the input specified by Digital Input goes high or low depending on the value of Stop Condition.

Parameter | Description
--- | ---
Direction | Forward, or Backward
Digital Input | One of the following local digital inputs on the controller can be selected: Local DI 1 Local DI 2 Local DI 3 Local DI 4
Brake (Valid only for Power Focus 6000 Synchronized tightening, Power Focus 8 Synchronized tightening and Flex). | If On the tool will be stopped when the target is reached. If Off the program goes directly to the next step without stopping the tool.
Stop Condition | Falling edge: The steps runs until a falling edge is detected after step start. Rising edge: The steps runs until a rising edge is detected after step start. Any edge: The step runs until a falling or a rising edge is detected after step start. Low: The step runs until low value is detected. High: The step runs until high value is detected.
Speed (rpm) | Default: 60 rpm.
Speed ramp type | Hard, soft, or manual. Default: Hard. If you select Manual, the Speed ramp field opens.
Speed ramp | Available if Speed ramp type is Manual. Default: 500 rpm/s.

## Microvideo

DI - Run Until Digital Input

# DT – Tighten to DynaTork

Tools
ES STR SL ST SR QST STB IXB

This step is not supported for tools configured with Gear Front Attachment (GFA) of type open end.

This step runs the tool with speed n in the forward direction until the Target torque is reached. The tool will then hold the current constant at the DynaTork Percentage of Target torque during the DynaTork time.

To avoid overheating of the tool, it is strongly recommended to never run DynaTork to more than 40% of the maximum torque of the tool.

Parameter | Description
--- | ---
Target torque | The torque target. Must be > 0.
DynaTork Time | The time DynaTork will be active.
DynaTork Percentage | The percentage of Torque target.
Speed ramp type | Hard, soft, or manual. Default: Hard. If you select Manual, the Speed ramp field opens.
Speed ramp | If Speed ramp type is Manual, this field opens. Default: 500 rpm/s.
Speed (rpm) | Default: 60 rpm.
Brake (Valid only for Power Focus 6000 Synchronized tightening, Power Focus 8 Synchronized tightening and Flex). | If On the tool will be stopped when the target is reached. If Off the program goes directly to the next step without stopping the tool.

Point and click on image to see more information:

A | Target Torque
B | Torque level retained during DynaTork Time
C | Percentage of Ts
D | Percentage of Ts
E | Torque level retained during DynaTork Time
F | DynaTork Time

## Microvideo

DT - Tighten to DynaTork

# E - Engage

Tools
ES STR SL ST SR QST IXB

This step is not supported for tools configured with Gear Front Attachment (GFA) of type open end.

This step runs the tool in both directions until the socket engages the screw. The step continues until Target torque or Target angle is reached, provided that Continue if not Engaged is set to Yes. If Target Angle is reached in any direction, the direction is reversed. Limit the search iterations by entering Max Engage Attempts. If Target Torque is reached in any direction the step will finish with OK status.

## Microvideo

E- Engage

# Ext - External Result

Tools
ES STR SL ST SR QST STB IXB BCP BCV External Tool

External result is a strategy used when an OK tightening is indicated by an external digital signal (and not by torque or angle values measured during tightening). This external signal can be provided through any means that can provide a digital signal into the controller (e.g through the I/O bus).

When the signal is sent, the result view (logged data) will show the value of the Target parameter provided in the tightening program (specified torque value, angle value, or text string). These (torque and angle) values do not represent actual measured values, but only inserted text.

Parameter | Description
--- | ---
Torque <Target torque> | Numerical value for desired displayed target torque value. A signal could for example come from a Click Wrench and display <Target torque>.
Angle <Target angle> | Numerical value for desired displayed target angle value. A signal could for example come from a Click Wrench and display <Target angle>.
Text | Alphanumerical string for desired displayed text. For example: "Oil has been changed".

# MWR - Mechatronic Wrench

Tools
MWR

Mechatronic Wrench is a specialized step that can be used only in conjunction with the Mechatronic Wrench (MWR).

This step cannot be used in combination with other steps. No restrictions can be used with this step. By default, the step has three monitors: Peak Torque, Angle, and Click.

Parameter | Description
--- | ---
Loosening limit | Numerical value for negative torque (i.e. torque in the loosening direction) at which point the tightening result is marked as NOK (False direction of tightening (loosen)); in Nm.
Tool Size | Numerical value for the specific length of the end fitting tool installed on the MWR-TA; in mm.
Tool Bend | Numerical value for the end fitting tool installed on the MWR-TA; in °/Nm.
Rehit Angle Window | Numerical value for the angle for determining if the screw was already tightened if the torque is reached; in °.
Max Angular Rate | Numerical value for the max rate at which the screw can be tightened; in °/s.

# RD – Rundown

Tools
ES STR SL ST SR QST IXB

Rundown step is the part of the tightening from when the screw enters the thread until just before the screw head touches the underlying surface and snug point is reached. The torque required during rundown does not contribute to any clamping force.

This step runs the tool with the speed in the forward direction, and depending on the Rundown Type, Torque or Snug the step behavior is as follows:

Rundown Type: To Torque: The step stops when the specified target torque is found.

Rundown Type: To Snug: The snug gradient calculation starts at the specified torque trigger level Tt. If no torque trigger is set the gradient calculation is started at the start of the step.

The slope calculation is made between two angle points Ad degrees apart and is calculated as: (Tn – Tn-1) / (An – An-1) and as soon as two slopes after each other are larger than TSLOPE the snug point is found.

Parameter | Description
--- | ---
Rundown type | To Torque or To Snug.
Target torque | Default: "not set". Must be > 0.
Speed | Default: 60 rpm. Must be > 0.
Speed ramp type | Hard, soft, or manual. Default: Hard. If you select Manual, the Speed ramp field opens.
Speed ramp | If Speed ramp type is Manual, this field opens. Default: 500 rpm/s.
Trigger Torque | If Rundown type is To Snug, the Trigger torque field is displayed. Default: "not set". Must be > 0.
Delta Angle | If Rundown type is To Snug, the Delta angle field is displayed. Default: "0". Must be > 0.
Torque Rate | If Rundown type is To Snug, the Torque rate field is displayed. Default: "0". Must be > 0.
Brake (Valid only for Power Focus 6000 Synchronized tightening, Power Focus 8 Synchronized tightening and Flex). | If On the tool will be stopped when the target is reached. If Off the program goes directly to the next step without stopping the tool.

Point and click on image to see more information:

A | Snug Point
B | Angle Delta
C | Torque Slope
D | Torque Target
E | Torque Trigger

# SR - Socket Release

Tools
ES STR SL ST SR QST STB IXB

This step is not supported for tools configured with Gear Front Attachment (GFA) of type open end.

This step runs the tool with speed n in the backward direction until the target angle is reached. The target angle is measured from the start of the step.

This step is only allowed to use as the last step in the tightening path of a multistep tightening program. However, it is possible to add a sync point after this step.

Parameter | Description
--- | ---
Target angle | The angle target. Default: 3 degrees, must be > 0
Speed ramp type | Hard, soft, or manual. Default: Hard. If you select Manual, the Speed ramp field opens.
Speed ramp | If Speed ramp type is Manual, this field opens. Default: 500 rpm/s.
Speed | Default: 60 rpm.

# SZP - Set Zero Position

Tools
ES STR SL ST SR QST

The step Set Zero Position sends out the signal set zero position to the tool. The position is repeated once every 360 degrees.

With the steps Loosen to Zero Position or Tighten to Zero Position it is possible to return the tool to zero position.

This step does not have any parameters.

The zero position is a specific position stored with either a “Set Zero Position” step or the signal “Set Zero Position”. The position is repeated once every 360 degrees.

# T - Tighten to Torque / Loosen to Torque

Tools
ES STR SL ST SR QST STB IXB

T – Tighten to Torque

This step runs the tool with the programmed speed in forward direction until the target torque is reached.

Parameter | Description
--- | ---
Target torque | The torque target. Must be > 0.
Speed ramp type | Hard, soft, or manual. Default: Hard. If you select Manual, the Speed ramp field opens.
Speed | Default: 60 rpm. Must be > 0.
Speed ramp | If Speed ramp type is Manual, this field opens. Default: 500 rpm/s.
Brake (Valid only for Power Focus 6000 Synchronized tightening, Power Focus 8 Synchronized tightening and Flex). | If On the tool will be stopped when the target is reached. If Off the program goes directly to the next step without stopping the tool.

## Microvideo

T - Tighten to Torque

T – Loosen to Torque

This step is not supported for tools configured with Gear Front Attachment (GFA) of type open end.

This step runs the tool with the speed in the backward direction. For the step to be active, the torque must first exceed 110 % of the Target torque. The Target torque should be set to a positive value. After reaching the target torque, the step runs until the torque drops below the target torque.

Parameter | Description
--- | ---
Target torque | The torque target. Must be > 0.
Speed ramp type | Hard, soft, or manual. Default: Hard. If you select Manual, the Speed ramp field opens.
Speed | Default: 60 rpm. Must be > 0.
Speed ramp | If Speed ramp type is Manual, this field opens. Default: 500 rpm/s.
Brake (Valid only for Power Focus 6000 Synchronized tightening, Power Focus 8 Synchronized tightening and Flex). | If On the tool will be stopped when the target is reached. If Off the program goes directly to the next step without stopping the tool.

Point and click on image to see more information:

A | Target Torque

# T&A – Tighten to Torque and Angle

Tools
ES STR SL ST SR QST STB IXB

This tightening step runs the tool with the given speed in the forward direction until both the target torque and the target angle are reached.

The torque measurement starts at the beginning of the step.
If the torque trigger is NOT set, the angle measurement starts at the beginning of the step.
If the torque trigger is set, the angle measurement starts when the torque trigger is reached.

The step ends when:
Measured Torque >= Target Torque (Ts)
AND
(Measured Angle - Angle Measured at Torque Trigger) >= Target Angle (As).

Parameter | Description
--- | ---
Target torque (Ts) | Default value: 0. Must be > 0 and <= Tool Max Torque.
Target angle (As) | Default value: 0. Must be > 0.
Torque Trigger (Tt) | Default value: NOT set. Must be > 0 and < Target torque (Ts).
Speed (n) | Default: 60 rpm. Must be > 0 and <= Tool Max Speed.
Speed ramp type | Hard, soft, or manual. Default: Hard. If you select Manual, Speed ramp type opens automatically.
Brake (Valid only for Power Focus 6000 Synchronized tightening, Power Focus 8 Synchronized tightening and Flex). | If On the tool will be stopped when the target is reached. If Off the program goes directly to the next step without stopping the tool.

Point and click on image to see more information:
Tightening to Torque AND Angle, without Torque Trigger set

A | Target Torque
B | Target Angle

Point and click on image to see more information:
Tightening to Torque AND Angle, with Torque Trigger set

A | Target Torque
B | Torque Trigger
C | Target Angle

# T|A – Tighten to Torque or Angle

Tools
ES STR SL ST SR QST STB IXB

This tightening step runs the tool with the given speed in the forward direction until either the target torque or the target angle is reached.

The torque measurement starts at the beginning of the step.
If the torque trigger is NOT set, the angle measurement starts at the beginning of the step.
If the torque trigger is set, the angle measurement starts when the torque trigger is reached.

The step ends when:
Measured Torque >= Target Torque (Ts)
OR
(Measured Angle - Angle Measured at Torque Trigger) >= Target Angle (As).

Parameter | Description
--- | ---
Target torque (Ts) | Default value: 0. Must be > 0 and <= Tool Max Torque.
Target angle (As) | Default value: 0. Must be > 0.
Torque Trigger (Tt) | Default value: NOT set. Must be > 0 and < Target torque (Ts).
Speed (n) | Default: 60 rpm. Must be > 0 and <= Tool Max Speed.
Speed ramp type | Hard, soft, or manual. Default: Hard. If you select Manual, Speed ramp type opens automatically.
Brake (Valid only for Power Focus 6000 Synchronized tightening, Power Focus 8 Synchronized tightening and Flex). | If On the tool will be stopped when the target is reached. If Off the program goes directly to the next step without stopping the tool.

Point and click on image to see more information:
Tightening to Torque OR Angle, without Torque Trigger set

A | Target Torque
B | Target Angle

Point and click on image to see more information:
Tighten to Torque OR Angle, with Torque Trigger set

A | Target Torque
B | Torque Trigger
C | Target Angle

# T+A – Tighten to Torque Plus Angle

Tools
ES STR SL ST SR QST STB IXB

This step runs the tool until the target torque is reached. From this point it continues to run an additional target angle.

Parameter | Description
--- | ---
Target torque | The torque target. Must be > 0.
Target angle | The angle target. Must be > 0.
Speed ramp type | Hard, soft, or manual. Default: Hard. If you select Manual, the Speed ramp field opens.
Speed ramp | If Speed ramp type is Manual, this field opens. Default: 500 rpm/s.
Speed | Default: 60 rpm.
Brake (Valid only for Power Focus 6000 Synchronized tightening, Power Focus 8 Synchronized tightening and Flex). | If On the tool will be stopped when the target is reached. If Off the program goes directly to the next step without stopping the tool.

Point and click on image to see more information:

A | Target Torque
B | Target Angle

# TC - Torque Calibration

Tools
QST

This step is only supported for multiple transducer tools.

The Torque Calibration step runs the tool with the specified speed in the forward direction until the torque target is reached.

Parameter | Description
--- | ---
Target torque | Must be > 0.
Speed | Must be > 0. Default: 60 rpm.
Transducer | Torque or Torque 2. Default: Torque. Set to Torque 2 in order to calibrate the front transducer.
Adaptive brake (Valid only for Power Focus 6000 Synchronized tightening, Power Focus 8 Synchronized tightening and Flex). | If On the tool will be stopped when the target is reached. If Off the program goes directly to the next step without stopping the tool.

# ThCT – Thread Cutting to Torque

Tools
ES STR SL ST SR QST STB IXB

The Thread Cutting to Torque function enables tightening where the Rundown torque required is greater than the Rundown complete torque, for example when tightening thin layers of metal using self-threading (or self-tapping) screws. The tool runs in forward direction until the Thread Cutting Angle (Aw) is reached. The thread cutting angle window is measured from when the torque passes Thread Cut Trigger Torque (Ttc) for the first time. From the point where Thread cutting angle is reached, the step continues to run until the Target Torque (Tt) is reached.

Parameter | Description
--- | ---
Target torque | Must be > 0.
Thread Cutting Angle Window | Default: 0. Must be > 0.
Trigger Torque | The angle measurement starts at this trigger.
Speed | Default: 60 rpm. Must be > 0.
Speed ramp type | Hard, soft, or manual. Default: Hard. If you select Manual, the Speed ramp field opens.
Brake (Valid only for Power Focus 6000 Synchronized tightening, Power Focus 8 Synchronized tightening and Flex). | If On the tool will be stopped when the target is reached. If Off the program goes directly to the next step without stopping the tool.

Point and click on image to see more information:

A | Target Torque
B | Torque Trigger
C | Thread Cutting Angle Window

# TPT - TensorPulse Tighten to Torque / Loosen to Torque

Tools
STR IXB

Before using TensorPulse tightening/loosening step, it is mandatory that the following license type is installed on the controller:

- Low Reaction Strategies

TensorPulse is valid only for the following tools: ETV-STR61-100-13, ETV-STR61-70-13, ETV-STR61-50-10, ITB-P.

This step is not supported for tools configured with Gear Front Attachment (GFA) of type open end or closed end.

TensorPulse Tighten to Torque

This step generates tightening pulses in the forward direction, until the torque target is reached.

TensorPulse Loosen to Torque

This step generates tightening pulses in the backward direction, until torque is below torque target.

If running TensorPulse tightening/loosening step, use the necessary PulseDrive socket/adapter.
If TensorPulse tightening/loosening step runs without the PulseDrive socket/adapter, all the tightenings are NOK. The step error “PulseDrive socket/adapter not detected” shows for no PulseDrive socket/adapter.

Parameter | Description
--- | ---
Torque Target - Ts | Torque Target must range from 0 through the maximum torque of the tool.
Pulse Energy - Pe | Pulse Energy is used to control the amount of energy/current in each pulse. Pulse Energy must range from 10% through 100 %. By default, it is set to 100%.
Reaction Force Tuning Factor | Reaction Force Tuning Factor is used to tune the reaction force when running TensorPulse step. It is the power that moves the tool in the opposite direction after each pulse. High tuning factor makes high reaction force and high pulse frequency; low tuning factor makes low reaction force and low pulse frequency. Reaction Force Tuning Factor must range from 0 through 100 %. By default, it is set to 40%.

In the trace, the angle reversal means that the tool rotates backward to enable pulsing, but the bolt head does not necessarily rotate backward because of the PulseDrive socket/adapter.

# TrR – Loosen to Trigger Release

Tools
ES STR SL ST SR STB IXB

This step is not supported for tools configured with Gear Front Attachment (GFA) of type open end.

This step runs in the backward direction until the tool trigger is released (loosen). It can only be used as a last step in a program.

For STB tools, this step is only applicable for loosening programs.

Parameter | Description
--- | ---
Speed | Numerical value for rotation speed; in rpm.
Speed Ramp Type | List of options where speed ramp can be chosen [Hard, Soft, Manual]

# TTC - Tighten to Clutch

Tools
XCB

This step runs the tool with the programmed speed in forward direction until the clutch has been released. When the tool detects the release of the clutch, the step will finish with an OK status.

Tighten to Clutch step is only valid for the XCB tool.

Parameter | Description
--- | ---
Speed shift | Angle or Torque
Trigger angle/Trigger Torque | The trigger angle (in deg) or trigger torque (in Nm) at which the speed shifts.
Speed | The target speed (in rpm)
Speed Ramp Type | Switch to choose the type of speed ramp: Hard, Soft or Manual

# TTTR – Tighten to Trigger Release

Tools
ES STR SL ST SR STB IXB

This step runs until the tool trigger is released (tighten). It can only be used as a last step in a tightening program.

Parameter | Description
--- | ---
Speed | Numerical value for rotation speed; in rpm.
Speed Ramp Type | List of options where speed ramp can be chosen [Hard, Soft, Manual]

# W – Wait

Tools
ES STR SL ST SR QST STB IXB

In this step the tool waits until the Wait Type condition is fulfilled. The tool does not rotate while waiting, but Hold condition can be specified.

Parameter | Description
--- | ---
Wait Type | Time: Wait specified time. Signal (valid only for Power Focus 6000 Synchronized tightening): Wait until a rising edge on the signal Continue Step is received.
Wait Time | Number of seconds the tool will stand still - valid only when Time is selected for Wait Type.
Hold Condition | No hold: The tool is waiting without running. Hold torque: While waiting the tool strives to hold the torque it had when entering the step. Hold position: While waiting the tool strives to hold the position it had when entering the step.

# WP - Wrench Production

Tools
STwrench

Strategy used for the quality test of the tightening performed with the STwrench.

Parameter | Description
--- | ---
Control Strategy | The Wrench Production step type can be configured with the following control strategies. Torque: This strategy guides the operator is reaching the desired target torque. Angle: This strategy guides the operator is reaching the desired target angle. Torque or Angle: This strategy guides the operator is reaching the desired target angle or desired target torque. Torque and Angle: This strategy guides the operator in tightening a bolt until both target torque and angle have been reached. Yield Point: With this strategy, the STwrench detects the yield point automatically. The torque limits specify the range in which the result is OK. Target angle specifies how far beyond the yield point the user may tighten. Loose: This strategy is used to loosen a tightened screw. PVT compensate with snug: This strategy guides the operator in reaching the desired target torque for joints with prevailing torque, when the prevailing torque level is higher than the final target.

Based on the control strategy selected, a combination of some of the parameters listed below will be displayed.

Parameters | Description
--- | ---
Target Torque | Defines the target torque for tightening step.
Measure torque at | Specifies where the torque will be measured. Choose between Peak torque or Peak angle. Peak torque: The torque value will be set to the peak torque value. Peak Angle : The torque value will be set to the torque measured at the peak angle.
Angle search limit | This is an offset that is used to the set the torque result value for a tightening. Measure torque at must be set to Peak Angle for this parameter to be available.
Ratchet time | Numerical value for ratchet time which is by default 5000 ms. This allows the operator to release the torque for a while and recharge during the tightening operation. If the Ratchet time is exceeded the result of the tightening is marked as NOK with the reason "Tightening timeout".
End cycle time | Numerical value in ms to indicate the end cycle time. Applied when torque goes below the rundown complete
Torque correction coefficient | The parameter is used to correct the torque reading when using an extension or torque multiplier on the wrench. Default value is 1.
Angle correction | The parameter is used to correct the angle reading when using an extension or torque multiplier on the wrench. Default value is 0.
Target Angle | Defines the target angle for tightening step.
Rehit detection | On or Off. Rehit detection can be used to determine when a tightening is a rehit based on the angle limit setting. Angle limit for rehit is enabled if Rehit direction is set to On.
Linear slope coefficient | Linear slope coefficient characterizes the joint stiffness in the linear part of the curve, as torque/angle slope in the Nm/Deg measurement unit.
Compensate value | Choose between Average torque and Peak torque. The Compensate value specifies how the PVT will be calculated. Average torque - The PVT will be based on an average calculated using the following: Delay monitoring PVT interval PVT distance Prevailing torque min Prevailing torque max Peak torque - The PVT will be based on the peak value measured before snug was detected.
Torque Compensation | This parameter sets if the system compensates for the prevailing torque. If set to On, the system subtracts the prevailing torque from the peak torque before it reports the final torque. If set to Off, the system reports the peak torque as measured.
Delay monitoring | PVT calculation will not start before this window has been passed, starts at tightening start.
PVT interval | Sets how many degrees the PVT window shall be calculated for, start from the PVT distance point.
PVT distance | Sets how many degrees prior to snug the system shall start the PVT window.
Prevailing torque min | Prevailing torque minimum limit.
Prevailing torque max | Prevailing torque maximum limit

## Microvideo

WP - Wrench Production

# WQ - Wrench Quality

Tools
STwrench

Strategy used for the quality test of the tightening performed with the STwrench.

Parameter | Description
--- | ---
Control Strategy | The Wrench Quality strategy can be configured with the following control strategies. Residual Torque/Time: This strategy analyzes the torque trace as a function of time. The operator shall execute this operation with a single, steady, movement. The wrench automatically recognizes the breakaway and residual point. Residual Torque/Angle: This strategy evaluates the residual torque on a joint, looking for the residual point of the Torque/Angle trace. Residual Torque/Peak: This strategy evaluates the residual torque on a joint as the peak torque necessary to rotate the bolt further. Loose and Retighten: This strategy loosens a bolt and retightens it back to its original position Yield Point: With this strategy the wrench detects the yield point automatically. Target Angle specifies how far beyond the yield point the user may tighten.

Based on the control strategy selected, a combination of some of the parameters listed below will be displayed.

Parameters | Description
--- | ---
Ratchet time | Numerical value for ratchet time which is by default 5000 ms. This allows the operator to release the torque for a while and recharge during the tightening operation. If the Ratchet time is exceeded the result of the tightening is marked as NOK with the reason "Tightening timeout".
Torque correction coefficient | The parameter is used to correct the torque reading when using an extension or torque multiplier on the wrench. Default value is 1.
Angle correction | The parameter is used to correct the angle reading when using an extension or torque multiplier on the wrench. Default value is 0.
Target Angle | Defines the target angle for tightening step.
Rehit detection | On or Off. Rehit detection can be used to determine when a tightening is a rehit based on the angle limit setting. Angle limit for rehit is enabled if Rehit direction is set to On.
Linear slope coefficient | Linear slope coefficient characterizes the joint stiffness in the linear part of the curve, as torque/angle slope in the Nm/Deg measurement unit.

# Y – Tighten to Yield

Tools
ES STR SL ST SR QST IXB

This strategy runs the tool with the speed in the forward direction until the yield point is detected. The yield point is found by monitoring the torque gradient from the point where the torque goes above the Trigger Torque level, calculated based on Torque and Angle distance measurements. The Angle distance parameter is set according to the specified hardness of the joint.

Set the Gradient angle window (for hard joint, for soft joint or for manually setting of the Angle window). If Manual is selected, the Angle Window must be set. A joint is considered Hard if the screw is tightened to its full torque and it rotates 30 degrees or less after it has been tightened to its snug point. A Soft joint rotates 720 degrees or more after it has been tightened to its snug point. The hardness parameter defines the Angle Window for the gradient calculation. The harder the joint - the smaller the angle window.

Parameter | Description
--- | ---
Gradient Angle Window | Specifies Angle Window: For Hard Joint: Angle Window = 1 deg. For Soft Joint: Angle Window = 20 deg. Manual: Manually set Angle Window.
Angle Window | Available when Gradient Angle Window is set to Manual. Must be > 0 and <= 100.
Trigger Torque | The angle measurement starts at this trigger. Must be >= 0 and < Tool MaxTorque.
Damping | Frequency in which the gradient is being calculated. Must be > 0 and < 100 and < Angle window.
Yield Point Percentage | Must be >= 20 %
Speed | Default: 60 rpm. Must be > 0.
Speed ramp type | Hard, soft, or manual. Default: Hard. If you select Manual, the Speed ramp field opens.
Torque Filter Type | The type of the filter: None: No filtering of the torque is used. The raw values are used as-is in the gradient calculation. Five-point: The torque value used in the calculation are filtered using a sliding average filter over 5 torque samples. Low pass: The torque values is filtered with a simple discrete Infinite Impulse Response filter. Sliding Average: The torque values used in the calculation are filtered using a sliding average filter over a Number of Samples specified by the use.
Cut-off Frequency | Needs to be specified when Torque Filter Type is set to Low pass: 20 Hz 40 Hz 90 Hz 200 Hz 600 Hz
Number of Samples | Needs to be specified when Torque Filter Type is set to Sliding Average: 2 4 6 8 16 32
Brake (Valid only for Power Focus 6000 Synchronized tightening, Power Focus 8 Synchronized tightening and Flex). | If On the tool will be stopped when the target is reached. If Off the program goes directly to the next step without stopping the tool.

Point and click on image to see more information:

A | Peak Gradient
B | Yield Point
C | Shut-off Point
D | Angle Distance
E | Torque Trigger

# YM2 - Tighten to Yield: Method 2

Tools
QST

This step runs the tool with the specified speed in the forward direction until the yield point is detected.

Search for the yield point starts when the torque has reached Tt. The average of the torque over Af degrees is calculated. This procedure is repeated N rs times.

A reference slope is calculated with linear regression over the N rs points. After that, new average values are continuously calculated over A f degrees.

The actual slope is calculated with linear regression over the last N s average points. The yield point is reached when the slope is less than Py % of the reference slope.

Parameter | Description
--- | ---
Target torque | Must be > 0.
Filter angle | Default: 1. Must be > 0.
Number of samples | Default: 6. Must be >=4.
Number pf samples, reference | Default: 6. Must be >=4.
Yield point percentage | Default: 90%. Must be >20%.
Speed | Default: 60 rpm. Must be > 0.
Speed ramp type | Hard, soft, or manual. Default: Hard. If you select Manual, the Speed ramp field opens.
Speed ramp | If Speed ramp type is Manual, this field opens. Default: 500 rpm/s.
Brake (Valid only for Power Focus 6000 Synchronized tightening, Power Focus 8 Synchronized tightening and Flex). | If On the tool will be stopped when the target is reached. If Off the program goes directly to the next step without stopping the tool.

Point and click on image to see more information:

A | Torque Trigger
B | Number of samples, ref
C | Actual Slope
D | Number of samples
E | Reference Slope
F | Filter Angle

# ZP - Loosen to Zero Position

Tools
ES STR SL ST SR QST

This step runs the tool with the speed (N) in the backward direction until it reaches the zero position. If the total angle to rotate to reach the zero position is less than the minimum angle (Am) degree the rotation will continue for one more revolution, 360 degrees.

The zero position is a specific position stored with either a “Set Zero Position” step or the signal “Set Zero Position”. The position is repeated once every 360 degrees.

Parameters

Parameter | Description
--- | ---
Minimum Angle | Minimum Angle (Am) [°]
Speed | Rotation speed (N) [rpm]. Default value 60 rpm.

# ZP - Tighten to Zero Position

Tools
ES STR SL ST SR QST

This step runs the tool with the speed (N) in the forward direction until it reaches the zero position. If the total angle to rotate to reach the zero position is less than the minimum angle (Am) degree the rotation will continue for one more revolution, 360 degrees.

The zero position is a specific position stored with either a “Set Zero Position” step or the signal “Set Zero Position”. The position is repeated once every 360 degrees.

Parameters

Parameter | Description
--- | ---
Minimum Angle | Minimum Angle (Am) [°]
Speed | Rotation speed (N) [rpm]. Default value 60 rpm

# Step Monitors

The availability of tightening steps, monitors and restrictions depends on the license installed on the controller.

The step monitors are used to verify that the tightening was achieved according to the specification, for example, angle limits or torque. Each step has mandatory step monitors and optional step monitors. The mandatory monitors are included when dragging a new step to the multistep program. The optional monitors are flexible and can be placed as needed in the multistep program. Every step can have up to eight monitors each.

The following monitors are automatically added to every step that is added to the multistep tightening program.

Default step monitors
Step Monitor | Applicable steps
--- | ---
Angle | All
Peak Torque | All

Available tools for each system type
Power Focus 6000 / Power Focus 8 | Power Focus 6000 Synchronized tightening / Power Focus 8 Synchronized tightening | Flex | IxB
--- | --- | --- | ---
ST | ST | QST | IxB
STR | STR |  |
SL | QST |  |
QST |  |  |
STB |  |  |
IxB |  |  |
Power Focus Connect |  |  |
XB |  |  |

Step Monitors
Tools
Search

# A - Angle

Tools
ES STR SL ST SR QST STB IXB MWR-TA

This step monitor measures the maximum angle reached during the monitor and checks that it is between High limit and Low limit.

The angle measurement starts at the start of the monitor or, if specified, at the point where the torque passes Trigger torque for the first time during the monitor.

Parameter | Description | Default value
--- | --- | ---
Stop condition | It specifies where the angle measurement ends: End End point used: the angle at the end of the monitor. Peak Torque End point used: the angle at the point where the highest torque is reached during the monitor. Shut Off End point used: the angle at the shut off point of the step. Peak End point used: the highest angle reached during the monitor. | Shut Off
Trigger torque | The angle measurement starts at this trigger. Minimum limit: must be >= 0 Maximum limit: must be < Tool Max Torque | Not set
Low Limit | Lowest acceptable angle. Minimum limit: must be >= 0 Maximum limit: must be < 9 999 999 and < High Limit | Not set
High Limit | Highest acceptable angle. Minimum limit: Must be > 0 and > Low Limit Maximum limit: must be < 9 999 999 | Not set

## Result Values

- Angle Measured: the angle measured by the monitor.

Point and click on image to see more information:
Step Monitor Angle - Stop condition End

A | Shut-off point | D | Angle high limit
B | Torque trigger | E | Measured angle
C | Angle low limit | F | Step

Point and click on image to see more information:
Step Monitor Angle - Stop condition Peak Torque

A | Peak torque | E | Angle high limit
B | Shut-off point | F | Measured angle
C | Torque trigger | G | Step
D | Angle low limit |  |

Point and click on image to see more information:
Step Monitor Angle, Stop condition Shut Off

A | Shut-off point | D | Angle high limit
B | Torque trigger | E | Measured angle
C | Angle low limit | F | Step

Point and click on image to see more information:
Step Monitor Angle - without Torque Trigger and with stop condition Peak

A | Shut-off point | D | Measured angle
B | Angle low limit | E | Step n-1
C | Angle high limit | F | Step n

# AZP - Adjust to Zero Position

Tools
QST

This monitor is used to return to the true Zero Crossing position, measured in the Zero Crossing monitor earlier in the program. Backlash angle is used if measured earlier in the program

Parameter | Description
--- | ---
Low Speed | Speed used when Slowdown Distance is reached. Must be < Speed and > 0.
ZeroPosition Adjustment | Target position from Zero Crossing value. Must be > -9,999,000 and < 9,999,999.
Slowdown Distance | Degrees before target in which the Low Speed will be used. Must be >= 0 and < 9,999,999.
Speed | Default: 60 rpm. Must be < Tool max speed.
Speed Ramp Type | Hard, Soft or Manual. Default: Hard. If you select Manual, the Speed Ramp field opens.

# BA - Backlash Angle

Tools
QST

This monitor monitors the backlash angle of the socket. Used with the Backlash Angle Measurement step.

Parameter | Description
--- | ---
High Limit | Maximum angle limit. Must be < 9,999,999.

# BM - Backlash Angle Measurement

Tools
QST

This monitor measures the backlash in the socket. The resulting angle is used in calculations in the Adjust to Zero Position monitor.

Parameter | Description
--- | ---
Direction | The direction in which the measurement ends.
Target Torque | The torque target. Must be >= 0.
Speed | Default: 60 rpm. Must be >= 0.
Speed Ramp Type | Hard, Soft or Manual. Default: Hard. If you select Manual, the Speed Ramp field opens.

# C - Current

Tools
ES STR SL ST SR QST STB IXB

This monitor measures the actual current at any point after the torque passes Torque Trigger. The result will be the first peak or low value, that made the monitor NOK. In case of OK, the result will be the last measured current value. If the torque trigger is never reached during the monitor it will end with NOK status and no measurement value.

Parameter | Description
--- | ---
Torque Trigger | Must be >= 0 and < Tool Max Torque.
Low limit | Lowest acceptable current.
High limit | Highest acceptable current.

# Cl - Click

Tools
MWR-T MWR-TA

This step monitor is not available for IxB tools.

Monitor to enable click torque and click angle results. This monitor has no settings, and can only be used with the MWR step.

# LD - Loosening Detection

Tools
STwrench

This step monitor is only available for STwrench tools

This monitor can be used to check the torque and direction to see if a loosening is attempted when using the Wrench Production step strategy for an STwrench. If the applied torque is above the value set for Loosening Limit in the direction opposite to the configured thread direction of the program, the result shall be reported as NOK.

# MT - Mean Torque

Tools
ES STR SL ST SR QST IXB

This monitor measures the average torque during the monitor and checks the calculated value is within the limits.

Parameter | Description
--- | ---
Type | Specifies start condition: Step Start: The measurement starts from step start and ends at the shut-off point. Torque Trigger: The measurement starts at the point where the torque passes Torque Trigger for the first time. It ends at the shut-off point. Angle Trigger: The measurement starts at the point where the angle is Angle Trigger, measured from the optional Trigger Torque, is reached. Without Trigger Torque, the Angle Trigger is measured from the start of the step. It ends at the shut-off point Angle Window: Measures during an Angle Window. The window starts at the point where the torque passes Trigger Torque for the first time plus an angle offset, Angle Trigger. Time Interval: Measures during the last Time Interval seconds of the tightening.
Torque Trigger | Available when Type is set to Trigger Torque, Angle Trigger or Angle Window. Must be >= 0 and < Tool Max Torque.
Angle Trigger | Available when Type is set to Angle Trigger or Angle Window. Must be > 0.
Angle Window | Available when Type is set to Angle Window. Must be > 0.
Time Interval | Available when Type is set to Time Interval. Must be > 0.
Low Limit | Lowest acceptable torque.
High Limit | Highest acceptable torque.

# PC - Pulse Count

Tools
STR

This step monitor is only available for the following tools:

- ETV-STR61-100-13

- ETV-STR61-70-13

- ETV-STR61-50-10

Before using the Pulse Count step monitor, the Low Reaction Strategies license must be installed on the controller.

This monitor measures the number of pulses and confirms if it is between the pulse count low limit and pulse count high limit.
If the torque trigger level is set, the check starts as soon as the measured torque is above the torque trigger level.

If running a tightening step with Pulse Count step monitor, use the necessary PulseDrive socket/adapter.
If the tightening step runs without the PulseDrive socket/adapter, all the tightenings are NOK. The step error “PulseDrive socket/adapter not detected” shows for no PulseDrive socket/adapter.

Parameter | Description
--- | ---
Pulse Count High Limit - n+ | The Pulse Count limits are used to determine if the measured number of pulses is OK or NOK. The measured number of pulses is OK if it is between the pulse count low limit and pulse count high limit. The measured number of pulses is NOK if: It is higher than the pulse count high limit. It is lower than the pulse count low limit. The trigger torque level is not reached. Pulse count high limit must range from 1 through 9999999. It must be greater than or equal to the pulse count low limit. Pulse Count High Limit text box can be empty.
Pulse Count Low Limit - n- | The Pulse Count limits are used to determine if the measured number of pulses is OK or NOK. The measured number of pulses is OK if it is between the pulse count low limit and pulse count high limit. The measured number of pulses is NOK if: It is higher than the pulse count high limit. It is lower than the pulse count low limit. The trigger torque level is not reached. Pulse Count Low Limit must range from 1 through 9999999. It must be lower than or equal to the Pulse Count High Limit. Pulse Count Low Limit text box can be empty.
Torque Trigger - Tt | Torque Trigger must range from 0 through the maximum torque of the tool. Torque Trigger text box can be empty.

# PrT - Prevailing Torque

Tools
ES STR SL ST SR QST STB IXB

The monitor calculates the prevailing torque value in the Window Length and checks that it is between the Torque limits. The Angle Window starts at the angle degrees set in Start Angle in reverse direction from the shut-off point. This then spans for the angle degrees set in Angle Window Length in reverse direction. If Start Angle is left blank the angle window starts at the shut-off point. The calculated prevailing torque value is the mean or peak torque value (depending on the parameter set by the user) during the Window Length. The calculated value is saved as result data Prevailing Torque Measured. If Torque compensation is set to On, the Prevailing Torque Measured will be subtracted from all torque result values in consecutive steps. Any previously calculated prevailing torque compensation values will no longer be subtracted from torque result values. If Torque compensation is set to Off, no subtraction will be made in consecutive steps.

If the total angle of the step is less than the Start Angle plus Window Length, then the monitor will report NOK.

Prevailing torque can be measured as an average of measured values, or at peak torque. To choose between these two modes, set the Use Value parameter to either Mean torque (for average values), or Peak torque (for peak value).

Parameter | Description
--- | ---
Torque Compensation | On or off.
Start Angle | Must be > 0
Window length | Must be >= 0
Low Limit | Must be > 0
High Limit | Must be >= 0
Use value | Mean torque (for average values), or Peak torque (for peak value).

# PT - Peak Torque

Tools
ES STR SL ST SR QST STB IXB MWR-TA MWR-T

This step monitor measures the maximum torque reached during the monitor, including any over shoot, and checks that it is between High limit and Low limit.

Parameter | Description
--- | ---
Low Limit | Lowest acceptable torque.
High Limit | Highest acceptable torque.

# PTCA - Post Thread Cut Angle

Tools
ES STR SL ST SR QST STB IXB

This step monitor measures the maximum angle reached during the monitor and checks that it is between High limit and Low limit.

The Trigger Torque level is ignored until the end of the Thread cut angle window is reached. After that, the angle measuring starts as soon as the measured torque is above Trigger Torque.

Parameter | Description | Default value
--- | --- | ---
Stop condition | It specifies where the angle measurement ends: End End point used: the angle at the end of the monitor. Peak Torque End point used: the angle at the point where the highest torque was reached during the monitor. Shut Off End point used: the angle at the shut off point of the step. Peak End point used: the highest angle reached during the monitor. | Shut Off
Trigger torque | The angle measurement starts at this trigger. Minimum limit: must be >= 0 Maximum limit: must be < Tool Max Torque | 0
Low Limit | Lowest acceptable angle. Minimum limit: must be >= 0 Maximum limit: must be < 9 999 999 and < High Limit | Not set
High Limit | Highest acceptable angle. Minimum limit: Must be > 0 and > Low Limit Maximum limit: must be < 9 999 999 | Not set
Thread cut trigger torque | Minimum limit: must be >= 0 Maximum limit: must be < Tool Max Torque | Not set
Thread cut angle window | Minimum limit: must be >= 0 Maximum limit: must be < 9 999 999 | 0

## Result Values

- Angle Measured: the angle measured by the monitor.

Point and click on image to see more information:
Step Monitor - Post Thread Cut Angle

A | Shut-off point | E | Angle low limit
B | Torque trigger | F | Angle high limit
C | Torque trigger thread cut | G | Measured angle
D | Thread cut angle window |  |

# PTCPT - Post Thread Cut Peak Torque

Tools
ES STR SL ST SR QST STB IXB

Measures the maximum torque achieved during the monitoring, including any over-shoot, and checks that it is between the Torque limits. All torque values are ignored until the end of the Thread cut angle window has been reached.

Parameter | Description
--- | ---
Thread cut trigger torque | Must be >= 0
Thread cutting angle window | Must be > 0
Low Limit | Must be >= 0
High Limit | Must be > 0 Must be > Low limit

# PVTH - Post View Torque High

Tools
ES STR SL ST SR QST STB IXB

This monitor checks that all torque values in the Angle Window Length are below the High limit.

The Angle Window starts at the angle degrees set in Start Angle in reverse direction from the shut-off point. This then spans for the angle degrees set in Angle Window Length in reverse direction. If Start Angle is left blank, the Angle Window starts at the shut-off point. The torque values used in the monitor are based on the mean torque value, calculated over Number of Samples. If the total angle of the step is less than Start Angle plus Angle Window Length the monitor will report NOK.

Parameter | Description
--- | ---
Start Angle | Must be >= 0
Window length | Must be > 0
Number of samples | Minimum value =1 Maximum value = 80
High Limit | Highest acceptable torque.

# PVTL - Post View Torque Low

Tools
ES STR SL ST SR QST STB IXB

Same as monitor Post View Torque High, but this monitor checks that all torque values in the Angle Window Length are above Low Limit instead.

Parameter | Description
--- | ---
Start Angle | Must be >= 0
Window length | Must be > 0
Number of samples | Minimum value =1 Maximum value = 80
Low Limit | Lowest acceptable torque.

# SOC - Shut Off Current

Tools
ES STR SL ST SR QST STB IXB

The shut off point is the point where the step reaches its target. The current is measured at the shut off point and checked to be between High limit and Low limit .

Parameter | Description
--- | ---
Low Limit | Lowest acceptable current.
High Limit | Highest acceptable current.

# SOT - Shut Off Torque

Tools
ES STR SL ST SR QST STB IXB

The shut off point is the point where the step reaches its target. The torque is measured at the shut off point and checked to be between High limit and Low limit.

Parameter | Description
--- | ---
Low Limit | Lowest acceptable torque.
High Limit | Highest acceptable torque.

# SSD - Stick Slip Detection

Tools
ES STR SL ST SR QST IXB

This step monitor detects and reports stick slip effects during a step. The detection is done by counting the number of times the torque falls below the Trigger Level. If the number of times is larger than Maximum Number of Oscillations then the stick slip error is reported. The monitor operates in two different modes, Dynamic or Fixed. The difference between the modes is the way that the Trigger level is calculated.

Dynamic Torque: Trigger Level is dynamically calculated as Peak Torque Percentage of the current max torque, which has been achieved so far during the monitoring. The monitoring is started as soon as the torque passes the Trigger Torque.

Fixed Torque: Trigger Level is the fixed Trigger Torque specified by the user. In this mode the percentage is not needed.

If the torque never reaches the Trigger Torque then the monitoring is not started, this will result in status NOK.

Parameter | Description
--- | ---
Type | Specifies what type of Stick slip detection that will be done in the monitor Stick Slip detection. Default: Dynamic torque.
Peak Torque Percentage | Default: 80%, Must be >=10 and < 100.
Trigger Torque | Default: 5, Must be >= 0 and < Tool max torque.
Maximum Number of Oscillations | Default: 5, Must be >= 3 and <20.

# TAW - Torque in Angle Window

Tools
ES STR SL ST SR QST STB IXB

This monitor checks that all torque values in the angle window are within the torque limits.

Parameter | Description
--- | ---
Trigger Torque | Must be >= 0
Start Angle | Must be > 0
Window Length | Must be <= 0
Low Limit | Must be >= 0
High Limit | Must be > 0 Must be > Low limit
NOK if window is passed | If set to Yes, status of this monitor is NOK if the end of angle window is not reached.

# TC - Torque Calibration

Tools
QST

This step monitor is only available for tools equipped with multiple transducers.

The Torque Calibration monitor checks if the maximum torque reached is within the torque limits.

Parameter | Description
--- | ---
Transducer type | Torque or Torque 2 Set to Torque 2 for the front transducer of the tool.
Low limit | Must be >= 0
High limit | Must be > 0 Must be > Low limit

# TG - Torque Gradient

Tools
ES STR SL ST SR QST IXB

This monitor checks that the gradient is within the limit.

Parameter | Description
--- | ---
Gradient Angle Window | Specifies Angle Window: For Hard Joint: Angle Window = 1 deg. For Soft Joint: Angle Window = 20 deg. Manual: Manually set Angle Window.
Angle Window | Available when Gradient Angle Window is set to Manual. Must be > 0 and <= 100.
End Point Check | If set to Yes, only the gradient measured at the shut off point of the step is checked to be within the limits.
Trigger Torque | The angle measurement starts at this trigger. Must be > 0 and < Tool MaxTorque.
Damping | Frequency in which the gradient is being calculated. Must be > 0 and < 100 and < Angle window.
Low Limit | Lowest acceptable torque gradient. Must be >= -100.
High Limit | Highest acceptable torque gradient. Must be > -100 and > Low limit.
Torque Filter Type | The type of the filter: None: No filtering of the torque is used. The raw values are used as-is in the gradient calculation. Five-point: The torque value used in the calculation are filtered using a sliding average filter over 5 torque samples. Low pass: The torque values is filtered with a simple discrete Infinite Impulse Response filter. Sliding Average: The torque values used in the calculation are filtered using a sliding average filter over a Number of Samples specified by the use.
Cut-off Frequency | Needs to be specified when Torque Filter Type is set to Low pass: 20 Hz 40 Hz 90 Hz 200 Hz 600 Hz
Number of Samples | Needs to be specified when Torque Filter Type is set to Sliding Average: 2 4 6 8 16 32
Angle Offset | Available when End Point Check is set to No. Specifies the degrees that the calculation of the gradient start after the trigger torque is passed for the first time.

# Ti - Time

Tools
ES STR SL ST SR QST STB IXB

Measures the elapsed time during the monitor and checks that it is between the time limits. The time measurement starts at the start of the monitor and, if the Trigger Torque is specified, at the point where the torque passes Trigger Torque for the first time during the monitor.

Parameter | Description
--- | ---
Trigger Torque | Must be >= 0 and < Tool max torque.
Low Limit | Must be >= 0
High Limit | Must be > 0 Must be > Low limit

# TRD - Torque Rate and Deviation

Tools
ES STR SL ST SR QST IXB

This step monitor measures and checks the torque rate, i.e. the ratio of torque vs. angle. The calculated torque rate is checked if it is within the torque rate limits defined by High Limit and Low Limit.

Parameter | Description
--- | ---
Trigger Torque | Torque of the angle start point.
Start Point Angle | When Start point angle has been measured from Trigger torque the measuring of the torque starts.
End Point Angle | Angle point where the measuring of the torque is stopped.
End Point Torque | Torque where the measuring of the torque is stopped.
Low Limit | Lowest acceptable torque.
High Limit | Highest acceptable torque.
Limit | Must be > 0

# YA - Angle from Yield

Tools
ES STR SL ST SR QST IXB

This monitor measures the peak angle reached from the yield point and checks that the peak angle is within the limit.

Parameter | Description
--- | ---
Gradient Angle Window | Specifies Angle Window: For Hard Joint: Angle Window = 1 deg. For Soft Joint: Angle Window = 20 deg. Manual: Manually set Angle Window.
Angle Window | Available when Gradient Angle Window is set to Manual. Must be > 0 and <= 100.
Yield Point Percentage | Must be >= 20 %
Trigger Torque | The angle measurement starts at this trigger. Must be > 0 and < Tool MaxTorque.
Damping | Frequency in which the gradient is being calculated. Must be > 0 and < 100 and < Angle window.
Low Limit | Lowest acceptable angle. Must be >= 0
High Limit | Highest acceptable angle. Must be > 0
Torque Filter Type | The type of the filter: None: No filtering of the torque is used. The raw values are used as-is in the gradient calculation. Five-point: The torque value used in the calculation are filtered using a sliding average filter over 5 torque samples. Low pass: The torque values is filtered with a simple discrete Infinite Impulse Response filter. Sliding Average: The torque values used in the calculation are filtered using a sliding average filter over a Number of Samples specified by the use.
Cut-off Frequency | Needs to be specified when Torque Filter Type is set to Low pass: 20 Hz 40 Hz 90 Hz 200 Hz 600 Hz
Number of Samples | Needs to be specified when Torque Filter Type is set to Sliding Average: 2 4 6 8 16 32

# ZC - Zero Crossing

Tools
QST

This monitor calculates the true start of a spring compression.

Parameter | Description
--- | ---
Trigger Torque | Torque value from where the monitor starts. Must be < End Point Torque.
End Point Torque | Torque value for stop measuring. Must be > Trigger Torque.
Start Point Angle | Angle value from where the monitor starts. Must be < End point angle.
End Point Angle | Angle value for stop measuring. Must be > Start point angle.
Torque Rate Limit High | Maximum torque rate. Must be > Torque Rate Limit Low and < 999.
Torque Rate Limit Low | Minimum torque rate. Must be < 999 and < Torque Rate Limit High.

# Step Restrictions

The availability of tightening steps, monitors and restrictions depends on the license installed on the controller.

To make sure the tightening stops if something unexpected happens, it is possible to add step restrictions to the multistep tightening program. These restrictions could, for example, test that a maximum torque is not reached or that a part of the multistep tightening does not take too long to run. Each step has its own set of mandatory step restrictions and optional step restrictions. The mandatory restrictions are included when dragging a new step to the multistep program. All steps can have up to four restrictions each.

For synchronized tightening in Power Focus 6000 and Power Focus 8, it is possible to use synchronization points in the tightening program. When any condition that is set for a restriction is met, the tool will be stopped immediately and the program jumps to the next synchronization point (only valid when using synchronized tightening in Power Focus 6000, Power Focus 8, and Flex), or the end of the program. In controllers without synchronized tightening the tool is stopped immediately and the program jumps to the end of the program.

For Flex only:

For each restriction, select Repairable = Yes to allow retry when tightening stops.

The following restrictions are automatically added to every step that is added to the multistep tightening program.

Default step restrictions
Step Restriction | Applicable steps
--- | ---
Maximum Time | All except External Result and MWR
Maximum Torque | Tighten to Angle Tighten to Torque+Angle Turbo Loosening Wait Socket release Run until Digital Input Tighten to Trigger Release TensorPulse Impulse
Maximum Angle | Tighten to Torque TurboTight Turbo Loosening Tighten to DynaTork Wait Run until Digital Input Loosen to Torque Thread Cutting to Torque Rundown Tighten to Yield Pulsing Rundown Snug TensorPulse

Available tools for each system type
Power Focus 6000 / Power Focus 8 | Power Focus 6000 Synchronized tightening / Power Focus 8 Synchronized tightening | Flex | IxB
--- | --- | --- | ---
ST | ST | QST | IxB
STR | STR |  |
SL | QST |  |
QST |  |  |
STB |  |  |
IxB |  |  |
Power Focus Connect |  |  |
XB |  |  |

Step Restrictions
Tools
Search

# A - Maximum Angle

Tools
ES STR SL ST SR QST STB IXB

This restriction measures the angle. If the measured angle reaches the Maximum Limit, the tool is stopped immediately. The angle is measured from the start of the restriction or, if specified, from the point where the torque passes Trigger Torque for the first time during the restriction.

Parameter | Description
--- | ---
Trigger Torque | If specified, this is the torque from where the angle is measured.
Maximum Limit | If this limit is reached the tool is stopped immediately.

# C - Current

Tools
ES STR SL ST SR QST STB IXB

This step restriction is not supported for Power Focus XC.

This restriction checks the actual current where torque passes Torque Trigger. If the actual current exceeds the limits, the tool will be stopped immediately and the tightening program will jump to the next synchronization point or the end of the program. The result will be the first peak or low value, that made the monitor NOK. In case of OK, the result will be the last measured current value. If the torque trigger is never reached during the restriction it will end with status OK.

Parameter | Description
--- | ---
Torque Trigger | Must be >= 0 and < Tool Max Torque.
Low limit | Lowest acceptable current.
High limit | Highest acceptable current.

# CTh - Cross Thread

Tools
ES STR SL ST SR QST STB IXB

This restriction checks the angle from the point where torque passes Start torque (T1) to the point where the torque passes End torque (T2). If the angle measured from Start torque (T1) is higher than Maximum limit (Amax), the tool is stopped immediately.

When the torque passes End torque (T2), the measured angle is checked against the limit Minimum limit (Amin). If the angle is lower than this limit, the tool is stopped immediately.

Parameter | Description | In illustration
--- | --- | ---
Start Torque | Must be <=0. | T1
End Torque | Must be <=0. | T2
Minimum Limit | The low angle limit. | Amin
Maximum Limit | The high angle limit. | Amax

# PCH - Pulse Count High

Tools
STR IXB

This restriction is only available for the following tools:

- ETV-STR61-100-13

- ETV-STR61-70-13

- ETV-STR61-50-10

- ITB-P

Before using the Pulse Count restriction, the Low Reaction Strategies license must be installed on the controller.

This restriction gives a limit to the number of pulses, and makes sure that those are below the specified pulse count high limit.
If the measured number of pulses is higher than the pulse count high limit, the tool is stopped immediately and the program goes to the next synchronization point or the end of the program.
If the torque trigger level is set, the check starts as soon as the measured torque is above the torque trigger level.

If running a tightening step with Pulse Count High step restriction, use the necessary PulseDrive socket/adapter.
If the tightening step runs without the PulseDrive socket/adapter, all the tightenings are NOK. The step error “PulseDrive socket/adapter not detected” shows for no PulseDrive socket/adapter.

Parameter | Description
--- | ---
Pulse Count High Limit - n+ | Pulse count high limit must range from 1 through 9999999. Pulse Count High Limit text box can be empty.
Torque Trigger - Tt | Torque Trigger must range from 0 through the maximum torque of the tool. Torque Trigger text box can be empty.

# Rh - Rehit

Tools
ES STR SL ST SR QST STB IXB

This restriction checks the torque. If the measured torque exceeds the Detection Torque, the tool is stopped immediately and the program jumps to the next synchronization point (for Power Focus 6000 Synchronized tightening and Power Focus 8 Synchronized tightening), or the end of the program.

It is only possible to add step Rehit restriction to the first step of the multistep tightening program. Once the Rehit restriction has been added to the first step it shall not be possible to move the step to any other position within the tightening program. The Rehit restriction has to be deleted from the first step in order to move it to other position in the tightening program.

Parameter | Description
--- | ---
Detection Torque | If the measured torque exceeds the Detection Torque, the tool is stopped immediately and the program jumps to the next synchronization point (for Power Focus 6000 Synchronized tightening and Power Focus 8 Synchronized tightening), or the end of the program. Must be greater than zero.
Angle Window | The angle window is measured from the start of the step. If no Angle Window is set, the restriction is active during the whole step.

# RT - Rescinding Torque

Tools
ES STR SL ST SR QST STB IXB

This restriction checks the torque. If the measured torque drops below the condition of the restriction the tool is stopped immediately and the program jumps to the next synchronization point (for Power Focus 6000 Synchronized Tightening and Power Focus 8 Synchronized Tightening), or the end of the program.

- Torque control processes
  The restriction condition is the measured torque. For the restriction to be active the torque must first exceed 110 % of the Rescinding Torque Limit.

- Angle control processes
  This restriction checks the maximum torque reached during the restriction. For the restriction to be active the torque must first exceed the Trigger Torque.

Torque control processes
Parameter | Description
--- | ---
Rescinding torque limit | Default: 10 Nm. Must be > 0.

Angle control processes (valid only for Power Focus 6000 Synchronized tightening and Power Focus 8 Synchronized tightening)
Parameter | Description
--- | ---
Trigger Torque | Must be > 0.
Peak torque percentage | Default: 95. Must be >= 50.
Rescinding torque time | Default: 20. Must be >= 5 and <= 500.
Rescinding Torque Angle | Must be > 0.

Cable tools have the option to select Rescinding Torque for Angle. This restriction is controlled by two parameters: Peak Torque Percentage and Rescending Torque Time. Percentage sets the downward deviation from the last peak torque, and Rescending Torque Time sets the duration (between 5 and 500 ms) of that deviation. Only when both conditions (equal to or lower than the indicated percentage for the set duration) are met, will the program be interrupted and jump to the end.

# T - Maximum Torque

Tools
ES STR SL ST SR QST STB IXB

This restriction checks the torque. If the measured torque exceeds the Maximum limit, the tool is stopped immediately.

Parameter | Description
--- | ---
Maximum Limit | If the torque reaches this specified limit the tool is stopped immediately.

# TAW - Torque in Angle Window

Tools
ES STR SL ST SR QST STB IXB

This restriction checks that the measured torque in the Angle Window Length is between the Torque limits. If the measured torque is outside the limits the tool is stopped immediately and the program jumps to the end. The Angle Window Length starts at the Start Angle from the point that the torque first passed the Trigger Torque. If Trigger Torque is not set, then the Start Angle begins at the start of the restriction.

If the end of the Angle Window Length is not reached, the status of the restriction is NOK.

Parameter | Description
--- | ---
Trigger Torque | Must be >= 0
Start Angle | Must be >= 0
Window Length | Must be >0
Minimum Limit | Must be >= 0
Maximum Limit | Must be <= Minimum limit

# TCD - Torque vs Current Deviation

Tools
ES STR SL ST SR QST IXB

This restriction verifies that all current measurements converted to the corresponding torque are, at most, the Maximum deviation away from the actual torque measured with the torque transducer. The restriction starts when the torque reaches Trigger Torque for the first time during the step and is active until the step reaches its target.

If Trigger Torque is never reached, the monitor will report OK.

Parameter | Description
--- | ---
Trigger Torque | Must be >= 0
Maximum Deviation | Default: 1, Must be > 0

# TG - Torque Gradient

Tools
ES STR SL ST SR QST IXB

This restriction checks the gradient and if it is outside the limits the tool is stopped immediately and the program jumps to the end of the program.

Parameter | Description
--- | ---
Gradient Angle Window | Specifies Angle Window: For Hard Joint: Angle Window = 1 deg. For Soft Joint: Angle Window = 20 deg. Manual: Manually set Angle Window.
Angle Window | Available when Gradient Angle Window is set to Manual. Must be > 0 and <= 100.
Trigger Torque | Must be > 0 and < Tool MaxTorque.
Damping | Frequency in which the gradient is being calculated. Must be > 0 and < 100 and < Angle window.
Minimum Limit | Must be >= -100.
Maximum Limit | Must be > -100 and > Low limit.
Torque Filter Type | The type of the filter: None: No filtering of the torque is used. The raw values are used as-is in the gradient calculation. Five-point: The torque value used in the calculation are filtered using a sliding average filter over 5 torque samples. Low pass: The torque values is filtered with a simple discrete Infinite Impulse Response filter. Sliding Average: The torque values used in the calculation are filtered using a sliding average filter over a Number of Samples specified by the use.
Cut-off Frequency | Needs to be specified when Torque Filter Type is set to Low pass: 20 Hz 40 Hz 90 Hz 200 Hz 600 Hz
Number of Samples | Needs to be specified when Torque Filter Type is set to Sliding Average: 2 4 6 8 16 32

# Ti - Maximum Time

Tools
ES STR SL ST SR QST STB IXB

This restriction checks the time. If Maximum Limit is reached, the tool is stopped immediately.

Parameter | Description
--- | ---
Maximum Limit | If this time is elapsed, the tool is stopped immediately.

# Sync Point

In a synchronization point the tool waits for all other tools to reach the corresponding synchronization point in their programs. Depending on the status for all tools the program continues on the tightening path, the repair path or the terminate path.

To prevent overheating of tools that are waiting in a synchronization point they are only allowed to “hold torque” or “hold position” for a maximum of 1 second. After this the tool will release the hold and continue to wait for the other tools.

Parameter | Description
--- | ---
Sync hold condition | Hold position: The tool holds the position it had when the previous step ended. No Hold: The motor is turned off and the position will not be held. Hold Torque: If the step before the synchronization point is a DynaTork step it is possible to set HoldTorque.

Configuring Sync point

1. In a Multistep Tightening Program, double-click on a Sync Point, or mark it and then select Configuration in the lower area of the workspace. To mark several, press CTRL.

2. In the Configuration area, select one of the following conditions for each Sync Point:

   - NoHold. The motor is turned off and the position will not be held.

   - HoldPosition. The tool holds the position it had when the previous step ended.

# Utilities

Connectors can be added to reuse a repair path or a terminate path.

Creating a connector

1. Select Connector.

2. Select a sync point.

   If a wrong sync point is selected, use the right mouse button or press Esc to cancel.

3. Select a step that is on a repair path or a terminate path.

   You can only select the repair path backward or the terminate path forward.

The connector is added.

One sync point can only have one repair path and one terminate path.

Example: Same repair path

A | Same repair path as step 5 from the second synchronization point.
B | Same repair path as step 5 from the third synchronization point.

Example: Same termination path

A | Same termination path as step 5 from the first synchronization point.
B | Same termination path as step 5 from the second synchronization point.

# Result Reporters

The result reporters makes it possible to extract specific values of selected producer from the result. The result reporters belong to a step but has to be tied to the monitor/restriction which they read the values from. Only monitors or restrictions located in the same step as the result reporter can be selected. A result reporter is added to a step using drag and drop (in the same way as monitors and restrictions). Each result reporter is responsible for reporting a specific result value, for example, Rundown Angle, Final Torque, Prevailing Torque.

It is possible to tie a result reporter to:

- Program monitors

- Step monitors

- Step restrictions

Each result reporter defines a final value type:

- Final Angle

- Final Torque

- Prevailing Torque

- Self-tap Torque

- Current

- Rundown Angle

- Number of Pulses

## General Parameters

Parameter | Description
--- | ---
Producer | Specifies which monitor/restriction produces the value.
Value | Specifies which value to show from the selected producer.

Limitations:

- It is only possible to add a result reporter on a monitor/restriction belonging to a step in main path or a program monitor/program restriction.

- There may exist several reporters on a step if they are of different type.

- There may exist a result reporter of, for example, type final angle on every step and program monitor angle.

- For those monitor/restrictions that have more than one result value, it is possible to add more than one result reporter if the result reporters are of different types.

- There may not exist several result reporters of the same type on a step or on a program monitor/restriction.

- There is only one result reported for each possible final value type.

Rules:

- The internal number of a result item has to be the same as for the corresponding result reporter.

- The internal number of a monitor/restriction result has to be the same as the internal number of the monitor/restriction in the configuration.

- The step results has to be ordered according to the order of execution. The first executed step has to be first.

Possible values reported by a result reporter if present in the monitor/restriction/step:

- The monitors/restrictions measured value (as float or integer)

- The monitors/restrictions high and low limits

- Status

- Torque trigger and angle trigger

- Angle target and torque target (read from the step)

Possible values for status:

- Low

- OK

- High

- Other

- NotSet

The target values do not belong to any step monitor so the target values are taken from the step that the monitor belongs to.

# Multistep Template

All created templates are visible in the tab Templates, when creating a multistep program. A template can be inserted (drag-and-drop) and act as a base to build the new multistep program on.

A template can only be dragged into the multistep program when steps have not yet been added. After dragging the template to the multistep program, steps may then be added.

The template itself will not be affected when modifying a multistep tightening program since the template is copied, and not linked to the program.

Create multistep program templates in Library > Program templates.

Relevant Information

- Program Templates
- Pushing Configurations to a Controller

# Multistep Tightening Program Properties

Parameter | Description
--- | ---
Name | A user-defined name for the multistep program.
Description | Description of the multistep program.
Type | Set type of tightening, for example, fixtured.
Thread direction | Clockwise (CW) or counter clockwise (CCW). Normally this direction is clockwise.
Program Start | The multistep tightening program starts when the torque passes the trigger torque value (Nm) for the first time, in order to avoid starting the program by accident.

## Trace Configuration

The trace configuration can be done on program level or for each step. The default configuration is set on the program level and can be overridden in each step as needed.

Here, enabling this function allows the configuration to be done on program level.

Parameter | Description
--- | ---
Enabled | On: Enables the trace resolution configuration on program level. Off: The trace recording is done with the same resolution for the whole tightening. In this case, the trace points are evenly distributed in time over the whole tightening. For each time slot (0.25 ms) two values (the minimum and the maximum measured value) are displayed in the trace. The maximum number of samples in this format is 2000.
Sample Type | Sample Time: specifies how often samples should be stored in the trace by specifying a sample time in ms. Sample Angle: specifies how often samples should be stored in the trace by specifying a sample in deg.
Sample Time | Choose the sample time from the drop-down list (0.25 - 1000 ms)
Sample Angle | Choose the sample angle from the drop-down list (0.25 - 20 degree)

## Program Restrictions

Parameter | Description
--- | ---
Maximum Time Limit | Set amount in seconds. This restriction checks the total time for the tightening and if it exceeds the Maximum Time Limit limit the tool is stopped immediately. The time is measured from the start of the program.
Maximum Torque Limit | Set amount. This restriction checks the torque and if the measured torque exceeds the Maximum Torque Limit limit the tool is stopped immediately.

Angle
Parameter | Description
--- | ---
Enabled | Turn angle restriction On or Off for the entire program. This restriction checks that the angle is within the specified angle limits.
Active in steps | Sets a range of steps this restriction is valid for: If no start step is specified, this restriction will start at program start. If no end step is specified, this restriction will stop at the last step of the program.
Trigger torque | Sets the value of the trigger torque at which the this restriction shall start.
High limit | Sets angle restriction (program) higher limit.

Time
Parameter | Description
--- | ---
Enabled | Turn time restriction On or Off for the entire program. This restriction checks that the time is within the specified time limits.
Active in steps | Sets a range of steps this restriction is valid for: If no start step is specified, this restriction will start at program start. If no end step is specified, this restriction will stop at the last step of the program.
Trigger torque | Sets the value of the trigger torque at which this restriction shall start.
High limit | Sets time restriction (program) higher limit.

## Program Monitor

Angle
Parameter | Description
--- | ---
Enabled | Turn angle monitoring On or Off for the entire program. This monitor checks that the angle is within the specified limits.
Active in steps | Sets a range of steps this monitor is valid for: If no start step is specified, this monitor will start at program start. If no end step is specified, this monitor will stop at the last step of the program.
Type | Type of angle monitoring: Peak Angle: the highest angle reached during the monitor. Angle at Peak Torque: the angle at the point where the highest torque was reached during the monitor. Shut Off Angle: the angle at the shut-off point of the step. Angle at End: the angle at the end of the monitor, including the brake, if active.
Trigger torque | Sets the value of the trigger torque at which this monitor shall start.
Low limit | Sets angle monitoring (program) lower limit.
High limit | Sets angle monitoring (program) higher limit.

Torque
Parameter | Description
--- | ---
Enabled | Turn Torque monitoring On or Off for the entire program. This monitor checks that the torque is within the specified limits.
Active in steps | Sets a range of steps this monitor is valid for: If no start step is specified, this monitor will start at program start. If no end step is specified, this monitor will stop at the last step of the program.
Type | Type of angle monitoring: Peak Torque: the highest torque reached during the monitor. Shut Off Torque: the torque at the shut-off point of the step.
Low limit | Sets torque monitoring (program) lower limit.
High limit | Sets torque monitoring (program) higher limit.

Time
Parameter | Description
--- | ---
Enabled | Turn time monitoring On or Off for the entire program. This monitor checks that the time is within the specified limits.
Active in steps | Sets a range of steps this monitor is valid for: If no start step is specified, this monitor will start at program start. If no end step is specified, this monitor will stop at the last step of the program.
Trigger torque | Sets the value of the trigger torque at which this monitor shall start.
Low limit | Sets time monitoring (program) lower limit.
High limit | Sets time monitoring (program) higher limit.

## Validation

Parameter | Description
--- | ---
Validate against tool values | Use On if tool is known and set Max Torque and Max Speed. Use Off if tool is not known.
Tool | Drop-down for choosing the tool to validate against.
Max torque | Maximum torque of the tool to validate against.
Max speed | Maximum speed of the tool to validate against.

## Attachment Tuning

Parameter | Description
--- | ---
Use attachment tuning | Select whether attachment tuning should be on or off.
Gear ratio | The gear ratio value can be between 0.5 and 100.
Efficiency tuning | The efficiency tuning value can be between 0.5 and 1.0.

## Reporters

This enables the user to choose which values (from monitors/restrictions) shall be shown as final values. Click Add to choose a result reporter to be tied to a program monitor/restriction value.

Parameter | Description
--- | ---
Reporter | Select a result reporter.
Producer | Select which monitor/restriction produces the value.
Value | Select which value to show from the selected producer.

# Approval Statuses

Status | Description
--- | ---
Approved | The program is approved and may be used on the controller. The program will be read-only.
Draft | The program is being changed/optimized. The program can be sent for approval once it is finalized. The program will be editable.

All programs can be used irrespective of the approval statuses. Approval statuses do not affect operational function of any programs.

Once a program enters the approval workflow, it will always have a status.

# Working with the Sync Mode Tab

Sync Mode is used in conjunction with a Multistep Tightening Program. To run a tightening, a Sync Mode must be created. The Sync Mode specifies the channels to use in the tightening and also the tightening program to be used for each channel. Up to 100 different Sync Modes can be created. If needed, different tightening programs can be used for each channel. The Sync Mode feature allows you to set up a mode for each configuration.

Sync Mode is used to:

- Define the tools that shall be included in a synchronized tightening or loosening

- Specify the tightening or the loosening program each tool shall run

- Handle reject management (valid only for tightening Sync Mode)

- Configuring the bolt configuration

The Sync Mode allows the different tools in a fixtured solution to run different multistep programs at the same time.

In a flexible production line you may need to use a different Sync Mode for each new product. The Sync Mode feature allows you to set up a mode for each configuration.

Each line represents one Sync Mode. The columns contain the following information:

Column | Description
--- | ---
Check box | Used when, for example, deleting a Sync Mode.
Name | For a tightening Sync Mode each name starts with an index number which is then followed by the user defined name. A loosening Sync Mode contains only an user defined name.
Description | Description of the Sync Mode.
Channels | The number of channels in the Sync Mode.
Last changed | Last changes made, expressed in ToolsTalk 2 time.
Changed by | Shows who saved the configuration data.
Controller updated | Time when the controller was updated, expressed in controller time.
Controller updated by | User who last updated the controller.

In this Section

- Adding a Sync Mode
- Deleting a Sync Mode
- Handling Tightening Sync Mode Configuration
- Handling Loosening Sync Mode Configuration
- Running a Loosening Sync Mode
- Copying and Pasting Batch sequences, Sync modes and Sources
- Exporting a Sync Mode
- Importing a Sync Mode

# Adding a Sync Mode

1. Select a controller in the Plant structure .

2. Select the Sync Mode icon in the Menu bar. The workspace area shows a list of all the current Sync Modes.

3. Select the Add command button and enter the Name and Index (valid only for tightening Sync Mode).

4. Select Tightening or Loosening in the Operation mode drop-down.

   A new Sync Mode is added at the lowest possible position and the list is updated.

# Deleting a Sync Mode

1. Select a controller in the Plant structure .

2. Select the Sync Mode icon in the Menu bar. The workspace area shows a list of all the current Sync Modes.

3. For each Sync Mode to be deleted, mark the check box in the left most column in the workspace area.

4. Select Manage, and then choose Delete from the drop-down menu.

   The selected Sync Mode is removed and the list is updated.

# Handling Tightening Sync Mode Configuration

- Double-click on a tightening Sync Mode to configure that Sync Mode.

Properties

Parameter | Description
--- | ---
Name | A user defined name for the mode.
Description | Description of the mode.

A tightening Sync Mode can be linked to a loosening Sync Mode. Referencing a loosening sync mode is located in the Properties menu of a tightening Sync Mode

1. Select the relevant loosening Sync Mode from the Loosening Sync mode drop-down.

   The number of bolt configurations and the channel numbers used in the bolt configurations of the tightening Sync Mode should be the same as the loosening Sync Mode selected and a warning is displayed if they differ.

## Reject management

When switch to Off:

Action if failure | Description
End all | All channels will end the tightening and report status NOK. The tightening that did not have an error itself will report additional info Terminated by other bolt.
Continue OK | The failing channels will end the tightening with status NOK. The remaining channels will continue with the rest of the tightening program.

When switch to On:

Parameter | Description
--- | ---
Max number of failing steps | Specifies the maximum number of different steps that can fail during the whole tightening. It does not matter if the same step fail more than once, it still only counts as one failing step. If not set an unlimited number of steps can fail.
Action if exceeded | Specifies the action if Maximum number of failing steps is exceeded.
Action if NOK during repair | Specifies the action if a new error (NOK) is detected while a repair is ongoing.

Triggers

To view the Sync point table a tightening program with sync points must be selected for at least one bolt in Bolt configuration.

For each synchronization point in the main path of the programs it is possible to specify different triggers to control the reject management.

Add trigger

1. Click on the + icon next to Add trigger.

2. Select trigger.

3. Set action for each sync point.

Delete trigger

1. Click on the + icon next to Add trigger.

2. Click on delete icon next to the trigger you want to delete.

Default trigger parameters | Description
--- | ---
Sync point | Sync point in the selected tightening program.
Default failing | Specifies the main action if an error is detected. Is used if none of the other conditions are fulfilled.
Default failing other | This parameter defines the action on the tools not running End or Terminate

Number of repairs parameters | Description
--- | ---
Repairs | Specifies the maximum number of repairs that can be started from the synchronization point and if not set, an unlimited number of repairs can be made
Repair action | Specifies the action if Maximum number of repairs have been made and a new error occurs
Repair action other | This parameter defines the action on the tools not running End or Terminate

NOK channels parameters | Description
--- | ---
NOK channels | Specifies the maximum number of channels that can fail in the synchronization point. If not set the number of failing channels settings will never be used to decide the action.
NOK channel action | Specifies the action if more than NOK channels have failed in the synchronization point.
NOK channel other | This parameter defines the action on the tools not running End NOK or Terminate NOK.

NOK groups parameters | Description
--- | ---
NOK groups | Specifies the maximum number of groups that can fail in the synchronization point. If not set the number of failing groups settings will never be used to decide the action.
NOK group action | Specifies the action if more than NOK groups have failed in the synchronization point.
NOK group other | This parameter defines the action on the tools not running End NOK or Terminate NOK.

Not repairable Parameters | Description
--- | ---
Not repairable | Specifies the action if the total status in the synchronization point is Not repairable.
NOK repairable other | This parameter defines the action on the tools not running End or Terminate.

## Bolt configuration

To add bolt configuration, click ADD or ADD MANY. You can have maximum 64 bolt configurations.

Parameter | Description
--- | ---
Check box | Used when, for example, deleting a channel.
Channel | Number of the channel, also named drive index.
Tightening program | Select tightening program defined in the menu Tightening Program.
Bolt | The actual fastener that is tightened when a tightening is made. This number will be used as the address when collecting data for the specific bolt, for example, in the fieldbus signal Bolt tightening status.
Bolt name (optional) | Name of the bolt.
Group | The repair groups are used to group bolts that depend on each other when running a repair. One channel can belong to none, one or more repair groups. If a group is specified for one bolt all the other bolts must also have a repair group defined, otherwise the Sync Mode is considered invalid.

In this Section

- Reject management

# Reject management

The reject management function is used for automatic repair or termination of failed steps. At each synchronization point the status of the tightening is evaluated. If the status is OK the next part of the tightening program starts. If the status is NOK an action is taken to repair, terminate or end the tightening program.

The repair path from each sync point is defined in the repair area in the tightening program.
The termination path from each sync point is defined in the termination area in the tightening program.

Status at a synchronization point

When all tools have reached a synchronization point the status of each tool and the total status is evaluated.

| OK | NOK | Not repairable | Fatal
--- | --- | --- | --- | ---
Status of a tool | Everything is OK so far. | The step(s) before the synchronization point has an error detected by a monitor. For these errors a repair is possible to do. | The step(s) before the synchronization point has an error detected by a restriction. | The step(s) before the synchronization point has a fatal error. Reasons for this can be: - Hardware errors in tool or drive - Max time in program restriction Time was exceeded - Max torque in program restriction Torque was exceeded.
Status for a repair group | All the tools in the repair group reached the synchronization point with status OK. | At least one of the tools in the repair group reached the synchronization point with status NOK (and none had the status Not repairable or Fatal). | At least one of the tools in the repair group reached the synchronization point with status Not repairable (and none had the status Fatal). | At least one of the tools in the repair group reached the synchronization point with status Fatal.
Total status | All the tools reached the synchronization point with status OK. The execution of the program continues with the next step in the tightening. | At least one of the tools reached the synchronization point with status NOK (and none had the status Not repairable or Fatal). | At least one of the tools reached the synchronization point with status Not repairable (and none had the status Fatal). | At least one of the tools reached the synchronization point with status Fatal.

Calculate action if total status at a synchronization point is NOK

If total status at a synchronization point is NOK the applicable action is calculated. The action is decided depending on the set triggers. The first trigger that is fulfilled decides the action to take:

1. Maximum number of failing steps exceeded:
   If the total number of failing steps in the whole tightening exceeds the number Max number of failing steps the Action of exceeded is used. If the same step fail more than once it still only counts as one failing step.

2. Maximum number of repairs exceeded:
   If the total number of repairs started from the current synchronization point exceeds the number Repairs in the Number of repairs trigger the Repair action is used.

3. Maximum number of failing groups:
   If the number of failing groups (groups that have status NOK) exceed the number NOK groups in the Number of NOK channels trigger the NOK group action is used.

4. Maximum number of failing tools:
   If the number of failing tools (tools that have status NOK ) exceed the number NOK channels in the Number of NOK groups trigger the NOK channel action is used.

5. Default failing action:
   If none of the conditions above is fulfilled the setting in Default failing action is used.

Action running a repair

A tool that runs a repair will run the steps in its repair path and jump back to a previous synchronization point. The repair is ongoing until the program returns to the synchronization point that started the repair. When the repair are done the status of the tools, repair groups and the total status will be evaluated again. If the total status is now OK all tools will continue with the next step, otherwise a new repair or termination is started.

The tools not running a repair will stay at the current synchronization point and wait for the repair to finish.

Action on status | Total status NOK
--- | ---
Repair NOK | All the tools with status NOK will run a repair. The tools not running a repair will stay at the current synchronization point and wait for the repair to finish.
Repair NOK groups | All tools that belong to a repair group with status NOK will run a repair. All the tools in the repair group will run a repair, regardless of their individual status. The tools not running a repair will stay at the current synchronization point and wait for the repair to finish.
Repair All | All the tools, regardless of their status, will run a repair.

Action running a termination

A tool that run a termination will run the steps in its termination path. After that the tightening is completed with status NOK.

Action on status | Total status NOK | Total status Not repairable
--- | --- | ---
Terminate NOK | All the tools with status NOK will run a termination. | All the tools with status NOK or Not repairable will run a termination.
Terminate NOK Groups | All tools that belong to a repair group with status NOK will run a termination. All the tools in the repair group will run a termination, regardless of their individual status. | All tools that belong to a repair group with status NOK or Not repairable will run a termination. All the tools in the repair group will run a termination, regardless of their individual status.
Terminate All | All the tools, regardless of their status, will run a termination.

The tools with status OK will continue according the setting Other :
- Continue, The other tools will wait on the current synchronization point until the termination is finished. After this they will continue with the remaining parts of the tightening program.
- End all, The other tools will end the tightening.

Action end a tightening program

A tool that end the tightening program will go directly to the end without running any other steps. After that the tightening is completed with status NOK.

Action on status | Total status NOK | Total status Not repairable
--- | --- | ---
End NOK | All the tools with status NOK will end the tightening without running the termination path. | All the tools with status NOK or Not repairable will end the tightening without running the termination path.
End NOK Groups | All tools that belong to a repair group with status NOK will end the tightening without running the termination path. All the tools in the repair group will end the tightening, regardless of their individual status. | All tools that belong to a repair group with status NOK or Not repairable will end the tightening without running the termination path. All the tools in the repair group will end the tightening, regardless of their individual status.
End All | All the tools, regardless of their status, will end the tightening without running the termination path.

The tools with status OK will continue according the setting Other :
- Continue: The other tools will continue with the remaining parts of the tightening program.
- Terminate all: The other tools will run a termination.

Action on total status Fatal

If the total status is Fatal a repair is not allowed. The tools with status Fatal cannot run anymore, so they will just end the tightening. The other tools will terminate, regardless of their individual status.

- If one of the bolts is NOK but has no repair action configured in the tightening program, the mode will end all. NOK will state the main NOK cause for that bolt.

- If one of the bolts is NOK and has a repair path, the system tries to repair until the maximum time limit is reached on the NOK bolt. The other bolts, which are OK, will wait. If the bolt gets OK after n number of repairs, the program continues as in the first bullet above with all the bolts. If the bolt still does not get OK, the whole sync mode will end as in bullet two.

# Handling Loosening Sync Mode Configuration

- Double-click on a loosening Sync Mode to configure that Sync Mode.

Properties
Parameter | Description
--- | ---
Name | A user defined name for the mode.
Description | Description of the mode.

## Bolt Configuration

The bolt configuration of a loosening Sync Mode can only be linked to a loosening multistep program and only lists the available loosening multistep programs.

To add bolt configurations, click ADD or ADD MANY. You can have maximum of 64 bolt configurations.

Parameter | Description
--- | ---
Check box | Used when, for example, deleting a channel.
Channel | Number of the channel, also named drive index.
Loosening program | Select the loosening multistep program defined in the menu Tightening Program.

# Running a Loosening Sync Mode

A loosening sync mode can be run in following possible ways.

All the conditions to start a tightening must be fulfilled (example: no emergency stop, enable signal is set and so on) in order for all the above cases to work correctly.

## Running a Loosening Sync Mode Using the Input Select Loosening

1. Select a tightening sync mode with an associated loosening sync mode.

   - This can be done by adding the I/O signal Select Input, Id 10020 in the To controller area in the Fieldbus sub-tab under Fieldbus and SoftPLC or this can also be done by selecting a task in the Task under the Virtual Station tab .

2. Select loosening using the I/O signal Select loosening, Id 10029 in the To controller area in the Fieldbus sub-tab under Fieldbus and SoftPLC .

3. Start the loosening using any of the two signals:

   - Start drive (continuos), Id 10028

   - Start drive (pulse), Id 10113

## Running a Loosening Sync Mode Using Input Start Loosening

1. Select a tightening sync mode with an associated loosening sync mode

   - This can be done by adding the I/O signal Select Input, Id 10020 in the To controller area in the Fieldbus sub-tab under Fieldbus and SoftPLC or this can also be done by selecting a task in the Task under the Virtual Station tab .

2. Start the loosening using any of these two signals:

   - Start loosening (continuous), Id 10011

   - Loosening pulse start (pulse), Id 10072

# Copying and Pasting Batch sequences, Sync modes and Sources

It is possible to copy and paste:

- Batch Sequences

- Sync modes

- Source Batches and Source Tightenings

The following rules applies for fixtured and synchronized applications:

- It can be done on the same controller

- It can be done between controllers of the same type that runs the same software version.

A copy of a batch sequence or source always includes everything as for example attached or associated programs and modes and links.

Example: A copy of a Source Batch > The paste creates a new Source batch with a new Batch Sequence and a Program linked to the new Source Batch.

Copying and pasting

1. Select a controller in the plant structure

2. Select Batch Sequence, Sync Mode or Source.

   The workspace area shows all the available programs.

3. Right-click on a single row or select check boxes for several rows, right click and select Copy.

4. To paste the copy into the same controller, right-click anywhere in the empty workspace area and select paste. The copy is added to the first available position in the existing list.

   If there is no space in the list for the copy, the whole operation will fail.

   To paste the copy into another controller; select a controller in the plant structure and then select the applicable workspace. Right-click in the workspace and select paste.

   It is also possible to paste a copy into the Program Templates library workspace.

5. Double-click the pasted copy to open and modify it.

# Exporting a Sync Mode

A Sync Mode can be exported from one controller and imported to another.

Export and Import are only possible if they are performed on the same controller, or different controllers running the same software version and controller type.

1. In the Plant structure , select a controller from the list.

2. On the menu bar, select the Sync Mode tab. The workspace area displays a list of all the current Sync Modes.

3. Select the check box of the Sync Mode to be exported.

4. Select Manage, and then choose Export from the drop-down menu.

   A browser window opens for saving the export file.

5. The default file name is <SyncModeName>.json, the exported file can be given any name with the *.json extension.
   Select Save.

# Importing a Sync Mode

A Sync Mode can be exported from one controller and imported to another.

Export and Import are only possible if they are performed on the same controller, or different controllers running the same software version and controller type.

1. In the Plant structure , select a controller from the list.

2. On the menu bar, select the Sync Mode tab. The workspace area displays a list of all the current Sync Modes.

3. Select the Add command button and select Import.

4. Select Open File and browse to select the relevant .json file.

5. Select Add.

When importing a Sync Mode, the connected Multistep Tightening Programs are also included. If there is no space to import the Multistep Tightening Programs, because the maximum number has already been reached, then the whole import operation will fail.

# Working with the Batch Sequence Tab

A Batch Sequence task is selected in a Virtual Station Task configuration, or by an external input source.

The tightening order can either follow a fixed scheme, or be left to the operator to decide in a free-order scheme. In either case, the sockets or signals can be used to communicate between the controller and the operator.

- A Batch consists of one tightening program, which is repeated a number of times.

- A Batch Sequence is an ordered set of batches, when the operation requires a combination of batches/tightening programs.

1. Select a controller in the Plant structure .

2. Go to Batch Sequence .

The columns contain the following information:

Batch sequence information
Column | Description
--- | ---
Name | Each Batch Sequence name starts with an index number. The following characters can be changed to any user defined name.
Description | The description of the batch sequence.
Last changed | Expressed in ToolsTalk 2 time.
Last changed by | Configuration data last changed by <user>.
Controller updated | Expressed in controller time.
Controller updated by | Controller updated by <user>.

The field Changed by and Controller updated by can be a registered ToolsTalk 2 user, created in the ToolsTalk 2 interface.

Command | Description
--- | ---
Manage | Export: Exports the Batch Sequence in .json format. Delete: Removes selected Batch Sequence from the list. Mark the check box for one or more batch sequences and select Manage, and then Delete from the drop-down list. The selected Batch Sequences are removed and the list is updated. The list of configurations will show irregularities in the index number scheme when a configuration is deleted. Index numbers do not change. Adding a new configuration will attempt to find the lowest free index position for a configuration.
Add | Create or Import a new Batch Sequence.

The Batch Sequence name consists of an index number combined with optional characters. The index position cannot be changed. A new configuration is given lowest possible available index number. The index number is important when using sources and identifier numbers to be part of the task selection process.

In this Section

- Batch Sequence Configuration Workspace
- Batch Sequence Configuration Menu
- Adding a New Batch to a Batch Sequence
- Copying and Pasting Batch sequences, Sync modes and Sources
- Exporting a Batch Sequence
- Importing a Batch Sequence
- Deleting a Batch in a Batch Sequence

# Batch Sequence Configuration Workspace

The Batch Sequence configuration workspace shows the details of a single batch sequence with the following configuration menus:

- Basic settings, with configuration name and description.

- General settings, controlling the flow and order of tightenings.

- Sequence configuration, creates the batch sequence from individual tightening programs.

Viewing the Batch Sequence menus

1. Select a controller in the Plant Structure workspace .

2. Select Batch Sequence in the menu bar.

3. Double-click on the Name of the desired batch sequence to display the menus.

# Batch Sequence Configuration Menu

The options in the Properties menu are as follows:

Parameter name | Description
--- | ---
Name | Default name Batch sequence. This can be edited.
Description | The optional description issued for the batch sequence.
Lock tool on batch sequence complete | A batch sequence is completed when the batch sequence counter is equal to the batch sequence size. On: The tool is locked and a tightening program or batch sequence must be selected to continue do tightenings. Off: After completion, the batch sequence is ready to be repeated.
Free order | No: The batches within the sequence are executed in the order listed by the index number. If sockets have been specified, the system will prompt for the next socket when the batch is to be done. Yes: The tightenings and the batches within the sequence can be executed in any order. The operator must indicate to the system which batch is to be executed by using the Socket selector bits which act as identifier numbers.
Increment on NOK | No: The batch counter is not incremented if the tightening fails (NOK). Yes: The batch counter is incremented if the tightening fails (NOK).
Max consecutive NOK | Max consecutive NOK is defined as the maximum allowed number of consecutive failed tightenings in a batch. If the value is reached, the event Too many NOK tightenings (4020) is displayed.
Decrement on loosening | Never: The batch counter is not decremented when a loosening is done. This is the default value. Always: The batch counter is decremented when a loosening is done. When last tightening OK: If the preceding tightening was OK, the batch counter is decremented when a loosening is done.
Sequence abort time | On: The selected batch sequence will be aborted within a specified time limit. When you select On, the Abort time field opens. Off: The selected batch sequence cannot be aborted.
Abort time | The number of seconds during which the selected batch sequence will be aborted. Allowed range is between 1 s to 1600 s.

A batch sequence is completed, and the tool may be locked, when either:

- All tightenings have been completed with an OK or NOK result.

- The Abort sequence signal terminates the task. Unperformed tightenings are reported with NOK result.

In the Sequence configuration menu, the different batches are combined into a batch sequence. A batch consists of one single tightening program that is repeated a number of times.

Each row in the Sequence configuration menu represents one single batch.

Workspace options
Column | Description
--- | ---
| Check box.
Batch | Batch index number (order number within the sequence).
Sync mode | Drop-down menu. Select sync mode for this batch.
Batch size | The number of tightenings the batch will consist of.
Identifier number | An externally generated identifier number or a Socket selector position translated into an identifier number. Using fixed order tightening, the operator is guided to pick the correct socket. Using free order tightening, the corresponding batch is selected when the operator picks a socket.

Relevant Information

- Pushing Configurations to a Controller

# Adding a New Batch to a Batch Sequence

1. In the Plant structure , select a controller from the list.

2. On the menu bar, select the Batch Sequence tab . The workspace displays a list of batch sequences.

3. Select the Add command button in the Sequence configuration menu. The To create a new Batch Sequence window opens.

4. Issue the Batch Sequence with a name, and then select ADD.

5. Select the relevant parameters in the Properties.

6. Select a Sync Mode for the batch in Sequence Configuration.

7. Enter the Batch Size (the number of tightenings the batch will consist of).

8. Enter an optional Identifier Number.

The new Batch Sequence will be issued the first free position in the sequence list. If there are no free slots it will be placed at the bottom of the list and assigned the lowest available index number. It is not possible to change the index number to rearrange the batch tightening order.

# Copying and Pasting Batch sequences, Sync modes and Sources

It is possible to copy and paste:

- Batch Sequences

- Sync modes

- Source Batches and Source Tightenings

The following rules applies for fixtured and synchronized applications:

- It can be done on the same controller

- It can be done between controllers of the same type that runs the same software version.

A copy of a batch sequence or source always includes everything as for example attached or associated programs and modes and links.

Example: A copy of a Source Batch > The paste creates a new Source batch with a new Batch Sequence and a Program linked to the new Source Batch.

Copying and pasting

1. Select a controller in the plant structure

2. Select Batch Sequence, Sync Mode or Source.

   The workspace area shows all the available programs.

3. Right-click on a single row or select check boxes for several rows, right click and select Copy.

4. To paste the copy into the same controller, right-click anywhere in the empty workspace area and select paste. The copy is added to the first available position in the existing list.

   If there is no space in the list for the copy, the whole operation will fail.

   To paste the copy into another controller; select a controller in the plant structure and then select the applicable workspace. Right-click in the workspace and select paste.

   It is also possible to paste a copy into the Program Templates library workspace.

5. Double-click the pasted copy to open and modify it.

# Exporting a Batch Sequence

A Batch Sequence can be exported from one controller and imported to another.

Export and Import are only possible if they are performed on the same controller, or different controllers running the same software version and controller type.

When you export an existing batch sequence, any programs and modes associated with the batch sequence are also exported. These configurations are only copies and can be changed as per requirements.

1. In the Plant structure , select a controller from the list.

2. On the menu bar, select the Batch Sequence tab . The workspace displays a list of all the current batch sequences.

3. Select the check box of the Batch Sequence to be exported.

4. Select Manage, and then choose Export from the drop-down menu.

   A browser window opens for saving the export file.

5. The default file name is <BatchSequenceName>.json, the exported file can be given any name with the *.json extension.
   Select Save.

# Importing a Batch Sequence

A Batch Sequence can be exported from one controller and imported to another.

Export and Import are only possible if they are performed on the same controller, or different controllers running the same software version and controller type.

When you import an existing batch sequence, any programs and modes associated with the batch sequence are also imported. These configurations are only copies and can be changed as per requirements.

1. In the Plant structure , select a controller from the list.

2. On the menu bar, select the Batch Sequence tab. The workspace area shows a list of all the current batch sequences.

3. Select the Add command button and select Import.

4. Select Open File and browse to select the relevant .json file.

5. Select Add.

If there are no available slots, then the Batch Sequence will be added to the bottom of the list and assigned the lowest available index number. It is not possible to change the index number to rearrange the order.

# Deleting a Batch in a Batch Sequence

1. In Batch Sequence , select the check box for the batch to be deleted. Selecting the check box enables the MANAGE command button function.

2. Select the MANAGE command button, and then select Delete from the drop-down list. The selected batches are removed from the list.

When a batch is deleted from the batch sequence, the index sequence is compressed and updated, leaving no gaps. The index number of the deleted batch sequence will be assigned automatically to the next sequence that is created.

# Working with the Sources Tab

Controller features, such as the Low Reaction Tightening Strategies and controller-wide functions among others, require licenses distributed through the Functionality Management System (FMS). Whereas configuration of features is possible without specific licenses, the assignment and use of those features will require the correct license to be installed on the controller. Please refer to Licenses (FMS) for more detailed information on licenses.

The selection of a task is done in the Task menu in the Virtual station configuration workspace.

External signals used as tasks for tightenings are configured in the Sources tab. Sources are accessories, or similar, connected to a virtual station. Two types of source tasks are available:

- Source Tightening task

- Source Batch task

Source Tightening is used to select a single sync mode.

Source Batch is used to select a batch sequence, a series of sync modes.

Relevant Information

- Assigning a Task to a Virtual Station

In this Section

- Source Tightening Overview
- Creating a Source Tightening
- Creating a Source Batch
- Significant Positions
- Copying and Pasting Batch sequences, Sync modes and Sources
- Exporting a Source Batch or a Source Tightening
- Importing a Source Batch or a Source Tightening

# Source Tightening Overview

The tightening menu shows a list of Source Batch and Source Tightening configurations. Separate lists can be linked to a Virtual Station by going to the Virtual Station in question, and in the Task properties selecting Choose. There, a Source can be chosen as a task. Source tightenings link a specific tightening program to an identifier number. When the identifier number is sent to the controller, the linked program will run over and over until a different signal is sent .

Parameter name | Description
--- | ---
Name | The name issued to the Source Tightening.
Description | The description of the Source Tightening.
Lock tool on batch sequence complete | On: The tool is locked when the batch sequence is completed. Off: The tool remains unlocked when the batch sequence is completed.
Increment on NOK | On: The batch will advance even if a NOK tightening is performed. Off : The batch will only advance if a successful tightening is performed.
Max consecutive NOK per program | On - Max consecutive NOK is configured on each individual program within the Source Tightening Task. Off - The Max consecutive NOK is configured on Source Tightening task level.
Max consecutive NOK | Set the number of consecutive NOK results to be allowed. If the value is set to 0, then there is no check performed for NOK tightenings. When reaching max consecutive NOK's, the controller locks the tool and the source tightening execution is halted.
Batch control | Select how the source tightening is to be executed: No batch control Internal batch control: Configure how many times a source tightening should be repeated. External batch control: Configure how many times a source tightening should be executed by using Open protocol or Fieldbus. Any configuration change clears the source tightening to start over from a clean and known state (the batch count in the batch will be reset to 0). Ongoing tightenings are able to finish before the changes take effect.

Command | Description
--- | ---
Add | Adds a new row with lowest identifier available.
Delete | Removes selected sync mode from the list. Select the sync mode by selecting the corresponding check box.

Relevant Information

- Assigning a Task to a Virtual Station

# Creating a Source Tightening

1. Select a controller in the Plant structure workspace .

2. Go to the Sources tab.

3. Select Add, the Create new source configuration dialog window opens. Choose Tightening from the drop-down menu then select Add.

4. Issue the Source Tightening with a name.

5. Set the number of Max consecutive NOK results to be allowed. If the value is set to 0, then there is no check performed for NOK tightenings. When reaching max consecutive NOK's, the controller locks the tool and the source tighteining execution is halted.

6. Select which Batch Control is to be used from the drop-down menu.

   Internal batch control: Configure how many times a source tightening should be repeated.

   External batch control: Configure how many times a source tightening should be executed by using Open protocol or Fieldbus. Any configuration change clears the source tightening so to start over from a clean and known state (the batch count in the batch will be reset to 0). Ongoing tightenings are able to finish before the changes take effect.

7. By default, only one editable Identifier number will be available when creating a new Source Tightening. Select Add to add more.

8. Give every item an identifier number

9. Choose a mode to link to each identifier number by selecting Mode and choosing from the list.

# Creating a Source Batch

1. Select a controller in the Plant structure workspace .

2. Go to the Sources tab.

3. Select Add, the Create new source configuration dialog window opens. Choose Batch from the drop-down menu then select Add.

4. Issue the Source Batch with a name

5. Set the Abort on new identifier to Yes if scanning a new identifier string should abort the previous scan.

6. Select the Identifier method (String for text, or Number for numerical strings).

7. Set Free order to On if the strings can be scanned in any order.

   Identifier strings can be made up of up to 4 different strings. When free order is set to No, the strings need to be scanned in a specific order for the system to recognize the string.

   An error may occur when Free order is set to On, and the lengths of the different strings are duplicated. The scanned sequence will then not activate a tightening program. To remedy this error, set Free order to Off, or adjust the string lengths.

8. Issue the string a Name and enter the length of the string. (For further information on concatenating strings, see Relevant Information in the User Guide).

9. Significant positions - the relevant positions in the string. (For further information on Significant Positions, see Relevant Information in the User Guide).

10. Saved positions - which positions are to be logged by the system. (For further information about Saved Positions, see Relevant Information in the User Guide).

11. Indicate which strings (in the String contains column) should be linked to which Batch sequence (in the Activates column). Select Add to add more strings.

Wildcards can be used when typing the "string contains". The wildcard(s) can be used at any position in the string. No Batch sequence is activated in case of an ambiguous matching result.

The wildcard is a . (period)

The Abort on new identifier controls how a second signal should be interpreted when a batch sequence has been activated and is ongoing.

If identifier numbers are used in the Batch sequence configuration , the input signal or the socket selector can be used to select a batch within a batch sequence.

The controller can be configured to select a batch sequence with input signal based on either an identifier number or an identifier string.

Relevant Information

- Assigning a Task to a Virtual Station
- Combining Identifier Strings
- Configuring Significant Positions to Read in Barcode String
- Saved Positions

# Significant Positions

Significant positions are used to specify which characters in the barcode string to read when putting together the string to match with your pre-defined string. The number of significant positions must match the number of characters in the pre-defined strings.

In this Section

- Configuring Significant Positions to Read in Barcode String
- Combining Identifier Strings
- Saved Positions

# Configuring Significant Positions to Read in Barcode String

The positions in the barcode string are associated with a number between 1 and 1024. The first position of the string is 1 and the last is 1024.

The significant positions must be specified following the rules described in the table below. Barcode strings:
Description | Significant positions | Valid configuration | Barcode string to match with pre-defined string
--- | --- | --- | ---
Significant positions in order | 1,2,3,7,8 | Ok | ABCGH
Significant positions in optional order | 7,1,2,3,8 | Ok | GABCH
Range of numbers | 1–3,7-8 | Ok | ABCGH

# Combining Identifier Strings

The identifier string that is used for matching is a combination of up to four strings from a factory management system or up to four scanner inputs that need to be combined into one string.

The Add and Delete command buttons manage how many strings are combined. The following parameters are available:

Parameters for combining identifier strings
Parameter | Description
--- | ---
Check box | Select an entry if it is to be deleted.
Name | The string must be given a name.
Length | The length of the string must be known and must be entered. This is important to be able to combine the correct string identifier.
Significant positions | The comma-separated positions or ranges (separated by hyphen) in the combined string that are used for matching.
Saved positions | The comma-separated positions or ranges in the strings that will be saved in the result.

If more than one identifier string is to be used, perform the following steps:

1. Press the Add command button to create a new entry in the table.

2. Issue the string a name.

3. Enter the length of the string.

4. Repeat steps 1-3 for every string to be added. Up to four strings can be combined.

The Start-End parameters in each row define the individual string positions in the combined string identifier that is used in the next step of the matching process.

The first part in the task selection process using an identifier string as an input, is to define which positions in the string that are to be activated:

- Enter the significant positions, to define which positions in the identifier string will be used for matching. The positions must be either comma-separated, or by range.

# Saved Positions

Saved positions is a field where the user can indicate which parts of each string used in the Source Batch will be saved, and how they will be represented in the log. In this field, indicate the positions in the string that need to be saved. Positions can constitute only parts of the entire string. If the field is left empty, the entire (concatenated) string will be saved. The table below shows some examples of saved position combinations.

Saved position values are comma-separated (without spaces), and ranges are indicated using a hyphen.

Identifier string | Positions
--- | ---
String 1: 1234567 | 1-7
String 2: abcdef | 8-13
String 3: GHIJKL | 14-19
String 4: 890 | 20-22

Saved position examples
Saved positions | Saved results
--- | ---
(empty) | 1234567abcdefGHIJKL890
1-3,9,11,15,20-22 | 123bdH890
8-12,1-7,19,20-21 will be changed automatically to: 1-12,19-21 | 1234567abcdeL89

# Copying and Pasting Batch sequences, Sync modes and Sources

It is possible to copy and paste:

- Batch Sequences

- Sync modes

- Source Batches and Source Tightenings

The following rules applies for fixtured and synchronized applications:

- It can be done on the same controller

- It can be done between controllers of the same type that runs the same software version.

A copy of a batch sequence or source always includes everything as for example attached or associated programs and modes and links.

Example: A copy of a Source Batch > The paste creates a new Source batch with a new Batch Sequence and a Program linked to the new Source Batch.

Copying and pasting

1. Select a controller in the plant structure

2. Select Batch Sequence, Sync Mode or Source.

   The workspace area shows all the available programs.

3. Right-click on a single row or select check boxes for several rows, right click and select Copy.

4. To paste the copy into the same controller, right-click anywhere in the empty workspace area and select paste. The copy is added to the first available position in the existing list.

   If there is no space in the list for the copy, the whole operation will fail.

   To paste the copy into another controller; select a controller in the plant structure and then select the applicable workspace. Right-click in the workspace and select paste.

   It is also possible to paste a copy into the Program Templates library workspace.

5. Double-click the pasted copy to open and modify it.

# Exporting a Source Batch or a Source Tightening

A Source batch or Source tightening can be exported from one controller and imported to another.

Export and Import are only possible if they are performed on the same controller, or different controllers of the same type and running the same software version.

When you export an existing Source batch or a Source tightening, any programs and modes associated with the tightening or batch sequence are also exported. These configurations are only copies and can be changed as per requirements.

1. In the Plant structure , select a controller from the list.

2. On the menu bar, select the Sources tab . The workspace displays a list of all the current Source batches and Source tightenings.

3. Select the check box of the Source batch or tightening to be exported.

4. Select Manage, and then choose Export from the drop-down menu.

   A browser window opens for saving the export file.

5. The default file name is <SourceBatch>.json or <SourceTightening>.json , the exported file can be given any name with the *.json extension.
   Select Save.

# Importing a Source Batch or a Source Tightening

A Source batch or Source tightening can be exported from one controller and imported to another.

Export and Import are only possible if they are performed on the same controller, or different controllers of the same type and running the same software version.

When you import an existing Source batch or a Source tightening, any programs and modes associated with the tightening or batch sequence are also imported. These configurations are only copies and can be changed as per requirements.

1. In the Plant structure , select a controller from the list.

2. On the menu bar, select the Sources tab . The workspace area shows a list of all the current Source batches and Source tightenings.

3. Select the Add command button and select Import.

4. Select Open File and browse to select the relevant .json file.

5. Select Add.

   The new Source batch or Source Tightening will be issued the first free position in the sequence list. If there are no free slots it will be placed at the bottom of the list and assigned the lowest available index number. It is not possible to change the index number.

# Working with the Configurations Tab

Scanners, Stacklights and Tools are just some of the examples of device types that are connected to the controller via the I/O bus. Multiple devices can be connected to the I/O bus and each type of device has its own set of configuration parameters. Before operation, the configurations must be assigned to a Virtual Station.

## Viewing Existing Configurations

1. Select a controller in the Plant structure .

2. Select the Configurations tab in the menu bar.

   The workspace area shows a list of all the current configurations.

3. Double-click on a row in the workspace list to view details of the selected configuration.

   The workspace area shows the configuration menus where it is possible to configure the selected device.

   Configuration overview list
   Column | Description
   --- | ---
   Check box | Select to get access to the Manage command button list.
   Description | Description of the configuration
   Name | Shows the name of the controller template.
   Type | Type of configuration set-up.
   Library link | Displays Yes if there is a library link for the configuration.
   Last changed | Last changes made, expressed in ToolsTalk 2 time.
   Changed by | Last changes made, by <user>
   Controller updated | Last changes made, expressed in controller time.
   Controller updated by | Last update of the controller made, by <user>

   The list can be sorted by clicking in the header of each column.

In this Section

- Adding a Configuration
- Importing a Configuration
- Deleting a Configuration
- Configuration Types

# Adding a Configuration

1. In Configurations , select ADD. The Create new configuration dialog window opens.

2. Select type of device from the drop-down list, and then select ADD

3. In the Properties menu, type in a configuration name and a description.

Depending on selected type of device, each configuration has their own set of input and output signals. How to configure each type of device is described separately.

Relevant Information

- General Virtual Station
- Indicatorbox

# Importing a Configuration

1. In Configurations , select Add. The Create new configuration dialog window opens.

2. Select the Import tab.

3. Select Open file.

   A browser window opens for reading the import file.

4. Select the desired import file. The file must be in the format <configuration_name>.json. Select Open.

5. Select Add in the dialog window.

# Deleting a Configuration

1. In Configurations , select the check box for the configuration to be deleted. Selecting the check box enables the MANAGE command button function.

2. Select MANAGE and then select Delete from the drop-down menu.

The selected configurations are removed from the list.

A configuration can only be deleted when it is not assigned to a Virtual Station.

# Configuration Types

# Internal I/O

The controller has two screw terminals located on the inside. They can be used to connect digital input and output signals.

All the digital input signals and the digital output signals that are listed in the Reference section can be routed to the internal I/O terminals.

For electrical specification and connections, see the controller documentation.

How to assign an accessory configuration to a Virtual Station is described in the Virtual Station section.

Relevant Information

- Adding an accessory to a Virtual Station
- Unassigning an Accessory from a Virtual Station

# I/O Expander

The I/O expander is connected to the I/O bus and provides an extension to connect digital input and output signals. Multiple expanders can be connected. Read the I/O expander documentation for address configuration and specifications of connections.

The following device types can be selected:

- I/O Hub: 8 channels

- I/O Expander: 16 channels

How to assign an accessory configuration to a Virtual Station is described in the Virtual Station section.

Relevant Information

- Adding an accessory to a Virtual Station
- Unassigning an Accessory from a Virtual Station

# Operator Panel

The Operator Panel is connected to the I/O bus and provides a configurable digital communication link between an operator and the controller. Lamps, buttons, buzzers and switches are used in the communication. Read the operator panel documentation for address configuration and specifications of connections.

How to assign an accessory configuration to a Virtual Station is described in the Virtual Station section.

Relevant Information

- Adding an accessory to a Virtual Station
- Unassigning an Accessory from a Virtual Station

# Stacklight

The Stacklight provides long distance visual communication from the controller to the operator. In addition to the lights, the accessory can be equipped with a button, key switch, buzzer and I/O connections.

The Stacklight is connected to the controller using the I/O bus. Multiple accessories can be connected on the I/O bus. Read the Stacklight documentation for address configuration and specifications of the connections.

How to assign an accessory configuration to a Virtual Station is described under the Virtual Station icon .

# Indicatorbox

The Indicatorbox is a flexible display indicator used to display status signals from the controller. The display is equipped with 20 dual color LEDs, these are mounted in a square with five LEDs at each side.

In this Section

- Configuring the Indicatorbox

# Configuring the Indicatorbox

Adding an LED configuration

1. Select Indicatorbox in the Configurations menu.

2. To add an LED click on the Add button.

3. Select LED letter in the Position box according to the illustration.

4. Select signal for red and green LED.

To remove an LED, select the LED and click on the DELETE button.

# Tool Configuration

With the Tool Configuration it is possible to activate and configure various functions related to the tool. Each tool configuration can be mapped to a tool in Hardware Layout Configuration.

To view or edit a tool configuration menu:

1. Select a controller in the Plant structure workspace .

2. Click Configurations in the Menu bar.

   The workspace area displays the current accessory configurations.

3. Add a new configuration or double click on an existing configuration with the type being a tool configuration.

4. Make necessary configurations. The parameters are described in each section.

The tool configuration is divided into the following menus:

Menu | Description
--- | ---
Properties | Configuration name and description and a tool type filter.
General | General parameters for the tool.
Multiple transducer (only available for FlexSystem) | Multiple transducer functionality.
Tool LEDs (only available for Synchronized tightening) | See Tool Configuration - Tool LEDs.
Buzzer (only available for Synchronized tightening) | See Tool Configuration - Buzzer.

## Properties

The Tool configuration should be given a unique name. An optional description field is also available.

The accessory configuration list displays all configurations in an alphabetical order

To view or edit a tool configuration menu:

1. Select a controller in the Plant structure workspace .

2. Select the Configuration icon in the menu bar.

   The workspace area shows a list of all the current accessory configurations.

3. Double-click on the name of the selected Tool configuration.

   The workspace area shows the details of the current configuration and is divided into different menus, one for each topic.

4. Enter a configuration name and a description in the Properties menu.

5. Select a tool type from the Filter by tool type drop-down menu.

   As the number of tools grow, the number of menus grow as well. To increase the visual comfort in the workspace, it is possible to filter menus and only show what is relevant for one selected tool type. The filter is set in the Properties menu. If No tool is selected, all the possible tool configuration parameters are displayed.

## General

Use Start source to set how to start the tool.

Start source | Description
--- | ---
Trigger only | Press the tool trigger to start the tightening.
Trigger OR Push | Press the tool trigger or push the tool against the joint to start the tightening.
Trigger AND Push | Press the tool trigger and push the tool against the joint to start the tightening.
Push only | Push the tool against the joint to start the tightening.
Digital input | Using an external digital input signal to trigger the start of the tightening.
Safety trigger | Press the safety trigger (both Main Trigger and Extra Trigger) to start the tightening.

## Multiple transducers

Only available for QST and IxB tools.

Depending on the tool type and the number of transducers, it is possible to set how the torque and angle transducers are used in a tightening. The transducers can be configured to be controlling or monitoring.

Multiple transducers
Parameter | Description
--- | ---
Controlling torque transducer | Set the torque transducer to use for tightening. Available settings: Auto: For QST tools, Torque is used by default. For IxB tools, Torque 2 is used by default. If Torque 2 is not available for the IxB tool type, Torque is used. Torque Torque 2
Controlling angle transducer | Set the angle transducer to use for tightening. Available settings: Auto: For QST tools, Motor angle is used by default. Motor angle Angle Angle 2

Select Details to open a sub-menu with more settings.

Monitor and reporting torque
Parameter | Description
--- | ---
Report monitoring torque values | If set, a Final Torque value will be reported from both the controlling and the monitoring transducer, including evaluation of the status for both (OK/High/Low).
Redundancy error reporting torque | Redundancy error is reported if the Final Torque measured on the controlling transducer differ from the value measured on the monitoring transducer.
Lock the tool on redundancy error | Lock the tool if a redundancy error is detected.

Torque transducer misc settings
Parameter | Description
--- | ---
Require dual torque | If set, the connected tool must have dual torque transducers (that are not disabled) to be able to run a tightening.
Monitoring torque in trace | If set, the values from the monitoring torque transducer are included in the trace.

Dual torque restrictions
Parameter | Description
--- | ---
Enable double torque restriction | If set, the double torque transducer restriction is active.
Maximum torque difference | The limit for the double torque difference restriction.

Monitor and reporting angle
Parameter | Description
--- | ---
Report monitoring angle values | If set, a Final Angle value will be reported from both the controlling and the monitoring transducer, including evaluation of the status for both (OK/High/Low).
Redundancy error reporting angle | Redundancy error is reported if the Final Angle measured on the controlling transducer differ from the value measured on the monitoring transducer.
Lock the tool on redundancy error | Lock the tool if a redundancy error is detected.

Angle transducer misc settings
Parameter | Description
--- | ---
Require dual angle | If set, the connected tool must have dual angle transducers (that are not disabled) to be able to run a tightening.
Monitoring angle in trace | If set, the values from the monitoring angle transducer is included in the trace.

Dual angle restrictions
Parameter | Description
--- | ---
Enable double angle restriction | If set, the double angle transducer restriction is active.
Maximum angle difference | The limit for the double angle difference restriction.

# Scanner

The Scanner is an accessory, it is installed directly to the controller via a USB cable.

In the Scanner configuration it is possible to configure the Pass through as On or Off. As default the configuration is Off. When Pass through is activated (set to On), the scanned barcode information is sent to either SoftPLC, or Fieldbus for decoding.

1. In the Plant structure workspace , select a controller.

2. In the tab menu bar in the workspace area, select the Configurations icon .

   The workspace area displays a list of configurations.

3. Double-click on a configuration row that has Scanner in the Type column.

   Alternatively, select Add to create a new scanner configuration.

Scanner options
Parameter | Description
--- | ---
Name | Optional name for the configuration
Description | Optional configuration description
Pass through = On | The scanned barcode is sent to either SoftPLC, or Fieldbus to be decoded
Pass through = Off | The scanned barcode is decoded in the controller

In this Section

- Scanner Configuration

# Scanner Configuration

The Scanner is a tool accessory that is installed on the tool and connected to the tool accessory bus. It has one function button that activates the Scanner.

In the Scanner configuration it is possible to configure the Pass through as On or Off. As default the configuration is Off. When Pass through is activated, On, the scanned barcode information is sent to either SoftPLC, or Fieldbus for decoding.

Configuring the Scanner

1. In the Plant structure workspace , select a controller.

2. In the tab menu bar in the workspace area, select the Configurations icon .

   The workspace area displays a list of configurations.

3. Click Add to create a new configuration.

4. Select Scanner from the Type of configuration drop-down

   and click Add

5. Make the selected configuration. The configurations are auto saved in ToolsTalk 2.

ST Scanner options.
Parameter | Description
--- | ---
Pass through = On | The scanned barcode is sent to either SoftPLC, or Fieldbus to be decoded
Pass through = Off | The scanned barcode is decoded in the controller

How to assign an accessory configuration to a virtual station is described in the Virtual station section.

# Socket Selector

# Viewing/Editing or Creating a Socket Selector Configuration

The Socket Selector is connected to the I/O and assists the operator in selecting the correct socket for the tightening procedure.

Viewing/Editing a Socket Selector Configuration

1. Select a controller in the Plant Structure .

2. Go to Configurations .

   The workspace area displays a list of created configurations for the selected controller.

3. Double-click on the name of the selected Socket Selector configuration in order to view or edit the configuration.

Creating a Socket Selector Configuration

1. In Configurations , selectAdd.

2. The Create new configuration dialog window is displayed. Choose Socket Selector form the drop-down list, and then select Add.

3. In the Properties area of the menu, enter a configuration name and description.

4. In the Socket Selector Configuration, choose Control type Auto or External.

5. For each socket position that should be active, select the check box .

6. For each socket position that should be inactive, clear the check box.

7. To add or remove a group of four sockets, select either Add or Remove.

Up to 32 socket selector positions can be used.

More information on how a configuration is addressed and assigned to a Virtual Station is given in the Virtual Station section .

# Socket Selector Control Switch

The Control switch has two positions:

Position | Description
--- | ---
Auto | The controller controls the LED lamps on the Socket Selector, which guide the operator to the correct socket selection.
External | The controller has no control of the socket selector. All functionality of the LED lamps is controlled by an external control system through the Open Protocol communication or by the Fieldbus module.

# General Virtual Station

Adding a General Virtual Station

1. In the Plant structure workspace , select a controller.

2. In the tab menu bar in the workspace area, select the Configurations icon .

   The workspace area displays a list of configurations.

3. Double-click on a configuration row that has General Virtual Station in the Type column.

   Alternatively, select Add to create a new General Virtual Station configuration .

Properties
Parameter | Description
--- | ---
Name | Optional name for the configuration
Description | Optional configuration description

When using Synchronized tightening or a Flex controller the following parameter is also visible in the General Virtual Station configuration.

Fixtured Stations

Auto Enable can use one of the following settings, the default setting is Never.

Setting | Description
--- | ---
Never | Input Enable Operation must be set high to be able to run a tightening.
Always | It is always possible to run tightenings regardless of the status of input Enable Operation.

To apply the General Virtual Station configuration, assign it to a Virtual Station in the Virtual Station section.

Only unassigned General Virtual Station configurations can be deleted.

Relevant Information

- Assigning a General Virtual Station Configuration
- Global Configurations Library - Creating a Global Configuration From An Existing
- Pushing Configurations to a Controller
- Working with the Configurations Tab

# Working with the Tools Tab

The Tools workspace displays a list of tools connected to the controller. The displayed menus differ between the controllers for fixtured tools and controllers for handheld tools and provide detailed information about connected tools.

In the menu Settings, tool alarms can be set. Trigger points for these alarms are taken from the Tools menu.

To view the tool menus:

1. Select a controller in the Plant structure workspace .

2. Go to Tools section.

   A list of tools connected to the controller is displayed.

   Column | Description
   --- | ---
   Tool type | Describes the type of the tool.
   Model | A detailed model number of the tool.
   Serial number | The serial number of the tool.
   MAC address | The MAC address is only visible if the tool has got a MAC address.
   Software version | The software version of the tool.
   Max torque | The maximum torque value the tool can produce.
   Max torque with TurboTight | The maximum torque value the tool can produce when using the TurboTight strategy. Applicable only to certain tools.
   Max torque with TensorPulse | The maximum torque value the tool can produce when using the TensorPulse strategy. Applicable only to certain tools.
   Max speed | The maximum rotation speed of the tool.
   Next calibration | Date for the next calibration of the tool.
   Virtual station | The name of the virtual station to which the tool is connected.
   Channel | The channel number of the tool.

3. Double-click on one of the tools in the table for more detailed information.

How to connect a tool or how to make a wireless pairing is described in the controller manual.

General information

The menu is valid for a controller that supports fixtured tools or handheld tools.

Information | Description
--- | ---
Model | Tool model denomination.
Serial number | Tool serial number.
MAC address | The MAC address is only visible if the tools have a MAC address.
Product number | The same as ordering number.
Software version | Tool software version number.

The general tool information is provided by the tool itself to the controller and to ToolsTalk 2.

Limits

The menu is valid for a controller that supports fixtured tools or handheld tools.

Information | Description
--- | ---
Max torque | The maximum torque the tool can use for a tightening.
Max speed | The maximum rotation speed of the tool.
Min torque | The minimum torque the tool can use for a tightening.
Gear ratio | The ratio of the angular velocity of the input gear to the angular velocity of the output gear.

The tool limit information is provided by the tool itself to the controller and to ToolsTalk 2.

Connection

Connection to the controller and to which virtual station it is assigned.

Service settings

Calibration

The menu is used to control how well a tool corresponds to a reference transducer and how to adjust differences.

The calibration value is stored in the tool memory and is used to adjust the torque value given by the tool’s torque transducer so that the correct torque value is displayed on the controller. The controller displays last calibration date.

Tool calibration is carried out at the controller and uses a torque reference transducer. This process is described in the Power Focus 6000 manual.

Store the new calibration value in the tool memory by entering the calculated value, and then click Set.

Parameter | Description
--- | ---
Last calibrated | Date for last calibration.
Calibration value | Enter the measured and calculated value into the parameter entry box.
Next calibration | Due date for next calibration.
Set | Stores the entered values.

Maintenance

The tool stores a service interval number and counts how many tightenings that can be performed before the next tool maintenance or service should be performed.

Parameter | Description
--- | ---
Last service | Date and time when last service was performed. The last service date is set at the repair workshop. The Last service date is set to current date and time when the Reset button is pressed.
Total tightenings at service | The Total tightenings at service is the total number of tightenings performed by the tool since it was used for the first time. This value is updated at service, and will remain the same until the next service.
Remaining tightenings | Total number of tightenings left until the service interval is reached.
Service interval | Number of tightenings to be performed before the next service. Can be set in multiples of 10 000.
Set | The command stores the value entered in the Service interval parameter entry field and adjusts the value to a multiple of 10 000.
Reset service counter/data | The Reset command resets the counter and sets the Last service date to the current date.

Transducer information

Only available for QST and IxB tools.

A tool can have several torque and angle transducers depending on tool type. An image shows the position of the transducers.

Select Details for more information about the torque or angle transducers. Depending on transducer type the following information can be available.

Angle transducer
Information | Description
--- | ---
Enabled | Indicates if the transducer is enabled.
Gear ratio | The gear ratio between the transducer and the out-going shaft of the tool.
Wind-up | The wind-up compensation factor for the angle transducer.

Torque transducer
Information | Description
--- | ---
Enabled | Indicates if the transducer is enabled.
Serial Number | Serial number of the transducer as a string.
Article Number | Article number of the transducer as a string.
Calibration Value | Calibration value for the transducer expressed in Nm.

Health

The menu provides data from environmental monitors. The equipment measures parameters regularly and stores them.

Parameter | Description | Value
--- | --- | ---
Refresh | Command button: read tool value. |
History | Command button: History window opens to display latest temperature readings. |
Tool motor temperature | Latest temperature recording expressed in month/day/year hours:minutes:seconds. | Degree C or F
Tool electronics temperature | Latest temperature recording expressed in month/day/year hours:minutes:seconds. | Degree C or F

Zero offset and shunt limits

Only available for FlexSystem.

A tool can have one main and one secondary torque transducers. For each torque transducer, the limits show here.

Information | Description
--- | ---
Shunt Limit | Maximum allowed measured shunt calibration value in %.
Shunt Drift Limit | Maximum allowed change in measured shunt calibration value in %.
Zero Offset Limit | Maximum allowed Zero offset compensation in %.
Zero Offset Drift Limit | Maximum allowed change in the zero offset compensation in %.

# Working with the Virtual Station Tab

The Virtual Station tab is located in the controller menu bar when a controller has been selected in the Plant structure

A virtual station is a software abstraction of a controller. Within one controller it is possible to create several virtual stations. Each virtual station behaves like a controller. The various configurations can be assigned to virtual stations as needed.

It is possible to select a task, assign accessory configurations, assign a tool, monitor and manipulate incoming and outgoing signals via diagnostics and set communication protocol parameters from the virtual station menu. The virtual station icon is available for both a FlexController and a Power Focus 6000.

Controller features, such as the Low Reaction Tightening Strategies and controller-wide functions among others, require licenses distributed through the Functionality Management System (FMS). Whereas configuration of features is possible without specific licenses, the assignment and use of those features will require the correct license to be installed on the controller. Please refer to Licenses (FMS) for more detailed information on licenses.

In this Section

- Virtual Station Overview
- Virtual Station - Properties
- Assigning License Types and Features to a Virtual Station
- Assigning a Task to a Virtual Station
- Virtual Station - Protocols
- Fieldbus Mapping in a Virtual Station
- Assigning Accessories to a Virtual Station
- Unassigning an Accessory from a Virtual Station
- Assigning a General Virtual Station Configuration

# Virtual Station Overview

To open the Virtual station workspace and view the list of virtual stations:

1. Select a controller in the Plant structure workspace .

2. Select the Virtual station tab in the menu bar.

   The workspace area displays a list of virtual stations in the controller. The list is empty if no virtual stations have been created.

Virtual station workspace information
Column | Description
--- | ---
Check box | Selects a virtual station.
Name | Shows the name of the virtual station.
Description | Description of the virtual station.
Changed by | Which user that made changes
Controller updated | Last time the controller was updated
Controller updated by | Which user that has updated the controller

Virtual station workspace command buttons
Command | Description
--- | ---
Add | Creates a new virtual station. Newly created virtual station needs to be pushed to controller to get full functionality.
Delete | Removes the selected virtual stations from the list.

To access the virtual station configuration menu:

## Navigating to Virtual station configuration

1. In the Plant structure workspace select a controller .

2. Select the Virtual Station tab .
   The virtual station overview shows a list of virtual stations for the selected controller. The list is empty if no virtual stations have been created.

3. Double-click on a virtual station to open an existing configuration, or click Add to create a new virtual station configuration.

The following menus are displayed:

Workspace information
Menu | Description
--- | ---
Properties | Issues the configuration a name and description. Optional.
Protocols | Activation and configuration of external communication protocols.
Tool | Assigns a tool to the virtual station.
Tool configuration | Assigns a tool configuration to the virtual station.
Fieldbus mapping | Displays a fieldbus mapping if it is configured and assigned to the controller. This field is information only. The actual fieldbus mapping and configuration is done in theFieldbus and SoftPLC tab.
Task | Assigns a task to the virtual station or configures how a source signal selects the task to be performed.
Accessories | Assigns an accessory configuration and an address to an accessory and assigns the combination to a virtual station.
General | Used when assigning a General Virtual Station.
Manual Mode | Used to configure the Manual Mode function.
Licenses | Used for assigning and removing licenses and features to a virtual station.

For a FlexController, only the Properties, Fieldbus mapping and Task menus are available.

Relevant Information

- Pushing Configurations to a Controller

# Virtual Station - Properties

A virtual station must have a name. This is configured in the Properties menu. The default name is Virtual station <index nr>. An optional description field is also available.

If the name field is left blank, a red error indicator is displayed .

# Assigning License Types and Features to a Virtual Station

In the Virtual Station area licenses can be assigned to specific Virtual Stations. Select a controller from the Plant Structure then select the Virtual Station tab. A list containing the different virtual stations is displayed.

Assigning a Virtual Station Type

1. Double-click on the row to be configured.

2. In Licenses configuration, select Virtual Station Type.

3. Select one of the following options:

   - Change to change the current type, a dialog window opens containing the available types.

   - Remove to remove the current type.

   - Choose to add a new type. Choose the type and select OK.

Assigning Virtual Station Features

1. Double-click on the row to be configured.

2. In Licenses configuration, select Virtual Station Features.

3. Select one of the following options:

   - Add to add a new feature, a dialog window opens containing the available features . Choose the feature and select OK.

   - Remove to remove the current type.

# Assigning a Task to a Virtual Station

The Task menu in the Virtual station window controls the task selection.

The Task menu is used to assign a task to the virtual station.

Task menu information
Function | Description
--- | ---
Name | Currently assigned task to the virtual station.
Unassign | Command button. Deselects any task from the virtual station.
Choose | Command button. Change the task manually or configure external sources to select a task. The Choose task pop-up window opens to configure the task selection.
Change | Command button. If a task is already selected, then the Choose command button is replaced by Change. Select Change to select a new task.

## Navigating to Virtual station configuration

1. In the Plant structure workspace select a controller .

2. Select the Virtual Station tab .
   The virtual station overview shows a list of virtual stations for the selected controller. The list is empty if no virtual stations have been created.

3. Double-click on a virtual station to open an existing configuration, or click Add to create a new virtual station configuration.

4. Click Choose in the Task menu.

   The Choose task pop-up window appears.

5. Select the desired task in the Sync Mode, Sources or Batch sequence tab.

6. Click Choose. The Choose task pop-up window is closed.

   The Close button closes the pop-up window without making any changes.

7. Update the controller through the push function.

The name field is updated in the Task menu.

The task selection using sources and identifier numbers and identifier strings to select a task is described in detail in the documentation for the sources configuration.

Relevant Information

- Pushing Configurations to a Controller

# Virtual Station - Protocols

The Protocols menu may contain one or more implemented communication protocols and their parameter settings. The availability of protocols depends on the IAM license.

Some communication protocols are configured in the Protocols menu.

In this Section

- Open Protocol

# Open Protocol

## Configuring open protocol

1. In the Plant structure workspace select a controller .

2. Select the Virtual Station tab .
   The virtual station overview shows a list of virtual stations for the selected controller. The list is empty if no virtual stations have been created.

3. Double-click on a virtual station to open an existing configuration, or click Add to create a new virtual station configuration.

4. Click on Configure in the Protocols menu.

- The virtual station Open protocol configuration switch allows a user to enable or to disable Open protocol communication between a virtual station and the integrator, which is part of the factory control equipment.

  Select On or Off to enable or disable the Open protocol communication

  The Open protocol uses the same factory ethernet connection on the controller that is used for configuration or for delivering tightening results.

  Each virtual station is uniquely identified by a port number. For each virtual station using the open protocol, a port number must be entered in the port field.

- The legacy counter setting counts all tightenings in a sequence and outputs that number to secondary systems. To enable this setting, set Use legacy counter to On.

- SoftPLC Index is used to map where in the shared memory the Open Protocol commands are to be written. The default value is 1 but it is possible to enter values 1 to 6.

As the default value for SoftPLC Index is always 1 and no check is made if it already has been used, there is a possibility that you may have configured the system so that the same index is configured several times when adding Virtual stations. In this case the Soft PLC will not be able to determine from which Virtual Station the incoming MID is originating from.

# Fieldbus Mapping in a Virtual Station

A controller may have one Fieldbus communication module installed. This communication module serves all the virtual stations. The Fieldbus mapping menu shows which fieldbus configuration is mapped to the controller. Fieldbus is configured and the configurations are assigned and mapped in Fieldbus and SoftPLC

In this Section

- Fieldbus Diagnostics

# Fieldbus Diagnostics

To access the Fieldbus mapping diagnose function:

1. Select a controller in the Plant structure workspace .

2. Go to Virtual Station .

   The workspace area displays a list of virtual stations in the controller. The list is empty if no virtual stations have been created.

3. Double-click on a virtual station name to open an existing configuration or select Add to create a new virtual station configuration.

4. The workspace shows the menu, including mapped fieldbus.

5. Click the Diagnose button to enter the Fieldbus diagnose function.

The fieldbus diagnostics function provides the possibility to Monitor the incoming and outgoing signals, sent to and received from the fieldbus. It is also possible to manipulate the information, compose and send frames, via Forced mode. Fieldbus diagnostics can be used from:

- Controller GUI

- Web GUI

- ToolsTalk

Fieldbus diagnostics - forced mode

Diagnostics mode | Activate Monitor mode or Forced mode. Monitor mode: In monitoring mode it is possible to see the status of all configured fields in the incoming and outgoing frames, sent to and received from the fieldbus. Whenever there is a change in any of the bits of a received frame, the view is updated. Forced mode: When entering forced mode, the data will freeze in its current state, the frame is locked. In forced mode it is possible to activate and deactivate signals manually, or enter values and force them on one or more signals. This is possible on the incoming frame, the outgoing frame, or both.
Boolean converter | Switch between System view and Bus view. The converter makes it possible to invert the signals sent to or received from the fieldbus.
Type | Type of signal.
Byte | Location in frame.
Bit | Location in frame.
Length | Length of signal in frame.
Name | Name of signal.
Has converter | Has converter is Yes if any converter is configured. If Yes, the converter can be used to invert the signal. If No, the converter is not applicable.
Value | The Value column shows a list of signals and their values. The value of each signal in the incoming and outgoing frame is seen in the following formats: boolean, integer or string, depending on type. The values are editable in Forced mode. It is possible to change one signal, a few signals or all signals in the same frame. After changing the values, click Send frame button for the new frame to be pushed to the controller and for the new values to be applied. When leaving diagnostics mode, all values are reverted to as they were in the last saved frame of incoming and outgoing signals.

Only one diagnostics session can be active at a time. If the diagnostics is already in use, an information message is shown on the screen.

# Assigning Accessories to a Virtual Station

This menu is only valid for a controller that supports a handheld tool.

A controller may have several accessories connected through a CAN bus. Each accessory must have a unique address on the bus within the range 1-15. It is possible to assign several accessories to a virtual station.

An accessory must have an accessory configuration assigned to it, before it is possible to assign the accessory to the virtual station.

To view the current accessory assignment to a virtual station:

## Navigating to Virtual station configuration

1. In the Plant structure workspace select a controller .

2. Select the Virtual Station tab .
   The virtual station overview shows a list of virtual stations for the selected controller. The list is empty if no virtual stations have been created.

3. Double-click on a virtual station to open an existing configuration, or click Add to create a new virtual station configuration.

Accessories menu information
Function | Description
--- | ---
Check box | Selects an accessory configuration that can be unassigned from the virtual station.
Name | Name of the configuration assigned to the accessory.
Type | Type of accessory.
CAN node | The CAN address of the accessory.
Serial number | The serial number of the accessory.
Status | Can be either: Connected. Assigned but not connected.

The CAN node column shows the used addresses which can not be used when new accessories are connected. An assignment for a socket selector can include multiple addresses.

For socket selectors the order of the CAN nodes is important. The lowest position in the first socket selector is the first position in the assignment.

Accessory menu command buttons
Function | Description
--- | ---
Unassign | The selected accessory is unassigned from the virtual station. The accessory remains connected to the controller.
Choose | Adds a new accessory. The Accessories pop-up window opens.
Diagnose | Monitoring of I/O signal behavior and possibility to force signals to a desired state between controller internal logic and the accessory.

Relevant Information

- Pushing Configurations to a Controller

In this Section

- Adding an Accessory to a Virtual Station

# Adding an Accessory to a Virtual Station

The selected accessory must have a unique and valid CAN bus address. An accessory configuration is assigned to an accessory and the accessory is assigned to a virtual station.

## Navigating to Virtual station configuration

1. In the Plant structure workspace select a controller .

2. Select the Virtual Station tab .
   The virtual station overview shows a list of virtual stations for the selected controller. The list is empty if no virtual stations have been created.

3. Double-click on a virtual station to open an existing configuration, or click Add to create a new virtual station configuration.

To assign an accessory to the virtual station:

1. Click the Choose button in the Accessories menu to open up the Accessories pop-up window.

2. Select an accessory type from one of the tabs.

   - Internal I/O

   - Socket selector

   - I/O expander

   - Operator panel

   - Stacklight

   - Scanner

   - Indicatorbox

3. Check to select a configuration in the list of Configurations.

4. Check select an address in the list of Available CAN nodes if applicable.

5. Click the Choose button and add one of the accessory options.

6. Repeat the procedure for each accessory that is to be assigned to the virtual station.

7. Click the Cancel button to close the pop-up window.

   The Accessories menu is updated and shows new assigned configurations.

An accessory address is set by a rotary switch on the accessory. See detailed product information documents for the accessory. Accessory address range is between 1 and 15.

Relevant Information

- Pushing Configurations to a Controller

# Unassigning an Accessory from a Virtual Station

To unassign an accessory configuration and remove the connection to a virtual station, perform the following steps:

## Navigating to Virtual station configuration

1. In the Plant structure workspace select a controller .

2. Select the Virtual Station tab .
   The virtual station overview shows a list of virtual stations for the selected controller. The list is empty if no virtual stations have been created.

3. Double-click on a virtual station to open an existing configuration, or click Add to create a new virtual station configuration.

4. Mark the check box of the accessory configurations that is to be unassigned in the Accessories menu.

5. Select the Unassign command button in the Accessories menu.

6. To update the controller with any changes, select the Push changes command button .

The list in the accessory menu will be updated.

Relevant Information

- Pushing Configurations to a Controller

# Assigning a General Virtual Station Configuration

## Navigating to Virtual station configuration

1. In the Plant structure workspace select a controller .

2. Select the Virtual Station tab .
   The virtual station overview shows a list of virtual stations for the selected controller. The list is empty if no virtual stations have been created.

3. Double-click on a virtual station to open an existing configuration, or click Add to create a new virtual station configuration.

## To assign a General configuration to the virtual station

1. In the virtual station configuration workspace, go to the General area.

2. Select Change. In the pop-up window: The listed General configurations are the ones added in Configurations .

3. Select one of the general configurations and select the Change button.

   The General menu is updated with the selected general configuration.

Only unassigned general virtual station configurations can be deleted.

Relevant Information

- Pushing Configurations to a Controller
- Working with the Configurations Tab

# Working with the Controller Information Tab

The menus in the Controller Information tab provide information about a single selected controller.

## Viewing the Controller Information menus:

1. Select a controller in the Plant structure workspace .

2. Go to theController tab.

   The workspace area displays the Controller menus.

In the Controller workspace, the following menus are shown:

Controller information
Menu | Functionality
--- | ---
Controller information | Provides general information about the controller and the IAM module. If the controller sends information or a configuration that is not valid, then an exception along with the parameters affected is displayed as an error message.
Licenses | Provides information about the different license types which have been issued to the controller.
Software | Provides information about the software configuration of the controller.
Hardware | Provides information about the hardware configuration of the controller.
Export / Import | Provides export of controller results and configurations, and import of controller configurations. A dialog box appears to for file location.
Health | Monitors and records environmental parameters and system health parameters.

The information displayed is for information only. No setting of parameters is possible in the menus.

In this Section

- Controller Information and IAM Menu
- Software Menu
- Licenses
- Hardware Configuration
- Export and Import
- Automated Backup
- System Health Monitor
- Server Connection Status

# Controller Information and IAM Menu

The Intelligent Application Module (IAM) is located on the inside of the controller door. It contains the controller program, configuration parameters and stored results.

The IAM module can easily be removed and moved into another controller, which then will behave exactly as the previous controller.

## Viewing the Controller information Menus and Current Configurations

1. Select a controller in the Plant structure .

2. Go to Controller .

   The workspace area displays the Controller menus.

Controller model information
Menu | Functionality
--- | ---
Model | Provides general information about the type of controller.
Serial number | Provides information about the serial number of the controller.
Service Ethernet port | Provides information about the IP address of the service port. Through this port a service engineer can access the controller without being connected to the factory network.

Controller IAM information
Menu | Functionality
--- | ---
Type | Atlas Copco provides different IAM types with different functionality.
Customer key | Is an identifier for application-specific or customer-specific configurations.
Serial number | Provides information about the serial number of the IAM module.

# Software Menu

1. Select a controller in the Plant structure workspace .

2. Go to Controller .

   The workspace area displays the Controller menus.

Controller software version
Menu | Functionality
--- | ---
Current version | The main active working software.
Stored version | A stored inactive software.

It is possible to switch between installed software versions and this has two advantages:

- Controller software can be loaded to controllers in parallel to normal operation. If several controllers are to be updated, a switch can then be made very quickly on all controllers at the same time.

- If a software upgrade results in unexpected results, a switch to the previous version is a quick back-up fix.

Relevant Information

- Introduction to Controller Software and Data Management
- Switching Controller Software
- Updating Controller Software

# Licenses

This field displays the available license types and features that have been issued to the controller.

# Hardware Configuration

This menu provides information about the system hardware configuration.

1. Select a controller in the Plant structure workspace .

2. Go to Controller .

   The workspace area displays the Controller menus.

The Hardware menu lists the different hardware modules that make up the controller.

For each module, the following data is provided:

- Serial number

- Article number

- Software version

# Export and Import

The export and import function is used to export the events and tightening results accessible in the Results menu for analysis in external programs, as well as allowing transfer of tightening program, batch, and controller configurations between controllers.

The command Export can be used for the following reasons:

- Exporting tightening results and events for further processing.

- Exporting log files for debug assistance from an Atlas Copco service engineer.

- Exporting the entire controller configuration that can be used to copy the configuration to another controller.

- Comparing two exported configurations to see differences.

Exporting Controller Information

1. Select a controller in the Plant structure .

2. Go to Controller .

   The workspace area displays the Controller menu.

3. Click the Export button to export one of the following:

   Parameter | Description
   --- | ---
   Export | Exports all controller information.
   Export Configuration | Exports settings and configurations.
   Export Tool Log | Exports logs (tightenings and hardware information) from connected tools. Available for SRB, TBP, STB and QST-M. The export consists of atlas_tool_i.zip and ExportInfo.txt

4. Select the location for saving the export file, click OK.

Importing Controller Information

1. Select a controller in the Plant structure .

2. Go to Controller .

   The workspace area displays the Controller menu.

3. To import controller configurations, click the Import command button.

4. Click Open file. Select the file to import.

   The import file must be a previously exported file.

   When using the import function, all settings for tightening program, batch, accessories, and controller are replaced by the settings from the import file. However, settings for network, PIN, and results and events are not imported.

# Automated Backup

The Automated Backup window enables or disables sFTP export.

By default, Enable sFTP export switch is set to OFF.
When turning ON Enable sFTP export switch, an export file is created 10 minutes after the last configuration change.
If Enable sFTP export switch is set to ON on system startup, an export file is automatically created within 2-3 minutes. The export file is created within 2-3 minutes to reflect changes that might have been done before the system was shutdown.

The old Backup file is deleted before the new Backup file is available.

The data in the exported file include all configurations and settings of the controller.

The sFTP users can retrieve the exported file stored in the following directory of the system: /Export/<export file name>.

A system supporting sFTP is needed.

To retrieve the file sFTP users do not need to use any password.

The username for sFTP users is as follows:

Username | autoexport

# System Health Monitor

The equipment health monitor regularly measures parameters and stores them.

1. Select a controller in the Plant structure workspace .

2. Go to Controller .

   The workspace area displays the Controller menus.

   The Health menu displays environmental data and system health information.

Controller health monitor
Information | Value | Description
--- | --- | ---
Refresh command button | Degree C or F | Reads information from the controller and displays the latest result.
Controller temperature | Degree C or F | Latest temperature recording expressed in month/day/year hour:minute:second.
Battery status | OK/NOK | Monitors the memory and real time clock battery in the controller computer board. Status message NOK, means the battery needs to be changed as soon as possible to avoid loss of data or wrong results. Latest recording expressed in month/day/year hour:minute:second.
History command button |  | Provides a list of monitor readings.

# Server Connection Status

The server connection status shows the connection status of the server. Currently, only the server that is connected to ToolsNet is available.

1. Select a controller in the Plant structure workspace .

2. Go to Controller .

   The workspace area displays the Controller menus.

   The Server Connection Status menu displays the status of server.

Server Connection Status
Information | Description
--- | ---
Refresh command button | Reads information from the controller and displays the latest information.
Configuration | Shows if the configuration is enabled on the controller. To enable the configuration, configure Server connections in Settings on the controller.
Connection | Shows the status of the connections to the server: OK / NOK
Server message | Message from the server.

# Working with the Settings Tab

# Preferences

The settings menu contains a preferences section, which is used to select language, torque units and PIN protection of the controller interface.

To set controller preferences:

1. Select a controller in the Plant structure .

2. Go to Settings .

   The workspace area displays the Settings menus.

Parameters for controller preference:

Parameter | Description | Default
--- | --- | ---
Torque unit | Selects the unit in which torque measurement results shall be displayed for this controller in the controller GUI or web GUI. | Nm
Temperature unit | Selects the unit in which temperature measurement results shall be displayed for this controller in the controller GUI or web GUI. | Celcius
Language | Selects the language for the controller that shall be displayed for this controller in the controller GUI or web GUI. | English
Access via factory port | On/Off. Enables (On) or disables (Off) the communication with the controller. | On
Use PIN | A PIN can be enabled for this controller when accessed through the controller GUI or webHMI (factory network). PIN only applies to users accessing Controller through its GUI or webHMI. User is not locked out from ToolsTalk 2 or from working with (configuring and pushing configuration) the controller from ToolsTalk 2 because of the activated PIN. On: User accessing the controller must use PIN code in order to get write access to the controller. Off: No PIN code is required for user to get write access to the controller. | Off
Use PIN for Service Port | A PIN can be enabled for the controller when accessed through the service port. On: User accessing the controller must use PIN code in order to get write access to the controller. Off: No PIN code is required for user to get write access to the controller. Use PIN for Service Port is enabled only when the Use PIN is set to On. Use PIN for Service Port uses the same Pin codes configured and Inactivity timeout as user going through the factory network. | Off
Pin codes | Select a 4 digit PIN code per added user. Enable/disable user PINs. |
Inactivity timeout | The controller GUI or web GUI is automatically locked after an inactivity timeout. Minimum value is 20s. | 120 s

The Pin codes and the Inactivity timeout are enabled for editing even when the Use PIN is set to Off.

Relevant Information

- Pushing Configurations to a Controller

In this Section

- PIN Settings
- Tool service alarms

# PIN Settings

Using a PIN prevents unauthorized usage of the controller or accidental changes. It is possible to have one or many different PIN configurations on the controller and one of the ways of configuring is through the ToolsTalk 2 Software. Users can decide whether or not to activate one or several PIN configurations at the same time. A maximum of ten users can be added to the controller, each with their own PIN.

Each PIN configuration has a PIN code, a user name, a switch for enabling or disabling the user/PIN, and a list of available configurations that the user can access.

When PIN is enabled and the screen is locked, a locked padlock icon is shown at the upper-right corner of the GUI. The user can access and make changes only to the selected configuration(s) without entering any PIN code, and browse the unselected configurations with read-only access only. The unselected configurations are greyed out or disabled.

The screen lock goes automatically on after a certain time of inactivity, configurable by the user.
The minimum value of the inactivity time is 20 sec and the maximum value is 600 sec. The inactivity time is configurable and applies to all PIN configurations.

After a system startup, the controller is locked if the PIN is turned on, regardless of the current inactivity time.

When PIN is activated, a PIN code is required when accessing the controller via:

- The controller GUI

- The web GUI

In this Section

- Configuring the PIN
- Accessing the Controller When Locked By PIN
- PIN Code for Station Setup

# Configuring the PIN

1. Go to the Settings menu, set Use PIN to On.

2. Select PIN CODES.

## Adding PIN Codes for New Users

1. Select Add in the Pin codes dialog window.

2. Enter the username in the Name field.

3. Enter the PIN in the Set PIN field to set the PIN for the user and repeat the same PIN in the Repeat PIN field . The PIN must be a four-digit number in the range 0000–9999.

   The PIN in both fields (Set PIN and Repeat PIN) need to match.

4. select the Enabled check box to enable the PIN code for that user.

   When PIN is enabled, the controller is locked automatically after the configured inactivity time.

   To disable a PIN, clear the Enabled check box for that user.

## Deleting a User/PIN

- In the list of users, mark the check box for each user PIN to delete and select the Delete button.

## Setting Controller User Access

It is possible to configure the enabled PIN code for different functions and features of the controller for a specific user.

1. Select Edit User Group to configure the PIN code for different features for that user.

   The Set Controller User Access window opens up and the top level sections (in a folder format) contain all the features related to it. Select the downward arrow to expand and see all the features available in that section.

   Read access is by default assigned to all users for all the features and programs.

2. Select the check box under the Create & Delete column, against the features for which access needs to be provided for the user.

   Create & Delete provides full write access to the user.

   If you select the check box against the top folder, all the features in that folder also get selected. To de-select a specific feature, expand and clear the check box . If all the features in a folder are not selected then the Check box displays a Dash (-) instead of an X mark.

3. Select Save.

4. Push changes on the controller to enable the PIN configurations.

If a new user with different permissions is added in the controller GUI, then the new user is also visible in the Pin codes dialog window. Select Edit User Group in order to see or modify the access rights for that user.

# Accessing the Controller When Locked By PIN

When accessing the controller with PIN enabled, a prompt asking for the PIN will appear. This is the case whether the controller is accessed via the web GUI, or the controller GUI.

# PIN Code for Station Setup

For a station set up application, if a PIN is enabled on a controller, then it is required to enter the PIN code when accessing the ToolsTalk 2 software for that controller. A dialog window requesting a PIN code is displayed when the user tries to access a controller which has a PIN enabled.

- Enter the PIN in the Enter PIN (Controller PIN) dialog window.

Once the PIN is authenticated, the user can access all the enabled configurations. But if you log off from the current session, it is required to enter the PIN again.

# Tool service alarms

The settings menu contains a tool section, which is used to select tool alarms for Service indicator alarm and Show calibration alarm

To set tool alarms:

1. Select a controller in the Plant structure .

2. Go to Settings .

   The workspace area displays the Settings menus.

Tool alarm parameters
Parameter | Description | Default | Location
--- | --- | --- | ---
Service indicator alarm | Selected in a switch. Turn the alarm On or Off. The alarm is triggered when the service interval is reached. | Off |
Show calibration alarm | Selected in a switch. Triggers the calibration alarm if the tool has not been calibrated within the specified time. Last calibration date can be seen in the Tool menu. Default interval is one year but can be changed from the controller GUI or web GUI. | Off |

# Server Connections

# Controller Communication with the License Server

Functionality can be added temporarily or permanently to a controller through the Functionality Management System. The added functionality is managed by a license server. It can be accessed through the controller GUI, the web GUI, or the ToolsTalk 2 GUI.

The address to the server must be configured, this is done in the controller Settings .

To set the communication between the controller and the license server:

1. Select a controller in the Plant structure .

2. Go to theSettings tab.

   The workspace area displays the Settings menus.

3. In the License Server menu, enable or disable the communication by setting the switch to the desired position.

4. If the communication is enabled, set the Server host address.

5. If the communication is enabled, set the Server port number.

6. Click the Sync button to synchronize the functionality management between the controller and the license server.

License server parameters
Parameter | Description | Default | Comment
--- | --- | --- | ---
License server enabled | Enables or disables communication to the license server. | Off |
Server host | The IP address of the server. |  |
Server port | Port number of the server. |  |
Sync | Command button. Synchronizes the licenses with the license server. |  | Visible when the communication is enabled.

The Sync command forces a synchronization between the controller and the license server. Synchronization shall normally occur automatically on a regular basis if the controller is in normal communication with the server. The command button may be used if synchronization has not been performed on a regular basis.

Relevant Information

- Pushing Configurations to a Controller

# Controller Communication with the ToolsNet Server

A controller always sends tightening results to ToolsTalk 2. A controller can also send the results to ToolsNet 8 for further processing. The address to the ToolsNet 8 server must be configured in the controller.

To set the communication between the controller and the ToolsNet server:

1. Select a controller in the Plant structure .

2. Go to Settings .

   The workspace area displays the Settings menus.

3. Go to ToolsNet, enable or disable the communication with the ToolsNet server.

4. If the communication is enabled, set the IP address and port number of the server.

License server parameters
Parameter | Description | Default | Comment
--- | --- | --- | ---
ToolsNet enabled | Enables/Disables communication to the server. | Off |
Server host | ToolsNet server IP address. |  | Communication enabled.
Server port | ToolsNet server port. |  | Communication enabled.

Relevant Information

- Pushing Configurations to a Controller

# Configuring the Remote Logging Connection

To connect a controller to a remote logging server, configure and activate the remote logging settings on the controller:

1. Select a controller in the Plant structure .

2. Go to Settings .

   The workspace area displays the Settings menus.

3. On the Remote Logging section, configure the following parameters:

   Field | Description
   --- | ---
   On/Off | Enables/Disables communication with the remote logging server
   Protocol | Selects TCP or UDP protocol
   Server host | Remote logging server IP address
   Server port | Remote logging server port

4. Select the applicable log level(s) for each facility:

   Log level | SysLog classification
   --- | ---
   Error | Alert, Critical, Emergency, Error
   Warning | Warning
   Info | Informational, Notice

5. Select Set to apply the configurations on the controller.

# Controller Date and Time

Each controller must have the date and time programmed for accurate reporting.

1. Select a controller in the Plant structure workspace .

2. Go to the Settings tab.

   The workspace area displays the General settings menus.

3. Select the source for the time reference.

4. Enter additional parameters, depending on the selected time source.

5. Select the controller's local time zone from the Time zone shortcut menu.

To achieve best time accuracy and stability it is recommended to use the NTP server that can communicate with all controllers.

The time source is selected from a shortcut menu, and can be one of the following:

- Manually enter time and date into the controller. This can be done through all GUI interfaces.

- Using the standardized Network Time Protocol (NTP). A server distributes time references to connected controllers. It is possible to configure up to two different NTP servers.

- Using the ToolsNet server as the time reference, if the controller is connected and online to the ToolsNet server. When using ToolsNet as the time reference it is important that the server and the controller are set to the same time zone, even if they are in separate time zones.

To add and configure Date and time:

Controller time setting
Parameter | Condition | Description
--- | --- | ---
Source |  | The selection is made from a shortcut menu. Select the method to configure a controller time and date.
Time zone |  | The selection is made from a shortcut menu. Select the time zone in which the controller is located.
Time | Source = Manual | Enter a time in the format Hours:Minutes:Seconds.
Date | Source = Manual | Enter a date from the calendar symbol.
SET command button | Source = Manual | Sends the entered date and time to the controller. To be able to execute this command, the controller must be online.
ADD command button | Source = NTP | Add an additional NTP server address.
DELETE command button | Source = NTP | Delete the selected NTP server address.
NTP server | Source = NTP | Enter the IP address of the NTP server.

# Events Menu

Events are operational states and other pieces of information, for example errors, reported to the operator. All events can be configured and have different severity.

Event type | Function
--- | ---
Display | Events can be informative and are displayed for a short duration of time on the controller screen.
Log | Events can be informative and are displayed for a short duration of time on the controller screen and are also written to the log file. These will be displayed in the Events tab.
Acknowledge | Events that must be acknowledged by the operator. To acknowledge an event, the operator must press a button on an accessory, tap the controller touch screen or acknowledge the event through the web-GUI.

The event configuration determines how every event signals is treated.

Controller settings - events

A | Events search window | B | Events list

All available events are listed in the chapter References. Events have two categories:

- Standard events are defined by Atlas Copco and are available in every deliverable.

- Custom events are implemented by Atlas Copco on customer request and are only valid and available for specific customers.

Relevant Information

- Pushing Configurations to a Controller

In this Section

- Event Configuration
- Adding Events to the Library

# Event Configuration

Configuring event handling:

1. Select a controller in the Plant structure workspace .

2. Go to the Settings tab and select Events.

3. Search for a specific event using the search window or expand the sections by selecting them and scrolling through the Events to find the desired event codes.

4. Select or deselect one or more of the following:

   - Acknowledge, if the event is to be displayed and acknowledged by the operator.

   - Log, if the event is to be displayed, written to the log file and shown in the Events tab.

   - Display, if the event is to be displayed on a screen.

   The Details field can be used to add comments.

5. When ready, push the changes to the specific controller.

6. Repeat steps 3 - 5 for every controller that shall be configured.

Event code numbers 0000-7999 are standard events.

Event code numbers 8000-9999 are customer-specific events.

Relevant Information

- Adding Events to the Library
- Pushing Configurations to a Controller

# Adding Events to the Library

1. Select Settings , then in the Events configuration tab select Manage. Choose Add to Library from the drop-down list.

2. The Create global configuration dialog window opens containing two configuration options:

   - Auto revert, set as default.

   - Unlink

3. Select Create, the event configuration is now locked and visible in the Global Event Library.

Updating global events through the GUI
Action | Result
--- | ---
Auto revert | Updating the events through the controller GUI or the web GUI are ignored, if the program is marked as a global event in ToolsTalk 2. The update is made and sent back to ToolsTalk 2 where the change is recognized but not acknowledged. The original global event program is then immediately pushed back to the controller.
Unlink | Updating the events through the controller GUI or the web GUI causes the program to change from a global event to a local event, in the affected controller. The update is made and sent to ToolsTalk 2 where the change is recognized. As a result the event is immediately removed from the distribution list to the controller.

The selection of auto revert or unlink must be made when a global event is configured for distribution to a controller. The selection cannot be changed at a later stage.

# Extended Logging

Logs can be automatically created and stored. These logs can be configured to include extended logging using log groups.

The default setting for a log group is off. To enable a log group:

1. Select a controller in the Plant structure .

2. Go to Settings and select Extended Logging tab.

3. On the Log Groups window, select the group(s) that you want to enable.

4. Select SET.

## Reset Log Groups

It is possible to reset all log groups to their default settings.

1. Select a controller in the Plant structure .

2. Go to Settings and select Extended Logging tab.

3. On the Reset Log Groups window, select Reset.

## Persistent Log Groups

The log groups resets to their default setting at every reboot. To prevent resetting use persistent log groups.

1. Select a controller in the Plant structure .

2. Go to Settings and select Extended Logging tab.

3. On the Keep Selection after Restart window, set Persistent to ON.

# Working with Fieldbus, SoftPLC and Acyclic Data Tab

The Fieldbus, Acyclic and SoftPLC are located in the Fieldbus and SoftPLC tab, when a single controller has been selected in the Plant structure .

A fieldbus is a communication link between a factory management system (fieldbus master) and a remote node (fieldbus subordinate).

The Fieldbus and SoftPLC is divided into four sections:

- Overview

- Fieldbus

- SoftPLC

- Acyclic

In this Section

- Fieldbus Overview
- Overview Configuration Tab
- Fieldbus Configuration Tab
- Working with Acyclic Fieldbus Configuration
- SoftPLC Configuration Tab
- Controller Fieldbus

# Fieldbus Overview

A typical factory management control system that uses fieldbus communication can look like the figure below when it communicates with a controller.

Fieldbus communication system

A | Fieldbus master (PLC) | B | Frame header
C | User data to and from several virtual stations inside the Process Data Frame | D | Virtual station
E | Controller vith multiple virtual stations |  |

A fieldbus master, normally a PLC, exchanges information with a number of remote nodes which are called fieldbus subordinates. The master communicates with one subordinate at a time. The master transmits a frame to the subordinate and receives another frame in response.

The PLC transmits data to a anybus module which then communicates to the controller that may contain identification data, task selection information and other signals.

A controller sends responses to the PLC through the anybus module that may contain event signals, status signals, tightening results and other signals.

The update frequencies of the process data may differ. The update frequency between the controller and the anybus module is around 100Hz and the update frequency between the anybus module and the PLC is around 500Hz.

The physical transmission link depends on the selected fieldbus type. A transmission consists of a Frame Header, containing address information, and a Process Data Frame, which contains all the data.

If the controller supports virtual stations, it is important to direct the correct information to each virtual station. The Process Data Frame may contain one or more Fieldbus maps, one for each virtual station.

In this Section

- Fieldbus Configuration Parameters
- Fieldbus Definitions
- Fieldbus Data Types
- Fieldbus Sizes

# Fieldbus Configuration Parameters

An item is placed into the Fieldbus Map by defining the position of the least significant bit. This position is identified by a byte number and a bit number.

Item position
Information | Description
--- | ---
Starting byte | The byte number in which the least significant byte of the item is located. A numeric number in the range from zero to size minus one. The numbering starts from zero (0). The least significant byte or bit is number 0.
Starting bit | The bit number in which the least significant bit of the item is located. Starting from the previous selected starting byte. A numeric number in the range from zero to seven. The numbering starts from zero (0). The least significant byte or bit is number 0.
Length | A numeric value representing the number of bits in the item.
Range | Information only. Provides information of minimum length, the maximum length and the default length of the selected item.
Converter | A drop-down list of available signal converters. This is used if the SoftPLC has any requirements on how items are represented in a digital format.

The item converters are used to convert items between different data types.

Item converters
Information | Description
--- | ---
Boolean inversion | Inverts the digital signal from active high (1) to active low (0).
Fixed-point |

# Fieldbus Definitions

An Item is a digital signal. It can for example be signals, as they are described in the controller reference section:

- A single bit of information, like Tightening OK.

- Several bits of information, like an Event code.

An Item can be several bits of information representing a counter value, an identification number or a tightening result.

An Item can be a string of characters.

Fieldbus items
Information | Description
--- | ---
Fieldbus Item | Boolean: The signal can be a simple boolean expression, occupying one single bit position. Examples are digital IO signals.
Integer: The data occupies one or more bits of data in the array.
Character or string: The signal can be a alphanumeric character string, occupying one or several byte positions.

Fieldbus definitions
Information | Description
--- | ---
Fieldbus Map | An array of data. The Size must be an even number of bytes. The fieldbus map is created in the Fieldbus window in the Fieldbus menu. Fieldbus items are placed in the fieldbus map to create a unique array for the master-subordinate communication. Items are placed into the array by defining the starting position and the length, expressed in number of bits.
Process Data Frame | An array of data. The size must be an even number of bytes. The Process Data Frame is created in the Fieldbus window in the Fieldbus menu. Fieldbus maps are placed into the Process Data Frame when they are assigned to a Virtual Station. The position of the map within the frame is defined by the Offset, which is calculated from the beginning of the frame.
Fieldbus Configuration | Fieldbus mapping configurations are done in the Fieldbus window in the Fieldbus menu. Configuration parameters consist of both common parameters and type specific parameters. A list of parameter entry boxes are displayed after the fieldbus type has been selected.

Filedbus item positions
Information | Description
--- | ---
Offset | A pointer variable. The signal can be a simple boolean expression, occupying one single bit position. Examples are digital IO signals.
Starting Byte | A pointer variable. Points to a byte within the fieldbus map that contains the LSB of an item.
Starting Bit | A pointer variable. Points to a bit in the previously defined byte within the fieldbus map that contains the LSB of an item.
Item Length | A size variable expressed in a number of bits.
LSB | Least Significant Bit or Byte.

Name | Description
--- | ---
Fieldbus Transmission | A datagram sent over the network. The transmitting node combines a Frame Header, containing address information, with a Process Data Frame that is sent to the network. The receiving node detects its address in the Frame Header and retrieves the Process Data Frame.
Frame Header | Network address information and other data to ensure an error free transmission over the network
Fieldbus Master | Typically a PLC that initiates the communication to a fieldbus subordinate. The master transmits a data frame and receives another frame from the subordinate.
Fieldbus Subordinate | A remote node responding to a transmission from a fieldbus master. When the subordinate detects a transmission, it receives a frame and responds by sending another frame in return to the sender.

# Fieldbus Data Types

Each fieldbus has its own capacity regarding the amount of data it could transfer over the bus.

- Cyclic data: Cyclic data (also called as "implicit" or "essential" data) is typically PLC data/process data such as Start, Stop, OK, NOK signals and so on. Cyclic data transfers occur on a regular basis (for example, 100ms) between the master and the controller fieldbus and must be updated as often as possible as it contains commands that are crucial to the operation.

- Acyclic data: Acyclic data (also called as "information") is usually tightening data. Acylic data is outside the cyclic data fieldbus mapping and an acyclic data transfer occurs only on a request from the master to the controller fieldbus.

- Async data: Async data is tightening data that is part of the cyclic data transfer and is part of the mapping and is meant to be for those fieldbus types that do not support acyclic data (CC Link). The async data function can be used in order to send the tightening results with cyclic data in packages over the fieldbus to the PLC. The PLC then merges all the packages into one tightening result. The async data from the controller is communicated with the I/O signal Fieldbus AsyncData from PF and the async data is communicated to the controller with the I/O signal Fieldbus AsyncData to PF. These signals are used for the async data handshake which is the same type of handshake done with acyclic data. The size of the Fieldbus AsyncData from PF can be considered as the instance size or record size and indicates how many bytes of data is transferred for each async data handshake request.

  For example, if the total acyclic data configuration is 1024 bytes and Fieldbus AsyncData to PF is set as 64 bytes, then the total async data will be sent 16 times X 64 bytes each time. That is, for each request from the PLC, the controller fills theFieldbus AsyncData to PF with the next 64 bytes of data from the total async data.

  In theory, if you define Fieldbus AsyncData from PF as 2 bytes long, then you can send upto 32K bytes of data (which will need 16K data requests).

Relevant Information

- Fieldbus Sizes

# Fieldbus Sizes

Item | DeviceNet M30a | DeviceNet M40b | Ethernet/IP M30 | Ethernet/IP M40 | Profinet I/O M30 | Profinet I/O M40c | Profibus DP-V1 M30d | Profibus DP-V1 M40 | CC Link M30 | CCLink M40 | CCLink IE M40
--- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | ---
a Values in this column are only applicable for StepSync and Flex. b Values in this column are only applicable for Power Focus 8. c Values in parentheses are only applicable when PF6 FlexSystem is used with Profinet I/O M40. d Only for Profibus DP-V1: the transfer speed for acyclic data is ~1 kB/s, depending on how often you trigger tightenings. This is the bottleneck for how much acyclic data one can transfer. For example, if a tightening is performed every 3 seconds, you should not try to transfer more than 3 kB/tightening.
Max. cyclic data (Read + Write) | 512 | 1024 | 512 | 512*/2896** | 512 | (508)*/2852 | 368 | 488 | 512 | 736 | 512*/2840**
Min. cyclic data (Read + Write) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0
Max. cyclic data (Write) | 256 | 512 | 256 | 256*/1448** | 256 | (254)*/1426** | 244 | 244 | 256 | 368 | 256*/1420**
Min. cyclic data (Write) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0
Max. cyclic data (Read) | 256 | 512 | 256 | 256*/1448** | 256 | (254)*/1426** | 244 | 244 | 256 | 368 | 256*/1420**
Min. cyclic data (Read) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0
Max. acyclic data (Read + Write) | 65535 | 65535 | 65535 | 65535 | 65535 | 65535 | 65535 | 65535 | N/A | N/A | 65535
Min. acyclic data (Read + Write) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | N/A | N/A | 65535
Max. acyclic data (Write) | 65535 | 65535 | 65535 | 65535 | 65535 | 65535 | 65535 | 65535 | N/A | N/A | 65535
Min. acyclic data (Write) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | N/A | N/A | 0
Max. acyclic data (Read) | 65535 | 65535 | 65535 | 65535 | 65535 | 65535 | 65535 | 65535 | N/A | N/A | 65535
Min. acyclic data (Read) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | N/A | N/A | 0

* Max value for PF6 FlexSystem

** Max value for PF8 StepSync

## CC Link Version 1

Occupied stations | Bit points (bits) | Word points (words) | Total (Bit + Word, in bytes)
--- | --- | --- | ---
1 | 32 | 4 | 12
2 | 64 | 8 | 24
3 | 96 | 12 | 36
4 | 128 | 16 | 48

## CC link version 2

Occupied stations | 1 Extension cycle | 2 Extension cycles | 4 Extension cycles | 8 Extension cycles
Points | Total | Points | Total | Points | Total | Points | Points
1 | 32 bits | 12 bytes | 32 bits | 20 bytes | 64 bits | 40 bytes | 128 bits | 80 bytes
4 words | 8 words | 16 words | 32 words
2 | 64 bits | 24 bytes | 96 bits | 44 bytes | 192 bits | 88 bytes | 384 bits | 176 bytes
8 words | 16 words | 32 words | 64 words
3 | 96 bits | 36 bytes | 160 bits | 68 bytes | 320 bits | 136 bytes | 640 bits | 272 bytes
12 words | 24 words | 48 words | 96 words
4 | 128 bits | 48 bytes | 224 bits | 92 bytes | 448 bits | 184 bytes | 896 bits | 368 bytes
16 words | 32 words | 64 words | 128 words

# Overview Configuration Tab

# Fieldbus settings

The Connection status can show the following status messages:

Status | Description
--- | ---
Fieldbus_Online | The fieldbus module is online. The communication between the controller and the fieldbus master is active.
Fieldbus_Offline | The fieldbus module is offline. The communication between the controller and the fieldbus master is not active.
Fieldbus_NoModuleInstalled | No fieldbus module is detected in the controller.
Fieldbus_NotConfigured | A fieldbus module is detected in the controller but the module is not configured.
Fieldbus_Initializing | A fieldbus status during reset or as a result when global parameters have been changed. This is a temporary status until a steady status is displayed.

The fieldbus status can also show errors:

Error Code | Description | Action
--- | --- | ---
Fieldbus_ModuleMismatch | Supported module. Parameter mismatch detected. | Contact Atlas Copco to read error log.
Fieldbus_UnsupportedModuleInstalled | Unsupported fieldbus module. | Contact Atlas Copco to read error log.
Fieldbus_ConfiguredModuleNot Installed | Configuration data created. No module detected. | Contact Atlas Copco to read error log.
Fieldbus_Unexpectedconfigurationerror | Mismatch between controller and ToolsTalk 2. | Contact Atlas Copco to read error log.

Changing some global parameters like frame size, fieldbus module address, will cause the fieldbus module to reset.

1. Select a controller in the Plant structure workspace .

2. Select Fieldbus in the Home screen then select the Overview sub-tab.

3. In Fieldbus settings select Fieldbus type from the drop-down menu.

4. Enter the size in bytes of the entire Frame size for both the receive and transmit direction. The value must be an even integer number.

5. Enter the fieldbus type specific parameters.

Relevant Information

- Pushing Configurations to a Controller

In this Section

- Fieldbus Parameters General
- Fieldbus parameters for DeviceNet
- Fieldbus parameters for EtherNet/IP and EtherNet/IP M40
- Fieldbus parameters for ProfinetIO
- Fieldbus parameters for Profibus
- Fieldbus parameters for CC Link
- Fieldbus parameters for CC Link IE
- Acyclic Data in General Fieldbus Settings

# Fieldbus Parameters General

Field | Description | Default value
--- | --- | ---
Fieldbus type | Select the fieldbus type from drop-down menu: DeviceNet EtherNet/IP ProfinetIO Profibus CC Link CC Link IE EtherNet/IP M40 | Undefined
Update interval | Set how often a Process Data Frame should be sent. The value is expressed in milliseconds. Minimum value is 100 ms. |
Lock tool when fieldbus offline | Selection switch On-Off. Determines the action taken by the controller if the fieldbus module loses communication with the fieldbus master (PLC). | Off
Read result handshake | Selection switch On-Off. When turned On, the setting will affect all virtual stations. The signal Read Result Handshake has to be mapped in the fieldbus configuration. Any results produced when there are no results to acknowledge will immediately be sent to the PLC. Results to acknowledge will be put in a queue and when acknowledged it will be cleared and the next result in the queue is sent. The time between the cleared result and the next result in the queue is dependent on the cycle time for the fieldbus set in the general fieldbus settings. If the setting is changed, or if the fieldbus mapping for the virtual station is changed, the results still in the queue will be flushed and not sent to the PLC. | Off
Set by network | Selection switch On-Off. Determines how the fieldbus module communication is configured. On: Communication parameters set automatically in the fieldbus module. Parameters are determined by the network during the initial connection with the far end station. Off: Communication parameters must be entered during the configuration. | Off
Sync on task selected |  | Off
Byte order Cyclic Data | Select which order of bytes is used for the cyclic data: Set by network Intel (little) Motorola (big) | Set by network
Byte order Acyclic Data | Select which order of bytes is used for the acyclic data: Intel (little) Motorola (big) | Motorola (big)
Load async data automatically | Selection switch On-Off. When turned On, the first and only package of the async data is automatically loaded. When enable this function, the fieldbus master must ensure that it is done reading data before starting a new cycle. | Off
To controller | Total receive Process Data Frame. The frame size is a combination of all the virtual station receive frames. The size is expressed in number of bytes. |
From controller | Total transmit Process Data Frame. The frame size is a combination of all the virtual station transmit frames. The size is expressed in number of bytes. |

In this Section

- Configuring tightening results without handshake protocol

# Configuring tightening results without handshake protocol

1. Configure an acyclic configuration with final angle and final torque for each spindle.

2. Configure a fieldbus configuration with the signal Fieldbus AsyncData From controller (In the tab From controller).

3. Map both the fieldbus configuration and the acyclic configuration to a Virtual Station.

4. In the general fieldbus configuration, choose Load async data automatically = On.

5. After a tightening, the user can get results in the signal Fieldbus AsyncData From controller.

# Fieldbus parameters for DeviceNet

The table below only lists specific parameters for DeviceNet. For the general parameters, see Fieldbus Parameters General.

Field | Description | Default value
--- | --- | ---
Fieldbus node address |  |
Baud rate | Speed of the communication link. Select speed from the drop-down menu. 125 kbps; 250 kbps; 500 kbps, Automatic. | Automatic
Connection mode | Select the type of communication between the fieldbus master (PLC) and the subordinate controller. Select from a drop-down menu: Polled Bitstrobe Change of state | Polled

Relevant Information

- Fieldbus Parameters General
- Fieldbus Parameters General

# Fieldbus parameters for EtherNet/IP and EtherNet/IP M40

The table below only lists specific parameters for EtherNet/IP. For the general parameters, see Fieldbus Parameters General.

Field | Description | Default value
--- | --- | ---
Fieldbus node IP address | Format is 0.0.0.0 |
Subnet mask | Format is 0.0.0.0 |
Gateway | Format is 0.0.0.0 |

Relevant Information

- Fieldbus Parameters General
- Fieldbus Parameters General

# Fieldbus parameters for ProfinetIO

The table below only lists specific parameters for ProfinetIO. For the general parameters, see Fieldbus Parameters General.

Field | Description | Default value
--- | --- | ---
Device name | Name of the device |
Fieldbus node IP address | Format is 0.0.0.0 |
Subnet mask | Format is 0.0.0.0 |
Gateway | Format is 0.0.0.0 |
Use ProfiSafe |  |
ProfiSafe address |  |
Max ADI size | Not valid for M40. Choose between the different application data instance sizes to be set as a maximum. Data consistency is only guaranteed for data mapped over one single ADI, that is, if the data to be sent is larger, or broken over two ADIs, data consistency cannot be guaranteed. Setting a maximum ADI size, which is equal to the sent data type size and mapped correctly to the total frame size will guarantee data consistency. The maximum data size to use for sending cyclic data, which must match the data size used in the Fieldbus master. Max size ADIs will be used until less than that size remains to map. For example, If Max ADI size is set as 8 bytes, then that will be used for mapping until less than 8 bytes remain, then 4, 2, 1 bytes will be used to transfer the rest of the data. |

The parameter Device name identifies the fieldbus module on the PROFINET and uses the syntax described in RFC 5890.

Relevant Information

- Fieldbus Parameters General
- Fieldbus Parameters General

# Fieldbus parameters for Profibus

The table below only lists specific parameters for Profibus. For the general parameters, see Fieldbus Parameters General.

Field | Description | Default value
--- | --- | ---
Sync on task selected | If enabled the fieldbus frame shall be Re-synced at task changes |
Extended mode | Chooses between the backward compatible152 bytes data mode and the 368 bytes data mode: On: 368 bytes data mode. Off: 152 bytes data mode. |
Fieldbus node address |  |
Max ADI size | Not valid for M40. Choose between the different application data instance sizes to be set as a maximum. Data consistency is only guaranteed for data mapped over one single ADI, that is, if the data to be sent is larger, or broken over two ADIs, data consistency cannot be guaranteed. Setting a maximum ADI size, which is equal to the sent data type size and mapped correctly to the total frame size will guarantee data consistency. The maximum data size to use for sending cyclic data, which must match the data size used in the Fieldbus master. Max size ADIs will be used until less than that size remains to map. For example, If Max ADI size is set as 8 bytes, then that will be used for mapping until less than 8 bytes remain, then 4, 2, 1 bytes will be used to transfer the rest of the data. |

Relevant Information

- Fieldbus Parameters General
- Fieldbus Parameters General

# Fieldbus parameters for CC Link

The table below only lists specific parameters for CC Link. For the general parameters, see Fieldbus Parameters General.

Field | Description | Default value
--- | --- | ---
Baud rate | Speed of the communication link. Select speed from the drop-down menu. 156 kbps; 625 kbps; 2500 kbps; 5 Mbps; 10 Mbps. | 156 kbps
Fieldbus node address | A unique address for each separate unit within the network |
Version | Version 1: By default, the module automatically calculates the required number of Occupied Stations based on the mapped Process Data. Version 2: By implementing the Network Settings in the CC-Link, it is possible to customize the implementation for CC-Link Version 2 and use larger data sizes through Extension Cycles. |
Occupied stations | A parameter setting which is dependent on which Version has been chosen. This is used in combination with the Extension Cycles parameter. |
Extension cycles | Parameter setting used for sending larger data sizes, used in combination with the Version and Occupied Station parameters. |

Relevant Information

- Fieldbus Parameters General
- Fieldbus Parameters General

# Fieldbus parameters for CC Link IE

The table below only lists specific parameters for CC Link IE. For the general parameters, see Fieldbus Parameters General.

Field | Description | Default value
--- | --- | ---
Station number | Each device on the network must be assigned a unique Station Number. |
Network number | The network can be segmented into several parts, each with a unique network number that is used for addressing. |

Relevant Information

- Fieldbus Parameters General
- Fieldbus Parameters General

# Acyclic Data in General Fieldbus Settings

# Adding Data Instance Size

In the Fieldbus Settings, the user can set Data instance size, which is a general value used for size span calculations. An instance defines where should the first byte of the acyclic data be read.

This is possible only for the following Fieldbus types:

- EtherNet IP

- DeviceNet

- Profinet IO

- Profibus

- CC Link IE

1. Select a controller in the Plant structure .

2. Go to Fieldbus and SoftPLC tab.

3. Select the Overview sub-tab.

4. Enter the value in the Data instance size field.

The value for Data instance size defines how big an instance should be. This is general for all instances in the acyclic fieldbus mapping with virtual stations. Default: 64, Maximum: 255 (256 bytes).

The size span calculation for CC link is done automatically.

In this Section

- Deleting an Acyclic Fieldbus Mapping

# Deleting an Acyclic Fieldbus Mapping

1. Select the Acyclic From controller tab in the Virtual Station Mapping Configuration area.

2. Select the check box for the fieldbus mapping that needs to be deleted and select Delete.

# SoftPLC settings

## Size

The inbound and outbound size allotted in the fieldbus for the PLC can be set in the To controller and From controller fields.

If the fieldbus for the PLC is not configured, the framesize will display 0 for both inbound and outbound size.

## Offset

The order between fieldbus maps can be changed manually and the spacing between fieldbus maps can be controlled. Both of these two functions are controlled by the Offset parameter. This value defines the starting position of a fieldbus map in the Process Data Frame array.

In this Section

- Changing the Offset

# Changing the Offset

1. In the To Controller section, type the offset of the fieldbus map within the Process Data Frame.

2. In the From Controller section, type the offset of the fieldbus map within the Process Data Frame.

Validation is done automatically. If the new offset value is accepted, it is shown in black text. If the value is not accepted an error message is shown in red text which provides information about which offset rule that is violated.

The start address must be an even number.

# Virtual Station Mapping Configuration

A virtual station in a controller and the fieldbus master communicate by exchanging a fieldbus map between each other.

One or more fieldbus maps are combined into a Process Data Frame, which is sent on the physical communication link between the controller and the fieldbus master.

Fieldbus Virtual Station Mapping Configuration
Column | Function
--- | ---
Check box | Select or deselect a mapping.
Virtual station | Name of virtual station.
Fieldbus configuration | The fieldbus map.
To/From controller offset | Starting point of the fieldbus map within the Process Data Frame.

Acyclic Virtual Station Mapping Configuration
Column | Function
--- | ---
Check box | Select or deselect a mapping.
Virtual station | Name of virtual station.
Acyclic configuration | The acyclic data map.
Start Instance | First instance number of the acyclic data. Default/minimum instance number: 2048.
End Instance | Last instance number of the acyclic data. Maximum instance number: 65535. The maximum size of the instance varies between the different fieldbus types.
No of Instances | Number of instances that are required to send the acyclic data. For example, if the Data instance size is set as 64 and the Start Instance is 2048 and the End Instance is 2060, then the No of instances are 13 and the maximum size for the acyclic configuration will be 832 bytes . The No of instances are generated automatically based on the Start Instance and End Instance.
Size in Bytes | Maximum size of the acyclic configuration based on the selected Data instance size, Start Instance and the End Instance.

The total size of the acyclic data should not exceed 65536 bytes.

A virtual station can only have one acyclic fieldbus configuration mapped, but an acyclic fieldbus configuration can be mapped to many virtual stations.

Relevant Information

- Pushing Configurations to a Controller

In this Section

- Adding a Fieldbus Mapping
- Adding an Acyclic Fieldbus Mapping
- Viewing a Fieldbus Map assigned to a Virtual Station

# Adding a Fieldbus Mapping

1. Select a controller in the Plant structure .

2. Go to Fieldbus and SoftPLC .

3. Select the Overview tab.

4. Select To controller or From controller and select Add in the Virtual Station Mapping Configuration field to add a fieldbus mapping to or from the controller.

5. Select the FieldBus tab and select the Virtual station and Fieldbus configuration from the drop-down menu.

   The fieldbus signal configuration is created in the Fieldbus sub-tab.

6. Select Add.

The fieldbus mappings are now visible in the Virtual Station Mapping Configuration.

# Adding an Acyclic Fieldbus Mapping

1. Select a controller in the Plant structure .

2. Go to Fieldbus and SoftPLC .

3. Select the Overview tab.

4. Select Acyclic from Controller and select Add in the Virtual Station Mapping Configuration.

5. Select the Acyclic FieldBus tab and select the Virtual station and Acyclic fieldbus configuration from the drop-down menu.

   The acyclic fieldbus configuration is created in the Acyclic sub-tab.

6. Select Add.

The fieldbus mapping is now visible in the Virtual Station Mapping Configuration area under the Acyclic from controller tab.

Fieldbus maps are placed into the Process Data Frame in the order that they are assigned to a virtual station, or at the lowest possible entry point where the Fieldbus map can fit.

In this Section

- Editing Start and End Instances

# Editing Start and End Instances

It is possible to edit start and end instances for the fieldbus mapping.

The start and end instances are the fixed positions that defines where the acyclic fieldbus configuration should start and end. It is important to enter the correct range.

1. Select the Acyclic from controller tab in the Virtual Station Mapping Configuration field.

2. Edit the Start instance and End instance values if required.

   If the correct value is not entered, a warning "The fieldbus frame must fit its content" is displayed.

## Lowest/First Possible Acyclic Data Instance Numbers

Fieldbus | To Controller Instance Number | From Controller Instance Number
--- | --- | ---
Profinet-IO | 32767 | 2048
Profibus-DP | 65025 | 2048
Ethernet/IP | 65535 | 2048
DeviceNet | 65535 | 2048
CC-Link | Not supported | Not supported
CC-Link IE | 65535 | 2048

- After each tightening, the measured values for the configured items are available as acyclic data for the PLC to read from the system. The data is updated with new values after each tightening.

- When the signal Cycle Complete is set to high, the data is ready to be read. The data is valid until the next tightening starts, that is until the input signal Start is sent.

- The PLC issues a series of GET_RECORD commands to collect all the data.

# Viewing a Fieldbus Map assigned to a Virtual Station

To view how a fieldbus map is assigned to a virtual station:

1. Select a controller in the Plant structure workspace .

2. Select the Fieldbus and SoftPLC tab then select the Overview sub-tab.

The Fieldbus Virtual Station Mapping Configuration menu displays a list of fieldbus maps, and to which virtual station they are assigned. The To Controller Offset column points to the address in the Process Data Frame where the fieldbus map starts.

# Fieldbus Configuration Tab

1. Select a controller in the Plant structure window .

2. Select the Fieldbus and SoftPLC tab in the menu bar.

   Select the Fieldbus sub-tab to show the list of maps or to create a new fieldbus map.

Column | Description
--- | ---
| Check box.
Name | Name: Shows the name of the map. The name is identical for both the receive map and the transmit map.
Size to | The size of the receive map to a virtual station. The value must be an even number of bytes.
Size from | The size of the transmit map from a virtual station. The value must be an even number of bytes.
Library link | Linked to global library Yes/No.
Last changed | When were the last changes made, expressed in ToolsTalk 2 time.
Changed by | Who made the last changes.
Controller updated | Controller updated, expressed in controller time.
Controller updated by | Who updated the controller.

In this Section

- Creating, Importing and Deleting a Fieldbus Map
- Creating a Fieldbus Signal Configuration
- Understanding the Fieldbus Configuration and the Fieldbus Map
- Automatic Placement of Fieldbus Maps in the Process Data Frame
- Automatic Placement of Items in the Fieldbus Map
- Editing or Viewing an Item in the Fieldbus Map
- Deleting Items From the Fieldbus Map
- Exporting a Fieldbus Map

# Creating, Importing and Deleting a Fieldbus Map

# Creating a New Fieldbus Map

1. Select a controller in the Plant structure window .

2. Select the Fieldbus and SoftPLC tab in the menu bar.

   Select the Fieldbus sub-tab to show the list of maps.

3. Select Add to create a new fieldbus configuration or double-click to edit an existing one.

   The Create new fieldbus configuration dialog window opens.

4. Select the New tab.

5. Issue the configuration with a name.

6. Enter the Size to controller parameter. This is the receive size of the data frame to a virtual station, expressed in number of bytes. This value must be an even number.

7. Enter the Size from controller parameter. This is the transmit size of the data frame from a virtual station, expressed in number of bytes. This value must be an even number.

   The transmit frame and the receive frame may have different size.

8. Select Add to continue with the configuration by adding items to the setup.

The map size entered can not be larger than the Process Data Frame.

Relevant Information

- Creating a Fieldbus Signal Configuration

# Importing a Fieldbus Map

A previously exported fieldbus map can be reused as a template and be imported to a controller.

1. Select a controller in the Plant structure window .

2. Select the Fieldbus and SoftPLC tab in the menu bar.

   Select the Fieldbus sub-tab to show the list of maps.

3. Select Add.

   The Create new fieldbus configuration dialog window opens.

4. Select the Import tab to reuse a existing map.

5. Select the Open file command button to open a browser window.

6. Select a file. The file type must be a JSON file. (*.json).

7. Select Open. The browser window closes.

8. Select Add to import the file. This action will also close the pop-up window and the list of maps is updated.

# Deleting a Fieldbus Map

1. Select a controller in the Plant structure window .

2. Select the Fieldbus and SoftPLC tab in the menu bar.

   Select the Fieldbus sub-tab to show the list of maps.

3. For each fieldbus map to be deleted, select the check box in the leftmost column in the fieldbus workspace. Select Manage, then Delete from the drop-down list.

The list of maps is updated.

# Creating a Fieldbus Signal Configuration

In this area, you can create a new fieldbus signal configuration from the controller or to the controller.

1. Select a controller in the Plant structure window .

2. Select the Fieldbus and SoftPLC tab in the menu bar.

   Select the Fieldbus sub-tab to show a list of maps.

3. Double-click on the name of a map to view it or select Add to create a new one.

   The workspace shows the configuration menus.

4. Select the To Controller tab or the From Controller tab in Fieldbus configuration menu.

5. Select Add.

   The Create signal configuration dialog window opens.

6. Select the item name in the list to select the item.

7. Set the item starting position by typing the BYTE number in which the least significant BIT is located.

8. Set the item starting position by typing the BIT in which the least significant BIT is located.

9. Set the Length of the item, expressed in number of bits.

10. Select an optional Converter value from the drop-down menu.

11. Select Add.

12. Repeat step 6-11 for every item to be added.

13. Select Close to terminate the adding operation and to close the dialog window.

If the item is not placed manually into the map, ToolsTalk 2 will try to place the item at the lowest possible position. It is possible to later move the item within the map.

In this Section

- Fieldbus Configuration Parameters
- Async Data

# Fieldbus Configuration Parameters

An item is placed into the Fieldbus Map by defining the position of the least significant bit. This position is identified by a byte number and a bit number.

Item position
Information | Description
--- | ---
Starting byte | The byte number in which the least significant byte of the item is located. A numeric number in the range from zero to size minus one. The numbering starts from zero (0). The least significant byte or bit is number 0.
Starting bit | The bit number in which the least significant bit of the item is located. Starting from the previous selected starting byte. A numeric number in the range from zero to seven. The numbering starts from zero (0). The least significant byte or bit is number 0.
Length | A numeric value representing the number of bits in the item.
Range | Information only. Provides information of minimum length, the maximum length and the default length of the selected item.
Converter | A drop-down list of available signal converters. This is used if the SoftPLC has any requirements on how items are represented in a digital format.

The item converters are used to convert items between different data types.

Item converters
Information | Description
--- | ---
Boolean inversion | Inverts the digital signal from active high (1) to active low (0).
Fixed-point |

# Async Data

Async data is used when acyclic data such as tightening results need to be sent over the process data.

If the signals Fieldbus AsyncData to PF and Fieldbus AsyncData from PF are added to a fieldbus map and then mapped to a virtual station, AsyncData is enabled and if an acyclic result configuration is mapped to the same virtual station, then the result is output to AsyncData and not to acyclic data.

Relevant Information

- Creating a Fieldbus Signal Configuration

In this Section

- Tightening Results in Async Data
- Configuring Async Data

# Tightening Results in Async Data

The following section provides an example of communication between the fieldbus master and controller using Async data when the I/O signals Fieldbus AsyncData to PF and Fieldbus AsyncData from PF are used.

1. Fieldbus master receives the signal Cycle Complete when a tightening is completed and the tightening result is ready to be fetched on receiving the signal Cycle Complete after a tightening.

2. Fieldbus master sends the I/O signal 10077 - Fieldbus AsyncData to PF, requesting the first package of result data which is read by the controller.

3. Controller responds with I/O signal 107 - Fieldbus AsyncData from PF with a sub-package of the tightening result.

   The tightening result from the controller may not be bigger than the maximum size of the fieldbus frame.

4. When the fieldbus master finished reading the first package, the command Fieldbus AsyncData to PF is set to zero indicating that the first sub message has been received and read.

5. The controller responds with the an acknowledge message Fieldbus AsyncData from PF that a new sub package tightening result can be requested again.

6. The fieldbus master reads the data frame and if the sequence number is negated, it indicates that the requested sub package is the last in queue.

7. If the fieldbus master requests the tightening results and the queue is empty, then the controller responds with an empty data frame.

# Configuring Async Data

1. Select a controller in the Plant structure window .

2. Select the Fieldbus and SoftPLC tab in the menu bar.

   Select the Fieldbus sub-tab to show a list of maps.

3. Double-click on the name of a map to view it or select Add to create a new one.

   The workspace shows the configuration menus.

4. Select the To Controller tab or the From Controller tab in Fieldbus configuration menu.

5. Select Add.

   The Create signal configuration dialog window opens.

6. Select the Fieldbus AsyncData to PF when the To Controller tab is selected or Fieldbus AsyncData from PF when the From Controller tab is connected.

7. Enter the BYTE number in which the least significant BIT is located.

8. Set the item starting position by typing the BIT in which the least significant BIT is located.

9. Set the Length of the item, expressed in number of bits.

10. Select Close to terminate the adding operation and to close the dialog window.

# Understanding the Fieldbus Configuration and the Fieldbus Map

In the Fieldbus configuration menu it is possible to edit the fieldbus map. Items can be added, deleted or moved inside the map.

The fieldbus map

A | Tabs; selects the receive map or the transmit map | B | The map shown in a graphical presentation of how items are placed
C | The map shown in a table presentation of how items are placed | D | Command buttons to Add or to Delete items from the map
E | Colour coded example of item positions |  |

If a row is selected in the list, the item is highlighted in the list and on the map.

If an item is selected on the map it is highlighted on the map and in the list.

An item can occupy one single bit or extend over several bits. An item position is always described with a starting position of the least significant bit. The starting position points to a byte and bit. The length parameter indicates how long the item stretches from right to left.

Items are added or edited in a pop-up window.

Pop-up window to add or edit items in the fieldbus map

A | Add item or Edit item pop-up window map | B | List of available items
C | Byte position | D | Bit position
E | Item length parameter field | F | Item information field
G | Command buttons |  |

# Automatic Placement of Fieldbus Maps in the Process Data Frame

A Fieldbus map is placed automatically in the Process Data Frame when it is assigned to a virtual station. It is possible to change the order later by editing the Offset position in the Fieldbus virtual station mapping configuraiton menu in the Fieldbus and SoftPLC tab.

The following methods are used:

- A Fieldbus map is placed in the order in which they are assigned to in the Process Data Frame.

- Each map starts with an Offset value from the beginning of the frame.

- A map is placed at the lowest possible location, just above the previous map or with offset zero for the first map.

- If a map is deleted from the Process Data Frame, a gap will be created. When a new map is assigned to a virtual station, the placement rule will try to fill the gap.

- If the map cannot fit in between existing maps, then the next free position in the array is tried.

The offset value may be changed manually in the Settings window. Care must be taken that Fieldbus maps do not overlap.

If ToolsTalk 2 detects any violation to the placement rules, an error indicator will appear beside the offset parameter. This indicates that maps overlap or that the map is outside the boundary. This may be corrected by changing the offset value.

A | Starting position of first Fieldbus map in the Process Data Frame; Offset = zero
B | Starting position of a Fieldbus map in the Process Data Frame; Expressed as an offset from the beginning of the PDF
C | Size of a Fieldbus map
D | Fieldbus map
E | Size of the Process Data Frame
F | Error example; Blue map overlaps starting position of “green” map
G | Map size
H | Starting position of “blue” map
J | Process Data Frame
K | First map in the Process Data Frame; Offset address is zero

# Automatic Placement of Items in the Fieldbus Map

Items are placed automatically in the Fieldbus map. It is possible to change the order later by editing the Fieldbus window.

The following methods are used:

- Items are placed in the order in which they are added to in the Fieldbus map, within the Fieldbus virtual station mapping configuration menu in Fieldbus and SoftPLC .

- An item is placed at the lowest possible location with regards to byte, bit and length position.

- If the item cannot fit in between existing items, the next free position in the array is tried.

- If an item is deleted from the Fieldbus map, a gap will be created. When a new item is added, the placement algorithm will try to fill the gap.

- If ToolsTalk 2 detects any violation of the placement rules. An error indicator will appear and indicate the error location. By placing the mouse cursor over the error indicator, more information about the rule violation is displayed.

# Editing or Viewing an Item in the Fieldbus Map

1. Select a controller in the Plant structure window .

2. Select the Fieldbus and SoftPLC tab in the menu bar.

   Select the Fieldbus sub-tab to show a list of maps.

3. Double-click on the name of the selected map.

   The workspace shows the configuration menus.

4. Select either the To Controller tab, or the From Controller tab in Fieldbus configuration menu.

5. Double-click the item name in the map table in the Fieldbus configuration menu.

   The Edit item dialog window opens.

6. Edit the item starting position by typing the BYTE number in which the least significant BIT is located.

7. Edit the item starting position by typing the BIT in which the least significant BIT is located.

8. Edit the Length of the item, expressed in number of bits.

9. Edit an optional Converter value from the drop-down menu.

10. Select OK to confirm any changes and to close the dialog window.

The Fieldbus configuration menu is updated in both the map and in the table.

# Deleting Items From the Fieldbus Map

1. Select a controller in the Plant structure window .

2. Select the Fieldbus and SoftPLC tab in the menu bar.

   Select the Fieldbus sub-tab to show a list of maps.

3. Double-click on the name of the selected map.

   The workspace shows the configuration menus.

4. Select the To Controller tab or the From Controller tab in Fieldbus configuration menu.

5. For each item to be deleted from the map, select the check box in the leftmost position in the table of items in the Fieldbus configuration menu.

6. Select Delete .

The Fieldbus configuration menu is updated in both the map and in the table.

# Exporting a Fieldbus Map

The Fieldbus map defines how signal items are placed into the communication frame that is used between a virtual station and a remote location. This map can be exported as a template and be imported and reused by another controller.

1. Select a controller in the Plant structure window .

2. Select the Fieldbus and SoftPLC tab in the menu bar.

   Select the Fieldbus sub-tab to show the workspace and a list of maps.

3. In the leftmost column in the fieldbus workspace, select the check box for the fieldbus map to be exported, and then select Manage followed by Export from the drop-down list.

4. Browse to the desired location and select Save.

The map will be saved as a JSON file (*.json). The exported file can be imported to a different controller.

# Working with Acyclic Fieldbus Configuration

Some of the data in a tightening result will be sent as acyclic data. The IO signal cycle_complete, usually indicates that the acyclic data is ready to be fetched by the PLC programmer.

The section below explains how to configure the acyclic data.

In this Section

- Acyclic Data Configuration Overview
- Example of a Tightening Result

# Acyclic Data Configuration Overview

In the acyclic data configuration area, it is possible to add a new acyclic data configuration and once added, the different acyclic data configurations are displayed as a list.

1. Select a controller in the Plant structure .

2. Select the Fieldbus and SoftPLC tab. .

3. Select the Acyclic sub-tab.

The columns contain the following information:

Column | Description
--- | ---
Name | Name of the selectable configuration in virtual station mapping.
Select channel by | Bolt or Channel. This value defines if the Identifier of each result configuration item is bolt or channel..
Data layout | Compact or Fixed.
Last changed | Expressed in ToolsTalk 2 time.
Changed by | Configuration data last changed by <user>.
Controller updated | Expressed in controller time.
Controller updated by | Controller updated by <user>.

In this Section

- Adding a New Acyclic Data Configuration

# Adding a New Acyclic Data Configuration

1. Select a controller in the Plant structure .

2. Go to Fieldbus and SoftPLC tab .

3. Select the Acyclic sub-tab.

4. Select Add and select New in the Create new acyclic data configuration window.

5. Enter the acyclic data configuration name and select Add.

   The Properties sub-tab for the newly created configuration opens.

   A new acyclic data configuration is added in the lowest possible position and the list is updated.

In this Section

- Acyclic Data Configuration Menu
- Configure Acyclic Data

# Acyclic Data Configuration Menu

Double-click on an acyclic data configuration in the Acyclic tab to open the acyclic data configuration menu.

Properties menu:

Parameter name | Description
--- | ---
Name | Name of the selectable configuration in virtual station mapping.
Max size | This value will be manually set until it is mapped to a virtual station. This value makes sure that the configuration fits within the selected instances in mapping. The value is calculated from the required number of instances, according data record size.
First channel or bolt offset | Address of the first channel or bolt offset. This defines the size of the common area.
Bolt or channel template size | Size of the bolt or channel.
Select channel by | Bolt or Channel. This value defines if the Identifier of each result configuration item is bolt or channel.
Data layout | Select between: Compact data layout - If the channel or bolt selected in the acyclic configuration does not exist in the current Sync Mode or system run, then that specific data will not be written on the fieldbus. Instead, the next channel/bolt that is present in the Sync Mode will be written in that space in the fieldbus data and will impact the offsets of all of the following bolts/channels. This only applies to whole bolts/channels and not to individual items or values inside a configured bolt/channel. Fixed data layout - The entire configured acyclic data will be written on the fieldbus regardless of how the current Sync Mode, Tightening Program, or system is configured. If no data can be found for an item, then the Non existing values will be written instead. This can be the case for entire bolts/channels. Reasons as to why there is no data written could be that the bolt does not exist in the current Sync Mode, the channel is inhibited, no restriction/monitor has been chosen in the Tightening Program, or the step selected does not have a restriction/monitor.
Add header | Select the check box to indicate that a header must to be added to the acyclic configuration result. When the checkbox is marked, the offset will be updated with 6 bytes lower or higher, depending on the usage. This is also visible graphically. The header can only be added if there is space available. If items are added in the common area and there is no space for the header, it is disabled. If the Compact data layout is chosen, it is strongly recommended to use the header in order to know the length of the acyclic data payload.
Non existing values | Non existing values for different data types are used if the configuration wants data that is not present in the tightening result or in the multistage configuration. When a new acyclic fieldbus is created, the values will be set automatically from the controller.

# Configure Acyclic Data

The Configure Acyclic Data area displays the visualization of the acyclic configuration set by max size, offset and template size. All configurations are in the byte level.

The acyclic data frame displayed on the left changes when items are added to the common, bolt or channel area.

If the values of offset and template size are zero, the common, bolt or channel area is greyed out and non-editable.

## Data in the Common Area

The common area contains data that is global and is applicable to all the spindles in the same station. The common area data is displayed after the header and before the bolt/channel data.

## Bolt or Channel Data

The data in the bolt or channel area is unique for the selected bolt or channel and the layout for the data in the bolt or channel area depends on the data layout chosen.

In this Section

- Common Area Overview
- Bolt or Channel Area Overview

# Common Area Overview

The first occupied area contains the following items:

- Multiple tightening result

- Batch sequence result

- Result notification

These items are "common" and are not specific to a bolt or a channel and contain the following parameters:

Parameter name | Description
--- | ---
Type | Value type of each item. Example: batch sequence result value, result notification or multiple tightening result value.
Offset | Item position in the byte array with acyclic data frames and is defined in bytes.
Size | Size in bytes. It is possible to configure this manually if the datatype is a string. If the datatype is not a string, the values are set automatically based on the data type.
Data type | Data type values. Example: String, Int8, Int16 and so on.
Name | Item name. Non editable.

Relevant Information

- Acyclic Result Items

In this Section

- Adding Acyclic Result Configuration in Common Area
- Deleting Acyclic Result Configuration from Common Area

# Adding Acyclic Result Configuration in Common Area

1. Select Add in the Common area.

   The Create acyclic result configuration window opens.

2. Select a parameter from the Multiple tightening, Result notification or Batch sequence drop-down menu.

3. Select the Output Data Type, enter the offset value and enter the size if the Output Data Type selected was a string.

4. Select Add and then select Close.

# Deleting Acyclic Result Configuration from Common Area

1. Select the check box for the configuration that needs to be deleted in the Common area.

2. Select Delete.

# Bolt or Channel Area Overview

In the bolt or channel configuration area, it is possible to configure the acyclic data items of the following types for a bolt or a channel:

- MultiStage tightening

- Program monitor

- Program restriction

- Step monitor

- Step restriction

Bolt or channel area properties
Parameter name | Description
--- | ---
Type | Value type of each item. Example: MultiStage tightening, Program monitor, Program restriction, Step monitor or Step restriction.
Offset | Item position in the acyclic data frame and is defined in bytes.
Size | Size in bytes. It is possible to configure this manually if the datatype is a string. If the datatype is not a string, the values are set automatically based on the data type.
Data type | Data type values. Example: String, Int8, Int16 and so on.
Name | Item name. Non editable.
Identifier | Sets the ID of the bolt or channel selected.

Relevant Information

- Acyclic Result Items

In this Section

- Adding Acyclic Result Configuration in the Bolt or Channel Area
- Creating Copies in the Bolt or Channel Area
- Deleting Acyclic Result Configuration from Bolt or Channel Area

# Adding Acyclic Result Configuration in the Bolt or Channel Area

1. Select Add in the bolt or channel area.

   The Create acyclic result configuration window opens.

2. Select a parameter from the Multistep tightening, Program monitor, Program restriction, Step monitor or Step restriction drop-down menu .

3. Select the Output Data Type, enter the offset value, identifier and enter the size if the Output Data Type selected was a string.

   For Step monitor and Step restriction, select the step category and choose between Soft start, Rundown, Start and Final.

   Instead of the step number, indicate which step category results should be displayed.

   If there are several steps with the same step category, you can choose to show the step that is Last executed or Last in program (the step with higher order number) in the Step category chooser drop-down menu.

4. Select Add and then Close.

# Creating Copies in the Bolt or Channel Area

It is possible to add many bolts or channels at once using the Create copy tab in the bolt or channel area.

1. Select the check box of the ID that needs to be copied and select Create copy.

   The Create copy of bolts or channels window opens.

2. Enter the number of copies in the Amount of copies field.

   If there is no space for a copy, then a warning "The amount of copies cannot fit into the remaining space in the current configuration" is displayed.

3. Select Create copy and then select Close.

A list of copies with sequential identifier numbers is now visible. The value of the copied ID is always the number after the largest number already existing. For example, if there are ID's 2, 5 and 6 already existing and ID with value 2 is copied, the value of the new ID will be 7. Double-click on the parameters to change any values.

# Deleting Acyclic Result Configuration from Bolt or Channel Area

1. Select the check box for the ID to delete all the configurations under that ID, or to delete an individual configuration, select the check box next to that configuration in the bolt or channel area.

2. Select Delete.

# Example of a Tightening Result

In this fieldbus map, the tightening result data starts at record number 2048 and each record is 64 bytes. The maximum size of the tightening data, including the header is 646 bytes in order to fit up to 64 channels.

Data | Data Type | Position in Frame | Byte
--- | --- | --- | ---
a The length of the data part and the sequence and length from the header, that is the length of data plus 4 bytes
Status | Integer | Header | 0-1
Sequence | Integer | Header | 2-3
Data lengtha | Integer | Header | 4-5
Bolt number channel 1 | Integer | Data | 6-7
Final torque channel 1 | Real | Data | 8-11
Final angle channel 1 | Real | Data | 12-15
Bolt number channel 2 | Integer | Data | 16-17
Final torque channel 2 | Real | Data | 18-21
Final angle channel 2 ....................................... | Real | Data | 22-25
Bolt number channel 64 | Integer | Data | 636-637
Final torque channel 64 | Real | Data | 638-641
Final angle channel 64 | Real | Data | 642-654

## The Functionality of the Header Fields

Signal | Data Type | Description
--- | --- | ---
Status | Integer | Added for future use, at the moment always 0x8100
Sequence | Integer | Will always be -1
Data Length | Integer | The length of the data and the Sequence and Length from the header, i.e. length of data + 4 bytes

## The Functionality of the Data Fields

Signal | Data Type | Description
--- | --- | ---
Bolt Number Channel X | Integer | Bolt number of the channel according to the configuration in the sync mode used in the tightening. For channels that was not included in the tightening the bolt number will be set to 0
Final Torque Channel X | Real | Final Torque value from the tightening result for the channel. The value is always sent in the unit Nm. For a channel that was not included in the tightening or that did not produced a Final Torque value it will be set to 0x7F820000
Final Angle Channel X | Real | Final Angle value from the tightening result for the channel. The value is always sent in the unit deg. For a channel that was not included in the tightening or that did not produced a Final Torque value it will be set to 0x7F820000

The Final Torque and Final Angle values will be sent a floating point binary32 according to ISO/IEC/IEEE60559:2011. Data is transmitted in network order (Big-endian). If a value cannot be sent the special value 0x7F820000 will be sent. If interpreted as a floating point number, it corresponds to NaN (Not a Number).

The integer values are sent as signed 16 bit integers, i.e. the valid range are -32768 to 32767

For example, if a tightening was made with channel 1 and channel 3 and the following tightening data was produced:

## Channel 1

- Bolt number 1

- Final Torque 10.23 Nm

- Final Angle 341.4°

## Channel 3

- Bolt number 5

- Final Torque 10.32 Nm

- No final angle was produced

The tightening data is sent at instance number 2048 as following:

Byte | Field | Value | Comment
--- | --- | --- | ---
0-1 | Status | 0X8100 | Will always be 0X8100
2-3 | Sequence | -1 | Will always be -1
4-5 | Length | 34 | 34 bytes, data for three channels + length and sequence number
6-7 | Bolt Number Channel 1 | 1 |
8 - 11 | Final Torque Channel 1 | 10.23 | 10.23 Nm
12-15 | Final Angle Channel 1 | 341.4 | 341.4°
16-17 | Bolt Number Channel 2 | 0 | Not included in the tightening
18-21 | Final Torque Channel 2 | 0x7F820000 | No torque value available
22-25 | Final Angle Channel 2 | 0x7F820000 | No angle value available
26-27 | Bolt Number Channel 3 | 5 |
28-31 | Final Torque Channel 3 | 10.32 | 10.32Nm
32-35 | Final Angle Channel 3 | 0x7F820000 | No angle value available

# SoftPLC Configuration Tab

# SoftPLC Overview

The SoftPLC is used to customize the behavior of the controller, sending and receiving fieldbus data, or exchanging I/O signals to and from the external SoftPLC. The external SoftPLC is used for control of machinery on assembly lines. Configuration and programming is done through a third party software called MultiProg, integrated with ToolsTalk 2, though running in a process of its own. The SoftPLC is found in the Fieldbus and SoftPLC tab and is visible for controllers supporting this function either by license and/or capability.

Controller features, such as the Low Reaction Tightening Strategies and controller-wide functions among others, require licenses distributed through the Functionality Management System (FMS). Whereas configuration of features is possible without specific licenses, the assignment and use of those features will require the correct license to be installed on the controller. Please refer to Licenses (FMS) for more detailed information on licenses.

Relevant Information

- Pushing Configurations to a Controller

# Creating SoftPLC Signal Configurations

Interaction between accessories and the SoftPLC is done through exchanging I/O signals.

1. Select Add in the SoftPLC Signal Configurations field to see the list with all supported I/O signals connected to this controller.

2. Clear the irrelevant signals in order to exclude them from the SoftPLC signal configuration (all signals are selected by default).

3. Name the signal configuration list.

The created signal configuration is then available as an option to select from the drop-down list when mapping the signal configurations to the virtual station.

The signals that are not included in a signal configuration (not checked), will still be visible in the SoftPLC configurator Multiprog, but crossed out.

# SoftPLC Virtual Station Mapping Configuration

## Creating a New SoftPLC Mapping

1. Select Add in SoftPLC Virtual Station Mapping Configuration

2. In the Create a New SoftPLC Mapping window, select the required Virtual station and the SoftPLC Signal Configuration from the drop-down menus.

   The same SoftPLC signal configuration can be used for multiple virtual stations.

   Each virtual station can use one SoftPLC signal configuration. When a virtual station is mapped with a particular signal configuration, it is no longer available in the drop-down menu when creating a new SoftPLC mapping. To make it available, delete the existing mapping for that virtual station.

   SoftPLC Index: Connect specific virtual stations on the controller to an ordered index in the SoftPLC environment. For example, if the SoftPLC refers to virtual station 2, this mapping will inform the SoftPLC exactly which virtual station currently is number 2.

   Select Update in the Project Virtual Stations to see any changes you made to a SoftPLC Signal Configuration or SoftPLC Mapping in the SoftPLC project. ToolsTalk 2 will not delete variables in the Multiprog SoftPLC project when updating, and it can only add or modify. Because of this, it is recommended to clear the global variables for Virtual stations or Fieldbus in Multiprog before updating.

## Deleting a SoftPLC Mapping

- Select the virtual station signal configuration mapping by marking the corresponding check box. Select Delete.

# Creating a New SoftPLC Project

1. Create a new SoftPLC Signal Configuration.

2. Assign the SoftPLC Signal Configuration to the virtual station.

3. Select SoftPLC ON in General SoftPLC Settings.

4. Select Create New and the Multiprog opens automatically to a new SoftPLC project.

   This project will use the basic template and this template includes all functions available in Multiprog.

   The created and edited project is continuously saved to the local disc when the project is built and stored in Documents > Mp Temp. At the ToolsTalk 2 SoftPLC startup, when OPEN is selected, the stored data project is uploaded and used if the SoftPLC project has not been saved to the ToolsTalk 2 server.

5. Edit the SoftPLC program in Multiprog and give the project a Name and Description in ToolsTalk 2.

   Add virtual station mappings with I/O signal configurations by selecting Update in the Project Virtual Stations field.

   Add Fieldbus data by selecting Update in the SoftPLC framesize in fieldbus field.

   The fieldbus frame size must be configured to contain a special SoftPLC input/output part to be able to send and receive fieldbus data directly to/from the SoftPLC.

6. Select Save to check in the edited project to the ToolsTalk 2 server.

7. Push the changes to the controller.

## Deleting a SoftPLC Project

Deleting a project

- Select Delete in the Project area. Select Delete again in the dialog window to confirm.

In this Section

- Creating SoftPLC User Data
- Setting Up SoftPLC Communications

# Creating SoftPLC User Data

The integration is implemented so that we have shared memory mapped between the SoftPLC and the OpenProtocol adapter and upto six virtual stations are supported. A virtual station is allotted 100 bytes for the data to the SoftPLC and 100 bytes for the data from the SoftPLC. A total of 600 bytes is mapped in both directions in total.

The SoftPLC can interact with protocol adapters through a dedicated part of the shared memory.

1. Select Add in the General SoftPLC Settings field.

2. In the Create SoftPLC user data window, choose the relevant protocol from the drop-down.

3. Fill in the To SoftPLC and From SoftPLC address fields with 0 for the Start addresses and 599 for the End addresses.

4. Select Add.

   The Global_Variables* section in the Multiprog software will contain the output variables (opOUT_VSX) and input variables (opIN_VSX) for each virtual station with the following addresses.

   Virtual Stations | Open Protocol user Data To SoftPLC | Open Protocol user Data From SoftPLC
   Virtual Station 1 | %MB3.38400 | %MB3.40448
   Virtual Station 2 | %MB3.38500 | %MB3.40548
   Virtual Station 3 | %MB3.38600 | %MB3.40648
   Virtual Station 4 | %MB3.38700 | %MB3.40748
   Virtual Station 5 | %MB3.38800 | %MB3.40848
   Virtual Station 6 | %MB3.38900 | %MB3.40948

   If you are importing or updating a project that does not already have the above addresses set, then it must be manually added in Multiprog.

5. Select SoftPLC ON or OFF.

   - On: If the SoftPLC process is lost the tool will be locked from performing any tightenings.

   - Off: If the SoftPLC process is lost the tool will still be able to perform tightenings.

6. Perform open protocol operations in the controller.

7. Push the changes to the controller.

# Setting Up SoftPLC Communications

1. In the open Protocol Client, subscribe user data with MID0241.

2. Controller accepts the command by sending MID0005 to the Open protocol client.

3. The Open protocol client uses MID0240 to download user data from the controller.

4. Controller accepts the command by sending MID0005 to the Open protocol client.

5. Controller uses MID0242 to send data out to the Open Protocol client.

6. Open protocol client acknowledges with MID0243 that it has received user data.

   Refer to the document "OpenProtocol Appendix for PowerFocus 6000 SW1.5.docx " for further information.

# Importing a SoftPLC Project Template

New SoftPLC projects can be created from an existing project template. The templates will serve as a basic suggestion which can be further adjusted. The selected project template is then copied, as to not overwrite the original project.

1. Select Import Project and select an existing SoftPLC project.

2. Edit SoftPLC project in the Multiprog.

   Add virtual station mappings with I/O signal configurations by selecting Update in Project Virtual stations.

   Add Fieldbus data by selecting Update in SoftPLC framesize in fieldbus.

3. Select Save to check in the edited project to the ToolsTalk 2 server.

4. Push the changes to the controller.

Select Update in Project Virtual Stations and the SoftPLC virtual station mappings are added or updated to the SoftPLC project, if not already included in the project.

# Controller Fieldbus

ToolsTalk 2 version 2.24 introduces Controller Fieldbus, which differs from a Fieldbus in one way: Controller Fieldbus is intended for controller-wide use and is shared by all Virtual Stations in a controller. Controller Fieldbus lets many Virtual Stations use the same incoming signal. This reduces the amount of required bandwidth, when compared with Fieldbus.

Controller Fieldbus provides a built-in signal-mapping feature by using Virtual Fieldbus. The purpose of Virtual Fieldbus is to map individual signal configurations into logical groups of signal configurations. Virtual Fieldbus provides a point from where Virtual Stations are mapped to signal configurations. A signal configuration can be mapped to many Virtual Fieldbuses, which lets Virtual Stations share the same signal configurations.

In this Section

- Prerequisites to Using Controller Fieldbus
- Creating a Controller Fieldbus Configuration
- Creating a Signal Configuration in the Controller Fieldbus
- Creating a Virtual Fieldbus
- Mapping a Signal Configuration to One or More Virtual Fieldbuses
- Mapping a Virtual Station to a Virtual Fieldbus

# Prerequisites to Using Controller Fieldbus

These prerequisites must be fulfilled to use Controller Fieldbus:

- ToolsTalk 2 version 2.24 or later

- Controller software version 3.13 or later

# Creating a Controller Fieldbus Configuration

1. Select a controller in the Plant structure workspace.

2. Select the Fieldbus and SoftPLC tab then select the Controller Fieldbus sub-tab.

3. Select Add.

   The Create new fieldbus configuration window comes into view.

4. Enter a Name for the new Controller Fieldbus configuration.

5. Enter a Size to controller number. This is the receive size of the data frame to a Virtual Station, expressed in the number of bytes. This value must be an even number.

6. Enter a Size from controller number. This is the transmit size of the data frame from a Virtual Station, expressed in the number of bytes. This value must be an even number.

7. Select Add.

A new Controller Fieldbus configuration is created and displayed.

# Creating a Signal Configuration in the Controller Fieldbus

1. Select a controller in the Plant structure workspace.

2. Select the Fieldbus and SoftPLC tab then select the Controller Fieldbus sub-tab.

3. Select the Controller Fieldbus instance.

4. To add a signal configuration to the Controller Fieldbus, select Add...

   The Create signal configuration window comes into view.

5. Select a signal.

6. Enter data for the signal configuration byte, bit, and length.

7. Select Add.

8. Select Close.

A signal configuration is created.

At this step, red exclamation marks appear next to the signal configuration. This is because the signal configuration is not yet mapped to a Virtual Fieldbus.

# Creating a Virtual Fieldbus

1. Select a controller in the Plant structure workspace.

2. Select the Fieldbus and SoftPLC tab then select the Controller Fieldbus sub-tab.

3. Double-click the fieldbus configuration to which you want to add a Virtual Fieldbus.

4. To add a Virtual Fieldbus to the Controller Fieldbus, select Add... in the Virtual Fieldbus section.

   The Create Virtual Fieldbus window comes into view.

5. Enter a name and select Tab on the physical keyboard.

6. Select Add.

7. Select Close.

A Virtual Fieldbus is created.

At this step, a red exclamation mark appears next to the Virtual Fieldbus. This is because signal configurations are not yet mapped to the Virtual Fieldbus.

# Mapping a Signal Configuration to One or More Virtual Fieldbuses

1. Select a controller in the Plant structure workspace.

2. Select the Fieldbus and SoftPLC tab then select the Controller Fieldbus sub-tab.

3. Double-click the fieldbus configuration to which you want to map a signal configuration.

4. In the Controller Fieldbus view, locate a signal configuration in the data frame. Right-click the signal configuration and select Map to Virtual Fieldbus.

   The Map signal to Virtual Fieldbus window comes into view.

5. Select the Virtual Fieldbuses to which the signal configuration will be mapped.

6. Select Map.

   The signal configuration is mapped to one or more Virtual Fieldbuses.

7. Select Close.

In the Controller Fieldbus view, select a Virtual Fieldbus to see the signal configurations that are connected to the Virtual Fieldbus. The signal configurations are displayed in green color.

# Mapping a Virtual Station to a Virtual Fieldbus

Make sure that the fieldbus size is large enough to contain the Controller Fieldbus that you want to use. Configure these settings in the Size section.

To map a Virtual Station to a Virtual Fieldbus, the Virtual Station mapping mode must be set to Many-to-one.

When the Virtual Station mapping mode is changed an eventual existing Virtual Station mapping configuration is deleted. A deleted mapping can not be restored.

1. Select a controller in the Plant structure workspace.

2. Select the Fieldbus and SoftPLC tab then select the Overview sub-tab.

3. In the Virtual Station mapping configuration section, select a Controller Fieldbus configuration.

4. Enter offsets to/from the controller to plan the fieldbus distribution.

   The offset is graphically displayed in the Fieldbus Distribution section.

5. In the Mappings section, select Add...

6. Select a Virtual Station.

7. Select a Virtual Fieldbus.

8. Select Add.

9. Select Close.

The Fieldbus mapping is seen both in the Overview sub-tab and in the Virtual Station tab. Select the Virtual Station tab to verify the mapping in the Fieldbus Mapping section.

# Working with Push Configuration Changes

ToolsTalk 2 contains mirrored data per each controller that is connected to the ToolsTalk 2 server. Data is automatically copied from the controller to ToolsTalk 2 at first connection, at reconnecting or at any configuration made in the controller or in the web interface.

Data from ToolsTalk 2 to the controller is not sent automatically. The operator must push data to the controller for the changes to apply.

A controller that is offline can have its configuration settings or parameter values changed by the ToolsTalk 2 application, the data is then stored and can be pushed later.

If any configuration settings are changed in ToolsTalk 2, the Push indicator appears next to the controller name in the structure listing and also next to the tightening programs that have been changed.

- Configurations can be made in the ToolsTalk 2 interface regardless whether the controller is online or offline.

- Configurations can only be pushed to a controller in online state. If the controller is offline, the command is ignored.

- A push can be made to multiple controllers simultaneously.

- As soon as the Push command is successfully executed, the indicator disappears.

In this Section

- Pushing Configurations to a Controller
- Reverting Controller Configurations

# Pushing Configurations to a Controller

WARNING

Risk of injury

A change in the configuration of the tightening program may cause unexpected torque, rotational direction, or speed in the system(s) where the tightening program is currently in use. This could result in severe bodily injury and/or property damage.

- Check the tightening program configurations after adding a new program or after applying changes to an existing program.

Pushing Configurations to One or More Controllers:

1. There are several different ways to push changes to a controller:

   - Select the Push indicator icon next to the controller name in the controller list.

   - Select the Manage button in the tab menu, then Push changes from the drop-down list.

   - Select the Push Changes button in the upper information bar.

2. After selection, the Controllers to push dialog window appears.

3. There are optional ways to push the configurations:

   A | Select this check box in order to push all configurations at once. This will apply to all controllers in the list.
   B | All configurations for the selected controllers will be pushed. Select controllers by marking the corresponding check box.
   C | Expand the list of configurations for a controller and handpick what configurations to be pushed. The remaining configurations will still be in the list after the selected ones have been pushed.

4. Select the Push command button (D).

5. Select Cancel or close the window to exit.

# Reverting Controller Configurations

Changes made in the ToolsTalk 2 application are automatically saved. The Push symbol , indicates that changes have been made to a controller, but are not yet pushed.

1. Select the Manage button, and then select Revert from the drop-down menu.

2. In the Revert controller warning dialog, select OK to revert the controller configurations, or CANCEL to cancel the reverting process.

The Revert operation removes all configurations stored in ToolsTalk 2 for the selected controller. It will also remove any blocking for the selected controller. Any changes made in the controller or web interface are copied to the database, just as usual.

# Working with the Libraries Tab

The Library tab is located in left side menu bar, it includes global functions and provides the following functionality:

Library functions
Library | Function
--- | ---
| Tightening Program library This library contains all global tightening programs available for the controllers to subscribe to. The global tightening programs may be copied from one controller or created in the library, modified and/or distributed to one or more controllers.
| Sync Mode library The Sync mode configuration library contains sync mode templates that can be used to create and modify sync mode configurations and distribute them to multiple controllers.
| Configurations library This library contains all global configurations available for the controllers to subscribe to. The configurations may be copied from one controller or created in the library, modified and/or distributed to one or more controllers.
| Fieldbus configuration library This library contains all global fieldbus configurations available for the controllers to subscribe to. The fieldbus configurations may be copied from one controller or created in the library, modified and/or distributed to one or more controllers.
| Settings library A library for Event configurations that can be distributed to other controllers. The events can be created here or in the Events section within the Settings and then added to the library. Editing an Event configuration will affect all controllers that subscribe to the configuration.
| Program templates library Create templates for Multistep tightening program. When creating a new multistep program, the template can be inserted (drag-and-drop) and act as a base to build the multistep program on.
| Controller configuration library The controller configuration library contains controller templates that can be used to create and modify controller configurations and distribute them to multiple controllers. The library is also very useful for copying and developing configurations in Station Setup mode without access to a ToolsTalk 2 server installation.

Command buttons in the library workspace
Command | Description
--- | ---
Add | Creates a new tightening program.
Manage | Distribute: Distributes the tightening program to the selected controllers. Any updates to the tightening program will update the distributed copies. Export: Exports a selected tightening program. File format is *.json Export to csv: (not available for mutistep) Exports selected tightening program(s). File format is *.csv Delete: Removes selected tightening program(s) from the list. Send for approval: Approve or Reject tightening in the Program Approval tab. Approve: Approves the tightening directly in this configuration view. Reset to draft: Changes the approval status to Draft.

In this Section

- Libraries - Distribution List
- Tightening Program Library
- Global Configurations Library
- FIeldbus Configuration Library
- Global Settings Library
- Program Templates
- Controller Configuration Library
- Global Sync Mode Library
- Program Approval

# Libraries - Distribution List

The distribution list works like a subscription list. Whenever a change is made to one of the global configurations, the change is propagated to all subscribers. The distribution list manages the subscriptions.

1. Select Library in the left-side menu bar.

2. Select one of the library icons to to view the distribution:

3. Select one or more check boxes in the chosen library section to view the content of the distribution list.

   The distribution list shows all controllers that subscribe to the currently selected configuration.

# Tightening Program Library

# Tightening Program Library Introduction

The combination of a tightening strategy selection and parameter values forms the tightening program, this is named as a tightening program. The tightening program can be either Global or Local.

A Local tightening program is valid for a single controller and a Global tightening program may have several controllers subscribing to the same tightening program.

A controller can subscribe to Global tightening programs. Whenever a change is made to a program, the change propagates to all controllers in ToolsTalk 2 which subscribe to the program.

The Tightening program library manages the global tightening programs and the controllers that subscribe to specific Tightening programs.

Updates to subscribers are made within the ToolsTalk 2 application. All affected controllers will show the Push indicator in the Line structure workspace.

ToolsTalk 2 can distinguish between a local and a global tightening program, although the controller itself has no knowledge of this. Therefore it is important to specify the action in ToolsTalk 2 if a tightening program is changed via either the controller GUI or the web GUI.

WARNING

Risk of injury

A change in configuration to the tightening program may cause unexpected torque, rotational direction, or speed in the system(s) where the tightening program is currently in use. This could result in severe bodily injury and/or property damage.

- Check the tightening program configurations after adding a new program or after applying changes to an existing program.

Relevant Information

- Pushing Configurations to a Controller

# Tightening Program Library Workspace

1. Select Library in the left-side menu bar.

2. Go to Tightening program library .

   The workspace area shows a list of Global tightening programs.

Tightening library overview
Column | Description
--- | ---
Check box | Select a configuration.
Name | Shows the name of the configuration. A Push indicator can be next to the name.
Strategy | The tightening strategy selected for the configuration.
Global | A Yes in the column indicates that this is a global tightening program.
Target | The final target is either expressed in a torque value or in an angle value.
Last changed | When the last changes were made, expressed in ToolsTalk 2 time.
Changed by | Which user made the last changes.
Version | Controller software version that can support the Global tightening program library.
| Not an actual column. The list of configurations can be sorted in rising or falling alphabetical order, numerical order or time order. Click on the table header row to make an arrow visible and click on the arrow to change the current sorting direction. One arrow is shown at a time.
Controller type | Shows which controller type the tightening program is intended for.

Tightening library workspace command buttons
Command | Description
--- | ---
Add | New. Creates a new tightening program. Import. Import a tightening program. File format is *.json
Manage | Distribute. Opens the Distribute Global Configurations dialog window. The selected Global tightening program can be added to the distribution list. Export. Exports a selected tightening program. File format is *.json Export to csv. (not available for mutistep) Exports selected tightening program(s). File format is *.csv Delete. Removes selected tightening program from the list. Import Distributed - In the unlikely event of a ToolsTalk 2 license downgrade, the global distributions are automatically exported. These global distributions can be later imported using the Import Distributed function.

Select one or more Global tightening programs check box to view the distribution list. The distribution list shows all controllers currently subscribing to the selected programs.

If no global tightening programs exist, the work space area is empty. Select Add to create a new tightening program or double-click on an existing program to view or edit parameters.

# Tightening Program Library - Adding a Global Tightening Program

1. Select Library in the left-side menu bar.

2. Go to Tightening Program .

   The workspace area shows a list of Global tightening programs.

3. Select Add. The Create new tightening program dialog window opens.

4. Enter the parameters described in the table below.

5. Select Add in the dialog window. The window closes and the workspace shows the tightening program menus.

Create new Tightening Program parameters
Parameter | Description
--- | ---
Controller type | Select a controller type from the shortcut menu.
Controller software version | Select a controller software version from the shortcut menu.
Name | Issue the global tightening program with a name in the parameter entry field.
Strategy | Select a tightening strategy from the shortcut menu.
Target | Select a target type from the shortcut menu.
Target value | Enter the numeric target value for the final step in the parameter entry field or fields.

WARNING

Risk of injury

A change in configuration to the tightening program may cause unexpected torque, rotational direction, or speed in the system(s) where the tightening program is currently in use. This could result in severe bodily injury and/or property damage.

- Check the tightening program configurations after adding a new program or after applying changes to an existing program.

# Tightening Program Library - Deleting a Global Tightening Program

1. Select Library in the left-side menu bar.

2. Go to Tightening Program .

   The workspace area shows a list of Global tightening programs.

3. For each tightening program to be deleted, select the check box in the leftmost column.

4. Select Manage and then select Delete.

   The global tightening program is removed from library and the list is updated.

The controllers subscribing to the deleted program do not lose the program. A deleted tightening program is removed from the list in the Tightening program library workspace. The tightening program is still present in the list in the Tightening workspace of the controllers that have subscribed to the global tightening program. The visible change is that the tightening program is transformed from being a global tightening program to a local tightening program. (The entry in the column Library link is cleared).

# Tightening Program Library - Distributing Global Tightening Programs

# Tightening program library - Distribution and Update

The global tightening program distribution list is like a subscription list. Whenever a change is made to a global tightening program, the change is propagated to all subscribers. The distribution list manages the subscription.

## Distribution

1. Select Library in the left-side menu bar.

2. Go to Tightening Program .

   The workspace area shows a list of Global tightening programs.

3. Select one or more check box in the Global tightening program library to view the content of the distribution list.

   The distribution list shows all controllers that subscribe to the selected tightening programs.

## Update

When a distributed program is changed, the change is distributed automatically to the plant structure expect for approved programs.

Approved programs must be set to Draft state to be changed. Changes done in a program set to draft is stored in the library but not updated in the plant structure. The change will be distributed to the plant structure when the program is set to approved.

# Tightening Program Library - Adding a Global Program to the Distribution List

1. Select Library in the left-side menu bar.

2. Go to Tightening Program .

   The workspace area shows a list of Global tightening programs.

3. Use the check box to select one or more programs to be added to the distribution list.

4. Select Manage and then select Distribute.

   The Distribute global configurations dialog window opens.

   The left-side column shows the selected Global tightening programs.

   The right side column show a list of controllers that are compatible with the selected programs and can be added to the distribution list.

   It is only possible to distribute between controllers of the same type and same software versions.

5. Use the check box to select one or more controllers in the right-side column.

   If a controller already subscribes to the selected Global tightening programs it will not show up in the right-side column.

6. Optional step: Select the down arrow to open additional configurations.

7. Optional step: Select the action to be taken by ToolsTalk 2 if a global tightening program is changed by the controller GUI or web GUI.

8. Select Add.

   The dialog window is closed.

ToolsTalk 2 can distinguish between a local and a global tightening program, although the controller itself has no knowledge of this. Therefore it is important to specify the action in ToolsTalk 2 if a tightening program is changed via either the controller GUI, or the web GUI. This action is defined in the distribution of a global tightening program in the tightening program library.

# Tightening Program Library - Removing a Global Program Subscription from the Distribution List

The global tightening program distribution list is like a subscription list. Whenever a change is made to a global tightening program, the change is propagated to all subscribers. The distribution list manages the subscription.

Select one Global tightening program check box to view the content of the distribution list. The distribution list shows all controllers subscribing to the selected program.

1. Select a controller in the Plant structure workspace .

2. Go to Tightening program .

   The Tightening program workspace shows a list of tightening programs.

   The entry in the column Library link is marked with Yes for the selected tightening program.

3. Select the check box for the selected tightening program.

4. Select Unlink.

   The entry in the column Library link is cleared for the selected tightening program.

5. Select Library in the left-side menu bar.

6. Go to Tightening program library .

7. Select the check box of the removed tightening program.

   The distribution list is updated and the controller name is removed from the list.

# Tightening Program Library - Updating a Global Tightening Program

1. Select Library in the left-side menu bar.

2. Go to Tightening Program .

   The workspace area shows a list of Global tightening programs.

3. Double-click on the name field, the tightening menus are editable. The changes are auto saved to the tightening program.

A global tightening program can only be edited or updated if the tightening menus are opened via the library path.

WARNING

Risk of injury

A change in configuration to the tightening program may cause unexpected torque, rotational direction, or speed in the system(s) where the tightening program is currently in use. This could result in severe bodily injury and/or property damage.

- Check the tightening program configurations after adding a new program or after applying changes to an existing program.

Updates to subscribers are made within the ToolsTalk 2 application. All affected controllers will show the Push indicator in the Plant structure workspace.

Relevant Information

- Pushing Configurations to a Controller

# Tightening program library - Converting a local tightening program to a global program

It is possible to convert a local tightening program, that has been developed at one controller, to become a global tightening program. This tightening program can then be distributed to selected controllers.

1. Select a controller from the Plant Strucure and select Tigthening Program .

2. Select the check box for the program that is to be added to the Tightening Program library.

3. Select Manage then choose Add to library form the drop-down list. The Create global configuration dialog window opens.

4. Select Create. The program is added to the list in the Tightening Program library .

ToolsTalk 2 can distinguish between a local and global tightening program, although the controller itself has no knowledge of this. Therefore it is important to specify the action in ToolsTalk 2 if a tightening program is changed via either the controller GUI, or the web GUI.

# Tightening Program Library - Copying and Pasting

It is possible to copy and paste tightening programs.

PF8, PF6000, STRW, PFXC, IXB and ToolsControl are considered as hand-held.

PF6 FlexSystem , PF8 Synchronized tightening and PF6000 Synchronized tightening are considered as fixtured.

The following rules apply:

- Programs from the fixtured family can only be pasted to controller types that also are a part of the fixtured family from 3.8 controller version and above.

- PF6000 programs can only be pasted to PF6000, PF8 and ToolsControl.

- PF8 programs can only be pasted to PF8 and ToolsControl.

- Programs for controller types STRW, PFXC, IXB and ToolsControl can only be pasted to the same controller types.

A copy of a tightening program always includes everything as for example attached or associated programs and links.

Examples:

A copy of a tightening program with a loosening program attached > The paste create a tightening program and a loosening program attached.

Copying and pasting

1. Select Library.

2. Select Tightening Program. The workspace area shows all the available programs or sequences.

3. Right-click on a single row or select check boxes for several rows, right click and select Copy.

4. To paste the copy into the library, right-click anywhere in the empty workspace area and select paste. The copy is added to the first available position in the existing list.

   If there is no space in the list for the copy, the whole operation will fail.

# Global Configurations Library

# Configurations library introduction

The configuration can be either Global or Local.

A Local configuration is valid for a single controller and a Global configuration is valid for several selected controllers.

A controller can subscribe to Global configurations. Whenever any changes are made to a configuration it propagates to all controllers in ToolsTalk 2 that subscribe to the configuration.

The Global configurations library manages the global configurations and the controllers that subscribe to the configurations.

ToolsTalk 2 can distinguish between a local and global configuration. The controller itself has no knowing of local or global configurations. Thus it is important to specify the action in ToolsTalk 2 if a device configuration is changed from either the controller GUI or the web GUI.

Relevant Information

- Pushing Configurations to a Controller

# Global Configurations Workspace

1. Select Library in the left-side menu bar.

2. Go to Configurations library .

   The workspace area shows a list of Global configuration.

Configurations library overview
Column | Description
--- | ---
Check box | Select a configuration.
Name | Shows the name of the configuration. A Push indicator can be next to the name.
Type | The configuration type
Last changed | When the last changes were made, expressed in ToolsTalk 2 time.
Changed by | Which user made the last changes.
Version | Controller software version that can support the Global configuration.
| Not an actual column. The list of configurations can be sorted in rising or falling alphabetical order, numerical order or time order. Click on the table header row to make an arrow visible and click on the arrow to change the current sorting direction. One arrow is shown at a time.
Controller type | Shows which controller type the configuration is intended for.

Configurations library workspace command buttons
Command | Description
--- | ---
Add | New. Creates a new configuration. Import. Import a configuration. File format is *.json
Manage | Distribute. Opens the Distribute Global Configurations dialog window. The selected Global configuration can be added to the distribution list. Export. Exports a selected configuration. File format is *.json Delete. Removes selected configuration from the list. Import Distributed - In the unlikely event of a ToolsTalk 2 license downgrade, the global distributions are automatically exported. These global distributions can be later imported using the Import Distributed function.

Select one or more Global configurations check box to view the distribution list. The distribution list shows all controllers currently subscribing to the selected configuration.

If no global configurations exist, the work space area is empty. Select Add to create a new configuration or double-click on an existing configuration to view or edit parameters.

# Global Configurations Library - Creating or Importing a Global Configuration

## Creating a Global Configuration:

1. Select Library in the left-side menu bar.

2. Go to the Configurations library in the upper menu bar in the workspace window.

   The workspace shows a list of Global configurations.

3. Select Add.

   The Create new configuration dialog window is shown.

4. Enter the following parameters:

   - Select Type of configuration to be added, Controller type and Controller software version for the configuration to apply to.

5. Select Add in the shortcut window.

6. The configuration window for selected type of configuration is shown.

The configuration is auto saved to the Configurations library.

## Importing an Already Existing Global Configuration:

1. Select Library in the left-side menu bar.

2. Go to Configurations library .

   The workspace shows a list of Configurations.

3. To add a new configuration to the list, select Add.

   The Create new configuration dialog window is displayed.

4. Select the Import tab.

5. Select Open file.

   A browser window opens for reading the import file.

6. Select the desired import file. The file must be in the format <configuration_name>.json. Select Open.

7. Select Add in the shortcut window.

8. The configuration window for the imported configuration is displayed.

The configuration is auto-saved to the configurations library.

Relevant Information

- Pushing Configurations to a Controller

# Global Configurations Library - Deleting a Global Configuration

1. Select Library in the left-side menu bar.

2. Go to Configuration library .

   The workspace shows a list of Global configurations.

3. For each configuration to be deleted, select the check box in the leftmost column.

4. Select Manage and then select Delete.

   The global configuration is removed from the library and the list is updated.

The controllers subscribing to the deleted configuration do not lose the configuration. A deleted global configuration is removed from the list in the Configuration library workspace. The configuration is still present in the list in the Configurations workspace of the configurations that have subscribed to the global configuration. The visible change is that the configuration is transformed from being a global configuration to a local configuration. (The entry in the column Library link is cleared).

# Global Configurations Library - Creating a Global Configuration From An Existing

1. Select a controller containing the desired configuration in the Plant structure .

2. In the menu bar, go to Configurations .

3. Select one or more configurations to add to the library and click Manage, then select Add to library.

4. The selected local configuration will become a global configuration, stored in the Global configurations library.

   If local changes are made in the controller or web interface, there are two options:

   - Auto revert: Changes in the controller will not apply to the global configuration, the global configurations will still be applied.

   - Unlink: Changes in the controller will apply to the configuration in the controller, and the link to the global configuration will be cut. As a result, the global configuration is immediately removed from the distribution list to the controller.

5. Select Library .

6. In the upper menu bar, Select Global configurations .

   The workspace shows a list of Global configurations and the newly added configuration is now visible in the list.

Relevant Information

- Pushing Configurations to a Controller

# Global Configurations Library - Distributing a Global Configuration

1. Select Library in the left-side menu bar.

2. Go to Configuration library .

   The workspace shows a list of Global configurations.

3. Select the configuration check box . Select Manage and then select Distribute.

   It is only possible to distribute between controllers of the same type and same software versions.

4. Use the check box to select each configuration which is to be included in the distribution.

5. Select one or more controllers in the right-side of the dialog window. Select Add in the dialog window.

   Any updates to the global configuration will update the distributed copies. Changes in the global configuration will apply to the selected controllers.

   If local changes are made in the controller or web GUI, there are two options:

   - Auto revert: Changes in the controller will not apply to the configuration, the global configurations will still be valid.

   - Unlink: Changes in the controller will apply to the configuration and the link to the global configuration will be cut. As a result, the global configuration is immediately removed from the distribution list to the controller.

The changes are auto saved to the global configurations library.

All affected controllers will show the Push indicator in the Plant structure workspace.

Relevant Information

- Pushing Configurations to a Controller

# Global Configurations Library - Editing a Global Configuration

1. Select Library in the left-side menu bar.

2. Select Global library .

   The workspace shows a list of Global configurations.

3. Double-click the configuration to be edited. The configuration window for the selected type of configuration is shown.

The changes are auto saved to the global configurations library.

All affected controllers will show the Push indicator in the Plant structure workspace.

Relevant Information

- Pushing Configurations to a Controller

# Global Configurations Library - Removing a Global Configuration Subscription From the Distribution List

The global configuration distribution list is like a subscription list. Whenever a change is made to a global configuration, the change is propagated to all subscribers. The distribution list manages the subscription.

Select one Global configuration check box to view the content of the distribution list. The distribution list shows all controllers subscribing to the selected configuration.

To remove the subscription of a Global configuration from one controller:

1. Select a controller in the Plant structure workspace .

2. Go to Configurations .

   The Configurations workspace shows a list of tightening programs.

   The entry in the column Library link is marked with Yes for the distributed configuration.

3. Select the check box for the selected tightening program.

4. Select Manage then Unlink from the drop-down menu.

   The entry in the column Library link is cleared for the selected configuration.

5. Select Library in the left-side menu bar.

6. Go to Configurations library .

7. Select the check box of the removed configuration.

   The distribution list is updated and the controller name is removed from the list.

# FIeldbus Configuration Library

The fieldbus configuration can be either Global or Local.

A Local fieldbus configuration is valid for a single controller and a Global fieldbus configuration is valid for several selected controllers.

A controller can subscribe to Global fieldbus configurations. Whenever any changes are made to a configuration it propagates to all controllers in ToolsTalk 2 that subscribe to the configuration.

The Global fieldbus configurations library manages the global fieldbus configurations and the controllers that subscribe to the configurations.

Updates to subscribers are done within the ToolsTalk 2 application. All affected controllers will show the Push indicator in the Line structure workspace.

ToolsTalk 2 can distinguish between a local and global fieldbus configuration, although the controller itself has no knowledge of this. Therefore it is important to specify the action in ToolsTalk 2 if a fieldbus configuration is changed via either the controller GUI, or the web GUI.

Relevant Information

- Pushing Configurations to a Controller

In this Section

- Fieldbus Configuration Workspace
- Fieldbus Configuration Library - Creating or Importing a Global Fieldbus Configuration
- Fieldbus Configuration Library - Deleting a Global Fieldbus Configuration
- Fieldbus Configuration Library - Creating a Global Fieldbus Configuration from an Existing Fieldbus Configuration
- Fieldbus Configuration Library - Distributing a Global Fieldbus Configuration
- Fieldbus Configuration Library - Editing a Global Fieldbus Configuration
- Fieldbus Configuration Library - Exporting a Global Fieldbus Configuration
- Fieldbus Configuration Library - Removing a Fieldbus Configuration Subscription from the Distribution List

# Fieldbus Configuration Workspace

1. Select Library in the left-side menu bar.

2. Go to Fieldbus library .

   The workspace area shows a list of Global Fieldbus configuration.

Fieldbus library overview
Column | Description
--- | ---
Check box | Select a Fieldbus configuration.
Name | Shows the name of the Fieldbus configuration. A Push indicator can be next to the name.
Size to controller | Displays the receive size of the data frame.
Size from controller | Displays the transmit size of the data frame.
Last changed | When the last changes were made, expressed in ToolsTalk 2 time.
Changed by | Which user made the last changes.
Version | Controller software version that can support the Global Fieldbus configuration.
| Not an actual column. The list of configurations can be sorted in rising or falling alphabetical order, numerical order or time order. Click on the table header row to make an arrow visible and click on the arrow to change the current sorting direction. One arrow is shown at a time.
Controller type | Shows which controller type the Fieldbus configuration is intended for.

Fieldbus Configurations library workspace command buttons
Command | Description
--- | ---
Add | New. Creates a new Fieldbus configuration. Import. Import a Fieldbus configuration. File format is *.json
Manage | Distribute. Opens the Distribute Global Configurations dialog window. The selected Global Fieldbus configuration can be added to the distribution list. Export. Exports a selected Fieldbus configuration program. File format is *.json Delete. Removes selected Fieldbus configuration program from the list. Import Distributed - In the unlikely event of a ToolsTalk 2 license downgrade, the global distributions are automatically exported. These global distributions can be later imported using the Import Distributed function.

Select one or more Global Fieldbus configuration check box to view the distribution list. The distribution list shows all controllers currently subscribing to the selected Fieldbus configuration.

If no global Fieldbus configurations exist, the work space area is empty. Select Add to create a new Fieldbus configuration or double-click on an existing configuration to view or edit parameters.

# Fieldbus Configuration Library - Creating or Importing a Global Fieldbus Configuration

## Creating a Fieldbus Configuration:

1. Select Library in the left-side menu bar.

2. Go to Fieldbus library .

   The workspace shows a list of Fieldbus configurations.

3. To add a new fieldbus configuration to the list, select Add.

   The Create new fieldbus configuration dialog window is displayed.

4. Enter the following parameters to add a new fieldbus map:

   - Enter a Name

   - Enter Size to controller and Size from controller

   - Select Controller type and Controller software version for the device, from the shortcut menu.

5. Select Add in the shortcut window.

6. The configuration window for the added fieldbus configuration is displayed.

The fieldbus configuration is auto-saved to the fieldbus library.

## Importing an Already Existing Fieldbus Configuration:

1. Select Library in the left-side menu bar.

2. Go to Fieldbus library .

   The workspace shows a list of Fieldbus configurations.

3. To add a new configuration to the list, select Add.

   The Create new fieldbus configuration dialog window is displayed.

4. Select the Import tab.

5. Select Open file.

   A browser window opens for reading the import file.

6. Select the desired import file. The file must be in the format <fieldbus_configuration_name>.json. Select Open.

7. Select Add in the shortcut window.

8. The configuration window for the added fieldbus configuration is displayed.

The fieldbus configuration is auto-saved to the fieldbus library.

Relevant Information

- Creating a New Fieldbus Map

# Fieldbus Configuration Library - Deleting a Global Fieldbus Configuration

1. Select Library in the left-side menu bar.

2. Go to Fieldbus configuration library .

   The workspace shows a list of Global fieldbus configurations.

3. To delete a fieldbus configuration, select the check box in the leftmost column and then select Delete

   The global fieldbus configuration is removed from library and the list is updated.

The controllers subscribing to the deleted configuration do not lose the configuration. A deleted global fieldbus configuration is removed from the list in the Fieldbus configuration library workspace. The fieldbus configuration is still present in the list in the Fieldbus workspace of the fieldbus that have subscribed to the global fieldbus configuration. The visible change is that the fieldbus configuration is transformed from being a global fieldbus configuration to a local fieldbus configuration. (The entry in the column Library link is cleared).

# Fieldbus Configuration Library - Creating a Global Fieldbus Configuration from an Existing Fieldbus Configuration

1. Select a controller (containing the desired fieldbus configuration) in the Plant structure workspace .

2. Select Fieldbus & SoftPlc in the menu bar.

3. In the Fieldbus menu select one or more fieldbus signal configurations to add to the library. Select Manage then Add to library from the drop-down menu.

   - The Create global configuration dialog window opens. Select Create.

4. The selected local configuration will become a global configuration, stored in the Global Fieldbus configuration library.

   If local changes are made in the controller or web GUI, the two options below are available:

   - Auto revert: Changes in the controller will not apply to the global fieldbus configuration, the global configurations will still be applied.

   - Unlink: Changes in the controller will apply to the fieldbus configuration in the controller, and the link to the global configuration will be cut. As a result, the global fieldbus configuration is immediately removed from the distribution list to the controller.

5. Select Library in the left-side menu bar.

6. Go to Global fieldbus library .

   The workspace shows a list of Global fieldbus configurations and the newly added fieldbus configuration is now visible in the list.

# Fieldbus Configuration Library - Distributing a Global Fieldbus Configuration

1. Select Library in the left-side menu bar.

2. Go to Global fieldbus library .

   The workspace shows a list of Global fieldbus configurations.

3. Select the check box for the fieldbus configuration to distribute. Select Manage then Distribute from the drop-down menu.

   It is only possible to distribute between controllers of the same type and same software versions.

   The Distribute Global Configurations dialog window opens.

4. Select one or more controllers in the right-side of the dialog window. Select Add.

   Any updates to the global configuration will update the distributed copies. Changes in the global configuration will apply to the selected controllers.

   If local changes are made in the controller or web GUI, the two options below are available:

   - Auto revert: Changes in the controller will not apply to the global fieldbus configuration, the global configurations will still be valid.

   - Unlink: Changes in the controller will apply to the fieldbus configuration in the controller, and the link to the global configuration will be cut. As a result, the global configuration is immediately removed from the distribution list to the controller.

The changes are auto saved to the global fieldbus configurations library.

All affected controllers will show the Push indicator in the Plant structure workspace.

Relevant Information

- Pushing Configurations to a Controller

# Fieldbus Configuration Library - Editing a Global Fieldbus Configuration

1. Select Library in the left-side menu bar.

2. Go to Global fieldbus library .

   The workspace shows a list of Global fieldbus configurations.

3. Double-click the fieldbus configuration to edit.

4. The configuration window for the selected fieldbus configuration is shown.

The fieldbus configuration is auto-saved to the global fieldbus configurations library.

All affected controllers will show the Push indicator in the Plant structure workspace.

Relevant Information

- Pushing Configurations to a Controller

# Fieldbus Configuration Library - Exporting a Global Fieldbus Configuration

1. Select Library in the left-side menu bar.

2. Go to Global fieldbus configurations library .

   The workspace shows a list of Global fieldbus configurations.

3. Select the check box of the global fieldbus configuration to be exported.

4. Select Export.

   A browser window opens for saving the export file.

5. The default file name is <configuration>.json Click Save.

# Fieldbus Configuration Library - Removing a Fieldbus Configuration Subscription from the Distribution List

The global Fieldbus configuration distribution list is like a subscription list. Whenever a change is made to a global Fieldbus configuration, the change is propagated to all subscribers. The distribution list manages the subscription.

Select one Global Fieldbus configuration check box to view the content of the distribution list. The distribution list shows all controllers subscribing to the selected configuration.

## Removing the Subscription of a Global Fieldbus Configuration from One Controller

1. Select a controller in the Plant structure workspace .

2. Go to Fieldbus & SoftPlc .

   The Fieldbus workspace shows a list of tightening programs.

   The entry in the column Library link is marked with Yes for the distributed Fieldbus configuration.

3. Select the check box for the selected Fieldbus configuration.

4. Select Manage then Unlink from the drop-down menu.

   The entry in the column Library link is cleared for the selected Fieldbus configuration.

5. Select Library in the left-side menu bar.

6. Go to Fieldbus Configuration library .

7. Select the check box of the removed Fieldbus configuration.

   The distribution list is updated and the controller name is removed from the list.

# Global Settings Library

Parameter | Description
--- | ---
Check box | Select the Event configuration template.
Name | Shows the name of the Event configuration template.
Last changed | Last change, expressed in ToolsTalk 2 time.
Changed by | Last changes made by...
Version | Controller software version that is supported by the Event configuration template.
| Not an actual column. The list of configurations can be sorted in rising or falling alphabetical order, numerical order or time order. Click on the table header row to make an arrow visible and click on the arrow to change the current sorting direction. One arrow is shown at a time.
Controller type | Shows which controller type the Event configuration is intended for.
Customer Key | Default value None when creating new Global Event configuration. Value taken from controller’s Iam.CustomerKey when creating Global event configuration from an existing controller.

## Settings configuration command buttons

Command | Description
--- | ---
Add | New. Creates a new Event configuration template. Import. Import an Event configuration template. File format is *.json
Manage | Distribute. Global Event configurations can be distributed to controllers that have the same CustomerKey. The list of controllers available for distribution will be pre-filtered by controller type + software version + customer key. Export. Exports a selected Event configuration. File format is *.json Delete. Removes selected Event configuration templates from the list. Import Distributed - In the unlikely event of a ToolsTalk 2 license downgrade, the global distributions are automatically exported. These global distributions can be later imported using the Import Distributed function.

If no previous Event configuration templates exist, the work space area will be empty. Select Add to create a new Event configuration template, or double-click on an existing template to view or edit the parameters.

In this Section

- Global Settings Library - Creating or importing a Global Event configuration
- Global Settings Library - Deleting a Global Events configuration
- Global Settings Library - Distributing a Global configuration
- Global Configurations Library - Removing a Global Configuration Subscription From the Distribution List
- Global Settings Library - Editing a Global Event configuration
- Global Settings Library - Exporting a Global Event configuration

# Global Settings Library - Creating or importing a Global Event configuration

## Creating a global Event configuration:

1. Select Library in the left-side menu bar.

2. Select the Settings library tab in the upper menu bar in the workspace window.

   The workspace shows a list of Global Event configurations.

3. Select Add.

   The Create new Event configuration dialog window is shown.

4. Enter the following parameters:

   - Issue the configuration a Name.

   - Select the Controller type from the drop-down list.

   - Select the Controller software version for the configuration.

5. Select Add in the dialog window.

6. The events configuration window is shown. Expand each section to set the specific parameters.

The new configuration is auto saved to the Global Settings Library.

## Importing an already existing global Event configuration:

1. Select Library in the left-side menu bar.

2. Go to Global Settings library .

   The workspace shows a list of Global Event configurations.

3. To add a new configuration to the list, select Add.

   The Create new Event configuration dialog window is displayed.

4. Select the Import tab.

5. Select Open file.

   A browser window opens for reading the import file.

6. Select the desired import file. The file must be in the format <configuration_name>.json. Select Open.

7. Select Add in the shortcut window.

8. The Event configuration window for the imported configuration is displayed.

The configuration is auto-saved to the Event configurations library.

# Global Settings Library - Deleting a Global Events configuration

1. Select Library in the left-side menu bar.

2. Select the Settings library tab in the upper menu bar in the workspace window.

   The workspace shows a list of Global Settings configurations.

3. For each configuration to be deleted, select the check box in the leftmost column.

4. Select Manage, then choose Delete from the drop-down menu.

   The Global Settings configuration is removed from the library and the list is updated.

The controllers subscribing to the deleted configuration do not lose the configuration. A deleted global configuration is removed from the list in the Settings library workspace. The configuration is still present in the list in the Event Configurations workspace of the configurations that have subscribed to the global configuration. The visible change is that the configuration is transformed from being a global Event configuration to a local Event configuration (the Library link under Events in Settings is also cleared).

# Global Settings Library - Distributing a Global configuration

1. Select Library in the left-side menu bar.

2. Select the Settings library tab in the upper menu bar in the workspace window.

   The workspace shows a list of Global Event configurations.

3. Select the check box of the Global Event to be distributed.

4. Select Manage and choose Distribute from the drop-down menu.

   It is only possible to distribute between controllers of the same type and same software versions.

   The Distribute Global configurations dialog window opens.

5. Select the check box of each configuration to be included in the distribution.

   Configurations type can be individually selected. Certain dependencies exist between configurations. When selecting to distribute a Global configuration, additional configurations may also be selected by default.

6. Select one or more controllers in the right side of the dialog window.

7. Select Add in the dialog window.

   The dialog window closes and the controller is added to the list in Distributed to. A new Library link will be added to the Events menu in Settings.

8. The selected configurations are only distributed to the controllers in ToolsTalk 2.

The distribution of new configurations will result in existing configurations being deleted and replaced with the configurations from the Library templates.

# Global Configurations Library - Removing a Global Configuration Subscription From the Distribution List

The global configuration distribution list is like a subscription list. Whenever a change is made to a global configuration, the change is propagated to all subscribers. The distribution list manages the subscription.

Select one Global configuration check box to view the content of the distribution list. The distribution list shows all controllers subscribing to the selected configuration.

To remove the subscription of a Global configuration from one controller:

1. Select a controller in the Plant structure workspace .

2. Go to Configurations .

   The Configurations workspace shows a list of tightening programs.

   The entry in the column Library link is marked with Yes for the distributed configuration.

3. Select the check box for the selected tightening program.

4. Select Manage then Unlink from the drop-down menu.

   The entry in the column Library link is cleared for the selected configuration.

5. Select Library in the left-side menu bar.

6. Go to Configurations library .

7. Select the check box of the removed configuration.

   The distribution list is updated and the controller name is removed from the list.

# Global Settings Library - Editing a Global Event configuration

1. Select Library in the left-side menu bar.

2. Select the Settings library tab in the upper menu bar in the workspace window.

   The workspace shows a list of Global Event configurations.

3. Double-click the configuration to be edited. The configuration window for the selected type of configuration is shown.

The changes are auto saved to the global settings configurations library.

All affected controllers will show the Push indicator in the Plant structure workspace.

# Global Settings Library - Exporting a Global Event configuration

A Global Event template can be exported and then reused (imported) in another ToolsTalk 2 installation or in a ToolsTalk 2 Station Setup installation.

1. Select Library in the left-side menu bar.

2. Select the Settings library tab in the upper menu bar in the workspace window.

   The workspace shows a list of Global Event configurations.

3. Select the check box of the controller template to be exported.

4. Select Export

   A browser window opens for saving the export file.

5. The default file name is <Configuration>.json, select Save.

The exported file can be given any name with the *.json extension.

Inside the exported *.json file the controller template is given the name from the controller column. When a controller template is imported, the name given to the controller template is taken from this field inside the *.json file, regardless of the file name. This means that an imported controller template may have a different name than the imported file name.

To avoid having controller templates with identical names it is advised to give the template a unique name before exporting and not to change the file name.

# Program Templates

Library > Program templates

Create templates for Multistep tightening program. When creating a new multistep program, the template can be used as a base to build the multistep program on.

Click Add to create a new template.

Modify an existing template by double clicking on the template in the Program Template list. Multistep programs based on that template will not be affected since the template is copied, not linked, to the programs.

WARNING

Risk of injury

A change in configuration to the tightening program may cause unexpected torque, rotational direction, or speed in the system(s) where the tightening program is currently in use. This could result in severe bodily injury and/or property damage.

- Check the tightening program configurations after adding a new program or after applying changes to an existing program.

Relevant Information

- Multistep Template
- Multistep Tightening Strategy

In this Section

- Program Templates Workspace
- Importing a Tightening Program Template

# Program Templates Workspace

1. Select Library in the left-side menu bar.

2. Go to Program templates library .

   The workspace area shows a list of Global Tightening Program templates.

Program templates overview
Column | Description
--- | ---
Check box | Select a Tightening Program template.
Name | Shows the name of the Tightening Program template. A Push indicator can be next to the name.
Strategy | The tightening strategy selected for the Tightening Program template.
Target | The final target is either expressed in a torque value or in an angle value.
Last changed | When the last changes were made, expressed in ToolsTalk 2 time.
Changed by | Which user made the last changes.
Version | Controller software version that can support the Global Tightening Program template.
| Not an actual column. The list of Tightening Program templates can be sorted in rising or falling alphabetical order, numerical order or time order. Click on the table header row to make an arrow visible and click on the arrow to change the current sorting direction. One arrow is shown at a time.
Controller type | Shows which controller type the Tightening Program template is intended for.

Tightening Program template library workspace command buttons
Command | Description
--- | ---
Add | New. Creates a new Tightening Program template. Import. Import a Tightening Program template. File format is *.json
Manage | Export. Exports a selected Tightening Program template. File format is *.json Delete. Removes selected Tightening Program template from the list.

Select one or more Global Tightening Program templates check box to view the distribution list. The distribution list shows all controllers currently subscribing to the selected Program template.

If no global Tightening Program templates exist, the work space area is empty. Select Add to create a new Tightening Program template or double-click on an existing Tightening Program template to view or edit parameters.

# Importing a Tightening Program Template

A previously exported Tightening Program template can be imported in a ToolsTalk 2 installation or in a ToolsTalk 2 Station Setup installation.

1. Select Library in the left-side menu bar.

2. Go to Program Templates .

   The workspace shows a list of Tightening Program templates.

3. Select Add and then select the Import tab in the Create new Tightening Program template window.

4. Select Open file and select the desired import file. The file must have the format <tightening_program_template_name>.json. Select Open.

   The workspace shows an updated list of Tightening Program templates.

   The exported file can be given any name with the *.json extension. The *.json file contains a Tightening Program template name that is shown in the list of Tightening Program templates. When a Tightening Program template is imported, the name given to the Tightening Program template is taken from inside the *.json file, regardless of the file name. This means that an imported Tightening Program template may have a different name than the imported file name. To avoid Tightening Program templates having identical names, it is advised to give the template a unique name before exporting and not to change the file name.

# Controller Configuration Library

# Controller Library Introduction

The Controller template is an entire virtual controller. It allows a user to create, edit and analyze all controller configurations without having access to a physical controller. A controller template can be created from the beginning with all parameter values empty. A controller template can be created by copying an existing controller with valid configurations and parameters.

A Controller template does not show information about tools, as no tools are connected. Hardware related information and configurations are not possible. Configurations of supporting functions, like various servers, are not possible from a template. When a template is distributed to a controller, these parameters must be checked or added.

# Controller Library Workspace

Parameter | Description
--- | ---
Check box | Select controller template.
Controller | Shows the name of the controller template.
Last change | Last change, expressed in ToolsTalk 2 time.
Changed by | Last changes made by...
Version | Controller software version that is supported by the controller template.
| Not an actual column. The list of configurations can be sorted in rising or falling alphabetical order, numerical order or time order. Click on the table header row to make an arrow visible and click on the arrow to change the current sorting direction. One arrow is shown at a time.
Controller type | Shows which controller type the configuration is intended for.

Controller template command buttons
Command | Description
--- | ---
Add | New. Creates a new controller template. Import. Import a controller template. File format is *.json
Manage | Distribute. Selects configurations from a template that are to be distributed to one or several controllers. Export. Exports a selected controller template. File format is *.json Delete. Removes selected controller templates from the list.

If no controller templates exist, the work space area is empty. Click Add to create a new controller template, or double-click on an existing template to view or edit parameters.

# Controller Configuration Library - Creating a New Controller Template

The Controller template is an entire virtual controller. It allows a user to create, edit and analyze all controller configurations without having access to a physical controller. A controller template can be created from the beginning with all parameter values empty. A controller template can be created by copying an existing controller with valid configurations and parameters.

A Controller template does not show information about tools, as no tools are connected. Hardware related information and configurations are not possible. Configurations of supporting functions, like various servers, are not possible from a template. When a template is distributed to a controller, these parameters must be checked or added.

1. Select Library in the left-side menu bar.

2. Go to Controller configuration .

   The workspace shows a list of Controller templates.

3. Select Add.

   The Create new controller template dialog window is shown.

4. Enter the following parameters:

   - Issue the controller template with a name.

   - Select the controller type from the drop-down menu.

   - Select the controller software version from the drop-down menu.

5. Select Add.

   The dialog window closes and the list of controller templates is updated.

It is important to select the correct controller software version. A template can only be distributed to controllers which have the same software version.

# Controller Configuration Library - Deleting Controller a Template

1. Select Library in the left-side menu bar.

2. Select Controller configuration .

   The workspace shows a list of Controller templates.

3. Select the check box of the controller template to be deleted.

4. Select Manage and choose Delete from the drop-down menu. The template is deleted form the list.

# Controller Configuration Library - Creating a Template From an Existing Controller

The Controller template is an entire virtual controller. It allows a user to create, edit and analyze all controller configurations without having access to a physical controller. A controller template can be created from the beginning with all parameter values empty. A controller template can be created by copying an existing controller with valid configurations and parameters.

A Controller template does not show information about tools, as no tools are connected. Hardware related information and configurations are not possible. Configurations of supporting functions, like various servers, are not possible from a template. When a template is distributed to a controller, these parameters must be checked or added.

1. Select a controller in the Plant structure workspace .

2. Select Manage and choose Add to library from the drop-down menu.

   All the controller configurations, except hardware and tool dependencies, are copied to the controller configuration library.

3. Select Library in the left-side menu bar.

4. Select Controller configuration in the upper menu bar in the workspace window.

   The workspace shows a list of Controller configurations and the newly created controller configuration that can be used as a template is shown in the list.

   The name of the controller template is copied from the source controller name.

It is recommended to issue the controller template a unique name in the library.

# Controller Configuration Library - Distributing a Controller Template

The Controller template is an entire virtual controller. It allows a user to create, edit and analyze all controller configurations without having access to a physical controller. A controller template can be created from the beginning with all parameter values empty. A controller template can be created by copying an existing controller with valid configurations and parameters.

A Controller template does not show information about tools, as no tools are connected. Hardware related information and configurations are not possible. Configurations of supporting functions, like various servers, are not possible from a template. When a template is distributed to a controller, these parameters must be checked or added.

A controller template or parts thereof can be distributed to one or several controllers. A distribution means that configurations are copied from the template and overwrite the configurations at the destination controllers whenever this is allowed.

The controller template software version, must be the same as the destination controller software version. If they do not match, the distribution is not possible

1. Select Library in the left-side menu bar.

2. Go to Controller configuration .

   The workspace shows a list of Controller templates.

3. Select the check box of the controller template to distribute.

4. Select Manage and choose Distribute from the drop-down menu.

   It is only possible to distribute between controllers of the same type and same software versions.

   The Distribute controller template dialog window opens.

5. Select the check box of each configuration to be included in the distribution.

   Configurations type can be individually selected. Certain dependencies exist between configurations. When selecting to distribute a template configuration, additional configurations may also be selected by default.

6. Select one or more controllers in the right side of the dialog window.

7. Select Distribute in the dialog window.

   The dialog window closes.

8. The selected configurations are only distributed to the controllers in ToolsTalk 2.

The configurations selected for distribution will result in that the existing configurations are deleted and are replaced with the controller configurations from the template.

Relevant Information

- Pushing Configurations to a Controller

# Controller Configuration Library - Editing or Configuring a Controller Template

Editing a controller template is very similar to normal controller configuration. Almost all menu icons and parameter settings are identical to what can be done to a real controller in the ToolsTalk 2 GUI.

1. Select Library in the left-side menu bar.

2. Go to Controller configuration .

   The workspace shows a list of Controller templates.

3. Double-click on the name field in the list of controller templates.

   The controller workspace is identical to a real controller. To show that this is a controller template, the background color of the controller menu is a lighter grey instead of dark.

# Controller Configuration Library - Exporting a Controller Template

The Controller template is an entire virtual controller. It allows a user to create, edit and analyze all controller configurations without having access to a physical controller. A controller template can be created from the beginning with all parameter values empty. A controller template can be created by copying an existing controller with valid configurations and parameters.

A Controller template does not show information about tools, as no tools are connected. Hardware related information and configurations are not possible. Configurations of supporting functions, like various servers, are not possible from a template. When a template is distributed to a controller, these parameters must be checked or added.

A controller template can be exported and then reused (imported) in another ToolsTalk 2 installation or in a ToolsTalk 2 Station Setup installation.

1. Select Library in the left-side menu bar.

2. Go to Controller configuration .

   The workspace shows a list of Controller templates.

3. Select the check box of the controller template to be exported.

4. Select Manage and choose Export from the drop-down menu.

   A browser window opens for saving the export file.

5. The default file name is <controller_template_name>.json Select Save.

The exported file can be given any name with the *.json extension.

Inside the exported *.json file the controller template is given the name from the controller column. When a controller template is imported, the name given to the controller template is taken from this field inside the *.json file, regardless of the file name. This means that an imported controller template may have a different name than the imported file name.

To avoid controller templates with identical names it is advised to give the template a unique name before exporting and not to change the file name.

# Controller Configuration Library - Importing a Controller Template

The Controller template is an entire virtual controller. It allows a user to create, edit and analyze all controller configurations without having access to a physical controller. A controller template can be created from the beginning with all parameter values empty. A controller template can be created by copying an existing controller with valid configurations and parameters.

A Controller template does not show information about tools, as no tools are connected. Hardware related information and configurations are not possible. Configurations of supporting functions, like various servers, are not possible from a template. When a template is distributed to a controller, these parameters must be checked or added.

A previously exported controller template can be imported in a ToolsTalk 2 installation or in a ToolsTalk 2 Station Setup installation.

1. Select Library in the left-side menu bar.

2. Go to Controller configuration .

   The workspace shows a list of Controller templates.

3. Select Add and then select the Import tab in the Create new controller template window.

4. Select Open file and select the desired import file. The file must have the format <controller_template_name>.json. Select Open.

   The workspace shows an updated list of Controller templates.

   The exported file can be given any name with the *.json extension. The *.json file contains a controller template name that is shown in the list of controller templates. When a controller template is imported, the name given to the controller template is taken from inside the *.json file, regardless of the file name. This means that an imported controller template may have a different name than the imported file name. To avoid controller templates having identical names, it is advised to give the template a unique name before exporting and not to change the file name.

# Global Sync Mode Library

# Global Sync Mode Library Workspace

1. Select Library in the left-side menu bar.

2. Go to Sync Mode library .

Column | Description
--- | ---
Check box | Used for example when deleting a Sync Mode.
Name | A user defined name for the Sync Mode.
Description | Description of the Sync Mode.
Operation Mode | Displays if the operation mode is Tightening or Loosening.
Channels | The number of channels in the Sync Mode.
Last changed | Time expressed in ToolsTalk 2 time.
Changed by | Shows which user last changed and saved the configuration data.
Version | Software version of the controller
Controller type | Type of the controller

Sync Mode Library workspace Command Buttons
Command | Description
--- | ---
Add | New. Creates a new Sync Mode.
Manage | Distribute - Opens the Distribute Global Configurations dialog window. The selected Sync Mode can be added to the distribution list. Delete - Removes selected Sync Mode from the list. Import Distributed - In the unlikely event of a ToolsTalk 2 license downgrade, the global distributions are automatically exported. These global distributions can be later imported using the Import Distributed function.

Select one or more of the global Sync Mode check boxes to view the distribution list. The distribution list shows all controllers currently subscribing to the selected configuration.

If no Sync Modes exist, the work space area is empty. Select Add to create a new Sync Mode or double-click on an existing Sync Mode to view or edit parameters.

# Global Sync Mode Library - Creating a Global Sync Mode

## Creating a Global Sync Mode:

1. Select Library in the left-side menu bar.

2. Go to the Sync Mode library in the upper menu bar in the workspace window.

   The workspace shows a list of global Sync Modes.

3. Select Add.

   The Create new Mode dialog window is shown.

4. Enter the following parameters:

   - Select Controller type, Controller Software Version, user defined Name of the global Sync Mode and select the Operation mode from the drop-down list.

5. Select Add.

6. The configuration window for selected type of Sync Mode is shown and you can enter the parameters for the Sync Mode as described in the section "Sync Mode".

   The Sync Mode configuration is auto saved to the Sync Mode library.

# Global Sync Mode Library - Importing a Distributed Sync Mode

In the unlikely event of a ToolsTalk 2 license downgrade, the global distributions are automatically exported. These global distributions can be later imported using the Import Distributed function.

The exported distributions are saved in the folder that was selected as a backup folder during the installation. Path = BackupFolder/DistributedConfigs

1. Select Library in the left-side menu bar.

2. Go to Sync Mode library .

   The workspace shows a list of global Sync Modes.

3. Select Manage and then select Import Distributed.

   A browser window opens for reading the import file.

4. Select the desired import file. The file must be in the format <Syncmodename>.json. Select Open.

5. Select Add in the shortcut window.

6. The configuration window for the imported Sync Mode is displayed.

The Sync Mode configuration is auto saved to the Sync Mode library.

# Global Sync Mode Library - Deleting a Global Sync Mode

1. Select Library in the left-side menu bar.

2. Go to Sync Mode library .

   The workspace shows a list of global Sync Modes.

3. For each Sync Mode to be deleted, select the check box in the leftmost column.

4. Select Manage and then select Delete.

   If a global sync mode loosening is connected to a tightening sync mode, it is not possible to delete it.

   The global Sync Mode is removed from the library and the list is updated.

The controllers subscribing to the deleted Sync Mode do not lose the Sync Mode. A deleted global Sync Mode is removed from the list in the Sync Mode library workspace. The Sync Mode is still present in the list in the Sync Mode workspace of the controllers that have subscribed to the global Sync Mode. The visible change is that the Sync Mode is transformed from being a global Sync Mode to a local Sync Mode. (The entry in the column Library link is cleared).

# Global Sync Mode Library - Distributing a Global Sync Mode

1. Select Library in the left-side menu bar.

2. Go to Sync Mode library .

   The workspace shows a list of global Sync Modes.

3. Select the check box for the Sync Mode/modes that needs to be distributed.

   If the sync mode is distributed already to a controller, then the controller name and the index is shown in the right side of the screen upon selecting the check box .

4. Select Manage and then select Distribute.

   Use the check box to select each configuration which is to be included in the distribution.

5. Select one or more controllers in the right-side of the Distribute Global Configurations dialog window and enter the Index if applicable. Select Add in the dialog window.

   Any updates to the global Sync Mode will update the distributed copies. Changes in the global Sync Mode will apply to the selected controllers.

   If local changes are made in the controller or web GUI, there are two options:

   - Auto revert: Changes in the controller will not apply to the Sync Mode, the global Sync Modes will still be valid.

   - Unlink: Changes in the controller will apply to the Sync Mode and the link to the global Sync Mode will be cut. As a result, the global Sync Mode is immediately removed from the distribution list to the controller.

# Global Sync Mode Library - Removing a Global Sync Mode Subscription From the Distribution List

The global Sync Mode distribution list is like a subscription list. Whenever a change is made to a global Sync Mode, the change is propagated to all subscribers. The distribution list manages the subscription.

Select one Global Sync Mode check box to view the content of the distribution list. The distribution list shows all controllers subscribing to the selected Sync Mode.

To remove the subscription of a Global Sync Mode from one controller:

1. Select a controller in the Plant structure workspace .

2. Go to Sync Mode .

   The Sync Mode workspace shows a list of Sync Modes.

   The entry in the column Library link is marked with Yes for the distributed Sync Mode.

3. Select the check box for the selected Sync Mode.

4. Select Manage then Unlink from the drop-down menu.

   The entry in the column Library link is cleared for the selected Sync Mode.

5. Select Library in the left-side menu bar.

6. Go to Sync Mode library .

7. Select the check box of the removed Sync Mode.

   The distribution list is updated and the controller name is removed from the list.

# Global Sync Mode Library - Editing a Global Sync Mode

1. Select Library in the left-side menu bar.

2. Go to Sync Mode library .

   The workspace shows a list of global Sync Modes.

3. Double-click on the Sync Mode to edit.

4. The configuration window for the selected Sync Mode configuration is shown.

   The Sync Mode is auto-saved to the global Sync Mode library.

   All affected controllers will show the Push indicator in the Plant structure workspace.

# Program Approval

This section describes the approval process for tightening or loosening programs. The program approval is managed by a user with approval privileges.

Relevant Information

- User Group Permissions Menu

# Working with the System Administration Tab

The System administration tab in ToolsTalk 2 is located in the left side menu bar and provides the following functionality:

System administrations functions
System administration Tabs | Description
--- | ---
| Controller Software and Data Management Manages software updates to all controllers. Organize controllers into Custom sections.
| Scheduled Task Controller configurations can be exported and imported at scheduled intervals.
| Functionality Management System (FMS) Manages the distribution of licensed functionality among the connected controllers.
| User Groups Different permissions to see or edit information in ToolsTalk 2 can be given to various user groups.

## Controller Software and Data Management

- Export controller results and settings.

- Import controller settings.

- Load new controller software.

- Switch between controller software installations.

- Generate report.

- Organize controllers in Custom sections.

Export controller configuration parameters and leave the controller program unchanged.

Import a new controller configuration.

Software update changes the controller's software. Controller name, IP address, and server connections can be manually entered.

## Scheduled Tasks

- Export controller results and settings.

- Import controller settings.

- Scheduling of export and import task to selected controllers.

- Database maintenance

- Push controller configuration

Export/import changes a controller's configuration parameters and leaves the controller's program unchanged. Controller names, IP addresses and server connections are unaffected by these operations.

## Functionality Management System

- Add licensed functionality to a controller.

- Remove licensed functionality from a controller.

- Manage a pool of licensed functionality.

- Load additional functionality from Atlas Copco when needed and return functionality when not needed any more.

## User Groups

- Create different user groups.

- Manage the rights to view folders and individual controllers.

- Manage the rights to configure ToolsTalk 2 functionality.

- Manage the rights to configure controller parameters and functionality.

In this Section

- Controller Software and Data Management
- Scheduled Tasks
- Functionality Management System (FMS)
- User Groups
- Program Approval

# Controller Software and Data Management

# Introduction to Controller Software and Data Management

Go to System administration , and then select Controller Software and Data Management .

- Export controller results, configurations and settings.

- Import controller settings.

- Load new controller software.

- Switch between controller software installations.

- Generate report.

- Organize controllers in Custom sections.

- Search for controllers.

Export/import: Changes the controller's configuration parameters and leaves the controller's software program unchanged.

Software update: Changes a controller's software and leaves the controller's configuration parameters unchanged.

Controller names, IP addresses and server connections are unaffected by these operations.

Column | Description
--- | ---
Controller | Controller name.
Controller Type | Which controller type that applies.
Factory port | On: For controllers with enabled communication via factory port. No text is displayed if the connection is disabled (set to off in the controller settings).
Current version | Current software version. Red: Software is not in the approved software list. Add it to the list by clicking the Add command button and enter the current software version. Black: Software is in the approved software list.
Stored version | Stored inactive software version.
Operation | Shows any ongoing operation such as: Task status and result during import and export, and software update task status and result.

Select the box to the left of the controller name to activate the options listed in the table below.

Button | Description
--- | ---
Restart | To restart the selected controller
Generate Report | Generates the SoftwareVersionReportcsv.csv file and opens a dialog pop-up window for storage selection.
Software | Activate stored software: Switches program execution to the stored version. The previous active program reverts to the inactive stored state. Software update: Loads a new program into the controller, into the stored version program space.
Export/Import | Export: Exports controller configurations, parameters and results. The file name should be written in the following format: Filename.tar.gz Export Configuration: Exports settings and configurations. The exported file will have a file name and extension that looks like <Filename>.tar.gz. Import: Imports controller configurations and parameters. The file name should be written in the following format: Filename.tar.gz

Button | Description
--- | ---
Edit | Activate and deactivate the Edit mode for organizing Custom sections.
+ | Adds a Custom sections folder or subfolder. Only visible in Edit mode.
- | Deletes a Custom sections folder or subfolder. Only visible in Edit mode.

The export and import function also exists in Controller Configurations and in the Scheduled Export and Import . The file format and the results are the same.

The right-side of the workspace window contains a list of approved software which is authorised to execute in a controller. Non-approved software is marked in red in the Current Version column.

Command | Description
--- | ---
Add | Opens a shortcut menu to enter a new software version to the list.
Delete | Removes one or more selected software versions from the list.

The Generate report creates a SoftwareVersionReportcsv.csv file containing a matrix with the following information in the columns:

- Controller name.

- Current software version.

- Stored software version.

- Indication if the current software is approved or not.

To organize the controllers in the Plant structure and to access the shortcut options below, click on the controller name. The background color of the controller name will change to light blue.

A maximum of 20 controllers can be selected at any one time.

Right-click on a controller to get the below options.

Shortcut menu | Description
--- | ---
Add new controller | Add a new controller to the Plant structure controller list.
Connect controller | Set controller status to online.
Disconnect controller | Set controller status to offline. The controller name will be struck through
Reset operation status | Force controller status to reset. Clears the current status and resets to idle. This does not interrupt the started process and acts as a failsafe if the connection is lost.
Delete | Deletes a controller from the Plant structure controller list. If a controller is deleted from the All controllers folder it will be permanently deleted. If a controller is deleted from a subfolder, only the copy of the controller is deleted. The controller will still be accessible in the All controllers folder.

## Searching for Controllers

In the Controller Software and Data Management workspace, there are two search fields. One field only searches for controllers in Custom sections and the other one searches for all controllers in the controller list.

- In the search field, enter at least two letters of the controller name.

  It is possible to search for either the controller name, or Type. In the main controller list, it is also possible to search for Software version (Current version).

Relevant Information

- Administrating Scheduled Tasks
- Working with the Controller Information Tab

# Exporting and Importing

The export/import function is used to export the events and tightening results accessible in the Results menu for analysis in external programs, as well as allowing transfer of tightening program, batch, and controller configurations between controllers.

The command Export/Import can be used for the following reasons:

- Exporting tightening results and events for further processing.

- Exporting log files for debug assistance from an Atlas Copco service engineer.

- Exporting the entire controller configuration that can be used to copy the configuration to another controller.

- Comparing two exported configurations to see differences.

- Importing controller configurations.

## Exporting

1. Select theSystem administration tab .

2. Go to Controller software and data management .

3. Select the check box of the controller. It is only possible to export a controller configuration if the controller is online.

4. Select Export/Import to export one of the following:

   Parameter | Description
   --- | ---
   Export... | Exports all controller information. The exported file will have a file name and extension that looks like <Filename>.tar.gz.
   Export Configuration... | Exports settings and configurations. The exported file will have a file name and extension that looks like <Filename>.tar.gz.
   Export program to csv | Exports programs of each controller. (not available for multistep programs) There will be one file for each controller. The exported file will have a file name and extension that looks like <Filename>.csv.
   Export Tool Log | Exports logs (tightenings and hardware information) from connected tools. Available for SRB, TBP and STB. The export consists of atlas_tool_i.zip and ExportInfo.txt

5. Select the location for saving the export file, select OK.

The filename consists of one part to identify the controller and of one part which is a time stamp.

## Importing a controller configuration

The purpose of the Import command is to copy a controller setting and to reuse a previously exported source file and shall have a file name and extension that looks like <Filename>.tar.gz.

1. Select System administration in the left-side menu bar.

2. Select Controller software and data management in the upper menu bar in the workspace window.

3. Select the check box of the controller. It is only possible to import to a controller configuration if the controller is online.

4. Select Export/Import.

   The Import to selected dialog window opens.

5. Select Open file and browse to the selected file.

6. Select the file and select Open.

7. The file path is shown and the Import button is active. Select Import.

After restarting, the imported file is now in use with a new configuration setting.

A file import does not change the program of the controller. It changes every setting and configuration except the factory IP address.

# Updating Controller Software

Updating and switching controller software are two different tasks that are tightly connected. The controller can have two different software versions installed, one active version and one passive version. It is a simple process to switch between the two versions. Switching controller software is the task that switches active and passive software.

## Loading New Software to the Controller:

1. Select the System administration tab .

2. Go to Controller software and data management .

3. Select the check box of the controller. It is only possible to update the controller software if the controller is online.

4. Select Software then Software update from the drop-down menu.

   The Software update dialog window opens.

5. Select Open file and browse the selected file.

   The file name should end with -px2it.zip

6. Mark the file and select Open.

7. The file path is shown and the button Software update is active. Select the button to start loading the software.

If the controller application fails to start repeatedly the controller will boot up in rescue mode. In rescue mode a new firmware can be installed. The rescue image is distributed with the software update and can be updated if a newer rescue image exists.

Do not power off the system during rescue image update. The system will reboot when starting the update.

# Switching Controller Software

Updating and switching controller software are two different tasks that are tightly connected. The controller can have two different software versions installed, one active version and one passive version. It is a simple process to switch between the two versions. Switching controller software is the task that switches active and passive software.

## Activating Stored Software in the Controller

1. Select the System administration tab in the left-side menu bar.

2. Go to Controller software and data management .

3. Select the check box for the controller. It is only possible to execute the command if the controller is online.

4. Select Software then Activate stored Software from the drop-down menu.

5. The Software update column in the workspace will show the following messages:

   1. Activating stored software.

   2. Stored software activated, controller restarting.

# Generating a Controller Software Report

The Controller update workspace shows all the controllers and both their current running software and the stored software.

## Generating a List On File:

1. Select the System administration tab in the left-side menu bar.

2. Go to Controller software and data management .

3. Select Generate report.

   The browser dialog window opens.

4. Select a file location and select Save.

The SoftwareVersionResultcsv.csv file will be written to the selected location.

# Managing Custom Sections

1. Go to the System administration tab , and then select Controller Software and Data Management .

2. In Custom sections, select Edit to enter the Edit mode. Edit will change color to light blue to indicate it has been selected and two new buttons appear, a + and a -, .

When in Edit mode, the following organizing options are available:

- Creating a new folder

- Creating a new subfolder

- Deleting a folder or subfolder

- Copying a controller to a folder

- Changing the display order of folders and controllers

To exit the Edit mode:

- Select Edit to exit the edit mode. Edit will change color and the + and - buttons will disappear.

## Creating a New Folder

1. To the left of the Edit button, select the + button

   or

   Right-click anywhere in the folder area and choose Add folder in the shortcut menu.

   A New folder will be created and added to the list.

2. Select the New folder . The color will change to light blue to indicate that it has been selected.

3. Press F2, re-name the folder and press Enter.

## Creating a New Subfolder

1. To the right of the folder name, click the + button

   or

   Right-click on an existing folder and select Add folder in the shortcut menu.

   A New folder will be created and added to the list.

2. Select the New folder. The color will change to light blue to indicate that it has been selected.

3. Press F2, re-name the folder and press Enter.

## Deleting a Folder or Subfolder

- To the right of the folder name, select the - button

  or

  Right-click on an existing folder and click Delete in the shortcut menu.

  The folder will be deleted and the copies of the controllers will be removed.

When a folder containing subfolders is deleted, all the subfolders are deleted too.

## Copying a Controller to a Folder

1. Select All controllers, or the appropriate Custom section, from the drop-down menu above the controller list.

2. Select a controller. The color will change to light blue to indicate that it has been selected.

   One or many controllers can be selected.

   Press Ctrl+ Left click to add one controller at the time to the selection.

   Press Shift+ Left click to add multiple controllers at once to the selection.

3. Drag the selected controllers to the destination folder.

## Changing the Order of Folders and Controllers

- Drag the selected folder or controller to its new position.

# Scheduled Tasks

Go to the System administration tab , and select Scheduled Task . The workspace displays the following information.

Column | Description
--- | ---
Check box | Select a task by using the check box.
Description | Description of the task.
Name | Task type.
Last changed | Time stamp for latest changes.
Changed by | Task modified by...
Latest run | Last time the task was executed.
Running | Status information of a currently running task.

Command | Description
--- | ---
Execute now | A task can be selected and forced to execute immediately, without waiting for the set scheduled date and time. If a scheduled task has an upload file location or a back up file location, then that must be must be defined in order for 'Execute now' to work.
Add | Create a new task. Select task type.
Delete | Delete one or more tasks from the task table.

The list of controllers on the right side displays which controllers that are affected by the scheduled task. The list is only populated if one or more tasks are selected.

In this Section

- Administrating Scheduled Tasks
- Controller Selection
- Export Controller Configuration
- Import Controller Configuration
- Upload Controller Software
- Database Maintenance
- Push Controller Configuration
- Backup License Distributions

# Administrating Scheduled Tasks

1. Go to System administration .

2. Go to Scheduled task .

Double-click on an existing task to view the configuration.

Menu | Description
--- | ---
Properties | Issue the task a name and description.
Schedule | Time and interval settings for the task.
Controllers | Select which controllers are affected by the task.
Results | The result of the task.
Import file | Only visible if the task type is import controller configuration.
Backup location | Only visible if the task type is export controller configuration.

## Adding a New Scheduled Task

1. Select Add.

2. Select a Scheduled task type:

   - Export controller configurations

   - Import controller configurations

   - Database Maintenance

   - Push controller configuration

   - Export License Distributions

## Execute Now

1. Select a task by selecting the corresponding check box.

2. Select Execute now in order to run the task immediately.

## Deleting a Scheduled Task

1. Select a task by selecting the corresponding check box, and then select Delete to remove the selected task.

   The deleted task is removed from list of scheduled tasks.

## Editing a Scheduled Task

1. Double-click on the task to be edited.

2. Edit the scheduled task.

Changes are automatically saved and no Push is needed.

The export and import function also exists in Controller configurations and in the Controller software and data management . The file format and the results are the same in both cases.

Relevant Information

- Export and Import

# Controller Selection

Valid for the Import, Export, and Push controller configuration scheduled tasks.

Select the controllers on which to run the scheduled task.

Parameter | Description
--- | ---
Schedule all controllers | When set to Yes, the scheduled task will run on all controllers that are connected to ToolsTalk 2 and that are visible in the plant structure . The controller list will not be visible when set to Yes. When set to No, the controller list will be visible and individual selections are possible.
Toggle all | All controllers are automatically marked and the task will run on all controllers. It is possible to deselect individual controllers.
| Select the controllers on which to run the scheduled task. The task will affect the selected controllers only.

Important difference between Toggle all and Schedule all controllers:

Toggle all
Easy to select or deselect individual controllers. A static list. If new controllers are added, they are not automatically included.

Schedule all controllers
Any changes in the structure with connected controllers will not alter the scheduled task. Dynamic list, all controllers are affected.

Important notice:

If an import is made to several controllers using the same import file, the controller name field is overwritten by the name of the controller in the imported file. Resulting in all controllers having the same name.

Further import or export with named controllers will fail, as the name will not be recognized anymore.

One way to overcome this issue is to set the Schedule all controllers to Yes.

# Export Controller Configuration

This menu is visible if the Scheduled task type is Export controller configuration.

Parameter | Description
--- | ---
Backup location | Enter a valid path to the location to which the export file is to be written. The default value is empty with an error indicator that shows the server does not recognize the location as a valid path. The path must be valid when the scheduled task is executed.
File name | The exported file is in the format : *.tar.gz It can later be used to import configurations to controllers or sent to Atlas Copco for debugging purpose or failure analysis. The default filename is something like PFExport_<controller-name>_<Date-code>.tar.gz. System variables can be used to differentiate and to create unique filenames.
Folder per controller | When set to Yes, each export will be saved in a separate sub folder. When set to No, the exports will be saved in the Save Location folder.
Folder name | System variables can be used to differentiate and to create unique folder names.
Delete old configuration files | When set to Yes, old controller configuration files stored with a unique file name will be deleted. The unique file name must contain a system variable. For example, <ControllerName>.

System variables can be used to specify file names and folder names for the export. They are added at runtime, to the file name or folder to create unique export files or locations.

The system variables are written inside brackets, and the following may be used:

- [ControllerName]

- [IpAddress]

- [ControllerSerialNumber]

It is possible to combine text with system variables. An example is Station_3_[ControllerName]_[IpAddress]. If the controller name is ABC and its IP address is 10.25.25.180, the resulting filename at runtime will be Station_3_ABC_10.25.25.180.tar.gz.

A scheduled file export can only occur if the controller is online at the time of the export and that the export path is valid.

Schedule
Parameter | Description
--- | ---
Enabled | When set to Yes, the scheduled task will run according to the scheduled configurations. When set to No, the scheduled task will not run.
Weekdays | Mark one or more weekdays when the task will run.
Time | Select a run time from the drop-down menu.
Start date | Select a start date for the run time from the calender icon.
Select end date | When set to Yes, the scheduled task will run according to the schedule until the end date. When set to No, the scheduled task will run according to the schedule from the start date.

After a task is executed, the results are shown in the Results menu.

Results
Parameter | Description
--- | ---
Status | The scheduled task status after running the task can show OK or NOK.
Controller | Displayed if available for the task.
Latest run | Time and date when the scheduled task was executed.
Error | Error code examples if the status is NOK. ControllerNotOnline ControllerNotFound NoWriteAccessToStorage ExportFailed ImportFailed FileNotFound TimedOut

# Import Controller Configuration

This menu is visible if the Scheduled task type is Import controller configuration.

Menu item | Description
--- | ---
File name | The file and name must be a previously exported configuration file. It must be in the format : *.tar.gz
Browse | The command opens the browser window to locate the file to import.

The file is loaded into ToolsTalk 2 and the scheduled task runs at the scheduled times.

A file import does not change the program of the controller. It changes every setting and configuration except the factory IP address.

A scheduled file import can only occur if the controller is online at the time of the import.

Schedule
Parameter | Description
--- | ---
Enabled | When set to Yes, the scheduled task will run according to the scheduled configurations. When set to No, the scheduled task will not run.
Weekdays | Mark one or more weekdays when the task will run.
Time | Select a run time from the drop-down menu.
Start date | Select a start date for the run time from the calender icon.
Select end date | When set to Yes, the scheduled task will run according to the schedule until the end date. When set to No, the scheduled task will run according to the schedule from the start date.

After a task is executed, the results are shown in the Results menu.

Results
Parameter | Description
--- | ---
Status | The scheduled task status after running the task can show OK or NOK.
Controller | Displayed if available for the task.
Latest run | Time and date when the scheduled task was executed.
Error | Error code examples if the status is NOK. ControllerNotOnline ControllerNotFound NoWriteAccessToStorage ExportFailed ImportFailed FileNotFound TimedOut

# Upload Controller Software

This scheduled task is used to upload the controller software to the stored version of the software in the controller.

This scheduled task is not an activation of the software but only an upload of the software.

## Properties

Parameter | Description
--- | ---
Name | Enter a name for the scheduled task.
Description | Enter a description for the scheduled task.

## Schedule

Parameter | Description
--- | ---
Enabled | When set to Yes, the scheduled task will run according to the scheduled configurations. When set to No, the scheduled task will not run.
Weekdays | Mark one or more weekdays when the task will run.
Time | Select a run time from the drop-down menu.
Start date | Select a start date for the run time from the calender icon.
Select end date | When set to Yes, the scheduled task will run according to the schedule until the end date. When set to No, the scheduled task will run according to the schedule from the start date.

## Software Update

Parameter | Description
--- | ---
File name | Select Browse and then select Open File to select and upload the controller software file.

## Controllers

Select Yes if the task has to be scheduled for all controllers or Select No and then select the required controllers from the drop-down list.

After a task is executed, the results are shown in the Results menu.

## Results

Parameter | Description
--- | ---
Status | The scheduled task status after running the task can show OK or NOK.
Controller | Displayed if available for the task.
Latest run | Time and date when the scheduled task was executed.
Error | Error code examples if the status is NOK. ControllerNotOnline ControllerNotFound NoWriteAccessToStorage ExportFailed ImportFailed FileNotFound TimedOut

# Database Maintenance

Events such as controller configurations, libraries, tightening programs, device settings, results, etc. are automatically added to the previously saved events in the database. To clear the database in order to save space, and to make the system more efficient, the history data can be deleted, keeping only the latest results of all the events. Taking "snapshots" of the latest results of all the events can be scheduled in the Database Maintenance feature.

Archive data: Select yes to save (archive) the history data in the database. History data will be deleted after every snapshot if selecting no. Note that the results of the taken snapshots are saved regardless.

Only one instance of Database Maintenance task type can be defined at a time.

Schedule
Parameter | Description
--- | ---
Enabled | When set to Yes, the scheduled task will run according to the scheduled configurations. When set to No, the scheduled task will not run.
Weekdays | Mark one or more weekdays when the task will run.
Time | Select a run time from the drop-down menu.
Start date | Select a start date for the run time from the calender icon.
Select end date | When set to Yes, the scheduled task will run according to the schedule until the end date. When set to No, the scheduled task will run according to the schedule from the start date.

After a task is executed, the results are shown in the Results menu.

Results
Parameter | Description
--- | ---
Status | The scheduled task status after running the task can show OK or NOK.
Controller | Displayed if available for the task.
Latest run | Time and date when the scheduled task was executed.
Error | Error code examples if the status is NOK. ControllerNotOnline ControllerNotFound NoWriteAccessToStorage ExportFailed ImportFailed FileNotFound TimedOut

# Push Controller Configuration

This menu is visible if the Scheduled task type is selected to Push controller configuration.

Schedule
Parameter | Description
--- | ---
Enabled | When set to Yes, the scheduled task will run according to the scheduled configurations. When set to No, the scheduled task will not run.
Weekdays | Mark one or more weekdays when the task will run.
Time | Select a run time from the drop-down menu.
Start date | Select a start date for the run time from the calender icon.
Select end date | When set to Yes, the scheduled task will run according to the schedule until the end date. When set to No, the scheduled task will run according to the schedule from the start date.

After a task is executed, the results are shown in the Results menu.

Results
Parameter | Description
--- | ---
Status | The scheduled task status after running the task can show OK or NOK.
Controller | Displayed if available for the task.
Latest run | Time and date when the scheduled task was executed.
Error | Error code examples if the status is NOK. ControllerNotOnline ControllerNotFound NoWriteAccessToStorage ExportFailed ImportFailed FileNotFound TimedOut

# Backup License Distributions

This Scheduled Task is used for creating backups of the License Distributions on a regular basis. The backups are stored on the ToolsTalk2 server and in the event of a ToolsTalk 2 license downgrade, the backup can then be used to restore the controllers with the reserved licenses again.

Only one instance of Backup License Distributions task type can be defined at a time.

## Setting Up the Backup License Distributions Task.

## Properties

Parameter | Description
--- | ---
Name | Enter a name for the scheduled task.
Description | Enter a description for the scheduled task.

## Schedule

Parameter | Description
--- | ---
Enabled | When set to Yes, the scheduled task will run according to the scheduled configurations. When set to No, the scheduled task will not run.
Weekdays | Mark one or more weekdays when the task will run.
Time | Select a run time from the drop-down menu.
Start date | Select a start date for the run time from the calender icon.
Select end date | When set to Yes, the scheduled task will run according to the schedule until the end date. When set to No, the scheduled task will run according to the schedule from the start date.

## Backup Location

Parameter | Description
--- | ---
File name | Enter a file name for the backup.

## Results

Parameter | Description
--- | ---
Status | The scheduled task status after running the task can show OK or NOK.
Controller | Displayed if available for the task.
Latest run | Time and date when the scheduled task was executed.
Error | Error code examples if the status is NOK. ControllerNotOnline ControllerNotFound NoWriteAccessToStorage ExportFailed ImportFailed FileNotFound TimedOut

In this Section

- Restoring the License Distributions from a Backup

# Restoring the License Distributions from a Backup

In the event of a ToolsTalk2 license downgrade, the License Distribution backup can be used to restore the License Distributions to the controllers again. The restore is performed by first downloading the License Distributions Backup, and then importing the downloaded backup.

## Downloading a License Distributions Backup

1. Select the System Administration tab , and then go to the Scheduled Tasks tab .

2. In the workspace, double-click on the Backup License Distribution task.

3. In Results, select to download the License Distribution backup that is to be restored.

4. In the Save As dialog , browse to a location for the download, and then select Save.

## Importing a License Distributions Backup

The downloaded file will now be accessible for import via the Functionality Management System tab , using the License Distributions Import function.

Relevant Information

- Managing License Distributions

# Functionality Management System (FMS)

# Functionality Management System Introduction

The Functionality Management System (FMS) allows Atlas Copco customers to use additional desired features, when they are needed, through a dynamic licensing scheme.

After receiving a purchase order, the customer’s account in Atlas Copco License Portal (ACLP) will automatically receive the purchased features within 24 hours and these features can be downloaded as a license file.

This capability file (included in the license agreement) is loaded in the Local License Server (LLS) where it is decoded and available for distribution.

A pool of features is created and may be used across a number of controllers. A desired feature item can be uploaded to the controller when needed, and be returned to the pool when it is not needed anymore.

In the Atlas Copco License Portal (ACLP) it is possible to manage an account with all features, entitle and return licenses to/from a license server.

The creation and management of a customer account in the ACLP is not covered in this documentation.

# Functionality Management System Definitions

Distribution of functionality to controllers
License distribution | Function
--- | ---
Local License Server (LLS) | A unit that holds the pool of feature items and that can distribute the feature items to the license manager in a controller.
Atlas Copco license portal (ACLP) | A unit that can send a license file, containing all the desired feature items, to the customer.
License | Access rights to feature items. The license states the conditions for how the feature items may be used.
License Manager | A function in the controller that loads, manages and returns feature items.
Virtual Station Type | A license for a fixed collection of features bundled together that are assigned in its entirety to a virtual station. For handheld systems.
Sync Functionality | A license for a fixed collection of features bundled together that are assigned in its entirety to a virtual station. For a fixtured system.
Virtual Station Feature | A license for an individual controller feature, for example TurboTight or TrueAngle.
Controller Feature | A license for a controller-wide feature, for example Step Sync or Soft PLC. These are assigned per controller and are not restricted to any virtual station on that controller.
Feature item | A piece of software code that can be loaded into the controller to provide additional functionality. The usage conditions are covered by the license agreement.
Intelligent Application module (IAM) | A storage module that contain all the controller programs, configurations and results. Certain modules may also include additional loaded feature items.
Reservation list | The distribution server has a pool of feature items. Some of them are allocated to controllers and some are free for distribution. The reservation list contains information on how feature items are allocated.
Borrow time | Applicable in a networked distribution environment. A controller must periodically check with the LLS and synchronize its feature items with the reservation list.
Expired license | Changes may be made in the controller configuration or program, and a mismatch between the loaded feature items and the content of the reservation list may occur. In this case an error event will be displayed if a feature item is used that has expired on the controller.
Capability file | The binary file that is downloaded from the ACLP. It contains all the valid feature items. When it is decoded and stored on the server, a pool of feature items is available for distribution to the controllers.

# Editing the Distribution of License Types and Features

The available License Types and Features can be either added, or removed from the controllers.

1. Select the System Administration tab .

2. Select the Functionality Management System tab to display an overview of the License Distribution on the controllers.

   You can filter the controllers by selecting a Custom Sections folder.

3. Select the Edit button for a specific controller. A dialog window with the available license types and features opens.

4. Select each of the tabs to enter the count for each license type, or feature, that shall be available on the controller.

5. Select OK to save and continue.

# Distribution of Feature Items

In the Functionality Management System (FMS) workspace, a user can manage licenses on all the controllers that are connected to the Local License Server (LLS) and online to the ToolsTalk 2 server.

1. Select the System Administration tab .

2. Select the Functionality Management System tab to show an overview of the License Distribution on the controllers.

The view and information below assumes that a capability file has been received from Atlas Copco, and that it is loaded into the LLS.

## License Distribution Overview

The License Distribution Overview is made up of several Sub-Tabs, these are explained below.

## Controller

The Controller sub-tab shows the distribution of Licensed Feature Items across the controllers. For a more detailed overview, select a specific row to expand it and view the controller's current capabilities

Controller
Column | Functionality
--- | ---
Edit | For editing the number of licences distributed on the controllers.
Controller | Name issued to the controller.
Virtual Station Types | The amount of licences, by type, distributed to each controller.
Sync Functionalities | The amount of licenses for a fixtured system, by type, distributed to each controller.
Virtual Station Features | Features on Virtual Station level that are present on each Controller.
Controller Features | Features on Controller level that are present on each controller.

## Virtual Station Types

The Virtual Station Types sub-tab shows the distribution of Licensed Virtual Station Feature Types across the controllers.

Virtual Station Types
Column | Functionality
--- | ---
Virtual Station Types | Type of License.
Controller Name | Name issued to the controller.
Count | The amount of Licensed Feature Types distributed to the controllers.
Available | The amount of Licensed Feature Types available to distribute to the controllers.
On controller | The amount of controllers on which the Licensed Feature Types are active.
Reserved | The amount of controllers on which the Licensed Feature Types are reserved. When a license is assigned to a controller from ToolsTalk 2, that license is reserved for that controller in the License server. When the controller connects and syncs with the license server, the license will be in both the states Reserved and On controller.
Total | The amount of Licensed Feature Types available in total.

## Sync Functionalities

The Sync Functionalities sub-tab shows the distribution of Licensed Sync Functionality Items for a fixtured system across the controllers.

Sync Functionalities
Column | Functionality
--- | ---
Sync Functionalities | Type of feature
Controller name | Name issued to the controller.
Count | The amount of Licensed Feature Items distributed to the controllers.
Available | The amount of Licensed Feature Items available to distribute to the controllers.
On controller | The amount of controllers on which the Licensed Feature Items are active.
Reserved | When a license is assigned to a controller from ToolsTalk 2, that license is reserved for that controller in the License server. When the controller connects and syncs with the license server, the license will be in both the states Reserved and On controller.
Total | The amount of Licensed Feature Types available in total.

## Virtual Station Features

The Virtual Station Features sub-tab shows the distribution of Licensed Virtual Station Feature Items across the controllers.

Virtual Station Features
Column | Functionality
--- | ---
Virtual Station Features | Type of Feature
Controller Name | Name issued to the controller.
Count | The amount of Licensed Feature Items distributed to the controllers.
Available | The amount of Licensed Feature Items available to distribute to the controllers.
On controller | The amount of controllers on which the Licensed Feature Items are active.
Reserved | The amount of controllers on which the Licensed Feature Types are reserved. When a license is assigned to a controller from ToolsTalk 2, that license is reserved for that controller in the License server. When the controller connects and syncs with the license server, the license will be in both the states Reserved and On controller.
Total | The amount of Licensed Feature Items available in total.

## Controller Features

The Controller Features sub-tab shows the distribution of Licensed Controller Feature Items across the controllers, these are dictated by the Tool License

Controller Features
Column | Functionality
--- | ---
Controller Features | Type of Feature
Controller Name | Name issued to the controller.
Count | The amount of Licensed Feature Items distributed to the controllers.
Available | The amount of Licensed Feature Items available to distribute to the controllers.
On controller | The amount of controllers on which the Licensed Feature Items are active.
Reserved | The amount of controllers on which the Licensed Feature Types are reserved. When a license is assigned to a controller from ToolsTalk 2, that license is reserved for that controller in the License server. When the controller connects and syncs with the license server, the license will be in both the states Reserved and On controller.
Total | The amount of Licensed Feature Items available in total.

## FMS Portable

The FMS Portable sub-tab shows the distribution of FMS Portable Devices across the controllers.

FMS Portable
Column | Functionality
--- | ---
FMS Portable | ID number of the FMS Portable device.
Controller Name | Name issued to the controller.

## FMS Workspace Features

## Command Button

Command button | Functionality
--- | ---
Manage | Download request... - The Capability file is retrieved from the LLS and can be sent to the ACLP for updating. Upload features... - The Capability file file received from ACLP is loaded into the LLS. License Distributions... - For exporting, importing, restoring and resetting License Distributions. For further information, see separate section in the User Guide.

The Capability file is a binary file that contains the license items. The file is created in the Atlas Copco Licensing Portal (ACLP) and downloaded to the customer. When decoded in the distribution server, a pool of features is created that can be distributed to the controllers in two ways:

- A networked distribution system using the Functionality Management System server which is controlled through the ToolsTalk 2 user interface.

- A manual distribution system using a secure USB flash drive that is inserted into each controller and managed through the controller user interface. It is described in detail in the controller documentation.

## General Information

Column | Functionality
--- | ---
Host Id | A unique identity of the distribution server on which the capability file is loaded.
ToolsTalk2 License | The name of the current functionality level.
ToolsTalk2 Virtual Stations | Number of configured virtual stations / total virtual stations available for configuration

Relevant Information

- Managing License Distributions
- Pushing Configurations to a Controller
- SoftPLC Overview

In this Section

- Editing the Distribution of License Types and Features

# Editing the Distribution of License Types and Features

The available License Types and Features can be either added, or removed from the controllers.

1. Select the System Administration tab .

2. Select the Functionality Management System tab to display an overview of the License Distribution on the controllers.

   You can filter the controllers by selecting a Custom Sections folder.

3. Select the Edit button for a specific controller. A dialog window with the available license types and features opens.

4. Select each of the tabs to enter the count for each license type, or feature, that shall be available on the controller.

5. Select OK to save and continue.

# Managing License Distributions

Export: The ToolsTalk2 server automatically stores an internal backup of the last successful License Distributions state. This license distributions backup can be exported from the system using the Export function.

Import: Imports a license distribution as a merge operation. Adds licensed devices with their license distributions to the system. If any licensed device is already represented with its license distribution in the system, its license distribution will be overwritten by the import.

Restore: Imports a license distribution as a restore operation. The license distributions state in the system is replaced by the state in the imported file. The Restore operation overwrites any existing license distribution.

Reset: Resets the license distributions on the local license server. All Licensed Feature Items are revoked from all connected controllers.

WARNING! It is strongly recommended to not to use the reset function in a production environment, as it would stop production!

Exporting License Distributions

1. Select the System Administration tab , and then the Functionality Management System tab .

2. Select the MANAGE button, and then select License Distributions... from the list.

3. Select the Export tab.

4. Specify a location for the export, and then select Export.

Importing License Distributions and Restoring License Distributions requires that the license file has first been uploaded, so that the system knows how many licenses are available to distribute.

Importing License Distributions

1. Select the System Administration tab , and then the Functionality Management System tab .

2. Select the MANAGE button, and then select License Distributions... from the list.

3. Select the Import tab.

4. Browse to the import file location, and then select Import.

Restoring License Distributions

1. Select the System Administration tab , and then the Functionality Management System tab .

2. Select the MANAGE button, and then select License Distributions... from the list.

3. Select the Restore tab.

4. Browse to the restore file location, and then select Restore.

WARNING! This action will remove any existing reservations and restore the License Distributions to the state in the imported file.

Resetting License Distributions

1. Select the System Administration tab , and then the Functionality Management System tab .

2. Select the MANAGE button, and then select License Distributions... from the list.

3. Select the Reset tab, read and select the Reset terms and conditions checkbox and select Reset.

WARNING! It is strongly recommended to not to use the reset function in a production environment, as it would stop production!

Relevant Information

- Distribution of Feature Items

# User Groups

# User Groups Overview

This feature is only visible for users that have user rights as Administrator in ToolsTalk 2.

The User group function in ToolsTalk 2 provides the following functions:

- Creating or deleting user groups.

- Assigning user access rights to folders and controllers.

- Assigning user rights to change controller configurations and parameter settings.

- Assigning user rights to distribute library functions to several controllers and ToolsTalk 2 administrative tasks.

## Viewing the user groups:

1. Select System administration in the left menu bar.

2. Select User group in the top menu bar.

Each row in the workspace table represents one user group that can be given different user rights.

The columns have the following headers from left to right:

Column | Description
--- | ---
Check box | To select or deselect a user group.
Name | User group name.
Description | Optional field.
AD group | Active Directory group name. Created by the IT department.
| Not an actual column. The list of configurations can be sorted in rising or falling alphabetical order, numerical order or time order. Click on the table header row to make an arrow visible and click on the arrow to change the current sorting direction. One arrow is shown at a time.

The top row in the table is named Administrators. This user group cannot be deleted.

Command | Description
--- | ---
Add | Create a new user group. A dialog window opens.
Delete | Delete one or more user groups from the group table.

# User Group Prerequisites

It is possible to create several user groups in ToolsTalk 2. Each of the user groups can be given different user rights to create, read, update and delete parameters, configurations and folders in ToolsTalk 2.

A network administrator in the company IT department must create one or more Active Directory (AD) groups. An AD group can be assigned to one user group in ToolsTalk 2. Each user group in ToolsTalk 2 can be given one unique set of user rights.

Thus, for every combination of ToolsTalk 2 user rights one AD group must be created. Individual users are assigned to one or more AD groups. All members in the user group have the same user rights in ToolsTalk 2

For example, create the following four groups:

- Operators on line 1.

- Line manager for line 1.

- Factory production engineer.

- Production quality manager.

Individual users are assigned to one or more of the groups.

Create also four user groups in ToolsTalk 2 (using the same group names). To each user group one AD group is assigned. Create the following user rights:

- Operators on line 1; can only see tightening results from line 1, and can not change any configuration parameters.

- Line manager for line 1; can see all controllers and has additional user rights to change configuration parameters for controllers on line 1.

- Factory production engineer; can change configuration parameters on line 1 and line 2, but can not see all tightening results.

- Production quality manager; can see all the tightening results and event logs from the entire factory.

# Creating, Deleting or Editing a User Group

1. Select the System administration icon in the left menu bar.

2. Select the User group icon in the top menu bar.

   The workspace window shows a table of user groups.

   - To delete a user group, select the check box and click Delete.

   - To edit the user rights of a user group, double click on the row in the table. The workspace shows the configuration menus.

   - To add a new user group, click Add. The Create group pop-up window appears and the following parameters must be entered:

     - User group name.

     - Optional user group description.

     - Name of an existing AD group.

3. Select Add to save and close the window.

   The workspace window shows an updated table of user groups.

User group properties
Column | Description
--- | ---
Name | The ToolsTalk 2 name of the user group
Description | Optional information field.
AD group | Active Directory group name, created by the IT department. Contains individual users who must have the user rights to access the ToolsTalk 2 server.
Enabled Yes/No | Valid only for super administrator credentials. This function disables the user groups during a downgrade instead of deleting them. Set Enabled to No before downgrading ToolsTalk2. Set Enabled to Yes after upgrading ToolsTalk2 and the license is in place. This starts the client for those specific users in that group, with same permissions set as before the downgrade. if the Enabled is not set to Yes after the upgrade, the client will not start for those specific users in that group and a warning "'You do not have access to the application" is displayed.

# User Group Permissions Menu

1. Select the System administration icon in the left menu bar.

2. Select the User group icon in the top menu bar.

   The workspace window shows a table of user groups.

3. Double-click on one row in the table to enable the editing of a user group.

   The Group permissions menu has three tabs to set user rights.

User group rights
Column | Description
--- | ---
Folders | Assigns user rights to access and modify folders in the plant structure.
Controllers | Assigns user rights to access and modify controllers in the selected folders.
Global functions | Assigns user rights to perform ToolsTalk 2 system administration tasks and global library functions.

1. Select the Folders tab, and select which folders the user group can access.

   If a folder is invisible, controllers contained in the folder are unaccessible.

2. Select the Controllers tab, and select what user rights the group has on the controllers.

   If a controller is visible, all configurations and parameters can be read.

3. Select the Global functions tab, and select which global functions in ToolsTalk 2 the user group can access.

Relevant Information

- Controller User Rights
- Folder User Rights
- Global Functions User Rights

# Folder User Rights

The first step in user rights is to assign which folders in the plant structure that are accessible.

1. Select the System administration icon in the left menu bar.

2. Select the User group icon in the top menu bar.

   The workspace window shows a table of user groups.

3. Double click on one row in the table to display the menus for editing.

4. Click the desired tab in the Group permissions menu.

5. Set desired user rights for the selected user group. A selected check box indicates that the feature is active.

   The possible combinations are described in the table.

   Changes are automatically saved.

The plant structure contains a folder named All controllers. This folder contains all controllers that are connected to the ToolsTalk 2 server.

Customized folders and sub-folders can be created for improved visibility and for logical grouping of controllers.

User rights to folders
Parameter | Description | Condition
--- | --- | ---
Same permission on all folders | Radio button If marked, the selected user rights are applicable for all folders in the plant structure (new included). | If unmarked: If the plant structure is changed, it may be necessary to update the user rights for certain folders.
Manually set permissions on each folder | If marked, the selected user rights are applicable only for the selected folders in the plant structure. |
Read | Checkbox The user group can see the folder and its content. | If unmarked: The folder and its content is invisible to the user group.
Update | Checkbox The user group can move, copy and delete controllers to/from the folder. |
Create & Delete | Checkbox With Create & Delete permission for a folder, the user can create and delete a sub-folder within a folder. With Create & Delete permission for folder All controllers, the user can also delete a controller from ToolsTalk 2. With Create & Delete permission for all folders (new included), the user also has the possibility to delete main folders. |

A folder with no marked user rights is invisible to the user group in the plant structure .

The minimum user rights level for a folder is Read. This level makes a folder visible and its content of subfolders and controllers are also visible.

If a controller is visible, its configurations and parameters can at least be read. Additional user rights can be assigned to the user group.

# Controller User Rights

The second step in user rights is to assign what permissions the group has on selected controllers that are accessible in the plant structure .

If a controller is visible, configurations and parameters can be read. Additional designated user rights can be given to the user group.

1. Select the System administration icon in the left menu bar.

2. Select the User group icon in the top menu bar.

   The workspace window shows a table of user groups.

3. Double click on one row in the table to display the menus for editing.

4. Click the desired tab in the Group permissions menu.

5. Set desired user rights for the selected user group. A selected check box indicates that the feature is active.

   The possible combinations are described in the table.

   Changes are automatically saved.

User rights to controllers
Parameter | Description | Condition
--- | --- | ---
Same permission on all controllers (new included) | Radio button If marked, the selected user rights are applicable for all visible controllers in the plant structure (new included. | If unmarked: If the plant structure is changed, for example if new controllers are added, it is necessary to update the user rights for the controllers.
Manually set permissions on each controller | Radio button If marked, the selected user rights are applicable only for selected controllers in the plant structure. |
Update | Check box Members of the user group can: Change controller configurations and settings that already exist on the controller. Revert the changes, Push the changes to the controller and Unlink global configurations. Restart a controller from Controller in the plant structure. |
Create & Delete | Check box Members of the user group Create & Delete have the permissions to: Create and delete configurations on the controller. Paste configurations to the controller (copied from other controllers or from a library). Export and Import controller data to/from file from controller in Plant structure. |
| Open the folder and display the content. |
| Close the folder and hide the content. |
(X/Y) | X controllers out of totally Y controllers in the marked folder, do have the selected privilege |

A folder with no marked user rights is invisible to the user group in the plant structure .

The minimum user rights level for a folder is Read. This level makes a folder visible and its content of subfolders and controllers are also visible.

If a controller is visible, its configurations and parameters can at least be read. Additional user rights can be assigned to the user group.

# Global Functions User Rights

The third step in user rights is to assign which global functions in ToolsTalk 2 are accessible.

1. Select the System administration icon in the left menu bar.

2. Select the User group icon in the top menu bar.

   The workspace window shows a table of user groups.

3. Double click on one row in the table to display the menus for editing.

4. Click the desired tab in the Group permissions menu.

5. Set desired user rights for the selected user group. A selected check box indicates that the feature is active.

   The possible combinations are described in the table.

   Changes are automatically saved.

If a user group has the Create & Delete user rights level for a controller, it is possible to create and edit all controller configurations.

Global functions is a group of ToolsTalk 2 administrative functions and library functions with icons in the left side menu. A user group can be given different user rights to global functions.

If no user rights are allowed for a function, the function is inaccessible to the user and the icon is hidden from the user.

User group rights to global and administrative functions - reports
Function | Selection | Description
--- | --- | ---
Global function: Reports |  |
Results | Enabled | If marked, the user group can see the Results workspace for the selected controller. If unmarked, the icon is not visible in ToolsTalk 2
Events | Enabled | If marked, the user group can see the Events workspace for the selected controller If unmarked, the icon is not visible in ToolsTalk 2

User group rights to global and administrative functions - system administration
Function | Selection | Description
--- | --- | ---
Global function: System administration |  |
Schedule export and import | Enabled | If marked, the user group can see and configure parameters for scheduling export and import of configurations and parameters. If unmarked, the icon is not visible in ToolsTalk 2
Controller software and data management | Enabled | If marked, the user group can see and configure software updates for selected controllers. If unmarked, the icon is not visible in ToolsTalk 2
Functionality management system | Enabled | If marked, the user group can manage licensed functionality and load and remove functionality from selected controllers. If unmarked, the icon is not visible in ToolsTalk 2
User group administration | Enabled | If marked, the user group can see and configure user group user rights. If unmarked, the icon is not visible in ToolsTalk 2
program Approval | Enabled | If marked, the user group can send programs for approval and also approve or reject a program. If unmarked, the icon is not visible in ToolsTalk 2.

User group rights to global and administrative functions - system administration
Function | Selection | Description
--- | --- | ---
Global function: Library |  |
Controller configuration library Program library Configuration library Fieldbus library | Read | If marked, the user group can see and read parameters in the library. If unmarked, the icon is not visible in ToolsTalk 2
Controller configuration library Program library Configuration library Fieldbus library | Update | If marked, the user group can see and edit parameters in the library. Controllers that subscribe to the library are automatically updated.
Controller configuration library Program library Configuration library Fieldbus library | Create & Delete | If marked, the user group can create, edit and delete configurations in the library. Controllers that subscribe to the library are automatically updated.
Controller configuration library Program library Configuration library Fieldbus library | Distribute | If marked, the user group can create, edit and delete configurations in the library. Controllers that subscribe to the library are automatically updated. In addition, the distribute user rights allows the user group to distribute global configurations to controllers that previously have not subscribed to library configurations. Global configurations will be created in affected controllers.

# Program Approval

This section describes the approval process for tightening or loosening programs. The program approval is managed by a user with approval privileges.

Relevant Information

- User Group Permissions Menu

In this Section

- Sending a Program for Approval
- Program Approval Workspace

# Sending a Program for Approval

1. Select a controller in the Plant structure workspace .

2. On the toolbar, select Tightening program .

   The Tightening program overview shows a list of tightening programs.

3. Select the check box for the program/programs that needs to be sent for approval.

   Only programs that have been pushed to the controller can be sent for approval.

4. Select Manage, enter comments if any in the Comment field and then select Send for approval.

   The maximum allowed number of characters allowed in the comments section is 255 including spaces.

   If you select multiple programs and enter comments in the comment section, only the common comments that is applicable to the selected programs are visible. To see a full list of comments that might be applicable to the program, select the program individually .

   The program/programs are now visible and ready to be approved or rejected in the Program Approval tab under System administration .

Copying and pasting a tightening program does not copy the approval statuses. The copied program will have the status Undefined.

Relevant Information

- Global Functions User Rights

# Program Approval Workspace

1. Go to System administration and select Program Approval .

   The Program Approval overview shows a list of controllers which have pending program approvals.

2. Select the controller to expand and see the list of programs.

Column | Description
--- | ---
Check box | Select a program by marking the check box.
Name | Name of the tightening or loosening program.
Last Changed | Last changes made, expressed in ToolsTalk 2 time.
Changed By | Indicates which user made the last changes.
Last Approved | Last approval to the program, expressed in controller time.
Last Approved By | Indicates which user last approved the program.
Approval Status | Approval status of the program.
Comment | Displays any comments added by user while sending the program for approval. Due to size restrictions, it is possible only to see few comments on the workspace. To see all the comments added, go to Manage -> Comment and if there are many comments, they are visible through a scrollable list.

In this Section

- Approval Statuses
- Approving or Rejecting a Program

# Approval Statuses

Status | Description
--- | ---
Approved | The program is approved and may be used on the controller. The program will be read-only.
Draft | The program is being changed/optimized. The program can be sent for approval once it is finalized. The program will be editable.

All programs can be used irrespective of the approval statuses. Approval statuses do not affect operational function of any programs.

Once a program enters the approval workflow, it will always have a status.

# Approving or Rejecting a Program

Only users with program approval user rights can approve or reject a program that is sent for approval. This feature is only available in licence level Line Manager.

User rights are determined in the User groups tab in System administration .

1. Go to System administration and select Program Approval .

   The Program Approval overview shows a list of controllers which have pending program approvals.

2. Select the controller to expand and see the list of programs.

3. Mark the checkbox for the program you would like to approve/reject.

4. Select Manage and select Approve or Reject and add any comments as required in the Comment field.

   The maximum allowed number of characters allowed in the comments section is 255 including spaces.

   Approval, rejection, and adding comments can be also done by selecting the program/multiple programs + Right click.

   Approve and Reset to draft can be done in the program approval tab, in the plant structure and in the library.

## Comments

Comments can be added while approving or rejected a program but can also be added in the following ways:

- Select the relevant program/programs + Right click and select Comment.

- Select the relevant program/programs and select Manage and then select Comment.

The maximum allowed number of characters allowed in the comments section is 255 including spaces.

If you select multiple programs and enter comments in the comment section, only the common comments that is applicable to the selected programs are visible. To see a full list of comments that might be applicable to the program, select the program individually .

## Configuration Approval History

It is possible to see the approval history of a program.

- Select the relevant program/programs + Right click and select History.

- Select the relevant program/programs and select Manage and then select History.

The Configuration Approval History window opens and if the program has been approved before, the following details are shown:

- Name

- Last Approved

- Last Approved By

- Approval Status

- Comment

The Comment field with the history of all comments is also visible and is non-editable.

Relevant Information

- Global Functions User Rights

# Reports and Statistics

In this section, you can learn about available reports and statistics.

# Working with the Results Tab

ToolsTalk 2 has the capability to show more detailed tightening results than the controller GUI.

Tightening results from the controller are automatically sent from the controller to ToolsTalk 2 as soon as the tightening is finished.

The controller has also the option to send the tightening results to ToolsNet 8 for further processing and statistical analysis.

In ToolsTalk 2 it is possible to view the results and to create reports from one controller at a time. Each task is displayed as one result. A single tightening can show results in a table with key parameters or as a tightening graph. A batch sequence shows all the individual tightenings in the order in which they were performed.

Statistical analysis, result filtering and tightening analysis can be performed using ToolsNet 8. More information on how this is done is described in the ToolsNet 8 documentation.

Icon | Description
--- | ---
| The workspace area shows tightening results from the selected controller. The results can be shown both in table format and in graphical traces.

Results can only be sent and displayed while there is an active connection to the server. If tightenings are performed while the server is offline, then these results will not be transmitted to ToolsTalk 2 during this period.

In this Section

- Handling Results
- Searching for Results
- Filtering Results
- Exporting Results
- Importing Results
- Synchronized Tightening Results

# Handling Results

Latest results tab - Shows the results for the latest tightenings.

Search Results tab - Use the Search button to search for results between specific dates.

Pinned tab - For investigation.
A tightening result can temporarily be stored into the Pinned tab. This is useful for detailed analysis of a tightening, and prevents the tightening result to be dropped from the window as new results are received.

Live results tab - A controller sends tightening results to ToolsTalk 2 as soon as the task is completed, and the result is added to the top of the Live results. A limited number of results can be stored. When the list is full, the oldest result is dropped from the list.

Imported results tab - For viewing imported results.

## Pinned - Holding area for investigation

Tightening results can temporarily be stored into the Pinned area. This is useful for detailed analysis of a tightening, and prevents the tightening result to be dropped from the window as new results are received.

- Manually: On a result, select the Pin icon.

  The tightening result is copied to the Pinned area for investigations. It is possible to pin several results to the temporary storage.

- Automated: Select the Auto pin drop-down menu and enter number of results to be pinned. Select Start. The next incoming result will be pinned automatically, continuing until the entered number has been reached, or until pressing Stop.

Remove all results from the pinned area

To remove individual results, unpin it by selecting the Pin icon .

## Live results

A controller sends tightening results to ToolsTalk as soon as the task is completed, and the result is added to the top of the Live results. A limited number of results can be stored. When the list is full, the oldest result is dropped from the list.

Each line in the list represents one task and can be a single tightening or a batch sequence, depending on the selected task. Expand the list to view a more detailed information about each tightening.

Use the arrows to expand the overview result to a more detailed result view or to collapse the view to only show the overview result.

Column | Description
--- | ---
Red bar | The leftmost position in the Live results table may contain a red bar icon , indicating erroneous tightenings for quick identification of errors. This corresponds to NOK.
Holding pin | Select the holding pin icon to pin the result to the pinned tab.
Trace | Select the trace icon to view a graphical view of the results in the Trace workspace.
Save icon | This command creates a .csv file with the trace data. A dialog window is opened as to save the file in a desired location, where it can later be imported from.
Overall Status | OK or NOK. NOK is always in combination with the red bar icon, to quickly identify erroneous tightenings. Incomplete tightenings will have the word Stopped next to the result.
Type of task | Shows if the performed task is a single tightening or a batch sequence.
Virtual station name | Name of the virtual station.
Scan sequence | If a scanner was used to select the task, the scanned sequence is shown. Otherwise the column is empty.
Task name | The name of the tightening or the batch sequence.
Time Stamp | Time stamp for the tightening, that is, time and date.

Live result details
Result parameter | Description
--- | ---
Trace | Select the trace icon to view a graphical view of the results in the Trace workspace.
Save | This command creates a .csv file with the trace data. A dialog window is opened as to save the file in a desired location, where it can later be imported from.
Status | This column can show either OK or NOK. NOK is always shown in combination with red text in the ToolsTalk 2 user interface.
Status info | Additional tightening information.
Tightening name | The name of the tightening.
Torque Low Limit | The Low limit which is set in the Step Monitor Peak Torque, that reports Final Torque.
Final Torque | Final Torque for the tightening. It is the Step Monitor Peak Torque located in the last tightening step that reports this Parameter.
Target Torque | The Target Torque will show the Target Torque value configured for the tightening strategy, which is used to perform the tightening.
Torque High Limit | The High limit which is set in the Step Monitor Peak Torque, that reports Final Torque.
Rundown Angle | If rundown is enabled there will be a Rundown Angle value presented in the result.
Angle Low Limit | The Low limit which is set in the Step Monitor Angle, that reports Final Angle.
Final Angle | The actual measured angle of the last tightening step It is the Step Monitor Peak Angle located in the last tightening step that reports this parameter.
Target Angle | The Target Angle will display the Target Angle value configured for the tightening strategy, which is used to perform the tightening.
Angle High Limit | The High limit which is set in the Step Monitor Angle, that reports Final Angle.
TrueAngle Compensation | The TrueAngle compensation will display the compensated angle.
Start Final Angle | The Start Final Angle will display the torque value from where the Final Angle was initiated.
Primary error | Primary error of why the result is NOK.
Failing Step | Indicates the number of the step that detected the first error in case of a NOK tightening.
Batch | The column is only displayed if the task is a batch sequence. The number indicates the order number of the batch within the batch sequence.
Batch count | The column is only displayed if the task is a batch sequence. The number indicates the order number of the tightening within the batch.
Angle and Torque results | Numeric value. Only shown if used as a target value or as a limit value.
Errors | Shows all errors.
Elapsed time | Time from tightening start to end.
Detailed status | For NOK results, additional information about the error is shown.

## Result Reporter

The list shows the values from the result reporters. If there is a result reporter defined for a program monitor/restriction, the value from that monitor/restriction is reported. If there is no result reporter defined for a program monitor/restriction, the value from the latest executed step in main path with a reporter is reported.

## Monitors / Restrictions results for multistep

Each step in the multistep tightening program reports data. Most of this data is coming from the monitors and restrictions that are active during the step, so the data is only reported if a monitor or restriction of the correct type is configured.

Step results
Step Result Parameter | Description
--- | ---
Step | The number of the step.
Status | Status of the step, OK or NOK.
Step type | Step type in the multistep program.
Step category | For each step, there is an option to choose a step category. These categories can be customized. By selecting step category, the NOK tightenings will be listed in the event result view with related detailed status together with the corresponding multistep error information. If no selection is made, the detailed status will be set to "uncategorized multistep error".
Primary error | Primary error of why the result is NOK.
Elapsed time | Time from tightening start to end.
Errors | Shows all errors.

## Trace

On a result click on the Trace icon if it is active. . The result graph is displayed. It is possible to view several traces simultaneously by selecting several traces.

The Trace workspace shows detailed graphical information on one or several tightening result.

On the workspace, use the mouse wheel to zoom in or zoom out. Or you can select an area to zoom in. Double click the trace area to go back.

Examples:

Select an area to zoom in:

To move the trace, press the wheel button of the mouse:

In the trace graph, delta information based on the selected axis types can be displayed. Right click the two points you want to compare to show the delta between them. Drag the point to modify the target.

Drag the delta to move it or press Delete to delete it.

Trace settings | Description
--- | ---
Limits | Possible to select and show Torque limits and Angle limits, if Torque or Angle limits are used in the tightening program. Torque over Angle trace need to be selected to view the limits. Possible to select and show Post view torque limits if Post view torque has been configured in the tightening program.
Chart | Possible to select Grid lines and Axis labels to show up in the tightening trace view.
Min/Max | Select to show minimum or maximum measured value.
|X-Axis| | Select to show the absolute value for X-axis.
Y1 | Select the information to show in the Y1-axis: Torque Angle Speed Current Gradient
Y2 | Select the information to show in the Y2-axis: None Torque Angle Speed Current Gradient
Y3 | Select the information to show in the Y3-axis: None Torque Angle Speed Current Gradient
X | Select the information to show X-axis: Time Angle

Traces can be synchronized by X-axis offset with different options. Trace synchronization is available when there are two or more trace results selected.

Sync Options | Description
--- | ---
None | No offset is set to any trace
Manual | (Only available when there are two trace results selected) Synchronize the traces to any synchronization point by manually dragging the lower scale of the X-axis.
Peak | Synchronizes the traces by their absolute peak values.
Set Value | Synchronizes the traces by a specific value: Torque: Offset all traces so that the angles or times of the first time the traces reaches this torque value coincide. Angle: Offset all traces so that the angles or times of the first time the traces reaches this angle value coincide. Speed: Offset all traces so that the angles or times of the first time the traces reaches this speed value coincide. Current: Offset all traces so that the angles or times of the first time the traces reaches this current value coincide. Gradient: Offset all traces so that the angles or times of the first time the traces reaches this gradient value coincide.
Measurement Point | Synchronizes the traces by a specific measurement point: Rundown Complete (CATLA) First Target (CATLA)

Buttons | Description
--- | ---
Remove all Δ | Remove all the deltas.
Export... | Exports the trace chart view to the following targets: JPEG / PNG image System printer
Remove all | This button clears the trace plot area.

# Searching for Results

Use the Search function to search for results between specific dates.

1. Go to the Results tab .

2. Select the sub-tab Search Results.

3. Select the Search... button to open the Result search settings dialog.

4. In Date range, select either a from and to date on the calendar, or a predefined range via the drop-down. Select Search when ready.

5. Search results will be displayed in the sub-tab Search Results, for further action or analysis.

Switching between controllers will clear the results from the Search Results sub-tab.

# Filtering Results

Results can be filtered by Status, Virtual Station, Task and free texts.

1. Go to the Results tab .

2. Select the sub-tab for the results.

   Live results cannot be filtered.

3. In the navigation panel below the result list, select filtering criteria to filter the results in the view.
   The free texts search on the names of Virtual Station and Task.

Filtered results will be displayed.

# Exporting Results

Export to a spreadsheet, select the source and number of results to export. All the details from one or more tightenings can be exported.

1. Select the Export button.

2. Select where to export from:

   - Export from latest: Exports a selected amount of results from the last received results.

   - Export from pinned: Exports a selected amount of results from the temporary storage area.

   - Export from controller: Exports a selected amount of results from the controller.

   - Amount of results: Enter number (amount) of results to export. The results are first taken from the top of the list and then downwards.

3. Select Export.

4. A dialog box opens for selecting the storage location.

5. Select Save.

# Importing Results

1. Select the Import button.

2. In the dialog window, select the .csv file to be imported.

3. Select Open.

4. The imported trace is added to the list in the Imported tab.

# Synchronized Tightening Results

The tightening results are displayed in a condensed list that can be individually or collectively chosen for further analysis.

For each controller, a maximum of 1024 latest received results can be stored in the ToolsTalk database. When the controller is offline, the results occurring during this time will not be transferred to ToolsTalk when the controller returns online.

Select Show only NOK results at the bottom of each page to only view the results with NOK status.

On the top level the result for a synchronized tightening with several channels contain the following information:

Tightening result

GUI part | Description
--- | ---
Red bar | The leftmost position in the Live results table may contain a red bar icon. This is shown together with erroneous tightenings for quick identification of errors. This corresponds to NOK.
Holding pin | Select the holding pin icon to pin the result to the pinned tab.
Trace icon | Select the trace icon to view a graphical view of the results in the Trace workspace.
Save icon | This command creates a .csv-file with the result data. A dialog window is opened as to save the file in a desired location.
Shunt calibration | Shown if shunt calibration is displayed.
Overall Status | Total status of the tightening, OK or NOK.
Type |
Virtual station name | Name of the virtual station.
Sync Mode Index and name | Index and name of the sync mode used in the tightening.
Time Stamp | Time stamp for the tightening, that is, time and date.

Channel result

For each channel an overall result is reported with the following content:

GUI part | Description
--- | ---
Trace | Select the trace icon to view a graphical view of the results in the Trace workspace.
Save | This command creates a csv-file with the result data. A pop-up dialogue window is opened to save the file at a desired location.
Bolt Name | The number and name of the bolt. Set in Sync Mode > “Name of the sync mode” > Bolt configuration > Bolt and Bolt name.
Status | Total status of the tightening, OK or NOK.
Status Info | Status information
Program | The tightening program. Set in Tightening and Multistep Program > “Name of the tightening program” > Basic settings > Name.
Channel | The channel number.
Target Angle | The Target Angle will display the Target Angle value configured for the tightening strategy, which is used to perform the tightening.
Final Angle | The actual measured angle of the last tightening step It is the Step Monitor Peak Angle located in the last tightening step that reports this parameter.
Final Torque | Final Torque for the tightening. It is the Step Monitor Peak Torque located in the last tightening step that reports this Parameter.
Target torque | Target torque.
Elapsed time | Time from tightening start to end.
Mode | Mode Name/Number
Shunt calibration | Select this icon to display the shunt calibration data.

Step results

Each step in the multistep tightening program reports data. Most of this data is coming from the monitors and restrictions that are active during the step, so the data is only reported if a monitor or restriction of the correct type is configured.

The same step may be executed more than once if repairs are made.

Result Parameter | Description
--- | ---
Step number | The number of the step.
Status | Status of the step, OK or NOK.
Step type | Step type in the multistep program.
Path | Indicates where in the program the step is located, that is, if it is in the tightening path, a repair, or a termination path.
Peak Torque | Measured final torque including the torque induced during the internal break. Typically the peak torque is higher than the shut-off torque.
Elapsed time | Time from tightening start to end.
Angle | Displays the angle
Click Torque | Displays the Click Torque
Click Angle | Displays the Click Angle

## Result Reporter

The list shows the values from the result reporters. If there is a result reporter defined for a program monitor/restriction, the value from that monitor/restriction is reported. If there is no result reporter defined for a program monitor/restriction, the value from the latest executed step in main path with a reporter is reported.

## Trace

On a result click on the Trace icon if it is active. . The result graph is displayed. It is possible to view several traces simultaneously by selecting several traces.

The Trace workspace shows detailed graphical information on one or several tightening result.

On the workspace, use the mouse wheel to zoom in or zoom out. Or you can select an area to zoom in. Double click the trace area to go back.

Examples:

Select an area to zoom in:

To move the trace, press the wheel button of the mouse:

In the trace graph, delta information based on the selected axis types can be displayed. Right-click the two points you want to compare to show the delta between them. Drag the point to modify the target.

Drag the delta to move it or press Delete to delete it.

Trace settings | Description
--- | ---
Limits | Check this box to If one curve is shown, limit values can be shown if they are used in the tightening program.
Gridlines | Check this box to show the gridlines in the result graph.
Min/Max | Show minimum or maximum measured value.
|X-Axis| | Show the absolute value for X-axis.
Y1 | Choose the information to be shown in the Y1-axis: Torque Angle Speed Current Gradient
Y2 | Choose the information to be shown in the Y2-axis: None Torque Angle Speed Current Gradient
Y3 | Choose the information to be shown in the Y3-axis: None Torque Angle Speed Current Gradient
X | Choose which information to be shown X-axis: Time Angle

Traces can be synchronized by X-axis offset with different options. Trace synchronization is available when there are two or more trace results selected.

Sync Options | Description
--- | ---
None | No offset is set to any trace
Manual | (Only available when there are two trace results selected) Synchronize the traces to any synchronization point by manually dragging the lower scale of the X-axis.
Peak | Synchronizes the traces by their absolute peak values.
Set Value | Synchronizes the traces by a specific value: Torque: Offset all traces so that the angles or times of the first time the traces reaches this torque value coincide. Angle: Offset all traces so that the angles or times of the first time the traces reaches this angle value coincide. Speed: Offset all traces so that the angles or times of the first time the traces reaches this speed value coincide. Current: Offset all traces so that the angles or times of the first time the traces reaches this current value coincide. Gradient: Offset all traces so that the angles or times of the first time the traces reaches this gradient value coincide.
Measurement Point | Synchronizes the traces by a specific measurement point: Rundown Complete (CATLA) First Target (CATLA)

Buttons | Description
--- | ---
Remove all Δ | Remove all the deltas.
Export... | Exports the trace chart view to the following targets: JPEG / PNG image System printer
Remove all | This button clears the trace plot area.

Latest results tab

Displays the results for the latest tightenings.

Search Results tab

Use the Search button to search for results between specific dates.

Pinned tab for investigation

A tightening result can temporarily be stored into the Pinned tab. This is useful for detailed analysis of a tightening, and prevents the tightening result to be dropped from the window as new results are received.

Live results tab

A controller sends tightening results to ToolsTalk 2 as soon as the task is completed, and the result is added to the top of the Live results. A limited number of results can be stored. When the list is full, the oldest result is dropped from the list.

Imported tab

For viewing imported results.

## Shunt Calibration

Shunt calibration is an electrical check of a transducer. The transducer is checked for offset and shunt calibration at the start of each cycle. Shunt calibration limits can be adjusted.

In ToolsTalk 2, the limits can be seen—but not changed—in Plant structure > Tools. Select a tool that can display offset and shunt-calibration values in the Zero Offset and Shunt Limits section.

To change offset and shunt values, access the tool display from a web browser. For more information, see the user guide or product information for the tool.

The shunt calibration results in different metrics:

Parameter | Unit | Description
--- | --- | ---
Multistep Name | [text field] |
Gain | Nm | Measured value from a shunt calibration test.
Gain Difference | Nm | The change in the measured gain value since the last test.
Gain Limit High | Nm | The limits for the measured gain to be acceptable.
Gain Limit Low | Nm | The limits for the measured gain to be acceptable.
Gain Max Change | Nm | The limit for the gain difference to be acceptable.
Offset | Nm | The measured zero offset, the torque reading at rest.
Offset Difference | Nm | The change in the measured offset value since the last test.
Offset Limit High | Nm | The limits for the measured offset to be acceptable.
Offset Limit Low | Nm | The limits for the measured offset to be acceptable.
Offset Max Change | Nm | The limit for the offset difference to be acceptable.
Shunt Failed | True or false | The value is true if the gain or gain difference is outside of limits.
Zero Offset Failed | True or false | The value is true if the offset or the offset difference is outside of limits.

Relevant Information

- Exporting Results
- Importing Results

# Working with the Events Tab

Controller events are displayed according to the configurations made in the Settings tab, in the sub-menu Events.

Events that are logged by the controller can be viewed in the list in the Events tab .

Only logged events will be displayed in the event list.

Viewing Controller Events

1. Select a controller in the Plant structure .

2. Go to the Events tab.

The workspace area provides different views of tightening results and some options to display details.

Controller event description
Column | Description
--- | ---
Severity | The severity is identified by icons: - Error - Warning - Information
Date and Time | Time stamp when the event occurred, expressed in controller time.
Code | Event code identification.
Description | Event code description.
Details | Event details.
Virtual Station | Virtual Station name.
Group | System description.

Relevant Information

- Events Menu

In this Section

- Severity Types

# Severity Types

Events are divided into three categories; Information, Warning and Error.

## Information Event

Information events signal a noteworthy event that has occurred from actions performed by the user or the system. Information events do not require any specific user actions.

## Warning Event

Warning events signal a potentially serious condition that could affect the system performance or result in injury.

## Error event

Error events signal a serious condition, such as a failed service, that almost exclusively requires the user to make changes to the setup or the configuration in order to continue.

# Working with the Statistics Tab

Only valid for PF6000 and PF8.

ToolsTalk 2 provides Statistical Process Control (SPC) function to handle SPC configuration of the controller and presentation of SPC result data from the statistical calculations in terms of charts. The statistical calculations are performed on controller and the results are provided to ToolsTalk 2 for presentation in the ToolsTalk 2 client.

By configuring the SPC function within the controller, it is possible to simplify and do the work directly on the controller without the need of external software. The charts data are generated on the controller.

Statistical calculations are based on tightening results stored in the controller.

Statistical calculations are done on a Virtual Station level, depending on the tightening program selected and used for that specific Virtual Station.

In this Section

- Configuring SPC Parameters
- Configuring SPC Variables
- Calculating Statistics
- Viewing Statistical Results

# Configuring SPC Parameters

1. Select a controller in the Plant Structure workspace and then select Statistics in the menu bar.

2. In the Configuration section, enter the following parameters to specify how to select tightening results for the statistical calculations:

   Variable Configuration
   Information | Description
   --- | ---
   Number of Subgroups | The number of subgroups the statistical calculation is based upon.
   Subgroup Size | The number of samples (tightening results) in each subgroup. The Subgroup Size can range from 2 through 25.
   Frequency | The interval between the subgroups. Frequency must be equal to or higher than Subgroup Size.

   The total number of results (Number of Subgroups × Frequency) can range from 2 through 500.

   For instance, if Frequency is 8 and Subgroup Size is 5, the first 5 data (results) is used for the subgroup. Because of the Frequency =8, the next subgroup starts considering data (results) from the 8th one on, and so on in a loop.

# Configuring SPC Variables

1. Select a controller in the Plant Structure workspace and then select Statistics in the menu bar.

2. The Variable Configuration section contains a list of a Variable Configurations.

   - To create a Variable Configuration, select Add... at the upper-right corner of the section.

   - To delete a Variable Configuration, select the configuration (you can also select more than one configuration) and then select Modify > Delete at the upper-right corner of the section.

   - To update a Variable Configuration, double click the configuration.

Variable Configuration
Information | Description
--- | ---
Name | The name of the variable.
Virtual Station | The Virtual Station that the tightening results are generated from.
Tightening Program | The multistep tightening program of the variable. The Tightening Program must be a Multistep Program.
Monitor | Select the aspect of the tightening result you want to monitor in the calculation: Step monitor peak torque Step monitor angle Final torque Final angle Program monitor torque Program monitor angle If the user uses the result reporters, it is possible to have an effect on the following monitor values: Final torque and Final angle.
Step Number | Specifies the step number. (Only available when Step monitor peak torque or Step monitor angle is selected for Monitor.)

Set the following limits:

Tolerance Limits
Information | Description
--- | ---
Lower Tolerance Limit | Lower tolerance limit for monitored value. Used for calculation of Cp, Cpk values as well as for tolerance limits rendering in SPC results charts.
Upper Tolerance Limit | Upper tolerance limit for monitored value. Used for calculation of Cp, Cpk values as well as for tolerance limits rendering in SPC results charts.

Capabilities
Information | Description
--- | ---
Cp | The process capability. The number of times the spread of the process is into the tolerance width (Upper tolerance limit - Lower tolerance limit). The higher the value of Cp, the better the process.
Cpk | The process capability corrected for the position. It is not useful having a high Cp index if the process setting is way off center in relation to the middle of the tolerance range. A high Cpk index means, then, that you have a good process with a small spread in relation to the tolerance width, and also that it is well centered within that width (Upper tolerance limit - Lower tolerance limit). If Cpk is equal to Cp, the process is set to produce exactly in the middle of the tolerance range.

Control Limits
Information | Description
--- | ---
Auto calculate | If set to On, the control limits are automatically calculated. If set to Off, set the following limits: Mean Range Sigma
Upper control limit | Upper control limit for calculated subgroup values. Used for limits rendering in SPC results charts.
Lower control limit | Lower control limit for calculated subgroup values. Used for limits rendering in SPC results charts.

# Calculating Statistics

1. Select a controller in the Plant Structure workspace and then select Statistics in the menu bar.

2. In the Configuration section, enter the parameters to collect results stored in the controller (Number of Subgroups, Subgroup Size, and Frequency).

3. In the Variable Configuration section, double click the variable configuration you want to calculate.

4. In the variable configuration page, select Calculate at the upper-right corner.

When a statistical calculation is done, the result is sent to the Web HMI and to ToolsTalk 2.

If Calculate is disabled, make sure that:

- the controller is online.

- SPC configuration is in sync with controller.

- the user is authorized to update the controller.

It is not possible to calculate statistics for results from deleted tightening programs or Virtual Stations, unless the results are still stored on the controller.

## Statistics Formulas

Data in a subgroup is calculated as:

- Average:

- Range = R = max (Xi) - min (Xi), where i=1...n

- Standard deviation for a subgroup:

- Total overall of the standard deviation:

  Where N = total number of observations.

When specified number of subgroups to use for calculations has been collected, the SPC function starts calculations to determine the statistical stability.
Calculations are performed through the following steps: (m = number of subgroups)

- Calculation of Average of Average values:

- Calculation of Average of Range:

- Calculation of Average of Standard deviation:

- Calculation of the process capabilities Cp and Cpk with respect to Sigma:

  Where:

  - is the overall arithmetic average of the observed characteristic values.

  - UTL is the Upper Tolerance Limit.

  - LTL is the Lower Tolerance Limit.

  - The sigma estimation is the mean square standard deviation within the subgroups:

- Calculation of the process capabilities Cp and Cpk with respect to Range:

  Where for a normal distribution su = sl = 3.

Calculations for control limits if, in the SPC Configuration section, the Auto calculate switch is set to Yes:

- X-bar R (Mean)

- X-bar R (Range)

- X-bar S (Mean)

- X-bar S (Sigma)

A2, A3, D3, D4, B3, and B4 are constants (for more information, see the "SPC Calculation Constants" paragraph).

## SPC Calculations Constants

Subgroup Size | Divisors for estimate of standard dev. | Factors for Control Limits
--- | --- | ---
|  | Xbar R | Xbar S
A2 | D3 | D4 | A3 | B3 | B4
n | d2
2 | 1.128 | 1.880 | - | 3.267 | 2.659 | - | 3.267
3 | 1.693 | 1.023 | - | 2.574 | 1.954 | - | 2.568
4 | 2.059 | 0.729 | - | 2.282 | 1.628 | - | 2.266
5 | 2.326 | 0.577 | - | 2.114 | 1.427 | - | 2.089
6 | 2.534 | 0.483 | - | 2.004 | 1.287 | 0.030 | 1.970
7 | 2.704 | 0.419 | 0.076 | 1.924 | 1.182 | 0.118 | 1.882
8 | 2.847 | 0.373 | 0.136 | 1.864 | 1.099 | 0.185 | 1.815
9 | 2.970 | 0.337 | 0.184 | 1.816 | 1.032 | 0.239 | 1.761
10 | 3.078 | 0.308 | 0.223 | 1.777 | 0.975 | 0.284 | 1.716
11 | 3.173 | 0.285 | 0.256 | 1.744 | 0.927 | 0.321 | 1.679
12 | 3.258 | 0.266 | 0.283 | 1.717 | 0.886 | 0.354 | 1.646
13 | 3.336 | 0.249 | 0.307 | 1.693 | 0.850 | 0.382 | 1.618
14 | 3.407 | 0.235 | 0.328 | 1.672 | 0.817 | 0.406 | 1.594
15 | 3.472 | 0.223 | 0.347 | 1.653 | 0.789 | 0.428 | 1.572
16 | 3.532 | 0.212 | 0.363 | 1.637 | 0.763 | 0.448 | 1.552
17 | 3.588 | 0.203 | 0.378 | 1.622 | 0.739 | 0.466 | 1.534
18 | 3.640 | 0.194 | 0.391 | 1.608 | 0.718 | 0.482 | 1.518
19 | 3.689 | 0.187 | 0.403 | 1.597 | 0.698 | 0.497 | 1.503
20 | 3.735 | 0.180 | 0.415 | 1.585 | 0.680 | 0.510 | 1.490
21 | 3.778 | 0.173 | 0.425 | 1.575 | 0.663 | 0.523 | 1.477
22 | 3.819 | 0.167 | 0.434 | 1.566 | 0.647 | 0.534 | 1.466
23 | 3.858 | 0.162 | 0.443 | 1.557 | 0.633 | 0.545 | 1.455
24 | 3.895 | 0.157 | 0.451 | 1.548 | 0.619 | 0.555 | 1.445
25 | 3.931 | 0.153 | 0.459 | 1.541 | 0.606 | 0.565 | 1.435

# Viewing Statistical Results

1. Select a controller in the Plant Structure workspace and then select Statistics in the menu bar.

2. After calculating the statistics, the statistical results can be viewed in the Results tab.
   The statistical results are displayed by different charts: HISTOGRAM, XBAR-R, and XBAR-S.

   The statistics result is not stored on the controller or in ToolsTalk 2, but ToolsTalk 2 holds up to 10 of the latest statistical results per controller in memory.

## Histogram

The histogram chart shows the frequency of the monitored aspect for a number of classes, together with the target, a Normal Distribution curve and a number of limits.
The histogram is a series of bars, each proportional in width to the range of values within a class and proportional in height to the number of samples falling in the class. A histogram reveals the amount of variation that any process has within it. The histogram is useful because it emphasizes and clarifies trends that are not readily discernible in tables.

Legend Item | Description
--- | ---
Normal Distribution | A Gaussian curve calculated from the samples collection. Shows the theoretical distribution of the samples, based on statistical calculations and probability.
Mean | The overall mean value of the samples collection.
+/- 3 Sigma | Part of the definition of the Normal Distribution, stating that 99.7% of the samples collection is expected to be between +/- 3 standard deviations from the Mean value.
Target | The tightening program target value.
Tolerance limits | Defined in the SPC Variable Configuration.

## XBar-R

The XBar-R control charts show both the mean value (XBar) and the range (R) for each subgroup. This is the most common type of control chart using indiscrete or continuous values. The XBar part of the chart shows any changes in the mean value of the process while the R part shows any changes in the dispersion of the process.
This chart is particularly useful because it shows changes in mean value and dispersion of the process at the same time, making it a very effective method for checking abnormalities in the process.

Legend Item | Description
--- | ---
Mean | The overall mean value for the samples collection.
Control limits | Defined in the SPC Variable Configuration. Can be auto-calculated or manual.
Target | The tightening program target value.
Centerline | The mean range of the subgroups.

## XBar-S

The XBar-S control charts show both the mean value (XBar) and the standard deviation (S) for each subgroup.
The XBar-S chart is identical to the XBar-R chart except that the XBar-S shows the standard deviation instead of range.

Legend Item | Description
--- | ---
Mean | The overall mean value for the samples collection.
Control limits | Defined in the SPC Variable Configuration. Can be auto-calculated or manual.
Target | The tightening program target value.
Centerline | The mean range of the subgroups.

## Calculated Statistical Values

A number of calculated statistical key values are displayed in information boxes below the histogram, the XBar-R chart, and the XBar-S chart.

The calculated statistical values are:

- Min = minimum value for all collected sample values

- Max = maximum value for all collected sample values

- Mean =

- Mean+3Sigma = + 3*stdDev

- Mean-3Sigma = - 3*stdDev

- Cp (in XBar-R chart the value is based on range, and in XBar-S chart the value is based on sigma)

- Cpk (in XBar-R chart the value is based on range, and in XBar-S chart the value is based on sigma)

- Center line = in Range part , and in Sigma part

- Target (if available the target value for the monitor)

- Standard deviation = Total overall standard deviation = stdDev

# Adding Controller Event Notifications

This section explains how to enable notifications for different controller events. If you want to receive notifications for a particular controller event, the Log and Display checkbox should be ticked for those events in the Events sub-tab in the Settings menu.

1. Select in the top right corner of the workspace.

2. In the ToolsTalk 2 User Settings dialog box, you can choose to switch Off all notifications or enable the following notifications:

   - Show All

   - Show Errors and Warnings

   - Show Errors Only

3. Select Save and Close.

   Based on what controller events are enabled (Log and Display boxes ticked) in the Settings/Events menu and the value selected in the ToolsTalk 2 User Settings (Errors, Warnings or both), all the events that are received from the connected controllers are displayed in the Controller Events Notifications window as and when they are received.

   Select a controller in the list to expand and see all the notifications related to that controller.

   Each notification has the following values described:

   Item | Description
   --- | ---
   Severity | The severity is identified by icons: - Error - Warning - Information
   Code | Event code identification.
   Description | Event code description.
   Date and Time | Time stamp when the event occurred, expressed in controller time.
   Group | System description.

Relevant Information

- Event Configuration
- Severity Types

# Troubleshooting and Service

This section provides assistance in troubleshooting problems, should they arise, and contains information to help you maintain and service the product.

# Troubleshooting During Installation

Restart the ToolsTalk Industrial Technique Host service after upgrading ToolsTalk 2.

Error | Solution
--- | ---
Error code 1920 Failed to start. Verify you have correct permission | Database authentication error. For the SQL database mixed mode authentication must be configured. Use the SQL management studio to correct the authentication. A restart of the computer is most likely needed before another installation attempt can be made.

The InstallShield Wizard detects if installations have already been made, when using an installation file. If older installations are present on the computer, they may not be detected.

It is therefore recommended to remove old instances of the program and of the database catalog before starting a new installation.

# Troubleshooting During Startup

Error | Solution
--- | ---
Application starts, but the desired controller is not seen. | Controller network connection is not correct. Make sure the controller is connected correctly to the factory network. Applicable if a network connection is used.
Application starts, but the desired controller is not seen. | Controller configuration to the ToolsTalk 2 is not correct. Make sure the server connections in the controller configuration point to the correct ToolsTalk 2 server.
Error message "Network connection lost or server unavailable" displayed when the ToolsTalk 2 is started. | The client application is not connected properly to the server application. Check that the server application has started. The application should start automatically. If this does not happen then a solution can be to remove the application (uninstallation) and reinstall the application.

Relevant Information

- System Information

# Reference

In this section, you can find miscellaneous useful information.

# System Information

Issue | Solution
--- | ---
Installation files | C:\Program Files (x86)\Atlas Copco\ToolsTalk Client C:\Program Files\Atlas Copco\ToolsTalk Server C:\Program Files (x86)\Atlas Copco\ToolsTalk Station Setup
Log file from the installation | In each installation folder is a log file named log.txt.
Computer IP address | Information needed for the controller configuration. Select the Windows start menu. Type cmd in the box in the bottom of the window and hit <return>. The administrator window opens. Type ipconfig and hit <return>. The IP address of the computer is displayed.
Computer name | Information needed for the client installation to point to correct server installation. Select the Windows start menu. Type or system information in the box in the bottom of the window and hit <return>. The system information window opens. The system name parameter is needed in the client installation to point to the location of the server.
Deleting database catalog | Start the management studio of the selected SQL server. Select the desired database catalog. The default name is ToolsTalkEventStore. Right-click and select Delete. Select the check box Delete backup and ....... Select the check box Close existing ....... Select OK.
Check and modify database authentication | Start the management studio of the selected SQL server. Select the desired server. Right-click and select Properties. Select Security page. In the server authentication field, mark the radio button labeled SQL server and windows authentication.
Installation of the Functionality Management System (FMS) | Only applicable in a client-server installation. The FMS installation is part of the InstallShield Wizard and runs automatically. For correct installation the system variable JAVA_HOME must have a correct value. Select the Windows start menu. Type System variables in the box in the bottom of the window. Several options are shown. Select Edit the system environmental variables. The system properties pop-up window opens. Select the Environment variables command button. Scroll down in the System variables window and search for the variable JAVA_HOME. If the variable is present, the value is the path to the 64-bit Java installation. If the variable is not present, select the New command button. A New system variable pop-up window opens. The variable name must be set to JAVA_HOME. The variable value must be set to the installation directory, for example C:\PROGRAM FILES\JAVA\JRE1.8.0_131. Do not include the BIN folder.
Check if the installation of the Functionality Management System (FMS) is correct. | Select the Windows start menu. Type Services in the box in the bottom of the window. Several options are shown. Select Services. The system properties pop-up window opens. Scroll down in the list and search for FlexNet License Server -acopco. If the Status indicates Started, the FMS is installed and is running.
Check if the ToolsTalk 2 server is installed and is running | Select the Windows start menu. Type Services in the box in the bottom of the window. Several options are shown. Select Services. The system properties pop-up window opens. Scroll down in the list and search for Atlas Copco Industrial Technique Host for ToolsTalk. If the Status indicates Started, the server is installed and is running.

# Helpful Hints

# Managing the Workspace Windows

The workspace for plant structure and reports both involve the selection of a single controller for further work. The workspace can be minimized or maximized to increase the space for the controller workspace by either, dragging as described and shown in the image below, or by selecting the Plant structure icon .

## Minimizing and Maximizing the Workspace View

1. Place the cursor on the line between the two workspace areas. The cursor shape changes from a white arrow to the shape of a horizontal double sided arrow.

2. Click-hold-drag and the border line between the two workspace area can be moved. The workspace can be maximized by moving the window border all the way to the left-side menu, or maximized by moving the window border to the right-side menu.

## Filtering and Sorting the Data Grid

The data grid columns in the workspace windows can be sorted and filtered.

1. Select a column header to access the sort and filter function.

2. To sort the list, select Sort list to arrange the list into ascending, descending, or default order.

3. To filter the list, select the check boxes to filter what is to be displayed. Select Clear filter to return to the default view.

## Search Functionality

It is possible to search for a specific content in the tabs in the Plant structure , Libraries and the System Administration tabs. This functionality is not available for the Scheduled Task and User Groups tabs in the System Administration tab.

1. Navigate to the main workspace of the particular tab where the data grid is displayed.

2. Enter the parameter you would like to search against in the Search bar seen in the top left corner of the workspace.

   The list narrows down, based on the parameters selected. For example, if you enter the parameter "Event", only the rows that contain the word "Event" is displayed.

## Multi-Sorting Functionality

It is possible to sort the data grid columns in an ascending or descending order (for example, based on index,alphabetical order and time and date and so on) and assign a priority for which column gets sorted first, second and so on.

1. Navigate to the main workspace of the particular tab where the data grid is displayed.

2. Select the present at the end of the header row of the data grid workspace.

3. Select the check box by the column name which you would like to first be sorted and then select the direction arrow to indicate if it should be ascending or descending. The arrow pointing up indicates ascending and the arrow pointing down indicates a descending order .

   For example, if you select Last Changed first, then the priority number 1 appears next to it and if you had selected the arrow pointing up, then the data in column Last Changed will be displayed with the latest time and date on the topmost row. The other columns will change the display order based on this selection. If another column is selected to be sorted next, then the priority number for that column will be displayed as 2 and the data in the column with priority 2 will be sorted based on the direction arrow after the data in column with priority 1 has been sorted and continues similarly for further columns selected.

4. To remove or change the priority of the columns, deselect the check boxes and/or make the selection again.

# File Formats For Export and Import

Export and import of controller configurations and results can be done from different places in the ToolsTalk 2 application. An export can also result in different file content.

- Export tightening results and events for further processing.

- Export log files for debug assistance from an Atlas Copco service engineer.

- Export controller configuration that can be used to copy settings to another controller.

An export of controller data can vary between controller type and between controller software version. For a detailed description of the file format and the file content, please refer to the documentation for each controller and version.

The tables provide a summary of the ToolsTalk 2 exports.

Export/import
Location | Path | File type and format | Usage
--- | --- | --- | ---
Controller library configuration |  | *.json | Export of controller configurations and to create controller templates. Used inside ToolsTalk 2.
Fieldbus configuration |  | *.json | Export of fieldbus configurations. Used to copy configurations. Used together with the import command. Used inside ToolsTalk 2.
Controller software and data management |  | *.tar.gz | Used to make a complete export of controller results and configurations from a controller. It is also possible to export Tool logs. Can be used to make imports of configurations and parameters of a previously exported file.
Scheduled controller export and import |  | *.tar.gz | Used to make a complete scheduled export of controller results and configurations from a controller. Can be used to make scheduled imports of configurations and parameters of a previously exported file.
Controller export and import |  | *.tar.gz | Used to make a complete scheduled export of controller results and configurations from a controller. Can also be used to make scheduled imports of configurations and parameters of a previously exported file. Used as an alternative route if user rights prevent access to the global icons.
Result export |  | *.csv | Used to only export tightening results from the controller
Controller software |  | *px2it.zip | Load new controller software.

Export locations and formats
File type and format | Usage
--- | ---
*.json | A file format used within the ToolsTalk 2. The files can be used to copy configurations and parameter settings. The file format can not be used by the ToolsTalk 2 application.
*.tar.gz | Used to make a complete export of controller results and configurations from a controller. The file format can not be used by the controller. The file can contain the following modules: A folder with configurations and parameters, that is used by a subsequent import. Several log and data files. Only used by Atlas Copco for debug information in case of error. *_events.csv. A result file listing the controller events. *_results.csv. A result file listing the controller tightening results.
*.csv | Used to only export tightening results or events from the controller. This file is included in the *.tar.gz file. The csv files uses different characters to separate the fields depending on the language setting in the controller. The fields can vary between controller software versions.
*px2it.zip | Only used to load controller software. Does not contain any configurations or parameter settings.

# Event Codes

Different types of events are used to notify the user of certain state changes or occurrences in the system. Each event requires a different action.

Some of the procedures described can only be performed by Atlas Copco Service personnel.

For more information about a specific event code, use the below filters or enter the event code search criteria in the search box.

Event Code
Event Type
Event Name
Description
Procedure
Log / Display / Ack / Conf
Available for
Group
Search

Event Code | Event Type | Event Name | Description | Procedure | Log / Display / Ack / Conf | Available for | Group
--- | --- | --- | --- | --- | --- | --- | ---
none | item | none | none | none | column | list | list
1000 | Info | Controller Started | The controller is started. |  | Log Conf | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC Power Focus HC ToolsControl | Controller and Tool
1001 | Warning | Controller Serial Number Updated | Generated at start-up if IT-board box serial number (controller serial number) differs from AUX-board box serial number. AUX-board is considered to be non-replaceable in field. The controller will reboot when the serial number is updated. | Replace IT-board or box. | Log Display Ack Conf | Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC | Controller and Tool
1010 | Info | Tool Connected | A tool is connected. |  | Log Display Conf | Flex Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC Power Focus HC ToolsControl | Controller and Tool
1011 | Info | Tool Disconnected | A tool is disconnected. |  | Log Display Conf | Flex Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC Power Focus HC ToolsControl | Controller and Tool
1012 | Info | Tool Rejected Controller Connection | This event can occur if the tool is into a skip-zone. | Verify if another controller is connected to the tool. Make sure that the tool settings are correctly set up. | Log Display Conf | Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Controller and Tool
2000 | Warning | Battery Low |  | Replace battery. | Log Display Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl XB | Tool
2001 | Warning | Battery Empty |  | Replace battery. | Log Display Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl XB | Tool
2002 | Warning | Tool Battery Health Low | Tool battery health problem is detected. Valid for SRB, TBP and IxB tools only. | Replace battery. | Log Display Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tool
2004 | Warning | Tool is not of the preferred type | Tool has been replaced by a tool with a different Tool Max Torque. | Change tool. | Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tool
2006 | Warning | Tool Backup Battery Health low | The backup battery in the tool has too poor performance. | The backup battery should be replaced. | Log Display Ack Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tool
2007 | Warning | Tool Backup Battery Missing or Broken | Tool backup battery is missing or broken. Valid for SRB and TBP tools only. | Insert battery. | Log Display Conf | Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tool
2008 | Warning | Tool Backup Battery Error | Tool backup battery error detected. Valid for SRB and TBP tools only. | Replace battery. | Log Display Conf | Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tool
2009 | Warning | Backup Battery Voltage Low | The controller's backup battery is almost empty. | Replace battery. | Log Display Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tool
2010 | Error | Tool Software Version Mismatch | Tool and controller software versions not compatible. | Service tool - update tool software. | Log Display Ack Conf | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC ToolsControl | Tool
2012 | Warning | Tool Communication Disturbance | Communication between tool and controller interrupted. | Relocate antenna placement. | Conf | Flex Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC Power Focus HC ToolsControl | Tool
2013 | Warning | Illegal Ring Position | Tool direction switch in faulty position. | If occurring frequently - service the tool. | Log Display Conf | Flex Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tool
2014 | Warning | Tool Overheated | Tool overheated. Valid for SRB, TBP and IxB tools only. | Allow tool to cool down. | Log Display Conf | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC ToolsControl XB | Tool
2015 | Error | Tool Temperature Sensor Error | SRB, TBP and IxB tools only. | Service the tool. | Log Display Conf | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC ToolsControl | Tool
2016 | Warning | Tool Pulse Unit Overheated | Pulse unit overheated. Tool is not locked, but the warning is displayed whenever the tool is started as long as the pulse unit temperature is over threshold. Valid for SRB, TBP and IxB tools only. | Allow tool to cool down. | Log Display Conf | Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tool
2019 | Warning | Tool Could not Start Motor | Tool motor failure. Valid for SRB, TBP and IxB tools only. |  | Log Display Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tool
2020 | Warning | Tool Requires Motor Tuning | Tool requires motor tuning. | Perform a motor tuning. | Log Display Conf | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC ToolsControl XB | Tool
2021 | Warning | Motor Tuning Failed | Motor tuning failed. | Complete motor tuning or service the tool. | Log | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC ToolsControl | Tool
2022 | Info | Motor Tuning Completed | Motor tuning completed. |  | Log Conf | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC ToolsControl | Tool
2023 | Warning | The Tool Requires Open End Tuning | The tool requires open end tuning. | Perform open end tuning. | Log Display Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tool
2024 | Warning | Open End Tuning Failed | Open end tuning failed. | Try to perform open end tuning one more time. If it fails again, service the tool. | Log Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tool
2025 | Info | Open End Tuning Successful | Open end tuning successful. |  | Log Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tool
2026 | Warning | Open End Position Failed | Open end position failed. | Press the tool trigger again and wait for the positioning to be completed. If it fails again, service the tool. | Log Display Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tool
2027 | Warning | Usage Limited Due To High Tool Temperature | Temperature limit value has been reached. Tightening has been inhibited to reduce risk for tool shutting down due to overheating. | Wait until tool temperature has been reduced. | Log Display Conf | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC ToolsControl XB | Tool
2030 | Error | Tool Memory Failure: Change Tool | Tool memory corrupt. | Service the tool. | Log Display Ack Conf | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC ToolsControl | Tool
2031 | Error | Tool Accessory Memory Corrupt | Tool accessory memory corrupt. | Service the tool accessory. | Log Display Ack Conf | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC ToolsControl | Tool
2040 | Error | System Check Failure |  |  | Log Display Ack Conf | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC ToolsControl XB | Tool
2041 | Error | Torque Transducer Error | Will be generated either on calibration error or if tool reports transducer error. | Service the tool. | Log Display Conf | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC ToolsControl XB | Tool
2042 | Error | Angle Transducer Error |  | Service the tool. | Log Display Ack Conf | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC ToolsControl | Tool
2043 | Error | Tool Ground Fault Error |  | Service the tool. | Log Display Ack Conf | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC ToolsControl | Tool
2044 | Info | Tool Service Interval Expired | Indicates that servicing of the tool is needed. Triggered when the number of set tightenings has been exceeded. | Perform service of tool. | Log Display Conf | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC ToolsControl | Tool
2045 | Warning | Tool Calibration Data Invalid | If validation of calibration data fails. | Service the tool. | Log Display Conf | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC ToolsControl XB | Tool
2046 | Info | Tool: Next Calibration Date Has Passed | Indicates that calibration of tool is needed. Triggered when calibration alarm is enabled in settings and the current time is greater than next calibration date. | Service the tool. | Log Display Conf | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC ToolsControl | Tool
2048 | Info | Tool Calibration Value Updated By QA Device | Tool calibration was updated when a calibration with a QA device was performed. |  | Log Display Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tool
2050 | Error | Tool Parameter File Not Supported | Required tool parameters are missing. | Update tool parameters. | Log Display Conf | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC ToolsControl | Tool
2060 | Info | Unexpected Trigger Behavior | Used to prevent start of tool if accessory is connected. |  | Log Display Conf | IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC ToolsControl | Tool
2071 | Error | Tool Memory Corrupt | Tool descriptor is corrupt. | Service the tool. | Log Display Conf | Flex Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC ToolsControl | Tool
2072 | Info | Unknown Device Connected |  |  | Log Display Conf | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC ToolsControl | Tool
2073 | Warning | Tool Trigger Supervision Failure | HW channel failure. Mismatch between hardware and software of tool trigger. |  | Log Display Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tool
2074 | Warning | Tool Indicator Board Failure | Tool indicator board failure. | Service the tool. | Log Display Conf | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC ToolsControl | Tool
2075 | Warning | Tool Fan Voltage Failure | Tool fan voltage failure. | Service the tool. | Log Display Conf | Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC ToolsControl | Tool
2076 | Warning | Tool Accessory Bus Voltage Failure | Tool accessory bus voltage failure. | Service the tool. | Log Display Conf | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC ToolsControl | Tool
2077 | Warning | Tool Trigger Sensor Error | Tool trigger sensor error. | Service the tool. | Log Display Conf | IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC ToolsControl | Tool
2078 | Info | Tool Tightening Program Updated | Tool locked due to tightening program update. |  | Log Display Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tool
2079 | Error | Tool Cable Not Supported | Tool cable is corrupt. The chip in the cable is not responding or is damaged. | Switch cable. | Log Display Conf | Flex Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC ToolsControl | Tool
2080 | Error | Tool Battery Failure | DC voltage too high or too low. Battery failure. | Contact the Atlas Copco service representative and send back battery to Atlas Copco (do not reuse it!). | Log Display Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl XB | Tool
2081 | Error | Tool Current Limit Reached | The current limit value has been reached and the drive is disabled. | Service the tool. | Log Display Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tool
2082 | Error | Tool Current Measurement Error | Current measurement error. Current cannot be measured with a reliable result. | Service the tool. | Log Display Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl XB | Tool
2083 | Error | Tool Internal Error | Various internal hardware errors. Valid for STB and IxB tools only. | Service the tool. | Log Display Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl XB | Tool
2084 | Error | Tool Internal Software Error | Various internal software errors. Valid for STB and IxB tools only. | Service the tool. | Log Display Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl XB | Tool
2085 | Error | Tool RBU Error | An RBU error was detected by the tool software. | Check that the RBU is correctly installed. If error is still present then service the tool. | Log Display Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tool
2086 | Error | Tool Stall | Tool motor is stalling. | Service the tool. | Log Display Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl XB | Tool
2087 | Warning | Tool Motor Current High | Tool motor current limit value is exceeded, and the tool is locked. Tool will enter failsafe mode. Valid for SRB, TBP and IxB tools only. |  | Log Display Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl XB | Tool
2088 | Warning | Tool Battery Current High | Tool battery current is too high. Valid for SRB, TBP and IxB tools only. |  | Log Display Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl XB | Tool
2089 | Warning | Tool Drive Voltage Low | Tool drive voltage is below the monitored lower voltage limit value. Valid for SRB, TBP and IxB tools only. |  | Log Display Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tool
2090 | Warning | Tool Drive Voltage High | Tool drive voltage is above monitored higher voltage limit value. Valid for SRB, TBP and IxB tools only. |  | Log Display Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tool
2091 | Warning | Tool Main Board Error | Tool main board internal error. Valid for SRB, TBP and IxB tools only. |  | Log Display Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl XB | Tool
2092 | Warning | Tool Power Module Error | Tool power module internal error. Valid for SRB, TBP and IxB tools only. |  | Log Display Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tool
2093 | Warning | Pulse Unit Oil Level Low | The oil level of the connected pulse tool is low. | Service the tool. | Log Display Conf | Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tool
2094 | Warning | Pulse Unit Oil Level Empty | The oil level of the connected pulse tool is below required operational level. | Service the tool. | Log Display Ack Conf | Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tool
2095 | Warning | Tool Battery Communication Lost | Tool lost communication with battery. Valid for SRB, TBP and IxB tools only. | Make sure battery is snugged correctly. Otherwise change battery. | Log Display Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tool
2096 | Error | Tool Battery Software Version Mismatch | Tool battery software incompatible with tool software. Valid for SRB, TBP and IxB tools only. | Update software. | Log Display Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tool
2100 | Info | STwrench smartHEAD Removed | STwrench smartHEAD has been removed. | Reconnect smartHEAD and restart the wrench. | Log Display Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tool
2101 | Warning | Wrench Tightening When Locked | A wrench tightening was performed when the tool status was locked in the controller. | Wait until the tool status in controller is unlocked. | Log Display Conf | Power Focus 6000 Power Focus 8 ToolsControl | Tool
2120 | Warning | Unable To Start: Tool Has No Active Torque Transducer |  |  | Log Display | Flex | Tool
2121 | Warning | Transducers Are Disabled For Connected Tool |  |  | Log Display | Flex | Tool
2122 | Warning | Unable To Start: Tool Is Missing Required Torque Transducer |  | Change to a tool with multiple torque transducers or update the setting "Require dual torque" in Tool Configuration. | Log Display | Flex IxB | Tool
2123 | Warning | Unable To Start: Tool Is Missing Required Angle Transducer |  | Change to a tool with multiple torque transducers or update the setting "Require dual torque" in Tool Configuration. | Log Display | Flex | Tool
2125 | Error | Torque Transducer Error On Transducer 2 | There is an error on torque transducer 2 of a tool with multiple transducers. | Service the tool. | Log Display | Flex | Tool
2127 | Error | Tool Torque Transducer Calibration Error | There is an error on the torque transducer. | Service the tool. | Log Display | Flex Synchronized tightening | Tool
2129 | Error | Tool Torque Transducer: Shunt Test Failed | There is an error on the torque transducer. | Service the tool. | Log Display | Flex Synchronized tightening XB | Tool
2131 | Error | Tool Torque Transducer: Zero Offset Compensation Failed | There is an error on the torque transducer. | Ensure the tightening is started with zero torque on the tool. Service the tool. | Log Display | Flex Synchronized tightening | Tool
2133 | Error | Tool Torque Transducer Hardware Error | There is an error on the torque transducer. | Service the tool. | Log Display | Flex Synchronized tightening | Tool
2135 | Error | Tool Torque Transducer Error: Overflow In A/D Converter | There is an error on the torque transducer. | Service the tool. | Log Display | Flex Synchronized tightening | Tool
2136 | Error | Tool Torque Transducer Calibration Error On Transducer 2 | There is an error on torque transducer 2 of a tool with multiple transducers. | Service the tool. | Log Display | Flex | Tool
2137 | Error | Tool Torque Transducer Error: Shunt Test Failed On Transducer 2 | There is an error on torque transducer 2 of a tool with multiple transducers. | Service the tool. | Log Display | Flex | Tool
2138 | Error | Tool Torque Transducer Error: Zero Offset Compensation Failed On Transducer 2 | There is an error on torque transducer 2 of a tool with multiple transducers. | Ensure the tightening is started with zero torque on the tool. Service the tool. | Log Display | Flex | Tool
2139 | Error | Tool Torque Transducer Hardware Error On Transducer 2 | There is an error on torque transducer 2 of a tool with multiple transducers. | Service the tool. | Log Display | Flex | Tool
2140 | Error | Tool Torque Transducer Error: Overflow In A/D Converter On Transducer 2 | There is an error on torque transducer 2 of a tool with multiple transducers. | Service the tool. | Log Display | Flex | Tool
2141 | Error | Tool Angle Transducer Error On Transducer 2 | Will be generated if tool reports transducer error from angle transducer 2. | Service the tool. | Log Display Conf | Flex Power Focus 6000 ToolsControl Power Focus 8 Synchronized tightening Power Focus XC | Tool
2142 | Error | Torque transducer redundancy error | There is an error on torque transducer 2 of a tool with multiple transducers. | Reset redundancy error | Log Display | Power Focus 6000 ToolsControl | Tool
2143 | Error | Angle transducer redundancy error | There is an error on torque transducer 2 of a tool with multiple transducers. | Reset redundancy error | Log Display | Power Focus 6000 ToolsControl | Tool
2144 | Warning | Tool Angle Transducer 2 Needs Calibration | Angle Transducer 2 needs calibration. | Tool requires motor tuning. | Log Conf Display | Flex Power Focus 6000 ToolsControl Power Focus 8 Synchronized tightening Power Focus XC | Tool
2145 | Warning | Tool Angle Transducer 3 Needs Calibration | Angle Transducer 3 needs calibration. | Tool requires motor tuning. | Log Conf Display | Flex Power Focus 6000 ToolsControl Power Focus 8 Synchronized tightening Power Focus XC | Tool
2146 | Error | Tool Angle Transducer Error on Transducer 3 | Will be generated if tool reports transducer error from angle transducer 3. | Service the tool. | Log Conf Display | Flex Power Focus 6000 ToolsControl Power Focus 8 Synchronized tightening Power Focus XC | Tool
2162 | Error | Torque transducer error: Torque value too low | Detected value below limits on torque transducer. | Restart the tool. If the problem persists, service the tool. | Log Display Conf | Power Focus 6000 Power Focus 8 Flex Synchronized tightening ToolsControl | Tool
2163 | Error | Torque transducer error: Torque value too high | Detected value above limits on torque transducer. | Restart the tool. If the problem persists, service the tool. | Log Display Conf | Power Focus 6000 Power Focus 8 Flex Synchronized tightening ToolsControl | Tool
2164 | Error | Torque transducer 2 error: Torque value too low | Detected value below limits on torque transducer 2. | Restart the tool. If the problem persists, service the tool. | Log Display Conf | Power Focus 6000 Power Focus 8 Flex Synchronized tightening ToolsControl | Tool
2165 | Error | Torque transducer 2 error: Torque value too high | Detected value above limits on torque transducer 2. | Restart the tool. If the problem persists, service the tool. | Log Display Conf | Power Focus 6000 Power Focus 8 Flex Synchronized tightening ToolsControl | Tool
2166 | Error | Tool restarted after an unexpected internal software error. | Tool was restarted after an unexpected internal software error. | Service the tool if problem persists. | Log Display Conf | Power Focus 6000 Power Focus 8 Flex Synchronized tightening ToolsControl | Tool
2167 | Error | Tool internal communication error on transducer module. | Tool internal communication error on transducer module. | Restart the tool. If the problem persists, service the tool. | Log Display Conf | Power Focus 6000 Power Focus 8 Flex Synchronized tightening ToolsControl | Tool
2168 | Error | Tool internal communication error on transducer module 2. | Tool internal communication error on transducer module 2. | Restart the tool. If the problem persists, service the tool. | Log Display Conf | Power Focus 6000 Power Focus 8 Flex Synchronized tightening ToolsControl | Tool
2169 | Error | Tool internal communication error with transducer module | Tool internal communication error with transducer module. | Restart the tool. If the problem persists, service the tool. | Log Display Conf | Power Focus 6000 Power Focus 8 Flex Synchronized tightening ToolsControl | Tool
2170 | Error | Tool transducer module error - Voltage out of range (Vdda on board 2) | Vdda votage is out of range on board 2 of tool transducer module. | Restart the tool. If the problem persists, service the tool. | Log Display Conf | Power Focus 6000 Power Focus 8 Flex Synchronized tightening ToolsControl | Tool
2171 | Error | Tool transducer module 2 error - Voltage out of range (Torque) | Torque supply voltage is out of range on torque transducer module 2. | Restart the tool. If the problem persists, service the tool. | Log Display Conf | Power Focus 6000 Power Focus 8 Flex Synchronized tightening ToolsControl | Tool
2174 | Error | Tool transducer module error - Voltage out of range (Vdda on board 1) | Vdda votage is out of range on board 1 of tool transducer module. | Restart the tool. If the problem persists, service the tool. | Log Display Conf | Power Focus 6000 Power Focus 8 Flex Synchronized tightening ToolsControl | Tool
2175 | Error | Tool transducer module error - CPU temperature high on board 1 | CPU temperature is high on board 1 of torque transducer module. | Wait until tool temperature has been reduced. If the problem persists, service the tool. | Log Display Conf | Power Focus 6000 Power Focus 8 Flex Synchronized tightening ToolsControl | Tool
2176 | Error | Tool transducer module error - CPU temperature high on board 2 | CPU temperature is high on board 2 of torque transducer module. | Wait until tool temperature has been reduced. If the problem persists, service the tool. | Log Display Conf | Power Focus 6000 Power Focus 8 Flex Synchronized tightening ToolsControl | Tool
2177 | Error | Tool torque transducer production calibration missing. | Production calibration parameters are missing on torque transducer module. | Restart the tool. If the problem persists, service the tool. | Log Display Conf | Power Focus 6000 Power Focus 8 Flex Synchronized tightening ToolsControl | Tool
2178 | Error | Tool transducer module error - Voltage out of range (Torque) | Torque supply voltage is out of range on torque transducer module. | Restart the tool. If the problem persists, service the tool. | Log Display Conf | Power Focus 6000 Power Focus 8 Flex Synchronized tightening ToolsControl | Tool
2179 | Error | Tool transducer module 2 error - Voltage out of range (Vdda on board 1) | Vdda votage is out of range on board 1 of tool transducer module 2. | Restart the tool. If the problem persists, service the tool. | Log Display Conf | Power Focus 6000 Power Focus 8 Flex Synchronized tightening ToolsControl | Tool
2180 | Error | Tool transducer module 2 error - CPU temperature high on board 1 | CPU temperature is high on board 1 of torque transducer module 2. | Wait until tool temperature has been reduced. If the problem persists, service the tool. | Log Display Conf | Power Focus 6000 Power Focus 8 Flex Synchronized tightening ToolsControl | Tool
2181 | Error | Tool transducer module 2 error - CPU temperature high on board 2 | CPU temperature is high on board 2 of torque transducer module 2. | Wait until tool temperature has been reduced. If the problem persists, service the tool. | Log Display Conf | Power Focus 6000 Power Focus 8 Flex Synchronized tightening ToolsControl | Tool
2182 | Error | Tool torque transducer 2 production calibration missing. | Production calibration parameters are missing on torque transducer module 2. | Restart the tool. If the problem persists, service the tool. | Log Display Conf | Power Focus 6000 Power Focus 8 Flex Synchronized tightening ToolsControl | Tool
2183 | Error | Tool transducer module 2 error - Voltage out of range (Vdda on board 2) | Vdda votage is out of range on board 2 of tool transducer module 2 | Restart the tool. If the problem persists, service the tool. | Log Display Conf | Power Focus 6000 Power Focus 8 Flex Synchronized tightening ToolsControl | Tool
2202 | Error | Tool HMI overcurrent occurred | Tool HMI overcurrent was detected. | Service the tool. Replace tool HMI. | Log Display Ack Conf | IxB | Tool
2203 | Error | Tool front light overcurrent occurred | Tool front light overcurrent was detected | Service the tool. Replace tool front light. | Log Display Ack Conf | IxB | Tool
2204 | Error | Accessory bus overcurrent occurred | Accessory bus overcurrent was detected. | Service the tool. Replace accessory bus. | Log Display Ack Conf | IxB | Tool
2207 | Error | Vibrator overcurrent occurred | Vibrator overcurrent was detected. | Service the tool. Replace the vibrator. | Log Display Ack Conf | IxB | Tool
2208 | Warning | System CPU temperature high | System CPU temperature high. | Wait until tool temperature has been reduced. | Log Display Conf | IxB XB | Tool
2209 | Error | System CPU temperature critical | System CPU temperature critical. | Wait until tool temperature has been reduced. | Log Display Conf | IxB XB | Tool
2210 | Error | Unsupported power source: tightening not permitted | Battery with too low voltage attached to the tool. | Attach battery with higher voltage to the tool. | Log Display Ack Conf | IxB | Tool
2217 | Info | Running on backup battery | Running on backup battery. |  | Log | IxB | Tool
2218 | Info | Battery connected | Battery connected or controller/tool started. |  | Log | IxB | Tool
2219 | Info | Power source: unknown | Unknown power source connected or controller/tool started with unknown power source. |  | Log | IxB | Tool
2220 | Error | Tool fan failure | Applies to IPB-P. | Service the tool. | Log Display Ack | IxB | Tool
2221 | Warning | Battery overheated | Battery temperature is too high. | Change battery and let overheated battery cool down. | Log Display Conf | IxB Power Focus 6000 Power Focus 8 ToolsControl | Tool
2222 | Warning | Usage limited due to high battery temperature | Battery temperature is too high. | Change battery and let overheated battery cool down. | Log Display Conf | IxB Power Focus 6000 Power Focus 8 ToolsControl | Tool
2223 | Error | Front LED is not available | When the tool boots up, if the front LED is not detected, this event will be triggered. | Fix the front light or the front light cable connection. | Log Display Conf | IxB Power Focus 6000 Power Focus 8 | Controller and Tool
2224 | Error | Front LED color is not available | When the tool boots up, if the front LED color is not detected, this event will be triggered. | Fix the front light color or the front light cable connection | Log Display Conf | IxB Power Focus 6000 Power Focus 8 | Controller and Tool
2225 | Error | RHMI buttons are not available | When the tool boots up, if the RHMI buttons are not detected, an event will be triggered. | Fix the RHMI buttons. | Log Display Conf | IxB Power Focus 6000 Power Focus 8 | Controller and Tool
2226 | Error | LED ring is not available | When the tool boots up, if the LED ring is not detected, an event will be triggered. | Fix the back ring lights or the back ring light connection. | Log Display Conf | IxB Power Focus 6000 Power Focus 8 | Controller and Tool
2227 | Error | Fan is not available | When the tool boots up, if the fan is not detected, an event will be triggered. | Fix the fan. | Log Display Conf | IxB Power Focus 6000 Power Focus 8 | Controller and Tool
2228 | Error | RRE board is not available | When the tool boots up, if the tool board interface is not detected, an event will be triggered. | Fix the tool board interface. | Log Display Conf | IxB Power Focus 6000 Power Focus 8 | Controller and Tool
2229 | Warning | Tool Backup battery empty | Tool backup battery is empty. |  | Log Display Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tool
2230 | Info | Tool Backup battery fully charged | Tool backup battery is fully charged. |  | Log Display Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tool
2231 | Warning | Tool Backup Battery Missing | Tool backup battery is missing. | Insert battery. | Log Display Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tool
2232 | Warning | Tool Backup Battery Broken | Tool backup battery is broken. |  | Log Display Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tool
2300 | Error | Tool main board error - Voltage out of range (Torque) |  | Restart the tool. If the error persist, service the tool an look for lose connections in the cable connectors. Inspect any possible damage in the cables. | Log Display Ack | IxB | Tool
2301 | Error | Tool main board error - Voltage out of range (Analog) |  | Restart the tool. If the error persist, service the tool an look for lose connections in the cable connectors. Inspect any possible damage in the cables. | Log Display Ack | IxB | Tool
2302 | Error | Tool main board error - Voltage out of range (MCU Vdd) |  | Restart the tool. If the error persist, service the tool an look for lose connections in the cable connectors. Inspect any possible damage in the cables. | Log Display Ack | IxB | Tool
2303 | Error | Tool main board error - Voltage out of range (Step up) |  | Restart the tool. If the error persist, service the tool an look for lose connections in the cable connectors. Inspect any possible damage in the cables. | Log Display Ack | IxB | Tool
2304 | Error | Tool main board error - Voltage out of range (UPS) |  | Restart the tool. If the error persist, service the tool an look for lose connections in the cable connectors. Inspect any possible damage in the cables. | Log Display Ack | IxB | Tool
2305 | Error | Tool main board error - Voltage out of range (Tool power) |  | Restart the tool. If the error persist, service the tool an look for lose connections in the cable connectors. Inspect any possible damage in the cables. | Log Display Ack | IxB XB | Tool
2306 | Error | Tool main board error - Voltage out of range (Vdd) |  | Restart the tool. If the error persist, service the tool an look for lose connections in the cable connectors. Inspect any possible damage in the cables. | Log Display Ack | IxB XB | Tool
2307 | Error | Tool main board error - Hardware failure (IMU) |  | Service the tool. | Log Display Ack | IxB | Tool
2331 | Error | Tool power module error - Voltage low (Reference) |  | Service the tool. | Log Display Ack | IxB | Tool
2332 | Error | Tool power module error - Voltage high (Reference) |  | Service the tool. | Log Display Ack | IxB | Tool
2333 | Error | Tool power module error - Voltage low (UPS) |  | Service the tool. | Log Display Ack | IxB | Tool
2334 | Error | Tool power module error - Voltage high (UPS) |  | Service the tool. | Log Display Ack | IxB | Tool
2335 | Error | Tool power module error - Voltage low (Backup domain) |  | Service the tool. | Log Display Ack | IxB | Tool
2336 | Error | Tool power module error - Voltage high (Backup domain) |  | Service the tool. | Log Display Ack | IxB | Tool
2500 | Error | Tensioner puller bar max number | Tensioner puller bar must be replaced. System is locked for usage. Pressure can only be released. | Send the tensioner to service organization for replacement of the puller bar. | Log Display Ack | Power Focus HC | Tool
2501 | Error | Pump motor protection alarm | The pump motor protection has stopped the motor. The system must stop. If the system is under pressure, it needs manual actions to release pressure. | Turn off the system. If under pressure, mechanically release the pressure and send the pump to service. | Log Display Ack | Power Focus HC | Tool
2502 | Error | Pump motor oil level low alarm | The pump motor oil level is low which has stopped the motor. If the system is under pressure, it needs manual actions to release pressure. | Turn off the system. If under pressure, mechanically release the pressure and top up oil. | Log Display Ack | Power Focus HC | Tool
2503 | Error | Pump motor oil temperature high alarm | The pump motor oil temperature is high. | Turn off the system and wait for the oil to cool down. | Log Display Ack | Power Focus HC | Tool
2504 | Error | Tensioner pressure sensor alarm | Failure in the pressure sensor electronics of the tensioner. No pressure can be read nor reported to the system. | Turn off the system. If under pressure, mechanically release the pressure and send the tensioner to service. | Log Display Ack | Power Focus HC | Tool
2505 | Error | Pump pressure sensor alarm | Failure in the pressure sensor electronics of the pump. No pressure can be read nor reported to the system. | Turn off the system. If under pressure, mechanically release the pressure and send the pump to service. | Log Display Ack | Power Focus HC | Tool
2506 | Error | Unexpected clockwise rotation detected | A clockwise nut rotation while waiting for pressure release after completed tensioning. The result is invalidated. | Release pressure and tension the nut again. | Log Display Conf | Power Focus HC | Tool
2507 | Error | Unexpected counter clockwise rotation detected | A counter clockwise nut rotation while waiting for pressure release after completed tensioning. The result is invalidated. | Release pressure and tension the nut again. | Log Display Conf | Power Focus HC | Tool
2508 | Error | Pump or tensioner pressure sensor failure | Too large difference between the pressure sensor readings in the pump and the tensioner. Pressurization is halted. | Problem in the hydraulics or the calibration of the pressure sensors. Restart the system and try again. If the problem repeats, contact your local Atlas Copco sales representative. | Log Display Ack | Power Focus HC | Tool
2509 | Error | Tensioner pressure sensor failure or hydraulic hose failure | The tensioner's pressure sensor indicates no pressure but the pump's sensor reads a pressure increase. Pressurization is halted. | Problem in the hydraulics or the calibration of the pressure sensors. Restart the system and try again. If the problem repeats, contact your local Atlas Copco sales representative. | Log Display Ack | Power Focus HC | Tool
2510 | Error | Set custom ID failed | Setting custom ID failed. | Restart the system and check the connected devices. If Custom ID for the unit is wrong, redo the setting. | Log Display Ack | Power Focus HC | Tool
2511 | Info | Custom ID is set | Setting custom ID succeeded. |  | Log Display Ack | Power Focus HC | Tool
2512 | Warning | Malformed Barcode string, ignored | The scanned string could not be parsed as a tower data bar code. | Scan a proper tower data qr code or scan tower section id. | Log Display Ack | Power Focus HC | Tool
2513 | Error | No pump pressure detected | The system is trying to pressurize but no pressure increase is registered in the pump. Possible cause is incorrect phase order in the three phase connector. | Power off the system and reverse the phases of the power connector. | Log Display Ack | Power Focus HC | Tool
2514 | Warning | Tensioner overtorque alarm | Too high torque is applied to the click wrench. This causes damage to the torque sensor. | Relax the torque. | Log | Power Focus HC | Tool
2515 | Warning | Tensioner overpressure alarm | The pressure in the tensioner is too high. | Let the pressure drop, or release the pressure. Check the hydraulic pressure parameters. | Log | Power Focus HC | Tool
2516 | Warning | Unexpected Pump or Tensioner firmware | Unexpected Pump or Tensioner firmware version detected, restart system. If the problem persists, the system may be possible to run, but carefully observe any unexpected behaviour. | Power cycle system | Log Display Ack | Power Focus HC | Tool
2517 | Error | Incompatible Pump or Tensioner firmware version, restart system. The system cannot run. | Incompatible Pump or Tensioner firmware version, restart system. The system cannot run. | Restart system, if this doesn’t help replace the failing unit. Check connected devices to see which one has not connected. | Log Display Ack | Power Focus HC | Tool
2518 | Error | Physical safety signal failed. | Safety signal from the hand controller has not reached the pump | Check the cable connected to the tensioner If the event re occurs contact service | Log Display Ack | Power Focus HC | Tool
2519 | Error | System entered fail safe mode | Fail safe mode activated | User acknowledgment required | Log Display Ack | Power Focus HC | Tool
2520 | Error | System exits fail safe mode | Fail safe mode deactivated | System returns to normal function | Log Display Ack | Power Focus HC | Tool
2523 | Error | Communication lost with the tensioner | Communication lost with the tensioner | Check the cable connected to the tensioner Event can occur when the system is powered off | Log Display Ack | Power Focus HC | Tool
2524 | Error | Communication lost with the pump | Communication lost with the pump | . Check the cables are connected Event can occur when the system is powered off | Log Display Ack | Power Focus HC | Tool
2525 | Error | Action requested from the hand controller is not performed by the pump | Action requested from the hand controller is not performed by the pump | Try again If this event occurs often contact service. | Log Display Ack | Power Focus HC | Tool
2800 | Error | There is an error on the clutch sensor | Check sensor and clutch assembly | If this event occurs often contact service. | Log Display Ack | Power Focus 6000 Power focus 8 | Tool
2801 | Error | Triggered when clutch settings alarm is enabled in settings and the current time is greater than next clutch settings date | Indicates that clutch settings of tool is needed | If this event occurs often contact service. | Log Display Ack | Power Focus 6000 Power focus 8 | Tool
3000 | Error | Controller Internal Software Error | Software error in the controller. | Contact service. | Log Display Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Controller
3001 | Error | Controller Clock Battery Empty | Internal battery is getting close to end of life. | Replace battery. | Log Display Ack Conf | Flex Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC | Controller, Drive and Synchronized tightening
3002 | Error | Drive Internal Software Error | Software error in the drive. | Contact service. | Log Display Conf | Flex Synchronized tightening | Drive
3010 | Warning | System Overheated | The controller is overheated. | Cool down. | Log Display Conf | Power Focus 6000 Power Focus 8 Power Focus XC | Controller, Drive and Synchronized tightening
3011 | Warning | Drive Overheated Controller Hardware |  | Cool down. | Log Display Conf | Flex ToolsControl | Controller, Drive and Synchronized tightening
3013 | Warning | Usage Limited Due To High Controller Temperature | Temperature limit value has been reached. Tightening has been inhibited to reduce risk for controller shutting down due to overheating. | Wait until controller temperature has been reduced. | Log Display Conf | Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC | Controller, Drive and Synchronized tightening
3020 | Warning | Controller Hardware Failure |  |  | Log Display Conf | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC | Controller, Drive and Synchronized tightening
3021 | Warning | System Voltage Problem | DC voltage too high or too low. |  | Log Display Conf | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC | Controller, Drive and Synchronized tightening
3022 | Warning | Controller Voltage Problem: AC Input Voltage Too High | DC voltage too high or too low. | Fix the input voltage. | Log Display | Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC | Controller, Drive and Synchronized tightening
3023 | Warning | Controller Voltage Problem: AC Input Voltage Too Low | DC voltage too high or too low. | Fix the input voltage. | Log Display | Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC | Controller, Drive and Synchronized tightening
3024 | Warning | Drive Voltage Problem: AC Input Voltage Too High | DC voltage too high or too low. | Fix the input voltage. | Log Display | Flex ToolsControl | Controller, Drive and Synchronized tightening
3025 | Warning | Drive Voltage Problem: AC Input Voltage Too Low | DC voltage too high or too low. | Fix the input voltage. | Log Display | Flex ToolsControl | Controller, Drive and Synchronized tightening
3026 | Info | Max number of IxB Connect tools already connected. | Indicates that the number of IxB Connect tools connected to the controller has reached the max. allowed connected tools. |  | Log | ToolsControl | Controller and Tool
3029 | Info | The client lost network connection | The tool has lost the network connection by either leaving the network coverage or due to another cause. | Troubleshoot by checking the roaming threshold and reduce the selected channel numbers to less than 24 to make sure roaming is enabled. | Log Display Conf Ack | IxB | Controller and Tool
3030 | Error | IP Address Conflicting With Another Node On The Network | The set IP address is in use by another device on the same network. | Change IP address on one of the devices. | Log Display Conf | Flex Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC Power Focus HC | Controller, Drive and Synchronized tightening
3031 | Info | Network Cable Unplugged | The carrier of the factory port is lost (cable disconnected). | Check the cable connection. | Log Display Conf | Flex Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC | Controller, Drive and Synchronized tightening
3032 | Info | Pairing Started | Tool pairing started. |  | Log Display Conf | Power Focus 6000 Power Focus 8 Power Focus XC | Controller, Drive and Synchronized tightening
3033 | Info | Pairing Successful | Tool pairing successful. |  | Log Display Conf | Power Focus 6000 Power Focus 8 Power Focus XC | Controller, Drive and Synchronized tightening
3034 | Info | Pairing Unsuccessful: No Tool Found | The controller found no tool to pair with when scanning for radio peers. | Set the tool in pairing mode and try again. | Log Display Conf | Power Focus 6000 Power Focus 8 Power Focus XC | Controller, Drive and Synchronized tightening
3035 | Error | Pairing Unsuccessful: More Than One Tool Found | The controller found more than one tool when scanning for radio peers. | Ensure that only one tool is in pairing mode when starting the pairing mode on the controller. | Log Display Conf | Power Focus 6000 Power Focus 8 Power Focus XC | Controller, Drive and Synchronized tightening
3036 | Error | Pairing Unsuccessful: Communication Error | The controller experienced a loss of connection, an unexpected answer or timeout during the pairing process. | Try to perform pairing one more time. If it fails again, service the tool. | Log Display Conf | Power Focus 6000 Power Focus 8 Power Focus XC | Controller, Drive and Synchronized tightening
3037 | Info | Pairing Unsuccessful: Tool Slot Is Full |  | Clear one tool slot. | Log Display Conf | Power Focus 6000 Power Focus 8 Power Focus XC | Controller, Drive and Synchronized tightening
3040 | Warning | Emergency Stop | Drive disabled due to emergency stop. | Reset emergency stop. | Log Display Conf | Flex Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC ToolsControl | Controller, Drive and Synchronized tightening
3050 | Info | System Clock Updated | System clock has been updated. |  | Log Conf | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC Power Focus HC | Controller, Drive and Synchronized tightening
3051 | Error | System Clock Error | Wrong time read from hardware Real Time Clock (RTC). | Change RTC battery. | Log Display Ack Conf | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC Power Focus HC | Controller, Drive and Synchronized tightening
3052 | Warning | Remote Start Configuration Error | Mismatch between HW and SW remote start configuration. | Verify that HW dip switch matches the selected start source. | Log Display Conf | Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC ToolsControl | Controller, Drive and Synchronized tightening
3053 | Info | Drive Connected | Synchronized tightening drive has been connected. |  | Log Display | Flex Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC ToolsControl | Controller, Drive and Synchronized tightening
3054 | Info | Drive Disconnected | Drive disconnected from controller. | Check cabling and power-supply for externally connected drives or replace the controller. | Log Display | Flex Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC ToolsControl | Controller, Drive and Synchronized tightening
3055 | Warning | Mode Configuration Error | Generated when selected mode is configured wrongly. E.g. configuring two bolts with the same bolt number or the same channel, incomplete mode configuration. | Check ToolsTalk 2 for mode configuration error. | Log Display | Flex Synchronized tightening | Controller, Drive and Synchronized tightening
3056 | Warning | Unable to Start: Tool Or Drive Is Missing | Generated when a used channel is missing a drive or tool. | Verify Channel Menu on the HMI. Connect missing drive or tool. | Log Display | Flex Synchronized tightening | Controller, Drive and Synchronized tightening
3057 | Info | Unable to Start: Channel Is Already In Use | Generated when a needed channel has been allocated to another virtual station. |  | Log Display | Flex | Controller, Drive and Synchronized tightening
3058 | Info | No Mode Selected |  | Select mode. | Log Display | Flex Synchronized tightening | Controller, Drive and Synchronized tightening
3059 | Warning | Failed To Connect To Atlas Copco License Manager | Indicates that the controller failed to connect to the local license manager to get licenses. | Verify the local network. If it fails again, service the controller. | Log Display Conf | IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC ToolsControl | Controller, Drive and Synchronized tightening
3060 | Error | Number of Virtual Station licenses is exceeded. | Virtual Station license greater than available licenses. | Update licenses or Virtual Station configuration. | Log Display Ack | ToolsControl | Controller
3061 | Warning | Unable To Start: Enable Signal Is Low |  | Ensure the signal "Enable Operation" is set to high before tightening is started. | Log Display | Flex Synchronized tightening | Controller, Drive and Synchronized tightening
3062 | Warning | Unable To Start: Stop Signal Is High |  | Ensure the signal "Enable Operation" is set to low before tightening is started. | Log Display | Flex Synchronized tightening | Controller, Drive and Synchronized tightening
3063 | Warning | Unable To Start: All Channels Inhibited | All channels have been set inhibited, so no tightening can be started. | Set at least one channel to not be inhibited. | Log Display | Flex Synchronized tightening | Controller, Drive and Synchronized tightening
3064 | Warning | Carrier Number Faulty | A FlexCarrier hex switch is set to zero. | Turn the switch to a non-zero value. | Log Display | Flex | Controller, Drive and Synchronized tightening
3065 | Warning | Carrier E-Stop Configuration Plug Wrong Type Or Missing | A Carrier is missing its E-stop configuration plug, or the plug type is wrong. | Insert correct plug type. | Log Display | Flex | Controller, Drive and Synchronized tightening
3066 | Warning | Carrier Voltage Inlet: No 3-Phase AC |  | Ensure the 3-phase power to the carrier is within acceptable limits and fully functional. Ensure the 3-phase cables are in good condition and properly connected. | Log Display | Flex | Controller, Drive and Synchronized tightening
3067 | Warning | Carrier Voltage Inlet: One AC Phase Missing |  | Ensure the 3-phase power to the carrier is within acceptable limits and fully functional. Ensure the 3-phase cables are in good condition and properly connected. | Log Display | Flex | Controller, Drive and Synchronized tightening
3068 | Warning | Carrier: Internal 24 VDC Power Supply Unit Broken |  | Service the carrier. | Log Display | Flex | Controller, Drive and Synchronized tightening
3069 | Warning | Carrier 24 Voltage OUT-Port Disabled Due To Over-Current |  | Reset the system. | Log Display | Flex | Controller, Drive and Synchronized tightening
3070 | Warning | Carrier, Hardware Error In PF6 FlexControl Cable OUT |  | Reset the system. | Log Display | Flex | Controller, Drive and Synchronized tightening
3071 | Warning | Carrier, Hardware Error In PF6 FlexControl Cable IN |  | Reset the system. | Log Display | Flex | Controller, Drive and Synchronized tightening
3072 | Warning | Emergency Stop 24 VDC Power Failure Due To Short-Circuit |  | Service the carrier. | Log Display | Flex | Controller, Drive and Synchronized tightening
3073 | Warning | Unable To Start: System Is Emergency Stopped | When allocating multiple spindles, this event is invoked by "preStartCheckFailed" due to emergency stop. | Reset the emergency stop. | Log Display | Flex Synchronized tightening | Controller, Drive and Synchronized tightening
3074 | Warning | Carrier Overheated |  | Cool down. | Log Display | Flex | Controller, Drive and Synchronized tightening
3075 | Warning | Carrier Temperature OK |  |  | Log Display | Flex | Controller, Drive and Synchronized tightening
3076 | Warning | Carrier: Internal 24 VDC Power Supply Overload | Current output from internal PSU is too high. | Disconnect other carriers that are powered from the PSU. Disconnect any external equipment using 24 VDC. | Log Display | Flex | Controller, Drive and Synchronized tightening
3077 | Warning | Carrier: Internal 24 VDC Power Supply Over Voltage | Voltage output from internal PSU is too high. | Replace the carrier. | Log Display | Flex | Controller, Drive and Synchronized tightening
3078 | Warning | Carrier: Internal 24 VDC Power Supply Under Voltage | Voltage output from internal PSU is too low. | Replace the carrier. | Log Display | Flex | Controller, Drive and Synchronized tightening
3079 | Warning | External Supply To Carrier: 24 VDC Over Voltage | Backup input voltage is more than 27 VDC. | Adjust the backup input voltage. | Log Display | Flex | Controller, Drive and Synchronized tightening
3080 | Warning | External Supply To Carrier: 24 VDC Under Voltage | Backup input voltage is less than 19 VDC. | Adjust the backup input voltage. | Log Display | Flex | Controller, Drive and Synchronized tightening
3081 | Warning | Carrier Voltage Inlet: 3-Phase AC Over Voltage | Input voltage is too high. | Lower input voltage: must be 400 VAC or 480 VAC. | Log Display | Flex | Controller, Drive and Synchronized tightening
3082 | Warning | Carrier Voltage Inlet: 3-Phase AC Under Voltage | Input voltage is too low. | Higher input voltage: must be 400 VAC or 480 VAC. | Log Display | Flex | Controller, Drive and Synchronized tightening
3083 | Error | Wrong Anybus/Profisafe Module Firmware |  | Update the firmware in the anybus module to the latest version. | Log Display | Flex Power Focus 6000 Power Focus 8 Synchronized tightening | Controller, Drive and Synchronized tightening
3084 | Error | Soft PLC Runtime Error | eCLR has terminated in an uncontrolled way. |  | Log Display Conf | Flex Power Focus 6000 Power Focus 8 Synchronized tightening | Controller, Drive and Synchronized tightening
3085 | Warning | Carrier: Fan Module Out Of Order |  | Replace fan module. | Log Display | Flex | Controller, Drive and Synchronized tightening
3086 | Warning | Carrier: Fan Module Partly Out Of Order |  | Replace fan module. | Log Display | Flex | Controller, Drive and Synchronized tightening
3087 | Warning | Carrier: Left Fan Module Out Of Order |  | Replace fan module. | Log Display | Flex | Controller, Drive and Synchronized tightening
3088 | Warning | Carrier: Left Fan Module Partly Out Of Order |  | Replace fan module. | Log Display | Flex | Controller, Drive and Synchronized tightening
3089 | Warning | Carrier: Right Fan Module Out Of Order |  | Replace fan module. | Log Display | Flex | Controller, Drive and Synchronized tightening
3090 | Warning | Carrier: Right Fan Module Partly Out Of Order |  | Replace fan module. | Log Display | Flex | Controller, Drive and Synchronized tightening
3091 | Info | Sync member channel collision | Generated when two or more sync members are configured to the same channel. | Reconfigure the colliding sync member to have a unique or different channel that has not been allocated to another sync member. | Log Conf Display Ack | Power Focus 8 Synchronized tightening ToolsControl | Controller, Drive and Synchronized tightening
3093 | Warning | Digital input received before the trigger is pressed. | Indicates that something went wrong with setup. |  | Log Conf Display Ack | Power Focus 8 Synchronized tightening ToolsControl | Controller, Drive and Synchronized tightening
3095 | Warning | WiFi Signal Strength Low | The wireless network signal strength is below the value set in setting "Warn on signal strength below (dBm)". |  | Conf | IxB | Controller and Tool
3096 | Warning | Cellular signal strength low | The RSSI value for the cellular connection is under the defined threshold value of -98 dBm. | Move the tool closer to the cellular antennas for a stronger connection and avoid data loss. | Conf | IxB | Controller, Drive and Synchronized tightening
3097 | Warning | Cellular connection lost | The system lost connection to the cellular network. | Move the tool closer to the cellular antennas. Check the cellular connection setup so correct APN is still configured. Check the cellular network for any problems. | Log Display Conf | IxB | Controller, Drive and Synchronized tightening
3100 | Warning | Mode Configuration Does Not Exist |  | Select an existing sync mode before starting a tightening. | Log Display | Flex Synchronized tightening | Controller, Drive and Synchronized tightening
3150 | Error | Software IAM Incompatibility | IAM is incompatible with the software that is installed on the controller. | Replace IAM. | Log Display Ack | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC | Controller, Drive and Synchronized tightening
3160 | Error | Failed To Activate Newly Installed Software | Something went wrong during the activation. When the newly installed software starts, a fallback to the previous working software happens. This error happens when the new software fails to start for three times and only during software installation. | Take an export and contact Atlas Copco for further assistance. Note down the software version you are trying to install as well as the software version that is working. | Log Display Ack | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC | Controller, Drive and Synchronized tightening
3161 | Error | Started On Unexpected Software Partition | The controller has started on the inactive software side and not on the expected software side. | Note down the software information (on the Home screen of the controller, select Controller > Software). Try to restart the controller and make sure its running on correct software when started again. If error persists, do an export and contact Atlas Copco. | Log Display Ack | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC | Controller, Drive and Synchronized tightening
3162 | Info | Software Upgrade Verification Failed | Failed to verify the integrity and authenticity of the software package. | Ensure that the software package that is being upgraded to is a signed, software package. Note down the software information (on the Home screen of the controller, select Controller > Software). If error persists, do an export and contact Atlas Copco. | Log Display Ack | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC | Controller, Drive and Synchronized tightening
3180 | Info | Software Adapter Import Verification Failed | Failed to verify the integrity and authenticity of the imported protocol adapters. | Make sure that the protocol adapters that are being imported are signed, protocol adapters. If error persists, do an export and contact Atlas Copco. | Log Display Ack | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC | Controller, Drive and Synchronized tightening
3500 | Error | Generic License Manager Error | Inconsistency detected in the feature management system used. | Contact Atlas Copco representative. | Log Display Ack | IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC ToolsControl | Controller, Drive and Synchronized tightening
3501 | Error | License Manager Synchronization Error | Synchronization with the license server failed. | Contact Atlas Copco service representative. | Log Display Ack | IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC ToolsControl | Controller, Drive and Synchronized tightening
3502 | Info | License Manager Synchronization Done | Synchronization with the license server completed. |  |  | IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC ToolsControl | Controller, Drive and Synchronized tightening
3503 | Warning | License Manager: Another Source in Use | License is used by another source. | Verify license assignment. | Log Display | IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC ToolsControl | Controller, Drive and Synchronized tightening
3504 | Warning | License Manager Restart Needed |  | Restart license manager. | Log Display | IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC ToolsControl | Controller, Drive and Synchronized tightening
3505 | Info | USB License Synchronization Started | Moving licenses from the USB license dongle started. |  | Log | Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl Power Focus HC | Controller, Drive and Synchronized tightening
3506 | Error | USB License Synchronization Error | Moving licenses from the USB license dongle failed. | Contact Atlas Copco service representative. | Log | Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl Power Focus HC | Controller, Drive and Synchronized tightening
3507 | Info | USB License Synchronization Done | Moving licenses from the USB license dongle done. |  | Log | Power Focus 6000 Power Focus 8 Power Focus HC | Controller, Drive and Synchronized tightening
3508 | Info | One or more of your licenses are about to expire. Please make sure you have a license server configured |  | Update licenses. | Log Display Conf | IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC ToolsControl | Controller, Drive and Synchronized tightening
3510 | Error | There is already a Local License Server in use. Return all licenses to the server prior to configuring a new one. | Inconsistency detected in a license to be used during configuration. | Update licenses. | Log Display Ack | ToolsControl | Controller
3511 | Warning | One of your licenses has a different license definition | Inconsistency detected in a license to be used. | Contact Atlas Copco representative. | Log Display Conf | IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC ToolsControl Power Focus HC | Controller, Drive and Synchronized tightening
3512 | Error | Unexpected license service error. Contact Atlas Copco for further assistance. |  | Contact Atlas Copco representative. | Log Conf Display Ack | ToolsControl | Controller
3550 | Warning | License Is Missing |  | Install the correct license. | Log Display Conf | IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC ToolsControl Power Focus HC | Controller, Drive and Synchronized tightening
3551 | Warning | Wireless Communication Disabled By Licensing |  | Unassign Standalone license from the Virtual Station. | Log Display Conf | IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC ToolsControl | Controller, Drive and Synchronized tightening
3600 | Info | System restart triggered by user | Restart is triggered as a consequence of a user action within the system, such as: After importing an export. Activating new software after software update. Swapping software side. Performing a service task that require a system restart. Open end tuning on IxB. Switching from WiFi to Bluetooth on IxB. |  | Log Conf | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC Power Focus HC | Controller and Tool
3601 | Info | Unexpected system shut down | The system rebooted or shut down unexpectedly |  | Log Conf | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC Power Focus HC ToolsControl | Controller and Tool
3610 | Info | System shut down due to power loss | Power switch is pressed or controller is disconnected from power source |  | Log Conf | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC Power Focus HC ToolsControl | Controller and Tool
3611 | Info | Backup battery timer timed out, shutting down | Tool have been runnning on backup battery for more than 20s |  | Log Conf | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC Power Focus HC ToolsControl | Controller and Tool
3612 | Info | System shut down due to inactivity | Inactivity timeout has expired |  | Log Conf | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC Power Focus HC ToolsControl | Controller and Tool
4010 | Info | Tool Locked By Digital Input | The tool is locked by a digital input signal. |  | Log Display Conf | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC ToolsControl | Tightening Process
4011 | Info | Tool Locked By Open Protocol | The tool is locked by Open Protocol. |  | Log Display Conf | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC ToolsControl | Tightening Process
4012 | Info | Tool Locked By Fieldbus | The tool is locked by the Fieldbus. |  | Log Display Conf | Flex Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC | Tightening Process
4013 | Info | Tool Locked By Socket Selector | Tool is locked when the socket selector is disconnected from the Virtual Station. | Unlock by Master Unlock. | Log Display Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tightening Process
4014 | Info | Tool Locked By Soft PLC | Soft PLC signal locked the tool. | Unlock by Master Unlock. | Log Display Conf | Flex Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC | Tightening Process
4015 | Info | Loosening Disabled | Loosening is disabled in the tightening program. |  | Log Display Conf | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC ToolsControl XB | Tightening Process
4016 | Info | Tightening Disabled |  |  | Log Display Conf | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC ToolsControl XB | Tightening Process
4017 | Info | Loosening Not Configured | Loosening is not configured in the selected tightening program | Select different tightening program. | Log Display Conf | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC ToolsControl | Tightening Process
4020 | Info | Too Many NOK Tightenings | Maximum consecutive NOK tightenings in batch is exceeded |  | Log Display Conf | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC ToolsControl | Tightening Process
4021 | Info | Too many consecutive loosenings | Maximum consecutive loosenings configured in General Virtual Station has been reached | An external input has to unlock and reset by signal Reset too many loosening lock or Master unlock. | Log Display Conf | Flex IxB Power Focus 6000 Power Focus 8 Sync Power Focus XC ToolsControl | Group
4025 | Info | No Tightening Program Selected | No tightening program selected. | Select tightening program or batch sequence. | Display Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tightening Process
4030 | Info | Batch Sequence Aborted | The batch sequence has been aborted. |  | Log Conf | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC Power Focus HC ToolsControl | Tightening Process
4031 | Info | Max Time To Complete Batch Sequence Reached |  |  | Log Display Conf | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC ToolsControl | Tightening Process
4032 | Info | Max Time To Complete First Tightening Reached |  |  | Log Display Conf | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC ToolsControl | Tightening Process
4035 | Info | Locked By Line Control |  |  | Log Display Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tightening Process
4040 | Info | Locked By Alternative Identifier | Tool locked by alternative identifier. |  | Log Display Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tightening Process
4050 |  | Invalid Socket Configuration | Tightening program assigned to multiple sockets. | Tightening program assigned to multiple sockets. | Log Display Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tightening Process
4060 | Info | Tool Locked On Batch Complete | When running a batch with flag Tool lock on batch sequence complete this event is generated when the user press the trigger. | Unlock with signal Unlock Tool on complete. | Log Display Conf | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC ToolsControl | Tightening Process
4062 | Info | Tool Locked By Result Synchronization | Results from tool are being synchronized with the controller. | Wait until result sync is done to restart work. | Log Display Conf Ack | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC ToolsControl | Tightening Process
4063 | Info | Tool Locked due to transducer redundancy error | Tool is locked due toredundancy error. |  | Log Display | Power Focus 6000 ToolsControl |
4064 | Info | Tool Locked by Automation Rules | Tool is locked by Automation rules. | No action | Log Display Conf | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC ToolsControl |
4065 | Info | Tool locked by test tightening | Tool is started when test tightening mode is active. | Exit test tightening | Log Conf Display | Flex Synchronized tightening | Tightening Process
4070 | Info | Process Enter Manual Mode | Indicates that manual mode has been activated for a virtual station. |  | Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tightening Process
4071 | Info | Process Enter Automatic Mode | Indicates that automatic mode has been entered for a virtual station. |  | Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tightening Process
4072 | Info | Test Bolt |  |  | Conf | Flex Synchronized tightening | Tightening Process
4073 | Info | Tool zero position updated | Indicates that the tool zero position is set using signals. |  | Conf | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC ToolsControl | Tightening Process
4100 | Warning | Identifier Not Accepted: Invalid String Length |  |  | Display Conf | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC ToolsControl | Tightening Process
4101 | Warning | String Selection Unsuccessful: Multiple Matches |  |  | Display Conf | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC ToolsControl | Tightening Process
4102 | Warning | String Selection Unsuccessful: No Match Found |  |  | Display Conf | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC ToolsControl | Tightening Process
4103 | Warning | Identifier Not Accepted: Identical String Already Received |  |  | Display Conf | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC ToolsControl | Tightening Process
4104 | Warning | Identifier Not Accepted: No Match Found |  |  | Display Conf | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC ToolsControl | Tightening Process
4105 | Warning | Assembly task selection unsuccessful: No match found |  |  | Log Conf Display | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening ToolsControl | Controller
4106 | Warning | Assembly task selection unsuccessful: Multiple matches |  |  | Log Conf Display | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening ToolsControl | Controller
4107 | Warning | Wrong location for selected assembly task | The assembly work task has been configured to use device location to validate but not select assembly tasks. The selected assembly task is allowed to start when the controller/tool is at the expected location. | Move the controller to the expected work zone. | Log Conf Display | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening ToolsControl | Controller
4108 | Warning | The assembly work task has been deleted | The active assembly work task (selected in the virtual station) has been deleted. | Select the new/correct assembly work task as the task in the virtual station. | Log Conf Display | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening ToolsControl | Controller
4109 | Warning | The assembly task has already been completed |  |  | Log Conf Display | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening ToolsControl | Controller
4110 | Warning | The selected assembly task is uncompleted | New input has been provided to the controller suggesting that a new assembly task should be selected when one is already selected and in progress (i.e. at least one tightening has been performed). | Return to the work zone and complete the started assembly task or abort it to be able to select another assembly task. | Log Conf Display | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening ToolsControl | Controller
4111 | Warning | Invalid assembly task priorities | In the controller there are at least two different assembly tasks which are configured with the same priority value. This is not allowed if the assembly tasks are supposed to be selected together one after the other i.e. a multiselection. | Check the assembly task configurations. | Log Conf Display | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening ToolsControl | Controller
4112 | Warning | PAT build data has been requested | The assembly work task has been configured to request new PAT build data when an unknown product identifier is provided to the controller. Such a request has been made and while in progress the tool will be locked until it either succeeds or time out. | Wait for request to complete or time out. | Log Conf Display | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening ToolsControl | Controller
4113 | Warning | PAT build data is missing | The assembly work task has been configured to request new PAT build data when an unknown product identifier is provided to the controller. Such a request has been made and was unsuccessful i.e. the provided product identifier is still unknown. | Check PAT build data and data/logs in customer upper layer system | Log Conf Display | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening ToolsControl | Controller
4114 | Warning | External dependencies not ready | The assembly task has been configured to require clearance from a customer upper layer system before it is allowed to be selected. | Check PAT build data and data/logs in customer upper layer system | Log Conf Display | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening ToolsControl | Controller
4115 | Warning | No assembly task selected |  |  | Log Conf Display | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening ToolsControl | Controller
4116 | Warning | Assembly task aborted, process timer expired | The assembly task has been configured to use one or more process timers which will trigger an abort if not satisfied in time. See the assembly task configuration for more details. |  | Log Conf Display | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening ToolsControl | Controller
4117 | Warning | Assembly task resume error, abort required | The assembly task to resume (or the parent assembly work task) has been modified in such as way that it cannot be resumed. An abort is required to confirm this, which will then allow new assembly task selections to be made. | Preform an abort. On IXB tools this can be done in the batch operations menu the EHMI/RHMI. | Log Conf Display | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening ToolsControl | Controller
4119 | Warning | Assembly task not found | The list of assembly task IDs in the assembly work task contains at least one invalid ID (the corresponding assembly task does not exist in the controller). | Check the assembly work task configuration | Log Conf Display | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening ToolsControl | Controller
4120 | Warning | Assembly task configuration error | General error code for an unknown assembly task configuration error. | Check the assembly task configurations. See the worktask log for details. | Log Conf Display | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening ToolsControl | Controller
4121 | Warning | Tightening task not set for assembly task | An assembly task doesn't have a tightening task (tightening program or batch sequence etc.) configured. | Check the assembly task configurations. | Log Conf Display | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening ToolsControl | Controller
4122 | Warning | Tightening task not found for assembly task | The id of the configured tightening task in an assembly task is invalid (the corresponding tightening task doesn't exist in the controller). | Check the assembly task configurations. | Log Conf Display | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening ToolsControl | Controller
4123 | Warning | Assembly task has no joint ids | An assembly task is configured to use "Batch control - Joint id" but no joint ids have been configured and none can be found in the PAT build data. | Check the assembly task configurations and PAT build data. | Log Conf Display | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening ToolsControl | Controller
4500 | Info | Result DriveError | Internal driver error or driver loss detected. |  | Conf | Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tightening Process
4501 | Info | Result Rehit | Attempt to tighten an already tightened bolt when Rehit detection is on. | Step Category for the Start Stage must be set to Soft Start. | Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tightening Process
4502 | Info | Result Soft Start Torque Low | Soft start torque below minimum level. |  | Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tightening Process
4503 | Info | Result Soft Start Torque High | Soft start torque exceeded maximum level. |  | Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tightening Process
4504 | Info | Result Self Tap Torque High | Self-tap torque exceeded maximum level. |  | Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tightening Process
4505 | Info | Result Self Tap Torque Low | Self-tap torque below minimum limit. |  | Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tightening Process
4506 | Info | Result Safety Torque Low | Automatically calculated torque value to ensure torque sensor is mounted correctly. |  | Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tightening Process
4507 | Info | Result Rundown Torque High | Rundown torque exceeded maximum level. |  | Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tightening Process
4508 | Info | Result Rundown Angle High | Rundown angle exceeded maximum level. |  | Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tightening Process
4509 | Info | Result Rundown Time High | Rundown time exceeded maximum limit. |  | Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tightening Process
4510 | Info | Result Rundown Time Low | Rundown time below minimum limit. |  | Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tightening Process
4511 | Info | Result Rundown Torque Low | Rundown torque below minimum level. |  | Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tightening Process
4512 | Info | Result Rundown Angle Low | Rundown angle below minimum level. |  | Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tightening Process
4513 | Info | Result Final Torque High | Final step torque exceeded maximum level. |  | Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tightening Process
4514 | Info | Result Final Angle High | Final step angle exceeded maximum level. |  | Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tightening Process
4515 | Info | Result Final Torque Low | Final step torque below minimum level. |  | Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tightening Process
4516 | Info | Result Final Angle Low | Final step angle below minimum level. |  | Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tightening Process
4517 | Info | Result Tightening Timeout | Tightening time limit exceeded. For General Tightening Strategies max tightening time is 30 seconds. For Multistep max tightening time depends on step restriction Maximum Time Limit. Error code is dependent on tightening stage. | Redo tightening. | Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tightening Process
4518 | Info | Result Trigger Lost | Tool trigger was released before target was reached. For General Tightening Strategies it is not allowed to release the trigger before the tightening stage has finished. For Multistep, the error is displayed when trigger is lost before the target in a specific step is reached. |  | Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tightening Process
4519 | Info | Premature Torque Loss | Socket has slipped off the nut. |  | Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tightening Process
4520 | Info | Result Target Reached Before Final Step | Target torque reached before final step in tightening program. |  | Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tightening Process
4521 | Info | Result Post View Torque Low | Post view torque below minimum level. |  | Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tightening Process
4522 | Info | Result Post View Torque High | Post view torque exceeded maximum level. |  | Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tightening Process
4523 | Info | Result Post View Torque Interval Not Reached | Post view torque interval not reached. |  | Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tightening Process
4524 | Info | Result Torque Compensation Interval Not Reached | Torque compensation interval angle before rundown end not reached. |  | Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tightening Process
4525 | Info | Result Tool Movement Exceeded | From a NOK tightening detailed status. |  | Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tightening Process
4526 | Info | Result SafetyCurrMon Sensor Mismatch | Current monitoring error. |  |  | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tightening Process
4527 | Info | Result Tool Movement Exceeded |  |  |  | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tightening Process
4538 | Info | Result Final Supervision Torque Low | Final Supervision Torque was not reached. |  | Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tightening Process
4543 | Info | Result Snug Monitor High | Wrench only. Monitor detected snug value exceeded. |  | Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tightening Process
4545 | Info | Result No Residual Torque | Wrench only. Residual torque was under threshold. |  | Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tightening Process
4546 | Info | Result Overspeed | Wrench only. Wrench gyro failed to measure angle due to high speed. |  | Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tightening Process
4547 | Info | Result Effective Loosening | Wrench only. Wrench detected unexpected loosening. |  | Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tightening Process
4548 | Info | Result Final Less Than Target | Final torque is below target torque set in tightening program. |  | Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tightening Process
4549 | Info | TurboTight Time Limit Exceeded |  |  | Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tightening Process
4550 | Info | Result Rundown Pulses High | Maximum number of rundown pulses is exceeded. |  | Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tightening Process
4551 | Info | Result Rundown Pulses Low | Rundown is completed before the minimum number of rundown pulses is reached. |  | Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tightening Process
4552 | Info | Result Final Pulses High | Maximum number of pulses is exceeded. |  | Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tightening Process
4553 | Info | Result Final Pulses Low | Tightening is completed before the minimum number of pulses is reached. |  | Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tightening Process
4554 | Info | Current At Shutoff High | Current at shut off exceeded Current Limit High. |  | Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tightening Process
4555 | Info | Current At Shutoff Low | Shut off current measured was below Current Limit Low. |  | Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tightening Process
4556 | Info | Uncategorized Multistep Error | An error in the multistep configuration, often with tool validation. |  | Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tightening Process
4557 | Info | Result Overload |  |  | Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tightening Process
4559 | Info | Result Stopped | The event is triggered when an external stop signal or lock signal is aborting an ongoing tightening. The event is introduced to distinguish between trigger loss and external stop. |  | Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Tightening Process
4600 | Warning | Data Drop or Data Hold used in combination with Batch Tightening. The signals have no effect |  | Data Drop and Data Hold are only supported for worktasks, without batch control. Select another worktask if the signals must be used. |  | Flex Synchronized tightening | Tightening Process
4601 | Info | Data Hold Active: tightening result is sent once signal is low |  |  |  | Flex Synchronized tightening | Tightening Process
4602 | Info | Data Drop active: tightening result discarded |  |  |  | Flex Synchronized tightening | Tightening Process
5010 | Warning | Invalid Tightening Program Parameter Value | The parameter in the selected tightening program are invalid. | Check the configuration of the selected tightening program to find and to change the value of the parameter. | Log Display Conf | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC Power Focus HC ToolsControl | Program Configuration
5011 | Warning | Couldn't prepare program storage in tool | It is not possible to read the current program storage size in the tool, or to prepare the program storage for downloading the updated, or newly selected program to the tool. | Check the tool for supported software version. Reboot the tool. Select the tightening program again. Check network connection for data consistency and quality. | Log Display Conf | Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Program Configuration
5020 | Info | Main Trigger Is Not The Active Start Source | Generated when configured for push start only and user presses main trigger. Will be generated until user presses the push start. | Press push start to start the tool. | Log Display Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Program Configuration
5030 | Info | Tightening Program Complexity Exceeds Tool Capacity | The selected tightening program is too complex for the STB tool that is used. Tool will be locked. | Reduce complexity of the tightening program, or choose different program. | Log Display Conf | Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Program Configuration
6010 | Info | Accessory Connected | Accessory is connected to the controller. |  | Log Display Ack Conf | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC ToolsControl | Accessory
6020 | Info | Accessory Disconnected | Accessory is disconnected from the controller. |  | Log Display Ack Conf | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC ToolsControl | Accessory
6021 | Warning | Fieldbus Offline | No communication with Fieldbus. |  | Log Display Ack Conf | Flex Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC | Accessory
6030 | Warning | Accessory Address Collision | Two or more accessories with the same address are connected. | Change address on accessory. | Log Display Ack Conf | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC ToolsControl | Accessory
6040 | Warning | Accessory Communication Error | Intermittent communication error with accessory. | Check cables and connectors. | Log Display Conf | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC ToolsControl | Accessory
6041 | Warning | Fieldbus Error | Communication error with Fieldbus. |  | Log Display Ack Conf | Flex Power Focus 6000 Power Focus 8 Synchronized tightening | Accessory
6042 | Warning | Fieldbus Module Mismatch | The installed Fieldbus module does not match with the configured module. | Change the configuration to match with the installed module, or replace the installed module with the correct one. | Log Display Ack Conf | Flex Power Focus 6000 Power Focus 8 Synchronized tightening | Accessory
6043 | Warning | Fieldbus Output Buffer Overflow | The output buffer used for the Fieldbus communication is exhausted and an overflow of the buffer has occurred. One or more signal updates have been discarded. | Stop Fieldbus communication and Fieldbus diagnostics (if used) to recover the buffer. If this event occurs frequently, check your Fieldbus communication setup, including the PLC program: too frequent updates compared to your update interval can lead to this scenario. | Log Display Ack Conf | Flex Power Focus 6000 Power Focus 8 Synchronized tightening | Accessory
6044 | Warning | Fieldbus Provider ID mismatch | The installed Fieldbus module is not supported. | Connect a supported Atlas Copco fieldbus module. | Log Display Ack | Power Focus 8 | Accessory
6050 | Info | Wrong Socket Selected | Generated when no or incorrect socket is selected. |  | Log Display Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Accessory
6090 | Warning | Barcode Scanner Could Not Be Identified | When no unique serial number is found. | Configure the barcode reader device. | Log Display Ack Conf | Flex Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC Power Focus HC | Accessory
6500 | Warning | Invalid Rule Configuration | Rule configuration is invalid if the virtual station mapped does not exist, invalid cease configuration or if the rule has no triggers or no actions | Verify the configuration of the tool. | Log Display Conf | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC ToolsControl |
6501 | Warning | Rule Triggered While Running | Running rule is re-triggered by the same trigger. | Disable and enable the rule. | Log Conf | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC ToolsControl |
6502 | Info | Failed to execute Action | Rule fails to execute an event when it cannot perform an action on a deleted or non-existent virtual station. This occurs when the virtual station configured for the rule has been removed. | Action is corrected rule is disabled and enabled. | Log Display Conf | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC ToolsControl |
6503 | Warning | Running Rule Deleted | This event occurs if a currently running rule is deleted. The action will not be reset if running rule is deleted. | No action. | Log Conf | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC ToolsControl |
6504 | Warning | Running Rule Disabled | This event occurs if a currently running rule is disabled. The action will not be reset if running rule is disabled. | No action. | Log Conf | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC ToolsControl |
6505 | Warning | Running Rule Updated | Running rule updated event if a currently running rule is updated. | No action. | Log Conf | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC ToolsControl |
7010 | Info | Message Text To Display | General event for displaying of messages. |  | Display Ack Conf | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC Power Focus HC ToolsControl | Message
8135 | Info | Machine capability test mode activated | Machine capability test mode has been activated. The mode allows targeted steps within a multistage configuration to not be executed while the mode is active. | Activate Machine capability test mode. | Log Conf Display Ack | Power Focus 6000 Power Focus 8 Flex Power Focus XC IxB XB | Controller
8136 | Info | Machine capability test mode deactivated | Machine capability test mode has been deactivated. All steps within a multistage program will be executed as normal. | Deactivate Machine capability test mode. | Log Conf Display Ack | Power Focus 6000 Power Focus 8 Flex Power Focus XC IxB XB | Controller
8200 | Info | Failed To Open Serial Port | Serial port to be used could not be opened. | Check serial port connections. | Display Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC | Miscellaneous
8300 | Warning | Open Protocol client communication timed out | Communication to an Open Protocol client has timed out. No keep alive message or command sent within expected time. | Check controller network connection. Check network setup: firewall and switches. Check client side application software. | Log Display Conf | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC ToolsControl | Miscellaneous
8214 | Error | EHMI Software Version Mismatch | EHMI software version does not match in compatibility with the controller. | Update the software version of the EHMI. | Log Display Ack Conf | IxB Power Focus 6000 Power Focus 8 Power Focus XC ToolsControl | Miscellaneous
8400 | Info | Controller event | Deleted configuration history. |  | Log Display Conf | Flex IxB Power Focus 6000 Power Focus 8 Synchronized tightening Power Focus XC Power Focus HC ToolsControl STRw Sync | Controller

## Glossary

Conf - Event Codes list

Tells the user whether it is possible to configure the event through the "Configure Event" page.

Available for - Event Codes list

List of products for which the event code is available.

Groups - Event Codes list

Group which the event codes belong to.

Event Description

A short description of the event and why it occurs.

Procedure - Event Codes list

If applicable, the procedure contains an instruction on how to clear the event.

Log - Event Codes list

Tells the user whether the event is to be saved in the event log or not. The value in this list is the default value.

display - Event Codes list

Tells the user whether the event is to be displayed on the screen or not. The value in this list is the default value.

Ack - Event Codes list

Tells the user whether the event must be acknowledged or not before you can proceed. The value in this list is the default value.

Event code

The unique event number.

Type of events - Event Codes list

Type of event: Info, Warning, and Error.

Event name

A descriptive name of the event.

# Input Signals Used by the Fieldbus

Code | Input signal | Type | Description | PF 6000 | PF 600
--- | --- | --- | --- | --- | ---
20020 | Field bus lock tightening | State | Acknowledgement of an event. | X |
20021 | Field bus lock loosening | State | Unlocks most locks defined in lock page. | X |
30000 | Disable tool | State | Disable tool. | X | X
30001 | Event code | State | Event code | X | X
30002 | Fieldbus Keep Alive | State | Fieldbus keep alive | X | X
30003 | Event Code Severity | State | Event code severity | X | X
31000 | Tightening OK | State | Tightening OK. | X | X
31001 | Tightening NOK | State | Tightening NOK. | X | X
31002 | Final torque | State | Final torque. | X | X
31003 | Final Angle | State | Final angle. | X | X
31004 | Tightening Program Max Angle | State | Tightening Program max angle. | X | X
31005 | Tightening Program Min Angle | State | Tightening Program min angle. | X | X
31006 | Final Angle Status | State | Final angle status. | X | X
31007 | Tightening Program Max Torque | State | Tightening Program max torque. | X | X
31008 | Tightening Program Min Torque | State | Tightening Program min torque. | X | X
31009 | Final Torque Status | State | Final torque status. | X | X
31039 | Rundown angle high | Event | Rundown angle high | X | X
31040 | Rundown angle low | Event | Rundown angle low | X | X
31027 | Tightening time high | Event | Tightening time high | X | X
31028 | Tightening time low | Event | Tightening time low | X | X

# Input Signals

Converter
Signal Type
Value Type
Size Min [bit]
Size Max [bit]
Devices
Search

# Abort Sequence - 10012

When a Batch sequence abort request is received, the Batch sequence functionality aborts the batch sequence only after getting the ongoing tightening result.

Name in SoftPLC: ABORT_BATCH_SEQUENCE

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Abort Sequence and Clear Results - 10127

When signal "Abort sequence and clear results" is set, the ongoing sequence is aborted and signals related to "Clear results" are cleared.

Name in SoftPLC:ABORT_SEQ_AND_CLEAR_RES

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Acknowledge Events - 10004

Acknowledge of an event.

Name in SoftPLC: ACKNOWLEDGE_EVENT

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Activate Tool Scanner - 10075

Activates the tool scanner through an external source.

Name in SoftPLC: ACTIVATE_TOOL_SCANNER

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Batch Decrement - 10002

Incrementally decreases the batch counter by one.

Name in SoftPLC: BATCH_DECREMENT

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Batch Increment - 10001

Incrementally increases the batch counter by one.

Name in SoftPLC: BATCH_INCREMENT

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Bypass Identifier - 10123

In source batch string used to bypass an identifier string in string receiving sequence.

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Bypass Tightening Program - 10008

Skips the next tightening program in the running batch sequence.

Name in SoftPLC: BYPASS_PSET

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Channel Command - 10054

Channel Command is an input signal that inhibits individual tools and prevents that those tools are included in the next tightening. It is also possible to replace the tightening program or bolt number configured in the sync mode configuration. Up to 64 channels are supported.

Name in SoftPLC: CHANNEL_COMMAND

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | uint32 array | 1 | 64

The signal Channel Command -10054 contains sub-signals (for more information, see "Input Signals: Sub-signals").

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Continue Step - 10128

Continue Step is an input signal that stops the Wait tightening step.
When the tightening has reached a Wait tightening step with the condition Signal configured as Wait Type, a rising edge of the signal Continue Step causes the system (one or more spindles) to release.

For more information, see the sub-signal Channel Command - 10054: Continue Step.

Name in SoftPLC: CONTINUE_STEP

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Data Hold - 10124

When signal DATAHOLD is set to true at the end of a tightening, transmission of the result data will be stopped.

Name in SoftPLC: DATAHOLD

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Data Drop - 10125

When set DATADROP to true at the end of a tightening DATADROP signal will drop result from the tightening. The result will not be stored persistently or sent to any device or clients like ToolsNet or protocol adapters.

Name in SoftPLC: DATADROP

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Disable Fieldbus - 10049

Disables the fieldbus.

Name in SoftPLC: DISABLE_FIELDBUS

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: FALSE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Disable Loosening at OK Tight - 20022

This lock signal is used to disable loosening after an OK tightening.

Name in SoftPLC:

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Disable Test Bolt - 10057

Name in SoftPLC: DISABLE_TESTBOLT

Converter | Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | --- | ---
Standard | State | Boolean | 1 | 1
Invert | State | Boolean | 1 | 1

To avoid duplicating signals, it is possible to define Value Converters.

Converters are used to support more than one representation of the same signal (for example Angle/Torque Status can both be represented bitwise or as a status character).

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Disable tool - 30000

If the signal is set to True, a tool is immediately stopped and locked.

Converter | Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | --- | ---
Standard | State | Boolean | 1 | 1
Invert | State | Boolean | 1 | 1

To avoid duplicating signals, it is possible to define Value Converters.

Converters are used to support more than one representation of the same signal (for example Angle/Torque Status can both be represented bitwise or as a status character).

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Disable Tool Scanner - 10119

Disables tool scanner when scanning by tool trigger when signal is set. It is still possible to scan by using the scan button but the scan string is ignored.

Name in SoftPLC: DISABLE_TOOL_SCANNER

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# Dynamic Batch Size - 10074

Name in SoftPLC: DYNAMIC_BATCH_SIZE

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Integer | 1 | 16

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Enable Operation - 10055

Name in SoftPLC: ENABLE_OPERATION

Converter | Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | --- | ---
Standard | State | Boolean | 1 | 1
Invert | State | Boolean | 1 | 1

To avoid duplicating signals, it is possible to define Value Converters.

Converters are used to support more than one representation of the same signal (for example Angle/Torque Status can both be represented bitwise or as a status character).

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# External OK - 10063

Name in SoftPLC: EXTERNAL_OK

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Fieldbus AsyncData To PF - 10077

Name in SoftPLC:

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | uint8 array | 16 | 2048

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Fieldbus Lock Loosening - 20021

A Virtual Station is locked when starting a loosening if the signal is set from a connected and supported accessory.
An ongoing loosening is aborted immediately when Fieldbus Lock Loosening is set to True, due to the Stop Drive setting.

Converter | Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | --- | ---
Standard | State | Boolean | 1 | 1
Invert | State | Boolean | 1 | 1

To avoid duplicating signals, it is possible to define Value Converters.

Converters are used to support more than one representation of the same signal (for example Angle/Torque Status can both be represented bitwise or as a status character).

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Fieldbus Lock Tightening - 20020

A Virtual Station is locked when starting a tightening if the signal is set from a connected and supported accessory.
An ongoing tightening is aborted immediately when Fieldbus Lock Tightening is set to True, due to the Stop Drive setting.

Converter | Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | --- | ---
Standard | State | Boolean | 1 | 1
Invert | State | Boolean | 1 | 1

To avoid duplicating signals, it is possible to define Value Converters.

Converters are used to support more than one representation of the same signal (for example Angle/Torque Status can both be represented bitwise or as a status character).

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Flush Read Result Queue - 30005

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# ID for Dynamic Batch Size - 10073

Name in SoftPLC: DYNAMIC_BATCH_SIZE_TPID

Converter | Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | --- | ---
Standard | State | Integer | 1 | 16
TreatZeroAsOne | State | Integer | 1 | 16

To avoid duplicating signals, it is possible to define Value Converters.

Converters are used to support more than one representation of the same signal (for example Angle/Torque Status can both be represented bitwise or as a status character).

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Lock Loosening - 20003

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: FALSE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Lock Tightening - 20002

Tool locked for tightening by digital input.

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: FALSE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Lock Tool Active High - 20004

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: FALSE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Lock Tool Active Low - 20061

Locks the tool when this signal is low.

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: FALSE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Manual Mode - 10061

Used to set the Virtual Station in manual mode.

If the signal is True (high) the signal 101 - Manual mode is high.
If the signal is False (low) the signal 101 - Manual mode is low.

Name in SoftPLC: SET_MANUAL_MODE

Converter | Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | --- | ---
Standard | State | Boolean | 1 | 1
Invert | State | Boolean | 1 | 1

To avoid duplicating signals, it is possible to define Value Converters.

Converters are used to support more than one representation of the same signal (for example Angle/Torque Status can both be represented bitwise or as a status character).

Relevant Information

- Manual Mode - 101

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Master Unlock - 10005

Master Unlock is an input signal which unlocks the following functions and signals.

FUNCTIONS:

- Disable loosening at OK tightening

- Disable loosening at NOK tightening

- Disable tightening

- Max consecutive NOK

- Tool Lock on Sequence complete

SIGNALS:

- 20001 - Pending Event Acknowledge Lock

- 20002 - Lock Tightening

- 20003 - Lock Loosening

- 20004 - Lock Tool Active High

- 20013 - WorkTask Lock Tightening

- 20014 - WorkTask Lock Loosening

- 20015 - Batch Done lLock

- 20018 - Open Protocol Lock

- 20020 - Fieldbus Lock Tightening

- 20021 - Fieldbus Lock Loosening

- 20022 - Disable Loosening At OK Tight

- 20023 - Too Many NOK Tightenings Lock

- 20033 - Line Control Lock

- 20034 - Locked By Alternative Identifier

Name in SoftPLC: MASTER_UNLOCK

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Pulse Stop - 10030

If this signal is generated any ongoing tightening or loosening will be stopped. Used in combination with 10024 or 10072.

Name in SoftPLC: TIGHTENING_STOP_PULSE

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Read Result Handshake Ack - 30004

Enable the Read Result Handshake feature in the Fieldbus device for making the controller available for the signal Rear Result Handshake Ack.

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Reset All Identifiers - 10115

In Source batch string used to reset all received string identifiers from string receiving sequence at once. In other worktasks clears VIN number.

Name in SoftPLC: RESET_ALL_IDENTIFIERS

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Reset Batch - 10003

Resets the batch counter to 0. No batch OK (nxOK). If batch OK is activated, it will be deactivated.

Name in SoftPLC: RESET_BATCH

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Reset Batch Sequence - 10053

Resets the Batch Sequence. Unlocks a tool that is locked by Tool Lock on Complete.

Name in SoftPLC: RESET_BATCH_SEQUENCE

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Reset Bistable Relay - 10022

Reset the bistable relay output.

Name in SoftPLC: RESET_BISTABLE_RELAY

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Reset Cycle Status - 10056

Name in SoftPLC: RESET_CYCLE_STATUS

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Reset Latest Identifier - 10114

In Source batch string used to reset latest received string from string receiving sequence. In other worktasks clears VIN number.

Name in SoftPLC: RESET_LATEST_IDENTIFIER

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Reset Relays - 10120

Resets all signals.

Name in SoftPLC: RESET_RELAYS

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Reset Sequence Status - 10118

Resets signals Batch Sequence Done/OK/NOK and Sequence Aborted.

Name in SoftPLC: RESET_SEQUENCE_STATUS

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Reset System Error - 10062

Name in SoftPLC: RESET_SYSTEM_ERROR

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Reset Too Many NOK - 10013

Reset the batch after receiving lock Too Many NOK

Name in SoftPLC: RESET_TOO_MANY_NOK

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Select Input - 10020

Selects Tightening Program withing Source Tightening/Batch within sequence.

Name in SoftPLC: SELECT_INPUT_VALUE

Converter | Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | --- | ---
Standard | State | Integer | 1 | 16
TreatZeroAsOne | State | Integer | 1 | 1

To avoid duplicating signals, it is possible to define Value Converters.

Converters are used to support more than one representation of the same signal (for example Angle/Torque Status can both be represented bitwise or as a status character).

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: TRUE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Select Input and Dynamic Batch Size - 30007

It is used to set the Batch Size for a specific "Identifier Number" in a Source Tightening Task, running "External batch control".

Batch size can be set to 1-250.

If Batch size is set to 0, it is treated as infinite batch. The user is not able to un-set a Batch back to a state where it has no size, once it has been set.

Converter | Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | --- | ---
Standard | State | Integer | 16 | 16
TreatZeroAsOne | State | Integer | 16 | 16

To avoid duplicating signals, it is possible to define Value Converters.

Converters are used to support more than one representation of the same signal (for example Angle/Torque Status can both be represented bitwise or as a status character).

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Select Input Bit 0 - 10016

Name in SoftPLC: SEL_INPUT_BIT_0

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: FALSE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Select Input Bit 1 - 10017

Name in SoftPLC: SEL_INPUT_BIT_1

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: FALSE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Select Input Bit 2 - 10018

Name in SoftPLC: SEL_INPUT_BIT_2

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: FALSE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Select Input Bit 3 - 10019

Name in SoftPLC: SEL_INPUT_BIT_3

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: FALSE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Select Input Bit 4 - 10066

Name in SoftPLC: SEL_INPUT_BIT_4

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: FALSE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Select Input Bit 5 - 10067

Name in SoftPLC: SEL_INPUT_BIT_5

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: FALSE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Select Input Bit 6 - 10068

Name in SoftPLC: SEL_INPUT_BIT_6

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: FALSE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Select Input Bit 7 - 10069

Name in SoftPLC: SEL_INPUT_BIT_7

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: FALSE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Select Input Bit 8 - 10070

Name in SoftPLC: SEL_INPUT_BIT_8

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: FALSE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Select Input Bit 9 - 10071

Name in SoftPLC: SEL_INPUT_BIT_9

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: FALSE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Select Loosening - 10029

Selects loosening as default operation mode and used in combination with Start Tools -10028 signal.

Name in SoftPLC: SELECT_LOOSENING

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

Relevant Information

- Start Tools - 10028

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Select Next Identifier Number - 10116

It is possible to use the signal Select Next Identifier Number when a task in the virtual station is configured as:

- Batch Sequence

- Source Tightening

- Source Batch

  - Number Identifier method

  - String Identifier method

ST Selector configurable functions Take Next and Take Previous enable the input signals Select Next Identifier Number and Select Previous Identifier Number.

## Batch Sequence selected as Virtual Station Task

If Free Order switch has been enabled, the signal Select Next Identifier Number can select different batches within the selected sequence.

Before selecting batches, it is mandatory that they have the identifier number assigned. If a batch does not have the identifier number assigned, the signal Select Next Identifier Number cannot select it, even if Free Order switch is enabled.

It enables looping through the batches that have a configured identifier number.
If identifier number is "None", it is possible to select it only after all Batches with configured identifier number are completed.

It is possible to do looping, but 0 is skipped. When a batch is finished, it is no longer selectable.

For example, in case of batches with assigned identifier numbers 1,2,4,5, the signal runs in loop: 1,2,4,5,1,2,4... as long as the batches are not finished.

## Source Tightening selected as Virtual Station Task

The signal selects the next identifier number from the list of tightening programs specified in the Source Tightening task.
The selection runs from the currently selected identifier number to the next larger one.

When the biggest identifier number is selected, this signal selects 0; after 0, the signal selects the next bigger identifier number.

If 0 is selected as identifier number, the tool is locked.

If the identifier number has been added to the Source Tightening list, but no tightening program has ever been assigned to it, it is skipped while looping through the Source Tightening list.

If the tightening program is assigned to an identifier number and then it is removed from the list of tightening programs, it is still possible to select this identifier number. In this case, the tool is locked because there is not a specific tightening program.

When Selector Mode switch is set to Confirm, the socket selector needs to be assigned and configured. All tightening programs can be selected, but before running them, appropriate socket must be lifted from the socket selector.

## Source Batch selected as Virtual Station Task

In Sources > Batch Sequence > Source Batch, when the identifier method is set to Number, the signal Select Next Identifier Number selects sequences from a list of sequences shown in Source Batch task.

It is possible to do looping through 0. The signal Select Next Identifier Number selects only the identifier numbers assigned to sequences.

For example, if there are 4 sequences available with identifier numbers 1,2,4, and 8, the signal Select Next Identifier Number iterates and selects 1,2,4,8,0,1,2...

The identifier numbers not defined are not selected.

In Sources > Batch Sequence > Source Batch, when the identifier method is set to String, it is necessary to select the sequence through external sources (like scanner or Open Protocol). The signal Select Next Identifier Number is able to select the batches within the selected sequence.

Name in SoftPLC: SELECT_NEXT_ID_NUMBER

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: TRUE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Select Previous Identifier Number - 10117

It is possible to use the signal Select Previous Identifier Number when a task in the virtual station is configured as:

- Batch Sequence

- Source Tightening

- Source Batch

  - Number Identifier method

  - String Identifier method

ST Selector configurable functions Take Next and Take Previous enable the input signals Select Next Identifier Number and Select Previous Identifier Number.

## Batch Sequence selected as Virtual Station Task

If Free Order switch has been enabled, the signal Select Previous Identifier Number can select different batches within the selected sequence.

Before selecting batches, it is mandatory that they have the identifier number assigned. If a batch does not have the identifier number assigned, the signal Select Previous Identifier Number cannot select it, even if Free Order switch is enabled.

It enables looping through the batches that have a configured identifier number.
If identifier number is "None", it is possible to select it only after all Batches with configured identifier number are completed.

It is possible to do looping, but 0 is skipped. When a batch is finished, it is no longer selectable.

For example, in case of batches with assigned identifier numbers 1,2,4,5, the signal runs in loop: 5,4,2,1,5,4,2... as long as the batches are not finished.

## Source Tightening selected as Virtual Station Task

The signal selects the previous identifier number from the list of tightening programs specified in the Source Tightening task.
The selection runs from the currently selected identifier number to the previous lower one.

When the smallest identifier number is selected, this signal selects 0; after 0, the signal selects the next smaller identifier number.

If 0 is selected as identifier number, the tool is locked.

If the tightening program is assigned to an identifier number and then it is removed from the list of tightening programs, it is still possible to select this identifier number. In this case, the tool is locked because there is not a specific tightening program.

When Selector Mode switch is set to Confirm, the socket selector needs to be assigned and configured. All tightening programs can be selected, but before running them, appropriate socket must be lifted from the socket selector.

## Source Batch selected as Virtual Station Task

In Sources > Batch Sequence > Source Batch, when the identifier method is set to Number, the signal Select Previous Identifier Number selects sequences from a list of sequences shown in Source Batch task.

It is possible to do looping through 0. The signal Select Previous Identifier Number selects only the identifier numbers assigned to sequences.

For example, if there are 4 sequences available with identifier numbers 1,2,4, and 8, the signal Select Previous Identifier Number iterates and selects 8,4,2,1,0,8,4...

The identifier numbers not defined are not selected.

In Sources > Batch Sequence > Source Batch, when the identifier method is set to String, it is necessary to select the sequence through external sources (like scanner or Open Protocol). The signal Select Previous Identifier Number is able to select the batches within the selected sequence.

Name in SoftPLC: SELECT_PREVIOUS_ID_NUMBER

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: TRUE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Set Bistable Relay - 10021

Set the bistable relay output.

Name in SoftPLC: SET_BISTABLE_RELAY

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Set CCW Direction - 10132

Set CCW Direction is an input signal which forces the SR21/SL tool to counterclockwise direction.

The SR21/SL tool is forced to counterclockwise direction only if, after being connected with the controller, the signal is set "high".
This operation is essential, even if the signal was set "high" before that the SR21/SL tool was connected with the controller.

If the tool is running clockwise, the signal will switch the direction to counterclockwise.
If the tool is running counterclockwise, the direction will not change.

Set CCW Direction overrides the input signal Toggle CW/CCW For Next Run.

If the signal is set "low", the tool will switch the direction to clockwise.

When the tool is set to counterclockwise, the orange direction LED on the tool lights up.

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Set Zero Position - 10135

For hand-held tools, the input signal Set Zero Position keeps the current position of the tools as home position. The signal is silently ignored if sent during an ongoing tightening.

For fixtured tools, the input signal Set Zero Position keeps the current position of the tools as home position. The signal affects all the tools in the system, regardless of the virtual station. The signal is silently ignored by fixtured tools that are part of an ongoing tightening.

Name in SoftPLC: IN_EXTERNAL_SET_ZERO_POSITION

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Socket Selector External Green Light - 10046

Controls green lights when socket selector is in external mode (how multiple physical devices are mapped to logical sockets are defined by the socket selector resource configuration).

- Byte0 - logical sockets 1-4

- Byte1 - logical sockets 5-8

- Byte2 - logical sockets 9-12

- Byte3 - logical sockets 13-16

- Byte4 - logical sockets 17-20

- Byte5 - logical sockets 21-24

- Byte6 - logical sockets 25-28

- Byte7 - logical sockets 29-32

2 bits per socket, 00=off, 01=flash, 10=solid

Name in SoftPLC: SOCKET_SEL_EXT_GREEN_LIGHT

Converter | Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | --- | ---
Standard | State | uint64 | 1 | 64
SocketLedControlTwoDevices | State | uint64 | 1 | 64

To avoid duplicating signals, it is possible to define Value Converters.

Converters are used to support more than one representation of the same signal (for example Angle/Torque Status can both be represented bitwise or as a status character).

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Socket Selector External Red Light - 10047

Controls red lights when socket selector is in external mode (how multiple physical devices are mapped to logical sockets are defined by the socket selector resource configuration).

- Byte0 - logical sockets 1-4

- Byte1 - logical sockets 5-8

- Byte2 - logical sockets 9-12

- Byte3 - logical sockets 13-16

- Byte4 - logical sockets 17-20

- Byte5 - logical sockets 21-24

- Byte6 - logical sockets 25-28

- Byte7 - logical sockets 29-32

2 bits per socket, 00=off, 01=flash, 10=solid

Name in SoftPLC: SOCKET_SEL_EXT_RED_LIGHT

Converter | Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | --- | ---
Standard | State | uint64 | 1 | 64
SocketLedControlTwoDevices | State | uint64 | 1 | 64

To avoid duplicating signals, it is possible to define Value Converters.

Converters are used to support more than one representation of the same signal (for example Angle/Torque Status can both be represented bitwise or as a status character).

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Start Loosening - 10011

Active signal starts loosening. Once digital input goes inactive the loosening must be stopped.

Name in SoftPLC: START_LOOSENING

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Start Loosening, Pulse - 10072

Name in SoftPLC: SELECT_PREVIOUS_ID_NUMBER

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: TRUE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Start Tightening - 10010

Active signal starts tightening. Once input goes inactive the tightening must be stopped.

Name in SoftPLC: START_TIGHTENING

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Start Tightening Pulse - 10024

The tightening starts at signal. Runs until the tightening is finished, or until the 30 sec timeout in tightening program occurs.

Name in SoftPLC: TIGHTENING_START_PULSE

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Start Tools - 10028

Active signal which starts the tool (default operation mode is tightening). As soon as signal goes inactive the tool must be stopped. Used in combination with Select Loosening - 10029 signal.

Name in SoftPLC: START_DRIVE_CONTINIOUS

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Start Tools, Pulse - 10113

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: TRUE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Stop (pulse) - 10129

If this signal is generated any ongoing tightening or loosening will be stopped. Used in combination with 10024 or 10072.

Name in SoftPLC: EXTERNAL_STOP_PULSE

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Stop (state) - 10133

If this signal is set, any ongoing tightening or loosening will be stopped. Will also block any start attempts while set high. Used in combination with 10024 or 10072.

Name in SoftPLC: IN_EXTERNAL_STOP_STATE

Converter | Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | --- | ---
Standard | State | Boolean | 1 | 1
Invert | State | Boolean | 1 | 1

To avoid duplicating signals, it is possible to define Value Converters.

Converters are used to support more than one representation of the same signal (for example Angle/Torque Status can both be represented bitwise or as a status character).

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# To SoftPLC - 10065

Name in SoftPLC: TO_PLC

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | uint8 array | 1 | 1

## Devices

- Fieldbus: FALSE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Toggle CW/CCW - 10130

Toggle CW/CCW is an input signal which toggles the direction of the SR21/SL tool.
If the tool is running clockwise, the signal will toggle the direction to counterclockwise.
If the tool is running counterclockwise, the signal will toggle the direction to clockwise.

Toggle CW/CCW overrides the input signal Toggle CW/CCW For Next Run.

When the tool is toggled to counterclockwise, the orange direction LED on the tool lights up.

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Toggle CW/CCW For Next Run - 10131

Toggle CW/CCW For Next Run is an input signal which toggles the direction of the SR21/SL tool for the next tightening/loosening.
If the tool is running clockwise, the signal will toggle the direction to counterclockwise.
If the tool is running counterclockwise, the signal will toggle the direction to clockwise.

When the next tightening/loosening is complete, the tool toggles back to the direction it was before the signal was sent.

When the tool is toggled to counterclockwise for the next tightening/loosening, the orange direction LED on the tool blinks.

It is possible to trigger the signal Toggle CW/CCW For Next Run only once.

When the signal toggles the tool direction, any other update of this signal will be neglected.

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Unlock Tool on Complete - 10051

Unlocks a tool that is locked by "Tool Lock on Complete".

Name in SoftPLC: UNLOCK_TOOL_ON_COMPLETE

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Unlock Tool on Disable - 10059

Name in SoftPLC: UNLOCK_TOOL_ON_DISABLE

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Output Signals

Converter
Signal Type
Value Type
Size Min [bit]
Size Max [bit]
Devices
Search

# Active Identifier String - 186

Set when an identifier string has been received and accepted by the work-task; it is necessary that even sequence or tightening program are running.
If running Source batch-string, it is set when all scans have been received and a sequence had been selected. In that case it includes concatenated string consisted of saved positions.
For other work-tasks it includes the “VIN” number.

Name in SoftPLC: ACTIVE_IDENTIFIER_STRING

Converter | Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | --- | ---
Standard | State | String | 8 | 800
IdentifierU32Hnw | State | String | 8 | 800
IdentifierU32 | State | String | 8 | 800

To avoid duplicating signals, it is possible to define Value Converters.

Converters are used to support more than one representation of the same signal (for example Angle/Torque Status can both be represented bitwise or as a status character).

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Active Identifier String 1 - 188

Signal corresponding to the first configured string in Source batch-string.
Active Identifier String 1 signal is sent once a scanning sequence is done and a sequence has been selected, thus the identifier parts are active.
The strings is filtered with saved position.
Only sent when running Source batch string.

Name in SoftPLC: ACTIVE_ID_STRING_1

Converter | Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | --- | ---
Standard | State | String | 8 | 800
IdentifierU32Hnw | State | String | 8 | 800
IdentifierU32 | State | String | 8 | 800

To avoid duplicating signals, it is possible to define Value Converters.

Converters are used to support more than one representation of the same signal (for example Angle/Torque Status can both be represented bitwise or as a status character).

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Active Identifier String 2 - 189

Signal corresponding to the second configured string in Source batch-string.
Active Identifier String 2 signal is sent once a scanning sequence is done and a sequence has been selected, thus the identifier parts are active.
The strings is filtered with saved position.
Only sent when running Source batch string.

Name in SoftPLC: ACTIVE_ID_STRING_2

Converter | Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | --- | ---
Standard | State | String | 8 | 800
IdentifierU32Hnw | State | String | 8 | 800
IdentifierU32 | State | String | 8 | 800

To avoid duplicating signals, it is possible to define Value Converters.

Converters are used to support more than one representation of the same signal (for example Angle/Torque Status can both be represented bitwise or as a status character).

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Active Identifier String 3 - 190

Signal corresponding to the third configured string in Source batch-string.
Active Identifier String 3 signal is sent once a scanning sequence is done and a sequence has been selected, thus the identifier parts are active.
The strings is filtered with saved position.
Only sent when running Source batch string.

Name in SoftPLC: ACTIVE_ID_STRING_3

Converter | Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | --- | ---
Standard | State | String | 8 | 800
IdentifierU32Hnw | State | String | 8 | 800
IdentifierU32 | State | String | 8 | 800

To avoid duplicating signals, it is possible to define Value Converters.

Converters are used to support more than one representation of the same signal (for example Angle/Torque Status can both be represented bitwise or as a status character).

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Active Identifier String 4 - 191

Signal corresponding to the fourth configured string in Source batch-string.
Active Identifier String 4 signal is sent once a scanning sequence is done and a sequence has been selected, thus the identifier parts are active.
The strings is filtered with saved position.
Only sent when running Source batch string.

Name in SoftPLC: ACTIVE_ID_STRING_4

Converter | Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | --- | ---
Standard | State | String | 8 | 800
IdentifierU32Hnw | State | String | 8 | 800
IdentifierU32 | State | String | 8 | 800

To avoid duplicating signals, it is possible to define Value Converters.

Converters are used to support more than one representation of the same signal (for example Angle/Torque Status can both be represented bitwise or as a status character).

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Activated Joint Id - 225

Set when a compatible task is configured and running with Joint Ids. When a program or batch is started where Joint Id is used, the signal is set with the corresponding configured Joint Id for the program that's is selected by an MES/Integrator/External system. The string indicates the currently active Joint Id and not the one in a result, please see “Joint Id Result - 31046” for Joint Ids tied to specific results. If automatic incrementation is used of the Joint Id within a batch the active Joint Id will be updated when next tightening in the batch is loaded. Please see Source Tightening Properties for further information about setup of Joint Id.

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | String | 8 | 800

## Devices

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

- User Display: FALSE

- Soft Selector: FALSE

- Indicator Box: FALSE

- Automation Rules: FALSE

- Fieldbus: TRUE

# Batch Completed - 30

Batch Completed is an output signal which is triggered when the batch is complete.
The batch result status (OK or NOK) has no effect on the Batch Completed signal.

Name in SoftPLC: BATCH_COMPLETED

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# Batch Completed NOK - 37

Batch finished with status NOK.

Name in SoftPLC: BATCH_COMPLETED_NOK

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# Batch Completed OK - 36

Batch finished with status OK.

Name in SoftPLC: BATCH_COMPLETED_OK

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# Batch Count - 31

Batch Count is an output signal which shows the current number of tightening in the batch.

Name in SoftPLC: BATCH_COUNT

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Integer | 1 | 8

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: TRUE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Batch Running - 32

Indicates that a batch in a batch sequence is running.

Name in SoftPLC: BATCH_RUNNING

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# Batch Sequence Completed NOK - 46

Batch sequence finished with status NOK.

Name in SoftPLC: BATCH_SEQUENCE_NOK

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# Batch Sequence Completed OK - 45

Batch sequence finished with status OK.

Name in SoftPLC: BATCH_SEQUENCE_OK

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# Batch Sequence Done - 48

Indicates when a sequence is completed, both in case Batch Sequence Completed OK and Batch Sequence Completed NOK.

Name in SoftPLC: BATCH_SEQUENCE_COMPLETED

Converter | Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | --- | ---
Standard | Event | Boolean | 1 | 1
Invert | Event | Boolean | 1 | 1

To avoid duplicating signals, it is possible to define Value Converters.

Converters are used to support more than one representation of the same signal (for example Angle/Torque Status can both be represented bitwise or as a status character).

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# Batch Sequence Running - 47

Indicates if the Batch Sequence is running or not.

Name in SoftPLC: BATCHSEQUENCE_RUNNING

Converter | Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | --- | ---
Standard | State | Boolean | 1 | 1
Invert | State | Boolean | 1 | 1

To avoid duplicating signals, it is possible to define Value Converters.

Converters are used to support more than one representation of the same signal (for example Angle/Torque Status can both be represented bitwise or as a status character).

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# Bistable Relay - 40

Bistable Relay is a signal controlled by the inputs "Set Bistable Relay" and "Reset Bistable Relay".
After receiving the input "Set Bistable Relay", Bistable Relay signal is set to True.
After receiving the input "Reset Bistable Relay", Bistable Relay signal is set to False.

If "Set Bistable Relay" or "Reset Bistable Relay" goes low, the Bistable relay keeps its state.
The state for the Bistable relay changes when "Set Bistable Relay" or "Reset Bistable Relay" goes high.

After restarting the controller, the Bistable relay is set to False as default.

Name in SoftPLC: BISTABLE_RELAY

Converter | Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | --- | ---
Standard | State | Boolean | 1 | 1
Invert | State | Boolean | 1 | 1

To avoid duplicating signals, it is possible to define Value Converters.

Converters are used to support more than one representation of the same signal (for example Angle/Torque Status can both be represented bitwise or as a status character).

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# Bolt Tightening Status - 79

Bolt Tightening Status is an output signal that identifies the status for individual bolts in a synchronized tightening. 100 bolts are supported.
Bolt Tightening Status signal shows information related to the running tightening and the result of the last tightening.

Name in SoftPLC: BOLT_TIGHTENING_STATUS

Converter | Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | --- | ---
Standard | State | uint32 array | 32 | 32
FordResultStatus | State |  | 4 | 4
CompactErrorStatus | State |  | 4 | 4

To avoid duplicating signals, it is possible to define Value Converters.

Converters are used to support more than one representation of the same signal (for example Angle/Torque Status can both be represented bitwise or as a status character).

The signal Bolt Tightening Status - 79 contains sub-signals (for more information, see "Output Signals: Sub-signals").

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Calibration Alarm - 138

The Calibration alarm from the Tool maintenance configuration. Provides a reminder for when it is time to calibrate the tool.

Name in SoftPLC: CALIBRATION_ALARM

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# Channel Hardware Status - 81

Channel Hardware Status is an output signal that identifies the hardware status for individual channels. 64 channels are supported.
Channel Hardware Status signal shows information about the hardware status and possible errors.

Name in SoftPLC: CHANNEL_HARDWARE_STATUS

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | uint32 array | 1 | 64

The signal Channel Hardware Status - 81 contains sub-signals (for more information, see "Output Signals: Sub-signals").

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Channel Tightening Status - 80

Channel Tightening Status is an output signal that identifies the status for individual channels in a synchronized tightening. 64 channels are supported.
Channel Tightening Status signal shows information related to the running tightening and the result of the last tightening.

Name in SoftPLC: CHANNEL_TIGHTENING_STATUS

Converter | Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | --- | ---
Standard | State | uint32 array | 1 | 64
FordResultStatus | State |  | 4 | 4
CompactErrorStatus | State |  | 4 | 4

To avoid duplicating signals, it is possible to define Value Converters.

Converters are used to support more than one representation of the same signal (for example Angle/Torque Status can both be represented bitwise or as a status character).

The signal Channel Tightening Status - 80 contains sub-signals (for more information, see "Output Signals: Sub-signals").

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Configuration Version - 88

Name in SoftPLC: CONFIGURATION_VERSION

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Integer | 1 | 32

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Confirm loosening - 206

Indicate if loosening is selected and possible to start. That is, a loosening sync mode or loosening program exists and are selected.

Name in SoftPLC: CONFIRM_LOOSENING

Converter | Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | --- | ---
Standard | State | Boolean | 1 | 1
Invert | State | Boolean | 1 | 1

To avoid duplicating signals, it is possible to define Value Converters.

Converters are used to support more than one representation of the same signal (for example Angle/Torque Status can both be represented bitwise or as a status character).

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# Controller Switched On - 42

Set to true at start up of IO Exchange

Name in SoftPLC: IO_ON

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# Current Running Batch - 180

Current Running Batch is an output signal which shows the index of the current running batch in a sequence.
If the user uses a socket selector, "Zero" appears if none, more than one, or wrong socket is selected.
If the user uses batch mode and a batch is running, "1" appears for Source Tightening configurations.

Name in SoftPLC: CURRENT_RUNNING_BATCH_IX

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Integer | 1 | 8

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: TRUE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Cycle Complete - 77

Name in SoftPLC: CYCLE_COMPLETE

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Cycle Emergency stopped - 202

Indicate last tightening or loosening was interrupted by emergency stop.

Name in SoftPLC: CYCLE_EMERGENCY_STOPPED

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Cycle NOK - 76

Name in SoftPLC: CYCLE_NOK

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Cycle OK - 75

Name in SoftPLC: CYCLE_OK

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Cycle Ready To Start - 82

Name in SoftPLC: CYCLE_READY_TO_START

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Cycle Running - 78

Name in SoftPLC: CYCLE_RUNNING

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Data Drop Active - 199

This signal will be set high whenever DATADROP function is active. When DATADROP input signal is set and worktask supporting DATADROP is selected.

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Data Hold Active - 198

This signal will be set high whenever the DATAHOLD function is active. When DATAHOLD signal is set and a worktask supporting DATAHOLD is selected.

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Direction Switch CCW - 13

The direction switch on the tool is turned in counter clockwise direction.

Name in SoftPLC: DIRECTION_SWITCH_CCW

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# Direction Switch CW - 12

The direction switch on the tool is turned in clockwise direction.

Name in SoftPLC: DIRECTION_SWITCH_CW

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# Emergency Stop - 20036

Name in SoftPLC: EMERGENCY_STOP

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# Event Code - 30001

Relay an event when it is triggered. Momentary, on for two cycle times.

Name in SoftPLC: EVENT_CODE

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Integer | 1 | 16

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Event Code Severity - 30003

Event Code Severity is an output signal which is activated when the triggered event has severity of error or warning.

Name in SoftPLC: EVENT_CODE_SEVERITY

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Event Present - 161

Indicates if event is triggered. It is only triggered on accessories if event requires an ACK.

Name in SoftPLC: EVENT_PRESENT

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# Fieldbus AsyncData From PF - 107

Name in SoftPLC:

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | uint8 array | 48 | 2048

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Fieldbus Disconnected - 96

Name in SoftPLC: FIELDBUS_DISCONNECTED

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: FALSE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# Final Angle - 8

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Float | 0 | 0

## Devices

- Fieldbus: FALSE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: TRUE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Final Angle - 31003

Actual measured Angle value at the end of the tightening cycle.

Name in SoftPLC: FINAL_ANGLE

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Integer | 16 | 16

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Final Angle Status - 31006

This signal shows the status of the final angle, which can be:

- OK - if the measured angle is within the limits configured in the tightening program.

- HIGH - if the measured angle is more than the high limit configured in the tightening program.

- LOW - if the measured angle is less than the low limit configured in the tightening program.

The value of the Final Angle Status signal shows differently, depending on the configuration of the fieldbus signal.
If the user selects the signal converter, the signal shows one of the following values:

- O - Final Angle Status OK.

- H - Final Angle Status High.

- L - Final Angle Status Low.

If there is no filter applied, the signal shows one of the following values:

- 1 - Final Angle Status OK.

- 2 - Final Angle Status High.

- 3 - Final Angle Status Low.

Name in SoftPLC: FINAL_ANGLE_STATUS

Converter | Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | --- | ---
Standard | State | Integer | 2 | 8
StatusAsChar | State | Integer | 2 | 8

To avoid duplicating signals, it is possible to define Value Converters.

Converters are used to support more than one representation of the same signal (for example Angle/Torque Status can both be represented bitwise or as a status character).

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Final Measured Current - 31017

Current at the measurement step of final angle and final torque. It is sent when a result is available.

Converter | Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | --- | ---
Standard | Event | Integer | 32 | 32
FixedPointToDecimal | Event | Integer | 32 | 32

To avoid duplicating signals, it is possible to define Value Converters.

Converters are used to support more than one representation of the same signal (for example Angle/Torque Status can both be represented bitwise or as a status character).

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Final Target Speed - 31020

The target speed of the last step of the tightening program.

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Integer | 16 | 16

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Final Target Torque - 31015

Gets the target torque of the tightening program for a performed tightening. The value is copied from the program of the tightening result and is published after the tightening.

The Multistep programs retrieve the Target Torque from the last tightening step in the tightening program defined as Step Category "Final".

Converter | Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | --- | ---
Standard | Event | Integer | 32 | 32
FixedPointToDecimal | Event | Integer | 32 | 32

To avoid duplicating signals, it is possible to define Value Converters.

Converters are used to support more than one representation of the same signal (for example Angle/Torque Status can both be represented bitwise or as a status character).

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Final Torque - 5

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Float | 1 | 1

## Devices

- Fieldbus: FALSE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: TRUE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Final Torque - 31002

Actual measured torque value at the end of the tightening cycle.

Name in SoftPLC: FINAL_TORQUE

Converter | Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | --- | ---
Standard | State | Integer | 32 | 32
FixedPointToDecimal | State | Integer | 32 | 32

To avoid duplicating signals, it is possible to define Value Converters.

Converters are used to support more than one representation of the same signal (for example Angle/Torque Status can both be represented bitwise or as a status character).

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Final Torque Status - 31009

This signal shows the status of the final torque, which can be:

- OK - if the measured torque is within the limits configured in the tightening program.

- HIGH - if the measured torque is more than the high limit configured in the tightening program.

- LOW - if the measured torque is less than the low limit configured in the tightening program.

The value of the Final Torque Status signal shows differently, depending on the configuration of the fieldbus signal.
If the user selects the signal converter, the signal shows one of the following values:

- O - Final Torque Status OK.

- H - Final Torque Status High.

- L - Final Torque Status Low.

If there is no filter applied, the signal shows one of the following values:

- 1 - Final Torque Status OK.

- 2 - Final Torque Status High.

- 3 - Final Torque Status Low.

Name in SoftPLC: FINAL_TORQUE_STATUS

Converter | Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | --- | ---
Standard | State | Integer | 2 | 8
StatusAsChar | State | Integer | 2 | 8

To avoid duplicating signals, it is possible to define Value Converters.

Converters are used to support more than one representation of the same signal (for example Angle/Torque Status can both be represented bitwise or as a status character).

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# First Target Torque - 31019

Retrieves the first target torque after a completed tightening.

Converter | Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | --- | ---
Standard | Event | Integer | 32 | 32
FixedPointToDecimal | Event | Integer | 32 | 32

To avoid duplicating signals, it is possible to define Value Converters.

Converters are used to support more than one representation of the same signal (for example Angle/Torque Status can both be represented bitwise or as a status character).

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# From SoftPLC - 10064

Allocated bytes for data transfer from PLC to accessories.

Name in SoftPLC: FROM_PLC

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | uint8 array | 8 | 8

## Devices

- Fieldbus: FALSE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# High Angle - 10

Angle result is too high.

Name in SoftPLC: HIGH_ANGLE

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# High Torque - 7

Torque result is higher than maximum torque limit.

Name in SoftPLC: HIGH_TORQUE

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# Identifier Received - 100

Name in SoftPLC: IDENTIFIER_RECEIVED

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# Joint Id Result - 31046

Sent together with the results on Fieldbus to indicate which configured Joint Id was used in the specific tightening result. Will not be set until a result where Joint Id is used are performed. It is cleared on next tightening or if any external system request to clear results. If “Read result handshake” is used the Joint Id Result part will clear in accordance to this functionality, as for any other result related results on the Fieldbus. For reading the currently selected Joint Id without a result please se “Activated Joint Id - 225”. For further assistance about setting up Joint Id, see Source Tightening Properties.

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | String | 8 | 800

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

- Manual Mode: FALSE

- Indicator Box: FALSE

- Tool Vibrator: FALSE

- Automation Rules: FALSE

# Last Cycle No Result - 200

This signal shall be set after a tightening is done if the tightening is considered as a free running.

Name in SoftPLC: LAST_CYCLE_NO_RESULT

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Last Received Identifier String - 187

Set directly when an identifier has been received in the work-task.
For Source batch-string, it is set at every scanning in scan process, thus it is changed for every scanning and sent even if it does not match in length.
String set is in raw format and not only "saved positions" in the string.
For other work-tasks this signal is equal to Active Identifier String signal.

Name in SoftPLC: LAST_RECEIVED_ID_STRING

Converter | Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | --- | ---
Standard | State | String | 8 | 800
IdentifierU32Hnw | State | String | 8 | 800
IdentifierU32 | State | String | 8 | 800

To avoid duplicating signals, it is possible to define Value Converters.

Converters are used to support more than one representation of the same signal (for example Angle/Torque Status can both be represented bitwise or as a status character).

Relevant Information

- Active Identifier String - 186

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# License Server Connection Lost - 134

Indicates that the connection to the Atlas Copco license server has been lost or the synchronization has failed. The signal is cleared when the License manager synchronization has been done successfully

Name in SoftPLC: LICENSE_SERVER_CONN_LOST

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# Loosening Disabled - 184

Loosening Disabled is an output signal which is activated when the loosening is externally locked by any of the following signals:

- 20003 - Lock Loosening

- 20004 - Lock Tool Active High

- 20033 - Line Control Lock

- 20018 - Open Protocol Lock

- 20021 - Fieldbus Lock Loosening

- 20041 - Soft PLC Lock Loosening

- 20061 - Lock Tool Active Low

Name in SoftPLC: LOOSENING_DISABLED

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# Loosening Enabled - 185

Loosening Disabled is an output signal which is activated when the loosening is not externally locked by any of the following signals:

- 20003 - Lock Loosening

- 20004 - Lock Tool Active High

- 20033 - Line Control Lock

- 20018 - Open Protocol Lock

- 20021 - Fieldbus Lock Loosening

- 20041 - Soft PLC Lock Loosening

- 20061 - Lock Tool Active Low

Name in SoftPLC: LOOSENING_ENABLED

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# Loosening is Locked - 28

The loosening is disabled.

Name in SoftPLC: LOOSENING_IS_LOCKED

Converter | Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | --- | ---
Standard | State | Boolean | 1 | 1
Invert | State | Boolean | 1 | 1

To avoid duplicating signals, it is possible to define Value Converters.

Converters are used to support more than one representation of the same signal (for example Angle/Torque Status can both be represented bitwise or as a status character).

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# Loosening NOK - 74

NOK loosening took place.

Name in SoftPLC: LOOSENING_NOK

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# Loosening OK - 70

OK loosening took place.

Name in SoftPLC: LOOSENING_OK

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# Low Angle - 9

Angle result is lower than minimum angle limit.

Name in SoftPLC: LOW_ANGLE

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# Low Torque - 6

Torque result is lower than minimum torque limit.

Name in SoftPLC: LOW_TORQUE

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# Manual Mode - 101

Indicates on any supported and configured accessory the Virtual Station status for manual mode

Name in SoftPLC: MANUAL_MODE

Converter | Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | --- | ---
Standard | State | Boolean | 1 | 1
Invert | State | Boolean | 1 | 1

To avoid duplicating signals, it is possible to define Value Converters.

Converters are used to support more than one representation of the same signal (for example Angle/Torque Status can both be represented bitwise or as a status character).

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# Max Consecutive NOK Reached - 35

Indicates Max coherent NOK tightening counter is reachead.

Name in SoftPLC: MAX_COHERENT_NOK_REACHED

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# No System Error - 83

Name in SoftPLC: NO_SYSTEM_ERROR

Converter | Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | --- | ---
Standard | State | Boolean | 1 | 1
Invert | State | Boolean | 1 | 1

To avoid duplicating signals, it is possible to define Value Converters.

Converters are used to support more than one representation of the same signal (for example Angle/Torque Status can both be represented bitwise or as a status character).

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# No System Warning - 102

Name in SoftPLC: NO_SYSTEM_WARNING

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# Open End in Open Position - 89

Open End tool in open position.

Name in SoftPLC: OPEN_END_IN_OPEN_POSITION

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# Open Protocol Disconnected - 95

If Open Protocol is set to off in the Virtual Station, "Open Protocol Disconnected" signal is set to False.
If Open Protocol is turned on in the Virtual Station the "Open Protocol Disconnected" signal is set to True.
When at least one client (several Open Protocol clients can connect to the same Virtual Station) is connected the "Open Protocol Disconnected" signal is set to False.

Name in SoftPLC: OPEN_PROTOCOL_DISCONNECTED

Converter | Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | --- | ---
Standard | State | Boolean | 1 | 1
Invert | State | Boolean | 1 | 1

To avoid duplicating signals, it is possible to define Value Converters.

Converters are used to support more than one representation of the same signal (for example Angle/Torque Status can both be represented bitwise or as a status character).

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# Pass-Through Identifier - 104

Output signal for sending a scanned string from a scanner to an external device.

Name in SoftPLC: BARCODE_ID_PASSTHROUGH

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | String | 8 | 800

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Program End - 168

This signal indicates the torque level when the tightening cycle is complete. A timer - Program end timeout - starts when the torque falls below this level. Tightening is complete when the torque has fallen below the level for Program end torque and stayed there until Program end timeout has been reached.

Name in SoftPLC: PROGRAM_END

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Program Start - 132

Defines the starting level for a tightening cycle.

Name in SoftPLC: PROGRAM_START

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Pulse Tool Alarm Oil Level Empty - 167

Oil level supervision configured in the Tool maintenance, provides a mechanism to remind the users when it is time to fill up oil on a pulse tool. The signal does not notify the user when the trigger gets pressed.
The signal is cleared when tool is disconnected; then, it is sent again from the tool if the condition prevails next time the tool is connected.

Name in SoftPLC: TOOL_OIL_LEVEL_EMPTY

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# PVT Compensate Value - 31029

Converter | Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | --- | ---
Standard | Event | Integer | 32 | 32
FixedPointToDecimal | Event | Integer | 32 | 32

To avoid duplicating signals, it is possible to define Value Converters.

Converters are used to support more than one representation of the same signal (for example Angle/Torque Status can both be represented bitwise or as a status character).

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Read Result Queue Flushed - 30006

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Ready to Start - 29

If a tool is connected to the virtual station, there is not any active tightening locks, emergency stop is not activated, and a valid Tightening Program is selected, this signal indicates that it is possible to start a tightening.

Name in SoftPLC: READY_TO_START

Converter | Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | --- | ---
Standard | State | Boolean | 1 | 1
Invert | State | Boolean | 1 | 1

To avoid duplicating signals, it is possible to define Value Converters.

Converters are used to support more than one representation of the same signal (for example Angle/Torque Status can both be represented bitwise or as a status character).

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# Received Identifier 1 - 192

Signal corresponding to the first configured string in Source batch-string.
Active Identifier String 1 signal is sent in the order the strings/identifiers are received by the system as soon as a string has been received. If running in forced order scan, it is in the configured order, but if running free order scan, 1 might not correspond to the first configured string, but to the first received string.
The strings is the raw received string and not have the "saved position" applied.
Only sent when running Source batch string.

Name in SoftPLC: RECEIVED_IDENTIFIER_1

Converter | Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | --- | ---
Standard | State | String | 8 | 800
IdentifierU32Hnw | State | String | 8 | 800
IdentifierU32 | State | String | 8 | 800

To avoid duplicating signals, it is possible to define Value Converters.

Converters are used to support more than one representation of the same signal (for example Angle/Torque Status can both be represented bitwise or as a status character).

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Received Identifier 2 - 193

Signal corresponding to the second configured string in Source batch-string.
Active Identifier String 2 signal is sent in the order the strings/identifiers are received by the system as soon as a string has been received. If running in forced order scan, it is in the configured order, but if running free order scan, 2 might not correspond to the second configured string, but to the second received string.
The strings is the raw received string and not have the "saved position" applied.
Only sent when running Source batch string.

Name in SoftPLC: RECEIVED_IDENTIFIER_2

Converter | Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | --- | ---
Standard | State | String | 8 | 800
IdentifierU32Hnw | State | String | 8 | 800
IdentifierU32 | State | String | 8 | 800

To avoid duplicating signals, it is possible to define Value Converters.

Converters are used to support more than one representation of the same signal (for example Angle/Torque Status can both be represented bitwise or as a status character).

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Received Identifier 3 - 194

Signal corresponding to the third configured string in Source batch-string.
Active Identifier String 3 signal is sent in the order the strings/identifiers are received by the system as soon as a string has been received. If running in forced order scan, it is in the configured order, but if running free order scan, 3 might not correspond to the third configured string, but to the third received string.
The strings is the raw received string and not have the "saved position" applied.
Only sent when running Source batch string.

Name in SoftPLC: RECEIVED_IDENTIFIER_3

Converter | Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | --- | ---
Standard | State | String | 8 | 800
IdentifierU32Hnw | State | String | 8 | 800
IdentifierU32 | State | String | 8 | 800

To avoid duplicating signals, it is possible to define Value Converters.

Converters are used to support more than one representation of the same signal (for example Angle/Torque Status can both be represented bitwise or as a status character).

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Received Identifier 4 - 195

Signal corresponding to the fourth configured string in Source batch-string.
Active Identifier String 4 signal is sent in the order the strings/identifiers are received by the system as soon as a string has been received. If running in forced order scan, it is in the configured order, but if running free order scan, 4 might not correspond to the fourth configured string, but to the fourth received string.
The strings is the raw received string and not have the "saved position" applied.
Only sent when running Source batch string.

Name in SoftPLC: RECEIVED_IDENTIFIER_4

Converter | Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | --- | ---
Standard | State | String | 8 | 800
IdentifierU32Hnw | State | String | 8 | 800
IdentifierU32 | State | String | 8 | 800

To avoid duplicating signals, it is possible to define Value Converters.

Converters are used to support more than one representation of the same signal (for example Angle/Torque Status can both be represented bitwise or as a status character).

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Rehit - 31014

Name in SoftPLC: FIELDBUS_TIGHTENING_REHIT

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Remaining Batch - 33

Remaining tightenings in a batch. Can only be viewed on a display.

Name in SoftPLC: REMAINING_BATCH

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Integer | 1 | 8

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: TRUE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Rundown Angle - 31038

Value of the rundown angle.

Name in SoftPLC: RUNDOWN_ANGLE

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Integer | 16 | 16

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Rundown Angle High - 165

This signal is active if the rundown angle on the program level is higher than the set one.

Name in SoftPLC: RUNDOWN_ANGLE_HIGH

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# Rundown Angle Low - 166

This signal is active if the rundown angle on the program level is lower than the set one.

Name in SoftPLC: RUNDOWN_ANGLE_LOW

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# Selected Identifier Number - 213

The identifier number of a selected tightening program; 0 if no identifier number selected.

Name in SoftPLC: SELECTED_IDENTIFIER_NUMBER

Converter | Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | --- | ---
Standard | State | Integer | 1 | 16
TreatZeroAsOne | State | Integer | 1 | 16

To avoid duplicating signals, it is possible to define Value Converters. Converters are used to support more than one representation of the same signal (for example Angle/Torque Status can both be represented bitwise or as a status character).

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: TRUE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Selected Mode Id - 72

Name in SoftPLC: SELECTED_MODE_ID

Converter | Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | --- | ---
Standard | State | Integer | 1 | 32
TreatZeroAsOne | State | Integer | 1 | 32

To avoid duplicating signals, it is possible to define Value Converters.

Converters are used to support more than one representation of the same signal (for example Angle/Torque Status can both be represented bitwise or as a status character).

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Selected Sequence Bit 0 - 139

Bit pattern showing selected sequence.

Name in SoftPLC: SELECTED_SEQUENCE_BIT_0

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: FALSE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Selected Sequence Bit 1 - 140

Bit pattern showing selected sequence.

Name in SoftPLC: SELECTED_SEQUENCE_BIT_1

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: FALSE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Selected Sequence Bit 2 - 141

Bit pattern showing selected sequence.

Name in SoftPLC: SELECTED_SEQUENCE_BIT_2

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: FALSE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Selected Sequence Bit 3 - 142

Bit pattern showing selected sequence.

Name in SoftPLC: SELECTED_SEQUENCE_BIT_3

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: FALSE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Selected Sequence Bit 4 - 143

Bit pattern showing selected sequence.

Name in SoftPLC: SELECTED_SEQUENCE_BIT_4

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: FALSE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Selected Sequence Bit 5 - 144

Bit pattern showing selected sequence.

Name in SoftPLC: SELECTED_SEQUENCE_BIT_5

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: FALSE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Selected Sequence Bit 6 - 145

Bit pattern showing selected sequence.

Name in SoftPLC: SELECTED_SEQUENCE_BIT_6

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: FALSE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Selected Sequence Bit 7 - 146

Bit pattern showing selected sequence.

Name in SoftPLC: SELECTED_SEQUENCE_BIT_7

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: FALSE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Selected Sequence Bit 8 - 147

Bit pattern showing selected sequence.

Name in SoftPLC: SELECTED_SEQUENCE_BIT_8

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: FALSE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Selected Sequence Bit 9 - 163

Bit pattern showing selected sequence.

Name in SoftPLC: SELECTED_SEQUENCE_BIT_9

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: FALSE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Selected Sequence Id - 84

Shows the index of the selected batch sequence.

Name in SoftPLC: SELECTED_BATCH_SEQUENCE_ID

Converter | Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | --- | ---
Standard | State | Integer | 1 | 16
TreatZeroAsOne | State | Integer | 1 | 16

To avoid duplicating signals, it is possible to define Value Converters.

Converters are used to support more than one representation of the same signal (for example Angle/Torque Status can both be represented bitwise or as a status character).

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: TRUE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Selected Tightening Program - 69

The actual id of a selected tightening program; 0 if no tightening program selected.

Name in SoftPLC: SELECTED_PSET_ID

Converter | Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | --- | ---
Standard | State | Integer | 1 | 16
TreatZeroAsOne | State | Integer | 1 | 16

To avoid duplicating signals, it is possible to define Value Converters.

Converters are used to support more than one representation of the same signal (for example Angle/Torque Status can both be represented bitwise or as a status character).

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: TRUE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Selected Tightening Program Bit 0 - 148

Bit pattern showing selected tightening program.

Name in SoftPLC: SELECTED_PROGRAM_BIT_0

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: FALSE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Selected Tightening Program Bit 1 - 149

Bit pattern showing selected tightening program.

Name in SoftPLC: SELECTED_PROGRAM_BIT_1

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: FALSE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Selected Tightening Program Bit 2 - 150

Bit pattern showing selected tightening program.

Name in SoftPLC: SELECTED_PROGRAM_BIT_2

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: FALSE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Selected Tightening Program Bit 3 - 151

Bit pattern showing selected tightening program.

Name in SoftPLC: SELECTED_PROGRAM_BIT_3

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: FALSE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Selected Tightening Program Bit 4 - 152

Bit pattern showing selected tightening program.

Name in SoftPLC: SELECTED_PROGRAM_BIT_4

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: FALSE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Selected Tightening Program Bit 5 - 153

Bit pattern showing selected tightening program.

Name in SoftPLC: SELECTED_PROGRAM_BIT_5

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: FALSE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Selected Tightening Program Bit 6 - 154

Bit pattern showing selected tightening program.

Name in SoftPLC: SELECTED_PROGRAM_BIT_6

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: FALSE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Selected Tightening Program Bit 7 - 155

Bit pattern showing selected tightening program.

Name in SoftPLC: SELECTED_PROGRAM_BIT_7

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: FALSE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Selected Tightening Program Bit 8 - 156

Bit pattern showing selected tightening program.

Name in SoftPLC: SELECTED_PROGRAM_BIT_8

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: FALSE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Selected Tightening Program Bit 9 - 157

Bit pattern showing selected tightening program.

Name in SoftPLC: SELECTED_PROGRAM_BIT_9

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: FALSE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Sequence Aborted - 160

Output signal indicating if sequence was aborted.

Name in SoftPLC: SEQUENCE_ABORTED

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# Service Indicator Alarm - 137

Service alarm configured in the Tool maintenance, provides a mechanism to remind the users when it is time to service the tool.

Name in SoftPLC: SERVICE_INDICATOR_ALARM

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# Size of Sequence - 181

Shows the size of the currently running sequence. Only set when a sequence is loaded and not reset when sequence is done.

Name in SoftPLC: SIZE_OF_RUNNING_SEQUENCE

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Integer | 1 | 8

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: TRUE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Socket Selector Disconnected Lock - 20039

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# Software Major Version - 86

Name in SoftPLC: SOFTWARE_MAJOR_VERSION

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Integer | 1 | 32

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Software Minor Version - 87

Name in SoftPLC: SOFTWARE_MINOR_VERSION

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Integer | 1 | 32

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Software Release Version - 85

Version of the software running.

Name in SoftPLC: SOFTWARE_RELEASE_VERSION

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Integer | 1 | 32

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Start Final Angle - 31016

The Start Final Angle torque value is shown if available. It is sent when a result is available.

Converter | Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | --- | ---
Standard | State | Integer | 32 | 32
FixedPointToDecimal | State | Integer | 32 | 32

To avoid duplicating signals, it is possible to define Value Converters.

Converters are used to support more than one representation of the same signal (for example Angle/Torque Status can both be represented bitwise or as a status character).

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Station Ready - 71

Indicates when the Virtual Station is ready.

Name in SoftPLC: STATION_READY

Converter | Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | --- | ---
Standard | State | Boolean | 1 | 1
Invert | State | Boolean | 1 | 1

To avoid duplicating signals, it is possible to define Value Converters.

Converters are used to support more than one representation of the same signal (for example Angle/Torque Status can both be represented bitwise or as a status character).

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# Sync Mode Valid - 207

Indicate if selected sync mode is valid or not. That is, if it exists and is configured properly.

Name in SoftPLC: SYNC_MODE_VALID

Converter | Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | --- | ---
Standard | State | Boolean | 1 | 1
Invert | State | Boolean | 1 | 1

To avoid duplicating signals, it is possible to define Value Converters.

Converters are used to support more than one representation of the same signal (for example Angle/Torque Status can both be represented bitwise or as a status character).

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Test Bolt Activated - 91

Name in SoftPLC: SELECTED_MODE_ID

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Thread Direction CCW - 26

Selected tightening program has counterclockwise chosen as thread direction.

Name in SoftPLC: THREAD_DIRECTION_CCW

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# Tightening Date - 31030

Tightening date in the format YYYY:MM:DD.

Name in SoftPLC: TIGHTENING_DATE

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | String | 80 | 80

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Tightening Date Day - 31032

Day of month when the tightening was performed.

Name in SoftPLC: TIGHTENING_DATE_DAY

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Integer | 8 | 16

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Tightening Date Month - 31033

Month when the tightening was performed.

Name in SoftPLC: TIGHTENING_DATE_MONTH

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Integer | 8 | 16

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Tightening Date Year - 31034

Year when the tightening was performed.

Name in SoftPLC: TIGHTENING_DATE_YEAR

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Integer | 16 | 16

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Tightening Disabled - 182

Tightening Disabled is an output signal which is activated when the tightening is externally disabled by any of the following signals:

- 20002 - Lock Tightening

- 20004 - Lock Tool Active High

- 20033 - Line Control Lock

- 20018 - Open Protocol Lock

- 20020 - Fieldbus Lock Tightening

- 20040 - Soft PLC Lock Tightening

- 20061 - Lock Tool Active Low

Name in SoftPLC: TIGHTENING_DISABLED

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# Tightening Done - 31010

Name in SoftPLC: TIGHTENING_DONE

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Tightening Enabled - 183

Tightening Enabled is an output signal which is activated when the tightening is not externally disabled by any of the following signals:

- 20002 - Lock Tightening

- 20004 - Lock Tool Active High

- 20033 - Line Control Lock

- 20018 - Open Protocol Lock

- 20020 - Fieldbus Lock Tightening

- 20040 - Soft PLC Lock Tightening

- 20061 - Lock Tool Active Low

Name in SoftPLC: TIGHTENING_ENABLED

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# Tightening is Locked - 27

The tightening is disabled; it is not possible to make any tightening.

Name in SoftPLC: TIGHTENING_IS_LOCKED

Converter | Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | --- | ---
Standard | State | Boolean | 1 | 1
Invert | State | Boolean | 1 | 1

To avoid duplicating signals, it is possible to define Value Converters.

Converters are used to support more than one representation of the same signal (for example Angle/Torque Status can both be represented bitwise or as a status character).

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# Tightening NOK - 4

At least one result of the tightening is outside the specified limits.

Name in SoftPLC: TIGHTENING_NOK

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# Tightening OK - 3

The result of the tightening is within the specified limits.

Name in SoftPLC: TIGHTENING_OK

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# Tightening Program Max Angle - 31004

Name in SoftPLC: MAX_ANGLE

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Integer | 16 | 16

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Tightening Program Max Torque - 31007

Name in SoftPLC: MAX_TORQUE

Converter | Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | --- | ---
Standard | State | Integer | 32 | 32
FixedPointToDecimal | State | Integer | 32 | 32

To avoid duplicating signals, it is possible to define Value Converters.

Converters are used to support more than one representation of the same signal (for example Angle/Torque Status can both be represented bitwise or as a status character).

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Tightening Program Min Angle - 31005

Name in SoftPLC: MIN_ANGLE

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Integer | 16 | 16

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Tightening Program Min Torque - 31008

Name in SoftPLC: MIN_TORQUE

Converter | Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | --- | ---
Standard | State | Integer | 32 | 32
FixedPointToDecimal | State | Integer | 32 | 32

To avoid duplicating signals, it is possible to define Value Converters.

Converters are used to support more than one representation of the same signal (for example Angle/Torque Status can both be represented bitwise or as a status character).

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Tightening Time - 31031

Tightening time in the format hh:mm:ss.

Name in SoftPLC: TIGHTENING_TIME

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | String | 64 | 64

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Tightening Time High - 135

Indicates if NOK tightenings occurred due to execution time exceeding the maximum allowed.

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Tightening Time Hour - 31035

Hour when the tightening was performed.

Name in SoftPLC: TIGHTENING_TIME_HOUR

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Integer | 8 | 16

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Tightening Time Low - 136

Indicates if NOK tightenings occurred due to execution time lowering the minimum allowed.

Tightening Time Low signal works only for Tightening Programs.

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Tightening Time Minute - 31037

Minute when the tightening was performed.

Name in SoftPLC: TIGHTENING_TIME_MINUTES

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Integer | 8 | 16

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Tightening Time Second - 31036

Second when the tightening was performed.

Name in SoftPLC: TIGHTENING_TIME_SEC

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Integer | 8 | 16

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Tool Battery Low - 90

Name in SoftPLC: TOOL_BATTERY_LOW

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# Tool Connected - 73

Indicates if a tool is connected or not to a Virtual Station.

Name in SoftPLC: TOOL_CONNECTED

Converter | Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | --- | ---
Standard | State | Boolean | 1 | 1
Invert | State | Boolean | 1 | 1

To avoid duplicating signals, it is possible to define Value Converters.

Converters are used to support more than one representation of the same signal (for example Angle/Torque Status can both be represented bitwise or as a status character).

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# Tool Disabled - 158

Tool Disabled is an output signal which is activated when the tool is externally disabled by any of the following signals:

- 20002 - Lock Tightening

- 20003 - Lock Loosening

- 20004 - Lock Tool Active High

- 20033 - Line Control Lock

- 20018 - Open Protocol Lock

- 20020 - Fieldbus Lock Tightening

- 20021 - Fieldbus Lock Loosening

- 20040 - Soft PLC Lock Tightening

- 20041 - Soft PLC Lock Loosening

- 20061 - Lock Tool Active Low

Name in SoftPLC: TOOL_DISABLED

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# Tool Enabled - 159

Tool Enabled is an output signal which is activated when the tool is not externally disabled by any of the following signals:

- 20002 - Lock Tightening

- 20003 - Lock Loosening

- 20004 - Lock Tool Active High

- 20033 - Line Control Lock

- 20018 - Open Protocol Lock

- 20020 - Fieldbus Lock Tightening

- 20021 - Fieldbus Lock Loosening

- 20040 - Soft PLC Lock Tightening

- 20041 - Soft PLC Lock Loosening

- 20061 - Lock Tool Active Low

Name in SoftPLC: TOOL_ENABLED

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# Tool Function Button Pressed - 179

Output signal tracking the Function button state. The signal is set when the Function button is pressed and cleared when the Function button is released. Not for critical use in case of battery tools.

Name in SoftPLC: FUNCTION_BUTTON_PRESSED

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Tool Health OK - 103

Tool Health OK is High when there is no tool error present, while Tool Health OK is Low when any of the following tool errors are set:

- Tool Overheated

- Tool Requires motor tuning

- Open End not tuned

- Tool parameter file not supported

- Tool battery empty

- Tool trigger supervision failure

- Tool cable not supported

- Tool memory failure

- Tool memory corrupt

- Tool service interval expired

- Tool software version mismatch

Converter | Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | --- | ---
Standard | State | Boolean | 1 | 1
Invert | State | Boolean | 1 | 1

To avoid duplicating signals, it is possible to define Value Converters.

Converters are used to support more than one representation of the same signal (for example Angle/Torque Status can both be represented bitwise or as a status character).

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# Tool Loosening - 22

Indicates that the tool is loosening.

Name in SoftPLC: TOOL_LOOSENING

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# Tool Rotation CCW - 25

Tool rotation direction is counterclockwise for left-handed threaded screws.

Name in SoftPLC: TOOL_ROTATION_CCW

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# Tool Rotation CW - 24

Tool rotation direction is clockwise for right-handed threaded screws.

Name in SoftPLC: TOOL_ROTATION_CW

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# Tool Running - 23

Indicates that the tool is rotating (clockwise [CW] or counter-clockwise [CCW]).

Name in SoftPLC: TOOL_RUNNING

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# Tool Serial Number Numeric - 31021

Integer part of the serial number.

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Integer | 32 | 32

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Tool Tag Identifier - 94

Name in SoftPLC: TOOLTAG_IDENTIFIER

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | String | 8 | 800

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Tool Tightening - 21

Indicates that the tool is tightening.

Name in SoftPLC: TOOL_TIGHTENING

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# Tools in Zero Position - 210

The output signal Tools in Zero Position is available only for hand-held tool.

The output signal Tools in Zero Position defines if the tool is in home position - for example, at the end of a forward or backward position step.
The signal is not updated in real time, so if the tool for any reason is moved out of position, the signal will not work.

Name in SoftPLC: TOOLS_IN_ZERO_POSITION

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# ToolsNet Connection Lost - 133

Indicates if enabled connection between ToolsNet and controller got interrupted or is working as expected.

Name in SoftPLC: TOOLSNET_CONNECTION_LOST

Converter | Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | --- | ---
Standard | State | Boolean | 1 | 1
Invert | State | Boolean | 1 | 1

To avoid duplicating signals, it is possible to define Value Converters.

Converters are used to support more than one representation of the same signal (for example Angle/Torque Status can both be represented bitwise or as a status character).

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# Total Number of Tightenings - 31018

Total number of the tightenings performed by the tool over its entire lifetime.

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Integer | 8 | 32

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Total Remaining Sequence Counter - 205

The amount of remaining tightenings to be completed in a batch sequence.

Name in SoftPLC: TOTAL_REMAINING_SEQ_COUNT

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Integer | 1 | 16

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: TRUE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Total Sequence Counter - 204

The amount of completed tightenings in a batch sequence.

Name in SoftPLC: TOTAL_SEQ_COUNTER

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Integer | 1 | 16

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: TRUE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Total Sequence Size - 203

The total amount of tightenings to be completed in a batch sequence.

Name in SoftPLC: TOTAL_SEQ_SIZE

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Integer | 1 | 16

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- I/O Expander: FALSE

- Operator Panel: FALSE

- ST Selector: TRUE

- Stacklight: FALSE

- Tool Functions: FALSE

- TLS Tag: FALSE

# Trigger pressed - 11

Indicates that the tool trigger has been pressed.

Name in SoftPLC: TRIGGER_PRESSED

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# Waiting To Continue - 201

Waiting To Continue is an output signal, which means that the tightening has reached a Wait tightening step with the condition Signal configured as Wait Type.
The system (one or more spindles) pauses the tightening waiting for the signal Continue Step - 10128 (for system release) or the sub-signal Channel Command - 10054: Continue Step (for individual spindle release).

For more information, see the sub-signals Bolt Tightening Status - 79: Waiting To Continue and Channel Tightening Status - 80: Waiting To Continue.

Name in SoftPLC: WAITING_FOR_CONTINUE

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Virtual Station Name - 105

Provides the virtual station name.

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | String | 8 | 800

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Input/Output Signals

Converter
Signal Type
Value Type
Size Min [bit]
Size Max [bit]
Devices
Search

# Clear Results - 39

Clears status of other signals set to next tightening.

Name in SoftPLC: CLEAR_RESULTS

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Disable Open Protocol Commands - 10060

Disables the possibility to send commands over Open Protocol to the Virtual Station.

Name in SoftPLC: DISABLE_OPEN_PRTCOL_CMDS

Converter | Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | --- | ---
Standard | State | Boolean | 1 | 1
Invert | State | Boolean | 1 | 1

To avoid duplicating signals, it is possible to define Value Converters.

Converters are used to support more than one representation of the same signal (for example Angle/Torque Status can both be represented bitwise or as a status character).

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# External Identifier - 10045

The string sent in External identifier is included in the result as VIN number. It is possible to provide up to 2 identifiers to be passed from Fieldbus for task selection.

Name in SoftPLC: EXTERNAL_IDENTIFIER

Converter | Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | --- | ---
Standard | State | String | 8 | 800
IdentifierU32Hnw | State | String | 8 | 800
IdentifierU32 | State | String | 8 | 800

To avoid duplicating signals, it is possible to define Value Converters.

Converters are used to support more than one representation of the same signal (for example Angle/Torque Status can both be represented bitwise or as a status character).

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# External Monitored 1 - 10035

External Monitored 1 is an Input/Output signal that is not attached to any specific feature in the controller and can be used for customer specific needs.

Name in SoftPLC: EXTERNAL_MONITORED_1

Converter | Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | --- | ---
Standard | State | Boolean | 1 | 1
Invert | State | Boolean | 1 | 1

To avoid duplicating signals, it is possible to define Value Converters.

Converters are used to support more than one representation of the same signal (for example Angle/Torque Status can both be represented bitwise or as a status character).

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# External Monitored 2 - 10036

External Monitored 2 is an Input/Output signal that is not attached to any specific feature in the controller and can be used for customer specific needs.

Name in SoftPLC: EXTERNAL_MONITORED_2

Converter | Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | --- | ---
Standard | State | Boolean | 1 | 1
Invert | State | Boolean | 1 | 1

To avoid duplicating signals, it is possible to define Value Converters.

Converters are used to support more than one representation of the same signal (for example Angle/Torque Status can both be represented bitwise or as a status character).

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# External Monitored 3 - 10037

External Monitored 3 is an Input/Output signal that is not attached to any specific feature in the controller and can be used for customer specific needs.

Name in SoftPLC: EXTERNAL_MONITORED_3

Converter | Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | --- | ---
Standard | State | Boolean | 1 | 1
Invert | State | Boolean | 1 | 1

To avoid duplicating signals, it is possible to define Value Converters.

Converters are used to support more than one representation of the same signal (for example Angle/Torque Status can both be represented bitwise or as a status character).

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# External Monitored 4 - 10038

External Monitored 4 is an Input/Output signal that is not attached to any specific feature in the controller and can be used for customer specific needs.

Name in SoftPLC: EXTERNAL_MONITORED_4

Converter | Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | --- | ---
Standard | State | Boolean | 1 | 1
Invert | State | Boolean | 1 | 1

To avoid duplicating signals, it is possible to define Value Converters.

Converters are used to support more than one representation of the same signal (for example Angle/Torque Status can both be represented bitwise or as a status character).

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# External Monitored 5 - 10039

External Monitored 5 is an Input/Output signal that is not attached to any specific feature in the controller and can be used for customer specific needs.

Name in SoftPLC: EXTERNAL_MONITORED_5

Converter | Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | --- | ---
Standard | State | Boolean | 1 | 1
Invert | State | Boolean | 1 | 1

To avoid duplicating signals, it is possible to define Value Converters.

Converters are used to support more than one representation of the same signal (for example Angle/Torque Status can both be represented bitwise or as a status character).

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# External Monitored 6 - 10040

External Monitored 6 is an Input/Output signal that is not attached to any specific feature in the controller and can be used for customer specific needs.

Name in SoftPLC: EXTERNAL_MONITORED_6

Converter | Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | --- | ---
Standard | State | Boolean | 1 | 1
Invert | State | Boolean | 1 | 1

To avoid duplicating signals, it is possible to define Value Converters.

Converters are used to support more than one representation of the same signal (for example Angle/Torque Status can both be represented bitwise or as a status character).

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# External Monitored 7 - 10041

External Monitored 7 is an Input/Output signal that is not attached to any specific feature in the controller and can be used for customer specific needs.

Name in SoftPLC: EXTERNAL_MONITORED_7

Converter | Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | --- | ---
Standard | State | Boolean | 1 | 1
Invert | State | Boolean | 1 | 1

To avoid duplicating signals, it is possible to define Value Converters.

Converters are used to support more than one representation of the same signal (for example Angle/Torque Status can both be represented bitwise or as a status character).

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# External Monitored 8 - 10042

External Monitored 8 is an Input/Output signal that is not attached to any specific feature in the controller and can be used for customer specific needs.

Name in SoftPLC: EXTERNAL_MONITORED_8

Converter | Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | --- | ---
Standard | State | Boolean | 1 | 1
Invert | State | Boolean | 1 | 1

To avoid duplicating signals, it is possible to define Value Converters.

Converters are used to support more than one representation of the same signal (for example Angle/Torque Status can both be represented bitwise or as a status character).

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# Fieldbus Keep Alive - 30002

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Integer | 1 | 8

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Flash Tool Green LED (external protocol) - 10058

Name in SoftPLC: FLASH_TOOL_GREEN_LED

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Generic I/O 1 - 50

Input/Output 1 used for Open Protocol.

Name in SoftPLC: GENERIC_IO_1

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Integer | 1 | 8

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: TRUE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# Generic I/O 10 - 59

Input/Output 10 used for Open Protocol.

Name in SoftPLC: GENERIC_IO_10

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Integer | 1 | 8

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: TRUE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# Generic I/O 2 - 51

Input/Output 2 used for Open Protocol.

Name in SoftPLC: GENERIC_IO_2

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Integer | 1 | 8

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: TRUE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# Generic I/O 3 - 52

Input/Output 3 used for Open Protocol.

Name in SoftPLC: GENERIC_IO_3

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Integer | 1 | 8

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: TRUE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# Generic I/O 4 - 53

Input/Output 4 used for Open Protocol.

Name in SoftPLC: GENERIC_IO_4

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Integer | 1 | 8

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: TRUE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# Generic I/O 5 - 54

Input/Output 5 used for Open Protocol.

Name in SoftPLC: GENERIC_IO_5

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Integer | 1 | 8

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: TRUE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# Generic I/O 6 - 55

Input/Output 6 used for Open Protocol.

Name in SoftPLC: GENERIC_IO_6

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Integer | 1 | 8

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: TRUE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# Generic I/O 7 - 56

Input/Output 7 used for Open Protocol.

Name in SoftPLC: GENERIC_IO_7

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Integer | 1 | 8

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: TRUE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# Generic I/O 8 - 57

Input/Output 8 used for Open Protocol.

Name in SoftPLC: GENERIC_IO_8

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Integer | 1 | 8

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: TRUE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# Generic I/O 9 - 58

Input/Output 9 used for Open Protocol.

Name in SoftPLC: GENERIC_IO_9

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Integer | 1 | 8

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: TRUE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# Generic Rising Edge 1 - 169

Generic Input/Output signal.

Name in SoftPLC: GENERIC_RISING_EDGE_1

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Generic Rising Edge 10 - 178

Generic Input/Output signal.

Name in SoftPLC: GENERIC_RISING_EDGE_10

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Generic Rising Edge 2 - 170

Generic Input/Output signal.

Name in SoftPLC: GENERIC_RISING_EDGE_2

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Generic Rising Edge 3 - 171

Generic Input/Output signal.

Name in SoftPLC: GENERIC_RISING_EDGE_3

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Generic Rising Edge 4 - 172

Generic Input/Output signal.

Name in SoftPLC: GENERIC_RISING_EDGE_4

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Generic Rising Edge 5 - 173

Generic Input/Output signal.

Name in SoftPLC: GENERIC_RISING_EDGE_5

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Generic Rising Edge 6 - 174

Generic Input/Output signal.

Name in SoftPLC: GENERIC_RISING_EDGE_6

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Generic Rising Edge 7 - 175

Generic Input/Output signal.

Name in SoftPLC: GENERIC_RISING_EDGE_7

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Generic Rising Edge 8 - 176

Generic Input/Output signal.

Name in SoftPLC: GENERIC_RISING_EDGE_8

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Generic Rising Edge 9 - 177

Generic Input/Output signal.

Name in SoftPLC: GENERIC_RISING_EDGE_9

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
Event | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: FALSE

- I/O Expander: TRUE

# Socket Lifted - 10014

Is generated when a unique socket is lifted on socket selector (integer = socket ID), no socket is lifted (integer = 0) or when more than one is lifted (integer = 0).

Name in SoftPLC: SOCKET_LIFTED

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Integer | 1 | 32

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Socket Lifted Raw - 10043

Added to support backwards compatibility with PF4000 in certain protocols for socket lifted notifications (as opposed to Socket Lifted 10013). Integer is bit pattern for all lifted sockets (regardless of flashing or how many is lifted).

Name in SoftPLC: SOCKET_LIFTED_RAW

Converter | Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | --- | ---
Standard | State | uint64 | 1 | 32
SocketSelectorTwoDevices | State | uint64 | 1 | 32

To avoid duplicating signals, it is possible to define Value Converters.

Converters are used to support more than one representation of the same signal (for example Angle/Torque Status can both be represented bitwise or as a status character).

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Tool in Production Space - 93

Name in SoftPLC: TOOL_IN_PRODUCT_SPACE

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# Tool in Work Space - 92

Name in SoftPLC: TOOL_IN_WORK_SPACE

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | Boolean | 1 | 1

## Devices

- Fieldbus: TRUE

- Indicator Box: TRUE

- Internal I/O: TRUE

- Operator Panel: TRUE

- Tool Functions: TRUE

- ST Selector: FALSE

- Stacklight: TRUE

- TLS Tag: TRUE

- I/O Expander: TRUE

# User ID - 10050

Name in SoftPLC: USER_ID

Signal Type | Value Type | Size Min [bit] | Size Max [bit]
--- | --- | --- | ---
State | String | 8 | 800

## Devices

- Fieldbus: TRUE

- Indicator Box: FALSE

- Internal I/O: FALSE

- Operator Panel: FALSE

- Tool Functions: FALSE

- ST Selector: FALSE

- Stacklight: FALSE

- TLS Tag: FALSE

- I/O Expander: FALSE

# Input Signals: Sub-signals

Select the needed input signal to examine the related sub-signals:

- Channel Command -10054

In this Section

- Channel Command - 10054: Sub-signals

# Channel Command - 10054: Sub-signals

# Continue Step

If in a Wait tightening step with the condition Signal configured as Wait Type, through the sub-signal Continue Step, it is possible to control tools individually and let the tightening continue.

For more information, see the input signal Continue Step - 10128.

Name in SoftPLC: CHANNEL_COMMAND_CONTINUE_STEP

Value Type | Start bit | Length | Size Min [bit] | Size Max [bit]
--- | --- | --- | --- | ---
Boolean | 3 | 1 | 1 | 1

# Force Bolt ID

Name in SoftPLC: CHANNEL_COMMAND_FORCE_BOLT_ID

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Integer | 1 | 8

# Force Pset

Name in SoftPLC: CHANNEL_COMMAND_FORCE_PSET

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Integer | 1 | 8

# Inhibit No Result

Name in SoftPLC: CHANNEL_COMMAND_NO_RESULT

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Boolean | 1 | 1

# Inhibit NOK Result

Name in SoftPLC: CHANNEL_COMMAND_NOK_RESULT

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Boolean | 1 | 1

# Inhibit OK Result

Name in SoftPLC: CHANNEL_COMMAND_OK_RESULT

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Boolean | 1 | 1

# Output Signals: Sub-signals

Select the needed output signal to examine the related sub-signals:

- Bolt Tightening Status - 79

- Channel Tightening Status - 80

- Channel Hardware Status - 81

In this Section

- Bolt Tightening Status - 79: Sub-signals
- Channel Tightening Status - 80: Sub-signals
- Channel Hardware Status - 81: Sub-signals

# Bolt Tightening Status - 79: Sub-signals

# All Signals

Name in SoftPLC: CYCLE_STATUS_ALL

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Integer | 1 | 32

# Cycle Running

Name in SoftPLC: CYCLE_STATUS_RUNNING

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Boolean | 1 | 1

# In Selected Mode

Name in SoftPLC: CYCLE_STATUS_IN_SELECTED_MODE

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Boolean | 1 | 1

# Inhibited

Name in SoftPLC: CYCLE_STATUS_INHIBITED

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Boolean | 1 | 1

# Last Cycle Angle High

Name in SoftPLC: CYCLE_STATUS_LAST_CYCLE_ANGLE_HIGH

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Boolean | 1 | 1

# Last Cycle Angle Low

Name in SoftPLC: CYCLE_STATUS_LAST_CYCLE_ANGLE_LOW

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Boolean | 1 | 1

# Last Cycle Hardware Error

Name in SoftPLC: CYCLE_STATUS_LAST_CYCLE_HW_ERROR

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Boolean | 1 | 1

# Last Cycle Inhibited

Name in SoftPLC: CYCLE_STATUS_LAST_CYCLE_INHIBITED

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Boolean | 1 | 1

# Last Cycle NOK

Name in SoftPLC: CYCLE_STATUS_LAST_CYCLE_NOK

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Boolean | 1 | 1

# Last Cycle Not Included

Name in SoftPLC: CYCLE_STATUS_LAST_CYCLE_NOT_INCLUDED

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Boolean | 1 | 1

# Last Cycle OK

Name in SoftPLC: CYCLE_STATUS_LAST_CYCLE_OK

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Boolean | 1 | 1

# Last Cycle Terminated By Other

Name in SoftPLC: CYCLE_STATUS_LAST_CYCLE_TERMINATED_BY_OTHER

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Boolean | 1 | 1

# Last Cycle Timeout

Name in SoftPLC: CYCLE_STATUS_LAST_CYCLE_TIMEOUT

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Boolean | 1 | 1

# Last Cycle Torque High

Name in SoftPLC: CYCLE_STATUS_LAST_CYCLE_TORQUE_HIGH

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Boolean | 1 | 1

# Last Cycle Torque Low

Name in SoftPLC: CYCLE_STATUS_LAST_CYCLE_TORQUE_LOW

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Boolean | 1 | 1

# Last Loosening NOK

Name in SoftPLC: CYCLE_STATUS_LAST_LOOSENING_NOK

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Boolean | 1 | 1

# Last Loosening OK

Name in SoftPLC: CYCLE_STATUS_LAST_LOOSENING_OK

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Boolean | 1 | 1

# Last Tightening NOK

Name in SoftPLC: CYCLE_STATUS_LAST_TIGHTENING_NOK

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Boolean | 1 | 1

# Last Tightening OK

Name in SoftPLC: CYCLE_STATUS_LAST_TIGHTENING_OK

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Boolean | 1 | 1

# Loosening Running

Name in SoftPLC: CYCLE_STATUS_RUNNING_LOOSENING

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Boolean | 1 | 1

# Running Repair

Name in SoftPLC: CYCLE_STATUS_REPAIR

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Boolean | 1 | 1

# Running Termination

Name in SoftPLC: CYCLE_STATUS_TERMINATE

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Boolean | 1 | 1

# Tightening Running

Name in SoftPLC: CYCLE_STATUS_RUNNING_TIGHTENING

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Boolean | 1 | 1

# Tool Led Mirror Green

Name in SoftPLC: CYCLE_STATUS_TOOL_LED_MIRROR_GREEN

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Boolean | 1 | 1

# Tool Led Mirror Red

Name in SoftPLC: CYCLE_STATUS_TOOL_LED_MIRROR_RED

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Boolean | 1 | 1

# Tool Led Mirror Yellow

Name in SoftPLC: CYCLE_STATUS_TOOL_LED_MIRROR_YELLOW

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Boolean | 1 | 1

# Waiting To Continue

If in a Wait tightening step with the condition Signal configured as Wait Type, through the sub-signal Waiting To Continue, each individual bolt shows if the related status is waiting for an input to continue.

For more information, see the output signal Waiting To Continue - 201.

Name in SoftPLC: CYCLE_STATUS_WAITING_FOR_CONTINUE

Value Type | Start bit | Length | Size Min [bit] | Size Max [bit]
--- | --- | --- | --- | ---
Boolean | 7 | 1 | 1 | 1

# Channel Tightening Status - 80: Sub-signals

# All Signals

Name in SoftPLC: CYCLE_STATUS_ALL

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Integer | 1 | 32

# Cycle Running

Name in SoftPLC: CYCLE_STATUS_RUNNING

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Boolean | 1 | 1

# In Selected Mode

Name in SoftPLC: CYCLE_STATUS_IN_SELECTED_MODE

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Boolean | 1 | 1

# Inhibited

Name in SoftPLC: CYCLE_STATUS_INHIBITED

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Boolean | 1 | 1

# Last Cycle Angle High

Name in SoftPLC: CYCLE_STATUS_LAST_CYCLE_ANGLE_HIGH

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Boolean | 1 | 1

# Last Cycle Angle Low

Name in SoftPLC: CYCLE_STATUS_LAST_CYCLE_ANGLE_LOW

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Boolean | 1 | 1

# Last Cycle Hardware Error

Name in SoftPLC: CYCLE_STATUS_LAST_CYCLE_HW_ERROR

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Boolean | 1 | 1

# Last Cycle Inhibited

Name in SoftPLC: CYCLE_STATUS_LAST_CYCLE_INHIBITED

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Boolean | 1 | 1

# Last Cycle NOK

Name in SoftPLC: CYCLE_STATUS_LAST_CYCLE_NOK

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Boolean | 1 | 1

# Last Cycle Not Included

Name in SoftPLC: CYCLE_STATUS_LAST_CYCLE_NOT_INCLUDED

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Boolean | 1 | 1

# Last Cycle OK

Name in SoftPLC: CYCLE_STATUS_LAST_CYCLE_OK

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Boolean | 1 | 1

# Last Cycle Terminated By Other

Name in SoftPLC: CYCLE_STATUS_LAST_CYCLE_TERMINATED_BY_OTHER

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Boolean | 1 | 1

# Last Cycle Timeout

Name in SoftPLC: CYCLE_STATUS_LAST_CYCLE_TIMEOUT

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Boolean | 1 | 1

# Last Cycle Torque High

Name in SoftPLC: CYCLE_STATUS_LAST_CYCLE_TORQUE_HIGH

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Boolean | 1 | 1

# Last Cycle Torque Low

Name in SoftPLC: CYCLE_STATUS_LAST_CYCLE_TORQUE_LOW

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Boolean | 1 | 1

# Last Loosening NOK

Name in SoftPLC: CYCLE_STATUS_LAST_LOOSENING_NOK

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Boolean | 1 | 1

# Last Loosening OK

Name in SoftPLC: CYCLE_STATUS_LAST_LOOSENING_OK

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Boolean | 1 | 1

# Last Tightening NOK

Name in SoftPLC: CYCLE_STATUS_LAST_TIGHTENING_NOK

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Boolean | 1 | 1

# Last Tightening OK

Name in SoftPLC: CYCLE_STATUS_LAST_TIGHTENING_OK

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Boolean | 1 | 1

# Loosening Running

Name in SoftPLC: CYCLE_STATUS_RUNNING_LOOSENING

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Boolean | 1 | 1

# Running Repair

Name in SoftPLC: CYCLE_STATUS_REPAIR

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Boolean | 1 | 1

# Running Termination

Name in SoftPLC: CYCLE_STATUS_TERMINATE

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Boolean | 1 | 1

# Tightening Running

Name in SoftPLC: CYCLE_STATUS_RUNNING_TIGHTENING

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Boolean | 1 | 1

# Tool Led Mirror Green

Name in SoftPLC: CYCLE_STATUS_TOOL_LED_MIRROR_GREEN

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Boolean | 1 | 1

# Tool Led Mirror Red

Name in SoftPLC: CYCLE_STATUS_TOOL_LED_MIRROR_RED

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Boolean | 1 | 1

# Tool Led Mirror Yellow

Name in SoftPLC: CYCLE_STATUS_TOOL_LED_MIRROR_YELLOW

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Boolean | 1 | 1

# Waiting To Continue

If in a Wait tightening step with the condition Signal configured as Wait Type, through the sub-signal Waiting To Continue, each individual channel shows if the related status is waiting for an input to continue.

For more information, see the output signal Waiting To Continue - 201.

Name in SoftPLC: CYCLE_STATUS_WAITING_FOR_CONTINUE

Value Type | Start bit | Length | Size Min [bit] | Size Max [bit]
--- | --- | --- | --- | ---
Boolean | 7 | 1 | 1 | 1

# Channel Hardware Status - 81: Sub-signals

# All Signals

Name in SoftPLC: CYCLE_STATUS_ALL

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Integer | 1 | 32

# Drive Disconnected

Name in SoftPLC: CHANNEL_HW_STATUS_DRIVE_DISCONNECTED

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Boolean | 1 | 1

# Drive Temp High

Name in SoftPLC: CHANNEL_HW_STATUS_DRIVE_TEMP_HIGH

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Boolean | 1 | 1

# Drive Voltage Error

Name in SoftPLC: CHANNEL_HW_STATUS_DRIVE_VOLTAGE_ERROR

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Boolean | 1 | 1

# Emergency Stop Active

Name in SoftPLC: CHANNEL_HW_STATUS_EMERGENCY_STOP_ACTIVE

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Boolean | 1 | 1

# General Hardware Error

Name in SoftPLC: CHANNEL_HW_STATUS_GENERAL_ERROR

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Boolean | 1 | 1

# Motortune Needed

Name in SoftPLC: CHANNEL_HW_STATUS_MOTORTUNE_NEEDED

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Boolean | 1 | 1

# Ready to Operate

This sub-signal is set if none of the following errors are found on the tool or drive:

- Tool disconnected

- Drive disconnected

- Tool any hardware error

- Drive any hardware error

- Emergency stop active

Name in SoftPLC: CHANNEL_HW_STATUS_READY_TO_OPERATE

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Boolean | 1 | 1

# Tool Cable Invalid

Name in SoftPLC: CHANNEL_HW_STATUS_TOOL_CABLE_INVALID

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Boolean | 1 | 1

# Tool Disconnected

Name in SoftPLC: CHANNEL_HW_STATUS_TOOL_DISCONNECTED

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Boolean | 1 | 1

# Tool Temp High

Name in SoftPLC: CHANNEL_HW_STATUS_TOOL_TEMP_HIGH

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Boolean | 1 | 1

# Torque Transducer Error

Name in SoftPLC: CHANNEL_HW_STATUS_TORQUE_TRANSDUCER_ERROR

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Boolean | 1 | 1

# Tool Hardware Error

This sub-signal is set for a collection of health parameters and can indicate any of the following: ToolGround, ToolIndicatorBoard, ToolFanVoltage, ToolAccessoryBusVoltage, ToolParameterFile or ToolTriggerS.

Name in SoftPLC: CHANNEL_HW_STATUS_TOOL_HARDWARE_ERROR

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Boolean | 1 | 1

# Tool Any Hardware Error

This sub-signal is set whenever a tool hardware error is detected. This can be any of Tool Temp High, Motortune Needed, Tool Cable Invalid, Tool Disconnected, Torque Transducer Error or Tool Hardware Error.

Name in SoftPLC: CHANNEL_HW_STATUS_TOOL_ANY_HARDWARE_ERROR

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Boolean | 1 | 1

# Drive Any Hardware Error

This sub-signal is set whenever a drive hardware error is detected. This can be any of Drive Temp High, Drive Voltage Error, or Drive Disconnected.

Name in SoftPLC: CHANNEL_HW_STATUS_DRIVE_ANY_HARDWARE_ERROR

Value Type | Size Min [bit] | Size Max [bit]
--- | --- | ---
Boolean | 1 | 1

# Acyclic Result Items

This section shows lists of result items that can be sent as acyclic data and a table for explanation of data types.

Data types
Data types | Description
--- | ---
Int8 | Value is formatted as a one-byte signed integer. For float any fractional part rounded, see below. For integers the least significant byte is kept.
Int16 | Value is formatted as a two-byte signed integer. For float any fractional part rounded, see below. For integers the least significant bytes is kept.
Int32 | Value is formatted as a four-byte signed integer. For float any fractional part rounded, see below. For integers the least significant bytes is kept.
Int64 | Value is formatted as a eight-byte signed integer. For float any fractional part rounded, see below.
Float32 | Value is formatted as a four-byte signed IEEE754 float value.
Fixed32 | Value is formatted as a four-byte integer. The two most significant bytes contains the integer part and the two least significant bytes the decimal part multiplied with 10000.
String | Value is formatted as a string. The number of bytes assigned will be the number of characters sent.

Round X to nearest integral value, rounding halfway cases away from zero.

Multiple tightening
Name | Description | Data types
--- | --- | ---
Status | Status of the multiple tightening or loosening (OK or NOK): NotSet = 0 OK = 1 NOK = 2 | Int32 (unsigned) Int16 (unsigned) Int8 (unsigned)
Total status additional information | Added information about the result, valid for both OK and NOK results, refer to Overall Status Additional Information. | Int32 (unsigned) Int16 (unsigned) Int8 (unsigned)
Sync mode name | The name of the sync mode used in the tightening | String (1-80 characters)
Sync mode index | The index of the sync mode used in the tightening | Int32 (unsigned) Int16 (unsigned) Int8 (unsigned)

Result Notification
Name | Description | Data types
--- | --- | ---
Virtual Station name | The name of the virtual station | String (1-80 characters)
Date and time | Time stamp for the tightening result UNIX format time stamp, number of seconds since 1970 | Int32 (unsigned) Int16 (unsigned) Int8 (unsigned)
VIN | VIN number in the tightening result | String (1-80 characters)

Batch Sequence
Name | Description | Data Types
--- | --- | ---
Batch Sequence counter |  | Int32 (unsigned) Int16 (unsigned) Int8 (unsigned)
Batch Sequence Current status | Status of the batch sequence: CompletedOK = 0 CompletedNOK = 1 NotComplete = 2 | Int32 (unsigned) Int16 (unsigned) Int8 (unsigned)
Batch size |  | Int32 (unsigned) Int16 (unsigned) Int8 (unsigned)
Batch current status | Status of the batch: CompletedOK = 0 CompletedNOK = 1 NotComplete = 2 | Int32 (unsigned) Int16 (unsigned) Int8 (unsigned)
Batch count |  | Int32 (unsigned) Int16 (unsigned) Int8 (unsigned)
Batch sequence name | The name of the batch sequence | String (1-80 characters)
Batch sequence index |  | Int32 (unsigned) Int16 (unsigned) Int8 (unsigned)

Multistep Tightening
Name | Description | Data types
--- | --- | ---
Tightening Program Name | The name of the program used for tightening or loosening. | String (1-80 characters)
Operation mode | Indicates if the result is a tightening or a loosening operation: NotSet = 0 Tightening = 1 Loosening = 2 | Int32 (unsigned) Int16 (unsigned) Int8 (unsigned)
Status | Status of the tightening or loosening (OK or NOK): NotSet = 0 OK = 1 NOK = 2 | Int32 (unsigned) Int16 (unsigned) Int8 (unsigned)
Status info | Added information about the result, valid for both OK and NOK results, refer to Overall Status Additional Information. | Int32 (unsigned) Int16 (unsigned) Int8 (unsigned)
Stopping error | Main error from the tightening, refer to Stopping error codes for possible values. | Int32 (unsigned) Int16 (unsigned) Int8 (unsigned)
Bolt Number | The number of the bolt that was tightened | Int32 (unsigned) Int16 (unsigned) Int8 (unsigned)
Bolt Name | The name of the bolt that was tightened | String (1-80 characters)
Channel | The number of the tightening channel (tool) that made the tightening | Int32 (unsigned) Int16 (unsigned) Int8 (unsigned)
Failing Step | In case of a NOK tightening indicates the step causing the NOK | Int32 (unsigned) Int16 (unsigned) Int8 (unsigned)
Final Torque | Measured Final Torque, unit [Nm] | Int16 (signed) Fixed32 (signed) Float32 (signed)
Torque low limit | Low limit for the Final Torque, as configured in the tightening program, unit [Nm] | Int16 (signed) Fixed32 (signed) Float32 (signed)
Torque high limit | High limit for the Final Torque, as configured in the tightening program, unit [Nm] | Int16 (signed) Fixed32 (signed) Float32 (signed)
Final Angle | Measured Final Angle, unit [deg] | Int16 (signed) Fixed32 (signed) Float32 (signed)
Angle low limit | Low limit for the Final Angle, as configured in the tightening program, unit [deg] | Int16 (signed) Fixed32 (signed) Float32 (signed)
Angle high limit | High limit for the Final Angle, as configured in the tightening program, unit [deg] | Int16 (signed) Fixed32 (signed) Float32 (signed)
Elapsed time | Total time needed for the tightening, unit [s] | Int16 (signed) Fixed32 (signed) Float32 (signed)
Target Angle | Target angle for the tightening, for Angle controlled process, unit [deg] | Int16 (signed) Fixed32 (signed) Float32 (signed)
Target Torque | Target torque for the tightening, for Torque controlled process, unit [Nm] | Int16 (signed) Fixed32 (signed) Float32 (signed)
Final Angle Torque Trigger | Torque trigger for the final angle measurement, unit [Nm] | Int16 (signed) Fixed32 (signed) Float32 (signed)
Tool article number | Article (product number) of the tool used in the tightening | String (1-80 characters)
Tool serial number | Serial number of the tool used in the tightening | String (1-80 characters)
Compact Error | Tightening errors in a "compact" format. Bit-coded with the following definitions: bit 0: Torque High bit 1: Torque Low bit 2: Angle High bit 3: Angle Low bit 4: Tightening OK bit 5: Spare bit 6: Spare bit 7: Spare | Int8 (unsigned)

Program Monitor
Name | Description | Data types
--- | --- | ---
Angle | Angle measured with Program Monitor angle, unit [deg] | Int16 (signed) Fixed32 Float32
Angle Torque Trigger | Torque trigger for the Program Monitor angle, unit [Nm] | Int16 (signed) Fixed32 Float32
Torque | Torque measured with Program Monitor angle, unit [Nm] | Int16 (signed) Fixed32 Float32

Program Restrictions
Name | Description | Data Types
--- | --- | ---
Torque difference | Highest measured torque difference between T1 and T2, for tools with multiple torque transducers, unit [Nm] | Int16 (signed) Fixed32 Float32
Angle difference | Highest measured angle difference between A1 and A2, for tools with multiple angle transducers, unit [deg] | Int16 (signed) Fixed32 Float32
Maximum Time Limit | Maximum allowed time for the tightening, as configured in the tightening program, unit [s] | Int16 (signed) Fixed32 Float32

Step Monitor
Name | Description | Data types
--- | --- | ---
Peak Torque | Value measured with step monitor PT - Peak Torque, unit [Nm]. | Int16 (signed) Fixed32 Float32
Shut off Torque | Value measured with step monitor SOT - Shut Off Torque, unit [Nm]. | Int16 (signed) Fixed32 Float32
Mean Torque | Value measured with step monitor MT - Mean Torque, unit [Nm]. | Int16 (signed) Fixed32 Float32
Angle | Value measured with step monitor A - Angle,unit [deg]. | Int16 (signed) Fixed32 Float32
Angle Torque Trigger | Measured torque trigger for the step monitor A - Angle, unit [Nm]. | Int16 (signed) Fixed32 Float32
Torque Rate | Torque rate measured with step monitor TRD - Torque Rate and Deviation, unit [Nm/deg]. | Int16 (signed) Fixed32 Float32
Torque Rate Deviation | Torque rate deviation measured with step monitor TRD - Torque Rate and Deviation, unit [Nm]. | Int16 (signed) Fixed32 Float32
Measured Post Thread Cut Angle | Value measured with step monitor PTCA - Post Thread Cut Angle, unit [deg]. | Int16 (signed) Fixed32 Float32
Measured Post Thread Cut Peak Torque | Value measured with step monitor PTCPT - Post Thread Cut Peak Torque, unit [Nm]. | Int16 (signed) Fixed32 Float32
Peak Torque in angle window | Value measured with step monitor PT - Peak Torque, unit [Nm]. | Int16 (signed) Fixed32 Float32
Low Torque in angle window | Value measured with step monitor TAW - Torque in Angle Window, unit [Nm]. | Int16 (signed) Fixed32 Float32
Post View Torque High | Value measured with step monitor PVTH - Post View Torque High, unit [Nm]. | Int16 (signed) Fixed32 Float32
Angle at Post View Torque High | Value measured with step monitor PVTH - Post View Torque High, unit [deg]. | Int16 (signed) Fixed32 Float32
Post View Torque Low | Value measured with step monitor PVTL - Post View Torque Low, unit [Nm]. | Int16 (signed) Fixed32 Float32
Angle at Post View Torque Low | Value measured with step monitor PVTL - Post View Torque Low, unit [deg]. | Int16 (signed) Fixed32 Float32
Yield Angle | Value measured with step monitor YA - Angle from Yield, unit [deg]. | Int16 (signed) Fixed32 Float32
Torque Gradient | Value measured with step monitor TG - Torque Gradient, unit [Nm/deg]. | Int16 (signed) Fixed32 Float32
Stick Slip Detection - Measured number of oscillations | Value measured with step monitor SSD - Stick Slip Detection, unit [no. of oscillations. | Int16 (signed) Fixed32 Float32
Shut Off current | Value measured with step monitor SOC - Shut Off Current, unit [A]. | Int16 (signed) Fixed32 Float32
Prevailing Torque | Value measured with step monitor PrT - Prevailing Torque, unit [Nm]. | Int16 (signed) Fixed32 Float32
Monitor Time | Value measured with step monitor Ti - Time, unit [s]. | Int16 (signed) Fixed32 Float32
Monitor Current | Value measured with step monitor C - Current, unit [A]. | Int16 (signed) Fixed32 Float32
Peak Torque - Low Limit | Limit as configured in step monitor PT - Peak Torque, unit [Nm]. | Int16 (signed) Fixed32 Float32
Peak Torque - High Limit | Limit as configured in step monitor PT - Peak Torque, unit [Nm]. | Int16 (signed) Fixed32 Float32
Shut Off Torque - Low Limit | Limit as configured in step monitor SOT - Shut Off Torque, unit [Nm]. | Int16 (signed) Fixed32 Float32
Shut Off Torque - High Limit | Limit as configured in step monitor SOT - Shut Off Torque, unit [Nm]. | Int16 (signed) Fixed32 Float32
Mean Torque - Low Limit | Limit as configured in step monitor MT - Mean Torque, unit [Nm]. | Int16 (signed) Fixed32 Float32
Mean Torque - High Limit | Limit as configured in step monitor MT - Mean Torque, unit [Nm]. | Int16 (signed) Fixed32 Float32
Torque Rate and deviation - Torque Rate Low Limit | Limit as configured in step monitor TRD - Torque Rate and Deviation, unit [Nm/deg]. | Int16 (signed) Fixed32 Float32
Torque Rate and deviation - Torque Rate High Limit | Limit as configured in step monitor TRD - Torque Rate and Deviation, unit [Nm/deg]. | Int16 (signed) Fixed32 Float32
Torque rate and deviation - Deviation Limit | Limit as configured in step monitor TRD - Torque Rate and Deviation, unit [Nm]. | Int16 (signed) Fixed32 Float32
Torque in angle window - Low Limit | Limit as configured in step monitor TAW - Torque in Angle Window, unit [Nm]. | Int16 (signed) Fixed32 Float32
Torque in angle window - High Limit | Limit as configured in step monitor TAW - Torque in Angle Window, unit [Nm]. | Int16 (signed) Fixed32 Float32
Post View Torque High - High Limit | Limit as configured in step monitor PVTH - Post View Torque High, unit [Nm]. | Int16 (signed) Fixed32 Float32
Post View Torque Low - Low Limit | Limit as configured in step monitor PVTL - Post View Torque Low, unit [Nm]. | Int16 (signed) Fixed32 Float32
Angle from Yield - High Limit | Limit as configured in step monitor YA - Angle from Yield, unit [deg]. | Int16 (signed) Fixed32 Float32
Angle from Yield - Low Limit | Limit as configured in step monitor YA - Angle from Yield, unit [deg]. | Int16 (signed) Fixed32 Float32
Torque Gradient - High Limit | Limit as configured in step monitor TG - Torque Gradient, unit [Nm/deg]. | Int16 (signed) Fixed32 Float32
Torque Gradient - Low Limit | Limit as configured in step monitor TG - Torque Gradient, unit [Nm/deg]. | Int16 (signed) Fixed32 Float32
Shut Off current - Low Limit | Limit as configured in step monitor SOC - Shut Off Current, unit [A]. | Int16 (signed) Fixed32 Float32
Shut Off current - High Limit | Limit as configured in step monitor SOC - Shut Off Current, unit [A]. | Int16 (signed) Fixed32 Float32
Prevailing Torque - High Limit | Limit as configured in step monitor PrT - Prevailing Torque, unit [Nm]. | Int16 (signed) Fixed32 Float32
Prevailing Torque - Low Limit | Limit as configured in step monitor PrT - Prevailing Torque, unit [Nm]. | Int16 (signed) Fixed32 Float32
Time - Low Limit | Limit as configured in step monitor Ti - Time, unit [s]. | Int16 (signed) Fixed32 Float32
Time - High Limit | Limit as configured in step monitor Ti - Time, unit [s]. | Int16 (signed) Fixed32 Float32
Monitor Current - Limit Low | Limit as configured in step monitor C - Current, unit [A]. | Int16 (signed) Fixed32 Float32
Monitor Current - Limit High | Limit as configured in step monitor C - Current, unit [s]. | Int16 (signed) Fixed32 Float32
Angle - High Limit | Limit as configured in step monitor A - Angle, unit [deg]. | Int16 (signed) Fixed32 Float32
Angle - Low Limit | Limit as configured in step monitor A - Angle, unit [deg]. | Int16 (signed) Fixed32 Float32
Yield Point Torque | Value measured with step monitor YA - Angle from Yield, unit [Nm]. | Int16 (signed) Fixed32 Float32
Yield Point Gradient | Value measured with step monitor YA - Angle from Yield, unit [Nm/deg]. | Int16 (signed) Fixed32 Float32
Peak Gradient | Value measured with step monitor YA - Angle from Yield, unit [Nmdeg]. | Int16 (signed) Fixed32 Float32

Step Restriction
Name | Description | Data types
--- | --- | ---
Cross Thread | Value measured with step restrictionCTh - Cross Thread, unit [deg]. | Int16 (signed) Fixed32 Float32
Elapsed time | Value measured with step restriction Ti - Time, unit [s]. | Int16 (signed) Fixed32 Float32
Restriction Current | Value measured with step restriction C - Current, unit [A]. | Int16 (signed) Fixed32 Float32
Maximum Time - High Limit | Limit as configured in step restriction Ti - Time, unit [s]. | Int16 (signed) Fixed32 Float32
Restriction Current - High Limit | Limit as configured in step restriction C - Current, unit [A]. | Int16 (signed) Fixed32 Float32
Restriction Current - Low Limit | Limit as configured in step restriction C - Current, unit [A]. | Int16 (signed) Fixed32 Float32
Cross Thread - Minimum Limit | Limit as configured in step restriction CTh - Cross Thread, unit [deg]. | Int16 (signed) Fixed32 Float32
Cross Thread - Maximum Limit | Limit as configured in step restriction CTh - Cross Thread, unit [deg]. | Int16 (signed) Fixed32 Float32

# Stopping error codes

Error code |
--- | ---
0 | Not Set
1 | Brake Failed
2 | Trigger Lost
3 | ShuntCalibration ShuntFailed
4 | ShuntCalibration ZeroOffsetFailed
5 | Overload
6 | Cycle Interrupted
10011 | StepPositioning PositionNotSet
10012 | Engage Failed
10013 | StepMechatronicWrench AngularSpeedHigh
10014 | StepMechatronicWrench LooseningLimitReached
10015 | StepMechatronicWrench Rehit
10021 | StepWrenchProduction OverSpeed
10022 | StepWrenchProduction NoResidualTorque
10023 | StepWrenchProduction SnugMonitorHigh
10024 | StepWrenchProduction Rehit
10025 | StepWrenchProduction TighteningTimeout
10031 | StepWrenchQuality OverSpeed
10032 | StepWrenchQuality NoResidualTorque
10033 | StepWrenchQuality SnugMonitorHigh
10034 | StepWrenchQuality Rehit
10035 | StepWrenchQuality Tightening Timeout
10041 | StepTensorPulse PulseDriveSocketNotDetected
10051 | StepResidualTorquePeakWrench ResidualTorqueNotDetected
10052 | StepResidualTorqueAngleWrench ResidualPointNotDetected
20011 | StepMonitor PeakAngle AngleNotMeasured
20012 | StepMonitor PeakAngle AngleLow
20013 | StepMonitor PeakAngle AngleHigh
20021 | StepMonitor PeakTorque TorqueNotMeasured
20022 | StepMonitor PeakTorque TorqueLow
20023 | StepMonitor PeakTorque TorqueHigh
20031 | StepMonitor MeanTorque TorqueNotMeasured
20032 | StepMonitor MeanTorque TorqueLow
20033 | StepMonitor MeanTorque TorqueHigh
20041 | StepMonitor ShutOffTorque TorqueNotMeasured
20042 | StepMonitor ShutOffTorque TorqueLow
20043 | StepMonitor ShutOffTorque TorqueHigh
20051 | StepMonitor TorqueRate TorqueRateNotMeasured
20052 | StepMonitor TorqueRate TorqueRateLow
20053 | StepMonitor TorqueRate TorqueRateHigh
20054 | StepMonitor TorqueRate TorqueRateDeviationTooBig
20055 | StepMonitor TorqueRate TorqueRateDeviationNotMeasured
20061 | StepMonitor Angle AngleNotMeasured
20062 | StepMonitor Angle AngleLow
20063 | StepMonitor Angle AngleHigh
20071 | StepMonitor PostThreadCutAngle AngleNotMeasured
20072 | StepMonitor PostThreadCutAngle AngleLow
20073 | StepMonitor PostThreadCutAngle AngleHigh
20081 | StepMonitor PostThreadCutPeakTorque TorqueNotMeasured
20082 | StepMonitor PostThreadCutPeakTorque TorqueLow
20083 | StepMonitor PostThreadCutPeakTorque TorqueHigh
20091 | StepMonitor TorqueInAngleWindow TorqueNotMeasured
20092 | StepMonitor TorqueInAngleWindow TorqueLow
20093 | StepMonitor TorqueInAngleWindow TorqueHigh
20101 | StepMonitor PostViewAverageTorqueHigh TorqueNotMeasured
20102 | StepMonitor PostViewAverageTorqueHigh TorqueHigh
20111 | StepMonitor PostViewAverageTorqueLow TorqueNotMeasured
20112 | StepMonitor PostViewAverageTorqueLow TorqueLow
20121 | StepMonitor YieldAngle AngleNotMeasured
20122 | StepMonitor YieldAngle AngleLow
20123 | StepMonitor YieldAngle AngleHigh
20131 | StepMonitor StickSlipDetection DropNotMeasured
20132 | StepMonitor StickSlipDetection DropBelowTrigger
20141 | StepMonitor ShutOffCurrent CurrentNotMeasured
20142 | StepMonitor ShutOffCurrent CurrentLow
20143 | StepMonitor ShutOffCurrent CurrentHigh
20151 | StepMonitor PrevailingTorque TorqueNotMeasured
20152 | StepMonitor PrevailingTorque TorqueLow
20153 | StepMonitor PrevailingTorque TorqueHigh
20161 | StepMonitor PulseCount CountNotMeasured
20162 | StepMonitor PulseCount CountLow
20163 | StepMonitor PulseCount CountHigh
20171 | StepMonitor Time TimeNotMeasured
20172 | StepMonitor Time TimeLow
20173 | StepMonitor Time TimeHigh
20181 | StepMonitor TorqueCalibration TorqueNotMeasured
20182 | StepMonitor TorqueCalibration TorqueLow
20183 | StepMonitor TorqueCalibration TorqueHigh
20191 | StepMonitor Click ClickAngleNotMeasured
20192 | StepMonitor Click ClickTorqueNotMeasured
20201 | StepMonitor TorqueGradient GradientNotMeasured
20202 | StepMonitor TorqueGradient GradientLow
20203 | StepMonitor TorqueGradient GradientHigh
20211 | StepMonitor LooseningDetection EffectiveLoosening
20221 | StepMonitor Torque TorqueNotMeasured
20222 | StepMonitor Torque TorqueLow
20223 | StepMonitor Torque TorqueHigh
20231 | StepMonitor MotorCurrent CurrentNotMeasured
20232 | StepMonitor MotorCurrent CurrentLow
20233 | StepMonitor MotorCurrent CurrentHigh
30011 | StepRestriction TorqueHigh TorqueNotMeasured
30012 | StepRestriction TorqueHigh TorqueLow
30013 | StepRestriction TorqueHigh TorqueHigh
30021 | StepRestriction AngleHigh AngleNotMeasured
30022 | StepRestriction AngleHigh AngleLow
30023 | StepRestriction AngleHigh AngleHigh
30031 | StepRestriction TimeHigh TimeNotMeasured
30032 | StepRestriction TimeHigh TimeLow
30033 | StepRestriction TimeHigh TimeHigh
30041 | StepRestriction CrossThread AngleNotMeasured
30042 | StepRestriction CrossThread AngleLow
30043 | StepRestriction CrossThread AngleHigh
30051 | StepRestriction TorqueGradient GradientNotMeasured
30052 | StepRestriction TorqueGradient GradientLow
30053 | StepRestriction TorqueGradient GradientHigh
30061 | StepRestriction TorqueLow TorqueNotMeasured
30062 | StepRestriction TorqueLow TorqueLow
30071 | StepRestriction ExcessiveAngularRotation PositiveReached
30072 | StepRestriction ExcessiveAngularRotation NegativeReached
30081 | StepRestriction CurrentDeviation CurrentValue
30091 | StepRestriction PulseCountHigh CountHigh
30100 | StepRestriction TorqueInAngleWindow TorqueNotMeasured
30101 | StepRestriction TorqueInAngleWindow TorqueHigh
30102 | StepRestriction TorqueInAngleWindow TorqueLow
30110 | StepRestriction Rehit LimitReached
30120 | StepRestriction SpeedHigh SpeedNotMeasured
30121 | StepRestriction SpeedHigh SpeedHigh
30122 | StepRestriction SpeedHigh SpeedLow
30123 | StepRestriction MotorCurrent CurrentHigh
30124 | StepRestriction MotorCurrent CurrentLow
30125 | StepRestriction MotorCurrent CurrentNotMeasured
40011 | ProgramRestriction TorqueHigh TorqueNotMeasured
40012 | ProgramRestriction TorqueHigh TorqueLow
40013 | ProgramRestriction TorqueHigh TorqueHigh
40021 | ProgramRestriction TimeHigh TimeNotMeasured
40022 | ProgramRestriction TimeHigh TimeLow
40023 | ProgramRestriction TimeHigh TimeHigh
40031 | ProgramRestriction DualTorqueTransducer TransducerError
40032 | ProgramRestriction DualAngleTransducer TransducerError
40042 | ProgramRestriction Angle AngleHigh
40051 | ProgramRestriction Time TimeHigh
50011 | ProgramMonitor Angle AngleNotMeasured
50012 | ProgramMonitor Angle AngleHigh
50013 | ProgramMonitor Angle AngleLow
50021 | ProgramMonitor Torque TorqueNotMeasured
50022 | ProgramMonitor Torque TorqueHigh
50023 | ProgramMonitor Torque TorqueLow
50031 | ProgramMonitor Time TimeNotMeasured
50032 | ProgramMonitor Time TimeHigh
50033 | ProgramMonitor Time TimeLow

# Overall Status Additional Information

On the multiple level and the overall level for each bolt there is a field called Overall Status Additional Information . The possible parameters for this field are as follows:

Parameter | Comment | Additional information
--- | --- | ---
No status | No status is set for the tighteningResult | NoStatus = 0
Repaired | The total status of the tightening is OK, but at least one error that was repaired occurred during the tightening. | Repaired = 1
Terminated By Reject Management | The bolt did not have any errors of its own but was ordered to terminate due to an error on another bolt. | TerminatedByRejectManagement = 2
Reject Management Termination Failed | The bolt was ordered to terminate and an error occurred while executing the termination path. | RejectManagementTerminationFailed = 3
Stopped | The tightening was ended due to a stop signal from the outside, for example Machine stop sent through fieldbus or if the tool trigger was released. | Stopped = 4
Emergency Stopped | The tightening was ended due to emergency stop. | EmergencyStopped = 5
Tool Error | The tightening was ended due to a hardware error in the tool. | ToolError = 6
Drive Error | The tightening was ended due to a hardware error in the drive. | DriveError = 7
Inhibited | The device was not allowed to run, since outside signal blocked it. | Inhibited = 8
InvalidPset | The controller has loaded an invalid tightening program. | InvalidPset = 9
PreStartCheckFailed | The preStartCheck state of Controller failed, it can be many reasons, such as tool errors, emergencyStop is active and the system received a stop signal and so on. | PreStartCheckFailed = 10
Reject Management Repair Failed | The bolt was ordered to repair and an error occurred while executing the repair path. | RejectManagementRepairFailed = 11

# Printing Scenarios

Printing done at the station

Use this when the programs to print are on a controller and your have access to an Atlas Copco PC with TT2 standalone version installed. Printing a program while at the station by connecting to the Flex controller:

1. Select the tightening program and open it to view.

2. Use the print button at the upper right of the software to print the program. (Note for Windows 10 machines, when you use print option in TT2, there is an option available called “Microsoft print to pdf” by default. In earlier version, this option can be added either installing Adobe acrobat or installing Foxit PDF reader on older Windows machines).

Printing with PF6 FlexSystem with an active (online) Flex controller

Use this when the programs to print are in an exported xxx.tar.gz file from a controller that you have no longer access to. Printing a program using a tar.gz file exported from a system:

1. Connect to any PF6 Flex controller.

2. Export the current configuration (original configuration) from the controller. This is done to back up the existing system in order to be able to restore it at the end.

3. Import the configuration file that contains the tightening programs to print, into this controller.

4. Open and print the tightening programs as stated in the steps in Printing done at the station.

5. Import the original configuration saved in step 2 to return the controller to its original state.

Printing with PF6 FlexSystem with an inactive (offline) PF6 FlexSystem

This provides the easiest way to print a file (xxx.json file) without being in front of a system.

A .json file is created as a result of an export of a configuration from an offline controller (library).

1. Import the .json file to the library.

2. Open the configuration from the .json file in the library.

3. Open and print the tightening programs.

Converting between tar.gz and .json

A configuration can be moved between a connected controller and an offline controller; from XXX.tar.gz to XXX.json and vice versa.

Prerequisites:

- Flex controller

- TT2 Installation

To convert a .tar.gz file to a .json file:

1. Follow steps 1-3 in Printing with PF6 FlexSystem with an active (online) Flex controller.

2. Right-click on the controller name in the left column and “add to library”.

3. Go to library and find the controller name that was added to library as an offline controller.

4. Select the controller check box – manage – export a .json file.

To convert a .json file to a .tar.gz file:

1. Follow steps 1-2 in Printing with PF6 FlexSystem with an inactive (offline) Flex controller.

2. Select the controller check box – manage – distribute. This will pop up a list of checkbox items that you want to distribute to the connected controller. Check what is relevant and select Distribute.

3. Open the plant structure – controller, and export to get a xxx.tar.gz file.

# RabbitMQ Overview

An installation of RabbitMQ is needed to publish messages from ToolsTalk 2 to ToolsTalk 2 (from version 2.17).

After installing RabbitMQ, ensure that the prerequisites are met before starting the ToolsTalk 2 service. Refer to RabbitMQ Prerequisites.

For a general overview of the RabbitMQ installation, visit https://www.rabbitmq.com/install-windows.html.

Installation
Step | To Do | Check
--- | --- | ---
1 | Installing Erlang runtime Download the Erlang runtime installer: https://github.com/erlang/otp/releases/download/OTP-25.3/otp_win64_25.3.exe. Run the installer and follow the guide. Select the default values proposed by the guide. | ░░
2 | Installing RabbitMQ Download the RabbitMQ installer: https://github.com/rabbitmq/rabbitmq-server/releases/download/v3.11.28/rabbitmq-server-3.11.28.exe. Run the installer and follow the guide. Select the default values proposed by the guide. | ░░
3 | Enabling RabbitMQ Web Management Plugin, to manage RabbitMQ via a web browser On the Windows Start menu, select RabbitMQ Server/RabbitMQ Command Prompt (sbin). In the RabbitMQ Command Prompt (sbin dir), enter rabbitmq-plugins.bat enable rabbitmq_management. | ░░

Before the configuration of RabbitMQ make sure that the Atlas Copco Data Communication has been configured correctly.

Configuration
Step | To Do | Check
--- | --- | ---
4 | Configuring RabbitMQ Open a web browser on the same device where RabbitMQ is installed. Enter http://localhost:15672 as the URL. Sign in using Username: guest and Password: guest. Select the Admin tab and then select Add a user. Enter a Username and a Password. Select Admin and then select Add user. Set the permissions for the added user by selecting the user name from the users list. Select Set permission. | ░░

If you need to install ToolsTalk 2, see Installing Atlas Copco Data Communication.

If ToolsTalk 2 is already installed, run the DataCommunication Installation Configurator again to complete the settings, see Working with the DataCommunication Installation Configurator and Configuring the Settings Tab.

Verification
Step | To Do | Check
--- | --- | ---
5 | After ToolsTalk 2 is installed, the following entry appears in the ToolsTalk 2 log file, [2021-06-11 12:16:03.368 INF RabbitMqBroadcastClient.CreateConnectionAndExchange ] - Created RabbitMQ broadcast exchange: AtlasCopco_ACDC_ToolsTalk_Exchange. The log file is located in C:\ProgramData\Atlas Copco\Logs\DataCommunicationService. | ░░

# List of Third-Party Licenses

A JSON file that is installed with ToolsTalk 2 Server and Client lists third-party components that are used in ToolsTalk 2 software. The file is found in different locations depending on software type and deployment technology:

ToolsTalk2 Client

C:\Program Files (x86)\Atlas Copco\ToolsTalk Client\_manifest\spdx_2.2\manifest.spdx.json

ToolsTalk2 Server ClickOnce

C:\Program Files\Atlas Copco\ToolsTalk ClickOnce\Server\_manifest\spdx_2.2\manifest.spdx.json

ToolsTalk2 Server

C:\Program Files\Atlas Copco\ToolsTalk Server\_manifest\spdx_2.2\manifest.spdx.json

ToolsTalk2 StationSetup

C:\Program Files (x86)\Atlas Copco\ToolsTalk StationSetup\_manifest\spdx_2.2\manifest.spdx.json

# Security Scan False Positives

In cybersecurity, a false positive is a test result that is incorrectly classified as positive.

Black Duck SCA is security software that falsely claims a vulnerability that relates to WinSCP in ToolsTalk 2. ToolsTalk 2 uses the WinSCP .NET Assembly (licensed under MPL) to interact with the WinSCP executable (licensed under GPL). Because ToolsTalk 2 accesses the WinSCP executable through its public scripting interface and not as a library, ToolsTalk 2 itself is not required to be licensed under GPL.