This is my archive

Documentation

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

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

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

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

Creating a changelog 

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

Publishing apps and libraries

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

Preparing a Library 

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) 

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 

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 

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