@srsa_4cSorry, my bad. Here is the correct one.
I'm not able to trigger the camera when "USB Shot Control" set to Pixhawk and "Shot Interval" set to Fast. It works when it's set to OneShot, but the time per shots seems to be slow (attached log -- sunny day outside). Does the Pixhawk setting only works exclusively with the Tuffwing trigger cable? I'm using the one from mobilexcopter instead, do you think that is a factor?
Setting "USB Shot Control" to OneShot will trigger a shot each time the USB +5V level toggles. The "Shot Interval" setting is ignored.
Are you actually using a Pixhawk controller? In Pixhawk mode, the script is waiting for a pulse of a certain length to take a shot - if you are not using a Pixhawk you'll need to setup something to get the same pulse width.
the only "Shot Interval" setting that matters in Pixhawk mode is Burst - which starts continuous shooting as fast as the camera will cycle when the Pixhawk requests a shot.
Edit 1: You need to jumper your Pixhawk correctly so that your interface cable can get +5V from the middle pin of its connector. Typically this requires getting the +5V from your BEC and connecting it to the middle row of pins of the pixhawk.
Edit 2: took another look at your log - thanks for providing that, it helps a lot. From what I can see, you have tried the following combinations :ModeSettingResults PixHawkFastfailPixHawkBurstfailPixHawkFastfailPixHawkFastfailOneShotFastslow random shotsOneShotBurstrandom shotsOn/OffFastfailOne ShotFastfailNoneFast3 sec per shotPixHawkFastfailOneShotFastslow random shotsNote that shooting never starts in Pixhawk mode regardless of the shot rate setting. This suggests that the script never sees the required 3 mSec start pulse from the Pixhawk. However, it does seem to see some USB activity as shown by the random shooting in OneShot mode (it shoots each time it detect the USB signal changing).
So my guess here is that you are not matching the setup of you PixHawk to what the script is expecting to see on the USB +5V line?
Looking for some help with my aerial shoots being extremely over exposed. I have a Powershot SX610 in a fixed wing drone and being triggered by a pixhawk. The attached picture was taken today at 400 ft on a sunny day.
Quote from: PaulOski on 26 / January / 2019, 20:49:51Looking for some help with my aerial shoots being extremely over exposed. I have a Powershot SX610 in a fixed wing drone and being triggered by a pixhawk. The attached picture was taken today at 400 ft on a sunny day. Please post the log file created by the script (kap.log) as an attachment here. It should be located in the top level folder of your SD card. Were all shots over exposed or just some of them? If only some were, it would be helpful to know some of affected image filenames too as I look through the log.Did you try shooting on the ground with the script? Disable the USB / Pixhawk stuff and just run the script as an intervalometer while the camera is pointed at a normal daylight exposure scene.
kap.log attached. All of the pictures (1/26/2019) on that flight were overexposed, 27 in total. I will try the intervalometer later today. Thanks for the guidance and any additional thoughts.
Started by Jim
Completed and Working Scripts
Started by nadavofi
« 1 2 »
Started by Benny_H88
« 1 2 3 »
Started by davefolts
Creative Uses of CHDK
Started by GlobalSurvey
General Help and Assistance on using CHDK stable releases