Post by miltos on licensing question ^{CODESYS Forge talk (Post)}
Greetings to all, I'm working on a webvisu project on control win V3 x64 runtime, and have purchased 3 licenses for my application. -Codesys Control Standard M -Codesys Visualization L -Codesys Communication M I have them installed on a Codesys usb dongle When I try to download the program, a login error window appears with the message "No valid license found for the webvisualization". The control win v3 communicates with 3 plc, and have enabled communication over codesys V3 communication by adding one datasource for every plc in the datamanager. If I remove the data manager from the project, the rest of the visualisation can be downloaded normally. Do I need to purchase another License and which one? Please find attached the software metrics and the error screen.
Last updated: 2025-10-31

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 caspershes on Checking the device tree, not just the code: what else is worth a static check? ^{CODESYS Forge talk (Post)}
I spend most of my time reviewing other people's CODESYS projects before commissioning, and two kinds of defects keep showing up. Both compile clean. Both read fine. One is in the code. A pause timer whose own input gets cleared inside the branch the timer is supposed to gate: rampDelay(IN := run_2); IF NOT run_2 OR rampDelay.Q THEN run_1 := TRUE; run_2 := FALSE; // the timer's own input, cleared right here ELSE run_1 := FALSE; run_2 := FALSE; END_IF Next scan IN is FALSE, the timer resets, the condition is true again, and the second pump starts immediately. A 30-second ramp delay that actually lasts one task cycle. The setpoint is on the HMI, the operator turns it, and nothing changes. The other is not in the code at all. On one site the outdoor temperature read 0.0 °C in mild weather. The ST was correct, the variable was bound to the channel — but the channel's sensor type was left at "disabled", so nothing was ever digitised. Same class: a module with Disable_module = TRUE, or an analog output bound to a variable while its mode is off. Nothing in the project reports any of this, and the code review never looks there, because the configuration lives in the device tree and not in the POUs. That second class is what pushed me to parse the .export format rather than PLCopenXML alone — the export carries the device tree and the visualization, so "nothing ever writes this alarm variable" stops being a guess and becomes a fact you can check against the screen bindings. Three things about the format that cost me time, in case they save you some: the same device parameter can appear three times (template, internal copy, actual configuration) — the last occurrence is the one in effect; the enum value of a parameter is not in the parameter itself, it is one level down in BaseType/Value; a channel counts as used when a variable is bound to SensorValueN.SensorValue — InputStatus is a bad indicator, people deliberately bind it on spare inputs. So the question. What else would you check automatically, given both the code and the device tree? I am collecting rules from sites, not from style guides, and the configuration side feels largely unexplored. For what it is worth, the checker I use for this is free and runs offline (single exe, no install, nothing uploaded anywhere): https://github.com/caspershes/plc-lint — 43 rules at the moment, reads .export and PLCopenXML. Happy to add rules people here suggest.
Last updated: 6 days ago

Post by carohe on VisuNamespace != null ^{CODESYS Forge talk (Post)}
Hello, this error occured frequently over the past couple of weeks. I found out, when adding a webvisu, CODESYS added Visu libraries in the library manager. One of the libraries was the "VisuElemsAlarm" library. In my case it added this one with the version 4.3.0.0. However another library that also contained the "VisuElemsAlarm", used the "VisuElemsAlarm" with the version "4.4.0.0". After changing the Version "4.4.0.0" and uninstalling this version, the error has not occured anymore. Regards, carohe
Last updated: 2024-04-02

Post by richard-wang on Codesys recipe manager - what does it do? ^{CODESYS Forge talk (Post)}
Hi All Thanks for sharing this information. For whom may not know why always get error code 16#4000 or 16#4002 while performing Recipe commands, the root cause is There is a line need to be inserted in CODESYSControl.cfg file, which is PlaceholderFilePath.1=/var/opt/codesys/PlcLogic/ I am using Pi, therefore the above path is set to my pi unit, after adding above line to my cfg file, all the Recipe commands work fine. But I still do not know how and when this file got modified though.
Last updated: 2024-04-29

Post by paro on send appliaction files to wago plc (codesys 3.5) via ssh ^{CODESYS Forge talk (Post)}
Hi, it is enough to copy the files to /home/codesys/PlcLogic/Application and adding the lines [CmpApp] Application.1=Application to the eRUNTIME.cfg, if your Application in your program is also called "Application". Reboot -> Bootapp should be loaded. If not please check the log /var/log/runtime.log There should be a line which explains why the bootproject is not loaded.
Last updated: 2024-05-29

Post by tyronnosaurus on ReceiveWatchdog FB not working on J1939 P2P PGNs ^{CODESYS Forge talk (Post)}
Hi guys. I've got a device that sends a status message over J1939 and a PLC running Codesys to receive it. This message uses a P2P PGN (as opposed to a broadcast PGN). Codesys can only read it if I mark the J1939_ECU as "Local" (see screenshot 1). The message is received correctly, that is not the problem. The problem is detecting if the message stops being received. Local ECUs have no Watchdog checkbox to detect if the message has been received in the last X seconds. In order to implement a watchdog, I've used a ReceiveWatchdog FB. The same code works well for any non-P2P message, but doesn't work for this particular P2P message I'm trying to monitor. Even if I physically disconnect the device, ReceiveWatchdog.xBusy stays True, and ReceiveWatchdog.xError never triggers due to a timeout error. Is there any caveat in the ReceiveWatchdog FB that makes it unable to monitor P2P PGNs in Local J1939_ECUs?
Last updated: 2024-07-11

Post by william-blandon on RecipeManCommands.ReloadRecipes ^{CODESYS Forge talk (Post)}
Hi Dave. Thanks for your answer. I still struggling with this. I have done everything according with the Codesys help even I have looked in detail at the example. I have double checked the recipe manager configuration and the use of all the methods. There are two methods that do not work as expected. I'm using Codesys 3.5.19.20 and recipe management 4.4.0.0 .CreateRecipe just create a recipe in the recipe definition but do not create the file. This have a walk around just giving a .ReadAndSaveRecipe afterwards. .ReloadRecipes do nothing but do not generate any error as well. After calling it I call the .GetRecipeCount and the number is always 0. When I create a new recipe (using the function block methods) then the number changes. Looks like this method is looking to the wrong directory finding nothing. I don't know if there is a missing configuration in the CODESYSControl.cfg file. I'm thinking in a walk around for this but I need to create a strings array with the recipe names as retentive and making all the management when deleting and adding recipes. Have had some one the same problem?
Last updated: 2024-05-23

Post by bjarne-pagaard on Global Variables ^{CODESYS Forge talk (Post)}
Old thread, I know - but it still has good answers. I would like to add a bit of info to it, as I was having a problem that lead me to this thread, but didn't give an exact answer. I am porting a project to a different PLC architecture. (Wago PFC300) A GVL named 'GVL' in the POUs section of my project was shadowed by a PLC-specific library in the Application->Library Manager. So all the existing references in the device specific code to 'GVL.something' would not resolve. Right-clicking the GVL in the code and 'Go to definition' would point me to the library in the Application Library Manager. All I had to do from there, was right-click the library, and set the property 'Only allow qualified access to all identifiers' in the library.
Last updated: 2025-04-11

Post by kurtk on Modbus TCP Server ^{CODESYS Forge talk (Post)}
ditto I'm just getting my codesys wheels on and the modbus stuff is confusing. I am re-platforming an existing PLC application On that platform one could simply tag variables to register numbers and the whole shooting match could be accessed via modbus and typically holding registers and input registers were treated the same way... On codesys I see there is a modbus TCP server Device I/O mapping tab and a Modbus TCP server IEC objects tab I get the sense that one can configure the serving of variables both/either way but am unclear about the optimum/necessary path. Apparently in the IEC Objects tab one can "ADD" something or other - presumeably channels. I have created a preliminary function block but the Select Function Block window shows nothing to select WTH ? I exported the Device mapping and was surprised to see the entire Device IO map - complete with all the bit-mapped holding/input registers!! WTH!!?? Bit-mapped words are strictly a nichey special purpose application. I am targetting making a couple hundred variables available which would turn into hundreds of pages of IO/mapping Is the FUnction Block IEC objects thingy an alternative to that ? I notice that CODESYS shows the tags which the PLC used to specify the register address... are tags used in CODESYS for any specific hard-core purpose ?
Last updated: 2025-08-19

Post by kunal-pinetics on USB Communication for IP Configuration & Application Update – STM32H Series PLC ^{CODESYS Forge talk (Post)}
Hello everyone, I am currently working on a PLC device based on the STM32H series MCU, running CODESYS. At the moment, I can: Change the Ethernet IP address Update/download the PLC application via Ethernet without any issues. However, I would like to implement the same functionality over USB (or Serial via USB) instead of Ethernet. My goals are: Change the device’s Ethernet IP address via USB Download/update the PLC application via USB communication Possibly use USB as a service/programming interface The hardware platform is based on STM32H series, and I am looking for guidance on: Whether CODESYS supports USB device communication for runtime download If a custom USB CDC (Virtual COM Port) implementation is required Whether a specific CODESYS runtime configuration is needed If a bootloader approach is recommended for application updates via USB If anyone has experience implementing USB communication for runtime download or device configuration on an STM32-based PLC, I would really appreciate your guidance. Thank you in advance for your help.
Last updated: 2026-02-26

Post by simotion on Pointer to Softmotion axis ^{CODESYS Forge talk (Post)}
In my projet I use Softmotion. There are several Softmotion axis (type SM_Drive_Virtual). In the Global Variable List I have an array of pointers to the adress of the Axis. Axis : ARRAY[1..iMaxCntAxes] OF POINTER TO AXIS_REF_SM3 := ADR(AX01_Axis), // [1 ADR(AX02_Axis), // [2] This works, but when compiling I get the message : . [WARNING] E3D: GVL Device: PLC Logic: Application: C0564: A reference to uninitialized variable AX01_Axis is used for initialization of Axis. Accessing the uninitialized variable may result in unexpected behavior. [WARNING] E3D: GVL Device: PLC Logic: Application: C0564: A reference to uninitialized variable AX02_Axis is used for initialization of Axis. Accessing the uninitialized variable may result in unexpected behavior. Is there a way when initializing to force the hardware (softmotion axis) to first initialize and then the Global Variable List?
Last updated: 2023-10-25

Post by kunz on Responsive Design Example ^{CODESYS Forge talk (Post)}
Hello everyone, I have a problem with the example project Responsive Design Example, which is available here in Codesys Forge. I wanted to try switching the visualization depending on the device type. To do this, I used a smartphone to access it. I can see via breakpoints that the Smartphone visualization is selected, but the visualization of the normal monitor still appears on the smartphone. Could there be a problem with the libraries, or why is the device not assigned the correct visualization page? I dont know how do further debuggin or troubleshooting. Here the page to the example: https://forge.codesys.com/prj/codesys-example/responsive-desi/home/Home/ Thank you very much.
Last updated: 2024-06-27

Post by struccc on Problem Reading Registers via Modbus from non Codesys device ^{CODESYS Forge talk (Post)}
Hi, Might be a good idea first to try out the connection and the device with some handy software, like Modbus Poll. There you can see better, what's really going on... - Is it really connected? - What error code does it return? - Can it read from the register address? - Maybe try Input registers and Holding Registers - can make a difference - Sometimes register addresses are messed up: shifted +-1 (mixing of 2 standards) - Sometimes register addresses start with offset 30000, 40000 ... - Are you using the right protocol? - Is it RTU or TCP? Maybe ASCII? - Can even have a look at the data packets, etc... All this is easier to figure out first with some modbus utility... and then to set it up in CODESYS should not be an issue. P.
Last updated: 2025-03-09

Post by elsmart on Sequential read and triggering of Modbs RTU channels in application ^{CODESYS Forge talk (Post)}
Hello I need some help understanding how to use Modbus RTU (COM port) in Codesys enviroment. I defined a Modbus Server device (slave) in device tree and added some channels to read from (function 3). Also I set trigering mode to Application. I have a POU in which I want to trigger each channel one after the other something like this (C code for better visualisation): for (int i = 0; i < channelsCount; i++) { triggerChannel(channelsArray[i]); // Start transmission while(channel.xBusy); // Wait for transmission to complete } I have found ModbusChannel function block documentation but examples are scarce. I don't understand how rising edge triggering works. What would be the best solution for achieving sequntial channel triggering? What is the common way to read multiple Modbus channels once every time a specified POU is executed?
Last updated: 2025-05-16

Post by qkkk on Device Scan ^{CODESYS Forge talk (Post)}
Hello all, I have developed a custom I/O driver in CODESYS that communicates via a Unix Domain Socket. In my DeviceDescription.xml, I have set up the following: <scan supported="true"> <scanfbinstance fbname="IOScanDevice"> The goal is to allow the user to scan for connected I/O modules from the CODESYS GUI ("Scan for Devices") and automatically populate the device tree with detected submodules.</scanfbinstance></scan> The function block IOScanDevice is implemented in the driver library and added to the main device's FB instances. However, when I initiate the scan from the GUI, nothing appears to happen the function is not executed. Is there an example project or driver (open source or from CODESYS Forge) that demonstrates a working custom scan implementation?
Last updated: 2025-05-26

Post by timvh on Codesys 3.5.18.60 – Application Loss and Persistent Data Corruption ^{CODESYS Forge talk (Post)}
Which device do you use? Does this have persistent memory (e.g. NVRAM) available? Maybe first ask your PLC vendor about the possibilities and how they advice to use persistent variables? If you have no NVRAM available, CODESYS will store the variables in a file when the device gracefully shuts down. But on an abrupt power failure, this is not possible. If you have no NVRAM and you want to use persistent variables, then consider using a UPS. In this case when the power is lost, the UPS can keep the power on the PLC which then can gracefully shut down. Alternatively use the Persistence Manager to store the variable values in a file e.g. only on change. See: https://content.helpme-codesys.com/en/CODESYS%20Application%20Composer/ac_pm_overview.html
Last updated: 2025-08-26

Post by bruceae on Special Characters ^{CODESYS Forge talk (Post)}
Hello, I am fairly new to the codesys environment. Is there a reference chart that I can look at in order to write special character in a string? The Special characters that I need to inclue inside the string are as follows; Null Bell Carriage Return I have a TCP_Write command that I am sending to an external device. In order for that device to function properly it needs to see the string with the null and bell characters as the header, followed by the desired command, terminated with the carriage return. Any reference sheet or how to write this in the actual string would be greatly appreciated.
Last updated: 2025-08-26

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 valenting on Runtime not working on raspberry pi Bullseye ^{CODESYS Forge talk (Post)}
Hello I have a problem with Codesys on Raspberry pi with Bullseye The device is not recognized as a Raspberry pi, as I get this error : ooops... this runtime was built for RASPBERRYPI. Hardware version or firmware version not supported! (-18, 0x00000BB8, 0xFFFFFFFB) I'm running Codesys on a compute module 4S with Raspbian GNU/Linux 11 (bullseye), my kernel version is Linux 5.10.90-v7l+ Codesys version is the latest, released last week (4.11.0.0, CODESYS Control V3.5.19.61 for ARM-32Bit - build Feb 22 2024) I know it works on the same device if I use Raspbian 10 (Buster) with Linux 5.4.81-v7l+ kernel, but for some other reasons I have to use Bullseye. What can I do ?
Last updated: 2024-03-01

Post by dhumphries on Not able to see input data coming from eip adapter on codesys ^{CODESYS Forge talk (Post)}
Does the device have a green icon next to it when the PLC is running? If not you have some kind of communication problem, wireshark may be picking up some data but the scanner may not be configured correctly to receive the data. Check the T>O and O>T bytes and make sure they match on both the scanner and adapter. I've had very little success loading a .eds file and having the configuration work without some manual configuration. If you have a green icon, have you enabled the device to always update variables?
Last updated: 2024-03-02

Post by timvh on Version management ^{CODESYS Forge talk (Post)}
This depends on what you want to achieve with installing the latest version and how you manage your projects and repositories. Maybe you also want to update your device (right click on it to update) or maybe your device is depending on certain versions of libraries (go to the library manager in your project and download the missing libraries). An option is also to first create a projectarchive of the current project you have before you install a new version of CODESYS. Then you can open this projectarchive in the new CODESYS version. Especially if you install the latest version of CODESYS in a Sandbox.
Last updated: 2025-12-15

Post by wbj0t on connect IDE to plc that uses modem ppp ^{CODESYS Forge talk (Post)}
Hello everyone! I have an PLC device that uses modem ppp connection to the internet with white IP. Device PPP connection with modem operator established, so I can connect to this device via SSH also within Codesys IDE (check version, info, etc...) BUT, I cant establish connection to this device in the device gateway options for application upload and debugging. How can I do this? Im trying set my device remote IP and port 11740, but, as I understand, it is wrong decision, because the next logic in this connection: local W10 service (Codesys Gateway) listen on 1217, then (some how) this service scanning local networks for seeking any local IP which listening on port 11740, and then connects and writes there. OR IM WRONG?:) W10 tool 'Test-NetConnection' with parameters 'ip -Port 11740' succeeded with True. Need some help, please :)
Last updated: 2024-05-21

Post by transmin01 on CANbus issue ^{CODESYS Forge talk (Post)}
Update: This initial issue was when using a Linux target PLC. Since then I have created a Win10 target PC and the Codesys software reported an issue associated with the device version (see attached). I am assuming this is an incompatibility with the xml file from the manufacturer and the firmware version on the module and I am chasing this up with Beckhoff. Question is, why would this not report with a Linux target?
Last updated: 2023-09-14

Post by fred on Rasperry Control Debian 12 ^{CODESYS Forge talk (Post)}
Hi, I have Proxmox running on a Rasperry 4 and have debian 12 ARM installed here. I wanted to install Codesys Control for Raspberry on it. According to the messages, the runtime environment and the gateway were installed successfully, but I can't find a device to downplay a program. The sudo service codesys start command fails. (see image) Does somebody has any idea? Thank you for your help! Greetings Fred
Last updated: 2023-11-22

Sort by relevance or date