Hey Nate, what are your thoughts on adding a a timer function to MultiMiner? I am working on setting my farm to stop mining during peak kWh times during the day to save $ on my power bill and maximize profits.
I'm not planning on a timer or scheduler, but I am planning on adding a way to pass command line arguments into MultiMiner. This would let you use something like the Task Scheduler in Windows or cron on *nix based systems to schedule interactions with MultiMiner.
Just got a USB dualminer to play around with and I'm having some issues here.
Firstly, there is no dualminer switch on the USB stick. I suspect I have an early revision.
You actually have a later revision. Only the first round of hardware had the dip-switch for changing voltage. It turned out to be far more trouble than it was worth and was removed from later hardware revisions.
I got it to work on the same BFGminer that I'm running with MuM using:
bfgminer -S dualminer:all --scrypt --set-device gridseed:clock=850
But I get this output:
...
I tried setting it to one com port or the other, but if I only set it to one (regardless which one), BFGminer doesn't detect the DMU, only the OCL. I'm assuming DMU is the SCRYPT and OCL is the SHA256.
No OCL is your graphics card. DMU is the DualMiner mining Scrypt. What you are seeing looks right. If you want to mine both Scrypt and SHA256 at the same time you'll need to run two instances of BFGMiner at the same time using another argument. This isn't supported by MultiMiner.
MultiMiner will not detect the dualminer, at all. I tried it on two computers using this config:
...
Make sure you are running the latest version of MultiMiner and the latest version (from Git) of BFGMiner. See the link in this post for grabbing a daily copy of the binaries. Remove the --scrypt argument from the Hardware scan arguments in settings. Sorry the way BFGMiner 3.99/4.0 handles these things is still a moving target. You now have to run it with -d? with and without --scrypt to get all the devices.
I'm still getting really poor hash rates (50%ish) when connecting to the MM proxy stratum, especially when mixing this with different clients like SGminer and CGminer.
If you are using the Stratum Proxy for Scrypt there are known issues unless you run some of the latest BFGMiner code from Git. Luke has been working on fixing Scrypt mining via the Stratum Proxy. Unfortunately I am a little behind on things and not sure if it's been merged into the master branch or still in its own branch.
How is the work coming along on allowing the g flag for more then one GPU? Someone mentioned a beta version of BFGminer had it. I still have a few machines that need this.
That's been done in Git for a while now. If you'd like the latest Windows build you can always get something compiled from the current Git source here:
http://luke.dashjr.org/tmp/code/webisect/webisect.php?dobuild=bfgminer