TextList name error (fake) ^{CODESYS Forge talk (Thread)}
TextList name error (fake)
Last updated: 2026-06-05

Home (version 1) discussion ^{chralyn wiki (Thread)}
Home (version 1) discussion
Last updated: 2026-06-05

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

Home (version 1) discussion ^{asarikhani wiki (Thread)}
Home (version 1) discussion
Last updated: 2026-06-06

Home (version 1) discussion ^{ntphx wiki (Thread)}
Home (version 1) discussion
Last updated: 2026-06-06

blog Discussion ^{brouwyka blog (Discussion)}
Forum for blog comments
Last updated: 2026-06-08

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

wiki Discussion ^{brouwyka wiki (Discussion)}
Forum for wiki comments
Last updated: 2026-06-08

(no subject) ^{brouwyka wiki (Thread)}
Last updated: 2026-06-08

Home ^{brouwyka wiki (WikiPage)}
Project Members: brouwyka (admin)
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

Home (version 1) discussion ^{brouwyka wiki (Thread)}
Home (version 1) discussion
Last updated: 2026-06-08

Post by brouwyka on JSONByteArrayWriter string result incorrect order ^{CODESYS Forge talk (Post)}
Hello everybody! We are currently working on implementing a call to an API that tracks data sent to it through a JSON body. Versions: CODESYS V3.5 SP19 Patch 7 using IIOT Libraries SL license, specifically JSON Utilities SL version 1.13.0.0. For simplicity, let's say we want to construct the following JSON body for our request (simplified to just 1 key-value pair in each of the array objects to keep things shorter, but we'd have multiple fields in each in reality): { "id": "machine_1", "readings": [ { "temp_mid": 153.8 }, { "temp_mid": 98.3 } ], "status": "RUNNING" } However, our "readings" data is added over time, not in creation, so calls to the builder would be somewhat out of order. In a simplified manner, our calls would look like this: jsonBuilder(pJsonData := JsonData, diRootObj => rootJsonIndex); // rootJsonIndex = 0. // Set "id" at root JSON object. wsValue := "machine_1"; jsonBuilder.SetKeyWithValue("id", wsValue, diParentIndex := rootJsonIndex); // JSONData KEY: diParentIndex = 0 & diIndex = 1, VALUE: diParentIndex = 1 & diIndex = 2. // ... Time passes, we get our first reading to add ... // The "readings" array does not exist yet, so we make it first at root JSON object before adding our first reading. readingsJsonArrayIndex := jsonBuilder.SetKeyWithArray("readings", diParentIndex := rootJsonIndex); // JSONData KEY: diParentIndex = 0 & diIndex = 3, VALUE: diParentIndex = 3 & diIndex = 4. // Then add the first reading, for which we first have to make an object. readingsJsonArrayObjectIndex := jsonBuilder.SetObject(diParentIndex := readingsJsonArrayIndex); // JSONData OBJECT: diParentIndex = 4 & diIndex = 5. // And then we add the field(s) in the object for the first reading. // NOTE the use of `readingsJsonArrayObjectIndex` so we set the field(s) in the first object in the array. rValue := 153.8; jsonBuilder.SetKeyWithValue("temp_mid", wsValue, diParentIndex := readingsJsonArrayObjectIndex); // JSONData KEY: diParentIndex = 5 & diIndex = 6, VALUE: diParentIndex = 6 & diIndex = 7. // ... Time passes, we want to add another root-JSON-level field ... // Set "status" at root JSON object. wsValue := "RUNNING"; jsonBuilder.SetKeyWithValue("status", wsValue, diParentIndex := rootJsonIndex); // JSONData KEY: diParentIndex = 0 & diIndex = 8, VALUE: diParentIndex = 8 & diIndex = 9. // ... Time passes, we want to add a second reading ... // "readings" array exists, so add the second reading, but first we have to make another object. // NOTE the re-use of the earlier stored `readingsJsonArrayIndex`, so we add the new object to that previously created array. readingsJsonArrayObjectIndex := jsonBuilder.SetObject(diParentIndex := readingsJsonArrayIndex); // JSONData OBJECT: diParentIndex = 4 & diIndex = 10. // And then we add the field(s) in the object for the first reading. // NOTE the use of `readingsJsonArrayObjectIndex` so we set the field(s) in the SECOND(, new) object in the array. rValue := 98.3; jsonBuilder.SetKeyWithValue("temp_mid", wsValue, diParentIndex := rootJsonIndex); // JSONData KEY: diParentIndex = 10 & diIndex = 11, VALUE: diParentIndex = 11 & diIndex = 12. // ... Finally, we want to send to the API, so we must convert the builder to data the client accepts as a body ... xTestWriteToJsonArray := TRUE; jsonArrayWriter( xExecute := xTestWriteToJsonArray, pwData := ADR(jsonDataString), udiSize := SIZEOF(jsonDataString), jsonData := JsonData^ ); IF jsonArrayWriter.xDone THEN // The writer was successful, the `jsonDataString` VAR should now contain a WString copy of the JSON object from the builder. xTestWriteToJsonArray := FALSE; END_IF We see that the JsonData STRUCT is correctly organised (in terms of the diParentIndex & diIndex set by it for each JsonElement) as we expect, as outlined in my comments in the simplified code above. However, as soon as we pass it to the jsonArrayWriter (which is a JSON.JSONByteArrayWriter), the resulting jsonDataString does not match our expectations, instead coming out like this: { "id": "machine_1", "readings": [ { "temp_mid": 153.8 } ] } { "temp_mid": 98.3 } "status": "RUNNING" The behaviour of the JSONByteArrayWriter thus seems to be the problem here. It does not seem to correctly process the children of JsonElements that are ARRAYs when additions to them are done broken up by additions to the lower level JSON OBJECT they are a part of. We have confirmed this by changing the order of the calls in our example to add both readings before adding the "status", in which case we get our expected outcome. However, in reality this is not possible for us - additions to any of the JSON's objects, arrays or array objects may happen at any time after other fields elsewhere in the JSON have been added. Does anyone know a way around this, a fix, or knows a solution we simply have not found? This same phenomenon was also noted on this forum by user @ryusoup at the end of 2023 (https://forge.codesys.com/forge/talk/Engineering/thread/c45929e2f1/#e27f) and user @mtho in early 2024 (https://forge.codesys.com/forge/talk/Engineering/thread/cd1bb450db/#1292) but both topics received no activity beyond both users' opening posts. Looking through the release notes of all the versions of the JSON Utilities SL library, I also did not see any remarks on resolutions of bugs in this vain. Thanks in advance for the assistance!
Last updated: 2026-06-10

Post by brouwyka on #2636 Unable to create topic ^{CODESYS Forge support (Post)}
After about 3 days have passed, I suddenly was able to create the topic I wanted to, so at least that is resolved. However, I would still like to use this ticket to suggest improvements to the website: - In case there is a period before new accounts can make topics, please clarify this somewhere, and also give an appropriate error when a new user still tries to make a topic in this time; - In case it has to do with a rate limiting system, I would suggest reviewing if this is working correctly, and also once again adding clear error messages that state rate limiting is being applied, and how long the remaining cooldown is (normally servers pass this in a header when they return a rate limit status code 429).
Last updated: 2026-06-10

(no subject) ^{CODESYS Forge support (Thread)}
Last updated: 2026-06-10

Ticket #2636: Unable to create topic ^{CODESYS Forge support (Ticket)}
Good morning! I made an account yesterday and have been trying to make a post about an issue I'm running into with the JSON Utilities SL library (1.13.0.0). However, when I try to create a topic (on Engineering), when pressing "Post" the website refreshes but stays on the same "create topic" page, and nothing happens. Refreshing my subscriptions list & the Engineering forum I do not see any post created either. I have attempted using different browsers, incognito mode, clearing cookies and changing networks (office wifi, mobile hotspot, home wifi, all of them) - nothing seems to work. Looking at the network traffic using my browser's developer tools I see no unsuccessful messages, only some redirects (which also seem to work correctly), so I'm really not sure what is going on. My only guess is that an account must be of a certain age to create topics, but I cannot find anything about this anywhere on Codesys Forge (I've gone through all the help pages, ToS, etc). Thank you in advance for your time and effort!2026-06-10 05:55:19.226000 Ticket #2636: Unable to create topic CODESYS Forge forge tickets support False /forge/support/2636/ Ticket Unable to create topic False 1 2026-06-09 07:07:28.601000 2636 Unable to create topic open Good morning! I made an account yesterday and have been trying to make a post about an issue I'm running into with the JSON Utilities SL library (1.13.0.0). However, when I try to create a topic (on Engineering), when pressing "Post" the website refreshes but stays on the same "create topic" page, and nothing happens. Refreshing my subscriptions list & the Engineering forum I do not see any post created either. I have attempted using different browsers, incognito mode, clearing cookies and changing networks (office wifi, mobile hotspot, home wifi, all of them) - nothing seems to work. Looking at the network traffic using my browser's developer tools I see no unsuccessful messages, only some redirects (which also seem to work correctly), so I'm really not sure what is going on. My only guess is that an account must be of a certain age to create topics, but I cannot find anything about this anywhere on Codesys Forge (I've gone through all the help pages, ToS, etc). Thank you in advance for your time and effort! False False 1 0 1 None brouwyka None
Last updated: 2026-06-10

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

Problem with keeping up the distance between two axes ^{CODESYS Forge talk (Thread)}
Problem with keeping up the distance between two axes
Last updated: 2026-06-10

Limit Axis CNC Jerk using SMC_Polynomial_AbsMaxLocs ^{CODESYS Forge talk (Thread)}
Limit Axis CNC Jerk using SMC_Polynomial_AbsMaxLocs
Last updated: 2026-06-10

Post by gseidel on Problem with keeping up the distance between two axes ^{CODESYS Forge talk (Post)}
Hi alex-n, are there any errors before the crash happens: MC_Phasing.Error, MC_Phasing.CommandAborted, what does the PLC log show before the crash? Does one of the drives show an error? You can achieve the same effect as MC_Phasing by using MC_GearIn and MC_MoveSuperImposed. But probably there is some problem in your application independent of MC_Phasing that can lead to the crash. Best regards, Georg
Last updated: 2026-06-10

wiki Discussion ^{cd-tt wiki (Discussion)}
Forum for wiki comments
Last updated: 2026-06-11

blog Discussion ^{cd-tt blog (Discussion)}
Forum for blog comments
Last updated: 2026-06-11

(no subject) ^{cd-tt wiki (Thread)}
Last updated: 2026-06-11

Home ^{cd-tt wiki (WikiPage)}
Project Members: cd-tt (admin)
Last updated: 2026-06-11

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

Sort by relevance or date