×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

Unable to connect to QSI 690 from RPi3

  • Posts: 97
  • Thank you received: 20
Hi Guys,

I'm unable to connect my QSI 690 to INDI server running on a Raspberry Pi3 and a freshly installed copy of Ubuntu Mate 16-04.

Here is the output of lsusb:

Bus 001 Device 006: ID 0403:eb49 Future Technology Devices International, Ltd
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

When starting up Indi using:
indiserver -v indi_qsi_ccd

I see:

2016-05-19T22:33:44: startup: indiserver -v indi_qsi_ccd
2016-05-19T22:33:44: Driver indi_qsi_ccd: pid=2249 rfd=3 wfd=6 efd=7
2016-05-19T22:33:44: listening to port 7624 on fd 4
2016-05-19T22:33:44: Driver indi_qsi_ccd: snooping on Telescope Simulator.EQUATORIAL_EOD_COORD
2016-05-19T22:33:44: Driver indi_qsi_ccd: snooping on Telescope Simulator.TELESCOPE_INFO
2016-05-19T22:33:44: Driver indi_qsi_ccd: snooping on CCD Simulator.FILTER_SLOT
2016-05-19T22:33:44: Driver indi_qsi_ccd: snooping on CCD Simulator.FILTER_NAME

I’ve enabled driver loggingin Indi Control Panel, when attempting to connect to the camera from clients like Cloudmakers AstroImager or Pixinsight new IndiDeviceController, I see the following entries in indi_qsi_ccd log file:

INFO 192.632082 sec : Session log file /tmp/indi_qsi_ccd_2016-05-19T22:33:44.log
INFO 306.267140 sec : Debug is disabled.
INFO 322.541949 sec : Attempting to find QSI CCD...
ERROR 322.545515 sec : Error: put_Connected(true) failed. 0x0:Cannot open camera connection.
INFO 350.973749 sec : Attempting to find QSI CCD...
ERROR 350.976698 sec : Error: put_Connected(true) failed. 0x0:Cannot open camera connection.
INFO 352.316165 sec : Attempting to find QSI CCD...
ERROR 352.319047 sec : Error: put_Connected(true) failed. 0x0:Cannot open camera connection.
INFO 475.041974 sec : Debug is enabled.
INFO 483.839470 sec : Attempting to find QSI CCD...
ERROR 483.842065 sec : Error: put_Connected(true) failed. 0x0:Cannot open camera connection.

Can someone please help me how to fix this issue?
7 years 10 months ago #8374

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

I added the device id to the driver, should be working tomorrow.
The following user(s) said Thank You: giorgio
7 years 10 months ago #8383

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

  • Posts: 97
  • Thank you received: 20
Thank you very much Jasem! I'll update the driver tomorrow and let you know.
7 years 10 months ago #8384

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

  • Posts: 97
  • Thank you received: 20
Hi Jasem,
After having done an apt-get update followed by apt-get upgrade the QSI690 seems to be detected but indiserver now terminates after 10 attempts.

I see the following logs repeated 10 times:

giorgio@astropi3:~$ indiserver -vv indi_qsi_ccd
2016-05-22T17:22:37: startup: indiserver -vv indi_qsi_ccd
2016-05-22T17:22:37: Driver indi_qsi_ccd: pid=22899 rfd=3 wfd=6 efd=7
2016-05-22T17:22:37: listening to port 7624 on fd 4
2016-05-22T17:22:37: Driver indi_qsi_ccd: sending <getProperties version='1.7'/>

2016-05-22T17:22:37: Driver indi_qsi_ccd: read <getProperties device='Telescope Simulator' name='EQUATORIAL_EOD_COORD'>
2016-05-22T17:22:37: Driver indi_qsi_ccd: snooping on Telescope Simulator.EQUATORIAL_EOD_COORD
2016-05-22T17:22:37: Driver indi_qsi_ccd: read <getProperties device='Telescope Simulator' name='TELESCOPE_INFO'>
2016-05-22T17:22:37: Driver indi_qsi_ccd: snooping on Telescope Simulator.TELESCOPE_INFO
2016-05-22T17:22:37: Driver indi_qsi_ccd: read <getProperties device='CCD Simulator' name='FILTER_SLOT'>
2016-05-22T17:22:37: Driver indi_qsi_ccd: snooping on CCD Simulator.FILTER_SLOT
2016-05-22T17:22:37: Driver indi_qsi_ccd: read <getProperties device='CCD Simulator' name='FILTER_NAME'>
2016-05-22T17:22:37: Driver indi_qsi_ccd: snooping on CCD Simulator.FILTER_NAME
2016-05-22T17:22:37: Driver indi_qsi_ccd: read <defSwitchVector device='QSI CCD' name='CONNECTION'>
2016-05-22T17:22:37: Driver indi_qsi_ccd: read <defTextVector device='QSI CCD' name='DRIVER_INFO'>
2016-05-22T17:22:37: Driver indi_qsi_ccd: read <defSwitchVector device='QSI CCD' name='DEBUG'>
2016-05-22T17:22:37: Driver indi_qsi_ccd: read <defSwitchVector device='QSI CCD' name='CONFIG_PROCESS'>
2016-05-22T17:22:37: Driver indi_qsi_ccd: read <defTextVector device='QSI CCD' name='ACTIVE_DEVICES'>
2016-05-22T17:22:38: Driver indi_qsi_ccd: stderr EOF
2016-05-22T17:22:38: Driver indi_qsi_ccd: restart #1
2016-05-22T17:22:38: Driver indi_qsi_ccd: pid=22901 rfd=0 wfd=6 efd=7
2016-05-22T17:22:38: Driver indi_qsi_ccd: sending <getProperties version='1.7'/>

after the 10th time I see:

2016-05-22T17:22:48: Driver indi_qsi_ccd: Terminated after #10 restarts.
2016-05-22T17:22:48: good bye

Would you know what the issue might be now?

Thank you for your help.
Giorgio
7 years 10 months ago #8448

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

  • Posts: 97
  • Thank you received: 20
please disregard my previous message. After another apt-get update, apt-get upgrade I can connect to the camera from both Cloudmakers AstroImager and Pixinsight.

Thank you,
Giorgio
7 years 10 months ago #8449

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

  • Posts: 97
  • Thank you received: 20
I confirm I'm now able to connect to the QSI690 from the Raspberry Pi3, set the cooler and operate the filter wheel. However, when I try to set an exposure time in the driver Expose section, it returns the following error in the logs and on screen.
I'm not getting any error when I manually open and close the shutter using the driver switch.

ERROR 413.872768 sec : StartExposure() failed. 0x80040400:Option not available on this model.
INFO 468.920820 sec : Shutter opened manually.
INFO 472.473637 sec : Shutter closed manually.

Would you know what might be causing this?

Thank you,
Giorgio
7 years 10 months ago #8454

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

Yes, looks like pre flushing is not supported on your model. I made it so that it only logs the result but shouldn't fail the exposure itself. Should be in PPA tomorrow.
The following user(s) said Thank You: giorgio
7 years 10 months ago #8458

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

  • Posts: 97
  • Thank you received: 20
Hello Jasem,

Thank you again for your support on this. I've updated the qsi driver and I no longer get error:
StartExposure() failed. 0x80040400:Option not available on this model.

Unfortunately I'm not completely out of the woods yet. I'm still unable to get an exposure, I do see the following message in the driver log no matter what exposure time I try to set:

WARNING 158.384030 sec : Exposure shorter than minimum ExposureRequest 0.0001 s requested.
Setting exposure time to 0.0001 s.

After seeing that warning the camera seemingly disconnects. Here is the full content of the log:

INFO 114.391743 sec : Session log file /tmp/indi_qsi_ccd_2016-05-24T22:19:12.log
INFO 128.639598 sec : Attempting to find QSI CCD...
INFO 129.275308 sec : CCD is online. Retrieving basic data.
INFO 129.291484 sec : The CCD Temperature is 0.000000.
INFO 129.292263 sec : QSI 690 Series Camera
INFO 129.292333 sec : The filter count is 8
DEBUG 129.446930 sec : Setting default binning 1 x 1.

WARNING 158.384030 sec : Exposure shorter than minimum ExposureRequest 0.0001 s requested.
Setting exposure time to 0.0001 s.

Thank you,
giorgio
7 years 10 months ago #8490

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

Hopefully tomorrow's update will fix the issue.
The following user(s) said Thank You: giorgio
7 years 10 months ago #8491

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

Time to create page: 0.462 seconds