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

[dropky]

Hello friends, dropky

@dropky, can you help me?

1- Using the algo-switching manually on Excavator(and at Nicehash servers), just like exemplified on command_file_switching_example.json, it would switch based on nicehash statistics? just like excavator changes when used by nicehash app? and are the earnings identical?

2- I'll use excavator from nicehash install, it would read my benchmarks made by nicehash exe before?

3- And where to add some overclocking params before each algo switch at "command_file_switching_example.json"?
I only wants to switch between Lyra2Rev2 and DaggerHashimoto, for one device, at nicehash, and based on my benchmarks which is lyra2rev2 = 69.3 MH/hs, and DaggerHashimoto 53.6 MH/s, and then add some overclock setup before each algo-switching, any example for this?

Any help???
Pleeease

1 - No, excavator doesn't perform auto switching and it doesn't receive any information for current algorithm profitability on its own. The command_file_switching_example.json file shows how the API can be used for easy algorithm switching in case you're developing your own application.

2 - Excavator doesn't read any benchmarks, that's all NiceHash Miner. Excavator doesn't make any decisions on its own. It has to be told what algorithm to mine, on which card, on what time.

3 - You can pass different OC settings through API (device related methods). But currently NiceHash Miner 2 doesn't support that, so either wait for NiceHash Miner 3 , write your own program/script or use a third party application that is build around excavator (I know that MinerPro for NiceHash supports individual overclocking for each algorithm).

 

[dropky]

We added CUDA 10 build for mining on RTX 2080 cards:

https://github.com/nicehash/excavator/releases/tag/v1.5.11a

[tempusbro]

Sorry if this isn't the proper place to post, but I downloaded Excavator a couple days ago and it ran great but my GTX 1060 was capped out at 100% the entire time. I've tried to edit it and put in my restrictions but every time I try to load it up it just does the default 100% and the main command prompt says "Error Core : Command file - invalid JSON: [". If I reload all the files it works fine but this is the only computer I have so I am wanting to run it as around 75% instead of putting it through lengthy stress tests every time I try to mine. I can post the changes I made but at this point it's so buggered up it just needs done from scratch again. Any advice would be great, I've been going at this for 2 days straight now (only slept one hr) and it's driving me insane. I need to be studying and doing homework but my obsessive nature literally won't let me. Thanks in advance.

Edit: Of course an hour after I posted this I got it working by just using one of the example files. Still don't know what the issue was with mine but at least this works now. I'm not actually mining anything though, it just loads, I'll have to go in and adjust the settings for my 1060. It's probably a good thing the devs preloaded lower values rather than higher ones.

[dj--alex]

Hello

please help move to nicehash-skunkhash this script

I use excavator 1.5.11

i just don't know what is write.
Official site nicehash tells only for Micro$$$oft window$$
https://www.nicehash.com/news/206
where i must write a btc address???
[
{"time":0,"commands":[
   {"id":1,"method":"algorithm.add","params":["skunkhash", "skunk.eu.nicehash.com:3362","dj--alex.rig1:x"]}
]}
   ,
   {"time":3,"commands":[
      {"id":1,"method":"worker.add","params":["0","0"]}
   ]},
   {"time":10,"loop":10,"commands":[
      {"id":1,"method":"algorithm.print.speeds","params":[]}
   ]}
]

excavator -p 0 -c skunk-nice-very-nice.json

[dropky]

Hello

please help move to nicehash-skunkhash this script

I use excavator 1.5.11

i just don't know what is write.
Official site nicehash tells only for Micro$$$oft window$$
https://www.nicehash.com/news/206
where i must write a btc address???
[
{"time":0,"commands":[
   {"id":1,"method":"algorithm.add","params":["skunkhash", "skunk.eu.nicehash.com:3362","dj--alex.rig1:x"]}
]}
   ,
   {"time":3,"commands":[
      {"id":1,"method":"worker.add","params":["0","0"]}
   ]},
   {"time":10,"loop":10,"commands":[
      {"id":1,"method":"algorithm.print.speeds","params":[]}
   ]}
]

excavator -p 0 -c skunk-nice-very-nice.json

Hey, excavator doesn't support skunk algorithm. You can use NiceHash Miner Legacy or some third party miner (e.g. ccminer).

Link to NiceHash Miner Legacy - https://github.com/nicehash/NiceHashMinerLegacy/releases

[dj--alex]

sorry i don't know. Maybe they added skunk later?

miner on the link i followed requires non free OS : Microsoft Windows
i don' t use it
i't  too unsafe and too defective by design to using for any purposes.

Wine doesn't work with Nicehash-legacy
how to skip this check. I don't believe battlefield 1 works  but Miner - not !



:/  go to reading ccminer compiling manual

[Staller]

Hi, I mine equihash on Nvidia 1070 and for comparison i tried two miners excavator & ccminer.
And i have noticed that for the same target from the pool ccminer and excavator have different difficulty:

for example, i got target 0000400000000000000000000000000000000000000000000000000000000000 from the pool and
ccminer says it is 1023.94 diff, but excavator says 15420.2

The question is why there is a difference and does it affect something or not? Solutions/s is almost the same for miners

tnx!