Hello there. Im busy implementing this on a SBC we want to mass produce and this makes it quite a bit easier. However how can I buy a license. I see on the Docker container itself when I log into it there is a process for the soft container (CodeMeterLin) but when I go into codesys and go to license manager it tells me Licensing info not available. There is no dongle attached to the device.
Hi, to license Virtual Control, you always need network licenses. CODESYS licenses are bound to the hardware, which is not accessible in a container. Therefore, a network license server is required to provide the licenses for CODESYS Virtual Control instances: content.helpme-codesys.com/en/CODESYS%20Control/_rtsl_license_controller.html#UUID-53f421ed-1a14-45c3-9ab9-72e9a694ef91_section-idm234367072936383
@@Codesys-AutomationSoftware Thank you! That makes a lot of sense. To confirm my understanding: if we have a standalone device, we can run the network license server directly on that device. This server will then manage and provide the necessary licenses to the running containers within their respective Docker environments. Is that correct? We mostly do Off highway machinery so in our case it would mostly be standalone devices without an 'actual' device that can host the server.
@@danilleverster5187 Yes, that's how it works. You can try it on a Raspberry Pi without needing to buy a license. The license to operate the CODESYS Control product is located on a device in the network. That can be the LinuxPLC itself. Multiple (virtual) controllers can contact this central device/hostplatform to obtain a CODESYS license.
Hi, depends on where you want to login. The login data for your host device is defined when installing the Linux distribution, you need the username and password of your linux user. The login credentials for you virtual control instance must be defined on your first login.
This is so exciting! Thank you for the informative video
Hello there. Im busy implementing this on a SBC we want to mass produce and this makes it quite a bit easier. However how can I buy a license.
I see on the Docker container itself when I log into it there is a process for the soft container (CodeMeterLin) but when I go into codesys and go to license manager it tells me Licensing info not available. There is no dongle attached to the device.
Hi,
to license Virtual Control, you always need network licenses. CODESYS licenses are bound to the hardware, which is not accessible in a container. Therefore, a network license server is required to provide the licenses for CODESYS Virtual Control instances: content.helpme-codesys.com/en/CODESYS%20Control/_rtsl_license_controller.html#UUID-53f421ed-1a14-45c3-9ab9-72e9a694ef91_section-idm234367072936383
@@Codesys-AutomationSoftware Thank you! That makes a lot of sense. To confirm my understanding: if we have a standalone device, we can run the network license server directly on that device. This server will then manage and provide the necessary licenses to the running containers within their respective Docker environments. Is that correct? We mostly do Off highway machinery so in our case it would mostly be standalone devices without an 'actual' device that can host the server.
@@danilleverster5187 Yes, that's how it works. You can try it on a Raspberry Pi without needing to buy a license. The license to operate the CODESYS Control product is located on a device in the network. That can be the LinuxPLC itself. Multiple (virtual) controllers can contact this central device/hostplatform to obtain a CODESYS license.
Where can I get login and password?
Hi, depends on where you want to login. The login data for your host device is defined when installing the Linux distribution, you need the username and password of your linux user. The login credentials for you virtual control instance must be defined on your first login.
@ exactly, thx