Megaminer 6.3 - Multi pool / Multi Algo launcher

[woarang]

I have problem with benchmarking following 3 combinations:


ccminernice - groestl
ccminerdjm34 - lyra2z
ccminerskunk - timetravel.

Intervall stops before time runs out (after 100-200 sec), even so the miner is working fine, all other miners and algorithm worked.

[jbonifacio]

My issue with benchmarking seems to be MM doesn't know when it's completed benchmarking a given power level. If I let it run a few hours to benchmark a given power and restart it goes to the next level. I do this over and over until all power levels are completed and MM seems to run normally then.

[cable_loco]

@Tutulfo

Take a look on what ahashpool recommends in relation to 24 hour actuals in profit switching script:

Announcement: [2018-02-04 22:49 UTC] Please do not use 24 hour actuals in your profit switching script. When chain split happens, the pool will disable coins, or even disable the entire algo, and if you are using the past 24 hours actuals algo profit ranking to pick algo, you will be wasting your hash power. Bul wark just had a chain split, we disabled Bulwark but there are still 700+ miners on Nist5 after an hour, this tells us at least 700 rigs are doing it wrong. You should only use current estimates in determining your algo. And if you don't want it to switch too often, just increase the interval time. Do NOT use 24 hours actuals.

[tutulfo]

I have powerlevels set to 90,80,70,60 and mm has been benchmarking power 90 for over 10 hours. I see the stat files for the 1060 and 1070 (26 for each). Not sure why it's stuck on 90. I did start as Administrator.

*First all maximum power level will be benchmarked for all algos (90 for you).

*After that when a miner/algo will be running one interval as more profitable, others power limits for that combo will be benchmarked.


This avoid test all miners/algo combos on all power limits, only best are tested on other power limits than maximum.

[tutulfo]

Very unstable release for me.
1. ccminer alexis not working, but in release 5.2 alexis worrking stable.Copy ccminer alexis from 5.2 to 6.0b1 solve this problem.
2. Restarts intervals.I.e. miner starts and interval is 600sec. When 60-70-80-90sec ends, miner can restart with new interval count value.
3. Never ends benchmark (after closing MM and starts it again some miners can start benchmark again).
4. Excavator can't mine neoscrypt algo (when added in json file)."Cuda ERROR - Not enough of memory" message shown, but the same release of excavator separately works for me.
And how i can disable miningpoolhub for excavator only? It works for nicehash perfectly.
5. Can you add palgin hsr miner in next release? https://github.com/palginpav/hsrminer/tree/master/Neoscrypt%20algo/Windows , https://github.com/palginpav/hsrminer/tree/master/HSR%20algo/Windows
Excavator and palgin hsr miners are the best neoscrypt miners for Nvidia pascal based cards (compared with Klaust - about 10% difference).
Thank you!

1. I think no changes for alexis, did you copy miner file or bin content?
2. I will set lower watchdog sensibility
3. I´m testing this now
4. Compare json entrance file pls to see differences.
5. It is in Additional miners, read changelog before, this miner is a little....

[tutulfo]

I have problem with benchmarking following 3 combinations:


ccminernice - groestl
ccminerdjm34 - lyra2z
ccminerskunk - timetravel.

Intervall stops before time runs out (after 100-200 sec), even so the miner is working fine, all other miners and algorithm worked.

There is benchmark related bug, I think is related to watchdog sensibility and short benchmark interval duration, I´m testing.

[tutulfo]

@Tutulfo

Take a look on what ahashpool recommends in relation to 24 hour actuals in profit switching script:

Announcement: [2018-02-04 22:49 UTC] Please do not use 24 hour actuals in your profit switching script. When chain split happens, the pool will disable coins, or even disable the entire algo, and if you are using the past 24 hours actuals algo profit ranking to pick algo, you will be wasting your hash power. Bul wark just had a chain split, we disabled Bulwark but there are still 700+ miners on Nist5 after an hour, this tells us at least 700 rigs are doing it wrong. You should only use current estimates in determining your algo. And if you don't want it to switch too often, just increase the interval time. Do NOT use 24 hours actuals.

MM uses "estimate_last24h" api field, problem is "actual_last24h" field, confirmed by ahashpool support

[celofan]

Very unstable release for me.
1. ccminer alexis not working, but in release 5.2 alexis worrking stable.Copy ccminer alexis from 5.2 to 6.0b1 solve this problem.
2. Restarts intervals.I.e. miner starts and interval is 600sec. When 60-70-80-90sec ends, miner can restart with new interval count value.
3. Never ends benchmark (after closing MM and starts it again some miners can start benchmark again).
4. Excavator can't mine neoscrypt algo (when added in json file)."Cuda ERROR - Not enough of memory" message shown, but the same release of excavator separately works for me.
And how i can disable miningpoolhub for excavator only? It works for nicehash perfectly.
5. Can you add palgin hsr miner in next release? https://github.com/palginpav/hsrminer/tree/master/Neoscrypt%20algo/Windows , https://github.com/palginpav/hsrminer/tree/master/HSR%20algo/Windows
Excavator and palgin hsr miners are the best neoscrypt miners for Nvidia pascal based cards (compared with Klaust - about 10% difference).
Thank you!

1. I think no changes for alexis, did you copy miner file or bin content?
 
ccminer.exe only file

4. Compare json entrance file pls to see differences.

Solved by deleting doubled {"id":1,"method":"worker.add","params":["0","#GPUID#"]} string in ExcavatorPattern.txt file in pattern directory

5. It is in Additional miners, read changelog before, this miner is a little....
After excavator works stable no need palginpaw miner because best hashrate.

Did you disable miningpoolhub mining for excavator because 0.000000 hashrate?
P.S> aaronsace solved this issue in multipoolminer https://github.com/MultiPoolMiner/MultiPoolMiner/releases
Excavator works with miningpoolhub

[flipflop.0]

Very unstable release for me.
1. ccminer alexis not working, but in release 5.2 alexis worrking stable.Copy ccminer alexis from 5.2 to 6.0b1 solve this problem.
2. Restarts intervals.I.e. miner starts and interval is 600sec. When 60-70-80-90sec ends, miner can restart with new interval count value.
3. Never ends benchmark (after closing MM and starts it again some miners can start benchmark again).
4. Excavator can't mine neoscrypt algo (when added in json file)."Cuda ERROR - Not enough of memory" message shown, but the same release of excavator separately works for me.
And how i can disable miningpoolhub for excavator only? It works for nicehash perfectly.
5. Can you add palgin hsr miner in next release? https://github.com/palginpav/hsrminer/tree/master/Neoscrypt%20algo/Windows , https://github.com/palginpav/hsrminer/tree/master/HSR%20algo/Windows
Excavator and palgin hsr miners are the best neoscrypt miners for Nvidia pascal based cards (compared with Klaust - about 10% difference).
Thank you!

1. I think no changes for alexis, did you copy miner file or bin content?
2. I will set lower watchdog sensibility
3. I´m testing this now
4. Compare json entrance file pls to see differences.
5. It is in Additional miners, read changelog before, this miner is a little....

Hey tutulfo, first, thanks for the great miner and your developing.

I am having the same issues as celofan in 2. and 3., a new interval just starts too early. i have set benchmark and mining interval both to 600 in the config, but the new interval always starts after 1-3 minutes.

i did not have the issue in previous releases, so my guess is that a new or changed parameter is overriding the interval time from the config time.

another observation is that currently i am mining on 2 pools. one api is not responding, pool issue. but since the api is not responding, MM restarts the interval every few seconds. almost like an instant override of the interval time from the config

[tutulfo]

Very unstable release for me.
1. ccminer alexis not working, but in release 5.2 alexis worrking stable.Copy ccminer alexis from 5.2 to 6.0b1 solve this problem.
2. Restarts intervals.I.e. miner starts and interval is 600sec. When 60-70-80-90sec ends, miner can restart with new interval count value.
3. Never ends benchmark (after closing MM and starts it again some miners can start benchmark again).
4. Excavator can't mine neoscrypt algo (when added in json file)."Cuda ERROR - Not enough of memory" message shown, but the same release of excavator separately works for me.
And how i can disable miningpoolhub for excavator only? It works for nicehash perfectly.
5. Can you add palgin hsr miner in next release? https://github.com/palginpav/hsrminer/tree/master/Neoscrypt%20algo/Windows , https://github.com/palginpav/hsrminer/tree/master/HSR%20algo/Windows
Excavator and palgin hsr miners are the best neoscrypt miners for Nvidia pascal based cards (compared with Klaust - about 10% difference).
Thank you!

Try master branch code from github, some problems are solved.

1. I think no changes for alexis, did you copy miner file or bin content?
2. I will set lower watchdog sensibility
3. I´m testing this now
4. Compare json entrance file pls to see differences.
5. It is in Additional miners, read changelog before, this miner is a little....

Hey tutulfo, first, thanks for the great miner and your developing.

I am having the same issues as celofan in 2. and 3., a new interval just starts too early. i have set benchmark and mining interval both to 600 in the config, but the new interval always starts after 1-3 minutes.

i did not have the issue in previous releases, so my guess is that a new or changed parameter is overriding the interval time from the config time.

another observation is that currently i am mining on 2 pools. one api is not responding, pool issue. but since the api is not responding, MM restarts the interval every few seconds. almost like an instant override of the interval time from the config

[flipflop.0]

How did You solved the problem with GPU driver crashing when Megaminer shuts down miner app?
Is the solution maybe to make one dummy Afterburner profile (e.g profile5) that is CoreClock 0, MemoryClock -502, PowerLimit 70 and to load that profile 30 seconds before miner shuts down? Maybe there is some other way to change the overclock settings without need for Afterburner profile?
I don't know... All these miner/algo/pool changing apps are cool (Megaminer, Nemosminer, AwesomeMiner) but they are absolutely useless for me if the driver crashes and the rig is not mining until manual restart.
Rig restart function would be also good for this problem. (e.g I have 4 cards in rig, mining app detects only 3 then reboot).

Thank's and excuse me if there was any discussion on this topic.

I had that problem when experimenting with OC. Had it again when I got another card of the same brand and applied the sync function in AB.

The problem is very likely not related to any mining software but your OC or the cards drivers, from my experience. Did you alter the clock curve in the OC-software? Driver failure at miner shutdown usually appears when the voltage of your card drops and the lower voltage can not handle the load.

[tutulfo]

How did You solved the problem with GPU driver crashing when Megaminer shuts down miner app?
Is the solution maybe to make one dummy Afterburner profile (e.g profile5) that is CoreClock 0, MemoryClock -502, PowerLimit 70 and to load that profile 30 seconds before miner shuts down? Maybe there is some other way to change the overclock settings without need for Afterburner profile?
I don't know... All these miner/algo/pool changing apps are cool (Megaminer, Nemosminer, AwesomeMiner) but they are absolutely useless for me if the driver crashes and the rig is not mining until manual restart.
Rig restart function would be also good for this problem. (e.g I have 4 cards in rig, mining app detects only 3 then reboot).

Thank's and excuse me if there was any discussion on this topic.

I had that problem when experimenting with OC. Had it again when I got another card of the same brand and applied the sync function in AB.

The problem is very likely not related to any mining software but your OC or the cards drivers, from my experience. Did you alter the clock curve in the OC-software? Driver failure at miner shutdown usually appears when the voltage of your card drops and the lower voltage can not handle the load.

I have the same problem on all the 10 mining rigs i operate. :-( If I load factory defaults before closing miner, then driver stays in one piece.

Are you sure, that is the problem?, it´s easy for me add a feature (for NVIDIA) that gpu goes default before closing and restore oc after that.

[tutulfo]

Just loading defaults can be dangerous. Some GPU-s mining few algos can pull more power and can damage the PSU. Power limit is always in some range between 65 and 85. I'm in to test some new functionality, why not.

Going default for core and mem speed, powerlimit is not altered by this features (it´s altered by automatic powerlimit feature if enabled when is apropiated)

[shmeker]

Post the example config.txt pls... How to set suprnova and MPH username? I still reciving error!!!

[celofan]

After several tests I can say that there are certain problems with the excavator. When using an excavator on those algorithms that are supported by miningpoolhub, we get zero speed.
Therefore, you need to either force the excavator to work with miningpoolhub, or delete the algorithms that support miningpoolhub in the * .json file if you want use miningpoolhub.
Then I again ask you to include in the next release the miner from palgin for neoscrypt and hsr algos https://github.com/palginpav/hsrminer/tree/master/Neoscrypt%20algo/Windows
https://github.com/palginpav/hsrminer/tree/master/HSR%20algo/Windows
Because palgin the best miner at neoscrypt algo for pascal based cards and it works with miningpoolhub

[tutulfo]

After several tests I can say that there are certain problems with the excavator. When using an excavator on those algorithms that are supported by miningpoolhub, we get zero speed.
Therefore, you need to either force the excavator to work with miningpoolhub, or delete the algorithms that support miningpoolhub in the * .json file if you want use miningpoolhub.
Then I again ask you to include in the next release the miner from palgin for neoscrypt and hsr algos https://github.com/palginpav/hsrminer/tree/master/Neoscrypt%20algo/Windows
https://github.com/palginpav/hsrminer/tree/master/HSR%20algo/Windows
Because palgin the best miner at neoscrypt algo for pascal based cards and it works with miningpoolhub

Palgin miner for neoscrypt is included in additional miners folder

[celofan]

After several tests I can say that there are certain problems with the excavator. When using an excavator on those algorithms that are supported by miningpoolhub, we get zero speed.
Therefore, you need to either force the excavator to work with miningpoolhub, or delete the algorithms that support miningpoolhub in the * .json file if you want use miningpoolhub.
Then I again ask you to include in the next release the miner from palgin for neoscrypt and hsr algos https://github.com/palginpav/hsrminer/tree/master/Neoscrypt%20algo/Windows
https://github.com/palginpav/hsrminer/tree/master/HSR%20algo/Windows
Because palgin the best miner at neoscrypt algo for pascal based cards and it works with miningpoolhub

Palgin miner for neoscrypt is included in additional miners folder

WOW  
I definitely need to rest  

Sorry for my blindness
Thank you, I will test it.

UPD Working but show next message on screen:   + CategoryInfo          : ObjectNotFound: (C:\Megaminer-6.0b1\Wrapper_4068.txt:String) [Get-Content], ItemNotFoundException

UPD2 Not working   strange profit and speed showed

   + CategoryInfo          : ObjectNotFound: (C:\Megaminer-6.0b1\Wrapper_4068.txt:String) [Get-Content], ItemNotFoundException
GroupName MMPowLmt LocalSpeed   Rev./Day Rev./Day Profit/Day Algorithm Coin      Miner           Power Efficiency PoolSpeed Workers Loc. Pool
--------- -------- ----------   -------- -------- ---------- --------- ----      -----           ----- ---------- --------- ------- ---- ----
3x1080ti             0.0 ph/s 0.00000btc   0.0036     0.0036 NEOSCRYPT neoscrypt N-PalginNeoWrap  589W   0.0 ph/W  0.0 ph/s    1103 US   AHASH

UPD3 Working with N-PalginNeo.json file from "Not Compatibles with more than one gpu group of same type" directory

[Klein80]

Hello Friends,

i have a question...
This time i have 2 Rigs with total 18 NVDIA Cards.

I will buy to AMD Cards to working this 2 Rigs so i can make:

1x Rig = 9 x NVDIA + 9x AMD
1x Rig = 9 x NVDIA + 9x AMD

Megaminer have no problem working with mixed AMD/NVDIA Rig or?

Thank you

[tutulfo]

Hello Friends,

i have a question...
This time i have 2 Rigs with total 18 NVDIA Cards.

I will buy to AMD Cards to working this 2 Rigs so i can make:

1x Rig = 9 x NVDIA + 9x AMD
1x Rig = 9 x NVDIA + 9x AMD

Megaminer have no problem working with mixed AMD/NVDIA Rig or?

Thank you

No problem

[Klein80]

Fine.

Thank you