tl;dr > use the most recent CHDK 1.3.0 to run kap_uav version 2.2
I believe the following issue is purely KAP_UAV related
Actually, it's not. Both the 1.2, 1.6 and 2.2 versions of the script are just fine.
But I can see how you could be confused about it.
With the new version of KAP_UAV I have now the following msg :
*** STARTED ***
KAP 2-2 started - Press Menu to exit
CHDK 1.3.0-3250 a2500 100a Nov 28 2013
CHDK 1.2.0 build 3276 or higher required
*** FINISHED ***
So my beloved kap_uav script is on strike.
This tells me you are running the 3250 build of CHDK release 1.3.0. That's an older version of CHDK 1.3.0 released prior to the problems with saving script parameters and before the changes to SD overrides that the 2.2 version of kap_uav.lua needs when using CHDK 1.3.0
So the script correctly refused to run.
Is CHDK 1.3.0 not higher than 1.2.0 ?
This is probably why you are confused. The source code for all versions of CHDK are kept in same svn version control repository. When an change is made to any version, the revision number for the whole repository increments. So CHDK 1.3.0-3250 is actually older than CHDK 1.2.0-3275 in terms of what version of the code repository it was built from, even though it may contain changes and updates not found in CHDK 1.2.0-3275.
If that's confusing, you'll just have to trust me on that one.
Compounding this confusion (and hence the deceptive error message) is the fact that the 2.2 version of the script will work with older versions of CHDK 1.2.0, which do not have the SD override updates used for "focus at infinity". When the script see 1.2.0, it uses older (inferior) methods to try and set focus at infinity. It could probably also do that for older versions of 1.3.0 but doesn't.
FYI, other scripts installed per default still work well (intervalometer, etc...)
They will as long as they are not trying to use the new features of 1.3.0
*** UPDATE
I kept CHDK 1.3 but downgraded to KAP_UAV 1.2 and guess what ? It works fine but also saves the script parameters values !
Proving my point. kap_uav 1.2 does not use the new MF features of 1.3.0 and so does not need a recent version of 1.3.0 And the old version of 1.3.0 you are using did not have the problem with saving script parameters. (Incidentally,
kap_uav 1.6 is the most recent version that does not need an up-to-date 1.3.0 release)
The answer here is to update your CHDK 1.3.0 version to 3394 or newer (which has the fix for the script parameter bug and the new SD overrride MF code) and you should be back in business for the most recent 2.2 version of kap_uav.lua !
