Get the skyX mount disconnect on session ending

I did notice that my AP mount stay connected in TheSkyX even after Voyager disconnect.

I investigate the TSX TCP API and found that the function Sky6RASCOMTele.disconnect() does not did the job, and the only way to proper disconnect the mount was to use a final Sky6RASCOMTele.Park().

So i push some golang code to crosscompile an exec i can call from my dragscript on the end of the session. But this force me to enable the TCP interface of TheSkyX under tools menu.

Here is the little code:
Disconnect scope: GOTSX

Leo, did i miss something on the Voyager side ?

Voyager is not the owner of the connection and cannot know the reasons why you use TheSkyX and if the connection to the mount continues to serve you. If you need to close TSX you can use the dragscript block which closes the processes, there is also the one for tsx. So everything closes, or use code as you did.

The code you wrote interfer with Voyager status, if you want to park the mount just use park in Voyager … calling exactly the method you talk about.

All the best
LO

“The code you wrote interfer with Voyager status, if you want to park the mount just use park in Voyager … calling exactly the method you talk about.”

I want to park but also disconnect the mount from TSX a session ending.
Voyager disconnect the camera in TSX but not the mount

My code is designed to work after voyager disconnect, so i’m not sure how it could interfer with voyager status.

“… calling exactly the method you talk about.”

I observe this behavior, not really the Park() method…
TheSkyX park and disconnect

LEO, i’ve my solution, thank you for your help.

You are welcome, I just wrote advice to you about status relation between voyager and theskyx, you are free to running every code you want .

All the best
LO

Hello LEO,

I want to thank you for the last addition in the 2.2.8 version of voyager.

TSXDisco

Voyager now can disconnect the mount in TheSkyX at the end of the session.
This work like expected :wink:

Thank you very much.

Hoxca

Voyager work with TSX since 9 years … compatibility is difficult to understand in users.
Someone think if he have the last version all have last version. Someone not update if work.
The method used and for what you thank is present in the latest versions , for you info. When someone check this flag and doesnt have result in Voyager because he doesnt have the right version i will call you :wink:

All the best
LO