Ebeo / arducopter

Automatically exported from code.google.com/p/arducopter
0 stars 0 forks source link

Camera Trigger Function Not Working #492

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
APM2, ACM, MP 1.2.1
What steps will reproduce the problem?
1. Follow steps in wiki to setup camera triggering function 
(http://code.google.com/p/ardupilot-mega/wiki/Tracking) - Set RC8_FUNCTION > 
camera_trigger.
2. Set RC8 Min and Max Servo values to 1100 & 1900ms
3. Plug servo into the correct channel output

What is the expected output? What do you see instead?
Expect servo to move to commanded position, either 1100ms or 1900ms. Servo does 
nothing, no response at all.

Additional feature request: Some way to actually test if the camera trigger 
works without actually having to go fly, a test button in the MP or set 
condition perhaps?

Original issue reported on code.google.com by graham.d...@gmail.com on 27 Sep 2012 at 5:49

GoogleCodeExporter commented 9 years ago
http://www.diydrones.com/forum/topics/automated-parachute-drop
http://www.diydrones.com/forum/topics/camera-control-with-2-5

Original comment by graham.d...@gmail.com on 27 Sep 2012 at 5:49

GoogleCodeExporter commented 9 years ago
www.diydrones.com/forum/topics/do-set-servo-works

Original comment by graham.d...@gmail.com on 28 Sep 2012 at 7:09

GoogleCodeExporter commented 9 years ago
It seems to be related to Issue #475. And  potential fix was suggested there. 

Original comment by roundfol...@gmail.com on 1 Oct 2012 at 10:11

GoogleCodeExporter commented 9 years ago
Did your potential fix actually fix the problem? 

Original comment by graham.d...@gmail.com on 1 Oct 2012 at 10:26

GoogleCodeExporter commented 9 years ago
Discovered while playing with the HIL simulation that any DO_xxx command only 
works if a dummy waypoint is placed after the that command, so DO_SET_SERVO 
actually does set the servo 6 (RC6_xxx) to whatever you told it in the mission 
planner (RC6_MIN/MAX) BUT although the mission planner actually shows the 
CH6_OUT as changing there is no physical PWM output that would drive a servo.

Original comment by graham.d...@gmail.com on 21 Nov 2012 at 7:26

GoogleCodeExporter commented 9 years ago
As for the additional feature request above, if you right click on the map in 
Mission Planner there is a popup menu option for 'trigger camera NOW'. Will 
that do the trick once the underlying functionality is working?

Original comment by amchap...@gmail.com on 9 Dec 2012 at 7:17

GoogleCodeExporter commented 9 years ago
In 2.9 the camera control is working again.  You'll be able to kick it off 
either using the DO_DIGICAM_CONTROL message or the channel 7 switch.

You can see the new configuration screen in the mission planner's Hardware 
Options, Camera Gimbal area down at the bottom.  It includes the ability to 
select the servo to use to trigger the shutter and the on/off position as well.

2.9 out is just about to go into testing so it won't be too long (maybe just 
over a week) before it's available in the planner.

Original comment by rmackay...@gmail.com on 10 Dec 2012 at 1:10

GoogleCodeExporter commented 9 years ago
Any idea of when 2.9 will be out?

Original comment by simone.chiaretta on 18 Dec 2012 at 5:47

GoogleCodeExporter commented 9 years ago
Yes I know when 2.9 came out ;-)
Issue should be fixed in 2.9

Original comment by Benny.Si...@gmail.com on 19 Jan 2013 at 7:08

GoogleCodeExporter commented 9 years ago
Issue closed. 
If you find this is an error please report it in the new issues list
https://github.com/diydrones/ardupilot/issues?labels=ArduCopter&page=1&state=ope
n

Original comment by Benny.Si...@gmail.com on 19 Jan 2013 at 7:08