Yeah, I can add an alias "TheSkyX" later on. I didn't implement all functionality, but the basic ones only available via TheSkyX scripting. Thanks for testing!
Any chance you can add the ability to home the paramounts? This might be a helpful start up sequence option, or even just a button to make it do this. I believe the command is findHome().
Hi, I am trying to control a Paramount Mount with TSX in ubuntu 16.04, with Ekos using TCP API of TSX. It does connect and read coordinates, but any slew fail. TSX stand-alone is capable, of course of slewing. Before connecting INDI, I prepare TSX with Find Home, that works, and leave the mount in tracking.
Any idea, how to debug the situacion? After any try to slew, or start tracking, or Park/Unpark.. etc, from INDI, the interface of TSX shows "Connection problems" and some time even bring COM popups. Later than this, I have to reboot the mountand TSX.
Thanks
I don't know how to get INDI logs (I tried to find how, but only found developers hints for debug mode in device code to generate a log in /tmp, but not how to get device protocols logs from a user pov).
I tried yesterday to put TSX TCP server script api logs and got this errors from their side.
Please, let me know how to generate debug logs in a Ekos device.
Thanks
It was in front of my nose. Sorry! Meanwhile, I solved the error by creating another clean configuration only with telescope and camera, and running meanwhile TSX as sudo. Since then, I don't have the error, nor the log to submits
BTW, I didn't find the way to auto enable TSX TCP server socket. Anybody knows?
Thanks!
In TSX go to Tools->TCP Server. A pop up window will open. Click the check box "Listening for connections". This option will stay enabled and persist across TSX restarts.
By the way, you should not need to run TSX with sudo. If the TCP server enable box not staying checked across restarts this may be why.
Hello, unfortunately it is not possible at the moment. We do not have any communication protocol to talk directly to the mount. If someone has access to one, let us know.
There is, but Software Bisque isn't sharing that. I could be outdated on this, but if you can ask them to share the communication protocol to communicate with the mount directly, that would be great.