Ben I know this is a long time after your comment but I'm wondering if you are still interested in providing assistance in working through the process of sorting a driver of the Orion G3? I've worked through the steps to get the drivers loaded on a Win 10 VirtualBox on a Ubuntu PC. I've managed to fire up the Orion Camera Studio and get different useless images out of the camera by exposing it to different light levels.
The device details is lsusb didn't change other than an incrementing Device no each time it's plugged back in.
Bus 002 Device 021: ID 07ee:0502 Torex Retail (formerly Logware) I tried sometime back to do the wireshark thing but was trying to do it all on windows. I'll revist that on Linux and see what I can capture.
I have just aquired an Orion StarShoot G3 color CCD camera and been using astroberry so would like an Indi driver for it. I have done some C/C++ embedded coding in the past and can get assistance from my son who runs a small business specialising in embedded software development. Can I help with this?
Hi Jasem. I am using Astroberry. Plugged the Starshoot G3 color it into an available USB slot but Indi reported it could not find it? I am selecting the starshootG listed under Orion cameras. Its not listed exactly as a Starshoot G3 color. I know there is a mono version and read somewhere there's an older model of a Starshoot camera so assumed this particular model wasn't supported. Attached is the logfile. Is there anything else I can log or test? Regards David
I've not seen anybody ever report that they were successful in using the StarShoot G3 camera with INDI. I strongly suspect that the starshootg driver doesn't support this camera and actually supports the older StarShoot cameras (like the V2). The udev rules associated with the starshootg driver show a vendor ID that doesn't match the vendor ID of the G3. That's not conclusive, but would support the idea. In any case, this is the problem with these closed-source libraries...we don't really know what they are supposed to support.
About a year ago Bob Stephens and I set out to reverse engineer the Starshoot G3 and write an INDI driver for it. It kind of fizzled once we found out about the starshootg driver. However, like you, Bob was not able to get the starshootg driver to work...which would make sense if the G3 wasn't actually supported.
If you are interested, we could pick back up on the work that we already started. We had reverse engineered enough of the protocol and have a driver hacked together, but it seems to crash when attempting a capture. I don't actually have a G3 camera, but am happy to help where I can. If this sounds appealing, maybe you could resume the following thread: indilib.org/forum/ccds-dslrs/7276-orion-...-g3-ccd.html?start=0
One minor clarification... I looked at the starshootg driver and it's for the current generation of Orion StarShoot cameras (like the G26, G10, Mini). These are, of course, just rebranded Touptek cameras.
Hi Ben. I failed to mention, but this does explain why after failing to start the driver a confusing second message is generated saying something like unable to find a Touptek device. I guess a common driver is used for several camera types and the specific camera type is not passed to the code where the failure is handled? This problem also crashes Indi and not handled gracefully. When selecting the camera it just says Starshoot G. As G3 is not supported it would be better if supported camera types was more specific.
Anyway question is, is it worth finishing off the Orion G3 development or just go and buy a ZWO?
This is another topic but does affect the decision to develop a G3 driver. I have not used the Ekos FITS viewer with a colour camera. I suspect the G3 may have an unusual Bayer Matrix only because to capture a colour image I haven't found any imaging software that can convert the RAW image correctly apart from Orion Camera Studio. I thick the raw image may be YCbCr but read reports CMYG, 4 x 4 and an offset of 0,4 works. Not got to the bottom of this yet.
In support of Indi and Astroberry I am willing to help finish off the development.
David, if you really want a camera that "just works" in the near future, you might consider buying a camera that's known to work with INDI. That said, it sounds like a few of us would be willing to try and get the G3 going. That might take a day, a week, or a month. My guess is a week is close, but my crystal ball isn't perfect. Even if you get another camera, I'm interested in getting the G3 working just so that other users can benefit.
Hi Ben. OK I am in. I am prepared to do some practical work like coding if that helps. I would be interested in getting a detailed look at Indi driver writing anyway. I can do some testing as well. I guess this will involve serial port sniffing to work out the comms. protocols.