https://forge.codesys.com/forge/talk/Runtime/thread/1b5d0d6cc0/2021-12-08T14:19:45.295000ZRecent posts to ooops... this runtime was built for raspberry pi (-12, 0x00000BB8, 0xFFFFFFFB)2021-12-08T14:19:45.295000Z2021-12-08T14:19:45.295000Zjreitzighttps://forge.codesys.com/u/jreitzig/https://forge.codesys.com3a5e36e7b784864960b5a91f87d830dc63da11d4

<div class="markdown_content"><p>Hi. thanks for your replies....This was a "layer 8 problem". Still not knowing how I got in and out of this mess I am now back on track... Just two last questions (taking this thread totally off-topic:-( ):<br/> 1) The icons for modbus do not turn green but are operational... any deeper meaning to this ?<br/> 2.) If this is related to the demo license (for raspberry), do I also need an additional license for ModBus ? The logs let me assume this: Demo mode for Modbus/TCP Master started.<br/> Thank you</p></div>

2021-12-08T12:31:56.452000Z2021-12-08T12:31:56.452000Zi-campbellhttps://forge.codesys.com/u/i-campbell/https://forge.codesys.com1f442c3989a3c36280b718764a8da0bef4928d6a

<div class="markdown_content"><p>looking at the release notes, there was a bump to debian 11 <a href="https://downloads.raspberrypi.org/raspios_armhf/release_notes.txt" rel="nofollow">https://downloads.raspberrypi.org/raspios_armhf/release_notes.txt</a></p> <p>just adding some info, not a solution though. I dont suppose they added a default firewall pr something?</p></div>

2021-12-08T12:06:56.144000Z2021-12-08T12:06:56.144000Zjreitzighttps://forge.codesys.com/u/jreitzig/https://forge.codesys.comce3a0a712c1631b6d262c960480c2fd280eeed79

<div class="markdown_content"><p>Hi. Just a fresh reinstall of the latest RPI OS. The CodeSys runtime is 4.2.0.0 logs. It seems the device error is gone, yet I still can no longer get the modbus tcp conncetion to work.<br/> Even though the logs seem to indicate that the slave (192.168.100.106) is the root of the issue, I can assure that not a single byte is crossing the wire in neither direction as I am checking via tcpdump/wireshark using display filters for mbtcp. It all worked flawlessly until 2 days ago and now I am getting the error "Connection aborted: socket_recv() failed!"</p> <p>Can somebody see from looking at the logs whats going on ? </p></div>

2021-12-08T12:06:52.068000Z2021-12-08T12:06:52.068000Zjreitzighttps://forge.codesys.com/u/jreitzig/https://forge.codesys.com8a7a692fb0862a04b66b2932708e6911319df35e

<div class="markdown_content"><p>Hi. Just a fresh reinstall of the latest RPI OS. The CodeSys runtime is 4.2.0.0 logs. It seems the device error is gone, yet I still can no longer get the modbus tcp conncetion to work.<br/> Even though the logs seem to indicate that the slave (192.168.100.106) is the root of the issue, I can assure that not a single byte is crossing the wire in neither direction as I am checking via tcpdump/wireshark using display filters for mbtcp. It all worked flawlessly until 2 days ago and now I am getting the error "Connection aborted: socket_recv() failed!"</p> <p>Can somebody see from looking at the logs whats going on ? </p></div>

2021-12-08T12:06:51.450000Z2021-12-08T12:06:51.450000Zjreitzighttps://forge.codesys.com/u/jreitzig/https://forge.codesys.com93402a57abc1835444df25746912d199c5bf4a5e

<div class="markdown_content"><p>Hi. Just a fresh reinstall of the latest RPI OS. The CodeSys runtime is 4.2.0.0 logs. It seems the device error is gone, yet I still can no longer get the modbus tcp conncetion to work.<br/> Even though the logs seem to indicate that the slave (192.168.100.106) is the root of the issue, I can assure that not a single byte is crossing the wire in neither direction as I am checking via tcpdump/wireshark using display filters for mbtcp. It all worked flawlessly until 2 days ago and now I am getting the error "Connection aborted: socket_recv() failed!"</p> <p>Can somebody see from looking at the logs whats going on ? </p></div>

2021-12-07T20:44:32.302000Z2021-12-07T20:44:32.302000Zeschwellingerhttps://forge.codesys.com/u/eschwellinger/https://forge.codesys.com858d22042f164d49d4786bcdc4b44015e3548d72

<div class="markdown_content"><p>which runtime version are you using with the PI4?</p></div>

2021-12-07T20:22:11.850000Z2021-12-07T20:22:11.850000Zjreitzighttps://forge.codesys.com/u/jreitzig/https://forge.codesys.comffc483bb7a26c989fd44bfc293d167086a398587

<div class="markdown_content"><p>The error just popped up again... stuff was working fin till yesterday :-(<br/> Hardware : BCM2711<br/> Revision : c03114<br/> Serial : xxxxxxxxxxxx<br/> Model : Raspberry Pi 4 Model B Rev 1.4</p> <p>root@rasp4:~# uname -a<br/> Linux rasp4 5.10.83-v7l+ #1499 SMP Tue Dec 7 14:08:09 GMT 2021 armv7l GNU/Linux</p> <p>Any ideas ? Thx</p></div>

2020-02-27T17:21:20.375000Z2020-02-27T17:21:20.375000Zjan233321https://forge.codesys.com/u/jan233321/https://forge.codesys.com4c959f539b6fea002889edf014fc3423f0b7ee66

<div class="markdown_content"><p>Hi Edwin,<br/> I can confirm, it works.</p> <p>Thanks,</p> <p>Jan.</p></div>

2020-02-27T17:21:19.349000Z2020-02-27T17:21:19.349000Zeschwellingerhttps://forge.codesys.com/u/eschwellinger/https://forge.codesys.com487d019103e025b5b1e9de9c3ad89f1baa30cdb2

<div class="markdown_content"><p>Hi Jan,<br/> this should work now with 3.5.10.0 release.<br/> Could you please check this?<br/> BR<br/> Edwin</p></div>

2020-02-27T17:21:18.342000Z2020-02-27T17:21:18.342000Zeschwellingerhttps://forge.codesys.com/u/eschwellinger/https://forge.codesys.com12653178794364624d147a255dd37ba3ac9d6719

<div class="markdown_content"><p>Hi,<br/> we agree that this need to be fixed!<br/> This will be released with 3.5SP10 release on 15th december. (+x days for the Pi Release in the CODESYS Store)<br/> BR<br/> Edwin</p></div>