Pi-Star 4.0 rc2 CPU load higher, temps up

[N3MNT]

Just played around with this. Started Zumspot (Pi0 w/heatsink) . Did not use HT( no local activity) and logged in from computer every half hour to check temp. 1st two hours temp was 95F. approximately just after hour two temp went up to 106F.

[MW0MWZ]

From what I have seen in this thread the logging created by MMDVMHost is higher than it was - I'll have a better look into this soon.

[K0TI]

Screen shot of CPU load when MMDVM log file is about 1M. Just for information and reference. This isn't full time like this but get's pretty close to this every few seconds (depending to when TOP updates of course).

Screenshot 2019-01-29 14.26.04.png (81.17 KiB) Viewed 4155 times

[W4JCH]

Running Pi-Star 4.1.0-RC1. The ZumSpot Zero is running at 59C or 125F with no activity other than listening. Prior to going to the latest Beta temps hovered around 112F in the same spot.

[VK7HSE]

As of the 2nd of July, there's alpha testing for new firmware for the USB3 controller that will significantly reduce the idle ambient temperature. This hasn't hit the mainline stable branch just yet but it is due for release soon.

Sent from my Pixel 2 XL using Tapatalk

[KE0FHS]

Running Pi-Star 4.1.0-RC1. The ZumSpot Zero is running at 59C or 125F with no activity other than listening. Prior to going to the latest Beta temps hovered around 112F in the same spot.

Andy mentioned in another topic that he is working on an issue for release in 4.1.0-RC2 that may address the issue with the CPU getting hammered: viewtopic.php?f=3&t=1907&start=50#p8950

[VK7HSE]

But that is only going to make a difference on a Pi 4 right? Cause USB3 isn't on any of the older Pi's.

That's correct my comment only applies for the raspberry pi4 as my comment was aimed to the post before mine...

Sent from my Pixel 2 XL using Tapatalk

[W4JCH]

My PiStar 3 A+ with V4.1.0 RC1 and a ZumSpot 1.3 OLED was running hot, 59C or 125F. Last night the software was updated and now the temps are back to what they were in the V3 build or 112F or 44C.

[MW0MWZ]

I've added some quite adhesive log stripping for the MMDVMHost log;

Update and within the next hour the log strip should take place, that should keep the MMDVMHost log to a reasonable size and help get those temps back to normal-ish.
This is an ugly way to deal with the problem, but its only going to be this way until I do the dashboard make-over.

The Pi4 board is a different beast, the SoC on those runs HOT before we do ANY processing at all, I hope that will improve in time with OS updates etc.