I've got a ST-8XE and a ST-i that I'd like to connect up with ekos. Although the ST-8XE can do it all, I'd like to be able to connect the ST-i as well if I need to have a guider in front of the filter.

However, in the ekos setup (CCD and Guider device selection), I can't choose 2 different SBIG CCD - I get just one camera appearing. Each camera connects fine if I use them separately. I note that if I have them both connected, one will be sbigusb0, the other sbigusb1.

How do I handle this?

Well this issue is now resolved (took a lot of changes fo hopefully no regression bugs) but no tested well. For Ekos in local mode, it should work OK, but for remote devices with 2 SBIGs, then you need to rename one of them using INDI server FIFO.

Then from another terminal:

This renames the 2nd SBIG Driver to ST-I, so just specify ST-I as the Guider in Ekos option.

Forgot to mention that if you want to use the guide chip on the SBIG, then do NOT set the guider to SBIG CCD, just select the CCD as SBIG and it will auto-detect the guide chip and use it. Only set the guider if you have using a DIFFERENT physical device than the CCD. For ST-I, you need to set the guider to "SBIG CCD" and you will get "SBIG CCD Guide" for the ST-I.

Can you also update indi-sbig and test if you can now capture using the primary CCD and the guide chip simultaneously? I made a change that _might_ permit that.

Wow, excellent. I'll update everything and test what I can - indoors only for now unfortunately.

Right, I've updated everything.

Fired up ekos to test ST-8XE and a ST-i together, testing local mode.
Chose SBIG CCD for both CCD and Guider.
Got SBIG CCD and SBIG CCD Guide panels as you described.
Set the correct port and connect fine.

All good so far.

Now things get confusing in the CCD and Guide panels.

In the CCD panel, I get 4 options for Device:
SBIG CCD Guide
SBIG CCD Guide Guider
SBIG CCD
SBIG CCD Guider

1. As you would expect SBIG CCD works ok and gets an image from the ST-8XE.
2. SBIG CCD Guide starts to capture an image from the ST-i, but doesn't complete, I have to abort.
3. SBIG CCD Guide Guider gives the error - Failed to set sub frame.
4. SBIG CCD Guider works ok (prints a message saying - "" frame type is unknown - I suspect because the Type field is disabled) and returns an image, I assume from the ST-8XE guider chip from the image size.

The options list is confusing, but not unusable. I wonder if it would be better to use the Product Name in the options list (or add it to the panel name displayed)?

Now the Guide panel.
Guider options listed are:
1 SBIG CCD Guide
2 SBIG CCD Guide Guider
3 SBIG CCD Guider

Via:
4 SBIG CCD Guide
5 SBIG CCD
6 SBIG CCD Guide
(yes, listed twice)

Now to try the combinations to try to capture an image (same session, no restarts, most combos should not make sense):
1+4 - Starts to capture an image, never returns?, no errors displayed. I try aborting via control panel but get a stop exposure error.
1+5 - Starts to capture an image but nothing happens.
1+6 - Same as 1+5

2+4 - Same as 1+5
2+5 - Same as 1+5
2+6 - Same as 1+5

3+4 - Works - I think this is the ST-8XE guide chip given the image size.
3+5 - Same as 3+4
3+6 - Same as 3+4

I'll post this so far, but I'm going to go back to the beginning again (restart everything), switch on all the debugging I think might be useful and repeat some tests.

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.