Closed jedimstr closed 10 years ago
Here's a reply from Kano in the BitcoinTalk Forums on the custom CGMiner version used in the Antminer S1 and the API issues I posted here.
This affects both the Last Time Share issue as well as the improper Hashrate display for summary command. https://bitcointalk.org/index.php?topic=28402.msg5155782#msg5155782
They feel the need to change the API.
They are morons.
It is not changed in master cgminer.
I have made sure that the cgminer API is backward compatible since I first wrote it.
The only things changed have been to remove CPU and GPU information (since they don't exist in cgminer)
Unfortunately, the idiots who make the Antminer, break this compatibility by changing names and values in the API in their clone of cgminer.
You will also find that they changed the name of the fields and values that report the hash rate in the summary.
So basically what it means is that either everyone who has ever written a program or script to access the API must modify their code to support these random needless changes, or tell them to stop fucking with the API and making it no longer compatible.
Edit: they were probably stupid enough to also not notice that STATUS->When is the time of the results - so the difference between 'When' and 'Last Share Time' will tell you how long ago it is if you want to display it differently ......... (as I already do in miner.php for 'Last Valid Work')
Last Share Submitted for Pool data shows "Invalid Date" with later versions of CGMiner used on Antminer S1's.
The actual issue is because formatting/data for Pool last share data is different than what is shown for what's available under the devs command:
{"command":"pools"}
{"command":"devs"}