B&R Automation

Overview

SDA supports Automated Backups for following B&R applications:

• Automation Studio 3.0.90

• Automation Studio 4.12

If there is a missing B&R Automation version, please feel free to get in touch with us. We will provide you with the requested version as soon as possible.

Requirements

In order to make a B&R Automation project backup, the project must be archived including the binaries.

Preparing the backup

When linking a project to the device, the right hardware configuration needs to be selected, which is related to the selected device.

The backup service performs validation exclusively on the binary files specified in the configuration settings.

When setting up a backup pipeline for B&R PLCs, users have the flexibility to selectively include or exclude specific B&R modules from the validation process. This functionality is particularly useful in scenarios where modules are dynamically generated on the target system through the Automation Runtime application.

Configuration Notes:

• By default, all modules with *$* naming patterns and .asproject modules are automatically excluded from validation

• Beyond the standard BR module checks, the system also validates the sysconf module by comparing it against recent modifications in the Physical folder of the associated hardware configuration

Performed Backup Checks

Following checks are performed when doing a project backup on a B&R Automation device. Those checks are done using the B&R Runtime Utility Center.

The following checks are only performed for the linked hardware configuration

1. Project Module Consistency

The system compares all .br modules in the project's binary folder against their corresponding source files. An inconsistency is flagged when a source file has been modified more recently than its associated .br module's creation timestamp.

2. Target-Project Module Synchronization

All .br modules that match the configured filter criteria (include/exclude settings) undergo validation against the target device modules. The system identifies inconsistencies in the following scenarios:

• Modules present on the target device but missing from the project

• Modules present in the project but missing from the target device

• Modules on the target are different then modules in the project (consistency check)

3. System Configuration Consistency

For system configuration validation (sysconf.br), the service performs a dual-layer check:

• Temporal consistency: Verifies that no changes have been made to the hardware configuration's Physical folder after the project's sysconf.br module was generated

• Target synchronization: Ensures the target device's sysconf module matches the local project's sysconf configuration

Result

If there are inconsistencies between the project and the target device, this is shown in the logs of the backup job.