mining_proxy.exe -o yourstratumpool -p poolstratumport -gp localgetworkport
The proxy defaults to 8332, same as the default config on the Cube.
Topic: [PENDING] ASICMiner Cubes. 30-38gh/s - USA - 1 BTC - Price protection! - page 2. (Read 18187 times)
December 13, 2013, 02:49:47 PM
December 13, 2013, 01:55:11 PM
Are you running it against bfgminer or slush's stratum proxy? I've found cubes/blades don't seem to run as well against the bfgminer implementation. Also, both proxies don't handle multiple units very well. Test out your cube on its own instance of slush's stratum proxy and see if you get different results.
Thanks. I'll try Slush's next once I figure out how to connect through it using other pools (I am coding and CLI-challenged). What port does slush's stratum proxy utilizes BTW?
Even if I could get it to 38 GH/s, I'm not sure if I'll be running it on high clock because that would still be around 18WAC/GH/s at the wall for the additional 6 GH/s; at least twice as much draw as the USB BEs. However, I'm still determined to get it to work just to be able to say that my Cube lived up to the hype.
December 13, 2013, 01:20:08 PM
Pull it apart and make sure all your heatsinks are tight. Mine with the stock overclock topped out around 37.5GH, could have been higher if some of the cards cooled better. You can run the chip outputs through a quick script to find the average hashrate per card and see which ones are the turds.
It's the first thing I did upon receiving it. I also fixed half of the blades that were off the top notches. Thanks.
December 13, 2013, 11:06:41 AM
Are you running it against bfgminer or slush's stratum proxy? I've found cubes/blades don't seem to run as well against the bfgminer implementation. Also, both proxies don't handle multiple units very well. Test out your cube on its own instance of slush's stratum proxy and see if you get different results.
December 13, 2013, 10:40:01 AM
Pull it apart and make sure all your heatsinks are tight. Mine with the stock overclock topped out around 37.5GH, could have been higher if some of the cards cooled better. You can run the chip outputs through a quick script to find the average hashrate per card and see which ones are the turds.
December 13, 2013, 02:56:55 AM
My cube fired right up with nary a hitch and doing 32 GH/s at low clock. However, it only does 2.5 GH/s more (34.5 GH/s) on high clock, drawing an additional 110WAC at the wall. Whatever happened to the advertised minimum of 38 GH/s when OC'd? Is AsicMiner doing a BFL nowadays?
To put it in perspective, 2.5 GH/s drawing 110WAC is a whopping 44WAC/GH (at the wall) or 37.4WDC/GH (with an 85%-efficient PSU). Is it worth it?
BTW, thanks to CrazyGuy for an excellent service and packing.
To put it in perspective, 2.5 GH/s drawing 110WAC is a whopping 44WAC/GH (at the wall) or 37.4WDC/GH (with an 85%-efficient PSU). Is it worth it?
BTW, thanks to CrazyGuy for an excellent service and packing.
December 10, 2013, 01:52:08 AM
Yes it is a dedicated 20 amp circuit that had the killiwatt on it. It was beeping from time to time as it was hitting the 15amp warning on the killiwatt. Its no longer plugged in, I just wanted to check the draw from the cubes.
I have two cubes on a 15, another one on a different 15, and five plus the switch on the 20.
I am definitely keeping an eye on things, and thanks for the warning.
-herener
I have two cubes on a 15, another one on a different 15, and five plus the switch on the 20.
I am definitely keeping an eye on things, and thanks for the warning.
-herener
December 10, 2013, 01:43:34 AM
I had a quad 5970 GPU rig ("The Minecart") back in the day running at about 1110 watts and plugged into a killawatt at all times. When I finally retired the machine, I realized the constant current had completely melted the plastic around the killawatt outlet. I'm always a little hesitent to go over 80% of any electrical component limits especially when running constant. Is that a 20 amp circuit you have those 5 cubes plugged into herener? Be careful out there...
December 10, 2013, 01:28:46 AM
Yea, I had five on high through this Kill-a-watt. 1718watts/5 is about 343.6watts each. I would use both cables to be safe. I did run two Cubes through one PSU for a bit and the PCIe power cable got much warmer than using a dedicated cable for each plug.
https://i.imgur.com/LmsYjG7.jpg?1
I'm also using the CX750M's on all Cubes.
https://i.imgur.com/MipJ8dq.jpg?1
I did have a problem with two cubes going all x's on me, had to switch out a PSU plug to another circuit.
-herener
https://i.imgur.com/LmsYjG7.jpg?1
I'm also using the CX750M's on all Cubes.
https://i.imgur.com/MipJ8dq.jpg?1
I did have a problem with two cubes going all x's on me, had to switch out a PSU plug to another circuit.
-herener
December 09, 2013, 10:18:05 PM
That psu includes 2 cables, each with 2 pcie connectors. Make sure you are using a single connector from each cable. I'm not sure that 1 cable can handle the full load required by high clock.
Agreed, but my measurements of the cube were 324 watts at high clock setting. Some have measured it at 350. That's really pushing the limits of a single cable, unless it's thick gauge.
December 09, 2013, 10:15:50 PM
That psu includes 2 cables, each with 2 pcie connectors. Make sure you are using a single connector from each cable. I'm not sure that 1 cable can handle the full load required by high clock.
December 09, 2013, 10:12:54 PM
Ok crazyguy, I have shipped 1 unit back to you out of 4. And looks like I am not the only one with blades out of position, and/or No network ethernet working but powering on. Anyway....I will check my others just in case...but they are fine.....and would like credit towards another unit from upcoming batch. I will PM you the tracking info.
Thanks,
sbfree.
Thanks,
sbfree.
December 09, 2013, 05:28:34 PM
Already tried that... Also am attempting to use BFGMINER proxy instead, however i'm getting the same results.
As soon as I click "CLOCK" it basically stop talking to the proxy instantly.
As soon as I click "CLOCK" it basically stop talking to the proxy instantly.
December 09, 2013, 05:23:55 PM
That psu includes 2 cables, each with 2 pcie connectors. Make sure you are using a single connector from each cable. I'm not sure that 1 cable can handle the full load required by high clock.
December 09, 2013, 04:36:42 PM
Looks Like I have to send 1 of 4 back. No Network card light, no status light but yet power ups. Looks like this cube was slammed together because the blades where not aligned with the grooves on the top inside of the case making it hard to pull out when it shouldn't. Not sure if that had anything to do with it but it sure wouldn't help. Something to look out for on any future shipments. Just an FYI. My other units are humming along.
2 are perfect and 1 w/ some x's on the chips but still hitting 30-35GH/s+.
thanks crazyguy.
sbfree
2 are perfect and 1 w/ some x's on the chips but still hitting 30-35GH/s+.
thanks crazyguy.
sbfree
December 09, 2013, 11:54:58 AM
December 09, 2013, 11:50:28 AM
Just the one.
What model PSU? December 09, 2013, 11:47:21 AM
Just the one.
December 09, 2013, 11:35:35 AM
Got My cube in the mail today,
Thanks CrazyGuy, for the Fast Responses, and shipping!! Would be happy to order from you again.
My cube however does appear to "crash" when setting the clock into "high", it restarts, then it wont connect to the proxy, until i power cycle it. My cube has firmware 9.17, is there an update or possible fix for this?
Thanks
My PSU: http://www.amazon.com/gp/product/B00ALK3KEM/ref=oh_details_o00_s00_i00?ie=UTF8&psc=1
Only running 1 cube off it, should be more then enough juice.
Thanks CrazyGuy, for the Fast Responses, and shipping!! Would be happy to order from you again.
My cube however does appear to "crash" when setting the clock into "high", it restarts, then it wont connect to the proxy, until i power cycle it. My cube has firmware 9.17, is there an update or possible fix for this?
Thanks
My PSU: http://www.amazon.com/gp/product/B00ALK3KEM/ref=oh_details_o00_s00_i00?ie=UTF8&psc=1
Only running 1 cube off it, should be more then enough juice.
I've found that setting the clock from some browsers does not work. I can't set the clock from mobile safari for some reason, but standard safari works fine. Which proxy are you using?
I tried other browser all did the same thing, as soon as I enable the clock to HIGH, it just basically stops getting data from the Proxy and the MHS display slowly goes to zero and then it stops hashing all together... I'm using Slush's: https://github.com/slush0/stratum-mining-proxy
When I first setup the device I had a lot of trouble getting it connect, however I no longer seem to have that problem any more. A Power Cycle of the cube will get it connect and working right away... and its stable. Is there a firmware update I can apply ? It seems like its just a bug in the code.
THanks
How many devices do you have hitting one proxy? I've found that there is a threshold where the proxy cannot provide enough work to all devices.
December 08, 2013, 10:01:38 PM
Got My cube in the mail today,
Thanks CrazyGuy, for the Fast Responses, and shipping!! Would be happy to order from you again.
My cube however does appear to "crash" when setting the clock into "high", it restarts, then it wont connect to the proxy, until i power cycle it. My cube has firmware 9.17, is there an update or possible fix for this?
Thanks
My PSU: http://www.amazon.com/gp/product/B00ALK3KEM/ref=oh_details_o00_s00_i00?ie=UTF8&psc=1
Only running 1 cube off it, should be more then enough juice.
Thanks CrazyGuy, for the Fast Responses, and shipping!! Would be happy to order from you again.
My cube however does appear to "crash" when setting the clock into "high", it restarts, then it wont connect to the proxy, until i power cycle it. My cube has firmware 9.17, is there an update or possible fix for this?
Thanks
My PSU: http://www.amazon.com/gp/product/B00ALK3KEM/ref=oh_details_o00_s00_i00?ie=UTF8&psc=1
Only running 1 cube off it, should be more then enough juice.
I've found that setting the clock from some browsers does not work. I can't set the clock from mobile safari for some reason, but standard safari works fine. Which proxy are you using?
I tried other browser all did the same thing, as soon as I enable the clock to HIGH, it just basically stops getting data from the Proxy and the MHS display slowly goes to zero and then it stops hashing all together... I'm using Slush's: https://github.com/slush0/stratum-mining-proxy
When I first setup the device I had a lot of trouble getting it connect, however I no longer seem to have that problem any more. A Power Cycle of the cube will get it connect and working right away... and its stable. Is there a firmware update I can apply ? It seems like its just a bug in the code.
THanks
Jump to: