We’ve got an Arducam UB0240 on a Jetson Orin NX 16GB, running per the UB0240 manual. It used to work fine, but lately it’s been misbehaving through V4L2.
When I set exposure_auto to 1 (Manual Mode) and then set exposure_absolute to 3, the device keeps streaming with the last settings but stops accepting any further configuration. Any control change after that fails with:
VIDIOC_S_EXT_CTRLS: failed: Connection timed out
exposure_absolute: Connection timed out
If I stop the stream while it’s stuck like this, it won’t start again. The only recovery I’ve found is physically unplugging the USB cable and reconnecting. That’s a problem because this camera is going into a chassis where unplugging/power cycling isn’t an option.
Has anyone else run into this? It really looks like the exposure control is what locks it up.
Thanks for the detailed description. I tried reproducing this on my side but I can’t get it to fail the same way so far. Could you record a short video showing the exact sequence? Start from a working stream, set exposure to 3, then try a couple of other control changes and a stop/restart of the stream. That would help me confirm we’re seeing the same thing.
I’ve put together a bug report with two short videos. I’ll send the folder link by private message since it’s hosted on our company SharePoint. The two clips are video0 - Zoom error.mp4 and video1 - Exposure error.mp4.
Tested on a Windows laptop (AMCap) and on Linux (V4L2), same UB0240 on the Jetson Orin NX 16GB.
Issue 1 - Zoom error (AMCap, Windows):
Setting the zoom value above 23 stops the video stream. Lowering it back to 23 or below resumes the stream.
Issue 2 - Absolute exposure value error (V4L2, Linux):
Setting exposure_auto to manual and then exposure_absolute to 3 causes configuration to stop working and timeouts to appear.
Expected exposure values for the camera:
Min = 3
Max = 2047
Step = 1
Default = 166
Current = 166
Flags = Inactive
Full log from video1 - Exposure error.mp4:
00:06 - Start stream - OK
00:31 - Set manual exposure - OK
00:41 - Set exposure value to 50 - OK
00:46 - Set exposure value to 80 - OK
00:52 - Set gain to 240 - OK
01:01 - Set exposure to 3 - no error code, but no changes
01:10 - Set gain to 220 - NOK, timeout error
01:27 - Set exposure to 4 - NOK, timeout error
01:44 - Disconnect USB camera
01:46 - Connect USB camera
01:50 - Start stream - OK
02:01 - Set manual exposure - OK
02:04 - Set exposure value to 4 - OK
02:09 - Set gain to 220 - OK
02:11 - Set gain to 250 - OK
02:14 - Set gain to 240 - OK
02:20 - Set exposure value to 10 - OK
02:25 - Set exposure value to 3 - no error code, but no changes
02:32 - Set exposure value to 15 - NOK, timeout error
02:55 - List camera parameters and ranges - slow
03:31 - Disconnect USB camera
03:33 - Connect USB camera
03:41 - List camera parameters and ranges - OK
03:45 - exposure value range prints 3-2047
The pattern is consistent: exposure=3 returns no error but nothing changes, then every subsequent control write times out. Only a physical unplug/reconnect brings it back, and setting exposure to 3 again repeats the whole lockup. If I stop the stream in that state, it can’t be restarted.
Got the videos, thanks. I can see what you mean in the exposure clip. Let me pass this along and check whether we can reproduce it internally. I’ll come back once I have something.
Thanks for your patience. We’ve confirmed this is a firmware-related issue on the UB0240.
To summarize what we’re seeing:
Zoom error - in AMCap on Windows, setting zoom above 23 stops the video stream, and lowering it back to 23 or below resumes it. This one is more of an inconvenience.
Exposure error - this is the significant one for your use case. The camera advertises an exposure range of 3-2047, but setting exposure_auto to manual and exposure_absolute to 3 leaves the device unresponsive. From that point every control write returns VIDIOC_S_EXT_CTRLS: failed: Connection timed out, and the only recovery is to physically disconnect and reconnect the USB. Stopping the stream while in that state also prevents a restart.
Our team is actively working on the firmware fix for this. It needs to go through testing and optimization before release. I’ll update this thread as soon as there’s something available to try.