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

[clarkey2013]

link to site doesn't work

[1715140144]

1715140144

[1715140144]

1715140144

[LordTheron]

link to site doesn't work

What error do you get?

[ptr727]

PayPal does not work:

The seller accepts encrypted website payments only. You cannot pay the seller through un-encrypted buttons. Please contact your seller for more details.

[LordTheron]

PayPal does not work:

The seller accepts encrypted website payments only. You cannot pay the seller through un-encrypted buttons. Please contact your seller for more details.

Let me check that quickly and I'll get back to you shortly.

[judypug1956]

Hey Guys can this miner mine other coins than BTC? Is it SHA-256 only?

I do the maths for ROI at the moment mining BTC doesn't look good...

That's not the point of these miners.  As diff goes up people up graded from block eruptors to bitfury/ants.... bi fury now here is the hexfury. More ghs by swapping out usb miners. Its simple/cheap/low power usage. I started mining feathercoins bought a few ant u1s then saved and bought an ant s1

these are bait to get someone to join the coin gang so to speak.  you really need to offer a 'special' designer hub with these. 

[LordTheron]

PayPal does not work:

The seller accepts encrypted website payments only. You cannot pay the seller through un-encrypted buttons. Please contact your seller for more details.

That should work now so please try again and let me know if you have any problems.

[dogie]

Very cool.
Can I put a link to it in my article for new users to have a quick link?

Dogie's comprehensive C-Scape HexFury USB setup guide is up!

Sure There's a prettier version now up at dogiecoin.com.

[dogie]

That is good news.
Thanks for the fast work on that.
 

The new version of cgminer also allows you to specify the bits on the command line as a complement to your overclocking attempts.

Code:

--bxf-bits <arg>    Set max BXF/HXF bits for overclocking (default: 54)

Wasn't something similar already there for the bifuries? How different is this? Isn't default 50 for them?

[-ck]

That is good news.
Thanks for the fast work on that.
 

The new version of cgminer also allows you to specify the bits on the command line as a complement to your overclocking attempts.

Code:

--bxf-bits <arg>    Set max BXF/HXF bits for overclocking (default: 54)

Wasn't something similar already there for the bifuries? How different is this? Isn't default 50 for them?

No, the bifuries only had target temperature control and were always set to a maximum of 54. This allows you to set the maximum now in concert with the target temperature control. There are a number of different bitfury chip based usb devices supported in cgminer and they all have different clocking command line options.

[ManeBjorn]

Excellent.
I will add that there.
Great guide site by the way.   

Very cool.
Can I put a link to it in my article for new users to have a quick link?

Dogie's comprehensive C-Scape HexFury USB setup guide is up!

Sure There's a prettier version now up at dogiecoin.com.

[-ck]

I received one of these devices courtesy of LordTheron, thanks!

I've committed some changes to cgminer master git to detect the number of active chips on the fly. It will now change to hexfury while running even if it reports the wrong number of chips to start with (this one reports 5).

Display output:

Code:

 22: HXF 2       :  47.7C                  | 10.49G / 10.19Gh/s WU:  146.6/m

API output:

Code:

[STATS22] =>
(
   [STATS] => 22
   [ID] => HXF2
   [Elapsed] => 206276
   [Calls] => 0
   [Wait] => 0.000000
   [Max] => 0.000000
   [Min] => 99999999.000000
   [Version] => 1.2
   [Revision] => 1
   [Chips] => 5
   [NonceRate] => 1.353960
   [NoMatchingWork] => 0
   [Temperature] => 45.000000
   [Max DeciTemp] => 451
   [Clock] => 54
   [Core0 hwerror] => 4
   [Core0 jobs] => 137
   [Core0 submits] => 98
   [Core1 hwerror] => 7
   [Core1 jobs] => 137
   [Core1 submits] => 92
   [Core2 hwerror] => 2
   [Core2 jobs] => 134
   [Core2 submits] => 84
   [Core3 hwerror] => 5
   [Core3 jobs] => 133
   [Core3 submits] => 93
   [Core4 hwerror] => 0
   [Core4 jobs] => 133
   [Core4 submits] => 96
   [USB Pipe] => 0
   [USB Delay] => r0 0.000000 w0 0.000000
   [USB tmo] => 1989 0
)

EDIT: Actually extended results only ever seem to indicate 5 chips as well.

Average after 24 hours: 10.47GH

[LordTheron]

Average after 24 hours: 10.47GH

What hub are you running it from? I only see this on hubs below 2A or cgminer 4.2.3. If you have min 2A hub you should get around 12.5GH even over 24hrs. Just kicked off 24 hrs test  to see what I get on my hubs. Also why are you getting HW errors on cores? I get none (maybe 1) without OC.

I have been testing different versions of cgminer and I found that 4.01 works almost flawlessly. On 4.2.3 I get usb errors and random crashes, and slower speed. Any idea why 4.0.1 works so well but not the new version?

[-ck]

Average after 24 hours: 10.47GH

What hub are you running it from? I only see this on hubs below 2A or cgminer 4.2.3. If you have min 2A hub you should get around 12.5GH even over 24hrs. Just kicked off 24 hrs test  to see what I get on my hubs. Also why are you getting HW errors on cores? I get none (maybe 1) without OC.

I have been testing different versions of cgminer and I found that 4.01 works almost flawlessly. On 4.2.3 I get usb errors and random crashes, and slower speed. Any idea why 4.0.1 works so well but not the new version?

Probably not enough power then. Does it only initialise 5 chips if it can't power up all 6?

The usual reason for an older version working better would be: sheer coincidence and nothing to do with cgminer. Though of course any bug is possible, however I'm not seeing the instability you speak of. The only change in the bxf driver between those versions was making bxf bits configurable on 4.2.3. What OS are you running it on? Are you giving it any extra options, bxf or icarus?

[dogie]

Probably not enough power then. Does it only initialise 5 chips if it can't power up all 6?

The usual reason for an older version working better would be: sheer coincidence and nothing to do with cgminer. Though of course any bug is possible, however I'm not seeing the instability you speak of. The only change in the bxf driver between those versions was making bxf bits configurable on 4.2.3. What OS are you running it on? Are you giving it any extra options, bxf or icarus?

Probably is the power. I've given my hex 6A and its rock solid for hours at ~13 (stock speed).

[LordTheron]

Average after 24 hours: 10.47GH

What hub are you running it from? I only see this on hubs below 2A or cgminer 4.2.3. If you have min 2A hub you should get around 12.5GH even over 24hrs. Just kicked off 24 hrs test  to see what I get on my hubs. Also why are you getting HW errors on cores? I get none (maybe 1) without OC.

I have been testing different versions of cgminer and I found that 4.01 works almost flawlessly. On 4.2.3 I get usb errors and random crashes, and slower speed. Any idea why 4.0.1 works so well but not the new version?

Probably not enough power then. Does it only initialise 5 chips if it can't power up all 6?

The usual reason for an older version working better would be: sheer coincidence and nothing to do with cgminer. Though of course any bug is possible, however I'm not seeing the instability you speak of. The only change in the bxf driver between those versions was making bxf bits configurable on 4.2.3. What OS are you running it on? Are you giving it any extra options, bxf or icarus?

I'm not sure about initializing chips so I need to ask c-scape. If after couple of minutes your speed is below 12gh usually it means not enough power. Been running couple  sticks since yesterday and both are just over 12GH.

Im on win7 64, no extra options. No crash since yesterday with 2 devices, and 2 crashes on xp machine with 37 devices.  When I enable bxf bits over 54 my performance is doping drastically. I'm back on 4.01 with no options, and its running sweet at 12.5gh rock solid. not sure why is that but for now im goanna stick with 4.0.1 as it seems to work best for me.

[-ck]

I'm not sure about initializing chips so I need to ask c-scape. If after couple of minutes your speed is below 12gh usually it means not enough power. Been running couple  sticks since yesterday and both are just over 12GH.

Im on win7 64, no extra options. No crash since yesterday with 2 devices, and 2 crashes on xp machine with 37 devices.  When I enable bxf bits over 54 my performance is doping drastically. I'm back on 4.01 with no options, and its running sweet at 12.5gh rock solid. not sure why is that but for now im goanna stick with 4.0.1 as it seems to work best for me.

XP is an interesting variable in the equation. If it's on windows, would it be too much to ask to try a debug version using the instructions here?

http://ck.kolivas.org/apps/cgminer/debug/

[Pazuzo]

This webpage is not available 

[ManeBjorn]

I was just on there it worked great for me.

This webpage is not available 

[casinocoin]

So you charge $198 for the gridseed I wont revel the actual price.
300 khs + 8ghs
or
11.25

11gh stick is $192

Why would anyone choose the usb stick over the gridseed?

[TheRealSteve]

Why would anyone choose the usb stick over the gridseed?

Re-read thread - this has been covered several times.