Focuslynx/Focus Boss not connecting to MacOS via USB #34799
Well for me at least, I have just had quite a bit to do recently. In January I had to completely remake a website at the same time that I had to finish up my students grades at the same time I was trying to rewrite the KStars for Mac build script. So I haven't had a lot of extra time to look into things like this. But now I should be able to get to them.
Focuslynx/Focus Boss not connecting to MacOS via USB #34896
I though the main problem I had was KStars not recognising my USB-RS232 adapter that Optec/Starlight have been so kind to include with the package.
So I went to FTDI website and downloaded the driver.
Now instead of a generic /dev/cu.usbserial, KStars sees /dev/cu.usbserial-A504AP6U, which is the USB device showing in my Mac's System Information.
Happy as a baby I tried to connect... nothing
Changed the BAUD rate to all the available ones from 9600 to 230400...nothing
I can't get my head around this, but my knowledge of this things is like Shakespeare to an ant...
P.S: maybe a Timeviewer session with you controlling my Mac could be in order, so you can see what's happening...
Focuslynx/Focus Boss not connecting to MacOS via USB #49123
no, not really. I've ended up only using the StellarMate (which, BTW, is an excellent device), and, not receiving much support from the coders here, gave up on the pursuit of perfection.
But if you pester them enough, I reckon they might tackle this issue again.
It's not that they are lazy, it's just that for them is unpaid charity work, so they have to do it in their spare time.
And astronomical vendors aren't making things easy for them, with their idiotic focus on Windows-only support.
Apple is not cooperating either, with their habit of throwing wrenches into low-level USB access with every iteration of their MacOS and their secretive attitude.
Unfortunately, this winter I haven't been able to use my telescopes even once, due to bad conditions (transparency, seeing, clouds, you name it), so I'm kinda out of touch with the whole issue.
Good luck, and please keep me informed of any developments
Focuslynx/Focus Boss not connecting to MacOS via USB #49351
Except for the "pester them" (a human does it's best when he is motivated and not when he is pestered) I agree with you.
The problem we are facing is most probably a problem of the Mac itself and therefore the possibilities for support from this forum is limited.
I'd like to ask another question here.
The FocusLynx can also be connected with an ethernet connection. I tried this but cannot make a successful connection. Can anybody quickly explain me what the "ethernet connection mode" in Indi's Focusser tab means? I start Ekos with the "local mode". Does this not mean that all devices it manages are connected locally and directly to my Mac? But Indi expects an IP and a port for a ethernet connection which seems to me like being a remote connection. I entered my Mac's IP address and Indi's port but the connection didn't succeed. I'm using a normal ethernet cable without a router and hook FocusLynx to the Mac directly.
Shouldn't it be possible to connect FocusLynx with ethernet to a local mode Ekos/Indi service?
Focuslynx/Focus Boss not connecting to MacOS via USB #49353
Sorry I know I said I would help with this soon, but I have been busy trying to fix an issue for some people with non-homebrew installations of python on OS X. They can't plate solve. Also I need to make a DMG for 3.4.0. As soon as all this is done, I promise I will take a look at this.
Focuslynx/Focus Boss not connecting to MacOS via USB #49396
I'm still trying to connect the FocusLynx to INDI.
Reading the thread "Serial timeout with Moonlite Focuser"
gave me hopes as in this thread a solution was published to successfully connect a FTDI USB/Serial focuser. Its not the same focuser as the FocusLynx but I tired to do the same as published there (installing the older version of the FTDI driver).
Unfortunately no success, still the "TTY timeout" message.
I can confirm that the driver is successfully loaded in macOS, the system report of the extensions confirmed this. The USB/Serial port is visible and available and INDI can also see the port, but cannot establish a connection.
Maybe this helps a bit in isolating the problem.