Post by yannickasselin on The selected container ... does not fit your ticket ^{CODESYS Forge talk (Post)}
Not sure this will help you but I had the same issue and was able to activate the license on a Windows PC using the Web Depot in a web browser. https://content.helpme-codesys.com/en/CODESYS%20Development%20System/_cds_installing_license.html
Last updated: 2025-01-08

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 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 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 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 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 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 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 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 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 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

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 rossanoparis on Upgrading CODESYS runtime from v4.7 to v4.9 using a bash script leads to lose the licences stored in the soft container ^{CODESYS Forge talk (Post)}
System information - Controller: KUNBUS RevPi CONNECT-S - OS: Linux buster 32bit 5.10.103-rt62-v7l #1 SMP PREEMPT_RT armv7l GNU/Linux - CODESYS v3.5 SP19 Patch 2 I'm facing a problem related to codesys licences using a procedure based on a bash script. Such bash script detect the presence of new .deb files and install them on system. My automation solution don't allow to be maintained by dedicated personal, thus even the CODESYS runtime SW must be installed using an "automatic" procedure instead of using the CODESYS tool. remark I've been using the following procedure since the runtime v4.5 without any issue. Before installing the new runtime packages, I need to copy the file CODESYSControl_User.cfg (here attached) because of new section which is necessary to add in order to allow some folders to be written by CODESYS runtime v4.9 Up to now, this has been unnecessary, this is the main difference between my previos bash file and the new one. remark If I skip this action, everythings goes fine, but my CODESYS application can't work as it needs to access some folders on controller's file system. Process - Before the procedure: the licenses are OK (see attached file lic-01.png) - After the procedure: the new CODESYS runtime version is correctly installed, but the software container with v1.19 and all licences disappear (see attached file lic-02.png) This is the synthetic content of bash script I'm using. # Stop runtime sudo service codesyscontrol stop sudo service codesysedge stop # Move the new CODESYSControl_User.cfg file # New configuraton with folders declared sudo mv -f CODESYSControl_User.cfg /etc # Install runtime package echo N | sudo apt-get install -y --allow-downgrades codesyscontrol_raspberry_4.9.0.0_armhf.deb # Install edge gateway package echo N | sudo apt-get install -y --allow-downgrades codesysedge_edgearmhf_4.9.0.0_armhf.deb # Reboot controller sudo reboot Thanks in advance
Last updated: 2023-09-19

codesys-->opc ua-->codesys ^{CODESYS Forge talk (Thread)}
codesys-->opc ua-->codesys
Last updated: 2021-08-11

Post by wmoon on Licensing info not available. ^{CODESYS Forge talk (Post)}
Hello, I bought some licenses from CODESYS store. I am trying to install licenses into my device(CODESYS Control for Linux ARM64 SL). But I have a trouble with it. I did it in the following order. Tool -> License Manager Selected Device and Next... Selected Soft container and Next... Select the device and Ok.. And then I always show a message "Licensing info not available. There is no dongle attached to the device." And I tried to click "Install Licenses" button. I saw the message "The value cannot be NULL. Parameter name : continerToLicenses" Could you let me know what I've missed or what I've got wrong?
Last updated: 2024-03-19

Post by milosfejgl on Codesys Licenses - How to reload them after updating the Raspberry Pi OS ^{CODESYS Forge talk (Post)}
We use several control units running on Raspberry Pi, programmed using Codesys software, with multiple licenses stored as soft containers. We are planning to update the SD card image of the Raspberry Pi to a newer OS version. However, we are concerned that this process might result in the loss of our soft container licenses. Is there a way to temporarily deactivate the license so that it can be reactivated on the updated system? Alternatively, what would be the best method to preserve the licenses during the update? Thank you in advance for any responses!
Last updated: 2025-03-13

Post by pernockham on How to manage soft container licenses for (remote) multi units? ^{CODESYS Forge talk (Post)}
Using Codesys runtime for Linux and thinking of the process of preparing multiple such systems for my customer. I don't necessarily have physical access to these units, they can be (very) remote. The idea so far is to use an image to install the Linux OS and codesys runtime. Application updates can be done by distribution of the PlcLogic/Application/application.app and application.crc files. But whats the most practical way of managing the license for these units? Do each controller need to be physically connected to a License Manager instance or can licenses be distributed by means of a license file for each unit? I believe that the license should be stored in soft containers for each unit. Help and insights appreciated! Per
Last updated: 2025-04-04

CODESYS ^{CODESYS Forge talk (Thread)}
CODESYS
Last updated: 2017-03-07

Codesys ^{CODESYS Forge talk (Thread)}
Codesys
Last updated: 2024-01-14

codesys v3 2 codesys v2 ^{CODESYS Forge talk (Thread)}
codesys v3 2 codesys v2
Last updated: 2014-08-04

Post by superjojo2002 on Licensing info not available. ^{CODESYS Forge talk (Post)}
I recognized that I have to start the two services "/etc/init.d/codemeter" and "/etc/init.d/codemeter-webadmin" in the docker container as well. If I do so, then the command "cmu -x" returns root@sensoredge-field-netfield-produktmanagment:/# 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. So this time there is no indication any more that "Codemeter is not running". But still we are getting the error when using the license manager in CODESYS development system.
Last updated: 2024-03-21

Sort by relevance or date