erossi Anyway, let's see if the new tool is going to work.
At this point, I will let the other people be guinea pigs, and will apply the updater when they finally release it.
They can't expect us to help them test something, when they are placing road blocks along the way. It is not as if they are doing us a favor (although that seems to be their attitude). They don't appear to realize that they are asking us to do them a favor by being alpha testers.
As it is, this bug has been there (and reported) since the 12V EAF days. And they had never bothered to investigate it for years until a customer measured the behavior carefully and described the bug. And now they post a file to the Google drive (of all places) that nobody can read. Why are they expecting us to do their homework??
ZWO knows my email address for crying out loud (just this past week, I received email from one of their software team asking for some help related to spherical geometry -- it is not as if they have lost my email address).
If they had wanted me to help with the EAF bug, they could at least have the courtesy to email the firmware update package directly to me; or even better, the Xcode project for it since they know that I still write Cocoa applications in my retirement.
By the way, with just using ∆T readings, it looks like I can stretch the frequency of needing to do a full V-curve from every 0.5ºC to every 2ºC. But, I need to establish my own V curve, since the ASIAIR auto focus algorithm stops just as it enters the CFZ (often times even before it has reached inside the CFZ) and if the EAF movement is not reversed correctly, it gives you zero ∆T tolerance to maintain focus, or never be in real focus at any temperature.