This is my archive
Creating a changelog Create a changelog (*.md, *.txt or *.pdf) to allow users of your app to more quickly and easily track changes between versions. There is no standardized changelog format, but Phoenix Contact recommends to use the information provided by the project Keep a Changelog as a guide (as… Read More
Preparing a PLCnext Control Solution Make sure that your PLCnext Control Solution is already executable on your PLCnext Control. 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… Read More
Publishing a PLCnext Control 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 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