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

Post by alexgooi on Codesys virtual control redundancy ^{CODESYS Forge talk (Post)}
Dear Forum, I’m currently investigating the possibilities of Codesys virtual control (Linux). The research rig consists of a PC (Debian with real time kernel) with a docker server installed on it. The PC is communicating with a Remote I/O and I have to say the performance is great. The process in the container is running (soft) real time. Currently I’m checking if it is possible to replace physical controllers by remote I/O’s and run the Codesys applications on a docker server. If I’m going into this route the reliability of the server is very important (server down, complete installation down), is it possible to make the server redundant without needing 2 separate containers (including licenses), and maintaining the real time behavior? I’m not only expecting direct answers, if you have any idea or thought they are very welcome. Kind regards Alex
Last updated: 2025-09-03

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

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

Post by taywinkel on Virtual Runtime CSV Utility Error ^{CODESYS Forge talk (Post)}
Hello, I am having trouble figuring out the proper location for my virtual runtime to create a .CSV file. No matter the file location I set, I get error 14 (CANNOT_OPEN_DIRECTORY). I have tried multiple different file paths ('/', '/var/opt/codesysvcontrol/PlcLogic', '/var/opt/codesys/'). I understand that there is only certain places that Codesys can read/write. I am also running this virtual runtime in a Podman container. Does anyone know what the location should be? I attached the archive I was using, a project that tests CSV capability that I borrowed from someone else. Thanks!
Last updated: 2025-09-03

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

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

Post by aseitzinger on CODESYS Control for Linux SL on virtual machine? ^{CODESYS Forge talk (Post)}
Hello, there in different information available regarding the possibility to run CODESYS Control for Linux SL on a virtual machine. https://forge.codesys.com/trg/linux-sl/home/Home/ says CODESYS Control for Linux SL is a runtime system, which can run on any Debian based X86 PC, VM or Cloud container... https://store.codesys.com/media/n98_media_assets/files/2302000005/3/CODESYS%20Control%20for%20Linux%20SL_de.pdf says CODESYS Control for Linux SL can not be used on virtual hardware Currently I run the package mentioned on a virtualized debian machine running in PROXMOX Virtual Environment 7.4-17 and apart from huge jitter it runs without problems. The CODESYS key is passed as a USB defice to the VM. I wonder why there are different statements regarding the suitability in virtual machines and if the jitter would be reduced by installing CODESYS runtime on the host installing CDS runtime on the host and using a preemptive kernel (if available for the PROXMOX installation leaving CDS runtime where it is (on the virtualized debian machine) and install a preemptive kernel on the host and on the guest... Any advice is appreciated. Greets Arno
Last updated: 2024-01-08

CoDeSys Implementation ^{CODESYS Forge talk (Thread)}
CoDeSys Implementation
Last updated: 2014-04-15

CoDeSys 2.3 Fonts ^{CODESYS Forge talk (Thread)}
CoDeSys 2.3 Fonts
Last updated: 2012-07-09

CoDeSys exercises ^{CODESYS Forge talk (Thread)}
CoDeSys exercises
Last updated: 2012-06-07

Email In CoDeSys ^{CODESYS Forge talk (Thread)}
Email In CoDeSys
Last updated: 2011-08-16

Codesys version 2.3.9.10 ^{CODESYS Forge talk (Thread)}
Codesys version 2.3.9.10
Last updated: 2009-03-23

CoDeSys to access ^{CODESYS Forge talk (Thread)}
CoDeSys to access
Last updated: 2007-01-15

CoDeSys Online ^{CODESYS Forge talk (Thread)}
CoDeSys Online
Last updated: 2006-07-10

Codesys Programming Help ^{CODESYS Forge talk (Thread)}
Codesys Programming Help
Last updated: 2011-02-23

Internal CodeSys Library ^{CODESYS Forge talk (Thread)}
Internal CodeSys Library
Last updated: 2009-03-01

CANopen and CoDeSys ^{CODESYS Forge talk (Thread)}
CANopen and CoDeSys
Last updated: 2012-11-21

codesys price strucuture ^{CODESYS Forge talk (Thread)}
codesys price strucuture
Last updated: 2013-03-08

Codesys Examples ^{CODESYS Forge talk (Thread)}
Codesys Examples
Last updated: 2009-03-19

Codesys Rpi sensors! ^{CODESYS Forge talk (Thread)}
Codesys Rpi sensors!
Last updated: 2021-05-18

Sort by relevance or date