dropky
Jr. Member
Offline
Activity: 132
Merit: 7
|
|
June 04, 2018, 08:05:17 PM |
|
@pupkinv From version 1.5.0 excavator supports only NiceHash stratums.
|
|
|
|
MiningTaken
Newbie
Offline
Activity: 28
Merit: 0
|
|
June 05, 2018, 06:51:03 PM |
|
@Dropky or anyone,
I want to setup my Awesome Miner to use Excavator 1.5.4a mining Lyra2REv2 at Nicehash, but it doesn't work. How should I setup it with AM? Should I setup the Json file ? I have 6 of GTX 1070 TI. Please help. Thanks.
|
|
|
|
dropky
Jr. Member
Offline
Activity: 132
Merit: 7
|
|
June 07, 2018, 06:26:30 AM |
|
@Dropky or anyone,
I want to setup my Awesome Miner to use Excavator 1.5.4a mining Lyra2REv2 at Nicehash, but it doesn't work. How should I setup it with AM? Should I setup the Json file ? I have 6 of GTX 1070 TI. Please help. Thanks.
I'm not familiar how Awesome Miner passes the commands to Excavator. Probably through the config file, can you post here the json file you mentioned?
|
|
|
|
MiningTaken
Newbie
Offline
Activity: 28
Merit: 0
|
|
June 07, 2018, 06:43:41 AM |
|
@Dropky or anyone,
I want to setup my Awesome Miner to use Excavator 1.5.4a mining Lyra2REv2 at Nicehash, but it doesn't work. How should I setup it with AM? Should I setup the Json file ? I have 6 of GTX 1070 TI. Please help. Thanks.
I'm not familiar how Awesome Miner passes the commands to Excavator. Probably through the config file, can you post here the json file you mentioned? @Dropky, Here is the "awesome.json" file made by Awesome Miner in Excavator 1.5.4a folder (and it doesn't work): [ {"time":0,"commands":[ {"id":1,"method":"algorithm.add","params":["lyra2rev2","lyra2rev2.jp.nicehash.com:3347","76FG5wMYLzy4KHrEsqCDBZ65KzuF8ambE:x"]} ]}, {"time":3,"commands":[ {"id":1,"method":"worker.add","params":["0","0"]}, {"id":1,"method":"worker.add","params":["0","1"]}, {"id":1,"method":"worker.add","params":["0","2"]}, {"id":1,"method":"worker.add","params":["0","3"]}, {"id":1,"method":"worker.add","params":["0","4"]}, {"id":1,"method":"worker.add","params":["0","5"]}, {"id":1,"method":"worker.add","params":["0","6"]}, {"id":1,"method":"worker.add","params":["0","7"]}, {"id":1,"method":"worker.add","params":["0","8"]}, {"id":1,"method":"worker.add","params":["0","9"]}, {"id":1,"method":"worker.add","params":["0","10"]}, {"id":1,"method":"worker.add","params":["0","11"]}, {"id":1,"method":"worker.add","params":["0","12"]} ]}, {"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":"worker.print.speed","params":["4"]}, {"id":1,"method":"worker.print.speed","params":["5"]}, {"id":1,"method":"worker.print.speed","params":["6"]}, {"id":1,"method":"worker.print.speed","params":["7"]}, {"id":1,"method":"worker.print.speed","params":["8"]}, {"id":1,"method":"worker.print.speed","params":["9"]}, {"id":1,"method":"worker.print.speed","params":["10"]}, {"id":1,"method":"worker.print.speed","params":["11"]}, {"id":1,"method":"worker.print.speed","params":["12"]}, {"id":1,"method":"algorithm.print.speeds","params":["0"]} ]} ] |
-------------------------------------------------------------------------------------------------------------------------------------- And here is the "awesome.json" file made by Awesome Miner in Excavator 1.4.4a folder (and it works) : [ {"time":0,"commands":[ {"id":1,"method":"algorithm.add","params":["lyra2rev2","lyra2rev2.jp.nicehash.com:3347","76FG5wMYLzy4KHrEsqCDBZ65KzuF8ambE:x"]} ]}, {"time":3,"commands":[ {"id":1,"method":"worker.add","params":["0","0"]}, {"id":1,"method":"worker.add","params":["0","1"]}, {"id":1,"method":"worker.add","params":["0","2"]}, {"id":1,"method":"worker.add","params":["0","3"]}, {"id":1,"method":"worker.add","params":["0","4"]}, {"id":1,"method":"worker.add","params":["0","5"]}, {"id":1,"method":"worker.add","params":["0","6"]}, {"id":1,"method":"worker.add","params":["0","7"]}, {"id":1,"method":"worker.add","params":["0","8"]}, {"id":1,"method":"worker.add","params":["0","9"]}, {"id":1,"method":"worker.add","params":["0","10"]}, {"id":1,"method":"worker.add","params":["0","11"]}, {"id":1,"method":"worker.add","params":["0","12"]} ]}, {"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":"worker.print.speed","params":["4"]}, {"id":1,"method":"worker.print.speed","params":["5"]}, {"id":1,"method":"worker.print.speed","params":["6"]}, {"id":1,"method":"worker.print.speed","params":["7"]}, {"id":1,"method":"worker.print.speed","params":["8"]}, {"id":1,"method":"worker.print.speed","params":["9"]}, {"id":1,"method":"worker.print.speed","params":["10"]}, {"id":1,"method":"worker.print.speed","params":["11"]}, {"id":1,"method":"worker.print.speed","params":["12"]}, {"id":1,"method":"algorithm.print.speeds","params":["0"]} ]} ] |
Please help. Thanks a lot.
|
|
|
|
dropky
Jr. Member
Offline
Activity: 132
Merit: 7
|
|
June 07, 2018, 07:25:36 AM |
|
Ok, I see the problem, we modified excavator API with 1.5.x versions. Try this (change btc address in subscribe method): [ {"time":1,"commands":[ {"id":1,"method":"subscribe","params":["nhmp.jp.nicehash.com:3200","BTC address"]} ]}, {"time":2,"commands":[ {"id":1,"method":"algorithm.add","params":["lyra2rev2"]} ]}, {"time":3,"commands":[ {"id":1,"method":"worker.add","params":["lyra2rev2", "0"]}, {"id":1,"method":"worker.add","params":["lyra2rev2", "1"]}, {"id":1,"method":"worker.add","params":["lyra2rev2", "2"]}, {"id":1,"method":"worker.add","params":["lyra2rev2", "3"]}, {"id":1,"method":"worker.add","params":["lyra2rev2", "4"]}, {"id":1,"method":"worker.add","params":["lyra2rev2", "5"]}, {"id":1,"method":"worker.add","params":["lyra2rev2", "6"]}, {"id":1,"method":"worker.add","params":["lyra2rev2", "7"]}, {"id":1,"method":"worker.add","params":["lyra2rev2", "8"]}, {"id":1,"method":"worker.add","params":["lyra2rev2", "9"]}, {"id":1,"method":"worker.add","params":["lyra2rev2", "10"]}, {"id":1,"method":"worker.add","params":["lyra2rev2", "11"]}, {"id":1,"method":"worker.add","params":["lyra2rev2", "12"]} ]}, {"time":10,"loop":10,"commands":[ {"id":1,"method":"worker.print.speeds","params":[]}, {"id":1,"method":"algorithm.print.speeds","params":[]} ]} ]
FYI, you said you have 6 devices in the rig, the config file is made for 13 GPUs.
|
|
|
|
MiningTaken
Newbie
Offline
Activity: 28
Merit: 0
|
|
June 07, 2018, 07:59:26 AM |
|
Ok, I see the problem, we modified excavator API with 1.5.x versions. Try this (change btc address in subscribe method): [ {"time":1,"commands":[ {"id":1,"method":"subscribe","params":["nhmp.jp.nicehash.com:3200","BTC address"]} ]}, {"time":2,"commands":[ {"id":1,"method":"algorithm.add","params":["lyra2rev2"]} ]}, {"time":3,"commands":[ {"id":1,"method":"worker.add","params":["lyra2rev2", "0"]}, {"id":1,"method":"worker.add","params":["lyra2rev2", "1"]}, {"id":1,"method":"worker.add","params":["lyra2rev2", "2"]}, {"id":1,"method":"worker.add","params":["lyra2rev2", "3"]}, {"id":1,"method":"worker.add","params":["lyra2rev2", "4"]}, {"id":1,"method":"worker.add","params":["lyra2rev2", "5"]}, {"id":1,"method":"worker.add","params":["lyra2rev2", "6"]}, {"id":1,"method":"worker.add","params":["lyra2rev2", "7"]}, {"id":1,"method":"worker.add","params":["lyra2rev2", "8"]}, {"id":1,"method":"worker.add","params":["lyra2rev2", "9"]}, {"id":1,"method":"worker.add","params":["lyra2rev2", "10"]}, {"id":1,"method":"worker.add","params":["lyra2rev2", "11"]}, {"id":1,"method":"worker.add","params":["lyra2rev2", "12"]} ]}, {"time":10,"loop":10,"commands":[ {"id":1,"method":"worker.print.speeds","params":[]}, {"id":1,"method":"algorithm.print.speeds","params":[]} ]} ]
FYI, you said you have 6 devices in the rig, the config file is made for 13 GPUs. @Dropky, Thank you very much for your help. I would like to confirm : for the BTC address, should I add ":x" behind my BTC address (like the one with Excavator 1.4.4a), or, no need to add those ":x" (just my BTC address) with v1.5.4a now ? FYI, I did have 6 GPUs. I don't know why Awesome Miner made the config with 13 devices. Should I edit it to only 6 devices, or, should I just leave it that way? Please advise. Thanks.
|
|
|
|
dropky
Jr. Member
Offline
Activity: 132
Merit: 7
|
|
June 07, 2018, 12:44:21 PM |
|
@Dropky, Thank you very much for your help. I would like to confirm : for the BTC address, should I add ":x" behind my BTC address (like the one with Excavator 1.4.4a), or, no need to add those ":x" (just my BTC address) with v1.5.4a now ? FYI, I did have 6 GPUs. I don't know why Awesome Miner made the config with 13 devices. Should I edit it to only 6 devices, or, should I just leave it that way? Please advise. Thanks. There is no need to add :x behind your BTC address. Yes, I would advise you to edit your config file for 6 GPUs, but it should work either way, excavator is ignoring commands send for devices that do not exist.
|
|
|
|
MiningTaken
Newbie
Offline
Activity: 28
Merit: 0
|
|
June 07, 2018, 01:52:46 PM |
|
@Dropky, Thank you very much for your help. I would like to confirm : for the BTC address, should I add ":x" behind my BTC address (like the one with Excavator 1.4.4a), or, no need to add those ":x" (just my BTC address) with v1.5.4a now ? FYI, I did have 6 GPUs. I don't know why Awesome Miner made the config with 13 devices. Should I edit it to only 6 devices, or, should I just leave it that way? Please advise. Thanks. There is no need to add :x behind your BTC address. Yes, I would advise you to edit your config file for 6 GPUs, but it should work either way, excavator is ignoring commands send for devices that do not exist. Ok, got it. Thanks again for your help. Cheers!
|
|
|
|
somaton
Jr. Member
Offline
Activity: 212
Merit: 6
|
|
June 07, 2018, 02:41:28 PM |
|
Why first accepted share (in green) is always number 10? Never seen any lower numbers.
|
|
|
|
dropky
Jr. Member
Offline
Activity: 132
Merit: 7
|
|
June 08, 2018, 06: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
|
|
|
|
Technicrate
Newbie
Offline
Activity: 68
Merit: 0
|
|
June 08, 2018, 09: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?
|
|
|
|
dropky
Jr. Member
Offline
Activity: 132
Merit: 7
|
|
June 08, 2018, 09: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
|
|
|
|
|
martyroz
|
|
June 17, 2018, 03:35:48 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.
|
|
|
|
dropky
Jr. Member
Offline
Activity: 132
Merit: 7
|
|
June 18, 2018, 09: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
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.
|
|
|
|
dropky
Jr. Member
Offline
Activity: 132
Merit: 7
|
|
June 18, 2018, 09: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.
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.
|
|
|
|
martyroz
|
|
June 19, 2018, 05: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?
|
|
|
|
dropky
Jr. Member
Offline
Activity: 132
Merit: 7
|
|
June 19, 2018, 08: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.
|
|
|
|
dropky
Jr. Member
Offline
Activity: 132
Merit: 7
|
|
July 02, 2018, 07:23:56 AM |
|
|
|
|
|
xinxilas
Newbie
Offline
Activity: 15
Merit: 0
|
|
July 31, 2018, 06:30:17 PM Last edit: July 31, 2018, 07:38:37 PM by xinxilas |
|
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
|
|
|
|
|