AC_Datalog DataLogChannel Save Cyclic is not working ^{CODESYS Forge talk (Thread)}
AC_Datalog DataLogChannel Save Cyclic is not working
Last updated: 2025-07-11

Post by davidbo on AC_Datalog DataLogChannel Save Cyclic is not working ^{CODESYS Forge talk (Post)}
"Save Cyclic" is set to 30s, but in my log I can see my variables are logged every 500ms which equals the cyclic time for my Task. Why is "Save Cyclic" ignored
Last updated: 2025-07-11

Post by jaguerop on j1939 ^{CODESYS Forge talk (Post)}
buenas noches, acudo a sus grandes conocimientos alguien quien mepuede orientar en j1939 y codesys 2.3 deseo controlar un motor deutz a traves de un plc CR0020 la aceleracion del motor diesel
Last updated: 2025-07-13

Script python for write in a file Project information ^{CODESYS Forge talk (Thread)}
Script python for write in a file Project information
Last updated: 2025-07-13

Post by iliyatsukerman on SoftMotion auf PFC200 ^{CODESYS Forge talk (Post)}
Hallo, Wir würden Ihre Unterstützung bei der Überprüfung der Kompatibilität der folgenden Konfiguration sehr schätzen: • PSTR-LO-16/400FEV ELMO • SCALANCE XC208 • WAGO PFC200 750-8213/40-010 • Die SPS (WAGO) wird gleichzeitig eingesetzt als: o EtherCAT-Master zur Kommunikation mit einem Elmo-Servoantrieb (EtherCAT-Slave, 4 Achsen – generisches CiA 402-Profil), und o Modbus-TCP-Server zur Kommunikation mit einem Siemens Modbus-TCP-Client, welcher zur Fernsteuerung des Elmo-Servoantriebs über die SPS dient. Bitte bestätigen Sie, ob die SPS in der Lage ist, diese Dualfunktion — als EtherCAT-Master und gleichzeitig als Modbus-TCP-Server — ohne Konflikte oder Performanceprobleme zu unterstützen. Insbesondere interessiert uns, ob die CODESYS SoftMotion SL Basislizenz (2305000000-F) notwendig ist, um 4 Servoachsen zu steuern, und ob diese Lizenz auf einer WAGO PFC200 SPS mit CODESYS Version 3.5 Service Pack 19 Patch 40 oder höher unterstützt wird. Alle Achsen im Servoantrieb werden unabhängig voneinander gesteuert. Mit freundlichen Grüßen. ILIYA
Last updated: 2025-07-13

SoftMotion auf PFC200 ^{CODESYS Forge talk (Thread)}
SoftMotion auf PFC200
Last updated: 2025-07-13

Post by dnordenberg on BOOL variable in OPC UA and modbus simultaneously ^{CODESYS Forge talk (Post)}
How can I have an BOOL variable that is read/write in both modbus TCP server and from OPC UA at the same time? Variables with %MX.n %QX.n addressing which is used for BOOL/coils in modbus server is not allowed in OPC UA symbol list on Schneider M251 controllers. I have already asked on Schneiders forum but there are not a lot of codesys experts over there :( So OPC symbols can't have a address and the modbus TCP server needs a address. So how should I do it then? It seems like an impossible combination. Since I want read/write access from both ways I can't just simply make a second variable and assign it the value of another since it would be a one way assignment. I also tried using VAR_CONFIG which then makes the address syntax %Q or %M in my main variable list and that fools OPC UA Symbol Configuration to allow it and then I add the complete %MX.n address of it in the VAR_CONFIG list. This semi works, I can toggle the BOOL from modbus but the OPC UA symbol seems to be read only. It displays symbol status but nothing happens when I toogle it. I think I need another way to have the variables and symbols pointing to the same bits in memory... My plan B is to write a BOOL array compare FB that saves a history bit from previous cycle and if that does not match current status at next cycle for either the OPC symbol or the modbus variable then it copies the new status over to the other. Maybe ugly but it's like my last alternative. Kind regards David
Last updated: 2025-07-14

Post by fkoenig on Codesys Control Win 64 3.5.21.0 KNX unaufgelöste Referenzen ^{CODESYS Forge talk (Post)}
Hallo Herr Schwellinger, wenn ich den KNX Stack in Ihrem Pfad des Configfiles hinzufüge, funktioniert es. Vielen Dank für Deine Unterstützung! Es wäre aber sehr hilfreich wenn dies in dem KNX Dokument oder in der der CoDeSys Hilfe mit drin stehen würde. Viele Grüße, Koeni
Last updated: 2025-07-14

Post by eschwellinger on CODESYS Control for Linux ARM SL (32 bit) on Moxa UC-3100 IPC ^{CODESYS Forge talk (Post)}
I would recommend to ask Moxa for a newer version of Debian. Debian 9 ("Stretch") has reached its end of life and is no longer receiving security updates from the official Debian Security Team as of June 30, 2022. This means any systems still running Debian 9 are vulnerable to security risks and should be upgraded to a newer, supported version of Debian like Debian 10 ("Buster") or Debian 11 ("Bullseye").
Last updated: 2025-07-14

Servo motor as an slave and AC motor as an Mster ^{CODESYS Forge talk (Thread)}
Servo motor as an slave and AC motor as an Mster
Last updated: 2025-07-14

CODESYS Control for Linux ARM SL (32 bit) on Moxa UC-3100 IPC ^{CODESYS Forge talk (Thread)}
CODESYS Control for Linux ARM SL (32 bit) on Moxa UC-3100 IPC
Last updated: 2025-07-14

Post by attarzade on Servo motor as an slave and AC motor as an Mster ^{CODESYS Forge talk (Post)}
Hello, I would like to control a servo motor via EtherCAT as a slave axis, and have it follow a master axis that is driven by a Control Techniques C200 AC drive (ethercat communication).Could anyone help me with how to achieve this setup? I use codesys version 3.5.20 and crevis Ethercat cards. AC drive is master axis and Servo drive is slave axis Thanks in advance
Last updated: 2025-07-14

Post by jonasz on Device diagnosis ( EtherCAT IO card ) ^{CODESYS Forge talk (Post)}
Hi, I'll link to the topic not wanting to start a new one. In the application I am building, I wanted to use the diagnostics described in the CAA Device Diagnosis library. In principle, everything is ok, except for the elements related to ModbusTCP. Despite the fact that ModbusTCP is taken into account in the documentation, it is not recognised via the interfaces. FUNCTION_BLOCK NET_HW_DIAG VAR_INPUT END_VAR VAR_OUTPUT END_VAR VAR (* Referencja do struktury z danymi dla HMI ASTRAADA.*) Visu: REFERENCE TO VISU; (* Wskaźnik na mastera EtherCAT.*) pEtherCATMaster : POINTER TO IoDrvEtherCAT; (* Wskaźnik na slave EtherCAT.*) pEtherCATSlave : POINTER TO EtcSlave; (* Interfejs dla węzła w drzewie urządzeń.*) _itfNode: DED.INode; (* Ogólny interfejs magistrali. Zapewnia podstawowe informacje o magistrali polowej.*) _itfBus: DED.IBus; (* Interfejs urządzenia. Zapewnia rozszerzone informacje o urządzeniu (magistralowym).*) _itfDevice2: DED.IDevice2; (* Ogólny interfejs magistrali. Zapewnia podstawowe informacje o magistrali polowej.*) _itfStack: DED.IStack; (* Numer węzła w drzewie urządzeń.*) uiNodes: UINT; (* Operator jest rozszerzeniem normy IEC 61131-3. W czasie wykonywania operator wykonuje konwersję typu odwołania do interfejsu na inny typ. Operator zwraca wynik BOOL. Wartość TRUE oznacza, że CODESYS pomyślnie wykonał konwersję. *) xQueryResultBus: BOOL; xQueryResultDevice2: BOOL; xQueryResultStack: BOOL; (* Struktura danych dotyczących węzłów w drzewie urządzeń.*) NetHwDiag: NW_HW_STAT; ModbusTcpClientDeviceInfo: IoDrvModbusTCP.DED.DEVICE_INFO; ModbusTcpClientDeviceState: IoDrvModbusTCP.DED.DEVICE_STATE; ModbusTcpDeviceInfo: IoDrvModbusTCP.DED.DEVICE_INFO; ModbusTcpDeviceState: IoDrvModbusTCP.DED.DEVICE_STATE; END_VAR (* Pobranie wskaźników dla pierwszego mastera i pierwszego slave w sieci EtherCAT.*) pEtherCATMaster := g_pFirstMaster; pEtherCATSlave := pEtherCATMaster^.FirstSlave; (* Diagnostyka sieci EtherCAT.*) pEtherCATMaster := g_pFirstMaster; pEtherCATSlave := pEtherCATMaster^.FirstSlave; NetHwDiag.xConfigFinished := pEtherCATMaster^.xConfigFinished; NetHwDiag.xDistributedClockInSync := pEtherCATMaster^.xDistributedClockInSync; NetHwDiag.xError := pEtherCATMaster^.xError; NetHwDiag.xSyncInWindow := pEtherCATMaster^.xSyncInWindow; NetHwDiag.sLastMessage := pEtherCATMaster^.LastMessage; NetHwDiag.LastError := pEtherCATMaster^.LastError; (* Diagnostyka drzewa urządzeń.*) uiNodes := 0; _itfNode := DED.GetRoot(); REPEAT NetHwDiag.asDeviceName[uiNodes] := DED.GetDeviceNameString(itfNode := _itfNode); xQueryResultBus := __QUERYINTERFACE(_itfNode,_itfBus); IF xQueryResultBus THEN _itfBus.GetBusInfo(buiInfo := NetHwDiag.aBusInfo[uiNodes]); NetHwDiag.aBusState[uiNodes] := _itfBus.GetBusState(); END_IF xQueryResultDevice2 := __QUERYINTERFACE(_itfNode,_itfDevice2); IF xQueryResultDevice2 THEN _itfDevice2.GetDeviceInfo(deiInfo := NetHwDiag.aDeviceInfo[uiNodes]); NetHwDiag.aDeviceState[uiNodes] := _itfDevice2.GetDeviceState(); IF pEtherCATSlave <>0 THEN pEtherCATSlave^(); IF pEtherCATSlave^.SlaveAddr = NetHwDiag.aDeviceInfo[uiNodes].idSystem THEN NetHwDiag.aAlStatus[uiNodes] := pEtherCATSlave^.ALStatus; pEtherCATSlave := pEtherCATSlave^.NextInstance; END_IF END_IF ELSE xQueryResultStack := __QUERYINTERFACE(_itfNode,_itfStack); IF xQueryResultStack THEN _itfStack.GetDeviceInfo(deiInfo := NetHwDiag.aDeviceInfo[uiNodes]); NetHwDiag.aDeviceState[uiNodes] := _itfStack.GetDeviceState(); END_IF END_IF uiNodes := uiNodes + 1; _itfNode := DED.GetNextNode(_itfNode); UNTIL _itfNode = 0 END_REPEAT (* Diagnostyka Modbus.*) Modbus_TCP_Client.GetDeviceInfo(deiInfo := ModbusTcpClientDeviceInfo); ModbusTcpClientDeviceState := Modbus_TCP_Client.GetDeviceState(); PAC_3200T.GetDeviceInfo(deiInfo := ModbusTcpDeviceInfo); ModbusTcpDeviceState := PAC_3200T.GetDeviceState(); Of course, you can take the easy way out and refer directly to the devices, but I wanted a reusable component. Any constructive help is very welcome Best regards Jonasz
Last updated: 2025-07-15

Custom colors in Ladder diagrams? ^{CODESYS Forge talk (Thread)}
Custom colors in Ladder diagrams?
Last updated: 2025-07-15

Device diagnosis ( EtherCAT IO card ) ^{CODESYS Forge talk (Thread)}
Device diagnosis ( EtherCAT IO card )
Last updated: 2025-07-15

Problem with Licences IDE 3.5.16.40 ^{CODESYS Forge talk (Thread)}
Problem with Licences IDE 3.5.16.40
Last updated: 2025-07-15

Post by rafa on MODBUS TCP SERVER DONT AUTO-STARTUP ^{CODESYS Forge talk (Post)}
Dear all, I have a project where I have two ModbusTCP communication drivers in the application. It's working normally until a power outage or the installation panel is restarted. As soon as the PLC CPU is restarted, the Ethernet port is OK, but the TCP Server displays an "UNDEFINED" error. I can't reset the error using the diagnostic confirmation or the "mbserver.xConfirmError" bit. I noticed that the error only appears in the "mbserver.byModbusError" memory and the description is "UNDEFINED." The "mbserver.xError" memory doesn't flag an error. When using the warm restart function and then START CPU, the devices return to normal operation. The following demonstration images; The main question is: How can I make devices boot automatically?
Last updated: 2025-07-15

MODBUS TCP SERVER DONT AUTO-STARTUP ^{CODESYS Forge talk (Thread)}
MODBUS TCP SERVER DONT AUTO-STARTUP
Last updated: 2025-07-15

Post by rafa on MODBUS TCP SERVER DON'T AUTOMATIC STARTUP ^{CODESYS Forge talk (Post)}
Dear all, I have a project where I have two ModbusTCP communication drivers in the application. It's working normally until a power outage or the installation panel is restarted. As soon as the PLC CPU is restarted, the Ethernet port is OK, but the TCP Server displays an "UNDEFINED" error. I can't reset the error using the diagnostic confirmation or the "mbserver.xConfirmError" bit. I noticed that the error only appears in the "mbserver.byModbusError" memory and the description is "UNDEFINED." The "mbserver.xError" memory doesn't flag an error. When using the warm restart function and then START CPU, the devices return to normal operation. The following demonstration images; The main question is: How can I make devices boot automatically? Um using Codesys Version 3.5.20.30 Patch 3+ My CPU is a Weintek Cmtx Built-int - ( CMT3092x )
Last updated: 2025-07-15

Post by jakubmphoenix on EtherCAT Master on RaspberryPi with EtherCAT Slave on Beckhoff ^{CODESYS Forge talk (Post)}
Hello everyone, I’m currently working on setting up an EtherCAT Master using CODESYS on a Raspberry Pi, and I’ve run into some issues I could use help with. Project Setup: EtherCAT Master: Raspberry Pi with CODESYS Control for Raspberry Pi 64 SL installed EtherCAT Slave: Beckhoff CX5130 with EK1200 coupler I/O Module: EL2008 License Module: EL6070-0033 I’ve installed the required CODESYS packages and the Linux gateway on the Raspberry Pi. In my project, I added the EtherCAT Master with the appropriate port settings and scanned for devices. The CX5130 shows up as a slave, but communication fails—I'm getting error messages and can't access the outputs. Specifically: The EL2008 output module isn’t recognized properly in CODESYS. There’s no option to communicate with it through the CX5130. I’ve tried connecting via both the Raspberry Pi’s built-in Ethernet port and an external network card. I've attached screenshots showing the errors I get in CODESYS and the devices detected via TwinCAT for reference. Any help or suggestions would be greatly appreciated! Thanks in advance! EMERGENCY FROM DEVICE 1001 ERROR CODE 16#A000 Error register 16#02 Error field: 16#02 Error field : 16#0E 16#04 16#00 16#04 16#00
Last updated: 2025-07-16

EtherCAT Master on RaspberryPi with EtherCAT Slave on Beckhoff ^{CODESYS Forge talk (Thread)}
EtherCAT Master on RaspberryPi with EtherCAT Slave on Beckhoff
Last updated: 2025-07-16

Post by gmau on RS232 Communication in CODESYS Control RTE V3 ^{CODESYS Forge talk (Post)}
Hello, I would like to implement RS232 communication into CODESYS Control RTE V3. I was writing the program testing it on CODESYS Control Win V3, where it worked fine. When I changed it to RTE, the communication was on, but I cannot send the data between PLC and scale - there is no or little response from scale - mostly one time receive and that is it. On Win V3 it was working fine. I read that I am supposed to configure CODESYSControl file for a proper communication using RTE, but even after that I can not get a stable and working communication. I am attaching my CODESYSControl and CODESYSControlUser data below, as well as I am sending the code from communication function. The communication should be through COM1 port of PC. CODESYS Version: CODESYS V3.5 SP21 + (64-bit) Runtime + Version: CODESYS Control RTE V3 Version 3.5.21.0 / CODESYS Gateway V3 - x64 Version 2.5.21.0 I would be much gratefull for any help. Sincerely,
Last updated: 2025-07-16

Post by installwhat on Login to Visu optional ^{CODESYS Forge talk (Post)}
you can restyle the landing page and do a login via st
Last updated: 2025-07-16

Login to Visu optional ^{CODESYS Forge talk (Thread)}
Login to Visu optional
Last updated: 2025-07-16

Post by installwhat on Opc remote alarms on Linux box ^{CODESYS Forge talk (Post)}
It seems that the hmi sl license only works with windows. If i'm happy using web visu, rather than target visu, is possible to use remote opc-ua remote alarms without the hmi sl? Maybe it can be included in a different license that works on Linux? thanks
Last updated: 2025-07-16

Sort by relevance or date