call of a method of a function block in another program ^{CODESYS Forge talk (Thread)}
call of a method of a function block in another program
Last updated: 2024-06-03

Post by onstage on Unable to add EL6751 to Control RTE V3 on W11 IoT LTSC using Eng. V3.5 SP21 ^{CODESYS Forge talk (Post)}
For reference, it was just me being unfamiliar with EtherCAT in CoDeSys. Anyone with knowledge who would have opened the ScanResult screenshot would have identified that the preceding EK1100 was the device missing in the library. Bottom line - Do something else for a while and then get back at it with fresh eyes!
Last updated: 2025-09-08

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 timvh on Communication between applications on same device/controller/runtime (Win RTE 3.5.20.20) ^{CODESYS Forge talk (Post)}
If you have a Windows system (RTE), then why not run the CODESYS HMI as separate controller. This could easily be moved to another PC if required. In the HMI you could also still use the Symbolic Var access as part of the Data Source Manager, although maybe OPC is the preferred way to make it more future proof. Or what about the Remote Target Visu. Then you can reduce the load of the main controller, while still only having to create one application including Visualization. This is now also supported for Linux systems. See: https://content.helpme-codesys.com/en/CODESYS%20Control/_rtsl_target_visu_for_linux.html https://content.helpme-codesys.com/en/CODESYS%20Visualization/_visu_execute_remote_target_visu.html
Last updated: 2024-09-28

Post by cihangur on OpC UA server on Raspberry Pi 64 SL runtime ^{CODESYS Forge talk (Post)}
After my tests, I noticed two issues. 1- WinCC disconnects the connection after receiving the GetEndPointResponse message from CoDeSys. (I found it with UAExpert and Wireshark.) 2- It establishes a connection despite waiting for a while on the network with DNS. As a result of this information: I solved the problem by adding the line "193.193.193.150 t9pac" to the C:\Windows\System32\Drivers\etc\hosts file and making Windows accept messages coming from the IP number 193.193.193.150 as coming from t9pac. (t9pac is the name of my PLC running CoDeSys.) If there is a setting that will allow CoDeSys OPC UA to respond to GetEndPointRequest with its IP address, this problem will not occur.
Last updated: 2024-12-12

Post by sumit on Not able to see input data coming from eip adapter on codesys ^{CODESYS Forge talk (Post)}
dhumphries, I changed the datatype this time from BYTE to USINT (because that's what my adapter is sending: array of uint8_t). The text "New Help String" you saw in previous screenshots is just the description of the input/s (it can be anything). I also looked into the logs (see attached) for that ! sign next to the device, I found that connection is being timeout. I tried some suggestions from online such as increase the RPI but still got connection timeout issue, also by changing the datatype, I still don't see incoming data from the adapter, although its visible on wireshark. thanks,
Last updated: 2024-03-07

Post by gseidel on CAM Motion Recover after STO ^{CODESYS Forge talk (Post)}
Dear Mr. Kolev, I'm not sure I understood correctly. But this is my take on your question: When the STO of the slave is triggered, store the current master position (e.g. 225 units) After the reset of the slave error, call MC_SetPosition on the virtual master and reset it to the stored position (225 units) Optionally, before MC_CamIn is restartet, move the slave back to the slave position corresponding to the stored master position. (If you do this, no ramping in will be necessary) Restart MC_CamIn, with absolute master position and absolute slave position. Choose the StartMode that is appropriate for your machine. Best regards, Georg Seidel
Last updated: 2026-02-16

Raspberry Pi Control SL MC - Restoring License not working anymore! ^{CODESYS Forge talk (Thread)}
Raspberry Pi Control SL MC - Restoring License not working anymore!
Last updated: 2023-08-24

SPI Master not running/MCP3008 Missing driver. ^{CODESYS Forge talk (Thread)}
SPI Master not running/MCP3008 Missing driver.
Last updated: 2023-09-13

Japanese characters are not displayed in webvisu ^{CODESYS Forge talk (Thread)}
Japanese characters are not displayed in webvisu
Last updated: 2021-03-25

CODESYS Control Not Showing Up in Devices ^{CODESYS Forge talk (Thread)}
CODESYS Control Not Showing Up in Devices
Last updated: 2023-01-02

Modbus: dis- / re-connect cable: modbus does not re-start ^{CODESYS Forge talk (Thread)}
Modbus: dis- / re-connect cable: modbus does not re-start
Last updated: 2013-09-28

CoDeSys SP Win V3 - Soft PLC Does not start. ^{CODESYS Forge talk (Thread)}
CoDeSys SP Win V3 - Soft PLC Does not start.
Last updated: 2010-11-17

Visualization "F" Key not Reseting Variable ^{CODESYS Forge talk (Thread)}
Visualization "F" Key not Reseting Variable
Last updated: 2018-01-18

The required device description is not installed.. ^{CODESYS Forge talk (Thread)}
The required device description is not installed..
Last updated: 2023-10-03

USB <-> CAN, CANfox, Component CmpCANFoxDrv NOT loaded ^{CODESYS Forge talk (Thread)}
USB <-> CAN, CANfox, Component CmpCANFoxDrv NOT loaded
Last updated: 2023-10-16

Persistence Manager does not save alphabetically first value ^{CODESYS Forge talk (Thread)}
Persistence Manager does not save alphabetically first value
Last updated: 2023-10-17

Codesys ARTI .XML file not creating but working. ^{CODESYS Forge talk (Thread)}
Codesys ARTI .XML file not creating but working.
Last updated: 2023-10-30

ReceiveWatchdog FB not working on J1939 P2P PGNs ^{CODESYS Forge talk (Thread)}
ReceiveWatchdog FB not working on J1939 P2P PGNs
Last updated: 2024-07-10

Runtime not working on raspberry pi Bullseye ^{CODESYS Forge talk (Thread)}
Runtime not working on raspberry pi Bullseye
Last updated: 2024-07-29

Codesys Control for PLCnext SL, Bus not running ^{CODESYS Forge talk (Thread)}
Codesys Control for PLCnext SL, Bus not running
Last updated: 2024-08-12

Codesys Control for PLCnext SL, Bus not running ^{CODESYS Forge talk (Thread)}
Codesys Control for PLCnext SL, Bus not running
Last updated: 2024-08-12

Persistent variables not working for Control Win ^{CODESYS Forge talk (Thread)}
Persistent variables not working for Control Win
Last updated: 2024-09-10

Visuutils FbOpenDialog(Extended) not open Dialog from POUs ^{CODESYS Forge talk (Thread)}
Visuutils FbOpenDialog(Extended) not open Dialog from POUs
Last updated: 2024-10-08

Error 'Library not found' and 'Unkown type' ^{CODESYS Forge talk (Thread)}
Error 'Library not found' and 'Unkown type'
Last updated: 2024-10-10

Sort by relevance or date