-
Ensure the bug was not already reported by searching on GitHub under Issues.
-
If you're unable to find an open issue addressing the problem, open a new one. Be sure to include a title and clear description, as much relevant information as possible, and a code sample or a clear explanation demonstrating the expected behavior that is not occurring.
-
Make sure there is a Github issue for the patch you are writing.
-
Open a new GitHub pull request with the patch.
-
Ensure the PR description clearly describes the problem and solution. Include the relevant issue number.
In case your specific project differs to much from the reference project in this repository, use the PLCopen XML to export the specific artifacts including the fix and paste them in the relevant Github issue.
-
Suggest your change/feature in the Gitter chat and start writing code.
-
Do not open an issue on GitHub until you have collected positive feedback about the change. GitHub issues are primarily intended for bug reports, fixes and milestone tracking.
- Ask any question about how to use the source code in the Gitter chat.
- Create own fork (if you not already did)
- Don't change the default
.ecp
for your own config - Optional: Create branch
- Code
- Prepare for export, see below.
- Add documentation in the markdown files.
- Create merge/pull request from your repo to this.
An export contains .export
and .xml
for people to update. The .ecp
is upgraded to the new changes, so its a basic version for newcomers.
-
Save file the
.ecp
- Make sure the original ecp is unmodified
- Save with another name.
-
Run export (from your modified ecp)
-
Export all files except configs
So no
*variables
,PRG's
andPersistenceVars
-
You can export Variables/Library if you see fit
- Codesys v3 >>> Exports\PLCopen.xml
- PLCopen XML >>> Exports\CodesysV3.export
-
-
Open the original
.ecp
. Keep your config out.-
Follow this guide to update your blocks
-
Add 1 example of the new function block/methods to the POU
-
Document the new function block/methods in the POU!
-