CODESYS Forge - CODESYS Forge / Talk / Search

<< < 1 .. 853 854 855 856 857 .. 888 > >> (Page 855 of 888)

Post by damian177 on CM4S GPIO's in Codesys ^{CODESYS Forge} ^talk ^(Post)
Hi, I am running my application on device based on Compute Module 4S (Cortex-A72 (ARMv8) 64-bit ). On this device I installed RPi Runtime in 4.11.0.0 version. In my project I use device: Codesys Control for Raspberry Pi 64SL and my project works, but I actually do not have acces to all GPIO's , because GPIOs Compute Module is available only in 3.5.16.0 version and it doesn't work. Properly work GPIOs B+/Pi2 but using this device I do not have acces to all GPIO's in CM4S. Anyone of can tell me how add GPIOs Compute Module 4.11.0.0 to my project ?
Last updated: 2024-05-28

Post by sigurdrb on send appliaction files to wago plc (codesys 3.5) via ssh ^{CODESYS Forge} ^talk ^(Post)
Hi, I was hoping I could send the two files "application.app" and "application.crc" directly to the directory "/home/codesys/PlcLogic/Application" instead of logging into the device with codesys, downloading the program to the controller and then do the "create boot application", so it will reboot with the correct program running. I think i also need to edit the file "eRUNTIME.cfg" located in the "/home/codesys/ folder, because when I create the boot application from the codesys IDE, these lines are added to the file: [CmpApp] Application.1 = Application [SysFileMap] /home/codesys/PlcLogic/Application/Application.app=0x212520, 0x2DBC747E, 2DBC747E.app I think the "eRUNTIME.cfg" file is the same as CODESYSControl.cfg I also dont know the purpose of the hexadecimal numbers etc. that is generated. When I tried to replicate what codesys was doing, I placed the same files in the same folder as when codesys generated the boot file. And also added the lines in the eRUNTIME.cfg file: [CmpApp] Application.1 = Application [SysFileMap] /home/codesys/PlcLogic/Application/Application.app The controller did not boot up with any program, so my method did not work at all. I guess these lines tells the controller to run an application and where to find it? Could any of you help me with the best way to get the compiled program to the controller without using codesys or wago-software?
Last updated: 2024-05-28

Post by plunje on Sensor not set ^{CODESYS Forge} ^talk ^(Post)
Thanks a lot!
Last updated: 2024-05-28

Sensor not set ^{CODESYS Forge} ^talk ^(Thread)
Sensor not set
Last updated: 2024-05-28

Post by jaspergain on Non-existing identifiers ^{CODESYS Forge} ^talk ^(Post)
Hello, I got a bit of a weird issue going on which is kind of annoying. So recently we switched a lot of Modbus IO to EtherCAT, as we were having issues with stability. All works fine, which is great. But sometimes when I change the program I get errors claiming that identifiers are not defined. Meaning I can't go online. See the picture below. I believe this is because some of these identifiers were used with Modbus, and they weren't properly removed/deleted? A clean all temporary fixes the issue, but it comes back again after a while of changing the code, and building. Any way to fix these non-existing required identifiers, or even find out where they are required? Thanks for the help in advance. Jasper.
Last updated: 2024-05-29

Post by dkugler on Nema 17 Schrittmotor 2.7V kann das sein? ^{CODESYS Forge} ^talk ^(Post)
Ein Schrittmotor muss immer an einem entsprechenden Schrittmotor-Treiber/Kontroller betrieben werden. Mit welcher Spannung dieser Treiber versorgt wird(üblich von 5V bis zu 70/80V DC und mehr) und bei welcher Strangspannung der Nennstrom durch die Motorwicklung fließt, ist ein himmelweiter Unterschied. Genau das ist u.a. die Aufgabe des Treibers, die Spannung so zu regeln, dass die Motorwicklungen von dem aktuell notwendigen Strom durchflossen werden. Siehe https://de.wikipedia.org/wiki/Schrittmotor Stichwort Chopperbetrieb.
Last updated: 2024-05-28

Nema 17 Schrittmotor 2.7V kann das sein? ^{CODESYS Forge} ^talk ^(Thread)
Nema 17 Schrittmotor 2.7V kann das sein?
Last updated: 2024-05-28

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

IoDrvModbusTCP_Diag not defined when using MODBUS ^{CODESYS Forge} ^talk ^(Thread)
IoDrvModbusTCP_Diag not defined when using MODBUS
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

<< < 1 .. 853 854 855 856 857 .. 888 > >> (Page 855 of 888)

Sort by relevance or date

Forums

Help

Search talk: -128到127是什么数据类型

Forums

Help

Search talk: -128到127是什么数据类型

Searching