Welcome to our new forum
All users of the legacy CODESYS Forums, please create a new account at account.codesys.com. But make sure to use the same E-Mail address as in the old Forum. Then your posts will be matched.
Close
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, everything works properly.
Did anybody else had this problem? Is there anything I can check / fix for this to stop happening?
Last edit: ivanmaltar 2023-03-07
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
which versions are involved? (Runtime and CODESYS version is always needed as additional information):
In such cases I would recommend the following:
stop the plc runtime by login by ssh to the pi(or exceute this local):
1.
sudo /etc/init.d/codesyscontrol stop
start the runtime manually by command line to have the debug output (for non multicore runtime)
cd /var/opt/codesys
sudo /opt/codesys/bin/codesyscontrol_armv6l_raspberry.bi -d /etc/CODESYSControl.cfg
in case of multicore runtime use:
cd /var/opt/codesys
sudo /opt/codesys/bin/codesyscontrol_armv7l_raspberry.bin -d /etc/CODESYSControl.cfg
open second CLI
tail -f /tmp/codesyscontrol.log
Now you should see more information why the runtime stops
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
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:
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, everything works properly.
Did anybody else had this problem? Is there anything I can check / fix for this to stop happening?
Last edit: ivanmaltar 2023-03-07
I edited the post, the systemctl status says the service is 'active (exited)'. The journalctl does not show any relevant informations.
The codesyscontrol log alwso doesn't show anything relevant. Is there something else I can check ??
Related
Talk.ru: 1
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.
which versions are involved? (Runtime and CODESYS version is always needed as additional information):
In such cases I would recommend the following:
stop the plc runtime by login by ssh to the pi(or exceute this local):
1.
sudo /etc/init.d/codesyscontrol stop
cd /var/opt/codesys
sudo /opt/codesys/bin/codesyscontrol_armv6l_raspberry.bi -d /etc/CODESYSControl.cfg
in case of multicore runtime use:
cd /var/opt/codesys
sudo /opt/codesys/bin/codesyscontrol_armv7l_raspberry.bin -d /etc/CODESYSControl.cfg
tail -f /tmp/codesyscontrol.log
Now you should see more information why the runtime stops
Hello,
CODESYS version is V3.5 SP17 Patch 3 + (64 bit)
The runtime version is 4.4.0.0 (raspberry, armhf)
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:
anything here?
/tmp/codesyscontrol.log
open second CLI
tail -f /tmp/codesyscontrol.log
while it stops?
Nothing in the log:
Now after it stopped again on its own, I tried to start it with
sudo /opt/codesys/bin/codesyscontrol_armv6l_raspberry.bin -d /etc/CODESYSControl.cfg
But it does not start. It gets stuck here:
In that moment, the tail -f /tmp/codesyscontrol.log gives the same output as before.
Hello,
We have the same issue.
Codesys control stop working at some point.
Did you find any solution ?
Hello,
We have the same issue.
Codesys control stop working at some point.
Did you find any solution ?
Hi,
look here maybe this solves it for you too.
https://forge.codesys.com/forge/talk/Runtime/thread/50aba4a915/
Hello,
We are with the version 4.8.0.0.
What can be the problem ?
Ivan
From: talk@forge.forge.codesys.com talk@forge.forge.codesys.com On Behalf Of rmaas
Sent: Thursday, August 10, 2023 4:58 PM
To: [forge:talk] Engineering@talk.forge.forge.codesys.com
Subject: [forge:talk] Codesys control service for Raspberry Pi randomly stops working
Hi,
look here maybe this solves it for you too.
https://forge.codesys.com/forge/talk/Runtime/thread/50aba4a915/
Codesys control service for Raspberry Pi randomly stops workinghttps://forge.codesys.com/forge/talk/Engineering/thread/ff9309ff19/?limit=25#447a
Sent from forge.codesys.com because you indicated interest in https://forge.codesys.com/forge/talk/Engineering/
To unsubscribe from further messages, please visit https://forge.codesys.com/auth/subscriptions/