×

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

Bi-monthly release with minor bug fixes and improvements

[SOLVED] Can't connect to Orion Starshoot Autoguider with INDI

  • Posts: 49
  • Thank you received: 4
Hi all,

I can't seem to connect to my Orion Starshoot Autoguider from my new laptop. My device seems to be completely unrecognized by my system.

When I plug the camera to my computer (USB2), I should have a red LED on it, but it does not turn on. I have a "test" profile on Ekos, using only indi_qhy_ccd driver, and as soon as I start INDI (even before I try to connect), I get a message box saying "No QHY camera detected. Power on?".

The Ekos output looks like this:
2018-02-05T00:35:45 Unable to establish:
+ QHY CCD
Please ensure the device is connected and powered on.
2018-02-05T00:35:40 INDI services started on port 7624. Please connect devices.
2018-02-05T00:35:40 Starting INDI services...
2018-02-05T00:35:40 INDI services stopped.
2018-02-05T00:31:21 Unable to establish:
+ QHY CCD
Please ensure the device is connected and powered on.
2018-02-05T00:31:17 INDI services started on port 7624. Please connect devices.
2018-02-05T00:31:17 Starting INDI services...
2018-02-05T00:31:15 INDI services stopped.
2018-02-05T00:30:59 Unable to establish:
+ QHY CCD
Please ensure the device is connected and powered on.
2018-02-05T00:30:54 INDI services started on port 7624. Please connect devices.
2018-02-05T00:30:54 Starting INDI services...

Interestingly, the output of the 'lsusb' command is:
tan@bobby ~$ lsusb
Bus 002 Device 002: ID 0424:5742 Standard Microsystems Corp. 
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 007: ID 0c45:670c Microdia 
Bus 001 Device 005: ID 04f3:20d0 Elan Microelectronics Corp. 
Bus 001 Device 003: ID 0cf3:e300 Qualcomm Atheros Communications 
Bus 001 Device 008: ID 1856:0011  
Bus 001 Device 006: ID 138a:0091 Validity Sensors, Inc. VFS7552 Touch Fingerprint Sensor
Bus 001 Device 004: ID 04f3:0235 Elan Microelectronics Corp. 
Bus 001 Device 002: ID 0424:2742 Standard Microsystems Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Notice the empty line for Device 008? That's the autoguider, which by the way works fine on other computers.

My INDI log directory (~/.indi/logs) does not exist. My laptop (Dell XPS 13 9360) is running Arch Linux with KDE Plasma, Kstars and Ekos.

Any ideas?
Last edit: 6 years 1 month ago by Adrien Barrajon.
6 years 1 month ago #22943

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

  • Posts: 49
  • Thank you received: 4
I found the source of the problem. The /lib/udev/rules.d/85-qhy.rules was missing the lines for the vendor 1856 / product 0011. I just copy/pasted them from the 85-qhy.rules I had on my other machine. Works fine now. Not sure why those lines weren't present. I guess I'll have to reinput them manually next time there's an update.

Anyway, solved.
6 years 1 month ago #23110

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

What was the line you exactly added? So I can add it to the one we have.
6 years 1 month ago #23132

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

  • Posts: 49
  • Thank you received: 4
85-qhy.rules file attached (renamed in .txt to allow upload).

So this is the file I am now using. It originally came with the libindi_3rdparty 1.6.2 (latest version), and I added these lines:

Lines 28 - 37:
#Van Ooijen Technische Informatica
ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="081a", RUN+="/sbin/fxload -t fx2 -I /lib/firmware/qhy/QHY5.HEX -D $env{DEVNAME} -s /lib/firmware/qhy/QHY5LOADER.HEX"
ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="0818", RUN+="/sbin/fxload -t fx2 -I /lib/firmware/qhy/QHY5.HEX -D $env{DEVNAME} -s /lib/firmware/qhy/QHY5LOADER.HEX"
ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="2972", RUN+="/sbin/fxload -t fx2 -I /lib/firmware/qhy/QHY8.HEX -D $env{DEVNAME}"
ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="2970", RUN+="/sbin/fxload -t fx2 -I /lib/firmware/qhy/QHY2PRO.HEX -D $env{DEVNAME}"
ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="296c", RUN+="/sbin/fxload -t fx2 -I /lib/firmware/qhy/QHY5.HEX -D $env{DEVNAME}"
 
# Orion SSAG
ATTRS{idVendor}=="1856", ATTRS{idProduct}=="0011", RUN+="/sbin/fxload -t fx2 -I /lib/firmware/qhy/QHY5.HEX -D $env{DEVNAME} -s /lib/firmware/qhy/QHY5LOADER.HEX"
ATTRS{idVendor}=="1856", ATTRS{idProduct}=="0113", RUN+="/sbin/fxload -t fx2 -I /lib/firmware/qhy/QHY5.HEX -D $env{DEVNAME} -s /lib/firmware/qhy/QHY5LOADER.HEX"

Lines 82-86:
SUBSYSTEMS=="usb", ATTRS{idVendor}=="1856", MODE="0666"
SUBSYSTEMS=="usb", ATTRS{idVendor}=="1781", ATTRS{idProduct}=="0c7c", MODE="0666"
SUBSYSTEMS=="usb", ATTRS{idVendor}=="04b4", ATTRS{idProduct}=="8613", MODE="0666"
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0547", ATTRS{idProduct}=="1002", MODE="0666"

I wasn't sure of which would be the relevant lines to add so I just added a bunch of them, making sure I wasn't introducing conflicts with several lines having the same idVendor or id Product.
Last edit: 6 years 1 month ago by Adrien Barrajon.
6 years 1 month ago #23216
Attachments:

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

This doesn't make any sense. These lines already exist in the current 85-qhy.rules. You probably had an older 85-qhy.rules that was not overwritten by the update.
6 years 1 month ago #23218

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

Time to create page: 0.505 seconds