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 carl25 on Confused about stepper spec & tips on pwm-step/dir ^{CODESYS Forge talk (Post)}
Hello! I have asked the few I know who have knowledge of this and now turn to this one inexhaustible source of knowledge aka. the electronics forum. I was going to buy stepper motors yesterday but got so confused about the spec that I need to get an answer to this first. 2 different stepper motors, quite close in size but with very different spec. https://www.oyostepper.de/goods-40-Nema-17-Schrittmotor-Bipolar-12V-18-Grad-40Ncm-04A-12-Volt-4-Dr%C3%A4hte-Hybrid-Schrittmotor.html https://www.oyostepper.de/goods-38-Nema-17-Schrittmotor-Bipolar-18-deg-22Ncm-133A-28V-4-Dr%C3%A4hte-Hybrid-Schrittmotor.html Both Nema17 but the first 1.33A and 22Ncm and the second only 0.4A but almost double the torque. I can see that the resistance is very much higher on the latter but what's the catch? Double the torque to 1/3 the current sounds a little too good to be true so what am I missing?
Last updated: 2025-02-21

Post by pistola on C0357: "GetNextClient" is obsolete, use VisuUtils instead ^{CODESYS Forge talk (Post)}
I'm having some troubles with this same issue and I'm wondering if someone can help me out. On a settings visual I allow the operator to enter some values however if they activate the page change button it will change the change with the Numpad dialog open. Since I'm using Visuelems.CURRENTVISU to change the pages I came across this code noted below for determining if the Numpad dialog was active. This code worked great however now in 3.5.19 it's now obsolete. I've tried following the directions in the attached program above however I can't see to get it to work in my program. Can anyone provide some help to determine if a dialog is open? FUNCTION Check_Dialog_Open : Bool VAR_INPUT sDialogName : STRING; // Input variable for the name of the dialog END_VAR VAR pstClientData : POINTER TO VisuElems.VisuStructClientData; // Pointer to the client data structure itfDialogManager : VisuElems.IDialogManager; // Interface for the dialog manager itfMyDialog : VisuElems.IVisualisationDialog; // Interface for the specific visualisation dialog END_VAR // Begin the iteration over the client manager VisuElems.g_ClientManager.BeginIteration(); // Loop through each client until no more clients are found WHILE (pstClientData := VisuElems.VisuElemBase.g_ClientManager.GetNextClient()) <> 0 DO // Get the dialog manager interface itfDialogManager := VisuElems.g_VisuManager.GetDialogManager(); // Get the specific dialog interface using the dialog name itfMyDialog := itfDialogManager.GetDialog(sDialogName); // Check if the dialog is open for the current client Check_Dialog_Open := VisuDialogs.VisuDlgUtil_IsDialogOpen(itfMyDialog, pstClientData, itfDialogManager); // If the dialog is open, exit the loop IF Check_Dialog_Open THEN EXIT; END_IF END_WHILE
Last updated: 2025-03-27

Post by macman on Codesys 3.5 OPC UA Client to Kepware OPC UA Server ^{CODESYS Forge talk (Post)}
Hi, I have problem with connecting Wago PLC WAGO 750-8212/0025-0002 configured as OPC UA client to Kepware OPC UA Server. I am using Codesys 3.5.19.70. What I did so far. To the Codesys project I added object Data Source Manager and configured connection OPC UA like below: pic 1 Then I can browse the OPC server tags in “Variables” tab after prior trust on the server side of the client certificate created in the “Communication” tab: pic 2 Additionally second certificate has been created in Codesys for runtime process in “Security screen” as well as the server certificate was approved here: pic 3 But when I compiled project, downloaded it to PLC and go to RUN I can’t read selected in “Variables” tab, OPC Server tags. I am getting such error (ID: 7001): pic 4 All two PLC certificates has been trusted in OPC server (Kepware) side: pic 5 and Kepware server configuration look like this: pic 6 I can easily connect using third party OPC UA client UaExpert to Kepware server without problem. In attachment I added also log from Kepware OPC UA server. pic # - this specifies the number of a concrete graphic from one of the collective in attachment
Last updated: 2025-04-02

Post by bmatlove on Variable Length Array - Cannot mix variable and fixed length dimensions? ^{CODESYS Forge talk (Post)}
Using Codesys 3.5.18.30 I am trying to work with an array of variable length in one dimension, but known in the other dimension. For example, using an array that represents a list of items, each with an attribute profile. I do not know how many items will be in the list, but I know that every item has 5 attributes, like size, weight, etc. Codesys does not seem to be able to accept this. I have referenced Data Type: ARRAY OF documentation page, which is not explicit if variable & fixed length array dimensions can be mixed. In the VAR_IN_OUT scope, I initially tried MY_ARRAY : ARRAY [*, *] OF REAL; which was no problem, of course. I then modified it to MY_ARRAY : ARRAY [*, 1..5] OF REAL; which throws C0006: ', or ]' expected instead of '..' among consequent downstream errors. I then used the Auto Declare -> Array Wizard, which accepted (asterisk)-(asterisk) and 1-5 for 2-dimensional lower and upper bounds. It output: MY_ARRAY: ARRAY[*..*, 1..6] OF INT; which throws the same error stream. What's the deal here? Is this possible?
Last updated: 2025-05-23

Post by christoph--b on Probleme mit Speicheraufteilung nach Wechsel von Wago 750-841 zu 750-891 ^{CODESYS Forge talk (Post)}
Hallo, ich habe in meiner Hausautomation eine Wago 750-841 mit einem doch mittlerweile umfangreichen Programm. Diese wollte ich nun gegen eine 750-891 der 4. Generation austauschen. Aufgrund der Programmgröße hatte ich damals die Speichergröße für Retainvariablen von 16#4000 auf 16#7000 vergrößert und so läuft sie nun seit Jahren fehlerfrei. Allerdings mit der 750-891 bekomme ich offensichtlich eine Überschneidung mit dem Modbusregister, denn die Werte über Modbus spielen verrückt. In der Standardgröße mit 16#4000 tritt das Phänomen nicht auf, reicht dann aber nicht für das vorhandene Programm. Dafür gibt es sicher eine Lösung, denn die 891 hat ja deutlich mehr Speicher. Allerdings kenne ich mich mit der Speicheraufteilung nicht aus, wo man da was optimieren kann, damit ich den Speicherbereich entsprechend erweitern kann, aber es zu keiner Überschneidung kommt. Für Hilfe wäre ich sehr dankbar
Last updated: 2025-07-20

Post by kurtk on Modbus TCP Server ^{CODESYS Forge talk (Post)}
ditto I'm just getting my codesys wheels on and the modbus stuff is confusing. I am re-platforming an existing PLC application On that platform one could simply tag variables to register numbers and the whole shooting match could be accessed via modbus and typically holding registers and input registers were treated the same way... On codesys I see there is a modbus TCP server Device I/O mapping tab and a Modbus TCP server IEC objects tab I get the sense that one can configure the serving of variables both/either way but am unclear about the optimum/necessary path. Apparently in the IEC Objects tab one can "ADD" something or other - presumeably channels. I have created a preliminary function block but the Select Function Block window shows nothing to select WTH ? I exported the Device mapping and was surprised to see the entire Device IO map - complete with all the bit-mapped holding/input registers!! WTH!!?? Bit-mapped words are strictly a nichey special purpose application. I am targetting making a couple hundred variables available which would turn into hundreds of pages of IO/mapping Is the FUnction Block IEC objects thingy an alternative to that ? I notice that CODESYS shows the tags which the PLC used to specify the register address... are tags used in CODESYS for any specific hard-core purpose ?
Last updated: 2025-08-19

Post by kurtk on dynamic modbus devices ^{CODESYS Forge talk (Post)}
I am CODESYS neophyte getting my wheels on. My goal is to re-platform an existing PLC application written in 61131 ST I've got the majority of the code/variables in a compilable form - excluding all the IO and comms nuances I am not sure whether this the right forum An important functionality which I implemented on the other platform was totally dynamic modbus devices... Most configurations I have come across impose static MB configs in which all configured devices MUST be present and functional... I have monkeyed around with MB enough to know that herding a half dozen MB cats into a working config can be tricky. I just do them one at a time and dynamically turn them on/off in whatever combination is convenient with ID, IP, baud, parity etc being runtime tweakable. I am totally curious whether this is possible with codesys, or whether its device configuration corrals one into a static cage which requires re-building the code to support flexible variations. Best regards
Last updated: 2025-08-19

Post by kurtk on runtime dynamic modbus devices ^{CODESYS Forge talk (Post)}
I am CODESYS neophyte getting my wheels on. My goal is to re-platform an existing PLC application written in 61131 ST I've got the majority of the code/variables in a compilable form - excluding all the IO and comms nuances I am not sure whether this the right forum An important functionality which I implemented on the other platform was totally dynamic modbus devices... Most configurations I have come across impose static MB configs in which all configured devices MUST be present and functional... I have monkeyed around with MB enough to know that herding a half dozen MB cats into a working config can be tricky. I just do them one at a time and dynamically turn them on/off in whatever combination is convenient with ID, IP, baud, parity etc being runtime tweakable. I am totally curious whether this is possible with codesys, or whether its device configuration corrals one into a static cage which requires re-building the code to support flexible variations. Best regards
Last updated: 2025-08-19

Post by nicetuxedo on Can not activate license on Raspberry pi ^{CODESYS Forge talk (Post)}
Hello everyone, I'm hoping for some assistance with a license activation issue: a software crash has left my license in a strange state. Here is the sequence of events: I purchased a new license for the Raspberry PI from the official CODESYS web store. I opened the CODESYS and started the online activation process using the ticket number I received. During the activation, the CODESYS software threw an exception and crashed. I was not able to see if the activation completed. After restarting CODESYS, I attempted to run the activation process again with the same ticket number. The License Manager now gives me an error stating that the ticket has already been activated/used. I am now stuck because my installation is not licensed, but the activation server believes my ticket has been consumed. Has anyone encountered this before? Is there a way to have the ticket status reset?
Last updated: 2025-10-08

Post by mdetrana on VPLCs Tab 'Grey-ed Out', Cannot Create VPLC ^{CODESYS Forge talk (Post)}
When evaluating Codesys functionality, I found that the VPLC tab under Deploy Control SL > Operation > VPLCs is 'grey-ed out', see attached image. I'm trying to evaluate how my infrastructure will interact with Codesys on a Raspberry Pi 4, so I'm trying to demo running it before purchasing licenses. I was going through the Codesys tutorial here, and it never shows the tab as grey, so I do not know how to proceed. Let me know if I can get any additional information that can help. This could be related to an Info message that's sent when connecting- [INFORMATION] Connected successfully! [INFORMATION] Successfully connected to target (<ip_address>) [INFORMATION] No supported container engine found on device. You have to install a supported container engine to use Virtual Control. Please contact the Administrator of the device. [INFORMATION] Finished reading device information</ip_address> I'm not exactly sure what I would need to do to install a 'supported container engine'.
Last updated: 2025-10-09

Post by forest on SM Drive license error ^{CODESYS Forge talk (Post)}
Hi, when it comes about license, I used INVTmatic Studio, which uses Codesys, for programming INVT plc. I bought Codesys Modbus license, it was not expensive, and then realised that INVT didn't have License Manager option (greyed out in program) which is needed for using of Codesys License. I contacted support from INVT, but developers told me that option is still not available. So depending on environment for programming Codesys, you can or not use Modbus license. Good thing about this version of Modbus TCP it works both direction. I could send commands and receive feedbacks from drive. But communication stops after 30 mins. So I used simple version of ethernet modbus which is somewhere in INVT or Condesys library (I can check tomorrow) which works only one way. I could send cmd to drive, and control it, but didn't have any feedback, like some readings back in PLC. which is bad, but at least I could start it and it didn't fail after 30 mins.
Last updated: 2024-01-10

Post by levih on DocScripting ^{CODESYS Forge talk (Post)}
Hello I'm trying to use the DocScripting collection in Codesys. I've made it work on one PC(1) for the 3.5.16.4 version of the script collection. But when I try the same setup on another PC(2), I get an error message: Error loading Python DLL: D:\SCRIPTING\3.5.16.40\python27.dll (error code 14001) My setup on both PC's is thus: 1. Downloaded and installed Python 2. Copied the folder with the scripting collection to C: (because of admin rights) 3. Placed my .library file in the same folder as the scripting collection Only difference is that Python is v3.12.0 on PC1 and v3.12.1 on PC2. I thought maybe it was something with Python, but then I have tried using the scripting collection from 3.5.16.1, and that seems to work. Just not for scripting collection 3.5.16.4. I also can't seem to find any scripting collections on newer versions of Codesys? (e.g. 3.5.19.10) Thanks in advance!
Last updated: 2024-01-22

Post by willbechel on Errors about PLC configuration in CoDeSYs software ^{CODESYS Forge talk (Post)}
I saved it as the same project but in a different location. I opened this "new project". I clicked on the "Direct Login from Automation Builder" button. It automatically directed me to CODESYS, where I was able to create the "Create Boot Project" but first I also clicked login again but inside CODESYS keeping the automation builder login online. Additional Information: The "Create Boot Project" function in CODESYS is used to create a project that will automatically start when the controller is booted up. To create a boot project, you must first create a new project in CODESYS. Once you have created a new project, you can then use the "Create Boot Project" function to create a boot application. The "Create Boot Project" function will create a new application that is based on the current project. The new application will be saved in the same location as the current project. You can then download the new application to the controller.
Last updated: 2024-02-01

Post by willbechel on Project Login Problem ^{CODESYS Forge talk (Post)}
I saved it as the same project but in a different location. I opened this "new project". I clicked on the "Direct Login from Automation Builder" button. It automatically directed me to CODESYS, where I was able to create the "Create Boot Project" but first I also clicked login again but inside CODESYS keeping the automation builder login online. Additional Information: The "Create Boot Project" function in CODESYS is used to create a project that will automatically start when the controller is booted up. To create a boot project, you must first create a new project in CODESYS. Once you have created a new project, you can then use the "Create Boot Project" function to create a boot application. The "Create Boot Project" function will create a new application that is based on the current project. The new application will be saved in the same location as the current project. You can then download the new application to the controller.
Last updated: 2024-02-01

Post by fredsta on Unable to load dynamic modules (Download failed: Application=Application) ^{CODESYS Forge talk (Post)}
Hey there, I am currently trying to find a good solution for the communication between CODESYS Control on Raspberry Pi and "the rest of the world", i. e. the things apart from CODESYS on my linux. My first approach was to use the c-integration. So I created a lib, defined extern fbs, compiled the code on my Pi using the SDK and put the .so into my lib project. When I try to log into the Pi and load the program, I get the error message which you can see in the attached picture. "Die dynamischen Module der C-Integration konnten nicht auf das Laufzeitsystem geladen werden" is german and means roughly "the modules from the c-integration could not be loaded onto the runtime system." Is this normal? Am I doing something wrong? I will have a look at the unix domain socket thing next, as I am still in the process of finding the best solution for the communication.
Last updated: 2024-02-15

Post by frank2 on 3.5.17: Rezepte: Fehlendes Kontextmenü ^{CODESYS Forge talk (Post)}
Guten Tag, ich möchte Rezepte verwenden. Mit Codesys 3.5.10.30 habe ich dabei auch keine Probleme. Mit Codesys 3.5.17.0 habe ich dabei auf fast allen Computern keine Probleme, lediglich bei meinem Laptop kann ich das Kontextmenü, welches es mir ermöglicht, Einträge zu lesen, schreiben, usw. nicht öffnen. Stattdessen kommt lediglich ein Standard-Menü, welches mir Kopieren, Einfügen usw. anbietet - hier ist das allerdings wenig hilfreich. Der Installer sowie das Projektarchiv sind auf allen Geräten identisch, ein Problem mit dem Projekt selber schließe ich also aus. Ich habe schon versucht, Codesys 3.5.17.0 neu zu installieren. Dazu habe ich die alte Version deinstalliert, und danach auch den Ordner "C:\Programme (X86)\Codesys 3.5.17.0" gelöscht. Mehr wollte ich ahnungslos nicht entfernen, und da ich bisher keinen Erfolg hatte, bitte ich euch um eure Unterstützung. Hat jemand eine Idee, was das Problem verursacht? Wo macht es Sinn, nachzuschauen? Kennt jemand genau das Problem vielleicht sogar? Falls ich mich unklar ausgedrückt habe, bitte ich um Rückfragen, dann versuche ich mein Problem entsprechend weiter zu erklären. Für jede Unterstützung bin ich dankbar! Viele Grüße Frank
Last updated: 2024-02-23

Post by dominggus on when going online, stuck on "Syncing file "visuelemsdatetime.tl_datetime.txt" ^{CODESYS Forge talk (Post)}
Hi, We are currently using a Raspberry Pi 4 CM4 module in a EdgeBox RPI 200 - Industrial Edge Controller running the latest CODESYS Runtime Package 4.11.0.0. On the PC (actually an Intel Macbook Pro running Windows 10 in Parallels) we run CODESYS V3.5.19.50. Yesterday end of day when I was about to logoff and head home, I wanted to send the latest build to the Raspberry I clicked the Login button to compile a new version and then sync the application and all the files, it get's stuck on the last file to sync (see attached screenshot). This takes eternally, although sometimes, when I use my SFTP client (Cyberduck) and go into the raspberry and refresh the directory /var/opt/codesys/PlcLogic/visu/, or when I open the actual file visuelemsdatetime.tl_datetime.txt, it gets un-stuck (forcing a refresh, which might fix the syncing issue) and CODESYS continues and I can click the Start button to start the application. But this SFTP force refresh trick does not always help either... What could be the issue here? network connectivity? Can someone please help me out?
Last updated: 2024-03-02

Post by francescoc on Custom log CmpLog ^{CODESYS Forge talk (Post)}
Hi, I am trying to create a log in my application. Since I cannot find any documentation regarding modifying the codesys configuration file to be able to log in ms, i tried to create a new log via CmpLog.LogCreate. Below is the part of the code where I create the logger and write a test string. In the log tab of codesys I actually see the new log that was created, but it is empty, and in the folder I cannot find any files. I can't find any detailed documentation. Can you guys give me support? Are there any examples? Thank you IF NOT FirstCycle THEN LogName:= 'LOGS/TestLog'; LogOptions.bEnable:= 1; LogOptions.iMaxEntries:= 5000; LogOptions.iMaxFiles:= 100; LogOptions.iMaxFileSize:= 5000; LogOptions.szName:= LogName; LogOptions.uiType:= CmpLog.LogTypes.LT_TIMESTAMP_RTC_HIGHRES; LogOptions.uiFilter:= CmpLog.LogClass.LOG_ALL; LogHandle:= CmpLog.LogCreate(pOptions := ADR(LogOptions), pResult:= ADR(Result)); LogHandle:= CmpLog.LogOpen(pszName:= LogName, pResult:= Result); Component_Manager.CMAddComponent2('TestLogNEW', 16#00000001, ADR(udiCmpIdNEW), 0); CmpLog.LogAdd2(LogHandle, udiCmpIdNEW, CmpLog.LogClass.LOG_INFO, 1, 1, 'Logger started...'); END_IF IF TestWrite THEN TestWrite:= FALSE; CmpLog.LogAdd2(LogHandle, udiCmpIdNEW, CmpLog.LogClass.LOG_INFO, 1, 1, 'Write test'); END_IF
Last updated: 2024-03-16

Post by thewizard8 on Raspberry PI4 Serial Port ^{CODESYS Forge talk (Post)}
Hi Dear All, I'm using my raspberry PI4 as a CoDeSyS PLC (Build from scratch with custom electronics). I was able to implement all fieldbuses with the exception of Modbus Serial. I'm using the internal Port (GPIO) and I configured it in /etc/Codesyscontrol_user.cfg the following away: [SysCom] Linux.Devicefile.1=/dev/ttyUSB0 Linux.Devicefile.2=/dev/ttyS0 I'm using COM2 on Master configuration. I'm using a interface board from TTL/RS485 (bidirectional board), and it's works perfectly with other devices but not in CoDeSyS. I'm able to send data with python script and read it on my pc using putty, but when I use a modbus slave simulator to interface with codesys I always get red icons on master and slave. (Please find image attached). I'm pretty shure that this might be a bad parameter on my CoDeSyS runtime configurstion file. Can someone help me? I'm stuck and this is for my master degree certification.
Last updated: 2024-03-18

Post by squiggleypuff on RemoteTargetVisu creates Unresolved Reference ^{CODESYS Forge talk (Post)}
I have a project with a Festo CPX-E-CEC-C1-PN PLC (Run-time version 3.5.12.50) that I have been developing on just fine using Codesys V3.5 SP19 Patch 5 (64bit). I am at the stage where I wanted to use the Festo HMI screen, and have added a RemoteTargetVisu object to my application. After adding this object, I am no longer able to log in to the PLC as I get an Unresolved Reference warning for 'USERMGRUSERGETPROPERTY' towards the end of the download process. I was able to find this post (https://forge.codesys.com/forge/talk/Visualization/thread/fc686a6cb2/) where the two possible solutions are to "set the placeholder to emtpy" or update the runtime. Problem is, I don't know how to do either of these things, as I'm still very green in Codesys land. I'd be happy to update the Festo PLC runtime, as that seems like the better option, but have not had any luck in finding a tutorial for this online. If anyone could point me in the right direction I'd appreciate it.
Last updated: 2024-03-19

Post by markushunter on Different behavior between the "Start" button in the IDE and the Cmp function "AppStartApplication()" ^{CODESYS Forge talk (Post)}
In our application with CODESYS V3.5 SP19 Patch 5 and the Soft-PLC Name: CODESYS Control Win V3 x64 Typ: 4096 ID: 0000 0004 Version: 3.5.19.50 the application behaves differently when we start the application via Cmp.AppStartApplication(pApp) than when we press the "Start" button in online mode in the IDE. Unfortunately, it looks like the AppStartApplication() function, which is called in the "StopDone" system event, is not able to restart the fieldbus driver correctly, in our case the EtherNet_IP_Scanner: Name: EtherNet/IP Scanner Hersteller: 3S - Smart Software Solutions GmbH Kategorien: EtherNet/IP Scanner Typ: 100 ID: 0000 100B Version: 4.5.1.0 Bestellnummer: 1 And one EtherNet/IP adapter Name: FANUC Robot R30iB Plus Hersteller: FANUC Robotics America Kategorien: EtherNet/IP Remote Adapter Typ: 101 ID: 356_12_4_3 Version: Major Revision=16#3, Minor Revision = 16#1 Beschreibung: EtherNet/IP Target imported from EDS File: fanucrobot0301_r30ibp.eds Device: FANUC Robot R30iB Plus Version Konfiguration 3.5.6.0 The application was cold reset in both cases via CmpApp.AppReset(pApp := pApp, usResetOption := CmpApp.RTS_RESET_COLD. Does anyone know the difference between the functions or services executed by the "START" button in online mode and Cmp.AppStartApplication()? Thanks and best regards, markushunter
Last updated: 2024-03-20

Post by markushunter on Different behavior between the "Start" button in the IDE and the Cmp function "AppStartApplication()" ^{CODESYS Forge talk (Post)}
In our application with CODESYS V3.5 SP19 Patch 5 and the Soft-PLC Name: CODESYS Control Win V3 x64 Typ: 4096 ID: 0000 0004 Version: 3.5.19.50 the application behaves differently when we start the application via CmpApp.AppStartApplication(pApp) than when we press the "Start" button in online mode in the IDE. Unfortunately, it looks like the AppStartApplication() function, which is called in the "StopDone" system event, is not able to restart the fieldbus driver correctly, in our case the EtherNet_IP_Scanner: Name: EtherNet/IP Scanner Hersteller: 3S - Smart Software Solutions GmbH Kategorien: EtherNet/IP Scanner Typ: 100 ID: 0000 100B Version: 4.5.1.0 Bestellnummer: 1 And one EtherNet/IP adapter Name: FANUC Robot R30iB Plus Hersteller: FANUC Robotics America Kategorien: EtherNet/IP Remote Adapter Typ: 101 ID: 356_12_4_3 Version: Major Revision=16#3, Minor Revision = 16#1 Beschreibung: EtherNet/IP Target imported from EDS File: fanucrobot0301_r30ibp.eds Device: FANUC Robot R30iB Plus Version Konfiguration 3.5.6.0 The application was cold reset in both cases via CmpApp.AppReset(pApp := pApp, usResetOption := CmpApp.RTS_RESET_COLD. Does anyone know the difference between the functions or services executed by the "START" button in online mode and Cmp.AppStartApplication()? Thanks and best regards, markushunter
Last updated: 2024-03-20

Post by markushunter on Different behavior between the "Start" button in the IDE and the Cmp function "AppStartApplication()" ^{CODESYS Forge talk (Post)}
In our application with CODESYS V3.5 SP19 Patch 5 and the Soft-PLC Name: CODESYS Control Win V3 x64 Typ: 4096 ID: 0000 0004 Version: 3.5.19.50 the application behaves differently when we start the application via Cmp.AppStartApplication(pApp) than when we press the "Start" button in online mode in the IDE. Unfortunately, it looks like the AppStartApplication() function, which is called in the "StopDone" system event, is not able to restart the fieldbus driver correctly, in our case the EtherNet_IP_Scanner: Name: EtherNet/IP Scanner Hersteller: 3S - Smart Software Solutions GmbH Kategorien: EtherNet/IP Scanner Typ: 100 ID: 0000 100B Version: 4.5.1.0 Bestellnummer: 1 And one EtherNet/IP adapter Name: FANUC Robot R30iB Plus Hersteller: FANUC Robotics America Kategorien: EtherNet/IP Remote Adapter Typ: 101 ID: 356_12_4_3 Version: Major Revision=16#3, Minor Revision = 16#1 Beschreibung: EtherNet/IP Target imported from EDS File: fanucrobot0301_r30ibp.eds Device: FANUC Robot R30iB Plus Version Konfiguration 3.5.6.0 The application was cold reset in both cases via CmpApp.AppReset(pApp := pApp, usResetOption := CmpApp.RTS_RESET_COLD. Does anyone know the difference between the functions or services executed by the "START" button in online mode and Cmp.AppStartApplication()? Thanks and best regards, markushunter
Last updated: 2024-03-20

Post by sanacfu on looking for v2.3 libraries on v3.5.19 ^{CODESYS Forge talk (Post)}
Hi all, I'm new to Codesys and Wago but well versed in Rockwell. I've been tasked with upgrading old Wago 750-880 PLCs that run Codesys v2.3. All I was giving is the original PLC program in v2.3 and the currently running machine. I've spec out to what I believe is a suitable upgrade, the PFC100 2ndGen, 750-8111. As I'm rewriting this code on the Codesys I can't find the same library functions blocks for ethernet settings PLC functions. Currently I'm working on code to get/set the PLC ethernet IP address and HMI IP addresses from the HMI screen. One other function I'm looking for is a warm reset function to the PLC. When googling for this stuff I see a lot of code not in ladder logic. Are these functions now not available to implement in ladder logic? Where can I get more information on finding and implementing this functions? Do I have to buy a license from Codesys to use these functions? The PLC I ordered should be arriving in 2-3 weeks.
Last updated: 2024-03-25

Sort by relevance or date