Crescent halo in frame rotates with camera – Arducam B0305 Linux

Hi everyone, I’m having a strange issue with my Arducam B0305 on a Linux setup (Raspberry Pi). There’s a crescent-shaped halo/glare artifact appearing right in the center of the frame. It’s pretty noticeable and ruining my shots.

Here’s what I’ve tried so far:

  • Cleaned the camera body and lens thoroughly
  • Removed the protective sticker from the lens (thought maybe that was it)
  • Adjusted lighting conditions in the room
  • Tested a different camera in the exact same position — no halo on that one
  • Rotated the camera itself — and the halo rotates with it, so it’s definitely something with this specific unit/optics

Here’s a sample image showing what I’m talking about:

TrN0vfSiv1qcrZFV.png

Anyone seen anything like this before? Could it be an internal reflection or some kind of sensor issue?

Thanks for the detailed report and the sample image — that helps a lot.

Before we go further down the hardware path, I have one diagnostic question: does the crescent halo persist when the camera is NOT under a direct light source? For example, if you take a shot in a dimmer environment or cover the light source, do you still see the same artifact? This will help rule out external reflections versus something internal to the module.

Good suggestion. I just tested it — changed up the light sources completely (moved to a different room, tried both natural window light and a desk lamp at different angles). The crescent halo is still there in every shot, regardless of the lighting setup.

Here’s another sample from the latest test:

TrN0vfSiv1qcrZFV.png

It really seems like it’s baked into the image regardless of what I do externally. Pretty frustrating.

Thanks for confirming that — the fact that the halo rotates with the camera and persists across different lighting conditions does point toward something internal to the module, likely an optical reflection between the lens elements or an issue with the IR filter/glass on the sensor.

At this stage, I think the most efficient path forward is to do a live diagnostic session so I can see the behavior in real time and check a few things on your setup directly. I’ve sent you the remote support instructions and scheduling details via private message — please take a look when you get a chance. It’ll involve installing a lightweight remote access tool on your Pi and booking a time slot that works for you. Once we connect, we can dig deeper and figure out whether this is a configuration quirk or a hardware-level problem.