[EU/UK GROUP BUY] Blue Fury USB miner 2.2 - 2.7 GH/s

[Slesh]

Hi OC3
 can you please answer on my 2 PM's about one pcs. of my delivery that was  DOA? thank you
Slesh

[OutCast3k]

Hi OC3
 can you please answer on my 2 PM's about one pcs. of my delivery that was  DOA? thank you
Slesh

I did respond to the first one, and I will answer the second once I'm sure of how I'm going to handle this and once I've worked out how many units there are to be returned. I've got a few people who need to return units and it makes sense to do everyone at once, I wasn't ignoring you or anything.

Will be in touch with everyone else who also needs to return a unit within the next 24 hours or so.

[Slesh]

Hi OC3
 can you please answer on my 2 PM's about one pcs. of my delivery that was  DOA? thank you
Slesh

OK, thanks ..

I did respond to the first one, and I will answer the second once I'm sure of how I'm going to handle this and once I've worked out how many units there are to be returned. I've got a few people who need to return units and it makes sense to do everyone at once, I wasn't ignoring you or anything.

Will be in touch with everyone else who also needs to return a unit within the next 24 hours or so.

[Jeffrey]

I also need to return one, sent a PM about it and waiting for answer. No need to reply to this as you just said you'll be replying soon, just an extra way to notice you about my dead miner.
Cheers

[timmybravo]

I appear to have a dead miner as well, it is detected in windows, but refuses to show up in bfgminer along with its brethren.

[OutCast3k]

I think i've got everyone accounted for now, will PM the instructions to everyone tomorrow so they can return them Monday.

[qukkM]

I may have one or two next week. Waiting for buyers to confirm they are dead.

[teletobi]

Seems like I have 4 not hashing Units.

[OutCast3k]

Right, I've accounted for all the extra faulty units that people messaged me about, since my last post.

The return address will be sent out in the next couple of hours, sorry for not doing it yesterday - I was unbelievably busy, but It doesn't make that much difference as obviously it couldn't have been posted until Monday.

*Edit* Instructions have been manually sent via PM. If you've got a faulty miner and have not yet received instructions, please get in touch.

[onryo]

Thx OutCast3k
SSH'd into the Debian armhf SoC about a day or two after kick off.
The Fury is doing Avg 2.77/ 2.58 Ghs. Just dropped a 0-25k SMD pot parallel over R15. With no fan I get about 4.5% HW error. With a fan HW Error is about 3.2%. Ill set it for about 2.7 GH/s and that will improve the error rate even more. No need to flash as Luke's code quills a lot of the issues.

https://i.imgur.com/gp8Lb8K.png

This is just a little side toy I am playing with. 3 BE, 1 "Blue Fury" and a 30 GH/s BFL on ARM SoC with a little Dlink DUB-H7. The OS is my own brew of Debian with a git pull from Luke-Jr from a few days back. Rock solid.

Might mod it by chaining in a a few more fury chips with their own power supplies and pcb board just for the “tinker factor”.
You don't have any bare bitfury chips to sell do you?

All the best
Onryo

[Beastlymac]

You can buy single bitfury chips from these two places.

http://www.bitfurystrikesback.com/product/bitfury-55nm-asic-chips/

https://megabigpower.com/shop/index.php?route=product/product&path=33&product_id=62

[HellDiverUK]

One of my miners has died.  On close inspection, it looks like the chip was installed with a bucket of solder and a 100W soldering iron.

How to I get a replacement?

[Markov]

Right, I've accounted for all the extra faulty units that people messaged me about, since my last post.

The return address will be sent out in the next couple of hours, sorry for not doing it yesterday - I was unbelievably busy, but It doesn't make that much difference as obviously it couldn't have been posted until Monday.

*Edit* Instructions have been manually sent via PM. If you've got a faulty miner and have not yet received instructions, please get in touch.

Hey Outcast, when do you think I can get mine? Have you posted them yet? Been waiting patiently but then you don't answer my PM. Maybe I should ask if you still have them?

Regards

[OutCast3k]

Right, I've accounted for all the extra faulty units that people messaged me about, since my last post.

The return address will be sent out in the next couple of hours, sorry for not doing it yesterday - I was unbelievably busy, but It doesn't make that much difference as obviously it couldn't have been posted until Monday.

*Edit* Instructions have been manually sent via PM. If you've got a faulty miner and have not yet received instructions, please get in touch.

Hey Outcast, when do you think I can get mine? Have you posted them yet? Been waiting patiently but then you don't answer my PM. Maybe I should ask if you still have them?

Regards

Hey mate,

As you wasn't able to come and collect it from me, I posted yours Friday - have you still not received it?

Will resend a tracking number now, and confirm the address it was shipped to via PM.

Sorry I didn't see your private message...

[Kenshin]

Thx OutCast3k
SSH'd into the Debian armhf SoC about a day or two after kick off.
The Fury is doing Avg 2.77/ 2.58 Ghs. Just dropped a 0-25k SMD pot parallel over R15. With no fan I get about 4.5% HW error. With a fan HW Error is about 3.2%. Ill set it for about 2.7 GH/s and that will improve the error rate even more. No need to flash as Luke's code quills a lot of the issues.



This is just a little side toy I am playing with. 3 BE, 1 "Blue Fury" and a 30 GH/s BFL on ARM SoC with a little Dlink DUB-H7. The OS is my own brew of Debian with a git pull from Luke-Jr from a few days back. Rock solid.

Might mod it by chaining in a a few more fury chips with their own power supplies and pcb board just for the “tinker factor”.
You don't have any bare bitfury chips to sell do you?

All the best
Onryo

How did you managed to get it to 2.7? I am also using the latest bfgminer. What commands are you using?

[HellDiverUK]

According to MinePeon, my remaining BlueFury was doing 3.5GH with 20% errors last night.  I'm not convinced it's telling the truth.

I'll do more investigation this evening...

[IYFTech]

"How did you managed to get it to 2.7? I am also using the latest bfgminer. What commands are you using?"

I believe it's called the pencil command 

[TheQuin]

"How did you managed to get it to 2.7? I am also using the latest bfgminer. What commands are you using?"

I believe it's called the pencil command 

Not exactly a command 

https://bitcointalk.org/index.php?topic=319419.msg3553170#msg3553170 - for the pencil mod.

[HellDiverUK]

Yep, the Staedtler Tradition 2B command.

More details here: http://www.staedtler.co.uk/tradition_uk

[onryo]

Thx OutCast3k
SSH'd into the Debian armhf SoC about a day or two after kick off.
The Fury is doing Avg 2.77/ 2.58 Ghs. Just dropped a 0-25k SMD pot parallel over R15. With no fan I get about 4.5% HW error. With a fan HW Error is about 3.2%. Ill set it for about 2.7 GH/s and that will improve the error rate even more. No need to flash as Luke's code quills a lot of the issues.

https://i.imgur.com/gp8Lb8K.png

This is just a little side toy I am playing with. 3 BE, 1 "Blue Fury" and a 30 GH/s BFL on ARM SoC with a little Dlink DUB-H7. The OS is my own brew of Debian with a git pull from Luke-Jr from a few days back. Rock solid.

Might mod it by chaining in a a few more fury chips with their own power supplies and pcb board just for the “tinker factor”.
You don't have any bare bitfury chips to sell do you?

All the best
Onryo

How did you managed to get it to 2.7? I am also using the latest bfgminer. What commands are you using?

I had about 2.23 GH/s at first like most here. Took a look at the PCB and realized the fury chip was a bit choked to prevent heat and USB power issues. R15 next to the button was set at 22k. Read that a value of 10k would be fine. By paralleling another resistor you get R= 1 /(1/R1 + 1/R2). Set a tiny SMD pot to about 19k (careful not to set to low!) and bridged the the 22k resistor for a total of about 10k. Did a reboot and was seeing about 2.84 GH/s. High error rate and the heat sink was getting really hot. A little increase on the pots resistance landed me at at an Avg of 2.78 GH/s and a report of 2.61 GH/s. Error 4.6%

 
So you have an idea of what you should be listing in your rc.local (using Debian armhf on a SoC)

Code:

ls /dev/tty*

To make sure you are really listing the right device (a /dev/ttyACMx) on the port see what is there.

Code:

udevadm info --query=all -n /dev/ttyACM0 | grep ID_VENDOR

A fury will show:

Code:

E: ID_VENDOR=BFMG
E: ID_VENDOR_ENC=BFMG
E: ID_VENDOR_FROM_DATABASE=Atmel Corp.
E: ID_VENDOR_ID=03eb

This is even more important for ttyUSB devices since BE and BFL etc all will show up as /dev/ttyUSB* stuff.

Just change the ttyUSB0 to ttyUSB1,2,3 …n. In my case this is the cmd in my;

Code:

/etc/rc.local

Code:

/usr/bin/screen -dmS bfgminer ./bfgminer -S bigpic:/dev/ttyACM0 -S erupter:/dev/ttyUSB0 -S erupter:/dev/ttyUSB1 -S erupter:/dev/ttyUSB2 --config /home/zion/.bfgminer/bfgminer.conf

If ports start changing on you give the -S noauto a read

This is even more important for ttyUSB* devices since BE and BFL etc all will show up as /dev/ttyUSB* stuff.
Just change the ttyUSB0 to ttyUSB1,2,3 …n.

Using screen like this with the -dmS will just kick off the command and detach while the S parameter gives it a nice name “bfgminer”.  

Anyway I have my fury set at 2.7 GH/s now and that seems to be “the sweet spot” on this thing. More or less what I got with a fury chip setup I built running at 0.84V @ 2.5A clocked at 230MHz. This thing should be easy to chain fury chips on...idk. If I can get hold of some bare chips Ill give it a shot...that is if I don't get some ANT (BM1380) chips sent to me first for another project.

Somebody said something about "the pencil mod cmd" lol, sure that might work too. Not sure I personally would do it that way.