Bitminter client (Windows/Linux/Mac)

[DrHaribo]

I'll have 10 of them come Monday... with how much space each one takes up on the screen, a more condensed overview option would be nice!

Here's v1.2.0 beta 9. You can click the green arrows to switch between full and compact display for each device.

New since beta 8:

• Scan devices one by one to circumvent concurrency bugs in serial port library
• Raise priority of serial port I/O threads to improve performance during high CPU load. This should fix "command timed out" and "extranous data" errors. If the program is starved of CPU time you can still run out of work, see hash rate drop due to slow work dispatch and stales rise due to slow reaction time. Note if you are CPU-mining: run the CPU miner at low priority and/or not on all CPU cores.
• The start button of the "total" device display now starts only the visible devices instead of all devices the first time you click it. The next time you use it to start devices it will resume those you stopped with it, like it always did. The start button on the status bar is the same.
• Added minimize/maximize buttons on each device. The compact display is handy if you have a long list of devices. Remembered across restarts.
• Adjusted expected hash rate (green zone) for AMD Juniper GPU
• Fixed miner GUI bugs

[SgtSpike]

So far, everything's working great!  Love the minimal view too!  I'm only keeping 4 of my 10 BFL's, but hey, even 4 with the full spread view is a bit much, so it helps.

[hakock]

I finally got my BitForce Single running with BitMinter on a linuxcoin system.
Running just fine, it almost doubled my hash rate.

I ordered a mini rig today, let's see how fast they will get it to me.
Is Bitminter ready for such a device? shure hope so, otherwise I think we will make it work somehow.
Ready for testing...

[DrHaribo]

I ordered a mini rig today, let's see how fast they will get it to me.
Is Bitminter ready for such a device? shure hope so, otherwise I think we will make it work somehow.
Ready for testing...

There's one issue I'm still working on with the beta. It seems to not grab new work from the server fast enough. This will surely be a problem with a mini rig. But it will be fixed long before your mini rig arrives.

Currently observed: Windows 7 with 8 singles shows slow work queue buildup but runs ok. Mac OS X with 10 singles ends up with an utterly depleted work queue and devices idling. A fix for this should be coming soon.

Congrats on getting a mini rig! I think it's awesome that so many in the pool are getting singles and mini rigs. I aim to make the miner run as smoothly on them as possible.

[hakock]

I ordered a mini rig today, let's see how fast they will get it to me.
Is Bitminter ready for such a device? shure hope so, otherwise I think we will make it work somehow.
Ready for testing...

There's one issue I'm still working on with the beta. It seems to not grab new work from the server fast enough. This will surely be a problem with a mini rig. But it will be fixed long before your mini rig arrives.

Currently observed: Windows 7 with 8 singles shows slow work queue buildup but runs ok. Mac OS X with 10 singles ends up with an utterly depleted work queue and devices idling. A fix for this should be coming soon.

Congrats on getting a mini rig! I think it's awesome that so many in the pool are getting singles and mini rigs. I aim to make the miner run as smoothly on them as possible.

Thanks, that sound's good.
Do you have an overview, how many singles and mini rigs are/will be there in the BitMinter network?

[DrHaribo]

Do you have an overview, how many singles and mini rigs are/will be there in the BitMinter network?

At least 4 mini rigs and a whole bunch of singles. There are also users mining with other FPGA devices and several people ordered the new Cairnsmore. I intend to add support for more FPGA devices in the future. First I would just like to get v1.2.0 out with BFL support.

[MaxSan]

Left 4 x 6970's mining and a BFL single mining overnight.

2781 accepted.
9440 rejected.

never has this issue with any other miner before.

[DrHaribo]

Left 4 x 6970's mining and a BFL single mining overnight.

2781 accepted.
9440 rejected.

never has this issue with any other miner before.

I never heard of anyone having such an issue with this miner either. Is there anything in the log (text part of the window) to give a clue as to what went wrong? Perhaps network problems?

Currently on my computer I have 317609 accepted and 46 rejected. That's 4 GPUs. BFL units seem to run a bit higher, roughly 0.3% rejected.

[MaxSan]

well i removed the GPUs and put em back on cgminer and kept my bitforce running on your client. seems to be in better order like that so Il keep it as is

[allinvain]

Am I the only one that can't get this miner to detect the bitforce singles? I should mention that I did install the FTDI drivers, but I did _not_ reboot yet. Both miners work fine in MPBM though.

[DrHaribo]

Am I the only one that can't get this miner to detect the bitforce singles? I should mention that I did install the FTDI drivers, but I did _not_ reboot yet. Both miners work fine in MPBM though.

You clicked "devices->probe all ports" in the menus? Which OS are you on?

[Fefox]

Video I made showing the singles power usage with stock PSU's and with a Corsair AX1200..  and of course bitminter running the 8 BFL singles

http://vimeo.com/42438781

[SgtMoth]

show off

[DrHaribo]

v1.2.0 beta10 is out.

This version can download work much faster, using multiple pipelined connections to the server. This should prevent running out of work when you have a high hash rate on the computer, like 9-10 BFL singles or more. All the network code has been rewritten completely. I've been running this a few days myself, but it needs some more testing before finalizing v1.2.0. Please check it out, especially interesting if you can try it on high latency connections (maybe big file transfers running that slow down your internet connection) or an unstable network where the connection comes and goes.

Let me know how it runs.

[ChiangYay]

Hi,

I.m testing your v1.2.0 beta10 with one Bit Force and I get: batch acquisition of 0 triggers.

What does it mean?

Is it bad?

Regards

v1.2.0 beta10 is out.

This version can download work much faster, using multiple pipelined connections to the server. This should prevent running out of work when you have a high hash rate on the computer, like 9-10 BFL singles or more. All the network code has been rewritten completely. I've been running this a few days myself, but it needs some more testing before finalizing v1.2.0. Please check it out, especially interesting if you can try it on high latency connections (maybe big file transfers running that slow down your internet connection) or an unstable network where the connection comes and goes.

Let me know how it runs.

[DrHaribo]

I.m testing your v1.2.0 beta10 with one Bit Force and I get: batch acquisition of 0 triggers.

What does it mean?

It's just the scheduling subsystem (see the automation part of the options) that is a bit chatty. It's nothing to worry about and you should only see it if you have verbose logging turned on.

[DrHaribo]

I just uploaded beta 11. It fixes a thread scheduling bug in beta 10 that could cause devices to run out of work when there was still work in the queue.

Beta 11 seems to run fine on 6 BFL singles, 5.2 GH/s, with low stales. Looking good so far.

[SgtSpike]

Question - would that new version help stale proof of work at all?  I have 4 BFL's running, and don't ever get a lack of work, but do get stale proof of work from time to time.

[LordMord]

I get this error with beta 11:
Connection failed: Invalid argument: getsockname

[DrHaribo]

One problem found in beta 11. On some systems (high hash rate?) after running for some time the CPU usage goes up and it starts running out of work. Investigating this now.

Question - would that new version help stale proof of work at all?  I have 4 BFL's running, and don't ever get a lack of work, but do get stale proof of work from time to time.

Yeah, it can use multiple connections and it gives priority to uploading proofs of work over downloading more work, so it might reduce rejects a bit.

I get this error with beta 11:
Connection failed: Invalid argument: getsockname

Do you have a firewall blocking the program? Are you running on Windows 8?