I'm working on a system with multiple Raspberry PI 5s with a combination of Arducam (Hawkeye and Owlsight) and some IMX477 cameras.
I realise that the Hawkeye has it's own Adrucam drivers, but I think this issue is unrelated to those specific drivers, it seems to be more OS 'kernel' related.
When I first started working with the Hawkeyes, they were slow to focus, but gave good results (most of the time), however more recently, after installing the new Trixie OS (and also on later versions of Bookworm) the focus is now really fast, maybe around 1.5-2 seconds to fully focus, but it's not accurate at all, and I have to tweak the LensPosition by 0.2 - 0.3 dioptres.
A test I've done...
On a PI with Trixie 6.18.29 OS Kernel and Hawkeye 64mp camera
This returns very quickly with this..
So after about 10 frames, it locks the focus.
So I reverted the kernel to 6.12.47 (which seems to be the last good kernel)
Rebooted the PI, and ran the rpicam command again, and it then shows..
Which is much more like the original scan speed, so, this kernel downgrade has resolved the focus issue. (I'm not sure if this is the difference between CDAF and the much hyped PDAF?)
I'm not keen on downgrading the kernel on multiple PIs, especially is I'm guessing it could be easily overwritten with another update, and might mess up other stuff (I've not fully tested it)
Is this is a known issue? are there any better ways to resolve this?
I realise that the Hawkeye has it's own Adrucam drivers, but I think this issue is unrelated to those specific drivers, it seems to be more OS 'kernel' related.
When I first started working with the Hawkeyes, they were slow to focus, but gave good results (most of the time), however more recently, after installing the new Trixie OS (and also on later versions of Bookworm) the focus is now really fast, maybe around 1.5-2 seconds to fully focus, but it's not accurate at all, and I have to tweak the LensPosition by 0.2 - 0.3 dioptres.
A test I've done...
On a PI with Trixie 6.18.29 OS Kernel and Hawkeye 64mp camera
Code:
rpicam-still -t 4000 --width=9152 --height=6944 --nopreview --autofocus-mode=auto --info-text "%focus %lp %afstate"Code:
267.00 3.03 scanning272.00 4.01 scanning302.00 4.90 scanning611.00 5.43 scanning831.00 5.74 scanning1213.00 5.92 scanning1701.00 6.02 scanning2032.00 6.02 scanning2094.00 6.02 scanning2093.00 6.02 focusedSo I reverted the kernel to 6.12.47 (which seems to be the last good kernel)
Rebooted the PI, and ran the rpicam command again, and it then shows..
Code:
262.00 1.00 scanning261.00 1.00 scanning421.00 1.00 scanning420.00 1.00 scanning419.00 0.00 scanning418.00 0.00 scanning430.00 0.00 scanning430.00 0.00 scanning431.00 0.00 scanning430.00 1.00 scanning431.00 1.00 scanning430.00 1.00 scanning430.00 1.00 scanning431.00 1.00 scanning431.00 2.00 scanning432.00 2.00 scanning431.00 2.00 scanningetc..I'm not keen on downgrading the kernel on multiple PIs, especially is I'm guessing it could be easily overwritten with another update, and might mess up other stuff (I've not fully tested it)
Is this is a known issue? are there any better ways to resolve this?
Statistics: Posted by richierichie321 — Fri Jun 05, 2026 10:50 pm
