How to Obtain Older Versions of Automation Studio [ AS2 | AS2.7 | AS3.0 | AS4.x ]

[kovarj (Jaroslav Kovar)]

Currently, Automation Studio 6.x and the latest Automation Studio 4.12 release are available for download from the B&R website. Older versions have been removed from the public download section due to regulatory compliance requirements related to EU dual-use export regulations.

I Need an Older Version. What Should I Do?

I Already Have the Installer

If you already have a local copy of the required Automation Studio version, you can continue using it for maintenance and service activities on existing projects.

I Do Not Have the Installer

If you require an older version for an existing project, please contact your local B&R support and provide:

• The exact Automation Studio version required
• The project or machine for which the version is needed

Based on a justified business need, legacy installation packages may still be provided through official channels outside the public download section.

Which Versions Are Typically Available?

The most commonly requested legacy versions include:

• Automation Studio 4.x
• Automation Studio 3.0
• Automation Studio 2.7

What About Very Old Versions?

Versions older than 2.7, such as Automation Studio 2.2 or Automation Studio 2.4 installer can be provided as well on request. However, these versions can no longer be registered and therefore are generally not practical for productive use.

In such cases,

migrating to at least Automation Studio 2.7 is recommended,

as it represents the oldest practically usable baseline version.

Why Can’t I Request These Versions Through B&R Community?

B&R Community cannot provide or distribute legacy Automation Studio versions.

Due to export control and compliance requirements, the Community platform has no reliable mechanism to uniquely verify the identity, location, and eligibility of a requestor. As a result, requests for legacy software must be handled through official B&R support channels, where the necessary verification and compliance processes can be performed

Jaroslav

[whyleys (Shaun Whyley)]

@kovarj

regulatory compliance requirements related to EU dual-use export regulations

a big problem is how the files would be transferred under B&Rs strict rules of file transfer…

I find this hugely disappointing that the versions have been removed already, especially later 4.x versions.

[kovarj (Jaroslav Kovar)]

Sure, I understand. I think there is still a chance that some AS4.12.x versions might become available again. On the other hand, most of us keep local copies of the AS installation files for the versions we need for our projects. For new projects, we use the latest AS4.12 or AS6 versions, and those are normally available.

The only situation where someone would really need an older version is if they deleted their local installer and later needed to go back to that specific version. But I don’t think this is a day-to-day use case.

[Michael.Uray]

Why don’t you just require username and password authentication for these legacy downloads?
After a login of a user it is clear if he is authorized to download these versions or not.

[alexander.hefner]

Hi,

Dual-use refers to goods, software, and technologies that can be used for both civilian and military applications. Because of that, we need to know a bit about the intended use, the machine location, and maybe some other background, before we’re allowed to grant access to such older versions.
Unfortunately, such information cannot be directly derived by a valid user login, that’s the reason why we can’t make the downloads accessible just via login.
I also hope that there will be again some possibility in future, but right now we can only follow the process as described by Jaroslav.

Best regards!

[kovarj (Jaroslav Kovar)]

I had some of the same questions as you, but @alexander.hefner explanation is absolutely valid.