Antminer D3 Blissz firmware (10/12 v1.12 update)

[TEmp69]

@Blissz

I really like what you have done modifiying the firmware but i have one suggestions, which i am pretty sure will ease the issue some ppl have when configuring theire miners regarding the dev fee.
I am all for it and i am pretty sure that others dont mind either that you get a fair share for your work.

I have 5 D3's myself and configuring those machines aint that easy, because each of them has different settings to be applied that the HW errors disappear.
The issue i have is, that after each reboot / configuration change (voltage, adresses, ....) you start mining on your dev pools (after some seconds), this makes it intense to check if my OWN settings are valid.

My suggestion is, please start mining your 1.5% fair share not at each and every reboot / configuration change, but once the miner has run for its 2 hours. So i am only asking you to change the first time you mine for yourself, after 2h you start with your rotation.

Thanks again.

[caymanguy]

3 $ profit that amazing 

[clyjr]

blissz,
  I have one D3 that was running pretty well at about 79 degrees on each Temp(Chip) reading for around 15 hrs, then it rebooted this morning and two chains were above 80 (81, 86) when I woke up.  It's running on Auto Silent fan mode, my understanding was that the silent mode keeps it around 80 degrees, is that incorrect?  I usually monitor the D3s ever few hours just in case, but this reboot happened overnight so it worries me a little that I might wake up with a burnt board...

[clyjr]

3 $ profit that amazing 

we get it, you hate the D3
Your posts are useless, we all understand the profit isn't great on the D3, this is why blissz is trying to help us maximize what little profit we can get, nobody wants or needs your posts about bitshit, or how bad the D3 is.  Why do you even keep coming back to post on D3 threads about how bad the D3 is, just give it a rest...

[cumbrian-miner]

Updated to v1.12

Two D3s both running on auto silent mode; about 15MH/s each; both running between 65 and 70ºC; all fans running between 2000 and 3000 revs; both running about 750w each.

One on zpool (6 blocks in 4.5 hours) and one on suprnova (0 blocks in 4 hours). Second D3 had to be rebooted after 30 mins when I noticed it wasn't hashing anything, so needed a quick restart.

I did have both pointing at zpool, but zpool seems to be down regularly. Anyone else experience this? What returns are people getting?

Tomorrow I will take delivery of some ducting to heat the house...

[lashatatu]

is it advised to increase voltage above 13? because i get hw errors on 13 on first 2 boards 3rd seems, running on 525

[blissz]

is it advised to increase voltage above 13? because i get hw errors on 13 on first 2 boards 3rd seems, running on 525

If you can keep it cool it's fine. Another approach is to decrease the frequency a bit on that board.

[lashatatu]

is it advised to increase voltage above 13? because i get hw errors on 13 on first 2 boards 3rd seems, running on 525

If you can keep it cool it's fine. Another approach is to decrease the frequency a bit on that board.

i decreased frequency and increased voltage for second board but still get around 10 hw errors in a minute and also it's the coolest one from boards

[BitAntonius]

Blissz.. when both of the dev fee pools are down you go into constant reboot mode.  Is this intended?  Seems like a bug

Thanks for reporting, I will have a look at it.

It goes to constant reboot mode when the internet connection is lost.

[Bajula]

Depends more on the heat on the chips than most things. if you look at the early posts about "performance" mode you can see you have quite the range there, though that will depend on how much wattage you can pour into it without it frying your psu or costing you more money than it's worth for the increase. - Though 525 and 13.. you "should" be able to get that at a lower voltage without hw errors, but as we have run across with these.. no board is the same. I'm guessing quality control for these was very lax - I have my own personal conspiracy theories on that

So anyway to be more specific, if your chips are sitting pretty at say 65-ish and you are running 525@13 then should be no problem at all to go up as much as you need to. *IF* your fans are set low then make that 65 higher, whatever you are comfortable with. - I don't like them even getting close to 80 personally since on every other bitmain machine that is the default emergency shutoff temp, these though seem to maybe be meant to run hotter.

[majorlee]

wow glad i found this, can give a little love to my D3's (and wallets)

[david916]

What method or product is everyone using to get precise measurements of energy usage per miner?  Is there a physical device or product people are running these through?  Thanks.

[hossamelsawy]

wow glad i found this, can give a little love to my D3's (and wallets)

which fireware did you use

[LiteMine]

@Blissz

I really like what you have done modifiying the firmware but i have one suggestions, which i am pretty sure will ease the issue some ppl have when configuring theire miners regarding the dev fee.
I am all for it and i am pretty sure that others dont mind either that you get a fair share for your work.

I have 5 D3's myself and configuring those machines aint that easy, because each of them has different settings to be applied that the HW errors disappear.
The issue i have is, that after each reboot / configuration change (voltage, adresses, ....) you start mining on your dev pools (after some seconds), this makes it intense to check if my OWN settings are valid.

My suggestion is, please start mining your 1.5% fair share not at each and every reboot / configuration change, but once the miner has run for its 2 hours. So i am only asking you to change the first time you mine for yourself, after 2h you start with your rotation.

Thanks again.

He can't set it to 2 hrs before mining to his pool or people would just reboot their miners every 1 hr 59 min and only lose 13 min per day of mining (based on a 30 sec restart), versus him mining for 22 min a day (1 min 30 sec every 2 hrs like he stated). The breakeven point is about 33 minutes, so he could set it to 20 min and people could configure miners for some time without paying any excess fees.

22 min dev mining per day / 30 sec reboot = 44 restarts/day

24 hr/day / 44 restarts/day = 0.5454 hr/restart = approx 33 min/restart

If the reboot takes 90 sec, then he could set it to 1 hr 39 min, but ppl still might restart often just to spite the dev. So he sets a short amount of time before it mines to his pool.

[deezhere]

@Blissz

I really like what you have done modifiying the firmware but i have one suggestions, which i am pretty sure will ease the issue some ppl have when configuring theire miners regarding the dev fee.
I am all for it and i am pretty sure that others dont mind either that you get a fair share for your work.

I have 5 D3's myself and configuring those machines aint that easy, because each of them has different settings to be applied that the HW errors disappear.
The issue i have is, that after each reboot / configuration change (voltage, adresses, ....) you start mining on your dev pools (after some seconds), this makes it intense to check if my OWN settings are valid.

My suggestion is, please start mining your 1.5% fair share not at each and every reboot / configuration change, but once the miner has run for its 2 hours. So i am only asking you to change the first time you mine for yourself, after 2h you start with your rotation.

Thanks again.

He can't set it to 2 hrs before mining to his pool or people would just reboot their miners every 1 hr 59 min and only lose 13 min per day of mining (based on a 30 sec restart), versus him mining for 22 min a day (1 min 30 sec every 2 hrs like he stated). The breakeven point is about 33 minutes, so he could set it to 20 min and people could configure miners for some time without paying any excess fees.

22 min dev mining per day / 30 sec reboot = 44 restarts/day

24 hr/day / 44 restarts/day = 0.5454 hr/restart = approx 33 min/restart

If the reboot takes 90 sec, then he could set it to 1 hr 39 min, but ppl still might restart often just to spite the dev. So he sets a short amount of time before it mines to his pool.

Wouldn't it be easier to just edit the hosts file of the miner to trick it into thinking the devpool address is the same as the primary pool address?

[caymanguy]

profit increase 4 dollar wow 

[david916]

@Blissz

I really like what you have done modifiying the firmware but i have one suggestions, which i am pretty sure will ease the issue some ppl have when configuring theire miners regarding the dev fee.
I am all for it and i am pretty sure that others dont mind either that you get a fair share for your work.

I have 5 D3's myself and configuring those machines aint that easy, because each of them has different settings to be applied that the HW errors disappear.
The issue i have is, that after each reboot / configuration change (voltage, adresses, ....) you start mining on your dev pools (after some seconds), this makes it intense to check if my OWN settings are valid.

My suggestion is, please start mining your 1.5% fair share not at each and every reboot / configuration change, but once the miner has run for its 2 hours. So i am only asking you to change the first time you mine for yourself, after 2h you start with your rotation.

Thanks again.

He can't set it to 2 hrs before mining to his pool or people would just reboot their miners every 1 hr 59 min and only lose 13 min per day of mining (based on a 30 sec restart), versus him mining for 22 min a day (1 min 30 sec every 2 hrs like he stated). The breakeven point is about 33 minutes, so he could set it to 20 min and people could configure miners for some time without paying any excess fees.

22 min dev mining per day / 30 sec reboot = 44 restarts/day

24 hr/day / 44 restarts/day = 0.5454 hr/restart = approx 33 min/restart

If the reboot takes 90 sec, then he could set it to 1 hr 39 min, but ppl still might restart often just to spite the dev. So he sets a short amount of time before it mines to his pool.

No.  Just no.  I'm so perplexed that this rigid mindset still exists.  If people don't want to pay, they will change the code, change the hosts file, or do something else not to pay.  Don't you people realize people who are willing to pay are requesting reasonable small changes?  How foolish to ignore them into oblivion.  This stance is a shining example of shortsightedness.  Never be penny wise and pound foolish.

Ok, I'm done on the subject of fees.  Hope you/dev/whoever sees the light on being a little more flexible.

[Wananavu99]

Off topic here, but difficulty of Dash is now at 3.41 Ph/s.  Just confirms why we need Blissz and folks like him. 

[blissz]

Thanks for all the support, I am working hard on the background to improve things. As I also do respect all your opinions I decided the following for the next versions:

• My intention is not to discourage you to change / play with the settings, so the dev mining will start after 5 minutes instead of 2 minutes. This will give you time to grab a coffee / check your settings / correct it if you see a lot of HW errors / do multiple settings at once after a restart before it starts mining on the dev pool.
• The dev fee pools are shown again in the mining status overview (light grey colored) and also in the kernel log, so everybody can check / see what's going on. If you still have questions about it, please ask friendly in this topic.

[Maicol792]

Thanks for all the support, I am working hard on the background to improve things. As I also do respect all your opinions I decided the following for the next versions:

• My intention is not to discourage changing settings, so the dev mining will start after 5 minutes instead of 2 minutes. This will give you time to grab a coffee / check your settings / correct it if you see a lot of HW errors / do multiple settings at once after a restart before it starts mining on the dev pool.
• The dev fee pools are shown again in the mining status overview (light grey colored) and also in the kernel log, so everybody can check / see what's going on. If you still have questions about it, please ask friendly in this topic.

thanks blissz ... are you working on change algo?? i think this is the first and absoluty priority!!! thanks for reply