SOLVED RPI Camera IMX327 different brightness values between startups
-
@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?
-
@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.- Do not enable low_light mode.
- Increase the speed of ae adjustment at the beginning of your scripts.
. / veye_mipi_i2c.sh-w-f aespeed-p1 0x64-p2 0x64It's just for the purpose of pure testing.
-
@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 Sorry, realised I had this error before: Problem: not current veye_mipi_i2c.sh ... solved now
-
@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 another problem that now occurs (and which has occured seldomly before): images are corrupted:
-
@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
-
@seka
Hi,
All problems sloved? -
@veye_xumm No, but I am currently assessing wether it is a light source problem or camera problem. Will get back soon..
-
@seka Seems to be fixed right now
-
@seka OK~
