Arducam 8MP IMX219 USB camera recognized but no image in Windows

Having an issue with an Arducam 8MP IMX219 Auto-focus USB Camera, model B029201 (the one with the case). We ordered 11 units total — 10 work perfectly, but this one unit shows up in Windows Device Manager as “USB Camera” but produces no video or image at all. The device is recognized and shows up fine in Device Manager, but any app I try just gets a black screen or no feed. The reseller also tested it and confirmed it’s faulty before forwarding it to us. Anyone seen this before?

Thanks for reaching out. Since the camera is showing up in Device Manager, the USB enumeration is working and the system is at least partially recognizing the device. That’s a good start. A couple of questions to help narrow this down:

  1. Which software are you using to preview the camera feed?
  2. Does the software actually list or detect the camera by name, or does it not appear in the device selection at all?
  3. When you say “no image,” can you describe exactly what you see? Is it a black window, an error message, a frozen frame, or does the preview window not open at all?

I’ve tried the default Windows Camera app and also AMCap. In both cases, the camera appears in the device dropdown as “USB Camera” and I can select it, but the preview window just stays completely black. No error messages pop up. It behaves like it’s connected and selected but the sensor just isn’t sending any frames. I also tested with VLC (DirectShow capture) — same result, black screen, no frames. On the working units, the same software shows video immediately.

That’s helpful. Since the 10 other identical units work fine with the same software and setup, we can pretty much rule out a driver or software configuration issue on your end. A few more things to try before we go further:

  • Have you tried different USB ports (preferably a rear port directly on the motherboard, not a hub)?
  • Can you check in a tool like USBTreeView whether the camera is enumerating with the correct USB descriptors (VID/PID)? For the B029201 it should typically show up as a UVC device.
  • Does the camera’s LED (if it has one) light up at all when plugged in?

If none of those reveal anything, the next step would be a remote session so we can take a closer look.

Tried all of that — different USB ports (2.0 and 3.0, direct on motherboard), different cables swapped from the working units, and checked with USBTreeView. It enumerates as a standard UVC device, same VID/PID as the working cameras. The LED does come on when plugged in, so power seems fine. Just no frames ever come through. At this point I’m pretty confident it’s a hardware fault with the image sensor or the onboard ISP, since USB communication itself is working. The other 10 units are all running flawlessly in the same environment.

Based on everything you’ve described — correct enumeration, UVC descriptors matching the working units, LED active, but zero frame output across multiple host applications — that does point strongly toward a hardware-level fault on the sensor side or the ISP pipeline on the camera itself. Since the USB bridge is alive and the host sees a valid UVC device, the issue is likely downstream of that.

I’d like to do a live remote diagnostic session to confirm before we proceed further. I’ve sent you the remote access details via private message — please check your messages and we can set up a time that works. This way I can verify the USB descriptors, UVC stream negotiation, and see if any frames are making it through at the driver level.

Quick update for anyone following this thread: we received the unit back and our R&D team has completed the inspection. They’ve confirmed the camera is indeed defective — hardware fault on the imaging side. The USB bridge and enumeration are fine (which matches what we saw), but the sensor module itself has failed.

We’re arranging a replacement unit. For anyone encountering similar symptoms (device recognized, LED on, but permanent black frames across all software), this seems to be a rare hardware defect rather than a driver or compatibility issue.