hi
i want use excavator mining multi algo switching . please help how can set it
i try default command_file_switching_example.json but not work
Topic: excavator by NiceHash - multi-algorithm NVIDIA GPU miner [1.5.6a] (Read 179317 times)
December 19, 2018, 06:47:27 AM
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!
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!
November 05, 2018, 05:08:05 PM
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
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
November 05, 2018, 04:53:02 PM
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
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
November 05, 2018, 06:08:08 AM
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
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
September 27, 2018, 03:59:26 PM
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.
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.
September 21, 2018, 06:48:53 AM
We added CUDA 10 build for mining on RTX 2080 cards:
https://github.com/nicehash/excavator/releases/tag/v1.5.11a
https://github.com/nicehash/excavator/releases/tag/v1.5.11a
August 03, 2018, 02:03:40 AM
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
@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). July 31, 2018, 01:30:17 PM
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
@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
July 02, 2018, 02:23:56 AM
We added x16r to the excavator:
https://github.com/nicehash/excavator/releases/tag/v1.5.6a
https://github.com/nicehash/excavator/releases/tag/v1.5.6a
June 19, 2018, 03:51:52 AM
Increase pagefile to 56 GB (7 x 8gb). Which driver are you using? Also, recheck all your risers, PSU connectors, if everything is connected ok.
The latest nVidia drivers. What's the general consensus on the most stable drivers?
Have you increased the pagefile? I haven't tried the latest drivers yet, usually I wait for a while. Currently I'm running 390.65 and I don't have any problems.
June 19, 2018, 12:43:05 AM
Increase pagefile to 56 GB (7 x 8gb). Which driver are you using? Also, recheck all your risers, PSU connectors, if everything is connected ok.
The latest nVidia drivers. What's the general consensus on the most stable drivers?
June 18, 2018, 04:21:16 AM
I am converting some rigs from nvOC (ubuntu) / nicehash-equihash to windows using nicehash miner. All rigs were rock solid stable under nvOC.
So far my 5*1080ti rig converted well and accepts the ETHlargementpill no problem, with good benchmark results.
But I'm having problems with my 6*1080 + 1*1070ti rig. Even with no pill and no overclock (just power limit adjust), my rig will reboot within 5 seconds - 10 minutes of mining with NHM.
daggerhashimoto will result in an almost instant reboot, whereas something like lyra2rev2, it will mine for 5 minutes and then reboot.
Any ideas on troubleshooting?
* Mobo is ASUS Z270-P, using 7 risers, one of which is using M2_1 slot.
* Only 4GB RAM. I have adjusted pagefile to 32GB.
* Windows installed on a 120GB SSD.
So far my 5*1080ti rig converted well and accepts the ETHlargementpill no problem, with good benchmark results.
But I'm having problems with my 6*1080 + 1*1070ti rig. Even with no pill and no overclock (just power limit adjust), my rig will reboot within 5 seconds - 10 minutes of mining with NHM.
daggerhashimoto will result in an almost instant reboot, whereas something like lyra2rev2, it will mine for 5 minutes and then reboot.
Any ideas on troubleshooting?
* Mobo is ASUS Z270-P, using 7 risers, one of which is using M2_1 slot.
* Only 4GB RAM. I have adjusted pagefile to 32GB.
* Windows installed on a 120GB SSD.
Increase pagefile to 56 GB (7 x 8gb). Which driver are you using? Also, recheck all your risers, PSU connectors, if everything is connected ok.
June 18, 2018, 04:06:05 AM
hi
i want use excavator mining multi algo switching . please help how can set it
i try default command_file_switching_example.json but not work
i want use excavator mining multi algo switching . please help how can set it
i try default command_file_switching_example.json but not work
command_file_switching_example.json file is just an example demonstrating how to use the excavator API in switching. I suggest you to use NiceHash Miner (https://miner.nicehash.com/), it runs excavator and it includes auto switching.
June 16, 2018, 10:35:48 PM
I am converting some rigs from nvOC (ubuntu) / nicehash-equihash to windows using nicehash miner. All rigs were rock solid stable under nvOC.
So far my 5*1080ti rig converted well and accepts the ETHlargementpill no problem, with good benchmark results.
But I'm having problems with my 6*1080 + 1*1070ti rig. Even with no pill and no overclock (just power limit adjust), my rig will reboot within 5 seconds - 10 minutes of mining with NHM.
daggerhashimoto will result in an almost instant reboot, whereas something like lyra2rev2, it will mine for 5 minutes and then reboot.
Any ideas on troubleshooting?
* Mobo is ASUS Z270-P, using 7 risers, one of which is using M2_1 slot.
* Only 4GB RAM. I have adjusted pagefile to 32GB.
* Windows installed on a 120GB SSD.
So far my 5*1080ti rig converted well and accepts the ETHlargementpill no problem, with good benchmark results.
But I'm having problems with my 6*1080 + 1*1070ti rig. Even with no pill and no overclock (just power limit adjust), my rig will reboot within 5 seconds - 10 minutes of mining with NHM.
daggerhashimoto will result in an almost instant reboot, whereas something like lyra2rev2, it will mine for 5 minutes and then reboot.
Any ideas on troubleshooting?
* Mobo is ASUS Z270-P, using 7 risers, one of which is using M2_1 slot.
* Only 4GB RAM. I have adjusted pagefile to 32GB.
* Windows installed on a 120GB SSD.
June 14, 2018, 06:56:20 AM
A new version has been released: https://github.com/nicehash/excavator/releases/tag/v1.5.5a
It includes speed improvements for lyra2z.
(and some really small improvements for lyra2rev2)
It includes speed improvements for lyra2z.
(and some really small improvements for lyra2rev2)
June 08, 2018, 04:53:14 AM
Why first accepted share (in green) is always number 10? Never seen any lower numbers.
We start counting shares at 10, so the first accepted share is always number 10. When we used standard stratum protocol, it came in handy because we could use lower numbers (0-9) for other custom messages between server and miner. Now with our custom protocol we could start counting at 0 but I guess we got used to counting from 10
So the 10 equals to 1 share?
Yes
June 08, 2018, 04:34:38 AM
Why first accepted share (in green) is always number 10? Never seen any lower numbers.
We start counting shares at 10, so the first accepted share is always number 10. When we used standard stratum protocol, it came in handy because we could use lower numbers (0-9) for other custom messages between server and miner. Now with our custom protocol we could start counting at 0 but I guess we got used to counting from 10
So the 10 equals to 1 share?
June 08, 2018, 01:38:49 AM
Why first accepted share (in green) is always number 10? Never seen any lower numbers.
We start counting shares at 10, so the first accepted share is always number 10. When we used standard stratum protocol, it came in handy because we could use lower numbers (0-9) for other custom messages between server and miner. Now with our custom protocol we could start counting at 0 but I guess we got used to counting from 10
June 07, 2018, 09:41:28 AM
Why first accepted share (in green) is always number 10? Never seen any lower numbers.
Jump to: