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, the new generation software in controller programming, is ready to take your line management to the next level. The client-server based software solution is geared to provide 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 amount of unique features. Tailored to fit your needs and optimized to get the job done. It allows you to delegate additional features at any time to respective stations, through the embedded simple Functionality Management System (FMS). With 100% customizable user rights, you maintain quality control in complex production systems and increase uptime in production critical operations.

Features

• Configuration master of PowerFocus6000, PF6 FlexSystem, accessories, multistep, Fieldbus and Soft plc

• Traces analysis and export

• Line structure management

• Active directory and user administration

• Embedded Functionality Management System

• Programs library containing full history

• Offline and Global programming

• Line software visibility and management

Benefits

• Reduced training needed due to simple and user friendly interface

• Reduced defects with global programs and error notifications

• Efficient new product introduction through quick and easy line configuration

• Improved productivity due to visibility and traceability on program changes

• Increased uptime due to live results analysis and line software management

• Full line control thanks to 100% customizable user access permissions

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.

Liabilities and Warnings

• Liability

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.

Revision History

System Overview

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

Software Structure

Global icons

Icon	Description
	The ToolsTalk 2 system user administration. Selection of language, temperature and torque units.
	The Help icon shows the following: ToolsTalk 2 Software version. ToolsTalk 2 License type. ToolsTalk 2 Virtual Station information.
	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.
	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. Socket selector General Virtual Station. Tool configuration. Scanner. 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 & SoftPLC The workspace is used to configure the fieldbus, acyclic data and SoftPLC settings.
	Settings Controller preferences. Tool alarm settings. Controller network connections. Controller time and date configurations.
	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 .
	Libraries Includes submenus for managing library templates that can be reused among 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.
	System administration Includes functions for software update, import/export of configuration parameters, 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.
	Compare configuration Select configuration files to compare.
	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.

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.

Conventions

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

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

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 Restrictions

• Compatibility Matrix
• Before Installing or Upgrading
• Database Requirements
• Computer Requirements
• License Requirements

Compatibility Matrix

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

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.

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.

Server Installation

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

Before starting the installation, make sure the following is available:

• Administrator rights to the computer upon which the server application is to be installed.

• Administrator rights to the computer upon which the client application is to be installed.

• Computers and programs according to the listed prerequisites.

• A completed installation of the 64-bit Microsoft SQL database according to the listed prerequisites.

• An executable file for the server application.

• An executable file for the client application.

• Atlas Copco Data Communication (ACDC) is installed and running and is compatible with the current version of the ToolsTalk 2 (only for versions of ToolsTalk 2 from 2.13 onwards). Please see the Atlas Copco Data Communication Installation Manual.

Station Setup

Before starting the installation, make sure the following is available:

• Administrator rights to the computer upon which the application is to be installed.

• Computers and programs according to the listed prerequisites.

• An executable file for the Station Setup application.

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 a standard installation.

• The Microsoft SQL database may be located on the same server or the same network as the ToolsTalk 2 application.

• If the database is located elsewhere, firewall needs to be properly configured between the database and the ToolsTalk 2 application server.

• The IP address of the Atlas Copco Data Communication server must be known and 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.

• Select both Microsoft SQL server authentication and windows authentication.

Recommended when installing the Microsoft SQL database

• Include the management studio in the installation.

• Enable the default instances.

Computer Requirements

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

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

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 Sequence

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

Software Installation

• ToolsTalk2 Configuration Window
• Default Installation Locations
• Installing the ToolsTalk Server Application
• Installing the Client Application
• Installing the Client by Using ClickOnce
• Installing the Station Setup Application
  • Station Setup Connection
• File Comparison
• SoftPLC Configurator 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

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 ToolsTalk 2 from 2.13 onwards). Please see the Atlas Copco Data Communication Installation Manual.

Server Settings Parameters

Database Settings

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.

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

Database Installation Settings

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.

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.

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

Installing the Client by Using ClickOnce

Server Settings Parameters

Database Settings

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.

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

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

Database Installation Settings

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.

Deploying the Client On a Remote Machine

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 the customer 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.

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.

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.

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.

Installation Validation

• Validating Windows System Services
• Validating the Client-Server Installation
• Validating the Station Setup Installation
• Validating the License Service

Validating Windows System Services

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

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.

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.

This validation process is not applicable for a Station Setup installation

Upgrading ToolsTalk 2

Please make sure that the ToolsTalk2 server is running before starting the upgrade.

When upgrading ToolsTalk 2 from 2.12 or earlier versions and Atlas Copco Data Communication (ACDC) is already installed, make sure that the controller port is pointing to the same port that ACDC was installed on. If you are installing ACDC for the first time and want to use another port than your current controller port in your ToolsTalk 2 version, then please change the controller port as described in the following procedure.

In the configuration files, controller port is named as HubPort.

• In ToolsTalk.Server.SelfHostService.exe.config(ClickOnce/Client/Server) or ToolsTalk.Standalone.exe.config(Station Setup), change the controller port to the correct port number <add key="HubPort" value="XXXX" />

   

Troubleshooting

• Troubleshooting During Installation

Troubleshooting During Installation

Restart the ToolsTalk Industrial Technique Host service after upgrading ToolsTalk 2.

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.

Configuration

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

Getting started

• Starting
• User Interface Start View
• Controllers
  • Adding Controllers
  • Managing the Controller List
• Saving Changes in Parameters and Configurations
• Managing the Workspace Windows
• User Interface - Workspace With Controller Overview

Starting

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

User Interface Start View

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

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.

At start the default icon selection is the Plant structure icon . This is indicated by changing the icon color to light blue. The workspace is divided into two parts:

• The structure workspace is used to organize controllers and to select an individual controller.

• The controller workspace shows all the controller icons and is used to view and set all parameters and configurations for one selected controller.

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.

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 different controller types are represented with an icon in the All Controllers list.

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.

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.

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

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:

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

Filtering and Sorting the Data Grid

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

User Interface - Workspace With Controller Overview

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

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.

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.

Tool box

The toolbox contains all valid products for the controller version.

Creating Hardware Layout

A new installation of a PF6 System does not have any hardware layout.

To create a hardware layout, always 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.

Drag FlexCarrier 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 and press Delete. The FlexCarrier containing the FlexController can only be deleted when it is the single remaining carrier.

Extracting a hardware layout configuration

If the Hardware Layout Configuration is empty, a current controller setup can be extracted by using the Extract button.

After extracting, push the changes to the controller in order to receive status and health. The hardware deployment status will change after validation.

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:

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

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.

Symbols

Symbols indicate status of each product. You can always point to each indicator to get a tooltip.

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

Working with the Tightening Program Tab

The list has the following columns:

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.

Tightening Program Menu

Each row in the list represents one multistep tightening program.

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.

Adding a Multistep Program

Copying and Pasting a Tightening Program

Existing tightening programs can be copied as a template and then pasted on another controller.

Copy and Paste are only possible if they are performed on the same controller, or different controllers running the same software version and controller type.

Importing a Multistep Program

Deleting a Multistep Program

Comparing Multistep Tightening Programs

In Tightening Programs, two different Multistep Programs can be compared.

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.

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.

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

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.

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

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:

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

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.

Tightening Steps

Tighten/Loosen to Angle (A)

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.

T – Tighten/Loosen to Torque

T – Tighten to Torque

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

T – Loosen to Torque

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.

T+A – Tighten to torque plus angle

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

DI – Run Until Digital Input

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.

Tighten to DynaTork (DT)

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.

Wait (W)

In this step the tool waits the specified amount of time. The tool does not rotate while waiting.

The step before the Wait step must have the setting Brake set to On, that is, the Wait step must start with the tool standing still.

Socket Release (SR)

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.

Tighten to torque or angle (T|A)

This step runs the tool with the speed n in the forward direction until the first of either torque target or angle target is reached. The torque and angle measurements start at the beginning of the step.

Rundown (RD)

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

Y - Tighten to Yield

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.

Tighten to yield, method 2 (YM2)

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.

TC – Torque Calibration

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

By setting this to either Main or Secondary it is possible to calibrate either one of the two transducers.

Engage (E)

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.

Thread Cutting to Torque (ThCT)

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 selftapping) 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.

Tighten to Torque and Angle (T&A)

The tool runs until with the specified speed in the forward direction until both target torque and target angle are reached. The target torque and the target angle must be set to > 0.

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.

Utilities

Connectors can be added to reuse a repair path or a terminate path.

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.

Step Monitors

The step monitors are used to verify that the tightening was made according to the specification, for example, angle limits or torque. The monitors are flexible and can be placed as needed in the multistep program.

For each step in the multistep tightening program it is possible to have up to four monitors.

A – Angle

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.

YA – Angle from Yield

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

MT – Mean Torque

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

PT – Peak Torque

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.

PTCA – Post Thread Cut Angle

Measures the angle achieved during the monitoring and checks that it is between the specified angle limits. 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. The parameter Stop Condition specifies where the angle measurement should end.

PTCPT – Post Thread Cut Peak Torque

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.

PVTH – Post View Torque High

This monitor checks that all torque values in the angle window are below the limit.

PVTL – Post View Torque Low

This monitor checks that all torque values in the angle window are above the limit.

PrT – Prevailing Torque

This monitor calculates the prevailing torque value in the angle window and checks that it is within the limits.

SOT – Shut Off Torque

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.

SOC – Shut Off Current

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 .

SSD - Stick Slip Detection

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.

Ti – Time

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.

TC – Torque Calibration

This monitor checks the maximum torque reached is within the torque limits.

TG – Torque Gradient

This monitor checks the gradient is within the limit.

TAW – Torque in Angle Window

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

TRD – Torque Rate and Deviation

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.

Step Restrictions

To make sure the tightening stops if something unexpected happens, it is possible to add restrictions to the multistep tightening program. For each restriction, select Repairable = Yes to allow retry when tightening stops. For each of the steps in a multistep program it is possible to have up to four restrictions.

CTh – Cross Thread

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 and the program jumps to the next synchronization point.

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 and the program jumps to the next synchronization point.

A – Maximum Angle

This restriction measures the angle. If the measured angle reaches the Maximum limit, the tool is stopped immediately and the program jumps to the next synchronization point. 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.

T – Maximum Torque

This restriction checks the torque. If the measured torque exceeds the Maximum limit, the tool is stopped immediately and the program jumps to the next synchronization point.

RH – Rehit

This restriction checks the torque. If the measured torque exceeds the Torque Limit, the tool is stopped immediately and the program jumps to the next synchronization point, or the end of the program.

RT – Rescinding Torque

This restriction checks the torque. If the measured torque is lower than the limit Torque low limit, the tool is stopped immediately and the program jumps to the next synchronization point, or the end of the program.

TG – Torque Gradient

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

TAW – Torque in Angle Window

This restriction checks that the measured torque in the angle window is within its limits. If the measured torque is outside the limits the tool is stopped immediately and the program jumps to the next synchronization point, or the end of the program.

TCD - Torque vs Current Deviation

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.

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 from which they will read the values. 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:

• FA – Final Angle

• FC – Final Current

• FT – Final Torque

• PT – Prevailing Torque

• RA – Rundown Angle

• ST – Self-tap Torque

General Parameters

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.

Multistep Tightening Program Properties

Program Restrictions

Program Monitor

Validation

Attachment Tuning

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.

Working with the Sync Mode Tab

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)

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:

Adding a Sync Mode

Deleting a Sync Mode

Handling Tightening Sync Mode Configuration

• Double-click on a tightening Sync Mode to configure that Sync Mode.

Properties