The pixhawk setup that we discovered somewhat by trial and error generates pulses in the range of about 4 mSec to 20 mSec, which CHDK can discriminate if high precision USB timing is enabled. The servo output of your RC radio generated pulses shorter than 2 mSec, too fast for CHDK to read.
Did anybody check with the Pixhawk developers if that could have any repercussions on the pixhawk hardware
I have also an S110 and manual focus setting does not work very well.
Although I did read through the source code - it's open source and available for anyone to download. From what I could see, using the values we "discovered" should not cause any issues.
/// Servo operated cameravoidAP_Camera::servo_pic(){ RC_Channel_aux::set_radio(RC_Channel_aux::k_cam_trigger, _servo_on_pwm); // leave a message that it should be active for this many loops (assumes 50hz loops) _trigger_counter = constrain_int16(_trigger_duration*5,0,255);}
/* set radio_out for all channels matching the given function type */voidRC_Channel_aux::set_radio(RC_Channel_aux::Aux_servo_function_t function, int16_t value){ if (!function_assigned(function)) { return; } for (uint8_t i = 0; i < RC_AUX_MAX_CHANNELS; i++) { if (_aux_channels[i] && _aux_channels[i]->function.get() == function) { _aux_channels[i]->radio_out = constrain_int16(value,_aux_channels[i]->radio_min,_aux_channels[i]->radio_max); _aux_channels[i]->output(); } }}
void RC_Channel::output() const{ hal.rcout->write(_ch_out, radio_out);}
/* * Output a single channel, possibly grouped with previous writes if * cork() has been called before. */ virtual void write(uint8_t ch, uint16_t period_us) = 0;
One of the kap_uav.lua users was trying unsuccessfully to engage in a dialog about the application with the pixhawk team. If you have a contact there feel free to reach out to them?
It's possible that cameras in the more expensive G series are actually calibrated - or the lens mechanism does not need calibration.
Quote from: waterwingz on 06 / November / 2015, 19:14:38It's possible that cameras in the more expensive G series are actually calibrated - or the lens mechanism does not need calibration.On this related note, is the G-series then the least expensive line in which you don't have to worry about this problem with "infinity" possibly not really working correctly?
It turns out that my S110 won't focus on infinity. The lens calibration is off. I tested two Canon S110 cameras with the exact same settings using KAP_UAV and the infinity button active. One camera takes perfect photos and the other camera produces blurry photos. Go figure...It wasn't the script. It's the darn cameras. Some are calibrated to work and some won't.
Just FWIW, prior to this http://chdk.setepontos.com/index.php?topic=12103.msg125325#msg125325 setting distances >64k on S100 through CHDK probably didn't work correctly.
Started by Jim Completed and Working Scripts
Started by nadavofi « 1 2 » Script Writing
Started by Benny_H88 « 1 2 3 » Script Writing
Started by davefolts Creative Uses of CHDK
Started by GlobalSurvey General Help and Assistance on using CHDK stable releases
