Documentation The documentation of the solution must be saved as a *.pdf file and uploaded to the PLCnext Store. Note: If you want a template for the documentation, please contact the PLCnext Store admin. He can provide you with an appropriate template. The following points must at least be included:… Read More
Building a PLCnext Control Solution App containers must be created on a PLCnext Control, using a command line utility called plcnextapp. In order to build an app, you will need an SSH client (e.g. PuTTY) and an SFTP client (e.g. WinSCP). Then you just have to follow the steps below. Read More
Overview creating a PLCnext Control Solution In the following, we use the term PLCnext Control Solution or solution for short. Program your PLCnext Control Solution with PLCnext Engineer. If you want to sell your PLCnext Control Solution, extend your program with our license mechanism. Download your PLCnext Control Solution on your PLCnext Control. Prepare your PLCnext Control Solution in the… Read More
Publishing PLCnext Technology Apps PLCnext Technology App types in the PLCnext Store In the PLCnext Store you can publish different types of software in the form of an app. In the following, we use the term PLCnext Technology App or app for short. Currently, seven app types are available in the PLCnext Store: PLCnext Control Function… Read More
Documentation (PDF and CHM) The documentation of the library must be saved as a *.pdf file in the *.zip folder and uploaded to the PLCnext Store. Ideally, you should also create this documentation as a *.chm or *.html file. For examples of how the documentation can be structured,… Read More
Standard and functional tests After you have finished your library, you need to run some tests. Standard tests Compile test Run a compile test with all PLCnext Engineer versions for which the library is released. For this test, all functions and function blocks must be instantiated in a test… Read More
Programming guideline In the following you find the minimum requirements that you must observe and implement when programming your library. 🗹 Naming the library Using several libraries within one project can cause problems if they do not have a unique name. Phoenix Contact recommends to include the… Read More
Preparing a Library Log in to your PLCnext Store account and create a new Library. To create a new Library, go to the “Software Products” tab on your profile and click the Create button. In the submenu that opens, select “Library”. A new page opens. On this page you have to describe… Read More
Building a library Programming guideline When building a library, you must observe and implement the minimum requirementsto ensure an adequate level of quality. Testing After you have finished your library, you need to run some tests. • Published/reviewed: 2025-08-26 • Revision 21 • … Read More
Publishing a Library General information The library and all documents are published as *.zip files. The *.zip file must contain at least the following files: English documentation (*.pdf) PLCnext Engineer library file (*.pcwlx) Refer to the topic Documentation (PDF and CHM) for important notes on documenting… Read More
