Excavator GUI by cTnko - Miner Interface for beginners and advanced users [0.9]

[zorvalth]

I have never carfed about both profitabilty values but the other 3 are clear:


Algo 20 is dagger(eth). From here https://www.nicehash.com/api?method=stats.global.current the eth stats are:

{"price":"0.0313","algo":20,"speed":"3343.53403830","profitability_eth":"0.0226","profitability_above_eth":"38.68"}

You can figure it out the rest from the stats page of each algo:



Price is the one yo uneed - 0.0313 BTC per GH per Day
algo is explained in the main page
speed is the hashing speed of the algo in nicehash in GH for ether : 3343 GH - you dont really need this.

for auto profit switch you just need the price of the algos in excavator.

[namjey]

Hey cTnko, I have been using your miner for 1 day and have some problems!

I got 484 rejects out of 2930 accepted shares!! I am mining LBC on suprnova. If i just use ccminer reject rate is way lower(around 10 out of 1000)
This is what i get:
[14:00:47][0x000035cc][info] net | Share #479 rejected
                                reason: low difficulty share of 132.21903125193825

Here is ss:

What's wrong with this?? Can anybody tell me how to fix this??

[cTnko]

Hey cTnko, I have been using your miner for 1 day and have some problems!

I got 484 rejects out of 2930 accepted shares!! I am mining LBC on suprnova. If i just use ccminer reject rate is way lower(around 10 out of 1000)
This is what i get:
[14:00:47][0x000035cc][info] net | Share #479 rejected
                                reason: low difficulty share of 132.21903125193825

Here is ss:

What's wrong with this?? Can anybody tell me how to fix this??

That's definitely very high amount of rejects (i can confirm that i had big amount of rejects last time i tested lbry).
Have you tried using the standalone excavator (without the GUI) to see if the reject rate is also this high? (just to determinate if GUI is causing the problem or not)

IF anyone could shine some light on the lbry parameters that don't result in such a high reject rate, i could make them defaults for lbry under the hood of my GUI.

[namjey]

can you share sample code for batch file to run excavator miner? I can try out and give you feedback!

[cTnko]

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"]}
	]}
]

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}

[aGeoM]

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

[cTnko]

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

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.

[slejvi]

nice work man  i hope that you Will support  this gui

[cTnko]

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:

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

[cTnko]

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.

[Runaque]

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.

[cTnko]

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 ?

[aGeoM]

I'm back

AMD fan problem solved.
10 Min run seams ok.

Tanks.

[Runaque]

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.

[Runaque]

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.

[Daywalker22]

Hey,
It is also possible to set something like auto switch? Like nicehash has?
Or you can only mine in a direct pool?

[cTnko]

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.

[rascao]

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

[cTnko]

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

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).

[Jake76er]

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