Having an issue with some B0506 cameras we’ve deployed. We’re using them with 3m USB cables (not the stock 1m ones they came with). We’ve got just under 40 units out there, and about 7 of them are showing intermittent problems — the video feed either freezes completely or the screen goes black/grey for a while, then sometimes comes back.
What’s weird is the cameras are always detected fine on startup. They show up in Windows Camera app, ArduCam Camera software, and our own monitoring software without any issues. It’s only after running for a while that the feed starts degrading. Not all units do it — maybe 17-18% of them. The rest are solid.
Thanks for the detailed report. Based on what you’re describing, my first suspicion is the 3m USB cable. The B0506 ships with a 1m cable for a reason — we’ve seen a lot of customers run into similar intermittent freeze and signal loss issues when they switch to longer cables, especially beyond the stock length.
Before we dig further — could you take a handful of the affected cameras and test them with the original 1m cable that came in the box? Just run them for a while and see if the freezing / black screen issue goes away. That’ll help us narrow down whether the cable length is really the culprit here.
Honestly, I’m a bit skeptical that the 3m cable is the whole story. We’ve run USB3 cameras with cables longer than 3m in other setups and never had this kind of problem. I get that longer cables introduce signal integrity concerns, but 3m isn’t exactly extreme. Is there anything that can be done to improve reliability with the 3m cables we’re already using? Because if we can’t make this work reliably, our end customer is going to start looking at alternate camera hardware.
That’s a fair point — 3m USB3 shouldn’t be crazy long, and I understand the frustration, especially since the majority of your units are running fine at that length. Could you grab some screenshots or photos of what the failure looks like when it happens? Specifically the black screen, the grey screen, and if possible what the frozen frame looks like. That’ll give our engineering team something concrete to work with while they look into this.
We’re actively investigating this on our side. The fact that it’s not all units — just a subset — could point to slight variances in the camera hardware, the cable quality itself, or even the host USB controller. We’ll circle back as soon as we have something. In the meantime, if you’re able to run that 1m cable test on a couple of the problem units, that data point would be really valuable for the investigation.
Alright, I’ll try to grab some captures next time one of the affected units acts up. Might take a day or two since the failures are intermittent. Haven’t had a chance to do the 1m cable swap test yet — the problem cameras are in a production environment so I can’t just pull them on a whim. I’ll update when I have something.
No rush, take your time. We’re continuing to investigate on our end whether there’s anything we can do on the firmware or driver side to improve tolerance for longer cable runs. Once you have those screenshots and the 1m cable test results, that should help us zero in on the root cause. We’ll post back here as soon as we have findings to share.