![]() Daemons are gonna daemon regardless of the user load. Power usage at idle is usually low but even that's unpredictable. I've already got Telegraf on the RPis sending basic host metrics to an InfluxDB instance so that script just gets called by an exec input to generate and persist the data for monitoring or analysis.Įventually I'd love to write (or contribute to) a proper Golang Telegraf plug-in that just reads from the VC mailbox directly but that's still on the back burner.Īs far as actual power consumption during use, I’ve recently started running tests using a decent USB power meter (WITRN/Qway U2 and X models, in particular) to monitor load over time while running various workloads on a Pi Zero W, a Pi 3B+ and a 4GB Pi 4. ![]() To monitor the throttled bitflags, which also report thermal throttling, I wrote a basic shell script that just converts the hex to bin then returns a Grok-ready string with the flags as booleans. I haven’t found an authoritative source but generally the Pi’s power management system starts complaining (flipping the “undervolt since boot” bitflag in “vcgencmd get_throttled”) around 4.6-4.7V Several I’ve bought drop as low as 4.1V at just 2A load which will almost definitely make any Pi very unhappy. As load goes up, voltage tends to drop slowly at first, then heavily at a certain point. ![]() This can be seen pretty easily using a cheap USB DC load. RPi power consumption and power supply is a bit more complicated than it seems on the surface.Ī large problem is that even “3A rated" supplies suffer large voltage droop under load. ![]()
0 Comments
Leave a Reply. |