From: Filipe Varela
Subject: [Paparazzi-devel] Groundstation development
Date: Wed, 15 Jun 2005 16:29:54 +0100
Hey all
After the wireless question comes the software question. I'm wrapping
up my mission planning code (mac os x, cocoa). It's quite powerful
(visual editing, drag'n drop waypoints, double click to set
attributes - altitude, flight script, etc - can i post screenshots in
this list as attachments?) but i was wondering what would be the best
way to implement it.
The beauty of cocoa is that you can design the object (mission
planning view) model (class) and implement it as a standalone app or
merge it inside an existing app.
Picture this situation. A single groundstation app that displays
state, map, etc. Should people be allowed to edit a mission
(waypoints) DURING autonomous flight? If so, then i can merge the
mission planning app with the telemetry/video app. If not, then it
makes sense to keep'em separated. Of course i could merge them
together and lock the waypoints during flight, but i feel that this
is quite clumsy from the usability point of view.
But picture this, if people are allowed to change waypoints during
flight, how would you go about synching the plane's state with the
map state? How does the plane know which waypoint is next when the
existing waypoints were just replaced.
I assume some of you have already considered these problems and would
appreciate any feedback.
ALSO, is there a paparazzi telemetry/video spec that i can use to
make sure my software can be used with it? I was considering offering
modular support for several UAV implementations.
P.S. - My code is not open yet because i want to make sure it's
usable. It'll be published somewhere, anytime soon.
Thanks for reading,
Filipe
---------- This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
-----------------------------------------
ES Viagens - Consultoria e Servicos, S.A.
DSI
From: antoine . drouin
Subject: Re: [Paparazzi-devel] Groundstation development
Date: Thu, 16 Jun 2005 23:11:27 +0200
User-agent: Internet Messaging Program (IMP) 3.2.5
Hi Filipe
I know nothing about OSX and cocoa. I only use free software.
For now, on paparazzi, missions cannot be changed during flight. One of the
reasons is that missions are not interpreted, but compiled before flight. Our
mission language is described in the following file :
paparazzi2/conf/flight_plans/flight_plan.dtd
and you have several examples in the same directory.
For the telemetry specifications, messages are described in the following file
: paparazzi2/conf/messages.xml
I think that one of the best way to obtain paparazzi interoperability would be
that your sofware communicate with our using the IVY software bus. It's
available from http://www.tls.cena.fr/products/ivy/
Best Regards
Antoine
Selon Filipe Varela :
> Hey all
>
> After the wireless question comes the software question. I'm wrapping
> up my mission planning code (mac os x, cocoa). It's quite powerful
> (visual editing, drag'n drop waypoints, double click to set
> attributes - altitude, flight script, etc - can i post screenshots in
> this list as attachments?) but i was wondering what would be the best
> way to implement it.
>
> The beauty of cocoa is that you can design the object (mission
> planning view) model (class) and implement it as a standalone app or
> merge it inside an existing app.
>
> Picture this situation. A single groundstation app that displays
> state, map, etc. Should people be allowed to edit a mission
> (waypoints) DURING autonomous flight? If so, then i can merge the
> mission planning app with the telemetry/video app. If not, then it
> makes sense to keep'em separated. Of course i could merge them
> together and lock the waypoints during flight, but i feel that this
> is quite clumsy from the usability point of view.
>
> But picture this, if people are allowed to change waypoints during
> flight, how would you go about synching the plane's state with the
> map state? How does the plane know which waypoint is next when the
> existing waypoints were just replaced.
>
> I assume some of you have already considered these problems and would
> appreciate any feedback.
>
> ALSO, is there a paparazzi telemetry/video spec that i can use to
> make sure my software can be used with it? I was considering offering
> modular support for several UAV implementations.
>
> P.S. - My code is not open yet because i want to make sure it's
> usable. It'll be published somewhere, anytime soon.
>
> Thanks for reading,
> Filipe
>
>
>
> ----------
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
> -----------------------------------------
> ES Viagens - Consultoria e Servicos, S.A.
> DSI
>
>
>
> _______________________________________________
> Paparazzi-devel mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel
>
Copyright 2005 http://lists.nongnu.org/mailman/listinfo/paparazzi-devel