Re: [Paparazzi-devel] CHDK and digital_cam.xml

[MRSA]

Thanks a lot. I had figured out some of it looking at the code, but you gave me some useful hints.

As for the pulse length I don’t really need it. I just wanted to retract the lens while starting and landing and I found another way to do it (described in a previous mail).

 

De : address@hidden [mailto:address@hidden De la part de Christophe De Wagter
Envoyé : mercredi 23 mai 2012 08:40
À : address@hidden
Objet : Re: [Paparazzi-devel] CHDK and digital_cam.xml

 

Hi,

 

In the flightplan you can simply SET variables or CALL functions. For digital camera shooting that would be calling dc_shoot() for a single photo (e.g. when you arrive at a destination point) or setting dc_autoshoot = DC_AUTOSHOOT_PERIODIC.

To make things better there is also the line-start and line-stop functions that can be filled and are automatically called from navigation routines. Paparazzi splits up all navigation into straight lines and circles. And most survey options only need photos during the straight parts, or the other way around. 

 

Put the following in your flight plan header to use this:

 

 

  <header>

 

#include "generated/airframe.h"

 

 

 

#ifdef DC_AUTOSHOOT_QUARTERSEC_PERIOD

 

#include "modules/digital_cam/dc.h"

 

#define LINE_START_FUNCTION dc_autoshoot = DC_AUTOSHOOT_PERIODIC;

 

//#define LINE_START_FUNCTION dc_Survey(dc_gps_dist);

 

#define LINE_STOP_FUNCTION dc_autoshoot = DC_AUTOSHOOT_STOP;

 

#endif

 

 

 

</header>

 

and define the wanted DC_AUTOSHOOT_QUARTERSEC_PERIOD in your airframe file.

 

To find out about all triggering options you should look into https://github.com/paparazzi/paparazzi/blob/master/sw/airborne/modules/digital_cam/dc.h. You can trigger on UTM grids, based on distance from a start point, on circles etc.

 

You can play with it in simulator mode too as the ground station shows yellow dots where photos were taken, (until some OCAML expert makes things nicer). This is shown based on the DC_SHOT message which has the photo number and its coordinates if you defined SENSOR_SYNC_SEND. 

 

To make different pulses for zooming, you should probably make a copy of led_cam_ctrl.h/c and have different DC_SHUTTER_DELAY. The default code has only one type of pulse (so far).

-Christophe 

On Tue, May 22, 2012 at 4:38 PM, Cédric Marzer (privé) <address@hidden> wrote:

Hello,

I just finished a wing with an ixus digital camera : twog + aspirin IMU + sparkfun logger + jeti sat receiver. The first flights are very promising.

I am playing with the digital camera module with some success but I still have a few questions :

-Did anyone try to use it with CHDK with scripts to determine what function to trigger (shoot, power on and off, zoom, etc.)  based on the length of the pulse ? http://chdk.wikia.com/wiki/USB_Remote_Cable see pulse width remote script

- Does anyone of you have a flight plan of a surveying job ? I am not sure how the digital_cam functions and the navigation routines interact with each other and there is very little documentation about it.

Thanks in advance,

Cédric

_______________________________________________
Paparazzi-devel mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/paparazzi-devel