Hi everyone, I recently bought two Arducam cameras (models B0322 and B0385) and I’m running into a weird issue. B0322 isn’t recognized at all when I use its own USB cable - it fails immediately. Here’s the strange part: B0385 was working perfectly with its own cable, but after I tried B0322’s cable with B0385, now neither camera gets recognized anymore. B0385 was fine before that cable swap. Has anyone seen anything like this before?
Thanks for reaching out. Could you let me know which operating system(s) you’re testing on, and if you can grab any error messages or logs when the cameras fail to show up? That’ll help us narrow this down.
Sure. I’ve tested on both Linux and Windows. On Linux it throws an error right away - I’ve attached a screenshot, though the text isn’t easily extractable. On Windows I get Error Code 43 in Device Manager. Here’s what I’ve tried so far: B0322 with its own cable → fails immediately on both Linux and Windows. Then I used that same B0322 cable with B0385 (which previously worked with its own cable) → no camera detected. I’ve also filled in the technical support forms for each camera.
Thanks, that’s very helpful. Let me summarize what I’m seeing so far: B0385 worked fine with its own cable, but when you used B0322’s cable with B0385 it failed. That points pretty strongly at the B0322 cable being faulty. The next step is to figure out whether B0322 itself still has problems after we swap the cables around. Can you try B0322 with B0385’s original (known-good) cable? If B0322 comes up, the cable is the culprit. If it still fails, then we’re looking at the module itself. We also need to confirm whether B0385 still works with its own cable, since it stopped being detected after the cross-test.
Quick update - one of my colleagues (an R&D robotics engineer) is going to take over the technical side. He gave me the exact sequence he ran, all on Windows using the Windows exe: 1) Received B0385 and B0322 separately. 2) Plugged in B0385 with its own cable → the Windows exe worked perfectly. 3) Plugged in B0322 with its own cable → no device found. 4) Tried reading B0385 video using B0322’s cable → no device found. 5) Plugged B0385 back in with its own cable → still no device found.
Thanks for the detailed reproduction sequence, that really helps. Sorry you’re having this trouble. Right now the root cause isn’t pinned down yet - the fact that B0385 worked initially and then stopped being detected even with its own cable means we need to inspect the physical connectors and cables. Could you send over photos of both camera boards’ connectors and the two cables? Close-ups of the connector pins would be ideal. Once we can see the hardware, we’ll be able to tell whether this is a cable issue or something on the module side. In the meantime, please still try B0322 with the known-good B0385 cable so we can isolate cable vs module - that’s the key test for now.