use min 100cfm and ~3000 rpm (pwm). But I suggest to use 2 fan. One is connected to the miner and regulated with pwm mode.
Other is placed on opposite side, soaking air out and powered direct from PDU molex at highest speed (its silent so it wont be so laud).
Or you can power them both at higest speed and from PDU, no need of connecting to the miner fan connector and pwm regulation.
Topic: [Setup & Troubleshoot] Bitmain AntMiner S1 180GH/S miner - page 147. (Read 452359 times)
any idea whats the CFM of the fan ?
i want to replace them with some silent ones, but need to know the CFM, anyone knows ?
Ok, well, I guess I found the source of the problem - the left side (aka blade #2) on that unit is bad. I had the unit on by itself on the same PSU as the fully working unit. Yes I did disconnect the other unit entirely. The faulty unit was all by its lonesome. Left the miner cool for a few minutes, powered it on - the same xxxxx on the second module. I tried powering just the faulty blade alone, but I guess the first blade needs to be one as it seems the controller board is fed through it so the unit will not power on fully without the "master" blade.
ASIC# says 16 for the faulty blade, so half of the chips are not functional, although if you go by counting x's and o's more than half are throwing errors or non functional.
xxxxxoxo xoxoxoxo xxxxxxxx xxxxxxxx
Swapping the PSU at this stage would be a pointless exercise.
so you are running a single antminer on what PSU? (brand, model, wattage, etc)ASIC# says 16 for the faulty blade, so half of the chips are not functional, although if you go by counting x's and o's more than half are throwing errors or non functional.
xxxxxoxo xoxoxoxo xxxxxxxx xxxxxxxx
Swapping the PSU at this stage would be a pointless exercise.
alternatively, use a multimeter and check the volatge on the bad board. to do this:
red (+) probe goes to the bottom connection of the large grey cube-shaped inductor (there are 4 of these per blade, test on all 4 on the bad side please)
black (-) probe goes to any of the small copper dots on the board marked with 'GND', or to the GND terminals for your PSU cables
you should see 1.10V on all 4 inductors. if not, it narrows down the possible sources/causes of the problem.
I mentioned the brand model wattage before..It's an OCZ EliteXstream 1000W, 1000 watts single 12v rail. Hmm, well I'm going to the hosting location today and I'll bring my multimeter with me. I'm going to note down what you said about the voltage test points.
any idea whats the CFM of the fan ?
Ok, well, I guess I found the source of the problem - the left side (aka blade #2) on that unit is bad. I had the unit on by itself on the same PSU as the fully working unit. Yes I did disconnect the other unit entirely. The faulty unit was all by its lonesome. Left the miner cool for a few minutes, powered it on - the same xxxxx on the second module. I tried powering just the faulty blade alone, but I guess the first blade needs to be one as it seems the controller board is fed through it so the unit will not power on fully without the "master" blade.
ASIC# says 16 for the faulty blade, so half of the chips are not functional, although if you go by counting x's and o's more than half are throwing errors or non functional.
xxxxxoxo xoxoxoxo xxxxxxxx xxxxxxxx
Swapping the PSU at this stage would be a pointless exercise.
so you are running a single antminer on what PSU? (brand, model, wattage, etc)ASIC# says 16 for the faulty blade, so half of the chips are not functional, although if you go by counting x's and o's more than half are throwing errors or non functional.
xxxxxoxo xoxoxoxo xxxxxxxx xxxxxxxx
Swapping the PSU at this stage would be a pointless exercise.
alternatively, use a multimeter and check the volatge on the bad board. to do this:
red (+) probe goes to the bottom connection of the large grey cube-shaped inductor (there are 4 of these per blade, test on all 4 on the bad side please)
black (-) probe goes to any of the small copper dots on the board marked with 'GND', or to the GND terminals for your PSU cables
you should see 1.10V on all 4 inductors. if not, it narrows down the possible sources/causes of the problem.
If you think one of your blade is not functioning, please let me know I will have Bitmain send you the replacement blade then send the damaged one back to their return address.
I'm suspecting it's the PSU that is causing the x.
quick way to test is to disconnect the 1st blade, replace it with the 2nd blade, power it on and see it hashes away or it gives you the same problem. If it runs and hashes away at 80-90 GHS range, then it's the PSU causing the issues.
SUSHI.
Thanks. I hope so too. As for return I'm glad to see Bitmain taking care of their customers.
I'm suspecting it's the PSU that is causing the x.
quick way to test is to disconnect the 1st blade, replace it with the 2nd blade, power it on and see it hashes away or it gives you the same problem. If it runs and hashes away at 80-90 GHS range, then it's the PSU causing the issues.
SUSHI.
Good luck, I hope you can fix it asap. You will get a return if not, i was offered one.
Thanks. I hope so too. As for return I'm glad to see Bitmain taking care of their customers.
sushi, check your PM. I requested to have Bitmain send me a replacement blade. Thanks.
Ok, well, I guess I found the source of the problem - the left side (aka blade #2) on that unit is bad. I had the unit on by itself on the same PSU as the fully working unit. Yes I did disconnect the other unit entirely. The faulty unit was all by its lonesome. Left the miner cool for a few minutes, powered it on - the same xxxxx on the second module. I tried powering just the faulty blade alone, but I guess the first blade needs to be one as it seems the controller board is fed through it so the unit will not power on fully without the "master" blade.
ASIC# says 16 for the faulty blade, so half of the chips are not functional, although if you go by counting x's and o's more than half are throwing errors or non functional.
xxxxxoxo xoxoxoxo xxxxxxxx xxxxxxxx
Swapping the PSU at this stage would be a pointless exercise.
I will be asking Sushi to talk with bitmain to see if they can send me a replacement blade.
Thanks to all those who've come up with suggestions.
ASIC# says 16 for the faulty blade, so half of the chips are not functional, although if you go by counting x's and o's more than half are throwing errors or non functional.
xxxxxoxo xoxoxoxo xxxxxxxx xxxxxxxx
Swapping the PSU at this stage would be a pointless exercise.
I will be asking Sushi to talk with bitmain to see if they can send me a replacement blade.
Thanks to all those who've come up with suggestions.
Sushi, is there a way to identify and differentiate between the two blades. For example, which one is chain one and which one is chain two. Are the blades labelled or is there some logic followed like for example chain one being the left blade and 2 being the right..etc
the string of 'x' or 'o' that includes a fan speed and is the upper of the 2 is the board that the control board is attached too. The second line is the board opposite the control board/module
Good luck, I hope you can fix it asap. You will get a return if not, i was offered one.
Thanks. I hope so too. As for return I'm glad to see Bitmain taking care of their customers.
I had something similar on my first Ant which uses more power than my second at the wall. I had a 1000W PSU that didn't provide enough amps to both blades as it seemed that both power feeds came from the same rail. I powered up the Ant with just blade 1 and it worked fine, a bag full of O's. In the end I had two old 450W Corsairs, one powering each blade but I had to power on, get a bag of X's and then reboot from the console. PSU's and their ability to deliver amps seems really important for these Ant's.
Now I have a CoolerMaster SilentPro Hybrid 1050W running two Ant's drawing 815W at the wall.
In my case one of the blades has a bag full of Os, but the second has a 60% empty bag lol. So maybe the PSU hasn't got the juice to feed the second blade fully. The other unit being powered by the same PSU is working perfectly; lots of Os
This OCZ PSU I'm using is supposed to have a 80A 12V rail.
If you think one of your blade is not functioning, please let me know I will have Bitmain send you the replacement blade then send the damaged one back to their return address.
I'm suspecting it's the PSU that is causing the x.
quick way to test is to disconnect the 1st blade, replace it with the 2nd blade, power it on and see it hashes away or it gives you the same problem. If it runs and hashes away at 80-90 GHS range, then it's the PSU causing the issues.
SUSHI.
Thanks. I hope so too. As for return I'm glad to see Bitmain taking care of their customers.
I'm suspecting it's the PSU that is causing the x.
quick way to test is to disconnect the 1st blade, replace it with the 2nd blade, power it on and see it hashes away or it gives you the same problem. If it runs and hashes away at 80-90 GHS range, then it's the PSU causing the issues.
SUSHI.
Good luck, I hope you can fix it asap. You will get a return if not, i was offered one.
Thanks. I hope so too. As for return I'm glad to see Bitmain taking care of their customers.
I'm definitely going to try that. First I will try powering the entire unit on it's own PSU. That seems to me like the easiest most logical next step. I'll get back to you either by the end of today or tomorrow. I'll try to find the cause today as this is pretty time sensitive.
You should keep it off for awhile. Maybe 1-2 hours and then give it a try again with a different psu
Sushi, is there a way to identify and differentiate between the two blades. For example, which one is chain one and which one is chain two. Are the blades labelled or is there some logic followed like for example chain one being the left blade and 2 being the right..etc
If you think one of your blade is not functioning, please let me know I will have Bitmain send you the replacement blade then send the damaged one back to their return address.
I'm suspecting it's the PSU that is causing the x.
quick way to test is to disconnect the 1st blade, replace it with the 2nd blade, power it on and see it hashes away or it gives you the same problem. If it runs and hashes away at 80-90 GHS range, then it's the PSU causing the issues.
SUSHI.
Thanks. I hope so too. As for return I'm glad to see Bitmain taking care of their customers.
I'm suspecting it's the PSU that is causing the x.
quick way to test is to disconnect the 1st blade, replace it with the 2nd blade, power it on and see it hashes away or it gives you the same problem. If it runs and hashes away at 80-90 GHS range, then it's the PSU causing the issues.
SUSHI.
Good luck, I hope you can fix it asap. You will get a return if not, i was offered one.
Thanks. I hope so too. As for return I'm glad to see Bitmain taking care of their customers.
I'm definitely going to try that. First I will try powering the entire unit on it's own PSU. That seems to me like the easiest most logical next step. I'll get back to you either by the end of today or tomorrow. I'll try to find the cause today as this is pretty time sensitive.
Is anyone else running into high loads (CPU) on their Ant's?
It looks like if I run them long enough without a reboot, the load becomes so high that even logging into the GUI is tricky. I have had to do a reboot to get them running again
It looks like if I run them long enough without a reboot, the load becomes so high that even logging into the GUI is tricky. I have had to do a reboot to get them running again
If you think one of your blade is not functioning, please let me know I will have Bitmain send you the replacement blade then send the damaged one back to their return address.
I'm suspecting it's the PSU that is causing the x.
quick way to test is to disconnect the 1st blade, replace it with the 2nd blade, power it on and see it hashes away or it gives you the same problem. If it runs and hashes away at 80-90 GHS range, then it's the PSU causing the issues.
SUSHI.
Thanks. I hope so too. As for return I'm glad to see Bitmain taking care of their customers.
I'm suspecting it's the PSU that is causing the x.
quick way to test is to disconnect the 1st blade, replace it with the 2nd blade, power it on and see it hashes away or it gives you the same problem. If it runs and hashes away at 80-90 GHS range, then it's the PSU causing the issues.
SUSHI.
Good luck, I hope you can fix it asap. You will get a return if not, i was offered one.
Thanks. I hope so too. As for return I'm glad to see Bitmain taking care of their customers.
Good luck, I hope you can fix it asap. You will get a return if not, i was offered one.
Thanks. I hope so too. As for return I'm glad to see Bitmain taking care of their customers.
I had something similar on my first Ant which uses more power than my second at the wall. I had a 1000W PSU that didn't provide enough amps to both blades as it seemed that both power feeds came from the same rail. I powered up the Ant with just blade 1 and it worked fine, a bag full of O's. In the end I had two old 450W Corsairs, one powering each blade but I had to power on, get a bag of X's and then reboot from the console. PSU's and their ability to deliver amps seems really important for these Ant's.
Now I have a CoolerMaster SilentPro Hybrid 1050W running two Ant's drawing 815W at the wall.
Good luck, I hope you can fix it asap. You will get a return if not, i was offered one.
Thanks. I hope so too. As for return I'm glad to see Bitmain taking care of their customers.
Good luck, I hope you can fix it asap. You will get a return if not, i was offered one.
I'd hope it's physically fine. I'd like to avoid the time waste of a RMA process, although if it has to come to that I'd go for it as I paid for 180 GH and I expect to get at least that. I PM'ed sushi. I bet he is sleeping now - the poor guy is overworked - so I shall have to wait it out.
I'll see if I can swing by the place where I'm hosting this miner and place it on it's own dedicated PSU. That may do the trick - or so I hope.
I'll see if I can swing by the place where I'm hosting this miner and place it on it's own dedicated PSU. That may do the trick - or so I hope.
Looks normal, pm sushi. He will do a teamviewer session with you trying to fix it.
I think most likely your miner is fine as theyre the exact same bugs mine showed.
I think most likely your miner is fine as theyre the exact same bugs mine showed.
root@antMiner:/etc/config# cat asic-freq
package 'cgminer'
config 'asic-freq' 'default'
#option 'freq_value' '0780' #400M
#option 'freq_value' '4d81' #350M
#option 'chip_freq' '350'
option 'timeout' '40'
#option 'freq_value' '4c81' #325M
#option 'chip_freq' '325'
option 'freq_value' '4d81' #350M
option 'chip_freq' '350'
#option 'freq_value' '0580' #300M
#option 'chip_freq' '300'
#option 'freq_value' '0981' #250M
#option 'chip_freq' '250'
#option 'freq_value' '4f02' #190M
#option 'chip_freq' '190'
root@antMiner:/etc/config#
package 'cgminer'
config 'asic-freq' 'default'
#option 'freq_value' '0780' #400M
#option 'freq_value' '4d81' #350M
#option 'chip_freq' '350'
option 'timeout' '40'
#option 'freq_value' '4c81' #325M
#option 'chip_freq' '325'
option 'freq_value' '4d81' #350M
option 'chip_freq' '350'
#option 'freq_value' '0580' #300M
#option 'chip_freq' '300'
#option 'freq_value' '0981' #250M
#option 'chip_freq' '250'
#option 'freq_value' '4f02' #190M
#option 'chip_freq' '190'
root@antMiner:/etc/config#
Jump to: