Post by kalmeyer on Stepper motor control with (SM_Drive_RaspStepper_direct) ^{CODESYS Forge talk (Post)}
Hi Helpers I'm trying to work with stepper motor on Rasp 5 for the first time. So I'm pretty new.😥here. I've used: https://forge.codesys.com/drv/sm3raspistepper/home/Home/ but I get the following error when I insert. I also get 6 errors when I "rebuilder" after installering "SM_Drive_RaspStepper_direct" from the tree. Hope there is help for me. Thanks in advance /Klaus
Last updated: 2025-11-04

Post by hinet on 22kW Wallbox mit Modbus ^{CODESYS Forge talk (Post)}
Hallo an alle, ich schaue mir gerade ein paar 22kW Wallboxen an: https://shop.einfacheauto.de/collections/22-kw-wallboxen Mir wäre vor allem wichtig, dass die Kommunikation per Modbus gut funktioniert. Es werden zwar ein paar Wallboxen gelistet, die Modbus ermöglichen, trotzdem wollte ich euch nach Erfahrungen fragen, welche Modelle in der Hinsicht besonders problemfrei funktionieren.
Last updated: 2025-11-06

Post by egret on Issue with J1939, PGN 65267 (Vehicle Position) ^{CODESYS Forge talk (Post)}
I have a J1939 network (ISOBUS) connected to my PLC. I can receive various PGNs such as 65256 (Vehicle Direction/Speed) and 65254 (Time/Date). However, I cannot receive 65267 (Vehicle Position). PGN 65267 (VP) contains SPN 584 (Latitude) and SPN 585 (Longitude). On the network both SPNs return a value of -210 (meaning the CAN message payload is zero in both cases). The conversion settings are the default values and appear to be correct (see attached screenshot). Using a CAN analyser I can see that PGN 65267 (Vehicle Position) is being transmitted over the network with valid (non-zero) data that matches the latitude and longitude coordinates I would expect. I've created a program to read the raw J1939 data and this also returns valid data. It seems that the Codesys J1939 database has a problem with reading PGN 65267 messages. Can anybody else confirm this? I'm using Codesys Version 3.5 SP16 Patch 5.
Last updated: 2023-09-13

Post by damian177 on Codesys and SMS in RPi ^{CODESYS Forge talk (Post)}
I tried initialize my GSM modem by write simple application in C, and GSM modem works, below used AT commands: AtChat: T : "AT" AtChat: F : "OK" AtChat: T : "AT+CMEE=1" AtChat: F : "OK" AtChat: T : "AT+CMGF=0" AtChat: F : "OK" AtChat: T : "AT+CGMI" AtChat: F : "WH_Ltd" AtChat: F : "WH_GM35" AtChat: F : "Revision: RDA BV5" AtChat: F : "OK" AtChat: T : "AT+CGMM" AtChat: F : "WH_GM35" AtChat: F : "OK" AtChat: T : "AT+CGMR" AtChat: F : "Revision: GM35-D_B5_R05_A01_D170914" AtChat: F : "OK" AtChat: T : "AT+CGSN" AtChat: F : "868221045990218" AtChat: F : "OK" AtChat: T : "AT+CNMI=2,1,0,1,0" AtChat: F : "OK" AtChat: T : "AT+CLIP=1" AtChat: F : "OK" AtChat: T : "AT+COPS?" AtChat: F : "+COPS: 0,2,\"26002\"" AtChat: F : "OK" operator name: "26002" AtChat: T : "AT+CREG?" AtChat: F : "+CREG: 1,1" AtChat: F : "OK" at+creg Modem is initialized I do not understand why Codesys SMS library send AT+CPIN? command ?
Last updated: 2023-09-29

Post by captaincookie on increase default string length in queue ^{CODESYS Forge talk (Post)}
Hello, I'm using Codesys V3.5 SP18 Patch 4. In the ElementCollectionExample Project from Codesys, I test the SimpleQueueExample in a Control Win V3 x64 environment. I try to add a string of 95 characters length to a queue. The default length of strings is defined as 80 characters. In the initialization of a string variable, it is possible to increase the length by the definition of e.g. STRING(1000). But when I write the string defined like this to the queue, only 80 characters are written to it and the rest is missing. I think the default length is still set in the queue definition, so it is necessary to change this, isn't it? Is there any option to increase the default length of strings in the queue? Attached you can find the used project. Thanks in advance. If any information are missing or my description unclear please let me know.
Last updated: 2023-10-05

Post by annd on Migration von "CODESYS Control for PFC200 SL" zu WAGO FW26 "CODESYS V3.5.19.2" ^{CODESYS Forge talk (Post)}
Ich hab's hinbekommen: Nach dem Controller Update hab ich ein neues Projekt gemacht und nur den PFC200(8212) eingefügt (es erscheint dann ein leerer Kbus und eine serielle Schnittstelle COM1). Dann hab ich mich am Controller eingeloggt und den Kbus (Rechtsklick: Geräte suchen) mit allen Modulen automatisch ergänzen lassen. Bei den leeren Modulen hab ich dann das E/A-Abbild in csv exportiert. Dasselbe hab ich bei meinem alten "PFC200 SL" Projekt gemacht. Und dann in Excel alle Variablennamen in die leeren csv kopiert und danach wieder im neuen Projekt importiert. Dann hab ich noch alle Programmblöcke, Tasks, Visualisierungen und auch Modbus TCP Master u. Slave und auch Modbus COM Port Master und Slave in das neue Projekt kopiert. Weiters hab ich alle notwendigen Bibliotheken im Bibliotheksverwalter eingefügt. Dann noch ein paar kleine Fehler korrigiert (ich musst einen anderen Block zum Lesen der Uhrzeit nehmen) bis ich das neue Projekt fehlerfrei übersetzen konnte. Dann konnte ich es auf den Wago Controller übertragen und direkt starten. Es sieht so aus, dass alles läuft. Gruß annD
Last updated: 2023-11-18

Post by mikek10 on Ethernet/IP 4.6.0 causing exceptions? ^{CODESYS Forge talk (Post)}
Hi, I have a project currently in development, it has a number of Ethernet/IP devices (18 adapter devices with Codesys as scanner, another scanner device with codesys as adapter). This has been stable whilst on factory floor for several months (though prior to that I did have some Ethernet/IP issues which were resolved by adjusting RPI rates). Today I tried updating to Ethernet /IP 4.6.0 from 4.5.1, subsequent to this I had 2 exceptions in a 2 hour period, I reverted to 4.5.1 and have had no further exceptions. Note I do have a device (Zebra printer) that frequently times out and reconnects, this does not seem to cause any issues in operation and does not cause any exceptions with 4.5.1. I believe the root cause of this is on the Zebra side, however there does not seem to be any adjustment I can make to prevent the time outs. Information from device log is in screenshot attached.
Last updated: 2024-06-27

Post by abinvest579 on TCP Client ^{CODESYS Forge talk (Post)}
Hi All, I am using codesys based plc to read and control magna power DC supply over LXI protocol using SCPI command. To connect device required socket programming for that i am using Net base service library function block TCP_Client to establish connection over TCP/IP , TCP_Write to write SCPI commands and TCP_Read to read data from Magna power DC supply. I have attached screenshot for logic developed. I am able to connect and write commands to device but i not receiving any information from device. For writing Commands i also tried various end of line character like \n,<nl>, A, D, 10, 13, 0x0A, 0x0D but not received any status from device. For testing purpose i am using simple command '*IDN?' to read data. Also if tried to check on hercules software what data actually plc read, first it read correct data after that is read wrong data as see in screen shot. 'Hello World' was correct read and after that Codesys in replaced with 'Codesysorld' that is not correct way. Same issue also appeared for send data. Any one have face same issue how i can read data directly from device correctly and send data please suggest solution on this.</nl>
Last updated: 2024-07-01

Post by climblinne on Calling OPC UA Methods from UaExpert ^{CODESYS Forge talk (Post)}
Hello, I hope someone could help me. I installed the newest Codesys 3.5 SP 20 Patch 1. When loading the demo files from @i-campbell I can upgrade them to the latest version and everthing works on the OPC-UA client side as expected (object "a" is visible, I can use the "ExampleMethod"). Now I * remove the "Information Model", * delete the "OPC_UA_Symbols Objects", * Add "Information Model" again * add "TestRootObjectType" again and "Generate IEC declarations" * and search for mapped instances (to get instance "a" again) Very good still working as expected. Now I delete the OPC_UA_Symbols and add it again referring to the "objecttest" from 16.9.2020. Also I redo the steps from above. The result is now, that I can't see the "a" object in the "Root/Objects" folder. Why ist this and how can I make it running? I think, it could may be a different version of the UA configuration file. I tried to build my own model definition files and got the same problem (but I am really not an expert). When someone has a actual model, which is also running in the actual Codesys I would be very grateful. Or even better, how to make the correct model in e.g. UA Modeler SW (I followed the description https://documentation.unified-automation.com/uamodeler/1.6.0/html/howprojnet_sec.html).
Last updated: 2024-07-01

Post by psychoengineer on Cannot Save CSV File on Windows Computer Using CODESYS and Control Win ^{CODESYS Forge talk (Post)}
I am currently working on a project using CODESYS and Control Win on a Windows computer. I've encountered an issue where I am unable to save a CSV file. I have followed the standard procedures and used the appropriate file handling functions, but the file is not being created or saved as expected. IF xStartTest THEN sFileName := '\logs.txt'; sFileName := CONCAT(gvl.g_sMainDirectory, sFileName); sFileNameCopy := '\CAAFileCopy.txt'; sFileNameCopy := CONCAT(gvl.g_sMainDirectory, sFileNameCopy); //eWriteState := FILE_OPEN_TRIGGER; xTestDone := FALSE; xError := FALSE; xStartTest := FALSE; END_IF VAR_GLOBAL g_sMainDirectory : STRING := 'C:\LogFiles'; // file path for CSV file END_VAR Despite this, the file does not appear in the specified directory, and no error messages are being generated. I've checked the directory permissions and ensured that the path is correct. Has anyone else experienced a similar issue or have any suggestions on how to resolve this? Any help would be greatly appreciated. Thank you!
Last updated: 2024-07-04

Post by to-ke on Errors with VisuUserManagement library ^{CODESYS Forge talk (Post)}
Hallo zusammen, hi all, ich habe den gleichen Fehler. Auf einem Raspberry Pi geht der Fehler weg, wenn ich alles bereinige und dann vollständig übersetze. Wenn das Projekt im Codesys Development System wieder neu geladen wird ist der Fehler aber wieder da. Mit eine Win V3 x64 PLC kann ich den Fehler nur unterbinden wenn ich auf der HMI das VUM_Login einbinde. Dieses brauche ich aber nicht, da ich die HMI für das User Management selbst gestaltet habe. Das funktioniert auch. I have the same error. On a Raspberry Pi the error goes away if I clean everything and then compile completely. When the project is reloaded in the Codesys Development System, the error returns. With a Win V3 x64 PLC I can only prevent the error if I integrate the VUM_Login on the HMI. But I don't need this because I designed the HMI for user management myself. That works too. Anyone have an idea to fix this problem. Many thanks
Last updated: 2024-07-09

Post by tyronnosaurus on ReceiveWatchdog FB not working on J1939 P2P PGNs ^{CODESYS Forge talk (Post)}
Hi guys. I've got a device that sends a status message over J1939 and a PLC running Codesys to receive it. This message uses a P2P PGN (as opposed to a broadcast PGN). Codesys can only read it if I mark the J1939_ECU as "Local" (see screenshot 1). The message is received correctly, that is not the problem. The problem is detecting if the message stops being received. Local ECUs have no Watchdog checkbox to detect if the message has been received in the last X seconds. In order to implement a watchdog, I've used a ReceiveWatchdog FB. The same code works well for any non-P2P message, but doesn't work for this particular P2P message I'm trying to monitor. Even if I physically disconnect the device, ReceiveWatchdog.xBusy stays True, and ReceiveWatchdog.xError never triggers due to a timeout error. Is there any caveat in the ReceiveWatchdog FB that makes it unable to monitor P2P PGNs in Local J1939_ECUs?
Last updated: 2024-07-11

Post by faceplant on CmpDynamicText unresolved references ^{CODESYS Forge talk (Post)}
Hello! I am new to codesys so I am sorry if this is not the right place to ask this question. I am using codesys V3.5 SP20 Patch 1 + (64-bit) and a Groov EPIC PLC (GRV-EPIC-PR2). I am trying to build and deploy my application to the PLC, but when I log in I get 6 errors (codesys_error.png). It seems that the errors have to do with the CmpDynamicText system library which I have as version 3.5.20.0. I have tried to add CmpDynamicText to the ComponentManager section in the PLC's CODESYSControl.cfg file as described in this forum post and still hit the same error. I noticed that the library is grayed out in the library manager, which I think might be the issue. However I don't remember if it was grayed out before I encountered this issue. Please let me know if I can provide anymore info. Thank you!!!
Last updated: 2024-07-19

Post by biiebs on Aufbau von Ablaufsteuerungen ermitteln ^{CODESYS Forge talk (Post)}
Hallo Zusammen, gibt es in CODESYS bei Ablaufsteuerungen weitere Möglichkeiten außer den AS-Einstellungen z.B. die Aufbaustruktur der Ablaufsteuerung herauszufinden? Gesamtanzahl der verwendeten Aktionen / Schritte - Im besten Fall auch die einzelnen Verzweigungen? Ich würde den gesamten Aufbau der Schrittkette gerne als "View" in einer übergeordneten Software abbilden lassen, da sich die Ablaufsteuerungen, je nach Projekt im Aufbau unterscheiden bräuchte ich die Kenntniss über den Aufbau dieser Schrittketten. Oder müsste ich mir hier einen "Workaround" programmieren, der z.B. bei Init erstmal den Aufbau der Ablaufsteuerung durchläuft und mir die nötigen Informationen liefert? Natürlich wäre auch ein Weg den Aufbau des AS-Bausteins über die PLCopen XML zu exportieren, jedoch müsste dies bei Änderungen jeweils nachgezogen werden - was etwas unschön wäre, falls dies vergessen würde. Mittlerweile habe ich auch das Tool "SFC Visu Generator" gefunden, dessen Funktion im Prinzip genau das darstellt, was ich benötige - jedoch leider nur als CODESYS interne Visualisierung. Ich würde den Export des Bausteins gerne in meine übergeordnete Software implementieren. Gibt es hier die Möglichkeit das Vorgehen zu Erfahren oder den vom Baustein generierten Export bei mir zu implementieren? Hat hier jemand sowas ähnliches schonmal gelöst? Vielen Dank im Voraus Mit freundlichen Grüßen Biiebs
Last updated: 2024-07-25

Post by kleeswi on Visualization scaling problem with B&R T30 panel ^{CODESYS Forge talk (Post)}
The probelm arises for the B&R T30 panel after updating Codesys from 3.5.17 to 3.5.19 patch 5. We have to use 3.5.19 for other reasons so we cannot downgrade the version. The scaling problem only exists for the B&R 6PPT30.0702.20F025 panel, the B&R T50 panel and a esa lumia panel work. When we choose a fixed resolution it looks also good, however we also want to support the esa lumia panel with a different resolution. The images show the anisotropic and isotropic option. In the anisotropic option it scales the hight correctly but not the width and in the isotropic option is scales both hight and width false, it also does not start in the top left corner. Does someone have any suggestion why it does not work anymore with the new codesys version and are there workarounds? I added all versions with visualization packages as an image, visuElems is 4.4.0.0.
Last updated: 2024-07-29

Post by programmierer on Implementing UDP Communication ^{CODESYS Forge talk (Post)}
Hello everyone, I hope you can help me with my problem. I am new to programming and am currently working with a WAGO controller in our lab, which controls a heat pump. My goal is to send the electrical power of the heat pump (Pel_WP) via a UDP connection to a specific IP address. I am using Codesys version 2.3 and following the guide I found here: https://forge.codesys.com/forum/de/396/genmed-Konfiguration%20der%20UDP%20Kommunikation%20Cosesys%20S7.pdf. I have adapted the guide to suit my needs. The data sending works since I can force the reception value Pel_WP and the data is sent accordingly. However, I am having trouble with the receiving part. The reception value is not being correctly received, and the diSocket variable shows -1. The connection between the heat pump and the WAGO controller seems to be set up correctly, as the heat pump is listed under the communication parameters with the correct IP address. I have also attached images to provide a better view of the setup. I would greatly appreciate any support or suggestions for a solution. Thank you in advance!
Last updated: 2024-08-02

Post by paulorb on STRUCT AT %MW1000 ^{CODESYS Forge talk (Post)}
Hi I am trying to use STRUCT to parse commands from Modbus/TCP, Modbus client will fill the bytes related to a specific command (type, parameters), then PLC (Codesys) will access the command parameters. A STRUCT will simplify a lot the process of parsing the data, so I don't need to parse byte per byte, address will be mapped to a struct and I can use it for parsing the data. From what I understood, the compiler does not allow me to specify the location of the struct for a %MW register. VAR_COMMAND AT %MW1002: structGenericModbusCommand; This will throw: Bad declaration, use '%ML' for 'structGenericModbusCommand' variable But If I change it to %ML, when you go online you see that it is actually allocating the struct in another memory address. When we go online, on GVL we can see: VAR_COMMAND. structGenericModbusCommand %ML1002 commandType COMMANDTYPE %MB8016 ... %MB8020 I am not specifying a pointer or a reference it is a struct type, why is it mapping to a %MW location (random one). How can I control where it is mapping to? I need a consistent way to map STRUCT to specific modbus address. Is it possible? Thanks, Paulo Note I am using a Codesys OEM: Schneider Machine Expert Logic Builder (M241)
Last updated: 2024-08-13

Post by ricola on ERROR: CodeMAccess2: Used CmRuntime 2.61.2705.500 is too old ^{CODESYS Forge talk (Post)}
hi there , can someone tell me how to deal with this error , please? I use the Linux ARM64SL (4.11) on a bullseye distro and when I want to update or install some package, I have the following reply : pi@NanoPi-R5C:~$ sudo apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: ** codesyscontrol : Depends: codemeter but it is not installable or codemeter-lite but it is not installable** E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). and if I try apt --fix-broken install as suggested, I have a proposal to uninstall codesyscontrol ... :-D so I tried to search if there is some Codesys repo: nothing, then I tried to see if ther was something inside Codesys dev (V3.5.20) and I only found that by reading/requesting my device, i spoted that codemeter was too old . I don't see how to deal with this issue. is there a codemeter.deb somewhere ? thanks in advance for any help.
Last updated: 2024-09-17

Post by s1ack on Request a dark mode for CODESYS ^{CODESYS Forge talk (Post)}
and other colors have to be licensed? Introducing Code-Based Licensing Code Basic S: White text w/ grey background (ST only) Code Basic M: White text w/ dark gray background (ST Only) Code Basic L: White test w/ black background (ST Only) Code Standard S: 2 Colors of light syntax highlight colors w/ black background. (ST Only) Code Standard M: 4 Colors of light syntax highlight colors w/ black background. (ST only) Code Standard L: 6 Colors of light syntax highlight colors w/ black background. (ST only) Code Performance S: 2 Colors of light syntax highlight colors w/ user definable background. (Entire IDE) Code Performance M: 4 Colors of light syntax highlight colors w/ user definable background. (Entire IDE) Code Performance L: 6 Colors of light syntax highlight colors w/ user definable background. (Entire IDE) You get the gist... I used to be a big fan of CoDeSys. Recent re-entry after 5 years away, not so much.
Last updated: 2024-11-15

Post by dom4u on Using PEAK CAN PCIe card (IPEH-004040) with Codesys Control RTE V3 ^{CODESYS Forge talk (Post)}
Some findings on this issue: PEAK CAN Driver is the same as in every PCI card from PEAK. I updated the inf file. Here are my steps: 1. Include right VendorID into the *.inf file 2. Disable Windows driver check (Disable WHQL check). This you need because 3S driver is not certified. You will find steps via google or ask chatgpt :) 3. Select: Select driver from a list and navigate to the folder. Say yes to install an uncertified driver. 4. Driver installed and device without errors I did the same with CAN Card from ESD, but here you dont need to include the vendor ID. In ANY CASE it was not successful. The RTIOwdmgeneric is not available in Codesys or anyhow accassable :( I wonder that it fails in two cases, two suppliers, two driver in the same way. How can RTIOwdmgeneric implemented into the project?
Last updated: 2024-12-20

Post by andrax on Bosch BME 280 bzw 688 Sensor per I2C Bus steuern und Daten in Codesys verarbeiten ^{CODESYS Forge talk (Post)}
Die Geräte Bibliothek von Stefan Dreyer ist dafür gedacht, um Treiber für deine Sensoren zu erstellen, damit sie an einem MUX-Board betrieben werden können. Auch ist ein Betrieb ohne MUX-Board möglich. Der Aufbau ist relativ einfach und besteht aus folgenden Komponenten: -Initialize (hier wird die .devdesc.xml eingelesen) -BeforeWriteOutputs (ruft initDevice auf und ist für ausgehende Signale gedacht) -initDevice (initialisiert den Sensor) -AfterReadInputs (Selbsterklärend, Werte einlesen und Signalkonversation) Bei meinen Sensoren habe ich es immer so gemacht. Zuerst habe ich mit die .devdesc.xml gebaut bzw. eine Vorlage umgeschrieben, wobei Parameter 1-10 für ein Mux-Board reserviert sind. In der .devdesc.xml definierst du alle wichtigen Parameter für den Sensor. Danach schreibst du die Initialize und liest die Werte ein. InitDevice ist Fleißarbeit. Für die meisten Sensoren liegt immer ein Pythonscript oder was in C bei. Du gehst die Scripte durch und baust es in Codesys nach. Im letzten Schritt baust du die AfterReadInputs. Signale einlesen und Conversation. Du solltest dir auch ein I2C-Logic Analyzer zulegen. Da Teil ist sehr hilfreich um die I2C Kommunikation mitzulesen. Wenn es irgendwo klemmt, siehst du sofort an welcher Stelle du suchen musst. Ich hab hier den AZ-Delivery Logic Analyzer! Grüße Andre
Last updated: 2025-01-11

Post by mattplc on OPC UA Codesys 3.5 Symbolkonfiguration VS Kommunikationsverwalter und Python/UA-Expert ^{CODESYS Forge talk (Post)}
Hallo, bisher war die Benutzung der Symbolkonfiguration für die OPC-UA Variablen recht easy einsetzbar. Im UAExpert Tool konnte man im Klarnamen den String sehen. var1 = client.get_node("ns=4;s=|var|WAGO 750-8212 PFC200 G2 2ETH RS.Application.PLC_PRG.fbTest.StateActual") Die Anbindung an die Python opcua Library hat so eigentlich gut funktioniert. Auch zum debuggen im UAExptert, konnte man den Value so sehen wie die Varibale heißt. In meinem Fall ein Enum. Was seit längerer Zeit nicht mehr funktionier ist das eingeben von Enums. Im UAExpert kommt die Fehlermeldung "BadTypeMismatch" früher war das nicht der Fall. Da die Symbolkonfiguration demnächst bei Codesys 3.5 rausfällt, wollte ich den Kommunikationsverwalter nutzen. Jetzt schaut der String mit der Node ID komplett anders aus. Bsp.: NS5|Opaque|0x01000000A6E12A718AF7333ABAFA2D7686EF27669CF33071C7D034759DE601779DF62178E9 Hier sieht man den Value gar nicht mehr im UA Expert. In Python finde ich auch keine Möglichkeit die OPC UA Variable einzulesen. Python: var1 = client.get_node("ns=5;s=|var|0x01000000A6E12A718AF7333ABAFA2D7686EF27669CF33071C7F016759BDC7114.PLC_PRG.fbTest.sVar_1") Weiß jemand wir das in Zukunft läuft? ich hab etwas das Gefühl, das die Übergeordneten Systeme die OPC UA Variablen nicht mehr so einfach einlesen können oder mache ich etwas falsch? Danke
Last updated: 2025-01-14

Post by mubeta on Profibus DP master with EL6731 and automatic restart of slaves ^{CODESYS Forge talk (Post)}
WHEREAS, I have already searched various posts and forums, where mostly there are few references and mostly geared toward integration in TwinCAT. I am looking for how to properly configure the EL6731 board as a DP master, (where I have its 3S license), with CoDeSys 3.5.19.x. I have three types of slaves, all integrated with their GSD descriptors. In the tab for the various slaves, I don't see options related to node restart on 'station return'. On the card manual, I read that for each slave I should be able to configure parameter 8000:2C: “8000:2C Restart behavior after DP fault Reserve, must be 0 BIT1 RW 0x00 (0dec)” However, in the project I see no way to configure this parameter, in any of the boards; and the arrays do not always have such an extensive size; most of the time they are only two or three words in size. The problem is that, after the hot reset of CoDeSys, the master restarts by starting all slave nodes, but if one or more get lost and go offline, there is then no automatic restart upon their return. I would need to figure out any solution, even via software, how to figure out that this one is back available and restart it.
Last updated: 2025-02-02

Post by shubadubalu on OP UA Client - Variablen zeigen alle 0 ^{CODESYS Forge talk (Post)}
Hallo liebe Codesys Community :) Momentan versuche ich eine OPC-UA Verbindung aufzubauen, dabei habe ich ein komisches Verhalten festgestellt. Man sucht sich ja die Variablen indem man auf "Variablen aktualisieren" in Datasource klickt. Diese werden dann auch in der enstprechenden Variablenliste automatisch deklariert. Wird das Programm übertragen und die CPU (PFC200) gestartet, aktualisieren sich die Werte entsprechend. Mittels UA Expert passen die Werte aller Variablen. Starte ich jetzt die CPU neu (OPCUA Client), werden alle Variablen mit dem Wert 0 angezeigt. Unter "Allgemein und Diagnose" wird verbunden angezeigt. Auch UA Expert zeigt weiterhin die aktuellen Server Werte. Klicke ich erneut auf "Variablen aktualisieren" und übertrage das Programm funktioniert wieder alles. Ein Kalt / Warmstart hat leider keine Auswirkung. Auch den Server Neustarten bringt kein Erfolg. Wie schaffe ich es, dass die Variablen nach CPU Neustart auch die Werte des Servers annehmen? Ich freue mich über Tipps und Ideen. :) Weitere Informationen: CODESYS 64 3.5.20.50 CPU: WAGO PFC 200 750-8216 OPC UA Kommunikation Anonym und ohne Security-Strategie
Last updated: 2025-02-18

Post by amani on PN Controller auf Raspberry Pi 4 ^{CODESYS Forge talk (Post)}
Hallo zusammen, Ich mache +/- erste Schritte mit RaspberryPi und Codesys: tolle Sache! Ich habe Codesys V3.5 auf einem Raspberry Pi 4 am laufen. Ich würde damit gerne einen Profinet-Slave bedienen. Die Kommunikation läuft, nun habe ich das Problem dass ich nicht verstehe wie ich den PN-Task mit dem PLC task synchron halte: Ich muss dem Slave eine Parameter-ID übergeben und beim nächsten Zyklus die Antwort auslesen. Da es dann mehrere Parameter gibt die ich nur sequentiell auslesen kann benutze ich also einen Zähler der mir die ID's durchstept. Aktuell sieht es aus als ob dieser Zähler schneller inkrementiert als der Slave antwortet (ich habe z.Bsp. 5 Parameter, diese zeigen dann alle das gleiche oder springen zwischen den Parametern). Also kurz gesagt ich muss sicherstellen dass die Datenbytes vom Slave zur gesetzten Parameter-ID passen... Ich wäre froh um ein paar Tipps! Herzlichen Dank! Grüsse, Stephan A. Wicki
Last updated: 2025-02-26

Sort by relevance or date