LEDs going alwasy ON RED, after hours working

[Projektraum]

Hello Kunbus team,

Currently I am having a weird behavior on a machine which contains a Core3 + DO + DIO +AIO after some random time (sometimes few minutes after boot-up, sometimes after 3 hours after boot-up).
As described on the title, the machine runs fine for a while. Then suddenly all Power LED on all devices goes RED (always on, not blinking) and machine stops. Unfortunately the network becomes unavailable
when such a situation occurs, making it impossible for me to connect to Core3 to check the Status Byte via PicTory webpage or to read its value via python script.

To be able to connect to the Core3 again, I have to restart the complete system. When I do that, the error is gone and all LEDs turns GREEN after the initialization phase.
I took a sos-report right after the restart, but I was not able to find anything regarding the piBridge or similar, which points out what was the cause that the LEDs turned RED.
The only thing I noticed was that the Core temperature was around 80°C. Could this be the reason why the system stops and the LEDs goes RED?

I copied manually all kern.log and daemon.log files, which I found on the device, too, just as extra resource.

Regarding my issue, I have the following questions:
a) Is there someone from Kunbus, that can maybe have a look on the sos-report? To who should I forward the link to all report files?

b) Also, when the described situation happens (All POWER LEDs going RED during the normal use), is it normal that the system becomes unavailable via network? Is it also locally unavailable, or can I connect I
keyboard and a monitor to it and use it? (Currently the system is at the costumer, what makes it really hard to attach a monitor and keyboard to the machine).

c) When the Status byte on the Core3 (or DIO, DO, AIO) changes, does it generate any new entry on the system logs? How can I access this value after it has been changed (on this scenario where the LED are RED)?
Do I have to keep reading it and storing somewhere, in order to read back the last value before a system restart?

d) What are the possible causes for such behavior from Core3, DIO, DO, AIO ? Is there something that affects all of them at same time? Or in case one is affected, all the others also go to this "error state"?

Many thanks in advance!
Nathan Nyland

[j.magnano@kunbus.com]

Dear Nathan,

Thanks for your request.

We would need the SOS Report, that we can reproduce it ourselves. Therefore we would need as much as possible information. Pls. follow the steps in the SOS Report below and send it back.
https://kunbus-gmbh.atlassian.net/servi ... 2036400208

About the very high temperature, did you install the RevPi correctly, according to the norm?
Temperature too high → DIN Rail mointing is important because of the Chimney effect
https://revolutionpi.com/tutorials/din-rail-mounting/

As well, try to update the firmware of all the expansion modules you are using currently e.g. I/O modules.
Here blow you will find the explanation
https://revolutionpi.com/tutorials/imag ... re-update/


Best Regards,

[Projektraum]

Dear Sr. Magnano,

thanks for your reply.
I just sent all information via email to the kunbus support.

In case any further action or info from my side is needed, just
contact me here via forum or email.

Best regards,
Nathan