Migration to Build 4026

Since TwinCAT 3.1 Build 4024 is installed via Setup and Build 4026 via TwinCAT System Manager, the installation of Build 4026 on existing Build 4024 systems is only possible via migration.

A system on which Build 4024 is installed and which is to be migrated to Build 4026 can be an engineering system and/or runtime system.

A guided migration is available via the TwinCAT Package Manager. If desired, you can then install engineering versions < Build 4026 (as before) as Remote Manager. The Remote Manager Workloads are available in the Package Manager.

Summary

The execution of the migration tool includes the following steps:

  1. All installed Build 4024 components are identified.
  2. The system is cleaned by uninstalling all Build 4024 components.
  3. Build 4026 is installed. On the one hand, the actual TwinCAT Engineering or runtime version of Build 4026 is installed. On the other hand, all components/functions that were previously installed on the 4024 system are installed for version 4026, provided the component is available under Build 4026.

Step-by-step instructions

1. Download the Beckhoff TwinCAT Package Manager from the Beckhoff homepage.
2. Execute TwinCAT-Package-Manager-Setup.exe by double-clicking on the file.
3. Follow the instructions for installing the Package Manager.
4. Open the Package Manager.
5. Add the Stable Feed and enter your myBeckhoff login data.
https://public.tcpkg.beckhoff-cloud.com/api/v1/feeds/Stable
Migration to Build 4026 1:
6. Select a suitable Visual Studio version or shell for the integration of Visual Studio.
7. Click Next.
A message appears stating that an older version of TwinCAT has been detected on the system and that the migration tool must be installed in order to continue.
8. Confirm with Yes.
Migration to Build 4026 2:
The installation of the migration tool is started and an output window appears.
If the message Package(s) installed: TwinCAT.XAE.MigrateCli appears in the window and the status at the bottom left changes to Finished, the installation has been completed.
9. Close the window with OK.
Migration to Build 4026 3:
Next, the migration process is simulated.
10. To do this, confirm the message with OK.
Migration to Build 4026 4:
All old TwinCAT setups found on the system and the corresponding TwinCAT Package Manager versions to be migrated to are listed.
11. To start the migration, click Next.
Migration to Build 4026 5:
12. Confirm the query as to whether you want to start the migration with Yes.
An output window appears in which the migration can be tracked. After a short time, the migration requires a system restart.
13. Confirm with Ok to restart the computer.
After the restart, the TwinCAT Package Manager will automatically open again and continue with the migration.
When the migration is complete, this appears in the output and the installed products are displayed.
14. End the migration with Close.
Migration to Build 4026 6:
15. If you have any questions about the process, please provide the log files of the following folder:
C:\ProgramData\Beckhoff\TcMigrateCmd
The migration to TwinCAT 3.1 Build 4026 has been completed.