Topic: Bitminter client (Windows/Linux/Mac) - page 24. (Read 654946 times)

Try having just the blue fury plugged in. Before you start the program press the rst button near the USB port. Wait for it to go dark red and then press start on bitminter.

Nice work Doc,

But where do we get drivers for the BlueFury?

EDIT: Ok, so I used the bf1.inf found in the bfgminer build. Now BitMinter detects my device but has the following error
And then the probing appears to just stop (only a few devices show up)

I am using both BE's and BF's, I have heard other miners have an issue with that, is that also the case with BitMinter?
If so, what is the solution? surely I am not forced to run 2 machines?

EDIT EDIT: I have tried with just the BlueFury plugged in, it still has the timeout error

If it isn't actually working the led should go a solid red.

BitMinter client v1.5.0beta1 is ready for testing.

New:

• Added support for Big Picture Mining BF1 (Red/Blue Fury)

Please check it out:


Please test whether it runs ok with Red/Blue Fury combined with BFL and/or ASICMiner USB units.

Known issue: doesn't handle it well if you disconnect the device while mining. Working on this.

These devices report a lot of results that are wrong. I'm not sure yet how to best handle that. Right now it looks a little crazy with all those bombs. I guess I could always show zero errors. But what if the device actually isn't working?

Extra power seemed to have done the trick. The D-Link doesn't seem to provide enough power for six erupter.

Thank you.

Congrats Thanks for describing what fixed it for you.


Most likely the erupters don't get enough power. Did you try plugging one or two of them directly in the computer, with the rest on the hub?

Useful advice: https://bitcointalksearch.org/topic/m.2998466

I am having some trouble with a 7 port D-Link USB hub I just received, and 6 erupters and a fan plugged into it.

These are the errors I am receiving https://i.imgur.com/PFiU7Wv.jpg.

I turn on each erupter one by one. All seems to go well until I turn on the 6th one. It doesn't matter what order I turn on the erupters, but once the sixth one is turned on, a few minutes later I start getting the errors and the client turns off the erupter. I receive a large number of "Miscalculations" and almost no proofs of work accepted.

What is causing this. Is it a problem with my D-link, my computer, both?

Status update, for anyone interested.

I did manage to finally get all my Erupters back online.  What finally worked was to do a full shutdown of the system, let it rest for a few minutes, and then power up.  When I started the BitMinter client I probed for each port manually instead of doing an auto-probe against all ports.  That seemed to do the trick.  I suspect that something with auto-probe is tripping up as it hits ports which have other things attached.  My rig is back up to its full potential now at a whopping 2.3GH/s.

You could try bfgminer. It uses the same drivers I believe.


Any error messages? Did you try if running with just 1 erupter works? Did you try reinstalling the driver?


The Bitminter server will auto adjust your difficulty. Setting a minimum difficulty is most useful right after you connect to the server, making the initial difficulty ramp up less bumpy.

Hi I'm using cgminer and my eroupters all went down recently marked as dead though it seemed like it was trying to revive with no luck. It probably has nothing to do with bit minter it self but it was wierd it started happening after joining this pool.



I do have to ask on another note how I can set the difficulty for my mining in this pool. It feels like for my 6 europters I'm not getting alot of shares at difficulty 2 which was sufficient on btcGuild and way to low for whatever eclipseMC thought of my mining. I haven't tripped over an auto set mode so i can get an idea what bitminter thinks is appropriate difficulty for my current and future speeds.

Thanks for any help or guidance on either matter

Probe doesn't see anything, no errors or any other messages.  The only message is that no external devices were found.  It acts like the device isn't there at all.

When I first returned home I tried doing a probe of ports and managed to see six of the seven.  In continuing to diagnose the issue I stopped BitMinter and started it up again.  The Erupters all went away again.

I have managed to get a few of the Erupters back online.  It required a cold start of the computer but then four of the seven started talking again.

I'm tempted to try another client and see if it can detect the Erupters.  Any suggestions?

When block erupters fail and don't come back, what happens when you go "devices" -> "probe all ports" in the menu? Are there any errors or messages at all about those COM/tty ports?

I'm having the same problems. At first I thought it was something wrong with the hub, but after some testing with other clients all seemed well. I've got 3 Erupters running ATM but just a couple hours ago I was having to unplug them and hook em back in, probe the ports and what not just to get em to work again.

Has anyone else had issues where the BitMinter client stops recognizing Block Erupter USB devices?

I have seven of them on one computer (six on a hub and one in a direct port).  They were running fine for a week.  Yesterday I shutdown the computer to do some work on it.  After I restarted it BitMinter would only see five of the devices.  If I go into Device Manager I still see all seven listed under USB devices.  In trying to diagnose the issue I moved one of the non-responding Erupters to a different USB port.  It started responding again, as a different COM port.  Moved it back, not visible.

Tried shuting the computer down and powering back up.  Devices show in Device Manager (with driver) but are still not seen by BitMinter.

Stopped BitMinter and took all of the Erupters out of the hub.  Put them back in one at a time and tried to have BitMinter rescan the ports.  Now BitMinter won't see any of the Erupters.  As of when I left home this morning nothing was visible.

Has anyone else seen this behavior?  Also, does anyone know if there is a way to test an Erupter outside of BitMinter?  My guess is it should be possible to point a terminal emulator at one of the COM ports and fire a few commands through it to at least get a response. 

FYI, this is on an I7-2600K processor based machine running Windows 7 64-bit.

Thanks.

The post above has a link to the previous version in case you have problems with the new release. There's also a bunch of different versions available under the "tools" menu on the website.

The only changes in the new version are listed above. I don't think your problems are related to the new version. I don't see why it would take longer to load either. That the devices lock up, including the hashrate, sounds like a driver issue. Perhaps reinstalling the silabs drivers can help.

Has anyone else noticed this new version of Bitminter Sucks??
I have multiple computers at multiple locations running different versions of windows (Vista & 7), for the last 3 months, NO problems worth mentioning, it was great, they would run for a week with not even a hiccup, now IF it can see all my USB miners when it starts they only last a few mins then it's like all the USB's "Freeze" they all go solid Christmas tree but the bitminter app says they are still running but the rate never changes again, the video cards on the computers will still mine but all the usbs on all my different hubs just quit...
I had stayed with bitminter for months because it was stable, I am away a lot of hours & I hardly ever came home to issues that were not power related, or broadband down...  Now it's another story & I don't have the time to put into it for a return of $10 a day tops.
Whatever the bitminter people did, the java script now takes longer to load & all I have its problems - Anyone have ideas worth mentioning??  If I could get a old version somehow I would just run it..

BitMinter client version 1.4.2 is out.

Changes from 1.4.1 to 1.4.2:

• Remove password from credentials dialog, mark worker name as optional.
• Support rescanning all ports repeatedly, not just probing new ports once.
    Useful for those with usb ports or devices that go haywire but begin
    functioning again a few minutes later. This option is available under
    "settings" -> "options" in the menu, under the "devices" tab.
• No more warnings about missing settings for Codebase and Permissions in
    java console of newer java versions

Try it out:


If you have issues with 1.4.2 then you can still get the previous release (1.4.1) at https://bitminter.com/client/1.4.1/bitminter.jnlp

BitMinter client v1.4.2beta1 is ready for testing.

New:

• Remove password from credentials dialog, mark worker name as optional.
• Support rescanning all ports repeatedly, not just probing new ports once.
    Useful for those with usb ports or devices that go haywire but begin
    functioning again a few minutes later. This option is available under
    "settings" -> "options" in the menu, under the "devices" tab.
• No more warnings about missing settings for Codebase and Permissions in
    java console of newer java versions
• Attempt to fix hashrate gauges not working for some users

Please check it out:

Contacted BFL this morning, they got back to me this afternoon... after a few back and forth e-mails they sent me an RMA number.

Say what you must about their shitty shipping practices, their RMA and support service is amazing...

But yeah, it took an entire reboot to find the damn device. I would run for an hour+/- and disconnect. Two different computers, both x86/X64, same issue.

Wasn't just Bitminter, BFGminer, & CGminer all had issues after it disconnected. It's a faulty unit... I was just hoping there was a log I could call to on disconnect and reboot the machine when it happened.

95% uptime over 3 days (today, tomorrow, Sunday) is better than no up-time for what looks like 6 or 7 now. It'll get shipped out Monday with a 2 day turn around. *sigh*

BitMinter client does not log to the Windows event logging system, if that's what you mean. I'll have a new version ready soon that can rescan the same ports over and over. So if the device reappears but is still unresponsive for a while, it will still get picked up when it starts working again.

Or do you really have to reboot to fix this situation? "devices" -> "probe all ports"  doesn't help?