Topic: [Awesome Miner] - Powerful Windows GUI to manage and monitor up to 200000 miners - page 539. (Read 703512 times)

I don't use the profit profile switching either for that reason it never really seems to work right , nothing against Awesome or patrike he seems good at what he does, i won't use anything else but AM to monitor with, right now .

But AM does have some set backs again nothing against Patrike or AM, if i did have issue with the software or your skills, i wouldn't use it... unless i had to like CGMINer, i don't care much for and am forced to use in some miners ..when BFG works just as good but they won't support it .

I´m wondering how reliable the profit profile switching is and if it picks the right coin to mine. The numbers jump from $5 per day to $0.8 per day.
I´ve tested Awesome Miner with 2x GTX 1070 and the software reported a profit of $2 per day wheras Nicehash generates $2.90 per day. The profile groups show also weird results. I´ve benchmarked one GTX 1070 and saved the profile. When selecting that profile in the Coins tab it shows $1.70 profit per day. Then I created a profile group, added the single GPU profile and set the profile count to 2. When I select the group profile the profit jumps to $11 per day. Honestly, the software looks great and has amazing features, but those weird numbers make me doubt.

/Doc

Yes I have 4 AMD cards mining ETH/DCR and 2 Nvidia mining ZEC.  All six devices are mapped to system monitoring.

Both miners show the total number of accepted shares correctly, it's just that the GPU list below shows zeroes for the AMDs.   I figured if the total is known the per-GPU value should be known as well.  Not a big deal, I can always look at the Claymore window if I need to know those values.

Just a suggestion but if some values are not available then I would prefer to see them shown as N/A or blanked out rather than see a zero.  Zero is not the real value.

@Dev

it qould be nice if i could add some kind of description or comments to each miner

also it qould be perfect if there where any kind of team viewer integration (add a field for the teamviewer id and right click to connect).

thanks so far for this great piece of software

Im new to this software and mining,  i got a baikal giant plus and should i trust the profitability estimation in the online service of zpool x13 for profit switching?

Hi,

just buying the pro version. Everything looks fine but i cant connect to any miner with EWBF Cuda Zcash mining. API is enabled on standardport, status webpage is shown. But Awesome is responding "Failed to connect".

Changing to other port is the same.

API Report
Version: 4.0.2
API command: {"id":1, "method":"getstat"}

Any ideas?

Thanks

After setting --api 0.0.0.0:42000 and 2 minutes waiting (?) everything is sortet out now.

Hey patrike,

I've finally got a profit switching miner going nicely, and it truly is 'awesome'.  I love it, except for one thing.  I can't see a way to change GPU clock/mem settings before each algo switch.  

The hashrate difference between the least and most optimal GPU setting can be quite big, or a setting will run fine with one miner/algo, but crash with another.  I don't need MSI Afterburner integration or any of the extra features that come with the expensive versions.  All I need is a way to run a few batch commands before each miner & algo starts.  Like -

nvidiaInspector.exe -setBaseClockOffset:0,0,140 -setMemoryClockOffset:0,0,600 -setPowerTarget:0,75 -setTempTarget:2,0,83

I can see the option for batch commands with managed miners, but not with a profit switching miner.  It would be nice if there was an option in the Algorithms section to run batch commands before each algo.  Without this function I have to either run the GPU's at lower clock settings and lose profit, or manually run a batch file with optimal settings every time AM switches algo's.  Most miners have options to set clocks, but they can't query 10 series cards.  I'm happy to pay for this program, but I'm mining mostly for fun with just 4 cards.  I don't need all the features that come with the expensive versions.  Just a way to change GPU settings.  

Cheers.

go to GPU tab make sure you have Map to system monitoring on using claymore .... I'm guessing your mining ZEC/zcash and using Claymore for the AMD cards ?.

That Might be why you don't see the AMD Card/s shares but do for the NV card sense Claymore zec miner doesn't support NV cards .
you have to use a different Software miner for the NV card/s mining Zec/zcash.. that has API access and Claymore doesn't have API access.




other wise, no idea why, mine all ways show when i turn on Map to system monitoring.

On the GPUs tab in Awesome Miner my AMD cards are showing 0 for the Accepted progress even though I have plenty of accepted shares that show in the Miners list above it.  My Nvidia cards show the Accepted values ok.

Bug?

Yeah! really ty!!

Good idea, i will try.

About xnsub, don't know if it's work correctly with Nicehash.
on one in FAS, they say add /#xnsub and another just #xnsub.... in URL...


EDIT: Perfect it's worked. Thanks you.

Its not right away. Its only using cc miner and I noticed that I saw once it said "cc miner has stopped working" and that was right after setting gpu intensities.

This one doesn't indicate any crash as you also pointed out. When it crashes, is it right away when the mining starts or after a while?
Maybe it was another mining software or algorithm when it crashed. You could run the Diagnostics right away after it crashes next time to see if there are any difference in the output.

In general, crashes has very little to do with Awesome Miner as it only launches the different mining software. There can always be compatibility issues between different GPUs, clocking settings, drivers, systems and specific mining software or algorithms.

You can use the Rules in Awesome Miner to detect low hashrate. You can see an example of this in the section "Example: Show notification on low hashrate" on this page:
http://www.awesomeminer.com/help/rules.aspx
The example is only showing a notification, but you can also add an action of the type "Miner Command" and set it to Restart or Reboot.

I ran diagnostics not showing anything bad.
I also reduced power to 80% still same thing is happening. I dont know what to do. Its very frustrating.


Starting Diagnostics
Starting Mining Software
Setting up Miner Engine. Instance: 1
Engine Type: CcMiner, Auto Download: True, EnginePath: , Subtype: Disabled, CustomExecutable:
Added rule for: C:\Users\Rig2\AppData\Roaming\AwesomeMinerService\ccminer-2.2_1\ccminer-2.2\ccminer-x64.exe
C:\Users\Rig2\AppData\Roaming\AwesomeMinerService\ccminer-2.2_1\ccminer-2.2\ccminer-x64.exe  -a lyra2v2 -o stratum+tcp://lyra2v2.mine.zpool.ca:4533 -u 1GtNWJLVDQHHmvmE4HwrTyUkU5pRTLNeED -p x -b 0.0.0.0:4028   (WindowMode: ConsoleFormat, EngineType: CcMiner)
Configuration:

Mining Engine Process started, PID: 4692

====================================================================================================
> *** ccminer 2.2 for nVidia GPUs by tpruvot@github ***
>     Built with VC++ 2013 and nVidia CUDA SDK 8.0 64-bits
>
>   Originally based on Christian Buchner and Christian H. project
>   Include some algos from alexis78, djm34, sp, tsiv and klausT.
>
> BTC donation address: 1AJdfCpLWPNoAMDfHF1wD5y8VgKSSTHxPo (tpruvot)
>
> [2017-09-24 10:04:49] Starting on stratum+tcp://lyra2v2.mine.zpool.ca:4533
> [2017-09-24 10:04:49] NVML GPU monitoring enabled.
> [2017-09-24 10:04:49] NVAPI GPU monitoring enabled.
> [2017-09-24 10:04:49] 8 miner threads started, using 'lyra2v2' algorithm.
> [2017-09-24 10:04:50] Stratum difficulty set to 64 (0.25000)
> [2017-09-24 10:04:50] lyra2v2 block 794692, diff 25795.206
> [2017-09-24 10:04:50] API open to the network in read-only mode on port 4028
> [2017-09-24 10:04:51] GPU #1: Intensity set to 20, 1048576 cuda threads
> [2017-09-24 10:04:51] GPU #3: Intensity set to 20, 1048576 cuda threads
> [2017-09-24 10:04:51] GPU #5: Intensity set to 20, 1048576 cuda threads
> [2017-09-24 10:04:51] GPU #7: Intensity set to 20, 1048576 cuda threads
> [2017-09-24 10:04:51] GPU #2: Intensity set to 20, 1048576 cuda threads
> [2017-09-24 10:04:51] GPU #0: Intensity set to 20, 1048576 cuda threads
> [2017-09-24 10:04:51] GPU #6: Intensity set to 20, 1048576 cuda threads
> [2017-09-24 10:04:51] GPU #4: Intensity set to 20, 1048576 cuda threads
> [2017-09-24 10:04:55] GPU #5: EVGA GTX 1070, 1035.13 kH/s
> [2017-09-24 10:04:55] GPU #7: Gigabyte GTX 1070, 1035.13 kH/s
> [2017-09-24 10:04:55] GPU #1: EVGA GTX 1070, 987.04 kH/s
> [2017-09-24 10:04:55] GPU #3: EVGA GTX 1070, 924.75 kH/s
> [2017-09-24 10:04:55] GPU #4: EVGA GTX 1070, 923.93 kH/s
> [2017-09-24 10:04:55] GPU #6: Gigabyte GTX 1070, 909.73 kH/s
> [2017-09-24 10:04:55] GPU #0: EVGA GTX 1070, 895.71 kH/s
> [2017-09-24 10:04:56] GPU #2: EVGA GTX 1070, 883.60 kH/s
> [2017-09-24 10:04:57] accepted: 1/1 (diff 0.537), 107.62 MH/s yes!
> [2017-09-24 10:05:01] GPU #5: EVGA GTX 1070, 25.10 MH/s
> [2017-09-24 10:05:01] accepted: 2/2 (diff 0.452), 197.93 MH/s yes!

====================================================================================================
Stopping miner process ...
Stopping Mining Software
Diagnostics completed

Yes i have 1070s card, but i'm not talking about ewbf's problem, i'm asking if awesome miner should know when the 0sol error appears and restart the miner.

How hard are you pushing your rig?  From the picture, your GPUs are pushing 480+ sols... sounds like you have GTX 1070s or maybe 1080s... but are pushing them way too hard.  Thus, the GPUs are crashing and EWBF is trying to recover.  Back off your power limits and or overclocks 5% here and there until you have a stable rig.  You can use Awesome Miner (if you have the correct edition) to control Afterburner Server... this will allow you to control GPU/Mem clocks, and power limit.

Well... 8x 1070s running at full power limit will be 1200W.  Add in say 150W for the rest of the system, and you are at 1350.  You are running the PSU at 85% of it's maximum load.  I'd back the power limit down to 80% using Afterburner to give your PSU a little more breathing room.

no other software, but this is a "normal" problem of ewbf, happen on all my miner random.

Thanks for the suggestion. This could be an improvement for future versions.