> These are *NOT* RS232 ports at all
Oh! I have blindly bought such cable as it was sold by Celestron itself (hence my assumption it is the right thing!).
When testing (with "Celestron NExstar" driver) I was connecting this cable to hand controllers input only (not the mount) from what i saw on internet (www.cloudynights.com/uploads/monthly_11_...42000-1479812820.jpg)
Looks like I am not using kstars-bleeding. Not sure If I am supposed to and not sure what is the difference (does "bleeding" stands for development version? )
1) Connection: fortunately the socket is different - so you are safe. Unfortunately the driver does not support serial connection so it is only useful with celestron-nexstar-gps driver (standard celestron driver). And it should work very well.
2) Driver: the 1.6 version has definitely some problem. Could you try the 1.5 version distributed with fedora 27? It should work. You can just install kstars and libindi from the standard fedora repo.
1. I have exactly same problem when connecting with Cable and trying celestron-nexstar-gps driver. It does connect to the mount (at least it says it's connected) but It doesn't respond to any actions.
Maybe I am doing something wrong here?
2. I've disabled repo,removed and re-installed kstars and indi drivers. Looks like your driver does not come with default fedora repos.
Should I use any specific repo to get your driver 1.5 ?
What bugs me and I am little bit lost here - As you have mentioned, adding usb/cable support is tricky, but as I understand, this is already supported via "indi_celestron_gps". Unless it is not designed to work with evolutions ?
I'm creating separate topic for that driver, as I understand that both problems might be unrelated?
(indilib.org/forum/mounts/2845-indi-celes...ion-no-response.html)
celestron_gps is quite a different driver but should work the way you are trying to use (i.e. over serial cable connected to the hand controller). The main difference between nexstar and nexstar-evolution is the addition of build-in skyfi device (wifi-to-serial bridge connected to the aux interface). The rest is very similar - control-wise.
I think the problems are not really connected. The serial connection problems are usually with access rights and serial speed settings.
The evolution driver is merged now and should show up in the repos over next build cycle (approx 24h)