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

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

More COM port in Linux Codesys ^{CODESYS Forge talk (Thread)}
More COM port in Linux Codesys
Last updated: 2022-03-28

Codesys V3.5SP17 Problem: update Raspberry Package ^{CODESYS Forge talk (Thread)}
Codesys V3.5SP17 Problem: update Raspberry Package
Last updated: 2021-05-19

Sort by relevance or date