Post by eschwellinger on Add licence ^{CODESYS Forge talk (Post)}
Which plc and in which version? Runtime Type? Runtime Version?
Last updated: 2024-01-05

Post by macros8 on Alarm Management - latched variable represented as Text list ^{CODESYS Forge talk (Post)}
Hi, I haven´t noticed you put the comment here. I thing it´s a bit different. What I want is to have detail errors of technology in data type e.g. INT. This variable I would latch to the corresponding error msg but I would like to get it convert to text from the text list and not keep it in INT form. Example. Main error Valve Error: SubErrors 1 - Both sensors 2 - Not retracted in time 3 - Not pulled out in time In HMI Main error + latch SubErrors => "Valve Error: Both sensors" The benefit is that text lists are part of translation and can be easily manipulated. I know I can create whole string msg in PLC but then, it lose advantage of Alarm management. Thanks. M.
Last updated: 2023-11-07

Post by alexgooi on Modbus writing on value change ^{CODESYS Forge talk (Post)}
The way I usally tackle this is by syncing only words (then you are able to use the FB above). If you then want to write a Boolean simply type it like this. Value[1].0 := Bool1; Value[1].1 := Bool2; Value[1].2 := Bool3; Uints have the same number of bits than a INT/WORD so these ones will work as well (they are only represented diffrently). A Real will work but you will loose some infomration in the conversion. If you want to keep the information you can convert 2 words to a float with a function (for example with the IEEE-754 standard) . In this way the syncing to the server is very simple and in the Codesys Program you decide what part of the word you want to use.
Last updated: 2024-04-03

Post by smartcoco on OPC server in "Communication manager" ^{CODESYS Forge talk (Post)}
I don't recommend using 'Communication Manager'. Under 'Communication Manager', the 'NodeId' type of OPC UA can only be of type 'OPAQUE'. This will bring compatibility issues to the development of the upper computer.
Last updated: 2025-01-24

Post by altus22 on Type SM3_Drive is not equal to type SM3_Drive ^{CODESYS Forge talk (Post)}
Another way to resolve this is to set Codesys to use a specific version of the offending library under Placeholders in the Library Manager.
Last updated: 2025-04-17

Post by imdatatas on The default ramp type selection in SoftMotion V4.18.0.0 is Quadratic ^{CODESYS Forge talk (Post)}
Unfortunately, The same behaviour still exist with SoftMotion V4.19.0.0 too. (default ramp type is quadratic instead trapezoid for new created axis object) For your information.
Last updated: 2025-09-04

[ERROR] The PLCopenXML import is not possible because Device not found. Type: 89, Id: 0000 0005, Version: 3.5.10.0 ^{CODESYS Forge talk (Thread)}
[ERROR] The PLCopenXML import is not possible because Device not found. Type: 89, Id: 0000 0005, Version: 3.5.10.0
Last updated: 2024-02-15

The element of type 'VisuFbElemImage' could not be updated. Reason: Index was outside the bounds of the array. ^{CODESYS Forge talk (Thread)}
The element of type 'VisuFbElemImage' could not be updated. Reason: Index was outside the bounds of the array.
Last updated: 2026-01-27

Post by dmb-fan on Attemp Convert old V2.3 projects : Error HRESULT: 0x80010105 (RPC_E_SERVERFAULT)) ^{CODESYS Forge talk (Post)}
I had runnig this already. Then I updated to SP22 patch3. After that I got always this error: ===== Project importieren: XXXXnameYYYYYY ===== *[FATALER FEHLER] Fehler beim Import des Projekts: Ausnahmefehler des Servers. * [FATAL ERROR] Error importing the project: Server exception. (Exception to HRESULT: 0x80010105 (RPC_E_SERVERFAULT)) I delete the version and installed again. Same. I uninstalled all CoDeSys on the PC and installed the old SP22 patch2 new. Same error by opening old projects. Immediatly, not by converting. Convert V3.5.17 was always installed. What is happening or what can I do?
Last updated: 2026-08-11

Post by pernockham on Inheritence of struct, ^{CODESYS Forge talk (Post)}
Im looking for a way to define predefined version of the same structures through "extends"/inheritance. What I want to do is best shown with an example: TYPE log_item_val_type : ( BOOL_ := 0, INT_, REAL_, STRING_ ); END_TYPE TYPE LOG_DATA_BASE STRUCT val_type : log_item_val_type; (* value, name etc *) ENDSTRUCT ENDTYPE (* this/below is not possible as I understand from the compiler?? *) TYPE LOG_DATA_BOOL extends LOG_DATA_BASE : STRUCT val_type : log_item_val_type := log_item_val_type.BOOL_; END_STRUCT END_TYPE TYPE LOG_DATA_INT extends LOG_DATA_BASE : STRUCT val_type : log_item_val_type := log_item_val_type.INT_; END_STRUCT END_TYPE etc. for LOG_DATA_REAL and ..STRING. The system will not allow me to "re-define" "val_type" however. Instead I must do the work-around of defining four different types with all fields individually defined. The benefit if I could extend the base item would be that Im (more) sure the structures are identical. In usage I can call in a specific type rather use the base type and assign which type. Usage by pointer/ref to log_data_base would also be easier.. (* Usage: *) log_data : log_data_int := (name, value etc.) (* Instead of: *) log_data : log_data_base := (name, value, val_type).. Is this possible to achieve in some way that I have missed?
Last updated: 2025-03-05

Post by ihatemaryfisher on Sorting array of any-sized structure ^{CODESYS Forge talk (Post)}
With that I could make an array of varying size, but would still have to define the array type in the function's declaration VAR_IN_OUT stArray: array [*..*] of <pre-defined data type> END_VAR I wanted a function that could take an array of any type (e.g., a structured VAR) as an input. That way I could call it in multiple POUs to handle different arrays structures.
Last updated: 2023-08-18

Post by timvh on Device logon problem following fresh install ^{CODESYS Forge talk (Post)}
In your project you selected the "CODESYS Control Win V3" as device, but the device you want to connect to is a "CODESYS Control Win V3 x64". Those are not the same. If you double click on the device during the network scan, you will get information that these are not the same, but that you can change the type in your project to the x64 bit type. Another option is to "right-click" on the device in the device tree of your project and select "update device" then select the x64 type.
Last updated: 2024-03-19

Post by ahmedbadawi10 on Codesys Trend Problem ^{CODESYS Forge talk (Post)}
I have control win v3 with simulation and a small program with function to convert analog values to percentages, I need to show these percentages in a trend chart, but nothing is shown in the trend as you see in snips attached! thanks in advance
Last updated: 2025-09-16

Post by reinier-geers on JSON (WString format) accessing elements. Convert to STRUCT? ^{CODESYS Forge talk (Post)}
HI , Ill try the same with Energy prices. But no data I add the Query to the wsPost. Add $ because wstring use "as start end end. Here the link of the API info https://reversed.notion.site/Marktprijzen-API-89ce600a88ac4abe8c2ad89d3167a83e
Last updated: 2025-10-09

Post by reinier-geers on JSON (WString format) accessing elements. Convert to STRUCT? ^{CODESYS Forge talk (Post)}
HI , Ill try the same with Energy prices. But no data I add the Query to the wsPost. Add $ because wstring use "as start end end. Here the link of the API info https://reversed.notion.site/Marktprijzen-API-89ce600a88ac4abe8c2ad89d3167a83e
Last updated: 2025-10-09

Post by tvm on Timer On Vijeo ^{CODESYS Forge talk (Post)}
Vijeo doesn't support TIME variables, so the easiest thing to do is convert to a STRING in your program, and use that variable. You could use TimeAsString:= TIME_TO_STRING(TimeVar) to get a string that looks like this: T#5h10m45s200ms
Last updated: 2024-05-07

Post by dmb-fan on Attemp Convert old V2.3 projects : Error HRESULT: 0x80010105 (RPC_E_SERVERFAULT)) ^{CODESYS Forge talk (Post)}
Installing SP17 on an old Win10 PC is working. Are there companys out there who can handle installing software on windows ? Siemens: No Dell: No CoDeSys: No
Last updated: 2026-08-11

Post by ph0010421 on How to manage variable types larger than 64 bits - Ethernet/IP ^{CODESYS Forge talk (Post)}
My guess is that's a STRING, not an INT type. And it's 128 bytes, not bits
Last updated: 2024-09-23

Post by athuum on Error 'Library not found' and 'Unkown type' ^{CODESYS Forge talk (Post)}
I have found the solution, the CmpEventMgr version has to correspond with the 3sLicense version.
Last updated: 2024-10-10

Post by eschwellinger on Server not adding PLC ^{CODESYS Forge talk (Post)}
which plc type do you try to add? Unique serial numbers of the plc are mandatory too.
Last updated: 2025-02-17

Post by timvh on Inheritence of struct, ^{CODESYS Forge talk (Post)}
Maybe the ANY type can help? https://content.helpme-codesys.com/en/CODESYS%20Development%20System/_cds_datatype_any.html
Last updated: 2025-03-08

Post by jampid on How do I fix ";Internal Error (x86-64): Invalid type size" error? ^{CODESYS Forge talk (Post)}
Bonjour Mucleus, peut-être mettre à jour le Device et recompiler?
Last updated: 2025-04-16

Post by dkugler on Reading a negative number ^{CODESYS Forge talk (Post)}
why not simply converting data type UINT to INT? Then avoid negative values with ... := MAX(0 , intTest); Good luck!
Last updated: 2025-05-28

Post by simotion on Property ^{CODESYS Forge talk (Post)}
Why can't a property be of type REFERENCE TO? Plc goes to stop if I try that.
Last updated: 2023-12-14

Post by hyplcmotion on The element of type 'VisuFbElemImage' could not be updated. Reason: Index was outside the bounds of the array. ^{CODESYS Forge talk (Post)}
Hello, I’m encountering the same issue. I only receive these errors when downloading to the PLC—there are no errors during the build—after upgrading to CODESYS 3.5.21.10. Is there any known fix or recommended solution? Visualization seems running ok, no PLC log error. Visualization: Error: The element of type 'VisuFbLabel' could not be updated. Reason: Source array was not long enough. Check srcIndex and length, and the array's lower bounds. Visualization: Error: The element of type 'VisuFbElemSimple' could not be updated. Reason: Source array was not long enough. Check srcIndex and length, and the array's lower bounds. Visualization: Error: The element of type 'VisuFbElemSimple' could not be updated. Reason: Source array was not long enough. Check srcIndex and length, and the array's lower bounds. Visualization: Error: The element of type 'VisuFbElemImage' could not be updated. Reason: Source array was not long enough. Check srcIndex and length, and the array's lower bounds. Visualization: Error: The element of type 'VisuFbElemSimple' could not be updated. Reason: Source array was not long enough. Check srcIndex and length, and the array's lower bounds. Visualization: Error: The element of type 'VisuFbElemSimple' could not be updated. Reason: Source array was not long enough. Check srcIndex and length, and the array's lower bounds. Visualization: Error: The element of type 'VisuFbElemImage' could not be updated. Reason: Source array was not long enough. Check srcIndex and length, and the array's lower bounds. Visualization: Error: The element of type 'VisuFbElemButton' could not be updated. Reason: Source array was not long enough. Check srcIndex and length, and the array's lower bounds. Visualization: Error: The element of type 'VisuFbElemButton' could not be updated. Reason: Source array was not long enough. Check srcIndex and length, and the array's lower bounds. Visualization: Error: The element of type 'VisuFbElemSimple' could not be updated. Reason: Source array was not long enough. Check srcIndex and length, and the array's lower bounds.
Last updated: 2026-01-26

Sort by relevance or date