leswright1977 / PySpectrometer2

The Second Incarnation of the Spectrometer project!
Apache License 2.0
228 stars 34 forks source link

Rpi4 keep restarting occasionally with PySpectrometer2 #3

Closed 68artik closed 1 year ago

68artik commented 1 year ago

Hi! I'm using active cooling with Rpi 4 4GB (the latest Bullseye clean install) while using PySpectrometer2. The temperatures are fine <60C, the CPU load max 50%. The computer does not look overloaded but the Rpi have tendency do restart (with and without the waterfall). My monitor resolution is 2560x1440. Any ideas what could be wrong?

BTW. I truly love the v2 software

68artik commented 1 year ago

update: Same situation on 4x lower pixel count 1280x800 monitor. Rpi just restarted in 5 minutes, so it is not the window scaling. Looks like something is unstable. The version 1 was rock solid

leswright1977 commented 1 year ago

That is very weird, a Python program should not be able to do that, and as you remark, although it is quite intense in terms of data processing, it is hardly hogging the CPU. Is there any indication as to why in /var/log/syslog ?

I will attempt to replicate the behaviour.

codeflight1 commented 1 year ago

What power supply are you using?

I know the Pis will restart if the voltage drops too much, which can happen if your power supply is not up to the task.

leswright1977 commented 1 year ago

This is what I am thinking it will be one of the following in order: 1) PSU 2) SD Card 3) RAM/CPU Issue 4) Something may be wrong with the new picam2 Library. It is the only thing in here that is accessing hardware.

68artik commented 1 year ago

Thank you guys. I'm using a brand new official Raspberry Pi power supply. I'll wait for a reboot and then check the syslog (just launched the PySpectrometer). It's interesting because the rebooting issue ha started since v2 introduction and that Raspberry Pi 4 is used just for the PySpectrometer. Stay in touch!

leswright1977 commented 1 year ago

It's a weird one for sure. When I made the YT video, I had the thing running for about 2 hours straight (multiple takes and all that!), with screen recorder software running and the browser open. If the issue occurs again, see what syslog says. Cheers!

68artik commented 1 year ago

I guess It was an overclocking issue!