We don’t have any control about what the manufacturer’s SDK are doing. For example on the QHY I get 30fps full image (1920x1080) on an USB3 port. And regarding installing, there is also a .deb package on the same folder. A double click on it should do the trick without manual intervention.
Hi procras, is it possible to send me your settings for KSTARS/EKOS for this camera. I am trying to fix the connection problem for the last 5 days now and all i can see is the prewiew image, but no video! I am on PI 4 with Astroberry. Firecapture does not work, OACapture does not work. It is possible to connect the camera to ASI Studio on my Mac, there i can see Preview Image and Video, but i don't want to use the MAC in the field, that's why i bought the PI.
oh really? does the QHY5III462C really work with firecapture with astroberry on a raspberry pi?
(becase this is the only instance on the internet i could find that this works)
And on the firecapture hp it states QHY cams only work on x86 not arm/raspy.
do you have a quick writeup on how you got it running? (no beginner description required, just the core parts)
(sry to crash into the discussion, but i'm also just deciding between the asi and qhy 462 cam, and not having it work on arm linux is a huge drawback)
Cam is on the way, I'll report back if there are problems.
Btw... I took a quick look at the Debian package... Is ther any way I can help a bit with the packaging? Some GitHub repo to submit pull requests? (I'm doing debian systems programming and packaging since 15 years)
Unfortunately there is not a public repo. Torsent handles this in a very particular way. For example, I only have access to some libraries code that is what needs to be compiled on each platform, but Torsten handles the java part (common code between all platforms).
But it could be very handy if you can help with the packages. If you want I can introduce you to Torsten, so you can propose your improvements. Because I'm pretty sure that there is a lot of improvements on the package department .
Dang, that's a bummer :/
Especially as it's java and high performance code without obfuscation is released practically as source anyway, just making it harder to help.
And as I've read Thorsten speaking about it being hard to find enough time to work on it... (Basically echoing the problem of being the sole responsible person for a project)
Ok, let's try that .
Normally I only contribute code/help anymore to projects being open about contribution, that means I expect an open development workflow with bugtracker and repository at least. (In my free time I don't want to again work on closed things, with all the warts)
In the end I not only want to propose the enhancements but provide them via PRs, because it's my way of giving back to Thorsten to help him make time free for other parts of the SW !
though it does not really work with firecapture.
It freezes after just a few seconds and then never works again until removing the camera from the system and plugging it in again.
i tried both qhyccd sdk version 21.02.01 (which seems to be the version included in firecapture 2.7beta4) and 21.03.13 (where i exchanged the libqhyccd.so to the one from the newer sdk and used the newer firmware).
in both cases firecapture only works with a fresh initialised camera, thus only the first time and there only for a few seconds before freezing.
any ideas how to debug that further?
firecapture does not show any additional log output
After a bit of debugging it seems the problems are not related to firecapture for the QHY5III462C camera:
cam freeze after a short period of time
only 30 fps
Debugging the freezing.
This helped to make it work for more than a few frames, though still breaks down after a few seconds:though, after a single stalled libusb transfer the only thing to get the camera working again is plugging it in again.
This means it's "dead"I debugged it via modifying the testapp/LiveFrameMode example from the SDK to compile on a modern linux and make it actually show more than one frame.
(I've uploaded the code for people who need it here: gist.github.com/gebi/f85de8444d81961fb432d3fa1f23ddeb )
Then set debug output to true in qhyccd.iniPartial log (full log attached)I'm at a bit of a loss here, seems really like some problem with the transfer, then the camera does not recognize the cmd and then there is the error recovering missing in the lib and possible cam firmware to get it working again
"awesome"... the forum editor seems to be broken regarding block quotes
my reply actually looked like this: *imaginary image*
(adding images in the editor is broken too, image is included as a big chunk of base64 data, but correctly displayed in editor)