paparazzi-devel
[Top][All Lists]
Advanced

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

RE: [Paparazzi-devel] Possible FTDI Fixes


From: Mohammed Abukhalid
Subject: RE: [Paparazzi-devel] Possible FTDI Fixes
Date: Sun, 10 Jan 2010 18:16:53 -0500

Well the simulations seem to be running without any errors (Still trying to make sense of how it all fits together) so I think its ok. Thanks again for all ur help Felix

> Date: Mon, 11 Jan 2010 00:14:17 +0100
> Subject: Re: [Paparazzi-devel] Possible FTDI Fixes
> From: address@hidden
> To: address@hidden
>
> Hi Mohammed,
>
> seems like there is no maintainer mode (and not needed), not sure what
> it was in the first place. Maybe Antoine can clear this point up?
>
> Felix
>
> On Sun, Jan 10, 2010 at 12:49 AM, Mohammed Abukhalid
> <address@hidden> wrote:
> > Thank you. It now compiles successfully!!! Ok just 2 things I would like to
> > verify before moving forward, as it looks like everything is functional and
> > configured properly.
> >
> > When I installed JSBSim, i was unable to enable maintainer-mode (also
> > compile warnings but thats not a big deal as compile warnings seem to work
> > fine) when compiling as it is not an option in the current version of JSBSim
> > as far as i can see... what is this mode supposed to be used for?  Is the
> > reason it is not enabled that it is by default now?
> >
> > Also, I am not sure if this is a potential problem, but Im seeing the
> > following warnings while compiling the aircraft (make AIRCRAFT=BOOZ2_A1
> > clean_ac sim):
> > /opt/jsbsim/include/JSBSim/simgear/xml/easyxml.hxx:249: warning: unused
> > parameter ‘name’
> > /opt/jsbsim/include/JSBSim/simgear/xml/easyxml.hxx:249: warning: unused
> > parameter ‘atts’
> > /opt/jsbsim/include/JSBSim/simgear/xml/easyxml.hxx:258: warning: unused
> > parameter ‘name’
> > /opt/jsbsim/include/JSBSim/simgear/xml/easyxml.hxx:273: warning: unused
> > parameter ‘s’
> > /opt/jsbsim/include/JSBSim/simgear/xml/easyxml.hxx:273: warning: unused
> > parameter ‘length’
> > /opt/jsbsim/include/JSBSim/simgear/xml/easyxml.hxx:288: warning: unused
> > parameter ‘target’
> > /opt/jsbsim/include/JSBSim/simgear/xml/easyxml.hxx:288: warning: unused
> > parameter ‘data’
> > /opt/jsbsim/include/JSBSim/simgear/xml/easyxml.hxx:301: warning: unused
> > parameter ‘message’
> > /opt/jsbsim/include/JSBSim/simgear/xml/easyxml.hxx:301: warning: unused
> > parameter ‘line’
> > /opt/jsbsim/include/JSBSim/simgear/xml/easyxml.hxx:301: warning: unused
> > parameter ‘column’
> >
> > Thanks again for all your help!
> >
> >
> >> Date: Fri, 8 Jan 2010 20:32:28 +0100
> >> Subject: Re: [Paparazzi-devel] Possible FTDI Fixes
> >> From: address@hidden
> >> To: address@hidden
> >>
> >> Hi Mohammed,
> >>
> >> I can not reproduce your error, are you running the latest code?
> >>
> >> In order to simulate a booz system you need a couple of config files:
> >> - aircraft model for jsbsim (has to match airframe name):
> >> conf/simulator/jsbsim/aircraft/BOOZ2_A1.xml
> >> - sensors parameters: conf/simulator/nps/nps_sensors_params_booz2_a1.h
> >> and the appropriate config in the airframe file. This is only done for
> >> BOOZ2_A1 in the repository.
> >>
> >> But I just fixed another error in the booz simulation regarding gps
> >> position in lat/long....
> >>
> >> Cheers, Felix
> >>
> >> On Fri, Jan 8, 2010 at 3:39 PM, Mohammed Abukhalid
> >> <address@hidden> wrote:
> >> > Hello everyone,
> >> >
> >> > We are trying to get the Booz system running and I ran into a problem
> >> > while
> >> > compiling the simulation for the aircraft. Namely when I type:
> >> > make AIRCRAFT=BOOZ_A1 clean_ac sim
> >> >
> >> >  I get an error saying that functions signal, and raise are not defined
> >> > in
> >> > the scope as well as variables SIGTSTP,SIG_DFL and SIGCONT are not
> >> > defined
> >> > in nps_main. Trying to make sim for BOOZ_A2 fails completely. However
> >> > compiling autopilot (make AIRCRAFT=BOOZ_A1 clean_ac ap) seems to work
> >> > without any issues, although just uploading that without seeing how the
> >> > sim
> >> > runs seems reckless :P Is there a working BOOZ aircraft config in
> >> > paparazzi3
> >> > or should I be examining the previous aircraft config files to write a
> >> > Booz
> >> > one? I noticed that compiling the aircraft simulation for the TJ1
> >> > aircraft
> >> > worked perfectly.
> >> >
> >> > Thanks
> >> > Mohammed
> >> >
> >> >> From: address@hidden
> >> >> To: address@hidden
> >> >> Date: Fri, 8 Jan 2010 11:22:02 +0000
> >> >> Subject: [Paparazzi-devel] Possible FTDI Fixes
> >> >>
> >> >> The latest Karmic updates include kernel 2.6.31-17, which has a whole
> >> >> bunch of FTDI fixes in it. I'm not currently on my paparazzi machine,
> >> >> so can't test, but can someone see if that resolves some of the serial
> >> >> connection problems?
> >> >>
> >> >> Cheers
> >> >> --G
> >> >>
> >> >>
> >> >>
> >> >> _______________________________________________
> >> >> Paparazzi-devel mailing list
> >> >> address@hidden
> >> >> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel
> >> >
> >> > ________________________________
> >> > Say Happy New Year with Messenger for Mobile. See more.
> >> > _______________________________________________
> >> > 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
> >
> > ________________________________
> > Spread the cheer with Messenger for mobile. Learn more.
> > _______________________________________________
> > 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


Windows Live Messenger makes it easier to stay in touch – learn how!

reply via email to

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