[ANN] HEX•FURY 11+Gh/s USB Stick Miner [ IN STOCK UK, EU ] Shipping Worldwide - page 6.

ManeBjorn

legendary

Activity: 1288

Merit: 1004

It is not the HexFury I am sure of that. It runs great on BFG despite the odd reporting.
It has run fine overnight though this time.
I am also running a OneString DIY1 that is running great as well.
I should be able to get the reviews of both done and up later today or by tomorrow morning.
The HexFury is solid and fun. I really like it. I also really like the OneString. Solid units both.

Quote from: LordTheron on March 31, 2014, 07:05:57 AM

Quote from: ManeBjorn on March 30, 2014, 06:58:03 PM

I don't think it is 100% the same. There must be something different somewhere.
On BFGMiner with the current driver the current hash rate is show at half the speed it is running at. On the same hand the effective speed shows up properly.
I have tried it on 2 different systems with the same results.
On cgminer it for the most part shows up properly but drops the pool connections frequently.
I will keep you posted as I finish my tests.
The unit itself runs nice and cool as well as fast. It has been a great miner so far. Once the driver situations are cleared up the skies the limit with this little beast.
I really like it.

Quote from: cscape on March 23, 2014, 11:04:46 AM

Quote from: ZBC3 on March 23, 2014, 10:59:47 AM

I apologize if I missed it, but did you say if it would be supported by cgminer? Where did you see the pricing? I must have looked over it.

The protocol is exactly the same as for the bi*fury devices (and also the same for the One String Miner), so cgminer already supports them.

First post has been updated with prices, by the way.

I'm not sure what is causing problems with bfgminer. It will get resolved soon. As to cgminer, it works flawlessly. I have 32 Hex connected for the last 24 hrs and not gtting any pool disconnections. Are you sure that your pool is not having problems?

LordTheron

full member

Activity: 197

Merit: 100

Quote from: ManeBjorn on March 30, 2014, 06:58:03 PM

I don't think it is 100% the same. There must be something different somewhere.
On BFGMiner with the current driver the current hash rate is show at half the speed it is running at. On the same hand the effective speed shows up properly.
I have tried it on 2 different systems with the same results.
On cgminer it for the most part shows up properly but drops the pool connections frequently.
I will keep you posted as I finish my tests.
The unit itself runs nice and cool as well as fast. It has been a great miner so far. Once the driver situations are cleared up the skies the limit with this little beast.
I really like it.

Quote from: cscape on March 23, 2014, 11:04:46 AM

Quote from: ZBC3 on March 23, 2014, 10:59:47 AM

I apologize if I missed it, but did you say if it would be supported by cgminer? Where did you see the pricing? I must have looked over it.

The protocol is exactly the same as for the bi*fury devices (and also the same for the One String Miner), so cgminer already supports them.

First post has been updated with prices, by the way.

I'm not sure what is causing problems with bfgminer. It will get resolved soon. As to cgminer, it works flawlessly. I have 32 Hex connected for the last 24 hrs and not gtting any pool disconnections. Are you sure that your pool is not having problems?

cscape

sr. member

Activity: 251

Merit: 250

Quote from: -ck on March 31, 2014, 04:32:03 AM

I'm well aware of ways to work around it, but I don't think anyone's using the data so with so much else to work on, unless it's requested I'll just leave it as is.

I was actually thinking that the user interested in having better statistics would volunteer to do the work themselves

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: cscape on March 31, 2014, 12:55:47 AM

If someone wanted to get per-chip statistics, the better way would be to have a dynamic list, which grows automatically when a new chip is mentioned in the results.

Of course, with the number of chips growing into the hundreds, the value of knowing exactly what happens in each individual chip starts to diminish. EDIT: also, measuring these statistics in the driver, with a high difficulty setting, produces very erratic per-chip results, unless you measure over very long times.

I'm well aware of ways to work around it, but I don't think anyone's using the data so with so much else to work on, unless it's requested I'll just leave it as is.

ManeBjorn

legendary

Activity: 1288

Merit: 1004

This is very cool.
The OneString and HexFuries are definitely build to expand.

Quote

Also, the OneStringMiner devices allow a simple serial connection to connect multiple boards through 1 'master' board connected to a USB port (potentially resulting in hundreds of chips). The firmware automatically detects and counts these boards, but this is done in parallel with the USB enumeration/initialization, so the number of chips could increase some time after the miner application request the version string.

cscape

sr. member

Activity: 251

Merit: 250

If someone wanted to get per-chip statistics, the better way would be to have a dynamic list, which grows automatically when a new chip is mentioned in the results.

Of course, with the number of chips growing into the hundreds, the value of knowing exactly what happens in each individual chip starts to diminish. EDIT: also, measuring these statistics in the driver, with a high difficulty setting, produces very erratic per-chip results, unless you measure over very long times.

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

I'll leave it as is then Roll Eyes

Only real concern is trying to write outside the bounds of the array and causing corruption but I think I accounted for the possibility of illegal values already.

cscape

sr. member

Activity: 251

Merit: 250

Quote from: -ck on March 31, 2014, 12:24:54 AM

EDIT: Shouldn't be hard for me to generically change it to as many chips are reported in chips, but I believe some earlier samples/firmware didn't report that so I'll add a workaround.

And some new firmware reports the wrong value Sad

Also, the OneStringMiner devices allow a simple serial connection to connect multiple boards through 1 'master' board connected to a USB port (potentially resulting in hundreds of chips). The firmware automatically detects and counts these boards, but this is done in parallel with the USB enumeration/initialization, so the number of chips could increase some time after the miner application request the version string. In theory, the user could even dynamically add some extra boards after the device has been running (although this would not be a common procedure).

ManeBjorn

legendary

Activity: 1288

Merit: 1004

It could be as it definitely reports oddly.
It's still a fun miner though. There is so much room to improve it's performance with low overhead.

Quote from: cscape on March 30, 2014, 11:50:34 PM

Quote from: ManeBjorn on March 30, 2014, 06:58:03 PM

I don't think it is 100% the same. There must be something different somewhere.
On BFGMiner with the current driver the current hash rate is show at half the speed it is running at. On the same hand the effective speed shows up properly.
I have tried it on 2 different systems with the same results.

Maybe the problem is that the firmware version string still reports "2 chips", but when it submits results, it provides a chip number 0 through 5. That's the only thing I can think of that would be different between the devices.

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: cscape on March 30, 2014, 11:47:34 PM

Quote from: -ck on March 30, 2014, 05:03:14 PM

Quote from: cscape on March 23, 2014, 11:04:46 AM

The protocol is exactly the same as for the bi*fury devices (and also the same for the One String Miner), so cgminer already supports them.

The code assumes 2 job queues so I assume you worked within that framework despite the extra chips?

Not sure where the 2 job queues come from, but the firmware internally uses a single queue with room for 4 jobs. That's the same on bi-fury and hex-fury. The only difference is that the hex-fury jobs are processed faster because there are more chips, but this should be transparent for the driver.

I wrote the driver for BXF aka Bi*fury at the time and while it sends enough work based on the request for more work, it stores data in its API assuming 2 chips exist because that's all the original devices had. As I said earlier, it probably only affects the data that's shown in the API. A string of invalid chip number messages in verbose mode and lack of debug support for the extra chips is likely the only consequence, but I don't know how many people ever looked at the API output of these devices which I originally added to aid debugging of which chip was doing what:

Code:

[STATS3] =>
(
   [STATS] => 3
   [ID] => BXF0
   [Elapsed] => 79099
   [Calls] => 0
   [Wait] => 0.000000
   [Max] => 0.000000
   [Min] => 99999999.000000
   [Version] => 1.2
   [Revision] => 1
   [Chips] => 2
   [NonceRate] => 0.663417
   [NoMatchingWork] => 0
   [Temperature] => 48.400000
   [Max DeciTemp] => 525
   [Clock] => 54
   [Core0 hwerror] => 598
   [Core1 hwerror] => 142
   [Core0 jobs] => 8458
   [Core1 jobs] => 8227
   [Core0 submits] => 5239
   [Core1 submits] => 5581
   [USB Pipe] => 0
   [USB Delay] => r0 0.000000 w0 0.000000
   [USB tmo] => 46161 0
)

EDIT: Shouldn't be hard for me to generically change it to as many chips are reported in chips, but I believe some earlier samples/firmware didn't report that so I'll add a workaround.

cscape

sr. member

Activity: 251

Merit: 250

Quote from: ManeBjorn on March 30, 2014, 06:58:03 PM

I don't think it is 100% the same. There must be something different somewhere.
On BFGMiner with the current driver the current hash rate is show at half the speed it is running at. On the same hand the effective speed shows up properly.
I have tried it on 2 different systems with the same results.

Maybe the problem is that the firmware version string still reports "2 chips", but when it submits results, it provides a chip number 0 through 5. That's the only thing I can think of that would be different between the devices.

cscape

sr. member

Activity: 251

Merit: 250

Quote from: -ck on March 30, 2014, 05:03:14 PM

Quote from: cscape on March 23, 2014, 11:04:46 AM

The protocol is exactly the same as for the bi*fury devices (and also the same for the One String Miner), so cgminer already supports them.

The code assumes 2 job queues so I assume you worked within that framework despite the extra chips?

Not sure where the 2 job queues come from, but the firmware internally uses a single queue with room for 4 jobs. That's the same on bi-fury and hex-fury. The only difference is that the hex-fury jobs are processed faster because there are more chips, but this should be transparent for the driver.

For the OneStringMiner version with the serial bus, the job queue has been extended to 16 (but we're still experimenting with that), because it supports a total of 16 boards with 15 chips each, so it goes through the work a lot faster.

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: ManeBjorn on March 30, 2014, 06:58:03 PM

On cgminer it for the most part shows up properly but drops the pool connections frequently.

That doesn't make sense if you're implying the driver somehow causes this. What do you mean drops the pool connections? Most stratum connections on cgminer stay up for weeks when pools are stable.

ManeBjorn

legendary

Activity: 1288

Merit: 1004

I don't think it is 100% the same. There must be something different somewhere.
On BFGMiner with the current driver the current hash rate is show at half the speed it is running at. On the same hand the effective speed shows up properly.
I have tried it on 2 different systems with the same results.
On cgminer it for the most part shows up properly but drops the pool connections frequently.
I will keep you posted as I finish my tests.
The unit itself runs nice and cool as well as fast. It has been a great miner so far. Once the driver situations are cleared up the skies the limit with this little beast.
I really like it.

Quote from: cscape on March 23, 2014, 11:04:46 AM

Quote from: ZBC3 on March 23, 2014, 10:59:47 AM

I apologize if I missed it, but did you say if it would be supported by cgminer? Where did you see the pricing? I must have looked over it.

The protocol is exactly the same as for the bi*fury devices (and also the same for the One String Miner), so cgminer already supports them.

First post has been updated with prices, by the way.

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: cscape on March 23, 2014, 11:04:46 AM

The protocol is exactly the same as for the bi*fury devices (and also the same for the One String Miner), so cgminer already supports them.

The code assumes 2 job queues so I assume you worked within that framework despite the extra chips?

ManeBjorn

legendary

Activity: 1288

Merit: 1004

I see now.
Could be worse remember at least you are able to make sales still in the meantime.

Quote from: LordTheron on March 30, 2014, 07:00:03 AM

Quote from: ManeBjorn on March 29, 2014, 01:52:59 PM

Are you able to use Coinbase? They have a simple a quick cart setup for BTC payments on websites.
I hope it helps.

Quote from: LordTheron on March 28, 2014, 05:52:08 PM

Hi Guys,

Review units have been delivered. Independent reviews will follow soon

Also I'm going to update the webstore at the weekend with some special offers so please check the thread for update.

I still can't take BTC payments through my webstore Embarrassed

so if you want to pay in BTC then please PM me with your order and I will send you payment details. It will get automated as soon as I find a solution.

Cheers,
LordTheron

Yes I've looked at it and have merchant account but it doesn't integrate with my cart software, and that is the problem. I can send payment requests directly from Coinbase but all has to be processes manually. The cart I'm using now is very nice but no one is making BTC plugins so best option is to move my store to a new cart. I got one couple days ago Wink

and rebuilding my store as I write this. Old webstore is working as it was and will be until new store is fully setup and domain repointed. All account will be migrated and all users will be notified. I hope to have it fully up and running by the end of next week.

LordTheron

full member

Activity: 197

Merit: 100

Quote from: nwoolls on March 29, 2014, 03:50:20 PM

Is it possible to get a single sample so that I can write a proper driver for BFGMiner? It sounds like this is currently recognized as Bi*Fury and shows the hashrate wrong.

Thanks in advance for any support Grin

Dev unit will be shipped on Monday Wink

LordTheron

full member

Activity: 197

Merit: 100

Quote from: ManeBjorn on March 29, 2014, 01:52:59 PM

Are you able to use Coinbase? They have a simple a quick cart setup for BTC payments on websites.
I hope it helps.

Quote from: LordTheron on March 28, 2014, 05:52:08 PM

Hi Guys,

Review units have been delivered. Independent reviews will follow soon

Also I'm going to update the webstore at the weekend with some special offers so please check the thread for update.

I still can't take BTC payments through my webstore Embarrassed

so if you want to pay in BTC then please PM me with your order and I will send you payment details. It will get automated as soon as I find a solution.

Cheers,
LordTheron

Yes I've looked at it and have merchant account but it doesn't integrate with my cart software, and that is the problem. I can send payment requests directly from Coinbase but all has to be processes manually. The cart I'm using now is very nice but no one is making BTC plugins so best option is to move my store to a new cart. I got one couple days ago Wink

and rebuilding my store as I write this. Old webstore is working as it was and will be until new store is fully setup and domain repointed. All account will be migrated and all users will be notified. I hope to have it fully up and running by the end of next week.

nwoolls

hero member

Activity: 840

Merit: 1002

Is it possible to get a single sample so that I can write a proper driver for BFGMiner? It sounds like this is currently recognized as Bi*Fury and shows the hashrate wrong.

Thanks in advance for any support Grin

ManeBjorn

legendary

Activity: 1288

Merit: 1004

Are you able to use Coinbase? They have a simple a quick cart setup for BTC payments on websites.
I hope it helps.

Quote from: LordTheron on March 28, 2014, 05:52:08 PM

Hi Guys,

Review units have been delivered. Independent reviews will follow soon

Also I'm going to update the webstore at the weekend with some special offers so please check the thread for update.

I still can't take BTC payments through my webstore Embarrassed

so if you want to pay in BTC then please PM me with your order and I will send you payment details. It will get automated as soon as I find a solution.

Cheers,
LordTheron

Topic: [ANN] HEX•FURY 11+Gh/s USB Stick Miner [ IN STOCK UK, EU ] Shipping Worldwide - page 6. (Read 36187 times)