ARRAY with and ENUM ^{CODESYS Forge talk (Thread)}
ARRAY with and ENUM
Last updated: 2022-06-16

OPCUA array max length? ^{CODESYS Forge talk (Thread)}
OPCUA array max length?
Last updated: 2024-02-19

Post by installwhat on Unable to select VisuDialogs.Numpad in Open Dialog input configuration ^{CODESYS Forge talk (Post)}
data type?
Last updated: 2025-07-16

Post by levih on FbHTTPs_Get how to get data from a website and use it in codesys ^{CODESYS Forge talk (Post)}
You get an array of DWORD into your receive buffer. You need to process this into usable data, before you can fit it into your DUT. I've made it work using FbWrite_ToIEC_ByRule in stead of Fb_JSON_ParseAndModify. I've attached images of the code. You receive the data into ARRAY[0..1023] OF DWORD. Then you use that array as the input for fbWrite_ToIEC_ByRule. To get the output from this you define a rule to fit the expected data structure including nesting levels. The you feed the rule into FbWrite_ToIEC_ByRule and then you can set the output to be of your DUT type.
Last updated: 2025-06-16

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

Unit Tests and C007: Unknown Type ^{CODESYS Forge talk (Thread)}
Unit Tests and C007: Unknown Type
Last updated: 2025-08-27

Question on LZS_DEFINE_ACCU_FLOW service type ^{CODESYS Forge talk (Thread)}
Question on LZS_DEFINE_ACCU_FLOW service type
Last updated: 2007-03-01

Characters inside a string type. ^{CODESYS Forge talk (Thread)}
Characters inside a string type.
Last updated: 2012-03-26

about TYPE AND END_TYPE ^{CODESYS Forge talk (Thread)}
about TYPE AND END_TYPE
Last updated: 2014-10-22

how to FUNCTION type VOID ^{CODESYS Forge talk (Thread)}
how to FUNCTION type VOID
Last updated: 2013-10-18

BIT type in persistent memory ^{CODESYS Forge talk (Thread)}
BIT type in persistent memory
Last updated: 2022-03-17

Cannot convert 'STRING' to type 'STRING' ^{CODESYS Forge talk (Thread)}
Cannot convert 'STRING' to type 'STRING'
Last updated: 2014-03-31

Mail Service IIoT : Choose TLS type? ^{CODESYS Forge talk (Thread)}
Mail Service IIoT : Choose TLS type?
Last updated: 2020-07-29

How to reset timer type PULSE ^{CODESYS Forge talk (Thread)}
How to reset timer type PULSE
Last updated: 2016-11-07

Struct FB Input, type coercion ^{CODESYS Forge talk (Thread)}
Struct FB Input, type coercion
Last updated: 2021-10-23

Type–length–value in Codesys ^{CODESYS Forge talk (Thread)}
Type–length–value in Codesys
Last updated: 2022-01-02

missing siemens type functions ^{CODESYS Forge talk (Thread)}
missing siemens type functions
Last updated: 2012-04-02

ERROR 3729 invalid type ? ^{CODESYS Forge talk (Thread)}
ERROR 3729 invalid type ?
Last updated: 2010-03-18

Flexible variable type for functions: ANY_TO_xxx ^{CODESYS Forge talk (Thread)}
Flexible variable type for functions: ANY_TO_xxx
Last updated: 2019-11-06

Get Type Of a Variable ^{CODESYS Forge talk (Thread)}
Get Type Of a Variable
Last updated: 2018-02-21

question on type conversions ^{CODESYS Forge talk (Thread)}
question on type conversions
Last updated: 2012-10-02

Write variable of type TIME ^{CODESYS Forge talk (Thread)}
Write variable of type TIME
Last updated: 2018-04-27

Error: Type mismatch at output... ^{CODESYS Forge talk (Thread)}
Error: Type mismatch at output...
Last updated: 2015-11-17

ModbusTCP-type BIT or BOOL ^{CODESYS Forge talk (Thread)}
ModbusTCP-type BIT or BOOL
Last updated: 2020-11-16

Compare operands of type STRUCT ^{CODESYS Forge talk (Thread)}
Compare operands of type STRUCT
Last updated: 2015-09-22

Sort by relevance or date