[Awesome Miner] - Powerful Windows GUI to manage and monitor up to 200000 miners - page 428.

Zaffor

newbie

Activity: 28

Merit: 2

Quote from: puwaha on January 31, 2018, 11:10:51 PM

Quote from: Zaffor on January 30, 2018, 11:34:57 PM

When one tweaks the profit option for Time and Percentages does Time stand for the minimum amount of time AM will allow the rig to stay on its last job (whatever pool/algo it was on) What happens after the time lapses? it will redirect ONLY if there is something offering a profit greater than the %percentage that is set?

Yes, you got it mostly. The time is just the amount of time that will pass before AM re-calculates "best coin or algo" profit values from the statistics it gets from either Whattomine (if you are mining individual pools or pool groups)... or it rechecks the enabled Online Services that you have enabled on profit miners. If you are mining individual pools or pool groups, there is also another time setting to pay attention to on the Statistics tab in the Options. That time setting is how often AM will check Whattomine or Coinwarz for updated statistics.

Quote

I dont fully follow when some of the posts talk about setting the values so that your rig doesnt jump around too often but yet doesnt miss out on the peaks?

If I understood how it worked a little more I could possibly run some tests with that idea in mind to see whats best.

The more I read the more I retain (although its in small bits)

Thanks for your help so far gents

I'll just requote what I wrote a few weeks (and a few pages) back:

Quote from: puwaha

Let's say you switch to mine a coin that has a 2 minute block time on say Zpool. You mine your share, and you get a percentage of the reward for that block. But now, you have to wait for say 10 confirmations to mature before it's sent to the exchange. That's now 20 minutes you are waiting for the coin to mature before it gets sent to the exchange. Now, let's say it's a mildly popular coin, and it's gets sent to the exchange... minimum 2 minutes of that coin's block time if Zpool has enough of that coin built up to make it worth their while to send to the exchange. We are up to 22 minutes. That transaction is going to take another 10 confirmations before the exchange makes it available to trade. We are now up to 42 minutes.

What are the chances that your coin is worth the same amount when you started mining it until it reaches the point where it can be traded on the exchange 42 minutes later? Not very likely. There are thousands and thousands of miners that use auto-switching algorithms and were mining the same coin you thought was hot in that moment. That shoots up the difficulty, and the massive dump on the exchange(s) sends the value of the coin down.

A 24 hour profitability evens out those nuances, and I would even argue that a longer period is necessary. You want to be mining a coin that is consistently in the top spot... not in the moment.

But, this is my opinion... there are other perspectives.

Thanks for that explanation Puwaha

I was under the assumption that when a coin was hot, it simply meant from a mining perspective. I didnt think it was related to its market price just perhaps difficulty or popularity. I was previously thinking that running AM for even less time to hit several of these small peaks would be beneficial but after reading your explanation I guess it could actually be detrimental. Im just trying to find a good rhythm to run these rigs on to maximize their profits (but I guess so is everyone else)

Thanks again for your help

yhbae

newbie

Activity: 119

Merit: 0

Not quite a copyright issue, but this is what Patrike said before:

---
Excavator v1.2 is not at all compatible with Excavator v1.1 included in Awesome Miner. They completely redesigned both the API and command line options between v1.1 and v1.2, so they are not compatible at all.

At some point I will add support for Excavator v1.2, once they keep the API more stable. There will be quite an implementation effort to support the new v1.2, and so far I don't think this miner has been so popular. Also, as you probably noticed in their license information, I'm explicitly forbidden to automatically download Excavator from Awesome Miner. So the user experience will not be as good when I move to v1.2.
---

also:

---
It's correct that the new versions of Excavator are forbidden to be automatically download by Awesome Miner, as Nicehash EULA restricts this. That's one of the reason why I didn't prioritize putting any effort into this mining software. The other reason is that the API and entire setup of this mining software is a bit strange, and was changed a lot from their previous versions. I do understand that it could still make sense to support it, but Excavator didn't turn out to be so popular in the community anyway.

I'm getting a large number of questions and requests these days so even if this item is on the list of features to implement, it has not yet been a top priority. Thanks for your feedback on this.
---

I assume we are currently on v1.1?

yhbae

newbie

Activity: 119

Merit: 0

I could be wrong, but didn't someone mention that excavator cannot be packaged with AM because of copyright issues?

soothaa

hero member

Activity: 1151

Merit: 528

I can write a program to convert excavator into being supported in AwesomeMiner.. already did it before CAST, stak, and xmrig were supported..

wildzer0

newbie

Activity: 28

Merit: 0

Quote from: fecker on February 02, 2018, 04:11:10 AM

And guys, with EWBF miner, can u also use other commands like --fee 0 --tempunits C --templimit 50 etc, within AM ? or the commands it supports are limited or it supports all commands what EWBF supports ?

Read the help:

http://www.awesomeminer.com/help.aspx
How to add custom command line argument to mining software?

fecker

jr. member

Activity: 30

Merit: 3

And guys, with EWBF miner, can u also use other commands like --fee 0 --tempunits C --templimit 50 etc, within AM ? or the commands it supports are limited or it supports all commands what EWBF supports ?

Cryptorayo

newbie

Activity: 74

Merit: 0

Quote from: yrk1957 on February 01, 2018, 09:12:46 PM

Quote from: Cryptorayo on February 01, 2018, 06:16:14 PM

Quote from: yrk1957 on February 01, 2018, 05:48:06 PM

Quote from: sharknakedo on February 01, 2018, 03:40:10 PM

Quote from: wildzer0 on February 01, 2018, 08:58:30 AM

Another vote for Excavator.

On a 1080 I'm getting 1.03 MH/s on ccminer-klausT and 1.27 MH/s on Excavator.

Same here for me. I have spent a long time with this software (paying customer, premium edition) but it isn't without its flaws.

1. The best miner for my Nvidia cards (Excavator, but hsrminer before that) doesn't have support
...

I have similar results with Excavator. We really need the latest version to be supported in AM.

I saw that Excavator had changed their API to json format a while back, which is why it does not work with AM anymore. I could get them to connect but AM does not issue any commands to it, so it just waits.

some one have contact with excavator developers Huh

?
it's a good point to check

Well the right way is for AM to adapt to the changes. I doubt Excavator guys will start supporting an obsolete API.

yes, you're right. we can't live only with hopes.. i think so... i can't imagine Excavator guys supporting an obsolete API only for support.

Mr.Spider703

member

Activity: 392

Merit: 27

http://radio.r41.ru

Quote from: yrk1957 on February 02, 2018, 01:07:36 AM

This built-in miners need a serious upgrade.

I tested the built-in ccminer vs Excavator (1.4.2.a) on AHashPool and found that Excavator is faster as follows:

Blake2s - 16% Faster
NeoScrypt - 30% Faster

These figures are nothing to joke about when it comes to dollars.

I hope the author seriously considers at least upgrading to the latest Excavator. Otherwise we are all loosing money big time.

(Note: I was able to configure the latest Excavator to run with AM, it can start/stop/monitor it, but does not report any metrics). And profit switching of course does not work.

At me 3 * 1060 and 1 * 1080 and at inclusion blake2s there is a blade of the driver, tell me your settings for card and command line parameters

yrk1957

member

Activity: 531

Merit: 29

This built-in miners need a serious upgrade.

I tested the built-in ccminer vs Excavator (1.4.2.a) on AHashPool and found that Excavator is faster as follows:

Blake2s - 16% Faster
NeoScrypt - 30% Faster

These figures are nothing to joke about when it comes to dollars.

I hope the author seriously considers at least upgrading to the latest Excavator. Otherwise we are all loosing money big time.

(Note: I was able to configure the latest Excavator to run with AM, it can start/stop/monitor it, but does not report any metrics). And profit switching of course does not work.

proteus7

newbie

Activity: 106

Merit: 0

Quote from: mettalmag on February 01, 2018, 10:54:04 AM

Quote from: proteus7 on February 01, 2018, 10:50:01 AM

Any idea how I can add sia to the balances section? tried various block explorers but can't get it to show up..

did you update the AM?

Yes, running the latest 4.4 version. I can see where I can add sia under options/balances..if there was a sia block explorer with a compatible API. I can't seem to find one anywhere....

rafaeldelrey

newbie

Activity: 31

Merit: 0

Quote from: eminer001 on January 31, 2018, 02:30:59 PM

Quote from: rafaeldelrey on January 30, 2018, 10:35:17 AM

Quote from: akhouston on January 29, 2018, 10:43:08 AM

Quote from: robl450 on January 29, 2018, 10:05:36 AM

for 24 hour profitability settings, why would you not set it to 1 minute or 5 minutes? It doesn't switch very often anyway. The problem I have with that at least on my system is it will basically just mine bitcore forever.

From my experience you need to be careful when selecting pools for this. AHashpool is most reliable in terms of not experiencing / showing crazy spikes, while zpool and MHP are the worst.

In my experience, ahashpool stats are totally misleding. I deactivated it from my profit switch.

I find all the values shown by AM misleading, they simply have absolutely no relation with the reality. I tried with 3 separate test rigs and with the same settings and same GPUs one shows $100/day and the the other shows that is it making $5/day.

It seems that statistics and profit that is shown are just random numbers.

PATRIKE, can you read it and explain why all profit values from AM are RANDOM NUMBERS ? It changes from one miner to another based on random numbers, nothing that has to do with reality or at least with the values from whattomine.com !!!

When I said the ahashpool numbers are misleading, I didnt say it was AM fault. It looks like ahashpool reports incorrect numbers.

yrk1957

member

Activity: 531

Merit: 29

Quote from: Cryptorayo on February 01, 2018, 06:16:14 PM

Quote from: yrk1957 on February 01, 2018, 05:48:06 PM

Quote from: sharknakedo on February 01, 2018, 03:40:10 PM

Quote from: wildzer0 on February 01, 2018, 08:58:30 AM

Another vote for Excavator.

On a 1080 I'm getting 1.03 MH/s on ccminer-klausT and 1.27 MH/s on Excavator.

Same here for me. I have spent a long time with this software (paying customer, premium edition) but it isn't without its flaws.

1. The best miner for my Nvidia cards (Excavator, but hsrminer before that) doesn't have support
...

I have similar results with Excavator. We really need the latest version to be supported in AM.

I saw that Excavator had changed their API to json format a while back, which is why it does not work with AM anymore. I could get them to connect but AM does not issue any commands to it, so it just waits.

some one have contact with excavator developers Huh

?
it's a good point to check

Well the right way is for AM to adapt to the changes. I doubt Excavator guys will start supporting an obsolete API.

Cryptorayo

newbie

Activity: 74

Merit: 0

Quote from: yrk1957 on February 01, 2018, 05:48:06 PM

Quote from: sharknakedo on February 01, 2018, 03:40:10 PM

Quote from: wildzer0 on February 01, 2018, 08:58:30 AM

Another vote for Excavator.

On a 1080 I'm getting 1.03 MH/s on ccminer-klausT and 1.27 MH/s on Excavator.

Same here for me. I have spent a long time with this software (paying customer, premium edition) but it isn't without its flaws.

1. The best miner for my Nvidia cards (Excavator, but hsrminer before that) doesn't have support
...

I have similar results with Excavator. We really need the latest version to be supported in AM.

I saw that Excavator had changed their API to json format a while back, which is why it does not work with AM anymore. I could get them to connect but AM does not issue any commands to it, so it just waits.

some one have contact with excavator developers Huh

?
it's a good point to check

yrk1957

member

Activity: 531

Merit: 29

Quote from: sharknakedo on February 01, 2018, 03:40:10 PM

Quote from: wildzer0 on February 01, 2018, 08:58:30 AM

Another vote for Excavator.

On a 1080 I'm getting 1.03 MH/s on ccminer-klausT and 1.27 MH/s on Excavator.

Same here for me. I have spent a long time with this software (paying customer, premium edition) but it isn't without its flaws.

1. The best miner for my Nvidia cards (Excavator, but hsrminer before that) doesn't have support
...

I have similar results with Excavator. We really need the latest version to be supported in AM.

I saw that Excavator had changed their API to json format a while back, which is why it does not work with AM anymore. I could get them to connect but AM does not issue any commands to it, so it just waits.

sharknakedo

newbie

Activity: 8

Merit: 1

Quote from: wildzer0 on February 01, 2018, 08:58:30 AM

Another vote for Excavator.

On a 1080 I'm getting 1.03 MH/s on ccminer-klausT and 1.27 MH/s on Excavator.

Same here for me. I have spent a long time with this software (paying customer, premium edition) but it isn't without its flaws.

1. The best miner for my Nvidia cards (Excavator, but hsrminer before that) doesn't have support
2. The best miner for my Radeon Vega cards (XMR-STAK) has only external mining support.
3. The statistics implementation needs help. For something like Nicehash, "current" stats work fine, as I am getting paid on a per-hash basis. However, on everything else I get jacked around far too often. That leaves a 24 hours as my only other option, which, given volatility of the alt-coin market is really far too long. MPM has a "stability" calculation that is better, and it essentially builds a real-time ongoing database of prices. My preference would be to implement an ability for us to do continuous sampling and apply our own math via the scripting function. I'd implement a EWMA and then play with the lambda until I was happy that I was able to usually mine coins that are either stable or increasing in value to match the TTF numbers so they get auto-exchanged for somewhere close to the value I supposedly mined them at.

Don't get me wrong, the program is better than others out there, but I can't say I am happy with it, and I don't think there would be too much trouble to implement a few of these. I'd be more than happy to help test solutions (or even contribute to coding) if it would speed things up a little.

koenkerst

newbie

Activity: 2

Merit: 0

Hi all from Awesome Miner,
I use the new version of Awesome miner but see some strange figures.
Is this a bug in the program?

See the green,red and blue lines

https://www.dropbox.com/sh/orvmmv8xzsf5a3j/AACfIN_uPFYz-D9g4V8SK6Tka?dl=0

mettalmag

legendary

Activity: 1084

Merit: 1003

≡v≡

Quote from: proteus7 on February 01, 2018, 10:50:01 AM

Any idea how I can add sia to the balances section? tried various block explorers but can't get it to show up..

did you update the AM?

proteus7

newbie

Activity: 106

Merit: 0

Any idea how I can add sia to the balances section? tried various block explorers but can't get it to show up..

abdullahsurati

newbie

Activity: 66

Merit: 0

Hi, I am running a Awesome Miner 4.4 with claymore 10.6
I have a 6x1050Ti rig. I have overclocked it with +150/+500 with 75% TDP.
Whenever I start the Claymore Miner with overclocked settings, it fails to start.
Here is the log:

Code:

20:25:33:052 209c Check and remove old log files...
20:25:33:053 209c args: -platform 2 -mode 1 -wd 1 -r -1 -mport 4028 -allcoins 1
20:25:33:054 209c
20:25:33:055 209c ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ»
20:25:33:056 209c º Claymore's Dual ETH + DCR/SC/LBC/PASC GPU Miner v10.6 º
20:25:33:057 209c ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ¼
20:25:33:058 209c
20:25:33:058 209c b471
20:25:33:259 209c You enabled full remote management, but did not specify -mpsw option to protect it by password, please do it, otherwise you can be attacked if you share remote management port to internet! Or use negative -mport value to enable read-only remote management mode, see Readme for details.
20:25:38:264 209c ETH: 1 pool is specified
20:25:38:265 209c Main Ethereum pool is asia.ethash-hub.miningpoolhub.com:20536
20:25:38:716 209c CUDA initializing...

20:25:38:717 209c NVIDIA Cards available: 6
20:25:38:718 209c CUDA Driver Version/Runtime Version: 9.1/8.0
20:25:38:736 209c GPU #0: GeForce GTX 1050 Ti, 4096 MB available, 6 compute units, capability: 6.1 (pci bus 1:0:0)

20:25:38:738 209c GPU #1: GeForce GTX 1050 Ti, 4096 MB available, 6 compute units, capability: 6.1 (pci bus 2:0:0)

20:25:38:740 209c GPU #2: GeForce GTX 1050 Ti, 4096 MB available, 6 compute units, capability: 6.1 (pci bus 3:0:0)

20:25:38:741 209c GPU #3: GeForce GTX 1050 Ti, 4096 MB available, 6 compute units, capability: 6.1 (pci bus 5:0:0)

20:25:38:743 209c GPU #4: GeForce GTX 1050 Ti, 4096 MB available, 6 compute units, capability: 6.1 (pci bus 6:0:0)

20:25:38:745 209c GPU #5: GeForce GTX 1050 Ti, 4096 MB available, 6 compute units, capability: 6.1 (pci bus 7:0:0)

20:25:38:746 209c Total cards: 6
20:25:42:753 209c No AMD cards in the list, ADL library will not be used.
20:25:42:758 209c NVML version: 9.390.65
20:25:43:453 fe4 ETH: Stratum - connecting to 'asia.ethash-hub.miningpoolhub.com' <172.104.94.4> port 20536
20:25:43:532 209c ETHEREUM-ONLY MINING MODE ENABLED (-mode 1)

20:25:43:534 209c ETH: eth-proxy stratum mode
20:25:43:535 209c "-allcoins" option is set, default pools will be used for devfee, check "Readme" file for details.
20:25:43:536 209c Watchdog enabled
20:25:43:538 209c Remote management is enabled on port 4028
20:25:43:539 209c

20:25:43:593 fe4 send: {"worker": "Kishorthakkar.am", "jsonrpc": "2.0", "params": ["", "x"], "id": 2, "method": "eth_submitLogin"}

20:25:43:593 fe4 ETH: Stratum - Connected (asia.ethash-hub.miningpoolhub.com:20536)
20:25:43:733 fe4 got 39 bytes
20:25:43:733 fe4 buf: {"id":2,"jsonrpc":"2.0","result":true}

20:25:43:734 fe4 parse packet: 38
20:25:43:735 fe4 ETH: Authorized
20:25:43:737 fe4 send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

20:25:43:737 fe4 new buf size: 0
20:25:43:874 fe4 got 243 bytes
20:25:43:875 fe4 buf: {"id":3,"jsonrpc":"2.0","result":["0xb25c38688aa152a0a6b31696f735946491e1bd39f4f8e8adf65c06e2719ff098","0xb683d2a971567602a1931b76b9fb447dd5563f0e4ab5dd69250556e7c1c94783","0x00000000ffb34c02420e9948eacd78cf33b059a88ade1ff0614f7f3c303cf3a7"]}

20:25:43:875 fe4 parse packet: 242
20:25:43:876 fe4 ETH: job changed
20:25:43:877 fe4 new buf size: 0
20:25:43:943 1440 Setting DAG epoch #167...
20:25:46:091 21bc Setting DAG epoch #167 for GPU5
20:25:46:092 690 Setting DAG epoch #167 for GPU3
20:25:46:094 404 Setting DAG epoch #167 for GPU1
20:25:46:095 21bc Create GPU buffer for GPU5
20:25:46:090 1440 Setting DAG epoch #167 for GPU0
20:25:46:095 2378 Setting DAG epoch #167 for GPU4
20:25:46:098 690 Create GPU buffer for GPU3
20:25:46:101 1440 Create GPU buffer for GPU0
20:25:46:103 a24 Setting DAG epoch #167 for GPU2
20:25:46:104 404 Create GPU buffer for GPU1
20:25:46:110 2378 Create GPU buffer for GPU4
20:25:46:114 a24 Create GPU buffer for GPU2
20:25:49:008 2054 srv_thr cnt: 1, IP: 127.0.0.1
20:25:49:014 2054 recv: 51
20:25:49:016 2054 srv pck: 50
20:25:49:019 2054 srv bs: 0
20:25:49:020 2054 sent: 208
20:25:53:898 fe4 ETH: checking pool connection...
20:25:53:909 fe4 send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

20:25:54:036 2144 srv_thr cnt: 1, IP: 127.0.0.1
20:25:54:037 2144 recv: 51
20:25:54:037 2144 srv pck: 50
20:25:54:040 2144 srv bs: 0
20:25:54:041 fe4 got 243 bytes
20:25:54:042 fe4 buf: {"id":3,"jsonrpc":"2.0","result":["0xb25c38688aa152a0a6b31696f735946491e1bd39f4f8e8adf65c06e2719ff098","0xb683d2a971567602a1931b76b9fb447dd5563f0e4ab5dd69250556e7c1c94783","0x00000000ffb34c02420e9948eacd78cf33b059a88ade1ff0614f7f3c303cf3a7"]}

20:25:54:043 fe4 parse packet: 242
20:25:54:043 fe4 ETH: job is the same
20:25:54:044 fe4 new buf size: 0
20:25:54:046 2144 sent: 208
20:25:55:268 690 GPU 3, GpuMiner cu_kd failed 4 (11), unspecified launch failure
20:25:55:270 690 GPU 3, Calc DAG failed!
20:25:55:327 21bc GPU 5, GpuMiner cu_kd failed 4 (19), unspecified launch failure
20:25:55:450 1440 GPU 0, GpuMiner cu_kd failed 4 (19), unspecified launch failure
20:25:55:452 1440 GPU 0, Calc DAG failed!
20:25:55:544 2378 GPU 4, GpuMiner cu_kd failed 4 (19), unspecified launch failure
20:25:55:545 404 GPU 1, GpuMiner cu_kd failed 4 (19), unspecified launch failure
20:25:55:684 a24 GPU 2, GpuMiner cu_kd failed 4 (19), unspecified launch failure
20:25:55:694 a24 GPU 2, Calc DAG failed!
20:25:55:696 2378 GPU 4, Calc DAG failed!
20:25:55:699 404 GPU 1, Calc DAG failed!
20:25:55:713 21bc GPU 5, Calc DAG failed!
20:25:58:869 690 Set global fail flag, failed GPU3
20:25:58:872 690 GPU 3 failed
20:25:58:870 3ac Setting DAG epoch #167 for GPU3
20:25:58:874 3ac GPU 3, CUDA error 4 - cannot write buffer for DAG

20:25:59:045 1440 Set global fail flag, failed GPU0
20:25:59:045 9d0 Setting DAG epoch #167 for GPU0
20:25:59:051 9d0 GPU 0, CUDA error 4 - cannot write buffer for DAG

20:25:59:062 1440 GPU 0 failed
20:25:59:067 ddc srv_thr cnt: 1, IP: 127.0.0.1
20:25:59:076 ddc recv: 51
20:25:59:076 ddc srv pck: 50
20:25:59:079 ddc srv bs: 0
20:25:59:080 ddc sent: 208
20:25:59:197 a24 Set global fail flag, failed GPU2
20:25:59:198 19cc Setting DAG epoch #167 for GPU2
20:25:59:201 19cc GPU 2, CUDA error 4 - cannot write buffer for DAG

20:25:59:204 a24 GPU 2 failed
20:25:59:213 2378 Set global fail flag, failed GPU4
20:25:59:214 1a28 Setting DAG epoch #167 for GPU4
20:25:59:216 1a28 GPU 4, CUDA error 4 - cannot write buffer for DAG

20:25:59:218 2378 GPU 4 failed
20:25:59:214 404 Set global fail flag, failed GPU1
20:25:59:223 404 GPU 1 failed
20:25:59:225 15b8 Setting DAG epoch #167 for GPU1
20:25:59:226 15b8 GPU 1, CUDA error 4 - cannot write buffer for DAG

20:25:59:218 21bc Set global fail flag, failed GPU5
20:25:59:229 21bc GPU 5 failed
20:25:59:230 1d40 Setting DAG epoch #167 for GPU5
20:25:59:231 1d40 GPU 5, CUDA error 4 - cannot write buffer for DAG

20:26:01:875 3ac Set global fail flag, failed GPU3
20:26:01:876 3ac GPU 3 failed
20:26:02:063 9d0 Set global fail flag, failed GPU0
20:26:02:064 9d0 GPU 0 failed
20:26:02:204 19cc Set global fail flag, failed GPU2
20:26:02:205 19cc GPU 2 failed
20:26:02:219 1a28 Set global fail flag, failed GPU4
20:26:02:222 1a28 GPU 4 failed
20:26:02:228 15b8 Set global fail flag, failed GPU1
20:26:02:229 15b8 GPU 1 failed
20:26:02:235 1d40 Set global fail flag, failed GPU5
20:26:02:236 1d40 GPU 5 failed
20:26:03:884 fe4 send: {"id":6,"worker":"Kishorthakkar.am","jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x0", "0x0000000000000000000000000000000000000000000000000000000074222981"]}

20:26:03:916 fe4 ETH: checking pool connection...
20:26:03:917 fe4 send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

20:26:04:019 fe4 got 39 bytes
20:26:04:019 fe4 buf: {"id":6,"jsonrpc":"2.0","result":true}

20:26:04:019 fe4 parse packet: 38
20:26:04:020 fe4 new buf size: 0
20:26:04:096 788 srv_thr cnt: 1, IP: 127.0.0.1
20:26:04:096 788 recv: 51
20:26:04:097 788 srv pck: 50
20:26:04:099 788 srv bs: 0
20:26:04:101 788 sent: 208
20:26:04:149 fe4 got 243 bytes
20:26:04:150 fe4 buf: {"id":3,"jsonrpc":"2.0","result":["0xb25c38688aa152a0a6b31696f735946491e1bd39f4f8e8adf65c06e2719ff098","0xb683d2a971567602a1931b76b9fb447dd5563f0e4ab5dd69250556e7c1c94783","0x00000000ffb34c02420e9948eacd78cf33b059a88ade1ff0614f7f3c303cf3a7"]}

20:26:04:151 fe4 parse packet: 242
20:26:04:153 fe4 ETH: job is the same
20:26:04:155 fe4 new buf size: 0
20:26:05:847 fe4 got 243 bytes
20:26:05:847 fe4 buf: {"id":0,"jsonrpc":"2.0","result":["0xcca0c35bf4cd033a1b1f8effd66769d52b01e504343fbed30f25abcfeed04d83","0xb683d2a971567602a1931b76b9fb447dd5563f0e4ab5dd69250556e7c1c94783","0x00000000ffb34c02420e9948eacd78cf33b059a88ade1ff0614f7f3c303cf3a7"]}

20:26:05:848 fe4 parse packet: 242
20:26:05:849 fe4 ETH: job changed
20:26:05:850 fe4 new buf size: 0
20:26:05:852 fe4 ETH: 02/01/18-20:26:05 - New job from asia.ethash-hub.miningpoolhub.com:20536
20:26:05:853 fe4 target: 0x00000000ffb34c02 (diff: 4300MH), epoch 167(2.30GB)
20:26:05:855 fe4 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00
20:26:05:856 fe4 ETH: GPU0 0.000 Mh/s, GPU1 0.000 Mh/s, GPU2 0.000 Mh/s, GPU3 0.000 Mh/s, GPU4 0.000 Mh/s, GPU5 0.000 Mh/s
20:26:08:319 20d4 GPU0 t=38C fan=48%%, GPU1 t=42C fan=49%%, GPU2 t=38C fan=48%%, GPU3 t=43C fan=49%%, GPU4 t=43C fan=49%%, GPU5 t=40C fan=49%%
20:26:08:417 20bc em hbt: 0, fm hbt: 32,
20:26:08:418 20bc watchdog - thread 0 (gpu0), hb time 9188
20:26:08:418 20bc watchdog - thread 1 (gpu0), hb time 9188
20:26:08:419 20bc watchdog - thread 2 (gpu1), hb time 9188
20:26:08:420 20bc watchdog - thread 3 (gpu1), hb time 9188
20:26:08:420 20bc watchdog - thread 4 (gpu2), hb time 9188
20:26:08:421 20bc watchdog - thread 5 (gpu2), hb time 9188
20:26:08:422 20bc watchdog - thread 6 (gpu3), hb time 9188
20:26:08:422 20bc watchdog - thread 7 (gpu3), hb time 9188
20:26:08:423 20bc watchdog - thread 8 (gpu4), hb time 9188
20:26:08:423 20bc watchdog - thread 9 (gpu4), hb time 9188
20:26:08:424 20bc watchdog - thread 10 (gpu5), hb time 9188
20:26:08:425 20bc watchdog - thread 11 (gpu5), hb time 9188
20:26:08:426 20bc WATCHDOG: GPU error, you need to restart miner :(

If I reset the overclock settings, and then start the miner, it starts mining, and then i can apply overclocking, and so it will continue mining with the improved hashrate.
But I cannot do this everytime the miner restarts.

Can anyone help with this? Thanks

yrk1957

member

Activity: 531

Merit: 29

There is a run profit switch action in rules. Does the HTTP API also support this?

Topic: [Awesome Miner] - Powerful Windows GUI to manage and monitor up to 200000 miners - page 428. (Read 703512 times)