My camera is elph320 hs.
Thanks for that. It would be good to know what version of CHDK you are using, and the version of the script.
KAP 2.4 with CHDK 1.3.0-3437
ixus240_elph320hs 101a
1. My flight was 300 meter high. Some picture are good, more are not good. Bad picture looks like has focus problem.
Hmmm ... so most likely causes are either low shutter speed, bad focus, UAV vibration, or earthquakes.
if you can check the picture and log, you will see all the shutter time are right at 1/1000. also from picture you can not see blur, i guess is the only focus problem, please let me know if I'm wrong.
My wing is kind of stable while flying, maybe bank and pitch in 5 degree. My camera is not in perfect status because was a hard crash before. But taking picture in the ground is normal.
Sound like you should be okay then. Hard crashes really suck though - kind of like watching $100 bills burn in a bucket.
Here I would like thanks for my Zephry II wing, so tough, I crash to a tree ar 60 meters high, and fall to the ground, just need a little fix, nothing need to replace. amazing, right ? only make me worried is my camera, test on the ground look normal, and fly in the sky still take some good picture, but more are bad picture. lololo... I shake the camera I can hear some sound inside, like some piece are not fixed.... that could be the problem ? but why still take good picture ?
Is that possible camera focus ability has problem, maybe focus lock time is too long ? How to verified it ?
The script locks the focus prior to the first shot. It should not change after that, so focus lock time or focus ability should be "all good" or "all bad". Unless the camera actually failed to lock focus that is. Need to see the script log.
what means script locks the focus prior to the first shot ? it is not always in infinity focus ? if it is always infinity lock, why some are good some are not good? even I saw my first shot is not focus, but later some picture can focus, some can not... that is the strange thing.
How to verified it ?
Let's start with the script log file? Please post it here.
That bank and pitch should not cause the problem right, because shutter was really fast at 1000.
Shutter speed at 1/1000 is probably the minimum you want to use. Faster would be better.
you are right, you can see in log, all are taken in 1/1000, no blur, just no focus.
2 USB control is really working great, but the problem is the time, when I trigger it, it took 6 second to be ready for another trigger, before that if you trigger it, it just been ignored. How can I improve it ? Because if I put intervalometer camera can the picture in 3 second fastest.
The USB control mode was setup to start/stop intervalometer shooting when the USB power = 5V ( i.e. On). It was really not designed for single shot shooting via USB pulses. Obviously it could be changed to do that if necessary if you can't leave the USB on when you want the UAV to be shooting. The nice thing about the current setup is that it retracts the lens when USB power is absent. This slows down the cycle time but is a really nice thing to have prior to your UAV rejoining the ground.
[/quote]
nice to know that, sorry for I can not undersstand clear the script about USB control. but my suggestion is for UAV shooting, most of case people will need autopilot control board to control the camera shoot, not by camera intervalometer shooting, because autopilot can make camera shoot by distance, not time. by the wind, UAV can fly faster or slower, but photo need to be arranged in same distance. for that reason, can you modified the script for this purpose ? one USB pulse, one shoot, as fast response as the best. that will helps a lot.
