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

[blissz]

L3+ support came a bit earlier then expected:

https://bitcointalk.org/index.php?topic=2694602.0

please report your L3+ results in the L3+ thread. Thank you! 

[sanitariu]

Quote from: sanitariu on Today at 08:41:30 AM
Obagam these spikes are because each 2 hours we have dev fee switching. I proposed solution. Option checkbox to mine
the whole devfee at the start for 24 hours.
It was originally done at the start, it was changed because everyone hated it and wanted the 2hr thing instead.

I meant devfee for the whole day  ! You got me wrong.
My idea is start miner then it starts devfee pool for 30 minutes, then switches to my pools for 23 hours and 30 minutes.
Even starting the whole devfee after 2 hours is okay too. Like D3 starts working 2 hours then mine 30 minutes for devfee then
no interruptions in the next 23 hours and 30 minutes.....
My pools are perfectly fine. No interruptions at all. I dig on my own pool

[atraer]

hard mod information (depricated)

UPDATE 16/11/2017: I successfully modded the firmware which will add unlocked voltage and fan control, so I advice NOT to hardware mod and see how far you can go with the firmware mod. If you want to undervolt more I advice the hard mod.

https://preview.ibb.co/jmOdDG/20171031_171454.jpg


Hardmod info

The antminer D3
As an owner of the October batch of the antminer D3 I have good news. I now run my antminer D3 stable @ 15Gh/s with just 750 watts.  
I decided to go for a mod, because I couldn't run the fans at full speed because of the noise. Therefore I could only run 13 Mh/s @ 850 watts before the mod, which is now not very profitable.

The mod:
To get there I tried to reverse engineer the power circuit of the antminer D3 mining boards. Unfortunately there is some chip which I still don't know the specs from (labeled ADP BDY+), but I found out it's controlling the PWM of the mosfets.
So I tried changing the resistors around it and found out that changing the resistor R80 controls the voltage. Woop Woop
So if you want to do the mod I advice to replace R80 by a 25k ohm potentiometer. The voltage can be measured over C948

Improvement:
without the mod the total voltage supplied to the asic chips is fixed @ 8.15v on the October batch. That means 1300 watts for 19Gh/s
After the mod the voltage is fully adjustable by using the potentiometer. It also allows to increase the voltage for overclocking if you want to do so.
But overclocking is not my goal, I wanted a silent miner: Therefore I now run my boards @ 7.1v @ 430 Mhz stable. That means 750 Watts for 15Gh/s
That is 50 instead of 68 watt per Gh/s  

Photos
The mod is quite easy if you have some proper soldering skills, but it's tricky if you don't have the proper tools / not have a steady hand...

https://preview.ibb.co/cYmyDG/20171031_163632.jpg
upload gifs online

ps. I will make new higher res zoomed pics soon.


Other possible mods:

Fan mod: (only when undervolting)
as I don't like that noise at all I also did some fan mods. I added a voltage regulator on one of the fans to decrease the noise during startup. cgminer won't allow you to go bellow 5000rpm othwerwise the miner fails to start.
 Furthermore I replaced the second fan with a 2000rpm silent fan. To make this work you have to use the yellow wire (fan rpm) from the first fan as wire for the 2nd fan. Otherwise it detects a too low fan speed on the second fan.
I can say that running both fans @ 2000 rpm is acceptable to run it in a living room now.

Power supply mod: (only when undervolting)
By default the power supply runs @ 12.2v. I used the potentiometer inside to make it run @ 12.05v. This saves a few watts of power as well. Furthermore I added a regulator on the fan, to run it at 5v as this  small fans makes an annoying high frequency noise when running at full speed.


Support
I hope this information does inspire you and help you improve the efficiency on the antminer D3. I hope to improve the mod: as I want to look into a software mod to enable changing the voltage from software. This would really open up the possibilities for all the users.
To get there I still look for a copy of the November miner firmware as bitmain is not supplying this yet. If one can login using ssh and make a full copy of the all the files that would be really welcome.

Hi Blissz, You could show a detail of the connection of the fans, thanks.

[Ppot]

Has someone managed to connect  D3-firmware Bliss through SFTP? It always fails me.

[philipma1957]

Obagam these spikes are because each 2 hours we have dev fee switching. I proposed solution. Option checkbox to mine
the whole devfee at the start for 24 hours. This way blissz will take his part and we will have stable hashing on a good pool.
I already setup the best of my miner and they are running without stop. I just forgot them for days.....

this seems like it would work

[obagam]

Obagam these spikes are because each 2 hours we have dev fee switching. I proposed solution. Option checkbox to mine
the whole devfee at the start for 24 hours. This way blissz will take his part and we will have stable hashing on a good pool.
I already setup the best of my miner and they are running without stop. I just forgot them for days.....

this seems like it would work

Agreed

[blissz]

Agreed

The spikes come from the high difficulty of the the work packages, but adding an option for once a day devfee mining option I will take into consideration

[blissz]

v2.06 beta :: 05/01 :: test version

Download:
https://mega.nz/#!mxwhmCZb!8Xsj5c2bfvuaK_fSI2av3zrqv3dFz-w3AoSt7W-MD8U

Changes 05/01:
- more stable autotune / reset of ASIC chains (HW errors will be reset to zero after changing a board's frequency)
- ~15 to 20 seconds faster startup of the miner after changing a setting
- optimized cgminer binary size
- fixed browser caching issue when changing between stock and blissz firmware

Changes 22/12:
- reboots the D3 on high temperatures (> 85 deg PCB temp). This feature will save your unit in case your fans will fail.
- improved auto tune algorithm stability
- Increased the chip starting frequency of the autotune algorithm for higher voltages.

Changes 14/12:
- fixed auto recover from xxxx
- cleaned up kernel logging
- a bit more aggressive tuning
- tunes down faster now when too many HW errors are detected


Changes 13/12:
- Totally rewritten code base, based from latest available bitmain / cgminer sources
- ASIC's now automatically recovers from xxxxx errors without restarting (The auto reboot options are still in there in case it doesn't succeed)
- blazing fast mining status overview in the webinterface
- as requested: the dev mining starts later now (after 5 minutes)
- as requested: dev pools status is now visible in the miner status


Important: The autotune feature is not completely finished and the startup is a bit slow now.. Therefore I need your help. So what do you need to do:

set your advanced settings the same as displayed bellow
let it run for at least 20 minutes
PM your (complete) kernel log, or if it doesn't fit, focus on the last part
By doing so I can get to a conclusion what the starting frequency of the auto tune algorithm should be.
In case you want to help more: increase the voltage a bit and do the steps above again as it will give some more information

Thank you!

[mikespax]

If anybody would like to sell their D3 please message me.

[stugots2]

does anyone else have D3 blades crapping out left and right???  (even ones NOT modded)

[ewil]

v2.06 beta :: 05/01 :: test version

Download:
https://mega.nz/#!mxwhmCZb!8Xsj5c2bfvuaK_fSI2av3zrqv3dFz-w3AoSt7W-MD8U

Changes 05/01:
- more stable autotune / reset of ASIC chains (HW errors will be reset to zero after changing a board's frequency)
- ~15 to 20 seconds faster startup of the miner after changing a setting
- optimized cgminer binary size
- fixed browser caching issue when changing between stock and blissz firmware

Changes 22/12:
- reboots the D3 on high temperatures (> 85 deg PCB temp). This feature will save your unit in case your fans will fail.
- improved auto tune algorithm stability
- Increased the chip starting frequency of the autotune algorithm for higher voltages.

Changes 14/12:
- fixed auto recover from xxxx
- cleaned up kernel logging
- a bit more aggressive tuning
- tunes down faster now when too many HW errors are detected


Changes 13/12:
- Totally rewritten code base, based from latest available bitmain / cgminer sources
- ASIC's now automatically recovers from xxxxx errors without restarting (The auto reboot options are still in there in case it doesn't succeed)
- blazing fast mining status overview in the webinterface
- as requested: the dev mining starts later now (after 5 minutes)
- as requested: dev pools status is now visible in the miner status


Important: The autotune feature is not completely finished and the startup is a bit slow now.. Therefore I need your help. So what do you need to do:

set your advanced settings the same as displayed bellow
let it run for at least 20 minutes
PM your (complete) kernel log, or if it doesn't fit, focus on the last part
By doing so I can get to a conclusion what the starting frequency of the auto tune algorithm should be.
In case you want to help more: increase the voltage a bit and do the steps above again as it will give some more information

Thank you!

https://img15.hostingpics.net/pics/453940Untitled.jpg

Blissz, have you gotten my PM's or noted my posts? I'm having some issues, but would like to submit the kernel logs to you and the PMs have a text limit size.

[ewil]

does anyone else have D3 blades crapping out left and right???  (even ones NOT modded)

Having problems over here. A few un-modded ones are having issues with their boards. Glad we're still in warranty for them.

[blissz]

does anyone else have D3 blades crapping out left and right???  (even ones NOT modded)

Having problems over here. A few un-modded ones are having issues with their boards. Glad we're still in warranty for them.

Have to say the D3 boards are not so stable quality wise. I am quite lucky with mine, but quite a lot of D3 boards (partly) fail after a while.
 I do think the custom firmware helps to improve the lifetime when you run them at a lower voltage / lower temperatures.

by the way  you got a PM now

[ollieskats]

Obagam these spikes are because each 2 hours we have dev fee switching. I proposed solution. Option checkbox to mine
the whole devfee at the start for 24 hours. This way blissz will take his part and we will have stable hashing on a good pool.
I already setup the best of my miner and they are running without stop. I just forgot them for days.....

this seems like it would work

Agreed

agree make it mine your dev fee all at once after 5 min or so, i bet everyone must think the same.

[ollieskats]

Also could it be possible to put the asic voltage show on the miner status, would save me a lot of time when im setting the machines, thanks.

[Brubittrader]

Also could it be possible to put the asic voltage show on the miner status, would save me a lot of time when im setting the machines, thanks.

+1!

[Arhgus]

++ Thank 

[vschekin]

Have an issue with several miners - when blade connected to 4th connector - Hashrate decreased to 2.2-2.3 GH per blade
https://yadi.sk/i/abCxiksm3RFidN
2.04 and 2.06 firmware tested
1.12 works correct:
https://yadi.sk/d/-dF5iKyc3RFizz

[dlezama]

I was using v1.11 and my miner rebooted every few hours, but both checkboxes for automatic reboot are unchecked. HW errors were reasonable, but a chain would go XXXX sometimes and I had to restart the miner.

Yesterday I upgraded to v1.12 keeping same configuration and it has behaved perfectly for 15 hours: 0 HW errors, no reboots. I see nothing in the release notes for v1.12 that explains it, maybe it's just a coincidence? (These machines tend to wake up with a different mood every time).

@blissz Any changes between these two versions that can explain this?

[blissz]

Have an issue with several miners - when blade connected to 4th connector - Hashrate decreased to 2.2-2.3 GH per blade

2.04 and 2.06 firmware tested
1.12 works correct:

Hi, thanks for pointing this out on the beta version. I do advice to always connect your chains to 1,2 and 3 and leave connection 4 unconnected, but I will have a look if I can make it compatible if you don't connect it correct.