excavator by NiceHash - multi-algorithm NVIDIA GPU miner [1.5.6a]

[djeZo]

When I try that above configuration for sia I just get this:


==================== www.nicehash.com ====================
         Excavator v1.2.2a GPU Miner for NiceHash.
    Copyright (C) 2017 NiceHash. All rights reserved.
Developed by djeZo and zawawa with help and contributors:
    pallas, Vorksholk, bitbandi, ocminer
==================== www.nicehash.com ====================

Build time: 2017-05-21 16:46:05
Build number: 29
Provided startup commandline:
        "E:\Mining\Excavator\excavator.exe"

[19:53:04][0x00000f30][info] Log started
[19:53:04][0x00000f30][info] core | Found CUDA device: GeForce GTX 1080 Ti
[19:53:05][0x00000f30][info] core | Found CUDA device: GeForce GTX 1080 Ti
[19:53:05][0x00000f30][info] api | Listening on 127.0.0.1:3456
[19:53:05][0x00000f30][info] core | Initialized!


This is my first foray into json, so I'm most likely missing something basic.

Run that .bat file instead of .exe. Keep in mind: excavator is more similar to a server app than desktop app.

previous version were working fine with the exe, why the change? getting more confusing and all..

Yes, it may look more confusing, but if take 10min of your time to study what it supports, you will realize that it has a very good aproach that covers everything needed: algo switching, multiple simultaneous pools, dual, tripple mining, device on/off

We could, of course, make a special limited startup fully featured command line like other miners have but that would just mean more programming work and more studying needed for end users.

Current approach gives you knowledge of API and startup commands at the same time, because they are basically the same. What you use for startup, you can use later when Excavator is already running and it will work the same way.

BTW, I suggest you all to take a look at API docs that are being written and almost fully complete: https://github.com/nicehash/excavator/tree/master/api

[1714941645]

1714941645

[1714941645]

1714941645

[zawawa]

Here comes Sia and Decred mining for AMD users. Enjoy!

excavator Release v1.2.3 alpha
https://github.com/nicehash/excavator/releases/tag/v1.2.3a

We are also preparing for ETH mining.
With it, dual- and triple-mining with any of the existing algorithms is possible.
We will keep you updated.

[baten]

How to set up on 5 GTX1070?
Old start line:
excavator.exe -a equihash -s zcl.suprnova.cc:4042 -u User.node07:x -ca -ca -od 5 -or -os 0 %core_delta% %mem_delta% %tdp% -os 1 %core_delta% %mem_delta% %tdp% -os 2 %core_delta% %mem_delta% %tdp% -os 3 %core_delta% %mem_delta% %tdp% -os 4 %core_delta% %mem_delta% %tdp%

I'm probably stupid, but I can not translate it into json file config  

The cmd file I use for my machine that has 4 various NVIDIA cards is following:

Code:

[
	{"time":1,"commands":[
		{"id":1,"method":"algorithm.add","params":["equihash","equihash.eu.nicehash.com:3357","EDITEDOUT"]}
	]},
	{"time":2,"commands":[
		{"id":1,"method":"worker.add","params":["0","0"]},
		{"id":1,"method":"worker.add","params":["0","1"]},
		{"id":1,"method":"worker.add","params":["0","1"]},
		{"id":1,"method":"worker.add","params":["0","2"]},
		{"id":1,"method":"worker.add","params":["0","2"]},
		{"id":1,"method":"worker.add","params":["0","3"]},
		{"id":1,"method":"worker.add","params":["0","3"]}
	]},
	{"time":5,"commands":[
		{"id":1,"method":"device.set.power_limit","params":["0","126"]},
		{"id":1,"method":"device.set.core_delta","params":["0","100"]},
		{"id":1,"method":"device.set.memory_delta","params":["0","800"]},
		{"id":1,"method":"device.set.power_limit","params":["1","90"]},
		{"id":1,"method":"device.set.core_delta","params":["1","100"]},
		{"id":1,"method":"device.set.memory_delta","params":["1","700"]},
		{"id":1,"method":"device.set.power_limit","params":["2","72"]},
		{"id":1,"method":"device.set.core_delta","params":["2","100"]},
		{"id":1,"method":"device.set.memory_delta","params":["2","400"]},
		{"id":1,"method":"device.set.power_limit","params":["3","126"]},
		{"id":1,"method":"device.set.core_delta","params":["3","130"]},
		{"id":1,"method":"device.set.memory_delta","params":["3","900"]}
	]},
	{"time":10,"commands":[
		{"id":1,"method":"worker.reset","params":["0"]},
		{"id":1,"method":"worker.reset","params":["1"]},
		{"id":1,"method":"worker.reset","params":["2"]},
		{"id":1,"method":"worker.reset","params":["3"]},
		{"id":1,"method":"worker.reset","params":["4"]},
		{"id":1,"method":"worker.reset","params":["5"]},
		{"id":1,"method":"worker.reset","params":["6"]}
	]},
	{"time":15,"loop":15,"commands":[
	  	{"id":1,"method":"algorithm.print.speeds","params":[]}
	]},
	{"event":"on_quit","commands":[
		{"id":1,"method":"device.set.tdp","params":["0","100"]},
		{"id":1,"method":"device.set.core_delta","params":["0","0"]},
		{"id":1,"method":"device.set.memory_delta","params":["0","0"]},
		{"id":1,"method":"device.set.tdp","params":["1","100"]},
		{"id":1,"method":"device.set.core_delta","params":["1","0"]},
		{"id":1,"method":"device.set.memory_delta","params":["1","0"]},
		{"id":1,"method":"device.set.tdp","params":["2","100"]},
		{"id":1,"method":"device.set.core_delta","params":["2","0"]},
		{"id":1,"method":"device.set.memory_delta","params":["2","0"]},
		{"id":1,"method":"device.set.tdp","params":["3","100"]},
		{"id":1,"method":"device.set.core_delta","params":["3","0"]},
		{"id":1,"method":"device.set.memory_delta","params":["3","0"]}
	]}
]

First, establish connection with remote pool - algorithm equihash.

Then I add workers so CUDA stuff is initialized (potential jump to P0 state can happen here).

Then waiting a bit for all these CUDA context are initialized and applying clocks and TDP.

After 10 seconds, I reset speed counter of all workers.

Then after 15 seconds and every 15 seconds print total speed to console.

And I also have on_quit even that resets applied clocks and TDPs back to default values.

Hope this helps you

Can you please explain what is the difference betweem "device.set.power_limit" and device.set.tpd"?

[DragonSlayer]

If I were to guess, "power_limit" is for opencl with amd, and "tpd" is for cuda with NVidia.  Correct me if I am wrong devs.

[Elder III]

I am using power_limit on a pair of GTX 1080 Tis  and it appears to be working correctly. For example, if I set it to 150 both GPUs will fluctuate right around 150 watts each for the duration of mining.

[Amph]

When I try that above configuration for sia I just get this:


==================== www.nicehash.com ====================
         Excavator v1.2.2a GPU Miner for NiceHash.
    Copyright (C) 2017 NiceHash. All rights reserved.
Developed by djeZo and zawawa with help and contributors:
    pallas, Vorksholk, bitbandi, ocminer
==================== www.nicehash.com ====================

Build time: 2017-05-21 16:46:05
Build number: 29
Provided startup commandline:
        "E:\Mining\Excavator\excavator.exe"

[19:53:04][0x00000f30][info] Log started
[19:53:04][0x00000f30][info] core | Found CUDA device: GeForce GTX 1080 Ti
[19:53:05][0x00000f30][info] core | Found CUDA device: GeForce GTX 1080 Ti
[19:53:05][0x00000f30][info] api | Listening on 127.0.0.1:3456
[19:53:05][0x00000f30][info] core | Initialized!


This is my first foray into json, so I'm most likely missing something basic.

Run that .bat file instead of .exe. Keep in mind: excavator is more similar to a server app than desktop app.

previous version were working fine with the exe, why the change? getting more confusing and all..

Yes, it may look more confusing, but if take 10min of your time to study what it supports, you will realize that it has a very good aproach that covers everything needed: algo switching, multiple simultaneous pools, dual, tripple mining, device on/off

We could, of course, make a special limited startup fully featured command line like other miners have but that would just mean more programming work and more studying needed for end users.

Current approach gives you knowledge of API and startup commands at the same time, because they are basically the same. What you use for startup, you can use later when Excavator is already running and it will work the same way.

BTW, I suggest you all to take a look at API docs that are being written and almost fully complete: https://github.com/nicehash/excavator/tree/master/api

i can't find how to launch the miner, by adding the url of the pool, where is the line to dd this in the bat?

[agis6]

@zawawa
Any progress with the Linux version?

I am currently doing preparatory work for the upcoming Linux version.
Excavator's code base is very clean, so there shouldn't be any problems.

This is very good news!
Thanks 

[Vaccinus]

how do i use the bat something is missing, i can't seems to get it work to run on suprnovaa, what line should i add for that? where to put username and password?

I believe you need to edit your default_command_file.json  with that information and then run the excavator+web+restart_script.bat to launch the miner.

i edited that with the commanline of my usually pool password and user, but nothing happen, i only see the browser open and tell me the number of gpu, but it say failed to initialaized etc..., can you post an example how to run this please? thank you

[restless]

by readme, in order to run equihash one has to run it "as admin"
But then the bat file (excavator+web+restart_script.bat) won't start from excavator's folder
so in the beginning of bat file one has to add cd to program folder

like:

Code:

@setlocal enableextensions
@cd /d "%~dp0"

It works with equihash on Pitcairn and Tahiti, but the speed is way lower than optiminer's - 3x slower for Pitcairn and 2x for Tahiti

[zawawa]

by readme, in order to run equihash one has to run it "as admin"
But then the bat file (excavator+web+restart_script.bat) won't start from excavator's folder
so in the beginning of bat file one has to add cd to program folder

like:

Code:

@setlocal enableextensions
@cd /d "%~dp0"

It works with equihash on Pitcairn and Tahiti, but the speed is way lower than optiminer's - 3x slower for Pitcairn and 2x for Tahiti

Again, excavator is not optimized for them yet. They are all GCN1 cards.
You can run the miner in the admin mode with "amd\start-admin.bat".

[restless]

any explanation of worker params?
How to set these

Parameter # | Range | Explanation
-----------------|----------|---------
1 | 0 or 1 | Disable/enable binary kernels
2 | 0 or 1 | Disable/enable the Global Data Share (requires admin privileges)

And how to add 2/3/4 workers per device, say, If I have 2 cards, should i add
   {"id":1,"method":"worker.add","params":["0","0"]}, lines for every worker&card, and how?


run excavator -c devicelist.txt (which comtains {"id":1,"method":"device.list","params":[]})
But result is not quite readable :/

IMHo next update should concentrate on making program useable. (examples how to find current config and set params)

[zawawa]

any explanation of worker params?
How to set these

Parameter # | Range | Explanation
-----------------|----------|---------
1 | 0 or 1 | Disable/enable binary kernels
2 | 0 or 1 | Disable/enable the Global Data Share (requires admin privileges)

And how to add 2/3/4 workers per device, say, If I have 2 cards, should i add
   {"id":1,"method":"worker.add","params":["0","0"]}, lines for every worker&card, and how?


run excavator -c devicelist.txt (which comtains {"id":1,"method":"device.list","params":[]})
But result is not quite readable :/

IMHo next update should concentrate on making program useable. (examples how to find current config and set params)

Well, excavator is actually designed to be used with other more user-friendly applications such as NiceHash Miner.
We should definitely add more examples of config files, though...

[Vaccinus]

by readme, in order to run equihash one has to run it "as admin"
But then the bat file (excavator+web+restart_script.bat) won't start from excavator's folder
so in the beginning of bat file one has to add cd to program folder

like:

Code:

@setlocal enableextensions
@cd /d "%~dp0"

It works with equihash on Pitcairn and Tahiti, but the speed is way lower than optiminer's - 3x slower for Pitcairn and 2x for Tahiti

still doesn't work, what the bat should look like, can you give me an example? i don't know where to put the pool and the username and password, i was able to get the webgui though, but that is the only thign that worked for me

[djeZo]

any explanation of worker params?
How to set these

Parameter # | Range | Explanation
-----------------|----------|---------
1 | 0 or 1 | Disable/enable binary kernels
2 | 0 or 1 | Disable/enable the Global Data Share (requires admin privileges)

And how to add 2/3/4 workers per device, say, If I have 2 cards, should i add
   {"id":1,"method":"worker.add","params":["0","0"]}, lines for every worker&card, and how?


run excavator -c devicelist.txt (which comtains {"id":1,"method":"device.list","params":[]})
But result is not quite readable :/

IMHo next update should concentrate on making program useable. (examples how to find current config and set params)

First, read https://github.com/nicehash/excavator to get general idea how it works.

Than read API docs which tells you commands for command file and TCP/HTTP API: https://github.com/nicehash/excavator/tree/master/api

[marvykkio]

I agree to put a string. Bat to help people like me who can not start mining execution, then put an example of file.bat, so people copy, and change the prarameters with theirs.
thank you

[baten]

How to set up on 5 GTX1070?
Old start line:
excavator.exe -a equihash -s zcl.suprnova.cc:4042 -u User.node07:x -ca -ca -od 5 -or -os 0 %core_delta% %mem_delta% %tdp% -os 1 %core_delta% %mem_delta% %tdp% -os 2 %core_delta% %mem_delta% %tdp% -os 3 %core_delta% %mem_delta% %tdp% -os 4 %core_delta% %mem_delta% %tdp%

I'm probably stupid, but I can not translate it into json file config  

The cmd file I use for my machine that has 4 various NVIDIA cards is following:

Code:

[
	{"time":1,"commands":[
		{"id":1,"method":"algorithm.add","params":["equihash","equihash.eu.nicehash.com:3357","EDITEDOUT"]}
	]},
	{"time":2,"commands":[
		{"id":1,"method":"worker.add","params":["0","0"]},
		{"id":1,"method":"worker.add","params":["0","1"]},
		{"id":1,"method":"worker.add","params":["0","1"]},
		{"id":1,"method":"worker.add","params":["0","2"]},
		{"id":1,"method":"worker.add","params":["0","2"]},
		{"id":1,"method":"worker.add","params":["0","3"]},
		{"id":1,"method":"worker.add","params":["0","3"]}
	]},
	{"time":5,"commands":[
		{"id":1,"method":"device.set.power_limit","params":["0","126"]},
		{"id":1,"method":"device.set.core_delta","params":["0","100"]},
		{"id":1,"method":"device.set.memory_delta","params":["0","800"]},
		{"id":1,"method":"device.set.power_limit","params":["1","90"]},
		{"id":1,"method":"device.set.core_delta","params":["1","100"]},
		{"id":1,"method":"device.set.memory_delta","params":["1","700"]},
		{"id":1,"method":"device.set.power_limit","params":["2","72"]},
		{"id":1,"method":"device.set.core_delta","params":["2","100"]},
		{"id":1,"method":"device.set.memory_delta","params":["2","400"]},
		{"id":1,"method":"device.set.power_limit","params":["3","126"]},
		{"id":1,"method":"device.set.core_delta","params":["3","130"]},
		{"id":1,"method":"device.set.memory_delta","params":["3","900"]}
	]},
	{"time":10,"commands":[
		{"id":1,"method":"worker.reset","params":["0"]},
		{"id":1,"method":"worker.reset","params":["1"]},
		{"id":1,"method":"worker.reset","params":["2"]},
		{"id":1,"method":"worker.reset","params":["3"]},
		{"id":1,"method":"worker.reset","params":["4"]},
		{"id":1,"method":"worker.reset","params":["5"]},
		{"id":1,"method":"worker.reset","params":["6"]}
	]},
	{"time":15,"loop":15,"commands":[
	  	{"id":1,"method":"algorithm.print.speeds","params":[]}
	]},
	{"event":"on_quit","commands":[
		{"id":1,"method":"device.set.tdp","params":["0","100"]},
		{"id":1,"method":"device.set.core_delta","params":["0","0"]},
		{"id":1,"method":"device.set.memory_delta","params":["0","0"]},
		{"id":1,"method":"device.set.tdp","params":["1","100"]},
		{"id":1,"method":"device.set.core_delta","params":["1","0"]},
		{"id":1,"method":"device.set.memory_delta","params":["1","0"]},
		{"id":1,"method":"device.set.tdp","params":["2","100"]},
		{"id":1,"method":"device.set.core_delta","params":["2","0"]},
		{"id":1,"method":"device.set.memory_delta","params":["2","0"]},
		{"id":1,"method":"device.set.tdp","params":["3","100"]},
		{"id":1,"method":"device.set.core_delta","params":["3","0"]},
		{"id":1,"method":"device.set.memory_delta","params":["3","0"]}
	]}
]

First, establish connection with remote pool - algorithm equihash.

Then I add workers so CUDA stuff is initialized (potential jump to P0 state can happen here).

Then waiting a bit for all these CUDA context are initialized and applying clocks and TDP.

After 10 seconds, I reset speed counter of all workers.

Then after 15 seconds and every 15 seconds print total speed to console.

And I also have on_quit even that resets applied clocks and TDPs back to default values.

Hope this helps you

Can you please explain what is the difference between "device.set.power_limit" and device.set.tpd"?

I have tried to use "device.set.power_limit","params":["0","80"] on my 1070 but it is not applied - although the other params like clock and mem are applied. I must be doing something wrong, but I cannot figure what...

[restless]

json file:

Code:

[
	{"time":0,"commands":[
		{"id":1,"method":"algorithm.add","params":["equihash","eu1-zcash.flypool.org:3333","wallet.h"]}
	]},
	{"time":3,"commands":[
		{"id":1,"method":"worker.add","params":["0","0","0"]},
		{"id":1,"method":"worker.add","params":["0","0","1"]},
		{"id":1,"method":"worker.add","params":["0","0","0","1"]},
		{"id":1,"method":"worker.add","params":["0","0","1","0"]}
	]},
	{"time":10,"loop":10,"commands":[
		{"id":1,"method":"worker.print.speed","params":["0"]},
		{"id":1,"method":"worker.print.speed","params":["1"]},
                {"id":1,"method":"worker.print.speed","params":["2"]},
                {"id":1,"method":"worker.print.speed","params":["3"]},
		{"id":1,"method":"algorithm.print.speeds","params":[""]}
	]}
]

result:

Code:

[14:55:34][0x00001490][info] ocl-equihash | Loaded an OpenCL kernel.
[14:55:34][0x000006ec][info] ocl-equihash | Loaded an OpenCL kernel.
[14:55:34][0x00003380][info] ocl-equihash | Loaded an OpenCL kernel.
[14:55:34][0x000033a0][info] ocl-equihash | Loaded an OpenCL kernel.
[14:55:35][0x00001490][info] ocl-equihash | GDS segment size: 0 bytes
[14:55:34][0x00001490][info] wrkr0-0 | Algorithm: opencl-equihash parameters: BIN=0,GDS=0
[14:55:35][0x000033a0][info] ocl-equihash | GDS segment size: 0 bytes
[14:55:34][0x000033a0][info] wrkr0-1 | Algorithm: opencl-equihash parameters: BIN=0,GDS=0
[14:55:36][0x00003380][info] ocl-equihash | GDS segment size: 0 bytes
[14:55:34][0x00003380][info] wrkr0-2 | Algorithm: opencl-equihash parameters: BIN=0,GDS=0
[14:55:37][0x000006ec][info] ocl-equihash | GDS segment size: 0 bytes
[14:55:34][0x000006ec][info] wrkr0-3 | Algorithm: opencl-equihash parameters: BIN=0,GDS=0

I tried to set equihash parameters , but it seems they are 0 no matter if I set additional params or not

[djeZo]

Can you please explain what is the difference between "device.set.power_limit" and device.set.tpd"?

I have tried to use "device.set.power_limit","params":["0","80"] on my 1070 but it is not applied - although the other params like clock and mem are applied. I must be doing something wrong, but I cannot figure what...

https://github.com/nicehash/excavator/tree/master/api#device-set-power-limit

[baten]

Can you please explain what is the difference between "device.set.power_limit" and device.set.tpd"?

I have tried to use "device.set.power_limit","params":["0","80"] on my 1070 but it is not applied - although the other params like clock and mem are applied. I must be doing something wrong, but I cannot figure what...

https://github.com/nicehash/excavator/tree/master/api#device-set-power-limit

Thanks very much - I will look carefully over that list.

I get this error sometime - CUDA error "an illegal memory access was encountered" in func "cuda_eq_run" line 2380 -- can you please let me know what it means? What parameter of the overclock is pushed too high?

[djeZo]

Can you please explain what is the difference between "device.set.power_limit" and device.set.tpd"?

I have tried to use "device.set.power_limit","params":["0","80"] on my 1070 but it is not applied - although the other params like clock and mem are applied. I must be doing something wrong, but I cannot figure what...

https://github.com/nicehash/excavator/tree/master/api#device-set-power-limit

Thanks very much - I will look carefully over that list.

I get this error sometime - CUDA error "an illegal memory access was encountered" in func "cuda_eq_run" line 2380 -- can you please let me know what it means? What parameter of the overclock is pushed too high?

Yep, this means your OC is too high and excavator does safety shutdown (calling on_quit event). A restart script can bring it back on. It is fine if you have few such crashes per day... but not if you have them too often. Also some unstable OCs can somehow corrupt your driver and restart of OS is needed in that case.