Introduction

• General Description
• General Data Protection Regulation (GDPR)
• Revision History
• Conventions
• System Overview

General Description

Atlas Copco Data Communication is a data communication service for collecting and storing data from controllers and devices.

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

Conventions

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

System Overview

A	Tools/Controllers
B	Producer/Interpreter
C	Consumer
D	Database
E	Unify (3rd party software)
F	MQTT
G	Alture
H	Web API

Installation and Upgrade

• Installation Restrictions
  • Supported Platforms
  • System Requirements
  • Before Installation
  • Default Installation Path
• Installing Atlas Copco Data Communication
  • Default Databases
• Starting Atlas Copco Data Communication Services
• Upgrade Prerequisites

Installation Restrictions

• Supported Platforms
• System Requirements
• Before Installation
• Default Installation Path

Supported Platforms

Depending on the version of the system and the license used, data collection can be gathered from the following systems:

• Power Focus 3000, Power Focus 4000, PowerMacs 3000, PowerMacs 4000, Power Focus 6000, MT Focus 6000, PF8, SYS6000, Unity.

• Non- Atlas Copco vendors through ToolsNet Open Protocol and ToolsNet Data Collection Protocol.

System Requirements

Atlas Copco Data Communication Software Requirements

• RabbitMQ, see Configuring the Settings Tab, RabbitMQ Overview.

• .NET 8.0 runtime, .NET Desktop 8.0 runtime and ASP.NET Core 8.0 runtime

• When HTTPS is enabled for the ACDC Web API or when TLS is enabled for Power Focus 6000, a valid certificate needs to be installed on the application server and configured to be used in Installation Configurator. See Configuring the Settings Tab.

To use TLS 1.3, Atlas Copco Data Communication WebAPI Services must run on Windows Server 2022 or later.

Https is enabled by default for new installations. Without a valid certificate ACDC WebAPI and ACDC DataCommunication services will fail to start.

One of the certificate's purposes must be Server Authentication.

Atlas Copco Data Communication Server Software Requirements

• Windows server, see release notes for verified versions.

For help with installation of this software, see the official web pages of the respective software providers.

Database Server Software Requirements

• SQL server

Ensure that SQL Server Agent is activated before installation. Activate SQL Server Agent in Windows services.

For help with installation of the Database Server software, see the official web pages of the respective software providers.

PowerMACS Installation Requirements

For installing requirements with PowerMacs, see the PowerMacs 4000 User Guide.

Before Installation

The following preparations have to be made prior to installation of Atlas Copco Data Communication:

• Ensure that the computer(s) that are to run Atlas Copco Data Communication satisfy the hardware and software requirements.

• Ensure that the system firewall is OFF, or open the ports.

• Install RabbitMQ and make sure that the setup corresponds to the Atlas Copco Data Communication configuration. Refer to RabbitMQ Prerequisites in RabbitMQ Overview.

Ensure that the database server is installed, properly setup, and running.

Hard Disks and Data Files

Contact the database administrator to decide the following settings:

The SQL server transaction log file grows when delete maintenance is running. This log file is truncated when the database is backed up. The database administrator must have a strategy for keeping a reasonable log file size.

Default Installation Path

For a default installation of Atlas Copco Data Communication, the file paths of files can be found in the tables below.

Installing Atlas Copco Data Communication

The DataCommunication Installation Configurator helps configure the necessary settings before starting the Atlas Copco Data Communication service.

Default Databases

The installation package will create the databases, add table spaces, and add required users, depending on the database types used.

ProtocolServerStore service can use either SQL Server or SQLite.

Starting Atlas Copco Data Communication Services

The Atlas Copco Data Communication services needs to be started manually. This is done through Windows Services.

Upgrade Prerequisites

In order to use the external WebAPIs or external publishing, a valid Atlas Copco Data Communication WebAPI Services Unify license must be applied.

RabbitMQ must be configured to use version 2 (v2) of the queues before starting the Atlas Copco Data Communication service.

When upgrading or installing the latest , make sure RabbitMQ prerequisites are set before starting. If these were already set in the previous version, you can skip the steps below.

RabbitMQ

When upgrading Atlas Copco Data Communication from a version lower than 3.5.0, the following prerequisites must be configured in RabbitMQ.

1. Ensure all non-meta data queues on the ACDC-Internal virtual host are empty.

2. Stop the RabbitMQ service and navigate to the RabbitMQ folder. The default path is C:\Users\{username}\AppData\Roaming\RabbitMQ. Adjust the path if you have a custom installation.

3. Locate or create the configuration file for RabbitMQ: rabbitmq.conf.

4. Add the following configuration setting to the file.

   # Set the default version for classic queues

   classic_queue.default_version = 2

   # Use '2' for classic queues (v2)

5. Restart the RabbitMQ service.

6. Apply a policy to the ACDC-InternalServices virtual host to ensure its queues run exclusively on version 1 (v1):

   1. Open the Admin tab in RabbitMQ.

   2. Select Policies.

   3. Add or update a policy using the following settings:

      • Virtual host: ACDC-InternalServices

      • Name: v1policy

      • Apply to: Queues

      • Definition: queue-version = 1

7. Delete all queues for the controllers on the ACDC-Internal virtual host before starting the Atlas Copco Data Communication service.

Configuration

• Working with the DataCommunication Installation Configurator
  • Configuring the Settings Tab
  • Database Installation Tab
• Working with the Database
• Working with Delete Maintenance
• Working with Delete Unbound Graphs
• Working with the Log Level
• Facts and Dimensions for Results
• Index Reorganize and Index Rebuild

Working with the DataCommunication Installation Configurator

It is possible to manually start the DataCommunication Installation Configurator. The application is located in a directory relative to the selected installation location <installation path>\Atlas Copco\ACDCInstallationConfigurator.

The default location is C:\Program Files (x86)\Atlas Copco\ACDCInstallationConfigurator.

Open the application by selecting AtlasCopco.InstallationConfigurator.DataCommunication.exe.

Configuring the Settings Tab

The Settings tab configures the Atlas Copco Data Communication Service, the Atlas Copco Data Communication WebAPI Services, the Protocol Server Store database, the on-premises database, and the Atlas Copco cloud.

ACDC

Enables settings for the Atlas Copco Data Communication Service.

Protocol Servers

Settings	Description
Protocol Server Ports	The ports used by the specific protocol listeners. The available options are: Px2 Px2 with TLS Power Focus 4000 PIM Power Focus 4000 PowerMACS PIM PowerMACS TNOP PIM TNOP TNDCP Enabling TLS for any protocol requires a certificate to be provided in Security Settings. To use TLS 1.3, Atlas Copco Data Communication WebAPI Services must run on Windows Server 2022 or later.
Enable Protocol Servers	Enable/disable listeners for specific protocols. The available options are: Px2 Px2 with TLS Power Focus 4000 PowerMACS TNOP TNDCP Open Protocol SYS6000 Enabling TLS for any protocol requires a certificate to be provided in Security Settings. To use TLS 1.3, Atlas Copco Data Communication WebAPI Services must run on Windows Server 2022 or later.

ToolsTalk 2 RabbitMQ

Settings

Description

ToolsTalk 2 RabbitMQ

Enable publishing of messages to ToolsTalk 2 (from release v2.17) via RabbitMQ. RabbitMQ must be installed before you can continue with the settings. For more information how to install RabbitMQ, see RabbitMQ Overview. Exchange Name The name of the RabbitMQ exchange that Atlas Copco Data Communication communicates with. Hostname The hostname of the RabbitMQ broker. The host where RabbitMQ broker is installed. The setting turns on or off the RabbitMQ publishing feature. The default value is blank, which means that RabbitMQ publishing is turned off. An entered value turns on the RabbitMQ publishing. Port The port that Atlas Copco Data Communication uses when connecting to the RabbitMQ broker. Virtual Host The virtual host name that Atlas Copco Data Communication uses when connecting to the RabbitMQ. It is required to be / if it is not possible to change within ToolsTalk 2 configuration. Username The username Atlas Copco Data Communication is using when connecting to the RabbitMQ broker. Password The password Atlas Copco Data Communication is using when connecting to the RabbitMQ broker. If Atlas Copco Data Communication has already been installed, restart the AtlasCopco_DataCommunication service to activate the settings.

Web API

Enables settings for the Atlas Copco Data Communication WebAPI Services to collect data over a web API with an option to host using HTTPS.

On Premise

Enables the settings for the on-premise database. The Service will store the data in a local database.

Alture

Verify that the ACDC application server supports the minimum TLS version required by the Alture installation. The recommendation is to use TLS 1.2 or higher.

Unify

In Publishing Settings, the settings for MQTT and RabbitMQ can be configured. The settings define messages to be published to MQTT or RabbitMQ or both. The prerequisite for this is to set Topics in MQTT and Routing keys in RabbitMQ before configuring and starting the Atlas Copco Data Communication service.

Publishing Settings

Settings	Description
MQTT Settings	MQTT broker must be installed before you can continue with the settings. MQTT Topics are used in the MQTT ecosystem for the broker to determine which clients receive specific messages. Enable Publish To MQTT Select this checkbox to publish data to an MQTT broker. By default, this checkbox is disabled. When enabled, more settings are available: Broker URL The host where the MQTT broker is installed. A URL must be entered to be able to publish messages to MQTT broker. Username Enter the username for MQTT broker authentication. Leave this field blank, if you use the MQTT broker without authentication configured. Password The password for the broker. Leave this field blank, if you use the MQTT broker without authentication configured.
RabbitMQ Settings	RabbitMQ must be installed before you can continue with the settings. For more information how to install RabbitMQ, see RabbitMQ Overview. In RabbitMQ, exchanges are used as routing mediators that decide what messages are sent to a queue, multiple queues or discarded. Queues deliver messages to consumers using a FIFO model. Bindings are used by exchanges to route messages to specific queues. Routing keys in RabbitMQ are attached to exchanges to filter specific messages and route them to the bounded queues. Enable RabbitMQ Publishing: Toggles the RabbitMQ publishing settings to be visible. When enabled, the following setting are available: Exchange Name: The name of the RabbitMQ exchange to use. Hostname: The host where RabbitMQ is installed. (This value must be set if the Enable RabbitMQ Publishing checkbox is checked) Username: The username Atlas Copco Data Communication is using when connecting to the RabbitMQ broker. Password: The password Atlas Copco Data Communication is using when connecting to the RabbitMQ broker. Virtual Host: The name of the RabbitMQ virtual host. Port: The port Atlas Copco Data Communication is using when connecting to the RabbitMQ broker. Publish Ack Timeout: Time allowed for message acknowledgment (in seconds).
CDM Settings	The CDM version(s) of the messages that should be published. Applies to both MQTT and RabbitMQ publishing. The latest CDM version is selected by default. It is possible to select more than one version. Latest version for all models: A checkbox that will select the latest version for each entity, excluding the depricated models. Clearing the checkbox will deselect the latest version of the models. It is recommended to keep the other versions selected if they are already selected. The available models are: Results Tools Joining Processes Tightening System Assets Trace All models have a multi-select drop-down list. Select the versions that should be published. When selecting multiple versions, each version will be published on the topics. Deprecated models: ACDC can publish models from earlier CDM versions that are in a draft state or not recommended to use. The available options are: Deprecated Results Deprecated Programs Deprecated Events Deprecated Traces

Remote Logging

Security Settings

Database Installation Tab

The Database Installation tab sets the installation settings for the on-premises database and the Protocol Server Store database.

On Premise

Protocol Server Store

Settings

The view and options in Settings depends on the selected Database Provider for Protocol Server Store in the Settings tab:

Working with the Database

In order to keep the Atlas Copco Data Communication database up and running with good performance and reliability, the following maintenance activities are recommended:

• Make regular backups of the database to secure the data in case of hardware failure and to keep the transaction log from growing in size.

• Rebuild and reorganize the indexes in the database regularly, to keep the transactions and searches fast and optimized.

• Delete old results that are no longer needed. This reduces the required disk space and improves report creation speed. After a Delete maintenance job it is also recommended to reorganize the indexes.

• To run the maintenance job, setup and start the job scheduler manager for required database type.

A	AtlasCopcoDataCommunication Service	B	AtlasCopcoDataCommunication_WebAPI service
C	AtlasCopcoDataCommunication_ProtocolServerStore Service	D	AtlasCopcoDataCommunication_PowerMacsProgramManager service
E	AtlasCopcoDataCommunication Database	F	PSS Database

Working with Delete Maintenance

Default Values

• Days to Keep = 9999

• Bulk Size = 5000

• Delete Manual Tool = 0

• Delete Program by Last Used Date = 0

• MinResultsPerUnitAndProgram = 0

Editing and Scheduling Jobs

Configuring Job Steps Properties

@Bulksize and @DaysToKeep: those properties define how long data should be stored and how large should be the chunks to be deleted. Each "delete operation" deletes data in batches, and each batch deletes a number of rows. The maximum number of rows that can be deleted, which is equal to @Bulksize. This operation is repeated until all data longer than @DaysToKeep are deleted.

@DeleteManualTool: this property selects if the manual tools are to be deleted or not.

@DeleteProgramByLastUsedDate: this property selects how programs are to be deleted when running the maintenance job for program and unit.

@MinResultsPerUnitAndProgram: this property determines whether there is a minimum required number of results to keep for each Unit and Program combination regardless of @DaysToKeep. Applies to SQL Server installations only.

Working with Delete Unbound Graphs

Working with the Log Level

If no custom log level is set, the default log level will be set by the configuration file.

If the Atlas Copco Data Communication service is restarted then all the current log filters will be removed, leaving only the global filter that was set up by the configuration file.

The log level can be changed while Atlas Copco Data Communication is running, by using the Atlas Copco Data Communication Web API.

The following log level system calls are available:

• Endpoint list of all the active log filters

  GET http://127.0.0.1:7110/DataCommunication/v1/logging

• Assign a new log level to a specific controller

  POST http://127.0.0.1:7110/DataCommunication/v1/logging/{logId}/level/{logLevel}

• Change the global log level for Atlas Copco Data Communication

  PUT http://127.0.0.1:7110/DataCommunication/v1/logging/global/level/{logLevel}

• Change the existing log level filter for a controller

  PUT http://127.0.0.1:7110/DataCommunication/v1/logging/{logId}/level/{logLevel}

• Reset the log level for the controller. This will revert to use the global log level

  DELETE http://127.0.0.1:7110/DataCommunication/v1/logging/{logId}

Communication of Log Id and Internet Protocol Address

The IP address can be found on the interface of the controller or in the log file, when it connects to Atlas Copco Data Communication.

Px2 uses a port number which is created when connecting to Atlas Copco Data Communication. You will find the port number in the log file and not in the controller.

Examples of System Calls

• Create a filter of the log level for PowerFocus 4000

  POST http://127.0.0.1:7110/DataCommunication/v1/logging/127.0.0.1/level/verbose

• Create a filter of the log level for Px2

  POST http://127.0.0.1:7110/DataCommunication/v1/logging/127.0.0.1:53069/level/verbose

Facts and Dimensions for Results

The database table FactsForResult is a source of information about result statistics. The job ACDC_FactsAndDimensionsForResult is responsible for the management of that information.

Atlas Copco Data Communication requires the job ACDC_FactsAndDimensionsForResult to be enabled. It is enabled and scheduled by default. All ACDC_FactsAndDimensionsForResult needs in order to run, is that the Server Agent is running.

Index Reorganize and Index Rebuild

Index reorganize and Index rebuild are set up as jobs in the SQL Server Agent. The reorganize job should be run once a day on a database. In a transaction heavy system, the rebuild job should be run once a week. The user can modify the job schedule for both jobs and also specify how long a job is allowed to execute in a single run. Both jobs will always run reorganize/rebuild in a specific order, starting with the heaviest fragmented index first.

For the Index Rebuild job, the user can specify:

• RebuildPercentageLimit: This sets the job to only rebuild indexes defraged with a percentage of this limit or above.

• RebuildStopTime: This sets the stop time for the index rebuild job relative to the scheduled start time. This specifies the maximum time the job is allowed to execute. The job will not stop at this time, it will finish up the current index rebuild but no additional indexes will be processed after. Example: The job is scheduled to start at 23:00 and should not run any longer than three hours, then the RebuildStopTime should be set to 02:00.

For the Index Reorganize job, the user can specify:

• LowerReorganizePercentageLimit: This sets job to only reorganize indexes defraged with a percentage of this limit or above

• UpperReorganizePercentageLimit: This sets the job to only reorganize indexes defraged with a percentage of this limit or lower.

• ReorganizeStopTime: This sets the stop time for the index reorganize job relative to the scheduled start time. This specifies the maximum time the job is allowed to execute. The job will not stop at this time, it will finish up the current index reorganization but no additional indexes will be processed after. Example: The job is scheduled to start at 20:00 and should not run any longer than two hours, then the ReorganizeStopTime should be set to 22:00.

Troubleshooting and Service

• Troubleshooting During Installation

Troubleshooting During Installation

Reference

• RabbitMQ Overview
  • RabbitMQ Prerequisites
  • RabbitMQ Setup
• Useful Information

RabbitMQ Overview

An installation of RabbitMQ is needed to publish messages from Atlas Copco Data Communication to ToolsTalk 2 (from version 2.17).

After installing RabbitMQ, ensure that the prerequisites are met before starting the Atlas Copco Data Communication service. Refer to RabbitMQ Prerequisites.

For a general overview of the RabbitMQ installation, visit https://www.rabbitmq.com/install-windows.html.

Before the configuration of RabbitMQ make sure that the Atlas Copco Data Communication has been configured correctly.

If you need to install Atlas Copco Data Communication, see Installing Atlas Copco Data Communication.

If Atlas Copco Data Communication 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.

RabbitMQ Prerequisites

When upgrading or installing the latest version of Atlas Copco Data Communication, make sure RabbitMQ prerequisites are set before starting. If these were already set in the previous version, you can skip the steps below.

Ensure that the Atlas Copco Data Communication service is stopped before configuring RabbitMQ to use version 2 (v2) of the queues.

1. Ensure all non-meta data queues on the ACDC-Internal virtual host are empty.

2. Stop the RabbitMQ service and navigate to the RabbitMQ folder. The default path is C:\Users\{username}\AppData\Roaming\RabbitMQ. Adjust the path if you have a custom installation.

3. Locate or create the configuration file for RabbitMQ: rabbitmq.conf.

4. Add the following configuration setting to the file.

   # Set the default version for classic queues

   classic_queue.default_version = 2

   # Use '2' for classic queues (v2)

5. Restart the RabbitMQ service.

6. Apply a policy to the ACDC-InternalServices virtual host to ensure its queues run exclusively on version 1 (v1):

   1. Open the Admin tab in RabbitMQ.

   2. Select Policies.

   3. Add or update a policy using the following settings:

      • Virtual host: ACDC-InternalServices

      • Name: v1policy

      • Apply to: Queues

      • Definition: queue-version = 1

7. Delete all queues for the controllers on the ACDC-Internal virtual host before starting the Atlas Copco Data Communication service.

RabbitMQ Setup

The following covers the basic setup of RabbitMQ in order to function with ACDC. Any further advanced scenarios or options are not covered in this guide.

• A virtual host for ACDC internal queuing should exist (default name: "ACDC-Internal").

• A virtual host for ACDC internal services should exist (default name: "ACDC-InternalServices").

• A full access user account must exist for these virtual hosts.

If ToolsTalk 2 is to be used together with ACDC, then the following setup should exist in the RabbitMQ-installation:

• A virtual host for ToolsTalk 2 should exist (default name "ACDC-TT2").

• An exchange of type topic, bound to the virtual host should exist (default name "AtlasCopco_ACDC_ToolsTalk_Exchange").

• A full access user account must exist for this virtual host.

If ACDC Unify is to be used then the following setup should exist in the RabbitMQ-installation:

• A virtual host for RabbitMQ publishing should exist (default name: "ACDC-Publishing").

• An exchange of type topic, bound to the virtual host should exist (default name "amq.topic").

• Queues should be created and bound to the exchange.

• A full access user account must exist for this virtual host.

Useful Information

ProtocolServerStartupDelayInSecs is a new optional configuration property that is recommended to be used only in installations that include more than 150 controllers.

By default, this property is disabled and all protocols start simultaneously. When configured, ProtocolServerStartupDelayInSecs introduces a delay between the startup of different protocol types. The recommendation is to set a delay of 5 minutes (300 seconds), though the optimal value may vary depending on the mix of controllers in the system.

Enabling this setting triggers a staggered startup process. As a result, it may take up to 30 minutes for the service to begin reading from all controllers.

To ensure system stability, particularly in large deployments with numerous units and high-frequency data collection, it is strongly recommend to set this delay. It helps prevent potential overload of RabbitMQ during the startup phase.