Topic: Excavator GUI by cTnko - Miner Interface for beginners and advanced users [0.9] (Read 11408 times)
July 30, 2018, 09:49:06 PM
This can be used with the latest Nicehash Excavator yet?
February 23, 2018, 08:19:14 AM
Hopefully this awesome GUI gets update to latest excavator. This is so easy and fast to use.
For developer: Put your BTC address I would like to donate for Excavator GUI by cTnko program developer(s)
For developer: Put your BTC address I would like to donate for Excavator GUI by cTnko program developer(s)
February 13, 2018, 07:02:52 PM
very good sofwtare indeed.
Any plan to integrate the gui by adding other mining software on the AMD side ?
Then , an explanation needed: what exactly are the efficiency on the top right corner ?
How can you calculate the power from Nvidia if there is no sensor ?
Any plan to integrate the gui by adding other mining software on the AMD side ?
Then , an explanation needed: what exactly are the efficiency on the top right corner ?
How can you calculate the power from Nvidia if there is no sensor ?
February 08, 2018, 07:24:00 AM
Great software, would love to see an update, including some of the more popular algorithms.
I hope this would be possible as your software is literally the best GUI i have seen for any miner. period.
Please update this project!
I hope this would be possible as your software is literally the best GUI i have seen for any miner. period.
Please update this project!
December 24, 2017, 11:45:07 PM
Just wanted to say thank you for an excellent piece of software. I consider myself to be somewhat intelligent, but COULD NOT get any of the nvidia miners to work for more than a few seconds before exiting. Your software works perfectly, and I'm mining Zcash like a champ.
-Jake
-Jake
August 22, 2017, 11:12:34 AM
cTnko
i am starting to use your GUI, but the OC feature is not working for me on my 1080`s evga dt. it change the TDP and fan speeds but the memori clocks or gpu clocks arent working i am using the lastes driver for nvidia
i am starting to use your GUI, but the OC feature is not working for me on my 1080`s evga dt. it change the TDP and fan speeds but the memori clocks or gpu clocks arent working i am using the lastes driver for nvidia
That's interesting and definitely shouldn't be happening, which driver version are you currently running ?
Have you also tried setting the overclock through the config file (with just regular excavator, without the GUI)?
That should tell us more (if the issue is on the GUI side or excavator side).
August 19, 2017, 06:38:04 PM
cTnko
i am starting to use your GUI, but the OC feature is not working for me on my 1080`s evga dt. it change the TDP and fan speeds but the memori clocks or gpu clocks arent working i am using the lastes driver for nvidia
i am starting to use your GUI, but the OC feature is not working for me on my 1080`s evga dt. it change the TDP and fan speeds but the memori clocks or gpu clocks arent working i am using the lastes driver for nvidia
July 31, 2017, 05:26:50 PM
It seems since I ran the Excavator GUI that Claymore doesn't read out the temperatures of the GPU's anymore. All I see is GPU0 t=0C fan=0% for bot GPU's.
I guess this should go away after you reboot the machine, this is definitely a bug in the Excavator and you should report it
Here https://bitcointalk.org/index.php?topic=1777827.new#new
or here https://github.com/nicehash/excavator/issues
@Daywalker22 If you are asking about profitability switching, no that is not supported right now.
July 31, 2017, 09:38:29 AM
Hey,
It is also possible to set something like auto switch? Like nicehash has?
Or you can only mine in a direct pool?
It is also possible to set something like auto switch? Like nicehash has?
Or you can only mine in a direct pool?
July 31, 2017, 03:35:39 AM
It seems since I ran the Excavator GUI that Claymore doesn't read out the temperatures of the GPU's anymore. All I see is GPU0 t=0C fan=0% for bot GPU's.
July 31, 2017, 01:40:31 AM
Which GPUs were affected by this problem, also have you tinkered with the overclocking inside of the GUI ?
I'm using two Sapphire R9 380 4Gb Nitro GPU's and I haven't touched the overclocking in the GUI.
July 30, 2017, 06:35:09 PM
I'm back 
AMD fan problem solved.
10 Min run seams ok.
Tanks.
AMD fan problem solved.
10 Min run seams ok.
Tanks.
July 30, 2017, 09:45:27 AM
Using the Excavator GUI screwed up my MSI Afterburner. It removed the control over vore voltage, power limit and temperature limit. Now I'm also unable to use my overclock profiles I saved in Afterburner. If I select a profile and confirm it you hear the fan speeding up for a second and then slow down to its speed is was running by itself. I can do it in Wattman, but it won't remember the settings after rebooting the PC.
Which GPUs were affected by this problem, also have you tinkered with the overclocking inside of the GUI ?
July 30, 2017, 02:39:41 AM
Using the Excavator GUI screwed up my MSI Afterburner. It removed the control over vore voltage, power limit and temperature limit. Now I'm also unable to use my overclock profiles I saved in Afterburner. If I select a profile and confirm it you hear the fan speeding up for a second and then slow down to its speed is was running by itself. I can do it in Wattman, but it won't remember the settings after rebooting the PC.
July 28, 2017, 05:35:55 PM
Hi guys, the new version of excavator is finally out (most importantly including bugfix for a bug that was causing 0 RPM fans on AMD cards).
Get it here: https://github.com/nicehash/excavator/releases/tag/v1.2.11a
I will also release a new version of the GUI today/tomorrow with lyra2rev2 support.
Get it here: https://github.com/nicehash/excavator/releases/tag/v1.2.11a
I will also release a new version of the GUI today/tomorrow with lyra2rev2 support.
July 24, 2017, 10:49:41 AM
Hi everyone, i just released a small update - version 0.8
The major change in this build is added "crash" monitoring (GUI will monitor if excavator became unstable), if this happens GUI will temporarily postpone any overclocking routines applied in the GUI for 1 minute.
This should prevent an infinite crash loop of death when you set your Overclock too high resulting in excavator permanently restarting.
This release also added small "~" button to every worker (when advanced settings are enabled) which can be used to reset worker statistics.
This is useful for when you are fine tuning the overclock and want to see the new hashrate as soon as possible, especially useful if you are using daggerhashimoto which always delays the statistics due to DAG generation.
Backup pool functionality is now hidden by default (to make the UI more simple for novice users), you can bring the button back by enabling advanced settings.
That's it for this release, enjoy & happy mining!
Changelog:
The major change in this build is added "crash" monitoring (GUI will monitor if excavator became unstable), if this happens GUI will temporarily postpone any overclocking routines applied in the GUI for 1 minute.
This should prevent an infinite crash loop of death when you set your Overclock too high resulting in excavator permanently restarting.
This release also added small "~" button to every worker (when advanced settings are enabled) which can be used to reset worker statistics.
This is useful for when you are fine tuning the overclock and want to see the new hashrate as soon as possible, especially useful if you are using daggerhashimoto which always delays the statistics due to DAG generation.
Backup pool functionality is now hidden by default (to make the UI more simple for novice users), you can bring the button back by enabling advanced settings.
That's it for this release, enjoy & happy mining!
Changelog:
Code:
24.07.2017 @ 0.8
- Added instability monitoring/protection related to Overclocking
- Added "Reset Statistics" for a worker button (advanced feature)
- Backup Pools functionality is now only visible when advanced settings are enabled
- Minor style changes
- Added instability monitoring/protection related to Overclocking
- Added "Reset Statistics" for a worker button (advanced feature)
- Backup Pools functionality is now only visible when advanced settings are enabled
- Minor style changes
July 22, 2017, 12:25:37 PM
nice work man 
i hope that you Will support this gui
i hope that you Will support this gui July 20, 2017, 06:09:33 PM
I didn't test Excavator command line, to help you cause the fan probles on AMD cards, as soon as they release a new version, I will do it.
Cheers
Cheers
That's ok, i am waiting for the excavator update as well, as i am running into quite a few "random" issues related to excavator lately.
July 20, 2017, 08:37:34 AM
I didn't test Excavator command line, to help you cause the fan probles on AMD cards, as soon as they release a new version, I will do it.
Cheers
Cheers
July 14, 2017, 05:47:54 AM
can you share sample code for batch file to run excavator miner? I can try out and give you feedback!
Thanks for doing this, go to the default_command_file.json and replace it with the code below.
Don't forget to change the pool address, port, wallet and worker name (i renamed them in the file so you would spot them easily).
Code:
[
{"time":0,"commands":[
{"id":1,"method":"algorithm.add","params":["lbry","poolAddress:poolPort","wallet.workerName"]}
]},
{"time":3,"commands":[
{"id":1,"method":"worker.add","params":["0","0"]}
]},
{"time":10,"loop":10,"commands":[
{"id":1,"method":"worker.print.speed","params":["0"]},
{"id":1,"method":"algorithm.print.speeds","params":["0"]}
]}
]
{"time":0,"commands":[
{"id":1,"method":"algorithm.add","params":["lbry","poolAddress:poolPort","wallet.workerName"]}
]},
{"time":3,"commands":[
{"id":1,"method":"worker.add","params":["0","0"]}
]},
{"time":10,"loop":10,"commands":[
{"id":1,"method":"worker.print.speed","params":["0"]},
{"id":1,"method":"algorithm.print.speeds","params":["0"]}
]}
]
Now, for this test i am expecting that the pool that you are using is able to count the rejected shares (because the Excavator console won't show a counter).
If it doesn't, after few hours of running, you can do this, go to your web browser, and paste this into your URL bar:
Code:
http://127.0.0.1:38080/api?command={%22id%22:1,%22method%22:%22algorithm.list%22,%22params%22:[]}
It will output an json string that will contain share info (among other information)
{"total_shares":1,"total_accepted":1,"total_rejected":0,"last_efficiency":1.0}
Jump to: