CODESYS Control Standard S and Beaglebone ^{CODESYS Forge talk (Thread)}
CODESYS Control Standard S and Beaglebone
Last updated: 2024-05-11

Read Serial Number of PLC ^{CODESYS Forge talk (Thread)}
Read Serial Number of PLC
Last updated: 2024-05-21

KNX SL on stock PFC200 firmware ^{CODESYS Forge talk (Thread)}
KNX SL on stock PFC200 firmware
Last updated: 2024-05-23

Raspberry Pi 4 POU not running ^{CODESYS Forge talk (Thread)}
Raspberry Pi 4 POU not running
Last updated: 2024-06-02

Raspberry Pi 4 POU not running ^{CODESYS Forge talk (Thread)}
Raspberry Pi 4 POU not running
Last updated: 2024-06-02

IO-LINK Package - new license model ^{CODESYS Forge talk (Thread)}
IO-LINK Package - new license model
Last updated: 2024-06-06

Data source and safety PLC ^{CODESYS Forge talk (Thread)}
Data source and safety PLC
Last updated: 2024-06-17

Strange Behavior on Raspberry Pi ^{CODESYS Forge talk (Thread)}
Strange Behavior on Raspberry Pi
Last updated: 2024-06-18

Stepper motor control with (SM_Drive_RaspStepper_direct) ^{CODESYS Forge talk (Thread)}
Stepper motor control with (SM_Drive_RaspStepper_direct)
Last updated: 2025-11-11

Deploy LicenseServer for Linux SL ^{CODESYS Forge talk (Thread)}
Deploy LicenseServer for Linux SL
Last updated: 2025-11-21

License problem with Raspberry Pi ^{CODESYS Forge talk (Thread)}
License problem with Raspberry Pi
Last updated: 2025-12-01

Deploy Control SL cant find Podman ^{CODESYS Forge talk (Thread)}
Deploy Control SL cant find Podman
Last updated: 2025-12-10

<Dereference of invalid pointer> ^{CODESYS Forge talk (Thread)}
<dereference of="" invalid="" pointer=""></dereference>
Last updated: 2026-06-26

Post by osande on Trend/trace data ^{CODESYS Forge talk (Post)}
Trend ....
Last updated: 2026-03-13

Post by osande on Trend/trace data ^{CODESYS Forge talk (Post)}
The standard Trace works...
Last updated: 2026-03-13

Hardware compatibility with Linux RealTime PLC ^{CODESYS Forge talk (Thread)}
Hardware compatibility with Linux RealTime PLC
Last updated: 2026-06-15

Pi as Modbus TCP slave. Errors ^{CODESYS Forge talk (Thread)}
Pi as Modbus TCP slave. Errors
Last updated: 2026-04-29

PFC200 - WAGO 750-8202 - MODBUS RTU ^{CODESYS Forge talk (Thread)}
PFC200 - WAGO 750-8202 - MODBUS RTU
Last updated: 2026-05-22

PFC200 - WAGO 750-8202 - MODBUS RTU ^{CODESYS Forge talk (Thread)}
PFC200 - WAGO 750-8202 - MODBUS RTU
Last updated: 2026-05-22

See if application is running ^{CODESYS Forge talk (Thread)}
See if application is running
Last updated: 2026-07-10

Post by arjunk on How to correctly create a device descriptor (.devdesc.xml) for a custom Linux ARM64 PLC in CODESYS 3.5.21.20? ^{CODESYS Forge talk (Post)}
I’m trying to integrate a custom PLC into CODESYS so that it appears under the Device section. From what I understand, this requires a .devdesc.xml device descriptor file. I attempted to create the XML manually, but whenever I try to install it in order to generate a .package file, CODESYS crashes. CODESYS version: 3.5.21.20 Target PLC: Linux ARM64–based My questions are: Is there an official or easier way to generate a valid .devdesc.xml file for a custom PLC? Are there tools, templates, or examples that can help ensure the XML is structured correctly and won’t cause crashes? For Linux ARM64 targets specifically, is there a recommended starting point (e.g., modifying an existing device descriptor)? Any guidance or best practices for creating and packaging custom device descriptors would be greatly appreciated.
Last updated: 2025-10-06

Post by talpade on WAGO PLC 200 750-8216 Ethernet connection to Codesys 3.5 ^{CODESYS Forge talk (Post)}
Hello, I have the WAGO PLC 200 750-8210. In addition I have downloaded the "WAGO Devices and Libraries 2.0.4.3" and installed the library into the Codesys v 3.5. I then create a new project on Codesys 3.5 and select the device "750-8216 PFC200 (WAGO)" (which I downloaded from the WAGO library). However when I have connected the ethernet cable from the WAGO device to my computer and on my codesys 3.5 i press "Scan Network" on codesys and it does not detect the device. How can I get it to detect the device? (I have put the ethernet cable from my WAGO to the computer, but it does not show the device).
Last updated: 2024-02-05

Post by infinitetool on No connection could be made because the target machine actively refused it ^{CODESYS Forge talk (Post)}
Hi! I'm having trouble connecting to a device in Deploy Control SL. I'm able to see the device is available during a scan, and I can ping the device as well, but when I try to connect I get the message "No connection could be made because the target machine actively refused it". I've worked on this for hours including turning off the firewall on the device PC but nothing seems to work. The device is running a fresh install of Windows 11 IoT Enterprise 2024 and the Development System is 3.5.21.50 running on Windows 11. Thank you in advance for any ideas!
Last updated: 2026-03-10

Post by bjarne-pagaard on Communication between applications on same device/controller/runtime (Win RTE 3.5.20.20) ^{CODESYS Forge talk (Post)}
Thanks for this - I have now been looking in to just having an extra (non-RTE) runtime on the same machine, as you suggest. I will probably proceed this way. Even though it still seems very odd to me, that variable exchange to a different runtime is easier than between applications on the same controller. There will be some fun with the licensing, it seems. Does anyone know if it is possible to specify which license container/specific license the runtime is going to use at runtime. Let's say I have two available licenses with different resources available, for example one license allows multicore and multiple EtherCAT channels, but not many visu tags (for the RTE). Another with less resources but a lot of visu tags (for the Visu controller). Let's say the program in one of the controllers could be fully licensed by either of the two available licenses, but picks the 'largest' first. A bit later, the larger application starts, but is left with the smaller license.. How can I make sure that the 2 runtimes select the right license at startup?
Last updated: 2024-10-01

Post by roundex on CSVReaderInit returns error : INVALID_HANDLE ^{CODESYS Forge talk (Post)}
I got same issue but managed to get it to work again by downgrading the Runtime. Here's my specs: CODESYS V3.5.19.0 Runtime Linux SL 4.7.0.0. CSV Utility SL 1.1.0.0 (Licensed IIoT libraries SL) I tried Runtime 4.8.0.0. and 4.9.0.0 but both result in INVALID_HANDLE error.
Last updated: 2023-08-30

Sort by relevance or date