I am using Ekos. I assume you mean the Paramount driver?

I did a quick test with the Paramount driver against TSX running the mount simulator. I will test with the MX+ tomorrow.

Initial feedback:

- The TCP connection establishes, TSX sees it and registers transactions
- The driver does not actually register as connected and gives the error "unable to connect to telescope: (0).
- The IP and port settings do not persist between restarts of indi server

I'll keep digging into this.

Thanks for testing. Please enable DEBUG logging from the driver to file. Check my signature for details. For IP & Port settings, go to Options --> Configuration --> Save

Submit log so we can check what went wrong exactly.

OK. It seems to be working with the mount attached. I did some basic tests and everything seemed to go well. Parking, unparking, turning tracking on/off, slews, etc all seem fine at least in the "lab". I'll need to dig into this a bit more once my next stint of travel finishes up - probably 2 weeks or so. On my todo list are guiding, astrometry-based slews, and general imaging. Anything else specifically I should test out? I can run a few more tests this weekend but they'll all be indoors.

I've attached the debug log file in case it is helpful.

This is very exciting. Thanks much for getting this going!

I did another test using the telescope simulator in TSX. Seems to work now. If that works, it might be that users with non-bisque mounts may like this option as it can allow them to take advantage of TPoint. Maybe renaming the driver to TSX or TheSkyX would be apropos to such a case.

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!

Sounds good.

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().

Thanks again!

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

INDI Paramount log could be useful.

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

Check my signature.

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.

Assuming your running TSX on linux this may be helpful:
www.bisque.com/sc/forums/t/31745.aspx