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

bigbeninlondon

hero member

Activity: 742

Merit: 500

Quote from: Luke-Jr on November 10, 2013, 01:24:59 PM

Quote from: bigbeninlondon on November 10, 2013, 11:59:19 AM

Can these mine in conjunction with Block Erupters?

Yes, I've been doing just that.

Quote from: bigbeninlondon on November 10, 2013, 11:59:19 AM

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.

RicRock

sr. member

Activity: 290

Merit: 250

If someone that has them working can try them in a USB 2.0 hub that would be awesome.

Luke-Jr

legendary

Activity: 2576

Merit: 1186

Quote from: bigbeninlondon on November 10, 2013, 11:59:19 AM

Can these mine in conjunction with Block Erupters?

Yes, I've been doing just that.

Quote from: bigbeninlondon on November 10, 2013, 11:59:19 AM

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.

bigbeninlondon

hero member

Activity: 742

Merit: 500

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?

RicRock

sr. member

Activity: 290

Merit: 250

Quote from: vs3 on November 10, 2013, 05:47:29 AM

Quote from: RicRock on November 10, 2013, 12:58:48 AM

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.

vs3

hero member

Activity: 622

Merit: 500

Quote from: RicRock on November 10, 2013, 12:58:48 AM

Quote from: Luke-Jr on November 10, 2013, 12:40:14 AM

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

sr. member

Activity: 290

Merit: 250

Quote from: Luke-Jr on November 10, 2013, 12:40:14 AM

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

RicRock

sr. member

Activity: 290

Merit: 250

Quote from: Luke-Jr on November 10, 2013, 12:40:14 AM

I wonder if they're not getting enough power?

one sec... will test quick

Luke-Jr

legendary

Activity: 2576

Merit: 1186

I wonder if they're not getting enough power?

RicRock

sr. member

Activity: 290

Merit: 250

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

legendary

Activity: 2576

Merit: 1186

The 248 suggests it was in the middle of a SPI transfer at some point.
Have you tried power cycling the NF?

RicRock

sr. member

Activity: 290

Merit: 250

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

RicRock

sr. member

Activity: 290

Merit: 250

Quote from: Luke-Jr on November 09, 2013, 11:46:34 PM

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.

Luke-Jr

legendary

Activity: 2576

Merit: 1186

Quote from: RicRock on November 09, 2013, 11:32:01 PM

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.

Quote from: RicRock on November 09, 2013, 11:32:01 PM

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

sr. member

Activity: 290

Merit: 250

Quote from: vs3 on November 09, 2013, 11:29:47 PM

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?

vs3

hero member

Activity: 622

Merit: 500

Quote from: RicRock on November 09, 2013, 11:13:57 PM

Quote from: Luke-Jr on October 16, 2013, 08:07:43 PM

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:

Quote from: vs3 on November 06, 2013, 04:42:21 AM

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

sr. member

Activity: 290

Merit: 250

Quote from: Luke-Jr on October 16, 2013, 08:07:43 PM

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?

RicRock

sr. member

Activity: 290

Merit: 250

Quote from: Luke-Jr on November 09, 2013, 10:40:47 PM

Quote from: RicRock on November 09, 2013, 10:22:43 PM

Quote from: Luke-Jr on November 09, 2013, 09:53:17 PM

Quote from: RicRock on November 09, 2013, 09:43:32 PM

Quote from: Taugeran on November 09, 2013, 08:35:13 PM

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://bitcointalksearch.org/topic/m.3352995

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.

Luke-Jr

legendary

Activity: 2576

Merit: 1186

Quote from: RicRock on November 09, 2013, 10:22:43 PM

Quote from: Luke-Jr on November 09, 2013, 09:53:17 PM

Quote from: RicRock on November 09, 2013, 09:43:32 PM

Quote from: Taugeran on November 09, 2013, 08:35:13 PM

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://bitcointalksearch.org/topic/m.3352995

RicRock

sr. member

Activity: 290

Merit: 250

Quote from: Luke-Jr on November 09, 2013, 09:53:17 PM

Quote from: RicRock on November 09, 2013, 09:43:32 PM

Quote from: Taugeran on November 09, 2013, 08:35:13 PM

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.

Topic: [CLOSED] NanoFury NF1 USB stick - Group Buy + Product Assembly - page 5. (Read 74360 times)