Post by baotthitawat on SCADA Systems Are Becoming Easier to Integrate With Modern Applications ^{CODESYS Forge talk (Post)}
One thing I’ve been seeing recently is that more industrial systems are starting to expose realtime SCADA data through APIs instead of keeping everything isolated inside the local monitoring software. This makes integration much easier for cloud platforms, mobile dashboards, AI analytics, and enterprise applications that need realtime industrial data. Instead of exporting reports manually or building complicated middleware, APIs allow external systems to access SCADA data directly in realtime. I think this becomes especially useful for applications like wastewater treatment monitoring, where operators need better visibility into alarms, equipment status, and operational conditions across different locations. Feels like modern SCADA is slowly evolving from a standalone monitoring platform into part of a larger connected industrial ecosystem.
Last updated: 2026-05-28

Post by baotthitawat on SCADA Systems Are Becoming Easier to Integrate With Modern Applications ^{CODESYS Forge talk (Post)}
One thing I’ve been seeing recently is that more industrial systems are starting to expose realtime SCADA data through APIs instead of keeping everything isolated inside the local monitoring software. This makes integration much easier for cloud platforms, mobile dashboards, AI analytics, and enterprise applications that need realtime industrial data. Instead of exporting reports manually or building complicated middleware, APIs allow external systems to access SCADA data directly in realtime. I think this becomes especially useful for applications like wastewater treatment monitoring, where operators need better visibility into alarms, equipment status, and operational conditions across different locations. Feels like modern SCADA is slowly evolving from a standalone monitoring platform into part of a larger connected industrial ecosystem.
Last updated: 2026-05-28

Post by baotthitawat on SCADA Systems Are Becoming Easier to Integrate With Modern Applications ^{CODESYS Forge talk (Post)}
One thing I’ve been seeing recently is that more industrial systems are starting to expose realtime SCADA data through APIs instead of keeping everything isolated inside the local monitoring software. This makes integration much easier for cloud platforms, mobile dashboards, AI analytics, and enterprise applications that need realtime industrial data. Instead of exporting reports manually or building complicated middleware, APIs allow external systems to access SCADA data directly in realtime. I think this becomes especially useful for applications like wastewater treatment monitoring, where operators need better visibility into alarms, equipment status, and operational conditions across different locations. Feels like modern SCADA is slowly evolving from a standalone monitoring platform into part of a larger connected industrial ecosystem.
Last updated: 2026-05-28

Post by brouwyka on JSONByteArrayWriter problem? ^{CODESYS Forge talk (Post)}
Hey there! I am currently running into the exact same issue. The JsonData object has all inexes & parent indexes in the way I expect, everything is correctly "linked". It purely seems that the writer is incorrectly parsing said JsonData, not based on parent & child index, but on something else that breaks it and puts things at the root, instead of the specified parent index. Did you ever manage to find a solution, or another way of achieving your JSON composing? I'm currently working on Codesys V3.5 SP19 Patch 7 with IIOT Libraries SL 1.13.0.0, specifically JSON Utilities SL 1.13.0.0 (to send requests to APIs with JSON bodies using Web Client SL 1.13.0.0).
Last updated: 2026-06-08

Post by brouwyka on JSON Utilities - JSON file written with invalid structure ^{CODESYS Forge talk (Post)}
Hey there! I am currently running into the exact same issue (and have also posted to a similar post here: https://forge.codesys.com/forge/talk/Engineering/thread/c45929e2f1/#e27f). The JsonData object has all inexes & parent indexes in the way I expect, everything is correctly "linked". It purely seems that the writer is incorrectly parsing said JsonData, not based on parent & child index, but on something else that breaks it and puts things at the root, instead of the specified parent index. Did you ever manage to find a solution, or another way of achieving your JSON composing? I'm currently working on Codesys V3.5 SP19 Patch 7 with IIOT Libraries SL 1.13.0.0, specifically JSON Utilities SL 1.13.0.0 (to send requests to APIs with JSON bodies using Web Client SL 1.13.0.0).
Last updated: 2026-06-08

Post by gseidel on Limit Axis CNC Jerk using SMC_Polynomial_AbsMaxLocs ^{CODESYS Forge talk (Post)}
Dear josepmariarams, this (internal) function has been removed with SoftMotion 4.17.0.0. We do not have public functions to compute the extrema of a polynomial. On which polynomials exactly did you call SMC_Polynomial_AbsMaxLocs? (Maybe if I understand better how you limit the jerk I can come up with an alternative.) There is no functionality to limit the jerk of individual axes in the CNC. With SMC_LimitDynamics, you can limit the velocity and acceleration of cartesian (X/Y/Z) and additional (P/Q/U/V/W/A/B/C) axes, but not the jerk. And with a quadratic ramp type you can limit the jerk on the path. Best regards, Georg
Last updated: 2026-06-10

Post by cd-tt on cannot connect ot linux runtime: device does not answer the scanrequest ^{CODESYS Forge talk (Post)}
I have the following setup: Proxmox PC with a debian 13 VM running CODESYS Control Linux SL and Edge Gateway. Installation method was through the Deploy Control SL and went rather smoothly. In my Device Tab I find the gateway and when scanning my network I also find my runtime. I want to connect and get promted that I should add a user. After setting up the user I get an error saying, that the device is not responding my scanrequest. Deploy Control SL Operation saying everythings up and running. I can confirm that from the terminal on the VM with "systemctl status codesyscontrol" and "systemctl status codesysgateway". I am running out of ideas how to fix that issue. Can anybody help? Screenshots attached.
Last updated: 2026-06-11

Post by hluecke on Codesys Virtual Safe Control mit Weidmüller UR20 FSOE Modulen ^{CODESYS Forge talk (Post)}
Hallo, ich versuche mit der Codesys Virtual Safe Control zwei Weidmüller UR20 FSOE Module zu betreiben. Allerdings läuft das zweite Modul nie an (Diagnosecode 16#C105), auch die Prozessdaten werden nicht aktualisiert. Jedes Modul einzeln läuft, auch bei getauschter Reihenfolge läuft immer das zweite Modul nicht an. Codesys Version 3.5.22.30 mit den aktuellsten Packages. Weidmüller UR20 FBC-EC und die Module auf aktuellem Firmwarestand, neueste Gerätebschreibungsdateien. Was mich dabei auch irritiert, ist dass beim ersten Gerät im E/A-Abbild mehr Ausgänge angezeigt werden, als beim Zweiten. Hat schon einmal jemand so eine Kombination in Betrieb gehabt oder ein ähnliches Verhalten erlebt? Vielen Dank!
Last updated: 2026-09-30

Post by jami on Reading multiple lines from csv file ^{CODESYS Forge talk (Post)}
Hello, i am trying to read multiple lines from csv file with caa file library and oscat. I have wrote 7 lines in the csv with separation '$R$L'. In my "extracting values" part I check line feeds and chars. After that I convert my buffer to string with oscat but I'm only able to read the first line from the csv. No matter if I even change start position where I start converting the buffer, I only get the first line. Here's my code for the reading and extracting value parts: 4: (*Reading the file*) fileread.hFile := filehandle; fileread.pBuffer := ADR(buffer); filesize1:=SIZEOF (buffer); fileread.szbuffer:=filesize1; fileread.udiTimeOut := 100000; fileread(xExecute := TRUE); IF fileRead.xDone THEN iFilesize:=TO_INT(fileread.szSize); writestate:=3; fileRead.xExecute := FALSE; END_IF 5: (*Extracting values*) //here i check the number of line feeds and chars. It works WHILE i < ifilesize DO c:=buffer[i]; IF c= 10 THEN IF lineindex<=99 THEN lineIndex := lineIndex + 1; END_IF ELSIF c <> 13 THEN IF charIndex <= 1000 THEN charIndex := charIndex + 1; END_IF END_IF i := i + 1; END_WHILE // Here i convert the buffer to string and transfer it to filelines:ARRAY[0..99] of string[254]. trig(CLK:=BUTTON); IF trig.Q THEN fileLines[i2]:=oscat_basic.BUFFER_TO_STRING(PT:=ADR(buffer), Size:=TO_UINT(fileread.szBuffer), start:=TO_UINT(bufferStart), stop:=TO_UINT(filesize1)); i2:=i2+1; bufferstart:=bufferstart+80; END_IF If anyone has idea how to read multiple lines, it would be nice. Even if you have example codes that work, that would help a lot.
Last updated: 2025-07-18

Post by timvh on Get Alarm status in Codesys ^{CODESYS Forge talk (Post)}
You are right, that you can use the GetState method, but it is not that simple. You first have to get a list of (filtered) alarms from the AlarmManager. You can find an example in Forge how to do this. See https://forge.codesys.com/prj/codesys-example/alarm-manager/home/Home/ Then you can go through this list to get the state of all the (filtered) alarms. See below the code which you could use. This is all based on the example from forge. Create a program: // This example shows how to access alarms via structured text. PROGRAM PLC_PRG VAR xInit : BOOL := TRUE; udiResult : UDINT; fbAlarmFilterCriteriaAll : FB_AlarmFilterCriteriaAll; fbAlarmManagerClient : FB_AlarmManagerClient; itfAlarmManagerClient : IAlarmManagerClient := fbAlarmManagerClient; xAlarm1 : BOOL; xAlarm2 : BOOL; xWarning : BOOL; iNrOfAlarmsInAlarmList : INT; iNrOfActiveAlarmsInAlarmList : INT; paitfAlarm: POINTER TO ARRAY [0..0] OF AlarmManager.IAlarm; iAlarmIndex : INT; eAlarmState: AlarmManager.AlarmState; END_VAR IF xInit THEN xInit := FALSE; fbAlarmManagerClient.itfAlarmFilterCriteria := fbAlarmFilterCriteriaAll; // register alarm client to get updated about alarm status / changes udiResult := AlarmManager.g_AlarmHandler.RegisterClient(itfAlarmManagerClient, 0, 0); END_IF // Polling the number of alarms udiResult := AlarmManager.g_AlarmHandler.GetActiveAlarms(itfAlarmManagerClient, parritfActiveAlarms => paitfAlarm, iCountActiveAlarms => iNrOfAlarmsInAlarmList); iAlarmIndex := 0; iNrOfActiveAlarmsInAlarmList := 0; WHILE iAlarmIndex < iNrOfAlarmsInAlarmList DO eAlarmState := paitfAlarm^[iAlarmIndex].GetState(); IF eAlarmState = AlarmManager.AlarmState.Active OR eAlarmState = AlarmManager.AlarmState.ActiveAcknowledged THEN iNrOfActiveAlarmsInAlarmList := iNrOfActiveAlarmsInAlarmList + 1; END_IF iAlarmIndex := iAlarmIndex + 1; END_WHILE See below some details about the function blocks: One function block should implement the IAlarmFilterCriteria interface. This can be empty except a few methods. FUNCTION_BLOCK FB_AlarmFilterCriteriaAll IMPLEMENTS AlarmManager.IAlarmFilterCriteria Method implementation (others related to interface are empty) METHOD AreAllAlarmClassesSelected : BOOL AreAllAlarmClassesSelected := TRUE; METHOD AreAllAlarmGroupsSelected : BOOL AreAllAlarmGroupsSelected := TRUE; METHOD GetPriorityFrom : USINT GetPriorityFrom := 0; METHOD GetPriorityTo : USINT GetPriorityTo := 255; The other function block should implement IAlarmManagerClient and get a reference to the FB which implements the IAlarmFilterCriteria FUNCTION_BLOCK FB_AlarmManagerClient IMPLEMENTS AlarmManager.IAlarmManagerClient VAR_INPUT itfAlarmFilterCriteria: AlarmManager.IAlarmFilterCriteria; END_VAR Method implementation (others related to the interface are empty) METHOD GetFilterCriteria : AlarmManager.IAlarmFilterCriteria // see VAR_INPUT for filter GetFilterCriteria := itfAlarmFilterCriteria; Off course you have to add the AlarmManager to your application and add some alarms to it.
Last updated: 2025-09-02

Post by mondinmr on Patched Wine packages for Ubuntu and CODESYS 3.5 ^{CODESYS Forge talk (Post)}
I have now published Ubuntu amd64 packages of my patched Wine build for CODESYS, targeting Ubuntu 22.04, 24.04, 26.04 and 26.10. The packages are based on Wine 11.20 and include all five compatibility patches covering NCrypt, thread suspension, security tokens, service tokens and local WMI marshalling. Both 32-bit and 64-bit Windows applications are supported through WoW64. In my working environment, CODESYS 3.5 SP21 successfully compiled and went online with a very complex project containing hundreds of thousands of lines of code and extensive use of polymorphism. PPA and installation All four binary builds have completed successfully and are now published and available through APT. Wine ADV for CODESYS PPA sudo add-apt-repository ppa:mondinmr/wine-adv sudo apt update sudo apt install wine-adv The runtime installs under /opt/wine-adv and provides dedicated commands, allowing it to coexist with your existing Wine installation. For example, to launch CODESYS from an existing dedicated prefix: WINEPREFIX="$HOME/.wine.codesys" wine-adv \ 'C:\Program Files\CODESYS 3.5.21.30\CODESYS\Common\CODESYS.exe' Adjust the executable path to match your installed version. Use the same WINEPREFIX when running the CODESYS installer or installing its prerequisites. The package contains the patched Wine runtime. CODESYS and its required Microsoft .NET components must be installed separately inside the prefix. Source code, patches and packaging are available on the project page. This is an experimental community build. Feedback and test results from other users are welcome! CODESYS Installer and CodeMeter licensing are also working in my setup. For CodeMeter, I use the native Linux CodeMeter runtime, while the Windows applications run under the patched Wine build.
Last updated: 2026-10-31

Post by dclements on Feature Request: Read-Only References / Pointer-to-Const Support ^{CODESYS Forge talk (Post)}
I would like to suggest adding support for persistent read-only references or pointers in CODESYS, similar to a C++ pointer-to-const (const T*). For example, something conceptually similar to: POINTER TO CONSTANT ST_MyData or REFERENCE TO CONSTANT ST_MyData The important distinction is that the reference itself may still be passed around or reassigned, but the referenced object cannot be modified through that reference. CODESYS currently supports VAR_IN_OUT CONSTANT, which provides read-only reference semantics for parameters, but there does not appear to be an equivalent type that can be stored in a variable or returned from a method. A practical use case is a registry that owns long-lived definitions. The registry needs to retain ownership of the data while downstream systems maintain persistent references to it. Currently, the main options are: Return the struct by value, which loses reference semantics and requires a copy. Return POINTER TO ST_Definition, which allows consumers to modify registry-owned data. Convert the structure into a Function Block and expose a getter-only interface, which provides the desired encapsulation but introduces more complexity and memory overhead. A read-only reference/pointer type would allow libraries to expose persistent, zero-copy access to internally owned data while preserving encapsulation. This would be particularly useful for library APIs and object-oriented CODESYS architectures where ownership of data should remain with one component while other components are allowed to observe it. Similar requests for constant references/pointers have been discussed on CODESYS Forge previously, so this appears to be a recurring use case rather than something specific to one application.
Last updated: 2026-09-01

Post by kevinl on Weidmüller und u-OS bugs ^{CODESYS Forge talk (Post)}
Hallo zusammen Wir setzen mehrere Weidmüller UC20-WL2000 mit CODESYS Runtime und System-Bus ein und kämpfen seit einiger Zeit mit Problemen, für die wir bisher keine Ursache finden konnten. Aktuell beobachten wir zwei Phänomene: System-Bus Probleme Bei einer Anlage verlieren die I/O-Module sporadisch die Verbindung. Im Log erscheinen Meldungen wie: SLIO:CheckModule missing NotReachable Module Unplugged Nach diversen Updates (u-OS 2.7, aktuelle Runtime, aktuelles CODESYS) wurde das Verhalten eher schlechter statt besser. Anfangs traten die Fehler sporadisch auf, inzwischen funktioniert der System-Bus teilweise gar nicht mehr. Auch ein Downgrade auf eine ältere u-OS Version half nicht wirklich, aber ev ist es mit der aktuellen Runtime nicht kompatibel. Probleme nach Spannungsunterbruch / Neustart Mehrfach hatten wir bereits den Fall, dass eine Steuerung nach einem Spannungsunterbruch oder Neustart nicht mehr vollständig hochkommt. Teilweise startet die CODESYS Runtime nicht mehr (vermutlich aufgrund von Problemen mit Persistent-Daten), in einem aktuellen Fall ist zusätzlich das u-OS Backend nicht mehr erreichbar. Die Welcome-Seite erscheint noch, beim Login läuft der Request jedoch in einen 504 Gateway Timeout. Hardware: UC20-WL2000 u-OS 2.x System-Bus mit mehreren UR20 Modulen CODESYS Control SL Runtime Mich würde interessieren: Hat jemand ähnliche Erfahrungen mit UC20-WL2000 oder u-OS gemacht? Gibt es bekannte Probleme mit dem System-Bus? Gibt es Workarounds bezüglich Persistent-Daten oder Recovery nach Spannungsunterbruch? Hat jemand ähnliche 504-Fehler im u-OS Backend gesehen? Vielen Dank für jeden Hinweis.
Last updated: 2026-06-05

Sort by relevance or date