Hi Nicolai

Nothing extraordinary. The RevPi Compact acts as a SCADA for a heating control. Real time processing is not used. The application is based on Node-RED: Temperature acquisition, communication (Modbus, M-Bus, MQTT), control some valves and pumps.

Best regards,
Michael

The Compact crashes after an uptime of several months with the following entries in /var/log/kern.log Mar 5 23:45:17 RevPi1927 kernel: [10413981.469836] piControl: piControl i/o: missed 1 cycles Mar 5 23:47:04 RevPi1927 kernel: [10414087.870235] piControl: piControl i/o: missed 13 cycles Mar 5 23:47...

I was able to reanimate the RevPi Compact: Mount the RevPi's file system using "rpiboot" . Disable the module "piConnect" in "/etc/modules". Reboot the RevPi. Switch "Max CPU clock rate" back to 1200 MHz. Enable the module "piConnect" in "/etc/m...

Hello

I have changed the setting "Max CPU clock rate" from the web interface. The RevPi Compact does not boot after this modification. Is there a way to revert this setting in the file system. I don't want to overwrite the image.

Hi Steven
Thank you for the hint. RevPiPyLoad was already disabled. Any other ideas?

Hello This hapens sporadically on a RevPi Connect as well as on a RevPi Compact: The revpi nodes (revpi single input, revpi multiple input etc.) in Node-RED remain in disconnected state after a reboot. Typically the connection is established after a manual restart of Node-RED (systemctl restart node...