Post by j-a-y on Version 2.5 SP18 -> Visualisation Elements missing Input Configuration Options ^{CODESYS Forge talk (Post)}
were you able to resolve it?
Last updated: 2024-04-22

Post by mubeta on parker servo and position ^{CODESYS Forge talk (Post)}
In general, drives have parameter sets to adjust behaviour in such cases: position recovery, adaptation with resistant torque, out-of-position window failure, etc. (Much depends on the type of configuration set for the axis: positioner, speed controller, torque controller, etc.). I have used that type of drive very little, in only two cases and a long time ago. To tell you what is normal is impossible. I know by reputation they are very simple objects, without too many pretensions and adjustments possible. Try running traces by monitoring actual position, motor current, torque and following error. These are the most sensible curves to understand what is going on. Maybe by fine tuning the motor tuning, the current controller or the speed controller you will get something closer to what you want. For example, from DS, the motor has a standstill torque of 3 Nm. Observe with traces whether this is effective: motor current trend. And afterwards, when you have your own accurate picture of the situation, you can also hear from the product's local support to see if you can steal a few more things from it performance-wise.
Last updated: 2024-08-05

Post by struccc on The future and proper use of CAA.BOLT, CAA.SEMA,.. ^{CODESYS Forge talk (Post)}
Dear All, Dear CODESYS, I'm curiously following CODESYS transitioning away from the CAA libraries, and I'm mostly in favor of these major changes. Naturally, I'd like to align my current (not end-user) developments accordingly. I'm tracking , reading release notes, ... And want to figure out the future :) Is it possible to hear / read more about the reasons, objectives and scope of these changes? One important element is CAA Types - CAA Types Extern. What is the plan with that? What's the future of CAA.SEMA, CAA.BOLT ? I have never used them (always relied on SysLib*), but they are tempting... Would be useful to have a platform independent "Macro" for this functionality... Is there something in existing or planned ? Are they suitable to be used in low level libraries... For Example IO-Drivers, Components, "to-become system libraries"? CAA.TaskLock, CAA.TaskUnlock ? Well, they don't claim platform independency, so I can't rely on those.... Any up-to-date advise, standard, pattern to follow in new libraries for task and resource locking? Practical set of conditional defines to be used? If this information is not publicly available, can you please send a private message about the proper way to achieve this? I have support agreement, just couldn't get trough with these questions... P.
Last updated: 2025-03-14

Post by timvh on Array of Program ^{CODESYS Forge talk (Post)}
You cannot create an array of Programs. Create a Function Block for this purpose instead of a program. You can create an array of FB instances and call each instance in a loop.
Last updated: 2024-09-03

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 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-03-18

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

Post by egr99 on Modbus TCP Server connection is ESTABLISHED but all holding registers are value 0? ^{CODESYS Forge talk (Post)}
Hi there, Read the above description and experienced the same: Reading coil/discrete input/input register/holding register doesn't fill the mapped I/O variable. Any suggestions? Defined (see attachment): - Ethernet (with parameters according to the used Ethernet adapter of my Windows 11 laptop) - -Modbus TCP Client - - -LOGO231 as Modbus TCP Server - - -WS242 as Modbus TCP Server (WaveShare Modbus TCP <-> RTU converter) - - - -WS242_01 as Modbus Server, COM port (slave-id 1 RTU) - - - -WS242_03 idem (slave-id 3 RTU) - - - -WS242_11 idem (slave-id 11 RTU) Writing coil/holding register works from a mapped I/O variable works fine. Verification of Modbus traffic with WireShark: QUERY to and the RESPONSE of all slave-ids are correct Status of all defined is CONNECTED, RESPONSE_SUCCESS, RUNNING etc. Request counters increase with expected frequency. Error counter = 0. (To have all counters works fine I had to change Modbus TCP Client's parameter OptimizationON to FALSE). LOGO231 works fine: values in mapped I/O conform expectation WS242 without Modbus Server, COM port and with defined channels (for only 1 slave-id possible) works fine. PLC Settings: Update I/O while in stop: I see xBusy changing from FALSE to TRUE and vice versa. Always update variables: Enabled 1
Last updated: 2026-04-05

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

Sort by relevance or date