Hello, the problem was that the 4.6.0.0 Codesys control was not compatible with S versions of the RevPi controller because of the becuase of the Compute Module 4S. For those controllers, 4.8.0.0 version must be used.
Hello, from today, I got an error when I try to open 'Tools/Update Raspberry Pi' and I got this error: There is no value with the specified name associated with this subkey. This feature worked before. I did not do any changes to Codesys installation. Codesys version is SP19.1, and CODESYS Control For Raspberry Pi 4.8.0.0
Hello, I have also came across this problem using the Revolution Pi Connect S controllers. Has anyone been able to find a solution or any workaround to this problem?
Nothing in the log: tail -f /tmp/codesyscontrol.log 2023-03-08T14:35:21Z, 0x00000002, 1, 0, 22, No retain area in bootproject of application [<app>Application</app>] 2023-03-08T14:35:21Z, 0x00000002, 1, 0, 6, Bootproject of application [<app>Application</app>] loaded 2023-03-08T14:35:21Z, 0x00000018, 1, 0, 1, Setting router <instance>0</instance> address to <address>(00b1)</address> 2023-03-08T14:35:21Z, 0x00000018, 1, 0, 1, Setting router <instance>1</instance> address to <address>(2ddc:c0a8:0bb1)</address>...
I executed the sudo /opt/codesys/bin/codesyscontrol_armv6l_raspberry.bin -d /etc/CODESYSControl.cfg command in the terminal, and got the output in the moment the PLC stoped, I don't see any irregularities: pi@TBreR2:/var/opt/codesys $ sudo /opt/codesys/bin/codesyscontrol_armv6l_raspberry.bin -d /etc/CODESYSControl.cfg CODESYS Control V3.5.17.30 for ARM-32Bit - build Feb 24 2022 Device type: 4102 id: 0x00000010 Device vendor: 3S - Smart Software Solutions GmbH Device name: CODESYS Control for Raspberry...
Hello, CODESYS version is V3.5 SP17 Patch 3 + (64 bit) The runtime version is 4.4.0.0 (raspberry, armhf)
When I restart the codesyscontrol.service it is not enough, I need to restart the whole controller for the Codesys runtime to start working again.
I edited the post, the systemctl status says the service is 'active (exited)'. The journalctl does not show any relevant informations. pi@TBreR2:~ $ sudo journalctl -u codesyscontrol.service -- Logs begin at Thu 2019-02-14 11:11:59 CET, end at Tue 2023-03-07 07:18:38 CET. -- Mar 03 00:21:22 TBreR2 systemd[1]: Starting LSB: Prepares and starts codesyscontrol... Mar 03 00:21:24 TBreR2 codesyscontrol[1531]: codesyscontrol started Mar 03 00:21:24 TBreR2 systemd[1]: Started LSB: Prepares and starts codesyscontrol....