CODESYS Control for BeagleBone SL use shared library ^{CODESYS Forge talk (Thread)}
CODESYS Control for BeagleBone SL use shared library
Last updated: 2018-08-04

Codesys 4 Linux don't found Device with Control Linux SL ^{CODESYS Forge talk (Thread)}
Codesys 4 Linux don't found Device with Control Linux SL
Last updated: 2021-10-05

CODESYS Control RTE SL as a profinet Slave ^{CODESYS Forge talk (Thread)}
CODESYS Control RTE SL as a profinet Slave
Last updated: 2020-06-20

CODESYS Control for PFC100 SL und Wago DALI 750-647 ^{CODESYS Forge talk (Thread)}
CODESYS Control for PFC100 SL und Wago DALI 750-647
Last updated: 2023-02-12

SPI device (MCP3204) in CODESYS Control for BeagleBone SL ^{CODESYS Forge talk (Thread)}
SPI device (MCP3204) in CODESYS Control for BeagleBone SL
Last updated: 2021-04-01

CODESYS Control for Raspberry Pi MC SL ^{CODESYS Forge talk (Thread)}
CODESYS Control for Raspberry Pi MC SL
Last updated: 2018-12-19

CODESYS Control for Linux SL on virtual machine? ^{CODESYS Forge talk (Thread)}
CODESYS Control for Linux SL on virtual machine?
Last updated: 2024-01-08

Control for Linux SL on Ubuntu Core ^{CODESYS Forge talk (Thread)}
Control for Linux SL on Ubuntu Core
Last updated: 2024-03-04

CODESYS control for Raspberry Pi 64 SL errors ^{CODESYS Forge talk (Thread)}
CODESYS control for Raspberry Pi 64 SL errors
Last updated: 2024-05-03

How to adapt Codesys Control SL to custom board ^{CODESYS Forge talk (Thread)}
How to adapt Codesys Control SL to custom board
Last updated: 2024-08-09

Codesys Control for PLCnext SL, Bus not running ^{CODESYS Forge talk (Thread)}
Codesys Control for PLCnext SL, Bus not running
Last updated: 2024-08-12

Codesys Control for PLCnext SL, Bus not running ^{CODESYS Forge talk (Thread)}
Codesys Control for PLCnext SL, Bus not running
Last updated: 2024-08-12

Scan Network on gateway created with Control Sl ^{CODESYS Forge talk (Thread)}
Scan Network on gateway created with Control Sl
Last updated: 2024-10-23

Modbus TCP & RTU with Control for Linux SL ^{CODESYS Forge talk (Thread)}
Modbus TCP & RTU with Control for Linux SL
Last updated: 2024-10-24

Not Possible to connect using control SL ^{CODESYS Forge talk (Thread)}
Not Possible to connect using control SL
Last updated: 2025-01-10

CODESYS Control for PFC100 SL Firmware upgrade ^{CODESYS Forge talk (Thread)}
CODESYS Control for PFC100 SL Firmware upgrade
Last updated: 2025-02-27

GPIO mit Codesys Virtual Control for Linux ARM64 SL ^{CODESYS Forge talk (Thread)}
GPIO mit Codesys Virtual Control for Linux ARM64 SL
Last updated: 2025-03-17

Post by peter-skokanek on Raspberry and problem with runtime ^{CODESYS Forge talk (Post)}
Hi, Similar problem, I have license for Raspberrypi Control MC SL. It didn't work with version 4.10.0.0. I have now instaled new version 4.11.0.0. Raspberrypi Control SL. The same behavior, runtime works sometime several minutes, sometime only several seconds. The second problem is with license. There isn't available any runtime MC SL on Codesys shop, not even older version 4.10.0.0. Is it only temporarily or, MC SL will be not available more for rpi?
Last updated: 2024-02-27

Post by fmbrew-rob on Licensing info not available. ^{CODESYS Forge talk (Post)}
Was there ever any resolution to this? I am using Virtual Control SL on a ProxMox setup, and I can't get the license installed. I get the same errors reported above.
Last updated: 2024-09-21

Post by eschwellinger on Virtual Control SL Profinet connection ^{CODESYS Forge talk (Post)}
means not licensed demo mode.. use the Licenserver on the host and apply a license and add the Ip of the license server then it will be green.
Last updated: 2025-02-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 mani-i4point0 on Issue with WebVisu on Raspberry PI ^{CODESYS Forge talk (Post)}
Hi, Any insights highly appreciated. Was wondering , Is this issue related to License ? The License I have is 'Codesys Control for Raspberry PI MC SL' Or is this issue related to any Memory ? kindly refer to the attached images for the License and memory. Any suggestions highly appreciated. Regards, Mani
Last updated: 2024-04-10

Post by aliazzz on Unable to deploy Virtual Control SL on ARM64 (Raspberry Pi5) ^{CODESYS Forge talk (Post)}
Hi, I have successfully deployed "Virtual Control SL" on a few x86/64 machines now. However, I'd now like to deploy this to a Raspberry Pi (ARM64). To do this I prepared the Raspberry Pi5 with the following prereq's; * Minimal PREEMPT Debian * Latest Bootfirmware * full SSH access via non-root account * Podman * RedHat Cockpit with CODESYS LicensServer plugin up and running However, I can't seem to resolve copying the correct (deploy) Images as they wont show up in the CODESYS IDE I have added CODESYS Virtual Control for Linux SL and the CODESYS LicenseServer for Linux SL via the CODESYS installer on my DevBox. I open CODESYS > Tools > Deploy Control SL Next I enter the SSH targets IP and Credentials and for my RPi5 and it shows "Connected". In the next tab, Deployment, the dropdown box only shows one (1) image, which also is the incorrect CPU architecture. Only Virtual Control AMDx64 shows up (!?) while I expect to see the ARM64 based images for both Edge and Control. Has someone encountered this too? I'd like to hear other people experiences with Virtual Control deployment on ARM based architecture. attachment 1: AMD64 based deployment pulldown menu (correct images) attachment 2: ARM64 based deployment pulldown menu (incorrect images) regards,
Last updated: 2024-07-28

Deploy Edge Gateway configuration without IDE ^{CODESYS Forge talk (Thread)}
Deploy Edge Gateway configuration without IDE
Last updated: 2022-06-23

runtime deploy tool hangs (3.5.14.300) ^{CODESYS Forge talk (Thread)}
runtime deploy tool hangs (3.5.14.300)
Last updated: 2019-07-19

Sort by relevance or date