-
Where did you get the camera module(s)?
Antratek -
Model number of the product(s)?
Arducam IMX519 16MP Autofocus Camera Module for Raspberry Pi, NVIDIA Jetson -
What hardware/platform were you working on?
-
Raspberry Pi 5 with HAILO AI module
-
Instructions you have followed. (link/manual/etc.)
-
Problems you were having?
can not set focus -
The dmesg log from your hardware?
-
Troubleshooting attempts you’ve made?
-
What help do you need?
Hardware:
- Raspberry Pi 5
- Arducam IMX519 16MP Autofocus camera module
- Raspberry Pi OS (Trixie-based), rpicam-apps 1.12.0-2, kernel 6.18.39+rpt-rpi-2712 (arm64)
- Camera connected via
dtoverlay=imx519,cam0in/boot/firmware/config.txt
Problem:
The sensor is detected correctly and image capture works fine, but autofocus never engages — --lens-position has zero effect regardless of value. rpicam-still logs:
WARN IPARPI ipa_base.cpp:812 Could not set AF_MODE - no AF algorithm
WARN IPARPI ipa_base.cpp:1424 Could not set LENS_POSITION - no AF algorithm
WARN IPARPI ipa_base.cpp:1331 Could not set AF_RANGE - no focus algorithm
WARN IPARPI ipa_base.cpp:1349 Could not set AF_SPEED - no focus algorithm
sudo dmesg | grep -iE "lens|dw9|vcm|ak73" returns nothing at all — not even a failed I2C probe/attempt for a VCM device, only the sensor itself is registered:
imx519 10-001a: Device found is imx519
rp1-cfe 1f00110000.csi: Using sensor imx519 10-001a for capture
Steps already taken, no change in any case:
- Replaced the camera module with a second, separate IMX519 AF unit — identical symptoms on both.
- Replaced the CSI ribbon cable (original was pinched between a lid and enclosure) — camera detection was briefly lost after reconnecting, restored after a reboot, but AF behavior unchanged.
- Rebooted multiple times.
- Ran your official install script:
install_pivariety_pkgs.sh -p libcamera_devand-p libcamera_apps, followed by a reboot — no change,dmesgstill shows zero lens/VCM activity.
Given that two separate physical units show identical behavior, this doesn’t look like an individual hardware defect. Could you advise on the specific dtoverlay/kernel driver requirements for VCM detection on Pi 5 with this module, or let me know if this is a known compatibility issue?