patrike,
Hello! New user / "Premium Edition" licensee.
I'm managing Z9s.
I've added the Z9s, set the default pools, set up API access, enabled auto-detect of ant miners...
The basic monitoring is working, however I'm unable to switch pools. When I try to switch pools by selecting a miner, right clicking, and choosing the new pool in the list, the miner goes offline as it appears to be reconfiguring, but it comes back up with whatever the first pool is every time.
If I manually send a "switchpool" command to the miners, it switches immediately without going offline and AwesomeMiner seems to show the change quickly.
I assume I'm missing something configuration wise for being able to switch it from awesome miner itself (not worried about profit switching yet, just want to get the basic functionalities going). This is with version 5.3.
So, 2 questions:
1) If "switchpool" works when I send it manually, what else is required on the Z9 configuration beyond (A) enabling API access, (B) configuring pools under Options->Pools [not pool groups], (C) Under Antminer->Default Pools, configuring the pools from B in the menu, and then (D) trying to manually change the running pool on each Z9 (or the group of, but still), (E) setting each miner for equihash algorithm and cgminer compatible
2) In the log file, there is an error I am not sure how to track down that may be related:
Here is a snippet:
7/10/2018 1:41:43 AM.456 [031] [E]Parsing API response failed
Newtonsoft.Json.JsonReaderException: Unexpected character encountered while parsing value: n. Path 'COIN[0]['Network Difficulty']', line 1, position 296.
7/10/2018 1:41:43 AM.456 [031] [E] at Newtonsoft.Json.JsonTextReader.ParseValue()
at Newtonsoft.Json.Linq.JContainer.ReadContentFrom(JsonReader r, JsonLoadSettings settings)
at Newtonsoft.Json.Linq.JContainer.ReadTokenFrom(JsonReader reader, JsonLoadSettings options)
at Newtonsoft.Json.Linq.JObject.Load(JsonReader reader, JsonLoadSettings settings)
at Newtonsoft.Json.Linq.JObject.Parse(String json, JsonLoadSettings settings)
at #=z2xLeZw_B5dXwcJOHkyG9xVRqNnoqZL68sG2jDR2USh7I.#=z4pmou5oY0nrldvgvjw==(String #=zs0MJwbU=, MinerBase #=zP3qP$WQWrfW1)
at #=zA$LVp_dIzZ6ih0BVqLWRtxjNv5AzsYRwXcqmyp_l6t9o.#=zHHgyFDg=[T](MinerBase #=zP3qP$WQWrfW1, Func`3 #=zgiXjQWvK5uqg, #=zopTEL3oNfgVtVjJpDp7JPYMrEcI6Zl5oNzTTQtG9SpOa #=ztzVONJc=, String #=z1m$C5Ns=)
7/10/2018 1:41:43 AM.456 [031] [E]{"STATUS":[{"STATUS":"S","When":1531201301,"Code":78,"Msg":"CGMiner coin","Description":"cgminer 4.9.0"}],"COIN":[{"Hash Method":"sha256","Current Block Time":1531201256.170012,"Current Block Hash":"0000000000000000000000000000000000000000000000000000000000000000","LP":true,"Network Difficulty":nan}],"id":1}
7/10/2018 1:41:44 AM.604 [028] [E]Parsing API response failed
Newtonsoft.Json.JsonReaderException: Unexpected character encountered while parsing value: n. Path 'COIN[0]['Network Difficulty']', line 1, position 296.
As an aside, here's an interesting Z9 cgminer bug(?).. asking for the details of 'coin' via the API says that the hash method is sha256 despite it being an equihash device.
{"STATUS":[{"STATUS":"S","When":1531231620,"Code":78,"Msg":"CGMiner coin","Description":"cgminer 4.9.0"}],"COIN":[{"Hash Method":"sha256","Current Block Time":1531206055.763028,"Current Block Hash":"0000000000000000000000000000000000000000000000000000000000000000","LP":true,"Network Difficulty":nan}],"id":1}
Thank you!
Thanks for all details. This is a unique behavior on the Z9 miner and you are correct that it's actually a bug in the API output from the miner itself. One of the API methods called "coins" is used by Awesome Miner to get the Network Difficulty from the ASIC miner. It's probably the least important of all API calls. The Z9 miner is responding with a invalid JSON format that simply cannot be parsed correctly. Awesome Miner considers the miner to not be working when this happens, but it should instead ignore the issue and move on.
I had a similar report yesterday from another Z9 user where it also started to act up after performing some pool operation. Thanks to your details here as well, I'm confident about the scenario now.
In the next update of Awesome Miner I will simply let Awesome Miner continue with all other API requests even if this one isn't valid. You can expect a new release within the next few days.
About the "sha256" part, there are actually many non-sha256 miners that do report sha256 here for some reason. This information is however not used by Awesome Miner.
