Example of a complete app_info.json To make it easier for you to create a correct JSON file, you can use the following JSON schema: { “$schema”: “https://raw.githubusercontent.com/PLCnext/App-Info-Schema/refs/heads/main/app-info-schema.json”, “plcnextapp”: { … } } If you use a code editor that supports JSON… 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
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
Shared Libraries The support for the Shared Libraries app part type is discarded and removed from PLCnext Technology firmware from version 2025.0. It can happen that an exe file integrated in the app container, such as a Command Line Tool, brings its own Shared Libraries with it and needs them for its… Read More
Creation of an app container The Linux command plcnextapp is available under /usr/bin and is used to create an app container. The following parameters are supported: create e.g.: plcnextapp create /opt/plcnext/myapp My App example e.g.: plcnextapp example “create”: Creates a… Read More
