^^^ If you can turn off your extra debug switch(es) then I'd be in a better position seeing where you are at, can not make sense of that for now. But yes, I bet you have not seen any of thatproverbial purple smoke yet, and aren't you glad you tried it?

Is this further than you've been? That screen tells me the dongle has been detected by cgminer, and if the light flashes on the board, then the board is getting communication from cgminer and if the next line reads getstatus no data finish, then the board is not succeeding in communicating back (not sure why).

It is more the logic that tx on the dongle should connect to the rx on the board, but when they say pin 3 on the board is the tx, what does that mean? Is that the tx on the board or is it the pin you connect the tx from the dongle to? That is what led me to stumble upon that ..... but when I had them connected the "wrong" way, never got any blue, purple or magic smoke!

I am sure you will not get any blue smoke .... and yes, the way I discovered was just that way, flipped them when plugged in and cgminer spewing errors at me ... then voilla!

Mine dongles are red in coulor, but look very similar in size to that one.

^^^ Before you try the rPi, it may be a good idea to try and flip the tx/rx connections during the cgminer detection routine. I did the same and "discovered" that these are twisted on the CP201x dongles I got.

If it is space heaters that you REALLY want, AND you do not mind maintaining / reducing your hash-rate, you could be better served by acquiring a set of S1's, underclock & undervolt them (to output ~125 GH/s @ - and don't ask me for a link, search the forum!) and replace the fan with a couple of quieter ones in a push pull layout at full pelt, aka blue wire hack; For a tad less power for both compared to your bitfury rig, you'd be laughing!

EDIT: I am currently running a couple of bare S1 boards (neither underclocked  nor undervolted) off cgminer with a fairly loud fan blowing over them and they hold their own as space heaters! Did my laundry drying rather quickly today too, so I can vouch for a couple of these archaic beasts to do the job well.

That means you are either getting a lot more stales than before, or you have set your timeout LOW such that the "dark" HW errors are not showing up in your GUI and your "upgraded"(?)  rigs are thus submiting less shares. You could try increasing the timeout on one unit and see how that affects your earnings, else I'd press the hard reset and revert to the stock firmware. Having said that, (and this is by no means authoritative), did you ever hear of those fabled old tales about the S3 not being optimised for P2Pool, or am I mistaken?
I'll have to ask again, why on earth did you choose to "upgrade" the firmware?

EDIT: I had to say timeout set LOW rather than HIGH

500GH/s bitfury rig? How much wattage does that beast consume, bearing in mind an OC'd S3+ @ 500+ GH/s consumes ~400w?

There is NOTHING wrong. Just that you do not have your miners pointed at slush, that's all! (unless of-course there has been another disconnect between the pool front and backends).

You need to clarify (even qualify!) that statement. You SHOULD get a significant improvement either way since an S1 consumes 400 watts for ~200GH/s while an S3+ consumes as much for ~500GH/s. So the question is, what exactly do you mean by a reduction in efficiency?


It has been said in this thread and a multitude others, if it ain't broke, don't fix it!

@ CHAOSiTEC - digression from topic - look at this post https://bitcointalk.org/index.php?topic=671189.msg9538818#msg9538818, maybe you can help!

Well, it is $210 each plus shipping of approx $200 so you are getting it cheap from Amazon ma friend.
On another note, you can always buy one unit on the bitmain site, but you'll have to pay the full shipping for the two units, so I guess that is out of your plans.

My payouts for all those rounds are noticeably less than I have been getting, so the pool must have been swamped with hashing power at that time .... possibly someone pointing some rented cloud hashing-power towards the pool.
But yes, that was sweet!

I do not have any complaints, just plain dissatisfaction with the shipping cost. It seems to be a lottery as to which country is serviced better by whatever courier, however, my experience is based on using both companies to ship units from bitmain (of-course that was before shipping charges were introduced!).

DHL took exactly 3 days to deliver from order confirmation, kept me abreast of shipment progress and gave me the option to pay my taxes & fees online at the earliest opportunity, which I did ofcourse.

On the other hand UPS took 7 working days (serious, that is NOT including the weekend) to deliver, and though I kept abreast of shipment progress via their tracking, I had to do it rather than them sending me updates. And when it came to delivery, they never offered a means to pay my taxes online / before delivery, and the guy practically refused to hand over the package until their invoice was paid. I was not at home so my neighbour (who usually helps with receiving parcels) had a dilema of sorts. Long story that, but the experience left its mark.

But UPS will take 7 days to deliver, and charge exhorbitant fees on top of the tax to boot! Give me the UPS rate for DHL and I'll order today.

Shipping still too high!

All is well that ends well ...... (or something like that  )

You probably should have thought to tell OP to do that in the first place. The only strange thing that was stated is that the unit was hashing properly and then simply stopped, that is VERY strange.
I suspect OP got intoa panic, reflashed the firmware, changed to DHCP and did not apply before rebooting again (in a panic again ...?). The only reason I know of that an S3+ will refuse to start hashing is when it is on a static IP. I can not explain why that happens, but it does.

Log into the unit's web UI and change network to DHCP. Remember to apply the settings.
It may change it's address after this, but that is all you have to do.

The file may say that 218.75 is the default value, however, you definitely have 225 set as the current value.
To set the the value, do it in the GUI, ie browse to Miner Configuration then click on Advanced Settings. You'll see a drop-down where you can choose what value to run at then click Save & Apply after that.