Hi all, hoping someone here can help me figure this out. I’m running a Raspberry Pi 4 with an Arducam V2 camera (model B0186). On its own it works, though honestly it’s a bit unstable and only works intermittently. The real problem is the moment I add an extension cable into the setup I get a lot of distortion in the video feed — and I mean 100% of the time. If I remove the extension the distortion goes away 100% of the time, so the extension is definitely the culprit. I’ve tested this on multiple cameras and tried 5 different extension cables, all with the exact same result. Did I get a batch of bad cables, or is this kind of distortion just normal with this product? Any help appreciated.
Thanks for the very clear description — that’s actually a helpful symptom to work with. Distortion that appears exactly when the extension is in and disappears exactly when it’s out usually points at the CSI connection/signal path rather than the camera itself.
A couple of things that would help me narrow it down:
- Can you share a short video or at least a still frame of the distortion? I want to see the pattern — is it tearing, horizontal lines, color noise/snow, or a rolling bar?
- What extension cables are you using? Length, and whether they’re the 15-pin or 22-pin type?
- How long is the total cable run (camera to Pi)?
- What software/OS are you capturing with — raspistill/raspivid or libcamera, and what resolution/framerate?
Ok, here’s a clip I grabbed showing the distortion: [video attachment]. It looks like horizontal tearing and some color rolling bars, especially in the darker areas.
The cables are generic ones I picked up — I don’t have exact part numbers. They range from about 30cm up to 1m. I’m not sure if they’re 15-pin or 22-pin to be honest, they just say Raspberry Pi camera extension. Total run is camera → extension → Pi 4 board.
Software is just the standard camera tool on Raspberry Pi OS, I think raspistill/raspivid. Default resolution mostly.
Also should’ve mentioned — I’ve already tried reseating all the ribbon connectors and flipping them, and even the shortest 30cm cable still shows the distortion, though it seems slightly less than the longer ones. So it’s not a single flaky cable.
Good, that clip helps a lot — tearing plus rolling color bars is very typical of the CSI signal getting degraded over an extra connector/cable, not a sensor fault.
A few things I’d like you to try so we can separate the cable from everything else:
-
Run the camera with NO extension (camera ribbon straight into the Pi) at the same resolution and confirm it’s clean — you already did this but let’s lock it in as our baseline.
-
With the extension in, drop the resolution and framerate significantly (e.g. 640x480 @ 15fps) and see if the distortion reduces or changes. Lower data rate puts less stress on the CSI link.
-
Check the kernel log for camera/CSI errors after a bad capture:
dmesg | grep -i -E “csi|unicam|bcm2835”
-
Confirm which physical camera port on the Pi 4 you’re using (CAM0 vs CAM1) and try the other one if possible.
Can you report back what the low-res test looks like and paste anything interesting from dmesg?
Did the baseline again without the extension — totally clean, no tearing at all. Then plugged the extension back in.
At low res (640x480 @ 15fps) the distortion is much less noticeable, but it’s still there if I look closely — maybe a thin tear every few seconds. At full res it’s back to being obvious.
Ran dmesg after a bad capture. Nothing screaming, no obvious CSI errors. Just the normal bcm2835 / unicam messages on boot. I can paste the whole thing if you want but I didn’t see anything that looked like an error.
Tried swapping CAM0 and CAM1 on the Pi 4 too — same distortion with the extension on both ports. And like I said earlier, this reproduces across multiple cameras, so it really seems tied to adding the extension at all, regardless of which camera or port.
That’s a really useful result — cleaner at low res, worse at full res, and it follows the extension across ports and cameras. That pattern is the signature of a signal-integrity problem on the CSI bus rather than anything wrong with the camera sensor or the Pi itself.
The Raspberry Pi CSI link isn’t designed to tolerate long or unshielded extensions well. Adding an extra cable + connector degrades the differential signalling, and the faster you clock the data (higher res/framerate) the worse it gets — which matches exactly what you’re seeing. Cheap/generic extension ribbons are especially prone to this because they’re often not impedance-matched or shielded the way the official ones are.
So to summarize where we are:
- Camera alone on the Pi: works (though you noted it’s a bit intermittent/unstable on its own).
- Any of your 5 extension cables in the path: distortion, 100% of the time.
- Lower data rate reduces but doesn’t eliminate it.
- Reproduced across multiple cameras and both CSI ports.
We haven’t found a fix that makes your current generic extensions work cleanly, and I don’t want to promise one — this looks like a limitation of the extension cables themselves rather than a defective unit. Can you tell me the exact model/length of at least one or two of your extension cables? If any of them are the official Arducam extension type (designed for the Pi CSI bus), that’s worth testing specifically, and if you can source a short shielded one I’d like to see whether it behaves differently. In the meantime, if your setup allows it, running the camera without the extension is the only combination we’ve confirmed is clean.