ContentHub
EdgeComp_COESYS_Lizenzen_Advanced-16072026_916_EN.mp4
10 views
View transcript
Hello, in this WAGO tutorial, we’ll show you how to provide licences for a virtual CODESYS Runtime on an Edge Computer via a licence server on the network. Since the virtual CODESYS Runtime runs inside a Docker container, the licences are always network licences. This also applies when the licence is activated directly on the Edge Computer using the CODESYS WBM. For this reason, the CODESYS License Server SL add-on is always required. The add-on does not run inside the Runtime’s Docker container; instead, it runs natively on the Edge Computer and provides the licence to the Runtime in Docker as a network licence. This offers a significant advantage: the licence can also be made temporarily available to other instances on the network, provided it is not currently in use. Licence management is handled by the CodeMeter software provided by WIBU-Systems. For this demonstration, we will use a simple example: an Edge Computer with a virtual CODESYS Runtime that we want to license using a USB dongle connected to a workstation PC. To do this, we first need to enable our workstation PC to act as a licence server. WIBU-Systems provides a tool for this purpose called CodeMeter Control Center. A link can be found in the video description. Install the software on the workstation PC and open it. Once the USB dongle containing the CODESYS licence is connected to the workstation PC, it will usually be detected automatically. Issues can occasionally occur when using USB hubs, so it is recommended to connect the dongle directly to a USB port on the PC. Use the button at the bottom to open the WebAdmin interface in your browser. Under the Configuration tab, navigate to Server and then Server Access. Enable the Network Server option and apply the changes. Your workstation PC is now fully operational as a licence server. Next, we need to tell the Runtime on the Edge Computer where the licence server is located. This is configured in the CODESYS Development System using the Deploy Control SL tool, which is where virtual runtimes are installed, managed, and configured. In previous tutorials, we already installed a Runtime, and for this demonstration we have extended it with a visualisation so that a larger licence package is required later on. We establish a connection to the Edge Computer and switch to the Operation menu to access the Runtime settings. For our Runtime, VPLC 1, we specified the Edge Computer’s own IP address in the License Server field during the Runtime installation tutorial. This is where the major advantage of network licences becomes apparent. Since all licences are network licences, we can simply replace that entry with the IP address of our workstation PC, save the settings, and we’re done. No further configuration is required. If we now connect to the Runtime via the Device tab, log in, and start the application, the log will confirm that the Runtime has been licensed successfully. In the visualisation, the integer variable increments whenever the button is pressed. If we now switch to the CodeMeter Licence Monitor, we can see in detail which licence components are currently in use by the Runtime and which are still available. When the Runtime is stopped, the licence is released again, which is immediately reflected in the updated Licence Monitor. The CodeMeter service therefore handles the complete licence management process. Monitoring is possible through the WebAdmin interface, which can be accessed on the workstation PC via port 22352. If the Edge Computer itself acts as the licence server, the WebAdmin interface, including the Licence Monitor, can also be accessed there. When the CODESYS License Server for Linux SL plug-in is installed, the CodeMeter software is installed automatically and takes over licence management out of the box. In this case, the WebAdmin interface and the Licence Monitor are also available via port twentytwo three fiftytwo, but using the IP address of the Edge Computer. For the WebAdmin interface to be accessible on the Edge Computer, two parameters must be configured in the CodeMeter settings. These can be modified through the Linux terminal, for example via the Edge Computer’s Web-Based Management interface. First, stop the CodeMeter service. Then open the Server.ini file. Under the General section, the parameter IsNetworkServer=1 must be set. In the Http section, the parameter RemoteRead=2 must be configured. Press Ctrl+O to save the changes and Ctrl+X to exit the file. Afterwards, restart the CodeMeter service. You can then verify its status to confirm that CodeMeter is running again. At this point, the Licence Monitor is also accessible from the Edge Computer. These parameter changes are only required if you want the WIBU WebAdmin interface to be available directly from the Edge Computer. The licence handling itself works out of the box without any additional configuration. At first, however, the Licence Monitor will not display any licences. The available licences only appear once the USB dongle is connected to the Edge Computer. Licence monitoring always takes place on the system that hosts the licence server. What may seem confusing at this point is that all licences are displayed as available, while the log contains the entry “Licence lost” together with the remaining grace period. This behaviour is expected. The virtual Runtime runs inside Docker and therefore has no direct access to the Edge Computer’s USB ports. Only after we explicitly tell the virtual Runtime that the Edge Computer is acting as the licence server will the logs indicate successful licensing. The Licence Monitor will then also show the corresponding licence components as occupied. As a result, we could now simply equip another Edge Computer with a virtual CODESYS Runtime and configure this Edge Computer as its licence server. CodeMeter will then provide the available licences automatically. Since these are network licences, it makes no difference whether the licences are stored on a USB dongle or inside a software container on the Edge Computer. This brings us to the end of the tutorial on providing licences for a virtual CODESYS Runtime over a network. If you found this video helpful, please give it a thumbs up, subscribe to the channel, and contact the WAGO Support Center if you have any further questions.