Hi everyone, I’m trying to run the Arducam Serial Number Tool against some UC-684 Rev F3 cameras. Every time I launch the tool it comes back with an ‘unknown device’ message and won’t let me read or write the serial number. Has anyone run into this before? Do I need a camera-specific DLL for this model? I couldn’t find any separate files for it.
Thanks for the details. Before we go down the DLL path, can you confirm a couple of things about the environment? How are the cameras connected (USB 3.0 ports, hub, etc.) and what OS are you on? Also, does the UC-684 show up correctly in Device Manager, or does it have a yellow exclamation mark?
They’re on USB 3.0 ports on a Windows 10 machine. The camera shows up fine in Device Manager as an imaging device, no error there, but the Serial Number Tool still just says ‘unknown device’ when I start it. I’ve already tried different ports and cables, same result. I’m pretty sure the tool needs a specific DLL for the UC-684 Rev F3 but I can’t find it anywhere.
That behavior usually means the generic DLL bundled with the tool doesn’t know how to enumerate the UC-684 Rev F3. The Serial Number Tool does require a camera-specific DLL for certain models, and the UC-684 Rev F3 is one of them. Without the matching DLL/config it will keep reporting ‘unknown device’ even when Windows detects the camera fine. I’ve prepared an updated version of the tool with the correct UC-684 Rev F3 support included and sent you the download link through private message. Please check your messages, grab it, and give it a try.
Got it, thanks. I downloaded the updated tool you sent over PM, closed the old one, and ran the new build. The UC-684 Rev F3 is now recognized and I was able to read the serial number without any ‘unknown device’ error. Thank you so much for your help, it worked!
Glad to hear it’s working now. Just to summarize for anyone else hitting this: the stock Serial Number Tool needs the camera-specific DLL for the UC-684 Rev F3. If you see ‘unknown device’ while the camera itself shows up fine in Device Manager, that missing model-specific DLL is the likely cause. The updated tool with that model’s support is available on request, and I’ve sent it to you via private message. Let us know if anything else comes up.