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

You need FTDI drivers installed:

http://www.ftdichip.com/Drivers/VCP.htm

http://imgur.com/Uw9U6Vg

nwoolls: it looks like there's some sort of peculiar stat problem on the dualminer. You'll notice that it's not showing shares being accepted properly, nor the best share, nor a rejection percentage.

However, my pool is accepting shares, and I am getting blocks. So I think it must just be a stat issue?

You'll note that everything looks a-okay on the SHA-256 instance that is running along side it.

On the DualMiner support.
I cannot get it to detect the unit.  It flashes the light on it and seems to know it's there but it never shows up in the device list.  I even tried on my laptop. 
Do I need to add something somewhere?

I have multiminer checking for straight profitability every 5 minutes from coinwarz, I know when it switches to a different coin it restarts the miner, does it restart every 5 minutes even if it's the same coin? also for the people that use multiminer for multiswitching, do you think coinchoose is a better option than coinwars in terms of profitabilility? I bought 50000 api calls from coinwarz, but I never compared it agains coinchoose which is free.

I just wanted to let everyone know I put up a small review of the DualMiner on cryptocoinsnews.com
http://www.cryptocoinsnews.com/2014/02/26/dualminer-sha-256-scrypt-usb-miner/

It really is a good product and I wanted to share my experience using it with everyone.
I also made sure to mention that Nate and Luke were working hard on getting support for them for MultiMiner and BFGMiner.

I'll bring it back up with Luke. I do have some notes from him. He suggested making sure that --scan-time and --expiry are working as intended. I just haven't had time to dig too deeply with everything going on. I'll try to make a point of it before I dig back into writing more drivers.

FWIW both Luke and I dug through all previous versions of BFGMiner and it isn't something that got broke at any point. Scrypt solo mining never worked (well) it seems, starting from the versions that very first supported Scrypt mining. So I think it is more of a case of CGMiner fixing something at some point, rather than BFGMiner breaking something.

Hmm...I think the pool I was on was DDoSed last night. I'm mining now with a bunch of failovers, and it seems to have been going fine for the last 2-3 hours.

I realize this isn't the BFGminer thread, but since we can only use Multiminer with BFGminer, has there been any work or progress on the issue of huge numbers of rejects and inability to solo mine using BFGminer? In order to keep profitability up, I have to be able to solo mine coins, and I cannot currently use multiminer to do that.

Still launching and tweaking 40+ cgminer batch files whenever I have to solo, and then I end up losing hash rate to dead or sick cards. Where exactly does the problem lay in BFGminer? Is there any band-aid that I can try?

To those not familiar, this is not just an issue of misconfigured cards, I've solo mined for nearly a year, but when I made the switch to BFGminer, nearly 99% of the blocks found are rejected. Nwoolls was also able to replicate on the testnet. I'm just confused on how BFGminer morphed away from CGminer and broke the feature.

I've got to start testing some other solutions.

So, not trying to the B mode yet, because I think I'm having trouble with the L mode.

I left it on for about 6 hours, and it seems to only rarely be giving accepted blocks. For instance, in the last 5 minutes, it's only given one accepted block. No HW errors, no rejections.

I wonder if I'm not adding the right commands to the command line? Additionally, the little yellow light on it that seems to indicate it's on turned off when I woke up this morning. The pool I was mining at indicated it had not accepted any shares for several hours.

I don't believe it's any sort of power problem, simply because my SHA-256 stuff, which is plugged in to the same hub, is still mining happily away.

I'm just writing in the following from commandline.


Do I need to tell BFGMiner to somehow set a difficulty or open a certain number of threads?

Current rig setup: Windows 7 x64, 1x Sapphire HD5830, 1xDiamond HD5830, Catalyst 13.1, scrypt arguments: --thread-concurrency 5568 --lookup-gap 2 --gpu-engine 990 --gpu-memclock 1000 --gpu-powertune 20 --temp-cutoff 90 --temp-overheat 85 --temp-target 70 --gpu-fan 40-100 --auto-fan -I19 -g 1 -w 256 = 625kh/s 69deg steady)

MultiMiner crashed 2x earlier on this machine. Here is a copy of the error message/crash report..


Description:
  Stopped working

Problem signature:
  Problem Event Name:   APPCRASH
  Application Name:   MultiMiner.Win.exe
  Application Version:   2.6.2.143
  Application Timestamp:   52f03f64
  Fault Module Name:   KERNELBASE.dll
  Fault Module Version:   6.1.7601.18229
  Fault Module Timestamp:   51fb1677
  Exception Code:   e053534f
  Exception Offset:   000000000000940d
  OS Version:   6.1.7601.2.1.0.256.48
  Locale ID:   1033

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt



Description:
  Stopped working

Problem signature:
  Problem Event Name:   APPCRASH
  Application Name:   MultiMiner.Win.exe
  Application Version:   2.6.2.143
  Application Timestamp:   52f03f64
  Fault Module Name:   KERNELBASE.dll
  Fault Module Version:   6.1.7601.18229
  Fault Module Timestamp:   51fb1677
  Exception Code:   e053534f
  Exception Offset:   000000000000940d
  OS Version:   6.1.7601.2.1.0.256.48
  Locale ID:   1033

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt

Are there any other log files generated by MM or perhaps BFG

As far as the hash rate drop I noticed between 2.6.2 and 2.7.2/2.7.4, I am puzzled as well since I made not other changes. I used the auto update feature, though sometimes the install hung and required a removal and reinstall/upgrade. I noticed the hash rate drop on another machine as well, this time a Windows 8 machine and same deal 2.6.2 was hashing @320+, upgraded to 2.7.4 and max my Sapphire 5830 could reach was approx. 289.
I will work on compiling some screenshots of this issue and posting them asap (as well as Cube machine errors). I am still recovering passwords and synchronizing my network.

Thanks again for all the help and hard work you have put into MultMiner. I have used a few other miners and I feel that MM offers a very robust features and a super friendly gui

I'm seriously considering buying an Antminer S1 soon, but there's one thing that's worrying me about using it with MuM.  In theory, if I start using a S1, whatever pool I'm using will increase the difficulty to compensate.  Would this not cause my U1s to mine at a difficulty of around 200?  If so, would it not cause them to have issues keeping up?

No problem and it is not an issue.
I just happened to notice it tonight when I was stuck in bed and using MobileMiner to check on things.

Got it - thank you!

In MobileMiner I can see the temp of my Avalon like this screenshot.

But in any of my MultiMiner instances I cannot see it.

I hope this makes sense and I am not just exhausted and not seeing things correctly.

I think you meant MultiMiner with one of these? I'm not quite sure what you meant - do you think you could post a couple of screenshots?

Sorry to be a pain - I have so many things going on these days it's easiest if I have a picture of something visual to go off. Thanks for understanding! 

Another most likely obvious answer I cannot seem to find.
On MobileMiner when I go to my Avalon it shows the temp yet in MobileMiner any of them all on the same network as the Avalon the temp is not shown.
Is this a bug or am I missing a setting?

By the way I did not get to try the DualMiner version yet.  Spasms landed me in bed unfortunately.  I will attempt that tomorrow.
Thanks again Nate for the info.

It requires two instances of BFGMiner (or any other miner really). We have plans to try to improve this in the future to work with one instance.

So you'd flip the switch to B on the device and then launch an instance of BFGMiner with -S dualminer:all --scrypt and another with just -S dualminer:all.

I can give that a shot tomorrow. Going to turn in soon.

What are the commands to tell the Dualminer which pools to mine each "half" of itself to? Right now, I'm just running a single instance of BFGMiner with the Dualminer pointed to a single scrypt pool, and another instance with my more complex command lines for my SHA-256 devices with various failover pools, overclocking, etc.

Awesome - thanks! You are the first to test things I think 

If you feel like continuing to test - both modes should work. If you stop mining, remove the stick, switch it to B, and then plug it in you can then launch BFGMiner with --scrypt to mine at 30Kh/s Scrypt or without --scrypt to mine at 500Mh/s SHA-2.

fyi: this works.

Currently running two instances of BFGMiner on my pi: one for my SHA-256 devices, and one for the Dualminer. Everything seems to be working as expected.