Activity for ivanmaltar
-
ivanmaltar posted a comment on discussion Runtime 🇬🇧
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....
-
Hello, I have a few RevPi PLC controllers licensed with 'CODESYS Control for Raspberry Pi SL'. CODESYS runtime randomly stops working on the controllers - Modbus server is stops being reachable and I don't see the controllers when I scan network with CODESYS. Controllers are working properly, and they are on the network. When I check the codesyscontrol.service on the controller, it says it is active (exited). In the codesys log files, I can't see any irregularity. After I restart the controller,...
-
Hello, I am using two RevPi Connect PLCs with 'CODESYS Control for Raspberry Pi MC SL' license. The PLCs work as redundant. Redundancy license is installed on both of them, and the redundancy works fine. No and then, the problem occurs and a primary PLC switches to SIMULATION mode. On the secondary PLC an redundancy error occurs - RDCY_NOMESSAGE_ERROR and then it switches state to STANDALONE. After a few seconds, the primary PLC gets back to ACTIVE state and it resets it CODESYS runtime. In the log...
-
Hello, I have a few RevPi PLC controllers licensed with 'CODESYS Control for Raspberry Pi SL'. CODESYS runtime randomly stops working on the controllers - Modbus server is stops being reachable and I don't see the controllers when I scan network with CODESYS. Controllers are working properly, and they are on the network. When I check the codesyscontrol.service on the controller, it says it is active and running. In the codesys log files, I can't see any irregularity. After I restart the controller,...
-
Hi Stephan, the problems are CODESYS specific. Is there a way to get direct support? Specifically, I am talking about setting up redundancy. We have been through the CODESYS Help page, but that wasn't enough. Best regards
-
Hello, in my company we started the project where we use CODESYS to program PLC controllers, and we have a few of the similar projects planned in the near future. As this is the first time we are using CODESYS, we are running in a couple of beginner problems now and then. I posted a question for some of this problems, but I didn't get any answers for a couple of days. My question is: what is the best and quickest way to get support regarding development in CODESYS? Thank you for your answer.
-
Hello, I have wo RevPi Connect+ controllers (PLCs) in redundant system. One PLC must be primary (always active) and the other must be secondary (active only when primary is down). Have to ensure that the primary PLC is always active? If one PLC goes down, the other one switches to 'standalone' state, if the PLC goes up again, both PLCs will be in 'standalone' state. How to ensure that automatically the primary PLC becomes active, and the secondary passive?
-
Hello, I am trying to set up a redundant system of two PLCs, the PLCs have a Modbus TCP Slave device setup. Is it possible to synchronize the IO map od the Modbus TCP SLave on the PLCs and how?
-
I am using two RevPi COnnect+ controllers and I want to make a redundant system. For that I am using Redundancy Configuration module. When I setup everything according to the manual, PLC 1 is always in 'Simulation' redundancy state. When I try to Activate it I get an error 'Switching simulation to standalone failed'. Also I can't synchronize the PLCs: 'Synchronization failed'. The project is downloaded to both PLCs and they are in Run state.