Post by eschwellinger on codesys installer deletes itself instead of updating ^{CODESYS Forge talk (Post)}
I would try to use: https://store.codesys.com/de/codesys-installer.html this standalone version. Seems if your version out of SP19 setup have some update problem.
Last updated: 2026-08-11

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

codesys installer deletes itself instead of updating ^{CODESYS Forge talk (Thread)}
codesys installer deletes itself instead of updating
Last updated: 2026-08-11

Post by manuknecht on Persistence Manager does not save alphabetically first value ^{CODESYS Forge talk (Post)}
Update: As of now (CODESYS V3.5 SP21 Patch 6) this Bug was fixed.
Last updated: 2026-08-12

Persistence Manager does not save alphabetically first value ^{CODESYS Forge talk (Thread)}
Persistence Manager does not save alphabetically first value
Last updated: 2026-08-12

Post by leag on Reset device password Festo PLC ^{CODESYS Forge talk (Post)}
Hi, I am new to CODESYS, and I want to program a new FESTO, but I am getting this authentication screen. I don't remember the password. I tried with Administrator/Administrator and some other defaults I found online but nothing works. I also tried searching for CODESYSControl_User.cfg and many other recommended directories but I dont seem to have any of them (like CODESYSControlWinV3x64) Could you please help me understand what I need to reset? Thanks a lot
Last updated: 2026-08-12

Post by eschwellinger on Reset device password Festo PLC ^{CODESYS Forge talk (Post)}
these credentials are saved in the plc - you need to ask Festo how to do this.
Last updated: 2026-08-13

Reset device password Festo PLC ^{CODESYS Forge talk (Thread)}
Reset device password Festo PLC
Last updated: 2026-08-13

Post by hammer on Cartesian XY Chart — 2-D array binding: "Element to use" enumerates the wrong dimension ^{CODESYS Forge talk (Post)}
Title: Cartesian XY Chart — 2-D array binding: "Element to use" enumerates the wrong dimension; documented example (Dialog: XY Chart Configuration, "Two-dimensional array of base type REAL") appears transposed Product / version: CODESYS Development System V3.5 SP21 Patch 40 (3.5.21.40). Cartesian XY Chart visualization element (System_VisuElemXYChart / VisuElemXYChart). Summary: When a curve's Data X/Data Y is bound to a two-dimensional array, the element treats the last array dimension as the per-point record (the one selected by "Element to use") and iterates the first dimension as the sequence of curve points. The online documentation's worked example has the dimensions in the opposite order, so following it produces a non-functional curve and a nonsensical "Element to use" list. Steps to reproduce (fails — matches the documented layout): 1. Declare aData : ARRAY[0..1, 0..4095] OF LREAL; (2 data sets × 4096 points, i.e. first dimension = set, second = point). 2. In XY Chart Configuration, bind a curve's Data X (and Y) Variable to this array. 3. Observe the "Element to use" combobox. Actual result: The "Element to use" combobox lists 4096 entries (the indices of the second dimension) instead of 2 (the data sets in the first dimension). Selecting a row does not produce the expected curve; at most a single/degenerate point is plotted. Steps to reproduce (works — transposed): 1. Declare aData : ARRAY[0..4095, 0..1] OF LREAL; (points first, set second). 2. Bind Data X/Y to this array; "Element to use" now correctly lists [0] and [1]. 3. Populate aData[point, set] and the curve plots as expected. Expected result: Either the documented example should select the data set from the first dimension (as its [1]/[2] "Element to use" implies), or the documentation should state that the last dimension is the record dimension (stride) and the first dimension is the point sequence — consistent with how the element actually behaves. Analysis: The behavior is self-consistent if the element always walks a single array by a fixed byte stride, reading one element per point — the same mechanism as the documented "one-dimensional array of a DUT" case, where it strides by SIZEOF(DUT) and "Element to use" picks the member offset. For a 2-D array the record is the last dimension: to plot column/set c it starts at [0, c] and strides by the last-dimension length to reach [1, c], [2, c], … (row-major layout makes this a contiguous column walk). Under that rule, ARRAY[0..N, 0..1] is correct (record length 2 → "Element to use" [0]/[1]), and the documented ARRAY[1..2, 1..50] with "Element to use" [1]/[2] is transposed. Documentation reference: Dialog: XY Chart Configuration → Data X / Data Y → "Example: Two-dimensional array of the base type REAL" (ARRAY[1..2, 1..50], Element to use [1]/[2], "100 array values are displayed"). This example does not plot as described in 3.5.21.40; transposing to ARRAY[1..50, 1..2] does. Request: Please confirm whether this is (a) a documentation error (example dimensions reversed) or (b) an element defect (combobox enumerates the wrong dimension). Either way, a corrected example plus an explicit statement of which dimension is the point sequence vs. the record/stride dimension would prevent others from hitting this. Two separate 1-D arrays for Data X and Data Y work correctly and are unaffected.
Last updated: 2026-08-14

Cartesian XY Chart — 2-D array binding: "Element to use" enumerates the wrong dimension ^{CODESYS Forge talk (Thread)}
Cartesian XY Chart — 2-D array binding: "Element to use" enumerates the wrong dimension
Last updated: 2026-08-14

Post by lmarmonti on Login problem with FileTransfer on Raspberry Pi 5 ^{CODESYS Forge talk (Post)}
Last updated: 2026-08-18

Login problem with FileTransfer on Raspberry Pi 5 ^{CODESYS Forge talk (Thread)}
Login problem with FileTransfer on Raspberry Pi 5
Last updated: 2026-08-18

Post by lmarmonti on Login problem with FileTransfer on Raspberry Pi 5 ^{CODESYS Forge talk (Post)}
Thanks. If I understand correctly, this is a known historical CODESYS bug
Last updated: 2026-08-18

Post by jari-koivuluoma on Comparing between SP19 patch 5 and patch 7 ^{CODESYS Forge talk (Post)}
Hello. Has anyone here used project compare tool across different versions of Codesys? I tried the compare of the title but it does not seem to do much. It lets me choose the project files and then seems to be comparing but no results are ever shown. If the compare tool cannot be used how else would I keep 2 nearly identical projects in sync when the versions differ? On the other hand it might be possible to just have one project but then I would need to use the older codesys with older target device description to develop for devices that have newer device description. Codesys will let me do that but its not recommending it. Any advice?
Last updated: 2026-08-20

Post by automa on SBOM ^{CODESYS Forge talk (Post)}
Hi, How do you create your SBOM in Codesys. I have been searching for this topic but couldn't find any useful information. I am referring to making an exported list of all libraries used in the project. I have developed a python script that exports them, but I am open for ideas of beast practice
Last updated: 2026-08-21

Cannot download program to CR1074 – Version mismatch error ^{CODESYS Forge talk (Thread)}
Cannot download program to CR1074 – Version mismatch error
Last updated: 2026-08-21

Post by megasilver on Cannot download program to CR1074 – Version mismatch error ^{CODESYS Forge talk (Post)}
Hello, I am having a problem downloading my application to an ifm CR1074 using CODESYS. When I try to download the program to the controller, I get the following errors: [FATAL ERROR] Version mismatch at: 'KEYBOARD_SET_MAPPING' Requested version: 2.0.0.12 Implemented version: 3.4.0.0 [FATAL ERROR] Version mismatch at: 'SYSCFG_SPLASH_SET_SPLASH_SCREEN_VISIBLE' Requested version: 2.0.0.12 Implemented version: 3.4.0.0 [FATAL ERROR] Version mismatch at: 'SYSTEM_IO_BACKLIGHT_SET_CURRENT_BACKLIGHT_BLOCKING' Requested version: 2.0.0.12 Implemented version: 3.4.0.0 [FATAL ERROR] Version mismatch at: 'SYSTEM_IO_BACKLIGHT_SET_CURRENT_BACKLIGHT' Requested version: 2.0.0.12 Implemented version: 3.4.0.0 [FATAL ERROR] Version mismatch at: 'KEYBOARD_RESET_LEDS_BLOCKING' Requested version: 2.0.0.12 Implemented version: 3.4.0.0 [FATAL ERROR] Version mismatch at: 'KEYBOARD_SET_LED_COLOR' Requested version: 2.0.0.12 Implemented version: 3.4.0.0 [FATAL ERROR] Version mismatch at: 'SYSCFG_DEVINFO_GET_KEYBOARDS_INFO' Requested version: 2.0.0.12 Implemented version: 3.4.0.0 The controller is running an OS version that should be compatible with CODESYS 3.5 SP16, and I am using the latest available ifm/ecomatDisplay package for this OS version. Therefore, I do not think this is simply a CODESYS or OS compatibility issue. It looks like the application expects system functions with version 2.0.0.12, while the controller implements version 3.4.0.0. Could this be caused by an incorrect or outdated library, device description, package installation, or a mismatch between the libraries used in the project and the libraries installed on the CR1074? What would be the correct way to identify which component is requesting version 2.0.0.12 and how can I resolve this version mismatch? Thank you for your help.
Last updated: 2026-08-21

Post by luca03 on OPC UA information model into the Communication Manager ^{CODESYS Forge talk (Post)}
Hello, unfortunately I am unable to load an OPC UA information model as a NodeSet2.xml file into the CODESYS Communication Manager. Importing via Tools -> OPC UA Information Model Repository still works, but when I try to load the model explicitly, CODESYS crashes without displaying an error message. Has anyone else encountered this problem, or does anyone have any suggestions? Thanks in advance
Last updated: 2026-08-22

OPC UA information model into the Communication Manager ^{CODESYS Forge talk (Thread)}
OPC UA information model into the Communication Manager
Last updated: 2026-08-22

Advice on OOP hardware I/O code structure ^{CODESYS Forge talk (Thread)}
Advice on OOP hardware I/O code structure
Last updated: 2026-08-31

Exception handler return value purpose in _CODESYS 3.5 ^{CODESYS Forge talk (Thread)}
Exception handler return value purpose in _CODESYS 3.5
Last updated: 2026-08-31

Post by hluecke on Codesys Virtual Safe Control startet nicht (mehr) ^{CODESYS Forge talk (Post)}
Hallo, ich versuche seit einiger Zeit eine virtuelle Codesys Control für Linux in Verbindung mit einer Virtual Safe Control ans Laufen zu bringen. Seit zwei Tagen, ohne dass eine Änderung gemacht wurde (auch keine Betriebssystem Updates), startet die Safe Control gar nicht mehr und ich erhalte die Fehlermeldung "Eine Ausnahme vom Typ "CODESYS.VirtualPlcCommunicator.VirtualApiException" wurde ausgelöst". Wenn man in den Operationen die VPLC manuell startet, wird sie als laufend angezeigt, bis man aktualisiert. Ich habe die Packages schon neu installiert und auf die aktuellste Version upgedated, keine Änderung. Ein Log lässt sich nicht abrufen. Hat jemand Erfahrung, was dieser Fehler bedeutet und wie man ihn beheben kann?
Last updated: 2026-09-01

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

Feature Request: Read-Only References / Pointer-to-Const Support ^{CODESYS Forge talk (Thread)}
Feature Request: Read-Only References / Pointer-to-Const Support
Last updated: 2026-09-01

Post by oscardelmagno on Codesys v3.5.22.10 - Internal error:System.AggregateException...Value cannot be null...Parameter name: expLValue ^{CODESYS Forge talk (Post)}
actualy I've solved the problem by creating a new project and copying the file.
Last updated: 2026-09-01

Sort by relevance or date