PLCnext Technology from Phoenix Contact is a unique, open ecosystem for modern automation that is capable of meeting all the challenges of the IoT world.
Find the right webinar for you, view tutorials, take advantage of our presence on GitHub, or get the info you need in our detailed documentation
Find user stories and applications of interesting ideas and solutions - Or add your own experiences
Publishing apps and libraries App types in the PLCnext Store In the PLCnext Store you can publish different types of software in the form of an app. Currently, six app types are available in the PLCnext Store: App Desktop Tool Library License PLCnext Engineer Project Solution … Read More
Documentation As a part of the app publication the contributor has to provide documentation in English language for the app. Description (promotional) The contributor has to provide a short description (app detail page > detailed description) for the app. The description includes: The purpose of… Read More
Building a Solution App 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… Read More
Preparing a Solution App Create an AXC F 2152 program in PLCnext Engineer. Note: If you want to publish your Solution App with a chargeable license, insert the function block LICENSE_STATUS from the “PLCnext Controller” library into your PLCnext Engineer program. Log in to your PLCnext Store account and create a new Solution App. To… 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
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
Overview creating a Library Program your library. Please follow our recommendations for good programming. If you want to sell your library, extend your function blocks with our license mechanism. Please test your library for a positive user experience. Create documentation for your library so… Read More
Publishing a Solution App Go back to the PLCnext Store. Go to Account → Software Products. Open the “Drafted” drop-down menu. Click the Action button next to your Solution App. In the submenu that opens, click the Edit button. You are now back in edit mode. Fill in the… Read More
Preparing a Library Create a Library in PLCnext Engineer. Note: If you want to publish your Library with a chargeable license, insert the function block LICENSE_STATUS from the “PLCnext Controller” library into your PLCnext Engineer program. Log in to your PLCnext Store account and create a new Library. To create a new Library, go to… 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
