there are also a few bugs in B9: Log was not updatedScreen was not updatedMenu button did not finish the script runningShoot button did not interrupt the script running
I have altered the code a little and ran a short test : Code: [Select] function pwm4(pwidth) repeat_check("shut down",pwidth) shut_down()end
function pwm4(pwidth) repeat_check("shut down",pwidth) shut_down()end
Quote from: waterwingz on 09 / July / 2015, 13:59:34What determine the time between pulses?It might sound strange, but I have no idea. I will look into it once I have a little time.
What determine the time between pulses?
--[[@title PWM Tester@chdk_version 1.3--]]print_screen(123)set_console_layout(1, 1, 44, 10)set_remote_timing(1000)print("USB pwm test started")set_config_value(121,1) -- make sure USB remote is enabledcount=0repeat until get_usb_power(2) == 0repeat x=get_usb_power(2) if ( x > 0 ) then count=count+1 print(count..") pulse="..x.." mSec") elseif (x < 0 ) then x=0-x print(count..") space="..x.." mSec") enduntil is_pressed("menu")set_config_value(121,0) -- make sure USB remote is disabled
Pixhawk generates output continuously so Camera continuously gets PWM input.
elseif pw < 5 then pwm1(pw) elseif pw < 10 then pwm2(pw) elseif pw < 15 then pwm3(pw) elseif pw < 20 then pwm4(pw)
Mission settings: DO_SET_CAM_TRIGG_DIST=17meter (like @ ~80m altitude)
Timing works like a charm! I reached the mission start point at picture 31. I was going 50-60Km/h till I exited the village, that is picture 95. I accelerated to 90Km/h held it there for a while and then accelerated to 110Km/h. Then mission finished. The pause between the pictures can be can be seen by the mode=1 repeated xx
There is only one modification that is absolutely needed : please take out the 10s interval picture taking, as first picture (the one that sets the focus and other things ) needs to be taken at mission operation start, above the target area.
I used the slightly modified version with the altered PWM ranges.
Oh, Question: Should I use ND filter or not? I need crisp crystal clear images.
I don't really want to do that because if the flight controller stops sending pulses once continuous shooting starts, the script will appear to hang. That is going to confuse a lot of people trying to use the script.What is supposed to happen is for the flight controller not to start sending pulses to the camera until it is over the target area and ready to shoot. This will leave the lens retracted and the camera idling in a low power standby mode (i.e. playback) prior to the first shot.Also, when a timeout occurs, the camera should refocus & reset the exposure on the next shot. That appears to not be working so I will fix that.Does that sound better than simply disabling the timeout?
Bottom line is setting focus F-stop ISO and other things has to be done at the operations area for the operations area.
Quote from: netptl39 on 11 / July / 2015, 10:33:22Bottom line is setting focus F-stop ISO and other things has to be done at the operations area for the operations area.Getting rid of the 10 second timeout will not make this happen. However, resetting the focus & exposure on a timeout will (should you happen to accidentally start shooting in continuous mode prior to reaching the target area).
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