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: Felix Ruess
Subject: Re: [Paparazzi-devel] Possible FTDI Fixes
Date: Sat, 9 Jan 2010 17:36:58 +0100

Hi Mohammed,

seems like the signal definitions are not found. I included signal.h
in nps_main.c wich was missing (strangely it still worked for me).
Please do a svn update to get the latest code and let me know if it works.

Cheers, Felix

On Sat, Jan 9, 2010 at 1:54 AM, Mohammed Abukhalid
<address@hidden> wrote:
> Hi Felix,
>
> thanks for taking the time to have a look at this. I have both config files
> and Im running the most recent version (paparazzi3) downloaded from the
> repository last week. When I configured paparazzi I followed the directions
> on http://paparazzi.enac.fr/wiki/Booz. the error to be exact is shown below:
>
> ##################################################
>
>  FLIGHT PLAN: Dummy
>
> ##################################################
> BUILD /home/team28/Programs/paparazzi3/var/BOOZ2_A1/flight_plan.xml
> cd sw/airborne; make PAPARAZZI_SRC=/home/team28/Programs/paparazzi3
> PAPARAZZI_HOME=/home/team28/Programs/paparazzi3 TARGET=sim ARCHI=sim all
> DEPEND /home/team28/Programs/paparazzi3/var/BOOZ2_A1/sim/.depend
> CC
> /home/team28/Programs/paparazzi3/var/BOOZ2_A1/sim//home/team28/Programs/paparazzi3/sw/simulator/nps/nps_main.o
> /home/team28/Programs/paparazzi3/sw/simulator/nps/nps_main.c: In function
> ‘void tstp_hdl(int)’:
> /home/team28/Programs/paparazzi3/sw/simulator/nps/nps_main.c:43: error:
> ‘SIGTSTP’ was not declared in this scope
> /home/team28/Programs/paparazzi3/sw/simulator/nps/nps_main.c:43: error:
> ‘SIG_DFL’ was not declared in this scope
> /home/team28/Programs/paparazzi3/sw/simulator/nps/nps_main.c:43: error:
> ‘signal’ was not declared in this scope
> /home/team28/Programs/paparazzi3/sw/simulator/nps/nps_main.c:44: error:
> ‘raise’ was not declared in this scope
> /home/team28/Programs/paparazzi3/sw/simulator/nps/nps_main.c: In function
> ‘void cont_hdl(int)’:
> /home/team28/Programs/paparazzi3/sw/simulator/nps/nps_main.c:51: error:
> ‘SIGCONT’ was not declared in this scope
> /home/team28/Programs/paparazzi3/sw/simulator/nps/nps_main.c:51: error:
> ‘signal’ was not declared in this scope
> /home/team28/Programs/paparazzi3/sw/simulator/nps/nps_main.c:52: error:
> ‘SIGTSTP’ was not declared in this scope
> /home/team28/Programs/paparazzi3/sw/simulator/nps/nps_main.c: In function
> ‘int main(int, char**)’:
> /home/team28/Programs/paparazzi3/sw/simulator/nps/nps_main.c:66: error:
> ‘SIGCONT’ was not declared in this scope
> /home/team28/Programs/paparazzi3/sw/simulator/nps/nps_main.c:66: error:
> ‘signal’ was not declared in this scope
> /home/team28/Programs/paparazzi3/sw/simulator/nps/nps_main.c:67: error:
> ‘SIGTSTP’ was not declared in this scope
> make[1]: ***
> [/home/team28/Programs/paparazzi3/var/BOOZ2_A1/sim//home/team28/Programs/paparazzi3/sw/simulator/nps/nps_main.o]
> Error 1
> make: *** [sim] Error 2
>
> Hope this helps shed a light on the problem!!
>
>> 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
>
> ________________________________
> _______________________________________________
> 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]