Post by nonstop-cat on Problem of assigning physical addresses to variables of type ARRAY OF ARRAY as MW and QW ^{CODESYS Forge talk (Post)}
Array writing method error,,,<arrayname>: ARRAY [<ll1>..<ul1>, <ll2>..<ul2>, <ll3>..<ul3>]</ul3></ll3></ul2></ll2></ul1></ll1> OF <basedatatype></basedatatype></arrayname>
Last updated: 2025-03-31

Post by jackbrady on Function Blocks and arrays of function blocks ^{CODESYS Forge talk (Post)}
Thanks for the reply. Much appreciated.
Last updated: 2024-02-15

Automation Server 🇬🇧 ^{CODESYS Forge talk (Discussion)}
The Industry 4.0 administration platform for users and operators of CODESYS compatible controllers
Last updated: 2026-02-11

Post by manuknecht on FileDialog - OnDialogClosed not called anymore ^{CODESYS Forge talk (Post)}
I had similar issues with the OnDialogClosed not being called. I realized that this behaviour is resolved, when the according visualization object on which the input configuration is set is moved to the foreground. Somehow, the object has to be one of the lowest elements in the Element List (i.e. in the foreground) for it to work.
Last updated: 2025-04-25

Post by paulpotat on cm4 runtime problem ^{CODESYS Forge talk (Post)}
Hello again, After looking into it, I noticed that the release note of "CODESYS Control for Raspberry PI 4.13.0.0" mentions a bug fix titled "Support Compute module 4". Is it possible to have more details about this fix from the CodeSys team please ? Because I have several CM4 boards with the same hardware revision / OS but some of them works with the 4.10 runtime and others only works with the 4.13 runtime...
Last updated: 2024-09-09

Post by davidking on Error, visualisation property handling, VISU_USEPROPERTYINFO ^{CODESYS Forge talk (Post)}
Solution: Disable VISU_USEPROPERTYINFO define Go to Project → Options (or Project → Properties, depending on your CODESYS version). Find the section called Compiler Defines. Look for the define: nginx Copy Edit VISU_USEPROPERTYINFO Delete it from the list, or uncheck it if it’s a checkbox. Save your changes and try compiling the project again. → This is the right approach if you don’t need property handling for visualization elements.
Last updated: 2025-07-09

Post by nano on Error building Extension SDK Linux code ^{CODESYS Forge talk (Post)}
Hey schnepper, when i look into your c-file, i would say that only the main-function is declared with cext-addendum in your codesys-library-project. all yöur funtions in library has to be the cext-addendum when the external implementation is activ. if i remeber right, methods and other subelements dont need that, but every base-elements
Last updated: 2024-04-02

XOR with four Inputs with OR-, NON- and AND-Operators ^{CODESYS Forge talk (Thread)}
XOR with four Inputs with OR-, NON- and AND-Operators
Last updated: 2024-11-05

Codesys and smartphone (read and write) ^{CODESYS Forge talk (Thread)}
Codesys and smartphone (read and write)
Last updated: 2012-01-14

method GetCurrentVisu and keypad's Max and Min values ^{CODESYS Forge talk (Thread)}
method GetCurrentVisu and keypad's Max and Min values
Last updated: 2010-07-27

Weatherstation based on PI and 7" LCD and Sense hat ^{CODESYS Forge talk (Thread)}
Weatherstation based on PI and 7" LCD and Sense hat
Last updated: 2017-09-27

Function to Browse and Return File Name and Path ^{CODESYS Forge talk (Thread)}
Function to Browse and Return File Name and Path
Last updated: 2012-04-26

Objects and Array Sizes when Extending and Implementing ^{CODESYS Forge talk (Thread)}
Objects and Array Sizes when Extending and Implementing
Last updated: 2018-10-11

Virtual Master and virtual slave - MC_CamIN and MC_Halt ^{CODESYS Forge talk (Thread)}
Virtual Master and virtual slave - MC_CamIN and MC_Halt
Last updated: 2019-03-20

Post by otdeveloper on IEC 61499 ^{CODESYS Forge talk (Post)}
It is being worked on by many companies and its even-driven function blocks seem like a natural evolution of the object oriented industrial programming I have seen Gary Pratt (author of the Book of CODESYS and much more) so expertly implement and explain. I would expect CODESYS to have this front and center on their sights and, if they do not, I would be very interested in learning why.
Last updated: 2024-02-09

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

Post by durallymax on How to use MQTT in CODESYS Control Win V3 ^{CODESYS Forge talk (Post)}
With the IIoT library/license or the one provided by the hardware OEM. Several examples online of how to use the MQTT Client SL library.
Last updated: 2025-12-12

Post by ralfki on XMLWriteAsync ^{CODESYS Forge talk (Post)}
Hello, I tried to write a XML file with XMLWriteAsync. Unfortunately after every Element it adds two CR and one LF. Is it possible to have only one CR and LF. Thanks for the support
Last updated: 2024-11-20

Post by glutenaron on Safety drive EL6900 and mitsubishi ^{CODESYS Forge talk (Post)}
I can mention that i needed to update the firmware on the mitsubishi servo and then i got a step closer. The old firmware did not support FSOE but the new does.
Last updated: 2025-05-20

Post by glutenaron on Safety drive EL6900 and mitsubishi ^{CODESYS Forge talk (Post)}
I can mention that i needed to update the firmware on the mitsubishi servo and then i got a step closer. The old firmware did not support FSOE but the new does.
Last updated: 2025-05-20

Post by pistola on C0357: "GetNextClient" is obsolete, use VisuUtils instead ^{CODESYS Forge talk (Post)}
I'm having some troubles with this same issue and I'm wondering if someone can help me out. On a settings visual I allow the operator to enter some values however if they activate the page change button it will change the change with the Numpad dialog open. Since I'm using Visuelems.CURRENTVISU to change the pages I came across this code noted below for determining if the Numpad dialog was active. This code worked great however now in 3.5.19 it's now obsolete. I've tried following the directions in the attached program above however I can't see to get it to work in my program. Can anyone provide some help to determine if a dialog is open? FUNCTION Check_Dialog_Open : Bool VAR_INPUT sDialogName : STRING; // Input variable for the name of the dialog END_VAR VAR pstClientData : POINTER TO VisuElems.VisuStructClientData; // Pointer to the client data structure itfDialogManager : VisuElems.IDialogManager; // Interface for the dialog manager itfMyDialog : VisuElems.IVisualisationDialog; // Interface for the specific visualisation dialog END_VAR // Begin the iteration over the client manager VisuElems.g_ClientManager.BeginIteration(); // Loop through each client until no more clients are found WHILE (pstClientData := VisuElems.VisuElemBase.g_ClientManager.GetNextClient()) <> 0 DO // Get the dialog manager interface itfDialogManager := VisuElems.g_VisuManager.GetDialogManager(); // Get the specific dialog interface using the dialog name itfMyDialog := itfDialogManager.GetDialog(sDialogName); // Check if the dialog is open for the current client Check_Dialog_Open := VisuDialogs.VisuDlgUtil_IsDialogOpen(itfMyDialog, pstClientData, itfDialogManager); // If the dialog is open, exit the loop IF Check_Dialog_Open THEN EXIT; END_IF END_WHILE
Last updated: 2025-03-27

Post by yr00 on OPC UA datasource low read frequency ^{CODESYS Forge talk (Post)}
Hello everyone, I am trying to test the OPC UA client feature in Codesys. My setup is the following; I have a Codesys simulation/ visualization running on Control Win V3. My OPC UA server is hosted on a Siemens 1518 PLC using PLCSim Advanced. The setup is completely virtual so there are no really PLCs. Everything is on my laptop. Writing data from the Codesys simualtion to the server is very quick. I have a PLC program running on another 1500 PLC which reads data from simulation via the server, and changes in the simulation (e.g. button pressed) appear within hundreds of miliseconds if not tens of miliseconds in my PLC program. However, when it comes to reading data from the OPC UA Server by Codesys, it taks around 1-2s. I connected a UAExpert client and it gets update very quickly so I am fairly sure the problem is with Codesys. I have tried changing the update rate in datasource -> General and Diagnosis, but it doesn't seem to have an effect. Do you guys have any suggestion on what I can do?
Last updated: 2023-08-29

Post by derpaul on Official MQTT-Client: MAX_RECEIVE_BUFFER_SIZE_EXCEEDED ^{CODESYS Forge talk (Post)}
I've got it running again! For testing I've extendet the g_udiMaxPacketSize from 6000 to 100000 and g_udiMaxPayloadSize from 4096 to 80000 After it does run again! Thank you very much for your help!
Last updated: 2023-09-28

Post by damian177 on MQTT_client disconnect when call MQTT_sunscribe ^{CODESYS Forge talk (Post)}
Probably I have the same problem, When I connect to broker and try subscribe to much topics then the client return error, did you solve your problem ?
Last updated: 2023-10-10

Post by mainak on OPC UA C# client connecting to OPC UA CODESYS server ^{CODESYS Forge talk (Post)}
it could be due to security settings. In codesys IDE, go to device-> change run-time security policy, and click the checkbox that says "Allow anonymous login". try if this works.
Last updated: 2024-10-19

Sort by relevance or date