Example of a complete app_info.json The following shows the contents of an app description file in which all types of app parts are configured by way of example: { “plcnextapp”: { “name”: “Full Multipart App”, “identifier”: “00000000000000”, “version”: “Full20.0 (112.12 DemoVersion)”, “target”:… Read More
PLCnext Control Solution A PLCnext Control Solution contains a complete PLCnext Engineer project configuration as an app part. A PLCnext Engineer Solution is also called solution for short. The user of a solution does not need any programming knowledge to use the app. A solution is transferred directly from the PLCnext Store or… Read More
OCI container The OCI container app part type is supported in the PLCnext Technology firmware from version 2025.0. This app part provides the possibility for simplified integration and run of OCI (Open Container Initiative) container images of apps on the PLCnext Technology device. For this topic the container engine… Read More
App parts The app container can contain various app parts. This allows different app types to be implemented. The app parts are entered as optional entries in the app description. If these parts are present, the PLCnext Runtime (AppManager) reacts accordingly. The app description file must contain… Read More
PLCnext Technology Extensions Extensions of the runtime can be integrated into a system in the form of an app. With a PLCnext Technology Extension, the runtime can be extended by the following elements: A process dependent on the runtime (process) A component (component) A Shared Library (library), which usually… Read More
Linux Daemons The support for the Linux Daemons app part type is discarded and removed from PLCnext Technology firmware from version 2025.0. From version 2025.0, the OCI container app part type is supported in the PLCnext Technology firmware. A (Linux) Daemon can be integrated into a system in the form of an app. Read More
Metadata The app description file must contain a JSON object with the name “plcnextapp”, which describes the properties of the PLCnext Technology App: { “plcnextapp”: { “name”: ““, “identifier”: ““, “version”: ““, “target”: ““, “minfirmware_version”: ““, “manufacturer”: ““, “licensetype”: ““,… Read More
Configuration of the PLCnext Technology Runtime Services If you need access or sometimes exclusive access to PLCnext Technology System Services in your app or a PLCnext Technology System Service is not allowed to be running when your app run, you can state this in the “plcnextservices” field of the app_info.json. This is often not… Read More
File and data storage The files of an app container are unpacked into a read only filesystem mounted via SquashFS, so that the apps cannot save/store data/files in their installation directory at runtime. The app description can be used to specify whether a persistent and/or… Read More
App installation states PLCnext Technology Apps must be installed and uninstalled using either the PLCnext Store or the web-based management (WBM) hosted on the controller. In the background, both the PLCnext Store and the WBM interact with the AppManager on the controller to handle the app installation and run states. A PLCnext Technology App… Read More
