NanoFury Project - Open Source Design

[TheRealSteve]

I did not solder these pads since there is not going to be placed a component anyway.
I don't see a point in soldering those, the are already conducting.

That's in the v0.7 change - basically, the MCP2210 USB bridge was difficult to source in the package used in v0.6 and earlier, so he added a footprint for an alternative package type.  If you look closely at a board/design file, you'll see that the pads just connect straight to the alternate one.

Edit: What he said - again.
I swear this used to tell you somebody else posted while you were editing - what happened to that?

[1713963067]

1713963067

[1713963067]

1713963067

[1713963067]

1713963067

[1713963067]

1713963067

[mikerbiker6]

Allright, I thought that was the case.
It is compatible with 2 types of MCP2210 sizes.

The MCP2210 is probably the issue, I will try and fix it tomorrow I think.
As you may have noticed I am a total noob at this and it is mostly trial and error for me haha.
Placing solder paste on the board is a total disaster without a stencil.
The paste is not sticking to the board, so I looked it up on the internet and my solder paste is probably dried out.
I also read that you can dilute it with some flux, maybe give that a try.
( flux are 2 different things apparently, the watery stuff and the fat yellow goo)

[Taugeran]

Allright, I thought that was the case.
It is compatible with 2 types of MCP2210 sizes.

The MCP2210 is probably the issue, I will try and fix it tomorrow I think.
As you may have noticed I am a total noob at this and it is mostly trial and error for me haha.
Placing solder paste on the board is a total disaster without a stencil.
The paste is not sticking to the board, so I looked it up on the internet and my solder paste is probably dried out.
I also read that you can dilute it with some flux, maybe give that a try.
( flux are 2 different things apparently, the watery stuff and the fat yellow goo)

I were to order a stencil, they ask you too upload some files in zip folder.
If this is just a picture(png/jpeg), how can they know what the actual size is.
Since it has to be printed in exactly the right size.

where are you getting the stencil from? and they should be asking for a gerber file of the top cream layer

[max337]

The problem is the bitfury chip, some bridges have formed.
What do you think is best, use a soldering iron to remove the bridges?

Solder wick, or re-do (chipquick is some nice stuff for that).

http://www.theledart.com/blog/archives/1301

+1 :-)

Solder wick is your best friend!
And an old fashion toaster oven might be your second best one


Also take a look at this video:
https://www.youtube.com/watch?v=c_Qt5CtUlqY
(the interesting part starts after 3:30)

Also, I've been using SMT stencils for majority of my work and that's how I've been making my prototypes.
Here is how I did mine: http://imgur.com/a/5hXU4

Hi vs3,

speaking of your toster oven: Do you just use an old oven or did you modify the oven too?
I'm building one for my self and didn't see on your pictures any thermocouples or something like this, how do you control the temperature?

Thank you and best regards,
max

[vs3]

The problem is the bitfury chip, some bridges have formed.
What do you think is best, use a soldering iron to remove the bridges?

Solder wick, or re-do (chipquick is some nice stuff for that).

http://www.theledart.com/blog/archives/1301

+1 :-)

Solder wick is your best friend!
And an old fashion toaster oven might be your second best one


Also take a look at this video:
https://www.youtube.com/watch?v=c_Qt5CtUlqY
(the interesting part starts after 3:30)

Also, I've been using SMT stencils for majority of my work and that's how I've been making my prototypes.
Here is how I did mine: http://imgur.com/a/5hXU4

Hi vs3,

speaking of your toster oven: Do you just use an old oven or did you modify the oven too?
I'm building one for my self and didn't see on your pictures any thermocouples or something like this, how do you control the temperature?

Thank you and best regards,
max

It happened to be on sale (for $20) so it was a brand new one
No mods whatsoever.

It has a temperature dial - which is way off but it worked for me.

- preheat: dial at 150C (which is closer to 180C), leave it there for 5min
- melt: dial 200-220C (you'll have to experiment and find out at what temp the solder starts melting - add 20C on top of that)
- measure 1min from the moment it starts melting, then unplug oven from outlet, open door and let it cool

[mikerbiker6]

Hmm, getting kind of annoying.

I Didn't find anything that was wrong so I soldered a whole new nanofury.
It looks identical to the old one but I am seeing some improvements in soldering. No bridges as far as I can see

But unfortunattely the miner is not detected by windows/raspberry.
I am hearing no sound when plugging it in, and led is not on.( I don't know if the led should be on).

[Taugeran]

Hmm, getting kind of annoying.

I Didn't find anything that was wrong so I soldered a whole new nanofury.
It looks identical to the old one but I am seeing some improvements in soldering. No bridges as far as I can see

But unfortunattely the miner is not detected by windows/raspberry.
I am hearing no sound when plugging it in, and led is not on.( I don't know if the led should be on).

Led is not normally on. Until software is running

[-ck]

I've added support for NF2 and NF6 into cgminer git master branch. I'm not getting much love out of the NF6 just yet but they may well need so much power that even a regular USB3 port is not enough. The NF2s are behaving very nicely. This is at --nfu-bits 54:

Code:

 14: NF2 00001099:                         | 4.670G / 4.655Gh/s WU:    65.2/m
 23: NF2 00000753:                         | 4.447G / 4.509Gh/s WU:    63.6/m

[simoncc]

I've added support for NF2 and NF6 into cgminer git master branch. I'm not getting much love out of the NF6 just yet but they may well need so much power that even a regular USB3 port is not enough. The NF2s are behaving very nicely. This is at --nfu-bits 54:

Code:

 14: NF2 00001099:                         | 4.670G / 4.655Gh/s WU:    65.2/m
 23: NF2 00000753:                         | 4.447G / 4.509Gh/s WU:    63.6/m

NFU??

[-ck]

I've added support for NF2 and NF6 into cgminer git master branch. I'm not getting much love out of the NF6 just yet but they may well need so much power that even a regular USB3 port is not enough. The NF2s are behaving very nicely. This is at --nfu-bits 54:

Code:

 14: NF2 00001099:                         | 4.670G / 4.655Gh/s WU:    65.2/m
 23: NF2 00000753:                         | 4.447G / 4.509Gh/s WU:    63.6/m

NFU??

Is that a question, statement, exasperation, disgust, or what?

[vs3]

I've added support for NF2 and NF6 into cgminer git master branch. I'm not getting much love out of the NF6 just yet but they may well need so much power that even a regular USB3 port is not enough. The NF2s are behaving very nicely. This is at --nfu-bits 54:

Code:

 14: NF2 00001099:                         | 4.670G / 4.655Gh/s WU:    65.2/m
 23: NF2 00000753:                         | 4.447G / 4.509Gh/s WU:    63.6/m

NFU??

Is that a question, statement, exasperation, disgust, or what?

Heh Fun with abbreviations!

Con - I suspect he wasn't sure what the "--nfu-bits 54" part meant - which is the osc6 bits, and the "nfu..." prefix is what is used in the source code - e.g. as in this line:
mcp->value.pin[NFU_PIN_PWR_EN0] = MCP2210_GPIO_PIN_LOW;

you would see also this in the source code:

/* Identify number of chips, and use it in device name if it can fit
* into 3 chars, otherwise use generic NFU name. */
val = sscanf(bitfury->usbdev->prod_string, "NanoFury NF%u ", &info->chips);

[simoncc]

I've added support for NF2 and NF6 into cgminer git master branch. I'm not getting much love out of the NF6 just yet but they may well need so much power that even a regular USB3 port is not enough. The NF2s are behaving very nicely. This is at --nfu-bits 54:

Code:

 14: NF2 00001099:                         | 4.670G / 4.655Gh/s WU:    65.2/m
 23: NF2 00000753:                         | 4.447G / 4.509Gh/s WU:    63.6/m

NFU??

Is that a question, statement, exasperation, disgust, or what?

I meant the identity was changed. that's great. not for NF1 only, but for MCP2210 based devices... great thing

[Killerloop]

This board hashes at 4.4-4.6 GHs with 5W consumption?

[mikerbiker6]

I think it is unlikely, but suppose both my MCP2210's are faulty, how could I measure this?

[Dexter770221]

....
you would see also this in the source code:

/* Identify number of chips, and use it in device name if it can fit
* into 3 chars, otherwise use generic NFU name. */
val = sscanf(bitfury->usbdev->prod_string, "NanoFury NF%u ", &info->chips);

In what file? I get 0 results when try to find in cgminer-4.3.3 repository.

[vs3]

....
you would see also this in the source code:

/* Identify number of chips, and use it in device name if it can fit
* into 3 chars, otherwise use generic NFU name. */
val = sscanf(bitfury->usbdev->prod_string, "NanoFury NF%u ", &info->chips);

In what file? I get 0 results when try to find in cgminer-4.3.3 repository.

https://github.com/ckolivas/cgminer/search?q=generic+NFU+name&ref=cmdform

[Dexter770221]

....
you would see also this in the source code:

/* Identify number of chips, and use it in device name if it can fit
* into 3 chars, otherwise use generic NFU name. */
val = sscanf(bitfury->usbdev->prod_string, "NanoFury NF%u ", &info->chips);

In what file? I get 0 results when try to find in cgminer-4.3.3 repository.

https://github.com/ckolivas/cgminer/search?q=generic+NFU+name&ref=cmdform

Looks like those are different versions. I downloded 4.3.3 bz2 package from here: http://ck.kolivas.org/apps/cgminer/ and in bitfury driver.c at line 438 I have this:

Code:

if (opt_debug) {
		struct gpio_pin gp;

		mcp2210_get_gpio_pindirs(bitfury, &gp);

EDIT: no occurence of "generic NFU name" in any file... Searched by notepad++ in all files...

[simoncc]

....
you would see also this in the source code:

/* Identify number of chips, and use it in device name if it can fit
* into 3 chars, otherwise use generic NFU name. */
val = sscanf(bitfury->usbdev->prod_string, "NanoFury NF%u ", &info->chips);

In what file? I get 0 results when try to find in cgminer-4.3.3 repository.

https://github.com/ckolivas/cgminer/search?q=generic+NFU+name&ref=cmdform

Looks like those are different versions. I downloded 4.3.3 bz2 package from here: http://ck.kolivas.org/apps/cgminer/ and in bitfury driver.c at line 438 I have this:

Code:

if (opt_debug) {
		struct gpio_pin gp;

		mcp2210_get_gpio_pindirs(bitfury, &gp);

EDIT: no occurence of "generic NFU name" in any file... Searched by notepad++ in all files...

It's just updated hours ago. I guess it's not ready for next rev. package. You should go to github to get the latest source.

[-ck]

EDIT: no occurence of "generic NFU name" in any file... Searched by notepad++ in all files...

It's just updated hours ago. I guess it's not ready for next rev. package. You should go to github to get the latest source.

I've added support for NF2 and NF6 into cgminer git master branch.

[Dexter770221]

EDIT: no occurence of "generic NFU name" in any file... Searched by notepad++ in all files...

It's just updated hours ago. I guess it's not ready for next rev. package. You should go to github to get the latest source.

I've added support for NF2 and NF6 into cgminer git master branch.

Didn't notice that sentence before. THX