Codesys Activate License

[Curtis Cassel]

Weare having problems with licensing PFC100 controller.

We are using WAGO PFC100 (750-8101) in one of our machines and for some reason it seems that we are not able to activate license on this controller.

I haven't tested the solution yet, but it might do the trick, we are running the system from SD card also. In our case the SD image was completely blank before we downloaded the application and tried to do the licensing. It might still be, that the soft container in the SD card is somehow corrupted or faulty?!

Hi, i have a similar problem. im using pfc200 4.5.0.0.

There are two softcontainer and only one with license in it. every 1-2 hrs it will auto logoff. i tried the steps above but i dont find the /var/opt/codesys/.cmact_licenses

The download button starts an automatic download of all software packages via the browser. To enable this, the browser must be configured to accept an automatic download. The individual packages can also be downloaded from the detailed pages of the individual components of the CODESYS Professional Developer Edition.

The subscription model for the CODESYS Professional Developer Edition is a cost-effective introduction to professional application optimization. With little effort, the toolchain can be tested for your benefit or a cost-effective application in the project can be achieved.

Licenses are activated on a software-based license container (soft container), which is permanently connected to the workstation. Alternatively the license can be stored on a CODESYS Key (USB-Dongle). By replugging the CODESYS Key, the license can be used on any other workstation.

This product includes a free addition to an otherwise paid support entitlement of one hour of support. The redemption must be made within 1 Year(s) from the date of purchase. After this time, the support entitlement expires.

To submit such a technical support request after purchase, a CODESYS Store account is required. After logging in, please use the "My Support Authorizations" list in your account or use the "My Question" contact form. After you have described and submitted your problem, the message will be forwarded to our technical support. They will contact you immediately to determine the next steps.

For general error messages or pre-sales inquiries, please also use the "My Question" contact form and select the appropriate department. This type of request can be used without logging in. A list of alternative support options can be found in the support section of the CODESYS Group website.

The instructions you posted are similar to those under the heading with the words "windows runtime" _cds_installing_license;product=codesys;version=3.5.16.0#id8 . Are you trying to run Windows 10 IoT core on your pi? I think CODESYS Control for Raspberry Pi MC SL is only possible with a Linux OS, like Ubuntu or Raspberry Pi OS.

I get to the point where I scan the network and I get nothing. I try to add a device and this doesn't work either. My Raspbery Pi is on a wireless network and different subnet. I can connect to in an was able to install the control. I see codesys running on the pi but I am unable to license it.

install current version of the PI Package 4.0.1.0 there is the Gateway included ( on runtime install), add the new Gateway in CODESYS ( IP Address of your PI) and use the Gateway in the PI

to do it. ( scan your PI by this new added Gateway)

The issue is that, all Controller's computer's came from the the same disk image, cloned from a reference PC, and I forgot to remove the existing container, and now it appears as being 2 runtime activated at the same computer.

...yet another question: How to remove an existing container from PC ? Once each license will be installed at PC's whose whole system were cloned from a unique template CloneZilla's file, there we can see a container which I presume should be deleted before installing/activating the just purchased license - a step that I didn't at the above mentioned case.

Using OS Images on Windows from installed ipc's , need the step

- "removing the license container & add a new empty before you activate the license.

We will add a description / how to - to the FAQ section.

It is nice to hear that this licence in particular was not lost at all, we've purchased the exact amount for the current need. And, I'm happy to know that there will be added the required steps on the online help.

My 2 cents: I have been trying to follow steps on the online help regarding distinct procedures, and many suffice for our needs, but some of them do not cover in detail, so I would suggest adding Videos at least to the most critical steps. I'm new on Codesys.

Alternately, just to make things simplest:

After succesfull removal of the invalid container, would suffice re-install "CODESYS Control Win 64 3.5.15.30.exe" on the Controler's side (since it is the one where are wrong license ) ?

By doing a re-install worked fine, a new (empty) container appeared at 'CodeMeter' viewer and the "License Manager" recognized it, being able to install there one license there; after all, 'CodeMeter' show up a valid license stored at this container.

most important information are missing:

Which CODESYS Version?

Which runtime version?

Which plc type (manufacturere)..

Not all plc manufacturer already support application based licenses.

From your pictures I see you have activated 4 axis Motion (which is an applications based license type)

does only work on plc's which do support this.

16.4 Epis What has it to do with the manufacture? It just a licence more not. So basicly the idee of codesys sucks. 3s acts like its posible to add a license. And then it depence on the manufacturer. Why ?? Its a computer !! has nothing to do with the manufacturer. Most dont what a basic licence because they have to pay for that. 3s is the problem not the manufacture of the hardware. Its like the licence of the raspberry pi. HMI is not working. Sorry you get a refund. Why suggest that its possible wen its not !!. It cost me a lot of time. Who pays my time. Why do i have to pay for somting thats not working.

I just try to help.

Anyway it is a big difference if a Store SL runtime or an oem plc and licence is used. These licenses need to be activated on plc side - so you have dependencies to the version (CODESYS and Runtime Version) Did you ever ask Epis out for this situation? They should know which license fit to their device. Even they should know if the device is capable for Softmotion and see the requiremnts in the CODESYS store: Runtime 4.9.0.0 - how should this work with Epis 3.5.16.x? Anyway refund is not a problem.

Epis doesnt want Softmotion. I thought it was about the price. If it was possible it would be working already and i dont need an extra licence. Thats the problem of codesys. The software is running but hangs on its license. Epis made it posible to see the stick. I can see the license. Softmotion is there from 3.5.14.Xx Like is said And Motion control is alrady posible 15 year ago. And i only need a Sync of 2 drives. I want a good solution not a refund. Dont point to the manufacturer. The software is made by 3s not by epis .

What we are trying to explain is that, yes CODESYS creates the software, but Epis decides how they implement it on their hardware, which runtime version they use and they decide which functionality they support.

What CODESYS provides is a runtime with options for e.g. visualization or softmotion. Epis could add this softmotion license as default to their controller, but if they don't then CODESYS provides another option with a single license in a "Wibu CodeMeter" container.

Then finally it depends on what type of runtime is on this controller and which license Epis is using. So if they have an OEM license (not an application based license), then most likely you will need the Softmotion license (not a number of axis). See -softmotion-sl-bundle.html.

The hole setup is made by 3s. So its a comination of one not two. If Epis decide not to support extra licence whats then the funtion of providing an option with a single license ?? So the idee by 3s has a flod. Epis change the system to add the Stick. I send controller inc stick to Epis. On my software i can see the stick. An then you tel me i need a other license to use an license ?? Makes completly no sense. Codesys should be flexible but is not. I tried Delta. But has no HMI and has its own Codesys ?? Why ?? Then i tried Crist. The block there own system by a password. But dont know the password and cant switch it off. At the end the want me to pay for support to solve ther own made problem. So i send it al back. The extra license is adviced by 3s . Now a few month later still no working solution.

Hi everyone,

I would like to control two IO-Link grippers via a ctrlX. Since a missing license has led to an exception error when uploading my PLC project I have purchased the "CODESYS IO-Link SL" after consultation with the support as these are not yet available from Rexroth (Link to the Topic).

However, it is not clear to me whether I have activated the license correctly. To store the Codesys license in PLC Engineering I followed the instructions Quick start guide: How to enable CoDeSys licensing using ctrlX PLC Engineering. With this guide I was able to add my license to the license repository:

Afterwards the project could be transferred without error and the grippers could be controlled. However, the IO Link connection to the grippers breaks off again after about 10 minutes. The only error message I receive is from the gripper instances in PLC enginnering itself with the message "Module reports and Error".

I suspect that the license has not been activated correctly as Codesys also states that the license must either be loaded onto a dongle or installed on a SoftContainer on the controller via the license manager (Codesys - Licensing of Products) .

The red X in the license repository also indicates the message "The license for the product does not exist in the selected license container".

3a8082e126