[Paparazzi-devel] Trajectory pivoting in flight plan and wind direction/speed

[Roman Nikitin]

Thank you all for the answers, after I spoke to Felix via IRC my sim session is 
working well. 

I have a couple of questions more, which are more general. 

First one: My flight plan trajectories are defined and each of them include a 
lot of points. I am looking for the way to pivot the trajectories including all 
the points about one point, so that the first part of the trajectory is always 
directed against the wind flow direction. Of course the wind direction will be 
defined before each flight. So I need to change all trajectories as I described 
before. Have anybody used something like this? Have you any ideas how to do it?

Second one: I need to define on some way the direction and speed of the wind in 
the altitudes my flights carried out. As I can see GCS show me some data about 
wind speed and direction. But I ask me how precise is it? And what methods will 
be used to calculate it? I had an idea to calculate the wind speed and wind 
direction using ground speed (GPS), truth airspeed (Airspeed sensor) and drift 
distance, so as it was done in the "stone times" by the pilots. Another idea is 
to use a balloon with an anemometer, but the models I could use together with a 
balloon are quite expensive. Any ideas for how to measure the wind speed and 
direction in different altitudes using paparazzi equipment? Or some alternative 
methods?

I heard Martin had similar questions some days, Martin, didn`t you? Have you 
found a solution for both of the questions above?

Regards, 

Roman

-----Ursprüngliche Nachricht-----
Von: address@hidden [mailto:address@hidden Im Auftrag von Martin Mueller
Gesendet: Freitag, 5. November 2010 15:57
An: address@hidden
Betreff: Re: [Paparazzi-devel] EagleTree Airspeed Sensor codes

Then please post the error message :-)

On 05.11.2010 16:54, Felix Ruess wrote:
> You actually should get an error message telling you to change it to
> twog_1.0 if you still have twog_1 set as your board.
>
> On Fri, Nov 5, 2010 at 4:52 PM, Martin Mueller<address@hidden>  wrote:
>>
>> try twog_1.0 instead of twog_1
>>
>> On 05.11.2010 16:41, Roman Nikitin wrote:
>>>
>>> Hi all,
>>>
>>> I used the instructions on wiki to add the codes for EagleTree Airspeed
>>> Sensor. Before I did it, my simulation was running unobstructed. After I
>>> did add the codes I have a number of errors.
>>>
>>> As I did error check, I realised that most of the .xml documents do not
>>> exist anymore.
>>>
>>> Please could anybody check the instructions on the wiki, if they are
>>> up-to-date. And it would be quite useful to have an example code so that
>>> I can compare my and working codes.
>>>
>>> I am using Twog1.
>>>
>>> Thank you.
>>>
>>> Regards,
>>>
>>> Roman
>>>
>>> Bristol Institute of Technology
>>>
>>> University of the West of England
>>>
>>> Aerospace Systems Engineering
>>>
>>> email: address@hidden<mailto:address@hidden>
>>>
>>> Mob.: +44 (0) 7760806643
>>>
>>> *P** **please consider the environment before printing emails.** *
>>>
>>>
>>>
>>> _______________________________________________
>>> Paparazzi-devel mailing list
>>> address@hidden
>>> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel
>>
>>
>> _______________________________________________
>> Paparazzi-devel mailing list
>> address@hidden
>> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel
>>
>
> _______________________________________________
> Paparazzi-devel mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel


_______________________________________________
Paparazzi-devel mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/paparazzi-devel