paparazzi-devel
[Top][All Lists]
Advanced

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

Re: [Paparazzi-devel] Thoughts about the GCS


From: Maik Höpfel
Subject: Re: [Paparazzi-devel] Thoughts about the GCS
Date: Thu, 10 Jun 2010 18:30:15 +0200

Hello Marko,

Paparazzi is very modular. As far as I understand things, I think it
would be much easier to write a translator/converter that sits between
the Paparazzi data stream and whatever standards people come up with.
That way, you will be able to do a smooth transition; you can continue
using all Paparazzi tools and still have a working interface to
whatever new standardized GCS comes around.
Regardless, I still applaud the people working to define a common UAV standard.

Regards,
Maik

2010/6/10 Marko Thaler <address@hidden>:
> Hello everybody!
> I have been observing the communication on the development board with
> regards to the future Paparazzi GCS development and the OCaml programming
> language.
> I have my deepest respect for the work Pascal has done on the GCS and
> Paparazzi in general. Now that we have lost him I gradually start to
> comprehend the enormous hole he has left behind and the implications of
> using a programming language for the GCS that is not widely adopted.
> As I understand the basic problem for future Paparazzi GCS development is
> the lack of OCaml programming skills that are present in the community. At
> the same time in the worldwide open source UAV communities there is a
> stronger and stronger desire for defining open standards for UAV <-> GCS
> communication and provide an open GCS development platform.  Is there a
> common solution to both problems?
> I do not know! However, while surfing the internet I came across
> the QGroundControl from the PixHawk team that tries to provide open
> standards and a general UAV GCS (everything written in GPL-ed
> C++ Qt framework). I understand there would be quite a lot of work to
> transition the Paparazzi system to another GCS (reintegrate communication
> protocol, rewrite the generation of control parameters from the airframe
> file, etc.). But maybe in the long run the Paparazzi community and open
> source UAV communities in general could benefit from using a common GCS
> development platform.
> I would love to hear your thoughts and opinions about the future Paparazzi
> GCS development options.
> Thank you and kind regards,
> Marko
>
>
>
>
>
> _______________________________________________
> Paparazzi-devel mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel
>
>



reply via email to

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