[Top][All Lists]

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

Re: [Paparazzi-devel] MAVLink / Ivy / ...

From: Oswald Berthold
Subject: Re: [Paparazzi-devel] MAVLink / Ivy / ...
Date: Tue, 06 Sep 2011 10:33:55 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.3 (gnu/linux)


i've been messing with this issue lately as well. we are using our
homebrew (mavlink-based) controller framework and in effect i wanted to
do, among other things, the reverse, that is, use the pprz plotter and
settings tools instead of qgroundcontrol (which is a cpu hog). this
works all quite well.

the main problem for a more comprehensive solution, but this applies to
working with mavlink alone as well, is that there is hardly a canonical
set of messages apart from IMU data, that suits all and everyone. in
that regard, if both systems used an identical message description XML,
that would make things easier.

much left on the system inter-operation side .. (UAVTalk?, OSC, ...)

bst, opt

Chris Gough <address@hidden> writes:

> Hi Jesus,
> I don't think so. Changing paparazzi to use MavLink nativley is a big
> job. I did muck around with an adapter that bridged between an IvyBus
> and MavProxy, translating "identity and location" messages so that I
> could use a paparazzi-based tracking antenna to follow vehicles
> speaking either protocol (and vica versa). I only got as far as a
> proof of concept, enough to satisfy myself that the "translator
> approach" is promising for that limited purpose.
> I'm not sure the translator approach could practically be taken as far
> as using qgroundcontrol with paparazzi (for example).
> Chris Gough
> (also known as Rufus)
> On Wed, Jul 20, 2011 at 9:34 PM, Jesus Martin Sanchez <address@hidden> wrote:
>> Hello:
>>   Anybody are using MAVLink with paparazzi? Rufus, if I´m not wrong you are
>> working about this, isn´t it?
>>   Thanks
>>   Jesus
>> _______________________________________________
>> Paparazzi-devel mailing list
>> address@hidden

Sent from my fingertip ...

reply via email to

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