patrike,
Z9 bug/interaction that I've not troubleshot yet, but want to report in case you have other hits.
The Z9 (like all antminers) has a /cgi-bin/minerStatus.cgi that shows a current summary of mining/temps/etc.
If in AM I add my Z9s, configure API access, configure pools, everything works as expected... I can go to /cgi-bin/minerStatus.cgi as usual... however, if I use AM to "switch pool", once the pool switch occurs, /cgi-bin/minerStatus.cgi is empty except for the headers of all of the fields.
It isn't populated again until I "Configure API Access" again (which also resets the default pool, etc...).
If I, as before, send "switchpool|X" to the miner itself out of band, this doesn't happen... How does AwesomeMiner tell the antminer to switch pool? Is it doing something other than "switchpool|[0-2]"?
I realize this report is lacking in detail, as I get time to track it down more I'll update.
Thank you,
-j
Awesome Miner uses the JSON format for all commands sent to miners. When you use the feaure "Prioritize" on a pool, the command can look like this (when you prioritize the first pool in the list):
{"command":"switchpool","parameter":"0"}
When you use the feature "Change Pool" or "Add Pool" in Awesome Miner:
{"command":"addpool","parameter":"stratum+tcp://hub.miningpoolhub.com:17001,yourusername.1,x"}
Please note that "switchpool" is the command for prioritizing a pool and "addpool" is related to when you either do "Change Pool" or "Add Pool" in Awesome Miner (Change Pool will also send "removepool" commands).
You can view the commands that Awesome Miner is sending to the miner if you go to the Options dialog, Advanced section, and set the log level to Detailed. You can then perform a pool operation and for example search for "switchpool" in the Awesome Miner log file to see the exact request being sent.