I just took a quick look and fixed the issue in the driver, so if you're using nightly it would be in tomorrow's build.. or you can compile from source.
What KStars version? logs? backtrace?
It is already included in the latest nightly.. why do you think it's not?
Also, there was an issue with the ZWO in focus module that was also fixed few days ago.. maybe also compile indi-asi and check it out?
What's broken exactly? possible to reproduce the issue with simulators?
ok I just pushed v0.2 of the driver:
1. Default baud set to 115200 for iEXOS100
2. Parking to set NONE (since custom parking is not support)
3. Added entries for EXOS2 and iEXOS100 in drivers.xml and then used this to automatically detect the mount type. So one less hassle for users.
Curious why there is limitation for southern hemisphere? How about setting date/time, what's the limitation here as well?
Thanks, I will make this the default baud rate for iEXES100 in the driver.
Yes, thanks to Ubuntu for breaking that package!
So there is one way to resolve this in Mate Terminal:
sudo apt-get update && sudo apt-get -y dist-upgrade
Once you get the error, just enter this command:
Then restart StellarMate. I fixed this in v1.4.3 at any rate.
This was reported as well for northern hemisphere. I'm still not sure what causes it. Someone way smarter than me needs to check the math. At any rate, I made it flip the correction vector now in the southern hemisphere, so check if that helps. The change should be in KStars nightly.
In GIT and Nightly releases. there is now a new driver INDI Toup base.
This is now the universal driver for all Touptek based cameras. There used to be a separate driver with duplicate code for each camera, but I decided to combine them all into one. This is applicable for the following cameras:
3. Orion Starshoot G
and probably others. so indi-toupcam and indi-altair will be gone and there is only indi-toupbase
1, 2, 3 above are already added, I will try to add #4 soon. If there are others (with available SDKs) please let me know.