Anybody here did test about this case ?

I have 10 Asic Cube running under proxy_mining, my pool = btcguild (same for all).

+ 06 of them are mining under my account/workers.
+ 02 of them running on 2nd Account/workers.
+ 02 rest running from 3rd account/workers.

After started few minutes the pool set Diff=256 for all cubes.

I'm wondering:
- For my 06 cubes's hashing = 180 - 235Gh/s ===> lower than 256.
- For 2nd account/worker. 02 cube hashing = 60 - 79Gh/s ===> lower than 256.
- 3rd Account is same with 2nd.

So... the question is: how this min Diff 256 does effect on each account/worker ? Is it make the shares faster upload to the pool or anything ?

Somebody tell me it's make the shares upload to pool faster and prevent "stale shares". Is it true?

Please help...

You guy have to setup extra cooling FAN @ front of CUBE to cooling all "jack" of PCI-E and fuses they getting hot all time.

I realize that my 10 cubes killed all Fuses before extra FANS added.

Any people here help me how to buy this devices please ?

I can pay via Paypal and BTC

Big thanksssss

There 2 products of AntMiner.

1. AntMiner U1 => USB. U need a PC to perform mining.
2. AntMiner S1 => Yes it's plug and play. Need PSU min. 360W with at lest 02 PCI-E (easiest way) and an extra FAN for cooling.

Could you help me step by step setup with BGFminer Newest Version? Because i get open and close right away. My Batch:

Payment for 1 HIGH CLOCK Cube, transaction and shipping address has sent via PM.  Thank you!

Hello Everyone ! I'm Xuan from VietNam.

First thank you for reading my topic and my problem issue. And ... sorry about my bad English

I've bough 2 ASICMiner Block Erupter Cube from Amazon's seller: Jones Gear

Unfortunately, at the first run one blade in first cube had 1 board dead 2 BE100 Chips. In cube's web control show like this in "LOW" clock mode

ASIC_49-64: x O O O O O O O x O O O O O O O

When mining ... the bigger problem that there are only M_01-16, M_17-32, M_33-48 do mining (working well, it's not show: 000 after almost 1 hour mining)
The rest chips from M_49-64, M_65-80, M_81-96 are look like standby. I did check the heat sink of them are still cool after 1 hour while other blade really hot.

And with "High" clock mode:

ASIC_33-48: x x x x x x x x O O O O O O O O
ASIC_49-64: x O O O O O O O x O O O O O O O

When do mining look like same problem on LOW clock mode, more and more chip are standby.

I did try to search around on internet for the blade diagram construction but there none exist.
So after 2 days can not sleep. I bring my board to a local "cellphone electric repair store" (the best store fixing dead cellphone's board) to ask them check those dead chips.

After 30 minutes they tell me that if possible bring them 1 BE100 Chip. I remember that i still have some ASICMiner Block Erupter USB 330MH/s. So i bring them 1 usb.

At first for testing:
They did take out BE100 CHIP on USB
Like picture below:


then "paste" them on the board at IC1 - BE100 Chip.


I've recheck the web control then suprise !!
The web show up:

ASIC_49-64: x O O O O O O O O O O O O O O O

Opsss => Is it meaning ... Fix the IC1 - BE100 .... make the 9th BE100 Chip come alive ?

At the end:
They do something like re-touch some where on the board at IC1 and ...

Bravo: ASIC_49-64: O O O O O O O O O O O O O O O O

But, this still not a big problem !!
After switch to "High" clock mode. Then the web control show like this:

ASIC_01-16: O O O O O O O O O O O O O O O O
ASIC_17-32: O O O O O O O O O O O O O O O O
ASIC_33-48: x x x x x x x O O O O O O O O O
ASIC_49-64: O O O O O O O O O O O O O O O O
ASIC_65-80: O O O O O O O O O x x x x x O O
ASIC_81-96: O O O O O O O O O O O O O O O O

A lot of x and x everywhere after each restarting.

So... finally, there is no way to use my this cube on HIGH clock mode. However, big thank to them that bring my all chip working again.
Now i have 1 cube running with High clock mode and another one in Low clock .

I did email to asicminer.help@gmail.com to hope if they can give me a "diagram construction" of the blade to identify exactly where each BE100 chipset locate on the board and show up on cube's web control.

If some body have same problem... you can try to fix it but please be notice that do with your own risk
To identify the blade, this picture may help you