Home (version 1) discussion ^{axberry wiki (Thread)}
Home (version 1) discussion
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

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

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

(no subject) ^{leag wiki (Thread)}
Last updated: 2026-08-12

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

Home (version 1) discussion ^{leag wiki (Thread)}
Home (version 1) discussion
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

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

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

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

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

(no subject) ^{brandonje wiki (Thread)}
Last updated: 2026-08-20

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

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

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

(no subject) ^{megasilver wiki (Thread)}
Last updated: 2026-08-21

Sort by relevance or date