Thanks for the speedy feedback, guys!

I updated EkosVM and the image is now the same as that taken from the Pi. Both are reporting version 1.6. I've attached a screenshot.

The connection also seems flakier now. After I've taken a shot, I'm usually unable to take another until I disconnect the device and shut down the local indi server and then fire it back up.

Several weeks ago, I started toying with the idea of INDI device development. I grabbed Eric Holmes' OpenSSAG code and was able to build it without issue. I was never able to actually use it successfully, though. When trying to connect I would always get the message from the library that it couldn't find the camera. The camera was showing up with no issue in the list of USB devices, but something was evidently going wrong (probably with my code). At that point, I realized I was quickly getting out of my depth for device driver development, so I let it go.

I then decided to try the indi_qhy_ccd driver in EkosVM and it just worked! I always thought the SSAG's ID prevented it from showing up as a QHY device (but what do I know?).

Please let me know if there's anything I can do to help, even if it is just testing new releases of the QHY libs against the SSAG.

Thank you!
Garth

Just wanted to give another example for the above mentioned issue. As far as I can tell there is no error thrown for me from the server, and the issue is present both when using the PI and when directly connecting to my laptop.

We have both the SSAG and the original QHY5 here. I can say with a large level of certainty, they are identical hardware with a different vid/pid programmed into the eeprom on board. Some years ago, I confirmed this by writing a small program for the on board fx2 chip (long since lost) that re-wrote the vid/pid eeprom on both of them, so now the QHY reported as the SSAG and vice versa, saw absolutely no difference in operation after the swap.

The have different VID/PID in uninitialised state, once firmware is uploaded (in case of linux by USB rules, not by INDI driver), SSAG and QHY5 are identical. Peter

This was what got me going down the road of testing / checking years ago. Back then, we were still using windows for our telescope kits, and the QHY5 drivers were somewhat unstable, but we found the SSAG drivers to be relatively stable in comparison. They both reported different vid/pid even after firmware load on windows, so my goal was, turn them both into SSAG, which I accomplished by using sdcc and fx2lib to write new values into the eeprom for the uninitialized vid/pid of the device.

I had been toying with the idea of reverse engineering a few of the connections inside the gadget, and writing a completely new firmware for it at the time, but, it's a lot of work for very little return. Once we got our systems stable with both of them programmed to be an SSAG, I abandoned that idea.

Maybe some day when I have more free time that I have projects, I'll re-visit the idea. ofc, the concept of having more free time than I have projects to deal with, not likely to ever happen

I had this issue in my RPi B+ and on a Ubuntu Mate PC. Have just updated the PC with the latest indi_qhy_ccd and the image is normal.
Disconnecting the device gives me a crash on the driver.
Added a Kstars log and a commented server output log.

Please try tomorrow to see if you get the same issue after the update.

It's working fine now after update. Thank you.

I updated EkosVM and it now works great! Could I ask someone to give me some guidance on updating the drivers for the Pi?

I checked out, built, and installed the 3rd party drivers off sourceforge and the problem is still there but also a little different. The strange patterns are still present, but the image now shows gradients that reflect the brightness of whatever I've turned the sensor towards.

I've attached an image of the SSAG pointed out the window with a collimation cap covering the sensor.

My Pi is an older version 1 Model B running Raspbian Jessie. Other than the speed and memory, could this generation of Pi have any issues that are hindering things?

Is there a better way for me to be updating the drivers, or a better distro to install on the Pi?

Thanks for any advice!

I'll get the Raspbian drivers updated soon, they're auto-build but they still point to the subversion and not Git. Hopefully you'll get a new version tomorrow.

After today's update of the driver I can't set the binning to 2x2, only 1x1 works:

"SetBin Mode Failed, invalid bin resquested 2x2"

Uh oh, I must remember to take snapshots of working setups as this has always worked and apparently suddenly not.