Monitoring MegaMiner machines:

While an API endpoint that could be requested from remote machines would be nice, I'm guessing this is a lot to implement and will come after other, more important features, issues and updates.

In the meantime I'd still like to monitor the miners, so I'm suggesting a simple push monitoring method: every time the "Current" screen gets refreshed (or every X minutes -- whatever is easier to implement), MegaMiner would post the current stats (as shown on the Current screen) to a remote server with a simple REST HTTP POST with the data JSON formatted. While I actually haven't done any PowerShell scripting ever, I do know .NET, so I should be able to implement this and post the data to my own (local) server.

Where do you suggest to insert a method call for that?

hi,

I currently have 2 nvdia cards but i am running the old one for display only and the other to mine.
however when i start megaminer, it groups the 2 cards together and start the benchmark.
Is it possible for me to disable the old card so that it will not be run for benchmark and only run benchmark for the new card only?

I think it is due to the fact that when it runs profitabilty algo, the old miner window did not close therefore you have both miner windows open at the same time.

I had this issue once.
go to config.txt and try setting "@@DELAYCLOSEMINERS=20" to "0" seconds.
it should be fine after that

Yes, this * indicates that is mining due to @@PERCENTTOSWITCH config variable, there is better miner but not "best enough".

Default config uses all cards, you can change this using @@GPUGROUPS config variable.

You can see Gpu id running gpulist.bat or current MM screen

if you got 2 cards one of this is what you want.

@@GPUGROUPS=[{"GroupName" : "XXXXX","Type":"NVIDIA,"Gpus":"0"}]

or

@@GPUGROUPS=[{"GroupName" : "XXXXX","Type":"NVIDIA,"Gpus":"1"}]

nvm, figured it out.

Eth donation sent on the 8th. Thanks for your efforts.

some miners/algos take a long time to ramp up hashing to full speed. depending on which algos you're hashing it might take longer than the 200 seconds to perform fully.