Obviously, not everybody with a Celestron mount has a problem (we had a person on this thread who said his Celestron connected fine), we just don't know why ASIAIR can see some of the Celestron mounts and not see others (sometimes the same model).
I know that Celestron uses both FTDI (UK) and Prolific (Taiwan) USB chip sets. I wonder if it has to do with that, i.e., if ZWO had removed the Prolific driver from ASIAIR. The general Raspbian release does include a Prolific driver nowadays, but ZWO is always cutting corners with their memory usage.
Perhaps the ones on this thread (presumably mainly people who can't see their mounts) can check the chipset in their mount by connecting it to a computer.
On macOS, that information is available when you drill down into the USB device tree of System Information (which you can get to by selecting "About This Mac" in the Apple Menu in the menu bar,
and clicking "System Report..."
My mount (RainbowAstro)shows up like this, for example:
Notice that I am connected through a USB hub (Genesis Logic Inc chipset), and the mount itself uses the FTDI (Future Tecnology Devices International Ltd.) FT232R USB chip.
There is probably some tool in Windows that will give you this information.
Other than FTDI and Prolific, another major supplier of USB Virtual Serial chips is Silicon Labs.
If we can find out if it is something common, we will get somewhere. It would be nice if everyone who has a problem has a Prolific chip and everyone whose mount work has a non-Prolific chip; then we know who the culprit is.
I really don't understand why ZWO is not tracking this problem. It is obviously a problem, and they are sticking their head in the sand. They are the ones who can for example immediately answer if Prolific chips are a problem instead of making us peons shotgun for the root cause of the problem.
Chen
