Topic: MultiMiner: Any Miner, Any Where, on Any Device (Free, Open Source, Cross Platform) - page 180. (Read 827334 times)

I would absolutely implement this for you, no funding needed. My only problem is this:

The app already uses "bfgminer.exe -S all", as seen by showing the Process Log. In the Settings dialog you can click Disable GPU mining. This will pass in the -G. So MultiMiner already passes those two flags. So it seems the only real issue with your setup is the -d parameters I am passing in. I hate to be stubborn but I am hesitant to add a new, advanced setup dialog, code which goes into a few different DLLs, etc. rather than identifying the actual issue and fixing that.

I really do appreciate the feedback and would love to get things working optimally for you. If you can look at the Process Log and see the executable path and arguments that MultiMiner is using, then compare to those that work for you that would be super. Even copying & pasting the executable and arguments that MultiMiner is using here may help me identify the issue. I would also absolutely be willing to do remote support (e.g. TeamViewer) if you are comfortable with that, or anything that helps us work together to identify and fix the issue.

I haven't had time to sit down and figure out the issues, but I was thinking about a feature or features I'd like to see.

I've said this before, I love your software, and especially the MobileMinerApp functionality.

As we all know, bitcoiners are an advanced bunch, and as such love to configure things. I think some of the issues I'm seeing with my setup would be fixed if you had an option in the settings for us to configure the exact flags that you are using to run bfgminer. There is already setting to set the flags for the respective algorithms, but it would be nice to be able to set the overall flags. To maintain the main functionality of the app(switching pools according to coin profitability) you could just add on the appropriate pool flags to the set of flags we assigned.

An example on how to implement in the GUI: In the settings dialog, you could have an advanced settings dialog with a warning about changing the settings. Then have a text box to input our flags. These flags would override all others input anywhere else, including any devices "auto detected"

This would allow me to pass on a usable configuration to bfgminer regardless of any issues relating to the gui. A config I know would work for my miners would be "bfgminer.exe -S all -G" and if your software just added on the appropriate pool flags for the most profitable coin, I could absolutely use it.

I would even be willing to put 0.50 BTC funding towards implementing it (I would put more down, but that's all I have readily available at this moment)

Just some thoughts while on a mini vacation. I'll still try and help debug the initial issues I was having though.

I'm totally legit man no worries there. That is only so I can get in touch with users if needed. One thing my experience has taught me, especially with mobile apps, it's good to get a verified email address early on rather than scramble to get one later. e.g. if you have to make some big breaking change.

Version 1.1 is already waiting for review with the following small enhancements (courtesy of suggestions from the Asteroid author):

• Delete machines by swiping (they will reappear if they submit data)
• Show the date data was fetched on main screen
• Refresh data older than 15 minutes when navigating
• Hide blank hashrates on the main screen
• Show the network activity indicator when fetching or updating data

Next on my list is the Android app as well as getting something up at mobileminerapp.com that lets people find out how to submit statics, request API keys, etc.

Thanks for your support!

Love the MobileMinerApp! Please don't sell my e-mail though... I'm gonna buy the notifications to help support your efforts!

Happy Friday folks. The MobileMiner iOS app has been approved and is now available on the Apple App Store. Happy mobile mining!

My pleasure. You can PM me on here or email me at my username @ gmail dot com. I'm on Skype too with the same info. If needed we can do some remote assistance too, if you are comfortable with that. I noticed in re-reading you have a FPGA as well, so that's another piece of your setup that I cannot reproduce, so there may be some quirkiness there in the current build.

I'd love to fix this stuff, so whenever you have time I'm down for doing whatever we can to diagnose.

I'll get back to you tomorrow or possibly sometime this weekend to help debug the issues for you, however I'm trying to get a new Scrypt machine up and running along with going away for the long weekend.

Thanks!

hahaha indeed if i start bfgminer simply with the -S all it crashed
the same goes for cgminer with --ndevs
I do admit that i did never change my mining setups besides certain pool changes
These problems started when i wanted to change my gpu's to scrypt and to get the usb devices to work
I did not ever expected such weird issues, but since i switched over to win 8 got more problems running miners

Well not if i use my gpu's on btc that still runs without problems
I also made sure to open command prompts as admin in case this would prevent them to access hardware

No offense taken at all. I would just like to fix what issues I can, and if you have time and care to help with that it would be excellent! 


Just trying to make sure I understand here. Are you saying that bfgminer itself crashes if you do --scan-serial all or -S all ? But it works if you list each and every device with --scan-serial? Or are you saying MultiMiner crashes? Can you post the crash details/text?

MultiMiner already launches bfgminer with --scan-serial all, so it should find your devices, unless bfgminer is failing here (which may be what you were saying to begin with).

Do not get me wrong i do love your program but i can not use it

Since its impossible to add all commands needed to let these miners run the same as with the config files
Its simply too much of a fuss, i think it has todo that both miners are getting too complex and the different usb devices not really work well

For instance the command to find all usb port devices on bfgminer simply fails blah blah -all did let it crash  

I have to make a huge list of usb devices to get them found:
"scan-serial" : [
   "/dev/ttyUSB0",
   "/dev/ttyUSB1",
   "/dev/ttyUSB2",
   "/dev/ttyUSB3",
   "/dev/ttyUSB4",
   "/dev/ttyUSB5",
   "/dev/ttyUSB6",
   "/dev/ttyUSB7",
   "/dev/ttyUSB8",
   "/dev/ttyUSB9",
   "/dev/ttyUSB10",

and so on till com 35

I have the drivers you posted installed on those machines and setup as most posted on the forum

But they simply refuse to work together, i am currently searching for a small cheap minibook which can act as a miner on bamt/linux
To see if that works better
But my experiment with bamt on a usb stick showed it could find the amu's, but again the bfl messes up

Gonna try the winpe experimental mining solution also, sadly its is pretty limited.
Sadly have no longer access to the free windows 8 server licenses because i left the company where i worked

PS the cgminer is simple i use zadig to get it running again on the amu's

Again i think you program will make many people happy if they can overcome the miner problems
The developers are not much of a help since they simply not respond at all

Hmmm I'll have to figure out a way to test this. I can't think of a reason off the top of my head why it would be limited to 10. Does it show all of the devices in the UI? But not mine with all of them? Any details you could give would be excellent, including the error text and call stacks, screenshots, etc. I'd love to get this fixed for you!.


What arguments do you use with cgminer when you don't use a password? Do you just omit that parameter? I'd be happy to add proper support for leaving the password out. Can you give me an example of a pool like this that I could test?


Can you please send me the full error text and call stack for this error? If possible please download the debug build as that will give me line numbers in the error.



It will automatically only use SHA-256 coins with USB/AMU devices. It will only Scrypt mine on GPUs. Let me know if you need something more there.

Thanks very much for your feedback. I'd love to get these issues addressed for you so any additional information would be great.

It appears your software can't deal with more than 10 devices. I have 12 Block eruptors and a Modminer on the same machine. In an error, I noticed that you specify each device by  a "-d 0 -d 1" flag. This ensures that there will only be 10 devices enabled, since it appears you don't make allowances for more devices?

Another thing is I have pools that don't need passwords. If I don't put a password into the coin settings dialog, the miner won't start.

If I put in a miscellaneous password just to get it started, I get an error of "An item with the same key has already been added" in a .NET dialog box. I have no idea what this means.

I have MultiMiner running successfully on my Scrypt rig, but not on my SHA-256 because of the device limitations and error messages.

Otherwise I love the software, works great! One question I have is can I force some devices to only mine scrypt coins and other devices to only mine SHA-256? especially at the same time? Because it is almost always more profitable for my GPUs to stick to scrypt mining, but my Block Eruptors & FPGA can't mine scrypt even though it is more profitable.

Hi there. I'm sorry to hear you are having trouble.


That honestly sounds about normal for me with cgminer. In my experience its USB support is pretty flakey. I have 2 USB Erupters and I sometimes have to start cgminer a couple of times for it to see all of them. This is on multiple machines and without MultiMiner.


Unfortunately I don't have any BFL devices yet for testing. From what I have read they work fine with bfgminer but I don't know about cgminer.


You can add any extra miner parameters within the Settings dialog.


In order for the USB Erupters to work with bfgminer you need to install this driver and reboot. Note that installing that driver will make the USB support for AMUs in cgminer stop working until you uninstall it.

Found 2 issues regarding this tool

I have 1 bfl jala
And 3 asic miner erupters at present

The first is when i start cgminer it finds 2 from 3 amu's.
Then comes the funny part if i start cgminer with the config it instant finds all 3

But now the second problem i can not get that bfl to work on cgminer i tried messing with the driver but somehow i could not get it to work
 
bfgminer finds the jala instant and does work flawless with it on this miner but i miss all the extra parameters from the config file.
But this miner does not see the amu's "sigh" 

Now this tool only let you choose one or the other which does not work for me as well

The MobileMiner iOS app has been submitted to the App Store for review. This should take about a week. The initial version includes:

• Open API that any mining software can adopt (currently supported by MultiMiner for Windows and Asteroid for Mac)
• Ability to monitor multiple machines and devices
• Icons make it easy to see which machines are offline, mining, and not mining
• Start, stop, and restart mining remotely
• Email and push notifications for offline machines, offline devices, and hot devices

Once this is out the door work will begin on the Android version, along with a proper website for the apps & API.

Version 1.0.12 of MultiMiner is now available on the Github Releases page. Changes include:

• Add the ability to configure the interval used for strategy checks
• Display a dialog if version 3.5 of the .NET Framework is not installed
• Automatically download the latest binaries for cgminer and bfgminer under OS X from the xgminer-osx project (previously a static version number was used)
• Support for remote monitoring and remote control using MobileMiner
• Additional fixes for NULL data returned from CoinChoose.com

I assure you an Android version is the first thing on my list once the version iOS release is out the door. There are a few more features that I want to do for the iOS version before I submit to the App Store, but an Android version isn't that far off.

This is so awesome nwolls.  You are making something miners have wanted for awhile now.  Being able to remotely control and monitor miners like this is amazing.  That being said if you ever need any android testers let me know.  Being an android fanboy I have a lack of iOS devices 

Okay folks. The iOS Dev Center is back up which means I should be able to start sending out beta versions of MobileMiner and - soon - submit a version to the App Store. If you have an iOS device (iPhone, iPad, iPod) with iOS 5 or greater and would like to try this out, please send me a private message with your device's UDID.

This should be limited to those with time to give feedback, with decent technical knowledge, good communication skills, and with the understanding that this is in order to test the app, not to shape the feature-set. This is not to say that users and testers will not have input on the direction of the app, but the point of testing this should be to find bugs and issues.

Thanks!

Edit: Beta participation will be first-come-first-served but with priority given to those who display, or have displayed, technical aptitude or given good feedback. Because of the way iOS development works I have a limited # of devices I can give beta copies to, plus it's harder to manage feedback from more testers. Thanks for understanding.

Crystal - thanks very much for that description! I thought that's where you were going but wasn't sure and like to make sure I have a good grasp on a feature before I try to implement it.

My own experience with merged mining has been limited to BTC+NMC so using a profitability adjustment was "good enough" there.