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
Is sure that on the PI5 is running bullseye, I would expect bookworm.
Anyway check if a ssh connection by putty work on this PI5. (use putty for example)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yep sure, though now that i think of it, its a pi 4. My bad. The whole ordeal was necessary to use the VGA666 adapter. That needs the old graphical system and GPIO directly on the CPU.
Edit: Putty on the virtual development machine connects fine. But i did change the login/pw. The account is still a sudo'er so that should be all right.
Edit2: Sorry i get a "Comment rate limit exceeded" from the forum. Then i'll add it as edit here.
So i have tried the stock raspberry pi image on a different pi5 (truly 5 this time). Packages updated. Standard password. Same symptoms, no runtime deployed and long hang time.
Versions of this pi:
pi@raspberrypi:~ $ uname -a
Linux raspberrypi 6.12.25+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.12.25-1+rpt1 (2025-04-30) aarch64 GNU/Linux
pi@raspberrypi:~ $ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 12 (bookworm)
Release: 12
Codename: bookworm
pi@raspberrypi:~ $ apt list --installed | grep openssh-server
openssh-server/stable,now 1:9.2p1-2+deb12u6 arm64 [installed,automatic]
Attached is the Device information and error text that Codesys comes up with.
Edit 3 (Comment rate limit, otherwise it would be a new post)
Now i have tried booting an older native Windows 10 machine (no virtualization), and it just works as expected. I have now a raspberry pi 4 and raspberry pi 5 with version 4.16.0.0 of the control application.
Windows 10 native: build 19045 (same as virtualised Win 10), same .NET version, same CODESYS version.
It seems that running CODESYS virtualized somehow messes with the deployment?
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 edit: jeindhoven 2 days ago
Is sure that on the PI5 is running bullseye, I would expect bookworm.
Anyway check if a ssh connection by putty work on this PI5. (use putty for example)
Yep sure, though now that i think of it, its a pi 4. My bad. The whole ordeal was necessary to use the VGA666 adapter. That needs the old graphical system and GPIO directly on the CPU.
Edit: Putty on the virtual development machine connects fine. But i did change the login/pw. The account is still a sudo'er so that should be all right.
Edit2: Sorry i get a "Comment rate limit exceeded" from the forum. Then i'll add it as edit here.
So i have tried the stock raspberry pi image on a different pi5 (truly 5 this time). Packages updated. Standard password. Same symptoms, no runtime deployed and long hang time.
Versions of this pi:
pi@raspberrypi:~ $ uname -a
Linux raspberrypi 6.12.25+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.12.25-1+rpt1 (2025-04-30) aarch64 GNU/Linux
pi@raspberrypi:~ $ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 12 (bookworm)
Release: 12
Codename: bookworm
pi@raspberrypi:~ $ apt list --installed | grep openssh-server
openssh-server/stable,now 1:9.2p1-2+deb12u6 arm64 [installed,automatic]
Attached is the Device information and error text that Codesys comes up with.
Edit 3 (Comment rate limit, otherwise it would be a new post)
Now i have tried booting an older native Windows 10 machine (no virtualization), and it just works as expected. I have now a raspberry pi 4 and raspberry pi 5 with version 4.16.0.0 of the control application.
Windows 10 native: build 19045 (same as virtualised Win 10), same .NET version, same CODESYS version.
It seems that running CODESYS virtualized somehow messes with the deployment?
Last edit: jeindhoven 1 day ago
..just use 'putty' ssh client on the virtual machine to login for a test to the pi.
if this work it should work in CODESYS too.