Hi everyone, I’m running into a weird sharpness consistency problem with the B0560 USB cameras and hoping someone can help.
We ordered 12 identical B0560 units. 7 of them are working great — nice and sharp. But 5 of them can’t resolve fine detail no matter what I do with focus or resolution settings. I’m saving images as 3840x2160 JPGs, using manual focus, lenses are freshly cleaned, all other settings at default.
Same subject, same settings, same lighting — one camera gives me a crisp image, the other has this obvious blur/aberration. It’s not subtle. I’ve attached comparison shots from two different units so you can see what I mean.
Any ideas what could cause this kind of unit-to-unit variation?
Bumping this — really need to get to the bottom of it ASAP. We’re waiting to order more cameras but can’t proceed until we understand what’s going on with these 5 bad units. Any support folks around?
Thanks for the detailed report and the comparison images — the difference in sharpness between those two units is pretty obvious and definitely not within what we’d consider acceptable variation.
From what you’re describing — 12 identical B0560 cameras, 7 sharp and 5 soft despite same settings, manual focus, clean lenses — this lines up with a pattern we’ve seen before: slight variation in lens focus calibration during manufacturing. With fixed-focus / manual-focus modules like the B0560, even minor calibration drift on the production line can cause noticeable sharpness differences unit-to-unit.
I’ve forwarded this to our QA team for an internal review of the production batch. They’ll dig into it and I should have a concrete plan for you within three business days. Sit tight.
Quick update — QA finished their investigation and they’ve surfaced something interesting that changes the picture a bit.
It turns out our engineering team recently released a firmware update that refines the camera’s auto-focus algorithm. The batch of 12 cameras you received may actually contain a mix of units running the older firmware and units with the newer firmware. That firmware-level difference can produce visible sharpness and aberration differences — even when you’re using manual focus, which surprised me too, but apparently the AF algorithm interacts with the image pipeline in ways that affect the final output regardless of focus mode.
So here’s what we can do — two paths:
If you can share your order number, we can trace the manufacturing and shipping data to confirm which firmware each unit should have.
Alternatively, you can copy the firmware from one of your perfectly sharp cameras and flash it onto the underperforming ones. That would bring all 12 units to the same firmware and performance level.
I’ve put together a video guide showing the firmware copying process — I’ll send that over to you via private message. Let me know which path you’d prefer.
First, I can’t access the video guide you shared — my company’s network blocks external cloud storage links (Google Drive etc.). Is there any way you can email the file directly, or use a method that doesn’t involve cloud storage?
Second, regarding the order — we purchased through a distributor (order placed October 7th) rather than directly. Not sure if that affects your ability to trace things on your end. Happy to provide whatever details you need.
No problem on the access issue — I’ve uploaded the firmware update tool and video guide to a couple of different locations so you have options. I’ve also sent you the package directly via private message, so check your inbox here on the forum.
In the meantime, there’s one more thing that would really help us narrow this down: could you take a photo of the lot code printed on the front of the camera packaging? That’ll let us trace exactly which manufacturing batch these came from and confirm the firmware situation definitively.
Alright, I flashed the firmware onto the faulty B0560 cameras. Unfortunately things didn’t improve — if anything, the image quality after flashing looks slightly worse than before. There’s a bit more haze in the post-flash images. This is consistent across all the faulty units I tested.
The good cameras still produce noticeably sharper images than anything I’m getting from the faulty ones, whether pre-flash or post-flash.
Also, I should mention — we already discarded the packaging, so I can’t get you the lot code. Sorry about that.
Here’s a comparison — old firmware vs new firmware on one of the faulty units:
Thanks for testing and sharing those comparison shots. The fact that the copied firmware actually made things worse — more haze rather than less — tells me the first approach wasn’t the right one. It’s possible the firmware you copied from the good unit isn’t the correct variant, or the copy process introduced something unexpected. This also makes me think the root issue isn’t purely firmware-version-related in the way we initially suspected.
Our engineering team has provided a different firmware binary — not a copy from another camera, but a fresh build specifically meant to address this sharpness problem. I’ve sent the file to you via private message. Give this one a try on one of the faulty units and let me know if you see any improvement. Fingers crossed.
That did it! Flashed the new firmware onto all the faulty B0560 cameras and the sharpness issue is completely resolved. All 12 units are now producing consistent, sharp images. Really appreciate the persistence on this.
On a related note — we’ve just placed an order for the B0561 model (looking for the increased resolution). Should I be worried about running into a similar sharpness issue with those? Is there a firmware update available for the B0561 as well, just in case?
Great to hear the new firmware sorted out all the B0560 units! Confirmed: that firmware binary is the definitive fix for the B0560 sharpness problem.
As for the B0561 — you shouldn’t need to worry about the same issue at all. The B0561 uses an autofocus mechanism, so it’s inherently immune to the fixed-focus calibration variation that caused all the trouble on the B0560. The AF system actively adjusts the lens position, so there’s no static calibration that can drift unit-to-unit. No special firmware needed for sharpness concerns on that model.
So the B0561 cameras arrived and I’m hitting a completely different set of problems now. Two issues:
Issue 1 — Corrupt JPEG data: I’m getting this error repeatedly: Corrupt JPEG data: premature end of data segment. I’m only opening and closing one camera at a time, so USB bandwidth shouldn’t be the bottleneck. I’ve tried reseating all the cables — didn’t help. And it’s not all cameras — only some of them are affected.
Issue 2 — Camera index shifting: The camera indices have mysteriously changed on me. Previously the indices were 0, 2, 4, etc. Now index 0 doesn’t work at all and everything has shifted — the new indices are 1, 2, 4, etc. I haven’t changed anything in my code or connection setup.
Environment: Multiple B0561 cameras connected through active USB extension cables to a single USB hub.
Interesting — I haven’t seen this particular combination of issues reported before, so this is new territory. Both symptoms — the corrupt JPEG data errors and the index shifting — point toward something going on at the USB communication level rather than a camera firmware or optics problem.
My strongest suspicion right now: the active USB extension cables. Active cables have their own repeater/re-timer circuitry, and when you’ve got multiple cameras running through them into a single hub, signal integrity can get unpredictable. Corrupt JPEG data (premature end of data segment) is exactly the kind of error you’d see from dropped packets or data truncation over an unreliable USB link. And the index shifting — where index 0 disappears and everything renumbers — that smells like enumeration weirdness, which can also be triggered by marginal signal quality during device detection.
Before we dig deeper into other possibilities, can you try this: disconnect the extension cables entirely and plug the B0561 cameras directly into the hub (or directly into the host) using just their original USB cables. Let me know if both issues disappear. That’ll tell us right away whether the active extensions are the culprit.
Also, could you share the exact make and model of the active USB extension cables you’re using? I’d like to try to reproduce this setup in our lab.
