Post by eschwellinger on OPC Da Server Code Meter Issues after Enabling License ^{CODESYS Forge talk (Post)}
it is mandatory to activate the OPC DA license into the 32-xxxxxx legacy container (not UFC) you need a remove ticket -> contact CODESYS store - my question to move the license
Last updated: 2024-05-03

Post by rafaelbrito on Licensing info not available. ^{CODESYS Forge talk (Post)}
Hello, I'm having the same problem. I'm trying to license Codesys running in a Linux container, which I downloaded from the following link (https://hub.docker.com/r/hilschernetiotedge/codesys_control_sl_linux). The same error that you mentioned appears. Is there any solution?
Last updated: 2024-05-22

Post by paulpotat on Can't open license manager with raspberry CM4 ^{CODESYS Forge talk (Post)}
Hello, I have a problem when opening the license manager for my raspberry pi (CM4 model) with runtime 4.13.0.0. I select "Device" --> "Soft Container" and click on my device in the scan window but I get this error message : Licensing info not available. There is no dongle attached to this device. I can't install licenses anymore, and I don't understand why is CodeSys looking for a dongle when I specified I wanted to use a Soft Container. Can somebody help me please ? Best regards
Last updated: 2024-10-04

Post by superjojo2002 on Licensing info not available. ^{CODESYS Forge talk (Post)}
I checked it using the very same docker container version like colleague moon and the command returned root@nt0001c02c5533:/# cmu -x cmu - CodeMeter Universal Support Tool. Version 7.60c of 2023-Aug-09 (Build 5625) for Linux/ARMHF 64-Bit Copyright (C) 2007-2023 by WIBU-SYSTEMS AG. All rights reserved. Result: 0 CmContainer(s) listed. (CodeMeter not running) Please consider that we intend to license a codesys ARM64 SL in a docker container.
Last updated: 2024-03-20

Post by timvh on How to manage soft container licenses for (remote) multi units? ^{CODESYS Forge talk (Post)}
You need to activate an individual license (ticket number) for each device. THe hardware of each device is unique, so you cannot copy a soft container from one device to another. This license can be installed in a local (wibu - codemeter) soft container, or you could optionally activate it on a hardware (USB) key. The benefit of the key is that you can easily move it to another device, nor does it get lost when you replace parts of the hardware of the device or completely overwrite the image. See: https://store.codesys.com/en/codesys-key.html
Last updated: 2025-04-08

Post by davidbo on Toradex and CODESYS and licensing ^{CODESYS Forge talk (Post)}
I am evaluating a Toradex product for use with CODESYS. Toradex and CODESYS are partners, but using "CODESYS Virtual Control for Linux ARM64 SL" together with a carrier board "Verdin mallow" However it doesn't seem to be a soft container for licenses. So how do I install a license
Last updated: 2025-10-20

Post by navan on License Reset Request – CODESYS Control Win V3 Standard L ^{CODESYS Forge talk (Post)}
Dear CODESYS Support Team, My IPC hardware failed and was replaced. The CODESYS Control Win V3 Standard L license now shows “Activation Invalid” in CodeMeter Control Center. Please reset or reissue the license to my new IPC. Details: Product: CODESYS Control Win V3 Standard L 32 bit Version: 3.5.20.10 Ticket : Xxxx-xxxx-xxxx-KJE4 New Container ID: (130-......837) Thank you,
Last updated: 2025-10-23

Post by teichhei on The selected container ... does not fit your ticket ^{CODESYS Forge talk (Post)}
Update, installed 3.5.19.70 with the same result. The error message is as useful as a chocolate fire guard. The container SN is in the 130-xxx range which should work. The Version, Chip, Rev number don't mean anything to me. There is no SD Card installed. I've also reinstalled a fresh Wago FW22 image, Deployed PFC200 SL and Edge for Linux, still the same result.
Last updated: 2025-01-09

Post by paulpotat on Can't open license manager with raspberry CM4 ^{CODESYS Forge talk (Post)}
Update : The solution I mentionned in a previous post does not always work. Some Raspberry Pi CM4 still won't create the license container. I will open a support ticket.
Last updated: 2024-10-18

Post by eschwellinger on PFC200 Will soft-container & IIoT license survive a firmware update? ^{CODESYS Forge talk (Post)}
need to be relicensed. 27 FW has an Wago Runtime for V3. So maybe using this would be an option too.
Last updated: 2024-11-16

Post by teichhei on The selected container ... does not fit your ticket ^{CODESYS Forge talk (Post)}
Don't I need a browser on the device for web depot? Could work on the Pi but not the Wago controller. Maximum I have is SSH.
Last updated: 2025-01-08

Post by alexgooi on Licensing info not available. ^{CODESYS Forge talk (Post)}
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
Last updated: 2025-10-02

Post by reinier-geers on Add licence ^{CODESYS Forge talk (Post)}
Hi I want to add a licence. I dont have the dongle jet. I tried a Stick. I dont see a Container. My Controler deliverer Dont put a motion licencens because its to expensive. How can i add a licensens?
Last updated: 2023-12-28

Post by superjojo2002 on Licensing info not available. ^{CODESYS Forge talk (Post)}
If support for a containerized CODESYS runtime with a license isn't feasible, then I've considered an alternative approach: I've purchased and activated a "CODESYS Control Basic S" license on my Windows notebook, where I already have the Codemeter Control Center installed. Upon activation, I can see the CODESYS license as active on my notebook. Subsequently, I followed the instructions provided in this link (https://faq.codesys.com/display/CDSFAQ/How+to%3A+Setup+a+Wibu+Network+Server+Access+for+Licenses) to configure the Wibu runtime in the CODESYS container to access my external license server hosted on my notebook by editing the CODESYSControl_User.cfg file accordingly. However, it's worth noting that I'm still receiving a response from the Licensing Manager indicating that the runtime is persistently searching for a dongle instead of recognizing the soft container. So how can I get my runtime licensed now? Any ideas?
Last updated: 2024-03-20

Post by alexgooi on Licensing info not available. ^{CODESYS Forge talk (Post)}
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?
Last updated: 2025-10-02

Post by mdetrana on VPLCs Tab 'Grey-ed Out', Cannot Create VPLC ^{CODESYS Forge talk (Post)}
When evaluating Codesys functionality, I found that the VPLC tab under Deploy Control SL > Operation > VPLCs is 'grey-ed out', see attached image. I'm trying to evaluate how my infrastructure will interact with Codesys on a Raspberry Pi 4, so I'm trying to demo running it before purchasing licenses. I was going through the Codesys tutorial here, and it never shows the tab as grey, so I do not know how to proceed. Let me know if I can get any additional information that can help. This could be related to an Info message that's sent when connecting- [INFORMATION] Connected successfully! [INFORMATION] Successfully connected to target (<ip_address>) [INFORMATION] No supported container engine found on device. You have to install a supported container engine to use Virtual Control. Please contact the Administrator of the device. [INFORMATION] Finished reading device information</ip_address> I'm not exactly sure what I would need to do to install a 'supported container engine'.
Last updated: 2025-10-09

Post by alexgooi on Licensing info not available. ^{CODESYS Forge talk (Post)}
Dear Forum I have the following config: Codesys_IDE 3.5.20 Codesys_Virtual_Control 4.13 Codesys_License_Server 4.13 I know these are not the newest versions, but in my mind these should work. I have the same problem here. I have the license server installed on the host, and in the docker container(Codesys virtual control) I'm able to ping the license server. In the /conf/codesyscontrol/CODESYSControl_User.cfg I have added the following config: [CmpCodeMeter] EnableNetLicenses=1 LicenseServer.1="ip address of the host" I have tried it via the wbm web-page. I can create new license containers over there, but still no luck. I also have tried to run the docker container with the -s "server_IP" command. I have searched for some tutorial's but I couldn't find it. If anyone has some clue or can give me a push in the right direction it would be very very welcome!
Last updated: 2025-09-29

Post by smic on Virtual Control SL Profinet connection ^{CODESYS Forge talk (Post)}
Hi. I'm trying to connect Profinet device with Virtual Control for Linux SL. After adding devices, I couldn't find actual device by Scan Device? Do I missed something? VPLC container on Docker IP: 172.17.0.4 Subnet: 255.255.0.0 Gateway: 172.17.0.1 Profinet device: AL1100 io-link master (default setting) IP: 0.0.0.0 Subnet:0.0.0.0 Gateway:0.0.0.0
Last updated: 2025-02-28

Post by alexgooi on Licensing info not available. ^{CODESYS Forge talk (Post)}
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?
Last updated: 2025-09-30

Post by wollvieh on License Activation Problems ^{CODESYS Forge talk (Post)}
on a raspberry pi delete the folder and its content before licensing. /var/opt/codesys/cmactlicense If you plug this SD card in another raspi ( which has another hw-serial number) you'll get a second empty softcontainer. This could lead to an unlicensed PFC (it could only handle one container) The solution is: To delete the /var/opt/codesys/cmactlicense directory and content of it and then aktivate the lizenz via WibuCmRau file and Lizenzmanager.
Last updated: 2024-06-24

Post by superjojo2002 on Licensing info not available. ^{CODESYS Forge talk (Post)}
I updated the docker container runtime to version 4.11.0.0. and build the container with this "Dockerfile" FROM arm64v8/debian:11.6 RUN apt-get update RUN apt-get install -y wget sudo unzip libusb-1.0-0-dev procps ENV CDS_VERSION "4.11.0.0" ENV EDGE_VERSION "4.11.0.0" ENV URL "https://store-archive.codesys.com/ftp_download/3S/LinuxARM64/2302000039/$CDS_VERSION/CODESYS%20Control%20for%20Linux%20ARM64%20SL%20$CDS_VERSION.package" ENV EDGE_URL "https://store-archive.codesys.com/ftp_download/3S/EdgeGatewayLinux/000120/$EDGE_VERSION/CODESYS%20Edge%20Gateway%20for%20Linux%20$EDGE_VERSION.package" RUN wget --output-document=/tmp/codesys.package $URL && \ unzip -p /tmp/codesys.package '*codemeter*.deb' > /tmp/codemeter.deb && dpkg -i /tmp/codemeter.deb && \ unzip -p /tmp/codesys.package '*codesyscontrol*.deb' > /tmp/codesys.deb && dpkg -i /tmp/codesys.deb RUN wget --output-document=/tmp/edge.package $EDGE_URL && \ unzip -p /tmp/edge.package '*arm64.deb' > /tmp/edge.deb && dpkg -i /tmp/edge.deb EXPOSE 11740 1217 11743 ENTRYPOINT ["/bin/sh", "-c" , "/etc/init.d/codemeter start && /etc/init.d/codemeter-webadmin start && /etc/init.d/codesyscontrol start && /etc/init.d/codesysedge start && tail -f /dev/null"] Now cmu -x" returns root@sensoredge-field-netfield-produktmanagment:/# cmu -x cmu - CodeMeter Universal Support Tool. Version 8.00 of 2023-Nov-28 (Build 5967) for Linux/ARMHF 64-Bit Copyright (C) 2007-2023 by WIBU-SYSTEMS AG. All rights reserved. But still CODESYS development system reports that it needs a dongle and when I click install that "value cannot be null. Parameter name: containerToLicenses" It seems that Codemeter is forced to look for a dongle instead of a CMsoftcontainer. Can you confirm that CODESYS licensing works also when CODESYS is installed in a Docker container?
Last updated: 2024-03-21

Post by timvh on License problem gateway ^{CODESYS Forge talk (Post)}
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. So it is always a combination of the two. 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. Eventhough the feature exists, Epis has to add this "CodeMeter" software on their controller to be able to access the licenses in the container. We don't know if they did this. 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 https://store.codesys.com/en/codesys-softmotion-sl-bundle.html. But to be sure if this is supported by the Epis controller, you must ask Epis.
Last updated: 2024-04-30

Post by gunstr on CODESYS control on RPi starts, shortly runs, then exits ^{CODESYS Forge talk (Post)}
I now tried to install 4.17.0.0 on a fully clean installations: A brand new RPi 4B Install latest Raspberry Pi OS Lite, Release date 13 May 2025, 64bit run sudo apt update && sudo apt full-upgrade When asked - Select to install the updated version of '/etc/initramfs-tools/initramfs.conf' Install CODESYS Control for Raspberry Pi SL. version 4.17.0.0 Log output: [INFORMATION] Connected successfully! [INFORMATION] Successfully connected to target (192.168.0.197) [WARNING] No supported container engine found on device. You have to install a supported container engine to use Virtual Control. Please contact the Administrator of the device. [WARNING] Error detecting container architecture [INFORMATION] Finished reading device information [ERROR] Error output: /var/lib/dpkg/info/codesyscontrol.postinst: 88: check_legacy_extensionapi_folder: not found [INFORMATION] Standard output: Selecting previously unselected package codesyscontrol. [INFORMATION] Standard output: (Reading database ... 76772 files and directories currently installed.) [INFORMATION] Standard output: Preparing to unpack .../codesyscontrol_raspberry_4.17.0.0_all.deb ... [INFORMATION] Standard output: Unpacking codesyscontrol (4.17.0.0) ... [INFORMATION] Standard output: Setting up codesyscontrol (4.17.0.0) ... [INFORMATION] Standard output: make config rw [INFORMATION] Standard output: set folder permissions [INFORMATION] Standard output: prepare permissions [INFORMATION] Standard output: check legacy extension api folder [INFORMATION] Standard output: create and install daemon [INFORMATION] Standard output: codesyscontrol started [WARNING] Unable to detect Raspberry Pi Architecture. Setting armv6l as default, you can change this through the settings panel. [INFORMATION] Standard output: codesyscontrol stopped [ERROR] Expected exit value of command failed: expected 0, received 1 [WARNING] Error setting the Raspberry Pi Architecture [ERROR] Error installing codesyscontrol If I read the log correctly the control is actually installed but cannot start. I'm running out of ideas how to proceeed now, any suggestions are welcome.
Last updated: 2025-09-03

Post by s1ack on PFC200 Will soft-container & IIoT license survive a firmware update? ^{CODESYS Forge talk (Post)}
I have an IIoT License activated on a PFC200 with older firmware 2.08.32 (11). If I flash it to the latest available 4.05.10 (27) does the license get destroyed? I have a back up file '3SLicenseInfo.tar'. But this looks quite a bit different form the backup I got from more modern firmware... 'CMLicenseNew.WibuCmRaU'. Can the new license manager restore it from the old .tar?
Last updated: 2024-11-12

Post by jshirazi on Restore license on Raspberry Pi ^{CODESYS Forge talk (Post)}
Hi, I recently got a license for Raspberry Pi, after license activation I made a backup copy of "CMLicenseNew.WibuCmRaU" file to a safe place. Things got complicated and I tried to downgrade OS for some reason after that I tried several times/ways to restore my license with no luck. the specifications are as follows: Raspberry Pi 4 Model B Rev 1.1 codesyscontrol 4.10.0.0 SDK 3.5.19.30 Logs: **** ERROR: CodeMWriteLicenseFile: 'CMLicenseNew.WibuCmRaU' failed: Container not found or Server dose not support .... So if someone know a solution for this please kindly help me. Regards
Last updated: 2024-02-03

Sort by relevance or date