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 problem with Codesys control shutdown. The text of the device SOS report is attached. The device (raspbian with support for Codesys) works correctly for a while and later it is no longer possible to connect to the device through the Codesys environment.
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?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I too have the same issue. After 1 or 2 days Codesys appears to lock up or freeze.
I was able to SSH into the RevPi but no matter what I did I could not stop/kill the codesyscontrol.bin process. I had to reboot the device and it was operational again.
Codesys Control for Raspberry Pi 4.5
CDS 3.5.17 Patch 4
RevPi Bridge Library 1.2.1.0
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This may be due to versioning issue - RevPi states the bridge version 1.2.1.0 is used for Codesys Raspberry Pi Control version 4.4.0.0 and the bridge version 1.3.0.0 is used for Codesys Pi Control version 4.6.0.0. I would try contacting RevPi to see if there is any known issues with this mismatch in versions or try updating the bridge or Codesys Pi Control versions. Let us know if this helps.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi, yes I am aware these are mismatched versions to what Kunbus recommend. We have also tried the latest official combination of software versions with still the same issue.
Software Combination 1 Codesys Development System 3.5.17 SP4 Codesys Control for Raspberry Pi 4.5.0.0
* Revolution Pi Bridge driver 1.2.1.0
Software Combination 2 Codesys Development System 3.5.18 SP4 Codesys Control for Raspberry Pi 4.6.0.0
* Revolution Pi Bridge driver 1.3.0.0
From what we can tell, the issue for us manifests on systems with a RevPi Connect+ and a MIO module in the chassis. All our other systems without MIO's have not exibited this issue.
I've been in contact with Kunbus and they have requested I try running the following versions, even though their documentation currently still states the versions under combination 2 above.
Suggested Combination from Kunbus Codesys Development System 3.5.19.0 Codesys Control for Raspberry Pi 4.8.0.0
* Revolution Pi Bridge driver 1.3.0.0
This combination has been working fine on our test bench for the last few days, our freezing issue has appeared anytime from a day later to 14 days later so still some time before we can assume it is resolved.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi, I'm experiencing this problem as well. Did the suggested combination resolve your issues in the end? If not, I can stop my efforts rolling back to these versions.
I'm trying to get CC for RPi 4.8.0.0 installed on the device, but I can't find it after installing it through the packet manager.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
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.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I have problem with Codesys control shutdown. The text of the device SOS report is attached. The device (raspbian with support for Codesys) works correctly for a while and later it is no longer possible to connect to the device through the Codesys environment.
Thanks for any suggestions.
Hi,
I have the same problem running codesys 4.7 on a revolution pi connect S with buster.
did you find a solution?
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?
I too have the same issue. After 1 or 2 days Codesys appears to lock up or freeze.
I was able to SSH into the RevPi but no matter what I did I could not stop/kill the codesyscontrol.bin process. I had to reboot the device and it was operational again.
Codesys Control for Raspberry Pi 4.5
CDS 3.5.17 Patch 4
RevPi Bridge Library 1.2.1.0
This may be due to versioning issue - RevPi states the bridge version 1.2.1.0 is used for Codesys Raspberry Pi Control version 4.4.0.0 and the bridge version 1.3.0.0 is used for Codesys Pi Control version 4.6.0.0. I would try contacting RevPi to see if there is any known issues with this mismatch in versions or try updating the bridge or Codesys Pi Control versions. Let us know if this helps.
Hi, yes I am aware these are mismatched versions to what Kunbus recommend. We have also tried the latest official combination of software versions with still the same issue.
Software Combination 1
Codesys Development System 3.5.17 SP4
Codesys Control for Raspberry Pi 4.5.0.0
* Revolution Pi Bridge driver 1.2.1.0
Software Combination 2
Codesys Development System 3.5.18 SP4
Codesys Control for Raspberry Pi 4.6.0.0
* Revolution Pi Bridge driver 1.3.0.0
From what we can tell, the issue for us manifests on systems with a RevPi Connect+ and a MIO module in the chassis. All our other systems without MIO's have not exibited this issue.
I've been in contact with Kunbus and they have requested I try running the following versions, even though their documentation currently still states the versions under combination 2 above.
Suggested Combination from Kunbus
Codesys Development System 3.5.19.0
Codesys Control for Raspberry Pi 4.8.0.0
* Revolution Pi Bridge driver 1.3.0.0
This combination has been working fine on our test bench for the last few days, our freezing issue has appeared anytime from a day later to 14 days later so still some time before we can assume it is resolved.
Hi, I'm experiencing this problem as well. Did the suggested combination resolve your issues in the end? If not, I can stop my efforts rolling back to these versions.
I'm trying to get CC for RPi 4.8.0.0 installed on the device, but I can't find it after installing it through the packet manager.
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.