FAQ

Error code 451 when accessing myBeckhoff (create feed / fetch packages)

New conditions must be accepted for error code 451. Please log in at www.beckhoff.com.

Visual Studio mapping at package level

Packages that represent a Visual Studio or XAE Shell integration have one corresponding package per supported Visual Studio variant. Depending on the configuration, this is used automatically and transparently by the TwinCAT Package Manager to execute the corresponding integration.

As they are handled transparently, these packages are not normally displayed separately, but appear, for example, as separate files on the file system.

For example, the following Visual Studio integration packages also exist for the "TwinCAT.XAE.SystemManagerVS" component:

TwinCAT.XAE.SystemManagerVS
TwinCAT.XAE.SystemManagerVS.TcXaeShell64
TwinCAT.XAE.SystemManagerVS.TcXaeShell
TwinCAT.XAE.SystemManagerVS.VS2017
TwinCAT.XAE.SystemManagerVS.VS2019
TwinCAT.XAE.SystemManagerVS.VS2022

"Changes to device" message from Powershell in connection with UAC

Depending on the user account control (UAC) set in Windows, Microsoft Powershell issues prompts for changes to the device while the TwinCAT Package Manager is being used:

FAQ 1:

These prompts result from the technical implementation of the TwinCAT Package Manager. Only the required write accesses such as configuration changes or the installations themselves are executed under administrator rights.