Post by egerobotics on [New Hardware] EtherCAT Digital & Analog IO Board – CODESYS Compatible, All Channels Isolated ^{CODESYS Forge talk (Post)}
Hi everyone, I'd like to share a new EtherCAT slave I/O board I've developed — the EtherCAT Digital & Analog IO Board by EGEROBOTICS. Key specs: 12x isolated digital outputs (24VDC) 12x isolated digital inputs (24VDC) 4x isolated 0–10V analog outputs (12-bit DAC) 4x isolated 0–10V analog inputs (12-bit ADC) All channels galvanically isolated 24VDC powered EtherCAT CoE protocol Typical use cases: Analog servo drive speed reference (0–10V) via EtherCAT Frequency inverter reference signal Proportional valve control Industrial sensor data acquisition Compatible with CODESYS SoftMotion, Beckhoff TwinCAT 2/3, LinuxCNC + EtherCAT HAL, and SOEM. Here's a quick demo video showing it running under CODESYS: 👉 https://www.youtube.com/watch?v=bUuo9reK29s ESI file, PDF manual and AutoCAD drawings available. Available on Tindie: https://www.tindie.com/products/emresensoy/ethercat-digan-io/ Happy to answer any technical questions!
Last updated: 2026-06-13

Post by jari-koivuluoma on Comparing between SP19 patch 5 and patch 7 ^{CODESYS Forge talk (Post)}
Hello. Has anyone here used project compare tool across different versions of Codesys? I tried the compare of the title but it does not seem to do much. It lets me choose the project files and then seems to be comparing but no results are ever shown. If the compare tool cannot be used how else would I keep 2 nearly identical projects in sync when the versions differ? On the other hand it might be possible to just have one project but then I would need to use the older codesys with older target device description to develop for devices that have newer device description. Codesys will let me do that but its not recommending it. Any advice?
Last updated: 2026-08-20

Post by gmau on Station 'xyz': AR aborted by device (alarm.ind): AR consumer DHT expired ^{CODESYS Forge talk (Post)}
Hello, I am writing to You with the problem of Profinet communication in my Codesys V2.5 SP21 project working on Codesys Control RTE V3 x64 device. I have implemented multiple Profinet devices in the network, the Profinet itself is configured properly, based on the hardware and software parameters of the industrial PC (Windows 10 IoT). My Profinet network contains such Profinet devices as a robot, IO-Link master with some devices on it, IO modules, safety, vision sensor (the configuration is attached to this topic). Once every few hours, sometimes more often, sometimes not even once a day, the error show up at one, two or a few random modules at the same time, every one is the same: "Station 'xyz': AR aborted by device (alarm.ind): AR consumer DHT expired". The communication is then lost with that module, but it is up instantly. It is not such a problem when it comes to regular IOs, but with safety or rotation table, it causes errors and machine stops. I have tried multiple solution based on any forum suggestions, manuals, etc., but it is still happening. Mabye when I turned on the Watchdog for this communication, it is happening less times, but still, I could not turning up the Watchdog parameters at the expense of cycle time of the process. The same is with Send Clock, Reduction and DHT. I have one of the ethernet port on the PC configured with CmpEt1000Drv driver. The card itself is Intel Ethernet Connection I219-LM. These devices are connected to one EKI-2728-NI-A Profinet switch (it was changed from the standard non Profinet one, but still nothing has changed). As I said ealier, I am attaching all the configurations for each device and the communication itself - if any of You had the same problems or have any ideas what could be the cause, I would be much gratefull for any help. For now I am out of ideas, if You have any additional question, please ask. Sincerely, PF
Last updated: 2025-09-04

Post by rossanoparis on CAN TX regression in Control for Raspberry Pi 4.21.0.0 with CAN API library (RX works, TX silently fails) ^{CODESYS Forge talk (Post)}
Environment: Target: Revolution Pi (Kunbus RevPi), armv7l 32-bit OS: Raspbian GNU/Linux 9 (Stretch), kernel 4.19.95-rt38-v7 (SMP PREEMPT RT, built 2022-03-22) CAN: via SocketCAN (can0) Runtime: CODESYS Control for Raspberry Pi SL IDE: CODESYS V3.5 SP22 + patch 3 (previously V3.5 SP22 + patch 2, where everything worked with runtime 4.18.0.0) Library: CANBusAPI from the "CAN API" package, version 1.0.0.3 Summary: The setup worked correctly with V3.5 SP22 + patch 2 and runtime 4.18.0.0. After updating the IDE to SP22 + patch 3 and the runtime to 4.21.0.0, CAN transmission via the CANBusAPI library stopped working. Reception is unaffected. There are no error indications anywhere: the application runs normally and the CAN diagnosis reports a healthy bus. Systematic testing (below) shows the problem follows the runtime version, not the IDE update. Regression isolation: The same application (compiled under SP22 + patch 3, unchanged between tests) was downloaded to the same target with different runtime versions, changing only the runtime each time: 4.18.0.0: TX and RX both work 4.19.0.0: TX and RX both work 4.20.0.0: TX and RX both work 4.21.0.0: RX works, TX does not The behavior is fully reproducible in both directions (downgrading to 4.20 restores TX, upgrading to 4.21 breaks it again). Hardware, wiring, OS, project, and application code are identical across all tests. Diagnostic data (CANBusDiagnosis FB, while the application is transmitting on 4.21): ctSendCounter: incrementing normally ctTxErrorCounter: 0 ctRxErrorCounter: 0 eState: ERROR_FREE xBusAlarm: FALSE So the library accepts and counts the outgoing messages, no TX errors are reported, and the CAN controller state stays error-free, but the messages never reach the other nodes on the bus. Expected behavior: Messages sent via CANBusAPI (CANDriver / SendMessage) are transmitted on the bus, as with runtime versions up to and including 4.20.0.0. Notes: I am aware that the CAN API package (1.0.0.3, from 2016) is old; however, the regression is tied to the runtime version, since the identical binary works on 4.18-4.20. Questions: Is there a known change in CmpSocketCanDrv / CmpCAACanL2 between 4.20.0.0 and 4.21.0.0 that could affect TX via the CAN API library? Is runtime 4.21.0.0 still supported on Debian 9 Stretch (kernel 4.19, RT-patched), or is a newer OS required? If a minimum OS/kernel requirement was introduced with 4.21, is it documented?
Last updated: 2026-08-17

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

(no subject) ^{CODESYS Forge talk (Thread)}
Last updated: 2007-09-28

IJSONData.FindAllElementsByKey ^{CODESYS Forge talk (Thread)}
IJSONData.FindAllElementsByKey
Last updated: 2021-12-09

SysDir ^{CODESYS Forge talk (Thread)}
SysDir
Last updated: 2022-02-15

MaxNodesPerRead ^{CODESYS Forge talk (Thread)}
MaxNodesPerRead
Last updated: 2018-03-16

Time ^{CODESYS Forge talk (Thread)}
Time
Last updated: 2023-03-03

Sprachumschaltung ^{CODESYS Forge talk (Thread)}
Sprachumschaltung
Last updated: 2009-06-10

Reglersimulation ^{CODESYS Forge talk (Thread)}
Reglersimulation
Last updated: 2018-01-16

swiping ^{CODESYS Forge talk (Thread)}
swiping
Last updated: 2020-11-30

CODESYSControl.cfg ^{CODESYS Forge talk (Thread)}
CODESYSControl.cfg
Last updated: 2015-06-02

how to run the machine using CNC editor in codesys ^{CODESYS Forge talk (Thread)}
how to run the machine using CNC editor in codesys
Last updated: 2007-10-24

ESP8266 ^{CODESYS Forge talk (Thread)}
ESP8266
Last updated: 2016-10-29

Cmpiecvaracces ^{CODESYS Forge talk (Thread)}
Cmpiecvaracces
Last updated: 2016-06-27

Sort by relevance or date