There is a small probability that the left side of the camera display may turn black, and can InitParameters.enable_image_validity_check detect this situation?

[IASUI]

Sometimes the camera will go black even if it starts normally;
in this case, there will be no prompt, and the error will not be detected even if you use ZED Diagnostic (I apologize for not saving the diagnostic file at that time, so I cannot provide it).

This situation is usually resolved using the reboot API,
but I noticed an API: InitParameters.enable_image_validity_check. I wonder if it can detect this situation?
Additionally, this API cannot actually be used because it corresponds to ERROR_CODE: CORRUPTED_FRAME, which seems to be unavailable.

PS: The SDK version I am using is 4.25.

[Myzhar]

Hi @IASUI
this is not normal.
Does it happen also with ZED Explorer or ZED Depth Viewer?

[IASUI]

Yes, but I didn’t check the ZED Depth Viewer when this happened before.
This situation rarely happens, but for the multiple devices I purchased over a long period of time, it is estimated that this situation has occurred more than 20 times in total.

[Myzhar]

OK, it seems a problem with the particular light conditions and the ISP processing concerning the automatic exposure.
Normally the enable_image_validity_check allows you to detect this type of condition and grab returns the error CORRUPTED_FRAME.

Please use the latest version of the ZED SDK for this feature.

[IASUI]

I think I have updated to the latest 4.2.5 version of the SDK, but the CORRUPTED_FRAME enumeration doesn’t seem to be available.

The name only exists in the member_names

[Myzhar]

This is probably a problem with the Python wrapper.
I reported the bug to the team and it will be fixed soon.

[IASUI]

OK, thank you very much