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
Publishing a solution 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. In the submenu that opens, click the Edit button. You are now back in edit mode. Fill in the remaining fields… Read More
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 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 solution Program your solution. Prepare your solution in the PLCnext Store. Build your app file. Create documentation for your solution so that everyone can use it easily. Every professional app has documentation! Publish your solution in the PLCnext Store and spark your users. Read More
Preparing a solution Create an AXC F 2152 program in PLCnext Engineer. Note: If you want to publish your solution 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. To create a new… 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
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
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
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
