Bitminter client (Windows/Linux/Mac)

[Grimsley]

SO!  I just picked up one of these Block Erupter cubes.  Got er all set up, and ran into a slight snag.  Can't seem to get it working with my mac. Aside from taking a hammer to may machines and buying new hardware, anyone have any advice on how to get this thing mining on bitminter?

[DrHaribo]

SO!  I just picked up one of these Block Erupter cubes.  Got er all set up, and ran into a slight snag.  Can't seem to get it working with my mac. Aside from taking a hammer to may machines and buying new hardware, anyone have any advice on how to get this thing mining on bitminter?

Did you try this? https://bitcointalk.org/index.php?topic=27062.msg3046129#msg3046129

[GuyllFyre]

Here's an interesting observation with BitMinter Client v1.6.0.
I had some system issues and was playing with some different distros, breaking them, then trying another (Settled on Linux Mint 16 x64 this time).
During this time, I moved the Anker hub and my 11 U1s to the Windows 7 Pro x64 laptop.
I had repeated disconnections, random miners would stop or be lost, and for some reason, when I got another new hub, I couldn't add more than 11 miners.

Now, with both of the Anker hubs moved into the office and plugged into the Linux box, I'm experiencing none of these issues.

I'm not really quite sure how to interpret this but it seems that the client and miners are much more stable and happy on Linux than on Windows.

[DrHaribo]

I had repeated disconnections, random miners would stop or be lost, and for some reason, when I got another new hub, I couldn't add more than 11 miners.

Did you notice if the Antminer COM ports would disappear at that point? Or were the COM ports still present, but the client still unable to communicate with the Antminters properly?

[GuyllFyre]

I had repeated disconnections, random miners would stop or be lost, and for some reason, when I got another new hub, I couldn't add more than 11 miners.

Did you notice if the Antminer COM ports would disappear at that point? Or were the COM ports still present, but the client still unable to communicate with the Antminters properly?

In some cases, the COM port would disappear, doing a scan would bring it back and it would start mining again.
In the cases where it would disconnect and prompt for credentials to reconnect, in the log window there would be an "internal script error" of some sort and random miners would not start, many times a restart of the client was needed.
If the client keeps that log file, I can fire up the laptop and pull the exact error.

[DrHaribo]

No, the log isn't saved. All of this sounds pretty odd. If you have this problem again see if you can get some screenshots and/or copy the log.

COM ports disappearing, not just in Bitminter but on OS level, and coming back, is usually because the device isn't getting enough power.

In Windows you can have a look in the device manager to see how many devices are detected by the OS and assigned to COM ports.

[GuyllFyre]

I discovered the COM port issue.
I bought a batch of short USB extension cables and found out two of them are bad.
That should clear up that.

If I plug things back into the Windows box, I'll look for the other error.

[FriedIV]

This is in reference to the BFL Monarchs that are soon to be delivered.

Josh has stated that "
It is built in to the design and you'll be able to overclock it from within the mining software (BFGminer currently supports it) and I assume CGminer will as soon as we can get cards to Kano and Con."

Will Bitminter be including the functionality to control the Monarchs and Imperial Monarchs?

Thx

[DrHaribo]

Will Bitminter be including the functionality to control the Monarchs and Imperial Monarchs?

I will look into it.

[Fluke.]

"Antminer (COM9): Not getting any results. Retuning timers."

Sometimes this doesn't work reliable. But stopping the device and starting it again is fine.
Is it possible to add an option how to deal with failing devices? Maybe some kind of event based actions similar to the scheduled actions.

[DrHaribo]

"Antminer (COM9): Not getting any results. Retuning timers."

Sometimes this doesn't work reliable. But stopping the device and starting it again is fine.
Is it possible to add an option how to deal with failing devices? Maybe some kind of event based actions similar to the scheduled actions.

What happens when it fails? The device is doing miscalculations over and over again until the client gives up on it? Or it times out?

If the timer retuning fails there is probably something wrong. It's not getting any data from the device with regular mining for a while, which is possible although unlikely. In this event it sends the device some work that is known to produce a certain result. In this case the device should respond with the correct answer if it has not malfunctioned.

In the options you can set it to scan for devices at regular intervals. You can also set it to start new devices automatically. This way you can use devices that occasionally die but recover after a while.

[Fluke.]

Thx for your reply.

The device times out. There are no miscalculations reported, neither before not getting any results nor while it tries to recover. Looks like this:

[...]
Antminer (COM9) ERROR: Selftest error. Timed out at 25000 ms.
Antminer (COM9) ERROR: Selftest error. Timed out at 25000 ms.
Antminer (COM9) ERROR: Selftest error. Timed out at 25000 ms.
Antminer (COM9) ERROR: Too many errors, giving up

As I said when starting the device manually again it does work. I will try to setup some regularly scan intervals to get it back up.

[GuyllFyre]

Thx for your reply.

The device times out. There are no miscalculations reported, neither before not getting any results nor while it tries to recover. Looks like this:

[...]
Antminer (COM9) ERROR: Selftest error. Timed out at 25000 ms.
Antminer (COM9) ERROR: Selftest error. Timed out at 25000 ms.
Antminer (COM9) ERROR: Selftest error. Timed out at 25000 ms.
Antminer (COM9) ERROR: Too many errors, giving up

As I said when starting the device manually again it does work. I will try to setup some regularly scan intervals to get it back up.

This may be a heat or voltage stability issue but when I saw that, I find that if I back off the speed one step at a time, I can find a speed that it will run 100% reliably at.
I've got a U2 that won't run at anything over 1.8 but I've got U1s that run at 2 with no issues.

Also verify that the connection to that miner is solid.  I had to use some short USB cables to be able to fit mine all into my older Anker hub and found two bad cables causing issues.
2 out of 20 cheapie Hong Kong eBay 6" USB extension cables isn't too bad but tracking down the issue can be annoying at best.

[Buchi-88]

Hello DrHaribo!

Bitminter also support the "BFx2 Bitfury USB stick miner"?

https://bitcointalk.org/index.php?topic=524521.20

greets

[DrHaribo]

Bitminter also support the "BFx2 Bitfury USB stick miner"?

Not supported by Bitminter client. You can mine with it in the Bitminter pool though, using bfgminer or cgminer.

[Buchi-88]

Bitminter also support the "BFx2 Bitfury USB stick miner"?

Not supported by Bitminter client. You can mine with it in the Bitminter pool though, using bfgminer or cgminer.

OK, thanks for your fast answer

greets

[theweiss]

For what its worth, I've had issues over clocking my U1.  It will happily overclock to 2.0 GH/S but anything over that and it errors out quite quickly.  But when its running at 2.0 is has a staggeringly low number of errors as compared to the old 336 mh/s Block Eruptors that I've used in the past.

[janonathon]

For what its worth, I've had issues over clocking my U1.  It will happily overclock to 2.0 GH/S but anything over that and it errors out quite quickly.  But when its running at 2.0 is has a staggeringly low number of errors as compared to the old 336 mh/s Block Eruptors that I've used in the past.

That is where all my U1's and even U2's (apart from some @ 2.1 and some others @ 1.9) spend all their time stable. other's can do more with voltage modfying but i haven't a clue what that invloves. With the price those miners are, 2GH/s is a pretty good value and easy to setup.

[ichtus27]

Funny that on my windows 7 i can ran my bitmain u2 only on 1,8 with no hw errors, but on my apple mini mac i can run it at 2,2gh no problem and no errors.
Bitminter does not go higher than 2,2 i saw, astroid did but made hw errors with  2-2,4gh's. 
Astroid is for apple.

Windows 7 with asicminer u1 is good on 2 gh's and with hw errors on 2,1gh/s.

Soon i hope to order s1's and butterfly's the 50gh/s's ...

will see.

Me just updating for what i learned allready.

[GuyllFyre]

Funny that on my windows 7 i can ran my bitmain u2 only on 1,8 with no hw errors, but on my apple mini mac i can run it at 2,2gh no problem and no errors.
Me just updating for what i learned allready.

Interesting note.
It seems that my x64 Linux box is much more stable with my small array of U1 and U2 miners than my Win 7 Pro x64 laptop.
My Win7 laptop would error out on random issues at least daily.
My Linux Mint 16 setup runs MUCH more stable.

Maybe it's the Java runtime?
Windows uses the Sun/Oracle/Crap.
My Linux machine (main machine) runs IcedTea...