[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Paparazzi-devel] Commanding h_ctl_course_setpoint and v_ctl_altitud

From: Todd Sandercock
Subject: Re: [Paparazzi-devel] Commanding h_ctl_course_setpoint and v_ctl_altitude_setpoint directly
Date: Wed, 16 Mar 2011 15:41:09 -0700 (PDT)

Hi Max

Variables are accessible easily by setting them in a settings file.

This is a really dodgy way of doing it but for a quick trial I would put the variables you want to access in the settings file, run a simulation, open ivy_probe then change the variables you want to change in the GCS and watch what commands the GCS sends on ivy_probe..... again it's a really dodgy way of doing it...

Second way is to make a module that receives telemetry commands and sets variables for you. Also probably just as quick....

I haven't got an ubuntu machine on me at the moment to check but I am pretty sure if you are flying in a "heading" flightplan block and change the course_setpoint (Or what ever the variable name is called) you should be able to tell paparazzi where to go...


From: Max Chtangeev <address@hidden>
To: address@hidden
Sent: Thu, 17 March, 2011 1:41:13 AM
Subject: [Paparazzi-devel] Commanding h_ctl_course_setpoint and v_ctl_altitude_setpoint directly


I was wondering if there is any information/documentation on how to command course_setpoint and altitude_setpoint directly, bypassing the navigation loop? We are working on an alternate fligh-planning / top-level navigation software and would like to drive the lower-level ap loops directly from it via Ivy bus messages. One thought was to move a waypoint via MOVE_WAYPOINT message, but this would introduce some redundancy in the use of the Paparazzi navigation loop.

Many thanks,

reply via email to

[Prev in Thread] Current Thread [Next in Thread]