Post by monw on Unable to Re-Import Native XML Exported Using CODESYS Script API ^{CODESYS Forge talk (Post)}
When exporting a Logical Device or Logical Exchange GVL using the native XML export functionality of the CODESYS Script API, I encounter the following error upon re-import: "Error in IEnumeratorOfTWrapper. Current. Could not cast: System.String in System.Char" I am using CODESYS V3.5 SP21 Patch 2. Is there a known solution or workaround for this issue? Notably, importing the same XML file through the CODESYS Engineering IDE's menu import works without error.
Last updated: 2025-09-12

Post by timvh on How to correctly create a device descriptor (.devdesc.xml) for a custom Linux ARM64 PLC in CODESYS 3.5.21.20? ^{CODESYS Forge talk (Post)}
If you are a vendor of controllers and want to have your own CODESYS Runtime on your device, then you need to contact the CODESYS Sales team and ask for the runtime Toolkit. For resellers of CODESYS devices, this can be interesting. If it is only for a few devices, then why not just take the standard runtime?
Last updated: 2025-10-07

Post by hismoon on CodeSys SVN funktionert nicht ^{CODESYS Forge talk (Post)}
Das CODESYS SVN AddOn hat Minimal-Versions-Vorgaben. In SP9 funktioniert wohl die neueste SVN Version nicht. Da mal am besten im Store auf die Release Notes auf der Download-Seite schauen. Da steht meistens, ab wann Minimal-Versionen erhöht wurden. (Required CODESYS version) V4.2.6.0 vom SVN AddOn scheint die letzte zu sein, die mit SP9 offiziell funktioniert. Eigentlich sollte das der CODESYS Installer / Package Manager abfangen, aber hmm.
Last updated: 2024-06-04

Post by timvh on History of Alarms ^{CODESYS Forge talk (Post)}
It is most likely related to the existing alarm log files in the Control Win. Depending on how you start up the Control Win, you can find the files in: C:\Users\<user name="">\AppData\Roaming\CODESYS\CODESYSControlWinV3x64\<unique id="">\PlcLogic\alarms\ Or C:\Windows\System32\config\systemprofile\AppData\Roaming\CODESYS\CODESYSControlWinV3x64\<unique id="">\PlcLogic\alarms\</unique></unique></user> Delete the files in this folder, download your project again and start the application. PS, if you have an older version of CODESYS, the files are in: C:\ProgramData\CODESYS\CODESYSControlWinV3x64\<unique id="">\PlcLogic\alarms</unique>
Last updated: 2026-01-07

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 jinlee on Symbol Configuration ^{CODESYS Forge talk (Post)}
Hi guys, I am working on an old project which using Codesys v2.3 talks to Beijer's screen TA150 (IX-Developer 2.20). Codesys v2.3 is different with 3.5 and Ecockpit. I know how to import the symbols from PLC to HMI for Codesys 3.5 and Ecockpit. However, I do not know how to do it on Codesys v2.3. I know that I can make excel sheet to import and export from the HMI and add whatever I want based on PLC. However, is there any quicker way of doing this? So that I can directly import the symbols (tags) from PLC (Codesys 2.3 to HMI).
Last updated: 2023-08-29

Post by micik on Start Codesys project and then execute python script from command line ^{CODESYS Forge talk (Post)}
Hello, by searching the forum, I have found an example of batch script that can be used to start codesys projct by temporarily setting env variables. However, I'm not sure how to modify this to start Codesys 3.5.20 and whether or not I need to specify "profile" with Codesys version at all. @echo off SET PROJECT=D:\TestScripts\Data\OnlineTest.project SET VARIABLES=POU.testint,POU.testoutput start /wait CoDeSys.exe --profile="CoDeSys V3.4 SP3" --noUI --runscript="D:\TestScripts\Forum_Environment.py" I have tried the following just to open the test project: SET PROJECT=C:\TEST\Example.project start CODESYS.exe --profile="CODESYS V3.5 SP20 Patch 2" But I'm not sure how to specify this project to be open after py script is executed. The py script should first add required library to the project and then project should be open.
Last updated: 2024-09-30

Post by timvh on Profinet fault with codesys control V3 - Receive packet error ^{CODESYS Forge talk (Post)}
Are you using the Control Win SL (installed together with the development environment of CODESYS)? If yes, you might want to consider using the CODESYS RTE instead. This has real-time capabilities (running on separate core(s)). But to be able to use this, you have to install the CODESYS Ethernet driver for your network interface to be able to let the RTE access the network port also in realtime. See: https://store.codesys.com/en/codesys-control-rte-sl-bundle.html https://content.helpme-codesys.com/en/CODESYS%20Control/_rtsl_windows_rts_v3.html PS, I haven't tested this myself yet, but you could try to use the SetCommunicationState method of the Profinet controller to see if you can reset and start the bus communication: result := PN_Controller.SetCommunicationState(eRequestedState := DED.DEVICE_TRANSITION_STATE.START); PS, if you are located in the Netherlands or Belgium, we could also provide the license(s) for you.
Last updated: 2024-02-28

Post by timvh on Profinet fault with codesys control V3 - Receive packet error ^{CODESYS Forge talk (Post)}
Are you using the Control Win SL (installed together with the development environment of CODESYS)? If yes, you might want to consider using the CODESYS RTE instead. This has real-time capabilities (running on separate core(s)). But to be able to use this, you have to install the CODESYS Ethernet driver for your network interface to be able to let the RTE access the network port also in realtime. See: https://store.codesys.com/en/codesys-control-rte-sl-bundle.html https://content.helpme-codesys.com/en/CODESYS%20Control/_rtsl_windows_rts_v3.html PS, I haven't tested this myself yet, but you could try to use the SetCommunicationState method of the Profinet controller to see if you can reset and start the bus communication: result := PN_Controller.SetCommunicationState(eRequestedState := DED.DEVICE_TRANSITION_STATE.START); PS, if you are located in the Netherlands or Belgium, we could also provide the license(s) for you.
Last updated: 2024-02-28

Post by valec on Connect local Asem HMI runtime to local Codesys Control Win V3 x64 ^{CODESYS Forge talk (Post)}
I have a project made on a PL700 PLC with Codesys and an Asem Premium HMI panel. I don't have access to the physical PLC right now, so I'm trying to use Codesys Control Win V3 x64. I created the application and loaded "Codesys Control Win V3 x64" without errors, then I activate "Start PLC" from the tray. Asem cannot connect. I tried to use "localhost" or the local IP address and it doesn't work (it's the "CoDeSys Soft PLC Communication Driver"). I need to connect my local Asem runtime to a virtual Codesys application on my PC. How can I do it?
Last updated: 2024-03-26

Post by timvh on Codesys v3.5.22.10 - Fail to create a project Archive ^{CODESYS Forge talk (Post)}
There is an issue with adding the visu styles to the archive with Visu add-on 4.9.0.0 and 4.9.1.0. When you create the projectarchive disable the option to add the style(s) to the archive. CODESYS support informed me it will be fixed with visu add-on 4.10.0.0 (May 26th 2026). An alternative is to start CODESYS as Administrator. Then it will work with styles as well. You could start CODESYS as Administrator by first opening the CODESYS Installer. At the bottom you can select to start the Installer as Administrator. If you do this and then start the CODESYS version from this installer, it will work.
Last updated: 2026-04-25

Post by caspershes on Checking the device tree, not just the code: what else is worth a static check? ^{CODESYS Forge talk (Post)}
I spend most of my time reviewing other people's CODESYS projects before commissioning, and two kinds of defects keep showing up. Both compile clean. Both read fine. One is in the code. A pause timer whose own input gets cleared inside the branch the timer is supposed to gate: rampDelay(IN := run_2); IF NOT run_2 OR rampDelay.Q THEN run_1 := TRUE; run_2 := FALSE; // the timer's own input, cleared right here ELSE run_1 := FALSE; run_2 := FALSE; END_IF Next scan IN is FALSE, the timer resets, the condition is true again, and the second pump starts immediately. A 30-second ramp delay that actually lasts one task cycle. The setpoint is on the HMI, the operator turns it, and nothing changes. The other is not in the code at all. On one site the outdoor temperature read 0.0 °C in mild weather. The ST was correct, the variable was bound to the channel — but the channel's sensor type was left at "disabled", so nothing was ever digitised. Same class: a module with Disable_module = TRUE, or an analog output bound to a variable while its mode is off. Nothing in the project reports any of this, and the code review never looks there, because the configuration lives in the device tree and not in the POUs. That second class is what pushed me to parse the .export format rather than PLCopenXML alone — the export carries the device tree and the visualization, so "nothing ever writes this alarm variable" stops being a guess and becomes a fact you can check against the screen bindings. Three things about the format that cost me time, in case they save you some: the same device parameter can appear three times (template, internal copy, actual configuration) — the last occurrence is the one in effect; the enum value of a parameter is not in the parameter itself, it is one level down in BaseType/Value; a channel counts as used when a variable is bound to SensorValueN.SensorValue — InputStatus is a bad indicator, people deliberately bind it on spare inputs. So the question. What else would you check automatically, given both the code and the device tree? I am collecting rules from sites, not from style guides, and the configuration side feels largely unexplored. For what it is worth, the checker I use for this is free and runs offline (single exe, no install, nothing uploaded anywhere): https://github.com/caspershes/plc-lint — 43 rules at the moment, reads .export and PLCopenXML. Happy to add rules people here suggest.
Last updated: 2026-10-27

Post by spiessli on Raspberry Pi 4 with Legacy Drivers and Codesys 3.5.19 Patch 4 ^{CODESYS Forge talk (Post)}
Thanks for the suggestion, I have tried it eagerly: I have updated all packages to latest version with Codesys Installer and installed newest runtime and gateway on Raspberry Pi. Unfortunately, the error is still there. As soon as I add the SM_Drive_Servo to the device tree, I get the error below when generating the code. Reverting SM3_Basic to version 4.14 makes the error disappear. ------ Übersetzungslauf gestartet: Applikation: Device.Application ------- Code typisieren... Code erzeugen... [FEHLER] sm3_drive_servo, 4.10.0.0 (codesys): GetStandardConfigParams [AXIS_REF_SERVO]: C0032: Typ 'Unbekannter Typ: 'ConfigGetParameterValueLREAL(pParam, 0)'' kann nicht in Typ 'LREAL' konvertiert werden [FEHLER] sm3_drive_servo, 4.10.0.0 (codesys): GetStandardConfigParams [AXIS_REF_SERVO]: C0046: Bezeichner 'ConfigGetParameterValueLREAL' nicht definiert [FEHLER] sm3_drive_servo, 4.10.0.0 (codesys): GetStandardConfigParams [AXIS_REF_SERVO]: C0035: Programmname, Funktion oder Funktionsbausteinstanz an Stelle von 'ConfigGetParameterValueLREAL' erwartet [FEHLER] sm3_drive_servo, 4.10.0.0 (codesys): GetStandardConfigParams [AXIS_REF_SERVO]: C0032: Typ 'Unbekannter Typ: 'ConfigGetParameterValueLREAL(pParam, 0)'' kann nicht in Typ 'LREAL' konvertiert werden [FEHLER] sm3_drive_servo, 4.10.0.0 (codesys): GetStandardConfigParams [AXIS_REF_SERVO]: C0046: Bezeichner 'ConfigGetParameterValueLREAL' nicht definiert [FEHLER] sm3_drive_servo, 4.10.0.0 (codesys): GetStandardConfigParams [AXIS_REF_SERVO]: C0035: Programmname, Funktion oder Funktionsbausteinstanz an Stelle von 'ConfigGetParameterValueLREAL' erwartet [FEHLER] sm3_drive_servo, 4.10.0.0 (codesys): GetStandardConfigParams [AXIS_REF_SERVO]: C0032: Typ 'Unbekannter Typ: 'ConfigGetParameterValueLREAL(pParam, 0)'' kann nicht in Typ 'LREAL' konvertiert werden [FEHLER] sm3_drive_servo, 4.10.0.0 (codesys): GetStandardConfigParams [AXIS_REF_SERVO]: C0046: Bezeichner 'ConfigGetParameterValueLREAL' nicht definiert [FEHLER] sm3_drive_servo, 4.10.0.0 (codesys): GetStandardConfigParams [AXIS_REF_SERVO]: C0035: Programmname, Funktion oder Funktionsbausteinstanz an Stelle von 'ConfigGetParameterValueLREAL' erwartet [FEHLER] sm3_drive_servo, 4.10.0.0 (codesys): GetStandardConfigParams [AXIS_REF_SERVO]: C0032: Typ 'Unbekannter Typ: 'ConfigGetParameterValueLREAL(pParam, 0)'' kann nicht in Typ 'LREAL' konvertiert werden [FEHLER] sm3_drive_servo, 4.10.0.0 (codesys): GetStandardConfigParams [AXIS_REF_SERVO]: C0046: Bezeichner 'ConfigGetParameterValueLREAL' nicht definiert [FEHLER] sm3_drive_servo, 4.10.0.0 (codesys): GetStandardConfigParams [AXIS_REF_SERVO]: C0035: Programmname, Funktion oder Funktionsbausteinstanz an Stelle von 'ConfigGetParameterValueLREAL' erwartet [FEHLER] sm3_drive_servo, 4.10.0.0 (codesys): GetStandardConfigParams [AXIS_REF_SERVO]: C0032: Typ 'Unbekannter Typ: 'ConfigGetParameterValueLREAL(pParam, 0)'' kann nicht in Typ 'LREAL' konvertiert werden [FEHLER] sm3_drive_servo, 4.10.0.0 (codesys): GetStandardConfigParams [AXIS_REF_SERVO]: C0046: Bezeichner 'ConfigGetParameterValueLREAL' nicht definiert [FEHLER] sm3_drive_servo, 4.10.0.0 (codesys): GetStandardConfigParams [AXIS_REF_SERVO]: C0035: Programmname, Funktion oder Funktionsbausteinstanz an Stelle von 'ConfigGetParameterValueLREAL' erwartet Übersetzung abgeschlossen -- 15 Fehler, 0 Warnungen : Kein Download möglich
Last updated: 2023-12-20

Post by erictur on CODESYS Control for Linux ARM SL (32 bit) on Moxa UC-3100 IPC ^{CODESYS Forge talk (Post)}
UC3100 comes with Arm Cortex-A8 1 GHz and belongs to Moxa Industrial Linux 1 (Debian 9) for Arm-based Computers. I tried to install the CODESYS Control for Linux ARM SL (32 bit) on Moxa UC-3100 IPC. Unfortunately, the Third-party requirements: - libc >= 2.27 (required by CodeMeter Runtime) of the CODESYS Control for Linux ARM SL cannot be met on the Debian 9, which comes with glibc 2.24. I read the post by @johnlee (Getting Start with Codesys Control for Linux SL) (https://forge.codesys.com/forge/talk/Runtime/thread/0a515ced3f/). Where he discusses installation of CODESYS Control for Linux ARM SL on Debian 9. There was CODESYS Linux runtime v3.5.14 availble and it was successfully intalled on the Debian 9. However, the CODESYS Store has the oldest version V4.1.0.0 32 bit available. There is no way to find the CODESYS Linux runtime v3.5.14. So is there any work around for this? Or I cannot install the CODESYS Runtime on any of the Moxa IPCs based on the Moxa Industrial Linux 1 (Debian 9)?
Last updated: 2025-07-10

Post by kuegerls on PROFINET Controller SL: WRREC remains BUSY forever, no DCE/RPC packets transmitted (RevPi Connect 5 + NORD SK205E) ^{CODESYS Forge talk (Post)}
Hello , I am currently evaluating the CODESYS PROFINET Controller SL on a Revolution Pi Connect 5 and have encountered a problem with acyclic PROFINET Record Access (WRREC/RDREC). System Hardware: Revolution Pi Connect 5 Runtime: CODESYS Control 4.16.0.0 (SDK 3.5.21.10) Development System: CODESYS V3.5 SP21 (64-bit) CommFB: 3.5.17.10 ProfinetCommon: 4.6.0.0 PROFINET Controller Device: PN-Controller 4.6.0.0 PROFINET Device: NORD DRIVESYSTEMS SK205E with SK TU4-PNT GSDML: GSDML-V2.46-NORDDRIVESYSTEMS-PNT-20251016.xml Network The PROFINET network is completely separated from the office network. RevPi: eth0 → Office network eth1 → PROFINET wlan0 → Visualization The PN Controller is configured to use eth1. IP configuration: RevPi (eth1): 192.168.100.1/24 NORD Drive: 192.168.100.3 Connection is established successfully. Current Status The PN Controller reports: Controller Status = Run Online = TRUE IP Active = TRUE Connections = 1 Cyclic PROFINET IO communication works correctly. Problem I am trying to access PKW parameters via WRREC (Record Index 100). The request buffer contains: 01 14 00 04 92 00 00 00 00 00 00 which corresponds to Reference = 0x01 Request = Read Axis = 0 Parameter = 170 + 1000 Subindex = 0 Value = 0 The WRREC call is fbWRREC( REQ := xWrReq, ID := ConnectionID, INDEX := 100, LEN := 11, RECORD := ADR(TxBuffer) ); REQ is pulsed for one PLC cycle only. Observed Behaviour WRREC enters BUSY state and never finishes. Observed values: BUSY = TRUE DONE = FALSE ERROR = FALSE STATUS = 16#FFFFFFFF indefinitely. Packet Capture A Wireshark capture was taken on the PROFINET network. Observed traffic: PROFINET RT LLDP DCP Observed: successful cyclic IO Not observed: DCE/RPC Record Write Record Read RPC Bind No RPC packets are transmitted at all. Diagnostic Messages The controller repeatedly reports AR alarm.ind(err) AR CMI timeout although cyclic IO communication continues to work. Already Verified The following points have already been checked: correct Ethernet interface (eth1) correct CREATE_ID result correct Device ID correct Slot/Subslot correct GSDML correct REQ pulse RECORD buffer is larger than LEN cyclic IO communication works different Record Indices (100...104) tested Question Is there any known issue or limitation where WRREC/RDREC requests remain permanently BUSY and no RPC Record Access packets are generated? Could this behaviour be related to Runtime 4.16.0.0, PN Controller 4.6.0.0, the missing runtime license (currently running in demo mode), or any known issue with the PROFINET Controller SL? I am currently evaluating the PROFINET Controller SL and therefore the runtime is operating in demo mode. Could you please confirm whether WRREC/RDREC (acyclic Record Data services) are fully supported in demo mode, or whether a valid license is required for these services? If required, I can provide: complete project archive Wireshark capture (.pcap) GSDML online screenshots diagnostic log Thank you very much for your help. Best regards, Stefan
Last updated: 2026-07-17

Post by gurke258 on Codesys Safety EtherCAT with Beckhoff ^{CODESYS Forge talk (Post)}
Hello :) We are currently configuring a system with Codesys as SoftPLC on a Linux system and with Beckhoff terminals. I have already gained some experience with Codesys and also with TwinCat incl. TwinCAT Safety. What is new to me now is Codesys in conjunction with Beckhoff safety terminals. We are currently using an EL1918 & EL2904 here. I have been able to integrate both terminals into my project, but I don't know how to interconnect them so that they communicate. That's a bit easier with Twincat ^^ Can any of you help me? I would also prefer a Codesys EtherCAT Safety training or webinar if anyone knows of one. Unfortunately I can't find such an event on the internet.
Last updated: 2023-11-07

Post by martin-k on Beispieldateien finden / Inhalt der Packages ^{CODESYS Forge talk (Post)}
Hallo, ich habe https://store.codesys.com/de/codesys-in-building-automation-examples.html runtergeladen und mit dem Installer und Adminrechten installiert. Jedoch finde ich auf C: keine *.project* Dateien. Kann mir jemand erklären wie ich an die Examples dran komme? Auch von Wago habe ich Packages bekommen in denen Beispiele enthalten sind. Auch hier finde ich nix. (Googel habe ich gefragt. Aber mit den Stichworten kommen viele Treffer die alle nicht hilfreich waren.) In der Hilfe von Codesys habe ich natürlich auch gesucht, aber auch hier nichts erklärendes gefunden. Angeblich findet sich was in C:\Programme\CODESYS 3.5.19.40\CODESYS\Projects oder auch unter C:\Users\BENUZTERNAME\CODESYS Examples Aber wie geschrieben finde ich auf C:\ nix was ein Beispiel wäre. Wäre echt super wenn mir jemand einen Hinweis geben könnte. Danke im Vorraus, Martin
Last updated: 2023-11-16

Post by vamsi on How to configure gateway for programming RPi 2B using Codesys ^{CODESYS Forge talk (Post)}
I am using a Raspberry Pi 2B. Installed Codesys V3.5.20.1 64-bit and installed 'CODESYS Control for Raspberry PI 4.12.0.0' I am able to install the packages using the 'Update Raspberry Pi' option, but when I try to log into the RPi, in the Device tab it says 'Sacn fail. Please checl that the gateway is running and that its settings are correct'. My setup looks like this. I connected my RPi to my company LAN and also my laptop to company LAN (using HP Docking station). This setup worked when I installed 'CODESYS Control for Raspberry PI', but now I donot know how to configure the gateway. Could anyone please help me in finding what I have to enter in the gateway configuration? Thanks, Vamsi.
Last updated: 2024-07-10

Post by damian177 on Problem with downloading OPC UA tags by Data Source Manager ^{CODESYS Forge talk (Post)}
Hi, In Codesys V3.5 SP20, using Data Source Manager I am trying to connect to the OPC UA server and receive tags from it. The connection is ok, but the Codesys have a problem with downloading Tags group. The window (downloadingTags.jpg in attachement) never stop. After waiting for a while, I disconnect the connection and only the Server group remains downloaded, with OPC UA server diagnostic data (and this is read in Codesys). Of course, I tried connected via another OPC UA client : UaExpert , and everything works as it should, all tags are downloaded (Uaexpert.jpg screen). Has anyone on the forum encountered the OPC UA client configuration in Codesys? Is it possible to manually request the appropriate tags from the OPC server for reading in Codesys?
Last updated: 2024-09-03

Post by tqvist on Gateway Start ^{CODESYS Forge talk (Post)}
Hello, I am trying to connect to my PLC (IFM CR711S) via VPN(EWON COSY). I have been told to use Gateway SP14 or higher. I installed CODESYS 3.5 SP20 Patch4. In the Codesys Installer Software I can sleect "Set Gateway Service" and I do so for CODESYS 3.5 SP20 Patch4. I can start the Gateyay and select About and it shows: "CoDeSys Gateway V3 - x64 Version 3.5.20.40" (see attached) For compatibility reasons I have to run my PLC code in 3.5 SP11 and when I start I can first connect but then somehow the system restarts an older version of the Gateway only displaying: "CoDeSys Gateway V3" (see attached) I guess my question is how to run an old Cocesys Software with a new Gateway?
Last updated: 2024-11-26

Post by mazino on How to download dependencies packages for CODESYS Control for Raspberry Pi SL ? ^{CODESYS Forge talk (Post)}
Hi starmaxou, I’m facing the same issue you mentioned with the dependencies for the CODESYS Control for Linux SL installation. I was able to find the manual downloads for the CODESYS Edge Gateway and CodeMeter, but I’m still stuck on the other two dependencies: CODESYS Control SL Extension v4.0.0.0 CODESYS Control SL Deploy Tool v4.10.0.0 Since you’ve encountered the same problem, I’d really appreciate any help or insights you can share on how you were able to resolve it. Any tips or suggestions would be greatly appreciated! Thanks in advance!
Last updated: 2025-03-07

Post by fkoenig on Codesys Control Win 64 3.5.21.0 KNX unaufgelöste Referenzen ^{CODESYS Forge talk (Post)}
Hallo Zusammen, bei meinem Projekt habe ich die CODESYS Control Win 64 3.5.21.0 auf einen Windows 11 Pro PC installiert. Auf meinem Laptop befindet sich die CODESYS Version 3.5.21.10 In meinem Codesys Projekt wurde unter dem Ethernet-Adapter der KNX Stack hinzugefügt. Das Projekt ist beim übersetzen fehlerfrei. Wenn ich das Projekt anschließend auf die CODESYS Control Win 64 aufspiele, kommt bei 98% des downloads die Fehlermeldung 17 unaufgelöste Referenzen... (siehe beigefügter screenshot "Fehlermeldung_unaufgelöste_Referenzen") Im screenshot "Auflistung_unaufgelöste_Referenzen" ist zu sehen, welche KNX Element nicht aufgelöst werden können. Wie kann ich diese Fehlermeldung beheben bzw. was muss ich machen, dass ich das Projekt aufspielen kann?! Für eure antworten bedanke ich mich im Voraus! MFG koeni
Last updated: 2025-06-30

Post by bbmussatto on Connetion with Topcon Opus B3 ECO Full display ^{CODESYS Forge talk (Post)}
I have a Topcon Opus B3 ECO Full display and i wanna program it with codesys, but i cant connect it to the display. After creating a new project, i choose the device "Opus B3-B4-B6-3.5.19.50" that is already available in my version of codesys, but i think the problem is that my version of codesys or something else is not the same as the codesys runtime version running on my display. Can anyone tell me how i can see the codesys runtime version on my display? i tried looking in the settings (Daemon > CDS) on the display, but all i see is "N/A" for "Customer Number", "Customer Part Number" and "Customer Serial Number". Can anyone help me make this connection?
Last updated: 2025-10-07

Post by talpade on WAGO PLC 200 750-8216 Ethernet connection to Codesys 3.5 ^{CODESYS Forge talk (Post)}
Hello, I have the WAGO PLC 200 750-8210. In addition I have downloaded the "WAGO Devices and Libraries 2.0.4.3" and installed the library into the Codesys v 3.5. I then create a new project on Codesys 3.5 and select the device "750-8216 PFC200 (WAGO)" (which I downloaded from the WAGO library). However when I have connected the ethernet cable from the WAGO device to my computer and on my codesys 3.5 i press "Scan Network" on codesys and it does not detect the device. How can I get it to detect the device? (I have put the ethernet cable from my WAGO to the computer, but it does not show the device).
Last updated: 2024-02-05

Post by tecnocons on Trouble Writing Files to External Paths in CODESYS ^{CODESYS Forge talk (Post)}
Hello everyone, I'm encountering an issue in CODESYS regarding writing files to external paths. Despite correctly configuring the placeholder in the CODESYSControl_User.cfg file to allow access to an external folder, CODESYS doesn't seem to write any files, and no errors are reported. The issue on the older versions was absent with no placeholders. I've checked the operating system permissions, and they seem to be in order, but the issue remains. Has anyone faced a similar situation or has any suggestions on how I might resolve this problem? Any help would be greatly appreciated. Thank you in advance for your support. I'm using raspberry PI as a logger. RPI3 Buster Codesys 32bit SL V4.11 Codesys Win64 3.5.20 [SysFile] PlaceholderFilePath.1=/home/pi/scan, $SCAN$
Last updated: 2024-04-09

Sort by relevance or date