I’m using the Zed2i
In some occasions, it has a problem of overexposure in the right image.
It seems it calibrates itself in the first frame, and keeps its setting until shut down. Problem, it happens that the right image (and only the right image) sets its exposure calibration way too high and the resulting SVO is not exploitable.
How can I prevent it from happening ?
I cannot watch the resulting image live via Zed Explorer : it is supposed to be used in a driving car, and we launch it via CLI.
Do you manually set the exposure or do you leave it on auto?
Also, does it happen from the start or does it happen during the execution? If it’s not from the start, does it always happen after some time?
Can you try hard resetting the auto-exposure ROI at the beginning of the program? You can do that by adding a call to set_camera_settings_roi with reset parameter to true ~5 seconds after the start of your program.
I’m suspecting that for some reason the auto exposure for the right sensor is calculated only once (and bad, it seems). Does the exposure on the right sensor change in “normal” usage? Like with zed explorer, if you vary the luminosity.
I’m having the same issue - only my right image is overexposed. I tried adding a call to set_camera_settings_roi, but that did not change anything. I also tried warming up the cameras by taking 20 images with a 200ms pause in between, but that also didnt help. How am I supposed to fix this?
I am running this version of the driver: ZED_SDK_Tegra_L4T36.4_v5.0.7.zstd with two GS Zed One’s
Hi @adinesh
what you described is something different because you are using different cameras with different technologies.
Please expose the problem in a new thread with all the details and pictures.