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

Home (version 1) discussion ^{dnordenberg wiki (Thread)}
Home (version 1) discussion
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

Home (version 1) discussion ^{cpoi wiki (Thread)}
Home (version 1) discussion
Last updated: 2025-07-14

wiki Discussion ^{infinitetool wiki (Discussion)}
Forum for wiki comments
Last updated: 2025-07-14

blog Discussion ^{infinitetool blog (Discussion)}
Forum for blog comments
Last updated: 2025-07-14

Home ^{infinitetool wiki (WikiPage)}
Project Members: infinitetool (admin)
Last updated: 2025-07-14

(no subject) ^{infinitetool wiki (Thread)}
Last updated: 2025-07-14

wiki Discussion ^{danielmbuyu wiki (Discussion)}
Forum for wiki comments
Last updated: 2025-07-14

blog Discussion ^{danielmbuyu blog (Discussion)}
Forum for blog comments
Last updated: 2025-07-14

Home ^{danielmbuyu wiki (WikiPage)}
Project Members: danielmbuyu (admin)
Last updated: 2025-07-14

(no subject) ^{danielmbuyu wiki (Thread)}
Last updated: 2025-07-14

wiki Discussion ^{princentuk wiki (Discussion)}
Forum for wiki comments
Last updated: 2025-07-15

blog Discussion ^{princentuk blog (Discussion)}
Forum for blog comments
Last updated: 2025-07-15

(no subject) ^{princentuk wiki (Thread)}
Last updated: 2025-07-15

Home ^{princentuk wiki (WikiPage)}
Project Members: princentuk (admin)
Last updated: 2025-07-15

wiki Discussion ^{williamwi wiki (Discussion)}
Forum for wiki comments
Last updated: 2025-07-15

blog Discussion ^{williamwi blog (Discussion)}
Forum for blog comments
Last updated: 2025-07-15

Home ^{williamwi wiki (WikiPage)}
Project Members: williamwi (admin)
Last updated: 2025-07-15

(no subject) ^{williamwi wiki (Thread)}
Last updated: 2025-07-15

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

Post by piesprancer on Custom colors in Ladder diagrams? ^{CODESYS Forge talk (Post)}
you could try adjusting your monitor’s color profile or IDE contrast settings to make the blue less harsh. https://content.helpme-codesys.com/en/libs/EtherCATStack/Current/EtherCATStack/pou-ETCMasterStack/DynamicConfig/fld-DynamicConfig.html schoolboy runaway
Last updated: 2025-07-15

Post by querulouslapis on j1939 ^{CODESYS Forge talk (Post)}
Usa herramientas como MultiTool para definir el dispositivo J1939 y sus propiedades. https://www.codesys.com/the-system/releases-updates-lifecycle/release-plan-roadmap.html melon playground
Last updated: 2025-07-15

Sort by relevance or date