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

[david916]

Is there any reason people are clocking these so low?  My D3s are running >600 with temps <80.  Is there a profitability aspect I'm missing?

[1714958948]

1714958948

[1714958948]

1714958948

[1714958948]

1714958948

[1714958948]

1714958948

[1714958948]

1714958948

[clyjr]

FYI, in case some people didn't know, there are at least 2 different hardware versions of the D3.  I know because I have 2 that were both supposedly from the same late november batch, but they look different and have different brand fans.  The first I received is shorter than the 2nd one (less of the vent holes and less space between the fan and the bottom of the case), but both have the 19.3 stickers on them. 
Both of them seem to run better at voltage 11, comparison of both running on Auto Silent mode:
 #1 is running at 462 frequency  chip temps (79,77,70), no HW errors, fans 2520, 3390 -- 17,321.95 MH/S (avg)
 #2 is running at 494 frequency  chip temps (78,72,28), no HW errors, fans 2940, 3810 -- 18,498.36 MH/S (avg)

I've also experimented with quite a few frequency / voltage / manual fan speed combinations when I was running on 110v (just switched to 220v this weekend).
For example on 110V, #1 at 400 freq/ 1 voltage, 35% fans was using 745 watts, #2 at same settings was using 734 watts even with the fan running faster...

The #1 miner always runs hotter at the same frequency and always required a higher voltage to run stable.
I don't have a way to monitor wattage now that I'm 220v, but I'm going to run them for a few days on the current settings and start trying to make adjustments again.

Now, taking all of that into account, half the time if you reboot one of the D3s they run different than before, even without changing settings, these things are finicky...

[clyjr]

Is there any reason people are clocking these so low?  My D3s are running >600 with temps <80.  Is there a profitability aspect I'm missing?

before switching to 220v I didn't want to stress my 15 amp circuit and wanted some headroom for the 85 degree limit in case my garage started to heat up. 
Currently my garage is staying around 73F with an outside temp of 45F, last week outside temps were 70F+ and the garage was up to 83F.  I also want to keep the noise down as much as possible as to not piss of my neighbors or HOA.  With no current way to remove the air from my garage, I'm stuck running them a little slower.  I'll probably start ramping them up after a few days to find the best noise / fan speed / hashrate combo though.

[david916]

before switching to 220v I didn't want to stress my 15 amp circuit and wanted some headroom for the 85 degree limit in case my garage started to heat up. 
Currently my garage is staying around 73F with an outside temp of 45F, last week outside temps were 70F+ and the garage was up to 83F.  I also want to keep the noise down as much as possible as to not piss of my neighbors or HOA.  With no current way to remove the air from my garage, I'm stuck running them a little slower.  I'll probably start ramping them up after a few days to find the best noise / fan speed / hashrate combo though.

Got it, thank you!  To clarify, is there a different level of importance on the two temperature identifiers? Temp(PCB)   Temp(Chip).  In other words, my current temps are:

Temp(PCB)   Temp(Chip)
51               77
49               74
52               78

Does this mean I can ramp them up even more until the Temp(PCB) gets near 80, and I can disregard Temp(Chip)?

[mikespax]

My machine never restarts, I don't know what you're all complaining about. Anyways, I'm running it at only 14 GHs for silence. By the way, I wanted to add that there's a free monitoring software besides minera and awesome miner that works great. Dev is responsive and planning to add some control options in the future. Check it out here:

https://github.com/anselal/antminer-monitor

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

Does anyone think 80c which is the max temp on auto silent is 100% safe long term though?

[blissz]

My machine never restarts, I don't know what you're all complaining about. Anyways, I'm running it at only 14 GHs for silence. By the way, I wanted to add that there's a free monitoring software besides minera and awesome miner that works great. Dev is responsive and planning to add some control options in the future. Check it out here:

https://github.com/anselal/antminer-monitor

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

looks simple and effective. Thanks for sharing!

[bcn2048]

hi, Blissz, I'm going to flash your firmware over my D3 to try to improve its working.

I have 19,3 GHs model and first thing was to lower the frequency.  I set it to 506 Mhz where I get average 18200 GHs, the power consumption is around 1130W. I find those settings are the sweetspot regarding HW errors.

HW errors appears mostly in the second hashboard, arround 200 a day, also third hashboard is around 4 Celsius degrees hotter than first and second - can these be fixed with changing voltage  ?

I  heard from some folks, that undervolting the graphical cards for mining could harm them in longterm (if this is true at all) - do you think it is the same with asics ?  I'm mainly conserned about loosing warranty - can Bitmain obtain any info from my D3 if there are any custom firmwares (antbleed is probably history now) ?

thanks in advance for answers,

best regards to you and to the rest of community

Blissz , anybody ?

[blissz]

hi, Blissz, I'm going to flash your firmware over my D3 to try to improve its working.

I have 19,3 GHs model and first thing was to lower the frequency.  I set it to 506 Mhz where I get average 18200 GHs, the power consumption is around 1130W. I find those settings are the sweetspot regarding HW errors.

HW errors appears mostly in the second hashboard, arround 200 a day, also third hashboard is around 4 Celsius degrees hotter than first and second - can these be fixed with changing voltage  ?

I  heard from some folks, that undervolting the graphical cards for mining could harm them in longterm (if this is true at all) - do you think it is the same with asics ?  I'm mainly conserned about loosing warranty - can Bitmain obtain any info from my D3 if there are any custom firmwares (antbleed is probably history now) ?

thanks in advance for answers,

best regards to you and to the rest of community

Blissz , anybody ?

It's the opposite: Undervolting will extend the lifetime of your miner as there is less heat produced and there is less stress on all the electric components. Furthermore it will simply saves you energy / money and a complaining wife because of the noise in case you got a wife

But no kidding: what I would do in your case: set the frequency of the second hashboard a bit lower (10 -20 Mhz) compared to the other boards (a hashboard is called chain in the advanced UI). The HW errors will drop and so will the temperature of that board. The hashrate will drop slightly but it's probably worth it

[clyjr]

before switching to 220v I didn't want to stress my 15 amp circuit and wanted some headroom for the 85 degree limit in case my garage started to heat up. 
Currently my garage is staying around 73F with an outside temp of 45F, last week outside temps were 70F+ and the garage was up to 83F.  I also want to keep the noise down as much as possible as to not piss of my neighbors or HOA.  With no current way to remove the air from my garage, I'm stuck running them a little slower.  I'll probably start ramping them up after a few days to find the best noise / fan speed / hashrate combo though.

Got it, thank you!  To clarify, is there a different level of importance on the two temperature identifiers? Temp(PCB)   Temp(Chip).  In other words, my current temps are:

Temp(PCB)   Temp(Chip)
51               77
49               74
52               78

Does this mean I can ramp them up even more until the Temp(PCB) gets near 80, and I can disregard Temp(Chip)?

Unless I'm confused, the 85 degree limit is on Temp(Chip), I don't think you need to focus on the Temp(PCB) value.  Maybe someone else can chime in to verify, but I'm pretty sure that's correct.

[blissz]

...

[david916]

before switching to 220v I didn't want to stress my 15 amp circuit and wanted some headroom for the 85 degree limit in case my garage started to heat up. 
Currently my garage is staying around 73F with an outside temp of 45F, last week outside temps were 70F+ and the garage was up to 83F.  I also want to keep the noise down as much as possible as to not piss of my neighbors or HOA.  With no current way to remove the air from my garage, I'm stuck running them a little slower.  I'll probably start ramping them up after a few days to find the best noise / fan speed / hashrate combo though.

Got it, thank you!  To clarify, is there a different level of importance on the two temperature identifiers? Temp(PCB)   Temp(Chip).  In other words, my current temps are:

Temp(PCB)   Temp(Chip)
51               77
49               74
52               78

Does this mean I can ramp them up even more until the Temp(PCB) gets near 80, and I can disregard Temp(Chip)?

Unless I'm confused, the 85 degree limit is on Temp(Chip), I don't think you need to focus on the Temp(PCB) value.  Maybe someone else can chime in to verify, but I'm pretty sure that's correct.

Well that means I'm very confused, because from Bitmain's installation guide quote: "Note: The miner will stop running when the PCB temperature is over 85°C"  No note about the Temp(Chip).  Clarification from anyone who knows about this would be appreciated by all, I'm sure.

[jackfirth]

v1.12 :: 10/12 :: recommended update

Download:
https://mega.nz/#!ylJX0LCQ!8JWryI0jDhgMvPdH2mrOvybkXCtrpYtQpxu0akdxU1s

Changes 10/12:
- Improved awesome miner / other mining managers compatibility (setting the priority was not working)
- fix kernel log window height (saves you double scrolling...)
- added permanent antbleed fix (prevent remote control of your miner by bitmain ) -> for details see http://www.antbleed.com/

happy mining!

* By the way I am very close to a first test version with some new features (including autotune), but let's fix the stable version first *

good work, just updating now, thanks for the priority fix - so quickly.

what about L3+ can we get firmware for that?

[blissz]

Well that means I'm very confused, because from Bitmain's installation guide quote: "Note: The miner will stop running when the PCB temperature is over 85°C"  No note about the Temp(Chip).  Clarification from anyone who knows about this would be appreciated by all, I'm sure.

The installation guide is a bit vague then... Form what I know from code: fans will run at 100% when above 85 °C chip temps. High temperature shutdown protection is not yet build in, but would be a good feature actually.
My advice: don't run your chip temperature above 80 °C for a longer period as it will definitely harm the lifetime on long term.

[blissz]

good work, just updating now, thanks for the priority fix - so quickly.

what about L3+ can we get firmware for that?

You're welcome

regarding the L3+: I will try to get my hands on one, as I got some time to kill around the Christmas days But first I want to have a stable auto tune functionality for the D3.

[clyjr]

Yeah, looks like we were both confused.  I knew I had seen people say to try and stay 75-80 Temp(Chip), and knew the guide said 85 shutdown but thought that was the chip temp.  Either way, if blissz and others say to try and stay below 80 (Chip), then that's what I'm going to do, just means there is more shutdown overhead than I thought since the PCB is way below 80 when the chip is at 80...

before switching to 220v I didn't want to stress my 15 amp circuit and wanted some headroom for the 85 degree limit in case my garage started to heat up. 
Currently my garage is staying around 73F with an outside temp of 45F, last week outside temps were 70F+ and the garage was up to 83F.  I also want to keep the noise down as much as possible as to not piss of my neighbors or HOA.  With no current way to remove the air from my garage, I'm stuck running them a little slower.  I'll probably start ramping them up after a few days to find the best noise / fan speed / hashrate combo though.

Got it, thank you!  To clarify, is there a different level of importance on the two temperature identifiers? Temp(PCB)   Temp(Chip).  In other words, my current temps are:

Temp(PCB)   Temp(Chip)
51               77
49               74
52               78

Does this mean I can ramp them up even more until the Temp(PCB) gets near 80, and I can disregard Temp(Chip)?

Unless I'm confused, the 85 degree limit is on Temp(Chip), I don't think you need to focus on the Temp(PCB) value.  Maybe someone else can chime in to verify, but I'm pretty sure that's correct.

Well that means I'm very confused, because from Bitmain's installation guide quote: "Note: The miner will stop running when the PCB temperature is over 85°C"  No note about the Temp(Chip).  Clarification from anyone who knows about this would be appreciated by all, I'm sure.

[qctechno]

v1.12 :: 10/12 :: recommended update

Download:
https://mega.nz/#!ylJX0LCQ!8JWryI0jDhgMvPdH2mrOvybkXCtrpYtQpxu0akdxU1s

Changes 10/12:
- Improved awesome miner / other mining managers compatibility (setting the priority was not working)
- fix kernel log window height (saves you double scrolling...)
- added permanent antbleed fix (prevent remote control of your miner by bitmain ) -> for details see http://www.antbleed.com/

happy mining!

* By the way I am very close to a first test version with some new features (including autotune), but let's fix the stable version first *

You save my day ! I updated my D3 to latest firmware and 1 board failed to hash after update.
I used your hacked firmware and I was able to fine tune my problematic chain 1.
I'm running v1.11 from the last 4hrs, work strong again.

Chain 1 : 412MHz / 11 Asic Voltage   --- 1017 HW    ---  Buggy chain with Bitmain Firmware
Chain 2 : 400Mhz / 10 Asic Voltage    --- 0
Chain 3 : 400Mhz / 10 Asic Voltage    --- 0

Super appreciated.

[llanaio]

Thanks for the update. To those who suggest the dev isn't responsive, I say, what do you call new updates every few days? It's one guy working on this, making our D3s more useful for us, whether our concern is noise, heat, or max hashrate. I expect he has a life and real job too.

Blissz, thanks for the development. Awesome Miner integration is a priority for me, since that's my main administration tool. I think that people have a point that mining the devfee soon after a restart does increase the amount of devfee mining. However, I expect if you wait too long then a few people will restart their miners to prevent your fee. What about mining the devfee after 45 minutes as a happy medium? That would ensure that the miners were running and stable for owners, but probably not be worth it to them to constantly restart to avoid your fee.

[reimon85]

With latest firmware im getting more hw errors, i just lowered freq to avoid but something seems poorer that 2 versions ago firmware that i was running

[dgwayne]

Looking into modify the antminer as well. I don't mind blissz taking fees. I have basic linux file modification skills. I just want to know where they are "hardcoded". I will figure it out sooner or later

https://ibb.co/fyXHkG

[taserz]

Hi Blissz,

please can you change your fee to be mined not every i think 2 hours for minute or so, but better once per day for couple minutes? i dont like that my miner disconnect every two hours and start mining again..what you think?
- autotuning option will be great!lets say, i will set my miner fan to 25% and temperature to 75degree or so. and it will start tune each board separately..one by one.. this will be awesome really.
- what about new firmware for L3 or S9 miners?


thanks

Go in your firewall and block the pool he uses. Easy solution now it won't eve mine for him!

This is what happens when the dev is not open to people's concerns regarding the fee and even the transparency of it.  People can come on and defend the dev all they want, and nip and paw at anyone who complains, but at the end of the day, if the concerns of users are not addressed (or appear to be dismissed), things like this will happen.  I'm not endorsing this.  But it is reality.  Dev, come on, just address these concerns a little.

Just make it optional most users are to dumb to uncheck boxes anyways