Nite
Newbie

Activity: 51
Merit: 0
|
 |
November 11, 2014, 09:32:22 AM |
|
Mine right now is at 38c and 36c so the fans bounce between low and medium speed, most of the time it stays at medium speed though
Low Speed = 1440 and 1080 rpm Medium Speed = 1680 and 1320 rpm High speed = 2100 and 1680 rpm
my room temp is currently 72f, but outside its 35f.... its cold tonight.
|
|
|
|
|
jackbox
Legendary

Activity: 1246
Merit: 1024
|
 |
November 11, 2014, 10:08:10 AM |
|
Mine right now is at 38c and 36c so the fans bounce between low and medium speed, most of the time it stays at medium speed though
Low Speed = 1440 and 1080 rpm Medium Speed = 1680 and 1320 rpm High speed = 2100 and 1680 rpm
my room temp is currently 72f, but outside its 35f.... its cold tonight.
Mine is running in Bangkok with ambient temps around 30 Celsius when the aircon is not on. 
|
|
|
|
Nite
Newbie

Activity: 51
Merit: 0
|
 |
November 11, 2014, 11:14:54 AM |
|
Mine right now is at 38c and 36c so the fans bounce between low and medium speed, most of the time it stays at medium speed though
Low Speed = 1440 and 1080 rpm Medium Speed = 1680 and 1320 rpm High speed = 2100 and 1680 rpm
my room temp is currently 72f, but outside its 35f.... its cold tonight.
Mine is running in Bangkok with ambient temps around 30 Celsius when the aircon is not on.  Yea I bet its loud at that temp, don't worry the same will probably happen to me around summer time when it gets hot where I am.
|
|
|
|
|
|
brush242
|
 |
November 11, 2014, 03:38:33 PM |
|
Right, and thank you. But there were several posts recently in this thread that noted that B11 fans were signficantly louder than prior batches of B3+.
I was wonder if there was any other discussion thereof, or if anyone knew of a change, et cetera, that was more specific.
Thanks again. I originally posted that my B11 were louder then my batch 8 and 9, but since then they have tapered off and run at fairly the same db as my original S3+s. Great, thanks for the heads up!
|
Support sidehack miner development. Donations to: 1BURGERAXHH6Yi6LRybRJK7ybEm5m5HwTr
|
|
|
|
brush242
|
 |
November 11, 2014, 03:44:44 PM |
|
Or if you want to really get creative, build like a duct behind all your S3 miners exaust fans and plug a dryer vent to it and the heat will go out of the house instead of surrounding the miners in the room lol Be careful with this, the fans on the miners are not sufficient to push down a dryer vent very far, especially if it has twists and turns. Net result? Disaster.
|
Support sidehack miner development. Donations to: 1BURGERAXHH6Yi6LRybRJK7ybEm5m5HwTr
|
|
|
|
brush242
|
 |
November 11, 2014, 04:21:04 PM |
|
After using an ip scanner to find an S3+ (Paragon whatever), it noted that and all the other hardware fine. However, it also noted say 700+ or so IPs all with the same MAC addy, without any hardware name.
Anyone know what that is or why? Never seen it before.
Thanks, in advance.
|
Support sidehack miner development. Donations to: 1BURGERAXHH6Yi6LRybRJK7ybEm5m5HwTr
|
|
|
|
cloh76
|
 |
November 11, 2014, 06:42:37 PM |
|
Mine right now is at 38c and 36c so the fans bounce between low and medium speed, most of the time it stays at medium speed though
Low Speed = 1440 and 1080 rpm Medium Speed = 1680 and 1320 rpm High speed = 2100 and 1680 rpm
my room temp is currently 72f, but outside its 35f.... its cold tonight.
You should put them outside in the garage or a covered area. You wont even need the fans and/or they will run at low speed j/k  The miners can replace your heater
|
[ BTC Donations: 13RNJdT72WEd1FsT3CwdJ6jy9NAa7Hsb54 ]
|
|
|
|
BITMAIN (OP)
|
 |
November 12, 2014, 02:17:30 PM |
|
BITMAIN announces Antpool: Pushing forward Decentralization We are pleased to announce Antpool (antpool.com) which is open for users all around the world. BITMAIN has invested significant resources into developing a bitcoin pool based on the p2pool mining protocol. BITMAIN reaffirms its commitment to help decentralize the Bitcoin network, strengthen the Bitcoin eco-system and put the majority of hashing power into the hands of consumers. The p2pool protocol prevents hashing power being controlled by one central entity (the pool owner), and has been significantly developed during the development of Antpool. All p2pool code will be open sourced and uploaded on BITMAIN’s Github link this week https://github.com/bitmaintech/p2pool. Antpool supports solo mining as well. Antpool has been proven to be stable and secure through its long testing period. From August 22th to November 10th, 295 blocks were found and 7398 Bitcoins were mined. Further stats can be found here link https://www.antpool.com/poolStats.htm. Antpool can be found at antpool.com, while miners now can connect at stratum.antpool.com:3333 for pooled mining, and will be able to connect at p2p.antpool.com:3333 for p2p mining this week. Pool nodes are deployed around the world to improve performance and provide redundancy. Miners are automatically routed their closest location, including: - United States
- Germany
- Hong Kong
- Beijing
- Shenzhen
- Qingdao
- Hangzhou and more.
Features- 0% fees and PPLNS earnings.
- Graphical displays for hashing speeds, income and pool statistics.
- Email warnings for underperforming miners.
- API and third party application support.
- Support for miner groups, group statistics and management.
Forum & Ticket System Users are able to access to Antpool with their BITMAIN account. The log in and ticket system is unified across all BITMAIN services, which allows communication and support to be more efficient. Miners now can buy mining rigs from bitmaintech.com and chose hosting service at Umisoo and mine at antpool.com. Your feedback is important for us to develop and improve our products. Ticket page: support.bitmain.com Forum Page: forum.bitmain.com
|
Cloud Mining? Just Go to Hashnest.com Best Liquidity Lowest Price 100% Real Mining Back Up
|
|
|
|
Deagle21
|
 |
November 12, 2014, 09:35:44 PM |
|
Hey guys, got a probelm with a S3. Unit was hashing fine but then it just stopped hashing for no reason. The red LED stays on all the time even after the unit is powered up and connects to the network.
After power up, the fans spin and red LED comes on then the fans stop for a bit. After a few seconds, then green and yellow LAN LEDs start flashing, then the fans start spinning. Then the green LED next the the RED LED comes on but the RED LED does not go out like expected. I can log into the miner from web brwoser fine but it never resumes hashing. Is there a fix for this issue? I have rebooted, cycled power, reinstalled backup program and reinstalled firmware and tried to reset the miner with the little button on the back. Nothing gets it hashing again. I even changed pools but no go either.
|
|
|
|
|
Biodom
Legendary

Activity: 4592
Merit: 6558
|
 |
November 12, 2014, 10:23:13 PM |
|
Hey guys, got a probelm with a S3. Unit was hashing fine but then it just stopped hashing for no reason. The red LED stays on all the time even after the unit is powered up and connects to the network.
After power up, the fans spin and red LED comes on then the fans stop for a bit. After a few seconds, then green and yellow LAN LEDs start flashing, then the fans start spinning. Then the green LED next the the RED LED comes on but the RED LED does not go out like expected. I can log into the miner from web brwoser fine but it never resumes hashing. Is there a fix for this issue? I have rebooted, cycled power, reinstalled backup program and reinstalled firmware and tried to reset the miner with the little button on the back. Nothing gets it hashing again. I even changed pools but no go either.
something else is on your network with the same IP? mistyped pool address?
|
|
|
|
|
|
Deagle21
|
 |
November 12, 2014, 10:38:50 PM |
|
Hey guys, got a probelm with a S3. Unit was hashing fine but then it just stopped hashing for no reason. The red LED stays on all the time even after the unit is powered up and connects to the network.
After power up, the fans spin and red LED comes on then the fans stop for a bit. After a few seconds, then green and yellow LAN LEDs start flashing, then the fans start spinning. Then the green LED next the the RED LED comes on but the RED LED does not go out like expected. I can log into the miner from web brwoser fine but it never resumes hashing. Is there a fix for this issue? I have rebooted, cycled power, reinstalled backup program and reinstalled firmware and tried to reset the miner with the little button on the back. Nothing gets it hashing again. I even changed pools but no go either.
something else is on your network with the same IP? mistyped pool address? It the only device on network that is 192.168.1.99. No I tried other pools and even copied and pasted pool info from my other miners.
|
|
|
|
|
Biodom
Legendary

Activity: 4592
Merit: 6558
|
 |
November 12, 2014, 10:44:59 PM |
|
Hey guys, got a probelm with a S3. Unit was hashing fine but then it just stopped hashing for no reason. The red LED stays on all the time even after the unit is powered up and connects to the network.
After power up, the fans spin and red LED comes on then the fans stop for a bit. After a few seconds, then green and yellow LAN LEDs start flashing, then the fans start spinning. Then the green LED next the the RED LED comes on but the RED LED does not go out like expected. I can log into the miner from web brwoser fine but it never resumes hashing. Is there a fix for this issue? I have rebooted, cycled power, reinstalled backup program and reinstalled firmware and tried to reset the miner with the little button on the back. Nothing gets it hashing again. I even changed pools but no go either.
something else is on your network with the same IP? mistyped pool address? It the only device on network that is 192.168.1.99. is it connected through pc or through router? if through pc, restart it. Also, check the settings of the network (WAN) on the web gui. I had one case when one setting got stuck even after the reset. You should have router at 192.168.1.1 for your setup to work. if your router IP is 192.168. 2.1, or something else, then it is what happened. Check your router IP with advanced-ip scanner.
|
|
|
|
|
|
Deagle21
|
 |
November 12, 2014, 10:57:49 PM |
|
Hey guys, got a probelm with a S3. Unit was hashing fine but then it just stopped hashing for no reason. The red LED stays on all the time even after the unit is powered up and connects to the network.
After power up, the fans spin and red LED comes on then the fans stop for a bit. After a few seconds, then green and yellow LAN LEDs start flashing, then the fans start spinning. Then the green LED next the the RED LED comes on but the RED LED does not go out like expected. I can log into the miner from web brwoser fine but it never resumes hashing. Is there a fix for this issue? I have rebooted, cycled power, reinstalled backup program and reinstalled firmware and tried to reset the miner with the little button on the back. Nothing gets it hashing again. I even changed pools but no go either.
something else is on your network with the same IP? mistyped pool address? It the only device on network that is 192.168.1.99. is it connected through pc or through router? if through pc, restart it. Also, check the settings of the network (WAN) on the web gui. I had one case when one setting got stuck even after the reset. You should have router at 192.168.1.1 for your setup to work. if your router IP is 192.168. 2.1, or something else, then it is what happened. Check your router IP with advanced-ip scanner. I have the miner plugged in to the router directly. I originally had it running on static IP 192.168.1.98. Router setting is default 192.168.1.1. I can see status through web browser on that IP and also on defalut IP 192.168.1.99 after I factory restore firmware. I also can see it when I set the IP to DHCP and the router set IP to 192.168.1.31. Web interface works great on all three IPs but the thing just wont start hashing. The Red LED stays red when all my other miners red LED go out once its connected to pool. I even did a ping test on openwrt.org diagnostic and is send 5 packets out but none received.
|
|
|
|
|
Biodom
Legendary

Activity: 4592
Merit: 6558
|
 |
November 12, 2014, 11:18:04 PM |
|
Hey guys, got a probelm with a S3. Unit was hashing fine but then it just stopped hashing for no reason. The red LED stays on all the time even after the unit is powered up and connects to the network.
After power up, the fans spin and red LED comes on then the fans stop for a bit. After a few seconds, then green and yellow LAN LEDs start flashing, then the fans start spinning. Then the green LED next the the RED LED comes on but the RED LED does not go out like expected. I can log into the miner from web brwoser fine but it never resumes hashing. Is there a fix for this issue? I have rebooted, cycled power, reinstalled backup program and reinstalled firmware and tried to reset the miner with the little button on the back. Nothing gets it hashing again. I even changed pools but no go either.
something else is on your network with the same IP? mistyped pool address? It the only device on network that is 192.168.1.99. is it connected through pc or through router? if through pc, restart it. Also, check the settings of the network (WAN) on the web gui. I had one case when one setting got stuck even after the reset. You should have router at 192.168.1.1 for your setup to work. if your router IP is 192.168. 2.1, or something else, then it is what happened. Check your router IP with advanced-ip scanner. I have the miner plugged in to the router directly. I originally had it running on static IP 192.168.1.98. Router setting is default 192.168.1.1. I can see status through web browser on that IP and also on defalut IP 192.168.1.99 after I factory restore firmware. I also can see it when I set the IP to DHCP and the router set IP to 192.168.1.31. Web interface works great on all three IPs but the thing just wont start hashing. The Red LED stays red when all my other miners red LED go out once its connected to pool. I even did a ping test on openwrt.org diagnostic and is send 5 packets out but none received. strange. try to reset again, then use static instead of DHCP, then try google's 8.8.8.8 or try 192.168.1.1 as DNS
|
|
|
|
|
|
pekatete
|
 |
November 12, 2014, 11:19:14 PM |
|
I have the miner plugged in to the router directly. I originally had it running on static IP 192.168.1.98. Router setting is default 192.168.1.1. I can see status through web browser on that IP and also on defalut IP 192.168.1.99 after I factory restore firmware. I also can see it when I set the IP to DHCP and the router set IP to 192.168.1.31. Web interface works great on all three IPs but the thing just wont start hashing. The Red LED stays red when all my other miners red LED go out once its connected to pool. I even did a ping test on openwrt.org diagnostic and is send 5 packets out but none received.
Log into the unit's web UI and change network to DHCP. Remember to apply the settings. It may change it's address after this, but that is all you have to do.
|
|
|
|
Biodom
Legendary

Activity: 4592
Merit: 6558
|
 |
November 12, 2014, 11:20:58 PM |
|
I have the miner plugged in to the router directly. I originally had it running on static IP 192.168.1.98. Router setting is default 192.168.1.1. I can see status through web browser on that IP and also on defalut IP 192.168.1.99 after I factory restore firmware. I also can see it when I set the IP to DHCP and the router set IP to 192.168.1.31. Web interface works great on all three IPs but the thing just wont start hashing. The Red LED stays red when all my other miners red LED go out once its connected to pool. I even did a ping test on openwrt.org diagnostic and is send 5 packets out but none received.
Log into the unit's web UI and change network to DHCP. Remember to apply the settings. It may change it's address after this, but that is all you have to do. yes, but he said it did not work, which is strange. maybe OP did not "save and apply"
|
|
|
|
|
|
pekatete
|
 |
November 12, 2014, 11:33:14 PM |
|
I have the miner plugged in to the router directly. I originally had it running on static IP 192.168.1.98. Router setting is default 192.168.1.1. I can see status through web browser on that IP and also on defalut IP 192.168.1.99 after I factory restore firmware. I also can see it when I set the IP to DHCP and the router set IP to 192.168.1.31. Web interface works great on all three IPs but the thing just wont start hashing. The Red LED stays red when all my other miners red LED go out once its connected to pool. I even did a ping test on openwrt.org diagnostic and is send 5 packets out but none received.
Log into the unit's web UI and change network to DHCP. Remember to apply the settings. It may change it's address after this, but that is all you have to do. yes, but he said it did not work, which is strange. maybe OP did not "save and apply" You probably should have thought to tell OP to do that in the first place. The only strange thing that was stated is that the unit was hashing properly and then simply stopped, that is VERY strange. I suspect OP got intoa panic, reflashed the firmware, changed to DHCP and did not apply before rebooting again (in a panic again ...?). The only reason I know of that an S3+ will refuse to start hashing is when it is on a static IP. I can not explain why that happens, but it does.
|
|
|
|
Biodom
Legendary

Activity: 4592
Merit: 6558
|
 |
November 12, 2014, 11:40:24 PM |
|
I have the miner plugged in to the router directly. I originally had it running on static IP 192.168.1.98. Router setting is default 192.168.1.1. I can see status through web browser on that IP and also on defalut IP 192.168.1.99 after I factory restore firmware. I also can see it when I set the IP to DHCP and the router set IP to 192.168.1.31. Web interface works great on all three IPs but the thing just wont start hashing. The Red LED stays red when all my other miners red LED go out once its connected to pool. I even did a ping test on openwrt.org diagnostic and is send 5 packets out but none received.
Log into the unit's web UI and change network to DHCP. Remember to apply the settings. It may change it's address after this, but that is all you have to do. yes, but he said it did not work, which is strange. maybe OP did not "save and apply" You probably should have thought to tell OP to do that in the first place. The only strange thing that was stated is that the unit was hashing properly and then simply stopped, that is VERY strange. I suspect OP got intoa panic, reflashed the firmware, changed to DHCP and did not apply before rebooting again (in a panic again ...?). The only reason I know of that an S3+ will refuse to start hashing is when it is on a static IP. I can not explain why that happens, but it does. oh, well, he has enough info to figure it now. sometimes doing twice the same thing brings "them" to life for one mysterios reason or another.
|
|
|
|
|
Nite
Newbie

Activity: 51
Merit: 0
|
 |
November 12, 2014, 11:53:13 PM Last edit: November 13, 2014, 12:26:30 AM by Nite |
|
freaking awesome that the bitcoin price is recovering, at the current $430 price a single S3+ can now do around $75 a month. Not bad at all.
|
|
|
|
|
|
Deagle21
|
 |
November 13, 2014, 12:59:52 AM |
|
Ok guys, got the miner working. I double checked all my settings then saved and rebooted several times. It still would not start hashing even though I could access the web UI just fine. I was about to give up then I decided to reboot my router and the darn thing started working again. I have several other miners working on the same router just fine but for some reason a reboot of the router was all it took for this particular miner to start hashing. Wierd!!! Thanks for all your help.
|
|
|
|
|
|