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.
Topic: Antminer D3 Blissz firmware (10/12 v1.12 update) - page 38. (Read 125923 times)
If you can keep it cool it's fine. Another approach is to decrease the frequency a bit on that board.
is it advised to increase voltage above 13? because i get hw errors on 13 on first 2 boards 3rd seems, running on 525
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...
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...
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...
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...
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...
3 $ profit that amazing
@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.
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.
Hi there,
I am running v1.1, thanks for your good job.
The only problem I found at the moment is - very late delay between the ASIC became "xxx xxxx" and miner restart. The restart has been executed only after 5 hours of the XXX XXX appearing on problematic chain
some inputs for analysis of such delayed restart:
1. The problematic chain is showing No. of ASICs = 60 (looks all healthy :-)
2. The problematic chain showing around 4000 HW errors and all XXXXXXXXXXXX
3. The true hashing speed is around 1/2 of normal one
All this information from miner management console. After auto- restart all correct... yet. I just lower frequency of the problematic chain a bit.
So on this status of clear needs to restart miner due to trouble with one chain (xxx , low hashrate) - the automatic restart has been done only after 5 hours
(Probably you should initiate restart of miner in 1 minute after the number of XXXXXXXXX has exceeded, let's say 10? I know some people are modifying stock firmware
in such way and it works well. From my practice if D3 chain is starting collect XXXXXXXXX, this chain very soon becomes obsolete and restart is a must.
Just IMHO.
Waiting for reply and patched version!
Good luck!
hi what is the best diff setting for the D3?
I would like to know that too.
hi what is the best diff setting for the D3?
Blissz, can you focus on D3 but not L3+ nor S9? Those two are making good money, but D3 is different, please?
Don't worry, main focus will be on D3 as indeed it needs the help the most
Hi I have a D3 on zpool with stock firmware. My hash rate fluctates, is this normal? Will this custom firmware help?
http://zpool.ca/?address=13tu1TeLmuDwJGgHnWPNxkH58QfZQUYng8
http://zpool.ca/?address=13tu1TeLmuDwJGgHnWPNxkH58QfZQUYng8
This is normal as luck is the random factor how many shares you will find. The custom firmware helps for a lot things, but not for the fluctuating hashrate. If you want it a bit more stable you can try to decrease the difficulty manually by setting "d=8" as password.
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.
Hi I have a D3 on zpool with stock firmware. My hash rate fluctates, is this normal? Will this custom firmware help?
http://zpool.ca/?address=13tu1TeLmuDwJGgHnWPNxkH58QfZQUYng8
http://zpool.ca/?address=13tu1TeLmuDwJGgHnWPNxkH58QfZQUYng8
Doe it matter if I get hundreds of HW, but 1 reject?
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
*
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
*Blissz.. when both of the dev fee pools are down you go into constant reboot mode. Is this intended? Seems like a bug
People. I keep wondering here.
I have already tested all methods to readjust this CHAIN # 1, but in all configurations it shows a high volume of HW error, I keep wondering.
Can I continue to use it this way and try to put a low temperature on this board?
It is because it will not be worth much I send it back to Bitmain, the loss of having bought it is already great, to send I will have to spend more money, in the end will only increase the loss ...
Could it be that with these errors, or trying to make a better readjustment possible, can I keep it going for a long time?
CHAIN #1 ~~~ HW ERRO :: https://i.imgur.com/MTAEmo6.png
WHAT DO YOU RECOMMEND TO ME
I have already tested all methods to readjust this CHAIN # 1, but in all configurations it shows a high volume of HW error, I keep wondering.
Can I continue to use it this way and try to put a low temperature on this board?
It is because it will not be worth much I send it back to Bitmain, the loss of having bought it is already great, to send I will have to spend more money, in the end will only increase the loss ...
Could it be that with these errors, or trying to make a better readjustment possible, can I keep it going for a long time?
CHAIN #1 ~~~ HW ERRO :: https://i.imgur.com/MTAEmo6.png
WHAT DO YOU RECOMMEND TO ME
Hello, my miner has been like this and after a few seconds everything goes to "X".
Can anyone tell me what to do?
https://i.imgur.com/KNPutSz.png
Can anyone tell me what to do?
https://i.imgur.com/KNPutSz.png
See if the information here helps : https://support.bitmain.com/hc/en-us/articles/220872007-Possible-problems-for-Antminer-Troubleshooting-for-S7-S9-L3-
This machine has the 3 defective plates.
There will be no other way to get her back to Bitmain, but their support is horrible in every way, they do not give a hand to this dung machine.
Hello, my miner has been like this and after a few seconds everything goes to "X".
Can anyone tell me what to do?
https://i.imgur.com/KNPutSz.png
Can anyone tell me what to do?
https://i.imgur.com/KNPutSz.png
See if the information here helps : https://support.bitmain.com/hc/en-us/articles/220872007-Possible-problems-for-Antminer-Troubleshooting-for-S7-S9-L3-
Chain# ASIC# Frequency GH/S(RT) HW Temp(PCB) Temp(Chip) ASIC status
1 60 537 6583.55 6 53 73 oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooo
2 60 537 6291.02 753 51 69 oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooo
3 where is chani 3
in other mines show 3 Chain#
1 60 537 6583.55 6 53 73 oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooo
2 60 537 6291.02 753 51 69 oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooo
3 where is chani 3
in other mines show 3 Chain#
Try with lower frequency 537 is to much, don´t know why bitmain do it, but there are to much HW-Errors and the Miner get mostime to hot, too
When you run the Miner with 220-240V then try 506
with 120V try something around 450
can't help but throw this in again, doesn't matter if you are 240 or 120 it matters what your psu can do without strain. *IF* you are using an old server psu where at 220 it is producing 1200w and at 110 it is producing 900 w THAT will make a difference - but if you have a 1500w psu that can run on either, then 1500 is the max you are looking at.. the 220 vs 110 is only going to change the amps going *IN* to the psu (less heat on your cord or ability to use a smaller cord maybe less strain on the psu in the way of heat) but that will in no way affect what setting you can put on the miner itself, from the psu out 12v at whatever amps is going to be 12v at whatever amps.. doesn't matter AT ALL if it is 110 or 220 coming in. - thickness of the individual wires in the 6-pin makes a difference, the amps your psu can handle on it's 12v rail makes a difference.. but the miner doesn't care at all. not even the tiniest bit- if you have issues at 120v with 537 then either you have a miner with issues (plenty of them out there) or you need a better psu.
When i wrote it, i have the orig. Bitmain PSU in mind, and this is to small on 120V with frequency 537
I have strange problem
after 4 hours it gives me xxxxxxxxxxxxxxx again
so do I need to decrease the frequency as i have 537 with 220 v
please anyone help
yeah decrease the freq, or increase the voltage -on the chain with the firmware but is has NOTHING to do with incoming voltage. did you even read what you replied to? or do you just disagree? If the chain dies at a certain freq or beyond, do you really not see that you need to adjust something? At least you didn't say "I set myself on fire should I put it out?" Wait you were messing with me right?
Jump to: