Uttam, thanks for the help. I am continuing to dig into this. I did try everything I could find to resurrect the throttle to no avail. The resurrect button did nothing, and setting kill_throttle to 0
Thank you Pascal. Your "PS" was the clue. The voltages in the airframe file were wrong. Steve from a fresh svn extraction, in the "Holding point" block of basic.xml, changed with <attitude roll="0" t
Hi, from a fresh svn extraction, in the "Holding point" block of basic.xml, changed with <attitude roll="0" throttle="0.5" vmode="throttle"/> compiled with microjet5.xml airframe, it runs as expected
Hi Iman, thank you for your hint. Another test with the same setup after "launching" resulted in a running motor in auto2 mode. However, I am not sure if this has been the point during my last test,
Hi Pascal I think you didn't "Launch" your aircraft! If you have red color in background of your throttle indicator in GCS strip, click on launch and resurrect buttons. On Fri, Jul 8, 2016 at 2:15 AM
I also had this problem and it was because I didn't hit the "Launch" button before doing a manual launch and then switch to AUTO1 and then AUTO 2. The reason is that the flight plan sets the throttle
I think you may also need to have the throttle set above idle/min when you switch from AUTO1 and AUTO2. Not entirely sure if that's just my own superstition so it would be great if someone could vali
Hi Kurtis, try the search string "resurrectthrottle" in the paparazzi-devel archive: http://lists.gnu.org/archive/cgi-bin/namazu.cgi?query=resurrect+throttle&idxname=paparazzi-devel&max=20&result=no
Hi Norman, before Takeoff make sure you have pressed the Takeoff and the Launch button. If you do not get any throttle in flight when switching from AUTO1 to AUTO2, it can help to press the Resurrect
Hi everyone, I figured out, what it was: The kill-switch bug like described here: https://github.com/paparazzi/paparazzi/issues/102 . It was solved by removing the kill switch define in the airframe.
Hello everybody, some news: I figured out, that I'm able to resurrect as long as the radio is off (the bar turns orange upon resurrect). Once it is switched on I'm not able to resurrect anymore. Acco
Hi Cedric, if you want to use arming via yaw stick, DON'T <define name="USE_KILL_SWITCH_FOR_MOTOR_ARMING"/> (or did you have this commented out when trying to arm via yaw stick?) Also I'm not sure wh
Hi, The fly test was.... same as the rainning weather... I have "gited" paparazzi....the nav switch on/off run now correctly. thanks, Eric Le 09/11/2011 11:50, Eric BAHIER a écrit : Hi, I go to fly,
Hi, I go to fly, the weather is OK, When I back, I'll update my system thanks, Eric Le 09/11/2011 10:25, Gautier Hattenberger a écrit : Hi, I already had this problem and it should be fixed in the c
Hi, I already had this problem and it should be fixed in the current master code. It was an issue of the state machine that controls start and stop with the RC. It used to override the nav kill/resur
Hello John, please note that you're able to set a custom voltage level where Paparazzi kills the throttle well above when the speed controller does. That way, you still have plenty of room to get the
Hello, I think my problem is that the autopilot doesn't read my yaw stick correctly. When I print the messages, the value of yaw changes in the ROTORCRAFT_RADIO_CONTROL message but it doesn't change