How the versioning of PLC projects should be carried out? A customer is currently using GIT for this and would like to continue doing so. But I couldn't find any support in the IDE.
I also did not find any source files for the POUs in the project directory. TwinCAT saves POUs in its own XML format, which is not ideal, but at least offers the possibility of viewing the code. For us it is important to be able to see the source code for commit, rebase and merges and also for the code reviews that we do as soon as a merge request of a branch has been created on GitLab. Furthermore, we have some scripts to be able to read the source code, as these extract data from our library for later building projects.
Currently there are plannings at CoDeSys to create a git package for all the engineering software. I hope there will something available for ctrlX Engineering until end of this year.
did you also purchase a license from Codesys or just the extension package?
The feature is not for free.
On my PC it is working with the version ctrlX WORKS 1.10 and a license.
Yes. this is the correct (test-) license.
I have ordered the 1 year license and it works at my system (RM 21.07, git package 22.214.171.124, license at a dongle but the softcontainer should work too)
If you have problems with the test-license please contact the CODESYS support.
I purchased this license and ran it in the previous version of the PLC application but updated to the latest version of PLC this morning and it no longer appears to be availble. Was this removed or am I missing something?
did you already install package again?
You can get it here and install it via the package manager.
(Click on Versions to get the latest 126.96.36.199, seems the "download" button gives you the older one.
I have the latest CtrlX PLC 1.12.1 installed and need to install this codesys developer license. i can not find where to enter the license code (ticket). License manager is not showing under tools.
any help will be appreciate it.
in ctrlX PLC 01V12 selected CODESYS are avaialable via the ctrlX App Zone using the Rexroth licensing.
Therefore the CODESYS licensing is no more available by default.
It is planned to provide version control with CODESYS Professional also via ctrlX App Zone in the future.
Because this is not yet implemented, we will directly contact you to show you how to activate the CODESYS license as an intermediate solution.
When will the integrated revisioning be available? Is it intended to be sold as a single license? The codesys developer license has extra items that aren't as useful but still carry a high price tag.
It will be available middle of this year (2022 :-)) at the ctrlX app store.
An it will be the same (Codesys professional) license.
"Because this is not yet implemented, we will directly contact you to show you how to activate the CODESYS license as an intermediate solution."
I also would like the solution for temporary licensing.
for further information how to activate CoDeSys licensing for engineering tools within ctrlX PLC Engineering see attachment .
I installed the "CODESYS Git 188.8.131.52.package" in "ctrlX PLC Engineering v1.14.1".
I purchased a test license from CODESYS as well.
After installing the package I get following error when trying to open ctrlX PLC Engineering --> see attachment
As a result I'm no longer able to run/open ctrlX PLC Engineering.
How to proceed to install the license?
I assume ctrlX PLC Engineering is needed to install the license via "License Manager"?
Is there a work around?
@Novice1, once I had this error I had to run a repair on the installation and you must install the license before installing the package. I also was never able to get 184.108.40.206 to run, only 220.127.116.11. I am attaching that package here (unzip it).
I hope this gets better integration because it is an awesome tool!
Unfortunately this is a bug in CODESYS.
The solution recommended by CODESYS GmbH is to purchase a CODESYS license dongle: https://store.codesys.com/de/codesys-key.html
I have installed Git with the trail licence in my virtual machine. In here it is working correctly. WORKS version 1.16 & SVN 18.104.22.168.
When i try to install exactly the same package in my Host device ill get the following error?
What might cause this enequility?