RPI Camera IMX327 different brightness values between startups

[Seka]

@veye_xumm Hello Xu,

I expect exact same images, but I get different ones. Images stay same within same boot cycle but change after booting. I will send you images later.

Can you please provide example code for raspistill where image settings are not automatic, all manual, everything controlled --> no changes between images?

[Seka]

@seka regarding example code: I still run the i2c commands and just raspistill, and that is all i guess... how much sleep between i2c commands do you recommend between commands and before taking image?

[veye_xumm]

@seka
I see your question.
There is no need to test with raspistill, the result should be the same as your python test.
I have some test suggestions that you can try.

1. Do not enable low_light mode.
2. Increase the speed of ae adjustment at the beginning of your scripts.

. / veye_mipi_i2c.sh-w-f aespeed-p1 0x64-p2 0x64

It's just for the purpose of pure testing.

[Seka]

@veye_xumm I just checked and another problem I have: I get no return value from the whitebalance mode and I cannot read its state also....

[Seka]

@seka Sorry, realised I had this error before: Problem: not current veye_mipi_i2c.sh ... solved now

[Seka]

@seka with regarding to your suggestion " do not enable low_light mode": When I disable it, images are very dark.... and I already have longest shutter settings....

[Seka]

@seka another problem that now occurs (and which has occured seldomly before): images are corrupted:

[Seka]

@seka ok, I understand now what the problem is: os.system does not reliably execute shell commands. When executing directly in the terminal ---> problem is gone. Thank you

[veye_xumm]

@seka
Hi,
All problems sloved?

[Seka]

@veye_xumm No, but I am currently assessing wether it is a light source problem or camera problem. Will get back soon..

[Seka]

@seka Seems to be fixed right now

[veye_xumm]

@seka OK~