paparazzi-devel
[Top][All Lists]
Advanced

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

Re: [Paparazzi-devel] Booz sim: Fatal GCS command errors


From: Stephen L Hulme
Subject: Re: [Paparazzi-devel] Booz sim: Fatal GCS command errors
Date: Mon, 27 Sep 2010 00:14:51 +1300

Hi Felix
 
Thank you for your reply.
 
The boozsim/paparazzi3 version is that taken from the repository and
remains unchanged by me. 
 
The aircraft in the conf.xml file are svn originals.
 
At least I know now to remove them if they offend. 
 
Regards
 
Stephen  
 
On Sun, 26 Sep 2010 11:48:06 +0200, Felix Reuss <address@hidden> wrote:
Hi Stephen,

all airframes listed in your conf.xml have to be valid. So either
delete the offending ones or change them to a valid airframe file.

The GCS is dynamic and can show all aircraft that you defined in the
A/C list in paparazzi center. Upon start it does not know which
aircraft will connect. That is why prior to starting it needs all
airframe and configuration files.

Maybe we should change the behavior of paparazzi center here? Or at
least print a sensible error message!

Cheers, Felix

On Sun, Sep 26, 2010 at 1:51 AM, Stephen L Hulme <address@hidden> wrote:
> Hi Guys and maybe Felix in particular.
>
> I noticed when executing JSBSim commands within the GCS rather than a
> terminal I get the following errors
> Inevitably the "PASettings" window fails to open.
>
> Run '/home/stephen/boozsim/paparazzi3/sw/ground_segment/tmtc/messages '
> Run '/home/stephen/boozsim/paparazzi3/sw/ground_segment/tmtc/settings '
> Run '/home/stephen/boozsim/paparazzi3/sw/ground_segment/tmtc/server '
> Fatal error: exception Failure("File not found:
> /home/stephen/boozsim/paparazzi3/conf/airframes/funjetmm.xml")
> Read Socket : Connection reset by peer
> Read Socket : Connection reset by peer
> Broadcasting on network 127.255.255.255, port 2010
>
> It is the same when I try to execute my built quadrotor airframe (AP) within
> the GCS. The only difference is that I get another airframe.xml cited.
> In this case a 'twinstar.xml. I do expect a fatal exception error when my
> modems are not live but not a call to another irrelevant airframe.
>
> Regards
>
> Stephen
>
> _______________________________________________
> 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]