×

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

Bi-monthly release with minor bug fixes and improvements

QSI error on Stellarmate

  • Posts: 30
  • Thank you received: 0
I'm using a stellarmate OS on a raspberry pi 3B+, and am getting the following error when connecting to my QSI. The QSI driver I'm using is 0.8~201802271130~ubuntu16.04.1, but that appears to be an older build.


2018-05-07T14:23:40: startup: indiserver indi_qsi_ccd
2018-05-07T14:23:40: Driver indi_qsi_ccd: indi_qsi_ccd: symbol lookup error: indi_qsi_ccd: undefined symbol: _ZN4INDI13DefaultDevice8SetTimerEi
2018-05-07T14:23:40: Driver indi_qsi_ccd: stderr EOF
Child process 3019 died
2018-05-07T14:23:40: Driver indi_qsi_ccd: restart #1
2018-05-07T14:23:40: Driver indi_qsi_ccd: indi_qsi_ccd: symbol lookup error: indi_qsi_ccd: undefined symbol: _ZN4INDI13DefaultDevice8SetTimerEi
2018-05-07T14:23:40: Driver indi_qsi_ccd: stderr EOF
Child process 3020 died
2018-05-07T14:23:40: Driver indi_qsi_ccd: restart #2
2018-05-07T14:23:40: Driver indi_qsi_ccd: indi_qsi_ccd: symbol lookup error: indi_qsi_ccd: undefined symbol: _ZN4INDI13DefaultDevice8SetTimerEi
2018-05-07T14:23:40: Driver indi_qsi_ccd: stderr EOF
Child process 3021 died
2018-05-07T14:23:40: Driver indi_qsi_ccd: restart #3
2018-05-07T14:23:40: Driver indi_qsi_ccd: indi_qsi_ccd: symbol lookup error: indi_qsi_ccd: undefined symbol: _ZN4INDI13DefaultDevice8SetTimerEi
2018-05-07T14:23:40: Driver indi_qsi_ccd: stderr EOF
Child process 3022 died
2018-05-07T14:23:40: Driver indi_qsi_ccd: restart #4
2018-05-07T14:23:40: Driver indi_qsi_ccd: indi_qsi_ccd: symbol lookup error: indi_qsi_ccd: undefined symbol: _ZN4INDI13DefaultDevice8SetTimerEi
2018-05-07T14:23:40: Driver indi_qsi_ccd: stderr EOF
Child process 3023 died
2018-05-07T14:23:40: Driver indi_qsi_ccd: restart #5
2018-05-07T14:23:40: Driver indi_qsi_ccd: indi_qsi_ccd: symbol lookup error: indi_qsi_ccd: undefined symbol: _ZN4INDI13DefaultDevice8SetTimerEi
2018-05-07T14:23:40: Driver indi_qsi_ccd: stderr EOF
Child process 3024 died
2018-05-07T14:23:40: Driver indi_qsi_ccd: restart #6
2018-05-07T14:23:40: Driver indi_qsi_ccd: indi_qsi_ccd: symbol lookup error: indi_qsi_ccd: undefined symbol: _ZN4INDI13DefaultDevice8SetTimerEi
2018-05-07T14:23:40: Driver indi_qsi_ccd: stderr EOF
Child process 3025 died
2018-05-07T14:23:40: Driver indi_qsi_ccd: restart #7
2018-05-07T14:23:40: Driver indi_qsi_ccd: indi_qsi_ccd: symbol lookup error: indi_qsi_ccd: undefined symbol: _ZN4INDI13DefaultDevice8SetTimerEi
2018-05-07T14:23:40: Driver indi_qsi_ccd: stderr EOF
Child process 3026 died
2018-05-07T14:23:40: Driver indi_qsi_ccd: restart #8
2018-05-07T14:23:40: Driver indi_qsi_ccd: indi_qsi_ccd: symbol lookup error: indi_qsi_ccd: undefined symbol: _ZN4INDI13DefaultDevice8SetTimerEi
2018-05-07T14:23:40: Driver indi_qsi_ccd: stderr EOF
Child process 3027 died
2018-05-07T14:23:40: Driver indi_qsi_ccd: restart #9
2018-05-07T14:23:40: Driver indi_qsi_ccd: indi_qsi_ccd: symbol lookup error: indi_qsi_ccd: undefined symbol: _ZN4INDI13DefaultDevice8SetTimerEi
2018-05-07T14:23:40: Driver indi_qsi_ccd: stderr EOF
Child process 3028 died
2018-05-07T14:23:40: Driver indi_qsi_ccd: restart #10
2018-05-07T14:23:40: Driver indi_qsi_ccd: indi_qsi_ccd: symbol lookup error: indi_qsi_ccd: undefined symbol: _ZN4INDI13DefaultDevice8SetTimerEi
2018-05-07T14:23:40: Driver indi_qsi_ccd: stderr EOF
Child process 3029 died
2018-05-07T14:23:40: Driver indi_qsi_ccd: Terminated after #10 restarts.
2018-05-07T14:23:40: good bye
5 years 10 months ago #25860

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

  • Posts: 30
  • Thank you received: 0
I switched to the nightly build and removed/installed the qsi driver and found the error is gone and the QSI runs fine. The new version of the qsi driver I'm using is 0.8~201805061330~ubuntu16.04.1. However, I'm not totally comfortable sitting on the nightly build for my imaging rig. Is it possible to push the changes to the stable build?

Gabe
5 years 10 months ago #25861

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

There were no changes to the driver, this is simply a packaging issue. I will retrigger the stable QSI build.
5 years 10 months ago #25880

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

Time to create page: 0.248 seconds