Remote connection to ifm PLC & HMI ^{CODESYS Forge talk (Thread)}
Remote connection to ifm PLC & HMI
Last updated: 2024-04-11

c2iec - translating C to ST ^{CODESYS Forge talk (Thread)}
c2iec - translating C to ST
Last updated: 2024-04-20

Upgrade from codesys 3.5.19 to 3.5.20 ^{CODESYS Forge talk (Thread)}
Upgrade from codesys 3.5.19 to 3.5.20
Last updated: 2024-04-20

Remote connection to ifm PLC & HMI ^{CODESYS Forge talk (Thread)}
Remote connection to ifm PLC & HMI
Last updated: 2024-04-23

Upgrade from codesys 3.5.19 to 3.5.20 ^{CODESYS Forge talk (Thread)}
Upgrade from codesys 3.5.19 to 3.5.20
Last updated: 2024-04-23

Codesys v3.5 Sint to byte ^{CODESYS Forge talk (Thread)}
Codesys v3.5 Sint to byte
Last updated: 2024-04-24

CANOpen SDO to write VISIBLE STRING ^{CODESYS Forge talk (Thread)}
CANOpen SDO to write VISIBLE STRING
Last updated: 2024-04-29

How to reset AzureMQTTClient after error? ^{CODESYS Forge talk (Thread)}
How to reset AzureMQTTClient after error?
Last updated: 2024-06-04

Is it possible to profile builds? ^{CODESYS Forge talk (Thread)}
Is it possible to profile builds?
Last updated: 2024-06-05

Is it possible to profile builds? ^{CODESYS Forge talk (Thread)}
Is it possible to profile builds?
Last updated: 2024-06-06

how to use UseDataExpanding() in datasource ^{CODESYS Forge talk (Thread)}
how to use UseDataExpanding() in datasource
Last updated: 2024-06-17

OPC UA Client failed to connect ^{CODESYS Forge talk (Thread)}
OPC UA Client failed to connect
Last updated: 2025-10-28

Can't get SMC_SmoothPath to work ^{CODESYS Forge talk (Thread)}
Can't get SMC_SmoothPath to work
Last updated: 2026-01-11

Access to the path *** is denied ^{CODESYS Forge talk (Thread)}
Access to the path *** is denied
Last updated: 2025-12-11

Library documentation up to date ^{CODESYS Forge talk (Thread)}
Library documentation up to date
Last updated: 2025-12-22

Deploying to raspberry pi 5 hangs ^{CODESYS Forge talk (Thread)}
Deploying to raspberry pi 5 hangs
Last updated: 2025-12-25

Best practice to reduce CPU load ^{CODESYS Forge talk (Thread)}
Best practice to reduce CPU load
Last updated: 2026-04-21

Connect to Azure IoT Hub ^{CODESYS Forge talk (Thread)}
Connect to Azure IoT Hub
Last updated: 2026-04-24

Unable to install previously installed version ^{CODESYS Forge talk (Thread)}
Unable to install previously installed version
Last updated: 2026-02-20

Connect to Azure IoT Hub ^{CODESYS Forge talk (Thread)}
Connect to Azure IoT Hub
Last updated: 2026-04-27

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

Post by rohitk on CoDeSys libraries for BECKHOFF EL7332/EL7342 ^{CODESYS Forge talk (Post)}
Hi, step 1 : go to beckhoff website, go to required IO card, go to download option in that, go to XML donlowad and download the file Step2 : Go to codesys software, go to tools - deviceRepository - install that downloaded file.
Last updated: 2023-08-24

Post by riccardo on How to allow a user to handle certificates without access to sourcecode? ^{CODESYS Forge talk (Post)}
It would be usefull to me too, I would need to manage HTTPS and OPC UA certificate without perform the access to the whole sorce code project
Last updated: 2023-11-27

Is it possible to link an array of bits to an alarm group to show a lot of alarms at once? ^{CODESYS Forge talk (Thread)}
Is it possible to link an array of bits to an alarm group to show a lot of alarms at once?
Last updated: 2021-07-08

How to transfer data from DINT to Union(16 Bools) which I need to use in Few FBs ^{CODESYS Forge talk (Thread)}
How to transfer data from DINT to Union(16 Bools) which I need to use in Few FBs
Last updated: 2023-12-14

Sort by relevance or date