Post by tk096 on High Cycle Times for SoftMotion_PlanningTask when using AxisGroup ^{CODESYS Forge talk (Post)}
Hi, you need a realtime capable plc. Codesys Control WinV3 is not realtime capable. https://content.helpme-codesys.com/en/CODESYS%20Control/_rtsl_performance_optimization_linux.html The last chapter of https://content.helpme-codesys.com/en/CODESYS%20SoftMotion/_sm_robotics_diagnosis_movement_problems.html deals with how to configure the planning task.
Last updated: 2024-03-13

Post by seweb on NTCIP ^{CODESYS Forge talk (Post)}
Hello everybody, In an upcoming project we are supposed to control a display board via NTCIP. Unfortunately, I have not yet found out whether this is possible with CODESYS. Are there any libraries for this in CODESYS? Best regards
Last updated: 2024-03-14

Post by fleaplc on MPC predictive control ^{CODESYS Forge talk (Post)}
Hi all, is there some library for Codesys to handle predictive models (MPC) such as https://www.mathworks.com/help/mpc/gs/what-is-mpc.html https://en.wikipedia.org/wiki/Model_predictive_control
Last updated: 2024-03-17

Post by valec on Connect local Asem HMI runtime to local Codesys Control Win V3 x64 ^{CODESYS Forge talk (Post)}
Solved: update all the software to the latest version, set optional user management, have a symbol configuration, check tasks priorities.
Last updated: 2024-03-28

Post by mibkid17 on Ethernet Adapter message: Adapter configured. Open all connections ^{CODESYS Forge talk (Post)}
Trying to control 525 with codsys the info from C-4 section. i should input the value in user defined parameters? in the generic device
Last updated: 2024-04-09

Post by tim-roelant on Problem mit control runtime V3 und profinet ^{CODESYS Forge talk (Post)}
Wann ich ein scan mache bekomme ich keine teilnehmer, mit ein ipscan sind alle da. Die version von Ethernet & Profinet master ist 4.3.1 (oder muss ich besser codesys actualisieren nach letzten stand?
Last updated: 2024-04-11

Post by eschwellinger on Cannot install Codesys control Multicore in raspberry pi 4 ^{CODESYS Forge talk (Post)}
just add in /etc/CODESYSControl_Usr.cfg [CmpRasPi] Architecture=armv7l for the 32Bit MC version... this is what this dialog does (or at least should do)
Last updated: 2024-04-22

Post by eschwellinger on CODESYS Control Raspberry Pi mit Servotreiber T6 von StepperOnline ^{CODESYS Forge talk (Post)}
Ist das RS232 oder RS485? Bei RS485 muss der Adaper also dein USB/Serial die Senderichtung in Hardware machen und das unterstützen. Abschlusswiederstände?
Last updated: 2024-06-01

Post by hjohnson123 on PLC Memory consumption? ^{CODESYS Forge talk (Post)}
Hi, How can you access the <root> of the Linux system? I'm struggling with this as the code above results in an invalid handle, as it cannot access '/'.</root> I am using Control for Raspberry Pi for context. Thanks.
Last updated: 2024-06-05

Post by kalmeyer on Stepper motor control with (SM_Drive_RaspStepper_direct) ^{CODESYS Forge talk (Post)}
I have installed: SM_Drive_PosControl 4.18.0.0 and SM_Drive_RaspiStepper_Direct 0.0.0.7 and SM_Drive_RaspiStepper_PulsDir 0.0.0.7 And when I "Generate Code" I immediately get 6 errors (see attached file) What can I do?????
Last updated: 2025-11-09

Post by kalmeyer on Stepper motor control with (SM_Drive_RaspStepper_direct) ^{CODESYS Forge talk (Post)}
Is there perhaps a place where I can see examples of programming with different instructions? This would be a great help. Maybe there are some places where ready-made programs are posted that can be downloaded and tested? /Klaus
Last updated: 2025-11-10

Post by eschwellinger on Stepper motor control with (SM_Drive_RaspStepper_direct) ^{CODESYS Forge talk (Post)}
.. try to use this projectarchive for the Stepper. In case you search for SoftMotion Examples: "c:\Program Files\CODESYS 3.5.21.X\CODESYS\CODESYS SoftMotion\Examples\Tutorial\"
Last updated: 2025-11-11

Post by gseidel on CODESYS SoftMotion Generic DSP402 on WAGO PFC200 + Festo CMMT-AS: MC_Power stays Busy, Controlword remains 0 ^{CODESYS Forge talk (Post)}
Hi gilad, I cannot tell for sure. But I think it should work on any PLC that is capable of doing motion control. Best regards, Georg
Last updated: 2026-07-01

Post by shivsrikakolum on SOFTMOTION - Error 34 when trying to execute and SMC_DI_AXIS_Error ^{CODESYS Forge talk (Post)}
I am using a Trio DX3 drive DC bus Unused , so I can control from SM3 Axis Datatype but as soon i try to Jog or Enable the MC_ Blocks It shows Error 36 can some one please the settings for this .
Last updated: 2026-07-07

Post by eschwellinger on Beckhoff CX9240 : Using Internal EtherCAT Bus ^{CODESYS Forge talk (Post)}
yes, you need to install Control RTE CX. In that package there is the Internal EthercatMaster / EthercatMasterSoftmotion which you could add then.
Last updated: 2026-07-10

Post by eschwellinger on CODESYS Control for Raspberry Pi 5 - "Hardware version or firmware version not supported" on Rev 1.1, persists across multiple runtime versions and OS images ^{CODESYS Forge talk (Post)}
see here: https://www.codesys.com/eco-system/up-to-date/release-lifecycle/release-plan-roadmap/ 18.8
Last updated: 2026-08-11

Post by timvh on Hilscher cards CoDeSys Control RTE ^{CODESYS Forge talk (Post)}
Completely managed by CODESYS, including licenses. You specifically have to set the parameters correctly in the CODESYSControl.cfg to let the RTE have access to the cards. See: https://content.helpme-codesys.com/en/CODESYS%20Control/_rtsl_windows_rte_v3_startup_cifx_hil.html
Last updated: 2026-08-06

Post by eschwellinger on CODESYS Control for Raspberry Pi 5 - "Hardware version or firmware version not supported" on Rev 1.1, persists across multiple runtime versions and OS images ^{CODESYS Forge talk (Post)}
you need to wait for the 4.22.0.0 release which will fix this problem
Last updated: 2026-08-10

Post by axberry on CODESYS Control for Raspberry Pi 5 - "Hardware version or firmware version not supported" on Rev 1.1, persists across multiple runtime versions and OS images ^{CODESYS Forge talk (Post)}
when is the releaseof the 4.2.0.0
Last updated: 2026-08-10

Post by eschwellinger on CAN TX regression in Control for Raspberry Pi 4.21.0.0 with CAN API library (RX works, TX silently fails) ^{CODESYS Forge talk (Post)}
seems to be an accident but there is a workaround in the Configfile: [CmpSocketCanDrv] AsyncSend=1 and will be solved with 4.22.0.0 Release
Last updated: 2026-08-17

Post by eschwellinger on How to reset forgotten User Management / Administrator password on CODESYS Control Win V3 (V3.5 SP22 Patch 2)? ^{CODESYS Forge talk (Post)}
since 3.5.20.10 version you should find it here: C:\Windows\system32\config\systemprofile\AppData\Roaming\CODESYS\xxxxxxxx (64Bit) C:\Windows\SysWOW64\config\systemprofile\AppData\Roaming\CODESYS\xxxxxxxx (32Bit) you need to have admin rights.
Last updated: 6 days ago

Post by rossanoparis on CAN TX regression in Control for Raspberry Pi 4.21.0.0 with CAN API library (RX works, TX silently fails) ^{CODESYS Forge talk (Post)}
Environment: Target: Revolution Pi (Kunbus RevPi), armv7l 32-bit OS: Raspbian GNU/Linux 9 (Stretch), kernel 4.19.95-rt38-v7 (SMP PREEMPT RT, built 2022-03-22) CAN: via SocketCAN (can0) Runtime: CODESYS Control for Raspberry Pi SL IDE: CODESYS V3.5 SP22 + patch 3 (previously V3.5 SP22 + patch 2, where everything worked with runtime 4.18.0.0) Library: CANBusAPI from the "CAN API" package, version 1.0.0.3 Summary: The setup worked correctly with V3.5 SP22 + patch 2 and runtime 4.18.0.0. After updating the IDE to SP22 + patch 3 and the runtime to 4.21.0.0, CAN transmission via the CANBusAPI library stopped working. Reception is unaffected. There are no error indications anywhere: the application runs normally and the CAN diagnosis reports a healthy bus. Systematic testing (below) shows the problem follows the runtime version, not the IDE update. Regression isolation: The same application (compiled under SP22 + patch 3, unchanged between tests) was downloaded to the same target with different runtime versions, changing only the runtime each time: 4.18.0.0: TX and RX both work 4.19.0.0: TX and RX both work 4.20.0.0: TX and RX both work 4.21.0.0: RX works, TX does not The behavior is fully reproducible in both directions (downgrading to 4.20 restores TX, upgrading to 4.21 breaks it again). Hardware, wiring, OS, project, and application code are identical across all tests. Diagnostic data (CANBusDiagnosis FB, while the application is transmitting on 4.21): ctSendCounter: incrementing normally ctTxErrorCounter: 0 ctRxErrorCounter: 0 eState: ERROR_FREE xBusAlarm: FALSE So the library accepts and counts the outgoing messages, no TX errors are reported, and the CAN controller state stays error-free, but the messages never reach the other nodes on the bus. Expected behavior: Messages sent via CANBusAPI (CANDriver / SendMessage) are transmitted on the bus, as with runtime versions up to and including 4.20.0.0. Notes: I am aware that the CAN API package (1.0.0.3, from 2016) is old; however, the regression is tied to the runtime version, since the identical binary works on 4.18-4.20. Questions: Is there a known change in CmpSocketCanDrv / CmpCAACanL2 between 4.20.0.0 and 4.21.0.0 that could affect TX via the CAN API library? Is runtime 4.21.0.0 still supported on Debian 9 Stretch (kernel 4.19, RT-patched), or is a newer OS required? If a minimum OS/kernel requirement was introduced with 4.21, is it documented?
Last updated: 2026-08-17

Post by cdutz on Problems connecting to Codesys 4.9.0.0 runtime on my Wago PFC200 ^{CODESYS Forge talk (Post)}
Hi all. I am currently struggling to get my Wago PFC200 running the Codesys Runtime in version 4.9.0.0 working. I am using Codesys V3.5SP19. I updated the PFC200 to the firmware version 04.01.10(23) after having tried the latest version (04.03.03(25) from Wago and not being able to start the runtime. After reading version 23 was needed, I changed to that and at least was able to have it start the codesys runtime. I also installed the "Codesys Control for PFC200 SL 4.9.0.0" plugin for Codesys to install the Codesys runtime in version 4.9.0.0 as well as update the Gateway on the device. While I seem to be able to connect to the gateway on the PLC (the dot is green) and when doing a scan, I do now find my PFC200, which is a huge improvement to before, where with firmware version 25 it just failed to start the runtime and I never found any device when doing a scan. Unfortunately I don't seem to be able to connect to the PLC in codesys. I logged in via SSH and changed the password and I can see that this password is correct as the stuff in the Codesys PFC200 tools tab only works if I use my changed password. And I used those credentials to update the installed Runtime version, which the log claimed to have worked fine. Now whenever I try to connect to the device found in the scan, I get a authentication pop-up with empy device name, device address: 000A. As User I use "root" and as password the password that I changed it to. As a response I just get "Ungültige Benutzerauthentifizierung auf dem Gerät" (Eng. probably something like "Invalid user authentication on the device". What could I be doing wrong? Admittedly I'm a bit lost here :-/ Chris
Last updated: 2023-08-26

Post by jeffg on ERROR: GetNetLinkSockAndInfoByMac(): could not open netlink socket: Too many open files ^{CODESYS Forge talk (Post)}
I just installed codesys runtime on a raspberry pi Cortex-A72 (ARM v8) 64-bit SoC @ 1.5GHz (Compute Module 4) I am running on Codesys control for raspberry pi 64 SL ver 4.13.0 and I keep getting a crash after about five to ten minutes. This program was running fine on a 32bit system with runtime 4.8 previously but they upgraded the panel PC cause it got smashed. Looking at the logs I see this error "ERROR: GetNetLinkSockAndInfoByMac(): could not open netlink socket: Too many open files" at the time of crash. I do have a UDP socket open for a serial to ethernet adapter and im wondering if maybe its opening a bunch of sockets and while receiving messages, Im not sending anything to the device only receiving. Below is the code used for the UDP VAR // Scale Comm fbPeerServer : NBS.UDP_Peer; ipAddress : NBS.IPv4Address; fbReceive : NBS.UDP_Receive; xPeerActiv : BOOL := TRUE; abyReceive : ARRAY [0..255] OF BYTE; sLastValidReceive : STRING(255); udiIndex : UDINT; END_VAR IF xPeerActiv AND NOT fbPeerServer.xBusy THEN ipAddress.SetInitialValue(ipAddress := gvlSettings.sIPAddres); fbPeerServer(xEnable := TRUE, itfIPAddress := ipAddress, uiPort := gvlSettings.uiPort); END_IF fbPeerServer(); fbReceive(xEnable := fbPeerServer.xBusy, itfPeer := fbPeerServer, pData := ADR(abyReceive), udiSize := SIZEOF(abyReceive)); IF fbReceive.udiCount > 0 THEN IF fbReceive.udiCount < SIZEOF(sLastValidReceive) THEN SysMem.SysMemCpy(pDest := ADR(sLastValidReceive), pSrc := ADR(abyReceive), udiCount := fbReceive.udiCount); // Set End of String sLastValidReceive[fbReceive.udiCount] := 0; END_IF END_IF If anyone as seen this I could really use some help figuring it out. I included the Log report
Last updated: 2024-09-19

Post by toffeebonbon on Die richtige CODESYS-Runtime auf dem Raspberry Pi ausrollen (3.5 SP18) ^{CODESYS Forge talk (Post)}
Guten Morgen, wie der Titel verrät soll es hier um das Ausrollen der CODESYS Runtime auf einem Raspberry Pi gehen. Ob ein klassischer Raspberry Pi aus dem Consumer-Bereich oder ein Compute-Modul spielt in dem Fall keine Rolle. Ich möchte nur anderen Nutzern Hilfestellung geben, die vielleicht ein vergleichbares Problem haben wie ich: Auf Raspberry Pi lief bei mir eine Anwendung, die mit Lizenzen auf einem CODESYS-Dongle lizenziert waren (Multicore-Support und Softmotion). Nach einem Hardware-Defekt habe ich meinen Rasperry Pi gegen eine robustere Lösung getauscht. Ich wollte auf der neuen Hardware die Runtime ausrollen und habe ständig den Fehler gezeigt bekommen, dass die Target- oder Zielsystem-ID nicht stimmt. Für den Raspberry Pi gibt es ja drei verschiedene Optionen der Runtime: 32bit Singlecore (armv6l) 32bit Multicore (armv7l) 64bit Multicore (aarch64) Entscheidend dafür, ob die 32 oder 64 Bit Runtime benötigt wird ist das auf der dem Raspberry Pi installierte Betriebssystem. In meinem Fall hatte ich durch die neue Hardware auch ein aktuellen Betriebsystem-Image aufgespielt, weshalb sich da der Umstieg von 32 auf 64Bit eingeschlichen hatte. In der Entwicklungsumgebung kann über Tools -> Control SL ausrollen das Fenster geöffnet werden, um die richtige Laufzeitumgebung auf dem Steuerungsrechner zu installieren. Bei kleinen Bildschirmen (bei mir ein 15" Laptop) kann der rechte Bereich "abgeschnitten" und das Dropdown-Menü als solches nicht auf den ersten Blick erkennbar sein. Mein Fehler war, dass ich den Scrollbalken nicht gesehen habe! (Bild im Anhang mit freundlicher Genehmigung von Herrn Heberle vom CoDeSys-Support) Nach dem auswählen der jeweils passenden Version kann die Runtime installiert und das Programm wieder geladen werden. Die Lizenzen sind bei mir wieder korrekt erkannt worden und alles läuft wie vorher (nur mit neuer Hardware). Vielen Dank an der Stelle noch mal an die schnelle Hilfe vom Support. Das hat wirklich top funktioniert.
Last updated: 2025-02-27

Sort by relevance or date