I am looking for firmware v2.27 for cp476
Hello @anon7194701 ,
attached I send you the Automation Runtime files of V2.27, which you have to copy in your installation folder of Automation Studio V2.x at “..[Automation Studio V2.x installation folder]\As”.
br Christoph
V0227.zip (5.7 MB)
Hello @anon7194701 ,
PG2000 is really old and I personally hasn’t used it, but I found the “installation disk” of Automation Runtime V2.27 for PG2000, which I attach.
Hopefully you can install the Automation Runtime.
V0227_PG2000.zip (10.5 MB)
br Christoph
Thank very much indeed
Thank you very much indeed
Subject: Technical Inquiry Regarding CP476 Migration from PG2000 to Automation Studio
Dear MMr.Chiristoph Behaf
I hope you are doing well.
First of all, I would like to sincerely thank you for your valuable support and guidance in the past. Your assistance has always been greatly appreciated.
I am contacting you regarding an important modernization project on one of our machines. The existing control system is based on a B&R CP476 CPU with Firmware Version 2.27, an IF V311 communication module, and several I/O modules.
The machine was originally programmed approximately 25 years ago using PG2000. Unfortunately, the original source code is no longer available, and the machine manufacturer is no longer able to provide software support. Therefore, we have decided to completely redevelop the control software from scratch.
Our intention is to develop the new application using Automation Studio while retaining the existing hardware platform, including the CP476 CPU, IF V311 module, and installed I/O modules.
Before proceeding, I would highly appreciate your advice regarding the following points:
-
Are there any known risks, limitations, or compatibility concerns when completely rewriting the application in Automation Studio while keeping the existing hardware?
-
Is it necessary or recommended to upgrade the current CPU firmware (Version 2.27), or can the existing firmware be retained for this project?
-
Is the CP476 CPU, despite its age, capable of supporting an Automation Studio-based application and development workflow?
-
Are there any specific recommendations or best practices for migrating from a PG2000-based system to an Automation Studio project while maintaining the original hardware configuration?
For your information, the CPU is currently fully operational. We can successfully communicate with it using Runtime Utility Center, and all hardware components appear to be functioning correctly. In addition, we have complete electrical documentation, wiring diagrams, and a thorough understanding of the machine’s operating sequence and functionality.
To assist your evaluation, I have attached the Hardware Information report and system details extracted from the controller.
Thank you very much for your time and support. I would greatly appreciate any recommendations or guidance you can provide.
Best regards,
Ghassem sharif
ای
CamScanner 06-12-2026 17.12.pdf
Hi,
even if I’m not able to give concrete binding advices, he’re some informations/ answers to your questions.
First about the risks keeping the hardware: the system family 2003, which are all hardware modules you posted are part of, is in lifecycle stage “obsolete”.
That means that in case of a hardware failure the system is maybe still repairable by B&R (I can’t guarantee), but the products are not longer produced or sold.
I did a quick check of the modules you’ve posted: it looks like that there’s nothing “very specific” in use, beside the PLC and a 2nd RS232 interface mostly digital input/output modules are used plus some analog output and thermocoupler temperature measurement.
For sure it has to be checked more in detail (in cooperation with your local B&R representative or partner) as we’re able to do it here in the Community, but I’m quite sure that a actual B&R system like X20 family could be used as hardware also.
About the software compatibility, I also did a quick check: system 2003 seems to be supported up to Automation Studio 4.12 (I don’t checked all hardware, just the PLC module), which is still officially available by today, but not longer in active development regarding new features and so on (Automation Studio 4.xx will not reach CRA compliance).
The actual version family of Automation Studio is 6.xx, where system 2003 any other discontinued hardware is not longer supported.
The firmware V2.27 is not part of Automation Studio 4.12, by default available versions are 2.40 and 2.52.
I’m not aware if 2.27 is in common usable with Automation Studio, but as you want to develop the software from scratch, I don’t think that there would be a mandatory reason still to use V2.27 (the PLC can be upgraded to newer versions, there’s nothing additionally needed beside Automation Studio).
About “porting software from PG2000 to Automation Studio”: as I remember, for some of the programming languages it was possible somehow in times of Automation Studio 2.xx.
But as this also very old versions of Automation Studio aren’t longer available too, I can’t imagine that there’s still a way to do this.
But if having somewhere still PG2000 running on an old Notebook or in some virtual environment, in my opinion having a look into the sources of the PG2000 project would still help a lot when rewriting the software.
So, in a nutshell:
- I think it could be possible to make a Automation Studio 4.12 project with your existing hardware
- I would nevertheless propose to switch additionally to new hardware supported by Automation Studio 6 because of the lifecycle stadium of the system 2003 hardware family and also of Automation Studio 4.xx
I hope those informations helped a bit and have at least answered some of your questions.
Best regards!