×

INDI Library v1.9.8 Released (29 Sep 2022)

Bi-monthly INDI Library released with new drivers and bug fixes.

Support for Orion StarShoot G3 CCD

  • Posts: 7
  • Thank you received: 0
You were just right ! Access rights related to the above file were rw-rw-r.
I added write access to all (file owner and group is root), so I changed file access properties to rw-rw-rw. The camera is now connected, and giving regular pictures with EKOS either as main CCD or autoguider. Cooling is also ok. It's just so great to have this almost unknown camera back to business !
Only trouble is that if I disconnect the USB cable and connect it back again, the device number is updated, and I have to chmod 666 again the BUS/DEVICE file. There may be a way to avoid this little pain.
1 year 2 weeks ago #77746

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

  • Posts: 148
  • Thank you received: 24
I'm glad to hear it works!

How did you install the driver? It should come with a udev file (99-orionssg3.rules) to automatically set the permissions, so I'm not sure why that's not working.
1 year 2 weeks ago #77749

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

  • Posts: 7
  • Thank you received: 0
I installed it through the package manager under the raspbian / astroberry environment, searching for INDI, and locating the orion g3. No git, no .deb execution, no compilations...
I'm really not a linux expert, sorry about this. Where is the file you mention supposed to be located ?
1 year 2 weeks ago #77750

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

  • Posts: 148
  • Thank you received: 24
I finally got around to implementing binning and subframing. To try it out, do:
git clone github.com/bgilsrud/indi-3rdparty.git
cd indi-3rdparty
git checkout ssg3_updates

Then you can build the drive like you normally would. I don't have one of these cameras, so I can only simulate how I think it should behave and I was able to see the USB sequences that I was expecting. I think the most useful test would be to take a recognizable image with binning enabled...there's a good chance that the frame will be reassembled incorrectly. The code will still attempt to deinterlace the downloaded image, which I'm thinking is not correct when binning is enabled.
 
1 year 1 week ago #78151

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

  • Posts: 148
  • Thank you received: 24
I think the file should be at /usr/lib/udev/rules.d/99-orionssg3.rules. Do you still see this problem after rebooting?
1 year 1 week ago #78152

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

  • Posts: 22
  • Thank you received: 5
I got your code cloned and built.  I am trying to shoot some recognizable images with it but since it is mid-day here I need to do short exposures to avoid maxing out the pixel counts.  This means that the issue with short exposures that I mentioned before is rearing its ugly head.  I will try to get some properly exposed subframed and 2x2 binned images and/or captures tonight and let you know how that part of the code is working.  In the meantime though here is a packet capture of the problematic 0.25 second exposures.  I took a first exposure, which seemed to download just fine, then waited a few seconds and tried a second one.  The second one downloaded but it paused for a really long time during the download. Hopefully this capture has what you need to figure out why this is happening.  In any case though I will investigate the subframing/binning code tonight when it is a bit darker.
1 year 6 days ago #78167
Attachments:

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

  • Posts: 148
  • Thank you received: 24
I pushed another branch called bin_no_deinterlace. This has the same changes as the other branch and an additional change to not deinterlace the frame if y-binning is enabled. I think this will work better, but I it would be nice if you could test both and find out for sure.
1 year 6 days ago #78170

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

  • Posts: 7
  • Thank you received: 0
I Ben, I copied this file from the web repository into the above folder and everything seems to be working now. Great !
1 year 1 day ago #78324

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

  • Posts: 59
  • Thank you received: 9
After an extended break from the G3 (a new ASI camera and not a lot of astro photography) I worked through the build of the indi-orion-ssg3 driver tonight and took a couple of test shots.
Not connected to a scope (it's raining here so that would not have helped much).

Very big thanks to those who stuck with this and got it working.

Looking forward to trying it on the sky sometime soon and see what it does..
4 months 2 weeks ago #84577

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

  • Posts: 1
  • Thank you received: 0
hmm, strage. Yeah I did double check that I pushed it. If you do a "git log" the most recent commit should be "fix half-frame download issue". get-vidmateapp.com mobdro download
Last edit: 4 months 1 week ago by hmmmhaa.
4 months 1 week ago #84598

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

  • Posts: 148
  • Thank you received: 24
The driver is available in the standard indi release, so you shouldn't have to build it. I'm using Jasem's PPA and can install it by doing "apt-get install indi-orion-ssg3".

-Ben
4 months 1 week ago #84608

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

  • Posts: 59
  • Thank you received: 9
Some notes which may relate to the earlier permission issue.
I went to setup the Camera driver on my primary control Raspberry Pi (trying to get two setups built) and of course didn't check back here first (Duh!).

I updated my 3rdparty repository and built from source then after hitting permission issues saw the comment that the package could be installed directly and tried that in the hope it would fix issues.
Permission issues still remained.

I found that I have several copies of the 99-orionssg3.rules file.
/etc/udev/rules.d/99-orionssg3.rules
/lib/udev/rules.d/99-orionssg3.rules
/home/astroberry/Projects/indi-3rdparty/indi-orion-ssg3/99-orionssg3.rules
I'm assuming run time issues would be in one of the first two and the repository one is just source for my build.

The copy under /etc Had an idVendor of 0722 and some specifics for the G3. The other two are generic for all Orion Camera with an idVendor 07ee. I've edited the /etc copy and added the general rule as well as changing the idVendor and am through the basics successfully.
The /lib and repository copies look like this
# All Orion Cameras
SUBSYSTEMS=="usb", ATTR{idVendor}=="07ee", MODE="0666"

The /etc copy was
ACTION=="add", ATTR{idVendor}=="156c", RUN+="/bin/sh -c '/bin/echo 256 >/sys/module/usbcore/parameters/usbfs_memory_mb'"

SUBSYSTEM=="usb", ACTION=="add", ATTR{idVendor}=="0722", ATTR{idProduct}=="0502", MODE="0666", SYMLINK+="orionssg3.%n"

It's now
ACTION=="add", ATTR{idVendor}=="156c", RUN+="/bin/sh -c '/bin/echo 256 >/sys/module/usbcore/parameters/usbfs_memory_mb'"

SUBSYSTEM=="usb", ACTION=="add", ATTR{idVendor}=="07ee", ATTR{idProduct}=="0502", MODE="0666", SYMLINK+="orionssg3.%n"

# All Orion Cameras
SUBSYSTEMS=="usb", ATTR{idVendor}=="07ee", MODE="0666"

From lsusb
Bus 001 Device 007: ID 07ee:0502 Torex Retail (formerly Logware)

I've taken a couple of basic sitting on the desk shots to confirm something happens. Hoping to give this thing some work this weekend.
4 months 1 week ago #84751

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

Time to create page: 0.779 seconds