| FORUM | LATEST POST | # TOPICS |
|---|---|---|
|
Engineering π¬π§ Discussions about the CODESYS Development System, IEC programming, CODESYS Professional Developer Edition |
PROFINET Controller SL: WRREC remains BUSY forever, no DCE/RPC packets t... by kuegerls 2 days ago |
6034 |
|
Runtime π¬π§ Related questions to SoftPLCs e.g. Raspberry Pi, Beaglebone, IoT2000 and other platforms |
CmpCharDevice blocks gpiochip access on Raspberry Pi 5 since update from... by eschwellinger 44 minutes ago |
2309 |
|
Visualization π¬π§ Realizing operator screens with CODESYS HMI, Targetvisu, Webvisu |
Dynamic Images by erik.gerrits 2026-07-10 |
1067 |
|
Motion π¬π§ Realizing single or multi axis motion control, CAM, CNC and Robotic applications |
Limit Axis CNC Jerk using SMC_Polynomial_AbsMaxLocs by gseidel 2026-07-09 |
574 |
|
Codesys V2.3 π¬π§ Forum about V2.3 |
Where Can I download the latest Version of CoDeSys V by yueqiqi 2026-06-15 |
2245 |
|
Deutsch π©πͺ German forum |
Zielsystem Problem nach Bibliotheken hinzufΓΌgen by dakmueller 2026-06-22 |
4589 |
|
Automation Server π¬π§ The Industry 4.0 administration platform for users and operators of CODESYS compatible controllers |
Gateway in China - "Gateway not connected" by pernockham 2026-03-18 |
81 |
|
Forge π¬π§ Discussions about CODESYS Forge projects and features of the CODESYS Forge website |
WebVisu scaling regression in V3.5.22 P2: frame size jumps when switchin... by charly29160 2026-06-15 |
232 |
this is probably: https://content.helpme-codesys.com/en/CODESYS%20Control/_rtsl_linux_dedicated_user.html ..switch back from rootless mode due GPIO will not work.
Hi, after updating CODESYS Control for Raspberry Pi SL from patch level 18 to 21 (currently 4.21.0.0), the IoDrvGPIO driver ("GPIOs B+/Pi2") can no longer open any GPIO chip on a Raspberry Pi 5. Log output on login: Could not open GPIOChip0. Access to path /dev/gpiochip0 not allowed. Add /dev/gpiochip0 to permitted paths in configuration file if required Could not open GPIOChip4. Trying to open GPIOChip0 Access to path /dev/gpiochip4 not allowed. Add /dev/gpiochip4 to permitted paths in configuration...
Hello , I am currently evaluating the CODESYS PROFINET Controller SL on a Revolution Pi Connect 5 and have encountered a problem with acyclic PROFINET Record Access (WRREC/RDREC). System Hardware: Revolution Pi Connect 5 Runtime: CODESYS Control 4.16.0.0 (SDK 3.5.21.10) Development System: CODESYS V3.5 SP21 (64-bit) CommFB: 3.5.17.10 ProfinetCommon: 4.6.0.0 PROFINET Controller Device: PN-Controller 4.6.0.0 PROFINET Device: NORD DRIVESYSTEMS SK205E with SK TU4-PNT GSDML: GSDML-V2.46-NORDDRIVESYSTEMS-PNT-20251016.xml...
Hi, I have exactly the same issue when I try to update from 3.5.21.50 to 3.5.22.20. Currently I didn't find where is the problem. Hope somebody can find a way. Tristan
Subject: Curtis 1229-4105 CANopen (CiA 301 / CiA 402) Hello everyone, I am developing a battery-powered industry vehicle using a Curtis 1229-4105 motor controller together with a Siemens S7-1200 PLC and an HMS (Ixxat) CANopen Master. I am looking for someone who has practical experience with the Curtis 1229-4105 CANopen implementation. I would appreciate your help with the following questions: Does the Curtis 1229-4105 support only CANopen CiA 301, or does it also support CiA 402? Is an EDS file...
I've been moving in the same direction. For new libraries, I'm trying to minimize dependencies on APIs that look like they're being phased out unless the documentation explicitly recommends them. For synchronization primitives like CAA.BOLT and CAA.SEMA, I'd love to see an official replacement or abstraction layer that's guaranteed to remain stable across runtimes. That would make library development much cleaner than relying on platform-specific SysLib* implementations or conditional compilation...
I've been moving in the same direction. For new libraries, I'm trying to minimize dependencies on APIs that look like they're being phased out unless the documentation explicitly recommends them. For synchronization primitives like CAA.BOLT and CAA.SEMA, I'd love to see an official replacement or abstraction layer that's guaranteed to remain stable across runtimes. That would make library development much cleaner than relying on platform-specific SysLib* implementations or conditional compilation...
On which plc you want to add this your screenshot show that it would work on Control Win ?
I am trying to use Codesys to connect by Modbus RTU to an Arduino UNO, I add the Modbus COM Port but when I try to add the master and the slave I don't have these options, I attach an image of the device manager. I am using Codesys 3.5 SP21.