Those previous logs were all tests in the garage primarily making sure the pixhawk would trigger the camera.
I thought that might be the case - the Bv (brightness values) are quite low as might be expected indoors. Important clue there - read on.
I used your suggestion and tested the intervalometer. The intervalometer scripted running looks good.
Actually, I meant for you to run the
kap_uav.lua script in "intervalometer mode" (i.e. with the Shot Interval set for shooting every 10 seconds or so - no pixhawk used).
I ran KAP again and made numerous adjustments to TV, ISO, Exposure and I'm getting closer.
Looking at your log file, the final script run (with the overexposed images) was done in very bright daylight. And that seems to be causing problems between the camera and script over the use of the ND filter. Strange to stumble on this now with a script that's been downloaded over 5000 times and used mostly outdoors.
Here's what I think I see, using the image you posted (IMG_0889.JPG) for reference.
- The camera wants to expose for 1/500 of a second at ISO80. Its fixed aperture lens opening is at f4.0 (determined by the zoom position you are using). From what I can see, the camera also used its ND filter - resulting in an effective f-stop of f11 instead of f4.0
- The script takes those values and tried to increase the exposure time towards your 1/1000 second target time. As it does so, it increases the ISO setting to compensate. When the ISO setting reaches the maximum value of 800, it stops increasing the shutter speed - in this case stopping at 1/640 seconds. It then shoot but without using the ND filter.
Something is very wrong here.
- the ISO setting goes up by a factor of 10x
- the shutter speed only increases by about 10%
- the effective aperture opens by 3x due to the script not using the ND filter
No wonder the image is massively over exposed. I need to spend a little more time studying how the ND filter is interacting here.
Maybe the reason we've not seen this before is that AFAIK most Powershot don't use the ND filter very often - in some cases only in scene modes like "fireworks".
Interestingly, your camera reports that it's running in something called HYBRID_AUTO mode, described in the manual for your camera as taking a 2 - 4 second video before each shot?? Do you really have it set to HYBRID_AUTO? Or is this a bug in the camera port resulting in the wrong shooting mode being reported?
So,
I'd suggest setting the camera into "P" mode if you have not done so, as very strongly recommended here :
KAP_UAV Exposure Control Script : Camera Settings . It won't fix whatever is wrong (if anything) in the script's ND filter logic but P mode might stop the camera from trying to use the ND filter in the first place.
More to come ....