Hi, I just started using MPBM for the first time, and what shall I say.... WOW I love it :-)
Easy to set up work sources, Easy to switch on & off & distribute hash power... Using it with my new Cairnsmore1 devices (running on dynamic clocking hashvoodoo bitstream).
Applied fpgaminer's stratum fix to get it to work with various stratum pools that didn't work without the patch.
Also, Hash rates are about 5-10% higher than I can achieve with bfgminer on the boards. (~217,5MH/s/ single FPGA with MPBM) Plus: Accurate Hash rates :-)
So now I'm having some questions, hoping that you'd help me here:
- I also have some ModMiner Quads that are running very stable and fine with cgminer, but now that I saw MPBM I'd really like to integrate them. At a first test, MPBM wants to send a bitstream to them, but doesn't find it since non is included. When I google for the file name MPBM expects, I cannot find anything. What bitstream would I need for them? Can I just use the same Hashvoodoo bitstream that I use for Cairnsmore1 and rename it to the file name MPBM expects?
- The stats displayed are over the whole running time of MPBM - Is there a way to reset them to see the effects of Priority changes better(without restarting MPBM)?
- Is there some tutorial/README on how the Priority settings / Hashrate settings work? Some work sources, like for example bitminter getwork seem to flood the processing that almost all hash power goes there, even when I have other pools at same priority or at same hashrate settings. So far I could not notice any effect of setting the hashrate for a work source. Basically all I can do right now is doing something like define a primary pool at prio 1000000, a backup pool at prio 1000 and a backup backup pool at prio 1 , but anything more elaborated was not as successful as I hoped it to be.
What I really would like to achive is: Have for example a work source group "bitcoin", a work source group "freicoin", .... and within each work source group I have a mix of multiple primary/secondary pools. Then I could on the fly define a target hashrate for each worksource group that could be easily adjusted. But so far no luck :-(
Thanks a lot for any help!