Post by jkessler on IoDrvModbusTCP_Diag not defined when using MODBUS ^{CODESYS Forge talk (Post)}
Hi, Same for me ! Works in Codesys 3.5.19 but not in 3.5.20. I'm currenly using with a WAGO PLC200 [ERREUR] EmPlcProgram: Application [Device: Logique API]: C0046: Identificateur 'IoDrvModbusTCP_Diag' non défini [ERREUR] EmPlcProgram: Application [Device: Logique API]: C0080: Le bloc fonctionnel 'IoDrvModbusTCP' doit être instancié pour permettre l’accès [ERREUR] EmPlcProgram: Application [Device: Logique API]: C0004: 'IoDrvModbusTCP_Diag' n’est pas un composant de 'IoDrvModbusTCP' [ERREUR] EmPlcProgram: Application [Device: Logique API]: C0046: Identificateur 'ModbusTCPSlave_Diag' non défini [ERREUR] EmPlcProgram: Application [Device: Logique API]: C0080: Le bloc fonctionnel 'IoDrvModbusTCP' doit être instancié pour permettre l’accès [ERREUR] EmPlcProgram: Application [Device: Logique API]: C0004: 'ModbusTCPSlave_Diag' n’est pas un composant de 'IoDrvModbusTCP' [ERREUR] EmPlcProgram: Application [Device: Logique API]: C0046: Identificateur 'ModbusTCPSlaveUnit_Diag' non défini [ERREUR] EmPlcProgram: Application [Device: Logique API]: C0080: Le bloc fonctionnel 'IoDrvModbusTCP' doit être instancié pour permettre l’accès [ERREUR] EmPlcProgram: Application [Device: Logique API]: C0004: 'ModbusTCPSlaveUnit_Diag' n’est pas un composant de 'IoDrvModbusTCP' Thanks in advance
Last updated: 2024-05-29

Post by jkessler on IoDrvModbusTCP_Diag not defined when using MODBUS ^{CODESYS Forge talk (Post)}
Hi, Same for me ! Works in Codesys 3.5.19 but not in 3.5.20. I'm currenly using with a WAGO PLC200 [ERREUR] EmPlcProgram: Application [Device: Logique API]: C0046: Identificateur 'IoDrvModbusTCP_Diag' non défini [ERREUR] EmPlcProgram: Application [Device: Logique API]: C0080: Le bloc fonctionnel 'IoDrvModbusTCP' doit être instancié pour permettre l’accès [ERREUR] EmPlcProgram: Application [Device: Logique API]: C0004: 'IoDrvModbusTCP_Diag' n’est pas un composant de 'IoDrvModbusTCP' [ERREUR] EmPlcProgram: Application [Device: Logique API]: C0046: Identificateur 'ModbusTCPSlave_Diag' non défini [ERREUR] EmPlcProgram: Application [Device: Logique API]: C0080: Le bloc fonctionnel 'IoDrvModbusTCP' doit être instancié pour permettre l’accès [ERREUR] EmPlcProgram: Application [Device: Logique API]: C0004: 'ModbusTCPSlave_Diag' n’est pas un composant de 'IoDrvModbusTCP' [ERREUR] EmPlcProgram: Application [Device: Logique API]: C0046: Identificateur 'ModbusTCPSlaveUnit_Diag' non défini [ERREUR] EmPlcProgram: Application [Device: Logique API]: C0080: Le bloc fonctionnel 'IoDrvModbusTCP' doit être instancié pour permettre l’accès [ERREUR] EmPlcProgram: Application [Device: Logique API]: C0004: 'ModbusTCPSlaveUnit_Diag' n’est pas un composant de 'IoDrvModbusTCP' Thanks in advance
Last updated: 2024-05-29

Post by jkessler on IoDrvModbusTCP_Diag not defined when using MODBUS ^{CODESYS Forge talk (Post)}
Hi, Same for me ! Works in Codesys 3.5.19 but not in 3.5.20. I'm currenly using with a WAGO PLC200 [ERREUR] EmPlcProgram: Application [Device: Logique API]: C0046: Identificateur 'IoDrvModbusTCP_Diag' non défini [ERREUR] EmPlcProgram: Application [Device: Logique API]: C0080: Le bloc fonctionnel 'IoDrvModbusTCP' doit être instancié pour permettre l’accès [ERREUR] EmPlcProgram: Application [Device: Logique API]: C0004: 'IoDrvModbusTCP_Diag' n’est pas un composant de 'IoDrvModbusTCP' [ERREUR] EmPlcProgram: Application [Device: Logique API]: C0046: Identificateur 'ModbusTCPSlave_Diag' non défini [ERREUR] EmPlcProgram: Application [Device: Logique API]: C0080: Le bloc fonctionnel 'IoDrvModbusTCP' doit être instancié pour permettre l’accès [ERREUR] EmPlcProgram: Application [Device: Logique API]: C0004: 'ModbusTCPSlave_Diag' n’est pas un composant de 'IoDrvModbusTCP' [ERREUR] EmPlcProgram: Application [Device: Logique API]: C0046: Identificateur 'ModbusTCPSlaveUnit_Diag' non défini [ERREUR] EmPlcProgram: Application [Device: Logique API]: C0080: Le bloc fonctionnel 'IoDrvModbusTCP' doit être instancié pour permettre l’accès [ERREUR] EmPlcProgram: Application [Device: Logique API]: C0004: 'ModbusTCPSlaveUnit_Diag' n’est pas un composant de 'IoDrvModbusTCP' Thanks in advance
Last updated: 2024-05-29

Post by ph0010421 on General question about library versions ^{CODESYS Forge talk (Post)}
Hello I can't find anything to read on the subject so I'll ask here. Up to now, when adding a (for example) Modbus Master, I've selected the version <= the RT version, so if I'm using SP13 Patch 3, I can use a library that doesn't exceed this. I've no idea if this is correct, but it's always worked. Can someone explain the 4.x.x.x libraries that have appeared; are they tied to a RT version? The controller I use is now at SP18Patch60, so should I continue to use 3.5.xxx or change? thanks
Last updated: 2024-05-29

Post by paro on Modbus Client Request Not Processed ^{CODESYS Forge talk (Post)}
Hi, Problem in your code is that you are not calling the ClientFb cyclic. Please look at the Example from CODESYS: https://forge.codesys.com/prj/codesys-example/modbus/home/Home/ Your code works if the client fb is called cyclic! IF NOT initDone THEN initDone := TRUE; // configure clientTcp clientTcp(aIPaddr:=Ethernet.IPAddress, uiPort:=502); // configure clientSerial clientSerial(iPort:=SysCom.SYS_COMPORT2, dwBaudRate:=SysCom.SYS_BR_115200, byDataBits:=8, eParity:=SysCom.SYS_EVENPARITY, eStopBits:=SysCom.SYS_ONESTOPBIT, eRtuAscii:=ModbusFB.RtuAscii.RTU); // configure clientRequestReadCoils_1 clientRequestReadCoils_1(rClient:=clientTcp, uiUnitId:=42, udiTimeout:=TO_UDINT(T#10MS)); // configure clientRequestWriteSingleRegister clientRequestWriteSingleRegister(rClient:=clientTcp, uiUnitId:=43, udiTimeout:=TO_UDINT(T#10MS)); // configure clientRequestReadCoils_2 clientRequestReadCoils_2(rClient:=clientTcp, uiUnitId:=44, udiTimeout:=TO_UDINT(T#10MS)); // configure clientRequestReadInputRegisters clientRequestReadInputRegisters(rClient:=clientTcp, uiUnitId:=44, udiTimeout:=TO_UDINT(T#10MS)); END_IF // call the client FB's clientTcp(); clientSerial(); // call client request FB's clientRequestReadCoils_1(rClient:=clientTcp, xExecute:=TRUE, uiStartItem:=2, uiQuantity:=3, pData:=ADR(aDataCoils_1[0])); // for more details see Example_TCP, especially ClientRequest control (xExecute, xDone, xError). IF clientRequestReadCoils_1.xDone THEN // get data from aDataCoils_1 ... END_IF clientRequestWriteSingleRegister(rClient:=clientTcp, xExecute:=TRUE, uiItem:=3, uiValue:=123); clientRequestReadCoils_2(rClient:=clientTcp, xExecute:=TRUE, uiStartItem:=2, uiQuantity:=3, pData:=ADR(aDataCoils_2[0])); clientRequestReadInputRegisters(rClient:=clientTcp, xExecute:=TRUE, uiStartItem:=16, uiQuantity:=3, pData:=ADR(aDataInputRegisters[0]));
Last updated: 2024-05-29

Post by paro on Non-existing identifiers ^{CODESYS Forge talk (Post)}
Hi, which CODESYS IDE version are you using? I think it's fixed in >= SP19 patch 7, maybe also in SP19 patch 6, but I'm not sure.
Last updated: 2024-05-29

General question about library versions ^{CODESYS Forge talk (Thread)}
General question about library versions
Last updated: 2024-05-29

Post by zer0g on Modbus Client Request Not Processed ^{CODESYS Forge talk (Post)}
Hi, I have the same problem as the guys above. Any solution or hint in the right direction is appreciated. Codesys version 3.5.19.2, Lib version: 4.4.0.0. Thank you!
Last updated: 2024-05-29

Post by paro on General question about library versions ^{CODESYS Forge talk (Post)}
I think you can use the newer versions. For a explanation from CODESYS, please read this post: https://www.codesys.com/the-system/versions-modularization.html
Last updated: 2024-05-29

Post by paro on "You are using inconsistent overlay settings, please check your compiler defines for the current application" error ^{CODESYS Forge talk (Post)}
Disable the setting "Support client animations and overlay of native elements" in the Visu Manager. Activating this setting should also set a compiler define (GENERATE_OVERLAY_VISU). Maybe the compiler define is set and the feature is not activated in the visu manager or or the other way round.. rightclick the Application -> Properties -> Build https://content.helpme-codesys.com/en/CODESYS%20Development%20System/_cds_dlg_properties_build.html
Last updated: 2024-05-29

"You are using inconsistent overlay settings, please check your compiler defines for the current application" error ^{CODESYS Forge talk (Thread)}
"You are using inconsistent overlay settings, please check your compiler defines for the current application" error
Last updated: 2024-05-29

Post by paro on send appliaction files to wago plc (codesys 3.5) via ssh ^{CODESYS Forge talk (Post)}
Hi, it is enough to copy the files to /home/codesys/PlcLogic/Application and adding the lines [CmpApp] Application.1=Application to the eRUNTIME.cfg, if your Application in your program is also called "Application". Reboot -> Bootapp should be loaded. If not please check the log /var/log/runtime.log There should be a line which explains why the bootproject is not loaded.
Last updated: 2024-05-29

Library error after creating project from python ^{CODESYS Forge talk (Thread)}
Library error after creating project from python
Last updated: 2024-05-29

Codesys HMI Redundancy ^{CODESYS Forge talk (Thread)}
Codesys HMI Redundancy
Last updated: 2024-05-30

Post by arrotek on Codesys HMI Redundancy ^{CODESYS Forge talk (Post)}
Is there a way to run Codesys HMI on two different PC's and have the web visu clients fail over to the HMI instance that is wokring or running?
Last updated: 2024-05-30

Post by paro on Modbus Client Request Not Processed ^{CODESYS Forge talk (Post)}
Hi, works in my case if I increase the timeout! to_udint(t#100ms) -> 100 -> 100us.. FUNCTION_BLOCK MODBUS_master_example_ST VAR initDone : BOOL := FALSE; aIPAddress : ARRAY [0..3] OF BYTE := [127,0,0,1]; clientTcp: ModbusFB.ClientTcp; // buffer to read input registers aDataInputRegisters : ARRAY[0..9] OF UINT; // some client requests clientRequestReadInputRegisters: ModbusFB.ClientRequestReadInputRegisters; xExecute: BOOL; uistart: UINT := 100; udiTimeout1: UDINT; END_VAR IF NOT initDone THEN initDone := TRUE; // configure clientTcp clientTcp(aIPaddr:=aIPAddress, uiPort:=502, udiLogOptions := ModbusFB.LoggingOptions.All); // configure clientRequestReadInputRegisters clientRequestReadInputRegisters(rClient:=clientTcp, uiUnitId:=1, udiTimeout:=1000000); // 1sec END_IF // call the client FB's clientTcp(); clientRequestReadInputRegisters(rClient:=clientTcp,xExecute := xExecute AND NOT clientRequestReadInputRegisters.xBusy ,uiStartItem:=uistart, uiQuantity:=3, pData:=ADR(aDataInputRegisters[0]));
Last updated: 2024-05-30

send appliaction files to wago plc (codesys 3.5) via ssh ^{CODESYS Forge talk (Thread)}
send appliaction files to wago plc (codesys 3.5) via ssh
Last updated: 2024-05-30

Non-existing identifiers ^{CODESYS Forge talk (Thread)}
Non-existing identifiers
Last updated: 2024-05-30

Post by zer0g on Modbus Client Request Not Processed ^{CODESYS Forge talk (Post)}
I'm using the code bellow which is based on the Codesys example: FUNCTION_BLOCK MODBUS_master_example_ST VAR initDone : BOOL := FALSE; aIPAddress : ARRAY [0..3] OF BYTE := [127,0,0,1]; clientTcp: ModbusFB.ClientTcp; // buffer to read input registers aDataInputRegisters : ARRAY[0..9] OF UINT; // some client requests clientRequestReadInputRegisters: ModbusFB.ClientRequestReadInputRegisters; xExecute: BOOL; END_VAR IF NOT initDone THEN initDone := TRUE; // configure clientTcp clientTcp(aIPaddr:=aIPAddress, uiPort:=502, udiLogOptions := ModbusFB.LoggingOptions.All); // configure clientRequestReadInputRegisters clientRequestReadInputRegisters(rClient:=clientTcp, uiUnitId:=1, udiTimeout:=TO_UDINT(T#1000MS)); END_IF // call the client FB's clientTcp(); clientRequestReadInputRegisters(rClient:=clientTcp,xExecute := xExecute AND NOT clientRequestReadInputRegisters.xBusy ,uiStartItem:=2, uiQuantity:=3, pData:=ADR(aDataInputRegisters[0])); As you can see the clientTCP is called cyclically with the same result.
Last updated: 2024-05-30

Post by jaspergain on Non-existing identifiers ^{CODESYS Forge talk (Post)}
Hi, I'm using SP19 Patch 5, the software is also updated from SP18 Patch 5, I forgot to mention this. I will try a newer patch to see if it fixes the issue. Thanks for your help.
Last updated: 2024-05-30

Post by sigurdrb on send appliaction files to wago plc (codesys 3.5) via ssh ^{CODESYS Forge talk (Post)}
Okey, I will try this out. Thank you for your answer!
Last updated: 2024-05-30

Post by bartg on Open a POU in the editor via scripting ^{CODESYS Forge talk (Post)}
Hi, I would like to automate opening some specific pous and visualisations in the codesys environment I found out that I can open it by using : system.commands["42f6acb9-bd6e-42e7-94bb-6e2a03973b83"].execute() But the POU has to be selected in the Devices or POUs navigator. Does anyone know how I can select a specific POU in the navigator? Or how I can open a specific POU? I can retreive the guid of the POU. Thx
Last updated: 2024-05-30

Post by zer0g on Modbus Client Request Not Processed ^{CODESYS Forge talk (Post)}
Hi, Thank you for your suggestion but the problem is fixed after I disabled and enabled the network adapter from Windows settings.
Last updated: 2024-05-30

Modbus Client Request Not Processed ^{CODESYS Forge talk (Thread)}
Modbus Client Request Not Processed
Last updated: 2024-05-30

Open a POU in the editor via scripting ^{CODESYS Forge talk (Thread)}
Open a POU in the editor via scripting
Last updated: 2024-05-30

Sort by relevance or date