Problem install codesys 3.5.17 SP 30 with Codesys Installer ^{CODESYS Forge talk (Thread)}
Problem install codesys 3.5.17 SP 30 with Codesys Installer
Last updated: 2024-01-26

Codesys HMI with a non codesys programmed controller ^{CODESYS Forge talk (Thread)}
Codesys HMI with a non codesys programmed controller
Last updated: 2024-02-21

conformation about the CODESYS Extends SL and CODESYS SDK ^{CODESYS Forge talk (Thread)}
conformation about the CODESYS Extends SL and CODESYS SDK
Last updated: 2025-11-11

Post by timvh on Licensing info not available. ^{CODESYS Forge talk (Post)}
In the VPLC configuration settings there is an entry for the IP address of the license server. In this setting fill in the IP address of your device (host IP address). Then when the virtual PLC starts up, it will get the license from the license container on the host. You can do this for all VPLC's running on your device. The VPLC will always take the smallest license which fits the required license. So if you have 2 licenses for VPLC's with small and large applications, then this will work fine if you start up one VPLC which requires the small license and the other which requires the large license. PS, personally I find it much easier, especially for testing and experimenting, to activate the licenses on a CODESYS (USB) key. This is easy to activate (on your development PC) and easier to move to another device. Addtionally you don't loose the license when you need to install a completely new image on the device.
Last updated: 2025-10-02

Post by denizerm on Deploy Control SL cant find Podman ^{CODESYS Forge talk (Post)}
Hello, CODESYS seems to have problems finding the container engine. In the "Deploy Control SL" window, after connecting via ssh, it simply says: [INFORMATION] Connected successfully! [INFORMATION] Successfully connected to target (192.168.4.199) [WARNING] Error detecting container architecture running podman info yields normal results. My podman info output is as follows: home/Admin$ podman info host: arch: amd64 buildahVersion: 1.35.3 cgroupControllers: - cpu - memory - pids cgroupManager: systemd cgroupVersion: v2 conmon: package: Unknown path: /usr/bin/conmon version: 'conmon version 2.1.10, commit: affab49967eb62f75d2a47398344ab053326289f' cpuUtilization: idlePercent: 99.36 systemPercent: 0.3 userPercent: 0.34 cpus: 4 databaseBackend: sqlite distribution: codename: scarthgap distribution: redagv version: 1.0.0 eventLogger: journald freeLocks: 2040 hostname: secure-automation-os idMappings: gidmap: - container_id: 0 host_id: 1000 size: 1 - container_id: 1 host_id: 100000 size: 65536 uidmap: - container_id: 0 host_id: 1100 size: 1 - container_id: 1 host_id: 100000 size: 65536 kernel: 6.6.65-intel-pk-standard linkmode: dynamic logDriver: journald memFree: 6115598336 memTotal: 8086278144 networkBackend: cni networkBackendInfo: backend: cni dns: {} ociRuntime: name: crun package: Unknown path: /usr/bin/crun version: |- crun version 1.14.3.0.0.0.8-89d44-dirty commit: 89d44467e3b410b73f2065756a12789be45b855b rundir: /run/user/1100/crun spec: 1.0.0 +SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +YAJL os: linux pasta: executable: /usr/bin/pasta package: Unknown version: "" remoteSocket: exists: true path: /run/podman-shared/podman.sock security: apparmorEnabled: false capabilities: CAP_CHOWN,CAP_DAC_OVERRIDE,CAP_FOWNER,CAP_FSETID,CAP_KILL,CAP_NET_BIND_SERVICE,CAP_SETFCAP,CAP_SETGID,CAP_SETPCAP,CAP_SETUID,CAP_SYS_CHROOT rootless: true seccompEnabled: true seccompProfilePath: "" selinuxEnabled: false serviceIsRemote: true slirp4netns: executable: /usr/bin/slirp4netns package: Unknown version: |- slirp4netns version 1.2.0-beta.0+dev commit: unknown libslirp: 4.7.0 SLIRP_CONFIG_VERSION_MAX: 4 libseccomp: 2.5.5 swapFree: 0 swapTotal: 0 uptime: 1h 36m 10.00s (Approximately 0.04 days) variant: "" plugins: authorization: null log: - k8s-file - none - passthrough - journald network: - bridge - macvlan - ipvlan volume: - local registries: localhost:5000: Blocked: false Insecure: true Location: localhost:5000 MirrorByDigestOnly: false Mirrors: null Prefix: localhost:5000 PullFromMirror: "" search: - localhost store: configFile: /home/serviceuser/.config/containers/storage.conf containerStore: number: 2 paused: 0 running: 2 stopped: 0 graphDriverName: overlay graphOptions: {} graphRoot: /data/containerfiles graphRootAllocated: 119952025600 graphRootUsed: 13801246720 graphStatus: Backing Filesystem: extfs Native Overlay Diff: "true" Supports d_type: "true" Supports shifting: "false" Supports volatile: "true" Using metacopy: "false" imageCopyTmpDir: /var/tmp imageStore: number: 4 runRoot: /run/user/1100/containers transientStore: false volumePath: /data/containerfiles/volumes version: APIVersion: 5.0.2-dev Built: 1711987427 BuiltTime: Mon Apr 1 16:03:47 2024 GitCommit: bb81e85a430fa95d23a15b77c717fd68bf06ebf2 GoVersion: go1.22.12 Os: linux
Last updated: 2025-10-22

Post by bjarne-pagaard on Communication between applications on same device/controller/runtime (Win RTE 3.5.20.20) ^{CODESYS Forge talk (Post)}
Thanks for this - I have now been looking in to just having an extra (non-RTE) runtime on the same machine, as you suggest. I will probably proceed this way. Even though it still seems very odd to me, that variable exchange to a different runtime is easier than between applications on the same controller. There will be some fun with the licensing, it seems. Does anyone know if it is possible to specify which license container/specific license the runtime is going to use at runtime. Let's say I have two available licenses with different resources available, for example one license allows multicore and multiple EtherCAT channels, but not many visu tags (for the RTE). Another with less resources but a lot of visu tags (for the Visu controller). Let's say the program in one of the controllers could be fully licensed by either of the two available licenses, but picks the 'largest' first. A bit later, the larger application starts, but is left with the smaller license.. How can I make sure that the 2 runtimes select the right license at startup?
Last updated: 2024-10-01

CoDeSys libraries for BECKHOFF EL7332/EL7342 ^{CODESYS Forge talk (Thread)}
CoDeSys libraries for BECKHOFF EL7332/EL7342
Last updated: 2023-08-25

Import RsLogix 5000 project to Codesys ^{CODESYS Forge talk (Thread)}
Import RsLogix 5000 project to Codesys
Last updated: 2023-09-07

Codesys Control RTE V3. Remote Control ^{CODESYS Forge talk (Thread)}
Codesys Control RTE V3. Remote Control
Last updated: 2023-09-22

Recommended Specification for running CodeSys ^{CODESYS Forge talk (Thread)}
Recommended Specification for running CodeSys
Last updated: 2013-11-14

Kommunikationsunterbrechung zwischen CODESYS und RPi 3 ^{CODESYS Forge talk (Thread)}
Kommunikationsunterbrechung zwischen CODESYS und RPi 3
Last updated: 2017-02-20

CODESYS Development System V3.5.18.30 Installation Error ^{CODESYS Forge talk (Thread)}
CODESYS Development System V3.5.18.30 Installation Error
Last updated: 2022-12-07

CoDeSys OPC server with SIMULATION3 interface ^{CODESYS Forge talk (Thread)}
CoDeSys OPC server with SIMULATION3 interface
Last updated: 2016-02-24

Neues Forum zur CoDeSys OPC Anbindung ^{CODESYS Forge talk (Thread)}
Neues Forum zur CoDeSys OPC Anbindung
Last updated: 2011-04-14

Modbus übertragung von CodeSys nach Excel ^{CODESYS Forge talk (Thread)}
Modbus übertragung von CodeSys nach Excel
Last updated: 2010-08-01

CoDeSys V3 mit Raspberry Pi Kamera ^{CODESYS Forge talk (Thread)}
CoDeSys V3 mit Raspberry Pi Kamera
Last updated: 2016-05-05

Codesys Projekt läst sich nicht öffnen ^{CODESYS Forge talk (Thread)}
Codesys Projekt läst sich nicht öffnen
Last updated: 2017-12-10

CODESYS on RPI - tcpip socket ^{CODESYS Forge talk (Thread)}
CODESYS on RPI - tcpip socket
Last updated: 2022-07-14

Codesys V3 and Enron Modbus ^{CODESYS Forge talk (Thread)}
Codesys V3 and Enron Modbus
Last updated: 2022-11-09

PY Script aus CoDeSys Programm ausführen ^{CODESYS Forge talk (Thread)}
PY Script aus CoDeSys Programm ausführen
Last updated: 2017-01-25

CoDeSys 3 auf dem STM32 ^{CODESYS Forge talk (Thread)}
CoDeSys 3 auf dem STM32
Last updated: 2009-03-03

CODESYS + Funktionale Sicherheit SIL3/PLe ^{CODESYS Forge talk (Thread)}
CODESYS + Funktionale Sicherheit SIL3/PLe
Last updated: 2020-05-28

Codesys on Beaglebone Green Wireless? ^{CODESYS Forge talk (Thread)}
Codesys on Beaglebone Green Wireless?
Last updated: 2019-07-04

Codesys V3.5 SP17 P3 Statusanzeige ^{CODESYS Forge talk (Thread)}
Codesys V3.5 SP17 P3 Statusanzeige
Last updated: 2022-04-14

CoDeSys Testmanager commenting out Test Cases ^{CODESYS Forge talk (Thread)}
CoDeSys Testmanager commenting out Test Cases
Last updated: 2022-04-05

Sort by relevance or date