Installation TwinCAT 3.1 Build 4026
The following installation instructions are intended for users installing TwinCAT 3.1 Build 4026. To install TwinCAT 3.1 Build 4024, read the documentation Installation TwinCAT 3.1 Build 4024.
TwinCAT 3.1 Build 4026 is installed with the help of the TwinCAT Package Manager. With this setup, you can not only install TwinCAT in three variants as before, but also select and install additional TwinCAT components individually. You can also update and uninstall TwinCAT components individually.
 | Installation of Build 4026 on existing 4024 systems only with migration On existing Build 4024 systems, you can only install Build 4026 by performing a migration. 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. Further information can be found in chapter Migration to Build 4026. |
| To be able to use TwinCAT Package Manager and TwinCAT 3.1 Build 4026, you need the myBeckhoff account. |
The TwinCAT Package Manager is based on two components that build on each other:
- TwinCAT Package Manager: The interface for menu-driven installation (User Interface)
- TwinCAT Package Manager Command Line Interface "TcPkg": The command line program is used by the user interface.
All actions on the interface lead to calls to the command line program. This means that all functions of the interface can be mapped in the command line, but the command line can sometimes provide more detailed functions that are not mapped in the interface.
Basics
The TwinCAT Package Manager downloads packages and their dependencies from one or more so-called feeds. "Stable" and "Testing" feeds are available from Beckhoff. However, customers can also provide their own feeds if these contain TwinCAT packages for offline installation, for example. The bases for this are either normal directories ("c:\packagesoffline", possibly provided via a network drive) or Nuget Package Server.
Products, as displayed in the interface, contain a list of packages with versions, i.e. they have dependencies on specific package versions. These packages for representing products are called workloads, as is also common in Visual Studio.
It is the task of the TwinCAT Package Manager to resolve these dependencies and fulfill them through installation.