Licensing info not available.

2025-10-02T15:21:21.800000Z

Thank you all,

The license is working now!!

Licensing info not available.

2025-10-02T11:36:07.999000Z

Dear Tim,

This is the missing link for me. I was not aware of the fact that the docker container is claiming the smallest possible license. Now the serial number makes much more sense. Thank you

Licensing info not available.

2025-10-02T11:29:57.171000Z

In the VPLC configuration settings there is an entry for the IP address of the license server. In this setting fill in the IP address of your device (host IP address). Then when the virtual PLC starts up, it will get the license from the license container on the host. You can do this for all VPLC's running on your device. The VPLC will always take the smallest license which fits the required license. So if you have 2 licenses for VPLC's with small and large applications, then this will work fine if you start up one VPLC which requires the small license and the other which requires the large license.

PS, personally I find it much easier, especially for testing and experimenting, to activate the licenses on a CODESYS (USB) key. This is easy to activate (on your development PC) and easier to move to another device. Addtionally you don't loose the license when you need to install a completely new image on the device.

Licensing info not available.

2025-10-02T06:59:13.393000Z

Thank you for the response,

The empty softcontainer does not become visible unfortunately, but I think I can get that back to working.

I think I'm misunderstanding something. You are pointing to the Softcontainer number and the ticket code, I thought that I needed to fill in the virtual control containers serial code is this a misunderstanding?

And if this is indeed the case, how is the link between the server (softcontainer) and the Codesys control docker container made? If I have multiple Codesys docker containers running on the same docker server, how is the correct license distributed to the correct Codesys runtime container?

Licensing info not available.

2025-10-01T17:44:35.490000Z

the procedure is usually
1. install the Licenserver (on the host)
2. if you go to the WBM you should see an empty Softcontainer 130-xxxxxx
3. activate the license with SoftContainer number and ticketnumber

that was it!

Licensing info not available.

2025-10-01T12:13:59.890000Z

Sorry for the question, but I'm not completely getting the idea here, could you be more specific, maybe give an example?

Licensing info not available.

2025-10-01T12:02:13.997000Z

add the Container serial number this is usually 130-xxxxxxxx and last row the license ticketnumber which you got from the CODESYS Store order

Licensing info not available.

2025-10-01T07:47:19.223000Z

Thank you for your quick response,

I have updated to the 4.17.0 (Virtual control and the license server).

Now I am able to see the softcontainer from the Codesys IDE.
But when I want to activate the license I get the following message:
Licensing info not available. The device does not support this service (See picture).

I then tried to active it via the WBM service like you suggested.
But when I try this is get an error (see picture for error).
I also tried to put RTS- in front of the serial number, but when I try this I get an error that the serial number is not correct.

I think I'm getting closer, but I'm not there yet.

Licensing info not available.

2025-09-30T19:07:08.485000Z

yes and no ... if you run the license server on the host (to serve licenses to the docker instances / vplcs then there is no runtime which could check the licenses on the host.
Therefore you need the CODESYS WBM to activate or check the licenes or you could use in CODESYS IDE the licensemanager ( not the one for the device licenses) but you have the the IP of the license server that he know where to search for the licenses ..tool options i guess to add it, will add a screenshot later.

Licensing info not available.

2025-09-30T06:30:44.671000Z

Dear Eschwellinger,

Thank you for the response.

Does that mean that the license-manager inside the Codesys-IDE does not work with this setup anymore?
Because when I use this I get the notification that there is no dongle attached to the device (see picture).

And If I insert the license by the deploy tool, can I then redeploy the Codesys virtual control container, or does this erase the license completely?

Recent posts to Licensing info not available.

Licensing info not available.

Licensing info not available.

Licensing info not available.

Licensing info not available.

Licensing info not available.

Licensing info not available.

Licensing info not available.

Licensing info not available.

Licensing info not available.

Licensing info not available.