Ever since I have installed the new release 2.3.4 the goto function is no longer responding. Let me try to expose my issue :
In the “on the fly section”, after choosing a target and retrieving the coordinates, nothing happens when the “goto” button is pushed.
As per my two exchanges with Leo late yesterday, Voyager is behaving like the “mount is already in the asked position” (as I was trying to reach a target that the mount has already reached…). But this is not the case.
As can be seen in the below example, I was trying to slew to M57 with its respective coordinates. However, after executing the “goto” function, nothing happened. More puzzling is the coordinates that you can see in the second printscreen (monitor) which are different from M57’s.
Worth mentioning that the goto function works perfectly with Carte du Ciel and APT tool. As a result, there should be something wrong in Voyager.
I would appreciate any help, suggestions, etc.
PS : I have re-installed Voyager from scratch but the problem remains.
Let me know if the installation of ASCOM 6.5 SP1 solve your problem please, like I wrote in the dedicated thread I tried to remove Voyager side an handle leak in Astrometry library of ASCOM, SP1 have a discrete number of Fix. I reported the thread because this solved goto problem for 2 users have reached me by support.
Quick update from my side. I confirm by installing ASCOME 6.5 SP1 solved my issue. I just gave it a try and the goto function responded as expected.
Also, next time I am seeking for support I will send you a direct email - as it seems the preferred way. I thought that the forum would / could potentially be also of assistance whenever someone if facing an issue. But message understood !
I don’t always want to pass for the bad guy, Voyager support is a product! As such it must be protected, the reason why we do not offer official support in the forum is this. It is our choice to give a more direct relationship with our customers and really solve things. Of course this does not mean that everyone’s contribution is definitely a solver for some issues and we thank those who help us but not in this case!