![]() ![]() If you do the initial alignment via the physical hand controller or the software one (NexRemote) then you certainly also can have one of hundreds of other mount control apps initiating the mount gotos. If they (SS and SkyPortal, not CPWI) are used to perform the initial alignment they cannot be used to share control with another mount control app. SkySafari and SkyPortal (and CPWI) apps are unique and contain the hand controller functionality. It gets the information on where the telescope is pointing from the mount. I will keep you all informed of the outcome. Today I cannot test that but I will try first the suggestion of SkipW to change from J2000 to JNow. But, if the difference is just a few degrees then that can explain the offset. * Coordinate system settings (on Stellarium): not sure about the difference between J2000 and JNow. * User interface settings (on Stellarium): from introduction youtube movies people left this blank thus I do not expect a problem from here The devise model is set to “Celestron NexStar (compatible) thus I do not expect a problem from here * Device setting (on Stellarium): cannot be a wrong serial port because otherwise the scope would not move. From what I can remember the offset distance was less than 15 degrees ![]() * time difference between NexStar and Stellarium: cannot be because the difference UT time and summer time would be hour (or 15 degrees = 360 /24 hrs). * location coordinates: cannot be because maximum difference between Stellarium and NexStar would be 0.5 arc-sec (due to round the number to zero decimal places) I did a mental troubleshooting and the (easiest) possible reasons are:
0 Comments
Leave a Reply. |