Release SP20 - Changes in behaviour? ^{CODESYS Forge talk (Thread)}
Release SP20 - Changes in behaviour?
Last updated: 2024-03-25

Recipe Manager in PRG (3.05.13.XX) ^{CODESYS Forge talk (Thread)}
Recipe Manager in PRG (3.05.13.XX)
Last updated: 2024-04-15

Set several bits in WORD ^{CODESYS Forge talk (Thread)}
Set several bits in WORD
Last updated: 2024-04-22

Remove white spaces in file .txt ^{CODESYS Forge talk (Thread)}
Remove white spaces in file .txt
Last updated: 2024-04-23

RevPi piBridgeRight not found in project. ^{CODESYS Forge talk (Thread)}
RevPi piBridgeRight not found in project.
Last updated: 2024-04-27

Rounding error in simple addition ^{CODESYS Forge talk (Thread)}
Rounding error in simple addition
Last updated: 2024-05-25

"CAA" meaning in library names ^{CODESYS Forge talk (Thread)}
"CAA" meaning in library names
Last updated: 2024-05-31

Active alarm access in ST ^{CODESYS Forge talk (Thread)}
Active alarm access in ST
Last updated: 2024-06-06

how to use UseDataExpanding() in datasource ^{CODESYS Forge talk (Thread)}
how to use UseDataExpanding() in datasource
Last updated: 2024-06-17

Custom configure tab in device editor ^{CODESYS Forge talk (Thread)}
Custom configure tab in device editor
Last updated: 2025-10-20

Nach Neuinstallation Plug-In Fehler ^{CODESYS Forge talk (Thread)}
Nach Neuinstallation Plug-In Fehler
Last updated: 2026-01-22

Gateway in China - "Gateway not connected" ^{CODESYS Forge talk (Thread)}
Gateway in China - "Gateway not connected"
Last updated: 4 days ago

Post by user3000 on Can't find an Extended Pulse Timer (TP and LTP) ^{CODESYS Forge talk (Post)}
Hello, For my program I need an extended pulse timer, which can be referred to as a retriggerable pulse timer. Where every rising edge of the input resets the elapsed time zero, extending the lenght of the output pulse. The Codesys pulse timer (TP) is a one-shot timer and only resets the elapsed time with the falling edge of the input. There is also a pulse timer (LTP) in codesys, but in my simulation it was also functioning as a one-shot even though the description sounds like LTP should be retriggerable. I have uploaded some timing plots from another PLC program for reference. I am looking for a timer equivalent to the "TEP" diagram. Is there an Extended Pulse Timer in Codesys? Maybe there is a way to manipulate the input so it resets the elapsed time outside the function block?
Last updated: 2023-12-06

Post by macros8 on Alarm Management - Import and Export of AlarmGroup ^{CODESYS Forge talk (Post)}
Hi, I struggle with exporting my Alarm Messages and following importing back to my project. Because filling in one by one is very time consuming I want to use export function and edit .csv file in Excel. As soon as I modify the file the import back to project does not work at all and function returns errors. Would you pls give me a hint how to properly use this functionality? Thanks a lot for help. Regards, M.
Last updated: 2023-12-02

Post by arvindkumar on Wago plc not going back to RUN Mode after Power failure ^{CODESYS Forge talk (Post)}
Hi im using wago pfc750-8207 plc and my programming software was codesys v2.3, im facing some issue in my plc after power failure my plc not going back to run mode sometimes, i did sourecode download, boot application created and still facing this issue, out of 10 power failure 8 times its going to run mode some time its missing to go run mode and only sys indication is in on condition Kindly please help me.
Last updated: 2023-12-15

Post by aniket-b on Multiple function blocks are not executing at the same time in ladder logic ^{CODESYS Forge talk (Post)}
I have two ethernet Ip drives and created Function Blocks for different motions tasks. I am using same FB for both the drives. When I try to execute the relative move start command on FB for both the drives it is not working. However, if I add 1ms second delay between the execution of each drive it is working. Also when I change the rung order it is working for the first drive in the rung. what could be the wrong here?
Last updated: 2024-03-12

Post by food on Beaglebone Black OPC-UA Server ^{CODESYS Forge talk (Post)}
Man, this was a long time ago. I think the problem probably stemmed from not loading the certificates from the client and the server on the server and client respectively in the correct manner. I believe I ended up getting around it just by removing all security on the server. In the end we did not move forward with that architecture so I never had to actually fix it.
Last updated: 2024-04-10

Post by dkugler on Alarm State Icon ^{CODESYS Forge talk (Post)}
thank you for pointing me to this "bug"!! I haven't recognized, the bit is reset after the first alarm is gone. I use this only for warnings, so it's not a drama, but was not correct in the past. I solved it now simply stupid by counting up a variable every time an alarm appears and decreasing it if an alarm is gone. The "warning lamp" is activated by checking the counter is > 0 The nice side effect, i'm able to show the number of active alarms in the state line now.
Last updated: 2024-04-24

Post by ndzied2 on Rounding error in simple addition ^{CODESYS Forge talk (Post)}
This is a consequence of how computers store floating point numbers. 0.1 cannot be exactly represented in a computer. This is not a CoDeSys thing. Here is a link to a converter to show you the exact value that is represented when you use a REAL data type (which is a 32 bit float). https://baseconvert.com/ieee-754-floating-point If you really need to keep track of 0.1 increments. use INT OR DINT and then add 1 each time and assume that there is one decimal place.
Last updated: 2024-05-24

Post by bitwitch on Einheiten umrechnen, Numpad und Eingabegrenzen ^{CODESYS Forge talk (Post)}
Das Codesys-Objekt 'Einheiten umrechnen' wirkt auf timeVar (TIME) z.B. innerhalb eines Visu-Rechtecks und funktionier in den Grundfunktionen einwadfrei. Die Ausgabe der Std. von timeVar läuft. Beispiel: Bei t#3d2h10m wird wunschgemäß 74h (volle Std-Anzahl). Die Grenzüberwachung Max= 10 funktioniert nicht, da die Angabe scheinbar ms erwartet (arbeitet mit 10ms). Irgend wie muss man jetzt codesys davon überzeugen, dass auch für Min und Max die Einheitenumrechnerei wirken soll, wobei die Eingabe der Grenzen in Std erfolen muß. Hat jemad einen TiPPPPPPPPP?
Last updated: 2024-06-14

Post by s1mon on Two OneWireMaster on one Raspberry PI 5 ^{CODESYS Forge talk (Post)}
All Sensors from the OneWire Master are assigned already to a seperate task with low prio (26) that runs with 1s cycle time. My EtherCat Task is running with Prio 1. It all works fine, until I adjust the CODESYScontrol.cfg or the CODESYScontrol_Usr.cfg files so that it supports a 2nd OneWire Master in the Codeys Runtime. If I change something in this config file and reboot my EtherCat Master stops working.
Last updated: 2025-10-19

Post by gseidel on Scara3 kinematic robot error ^{CODESYS Forge talk (Post)}
Hi aniket-b, the maximum cycle time of the EtherCAT_Task is very high, ca. 35 ms. Could you please check if this is just the first cycle after starting the application or if it happens during motion? (You can reset the times in the task configuration by right-clicking in the "monitoring" tab.) Another thing to try: put the SoftMotion_Planning task on a different core. Best regards, Georg
Last updated: 2026-01-07

Post by open on How to create a stopwatch? ^{CODESYS Forge talk (Post)}
Hi @ph0010421, I tried the program the TimeTaken is calculated when stop is triggered. I want the TimeTaken to be continuously calculated and counting when a BOOL variable is true. I tried to program this way: Declaration: PROGRAM PLC_PRG VAR bStartStop: BOOL := FALSE; // Start/Stop button bReset: BOOL := FALSE; // Reset button bRunning: BOOL := FALSE; // Flag indicating whether the stopwatch is running tStartTime: TIME; // Variable to store the start time tElapsedTime: TIME; // Variable to store the elapsed time END_VAR Implementation: // Main program logic IF bReset THEN // Reset button pressed, reset the stopwatch bRunning := FALSE; tElapsedTime := T#0s; ELSIF bStartStop THEN // Start/Stop button pressed, toggle the running state IF bRunning THEN // Stop the stopwatch bRunning := FALSE; ELSE // Start the stopwatch bRunning := TRUE; tStartTime := tElapsedTime; END_IF; END_IF // Update the elapsed time when the stopwatch is running IF bRunning THEN tElapsedTime := tElapsedTime + T#1s; // Adjust the time increment as needed END_IF However counting of the seconds is not accurate. I tried changing the main task cycle time interval to 1000ms. The counting of seconds become slower. (see attached) Please help
Last updated: 2023-12-08

Post by mubeta on Some 'pathetic' errors in SoftMotion program ^{CODESYS Forge talk (Post)}
Hello everyone, I have a very simple program for the process, but it's driving me crazy and I can't see the problems I'm left with: Short topological description: Dual Core Berghof controller with softmotion runtime version 3.5.19.30; Two axes with servodrive on canopen bus, clocked distributed from master; Ethercat I/O node; 2 ms ethercat task, 2 ms canopen bus cycle time; I/O objects of the canopen master and canopen drives connected to the ethercat task cycle; Problem 1: Two separate programs each manage their own axis and drive, with separate state machines. A first axis moves primarily in velocity, except having to position itself absolutely at a predetermined point at the end of the job; the second axis, on the other hand, is a paper unwinder that changes, for each job cycle, from actions in absolute, relative, and cam displacement with the master axis. Well, the state machine of both axes was written in such a way as to call running the useful FB and change it on state change in this way: CASE i_stateMachine OF 0: o_Power(Enable := TRUE, bRegulatorOn := FALSE, bDriveStart := FALSE, Axis := o_PaperUnwinderAxis); o_MoveAbs(Execute := FALSE, Axis := o_PaperUnwinderAxis); o_MoveRel(Execute := FALSE, Axis := o_PaperUnwinderAxis); o_CamSelect(Execute := FALSE, Master := o_MachineAxis, Slave := o_PaperUnwinderAxis, CamTable := cam_PaperUnwinder); o_CamIn(Execute := FALSE, Master := MachineEncoder, Slave := o_PaperUnwinderAxis); o_CamOut(Execute := FALSE, Slave := o_PaperUnwinderAxis); o_SetPosition(Execute := FALSE, Axis := o_PaperUnwinderAxis); IF ... THEN i_StateMachine := 10; END_IF; 10: o_Power( Enable := TRUE, bRegulatorOn := TRUE, bDriveStart := TRUE, Axis := o_PaperUnwinderAxis ); IF o_Power.Status THEN i_StateMachine := 20; END_IF; 20: (* Avanzamento carta *) o_MoveAbs( Execute := TRUE, Position := o_Somewhere, Velocity := 25.0, Acceleration := 3666.7, Deceleration := 3666.7, Jerk := 48000.0, Direction := MC_DIRECTION.positive, Axis := o_PaperUnwinderAxis ); IF o_MoveAbs.Done THEN o_MoveAbs(Execute := FALSE, Axis := o_PaperUnwinderAxis); i_StateMachine := 30; END_IF 30: d_HomingPosition := ...; o_SetPosition( Execute := TRUE, Position := d_HomingPosition, Mode := FALSE, Axis := o_PaperUnwinderAxis ); (* ... *) IF o_SetPosition.Done = TRUE THEN o_SetPosition(Execute := FALSE, Axis := o_PaperUnwinderAxis ); o_LogServer.Append(sMessage := '...', lscClass := LOGSERVER_CLASS.ALWAYS, sdt := o_CommonsMgrData.systime.sdtLocal); i_StateMachine := 40; END_IF; 50: ... The code above is a sketchy example of what I wanted to write. But it gives me a spot problem: in some, the state change results in a drive error, which is unrecoverable except with a reinitialization via SM3_ReinitDrive(). Things are improved a little if in the program I always run the call of all softmotion blocks in this way: o_Power(Axis := o_PaperUnwinderAxis); o_Jog(Axis := o_PaperUnwinderAxis); o_Halt(Axis := o_PaperUnwinderAxis); o_MoveAbs(Axis := o_PaperUnwinderAxis); o_MoveRel(Axis := o_PaperUnwinderAxis); o_CamIn(Master := MachineEncoder, Slave := o_PaperUnwinderAxis); o_CamOut(Slave := o_PaperUnwinderAxis); If I don't execute all the calls of all the motion FBs used, when exchanging machine state often (but not always), the axis goes into error with event id THE_FB_WASNT_CALL... Done a little diagnostics it seems that the FBs return the bDone, before they are completely terminated. I tried doing the machine state exchange not with the bDone bit of the FBs, but with the 'standstill' state of the axis. It didn't seem to change anything. Problem 2: During the use SM3_ReinitDrive() I get the erro in the log: "NetID 0: SDO read error for object 16#607C..." Assuming that the device involved it's one of the two servodrive, (no others device are present in the network), I don't found any object 0x607C in the 'possible object list in/out' of the two drive, and I don't understand where this object can be listed. So any ideas and suggestions regarding these two issues will be very, very welcome. If you need the source project, I am willing to send it.
Last updated: 2024-07-17

Post by acc00 on Main Task cycle too long leading to PLC Fail ^{CODESYS Forge talk (Post)}
I have 2 Wago PFC200 PLC, running with Runtime SP19 Patch 5, with the Redundant application. The PLC communicates as Modbus Master with at this moment 15 Modbus Slaves -later there will be 28 in total- (Drives, Power management units,...). These devices are connected in 2 rings (1 ring of Drives, 1 ring of Power Management units), with 2 Managed Moxa Switches being part of the ring. Each PLC is connected to one of these switches. The issue I'm encountering is that the Cycle time of the Active PLC goes very high when I'm closing the Drive ring (simulating an issue on one Cabinet supply, resulting in that one Drive shut down, which can happen on field quite often). As a result of this long cycle, the PLC fails and goes to Exception, and the Passive PLC does not take control of the system. A normal cycle is around 30ms for the Main task, and a few ms for the Ethercat task. When I monitor with Profiler, I see that in this Maximum Cycle, the main Task is only taking 13ms, so I'm not sure where the PLC is hanging for so long. Is the remaining cycle time the Redundant management/sync or something else? Thank you in advance.
Last updated: 2024-03-08

Sort by relevance or date