×

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

Bi-monthly release with minor bug fixes and improvements

StellarMate OS and Orion SSAG Pro

  • Posts: 4
  • Thank you received: 0
Hi,

I'm using StellarMate OS on a Raspberry Pi 3+ Plugging in the SSAG Pro does nothing much.
The camera doesn't appear when running lsusb. Running tail -f on syslog on plug-in shows the usb device is detected, but that no drivers are loaded.
I've updated the StellarMate to the latest software (as of this afternoon). I've seen on another thread that people have got the camera running, by editing a udev rule, but I don't have the rule to start with. I've been running linux for years, so I'm quite comfortable creating anything I need, I just don't really want to break StellarMate OS.

Does anyone know if upgrading to latest indi from the PPA will break StellarMate?

David
5 years 3 weeks ago #35776

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

Upgrading from the PPA is fine since StellarMate is using that PPA to start with. Regarding SSAG, the only supported version is the older version based on QHY5. What's the output from dmesg when you plug that camera in?
5 years 3 weeks ago #35791

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

  • Posts: 4
  • Thank you received: 0
I've upgraded to the latest INDI - it made no difference. I then moved to the nightly release do I could try the indi-sssag package. This installed fine, but the camera still doesn't seem to be detected.

Output from dmesg on plugging in the camera:
[44820.427273] usb 1-1.4.1: new high-speed USB device number 10 using dwc_otg
[44820.557664] usb 1-1.4.1: New USB device found, idVendor=16c0, idProduct=29a2
[44820.557680] usb 1-1.4.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
5 years 3 weeks ago #35811

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

So I see 16c0 already in 85-qhyccd.rules (part of libqhy package), but with different product IDs.. you can try editing to /lib/udev/rules.d/85-qhyccd.rules

Then try to replicate one of the rules for your camera. Though do this at your own risk as uploading the wrong firmware could break your camera. After editing the file, reload the rules:
sudo udevadm control --reload-rules

Then unplug and replug the camera.
5 years 3 weeks ago #35812

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

  • Posts: 4
  • Thank you received: 0
I tried both of these with no luck (if it's QHY5 based, these seemed like a reasonable choice)
(only one at a time)
ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="29a2", 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}=="29a2", RUN+="/sbin/fxload -t fx2 -I /lib/firmware/qhy/QHY5.HEX -D $env{DEVNAME}"

dmesg output was
[50756.552342] usb 1-1.4.1: new high-speed USB device number 13 using dwc_otg
[50756.682735] usb 1-1.4.1: config 1 interface 0 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64
[50756.683109] usb 1-1.4.1: New USB device found, idVendor=16c0, idProduct=296d
[50756.683121] usb 1-1.4.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[50756.683129] usb 1-1.4.1: Product: QHY5-CMOS
[50756.683138] usb 1-1.4.1: Manufacturer: QHY_CAMS
[50756.684148]usb 1-1.4.1: device descriptor read/64, error -110

I do a bit of hardware development, so I took a look at the camera PCBs to see if the IC markings would offer any suggestions, they had all had their markings sanded off. The camera still works with the windows drivers, so nothing has caused permanent damage. I might take a look at the windows driver to see if I can figure out what's going on.
5 years 3 weeks ago #35819

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

  • Posts: 4
  • Thank you received: 0
I've not had much time to look at this since last week, but I did just manage to get a quick capture of the USB bus as the camera is plugged in. I also caught another session where it's plugged in and captures a couple of dark frames at native resolution.

The captures are in wireshark format if anyone is interested.
www.dropbox.com/sh/4k7fbv1vn2ttotu/AABKW...UVrgDB0t7L7HLaa?dl=0

David
5 years 2 weeks ago #36241

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

Time to create page: 0.521 seconds