Topic: [PENDING] ASICMiner Cubes. 30-38gh/s - USA - 1 BTC - Price protection! (Read 18187 times)
December 17, 2013, 07:08:12 PM
Good news, my shipper has received a delivery from ASICMiner and I'm told there were no breathing holes! I'll be creating a new sale thread shortly after I receive details on the shipment.
December 17, 2013, 02:10:25 PM
Need to slap those guys around a bit. Haven't you been waiting on word for a week already?
Haha, no way man. Mess with friedcat and you're likely to get a very quick shipment. Unfortunately, it's going to be a box filled to the brim with nunchaku laden little people.
Seriously though, I think the cat is very busy with third gen, but I hope he's got another batch heading my way soon. I'll keep trying fellas.
December 17, 2013, 01:07:40 PM
Need to slap those guys around a bit. Haven't you been waiting on word for a week already?
December 17, 2013, 12:51:56 PM
ya got anymore?
Not yet, still waiting on word of shipment. I'll update the thread when I hear something.
December 17, 2013, 03:39:45 AM
ya got anymore?
December 16, 2013, 02:47:41 AM
Nice setup visdude, thanks for posting pics. I'm still trying to secure a 3rd batch and will let everyone know when I have word on shipment.
Thanks, CrazyGuy...and you're welcome. I look forward to your next GB.
December 16, 2013, 01:47:18 AM
Nice setup visdude, thanks for posting pics. I'm still trying to secure a 3rd batch and will let everyone know when I have word on shipment.
December 15, 2013, 11:50:56 PM
If I understand it, they're already working on the next gen chips. Took them a while to get started on it so no delivery until at least February. At least someone's making decent mid-entry hardware that's not built-for-n00bs or $4000.
I feel that the Cube is a culmination of their research for a platform to house their next-gen chips and the current Cube offering with the BE100 chips is just a dry run. If the anticipated chips are anything like the Bitfury 55nm chips (or better), then that would be exciting. Just imagine a yield of at least 200+ GH/s in a very attractive tiny 5.3" x 6.0" x 5.8" package drawing similar wattage as the current Cube. I also feel that USB connectivity (with the existing port) will be implemented then for mainstream appeal.
I couldn't agree with you more. AM has allowed us regular small-time miners to be significant part of the network. Still, just like with any other company or business, profit is paramount.
December 15, 2013, 11:23:40 PM
Does anyone had advice for trouble shooting a bad blade in a cube? Or is it even possible? The bad blade sometimes works but most of the time it will cause the entire cube to turn 'xxxx'. I switched power supplies and did a long troubleshooting process to ID the bade blade. I looked for any obvious damage but couldn't find any.
I should have posted my troubleshooting process...
Took the cube apart. Labeled blades 1-6. Removed all blades and tested each blade in each port on the main board. That took a bit. Finally found the bad blade. Tested the cube with the bad blade in each of the 6 ports to confirm.
Exactly - classic troubleshooting. Labeling and keeping track of what slots they were tried in will narrow it down. Don't change more than 1 variable at a time. That was the mistake I made with the hub issue. I know better but took a shortcut.
December 15, 2013, 11:13:46 PM
Does anyone had advice for trouble shooting a bad blade in a cube? Or is it even possible? The bad blade sometimes works but most of the time it will cause the entire cube to turn 'xxxx'. I switched power supplies and did a long troubleshooting process to ID the bade blade. I looked for any obvious damage but couldn't find any.
I should have posted my troubleshooting process...
Took the cube apart. Labeled blades 1-6. Removed all blades and tested each blade in each port on the main board. That took a bit. Finally found the bad blade. Tested the cube with the bad blade in each of the 6 ports to confirm.
December 15, 2013, 11:02:22 PM
I've got one that did the same thing, haven't narrowed down the source yet but I'll post about it when I do.
December 15, 2013, 10:59:04 PM
Does anyone had advice for trouble shooting a bad blade in a cube? Or is it even possible? The bad blade sometimes works but most of the time it will cause the entire cube to turn 'xxxx'. I switched power supplies and did a long troubleshooting process to ID the bade blade. I looked for any obvious damage but couldn't find any.
December 15, 2013, 07:27:04 PM
If I understand it, they're already working on the next gen chips. Took them a while to get started on it so no delivery until at least February. At least someone's making decent mid-entry hardware that's not built-for-n00bs or $4000.
December 15, 2013, 06:23:11 PM
I'm an admitted hardware geek and I like to take pictures of them. I took some while taking apart and prepping my Cube. I might as well share it. I hope CrazyGuy doesn't mind:
Thanks for the pic's !!!
Next time anyone has theirs apart I would like to see a pic straight on of the card tops meshing in the slots and of the bottom board again straight on in the slots of the bottom case.
I think that is where the problems are coming from. Asic miner put the cards in too tight in the slots. So any kind of pressure to the case top or bottom is putting pressure on the heat sinks and popping the cards/heatsink screws out. They probably should just flat pack the cards and let a little assembly be done on receipt or increase height of case and use a springy plastic grid retainer with groves to hold the card tops like better workstation class pc's have. Keeps the cards in their slot, but has enough give to accommodate shifts in the motherboard and or heat expansion.
my .0001
You're welcome.
Once the backplane and the blades are aligned to the notches/slots, they slide right in with hardly any effort; at least with mine anyway. I think it's just an issue of shoddy QC. I had to do some tightening of the plastic heat sink screws on the USB BEs too because about 80% of them were very loose. Overall, I grade the Cube's build "A". It's a nicely made and sturdy unit. However, I would have to give the chips in it a "C". Just imagine if they mounted at least 55nm chips on them. ASICMiner has to get with the times. But they're not gonna do it while they're still making money off the damn 130nm chips. They're milking it.
December 15, 2013, 11:35:44 AM
I'm an admitted hardware geek and I like to take pictures of them. I took some while taking apart and prepping my Cube. I might as well share it. I hope CrazyGuy doesn't mind:
Thanks for the pic's !!!
Next time anyone has theirs apart I would like to see a pic straight on of the card tops meshing in the slots and of the bottom board again straight on in the slots of the bottom case.
I think that is where the problems are coming from. Asic miner put the cards in too tight in the slots. So any kind of pressure to the case top or bottom is putting pressure on the heat sinks and popping the cards/heatsink screws out. They probably should just flat pack the cards and let a little assembly be done on receipt or increase height of case and use a springy plastic grid retainer with groves to hold the card tops like better workstation class pc's have. Keeps the cards in their slot, but has enough give to accommodate shifts in the motherboard and or heat expansion.
my .0001
December 15, 2013, 06:36:39 AM
I'm an admitted hardware geek and I like to take pictures of them. I took some while taking apart and prepping my Cube. I might as well share it. I hope CrazyGuy doesn't mind:
...and hashing away in good company:
...and hashing away in good company:
December 15, 2013, 06:19:38 AM
You guys are right. Slush's stratum proxy did get my Cube up to 37.9 GH/s on high clock. Close enough. Thanks again.
I started using the mining_proxy.exe a few days ago to use with my blades and I am very impressed. I wanted to try it because of the "no midstate" (-nm) option. I have been running it on my laptop and the blades efficiency are all running from 99.49% up to 99.71%. I miss the miner stats using this proxy. I use this laptop all day long to do my normal work and web viewing.I have not tried running the proxy without the -nm switch to compare yet. I have not figured out how to setup a backup pool with it yet.
Not to bash bfgminer any, as I use it for my BFL miners and my erupters, but as a proxy, my blades efficiency was 94-96%. I could not find a compatible switch to use for the no midstate option.
I did like being able to get the miner stats using bfgminer. It is also very easy to us another pool for backup mining.
Both have their pros and cons. Try them both and see which works best for you.
Thanks for the tip. For some reason, I only get up to 97% efficiency, even with Slush's proxy. I think I could live with it tough. BTW, what does the number labeled "Utility" right next to "Efficiency" represent?
December 14, 2013, 05:54:57 PM
You guys are right. Slush's stratum proxy did get my Cube up to 37.9 GH/s on high clock. Close enough. Thanks again.
I started using the mining_proxy.exe a few days ago to use with my blades and I am very impressed. I wanted to try it because of the "no midstate" (-nm) option. I have been running it on my laptop and the blades efficiency are all running from 99.49% up to 99.71%. I miss the miner stats using this proxy. I use this laptop all day long to do my normal work and web viewing.I have not tried running the proxy without the -nm switch to compare yet. I have not figured out how to setup a backup pool with it yet.
Not to bash bfgminer any, as I use it for my BFL miners and my erupters, but as a proxy, my blades efficiency was 94-96%. I could not find a compatible switch to use for the no midstate option.
I did like being able to get the miner stats using bfgminer. It is also very easy to us another pool for backup mining.
Both have their pros and cons. Try them both and see which works best for you.
December 14, 2013, 04:28:34 AM
You guys are right. Slush's stratum proxy did get my Cube up to 37.9 GH/s on high clock. Close enough. Thanks again.
December 13, 2013, 03:41:23 PM
Thanks, sidehack. I'll give it a shot.
Jump to: