×

INDI Library v2.0.7 is Released (01 Apr 2024)

Bi-monthly release with minor bug fixes and improvements

2 Sbig Cameras, remote operation

  • Posts: 205
  • Thank you received: 19
I've got 2 Sbig cameras, a ST8 and a STi that are my CCD and guide cameras respectively.

I'm trying to start the indiserver with all my devices, but I can't work out how to get the STi to start.

I've tried adding the indi_sbig_ccd driver to the command line twice, but while that started 2 of them in the process list, ekos didn't find the STi when I connected remotely.

All the other devices and the ST8 seem to be ok.

Is there a way to bind the driver to the correct config to invoke each camera? Or am I suppose to invoke the server in some other manner? Do I need to do anything special in the remote ekos client connecting to the server?
8 years 4 months ago #6110

Please Log in or Create an account to join the conversation.

SBIG driver only support one-camera-per-driver. So your best option is to start INDI server in FIFO mode and then start each driver with a unique name afterwards:
mkfifo /tmp/indififo
indiserver -v -f /tmp/indififo

Open another console and start the drivers:
echo start indi_sbig_ccd -n \"ST8\" > /tmp/indififo
echo start indi_sbig_ccd -n \"STi\" > /tmp/indififo

In Ekos, make sure to go to Ekos options in KStars settings, and set the CCD to "ST8" and Guider to "STi" before you try to connect.
The following user(s) said Thank You: Chris Ryan
8 years 4 months ago #6112

Please Log in or Create an account to join the conversation.

  • Posts: 205
  • Thank you received: 19
Just tested this and it works perfectly. Thanks.
8 years 4 months ago #6121

Please Log in or Create an account to join the conversation.

No problem, can you test the STi under Raspberry PI? I tested it here and capture is very slow.
8 years 4 months ago #6123

Please Log in or Create an account to join the conversation.

  • Posts: 205
  • Thank you received: 19
Looks like I've got some debugging to do.

I'm using the Guider panel to try to capture an image (it'll be dark since it's afternoon here and the scope is covered, but it doesn't matter).

Here's some debug output:
INFO	7503.694707 sec	: Session log file /tmp/indi_sbig_ccd_2015-12-06T06:50:17.log
DEBUG	7510.806754 sec	: Aborting Primary CCD Exposure...
DEBUG	7510.808680 sec	: Exposure cancelled.
DEBUG	7510.808885 sec	: Exposure Params. CCD (0) openShutter(1), exposureTime(100), binnig (1), left (0), top (0), w(324), h(243)
DEBUG	7510.858985 sec	: Light Frame exposure in progress...
DEBUG	7510.859161 sec	: Primary CCD Exposure Time (s) is: 1
DEBUG	7511.526951 sec	: Primary CCD exposure in progress with 0 seconds left.
DEBUG	7512.528765 sec	: Primay CCD exposure done, downloading image...

Not sure why the abort is there. Maybe from a previous attempt?
8 years 4 months ago #6124

Please Log in or Create an account to join the conversation.

Time to create page: 0.200 seconds