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
F	Alture
G	Web API

Installation and Upgrade

• Installation Requirements
  • 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 Requirements

• 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, Power Focus 8, SYS6000, Unity, FDF.

• Non- Atlas Copco vendors through ToolsNet Open Protocol.

System Requirements

Atlas Copco Data Communication Software Requirements

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

• .NET 10.0.7 runtime, .NET Desktop 10.0.7 runtime and ASP.NET Core 10.0.7 runtime. Note: ASP.NET Core 10.0.7 requires both 32 and 64 bit installations.

• 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 must run on Windows Server 2022 or later.

HTTPS is disabled by default. If HTTPS is selected without a valid certificate, ACDC WebAPI and ACDC DataCommunication services will fail to start.

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

• Microsoft SQL Server 2019 or later

Ensure that SQL Server Agent is activated before installation. Activate the 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 installation requirements with PowerMacs, see the PowerMacs 4000 User Guide.

To enable JoiningProcess for Pmacs Programs, install and run PowerMacsProgramService.

Install the correct ToolsNet Program Manager on the server. Make sure the ToolsNet Program Manager version matches or is higher than the PM4000 ToolsTalk version used to create the program.

Before Installation

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

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

• Ensure that the firewall is configured to allow communication through the required 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 configured, 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

Uninstall any previous version of Atlas Copco Data Communication before upgrading to version 3.7.x or above.

In order to use Atlas Copco Data Communication Unify Service, a valid Atlas Copco Data Communication 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.

When using Atlas Copco Data Communication version 3.7.x or above, upgrading from RabbitMQ v3.11.x to RabbitMQ v4.x.x, specific upgrade steps must be followed. Read RabbitMQ v4.2.4 - Upgrade from ACDC 3.7.x for more information.

RabbitMQ

When upgrading Atlas Copco Data Communication from a version earlier than 3.5.0, configure the following RabbitMQ prerequisites before you upgrade. These steps are not required if you are migrating to RabbitMQ 4.x.x.

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
• Working with AppSettings
  • TTL (Time To Live) for ACDC-Gateway messages
• 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-premise database, Unify service 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 TNDCP with TLS 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 TNDCP with TLS 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.

Protocol Server Store

Settings	Description
General Settings	Port The port used by the Protocol Server Store. Hostname The host where the Protocol Server Store is installed.
Log Settings	Level Indicates the level of detail in the information to be stored in the log. The available options are: Verbose Debug Information Warning Error Location The file path where the logs are stored.
Database settings	Database Provider: The database provider for storing controller data. The available options are: Microsoft SQL Server Recommended for installation as an on-premise database. Data Source The IP address of the SQL Server. Initial Catalog The name of the SQL Server database. Trust server certificate Select the checkbox to trust the SQL server's self-signed certificate. By default this checkbox is cleared. Note: The checkbox is always cleared, even when backup settings are restored. If this checkbox is: Cleared (default): Microsoft SQL Server must use a trusted certificate. Selected: SQL Server’s self-signed certificate is trusted automatically. Not recommended for security reasons. Authentication Type SQL Server Enter and confirm the password for authentication. Windows Authentication Enter the Domain User where the service will run. Note: To run Atlas Copco Data Communication using Windows Authentication, manually configure the selected Domain User as the Log On user for the Windows service. When using SQL Server for the Protocol Server Store database with Windows Authentication, set the service Log on account to the domain user before installing and migrating the Protocol Server Store database.   SQLite Recommended for any other type of installation. Location The path to where the SQLite database is stored. After updating any database authorization configuration, run the installation scripts to apply the changes. If the scripts are not run, Atlas Copco Data Communication will not be able to connect to the database.

External 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. By default, this field is empty which means RabbitMQ publishing is turned off. Specify a value to turn on 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. Default value: ACDC-TT2 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.
ToolsNet RabbitMQ	Enable publishing of messages to ToolsNet via RabbitMQ. 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. By default, this field is empty which means RabbitMQ publishing is turned off. Specify a value to turn on RabbitMQ publishing. Port The port that Atlas Copco Data Communication uses when connecting to the RabbitMQ broker. Default value: 5672. 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 ToolsNet configuration. Default value: ACDC-ToolsNet. Username The username that Atlas Copco Data Communication uses when connecting to the RabbitMQ broker. Password The password that Atlas Copco Data Communication uses when connecting to the RabbitMQ broker.

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 stores the data in a local database.

After updating any database authorization configuration, run the installation scripts to apply the changes. If the scripts are not run, Atlas Copco Data Communication will not be able to connect to the database.

Alture

Enables settings for Atlas Copco cloud.

Verify that the Atlas Copco Data Communication application server supports the minimum TLS version required by the Alture installation. It is recommended to use TLS 1.2 or higher.

Unify

Settings to configure Unify.

After updating any database authorization configuration, run the installation scripts to apply the changes. If the scripts are not run, Atlas Copco Data Communication will not be able to connect to the database.

In Unify 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. The broker must support MQTT v5 and QoS level 2 (Exactly Once). For more information on how to install an MQTT broker, see MQTT Overview. 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. Click VERIFY CONNECTION to update the Verification Status.
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). Click VERIFY CONNECTION to update the Verification Status.
Unify V1	The Unify version(s) of the messages that should be published. Applies to both MQTT and RabbitMQ publishing. Currently only Unify V1 is supported. Selected only when Unify is enabled and either MQTT or RabbitMQ is chosen. The available models are: Tools Controller Result with Trace Events Joining Processes

Remote Logging

Security Settings

Database Installation Tab

The Database Installation tab configures the settings for the On Premise, Protocol Server Store and CDM database installations.

After updating any database authorization configuration, run the installation scripts to apply the changes. If the scripts are not run, Atlas Copco Data Communication will not be able to connect to the database.

On Premise

Protocol Server Store

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

Ensure that the user has permission to create a database, users, and database jobs.

The user account entered in this step is only used for the installation. The installer creates new users with limited access only to the Atlas Copco Data Communication database and the Atlas Copco Data Communication related database jobs.

CDM

The Database settings for CDM are enabled (and required), if both On-premise and Unify are enabled.

There are currently no extra features available for CDM.

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

Default Values

• Days to Keep = 90

• Bulk Size = 10000

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

Working with AppSettings

AppSettings contain various application settings that are not visible in the Installation Configurator interface. If a user wants to configure these settings, they should open the appSettings.config file and manually update the desired values.

Users must ensure they fully understand the values they are modifying and the potential impact of those changes. If they are unsure, it is recommended to consult an Atlas Copco Service Technician before making any updates.

The default location of the appSettings.config file is: C:\Program Files (x86)\Atlas Copco\ACDataCommunication

After making changes to the file and saving it, the AtlasCopco_DataCommunication service must be restarted for the new settings to take effect.

TTL (Time To Live) for ACDC-Gateway messages

Configure TTL (Time To Live) for ACDC-Gateway messages using two new settings in the appSettings.config file. These settings determine how long messages stay in the queue before they are automatically discarded.

MQTT Message TTL

• Setting name: MqttMessageExpirationTimeInHours

• Description: Specifies the TTL (in hours) for messages sent via MQTT. After this time, messages will be discarded from topic.

• Default value: 24 hours

• How to disable TTL: Leave the value empty to disable TTL for MQTT messages

This setting is only applicable when using MQTT Client v5

RabbitMQ Message TTL

• Setting name: PublishingRabbitMqMessageExpirationTimeInHours

• Description: Specifies the TTL (in hours) for messages sent via RabbitMQ. After this, the messages will be removed from the queue.

• Default value: 24 hours

• How to disable TTL: Leave the value empty to disable TTL for RabbitMQ messages

Index Reorganize and Index Rebuild

Index reorganize and Index rebuild are set up as jobs in the SQL Server Agent. There are separate jobs for the ACDC database and the ACDC CDM database. 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.

• MinPageCount: This sets the job only to reorganize indexes with a page size equal to this limit or above.

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.

• MinPageCount: This sets the job only to reorganize indexes with a page size equal to this limit or above.

Troubleshooting and Service

• Troubleshooting During Installation

Troubleshooting During Installation

Reference

• RabbitMQ Overview
  • RabbitMQ Prerequisites
    • RabbitMQ v4.2.4 - Upgrade from ACDC 3.7.x
  • RabbitMQ Setup
• MQTT Overview
• Useful Information
• Cybersecurity Recommendations

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.

When using Atlas Copco Data Communication version 3.7.x or above, specific steps must be followed when upgrading from RabbitMQ v3.11.x to RabbitMQ v4.x.x. Read RabbitMQ v4.2.4 - Upgrade from ACDC 3.7.x for more information.

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. For more information, read Upgrade Prerequisites.

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

When using Atlas Copco Data Communication version 3.7.x or above, specific steps must be followed when upgrading from RabbitMQ v3.11.x to RabbitMQ v4.x.x. Read RabbitMQ v4.2.4 - Upgrade from ACDC 3.7.x for more information.

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.

Additional information

• Delete all queues on ACDC Internal

  RabbitMQ's topology has been updated to version 3.6. To ensure proper configuration and avoid unexpected behavior, all queues in the ACDC internal vhost must be deleted before setting up the new topology.

• Exclude RabbitMQ folders from Antimalware (Recommendation)

  To prevent RabbitMQ queues from entering a “Down” state—which can disrupt a significant portion of the system—it is recommended to exclude all RabbitMQ folders from antimalware scanning.

• Upgrade to secure erlang version (SSH) (Recommendation)

  By default, RabbitMQ does not enable Erlang’s SSH module. However, administrators and operators can manually enable it, which may introduce potential security vulnerabilities.

RabbitMQ v4.2.4 - Upgrade from ACDC 3.7.x

Use this procedure when upgrading RabbitMQ from version 3.11.x to version 4.2.x for Atlas Copco Data Communication 3.7.x or above.

Requirements

• Erlang 26.2 or later (supported up to 27.x).

• Minimum 200 GB free disk space on the application server.

• Disk write speed of at least 200 MB/s.

• Windows Server 2022 or later.

Prerequisites

• Stop Atlas Copco Data Communication.

• Empty all queues on ACDC Internal.

• Verify no Atlas Copco Data Communication processes are running before starting the upgrade.

Important information and verification

• Ensure the AtlasCopco_ACDC_ProtocolStore database state is preserved during the RabbitMQ upgrade. Changing the database type or deleting the database catalog/file will reset its state and may trigger reprocessing of a large number of controller messages.

• Make sure Erlang and RabbitMQ versions are compatible before starting Atlas Copco Data Communication.

• After installation, verify RabbitMQ service status and that all required ports and users are configured per the Atlas Copco Data Communication User Guide.

• Restart Atlas Copco Data Communication only after RabbitMQ is running and verified.

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.

MQTT Overview

An installation of MQTT broker is necessary to publish messages from the Atlas Copco Data Communication. In the following setup, the MQTT broker used is Eclipse Mosquitto but any broker that supports MQTT v5 and QoS level 2 (Exactly Once) can be used.

Setting Up the Mosquitto MQTT Broker

Follow these steps to install and configure the Mosquitto MQTT Broker with support for MQTT v5.

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.

Cybersecurity Recommendations

Do not expose ACDC endpoints or services to the public internet.

If the Atlas Copco Data Communication server is decommissioned, the application owner must make sure all associated application data, configurations, and sensitive information stored on the server are securely deleted in accordance with the organization’s data‑handling and security policies.