I've started getting fans to fail and I'm worried that as the warranty lapses I will need to track down a supplier of fans.
Has anyone sourced a replacement fan? Not worried about cable length, more the CFM and static pressure specs being similiar.
I've replaced a few that have already failed with some Delta afb1212vhe that i had from gpu days to replace dead gpu fans. (i know.. i know.. overkill.. but they were "free")
The Deltas I have don't have pwm or tach, so would be nice to have those on any replacement.
Any ideas?
Also, what's the warranty on these? 3 months? or longer?
Topic: ANTMINER S4 Discussion and Support Thread - page 48. (Read 301481 times)
thanks.
No, that would be the S5 or SP20E. The S4 can apparently be made as efficient as they are by underclocking/undervolting, though.
is this the most power efficient bitcoin asic currently?
Dogie support for this product has now expired. Other staff will now service your queries in this thread. I can still be found in my own thread.
No problem. Good luck!
I have searched and read through many pages of this thread but I think it might just be easier for me to ask.
What should my voltage be if I overclock my S4's to 225M and higher? Thanks
What should my voltage be if I overclock my S4's to 225M and higher? Thanks
0725 is fine for 225, some units will also work at 0720. You can't go above 225/0725 with the PSU included with the S4, you will overload it.
I measured 117A of current from the PSU at 225/0725, and it's rated for 120A.
Thanks!
I have searched and read through many pages of this thread but I think it might just be easier for me to ask.
What should my voltage be if I overclock my S4's to 225M and higher? Thanks
What should my voltage be if I overclock my S4's to 225M and higher? Thanks
0725 is fine for 225, some units will also work at 0720. You can't go above 225/0725 with the PSU included with the S4, you will overload it.
I measured 117A of current from the PSU at 225/0725, and it's rated for 120A.
I have searched and read through many pages of this thread but I think it might just be easier for me to ask.
What should my voltage be if I overclock my S4's to 225M and higher? Thanks
What should my voltage be if I overclock my S4's to 225M and higher? Thanks
I still don't understand why you swap one from the front to the back though Smiley
Its fluid dynamics, the rear fans do most of the work overcoming the static pressure. You wouldn't see much difference to temps if you turned both front fans off, but you certainly would if you turned both rear fans off.
fluid dynamics don't apply to air the last I checked 02 is air and fluid version of O2 is H20
0_o Air is most certainly a fluid, and the fluid version of O2 is still O2 [2O].
Sorry what I really meant to say was there are no bloody dynamics in play that will extend the cables of any store bought fan to the required 45cm (soldering doesn't count) and the only option is to replace the front fans because you wont find any that will reach the controller if you connect them in the back...BUT rather than give a proper answer you decide to throw in fluid dynamics to throw off the scent of the dogie poop lets not mince words here again you missed the point of the post kinda like driving a car into a wall or rock and expecting warranty
4 pin extension cables (example).
I still don't understand why you swap one from the front to the back though Smiley
Its fluid dynamics, the rear fans do most of the work overcoming the static pressure. You wouldn't see much difference to temps if you turned both front fans off, but you certainly would if you turned both rear fans off.
fluid dynamics don't apply to air the last I checked 02 is air and fluid version of O2 is H20
0_o Air is most certainly a fluid, and the fluid version of O2 is still O2 [2O].
Sorry what I really meant to say was there are no bloody dynamics in play that will extend the cables of any store bought fan to the required 45cm (soldering doesn't count) and the only option is to replace the front fans because you wont find any that will reach the controller if you connect them in the back...BUT rather than give a proper answer you decide to throw in fluid dynamics to throw off the scent of the dogie poop lets not mince words here again you missed the point of the post kinda like driving a car into a wall or rock and expecting warranty
I still don't understand why you swap one from the front to the back though Smiley
Its fluid dynamics, the rear fans do most of the work overcoming the static pressure. You wouldn't see much difference to temps if you turned both front fans off, but you certainly would if you turned both rear fans off.
fluid dynamics don't apply to air the last I checked 02 is air and fluid version of O2 is H20
0_o Air is most certainly a fluid, and the fluid version of O2 is still O2 [2O].
OK, so it's not just me. Thanks for testing this out!
Feel free to keep mining with me on my node, BTW. P2Pool pays better than any other pool, by a small amount. If you don't want to mine with p2pool I'd suggest sticking around until you at least get 1 share, that way you'll earn something from your testing.
Feel free to keep mining with me on my node, BTW. P2Pool pays better than any other pool, by a small amount. If you don't want to mine with p2pool I'd suggest sticking around until you at least get 1 share, that way you'll earn something from your testing.
My pleasure glad I could help and thanks for figuring out that those flags don't do anything any more in the password field
I will give P2Pool a shot another time Im not concerned about a satoshi or 2...
If we saved some others from banging their heads against a wall wondering the same thing we just confirmed; that to me is priceless
OK, so it's not just me. Thanks for testing this out!
Feel free to keep mining with me on my node, BTW. P2Pool pays better than any other pool, by a small amount. If you don't want to mine with p2pool I'd suggest sticking around until you at least get 1 share, that way you'll earn something from your testing.
Feel free to keep mining with me on my node, BTW. P2Pool pays better than any other pool, by a small amount. If you don't want to mine with p2pool I'd suggest sticking around until you at least get 1 share, that way you'll earn something from your testing.
M's Miner Monitor is the best way:
You can also ssh (use putty with Windows) into the miner, type "screen -r" and then press "s" and you'll see the current settings for queue scan-time and expiry. Press ctrl+a+d to get back to command line.
Judging by your reported hashrate, you're running 8192. Try setting it to 0 or 1 with the other method I mentioned, and let's see what happens to your hashrate. After that, I'd suggest trying 218.75mhz, which seems to give me the best result now with this firmware and p2pool.
You can also ssh (use putty with Windows) into the miner, type "screen -r" and then press "s" and you'll see the current settings for queue scan-time and expiry. Press ctrl+a+d to get back to command line.
Judging by your reported hashrate, you're running 8192. Try setting it to 0 or 1 with the other method I mentioned, and let's see what happens to your hashrate. After that, I'd suggest trying 218.75mhz, which seems to give me the best result now with this firmware and p2pool.
Confirmed those flags don't do anything now in the password field
I will go in and edit the file and see what happens
Yeah, that's what I thought. They didn't work with the previous firmware either for me.
Wouldn't it be great if we had an active Bitmain employee in these threads to help out like Spondoolies does?
There is something strange with 225MHz and P2Pool I don't know what it is but the numbers speak for themselves... 218 MHz Im seeing average over 2.1T within the first 3 mins and I never saw higher than 1975 using 225MHz and the same effect using queue 0 or 1 so for some reason don't go higher than 218 for P2Pool unless you want to lose 10% of your hashrate
with queue 1 @218MHz I am seeing 2173GH/s avg after 7 mins
with queue 1 @225MHz I never see more than 1975
Note these results are only for P2Pool
In case nobody noticed, there is a new firmware for S4. Release date 29th Jan.
That's good to know. I shall upgrade to new firmware and give it a try. I had no problem with older firmware but I want to see if there is an improvement. M's Miner Monitor is the best way:
You can also ssh (use putty with Windows) into the miner, type "screen -r" and then press "s" and you'll see the current settings for queue scan-time and expiry. Press ctrl+a+d to get back to command line.
Judging by your reported hashrate, you're running 8192. Try setting it to 0 or 1 with the other method I mentioned, and let's see what happens to your hashrate. After that, I'd suggest trying 218.75mhz, which seems to give me the best result now with this firmware and p2pool.
You can also ssh (use putty with Windows) into the miner, type "screen -r" and then press "s" and you'll see the current settings for queue scan-time and expiry. Press ctrl+a+d to get back to command line.
Judging by your reported hashrate, you're running 8192. Try setting it to 0 or 1 with the other method I mentioned, and let's see what happens to your hashrate. After that, I'd suggest trying 218.75mhz, which seems to give me the best result now with this firmware and p2pool.
Confirmed those flags don't do anything now in the password field
I will go in and edit the file and see what happens
Yeah, that's what I thought. They didn't work with the previous firmware either for me.
Wouldn't it be great if we had an active Bitmain employee in these threads to help out like Spondoolies does?
M's Miner Monitor is the best way:
You can also ssh (use putty with Windows) into the miner, type "screen -r" and then press "s" and you'll see the current settings for queue scan-time and expiry. Press ctrl+a+d to get back to command line.
Judging by your reported hashrate, you're running 8192. Try setting it to 0 or 1 with the other method I mentioned, and let's see what happens to your hashrate. After that, I'd suggest trying 218.75mhz, which seems to give me the best result now with this firmware and p2pool.
You can also ssh (use putty with Windows) into the miner, type "screen -r" and then press "s" and you'll see the current settings for queue scan-time and expiry. Press ctrl+a+d to get back to command line.
Judging by your reported hashrate, you're running 8192. Try setting it to 0 or 1 with the other method I mentioned, and let's see what happens to your hashrate. After that, I'd suggest trying 218.75mhz, which seems to give me the best result now with this firmware and p2pool.
Confirmed those flags don't do anything now in the password field
I will go in and edit the file and see what happens
M's Miner Monitor is the best way:
You can also ssh (use putty with Windows) into the miner, type "screen -r" and then press "s" and you'll see the current settings for queue scan-time and expiry. Press ctrl+a+d to get back to command line.
Judging by your reported hashrate, you're running 8192. Try setting it to 0 or 1 with the other method I mentioned, and let's see what happens to your hashrate. After that, I'd suggest trying 218.75mhz, which seems to give me the best result now with this firmware and p2pool.
You can also ssh (use putty with Windows) into the miner, type "screen -r" and then press "s" and you'll see the current settings for queue scan-time and expiry. Press ctrl+a+d to get back to command line.
Judging by your reported hashrate, you're running 8192. Try setting it to 0 or 1 with the other method I mentioned, and let's see what happens to your hashrate. After that, I'd suggest trying 218.75mhz, which seems to give me the best result now with this firmware and p2pool.
I put in a difficulty of 2250 which is the same as what I use on CKPool lets see what happens now also I removed the scan-time and expiry options now the password field is just
x --queue 1
x --queue 1
I use 2250 also. Are you sure adding --queue 1 to the password field works? I tried it after you suggested it in the other firmware thread, but it never actually applied it. Was still running 8192. With this new firmware, you can change queue by editing /config/user_setting through ssh or putty. I set mine to 0 and it is persistent across power downs.
Are you running 200mhz, or overclocked?
I got the info about the extra flags from 1 of kanos posts a while ago...how are you verifying if it has applied or not? I know it used to work
I have been using those flags in the password for westhash as well with scan 1 queue 0 expiry 1I am running at 225MHz
By putting the values in the password field I am definitely getting different hashrates with queue 0 giving the highest so far, then 1, then default (nothing specified but its 8192)
Jump to: