Quote from: moppidoo on April 17, 2019, 10:53:21 AM

Quote from: patrike on April 17, 2019, 08:58:51 AM

Awesome Miner version 6.3.2

ASIC mining
- Support for Antminer B7
Integration
- SrbMiner pool configuration will set the property for Nicehash automatically
- Added CryptoNight HeavyX to XmRig by default
User interface
- Highlight modified coin properties in blue color on the Coins tab
Mining software
- GrinPro 2.1
- TT-miner 2.2.2
- Nanominer 1.2.1
Corrections
- Correction to trigger for detecting miner state

Wow thanks heaps patrike! That was fast!!!

A little problem though, if you recall I had issues with updating block rewards from wallet JSON-RPC about 2 weeks ago, I'm having these issues still, and this time with network hashrate as well (block rewards was not resolved either). (ref: https://bitcointalk.org/index.php?topic=676942.msg50374809;topicseen#msg50374809)

In AM log, I'm getting these:

Code:

17/04/2019 7:35:43 PM.794 [061] [S]Dynamic update of coin property for TZC, Difficulty: 15.2433979493097
17/04/2019 7:35:43 PM.795 [061] [S]Dynamic update of coin property for TZC, Network Hashrate: (failed)

17/04/2019 8:00:41 PM.227 [061] [S]Dynamic update of coin property for TZC, Difficulty: 25.3156886119117
17/04/2019 8:00:41 PM.227 [061] [S]Dynamic update of coin property for TZC, Block Reward: (failed)

I can however, get updates from MPOS based pools with their public API provided if I found one, though since I'm running the wallet node already, I prefer to have it read from local node.
I'm wondering if that's due to some sort of type parsing causing error in AM for those values other than difficulty?

sample output from wallet node JSON response as below (getnetworkhashps):

Code:

{
"result": 1313273656.397802,
"error": null,
"id": "curltest"
}

again, the test button shows correct result from the response, but the properties kept failing the update.

Thanks for the feedback - I will go ahead and add more log entries to make it possible to track down any update failures.