We join the discussion with the purpose to clarify the philosophy behind the design of the StarGo2 Pro and the StarGo Plus controllers.
Thank you! Highly appreciated!
Following the current technology progress, our vision is to provide an innovative and open system that allows the astrophotography users to implement their own setup on an All in One Solution based on the INDI/ASCOM Alpaca protocol, compatible with all the operative system, however it can also be used as a simple mount controller only.
This also follow a growing trend that see a lot of users that are using micro computers embedded on their setup, reducing cabling, gaining a setup as more compact as possible, giving the opportunity to have a remote control also for a remote location.
I fully agree on your motivation and following this trend. That's why I bought the StarGO2 Pro controller with the Raspberry Pi4 mini-computer running under LINUX and with INDI, ASCOM, KStars/EKOS, etc... pre-installed.
Our system is based on Linux/INDI server with no limited function.
That means that it can works with every INDI/ASCOM Alpaca devices and system.
Not 100% correct. What is still missing is the full support of the LX200 protocol under INDI.
Currently, you are providing two INDI wrappers ("drivers") for your own proprietary drivers: 1) SkySafari driver and 2) StarGO2 INDI driver, that is a pretty complete wrapper of your internal controllers. While the first one is extremely limited in its functionality (and outdated and buggy, I might add), the latter is not part of the INDILIB repository. This means, one either has very limited functionality or full access but "only" with INDI servers that accept your INDI interface.
INDIGO and ASIAIR are both based on INDI and fully support the classical LX200 protocol and the more modern onstep interface. Your wrappers/drivers and interfaces do NOT support these standardised protocols. So... sorry to say that, you are not compatible "with every INDI/ASCOM devices and systems".
Lots of tests has been done, as shown in the StarGo2 Pro User Manual, that it is possible to download without registration on our Support page.
Probably the systems or devices that have problems to connect with the StarGo2 Pro, may have some kind of proprietary protocol policy that prevent the connection.
I think you are referring to ZWO ASIAIR and INDIGO... Yes, they are proprietary considering their GUIs and algorithms, but their interfacing protocols and drivers are all based on open source drivers and in particular the very common LX200 protocol that you are not supporting. In a way your system is more proprietary than they are.
We continuously work on the system in order to provide the full compatibility with operative systems update, drivers and devices but not always the issues come from our side.
Well, then please, listen to customers and finally update the SkySafari driver (try slewing to M2) and provide full LX200 support. Then these "issues" might just disappear.
BTW, I highly recommend you to add a built-in external
antenna to the new StarGO Plus. All other suppliers of mini-computer/controller learned this the hard way and replaced or upgraded their Raspberry Pi's with a stronger and more stable WiFi based on an external antenna. Check out TheSky Fusion, StellarMate Pro, PrimaLuce, all mini PCs, ASIAIR Plus/mini, ... they all decided to go for the better WiFi interface. I do not even consider using the StarGO2's WiFi hotspot, because it is so weak and unreliable. This is not your fault, it is inherent to the Raspberry Pi4. I only use the Ethernet connection.
I am still using the StarGO2 Pro with my Mac and the ASIAIR (only for imaging, no guiding possible!), but I also need to use a separate instance of PHD2 or EKOS. I do not use the VNC-based interface, because it either has issues with the GUI or the font is so small, that it is very hard to read.
Looking at your excellent hardware, I am surprised about the compromised you chose for the new StarGO Plus mini-computers.
Again, I appreciate that you are participating in this thread. I sincerely hope, that you will open up to all established standards to allow better access to your mount.
Potential new clients would also appreciate more insight on the encoder discussion and the actual difference between all your new and classical mounts. A little table and some selected user feedback/reviews at the right place might do some wonders ;-)
[ I cannot comment on the encoder questions, since my mount does not have any. ]
Edited by Obs30, 23 May 2023 - 12:24 AM.