Issues:
1. SBIG CCD Guide configuration for port is not being saved/restored (I have to change it to sbigusb1).

2. I'm trying to set driver debug on in both panels (SBIG CCD and SBIG CCD Guide), but it's wanting to use the same session file for logging.

Connecting ST-i as SBIG CCD Guide gives this error in the logs:

Dispatch command error(-1): INDI: Could not find property CCD_TEMPERATURE in SBIG CCD Guide
<setNumberVector device="SBIG CCD Guide" name="CCD_TEMPERATURE" state="Idle" timeout="60" timestamp="2014-07-22T10:49:34">
<oneNumber name="CCD_TEMPERATURE_VALUE" min="-70" max="40" step="0">
0
</oneNumber>
</setNumberVector>

II went to the Guide panel to check the options. There was only 2 this time. I'd include exactly what they were, except the next thing I did caused a crash. I chose what I thought would be the ST-i and hit capture.

KCrash: Application 'kstars' crashing...
KCrash: Attempting to start from kdeinit
KCrash: Attempting to start directly
KCrash failed to exec(), errno = 2

plus
Could not find '' executable.

I'll repeat and get more details.

Actually, I looked at the code and decided it is best to develop the driver inline with how other INDI CCDs drivers are developed (i.e. multiple devices per driver). So stay tuned.

Restarted, Guide panel shows this now:

Guider:
1 SBIG CCD Guide
2 SBIG CCD Guider

Via:
3 SBIG CCD Guide
4 SBIG CCD

Trying combinations again:
1+3: Failed, debug logging:
...and I just saw your reply... will abandon further testing for now.

Will do and I'll be happy to test when it's done.

Ok, let's test this one thing at a time. I added support for reading the guide chip at the same time as the primary ccd, please test and let me know if it works for you.

Ok, I updated again and am trying just the ST-8XE.

I can only indoor test, however I think it's still valid. I'm using the telescope simulator as well.

I did the guide capture, "calibrate", then told it to autoguide.
Then I went to the CCD panel and told it to take a 30+ sec exposure.

I didn't get a guiding suspended message, but it doesn't seem to be doing much. Also the CCD panel never returned from capturing the image.

I re-ran the test with debugging on. It did the same as before, and stopping the main CCD exposure did not get the guiding going again.

Debug log attached of my second run.

No log attached. At any rate, there was an issue with signals/slots in Qt which caused the CCD capture progress to halt if a guide frame was captured. I'm not sure if this resolves your issue, please update to latest kstars-bleeding from GIT, or tomorrow if you're using the PPA.

D'oh - I didn't check it uploaded ok.

Anyway, I build from git/svn, so I will retry soon.

It's improved, but not there yet.

I had an issue getting the guiding going - it just hung at one point, with an error in the main panel of the sbug ccd for the guide exposure. It was set to 0, so I set it to 1 and the guiding started again.

Once started, I tried taking an image with the primary. This time it started, but the guiding seemed to stop - which was confirmed when the primary finished and a guiding suspended message appeared.

log file:

Thanks for the log. Ekos suspends guiding because you cannot read the guide head while the main CCD is downloading an image, it should resume guiding when the primary image is downloaded. I've made a few changes. Please update both indi-sbig and KStars and let me know if it works for you now. Also, if you play to use the ST-I, it should only report "SBIG CCD Guide" and no "SBIG CCD Guide Guider"!!!