×

INDI Library v1.9.3 Released (11 Nov 2021)

Bimonthly Stable INDI Library release introduces new drivers and fixes for existing ones. Some highlights:

Support for Orion StarShoot G3 CCD

  • Posts: 146
  • Thank you received: 23
Sounds great! I just posted in the thread where we started the development for this camera (indilib.org/forum/ccds-dslrs/7276-orion-....html?start=24#72665).
5 months 1 week ago #72666

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

  • Posts: 57
  • Thank you received: 8
Hi Ben. I have installed the G3 driver you just updated and to my delight found a new entry under others for the starshoot G3.  Attempted a default 1 sec exposure and crashed. Log attached. Anything I can do to help please ask.
5 months 1 week ago #72685
Attachments:

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

  • Posts: 146
  • Thank you received: 23
Thanks, I have an idea of what's wrong and will take a look tonight.
5 months 1 week ago #72687

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

  • Posts: 57
  • Thank you received: 8
After you have taken that lovely dog for a walk?
5 months 1 week ago #72693

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

  • Posts: 146
  • Thank you received: 23
She's a lot bigger now :)

The problem is that it seems you don't have permission to connect to the device. To double check, if you do lsusb you will a list of USB devices connected to your computer. The camera is labeled something like "Torex" and you should see the numbers "0722:0502". A different part of the line will show "Bus" and "Device". Then do the following:

ls -alh /dev/bus/usb/${BUS}/${DEVICE}

where ${BUS} and ${DEVICE} are the bus and device values from the line of lsusb that corresponds to the camera. You should see something like:

bgilsrud@lyra:~/lpig/indi-3rdparty/indi-orion-ssg3$ ls -alh /dev/bus/usb/001/004
crw-rw-r-- 1 root root 189, 3 Jun 21 22:10 /dev/bus/usb/001/004

We want to make sure that you have write access to the device so we want to see it show "crw-rw-rw-". If you don't see that, do:

sudo udevadm control --reload-rules
sudo udevadm trigger

Then check that file again, if you see that it shows "crw-rw-rw-", then try the driver again. If you don't, you can do:
chmod 666 /dev/bus/usb/${BUS}/${DEVICE}

and then try the driver.
 
5 months 1 week ago #72707

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

  • Posts: 57
  • Thank you received: 8
Hi Ben got further. Tried a one second exposure now get: CCD capture aborted. Capture failed. Check Indi Control Panel for details. Nothing relevant reported on the Indi control Panel.
  • udevadm didnt work so I had to use chmod. I notice on reboot the file permissions revert back crw-rw-r--
  • First time I tried taking an exposure it complained I hadn't saved the configuration under the Options Tab. Minor point.
  • I notice after it fails to take an exposure the red LED in the back of the camera is off. I have to restart Kstars to get it back on-line.
I have a raspberry pi 4 in the observatory and a pi 3 in the study for testing. The pi 4 I built using the latest astroberry image file. The pi 3 I updated from previous version of Indi to latest version earlier this year before the astroberry image had been updated because it fixed a LX200 driver problem. I have a lingering doubt if permissions or something are not quite correct on pi 3 and it might be best rebuild from latest astroberry image.  I mention this just in case this compounds the problem. However Kstars runs OK on the pi 3 so its probably not an issue.
 
5 months 1 week ago #72715
Attachments:

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

  • Posts: 146
  • Thank you received: 23
I found and fixed the bug that was causing the permission problem. I also added some code to debug the capture issue. On a side note, I was able to verify the USB commands that the driver is sending to start the exposure and it looks correct to me. Can you pull and try again and send the log?

Thanks,
Ben
5 months 1 week ago #72724

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

  • Posts: 57
  • Thank you received: 8
Ben, same error as last time. CCD capture Aborted.  I can see a new device file is created now with correct permissions.
5 months 1 week ago #72727
Attachments:

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

  • Posts: 57
  • Thank you received: 8
I am not familiar with Wireshark but could see a Get Descriptor request followed by 3 URB Control Out packets from host and destination when starting an exposure. Nothing more.
5 months 1 week ago #72733

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

  • Posts: 146
  • Thank you received: 23
If you have the wireshark capture, could you save it and attach it?
5 months 1 week ago #72734

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

  • Posts: 146
  • Thank you received: 23
I pushed a few changes. Could you run wireshark and try doing a 30s exposure then upload the debug log and the wireshark pcap file?
5 months 1 week ago #72738

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

  • Posts: 57
  • Thank you received: 8
Hi Ben. git status reports no change so I must have used latest code with previous test?  Here's the wireshark output and kstars log file for a 30 second exposure.  The camera was device file 007.
The following user(s) said Thank You: Ben Gilsrud
5 months 1 week ago #72767
Attachments:

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

Time to create page: 0.694 seconds