I'm playing with my new toy, the EAF, and noticed some irregularity:
If I use the EAF via ASICAP, then quit ASICAP and start INDI/EKOS, it will not properly connect to the EAF. It can read some settings, but fails to set max position and (reverse) direction. Tuning the device is also not possible. I have to powercycle the EAF and restart INDI to be able to control the EAF again.
Same happens the other way round: After I have used it with INDI, ASICAP will not detect the EAF anymore, unless I powercycle it.
I am using Linux with ASICAP 1.6.1 and the latest INDI/KStars versions from GIT.
- Looking closer at that, I could see that if I disconnect the EAF in ASICAP, and then connect again, it will be in 'moving mode' (the control window for the EAF shows 'Stop' in the button, instead of 'Goto Position').
- On INDI side the problem is solved now (git version) by calling EAFStop() during initialization.
- After having used it via INDI I still need to re-plug the USB cable of the EAF, else ASICAP will not see it at all