[CLOSED] NanoFury NF1 USB stick - Group Buy + Product Assembly

[vs3]

PREORDER IS NOW CLOSED

UPDATE OCT/7 : We've now ordered all NanoFury NF1 devices for manufacturing. Everyone that placed an order has been sent an email with instructions for the second payment (which was also due to bitcointalk being down for several days). If you placed an order and did not get one with those instructions please send an email and PM to vs3 just in case and we'll get back to you

UPDATE OCT/2 : We'll be announcing the final price at some point tomorrow (while we confirm actual component prices today and tomorrow).
As announced on Oct/1 we can still accommodate a few more orders but they will not influence the price anymore. Cut-off date for any additional last-minute orders is Oct/6.

UPDATE OCT/1 : We might be able to accommodate a few extra orders before we've purchased all components.
Any orders received after the final price has been announced will be required to prepay them in full.
We'll be ordering all components and services on Oct/6 and there will be no exceptions after that's happened!

Orders placed after that will be automatically cancelled!

Group Buy And Product Assembly Announcement
for
NanoFury NF1 USB stick using 1 Bitfury chip offering approx. 2GH/s
(see second post for all technical details and third post for FAQ)

There are 2 options with this group buy with the following pricing:

- Assembly service only: You supply the chips, we do the rest. Includes full PCB assembly, PCB and components based on the NanoFury NF1 design.
Final price will depend on the quantities in this group buy. Current estimate is 0.3BTC (for less than 500 devices) to 0.2BTC (for over 3000 devices).
- Fully Assembled NF1 unit: Utilizes 1 BitFury ASIC chip to produce approx. 2gh/s per unit. Includes one BitFury chip and assembly service - full PCB assembly, PCB and components based on the NanoFury NF1 design.
Final price is currently estimated to be in the 0.3-0.6BTC range (depending on total quantities this GB attracts) and price of BitFury chip (currently anticipated in the 0.2-0.3BTC range pending announcement happening supposedly this weekend)

Above prices do not include shipping.

- PCB or DIY kit option: PCB only or PCB and all components in unsoldered form for those who like to solder. Please contact us individually with requests.


Payment (2 stage):

stage 1: Pre-order at 0.4BTC per NF1 device or 0.2BTC per device for assembly-only service. Closes Oct 1.
stage 2: By Oct 3 detailed final price including shipping options will be determined. By Oct 14 you'll be required to pay the remainder of that price and your pre-order price.


Target dates and anticipated schedule:

- Oct/1 - End of pre-order.
- Oct/3 - Final pricing announced (including shipping).
- Oct/6 - Components ordering. No cancellations after this date.
- Oct/11 - All Bitfury chips must be received for the assembly only service.
- Oct/14 - All components sent to assembly factory. All orders need to be fully paid.
- Oct/28-31 - Finished products received from assembly factory. Start of testing and shipping.

Note: all this presumes that everything goes as planned. There is always the possibility of something getting delayed which may cause the dates following it to slip. We have a few days of buffers here and there and hope that if any slippage does occur it will be limited to a week or so.


Shipping

Shipping prices will be as follows:

Within the US:
|----------------|------------|------------|---------|
|Service:        |First Class | Priority   | Express |
|Shipping time:* | 3-5 b.days | 2-3 b.days | 1 b.day |
|----------------|------------|------------|---------|
|Devices:        |            |            |         |
|1-3             |     $4     |    $6      |  $47    |
|4-12            |     $6     |    $6      |  $47    |
|13-70           |    $16     |   $16      |  $47    |
|71-125          |    $24     |   $24      |  $47    |
|126-250         |   free     |   free     |  $94    |
|250-500         |   free     |   free     |  $188   |
|501+            |   free     |   free     |  free   |
|----------------|------------|------------|---------|

International:
|----------------|-------------|-------------|------------|
|Service:        | First Class |   Priority  |   Express  |
|Shipping time:* |    varies   | 6-10 b.days | 3-5 b.days |
|----------------|-------------|-------------|------------|
|Devices:        |             |             |            |
|1-4             |      $12    |    $24      |    $100    |
|5-8             |      $21    |    $24      |    $100    |
|9-70            |      $65 ** |    $65      |    $100    |
|71-100          |      $85 ** |    $85      |    $100    |
|101-500         | $0.9/device | $0.9/device | $1/device  |
|501+            |    free     |   free      |  free      |
|----------------|-------------|-------------|------------|

Notes:
* - Shipping time is in Business Days (as per USPS)
** - International "First Class" for those amounts is same price as "Priority" so we'll automatically upgrade it to "Priority"

Terms

- Full payment is required prior to shipment to final destination.
- All purchases are processed in a First in, First out queue.
- Address signing is required for dispute settlement.
- We assume no responsibility for any issues that may arise due to circumstances outside our control, including but not limited to buzzdave failing to ship, shipment being seized by customs, shipment arriving late, etc.
- All NF1 devices will have a warranty against manufacturing defects for 30 days. There are no other expressed or implied warranties of any kind. Any modifications to the board void the warranty.
- You may choose to change your address a maximum of two times.
- In order to change your shipping address you must sign the change order with the purchase address.


Important notes. Please Read!

* 3000 devices is the target volume for this GB (50 have already been pre-ordered by myself )
If there are less than 300 orders we'll consider cancelling the GB and issuing a refund. We’re open to this discussion even if number of orders are a few more or a few less.

* Pricing is based on $120/BTC exchange rate as per Coinbase. If exchange rate changes significantly we’ll adjust the prices accordingly. That’s the exchange we’re using for now and that’s the rate that will matter.

* The prices above, including the BitFury ASIC chips, are tentative and subject to change pending finalization of all parts required. Each item which price has not been finalized includes an increased margin reflecting this uncertainty, and may be reduced.

* If final prince ends up being less than your initial deposit we’ll refund the BTC difference.

* Cancellations: You may cancel your order at any time prior closing of the group-buy. No cancellations will be accepted after that since we would have spent the money on the parts and services. All cancellations and refunds are subject to a 1% fee (which is how much we get charged).

* The NanoFury NF1 project is currently in a testing phase. Within a week or two we’ll know exactly how much hashing power it will produce, potential heat issues and all other details and limitations. We’ll be posting regular updates to this thread about that.

* We are a small team and have daytime jobs that give us enough free time to run this project. We also sleep at night. So please cut us a break if we don’t reply to posts and emails right away.
We will however try to address all questions and emails in a timely manner.
We're in Southern California, so expect most of our posts to occur in the morning and evening hours (Pacific time).

* We’ve seen what happened to Avalon and BFL preorders and we’re absolutely committed to not repeating their mistakes!
We will not spend a single cent of your money until we know that we can deliver what we promised! And if we can’t we’ll be refunding your money.
Currently there are two gotchas: 1) We are dependent on buzzdave (megabigpower.com) to deliver chips on time, and 2) we are dependent on him for reasonable chip pricing. Regarding #1 he has already stated that they have plenty of chips in stock, so currently our only concern is #2.


Purchase instructions (or HOW TO PLACE AN ORDER):

Until we get our online shop up please use the following procedure:

1. To calculate BTC required: Multiply the number of NF1 boards desired by NF board price (either Fully Assembled NF1 or Assembly-only service)
2. Send payment to: 1AHvViTD5wohPywNYHi8NZ8uPhbY9dZXCY
*Note* Do not send funds from an address you do not control. You will be required to prove ownership of the sending address upon request.
3. Sign and Email: nf1order[at]nanofury[dot]com (and just in case send also a PM) with the subject “NF1 Order”, and the following information in the body:


--------------------------
Forum Name:
First Name:
Last Name:
Street Address:
City:
State:
Zip Code:
Country:
Shipping type:
Phone Number:
Email Address:
Number of  NF1 boards:
Payment amount:
Service type: (Fully Assembled NF1 or Assembly-only)
Sending Address:
TX ID:
--------------------------
Signature:


* Please put the part of the message that you signed between the dashes (don't include the dashes so that we know from where to where to copy-paste; the slightest change - every single character, space, extra or missing one, etc will invalidate the signature).


 *See FAQ for questions.

[1715447497]

1715447497

[1715447497]

1715447497

[1715447497]

1715447497

[vs3]

Technical details

* No external power supply is required as the board is USB2.0-powered. If you want to run multiple units via a powered external USB hub you’ll need to get that separately. Powered USB hub is not included in this GB.

* For the same reason the hashing rate will be limited to about 2GH/s. (This is because the device can draw no more than 500mA from a standard USB 2.0 port). At this point we estimate that we should be able to achieve roughly 2GH with those power constraints, even though the chips have demonstrated up to 3.2GH/s. It is also possible that due to those limitations we may have to run the chips at a slightly slower hashing speeds (most likely not below 1.7-1.8GH/s), which on the good side will be controlled via software (cgminer) and depending on your specific USB hub you might be able to squeeze out a few more hashes.

* Overclocking: the board does permit some overclocking (with hardware modifications - see also “pencil mod”). Be aware though that if this exceeds the limits of your USB port your computer may just turn off the port completely. Also, with increase of speed you will get more heat. The chip and board is designed to use the back side as a heatsink, but if that’s not enough you may have to add an additional heatsink. For example - an external powered USB hub or a USB3.0 port may provide significantly more power, so if you want to you could experiment with higher core voltage (currently 0.81V).

* Final product will be a fully assembled and working board. There will be no (plastic) housing or heatsink as those just increase the price. At the announced hashing rate the board should not need any additional heatsink or cooling. Even though there are no harmful voltages on the board it is highly recommended that you avoid touching any of the components while running (mostly as you may disrupt the USB communication).

* Electric shock warning: If your computer is not properly grounded touching the board (or for that matter any metal part of the computer) while your computer is plugged in the wall outlet may result in an electric shock!
Please be safe - plug the device(s) in this order: first turn off and unplug your computer from the wall outlet, then connect all devices and then plug the computer back in the wall.
For unplugging the devices follow the same order - shut the computer down, unplug from the wall, unplug any devices and then plug the computer back into the outlet.
Even though modern power supplies provide proper insulation and the above scenario is unlikely nothing can guarantee that a power supply won’t suddenly go bad. So - PLEASE PLEASE PLEASE BE CAREFUL!

* This evaluation unit is intended for use for ENGINEERING DEVELOPMENT, DEMONSTRATION, OR EVALUATION PURPOSES ONLY and is not considered to be a finished end-product fit for general consumer use. Persons handling the product must have electronics training and observe good engineering practice standards. As such, the goods being provided are not intended to be complete in terms of required design-, marketing-, and/or manufacturing-related protective considerations, including product safety and environmental measures typically found in end products that incorporate such semiconductor components or circuit boards. This evaluation unit does not fall within the scope of the international or transnational directives regarding electromagnetic compatibility, restricted substances (RoHS), recycling (WEEE), FCC, CE or UL, and therefore may not meet the technical requirements of these directives or other related directives.




More images and albums:

The version 1 board: http://imgur.com/a/eCsVe
Version 2: http://imgur.com/a/OJy63
Version 5: http://imgur.com/a/rVI7o
Version 6: http://imgur.com/a/c4VgM (which is the final one)

Acknowledgments and other information:

* This project was inspired to a great extent by BKKCoin's Klondike K1 Nano Open Source Board and we're grateful for all his work and we'll continue to support his project down the road as we can!

* We've reused the same physical dimensions (including heatsink holes size and position) with the goal that if necessary we may share the same plastic hosing and/or heatsink. We are also planning to release this project as Open Source as well.

[vs3]

FREQUENTLY ASKED QUESTIONS

Emails received regarding questions outlined in this FAQ will be asked to review the information contained herein.

Purchasing

What is a TX ID?
A transaction ID is a number that is generated every time coins are moved from one address to another. In order to find the TX ID of your purchase you can right click and select “show transaction details” within the bitcoin-qt software, or go to blockchain.info and enter your payment address.

How do I sign a message?
In order to sign a verification message, you must use a wallet that supports this feature.
To sign a message with bitcoin-qt: click File, Sign Message. Input your sending address and message, and then click sign. The sending address, message, and signature must be included to verify the message.

When including a signed message, please use the following format:

Code:

--------------------------
Forum Name:
Name:
Street Address:
City:
State/Province:
Posta/ZIP Code:
Country:
Shipping type:
Phone Number:
Email Address:
Number of  NF1 boards:
Payment amount:
Service type: (Fully Assembled NF1 or Assembly-only)
Sending Address:
TX ID:
--------------------------
Signature: 

Do you accept reservations?
Purchases are on a first come, first serve basis, and all orders must be paid in full.

Can orders be split and/or transferred?
We are not responsible for any splits or transfers negotiated after purchase of the chips, nor will we facilitate any trades.

Can I pay with (Insert anything other than BTC here)
BTC is currently the only accepted form of payment.

Shipping

How do I pay for shipping?
Final fees, including shipping, will be calculated once the pre-order is done and included in the second payment stage. You will need to pay the final fees in order to receive your order.

[Beastlymac]

Wouldn't this be in the group buy section. Also looks similar to the k1. Good luck.

[vs3]

Wouldn't this be in the group buy section. Also looks similar to the k1. Good luck.

To be honest - I couldn't really tell which option is better since this is both a custom hardware _and_ a group buy .

And yes - the design is based on BKKCoin's K1 in terms of physical dimensions. We also kept the heatsink holes exactly the same - that's in case if a heatsink is needed so that we can reuse the same parts.

[darkfriend77]

interesting project ...

did you have a working prototype ... ? to test heat, power drain and hashrate ...

I'm unsure but from my experience, already getting 2 GH from one chip drains a lot more power and generates a lot more heat, then what they are supposed to use in there normal 1.5 GH running mod.

Did you calculated with that? ... Just looking at my own boards ... 1.6 more power drain .... fully cooled the pcb temp. went from 41° to 49° ... having front and back fans with 1200 rpm .... and most of the chips are still running under 2 GH ...

[MRKLYE]

Interesting.. You got the PCB's in hand?

[vs3]

Interesting.. You got the PCB's in hand?

It's on its way - according to FedEx:
Estimated delivery : Thur 9/12/2013 4:30 pm

[btceic]

Sigh.....
Please notify us when you have a video of a working prototype.

[vs3]

interesting project ...

did you have a working prototype ... ? to test heat, power drain and hashrate ...

I'm unsure but from my experience, already getting 2 GH from one chip drains a lot more power and generates a lot more heat, then what they are supposed to use in there normal 1.5 GH running mod.

Did you calculated with that? ... Just looking at my own boards ... 1.6 more power drain .... fully cooled the pcb temp. went from 41° to 49° ... having front and back fans with 1200 rpm .... and most of the chips are still running under 2 GH ...

To be quite honest I'm not concerned as much about the temperature. If we have to add a small heatsink - so be it. They're cheap. The board is already designed for one, so it will be just a matter of choice. The goal here is to get the most hashes for the $. If adding a $5 heatsink will get us 0.5GH more then that might be worth the effort. If adding it will give us 0.1-0.2GH then maybe not as much.

There were also plenty of notes on bitfury's FREE MONEY thread with feedback and also a lot on the Russian thread. According to this:

Latest test was done to maximize performance, while keeping chip temperature below 50 degrees C. A small heatsink was mounted on the bottom of the PCB, and cooled with a fan to control the temperature.

Vcore at 0.835 Volts, resulting in 2.5A current (2.1W). Clock frequency of 230 MHz. Instead of bitfury's test vectors, a test was done with 2048 more or less random vectors. Based on 756 cores, a yield of 1512 valid hashes would be expected, but 1511 were found, so COP is very close to 1.

Net hash rate would be almost 2.7 GH/sec @ 0.8W/GH.
https://i.imgur.com/g7UTw6V.jpg

In our case VCore will be lower - 0.800V-0.815V at least initially. There are also various options for the clock settings - instead of 54 bits we're looking at 53.

Also bitfury's test results using the same board - roughly translated via google-translate:

(...)
Measurements of the errors and hash rate values were done using the first 100 test vectors , the board is not actively cooled (impressive - running on a passive 2-layer board made ​​by Rene - intron - by the way big thanks to him) (...)
So the results : (...)
0.596 V, 45 Mhz, 0.39 Amps, 0.23 W, 100 tasks sent, 145 solutions got, COP is 1.0, Ideal 0.52 Gh / s, Real 0.52 Gh / s, 0.44 W / Gh / s
0.596 V, 96 Mhz, 0.725 Amps, 0.43 W, 100 tasks sent, 143 solutions got, COP is 0.986, Ideal 1.12 Gh / s, Real 1.1 Gh / s, 0.39 W / Gh / s

Please note that the 96 Mhz looks very close to the best solution ... After I started to raise the voltage without changing the settings of the oscillator - it was on purpose not voltage stabilized and its oscillation frequency should follow the supply voltage. What is most interesting that, when the oscillation frequency increases , the error-rate remained virtually unchanged, thanks to matching the characteristics of the oscillator transistor and transistor logic within a single crystal.

0.7 V 140 Mhz 1.2 Amps 0.84 W 100 tasks, 143 solutions got, COP is 0.986, Ideal 1.63 Gh / s, Real 1.6 Gh / s, 0.52 W / GH / s
0.8 V 180 Mhz 1.87 Amps 1.49 W 100 tasks, 139 solutions got, COP is 0.958, Ideal 2.093 Gh / s, Real 2 Gh / s, 0.75 W / GH / s
0.9 V 214 Mhz 2.62 Amps 2.36 W 100 tasks, 132 solutions got, COP is 0.91, Ideal 2.48 Gh / s, Real 2.26 Gh / s, 1.04 W / Gh / s.

Did not test any further - does not seem to have enough cooling.

So getting the 2GH is not the question. It is if the passive cooling will be sufficient. If we get better bang for the buck at 1.8GH then that may be the "stock" hashrate. The primary goal here is simplicity, even if that means that we may have to sacrifice a few hashes.

Have in mind that those chips are quite "overclockable" - there is nothing stopping you from trying to get 3.2GH/s. The board would likely still work just fine except that you'll then have to add some active cooling.

[vs3]

Sigh.....
Please notify us when you have a video of a working prototype.

The ultimate "show me the money" question

We'll definitely do that.

Hopefully it wouldn't take more than a week ( BFL^(TM) )

[jeezy]

If you would be willing to let John K escrow the BTC until you prove that you got it running with said specs and are ready to deliver, I'm sure you will get a lot more interest on this.

[vs3]

If you would be willing to let John K escrow the BTC until you prove that you got it running with said specs and are ready to deliver, I'm sure you will get a lot more interest on this.

Jeezy - I appreciate the feedback. We actually did consider the idea initially. But the more I look at it the more I don't see any real advantages. Instead of the extra 2% fees you can just keep an eye on the project and decide for yourself if you want to order or not. And besides - having escrow is really no guarantee that everything will happen the way everyone expects it. (just look at what happened to all of the Avalon group-buys with escrow). Since it really serves you no advantage, while it cost (your) money, and has the potential to slow the project and other headaches - we thought we'd rather save ourselves the hassle.

With all that said I want to add that I'm open to opening an escrow if that would make any difference. I just don't see the benefit - you may as well just wait a week or two, see the videos and then decide.

We are going to upload a video showing the product in the coming week or so anyways. I'm waiting for the nicer looking boards to arrive (as the engineering ones are not necessarily "pretty" ). We'll see how that goes. We may end up shooting them first anyways.

[miffman]

I would prefer to buy one once other people received it and so on.

[console_cowboy]

So will there be a way to overclock from software rather than having to resort to mild hardware modification? That's a pretty serious feature on the Bit Fury chips.

[philipma1957]

okay I would buy 10 fully assembled plug n play. so are we looking at 6btc for ten?

I have other questions will these run with bitminter's plug n play java client. I am running 100 asic miner sticks on bit minter as i type so this is a perfect upgrade item for me..

 10 of these would be 45 to 60 am sticks. frankly I am very adverse to any preorders no preorder has delivered correctly to me and I have 5 outstanding preorders.  so if I preorder 10 of these for 6btc how long before you want my coins oct 1 to  give the coins up to oct 31 to get gear is what I am reading.  

I am not sure I want to wait 30 days. I would have to think about it.

[bobsag3]

PM'ed

[dentldir]

Final price is currently estimated to be in the 0.3-0.6BTC range (depending on total quantities this GB attracts) and price of BitFury chip (currently anticipated in the 0.2-0.3BTC range pending announcement happening supposedly this weekend)

It seems punin has put up pricing for September chips, approximately 0.21633 BTC if I did the math correctly.

So the high end of the final estimated price per unit is 0.6BTC + 0.21633BTC = 0.81633 BTC correct?

[philipma1957]

Final price is currently estimated to be in the 0.3-0.6BTC range (depending on total quantities this GB attracts) and price of BitFury chip (currently anticipated in the 0.2-0.3BTC range pending announcement happening supposedly this weekend)

It seems punin has put up pricing for September chips, approximately 0.21633 BTC if I did the math correctly.

So the high end of the final estimated price per unit is 0.6BTC + 0.21633BTC = 0.81633 BTC correct?

  missed the high range which looks like it is too high for me. .

well at .81633btc  for 2gh it is okay,   but the oct 31 delivery  is a long time off.  adjustments will be:

sept 14  = 107  mill
sept 25  = 133  mill
oct 6     = 166  mill
oct 17   = 207  mill
oct 28   = 259  mill   these are 25% adjustments. 

I can get .333 ghs sticks in 3 days.

 6x .333= 2gh  =  6x .15 btc = about .9

 and I will be hashing  with the sticks by monday the 16th of sept. 

So as much as I want them to upgrade.
I will wait until sept 28-30th to commit.

[vs3]

Final price is currently estimated to be in the 0.3-0.6BTC range (depending on total quantities this GB attracts) and price of BitFury chip (currently anticipated in the 0.2-0.3BTC range pending announcement happening supposedly this weekend)

It seems punin has put up pricing for September chips, approximately 0.21633 BTC if I did the math correctly.

So the high end of the final estimated price per unit is 0.6BTC + 0.21633BTC = 0.81633 BTC correct?

dentldir sorry for the confusion - I guess I need to expand on the pricing box a bit more.

The anticipated final price (including BitFury chip AND assembly) is in the 0.3-0.6BTC range. It is made of two components: BitFury chip (0.2-0.3BTC anticipated for October delivery) plus assembly and all other components (which we anticipate to be in the 0.2-0.3BTC range depending on quantity).

So the high-end estimated final price is 0.6BTC at the moment.

[bitterdog]

Final price is currently estimated to be in the 0.3-0.6BTC range (depending on total quantities this GB attracts) and price of BitFury chip (currently anticipated in the 0.2-0.3BTC range pending announcement happening supposedly this weekend)

It seems punin has put up pricing for September chips, approximately 0.21633 BTC if I did the math correctly.

So the high end of the final estimated price per unit is 0.6BTC + 0.21633BTC = 0.81633 BTC correct?

dentldir sorry for the confusion - I guess I need to expand on the pricing box a bit more.

The anticipated final price (including BitFury chip AND assembly) is in the 0.3-0.6BTC range. It is made of two components: BitFury chip (0.2-0.3BTC anticipated for October delivery) plus assembly and all other components (which we anticipate to be in the 0.2-0.3BTC range depending on quantity).

So the high-end estimated final price is 0.6BTC at the moment.

Who is WE?

[vs3]

Final price is currently estimated to be in the 0.3-0.6BTC range (depending on total quantities this GB attracts) and price of BitFury chip (currently anticipated in the 0.2-0.3BTC range pending announcement happening supposedly this weekend)

It seems punin has put up pricing for September chips, approximately 0.21633 BTC if I did the math correctly.

So the high end of the final estimated price per unit is 0.6BTC + 0.21633BTC = 0.81633 BTC correct?

dentldir sorry for the confusion - I guess I need to expand on the pricing box a bit more.

The anticipated final price (including BitFury chip AND assembly) is in the 0.3-0.6BTC range. It is made of two components: BitFury chip (0.2-0.3BTC anticipated for October delivery) plus assembly and all other components (which we anticipate to be in the 0.2-0.3BTC range depending on quantity).

So the high-end estimated final price is 0.6BTC at the moment.

Who is WE?

The NanoFury team

[dentldir]

dentldir sorry for the confusion - I guess I need to expand on the pricing box a bit more.

The anticipated final price (including BitFury chip AND assembly) is in the 0.3-0.6BTC range. It is made of two components: BitFury chip (0.2-0.3BTC anticipated for October delivery) plus assembly and all other components (which we anticipate to be in the 0.2-0.3BTC range depending on quantity).

So the high-end estimated final price is 0.6BTC at the moment.

Excellent.  Thanks.

[junp]

0.4BTC for a stick is eccellent...
propabilly will never ROI, but I always can resell them!

So if I want to order 5 o 10 of them incl. shipping to Italy what I've to do?

The amount of 5 is 2BTC, right?

[philipma1957]

Final price is currently estimated to be in the 0.3-0.6BTC range (depending on total quantities this GB attracts) and price of BitFury chip (currently anticipated in the 0.2-0.3BTC range pending announcement happening supposedly this weekend)

It seems punin has put up pricing for September chips, approximately 0.21633 BTC if I did the math correctly.

So the high end of the final estimated price per unit is 0.6BTC + 0.21633BTC = 0.81633 BTC correct?

dentldir sorry for the confusion - I guess I need to expand on the pricing box a bit more.

The anticipated final price (including BitFury chip AND assembly) is in the 0.3-0.6BTC range. It is made of two components: BitFury chip (0.2-0.3BTC anticipated for October delivery) plus assembly and all other components (which we anticipate to be in the 0.2-0.3BTC range depending on quantity).

So the high-end estimated final price is 0.6BTC at the moment.

I will get some at the price of .3 btc fully assembled. 
I will commit to 6btc on sept 30. 

  so if it is the max price of .6 I get 10 sticks.

 if it is the min price of .3 I get 20 sticks. .

I will book mark this thread.

[vesperwillow]

Definitely watching, would be a neat fun factor evolution over the asicminer stick.

[philipma1957]

Definitely watching, would be a neat fun factor evolution over the asicminer stick.

 yeah if it is .4 btc  and is 2gh  at 2.5 watts it would be pretty nice.

 that is about 3x the price of an am stick but 6x the hash.  same watts

I have the hubs so it would be a lower setup cost for me. 

 I can run 100 sticks so 100 at 2gh would be good.

[tempestb]

Based on the schedule you're really in November by the time these are in my hands.  And that is only if everything goes perfect.  November, even with NO cost on power never returns their value.  And by never, I mean before I die of old age.  (Based on the Genesis Block)  At this point, the only safe play is to wait until these can be shipped on-demand to know what the difficulty level is and btc price.  Otherwise it's a loser.  Not to say I wouldn't like to have them, it's just that they won't actually make me any money.

[Swimmer63]

I'm interested in 25 if this GB starts to get going.

[bobsag3]

I'm interested in 25 if this GB starts to get going.

I have emailed/pmed them about it to 0 response

[vs3]

I'm interested in 25 if this GB starts to get going.

I have emailed/pmed them about it to 0 response

Hello bobsag,

we did exchange a few messages:

Is this what you're referring to?

Or was there another message? (which I may have somehow overlooked? and my apologies if that's the case)

[vs3]

=== PRICING UPDATE ===

With both punin and buzzdave now having officially released October pricing it seems the BitFury chips will be closer to the 0.2-0.25BTC range. If we exceed the initial target of 3000 devices that would put the final price also closer to 0.4-0.5BTC (as assembly and all other components will likely also get closer to 0.2-0.25BTC).

The final cost of course will be dependent on the number of devices this GB attracts. But even at the low range of 500 that still leads to a bit lower final price (than our initial estimates) which will likely be in the 0.50 - 0.55 BTC range.

We'll keep you posted.

[philipma1957]

=== PRICING UPDATE ===

With both punin and buzzdave now having officially released October pricing it seems the BitFury chips will be closer to the 0.2-0.25BTC range. If we exceed the initial target of 3000 devices that would put the final price also closer to 0.4-0.5BTC (as assembly and all other components will likely also get closer to 0.2-0.25BTC).

The final cost of course will be dependent on the number of devices this GB attracts. But even at the low range of 500 that still leads to a bit lower final price (than our initial estimates) which will likely be in the 0.50 - 0.55 BTC range.

We'll keep you posted.

I will still keep a 6btc commitment by sept 30th.

I will turn in  6btc.  hopefully I will get  15 sticks (.4btc each) for that rather then 11. (.55btc each)

[itod]

If we exceed the initial target of 3000 devices that would put the final price also closer to 0.4-0.5BTC (as assembly and all other components will likely also get closer to 0.2-0.25BTC).

Will this design be opensource? I'm asking this because I think components + assembly can be lower than 0.2-0.25, especially if you consider + shipping costs for us European based. If not, please don't forget the kit option you've mentioned in opening post.

[bitterdog]

Where are you located in SoCal?

[bigbeninlondon]

@.4 I'm in for 10

[vesperwillow]

I would certainly buy a whole bunch if their total cost was .2btc plus shipping.

[Xian01]

I'm interested in 100 of these @ 0.3 BTC

[vs3]

If we exceed the initial target of 3000 devices that would put the final price also closer to 0.4-0.5BTC (as assembly and all other components will likely also get closer to 0.2-0.25BTC).

Will this design be opensource? I'm asking this because I think components + assembly can be lower than 0.2-0.25, especially if you consider + shipping costs for us European based. If not, please don't forget the kit option you've mentioned in opening post.

On the several questions:

Open Source: Yes. We need to iron out a few legalities but the goal is to release the entire project as open source. We'll probably do a similar thing as BKKCoin.

EU Assembly: We've been in talks with Marto74 and we're seriously considering to manufacture some boards there and ship EU orders from there. It isn't impossible that we end up making all boards there (as we're still negotiating with two assembly houses here in the US).

DYI Kit option: the only reason why we didn't put it up from day one is that it is really such a hassle to cut out tapes and count and package tiny components
But if there is enough interest we'll probably hire some unfortunate local soul and will offer that option. A rough pricing estimate for the DYI Kit option is 0.1BTC (+ BitFury chip's price) and I might be off +/- a bit depending on how much we end up paying for shipping.

[itod]

But if there is enough interest we'll probably hire some unfortunate local soul and will offer that option. A rough pricing estimate for the DYI Kit option is 0.1BTC (+ BitFury chip's price) and I might be off +/- a bit depending on how much we end up paying for shipping.

Don't you worry about the interest for DIY kit option at 0.1BTC + chip price, people will by them in dozens. This is only realistic positive ROI option for small miners and hobbyists.

[vesperwillow]

But if there is enough interest we'll probably hire some unfortunate local soul and will offer that option. A rough pricing estimate for the DYI Kit option is 0.1BTC (+ BitFury chip's price) and I might be off +/- a bit depending on how much we end up paying for shipping.

Don't you worry about the interest for DIY kit option at 0.1BTC + chip price, people will by them in dozens. This is only realistic positive ROI option for small miners and hobbyists.

I think what he means is, if there's enough preorders.

[RicRock]

So do we need to preorder @ 0.4 or 0.3 per unit?

nvm, will figure 0.4

[bitterdog]

Id be in for 100-200 units @ BTC0.3-0.4

But 1st Id like to see some actual pictures and some video.

[ipxtreme]

Id be in for 100-200 units @ BTC0.3-0.4

But 1st Id like to see some actual pictures and some video.

Bitterdog: I am interested why you would buy 200 at 0.4 btc each? Are you going to mine with them?

200 at 2gh = 400gh
200 x 0.4 btc = 80 btc
80 btc x $140 USD = $11,200 for 400 gh

If you buy a KNC Saturn for 400gh it only costs $5,000.

[bitterdog]

Id be in for 100-200 units @ BTC0.3-0.4

But 1st Id like to see some actual pictures and some video.

Bitterdog: I am interested why you would buy 200 at 0.4 btc each? Are you going to mine with them?

200 at 2gh = 400gh
200 x 0.4 btc = 80 btc
80 btc x $140 USD = $11,200 for 400 gh

If you buy a KNC Saturn for 400gh it only costs $5,000.

I have no interest in mining with them. The profit is in the Hardware selling not the mining.

These appear to be using Bitfury chips. im guessing that 2GH/s is on the low conservative end. Im guessing more like 2.5GH/s - 2.7GH/s

[ipxtreme]

Want to pre-order but not sure how much to pay. I have been reading this thread for about 1 hour now.

[vs3]

Id be in for 100-200 units @ BTC0.3-0.4

But 1st Id like to see some actual pictures and some video.

Bitterdog: I am interested why you would buy 200 at 0.4 btc each? Are you going to mine with them?

200 at 2gh = 400gh
200 x 0.4 btc = 80 btc
80 btc x $140 USD = $11,200 for 400 gh

If you buy a KNC Saturn for 400gh it only costs $5,000.

I have no interest in mining with them. The profit is in the Hardware selling not the mining.

These appear to be using Bitfury chips. im guessing that 2GH/s is on the low conservative end. Im guessing more like 2.5GH/s - 2.7GH/s

Bitterdog - that is correct. We're on purpose limiting it to about 2GH for two reasons:
1) and that's the bigger one - power consumption. A standard USB2.0 port provides about 2.5W so with some losses in conversion and in the other components we're likely looking at max 2W for the BitFury chip. There are two possible solutions if you want to overclock the chip: USB3 provides almost twice as much power, or you can use a powered USB hub that provides more power (and some of the newer such hubs actually don't quite follow the USB2 limits and let you draw more)
2) heat issues: the higher the voltage and speed the more heat is produced. We're already considering adding a small heatsink, but overclocking it will likely require a bigger one.

ipxtreme - the main reason why I first started looking at a solution like this is - I wanted something small and simple (the KISS principle) - I don't want RasPI, external power supplies, or messy stuff like watercooling, etc. I wanted also something that would let me easily experiment with - if I wanted to overclock/underclock it, etc and something that won't cost me a fortune when I burn it. (because with experimenting that's not a matter of if but of when )

[vs3]

Want to pre-order but not sure how much to pay. I have been reading this thread for about 1 hour now.

hmm... maybe we should redo the opening post

OK, here is the shortest/simplest answer:

If you want full devices - that's 0.4BTC per device now,
If you have your own bitfury chips and want them just assembled into our device - that's 0.2BTC per device now,
and by Oct/3 we'll know exactly how much the final price is going to end up being and you'll need to send us the remainder.

[ipxtreme]

Want to pre-order but not sure how much to pay. I have been reading this thread for about 1 hour now.

hmm... maybe we should redo the opening post

OK, here is the shortest/simplest answer:

If you want full devices - that's 0.4BTC per device now,
If you have your own bitfury chips and want them just assembled into our device - that's 0.2BTC per device now,
and by Oct/3 we'll know exactly how much the final price is going to end up being and you'll need to send us the remainder.

Thanks VS3. I am only interested in assembled product so I can plug in and go.

So if I buy 1, it will be 0.4 btc now plus an unknown amount on  Oct 3 for shipping? Wouldn't shipping be about the same as other distros like 0.05 btc per shipment up to so many units?

I want to buy but if I am in at 0.4 plus another 0.4 on Oct 3rd for shipping, so 0.8 btc for 1 unit. That's why I am wondering....

[Unacceptable]

Want to pre-order but not sure how much to pay. I have been reading this thread for about 1 hour now.

hmm... maybe we should redo the opening post

OK, here is the shortest/simplest answer:

If you want full devices - that's 0.4BTC per device now,
If you have your own bitfury chips and want them just assembled into our device - that's 0.2BTC per device now,
and by Oct/3 we'll know exactly how much the final price is going to end up being and you'll need to send us the remainder.

Thanks VS3. I am only interested in assembled product so I can plug in and go.

So if I buy 1, it will be 0.4 btc now plus an unknown amount on  Oct 3 for shipping? Wouldn't shipping be about the same as other distros like 0.05 btc per shipment up to so many units?

I want to buy but if I am in at 0.4 plus another 0.4 on Oct 3rd for shipping, so 0.8 btc for 1 unit. That's why I am wondering....

I thought the .40BTC price was for the board & parts assembled ONLY...........chip was extra.Did I misunderstand this

A fully assembled unit w/chip @ .40 BTC + shipping,of course 

[vs3]

Want to pre-order but not sure how much to pay. I have been reading this thread for about 1 hour now.

hmm... maybe we should redo the opening post

OK, here is the shortest/simplest answer:

If you want full devices - that's 0.4BTC per device now,
If you have your own bitfury chips and want them just assembled into our device - that's 0.2BTC per device now,
and by Oct/3 we'll know exactly how much the final price is going to end up being and you'll need to send us the remainder.

Thanks VS3. I am only interested in assembled product so I can plug in and go.

So if I buy 1, it will be 0.4 btc now plus an unknown amount on  Oct 3 for shipping? Wouldn't shipping be about the same as other distros like 0.05 btc per shipment up to so many units?

I want to buy but if I am in at 0.4 plus another 0.4 on Oct 3rd for shipping, so 0.8 btc for 1 unit. That's why I am wondering....

I thought the .40BTC price was for the board & parts assembled ONLY...........chip was extra.Did I misunderstand this

A fully assembled unit w/chip @ .40 BTC + shipping,of course 

Yes - 0.4 per board is the initial payment for a fully assembled one INCLUDING a bitfury chip and the second payment would be the remainder to the final price (whatever that end up being based on the number of devices we manufacture) plus shipping.

That's how we ended up with that price:

=== PRICING UPDATE ===

With both punin and buzzdave now having officially released October pricing it seems the BitFury chips will be closer to the 0.2-0.25BTC range. If we exceed the initial target of 3000 devices that would put the final price also closer to 0.4-0.5BTC (as assembly and all other components will likely also get closer to 0.2-0.25BTC).

The final cost of course will be dependent on the number of devices this GB attracts. But even at the low range of 500 that still leads to a bit lower final price (than our initial estimates) which will likely be in the 0.50 - 0.55 BTC range.

We'll keep you posted.

[vs3]

Want to pre-order but not sure how much to pay. I have been reading this thread for about 1 hour now.

hmm... maybe we should redo the opening post

OK, here is the shortest/simplest answer:

If you want full devices - that's 0.4BTC per device now,
If you have your own bitfury chips and want them just assembled into our device - that's 0.2BTC per device now,
and by Oct/3 we'll know exactly how much the final price is going to end up being and you'll need to send us the remainder.

Thanks VS3. I am only interested in assembled product so I can plug in and go.

So if I buy 1, it will be 0.4 btc now plus an unknown amount on  Oct 3 for shipping? Wouldn't shipping be about the same as other distros like 0.05 btc per shipment up to so many units?

I want to buy but if I am in at 0.4 plus another 0.4 on Oct 3rd for shipping, so 0.8 btc for 1 unit. That's why I am wondering....

We'll be posting a separate update with the shipping details (hopefully by the end of this week). USPS has some insane prices, and in some cases it is both faster AND cheaper to ship via FedEx/UPS ground.

[ipxtreme]

Want to pre-order but not sure how much to pay. I have been reading this thread for about 1 hour now.

hmm... maybe we should redo the opening post

OK, here is the shortest/simplest answer:

If you want full devices - that's 0.4BTC per device now,
If you have your own bitfury chips and want them just assembled into our device - that's 0.2BTC per device now,
and by Oct/3 we'll know exactly how much the final price is going to end up being and you'll need to send us the remainder.

Thanks VS3. I am only interested in assembled product so I can plug in and go.

So if I buy 1, it will be 0.4 btc now plus an unknown amount on  Oct 3 for shipping? Wouldn't shipping be about the same as other distros like 0.05 btc per shipment up to so many units?

I want to buy but if I am in at 0.4 plus another 0.4 on Oct 3rd for shipping, so 0.8 btc for 1 unit. That's why I am wondering....

We'll be posting a separate update with the shipping details (hopefully by the end of this week). USPS has some insane prices, and in some cases it is both faster AND cheaper to ship via FedEx/UPS ground.

Small USPS priority box is $5.80 shipped anywhere in US. The box is even free at the post office. I use it every day for shipping needs.

[RicRock]

We'll be posting a separate update with the shipping details (hopefully by the end of this week). USPS has some insane prices, and in some cases it is both faster AND cheaper to ship via FedEx/UPS ground.

Small USPS priority box is $5.80 shipped anywhere in US. The box is even free at the post office. I use it every day for shipping needs.

Yeah... I'd think USPS would be the cheapest

[Unacceptable]

Even the generic,manila padded envolopes are ok for these,thats how I got my BE's shipped to me & no damage & I think the total was $3.80,shipped inside the US  

[thomas_s]

I've used USPS, while I do hate them profusely the flat rate boxes I love.

If you do online purchasing of the shipping you get a small discount around 60 cents or so for the small box (but adds up when you ship hundreds of packages).
For smaller pieces you can ship first class mail sometimes fairly cheap.
International can be done in the flat rate boxes.

But and this is a huge but....if the price goes anywhere near the cost for UPS or Fedex I will immediately ship that package without hesitation with that carrier. ($12 or so)

[bigbeninlondon]

Even the generic,manila padded envolopes are ok for these,thats how I got my BE's shipped to me & no damage & I think the total was $3.80,shipped inside the US  

up to 3 oz is $1.69 for First Class shipping.  $1.86 for 4 oz.  I bet these things are 1.5 oz, plus .5 oz for the padded envelope.  100 padded envelopes can be had on eBay for about $20.  That's about $3 for total shipping first class.

[thomas_s]

Even the generic,manila padded envolopes are ok for these,thats how I got my BE's shipped to me & no damage & I think the total was $3.80,shipped inside the US  

up to 3 oz is $1.69 for First Class shipping.  $1.86 for 4 oz.  I bet these things are 1.5 oz, plus .5 oz for the padded envelope.  100 padded envelopes can be had on eBay for about $20.  That's about $3 for total shipping first class.

You can get shipping supplies much cheaper by ordering from shipping supply suppliers that specialize in packaging. Usually the downside that increases the cost of the order is the shipping but if your ordering cases of w/e your ordering the price is next to nothing compared to what you can get ordering off ebay.

The shipping can also get cheaper if you have a commercial account and are able to process your shipments correctly, I've worked for places and shipped items with UPS for $4 a package (not tiny light packages ~20lbs each) and the center that I worked at didn't even do a ton of shipping maybe around 100 packages a day (with ups) another 50-100 by messenger.

[philipma1957]

ship to the 50 states in a small flat rate box.  it runs about 5-6 bucks.  give the buyer the chance to send a label to you.  like canaryinthemine does..    and force buyers to purchase at least 2 sticks.  the 2 stick minimum  purchase rule would help your handling costs a lot.  also a buyer that purchases 2 sticks is more then happy to spend for tracking and free 50 dollar insurance.  at least he should be.

you have to understand your market upside is huge! why?

 30 k am sticks have been sold by canary in the mine.  and at least 10 k by silent sonic boom

 that means lots of people have hubs   giving them an upgrade from 3.3 gh on a 10 port hub to 20gh is golden.

[vesperwillow]

Yup! Totally agree with what he said. Plus, it would force the cost of the other miners down, or force their buyers to look this way.

[philipma1957]

Yup! Totally agree with what he said. Plus, it would force the cost of the other miners down, or force their buyers to look this way.

I mine about 90 am sticks. I can mine 150 sticks no problem. (i i have the hubs and have mined at 137 so far as a max.)


 I sold about 200 am sticks on ebay.

  I am drooling at this new product it would allow good sales on ebay and allow me to upgrade my personal mine.

[Swimmer63]

Want to pre-order but not sure how much to pay. I have been reading this thread for about 1 hour now.

hmm... maybe we should redo the opening post

OK, here is the shortest/simplest answer:

If you want full devices - that's 0.4BTC per device now,
If you have your own bitfury chips and want them just assembled into our device - that's 0.2BTC per device now,
and by Oct/3 we'll know exactly how much the final price is going to end up being and you'll need to send us the remainder.

I will order at least 10. How close/far away are we from 3000.

[tk1337]

Interested in grabbing a some...

But (and I'm sure this is answered somewhere in this thread, just have a headache and don't feel like searching atm) not sure  what the estimated price range will be for the remainder after the 0.40BTC initial. Will try to keep an eye on this thread and read more tomorrow.

[vs3]

Interested in grabbing a some...

But (and I'm sure this is answered somewhere in this thread, just have a headache and don't feel like searching atm) not sure  what the estimated price range will be for the remainder after the 0.40BTC initial. Will try to keep an eye on this thread and read more tomorrow.

I'll be updating the opening post tomorrow and for now the latest pricing information is in the PRICING UPDATE post : https://bitcointalk.org/index.php?topic=291456.msg3150508#msg3150508

[vs3]

ship to the 50 states in a small flat rate box.  it runs about 5-6 bucks.  give the buyer the chance to send a label to you.  like canaryinthemine does..    and force buyers to purchase at least 2 sticks.  the 2 stick minimum  purchase rule would help your handling costs a lot.  also a buyer that purchases 2 sticks is more then happy to spend for tracking and free 50 dollar insurance.  at least he should be.

you have to understand your market upside is huge! why?

 30 k am sticks have been sold by canary in the mine.  and at least 10 k by silent sonic boom

 that means lots of people have hubs   giving them an upgrade from 3.3 gh on a 10 port hub to 20gh is golden.

Shipping to the 50 states is a given. For small orders (less than 10 units) it is most likely going to be USPS. For larger orders USPS is not as competitive - for example 2lb box will get from Los Angeles to Seattle in 2 days with either USPS or FedEx ground, except that FedEx is half the price. Anyways - my point is - there are options and we'll look at the ones that make most sense.

If you want to send me a prepaid shipping label - I'm fine with that too. I guess in that case we'll just have a flat buck or two charge to cover for the shipping materials and the unfortunate soul that will be in charge of wrapping, packaging and shipping everything.

Insurance - in my opinion it should be included in every order, but I am inclined to leave it optional for now.

Anyways - more details will be in the shipping update coming at some point later in the week.

[bobsag3]

ship to the 50 states in a small flat rate box.  it runs about 5-6 bucks.  give the buyer the chance to send a label to you.  like canaryinthemine does..    and force buyers to purchase at least 2 sticks.  the 2 stick minimum  purchase rule would help your handling costs a lot.  also a buyer that purchases 2 sticks is more then happy to spend for tracking and free 50 dollar insurance.  at least he should be.

you have to understand your market upside is huge! why?

 30 k am sticks have been sold by canary in the mine.  and at least 10 k by silent sonic boom

 that means lots of people have hubs   giving them an upgrade from 3.3 gh on a 10 port hub to 20gh is golden.

Shipping to the 50 states is a given. For small orders (less than 10 units) it is most likely going to be USPS. For larger orders USPS is not as competitive - for example 2lb box will get from Los Angeles to Seattle in 2 days with either USPS or FedEx ground, except that FedEx is half the price. Anyways - my point is - there are options and we'll look at the ones that make most sense.

If you want to send me a prepaid shipping label - I'm fine with that too. I guess in that case we'll just have a flat buck or two charge to cover for the shipping materials and the unfortunate soul that will be in charge of wrapping, packaging and shipping everything.

Insurance - in my opinion it should be included in every order, but I am inclined to leave it optional for now.

Anyways - more details will be in the shipping update coming at some point later in the week.

I can ship a 2lb box 2 days for 5.99, 1.95 and ~16... all via flat rate, and the boxes are free.
I got a quote for shipping a 100 blades to UK via fedex/ups, and then USPS, and it was no contest USPS

[Molex1701]

So this is one of those bring your own chip deals?

[lano1106]

I am monitoring this thread. Could be interested in reserving 20-25 NF1s.

The only things missing are:

1. I hate to hand over money to strangers. Have you conducted successfully GB in the past?
2. So far, you are only pseudonyms on a online forum, Can you share real life identity of the NF1 members and contact info?
3. I am waiting to see a video of a working prototype.
4. I have red this thread and you really like to know what you're talking about. I would like to know if this is your first electronic project or if you have accumulated a serie of similar realisations in the electronic field and/or if you have relevent professional background that would help potential customers to trust your ability to fulfill this project successfully.

If you're able to address these points, I am pretty that I will be interested to invest in this venture and probably many more will with these info as well.

Good luck and be your enterprise successful!

[ajw7989]

I am definitely interested in purchasing some depending when the product will ship and the final price

[vs3]

So this is one of those bring your own chip deals?

That is indeed one of the two options. We can use your chips, or we can buy the chips on your behalf.

[vs3]

I am monitoring this thread. Could be interested in reserving 20-25 NF1s.

The only things missing are:

1. I hate to hand over money to strangers. Have you conducted successfully GB in the past?
2. So far, you are only pseudonyms on a online forum, Can you share real life identity of the NF1 members and contact info?
3. I am waiting to see a video of a working prototype.
4. I have red this thread and you really like to know what you're talking about. I would like to know if this is your first electronic project or if you have accumulated a serie of similar realisations in the electronic field and/or if you have relevent professional background that would help potential customers to trust your ability to fulfill this project successfully.

If you're able to address these points, I am pretty that I will be interested to invest in this venture and probably many more will with these info as well.

Good luck and be your enterprise successful!

Hi,

on the various questions:

#2 : I understand your concerns. Would it work for you if I provide my info to John K? For a number of reasons I would prefer not to publish team members personal info.

#3 : We're working hard on that. Getting the chips running is one thing. Rewriting the mining software to support them - quite a different challenge. We've been in talks with several mining software developers (ckolivas, luke_jr and DrHaribo to name a few).
While we're probably going to launch with limited support for just cgminer we are also going to provide those developers hardware and whatever further assistance they need for incorporating support for NF1 in their miners. This however may not happen right away and most likely after we have the mass-produced miners. We've set aside about a dozen devices to be sent out to developers for that specific reason.

#1 and to some extent #4 : I have been in the electronics and software field for over 20 years (I think one of my first hardware+software projects was presented at an exhibition in 1991). I've been working for example with Microchip PIC's microcontrollers when they only had 16C84 (including the one with the software protection bug). Over the last decade I've designed and executed a number projects from end to end - and I mean here from designing the schematics, through writing the software and organizing the entire manufacturing process (including procuring of materials, services, etc) to setting up industrial-scale Q&A and testing for finished products. Compared to some of those projects this one is rather tiny.
Have I done a GB specifically on bitcointalk.org - no, that's the first such GB. Nonetheless - I know first hand (and in details) exactly what's involved in every step. Some of the other team members have been coding for even longer than me. I'm okay also providing JohnK our team members LinkedIn profiles.

Please PM me if I missed anything as I would prefer not to go too much off-topic

[Molex1701]

So this is one of those bring your own chip deals?

That is indeed one of the two options. We can use your chips, or we can buy the chips on your behalf.

So if I can get in .4 by oct 1st I can get one assembled  with a chip?  Then maybe .3 more when done?
Thanks.

[vs3]

So this is one of those bring your own chip deals?

That is indeed one of the two options. We can use your chips, or we can buy the chips on your behalf.

So if I can get in .4 by oct 1st I can get one assembled  with a chip?  Then maybe .3 more when done?
Thanks.

The 0.3 second payment (after the final price is clarified) would actually most likely be less than 0.2 (and we're hoping for 0.1) so that the final price would be in the 0.5 range (although if we attract fewer orders than anticipated we may have to buy bitfury chips at higher price - e.g. zefir's 0.27BTC/chip which would result in final price around 0.6).

[Aggrophobia]

0.5 is not attracting people, so you will get less orders than expected

[bigbeninlondon]

So this is one of those bring your own chip deals?

That is indeed one of the two options. We can use your chips, or we can buy the chips on your behalf.

So if I can get in .4 by oct 1st I can get one assembled  with a chip?  Then maybe .3 more when done?
Thanks.

The 0.3 second payment (after the final price is clarified) would actually most likely be less than 0.2 (and we're hoping for 0.1) so that the final price would be in the 0.5 range (although if we attract fewer orders than anticipated we may have to buy bitfury chips at higher price - e.g. zefir's 0.27BTC/chip which would result in final price around 0.6).

The problem here is that the final price is unknown and policy states I have to commit without knowing the price.  Can you guarantee that .6 is the ceiling?  I'm a small buyer but I imagine the sentiment is the same. 

[vs3]

So this is one of those bring your own chip deals?

That is indeed one of the two options. We can use your chips, or we can buy the chips on your behalf.

So if I can get in .4 by oct 1st I can get one assembled  with a chip?  Then maybe .3 more when done?
Thanks.

The 0.3 second payment (after the final price is clarified) would actually most likely be less than 0.2 (and we're hoping for 0.1) so that the final price would be in the 0.5 range (although if we attract fewer orders than anticipated we may have to buy bitfury chips at higher price - e.g. zefir's 0.27BTC/chip which would result in final price around 0.6).

The problem here is that the final price is unknown and policy states I have to commit without knowing the price.  Can you guarantee that .6 is the ceiling?  I'm a small buyer but I imagine the sentiment is the same. 

0.6 is the ceiling. Period.

[vesperwillow]

So basically we will xfer you X amount of BTC, and whatever that eventually amounts to for units, is what you'll get in the first batch right?

Correct me if my memory fails me, is there any benefit to being in the first group (loyalty rewards lol), or not?

[Istie]

Interested in 5-10 Fully Assembled NF1 plug&play units @.4 maybe more @.3

Do you ship to Europe as well?
What are the shipping costs for international orders? 0.1?
How many pre-orders are placed?
I'm looking forward to see your video/pics

[vs3]

Interested in 5-10 Fully Assembled NF1 plug&play units @.4 maybe more @.3

Do you ship to Europe as well?
What are the shipping costs for international orders? 0.1?
How many pre-orders are placed?
I'm looking forward to see your video/pics

Yes, we will be shipping to Europe. We're also working on setting up a manufacturing point and distribution in Europe (to also cover for such orders).

[vesperwillow]

So basically we will xfer you X amount of BTC, and whatever that eventually amounts to for units, is what you'll get in the first batch right?

Correct me if my memory fails me, is there any benefit to being in the first group (loyalty rewards lol), or not?

[MAREKU]

Hi vs3,
I would order between 10 and 20- fully asssembled NF1 USB sticks, but i will wait to place the order until the end of september.
If you send them from Europe that would be great, because we would save taxes and Import fees (u never know  )
So when next weekend or next week you got more final informations, then i know how much i will order. 

[bigbeninlondon]

Hey vs3;

PM'd.  Let me know if you need anything additional.

[nemercry]

I'm also in for 5 Units at .4 BTC.
At .3 BTC i would buy a lot more.
Shipped to Europe.

[Stinky_Pete]

I'd buy a few in Europe.

[vs3]

Hey vs3;

PM'd.  Let me know if you need anything additional.

Replied to PM (earlier today). All is good.

[vs3]

Thanks for the interest folks!

Please don't forget to place your preorders!

On October 1 we'll be counting PLACED orders. "Promised" will not be considered.

The more chips we get the cheaper they'll be. If we reach 3000 chips we can just buy a whole reel (at $30/chip) which will bring the price down significantly! Currently our biggest expense is the bitfury chips.

Presuming we hit the 3000 mark that would give us chips at 0.2-0.25BTC and the other components with assembly will likely be around 0.15-0.2BTC for a total price of 0.35-0.45BTC (depending also on the $/BTC exchange rate).

[Istie]

What if I place an order before 1 okt (stage 1).
For now it seems a Pre-order costs 0.4BTC per NF1 device.

If at 3 okt the final prices goes up I have to pay extra.

But if the price goes down, say 0.3BTC
Do I get more devices or for the btc I already paid? Settle it with the shipping costs?
Or are you giving a refund for the remaining btc?

[MAREKU]

vs3 can you give us an overview, how many units are allready ordered?
thanx 

[vs3]

What if I place an order before 1 okt (stage 1).
For now it seems a Pre-order costs 0.4BTC per NF1 device.

If at 3 okt the final prices goes up I have to pay extra.

But if the price goes down, say 0.3BTC
Do I get more devices or for the btc I already paid? Settle it with the shipping costs?
Or are you giving a refund for the remaining btc?

As per the opening post the plan (at least for the moment) is to:

* If final prince ends up being less than your initial deposit we’ll refund the BTC difference.

[blitzwilli1]

I would like to have 5 pieces

[vs3]

vs3 can you give us an overview, how many units are allready ordered?
thanx 

Confirmed orders are just about a hundred devices. Pending confirmation are another few hundreds (but I'm not going to count those until they become confirmed).
"Promised" with a bunch of "if" and "when", and "I'm interested" and "I will get X many" are over a thousand so far (which I'm not going to count either unless they do become confirmed).

[vs3]

We got some boards today!



Aaaaaand it seems to be one of our better screw-ups

hint: look at the USB connector pins ....


/running for paint thinner now

[doxavg]

Board looks nice, question though.  I know for most of us running these thumbs it likely won't matter much as they'll be vertically mounted and fan cooled, but why are the heatsinks on the NF1 and the ASICMiner thumbs on the bottom?  I understand why they aren't on the chip itself, but it seems weird to me that with heat prone to rising, the design has the heatsinks below the thing that they cooling.  It's been bugging me since I bought my first BE and plugged it in seemingly upside down to a USB port on my laptop before eventually moving it to a hub (and Pi) after getting it a brother.  Anyway, just a question from a curious person with no more money to buy cool looking products

[vs3]

(...) why are the heatsinks on the NF1 and the ASICMiner thumbs on the bottom?

That's due to the chip design. Most desktop CPUs are designed to dissipate heat through the packaging - so the packaging material for them is metal. But that's very expensive.

The cheapest chip package is plastic, which unfortunately isn't very good conductor of heat. To get around that they used the fact that usually the silicon crystal is first mounted on a metal base, and then the whole thing is covered in plastic (to put it a bit overly simplified). So they ended up with the metal bit that gets the most heat out underneath the chip.

In that case in order to move the heat away from the chip you need to channel it literally through the board towards the back of the board (using numerous "via"s or holes which itself are copper plated and usually during the soldering process get filled in with tin or whatever the soldering material). On the back a large copper plane acts as a heat sink. Or you can add an additional heat sink on top of it.

So if you look at it from a 3D prospective it looks like small heat pipes (the tin-filled vias) that connect the chip to the heatsink. Probably not the most efficient way but certainly cheap

[doxavg]

Thanks for the quick reply, I think I missed something in the wording of my question.  I understood (for the most part - the extra detail was much appreciated) why the heat was dissipated from the back of the board.  I was looking more to understand why the traces for the USB power were on that side of the board and not on the side with the components.  After actually checking the traces again, I realized that you did design your board opposite what ASICMiner did and the heat sink will actually face up when plugged in (at least on the two machines I have in front of me).

[vs3]

Thanks for the quick reply, I think I missed something in the wording of my question.  I understood (for the most part - the extra detail was much appreciated) why the heat was dissipated from the back of the board.  I was looking more to understand why the traces for the USB power were on that side of the board and not on the side with the components.  After actually checking the traces again, I realized that you did design your board opposite what ASICMiner did and the heat sink will actually face up when plugged in (at least on the two machines I have in front of me).

Ah ..

The board was initially designed to have the exact same physical dimensions ad BKKCoin's K1 Nano board (so that we can use the same heatsink, plastics, etc). And he had put the USB connector (tracks) on the back, so we just kept it the same. That was probably not necessary but since it didn't hurt either we just left it there and moved on.

Either way - a lot of things happened in the mean time, and with the Avalon fiasco the whole Klondike project development has grinded to a halt. We also got updated quotes for the board manufacturing, and we either have to have those those tracks gold-plated (so that they don't corrode and oxidize) or if we leave them tin-covered it is likely that after a few months to a year they may start having connectivity issues (and you'll have to clean the contacts, etc).  So ... as a result in the next version of the board we're going to replace the USB connector and instead of a printed one on the board (although a bit cheaper) we're going to use a real one.

[marto74]

Thanks for the quick reply, I think I missed something in the wording of my question.  I understood (for the most part - the extra detail was much appreciated) why the heat was dissipated from the back of the board.  I was looking more to understand why the traces for the USB power were on that side of the board and not on the side with the components.  After actually checking the traces again, I realized that you did design your board opposite what ASICMiner did and the heat sink will actually face up when plugged in (at least on the two machines I have in front of me).

Ah ..

The board was initially designed to have the exact same physical dimensions ad BKKCoin's K1 Nano board (so that we can use the same heatsink, plastics, etc). And he had put the USB connector (tracks) on the back, so we just kept it the same. That was probably not necessary but since it didn't hurt either we just left it there and moved on.

Either way - a lot of things happened in the mean time, and with the Avalon fiasco the whole Klondike project development has grinded to a halt. We also got updated quotes for the board manufacturing, and we either have to have those those tracks gold-plated (so that they don't corrode and oxidize) or if we leave them tin-covered it is likely that after a few months to a year they may start having connectivity issues (and you'll have to clean the contacts, etc).  So ... as a result in the next version of the board we're going to replace the USB connector and instead of a printed one on the board (although a bit cheaper) we're going to use a real one.

Hi,
Some info.
Generally you can ask PCB shop to cover contacts with so called "hard " gold plating in order to have this pins long lasting.
Also to if you do not use additional pad the board have to be 2 mm +/- 0.05 mm.
This is the USB connector spec

[nemercry]

Interested in 5-10 Fully Assembled NF1 plug&play units @.4 maybe more @.3

Do you ship to Europe as well?
What are the shipping costs for international orders? 0.1?
How many pre-orders are placed?
I'm looking forward to see your video/pics

Yes, we will be shipping to Europe. We're also working on setting up a manufacturing point and distribution in Europe (to also cover for such orders).

Maybe you can join forces with marto74. He deals with EU customers and really proofed his skills with his hex board.
Would be good to see someone handy around. You just need to ensure that you can keep your low margin, otherwise the only incentive on this product which is reselling wont be possible.
Most of the people buying here are probably resellers, with extreme little margin.

[itod]

Also to if you do not use additional pad the board have to be 2 mm +/- 0.05 mm.

This is very important, majority of PCB's manufactured today have lesser thickness (around 1.6mm), so you have to use pads for them to sit firmly in the USB port, witch is major pain in the a**. Don't forget to ask for a 2mm PCB from your supplier.

[philipma1957]

Interested in 5-10 Fully Assembled NF1 plug&play units @.4 maybe more @.3

Do you ship to Europe as well?
What are the shipping costs for international orders? 0.1?
How many pre-orders are placed?
I'm looking forward to see your video/pics

Yes, we will be shipping to Europe. We're also working on setting up a manufacturing point and distribution in Europe (to also cover for such orders).

Maybe you can join forces with marto74. He deals with EU customers and really proofed his skills with his hex board.
Would be good to see someone handy around. You just need to ensure that you can keep your low margin, otherwise the only incentive on this product which is reselling wont be possible.
Most of the people buying here are probably resellers, with extreme little margin.

 I have a lot of interest from former AM stick buyers.  If I buy I would sell 60-70% at a small markup  keeping the rest for myself. Right now there is a second seller of sticks like these.  His would come 20 to 30 days sooner.  Of course they cost more.   I am mulling over whom to choose. I may buy some from both.

[vs3]

Interested in 5-10 Fully Assembled NF1 plug&play units @.4 maybe more @.3

Do you ship to Europe as well?
What are the shipping costs for international orders? 0.1?
How many pre-orders are placed?
I'm looking forward to see your video/pics

Yes, we will be shipping to Europe. We're also working on setting up a manufacturing point and distribution in Europe (to also cover for such orders).

Maybe you can join forces with marto74. He deals with EU customers and really proofed his skills with his hex board.
Would be good to see someone handy around. You just need to ensure that you can keep your low margin, otherwise the only incentive on this product which is reselling wont be possible.
Most of the people buying here are probably resellers, with extreme little margin.

We are listening to our customers. Stay tuned for updates.

[vs3]

Interested in 5-10 Fully Assembled NF1 plug&play units @.4 maybe more @.3

Do you ship to Europe as well?
What are the shipping costs for international orders? 0.1?
How many pre-orders are placed?
I'm looking forward to see your video/pics

Yes, we will be shipping to Europe. We're also working on setting up a manufacturing point and distribution in Europe (to also cover for such orders).

Maybe you can join forces with marto74. He deals with EU customers and really proofed his skills with his hex board.
Would be good to see someone handy around. You just need to ensure that you can keep your low margin, otherwise the only incentive on this product which is reselling wont be possible.
Most of the people buying here are probably resellers, with extreme little margin.

 I have a lot of interest from former AM stick buyers.  If I buy I would sell 60-70% at a small markup  keeping the rest for myself. Right now there is a second seller of sticks like these.  His would come 20 to 30 days sooner.  Of course they cost more.   I am mulling over whom to choose. I may buy some from both.

Pick ours! :-)

[RicRock]

Any further projections on final cost?

I'd like to order more but want to make sure I have the funds.

Still looking like 0.6 per?

[MAREKU]

yeah RicRock same here-and maybe they look like the red fury max 2.7 sticks?who knows :S

[MAREKU]

dont get me wrong vs3, but i need a bit more information about what we could get and how secure the order is, iam not a gambler  all on NF1-rien ne va plus 

[volosator]

Is this group still open? How many slots are available?

[nemercry]

Looks like everyone wants to hear the final pricing of at least .4 BTC per device.

[zamot]

VS3, is this group buy just for US or can it be delivered to EU ?

[vs3]

Any further projections on final cost?

I'd like to order more but want to make sure I have the funds.

Still looking like 0.6 per?

I think it would be a safe bet that the final price would be below 0.55BTC even with the (relatively small) number of confirmed orders so far.

The bigger the order the lower the price. Ideally we would like to exceed 3000 devices so that we can get a reel of chips from Buzzdave at $30/chip (as opposed to zefir's at 0.27BTC). In this case our projections indicate a final price in the 0.40-0.43 range.

[vs3]

Is this group still open? How many slots are available?

Yes, the group is still open.

As for limits - we're still a bit far from the 3k goal, so no limit in sight for now. We are getting closer to exceeding the low-water mark, so we're almost certainly going to manufacture at least several hundred devices.

[RicRock]

Cool... ordering more then

[vs3]

VS3, is this group buy just for US or can it be delivered to EU ?

Yes, we ship worldwide (or more precisely wherever USPS ships )

[w33mhz]

Well I think the orders will start rolling in once there is a proof of concept built and running.  The avalon fiasco has made quite a few of people gun shy, most people are wanting to pay for product (post creation) and not the development of the product (pre-creation).  As the saying goes "Build it and they will come".

[bitterdog]

Well I think the orders will start rolling in once there is a proof of concept built and running.  The avalon fiasco has made quite a few of people gun shy, most people are wanting to pay for product (post creation) and not the development of the product (pre-creation).  As the saying goes "Build it and they will come".

Correct.

Atleast the guys selling the Red Fury had a video of the device working. Not just a picture of a screwed up mobo.

Come on guys!
There a lot of people who want to see this be successful, throw us a Bone.

[zamot]

VS3, is this group buy just for US or can it be delivered to EU ?

Yes, we ship worldwide (or more precisely wherever USPS ships )

Great. I suppose you do not have an idea about shiping cost to Slovenia.
How far is the disribution in EU? you mentioned in one of previous post, that there is some activity to have distribution in EU.
I am interested on 4 - 5 NF1s( fully assembled ) but depends on price ( including shipping price ).

[thomas_s]

VS3, is this group buy just for US or can it be delivered to EU ?

Yes, we ship worldwide (or more precisely wherever USPS ships )

Great. I suppose you do not have an idea about shiping cost to Slovenia.
How far is the disribution in EU? you mentioned in one of previous post, that there is some activity to have distribution in EU.
I am interested on 4 - 5 NF1s( fully assembled ) but depends on price ( including shipping price ).

Priority mail to most international countries is around $30-40 for around 10 or so usb sticks depending on the size, they might add a handling fee on top of that because they have to package it w/ packing supplies and to fill out the customs forms.

[nemercry]

Is there a smart possibility to bring them inside the EU and sending them there to customers to avoid customs.
You said something about eu outpost, maybe ?

[thomas_s]

Is there a possibility to send them from the inside of the EU to get around customs ?

If you pay in btc I'm sure they can easily mark the package as cheap (usb's are cheap) and that should get around customs. or there would need to be 1 person in the EU to ship all too then that person ships to other eu people.

[nemercry]

Is there a possibility to send them from the inside of the EU to get around customs ?

If you pay in btc I'm sure they can easily mark the package as cheap (usb's are cheap) and that should get around customs. or there would need to be 1 person in the EU to ship all too then that person ships to other eu people.

Sounds like a reasonable good idea.

[BTClobsta]

Any further projections on final cost?

I'd like to order more but want to make sure I have the funds.

Still looking like 0.6 per?

I think it would be a safe bet that the final price would be below 0.55BTC even with the (relatively small) number of confirmed orders so far.

The bigger the order the lower the price. Ideally we would like to exceed 3000 devices so that we can get a reel of chips from Buzzdave at $30/chip (as opposed to zefir's at 0.27BTC). In this case our projections indicate a final price in the 0.40-0.43 range.

how much do i need to order to get it at .40btc complete and shipped? I'm located in the US.

[bitterdog]

I'd like to place a order, but not until I see a working unit

[Istie]

vs3 can you give us an overview, how many units are allready ordered?
thanx 

Confirmed orders are just about a hundred devices. Pending confirmation are another few hundreds (but I'm not going to count those until they become confirmed).
"Promised" with a bunch of "if" and "when", and "I'm interested" and "I will get X many" are over a thousand so far (which I'm not going to count either unless they do become confirmed).

Are the confirmed and pending confirmation orders payed to a different address?
On the blockchain there are only 6 transaction with a total of 7.2btc on the payment address: 1AHvViTD5wohPywNYHi8NZ8uPhbY9dZXCY
That would be 18 fully NF1 devices at 0.4btc
https://blockchain.info/address/1AHvViTD5wohPywNYHi8NZ8uPhbY9dZXCY

[philipma1957]

vs3 can you give us an overview, how many units are allready ordered?
thanx 

Confirmed orders are just about a hundred devices. Pending confirmation are another few hundreds (but I'm not going to count those until they become confirmed).
"Promised" with a bunch of "if" and "when", and "I'm interested" and "I will get X many" are over a thousand so far (which I'm not going to count either unless they do become confirmed).

Are the confirmed and pending confirmation orders payed to a different address?
On the blockchain there are only 6 transaction with a total of 7.2btc on the payment address: 1AHvViTD5wohPywNYHi8NZ8uPhbY9dZXCY
That would be 18 fully NF1 devices at 0.4btc
https://blockchain.info/address/1AHvViTD5wohPywNYHi8NZ8uPhbY9dZXCY

this seems like only a few people have sent in coins.

in contrast the other buy for these sticks uses:

https://blockchain.info/address/1LRUwL1sF5j4DPjXrkVGGiDGFd7qGVqwGX

  and that address has more then 60 coins placed into it. The other seller wants .85 a stick so for me to buy 20 sticks it is 17 coins I get them lets say  Oct 2- oct 10th. 

Your sticks are lower cost I like that but they come Oct 30 - NOV 4th

 Frankly as a person still waiting for my bfl orders from Jan of 2013 sending 12 coins to you for 20-30 sticks is kind of hard for me to do. 
 

Not only am I waiting on bfl. 5 coins
 I am waiting on knc.            7 coins
 I am waiting for a baby jet.   2 coins
I am waiting  on a metabank. 3 coins

most of the above is group buys from this site.


I am not sure I want to tie up 12 coins for a long time say 42 days. Very frustrating doing business with asic providers.  It is almost always hurry up and wait.

 So as much as I want to pay .4 to .6 a stick I will most  likely pay .85 a stick to the other seller. Not my first choice but it looks safer.  If I order here it will be 2 or 3 sticks tops. I can deal with waiting on a small amount of coins for gear.

[RicRock]

I see TechnoBit is selling NanoFury's in EU.

http://technobit.eu/index.php

Will you be selling the S-Hash in the US?

[vs3]

I see TechnoBit is selling NanoFury's in EU.

http://technobit.eu/index.php

Will you be selling the S-Hash in the US?

Yes, indeed -  we've set up a second distribution and manufacturing point in Europe and are working with Marto74 in that regard. Have I mentioned before that we listen to our customers?

We're still shipping to the entire world (or more precisely wherever USPS does), and for shipping and tax purposes it is sometimes better to ship such products from EU vs US (and vice versa).

By the way - he announced it on his thread too - https://bitcointalk.org/index.php?topic=293030.msg3201837#msg3201837

[prehistoric]

I see TechnoBit is selling NanoFury's in EU.
http://technobit.eu/index.php

Yes, indeed -  we've set up a second distribution and manufacturing point in Europe and are working with Marto74 in that regard. Have I mentioned before that we listen to our customers?

What is the preferable buying option now: through http://technobit.eu/index.php (which lags horribly and shows nothing at the moment) or this GB? Thanks.
Upd: Sorry about lags, next time it opened blazing fast! Not sure what that was.

[philipma1957]

I decided to buy from you and from ssinc.  spread the risk.

I will send in 4 btc on thur. the 26th this would be  for 10  fully assembled sticks all parts  provided by you.   

 you would then come up with final pricing on the 3rd of oct correct. and since sticks may be as high as .6 btc I could owe 2btc more? 

  If I have it correct please confirm.  thanks.   phil

[vs3]

(..) and since sticks may be as high as .6 btc I could owe 2btc more? 

That is mostly correct - the highest price that we're looking at (currently) is actually 0.55BTC so that would be eventually 1.5BTC more (plus shipping).

[vs3]

What is the preferable buying option now: through http://technobit.eu/index.php or this GB?.

We're running two separate business models and therefore there isn't necessarily a "better" place. There are also several factors which may affect your preference - see below.

Marto74 is taking a bigger risk by ordering a full reel of bitfury chips, and also estimating the demand and thus final price. On the other hand, because of those factors he'll be shipping a few weeks earlier than us.

We on the other hand are trying to get the lowest price by first knowing the demand precisely. That way we won't have to pre-order tons of components which may end up not being necessary. At the end of the day if our price ends up being higher than Marto74's we're going to order our devices via Marto74, and his price will be our price too. I'm pretty much trying to say that no matter where you end up ordering from you will pay no more than Marto74's price (which is around 0.54-0.55BTC based on the current exchange rate).

The other factor that you might want to take into consideration is shipping. In the second email we'll be asking the question "Shipping preference: (From EU), (From US), (no preference)". For some countries it might be better to ship from US and for some from EU. There are also often different customs procedures, duties and taxes/VAT based on the country of origin.

[philipma1957]

(..) and since sticks may be as high as .6 btc I could owe 2btc more? 

That is mostly correct - the highest price that we're looking at (currently) is actually 0.55BTC so that would be eventually 1.5BTC more (plus shipping).

 okay sounds good.  I will have 4 coins on thur the 26th,   thank you.

[nemercry]

What is the preferable buying option now: through http://technobit.eu/index.php or this GB?.

We're running two separate business models and therefore there isn't necessarily a "better" place. There are also several factors which may affect your preference - see below.

Marto74 is taking a bigger risk by ordering a full reel of bitfury chips, and also estimating the demand and thus final price. On the other hand, because of those factors he'll be shipping a few weeks earlier than us.

We on the other hand are trying to get the lowest price by first knowing the demand precisely. That way we won't have to pre-order tons of components which may end up not being necessary. At the end of the day if our price ends up being higher than Marto74's we're going to order our devices via Marto74, and his price will be our price too. I'm pretty much trying to say that no matter where you end up ordering from you will pay no more than Marto74's price (which is around 0.54-0.55BTC based on the current exchange rate).

The other factor that you might want to take into consideration is shipping. In the second email we'll be asking the question "Shipping preference: (From EU), (From US), (no preference)". For some countries it might be better to ship from US and for some from EU. There are also often different customs procedures, duties and taxes/VAT based on the country of origin.

Thanks for that clarification, helped me a lot.

[Swimmer63]

In for 20.

[zamot]

Thanks for the interest folks!

Please don't forget to place your preorders!

On October 1 we'll be counting PLACED orders. "Promised" will not be considered.

The more chips we get the cheaper they'll be. If we reach 3000 chips we can just buy a whole reel (at $30/chip) which will bring the price down significantly! Currently our biggest expense is the bitfury chips.

Presuming we hit the 3000 mark that would give us chips at 0.2-0.25BTC and the other components with assembly will likely be around 0.15-0.2BTC for a total price of 0.35-0.45BTC (depending also on the $/BTC exchange rate).

How is the latest situation about price ?

[Zillions]

I'm In for 3 assuming max price of 0.6btc
PMing you momentarily.

[vs3]

We've announced the shipping prices - updated opening post:

Shipping prices will be as follows:

Within the US:
|----------------|------------|------------|---------|
|Service:        |First Class | Priority   | Express |
|Shipping time:  | 3-5 b.days | 2-3 b.days | 1 b.day |
|----------------|------------|------------|---------|
|Devices:        |            |            |         |
|1-3             |     $4     |    $6      |  $47    |
|4-12            |     $6     |    $6      |  $47    |
|13-70           |    $16     |   $16      |  $47    |
|71-125          |    $24     |   $24      |  $47    |
|126-250         |   free     |   free     |  $94    |
|250-500         |   free     |   free     |  $188   |
|501+            |   free     |   free     |  free   |
|----------------|------------|------------|---------|

International:
|----------------|-------------|-------------|------------|
|Service:        | First Class |   Priority  |   Express  |
|Shipping time:  |    varies   | 6-10 b.days | 3-5 b.days |
|----------------|-------------|-------------|------------|
|Devices:        |             |             |            |
|1-4             |      $12    |    $24      |    $100    |
|5-8             |      $21    |    $24      |    $100    |
|9-70            |      $65 *  |    $65      |    $100    |
|71-100          |      $85 *  |    $85      |    $100    |
|101-500         | $0.9/device | $0.9/device | $1/device  |
|501+            |    free     |   free      |  free      |
|----------------|-------------|-------------|------------|

* Note: Shipping time is in Business Days (as per USPS)

[philipma1957]

We got some boards today!



Aaaaaand it seems to be one of our better screw-ups

hint: look at the USB connector pins ....


/running for paint thinner now

so do you have a working stick to show?

[vs3]

We got some boards today!

https://i.imgur.com/rrSYYPSl.jpg

Aaaaaand it seems to be one of our better screw-ups

hint: look at the USB connector pins ....
/running for paint thinner now

so do you have a working stick to show?

The nicer looking boards unfortunately won't make it until some time next week and I'll have just the engineering samples on Friday. I'll be assembling them over the weekend and if they don't look way too ugly I'll add some pictures of the finished devices.

Here is a picture that I took the other day while doing stress-testing with one of the V1 boards:

I know that at first it looks scary but it was actually a successful test. (If you're not interested in the technical details and lingo you can stop reading here )
I was experimenting with extreme values for some of the components and even in that case the communication was still stable and usable at SPI speeds of up to 200-300kHz (and as a reference - for a one-chip design 50-100kHz is more than sufficient). What you see on the oscilloscope is the MISO line after it's been converted from 1.8 to 3.3V and the effects of the capacitance of some of the components. The data was fed back to the USB controller once it was converted down to 1.8V (sort of a loopback - 3.3->1.8->3.3) which also contributes a lot to the image.

[nemercry]

We got some boards today!

https://i.imgur.com/rrSYYPSl.jpg

Aaaaaand it seems to be one of our better screw-ups

hint: look at the USB connector pins ....
/running for paint thinner now

so do you have a working stick to show?

The nicer looking boards unfortunately won't make it until some time next week and I'll have just the engineering samples on Friday. I'll be assembling them over the weekend and if they don't look way too ugly I'll add some pictures of the finished devices.

Here is a picture that I took the other day while doing stress-testing with one of the V1 boards:

I know that at first it looks scary but it was actually a successful test. (If you're not interested in the technical details and lingo you can stop reading here )
I was experimenting with extreme values for some of the components and even in that case the communication was still stable and usable at SPI speeds of up to 200-300kHz (and as a reference - for a one-chip design 50-100kHz is more than sufficient). What you see on the oscilloscope is the MISO line after it's been converted from 1.8 to 3.3V and the effects of the capacitance of some of the components. The data was fed back to the USB controller once it was converted down to 1.8V (sort of a loopback - 3.3->1.8->3.3) which also contributes a lot to the image.

So that means the pcb and its components are pretty stable, right ?

[viriat0]

Watch 
good luck

[vs3]

So that means the pcb and its components are pretty stable, right ?

Pretty much. All of the important pieces of the design are stable. In the last revision I added also an LED (as people like blinky stuff ) but this it is purely for prettiness - it doesn't affect the core functionality in any way.

[nemercry]

So that means the pcb and its components are pretty stable, right ?

Pretty much. All of the important pieces of the design are stable. In the last revision I added also an LED (as people like blinky stuff ) but this it is purely for prettiness - it doesn't affect the core functionality in any way.

Sounds awesome, im currently waiting for some money from a GB. After that i will order all my miners from marto. Cant wait to see them

[Molex1701]

Actually I don't like them blinking.  I'm in small place and the AM miners got annoying.  I soldered off the led.

[vs3]

Actually I don't like them blinking.  I'm in small place and the AM miners got annoying.  I soldered off the led.

hahahahaha
Okay, I think that's a very good "feature request": --led-disable

we'll keep it in mind.

[thomas_s]

Actually I don't like them blinking.  I'm in small place and the AM miners got annoying.  I soldered off the led.

The only thing I liked about the led was that it made it really easy to tell if the miners were offline, I'd get up in the morning go downstairs and see a light on and know to restart that strip.

No need to have to check on the computer or ui.

A disable feature would be cool (also multicolor lights not just one color for every one of them)

[nemercry]

Actually I don't like them blinking.  I'm in small place and the AM miners got annoying.  I soldered off the led.

The only thing I liked about the led was that it made it really easy to tell if the miners were offline, I'd get up in the morning go downstairs and see a light on and know to restart that strip.

No need to have to check on the computer or ui.

A disable feature would be cool (also multicolor lights not just one color for every one of them)

Let's keep it cheap and simple

[nemercry]

What is the preferable buying option now: through http://technobit.eu/index.php or this GB?.

We're running two separate business models and therefore there isn't necessarily a "better" place. There are also several factors which may affect your preference - see below.

Marto74 is taking a bigger risk by ordering a full reel of bitfury chips, and also estimating the demand and thus final price. On the other hand, because of those factors he'll be shipping a few weeks earlier than us.

We on the other hand are trying to get the lowest price by first knowing the demand precisely. That way we won't have to pre-order tons of components which may end up not being necessary. At the end of the day if our price ends up being higher than Marto74's we're going to order our devices via Marto74, and his price will be our price too. I'm pretty much trying to say that no matter where you end up ordering from you will pay no more than Marto74's price (which is around 0.54-0.55BTC based on the current exchange rate).

The other factor that you might want to take into consideration is shipping. In the second email we'll be asking the question "Shipping preference: (From EU), (From US), (no preference)". For some countries it might be better to ship from US and for some from EU. There are also often different customs procedures, duties and taxes/VAT based on the country of origin.

Do you know when marto74 will receive his pcbs for assembling those miners ? I've read 1/2 week of oktober in his thread, but i think this is for his s-hash model only.

[Molex1701]

Actually I don't like them blinking.  I'm in small place and the AM miners got annoying.  I soldered off the led.

The only thing I liked about the led was that it made it really easy to tell if the miners were offline, I'd get up in the morning go downstairs and see a light on and know to restart that strip.

No need to have to check on the computer or ui.

A disable feature would be cool (also multicolor lights not just one color for every one of them)

That's true.  If they go zombie or such.

[Molex1701]

Actually I don't like them blinking.  I'm in small place and the AM miners got annoying.  I soldered off the led.

hahahahaha
Okay, I think that's a very good "feature request": --led-disable

we'll keep it in mind.

That would be a nice feature, thanks.   

[philipma1957]

Was checking the payment address


https://blockchain.info/address/1AHvViTD5wohPywNYHi8NZ8uPhbY9dZXCY 


 so far you have under 25 coins about 21.6 which is 54 sticks. I have a suggestion try to show us more photos of it working.

 Here is my preorder score for asics.

1) BFL   2 jallys on order many orders cancelled no gear. waiting 7 months

2)https://bitcointalk.org/index.php?topic=223746.0;all   order cancelled got a refund coins tied up 3-4 months

3) https://bitcointalk.org/index.php?topic=238336.0    Knc gear 7.5 coins for 45gh hash waiting 3 months

4)https://bitcointalk.org/index.php?topic=274055.0;all  1.55 btc for 10gh hash  will wait till dec?

5) https://bitcointalk.org/index.php?topic=296301.0    17 coins tied up waiting a few days so far.



only thecanryinthemine and silentsonicboom have delivered any working gear to me.  I have ordered more then 400 sticks from them.

 My point is I am not doing well on anything but AM usb sticks. I have more then 25 btc in preorders and 500 usd with bfl. about 3.5k

0 delivery but to be fair theswede75 was super fast with the refund on that dead deal and my biggest preorder with 17 coins is about 2 days old and on schedule for under 2-3 weeks. 

Still no video not much info and you only have 54 sticks prepaid.

 https://blockchain.info/address/1AHvViTD5wohPywNYHi8NZ8uPhbY9dZXCY  only  21.6btc 

  I sent 17 btc to ssinc for his sticks. as he had a lot more info to show on his prebuy.

 I do want to order as I am a preorder junkie but please a little more info before i send my btc out into cyberspace.

[vs3]

Was checking the payment address


https://blockchain.info/address/1AHvViTD5wohPywNYHi8NZ8uPhbY9dZXCY 


 so far you have under 25 coins about 21.6 which is 54 sticks. I have a suggestion try to show us more photos of it working.

 Here is my preorder score for asics.

1) BFL   2 jallys on order many orders cancelled no gear. waiting 7 months

2)https://bitcointalk.org/index.php?topic=223746.0;all   order cancelled got a refund coins tied up 3-4 months

3) https://bitcointalk.org/index.php?topic=238336.0    Knc gear 7.5 coins for 45gh hash waiting 3 months

4)https://bitcointalk.org/index.php?topic=274055.0;all  1.55 btc for 10gh hash  will wait till dec?

5) https://bitcointalk.org/index.php?topic=296301.0    17 coins tied up waiting a few days so far.



only thecanryinthemine and silentsonicboom have delivered any working gear to me.  I have ordered more then 400 sticks from them.

 My point is I am not doing well on anything but AM usb sticks. I have more then 25 btc in preorders and 500 usd with bfl. about 3.5k

0 delivery but to be fair theswede75 was super fast with the refund on that dead deal and my biggest preorder with 17 coins is about 2 days old and on schedule for under 2-3 weeks. 

Still no video not much info and you only have 54 sticks prepaid.

 https://blockchain.info/address/1AHvViTD5wohPywNYHi8NZ8uPhbY9dZXCY  only  21.6btc 

  I sent 17 btc to ssinc for his sticks. as he had a lot more info to show on his prebuy.

 I do want to order as I am a preorder junkie but please a little more info before i send my btc out into cyberspace.

philipma1957 -

first - I understand your concerns very well. I have personally been burnt by BFL and several Avalon pre-orders. And it is for that reason that we added the following text in the opening post:

* We’ve seen what happened to Avalon and BFL preorders and we’re absolutely committed to not repeating their mistakes!
We will not spend a single cent of your money until we know that we can deliver what we promised! And if we can’t we’ll be refunding your money.
Currently there are two gotchas: 1) We are dependent on buzzdave (megabigpower.com) to deliver chips on time, and 2) we are dependent on him for reasonable chip pricing. Regarding #1 he has already stated that they have plenty of chips in stock, so currently our only concern is #2.

Second - I more than anyone want to add more pictures and video of our device. Our nicer-looking boards unfortunately won't be here until probably late next week (which will be too late for some). At this point I'm planning to add some more pictures from the engineering boards (and please excuse their not-so-pretty look).

This is likely going to happen either later tonight or tomorrow as I just got them yesterday and they're just bare boards as of this moment yet. That's how they look like as of this moment:


Out of the 3 or 4 that I'll be putting together some will be going to the various miner software developers (e.g. one will be going to Luke-Jr so that he can start integrating support into his bfgminer, etc).

Anyways - it's time for me to get back to work
Feel free to PM me if you have any questions.

[bitterdog]

only thecanryinthemine and silentsonicboom have delivered any working gear to me.  I have ordered more then 400 sticks from them.

 My point is I am not doing well on anything but AM usb sticks. I have more then 25 btc in preorders and 500 usd with bfl. about 3.5k

0 delivery but to be fair theswede75 was super fast with the refund on that dead deal and my biggest preorder with 17 coins is about 2 days old and on schedule for under 2-3 weeks.  

Still no video not much info and you only have 54 sticks prepaid.

 https://blockchain.info/address/1AHvViTD5wohPywNYHi8NZ8uPhbY9dZXCY  only  21.6btc  

  I sent 17 btc to ssinc for his sticks. as he had a lot more info to show on his prebuy.

 I do want to order as I am a preorder junkie but please a little more info before i send my btc out into cyberspace.

This was the last straw for me to not even consider these guys. Stack this on top of no video, no proof of work.. nothing.... don't waste your time
Might as well call it VaporFury1
If you are going to have a pre-order, SHOW US WHAT WE ARE ORDERING!

We got some boards today!



Aaaaaand it seems to be one of our better screw-ups

hint: look at the USB connector pins ....


/running for paint thinner now

[Taugeran]

only thecanryinthemine and silentsonicboom have delivered any working gear to me.  I have ordered more then 400 sticks from them.

 My point is I am not doing well on anything but AM usb sticks. I have more then 25 btc in preorders and 500 usd with bfl. about 3.5k

0 delivery but to be fair theswede75 was super fast with the refund on that dead deal and my biggest preorder with 17 coins is about 2 days old and on schedule for under 2-3 weeks.  

Still no video not much info and you only have 54 sticks prepaid.

 https://blockchain.info/address/1AHvViTD5wohPywNYHi8NZ8uPhbY9dZXCY  only  21.6btc  

  I sent 17 btc to ssinc for his sticks. as he had a lot more info to show on his prebuy.

 I do want to order as I am a preorder junkie but please a little more info before i send my btc out into cyberspace.

This was the last straw for me to not even consider these guys. Stack this on top of no video, no proof of work.. nothing.... don't waste your time
Might as well call it VaporFury1
If you are going to have a pre-order, SHOW US WHAT WE ARE ORDERING!

We got some boards today!



Aaaaaand it seems to be one of our better screw-ups

hint: look at the USB connector pins ....


/running for paint thinner now

why so hateful?

[philipma1957]

only thecanryinthemine and silentsonicboom have delivered any working gear to me.  I have ordered more then 400 sticks from them.

 My point is I am not doing well on anything but AM usb sticks. I have more then 25 btc in preorders and 500 usd with bfl. about 3.5k

0 delivery but to be fair theswede75 was super fast with the refund on that dead deal and my biggest preorder with 17 coins is about 2 days old and on schedule for under 2-3 weeks.  

Still no video not much info and you only have 54 sticks prepaid.

 https://blockchain.info/address/1AHvViTD5wohPywNYHi8NZ8uPhbY9dZXCY  only  21.6btc  

  I sent 17 btc to ssinc for his sticks. as he had a lot more info to show on his prebuy.

 I do want to order as I am a preorder junkie but please a little more info before i send my btc out into cyberspace.

This was the last straw for me to not even consider these guys. Stack this on top of no video, no proof of work.. nothing.... don't waste your time
Might as well call it VaporFury1
If you are going to have a pre-order, SHOW US WHAT WE ARE ORDERING!

We got some boards today!



Aaaaaand it seems to be one of our better screw-ups

hint: look at the USB connector pins ....


/running for paint thinner now

why so hateful?

   He is probably like me 0 for 5 on preorders with a lot of coins floating in cyberspace.  Maybe he did not make a lot when this was gpu and not asics. So he is disgusted.  Myself I wanted to buy  but I have now been told my knc orders will be 7 to 14 days wait. Was hoping they would be on time and now that the delay is certain I am holding back.

[vs3]

Greetings everyone,

So here is my weekend update:

First the (sort of) bad news - despite me triple-checking the documentation I've managed to put the USB connector backwards. (pins are 4-3-2-1 instead of 1-2-3-4)
The immediate result was that I had to solder it backwards on the test boards, and that there will be yet another version of the board I guess that's just a bit more work for me (and no sleep again) but at least that's a very easy fix.

The good news - and before that please excuse the not-so-pretty looking boards - those are the engineering samples as the nice-and-pretty ones are not going to make it on time.

Out of the 4 borders I hand-soldered 2 had the bitfury chip misplaced by a bit (and had shorts and I'll be unsoldering and fixing them later) and 2 were fully completed. And because of the USB connector bug it's been soldered backwards.

Here are the two boards, and one of them hashing (the LED on) :
 

and for the geeks - on that one I was looking at the MOSI and MISO signals (data being sent to and from the chip) :



And for those with "Show Me The Money" question - below are two screen shots from the debugger as the boards passed all tests:


On the two pictures I was testing with 54 and 52 bits speed setting - which is the thing that controls the speed - the more the bits the faster it hashes (and more heat, and eventually hardware errors).

For that test I've adapted BitFury's code (taken from here) and replaced his RaspberryPI stuff with what I needed to run it with our controller and under Windows. Oh, yeah - did I say that this device was going to run under Windows (too)?

Some more technical details:
- Voltage was set to 0.808V. We can go as low as 0.800 (due to power regulator limitations) and as high as 5V for those inclined to experiment
- Temperature: After running for about 30 minutes on 54 bits and as it was taped on the desk the board got up to 75C. That was the most extreme condition - no ventilation, and all heat was directed to the side that was taped to the desk (and wood is not very much thermally conductive ). I'll be doing some more tests with no and a little bit of ventilation.
- GHashes - I haven't measured the exact GHash rate yet, but at 52 bits it's somewhere around 2.0-2.1GH/s and at 24 bits it's in the vicinity of 2.4-2.7GH/s.
- Power consumption will be the next thing to measure. I know for sure that it is below 2.5W as it was plugged into an old monitor which is very picky about devices drawing over 0.5Amps.

For those asking what's next - We gave up on the idea of writing our own miner (yeah, I guess we were a bit optimistic about that ) and we're currently doing the surgical cutting and pasting into legkodymov's cgminer clone (which was never meant to work under Windows and that's what we're currently fixing). My guesstimate is that this is going to take us probably another 10-20 hours of coding, or barring any nasty surprises in a few days the next pictures (and video!) will be of cgminer running our device.


Finally - I realize that for many of you guys this entire GB represents some kind of a risk, and as we're near the end patience is running thin and I want to assure everyone that we stand absolutely firmly behind our promise. We will either deliver what we promised or you'll have your money back. All 100% of it. I'll even pay the transaction fees.

I realize that many of you are considering the risks in this GB and speaking of risk - I doubt that anyone has taken more risk than the development team, who so far has invested their own money into ordering boards and materials (have I mentioned that we've been paying $70 extra for overnight shipping on everything?) and dedicated countless hours into this project. Looking in retrospect I see a lot of things that we could've done different (and faster) but we're a very small team and without the (sort of) unlimited resources of the big businesses.

Nonetheless - I'm very excited with our progress so far and I'm confident that we'll be able to deliver the nice NanoFury devices in your hands as promised!

And we do appreciate your trust in us and all the support and encouraging feedback from the forum!

[Taugeran]

Greetings everyone,

So here is my weekend update:

First the (sort of) bad news - despite me triple-checking the documentation I've managed to put the USB connector backwards. (pins are 4-3-2-1 instead of 1-2-3-4)
The immediate result was that I had to solder it backwards on the test boards, and that there will be yet another version of the board I guess that's just a bit more work for me (and no sleep again) but at least that's a very easy fix.

The good news - and before that please excuse the not-so-pretty looking boards - those are the engineering samples as the nice-and-pretty ones are not going to make it on time.

Out of the 4 borders I hand-soldered 2 had the bitfury chip misplaced by a bit (and had shorts and I'll be unsoldering and fixing them later) and 2 were fully completed. And because of the USB connector bug it's been soldered backwards.

Here are the two boards, and one of them hashing (the LED on) :
 

and for the geeks - on that one I was looking at the MOSI and MISO signals (data being sent to and from the chip) :



And for those with "Show Me The Money" question - below are two screen shots from the debugger as the boards passed all tests:


On the two pictures I was testing with 54 and 52 bits speed setting - which is the thing that controls the speed - the more the bits the faster it hashes (and more heat, and eventually hardware errors).

For that test I've adapted BitFury's code (taken from here) and replaced his RaspberryPI stuff with what I needed to run it with our controller and under Windows. Oh, yeah - did I say that this device was going to run under Windows (too)?

Some more technical details:
- Voltage was set to 0.808V. We can go as low as 0.800 (due to power regulator limitations) and as high as 5V for those inclined to experiment
- Temperature: After running for about 30 minutes on 54 bits and as it was taped on the desk the board got up to 75C. That was the most extreme condition - no ventilation, and all heat was directed to the side that was taped to the desk (and wood is not very much thermally conductive ). I'll be doing some more tests with no and a little bit of ventilation.
- GHashes - I haven't measured the exact GHash rate yet, but at 52 bits it's somewhere around 2.0-2.1GH/s and at 24 bits it's in the vicinity of 2.4-2.7GH/s.
- Power consumption will be the next thing to measure. I know for sure that it is below 2.5W as it was plugged into an old monitor which is very picky about devices drawing over 0.5Amps.

For those asking what's next - We gave up on the idea of writing our own miner (yeah, I guess we were a bit optimistic about that ) and we're currently doing the surgical cutting and pasting into legkodymov's cgminer clone (which was never meant to work under Windows and that's what we're currently fixing). My guesstimate is that this is going to take us probably another 10-20 hours of coding, or barring any nasty surprises in a few days the next pictures (and video!) will be of cgminer running our device.


Finally - I realize that for many of you guys this entire GB represents some kind of a risk, and as we're near the end patience is running thin and I want to assure everyone that we stand absolutely firmly behind our promise. We will either deliver what we promised or you'll have your money back. All 100% of it. I'll even pay the transaction fees.

I realize that many of you are considering the risks in this GB and speaking of risk - I doubt that anyone has taken more risk than the development team, who so far has invested their own money into ordering boards and materials (have I mentioned that we've been paying $70 extra for overnight shipping on everything?) and dedicated countless hours into this project. Looking in retrospect I see a lot of things that we could've done different (and faster) but we're a very small team and without the (sort of) unlimited resources of the big businesses.

Nonetheless - I'm very excited with our progress so far and I'm confident that we'll be able to deliver the nice NanoFury devices in your hands as promised!

And we do appreciate your trust in us and all the support and encouraging feedback from the forum!

first congrats!!!!! 

second, hooree sheet. a diehard windows VS2010 coder. props and love

[RicRock]

For those asking what's next - We gave up on the idea of writing our own miner (yeah, I guess we were a bit optimistic about that ) and we're currently doing the surgical cutting and pasting into legkodymov's cgminer clone (which was never meant to work under Windows and that's what we're currently fixing). My guesstimate is that this is going to take us probably another 10-20 hours of coding, or barring any nasty surprises in a few days the next pictures (and video!) will be of cgminer running our device.

Good news indeed.

Being a Bfgminer/Linux guy, I say don't worry about the windows stuff 

[vs3]

Some more technical info:

bits |Max C|Max A| solutions |
 48  |  70 | .51 |   149     |
 49  |     | .55 |   148     |
 50  |     | .57 |   138     |
 51  |     | .60 |   135     |
 52  |     | .67 |   142     |
 53  |     | .74 |   139     |
 54  |     | .81 |   156     |
 55  |     | .89 |   101     |
 56  |  84 |1.01 |    47     |

Each device behaves differently and those are the values from the worse of the two.

The maximum usable bits (max speed) is 54 bits in which case it draws 0.81A (when it heats up).

Also, I noticed that my old monitor was actually horrible and rather in an unexpected way - when the device started drawing a lot of current the 5V voltage dropped to 3.6V (that was at 1A). This also skews my measurements as the amps would've been lower at 5V. Even at 0.5A the voltage had dropped to 4.8V. Also - probably a side effect of the long cable or usb hub - the voltage wasn't properly stabilized or filtered and I could see a lot of USB noise coming through the power supply. All the LDOs did a good job actually and filtered everything.

I didn't measure temperature all the time, but it went gradually from hovering around 70C at slow speeds to about 82-84C at the highest.

I'll be repeating those with different (powered) hubs over the next days.

Conclusion: Likely the 50 or 51 bits speed (1.7-1.9GH) would be the optimal limit for the standard USB 2.0 and some may be able to go up to 52 bits (2-2.1GH) depending on how much power would they be able to draw from the port. The maximum usable speed (for the overclockers) would probably be 54 bits (or possibly 55 with some extra cooling and voltage tweaking) leading to 2.5-2.7GH/s and above.

[itod]

Nonetheless - I'm very excited with our progress so far and I'm confident that we'll be able to deliver the nice NanoFury devices in your hands as promised!

And we do appreciate your trust in us and all the support and encouraging feedback from the forum!

Congrats on the great work, vs3! It is so hard to get so much done in limited time, hope people will appreciate it.

[bigbeninlondon]

This was the last straw for me to not even consider these guys. Stack this on top of no video, no proof of work.. nothing.... don't waste your time
Might as well call it VaporFury1
If you are going to have a pre-order, SHOW US WHAT WE ARE ORDERING!

There's always got to be at least one.  Notice the username too.  Fitting.

[RicRock]

5 more ordered before the deadline 

[bitterdog]

This was the last straw for me to not even consider these guys. Stack this on top of no video, no proof of work.. nothing.... don't waste your time
Might as well call it VaporFury1
If you are going to have a pre-order, SHOW US WHAT WE ARE ORDERING!

There's always got to be at least one.  Notice the username too.  Fitting.

Always one what there chief? One who questions the word? I don't drink the koolaid without finding out what's in it. So far we saw a screwed up motherboard.. then the op states he soldere the usb connector on wrong.. very reassuring and comforting knowing this stuff isn't it?.. Just a little hint... if you fuck something up like that.. don't tell the people you are wanting to invest in you and your project so you don't look amature.

[bigbeninlondon]

This was the last straw for me to not even consider these guys. Stack this on top of no video, no proof of work.. nothing.... don't waste your time
Might as well call it VaporFury1
If you are going to have a pre-order, SHOW US WHAT WE ARE ORDERING!

There's always got to be at least one.  Notice the username too.  Fitting.

Always one what there chief? One who questions the word? I don't drink the koolaid without finding out what's in it. So far we saw a screwed up motherboard.. then the op states he soldere the usb connector on wrong.. very reassuring and comforting knowing this stuff isn't it?.. Just a little hint... if you fuck something up like that.. don't tell the people you are wanting to invest in you and your project so you don't look amature.

You called it vaporware.  Now that there is evidence of progress, suddenly it's not "vaporware" but "amateur hour".  You said "Show us what we are buying!" and then when they did, you criticized that.  If you don't like what you see, then move on. 

[Swimmer63]

This was the last straw for me to not even consider these guys. Stack this on top of no video, no proof of work.. nothing.... don't waste your time
Might as well call it VaporFury1
If you are going to have a pre-order, SHOW US WHAT WE ARE ORDERING!

There's always got to be at least one.  Notice the username too.  Fitting.

Always one what there chief? One who questions the word? I don't drink the koolaid without finding out what's in it. So far we saw a screwed up motherboard.. then the op states he soldere the usb connector on wrong.. very reassuring and comforting knowing this stuff isn't it?.. Just a little hint... if you fuck something up like that.. don't tell the people you are wanting to invest in you and your project so you don't look amature.

If you are not participating what are you doing here?

[vs3]

AAAAaaaaand it seems Slush likes our device!!! :-)



cgminer seems happy too:


I'll be posting some more pictures and stuff a bit later!

[rampantparanoia]

vs3, how long did you run that device to get 51 shares?

[nemercry]

AAAAaaaaand it seems Slush likes our device!!! :-)



cgminer seems happy too:


I'll be posting some more pictures and stuff a bit later!

Nice.
Could you do a testrun at higher speeds. Lets say longterm run aroung 2.1 - 2.3 GH/s?

[vs3]

vs3, how long did you run that device to get 51 shares?

Probably about 30 seconds... I was so excited when I saw the result that I took the screenshot right away

[vs3]

AAAAaaaaand it seems Slush likes our device!!! :-)

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

cgminer seems happy too:
https://i.imgur.com/DhwGucc.png

I'll be posting some more pictures and stuff a bit later!

Nice.
Could you do a testrun at higher speeds. Lets say longterm run aroung 2.1 - 2.3 GH/s?

Definitely. We'll be doing a lot of testing over the next few days and will certainly post more results and statistics.

[vs3]

PREORDER CLOSING TIME WILL BE 10:00 AM PACIFIC TIME ON OCT-2 (17:00 UTC)

UPDATE OCT/1 : We might be able to accommodate a few extra orders before we've purchased all components.
Any orders received after the final price has been announced will be required to prepay them in full.
We'll be ordering all components and services on Oct/6 and there will be no exceptions after that's happened!

Orders placed after that will be automatically cancelled!

Edit: Updated to match opening post (regarding last-minute orders)

[vs3]

In the mean time we got several requests for people to jump in the last second and place their order before the end of the week. Below is the update from the opening post in that regard:

UPDATE OCT/1 : We might be able to accommodate a few extra orders before we've purchased all components.
Any orders received after the final price has been announced will be required to prepay them in full.
We'll be ordering all components and services on Oct/6 and there will be no exceptions after that's happened!

[OleOle]

Any chance we could get another status update please? Maybe put it in a larger font or perhaps use another colour in case we miss it?

Thanks in advance 


-----



Heard near the water cooler:

"Did you hear about those guys making the new usb Fury devices in the United States?"
"No, I haven't heard. Are those the same devices that some people are calling Red Fury or Blue Fury?"
"I don't know, all I know is that some people prefer to wait a while and buy unseen devices rather than buy similar units that are fully operational."
"Really? Why the hell would they do that?"
"I have absolutely no idea."



-----

Reference: https://bitcointalk.org/index.php?topic=296953

[vs3]

Any chance we could get another status update please? Maybe put it in a larger font or perhaps use another colour in case we miss it?

Thanks in advance 
-----

I'll keep it in mind for the next update

[baros008]

......

Acknowledgments and other information:

* This project was inspired to a great extent by BKKCoin's Klondike K1 Nano Open Source Board and we're grateful for all his work and we'll continue to support his project down the road as we can!

* We've reused the same physical dimensions (including heatsink holes size and position) with the goal that if necessary we may share the same plastic hosing and/or heatsink. We are also planning to release this project as Open Source as well.

I ordered NF1s from marto74 because I am from EU and I would like to prepare heatsinks in advance. I can't find drawing of K1 Nano and I don't know if version 05 still reuses same physical dimensions.

So can you share drawing with physical dimensions of NF1?

[OtaconEmmerich]

I think I'm gunna wait for a final pricing before I even think about ordering even at BTC0.4 there's a very thin chance to get ROI if any at all. It would be different if it didn't take so long to get units in-hand.

[vs3]

......

Acknowledgments and other information:

* This project was inspired to a great extent by BKKCoin's Klondike K1 Nano Open Source Board and we're grateful for all his work and we'll continue to support his project down the road as we can!

* We've reused the same physical dimensions (including heatsink holes size and position) with the goal that if necessary we may share the same plastic hosing and/or heatsink. We are also planning to release this project as Open Source as well.

I ordered NF1s from marto74 because I am from EU and I would like to prepare heatsinks in advance. I can't find drawing of K1 Nano and I don't know if version 05 still reuses same physical dimensions.

So can you share drawing with physical dimensions of NF1?

Baros - I'll post that a bit later today.

[vs3]

As announced in the opening post:

PREORDER IS NOW CLOSED

UPDATE OCT/2 : We'll be announcing the final price at some point tomorrow (while we confirm actual component prices today and tomorrow).
As announced on Oct/1 we can still accommodate a few more orders but they will not influence the price anymore. Cut-off date for any additional last-minute orders is Oct/6.

[vs3]

UPDATE OCT/7 : We've now ordered all NanoFury NF1 devices for manufacturing. Everyone that placed an order has been sent an email with instructions for the second payment (which was also due to bitcointalk being down for several days). If you placed an order and did not get one with those instructions please send an email and PM to vs3 just in case and we'll get back to you

[vs3]

Here are the PCB dimensions and heatsink holes positions. Please note that holes would likely end up being a 0.1mm smaller (as they'll be metalized).

[baros008]

Thanks

[Luke-Jr]

Out of the 3 or 4 that I'll be putting together some will be going to the various miner software developers (e.g. one will be going to Luke-Jr so that he can start integrating support into his bfgminer, etc).

FWIW, I can confirm receipt of this. I plan to include NanoFury support in BFGMiner 3.4 at the latest.

[Taugeran]

Out of the 3 or 4 that I'll be putting together some will be going to the various miner software developers (e.g. one will be going to Luke-Jr so that he can start integrating support into his bfgminer, etc).

FWIW, I can confirm receipt of this. I plan to include NanoFury support in BFGMiner 3.4 at the latest.

Code:

woo. let us hear what hash rate you get out of it luke ^_^

also are these gunna be software overclockable with a bfgminer arg like --bitfury-osc6-bits NN

[erk]

I missed out on the group buy, I didn't see the thread in time. Will there be another? I just need one unit for a project.

[vs3]

I missed out on the group buy, I didn't see the thread in time. Will there be another? I just need one unit for a project.

Hi erk,

we've ordered some extra devices (to have spares in case of defective ones) and I'm pretty sure we would be able to send you one.

Place an order following the instructions in the opening post please - pick your shipping preferences and add that to the device' price of 0.53BTC. Don't forget to sign the message.

Also - we've been having problems with email clients adding/removing a space here and there (thus ruining the signature) so just in case sign also just the transaction ID (and don't add any text like "Transaction ID" etc.)

[erk]

I missed out on the group buy, I didn't see the thread in time. Will there be another? I just need one unit for a project.

Hi erk,

we've ordered some extra devices (to have spares in case of defective ones) and I'm pretty sure we would be able to send you one.

Place an order following the instructions in the opening post please - pick your shipping preferences and add that to the device' price of 0.53BTC. Don't forget to sign the message.

Also - we've been having problems with email clients adding/removing a space here and there (thus ruining the signature) so just in case sign also just the transaction ID (and don't add any text like "Transaction ID" etc.)

Thanks for that, much appreciated, payment has been sent. If the email doesn't verify let me know and I will send it from a console text email program that doesn't add stuff like the GUI ones do.

[nemercry]

Any Update on this ? Are there more Pictures of working units or any status updates ?

Regards

[vs3]

As for pictures - Marto74 will likely have the final devices within the next days to a week and we'll post some pictures of them as soon as they're ready.

In the mean time I've been experimenting with the engineering samples - I had one of them running with BitMinter for several days and one on Slush. At the moment using 54 bits produces a pretty stable 2.2-2.3GH output.

Some observations - at 54bits speed it is actually consuming a bit more than 2.5W - about 600-650mA which is roughly 3-3.2W and to my surprise all computers that I've tested so far let the device run (and it didn't trigger the over-current protection). So you might be able to actually "overclock" them by just setting a higher speed multiplier. You should keep in mind that the board will run quite hot - I've been checking with an infrared thermometer and the ones I've tested report 80-87C with just passive cooling (no fan).
You can also overclock them additionally by tweaking the voltage (e.g. doing the "pencil mod") and this will very likely yield 2.5-2.7GH easily. Boards will definitely be very hot though - you'll need to consider better cooling in that case.

Using 51 bits makes it consume just a tad over 500mA and that results in about 1.8-1.85 GH/s (in case you got a very restrictive USB2.0 board).

Below is the BitMinter data with the 54-bit speed I've been running over the last week or so (I used Excel and added the extra 2 columns at the end):

   No.       Completed  Duration  Total Ghps Difficulty  Your score Total score Your work Total work     My % work  My GH/s
   18532 10/10/2013 1:33  0h 57m   94,114.78 189,281,249 0.00000953  0.40055896     1,804 75,818,301  0.0000237937 2.239341
   18531 10/10/2013 0:35  0h 56m   96,182.10 189,281,249 0.00000943  0.40237726     1,784 76,162,470  0.0000234236 2.252932
   18530 10/9/2013 23:38  0h 56m   95,796.48 189,281,249  0.0000095  0.40076400     1,799 75,857,111  0.0000237156 2.271875
   18529 10/9/2013 22:41  0h 57m   95,018.86 189,281,249 0.00000968  0.40125102     1,832 75,949,294  0.0000241214 2.291984
   18528 10/9/2013 21:43  0h 57m   94,805.07 189,281,249 0.00000968  0.40338028     1,832 76,352,323  0.0000239940 2.274756
   18527 10/9/2013 20:45  0h 57m   95,004.77 189,281,249 0.00000927  0.40084093     1,754 75,871,672  0.0000231180 2.196319
   18526 10/9/2013 19:48  0h 57m   95,376.50 189,281,249 0.00000927  0.40170539     1,755 76,035,298  0.0000230814 2.201422
   18525 10/9/2013 18:50  0h 57m   95,233.18 189,281,249  0.0000096  0.40145319     1,818 75,987,561  0.0000239250 2.278451
   18524 10/9/2013 17:53  0h 57m   95,280.15 189,281,249 0.00000937  0.40141679     1,773 75,980,672  0.0000233349 2.223351
   18523 10/9/2013 16:55  0h 57m   94,909.45 189,281,249 0.00000969  0.40324069     1,835 76,325,902  0.0000240416 2.281779
   18522 10/9/2013 15:57  0h 58m   93,531.68 189,281,249 0.00000973  0.40152882     1,842 76,001,877  0.0000242362 2.266857
   18521 10/9/2013 14:59  0h 57m   94,356.86 189,281,249 0.00000932  0.40100897     1,765 75,903,479  0.0000232532 2.194101
   18520 10/9/2013 14:01  0h 58m   93,506.68 189,281,249  0.0000101  0.40038631     1,912 75,785,621  0.0000252291 2.359086
   18519 10/9/2013 13:02  0h 59m   91,907.31 189,281,249 0.00000973  0.40099947     1,841 75,901,680  0.0000242551 2.229218
   18518 10/9/2013 12:03  1h 00m   89,486.81 189,281,249  0.0000099  0.40045552     1,873 75,798,721  0.0000247102 2.211235
   18517 10/9/2013 11:02  0h 59m   91,254.05 189,281,249 0.00000921  0.40129222     1,743 75,957,092  0.0000229472 2.094022
   18516 10/9/2013 10:02  0h 59m   92,273.10 189,281,249 0.00000968  0.40236844     1,833 76,160,801  0.0000240675 2.220783
   18515  10/9/2013 9:02  0h 58m   93,226.31 189,281,249 0.00001013  0.40297009     1,918 76,274,682  0.0000251460 2.344265
   18514  10/9/2013 8:03  0h 58m   93,150.22 189,281,249 0.00000966  0.40287035     1,829 76,255,804  0.0000239851 2.234214
   18513  10/9/2013 7:04  0h 58m   92,987.94 189,281,249 0.00000966  0.40216847     1,828 76,122,950  0.0000240138 2.232992
                                                                                                              Avg: 2.244949

Here are some screenshots:


Above table from Bitminter: and after running several days:

Running on Slush: and then 40+ hours later:

[BadAss.Sx]

I know i am a little bit late, but can i order also? Normally i am active here, but i had e few unpleasant weeks behind me, so i missed out this one

[viriat0]

great update keep up!

[vs3]

I know i am a little bit late, but can i order also? Normally i am active here, but i had e few unpleasant weeks behind me, so i missed out this one

Hello,

I might be able to get you one or two the most, but no promises. We ordered some extra ones to have spares (to replace defective ones) but it would all depend on how it goes.

As for ordering - follow the same instructions as from a few posts ago:

Place an order following the instructions in the opening post please - pick your shipping preferences and add that to the device' price of 0.53BTC. Don't forget to sign the message.

Also - we've been having problems with email clients adding/removing a space here and there (thus ruining the signature) so just in case sign also just the transaction ID (and don't add any text like "Transaction ID" etc.).

Send an email and also just in case send me a copy of the signed stuff in a PM.

[Swimmer63]

Any delivery / assembly / shipping updates Vs3?

[vs3]

Any delivery / assembly / shipping updates Vs3?

Nothing much newer than what I wrote yesterday.

Marto74 got the PCBs and everything has been sent to the assembly factory.
Marto mentioned the other day that if everything goes as planned we should have the first devices on Friday or early next week and hopefully all devices at some point next week. As soon as the first devices are in he'll be doing some extra testing on them to make sure everything is good so in case if it isn't we can fix it before all devices are assembled. (and so that we can catch things like let's say some component is flipped like the LED on one of my previous project, etc).

I guess until that happens there isn't going to be anything to report. Probably the next significant news update will be in the beginning of next week.

[JoRoidx]

vs3
I would love to buy a couple of these units, are they cheaper if they are not put together?
I normally do not use a Bitcoin wallet, I used Coinbase and Mt.gox, is there away I can get in on the buy?

JoRoidx

[Luke-Jr]

Code:

 bfgminer version 3.3.0 - Started: [2013-10-16 16:57:08] - [  0 days 00:17:00]
 [M]anage devices [P]ool management [S]ettings [D]isplay options  [H]elp [Q]uit 
 Connected to mining.eligius.st diff 2 with stratum as user x
 Block: ...0441d23a #264126  Diff:268M ( 1.92Ph/s)  Started: [16:59:59]
 ST:2  F:0  NB:2  AS:0  BW:[103/ 34 B/s]  E:8.42  I:  190uBTC/hr  BS:129
 1            |  2.49/ 2.44/ 2.51Gh/s | A:287 R:1+0(.35%) HW:11/1.8%
--------------------------------------------------------------------------------
 NFY 0:       |  2.43/ 2.45/ 2.53Gh/s | A:288 R:1+0(.35%) HW:11/1.8%
--------------------------------------------------------------------------------
 [2013-10-16 17:12:56.715328] Stratum from pool 0 requested work update
 [2013-10-16 17:12:57.383380] Accepted 5ad11cc2 NFY 0  Diff 2/2
 [2013-10-16 17:12:58.964609] Accepted 3dd03c65 NFY 0  Diff 4/2
 [2013-10-16 17:13:02.832086] Accepted 5e1db25d NFY 0  Diff 2/2
 [2013-10-16 17:13:07.178307] Accepted 73924629 NFY 0  Diff 2/2
 [2013-10-16 17:13:10.591666] Accepted 41377ee1 NFY 0  Diff 3/2
 [2013-10-16 17:13:11.191507] Accepted 4e81a07a NFY 0  Diff 3/2
 [2013-10-16 17:13:26.225879] Accepted 564eba42 NFY 0  Diff 2/2
 [2013-10-16 17:13:27.425181] Accepted 609b937b NFY 0  Diff 2/2
 [2013-10-16 17:13:28.768057] Accepted 0e4fbd6a NFY 0  Diff 17/2
 [2013-10-16 17:13:29.501953] Accepted 54ff281c NFY 0  Diff 3/2
 [2013-10-16 17:13:32.633905] Accepted 781b7ce4 NFY 0  Diff 2/2
 [2013-10-16 17:13:35.459990] Accepted 1fb0e690 NFY 0  Diff 8/2
 [2013-10-16 17:13:50.062610] Accepted 5f6e97f8 NFY 0  Diff 2/2
 [2013-10-16 17:13:51.725775] Stratum from pool 0 requested work update
 [2013-10-16 17:13:53.184233] Accepted 250d457b NFY 0  Diff 6/2
 [2013-10-16 17:14:00.036483] Accepted 355fdf81 NFY 0  Diff 4/2
 [2013-10-16 17:14:00.649419] Accepted 55365bbf NFY 0  Diff 3/2
 [2013-10-16 17:14:01.376224] Accepted 25199743 NFY 0  Diff 6/2

[bigbeninlondon]

Code:

 bfgminer version 3.3.0 - Started: [2013-10-16 16:57:08] - [  0 days 00:17:00]
 [M]anage devices [P]ool management [S]ettings [D]isplay options  [H]elp [Q]uit 
 Connected to mining.eligius.st diff 2 with stratum as user x
 Block: ...0441d23a #264126  Diff:268M ( 1.92Ph/s)  Started: [16:59:59]
 ST:2  F:0  NB:2  AS:0  BW:[103/ 34 B/s]  E:8.42  I:  190uBTC/hr  BS:129
 1            |  2.49/ 2.44/ 2.51Gh/s | A:287 R:1+0(.35%) HW:11/1.8%
--------------------------------------------------------------------------------
 NFY 0:       |  2.43/ 2.45/ 2.53Gh/s | A:288 R:1+0(.35%) HW:11/1.8%
--------------------------------------------------------------------------------
 [2013-10-16 17:12:56.715328] Stratum from pool 0 requested work update
 [2013-10-16 17:12:57.383380] Accepted 5ad11cc2 NFY 0  Diff 2/2
 [2013-10-16 17:12:58.964609] Accepted 3dd03c65 NFY 0  Diff 4/2
 [2013-10-16 17:13:02.832086] Accepted 5e1db25d NFY 0  Diff 2/2
 [2013-10-16 17:13:07.178307] Accepted 73924629 NFY 0  Diff 2/2
 [2013-10-16 17:13:10.591666] Accepted 41377ee1 NFY 0  Diff 3/2
 [2013-10-16 17:13:11.191507] Accepted 4e81a07a NFY 0  Diff 3/2
 [2013-10-16 17:13:26.225879] Accepted 564eba42 NFY 0  Diff 2/2
 [2013-10-16 17:13:27.425181] Accepted 609b937b NFY 0  Diff 2/2
 [2013-10-16 17:13:28.768057] Accepted 0e4fbd6a NFY 0  Diff 17/2
 [2013-10-16 17:13:29.501953] Accepted 54ff281c NFY 0  Diff 3/2
 [2013-10-16 17:13:32.633905] Accepted 781b7ce4 NFY 0  Diff 2/2
 [2013-10-16 17:13:35.459990] Accepted 1fb0e690 NFY 0  Diff 8/2
 [2013-10-16 17:13:50.062610] Accepted 5f6e97f8 NFY 0  Diff 2/2
 [2013-10-16 17:13:51.725775] Stratum from pool 0 requested work update
 [2013-10-16 17:13:53.184233] Accepted 250d457b NFY 0  Diff 6/2
 [2013-10-16 17:14:00.036483] Accepted 355fdf81 NFY 0  Diff 4/2
 [2013-10-16 17:14:00.649419] Accepted 55365bbf NFY 0  Diff 3/2
 [2013-10-16 17:14:01.376224] Accepted 25199743 NFY 0  Diff 6/2

Good to see!  Thanks Luke-Jr.

[Luke-Jr]

Note the hashrate there is overclocked. It overheated not long after I posted the screen.
To meet USB 2 specs, it'll probably be closer to the 2 Gh/s advertised.

[Taugeran]

Note the hashrate there is overclocked. It overheated not long after I posted the screen.
To meet USB 2 specs, it'll probably be closer to the 2 Gh/s advertised.

how bad of an overheat? and powered hub or host port?  could an active usb fan help?

[Luke-Jr]

Note the hashrate there is overclocked. It overheated not long after I posted the screen.
To meet USB 2 specs, it'll probably be closer to the 2 Gh/s advertised.

how bad of an overheat? and powered hub or host port?  could an active usb fan help?

Even running at spec, these things get pretty hot.
This was on a powered USB 3 hub, with no cooling.

[vs3]

Note the hashrate there is overclocked. It overheated not long after I posted the screen.
To meet USB 2 specs, it'll probably be closer to the 2 Gh/s advertised.

how bad of an overheat? and powered hub or host port?  could an active usb fan help?

A small fan would certainly help. That's my observations (from a few posts above) :

You should keep in mind that the board will run quite hot - I've been checking with an infrared thermometer and the ones I've tested report 80-87C with just passive cooling (no fan).

Note that going way over 85C would probably lead to unknown side effects. Bitfury's chips are known to be able to take quite a lot of heat but the rest of the components may not behave well at such conditions.

Chips have been tested to run at extreme temperatures. One user used a soldering iron to heat the chip to the point it desoldered. Hashing stopped only when chip started floating on solder and shortcircuited.

[Taugeran]

Chips have been tested to run at extreme temperatures. One user used a soldering iron to heat the chip to the point it desoldered. Hashing stopped only when chip started floating on solder and shortcircuited.

dafuq O.o

[Taugeran]

Chips have been tested to run at extreme temperatures. One user used a soldering iron to heat the chip to the point it desoldered. Hashing stopped only when chip started floating on solder and shortcircuited.

dafuq O.o

and a side note did the diff really jump 80M?

[vs3]

Chips have been tested to run at extreme temperatures. One user used a soldering iron to heat the chip to the point it desoldered. Hashing stopped only when chip started floating on solder and shortcircuited.

dafuq O.o

What can I say ... the bitfury chip is a Russian design
Their stuff may not always be the prettiest or most efficient but it's been known to work when nothing else works ...

[Taugeran]

Chips have been tested to run at extreme temperatures. One user used a soldering iron to heat the chip to the point it desoldered. Hashing stopped only when chip started floating on solder and shortcircuited.

dafuq O.o

What can I say ... the bitfury chip is a Russian design
Their stuff may not always be the prettiest or most efficient but it's been known to work when nothing else works ...

true that

ßfury
-Built like an AK-47

[Luke-Jr]

Got 2 nanofuries mining away overclocked to 53 osc6-bits on my USB 3 hub. Stable for 5½ hours so far.
Pool stats: http://eligius.st/~wizkid057/newstats/userstats.php/16kNKa7WUg8QAPFy8dJRv7USSu2fAG2pkW

Code:

 bfgminer version 3.3.0 - Started: [2013-10-16 19:30:51] - [  0 days 05:34:25]
 [M]anage devices [P]ool management [S]ettings [D]isplay options  [H]elp [Q]uit 
 Connected to mining.eligius.st diff 2 with stratum as user 16kNKa7WUg8QAPFy8dJRv7USSu2fAG2pk
 Block: ...ec421847 #264187  Diff:268M ( 1.92Ph/s)  Started: [00:58:54]
 ST:2  F:1  NB:46  AS:0  BW:[100/ 82 B/s]  E:11.61  I:  349uBTC/hr  BS:39k
 2            |  4.49/ 4.58/ 4.49Gh/s | A:10412 R:41+67(1.0%) HW:75/.35%
--------------------------------------------------------------------------------
 NFY 0:       |  2.27/ 2.27/ 2.21Gh/s | A: 5106 R:19+30(.95%) HW:28/.27%
 NFY 1:       |  2.30/ 2.31/ 2.28Gh/s | A: 5306 R:22+37(1.1%) HW:47/.44%
--------------------------------------------------------------------------------
 [2013-10-17 01:04:39.133427] Accepted 7f12bc92 NFY 1  Diff 2/2
 [2013-10-17 01:04:40.187387] Accepted 454b4f89 NFY 1  Diff 3/2
 [2013-10-17 01:04:40.751288] Accepted 67e0abdd NFY 0  Diff 2/2
 [2013-10-17 01:04:44.327965] Accepted 28d1d632 NFY 0  Diff 6/2
 [2013-10-17 01:04:47.043346] Accepted 194a179b NFY 1  Diff 10/2
 [2013-10-17 01:04:55.978596] Accepted 1c6fcfd0 NFY 1  Diff 9/2
 [2013-10-17 01:04:56.836878] Accepted 7e1929d9 NFY 0  Diff 2/2
 [2013-10-17 01:04:57.158243] Accepted 116bee29 NFY 1  Diff 14/2
 [2013-10-17 01:04:57.297099] Accepted 04ce8b4c NFY 1  Diff 53/2
 [2013-10-17 01:04:58.105164] Accepted 3f2081c5 NFY 1  Diff 4/2
 [2013-10-17 01:05:00.583995] Accepted 5dc8bb49 NFY 0  Diff 2/2
 [2013-10-17 01:05:02.203167] Accepted 0d08dcc0 NFY 0  Diff 19/2
 [2013-10-17 01:05:03.708555] Accepted 6fdf6dc0 NFY 0  Diff 2/2
 [2013-10-17 01:05:04.614318] Accepted 63ff6b24 NFY 1  Diff 2/2
 [2013-10-17 01:05:05.672861] Accepted 2dfeb64e NFY 0  Diff 5/2
 [2013-10-17 01:05:06.126697] Accepted 370eb922 NFY 0  Diff 4/2
 [2013-10-17 01:05:06.275658] Accepted 304ba398 NFY 1  Diff 5/2
 [2013-10-17 01:05:09.964627] Accepted 1ed02065 NFY 0  Diff 8/2
 [2013-10-17 01:05:11.624928] Accepted 1db54bee NFY 0  Diff 8/2
 [2013-10-17 01:05:11.769494] Accepted 02aa49ad NFY 1  Diff 96/2
 [2013-10-17 01:05:12.659018] Accepted 0b79f1eb NFY 0  Diff 22/2
 [2013-10-17 01:05:13.250872] Accepted 781367a3 NFY 0  Diff 2/2
 [2013-10-17 01:05:14.877515] Accepted 3e63c5f7 NFY 0  Diff 4/2
 [2013-10-17 01:05:17.013139] Accepted 3f623edb NFY 1  Diff 4/2
 [2013-10-17 01:05:20.096350] Accepted 1ea01258 NFY 0  Diff 8/2
 [2013-10-17 01:05:21.763496] Accepted 2cfa45ec NFY 1  Diff 5/2
 [2013-10-17 01:05:26.004017] Stratum from pool 0 requested work update
 [2013-10-17 01:05:28.590438] Accepted 7e81a4d8 NFY 0  Diff 2/2
 [2013-10-17 01:05:31.426182] Accepted 188138cf NFY 0  Diff 10/2
 [2013-10-17 01:05:31.876986] Accepted 544b98b7 NFY 1  Diff 3/2

[erk]

Got 2 nanofuries mining away overclocked to 53 osc6-bits on my USB 3 hub. Stable for 5½ hours so far.
Pool stats: http://eligius.st/~wizkid057/newstats/userstats.php/16kNKa7WUg8QAPFy8dJRv7USSu2fAG2pkW

Code:

 bfgminer version 3.3.0 - Started: [2013-10-16 19:30:51] - [  0 days 05:34:25]
 [M]anage devices [P]ool management [S]ettings [D]isplay options  [H]elp [Q]uit 
 Connected to mining.eligius.st diff 2 with stratum as user 16kNKa7WUg8QAPFy8dJRv7USSu2fAG2pk
 Block: ...ec421847 #264187  Diff:268M ( 1.92Ph/s)  Started: [00:58:54]
 ST:2  F:1  NB:46  AS:0  BW:[100/ 82 B/s]  E:11.61  I:  349uBTC/hr  BS:39k
 2            |  4.49/ 4.58/ 4.49Gh/s | A:10412 R:41+67(1.0%) HW:75/.35%
--------------------------------------------------------------------------------
 NFY 0:       |  2.27/ 2.27/ 2.21Gh/s | A: 5106 R:19+30(.95%) HW:28/.27%
 NFY 1:       |  2.30/ 2.31/ 2.28Gh/s | A: 5306 R:22+37(1.1%) HW:47/.44%
--------------------------------------------------------------------------------
 [2013-10-17 01:04:39.133427] Accepted 7f12bc92 NFY 1  Diff 2/2
 [2013-10-17 01:04:40.187387] Accepted 454b4f89 NFY 1  Diff 3/2
 [2013-10-17 01:04:40.751288] Accepted 67e0abdd NFY 0  Diff 2/2
 [2013-10-17 01:04:44.327965] Accepted 28d1d632 NFY 0  Diff 6/2
 [2013-10-17 01:04:47.043346] Accepted 194a179b NFY 1  Diff 10/2
 [2013-10-17 01:04:55.978596] Accepted 1c6fcfd0 NFY 1  Diff 9/2
 [2013-10-17 01:04:56.836878] Accepted 7e1929d9 NFY 0  Diff 2/2
 [2013-10-17 01:04:57.158243] Accepted 116bee29 NFY 1  Diff 14/2
 [2013-10-17 01:04:57.297099] Accepted 04ce8b4c NFY 1  Diff 53/2
 [2013-10-17 01:04:58.105164] Accepted 3f2081c5 NFY 1  Diff 4/2
 [2013-10-17 01:05:00.583995] Accepted 5dc8bb49 NFY 0  Diff 2/2
 [2013-10-17 01:05:02.203167] Accepted 0d08dcc0 NFY 0  Diff 19/2
 [2013-10-17 01:05:03.708555] Accepted 6fdf6dc0 NFY 0  Diff 2/2
 [2013-10-17 01:05:04.614318] Accepted 63ff6b24 NFY 1  Diff 2/2
 [2013-10-17 01:05:05.672861] Accepted 2dfeb64e NFY 0  Diff 5/2
 [2013-10-17 01:05:06.126697] Accepted 370eb922 NFY 0  Diff 4/2
 [2013-10-17 01:05:06.275658] Accepted 304ba398 NFY 1  Diff 5/2
 [2013-10-17 01:05:09.964627] Accepted 1ed02065 NFY 0  Diff 8/2
 [2013-10-17 01:05:11.624928] Accepted 1db54bee NFY 0  Diff 8/2
 [2013-10-17 01:05:11.769494] Accepted 02aa49ad NFY 1  Diff 96/2
 [2013-10-17 01:05:12.659018] Accepted 0b79f1eb NFY 0  Diff 22/2
 [2013-10-17 01:05:13.250872] Accepted 781367a3 NFY 0  Diff 2/2
 [2013-10-17 01:05:14.877515] Accepted 3e63c5f7 NFY 0  Diff 4/2
 [2013-10-17 01:05:17.013139] Accepted 3f623edb NFY 1  Diff 4/2
 [2013-10-17 01:05:20.096350] Accepted 1ea01258 NFY 0  Diff 8/2
 [2013-10-17 01:05:21.763496] Accepted 2cfa45ec NFY 1  Diff 5/2
 [2013-10-17 01:05:26.004017] Stratum from pool 0 requested work update
 [2013-10-17 01:05:28.590438] Accepted 7e81a4d8 NFY 0  Diff 2/2
 [2013-10-17 01:05:31.426182] Accepted 188138cf NFY 0  Diff 10/2
 [2013-10-17 01:05:31.876986] Accepted 544b98b7 NFY 1  Diff 3/2

Fans blowing on them or just static testing?

[vs3]

Got 2 nanofuries mining away overclocked to 53 osc6-bits on my USB 3 hub. Stable for 5½ hours so far.
Pool stats: http://eligius.st/~wizkid057/newstats/userstats.php/16kNKa7WUg8QAPFy8dJRv7USSu2fAG2pkW

Code:

 bfgminer version 3.3.0 - Started: [2013-10-16 19:30:51] - [  0 days 05:34:25]
 [M]anage devices [P]ool management [S]ettings [D]isplay options  [H]elp [Q]uit 
 Connected to mining.eligius.st diff 2 with stratum as user 16kNKa7WUg8QAPFy8dJRv7USSu2fAG2pk
 Block: ...ec421847 #264187  Diff:268M ( 1.92Ph/s)  Started: [00:58:54]
 ST:2  F:1  NB:46  AS:0  BW:[100/ 82 B/s]  E:11.61  I:  349uBTC/hr  BS:39k
 2            |  4.49/ 4.58/ 4.49Gh/s | A:10412 R:41+67(1.0%) HW:75/.35%
--------------------------------------------------------------------------------
 NFY 0:       |  2.27/ 2.27/ 2.21Gh/s | A: 5106 R:19+30(.95%) HW:28/.27%
 NFY 1:       |  2.30/ 2.31/ 2.28Gh/s | A: 5306 R:22+37(1.1%) HW:47/.44%
--------------------------------------------------------------------------------
 [2013-10-17 01:04:39.133427] Accepted 7f12bc92 NFY 1  Diff 2/2
 [2013-10-17 01:04:40.187387] Accepted 454b4f89 NFY 1  Diff 3/2
 [2013-10-17 01:04:40.751288] Accepted 67e0abdd NFY 0  Diff 2/2
 [2013-10-17 01:04:44.327965] Accepted 28d1d632 NFY 0  Diff 6/2
 [2013-10-17 01:04:47.043346] Accepted 194a179b NFY 1  Diff 10/2
 [2013-10-17 01:04:55.978596] Accepted 1c6fcfd0 NFY 1  Diff 9/2
 [2013-10-17 01:04:56.836878] Accepted 7e1929d9 NFY 0  Diff 2/2
 [2013-10-17 01:04:57.158243] Accepted 116bee29 NFY 1  Diff 14/2
 [2013-10-17 01:04:57.297099] Accepted 04ce8b4c NFY 1  Diff 53/2
 [2013-10-17 01:04:58.105164] Accepted 3f2081c5 NFY 1  Diff 4/2
 [2013-10-17 01:05:00.583995] Accepted 5dc8bb49 NFY 0  Diff 2/2
 [2013-10-17 01:05:02.203167] Accepted 0d08dcc0 NFY 0  Diff 19/2
 [2013-10-17 01:05:03.708555] Accepted 6fdf6dc0 NFY 0  Diff 2/2
 [2013-10-17 01:05:04.614318] Accepted 63ff6b24 NFY 1  Diff 2/2
 [2013-10-17 01:05:05.672861] Accepted 2dfeb64e NFY 0  Diff 5/2
 [2013-10-17 01:05:06.126697] Accepted 370eb922 NFY 0  Diff 4/2
 [2013-10-17 01:05:06.275658] Accepted 304ba398 NFY 1  Diff 5/2
 [2013-10-17 01:05:09.964627] Accepted 1ed02065 NFY 0  Diff 8/2
 [2013-10-17 01:05:11.624928] Accepted 1db54bee NFY 0  Diff 8/2
 [2013-10-17 01:05:11.769494] Accepted 02aa49ad NFY 1  Diff 96/2
 [2013-10-17 01:05:12.659018] Accepted 0b79f1eb NFY 0  Diff 22/2
 [2013-10-17 01:05:13.250872] Accepted 781367a3 NFY 0  Diff 2/2
 [2013-10-17 01:05:14.877515] Accepted 3e63c5f7 NFY 0  Diff 4/2
 [2013-10-17 01:05:17.013139] Accepted 3f623edb NFY 1  Diff 4/2
 [2013-10-17 01:05:20.096350] Accepted 1ea01258 NFY 0  Diff 8/2
 [2013-10-17 01:05:21.763496] Accepted 2cfa45ec NFY 1  Diff 5/2
 [2013-10-17 01:05:26.004017] Stratum from pool 0 requested work update
 [2013-10-17 01:05:28.590438] Accepted 7e81a4d8 NFY 0  Diff 2/2
 [2013-10-17 01:05:31.426182] Accepted 188138cf NFY 0  Diff 10/2
 [2013-10-17 01:05:31.876986] Accepted 544b98b7 NFY 1  Diff 3/2

Fans blowing on them or just static testing?

I think he mentioned before that it was just passive cooling - no fans.

Edit: I found it:

This was on a powered USB 3 hub, with no cooling.

[Luke-Jr]

Fans blowing on them or just static testing?

Still no fans. Ambient is somewhere around 27 C / 80 F.

[Taugeran]

Fans blowing on them or just static testing?

Still no fans. Ambient is somewhere around 27 C / 80 F.

where do you set the osc6 bits in the source?

[Luke-Jr]

Fans blowing on them or just static testing?

Still no fans. Ambient is somewhere around 27 C / 80 F.

where do you set the osc6 bits in the source?

driver-nanofury.c, nanofury_init, currently line 271.
Or just use the RPC procset method.

[Taugeran]

Fans blowing on them or just static testing?

Still no fans. Ambient is somewhere around 27 C / 80 F.

where do you set the osc6 bits in the source?

driver-nanofury.c, nanofury_init, currently line 271.
Or just use the RPC procset method.

looked at the git branch graph. you took these from 0 to hashing in under 2 days

[vs3]

just to update everyone on the current status - reposting the relevant stuff from Marto74 :

Nano furies are still in production.
I hope We'll be able to start shipping too.

[Taugeran]

any ideas on wether or not this hub would allow over clocking beyond 50 osc6 bits if they were plugged into the 1.2 A ports?

[vs3]

any ideas on wether or not this hub would allow over clocking beyond 50 osc6 bits if they were plugged into the 1.2 A ports?

I think there is a very good chance it will work - with more power you could easily go up to 53-54 bits. Have in mind that the higher the speed the more heat you'll get. So, cooling will be a must.

[gusto88]

any ideas on wether or not this hub would allow over clocking beyond 50 osc6 bits if they were plugged into he 1.2 A ports?

The 1.2A ports only work, if no computer is connected! On the page you will find a footnote:

2 Enter the Fast-Charge Mode by disconnecting the DUB-H7 from your computer, or by powering off your computer. It is recommended that the total power consumption of
the connected USB devices should not exceed 2.4 A, or 12 W.

I would recommend an USB3 Hub. USB3 allows up to 900mA per port.

[Taugeran]

any ideas on wether or not this hub would allow over clocking beyond 50 osc6 bits if they were plugged into he 1.2 A ports?

The 1.2A ports only work, if no computer is connected! On the page you will find a footnote:

2 Enter the Fast-Charge Mode by disconnecting the DUB-H7 from your computer, or by powering off your computer. It is recommended that the total power consumption of
the connected USB devices should not exceed 2.4 A, or 12 W.

I would recommend an USB3 Hub. USB3 allows up to 900mA per port.

any recommendations on one for an rpi?

[thomas_s]

any ideas on wether or not this hub would allow over clocking beyond 50 osc6 bits if they were plugged into he 1.2 A ports?

The 1.2A ports only work, if no computer is connected! On the page you will find a footnote:

2 Enter the Fast-Charge Mode by disconnecting the DUB-H7 from your computer, or by powering off your computer. It is recommended that the total power consumption of
the connected USB devices should not exceed 2.4 A, or 12 W.

I would recommend an USB3 Hub. USB3 allows up to 900mA per port.

any recommendations on one for an rpi?

rPi doesn't support USB3.0 unless its updated now.

[Taugeran]

any ideas on wether or not this hub would allow over clocking beyond 50 osc6 bits if they were plugged into he 1.2 A ports?

The 1.2A ports only work, if no computer is connected! On the page you will find a footnote:

2 Enter the Fast-Charge Mode by disconnecting the DUB-H7 from your computer, or by powering off your computer. It is recommended that the total power consumption of
the connected USB devices should not exceed 2.4 A, or 12 W.

I would recommend an USB3 Hub. USB3 allows up to 900mA per port.

any recommendations on one for an rpi?

rPi doesn't support USB3.0 unless its updated now.

Interesting. found this quote on Dlink's page specs tab

Diagnostic LEDs
Standard Mode (blue)
Fast Charge Mode (green)
Supplied Charging Current1

and plugged into my pi the light is green O.o it just might work!!!! puahahahahaha. gotta wait and see :/

[Taugeran]

also found https://github.com/mkorenkov/ipad_charge can be easily modified to work with any usb powered miner for that matter  

or even added to certain top of the line mining host software

[philipma1957]

also found https://github.com/mkorenkov/ipad_charge can be easily modified to work with any usb powered miner for that matter  

or even added to certain top of the line mining host software

http://www.amazon.com/gp/product/B00BZABE72/ref=oh_details_o00_s00_i00?ie=UTF8&psc=1   


 this hub is going to work well   .. I have 4 of them and no sticks as I ordered from ssinc's buy and he has had a long delay I canceled and got a refund.  I may have been better off ordering here.   these hubs have a smart power chip http://www.gearmo.com/shop/gm-3dh7/


and at amazon they are 29.99 the brick is 5volt 4 amp but you could attach this


http://www.amazon.com/dp/B00EKTZNAE?psc=1     I believe  that 3x hubs for 90 and this psu for 30 a total of 120 usd

would allow 21 hubs well spaced and well powered.  play it safe use 6 sticks a hub with 3 fans and you would have a beast. oc like a mofo.

[gusto88]

any ideas on wether or not this hub would allow over clocking beyond 50 osc6 bits if they were plugged into he 1.2 A ports?

The 1.2A ports only work, if no computer is connected! On the page you will find a footnote:

2 Enter the Fast-Charge Mode by disconnecting the DUB-H7 from your computer, or by powering off your computer. It is recommended that the total power consumption of
the connected USB devices should not exceed 2.4 A, or 12 W.

I would recommend an USB3 Hub. USB3 allows up to 900mA per port.

any recommendations on one for an rpi?

rPi doesn't support USB3.0 unless its updated now.

rPI supports USB3. Update the kernel, on raspbian with "sudo rpi-update".

[RicRock]

rPI supports USB3. Update the kernel, on raspbian with "sudo rpi-update".

I thought the no USB 3  was a hardware thing... not a software thing

[erk]

rPI supports USB3. Update the kernel, on raspbian with "sudo rpi-update".

I thought the no USB 3  was a hardware thing... not a software thing

Both you have to be able to detect USB 3 features.

Hubs are misleading, I just received a 10 port USB 2.0 hub and it had a 500mA plug pack! So you can drive a max or 1 port at proper USB 2.0 spec.

I think the NF1 could benefit from a good USB 3.0 hub if you are going to run several of them. but make sure you study the specs carefully and be certain it is in a good hub.

[Luke-Jr]

This hub seems to work well

[philipma1957]

This hub seems to work well

 I had a few of them they like a better brick but with a better 5 amp or 6 amp brick they are good.

[Taugeran]

@vs3 or ljr: how much does each osc6 bit increase appear to increase hashrate by? my math is saying anywhere from 35mh/s up to 50mh/s.


just curious on your results



edit: my math is probably fudged. :/

[vs3]

Taugeran - I'll give it a try.

Have in mind that no two chips are the same, so you might get slightly varying results. Also - since the hashrate fluctuates it will have to be run for at least 12-24hrs before we have some statistically accurate numbers for comparison.

[Taugeran]

Taugeran - I'll give it a try.

Have in mind that no two chips are the same, so you might get slightly varying results. Also - since the hashrate fluctuates it will have to be run for at least 12-24hrs before we have some statistically accurate numbers for comparison.

fair enough

[nemercry]

@Vs3: as i will shortly receive my sticks. is it possible to give an update how to start those sticks ?
On Linux and on Windows please.

Regards.

[Taugeran]

@Vs3: as i will shortly receive my sticks. is it possible to give an update how to start those sticks ?
On Linux and on Windows please.

Regards.

from Microchip's MCP2210 webpage:

Uses standard HID drivers (built-in support on Windows® XP, Vista, 7, Linux and Mac OS®)


So on both OSes it should be a matter of plug and play. it should be auto detected i believe and with cgminer the only thing cg looks for is the USB VID:PID combo to identify the device.

bfminer you will probably have to add -S ......


heres an example from his dev work with cgminer

[vs3]

I'll follow up with Luke-Jr to see if we can get pre-compiled binaries for Linux.

I'm currently trying to set up my Windows box for compiling bfgminer and as soon as I get through the various missing pieces I'll post a zip with the exe and all other required dlls.

In the mean time we're also working on final tweaks to cgminer - I'll post a link to the Windows executable in the next few days as well.

We'll be publishing all source code as well, so anyone can compile his or her own binaries. On a theory everything should be compile-able for Linux too but I don't have the experience there to do a proper testing, so any help in that regard would certainly be welcome.

[Luke-Jr]

My webserver will build any bfgminer branch for Windows: http://luke.dashjr.org/tmp/code/webisect/webisect.php?dobuild=nanofury

Every Linux-based OS really needs its own package/binary - there is no good runs-everywhere solution.

[vs3]

My webserver will build any bfgminer branch for Windows: http://luke.dashjr.org/tmp/code/webisect/webisect.php?dobuild=nanofury

Every Linux-based OS really needs its own package/binary - there is no good runs-everywhere solution.

Luke - I don't know if I've mentioned that before, but ... YOU ROCK!!!

[bigbeninlondon]

This hub seems to work well

Here's the specs from the mfg website:

http://www.orico.com.cn/en/ProductInfo.aspx?typeid=237&id=2078

It says the brick is only 4A; 400mA per port seems low.  Isn't USB3.0 specs 900mA per port?

[nemercry]

Yeah im really amazed to get them. Lets hope Marto will give some information out soon.

 

[Luke-Jr]

This hub seems to work well

Here's the specs from the mfg website:

http://www.orico.com.cn/en/ProductInfo.aspx?typeid=237&id=2078

It says the brick is only 4A; 400mA per port seems low.  Isn't USB3.0 specs 900mA per port?

The brick is 4A @ 12V = 48 W.
48 W / 5V = 9.6A = 10 ports at 0.9A each + 0.6A leftover

[bigbeninlondon]

This hub seems to work well

Here's the specs from the mfg website:

http://www.orico.com.cn/en/ProductInfo.aspx?typeid=237&id=2078

It says the brick is only 4A; 400mA per port seems low.  Isn't USB3.0 specs 900mA per port?

The brick is 4A @ 12V = 48 W.
48 W / 5V = 9.6A = 10 ports at 0.9A each + 0.6A leftover

Aha, didn't notice the voltage.

Thanks for clarifying.

[vs3]

Taugeran - I'll give it a try.

Have in mind that no two chips are the same, so you might get slightly varying results. Also - since the hashrate fluctuates it will have to be run for at least 12-24hrs before we have some statistically accurate numbers for comparison.

fair enough

So, I left one of the slightly under-voltaged sticks run at 54 bits for a bit and that's what I got:

Code:

 No.     Completed     Duration Total Ghps  Difficulty  Your score  Total score Your work Total work     My %      My GH
18951  10/24/2013 4:28   0h 41m  188,383.90 267,731,249   0.00000455 0.40399681   1,217   108,162,570 0.0000112516 2.1196
18950  10/24/2013 3:47   0h 41m  187,203.10 267,731,249   0.00000457 0.40179013   1,223   107,571,773 0.0000113692 2.1283
18949  10/24/2013 3:05   0h 40m  189,955.13 267,731,249   0.00000493 0.40174980   1,319   107,560,976 0.0000122628 2.3294
18948  10/24/2013 2:25   0h 41m  187,332.84 267,731,249   0.00000502 0.40337190   1,345   107,995,263 0.0000124542 2.3331
18947  10/24/2013 1:43   0h 40m  187,984.87 267,731,249   0.00000461 0.40101584   1,235   107,364,471 0.0000115029 2.1624
18946  10/24/2013 1:02   0h 41m  186,340.49 267,731,249   0.00000495 0.40091102   1,326   107,336,409 0.0000123537 2.3020
18945  10/24/2013 0:20   0h 41m  187,377.36 267,731,249   0.00000465 0.40183825   1,246   107,584,656 0.0000115816 2.1701
18944 10/23/2013 23:39   0h 42m  182,619.49 267,731,249   0.00000464 0.40116362   1,241   107,404,036 0.0000115545 2.1101
18943 10/23/2013 22:56   0h 42m  182,848.92 267,731,249   0.00000489 0.40166762   1,308   107,538,974 0.0000121630 2.2240
18942 10/23/2013 22:14   0h 41m  186,041.04 267,731,249   0.00000454 0.40382612   1,216   108,116,872 0.0000112471 2.0924
18941 10/23/2013 21:32   0h 41m  185,877.88 267,731,249   0.00000501 0.40347196   1,341   108,022,052 0.0000124141 2.3075
18940 10/23/2013 20:50   0h 41m  184,525.07 267,731,249   0.00000483 0.40181929   1,294   107,579,581 0.0000120283 2.2195
18939 10/23/2013 20:08   0h 41m  187,276.17 267,731,249   0.00000481 0.40145836   1,288   107,482,948 0.0000119833 2.2442
18938 10/23/2013 19:26   0h 42m  183,265.94 267,731,249   0.00000479 0.40433683   1,283   108,253,605 0.0000118518 2.1720
18937 10/23/2013 18:44   0h 42m  183,798.82 267,731,249   0.00000486 0.40343460   1,301   108,012,049 0.0000120450 2.2138
18936 10/23/2013 18:01   0h 42m  183,698.71 267,731,249   0.00000472 0.40401361   1,264   108,167,069 0.0000116856 2.1466
18935 10/23/2013 17:19   0h 42m  182,855.88 267,731,249   0.00000496 0.40311408   1,329   107,926,237 0.0000123140 2.2517
18934 10/23/2013 16:36   0h 42m  183,825.20 267,731,249   0.00000505 0.40397210   1,351   108,155,954 0.0000124912 2.2962
18933 10/23/2013 15:54   0h 43m  179,528.50 267,731,249   0.00000525 0.40374113   1,406   108,094,118 0.0000130072 2.3352
18932 10/23/2013 15:10   0h 43m  179,000.77 267,731,249   0.00000526 0.40379965   1,409   108,109,784 0.0000130330 2.3329
                                                                                                                   ------
                                                                                                                   2.2246

and according to cgminer:

Code:

Summary of runtime statistics:

 [2013-10-23 21:33:52] Started at [2013-10-23 04:42:38]
 [2013-10-23 21:33:52] Pool: stratum+tcp://mint.bitminter.com:3333
 [2013-10-23 21:33:52] Runtime: 16 hrs : 51 mins : 14 secs
 [2013-10-23 21:33:52] Average hashrate: 2231.9 Megahash/s
 [2013-10-23 21:33:52] Solved blocks: 0
 [2013-10-23 21:33:52] Best share difficulty: 29.9K
 [2013-10-23 21:33:52] Share submissions: 31528
 [2013-10-23 21:33:52] Accepted shares: 31296
 [2013-10-23 21:33:52] Rejected shares: 232
 [2013-10-23 21:33:52] Accepted difficulty shares: 31296
 [2013-10-23 21:33:52] Rejected difficulty shares: 232
 [2013-10-23 21:33:52] Reject ratio: 0.7%
 [2013-10-23 21:33:52] Hardware errors: 0
 [2013-10-23 21:33:52] Utility (accepted shares / min): 30.95/min
 [2013-10-23 21:33:52] Work Utility (diff1 shares solved / min): 31.18/min

 [2013-10-23 21:33:52] Stale submissions discarded due to new blocks: 0
 [2013-10-23 21:33:52] Unable to get work from server occasions: 0
 [2013-10-23 21:33:52] Work items generated locally: 51412
 [2013-10-23 21:33:52] Submitting work remotely delay occasions: 0
 [2013-10-23 21:33:52] New blocks detected on network: 160

 [2013-10-23 21:33:52] Summary of per device statistics:

 [2013-10-23 21:33:52] BITFURY0 (5s):3.107G (avg):2.231Gh/s | A:31296 R:232 HW:0 WU:31.2/m
 [2013-10-23 21:33:52]

I've restarted the exact same test and same device at 53 bits and will post the statistics in 10-12 hrs.

[vs3]

Here are the same stats running at 53 bits for about a day:

Code:

 No.     Completed     Duration Total Ghps  Difficulty  Your score  Total score Your work Total work     My %      My GH
18985  10/25/2013 3:44   0h 40m  192,559.21 267,731,249   0.00000456 0.40307092   1,220   107,914,681 0.0000113052 2.1769
18984  10/25/2013 3:03   0h 40m  191,228.66 267,731,249   0.00000446 0.40011946   1,193   107,124,483 0.0000111366 2.1296
18983  10/25/2013 2:23   0h 40m  190,384.85 267,731,249   0.00000446 0.40315534   1,194   107,937,284 0.0000110620 2.1060
18982  10/25/2013 1:42   0h 40m  188,139.84 267,731,249   0.00000436 0.40200088   1,166   107,628,198 0.0000108336 2.0382
18981  10/25/2013 1:01   0h 41m  186,461.62 267,731,249   0.00000479  0.4031175   1,282   107,927,152 0.0000118784 2.2149
18980  10/25/2013 0:19   0h 40m  189,475.87 267,731,249   0.00000441 0.40139529   1,180   107,466,063 0.0000109802 2.0805
18979 10/24/2013 23:38   0h 40m  190,490.06 267,731,249   0.00000467 0.40387512   1,250   108,129,990 0.0000115602 2.2021
18978 10/24/2013 22:57   0h 41m  186,994.80 267,731,249   0.00000452 0.40101782   1,211   107,365,003 0.0000112793 2.1092
18977 10/24/2013 22:16   0h 41m  188,263.32 267,731,249   0.00000484 0.40406566   1,296   108,181,003 0.0000119799 2.2554
18976 10/24/2013 21:34   0h 40m  187,644.43 267,731,249   0.00000452 0.40012641   1,209   107,126,343 0.0000112857 2.1177
18975 10/24/2013 20:53   0h 41m  188,295.79 267,731,249   0.00000436 0.40397159   1,167   108,155,818 0.0000107900 2.0317
18974 10/24/2013 20:12   0h 40m  188,937.12 267,731,249   0.00000454 0.40008967   1,216   107,116,507 0.0000113521 2.1448
18973 10/24/2013 19:31   0h 40m  190,594.11 267,731,249   0.00000458 0.40376422   1,226   108,100,299 0.0000113413 2.1616
18972 10/24/2013 18:50   0h 40m  188,682.02 267,731,249   0.00000449 0.40250302   1,202   107,762,636 0.0000111541 2.1046
18971 10/24/2013 18:09   0h 40m  189,075.18 267,731,249   0.00000437 0.40054645   1,170   107,238,802 0.0000109102 2.0629
18970 10/24/2013 17:28   0h 40m  191,763.14 267,731,249   0.00000453 0.40090427   1,212   107,334,600 0.0000112918 2.1653
18969 10/24/2013 16:47   0h 40m  189,429.14 267,731,249   0.00000467 0.40063734   1,251   107,263,135 0.0000116629 2.2093
18968 10/24/2013 16:06   0h 40m  189,140.87 267,731,249   0.00000461 0.40068561   1,233   107,276,058 0.0000114937 2.1739
18967 10/24/2013 15:25   0h 40m  187,813.82 267,731,249   0.00000462 0.40097759   1,236   107,354,232 0.0000115133 2.1624
18966 10/24/2013 14:44   0h 40m  190,044.65 267,731,249   0.00000458 0.40226968   1,225   107,700,164 0.0000113742 2.1616
                                                                                                                   ------
                                                                                                                   2.1404                                                                                                                  

Code:

Summary of runtime statistics:

 [2013-10-24 20:55:18] Started at [2013-10-23 21:34:17]
 [2013-10-24 20:55:18] Pool: stratum+tcp://mint.bitminter.com:3333
 [2013-10-24 20:55:18] Runtime: 23 hrs : 21 mins : 1 secs
 [2013-10-24 20:55:18] Average hashrate: 2150.4 Megahash/s
 [2013-10-24 20:55:18] Solved blocks: 0
 [2013-10-24 20:55:18] Best share difficulty: 33K
 [2013-10-24 20:55:18] Share submissions: 42056
 [2013-10-24 20:55:18] Accepted shares: 41721
 [2013-10-24 20:55:18] Rejected shares: 335
 [2013-10-24 20:55:18] Accepted difficulty shares: 41751
 [2013-10-24 20:55:18] Rejected difficulty shares: 335
 [2013-10-24 20:55:18] Reject ratio: 0.8%
 [2013-10-24 20:55:18] Hardware errors: 0
 [2013-10-24 20:55:18] Utility (accepted shares / min): 29.78/min
 [2013-10-24 20:55:18] Work Utility (diff1 shares solved / min): 30.04/min

 [2013-10-24 20:55:18] Stale submissions discarded due to new blocks: 0
 [2013-10-24 20:55:18] Unable to get work from server occasions: 0
 [2013-10-24 20:55:18] Work items generated locally: 67460
 [2013-10-24 20:55:18] Submitting work remotely delay occasions: 0
 [2013-10-24 20:55:18] New blocks detected on network: 215

 [2013-10-24 20:55:18] Summary of per device statistics:

 [2013-10-24 20:55:18] BITFURY0 (5s):2.447G (avg):2.150Gh/s | A:41751 R:335 HW:0 WU:30.0/m
 [2013-10-24 20:55:18]

Or in other words - the 1-bit difference was 2.224GH/s vs 2.14GH/s

[vs3]

And long live Luke-Jr and BFGMINER!!! :-)

two devices at 52 bits on one machine: (one is a bit overvoltaged - I think you can spot which one - the other is stock )

Code:

 bfgminer version 3.3.0 - Started: [2013-10-24 23:58:24] - [  0 days 00:24:49]
 [M]anage devices [P]ool management [S]ettings [D]isplay options  [H]elp [Q]uit
 Connected to stratum.bitcoin.cz diff 3 with stratum as user vs3.nanofury2
 Block: ...46f41298 #265919  Diff:268M ( 1.92Ph/s)  Started: [23:58:24]
 ST:2  F:0  NB:1  AS:0  BW:[ 53/ 42 B/s]  E:22.83  I:  361uBTC/hr  BS:940
 2            |  2.13/ 4.50/ 4.45Gh/s | A:533 R:0+0(none) HW:16/.45%
--------------------------------------------------------------------------------
 NFY 0:       |  2.22/ 2.24/ 2.19Gh/s | A:270 R:0+0(none) HW: 5/.52%
 NFY 1:       |  2.33/ 2.26/ 2.27Gh/s | A:263 R:0+0(none) HW:11/.38%
--------------------------------------------------------------------------------
 [2013-10-25 00:22:55] Accepted 1883610d NFY 0  Diff 10/3

and at 54 bits another one on another machine: (that's the slightly undervoltaged one)

Code:

 bfgminer version 3.3.0 - Started: [2013-10-24 22:49:51] - [  0 days 01:38:00]
 [M]anage devices [P]ool management [S]ettings [D]isplay options  [H]elp [Q]uit
 Connected to mint.bitminter.com diff 1 with stratum as user vs3_nanofury1
 Block: ...c330b15f #265920  Diff:268M ( 1.92Ph/s)  Started: [00:24:25]
 ST:2  F:0  NB:15  AS:0  BW:[ 60/ 67 B/s]  E:8.84  I:  185uBTC/hr  BS:2.35k
 1            |  2.43/ 2.43/ 2.37Gh/s | A:3152 R:9+0(.31%) HW:48/1.5%
--------------------------------------------------------------------------------
 NFY 0:       |  2.44/ 2.43/ 2.37Gh/s | A:3154 R:9+0(.31%) HW:48/1.5%
--------------------------------------------------------------------------------
 [2013-10-25 00:26:58] Accepted 304192a6 NFY 0  Diff 5/1
 [2013-10-25 00:26:59] Accepted 88ee8e60 NFY 0  Diff 1/1
 [2013-10-25 00:26:59] Accepted 58d55f6a NFY 0  Diff 2/1
 [2013-10-25 00:27:00] Accepted dfafe7fd NFY 0  Diff 1/1
 [2013-10-25 00:27:00] Accepted 060a55c0 NFY 0  Diff 42/1

I'll leave that one run overnight and post the average from bitminter tomorrow.

[erk]

How is the production coming along, any eta?

[vs3]

How is the production coming along, any eta?

When I spoke with Marto a few days ago he mentioned that he expects the first devices today or Monday.

[Taugeran]

How is the production coming along, any eta?

When I spoke with Marto a few days ago he mentioned that he expects the first devices today or Monday.

bomb diggity so by next friday they could be in the mail?

[Taugeran]

also just thought of a possible tui improvement:

Add the current osc6 bits to the display lines. like gpu show fan speed etc

--------------------------------------------------------------------------------
 NFY 0:       |  2.22/ 2.24/ 2.19Gh/s | A:270 R:0+0(none) HW: 5/.52%
 NFY 1:       |  2.33/ 2.26/ 2.27Gh/s | A:263 R:0+0(none) HW:11/.38%
--------------------------------------------------------------------------------

|
|
↓

--------------------------------------------------------------------------------
 NFY 0: 52   |  2.22/ 2.24/ 2.19Gh/s | A:270 R:0+0(none) HW: 5/.52%
 NFY 1: 52   |  2.33/ 2.26/ 2.27Gh/s | A:263 R:0+0(none) HW:11/.38%
--------------------------------------------------------------------------------

[vs3]

How is the production coming along, any eta?

When I spoke with Marto a few days ago he mentioned that he expects the first devices today or Monday.

bomb diggity so by next friday they could be in the mail?

Very likely. Presuming Marto gets everything on Monday (and manages to send us our box on Monday) we should have the devices by Thursday, which means that Friday we can be shipping. Even if the box arrives on Friday we can ship on Saturday.

We'll keep you guys updated.

[vs3]

also just thought of a possible tui improvement:

Add the current osc6 bits to the display lines. like gpu show fan speed etc

--------------------------------------------------------------------------------
 NFY 0:       |  2.22/ 2.24/ 2.19Gh/s | A:270 R:0+0(none) HW: 5/.52%
 NFY 1:       |  2.33/ 2.26/ 2.27Gh/s | A:263 R:0+0(none) HW:11/.38%
--------------------------------------------------------------------------------

|
|
↓

--------------------------------------------------------------------------------
 NFY 0: 52   |  2.22/ 2.24/ 2.19Gh/s | A:270 R:0+0(none) HW: 5/.52%
 NFY 1: 52   |  2.33/ 2.26/ 2.27Gh/s | A:263 R:0+0(none) HW:11/.38%
--------------------------------------------------------------------------------

Interesting idea ...

By the way - bfgminer will start by default with 50 bits - as that's the one that is safely within the USB2.0 specs.

Our observations show that everything would most likely work just fine even at 52-54 bits, but since that would be pushing the boundaries you can do your own experiments and find out how much could your PC or hub tolerate. Hence the command-line parameter with the bits.

Keep in mind that the command-line parameter will set the default bits for all Bitfury chips. After you start bfgminer you can go to the device management and change the bits for each individual device - that way if you have devices or ports that tolerate a bit more you can set a different speed for just those individual devices. You can even set a different speed for every single one.

Another observation - it appears that bfgminer is able to squeeze out a few extra gigahashes than cgminer

Below is the same stats from bitminter of the device I've been testing for the last few days - running at 54 bits:

Code:

 No.    Completed      Duration    Total Ghps    Difficulty      Your score    Total score   Your work   Total work      My %      My GH
19023 10/26/2013 5:11     0h 56m     198,763.04    390,928,787      0.00000482    0.40107124      1,885   156,790,293 0.0000120224 2.3896
19022 10/26/2013 4:14     0h 56m     198,062.58    390,928,787      0.00000489    0.40119134      1,912   156,837,243 0.0000121910 2.4146
19021 10/26/2013 3:17     0h 55m     199,040.56    390,928,787      0.00000489    0.40010072      1,886   154,460,358 0.0000122103 2.4303
19020 10/26/2013 2:21     0h 38m     199,221.31    267,731,249      0.00000476    0.40125034      1,274   107,427,255 0.0000118592 2.3626
19019 10/26/2013 1:42     0h 38m     199,667.36    267,731,249      0.00000492     0.4028433      1,316   107,853,739 0.0000122017 2.4363
19018 10/26/2013 1:03     0h 39m     197,912.16    267,731,249      0.00000485    0.40480966      1,299   108,380,195 0.0000119856 2.3721
19017 10/26/2013 0:24     0h 38m     198,882.46    267,731,249      0.00000479    0.40074082      1,283   107,290,841 0.0000119582 2.3783
1901610/25/2013 23:45     0h 39m     197,049.78    267,731,249      0.00000477    0.40218894      1,277   107,678,548 0.0000118594 2.3369
1901510/25/2013 23:05     0h 38m     201,886.68    267,731,249      0.00000465    0.40468739      1,245   108,347,460 0.0000114908 2.3198
1901410/25/2013 22:27     0h 38m     196,948.57    267,731,249      0.00000459     0.4002696      1,229   107,164,680 0.0000114683 2.2587
1901310/25/2013 21:47     0h 38m     201,282.27    267,731,249      0.00000468    0.40032505      1,253   107,179,526 0.0000116907 2.3531
1901210/25/2013 21:09     0h 38m     198,070.43    267,731,249      0.00000507    0.40065487      1,357   107,267,829 0.0000126506 2.5057
1901110/25/2013 20:30     0h 38m     200,747.95    267,731,249      0.00000489    0.40153187      1,308   107,502,630 0.0000121671 2.4425
1901010/25/2013 19:51     0h 38m     199,415.63    267,731,249      0.00000492     0.4014683      1,316   107,485,609 0.0000122435 2.4415
1900910/25/2013 19:12     0h 39m     198,747.57    267,731,249      0.00000469    0.40513568      1,255   108,467,483 0.0000115703 2.2996
1900810/25/2013 18:33     0h 39m     195,373.80    267,731,249      0.00000492    0.40080704      1,316   107,308,570 0.0000122637 2.3960
1900710/25/2013 17:53     0h 39m     195,515.88    267,731,249      0.00000493    0.40109851      1,320   107,386,605 0.0000122920 2.4033
1900610/25/2013 17:14     0h 39m     195,703.41    267,731,249      0.00000496     0.4043765      1,328   108,264,226 0.0000122663 2.4006
1900510/25/2013 16:34     0h 39m     195,852.02    267,731,249      0.00000487    0.40298034      1,304   107,890,430 0.0000120863 2.3671
1900410/25/2013 15:54     0h 39m     193,534.11    267,731,249      0.00000502    0.40023075      1,345   107,154,279 0.0000125520 2.4292
                                                                                                                                   2.3869

[Luke-Jr]

Note that some USB hosts/hubs may "work" at above-spec currents yet destroy the port over time!

The official BFGMiner 5.4 release will be using a new option to set the bits: --set-device osc6_bits=54
This also allows you to set it just for nanofurys: --set-device NFY:osc6_bits=54

[vs3]

And let's start the week with some good news:

Hi all,
today the first batch of NanoFury came out of trough hole assembly
here are some photos of the very first board of the production run.


We are working on heat sink now. To be ready until tomorrow morning then start shipping

I guess this is the one everyone has been waiting for

(that's a bigger version of the same image as in Marto's post)

[bigbeninlondon]

Woo! 

I'm really excited to have participated in this.

[TheQuin]

And let's start the week with some good news:

Hi all,
today the first batch of NanoFury came out of trough hole assembly
here are some photos of the very first board of the production run.


We are working on heat sink now. To be ready until tomorrow morning then start shipping

I guess this is the one everyone has been waiting for

(that's a bigger version of the same image as in Marto's post)

You should have called it "Green Fury" 

[Taugeran]

And let's start the week with some good news:

Hi all,
today the first batch of NanoFury came out of trough hole assembly
here are some photos of the very first board of the production run.


We are working on heat sink now. To be ready until tomorrow morning then start shipping

I guess this is the one everyone has been waiting for

(that's a bigger version of the same image as in Marto's post)

ive noticed all the EU bit fury chips have Bio....... on them but the US ones have ß on them just different packaging marks?

[vs3]

I've noticed all the EU bit fury chips have Bio....... on them but the US ones have ß on them just different packaging marks?

Yeah, I remember asking that question before (but I'm too tired to search for it right now to quote it )

In essence - the ones with the ß symbol were from the first packaging batch, and the ones with the BioInfoBank were from the subsequent packaging. Both chips are from the same silicon dies, so the silicon part in them is identical. I think I someone mentioned that the marking is such because BioInfoBank was the entity that actually paid the bill. Which doesn't really matter for us - as long as the chips work fine I could care less what does it say on the packaging.

[vs3]

Just to update everyone - as I bet you're as eager to get those in your hands as I am - and it is a mix of good and could've-been-better news, so here we go:

Marto74 got the boards on Monday and that's when we got the first glimpse at the finished units.

Even though we had said initially that there will be no heatsink after some testing we figured it would really be much better if the units did indeed have a heatsink. We know they can get 2.2-2.4GH easily and it would be just a pity to artificially limit them. That way they would be much more stable and reliable too.
So Marto ordered the heatsinks on Tuesday morning with the promise that they'll arrive on Wednesday ... which they did - at 8pm (instead of the promised noon). As a result of that a bit late delivery he couldn't meet the Wednesday shipping deadline and sent our package first thing on Thursday morning, but unfortunately my plans for shipping over the weekend won't work as the box will arrive here on Monday - according to UPS : "Scheduled Delivery: Monday, 11/04/2013, By End of Day"

So barring anything else unexpected we expect to be shipping everything on Tuesday or Wednesday.


I know I wanted to have my devices as soon as possible, and this unexpected extra 2-3 day delay is annoying... so at the very least I just wanted to keep everyone updated on where we are.

At least we got some really nice copper heatsinks:

[Taugeran]

Just to update everyone - as I bet you're as eager to get those in your hands as I am - and it is a mix of good and could've-been-better news, so here we go:

Marto74 got the boards on Monday and that's when we got the first glimpse at the finished units.

Even though we had said initially that there will be no heatsink after some testing we figured it would really be much better if the units did indeed have a heatsink. We know they can get 2.2-2.4GH easily and it would be just a pity to artificially limit them. That way they would be much more stable and reliable too.
So Marto ordered the heatsinks on Tuesday morning with the promise that they'll arrive on Wednesday ... which they did - at 8pm (instead of the promised noon). As a result of that a bit late delivery he couldn't meet the Wednesday shipping deadline and sent our package first thing on Thursday morning, but unfortunately my plans for shipping over the weekend won't work as the box will arrive here on Monday - according to UPS : "Scheduled Delivery: Monday, 11/04/2013, By End of Day"

So barring anything else unexpected we expect to be shipping everything on Tuesday or Wednesday.


I know I wanted to have my devices as soon as possible, and this unexpected extra 2-3 day delay is annoying... so at the very least I just wanted to keep everyone updated on where we are.

At least we got some really nice copper heatsinks:

moar shinies!!!

[prehistoric]

I know I wanted to have my devices as soon as possible, and this unexpected extra 2-3 day delay is annoying... so at the very least I just wanted to keep everyone updated on where we are.

At least we got some really nice copper heatsinks: https://i.imgur.com/nKveYU1s.jpg

They are quite nice!
No problem with the delay, please test nanoFurys before shipping.

[vs3]

I know I wanted to have my devices as soon as possible, and this unexpected extra 2-3 day delay is annoying... so at the very least I just wanted to keep everyone updated on where we are.

At least we got some really nice copper heatsinks:

They are quite nice!
No problem with the delay, please test nanoFurys before shipping.

Yep - we'll certainly double check and test each device.

[erk]

Don't stick the heatsink on if it's self adhesive, as each rig may have a different orientation of the sticks, so the fins need to be aligned for it.

[vs3]

Don't stick the heatsink on if it's self adhesive, as each rig may have a different orientation of the sticks, so the fins need to be aligned for it.

I think we might be a bit late with that.. I'll find out tomorrow if the heatsinks have all been installed or not. If they're not yet put I'll ship them that way, but if they're already installed I'm not going to take them off.

Generally speaking the fins can either be horizontally (as shown on the picture) or vertically (turned 90 degrees). The horizontal ones will almost always be a better option and even more if you have any additional cooling (e.g. a fan). The vertical ones might be a bit better for passive cooling and if the devices are put vertically.

Oh well, we'll find out soon.

[vs3]

Those were the 3 longest hours ... of unwrapping



So now next is testing.


Also - we got 3 devices with a black heatsink (due to some defective copper ones that had to be replaced).

If anyone has a preference and wants those - please post on the thread. The first to post will get them.

[Swimmer63]

Anxious for test results and delivery.

[bigbeninlondon]

Would love 1 with black.

[Taugeran]

Those were the 3 longest hours ... of unwrapping



So now next is testing.


Also - we got 3 devices with a black heatsink (due to some defective copper ones that had to be replaced).

If anyone has a preference and wants those - please post on the thread. The first to post will get them.

sooooo shiny!!!

[Swimmer63]

Got a message mine arrive today (Wednesday).
Is there a setup or support thread for these?
I need install instructions for win7.

[vs3]

Update: All devices have been shipped.

Sample usage instructions:

Get the latest BFGMINER - e.g. from this link: http://luke.dashjr.org/tmp/code/webisect/webisect.php?dobuild=bfgminer

I did my tests with this version:
http://luke.dashjr.org/tmp/code/webisect/wr/6e770d6c7c3ffbca03c4a1eaf25cfafc77542fc4-win32.zip
http://luke.dashjr.org/tmp/code/webisect/wr/6e770d6c7c3ffbca03c4a1eaf25cfafc77542fc4-win64.zip
 
sample command line:
bfgminer.exe -o stratum+tcp://mint.bitminter.com:3333 -u vs3_nanofury1 -p nanofury1 -G -S all --set-device NFY:osc6_bits=52
 
The last parameter overwrites the speed bits. A note of caution - the "safe" speed is around 50 bits, so anything over that will likely use more power than what the USB2.0 specs permit. No two chips are the same, so the upper limit will probably be different for each device. On my devices it was around 52-54.
Two things have been happening with my devices when I go over the limit - 1) when they overheat hashrate drops significantly - like 0.3-0.5GH, and 2) if the hub can't provide enough power (and voltage drops below 3.6-3.8V) that just ruins the USB communication and the device appears to have disconnect - beware that the bitfury chip will still have enough power (it needs 1V) and will continue to work even though the PC doesn't "see" the device, so you'll need to unplug it and plug it back in.

Please be careful when handling them - THEY WILL BE HOT!!! and especially even more if you push them. DO NOT TOUCH THE HEATSINKS when they work - heatsinks may reach over 80C!


I wish to thank again everyone for your trust in me with this group-buy and I'm hoping you'll like your devices!

HAPPY HASHING! :-)

[whiteEAGLE]

Is it possible to run this units overclocked on a powered USB3.0 hub connected to a USB 2.0 port on the PC?

Will they get 500 mA or 900 mA?

[erk]

Good work vs3 you beat most of the other group projects of late, obviously a person that understands BTC diff increases.


heatsinks may reach over 80C probably means to many bits. Did you use a cooling fan?

[bigbeninlondon]

Is there tracking information?

[whiteEAGLE]

Update: All devices have been shipped.

Sample usage instructions:


sample command line:
bfgminer.exe -o stratum+tcp://mint.bitminter.com:3333 -u vs3_nanofury1 -p nanofury1 -G -S all --set-device NFY:osc6_bits=52
 

Can i write this part into the config file?
what is the correct form for this?

[vs3]

on the various questions:

>Will they get 500 mA or 900 mA?
At 50 bits they should be using around 500mA. At 53 it's around 650-700mA but each device is a bit different. USB3 will provide sufficient power for such overclocking.

>heatsinks may reach over 80C probably means to many bits. Did you use a cooling fan?
I did not use any fan - just passive cooling (e.g. the heatsink). A fan will certainly help

>Is there tracking information?
On the domestic packages - yes. It should've been included in the email sent yesterday. If you're missing it send an email to the nf1order@ one and we'll take a look.

>sample command line:
>bfgminer.exe -o stratum+tcp://mint.bitminter.com:3333 -u vs3_nanofury1 -p nanofury1 -G -S all --set-device NFY:osc6_bits=52
>Can i write this part into the config file?
I have no idea to be honest
Check bfgminer documentation and if you don't find the answer post on Luke-jr's support thread and he or someone else there might be able to answer that.

[Swimmer63]

Do any special drivers need to be installed?

[vs3]

Do any special drivers need to be installed?

Nope. Windows should recognize it as a standard HID device (and use its built-in drivers).

[Luke-Jr]

Get the latest BFGMINER - e.g. from this link: http://luke.dashjr.org/tmp/code/webisect/webisect.php?dobuild=bfgminer

3.5.0 should work fine, no need for bleeding edge anymore

bfgminer.exe -o stratum+tcp://mint.bitminter.com:3333 -u vs3_nanofury1 -p nanofury1 -G -S all --set-device NFY:osc6_bits=52

Can i write this part into the config file?
what is the correct form for this?

...
"set-device":["NFY:osc6_bits=52"],
...

[Swimmer63]

Get the latest BFGMINER - e.g. from this link: http://luke.dashjr.org/tmp/code/webisect/webisect.php?dobuild=bfgminer

3.5.0 should work fine, no need for bleeding edge anymore

bfgminer.exe -o stratum+tcp://mint.bitminter.com:3333 -u vs3_nanofury1 -p nanofury1 -G -S all --set-device NFY:osc6_bits=52

Can i write this part into the config file?
what is the correct form for this?

...
"set-device":["NFY:osc6_bits=52"],
...

When I add this in as it's typed bfg shuts down.  If I leave it off they work.  I have 8 hashing at about 2.0 and one at 1.62.

[bigbeninlondon]

Get the latest BFGMINER - e.g. from this link: http://luke.dashjr.org/tmp/code/webisect/webisect.php?dobuild=bfgminer

3.5.0 should work fine, no need for bleeding edge anymore

bfgminer.exe -o stratum+tcp://mint.bitminter.com:3333 -u vs3_nanofury1 -p nanofury1 -G -S all --set-device NFY:osc6_bits=52

Can i write this part into the config file?
what is the correct form for this?

...
"set-device":["NFY:osc6_bits=52"],
...

When I add this in as it's typed bfg shuts down.  If I leave it off they work.  I have 8 hashing at about 2.0 and one at 1.62.

Watch your commas.  If you put that at the end of your config file, the comma at the end is unnecessary. 

[fractalbc]

Watch your commas.  If you put that at the end of your config file, the comma at the end is unnecessary. 

jsonlint ( http://jsonlint.com/ ) is everyones friend.  Always check your config file (cut and paste to the form) after making manual changes to avoid "oops"es.

[erk]

Could someone do a table at the various different bit settings, of the GH/s vs power consumption please?

I am looking for the efficiency sweet spot to run the NF1 at, not just the max.

[Swimmer63]

Get the latest BFGMINER - e.g. from this link: http://luke.dashjr.org/tmp/code/webisect/webisect.php?dobuild=bfgminer

3.5.0 should work fine, no need for bleeding edge anymore

bfgminer.exe -o stratum+tcp://mint.bitminter.com:3333 -u vs3_nanofury1 -p nanofury1 -G -S all --set-device NFY:osc6_bits=52

Can i write this part into the config file?
what is the correct form for this?

...
"set-device":["NFY:osc6_bits=52"],
...

When I add this in as it's typed bfg shuts down.  If I leave it off they work.  I have 8 hashing at about 2.0 and one at 1.62.

Watch your commas.  If you put that at the end of your config file, the comma at the end is unnecessary. 

What about the quote marks?  I copied this into jsonlint and got back:
Parse error on line 1:
bfgminer.exe-ostratu
^
Expecting '{', '['

[Swimmer63]

Very steady at stock bits.  Much better quality control than the Blue Furys which all over the place.  Although the average for them is about 2.2 Gh/s.
Still trying to figure out the code to increase the bits.

[bigbeninlondon]

Get the latest BFGMINER - e.g. from this link: http://luke.dashjr.org/tmp/code/webisect/webisect.php?dobuild=bfgminer

3.5.0 should work fine, no need for bleeding edge anymore

bfgminer.exe -o stratum+tcp://mint.bitminter.com:3333 -u vs3_nanofury1 -p nanofury1 -G -S all --set-device NFY:osc6_bits=52

Can i write this part into the config file?
what is the correct form for this?

...
"set-device":["NFY:osc6_bits=52"],
...

When I add this in as it's typed bfg shuts down.  If I leave it off they work.  I have 8 hashing at about 2.0 and one at 1.62.

Watch your commas.  If you put that at the end of your config file, the comma at the end is unnecessary.  

What about the quote marks?  I copied this into jsonlint and got back:
Parse error on line 1:
bfgminer.exe-ostratu
^
Expecting '{', '['

That shouldn't be part of your JSON config file.  That is the command line executable.  You need to add only the part that Luke-Jr stated to your config file:

"set-device":["NFY:osc6_bits=52"],

Edit: If you want to use jsonlint, you need to copy your entire config file into the edit box to see if your config file is right.

[Swimmer63]

I did.  4 times.

[Taugeran]

I did.  4 times.

.conf file or ur .bat file?

[Swimmer63]

Ahhhhh......  .bat
Needs to be in .conf huh?
Kind of like instructions I suppose.
Thx

[Swimmer63]

Thanks for your patience with me.  I did figure that out.

I used to run BE's on this machine and decided to clean up all the unused Com Ports and USB hubs listed in the Device Mgr.
I was hoping to be able to get more than 13 Nano's to run.  I have 20 right now.
But now Bfgminer won't start.  It locks up.  I think it has something to do with the fact that despite reinstalling all the Nano's I don't have any COM ports listed in the Device Mgr.  They are just gone.  Not even a heading that says "Ports"
Any idea how I get that back?

[vs3]

Nanos don't use COM ports - they should show up under the HID (Human Interface Device) devices section.

I'm not sure how you deleted those COM ports - I guess it is possible that this may have messed up Windows' configuration...
Take a look at this link and see if that makes any difference: https://bitcointalk.org/index.php?topic=300638

Also - try it first with just one device, then add some more, and then even more. Also, try different USB ports.
That way you can find out if you're hitting any kind of limitation (software or hardware)

[whiteEAGLE]

Is someone runnig nanofurys on minepeon?

i'm running 2 of them on windows, but i'd like to add them to my BE on minepeon....

how can i manage that?

[Taugeran]

i can't get bfgminer to pickup on the .so files for libhidapi on raspian wheezy


from ~/

Code:

git clone https://github.com/signal11/hidapi && git clone https://github.com/luke-jr/bfgminer

cd hidapi
./bootstrap
./configure
make -j2
make install

cd ../bfgminer
./autogen.sh
CFLAGS="-ggdb -O0" ./configure --disable-opencl --enable-bitfury --enable-icarus --enable-bigpic --enable-nanofury
make -j2


sudo ./bfgminer -D -T -S NFY:all

output:

Code:

miner@raspberrypi ~/repos/bfgminer $ sudo ./bfgminer -D -T -S NFY:all
 [2013-11-07 19:42:09] Timers: Using clock_gettime(CLOCK_MONOTONIC_RAW)                    
 [2013-11-07 19:42:09] Global quota greatest common denominator set to 1                    
 [2013-11-07 19:42:09] setrlimit: Soft fd limit not being changed from 1024 (FD_SETSIZE=1024; hard limit=4096)                    
 [2013-11-07 19:42:09] Started bfgminer 3.5.1                    
 [2013-11-07 19:42:09] Loaded configuration file /root/.cgminer/cgminer.conf                    
 [2013-11-07 19:42:09] hidapi_try_lib: Couldn't load libhidapi.so: libhidapi.so: cannot open shared object file: No such file or directory                    
 [2013-11-07 19:42:09] hidapi_try_lib: Couldn't load libhidapi-0.so: libhidapi-0.so: cannot open shared object file: No such file or directory                    
 [2013-11-07 19:42:09] hidapi_try_lib: Couldn't load libhidapi-hidraw.so: libhidapi-hidraw.so: cannot open shared object file: No such file or directory                    
 [2013-11-07 19:42:09] hidapi_try_lib: Couldn't load libhidapi-libusb.so: libhidapi-libusb.so: cannot open shared object file: No such file or directory                    
 [2013-11-07 19:42:09] hid_devinfo_scan: Failed to load any hidapi library                    
 [2013-11-07 19:42:09] lowlevel_scan: Found usb device at usb:001:009 (path=(null), vid=0835, pid=8500, manuf=Action Star, prod=USB2.0 Hub, serial=(null))                    
 [2013-11-07 19:42:09] lowlevel_scan: Found usb device at usb:001:023 (path=(null), vid=04d8, pid=00de, manuf=Microchip Technology Inc., prod=NanoFury NF1 v0.6, serial=0000072328)                    
 [2013-11-07 19:42:09] lowlevel_scan: Found usb device at usb:001:024 (path=(null), vid=04d8, pid=00de, manuf=Microchip Technology Inc., prod=NanoFury NF1 v0.6, serial=0000072543)                    
 [2013-11-07 19:42:09] lowlevel_scan: Found usb device at usb:001:005 (path=(null), vid=0835, pid=8501, manuf=Action Star, prod=USB HID, serial=(null))                    
 [2013-11-07 19:42:09] lowlevel_scan: Found usb device at usb:001:004 (path=(null), vid=0835, pid=8500, manuf=Action Star, prod=USB2.0 Hub, serial=(null))                    
 [2013-11-07 19:42:09] lowlevel_scan: Found usb device at usb:001:003 (path=(null), vid=0424, pid=ec00, manuf=(null), prod=(null), serial=(null))                    
 [2013-11-07 19:42:09] lowlevel_scan: Found usb device at usb:001:010 (path=(null), vid=0835, pid=8502, manuf=Action Star, prod=USB HID, serial=(null))                    
 [2013-11-07 19:42:09] lowlevel_scan: Found usb device at usb:001:001 (path=(null), vid=1d6b, pid=0002, manuf=Linux 3.6.11+ dwc_otg_hcd, prod=DWC OTG Controller, serial=bcm2708_usb)                    
 [2013-11-07 19:42:09] lowlevel_scan: Found usb device at usb:001:002 (path=(null), vid=0424, pid=9512, manuf=(null), prod=(null), serial=(null))                    
 [2013-11-07 19:42:09] DISPLAY not set, setting :0 just in case                    
 [2013-11-07 19:42:09] Failed to load OpenCL library, no GPUs usable                    
All devices disabled, cannot mine!

cross posted in bfgminer dev thread

[Luke-Jr]

i can't get bfgminer to pickup on the .so files for libhidapi on raspian wheezy

For some reason, ld.so isn't looking in /usr/local/lib

Edit: Nevermind, looks like I forgot to run ldconfig myself!

[bigbeninlondon]

Woot!  Up and running.  Thanks vs3 et al!  Will definitely buy from again!

One quick question.  I highlighted a bunch of statistics.  Anywhere I can get a rundown of those?  I've never thought to ask, but figure someone on here could point me in the right direction so I can read some of these interesting numbers.

Thanks again!
Ben

[Taugeran]

have arrived and are trying to figure out how to 1.) function properly on a pi
                                                                      2.) play nice with with 1 BF1 and 4 erupters :S

[Taugeran]

no pi for now running on windows   

[Luke-Jr]

One quick question.  I highlighted a bunch of statistics.  Anywhere I can get a rundown of those?  I've never thought to ask, but figure someone on here could point me in the right direction so I can read some of these interesting numbers.

README file

[vs3]

Woot!  Up and running.  Thanks vs3 et al!  Will definitely buy from again!

One quick question.  I highlighted a bunch of statistics.  Anywhere I can get a rundown of those?

Thanks for the feedback! That's all great news!

As for your question - see the README: https://github.com/luke-jr/bfgminer
search for "The BFGMiner status line shows:"

[RicRock]

i can't get bfgminer to pickup on the .so files for libhidapi on raspian wheezy

To get rid of that error I ran ldconfig as Luke implied.
I really do appreciate Luke-Jr's efforts, he always seems to jump to the aid of the community.

I still can't get mine running tho.

[bigbeninlondon]

Well I'll be damned, the readme file actually has pertinent information.   Gracias.

[Taugeran]

update after 11 hrs at 54 bits. still playing nice with others ^_^ and to boot bfg 3.5.1 is getting an extra 0.1ghs out of my BF1



can i buy more?

[baros008]

5 NanoFuries with 54 bits in Anker USB 3.0 48W hub, active cooling

[RicRock]

update after 11 hrs at 54 bits. still playing nice with others ^_^ and to boot bfg 3.5.1 is getting an extra 0.1ghs out of my BF1



can i buy more?

I'd talk about selling you mine.

I didn't realize they were going to be a windows thing.

[vs3]

I didn't realize they were going to be a windows thing.

not quite - you can run them everywhere where you can run bfgminer

[Taugeran]

I didn't realize they were going to be a windows thing.

not quite - you can run them everywhere where you can run bfgminer

yea only reason I'm posting from windows is i was getting timeouts etc on my rpi. its about time to reformat the lil thing and start from a fresh image. that thing has been used for all kinds of shit

[RicRock]

I didn't realize they were going to be a windows thing.

not quite - you can run them everywhere where you can run bfgminer

I don't believe that is true

Please give detailed instructions then.

I am unable to get them to run on bfg 3.5.1 and wheezy

[Taugeran]

I didn't realize they were going to be a windows thing.

not quite - you can run them everywhere where you can run bfgminer

I don't believe that is true

Please give detailed instructions then.

I am unable to get them to run on bfg 3.5.1 and wheezy

will work on it in a few days. i moved to windows because of lockups/freezes in bfg on wheezy due to not being able to initialize/ MCP2210_SPI_Transfer temp. rejected (XX bytes remaining)

[RicRock]

will work on it in a few days. i moved to windows because of lockups/freezes in bfg on wheezy due to not being able to initialize/ MCP2210_SPI_Transfer temp. rejected (XX bytes remaining)

I appreciate your efforts but I'll reiterate, since it appears to be a windows only device, I'm willing to accept offers to purchase my devices.

[Luke-Jr]

will work on it in a few days. i moved to windows because of lockups/freezes in bfg on wheezy due to not being able to initialize/ MCP2210_SPI_Transfer temp. rejected (XX bytes remaining)

I appreciate your efforts but I'll reiterate, since it appears to be a windows only device, I'm willing to accept offers to purchase my devices.

You're free to sell your devices or whatever, but you don't need to troll with FUD like "windows only".
There is nothing Windows-only about the NanoFury. I don't even use Windows.

[RicRock]

will work on it in a few days. i moved to windows because of lockups/freezes in bfg on wheezy due to not being able to initialize/ MCP2210_SPI_Transfer temp. rejected (XX bytes remaining)

I appreciate your efforts but I'll reiterate, since it appears to be a windows only device, I'm willing to accept offers to purchase my devices.

You're free to sell your devices or whatever, but you don't need to troll with FUD like "windows only".
There is nothing Windows-only about the NanoFury. I don't even use Windows.

My apologies, not sure what FUD is but only stated that to make sure anyone who wishes to buy it knows it appears to work best on windows.

Our at least I've only seen threads of success on windows.

[Luke-Jr]

will work on it in a few days. i moved to windows because of lockups/freezes in bfg on wheezy due to not being able to initialize/ MCP2210_SPI_Transfer temp. rejected (XX bytes remaining)

I appreciate your efforts but I'll reiterate, since it appears to be a windows only device, I'm willing to accept offers to purchase my devices.

You're free to sell your devices or whatever, but you don't need to troll with FUD like "windows only".
There is nothing Windows-only about the NanoFury. I don't even use Windows.

My apologies, not sure what FUD is but only stated that to make sure anyone who wishes to buy it knows it appears to work best on windows.

Our at least I've only seen threads of success on windows.

https://bitcointalk.org/index.php?topic=291456.msg3352995#msg3352995

[RicRock]

will work on it in a few days. i moved to windows because of lockups/freezes in bfg on wheezy due to not being able to initialize/ MCP2210_SPI_Transfer temp. rejected (XX bytes remaining)

I appreciate your efforts but I'll reiterate, since it appears to be a windows only device, I'm willing to accept offers to purchase my devices.

You're free to sell your devices or whatever, but you don't need to troll with FUD like "windows only".
There is nothing Windows-only about the NanoFury. I don't even use Windows.

My apologies, not sure what FUD is but only stated that to make sure anyone who wishes to buy it knows it appears to work best on windows.

Our at least I've only seen threads of success on windows.

https://bitcointalk.org/index.php?topic=291456.msg3352995#msg3352995

Point taken.

But I meant normal linux guys like me, not programers who can bend the source code to their will.

Again, It wasn't my intent to be offensive. What does FUD mean? I've always wondered.

[RicRock]

Got 2 nanofuries mining away overclocked to 53 osc6-bits on my USB 3 hub. Stable for 5½ hours so far.

Could you share your command line please?

[vs3]

Got 2 nanofuries mining away overclocked to 53 osc6-bits on my USB 3 hub. Stable for 5½ hours so far.

Could you share your command line please?

This is how I'm running mine:

Sample usage instructions:

sample command line:
bfgminer.exe -o stratum+tcp://mint.bitminter.com:3333 -u vs3_nanofury1 -p nanofury1 -G -S all --set-device NFY:osc6_bits=52

Although I'm running that under Windows (as you can tell by the .exe) the command line would be the same for all operating systems.

[RicRock]

I'm running that under Windows (as you can tell by the .exe) the command line would be the same for all operating systems.

Thanks, I wanted to replicate exactly Luke's running on 3.3.0 since I'm unable to get them detected using that version either.

He's not running on a Pi tho, so maybe that is the true difference?

[Luke-Jr]

Thanks, I wanted to replicate exactly Luke's running on 3.3.0 since I'm unable to get them detected using that version either.

Code:

{
    "scan-serial":["nanofury:0000062320","nanofury:0000062135"],
    "set-device":"NFY:osc6_bits=53"
}

You shouldn't need anything special though.
My first line is necessary because mine haven't had their USB strings programmed.
The second increases osc6_bits to use more power since it's on a USB 3 hub.

He's not running on a Pi tho, so maybe that is the true difference?

Could be... I may have to dig out my pi to test this.

[RicRock]

Could be... I may have to dig out my pi to test this.

I re-upgraded to 3.5.1 and output below:

Code:

pi@raspberrypi ~/clones/bfgminer $ sudo bfgminer -c /usr/local/etc/miner.conf -S NFY:all -D -d?
 [2013-11-09 23:43:50] setrlimit: Soft fd limit not being changed from 1024 (FD_SETSIZE=1024; hard limit=4096)                    
 [2013-11-09 23:43:50] Started bfgminer 3.5.1                    
 [2013-11-09 23:43:50] Loaded configuration file /usr/local/etc/miner.conf                    
 [2013-11-09 23:43:50] hidapi_try_lib: Couldn't load libhidapi.so: libhidapi.so: cannot open shared object file: No such file or directory                    
 [2013-11-09 23:43:50] hidapi_try_lib: Couldn't load libhidapi-0.so: libhidapi-0.so: cannot open shared object file: No such file or directory                    
 [2013-11-09 23:43:50] hidapi_try_lib: Successfully loaded libhidapi-hidraw.so                    
 [2013-11-09 23:43:50] hid_devinfo_scan: Found "NanoFury NF1 v0.6" serial "0000068980"                    
 [2013-11-09 23:43:50] hid_devinfo_scan: Found "NanoFury NF1 v0.6" serial "0000068550"                    
 [2013-11-09 23:43:51] lowlevel_scan: Found hid device at hid:/dev/hidraw0 (path=/dev/hidraw0, vid=04d8, pid=00de, manuf=Microchip Technology Inc., prod=NanoFury NF1 v0.6, serial=0000068550)                    
 [2013-11-09 23:43:51] lowlevel_scan: Found hid device at hid:/dev/hidraw1 (path=/dev/hidraw1, vid=04d8, pid=00de, manuf=Microchip Technology Inc., prod=NanoFury NF1 v0.6, serial=0000068980)                    
 [2013-11-09 23:43:51] lowlevel_scan: Found mcp2210 device at hid:/dev/hidraw1 (path=/dev/hidraw1, vid=04d8, pid=00de, manuf=Microchip Technology Inc., prod=NanoFury NF1 v0.6, serial=0000068980)                    
 [2013-11-09 23:43:51] lowlevel_scan: Found mcp2210 device at hid:/dev/hidraw0 (path=/dev/hidraw0, vid=04d8, pid=00de, manuf=Microchip Technology Inc., prod=NanoFury NF1 v0.6, serial=0000068550)                    
 [2013-11-09 23:43:51] mcp2210_set_cfg_spi: Error setting current SPI config (248)                    
 [2013-11-09 23:43:51] nanofury_foundlowl: Matched "NanoFury NF1 v0.6" serial "0000068980", but failed to detect nanofury                    
 [2013-11-09 23:43:51] mcp2210_set_cfg_spi: Error setting current SPI config (248)                    
 [2013-11-09 23:43:51] nanofury_foundlowl: Matched "NanoFury NF1 v0.6" serial "0000068550", but failed to detect nanofury                    
 [2013-11-09 23:43:51] Devices detected:                    
0 devices listed

Like I stated in a different thread.

/dev/hidraw* are present but are created with 600 root:root and no t sticky bit.

I've manually changed those with no difference in the results.

[RicRock]

Not sure if this would be helpful:

Code:

pi@raspberrypi ~/clones/hidapi/hidtest $ sudo ./hidtest-hidraw
Device Found
  type: 04d8 00de
  path: /dev/hidraw1
  serial_number: 0000068980
  Manufacturer: Microchip Technology Inc.
  Product:      NanoFury NF1 v0.6
  Release:      2
  Interface:    0

Device Found
  type: 04d8 00de
  path: /dev/hidraw0
  serial_number: 0000068550
  Manufacturer: Microchip Technology Inc.
  Product:      NanoFury NF1 v0.6
  Release:      2
  Interface:    0

unable to open device

[Luke-Jr]

The 248 suggests it was in the middle of a SPI transfer at some point.
Have you tried power cycling the NF?

[RicRock]

After power cycle I get this:

Code:

pi@raspberrypi ~/clones/bfgminer $ sudo bfgminer -c /usr/local/etc/miner.conf -D -d? -S nanofury:all
 [2013-11-10 00:22:30] setrlimit: Soft fd limit not being changed from 1024 (FD_SETSIZE=1024; hard limit=4096)                    
 [2013-11-10 00:22:30] Started bfgminer 3.5.1                    
 [2013-11-10 00:22:30] Loaded configuration file /usr/local/etc/miner.conf                    
 [2013-11-10 00:22:30] hidapi_try_lib: Couldn't load libhidapi.so: libhidapi.so: cannot open shared object file: No such file or directory                    
 [2013-11-10 00:22:30] hidapi_try_lib: Couldn't load libhidapi-0.so: libhidapi-0.so: cannot open shared object file: No such file or directory                    
 [2013-11-10 00:22:30] hidapi_try_lib: Successfully loaded libhidapi-hidraw.so                    
 [2013-11-10 00:22:30] hid_devinfo_scan: Found "NanoFury NF1 v0.6" serial "0000068980"                    
 [2013-11-10 00:22:30] hid_devinfo_scan: Found "NanoFury NF1 v0.6" serial "0000068550"                    
 [2013-11-10 00:22:30] lowlevel_scan: Found hid device at hid:/dev/hidraw1 (path=/dev/hidraw1, vid=04d8, pid=00de, manuf=Microchip Technology Inc., prod=NanoFury NF1 v0.6, serial=0000068550)                    
 [2013-11-10 00:22:30] lowlevel_scan: Found hid device at hid:/dev/hidraw0 (path=/dev/hidraw0, vid=04d8, pid=00de, manuf=Microchip Technology Inc., prod=NanoFury NF1 v0.6, serial=0000068980)                    
 [2013-11-10 00:22:30] lowlevel_scan: Found mcp2210 device at hid:/dev/hidraw0 (path=/dev/hidraw0, vid=04d8, pid=00de, manuf=Microchip Technology Inc., prod=NanoFury NF1 v0.6, serial=0000068980)                    
 [2013-11-10 00:22:30] lowlevel_scan: Found mcp2210 device at hid:/dev/hidraw1 (path=/dev/hidraw1, vid=04d8, pid=00de, manuf=Microchip Technology Inc., prod=NanoFury NF1 v0.6, serial=0000068550)                    
 [2013-11-10 00:22:30] Devices detected:                    
 [2013-11-10 00:22:30]   0. NFY 0  (driver: nanofury)                    
 [2013-11-10 00:22:30]   1. NFY 1  (driver: nanofury)                    
2 devices listed

When I run I get this:
http://pastebin.com/UTq4h2Dy

(ignore the BE's and BF's)

So seems closer to working but not sure

[Luke-Jr]

I wonder if they're not getting enough power?

[RicRock]

I wonder if they're not getting enough power?

one sec... will test quick

[RicRock]

I wonder if they're not getting enough power?

Still unclear....

I have rosewill's and dlink hubs

I inserted one into hub:

Code:

[2013-11-10 00:56:43] Selecting pool 1 for work                    
 [2013-11-10 00:56:43] Generated stratum header 00000002ed60a17f1ba5d894d2604f6fb2afe0d585849de3c13595fd00000f0600000000f4a29090b69297b46b6c5945b9c6ae2d212cb29f03cce7be8974e9538ca42a9b527f1fd61b0096a800000000                    
 [2013-11-10 00:56:43] Work job_id 1e nonce2 02000000                    
 [2013-11-10 00:56:43] Generated target 00000000ffff0000000000000000000000000000000000000000000000000000                    
 [2013-11-10 00:56:43] Generated stratum work                    
 [2013-11-10 00:56:43] Pushing work from pool 1 to hash queue                    
 [2013-11-10 00:56:43] Selecting pool 1 for work                    
 [2013-11-10 00:56:43] Generated stratum header 00000002ed60a17f1ba5d894d2604f6fb2afe0d585849de3c13595fd00000f0600000000ccd1564f8ce73529687691ac31c2af4dd134ae904023e5f6bf97b04f39620e37527f1fd61b0096a800000000                    
 [2013-11-10 00:56:43] Work job_id 1e nonce2 03000000                    
 [2013-11-10 00:56:43] Generated target 00000000ffff0000000000000000000000000000000000000000000000000000                    
 [2013-11-10 00:56:43] Generated stratum work                    
 [2013-11-10 00:56:43] Pushing work from pool 1 to hash queue                    
 [2013-11-10 00:56:43] Selecting pool 1 for work                    
 [2013-11-10 00:56:43] Generated stratum header 00000002ed60a17f1ba5d894d2604f6fb2afe0d585849de3c13595fd00000f0600000000426cd1741d7f927949fdbfe5d47a0b5a727523ef8923212369673db93f744dff527f1fd61b0096a800000000                    
 [2013-11-10 00:56:43] Work job_id 1e nonce2 04000000                    
 [2013-11-10 00:56:43] Generated target 00000000ffff0000000000000000000000000000000000000000000000000000                    
 [2013-11-10 00:56:43] Generated stratum work                    
 [2013-11-10 00:56:43] Pushing work from pool 1 to hash queue                    
 [2013-11-10 00:56:43] Selecting pool 1 for work                    
 [2013-11-10 00:56:43] Generated stratum header 00000002ed60a17f1ba5d894d2604f6fb2afe0d585849de3c13595fd00000f0600000000581f9252da38ba7c9a8c3e1e01ff223d5a335ffbf0e335e4cfafcab6185da735527f1fd61b0096a800000000                    
 [2013-11-10 00:56:43] Work job_id 1e nonce2 05000000                    
 [2013-11-10 00:56:43] Generated target 00000000ffff0000000000000000000000000000000000000000000000000000                    
 [2013-11-10 00:56:43] Generated stratum work                    
 [2013-11-10 00:56:43] Pushing work from pool 1 to hash queue                    
 [2013-11-10 00:56:43] mcp2210_get_gpio_input: Failed to get current GPIO input values                    
 [2013-11-10 00:56:43] NFY 0: checkport failed                    
 [2013-11-10 00:56:43] NFY 0 failure, exiting     

Still not sure of power... is there a light on these things?

I alternated between all 10 units and plugged them in with no lights on the nano fury's

[vs3]

I wonder if they're not getting enough power?

Still unclear....

I have rosewill's and dlink hubs

I inserted one into hub:
(...)
Still not sure of power... is there a light on these things?

Just to clarify - the question is whether the devices get enough power or not. It is not what is the brand of the hub.
The only thing that matters is if those are powered hub or not.

You need a powered hub. And you appear to have a regular one that draws all its power from the PC. That power is barely enough for 1 device (when you add the power used by the hub).

From your logs it appears that the NanoFury devices do get detected and they pass the first check (that's when it reads the serial numbers), but once the chip gets turned on and given work to do (which leads to the chip starting to need and use all that power) you get a "checkport failed" message indicating that the device no longer responds.
So the only difference between the first check and after the second check is that the second time the chip is working and using power.

That leads me to suspect that your hubs are likely not powered or don't have enough power.

You can easily check if my theory is correct by plugging just one device into a USB port directly on your computer (and not via hub and not on a RasPI since its ports are not properly powered - e.g. don't provide at least 500mA as per the USB2.0 specs).

The NanoFury devices do have a light - that white component on the board is the LED. It will turn on (yellow) when the device is working. In your case since it probably runs out of power very quickly you may see this light turn on for a very brief moment - like a fraction of a second (e.g. 10-20mS).

[RicRock]

Still unclear....

I have rosewill's and dlink hubs

I inserted one into hub:
(...)
Still not sure of power... is there a light on these things?

Just to clarify - the question is whether the devices get enough power or not. It is not what is the brand of the hub.
The only thing that matters is if those are powered hub or not.

You need a powered hub. And you appear to have a regular one that draws all its power from the PC. That power is barely enough for 1 device (when you add the power used by the hub).

I'm using 4A hubs, I mention the brands so we know they are name brand hubs and not china hubs.

What in my statement made you think they were un-powered?


I plugged 1 nanofury into a 4A powered hub and got the error messages above.

I alternated placing 1 nanofury into the 4A hub and did not see any lights appear so I asked if they had lights on them.

[bigbeninlondon]

Quick question:

Can these mine in conjunction with Block Erupters?  It appears that bfgminer doesn't auto-detect my block erupters, and cgminer doesn't detect the nanofuries, so I have to have both processes running ATM.  I tried adding --scan-serial erupter:all to my bfgminer parameters, to no avail.  Are there additional steps I have to take?

[Luke-Jr]

Can these mine in conjunction with Block Erupters?

Yes, I've been doing just that.

It appears that bfgminer doesn't auto-detect my block erupters, and cgminer doesn't detect the nanofuries, so I have to have both processes running ATM.  I tried adding --scan-serial erupter:all to my bfgminer parameters, to no avail.  Are there additional steps I have to take?

Many block erupters were sold without autodetection support*.
If you are using cgminer with them, then you/cgminer (Windows/Linux) have replaced the correct SiLabs/cp210x driver with WinUSB/usbfs.
You will need to undo this to use it with any software that uses the standard interfaces, including BFGMiner.

* cgminer will automatically probe any cp210x devices to check if they are erupters; BFGMiner only does this with -S erupter:all unless they identify themselves as Erupters up-front.

[RicRock]

If someone that has them working can try them in a USB 2.0 hub that would be awesome.

[bigbeninlondon]

Can these mine in conjunction with Block Erupters?

Yes, I've been doing just that.

It appears that bfgminer doesn't auto-detect my block erupters, and cgminer doesn't detect the nanofuries, so I have to have both processes running ATM.  I tried adding --scan-serial erupter:all to my bfgminer parameters, to no avail.  Are there additional steps I have to take?

Many block erupters were sold without autodetection support*.
If you are using cgminer with them, then you/cgminer (Windows/Linux) have replaced the correct SiLabs/cp210x driver with WinUSB/usbfs.
You will need to undo this to use it with any software that uses the standard interfaces, including BFGMiner.

* cgminer will automatically probe any cp210x devices to check if they are erupters; BFGMiner only does this with -S erupter:all unless they identify themselves as Erupters up-front.

Thanks for the help.  That worked like a charm.  I'm now 100% bfgminer.

[Taugeran]

If someone that has them working can try them in a USB 2.0 hub that would be awesome.

i have them working in the hub with all the asicminer usbs and the BF1 pictured below. pic is from when i first unwrapped them


Hub is a Dlink DUB-H7 powered usb2.0 hub i can get them going at 56 bits in the charging ports but they don't have enough cooling to be stable so 54 bits for now

screen of 11 hrs of them running on that hub

[Swimmer63]

I'm impressed. You have all the types of USBs working in one miner and on one hub?

[bigbeninlondon]

I'm impressed. You have all the types of USBs working in one miner and on one hub?

I have two four port hubs, but yea.

[RicRock]

If someone that has them working can try them in a USB 2.0 hub that would be awesome.

i have them working in the hub with all the asicminer usbs and the BF1 pictured below. pic is from when i first unwrapped them


Hub is a Dlink DUB-H7 powered usb2.0 hub i can get them going at 56 bits in the charging ports but they don't have enough cooling to be stable so 54 bits for now

screen of 11 hrs of them running on that hub

Can't see the image at work.

So works on your Dlink, What about your Pi?

Again, sorry if it shows in the pic.

[Taugeran]

If someone that has them working can try them in a USB 2.0 hub that would be awesome.

i have them working in the hub with all the asicminer usbs and the BF1 pictured below. pic is from when i first unwrapped them
snip

Hub is a Dlink DUB-H7 powered usb2.0 hub i can get them going at 56 bits in the charging ports but they don't have enough cooling to be stable so 54 bits for now

screen of 11 hrs of them running on that hub
snip

Can't see the image at work.

So works on your Dlink, What about your Pi?

Again, sorry if it shows in the pic.

not currently running on a pi. having lockup issues (investigating...)

running on windows but should run just fine on a normal linux box


the dlink is running 2 NFY and all my other hardware is on a cheap 7 port hub from MCM electronics (i live just down the street from their warehouse)


in all 5 BES, 1 BPM, 2 NFY totaling ~8-9 ghs depending on the timeframe


goin to try  few different linux distros to see fi the lockups are raspian specific

[Taugeran]

I'm impressed. You have all the types of USBs working in one miner and on one hub?

2 hubs the top screen was before i set up the second

[Taugeran]

I'm impressed. You have all the types of USBs working in one miner and on one hub?

2 hubs the top screen was before i set up the second

command used

Code:

bfgminer -c windows.conf -D  -S BPM:\\.\COM8 -S BES:\\.\COM9 -S BES:\\.\COM10 -S BES:\\.\COM11 -S BES:\\.\COM12 -S BES:\\.\COM13

though i could condense it into my config file as:

Code:

"scan-serial":
[
"BPM:\\.\COM8",
"BES:\\.\COM9",
"BES:\\.\COM10",
"BES:\\.\COM11",
"BES:\\.\COM12",
"BES:\\.\COM13"
]

and unfortunately ill probably never have a klondike k1 to add to the collection :,< silent tear

[RicRock]

Can't see the image at work.

So works on your Dlink, What about your Pi?

Again, sorry if it shows in the pic.

not currently running on a pi. having lockup issues (investigating...)

How is Pi powered? maybe lockup is power feed back from powered hub?


As far as running nanos on Pi, I wonder if it has something to do with the Broadcom BCM2835 chip used.

My hubs are powered but no go on nanos

[Taugeran]

Can't see the image at work.

So works on your Dlink, What about your Pi?

Again, sorry if it shows in the pic.

not currently running on a pi. having lockup issues (investigating...)

How is Pi powered? maybe lockup is power feed back from powered hub?


As far as running nanos on Pi, I wonder if it has something to do with the Broadcom BCM2835 chip used.

My hubs are powered but no go on nanos

its not a lockup of the whole device. i can ctrl-c bfgminer to death just fine.

its just bfgminer seems to hang/not produce anymore debug output after a seemingly random number of MCP2210 transfers temporarily rejected....

anyway ttyal must rest

pi was powered through power micro usb and probably some back feed from hubs

[RicRock]

Would love to hear from some additional linux users.

We know they work:

On windows with USB2 and USB3 hubs.
On "normal" linux box with USB3 hubs.

We know it doesn't appear to work w/ Pi and USB2 hubs.

[erk]

Would love to hear from some additional linux users.

We know they work:

On windows with USB2 and USB3 hubs.
On "normal" linux box with USB3 hubs.

We know it doesn't appear to work w/ Pi and USB2 hubs.

A Pi is a normal Linux box it's just not Intel based. You obviously have to make the effort to compile the correct version of bfgminer to support the NF1 the hub is irrelevant is it's not part of the Pi.

[Luke-Jr]

Would love to hear from some additional linux users.

We know they work:

On windows with USB2 and USB3 hubs.
On "normal" linux box with USB3 hubs.

We know it doesn't appear to work w/ Pi and USB2 hubs.

A Pi is a normal Linux box it's just not Intel based. You obviously have to make the effort to compile the correct version of bfgminer to support the NF1 the hub is irrelevant is it's not part of the Pi.

Not quite. Pi has various USB-related hardware issues.

[erk]

Would love to hear from some additional linux users.

We know they work:

On windows with USB2 and USB3 hubs.
On "normal" linux box with USB3 hubs.

We know it doesn't appear to work w/ Pi and USB2 hubs.

A Pi is a normal Linux box it's just not Intel based. You obviously have to make the effort to compile the correct version of bfgminer to support the NF1 the hub is irrelevant is it's not part of the Pi.

Not quite. Pi has various USB-related hardware issues.

Wouldn't they be the same for all USB miners on the Pi then?

[RicRock]

Wouldn't they be the same for all USB miners on the Pi then?

Proof is in testing and what I posted is what we know so far.

I was also an Admin not a programmer but maybe commands are used that the Broadcom BCM2835 used in the Pi as USB host doesn't understand?

[vs3]

I wonder if they're not getting enough power?

Still unclear....

I have rosewill's and dlink hubs

I inserted one into hub:

Code:

 [2013-11-10 00:56:43] Pushing work from pool 1 to hash queue                    
 [2013-11-10 00:56:43] mcp2210_get_gpio_input: Failed to get current GPIO input values                    
 [2013-11-10 00:56:43] NFY 0: checkport failed                    
 [2013-11-10 00:56:43] NFY 0 failure, exiting     

Still not sure of power... is there a light on these things?

I alternated between all 10 units and plugged them in with no lights on the nano fury's

The clue for me in the log above is the "checkport failed" message.

The program does "checkport" while it first tests all devices and later at regular intervals when it sends work to the device.

The fact that it passed the first "checkport" means that there was good communication with the device at that time and everything worked as expected.

The line immediately preceding the "checkport failed" message says "mcp2210_get_gpio_input: Failed to get current GPIO input values" which indicates that the device is no longer plugged into the USB hub. Or in other words - the host can no longer communicate with the device. As for why did the communication get disrupted - there are many possible answers.

My guess is that the USB host (or hub) did not provide enough power to the device and either the hub got entirely dropped or just the device got dropped.
You can test whether that is the case by plugging the device directly into your PC - all motherboards will provide sufficient power. Note however that Raspberry Pi ports are not USB2.0 compliant - they barely provide enough power for a mouse and a keyboard - so plugging it directly into RPi's USB port may or may not work.

It seems that wherever you had plugged the device was good enough for the initial communication, and had it not been for the power issues everything else worked.

[Taugeran]

@vs3

can you elaborate on the req's to pencil mod the NFY similar to the BF1?

if the voltage setup circuits are anything similar: on BF1

rub graphite pencil across R15 until resistance measured across R15 and R16 is ~0.89Kohm

[vs3]

@vs3

can you elaborate on the req's to pencil mod the NFY similar to the BF1?

if the voltage setup circuits are anything similar: on BF1

rub graphite pencil across R15 until resistance measured across R15 and R16 is ~0.89Kohm

Yes - the procedure is almost identical - I'll repost what I wrote about that (on Marto74's thread) - let me know if that covers it or I missed anything:

Can you give me instructions for pencil mod?

See this image:


R2 and R3 determine the voltage:
V = 0.8*(R2+R3)/R3
(and factory settings are R2=100 and R3=2.4k for about 0.833V)

If you want to increase the voltage you can either increase R2 or decrease R3 (pencil mod decreases resistance).
And to lower the voltage - you can lower R2 or increase R3.

My 2 cents - start by first lowering the voltage. At least that's the safer option

[erk]

Does the NF1 worth with cgminer as well or only bfgminer?

[vs3]

Does the NF1 worth with cgminer as well or only bfgminer?

We started working on a cgminer port but it turned out bfgminer somehow gets 10-15% more GH/s, so we've sort of given up on fiddling with cgminer (at least for now). I can send you what we have if you want - I've gotten it to work on Windows only though. If there are any volunteers that know their way around Linux and can take care of that part - just let me know and I'd be glad to assist.

For a proper port into cgminer it will have to be done by Con Kolivas - but at the moment it is unclear when and if at all that's going to happen. In my last email exchange with him he said "I'm overwhelmed with other code tasks at the time (mostly paid which means things like your code gets low priority I'm afraid)."
And since Luke did such an awesome job with bfgminer I haven't had to bother Con again.

[vs3]

Can you give me instructions for pencil mod?

...

By the way - if anyone does indeed do some pencil mods - would you please share your observations? Some feedback about what works the best would be more than welcome

[whiteEAGLE]

i didn`t do a pencil mode, but with a powered USB 3.0 Hub and OS-bits set to 54 the miners run above stable 2,6 gH/s (with fan)

[bigbeninlondon]

I believe one of my sticks mines less efficiently at 54 bits.  Can I specify the bits individually?

[vs3]

I believe one of my sticks mines less efficiently at 54 bits.  Can I specify the bits individually?

I don't know if you can do that on the command line, but you can adjust the bits individually via bfgminer's Device Manager:

bfgminer version 3.3.0 - Started: [2013-11-14 20:06:10] - [  0 days 04:23:41]
 [ M ]anage devices [ P ]ool management [ S ]ettings [ D ]isplay options  [ H ]elp [ Q ]uit
 Connected to mint.bitminter.com diff 4 with stratum as user vs3_nanofury1
 Block: ...a4cca397 #269713  Diff:511M ( 3.66Ph/s)  Started: [00:23:57]
 ST:2  F:0  NB:31  AS:0  BW:[ 54/ 46 B/s]  E:21.08  I:  183uBTC/hr  BS:128k
 2            |  4.68/ 4.57/ 4.48Gh/s | A:5781 R:14+0(.24%) HW:231/1.4%
--------------------------------------------------------------------------------
 NFY 0:       |  2.42/ 2.41/ 2.35Gh/s | A:3058 R: 7+0(.18%) HW:171/1.9%
 NFY 1:       |  2.16/ 2.16/ 2.13Gh/s | A:2723 R: 7+0(.31%) HW: 60/.74%
--------------------------------------------------------------------------------

Select processor to manage using up/down arrow keys
 NFY 1 :       |  2.16/ 2.16/ 2.13Gh/s | A:2723 R: 7+0(.31%) HW: 60/.74%
  NanoFury NF1 v0.6
Serial: 0000068967
Oscillator bits: 52

[ D ]isable [ O ]scillator bits
[Slash] Find processor  [Plus] Add device(s)  [Enter] Close device manager

[erk]

Anyone managed to get the latest bfgminer to compile on FreeBSD 9.2-RELEASE?

The configure script can't seem to find libusb for some reason which is in the standard location  /usr/lib/libusb.a

I got bfgminer to compile on my Mac with Snow Leopard, but it gives a segfault when I try and mine. No luck on either platform.

I tried Debian linux and the bfgminer configure can't find hidapi even though it's compiled and installed.

This is pissing me off, I just want to run the NF1 I don't have a spare windows machine to put it on, only Mac, FreeBSD, or Linux.

[Zich]

Anyone had luck with Raspberry Pi wheezy?

[vs3]

Anyone had luck with Raspberry Pi wheezy?

I bought a RasPi last week and am waiting for it to arrive .. as soon as I get it I'll give it a shot too.
No promises though - I'm not sure if the hidapi is compatible with it at all or what is the nature of the issue..

[Zich]

Anyone had luck with Raspberry Pi wheezy?

I bought a RasPi last week and am waiting for it to arrive .. as soon as I get it I'll give it a shot too.
No promises though - I'm not sure if the hidapi is compatible with it at all or what is the nature of the issue..

Great, i am looking for it 

[RicRock]

Anyone had luck with Raspberry Pi wheezy?

I bought a RasPi last week and am waiting for it to arrive .. as soon as I get it I'll give it a shot too.
No promises though - I'm not sure if the hidapi is compatible with it at all or what is the nature of the issue..

Great, i am looking for it 

+1000

[dennisc]

Anyone managed to get the latest bfgminer to compile on FreeBSD 9.2-RELEASE?

The configure script can't seem to find libusb for some reason which is in the standard location  /usr/lib/libusb.a

I got bfgminer to compile on my Mac with Snow Leopard, but it gives a segfault when I try and mine. No luck on either platform.

I tried Debian linux and the bfgminer configure can't find hidapi even though it's compiled and installed.

This is pissing me off, I just want to run the NF1 I don't have a spare windows machine to put it on, only Mac, FreeBSD, or Linux.

I have no experience with FreeBSD.  However I had trouble (they say rasbpian's libusb is not useable) compiling for raspberrypi. The suggested solution was to provide libusb from compiled source. See https://bitcointalk.org/index.php?topic=338938.msg3634958#msg3634958 for how this was done for pi. Maybe you can adapt it to your situation.

[zamot]

Anyone managed to get the latest bfgminer to compile on FreeBSD 9.2-RELEASE?

The configure script can't seem to find libusb for some reason which is in the standard location  /usr/lib/libusb.a

I got bfgminer to compile on my Mac with Snow Leopard, but it gives a segfault when I try and mine. No luck on either platform.

I tried Debian linux and the bfgminer configure can't find hidapi even though it's compiled and installed.

This is pissing me off, I just want to run the NF1 I don't have a spare windows machine to put it on, only Mac, FreeBSD, or Linux.

Did you try cgminer ?

[vs3]

Anyone managed to get the latest bfgminer to compile on FreeBSD 9.2-RELEASE?

The configure script can't seem to find libusb for some reason which is in the standard location  /usr/lib/libusb.a

I got bfgminer to compile on my Mac with Snow Leopard, but it gives a segfault when I try and mine. No luck on either platform.

I tried Debian linux and the bfgminer configure can't find hidapi even though it's compiled and installed.

This is pissing me off, I just want to run the NF1 I don't have a spare windows machine to put it on, only Mac, FreeBSD, or Linux.

Did you try cgminer ?

Out of curiosity - what makes you think that cgminer will work? Does it support NanoFury?

[erk]

Anyone managed to get the latest bfgminer to compile on FreeBSD 9.2-RELEASE?

The configure script can't seem to find libusb for some reason which is in the standard location  /usr/lib/libusb.a

I got bfgminer to compile on my Mac with Snow Leopard, but it gives a segfault when I try and mine. No luck on either platform.

I tried Debian linux and the bfgminer configure can't find hidapi even though it's compiled and installed.

This is pissing me off, I just want to run the NF1 I don't have a spare windows machine to put it on, only Mac, FreeBSD, or Linux.

Did you try cgminer ?

cgminer does not have the hidapi driver.

I just want to get the NF1 running on any os other than Windows, has anyone done this, if so can you describe the steps please?

[Luke-Jr]

I just want to get the NF1 running on any os other than Windows, has anyone done this, if so can you describe the steps please?

With Gentoo, you can just emerge bfgminer with the nanofury USE flag.

[erk]

I just want to get the NF1 running on any os other than Windows, has anyone done this, if so can you describe the steps please?

With Gentoo, you can just emerge bfgminer with the nanofury USE flag.

Gentoo is not very mainstream, meaning that's probably not what Linux users of the NF1 are going to be running, it's like #37 on http://distrowatch.com/ nevertheless I will try it. I would have thought it would be tested on on a Debian or Redhat derivative by now.

[Luke-Jr]

I just want to get the NF1 running on any os other than Windows, has anyone done this, if so can you describe the steps please?

With Gentoo, you can just emerge bfgminer with the nanofury USE flag.

Gentoo is not very mainstream, meaning that's probably not what Linux users of the NF1 are going to be running, it's like #37 on http://distrowatch.com/ nevertheless I will try it. I would have thought it would be tested on on a Debian or Redhat derivative by now.

I've tested another HID miner on Debian with no problems, so I would be surprised if NanoFury didn't work as well.

[erk]

I just want to get the NF1 running on any os other than Windows, has anyone done this, if so can you describe the steps please?

With Gentoo, you can just emerge bfgminer with the nanofury USE flag.

Gentoo is not very mainstream, meaning that's probably not what Linux users of the NF1 are going to be running, it's like #37 on http://distrowatch.com/ nevertheless I will try it. I would have thought it would be tested on on a Debian or Redhat derivative by now.

I've tested another HID miner on Debian with no problems, so I would be surprised if NanoFury didn't work as well.

How did you get bfgminer to detect the hidapi libraries during configure? Did you have to move them from the default location /usr/local/lib/hidapi? the bfgminer configure seems to be looking for a package installed.

[Luke-Jr]

I just want to get the NF1 running on any os other than Windows, has anyone done this, if so can you describe the steps please?

With Gentoo, you can just emerge bfgminer with the nanofury USE flag.

Gentoo is not very mainstream, meaning that's probably not what Linux users of the NF1 are going to be running, it's like #37 on http://distrowatch.com/ nevertheless I will try it. I would have thought it would be tested on on a Debian or Redhat derivative by now.

I've tested another HID miner on Debian with no problems, so I would be surprised if NanoFury didn't work as well.

How did you get bfgminer to detect the hidapi libraries during configure? Did you have to move them from the default location /usr/local/lib/hidapi? the bfgminer configure seems to be looking for a package installed.

No, Everything is under /usr/local:

Code:

/usr/share/doc/hidapi
/usr/share/doc/hidapi/README.txt
/usr/local/include/hidapi
/usr/local/include/hidapi/hidapi.h
/usr/local/share/doc/hidapi
/usr/local/share/doc/hidapi/LICENSE-gpl3.txt
/usr/local/share/doc/hidapi/LICENSE-orig.txt
/usr/local/share/doc/hidapi/AUTHORS.txt
/usr/local/share/doc/hidapi/README.txt
/usr/local/share/doc/hidapi/LICENSE.txt
/usr/local/share/doc/hidapi/LICENSE-bsd.txt
/usr/local/lib/libhidapi-libusb.so.0.0.0
/usr/local/lib/libhidapi-hidraw.so
/usr/local/lib/libhidapi-libusb.a
/usr/local/lib/libhidapi-libusb.la
/usr/local/lib/libhidapi-libusb.so.0
/usr/local/lib/libhidapi-hidraw.so.0
/usr/local/lib/libhidapi-hidraw.a
/usr/local/lib/libhidapi-libusb.so
/usr/local/lib/libhidapi-hidraw.la
/usr/local/lib/libhidapi-hidraw.so.0.0.0
/usr/local/lib/pkgconfig/hidapi-libusb.pc
/usr/local/lib/pkgconfig/hidapi-hidraw.pc

Note the README's FAQ entry "Q: Why can't BFGMiner find lib<something> even after I installed it from source code?" for actually running, after you get it built...

[erk]

Note the README's FAQ entry "Q: Why can't BFGMiner find lib<something> even after I installed it from source code?" for actually running, after you get it built...

Ok I did the ldconfig from the README FAQ entry and it's gotten a little further:

# ./bfgminer -S NFY:all -d? -D
 [2013-11-20 09:17:05] setrlimit: Soft fd limit not being changed from 1024 (FD_SETSIZE=1024; hard limit=4096)                    
 [2013-11-20 09:17:05] Started bfgminer 3.6.0                    
 [2013-11-20 09:17:05] hidapi_try_lib: Couldn't load libhidapi.so: libhidapi.so: cannot open shared object file: No such file or directory                    
 [2013-11-20 09:17:05] hidapi_try_lib: Couldn't load libhidapi-0.so: libhidapi-0.so: cannot open shared object file: No such file or directory                    
 [2013-11-20 09:17:05] hidapi_try_lib: Successfully loaded libhidapi-hidraw.so                    
 [2013-11-20 09:17:05] hid_devinfo_scan: Found "NanoFury NF1 v0.6" serial "0000073625"                    
 [2013-11-20 09:17:05] lowlevel_scan: Found usb device at usb:002:004 (path=(null), vid=04d8, pid=00de, manuf=Microchip Technology Inc., prod=NanoFury NF1 v0.6, serial=0000073625)                    
 [2013-11-20 09:17:05] lowlevel_scan: Found usb device at usb:005:001 (path=(null), vid=1d6b, pid=0001, manuf=Linux 2.6.32-23-pve uhci_hcd, prod=UHCI Host Controller, serial=0000:00:1d.3)                    
 [2013-11-20 09:17:05] lowlevel_scan: Found usb device at usb:004:001 (path=(null), vid=1d6b, pid=0001, manuf=Linux 2.6.32-23-pve uhci_hcd, prod=UHCI Host Controller, serial=0000:00:1d.2)                    
 [2013-11-20 09:17:05] lowlevel_scan: Found usb device at usb:003:001 (path=(null), vid=1d6b, pid=0001, manuf=Linux 2.6.32-23-pve uhci_hcd, prod=UHCI Host Controller, serial=0000:00:1d.1)                    
 [2013-11-20 09:17:05] lowlevel_scan: Found usb device at usb:002:001 (path=(null), vid=1d6b, pid=0001, manuf=Linux 2.6.32-23-pve uhci_hcd, prod=UHCI Host Controller, serial=0000:00:1d.0)                    
 [2013-11-20 09:17:05] lowlevel_scan: Found usb device at usb:001:001 (path=(null), vid=1d6b, pid=0002, manuf=Linux 2.6.32-23-pve ehci_hcd, prod=EHCI Host Controller, serial=0000:00:1d.7)                    
 [2013-11-20 09:17:05] lowlevel_scan: Found hid device at hid:/dev/hidraw0 (path=/dev/hidraw0, vid=04d8, pid=00de, manuf=Microchip Technology Inc., prod=NanoFury NF1 v0.6, serial=0000073625)                    
 [2013-11-20 09:17:05] lowlevel_scan: Found mcp2210 device at hid:/dev/hidraw0 (path=/dev/hidraw0, vid=04d8, pid=00de, manuf=Microchip Technology Inc., prod=NanoFury NF1 v0.6, serial=0000073625)                    
 [2013-11-20 09:17:05] mcp2210_get_configs: Failed to get current SPI config                    
 [2013-11-20 09:17:05] nanofury_foundlowl: Matched "NanoFury NF1 v0.6" serial "0000073625", but mcp2210 lowlevel driver failed to open it                    
 [2013-11-20 09:17:05] Devices detected:                    
 [2013-11-20 09:17:05] Timers: Using clock_gettime(CLOCK_MONOTONIC_RAW)                    
0 devices listed

Does it need to use hidraw or will it try libusb? I doubt if hidraw is compile into the kernel, libusb is there.

/EDIT nvm I deleted all the hidraw libs, ran another ldconfig and it found the device with libusb it's mining now at about 2.1GH/s with standard defaults.

Thanks.

[Zich]

/EDIT nvm I deleted all the hidraw libs, ran another ldconfig and it found the device with libusb it's mining now at about 2.1GH/s with standard defaults.

Thanks.

Hi erk, please tell me how to delete the hidraw lib? step by step since i am new to linux 

[erk]

/EDIT nvm I deleted all the hidraw libs, ran another ldconfig and it found the device with libusb it's mining now at about 2.1GH/s with standard defaults.

Thanks.

Hi erk, please tell me how to delete the hidraw lib? step by step since i am new to linux 

Assuming you are using Debian and the files are in the same place.

 cd /usr/local/lib

 rm -i *hidraw*

The only reason I removed them was I can't be bothered install installing the kernel source, setting the zillion options, and recompiling with hidraw enabled.

[RicRock]

Does it need to use hidraw or will it try libusb? I doubt if hidraw is compile into the kernel, libusb is there.

/EDIT nvm I deleted all the hidraw libs, ran another ldconfig and it found the device with libusb it's mining now at about 2.1GH/s with standard defaults.

Thanks.

Would def love further instructions

[RicRock]

so from the hidapi GIT source I did a make uninstall and this is what I have left

Code:

/usr/include/linux/hidraw.h
/usr/lib/libhidapi-hidraw.so
/usr/lib/libhidapi-hidraw.la
/usr/lib/libhidapi-hidraw.so.0.0.0
/usr/lib/pkgconfig/hidapi-hidraw.pc
/usr/lib/libhidapi-hidraw.so.0
/usr/lib/libhidapi-hidraw.a

Removing those to see if configure of bfgminer errors out for having nanofury enabled but no hidapi libs

Compiled ok but same errors as before on my PI (Wheezy)

[Zich]

Assuming you are using Debian and the files are in the same place.

 cd /usr/local/lib

 rm -i *hidraw*

The only reason I removed them was I can't be bothered install installing the kernel source, setting the zillion options, and recompiling with hidraw enabled.

Thanks erk. But it's seem with pi, it's more complicated.

[erk]

Assuming you are using Debian and the files are in the same place.

 cd /usr/local/lib

 rm -i *hidraw*

The only reason I removed them was I can't be bothered install installing the kernel source, setting the zillion options, and recompiling with hidraw enabled.

Thanks erk. But it's seem with pi, it's more complicated.

How do you know the hidapi driver even works on a Pi? I would be surprised if it did without modifications.

[Zich]

How do you know the hidapi driver even works on a Pi? I would be surprised if it did without modifications.

That's the problem, it's didn't work 

[RicRock]

/EDIT nvm I deleted all the hidraw libs, ran another ldconfig and it found the device with libusb it's mining now at about 2.1GH/s with standard defaults.

Thanks.

Hi erk, please tell me how to delete the hidraw lib? step by step since i am new to linux 

Assuming you are using Debian and the files are in the same place.

 cd /usr/local/lib

 rm -i *hidraw*

The only reason I removed them was I can't be bothered install installing the kernel source, setting the zillion options, and recompiling with hidraw enabled.

if I remove hidapi, ./configure complains and doesn't enable nano fury.

did you install hidapi, run configure of bfgminer, delete libraries, then ran the bfgminer make?

[erk]

/EDIT nvm I deleted all the hidraw libs, ran another ldconfig and it found the device with libusb it's mining now at about 2.1GH/s with standard defaults.

Thanks.

Hi erk, please tell me how to delete the hidraw lib? step by step since i am new to linux 

Assuming you are using Debian and the files are in the same place.

 cd /usr/local/lib

 rm -i *hidraw*

The only reason I removed them was I can't be bothered install installing the kernel source, setting the zillion options, and recompiling with hidraw enabled.

if I remove hidapi, ./configure complains and doesn't enable nano fury.

did you install hidapi, run configure of bfgminer, delete libraries, then ran the bfgminer make?

You have to have hidapi for nanofury I was talking about removing the hidraw variant not all the hidapi libraries. However we don't know that the hidapi works with the Pi hardware.

I don't own a Pi so my setup is nothing like yours I am working with Debian on Intel hardware.

[Zillions]

Stupid question I just freed up a usb port on my hub is there any more available? or was there another thread?

[Zich]

Stupid question I just freed up a usb port on my hub is there any more available? or was there another thread?

Technobit NanoFury

[RicRock]

You have to have hidapi for nanofury I was talking about removing the hidraw variant not all the hidapi libraries. However we don't know that the hidapi works with the Pi hardware.

I don't own a Pi so my setup is nothing like yours I am working with Debian on Intel hardware.

Was worth a shot, closest they've been to starting:

[RicRock]

OK

Unplugged all but 2 Nanofury's from a D-Link hub with 4amp power supply.

I set the osc6-bits to 5

I'm now getting this:

[vs3]

OK

Unplugged all but 2 Nanofury's from a D-Link hub with 4amp power supply.

I set the osc6-bits to 5

I'm now getting this:

There is a way to get the debug logging turned on and it will print all kinds of info that would be helpful with chasing that further. I forgot what was the parameter - I'll look it up tonight and post a note.

If you figure it out in the mean time - plug only one NanoFury (and no other boards - that's just to minimize the amount of noise and unrelated transactions) and PM or email me the debug log.

[Taugeran]

-D -T 2>./dafuq.log

will enable startup debug and disable curses

and log to dafuq.log in bfgminer startup dir

[Zillions]

Stupid question I just freed up a usb port on my hub is there any more available? or was there another thread?

Technobit NanoFury

Was hoping for something a tad more local (East coast,USA) to avoid shipping fees? Guess I'll have to wait till there's another group buy.

[RicRock]

-D -T 2>./dafuq.log

will enable startup debug and disable curses

and log to dafuq.log in bfgminer startup dir

Really just

mcp2210_spi_transfer: Failed to continue SPI transfer (59 bytes remaining)
 [2013-11-20 23:35:23] NFY 0 failure, disabling!
 [2013-11-20 23:35:23] mcp2210_set_cfg_spi: Error setting current SPI config (248)
 [2013-11-20 23:35:23] mcp2210_set_cfg_spi: Error setting current SPI config (248)
 [2013-11-20 23:35:23] NFY 0 failure, disabling!
 [2013-11-20 23:35:23] NFY 0: bitfury_init_oldbuf: Giving up after 4 tries
 [2013-11-20 23:35:24] NFY 0: bitfury_init_oldbuf: Giving up after 4 tries
 [2013-11-20 23:35:24] Accepted 3b1fd2cb BES12  Diff 4/2
 [2013-11-20 23:35:25] NFY 0: bitfury_init_oldbuf: Giving up after 4 tries
 [2013-11-20 23:35:25] Accepted 71b2c25a BES 6  Diff 2/2
 [2013-11-20 23:35:25] mcp2210_spi_transfer: Failed to continue SPI transfer (60 bytes remaining)
 [2013-11-20 23:35:25] NFY 0 failure, disabling!
 [2013-11-20 23:35:25] mcp2210_set_cfg_spi: Error setting current SPI config (248)


over and over again

[vs3]

The log would look like this:

Code:

 [2013-10-16 04:40:32.895136] hidapi_try_lib: Successfully loaded libhidapi-libusb.so
 [2013-10-16 04:40:32.907271] mcp2210_devinfo_scan: Found "MCP2210 USB to SPI Master" serial "0000062135"
 [2013-10-16 04:40:32.962958] >>>tx>42010000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
 [2013-10-16 04:40:32.964924] >>>rx>42000020400d0300ffffefff000000000000010000000000e5c3384be5c3384be03dc4a0c2139285f1f119c8e5c3384be5c3384be5c3384be01489a0e027c5a0
 [2013-10-16 04:40:32.964931] >>>w>00
 [2013-10-16 04:40:32.964938] >>>tx>42000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
 [2013-10-16 04:40:32.966924] >>>rx>42000110ff0d0300ffffefff000000000000010000000000e5c3384be5c3384be03dc4a0c2139285f1f119c8e5c3384be5c3384be5c3384be01489a0e027c5a0
 [2013-10-16 04:40:32.966931] >>>r>ff
 [2013-10-16 04:40:32.974963] >>>tx>42010000ff0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
 [2013-10-16 04:40:32.976937] >>>rx>42000020400d0300ffffefff000000000000010002000000e5c3384be5c3384be03dc4a0c2139285f1f119c8e5c3384be5c3384be5c3384be01489a0e027c5a0
...
 [2013-10-16 04:40:35.227910] >>>tx>423c000004f230009f590fab4e2c823b79088bf8d7b3c7af4a8f28c660288b48a8a49c8bbeee5abf4a8f28c6cd34ee8625d9e8b66cf89b279f590fabf47bbc55
 [2013-10-16 04:40:35.229879] >>>rx>42000020400d0300ffffefff0000000000003c0000000000e5c3384be5c3384be03dc4a0c2139285f1f119c8e5c3384be5c3384be5c3384be01489a0e027c5a0
 [2013-10-16 04:40:35.229891] >>>w>04f230009f590fab4e2c823b79088bf8d7b3c7af4a8f28c660288b48a8a49c8bbeee5abf4a8f28c6cd34ee8625d9e8b66cf89b279f590fabf47bbc55
 [2013-10-16 04:40:35.229897] >>>tx>4200000004f230009f590fab4e2c823b79088bf8d7b3c7af4a8f28c660288b48a8a49c8bbeee5abf4a8f28c6cd34ee8625d9e8b66cf89b279f590fabf47bbc55
 [2013-10-16 04:40:35.231890] >>>rx>42f80020400d0300ffffefff0000000000003c0000000000e5c3384be5c3384be03dc4a0c2139285f1f119c8e5c3384be5c3384be5c3384be01489a0e027c5a0
 [2013-10-16 04:40:35.231901] mcp2210_spi_transfer: SPI transfer rejected temporarily (60 bytes remaining)
 [2013-10-16 04:40:35.251974] >>>tx>4200000004f230009f590fab4e2c823b79088bf8d7b3c7af4a8f28c660288b48a8a49c8bbeee5abf4a8f28c6cd34ee8625d9e8b66cf89b279f590fabf47bbc55
 [2013-10-16 04:40:35.253915] >>>rx>42003c10ffffffff82d29cedc01a86871b139197e25e1985510093871b808216d0559a43c21392851b1391971b1391971b1391971b1391971b13919734d480da
 [2013-10-16 04:40:35.253927] >>>r>ffffffff82d29cedc01a86871b139197e25e1985510093871b808216d0559a43c21392851b1391971b1391971b1391971b1391971b13919734d480da
 [2013-10-16 04:40:35.255912] >>>tx>4214000072434268f0004fdc42d0bdf5c6a2436d4ac25fb600000000000000000000000000000000000000000000000000000000000000000000000000000000
 [2013-10-16 04:40:35.257909] >>>rx>42000020400d0300ffffefff0000000000001400005e1985510093871b808216d0559a43c21392851b1391971b1391971b1391971b1391971b13919734d480da
 [2013-10-16 04:40:35.257921] >>>w>72434268f0004fdc42d0bdf5c6a2436d4ac25fb6
 [2013-10-16 04:40:35.257927] >>>tx>4200000072434268f0004fdc42d0bdf5c6a2436d4ac25fb600000000000000000000000000000000000000000000000000000000000000000000000000000000
 [2013-10-16 04:40:35.259910] >>>rx>42001410c44b8009443234c0ffffffffffffffffffffffff510093871b808216d0559a43c21392851b1391971b1391971b1391971b1391971b13919734d480da
 [2013-10-16 04:40:35.259932] >>>r>c44b8009443234c0ffffffffffffffffffffffff
...

[Luke-Jr]

The log would look like this:

Sorry, the >>>tx/rx was a temporary hack for debugging

If I have time, I'll try to add some equivalent I guess...

[vs3]

The log would look like this:

Sorry, the >>>tx/rx was a temporary hack for debugging

If I have time, I'll try to add some equivalent I guess...

Ah ... never mind then.

Luke - and thanks for being so lightning fast with the reply! That saved us from a lot of hassles trying to get that kind of a log

[RicRock]

Snippet from log file in case anything is interesting

Code:

 [2013-11-20 23:30:30] mcp2210_spi_transfer: SPI transfer rejected temporarily (60 bytes remaining)
 [2013-11-20 23:30:30] mcp2210_spi_transfer: SPI transfer rejected temporarily (60 bytes remaining)
 [2013-11-20 23:30:30] mcp2210_spi_transfer: SPI transfer rejected temporarily (60 bytes remaining)
 [2013-11-20 23:30:30] mcp2210_spi_transfer: SPI transfer rejected temporarily (60 bytes remaining)
 [2013-11-20 23:30:30] mcp2210_spi_transfer: SPI transfer rejected temporarily (60 bytes remaining)
 [2013-11-20 23:30:30] mcp2210_spi_transfer: SPI transfer rejected temporarily (60 bytes remaining)
 [2013-11-20 23:30:30] mcp2210_spi_transfer: SPI transfer rejected temporarily (60 bytes remaining)
 [2013-11-20 23:30:30] mcp2210_spi_transfer: SPI transfer rejected temporarily (60 bytes remaining)
 [2013-11-20 23:30:30] mcp2210_spi_transfer: SPI transfer rejected temporarily (24 bytes remaining)
 [2013-11-20 23:30:30] mcp2210_spi_transfer: SPI transfer rejected temporarily (24 bytes remaining)
 [2013-11-20 23:30:30] mcp2210_spi_transfer: SPI transfer rejected temporarily (60 bytes remaining)
 [2013-11-20 23:30:30] mcp2210_spi_transfer: SPI transfer rejected temporarily (60 bytes remaining)
 [2013-11-20 23:30:30] NFY 1: bitfury_init_oldbuf: Differ at 1
 [2013-11-20 23:30:30] NFY 1: bitfury_init_oldbuf: Second differ at 2; trying again
 [2013-11-20 23:30:30] mcp2210_spi_transfer: SPI transfer rejected temporarily (60 bytes remaining)
 [2013-11-20 23:30:30] NFY 0: bitfury_init_oldbuf: Differ at 4
 [2013-11-20 23:30:30] NFY 0: bitfury_init_oldbuf: Second differ at 5; trying again
 [2013-11-20 23:30:30] mcp2210_spi_transfer: SPI transfer rejected temporarily (60 bytes remaining)
 [2013-11-20 23:30:30] NFY 1: bitfury_init_oldbuf: Differ at 1
 [2013-11-20 23:30:30] NFY 1: bitfury_init_oldbuf: Second differ at 2; trying again
 [2013-11-20 23:30:30] mcp2210_set_cfg_gpio: Failed to set current GPIO config
 [2013-11-20 23:30:30] mcp2210_spi_transfer: SPI transfer rejected temporarily (60 bytes remaining)
 [2013-11-20 23:30:30] NFY 1: bitfury_init_oldbuf: Differ at 1
 [2013-11-20 23:30:30] NFY 1: bitfury_init_oldbuf: Second differ at 2; trying again

BTW vs3, you'll need a USB2.0 hub for your pi and it's kinda specific. Great thread regarding that I'll try to dig up a link for.

Most use DLINK DUB-H7 HUBs

Edit to add:

Meh, can't find thread here but here's a link with a list:
http://elinux.org/RPi_Powered_USB_Hubs

[Swimmer63]

So I am trying to get my Asicminer Erupters to work with my Nano Fury.  I am not using a hub right now, just have them all in the PC.
This is what I have for the CONF file that works great with the Nano.
What do I need to do to get it to work with both Nano and Erupters?

      "pool-priority" : "0"
   }
]
,
"api-mcast-port" : "4028",
"api-port" : "4028",
"disable-gpu" : true,
"expiry" : "120",
"expiry-lp" : "3600",
"gpu-dyninterval" : "7",
"log" : "5",
"no-pool-disable" : true,
"no-show-processors" : true,
"no-show-procs" : true,
"no-unicode" : true,
"queue" : "1",
"scan-time" : "60",
"skip-security-checks" : "0",
"submit-stale" : true,
"temp-hysteresis" : "3",
"shares" : "0",
"set-device":["NFY:osc6_bits=54"],
"kernel-path" : "C:\\Program Files\\BFGMiner\\/share/bfgminer"
}

[Taugeran]

So I am trying to get my Asicminer Erupters to work with my Nano Fury.  I am not using a hub right now, just have them all in the PC.
This is what I have for the CONF file that works great with the Nano.
What do I need to do to get it to work with both Nano and Erupters?

      "pool-priority" : "0"
   }
]
,
"api-mcast-port" : "4028",
"api-port" : "4028",
"disable-gpu" : true,
"expiry" : "120",
"expiry-lp" : "3600",
"gpu-dyninterval" : "7",
"log" : "5",
"no-pool-disable" : true,
"no-show-processors" : true,
"no-show-procs" : true,
"no-unicode" : true,
"queue" : "1",
"scan-time" : "60",
"skip-security-checks" : "0",
"submit-stale" : true,
"temp-hysteresis" : "3",
"shares" : "0",
"set-device":["NFY:osc6_bits=54"],
"kernel-path" : "C:\\Program Files\\BFGMiner\\/share/bfgminer"
}

add:

Code:

"scan-serial":["BES:\\\\.\\COMX", BES:\\\\.\\COMY"]

repeat BES:\\\\.\\COMX for as many erupts as you have and change X to the actual com port number (available from printers and devices)



edit: the above method will work if you have a bigpic device as well. if you do not however, then simply -S BES:auto added to the command line or

Code:

"scan-serial":["BES:auto"]

[Taugeran]

Snippet from log file in case anything is interesting

Code:

 [2013-11-20 23:30:30] mcp2210_spi_transfer: SPI transfer rejected temporarily (60 bytes remaining)
 [2013-11-20 23:30:30] mcp2210_spi_transfer: SPI transfer rejected temporarily (60 bytes remaining)
 [2013-11-20 23:30:30] mcp2210_spi_transfer: SPI transfer rejected temporarily (60 bytes remaining)
 [2013-11-20 23:30:30] mcp2210_spi_transfer: SPI transfer rejected temporarily (60 bytes remaining)
 [2013-11-20 23:30:30] mcp2210_spi_transfer: SPI transfer rejected temporarily (60 bytes remaining)
 [2013-11-20 23:30:30] mcp2210_spi_transfer: SPI transfer rejected temporarily (60 bytes remaining)
 [2013-11-20 23:30:30] mcp2210_spi_transfer: SPI transfer rejected temporarily (60 bytes remaining)
 [2013-11-20 23:30:30] mcp2210_spi_transfer: SPI transfer rejected temporarily (60 bytes remaining)
 [2013-11-20 23:30:30] mcp2210_spi_transfer: SPI transfer rejected temporarily (24 bytes remaining)
 [2013-11-20 23:30:30] mcp2210_spi_transfer: SPI transfer rejected temporarily (24 bytes remaining)
 [2013-11-20 23:30:30] mcp2210_spi_transfer: SPI transfer rejected temporarily (60 bytes remaining)
 [2013-11-20 23:30:30] mcp2210_spi_transfer: SPI transfer rejected temporarily (60 bytes remaining)
 [2013-11-20 23:30:30] NFY 1: bitfury_init_oldbuf: Differ at 1
 [2013-11-20 23:30:30] NFY 1: bitfury_init_oldbuf: Second differ at 2; trying again
 [2013-11-20 23:30:30] mcp2210_spi_transfer: SPI transfer rejected temporarily (60 bytes remaining)
 [2013-11-20 23:30:30] NFY 0: bitfury_init_oldbuf: Differ at 4
 [2013-11-20 23:30:30] NFY 0: bitfury_init_oldbuf: Second differ at 5; trying again
 [2013-11-20 23:30:30] mcp2210_spi_transfer: SPI transfer rejected temporarily (60 bytes remaining)
 [2013-11-20 23:30:30] NFY 1: bitfury_init_oldbuf: Differ at 1
 [2013-11-20 23:30:30] NFY 1: bitfury_init_oldbuf: Second differ at 2; trying again
 [2013-11-20 23:30:30] mcp2210_set_cfg_gpio: Failed to set current GPIO config
 [2013-11-20 23:30:30] mcp2210_spi_transfer: SPI transfer rejected temporarily (60 bytes remaining)
 [2013-11-20 23:30:30] NFY 1: bitfury_init_oldbuf: Differ at 1
 [2013-11-20 23:30:30] NFY 1: bitfury_init_oldbuf: Second differ at 2; trying again

BTW vs3, you'll need a USB2.0 hub for your pi and it's kinda specific. Great thread regarding that I'll try to dig up a link for.

Most use DLINK DUB-H7 HUBs

Edit to add:

Meh, can't find thread here but here's a link with a list:
http://elinux.org/RPi_Powered_USB_Hubs

i can't get my raspberry to even recognize the DUB-H7 that i have, but it will recognize regular devices

[RicRock]

i can't get my raspberry to even recognize the DUB-H7 that i have, but it will recognize regular devices

I run 2 DUB-H7's and 2 Rosewill's

What regular device do you mean?

output of lsusb -t

Only one Dlink in there right now:

Code:

pi@PI-MINER ~ $ lsusb -t
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc_otg/1p, 480M
    |__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/3p, 480M
        |__ Port 1: Dev 3, If 0, Class=vend., Driver=smsc95xx, 480M
        |__ Port 2: Dev 4, If 0, Class=vend., Driver=rt2800usb, 480M
        |__ Port 3: Dev 5, If 0, Class=hub, Driver=hub/4p, 480M
            |__ Port 1: Dev 6, If 0, Class=hub, Driver=hub/4p, 480M
                |__ Port 1: Dev 10, If 0, Class=hub, Driver=hub/4p, 480M
                    |__ Port 1: Dev 20, If 0, Class=vend., Driver=cp210x, 12M
                    |__ Port 2: Dev 21, If 0, Class=vend., Driver=cp210x, 12M
                    |__ Port 3: Dev 22, If 0, Class=vend., Driver=cp210x, 12M
                    |__ Port 4: Dev 23, If 0, Class=vend., Driver=cp210x, 12M
                |__ Port 2: Dev 11, If 0, Class=vend., Driver=cp210x, 12M
                |__ Port 3: Dev 12, If 0, Class=vend., Driver=cp210x, 12M
                |__ Port 4: Dev 13, If 0, Class=hub, Driver=hub/4p, 480M
                    |__ Port 1: Dev 24, If 0, Class=vend., Driver=cp210x, 12M
                    |__ Port 2: Dev 25, If 0, Class=comm., Driver=cdc_acm, 12M
                    |__ Port 2: Dev 25, If 1, Class=data, Driver=cdc_acm, 12M
            |__ Port 2: Dev 7, If 0, Class=hub, Driver=hub/4p, 480M
                |__ Port 1: Dev 14, If 0, Class=hub, Driver=hub/4p, 480M
                    |__ Port 1: Dev 26, If 0, Class=vend., Driver=cp210x, 12M
                    |__ Port 2: Dev 27, If 0, Class=vend., Driver=cp210x, 12M
                    |__ Port 3: Dev 28, If 0, Class=vend., Driver=cp210x, 12M
                    |__ Port 4: Dev 29, If 0, Class=vend., Driver=cp210x, 12M
                |__ Port 2: Dev 15, If 0, Class=vend., Driver=cp210x, 12M
                |__ Port 3: Dev 16, If 0, Class=vend., Driver=cp210x, 12M
                |__ Port 4: Dev 17, If 0, Class=hub, Driver=hub/4p, 480M
                    |__ Port 1: Dev 30, If 0, Class=vend., Driver=cp210x, 12M
                    |__ Port 2: Dev 31, If 0, Class=comm., Driver=cdc_acm, 12M
                    |__ Port 2: Dev 31, If 1, Class=data, Driver=cdc_acm, 12M
            |__ Port 3: Dev 8, If 0, Class=hub, Driver=hub/4p, 480M
                |__ Port 1: Dev 18, If 0, Class=hub, Driver=hub/4p, 480M
                    |__ Port 1: Dev 32, If 0, Class=vend., Driver=cp210x, 12M
                    |__ Port 2: Dev 33, If 0, Class=vend., Driver=cp210x, 12M
                |__ Port 2: Dev 19, If 0, Class=vend., Driver=cp210x, 12M
            |__ Port 4: Dev 9, If 0, Class=hub, Driver=hub/4p, 480M

Be's and Blue fury's

[Zich]

i can't get my raspberry to even recognize the DUB-H7 that i have, but it will recognize regular devices

I remember my Pi not recognize DUB-H7 on lower usb port but work fine in upper usb port. This is nut, what is the differences.

Ok, i give up running nanofury on Pi. Just  lets it burn on Windows.

[Taugeran]

i can't get my raspberry to even recognize the DUB-H7 that i have, but it will recognize regular devices

I run 2 DUB-H7's and 2 Rosewill's

What regular device do you mean?

output of lsusb -t

Only one Dlink in there right now:

Code:

pi@PI-MINER ~ $ lsusb -t
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc_otg/1p, 480M
    |__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/3p, 480M
        |__ Port 1: Dev 3, If 0, Class=vend., Driver=smsc95xx, 480M
        |__ Port 2: Dev 4, If 0, Class=vend., Driver=rt2800usb, 480M
        |__ Port 3: Dev 5, If 0, Class=hub, Driver=hub/4p, 480M
            |__ Port 1: Dev 6, If 0, Class=hub, Driver=hub/4p, 480M
                |__ Port 1: Dev 10, If 0, Class=hub, Driver=hub/4p, 480M
                    |__ Port 1: Dev 20, If 0, Class=vend., Driver=cp210x, 12M
                    |__ Port 2: Dev 21, If 0, Class=vend., Driver=cp210x, 12M
                    |__ Port 3: Dev 22, If 0, Class=vend., Driver=cp210x, 12M
                    |__ Port 4: Dev 23, If 0, Class=vend., Driver=cp210x, 12M
                |__ Port 2: Dev 11, If 0, Class=vend., Driver=cp210x, 12M
                |__ Port 3: Dev 12, If 0, Class=vend., Driver=cp210x, 12M
                |__ Port 4: Dev 13, If 0, Class=hub, Driver=hub/4p, 480M
                    |__ Port 1: Dev 24, If 0, Class=vend., Driver=cp210x, 12M
                    |__ Port 2: Dev 25, If 0, Class=comm., Driver=cdc_acm, 12M
                    |__ Port 2: Dev 25, If 1, Class=data, Driver=cdc_acm, 12M
            |__ Port 2: Dev 7, If 0, Class=hub, Driver=hub/4p, 480M
                |__ Port 1: Dev 14, If 0, Class=hub, Driver=hub/4p, 480M
                    |__ Port 1: Dev 26, If 0, Class=vend., Driver=cp210x, 12M
                    |__ Port 2: Dev 27, If 0, Class=vend., Driver=cp210x, 12M
                    |__ Port 3: Dev 28, If 0, Class=vend., Driver=cp210x, 12M
                    |__ Port 4: Dev 29, If 0, Class=vend., Driver=cp210x, 12M
                |__ Port 2: Dev 15, If 0, Class=vend., Driver=cp210x, 12M
                |__ Port 3: Dev 16, If 0, Class=vend., Driver=cp210x, 12M
                |__ Port 4: Dev 17, If 0, Class=hub, Driver=hub/4p, 480M
                    |__ Port 1: Dev 30, If 0, Class=vend., Driver=cp210x, 12M
                    |__ Port 2: Dev 31, If 0, Class=comm., Driver=cdc_acm, 12M
                    |__ Port 2: Dev 31, If 1, Class=data, Driver=cdc_acm, 12M
            |__ Port 3: Dev 8, If 0, Class=hub, Driver=hub/4p, 480M
                |__ Port 1: Dev 18, If 0, Class=hub, Driver=hub/4p, 480M
                    |__ Port 1: Dev 32, If 0, Class=vend., Driver=cp210x, 12M
                    |__ Port 2: Dev 33, If 0, Class=vend., Driver=cp210x, 12M
                |__ Port 2: Dev 19, If 0, Class=vend., Driver=cp210x, 12M
            |__ Port 4: Dev 9, If 0, Class=hub, Driver=hub/4p, 480M

Be's and Blue fury's

Code:

[root@alarmpi ~]# lsusb -t
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc_otg/1p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/3p, 480M
        |__ Port 1: Dev 3, If 0, Class=Vendor Specific Class, Driver=smsc95xx, 480M
[root@alarmpi ~]#

thats with the dub-h7 with a be and 2 NF1 plugged into it. it don't even recognize it top or bottom port. yet windows sees just fine

[RicRock]

thats with the dub-h7 with a be and 2 NF1 plugged into it. it don't even recognize it top or bottom port. yet windows sees just fine

Don't know what to tell you my friend.

Remember, I'm the guy that couldn't get them running.

There are plenty of threads showing the DLINK hubs work on the PI tho.

Nothing plugged into the ports that aren't recognized?

[RicRock]

Code:

[root@alarmpi ~]# lsusb -t
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc_otg/1p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/3p, 480M
        |__ Port 1: Dev 3, If 0, Class=Vendor Specific Class, Driver=smsc95xx, 480M
[root@alarmpi ~]#

thats with the dub-h7 with a be and 2 NF1 plugged into it. it don't even recognize it top or bottom port. yet windows sees just fine

I don't believe it will list "empty" ports if that's what you are expecting.

I suggest you get it running with your BE first then try to add the nano fury's.

Like I said, I was never able to get them running.

[Taugeran]

Code:

[root@alarmpi ~]# lsusb -t
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc_otg/1p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/3p, 480M
        |__ Port 1: Dev 3, If 0, Class=Vendor Specific Class, Driver=smsc95xx, 480M
[root@alarmpi ~]#

thats with the dub-h7 with a be and 2 NF1 plugged into it. it don't even recognize it top or bottom port. yet windows sees just fine

I don't believe it will list "empty" ports if that's what you are expecting.

I suggest you get it running with your BE first then try to add the nano fury's.

Like I said, I was never able to get them running.

i even tried filling the hub with all flash drives and a kb and still none were recognized

i think ive fudged something. 

note this is across 2 different linux OSes

[vs3]

I know a lot of people were asking about Raspberry Pi - I spotted this while browsing around:

Working fine here after hours of trying...  At least I get ~2.3 GH/s out of the Nanofury.

I'm using bfgminer 3.8.0 (latest git version) and all you have to do (after compiling) is to enforce the USB 2.0 low speed mode to make the USB communication stable. Note: this will also limit the network speed of your Raspi!

The slowdown can be achieved by putting dwc_otg.speed=1 into /boot/cmdline.txt. Note: all statements need to be at one line.

See this page for more infomation: http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=53832#sig411106 (the last section at the bottom.

Hopefully that helps!

[prehistoric]

Hi vs3,

I'm trying to pencil mod NF1 v0.6 and I've measured R2=100 Ohm and R3=115 Ohm in 3 NF1s by digital multimeter DT830B. R3 is different from R3=2.4 kOhm you've specified in https://bitcointalk.org/index.php?topic=291456.msg3574768#msg3574768
What could be wrong here?

Taugeran also mentioned R15 and R16 in https://bitcointalk.org/index.php?topic=291456.msg3574726#msg3574726 Could you please point them on the picture as well as measurement points just to be sure that the measurements will be correct?

Thank you.

[Taugeran]

Hi vs3,

I'm trying to pencil mod NF1 v0.6 and I've measured R2=100 Ohm and R3=115 Ohm in 3 NF1s by digital multimeter DT830B. R3 is different from R3=2.4 kOhm you've specified in https://bitcointalk.org/index.php?topic=291456.msg3574768#msg3574768
What could be wrong here?

Taugeran also mentioned R15 and R16 in https://bitcointalk.org/index.php?topic=291456.msg3574726#msg3574726 Could you please point them on the picture as well as measurement points just to be sure that the measurements will be correct?

Thank you.

i attempted a pencil mod by using a pencil across the right side of r3 (2.4kOhm). i could not get the graphite to stick to the side and was unsuccessful in lowering the resistance (increase the voltage). the performance of my unit decreased due to comms errors with bfgminer:(bitfury_init_oldbuf [4 tries]) caused posibly damaged r3 while penciling. 

the unit i tried pencil mod on lost the ability to run higher than 51 or 52 osc6 bits while the untouched unit will run at 54 bits just fine( no comm errors)

if you want to mod the voltage i would recommend purchasing some smd resistors to fit the following calculation:

V = 0.8*(R2+R3)/R3
(and factory settings are R2=100 and R3=2.4k for about 0.833V)

find value of R3(marked 242) that increases voltage to ~0.865 or your preferred target.

resistance across the right side of r3 and left side of r2 at 2k measurement setting is ~0.95 if i rememeber correctly; at work atm :/



tl;dr: ymmv

[prehistoric]

i attempted a pencil mod by using a pencil across the right side of r3 (2.4kOhm). i could not get the graphite to stick to the side and was unsuccessful in lowering the resistance (increase the voltage). the performance of my unit decreased due to comms errors with bfgminer:(bitfury_init_oldbuf [4 tries]) caused posibly damaged r3 while penciling. 

the unit i tried pencil mod on lost the ability to run higher than 51 or 52 osc6 bits while the untouched unit will run at 54 bits just fine( no comm errors)

if you want to mod the voltage i would recommend purchasing some smd resistors to fit the following calculation:

V = 0.8*(R2+R3)/R3
(and factory settings are R2=100 and R3=2.4k for about 0.833V)

find value of R3(marked 242) that increases voltage to ~0.865 or your preferred target.

resistance across the right side of r3 and left side of r2 at 2k measurement setting is ~0.95 if i rememeber correctly; at work atm :/

Thank you, I'll restrain myself to tinker with R3 for now. And thanks for clarification on measuring R2,R3 resistance.
Am I correct that if at 2k measurement multimeter LCD reads 0.95 it means 1.9kOhms?
If go on changing R3 resistance, to calculate resulting V is it correct to measure resistance between left side of R2 and left side of R3 (it is bottom on the picture when USB points right), then divide by resistance of R3, then multiply by 0.8?

[Taugeran]

...
V = 0.8*(R2+R3)/R3
(and factory settings are R2=100 and R3=2.4k for about 0.833V)
...

Thank you, I'll restrain myself to tinker with R3 for now. And thanks for clarification on measuring R2,R3 resistance.
Am I correct that if at 2k measurement multimeter LCD reads 0.95 it means 1.9kOhms?
If go on changing R3 resistance, to calculate resulting V is it correct to measure resistance between left side of R2 and left side of R3 (it is bottom on the picture when USB points right), then divide by resistance of R3, then multiply by 0.8?

sorry for the equation with no explanation. O.o

if you choose to go the route of switching out the 242 resistor (2.4K) you will need to select a new target voltage not greater than 0.9000V
that becomes V in the equation i posted. ill give an example.

stock voltage on NF1 is ~0.8333V
and you want to overvolt to stabilize higher frequencies, so you choose the target 0.8650V
R2 = 100 R3=x



then solve for x.

a quick plug into wolfram gave x= 1230.8

so we would need a 1.23K resistor for R3

here's a list from mouser. i forget the exact dimension of the part so its a mix of 3 sizes

list


and on your question of the resistance reading i would check the spec sheet on your multimeter to be doubly sure. the 2k setting on my reads the same for a NF1 as the 20K setting is for my BPMC BF1 (this is due to the different resistors used); the setting just moves the decimal appropriately.

[vs3]

I had posted that earlier - let me know if it covered the question or if there is any additional info needed.

@vs3

can you elaborate on the req's to pencil mod the NFY similar to the BF1?

if the voltage setup circuits are anything similar: on BF1

rub graphite pencil across R15 until resistance measured across R15 and R16 is ~0.89Kohm

Yes - the procedure is almost identical - I'll repost what I wrote about that (on Marto74's thread) - let me know if that covers it or I missed anything:

Can you give me instructions for pencil mod?

See this image:


R2 and R3 determine the voltage:
V = 0.8*(R2+R3)/R3
(and factory settings are R2=100 and R3=2.4k for about 0.833V)

If you want to increase the voltage you can either increase R2 or decrease R3 (pencil mod decreases resistance).
And to lower the voltage - you can lower R2 or increase R3.

My 2 cents - start by first lowering the voltage. At least that's the safer option

[vs3]

Some more info about running it on Raspberry Pi:

Hello,

could anyone sent me a kind of tutorial how to get the nanofury working on rasberry pi? I dont know much about linux.

Raspian ist still installed, and networkspeed ist reduced like in your messages. But which bfgminer version should I install (link?). What do you mean with "after comiling"

are there any other settings do do? ... I tryed lots of versions but nothing works... A small tutorial would save my next 5 evenings

Greetings from Germany

First you need to install needed library

Code:

1. sudo aptitude update
2. sudo aptitude install libudev-dev libusb-1.0-0-dev libfox-1.6-dev autotools-dev autoconf automake libtool libncurses-dev yasm curl libcurl4-openssl-dev libjansson-dev pkg-config uthash-dev make pkg-config yasm 

Second download HIDAPI from git

Code:

1. git clone git://github.com/signal11/hidapi.git hidapi
2. cd hidapi
3. ./bootstrap
4. ./configure --prefix=/usr
5. make
6. sudo make install 

Third download bfgminer to some directory(in this example is "miner")

Code:

1. mkdir miner
2. cd miner
3. wget http://luke.dashjr.org/programs/bitcoin/files/bfgminer/3.8.1/bfgminer-3.8.1.tbz2
4. tar xvf bfgminer-3.8.1.tbz2
5. cd bfgminer-3.8.1
6. ./configure 
7. make

You can enable or disable some miner while run ./configure bfgminer with this options
Example: ./configure --enable-bfsb --disable-bitforce

Code:

	--disable-avalon        Compile support for Avalon (default enabled)
	--enable-cpumining      Build with cpu mining support(default disabled)
	--enable-opencl         Compile support for OpenCL (default disabled)
	--disable-adl           Build without ADL monitoring (default enabled)
	--disable-bitfury       Compile support for Bitfury (default enabled)
	--enable-bfsb           Compile support for BFSB (default disabled)
	--disable-bigpic        Compile support for Big Picture Mining USB (default enabled)
	--disable-littlefury    Compile support for LittleFury (default enabled)
	--disable-nanofury      Compile support for NanoFury (default enabled)
	--disable-hashbuster    Compile support for HashBuster Nano (default enabled)
	--disable-hashbuster2   Compile support for HashBuster Micro (default if libusb)
	--enable-metabank       Compile support for Metabank (default disabled)
	--disable-bitforce      Compile support for BitForce (default enabled)
	--disable-icarus        Compile support for Icarus (default enabled)
	--disable-klondike      Compile support for Klondike (default enabled)
	--enable-knc            Compile support for KnC (default disabled)
	--disable-modminer      Compile support for ModMiner (default enabled)
	--disable-x6500         Compile support for X6500 (default enabled)
	--disable-ztex          Compile support for ZTEX (default if libusb)
	--enable-scrypt         Compile support for scrypt mining (default disabled)
	--with-system-libblkmaker  Use system libblkmaker rather than bundled one (default disabled)
	--without-sensors       Build with libsensors monitoring (default enabled)
	--without-curses        Compile support for curses TUI (default enabled)
	--without-libmicrohttpd Compile support for libmicrohttpd getwork server (default enabled)
	--without-libevent      Compile support for libevent stratum server (default enabled)
	--without-libusb        Compile using libusb (default enabled)
	--without-libudev       Autodetect FPGAs using libudev (default enabled)

Then change usb speed to usb 1 with text editor nano

Code:

1. sudo nano /boot/cmdline.txt
then add dwc_otg.speed=1 at the end of line

To run bfgminer just go to the directory

Code:

1. cd miner
2. cd bfgminer-3.8.1
3. sudo ./bfgminer

That was the summary i colected from other thread since i am also linux noob 

[Zich]

But sadly after various test, i found that with this setting, i am unable to run cgminer which use to hash HEX16A 
The symptom is suddenly after run cgminer, the network LED on Pi become intermittent.

[Taugeran]

But sadly after various test, i found that with this setting, i am unable to run cgminer which use to hash HEX16A 
The symptom is suddenly after run cgminer, the network LED on Pi become intermittent.

get a BBB

[Zich]

But sadly after various test, i found that with this setting, i am unable to run cgminer which use to hash HEX16A  
The symptom is suddenly after run cgminer, the network LED on Pi become intermittent.

get a BBB

Good idea  

[vs3]

For those with a Mac OS X:

Hi there. I have a How-To up for mining with Ice Fury on Mac OS X:

http://nf1.xgminer.com

Great little devices! 

[segaklon]

I have a problem with one of these, the pc does not detect it and I've tried several and the same, anyone know where the fault.

thanks