paradice for asic owners  anyone who pays for electricity should buy asics, period. I used to pay $350 a month for power to run 3 GPU rigs and get about 7MH, plus the issue of dealing with the heat. Now I pay about $15 a month for power and get 14MH, almost no heat. You do the math. thats true, but for how long you get good results with 14MHs on scrypt?? scrypt will raise like Sha256 now with asics...better focus on Scrypt Adaptive N and X11 Ok we have a network of 11GHs, but can anyone tell me where they are?on which Pool? That's very true, but as of now, and for the past 3 months 14MH scrypt for $15 dollars a month has been great. With the savings on power alone, they have about 30% been paid off. I think it will be a while before they cost more in power than what they make. When that happens, yes they will become paperweights. As of now, its just not profitable enough to run GPU rigs for Scrypt-N and X11. You still make more running your GPU Scrypt. At this very moment, I can make 1 BTC a month running 3500 KH Scrypt-N power. That barely covers my power cost, not to mention dealing with the heat is problematic. *EDITED to fix some of my math  * |
|
|
|
paradice for asic owners anyone who pays for electricity should buy asics, period. I used to pay $350 a month for power to run 3 GPU rigs and get about 7MH, plus the issue of dealing with the heat. Now I pay about $15 a month for power and get 14MH, almost no heat. You do the math. we have 53 GPU and we pay for electricity 1600$  Power must be fairly cheap where you live! Where I live its expensive, plus I was doing it out of my home, so they gouge you even more. |
|
|
|
paradice for asic owners anyone who pays for electricity should buy asics, period. I used to pay $350 a month for power to run 3 GPU rigs and get about 7MH, plus the issue of dealing with the heat. Now I pay about $15 a month for power and get 14MH, almost no heat. You do the math. |
|
|
|
Is dedicated Pool down?
all my rigs disconnected and will not reconnect! For me also down... I have had nothing but problems with dedicatedpool recently. They launch all the new coins on their East1 server for US and it gets heavily overloaded, to the point where you cannot connect anymore, and if you do your miners will drop off and then come back on. I have had good luck with pool.mn |
|
|
|
|
I have minepeon working on a rasberrypi with 21 gridseeds and it's working great. I swapped the bfgminer with the one modified with the gridseed driver and changed the command line in the WebUI to the gridseed flags. Working great so far, except the hashrate shows under SHA-256 and not "Scrypt". I assume this may be because of me switching out the bfgminer version? Not a big deal, but would like to correct if possible.
|
|
|
|
|
is bfgminer stable with the 5 chip gridseeds yet? I have yet to find something as stable as running individual cpuminer threads.
|
|
|
|
I don't how this could have possibly happened because I know he had a surge protector and aren't those things supposed to trip when there's too much voltage going through them?
Sorry, but that just isn't true. It may have just been a freak incident, but more likely your friend probably pulled too much current through too thin of wire gauge. Circuit breakers are meant to protect the wire, not the devices. You can pump 16A through 24 gauge wire and it wont ever trip a 20A breaker, but your wire gets too hot, the sleeve melts, and now you have a wire that is 110+ degrees Celsius exposed. Do yourself a favor and get a Kill-a-Watt meter. It will give you a little piece of mind. Find out what other outlets are controlled by the breaker your rigs are on, and then add up the total amperage of all devices on that circuit, including your rigs. You should be at no more than 80% of the breakers capacity. If you did any DIY wiring, make sure you used the proper gauge wire for the current its carrying. Over gauge the wire if you are extra worried. Also, make sure your PSU power cables are gauged heavy enough for the current they pull. Lastly, make sure your surge protector is rated to at least 15A (most are). With the rig you are describing you have, I highly doubt you have anything to worry about. |
|
|
|
|
So I found the limit of gridseed devices you can run on the Pi. That limit is 32. Not because the processor isn't fast enough, but because the serial to usb driver that it uses only supports 32. The other devices are seen by the Pi but it does not assign them a ttyACM address and therefore cannot be used.
Unless there is a workaround, 32 is the magic number!
|
|
|
|
how can you check polarity of a cable with a multimeter?
check for resistance in the wire and connector. Hold one probe on the sleeve of the connector (I assume you are talking about DC plugs) and then touch the other probe to the ends of the cables. The one that registers resistance is your ground or (-) wire. |
|
|
|
 I will try that, I had them daisy chained because all the ports are full on the hubs and was using the other usb for keyboard and mouse. I now just ssh in so I dont need the port. Didnt cross my mind because cpuminer was working flawlessly. changing the ports didn't help. Whats really wierd is if I let it sit long enough, they all enventually submit shares, except the power usage fluctuates alot, 140 watts up to 220, and back down. Almost like the Pi just isnt fast enough to run 28 in cgminer. Maybe the code is less cpu efficient than cpuminer. I get the feeling it cant keep up and miners are going idle and then back online, which would explain the power fluctuations. |
|
|
|
Has anyone tried a large amount of gridseeds on cgminer? I am trying 28 of them on a rasberry pi and it stops accepting shares and eventually crashes after about 2 minutes. Running 28 instances of cpuminer works great, stable, and multipool reports right about where the hash rate should be.
Mine's been stable since upgrading to the "next" kernel (3.10.30+): sudo apt-get install rpi-update sudo BRANCH=next rpi-update This is potentially great news! I've been having stability issues and set a cron job to do a reboot every 6 hours. I've applied the update and disabled the cron job on 1 of 2 of my Pi's and i'll monitor over the next 24 hours. Oh and just a recommendation, i've been using JuiceSSH for Android to remotely manage my RPI's and it works great. I even set up some port forwarding on my router so I can remote access from anywhere I have cell service! Has come in handy on several occasions (issuing a quick reboot command when needed). -EMoomjean I tried that and now cgminer just crashes on startup. Did you have to recompile cgminer after updating? Nope, I just executed the 2 commands and performed a reboot afterwards. BTW, I double checked and the slub debug command in the cmdline.txt persists through the update (I only mention it because I saw cmdline.txt scroll by as one of the files that was touched in the patch). -EMoomjean Just recompiled and checked my cmdline.txt, was missing the stability fix. Changed and now cgminer starts, but I get some HW errors and some miners dont accept any shares. Power usage is only 140 watts compared to 240 running cpuminer. Sounds like either cgminer isn't seeing all your miners or the RPI isnt seeing them. I would try running the lsusb -t command to verify all of your miners are recognized by the RPI as a first step. If you're using the 10 port hub that came with the Lightning Asic kits the ports with comm/data are the miner ports (should be 1-6, then 7 is Class=hub under which you'll see another 1-4). -EMoomjean Thanks for all your help. I am using the monoprice 24 port hub, with another 7 port hub daisy chained. Cpuminer sees all of the devices so I assume cgminer would as well. 28 total gridseeds screen -dmS 1 sudo ./cgminer --scrypt -o stratum+tcp://us-west2.multipool.us:7777 -u myuser.gs1 -p x --gridseed-options=baud=115200,freq=800,chips=5 --hotplug 0 When I run lsusb -t I get this: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc_otg/1p, 480M
|__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/3p, 480M
|__ Port 1: Dev 3, If 0, Class=vend., Driver=smsc95xx, 480M
|__ Port 2: Dev 4, If 0, Class=hub, Driver=hub/7p, 480M
|__ Port 1: Dev 5, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 1: Dev 5, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 2: Dev 6, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 2: Dev 6, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 3: Dev 7, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 3: Dev 7, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 4: Dev 8, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 4: Dev 8, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 5: Dev 9, If 0, Class=hub, Driver=hub/7p, 480M
|__ Port 1: Dev 12, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 1: Dev 12, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 2: Dev 13, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 2: Dev 13, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 3: Dev 14, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 3: Dev 14, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 4: Dev 15, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 4: Dev 15, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 6: Dev 16, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 6: Dev 16, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 7: Dev 17, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 7: Dev 17, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 6: Dev 10, If 0, Class=hub, Driver=hub/7p, 480M
|__ Port 1: Dev 18, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 1: Dev 18, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 2: Dev 19, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 2: Dev 19, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 3: Dev 20, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 3: Dev 20, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 4: Dev 21, If 0, Class=hub, Driver=hub/4p, 480M
|__ Port 1: Dev 32, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 1: Dev 32, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 2: Dev 33, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 2: Dev 33, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 4: Dev 34, If 0, Class=hub, Driver=hub/4p, 480M
|__ Port 1: Dev 35, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 1: Dev 35, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 2: Dev 36, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 2: Dev 36, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 3: Dev 37, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 3: Dev 37, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 5: Dev 22, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 5: Dev 22, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 6: Dev 23, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 6: Dev 23, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 7: Dev 24, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 7: Dev 24, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 7: Dev 11, If 0, Class=hub, Driver=hub/7p, 480M
|__ Port 1: Dev 25, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 1: Dev 25, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 2: Dev 26, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 2: Dev 26, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 3: Dev 27, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 3: Dev 27, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 4: Dev 28, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 4: Dev 28, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 5: Dev 29, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 5: Dev 29, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 6: Dev 30, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 6: Dev 30, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 7: Dev 31, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 7: Dev 31, If 1, Class=data, Driver=cdc_acm, 12M The command line argument you are using looks like the cgminer for windows version (boy do I spend too much time reading all these threads to spot that). I don't use the chips=5 or --hotplug 0 variables and mine works fine. Its a stab in the dark, but worth a try... (though i'll admit your USB topology is slightly different so hotplug *might* be needed, though I doubt it). -EMoomjean Edit: Out of curiosity, why are you daisy chaining the hubs? The RPI has 2 USB ports (excluding the power port) Why not plug the 24-port into one of the RPI's USB ports and the 7-port into the other? I will try that, I had them daisy chained because all the ports are full on the hubs and was using the other usb for keyboard and mouse. I now just ssh in so I dont need the port. Didnt cross my mind because cpuminer was working flawlessly. |
|
|
|
Has anyone tried a large amount of gridseeds on cgminer? I am trying 28 of them on a rasberry pi and it stops accepting shares and eventually crashes after about 2 minutes. Running 28 instances of cpuminer works great, stable, and multipool reports right about where the hash rate should be.
Mine's been stable since upgrading to the "next" kernel (3.10.30+): sudo apt-get install rpi-update sudo BRANCH=next rpi-update This is potentially great news! I've been having stability issues and set a cron job to do a reboot every 6 hours. I've applied the update and disabled the cron job on 1 of 2 of my Pi's and i'll monitor over the next 24 hours. Oh and just a recommendation, i've been using JuiceSSH for Android to remotely manage my RPI's and it works great. I even set up some port forwarding on my router so I can remote access from anywhere I have cell service! Has come in handy on several occasions (issuing a quick reboot command when needed). -EMoomjean I tried that and now cgminer just crashes on startup. Did you have to recompile cgminer after updating? Nope, I just executed the 2 commands and performed a reboot afterwards. BTW, I double checked and the slub debug command in the cmdline.txt persists through the update (I only mention it because I saw cmdline.txt scroll by as one of the files that was touched in the patch). -EMoomjean Just recompiled and checked my cmdline.txt, was missing the stability fix. Changed and now cgminer starts, but I get some HW errors and some miners dont accept any shares. Power usage is only 140 watts compared to 240 running cpuminer. Sounds like either cgminer isn't seeing all your miners or the RPI isnt seeing them. I would try running the lsusb -t command to verify all of your miners are recognized by the RPI as a first step. If you're using the 10 port hub that came with the Lightning Asic kits the ports with comm/data are the miner ports (should be 1-6, then 7 is Class=hub under which you'll see another 1-4). -EMoomjean Thanks for all your help. I am using the monoprice 24 port hub, with another 7 port hub daisy chained. Cpuminer sees all of the devices so I assume cgminer would as well. 28 total gridseeds screen -dmS 1 sudo ./cgminer --scrypt -o stratum+tcp://us-west2.multipool.us:7777 -u myuser.gs1 -p x --gridseed-options=baud=115200,freq=800,chips=5 --hotplug 0 When I run lsusb -t I get this: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc_otg/1p, 480M
|__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/3p, 480M
|__ Port 1: Dev 3, If 0, Class=vend., Driver=smsc95xx, 480M
|__ Port 2: Dev 4, If 0, Class=hub, Driver=hub/7p, 480M
|__ Port 1: Dev 5, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 1: Dev 5, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 2: Dev 6, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 2: Dev 6, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 3: Dev 7, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 3: Dev 7, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 4: Dev 8, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 4: Dev 8, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 5: Dev 9, If 0, Class=hub, Driver=hub/7p, 480M
|__ Port 1: Dev 12, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 1: Dev 12, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 2: Dev 13, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 2: Dev 13, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 3: Dev 14, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 3: Dev 14, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 4: Dev 15, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 4: Dev 15, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 6: Dev 16, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 6: Dev 16, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 7: Dev 17, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 7: Dev 17, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 6: Dev 10, If 0, Class=hub, Driver=hub/7p, 480M
|__ Port 1: Dev 18, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 1: Dev 18, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 2: Dev 19, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 2: Dev 19, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 3: Dev 20, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 3: Dev 20, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 4: Dev 21, If 0, Class=hub, Driver=hub/4p, 480M
|__ Port 1: Dev 32, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 1: Dev 32, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 2: Dev 33, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 2: Dev 33, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 4: Dev 34, If 0, Class=hub, Driver=hub/4p, 480M
|__ Port 1: Dev 35, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 1: Dev 35, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 2: Dev 36, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 2: Dev 36, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 3: Dev 37, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 3: Dev 37, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 5: Dev 22, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 5: Dev 22, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 6: Dev 23, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 6: Dev 23, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 7: Dev 24, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 7: Dev 24, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 7: Dev 11, If 0, Class=hub, Driver=hub/7p, 480M
|__ Port 1: Dev 25, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 1: Dev 25, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 2: Dev 26, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 2: Dev 26, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 3: Dev 27, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 3: Dev 27, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 4: Dev 28, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 4: Dev 28, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 5: Dev 29, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 5: Dev 29, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 6: Dev 30, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 6: Dev 30, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 7: Dev 31, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 7: Dev 31, If 1, Class=data, Driver=cdc_acm, 12M |
|
|
|
Has anyone tried a large amount of gridseeds on cgminer? I am trying 28 of them on a rasberry pi and it stops accepting shares and eventually crashes after about 2 minutes. Running 28 instances of cpuminer works great, stable, and multipool reports right about where the hash rate should be.
Mine's been stable since upgrading to the "next" kernel (3.10.30+): sudo apt-get install rpi-update sudo BRANCH=next rpi-update This is potentially great news! I've been having stability issues and set a cron job to do a reboot every 6 hours. I've applied the update and disabled the cron job on 1 of 2 of my Pi's and i'll monitor over the next 24 hours. Oh and just a recommendation, i've been using JuiceSSH for Android to remotely manage my RPI's and it works great. I even set up some port forwarding on my router so I can remote access from anywhere I have cell service! Has come in handy on several occasions (issuing a quick reboot command when needed). -EMoomjean I tried that and now cgminer just crashes on startup. Did you have to recompile cgminer after updating? Nope, I just executed the 2 commands and performed a reboot afterwards. BTW, I double checked and the slub debug command in the cmdline.txt persists through the update (I only mention it because I saw cmdline.txt scroll by as one of the files that was touched in the patch). -EMoomjean Just recompiled and checked my cmdline.txt, was missing the stability fix. Changed and now cgminer starts, but I get some HW errors. Power usage is only 140 watts compared to 240 running cpuminer. It seems some miners are lazy and rarely accept shares, they all eventually start but some already have over 1000 accepted while some have 32. I also am getting many more rejects. I'll stick with cpuminer until thebugs get sorted. Here is my command to launch: screen -dmS 1 sudo ./cgminer --scrypt -o stratum+tcp://us-west2.multipool.us:7777 -u myuser.gs1 -p x --gridseed-options=baud=115200,freq=800,chips=5 --hotplug 0 |
|
|
|
Has anyone tried a large amount of gridseeds on cgminer? I am trying 28 of them on a rasberry pi and it stops accepting shares and eventually crashes after about 2 minutes. Running 28 instances of cpuminer works great, stable, and multipool reports right about where the hash rate should be.
Mine's been stable since upgrading to the "next" kernel (3.10.30+): sudo apt-get install rpi-update sudo BRANCH=next rpi-update This is potentially great news! I've been having stability issues and set a cron job to do a reboot every 6 hours. I've applied the update and disabled the cron job on 1 of 2 of my Pi's and i'll monitor over the next 24 hours. Oh and just a recommendation, i've been using JuiceSSH for Android to remotely manage my RPI's and it works great. I even set up some port forwarding on my router so I can remote access from anywhere I have cell service! Has come in handy on several occasions (issuing a quick reboot command when needed). -EMoomjean I tried that and now cgminer just crashes on startup. Did you have to recompile cgminer after updating? |
|
|
|
|
Has anyone tried a large amount of gridseeds on cgminer? I am trying 28 of them on a rasberry pi and it stops accepting shares and eventually crashes after about 2 minutes. Running 28 instances of cpuminer works great, stable, and multipool reports right about where the hash rate should be.
|
|
|
|
anyone have a top choice of PSU/recommendations, just read over on the Gridseed post a 30W saving on using a Platinum PSU over the supplied PSU!. Any advice appreciated.
It is a matter of cost vs efficiency. Assuming the miners take 60 watts, using 90 watts to run the miners is a 67% efficient PSU. If you use a 90% efficient PSU (platinum), then it would only take 67 watts. 90% efficient PSU will cost more than a 67% efficient PSU. What is it worth to you to save 23 watts? At 1/2 Kwh/day at 15 cents per kwh, that is $27 per year. A cheap PSU costs $20. A Platinum PSU costs $80. I would go for a 80 plus gold psu, and get the lowest wattage you can while still leaving 20-25% of headroom. Those psu that come with a majority of the units are junk and inefficient. Atx power supplies are readily available anywhere and IMO are better because they at least have guidelines to adhere to (ATX v2.2 or 2.3). Plus they are way quieter than the brick PSUs. |
|
|
|
I bought the monoprice ones with the ferrite core and the connector is just barely too big, very snug fit. However, you can just bend the fins on the heatsink out of the way, right above the usb port, and then they fit great. I also have some of the monoprice ones without the ferrite core and they fit fine with no modification. |
|
|
|
|
Just thought I would chime in. I am running 24 off one rasberry pi. Scrypt only. So far stable. Using the monoprice 24 port hub. All including hub and pi running off an atx power supply. Running at 850 mhz. Multipool reports 8500 kh on the 10 minute.
Used the raspbian wheezy image and cpuminer. Command line interface only, not booting to desktop.
|
|
|
|
+1 for the Rasberry Pi. Throw your controller away and use one. I have 24 running at the moment off one Pi. Working great so far. Plus it's so cute! |
|
|
|
|
Picked up some gridseeds from zoomhash for cash money, met down at the shop. Great guy! Definitely has my business in the future! Can't beat the instant gratification instead of waiting for your overseas order.
|
|
|
|
|
Show Posts
