Missing configuration file error when running Arducam Python SDK examples with 12MP A708 USB2 UVC camera on Windows 11

Hey everyone, I’m trying to get my Arducam 12MP A708 USB2 UVC Camera Module (model B0304-1) working with the Arducam Python SDK on Windows 11, but I keep hitting a wall.

Whenever I try to run the example scripts (async.py or sync.py) from the ArducamEvkSDK (version 1.0.8), I get an error about a missing configuration file. There’s no .cfg file for my camera model anywhere in the SDK folder.

My setup:

  • Camera: Arducam 12MP A708 USB2 UVC Camera Module B0304-1
  • OS: Windows 11
  • Python: 3.10.10
  • IDE: Visual Studio Code
  • SDK: ArducamEvkSDK v1.0.8

Has anyone managed to use this SDK with a UVC camera module? I followed the docs but they all seem to assume an evaluation kit. Am I missing something obvious here?

Welcome to the forum! The issue you’re running into is actually pretty common, and I know it can be confusing.

The short answer: the Arducam Python SDK (ArducamEvkSDK) is designed specifically for the Evaluation Kit (EK) series cameras. It won’t work with UVC camera modules like your B0304-1 — they use completely different software interfaces under the hood. That missing config file error is basically the SDK telling you it doesn’t know how to talk to your device.

For UVC cameras, the recommended approach is to use OpenCV with GStreamer, which treats the camera as a standard UVC device. Here are the official guides:

Try those out and you should be able to capture video without any special SDK or config files. Let us know how it goes!

Thanks for the quick reply! I followed the Windows guide and I can now access the camera through OpenCV as a standard webcam — that part is working great now.

But here’s the thing: for my R&D project I actually need autofocus functionality, and I only realized after purchasing that the B0304-1 is the fixed-focus version. USB Type-C and UVC compatibility are non-negotiable for my application though.

I noticed the B0304-1 has two boards connected by a 15-22 pin FFC ribbon cable — a bottom USB UVC converter board and a top camera sensor board. So my question is: can I simply swap the top camera board with an autofocus version, like the 12MP IMX708 autofocus module from the Raspberry Pi lineup (https://www.arducam.com/arducam-12mp-imx708-autofocus-camera-module-with-hdr-pdaf-for-raspberry-pi.html), while keeping the existing FPC cable and UVC converter board?

And out of curiosity — would the same approach work with the newer 64MP autofocus module (https://www.arducam.com/64mp-af-for-raspberry-pi.html)?

If swapping isn’t possible, are there any manually adjustable focus lenses I can attach to the B0304-1 instead?

Good to hear OpenCV is working! As for the hardware swap idea — unfortunately, that won’t work. Here’s why:

The bottleneck is not the camera sensor board or the FPC cable (which is physically standard), it’s the UVC converter board firmware. The converter board that came with your B0304-1 fixed-focus kit is specifically designed and programmed to stream video from a fixed-focus sensor. It doesn’t have the firmware routines or the control circuitry needed to drive a Voice Coil Motor (VCM) for autofocus. So even if you physically attached an autofocus camera board, the converter board simply wouldn’t know how to move the lens.

This same limitation applies across the board — the 64MP autofocus module would have the exact same problem with that converter board. The UVC board is not a universal interface; fixed-focus and autofocus variants have different firmware and are not interchangeable.

The correct product for what you need is the B030401 (Upgraded) kit, which pairs an autofocus-capable IMX708 camera board with the proper UVC converter board that’s been designed from the ground up to handle autofocus commands over USB/UVC:

And regarding your last question — no, we don’t offer separately sold manually adjustable focus lenses for the B0304-1 fixed-focus module.

Thanks for the detailed explanation — that makes a lot of sense about the firmware being the limiting factor. I’ll look into the B030401 upgraded kit.

Before I pull the trigger though, I need to be really sure about one thing: how does the autofocus actually behave on the B030401? For my research application, I need full-time continuous autofocus — the kind that constantly monitors the scene and adjusts focus on the fly as objects move or the scene changes. I can’t work with something that only focuses once on startup, or only when I manually trigger it.

Is the B030401 continuous autofocus (CAF), or is it more of an on-demand / one-shot type? Here’s a picture of the module I’m looking at:

B030401

Yes, the B030401 (Upgraded) module supports full-time Continuous Autofocus (CAF) out of the box — that’s actually the default mode of operation.

In CAF mode, the camera’s firmware continuously analyzes the scene. Whenever it detects a change in object distance or scene composition, it automatically adjusts the lens position to maintain sharp focus, with no user intervention required. You don’t need to trigger it programmatically or manually — it just works.

For testing and verifying the focus behavior, you can use tools like Amcap or Potplayer — they’ll let you observe the autofocus in action and play with focus control functions.

When you’re ready to integrate it into your research application, you can access focus control through standard libraries like OpenCV. Since the camera presents itself as a standard UVC device, all the usual UVC control interfaces apply.

Given your requirements for dynamic, real-time focus adjustment, the B030401 should be a good fit.