Quote from: kingofhammers on May 11, 2019, 04:37:37 AM

What would be the best way to test for correct voltage settings, a test point to check or a particular pin?

If the fault is on the I²C bus where should I test and what logic (high/low) should I be looking for?

I'm going to do another power down, would you recommend a specific voltage setting before doing so?

Again, these units are hashing away as expected, just have a few more blinky lights.

Have you tried running only 2 or 3 units at once to isolate a potential power insufficiency (or possible limitation of pi), and/or data/throughput jam?

Sounds like a lack of power or communication jam, especially when using AsicBoost. I would try running the two units with the flashing lights by themselves, and see if that helps.

Not very familiar with raspberry pi, but ~400 Watts+ seems like a big ask?

Quote from: House Xylander on May 11, 2019, 05:25:06 AM

Added the --gekko-noboost setting for btc.viabtc.com and it seems to be working. no crashes so far after 20 minutes.

I set the target freq of the R606 as 600. It has run over an hour and changed the target to 368 and then 15 minutes later changed again down to 362 which result in about 460gh. I have the R606 set to 450mv (setting 6) should I move it up to 7 or down to another setting to reach stock 750gh.

Move it up to 7! Wink

@kano - I currently have four R606 miners on your pool, all with R606 in their worker names. My newest one is averaging 1.10Th/s on the pool if you want to grab some stats. I'm back in PA now btw, and two additional R606 miners will be online soon! Wink