So it's basically solved. Turns out I was using an old ST4-connection cable from the SBIG ST10 camera to the mount. Apparently over time the pinout of the ST4-cable was modified (reversed). So with a modern ST4-
I have managed to get my SBIG ST10 CCD camera going under INDI, and would like to use it for simultaneous autoguiding in INDI, as it is a dual chip camera.
The mount is Astro-Physics 1200 QMD (Pre-GTO version) which guides fine using the old Windows SBIG CCDOPS control program with an ST4 cable.
A few questions:
1) Can you select the same driver (SBIG CCD) also for guiding, or should I use SBIG STI for the guiding chip, is it is part of the same camera.
2) in INDI descriptions I only find a suggestion to use the 'lx200ap' driver for Astro-Physics GTOCP2 and Legacy mounts.
The mount as far as I know is using ST4 protocol, not lx200. So would this driver work with an ST4 guiding cable? Do I need another driver for this non-GTO legacy mount?
Happy to hear any suggestions to get it guiding in INDI,
Just tried it, disconnected and reconnected a couple of times, even restarted kstars and ekos, but it makes no difference.
Still 'capturing image' forever.
In guide mode I see the exposure countdown and keep looping, but I never get to see a capture result.
Thanks for the reply,
I carefully read through this thread, but I don't see an issue like my ZWO ASI120MM capture problem.
I recently installed KStars (v 2.5.0), Indi (v 1.2.0) and indi-asicam-bleeding support in Fedora 23 Linux (as referenced on the indilib.org site).
Everything seems to work fine, I can connect the ASI120MM, it replies the camera is ready, but when I start any kind of imaging sequence, it remains stuck with message 'capturing image' forever. I can only abort, it never writes an image file.
any hint would be much appreciated, as I don't have a clue for now what to try next.