I've also noticed very high HW error counts after a 24 hour run after autotune has supposedly set all the pods to their optimal clock speeds.
Autotune does not set optimal clock speeds in all cores of all Gridseeds. You've got to take the values given from autotune and lower/raise them a bit. Not all cores from my devices were set to their optimal speeds. Autotune is VERY, very good, but not perfect.
As for the rest I don't know. Don't have as many Gridseeds as you, and no problems here.
Right, I realize that, but I beg to differ. That is exactly what auto-tune IS supposed to accomplish. Optimum clock rates for each pod. Then one is supposed to 'rather left with' having to record each setting where you don't see more HW errors accumulating and set each pod manually to that specified frequency. Otherwise autotune is a waste of time IMO.
I just found the sweet spot for ALL of my pods, at least where 98% of them are still at 0 HW errors after an hour now, where before they would be up over 30 or even 50...some out the roof!
Anyway, after re-modding 6 of my original pods for 5V regulated power feed from the 12V rail, I tested each one separately and found that most of them really like running at 1163MHz! The chips settle at 492MHs to 498MHs. Pool side sees that as the same or more and some of them are peaking at over 800MHs..I"m looking at one right now that's been hovering at 790 for several minutes now...Pool side of course...My pool side total hash rate is hovering at over 14500KHs! Yeah baby!
Before it would hover at around 10 to 12MHs...oops, it just hit 15211KHs
. I see it hit over 17MHs a lot too! I want ZERO HW errors so those otherwise wasted hashes get put to good use = mo-coin!
One thing that still bugs me though is not being able to set the whole set of chips (5) to one fixed frequency. I see how one can use com in the command line to set each chip to it's own fixed frequency, so why is there not a similar com option to set all 5 together? It's simple enough to do but of course if that were totally true, I would have done it already, wouldn't I?
Anyway, you get the point. I just wanna set each pod to it's own hash rate and that's that.
They are doing wonderfully at 1163MHz though, so I might just leave it there. Still, I'd like to know how it's done....Just in case
Woofy
Pea Ess, just in case someone doesn't believe my claims....have a looksee