Please update this issue should be fixed now.

Thanks again Rob. So what should I do after I start up INDI server from the command line?
Should I start KSTARS and try and connect from the "local" service, or connect remotely. If remotely, how exactly do I do that?

Also - I think it would be best if have KSTARS running my mount properly before I attempt to move into EKOS, do you agree?

Peter

Here's some screenshots showing what I was trying to do, and perhaps it's just user error. I will post server logs soon.
(see attached PDF).



As far s I can tell, this is the procedure to connect KSTARS to a mount. I just tried again with both AstroTelescope and Skysafari and the mounts runs perfectly. So the physical connections to the Mac are working well.

Peter,

Are you planning to use KStars for Astrophotography or just for controlling the mount? If you want to do astrophotography you will want to use Ekos which is the dome button on the toolbar. If not, then your method to connect using device manager is fine.

To run the test I mentioned in my other post, running indi from the command line and connecting to it "remotely" from kstars, you can use this interface instead of Ekos but you will need to follow these steps after you do the steps I posted before to get the indiserver started.

0. Follow the steps in my other post to get the embedded Indiserver started from the command line.
1. In device manager, click the Client tab (not the Local/Server tab
2. Click the add button.
3. Type a name you will use to remember this host.
4. For the Host, type localhost
5. For the port, type 7624 and then click ok.
6. Click, connect (in device manager)
7. When the Indi control panel pops up, click Connect.

Now a lot of stuff should be printing in the Terminal, basically it is everything the driver is doing. Save or copy that transcript.

Thanks,

Rob

Here's the log from the terminal, following your instructions.
The Connect green light is on, but the scope does not respond to any commands.



PS: I want to use EKOS for photography and KSTARS to control the mount. I had thought that if I can't get KSTARS to work, EKOS will not be much use.

Thanks, we're very close to the problem. But one more step is required. Before you connect, go to Options --> Enable Debug then you'll see two new properties for Debug & Logging, Check all Logging checkboxes on and select "Log to File" (See signature for more details). You'll get a detailed log file for the mount communication. Attach this file.

The reason I was asking is because I actually have never connected my mount with device manager. I have always just used Ekos. But yes, this has been useful in this case since you really don't need to connect a camera or to get Ekos all started up just to check if the mount connects properly.

I don't see any Mac-specific driver problems in that terminal output. When we had problems with the Mac build in the first couple of months, it was generally related to dylibs not being present or required files missing. These problems were revealing themselves in the terminal output. That does not appear to be the problem here. The terminal just said a child process died, though it did give more information as to when it happened, it did not reveal why it happened, since I don't think the output directly before the statement that it died has anything to do with it (but I could be wrong).

So yes, I would try what Jasem said, maybe it will reveal more info.

Hopefully it gets solved soon.

Thanks,

Rob

Here's the new INDI log from today, along with the debug log.

I forgot the INDI log. I went back in and turned on the INDI logging, then connected with the internal server, which of course crashed right away.
Here's the log:

Another attempt with INDI logs on, and trying to start up from KSTARS and then EKOS. Trying to find something different - but I still get the same error message and crash.

Nice work Peter, I think that should help get the problem diagnosed. I don't have experience with an ioptron mount or the ioptron driver, though I do have a sky tracker. But from looking at each log, it seems it updates the information such as GPS successfully and then there is a crash. The INDI log that you attached does list the commands sent and the response received. I think the last one might indicate the problem. Jasem should be able to help you with that much better than I can.

Thanks and good luck,
Rob