Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
Search
RPi5 with QHY533C
I'm running FireCapture v2.7.14 on a RPi 5 with 8G and NVMe SSD. I have a QHY533C and a ZWO ASI120MM Mini cameras. The RPi 5 is running Bookworm.
When I use FC with the 120MM, it seems to work fine. With the QHY, it seems to struggle. I've been playing with the settings to try and optimize (reading through some of the posts here). With the QHY, if I set it to bin x2 the preview looks ok (although debayer is not allowed). I do see that 1 core of the RPi is pegged at 100%, even when using 1 FPS. With the 120MM, the CPU usage is much lower on all cores. I realize the QHY has a lot more data to retrieve. If I uncheck the FPS control so the FPS goes up to 10, the % usage on that core goes down slightly to 96% - 98%. Maybe not really an issue, but seems odd. Just something that I noticed based on my years as a RTOS and Linux kernel developer. I'm using Kstars/ekos/PHD2 on the RPi to control my mount and cameras, I am intending on using FC to give me a live view for doing manual focusing, then go back to Kstars for the data collection. Would I be better to use indi server with FC, or leave it directly connecting to the camera like I am using it now? This post is part introduction, and part looking for suggestions to tweak FC for better performance. Thanks! Pete Kockritz |
It actually is, or sounds like it. I'll have to do some reading-upping to catch up on this one.
toggle quoted message
Show quoted text
On 5/25/24 12:50, PeteKz wrote:
I actually meant to post this in a different group. I guess it is somewhat on topic here. |
to navigate to use esc to dismiss