Topic: [Sold Out] ASICMiner Cubes 30gh-38gh/s - USA .25 BTC - 4+ orders Free Shipping - page 10. (Read 14836 times)

I can't seem to post in this thread but I sent PM and Payment for 4 of these a few hours ago.

EDIT: Well I guess a post finally got through!

Testers are cranking through cubes tonight. All orders up to this point will be sent a 38gh/s verified unit tomorrow. Any orders past this point will likely be shipped Wednesday(Thursday due to holiday) as the testers catch up to incoming supply.

If you are fine with receiving and unverified cube, and don't care if it can clock high, please let me know and I will ship tomorrow.

PM + Payment Sent.

Payment for 2 Cubes, transaction and shipping send via PM.  Thank you!

PM Sent regarding payment.

I post this in case others may not be aware as I just learned it myself. When using the slush stratum proxy you of course need the server ip of the blade/cube to point to the ip of the computer the proxy is running on, but need to use real user_worker:123 for the pool it is pointed at. On multiple blades it would be the same.

On bfgminer, you MUST have unique user names for each blade/cube which is different then using slush's. If you don't, you will see a drop of 10 to 20%.

Again I apologize if this is old hat, but I was searching the bfgminer section for "blade" to see what I missed that they were not running at top speed and found this:

https://bitcointalk.org/index.php?topic=168174.msg3391532;topicseen#msg3391532

End result is on bfgminer you end up with a PXY for each blade/cube if you don't have a "PXY" for each cube/blade then you have duplicate id.s.

hit "d" for device manager and use the arrows to see what each "logged" user name is.

my blades for example are assigned .40 up so with bfgminer, the user:pass field if just use "bladexx:123" where xx is the ip of the blade to keep them unique and simple.

Sorry if this wasted space.

I will respond to all PMs later this evening. Please remember to include your transaction id, quantity ordered, and shipping address.

PM Sent regarding payment.

Payment sent. PM sent.

------- IMPORTANT Cube Prep ----------

It is imperative that you perform the following tasks upon receipt of your cube as some shifting has likely occurred during shipping.

1) Open the unit up and tighten the 4 heatsink screws on each blade. If there's a loose screw inside of the case, odds are it's missing from a heatsink. Don't ignore loose screws or throw them away!
2) Line the blades up in the upper rails of the case.

Notes:
When putting the cube back together, make sure to guide the red status led into the small hole on the fan side faceplate. If disregarded, it could possibly bend back and break off.

When tuning your cube, do not hit the browser refresh button after changing clock speed. The unit will cycle back and forth between clock speeds with each refresh of the SW_CLOCK page. Instead, use the UI's refresh button located at the bottom left of the screen.


Suggestions:

BFGMiner is a great application for running multiple cubes in one easy interface. However, I have found that it comes with a slight decrease in performance on cubes and Blades. If you are not seeing your cubes performing to their full potential, I suggest trying Slush's stratum proxy:

http://mining.bitcoin.cz/mining-proxy-howto

If you are experiencing performance loss when connecting many cubes or blades to one instance of Slush's stratum proxy, I suggest running multiple instances on separate ports.

Make sure you change settings on your pool to enable a minimum difficulty of 32 for each cube. This will result in lower bandwidth usage and prevent slowdown if running multiple units.

Setup Guide:

I highly recommend Dogie's Comprehensive ASICMiner Cube Setup guide
https://bitcointalksearch.org/topic/guide-dogies-comprehensive-asicminer-cube-setup-hd-352658