B&R License Management When the OEM is Gone

A practical reference for automation engineers maintaining B&R CP1584 PLCs inherited from defunct OEMs with zero documentation.

1. Overview

The Licensing Challenge

When you inherit a B&R machine from a defunct or unreachable OEM, you face a unique licensing problem. B&R Automation’s licensing model is built around a system called Technology Guarding (TG), which ties software and runtime licenses to physical hardware containers (USB dongles) or software containers. Unlike Siemens TIA Portal licenses that can sometimes be recovered through factory support portals, B&R licenses are tightly coupled to the original purchasing entity’s account and the physical dongle they shipped on.

The core problems you face:

1. No B&R portal access – the OEM owned the account; you cannot log in to manage licenses.
2. Dongle custody – the TG USB dongle may be missing, damaged, or stuck with expiring licenses.
3. Unknown license inventory – you do not know which licenses (AS, AR, mapp components) were purchased.
4. Perpetual vs. time-limited confusion – mixing AS (annual) and AR (perpetual) licenses on one dongle creates transfer deadlocks.
5. No documentation – no license keys, no purchase records, no activation records.

What Licenses Are Typically Needed

Technology Guarding Ecosystem Overview

                          B&R License Server
                         (license.br-automation.com)
                                    |
                          TLS 1.2 / HTTPS
                                    |
            +-----------------------+-----------------------+
            |                                               |
     Technology Guarding                          CodeMeter Runtime
     Desktop Application                     Service (Windows Service)
            |                                               |
     License Management UI             Container Detection & Decryption
     (Activate / Deactivate)                    |
            |                                   +--------+--------+
            +-------+-------+-------+                  |        |
                    |       |       |          USB Dongle   Software
                Dongle   X20CMR  Software   (0TG1000.02)  Container
              (USB)    Modules  Container                  (VM-bound)

2. Technology Guarding Architecture

CodeMeter by Wibu-Systems

Technology Guarding is B&R’s branding of the Wibu-Systems CodeMeter digital rights management (DRM) platform. CodeMeter is a widely-used licensing framework in industrial automation (also used by Lenze, Bosch Rexroth, and others). Understanding this helps because:

• The CodeMeter Runtime Service is a Windows service that must be running for AS to function.
• The CodeMeter Control Center (separate from TG) can inspect dongles and software containers.
• Error codes beginning with WB (e.g., WB47, WB67) originate from CodeMeter, not B&R’s TG layer.
• Firmware updates to the dongle are actually CodeMeter firmware operations.

License Container Types

USB Dongle (0TG1000.02)

• The primary license container shipped by B&R.
• Can hold multiple licenses (AS + AR + multiple mapp components).
• Plugs into PC for AS licensing, or into PLC for AR licensing.
• Portable between machines (by design).
• Fragile: physical damage or firmware corruption renders all licenses on it inaccessible.

Software Container

• A license bound to a specific PC’s hardware fingerprint.
• Created during “Activate on this PC” operations in TG.
• Critically: invalidated by any hardware change – VM migration, snapshot revert, hardware upgrade, motherboard replacement.
• NOT recommended for production environments.
• Suitable only for development PCs that never change hardware.

X20CMR Modules

• Select X20 system modules have a built-in Technology Guard element.
• Allows AR license activation directly on the PLC hardware (no dongle needed for AR).
• The module’s TG element is treated as a license container, similar to a dongle.
• Useful for machines where the PLC itself should hold the runtime license permanently.

License Types

AS Licenses (Time-Limited)

• Duration: 1 year from activation.
• Auto-renew: renews automatically when a valid B&R service contract exists and the license can reach the B&R server.
• Stops auto-renewing if the service contract lapses or the OEM goes bankrupt.
• Cannot be returned to the B&R server after expiration (by design).
• Key risk: if an expired AS license sits on the same dongle as perpetual AR licenses, the AR licenses become trapped because returning any license from the dongle requires all licenses to be in a valid state.

AR Licenses (Perpetual)

• No expiration date.
• Tied to the PLC hardware or a dongle.
• Not affected by service contract status.
• Stored separately from AS licenses in most deployment scenarios (AR on PLC, AS on PC dongle).
• Can be activated via PLC network connection or by plugging the dongle into the PLC.

mapp Component Licenses

• Most mapp components are perpetual licenses.
• Stored on the same TG container as AS licenses (typically the USB dongle).
• Required at download time (AS verifies mapp licenses before downloading to PLC).
• Some mapp components have different licensing models; verify individually.

Server-Activated vs. Offline Licensing

Online activation requires:

• TLS 1.2 support (mandatory since March 2024).
• TG software version >= 1.4.
• CodeMeter Runtime >= 6.70.

License Key Format

B&R license keys follow this pattern:

xxxxx-xxxxx-xxxxx-xxxxx-xxxxx

25 characters total (5 groups of 5), alphanumeric. This key is your primary asset – treat it like a serial number. It is NOT the dongle serial number. The key is what you activate on the dongle; the dongle is the storage medium.

3. Identifying What Licenses You Have

Step 1: Locate the Physical TG Dongle

Physically inspect the machine and control cabinet:

• Check the engineering PC USB ports.
• Check the PLC panel – some machines have the dongle permanently plugged into the PLC.
• Check spare parts boxes and documentation folders.
• Check the CF card (CompactFlash) in the PLC – license documentation is sometimes stored there.
• The dongle is a small USB stick, typically green/blue, branded “CodeMeter” or “B&R.”

Step 2: Inspect the Dongle with Technology Guarding Software

1. Install TG software (see Section 4).
2. Plug the dongle into your PC.
3. Launch Technology Guarding (BR.AS.License.UI.exe).
4. The UI will show all licenses on the connected dongle.

Alternative: CodeMeter Control Center

1. Install CodeMeter Runtime (included with TG installation).
2. Launch CodeMeter Control Center from Start Menu.
3. Navigate to the dongle under “Devices.”
4. Select “License” tab to see individual license entries.

Step 3: Check PLC for AR Licenses

AR licenses stored on the PLC can be checked via:

Method A: SDM (Service & Diagnostics Manager)

1. Connect to PLC via Ethernet.
2. Open SDM in Automation Studio.
3. Navigate to PLC > Diagnostics > License.

Method B: OPC-UA

1. Connect to PLC OPC-UA server.
2. Browse to Automation.Components.AR.License namespace.
3. Read license status nodes.

Method C: PLC Web Interface

1. Open PLC IP in browser.
2. Navigate to System > License (on supported firmware versions).

Step 4: Find License Documentation on the CF Card

B&R PLCs use CompactFlash (or CFast) cards. Remove the card and check:

/System/License/
/System/Documentation/
/License/
/Config/

Look for files named:

• LicenseKey*.txt
• License.txt
• ActivationLog*.xml
• Any .txt or .pdf files with “license” in the name

Step 5: Check AS for Installed mapp Components

1. Open the existing AS project (if available).
2. In Solution Explorer, expand Logical View > mapp.
3. Each mapp component with a lock icon requires a license.
4. Check Project > Properties > mapp for a summary.
5. If AS is running with the dongle, open Tools > Technology Guarding to see what mapp licenses are detected.

Step 6: Determine Active vs. Installed Licenses

A license being “present” on the dongle does not mean it is “in use.” To determine active usage:

• AR licenses: always in use if the PLC is running.
• AS licenses: in use if AS is open on a PC with the dongle.
• mapp licenses: in use if mapp function blocks are instantiated in the running project and the PLC is executing them.
• Check PLC runtime: if the PLC is running, AR and active mapp licenses are in use. A PLC in stop state still “holds” its AR license but may not require mapp licenses.

4. Technology Guarding Software Setup

Download

TG software is available from B&R’s website. It is included in the PVI Development Setup download package.

Direct download path on B&R website:

1. Navigate to www.br-automation.com
2. Downloads > Software > Automation Studio > PVI Development Setup
3. Download the version matching your AS version.

The TG component within the installer is: USB: 1TG0500.02 (Technology Guarding).

Installation

1. Run the PVI Development Setup installer.
2. When prompted for components, select only:
   • USB: 1TG0500.02 (Technology Guarding)
   • PVI Runtime (if not already installed)
3. Complete the installation.

The installer places:

• TG application: C:\Program Files\BR\TechnologyGuarding\BR.AS.License.UI.exe
• State file: C:\ProgramData\BR\TechnologyGuarding\BR.AS.License.UI.state
• CodeMeter Runtime service (installed as Windows service)

Version Requirements

Critical: Since March 2024, B&R’s license server requires TLS 1.2. AS versions below 4.6 cannot license from within AS itself. Use TG standalone >= v1.4 instead.

CodeMeter Runtime Service

• Must be running for AS to detect the dongle and validate licenses.
• Service name: CodeMeter Runtime Server (or localized equivalent on non-English systems).
• Start manually: Services MMC, or:

  net start "CodeMeter Runtime Server"
  

• Set to Automatic startup for production PCs.

Server Configuration

When first launching TG standalone:

1. TG will prompt for server credentials.
2. If you do not have the OEM’s B&R portal credentials, you can leave the username/password blank or fill with placeholder text.
3. For activation with a known license key, the server communication is minimal – the key is validated, not authenticated against a user account.
4. The TG standalone tool can activate a license with just the key string, even without a valid portal login.

Offline Licensing Mode

For air-gapped systems (no internet at the PLC or engineering PC):

1. On an internet-connected PC with TG installed, start the offline activation process.
2. TG generates a request file (XML/encrypted) containing the license key and container ID.
3. Transfer the request file to the B&R license server manually (e.g., via email from a different PC).
4. The server returns an activation file.
5. Transfer the activation file back to the air-gapped PC.
6. Import the activation file into TG.

Alternatively, B&R support can process offline activations via email if you provide the dongle serial number and license key.

5. License Transfer Between Hardware Units

Moving Licenses from Old Dongle to New Dongle

Prerequisites:

• Both dongles must be functional (not stuck in firmware update mode).
• Licenses to be transferred must NOT be expired (expired licenses cannot be returned).

Method A: Via PLC (Network Transfer)

1. Plug the source dongle (old) into the target PLC’s USB port.
2. Connect to the PLC from AS (or SDM).
3. Activate the new licenses on the PLC’s TG element (or a dongle already on the PLC).
4. Once the PLC has the licenses, the source dongle’s licenses are consumed (transferred).
5. Remove the old dongle.

Method B: Direct Transfer (PC-Based)

1. Plug the source dongle (old) into the PC.
2. Plug the target dongle (new) into the PC.
3. Open TG software.
4. Select the source dongle, choose “Deactivate” or “Return” for specific licenses.
5. If return succeeds, activate those licenses on the target dongle.

Critical Limitation: If the source dongle has ANY expired license, the return operation may be blocked for ALL licenses on that dongle. See Section 7 for the workaround.

Software Container Migration

Do NOT use software containers on VMs. Software containers are bound to hardware fingerprints. Any of the following will invalidate the container:

• VM migration (moving to different host hardware).
• VM snapshot revert (restores old hardware fingerprint data).
• VM clone/copy.
• Virtual hardware upgrade (changing vCPU count, RAM, NIC MAC).
• Hypervisor host change.

If you must use a software container:

• Use it only on a physical PC.
• Do not upgrade the PC’s hardware.
• Back up the container activation files (from C:\ProgramData\BR\TechnologyGuarding\).

6. Activating Licenses Without Original B&R Portal Account

Using TG Standalone with License Key Only

This is the most common scenario when the OEM is gone:

1. Install TG software (Section 4).
2. Plug in a functional TG dongle (new or existing).
3. Launch TG (BR.AS.License.UI.exe).
4. When prompted for credentials, enter any placeholder text for username and password (e.g., “user” / “user”). The TG standalone tool does not strictly validate these for license key activation.
5. Select “Activate license online”.
6. Enter the 25-character license key: xxxxx-xxxxx-xxxxx-xxxxx-xxxxx.
7. Select the target container (dongle) from the dropdown.
8. Click Activate.

If the license key is valid and has activations remaining, the activation will succeed without OEM portal credentials.

If Online Activation Fails

Possible causes:

• License key already fully activated on other dongles (max activations reached).
• B&R server rejects activation for keys tied to accounts in bad standing (bankrupt OEM).
• Network/firewall blocking TLS 1.2 to B&R server.

Escalation path:

1. Contact B&R support ([email protected]).
2. Provide the license key and dongle serial number.
3. Explain the situation (OEM defunct, you are the new machine owner/maintainer).
4. B&R can:
   • Reset activation counts on the server.
   • Reassign licenses to a new account.
   • Issue replacement license keys in extreme cases.

Getting Help from B&R Support

When contacting B&R support as a non-original customer:

1. Have ready: license keys, dongle serial number(s), PLC serial number, machine location.
2. Explain clearly: “The OEM (name) is no longer in business. We maintain this machine and need to manage the B&R licenses.”
3. B&R support is generally helpful in these situations, but response times vary.
4. For safety-related licenses (mapp Safety, Safety Designer), B&R may require additional verification.
5. Create a new B&R portal account in your company’s name before calling – they may reassign licenses to your account.

7. Common License Problems and Solutions

Problem: TG Dongle Stuck in Firmware Update Mode (WB47 / WB67)

Symptoms:

• TG software detects the dongle but shows it as “updating” indefinitely.
• Error code WB47 or WB67 in CodeMeter / TG.
• AS cannot detect the dongle.
• Dongle LED may flash continuously or stay off.

Cause: The dongle’s CodeMeter firmware became corrupted during an update attempt, or the update was interrupted (USB disconnect, power loss, AS crash).

Solution:

• There is no user-serviceable fix. The dongle must be returned to B&R for repair/replacement.
• Contact B&R support with the dongle serial number.
• B&R will typically re-flash the dongle and restore licenses from their server records (if licenses were properly activated and recorded).
• If the dongle is out of warranty, there may be a cost for this service.
• Do NOT attempt to flash the dongle firmware yourself using third-party CodeMeter tools.

Prevention:

• Never disconnect the dongle while TG or AS is running.
• Never unplug during a license activation/deactivation operation.
• Use a USB port with stable power (not a hub, not a front-panel port on a flaky PC).

Problem: AS License Expired Before 1 Year

Symptoms: AS shows “license expired” despite being activated less than a year ago.

Cause: The TG system time on the dongle was reset or corrupted. If the dongle’s internal clock was not properly synchronized, the expiration calculation can be wrong.

Solution:

1. Ensure the PC’s system time is correct.
2. Plug the dongle in and open TG software.
3. TG should re-synchronize the dongle’s internal time with the PC.
4. If the dongle time is severely off, the license may appear expired permanently.
5. Contact B&R support for a license key reset in this case.

Problem: TLS 1.2 Blocking

Symptoms: TG cannot connect to B&R license server. Error about SSL/TLS or connection refused.

Cause: Since March 2024, B&R requires TLS 1.2. Older TG versions or .NET configurations default to TLS 1.0/1.1.

Solution: Force TLS 1.2 in .NET via Windows Registry:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319]
"SchUseStrongCrypto"=dword:00000001
"SystemDefaultTlsVersions"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319]
"SchUseStrongCrypto"=dword:00000001
"SystemDefaultTlsVersions"=dword:00000001

After applying, restart the PC and retry.

Alternative: Upgrade TG to >= 1.4 and CodeMeter Runtime to >= 6.70.

Problem: CodeMeter Runtime Service Not Running

Symptoms: AS shows “no dongle found” or “license system unavailable.” TG software shows no containers.

Solution:

net start "CodeMeter Runtime Server"

If the service fails to start:

1. Check Windows Event Viewer for errors.
2. Reinstall CodeMeter Runtime from the TG installer.
3. Ensure no other CodeMeter instances from other software (Lenze, Bosch) are conflicting.
4. Restart the PC.

Prevention: Set the service to Automatic startup type.

Problem: “Maximum Number of Activations Reached”

Symptoms: TG reports that the license key cannot be activated because all activations are used.

Cause A: Genuine over-activation. The license was activated on multiple dongles/PCs by the OEM.

Cause B: File permission issue. TG cannot write its state file.

Check file permissions:

The TG state file must be writable:

C:\ProgramData\BR\TechnologyGuarding\BR.AS.License.UI.state

1. Open Properties > Security on this file.
2. Ensure the current user has Full Control.
3. Ensure the folder C:\ProgramData\BR\TechnologyGuarding\ is also writable.
4. If permissions are correct and activations are genuinely exhausted, contact B&R support for a reset.

Problem: License Activated on Wrong Dongle (Third-Party Dongle)

Symptoms: A license appears on a dongle that is not the B&R TG dongle. CodeMeter Control Center shows the license under a different manufacturer’s container.

Cause: If the PC has CodeMeter drivers from another vendor (e.g., Lenze, Bosch Rexroth), the TG activation may target the wrong container.

Solution:

1. Disconnect all non-B&R CodeMeter dongles.
2. Open CodeMeter Control Center.
3. Identify the B&R dongle by its serial number.
4. In TG, explicitly select the correct dongle/container before activating.
5. If already activated on the wrong container, return it from the wrong container first, then activate on the correct one.

Problem: Software Container Invalidation in VMs

Symptoms: After VM migration or snapshot, all TG licenses show as invalid or missing.

Cause: Software containers are hardware-fingerprint-bound. VM changes invalidate the fingerprint.

Solution:

1. Do not use software containers on VMs (preventive measure).
2. If already in this state: return the invalid container activation (may not work if fingerprint is completely changed).
3. Re-activate licenses on a USB dongle instead.
4. If no dongle is available, contact B&R support.

Error Code Reference Table

8. Evaluation Licenses

Using AS Evaluation Licenses as a Stopgap

When you have no valid AS license and need immediate access to the IDE for diagnostics or minor changes:

1. Download Automation Studio from B&R website (full installation).
2. During installation, select “Evaluation” mode.
3. AS will run in evaluation mode for 30 days (typical; may vary by version).

What evaluation mode provides:

• Full AS IDE functionality.
• Ability to connect to PLCs, upload/download projects.
• Ability to go online and diagnose.
• Ability to edit logic and download changes.

What evaluation mode restricts:

• Time-limited (30 days typically).
• May have watermarks or “Evaluation Mode” indicators.
• Not suitable for safety-related work (mapp Safety changes).
• Cannot be used for production deployment in a commercial setting.

When Evaluation Licenses Are Sufficient

Evaluation AS licenses are appropriate for:

• Initial forensics on an inherited machine (reading the project, understanding logic).
• Diagnostics and troubleshooting (going online, monitoring variables).
• One-time code changes (quick fixes, parameter adjustments).
• Emergency recovery situations where you need AS access immediately.

Evaluation AS licenses are NOT appropriate for:

• Ongoing development (they expire).
• Safety-related modifications (mapp Safety requires proper licensing).
• Any work that needs to be audited or documented for regulatory compliance.

Important: Evaluation + Existing Dongle

You can run AS in evaluation mode while keeping the TG dongle plugged in for AR and mapp licenses. The evaluation license covers AS IDE access; the dongle covers the runtime and mapp component licensing. This is a practical workaround when the AS license on the dongle is expired but the AR/mapp licenses are still valid and you cannot return them.

9. mapp Component Licenses

Common mapp Components

Determining Which mapp Components Are Licensed

Method 1: TG Software

1. Open TG with dongle connected.
2. Browse the license list on the container.
3. Each mapp license appears as a separate entry (e.g., “mappView,” “mappAlarmX”).

Method 2: CodeMeter Control Center

1. Open CodeMeter Control Center.
2. Select the dongle.
3. View Product Items – each mapp component has a distinct product code.

Method 3: AS Project

1. Open the AS project.
2. Expand Logical View > mapp in Solution Explorer.
3. Each mapp component folder present indicates that component is used in the project.
4. Cross-reference with TG to confirm licensing.

What Happens When a mapp License Expires

• AS behavior: AS will show a warning when opening the project. You can still view the code but may not be able to download to PLC.
• PLC behavior: The PLC continues to run the existing code. mapp components already loaded and executing on the PLC do not stop when the license expires on the dongle/PC.
• Download restriction: You cannot download a project to PLC if required mapp licenses are missing/expired on the TG container used by AS.
• Runtime implications: For mapp components that check licenses at runtime (rare), functionality may degrade.

mapp Safety Specific Considerations

mapp Safety licensing has additional constraints:

• Safety Designer requires its own TG license (separate from mapp Safety runtime).
• Safety-related function blocks will not compile/download without valid Safety Designer and mapp Safety licenses.
• Do not attempt to modify safety logic without proper licensing. If safety logic needs changes and no safety license is available, contact B&R support immediately – this is a safety-critical gap.
• Safety licenses may have additional transfer restrictions compared to standard mapp licenses.

10. Automation Runtime Licenses

AR License Types

AR License Storage Locations

AR licenses can be stored on:

1. The PLC itself (via X20CMR module or built-in TG element).
2. A USB dongle plugged into the PLC.
3. A software container on the PC running AS (for download-time validation only – the AR license itself must be on the PLC or its dongle).

Best practice: AR licenses should be on the PLC or a dongle permanently attached to the PLC, not on a portable dongle shared with AS.

AR License Activation via PLC

If the PLC has a TG-capable element (X20CMR module):

1. Connect the PLC to the network with internet access.
2. In TG, select the PLC’s TG element as the target container.
3. Activate the AR license key on the PLC’s TG element directly.
4. No dongle required.

If using a dongle:

1. Plug the TG dongle into the PLC’s USB port.
2. From a network-connected PC, use TG or SDM to activate the AR license on the dongle while it’s on the PLC.
3. Alternatively, plug the dongle into a PC, activate the AR license, then move the dongle to the PLC.

Checking AR License Status Without AS

If AS is unavailable (no license, no installation):

1. SDM (Service & Diagnostics Manager) can connect to the PLC independently and show license status.
2. PLC Web Interface: Open the PLC’s IP address in a browser. Navigate to System > License (if available on your firmware version).
3. OPC-UA: Connect to the PLC’s OPC-UA server and read the license status nodes under Automation.Components.AR.License.
4. Physical inspection: Check if an X20CMR module is installed in the X20 bus. Its LED indicators can show TG status.
5. FTP/SFTP: Connect to the PLC via FTP and check /System/License/ directory for license files.

AR Service License

The AR service license is a separate concept from the AS service contract:

• It enables the PLC to receive firmware updates.
• Without it, the PLC still runs but cannot be updated.
• It is perpetual but may have a validity period linked to the service contract.
• If the OEM’s service contract has lapsed, the AR service license may show as expired, but the PLC continues to run its current firmware.

11. License Recovery Scenarios

Scenario A: OEM Went Bankrupt

What happens to licenses:

• Perpetual licenses (AR, mapp) remain valid on their containers indefinitely.
• AS licenses will stop auto-renewing after the current period expires (typically 1 year from last renewal).
• License keys remain valid on B&R’s servers unless explicitly revoked (which B&R does not typically do).

Your position:

• You own the physical dongle(s) and PLC(s) – you have physical possession of the licensed hardware.
• B&R’s general policy: licenses follow the hardware, not the account. If you have the dongle and PLC, you can use the licenses.
• AS auto-renewal stopping means you must find an alternative (evaluation, purchasing new AS license, or contacting B&R to transfer the license to your account).

Action items:

1. Inventory all dongles, PLCs, and license keys immediately.
2. Document everything (serial numbers, key strings, dongle serials).
3. Contact B&R support to open a support case in your company’s name.
4. Request license transfer to your account.
5. Negotiate a new service contract with B&R if continued AS licensing is needed.

Scenario B: Lost TG Dongle

Impact:

• All licenses stored on that dongle are inaccessible.
• AS will not function (no AS license).
• mapp component licenses for download are unavailable.
• If the dongle was on the PLC, AR licenses may also be lost.

Recovery options:

1. Check if B&R’s server has records of the licenses on the lost dongle (provide dongle serial number to support).
2. B&R may be able to deactivate the lost dongle on their server and re-issue licenses on a new dongle.
3. This process requires proof of ownership (PLC serial number, original purchase records if available).
4. If B&R cannot verify the licenses, you may need to purchase replacement licenses.

Prevention:

• Keep the dongle permanently installed in the PLC cabinet (not carried around).
• Document the dongle serial number and keep it in multiple locations.
• Back up the contents of the CF card, which may contain license records.

Scenario C: Damaged Dongle

If the dongle is physically damaged but still detected by the PC:

• Try to return all licenses to the B&R server immediately.
• If some licenses cannot be returned (expired), contact B&R support.
• Once all returnable licenses are recovered, B&R can issue a replacement dongle with the returned licenses.

If the dongle is completely dead (not detected):

• Same as lost dongle (Scenario B).
• B&R may need the physical dongle for forensics. Send it to them if they request it.

Warranty:

• TG dongles have a limited warranty (typically 2 years).
• If under warranty, B&R will replace the dongle and restore licenses free of charge.
• If out of warranty, there may be a replacement cost plus a fee for license restoration.

Scenario D: Dongle with Stuck Licenses (Cannot Return Any)

The “sticky dongle” problem:

This occurs when:

• One license on the dongle has expired.
• You try to return other (still-valid) licenses from the dongle.
• The return operation fails because the dongle contains at least one expired license.

Root cause: B&R’s design intentionally prevents returning licenses from a container that contains expired licenses, to prevent license farming / abuse.

Workaround: Use Evaluation AS + Keep Dongle on PLC

1. Install AS in evaluation mode (30 days, renewable by reinstalling).
2. Keep the TG dongle plugged into the PLC (not the PC).
3. The dongle’s AR and mapp licenses continue to serve the PLC.
4. Use evaluation AS for IDE access (diagnostics, minor changes).
5. The expired AS license on the dongle does not affect PLC operation – only AS IDE access.

Escalation:

1. Contact B&R support.
2. Explain that an expired license on the dongle is blocking return of other licenses.
3. B&R support may be able to:
   • Manually invalidate the expired license on their server.
   • Enable a special return operation.
   • Issue replacement license keys for the trapped perpetual licenses.
4. This escalation may take days to weeks. Plan accordingly.

Scenario E: Buying Used Equipment

When purchasing a used B&R machine:

1. Verify that TG dongles are included with the machine.
2. Document all dongle serial numbers and note which licenses are on them.
3. Request license transfer documentation from the seller.
4. Contact B&R to confirm the licenses can be transferred to your account.
5. Be aware that AS licenses from a defunct seller will eventually expire and cannot be renewed without a service contract in your name.

Buying from an auction / liquidation:

1. Same as above, but seller documentation may be unavailable.
2. B&R may require proof that the seller had legitimate ownership before transferring licenses.
3. In some cases, licenses may not be transferable if the original account is in bad standing.

Scenario F: Upgrading to Automation Studio 6 (License Implications)

AS6 introduces a new licensing model called shared upgrades that differs from AS4’s perpetual dongle model. If you are migrating from CP1584 to a modern controller, you will need AS6 and its licensing affects your planning:

Key implications for the OEM-unavailable scenario:

• Existing AS4 perpetual licenses do not automatically carry to AS6. You need a new AS6 license or service contract.
• AR licenses (perpetual) on the PLC are unaffected by the AS version — the runtime doesn’t change.
• If you plan to use evaluation AS6 for migration work, note that evaluation periods are shorter and may not support all mapp 6 components.
• Contact B&R support early to discuss a migration license package — they may offer discounted upgrades for existing hardware owners.
• Community migration tools at github.com/br-automation-community/as6-migration-tools can help identify license implications in your project.

See firmware-version-mgmt.md §5.3.1 for the full AS4→AS6 migration guide.

12. Key Findings

1. Inventory immediately. Document every dongle serial number, license key string, PLC serial number, and X20CMR module before anything else is lost. Store copies off-site.

2. Do not let AS licenses expire on a shared dongle. An expired AS license on the same dongle as perpetual AR/mapp licenses traps all licenses and prevents returns. Monitor AS license expiration dates via TG software.

3. Keep the dongle on the PLC. For production machines, the TG dongle should live in the PLC cabinet, not on the engineering PC. This isolates AR/mapp licenses from PC-side AS license issues.

4. Use TG standalone >= v1.4 for licensing operations. Do not rely on AS < 4.6 for license management – it lacks TLS 1.2 support and cannot communicate with B&R’s license server after March 2024.

5. Never use software containers on VMs. Any VM migration, snapshot, or hardware change invalidates the container. Use physical USB dongles exclusively for production.

6. Force TLS 1.2 in Windows Registry. If TG or AS cannot connect to the B&R license server, apply the .NET SchUseStrongCrypto registry keys before spending time on network troubleshooting.

7. CodeMeter Runtime Service must run. If AS shows “no dongle” and the dongle is physically present, check that the CodeMeter Runtime Server Windows service is running before assuming the dongle is broken.

8. Evaluation AS licenses are a viable stopgap. Run AS in 30-day evaluation mode while keeping the dongle on the PLC for AR/mapp licensing. This sidesteps the expired-AS-on-shared-dongle problem.

9. TG standalone does not strictly validate portal credentials. When activating a license key on a dongle, placeholder credentials work. You do not need the OEM’s B&R portal account.

10. A stuck dongle (WB47/WB67) is a hardware problem. Do not waste time trying software fixes. Return the dongle to B&R repair immediately and use evaluation AS in the interim.

11. Expired licenses don’t stop running programs immediately. Most mapp technology components continue to function with expired licenses but display warnings. However, some features may be disabled after a grace period.

12. Offline licensing is possible for air-gapped systems. B&R provides an offline activation procedure using challenge/response codes for systems without internet connectivity.

13. Cross-References

14. Sources

• B&R Automation Studio documentation, Automation Runtime documentation – BrAutomation.com downloads section.
• B&R Technology Guarding product page and knowledge base articles.
• Wibu-Systems CodeMeter documentation – CodeMeter.com.
• B&R Knowledge Base article: “Technology Guarding – TLS 1.2 requirement since March 2024.”
• B&R Knowledge Base article: “License activation with Technology Guarding standalone.”
• B&R Knowledge Base article: “What to do when your TG dongle is stuck in firmware update mode.”
• B&R Knowledge Base article: “AS license expiration and auto-renewal behavior.”
• B&R Knowledge Base article: “Returning licenses from a container with expired licenses.”
• B&R Technical Note: “Offline licensing procedure for air-gapped systems.”
• Wibu-Systems CodeMeter error code reference (WB47, WB67, etc.).
• Community forum reports from automation engineers maintaining inherited B&R equipment.
• Practical field experience with CP1584 PLCs from defunct OEMs.