Debug version of the script : ku_test.luaPlease run this and post the resulting log here.TIA
two KAP.LOGs as attachment.
dprint("Debug :hook_shoot.set") press('shoot_full') -- and finally shoot the imagedprint("Debug : shoot_full") while not hook_shoot.is_ready() do sleep(10) end -- wait until the hook is reacheddprint("Debug : hook_shoot.is_ready done")
The hook_shoot.is_ready() function never returns true on your older camera. Either something wrong with the raw hooks or (more likely) something I am doing wrong while trying to use them. Will likely need some of reyalp's help here.
Quote from: waterwingz on 12 / April / 2015, 16:47:16@exposeIT I think I found the issue, please try the test build posted in the porting thread.I posted a test build in the porting thread,
@exposeIT I think I found the issue, please try the test build posted in the porting thread.I posted a test build in the porting thread,
Hello Waterwingz,Thanks for the awesome script! I'm using it successfully with USB Shot Control set to One Shot with a Pixhawk Autopilot. However, I'm unable to retract the lens. I see you've implemented a couple of features that will almost work (PWM and return camera to playback mode). Can the script be set so that I use multiple PWM values to, extend lens, take picture, retract lens?Thanks!Brian
Brian, I am also using PixHawk with CHDK. Unfortunatedly, "PWM" is not the best name for that mode. The script is not reading a RC PWM signal. It just reads 5v DC signal (what it does is measure for how long there is a 5v voltage in the usb power line).
You cannot use the pixhawk as is to drive the camera's (wrongly named) "PWM" mode. What I did is buy a "RC controlled switch", and connect it to the Pixhawk's channel 7 output on one side and a gutted USB port on the other.
Quote from: Naccio on 17 / April / 2015, 12:43:02Brian, I am also using PixHawk with CHDK. Unfortunatedly, "PWM" is not the best name for that mode. The script is not reading a RC PWM signal. It just reads 5v DC signal (what it does is measure for how long there is a 5v voltage in the usb power line).Well, PWM is an acronym that means Pulse Width Modulation. With PWM information is conveyed by an input pulse via the length of the pulse. CHDK's USB input function can read such "pulse width modulated" signals. And as such, calling the CHDK PWM input by that name is correct.
Quote from: NaccioYou cannot use the pixhawk as is to drive the camera's (wrongly named) "PWM" mode. What I did is buy a "RC controlled switch", and connect it to the Pixhawk's channel 7 output on one side and a gutted USB port on the other.As I understand the issue with the PixHawk output is a question of the Pixhawk only providing a 3.3V PWM signal and the Canon camera USB port expecting 5V. So a level translator is needed. Many others have interfaced a Pixhawk directly to a CHDK camera using the PWM capability of both. I'll dig up the links later if necesary.Otherwise, there is a device available from Gentles that will directly connect an RC servo signal to the camera.
I don't have any formal knowledge about the subject, so I may be wrong. I believe that to be able to call a pulsed signal "PWM" the signal has to pulse regularly (for example every 20ms), and what you vary is how long you keep the pulse high. I don't know if it can be called PWM when there is no pulse repetition.
Anyway, this is not really important except for one detail: In RC the standard is to use a PWM signal at 5v, with the pulse's length (usually) varying between 900 and 1900us, and the pulse repeating every 20ms. If you have RC background and read 5v PWM, you might believe this script's "PWM" control scheme is compatible with RC's standard PWM, when it is not.
What you are talking about here are not the Pixhawk's main RC PWM outputs (which output a 5v PWM signal), but it's auxiliary outputs, which can be configured as switches, but output a 3.3v signal instead of a 5v signal. These switches could be used to drive your script's "PWM" mode, but in order to do so you need to drive the voltage up to 5v.
The Gentles device reads the Pixhawk's main RC outputs' PWM signal (or any RC receiver's PWM signal) to drive a switch which outputs 5v pulses.
Using the new high precision timer in CHDK 1.3.0 it is quite possible to read and interpret a PWM sequence generated to this specification. So it can be quite compatible if setup correctly.
Hmmm ... well seeing as we are on a terminology kick today, I think those PWM outputs your are describing are simply the standard RC digital servo signal that had been around forever?
I never thought the hardware might be able to read pulses with sub millisecond resolution! Implementing this would be great, it would enable anyone with a RC radio system to control a canon camera without any extra hardware!
#define CAM_REMOTE_HIGHSPEED_LIMIT 250
As soon as I get my SD1100 back I will try to program a script to do just that.
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