@seka Seems to be fixed right now

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

@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 another problem that now occurs (and which has occured seldomly before): images are corrupted:

@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 Sorry, realised I had this error before: Problem: not current veye_mipi_i2c.sh ... solved now

@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 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 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?

@what I forgot to say: Sometimes, the images are also the same between the boot cycles. For example the last test: 1. boot image is "normal", all are the same,
2. boot cylcle: images are brighter than in 1. cycle but all the same within the 2. boot cycle,
3. boot cycle: all are same as first boot cycle and all are same