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

Post by baldeep on Codesys Raspberry Runtime 4.10.0.0 and RSM Utility 3.5.19.0 ^{CODESYS Forge talk (Post)}
I had been using Codesys Raspberry 4.9.0.0 Runtime for a Project with CAA File 3.5.19.0. But now with Update 4.10.0.0 and Raspberry pi 64 Bit.....i cannot compile my code as RSM Utility 3.5.19.0 is not recognised. Any help? Regards
Last updated: 2023-11-20

Post by ggis on Rasperry Control Debian 12 ^{CODESYS Forge talk (Post)}
From bash I usually see codesyscontrol.service as the runtime service. Taking a step back, I guess you used Tool > Update RaspberryPi SL interface to install the runtime: what does the info popup window tells you about your destination system?
Last updated: 2023-11-26

Post by eschwellinger on Rpi install runtime licence on SP13 ^{CODESYS Forge talk (Post)}
there are big changes on OS side, so you need latest Runtime version which does even work if you stay on an oder CODESYS version.Especially in Bookworm from December it must be 4.11.0.0 use Bookworm from October
Last updated: 2024-01-09

Post by peter-skokanek on Rpi install runtime licence on SP13 ^{CODESYS Forge talk (Post)}
Hi, In fact, I reinstaled OS from the latest version Bookworm to older Booster and everithing works OK. Anyway, can somebody know when will be available new version of runtime 4.11.0.0?
Last updated: 2024-01-18

Post by eschwellinger on search runtime 4.9.0.0 for pi 3 ^{CODESYS Forge talk (Post)}
sorry I missed to say how to do this just update the runtime. (extract latest debian package out of the CODESYS package) but 8n this case an update all to the latest version including CODESYS is probably the easiest option now.
Last updated: 2025-10-26

CODESYS Control for Raspberry Pi 5 - "Hardware version or firmware version not supported" on Rev 1.1, persists across multiple runtime versions and OS images ^{CODESYS Forge talk (Thread)}
CODESYS Control for Raspberry Pi 5 - "Hardware version or firmware version not supported" on Rev 1.1, persists across multiple runtime versions and OS images
Last updated: 2026-08-11

Post by mozed on Connection to device closed ^{CODESYS Forge talk (Post)}
Hello I am using an OpusA3 with version 3.5 SP17 Patch 3 as part of a project. I had no real problem before I encountered a problem that blocked me. The detection of the OpusA3 from Codesys is done correctly. The gateway is well configured and if I ping the gateway or the OpusA3 I receive the response correctly. The problem is that when I try to connect, the Opus screen freezes and a few moments later Codesys displays an error message ("connection to device closed"). I tried to change PC, to update the runtime, to change OpusA3 but the problem remains the same. I'm a little lost knowing that before it worked without problem. I went back to a previous version of the project (where it worked correctly) but the message still appears. Do you have any clues to solve the problem? Sincerely,
Last updated: 2023-08-23

Post by jonathan1321351 on IO-Link write parameters Ethernet/IP ^{CODESYS Forge talk (Post)}
I want to read and write parameters of an IO-Link device using acyclic messages. I have a Cube67+ in Ethernet/IP, connected to an IO-Link master. In the datasheet, I can find the parameters required for the message (Service, Class, Instance, etc.). I see the function block "Set_attribute_single" in the "EthernetIP Services" library, but I'm not sure how to correctly send the index and sub-index for the IO-Link device. The class in the datasheet is 0x80 for the IO-Link Parameter Object, but it’s not present in the CPIClass enum. Is there another function block more suitable for configuring IO-Link devices? (similar to "iol_call" in PROFINET or what’s used in EtherCAT).
Last updated: 2024-09-02

Post by yoeri on Refresh visulization realtime ^{CODESYS Forge talk (Post)}
Hi everyone, I need some help with displaying an image (test.png) on my device. Initially, showing the image is straightforward. However, I want to be able to update the image dynamically. My goal is to send updated files via FTP to the device, and have the display automatically show the latest version of the image. All images will be sent with the same name (e.g., test.png). Currently, I can see the updated image after sending it via FTP and performing a warm restart, but I'd like to achieve this in runtime, without having to restart the display or application. Does anyone have suggestions on how to implement this? Thanks in advance!
Last updated: 2024-10-21

Post by pernockham on Control for linux SL, 4.14.0.0 -> 4.15.0.0 breaks web page access. URL requires authentication ^{CODESYS Forge talk (Post)}
I have a problem which I have identified with a device-update from 4.14.0.0 to (4.15.0.0-4.17.0.0) where the newer versions will stop any local access to the internal web page with the browser responding "The requested URL requires authentication". Setting the device back to 4.14.0.0. the web page will respond. Access to web page through Automation server is possible also for the newer version, but not "local" access. Runtime (Codesys control for linux SL) is on 4.17.0.0. I have tried to manipulate settings for 'Access-Control-Allow-Origin' '*' always; through nginx (normally a proxy_pass to localhost:8080). Also tested bypassing nginx by accessing 8080 directly with the same result.
Last updated: 2025-09-08

Post by royw on Profinet library for C# ^{CODESYS Forge talk (Post)}
Hi, I don't know if I'm in the right place or if it's even possible... I'm looking for a way to address a Profinet device with Record Read and Write from my own PC. I actually only need very few commands to configure our device. This means setting the MAC address and a serial number. We would like to do this from a C# program. Now we are looking for a library or something similar. Since you can do it from Codesys, I thought there might be a DLL or something similar that you could use for this. As I said, we don't want real-time queries of the cyclic data but only record read/write. Does anyone have any helpful hint? Thanks in advance
Last updated: 2023-12-22

Post by mp9876 on Device logon problem following fresh install ^{CODESYS Forge talk (Post)}
All screenshots are enclosed in MS Word document. NOTE; 4 questions features at the end. Any assistance would be greatly appreciated! Hi everyone, I am still having device logon problem following a fresh install Here are the STEPS I went through following a FRESH CODESYS Win 64 3.5.19.60 install on a different computer. ‘Gateway not configured properly’ when attempting to REFRESH from the Users and Groups. Then did Gateway manage and confirmed it was ok: This message popped out as it was a fresh install: YES then: Initially went with Administrator twice (user & password) but it did not like it. No device is responding to …: Continued by setting a new user Pressed OK and obtained the following message: Stopped and Restarted PLC at that point: Obtained the following: Attempted to login a 2nd time without success. Then I scanned the network to see if matching device can be detected: Only way to get it detected was to remove the tick in the ‘Hide non-matching devices…’ Attempted a WINK but got a return like this one: REFRESH either @ Users and Groups or @ Access Rights returns: Then created user ‘mp’ at Project level ang logged in: Understandably device user mp9876 was not valid for the Project. Device information A few questions comes to my mind following these connection attempts: 1- Gateway not configured properly message pops out because of a non-compatible device ? 2- Why would the device not be compatible ? 3- Any way to make the device compatible ? 4- Any ideas on how to get this connectivity problem to the device solved ?
Last updated: 2024-03-17

Post by lzml on HTML5 visualization controls disabled on CODESYS Control for Linux SL - overlay not supported? ^{CODESYS Forge talk (Post)}
Hello, I'm developing a custom HTML5 visualization control (via the HTML5 Control Editor / Tools > Visualization Element Repository) and I'm running into what looks like a target-device limitation when trying to deploy it to CODESYS Control for Linux SL. I'd like to understand whether this is a known/expected limitation or something in my setup. Environment - CODESYS Development System: V3.5.22.0 - Target runtime: CODESYS Control for Linux SL, package version 4.15.0.0 (installed together with CODESYS Edge Gateway for Linux 4.15.0.0) - Visu system libraries (VisuElems, VisuElemsAlarm, VisuInputs, VisuNativeControl, etc.): version 4.7.0.0 - Host OS: Debian RT (minimal/base installation) - We only use WebVisu, not TargetVisu. What I did 1. Built a custom HTML5 control following the official HTML5-API-Examples pattern (.html5control.xml manifest + ElementWrapper.js + CSS), installed it successfully via the HTML5 Control Editor ("Save and Install") into the Visualization Element Repository. 2. In the Visualization Manager, enabled "Support client animations and overlay of native elements" (documented as required for HTML5 controls to work at all). 3. With the project's Device set to CODESYS Control for Linux SL, compiling/downloading fails with: "Overlay is not supported for your target visualization device." (Visualization Manager) Build stops with 1 error, download not possible. Isolating the cause - The Visualization Element Repository confirms the control is correctly installed. - With the project Device set to a Windows-based device, the HTML5 control appears and is enabled in the Toolbox as expected. - With the project Device set to CODESYS Control for Linux SL, the HTML5 control is disabled/missing from the Toolbox entirely, even though it's installed in the repository. This points to the Linux SL device description simply not declaring overlay/HTML5 support, rather than a missing package or Debian-side dependency (WebVisu itself already works fine for standard/native visualization elements on this same target). Questions 1. Does CODESYS Control for Linux SL currently support WebVisu overlay (and therefore custom HTML5 controls)? I found documentation stating overlay support for target visualizations (Windows and Linux) was added starting with CODESYS Development System V3.5.17.0, but that seems to refer to TargetVisu, and our case is WebVisu-only on a Linux runtime. 2. If not currently supported, is this on a roadmap, or is there a different Linux runtime package/edition that does support WebVisu overlay for HTML5 controls? 3. Is there any Linux-side configuration or package needed to enable this (given the check appears to happen against a static device capability declaration rather than a live server check), or is this purely a matter of the device description bundled with the current Control for Linux SL package? Thanks in advance for any pointers.
Last updated: 2026-08-05

Post by benediktenger on Access project information of references library by script ^{CODESYS Forge talk (Post)}
Hi, I need to accesss to project information of a referenced library in the project. At least I need the "Released" flag from these information to check that no project gets shipped with unreleased libraries. Unfortunally, I do not get this information by script. I archieved to get the library reference object and the managed library object but both won't give me this flag but only basic information like company, name, version, etc. Here is my code: # get the library refernces proj = projects.primary objects = proj.get_children(recursive=True) for object in objects: if object.is_libman: for libref in iter(object): if libref.is_placeholder and isinstance(libref.effective_resolution,str): print(libref) print(libref.name) # get the managed libraries libs = librarymanager.get_all_libraries() for lib in libs: print(lib.displayname) print(lib.version) Does somebody know how do get these information?
Last updated: 2023-10-23

Post by askic on Name Validation of Visualization objects ^{CODESYS Forge talk (Post)}
Hello, In my projects, I'm following this recommendation about the rule names in Codesys https://content.helpme-codesys.com/en/CODESYS%20Development%20System/_cds_rules.html, so I always use backtick identifiers, not only for variables, but also for the object names. However, I have noticed that in the current version of Codesys, when adding Visu object, it is not allowed to used these identifiers in the name. This is very different from all other objects like, folder names, POU names, Variable list names etc. I wonder if there is some hidden settings I can use to enable backtick identifiers in the Visu object names? Attached is a screenshot with the details. Thank you!
Last updated: 2025-01-10

Sort by relevance or date