I’ve got four UCTRONICS B0447 UVC cameras hooked up to a Windows 10 machine. I was using the serial number modification tool to give each camera its own serial number. It worked on three of them, but the fourth one failed partway through. Now the tool doesn’t detect any cameras at all, and USBView shows the affected camera is failing enumeration. I’ve tried different USB ports and even different machines - same result every time. Anyone else run into this?
Thanks for the details. Before we dig further, can you check if the problem camera shows a preview in AMCap (Amcap.exe)? That will tell us whether the device is completely dead at the USB level or just not visible to the serial tool. If AMCap can’t see it either, we’re likely looking at a corrupted descriptor from the failed serial write.
I ran AMCap and got “Sorry, you have no video capture hardware.” So it’s not being seen at all. I suspect the write of the device name and serial number failed during the modification and left it half-written. Here’s what USBView shows for that port:
[Port3] FailedEnumeration : USB Composite Device
Is Port User Connectable: yes
Is Port Debug Capable: no
Companion Port Number: 0
Companion Hub Symbolic Link Name:
Protocols Supported:
USB 1.1: yes
USB 2.0: yes
USB 3.0: no
Device Information:
Device Bus Speed: High (is not SuperSpeed or higher capable)
Device Address: 0x11
Open Pipes: 0
*!*ERROR: No open pipes!
Device Descriptor:
bLength: 0x12
bDescriptorType: 0x01
bcdUSB: 0x0201
bDeviceClass: 0xEF
*!*ERROR: Device enumeration failure
Is there any way to reset it or force a write of the device name and serial number?
That log confirms the camera isn’t enumerating - no open pipes and the descriptor is failing. A failed serial number write has most likely left it in a state where Windows can’t enumerate it, so the serial tool (and AMCap) won’t see it either. The recovery path here is to reflash the firmware on that camera. I’ve sent you the CommonBurner_B0447.7z package through private message - it contains the burner tool and a guide video. Please check your messages, and only flash the affected camera, not the three working ones.
Thanks, I grabbed the package and ran CommonBurnerAP v1.0.1.8.exe, but it throws “Can’t find video device.” So the burner can’t see the camera either. Is the source code for CommonBurnerAP available anywhere? If I could disable that device check, maybe I could force the firmware update to run anyway.
That’s actually useful info. Before we try anything more aggressive, can you run CommonBurnerAP v1.0.1.8.exe with one of the three cameras that ARE working normally? Just to see if the tool recognizes them. Important: do NOT actually burn firmware on those working cameras - we only need to know if they show up in the tool. That will tell us whether the problem is specific to the broken camera or if the tool itself isn’t detecting anything.
I tried all three working cameras with CommonBurnerAP v1.0.1.8.exe - every single one of them returns “Can’t find video device.” So it’s not just the broken camera; the tool doesn’t seem to recognize any B0447 at all.
That rules out a fault with your particular cameras - the v1.0.1.8 tool simply doesn’t recognize these devices. I’ve sent you an updated CommonBurner_B0447.7z package through private message with a newer burner tool. Please use that one to flash the firmware, and again, only burn the camera that isn’t working. Current status: the failed serial write left the camera non-enumerable, the previous burner tool couldn’t detect any device (even the working ones), so we’ve switched to the updated tool to attempt the recovery flash.