Topic: Megaminer 6.3 - Multi pool / Multi Algo launcher - page 23. (Read 70970 times)
How well does this fair with nvidia gpus? I know they generally are not ideal but does it support any algos that are decent for them?
thanks for the 5.0 release, will try that later tonight.
is there a way to use 24 hour profitability instead of current prof. from the pool? i'd like to reduce algo switching, but long interval times work better with profit calculated over a longer time (like the last 24 hours).
is there a way to use 24 hour profitability instead of current prof. from the pool? i'd like to reduce algo switching, but long interval times work better with profit calculated over a longer time (like the last 24 hours).
For interval, you can change this in the config file:
Code:
-- Profit recheck interval time (in seconds - less than 600 not recommended)
-- This interval recalculates and selects the most profitable algorithm
@@INTERVAL=600
-- This interval recalculates and selects the most profitable algorithm
@@INTERVAL=600
For using 24h profits, just change MiningMode from automatic to automatic24h in the bat file.
Hello,
Can´t mine LYRA2V2, hashrate is always 0
Using MPH
Have tried in 3 diferent rigs using nvidia GTX1060
here is an image
Any ideas on how to solve this?
Can´t mine LYRA2V2, hashrate is always 0
Using MPH
Have tried in 3 diferent rigs using nvidia GTX1060
here is an image
Any ideas on how to solve this?
Same for me in other algos with excavator...I have no idea, somebody?
Lyra2v2 is covered by other miners, you can delete excavator miner file.
thanks for the 5.0 release, will try that later tonight.
is there a way to use 24 hour profitability instead of current prof. from the pool? i'd like to reduce algo switching, but long interval times work better with profit calculated over a longer time (like the last 24 hours).
is there a way to use 24 hour profitability instead of current prof. from the pool? i'd like to reduce algo switching, but long interval times work better with profit calculated over a longer time (like the last 24 hours).
Hello,
Can´t mine LYRA2V2, hashrate is always 0
Using MPH
Have tried in 3 diferent rigs using nvidia GTX1060
here is an image
https://imgur.com/D5uMV1i
Any ideas on how to solve this?
Can´t mine LYRA2V2, hashrate is always 0
Using MPH
Have tried in 3 diferent rigs using nvidia GTX1060
here is an image
https://imgur.com/D5uMV1i
Any ideas on how to solve this?
5.0 Release
*Better miners "close" mechanism (safer and more agrresive)
*Enhanced dynamic api port assignation, now is possible to run more than one instance of MM without ports conflicts.
*Added Excavator for NVIDIA
*Added Ccminer Nanashi
*Added XMrig msvc for CPU
*Updated ccminer klaust to 8.16
*Updated claymore crypto to 11.0
*Added AMD gpu info on current screen (experimental)
*Fixed: pool not recovering from fail when multiple pools running
*Fixed: xmrcast not selecting devices
*Fixed: new zpool api profit units for keccak
*Fixed: automatic log folder deletion not working
*Fixed: ccminer polytmos not allowing more than one instance
THIS VERSION REQUIRES 5.0 FORMAT CONFIG.TXT FILE, IF YOU UPGRADE FROM 4.X RELEASE YOU MUST DOWNLOAD AND CONFIGURE AGAIN!!!
Hi, sorry, may I know the 5.0 release version consists of CPU miners? As I don't see any configuration params in the txt file.*Better miners "close" mechanism (safer and more agrresive)
*Enhanced dynamic api port assignation, now is possible to run more than one instance of MM without ports conflicts.
*Added Excavator for NVIDIA
*Added Ccminer Nanashi
*Added XMrig msvc for CPU
*Updated ccminer klaust to 8.16
*Updated claymore crypto to 11.0
*Added AMD gpu info on current screen (experimental)
*Fixed: pool not recovering from fail when multiple pools running
*Fixed: xmrcast not selecting devices
*Fixed: new zpool api profit units for keccak
*Fixed: automatic log folder deletion not working
*Fixed: ccminer polytmos not allowing more than one instance
THIS VERSION REQUIRES 5.0 FORMAT CONFIG.TXT FILE, IF YOU UPGRADE FROM 4.X RELEASE YOU MUST DOWNLOAD AND CONFIGURE AGAIN!!!
included on Config.txt
-- Use your cpu to mine: ENABLED = yes, DISABLED = no (you can start cpu alone mining also using -groupnames parameter in batch file)
@@CPUMINING=DISABLED
5.0 Release
*Better miners "close" mechanism (safer and more agrresive)
*Enhanced dynamic api port assignation, now is possible to run more than one instance of MM without ports conflicts.
*Added Excavator for NVIDIA
*Added Ccminer Nanashi
*Added XMrig msvc for CPU
*Updated ccminer klaust to 8.16
*Updated claymore crypto to 11.0
*Added AMD gpu info on current screen (experimental)
*Fixed: pool not recovering from fail when multiple pools running
*Fixed: xmrcast not selecting devices
*Fixed: new zpool api profit units for keccak
*Fixed: automatic log folder deletion not working
*Fixed: ccminer polytmos not allowing more than one instance
THIS VERSION REQUIRES 5.0 FORMAT CONFIG.TXT FILE, IF YOU UPGRADE FROM 4.X RELEASE YOU MUST DOWNLOAD AND CONFIGURE AGAIN!!!
Hi, sorry, may I know the 5.0 release version consists of CPU miners? As I don't see any configuration params in the txt file. *Better miners "close" mechanism (safer and more agrresive)
*Enhanced dynamic api port assignation, now is possible to run more than one instance of MM without ports conflicts.
*Added Excavator for NVIDIA
*Added Ccminer Nanashi
*Added XMrig msvc for CPU
*Updated ccminer klaust to 8.16
*Updated claymore crypto to 11.0
*Added AMD gpu info on current screen (experimental)
*Fixed: pool not recovering from fail when multiple pools running
*Fixed: xmrcast not selecting devices
*Fixed: new zpool api profit units for keccak
*Fixed: automatic log folder deletion not working
*Fixed: ccminer polytmos not allowing more than one instance
THIS VERSION REQUIRES 5.0 FORMAT CONFIG.TXT FILE, IF YOU UPGRADE FROM 4.X RELEASE YOU MUST DOWNLOAD AND CONFIGURE AGAIN!!!
5.0 Release
*Better miners "close" mechanism (safer and more agrresive)
*Enhanced dynamic api port assignation, now is possible to run more than one instance of MM without ports conflicts.
*Added Excavator for NVIDIA
*Added Ccminer Nanashi
*Added XMrig msvc for CPU
*Updated ccminer klaust to 8.16
*Updated claymore crypto to 11.0
*Added AMD gpu info on current screen (experimental)
*Fixed: pool not recovering from fail when multiple pools running
*Fixed: xmrcast not selecting devices
*Fixed: new zpool api profit units for keccak
*Fixed: automatic log folder deletion not working
*Fixed: ccminer polytmos not allowing more than one instance
THIS VERSION REQUIRES 5.0 FORMAT CONFIG.TXT FILE, IF YOU UPGRADE FROM 4.X RELEASE YOU MUST DOWNLOAD AND CONFIGURE AGAIN!!!
*Better miners "close" mechanism (safer and more agrresive)
*Enhanced dynamic api port assignation, now is possible to run more than one instance of MM without ports conflicts.
*Added Excavator for NVIDIA
*Added Ccminer Nanashi
*Added XMrig msvc for CPU
*Updated ccminer klaust to 8.16
*Updated claymore crypto to 11.0
*Added AMD gpu info on current screen (experimental)
*Fixed: pool not recovering from fail when multiple pools running
*Fixed: xmrcast not selecting devices
*Fixed: new zpool api profit units for keccak
*Fixed: automatic log folder deletion not working
*Fixed: ccminer polytmos not allowing more than one instance
THIS VERSION REQUIRES 5.0 FORMAT CONFIG.TXT FILE, IF YOU UPGRADE FROM 4.X RELEASE YOU MUST DOWNLOAD AND CONFIGURE AGAIN!!!
I'm testing the master-copy on github and it seems to be working.
btw would it be possible to add back the auto speed updating feature found in the original MPM?
Also would it be possible to set a profit switching threshold (in %)?
btw would it be possible to add back the auto speed updating feature found in the original MPM?
Also would it be possible to set a profit switching threshold (in %)?
Switching threshold will be in next release, I wnat to close 5.0 stable release before.
What is Auto speed updating?
Auto speed updating is updating hashrate stat files while in mining process , either implement second value or simply overwrite initial profiling value periodically.
Inital profiling isnt particulary accurate , it shaves off quite some margin using 200 sec profiling. So when profiling rig i have to manually enter actual values and usualy thos are quite a bit higher , than written after profiling period.
This was implemented releases ago but some miners sometimes send hashrates peaks, until you see and correct that miner/algo was always running.
I deactivated this option to check only one time stats are right after benchmark
I'm testing the master-copy on github and it seems to be working.
btw would it be possible to add back the auto speed updating feature found in the original MPM?
Also would it be possible to set a profit switching threshold (in %)?
btw would it be possible to add back the auto speed updating feature found in the original MPM?
Also would it be possible to set a profit switching threshold (in %)?
Switching threshold will be in next release, I wnat to close 5.0 stable release before.
What is Auto speed updating?
Auto speed updating is updating hashrate stat files while in mining process , either implement second value or simply overwrite initial profiling value periodically.
Inital profiling isnt particulary accurate , it shaves off quite some margin using 200 sec profiling. So when profiling rig i have to manually enter actual values and usualy thos are quite a bit higher , than written after profiling period.
yes and don't update (give an error message) if the hash rate is outside of the tolerance
I'm testing the master-copy on github and it seems to be working.
btw would it be possible to add back the auto speed updating feature found in the original MPM?
Also would it be possible to set a profit switching threshold (in %)?
btw would it be possible to add back the auto speed updating feature found in the original MPM?
Also would it be possible to set a profit switching threshold (in %)?
Switching threshold will be in next release, I wnat to close 5.0 stable release before.
What is Auto speed updating?
Auto speed updating is updating hashrate stat files while in mining process , either implement second value or simply overwrite initial profiling value periodically.
Inital profiling isnt particulary accurate , it shaves off quite some margin using 200 sec profiling. So when profiling rig i have to manually enter actual values and usualy thos are quite a bit higher , than written after profiling period.
I'm testing the master-copy on github and it seems to be working.
btw would it be possible to add back the auto speed updating feature found in the original MPM?
Also would it be possible to set a profit switching threshold (in %)?
btw would it be possible to add back the auto speed updating feature found in the original MPM?
Also would it be possible to set a profit switching threshold (in %)?
Switching threshold will be in next release, I wnat to close 5.0 stable release before.
What is Auto speed updating?
I'm testing the master-copy on github and it seems to be working.
btw would it be possible to add back the auto speed updating feature found in the original MPM?
Also would it be possible to set a profit switching threshold (in %)?
btw would it be possible to add back the auto speed updating feature found in the original MPM?
Also would it be possible to set a profit switching threshold (in %)?
yeah thos two are on top of wishlist too , imho must have features
I'm testing the master-copy on github and it seems to be working.
btw would it be possible to add back the auto speed updating feature found in the original MPM?
Also would it be possible to set a profit switching threshold (in %)?
btw would it be possible to add back the auto speed updating feature found in the original MPM?
Also would it be possible to set a profit switching threshold (in %)?
Getting a lot of these with beta 4 (including today's updates) - not seeing this with beta3 nor am I getting this error with Hash Refinery, just AHASHPOOL:
PS>TerminatingError(Invoke-WebRequest): "The operation has timed out."
PS>TerminatingError(Invoke-WebRequest): "The operation has timed out."
AHASHPOOL API NOT RESPONDING...ABORTING
NO POOLS!....retry in 10 sec
REMEMBER, IF YOUR ARE MINING ON ANONYMOUS WITHOUT AUTOEXCHANGE POOLS LIKE YIIMP, NANOPOOL, ETC. YOU MUST SET WALLET FOR AT LEAST ONE POOL COIN IN CONFIG.TXT
Next Interval: 599 secs...
PS>TerminatingError(Invoke-WebRequest): "The operation has timed out."
PS>TerminatingError(Invoke-WebRequest): "The operation has timed out."
AHASHPOOL API NOT RESPONDING...ABORTING
NO POOLS!....retry in 10 sec
REMEMBER, IF YOUR ARE MINING ON ANONYMOUS WITHOUT AUTOEXCHANGE POOLS LIKE YIIMP, NANOPOOL, ETC. YOU MUST SET WALLET FOR AT LEAST ONE POOL COIN IN CONFIG.TXT
Next Interval: 599 secs...
I get these randomly from ahashpool and that is also why I use no less than 2 pools in the config, just wish there was a way to define a primary pool then a failover until the primary returns.
Getting a lot of these with beta 4 (including today's updates) - not seeing this with beta3 nor am I getting this error with Hash Refinery, just AHASHPOOL:
PS>TerminatingError(Invoke-WebRequest): "The operation has timed out."
PS>TerminatingError(Invoke-WebRequest): "The operation has timed out."
AHASHPOOL API NOT RESPONDING...ABORTING
NO POOLS!....retry in 10 sec
REMEMBER, IF YOUR ARE MINING ON ANONYMOUS WITHOUT AUTOEXCHANGE POOLS LIKE YIIMP, NANOPOOL, ETC. YOU MUST SET WALLET FOR AT LEAST ONE POOL COIN IN CONFIG.TXT
Next Interval: 599 secs...
PS>TerminatingError(Invoke-WebRequest): "The operation has timed out."
PS>TerminatingError(Invoke-WebRequest): "The operation has timed out."
AHASHPOOL API NOT RESPONDING...ABORTING
NO POOLS!....retry in 10 sec
REMEMBER, IF YOUR ARE MINING ON ANONYMOUS WITHOUT AUTOEXCHANGE POOLS LIKE YIIMP, NANOPOOL, ETC. YOU MUST SET WALLET FOR AT LEAST ONE POOL COIN IN CONFIG.TXT
Next Interval: 599 secs...
I've started work on the GUI (pretty raw currently).
If anyone would like to contribute (looking for people that know C# in any capacity) please send me a PM and we can talk.
I've also go ahead and setup a Slack server, and once Tutu sends me his details I'll hand over ownership.
If anyone would like to contribute (looking for people that know C# in any capacity) please send me a PM and we can talk.
I've also go ahead and setup a Slack server, and once Tutu sends me his details I'll hand over ownership.
I'm the only one who's CCminer crash on benchmark ?
what does it do?
https://www.evernote.com/l/ABjcLTCVjxRAxKVAumrSl-jFtgx4ewIE27g
CCminer crash
Set memory overclock to 0
That's what resolved my ccminer memory crash issues.
Where I can set this value ?
If you dont know where find it, I can assume you have not change it before.
Try delete bin folder content, this get miners download again.
I'm the only one who's CCminer crash on benchmark ?
what does it do?
https://www.evernote.com/l/ABjcLTCVjxRAxKVAumrSl-jFtgx4ewIE27g
CCminer crash
Set memory overclock to 0
That's what resolved my ccminer memory crash issues.
Where I can set this value ?
I found X17 sgminer here: https://mega.nz/#!Udpl1AaJ!d49cP3X5O8ROnKxjp2UNldpro0OKN099GeB10WGwh304
but it's not worth to use it, testet on RX560 with -G2 -I19 gives ~300Kh/s
but it's not worth to use it, testet on RX560 with -G2 -I19 gives ~300Kh/s
Jump to: