MultiMiner: Any Miner, Any Where, on Any Device (Free, Open Source, Cross Platform)

[124C41]

There is still a persistent bug in the MobileMiner app for iOS. All rigs show as offline in Status, even thought they are not.

Can you check to see if this is happening on the HTML5 app?

http://web.mobileminerapp.com

Also note that the MobileMiner API has been up and down this evening as I tuned many things for the increase in users I am seeing.

The HTML5 app is displaying all as 'mining' correctly.

[1714499685]

1714499685

[1714499685]

1714499685

[TsaktuO]

Installed multiminer on xunbuntu 12.03. Once I hit start for mining, the client crashes...

Any thought on how to fix this issues. Everything else seems to be working out. If I can not get this to work... cgminer it is :  (

[nwoolls]

Installed multiminer on xunbuntu 12.03. Once I hit start for mining, the client crashes...

Any thought on how to fix this issues. Everything else seems to be working out. If I can not get this to work... cgminer it is :  (

Please copy the text that is left on the console after the MultiMiner window closes and paste it in a response here.

[doctormandrake]

Hi, having some trouble with multiminer. FOr some reason I am having no luck getting it to properly detect my miners. Have 4 ants and 2 block erupters running, all have been detected in the past easily.

Did you try right-clicking and clicking Scan Hardware? Starting with 2.7 this no longer happens automatically on startup.

no such luck, in fact when I right click, the toggle for scan hardware is "grey"   (not selectable) updated to the most recent multiminer to check, no such luck.

Just using bfgminer for the moment with .cmd files and periodically testing, only thing i havent done is uninstall and reinstall drivers, but with bfgminer detecting them and working I didn't see that to be useful.

[nwoolls]

no such luck, in fact when I right click, the toggle for scan hardware is "grey"   (not selectable)

Click the Stop button to stop mining and then click Scan Hardware. You can't scan for hardware while mining (devices are in use).

[Raptor2213]

Two requests for you.

• I know I asked for this previously, but please have MuM stop suggesting crappy coins.  I've had it suggest coins that are 0.1% profitable.  I would like to have push notifications on, but I don't like getting stupid coin SPAM (and it's useful to see what's profitable).
• Could you make it so that we can tell MuM to update to the latest version through MobileMiner?

[nwoolls]

For those of you who live on the raggedy-edge, version 2.8 PR1 (preview/pre-release) is now available for testing:

https://www.dropbox.com/s/lh4qwxqi0gs9vxt/MultiMiner-2.8.0.zip

There are a few more changes in-store for this update, but so far this preview includes:

• Improved overall performance
• Coin difficulty is read directly from the network once mining begins
• Worker temperatures are shown for Network Devices and the Stratum Proxy
• Added the option to Copy / Clone an existing configuration in the Configure Coins dialog
• Added support for the MobileMiner Pools API, allowing switching coins from smart phones and browsers
• Added the option to save coin configurations to all rigs via MultiMiner Remoting
• Customized names for machines and devices are now pushed to MobileMiner

Thanks in advance for any feedback and bug reports  

[124C41]

For those of you who live on the raggedy-edge, version 2.8 PR1 (preview/pre-release) is now available for testing:

https://www.dropbox.com/s/lh4qwxqi0gs9vxt/MultiMiner-2.8.0.zip

There are a few more changes in-store for this update, but so far this preview includes:

• Improved overall performance
• Coin difficulty is read directly from the network once mining begins
• Worker temperatures are shown for Network Devices and the Stratum Proxy
• Added the option to Copy / Clone an existing configuration in the Configure Coins dialog
• Added support for the MobileMiner Pools API, allowing switching coins from smart phones and browsers
• Added the option to save coin configurations to all rigs via MultiMiner Remoting
• Customized names for machines and devices are now pushed to MobileMiner

Thanks in advance for any feedback and bug reports  

Living on the edge
Running smoothly on two rigs right now for the last 10 minutes

[Blackbird0]

Just checking in, have you gotten replacements for DualMiners yet? I'm interested in testing the OC function.

[nwoolls]

Just checking in, have you gotten replacements for DualMiners yet? I'm interested in testing the OC function.

It should be here tomorrow.

[ManeBjorn]

I have an odd question.
I had updated my firmware on the Avalon lastnight and that went great.
The only problem I have is it no longer shows the current gh/s rate in MuMi.
It does show the average rate and accepted and rejected and such.
I am using the pre-release 2.7.6
It's the same on both systems.

[nwoolls]

I have an odd question.
I had updated my firmware on the Avalon lastnight and that went great.
The only problem I have is it no longer shows the current gh/s rate in MuMi.
It does show the average rate and accepted and rejected and such.
I am using the pre-release 2.7.6
It's the same on both systems.

Try adding --log 5 to the argument / config file for your Avalon.

[ManeBjorn]

So does this look correct then?

Code:

--api-listen --log 5 --api-allow W:127.0.0.1,192.168.0.0/24

I have an odd question.
I had updated my firmware on the Avalon lastnight and that went great.
The only problem I have is it no longer shows the current gh/s rate in MuMi.
It does show the average rate and accepted and rejected and such.
I am using the pre-release 2.7.6
It's the same on both systems.

Try adding --log 5 to the argument / config file for your Avalon.

[nwoolls]

So does this look correct then?

Code:

--api-listen --log 5 --api-allow W:127.0.0.1,192.168.0.0/24

That should be right. That controls how often the miner logs statistics, which (unfortunately - not sure why this is) changes the actual key used for the current hashrate in the API. Added to that, the miners also change the internal default, meaning that (unless you specify --log manually) you cannot count on a consistent key for current hashrate in the API.

</toomuchinfo>

[ManeBjorn]

That makes sense though especially with the way cgminer is setup to run these things.
I am learning more each day.
Thanks I will let you know how it works.

So does this look correct then?

Code:

--api-listen --log 5 --api-allow W:127.0.0.1,192.168.0.0/24

That should be right. That controls how often the miner logs statistics, which (unfortunately - not sure why this is) changes the actual key used for the current hashrate in the API. Added to that, the miners also change the internal default, meaning that (unless you specify --log manually) you cannot count on a consistent key for current hashrate in the API.

</toomuchinfo>

[Blackbird0]

Just checking in, have you gotten replacements for DualMiners yet? I'm interested in testing the OC function.

It should be here tomorrow.

Thanks!

[brunosky]

Hello Nate,
I've just installed MultiMiner on my Mac Pro.
I don't understand why it can't see or the 6 Twinfury or the GPU: in the low right corner I can read 0 device(s).
Can you help me?
Thanks in advance

[ManeBjorn]

Did you right click on the empty part of the screen and have it do a hardware scan?
Also what software were you using with your TwinFury before you installed MultiMiner?
If it was CGMiner you need to remove the drivers for it and reinstall the new drivers that you can download from the MultiMiner webiste.
http://www.multiminerapp.com/
You should choose the Blue/RedFury drivers.
I hope this helps you.
Happy Mining.

Hello Nate,
I've just installed MultiMiner on my Mac Pro.
I don't understand why it can't see or the 6 Twinfury or the GPU: in the low right corner I can read 0 device(s).
Can you help me?
Thanks in advance

[ManeBjorn]

Hi Nate,
Same weird acting displays.
Everything runs ok though.

So does this look correct then?

Code:

--api-listen --log 5 --api-allow W:127.0.0.1,192.168.0.0/24

That should be right. That controls how often the miner logs statistics, which (unfortunately - not sure why this is) changes the actual key used for the current hashrate in the API. Added to that, the miners also change the internal default, meaning that (unless you specify --log manually) you cannot count on a consistent key for current hashrate in the API.

</toomuchinfo>

[124C41]

Found bug?

After 1 full day of mining with 2.8 PR1 only 2 of my 3 rigs have pool switching enabled on web.mobileminerapp.com.

Nate, let me know if you would like me to supply more info - happy to help.