CODESYS Security Key vs CODESYS Runtime Key ^{CODESYS Forge talk (Thread)}
CODESYS Security Key vs CODESYS Runtime Key
Last updated: 2016-09-13

Conversion from CoDeSys 2 to CoDeSys 3 ^{CODESYS Forge talk (Thread)}
Conversion from CoDeSys 2 to CoDeSys 3
Last updated: 2013-10-17

etablish communication between codesys 2 and codesys 3 ^{CODESYS Forge talk (Thread)}
etablish communication between codesys 2 and codesys 3
Last updated: 2017-08-18

Licensing Codesys control for raspi without using codesys software ^{CODESYS Forge talk (Thread)}
Licensing Codesys control for raspi without using codesys software
Last updated: 2023-04-12

Copy a program IL from codesys 2 to codesys 3 ^{CODESYS Forge talk (Thread)}
Copy a program IL from codesys 2 to codesys 3
Last updated: 2017-02-27

How to open a Codesys V2.3 project in Codesys V3.5 ^{CODESYS Forge talk (Thread)}
How to open a Codesys V2.3 project in Codesys V3.5
Last updated: 2018-03-23

share data between codesys and non-codesys application ^{CODESYS Forge talk (Thread)}
share data between codesys and non-codesys application
Last updated: 2016-03-03

Library from codesys 2.3 to codesys 3.5 ^{CODESYS Forge talk (Thread)}
Library from codesys 2.3 to codesys 3.5
Last updated: 2022-01-28

Shortcuts (hot keys) from Codesys 2.3 to Codesys 3.5 ^{CODESYS Forge talk (Thread)}
Shortcuts (hot keys) from Codesys 2.3 to Codesys 3.5
Last updated: 2021-08-26

Codesys Profinet Controller - Codesys Profinet Device Communication ^{CODESYS Forge talk (Thread)}
Codesys Profinet Controller - Codesys Profinet Device Communication
Last updated: 2019-04-04

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

Codesys Network driver install for Codesys Control RTE x64 ^{CODESYS Forge talk (Thread)}
Codesys Network driver install for Codesys Control RTE x64
Last updated: 2026-02-06

Python script: Launch Codesys, Execute Script, Exit Codesys ^{CODESYS Forge talk (Thread)}
Python script: Launch Codesys, Execute Script, Exit Codesys
Last updated: 2026-02-12

Post by gmau on RS232 Communication in CODESYS Control RTE V3 ^{CODESYS Forge talk (Post)}
Hello, I would like to implement RS232 communication into CODESYS Control RTE V3. I was writing the program testing it on CODESYS Control Win V3, where it worked fine. When I changed it to RTE, the communication was on, but I cannot send the data between PLC and scale - there is no or little response from scale - mostly one time receive and that is it. On Win V3 it was working fine. I read that I am supposed to configure CODESYSControl file for a proper communication using RTE, but even after that I can not get a stable and working communication. I am attaching my CODESYSControl and CODESYSControlUser data below, as well as I am sending the code from communication function. The communication should be through COM1 port of PC. CODESYS Version: CODESYS V3.5 SP21 + (64-bit) Runtime + Version: CODESYS Control RTE V3 Version 3.5.21.0 / CODESYS Gateway V3 - x64 Version 2.5.21.0 I would be much gratefull for any help. Sincerely,
Last updated: 2025-07-16

Post by reinier-geers on License problem gateway ^{CODESYS Forge talk (Post)}
16.4 Epis What has it to do with the manufacture? It just a licence more not. So basicly the idee of codesys sucks. 3s acts like its posible to add a license. And then it depence on the manufacturer. Why ?? Its a computer !! has nothing to do with the manufacturer. Most dont what a basic licence because they have to pay for that. 3s is the problem not the manufacture of the hardware. Its like the licence of the raspberry pi. HMI is not working. Sorry you get a refund. Why suggest that its possible wen its not !!. It cost me a lot of time. Who pays my time. Why do i have to pay for somting thats not working.
Last updated: 2024-04-26

Post by reinier-geers on License problem gateway ^{CODESYS Forge talk (Post)}
Epis doesnt want Softmotion. I thought it was about the price. If it was possible it would be working already and i dont need an extra licence. Thats the problem of codesys. The software is running but hangs on its license. Epis made it posible to see the stick. I can see the license. Softmotion is there from 3.5.14.Xx Like is said And Motion control is alrady posible 15 year ago. And i only need a Sync of 2 drives. I want a good solution not a refund. Dont point to the manufacturer. The software is made by 3s not by epis .
Last updated: 2024-04-29

Post by husarz17 on How change Unity-ID in TCP Modbus Slave ^{CODESYS Forge talk (Post)}
My codesys is 3.5.21.30. I am using function ModbusServer from library ModbusTCP_Slave. The reason is that I need share 9000 Holding registers. By standard configuration it is only 4096. fbMbTcpDevice: ModbusTCP_Slave.ModbusServer; fbMbTcpDevice( wPort := 502, pInputData := ADR(awInputReg), pOutputData := ADR(awHoldingReg), uiInputDataSize := 10, uiOutputDataSize := 9000, xEnable := TRUE, tTimeout := 10000, InterfaceName := "eth0", xBusy => xBusy, xError => xError, byClientConnections => byConnections ); Ethernet port is cofigured: Network interface: eth0 IP address: 10.10.22.55 Subnet maskL 255.255.255.0 Default gateway: 0.0.0.0 And it only works when I am reading registers with ID 255 by Modbus Poll. Any other IDs don't work. The actual TCP client device try to read registers with ID 1 and I can't change it... Thanks in advance for your help!
Last updated: 2026-04-01

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

Post by jakubmphoenix on EtherCAT Master on RaspberryPi with EtherCAT Slave on Beckhoff ^{CODESYS Forge talk (Post)}
Hello everyone, I’m currently working on setting up an EtherCAT Master using CODESYS on a Raspberry Pi, and I’ve run into some issues I could use help with. Project Setup: EtherCAT Master: Raspberry Pi with CODESYS Control for Raspberry Pi 64 SL installed EtherCAT Slave: Beckhoff CX5130 with EK1200 coupler I/O Module: EL2008 License Module: EL6070-0033 I’ve installed the required CODESYS packages and the Linux gateway on the Raspberry Pi. In my project, I added the EtherCAT Master with the appropriate port settings and scanned for devices. The CX5130 shows up as a slave, but communication fails—I'm getting error messages and can't access the outputs. Specifically: The EL2008 output module isn’t recognized properly in CODESYS. There’s no option to communicate with it through the CX5130. I’ve tried connecting via both the Raspberry Pi’s built-in Ethernet port and an external network card. I've attached screenshots showing the errors I get in CODESYS and the devices detected via TwinCAT for reference. Any help or suggestions would be greatly appreciated! Thanks in advance! EMERGENCY FROM DEVICE 1001 ERROR CODE 16#A000 Error register 16#02 Error field: 16#02 Error field : 16#0E 16#04 16#00 16#04 16#00
Last updated: 2025-07-16

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

Sort by relevance or date