Topic: [ANN] Miner Control 1.6.1 - Auto profit switching miner controller - page 45. (Read 164304 times)

How about trying the issue tracker over at GitHub? link

It may be able to handle longer text.  You probably don't need to include the entire file either, just the last 10 minutes or so.  Most of the file is probably failed connects to the remote API providers.

For NiceHash you need to use sgminer.   https://bitcointalksearch.org/topic/m.9459003

Here is my conf for it for my 750 ti

Bug report time.
I think I may have caught a crash, though I'm not sure since I was at work when it occurred.  Still, I have logs that look like they go right up to the time of the apparent crash.  In addition, it looks like the Miner Control crash also caused the crash (or perhaps just closure) of numerous other processes running…my desktop was devoid of all apps and/or windows when I got home, including several background tasks (had to reboot my PC to get everything back up & running).  The log is rather lengthy, so you may want to grab a snack & a drink before diving in:
Apparently the logs are too long for this message board to handle properly.  Let me know another way of getting them to you, and I'll send them that way. 

Done and released as version 1.5.3.

Perhaps with it's own inactivity timer, or perhaps if the GPU activity is lower than a certain percentage for a certain time (all configurable by .conf?) it starts. The same could apply for CPU. It would not deactivate when you would resume normal use, but you'd just have to check for that.

and TMB - NeoScrypt Port 8880

Please, add NeoScrypt for NiceHash.
https://www.nicehash.com/index.jsp?p=allorders&a=8

I had tabled the idea a while back when I noticed that every time Miner Control stopped one miner and started another it would bring the computer out of screen saver mode.  Appeared to be related to opening a new window.  Since I put in the internal console I haven't seen that behavior so it may be worth revisiting the idea.  I did a little bit of research on how to detect the screen saver but it looked at the time like the techniques were a bit hit or miss.  I'll have to look into it again.

still not authenticating
is there an api code or something? I can ping the url...
I'm using cudaminer-2014-02-28

Tried using they're proxy server and all I can say is WTF
2014-11-06 14:35:54,748 INFO     [main]:strat.mining.stratum.proxy.Launcher - Us
ing pools: [Pool [name=Nicehash Scrypt, host=stratum.nicehash.com:3333, username
=BTC, password=x, readySince=null, isReady=false,
 isEnabled=true, isStable=false, priority=0, weight=1], Pool [name=Westhash Scry
pt, host=stratum.westhash.com:3333, username=3P7rDh9L5BHamWQNCmNNu1jffBHczgmLjC,
 password=x, readySince=null, isReady=false, isEnabled=true, isStable=false, pri
ority=1, weight=1]].

StuffOfInterest, some time ago, you talked about an option that would automatically start the miner when the screensaver got activated, or something similar. How's that coming along? I sometimes forget to turn on the miner, and when I come back after an hour and see that my PC was just idling, it is pretty annoying.

[slap] duh, thanks.

Well, Scrypt-N is back in the gutter so hopefully ccminer is working for you on the X protocols now.

I think your problem may have been a local security issue keeping cudaminer from talking to the nicehash server.  Try this.  Open a command prompt window, change to the directory where you have cudaminer, and paste in this command:


Replace the wallet number and then hit enter.  You may end up seeing a popup warning about communicating on the network.  If you do, select the option to always allow this.

If all this works right, you should be able to go back to Miner Control, stop whatever miner you have running, and then manually start Scrypt-N on NiceHash.

One more thing you can try is the "usewindow" option to force the miner into a separate command window instead of running inside of Miner Control.  I don't have to do that for cudaminer but your mileage may vary.

GTX 980s

Well, there's your problem!

You won't get very far using cudaminer with AMD cards.  It only works with nVIDIA CUDA cards.  You probably want to look at sgminer.

2x 980s

The prob is  that I am not authenticating via stratum. Westhash, nicehash  for some reason isn't accepting a connection.

Starting NiceHash X11 with CCMiner.exe -a x11 -o stratum+tcp://stratum.nicehash.com:3336 -u BTC.1 -p
option requires an argument -- p
*** ccMiner for nVidia GPUs by Christian Buchner and Christian H. ***
Try `ccminer --help' for more information.
    This is the forked version 1.4.4 (tpruvot@github)
     Built with VC++ 2013 and nVidia CUDA SDK 6.5

     based on pooler-cpuminer 2.3.2 (c) 2010 Jeff Garzik, 2012 pooler
       and HVC extension from http://hvc.1gh.com/

   Cuda additions Copyright 2014 Christian Buchner, Christian H.

   Include some of djm34 additions, cleaned by Tanguy Pruvot
     BTC donation address: 1AJdfCpLWPNoAMDfHF1wD5y8VgKSSTHxPo

added difficulty and now ggetting this

[19:17:42] Starting NiceHash X11 with CCMiner.exe -a x11 -o stratum+tcp://stratum.nicehash.com:3336 -u BTCx.1 -p d=0.16
[2014-11-05 19:17:42] Starting Stratum on stratum+tcp://stratum.nicehash.com:3336
[2014-11-05 19:17:42] Binding thread 0 to cpu 0
[2014-11-05 19:17:42] Binding thread 1 to cpu 1
[2014-11-05 19:17:42] 2 miner threads started, using 'x11' algorithm.
[2014-11-05 19:17:43] Stratum authentication failed
[2014-11-05 19:17:43] ...retry after 30 seconds
[2014-11-05 19:17:43] GPU #0: GeForce GTX 980, 3197 kH/s
[2014-11-05 19:17:43] GPU #1: GeForce GTX 980, 3102 kH/s
[2014-11-05 19:18:09] GPU #0: GeForce GTX 980, 7605 kH/s
[2014-11-05 19:18:10] GPU #1: GeForce GTX 980, 7112 kH/s
[2014-11-05 19:18:13] GPU #0: GeForce GTX 980, 7630 kH/s
[2014-11-05 19:18:13] GPU #1: GeForce GTX 980, 7131 kH/s
[2014-11-05 19:18:13] Stratum authentication failed
[2014-11-05 19:18:13] ...retry after 30 seconds
[2014-11-05 19:18:43] GPU #1: GeForce GTX 980, 7078 kH/s
[2014-11-05 19:18:43] GPU #0: GeForce GTX 980, 7609 kH/s
[2014-11-05 19:18:44] Stratum authentication failed
[2014-11-05 19:18:44] ...retry after 30 seconds
[2014-11-05 19:19:14] GPU #0: GeForce GTX 980, 7670 kH/s
[2014-11-05 19:19:14] GPU #1: GeForce GTX 980, 7100 kH/s
[2014-11-05 19:19:14] Stratum authentication failed
[2014-11-05 19:19:14] ...retry after 30 seconds

As long as you have two video cards this looks fine.  Very close to what I have mining against westhash right now.

I've been stuck trying to config cudaminer all night for scrypt. for whatever reason it's most profit tonight. Nicehash keeps saying strutum auth failed. My config is as follows.
this is what MC spits out

[18:29:36] Starting NiceHash Scrypt-N with F:\P\MinerControl-1.2.2\cudaminer.exe -a scrypt:2048 -d 0,1 -o stratum+tcp://stratum.nicehash.com:3335 -u [#real wallet#].1 -p x
[2014-11-05 18:29:36] Starting Stratum on stratum+tcp://stratum.nicehash.com:3335
[2014-11-05 18:29:36] 2 miner threads started, using 'scrypt' algorithm.
[2014-11-05 18:29:37] Stratum authentication failed
[2014-11-05 18:29:37] ...retry after 15 seconds


What am I missing?

In a case like this I'd apply a less than 1 weighting on tmb to adjust for any over reporting they may do.

I've noticed a discrepancy among the payouts between trademybit and yaamp. Trademybit always seems to one-up yaamp by a percent. But when I look at time mined vs payout in miner control, it seems like I put in more time and less payout than yaamp. Is this because of auto-exchange or are the numbers getting jacked around when miner control is calculating profits. I remember reading something on trademybit that the exchange value is only calculated at the time of the exchange which is probably later than the mining for alt coin occurred. This seems a little sketchy.

I received an e-mail this morning that NiceHash has been under a major DDOS attack again.  It could be that some of the other services are suffering similar attacks.  The APIs for prices are called once a minute independent of each other.  If one service stalls it should not affect any others being able to get pricing.  If a service has pricing but MC is unable to contact the pricing API for 30 minutes then the prices are set back to 0 to avoid working from stale data.