Post by khaledkhalil on Import OPC UA model to Codesys ^{CODESYS Forge talk (Post)}
I have added a models in SiOME which a software to design nodes and add instances. and created a resultant xml file. I tried to import the xml file to Codesys through OPC UA information model Repository the problem i don't know how to view my objects which i have designed. and map it to my PLC to make viewable on my server UaExpert. I watched the tutorial video https://youtu.be/aJhzN3Uk-Do?feature=shared. But it only give you how to add the Information model, and my resultant model doesn't have information type. So how in Codesys i can view a model which i have designed in SiOME and mapped my instances (Objects, Variable or methods) with my Variables in PLC I saw people do it in Tia Portal or other Software, but i have no clue how to do it on CODESYS
Last updated: 2024-03-12

Post by mp9876 on Problems with simulation in Window 10 ^{CODESYS Forge talk (Post)}
Hi Automa, it seems the solution you were bringing up on 2022-04-06 could really help me as I did not remember the password I initially set. My problem though is that I am using Codesys Control Win V3.5 SP19/60 (64 bit) and I cannot locate any of the files you listed up there. I have been looking inside folder: C:\Program Files\CODESYS 3.5.19.60\CODESYS\ and they appear not to be present at all neither in the CODESYS folder or any sub-folders. Uninstalling and re-installing unfortunately does not do the trick. Any idea how I could get out of the ditch on this issue ? Anyone else maybe ? Thanks
Last updated: 2024-03-18

Post by superjojo2002 on Licensing info not available. ^{CODESYS Forge talk (Post)}
If support for a containerized CODESYS runtime with a license isn't feasible, then I've considered an alternative approach: I've purchased and activated a "CODESYS Control Basic S" license on my Windows notebook, where I already have the Codemeter Control Center installed. Upon activation, I can see the CODESYS license as active on my notebook. Subsequently, I followed the instructions provided in this link (https://faq.codesys.com/display/CDSFAQ/How+to%3A+Setup+a+Wibu+Network+Server+Access+for+Licenses) to configure the Wibu runtime in the CODESYS container to access my external license server hosted on my notebook by editing the CODESYSControl_User.cfg file accordingly. However, it's worth noting that I'm still receiving a response from the Licensing Manager indicating that the runtime is persistently searching for a dongle instead of recognizing the soft container. So how can I get my runtime licensed now? Any ideas?
Last updated: 2024-03-20

Post by hafizapik99 on Webvisu not showing Codesys V3.5 SP13 Patch 2. ^{CODESYS Forge talk (Post)}
Hello, I am using a Hitachi Micro EHV+ for a small project, and I wanted to have a Web visu, done with Codesys V3.5 SP13 Patch 2. I test the Visu screen and it works well in Codesys, but I get a blank page when i enter the web visu in a browser. Here is the setting under web visualization: Update rate (ms): 5000 Default communication size: 100000 Under Visu_Task tab: Priority: 3 The Visu_Task interval is set to 2500ms I'm using Google chrome with the latest update, the Javascript is enabled with HTML5. Any advice?
Last updated: 2024-04-06

Post by cdutz on Problems connecting to Codesys 4.9.0.0 runtime on my Wago PFC200 ^{CODESYS Forge talk (Post)}
Hi all. I am currently struggling to get my Wago PFC200 running the Codesys Runtime in version 4.9.0.0 working. I am using Codesys V3.5SP19. I updated the PFC200 to the firmware version 04.01.10(23) after having tried the latest version (04.03.03(25) from Wago and not being able to start the runtime. After reading version 23 was needed, I changed to that and at least was able to have it start the codesys runtime. I also installed the "Codesys Control for PFC200 SL 4.9.0.0" plugin for Codesys to install the Codesys runtime in version 4.9.0.0 as well as update the Gateway on the device. While I seem to be able to connect to the gateway on the PLC (the dot is green) and when doing a scan, I do now find my PFC200, which is a huge improvement to before, where with firmware version 25 it just failed to start the runtime and I never found any device when doing a scan. Unfortunately I don't seem to be able to connect to the PLC in codesys. I logged in via SSH and changed the password and I can see that this password is correct as the stuff in the Codesys PFC200 tools tab only works if I use my changed password. And I used those credentials to update the installed Runtime version, which the log claimed to have worked fine. Now whenever I try to connect to the device found in the scan, I get a authentication pop-up with empy device name, device address: 000A. As User I use "root" and as password the password that I changed it to. As a response I just get "Ungültige Benutzerauthentifizierung auf dem Gerät" (Eng. probably something like "Invalid user authentication on the device". What could I be doing wrong? Admittedly I'm a bit lost here :-/ Chris
Last updated: 2023-08-26

Post by tariq on Using Hilscher CIFX Cards as EtherCAT Masters in CODESYS ^{CODESYS Forge talk (Post)}
Dear Codesys Support Team, I hope this message finds you well. I am currently working on a project that involves using a Hilscher CIFX card to act as an EtherCAT master within the CODESYS environment. Despite following the available documentation and setup guides, I have encountered some challenges and require assistance to ensure proper configuration and operation. Questions: 1- Could you please confirm if the Hilscher CIFX card is supported as an EtherCAT master in CODESYS? If so, are there specific drivers or configuration files that need to be installed? 2- Are there detailed setup guides or example projects available that demonstrate the integration of Hilscher CIFX cards with CODESYS for EtherCAT communication? 3- Is there any additional software or plugins required for ensuring seamless communication between the CIFX card and the EtherCAT slaves within CODESYS? Your support and guidance on these matters would be greatly appreciated, as it is crucial for the success of our project. Thank you for your time and assistance. I look forward to your prompt response. Best regards, TB
Last updated: 2024-07-02

Post by aliazzz on Unable to deploy Virtual Control SL on ARM64 (Raspberry Pi5) ^{CODESYS Forge talk (Post)}
Hi, I have successfully deployed "Virtual Control SL" on a few x86/64 machines now. However, I'd now like to deploy this to a Raspberry Pi (ARM64). To do this I prepared the Raspberry Pi5 with the following prereq's; * Minimal PREEMPT Debian * Latest Bootfirmware * full SSH access via non-root account * Podman * RedHat Cockpit with CODESYS LicensServer plugin up and running However, I can't seem to resolve copying the correct (deploy) Images as they wont show up in the CODESYS IDE I have added CODESYS Virtual Control for Linux SL and the CODESYS LicenseServer for Linux SL via the CODESYS installer on my DevBox. I open CODESYS > Tools > Deploy Control SL Next I enter the SSH targets IP and Credentials and for my RPi5 and it shows "Connected". In the next tab, Deployment, the dropdown box only shows one (1) image, which also is the incorrect CPU architecture. Only Virtual Control AMDx64 shows up (!?) while I expect to see the ARM64 based images for both Edge and Control. Has someone encountered this too? I'd like to hear other people experiences with Virtual Control deployment on ARM based architecture. attachment 1: AMD64 based deployment pulldown menu (correct images) attachment 2: ARM64 based deployment pulldown menu (incorrect images) regards,
Last updated: 2024-07-28

Post by rossanoparis on Clarifications regarding the appropriate runtime system to use ^{CODESYS Forge talk (Post)}
Hallo all I would appreciate some clarifications regarding the appropriate runtime system to use. I've been using 'KUNBUS CPUs' and 'CODESYS Control for Raspberry Pi MC SL' for the last 4 years. Recently, there have been some changes in the CODESYS licensing policy. [ https://store.codesys.com/en/howto_applicationbasedlicenses ] My questions are mainly two: 1) If I need to start a new project using 'KUNBUS CPUs', which is the correct runtime system to use. 2) Old projects built using 'CODESYS Control for Raspberry Pi MC SL' should be updated to another RT system? Current RT systems ... a)CODESYS Control for Raspberry Pi MC SL b)CODESYS Control for Linux ARM SL c)CODESYS Virtual Control SL May I count on receiving an explanation to understand the differences among the runtime systems listed above? A detailed and well-organized answer would be greatly appreciated. Kind regards Rossano
Last updated: 2024-09-23

Post by koerbejm on Probleme beim aktivieren von Lizenzen ^{CODESYS Forge talk (Post)}
Liebe Codesys-Gemeinde, ich habe folgendes Problem und bitte um Hilfe: Um eine auf meinem dem Raspberry Pi laufende Steuerung ohne große Mühe duplizieren zu können, habe ich mir ein Image der SD Karte mit Win32 Diskimager erstellt. Dieses konnte ich bisher ohne weitere Probleme auf eine weitere Micro-SD karte ausrollen. Anschließend habe ich mich via Putty auf den PI geschaltet, die vorherige Lizenz (die ja für den vorheringen PI zulässig war) gelöscht über - sudo su - rm -r /var/opt/codesys/cmact_licenses/ - reboot Um dann via Codesys 3.5 SP16 Patch 4 eine neue Lizenznummer ">>Tools>Lizenzmanager>Lizenz aktivieren" zu aktivieren und das wars. Durch die Umstellung des Lizensierungsverfahrens klappt diese Variante nun nicht mehr. Ich habe mir neue Lizenzen von Codesys gekauf, doch sobald ich diese in die Ticket-ID eintrage und aktivieren möchte bekomme ich folgende Fehlermeldung: ReturnCode: 403046401, An internal error has occured. Please try it again later. (siehe Bild im Anhang "Fehler_Codesys3.5V16.png") Ich habe dann meine Codesys-Version auf Version 3.5 SP20 geupdated und das selbe versucht mit dem Resultat, dass ich nun folgende Fehlermeldung erhalte: "Der ausgewählte Container "...." paßt nicht zu Ihrem Ticket. Bitte wählen Sie einen passenden aus." --> Siehe Bild im Anhang "Fehler_Codesys3.5V120.png" Was genau kann/muss ich tun, damit ich einfach wie bisher meine Steuerungen duplizieren kann? Verwendete Hardware: Raspberry Pi 3 Model B+ Verwendete Lizenz: Codesys Control Basic L Viele Grüße und Danke, Jan
Last updated: 2024-10-23

Post by faceplant on Comparison via CLI is broken ^{CODESYS Forge talk (Post)}
Hello! I am trying to compare 2 projects via the --compare CLI option. In the docs for the --compare option, it describes the usage as .\CODESYS.exe --compare "project path 1" "project path 2". I store my projects in WSL2 on my windows machine. Since CODESYS is happy to open those projects via a path like \\wsl.localhost\home\project.project. So, to compare, I use the command .\CODESYS.exe --compare "\\wsl.localhost\home\prog1.project" "\\wsl.localhost\home\prog2.project". This results in CODESYS just opening the project and starting, not comparing the two projects. No errors are thrown, and I know the paths are correct since I can open both independently in CODESYS, and I can compare them manually through the CODESYS UI. I have also tried moving my projects to the Windows 11 OS and still have the same issue. CODESYS opens the project and does not actually compare them. I am using CODESYS profile v3.5 sp20 patch 1. What is the correct way to compare 2 projects using the --compare CLI option?
Last updated: 2024-12-18

Post by x97tommi on XMLWriteAsync erzeugt keine XML-Datei unter CODESYS Control Win V3, obwohl NO_ERROR gemeldet wird ^{CODESYS Forge talk (Post)}
Ich versuche, mit dem Funktionsbaustein XMLWriteAsync eine XML-Datei zu erstellen, aber die Datei wird nicht erzeugt, obwohl der Funktionsbaustein NO_ERROR meldet. Ich habe sowohl meinen eigenen Code als auch das CODESYS-Beispiel getestet, aber in beiden Fällen wird keine Datei geschrieben. Ich arbeite mit CODESYS Control Win V3 als SoftPLC unter Windows. Problem: • Der Funktionsbaustein XMLWriteAsync meldet NO_ERROR (keine Fehler in xError, eError, oder eLastError), aber die XML-Datei wird weder im angegebenen Pfad (C:\Users\tomgs\Documents\CodesysDataTest\xmltest.xml) noch im res/-Verzeichnis (wie im CODESYS-Beispiel verwendet) erstellt. • Das CODESYS-Beispiel mit res/xmltest.xml als Pfad funktioniert ebenfalls nicht. • Ich aktiviere xExecute manuell in der Online-Ansicht, und xDone wird TRUE, ohne dass xError ausgelöst wird. • Der Ordner C:\Users\tomgs\Documents\CodesysDataTest\ existiert, und ich habe Schreibrechte. • Ich habe auch alternative Pfade wie C:\Temp\xmltest.xml und res/xmltest.xml getestet, ohne Erfolg. Im Anhang das Beispiel von Codesys. Vielen Dank im Vorraus.
Last updated: 2025-07-16

Post by pouyavakili on Execute Codesys Tests with python ^{CODESYS Forge talk (Post)}
❓ Issue: TestManager Not Available in Python Script (AttributeError) 🙏 Question: Why does project.get_testmanager() not work in scripting, even though Test Manager is installed and licensed, and the script runs in GUI mode? Is there a way to ensure the Test Manager interface is loaded or accessible from the scripting environment? 🧠 Summary: I'm trying to automate test execution using the CODESYS scripting engine (Python) via a script that opens a project, builds the application, and runs tests from a TestRepository.xml. Although the Test Manager works manually in the IDE, it fails when accessed via script with the following error: AttributeError: 'ScriptObject' object has no attribute 'testmanager' 🧪 Test Setup: CODESYS version: 3.5.21.10 Test Manager: Installed and licensed (works in the IDE manually) Project: Contains a test repository, which can be executed via the GUI Script execution method: powershell Start-Process -FilePath "C:\Program Files\CODESYS 3.5.21.10\CODESYS\Common\CODESYS.exe" ` -ArgumentList @( '--profile="CODESYS V3.5 SP21 Patch 1"', '--runscript="C:\Scripts\run_tests.py"' ) -Wait 📜 Script Summary: python project = projects.open(project_path) application = project.active_application application.build() This fails: testmanager = project.get_testmanager() ❗ Problem: Calling project.get_testmanager() or application.testmanager throws an AttributeError, even though the same project and test repository work in the GUI.
Last updated: 2025-07-23

Post by ranadheer on PHOENIX CONTACT Axioline PLCnext project in CodeSys SodftPLC ^{CODESYS Forge talk (Post)}
Hello Everyone, I'm working on a CODESYS Standard Project using CODESYS Control Win V3 x64 with Structured Text. The goal is to integrate a Phoenix Contact device coupler (Part ID: BK PN TPS 2403869) via PROFINET. Here am using the CODESYS V3.5 SP21 PATCH2 ,VERSION 3.5.21.20 , and Downloaded extension package 4.16.0.0 (old versions are not available in the extension CodeSys installer) Devices used here are: BUS COUPLER : 2403869 BK PN TPS Module carrier slot 1 : 1088127 AXL SE DI16/1 Module carrier slot 2 : 1088062 AXL SE AI4 | 4-20 Module carrier slot 3 : 1088129 AXL SE DO16/1 Module carrier slot 4 : 1088123 AXL SE AO4 | 4-20 -->Start a New Project Type: Standard Project Device: CODESYS Control Win V3 x64 Language: Structured Text -->Install GSDML File Navigate to: Tools > Device Repository > Install Select the GSDML file path (downloaded from Phoenix Contact for device coupler Part ID: BK PN TPS 2403869) Click Renew Device Repository Close the dialog -->Add Device to Project -->Right-click on Devices > Add Device Issue: Devices from the repository are not available to select or call into the project! I’d really appreciate any guidance or suggestions you can offer. Best Regards Ranadheer Reddy
Last updated: 2025-09-09

Post by hprog on Codesys 3.5.20/21 Import Geräterepository bzw. Bibliothen Repository funktioniert nicht ^{CODESYS Forge talk (Post)}
Hallo, Ich habe schon mehrfach Treiber für I2C Geräte geschrieben und keine Probleme mit dem Einbinden gehabt, aber derzeit komme ich auf keinen grünen Zweig. Der Import des Geräterepository (xml) funktioniert, der Import ins Bibliothekenrepository funktioniert auch, aber wenn ich dann das Gerät an den I2C MAster anfüge funktioniert der Import in das Projektbibiothek nicht und somit wird auch der entsprechende FB nicht instanziert und ich bekomme folgende Fehlermeldungen ------ Übersetzungslauf gestartet: Applikation: Device.Application ------- Code typisieren... [FEHLER] I2C_Test_Examples: MCP23008_X81 [Device: I²C: I2C_master]: Bibliothek Raspberry I2C MCP23008_X81, 1.1.0.1 (3S - Smart Software Solutions GmbH) konnte nicht eingefügt werden: [FEHLER] I2C_Test_Examples: C0035: Programmname, Funktion oder Funktionsbausteinstanz an Stelle von 'MCP23008_X81.AfterReadInputs' erwartet [FEHLER] I2C_Test_Examples: C0046: Bezeichner 'MCP23008_X81' nicht definiert [FEHLER] I2C_Test_Examples: C0035: Programmname, Funktion oder Funktionsbausteinstanz an Stelle von 'MCP23008_X81.BeforeWriteOutputs' erwartet [FEHLER] I2C_Test_Examples: C0046: Bezeichner 'MCP23008_X81' nicht definiert Kompilierung abgeschlossen -- 5 Fehler, 0 Warnungen Übersetzung abgeschlossen -- 5 Fehler, 0 Warnungen : Kein Download möglich Als Device habe ich Name: CODESYS Control for Raspberry Pi SL Hersteller: CODESYS Kategorien: SoftMotion Steuerungen Version: 4.13.0.0 Bestellnummer: 2302000009 Beschreibung: Eine Soft-SPS nach IEC 61131-3 für Raspberry Pi. CODESYS Control basiert auf CODESYS SDK 3.5.20.20, Release . Das ganze unabhängig von der Codesys Version
Last updated: 2025-10-06

Post by hprog on Codesys 3.5.21 Import Geräterepository bzw. Bibliothen Repository funktioniert nicht ^{CODESYS Forge talk (Post)}
Hallo, Ich habe schon mehrfach Treiber für I2C Geräte geschrieben und keine Probleme mit dem Einbinden gehabt, aber derzeit komme ich auf keinen grünen Zweig. Der Import des Geräterepository (xml) funktioniert, der Import ins Bibliothekenrepository funktioniert auch, aber wenn ich dann das Gerät an den I2C MAster anfüge funktioniert der Import in das Projektbibiothek nicht und somit wird auch der entsprechende FB nicht instanziert und ich bekomme folgende Fehlermeldungen ------ Übersetzungslauf gestartet: Applikation: Device.Application ------- Code typisieren... [FEHLER] I2C_Test_Examples: MCP23008_X81 [Device: I²C: I2C_master]: Bibliothek Raspberry I2C MCP23008_X81, 1.1.0.1 (3S - Smart Software Solutions GmbH) konnte nicht eingefügt werden: [FEHLER] I2C_Test_Examples: C0035: Programmname, Funktion oder Funktionsbausteinstanz an Stelle von 'MCP23008_X81.AfterReadInputs' erwartet [FEHLER] I2C_Test_Examples: C0046: Bezeichner 'MCP23008_X81' nicht definiert [FEHLER] I2C_Test_Examples: C0035: Programmname, Funktion oder Funktionsbausteinstanz an Stelle von 'MCP23008_X81.BeforeWriteOutputs' erwartet [FEHLER] I2C_Test_Examples: C0046: Bezeichner 'MCP23008_X81' nicht definiert Kompilierung abgeschlossen -- 5 Fehler, 0 Warnungen Übersetzung abgeschlossen -- 5 Fehler, 0 Warnungen : Kein Download möglich Als Device habe ich Name: CODESYS Control for Raspberry Pi SL Hersteller: CODESYS Kategorien: SoftMotion Steuerungen Version: 4.13.0.0 Bestellnummer: 2302000009 Beschreibung: Eine Soft-SPS nach IEC 61131-3 für Raspberry Pi. CODESYS Control basiert auf CODESYS SDK 3.5.20.20, Release . Das ganze unabhängig von der Codesys Version
Last updated: 2025-10-06

Post by hprog on Codesys 3.5.20/21 Import Geräterepository bzw. Bibliothen Repository funktioniert nicht ^{CODESYS Forge talk (Post)}
Hallo, Ich habe schon mehrfach Treiber für I2C Geräte geschrieben und keine Probleme mit dem Einbinden gehabt, aber derzeit komme ich auf keinen grünen Zweig. Der Import des Geräterepository (xml) funktioniert, der Import ins Bibliothekenrepository funktioniert auch, aber wenn ich dann das Gerät an den I2C MAster anfüge funktioniert der Import in das Projektbibiothek nicht und somit wird auch der entsprechende FB nicht instanziert und ich bekomme folgende Fehlermeldungen ------ Übersetzungslauf gestartet: Applikation: Device.Application ------- Code typisieren... [FEHLER] I2C_Test_Examples: MCP23008_X81 [Device: I²C: I2C_master]: Bibliothek Raspberry I2C MCP23008_X81, 1.1.0.1 (3S - Smart Software Solutions GmbH) konnte nicht eingefügt werden: [FEHLER] I2C_Test_Examples: C0035: Programmname, Funktion oder Funktionsbausteinstanz an Stelle von 'MCP23008_X81.AfterReadInputs' erwartet [FEHLER] I2C_Test_Examples: C0046: Bezeichner 'MCP23008_X81' nicht definiert [FEHLER] I2C_Test_Examples: C0035: Programmname, Funktion oder Funktionsbausteinstanz an Stelle von 'MCP23008_X81.BeforeWriteOutputs' erwartet [FEHLER] I2C_Test_Examples: C0046: Bezeichner 'MCP23008_X81' nicht definiert Kompilierung abgeschlossen -- 5 Fehler, 0 Warnungen Übersetzung abgeschlossen -- 5 Fehler, 0 Warnungen : Kein Download möglich Als Device habe ich Name: CODESYS Control for Raspberry Pi SL Hersteller: CODESYS Kategorien: SoftMotion Steuerungen Version: 4.13.0.0 Bestellnummer: 2302000009 Beschreibung: Eine Soft-SPS nach IEC 61131-3 für Raspberry Pi. CODESYS Control basiert auf CODESYS SDK 3.5.20.20, Release . Das ganze unabhängig von der Codesys Version
Last updated: 2025-10-06

Post by user0815 on Kommunikation zwischen ROS2 und CODESYS über Web Sockets ^{CODESYS Forge talk (Post)}
Hallo zusammen, ich hoffe ihr könnt mir weiterhelfen. Meine CODESYS Version ist die V3.5 SP19 Patch 4 und die Zielsystemversion ist die 4.10.0.0 . Ich verwende CODESYS ohne Lizenz. Ich probiere eine Verbindung über Web Sockets zwischen ROS und CODESYS aufzubauen. Der Client von CODESYS verbindet sich mit dem Ros Bridge Server aber ich weiß nicht wie ich dem Ros Server sage welches Topic er publishen soll. Über Node-Red habe ich eine Verbindung aufbauen können. Dafür habe ich "node-red-contrib-flowake-ros-nodes" verwendet. Den Daten Austausch habe ich mit mit Wireshark angeschaut und nun probiere ich den mithilfe von CODESYS nachzubauen. NAch dem sich der Client verbunden hat muss folgende Nachricht übermittelt werden:"{"op":"call_service","id":"call_service:/rosapi/topic_type:1","type":"rosapi/TopicType","args":{"topic":"/cmd_vel"}}." Ich vermute es funktioniert über Frames aber ich weiß nicht wie ich es umsetzten soll. Besten Dank für die Hilfe und schöne Grüße
Last updated: 2024-01-03

Post by rossanoparis on Upgrading CODESYS runtime from v4.7 to v4.9 using a bash script leads to lose the licences stored in the soft container ^{CODESYS Forge talk (Post)}
System information - Controller: KUNBUS RevPi CONNECT-S - OS: Linux buster 32bit 5.10.103-rt62-v7l #1 SMP PREEMPT_RT armv7l GNU/Linux - CODESYS v3.5 SP19 Patch 2 I'm facing a problem related to codesys licences using a procedure based on a bash script. Such bash script detect the presence of new .deb files and install them on system. My automation solution don't allow to be maintained by dedicated personal, thus even the CODESYS runtime SW must be installed using an "automatic" procedure instead of using the CODESYS tool. remark I've been using the following procedure since the runtime v4.5 without any issue. Before installing the new runtime packages, I need to copy the file CODESYSControl_User.cfg (here attached) because of new section which is necessary to add in order to allow some folders to be written by CODESYS runtime v4.9 Up to now, this has been unnecessary, this is the main difference between my previos bash file and the new one. remark If I skip this action, everythings goes fine, but my CODESYS application can't work as it needs to access some folders on controller's file system. Process - Before the procedure: the licenses are OK (see attached file lic-01.png) - After the procedure: the new CODESYS runtime version is correctly installed, but the software container with v1.19 and all licences disappear (see attached file lic-02.png) This is the synthetic content of bash script I'm using. # Stop runtime sudo service codesyscontrol stop sudo service codesysedge stop # Move the new CODESYSControl_User.cfg file # New configuraton with folders declared sudo mv -f CODESYSControl_User.cfg /etc # Install runtime package echo N | sudo apt-get install -y --allow-downgrades codesyscontrol_raspberry_4.9.0.0_armhf.deb # Install edge gateway package echo N | sudo apt-get install -y --allow-downgrades codesysedge_edgearmhf_4.9.0.0_armhf.deb # Reboot controller sudo reboot Thanks in advance
Last updated: 2023-09-19

Post by maldus512 on How to adapt Codesys Control SL to custom board ^{CODESYS Forge talk (Post)}
Hello everyone, I have been given the task to develop I/O drivers for a custom made, Linux based board to allow for Codesys applications to run and control the hardware. I have successfully installed Codesys Control SL for ARM/Linux and tested it with a simple demo application. Now I should start interfacing the runtime to the actual hardware; I should be able to interact with 2 RS485 serial ports, a few GPIOs and an I2C port, all of which already have the corresponding /dev/ interface in the Linux system. I am having trouble understanding how it should be approached. I have found sporadic references that fail to lead to a really comprehensive documentation. For example: The store page (https://store.codesys.com/en/codesys-control-for-linux-arm-sl-1.html#options) mentions a "runtime package" that should allow "Integration of existing C code" and "Usage of local I/Os", which seems exactly what I need to interact with custom peripherals. I have found no further reference to Codesys-C interpop. The Codesys Help page for the runtime package has a page on the "Development of Drivers" (https://content.helpme-codesys.com/en/CODESYS%20Control/rtsllinuxrbpdriverdevelopment.html) that suggests to either "Implement a function block" or "Implement I/O drivers". Those in turn lead to this page (https://forge.codesys.com/drv/io-drivers/doc/Generic/) which describes briefly an XML schema to describe new devices; unfortunately, it doesn't mention what to do with such a description (i.e. how does the runtime know about it) or how it is in any way connected to the actual hardware. Could anyone give me some pointers? I should also mention I have no prior experience with Codesys, so maybe I'm missing an obvious answer.
Last updated: 2024-08-09

Post by edson-bueno on SysProcess Execute Command unable to run commands with special characters ^{CODESYS Forge talk (Post)}
Hi, I found the same issue, and I fixed with this steps: 1st go to codesys .cfg file. sudo nano CODESYSControl.cfg Then insert this: [SysProcess] BasePriority=Realtime Command=AllowAll Now we need to grant codesys root rights on Linux. Step 1: Create or edit the systemd override configuration: sudo systemctl edit codesyscontrol In the editor that opens, insert: [Service] User=root Save and exit: Press Ctrl+O to save Press Ctrl+X to exit Step 2: Reload systemd and reboot To apply the override: sudo systemctl daemon-reexec sudo systemctl daemon-reload sudo reboot Step 3: Confirm CODESYS is running as root After reboot, open the terminal and run: ps aux | grep codesyscontrol You should see something like: root 1234 ... /opt/codesys/bin/codesyscontrol.bin ... If instead it shows admin or another user, the override was not applied correctly. Step 4: (Optional) Confirm from within CODESYS In your CODESYS project, insert this test code to run the Linux command whoami: Make sure the lib SysProcessImplementation, SysTypes, and CmpErrors is on the project. VAR sCommand : STRING := '/usr/bin/whoami'; sOutput : STRING(255); refCommand : REFERENCE TO STRING; refOutput : REFERENCE TO STRING; resultCmd : UDINT; END_VAR refCommand REF= sCommand; refOutput REF= sOutput; SysProcessExecuteCommand2( pszCommand := refCommand, pszStdOut := refOutput, udiStdOutLen := SIZEOF(sOutput), pResult := ADR(resultCmd) ); Notes & Warnings This method gives full system access to the CODESYS runtime — do not expose this system to the public network without protection. Do not use sudo in commands inside CODESYS when the runtime is already running as root. @tomas111, in case you want to read the temperatur, use this command: sCommand:STRING:='/usr/bin/vcgencmd measure_temp';
Last updated: 2025-05-20

Post by jeindhoven on Deploying to raspberry pi 5 hangs ^{CODESYS Forge talk (Post)}
Hi CoDeSys support forum, hope that this is the correct place to ask this. Might be double as i am new to Codesys and dont know all terminology. I am trying to test Codesys with a virtual plc on a raspberry pi 5. Already figured that i need Tools -> Deploy Control SL, enter Communication parameters. Codesys says "Connected". Then tab "Deployment", there i select "CODESYS Control for Raspberri Pi SL" and "4.16.0.0 (all)". Click "Install" and the gui turns grey and unresponsive. The titlebar says "Untitled1.project - CODESYS (Not Responding)" as well. Restarting Codesys and checking shows no package was installed. How to deploy the runtime? Thank you in advance for your time. Edit: After some patience, an error showed up: "Error when sending ssh heartbeat: Session operation has timed out" "Error installing codesyscontrol" Any pointers to what remote command might have failed, or log of some sort, would be welcome. Software versions: Codesys version 3.5.21.10 Raspberry pi 5 (deployment machine): $ uname -a Linux raspberrypi 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 11 (bullseye) Release: 11 Codename: bullseye $ apt list --installed | grep openssh-server openssh-server/oldstable,now 1:8.4p1-5+deb11u3 arm64 Development machine: $ uname -a Linux 2B 6.1.0-35-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.137-1 (2025-05-07) x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 12 (bookworm) Release: 12 Codename: bookworm VirtualBox Version 7.0.26 r168464 (Qt5.15.8) Virtual OS: Windows 10 Pro 64-bit (10.0, Build 19045) .NET version 4.0.30319.42000
Last updated: 2025-06-22

Post by vformanek on No source code available for profinet library ^{CODESYS Forge talk (Post)}
Hello, I have been using CODESYS for a while and after updating to version 3.5.18.50 the code randomly stops with this fault. Why is that ? I have tried to locate the fault in the Call Stack but I dont know what to do now... I have updated the projects properly for the version I am using. This fault started happening after like 14 days of using the new version of CODESYS.
Last updated: 2023-08-23

Post by mozed on Connection to device closed ^{CODESYS Forge talk (Post)}
Hello, Exulting the command /opt/CoDeSysControl/Files/run restart debug I get this response from the linux terminal:(ScreenShot1 to ScreenShot7) When I try to reconnect via codesys this line appears at the linux terminal level:(ScreenShot8) A few seconds later, the error window appears on Codesys.(ScreenShot9) I see that following the command /opt/CoDeSysControl/Files/run restart debug there are errors, are they the problem? Sincerely,
Last updated: 2023-08-24

Post by john-ronald on Communication error (#0), logout performed,please check if plc is connected ^{CODESYS Forge talk (Post)}
Hi, I have the same problem. However I am using ethernet connection not USB. I can ping the PLC and also connect to it via Wago ethernet settings, but I cannot upload using the Codesys 2.3. My PLC is Wago 750-862. The detailed error is - " connect: Connection refused Write attempt from invalid socket. " Any help would be appreciated.
Last updated: 2023-09-11

Post by timvh on ernesto881124 ^{CODESYS Forge talk (Post)}
You will need a USB to RS485 converter to connect the PC to the Modbus RTU Slave Device. In Windows this converter will be recognized as Serial COM poort (e.g. COM2, or COM3, see the windows device manager to find this out). Select this port in your CODESYS application. On the PC you need to use the CODESYS Control Win (SoftPLC) to run your application. It will not work in simulation mode, because then the Modbus Communication will not be activated.
Last updated: 2023-09-14

Sort by relevance or date