Hello,

I performed an upgrade of the indi drivers on my Raspberry Pi and I cannot connect my Lodestar anymore.
Here is the test I am doing:

lsusb
Bus 001 Device 005: ID 04d8:003f Microchip Technology, Inc.
Bus 001 Device 096: ID 1278:0507 Starlight Xpress Lodestar autoguider

indiserver -v indi_sx_ccd
2019-04-26T12:17:14: startup: indiserver -v indi_sx_ccd
2019-04-26T12:17:14: Driver indi_sx_ccd: pid=4049 rfd=3 wfd=6 efd=7
2019-04-26T12:17:14: listening to port 7624 on fd 4
2019-04-26T12:17:14: Driver indi_sx_ccd: snooping on Telescope Simulator.EQUATORIAL_EOD_COORD
2019-04-26T12:17:14: Driver indi_sx_ccd: snooping on Telescope Simulator.TELESCOPE_INFO
2019-04-26T12:17:14: Driver indi_sx_ccd: snooping on Telescope Simulator.GEOGRAPHIC_COORD
2019-04-26T12:17:14: Driver indi_sx_ccd: snooping on Focuser Simulator.ABS_ROTATOR_ANGLE
2019-04-26T12:17:14: Driver indi_sx_ccd: snooping on CCD Simulator.FILTER_SLOT
2019-04-26T12:17:14: Driver indi_sx_ccd: snooping on CCD Simulator.FILTER_NAME
2019-04-26T12:17:14: Driver indi_sx_ccd: snooping on SQM.SKY_QUALITY
2019-04-26T12:17:54: Client 0: new arrival from 192.168.0.3:37712 - welcome!
2019-04-26T12:17:54: Driver indi_sx_ccd: stderr EOF
Child process 4049 died
2019-04-26T12:17:54: Driver indi_sx_ccd: restart #1
2019-04-26T12:17:54: Driver indi_sx_ccd: pid=4053 rfd=3 wfd=7 efd=8

Ekos logs are attached.
On Ekos, there is no error message and the connection is not happening (no green bullet).

Thank you for your help
Florian

Adding some info, ekos says driver version 1.13 Interface 6

Run the driver via gdb in the terminal:
In Ekos, create a new profile, turn off Auto Connect and add Telescope Simulator + SX CCD. Set mode to remote and leave it to localhost. In Logs, make sure to select Verbose Logging to File, check INDI + CCD. Click Start then in INDI Control Panel --> SX CCD --> Options, make sure "Driver Debug" is checked. Then go back to Main Control Panel and press "Connect". Check the terminal to see if the driver crashed, if it did, type backtrace and paste the trace here. Also attach the KStars log file.

Hello

Sorry, cannot do this I cannot add the PPA anymore:

> apt-add-repository ppa:mutlaqja/ppa
Latest INDI Library and drivers!

This PPA is for stable Ekos & INDI drivers releases.
More info: launchpad.net/~mutlaqja/+archive/ubuntu/ppa
Press [ENTER] to continue or Ctrl-c to cancel adding it.

Error: retrieving gpg key timed out.

OK, forget my last message, despite the timeout error, it seems the PPA was added.

Here is the result:

2019-04-27T12:45:18: Client 0: new arrival from 192.168.0.3:44856 - welcome!
2019-04-27T12:46:08: Driver indi_sx_ccd: sxOpen: libusb_open -> LIBUSB_ERROR_IO

Thread 2.1 "indi_sx_ccd" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x76ff1650 (LWP 5232)]
0x76e51a1c in ?? () from /lib/arm-linux-gnueabihf/libusb-1.0.so.0
(gdb) backtrace
#0 0x76e51a1c in ?? () from /lib/arm-linux-gnueabihf/libusb-1.0.so.0
#1 0x76e51cd8 in libusb_bulk_transfer () from /lib/arm-linux-gnueabihf/libusb-1.0.so.0
#2 0x00000002 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

I've triggered a rebuild and I believe it should build and update the packages in a couple of hours.

Hello, seems to be the same result:

[New process 2009]
2019-04-28T10:07:05: Driver indi_sx_ccd: pid=2009 rfd=3 wfd=6 efd=7
2019-04-28T10:07:05: Driver indi_simulator_telescope: pid=2010 rfd=4 wfd=9 efd=10
2019-04-28T10:07:05: listening to port 7624 on fd 5
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
process 2009 is executing new program: /usr/bin/indi_sx_ccd
2019-04-28T10:07:05: Driver indi_simulator_telescope: snooping on GPS Simulator.GEOGRAPHIC_COORD
2019-04-28T10:07:05: Driver indi_simulator_telescope: snooping on GPS Simulator.TIME_UTC
2019-04-28T10:07:05: Driver indi_simulator_telescope: snooping on Dome Simulator.DOME_PARK
2019-04-28T10:07:05: Driver indi_simulator_telescope: snooping on Dome Simulator.DOME_SHUTTER
Cannot parse expression `.L1207 4@r4'.
warning: Probes-based dynamic linker interface failed.
Reverting to original interface.

[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
[New Thread 0x76086320 (LWP 2011)]
2019-04-28T10:07:07: Driver indi_sx_ccd: snooping on Telescope Simulator.EQUATORIAL_EOD_COORD
2019-04-28T10:07:07: Driver indi_sx_ccd: snooping on Telescope Simulator.TELESCOPE_INFO
2019-04-28T10:07:07: Driver indi_sx_ccd: snooping on Telescope Simulator.GEOGRAPHIC_COORD
2019-04-28T10:07:07: Driver indi_sx_ccd: snooping on Focuser Simulator.ABS_ROTATOR_ANGLE
2019-04-28T10:07:07: Driver indi_sx_ccd: snooping on CCD Simulator.FILTER_SLOT
2019-04-28T10:07:07: Driver indi_sx_ccd: snooping on CCD Simulator.FILTER_NAME
2019-04-28T10:07:07: Driver indi_sx_ccd: snooping on SQM.SKY_QUALITY
2019-04-28T10:07:39: Client 0: new arrival from 192.168.0.3:53770 - welcome!
2019-04-28T10:08:01: Driver indi_sx_ccd: sxOpen: libusb_open -> LIBUSB_ERROR_IO

Thread 2.1 "indi_sx_ccd" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x76ff1650 (LWP 2009)]
0x76e51a1c in ?? () from /lib/arm-linux-gnueabihf/libusb-1.0.so.0
(gdb) backtrace
#0 0x76e51a1c in ?? () from /lib/arm-linux-gnueabihf/libusb-1.0.so.0
#1 0x76e51cd8 in libusb_bulk_transfer () from /lib/arm-linux-gnueabihf/libusb-1.0.so.0
#2 0x00000002 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Hello,

I tried to compile indi-sx from sources with older tags (from v1.7.2) and I got the same error from libusb.
So, the issue does not seem to be triggered by a change in indi-sx.
I suppose something else did. If it can help, I upgraded my RPi from ubuntu 16.04 to 18.04.
I can also reproduce identically connecting the camera directly to my laptop, which is also running 18.04.

Please find in attachment the output of sx_ccd_test.
Thanks for the help.

Florian

Hi,

I tested the sx driver yesterday and it worked with my LodestarX2 and SXVR-H9 so there must be something else wrong..??

Cs
/Markku

Hello,

This was a tough one.
It appears that the Lodestar does not support well the autosuspend feature from TLP power management.
Upgrading my Raspberry had activated it (and it is active on my laptop too).

This is the thread that helped me to find the issue:
github.com/LudovicRousseau/CCID/issues/36

As a solution, I added the following line to /etc/default/tlp:
USB_BLACKLIST="1278:0507"

Isn't there a way to prevent that from happening? udev rules?

Clear skies