General • Inspections

Cargo Camera Overexposure

This procedure outlines the steps for diagnosing and correcting interior cargo camera overexposure on the robot by verifying the installed camera, checking camera settings, and confirming proper operation. It includes inspecting the camera feed, using Jenkins, CHViz, and Teleport to run diagnostic commands, replacing the camera when necessary, updating the exposure_dynamic_framerate setting when required, and verifying that the overexposure issue has been resolved before returning the robot to service.

DoorDash Labs Global Org

07/15/2026

Cargo Camera Overexposure

Follow these steps when the interior cargo camera is exhibiting overexposure symptoms.

Power on the robot and connect a charger if needed.

Access jenkins to launch stack. Once launched, view CHViz to inspect cargo camera feed. May need to be outside in the sun to duplicate overexposure issue or point a bright flashlight directly at the camera. This is just to attempt to duplicate the issue and may not always result in overexposure condition.

Access telepot of the bot you are working on. It may be necessary to connect the bot to ethernet.

Once you are connected to the main compute within teleport, copy and paste this " v4l2-ctl --list-devices " (Without quotations) then hit enter.

Review the output from the Compute.

If the output returns with this "Arducam 1080P Low Light: Arduca (usb-0000:00:14.0-3)" replace the camera then recheck the camera feed for overexposure condition. Should be resolved. Release the bot back to operations.
If the output returns with this "Arducam USB Camera: Arducam USB" the correct camera is installed. In teleport at the compute type " v4l2-ctl -d /dev/video0 --list-ctrls " (Without quotations). Look for the output line called "exposure_dynamic_framerate". The value should be set to "value=1". If the value shows "value=0" continue to the next step.

Change the non-low light camera exposure_dynamic_framerate value to 1 if needed. While in the compute and on teleport, type " v4l2-ctl -d /dev/video0 -c exposure_dynamic_framerate=1 ". (Without quotations) Once successful, type " v4l2-ctl -d /dev/video0 --list-ctrls " (Without quotations) again to check the "exposure_dynamic_framerate" value is now set to 1. Double check the camera feed to verify the overexposure condition is no longer present.

If you would like to verify the replacement camera has the correct exposure setting stored, type " v4l2-ctl -d /dev/video0 --list-ctrls " (Without quotations) to verify "value=1"

Source: DoorDash Labs Global Org (Community Member)

Power on the robot and connect a charger if needed.

Access telepot of the bot you are working on. It may be necessary to connect the bot to ethernet.

Once you are connected to the main compute within teleport, copy and paste this " v4l2-ctl --list-devices " (Without quotations) then hit enter.

Review the output from the Compute.

If the output returns with this "Arducam 1080P Low Light: Arduca (usb-0000:00:14.0-3)" replace the camera then recheck the camera feed for overexposure condition. Should be resolved. Release the bot back to operations.

If you would like to verify the replacement camera has the correct exposure setting stored, type " v4l2-ctl -d /dev/video0 --list-ctrls " (Without quotations) to verify "value=1"