Post by timvh on Codesys complains about matching versions ^{CODESYS Forge talk (Post)}
Open the CODESYS Installer. Create an export file from your current PC from your current version. Then on the other PC Open the installer and install a new version based on the same essentials version, but additionally select the export file which you have created on the first PC. Or just install (import) it within the already existing version. For the installer, you can install it from: https://store.codesys.com/en/codesys-installer.html For help see: https://content.helpme-codesys.com/en/CODESYS%20Installer/_inst_install_setups_and_addons.html On PC 1, save the project as projectarchive (which will then include all the libraries and devices). Then extract this projectarchive on PC 2.
Last updated: 4 days ago

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 gilbert-mh on CAA net base TCP client cause PLC to crash - Kernel message : N0HZ_local_softirq_pending 80 ^{CODESYS Forge talk (Post)}
Hello all, I have been trying to implement a TCP client on a Festo PLC (CPX-E-CEC-M1) and it looks like it works well except that after some time (greatly varies between a few hours to more than 100h) my PLC crash. When I look into the log file the only thing I see is that before the crash happens a few kernel warnings : N0HZ_local_softirq_pending 80 and then the crash. I've looked into this warning and from what I could find on the net it seems that this is warning is triggered when the ethernet link is down. I've tried to correct this bug for quite some time and what I know is that : - The crash is caused by my TCP client, when I remove it from my code I see no crash - The crash happens more quickly the more the TCP client is used. - The time before the crash is not directly proportional to the number of communications or their size. But it looks like it is just more likely to happen if the client connect to the server at a higher frequency. - The precedent observation makes it seem unlikely that the crash is caused by some memory overflow because then the crash speed would be more proportional to the amount of data exchanged. SO from these observations, I believe that the crash could be caused by the PLC trying to connect to a server while there is some kind of issue with the ethernet link resulting in the PLC getting stuck in some indefinite state and making it crash. This still seems a bit unlikely to me because if the ethernet is down it simply shouldn't be able to contact the server and the communication would just fail which doesn't cause my PLC to crash. Has anyone encountered the same kind of problem (with the same kernel message) ? I am pretty sure the warning is not the direct cause of the crash but just an indicator that something is wrong with my PLC. Thanks in advance
Last updated: 2024-01-12

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 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 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 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 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 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

Post by albertisa on GPIO Konfiguration auf SK-AM64B ^{CODESYS Forge talk (Post)}
Hallo, seit einigen Tagen versuche ich erfolglos eine Ansteuerung der GPIOs des SK-AM64B Entwicklungsboards (Texas Instruments) über Codesys zu bewerkstelligen. Bei dem Versuch GPIOs anzusteuern, ohne die devdesc.xml bzw. den iodriver anzupassen, wird mir von Codesys die Fehlermeldung "Bus läuft nicht" (siehe Screenshot) angezeigt. Welche Vorgehensweise wird zur Konfiguration der IO empfohlen? Ist eine Anpassung der devdesc.xml und des IOdrivers notwendig? Wie wird am besten bei der Anpassung der genannten Dateien vorgegangen? Folgende Dokumentation ist mir bekannt, hat mir aber noch nicht weitergeholfen: https://forge.codesys.com/drv/io-drivers/doc/Generic/
Last updated: 2023-09-19

Post by damian177 on Codesys and SMS in RPi ^{CODESYS Forge talk (Post)}
Hi, I try use IIoT library to send and receive SMS by Raspbery PI and Codesys. I installed IIoT package and added the SMS library, But something is wrong, when I init communication it doesn't work, When I sniffer my communication (AT commands) beetwen RS232 RaspberryPi and my GSM modem I have only below commands: AT+CMEE=1 OK AT+CPIN? +CPIN: READY Anyone have idea what can be wrong ?
Last updated: 2023-09-28

Post by martinlithlith on Raspberry Pi: List of available drivers / libraries ^{CODESYS Forge talk (Post)}
As most of the posts are moved here around 2015, what would be the right version of codesys to run? Would it be better to install a older version of codesys or should i keep on downgrading libraries? Is there any work done to update theses libraries? It´s been a few years since the last update in this post, are there new libraries/devices for raspberry being added/posted somewhere else? Thanks, Martin
Last updated: 2023-10-17

Post by tehthoams on Find Function: Object reference not set to an instance of an object. ^{CODESYS Forge talk (Post)}
Hey, Sorry this isn't super helpful, but i had this problem once and was able to resolve it. I can't recall how I solved it and whether it was a problem with my codesys installation or the project itself. If it is the codesys installation, make sure all your required libraries and plugins are installed and available. compare with a colleagues installation if possible. I vaguely recall saving a copy of my project and deleting things one by one until the error went away...
Last updated: 2023-10-30

Post by tehthoams on Find Function: Object reference not set to an instance of an object. ^{CODESYS Forge talk (Post)}
Hey, Sorry this isn't super helpful, but i had this problem once and was able to resolve it. I can't recall how I solved it and whether it was a problem with my codesys installation or the project itself. If it is the codesys installation, make sure all your required libraries and plugins are installed and available. compare with a colleagues installation if possible. I vaguely recall saving a copy of my project and deleting things one by one until the error went away...
Last updated: 2023-10-30

Post by john-martin on Send file from codesys to...... ftp, cloud, etc ^{CODESYS Forge talk (Post)}
Hi everybody, I am looking for a solution to send files, for example, to an ftp or a cloud. I can't use oscat library because 64 bit controller are not supported. Therefore, I see that the IIoT library has some functions that might help me to implement this sending process in codesys. Does anyone have any examples of how to do this? I have spent some days with this issue without success. Best regards.
Last updated: 2023-11-02

Post by fred on Rasperry Control Debian 12 ^{CODESYS Forge talk (Post)}
Hi, I have Proxmox running on a Rasperry 4 and have debian 12 ARM installed here. I wanted to install Codesys Control for Raspberry on it. According to the messages, the runtime environment and the gateway were installed successfully, but I can't find a device to downplay a program. The sudo service codesys start command fails. (see image) Does somebody has any idea? Thank you for your help! Greetings Fred
Last updated: 2023-11-22

Post by song on How to convert a standard robot program into an excutive list when a robot runs? ^{CODESYS Forge talk (Post)}
Dear Sir, I'd like to learn and try to make robot based on Codesys, is there a FB block or other ways to convert a standard robot program into an excutive list? how codesys explain the robot command instructions on HMI, just like the SMC_NCDecoder used to convert CNC program into a list of SMC_GEOINFO object. Thanks very much! Peter Yan
Last updated: 2023-11-25

Post by timvh on Management of a PLC network from a remote station ^{CODESYS Forge talk (Post)}
Maybe the CODESYS HMI is a good solution. https://store.codesys.com/en/codesys-hmi-sl-bundle.html Run this on the remote main control station. In the HMI application you can add the data source manager and to this manager you can add Data sources. A data source has a reference to the PLC you want to connect to and can get access to the variables of the PLC application. You can then use these variables in the visualization of the HMI application.
Last updated: 2023-12-04

Post by snhatton on Running webvisu with Codesys Control Win V3 in Simulation Mode ^{CODESYS Forge talk (Post)}
Yes, you can use the CODESYS ControlWin V3 Soft PLC. However, if simulation is enabled on the device this will disable all communication, so you need to turn off simulation to view the visualization in a web browser. In simulation mode, all IO and communication is disabled for standalone testing. In addition, make sure to set the start visualization in the WebVisu object in the application tree. I hope this helps!
Last updated: 2023-12-04

Post by bfunk on Codesys 3.5 auf Wago 750-8101 ^{CODESYS Forge talk (Post)}
Moin, hat hier noch jemand das Problem, das die Codesysruntime (PFC100, Ver.4.11, projektiert mit Codesys 3.5.20sp1), auf der Steuerung nach kurzer Zeit mit einem AUSNAHMEFEHLER in STOP geht? Ich hatte das ganze schon am laufen, sollte dann ein Firmwareupdate durchfuehren (auf die neuste moegliche). Das Firmwareupdate konnte ich auf 03.10.08(22) ist sauber durchgelaufen, die Firmware laeuft auch noch wenn die runtime aufgegeben hat. bekomme die runtime nur dann wieder zum laufen, wenn ich den ganzen controller reboote.
Last updated: 2024-07-03

Post by vamsi on How to configure gateway for programming RPi 2B using Codesys ^{CODESYS Forge talk (Post)}
I found out what I was doing wrong. I was entering the wrong IP in the gateway. I found that I have to enter the RPi's IP in the gateway field from this post https://forge.codesys.com/forge/talk/Runtime/thread/01703ca970/#d9f6 But I do not understand why it has to be the RPi's IP. Could anyone help me in clarifying this?
Last updated: 2024-07-10

Sort by relevance or date