Post by k2saki on CNC / G01 Speed is very slow (or go-stop motion) in Continuous short segment . ^{CODESYS Forge talk (Post)}
I'm using CAD/CAM that outputs GCode with G01 many short segments from NURBS Curve, only X-Y axis. But CODESYS CNC motion seems much slower ( or stop-go motion ) in simulation mode than F-Value (I checked value from SMC_Interpolator - dVel ). In GCode G01, F value is F500, but movement is very slow, actual speed (dVel) is between 0 to 30 back and forth. I think very old CNC can move like that, but nowadays, a lot of CNC can move smoothly to process free curve ( somethimes option switch ) I tried to use G51 Dxx but I got the same result. My questions are 1) How do I improve CODESYS CNC motion in this case ? 2) How can I graph the sampling from dVel of SMC_Interpolate in CODESYS? From my GCode N2006 G01 X1.4364 Y-14.6847 F500 N2007 G01 X1.6759 Y-14.6768 N2008 G01 X1.9152 Y-14.6486 N2009 G01 X2.1547 Y-14.6400 N2010 G01 X2.3943 Y-14.6090 N2011 G01 X2.6336 Y-14.6002 N2012 G01 X2.8732 Y-14.5716 N2013 G01 X3.1127 Y-14.5634 N2014 G01 X3.3520 Y-14.5410 N2015 G01 X3.5915 Y-14.5336 N2016 G01 X3.8308 Y-14.5307 ... Thansk.
Last updated: 2024-04-29

Post by mxj262 on FB having single input but initialized with Array ^{CODESYS Forge talk (Post)}
Ok yes now the loop has stopped when I set sum to zero before the for loop. Why will it retain the sum value from the last call?
Last updated: 2024-05-06

Post by guilhermeleao on How to communicate 2 pcs that are using CODESYS ^{CODESYS Forge talk (Post)}
I need to connect 2 computers on the same network that are running codesys, so that they can receive and change variable values from each other. This connection must preferably be made using Modbus.
Last updated: 2024-05-06

Post by fugtwad on Automation Builder V2.5 EtherCAT CM579 Master Scan for devices - >No gateway selected ^{CODESYS Forge talk (Post)}
Scan from "IP-Configuration" with PC connected to first EtherCAT slave and "EtherCAT" tick box ticked gives slave info. As does ticking the "Emergency" tickbox.
Last updated: 2024-05-20

Post by rafaelbrito on Licensing info not available. ^{CODESYS Forge talk (Post)}
Hello, I'm having the same problem. I'm trying to license Codesys running in a Linux container, which I downloaded from the following link (https://hub.docker.com/r/hilschernetiotedge/codesys_control_sl_linux). The same error that you mentioned appears. Is there any solution?
Last updated: 2024-05-22

Post by paro on General question about library versions ^{CODESYS Forge talk (Post)}
I think you can use the newer versions. For a explanation from CODESYS, please read this post: https://www.codesys.com/the-system/versions-modularization.html
Last updated: 2024-05-29

Post by jaspergain on Non-existing identifiers ^{CODESYS Forge talk (Post)}
Hi, I'm using SP19 Patch 5, the software is also updated from SP18 Patch 5, I forgot to mention this. I will try a newer patch to see if it fixes the issue. Thanks for your help.
Last updated: 2024-05-30

Post by eschwellinger on Licensing info not available (WAGO PFC200 + Codesys V3) ^{CODESYS Forge talk (Post)}
Seems that the Wago Target does not support the licensing. Either use PFC200 SL from CODESYS Store or ask the Wago support for help.
Last updated: 2024-06-10

Post by fajean on CODESYS control on RPi starts, shortly runs, then exits ^{CODESYS Forge talk (Post)}
https://us.store.codesys.com/codesys-control-for-raspberry-pi-sl.html Quoted from the "additional requirements" section : The operating system Raspberry Pi OS (32-bit)
Last updated: 2024-06-14

Post by mbart on VAR_INFO from inside of a FB to get info on the instance. ^{CODESYS Forge talk (Post)}
I experienced the same problem: using __VARINFO is working only in PRG context, while it crashes if used inside Function Blocks. I would really appreciate if they would fix this issue
Last updated: 2025-12-04

Post by sb879 on Non-formal invocation of function blocks in CODESYS ^{CODESYS Forge talk (Post)}
Is it possible to do non-formal invocation of function blocks in CODESYS? I get an error when I try, see the attached pic. Also attached a pic from IEC 61131-3 describing non-formal invocations.
Last updated: 2025-12-04

Post by sb879 on Non-formal invocation of function blocks in CODESYS ^{CODESYS Forge talk (Post)}
Is it possible to do non-formal invocation of function blocks in CODESYS? I get an error when I try, see the attached pic. Also attached a pic from IEC 61131-3 describing non-formal invocations.
Last updated: 2025-12-04

Post by jackyrileap on Conversion of analogue input into Real measurement value ^{CODESYS Forge talk (Post)}
You need proper scaling from raw ADC counts to engineering units, handling underflow, overflow, and using linear conversion logic carefully.
Last updated: 1 day ago

Post by mondinmr on Why SysPipeWindows is not implemented in RTE? ^{CODESYS Forge talk (Post)}
This library would be very useful for IPC communications. Using a UDP socket on localhost is unpredictable, as with slightly loaded machines it does not even guarantee packet delivery locally. Using TCP creates a lot of overhead. Message named pipes would be an excellent solution for Windows RTE. On Linux, since the release of the extension package, there is no issue, as it is sufficient to develop a component. However, although now 90% of our clients understand that Linux runtimes are better in every way compared to Windows RTE, especially from the security aspect (Not in kernel space) and the issues with Windows updates, 10% stubbornly insist (sometimes for trivial commercial reasons) on using Windows. Managing IPC with circular buffers in shared memory is quite ugly, or rather really ugly and unaesthetic. In the manuals, I saw the SysPipeWindows libraries, so I decided to test them, but unfortunately, I noticed that they are not implemented for RTE devices. Technically, I could try to open them as regular files, but SysFileOpen returns 16#27 or 16#39 depending on how I set the name (direction of the slashes). Here is the code to create shared memory and named pipes. Shared memory work great, named pipes no! #ifdef Q_OS_WIN32 SECURITY_ATTRIBUTES sa; SECURITY_DESCRIPTOR sd; InitializeSecurityDescriptor(&sd, SECURITY_DESCRIPTOR_REVISION); SetSecurityDescriptorDacl(&sd, TRUE, NULL, FALSE); sa.nLength = sizeof(SECURITY_ATTRIBUTES); sa.lpSecurityDescriptor = &sd; sa.bInheritHandle = FALSE; const wchar_t* name = L"Global\\ShmTest"; HANDLE hMapFile = CreateFileMapping( INVALID_HANDLE_VALUE, NULL, PAGE_READWRITE, 0, sizeof(SharedData), name); if (hMapFile == NULL) { qCritical("Error creating shared memory"); return 1; } data = static_cast<SharedData*>(MapViewOfFile(hMapFile, FILE_MAP_ALL_ACCESS, 0, 0, sizeof(SharedData))); if (data == NULL) { qCritical("Error mapping shared memory"); return 1; } HANDLE hPipe = CreateNamedPipe( TEXT("\\\\.\\pipe\\MyPipe"), PIPE_ACCESS_DUPLEX, PIPE_TYPE_MESSAGE | PIPE_READMODE_MESSAGE | PIPE_WAIT, PIPE_UNLIMITED_INSTANCES, 1024 * 1024, 1024 * 1024, NMPWAIT_USE_DEFAULT_WAIT, &sa); if (hPipe == INVALID_HANDLE_VALUE) { qCritical("Error creating named pipe"); return -1; } if (!ConnectNamedPipe(hPipe, NULL)) { qCritical("Error connecting to named pipe"); return -1; } checkPipe(hPipe); #endif
Last updated: 2024-02-02

Post by garyl on Comments in arrays and assigning RST coil's to 600 outputs ^{CODESYS Forge talk (Post)}
Hello all, im working on a project that requires me to convert an old automation direct DirectSoft PLC d2-250-1. One of the problems im encountering is that all of the comments are attached to members of the different addresses. When i convert the addresses (1777 "C" registers, 777 X registers, and 20,0000 V registers) im running into difficulties keeping the inputs/outputs correct since they are missing documentation. Is there a good way to retain the comments of the indexes in the array? Secondly, initially i was declaring the "C" and "V" addresses individually and this worked to retain the comments as to which register did what, however i ran into a problem when one rung reset (or set to 0) approximately 600 C Addresses. Since each tag is separately declared this proved to be nearly impossible without a literal wall of code that attempted to crash the program. So i converted all of the registers (C,X,Y,V) into separate structs, declared them as arrays and pointed all of the original call outs in the program to the newly defined structs. However i have now lost comments and the program is very hard to follow. Thanks for any help with this issue.
Last updated: 2023-08-31

Post by codesysbeginner on Eaton XC303 - USB Mounting / Trend manager ^{CODESYS Forge talk (Post)}
Hi, For a project I am using the trendmanager functionality, I changed the placeholder filepath to which the SQL database is saved to: home/disk_usb, $trend$. Which only works as long as the usb was mounted to the PLC at boot. However, I'd like to be able to switch the USB's out if they break or for data analysis. However when a new (or the same) USB is plugged back in the shortcut doens't exist on the device anymore. Also in the device directory under root/mnt/ a new folder appears SDB1 in addition to SDA1 to which the Trendmanager was originally writing. The SDA1 folder is empty/unreachable while the new SDB1 folder has the contents of the USB drive. I tried disabling the trendmanger while unplugging the USB's however this doesn't work. My question, how do I make it so that when I plug a USB drive back in, it will be mounted to SDA1 instead of SDB1? Kind Regards
Last updated: 2024-10-09

Post by peterkcontrols on Codesys Network driver install for Codesys Control RTE x64 ^{CODESYS Forge talk (Post)}
Hello I am trying to download my project onto my Codesys Control RTE x64 soft PLC. and I have had an issue when downloading. [FATAL ERROR] Unresolved reference: 'SYSETHERNETADAPTEROPEN' [FATAL ERROR] Unresolved reference: 'SYSETHERNETADAPTERCLOSE' [FATAL ERROR] Unresolved reference: 'GETNUMBEROFADAPTERS' [FATAL ERROR] Unresolved reference: 'GETADAPTERINFO' [FATAL ERROR] Unresolved reference: 'SYSETHERNETIPFRAMERECEIVE' [FATAL ERROR] Unresolved reference: 'SYSETHERNETETHFRAMESEND' [FATAL ERROR] Unresolved reference: 'SYSETHERNETETHFRAMERECEIVE' [FATAL ERROR] Unresolved reference: 'SYSETHERNETIPFRAMESEND' [FATAL ERROR] Unresolved reference: 'SYSETHERNETFRAMERELEASE' Looking on the forum I have found other people had to install the network driver, which I have done following this youtube video by codesysGroup: https://youtu.be/10oj4wABaKc?si=664l83JXUGQSDlAe I have added the network driver, please see attached image. I have checked my BIOS to make sure my secure boot status is disabled, see attached image. when I go to component manager, the drop down menu doesnt have the new network adapter, see attached image. I have not yet purchased or installed any licenses is that what I am missing? What other reason is there that I can't download to the runtime. Thanks
Last updated: 2025-03-18

Post by dhumphries on Minimum system requirements for codesys control standard S ^{CODESYS Forge talk (Post)}
I'm working on a low cost project and I'm considering installing the Codesys runtime on a PC running Linux Debian instead of buying a PLC with a pre-installed runtime. For my needs the Control Standard S license should be capable of running some IO over ethernet/ip, and a webvisu. The PC I am considering has a AMD GX-424CC 2.4GHz processor (4 core/4 thread) and 4GB RAM. This may compare to a raspberry pi4, but I know an X86 processor doesn't directly compare to an ARM processor, and a processor can have a high clock speed but other factors like L2/L3 cache can influence the overall performance. I can't find any published specs for the processor and RAM requirements to run the Codesys Control runtime, does anybody have a link to the minimum system requirements or experience using devices that are at or below the minimum system requirements. A raspberry pi with the control for raspberry pi SL runtime license would be the lowest cost option, but the license is not for commerical use. This restriction is somewhat vague, can anybody clarify if this means I can use a raspberry Pi runtime for in-house automation, what about if I am selling an integrated system that uses a raspberry Pi as a controller?
Last updated: 2023-12-25

Post by squiggleypuff on Can't Add New Version of Modbus TCP Master ^{CODESYS Forge talk (Post)}
I'm having a tough time trying to get Modbus working on a Festo CPX-E PLC; it throws these pre-compiler errors as soon as I add in my Modbus TCP Master 3.5.12.30 to my project: I'm confused about the C0046 error, as I have IODrvModbusTCP 4.3.0.0 Library installed. So I thought maybe I needed to use the newest Modbus TCP Master 4.3.0.0, which is in my device repository: However, whenever I go to add this underneath the Ethernet adapter (which is version 4.2.0.0), the only TCP Master version available is the old 3.5.12.30 one, even if I have Display all versions checked.: I even went so far as to delete the old version, but then there were no options to add a Modbus TCP Master under my Ethernet adapter. What needs to be done to use the newest Modbus TCP Master? Or are these pre-compiler errors unrelated and I'm missing something? Any help greatly appreciated.
Last updated: 2024-04-04

Post by salvatorethomas on Port instantiation of serial interface in WAGO PLC using Modb_L05.lib in CoDeSys v2.3 ^{CODESYS Forge talk (Post)}
Hi — good description of the problem. A few suggestions / questions that might help narrow this down: Since your first serial port (COM2) works fine but the second (COM4 + MODBUS_EXT_MASTER) never opens, check whether the two ports are truly independent — some WAGO modules share internal resources, so COM4 might conflict with other functions or modules. Make sure that the physical wiring and module configuration for the second port (baud rate, flow control, RS-485 vs RS-422, etc.) exactly match what the library expects — a mismatch in flow control or wiring could prevent port opening even if the LED signals seem OK. Try using a plain SERIAL_INTERFACE on COM4 first (like you did for COM2) without Modbus logic — if that opens, you know the hardware + port config is fine, so the issue is more likely with modb_L05.lib. If the port opens but Modbus still fails, enable debug/logging (if available) to inspect whether the port opening fails or the subsequent Modbus negotiation fails. If you like — I can share a minimal example project I used with WAGO + COM4 + Modbus that worked; you could adapt that to test your setup. Wacky Flip
Last updated: 2025-12-01

Post by e13740e on Сalling the context menu from the keyboard ^{CODESYS Forge talk (Post)}
Hello. I have a question for you, perhaps you have an answer to it. Regarding calling the Context menu from the keyboard in Devices, specifically calling the context menu window from the keyboard via an assigned combination. Goal: to have the ability to navigationally add internal Objects (Methods, Properties) to Function Blocks from the keyboard without using the mouse. The Codesys environment interface does not allow Windows access to this via Shift+F10. Externally (outside the Codesys environment), the hotkey call for the context menu (Shift+F10) from the keyboard works in various environments, but at the same time, in Codesys it does not (it doesn't work). I have already tried various options on my own to achieve this (but unsuccessfully): Tools\Customize\Keyboard\Objects (the set combination does not give the desired result) Tools\Customize\Keyboard\Objects... (the set combination is extremely useful as it provides access to adding objects directly to Devices but does not provide the ability to add an internal object (Method/Property) to a Function Block). Thank you in advance for your help!!! P.S. I have already started trying to implement a script-based solution to call the context menu via AutoHotkey - by relocating the mouse cursor to the area of the navigational selection with a subsequent call of the context menu on it and relocating the mouse cursor back to its initial position. And in order not to "reinvent the wheel," I am writing this request to you!!!
Last updated: 2025-10-05

Post by e13740e on Сalling the context menu from the keyboard ^{CODESYS Forge talk (Post)}
Hello. I have a question for you, perhaps you have an answer to it. Regarding calling the Context menu from the keyboard in Devices, specifically calling the context menu window from the keyboard via an assigned combination. Goal: to have the ability to navigationally add internal Objects (Methods, Properties) to Function Blocks from the keyboard without using the mouse. The Codesys environment interface does not allow Windows access to this via Shift+F10. Externally (outside the Codesys environment), the hotkey call for the context menu (Shift+F10) from the keyboard works in various environments, but at the same time, in Codesys it does not (it doesn't work). I have already tried various options on my own to achieve this (but unsuccessfully): Tools\Customize\Keyboard\Objects (the set combination does not give the desired result) Tools\Customize\Keyboard\Objects... (the set combination is extremely useful as it provides access to adding objects directly to Devices but does not provide the ability to add an internal object (Method/Property) to a Function Block). Thank you in advance for your help!!! P.S. I have already started trying to implement a script-based solution to call the context menu via AutoHotkey - by relocating the mouse cursor to the area of the navigational selection with a subsequent call of the context menu on it and relocating the mouse cursor back to its initial position. And in order not to "reinvent the wheel," I am writing this request to you!!!
Last updated: 2025-10-05

Post by xcqt on Oop best practice ^{CODESYS Forge talk (Post)}
Hi all, I’m currently trying to improve my OOP structure in CODESYS and I’m looking for some input on how others approach this. I understand the basics like inheritance, interfaces, abstract FBs, methods, and properties, but I still struggle a bit with the overall architecture and what’s considered clean or scalable in bigger projects. As an example, I’m working on two different energy meter function blocks: FB_EnergyMeter_MQTT reads data from MQTT (strings) FB_EnergyMeter_Modbus reads data from Modbus (words) Both have their own Update() method and implement the same interface (something like IF_EnergyMeter). Later on, I’ll probably add more meter types, but they should all behave the same from the controller’s point of view. Now, there’s a FB_GridControl block that needs power data from these meters. I see two options here: Define the meter blocks inside FB_GridControl and call them directly (for example fbModbusMeter.UpdateModbus()). Keep the meter blocks outside and pass them into FB_GridControl as interface references, so the control block doesn’t know which specific type of meter it’s dealing with. Option 2 feels cleaner and more flexible to me, but I’m not entirely sure how to handle the data flow in that case. Should I pass the meter instance through an interface reference (REFERENCE TO IF_EnergyMeter)? Or is there a better way to link the external FBs to the control block? I’d like to hear how you structure this kind of setup or see an example from someone who has done something similar. EDIT: I think i need to do something like this fbModbusUpdateInput(wInput:= wWordValue); fbMqttUpdateInput(strInput:= strStringValue); IF bUseMqtt THEN Meter REF = fbMqttUpdateInput; ELSE Meter REF = fbModbusUpdateInput; END_IF fbControl.SetMeter(UsedMeter := Meter); Or am i thinking wrong? Thanks, Thomas
Last updated: 2025-10-16

Post by timvh on CANbus issue ^{CODESYS Forge talk (Post)}
On a PC with the Control Win, this is probably related to the fact that the CAN drivers are not loaded. Go to the folder where your Control Win Configuration file is: - E.g. C:\ProgramData\CODESYS\CODESYSControlWinV3x64\E1FA7ABE - Open the CODESYSControl.cfg - Remove the semi-colon in front of the CAN driver you want to use (section ComponentManager). - Set the component ID to the next number in the list (e.g. Component.8) - Save this file and restart the Control Win.
Last updated: 2023-09-14

Post by mondinmr on Jitter problems on imx8 ^{CODESYS Forge talk (Post)}
SOLVED!!! In this imx8 max_cstate=1 in kernel boot parameters is not working! We found a workaround: #include <stdio.h> #include <fcntl.h> #include <unistd.h> #include <stdint.h> int main(void) { int fd; uint32_t value = 0; fd = open("/dev/cpu_dma_latency", O_WRONLY); if (fd < 0) { perror("Error opening /dev/cpu_dma_latency"); return 1; } if (write(fd, &value, sizeof(value)) != sizeof(value)) { perror("Error writing to /dev/cpu_dma_latency"); close(fd); return 1; } while (1) { pause(); } } This simple code launched before CODESYS do the same work! Now jitter is identical as measured by cyclictest!
Last updated: 2023-10-19

Sort by relevance or date