Sure here's a screen shot of my cgminer: https://imgur.com/a/0GSDqIs

I've got four of these running at default settings pulling ~300W at the wall.

1TH/s at 100W is pretty damn good for a near silent in home miner.

So after a while of running these little machines I have an update.

I'm running on a Pi and getting exactly what was advertised, here's a cgminer screenshot: https://imgur.com/qnqb71q.

I'm on power setting 4 and am pulling roughly 78W per unit so ~1TH/s at 100W, which is pretty damn good for how quiet these things are.

I did end up changing my power supply a few weeks ago to a SeaSonic SSR-650FX which handles the load easily. Also much quieter than the bitmain AWM7 or whatever that turbo induction power supply was.

I'm not sure if I'm on the most current version of VH's cgminer, everything is running pretty well so I see no need to change it.

It looks like if I were to upgrade my cpu and run an actual computer as the controller I'd be able to squeeze a bit more hash power from these units without incurring a significant power draw. But I haven't gotten around to wiping windows off an older HP machine and doing an Ubuntu build, I might never get around to it, who knows.

I attribute this to my own laziness. I have all the stuff to make a headless rig without using my pi, I just need to put it all together and do it.

This is damn near a mirror of what I am seeing. My Pi is hardwired just because of proximity.

Good to know that someone is having a similar experience. Time to pull an old desktop out and start fiddling with it.

Thank you for the insight @DieselWeaseI

@sidehack- after careful consideration I have decided to forgo re-engineering a case. The fun part is outweighed by the cost part.

I did get those failures but that seemed as though it could be related to running on the Pi, are you running on a Pi?

The temp tester that @phillipma1975 recommended works like a charm and verified that the temps are stable.

I had never thought that the errors would be related to the temp sensor as they showed up on all units while the temp was only flashing on two of them. Earlier in the thread there is some talk about the weakest chip in the unit and I think that may be the source of the errors. After fooling with the voltage and frequency settings I had them all operating as intended. As the autotune dialed in the frequency for each unit the errors became more and more rare and when a unit would reset it would recover its hash rate in a matter of 45-60 seconds.

They'd still be running if it weren't for the damn power supply. I have these set up in my office and I'm running them off of a bitmain power supply that sounds like a hair dryer. Needless to say, the wife isn't a fan. So, I'm working out a design to remove the boards and place them into a much larger all in one contained unit that I'll put in my garage. It'll give me an excuse to upgrade my home network to a mesh, and I'll be able to extend my wifi into the garage. So, I got that going for me.

@rockmoney Thanks, I'm just glad to be mining again, if I can help...I will.

@sidehack I appreciate you leaving it up to me. As I said, there is no discernible difference between the functionality of the four units aside from the blinking lights. I targeted 600Mhz and they've all settled right around 565Mhz +/- 2hz with voltage setting 5 (440mv). KanoPool is showing me with a share rate of 3.37TH/s and a hash rate of 3.03TH/s. So, as far as I'm concerned, these units are working exactly as advertised. That said, it would be nice if the high temp warning indicators were fully functional. I'd be more than happy to ship the units back especially if it would help you out in any way moving forward. Just PM me with directions if you want to take a look at them.

I've updated cgminer to the most current version, thank you for that @vh


The temps do seem fine.


I tested the temperatures on them by pointing the laser at the heat sink through the access area where all the connections are made. I did this on each individual unit.

The leds blink before I even connect the units to the pi that I'm using as a controller. I've cycled power on the units several times. I could disconnect them and reconnect them one at a time but I don't see the point in doing that, given their behavior. Without a great depth of knowledge on the design and which components are all tied to the I²C bus, I am very hesitant to go in and touch anything for anything but testing purposes, which at this point doesn't seem necessary as the voltage adjustments appear to be functioning correctly. I am able to destabilize the units and crash them by lowering voltages.

I'll keep an eye on the temps but I don't think there is anything that is actually wrong. If it becomes an issue I may go in and probe around the areas that were named earlier.

@sidehack said it before and I agree, at this point its purely academic, given that the units are performing as expected.

This is correct.

My temperature sensor comes came in today, so I'll check for temps and update later. All four topside heat sinks are showing ~26^oC. I'll also update the cgminer to the most recent version and see if that changes anything.

Here's my current cgminer screen:

https://imgur.com/a/pZpetQg

Everything seems fine.

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.

Yes, I power-cycled the miners. I'm not an expert in mining hardware by any stretch but my line of work is electronics, specifically avionics systems. If there is known voltage/amperage/resistance at specific points that I can check for that will perhaps help in identifying the issue just let me know.

I know my way around test equipment, just not code or command line. Nine of ten times I suspect PEBKAC as well, just because I know me. I'm still hitting ~2.8T with all four I just want to make sure that I'm not causing damage to the units.

I ordered the temperature sensor that @phillipma1957 suggested so I'll have some definitive data on temps tomorrow evening.

The exhaust side is plenty cool and none of the miners seem even the slightest bit warm to the touch. If I start to notice a significant drop in performance I'll break out my meter and start probing around.

Here's what I'm working with now on voltage setting 5 and target freq set to 550Mhz: https://imgur.com/imYNFcL

The units with the flashing lights are: 10040020 & 10040022

I've restarted everything to track for the next 24 hours, as I've had some issues that need isolating.

Upon restart, 2 of the four units are flashing all three vcore adjustment indicators at me now. I read something about flashing lights being an overtemp indicator, its 71 degF in the room. The units in question seem to be hashing away with no discernible issues.  But, is this something I should worry about?

The miners also seem to be ignoring the custom frequency settings that I'm designating at startup [--gekko-r606-freq 700] yet the target freq is 550Mhz. I know that the autotune finds the optimal frequency for the chips at a given voltage so its no big deal. But if I want to push them a little harder, how do I get past that? <-- figured this out

I'm running on a raspberry pi with raspbian and the most recent version of the modified cgminer. My power supply is a Bitmain AWP7. Right now the target freq is 550Mhz, despite my inputs, 700Mhz at volt setting 3 4.

Edit: Back to 550Mhz, volt setting 5. Just had a nonce error and a retarget to 506Mhz, this is one of the two units with the flashing lights room temp is 72degF.

So after ~20 hours this is where I'm at. All but one of the miners is running on voltage setting 1 with the loner running on voltage setting 2.

They run quiet. They run cool. And the auto tune feature is really pretty awesome.

Overall, very happy with these miners. Now we just need to hit a block at KanoPool.

https://imgur.com/a/L1oowRi

I updated my other post to be more specific.

I figured its down to the chips. No big deal.


The miner in question is actually having the fewest rejects and hardware errors of the four. Weird. If there is anything else that I can provide you just let me know.

Like I said, its not a huge deal for me, I just wanted to scratch my mining itch and these are the best for that.

No worries, I just got them up and running today and I've got all four on voltage setting 5. They've all re-targeted below my 588MHz and only one of them is below 550MHz. I'll keep an eye on it for the next 12 hours or so to see if there are any changes. I'm not super concerned about it.


Its a Bitmain APW7, the fan screams right from the get go. It has a rating of 1000w at 83.3A (or at least thats what it says on the side) so I should be fine there.

I was running them at something high like 750Mhz on the highest mV setting, it was only one unit doing it and I can't really believe that it would be viable to run them like that in the long term.

Currently, I've got the freq set to 588Mhz to get me somewhere near 800GH/s. I'll slowly up the mv settings until it stabilizes.

Just trying to find the optimum settings so I can set and forget.

Well, I've got all 4 of these running. Pretty easy too, setup on a Pi just using the 4 usb ports on there until I get more of these bad boys.

@rockmoney - thank you for delivering so quickly
@vh - thank you for the support
@sidehack - thanks for making these, they are awesome

Now I just need to figure a way to either quiet my power supply or perhaps move the whole setup to the garage.

edit: why does something called "asic plateau" keep happening?

Thank you @philipma1957 and @sidehack.

Now if I can get by this "C compiler cannot create executables" can't tell difference between O and 0 error I'll be in business.

One quick question about USB hubs for the R606.

Does the hub need to be powered?

Logically, I can't see why it would need to be but just wanted to make sure before I settle on my total hardware configuration.