Post by ben1 on How to stay in a method until something is finished. ^{CODESYS Forge talk (Post)}
Why must you use a method? Top of my head can't you just use the button to turn on a bit and use it in a normal task? Just turn a bit on with the button, and run a TON from it in code, and turn it back off with the ton. And then just log the pressure on both the rising & falling edge?
Last updated: 2025-11-03

Post by bertus on Can't get SMC_SmoothPath to work ^{CODESYS Forge talk (Post)}
Thanks. I will do more investigation and testing next week.
Last updated: 2026-01-02

Post by josepmariarams on Limit Axis CNC Jerk using SMC_Polynomial_AbsMaxLocs ^{CODESYS Forge talk (Post)}
Dears. Until now, I have been using CNC libraries with Codesys 3.5SP11. I was using SMC_Polynomial_AbsMaxLocs function, from CNC library, to calculate the axis jerks, interpolating splines, to limit it. Now I have passed to SP20, and the functions which calculates the zeros and the maximum-minimum and zeros of polynomials has been disapeared. Questions: -Exist any FB wich can limit the jerk of individual axis in CNC? -Exist any other functions which can calculate max-min and zeros of polynomials? Thanks
Last updated: 2026-05-22

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

Post by nz-dave on *exception* [processorloadwatchdog] occurred in: app=[all], task=[all] ^{CODESYS Forge talk (Post)}
Can anyone shed some light on this issue im having. at random, sometimes days, sometimes weeks or months. i get this error and have to reset the plc. Im using a Weintek HMI with ethernet/ip remote io and vsd. i have tried increasing my task times and watchdogs. and when i view my PLCload in the shell its normally around 3-4%, highest ive ever seen is 7%. Nothing i do seems to help the issue. Could the HMI's Codesys CPU be getting to hot do to high ambient temp?
Last updated: 2026-02-01

Post by konstantin on Lenze i950 Servo and WAGO PFC200 ^{CODESYS Forge talk (Post)}
Hello, In our workshop we have a Lenze i950 servo drive that has an EtherCAT bus and CiA402 compatibility. The WAGO is PFC200 750-8212 and as per documentation it has built-in license for SoftMotion Light functionality. It is not capable of supporting the full SoftMotion functionality like gearing and synchronizing. I added the EtherCAT esi files from Lenze and the EtherCAT master does see the drive, then I added a SoftMotion Light Axis object. The problem is that I can only energize the axis, I cannot execute any other commands. I set the positive and negative torque limits from the PDOs to 200% and when I try to move the axis by force it does not move back to its original position. I use the SML function blocks from the PLCOpen library and the error from the function blocks is that the op mode cannot be changed. Then I tried using a standard SoftMotion axis object and everything works fine, except the MC_Home function block. The axis moves back to its position when forced out of it. I follow this guide from Lenze - Lenze i950 CODESYS V3 What could cause this issue with the SoftMotion Light axis object? Best Regards Konstantin Kolev
Last updated: 2026-02-11

Post by tommyk-mar on Smooth path is not working with SMC_NCInterpreter ^{CODESYS Forge talk (Post)}
Hello, Im using SMC_NCInterpreter and SMC_NCReadFile2 to read gcode program for CNC machine and what I have observed is that G51 and G52 is not smoothing the path. Machine stops in every point, what could I do to make machine pass through the points without stopping or what could allow me to use smooth path corretly if I use NCInterpreter. Im using it because I want to add variables to my gcode and its not possible directly from the CNC editor thats why I do use external file. Any ideas?
Last updated: 2026-03-26

Post by eschwellinger on RaspberryPi 5 gateway problem ^{CODESYS Forge talk (Post)}
Which CODESYS version and which runtime version do you use?
Last updated: 2026-05-22

Post by timvh on Block the program upload ^{CODESYS Forge talk (Post)}
Don't share your username and password.
Last updated: 2026-10-21

Post by smeitink on Timeout Error in Modbus Communication with WAGO PFC200 and iEM2050 Meter using 750-652 Module ^{CODESYS Forge talk (Post)}
Hi all, I'm looking for help with an issue I've come across while trying to facilitate Modbus communication between a WAGO PFC200 PLC using a 750-652 communication module and an iEM2050 Series Single Phase Energy Meter. I believe to have everything wired and setup correcty, but I keep running into a "Error time out" message, and by now I don't really know what else to try. My setup is as follows: A PFC200 Wago PLC, which has 2 750-652 Serial Interfaces extension modules connected to its field bus. I'm using one of these to talk to a Schneider iEM2050 - kWh-meter over modbus. I have connected terminal 23 (A) of the iEM2050 to connector 6 (A) on the 750-652. I have connected terminal 24 (B) of the iEM2050 to connector 2 (B) of the 750-652. I'm using 200mm of twisted together wires to connected them both, and I have placed a 120 ohm resistor between A and B at both ends. I've attached relevant pinout images to this post. I then wrote a simple program that configures the Mobus port, as per the datasheet of the iEM2050. You can find an image of the relavent page attached to this post too. This is my program: PROGRAM PLC_PRG VAR Master: FbMbMasterSerial; xIsConnected: BOOL; xError: BOOL; iIndex: INT := 1; xTrigger: BOOL; utQuery : typMbQuery := ( bUnitId := 1, // The Modbus unit or slave address bFunctionCode := 4, // Function code for reading input registers uiReadAddress := 1829, // adress for the Power on off counter uiReadQuantity := 1 // Quantity of registers to read ); iStep: INT; oStatusModbus: WagoSysErrorBase.FbResult; utResponseModbus: typMbResponse; xConnect: BOOL := FALSE; delayTimer: TON; END_VAR Master( xConnect:= xConnect, I_Port:= _750_652_24_1, udiBaudrate:= 9600, usiDataBits:= 8, eParity:= WagoTypesCom.eTTYParity.Even, eStopBits:= WagoTypesCom.eTTYStopBits.One, eHandshake:= WagoTypesCom.eTTYHandshake.None, ePhysical:= WagoTypesCom.eTTYPhysicalLayer.RS485_HalfDuplex, xIsConnected=> xIsConnected, xError=> xError, oStatus=> oStatusModbus, eFrameType:= WagoAppPlcModbus.eMbFrameType.RTU, tTimeOut:= T#5S, utQuery:= utQuery, xTrigger:= xTrigger, utResponse:= utResponseModbus); delayTimer(IN := TRUE, PT := T#3S); // Use the Q output of the timer to set xConnect after the delay IF delayTimer.Q THEN xConnect := TRUE; END_IF CASE iStep OF 0: //Wacht totdat de master de poort geopend heeft IF xIsConnected THEN iStep := 1; END_IF 1: //Stuur request naar de slave xTrigger := TRUE; iStep := 2; 2: //Wacht totdat de master klaar is met het afhandelen van de request IF NOT xTrigger THEN iStep := 3; END_IF END_CASE The TON delay before opening the port is due to a an error I encountered when opening it straight away. This seems to be a bug, as described here. However, the TON solved that particular issue. I tried reading multiple registers, but like I said, I still always end up with the "Error time out". What else can I test or try at this point?
Last updated: 2024-02-24

Post by youness on No source code available (cip object) ^{CODESYS Forge talk (Post)}
Hi yotaro, hope your problem was resolved. I had the same, but with an other library title. This exception is not detected during compilation, but rather at a given position in the program (when switching to a given visualization). Although the exception is generated at this point, it does not involve the visualization in question. This error is due to one of 3 reasons: 1) A division by zero somewhere: The program is able to detect divisions by zero at compile time. But in the case of a variable, which takes a valid value at init and changes to 0 at a later stage. 2) An invalid pointer: (either because it has a value of 0, or because it points outside the memory reserved for the program) is being dereferenced. Locate any pointers or interfaces you have in the code and check them - you should also be wary of mixing inline modifications and pointers. 3) Array overflow: Generally when a processing operation is executed outside the array's definition range. Example: a write loop with n iterations is executed on an array of dimmension n-1. On the other hand, the error message may not appear. In the latter case, the error may have fatal consequences, as the overflow has induced writing to potentially forbidden memory areas. This problem can be explained by the fact that it's not always the adjacent memory areas of PLC_PRG that are overwritten, but the memory areas that are randomly allocated to the array during compilation. In this case, however, there is no entry in the log, so you need to integrate the "Implicit Check function", which checks the line of code generating the error. To integrate this functions, click on Application --> POU for implicit controls Regards,
Last updated: 2024-07-16

Sort by relevance or date