Cannot seem to remove D3 Blissz firmware no matter how many times we click upgrade. I would like to restore the Bitmain original firmware without the fee. Can you please advise on how to restore to the factory firmware since flashing and using the instructions in the post does not help
It probably is removed. It’s usually a browser cache issue. Hit refresh after you upgrade to the bitmain firmware. 
Topic: Antminer D3 Blissz firmware (10/12 v1.12 update) - page 37. (Read 125911 times)
Cannot seem to remove D3 Blissz firmware no matter how many times we click upgrade. I would like to restore the Bitmain original firmware without the fee. Can you please advise on how to restore to the factory firmware since flashing and using the instructions in the post does not help
Why do say everybody Mhs instead Ghs. This machine can mine with 17-20Ghs.
@Blissz
Swhat is your opinion from the expand of other algos? This will be possible?
No it wont happen The ASIC chips are made to mine x11 algos only it will never happen. @Blissz
Swhat is your opinion from the expand of other algos? This will be possible?
Why do say everybody Mhs instead Ghs. This machine can mine with 17-20Ghs.
@Blissz
Swhat is your opinion from the expand of other algos? This will be possible?
@Blissz
Swhat is your opinion from the expand of other algos? This will be possible?
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.
Did you remove the reboot code if the dev pools are down? This is something that can happen from time to time and I would prefer not having my D3s spin off into reboots.
Thanks for your hard work!
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.
Well done! Nice to see an honest person on the net .
Thanks
Just installed the 12/10 version. I was able to tweek my boards a bit better. I was able to get an extra G.
Out of my 2 machines I'm getting a total of 30.5G using under 1500w combined.
I do not want to tranfer automatic my money from account dash transfer to Jaxx every 24 hours. sorry for my english.
how to solve this help me.
how to solve this help me.
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
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.
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
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.
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.
Ok, I'm done on the subject of fees. Hope you/dev/whoever sees the light on being a little more flexible.
profit increase 4 dollar wow 
@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.
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?
@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.
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.
wow glad i found this, can give a little love to my D3's (and wallets)
which fireware did you use
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.
wow glad i found this, can give a little love to my D3's (and wallets)
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.
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.
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.
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
Jump to: