APM Camera trigger experience please!

Hi Guys, 

APM2.6 + AP3.2 + Canon S110 + CHDK + Gentles wire + modified KAP_UAV.lua is what I am using.

 

this way I should have 6 paramateres I can set remotely. Ch1 is set to RC7 and CH2 is set to RC6 as I was unable to get reliable signal from A9. 

At this moment I only need 2 of the 6 parameter slots: Shoot +shut_down. 

RC7_FUNCTION=10 which is camera trigger 

RC6_FUNCTION=1 which is RC passthru (to least save most of the camera if it is on the way to crash).

Question: 

who is using what PWM to not have it translated to the camera as input?

Why is this an issue? 

case1: the camera trigger gets delayed due to signal that doesn't do anything, but PWM is sent to camera . 

case2: misalignment of APM signals lead to shud_down command being received.

case3: flight log showing camera trigger without a photo actually being taken

I would really appreciate some ideas on who did you guys solve this! 

Many thanks in advance!

Tom

You need to be a member of diydrones to add comments!

Join diydrones

Email me when people reply –

Replies

  • Tom :

    The latest version of the kap_uav.lua script ( 3.4 ) uses CHDK's new support for high precision PWM timing (CHDK 1.3.0 or newer).   This should help a lot with your issue,  Prior to this, some cameras models showed jitter exceeding 50 mSec.  Now they are all good to 1 mSec - a huge improvement!

    WWZ

    • Thanks WWZ!

      I moved to above version, but all I was getting was that the pulse was too high. For the moment I went back to the old versions but accurate 1mSec would be huge.

      I will check back once i know why this happened. 

      • Somebody else caught this too!  

        The script's new precision USB pulse width measurements are accurate to 1mSec rather than 10 mSec.   So the timer base was set to 1mSec and that throws off systems expecting 10mSec.

        The updated version of the script reverts back to 10mSec.  This will fix the "pulse too high" problem you are seeing.  Just download the current version - it should work like the old one except the measurements will be much more precise.

        The next version of the script (currently being tested) will allow the user to select the base pulse time and automatically adjust based on what is selected.  Which is pretty much what I should have coded it to do in the first place.  My bad.

This reply was deleted.

Activity