Hi, is possible to downclock the 19.3G model to obtain max 950w at the wall?
Cheers W_M
Downclock it to 487, which is the stock value for the 17.xG version or a bit less for 950W , my stock 17.x does like 1040W, so... you can try lower, but the hashrate will also be lower. |
|
|
|
|
ROFL and I turned off my D3's, as 2 GPU rigs, at this moment, make 4 times more profit than 2 D3's
And i'm from first batch, oh well, I got two nice heaters!
Just not worth it
EDIT, they make that profit, for like... 60% of the wattage
|
|
|
|
|
Checked your vid and other vids on the D3,
And unfortunately I have to agree with you, X11 is doomed, not sure why they did it this way, S9's are still profitable (although they had bad months too, like very bad ones), L3+'s are as well , but D3... they just spammed everything, it like they want to "kill X11" by overloading it with hashrate.
At this moment I'd stay away from X11 (I have 2 of them from the first batch, and I regret it, really, the ROI will be like never), and i'm not even converting back to BTC.
The only way for this to keep being profitable, IMHO, would be if all X11 coins went up in value like 8x, but yet again, baikals will be right around the corner, innosillicon will deliver their A5's, and we still have the iBelinks.
The future is really looking grim for X11.
But the main problem is also the increase of miner speeds , it was insane, totally insane!
|
|
|
|
Anyone else get emails from Bitmain on products already shipped and delivered?
Got a couple emails dated today...on equip and psu I got last month...(go figure?)
Anyway, as a 'thought experiment', what would/could you do if they sent you them again?
I heard in USA, you are not responsible for 'unpaid' equip arriving on your doorstep you did not order'
Anyone else but bitmain (evil) I'd just send it back...them...er ....conflicted....
Anyway, thoughts or clarity on any of the above
I guess this is kinda 'off topic' unless they send me duplicate orders......then it would be WAY on topic indeed
Anyway, thought it was weird as heck.....
Yep, got exactly the same mail, with the very same invoices as the previous ones, I think that if they send duplicate orders, i'll laugh my ass out! |
|
|
|
WRote a small script in php to check your D3's and reboot them automatically in case an hashboard has errors https://gist.github.com/tperalta82/6e11253cd4b9cf9c5c6fa15bbf046d4fput this in a linux server as a cronjob, change the $hosts array, to add your hosts. There are 3 different methods to call reboot on the miner, personally, the wget one is better for me, because it runs everywhere (embedded devices) Had an issue with curl, seems to fail to authetnicate on some weird cases and ssh lib is not present everywhere. Read the code first, understand it, redistribute it, improve it, do whatever you want with it. P.S.: it works for me |
|
|
|
WRote a small script in php to check your D3's and reboot them automatically in case an hashboard has errors https://gist.github.com/tperalta82/6e11253cd4b9cf9c5c6fa15bbf046d4fput this in a linux server as a cronjob, change the $hosts array, to add your arrays. There are 3 different methods to call reboot on the miner, personally, the wget one is better for me, because it runs everywhere (embedded devices) Had an issue with curl, seems to fail to authetnicate on some weird cases and ssh lib is not present everywhere. Read the code first, understand it, redistribute it, improve it, do whatever you want with it. P.S.: it works for me |
|
|
|
And i'm still having issues, i'm on EU pool, switching to backup US pool, and then it goes to another pool as a third backup and works, only this pool is giving me issues  |
|
|
|
|
Hey there, both of my miners usually have issues with your pool
Oct 7 17:55:09 (none) local0.warn cgminer[19937]: Pool 0 stratum+tcp://stratum-us.granatgas-pool.info:1111 not responding!
, this is one of them, i only have this with you, any ideas?
|
|
|
|
The software is looking at the wrong pointer for the info from the hardware. You need to supply the proper info for the software, probably in the config file and then restart the whole thing, that will solve the problem. It is not a big deal and only takes a minute of two.
The data is hardcoded into the miner when it's built, you can probably check the cgminer from ckolivas and check the antminers headers there (although D3 is not there) So the software is not getting wrong pointers, it's just badly made, like whenever there is a connection error to one of the pools, the PIC temperature error is thrown, because the ASIC's are kind of reset or something, and even the fans spin up for no reason, bad coding. Or if there is no work from the pool (can happen), same things happen. Just check the kernel log and you'll find this pattern |
|
|
|
|
Hey everyone,
Is it possible to mine a specific coin?
Let's say, CANN, I know it's x11, but I see no specific port for CANN anywhere, would the url be like cann-x11?
Thanks in advance
|
|
|
|
i am also having this issue, does new firmware packed in tar.gz i have to upload via webgui ?, does this new firmware helped others ?
Mine are much more stable lately. And yes, you have to upload via webgui and the firmware is packed on tar.gz |
|
|
|
Great input, I also tested with 7 different PSU's, same results, as for the controller, I switched the boards around on the controller, and in my case, the same board has errors along the controller ports. A thing i noted, is that whenever the pool stops responding, those errors just come up, and then when it starts receiving back jobs, everything comes back to normal (just not the HW Errors part of course), this happens like 100% of the times so far. So i'd say it's a software bug mixed with hardware issues. Also, then the pool stops responding, the fans spin up to their max (bad software design i'd say). Also tried to underclock to under 15GH/s values, same issues happen. As for the networking part, well, I have other things running on the network for months now with no issues... so I cut that one out Let's wait and see what bitmain does about this Hi Guys, Just a quick followup, I've had a chance to so some more testing with 5 D3's and did the following: 1) Tested with a single APW3++ PSU on a 230V mains source 2) Tested with a 3600 Watts single rail PSU (Lab testbench PSU, so not a converted server PSU or PC PSU) 3) Tested with a power conditioner (used in high end audio setups) 4) Flashed the latest available firmware from: https://s3.cn-north-1.amazonaws.com.cn/shop-bitmain/download/Antminer-D3-201709131713-0M.tar.gz5) Hard wire connection to a Cisco 24Port managed switch (tested on different ports with different cables) 6) Set the mining pool to Antpool 7) Inspected the hashbords of a single D3 for damaged solder points powerlanes etc, loose/missing heatsinks -> All looked fine. Results: - All of the D3's had the random error mode red led warning flash - All of the D3's had the random (The red led is in sync with this message) " read_temp_func: can't read all sensor's temperature, close PIC and need reboot!!!" message in the kernel log's. - All of the D3's had the occasional "all x'es" on 1 or 2 hashbords, and returning to normal after a "reboot" This seems to be what most of the contributors to this thread experienced as well. - So it seems that it's not related to the stability of the used power supply. - Chances that each D3 (at least in the case of the posters in this thread, that have several D3's that exhibit the exact same behavior) has 1 or 2 malfunctioning hashbords seems unlikely, and I assume that Bitmain would notice this with their Quality Assurance tests. That kind of leaves me with: - Software bugs - Controller (board) bugs What I still want to test: - Is the behavior the same when disconnecting 1 or 2 hashboards. I'm hoping that Bitmain is able to sort this out with a firmware update (if it's indeed a software problem), however... They might not be inclined to do so since the rapid increase in Dash difficulty might make this an uninteresting investment. |
|
|
|
same here, underclocked to 438, and always Errors on both of them
At what temperature is yours running? now testing with freq 425, both 9hours stable, Chain# ASIC# Frequency MH/S(RT) HW Temp(PCB) Temp(Chip) 1 60 425 4965.46 0 53 68 1 60 425 4991.61 0 51 65 1 60 425 5035.19 0 52 65 original and new apw3++ PSU from Bitmain yeah it seems they probably clocked it too high |
|
|
|
same here, underclocked to 438, and always Errors on both of them
At what temperature is yours running? |
|
|
|
|
This may or not make sense, I underclocked to 456M was still having HW Errors, then I switched the blade to the empty controller connector, and so far 10 minutes without errors (i was having them after 2m , mostly 5)
Thanks tomi_maroni for the underclock idea.
Try it and see if it works for you
EDIT: After I pressed post, here comes the error... FML
|
|
|
|
ok, i think i got the solution, i had same issue, i had my miners connected to internet through powerline (internet over power) but after i connected them directly to router and since then they run nonstop without issues....
Try to put your miners to run directly to router, and check if they ll get same XXXXX issue again, im pretty sure the powerline adaptors cause this issue
Mine is connected to a switch directly, which in turn is connected to the router, directly as well. 2 D3's, one with the issue, another without, I can only think it's hardware now |
|
|
|
Perhaps not enough power, that is the sound of it, maybe. You need the log files to see where the issue is. Before coming here, check those because that will tell you what the deal is and you will probably not even need advice after that because it is very straight forward
Already switched PSU, and still the same, and it's only happening on one (in my case), and the PSU i switched is working perfectly on another rig |
|
|
|
I'm having exactly the same issue, but mine causes mostly HW errors, will try to leave it on just DASH instead of zpool which is constantly jumping in/out of different coins, as such, difficulty changes and causes this EDIT: Even with Dash only it happens, but less because it's only 1 coin, this will probably be fixed in a firmware update , HOPEFULLY |
|
|
|
|
An interesting one as well, do any of you guys have a blade constantly running hotter than the others, like 8degress?
Chain# ASIC# Frequency MH/S(RT) HW Temp(PCB) Temp(Chip) ASIC status
1 60 487 5646.18 0 53 65 oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooo
2 60 487 5637.95 0 51 65 oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooo
3 60 487 5718.85 0 58 73 oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooo
EDIT: And I only get HW Errors on the same blade , switched PSU, same...
Until my proper PSU arrives, i'm running a 3 PSU setup, one per blade, the PSU's were fine, as they were running on GPU rigs..., this is getting me frustrated.
|
|
|
|
|
Show Posts
