The installation of the product ends with an error.

Requirements

The CODESYS installation includes the product-specific CODESYS package (and its dependent products). You can get an overview of the installed products in the CODESYS Installer in the list of installed add-ons.

Troubleshooting

Errors during installation may be caused by the target device. Common errors are read-only file systems and outdated or missing dependencies.

All products expect their package to be stored in the location where the CODESYS Installer stored it when the add-on was installed.

. The Deploy Tool performs the following steps for each installed product:

Stop the runtime process.
Save the old config file.
Delete the existing package.
Transfer the new package.

Additional product-specific checks are listed below, which the Deploy Tool performs depending on the product. The Package Manager then attempts to install the newly transferred package:

BeagleBoneBlack	No additional steps or checks are performed.
Edge Gateway	The Deploy Tool checks whether the device has an armv4, armv5, or armv6 architecture. The value is read by executing the command `uname -m`.
emPC	No additional steps or checks are performed.
IOT2000	No additional steps or checks are performed.
License Server	The Deploy Tool attempts to install a current version of Codemeter. If Codemeter or Codemeter Lite is installed in the same or newer version than the version expected by Deploy Tool, then no changes will be made to the system. If an upgrade or change is necessary, then a dialog prompt will open for you to agree before any changes are made to your system. If you agree, then the currently installed version of Codemeter will be removed and a current version will be installed. Please note that the CODESYS License Server for Linux SL cannot be used if Codemeter is not installed on the system. The Deploy Tool also allows you to install an optional plug-in called "Cockpit". This enables the CODESYS WBM to be used, which facilitates the activation of licenses on the target device. You can decline this option and the installation process will continue. If you agree and an error occurs during the installation of the Cockpit Package, then the installation process will be aborted.
Linux SL LinuxARM SL LinuxARM64 SL	The Deploy Tool attempts to install a current version of Codemeter. If Codemeter or Codemeter Lite is installed in the same or newer version than the version expected by Deploy Tool, then no changes will be made to the system. If an upgrade or change is necessary, then a dialog prompt will open for you to agree before any changes are made to your system. If you agree, then the currently installed version of Codemeter will be removed and a current version will be installed instead. Please note that these products cannot be used if Codemeter is not installed on the system.
Safe Control	No additional steps or checks are performed.
SafeTimeProvider	No additional steps or checks are performed.
PFC100 PFC200	Before version 4.15: The Deploy Tool attempts to install the EntropyHelper package. The products expect the package to be stored in the location where the CODESYS Installer stored it when the add-on was installed. If the package is not listed, not found, or the installation fails, the product will not be installed.
TP600	No additional steps or checks are performed.
PLCNext	The Deploy Tool attempts to read the firmware version with the following command: `cat /etc/plcnext/arpversion \| head -1 \| cut -f2 -d' ' \| cut -f-3 -d '.'` If the version cannot be read, then the installation is aborted. The Deploy Tool searches locally for the `codesys-arp PLCnext` package in a version which matches the firmware. The package is installed. If no package is found or the installation fails, then the installation of the product is aborted.
Raspberry Pi	After the package is installed, the runtime type to be used is defined. The type depends on the loaders which are available on the system. The loaders are retrieved as described in the "Userland architectures" chapter. If no loader is found, then the armv6l variant is used. The following list shows the individual variants: Multicore 64-bit: aarch64 Multicore 32-bit: ARMv7 Standard (no multicore): ARMv6 Depending on your system, you can change this setting in the Deploy Tool after the product is installed.
TargetVisualization	No additional steps or checks are performed.
Virtual Control Virtual Edge Virtual Safe Virtual SafeTimeProvider	Python version 3.9 or newer and either Docker or Podman must be installed on your device.