Codesys 3.5.21.3 add Library search not work ^{CODESYS Forge talk (Thread)}
Codesys 3.5.21.3 add Library search not work
Last updated: 2026-05-26

Codesys 3.5.21 fails to copy file to USB ^{CODESYS Forge talk (Thread)}
Codesys 3.5.21 fails to copy file to USB
Last updated: 2026-06-16

Deploy Codesys Control SL to a 'secure' device ^{CODESYS Forge talk (Thread)}
Deploy Codesys Control SL to a 'secure' device
Last updated: 2026-08-10

codesys installer deletes itself instead of updating ^{CODESYS Forge talk (Thread)}
codesys installer deletes itself instead of updating
Last updated: 2026-08-11

Codesys Virtual Safe Control startet nicht (mehr) ^{CODESYS Forge talk (Thread)}
Codesys Virtual Safe Control startet nicht (mehr)
Last updated: 2026-09-08

Codesys EtherCAT Driver (CmpEt1000MPD) can't set MAC address ^{CODESYS Forge talk (Thread)}
Codesys EtherCAT Driver (CmpEt1000MPD) can't set MAC address
Last updated: 2026-02-09

Unit testing support / libraries for EcoStruxure Machine Expert (CODESYS) ^{CODESYS Forge talk (Thread)}
Unit testing support / libraries for EcoStruxure Machine Expert (CODESYS)
Last updated: 2026-02-20

How to use MQTT in CODESYS Control Win V3 ^{CODESYS Forge talk (Thread)}
How to use MQTT in CODESYS Control Win V3
Last updated: 2026-02-25

RS232 Communication in CODESYS Control RTE V3 ^{CODESYS Forge talk (Thread)}
RS232 Communication in CODESYS Control RTE V3
Last updated: 2026-03-14

CODESYS device discovery performance in large networks (/16) ^{CODESYS Forge talk (Thread)}
CODESYS device discovery performance in large networks (/16)
Last updated: 2026-03-29

Codesys Installation Always Freeze when the installing is almost done ^{CODESYS Forge talk (Thread)}
Codesys Installation Always Freeze when the installing is almost done
Last updated: 2026-04-05

file library ifm CR2033 .lib in the CODESYS v2.3 ^{CODESYS Forge talk (Thread)}
file library ifm CR2033 .lib in the CODESYS v2.3
Last updated: 2026-04-22

Equal Objects at Unstaged Changes - Git (Codesys Pro) ^{CODESYS Forge talk (Thread)}
Equal Objects at Unstaged Changes - Git (Codesys Pro)
Last updated: 2026-05-14

Post by axberry on CODESYS Control for Raspberry Pi 5 - "Hardware version or firmware version not supported" on Rev 1.1, persists across multiple runtime versions and OS images ^{CODESYS Forge talk (Post)}
Hi, I'm trying to run CODESYS Control for Raspberry Pi SL on a Raspberry Pi 5, and the runtime consistently fails to start with the following error when launched manually: ooops... this runtime was built for RASPBERRYPI. Hardware version or firmware version not supported! (-18, 0x00000BB8, 0xFFFFFFFB) Hardware: Raspberry Pi 5 Model B Rev 1.1 Revision code: d04171 CPU: aarch64, BCM2712 Serial number is correctly exposed via /proc/cpuinfo and /proc/device-tree/serial-number /proc/device-tree/model correctly reports "Raspberry Pi 5 Model B" What I've tried (all resulting in the same error): CODESYS Control for Raspberry Pi SL 4.11.0.0 (SDK 3.5.19.61) — the version that introduced Pi 5 support CODESYS Control for Raspberry Pi SL 4.21.0.0 (SDK 3.5.22.20) — latest available Raspberry Pi OS Bookworm (64-bit) with kernel 6.12.93+rpt-rpi-2712 (June 2026 build) Fresh install on Raspberry Pi OS Bookworm (64-bit) with an older image from November 24, 2025 — same error, ruling out a kernel-version regression Bootloader/EEPROM confirmed up to date (rpi-eeprom-update reports "up to date") Clean purge and reinstall of the codesyscontrol package each time (verified via dpkg -l, no leftover files) Verified /etc/codesyscontrol/3S.dat correctly symlinks to /etc/codesyscontrol/3S_aarch64.dat The service starts (systemctl status briefly shows active (running) with a real PID under /opt/codesys/bin/codesyscontrol.bin), but crashes shortly after and the process disappears — port 11740 never opens. Since this happens identically across two different runtime versions and two different OS images (5+ months apart), it doesn't seem to be a kernel/firmware timing issue. Could this be specific to the Rev 1.1 board revision, or is there a known issue with the hardware detection logic in the SL runtime that I should be aware of? Happy to provide full debug logs (-d flag output) or journalctl output if useful. Thanks in advance!
Last updated: 2026-08-10

Post by artplc on 3.5 P20 hangs - no response ^{CODESYS Forge talk (Post)}
Subject: Solution: CODESYS Freezes Linked to Large Symbol Configuration (OPC UA) Hello everyone, I was experiencing the same problem as many here: CODESYS (v3.5 SP20+) freezing during compilation and download, especially on projects that use OPC UA for SCADA. The only workaround was to run Build > Clean all before every download. I believe I have found the root cause and a permanent solution. The Problem: The issue is directly related to a large Symbol Configuration. In my project, I only need about 700 tags for OPC UA, but the Symbol Configuration list was showing over 250,000 tags. This is because it automatically includes all variables from Global Variable Lists (GVLs) and other memory areas. When any static variable is changed, the IDE tries to rebuild this enormous list, causing it to freeze for several minutes. The Solution: Instead of letting CODESYS export every variable by default, you can use a pragma to tell it which variables or GVLs to exclude from the symbol export process. Place the following pragma at the top of any GVL or data structure that you do not want to be part of the symbol configuration: 1 {attribute 'symbol' := 'none'} 2 VAR_GLOBAL 3 // All variables in this GVL will now be excluded from the 4 // Symbol Configuration by default. 5 InternalVariable1 : INT; 6 InternalVariable2 : BOOL; 7 END_VAR After adding this pragma to all the GVLs that were not needed for OPC UA, the number of tags in my Symbol Configuration dropped to the correct amount. The compilation and download process is now fast again, with no freezing. This method is much more efficient than manually managing the symbol list in the editor. I hope this helps others who are facing this frustrating issue. Best regards.
Last updated: 2025-08-10

Post by thierry-b on Blocking UDP ports 1740–1743 and 22350 to disable CODESYS network scan (startup + device discovery) ^{CODESYS Forge talk (Post)}
Hello, I am currently investigating the network behavior of CODESYS 3.5 (IDE + Gateway) in environments where the engineering workstation is connected to a very large /16 network. In such networks, the automatic device scan performed at IDE startup (and the manual “Scan Network” device discovery) can cause significant delays or freezes, due to the broadcast‑based discovery mechanism. After analyzing the traffic with Wireshark, I identified that the IDE uses the following UDP ports: 1740 – broadcast discovery 1741 – handshake / responses 1742 – fallback discovery 1743 – fallback handshake 22350 – additional runtime / gateway communication (WAGO, debug, extended discovery) To prevent the IDE from scanning the large /16 network, I tested blocking these ports in both directions (IN/OUT) on the network interface connected to the /16 segment (while keeping them open on the OT /24 network interface). Result: When UDP 1740, 1741, 1742 and 1743 are blocked on the IT interface, the IDE no longer sends any discovery traffic on that interface. The IDE still works normally on the OT interface (device discovery, online mode, download, etc.). Blocking port 22350 does not seem required to stop the scan, but I included it for completeness. My question: => Can you confirm that blocking UDP ports 1740, 1741, 1742, 1743 (and optionally 22350) on a specific network interface is a valid and supported way to completely disable the CODESYS IDE network scan on that interface (both at startup and during manual device discovery)? I am not trying to block communication with controllers on the OT network — only to prevent the IDE from scanning the large /16 IT network. Any confirmation or additional technical details about the discovery mechanism would be greatly appreciated. Thank you.
Last updated: 2026-03-31

communication ^{CODESYS Forge talk (Thread)}
communication
Last updated: 2023-08-19

NETVAR_UDP ^{CODESYS Forge talk (Thread)}
NETVAR_UDP
Last updated: 2023-08-29

VPN ^{CODESYS Forge talk (Thread)}
VPN
Last updated: 2023-09-06

VPN ^{CODESYS Forge talk (Thread)}
VPN
Last updated: 2023-09-06

VPN ^{CODESYS Forge talk (Thread)}
VPN
Last updated: 2023-09-06

ernesto881124 ^{CODESYS Forge talk (Thread)}
ernesto881124
Last updated: 2023-09-14

Benutzeranmeldung ^{CODESYS Forge talk (Thread)}
Benutzeranmeldung
Last updated: 2009-01-19

Trend ^{CODESYS Forge talk (Thread)}
Trend
Last updated: 2021-11-26

Warten ^{CODESYS Forge talk (Thread)}
Warten
Last updated: 2009-09-17

Sort by relevance or date