From MAILER-DAEMON Sun Aug 02 21:46:47 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MXmdT-0001xb-6s for mharc-paparazzi-devel@gnu.org; Sun, 02 Aug 2009 21:46:47 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MXmdQ-0001ur-Gb for paparazzi-devel@nongnu.org; Sun, 02 Aug 2009 21:46:44 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MXmdL-0001qn-TT for paparazzi-devel@nongnu.org; Sun, 02 Aug 2009 21:46:43 -0400 Received: from [199.232.76.173] (port=51110 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MXmdL-0001qk-NU for paparazzi-devel@nongnu.org; Sun, 02 Aug 2009 21:46:39 -0400 Received: from eth2503.sa.adsl.internode.on.net ([150.101.238.198]:49898 helo=loki.acres.com.au) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MXmdK-0007xQ-NZ for paparazzi-devel@nongnu.org; Sun, 02 Aug 2009 21:46:39 -0400 Received: from localhost (localhost [127.0.0.1]) by loki.acres.com.au (Postfix) with ESMTP id B6E99859F for ; Mon, 3 Aug 2009 11:16:33 +0930 (CST) Received: from loki.acres.com.au ([127.0.0.1]) by localhost (loki.acres.com.au [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2HElX+085koH for ; Mon, 3 Aug 2009 11:16:25 +0930 (CST) Received: from [192.0.2.159] (unknown [192.0.2.159]) by loki.acres.com.au (Postfix) with ESMTP id 41159859E for ; Mon, 3 Aug 2009 11:16:25 +0930 (CST) Message-ID: <4A76416F.6030909@acres.com.au> Date: Mon, 03 Aug 2009 11:16:23 +0930 From: Steven Wawryk User-Agent: Thunderbird 2.0.0.22 (X11/20090608) MIME-Version: 1.0 To: paparazzi-devel@nongnu.org Subject: Re: [Paparazzi-devel] fly in the loop References: <4A724D01.6070105@acres.com.au> In-Reply-To: Content-Type: text/plain; charset=Big5 Content-Transfer-Encoding: quoted-printable X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Aug 2009 01:46:45 -0000 What are you trying to achieve with the inner "while"? It seems to me it's now doing nothing and can be removed altogether. Steve =B3=A2 flying pig wrote: > Hi all > > Thanks for the tip, I want to create the loop that aircraft just cont= inue fly in the loop. > > After reading your e-mail that i also found out the stage_time is res= et , so i use =20 > > > > > =20 > > stage_time"/> > > > > then, everything works now. > > > > Thanks > > = Chen > =20 >> Date: Fri, 31 Jul 2009 11:16:41 +0930 >> From: stevenw@acres.com.au >> To: paparazzi-devel@nongnu.org >> Subject: Re: [Paparazzi-devel] fly in the loop >> >> >> I have noticed previously that stage_time is reset to zero every itera= tion of a >> while loop. It works fine with "until=3D" attributes in other element= s or >> "stages", but not while elements. I think this is a bug. >> >> Try another element that has an "until" attribute, like > <=3D stage_time"> >> >> >> =B3=A2 flying pig wrote: >> =20 >>> Hi all >>> >>> I have try to create a loop flight in the basic.xml (from HOME --> = STDBY --->CLIMB ....repeat), i use the following=20 >>> >>> >>> >>> >>> >>> >>> =20 >>> >>> stage_time"/> >>> >>> >>> >>> >>> The problem i have is that once i call the block, it will fly from = HOME --->STDBY ---->CLIMB , but after that it will not do anything until = i call the block again, does anyone one have any idea how to do it right?= =20 >>> >>> I have enclosed my basic2.xml for the flight plan. >>> >>> >>> Thanks >>> >>> = Chen >>> >>> _________________________________________________________________ >>> =BB=B4=C3P=A4=C0=A8=C9 =A1V =A7Q=A5=CE Windows Live =AC=DB=C3=AF=A4=C0= =A8=C9=AC=DB=A4=F9 >>> >>> http://download.live.com/toolbar >>> >>> >>> ---------------------------------------------------------------------= --- >>> >>> _______________________________________________ >>> Paparazzi-devel mailing list >>> Paparazzi-devel@nongnu.org >>> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel >>> =20 >> _______________________________________________ >> Paparazzi-devel mailing list >> Paparazzi-devel@nongnu.org >> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel >> =20 > > _________________________________________________________________ > =A5=CE=B3=A1=B8=A8=AE=E6=A4=C0=A8=C9=B7=D3=A4=F9=A1B=BCv=AD=B5=A1B=BD=EC= =A8=FD=A4p=A4u=A8=E3=A9M=B3=CC=B7R=B2M=B3=E6=A1A=BA=C9=B1=A1=A8q=A5X=A7A=A6= =DB=A4v =A1X Windows Live Spaces > http://home.spaces.live.com/?showUnauth=3D1&lc=3D1028 > =20 > -----------------------------------------------------------------------= - > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > =20 From MAILER-DAEMON Mon Aug 03 02:12:57 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MXqn3-0007ra-Hd for mharc-paparazzi-devel@gnu.org; Mon, 03 Aug 2009 02:12:57 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MXqn1-0007qu-8J for paparazzi-devel@nongnu.org; Mon, 03 Aug 2009 02:12:55 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MXqmw-0007p6-7A for paparazzi-devel@nongnu.org; Mon, 03 Aug 2009 02:12:54 -0400 Received: from [199.232.76.173] (port=53475 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MXqmv-0007oy-Sh for paparazzi-devel@nongnu.org; Mon, 03 Aug 2009 02:12:49 -0400 Received: from smtp6-g21.free.fr ([212.27.42.6]:44453) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MXqmu-0002jz-2M for paparazzi-devel@nongnu.org; Mon, 03 Aug 2009 02:12:48 -0400 Received: from smtp6-g21.free.fr (localhost [127.0.0.1]) by smtp6-g21.free.fr (Postfix) with ESMTP id 21ACAE08067 for ; Mon, 3 Aug 2009 08:12:43 +0200 (CEST) Received: from [192.168.0.10] (uni31-1-82-234-59-180.fbx.proxad.net [82.234.59.180]) by smtp6-g21.free.fr (Postfix) with ESMTP id 2E89DE0808D for ; Mon, 3 Aug 2009 08:12:41 +0200 (CEST) Message-ID: <4A767FD7.1080408@free.fr> Date: Mon, 03 Aug 2009 08:12:39 +0200 From: Pascal Brisset User-Agent: Thunderbird 2.0.0.22 (X11/20090608) MIME-Version: 1.0 To: paparazzi-devel@nongnu.org Subject: Re: [Paparazzi-devel] fly in the loop References: <4A724D01.6070105@acres.com.au> In-Reply-To: <4A724D01.6070105@acres.com.au> Content-Type: text/plain; charset=Big5 Content-Transfer-Encoding: quoted-printable X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 3) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Aug 2009 06:12:55 -0000 Hi, there is a single "stage_time" variable which is reset at the beginning of every stage. Here, there is a hidden empty stage inside the while loop where the variable is reset. It is probably not enough documented. However, what do you expect of doing nothing during 2s ? Except during an initialisation phase (or a perch phase with an heli), on the ground, you probably want to continue to fly ... So the instruction is a good answer --Pascal Steven Wawryk wrote: > I have noticed previously that stage_time is reset to zero every iterat= ion of a > while loop. It works fine with "until=3D" attributes in other elements= or > "stages", but not while elements. I think this is a bug. > > Try another element that has an "until" attribute, like <=3D stage_time"> > > > =B3=A2 flying pig wrote: > =20 >> Hi all >> >> I have try to create a loop flight in the basic.xml (from HOME --> S= TDBY --->CLIMB ....repeat), i use the following=20 >> >> >> >> >> >> >> =20 >> >> stage_time"/> >> >> >> >> >> The problem i have is that once i call the block, it will fly from H= OME --->STDBY ---->CLIMB , but after that it will not do anything until i= call the block again, does anyone one have any idea how to do it right?=20 >> >> I have enclosed my basic2.xml for the flight plan. >> >> >> Thanks >> >> = Chen >> >> _________________________________________________________________ >> =BB=B4=C3P=A4=C0=A8=C9 =A1V =A7Q=A5=CE Windows Live =AC=DB=C3=AF=A4=C0= =A8=C9=AC=DB=A4=F9 >> >> http://download.live.com/toolbar >> >> >> ----------------------------------------------------------------------= -- >> >> _______________________________________________ >> Paparazzi-devel mailing list >> Paparazzi-devel@nongnu.org >> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel >> =20 > > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > =20 From MAILER-DAEMON Mon Aug 03 06:43:32 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MXv0u-00018B-3Z for mharc-paparazzi-devel@gnu.org; Mon, 03 Aug 2009 06:43:32 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MXv0r-000177-M4 for paparazzi-devel@nongnu.org; Mon, 03 Aug 2009 06:43:29 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MXv0n-00016R-0q for paparazzi-devel@nongnu.org; Mon, 03 Aug 2009 06:43:29 -0400 Received: from [199.232.76.173] (port=59547 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MXv0m-00016O-Sk for paparazzi-devel@nongnu.org; Mon, 03 Aug 2009 06:43:24 -0400 Received: from eth2503.sa.adsl.internode.on.net ([150.101.238.198]:55120 helo=loki.acres.com.au) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MXv0l-0005mf-M6 for paparazzi-devel@nongnu.org; Mon, 03 Aug 2009 06:43:24 -0400 Received: from localhost (localhost [127.0.0.1]) by loki.acres.com.au (Postfix) with ESMTP id A5FB9869D for ; Mon, 3 Aug 2009 20:13:23 +0930 (CST) Received: from loki.acres.com.au ([127.0.0.1]) by localhost (loki.acres.com.au [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ng4aTvo+H4u1 for ; Mon, 3 Aug 2009 20:13:17 +0930 (CST) Received: from [192.0.2.159] (unknown [192.0.2.159]) by loki.acres.com.au (Postfix) with ESMTP id A4E87869C for ; Mon, 3 Aug 2009 20:13:17 +0930 (CST) Message-ID: <4A76BF43.6080606@acres.com.au> Date: Mon, 03 Aug 2009 20:13:15 +0930 From: Steven Wawryk User-Agent: Thunderbird 2.0.0.22 (X11/20090608) MIME-Version: 1.0 To: paparazzi-devel@nongnu.org Subject: Re: [Paparazzi-devel] fly in the loop References: <4A724D01.6070105@acres.com.au> <4A767FD7.1080408@free.fr> In-Reply-To: <4A767FD7.1080408@free.fr> Content-Type: text/plain; charset=Big5 Content-Transfer-Encoding: quoted-printable X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Aug 2009 10:43:30 -0000 Hi Pascal, It's not a criticism, it's just a usage that I find more intuitive and re= adable. I agree that it makes no sense during any fixed-wing flying phase. The situations I've encountered where I would have liked it are all before la= unch when it doesn't make sense for a controller to be running. One example was for a delay between control surface position changes duri= ng pre-launch testing where I wanted: and worked around it with: . Another was to speed up GPS settling where I wanted a timed out accuracy = criterion: and worked around with: I personally think that the "while" element is more readable. The use of empty "while" element works when used with block_time (NavBlockTime()) or any other variable for that matter and there are lots= of examples of this in the flight_plan directory, so it can entice the naive= user like me to use stage_time and wonder why it hangs and never gets past tha= t stage (though the flight plan display doesn't actually show that it is hung up = on that stage, so it takes a bit of investigating). Of course, it's not a show-stopper because there is a work around. Steve Pascal Brisset wrote: > Hi, >=20 > there is a single "stage_time" variable which is reset at the beginning > of every stage. Here, there is a hidden empty stage inside the while > loop where the variable is reset. It is probably not enough documented. >=20 > However, what do you expect of doing nothing during 2s ? Except during > an initialisation phase (or a perch phase with an heli), on the ground, > you probably want to continue to fly ... >=20 > So the instruction is a good answer >=20 > --Pascal >=20 > Steven Wawryk wrote: >> I have noticed previously that stage_time is reset to zero every itera= tion of a >> while loop. It works fine with "until=3D" attributes in other element= s or >> "stages", but not while elements. I think this is a bug. >> >> Try another element that has an "until" attribute, like > <=3D stage_time"> >> >> >> =B3=A2 flying pig wrote: >> =20 >>> Hi all >>> >>> I have try to create a loop flight in the basic.xml (from HOME --> = STDBY --->CLIMB ....repeat), i use the following=20 >>> >>> >>> >>> >>> >>> >>> =20 >>> >>> stage_time"/> >>> >>> >>> >>> >>> The problem i have is that once i call the block, it will fly from = HOME --->STDBY ---->CLIMB , but after that it will not do anything until = i call the block again, does anyone one have any idea how to do it right?= =20 >>> >>> I have enclosed my basic2.xml for the flight plan. >>> >>> >>> Thanks >>> >>> = Chen >>> >>> _________________________________________________________________ >>> =BB=B4=C3P=A4=C0=A8=C9 =A1V =A7Q=A5=CE Windows Live =AC=DB=C3=AF=A4=C0= =A8=C9=AC=DB=A4=F9 >>> >>> http://download.live.com/toolbar >>> >>> >>> ---------------------------------------------------------------------= --- >>> >>> _______________________________________________ >>> Paparazzi-devel mailing list >>> Paparazzi-devel@nongnu.org >>> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel >>> =20 >> >> _______________________________________________ >> Paparazzi-devel mailing list >> Paparazzi-devel@nongnu.org >> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel >> =20 >=20 >=20 >=20 > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel From MAILER-DAEMON Mon Aug 03 17:27:18 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MY53s-0004Oz-2w for mharc-paparazzi-devel@gnu.org; Mon, 03 Aug 2009 17:27:17 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MY53m-0004Nd-AE for paparazzi-devel@nongnu.org; Mon, 03 Aug 2009 17:27:10 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MY53h-0004Kz-Fd for paparazzi-devel@nongnu.org; Mon, 03 Aug 2009 17:27:09 -0400 Received: from [199.232.76.173] (port=57117 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MY53f-0004KN-OL for paparazzi-devel@nongnu.org; Mon, 03 Aug 2009 17:27:04 -0400 Received: from smtp6-g21.free.fr ([212.27.42.6]:43496) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MY53e-0006mW-Vs for paparazzi-devel@nongnu.org; Mon, 03 Aug 2009 17:27:03 -0400 Received: from smtp6-g21.free.fr (localhost [127.0.0.1]) by smtp6-g21.free.fr (Postfix) with ESMTP id CE9DEE080B9 for ; Mon, 3 Aug 2009 23:26:59 +0200 (CEST) Received: from [192.168.0.10] (uni31-1-82-234-59-180.fbx.proxad.net [82.234.59.180]) by smtp6-g21.free.fr (Postfix) with ESMTP id C477FE0809F for ; Mon, 3 Aug 2009 23:26:56 +0200 (CEST) Message-ID: <4A77561E.7090307@free.fr> Date: Mon, 03 Aug 2009 23:26:54 +0200 From: Pascal Brisset User-Agent: Thunderbird 2.0.0.22 (X11/20090608) MIME-Version: 1.0 To: paparazzi-devel@nongnu.org Subject: Re: [Paparazzi-devel] fly in the loop References: <4A724D01.6070105@acres.com.au> <4A767FD7.1080408@free.fr> <4A76BF43.6080606@acres.com.au> In-Reply-To: <4A76BF43.6080606@acres.com.au> Content-Type: text/plain; charset=Big5 Content-Transfer-Encoding: quoted-printable X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 3) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Aug 2009 21:27:11 -0000 Hi, we could have a instruction or a new "loop_time" variable. What do you think ? --Pascal Steven Wawryk wrote: > Hi Pascal, > > It's not a criticism, it's just a usage that I find more intuitive and = readable. > > I agree that it makes no sense during any fixed-wing flying phase. The > situations I've encountered where I would have liked it are all before = launch > when it doesn't make sense for a controller to be running. > > One example was for a delay between control surface position changes du= ring > pre-launch testing where I wanted: > > > > and worked around it with: > > until=3D"LessThan(4,stage_time)"/>. > > Another was to speed up GPS settling where I wanted a timed out accurac= y criterion: > > > > and worked around with: > > until=3D"Or(LessThan(gps_Pacc,1000),LessThan(10,stage_time))"/> > > I personally think that the "while" element is more readable. > > The use of empty "while" element works when used with block_time > (NavBlockTime()) or any other variable for that matter and there are lo= ts of > examples of this in the flight_plan directory, so it can entice the nai= ve user > like me to use stage_time and wonder why it hangs and never gets past t= hat stage > (though the flight plan display doesn't actually show that it is hung u= p on that > stage, so it takes a bit of investigating). > > Of course, it's not a show-stopper because there is a work around. > > Steve > > > Pascal Brisset wrote: > =20 >> Hi, >> >> there is a single "stage_time" variable which is reset at the beginnin= g >> of every stage. Here, there is a hidden empty stage inside the while >> loop where the variable is reset. It is probably not enough documented= . >> >> However, what do you expect of doing nothing during 2s ? Except during >> an initialisation phase (or a perch phase with an heli), on the ground= , >> you probably want to continue to fly ... >> >> So the instruction is a good answer >> >> --Pascal >> >> Steven Wawryk wrote: >> =20 >>> I have noticed previously that stage_time is reset to zero every iter= ation of a >>> while loop. It works fine with "until=3D" attributes in other elemen= ts or >>> "stages", but not while elements. I think this is a bug. >>> >>> Try another element that has an "until" attribute, like >> <=3D stage_time"> >>> >>> >>> =B3=A2 flying pig wrote: >>> =20 >>> =20 >>>> Hi all >>>> >>>> I have try to create a loop flight in the basic.xml (from HOME -->= STDBY --->CLIMB ....repeat), i use the following=20 >>>> >>>> >>>> >>>> >>>> >>>> >>>> =20 >>>> >>>> stage_time"/> >>>> >>>> >>>> >>>> >>>> The problem i have is that once i call the block, it will fly from= HOME --->STDBY ---->CLIMB , but after that it will not do anything until= i call the block again, does anyone one have any idea how to do it right= ?=20 >>>> >>>> I have enclosed my basic2.xml for the flight plan. >>>> >>>> >>>> Thanks >>>> >>>> = Chen >>>> >>>> _________________________________________________________________ >>>> =BB=B4=C3P=A4=C0=A8=C9 =A1V =A7Q=A5=CE Windows Live =AC=DB=C3=AF=A4=C0= =A8=C9=AC=DB=A4=F9 >>>> >>>> http://download.live.com/toolbar >>>> >>>> >>>> --------------------------------------------------------------------= ---- >>>> >>>> _______________________________________________ >>>> Paparazzi-devel mailing list >>>> Paparazzi-devel@nongnu.org >>>> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel >>>> =20 >>>> =20 >>> _______________________________________________ >>> Paparazzi-devel mailing list >>> Paparazzi-devel@nongnu.org >>> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel >>> =20 >>> =20 >> >> _______________________________________________ >> Paparazzi-devel mailing list >> Paparazzi-devel@nongnu.org >> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel >> =20 > > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > =20 From MAILER-DAEMON Mon Aug 03 18:53:20 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MY6PA-00038q-6b for mharc-paparazzi-devel@gnu.org; Mon, 03 Aug 2009 18:53:20 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MY6P6-00036V-IE for paparazzi-devel@nongnu.org; Mon, 03 Aug 2009 18:53:16 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MY6P1-00033P-TD for paparazzi-devel@nongnu.org; Mon, 03 Aug 2009 18:53:15 -0400 Received: from [199.232.76.173] (port=39510 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MY6P0-000338-3z for paparazzi-devel@nongnu.org; Mon, 03 Aug 2009 18:53:10 -0400 Received: from smtp6-g21.free.fr ([212.27.42.6]:52334) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MY6Oz-0002kc-88 for paparazzi-devel@nongnu.org; Mon, 03 Aug 2009 18:53:09 -0400 Received: from smtp6-g21.free.fr (localhost [127.0.0.1]) by smtp6-g21.free.fr (Postfix) with ESMTP id 05FD1E0808B for ; Tue, 4 Aug 2009 00:53:05 +0200 (CEST) Received: from [192.168.0.10] (uni31-1-82-234-59-180.fbx.proxad.net [82.234.59.180]) by smtp6-g21.free.fr (Postfix) with ESMTP id D56C3E08076 for ; Tue, 4 Aug 2009 00:53:02 +0200 (CEST) Message-ID: <4A776A4C.5060807@free.fr> Date: Tue, 04 Aug 2009 00:53:00 +0200 From: Pascal Brisset User-Agent: Thunderbird 2.0.0.22 (X11/20090608) MIME-Version: 1.0 To: paparazzi-devel@nongnu.org Subject: Re: [Paparazzi-devel] Flight plan blocks and keyboard References: <76911248793382@webmail85.yandex.ru> In-Reply-To: <76911248793382@webmail85.yandex.ru> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 3) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Aug 2009 22:53:17 -0000 Andrew S wrote: > Thanks. > > Is it any way to just increase or decrease value with STEP by keys? > Using left and right arrows, the page keys or the mouse wheel ? > And this feature works incorrectly with more than two keys=values. > Hmm, it _was_ working. I will check --Pascal > Andrew > > 04.07.09, 02:05, "Pascal Brisset" : > > >> Hi, >> key accelerators are now also available for the settings in the GCS: >> >> > > > >> --Pascal >> > > > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > From MAILER-DAEMON Mon Aug 03 22:27:53 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MY9kn-0000TI-1S for mharc-paparazzi-devel@gnu.org; Mon, 03 Aug 2009 22:27:53 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MY9kl-0000SW-9F for paparazzi-devel@nongnu.org; Mon, 03 Aug 2009 22:27:51 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MY9kg-0000PL-LD for paparazzi-devel@nongnu.org; Mon, 03 Aug 2009 22:27:50 -0400 Received: from [199.232.76.173] (port=53706 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MY9kg-0000P0-3I for paparazzi-devel@nongnu.org; Mon, 03 Aug 2009 22:27:46 -0400 Received: from mail-pz0-f196.google.com ([209.85.222.196]:38524) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MY9kf-0002vS-GE for paparazzi-devel@nongnu.org; Mon, 03 Aug 2009 22:27:45 -0400 Received: by pzk34 with SMTP id 34so2714372pzk.4 for ; Mon, 03 Aug 2009 19:27:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type:content-transfer-encoding; bh=Yvv1BwzxhOfWHvqMQ9tsIcZSl/VLKRzVKr4WZRpqAuU=; b=SGKcJGyLbaRQmwZ0TLCAlWg4ktp8Wo2HPkRfd1bKbYCDl1PPuD2WbN4HJZqRTD+SZZ rvFXmQTpMsCtDrNDt8dG22jEYXZEthnSKZzikhpZuWJErsmPziWrpsQ8ucQe3iJVe5xt StMLBCZ6+Tkl4mt621gR8gBHKBobqy2wsF8q8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=K7KtxP/rdCYnW9am8O9qO3y5y3Nok0Gjn1jUzvwtUFCNf9744ODtkV8+UHfFKgvIp6 py7kbEyXmoGjKV/TgMM7C3Sx7MalwKMbMLI2F1z+oS7JEADVlf5vIZ66mppD1XKVO2eA m7ri+wt/U/a9jL/uvuvYYShrRmCJl0qjfdrew= MIME-Version: 1.0 Received: by 10.142.127.7 with SMTP id z7mr406234wfc.315.1249352863847; Mon, 03 Aug 2009 19:27:43 -0700 (PDT) Date: Tue, 4 Aug 2009 12:27:43 +1000 Message-ID: <8a0861de0908031927la57989ahd15044bf6ac0473b@mail.gmail.com> From: Chris Gough To: paparazzi-devel@nongnu.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) Subject: [Paparazzi-devel] bug report? bogus wild altitude changes in simulation X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Aug 2009 02:27:51 -0000 I'm completly green, so please forgive my ignorance (hardware just arrived, ~20 hours reading wiki and playing with the simulator etc.) Something weird is happening with altitude in my simulations, it suddenly leaps into geostationary orbit (33,000 - 38,000 meters), stays at that level for a while, and suddenly jumps down again. It happens repeatedly (during a simulation) and is really freaking out the passengers. I haven't figured out how to reproduce it reliably (yet). It may corelate with: - entering my survey block / leaving standby - switching the "cam footprint" on/off in GCS * I never noticed it before I starting to use SRTM data (DEM), and I have been messing about with waypoint altitudes quite a bit. All my waypoints are under a 100m AGL ceiling, my runway is ~580m above sea level (Canberra, Australia). * this may be an illusion, It's very obvious with the cam footprint on because it suddenly shades the entire city. Is this a known problem, is there some sort of issue tracker I should check before posting to this list? My environment is an old laptop (256Mb RAM), with the XMas Ubuntu image (from the paparazi web site) installed (and subsequently upgraded). The default install is still there but I'm using a relatively recent checkout from SVN. Most of my simulations are basic survey scenarios (launch, climb, standby, survey, approach, land), using an extensively modified version of the versatile.xml flight plan, and modified versions of the funjet.xml and holiday.xml airframe files (working through the docs while running simulations with modified flight plans and airframe files pretty much sums up my experience with paparazzi). Thanks Chris Gough P.S. if anyone could point me at a reference airframe.xml for a Multiplex EasyStar (with or without addition of ailerons), or any rudder/elevator/throttle 3 chanel plane, that would be very interesting :) From MAILER-DAEMON Tue Aug 04 00:10:31 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MYBM6-0001xy-Uq for mharc-paparazzi-devel@gnu.org; Tue, 04 Aug 2009 00:10:30 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MYBM5-0001xO-Bn for paparazzi-devel@nongnu.org; Tue, 04 Aug 2009 00:10:29 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MYBM0-0001vY-8M for paparazzi-devel@nongnu.org; Tue, 04 Aug 2009 00:10:28 -0400 Received: from [199.232.76.173] (port=58514 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MYBLz-0001vT-Uw for paparazzi-devel@nongnu.org; Tue, 04 Aug 2009 00:10:23 -0400 Received: from mxout-07.mxes.net ([216.86.168.182]:49043) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MYBLz-0001TH-K8 for paparazzi-devel@nongnu.org; Tue, 04 Aug 2009 00:10:23 -0400 Received: from [192.168.1.4] (unknown [66.100.224.186]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 86C6722E247 for ; Tue, 4 Aug 2009 00:10:11 -0400 (EDT) Message-ID: <4A77B4A2.1030106@dcarr.org> Date: Mon, 03 Aug 2009 23:10:10 -0500 From: David Carr User-Agent: Thunderbird 2.0.0.22 (X11/20090608) MIME-Version: 1.0 To: paparazzi-devel@nongnu.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-detected-operating-system: by monty-python.gnu.org: FreeBSD 6.x (1) Subject: [Paparazzi-devel] MLX90247 $5 each, LEA-4H $35, LEA-5H $40 X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Aug 2009 04:10:29 -0000 Guys, I've got 17 MLX90247 IR sensors I'd like to get rid of. They are new, never used. $5 each + $2 shipping in the US. I also have 2 LEA-4Hs for $35 and 1 LEA-5H for $40. Same deal as above. -David Carr From MAILER-DAEMON Tue Aug 04 01:02:33 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MYCAT-0003O4-SA for mharc-paparazzi-devel@gnu.org; Tue, 04 Aug 2009 01:02:33 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MYCAS-0003Nz-V7 for paparazzi-devel@nongnu.org; Tue, 04 Aug 2009 01:02:33 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MYCAN-0003Nf-Re for paparazzi-devel@nongnu.org; Tue, 04 Aug 2009 01:02:32 -0400 Received: from [199.232.76.173] (port=44687 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MYCAN-0003Nc-OA for paparazzi-devel@nongnu.org; Tue, 04 Aug 2009 01:02:27 -0400 Received: from forward11.yandex.ru ([95.108.130.93]:52885) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MYCAN-0002DX-3a for paparazzi-devel@nongnu.org; Tue, 04 Aug 2009 01:02:27 -0400 Received: from webmail112.yandex.ru (webmail112.yandex.ru [95.108.130.11]) by forward11.yandex.ru (Yandex) with ESMTP id 9A690F482E4 for ; Tue, 4 Aug 2009 09:02:09 +0400 (MSD) Received: from localhost (localhost.localdomain [127.0.0.1]) by webmail112.yandex.ru (Yandex) with ESMTP id 88C9B4F4001 for ; Tue, 4 Aug 2009 09:02:09 +0400 (MSD) X-Yandex-Spam: 1 X-Yandex-Front: webmail112 X-Yandex-TimeMark: 1249362129 Received: from [195.131.178.181] ([195.131.178.181]) by mail.yandex.ru with HTTP; Tue, 04 Aug 2009 09:02:09 +0400 From: Andrew S To: paparazzi-devel@nongnu.org In-Reply-To: <4A776A4C.5060807@free.fr> References: <76911248793382@webmail85.yandex.ru> <4A776A4C.5060807@free.fr> Subject: Re: [Paparazzi-devel] Flight plan blocks and keyboard MIME-Version: 1.0 Message-Id: <249991249362129@webmail112.yandex.ru> Date: Tue, 04 Aug 2009 09:02:09 +0400 X-Mailer: Yamail [ http://yandex.ru ] 5.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Aug 2009 05:02:33 -0000 04.08.09, 02:53, "Pascal Brisset" : > Andrew S wrote: > > Thanks. > > > > Is it any way to just increase or decrease value with STEP by keys? > > > Using left and right arrows, the page keys or the mouse wheel ? No, with any key assigned for this. For example Or better solution could be (not depends of step) This feature could be excellent solution for payloads drive. > > And this feature works incorrectly with more than two keys=values. > > > Hmm, it _was_ working. I will check Maybe it depends on hardware? Andrew From MAILER-DAEMON Tue Aug 04 01:30:26 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MYCbS-0003Gv-Qj for mharc-paparazzi-devel@gnu.org; Tue, 04 Aug 2009 01:30:26 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MYCbP-0003EA-U4 for paparazzi-devel@nongnu.org; Tue, 04 Aug 2009 01:30:24 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MYCbK-0003Af-TK for paparazzi-devel@nongnu.org; Tue, 04 Aug 2009 01:30:23 -0400 Received: from [199.232.76.173] (port=58702 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MYCbK-0003AP-Nw for paparazzi-devel@nongnu.org; Tue, 04 Aug 2009 01:30:18 -0400 Received: from eth2503.sa.adsl.internode.on.net ([150.101.238.198]:35785 helo=loki.acres.com.au) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MYCbJ-0007Tz-FK for paparazzi-devel@nongnu.org; Tue, 04 Aug 2009 01:30:18 -0400 Received: from localhost (localhost [127.0.0.1]) by loki.acres.com.au (Postfix) with ESMTP id D6BEC88DD for ; Tue, 4 Aug 2009 15:00:15 +0930 (CST) Received: from loki.acres.com.au ([127.0.0.1]) by localhost (loki.acres.com.au [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 15BIjsxeQh0D for ; Tue, 4 Aug 2009 15:00:07 +0930 (CST) Received: from [192.0.2.159] (unknown [192.0.2.159]) by loki.acres.com.au (Postfix) with ESMTP id 62DE78893 for ; Tue, 4 Aug 2009 15:00:07 +0930 (CST) Message-ID: <4A77C75C.7090805@acres.com.au> Date: Tue, 04 Aug 2009 15:00:04 +0930 From: Steven Wawryk User-Agent: Thunderbird 2.0.0.22 (X11/20090608) MIME-Version: 1.0 To: paparazzi-devel@nongnu.org Subject: Re: [Paparazzi-devel] fly in the loop References: <4A724D01.6070105@acres.com.au> <4A767FD7.1080408@free.fr> <4A76BF43.6080606@acres.com.au> <4A77561E.7090307@free.fr> In-Reply-To: <4A77561E.7090307@free.fr> Content-Type: text/plain; charset=Big5 Content-Transfer-Encoding: quoted-printable X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Aug 2009 05:30:24 -0000 Hi Pascal, I guess I like to think of the entire statement as= a "stage". But if others like to think of each iteration as a stage, then = I'd be happy with anything that allows a readable construct. Either of your suggestions would make me happy. Prominent warnings about the use of sta= ge_time in while elements are probably needed. Steve Pascal Brisset wrote: > Hi, >=20 > we could have a >=20 > >=20 > instruction or a new "loop_time" variable. What do you think ? >=20 > --Pascal >=20 > Steven Wawryk wrote: >> Hi Pascal, >> >> It's not a criticism, it's just a usage that I find more intuitive and= readable. >> >> I agree that it makes no sense during any fixed-wing flying phase. Th= e >> situations I've encountered where I would have liked it are all before= launch >> when it doesn't make sense for a controller to be running. >> >> One example was for a delay between control surface position changes d= uring >> pre-launch testing where I wanted: >> >> >> >> and worked around it with: >> >> > until=3D"LessThan(4,stage_time)"/>. >> >> Another was to speed up GPS settling where I wanted a timed out accura= cy criterion: >> >> >> >> and worked around with: >> >> > until=3D"Or(LessThan(gps_Pacc,1000),LessThan(10,stage_time))"/> >> >> I personally think that the "while" element is more readable. >> >> The use of empty "while" element works when used with block_time >> (NavBlockTime()) or any other variable for that matter and there are l= ots of >> examples of this in the flight_plan directory, so it can entice the na= ive user >> like me to use stage_time and wonder why it hangs and never gets past = that stage >> (though the flight plan display doesn't actually show that it is hung = up on that >> stage, so it takes a bit of investigating). >> >> Of course, it's not a show-stopper because there is a work around. >> >> Steve >> >> >> Pascal Brisset wrote: >> =20 >>> Hi, >>> >>> there is a single "stage_time" variable which is reset at the beginni= ng >>> of every stage. Here, there is a hidden empty stage inside the while >>> loop where the variable is reset. It is probably not enough documente= d. >>> >>> However, what do you expect of doing nothing during 2s ? Except durin= g >>> an initialisation phase (or a perch phase with an heli), on the groun= d, >>> you probably want to continue to fly ... >>> >>> So the instruction is a good answer >>> >>> --Pascal >>> >>> Steven Wawryk wrote: >>> =20 >>>> I have noticed previously that stage_time is reset to zero every ite= ration of a >>>> while loop. It works fine with "until=3D" attributes in other eleme= nts or >>>> "stages", but not while elements. I think this is a bug. >>>> >>>> Try another element that has an "until" attribute, like >>> <=3D stage_time"> >>>> >>>> >>>> =B3=A2 flying pig wrote: >>>> =20 >>>> =20 >>>>> Hi all >>>>> >>>>> I have try to create a loop flight in the basic.xml (from HOME --= > STDBY --->CLIMB ....repeat), i use the following=20 >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> =20 >>>>> >>>>> stage_time"/> >>>>> >>>>> >>>>> >>>>> >>>>> The problem i have is that once i call the block, it will fly fro= m HOME --->STDBY ---->CLIMB , but after that it will not do anything unti= l i call the block again, does anyone one have any idea how to do it righ= t?=20 >>>>> >>>>> I have enclosed my basic2.xml for the flight plan. >>>>> >>>>> >>>>> Thanks >>>>> >>>>> = Chen >>>>> >>>>> _________________________________________________________________ >>>>> =BB=B4=C3P=A4=C0=A8=C9 =A1V =A7Q=A5=CE Windows Live =AC=DB=C3=AF=A4= =C0=A8=C9=AC=DB=A4=F9 >>>>> >>>>> http://download.live.com/toolbar >>>>> >>>>> >>>>> -------------------------------------------------------------------= ----- >>>>> >>>>> _______________________________________________ >>>>> Paparazzi-devel mailing list >>>>> Paparazzi-devel@nongnu.org >>>>> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel >>>>> =20 >>>>> =20 >>>> _______________________________________________ >>>> Paparazzi-devel mailing list >>>> Paparazzi-devel@nongnu.org >>>> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel >>>> =20 >>>> =20 >>> _______________________________________________ >>> Paparazzi-devel mailing list >>> Paparazzi-devel@nongnu.org >>> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel >>> =20 >> >> _______________________________________________ >> Paparazzi-devel mailing list >> Paparazzi-devel@nongnu.org >> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel >> =20 >=20 >=20 >=20 > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel From MAILER-DAEMON Tue Aug 04 14:52:45 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MYP7t-0007LI-KD for mharc-paparazzi-devel@gnu.org; Tue, 04 Aug 2009 14:52:45 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MYP7s-0007LD-2b for paparazzi-devel@nongnu.org; Tue, 04 Aug 2009 14:52:44 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MYP7n-0007L1-Ce for paparazzi-devel@nongnu.org; Tue, 04 Aug 2009 14:52:43 -0400 Received: from [199.232.76.173] (port=33099 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MYP7n-0007Ky-6n for paparazzi-devel@nongnu.org; Tue, 04 Aug 2009 14:52:39 -0400 Received: from smtpoutwbe06.prod.mesa1.secureserver.net ([208.109.78.208]:39319) by monty-python.gnu.org with smtp (Exim 4.60) (envelope-from ) id 1MYP7m-0007do-Dg for paparazzi-devel@nongnu.org; Tue, 04 Aug 2009 14:52:38 -0400 Received: (qmail 18772 invoked from network); 4 Aug 2009 18:52:32 -0000 Received: from unknown (HELO p3plgemwbe01-05.prod.phx3.secureserver.net) (72.167.218.5) by smtpoutwbe06.prod.mesa1.secureserver.net with SMTP; 4 Aug 2009 18:52:31 -0000 Received: (qmail 17037 invoked by uid 99); 4 Aug 2009 18:52:31 -0000 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="utf-8" X-Originating-IP: 199.46.200.232 User-Agent: Web-Based Email 5.1.5 Message-Id: <20090804115231.e412a968f7f3915fb4f3361627e3fef7.d37c81fc99.wbe@email01.secureserver.net> From: akochevar@miraterre.com To: paparazzi-devel@nongnu.org Subject: RE: [Paparazzi-devel] fly in the loop Date: Tue, 04 Aug 2009 11:52:31 -0700 Mime-Version: 1.0 X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.4-2.6 X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Aug 2009 18:52:44 -0000
Pascal,
Just for my own curiousity.  Couldnt the answer to this original = question about looping a block been solved by adding a deroute at the end o= f the last <go> command?
 
AJ
 
-------- Original Message --------
Subject: Re: [Paparazzi-devel= ] fly in the loop
From: Steven Wawryk <stevenw@acres.com.au>
Da= te: Mon, August 03, 2009 10:30 pm
To: paparazzi-devel@nongnu.org

=
Hi Pascal,

I guess I like to think of the entire <while until= =3D"..."/> statement as a
"stage". But if others like to think of eac= h iteration as a stage, then I'd be
happy with anything that allows a re= adable construct. Either of your
suggestions would make me happy. Promin= ent warnings about the use of stage_time
in while elements are probably = needed.

Steve


Pascal Brisset wrote:
> Hi,
> <= BR>> we could have a
>
> <sleep until=3D"condition"/>=
>
> instruction or a new "loop_time" variable. What do you th= ink ?
>
> --Pascal
>
> Steven Wawryk wrote:
&g= t;> Hi Pascal,
>>
>> It's not a criticism, it's just a= usage that I find more intuitive and readable.
>>
>> I a= gree that it makes no sense during any fixed-wing flying phase. The
>= > situations I've encountered where I would have liked it are all before= launch
>> when it doesn't make sense for a controller to be runni= ng.
>>
>> One example was for a delay between control sur= face position changes during
>> pre-launch testing where I wanted:=
>>
>> <while cond=3D"LessThan(stage_time,4)"/>
= >>
>> and worked around it with:
>>
>> <= ;attitude roll=3D"0.0" throttle=3D"0.0" vmode=3D"throttle"
>> unti= l=3D"LessThan(4,stage_time)"/>.
>>
>> Another was to s= peed up GPS settling where I wanted a timed out accuracy criterion:
>= >
>> <while cond=3D"And(LessThan(1000,gps_Pacc),LessThan(sta= ge_time,10))"/>
>>
>> and worked around with:
>&= gt;
>> <attitude roll=3D"0.0" throttle=3D"0.0" vmode=3D"throttl= e"
>> until=3D"Or(LessThan(gps_Pacc,1000),LessThan(10,stage_time))= "/>
>>
>> I personally think that the "while" element = is more readable.
>>
>> The use of empty "while" element = works when used with block_time
>> (NavBlockTime()) or any other v= ariable for that matter and there are lots of
>> examples of this = in the flight_plan directory, so it can entice the naive user
>> l= ike me to use stage_time and wonder why it hangs and never gets past that s= tage
>> (though the flight plan display doesn't actually show that= it is hung up on that
>> stage, so it takes a bit of investigatin= g).
>>
>> Of course, it's not a show-stopper because ther= e is a work around.
>>
>> Steve
>>
>>>> Pascal Brisset wrote:
>>
>>> Hi,
>&g= t;>
>>> there is a single "stage_time" variable which is res= et at the beginning
>>> of every stage. Here, there is a hidden= empty stage inside the while
>>> loop where the variable is re= set. It is probably not enough documented.
>>>
>>> = However, what do you expect of doing nothing during 2s ? Except during
&= gt;>> an initialisation phase (or a perch phase with an heli), on the= ground,
>>> you probably want to continue to fly ...
>&g= t;>
>>> So the <attitude/> instruction is a good answe= r
>>>
>>> --Pascal
>>>
>>> = Steven Wawryk wrote:
>>>
>>>> I have noticed pr= eviously that stage_time is reset to zero every iteration of a
>>&= gt;> while loop. It works fine with "until=3D" attributes in other eleme= nts or
>>>> "stages", but not while elements. I think this i= s a bug.
>>>>
>>>> Try another element that h= as an "until" attribute, like <attitude ... until=3D"2
>>>&g= t; <=3D stage_time">
>>>>
>>>>
>&= gt;>> =E9=83=AD flying pig wrote:
>>>>
>>>= ;>
>>>>> Hi all
>>>>>
>>&g= t;>> I have try to create a loop flight in the basic.xml (from HOME -= -> STDBY --->CLIMB ....repeat), i use the following
>>>&= gt;>
>>>>>
>>>>>
>>>>= > <block name=3D"loop" strip_button=3D"lop">
>>>>&g= t; <while cond=3D"TRUE">
>>>>> <go wp=3D"HOME"/&= gt;
>>>>> <go wp=3D"STDBY"/>
>>>>&g= t; <go wp=3D"CLIMB"/>
>>>>> <while cond=3D"2 >= ; stage_time"/>
>>>>> </while>
>>>&g= t;> </block>
>>>>>
>>>>>
&g= t;>>>> The problem i have is that once i call the block, it wil= l fly from HOME --->STDBY ---->CLIMB , but after that it will not do = anything until i call the block again, does anyone one have any idea how to= do it right?
>>>>>
>>>>> I have enclo= sed my basic2.xml for the flight plan.
>>>>>
>>&= gt;>>
>>>>> Thanks
>>>>>
>&= gt;>>> Chen
>>>>>
>>>>> ______= ___________________________________________________________
>>>= >> =E8=BC=95=E9=AC=86=E5=88=86=E4=BA=AB =E2=80=93 =E5=88=A9=E7=94=A8 = Windows Live =E7=9B=B8=E7=B0=BF=E5=88=86=E4=BA=AB=E7=9B=B8=E7=89=87
>= >>>>
>>>>> ht= tp://download.live.com/toolbar
>>>>>
>>>&= gt;>
>>>>> -------------------------------------------= -----------------------------
>>>>>
>>>>&g= t; _______________________________________________
>>>>> = Paparazzi-devel mailing list
>>>>> Paparazzi-devel@nongnu= .org
>>>>> http://lists.nongnu.org/mailman/listinfo/= paparazzi-devel
>>>>>
>>>>>
&g= t;>>> _______________________________________________
>>&= gt;> Paparazzi-devel mailing list
>>>> Paparazzi-devel@no= ngnu.org
>>>> http://lists.nongnu.org/mailman/listinfo/= paparazzi-devel
>>>>
>>>>
>>&g= t; _______________________________________________
>>> Paparazz= i-devel mailing list
>>> Paparazzi-devel@nongnu.org
>>= > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel
&= gt;>>
>>
>> ______________________________________= _________
>> Paparazzi-devel mailing list
>> Paparazzi-de= vel@nongnu.org
>> http://lists.nongnu.org/mailman/listinfo/pa= parazzi-devel
>>
>
>
>
> _________= ______________________________________
> Paparazzi-devel mailing list=
> Paparazzi-devel@nongnu.org
> http://lists.nongnu.org/ma= ilman/listinfo/paparazzi-devel


_____________________________= __________________
Paparazzi-devel mailing list
Paparazzi-devel@nongn= u.org
http://lists.nongnu.org/mailman/listinfo/paparazzi-devel<= BR>
From MAILER-DAEMON Tue Aug 04 21:34:09 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MYVOL-0002mN-UK for mharc-paparazzi-devel@gnu.org; Tue, 04 Aug 2009 21:34:09 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MYVOK-0002m8-Qa for paparazzi-devel@nongnu.org; Tue, 04 Aug 2009 21:34:08 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MYVOG-0002lw-5h for paparazzi-devel@nongnu.org; Tue, 04 Aug 2009 21:34:08 -0400 Received: from [199.232.76.173] (port=47015 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MYVOG-0002lt-3A for paparazzi-devel@nongnu.org; Tue, 04 Aug 2009 21:34:04 -0400 Received: from eth2503.sa.adsl.internode.on.net ([150.101.238.198]:50687 helo=loki.acres.com.au) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MYVOF-0007cj-3A for paparazzi-devel@nongnu.org; Tue, 04 Aug 2009 21:34:03 -0400 Received: from localhost (localhost [127.0.0.1]) by loki.acres.com.au (Postfix) with ESMTP id CFC418D5C for ; Wed, 5 Aug 2009 11:04:00 +0930 (CST) Received: from loki.acres.com.au ([127.0.0.1]) by localhost (loki.acres.com.au [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4Ufpbp-HCgsV for ; Wed, 5 Aug 2009 11:03:54 +0930 (CST) Received: from [192.0.2.159] (unknown [192.0.2.159]) by loki.acres.com.au (Postfix) with ESMTP id A16A08D13 for ; Wed, 5 Aug 2009 11:03:54 +0930 (CST) Message-ID: <4A78E182.9010405@acres.com.au> Date: Wed, 05 Aug 2009 11:03:54 +0930 From: Steven Wawryk User-Agent: Thunderbird 2.0.0.22 (X11/20090608) MIME-Version: 1.0 To: paparazzi-devel@nongnu.org Subject: Re: [Paparazzi-devel] fly in the loop References: <20090804115231.e412a968f7f3915fb4f3361627e3fef7.d37c81fc99.wbe@email01.secureserver.net> In-Reply-To: <20090804115231.e412a968f7f3915fb4f3361627e3fef7.d37c81fc99.wbe@email01.secureserver.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Aug 2009 01:34:09 -0000 There was no problem with looping. The outer ... loop was= just=20 fine. It was the inner, empty that was the problem, and was=20 unnecessary anyway. akochevar@miraterre.com wrote: > Pascal, > Just for my own curiousity. Couldnt the answer to this original questi= on about=20 > looping a block been solved by adding a deroute at the end of the last = command? > =20 > AJ > =20 >=20 > -------- Original Message -------- > Subject: Re: [Paparazzi-devel] fly in the loop > From: Steven Wawryk > Date: Mon, August 03, 2009 10:30 pm > To: paparazzi-devel@nongnu.org >=20 >=20 > Hi Pascal, >=20 > I guess I like to think of the entire statem= ent as a > "stage". But if others like to think of each iteration as a stage, = then I'd be > happy with anything that allows a readable construct. Either of you= r > suggestions would make me happy. Prominent warnings about the use o= f stage_time > in while elements are probably needed. >=20 > Steve >=20 >=20 > Pascal Brisset wrote: > > Hi, > > > > we could have a > > > > > > > > instruction or a new "loop_time" variable. What do you think ? > > > > --Pascal > > > > Steven Wawryk wrote: > > > Hi Pascal, > > > > > > It's not a criticism, it's just a usage that I find more intuit= ive and > readable. > > > > > > I agree that it makes no sense during any fixed-wing flying pha= se. The > > > situations I've encountered where I would have liked it are all= before launch > > > when it doesn't make sense for a controller to be running. > > > > > > One example was for a delay between control surface position ch= anges during > > > pre-launch testing where I wanted: > > > > > > > > > > > > and worked around it with: > > > > > > > > until=3D"LessThan(4,stage_time)"/>. > > > > > > Another was to speed up GPS settling where I wanted a timed out= accuracy > criterion: > > > > > > > > > > > > and worked around with: > > > > > > > > until=3D"Or(LessThan(gps_Pacc,1000),LessThan(10,stage_time))"/> > > > > > > I personally think that the "while" element is more readable. > > > > > > The use of empty "while" element works when used with block_tim= e > > > (NavBlockTime()) or any other variable for that matter and ther= e are lots of > > > examples of this in the flight_plan directory, so it can entice= the naive > user > > > like me to use stage_time and wonder why it hangs and never get= s past > that stage > > > (though the flight plan display doesn't actually show that it i= s hung up > on that > > > stage, so it takes a bit of investigating). > > > > > > Of course, it's not a show-stopper because there is a work arou= nd. > > > > > > Steve > > > > > > > > > Pascal Brisset wrote: > > > > > >> Hi, > > >> > > >> there is a single "stage_time" variable which is reset at the = beginning > > >> of every stage. Here, there is a hidden empty stage inside the= while > > >> loop where the variable is reset. It is probably not enough do= cumented. > > >> > > >> However, what do you expect of doing nothing during 2s ? Excep= t during > > >> an initialisation phase (or a perch phase with an heli), on th= e ground, > > >> you probably want to continue to fly ... > > >> > > >> So the instruction is a good answer > > >> > > >> --Pascal > > >> > > >> Steven Wawryk wrote: > > >> > > >>> I have noticed previously that stage_time is reset to zero ev= ery > iteration of a > > >>> while loop. It works fine with "until=3D" attributes in other= elements or > > >>> "stages", but not while elements. I think this is a bug. > > >>> > > >>> Try another element that has an "until" attribute, like until=3D"2 > > >>> <=3D stage_time"> > > >>> > > >>> > > >>> =E9=83=AD flying pig wrote: > > >>> > > >>> > > >>>> Hi all > > >>>> > > >>>> I have try to create a loop flight in the basic.xml (from HO= ME --> > STDBY --->CLIMB ....repeat), i use the following > > >>>> > > >>>> > > >>>> > > >>>> > > >>>> > > >>>> > > >>>> > > >>>> > > >>>> stage_time"/> > > >>>> > > >>>> > > >>>> > > >>>> > > >>>> The problem i have is that once i call the block, it will fl= y from > HOME --->STDBY ---->CLIMB , but after that it will not do anything = until i > call the block again, does anyone one have any idea how to do it ri= ght? > > >>>> > > >>>> I have enclosed my basic2.xml for the flight plan. > > >>>> > > >>>> > > >>>> Thanks > > >>>> > > >>>> Chen > > >>>> > > >>>> ____________________________________________________________= _____ > > >>>> =E8=BC=95=E9=AC=86=E5=88=86=E4=BA=AB =E2=80=93 =E5=88=A9=E7=94= =A8 Windows Live =E7=9B=B8=E7=B0=BF=E5=88=86=E4=BA=AB=E7=9B=B8=E7=89=87 > > >>>> > > >>>> http://download.live.com/toolbar > > >>>> > > >>>> > > >>>> ------------------------------------------------------------= ------------ > > >>>> > > >>>> _______________________________________________ > > >>>> Paparazzi-devel mailing list > > >>>> Paparazzi-devel@nongnu.org > > >>>> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > > >>>> > > >>>> > > >>> _______________________________________________ > > >>> Paparazzi-devel mailing list > > >>> Paparazzi-devel@nongnu.org > > >>> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > > >>> > > >>> > > >> _______________________________________________ > > >> Paparazzi-devel mailing list > > >> Paparazzi-devel@nongnu.org > > >> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > > >> > > > > > > _______________________________________________ > > > Paparazzi-devel mailing list > > > Paparazzi-devel@nongnu.org > > > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > > > > > > > > > > > _______________________________________________ > > Paparazzi-devel mailing list > > Paparazzi-devel@nongnu.org > > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel >=20 >=20 > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel >=20 >=20 > -----------------------------------------------------------------------= - >=20 > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel From MAILER-DAEMON Tue Aug 04 23:36:42 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MYXIw-00030J-0i for mharc-paparazzi-devel@gnu.org; Tue, 04 Aug 2009 23:36:42 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MYXIu-0002ze-MF for paparazzi-devel@nongnu.org; Tue, 04 Aug 2009 23:36:40 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MYXIr-0002yo-LB for paparazzi-devel@nongnu.org; Tue, 04 Aug 2009 23:36:40 -0400 Received: from [199.232.76.173] (port=36215 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MYXIr-0002yd-Fb for paparazzi-devel@nongnu.org; Tue, 04 Aug 2009 23:36:37 -0400 Received: from smtpoutwbe11.prod.mesa1.secureserver.net ([208.109.78.27]:60773) by monty-python.gnu.org with smtp (Exim 4.60) (envelope-from ) id 1MYXIq-0005Ir-0G for paparazzi-devel@nongnu.org; Tue, 04 Aug 2009 23:36:36 -0400 Received: (qmail 7706 invoked from network); 5 Aug 2009 03:36:34 -0000 Received: from unknown (HELO p3plgemwbe01-03.prod.phx3.secureserver.net) (72.167.218.3) by smtpoutwbe11.prod.mesa1.secureserver.net with SMTP; 5 Aug 2009 03:36:33 -0000 Received: (qmail 3859 invoked by uid 99); 5 Aug 2009 03:36:33 -0000 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="utf-8" X-Originating-IP: 70.176.119.64 User-Agent: Web-Based Email 5.1.5 Message-Id: <20090804203633.e412a968f7f3915fb4f3361627e3fef7.47f7c2e78b.wbe@email01.secureserver.net> From: akochevar@miraterre.com To: paparazzi-devel@nongnu.org Subject: RE: [Paparazzi-devel] fly in the loop Date: Tue, 04 Aug 2009 20:36:33 -0700 Mime-Version: 1.0 X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.4-2.6 X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Aug 2009 03:36:41 -0000 I was just simply stating that I believe a simple solution would also = have been to add a <deroute block=3D"block_name"/> after the last <= ;go> line.  Its nice to give people options.  I never said the= re was anything wrong with it.

AJ

-------- Original Message --------
Subject: Re: [Paparazzi-devel] fly in the loop
From: Steven Wawryk <stevenw@acres.com.au>
Date: Tue, August 04, 2009 6:33 pm
To: paparazzi-devel@nongnu.org


There was no problem with looping. The outer <while>...</while>= ; loop was just
fine. It was the inner, empty <while.../>that was the problem, and w= as
unnecessary anyway.


akochevar@miraterre.com wrote:
> Pascal,
> Just for my own curiousity. Couldnt the answer to this original quest= ion about
> looping a block been solved by adding a deroute at the end of the last= <go> command?
>
> AJ
>
>
> -------- Original Message --------
> Subject: Re: [Paparazzi-devel] fly in the loop
> From: Steven Wawryk <stevenw@acres.com.au>
> Date: Mon, August 03, 2009 10:30 pm
> To: paparazzi-devel@nongnu.org
>
>
> Hi Pascal,
>
> I guess I like to think of the entire <while until=3D"..."/>= statement as a
> "stage". But if others like to think of each iteration as a stage,= then I'd be
> happy with anything that allows a readable construct. Either of yo= ur
> suggestions would make me happy. Prominent warnings about the use = of stage_time
> in while elements are probably needed.
>
> Steve
>
>
> Pascal Brisset wrote:
> > Hi,
> >
> > we could have a
> >
> > <sleep until=3D"condition"/>
> >
> > instruction or a new "loop_time" variable. What do you think= ?
> >
> > --Pascal
> >
> > Steven Wawryk wrote:
> > > Hi Pascal,
> > >
> > > It's not a criticism, it's just a usage that I find more= intuitive and
> readable.
> > >
> > > I agree that it makes no sense during any fixed-wing fly= ing phase. The
> > > situations I've encountered where I would have liked it = are all before launch
> > > when it doesn't make sense for a controller to be runnin= g.
> > >
> > > One example was for a delay between control surface posi= tion changes during
> > > pre-launch testing where I wanted:
> > >
> > > <while cond=3D"LessThan(stage_time,4)"/>
> > >
> > > and worked around it with:
> > >
> > > <attitude roll=3D"0.0" throttle=3D"0.0" vmode=3D"thro= ttle"
> > > until=3D"LessThan(4,stage_time)"/>.
> > >
> > > Another was to speed up GPS settling where I wanted a ti= med out accuracy
> criterion:
> > >
> > > <while cond=3D"And(LessThan(1000,gps_Pacc),LessThan(s= tage_time,10))"/>
> > >
> > > and worked around with:
> > >
> > > <attitude roll=3D"0.0" throttle=3D"0.0" vmode=3D"thro= ttle"
> > > until=3D"Or(LessThan(gps_Pacc,1000),LessThan(10,stage_ti= me))"/>
> > >
> > > I personally think that the "while" element is more read= able.
> > >
> > > The use of empty "while" element works when used with bl= ock_time
> > > (NavBlockTime()) or any other variable for that matter a= nd there are lots of
> > > examples of this in the flight_plan directory, so it can= entice the naive
> user
> > > like me to use stage_time and wonder why it hangs and ne= ver gets past
> that stage
> > > (though the flight plan display doesn't actually show th= at it is hung up
> on that
> > > stage, so it takes a bit of investigating).
> > >
> > > Of course, it's not a show-stopper because there is a wo= rk around.
> > >
> > > Steve
> > >
> > >
> > > Pascal Brisset wrote:
> > >
> > >> Hi,
> > >>
> > >> there is a single "stage_time" variable which is res= et at the beginning
> > >> of every stage. Here, there is a hidden empty stage = inside the while
> > >> loop where the variable is reset. It is probably not= enough documented.
> > >>
> > >> However, what do you expect of doing nothing during = 2s ? Except during
> > >> an initialisation phase (or a perch phase with an he= li), on the ground,
> > >> you probably want to continue to fly ...
> > >>
> > >> So the <attitude/> instruction is a good answe= r
> > >>
> > >> --Pascal
> > >>
> > >> Steven Wawryk wrote:
> > >>
> > >>> I have noticed previously that stage_time is res= et to zero every
> iteration of a
> > >>> while loop. It works fine with "until=3D" attrib= utes in other elements or
> > >>> "stages", but not while elements. I think this i= s a bug.
> > >>>
> > >>> Try another element that has an "until" attribut= e, like <attitude ...
> until=3D"2
> > >>> <=3D stage_time">
> > >>>
> > >>>
> > >>> =E9=83=AD flying pig wrote:
> > >>>
> > >>>
> > >>>> Hi all
> > >>>>
> > >>>> I have try to create a loop flight in the ba= sic.xml (from HOME -->
> STDBY --->CLIMB ....repeat), i use the following
> > >>>>
> > >>>>
> > >>>>
> > >>>> <block name=3D"loop" strip_button=3D"lop"= >
> > >>>> <while cond=3D"TRUE">
> > >>>> <go wp=3D"HOME"/>
> > >>>> <go wp=3D"STDBY"/>
> > >>>> <go wp=3D"CLIMB"/>
> > >>>> <while cond=3D"2 > stage_time"/> > > >>>> </while>
> > >>>> </block>
> > >>>>
> > >>>>
> > >>>> The problem i have is that once i call the b= lock, it will fly from
> HOME --->STDBY ---->CLIMB , but after that it will not do an= ything until i
> call the block again, does anyone one have any idea how to do it r= ight?
> > >>>>
> > >>>> I have enclosed my basic2.xml for the flight= plan.
> > >>>>
> > >>>>
> > >>>> Thanks
> > >>>>
> > >>>> Chen
> > >>>>
> > >>>> ____________________________________________= _____________________
> > >>>> =E8=BC=95=E9=AC=86=E5=88=86=E4=BA=AB =E2=80= =93 =E5=88=A9=E7=94=A8 Windows Live =E7=9B=B8=E7=B0=BF=E5=88=86=E4=BA=AB=E7= =9B=B8=E7=89=87
> > >>>>
> > >>>> http://dow= nload.live.com/toolbar
> > >>>>
> > >>>>
> > >>>> --------------------------------------------= ----------------------------
> > >>>>
> > >>>> ____________________________________________= ___
> > >>>> Paparazzi-devel mailing list
> > >>>> Paparazzi-devel@nongnu.org
> > >>>> http://lists.nongnu.org/mailman/listi= nfo/paparazzi-devel
> > >>>>
> > >>>>
> > >>> _______________________________________________<= br> > > >>> Paparazzi-devel mailing list
> > >>> Paparazzi-devel@nongnu.org
> > >>> http://lists.nongnu.org/mailman/listinfo/= paparazzi-devel
> > >>>
> > >>>
> > >> _______________________________________________
> > >> Paparazzi-devel mailing list
> > >> Paparazzi-devel@nongnu.org
> > >> http://lists.nongnu.org/mailman/listinfo/papa= razzi-devel
> > >>
> > >
> > > _______________________________________________
> > > Paparazzi-devel mailing list
> > > Paparazzi-devel@nongnu.org
> > > http://lists.nongnu.org/mailman/listinfo/paparazz= i-devel
> > >
> >
> >
> >
> > _______________________________________________
> > Paparazzi-devel mailing list
> > Paparazzi-devel@nongnu.org
> > http://lists.nongnu.org/mailman/listinfo/paparazzi-de= vel
>
>
> _______________________________________________
> Paparazzi-devel mailing list
> Paparazzi-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel
>
>
> ----------------------------------------------------------------------= --
>
> _______________________________________________
> Paparazzi-devel mailing list
> Paparazzi-devel@nongnu.org
>
http://lists.nongnu.org/mailman/listinfo/paparazzi-devel

_______________________________________________
Paparazzi-devel mailing list
Paparazzi-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/paparazzi-devel
From MAILER-DAEMON Wed Aug 05 04:05:00 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MYbUa-0004NZ-AF for mharc-paparazzi-devel@gnu.org; Wed, 05 Aug 2009 04:05:00 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MYbUY-0004NH-9v for paparazzi-devel@nongnu.org; Wed, 05 Aug 2009 04:04:58 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MYbUT-0004Mj-J2 for paparazzi-devel@nongnu.org; Wed, 05 Aug 2009 04:04:57 -0400 Received: from [199.232.76.173] (port=55279 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MYbUT-0004Mf-FJ for paparazzi-devel@nongnu.org; Wed, 05 Aug 2009 04:04:53 -0400 Received: from mail-fx0-f207.google.com ([209.85.220.207]:36396) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MYbUS-0006ta-TS for paparazzi-devel@nongnu.org; Wed, 05 Aug 2009 04:04:53 -0400 Received: by fxm3 with SMTP id 3so765553fxm.8 for ; Wed, 05 Aug 2009 01:04:48 -0700 (PDT) Received: by 10.103.251.20 with SMTP id d20mr4739667mus.42.1249459488702; Wed, 05 Aug 2009 01:04:48 -0700 (PDT) Received: from server ([41.182.152.246]) by mx.google.com with ESMTPS id e9sm43426053muf.2.2009.08.05.01.04.47 (version=SSLv3 cipher=RC4-MD5); Wed, 05 Aug 2009 01:04:48 -0700 (PDT) From: "gisela.noci" To: Date: Wed, 5 Aug 2009 10:04:48 +0200 Message-ID: <50267EEE11C3460883A3943E45D600DD@server> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_00DB_01CA15B4.2DAA1BE0" X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 Thread-Index: AcoVoyr1/GQTcPZ8RA+hnHMKfKf4BA== X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) Subject: [Paparazzi-devel] Auto Take Off / Auto Land X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Aug 2009 08:04:58 -0000 This is a multi-part message in MIME format. ------=_NextPart_000_00DB_01CA15B4.2DAA1BE0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Does the Paparazzi Software manage either Auto Take Off or Auto Land or both? If so, where can I find out more about the rationale behind these functions? Gisela Noci ------=_NextPart_000_00DB_01CA15B4.2DAA1BE0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Does the Paparazzi Software manage either Auto Take = Off or Auto = Land or both? If so, where can I find out more about the rationale behind = these functions?

Gisela Noci

------=_NextPart_000_00DB_01CA15B4.2DAA1BE0-- From MAILER-DAEMON Wed Aug 05 05:12:06 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MYcXW-0000Uy-Aq for mharc-paparazzi-devel@gnu.org; Wed, 05 Aug 2009 05:12:06 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MYcXU-0000Us-0l for paparazzi-devel@nongnu.org; Wed, 05 Aug 2009 05:12:04 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MYcXP-0000RE-8L for paparazzi-devel@nongnu.org; Wed, 05 Aug 2009 05:12:03 -0400 Received: from [199.232.76.173] (port=33470 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MYcXP-0000R9-0C for paparazzi-devel@nongnu.org; Wed, 05 Aug 2009 05:11:59 -0400 Received: from mail-gx0-f220.google.com ([209.85.217.220]:36618) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MYcXO-0000o6-PF for paparazzi-devel@nongnu.org; Wed, 05 Aug 2009 05:11:58 -0400 Received: by gxk20 with SMTP id 20so19563953gxk.10 for ; Wed, 05 Aug 2009 02:11:57 -0700 (PDT) MIME-Version: 1.0 Sender: maik@zackbumm.biz Received: by 10.90.79.4 with SMTP id c4mr3758647agb.21.1249463516106; Wed, 05 Aug 2009 02:11:56 -0700 (PDT) In-Reply-To: <50267EEE11C3460883A3943E45D600DD@server> References: <50267EEE11C3460883A3943E45D600DD@server> From: =?UTF-8?B?TWFpayBIw7ZwZmVs?= Date: Wed, 5 Aug 2009 11:11:36 +0200 X-Google-Sender-Auth: 3b57ea5e689776bc Message-ID: Subject: Re: [Paparazzi-devel] Auto Take Off / Auto Land To: paparazzi-devel@nongnu.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Aug 2009 09:12:04 -0000 As far as I know, Paparazzi can do both. Check out the simulation if you want to get a closer understanding on how things are working. If I remember right, for landing, it just does circles until it reaches a certain height, and then the engine power's reduced and the plane slowly descends. I don't know about details though. I have the feeling that is not used too much because of safety concerns. Regards, Maik 2009/8/5 gisela.noci : > Does the Paparazzi Software manage either Auto Take Off or Auto Land or > both? If so, where can I find out more about the rationale behind these > functions? > > Gisela Noci > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > > From MAILER-DAEMON Wed Aug 05 10:51:24 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MYhps-0007RY-EU for mharc-paparazzi-devel@gnu.org; Wed, 05 Aug 2009 10:51:24 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MYhpq-0007NT-Da for paparazzi-devel@nongnu.org; Wed, 05 Aug 2009 10:51:22 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MYhpl-0007Gq-Mh for paparazzi-devel@nongnu.org; Wed, 05 Aug 2009 10:51:22 -0400 Received: from [199.232.76.173] (port=57643 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MYhpl-0007Gn-Ju for paparazzi-devel@nongnu.org; Wed, 05 Aug 2009 10:51:17 -0400 Received: from basicbox10.server-home.net ([195.137.212.35]:52014) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MYhpk-0006fR-Uh for paparazzi-devel@nongnu.org; Wed, 05 Aug 2009 10:51:17 -0400 Received: by basicbox10.server-home.net (Postfix, from userid 1141) id EE889C84FB4; Wed, 5 Aug 2009 16:51:13 +0200 (CEST) To: paparazzi-devel@nongnu.org From: martin@pfump.org X-Priority: 3 Importance: Normal X-MSMail-Priority: Normal X-MimeOLE: Produced by Confixx WebMail X-Mailer: Confixx WebMail (like SquirrelMail) Cc: MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <20090805145113.EE889C84FB4@basicbox10.server-home.net> Date: Wed, 5 Aug 2009 16:51:13 +0200 (CEST) X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 3) Subject: [Paparazzi-devel] svn update, changed gps message X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Aug 2009 14:51:22 -0000 Hi, there is a new field "week" added to the gps message so that data logged to an SD card on-board can be reconstructed to the correct time in post processing. All files using gps (ubx, xsens, sim, jsbsim, ...) are adapted but you might want to check. You have to do a 'make' in the main Paparazzi directory if you update svn in any case. Martin From MAILER-DAEMON Wed Aug 05 11:25:33 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MYiMv-0001UU-3j for mharc-paparazzi-devel@gnu.org; Wed, 05 Aug 2009 11:25:33 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MYiMu-0001TA-1b for paparazzi-devel@nongnu.org; Wed, 05 Aug 2009 11:25:32 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MYiMp-0001Mg-Bd for paparazzi-devel@nongnu.org; Wed, 05 Aug 2009 11:25:31 -0400 Received: from [199.232.76.173] (port=40473 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MYiMp-0001MP-1d for paparazzi-devel@nongnu.org; Wed, 05 Aug 2009 11:25:27 -0400 Received: from imss-1.enac.fr ([195.220.159.36]:41835) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MYiMo-0003mC-JX for paparazzi-devel@nongnu.org; Wed, 05 Aug 2009 11:25:26 -0400 Received: from mauve.recherche.enac.fr (imss-1.imss.interne.enac [127.0.0.1]) by imss-1.enac.fr (Postfix) with ESMTP id D113C18B3A5 for ; Wed, 5 Aug 2009 17:25:11 +0200 (CEST) Received: from [10.31.1.82] (sepia.recherche.enac.fr [10.31.1.82])by mauve.recherche.enac.fr (Postfix) with ESMTP id A4D132FA822for ; Wed, 5 Aug 2009 17:25:11 +0200 (CEST) Message-ID: <4A79A457.6080801@free.fr> Date: Wed, 05 Aug 2009 17:25:11 +0200 From: Pascal Brisset User-Agent: Mozilla-Thunderbird 2.0.0.22 (X11/20090706) MIME-Version: 1.0 To: paparazzi-devel@nongnu.org Subject: Re: [Paparazzi-devel] Auto Take Off / Auto Land References: <50267EEE11C3460883A3943E45D600DD@server> In-Reply-To: <50267EEE11C3460883A3943E45D600DD@server> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-imss-version: 2.5 X-imss-result: Passed X-imss-scores: Clean:37.54198 C:22 M:1 S:5 R:5 X-imss-settings: Baseline:1 C:1 M:1 S:1 R:1 (0.0000 0.0000) X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.4-2.6 X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Aug 2009 15:25:32 -0000 Hi, it's partially described in http://paparazzi.enac.fr/wiki_images/Users_manual.pdf (link from the wiki) --Pascal gisela.noci wrote: > > Does the Paparazzi Software manage either Auto Take Off or Auto Land > or both? If so, where can I find out more about the rationale behind > these functions? > > Gisela Noci > > ------------------------------------------------------------------------ > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > From MAILER-DAEMON Wed Aug 05 11:27:49 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MYiP7-0002Hg-N8 for mharc-paparazzi-devel@gnu.org; Wed, 05 Aug 2009 11:27:49 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MYiP5-0002Gt-QJ for paparazzi-devel@nongnu.org; Wed, 05 Aug 2009 11:27:47 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MYiP1-0002E9-3J for paparazzi-devel@nongnu.org; Wed, 05 Aug 2009 11:27:47 -0400 Received: from [199.232.76.173] (port=32775 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MYiP1-0002Dx-08 for paparazzi-devel@nongnu.org; Wed, 05 Aug 2009 11:27:43 -0400 Received: from imss-1.enac.fr ([195.220.159.36]:41842) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MYiOz-0004A0-Sx for paparazzi-devel@nongnu.org; Wed, 05 Aug 2009 11:27:42 -0400 Received: from mauve.recherche.enac.fr (imss-1.imss.interne.enac [127.0.0.1]) by imss-1.enac.fr (Postfix) with ESMTP id 097F718B3A5 for ; Wed, 5 Aug 2009 17:27:41 +0200 (CEST) Received: from [10.31.1.82] (sepia.recherche.enac.fr [10.31.1.82])by mauve.recherche.enac.fr (Postfix) with ESMTP id DE4552FA822for ; Wed, 5 Aug 2009 17:27:40 +0200 (CEST) Message-ID: <4A79A4EC.1090308@free.fr> Date: Wed, 05 Aug 2009 17:27:40 +0200 From: Pascal Brisset User-Agent: Mozilla-Thunderbird 2.0.0.22 (X11/20090706) MIME-Version: 1.0 To: paparazzi-devel@nongnu.org Subject: Re: [Paparazzi-devel] Auto Take Off / Auto Land References: <50267EEE11C3460883A3943E45D600DD@server> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed X-imss-version: 2.5 X-imss-result: Passed X-imss-scores: Clean:45.26306 C:21 M:2 S:5 R:5 X-imss-settings: Baseline:1 C:1 M:1 S:1 R:1 (0.0000 0.0000) Content-Transfer-Encoding: quoted-printable X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.4-2.6 X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Aug 2009 15:27:48 -0000 Maik H=C3=B6pfel wrote: > As far as I know, Paparazzi can do both. Check out the simulation if > you want to get a closer understanding on how things are working. If I > remember right, for landing, it just does circles until it reaches a > certain height, and then the engine power's reduced and the plane > slowly descends. I don't know about details though. I have the feeling > that is not used too much because of safety concerns. > =20 When we delivered the system in 2007 to non-RC people, it was used=20 every time, for safety concerns :-) --Pascal > Regards, > Maik > > 2009/8/5 gisela.noci : > =20 >> Does the Paparazzi Software manage either Auto Take Off or Auto Land o= r >> both? If so, where can I find out more about the rationale behind thes= e >> functions? >> >> Gisela Noci >> >> _______________________________________________ >> Paparazzi-devel mailing list >> Paparazzi-devel@nongnu.org >> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel >> >> >> =20 > > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > =20 From MAILER-DAEMON Wed Aug 05 17:41:25 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MYoEf-00069T-Pa for mharc-paparazzi-devel@gnu.org; Wed, 05 Aug 2009 17:41:25 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MYoEd-00068R-Qd for paparazzi-devel@nongnu.org; Wed, 05 Aug 2009 17:41:23 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MYoEZ-00066T-0V for paparazzi-devel@nongnu.org; Wed, 05 Aug 2009 17:41:23 -0400 Received: from [199.232.76.173] (port=58855 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MYoEY-00066O-P1 for paparazzi-devel@nongnu.org; Wed, 05 Aug 2009 17:41:18 -0400 Received: from mail.gmx.net ([213.165.64.20]:52437) by monty-python.gnu.org with smtp (Exim 4.60) (envelope-from ) id 1MYoEY-0005XM-5Z for paparazzi-devel@nongnu.org; Wed, 05 Aug 2009 17:41:18 -0400 Received: (qmail 20369 invoked by uid 0); 5 Aug 2009 21:41:15 -0000 Received: from 77.119.153.37 by www157.gmx.net with HTTP; Wed, 05 Aug 2009 23:41:12 +0200 (CEST) Content-Type: text/plain; charset="us-ascii" Date: Wed, 05 Aug 2009 23:41:12 +0200 From: martinpi.public@gmx.org Message-ID: <20090805214112.22600@gmx.net> MIME-Version: 1.0 To: paparazzi-devel@nongnu.org X-Authenticated: #19891149 X-Flags: 0001 X-Mailer: WWW-Mail 6100 (Global Message Exchange) X-Priority: 3 X-Provags-ID: V01U2FsdGVkX19D09Zat8hDK7+Fn7fY4qRumuiBZdEH/hgter4Zit WQa632+7BCYjdBrjR6bkZFPnNX2SPdMpA3UQ== Content-Transfer-Encoding: 7bit X-GMX-UID: SoZMIr9iZDIrFaOwVWc2YLh5emhmY8Gn X-FuHaFi: 0.74 X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 3) Subject: [Paparazzi-devel] flight plans: what makes it hold in holding point? X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Aug 2009 21:41:24 -0000 Just for curiosity: >From this code (basic.xml) I wouldn't expect the autopilot to wait for anything but go on to the next block immediately. Instead, in the holding point block, I would expect a loop like while launch==0 ... How does it work? From MAILER-DAEMON Wed Aug 05 20:13:16 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MYqbc-0008Rr-JQ for mharc-paparazzi-devel@gnu.org; Wed, 05 Aug 2009 20:13:16 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MYqbb-0008Rf-4i for paparazzi-devel@nongnu.org; Wed, 05 Aug 2009 20:13:15 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MYqbX-0008NB-G1 for paparazzi-devel@nongnu.org; Wed, 05 Aug 2009 20:13:14 -0400 Received: from [199.232.76.173] (port=58733 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MYqbX-0008N3-9l for paparazzi-devel@nongnu.org; Wed, 05 Aug 2009 20:13:11 -0400 Received: from smtpoutwbe08.prod.mesa1.secureserver.net ([208.109.78.210]:36067) by monty-python.gnu.org with smtp (Exim 4.60) (envelope-from ) id 1MYqbW-0002Ze-SK for paparazzi-devel@nongnu.org; Wed, 05 Aug 2009 20:13:11 -0400 Received: (qmail 13606 invoked from network); 6 Aug 2009 00:13:08 -0000 Received: from unknown (HELO p3plgemwbe01-02.prod.phx3.secureserver.net) (72.167.218.2) by smtpoutwbe08.prod.mesa1.secureserver.net with SMTP; 6 Aug 2009 00:13:08 -0000 Received: (qmail 3112 invoked by uid 99); 6 Aug 2009 00:13:07 -0000 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="utf-8" X-Originating-IP: 70.176.119.64 User-Agent: Web-Based Email 5.1.5 Message-Id: <20090805171307.e412a968f7f3915fb4f3361627e3fef7.fdca4357fb.wbe@email01.secureserver.net> From: akochevar@miraterre.com To: paparazzi-devel@nongnu.org Subject: RE: [Paparazzi-devel] flight plans: what makes it hold in holding =?UTF-8?Q?point=3F?= Date: Wed, 05 Aug 2009 17:13:07 -0700 Mime-Version: 1.0 X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.4-2.6 X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Aug 2009 00:13:15 -0000 The attitude code inside the autopilot has no exit criteria.  The= refore it just gets stuck in the attitude command until a block is change, = or a deroute event happens.  In the case of a <go> command the "= waypoint reached"
 designation exits the current stage.  If yo= u think about a circle, it never goes out of that either :)

AJ
<= br>
-------- Original Message --------
Subject: [Paparazzi-devel] flight plans: what makes it hold in holding
point?
From: martinpi.public@gmx.org
Date: Wed, August 05, 2009 2:41 pm
To: paparazzi-devel@nongnu.org

Just for curiosity:
>From this code (basic.xml)

<block name=3D"Holding point">
<set value=3D"1" var=3D"kill_throttle"/>
<attitude roll=3D"0" throttle=3D"0" vmode=3D"throttle"/>
</block>

I wouldn't expect the autopilot to wait for anything but go on to the next = block immediately.

Instead, in the holding point block, I would expect a loop like
while launch=3D=3D0 ...

How does it work?


_______________________________________________
Paparazzi-devel mailing list
Paparazzi-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/paparazzi-devel
From MAILER-DAEMON Thu Aug 06 06:02:21 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MYznh-00078K-AT for mharc-paparazzi-devel@gnu.org; Thu, 06 Aug 2009 06:02:21 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MYzne-00077Z-SX for paparazzi-devel@nongnu.org; Thu, 06 Aug 2009 06:02:18 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MYznZ-00073y-W3 for paparazzi-devel@nongnu.org; Thu, 06 Aug 2009 06:02:18 -0400 Received: from [199.232.76.173] (port=47203 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MYznZ-00073a-Qw for paparazzi-devel@nongnu.org; Thu, 06 Aug 2009 06:02:13 -0400 Received: from mx20.gnu.org ([199.232.41.8]:49682) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MYznZ-00078N-43 for paparazzi-devel@nongnu.org; Thu, 06 Aug 2009 06:02:13 -0400 Received: from stoat.shef.ac.uk ([143.167.2.187]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MYznW-0003lK-HD for paparazzi-devel@nongnu.org; Thu, 06 Aug 2009 06:02:10 -0400 Received: from dcs02962.dcs.shef.ac.uk ([143.167.10.18]) by stoat.shef.ac.uk with esmtpsa (TLSv1:RC4-MD5:128) (Exim 4.68) (envelope-from ) id 1MYznS-0002EP-QP for paparazzi-devel@nongnu.org; Thu, 06 Aug 2009 11:02:06 +0100 From: Gareth R To: paparazzi-devel@nongnu.org In-Reply-To: <4A79A4EC.1090308@free.fr> References: <50267EEE11C3460883A3943E45D600DD@server> <4A79A4EC.1090308@free.fr> Content-Type: text/plain Date: Thu, 06 Aug 2009 11:02:06 +0100 Message-Id: <1249552926.4853.67.camel@gareth> Mime-Version: 1.0 X-Mailer: Evolution 2.26.1 Content-Transfer-Encoding: 7bit X-S0phie-Scan: no X-Detected-Operating-System: by mx20.gnu.org: Solaris 10 (beta) X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6, seldom 2.4 (older, 4) Subject: [Paparazzi-devel] ACT Micro 6 X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Aug 2009 10:02:19 -0000 Hello everyone, There is mention of ACT Micro 6 receivers on the paparazzi site. I'm tempted because we've managed to destroy all our R136's (damn pilots...) and I can't find a reasonably priced source for new ones any more. So does anyone know either: -- The range like on the ACT Micros, whether they need special xtals and do they play nice with Futaba trannies? -- Recommendations of a receiver/supplier for the UK that has an accessible PPM tap and works with Futaba T6EXAPs. Cheers, and hope the EMAV entries are coming along nicely --G From MAILER-DAEMON Thu Aug 06 12:00:53 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MZ5Oe-0006Pq-HO for mharc-paparazzi-devel@gnu.org; Thu, 06 Aug 2009 12:00:52 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MZ5Oc-0006Om-J9 for paparazzi-devel@nongnu.org; Thu, 06 Aug 2009 12:00:50 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MZ5OV-0006MQ-Tw for paparazzi-devel@nongnu.org; Thu, 06 Aug 2009 12:00:49 -0400 Received: from [199.232.76.173] (port=57842 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MZ5OV-0006MI-Mb for paparazzi-devel@nongnu.org; Thu, 06 Aug 2009 12:00:43 -0400 Received: from mail-fx0-f207.google.com ([209.85.220.207]:36630) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MZ5OV-0003JB-7G for paparazzi-devel@nongnu.org; Thu, 06 Aug 2009 12:00:43 -0400 Received: by fxm3 with SMTP id 3so870381fxm.8 for ; Thu, 06 Aug 2009 09:00:39 -0700 (PDT) Received: by 10.103.108.11 with SMTP id k11mr29302mum.5.1249574438738; Thu, 06 Aug 2009 09:00:38 -0700 (PDT) Received: from server ([41.182.152.246]) by mx.google.com with ESMTPS id y6sm674325mug.40.2009.08.06.09.00.36 (version=SSLv3 cipher=RC4-MD5); Thu, 06 Aug 2009 09:00:37 -0700 (PDT) From: "gisela.noci" To: References: <50267EEE11C3460883A3943E45D600DD@server> <4A79A457.6080801@free.fr> Subject: RE: [Paparazzi-devel] Auto Take Off / Auto Land Date: Thu, 6 Aug 2009 18:00:42 +0200 Message-ID: <0FA7BF11D8554538B8192784EC9E7016@server> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 In-Reply-To: <4A79A457.6080801@free.fr> Thread-Index: AcoV4S2UC/TidKgPRsaq1L8/T7owrwAzYGjQ X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Aug 2009 16:00:50 -0000 Hi Pascal When guiding from the AF waypoint to the TD waypoint, which of the vertical guidance modes is used (ie CLIMB_MODE_AUTO_PITCH or CLIMB_MODE_AUTO_THROTTLE), or is the vertical guidance is the case of the landing a completely different thing, and if so, where can I find it in the source code? Gisela -----Original Message----- From: paparazzi-devel-bounces+gisela.noci=ate-international.com@nongnu.org [mailto:paparazzi-devel-bounces+gisela.noci=ate-international.com@nongnu.org ] On Behalf Of Pascal Brisset Sent: Wednesday, August 05, 2009 5:25 PM To: paparazzi-devel@nongnu.org Subject: Re: [Paparazzi-devel] Auto Take Off / Auto Land Hi, it's partially described in http://paparazzi.enac.fr/wiki_images/Users_manual.pdf (link from the wiki) --Pascal gisela.noci wrote: > > Does the Paparazzi Software manage either Auto Take Off or Auto Land > or both? If so, where can I find out more about the rationale behind > these functions? > > Gisela Noci > > ------------------------------------------------------------------------ > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > _______________________________________________ Paparazzi-devel mailing list Paparazzi-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/paparazzi-devel From MAILER-DAEMON Thu Aug 06 14:08:13 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MZ7Nt-0004p6-6d for mharc-paparazzi-devel@gnu.org; Thu, 06 Aug 2009 14:08:13 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MZ7Nr-0004oX-GJ for paparazzi-devel@nongnu.org; Thu, 06 Aug 2009 14:08:11 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MZ7Nm-0004n7-P3 for paparazzi-devel@nongnu.org; Thu, 06 Aug 2009 14:08:11 -0400 Received: from [199.232.76.173] (port=51904 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MZ7Nm-0004n2-KO for paparazzi-devel@nongnu.org; Thu, 06 Aug 2009 14:08:06 -0400 Received: from smtp6-g21.free.fr ([212.27.42.6]:38904) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MZ7Nl-0003E0-K4 for paparazzi-devel@nongnu.org; Thu, 06 Aug 2009 14:08:06 -0400 Received: from smtp6-g21.free.fr (localhost [127.0.0.1]) by smtp6-g21.free.fr (Postfix) with ESMTP id 992A6E08035 for ; Thu, 6 Aug 2009 20:08:01 +0200 (CEST) Received: from [192.168.0.10] (uni31-1-82-234-59-180.fbx.proxad.net [82.234.59.180]) by smtp6-g21.free.fr (Postfix) with ESMTP id AA061E080C2 for ; Thu, 6 Aug 2009 20:07:58 +0200 (CEST) Message-ID: <4A7B1BF8.2060904@free.fr> Date: Thu, 06 Aug 2009 20:07:52 +0200 From: Pascal Brisset User-Agent: Thunderbird 2.0.0.22 (X11/20090608) MIME-Version: 1.0 To: paparazzi-devel@nongnu.org Subject: Re: [Paparazzi-devel] Auto Take Off / Auto Land References: <50267EEE11C3460883A3943E45D600DD@server> <4A79A457.6080801@free.fr> <0FA7BF11D8554538B8192784EC9E7016@server> In-Reply-To: <0FA7BF11D8554538B8192784EC9E7016@server> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 3) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Aug 2009 18:08:11 -0000 Hi, the instruction is and the related code is in nav.c:156 : #define NavGlide(_last_wp, _wp) { \ float start_alt = waypoints[_last_wp].a; \ float diff_alt = waypoints[_wp].a - start_alt; \ float alt = start_alt + nav_leg_progress * diff_alt; \ float pre_climb = estimator_hspeed_mod * diff_alt / nav_leg_length; \ NavVerticalAltitudeMode(alt, pre_climb); \ } CLIMB_MODE_AUTO_THROTTLE is the default mode. If you want to use the pitch control with constant throtle, use --Pascal gisela.noci wrote: > Hi Pascal > When guiding from the AF waypoint to the TD waypoint, which of the vertical > guidance modes is used (ie CLIMB_MODE_AUTO_PITCH or > CLIMB_MODE_AUTO_THROTTLE), or is the vertical guidance is the case of the > landing a completely different thing, and if so, where can I find it in the > source code? > Gisela > > -----Original Message----- > From: paparazzi-devel-bounces+gisela.noci=ate-international.com@nongnu.org > [mailto:paparazzi-devel-bounces+gisela.noci=ate-international.com@nongnu.org > ] On Behalf Of Pascal Brisset > Sent: Wednesday, August 05, 2009 5:25 PM > To: paparazzi-devel@nongnu.org > Subject: Re: [Paparazzi-devel] Auto Take Off / Auto Land > > Hi, > > it's partially described in > http://paparazzi.enac.fr/wiki_images/Users_manual.pdf (link from the wiki) > > --Pascal > > gisela.noci wrote: > >> Does the Paparazzi Software manage either Auto Take Off or Auto Land >> or both? If so, where can I find out more about the rationale behind >> these functions? >> >> Gisela Noci >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> Paparazzi-devel mailing list >> Paparazzi-devel@nongnu.org >> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel >> >> > > > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > > > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > From MAILER-DAEMON Thu Aug 06 17:27:08 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MZAUN-0001xR-Rl for mharc-paparazzi-devel@gnu.org; Thu, 06 Aug 2009 17:27:07 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MZAUM-0001u0-1x for paparazzi-devel@nongnu.org; Thu, 06 Aug 2009 17:27:06 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MZAUH-0001gR-Cm for paparazzi-devel@nongnu.org; Thu, 06 Aug 2009 17:27:05 -0400 Received: from [199.232.76.173] (port=45995 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MZAUH-0001g1-1R for paparazzi-devel@nongnu.org; Thu, 06 Aug 2009 17:27:01 -0400 Received: from smtp6-g21.free.fr ([212.27.42.6]:43633) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MZAUG-0002WD-Br for paparazzi-devel@nongnu.org; Thu, 06 Aug 2009 17:27:00 -0400 Received: from smtp6-g21.free.fr (localhost [127.0.0.1]) by smtp6-g21.free.fr (Postfix) with ESMTP id BB1C7E080A9 for ; Thu, 6 Aug 2009 23:26:56 +0200 (CEST) Received: from [192.168.0.10] (uni31-1-82-234-59-180.fbx.proxad.net [82.234.59.180]) by smtp6-g21.free.fr (Postfix) with ESMTP id 9944BE080B8 for ; Thu, 6 Aug 2009 23:26:53 +0200 (CEST) Message-ID: <4A7B4A97.6030305@free.fr> Date: Thu, 06 Aug 2009 23:26:47 +0200 From: Pascal Brisset User-Agent: Thunderbird 2.0.0.22 (X11/20090608) MIME-Version: 1.0 To: paparazzi-devel@nongnu.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 3) Subject: [Paparazzi-devel] Flying ... X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Aug 2009 21:27:06 -0000 Some numbers: - 1800m: altitude of take-off and landing - 2400m: highest reached altitude (50m higher than the desired one, thanks to wind and/or thermals) - 11.85km: range reached with standard 2.4Ghz XBees (line of sight) - 3: number of lakes seen on the pictures - 15km: length of the route - 2000mAh: consumed energy (3 cells) - 80m: lowest height above the ground, while crossing the pass (2262m) - 2: number of ground stations - 1: number of megabytes of telemetry logged on board Today, a Paparazzi equipped Funjet autonomously crossed the Pyrenees (the mountains in the south-west of France), from North to South: http://paparazzi.enac.fr/wiki/Image:Pyrenees_crossing_NS.kmz Some stress while we were waiting (only 2 minutes) for the aircraft to appear on the GCS at the arrival and ... a lot of fun --Paparazzi Users From MAILER-DAEMON Thu Aug 06 17:48:14 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MZAoo-0005dM-KM for mharc-paparazzi-devel@gnu.org; Thu, 06 Aug 2009 17:48:14 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MZAon-0005cp-1f for paparazzi-devel@nongnu.org; Thu, 06 Aug 2009 17:48:13 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MZAoi-0005b9-4f for paparazzi-devel@nongnu.org; Thu, 06 Aug 2009 17:48:12 -0400 Received: from [199.232.76.173] (port=36915 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MZAoh-0005b1-U9 for paparazzi-devel@nongnu.org; Thu, 06 Aug 2009 17:48:07 -0400 Received: from asmtpout020.mac.com ([17.148.16.95]:58023) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MZAoh-0005JI-HF for paparazzi-devel@nongnu.org; Thu, 06 Aug 2009 17:48:07 -0400 MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Received: from 234.sub-75-217-189.myvzw.com (234.sub-75-217-189.myvzw.com [75.217.189.234]) by asmtp020.mac.com (Sun Java(tm) System Messaging Server 6.3-8.01 (built Dec 16 2008; 32bit)) with ESMTPSA id <0KNZ007DA5VYIT00@asmtp020.mac.com> for paparazzi-devel@nongnu.org; Thu, 06 Aug 2009 14:48:00 -0700 (PDT) Message-id: <6BC7C795-2413-4CAC-8B21-11969BC6BCBE@mac.com> From: David Conger To: paparazzi-devel@nongnu.org In-reply-to: <4A7B4A97.6030305@free.fr> Subject: Re: [Paparazzi-devel] Flying ... Date: Thu, 06 Aug 2009 14:47:58 -0700 References: <4A7B4A97.6030305@free.fr> X-Mailer: Apple Mail (2.935.3) X-detected-operating-system: by monty-python.gnu.org: Solaris 10 (1203?) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Aug 2009 21:48:13 -0000 Wow! That is awesome. Congratulations. Was there onboard video? :) -David Conger On Aug 6, 2009, at 2:26 PM, Pascal Brisset wrote: > Some numbers: > - 1800m: altitude of take-off and landing > - 2400m: highest reached altitude (50m higher than the desired one, > thanks to wind and/or thermals) > - 11.85km: range reached with standard 2.4Ghz XBees (line of sight) > - 3: number of lakes seen on the pictures > - 15km: length of the route > - 2000mAh: consumed energy (3 cells) > - 80m: lowest height above the ground, while crossing the pass (2262m) > - 2: number of ground stations > - 1: number of megabytes of telemetry logged on board > > Today, a Paparazzi equipped Funjet autonomously crossed the Pyrenees > (the mountains in the south-west of France), from North to South: > > http://paparazzi.enac.fr/wiki/Image:Pyrenees_crossing_NS.kmz > > Some stress while we were waiting (only 2 minutes) for the aircraft > to appear on the GCS at the arrival and ... a lot of fun > > --Paparazzi Users > > > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel From MAILER-DAEMON Thu Aug 06 21:16:09 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MZE41-0007gg-9R for mharc-paparazzi-devel@gnu.org; Thu, 06 Aug 2009 21:16:09 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MZE3z-0007fv-GV for paparazzi-devel@nongnu.org; Thu, 06 Aug 2009 21:16:07 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MZE3t-0007Yd-Uw for paparazzi-devel@nongnu.org; Thu, 06 Aug 2009 21:16:06 -0400 Received: from [199.232.76.173] (port=52526 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MZE3t-0007YU-QU for paparazzi-devel@nongnu.org; Thu, 06 Aug 2009 21:16:01 -0400 Received: from an-out-0708.google.com ([209.85.132.251]:1913) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MZE3t-0003g7-Cx for paparazzi-devel@nongnu.org; Thu, 06 Aug 2009 21:16:01 -0400 Received: by an-out-0708.google.com with SMTP id c38so297731ana.37 for ; Thu, 06 Aug 2009 18:16:00 -0700 (PDT) MIME-Version: 1.0 Received: by 10.100.191.7 with SMTP id o7mr12446397anf.33.1249607760515; Thu, 06 Aug 2009 18:16:00 -0700 (PDT) In-Reply-To: <4A7B4A97.6030305@free.fr> References: <4A7B4A97.6030305@free.fr> Date: Thu, 6 Aug 2009 19:16:00 -0600 Message-ID: <875d4d950908061816qa597162n74bd3f044dbf06ee@mail.gmail.com> Subject: Re: [Paparazzi-devel] Flying ... From: Haiyang Chao To: paparazzi-devel@nongnu.org Content-Type: multipart/alternative; boundary=0016e6440358ac946b047082fa34 X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Aug 2009 01:16:07 -0000 --0016e6440358ac946b047082fa34 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cool and congratulations. What is the strongest wind u guys had flying above the mountain? Haiyang On Thu, Aug 6, 2009 at 3:26 PM, Pascal Brisset wrote: > Some numbers: > - 1800m: altitude of take-off and landing > - 2400m: highest reached altitude (50m higher than the desired one, thanks > to wind and/or thermals) > - 11.85km: range reached with standard 2.4Ghz XBees (line of sight) > - 3: number of lakes seen on the pictures > - 15km: length of the route > - 2000mAh: consumed energy (3 cells) > - 80m: lowest height above the ground, while crossing the pass (2262m) > - 2: number of ground stations > - 1: number of megabytes of telemetry logged on board > > Today, a Paparazzi equipped Funjet autonomously crossed the Pyrenees (the > mountains in the south-west of France), from North to South: > > http://paparazzi.enac.fr/wiki/Image:Pyrenees_crossing_NS.kmz > > Some stress while we were waiting (only 2 minutes) for the aircraft to > appear on the GCS at the arrival and ... a lot of fun > > --Paparazzi Users > > > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > --0016e6440358ac946b047082fa34 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cool and congratulations.
What is the strongest wind u guys had flying a= bove the mountain?

Haiyang

On Thu,= Aug 6, 2009 at 3:26 PM, Pascal Brisset <pascal.brisset@free.fr> wrote:
Some numbers:
- 1800m: altitude of take-off and landing
- 2400m: highest reached altitude (50m higher than the desired one, thanks = to wind and/or thermals)
- 11.85km: range reached with standard 2.4Ghz XBees (line of sight)
- 3: number of lakes seen on the pictures
- 15km: length of the route
- 2000mAh: consumed energy (3 cells)
- 80m: lowest height above the ground, while crossing the pass (2262m)
- 2: number of ground stations
- 1: number of megabytes of telemetry logged on board

Today, a Paparazzi equipped Funjet autonomously crossed the Pyrenees (the m= ountains in the south-west of France), from North to South:

=A0 http://paparazzi.enac.fr/wiki/Image:Pyrenees_crossing_= NS.kmz

Some stress while we were waiting (only 2 minutes) for the aircraft to appe= ar on the GCS at the arrival and ... a lot of fun

--Paparazzi Users



_______________________________________________
Paparazzi-devel mailing list
Paparazzi-d= evel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/paparazzi-devel

--0016e6440358ac946b047082fa34-- From MAILER-DAEMON Fri Aug 07 01:52:34 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MZINV-0000bA-91 for mharc-paparazzi-devel@gnu.org; Fri, 07 Aug 2009 01:52:33 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MZINS-0000ac-Oz for paparazzi-devel@nongnu.org; Fri, 07 Aug 2009 01:52:30 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MZINN-0000ZG-Ig for paparazzi-devel@nongnu.org; Fri, 07 Aug 2009 01:52:29 -0400 Received: from [199.232.76.173] (port=45493 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MZINM-0000ZC-OI for paparazzi-devel@nongnu.org; Fri, 07 Aug 2009 01:52:24 -0400 Received: from blu0-omc2-s34.blu0.hotmail.com ([65.55.111.109]:50421) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MZINM-0003ZU-7a for paparazzi-devel@nongnu.org; Fri, 07 Aug 2009 01:52:24 -0400 Received: from BLU149-W23 ([65.55.111.72]) by blu0-omc2-s34.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 6 Aug 2009 22:52:23 -0700 Message-ID: Content-Type: multipart/alternative; boundary="_52563424-3ad9-4bf2-85e9-367a3961cd85_" X-Originating-IP: [134.96.163.226] From: =?big5?B?s6IgZmx5aW5nIHBpZw==?= To: Subject: RE: [Paparazzi-devel] Flying ... Date: Fri, 7 Aug 2009 05:52:23 +0000 Importance: Normal In-Reply-To: <4A7B4A97.6030305@free.fr> References: <4A7B4A97.6030305@free.fr> MIME-Version: 1.0 X-OriginalArrivalTime: 07 Aug 2009 05:52:23.0407 (UTC) FILETIME=[3C289FF0:01CA1723] X-detected-operating-system: by monty-python.gnu.org: Windows 2000 SP4, XP SP1+ X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Aug 2009 05:52:31 -0000 --_52563424-3ad9-4bf2-85e9-367a3961cd85_ Content-Type: text/plain; charset="big5" Content-Transfer-Encoding: 8bit Hi there wow, 15km flight, that was a very long distance. i was wondering you mention that there are 2 GCS and 2 min lost of singal while funjet is still flying, so how to setup the airfram that even if it is out of ground modem range, and still continou flying? let's say, i want to aircraft flight outside of my range for some time, then return to home. it is possible? Thanks Chen > Date: Thu, 6 Aug 2009 23:26:47 +0200 > From: pascal.brisset@free.fr > To: paparazzi-devel@nongnu.org > Subject: [Paparazzi-devel] Flying ... > > Some numbers: > - 1800m: altitude of take-off and landing > - 2400m: highest reached altitude (50m higher than the desired one, > thanks to wind and/or thermals) > - 11.85km: range reached with standard 2.4Ghz XBees (line of sight) > - 3: number of lakes seen on the pictures > - 15km: length of the route > - 2000mAh: consumed energy (3 cells) > - 80m: lowest height above the ground, while crossing the pass (2262m) > - 2: number of ground stations > - 1: number of megabytes of telemetry logged on board > > Today, a Paparazzi equipped Funjet autonomously crossed the Pyrenees > (the mountains in the south-west of France), from North to South: > > http://paparazzi.enac.fr/wiki/Image:Pyrenees_crossing_NS.kmz > > Some stress while we were waiting (only 2 minutes) for the aircraft to > appear on the GCS at the arrival and ... a lot of fun > > --Paparazzi Users > > > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel _________________________________________________________________ ¥Î³¡¸¨®æ¤À¨É·Ó¤ù¡B¼v­µ¡B½ì¨ý¤p¤u¨ã©M³Ì·R²M³æ¡AºÉ±¡¨q¥X§A¦Û¤v ¡X Windows Live Spaces http://home.spaces.live.com/?showUnauth=1&lc=1028 --_52563424-3ad9-4bf2-85e9-367a3961cd85_ Content-Type: text/html; charset="big5" Content-Transfer-Encoding: 8bit Hi there
 
  wow, 15km flight, that was a very long distance. i was wondering you mention that there are 2 GCS and 2 min lost of singal while funjet is still flying, so how to setup the airfram that even if it is out of ground modem range, and still continou flying?  let's say, i want to aircraft flight outside of my range for some time, then return to home. it is possible?
 
 
 
  Thanks
 
                                                                                            Chen
 
> Date: Thu, 6 Aug 2009 23:26:47 +0200
> From: pascal.brisset@free.fr
> To: paparazzi-devel@nongnu.org
> Subject: [Paparazzi-devel] Flying ...
>
> Some numbers:
> - 1800m: altitude of take-off and landing
> - 2400m: highest reached altitude (50m higher than the desired one,
> thanks to wind and/or thermals)
> - 11.85km: range reached with standard 2.4Ghz XBees (line of sight)
> - 3: number of lakes seen on the pictures
> - 15km: length of the route
> - 2000mAh: consumed energy (3 cells)
> - 80m: lowest height above the ground, while crossing the pass (2262m)
> - 2: number of ground stations
> - 1: number of megabytes of telemetry logged on board
>
> Today, a Paparazzi equipped Funjet autonomously crossed the Pyrenees
> (the mountains in the south-west of France), from North to South:
>
> http://paparazzi.enac.fr/wiki/Image:Pyrenees_crossing_NS.kmz
>
> Some stress while we were waiting (only 2 minutes) for the aircraft to
> appear on the GCS at the arrival and ... a lot of fun
>
> --Paparazzi Users
>
>
>
> _______________________________________________
> Paparazzi-devel mailing list
> Paparazzi-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel


¥Î³¡¸¨®æ¤À¨É·Ó¤ù¡B¼v­µ¡B½ì¨ý¤p¤u¨ã©M³Ì·R²M³æ¡AºÉ±¡¨q¥X§A¦Û¤v ¡X Windows Live Spaces --_52563424-3ad9-4bf2-85e9-367a3961cd85_-- From MAILER-DAEMON Fri Aug 07 02:14:59 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MZIjD-0008VT-DG for mharc-paparazzi-devel@gnu.org; Fri, 07 Aug 2009 02:14:59 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MZIjA-0008VI-BU for paparazzi-devel@nongnu.org; Fri, 07 Aug 2009 02:14:56 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MZIj5-0008V5-DM for paparazzi-devel@nongnu.org; Fri, 07 Aug 2009 02:14:56 -0400 Received: from [199.232.76.173] (port=33160 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MZIj5-0008V2-6J for paparazzi-devel@nongnu.org; Fri, 07 Aug 2009 02:14:51 -0400 Received: from forward6.yandex.ru ([77.88.60.125]:57410) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MZIj4-000830-HP for paparazzi-devel@nongnu.org; Fri, 07 Aug 2009 02:14:50 -0400 Received: from webmail44.yandex.ru (webmail44.yandex.ru [77.88.60.23]) by forward6.yandex.ru (Yandex) with ESMTP id 8C12DDC8EEE for ; Fri, 7 Aug 2009 10:14:46 +0400 (MSD) Received: from localhost (localhost.localdomain [127.0.0.1]) by webmail44.yandex.ru (Yandex) with ESMTP id 416ECF01DD for ; Fri, 7 Aug 2009 10:14:46 +0400 (MSD) X-Yandex-Spam: 1 X-Yandex-Front: webmail44 X-Yandex-TimeMark: 1249625686 Received: from [82.137.173.16] ([82.137.173.16]) by mail.yandex.ru with HTTP; Fri, 07 Aug 2009 10:14:45 +0400 From: Andrew S To: paparazzi-devel@nongnu.org In-Reply-To: <4A7B4A97.6030305@free.fr> References: <4A7B4A97.6030305@free.fr> Subject: Re: [Paparazzi-devel] Flying ... MIME-Version: 1.0 Message-Id: <230051249625685@webmail44.yandex.ru> Date: Fri, 07 Aug 2009 10:14:45 +0400 X-Mailer: Yamail [ http://yandex.ru ] 5.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Aug 2009 06:14:56 -0000 Great job, congratulations! Your Xbee was with standard antenna, or with advanced? 07.08.09, 01:26, "Pascal Brisset" : > Some numbers: > - 1800m: altitude of take-off and landing > - 2400m: highest reached altitude (50m higher than the desired one,=20 > thanks to wind and/or thermals) > - 11.85km: range reached with standard 2.4Ghz XBees (line of sight) > - 3: number of lakes seen on the pictures > - 15km: length of the route > - 2000mAh: consumed energy (3 cells) > - 80m: lowest height above the ground, while crossing the pass (2262m) > - 2: number of ground stations > - 1: number of megabytes of telemetry logged on board > Today, a Paparazzi equipped Funjet autonomously crossed the Pyrenees=20 > (the mountains in the south-west of France), from North to South: > http://paparazzi.enac.fr/wiki/Image:Pyrenees_crossing_NS.kmz > Some stress while we were waiting (only 2 minutes) for the aircraft to=20 > appear on the GCS at the arrival and ... a lot of fun > --Paparazzi Users > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel --=20 =D0=AF=D0=BD=D0=B4=D0=B5=D0=BA=D1=81.=D0=9F=D0=BE=D1=87=D1=82=D0=B0. =D0=9F= =D0=BE=D0=B8=D1=89=D0=B8=D1=82=D0=B5 =D1=81=D0=BF=D0=B0=D0=BC =D0=B3=D0=B4= =D0=B5-=D0=BD=D0=B8=D0=B1=D1=83=D0=B4=D1=8C =D0=B5=D1=89=D0=B5 http://mai= l.yandex.ru/nospam/sign From MAILER-DAEMON Fri Aug 07 02:40:01 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MZJ7R-0001RC-5d for mharc-paparazzi-devel@gnu.org; Fri, 07 Aug 2009 02:40:01 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MZJ7O-0001O5-PC for paparazzi-devel@nongnu.org; Fri, 07 Aug 2009 02:39:58 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MZJ7J-0001Hq-VS for paparazzi-devel@nongnu.org; Fri, 07 Aug 2009 02:39:58 -0400 Received: from [199.232.76.173] (port=36778 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MZJ7J-0001Hc-Q3 for paparazzi-devel@nongnu.org; Fri, 07 Aug 2009 02:39:53 -0400 Received: from mail-fx0-f207.google.com ([209.85.220.207]:56159) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MZJ7J-0004Gn-FQ for paparazzi-devel@nongnu.org; Fri, 07 Aug 2009 02:39:53 -0400 Received: by fxm3 with SMTP id 3so1515023fxm.8 for ; Thu, 06 Aug 2009 23:39:51 -0700 (PDT) Received: by 10.103.138.19 with SMTP id q19mr327047mun.56.1249627191615; Thu, 06 Aug 2009 23:39:51 -0700 (PDT) Received: from server ([41.182.140.226]) by mx.google.com with ESMTPS id s11sm3560452mue.41.2009.08.06.23.39.46 (version=SSLv3 cipher=RC4-MD5); Thu, 06 Aug 2009 23:39:47 -0700 (PDT) From: "gisela.noci" To: References: <4A7B4A97.6030305@free.fr> Subject: RE: [Paparazzi-devel] Flying ... Date: Fri, 7 Aug 2009 08:39:53 +0200 Message-ID: <6F2D323B472247118C8936599F15DF69@server> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 In-Reply-To: <4A7B4A97.6030305@free.fr> Thread-Index: AcoW3LZDxy3pH/qqRvSJmIORKpxK3wASgAxA X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Aug 2009 06:39:59 -0000 Very Interesting Pascal. Could you give some info on the aircraft - Motor type, A/C flying weight, takeoff motor amps and cruise motor amps, cruise speed. What was the total flight duration? You state a 11.85km 'line of sight' range. At this range there is approx 122dB path loss @ 2.4GHz. I do not know the TX power of the XBees stuff, but if I assume 500mW ( 27dBM) and a Video receiver typical sensitivity of around -75dBM then the antenna's used need to make up a gain requirement of around 20dB's. What antenna's did you use? We are doing some interesting stuff here in Namibia; using a 1 hour duration slow composite flyer we designed , carrying a stabilized camera to take photos of Vultures nesting in tree tops in the Namib Desert, which is then used by Nature Conservation for the annual Vulture count as a measure of 'health' of the wildlife environment. Really great flying in the wide open spaces here! Well done. Joe -----Original Message----- From: paparazzi-devel-bounces+gisela.noci=ate-international.com@nongnu.org [mailto:paparazzi-devel-bounces+gisela.noci=ate-international.com@nongnu.org ] On Behalf Of Pascal Brisset Sent: Thursday, August 06, 2009 11:27 PM To: paparazzi-devel@nongnu.org Subject: [Paparazzi-devel] Flying ... Some numbers: - 1800m: altitude of take-off and landing - 2400m: highest reached altitude (50m higher than the desired one, thanks to wind and/or thermals) - 11.85km: range reached with standard 2.4Ghz XBees (line of sight) - 3: number of lakes seen on the pictures - 15km: length of the route - 2000mAh: consumed energy (3 cells) - 80m: lowest height above the ground, while crossing the pass (2262m) - 2: number of ground stations - 1: number of megabytes of telemetry logged on board Today, a Paparazzi equipped Funjet autonomously crossed the Pyrenees (the mountains in the south-west of France), from North to South: http://paparazzi.enac.fr/wiki/Image:Pyrenees_crossing_NS.kmz Some stress while we were waiting (only 2 minutes) for the aircraft to appear on the GCS at the arrival and ... a lot of fun --Paparazzi Users _______________________________________________ Paparazzi-devel mailing list Paparazzi-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/paparazzi-devel From MAILER-DAEMON Fri Aug 07 04:48:45 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MZL81-0000PJ-7H for mharc-paparazzi-devel@gnu.org; Fri, 07 Aug 2009 04:48:45 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MZL7z-0000NG-1c for paparazzi-devel@nongnu.org; Fri, 07 Aug 2009 04:48:43 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MZL7u-0000LI-60 for paparazzi-devel@nongnu.org; Fri, 07 Aug 2009 04:48:42 -0400 Received: from [199.232.76.173] (port=50751 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MZL7t-0000LB-TE for paparazzi-devel@nongnu.org; Fri, 07 Aug 2009 04:48:37 -0400 Received: from stoat.shef.ac.uk ([143.167.2.187]:45933) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_3DES_EDE_CBC_SHA1:24) (Exim 4.60) (envelope-from ) id 1MZL7t-0006XP-G1 for paparazzi-devel@nongnu.org; Fri, 07 Aug 2009 04:48:37 -0400 Received: from dcs02962.dcs.shef.ac.uk ([143.167.10.18]) by stoat.shef.ac.uk with esmtpsa (TLSv1:RC4-MD5:128) (Exim 4.68) (envelope-from ) id 1MZL7n-00070i-Ux for paparazzi-devel@nongnu.org; Fri, 07 Aug 2009 09:48:31 +0100 From: Gareth R To: paparazzi-devel@nongnu.org In-Reply-To: <4A7B4A97.6030305@free.fr> References: <4A7B4A97.6030305@free.fr> Content-Type: text/plain Date: Fri, 07 Aug 2009 09:48:31 +0100 Message-Id: <1249634911.4100.10.camel@gareth> Mime-Version: 1.0 X-Mailer: Evolution 2.26.1 Content-Transfer-Encoding: 7bit X-S0phie-Scan: no X-detected-operating-system: by monty-python.gnu.org: Solaris 10 (beta) Subject: [Paparazzi-devel] Possible SVN problem X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Aug 2009 08:48:43 -0000 Firstly, congratulations on that incredible flight Pascal! You'll have to try over the Alps into Italy next... I updated to the latest svn this morning, cleaned, rebuilt and tried to build my aircraft as usual, but get a string of errors like this: " /home/blutack/Sources/paparazzi3/sw/airborne/arm7/sys_time_hw.h:35:10: #include expects "FILENAME" or In file included from /home/blutack/Sources/paparazzi3/sw/airborne/led.h:37, from /home/blutack/Sources/paparazzi3/sw/airborne/arm7/sys_time_hw.h:36, from sys_time.h:39, from autopilot.h:35, from fw_v_ctl.c:35: /home/blutack/Sources/paparazzi3/sw/airborne/arm7/led_hw.h:4:10: #include expects "FILENAME" or In file included from sys_time.h:39, from autopilot.h:35, from fw_v_ctl.c:35: /home/blutack/Sources/paparazzi3/sw/airborne/arm7/sys_time_hw.h:56:2: #error unknown PCLK frequency " The complete build log is here: http://paste2.org/p/365563 Is there a problem in the svn, or have I done something stupid? Many Thanks --G From MAILER-DAEMON Fri Aug 07 04:59:53 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MZLIn-0004vJ-Dn for mharc-paparazzi-devel@gnu.org; Fri, 07 Aug 2009 04:59:53 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MZLIl-0004tk-Kj for paparazzi-devel@nongnu.org; Fri, 07 Aug 2009 04:59:51 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MZLIg-0004pt-ED for paparazzi-devel@nongnu.org; Fri, 07 Aug 2009 04:59:50 -0400 Received: from [199.232.76.173] (port=39453 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MZLIg-0004pm-89 for paparazzi-devel@nongnu.org; Fri, 07 Aug 2009 04:59:46 -0400 Received: from stoat.shef.ac.uk ([143.167.2.187]:48165) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_3DES_EDE_CBC_SHA1:24) (Exim 4.60) (envelope-from ) id 1MZLIf-00086r-Kk for paparazzi-devel@nongnu.org; Fri, 07 Aug 2009 04:59:45 -0400 Received: from dcs02962.dcs.shef.ac.uk ([143.167.10.18]) by stoat.shef.ac.uk with esmtpsa (TLSv1:RC4-MD5:128) (Exim 4.68) (envelope-from ) id 1MZLIe-0001HL-9M for paparazzi-devel@nongnu.org; Fri, 07 Aug 2009 09:59:44 +0100 Subject: Re: [Paparazzi-devel] Possible SVN problem From: Gareth R To: paparazzi-devel@nongnu.org In-Reply-To: <1249634911.4100.10.camel@gareth> References: <4A7B4A97.6030305@free.fr> <1249634911.4100.10.camel@gareth> Content-Type: text/plain Date: Fri, 07 Aug 2009 09:59:44 +0100 Message-Id: <1249635584.4100.14.camel@gareth> Mime-Version: 1.0 X-Mailer: Evolution 2.26.1 Content-Transfer-Encoding: 7bit X-S0phie-Scan: no X-detected-operating-system: by monty-python.gnu.org: Solaris 10 (beta) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Aug 2009 08:59:51 -0000 Oops, just went through the mailing list archive for the 2 weeks I was on holiday. Sorry! --G From MAILER-DAEMON Fri Aug 07 10:43:22 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MZQfC-0002xS-2T for mharc-paparazzi-devel@gnu.org; Fri, 07 Aug 2009 10:43:22 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MZQf9-0002we-MT for paparazzi-devel@nongnu.org; Fri, 07 Aug 2009 10:43:19 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MZQf5-0002wC-4p for paparazzi-devel@nongnu.org; Fri, 07 Aug 2009 10:43:19 -0400 Received: from [199.232.76.173] (port=47038 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MZQf5-0002w9-04 for paparazzi-devel@nongnu.org; Fri, 07 Aug 2009 10:43:15 -0400 Received: from mail-yx0-f188.google.com ([209.85.210.188]:46723) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MZQf4-0000DO-L9 for paparazzi-devel@nongnu.org; Fri, 07 Aug 2009 10:43:14 -0400 Received: by yxe26 with SMTP id 26so1987795yxe.4 for ; Fri, 07 Aug 2009 07:43:13 -0700 (PDT) MIME-Version: 1.0 Sender: maik@zackbumm.biz Received: by 10.90.101.17 with SMTP id y17mr1004692agb.29.1249656191770; Fri, 07 Aug 2009 07:43:11 -0700 (PDT) In-Reply-To: <230051249625685@webmail44.yandex.ru> References: <4A7B4A97.6030305@free.fr> <230051249625685@webmail44.yandex.ru> From: =?UTF-8?B?TWFpayBIw7ZwZmVs?= Date: Fri, 7 Aug 2009 16:42:51 +0200 X-Google-Sender-Auth: ff3e8908ec3a6bca Message-ID: Subject: Re: [Paparazzi-devel] Flying ... To: paparazzi-devel@nongnu.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Aug 2009 14:43:19 -0000 This is so awesome! But, as they say: "pics or it didn't happen!" ;) 2009/8/7 Andrew S : > Great job, congratulations! > Your Xbee was with standard antenna, or with advanced? > > 07.08.09, 01:26, "Pascal Brisset" : > >> =C2=A0Some numbers: >> =C2=A0- 1800m: altitude of take-off and landing >> =C2=A0- 2400m: highest reached altitude (50m higher than the desired one= , >> thanks to wind and/or thermals) >> =C2=A0- 11.85km: range reached with standard 2.4Ghz XBees (line of sight= ) >> =C2=A0- 3: number of lakes seen on the pictures >> =C2=A0- 15km: length of the route >> =C2=A0- 2000mAh: consumed energy (3 cells) >> =C2=A0- 80m: lowest height above the ground, while crossing the pass (22= 62m) >> =C2=A0- 2: number of ground stations >> =C2=A0- 1: number of megabytes of telemetry logged on board >> Today, a Paparazzi equipped Funjet autonomously crossed the Pyrenees >> (the mountains in the south-west of France), from North to South: >> =C2=A0 =C2=A0 http://paparazzi.enac.fr/wiki/Image:Pyrenees_crossing_NS.k= mz >> Some stress while we were waiting (only 2 minutes) for the aircraft to >> appear on the GCS at the arrival and ... a lot of fun >> --Paparazzi Users >> _______________________________________________ >> Paparazzi-devel mailing list >> Paparazzi-devel@nongnu.org >> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > > -- > =D0=AF=D0=BD=D0=B4=D0=B5=D0=BA=D1=81.=D0=9F=D0=BE=D1=87=D1=82=D0=B0. =D0= =9F=D0=BE=D0=B8=D1=89=D0=B8=D1=82=D0=B5 =D1=81=D0=BF=D0=B0=D0=BC =D0=B3=D0= =B4=D0=B5-=D0=BD=D0=B8=D0=B1=D1=83=D0=B4=D1=8C =D0=B5=D1=89=D0=B5 http://ma= il.yandex.ru/nospam/sign > > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > From MAILER-DAEMON Sat Aug 08 04:32:30 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MZhLq-0001wa-86 for mharc-paparazzi-devel@gnu.org; Sat, 08 Aug 2009 04:32:30 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MZhLo-0001wC-5X for paparazzi-devel@nongnu.org; Sat, 08 Aug 2009 04:32:28 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MZhLi-0001vs-Us for paparazzi-devel@nongnu.org; Sat, 08 Aug 2009 04:32:27 -0400 Received: from [199.232.76.173] (port=38383 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MZhLi-0001vp-PT for paparazzi-devel@nongnu.org; Sat, 08 Aug 2009 04:32:22 -0400 Received: from mail-fx0-f207.google.com ([209.85.220.207]:58136) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MZhLi-0003mz-C0 for paparazzi-devel@nongnu.org; Sat, 08 Aug 2009 04:32:22 -0400 Received: by fxm3 with SMTP id 3so2605452fxm.8 for ; Sat, 08 Aug 2009 01:32:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:content-type :content-transfer-encoding; bh=SXJlXkbkdYtnB4LWRJL3THQo29XpbVQdgN98m8yVmQM=; b=kv2mq0cvTZCE4Hhq8wq1iT5m0zHwOXoMXRM+z9OiRv77IFSruPhYIOEGWS3taa7ZGX W9P0YLkgLxJjqZvQhNYWH+77yiTxdLOHW0arJiQsTPBST/h3RYgZ0LZB6Ceg5JZ+7Vc+ yvH8lHsg4/uBUi5di8VtwYOe3wpPaVT+Z9xzQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; b=PiI8OkE5PFWydBwonJPxMJctg6DJSoBiQYX5LCNeAc4cNh0rFDzFkWgUQosbh9T+ws Smh+HCcS64FLl2eEU2O3ip4SkgSkUUTVQE/d8ioU/Y3hFeKGk52pbhIQLkviKnRXQLtm nz2EYaVkZibLQkjJyBghczUqU5AuEQuapJ8jA= Received: by 10.204.50.195 with SMTP id a3mr4002575bkg.94.1249720340625; Sat, 08 Aug 2009 01:32:20 -0700 (PDT) Received: from ?192.168.1.2? ([88.218.149.158]) by mx.google.com with ESMTPS id z10sm3714615fka.35.2009.08.08.01.32.18 (version=SSLv3 cipher=RC4-MD5); Sat, 08 Aug 2009 01:32:18 -0700 (PDT) Message-ID: <4A7D3810.1010700@gmail.com> Date: Sat, 08 Aug 2009 11:32:16 +0300 From: chris User-Agent: Thunderbird 2.0.0.22 (X11/20090608) MIME-Version: 1.0 To: paparazzi-devel@nongnu.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) Subject: [Paparazzi-devel] aggressive descend? X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Aug 2009 08:32:28 -0000 I have yet another question.... :-) In my flight plan i climb to 2000 feet and take pictures of an imaginary target. When it is time to descend the plane refuses to do so although it shuts the motor off. Thermals are very strong and they make the plane climb even with 0 throttle. Is there any way to force an aggressive descend like the aggressive climb definition does? Thanks in advance. Chris From MAILER-DAEMON Sun Aug 09 04:06:44 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Ma3QS-0003GC-Ho for mharc-paparazzi-devel@gnu.org; Sun, 09 Aug 2009 04:06:44 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Ma3QP-0003E3-TU for paparazzi-devel@nongnu.org; Sun, 09 Aug 2009 04:06:42 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Ma3QK-0003A2-Ii for paparazzi-devel@nongnu.org; Sun, 09 Aug 2009 04:06:40 -0400 Received: from [199.232.76.173] (port=59630 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ma3QK-00039o-BD for paparazzi-devel@nongnu.org; Sun, 09 Aug 2009 04:06:36 -0400 Received: from mail.gmx.net ([213.165.64.20]:59419) by monty-python.gnu.org with smtp (Exim 4.60) (envelope-from ) id 1Ma3QJ-0001ED-LF for paparazzi-devel@nongnu.org; Sun, 09 Aug 2009 04:06:36 -0400 Received: (qmail 26032 invoked by uid 0); 9 Aug 2009 07:39:50 -0000 Received: from 77.117.70.69 by www048.gmx.net with HTTP; Sun, 09 Aug 2009 09:39:50 +0200 (CEST) Content-Type: text/plain; charset="us-ascii" Date: Sun, 09 Aug 2009 09:39:50 +0200 From: "Martin P" In-Reply-To: <20090805171307.e412a968f7f3915fb4f3361627e3fef7.fdca4357fb.wbe@email01.secureserver.net> Message-ID: <20090809073950.23230@gmx.net> MIME-Version: 1.0 References: <20090805171307.e412a968f7f3915fb4f3361627e3fef7.fdca4357fb.wbe@email01.secureserver.net> Subject: Re: RE: [Paparazzi-devel] flight plans: what makes it hold in holding point? To: paparazzi-devel@nongnu.org X-Authenticated: #19891149 X-Flags: 0001 X-Mailer: WWW-Mail 6100 (Global Message Exchange) X-Priority: 3 X-Provags-ID: V01U2FsdGVkX1+gla1CXSKgYUNg9+sghKqOk7Jz2JOhTQbkqd8xMB boJC1f5dapuW2zCbB29DSCxpW8S0LfovYbFA== Content-Transfer-Encoding: 7bit X-GMX-UID: fkpLfmZOTiE+Ur7iSGVw+2Z9ZUVSRJfv X-FuHaFi: 0.73 X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Aug 2009 08:06:42 -0000 Thank you! -------- Original-Nachricht -------- > Datum: Wed, 05 Aug 2009 17:13:07 -0700 > Von: akochevar@miraterre.com > An: paparazzi-devel@nongnu.org > Betreff: RE: [Paparazzi-devel] flight plans: what makes it hold in holding point? > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel From MAILER-DAEMON Sun Aug 09 04:13:48 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Ma3XI-000525-5X for mharc-paparazzi-devel@gnu.org; Sun, 09 Aug 2009 04:13:48 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Ma3XG-00051p-Ir for paparazzi-devel@nongnu.org; Sun, 09 Aug 2009 04:13:46 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Ma3XB-00051d-HJ for paparazzi-devel@nongnu.org; Sun, 09 Aug 2009 04:13:45 -0400 Received: from [199.232.76.173] (port=42603 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ma3XB-00051a-Bp for paparazzi-devel@nongnu.org; Sun, 09 Aug 2009 04:13:41 -0400 Received: from mail.gmx.net ([213.165.64.20]:58465) by monty-python.gnu.org with smtp (Exim 4.60) (envelope-from ) id 1Ma3XA-000236-R6 for paparazzi-devel@nongnu.org; Sun, 09 Aug 2009 04:13:41 -0400 Received: (qmail 2812 invoked by uid 0); 9 Aug 2009 07:46:59 -0000 Received: from 77.117.70.69 by www048.gmx.net with HTTP; Sun, 09 Aug 2009 09:46:59 +0200 (CEST) Content-Type: text/plain; charset="us-ascii" Date: Sun, 09 Aug 2009 09:46:59 +0200 From: "Martin P" Message-ID: <20090809074659.23250@gmx.net> MIME-Version: 1.0 To: paparazzi-devel@nongnu.org X-Authenticated: #19891149 X-Flags: 0001 X-Mailer: WWW-Mail 6100 (Global Message Exchange) X-Priority: 3 X-Provags-ID: V01U2FsdGVkX19ViMdXrl1VtH7zwggN3sw5VHgV2YS4D99Qb5NR17 MhygG5aTXUp/TuEbGOtnQ7tfGk4am65J8RFQ== Content-Transfer-Encoding: 7bit X-GMX-UID: wElMeyEhIydmAOjmW2ZrOHRSa2FkZpWt X-FuHaFi: 0.71 X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. Subject: [Paparazzi-devel] AGL and NavSetGroundReferenceHere() X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Aug 2009 08:13:46 -0000 I use a flight plan with goround_alt=0 (derived from basic.xml). After calling NavSetGroundReferenceHere(), I would expect that the AGL is 0. Instead, it is the altitude above sea level. The GPS mode is 3D and the AGL varies within 3 or 4 meters. Is this the way it should be? Should I set the ground_alt to the actual altitude? From MAILER-DAEMON Sun Aug 09 04:17:59 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Ma3bL-0006zI-OR for mharc-paparazzi-devel@gnu.org; Sun, 09 Aug 2009 04:17:59 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Ma3bJ-0006ya-VI for paparazzi-devel@nongnu.org; Sun, 09 Aug 2009 04:17:57 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Ma3bE-0006yA-Nc for paparazzi-devel@nongnu.org; Sun, 09 Aug 2009 04:17:56 -0400 Received: from [199.232.76.173] (port=36802 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ma3bE-0006y7-HU for paparazzi-devel@nongnu.org; Sun, 09 Aug 2009 04:17:52 -0400 Received: from mail.gmx.net ([213.165.64.20]:41066) by monty-python.gnu.org with smtp (Exim 4.60) (envelope-from ) id 1Ma3bD-0002ag-VK for paparazzi-devel@nongnu.org; Sun, 09 Aug 2009 04:17:52 -0400 Received: (qmail 21219 invoked by uid 0); 9 Aug 2009 08:17:50 -0000 Received: from 77.117.70.69 by www039.gmx.net with HTTP; Sun, 09 Aug 2009 10:17:48 +0200 (CEST) Content-Type: text/plain; charset="us-ascii" Date: Sun, 09 Aug 2009 10:17:48 +0200 From: "Martin P" Message-ID: <20090809081748.23240@gmx.net> MIME-Version: 1.0 To: paparazzi-devel@nongnu.org X-Authenticated: #19891149 X-Flags: 0001 X-Mailer: WWW-Mail 6100 (Global Message Exchange) X-Priority: 3 X-Provags-ID: V01U2FsdGVkX199PIls+1R9wIeSpctvJG6iLliwWpx0z55ZixYVIP UxgF/1fj0wlKY/EDX8pUXg08ay4Fx1ZIJOZg== Content-Transfer-Encoding: 7bit X-GMX-UID: Hr9Gfyh6bmwoTr/xRzZL+F9PUzc4clF4 X-FuHaFi: 0.6 X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 3) Subject: [Paparazzi-devel] crashed X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Aug 2009 08:17:58 -0000 Hello everyone! Last weekend I had a good AUTO1 flight with my Minimag. It reacted to pitch and roll commands, and I was able to control the throttle. I had an attitude command in my flightplan which was never left (as I know now). Yesterday I tried again, without the attitude statement and without a holding point block. In AUTO1, it killed the throttle. Switched to manual and landed to change battery because it was not fully charged. Took off again. Switched to AUTO1 and it immediately stabilized the plane. Strangely, this time it did not react to the roll command. I flew around using the rudder. When I used the elevator stick, the autopilot controlled the throttle. Good, so far. Suddenly the plane dived down vertically from an altitude of roughly 40m. No reaction, just kept going vertical and slowly spinning around the longitudinal axis until it crashed. There was not as much damage done as I expected. These foamies are awesome. All RC components including Tiny and Xbee are OK. Except for the Lipo which is badly bent out of shape and will be replaced for safety reasons. Unfortunately I can't see much from the log as I had lost the link probably minutes before. I was in stage "HOME" because I had left the fly-too-far circle before and came back manually. The switch was on manual so I probably tried to rescue. The Tiny was unplugged which can have happened at the crash or before. One aileron was ripped off and the horizontal IR was missing (I found it in the grass). So far, my report. The Minimag is already repaired and I'll keep trying. Greetz, Martin From MAILER-DAEMON Sun Aug 09 08:48:02 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Ma7og-0006Kf-AT for mharc-paparazzi-devel@gnu.org; Sun, 09 Aug 2009 08:48:02 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Ma7oe-0006KV-O3 for paparazzi-devel@nongnu.org; Sun, 09 Aug 2009 08:48:00 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Ma7oc-0006KI-S8 for paparazzi-devel@nongnu.org; Sun, 09 Aug 2009 08:47:59 -0400 Received: from [199.232.76.173] (port=60453 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ma7oc-0006KF-Mv for paparazzi-devel@nongnu.org; Sun, 09 Aug 2009 08:47:58 -0400 Received: from forward2.yandex.ru ([77.88.46.7]:59294) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Ma7oc-0007zs-8i for paparazzi-devel@nongnu.org; Sun, 09 Aug 2009 08:47:58 -0400 Received: from webmail16.yandex.ru (webmail16.yandex.ru [77.88.47.38]) by forward2.yandex.ru (Yandex) with ESMTP id 197AD3968B35 for ; Sun, 9 Aug 2009 16:47:54 +0400 (MSD) Received: from localhost (localhost.localdomain [127.0.0.1]) by webmail16.yandex.ru (Yandex) with ESMTP id E802A12063E for ; Sun, 9 Aug 2009 16:47:53 +0400 (MSD) X-Yandex-Spam: 1 X-Yandex-Front: webmail16 X-Yandex-TimeMark: 1249822073 Received: from [83.149.3.24] ([83.149.3.24]) by mail.yandex.ru with HTTP; Sun, 09 Aug 2009 16:47:52 +0400 From: Andrew S To: paparazzi-devel@nongnu.org In-Reply-To: <20090809074659.23250@gmx.net> References: <20090809074659.23250@gmx.net> Subject: Re: [Paparazzi-devel] AGL and NavSetGroundReferenceHere() MIME-Version: 1.0 Message-Id: <260401249822073@webmail16.yandex.ru> Date: Sun, 09 Aug 2009 16:47:53 +0400 X-Mailer: Yamail [ http://yandex.ru ] 5.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Aug 2009 12:48:00 -0000 Hello I can ask the same. For me AGL shows altitude abowe sea level, but in sim= ulator abowe ground reference. Maybe we miss somethink in adjustments? Andrew 09.08.09, 11:46, "Martin P" : > I use a flight plan with goround_alt=3D0 (derived from basic.xml). > After calling NavSetGroundReferenceHere(), I would expect that the AGL = is 0.=20 > Instead, it is the altitude above sea level. The GPS mode is 3D and the= AGL varies within 3 or 4 meters.=20 > Is this the way it should be? Should I set the ground_alt to the actual= altitude?=20 > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel=C2=A0 -- =D0=AF=D0=BD=D0=B4=D0=B5=D0=BA=D1=81.=D0=9F=D0=BE=D1=87=D1=82=D0=B0. =D0=9F= =D0=BE=D0=B8=D1=89=D0=B8=D1=82=D0=B5 =D1=81=D0=BF=D0=B0=D0=BC =D0=B3=D0=B4= =D0=B5-=D0=BD=D0=B8=D0=B1=D1=83=D0=B4=D1=8C =D0=B5=D1=89=D0=B5 http://mai= l.yandex.ru/nospam/sign From MAILER-DAEMON Sun Aug 09 10:47:26 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Ma9gE-00084g-KB for mharc-paparazzi-devel@gnu.org; Sun, 09 Aug 2009 10:47:26 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Ma9gC-000812-5x for paparazzi-devel@nongnu.org; Sun, 09 Aug 2009 10:47:24 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Ma9g6-0007tK-TQ for paparazzi-devel@nongnu.org; Sun, 09 Aug 2009 10:47:23 -0400 Received: from [199.232.76.173] (port=56817 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ma9g6-0007tA-Ph for paparazzi-devel@nongnu.org; Sun, 09 Aug 2009 10:47:18 -0400 Received: from mx20.gnu.org ([199.232.41.8]:31574) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Ma9g6-0004BU-96 for paparazzi-devel@nongnu.org; Sun, 09 Aug 2009 10:47:18 -0400 Received: from smtp6-g21.free.fr ([212.27.42.6]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Ma9g3-0004Ku-DM for paparazzi-devel@nongnu.org; Sun, 09 Aug 2009 10:47:16 -0400 Received: from smtp6-g21.free.fr (localhost [127.0.0.1]) by smtp6-g21.free.fr (Postfix) with ESMTP id 418BEE080B8 for ; Sun, 9 Aug 2009 16:47:09 +0200 (CEST) Received: from [192.168.0.10] (uni31-1-82-234-59-180.fbx.proxad.net [82.234.59.180]) by smtp6-g21.free.fr (Postfix) with ESMTP id 521FDE08051 for ; Sun, 9 Aug 2009 16:47:07 +0200 (CEST) Message-ID: <4A7EE169.1050106@free.fr> Date: Sun, 09 Aug 2009 16:47:05 +0200 From: Pascal Brisset User-Agent: Thunderbird 2.0.0.22 (X11/20090608) MIME-Version: 1.0 To: paparazzi-devel@nongnu.org Subject: Re: [Paparazzi-devel] Flying ... References: <4A7B4A97.6030305@free.fr> In-Reply-To: Content-Type: text/plain; charset=Big5 Content-Transfer-Encoding: quoted-printable X-Detected-Operating-System: by mx20.gnu.org: GNU/Linux 2.6 (newer, 3) X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6, seldom 2.4 (older, 4) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Aug 2009 14:47:24 -0000 Hi, =B3=A2 flying pig wrote: > range, and still continou flying? let's say, i want to aircraft flight > outside of my range for some time, then return to home. it is possible? > It's the default behaviour :-) Unless an explicit monitoring of the uplink is added, the autopilot do not need any communications with the GCS to execute its flight plan. Example in the flight_plans/basic.xml line block: 22" deroute=3D"Standby"/> where datalink_time is the time since the last received message (the GCS sends a PING message every 5s) --Pascal From MAILER-DAEMON Sun Aug 09 10:48:45 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Ma9hV-0000YB-42 for mharc-paparazzi-devel@gnu.org; Sun, 09 Aug 2009 10:48:45 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Ma9hT-0000Y5-Ja for paparazzi-devel@nongnu.org; Sun, 09 Aug 2009 10:48:43 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Ma9hO-0000Xj-3S for paparazzi-devel@nongnu.org; Sun, 09 Aug 2009 10:48:42 -0400 Received: from [199.232.76.173] (port=56830 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ma9hN-0000Xf-TM for paparazzi-devel@nongnu.org; Sun, 09 Aug 2009 10:48:37 -0400 Received: from mx20.gnu.org ([199.232.41.8]:31701) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Ma9hN-0005wc-Gl for paparazzi-devel@nongnu.org; Sun, 09 Aug 2009 10:48:37 -0400 Received: from smtp6-g21.free.fr ([212.27.42.6]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Ma9hM-0004QL-Dm for paparazzi-devel@nongnu.org; Sun, 09 Aug 2009 10:48:37 -0400 Received: from smtp6-g21.free.fr (localhost [127.0.0.1]) by smtp6-g21.free.fr (Postfix) with ESMTP id 48365E080B8 for ; Sun, 9 Aug 2009 16:48:32 +0200 (CEST) Received: from [192.168.0.10] (uni31-1-82-234-59-180.fbx.proxad.net [82.234.59.180]) by smtp6-g21.free.fr (Postfix) with ESMTP id 278FCE08056 for ; Sun, 9 Aug 2009 16:48:30 +0200 (CEST) Message-ID: <4A7EE1BC.9010906@free.fr> Date: Sun, 09 Aug 2009 16:48:28 +0200 From: Pascal Brisset User-Agent: Thunderbird 2.0.0.22 (X11/20090608) MIME-Version: 1.0 To: paparazzi-devel@nongnu.org Subject: Re: [Paparazzi-devel] Flying ... References: <4A7B4A97.6030305@free.fr> <230051249625685@webmail44.yandex.ru> In-Reply-To: <230051249625685@webmail44.yandex.ru> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Detected-Operating-System: by mx20.gnu.org: GNU/Linux 2.6 (newer, 3) X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6, seldom 2.4 (older, 4) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Aug 2009 14:48:43 -0000 Hi, some answers and pictures in the wiki: http://paparazzi.enac.fr/wiki/Pyrenees_Crossing --Pascal Andrew S wrote: > Great job, congratulations! > Your Xbee was with standard antenna, or with advanced? > > 07.08.09, 01:26, "Pascal Brisset" : > > >> Some numbers: >> - 1800m: altitude of take-off and landing >> - 2400m: highest reached altitude (50m higher than the desired one, >> thanks to wind and/or thermals) >> - 11.85km: range reached with standard 2.4Ghz XBees (line of sight) >> - 3: number of lakes seen on the pictures >> - 15km: length of the route >> - 2000mAh: consumed energy (3 cells) >> - 80m: lowest height above the ground, while crossing the pass (2262m) >> - 2: number of ground stations >> - 1: number of megabytes of telemetry logged on board >> Today, a Paparazzi equipped Funjet autonomously crossed the Pyrenees >> (the mountains in the south-west of France), from North to South: >> http://paparazzi.enac.fr/wiki/Image:Pyrenees_crossing_NS.kmz >> Some stress while we were waiting (only 2 minutes) for the aircraft to >> appear on the GCS at the arrival and ... a lot of fun >> --Paparazzi Users >> _______________________________________________ >> Paparazzi-devel mailing list >> Paparazzi-devel@nongnu.org >> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel >> > > From MAILER-DAEMON Sun Aug 09 11:08:10 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MaA0I-0007R0-6K for mharc-paparazzi-devel@gnu.org; Sun, 09 Aug 2009 11:08:10 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MaA0F-0007P0-VQ for paparazzi-devel@nongnu.org; Sun, 09 Aug 2009 11:08:08 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MaA0B-0007On-Ro for paparazzi-devel@nongnu.org; Sun, 09 Aug 2009 11:08:07 -0400 Received: from [199.232.76.173] (port=55430 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MaA0B-0007Ok-M8 for paparazzi-devel@nongnu.org; Sun, 09 Aug 2009 11:08:03 -0400 Received: from smtp6-g21.free.fr ([212.27.42.6]:51502) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MaA0A-00034m-Qz for paparazzi-devel@nongnu.org; Sun, 09 Aug 2009 11:08:03 -0400 Received: from smtp6-g21.free.fr (localhost [127.0.0.1]) by smtp6-g21.free.fr (Postfix) with ESMTP id B77A2E08053 for ; Sun, 9 Aug 2009 17:07:59 +0200 (CEST) Received: from [192.168.0.10] (uni31-1-82-234-59-180.fbx.proxad.net [82.234.59.180]) by smtp6-g21.free.fr (Postfix) with ESMTP id C4883E08098 for ; Sun, 9 Aug 2009 17:07:56 +0200 (CEST) Message-ID: <4A7EE64A.1030408@free.fr> Date: Sun, 09 Aug 2009 17:07:54 +0200 From: Pascal Brisset User-Agent: Thunderbird 2.0.0.22 (X11/20090608) MIME-Version: 1.0 To: paparazzi-devel@nongnu.org Subject: Re: [Paparazzi-devel] AGL and NavSetGroundReferenceHere() References: <20090809074659.23250@gmx.net> In-Reply-To: <20090809074659.23250@gmx.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 3) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Aug 2009 15:08:08 -0000 Hi, what do you call AGL ? - in the airborne code, NavSetGroundReferenceHere() sets ground_alt to the current altitude (common_nav.c:84). This variable is for example use in HOME mode (nav.c:370) or in the Takeoff and Final block of the basic.xml flight plan. - in the GCS, AGL is computed by subtracting the terrain altitude (from the SRTM model ... if the file is available in data/SRTM) from the current altitude --Pascal Martin P wrote: > I use a flight plan with goround_alt=0 (derived from basic.xml). > After calling NavSetGroundReferenceHere(), I would expect that the AGL is 0. > Instead, it is the altitude above sea level. The GPS mode is 3D and the AGL varies within 3 or 4 meters. > > Is this the way it should be? Should I set the ground_alt to the actual altitude? > > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > From MAILER-DAEMON Sun Aug 09 11:10:30 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MaA2Y-0000AJ-Fa for mharc-paparazzi-devel@gnu.org; Sun, 09 Aug 2009 11:10:30 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MaA2X-00009p-8u for paparazzi-devel@nongnu.org; Sun, 09 Aug 2009 11:10:29 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MaA2S-00007r-F9 for paparazzi-devel@nongnu.org; Sun, 09 Aug 2009 11:10:28 -0400 Received: from [199.232.76.173] (port=42405 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MaA2S-00007m-C2 for paparazzi-devel@nongnu.org; Sun, 09 Aug 2009 11:10:24 -0400 Received: from blu0-omc2-s32.blu0.hotmail.com ([65.55.111.107]:55376) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MaA2R-0003jp-Ul for paparazzi-devel@nongnu.org; Sun, 09 Aug 2009 11:10:24 -0400 Received: from BLU149-W30 ([65.55.111.72]) by blu0-omc2-s32.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Sun, 9 Aug 2009 08:10:23 -0700 Message-ID: Content-Type: multipart/alternative; boundary="_8368eb68-8bab-4d23-ac41-6dbe061f1959_" X-Originating-IP: [78.52.188.13] From: =?big5?B?s6IgZmx5aW5nIHBpZw==?= To: Subject: RE: [Paparazzi-devel] Flying ... Date: Sun, 9 Aug 2009 15:10:23 +0000 Importance: Normal In-Reply-To: <4A7EE169.1050106@free.fr> References: <4A7B4A97.6030305@free.fr> <4A7EE169.1050106@free.fr> MIME-Version: 1.0 X-OriginalArrivalTime: 09 Aug 2009 15:10:23.0427 (UTC) FILETIME=[84A1C130:01CA1903] X-detected-operating-system: by monty-python.gnu.org: Windows 2000 SP4, XP SP1+ X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Aug 2009 15:10:29 -0000 --_8368eb68-8bab-4d23-ac41-6dbe061f1959_ Content-Type: text/plain; charset="big5" Content-Transfer-Encoding: 8bit Hi there Thanks for your answer, i understand it now. We also plan to fly our funjet amd twin satrt for long sidtance. we will let you guys know what the result will be. Regards Chen > Date: Sun, 9 Aug 2009 16:47:05 +0200 > From: pascal.brisset@free.fr > To: paparazzi-devel@nongnu.org > Subject: Re: [Paparazzi-devel] Flying ... > > Hi, > > ³¢ flying pig wrote: > > range, and still continou flying? let's say, i want to aircraft flight > > outside of my range for some time, then return to home. it is possible? > > > It's the default behaviour :-) Unless an explicit monitoring of the > uplink is added, the autopilot do not need > any communications with the GCS to execute its flight plan. > Example in the flight_plans/basic.xml line block: > > > > where datalink_time is the time since the last received message (the GCS > sends a PING message every 5s) > > --Pascal > > > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel _________________________________________________________________ »P±z³ßÅwªº¤H¦b½u¤W¤À¨É¦^¾Ð¡C http://www.microsoft.com/taiwan/windows/windowslive/products/photos-share.aspx?tab=1 --_8368eb68-8bab-4d23-ac41-6dbe061f1959_ Content-Type: text/html; charset="big5" Content-Transfer-Encoding: 8bit Hi there
 
 
  Thanks for your answer, i understand it now.  We also plan to fly our funjet amd twin satrt for long sidtance. we will let you guys know what the result will be.
 
 
 
Regards
 
                                                                 Chen
 
> Date: Sun, 9 Aug 2009 16:47:05 +0200
> From: pascal.brisset@free.fr
> To: paparazzi-devel@nongnu.org
> Subject: Re: [Paparazzi-devel] Flying ...
>
> Hi,
>
> ³¢ flying pig wrote:
> > range, and still continou flying? let's say, i want to aircraft flight
> > outside of my range for some time, then return to home. it is possible?
> >
> It's the default behaviour :-) Unless an explicit monitoring of the
> uplink is added, the autopilot do not need
> any communications with the GCS to execute its flight plan.
> Example in the flight_plans/basic.xml line block:
>
> <exception cond="datalink_time > 22" deroute="Standby"/>
>
> where datalink_time is the time since the last received message (the GCS
> sends a PING message every 5s)
>
> --Pascal
>
>
>
> _______________________________________________
> Paparazzi-devel mailing list
> Paparazzi-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel


»P±z³ßÅwªº¤H¦b½u¤W¤À¨É¦^¾Ð »P±z³ßÅwªº¤H --_8368eb68-8bab-4d23-ac41-6dbe061f1959_-- From MAILER-DAEMON Sun Aug 09 11:33:08 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MaAOR-00073F-V1 for mharc-paparazzi-devel@gnu.org; Sun, 09 Aug 2009 11:33:08 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MX11P-0007sW-Nv for paparazzi-devel@nongnu.org; Fri, 31 Jul 2009 18:56:19 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MX11M-0007oY-83 for paparazzi-devel@nongnu.org; Fri, 31 Jul 2009 18:56:19 -0400 Received: from [199.232.76.173] (port=36960 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MX11L-0007oT-O9 for paparazzi-devel@nongnu.org; Fri, 31 Jul 2009 18:56:15 -0400 Received: from mail-05.name-services.com ([69.64.155.197]:2631) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MX11L-0006Do-99 for paparazzi-devel@nongnu.org; Fri, 31 Jul 2009 18:56:15 -0400 Received: from [10.171.190.209] ([166.205.132.112]) by mail-05.name-services.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 31 Jul 2009 15:08:21 -0700 Message-Id: From: David To: "paparazzi-devel@nongnu.org" In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit X-Mailer: iPhone Mail (7A341) Mime-Version: 1.0 (iPhone Mail 7A341) Subject: Re: [Paparazzi-devel] Quick Question Date: Fri, 31 Jul 2009 15:07:39 -0700 References: X-OriginalArrivalTime: 31 Jul 2009 22:08:22.0746 (UTC) FILETIME=[6B5A63A0:01CA122B] X-Sender: sales@ppzuav.com X-detected-operating-system: by monty-python.gnu.org: Windows XP/2000 (RFC1323+, w, tstamp+) X-Greylist: delayed 2847 seconds by postgrey-1.27 at monty-python; Fri, 31 Jul 2009 18:56:13 EDT X-Mailman-Approved-At: Sun, 09 Aug 2009 11:33:05 -0400 X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Jul 2009 22:56:19 -0000 Hi Armen, Good work, now disconnect the motor and try AUT2. only in AUTO2 is the auto pilot truly in control. Hey, we can also fly Sunday AM as well. Let's get this thing full-auto this weekend. Try and verify when you turn off the RC Tx it goes to auto2. Your RC gets goofy so we may need AUTO2 to fly it. - David Conger On Jul 31, 2009, at 9:22 AM, Armen Gharibans wrote: > Hello, > > If the control surfaces are working correctly in Manual and Auto1, > does that mean it works correctly in Auto2? > > Thanks. > Armen > > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel From MAILER-DAEMON Sun Aug 09 11:33:08 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MaAOS-00073X-E6 for mharc-paparazzi-devel@gnu.org; Sun, 09 Aug 2009 11:33:08 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MYBjR-0001Cj-Eg for paparazzi-devel@nongnu.org; Tue, 04 Aug 2009 00:34:37 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MYBjM-0001CX-2g for paparazzi-devel@nongnu.org; Tue, 04 Aug 2009 00:34:36 -0400 Received: from [199.232.76.173] (port=52253 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MYBjL-0001CU-Te for paparazzi-devel@nongnu.org; Tue, 04 Aug 2009 00:34:31 -0400 Received: from mail-px0-f201.google.com ([209.85.216.201]:36200) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MYBjL-0005oY-Ai for paparazzi-devel@nongnu.org; Tue, 04 Aug 2009 00:34:31 -0400 Received: by pxi39 with SMTP id 39so2707888pxi.4 for ; Mon, 03 Aug 2009 21:34:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:references :in-reply-to:subject:date:message-id:mime-version:content-type :content-transfer-encoding:x-mailer:thread-index:content-language; bh=MYCO0xnFyZAkZvqLeMcnIA+/cUUTXXH5pb8NXTnDnTc=; b=Q8KpHvlupgWA6Pq4IXne/sNNJZ0XyA1RRbNYWWJiNjnOVFEvhBoMFNU7ngEO+w2ff0 PQLu/G9efWzuew5YE4yuYKwwEfGY+nbgAxOK2QBh9ezsq9oCvXzK41hDrGnOvXWulIyw MYx0ZeILQSprZjsvquRE+dMm+DU+tIyqVN+1I= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:references:in-reply-to:subject:date:message-id:mime-version :content-type:content-transfer-encoding:x-mailer:thread-index :content-language; b=rTnYx7RMDF88aJlANOqsAaJDVgxWZl4VrzUfpQmcJjPOMBp9wp8IEpv2L6XIXQJZZD qJfs2t531fcXtvgjvN9F5Dd6v+8vkmNJhDR4sCmE/qRkrPsvBfLMDr9GNfcndvc/jlPc PB33BKn+kcVuPxAlXOhE9Xfg5SdwOXdDnvnVE= Received: by 10.141.29.3 with SMTP id g3mr4488937rvj.230.1249360469593; Mon, 03 Aug 2009 21:34:29 -0700 (PDT) Received: from AntoineDURIEUX (adsl-71-131-18-32.dsl.sntc01.pacbell.net [71.131.18.32]) by mx.google.com with ESMTPS id f42sm406239rvb.35.2009.08.03.21.34.26 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 03 Aug 2009 21:34:27 -0700 (PDT) From: "Antoine DURIEUX" To: References: <4A77B4A2.1030106@dcarr.org> In-Reply-To: <4A77B4A2.1030106@dcarr.org> Subject: RE: [Paparazzi-devel] MLX90247 $5 each, LEA-4H $35, LEA-5H $40 Date: Tue, 4 Aug 2009 06:34:22 +0200 Message-ID: <4a77ba53.2a528c0a.2d15.5887@mx.google.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AcoUuZQep//v5KAJTYmHpCAXyiSKCQAAvqug Content-Language: fr X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) X-Mailman-Approved-At: Sun, 09 Aug 2009 11:33:05 -0400 X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Aug 2009 04:34:37 -0000 Hi ! I'm interested by the LEA-5h and some IR sensors. Where do you live ? Best regards, Antoine Durieux -----Message d'origine----- De=A0: = paparazzi-devel-bounces+antoine.durieux=3Dpolytechnique.org@nongnu.org [mailto:paparazzi-devel-bounces+antoine.durieux=3Dpolytechnique.org@nongn= u.org ] De la part de David Carr Envoy=E9=A0: mardi 4 ao=FBt 2009 06:10 =C0=A0: paparazzi-devel@nongnu.org Objet=A0: [Paparazzi-devel] MLX90247 $5 each, LEA-4H $35, LEA-5H $40 Guys, I've got 17 MLX90247 IR sensors I'd like to get rid of. They are new,=20 never used. $5 each + $2 shipping in the US. I also have 2 LEA-4Hs for $35 and 1 LEA-5H for $40. Same deal as above. -David Carr _______________________________________________ Paparazzi-devel mailing list Paparazzi-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/paparazzi-devel From MAILER-DAEMON Sun Aug 09 11:33:09 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MaAOS-00073m-TK for mharc-paparazzi-devel@gnu.org; Sun, 09 Aug 2009 11:33:08 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MYW3t-0002TY-N7 for paparazzi-devel@nongnu.org; Tue, 04 Aug 2009 22:17:05 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MYW3p-0002TM-2S for paparazzi-devel@nongnu.org; Tue, 04 Aug 2009 22:17:04 -0400 Received: from [199.232.76.173] (port=60480 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MYW3o-0002TJ-97 for paparazzi-devel@nongnu.org; Tue, 04 Aug 2009 22:17:00 -0400 Received: from et1.ou.edu ([129.15.0.239]:5060) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_ARCFOUR_MD5:16) (Exim 4.60) (envelope-from ) id 1MYW3n-0005AA-OQ for paparazzi-devel@nongnu.org; Tue, 04 Aug 2009 22:16:59 -0400 Received: from IT-TIGER.sooner.net.ou.edu (10.254.255.10) by it-fiestabowl.sooner.net.ou.edu (10.254.255.17) with Microsoft SMTP Server (TLS) id 8.2.176.0; Tue, 4 Aug 2009 20:54:05 -0500 Received: from XMAIL4.sooner.net.ou.edu ([10.254.254.56]) by IT-TIGER.sooner.net.ou.edu ([10.254.254.41]) with mapi; Tue, 4 Aug 2009 20:56:16 -0500 From: "Langston, Joel T." To: "paparazzi-devel@nongnu.org" Date: Tue, 4 Aug 2009 20:56:15 -0500 Thread-Topic: Transmitter compatability Thread-Index: AQHKFW/qPhojSzH1jEKyFcuuyokJzA== Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-detected-operating-system: by monty-python.gnu.org: Windows 2000 SP4, XP SP1+ X-Greylist: delayed 1241 seconds by postgrey-1.27 at monty-python; Tue, 04 Aug 2009 22:16:59 EDT X-Mailman-Approved-At: Sun, 09 Aug 2009 11:33:05 -0400 Subject: [Paparazzi-devel] Transmitter compatability X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Aug 2009 02:17:05 -0000 To Paparazzi,=20 I am involved in a university funded research project building a meteorolog= y UAV. We are planning on using the TINY 2.1 autopilot system. Is it comp= atible with all transmitters? We need at least 10 channels on our aircraft= , so we are looking at purchasing either the FUTABA 10C or the JR 12X. Wil= l the autopilot work with either of these radios? Thanks for your response in advance. Joel Langston Aerospace Engineering University of Oklahoma From MAILER-DAEMON Sun Aug 09 12:18:10 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MaB61-0001Z1-Na for mharc-paparazzi-devel@gnu.org; Sun, 09 Aug 2009 12:18:09 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MaB5z-0001Xa-Gr for paparazzi-devel@nongnu.org; Sun, 09 Aug 2009 12:18:07 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MaB5y-0001Wy-7s for paparazzi-devel@nongnu.org; Sun, 09 Aug 2009 12:18:06 -0400 Received: from [199.232.76.173] (port=37421 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MaB5y-0001Wu-0G for paparazzi-devel@nongnu.org; Sun, 09 Aug 2009 12:18:06 -0400 Received: from ey-out-1920.google.com ([74.125.78.145]:30990) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MaB5x-0003hH-P0 for paparazzi-devel@nongnu.org; Sun, 09 Aug 2009 12:18:05 -0400 Received: by ey-out-1920.google.com with SMTP id 5so624108eyb.4 for ; Sun, 09 Aug 2009 09:18:03 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.39.85 with SMTP id c63mr696953web.103.1249834683009; Sun, 09 Aug 2009 09:18:03 -0700 (PDT) In-Reply-To: References: Date: Sun, 9 Aug 2009 10:18:02 -0600 Message-ID: <5e20ac400908090918y7aa0465bp5e2a2e0b32c38ea5@mail.gmail.com> Subject: Re: [Paparazzi-devel] Transmitter compatability From: Nicholas Wagner To: paparazzi-devel@nongnu.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Aug 2009 16:18:07 -0000 Hi Joel - We are building a UAV with the Futaba 10CAP currently. Any receiver will work with the servo2ppm board for sale on David Conger's website (ppzuav.com). We have successfully used it on our first plane and are now transitioning over to our second UAV. Nick On Tue, Aug 4, 2009 at 7:56 PM, Langston, Joel T. wrote: > To Paparazzi, > > I am involved in a university funded research project building a meteorol= ogy UAV. =A0We are planning on using the TINY 2.1 autopilot system. =A0Is i= t compatible with all transmitters? =A0We need at least 10 channels on our = aircraft, so we are looking at purchasing either the FUTABA 10C or the JR 1= 2X. =A0Will the autopilot work with either of these radios? > > Thanks for your response in advance. > > Joel Langston > Aerospace Engineering > University of Oklahoma > > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > --=20 Nick Wagner Mechanical Engineering Colorado State University E: nawagner@rams.colostate.edu From MAILER-DAEMON Sun Aug 09 13:39:55 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MaCN9-0000cc-5U for mharc-paparazzi-devel@gnu.org; Sun, 09 Aug 2009 13:39:55 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MaCN6-0000bh-Rb for paparazzi-devel@nongnu.org; Sun, 09 Aug 2009 13:39:52 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MaCN1-0000Yg-Iu for paparazzi-devel@nongnu.org; Sun, 09 Aug 2009 13:39:51 -0400 Received: from [199.232.76.173] (port=53984 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MaCN1-0000YZ-BJ for paparazzi-devel@nongnu.org; Sun, 09 Aug 2009 13:39:47 -0400 Received: from mxout4.cac.washington.edu ([140.142.33.19]:47795) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MaCN0-0008F7-QK for paparazzi-devel@nongnu.org; Sun, 09 Aug 2009 13:39:47 -0400 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.7] (may be forged)) by mxout4.cac.washington.edu (8.14.3+UW09.06/8.14.3+UW09.05) with ESMTP id n79Hdgqv016543 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Sun, 9 Aug 2009 10:39:42 -0700 X-Auth-Received: from [192.168.1.100] (c-76-27-232-248.hsd1.or.comcast.net [76.27.232.248]) (authenticated authid=quill) by smtp.washington.edu (8.14.3+UW09.06/8.14.3+UW09.05) with ESMTP id n79HdfaH019732 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Sun, 9 Aug 2009 10:39:42 -0700 Message-ID: <4A7F09D7.8030601@u.washington.edu> Date: Sun, 09 Aug 2009 10:39:35 -0700 From: John Burt Organization: University of Washington User-Agent: Thunderbird 2.0.0.22 (Windows/20090605) MIME-Version: 1.0 To: paparazzi-devel@nongnu.org Subject: Re: [Paparazzi-devel] crashed References: <20090809081748.23240@gmx.net> In-Reply-To: <20090809081748.23240@gmx.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-PMX-Version: 5.5.7.378829, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2009.8.9.172717 X-Uwash-Spam: Gauge=X, Probability=10%, Report=' TO_IN_SUBJECT 0.5, SUPERLONG_LINE 0.05, BODY_SIZE_2000_2999 0, BODY_SIZE_5000_LESS 0, BODY_SIZE_7000_LESS 0, TO_NO_NAME 0, __BOUNCE_CHALLENGE_SUBJ 0, __CP_NOT_1 0, __CP_URI_IN_BODY 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __FRAUD_419_BADTHINGS 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __MOZILLA_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __URI_NS , __USER_AGENT 0' X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.4-2.6 X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: quill@u.washington.edu, paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Aug 2009 17:39:53 -0000 Martin, I crashed an Easystar just like that during early flight testing. The AP (Tiny 2.11) went nonresponsive and dived into the ground, despite my having immediately flipped the switch to manual. It would seem that the AP processor just locked up - truly a worst case scenario. The cause of the behavior was an undervoltage spike condition due to sourcing the four servos and RC RX off the 5V supply. In case you haven't already, you should always power your hardware off a separate BEC (which begs the question of why the AP has a 5V source anyway). AP generated noise on the ground wire was other cause of bad AP behavior that I experienced. This causes glitching and reduced RC range. It has been covered ad nauseam in other posts, but I'll repeat it: it's especially helpful to put an RF choke on the RC RX cable. Try to wrap the wire 4+ times around the choke. Martin P wrote: > Hello everyone! > > Last weekend I had a good AUTO1 flight with my Minimag. It reacted to pitch and roll commands, and I was able to control the throttle. I had an attitude command in my flightplan which was never left (as I know now). > > Yesterday I tried again, without the attitude statement and without a holding point block. > > In AUTO1, it killed the throttle. Switched to manual and landed to change battery because it was not fully charged. > > Took off again. Switched to AUTO1 and it immediately stabilized the plane. Strangely, this time it did not react to the roll command. I flew around using the rudder. When I used the elevator stick, the autopilot controlled the throttle. Good, so far. > > Suddenly the plane dived down vertically from an altitude of roughly 40m. No reaction, just kept going vertical and slowly spinning around the longitudinal axis until it crashed. > > There was not as much damage done as I expected. These foamies are awesome. All RC components including Tiny and Xbee are OK. Except for the Lipo which is badly bent out of shape and will be replaced for safety reasons. > > Unfortunately I can't see much from the log as I had lost the link probably minutes before. I was in stage "HOME" because I had left the fly-too-far circle before and came back manually. > > The switch was on manual so I probably tried to rescue. The Tiny was unplugged which can have happened at the crash or before. One aileron was ripped off and the horizontal IR was missing (I found it in the grass). > > So far, my report. The Minimag is already repaired and I'll keep trying. > > Greetz, Martin > > > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > From MAILER-DAEMON Sun Aug 09 15:00:25 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MaDd3-0006a1-C0 for mharc-paparazzi-devel@gnu.org; Sun, 09 Aug 2009 15:00:25 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MaDd1-0006Yp-1A for paparazzi-devel@nongnu.org; Sun, 09 Aug 2009 15:00:23 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MaDcw-0006Vz-CD for paparazzi-devel@nongnu.org; Sun, 09 Aug 2009 15:00:22 -0400 Received: from [199.232.76.173] (port=49334 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MaDcv-0006Vu-Uz for paparazzi-devel@nongnu.org; Sun, 09 Aug 2009 15:00:17 -0400 Received: from mail.gmx.net ([213.165.64.20]:51839) by monty-python.gnu.org with smtp (Exim 4.60) (envelope-from ) id 1MaDcv-0006EE-89 for paparazzi-devel@nongnu.org; Sun, 09 Aug 2009 15:00:17 -0400 Received: (qmail 19260 invoked by uid 0); 9 Aug 2009 19:00:14 -0000 Received: from 77.119.158.89 by www093.gmx.net with HTTP; Sun, 09 Aug 2009 21:00:12 +0200 (CEST) Content-Type: text/plain; charset="us-ascii" Date: Sun, 09 Aug 2009 21:00:12 +0200 From: "Martin P" In-Reply-To: <4A7EE64A.1030408@free.fr> Message-ID: <20090809190012.54660@gmx.net> MIME-Version: 1.0 References: <20090809074659.23250@gmx.net> <4A7EE64A.1030408@free.fr> Subject: Re: [Paparazzi-devel] AGL and NavSetGroundReferenceHere() To: paparazzi-devel@nongnu.org X-Authenticated: #19891149 X-Flags: 0001 X-Mailer: WWW-Mail 6100 (Global Message Exchange) X-Priority: 3 X-Provags-ID: V01U2FsdGVkX1/J/4AEy4jJs5E32m3dTOFnkEGlPDtXofNzeIE+21 G1+dq0QvAaHfPed1iAZyyl0n06KswV3sxRTg== Content-Transfer-Encoding: 7bit X-GMX-UID: iC5NeWsiPTR+IfqwHjMwIzI5c2tpZEu3 X-FuHaFi: 0.55 X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 3) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Aug 2009 19:00:23 -0000 Hi, thanks for answering! What I call AGL: What is displayed in the GCS. SRTM: I have a file N47E011.hgt.bz2. I am at N47.82 and E16.88. Does this file cover my location? If yes, I would say it is available. If no, where do I get it from? I did a "Google Maps fill". Btw, the terrain here is dead level. Greetings, Martin -------- Original-Nachricht -------- > Datum: Sun, 09 Aug 2009 17:07:54 +0200 > Von: Pascal Brisset > An: paparazzi-devel@nongnu.org > Betreff: Re: [Paparazzi-devel] AGL and NavSetGroundReferenceHere() > Hi, > > what do you call AGL ? > - in the airborne code, NavSetGroundReferenceHere() sets ground_alt to > the current altitude (common_nav.c:84). > This variable is for example use in HOME mode (nav.c:370) or in the > Takeoff and Final block of the basic.xml flight plan. > - in the GCS, AGL is computed by subtracting the terrain altitude (from > the SRTM model ... if the file is available in data/SRTM) from the > current altitude > > --Pascal > > Martin P wrote: > > I use a flight plan with goround_alt=0 (derived from basic.xml). > > After calling NavSetGroundReferenceHere(), I would expect that the AGL > is 0. > > Instead, it is the altitude above sea level. The GPS mode is 3D and the > AGL varies within 3 or 4 meters. > > > > Is this the way it should be? Should I set the ground_alt to the actual > altitude? > > > > > > _______________________________________________ > > Paparazzi-devel mailing list > > Paparazzi-devel@nongnu.org > > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > > > > > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel From MAILER-DAEMON Sun Aug 09 17:29:39 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MaFxT-00027e-OM for mharc-paparazzi-devel@gnu.org; Sun, 09 Aug 2009 17:29:39 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MaFxS-00027A-3M for paparazzi-devel@nongnu.org; Sun, 09 Aug 2009 17:29:38 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MaFxN-00026f-KH for paparazzi-devel@nongnu.org; Sun, 09 Aug 2009 17:29:37 -0400 Received: from [199.232.76.173] (port=48910 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MaFxN-00026a-FM for paparazzi-devel@nongnu.org; Sun, 09 Aug 2009 17:29:33 -0400 Received: from smtp6-g21.free.fr ([212.27.42.6]:46017) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MaFxM-00044z-MC for paparazzi-devel@nongnu.org; Sun, 09 Aug 2009 17:29:33 -0400 Received: from smtp6-g21.free.fr (localhost [127.0.0.1]) by smtp6-g21.free.fr (Postfix) with ESMTP id 8541FE080CB for ; Sun, 9 Aug 2009 23:29:28 +0200 (CEST) Received: from [192.168.0.10] (uni31-1-82-234-59-180.fbx.proxad.net [82.234.59.180]) by smtp6-g21.free.fr (Postfix) with ESMTP id 8C3CBE080C2 for ; Sun, 9 Aug 2009 23:29:26 +0200 (CEST) Message-ID: <4A7F3FB4.9010600@free.fr> Date: Sun, 09 Aug 2009 23:29:24 +0200 From: Pascal Brisset User-Agent: Thunderbird 2.0.0.22 (X11/20090608) MIME-Version: 1.0 To: paparazzi-devel@nongnu.org Subject: Re: [Paparazzi-devel] AGL and NavSetGroundReferenceHere() References: <20090809074659.23250@gmx.net> <4A7EE64A.1030408@free.fr> <20090809190012.54660@gmx.net> In-Reply-To: <20090809190012.54660@gmx.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 3) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Aug 2009 21:29:38 -0000 Hi, you need http://dds.cr.usgs.gov/srtm/version2_1/SRTM3/Eurasia/N47E016.hgt.zip in data/srtm/ --Pascal Martin P wrote: > Hi, thanks for answering! > > What I call AGL: What is displayed in the GCS. > SRTM: I have a file N47E011.hgt.bz2. > I am at N47.82 and E16.88. Does this file cover my location? > If yes, I would say it is available. > If no, where do I get it from? I did a "Google Maps fill". Btw, the terrain here is dead level. > > Greetings, Martin > > -------- Original-Nachricht -------- > >> Datum: Sun, 09 Aug 2009 17:07:54 +0200 >> Von: Pascal Brisset >> An: paparazzi-devel@nongnu.org >> Betreff: Re: [Paparazzi-devel] AGL and NavSetGroundReferenceHere() >> > > >> Hi, >> >> what do you call AGL ? >> - in the airborne code, NavSetGroundReferenceHere() sets ground_alt to >> the current altitude (common_nav.c:84). >> This variable is for example use in HOME mode (nav.c:370) or in the >> Takeoff and Final block of the basic.xml flight plan. >> - in the GCS, AGL is computed by subtracting the terrain altitude (from >> the SRTM model ... if the file is available in data/SRTM) from the >> current altitude >> >> --Pascal >> >> Martin P wrote: >> >>> I use a flight plan with goround_alt=0 (derived from basic.xml). >>> After calling NavSetGroundReferenceHere(), I would expect that the AGL >>> >> is 0. >> >>> Instead, it is the altitude above sea level. The GPS mode is 3D and the >>> >> AGL varies within 3 or 4 meters. >> >>> Is this the way it should be? Should I set the ground_alt to the actual >>> >> altitude? >> >>> _______________________________________________ >>> Paparazzi-devel mailing list >>> Paparazzi-devel@nongnu.org >>> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel >>> >>> >> >> _______________________________________________ >> Paparazzi-devel mailing list >> Paparazzi-devel@nongnu.org >> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel >> > > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > From MAILER-DAEMON Sun Aug 09 23:17:03 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MaLNe-00011y-Rg for mharc-paparazzi-devel@gnu.org; Sun, 09 Aug 2009 23:17:02 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MaLNd-00011L-7k for paparazzi-devel@nongnu.org; Sun, 09 Aug 2009 23:17:01 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MaLNY-0000w3-4n for paparazzi-devel@nongnu.org; Sun, 09 Aug 2009 23:17:00 -0400 Received: from [199.232.76.173] (port=48899 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MaLNX-0000vv-S5 for paparazzi-devel@nongnu.org; Sun, 09 Aug 2009 23:16:55 -0400 Received: from viper.snap.net.nz ([202.37.101.25]:43587) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MaLNW-0001d9-RR for paparazzi-devel@nongnu.org; Sun, 09 Aug 2009 23:16:55 -0400 Received: from IBM2 (215.109.124.202.static.snap.net.nz [202.124.109.215]) by viper.snap.net.nz (Postfix) with SMTP id A1A3F3DA6AF for ; Mon, 10 Aug 2009 14:44:29 +1200 (NZST) Message-ID: From: "Stephen L Hulme" To: Date: Mon, 10 Aug 2009 14:44:26 +1200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_000B_01CA19C9.0EDB1480" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5512 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.4-2.6 Subject: [Paparazzi-devel] Flying X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Aug 2009 03:17:01 -0000 This is a multi-part message in MIME format. ------=_NextPart_000_000B_01CA19C9.0EDB1480 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Dear Pascal Any chance of a photo of the plane? I have a similar Pentax = Optio camera and would consider mounting it if I knew where a good = position could be found i.e. CG neutral etc. RegardsStephen Pascal = wrote: Hi, some answers and pictures in the wiki: http://paparazzi.enac.fr/wiki/Pyrenees_Crossing --Pascal ------=_NextPart_000_000B_01CA19C9.0EDB1480 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Dear Pascal 
 
Any chance of a photo of the =
plane? I have a similar Pentax Optio camera 
and would consider mounting it if I knew where a good position =
could be 
found i.e. CG neutral etc. =
 
Regards
 
Stephen 
 
 
Pascal wrote: 
 
Hi,

some answers and pictures in the =
wiki:

http://paparazzi=
.enac.fr/wiki/Pyrenees_Crossing

--Pascal
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
------=_NextPart_000_000B_01CA19C9.0EDB1480-- From MAILER-DAEMON Mon Aug 10 03:50:44 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MaPeW-0001s5-9Q for mharc-paparazzi-devel@gnu.org; Mon, 10 Aug 2009 03:50:44 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MaPeT-0001mX-9i for paparazzi-devel@nongnu.org; Mon, 10 Aug 2009 03:50:41 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MaPeO-0001es-Jf for paparazzi-devel@nongnu.org; Mon, 10 Aug 2009 03:50:40 -0400 Received: from [199.232.76.173] (port=42488 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MaPeO-0001ep-Cj for paparazzi-devel@nongnu.org; Mon, 10 Aug 2009 03:50:36 -0400 Received: from mx20.gnu.org ([199.232.41.8]:24064) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MaPeN-0003da-OK for paparazzi-devel@nongnu.org; Mon, 10 Aug 2009 03:50:36 -0400 Received: from mail-bw0-f227.google.com ([209.85.218.227]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MaPeL-0007IM-IM for paparazzi-devel@nongnu.org; Mon, 10 Aug 2009 03:50:34 -0400 Received: by bwz27 with SMTP id 27so2347130bwz.34 for ; Mon, 10 Aug 2009 00:50:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type; bh=iONflNn6V895Zu6w7rEryIlQHMTReIhDSmpaQMs42h8=; b=DEfvUFQV55mXb71HMu4zmpB1SYR2FpCmdKsEqrerqWMqVsN0v4d/PGLFyaDhKiOGwt AMaMZFNLlfs/8i2vDTkJSSwr+Y03RaKv3FLGBGqYBP8YqWQp8Oy5uZ1APUvPirqpZX0t ccQru5ifoTKx3FiQcFifQkARbaEAutlKsmr1o= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=bbfd/F+7UPDYW22XWDtSV0GjgFQcBlz7IwcD1Hn0651G1rZXDzbKB65Ci4X4NhZyR5 WReoRlB1KDYgeER1cSfs4dAcqcDy3RVxBLjvvtFTqQ9T+Hxo0Sxz5xGZZ1CSVb1z8215 mC6SNwsENe20PhLOaUJ+izq8/RTb1MnFbRMVI= MIME-Version: 1.0 Sender: adam.spence@gmail.com Received: by 10.204.101.207 with SMTP id d15mr5360336bko.93.1249890630048; Mon, 10 Aug 2009 00:50:30 -0700 (PDT) In-Reply-To: <4A7F09D7.8030601@u.washington.edu> References: <20090809081748.23240@gmx.net> <4A7F09D7.8030601@u.washington.edu> Date: Mon, 10 Aug 2009 08:50:30 +0100 X-Google-Sender-Auth: 2ce119110b05bd8e Message-ID: Subject: Re: [Paparazzi-devel] crashed From: Adam Spence <4x4Ninja@gmail.com> To: paparazzi-devel@nongnu.org Content-Type: multipart/alternative; boundary=0016e6de17da031a930470c4d779 X-Detected-Operating-System: by mx20.gnu.org: GNU/Linux 2.6 (newer, 2) X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6, seldom 2.4 (older, 4) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Aug 2009 07:50:42 -0000 --0016e6de17da031a930470c4d779 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit John, what are you referring to with the RC RX cable? Is this the PPM cable attaching the receiver to PPZ? There's been a couple of crashes like this discussed on IRC recently. I'm not sure if the fault was identified but the overloading of the 5v PSU was suggested. This could easily happen when the servos are driven to the limit and stall due to the hardware set up. Where ever possible the currents drawn by the servos need to be measured when all control surfaces are at the limit. If there are any stall conditions the setup needs to be adjusted either physically on the air frame or by reducing the control throws in the config file. The 5V PSU is not only responsible for supplying the servo power but also the 3v3 regulators power! Therefore if the 5v line drops due to too much current being drawn then it may take out the main CPU. For my particular setup with an 868 modem, the CPU, GPS and Modem can take upto 500mA of current. The limit of the 5V PSU is 2.25A so roughly there may be something in the region of 1.75A left for all of the servos. That only needs a couple of servos to stall and you could be in trouble. Due to the above, I will be removing the 5V connection to the servos and providing another regulated 5v directly from the battery. This will have a limit of maybe 5-10A which is complete over kill. I've just noticed the current-limiting switch on the hardware, this means the servos can only draw 1A and then the switch kicks in and notifies the CPU using GPIO. Does anyone know what the firmware does in this instance? That therefore means that there's even less current available for the servos and anything else which you may have connected on the 5v rail... hmmm. I see this can trigger from 0.5A to 1.25A, anyone ever tested this? I'm wondering now what would happen if this were to fire, the servos would be left in their current position (or driven back slightly from mechanical pressure). The AP might (depending on what the GPIO signal does) try and keep driving the servos at their current position which would mean that when the current limiter recovers it then goes straight to the limit again? Anyway I've rambled enough this morning! Adam 2009/8/9 John Burt > Martin, > > I crashed an Easystar just like that during early flight testing. The AP > (Tiny 2.11) went nonresponsive and dived into the ground, despite my having > immediately flipped the switch to manual. It would seem that the AP > processor just locked up - truly a worst case scenario. The cause of the > behavior was an undervoltage spike condition due to sourcing the four servos > and RC RX off the 5V supply. In case you haven't already, you should always > power your hardware off a separate BEC (which begs the question of why the > AP has a 5V source anyway). > > AP generated noise on the ground wire was other cause of bad AP behavior > that I experienced. This causes glitching and reduced RC range. It has been > covered ad nauseam in other posts, but I'll repeat it: it's especially > helpful to put an RF choke on the RC RX cable. Try to wrap the wire 4+ times > around the choke. > > > Martin P wrote: > >> Hello everyone! >> Last weekend I had a good AUTO1 flight with my Minimag. It reacted to >> pitch and roll commands, and I was able to control the throttle. I had an >> attitude command in my flightplan which was never left (as I know now). >> Yesterday I tried again, without the attitude statement and without a >> holding point block. >> In AUTO1, it killed the throttle. Switched to manual and landed to change >> battery because it was not fully charged. >> Took off again. Switched to AUTO1 and it immediately stabilized the plane. >> Strangely, this time it did not react to the roll command. I flew around >> using the rudder. When I used the elevator stick, the autopilot controlled >> the throttle. Good, so far. >> Suddenly the plane dived down vertically from an altitude of roughly 40m. >> No reaction, just kept going vertical and slowly spinning around the >> longitudinal axis until it crashed. >> There was not as much damage done as I expected. These foamies are >> awesome. All RC components including Tiny and Xbee are OK. Except for the >> Lipo which is badly bent out of shape and will be replaced for safety >> reasons. >> Unfortunately I can't see much from the log as I had lost the link >> probably minutes before. I was in stage "HOME" because I had left the >> fly-too-far circle before and came back manually. >> The switch was on manual so I probably tried to rescue. The Tiny was >> unplugged which can have happened at the crash or before. One aileron was >> ripped off and the horizontal IR was missing (I found it in the grass). >> So far, my report. The Minimag is already repaired and I'll keep trying. >> Greetz, Martin >> >> >> _______________________________________________ >> Paparazzi-devel mailing list >> Paparazzi-devel@nongnu.org >> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel >> >> > > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > --0016e6de17da031a930470c4d779 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
John, what are you referring to with the RC RX cable? Is this the PPM = cable attaching the receiver to PPZ?

There's been a= couple of crashes like this discussed on IRC recently. I'm not sure if= the fault was identified but the overloading of the 5v PSU was suggested. = This could easily happen when the servos are driven to the limit and stall = due to the hardware set up. Where ever possible the currents drawn by the s= ervos need to be measured when all control surfaces are at the limit. If th= ere are any stall conditions the setup needs to be adjusted either physical= ly on the air frame or by reducing the control throws in the config file.
The 5V PSU is not only responsible for supplying the servo p= ower but also the 3v3 regulators power! Therefore if the 5v line drops due = to too much current being drawn then it may take out the main CPU. For my p= articular setup with an 868 modem, the CPU, GPS and Modem can take upto 500= mA of current. The limit of the 5V PSU is 2.25A so roughly there may be som= ething in the region of 1.75A left for all of the servos. That only needs a= couple of servos to stall and you could be in trouble.

Due to the above, I will be removing the 5V connection = to the servos and providing another regulated 5v directly from the battery.= This will have a limit of maybe 5-10A which is complete over kill.

I've just noticed the current-limiting switch on th= e hardware, this means the servos can only draw 1A and then the switch kick= s in and notifies the CPU using GPIO. Does anyone know what the firmware do= es in this instance? That therefore means that there's even less curren= t available for the servos and anything else which you may have connected o= n the 5v rail... hmmm. I see this can trigger from 0.5A to 1.25A, anyone ev= er tested this? I'm wondering now what would happen if this were to fir= e, the servos would be left in their current position (or driven back sligh= tly from mechanical pressure). The AP might (depending on what the GPIO sig= nal does) try and keep driving the servos at their current position which w= ould mean that when the current limiter recovers it then goes straight to t= he limit again?

Anyway I've rambled enough this morning!
=
Adam=A0

2009/8/9 John= Burt <quill= @u.washington.edu>
Martin,

I crashed an Easystar just like that during early flight testing. The AP (T= iny 2.11) went nonresponsive and dived into the ground, despite my having i= mmediately flipped the switch to manual. It would seem that the AP processo= r just locked up - truly a worst case scenario. The cause of the behavior w= as an undervoltage spike condition due to sourcing the four servos and RC R= X off the 5V supply. In case you haven't already, you should always pow= er your hardware off a separate BEC (which begs the question of why the AP = has a 5V source anyway).

AP generated noise on the ground wire was other cause of bad AP behavior th= at I experienced. This causes glitching and reduced RC range. It has been c= overed ad nauseam in other posts, but I'll repeat it: it's especial= ly helpful to put an RF choke on the RC RX cable. Try to wrap the wire 4+ t= imes around the choke.


Martin P wrote:
Hello everyone!
Last weekend I had a good AUTO1 flight with my Minimag. It reacted to pitch= and roll commands, and I was able to control the throttle. I had an attitu= de command in my flightplan which was never left (as I know now). =A0
Yesterday I tried again, without the attitude statement and without a holdi= ng point block.
In AUTO1, it killed the throttle. Switched to manual and landed to change b= attery because it was not fully charged.
Took off again. Switched to AUTO1 and it immediately stabilized the plane. = Strangely, this time it did not react to the roll command. I flew around us= ing the rudder. When I used the elevator stick, the autopilot controlled th= e throttle. Good, so far.
Suddenly the plane dived down vertically from an altitude of roughly 40m. N= o reaction, just kept going vertical and slowly spinning around the longitu= dinal axis until it crashed.
There was not as much damage done as I expected. These foamies are awesome.= All RC components including Tiny and Xbee are OK. Except for the Lipo whic= h is badly bent out of shape and will be replaced for safety reasons.
Unfortunately I can't see much from the log as I had lost the link prob= ably minutes before. I was in stage "HOME" because I had left the= fly-too-far circle before and came back manually. =A0
The switch was on manual so I probably tried to rescue. The Tiny was unplug= ged which can have happened at the crash or before. One aileron was ripped = off and the horizontal IR was missing (I found it in the grass).
So far, my report. The Minimag is already repaired and I'll keep trying= .
Greetz, Martin


_______________________________________________
Paparazzi-devel mailing list
Paparazzi-d= evel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/paparazzi-devel =A0


_______________________________________________
Paparazzi-devel mailing list
Paparazzi-d= evel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/paparazzi-devel

--0016e6de17da031a930470c4d779-- From MAILER-DAEMON Mon Aug 10 04:15:04 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MaQ23-00012F-UH for mharc-paparazzi-devel@gnu.org; Mon, 10 Aug 2009 04:15:03 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MaQ21-00011M-Bd for paparazzi-devel@nongnu.org; Mon, 10 Aug 2009 04:15:01 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MaQ1w-0000w3-JC for paparazzi-devel@nongnu.org; Mon, 10 Aug 2009 04:15:00 -0400 Received: from [199.232.76.173] (port=36235 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MaQ1w-0000vs-Fg for paparazzi-devel@nongnu.org; Mon, 10 Aug 2009 04:14:56 -0400 Received: from rv-out-0708.google.com ([209.85.198.246]:14875) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MaQ1w-0006Ej-1u for paparazzi-devel@nongnu.org; Mon, 10 Aug 2009 04:14:56 -0400 Received: by rv-out-0708.google.com with SMTP id b17so747970rvf.22 for ; Mon, 10 Aug 2009 01:14:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=XZOjBRNILRtCgfnqoNES46zPrTFEu4i6oRjp0f0F5Lw=; b=gamrxoHAyfDGbHeiK/HQSnhZFhuRnWvBsAIw1qv3MswEfSgXtldkr6FqqY1Qwjzgtj z4Io70Ycq8CycaS1/4nNeh5qw670K1unxmxdDNo10Pk9/jKRgxXXDTme4b7eyBLcNrXd uFVuWZbX2AZUKz7RyGcoepklSNOwdD9hhSjao= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=I5j8YL9RnwfnZW5nr6C2kWxyhMf6n1UsHc/UwYDSe+a4/4mFBFZpbj+z7rfaYDwakf CdQcALTmIYpV4M2Y5KE2dYoLU++vYZhvWE5XwsKJ+pnOqJuSq562/BFtYTB9zmZ8vyEr iURTdIqSdZcFF86lvcGne5noUz9MsxKWy+oNA= MIME-Version: 1.0 Received: by 10.140.170.12 with SMTP id s12mr1532452rve.278.1249892094315; Mon, 10 Aug 2009 01:14:54 -0700 (PDT) Date: Mon, 10 Aug 2009 16:14:54 +0800 Message-ID: <2f88794c0908100114o177af4f2va83c7445d378b398@mail.gmail.com> From: =?GB2312?B?za/A2g==?= To: paparazzi-devel@nongnu.org Content-Type: multipart/alternative; boundary=000e0cd2c14a4a0fd40470c52e97 X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) Subject: [Paparazzi-devel] Airframe debug problem,stop at ap.elf X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Aug 2009 08:15:01 -0000 --000e0cd2c14a4a0fd40470c52e97 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi, I had problem when trying to remove lines of Gyro from the airframe file.Debuging always stopped at LD /home/mnw/paparazzi3/var/mnwAC/ap/ap.elf,I couldn't figure out why.I'v put the airframe file here http://pastebin.com/m6cb0a486. Help me out. Thanks all. --000e0cd2c14a4a0fd40470c52e97 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,
=A0 I had problem when trying to remove lines of Gyro from the airfr= ame file.Debuging always stopped at LD /home/mnw/paparazzi3/var/mnwAC/ap/ap= .elf,I couldn't figure out why.I'v put the airframe file here http://pastebin.com/m6cb0a486.
=A0 Help me out.

Thanks all.
--000e0cd2c14a4a0fd40470c52e97-- From MAILER-DAEMON Mon Aug 10 06:37:34 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MaSFy-0001II-Hp for mharc-paparazzi-devel@gnu.org; Mon, 10 Aug 2009 06:37:34 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MaSFw-0001I8-Sz for paparazzi-devel@nongnu.org; Mon, 10 Aug 2009 06:37:32 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MaSFw-0001Ht-0n for paparazzi-devel@nongnu.org; Mon, 10 Aug 2009 06:37:32 -0400 Received: from [199.232.76.173] (port=40274 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MaSFv-0001Hq-TZ for paparazzi-devel@nongnu.org; Mon, 10 Aug 2009 06:37:31 -0400 Received: from mx20.gnu.org ([199.232.41.8]:36220) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MaSFv-0003dF-DI for paparazzi-devel@nongnu.org; Mon, 10 Aug 2009 06:37:31 -0400 Received: from ey-out-1920.google.com ([74.125.78.148]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MaSFt-0004zh-2u for paparazzi-devel@nongnu.org; Mon, 10 Aug 2009 06:37:29 -0400 Received: by ey-out-1920.google.com with SMTP id 5so689635eyb.4 for ; Mon, 10 Aug 2009 03:37:23 -0700 (PDT) Received: by 10.210.17.16 with SMTP id 16mr5080522ebq.17.1249900643802; Mon, 10 Aug 2009 03:37:23 -0700 (PDT) Received: from server ([41.182.154.20]) by mx.google.com with ESMTPS id 28sm8142453eye.24.2009.08.10.03.37.20 (version=SSLv3 cipher=RC4-MD5); Mon, 10 Aug 2009 03:37:22 -0700 (PDT) From: "gisela.noci" To: , References: <20090809081748.23240@gmx.net> <4A7F09D7.8030601@u.washington.edu> Subject: RE: [Paparazzi-devel] crashed Date: Mon, 10 Aug 2009 12:37:09 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 Thread-Index: AcoZGHU4ev5i0elWTu6EUN/hrFJ/IAAjSs1Q In-Reply-To: <4A7F09D7.8030601@u.washington.edu> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 X-Detected-Operating-System: by mx20.gnu.org: GNU/Linux 2.6 (newer, 2) X-detected-operating-system: by monty-python.gnu.org: Error: [-] ERROR: /var/run/p0f.sock: Connection refused Cc: X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Aug 2009 10:37:33 -0000 Just a comment on the RF choke on the RX cable.... This is NOT a good idea, since the RCS received signal will suffer the same attenuation within its bandpass as would the 'interfering' signals. The signal to noise ratio would simply remain in the same, but with reduced receiver sensitivity. Any interfering signals within the receiver bandpass CANNOT be filtered (choked)out. These signals can only be eliminated at source, such as by proper system ground design, and probable shielding of the offending noise generator. Joe -----Original Message----- From: paparazzi-devel-bounces+gisela.noci=ate-international.com@nongnu.org [mailto:paparazzi-devel-bounces+gisela.noci=ate-international.com@nongnu.org ] On Behalf Of John Burt Sent: Sunday, August 09, 2009 7:40 PM To: paparazzi-devel@nongnu.org Subject: Re: [Paparazzi-devel] crashed Martin, I crashed an Easystar just like that during early flight testing. The AP (Tiny 2.11) went nonresponsive and dived into the ground, despite my having immediately flipped the switch to manual. It would seem that the AP processor just locked up - truly a worst case scenario. The cause of the behavior was an undervoltage spike condition due to sourcing the four servos and RC RX off the 5V supply. In case you haven't already, you should always power your hardware off a separate BEC (which begs the question of why the AP has a 5V source anyway). AP generated noise on the ground wire was other cause of bad AP behavior that I experienced. This causes glitching and reduced RC range. It has been covered ad nauseam in other posts, but I'll repeat it: it's especially helpful to put an RF choke on the RC RX cable. Try to wrap the wire 4+ times around the choke. Martin P wrote: > Hello everyone! > > Last weekend I had a good AUTO1 flight with my Minimag. It reacted to pitch and roll commands, and I was able to control the throttle. I had an attitude command in my flightplan which was never left (as I know now). > > Yesterday I tried again, without the attitude statement and without a holding point block. > > In AUTO1, it killed the throttle. Switched to manual and landed to change battery because it was not fully charged. > > Took off again. Switched to AUTO1 and it immediately stabilized the plane. Strangely, this time it did not react to the roll command. I flew around using the rudder. When I used the elevator stick, the autopilot controlled the throttle. Good, so far. > > Suddenly the plane dived down vertically from an altitude of roughly 40m. No reaction, just kept going vertical and slowly spinning around the longitudinal axis until it crashed. > > There was not as much damage done as I expected. These foamies are awesome. All RC components including Tiny and Xbee are OK. Except for the Lipo which is badly bent out of shape and will be replaced for safety reasons. > > Unfortunately I can't see much from the log as I had lost the link probably minutes before. I was in stage "HOME" because I had left the fly-too-far circle before and came back manually. > > The switch was on manual so I probably tried to rescue. The Tiny was unplugged which can have happened at the crash or before. One aileron was ripped off and the horizontal IR was missing (I found it in the grass). > > So far, my report. The Minimag is already repaired and I'll keep trying. > > Greetz, Martin > > > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > _______________________________________________ Paparazzi-devel mailing list Paparazzi-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/paparazzi-devel From MAILER-DAEMON Mon Aug 10 07:52:48 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MaTQm-0002p1-EZ for mharc-paparazzi-devel@gnu.org; Mon, 10 Aug 2009 07:52:48 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MaTQl-0002od-9h for paparazzi-devel@nongnu.org; Mon, 10 Aug 2009 07:52:47 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MaTQg-0002mj-Iu for paparazzi-devel@nongnu.org; Mon, 10 Aug 2009 07:52:46 -0400 Received: from [199.232.76.173] (port=56440 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MaTQg-0002mT-Cn for paparazzi-devel@nongnu.org; Mon, 10 Aug 2009 07:52:42 -0400 Received: from mail-fx0-f207.google.com ([209.85.220.207]:37341) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MaTQf-0000CJ-S1 for paparazzi-devel@nongnu.org; Mon, 10 Aug 2009 07:52:42 -0400 Received: by fxm3 with SMTP id 3so4224824fxm.8 for ; Mon, 10 Aug 2009 04:52:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:content-type :content-transfer-encoding; bh=hvXoSSNO764LR/rY7tCxN1hZgBByzyOGdXJaramWFCs=; b=ZTc2aTVCx/3F/8/DcUwQBnrdzrXwo35fECOyVv9gboIbZlj/v5ClshRCzAZ7rCJhJ8 rXebcJq9ZqIOM7MmmsSSc1rPY6HCC3MqlKtXjVUMp+z/syZcKq5N5H6oWCXlvgOzPExX /U1r1IS/0n0q688AclnJq1p6ZQ0xn5kQw1VV8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; b=bbgmrN/gZHrhnanVo1a+E4Fz4aFvjWFJHpgFRP9pUQuozbGZyE49b1mSTDBMwqQ740 rH6ad0EY5KrGmFgOk/2lVR8n+73JtFyJemcYBqUFNDlGIUc2fOC9m/DcgHPUwuNuZa41 QSkFkCpzFAMkv7KjiJ4o349A+cUqLvs3Al94A= Received: by 10.204.122.141 with SMTP id l13mr1739944bkr.104.1249905159237; Mon, 10 Aug 2009 04:52:39 -0700 (PDT) Received: from ?192.168.1.2? ([88.218.149.158]) by mx.google.com with ESMTPS id b17sm6606177fka.6.2009.08.10.04.52.36 (version=SSLv3 cipher=RC4-MD5); Mon, 10 Aug 2009 04:52:37 -0700 (PDT) Message-ID: <4A800A03.6010508@gmail.com> Date: Mon, 10 Aug 2009 14:52:35 +0300 From: chris User-Agent: Thunderbird 2.0.0.22 (X11/20090608) MIME-Version: 1.0 To: paparazzi-devel@nongnu.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) Subject: [Paparazzi-devel] Pentax optio X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Aug 2009 11:52:47 -0000 Hi. I have used the Pentax optio 60 but i found that even powering up the camera close to the paparazzi board (tiny 2.11) the GPS looses the signal. There was no electrical connection between the camera and the autopilot. I thought it would be a good idea to mention this. Chris From MAILER-DAEMON Mon Aug 10 12:00:14 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MaXID-0002tc-NW for mharc-paparazzi-devel@gnu.org; Mon, 10 Aug 2009 12:00:13 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MaXI7-0002ra-OP for paparazzi-devel@nongnu.org; Mon, 10 Aug 2009 12:00:07 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MaXI3-0002qL-Lk for paparazzi-devel@nongnu.org; Mon, 10 Aug 2009 12:00:07 -0400 Received: from [199.232.76.173] (port=54310 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MaXI3-0002qI-7A for paparazzi-devel@nongnu.org; Mon, 10 Aug 2009 12:00:03 -0400 Received: from mxout2.cac.washington.edu ([140.142.33.4]:58606) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MaXI1-0003X1-5r for paparazzi-devel@nongnu.org; Mon, 10 Aug 2009 12:00:02 -0400 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9] (may be forged)) by mxout2.cac.washington.edu (8.14.3+UW09.06/8.14.3+UW09.05) with ESMTP id n7AFxwf4014501 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Mon, 10 Aug 2009 08:59:58 -0700 X-Auth-Received: from [192.168.1.109] (c-76-27-232-248.hsd1.or.comcast.net [76.27.232.248]) (authenticated authid=quill) by smtp.washington.edu (8.14.3+UW09.06/8.14.3+UW09.05) with ESMTP id n7AFxvUP022377 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Mon, 10 Aug 2009 08:59:57 -0700 Message-ID: <4A8043E1.4050107@u.washington.edu> Date: Mon, 10 Aug 2009 08:59:29 -0700 From: John Burt User-Agent: Thunderbird 2.0.0.22 (Windows/20090605) MIME-Version: 1.0 To: paparazzi-devel@nongnu.org Subject: Re: [Paparazzi-devel] crashed, 5V supply overloading issue References: <20090809081748.23240@gmx.net> <4A7F09D7.8030601@u.washington.edu> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-PMX-Version: 5.5.7.378829, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2009.8.10.155116 X-Uwash-Spam: Gauge=X, Probability=10%, Report=' TO_IN_SUBJECT 0.5, BODY_SIZE_6000_6999 0, BODY_SIZE_7000_LESS 0, TO_NO_NAME 0, __BOUNCE_CHALLENGE_SUBJ 0, __CP_NOT_1 0, __CP_URI_IN_BODY 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __FRAUD_419_BADTHINGS 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __MOZILLA_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __URI_NS , __USER_AGENT 0' X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.4-2.6 X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Aug 2009 16:00:08 -0000 Yes, I am referring to the PPM signal from the RC receiver to PPZ. It was pretty clear that the fault was due to an overloaded 5V supply. On the ground I was able to faithfully re-create the AP crash conditions simply by rapidly exercising all the servos. I also did fairly extensive testing to debug this problem, including measuring current drain with all servos operating, which is what clarified the issue. I have suggested in the past that PPZ be updated with a higher capacity 5V converter, and given what you wrote below, it might also be a good thing to source the 3.3v line off the battery, rather than the 5V supply. However, the "temporary" solution is to simply use a separate 5V supply for external devices like servos, modems, etc. Adam Spence wrote: > John, what are you referring to with the RC RX cable? Is this the PPM > cable attaching the receiver to PPZ? > > There's been a couple of crashes like this discussed on IRC recently. > I'm not sure if the fault was identified but the overloading of the 5v > PSU was suggested. This could easily happen when the servos are driven > to the limit and stall due to the hardware set up. Where ever possible > the currents drawn by the servos need to be measured when all control > surfaces are at the limit. If there are any stall conditions the setup > needs to be adjusted either physically on the air frame or by reducing > the control throws in the config file. > > The 5V PSU is not only responsible for supplying the servo power but > also the 3v3 regulators power! Therefore if the 5v line drops due to too > much current being drawn then it may take out the main CPU. For my > particular setup with an 868 modem, the CPU, GPS and Modem can take upto > 500mA of current. The limit of the 5V PSU is 2.25A so roughly there may > be something in the region of 1.75A left for all of the servos. That > only needs a couple of servos to stall and you could be in trouble. > > Due to the above, I will be removing the 5V connection to the servos and > providing another regulated 5v directly from the battery. This will have > a limit of maybe 5-10A which is complete over kill. > > I've just noticed the current-limiting switch on the hardware, this > means the servos can only draw 1A and then the switch kicks in and > notifies the CPU using GPIO. Does anyone know what the firmware does in > this instance? That therefore means that there's even less current > available for the servos and anything else which you may have connected > on the 5v rail... hmmm. I see this can trigger from 0.5A to 1.25A, > anyone ever tested this? I'm wondering now what would happen if this > were to fire, the servos would be left in their current position (or > driven back slightly from mechanical pressure). The AP might (depending > on what the GPIO signal does) try and keep driving the servos at their > current position which would mean that when the current limiter recovers > it then goes straight to the limit again? > > Anyway I've rambled enough this morning! > > Adam > > 2009/8/9 John Burt > > > Martin, > > I crashed an Easystar just like that during early flight testing. > The AP (Tiny 2.11) went nonresponsive and dived into the ground, > despite my having immediately flipped the switch to manual. It would > seem that the AP processor just locked up - truly a worst case > scenario. The cause of the behavior was an undervoltage spike > condition due to sourcing the four servos and RC RX off the 5V > supply. In case you haven't already, you should always power your > hardware off a separate BEC (which begs the question of why the AP > has a 5V source anyway). > > AP generated noise on the ground wire was other cause of bad AP > behavior that I experienced. This causes glitching and reduced RC > range. It has been covered ad nauseam in other posts, but I'll > repeat it: it's especially helpful to put an RF choke on the RC RX > cable. Try to wrap the wire 4+ times around the choke. > > > Martin P wrote: > > Hello everyone! > Last weekend I had a good AUTO1 flight with my Minimag. It > reacted to pitch and roll commands, and I was able to control > the throttle. I had an attitude command in my flightplan which > was never left (as I know now). > Yesterday I tried again, without the attitude statement and > without a holding point block. > In AUTO1, it killed the throttle. Switched to manual and landed > to change battery because it was not fully charged. > Took off again. Switched to AUTO1 and it immediately stabilized > the plane. Strangely, this time it did not react to the roll > command. I flew around using the rudder. When I used the > elevator stick, the autopilot controlled the throttle. Good, so > far. > Suddenly the plane dived down vertically from an altitude of > roughly 40m. No reaction, just kept going vertical and slowly > spinning around the longitudinal axis until it crashed. > There was not as much damage done as I expected. These foamies > are awesome. All RC components including Tiny and Xbee are OK. > Except for the Lipo which is badly bent out of shape and will be > replaced for safety reasons. > Unfortunately I can't see much from the log as I had lost the > link probably minutes before. I was in stage "HOME" because I > had left the fly-too-far circle before and came back manually. > The switch was on manual so I probably tried to rescue. The Tiny > was unplugged which can have happened at the crash or before. > One aileron was ripped off and the horizontal IR was missing (I > found it in the grass). > So far, my report. The Minimag is already repaired and I'll keep > trying. > Greetz, Martin > > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > > > > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > > > > ------------------------------------------------------------------------ > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel From MAILER-DAEMON Mon Aug 10 12:47:40 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MaY28-0000m4-Pw for mharc-paparazzi-devel@gnu.org; Mon, 10 Aug 2009 12:47:40 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MaY28-0000lq-7c for paparazzi-devel@nongnu.org; Mon, 10 Aug 2009 12:47:40 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MaY23-0000kA-LI for paparazzi-devel@nongnu.org; Mon, 10 Aug 2009 12:47:39 -0400 Received: from [199.232.76.173] (port=41450 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MaY23-0000k5-FW for paparazzi-devel@nongnu.org; Mon, 10 Aug 2009 12:47:35 -0400 Received: from gwise-al5.server.gvsu.edu ([148.61.8.25]:21604 helo=gvsu.edu) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MaY23-0001JT-0P for paparazzi-devel@nongnu.org; Mon, 10 Aug 2009 12:47:35 -0400 Received: from SMTPDOM-MTA by gvsu.edu with Novell_GroupWise; Mon, 10 Aug 2009 12:47:21 -0400 Message-Id: <4A8016AE.BCAB.0027.0@gvsu.edu> X-Mailer: Novell GroupWise Internet Agent 7.0.2 HP Date: Mon, 10 Aug 2009 12:46:38 -0400 From: "John Koches" To: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="=__Part1239D5FE.0__=" X-detected-operating-system: by monty-python.gnu.org: Novell Netware 6 SP3 Subject: [Paparazzi-devel] Re: Flying X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Aug 2009 16:47:40 -0000 --=__Part1239D5FE.0__= Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Pascal: =20 Again, congratulations on your recent accomplishment. My work requires = flights along shorelines and up rivers and streams. I was wondering about = the logistics associated with your Pyrenees Crossing. =20 =20 Do you have a separate team with their own ground control station and = radio control transmitter at the other end of a long flight plan? It = seems like the only practical way of handling the distance, but I have = never tried planning a mission that didn't return home. I was hoping you = could elaborate. =20 jkk --=__Part1239D5FE.0__= Content-Type: text/html; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Content-Description: HTML
Pascal:
 
Again, congratulations on your recent accomplishment.  My work = requires flights along shorelines and up rivers and streams.  I was = wondering about the logistics associated with your Pyrenees Crossing. =
 
Do you have a separate team with their own ground control station and = radio control transmitter at the other end of a long flight plan?  It = seems like the only practical way of handling the distance, but I have = never tried planning a mission that didn't return home.  I was = hoping you could elaborate.
 
jkk
--=__Part1239D5FE.0__=-- From MAILER-DAEMON Mon Aug 10 13:13:41 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MaYRI-0002Us-Uw for mharc-paparazzi-devel@gnu.org; Mon, 10 Aug 2009 13:13:41 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MaYRH-0002UR-G2 for paparazzi-devel@nongnu.org; Mon, 10 Aug 2009 13:13:39 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MaYRD-0002T6-Du for paparazzi-devel@nongnu.org; Mon, 10 Aug 2009 13:13:39 -0400 Received: from [199.232.76.173] (port=35800 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MaYRD-0002Sw-5Q for paparazzi-devel@nongnu.org; Mon, 10 Aug 2009 13:13:35 -0400 Received: from bay0-omc3-s36.bay0.hotmail.com ([65.54.246.236]:23826) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MaYRC-0006bl-LE for paparazzi-devel@nongnu.org; Mon, 10 Aug 2009 13:13:35 -0400 Received: from BAY119-W48 ([207.46.9.83]) by bay0-omc3-s36.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 10 Aug 2009 10:13:32 -0700 Message-ID: Content-Type: multipart/alternative; boundary="_b909ee30-7b4f-44fd-9d80-8c85208a60cd_" X-Originating-IP: [206.172.0.196] From: Yves Touchette To: Subject: RE: [Paparazzi-devel] crashed, 5V supply overloading issue Date: Mon, 10 Aug 2009 13:13:32 -0400 Importance: Normal In-Reply-To: <4A8043E1.4050107@u.washington.edu> References: <20090809081748.23240@gmx.net> <4A7F09D7.8030601@u.washington.edu> <4A8043E1.4050107@u.washington.edu> MIME-Version: 1.0 X-OriginalArrivalTime: 10 Aug 2009 17:13:32.0818 (UTC) FILETIME=[E3771720:01CA19DD] X-detected-operating-system: by monty-python.gnu.org: Windows 2000 SP4, XP SP1+ X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Aug 2009 17:13:39 -0000 --_b909ee30-7b4f-44fd-9d80-8c85208a60cd_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I personnally think that the best solution is not to power the servos from = the AP=2C period.=20 How about designing a PCB that would contain a servo demux (like a 4017)=2C= be powered by the ESC BEC and have pads for both .1" connectors (regular s= ervos) and for pico blade connectors? Many of the newer good quality ESC have switching BEC's that are more then = capable of driving a reasonable server load. Running of the BEC will also prevent power related crashs. The BEC is alrea= dy in most planes. Those that don't have one (glow engins=2C etc) could use= an external BEC. This should be pretty easy to build without having to reroute a complete AP= . The two sets of connectors would alow users to choose which they prefer and= install only those. Does this sound good? -yvest > Date: Mon=2C 10 Aug 2009 08:59:29 -0700 > From: quill@u.washington.edu > To: paparazzi-devel@nongnu.org > Subject: Re: [Paparazzi-devel] crashed=2C 5V supply overloading issue >=20 > Yes=2C I am referring to the PPM signal from the RC receiver to PPZ. >=20 > It was pretty clear that the fault was due to an overloaded 5V supply.=20 > On the ground I was able to faithfully re-create the AP crash conditions= =20 > simply by rapidly exercising all the servos. I also did fairly extensive= =20 > testing to debug this problem=2C including measuring current drain with=20 > all servos operating=2C which is what clarified the issue. >=20 > I have suggested in the past that PPZ be updated with a higher capacity=20 > 5V converter=2C and given what you wrote below=2C it might also be a good= =20 > thing to source the 3.3v line off the battery=2C rather than the 5V=20 > supply. However=2C the "temporary" solution is to simply use a separate 5= V=20 > supply for external devices like servos=2C modems=2C etc. >=20 > Adam Spence wrote: > > John=2C what are you referring to with the RC RX cable? Is this the PPM= =20 > > cable attaching the receiver to PPZ? > >=20 > > There's been a couple of crashes like this discussed on IRC recently.=20 > > I'm not sure if the fault was identified but the overloading of the 5v= =20 > > PSU was suggested. This could easily happen when the servos are driven= =20 > > to the limit and stall due to the hardware set up. Where ever possible= =20 > > the currents drawn by the servos need to be measured when all control=20 > > surfaces are at the limit. If there are any stall conditions the setup= =20 > > needs to be adjusted either physically on the air frame or by reducing= =20 > > the control throws in the config file. > >=20 > > The 5V PSU is not only responsible for supplying the servo power but=20 > > also the 3v3 regulators power! Therefore if the 5v line drops due to to= o=20 > > much current being drawn then it may take out the main CPU. For my=20 > > particular setup with an 868 modem=2C the CPU=2C GPS and Modem can take= upto=20 > > 500mA of current. The limit of the 5V PSU is 2.25A so roughly there may= =20 > > be something in the region of 1.75A left for all of the servos. That=20 > > only needs a couple of servos to stall and you could be in trouble. > >=20 > > Due to the above=2C I will be removing the 5V connection to the servos = and=20 > > providing another regulated 5v directly from the battery. This will hav= e=20 > > a limit of maybe 5-10A which is complete over kill. > >=20 > > I've just noticed the current-limiting switch on the hardware=2C this=20 > > means the servos can only draw 1A and then the switch kicks in and=20 > > notifies the CPU using GPIO. Does anyone know what the firmware does in= =20 > > this instance? That therefore means that there's even less current=20 > > available for the servos and anything else which you may have connected= =20 > > on the 5v rail... hmmm. I see this can trigger from 0.5A to 1.25A=2C=20 > > anyone ever tested this? I'm wondering now what would happen if this=20 > > were to fire=2C the servos would be left in their current position (or= =20 > > driven back slightly from mechanical pressure). The AP might (depending= =20 > > on what the GPIO signal does) try and keep driving the servos at their= =20 > > current position which would mean that when the current limiter recover= s=20 > > it then goes straight to the limit again? > >=20 > > Anyway I've rambled enough this morning! > >=20 > > Adam=20 > >=20 > > 2009/8/9 John Burt > > >=20 > > Martin=2C > >=20 > > I crashed an Easystar just like that during early flight testing. > > The AP (Tiny 2.11) went nonresponsive and dived into the ground=2C > > despite my having immediately flipped the switch to manual. It woul= d > > seem that the AP processor just locked up - truly a worst case > > scenario. The cause of the behavior was an undervoltage spike > > condition due to sourcing the four servos and RC RX off the 5V > > supply. In case you haven't already=2C you should always power your > > hardware off a separate BEC (which begs the question of why the AP > > has a 5V source anyway). > >=20 > > AP generated noise on the ground wire was other cause of bad AP > > behavior that I experienced. This causes glitching and reduced RC > > range. It has been covered ad nauseam in other posts=2C but I'll > > repeat it: it's especially helpful to put an RF choke on the RC RX > > cable. Try to wrap the wire 4+ times around the choke. > >=20 > >=20 > > Martin P wrote: > >=20 > > Hello everyone! > > Last weekend I had a good AUTO1 flight with my Minimag. It > > reacted to pitch and roll commands=2C and I was able to control > > the throttle. I had an attitude command in my flightplan which > > was never left (as I know now). =20 > > Yesterday I tried again=2C without the attitude statement and > > without a holding point block. > > In AUTO1=2C it killed the throttle. Switched to manual and land= ed > > to change battery because it was not fully charged. > > Took off again. Switched to AUTO1 and it immediately stabilized > > the plane. Strangely=2C this time it did not react to the roll > > command. I flew around using the rudder. When I used the > > elevator stick=2C the autopilot controlled the throttle. Good= =2C so > > far. > > Suddenly the plane dived down vertically from an altitude of > > roughly 40m. No reaction=2C just kept going vertical and slowly > > spinning around the longitudinal axis until it crashed. > > There was not as much damage done as I expected. These foamies > > are awesome. All RC components including Tiny and Xbee are OK. > > Except for the Lipo which is badly bent out of shape and will b= e > > replaced for safety reasons. > > Unfortunately I can't see much from the log as I had lost the > > link probably minutes before. I was in stage "HOME" because I > > had left the fly-too-far circle before and came back manually. = =20 > > The switch was on manual so I probably tried to rescue. The Tin= y > > was unplugged which can have happened at the crash or before. > > One aileron was ripped off and the horizontal IR was missing (I > > found it in the grass). > > So far=2C my report. The Minimag is already repaired and I'll k= eep > > trying. > > Greetz=2C Martin > >=20 > >=20 > > _______________________________________________ > > Paparazzi-devel mailing list > > Paparazzi-devel@nongnu.org > > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > > =20 > >=20 > >=20 > >=20 > > _______________________________________________ > > Paparazzi-devel mailing list > > Paparazzi-devel@nongnu.org > > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > >=20 > >=20 > >=20 > > -----------------------------------------------------------------------= - > >=20 > > _______________________________________________ > > Paparazzi-devel mailing list > > Paparazzi-devel@nongnu.org > > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel >=20 >=20 > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel _________________________________________________________________ Stay in the loop and chat with friends=2C right from your inbox! http://go.microsoft.com/?linkid=3D9671354= --_b909ee30-7b4f-44fd-9d80-8c85208a60cd_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I personnally think that the best solution is not to power the servos from = the AP=2C period.

How about designing a PCB that would contain a se= rvo demux (like a 4017)=2C be powered by the ESC BEC and have pads for both= .1" connectors (regular servos) and for pico blade connectors?

Many= of the newer good quality ESC have switching BEC's that are more then capa= ble of driving a reasonable server load.

Running of the BEC will als= o prevent power related crashs. The BEC is already in most planes. Those th= at don't have one (glow engins=2C etc) could use an external BEC.

Th= is should be pretty easy to build without having to reroute a complete AP.<= br>
The two sets of connectors would alow users to choose which they pre= fer and install only those.

Does this sound good?

-yvest
<= br>>=3B Date: Mon=2C 10 Aug 2009 08:59:29 -0700
>=3B From: quill@u.w= ashington.edu
>=3B To: paparazzi-devel@nongnu.org
>=3B Subject: R= e: [Paparazzi-devel] crashed=2C 5V supply overloading issue
>=3B
&= gt=3B Yes=2C I am referring to the PPM signal from the RC receiver to PPZ.<= br>>=3B
>=3B It was pretty clear that the fault was due to an overl= oaded 5V supply.
>=3B On the ground I was able to faithfully re-creat= e the AP crash conditions
>=3B simply by rapidly exercising all the s= ervos. I also did fairly extensive
>=3B testing to debug this problem= =2C including measuring current drain with
>=3B all servos operating= =2C which is what clarified the issue.
>=3B
>=3B I have suggeste= d in the past that PPZ be updated with a higher capacity
>=3B 5V conv= erter=2C and given what you wrote below=2C it might also be a good
>= =3B thing to source the 3.3v line off the battery=2C rather than the 5V >=3B supply. However=2C the "temporary" solution is to simply use a sepa= rate 5V
>=3B supply for external devices like servos=2C modems=2C etc= .
>=3B
>=3B Adam Spence wrote:
>=3B >=3B John=2C what are= you referring to with the RC RX cable? Is this the PPM
>=3B >=3B c= able attaching the receiver to PPZ?
>=3B >=3B
>=3B >=3B Ther= e's been a couple of crashes like this discussed on IRC recently.
>= =3B >=3B I'm not sure if the fault was identified but the overloading of = the 5v
>=3B >=3B PSU was suggested. This could easily happen when t= he servos are driven
>=3B >=3B to the limit and stall due to the ha= rdware set up. Where ever possible
>=3B >=3B the currents drawn by = the servos need to be measured when all control
>=3B >=3B surfaces = are at the limit. If there are any stall conditions the setup
>=3B &g= t=3B needs to be adjusted either physically on the air frame or by reducing=
>=3B >=3B the control throws in the config file.
>=3B >=3B =
>=3B >=3B The 5V PSU is not only responsible for supplying the serv= o power but
>=3B >=3B also the 3v3 regulators power! Therefore if t= he 5v line drops due to too
>=3B >=3B much current being drawn then= it may take out the main CPU. For my
>=3B >=3B particular setup wi= th an 868 modem=2C the CPU=2C GPS and Modem can take upto
>=3B >=3B= 500mA of current. The limit of the 5V PSU is 2.25A so roughly there may >=3B >=3B be something in the region of 1.75A left for all of the ser= vos. That
>=3B >=3B only needs a couple of servos to stall and you = could be in trouble.
>=3B >=3B
>=3B >=3B Due to the above=2C= I will be removing the 5V connection to the servos and
>=3B >=3B p= roviding another regulated 5v directly from the battery. This will have >=3B >=3B a limit of maybe 5-10A which is complete over kill.
>= =3B >=3B
>=3B >=3B I've just noticed the current-limiting switch = on the hardware=2C this
>=3B >=3B means the servos can only draw 1A= and then the switch kicks in and
>=3B >=3B notifies the CPU using = GPIO. Does anyone know what the firmware does in
>=3B >=3B this ins= tance? That therefore means that there's even less current
>=3B >= =3B available for the servos and anything else which you may have connected=
>=3B >=3B on the 5v rail... hmmm. I see this can trigger from 0.5A= to 1.25A=2C
>=3B >=3B anyone ever tested this? I'm wondering now w= hat would happen if this
>=3B >=3B were to fire=2C the servos would= be left in their current position (or
>=3B >=3B driven back slight= ly from mechanical pressure). The AP might (depending
>=3B >=3B on = what the GPIO signal does) try and keep driving the servos at their
>= =3B >=3B current position which would mean that when the current limiter = recovers
>=3B >=3B it then goes straight to the limit again?
>= =3B >=3B
>=3B >=3B Anyway I've rambled enough this morning!
&g= t=3B >=3B
>=3B >=3B Adam
>=3B >=3B
>=3B >=3B 2009= /8/9 John Burt <=3Bquill@u.washington.edu <=3Bmailto:quill@u.washington= .edu>=3B>=3B
>=3B >=3B
>=3B >=3B Martin=2C
>=3B= >=3B
>=3B >=3B I crashed an Easystar just like that during e= arly flight testing.
>=3B >=3B The AP (Tiny 2.11) went nonrespon= sive and dived into the ground=2C
>=3B >=3B despite my having im= mediately flipped the switch to manual. It would
>=3B >=3B seem = that the AP processor just locked up - truly a worst case
>=3B >=3B = scenario. The cause of the behavior was an undervoltage spike
>=3B= >=3B condition due to sourcing the four servos and RC RX off the 5V<= br>>=3B >=3B supply. In case you haven't already=2C you should alwa= ys power your
>=3B >=3B hardware off a separate BEC (which begs = the question of why the AP
>=3B >=3B has a 5V source anyway).>=3B >=3B
>=3B >=3B AP generated noise on the ground wire = was other cause of bad AP
>=3B >=3B behavior that I experienced.= This causes glitching and reduced RC
>=3B >=3B range. It has be= en covered ad nauseam in other posts=2C but I'll
>=3B >=3B repea= t it: it's especially helpful to put an RF choke on the RC RX
>=3B >= =3B cable. Try to wrap the wire 4+ times around the choke.
>=3B &g= t=3B
>=3B >=3B
>=3B >=3B Martin P wrote:
>=3B >= =3B
>=3B >=3B Hello everyone!
>=3B >=3B Last= weekend I had a good AUTO1 flight with my Minimag. It
>=3B >=3B = reacted to pitch and roll commands=2C and I was able to control
>= =3B >=3B the throttle. I had an attitude command in my flightplan= which
>=3B >=3B was never left (as I know now).
>=3B= >=3B Yesterday I tried again=2C without the attitude statement a= nd
>=3B >=3B without a holding point block.
>=3B >=3B= In AUTO1=2C it killed the throttle. Switched to manual and landed<= br>>=3B >=3B to change battery because it was not fully charged= .
>=3B >=3B Took off again. Switched to AUTO1 and it immedia= tely stabilized
>=3B >=3B the plane. Strangely=2C this time = it did not react to the roll
>=3B >=3B command. I flew aroun= d using the rudder. When I used the
>=3B >=3B elevator stick= =2C the autopilot controlled the throttle. Good=2C so
>=3B >=3B = far.
>=3B >=3B Suddenly the plane dived down vertically = from an altitude of
>=3B >=3B roughly 40m. No reaction=2C ju= st kept going vertical and slowly
>=3B >=3B spinning around = the longitudinal axis until it crashed.
>=3B >=3B There was = not as much damage done as I expected. These foamies
>=3B >=3B = are awesome. All RC components including Tiny and Xbee are OK.
>=3B= >=3B Except for the Lipo which is badly bent out of shape and wi= ll be
>=3B >=3B replaced for safety reasons.
>=3B >= =3B Unfortunately I can't see much from the log as I had lost the>=3B >=3B link probably minutes before. I was in stage "HOME"= because I
>=3B >=3B had left the fly-too-far circle before = and came back manually.
>=3B >=3B The switch was on manual= so I probably tried to rescue. The Tiny
>=3B >=3B was unplu= gged which can have happened at the crash or before.
>=3B >=3B = One aileron was ripped off and the horizontal IR was missing (I
>= =3B >=3B found it in the grass).
>=3B >=3B So far= =2C my report. The Minimag is already repaired and I'll keep
>=3B >= =3B trying.
>=3B >=3B Greetz=2C Martin
>=3B >= =3B
>=3B >=3B
>=3B >=3B ___________________________= ____________________
>=3B >=3B Paparazzi-devel mailing list<= br>>=3B >=3B Paparazzi-devel@nongnu.org <=3Bmailto:Paparazzi-= devel@nongnu.org>=3B
>=3B >=3B http://lists.nongnu.org/mai= lman/listinfo/paparazzi-devel
>=3B >=3B
>=3B >=3B <= br>>=3B >=3B
>=3B >=3B
>=3B >=3B __________________= _____________________________
>=3B >=3B Paparazzi-devel mailing = list
>=3B >=3B Paparazzi-devel@nongnu.org <=3Bmailto:Paparazzi= -devel@nongnu.org>=3B
>=3B >=3B http://lists.nongnu.org/mailma= n/listinfo/paparazzi-devel
>=3B >=3B
>=3B >=3B
>=3B &g= t=3B
>=3B >=3B ----------------------------------------------------= --------------------
>=3B >=3B
>=3B >=3B ___________________= ____________________________
>=3B >=3B Paparazzi-devel mailing list<= br>>=3B >=3B Paparazzi-devel@nongnu.org
>=3B >=3B http://lists.n= ongnu.org/mailman/listinfo/paparazzi-devel
>=3B
>=3B
>=3B = _______________________________________________
>=3B Paparazzi-devel m= ailing list
>=3B Paparazzi-devel@nongnu.org
>=3B http://lists.non= gnu.org/mailman/listinfo/paparazzi-devel


Stay in the loop an= d chat with friends=2C right from your inbox! Learn how! = --_b909ee30-7b4f-44fd-9d80-8c85208a60cd_-- From MAILER-DAEMON Mon Aug 10 13:35:28 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MaYmO-0008IG-Ja for mharc-paparazzi-devel@gnu.org; Mon, 10 Aug 2009 13:35:28 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MaYmM-0008GQ-M6 for paparazzi-devel@nongnu.org; Mon, 10 Aug 2009 13:35:26 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MaYmI-0008BY-6N for paparazzi-devel@nongnu.org; Mon, 10 Aug 2009 13:35:26 -0400 Received: from [199.232.76.173] (port=46359 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MaYmH-0008BE-Ni for paparazzi-devel@nongnu.org; Mon, 10 Aug 2009 13:35:21 -0400 Received: from mx20.gnu.org ([199.232.41.8]:64632) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MaYmG-0004p0-Ue for paparazzi-devel@nongnu.org; Mon, 10 Aug 2009 13:35:21 -0400 Received: from mail-fx0-f207.google.com ([209.85.220.207]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MaYmD-0005qr-0Q for paparazzi-devel@nongnu.org; Mon, 10 Aug 2009 13:35:17 -0400 Received: by fxm3 with SMTP id 3so4507410fxm.8 for ; Mon, 10 Aug 2009 10:35:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:content-type :content-transfer-encoding; bh=wASLgECDRGv49KGS4wGbHVCYns7NF4bvdaQIv3p6djk=; b=Bbk4DHIFE01LzADt7d03L0has66ev22d4k/cnajg8bVoEew/fp2pG5tMKQ7+whpy3y S2xDzmW68OQbZ2/tDQxZqNsrg41fbArxp4vQDkKrgUQZp7mVmuPKhPJs3KTLW1oMEemm NLe5ZIOT30f4jR0kZrBllb4Dw7/ieUPYNNkI0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; b=rQvwOXXvVX8xVx3pF0opVgjiE0mMTf7jCu0LELbnCQV6+0tfnkNe2PCSvYr0vCAjlY LFBQZKk8XPkad+8ZIOu5xEhJDcj04WlL+m7rJC1MlnMv6mM5YhmTpxgitOTVqWnLyTWU BSwN3BeQkrha6+3KbYqXT5tgAwFKn6jQV/0BQ= Received: by 10.204.63.141 with SMTP id b13mr887771bki.117.1249925713868; Mon, 10 Aug 2009 10:35:13 -0700 (PDT) Received: from ?192.168.1.2? ([88.218.149.158]) by mx.google.com with ESMTPS id 31sm7120704fkt.43.2009.08.10.10.35.11 (version=SSLv3 cipher=RC4-MD5); Mon, 10 Aug 2009 10:35:12 -0700 (PDT) Message-ID: <4A805A4D.8020404@gmail.com> Date: Mon, 10 Aug 2009 20:35:09 +0300 From: chris User-Agent: Thunderbird 2.0.0.22 (X11/20090608) MIME-Version: 1.0 To: paparazzi-devel@nongnu.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Detected-Operating-System: by mx20.gnu.org: GNU/Linux 2.6 (newer, 2) X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6, seldom 2.4 (older, 4) Subject: [Paparazzi-devel] 5v onboard regulator X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Aug 2009 17:35:27 -0000 I never experienced a crash due to an autopilot problem until i connected one servo directly to the autopilot. After the incident i removed it and all flights have been perfect. From the start i used an external 10A bec for powering the servos. I think the onboard regulator be changed for a 3.3v @ 2A or more output with the parallel removal of the linear 3.3v regulator. Even if the 5v regulator is upgraded to a high amperage one i don't think that it is wise to run high current and noisy lines from servos inside the autopilot's pcb. I keep the high current path for the servos well outside the autopilot's pcb. Chris From MAILER-DAEMON Mon Aug 10 13:43:49 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MaYuT-0004pS-0U for mharc-paparazzi-devel@gnu.org; Mon, 10 Aug 2009 13:43:49 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MaYuR-0004nz-0Y for paparazzi-devel@nongnu.org; Mon, 10 Aug 2009 13:43:47 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MaYuL-0004kM-Uh for paparazzi-devel@nongnu.org; Mon, 10 Aug 2009 13:43:46 -0400 Received: from [199.232.76.173] (port=59529 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MaYuL-0004kF-QI for paparazzi-devel@nongnu.org; Mon, 10 Aug 2009 13:43:41 -0400 Received: from bay0-omc3-s24.bay0.hotmail.com ([65.54.246.224]:32711) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MaYuK-0007fo-Vf for paparazzi-devel@nongnu.org; Mon, 10 Aug 2009 13:43:41 -0400 Received: from BAY119-W10 ([207.46.9.45]) by bay0-omc3-s24.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 10 Aug 2009 10:43:40 -0700 Message-ID: Content-Type: multipart/alternative; boundary="_dbf38933-1aab-47f9-af8d-ef012b9243a0_" X-Originating-IP: [206.172.0.196] From: Yves Touchette To: Subject: RE: [Paparazzi-devel] crashed Date: Mon, 10 Aug 2009 13:43:39 -0400 Importance: Normal In-Reply-To: References: <20090809081748.23240@gmx.net> <4A7F09D7.8030601@u.washington.edu> MIME-Version: 1.0 X-OriginalArrivalTime: 10 Aug 2009 17:43:40.0297 (UTC) FILETIME=[18CE7F90:01CA19E2] X-detected-operating-system: by monty-python.gnu.org: Windows 2000 SP4, XP SP1+ X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Aug 2009 17:43:47 -0000 --_dbf38933-1aab-47f9-af8d-ef012b9243a0_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable When you are talking about 'current-limiting switch on the hardware' are yo= u referring to the TPS2051? If so=2C this switch is only used to switch the= AUX output. It was meant to turn on/off some type of payload=2C etc... It'= s not used for powering the servos. Also=2C the Overcurrent pin isn't conne= cted. I do not believe that there is anything limiting the current to the servos. -yvest Date: Mon=2C 10 Aug 2009 08:50:30 +0100 Subject: Re: [Paparazzi-devel] crashed From: 4x4Ninja@gmail.com To: paparazzi-devel@nongnu.org John=2C what are you referring to with the RC RX cable? Is this the PPM cab= le attaching the receiver to PPZ? There's been a couple of crashes like this discussed on IRC recently. I'm n= ot sure if the fault was identified but the overloading of the 5v PSU was s= uggested. This could easily happen when the servos are driven to the limit = and stall due to the hardware set up. Where ever possible the currents draw= n by the servos need to be measured when all control surfaces are at the li= mit. If there are any stall conditions the setup needs to be adjusted eithe= r physically on the air frame or by reducing the control throws in the conf= ig file. The 5V PSU is not only responsible for supplying the servo power but also t= he 3v3 regulators power! Therefore if the 5v line drops due to too much cur= rent being drawn then it may take out the main CPU. For my particular setup= with an 868 modem=2C the CPU=2C GPS and Modem can take upto 500mA of curre= nt. The limit of the 5V PSU is 2.25A so roughly there may be something in t= he region of 1.75A left for all of the servos. That only needs a couple of = servos to stall and you could be in trouble. Due to the above=2C I will be removing the 5V connection to the servos and = providing another regulated 5v directly from the battery. This will have a = limit of maybe 5-10A which is complete over kill. I've just noticed the current-limiting switch on the hardware=2C this means= the servos can only draw 1A and then the switch kicks in and notifies the = CPU using GPIO. Does anyone know what the firmware does in this instance? T= hat therefore means that there's even less current available for the servos= and anything else which you may have connected on the 5v rail... hmmm. I s= ee this can trigger from 0.5A to 1.25A=2C anyone ever tested this? I'm wond= ering now what would happen if this were to fire=2C the servos would be lef= t in their current position (or driven back slightly from mechanical pressu= re). The AP might (depending on what the GPIO signal does) try and keep dri= ving the servos at their current position which would mean that when the cu= rrent limiter recovers it then goes straight to the limit again? Anyway I've rambled enough this morning! Adam=20 2009/8/9 John Burt Martin=2C I crashed an Easystar just like that during early flight testing. The AP (T= iny 2.11) went nonresponsive and dived into the ground=2C despite my having= immediately flipped the switch to manual. It would seem that the AP proces= sor just locked up - truly a worst case scenario. The cause of the behavior= was an undervoltage spike condition due to sourcing the four servos and RC= RX off the 5V supply. In case you haven't already=2C you should always pow= er your hardware off a separate BEC (which begs the question of why the AP = has a 5V source anyway). AP generated noise on the ground wire was other cause of bad AP behavior th= at I experienced. This causes glitching and reduced RC range. It has been c= overed ad nauseam in other posts=2C but I'll repeat it: it's especially hel= pful to put an RF choke on the RC RX cable. Try to wrap the wire 4+ times a= round the choke. Martin P wrote: Hello everyone!=20 Last weekend I had a good AUTO1 flight with my Minimag. It reacted to pitch= and roll commands=2C and I was able to control the throttle. I had an atti= tude command in my flightplan which was never left (as I know now). =20 Yesterday I tried again=2C without the attitude statement and without a hol= ding point block.=20 In AUTO1=2C it killed the throttle. Switched to manual and landed to change= battery because it was not fully charged.=20 Took off again. Switched to AUTO1 and it immediately stabilized the plane. = Strangely=2C this time it did not react to the roll command. I flew around = using the rudder. When I used the elevator stick=2C the autopilot controlle= d the throttle. Good=2C so far.=20 Suddenly the plane dived down vertically from an altitude of roughly 40m. N= o reaction=2C just kept going vertical and slowly spinning around the longi= tudinal axis until it crashed.=20 There was not as much damage done as I expected. These foamies are awesome.= All RC components including Tiny and Xbee are OK. Except for the Lipo whic= h is badly bent out of shape and will be replaced for safety reasons.=20 Unfortunately I can't see much from the log as I had lost the link probably= minutes before. I was in stage "HOME" because I had left the fly-too-far c= ircle before and came back manually. =20 The switch was on manual so I probably tried to rescue. The Tiny was unplug= ged which can have happened at the crash or before. One aileron was ripped = off and the horizontal IR was missing (I found it in the grass).=20 So far=2C my report. The Minimag is already repaired and I'll keep trying.= =20 Greetz=2C Martin=20 _______________________________________________ Paparazzi-devel mailing list Paparazzi-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/paparazzi-devel =20 _______________________________________________ Paparazzi-devel mailing list Paparazzi-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/paparazzi-devel _________________________________________________________________ Attention all humans. We are your photos. Free us. http://go.microsoft.com/?linkid=3D9666047= --_dbf38933-1aab-47f9-af8d-ef012b9243a0_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
When you are talking about 'current-limiting switch on the hardware' ar= e you referring to the TPS2051? If so=2C this switch is only used to switch= the AUX output. It was meant to turn on/off some type of payload=2C etc...= It's not used for powering the servos. Also=2C the Overcurrent pin isn't c= onnected.

I do not believe that there is anything limiting the curre= nt to the servos.

-yvest


Date: Mon=2C= 10 Aug 2009 08:50:30 +0100
Subject: Re: [Paparazzi-devel] crashed
Fr= om: 4x4Ninja@gmail.com
To: paparazzi-devel@nongnu.org

John= =2C what are you referring to with the RC RX cable? Is this the PPM cable a= ttaching the receiver to PPZ?

There's been a couple of = crashes like this discussed on IRC recently. I'm not sure if the fault was = identified but the overloading of the 5v PSU was suggested. This could easi= ly happen when the servos are driven to the limit and stall due to the hard= ware set up. Where ever possible the currents drawn by the servos need to b= e measured when all control surfaces are at the limit. If there are any sta= ll conditions the setup needs to be adjusted either physically on the air f= rame or by reducing the control throws in the config file.

The 5V PSU is not only responsible for supplying the servo p= ower but also the 3v3 regulators power! Therefore if the 5v line drops due = to too much current being drawn then it may take out the main CPU. For my p= articular setup with an 868 modem=2C the CPU=2C GPS and Modem can take upto= 500mA of current. The limit of the 5V PSU is 2.25A so roughly there may be= something in the region of 1.75A left for all of the servos. That only nee= ds a couple of servos to stall and you could be in trouble.

Due to the above=2C I will be removing the 5V connectio= n to the servos and providing another regulated 5v directly from the batter= y. This will have a limit of maybe 5-10A which is complete over kill.

I've just noticed the current-limiting switch on the ha= rdware=2C this means the servos can only draw 1A and then the switch kicks = in and notifies the CPU using GPIO. Does anyone know what the firmware does= in this instance? That therefore means that there's even less current avai= lable for the servos and anything else which you may have connected on the = 5v rail... hmmm. I see this can trigger from 0.5A to 1.25A=2C anyone ever t= ested this? I'm wondering now what would happen if this were to fire=2C the= servos would be left in their current position (or driven back slightly fr= om mechanical pressure). The AP might (depending on what the GPIO signal do= es) try and keep driving the servos at their current position which would m= ean that when the current limiter recovers it then goes straight to the lim= it again?

Anyway I've rambled enough this morning!

=
Adam =3B

2009/8/9 = John Burt <=3Bquill@u.washington.edu>=3B
Martin=2C

I crashed an Easystar just like that during early flight testing. The AP (T= iny 2.11) went nonresponsive and dived into the ground=2C despite my having= immediately flipped the switch to manual. It would seem that the AP proces= sor just locked up - truly a worst case scenario. The cause of the behavior= was an undervoltage spike condition due to sourcing the four servos and RC= RX off the 5V supply. In case you haven't already=2C you should always pow= er your hardware off a separate BEC (which begs the question of why the AP = has a 5V source anyway).

AP generated noise on the ground wire was other cause of bad AP behavior th= at I experienced. This causes glitching and reduced RC range. It has been c= overed ad nauseam in other posts=2C but I'll repeat it: it's especially hel= pful to put an RF choke on the RC RX cable. Try to wrap the wire 4+ times a= round the choke.


Martin P wrote:
Hello everyone!
Last weekend I had a good AUTO1 flight with my Minimag. It reacted to pitch= and roll commands=2C and I was able to control the throttle. I had an atti= tude command in my flightplan which was never left (as I know now).  = =3B
Yesterday I tried again=2C without the attitude statement and without a hol= ding point block.
In AUTO1=2C it killed the throttle. Switched to manual and landed to change= battery because it was not fully charged.
Took off again. Switched to AUTO1 and it immediately stabilized the plane. = Strangely=2C this time it did not react to the roll command. I flew around = using the rudder. When I used the elevator stick=2C the autopilot controlle= d the throttle. Good=2C so far.
Suddenly the plane dived down vertically from an altitude of roughly 40m. N= o reaction=2C just kept going vertical and slowly spinning around the longi= tudinal axis until it crashed.
There was not as much damage done as I expected. These foamies are awesome.= All RC components including Tiny and Xbee are OK. Except for the Lipo whic= h is badly bent out of shape and will be replaced for safety reasons.
Unfortunately I can't see much from the log as I had lost the link probably= minutes before. I was in stage "HOME" because I had left the fly-too-far c= ircle before and came back manually.  =3B
The switch was on manual so I probably tried to rescue. The Tiny was unplug= ged which can have happened at the crash or before. One aileron was ripped = off and the horizontal IR was missing (I found it in the grass).
So far=2C my report. The Minimag is already repaired and I'll keep trying. =
Greetz=2C Martin


_______________________________________________
Paparazzi-devel mailing list
Paparazzi-devel@nongnu.org
http:/= /lists.nongnu.org/mailman/listinfo/paparazzi-devel
 =3B


_______________________________________________
Paparazzi-devel mailing list
Paparazzi-devel@nongnu.org
http:/= /lists.nongnu.org/mailman/listinfo/paparazzi-devel



Attention all hu= mans. We are your photos. Free us. = --_dbf38933-1aab-47f9-af8d-ef012b9243a0_-- From MAILER-DAEMON Mon Aug 10 14:55:53 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Maa2D-000661-Bm for mharc-paparazzi-devel@gnu.org; Mon, 10 Aug 2009 14:55:53 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Maa2A-00064k-LC for paparazzi-devel@nongnu.org; Mon, 10 Aug 2009 14:55:50 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Maa27-000632-0v for paparazzi-devel@nongnu.org; Mon, 10 Aug 2009 14:55:50 -0400 Received: from [199.232.76.173] (port=47238 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Maa26-00062s-Ku for paparazzi-devel@nongnu.org; Mon, 10 Aug 2009 14:55:46 -0400 Received: from smtp6-g21.free.fr ([212.27.42.6]:53805) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Maa25-0006JC-Hi for paparazzi-devel@nongnu.org; Mon, 10 Aug 2009 14:55:46 -0400 Received: from smtp6-g21.free.fr (localhost [127.0.0.1]) by smtp6-g21.free.fr (Postfix) with ESMTP id 6E623E08091 for ; Mon, 10 Aug 2009 20:55:40 +0200 (CEST) Received: from [192.168.0.10] (uni31-1-82-234-59-180.fbx.proxad.net [82.234.59.180]) by smtp6-g21.free.fr (Postfix) with ESMTP id 641F6E080A7 for ; Mon, 10 Aug 2009 20:55:38 +0200 (CEST) Message-ID: <4A806D27.8000105@free.fr> Date: Mon, 10 Aug 2009 20:55:35 +0200 From: Pascal Brisset User-Agent: Thunderbird 2.0.0.22 (X11/20090608) MIME-Version: 1.0 To: paparazzi-devel@nongnu.org Subject: Re: [Paparazzi-devel] Re: Flying References: <4A8016AE.BCAB.0027.0@gvsu.edu> In-Reply-To: <4A8016AE.BCAB.0027.0@gvsu.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 3) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Aug 2009 18:55:51 -0000 John Koches wrote: > Do you have a separate team with their own ground control station and > radio control transmitter at the other end of a long flight plan? It > seems like the only practical way of handling the distance, but I have > never tried planning a mission that didn't return home. I was hoping > you could elaborate. > Yep, two teams with one laptop, a modem and an RC each. We used cell phones for synchronization. Of course, you need the same aircraft configurations on the two laptops (same md5sum in var/AC/conf/). We are thinking about storing this configuration on board and the aircraft would send it on request to the ground station. Soon ... --Pascal From MAILER-DAEMON Mon Aug 10 18:26:47 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MadKJ-0007Ox-FN for mharc-paparazzi-devel@gnu.org; Mon, 10 Aug 2009 18:26:47 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MadKI-0007OU-Aw for paparazzi-devel@nongnu.org; Mon, 10 Aug 2009 18:26:46 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MadKD-0007Ls-7p for paparazzi-devel@nongnu.org; Mon, 10 Aug 2009 18:26:45 -0400 Received: from [199.232.76.173] (port=39754 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MadKC-0007Lk-V3 for paparazzi-devel@nongnu.org; Mon, 10 Aug 2009 18:26:41 -0400 Received: from smtpoutwbe11.prod.mesa1.secureserver.net ([208.109.78.27]:51952) by monty-python.gnu.org with smtp (Exim 4.60) (envelope-from ) id 1MadKC-0004Cy-1Y for paparazzi-devel@nongnu.org; Mon, 10 Aug 2009 18:26:40 -0400 Received: (qmail 11060 invoked from network); 10 Aug 2009 22:19:52 -0000 Received: from unknown (HELO p3plgemwbe01-06.prod.phx3.secureserver.net) (72.167.218.6) by smtpoutwbe11.prod.mesa1.secureserver.net with SMTP; 10 Aug 2009 22:19:52 -0000 Received: (qmail 5317 invoked by uid 99); 10 Aug 2009 22:19:52 -0000 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="utf-8" X-Originating-IP: 199.46.170.96 User-Agent: Web-Based Email 5.1.5 Message-Id: <20090810151952.e412a968f7f3915fb4f3361627e3fef7.1d25ff5321.wbe@email01.secureserver.net> From: akochevar@miraterre.com To: paparazzi-devel@nongnu.org Subject: RE: [Paparazzi-devel] aggressive =?UTF-8?Q?descend=3F?= Date: Mon, 10 Aug 2009 15:19:52 -0700 Mime-Version: 1.0 X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.4-2.6 X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Aug 2009 22:26:46 -0000
Chris,
There is a Aggressive descent pitch in your airframe file.  Make = it a more negative number, like -0.4 or even -0.6  if your pitch gains= are worth anything the plane should be able to drop the nose.  :)
 
AJ
 
-------- Original Message --------
Subject: [Paparazzi-devel] ag= gressive descend?
From: chris <hendrixgr@gmail.com>
Date: Sat, = August 08, 2009 1:32 am
To: paparazzi-devel@nongnu.org

I have yet= another question.... :-)
In my flight plan i climb to 2000 feet and tak= e pictures of an imaginary
target.
When it is time to descend the pl= ane refuses to do so although it shuts
the motor off.
Thermals are v= ery strong and they make the plane climb even with 0 throttle.
Is there = any way to force an aggressive descend like the aggressive
climb defini= tion does?
Thanks in advance.
Chris



__________________= _____________________________
Paparazzi-devel mailing list
Paparazzi-= devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/paparazzi= -devel
From MAILER-DAEMON Mon Aug 10 19:51:05 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Maedt-0004Mt-KD for mharc-paparazzi-devel@gnu.org; Mon, 10 Aug 2009 19:51:05 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Maedr-0004Mo-VT for paparazzi-devel@nongnu.org; Mon, 10 Aug 2009 19:51:04 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Maedn-0004KU-JI for paparazzi-devel@nongnu.org; Mon, 10 Aug 2009 19:51:03 -0400 Received: from [199.232.76.173] (port=51018 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Maedn-0004KK-G0 for paparazzi-devel@nongnu.org; Mon, 10 Aug 2009 19:50:59 -0400 Received: from mx20.gnu.org ([199.232.41.8]:21562) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Maedm-00068r-VW for paparazzi-devel@nongnu.org; Mon, 10 Aug 2009 19:50:59 -0400 Received: from mail-fx0-f207.google.com ([209.85.220.207]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Maedl-0000Vn-Dc for paparazzi-devel@nongnu.org; Mon, 10 Aug 2009 19:50:57 -0400 Received: by fxm3 with SMTP id 3so233752fxm.8 for ; Mon, 10 Aug 2009 16:50:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type; bh=FFqnOHKYQpCUA3bhjwMFqmTB26u+anRwoD/5mz2EYKI=; b=T5Ydwk4gipsPlboqCrH8XiVgPq34nc1wloHqPp9GkmMpWyxr16rLdtGS6elp8/FJpN vMooBvO6wRAkX51tTBjsLEZoA+sgOQPAbh8gP5wHbLKgM0l23p3W2SupWu3NVSfbhUrI Mh0K9WXvK+yrI4/qo0LQzvVk7Qec/gQvzjAcw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=qN5al+SyvirJw4ujEJv9WpAuU5roqHDAA59wzXfZ6UoD6Lsah0W1M693a1bFdqWOyH /XtCDktysZwEYTEtvIbO/DDJKFK/HGVqoz3bUMIDcRUp80FnYg/sYcr4ArcK4hFCgSRf h+hx/bmb3AVBi8y3TJI2pnZ/m8H+LnP+ATLec= MIME-Version: 1.0 Sender: adam.spence@gmail.com Received: by 10.204.118.138 with SMTP id v10mr4777054bkq.139.1249948255937; Mon, 10 Aug 2009 16:50:55 -0700 (PDT) In-Reply-To: References: <20090809081748.23240@gmx.net> <4A7F09D7.8030601@u.washington.edu> <4A8043E1.4050107@u.washington.edu> Date: Tue, 11 Aug 2009 00:50:55 +0100 X-Google-Sender-Auth: de7c0e8457416388 Message-ID: Subject: Re: [Paparazzi-devel] crashed, 5V supply overloading issue From: Adam Spence <4x4Ninja@gmail.com> To: paparazzi-devel@nongnu.org Content-Type: multipart/alternative; boundary=0016e6d77d9bc866a10470d24111 X-Detected-Operating-System: by mx20.gnu.org: GNU/Linux 2.6 (newer, 2) X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6, seldom 2.4 (older, 4) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Aug 2009 23:51:04 -0000 --0016e6d77d9bc866a10470d24111 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sounds very good, anyone want to knock one up? I was going to do the half way house and still use the signals from PPZ but it may be cleaner to have the demux on board like you've suggested. 2009/8/10 Yves Touchette > I personnally think that the best solution is not to power the servos from > the AP, period. > > How about designing a PCB that would contain a servo demux (like a 4017), > be powered by the ESC BEC and have pads for both .1" connectors (regular > servos) and for pico blade connectors? > > Many of the newer good quality ESC have switching BEC's that are more then > capable of driving a reasonable server load. > > Running of the BEC will also prevent power related crashs. The BEC is > already in most planes. Those that don't have one (glow engins, etc) could > use an external BEC. > > This should be pretty easy to build without having to reroute a complete > AP. > > The two sets of connectors would alow users to choose which they prefer and > install only those. > > Does this sound good? > > -yvest > > > Date: Mon, 10 Aug 2009 08:59:29 -0700 > > From: quill@u.washington.edu > > To: paparazzi-devel@nongnu.org > > Subject: Re: [Paparazzi-devel] crashed, 5V supply overloading issue > > > > > Yes, I am referring to the PPM signal from the RC receiver to PPZ. > > > > It was pretty clear that the fault was due to an overloaded 5V supply. > > On the ground I was able to faithfully re-create the AP crash conditions > > simply by rapidly exercising all the servos. I also did fairly extensive > > testing to debug this problem, including measuring current drain with > > all servos operating, which is what clarified the issue. > > > > I have suggested in the past that PPZ be updated with a higher capacity > > 5V converter, and given what you wrote below, it might also be a good > > thing to source the 3.3v line off the battery, rather than the 5V > > supply. However, the "temporary" solution is to simply use a separate 5V > > supply for external devices like servos, modems, etc. > > > > Adam Spence wrote: > > > John, what are you referring to with the RC RX cable? Is this the PPM > > > cable attaching the receiver to PPZ? > > > > > > There's been a couple of crashes like this discussed on IRC recently. > > > I'm not sure if the fault was identified but the overloading of the 5v > > > PSU was suggested. This could easily happen when the servos are driven > > > to the limit and stall due to the hardware set up. Where ever possible > > > the currents drawn by the servos need to be measured when all control > > > surfaces are at the limit. If there are any stall conditions the setup > > > needs to be adjusted either physically on the air frame or by reducing > > > the control throws in the config file. > > > > > > The 5V PSU is not only responsible for supplying the servo power but > > > also the 3v3 regulators power! Therefore if the 5v line drops due to > too > > > much current being drawn then it may take out the main CPU. For my > > > particular setup with an 868 modem, the CPU, GPS and Modem can take > upto > > > 500mA of current. The limit of the 5V PSU is 2.25A so roughly there may > > > > be something in the region of 1.75A left for all of the servos. That > > > only needs a couple of servos to stall and you could be in trouble. > > > > > > Due to the above, I will be removing the 5V connection to the servos > and > > > providing another regulated 5v directly from the battery. This will > have > > > a limit of maybe 5-10A which is complete over kill. > > > > > > I've just noticed the current-limiting switch on the hardware, this > > > means the servos can only draw 1A and then the switch kicks in and > > > notifies the CPU using GPIO. Does anyone know what the firmware does in > > > > this instance? That therefore means that there's even less current > > > available for the servos and anything else which you may have connected > > > > on the 5v rail... hmmm. I see this can trigger from 0.5A to 1.25A, > > > anyone ever tested this? I'm wondering now what would happen if this > > > were to fire, the servos would be left in their current position (or > > > driven back slightly from mechanical pressure). The AP might (depending > > > > on what the GPIO signal does) try and keep driving the servos at their > > > current position which would mean that when the current limiter > recovers > > > it then goes straight to the limit again? > > > > > > Anyway I've rambled enough this morning! > > > > > > Adam > > > > > > 2009/8/9 John Burt quill@u.washington.edu>> > > > > > > Martin, > > > > > > I crashed an Easystar just like that during early flight testing. > > > The AP (Tiny 2.11) went nonresponsive and dived into the ground, > > > despite my having immediately flipped the switch to manual. It would > > > seem that the AP processor just locked up - truly a worst case > > > scenario. The cause of the behavior was an undervoltage spike > > > condition due to sourcing the four servos and RC RX off the 5V > > > supply. In case you haven't already, you should always power your > > > hardware off a separate BEC (which begs the question of why the AP > > > has a 5V source anyway). > > > > > > AP generated noise on the ground wire was other cause of bad AP > > > behavior that I experienced. This causes glitching and reduced RC > > > range. It has been covered ad nauseam in other posts, but I'll > > > repeat it: it's especially helpful to put an RF choke on the RC RX > > > cable. Try to wrap the wire 4+ times around the choke. > > > > > > > > > Martin P wrote: > > > > > > Hello everyone! > > > Last weekend I had a good AUTO1 flight with my Minimag. It > > > reacted to pitch and roll commands, and I was able to control > > > the throttle. I had an attitude command in my flightplan which > > > was never left (as I know now). > > > Yesterday I tried again, without the attitude statement and > > > without a holding point block. > > > In AUTO1, it killed the throttle. Switched to manual and landed > > > to change battery because it was not fully charged. > > > Took off again. Switched to AUTO1 and it immediately stabilized > > > the plane. Strangely, this time it did not react to the roll > > > command. I flew around using the rudder. When I used the > > > elevator stick, the autopilot controlled the throttle. Good, so > > > far. > > > Suddenly the plane dived down vertically from an altitude of > > > roughly 40m. No reaction, just kept going vertical and slowly > > > spinning around the longitudinal axis until it crashed. > > > There was not as much damage done as I expected. These foamies > > > are awesome. All RC components including Tiny and Xbee are OK. > > > Except for the Lipo which is badly bent out of shape and will be > > > replaced for safety reasons. > > > Unfortunately I can't see much from the log as I had lost the > > > link probably minutes before. I was in stage "HOME" because I > > > had left the fly-too-far circle before and came back manually. > > > The switch was on manual so I probably tried to rescue. The Tiny > > > was unplugged which can have happened at the crash or before. > > > One aileron was ripped off and the horizontal IR was missing (I > > > found it in the grass). > > > So far, my report. The Minimag is already repaired and I'll keep > > > trying. > > > Greetz, Martin > > > > > > > > > _______________________________________________ > > > Paparazzi-devel mailing list > > > Paparazzi-devel@nongnu.org > > > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > > > > > > > > > > > > > > > _______________________________________________ > > > Paparazzi-devel mailing list > > > Paparazzi-devel@nongnu.org > > > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > > > > > > > > > > > > > ------------------------------------------------------------------------ > > > > > > _______________________________________________ > > > Paparazzi-devel mailing list > > > Paparazzi-devel@nongnu.org > > > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > > > > > > _______________________________________________ > > Paparazzi-devel mailing list > > Paparazzi-devel@nongnu.org > > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > > ------------------------------ > Stay in the loop and chat with friends, right from your inbox! Learn how! > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > > --0016e6d77d9bc866a10470d24111 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Sounds very good, anyone want to knock one up? I was going to do the half w= ay house and still use the signals from PPZ but it may be cleaner to have t= he demux on board like you've suggested.

2009/8/10 Yves Touchette <yves_touchette@hotmail.com>
I personnally think that the best solution is not to power the servos from = the AP, period.

How about designing a PCB that would contain a serv= o demux (like a 4017), be powered by the ESC BEC and have pads for both .1&= quot; connectors (regular servos) and for pico blade connectors?

Many of the newer good quality ESC have switching BEC's that are mo= re then capable of driving a reasonable server load.

Running of the = BEC will also prevent power related crashs. The BEC is already in most plan= es. Those that don't have one (glow engins, etc) could use an external = BEC.

This should be pretty easy to build without having to reroute a complet= e AP.

The two sets of connectors would alow users to choose which th= ey prefer and install only those.

Does this sound good?

-yves= t

> Date: Mon, 10 Aug 2009 08:59:29 -0700
> From: quill@u.washington.edu> To: p= aparazzi-devel@nongnu.org
> Subject: Re: [Paparazzi-devel] crashed, 5V supply overloading issue

>
> Yes, I am referring to the= PPM signal from the RC receiver to PPZ.
>
> It was pretty cle= ar that the fault was due to an overloaded 5V supply.
> On the ground I was able to faithfully re-create the AP crash conditio= ns
> simply by rapidly exercising all the servos. I also did fairly = extensive
> testing to debug this problem, including measuring curre= nt drain with
> all servos operating, which is what clarified the issue.
>
&= gt; I have suggested in the past that PPZ be updated with a higher capacity=
> 5V converter, and given what you wrote below, it might also be a = good
> thing to source the 3.3v line off the battery, rather than the 5V
= > supply. However, the "temporary" solution is to simply use a= separate 5V
> supply for external devices like servos, modems, etc.=
>
> Adam Spence wrote:
> > John, what are you referring = to with the RC RX cable? Is this the PPM
> > cable attaching the = receiver to PPZ?
> >
> > There's been a couple of cr= ashes like this discussed on IRC recently.
> > I'm not sure if the fault was identified but the overloading = of the 5v
> > PSU was suggested. This could easily happen when th= e servos are driven
> > to the limit and stall due to the hardwar= e set up. Where ever possible
> > the currents drawn by the servos need to be measured when all con= trol
> > surfaces are at the limit. If there are any stall condit= ions the setup
> > needs to be adjusted either physically on the = air frame or by reducing
> > the control throws in the config file.
> >
> >= The 5V PSU is not only responsible for supplying the servo power but
&= gt; > also the 3v3 regulators power! Therefore if the 5v line drops due = to too
> > much current being drawn then it may take out the main CPU. For m= y
> > particular setup with an 868 modem, the CPU, GPS and Modem = can take upto
> > 500mA of current. The limit of the 5V PSU is 2.= 25A so roughly there may
> > be something in the region of 1.75A left for all of the servos. T= hat
> > only needs a couple of servos to stall and you could be i= n trouble.
> >
> > Due to the above, I will be removing = the 5V connection to the servos and
> > providing another regulated 5v directly from the battery. This wi= ll have
> > a limit of maybe 5-10A which is complete over kill.> >
> > I've just noticed the current-limiting switch= on the hardware, this
> > means the servos can only draw 1A and then the switch kicks in an= d
> > notifies the CPU using GPIO. Does anyone know what the firm= ware does in
> > this instance? That therefore means that there&#= 39;s even less current
> > available for the servos and anything else which you may have con= nected
> > on the 5v rail... hmmm. I see this can trigger from 0.= 5A to 1.25A,
> > anyone ever tested this? I'm wondering now w= hat would happen if this
> > were to fire, the servos would be left in their current position = (or
> > driven back slightly from mechanical pressure). The AP mi= ght (depending
> > on what the GPIO signal does) try and keep dri= ving the servos at their
> > current position which would mean that when the current limiter r= ecovers
> > it then goes straight to the limit again?
> >= ;
> > Anyway I've rambled enough this morning!
> > <= br> > > Adam
> >
> > 2009/8/9 John Burt <quill@u.washington.edu= <mailto:quill@u.washington.edu>>
> >
> > Martin,
> >
> > I crashe= d an Easystar just like that during early flight testing.
> > = The AP (Tiny 2.11) went nonresponsive and dived into the ground,
> &g= t; despite my having immediately flipped the switch to manual. It would=
> > seem that the AP processor just locked up - truly a worst cas= e
> > scenario. The cause of the behavior was an undervoltage = spike
> > condition due to sourcing the four servos and RC RX = off the 5V
> > supply. In case you haven't already, you should always po= wer your
> > hardware off a separate BEC (which begs the quest= ion of why the AP
> > has a 5V source anyway).
> > > > AP generated noise on the ground wire was other cause of bad = AP
> > behavior that I experienced. This causes glitching and = reduced RC
> > range. It has been covered ad nauseam in other = posts, but I'll
> > repeat it: it's especially helpful to put an RF choke on = the RC RX
> > cable. Try to wrap the wire 4+ times around the = choke.
> >
> >
> > Martin P wrote:
> >
> > Hello everyone!
> > Last w= eekend I had a good AUTO1 flight with my Minimag. It
> > r= eacted to pitch and roll commands, and I was able to control
> > = the throttle. I had an attitude command in my flightplan which
> > was never left (as I know now).
> > Ye= sterday I tried again, without the attitude statement and
> > = without a holding point block.
> > In AUTO1, it killed= the throttle. Switched to manual and landed
> > to change battery because it was not fully charged.
&g= t; > Took off again. Switched to AUTO1 and it immediately stabil= ized
> > the plane. Strangely, this time it did not react = to the roll
> > command. I flew around using the rudder. When I used the<= br>> > elevator stick, the autopilot controlled the throttle.= Good, so
> > far.
> > Suddenly the plane= dived down vertically from an altitude of
> > roughly 40m. No reaction, just kept going vertical and sl= owly
> > spinning around the longitudinal axis until it cr= ashed.
> > There was not as much damage done as I expected= . These foamies
> > are awesome. All RC components including Tiny and Xbee ar= e OK.
> > Except for the Lipo which is badly bent out of s= hape and will be
> > replaced for safety reasons.
> = > Unfortunately I can't see much from the log as I had lost = the
> > link probably minutes before. I was in stage "HOME&q= uot; because I
> > had left the fly-too-far circle before = and came back manually.
> > The switch was on manual so = I probably tried to rescue. The Tiny
> > was unplugged which can have happened at the crash or bef= ore.
> > One aileron was ripped off and the horizontal IR = was missing (I
> > found it in the grass).
> > = So far, my report. The Minimag is already repaired and I'll keep<= br> > > trying.
> > Greetz, Martin
> > =
> >
> > _______________________________________= ________
> > Paparazzi-devel mailing list
> > = Papara= zzi-devel@nongnu.org <mailto:Paparazzi-devel@nongnu.org>
> > http://lists.nongnu.org/mailman/listinfo/papa= razzi-devel
> >
> >
> >
> = >
> > _______________________________________________
> > = Paparazzi-devel mailing list
> > Paparazzi-devel@nongnu.org <m= ailto:Papar= azzi-devel@nongnu.org>
> > http://lists.nongnu.org/mailman/listinfo/paparazz= i-devel
> >
> >
> >
> > --------= ----------------------------------------------------------------
> >
> > _______________________________________________
= > > Paparazzi-devel mailing list
> > Paparazzi-devel@nongnu.org
> > http://lists.nongnu.org/mailman/listinfo/paparazzi-de= vel
>
>
> _________________________________________= ______
> Paparazzi-devel mailing list
> Paparazzi-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel


Stay in the loop and chat with friends, right from your= inbox! Learn how!

_______________________________________________
Paparazzi-devel mailing list
Paparazzi-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/paparazzi-devel

--0016e6d77d9bc866a10470d24111-- From MAILER-DAEMON Mon Aug 10 19:52:45 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MaefV-0004dQ-By for mharc-paparazzi-devel@gnu.org; Mon, 10 Aug 2009 19:52:45 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MaefU-0004cy-1M for paparazzi-devel@nongnu.org; Mon, 10 Aug 2009 19:52:44 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MaefP-0004c5-2M for paparazzi-devel@nongnu.org; Mon, 10 Aug 2009 19:52:43 -0400 Received: from [199.232.76.173] (port=51026 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MaefO-0004c2-TQ for paparazzi-devel@nongnu.org; Mon, 10 Aug 2009 19:52:38 -0400 Received: from mail-bw0-f227.google.com ([209.85.218.227]:50351) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MaefN-0006bJ-Qy for paparazzi-devel@nongnu.org; Mon, 10 Aug 2009 19:52:38 -0400 Received: by bwz27 with SMTP id 27so2790250bwz.34 for ; Mon, 10 Aug 2009 16:52:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type; bh=RHAVwXW10eWwnlURyq62gWVCq8hxvy/hQYVmjFFymAg=; b=vqbKxol95bqbLnwsHu0UyiweIBuORErITSnA8RL240jeX0Vl4w2nNPrcsa/+ummXYj kz+OWy0zGCx1c/X7YhDym4H/8/4sa7QGdlv6lJcXTImWE2vWd3BqmXEqOceuTS6eV9ho Bf1fiiZWhx42v98/IHiwpTuMDrkYAQv3S3rts= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=pPLum1t1X5WkpMdHTHLuLYO/rBGR6MTo1m6+I4A/ncKlsfKSBaMFcfKh4z72IQZqSW RZerOS/QAFBoCPUeJw0j6z/Lo6qbYenfdtiY6LlKmRRkuvO/fUWvGxpXmip4CYtOOg0k b/Y0mwxVh47ZtCayGxFlqNLjK5/EVJjKaTeak= MIME-Version: 1.0 Sender: adam.spence@gmail.com Received: by 10.204.101.207 with SMTP id d15mr6135769bko.93.1249948356461; Mon, 10 Aug 2009 16:52:36 -0700 (PDT) In-Reply-To: References: <20090809081748.23240@gmx.net> <4A7F09D7.8030601@u.washington.edu> Date: Tue, 11 Aug 2009 00:52:36 +0100 X-Google-Sender-Auth: f8bd9fecb0269d90 Message-ID: Subject: Re: [Paparazzi-devel] crashed From: Adam Spence <4x4Ninja@gmail.com> To: paparazzi-devel@nongnu.org Content-Type: multipart/alternative; boundary=0016e6de17dac6477b0470d24755 X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Aug 2009 23:52:44 -0000 --0016e6de17dac6477b0470d24755 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Ah cool, I was merely looking at the over view diagram on the wiki so probably didn't study it quite enough. Adam 2009/8/10 Yves Touchette > > When you are talking about 'current-limiting switch on the hardware' are > you referring to the TPS2051? If so, this switch is only used to switch the > AUX output. It was meant to turn on/off some type of payload, etc... It's > not used for powering the servos. Also, the Overcurrent pin isn't connected. > > I do not believe that there is anything limiting the current to the servos. > > -yvest > > ------------------------------ > Date: Mon, 10 Aug 2009 08:50:30 +0100 > Subject: Re: [Paparazzi-devel] crashed > From: 4x4Ninja@gmail.com > To: paparazzi-devel@nongnu.org > > John, what are you referring to with the RC RX cable? Is this the PPM cable > attaching the receiver to PPZ? > > There's been a couple of crashes like this discussed on IRC recently. I'm > not sure if the fault was identified but the overloading of the 5v PSU was > suggested. This could easily happen when the servos are driven to the limit > and stall due to the hardware set up. Where ever possible the currents drawn > by the servos need to be measured when all control surfaces are at the > limit. If there are any stall conditions the setup needs to be adjusted > either physically on the air frame or by reducing the control throws in the > config file. > The 5V PSU is not only responsible for supplying the servo power but also > the 3v3 regulators power! Therefore if the 5v line drops due to too much > current being drawn then it may take out the main CPU. For my particular > setup with an 868 modem, the CPU, GPS and Modem can take upto 500mA of > current. The limit of the 5V PSU is 2.25A so roughly there may be something > in the region of 1.75A left for all of the servos. That only needs a couple > of servos to stall and you could be in trouble. > > Due to the above, I will be removing the 5V connection to the servos and > providing another regulated 5v directly from the battery. This will have a > limit of maybe 5-10A which is complete over kill. > > I've just noticed the current-limiting switch on the hardware, this means > the servos can only draw 1A and then the switch kicks in and notifies the > CPU using GPIO. Does anyone know what the firmware does in this instance? > That therefore means that there's even less current available for the servos > and anything else which you may have connected on the 5v rail... hmmm. I see > this can trigger from 0.5A to 1.25A, anyone ever tested this? I'm wondering > now what would happen if this were to fire, the servos would be left in > their current position (or driven back slightly from mechanical pressure). > The AP might (depending on what the GPIO signal does) try and keep driving > the servos at their current position which would mean that when the current > limiter recovers it then goes straight to the limit again? > > Anyway I've rambled enough this morning! > > Adam > > 2009/8/9 John Burt > > Martin, > > I crashed an Easystar just like that during early flight testing. The AP > (Tiny 2.11) went nonresponsive and dived into the ground, despite my having > immediately flipped the switch to manual. It would seem that the AP > processor just locked up - truly a worst case scenario. The cause of the > behavior was an undervoltage spike condition due to sourcing the four servos > and RC RX off the 5V supply. In case you haven't already, you should always > power your hardware off a separate BEC (which begs the question of why the > AP has a 5V source anyway). > > AP generated noise on the ground wire was other cause of bad AP behavior > that I experienced. This causes glitching and reduced RC range. It has been > covered ad nauseam in other posts, but I'll repeat it: it's especially > helpful to put an RF choke on the RC RX cable. Try to wrap the wire 4+ times > around the choke. > > > Martin P wrote: > > Hello everyone! > Last weekend I had a good AUTO1 flight with my Minimag. It reacted to pitch > and roll commands, and I was able to control the throttle. I had an attitude > command in my flightplan which was never left (as I know now). > Yesterday I tried again, without the attitude statement and without a > holding point block. > In AUTO1, it killed the throttle. Switched to manual and landed to change > battery because it was not fully charged. > Took off again. Switched to AUTO1 and it immediately stabilized the plane. > Strangely, this time it did not react to the roll command. I flew around > using the rudder. When I used the elevator stick, the autopilot controlled > the throttle. Good, so far. > Suddenly the plane dived down vertically from an altitude of roughly 40m. > No reaction, just kept going vertical and slowly spinning around the > longitudinal axis until it crashed. > There was not as much damage done as I expected. These foamies are awesome. > All RC components including Tiny and Xbee are OK. Except for the Lipo which > is badly bent out of shape and will be replaced for safety reasons. > Unfortunately I can't see much from the log as I had lost the link probably > minutes before. I was in stage "HOME" because I had left the fly-too-far > circle before and came back manually. > The switch was on manual so I probably tried to rescue. The Tiny was > unplugged which can have happened at the crash or before. One aileron was > ripped off and the horizontal IR was missing (I found it in the grass). > So far, my report. The Minimag is already repaired and I'll keep trying. > Greetz, Martin > > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > > > > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > > > > ------------------------------ > Attention all humans. We are your photos. Free us. > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > > --0016e6de17dac6477b0470d24755 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Ah cool, I was merely looking at the over view diagram on the wiki so proba= bly didn't study it quite enough.

Adam

2009/8/10 Yves Touchette <yves_touchette@hotmail.com>

When you are talking about 'current-limiting switch on the hardware= ' are you referring to the TPS2051? If so, this switch is only used to = switch the AUX output. It was meant to turn on/off some type of payload, et= c... It's not used for powering the servos. Also, the Overcurrent pin i= sn't connected.

I do not believe that there is anything limiting the current to the ser= vos.

-yvest


Date: Mon, 10 Aug 2009 08:50:30 +0100

Subject: Re: [Paparazzi-devel] crashed
From: 4x4Ninja@gmail.com
To: pap= arazzi-devel@nongnu.org

=
John, what are you referring to with the RC RX cable? Is this the PPM = cable attaching the receiver to PPZ?

There's been a couple of crashes like this discussed on = IRC recently. I'm not sure if the fault was identified but the overload= ing of the 5v PSU was suggested. This could easily happen when the servos a= re driven to the limit and stall due to the hardware set up. Where ever pos= sible the currents drawn by the servos need to be measured when all control= surfaces are at the limit. If there are any stall conditions the setup nee= ds to be adjusted either physically on the air frame or by reducing the con= trol throws in the config file.

The 5V PSU is not only responsible for supplying the servo p= ower but also the 3v3 regulators power! Therefore if the 5v line drops due = to too much current being drawn then it may take out the main CPU. For my p= articular setup with an 868 modem, the CPU, GPS and Modem can take upto 500= mA of current. The limit of the 5V PSU is 2.25A so roughly there may be som= ething in the region of 1.75A left for all of the servos. That only needs a= couple of servos to stall and you could be in trouble.

Due to the above, I will be removing the 5V connection = to the servos and providing another regulated 5v directly from the battery.= This will have a limit of maybe 5-10A which is complete over kill.

I've just noticed the current-limiting switch on th= e hardware, this means the servos can only draw 1A and then the switch kick= s in and notifies the CPU using GPIO. Does anyone know what the firmware do= es in this instance? That therefore means that there's even less curren= t available for the servos and anything else which you may have connected o= n the 5v rail... hmmm. I see this can trigger from 0.5A to 1.25A, anyone ev= er tested this? I'm wondering now what would happen if this were to fir= e, the servos would be left in their current position (or driven back sligh= tly from mechanical pressure). The AP might (depending on what the GPIO sig= nal does) try and keep driving the servos at their current position which w= ould mean that when the current limiter recovers it then goes straight to t= he limit again?

Anyway I've rambled enough this morning!
=
Adam=A0

2009/8/9 John Burt <quill@u.w= ashington.edu>
Martin,

I crashed an Easystar just like that during early flight testing. The AP (T= iny 2.11) went nonresponsive and dived into the ground, despite my having i= mmediately flipped the switch to manual. It would seem that the AP processo= r just locked up - truly a worst case scenario. The cause of the behavior w= as an undervoltage spike condition due to sourcing the four servos and RC R= X off the 5V supply. In case you haven't already, you should always pow= er your hardware off a separate BEC (which begs the question of why the AP = has a 5V source anyway).

AP generated noise on the ground wire was other cause of bad AP behavior th= at I experienced. This causes glitching and reduced RC range. It has been c= overed ad nauseam in other posts, but I'll repeat it: it's especial= ly helpful to put an RF choke on the RC RX cable. Try to wrap the wire 4+ t= imes around the choke.


Martin P wrote:
Hello everyone!
Last weekend I had a good AUTO1 flight with my Minimag. It reacted to pitch= and roll commands, and I was able to control the throttle. I had an attitu= de command in my flightplan which was never left (as I know now). =A0
Yesterday I tried again, without the attitude statement and without a holdi= ng point block.
In AUTO1, it killed the throttle. Switched to manual and landed to change b= attery because it was not fully charged.
Took off again. Switched to AUTO1 and it immediately stabilized the plane. = Strangely, this time it did not react to the roll command. I flew around us= ing the rudder. When I used the elevator stick, the autopilot controlled th= e throttle. Good, so far.
Suddenly the plane dived down vertically from an altitude of roughly 40m. N= o reaction, just kept going vertical and slowly spinning around the longitu= dinal axis until it crashed.
There was not as much damage done as I expected. These foamies are awesome.= All RC components including Tiny and Xbee are OK. Except for the Lipo whic= h is badly bent out of shape and will be replaced for safety reasons.
Unfortunately I can't see much from the log as I had lost the link prob= ably minutes before. I was in stage "HOME" because I had left the= fly-too-far circle before and came back manually. =A0
The switch was on manual so I probably tried to rescue. The Tiny was unplug= ged which can have happened at the crash or before. One aileron was ripped = off and the horizontal IR was missing (I found it in the grass).
So far, my report. The Minimag is already repaired and I'll keep trying= .
Greetz, Martin


_______________________________________________
Paparazzi-devel mailing list
Paparazzi-d= evel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/paparazzi-devel =A0


_______________________________________________
Paparazzi-devel mailing list
Paparazzi-d= evel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/paparazzi-devel



Attentio= n all humans. We are your photos. Free us.

_______________________________________________
Paparazzi-devel mailing list
Paparazzi-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/paparazzi-devel

--0016e6de17dac6477b0470d24755-- From MAILER-DAEMON Tue Aug 11 01:42:25 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Mak7s-0004a0-SP for mharc-paparazzi-devel@gnu.org; Tue, 11 Aug 2009 01:42:24 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mak7p-0004Zu-Sh for paparazzi-devel@nongnu.org; Tue, 11 Aug 2009 01:42:21 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mak7k-0004Za-VH for paparazzi-devel@nongnu.org; Tue, 11 Aug 2009 01:42:21 -0400 Received: from [199.232.76.173] (port=44596 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mak7k-0004ZX-NK for paparazzi-devel@nongnu.org; Tue, 11 Aug 2009 01:42:16 -0400 Received: from mail-ew0-f210.google.com ([209.85.219.210]:37906) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Mak7j-00068A-57 for paparazzi-devel@nongnu.org; Tue, 11 Aug 2009 01:42:16 -0400 Received: by ewy6 with SMTP id 6so1668875ewy.34 for ; Mon, 10 Aug 2009 22:42:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=wivdBKnfTkfUrvm8GM4mCHxQIPtfu9X32356XlQRoc0=; b=jnZ2K9sRGGlveizqoxfTu0wU6Wvq8V3AkaWWZl7oKFo0ErH+DOP4Hgm0sIz7rm6daE OK4AvwJSsJXvcFVG/TmvJtjFPkTBiZQJYE+eqKdnv6UnFAp3Wwn4DY0LJoGbCQjGjpe+ GaoQpphA3jvLoXSHaLCqZggVC5q5fpIKxRT/A= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=N+wbtgzQ48ugx29qxbeHXrZJOrMWywWkaiou/UJ28QOVgOdj1Zsi9kFSx4PARqQaFx k5/fAEM9unqLww2j7zvEhbyNtPJzIiPt7V+gEg6YF4FLJsT977Y9hoDt5Di1bLa9Kby7 RbUCUldBZuGNWlpfRKRckL+GwLW6Yx+mmNkVE= MIME-Version: 1.0 Received: by 10.216.6.198 with SMTP id 48mr1189060wen.200.1249969333388; Mon, 10 Aug 2009 22:42:13 -0700 (PDT) In-Reply-To: References: <20090809081748.23240@gmx.net> <4A7F09D7.8030601@u.washington.edu> <4A8043E1.4050107@u.washington.edu> Date: Tue, 11 Aug 2009 07:42:13 +0200 Message-ID: <689b39d80908102242j7ddc6514mb475ad0ac80a6664@mail.gmail.com> Subject: Re: [Paparazzi-devel] crashed, 5V supply overloading issue From: Michel GORRAZ To: paparazzi-devel@nongnu.org Content-Type: multipart/alternative; boundary=0016364d1d9118c7690470d72af5 X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Aug 2009 05:42:22 -0000 --0016364d1d9118c7690470d72af5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi, Don't forget that "Tiny" means autopilot for small aircraft equipped with....small servos. @+ Michel 2009/8/11 Adam Spence <4x4Ninja@gmail.com> > Sounds very good, anyone want to knock one up? I was going to do the half > way house and still use the signals from PPZ but it may be cleaner to have > the demux on board like you've suggested. > > 2009/8/10 Yves Touchette > > I personnally think that the best solution is not to power the servos from >> the AP, period. >> >> How about designing a PCB that would contain a servo demux (like a 4017), >> be powered by the ESC BEC and have pads for both .1" connectors (regular >> servos) and for pico blade connectors? >> >> Many of the newer good quality ESC have switching BEC's that are more then >> capable of driving a reasonable server load. >> >> Running of the BEC will also prevent power related crashs. The BEC is >> already in most planes. Those that don't have one (glow engins, etc) could >> use an external BEC. >> >> This should be pretty easy to build without having to reroute a complete >> AP. >> >> The two sets of connectors would alow users to choose which they prefer >> and install only those. >> >> Does this sound good? >> >> -yvest >> >> > Date: Mon, 10 Aug 2009 08:59:29 -0700 >> > From: quill@u.washington.edu >> > To: paparazzi-devel@nongnu.org >> > Subject: Re: [Paparazzi-devel] crashed, 5V supply overloading issue >> >> > >> > Yes, I am referring to the PPM signal from the RC receiver to PPZ. >> > >> > It was pretty clear that the fault was due to an overloaded 5V supply. >> > On the ground I was able to faithfully re-create the AP crash conditions >> >> > simply by rapidly exercising all the servos. I also did fairly extensive >> >> > testing to debug this problem, including measuring current drain with >> > all servos operating, which is what clarified the issue. >> > >> > I have suggested in the past that PPZ be updated with a higher capacity >> > 5V converter, and given what you wrote below, it might also be a good >> > thing to source the 3.3v line off the battery, rather than the 5V >> > supply. However, the "temporary" solution is to simply use a separate 5V >> >> > supply for external devices like servos, modems, etc. >> > >> > Adam Spence wrote: >> > > John, what are you referring to with the RC RX cable? Is this the PPM >> > > cable attaching the receiver to PPZ? >> > > >> > > There's been a couple of crashes like this discussed on IRC recently. >> > > I'm not sure if the fault was identified but the overloading of the 5v >> >> > > PSU was suggested. This could easily happen when the servos are driven >> >> > > to the limit and stall due to the hardware set up. Where ever possible >> >> > > the currents drawn by the servos need to be measured when all control >> > > surfaces are at the limit. If there are any stall conditions the setup >> >> > > needs to be adjusted either physically on the air frame or by reducing >> >> > > the control throws in the config file. >> > > >> > > The 5V PSU is not only responsible for supplying the servo power but >> > > also the 3v3 regulators power! Therefore if the 5v line drops due to >> too >> > > much current being drawn then it may take out the main CPU. For my >> > > particular setup with an 868 modem, the CPU, GPS and Modem can take >> upto >> > > 500mA of current. The limit of the 5V PSU is 2.25A so roughly there >> may >> > > be something in the region of 1.75A left for all of the servos. That >> > > only needs a couple of servos to stall and you could be in trouble. >> > > >> > > Due to the above, I will be removing the 5V connection to the servos >> and >> > > providing another regulated 5v directly from the battery. This will >> have >> > > a limit of maybe 5-10A which is complete over kill. >> > > >> > > I've just noticed the current-limiting switch on the hardware, this >> > > means the servos can only draw 1A and then the switch kicks in and >> > > notifies the CPU using GPIO. Does anyone know what the firmware does >> in >> > > this instance? That therefore means that there's even less current >> > > available for the servos and anything else which you may have >> connected >> > > on the 5v rail... hmmm. I see this can trigger from 0.5A to 1.25A, >> > > anyone ever tested this? I'm wondering now what would happen if this >> > > were to fire, the servos would be left in their current position (or >> > > driven back slightly from mechanical pressure). The AP might >> (depending >> > > on what the GPIO signal does) try and keep driving the servos at their >> >> > > current position which would mean that when the current limiter >> recovers >> > > it then goes straight to the limit again? >> > > >> > > Anyway I've rambled enough this morning! >> > > >> > > Adam >> > > >> > > 2009/8/9 John Burt > quill@u.washington.edu>> >> > > >> > > Martin, >> > > >> > > I crashed an Easystar just like that during early flight testing. >> > > The AP (Tiny 2.11) went nonresponsive and dived into the ground, >> > > despite my having immediately flipped the switch to manual. It would >> > > seem that the AP processor just locked up - truly a worst case >> > > scenario. The cause of the behavior was an undervoltage spike >> > > condition due to sourcing the four servos and RC RX off the 5V >> > > supply. In case you haven't already, you should always power your >> > > hardware off a separate BEC (which begs the question of why the AP >> > > has a 5V source anyway). >> > > >> > > AP generated noise on the ground wire was other cause of bad AP >> > > behavior that I experienced. This causes glitching and reduced RC >> > > range. It has been covered ad nauseam in other posts, but I'll >> > > repeat it: it's especially helpful to put an RF choke on the RC RX >> > > cable. Try to wrap the wire 4+ times around the choke. >> > > >> > > >> > > Martin P wrote: >> > > >> > > Hello everyone! >> > > Last weekend I had a good AUTO1 flight with my Minimag. It >> > > reacted to pitch and roll commands, and I was able to control >> > > the throttle. I had an attitude command in my flightplan which >> > > was never left (as I know now). >> > > Yesterday I tried again, without the attitude statement and >> > > without a holding point block. >> > > In AUTO1, it killed the throttle. Switched to manual and landed >> > > to change battery because it was not fully charged. >> > > Took off again. Switched to AUTO1 and it immediately stabilized >> > > the plane. Strangely, this time it did not react to the roll >> > > command. I flew around using the rudder. When I used the >> > > elevator stick, the autopilot controlled the throttle. Good, so >> > > far. >> > > Suddenly the plane dived down vertically from an altitude of >> > > roughly 40m. No reaction, just kept going vertical and slowly >> > > spinning around the longitudinal axis until it crashed. >> > > There was not as much damage done as I expected. These foamies >> > > are awesome. All RC components including Tiny and Xbee are OK. >> > > Except for the Lipo which is badly bent out of shape and will be >> > > replaced for safety reasons. >> > > Unfortunately I can't see much from the log as I had lost the >> > > link probably minutes before. I was in stage "HOME" because I >> > > had left the fly-too-far circle before and came back manually. >> > > The switch was on manual so I probably tried to rescue. The Tiny >> > > was unplugged which can have happened at the crash or before. >> > > One aileron was ripped off and the horizontal IR was missing (I >> > > found it in the grass). >> > > So far, my report. The Minimag is already repaired and I'll keep >> > > trying. >> > > Greetz, Martin >> > > >> > > >> > > _______________________________________________ >> > > Paparazzi-devel mailing list >> > > Paparazzi-devel@nongnu.org >> > > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel >> > > >> > > >> > > >> > > >> > > _______________________________________________ >> > > Paparazzi-devel mailing list >> > > Paparazzi-devel@nongnu.org >> > > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel >> > > >> > > >> > > >> > > >> ------------------------------------------------------------------------ >> > > >> > > _______________________________________________ >> > > Paparazzi-devel mailing list >> > > Paparazzi-devel@nongnu.org >> > > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel >> > >> > >> > _______________________________________________ >> > Paparazzi-devel mailing list >> > Paparazzi-devel@nongnu.org >> > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel >> >> ------------------------------ >> Stay in the loop and chat with friends, right from your inbox! Learn how! >> >> _______________________________________________ >> Paparazzi-devel mailing list >> Paparazzi-devel@nongnu.org >> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel >> >> > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > > --0016364d1d9118c7690470d72af5 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,

Don't forget that "Tiny" means autopilot for small= aircraft equipped with....small servos.

@+
Michel

2009/8/11 Adam Spence <4x4Ninja@gmail.com>
Sounds very good,= anyone want to knock one up? I was going to do the half way house and stil= l use the signals from PPZ but it may be cleaner to have the demux on board= like you've suggested.

2009/8/10 Yves Touchette <yves_touchette@hotmail.com>

I personnally think that the best solution is not to power the servos from = the AP, period.

How about designing a PCB that would contain a serv= o demux (like a 4017), be powered by the ESC BEC and have pads for both .1&= quot; connectors (regular servos) and for pico blade connectors?

Many of the newer good quality ESC have switching BEC's that are mo= re then capable of driving a reasonable server load.

Running of the = BEC will also prevent power related crashs. The BEC is already in most plan= es. Those that don't have one (glow engins, etc) could use an external = BEC.

This should be pretty easy to build without having to reroute a complet= e AP.

The two sets of connectors would alow users to choose which th= ey prefer and install only those.

Does this sound good?

-yvest

> Date: Mon, 10 Aug 2009 08:59:29 -0700
> From: quill@u.washington.edu> To: p= aparazzi-devel@nongnu.org
> Subject: Re: [Paparazzi-devel] crashed, 5V supply overloading issue

>
> Yes, I am referring to the PPM signal f= rom the RC receiver to PPZ.
>
> It was pretty clear that the f= ault was due to an overloaded 5V supply.
> On the ground I was able to faithfully re-create the AP crash conditio= ns
> simply by rapidly exercising all the servos. I also did fairly = extensive
> testing to debug this problem, including measuring curre= nt drain with
> all servos operating, which is what clarified the issue.
>
&= gt; I have suggested in the past that PPZ be updated with a higher capacity=
> 5V converter, and given what you wrote below, it might also be a = good
> thing to source the 3.3v line off the battery, rather than the 5V
= > supply. However, the "temporary" solution is to simply use a= separate 5V
> supply for external devices like servos, modems, etc.=
>
> Adam Spence wrote:
> > John, what are you referring = to with the RC RX cable? Is this the PPM
> > cable attaching the = receiver to PPZ?
> >
> > There's been a couple of cr= ashes like this discussed on IRC recently.
> > I'm not sure if the fault was identified but the overloading = of the 5v
> > PSU was suggested. This could easily happen when th= e servos are driven
> > to the limit and stall due to the hardwar= e set up. Where ever possible
> > the currents drawn by the servos need to be measured when all con= trol
> > surfaces are at the limit. If there are any stall condit= ions the setup
> > needs to be adjusted either physically on the = air frame or by reducing
> > the control throws in the config file.
> >
> >= The 5V PSU is not only responsible for supplying the servo power but
&= gt; > also the 3v3 regulators power! Therefore if the 5v line drops due = to too
> > much current being drawn then it may take out the main CPU. For m= y
> > particular setup with an 868 modem, the CPU, GPS and Modem = can take upto
> > 500mA of current. The limit of the 5V PSU is 2.= 25A so roughly there may
> > be something in the region of 1.75A left for all of the servos. T= hat
> > only needs a couple of servos to stall and you could be i= n trouble.
> >
> > Due to the above, I will be removing = the 5V connection to the servos and
> > providing another regulated 5v directly from the battery. This wi= ll have
> > a limit of maybe 5-10A which is complete over kill.> >
> > I've just noticed the current-limiting switch= on the hardware, this
> > means the servos can only draw 1A and then the switch kicks in an= d
> > notifies the CPU using GPIO. Does anyone know what the firm= ware does in
> > this instance? That therefore means that there&#= 39;s even less current
> > available for the servos and anything else which you may have con= nected
> > on the 5v rail... hmmm. I see this can trigger from 0.= 5A to 1.25A,
> > anyone ever tested this? I'm wondering now w= hat would happen if this
> > were to fire, the servos would be left in their current position = (or
> > driven back slightly from mechanical pressure). The AP mi= ght (depending
> > on what the GPIO signal does) try and keep dri= ving the servos at their
> > current position which would mean that when the current limiter r= ecovers
> > it then goes straight to the limit again?
> >= ;
> > Anyway I've rambled enough this morning!
> > <= br> > > Adam
> >
> > 2009/8/9 John Burt <quill@u.washington.edu= <mailto:quill@u.washington.edu>>
> >
> > Martin,
> >
> > I crashe= d an Easystar just like that during early flight testing.
> > = The AP (Tiny 2.11) went nonresponsive and dived into the ground,
> &g= t; despite my having immediately flipped the switch to manual. It would=
> > seem that the AP processor just locked up - truly a worst cas= e
> > scenario. The cause of the behavior was an undervoltage = spike
> > condition due to sourcing the four servos and RC RX = off the 5V
> > supply. In case you haven't already, you should always po= wer your
> > hardware off a separate BEC (which begs the quest= ion of why the AP
> > has a 5V source anyway).
> > > > AP generated noise on the ground wire was other cause of bad = AP
> > behavior that I experienced. This causes glitching and = reduced RC
> > range. It has been covered ad nauseam in other = posts, but I'll
> > repeat it: it's especially helpful to put an RF choke on = the RC RX
> > cable. Try to wrap the wire 4+ times around the = choke.
> >
> >
> > Martin P wrote:
> >
> > Hello everyone!
> > Last w= eekend I had a good AUTO1 flight with my Minimag. It
> > r= eacted to pitch and roll commands, and I was able to control
> > = the throttle. I had an attitude command in my flightplan which
> > was never left (as I know now).
> > Ye= sterday I tried again, without the attitude statement and
> > = without a holding point block.
> > In AUTO1, it killed= the throttle. Switched to manual and landed
> > to change battery because it was not fully charged.
&g= t; > Took off again. Switched to AUTO1 and it immediately stabil= ized
> > the plane. Strangely, this time it did not react = to the roll
> > command. I flew around using the rudder. When I used the<= br>> > elevator stick, the autopilot controlled the throttle.= Good, so
> > far.
> > Suddenly the plane= dived down vertically from an altitude of
> > roughly 40m. No reaction, just kept going vertical and sl= owly
> > spinning around the longitudinal axis until it cr= ashed.
> > There was not as much damage done as I expected= . These foamies
> > are awesome. All RC components including Tiny and Xbee ar= e OK.
> > Except for the Lipo which is badly bent out of s= hape and will be
> > replaced for safety reasons.
> > Unfortunately I can't see much from the log as I had = lost the
> > link probably minutes before. I was in stage "HOME&q= uot; because I
> > had left the fly-too-far circle before = and came back manually.
> > The switch was on manual so = I probably tried to rescue. The Tiny
> > was unplugged which can have happened at the crash or bef= ore.
> > One aileron was ripped off and the horizontal IR = was missing (I
> > found it in the grass).
> > = So far, my report. The Minimag is already repaired and I'll keep<= br> > > trying.
> > Greetz, Martin
> > =
> >
> > _______________________________________= ________
> > Paparazzi-devel mailing list
> > = Papara= zzi-devel@nongnu.org <mailto:Paparazzi-devel@nongnu.org>
> > http://lists.nongnu.org/mailman/listinfo/papa= razzi-devel
> >
> >
> >
> = >
> > _______________________________________________
> > = Paparazzi-devel mailing list
> > Paparazzi-devel@nongnu.org <m= ailto:Papar= azzi-devel@nongnu.org>
> > http://lists.nongnu.org/mailman/listinfo/paparazz= i-devel
> >
> >
> >
> > --------= ----------------------------------------------------------------
> >
> > _______________________________________________
= > > Paparazzi-devel mailing list
> > Paparazzi-devel@nongnu.org
> > http://lists.nongnu.org/mailman/listinfo/paparazzi-de= vel
>
>
> _________________________________________= ______
> Paparazzi-devel mailing list
> Paparazzi-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel


Stay in the loop and chat with friends, right from your= inbox! Learn how!

_______________________________________________
Paparazzi-devel mailing list
Paparazzi-d= evel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/paparazzi-devel


_______________________________________________
Paparazzi-devel mailing list
Paparazzi-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/paparazzi-devel

--0016364d1d9118c7690470d72af5-- From MAILER-DAEMON Tue Aug 11 03:35:39 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MaltS-0007iU-UI for mharc-paparazzi-devel@gnu.org; Tue, 11 Aug 2009 03:35:38 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MaltR-0007hL-2R for paparazzi-devel@nongnu.org; Tue, 11 Aug 2009 03:35:37 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MaltM-0007dP-61 for paparazzi-devel@nongnu.org; Tue, 11 Aug 2009 03:35:36 -0400 Received: from [199.232.76.173] (port=50527 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MaltL-0007dD-UX for paparazzi-devel@nongnu.org; Tue, 11 Aug 2009 03:35:32 -0400 Received: from mx20.gnu.org ([199.232.41.8]:49897) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MaltK-00075X-Ss for paparazzi-devel@nongnu.org; Tue, 11 Aug 2009 03:35:31 -0400 Received: from wf-out-1314.google.com ([209.85.200.172]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MaltJ-0007Rq-Br for paparazzi-devel@nongnu.org; Tue, 11 Aug 2009 03:35:29 -0400 Received: by wf-out-1314.google.com with SMTP id 26so1316617wfd.4 for ; Tue, 11 Aug 2009 00:35:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=fmSuzLN3kfwIUVYIzdWNGhDHPgSbdJZzwIc/sJfvkgM=; b=vO6zNG5on2rQ5z/feJODVj0WD6mGvre5gtvkPzoGekB92A+dgiG1SA2thv6X8aOe4O 9LTrJQnck1jHd5tC/W0FCRnF62cVWeUkaSJ1iQYE8OeaI/yZVMAR5SJmo718hnoYOC/j sERQu/CdbDbcbLJ/ShiEMffJap4+T5RDvDR/U= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=cqjoqjrHHR0eQZGKlmUK8IlNwpiWQIrOrYDX+udT4+Wupw0gTldG4dVFjF0pXNMhF2 gx1Hp0CGytAUHBMjpweM5hL5V9pUSy0nuGVsz3pQkOapoAFT5gGCgzgzxE3NjJbrUNlo Kx+nZ9S3cKRhDJ9Z01n7RvWYFODS3scBRmHO4= MIME-Version: 1.0 Received: by 10.142.155.17 with SMTP id c17mr182667wfe.207.1249976127365; Tue, 11 Aug 2009 00:35:27 -0700 (PDT) In-Reply-To: <689b39d80908102242j7ddc6514mb475ad0ac80a6664@mail.gmail.com> References: <20090809081748.23240@gmx.net> <4A7F09D7.8030601@u.washington.edu> <4A8043E1.4050107@u.washington.edu> <689b39d80908102242j7ddc6514mb475ad0ac80a6664@mail.gmail.com> Date: Tue, 11 Aug 2009 17:35:27 +1000 Message-ID: <8a0861de0908110035h7e6649bkd762256d017cef40@mail.gmail.com> Subject: Re: [Paparazzi-devel] crashed, 5V supply overloading issue From: Chris Gough To: paparazzi-devel@nongnu.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Detected-Operating-System: by mx20.gnu.org: GNU/Linux 2.6 (newer, 2) X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6, seldom 2.4 (older, 4) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Aug 2009 07:35:37 -0000 I sourced* some very cheep 2.4Ghz radio gear from EBay (Hong Kong). The included receiver has a "main" part (servos, aerial, and satelite plug) and a "satellite" part (with just an aerial and 3 twisted wires that I think are PPM). My initial plan was to plug the PPM from the satellite directly into the tiny, and discard the "main" part (until I learned the transmitter was probably not legal here in AU, and shelved the lot). It occurs to me that simply removing the aerial from the "main" part would turn it into a PPM demultiplexer that I could use with a BEC, if I needed to drive a collection of non-tiny servos. Would that be a (this) lazy-man's implementation of what are suggesting Yves, or have I misunderstood? Is modulated output available from the tiny, instead of PWM (yes, I am that ignorant)? -- Chris * Like this one (I'm not seller) http://cgi.ebay.com.au/RC-Turborix-2-4Ghz-6-Channel-Digital-Radio-Receiver-Rx_W0QQitemZ110406182895QQcmdZViewItemQQptZAU_Toys_Hobbies_Radio_Controlled_Vehicles?hash=item19b4b8a7ef&_trksid=p4634.c0.m14.l1262 On Tue, Aug 11, 2009 at 3:42 PM, Michel GORRAZ wrote: > Hi, > > Don't forget that "Tiny" means autopilot for small aircraft equipped > with....small servos. > > @+ > Michel > > 2009/8/11 Adam Spence <4x4Ninja@gmail.com> >> >> Sounds very good, anyone want to knock one up? I was going to do the half >> way house and still use the signals from PPZ but it may be cleaner to have >> the demux on board like you've suggested. >> >> 2009/8/10 Yves Touchette >>> >>> I personnally think that the best solution is not to power the servos >>> from the AP, period. >>> >>> How about designing a PCB that would contain a servo demux (like a 4017), >>> be powered by the ESC BEC and have pads for both .1" connectors (regular >>> servos) and for pico blade connectors? >>> >>> Many of the newer good quality ESC have switching BEC's that are more >>> then capable of driving a reasonable server load. >>> >>> Running of the BEC will also prevent power related crashs. The BEC is >>> already in most planes. Those that don't have one (glow engins, etc) could >>> use an external BEC. >>> >>> This should be pretty easy to build without having to reroute a complete >>> AP. >>> >>> The two sets of connectors would alow users to choose which they prefer >>> and install only those. >>> >>> Does this sound good? >>> >>> -yvest >>> >>> > Date: Mon, 10 Aug 2009 08:59:29 -0700 >>> > From: quill@u.washington.edu >>> > To: paparazzi-devel@nongnu.org >>> > Subject: Re: [Paparazzi-devel] crashed, 5V supply overloading issue >>> > >>> > Yes, I am referring to the PPM signal from the RC receiver to PPZ. >>> > >>> > It was pretty clear that the fault was due to an overloaded 5V supply. >>> > On the ground I was able to faithfully re-create the AP crash >>> > conditions >>> > simply by rapidly exercising all the servos. I also did fairly >>> > extensive >>> > testing to debug this problem, including measuring current drain with >>> > all servos operating, which is what clarified the issue. >>> > >>> > I have suggested in the past that PPZ be updated with a higher capacity >>> > 5V converter, and given what you wrote below, it might also be a good >>> > thing to source the 3.3v line off the battery, rather than the 5V >>> > supply. However, the "temporary" solution is to simply use a separate >>> > 5V >>> > supply for external devices like servos, modems, etc. >>> > >>> > Adam Spence wrote: >>> > > John, what are you referring to with the RC RX cable? Is this the PPM >>> > > cable attaching the receiver to PPZ? >>> > > >>> > > There's been a couple of crashes like this discussed on IRC recently. >>> > > I'm not sure if the fault was identified but the overloading of the >>> > > 5v >>> > > PSU was suggested. This could easily happen when the servos are >>> > > driven >>> > > to the limit and stall due to the hardware set up. Where ever >>> > > possible >>> > > the currents drawn by the servos need to be measured when all control >>> > > surfaces are at the limit. If there are any stall conditions the >>> > > setup >>> > > needs to be adjusted either physically on the air frame or by >>> > > reducing >>> > > the control throws in the config file. >>> > > >>> > > The 5V PSU is not only responsible for supplying the servo power but >>> > > also the 3v3 regulators power! Therefore if the 5v line drops due to >>> > > too >>> > > much current being drawn then it may take out the main CPU. For my >>> > > particular setup with an 868 modem, the CPU, GPS and Modem can take >>> > > upto >>> > > 500mA of current. The limit of the 5V PSU is 2.25A so roughly there >>> > > may >>> > > be something in the region of 1.75A left for all of the servos. That >>> > > only needs a couple of servos to stall and you could be in trouble. >>> > > >>> > > Due to the above, I will be removing the 5V connection to the servos >>> > > and >>> > > providing another regulated 5v directly from the battery. This will >>> > > have >>> > > a limit of maybe 5-10A which is complete over kill. >>> > > >>> > > I've just noticed the current-limiting switch on the hardware, this >>> > > means the servos can only draw 1A and then the switch kicks in and >>> > > notifies the CPU using GPIO. Does anyone know what the firmware does >>> > > in >>> > > this instance? That therefore means that there's even less current >>> > > available for the servos and anything else which you may have >>> > > connected >>> > > on the 5v rail... hmmm. I see this can trigger from 0.5A to 1.25A, >>> > > anyone ever tested this? I'm wondering now what would happen if this >>> > > were to fire, the servos would be left in their current position (or >>> > > driven back slightly from mechanical pressure). The AP might >>> > > (depending >>> > > on what the GPIO signal does) try and keep driving the servos at >>> > > their >>> > > current position which would mean that when the current limiter >>> > > recovers >>> > > it then goes straight to the limit again? >>> > > >>> > > Anyway I've rambled enough this morning! >>> > > >>> > > Adam >>> > > >>> > > 2009/8/9 John Burt >> > > > >>> > > >>> > > Martin, >>> > > >>> > > I crashed an Easystar just like that during early flight testing. >>> > > The AP (Tiny 2.11) went nonresponsive and dived into the ground, >>> > > despite my having immediately flipped the switch to manual. It would >>> > > seem that the AP processor just locked up - truly a worst case >>> > > scenario. The cause of the behavior was an undervoltage spike >>> > > condition due to sourcing the four servos and RC RX off the 5V >>> > > supply. In case you haven't already, you should always power your >>> > > hardware off a separate BEC (which begs the question of why the AP >>> > > has a 5V source anyway). >>> > > >>> > > AP generated noise on the ground wire was other cause of bad AP >>> > > behavior that I experienced. This causes glitching and reduced RC >>> > > range. It has been covered ad nauseam in other posts, but I'll >>> > > repeat it: it's especially helpful to put an RF choke on the RC RX >>> > > cable. Try to wrap the wire 4+ times around the choke. >>> > > >>> > > >>> > > Martin P wrote: >>> > > >>> > > Hello everyone! >>> > > Last weekend I had a good AUTO1 flight with my Minimag. It >>> > > reacted to pitch and roll commands, and I was able to control >>> > > the throttle. I had an attitude command in my flightplan which >>> > > was never left (as I know now). >>> > > Yesterday I tried again, without the attitude statement and >>> > > without a holding point block. >>> > > In AUTO1, it killed the throttle. Switched to manual and landed >>> > > to change battery because it was not fully charged. >>> > > Took off again. Switched to AUTO1 and it immediately stabilized >>> > > the plane. Strangely, this time it did not react to the roll >>> > > command. I flew around using the rudder. When I used the >>> > > elevator stick, the autopilot controlled the throttle. Good, so >>> > > far. >>> > > Suddenly the plane dived down vertically from an altitude of >>> > > roughly 40m. No reaction, just kept going vertical and slowly >>> > > spinning around the longitudinal axis until it crashed. >>> > > There was not as much damage done as I expected. These foamies >>> > > are awesome. All RC components including Tiny and Xbee are OK. >>> > > Except for the Lipo which is badly bent out of shape and will be >>> > > replaced for safety reasons. >>> > > Unfortunately I can't see much from the log as I had lost the >>> > > link probably minutes before. I was in stage "HOME" because I >>> > > had left the fly-too-far circle before and came back manually. >>> > > The switch was on manual so I probably tried to rescue. The Tiny >>> > > was unplugged which can have happened at the crash or before. >>> > > One aileron was ripped off and the horizontal IR was missing (I >>> > > found it in the grass). >>> > > So far, my report. The Minimag is already repaired and I'll keep >>> > > trying. >>> > > Greetz, Martin >>> > > >>> > > >>> > > _______________________________________________ >>> > > Paparazzi-devel mailing list >>> > > Paparazzi-devel@nongnu.org >>> > > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel >>> > > >>> > > >>> > > >>> > > >>> > > _______________________________________________ >>> > > Paparazzi-devel mailing list >>> > > Paparazzi-devel@nongnu.org >>> > > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel >>> > > >>> > > >>> > > >>> > > >>> > > ------------------------------------------------------------------------ >>> > > >>> > > _______________________________________________ >>> > > Paparazzi-devel mailing list >>> > > Paparazzi-devel@nongnu.org >>> > > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel >>> > >>> > >>> > _______________________________________________ >>> > Paparazzi-devel mailing list >>> > Paparazzi-devel@nongnu.org >>> > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel >>> >>> ________________________________ >>> Stay in the loop and chat with friends, right from your inbox! Learn how! >>> _______________________________________________ >>> Paparazzi-devel mailing list >>> Paparazzi-devel@nongnu.org >>> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel >>> >> >> >> _______________________________________________ >> Paparazzi-devel mailing list >> Paparazzi-devel@nongnu.org >> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel >> > > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > > From MAILER-DAEMON Tue Aug 11 03:45:54 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Mam3O-00036W-Mx for mharc-paparazzi-devel@gnu.org; Tue, 11 Aug 2009 03:45:54 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mam3N-00034p-46 for paparazzi-devel@nongnu.org; Tue, 11 Aug 2009 03:45:53 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mam3I-00030B-1w for paparazzi-devel@nongnu.org; Tue, 11 Aug 2009 03:45:52 -0400 Received: from [199.232.76.173] (port=37053 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mam3H-000305-SI for paparazzi-devel@nongnu.org; Tue, 11 Aug 2009 03:45:47 -0400 Received: from mx20.gnu.org ([199.232.41.8]:50664) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Mam3H-0000ew-65 for paparazzi-devel@nongnu.org; Tue, 11 Aug 2009 03:45:47 -0400 Received: from mail-bw0-f227.google.com ([209.85.218.227]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Mam3F-00085i-K0 for paparazzi-devel@nongnu.org; Tue, 11 Aug 2009 03:45:45 -0400 Received: by bwz27 with SMTP id 27so2911051bwz.34 for ; Tue, 11 Aug 2009 00:45:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=/zDlQQGwpui+Lr0oiZqzhd6WoVOsTLYBGPv1OCw+O30=; b=VxXAn8fF1by+YXeNQg5RaDIBdDo+SMRpoIjuoTyKud+/vPVsl7ajNadIt4BJs2xcAR XrnwwppvgJ5ULPaAAS9DJxSGM/g3uOCf8XgyPyoSZLcuQ33ozAaqlDO3dHGTyPmH1vSQ IzRUjUL6Vs809LRo/u8n87yvHG605p+2I0cdY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=xML1TQmkR2dPIutKFFOUbIEZ/nhFjRslMs0cIFaMf99FykkeYjWxYLAFuTdE/h7/Cn xDUcAEdZGBW44R6YO8iNl+fmKxjEkNvRhSbSSWIABNheBtzV+penJzmGaYSJMFP9khUI s5D9FeavA6egSeHjakCP3JoSwu+tR//Y2N6RI= MIME-Version: 1.0 Received: by 10.204.72.130 with SMTP id m2mr5544210bkj.46.1249976741648; Tue, 11 Aug 2009 00:45:41 -0700 (PDT) Date: Tue, 11 Aug 2009 07:45:41 +0000 Message-ID: <4d39daa50908110045t23cc4afcwd7fb6d0d8429c85a@mail.gmail.com> From: Rui Costa To: paparazzi-devel@nongnu.org Content-Type: multipart/alternative; boundary=001636c5abc8a9da810470d8e37d X-Detected-Operating-System: by mx20.gnu.org: GNU/Linux 2.6 (newer, 2) X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. Subject: [Paparazzi-devel] Andreas Dei E-mail Contact X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Aug 2009 07:45:53 -0000 --001636c5abc8a9da810470d8e37d Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hello, I would like to talk with Andreas Dei. What's your e-mail address and nickname on IRC? Best Regards Rui Costa www.azoreanuav.com --001636c5abc8a9da810470d8e37d Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hello,
=A0
I would like to talk with Andreas Dei. What's your e-mail address = and nickname on IRC?

Best Regards
Rui Costa
www.azoreanuav.com
--001636c5abc8a9da810470d8e37d-- From MAILER-DAEMON Tue Aug 11 10:33:55 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MasQE-0004s8-TH for mharc-paparazzi-devel@gnu.org; Tue, 11 Aug 2009 10:33:54 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MasQB-0004pk-Rp for paparazzi-devel@nongnu.org; Tue, 11 Aug 2009 10:33:51 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MasQ7-0004oP-39 for paparazzi-devel@nongnu.org; Tue, 11 Aug 2009 10:33:51 -0400 Received: from [199.232.76.173] (port=53453 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MasQ6-0004oI-QI for paparazzi-devel@nongnu.org; Tue, 11 Aug 2009 10:33:46 -0400 Received: from bay0-omc3-s36.bay0.hotmail.com ([65.54.246.236]:54543) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MasQ5-0004LT-VN for paparazzi-devel@nongnu.org; Tue, 11 Aug 2009 10:33:46 -0400 Received: from BAY119-W4 ([207.46.9.39]) by bay0-omc3-s36.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 11 Aug 2009 07:33:44 -0700 Message-ID: Content-Type: multipart/alternative; boundary="_7f32844b-e9ab-4cb6-a7ab-373ecc379320_" X-Originating-IP: [206.172.0.195] From: Yves Touchette To: Subject: RE: [Paparazzi-devel] crashed, 5V supply overloading issue Date: Tue, 11 Aug 2009 10:33:44 -0400 Importance: Normal In-Reply-To: <8a0861de0908110035h7e6649bkd762256d017cef40@mail.gmail.com> References: <20090809081748.23240@gmx.net> <4A7F09D7.8030601@u.washington.edu> <4A8043E1.4050107@u.washington.edu> <689b39d80908102242j7ddc6514mb475ad0ac80a6664@mail.gmail.com> <8a0861de0908110035h7e6649bkd762256d017cef40@mail.gmail.com> MIME-Version: 1.0 X-OriginalArrivalTime: 11 Aug 2009 14:33:44.0901 (UTC) FILETIME=[BB08CF50:01CA1A90] X-detected-operating-system: by monty-python.gnu.org: Windows 2000 SP4, XP SP1+ X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Aug 2009 14:33:52 -0000 --_7f32844b-e9ab-4cb6-a7ab-373ecc379320_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable > It occurs to me that simply removing the aerial from the "main" part > would turn it into a PPM demultiplexer that I could use with a BEC=2C if > I needed to drive a collection of non-tiny servos. Would that be a > (this) lazy-man's implementation of what are suggesting Yves=2C or have > I misunderstood? =20 Personally=2C I doubt that the main part is just a demux as it has an anten= na=2C etc... > Is modulated output available from the tiny=2C instead of PWM (yes=2C I a= m > that ignorant)? The connector for the receiver as 5 pins two of which are meant to connect = to an external demux. If I remember correctly=2C tiny1.3 had a little bug w= here those pins weren't routed properly=2C but as far as I know=2C they are= OK on tiny 2.11. -yvest > -- > Chris >=20 > * Like this one (I'm not seller) > http://cgi.ebay.com.au/RC-Turborix-2-4Ghz-6-Channel-Digital-Radio-Receive= r-Rx_W0QQitemZ110406182895QQcmdZViewItemQQptZAU_Toys_Hobbies_Radio_Controll= ed_Vehicles?hash=3Ditem19b4b8a7ef&_trksid=3Dp4634.c0.m14.l1262 >=20 > On Tue=2C Aug 11=2C 2009 at 3:42 PM=2C Michel GORRAZ wrote: > > Hi=2C > > > > Don't forget that "Tiny" means autopilot for small aircraft equipped > > with....small servos. > > > > @+ > > Michel > > > > 2009/8/11 Adam Spence <4x4Ninja@gmail.com> > >> > >> Sounds very good=2C anyone want to knock one up? I was going to do the= half > >> way house and still use the signals from PPZ but it may be cleaner to = have > >> the demux on board like you've suggested. > >> > >> 2009/8/10 Yves Touchette > >>> > >>> I personnally think that the best solution is not to power the servos > >>> from the AP=2C period. > >>> > >>> How about designing a PCB that would contain a servo demux (like a 40= 17)=2C > >>> be powered by the ESC BEC and have pads for both .1" connectors (regu= lar > >>> servos) and for pico blade connectors? > >>> > >>> Many of the newer good quality ESC have switching BEC's that are more > >>> then capable of driving a reasonable server load. > >>> > >>> Running of the BEC will also prevent power related crashs. The BEC is > >>> already in most planes. Those that don't have one (glow engins=2C etc= ) could > >>> use an external BEC. > >>> > >>> This should be pretty easy to build without having to reroute a compl= ete > >>> AP. > >>> > >>> The two sets of connectors would alow users to choose which they pref= er > >>> and install only those. > >>> > >>> Does this sound good? > >>> > >>> -yvest > >>> > >>> > Date: Mon=2C 10 Aug 2009 08:59:29 -0700 > >>> > From: quill@u.washington.edu > >>> > To: paparazzi-devel@nongnu.org > >>> > Subject: Re: [Paparazzi-devel] crashed=2C 5V supply overloading iss= ue > >>> > > >>> > Yes=2C I am referring to the PPM signal from the RC receiver to PPZ= . > >>> > > >>> > It was pretty clear that the fault was due to an overloaded 5V supp= ly. > >>> > On the ground I was able to faithfully re-create the AP crash > >>> > conditions > >>> > simply by rapidly exercising all the servos. I also did fairly > >>> > extensive > >>> > testing to debug this problem=2C including measuring current drain = with > >>> > all servos operating=2C which is what clarified the issue. > >>> > > >>> > I have suggested in the past that PPZ be updated with a higher capa= city > >>> > 5V converter=2C and given what you wrote below=2C it might also be = a good > >>> > thing to source the 3.3v line off the battery=2C rather than the 5V > >>> > supply. However=2C the "temporary" solution is to simply use a sepa= rate > >>> > 5V > >>> > supply for external devices like servos=2C modems=2C etc. > >>> > > >>> > Adam Spence wrote: > >>> > > John=2C what are you referring to with the RC RX cable? Is this t= he PPM > >>> > > cable attaching the receiver to PPZ? > >>> > > > >>> > > There's been a couple of crashes like this discussed on IRC recen= tly. > >>> > > I'm not sure if the fault was identified but the overloading of t= he > >>> > > 5v > >>> > > PSU was suggested. This could easily happen when the servos are > >>> > > driven > >>> > > to the limit and stall due to the hardware set up. Where ever > >>> > > possible > >>> > > the currents drawn by the servos need to be measured when all con= trol > >>> > > surfaces are at the limit. If there are any stall conditions the > >>> > > setup > >>> > > needs to be adjusted either physically on the air frame or by > >>> > > reducing > >>> > > the control throws in the config file. > >>> > > > >>> > > The 5V PSU is not only responsible for supplying the servo power = but > >>> > > also the 3v3 regulators power! Therefore if the 5v line drops due= to > >>> > > too > >>> > > much current being drawn then it may take out the main CPU. For m= y > >>> > > particular setup with an 868 modem=2C the CPU=2C GPS and Modem ca= n take > >>> > > upto > >>> > > 500mA of current. The limit of the 5V PSU is 2.25A so roughly the= re > >>> > > may > >>> > > be something in the region of 1.75A left for all of the servos. T= hat > >>> > > only needs a couple of servos to stall and you could be in troubl= e. > >>> > > > >>> > > Due to the above=2C I will be removing the 5V connection to the s= ervos > >>> > > and > >>> > > providing another regulated 5v directly from the battery. This wi= ll > >>> > > have > >>> > > a limit of maybe 5-10A which is complete over kill. > >>> > > > >>> > > I've just noticed the current-limiting switch on the hardware=2C = this > >>> > > means the servos can only draw 1A and then the switch kicks in an= d > >>> > > notifies the CPU using GPIO. Does anyone know what the firmware d= oes > >>> > > in > >>> > > this instance? That therefore means that there's even less curren= t > >>> > > available for the servos and anything else which you may have > >>> > > connected > >>> > > on the 5v rail... hmmm. I see this can trigger from 0.5A to 1.25A= =2C > >>> > > anyone ever tested this? I'm wondering now what would happen if t= his > >>> > > were to fire=2C the servos would be left in their current positio= n (or > >>> > > driven back slightly from mechanical pressure). The AP might > >>> > > (depending > >>> > > on what the GPIO signal does) try and keep driving the servos at > >>> > > their > >>> > > current position which would mean that when the current limiter > >>> > > recovers > >>> > > it then goes straight to the limit again? > >>> > > > >>> > > Anyway I've rambled enough this morning! > >>> > > > >>> > > Adam > >>> > > > >>> > > 2009/8/9 John Burt >>> > > > > >>> > > > >>> > > Martin=2C > >>> > > > >>> > > I crashed an Easystar just like that during early flight testing. > >>> > > The AP (Tiny 2.11) went nonresponsive and dived into the ground= =2C > >>> > > despite my having immediately flipped the switch to manual. It wo= uld > >>> > > seem that the AP processor just locked up - truly a worst case > >>> > > scenario. The cause of the behavior was an undervoltage spike > >>> > > condition due to sourcing the four servos and RC RX off the 5V > >>> > > supply. In case you haven't already=2C you should always power yo= ur > >>> > > hardware off a separate BEC (which begs the question of why the A= P > >>> > > has a 5V source anyway). > >>> > > > >>> > > AP generated noise on the ground wire was other cause of bad AP > >>> > > behavior that I experienced. This causes glitching and reduced RC > >>> > > range. It has been covered ad nauseam in other posts=2C but I'll > >>> > > repeat it: it's especially helpful to put an RF choke on the RC R= X > >>> > > cable. Try to wrap the wire 4+ times around the choke. > >>> > > > >>> > > > >>> > > Martin P wrote: > >>> > > > >>> > > Hello everyone! > >>> > > Last weekend I had a good AUTO1 flight with my Minimag. It > >>> > > reacted to pitch and roll commands=2C and I was able to control > >>> > > the throttle. I had an attitude command in my flightplan which > >>> > > was never left (as I know now). > >>> > > Yesterday I tried again=2C without the attitude statement and > >>> > > without a holding point block. > >>> > > In AUTO1=2C it killed the throttle. Switched to manual and landed > >>> > > to change battery because it was not fully charged. > >>> > > Took off again. Switched to AUTO1 and it immediately stabilized > >>> > > the plane. Strangely=2C this time it did not react to the roll > >>> > > command. I flew around using the rudder. When I used the > >>> > > elevator stick=2C the autopilot controlled the throttle. Good=2C = so > >>> > > far. > >>> > > Suddenly the plane dived down vertically from an altitude of > >>> > > roughly 40m. No reaction=2C just kept going vertical and slowly > >>> > > spinning around the longitudinal axis until it crashed. > >>> > > There was not as much damage done as I expected. These foamies > >>> > > are awesome. All RC components including Tiny and Xbee are OK. > >>> > > Except for the Lipo which is badly bent out of shape and will be > >>> > > replaced for safety reasons. > >>> > > Unfortunately I can't see much from the log as I had lost the > >>> > > link probably minutes before. I was in stage "HOME" because I > >>> > > had left the fly-too-far circle before and came back manually. > >>> > > The switch was on manual so I probably tried to rescue. The Tiny > >>> > > was unplugged which can have happened at the crash or before. > >>> > > One aileron was ripped off and the horizontal IR was missing (I > >>> > > found it in the grass). > >>> > > So far=2C my report. The Minimag is already repaired and I'll kee= p > >>> > > trying. > >>> > > Greetz=2C Martin > >>> > > > >>> > > > >>> > > _______________________________________________ > >>> > > Paparazzi-devel mailing list > >>> > > Paparazzi-devel@nongnu.org > >>> > > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > >>> > > > >>> > > > >>> > > > >>> > > > >>> > > _______________________________________________ > >>> > > Paparazzi-devel mailing list > >>> > > Paparazzi-devel@nongnu.org > >>> > > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > >>> > > > >>> > > > >>> > > > >>> > > > >>> > > -----------------------------------------------------------------= ------- > >>> > > > >>> > > _______________________________________________ > >>> > > Paparazzi-devel mailing list > >>> > > Paparazzi-devel@nongnu.org > >>> > > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > >>> > > >>> > > >>> > _______________________________________________ > >>> > Paparazzi-devel mailing list > >>> > Paparazzi-devel@nongnu.org > >>> > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > >>> > >>> ________________________________ > >>> Stay in the loop and chat with friends=2C right from your inbox! Lear= n how! > >>> _______________________________________________ > >>> Paparazzi-devel mailing list > >>> Paparazzi-devel@nongnu.org > >>> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > >>> > >> > >> > >> _______________________________________________ > >> Paparazzi-devel mailing list > >> Paparazzi-devel@nongnu.org > >> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > >> > > > > > > _______________________________________________ > > Paparazzi-devel mailing list > > Paparazzi-devel@nongnu.org > > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > > > > >=20 >=20 > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel _________________________________________________________________ More storage. Better anti-spam and antivirus protection. Hotmail makes it s= imple. http://go.microsoft.com/?linkid=3D9671357= --_7f32844b-e9ab-4cb6-a7ab-373ecc379320_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable >=3B It occurs to me that simply removing the aerial from the "main" part=
>=3B would turn it into a PPM demultiplexer that I could use with a B= EC=2C if
>=3B I needed to drive a collection of non-tiny servos. Would= that be a
>=3B (this) lazy-man's implementation of what are suggestin= g Yves=2C or have
>=3B I misunderstood?

Personally=2C I doubt = that the main part is just a demux as it has an antenna=2C etc...

&g= t=3B Is modulated output available from the tiny=2C instead of PWM (yes=2C = I am
>=3B that ignorant)?

The connector for the receiver as 5 p= ins two of which are meant to connect to an external demux. If I remember c= orrectly=2C tiny1.3 had a little bug where those pins weren't routed proper= ly=2C but as far as I know=2C they are OK on tiny 2.11.

-yvest
>=3B --
>=3B Chris
>=3B
>=3B * Like this one (I'm not s= eller)
>=3B http://cgi.ebay.com.au/RC-Turborix-2-4Ghz-6-Channel-Digita= l-Radio-Receiver-Rx_W0QQitemZ110406182895QQcmdZViewItemQQptZAU_Toys_Hobbies= _Radio_Controlled_Vehicles?hash=3Ditem19b4b8a7ef&=3B_trksid=3Dp4634.c0.m= 14.l1262
>=3B
>=3B On Tue=2C Aug 11=2C 2009 at 3:42 PM=2C Michel= GORRAZ<=3Bmichel.gorraz@gmail.com>=3B wrote:
>=3B >=3B Hi=2C>=3B >=3B
>=3B >=3B Don't forget that "Tiny" means autopilot fo= r small aircraft equipped
>=3B >=3B with....small servos.
>=3B = >=3B
>=3B >=3B @+
>=3B >=3B Michel
>=3B >=3B
>= =3B >=3B 2009/8/11 Adam Spence <=3B4x4Ninja@gmail.com>=3B
>=3B &= gt=3B>=3B
>=3B >=3B>=3B Sounds very good=2C anyone want to knock= one up? I was going to do the half
>=3B >=3B>=3B way house and st= ill use the signals from PPZ but it may be cleaner to have
>=3B >=3B= >=3B the demux on board like you've suggested.
>=3B >=3B>=3B
= >=3B >=3B>=3B 2009/8/10 Yves Touchette <=3Byves_touchette@hotmail.c= om>=3B
>=3B >=3B>=3B>=3B
>=3B >=3B>=3B>=3B I person= nally think that the best solution is not to power the servos
>=3B >= =3B>=3B>=3B from the AP=2C period.
>=3B >=3B>=3B>=3B
>= =3B >=3B>=3B>=3B How about designing a PCB that would contain a servo= demux (like a 4017)=2C
>=3B >=3B>=3B>=3B be powered by the ESC = BEC and have pads for both .1" connectors (regular
>=3B >=3B>=3B&g= t=3B servos) and for pico blade connectors?
>=3B >=3B>=3B>=3B>=3B >=3B>=3B>=3B Many of the newer good quality ESC have switchin= g BEC's that are more
>=3B >=3B>=3B>=3B then capable of driving = a reasonable server load.
>=3B >=3B>=3B>=3B
>=3B >=3B>= =3B>=3B Running of the BEC will also prevent power related crashs. The BE= C is
>=3B >=3B>=3B>=3B already in most planes. Those that don't = have one (glow engins=2C etc) could
>=3B >=3B>=3B>=3B use an ext= ernal BEC.
>=3B >=3B>=3B>=3B
>=3B >=3B>=3B>=3B This s= hould be pretty easy to build without having to reroute a complete
>= =3B >=3B>=3B>=3B AP.
>=3B >=3B>=3B>=3B
>=3B >=3B>= =3B>=3B The two sets of connectors would alow users to choose which they = prefer
>=3B >=3B>=3B>=3B and install only those.
>=3B >= =3B>=3B>=3B
>=3B >=3B>=3B>=3B Does this sound good?
>= =3B >=3B>=3B>=3B
>=3B >=3B>=3B>=3B -yvest
>=3B >=3B= >=3B>=3B
>=3B >=3B>=3B>=3B >=3B Date: Mon=2C 10 Aug 2009 0= 8:59:29 -0700
>=3B >=3B>=3B>=3B >=3B From: quill@u.washington.= edu
>=3B >=3B>=3B>=3B >=3B To: paparazzi-devel@nongnu.org
&= gt=3B >=3B>=3B>=3B >=3B Subject: Re: [Paparazzi-devel] crashed=2C 5= V supply overloading issue
>=3B >=3B>=3B>=3B >=3B
>=3B &g= t=3B>=3B>=3B >=3B Yes=2C I am referring to the PPM signal from the RC= receiver to PPZ.
>=3B >=3B>=3B>=3B >=3B
>=3B >=3B>= =3B>=3B >=3B It was pretty clear that the fault was due to an overloade= d 5V supply.
>=3B >=3B>=3B>=3B >=3B On the ground I was able t= o faithfully re-create the AP crash
>=3B >=3B>=3B>=3B >=3B con= ditions
>=3B >=3B>=3B>=3B >=3B simply by rapidly exercising al= l the servos. I also did fairly
>=3B >=3B>=3B>=3B >=3B extensi= ve
>=3B >=3B>=3B>=3B >=3B testing to debug this problem=2C inc= luding measuring current drain with
>=3B >=3B>=3B>=3B >=3B all= servos operating=2C which is what clarified the issue.
>=3B >=3B>= =3B>=3B >=3B
>=3B >=3B>=3B>=3B >=3B I have suggested in th= e past that PPZ be updated with a higher capacity
>=3B >=3B>=3B>= =3B >=3B 5V converter=2C and given what you wrote below=2C it might also = be a good
>=3B >=3B>=3B>=3B >=3B thing to source the 3.3v line= off the battery=2C rather than the 5V
>=3B >=3B>=3B>=3B >=3B = supply. However=2C the "temporary" solution is to simply use a separate
= >=3B >=3B>=3B>=3B >=3B 5V
>=3B >=3B>=3B>=3B >=3B sup= ply for external devices like servos=2C modems=2C etc.
>=3B >=3B>= =3B>=3B >=3B
>=3B >=3B>=3B>=3B >=3B Adam Spence wrote:
= >=3B >=3B>=3B>=3B >=3B >=3B John=2C what are you referring to w= ith the RC RX cable? Is this the PPM
>=3B >=3B>=3B>=3B >=3B &g= t=3B cable attaching the receiver to PPZ?
>=3B >=3B>=3B>=3B >= =3B >=3B
>=3B >=3B>=3B>=3B >=3B >=3B There's been a couple= of crashes like this discussed on IRC recently.
>=3B >=3B>=3B>= =3B >=3B >=3B I'm not sure if the fault was identified but the overload= ing of the
>=3B >=3B>=3B>=3B >=3B >=3B 5v
>=3B >=3B&g= t=3B>=3B >=3B >=3B PSU was suggested. This could easily happen when t= he servos are
>=3B >=3B>=3B>=3B >=3B >=3B driven
>=3B &= gt=3B>=3B>=3B >=3B >=3B to the limit and stall due to the hardware = set up. Where ever
>=3B >=3B>=3B>=3B >=3B >=3B possible
&= gt=3B >=3B>=3B>=3B >=3B >=3B the currents drawn by the servos nee= d to be measured when all control
>=3B >=3B>=3B>=3B >=3B >= =3B surfaces are at the limit. If there are any stall conditions the
>= =3B >=3B>=3B>=3B >=3B >=3B setup
>=3B >=3B>=3B>=3B >= =3B >=3B needs to be adjusted either physically on the air frame or by>=3B >=3B>=3B>=3B >=3B >=3B reducing
>=3B >=3B>=3B>= =3B >=3B >=3B the control throws in the config file.
>=3B >=3B&g= t=3B>=3B >=3B >=3B
>=3B >=3B>=3B>=3B >=3B >=3B The 5V = PSU is not only responsible for supplying the servo power but
>=3B >= =3B>=3B>=3B >=3B >=3B also the 3v3 regulators power! Therefore if t= he 5v line drops due to
>=3B >=3B>=3B>=3B >=3B >=3B too
&= gt=3B >=3B>=3B>=3B >=3B >=3B much current being drawn then it may= take out the main CPU. For my
>=3B >=3B>=3B>=3B >=3B >=3B p= articular setup with an 868 modem=2C the CPU=2C GPS and Modem can take
&= gt=3B >=3B>=3B>=3B >=3B >=3B upto
>=3B >=3B>=3B>=3B &g= t=3B >=3B 500mA of current. The limit of the 5V PSU is 2.25A so roughly t= here
>=3B >=3B>=3B>=3B >=3B >=3B may
>=3B >=3B>=3B&= gt=3B >=3B >=3B be something in the region of 1.75A left for all of the= servos. That
>=3B >=3B>=3B>=3B >=3B >=3B only needs a coupl= e of servos to stall and you could be in trouble.
>=3B >=3B>=3B>= =3B >=3B >=3B
>=3B >=3B>=3B>=3B >=3B >=3B Due to the abo= ve=2C I will be removing the 5V connection to the servos
>=3B >=3B&g= t=3B>=3B >=3B >=3B and
>=3B >=3B>=3B>=3B >=3B >=3B pro= viding another regulated 5v directly from the battery. This will
>=3B = >=3B>=3B>=3B >=3B >=3B have
>=3B >=3B>=3B>=3B >=3B &= gt=3B a limit of maybe 5-10A which is complete over kill.
>=3B >=3B&= gt=3B>=3B >=3B >=3B
>=3B >=3B>=3B>=3B >=3B >=3B I've j= ust noticed the current-limiting switch on the hardware=2C this
>=3B &= gt=3B>=3B>=3B >=3B >=3B means the servos can only draw 1A and then = the switch kicks in and
>=3B >=3B>=3B>=3B >=3B >=3B notifies= the CPU using GPIO. Does anyone know what the firmware does
>=3B >= =3B>=3B>=3B >=3B >=3B in
>=3B >=3B>=3B>=3B >=3B >=3B= this instance? That therefore means that there's even less current
>= =3B >=3B>=3B>=3B >=3B >=3B available for the servos and anything = else which you may have
>=3B >=3B>=3B>=3B >=3B >=3B connecte= d
>=3B >=3B>=3B>=3B >=3B >=3B on the 5v rail... hmmm. I see = this can trigger from 0.5A to 1.25A=2C
>=3B >=3B>=3B>=3B >=3B = >=3B anyone ever tested this? I'm wondering now what would happen if this=
>=3B >=3B>=3B>=3B >=3B >=3B were to fire=2C the servos woul= d be left in their current position (or
>=3B >=3B>=3B>=3B >=3B= >=3B driven back slightly from mechanical pressure). The AP might
>= =3B >=3B>=3B>=3B >=3B >=3B (depending
>=3B >=3B>=3B>= =3B >=3B >=3B on what the GPIO signal does) try and keep driving the se= rvos at
>=3B >=3B>=3B>=3B >=3B >=3B their
>=3B >=3B&g= t=3B>=3B >=3B >=3B current position which would mean that when the cu= rrent limiter
>=3B >=3B>=3B>=3B >=3B >=3B recovers
>=3B= >=3B>=3B>=3B >=3B >=3B it then goes straight to the limit again?=
>=3B >=3B>=3B>=3B >=3B >=3B
>=3B >=3B>=3B>=3B &g= t=3B >=3B Anyway I've rambled enough this morning!
>=3B >=3B>=3B= >=3B >=3B >=3B
>=3B >=3B>=3B>=3B >=3B >=3B Adam
>= =3B >=3B>=3B>=3B >=3B >=3B
>=3B >=3B>=3B>=3B >=3B &g= t=3B 2009/8/9 John Burt <=3Bquill@u.washington.edu
>=3B >=3B>=3B= >=3B >=3B >=3B <=3Bmailto:quill@u.washington.edu>=3B>=3B
>= =3B >=3B>=3B>=3B >=3B >=3B
>=3B >=3B>=3B>=3B >=3B &g= t=3B Martin=2C
>=3B >=3B>=3B>=3B >=3B >=3B
>=3B >=3B&= gt=3B>=3B >=3B >=3B I crashed an Easystar just like that during early= flight testing.
>=3B >=3B>=3B>=3B >=3B >=3B The AP (Tiny 2.= 11) went nonresponsive and dived into the ground=2C
>=3B >=3B>=3B&= gt=3B >=3B >=3B despite my having immediately flipped the switch to man= ual. It would
>=3B >=3B>=3B>=3B >=3B >=3B seem that the AP p= rocessor just locked up - truly a worst case
>=3B >=3B>=3B>=3B &= gt=3B >=3B scenario. The cause of the behavior was an undervoltage spike<= br>>=3B >=3B>=3B>=3B >=3B >=3B condition due to sourcing the fo= ur servos and RC RX off the 5V
>=3B >=3B>=3B>=3B >=3B >=3B s= upply. In case you haven't already=2C you should always power your
>= =3B >=3B>=3B>=3B >=3B >=3B hardware off a separate BEC (which beg= s the question of why the AP
>=3B >=3B>=3B>=3B >=3B >=3B has= a 5V source anyway).
>=3B >=3B>=3B>=3B >=3B >=3B
>=3B = >=3B>=3B>=3B >=3B >=3B AP generated noise on the ground wire was = other cause of bad AP
>=3B >=3B>=3B>=3B >=3B >=3B behavior t= hat I experienced. This causes glitching and reduced RC
>=3B >=3B>= =3B>=3B >=3B >=3B range. It has been covered ad nauseam in other post= s=2C but I'll
>=3B >=3B>=3B>=3B >=3B >=3B repeat it: it's es= pecially helpful to put an RF choke on the RC RX
>=3B >=3B>=3B>= =3B >=3B >=3B cable. Try to wrap the wire 4+ times around the choke.>=3B >=3B>=3B>=3B >=3B >=3B
>=3B >=3B>=3B>=3B >= =3B >=3B
>=3B >=3B>=3B>=3B >=3B >=3B Martin P wrote:
&g= t=3B >=3B>=3B>=3B >=3B >=3B
>=3B >=3B>=3B>=3B >=3B &= gt=3B Hello everyone!
>=3B >=3B>=3B>=3B >=3B >=3B Last weeke= nd I had a good AUTO1 flight with my Minimag. It
>=3B >=3B>=3B>= =3B >=3B >=3B reacted to pitch and roll commands=2C and I was able to c= ontrol
>=3B >=3B>=3B>=3B >=3B >=3B the throttle. I had an at= titude command in my flightplan which
>=3B >=3B>=3B>=3B >=3B &= gt=3B was never left (as I know now).
>=3B >=3B>=3B>=3B >=3B &= gt=3B Yesterday I tried again=2C without the attitude statement and
>= =3B >=3B>=3B>=3B >=3B >=3B without a holding point block.
>= =3B >=3B>=3B>=3B >=3B >=3B In AUTO1=2C it killed the throttle. Sw= itched to manual and landed
>=3B >=3B>=3B>=3B >=3B >=3B to c= hange battery because it was not fully charged.
>=3B >=3B>=3B>= =3B >=3B >=3B Took off again. Switched to AUTO1 and it immediately stab= ilized
>=3B >=3B>=3B>=3B >=3B >=3B the plane. Strangely=2C t= his time it did not react to the roll
>=3B >=3B>=3B>=3B >=3B &= gt=3B command. I flew around using the rudder. When I used the
>=3B &g= t=3B>=3B>=3B >=3B >=3B elevator stick=2C the autopilot controlled t= he throttle. Good=2C so
>=3B >=3B>=3B>=3B >=3B >=3B far.
= >=3B >=3B>=3B>=3B >=3B >=3B Suddenly the plane dived down verti= cally from an altitude of
>=3B >=3B>=3B>=3B >=3B >=3B roughl= y 40m. No reaction=2C just kept going vertical and slowly
>=3B >=3B&= gt=3B>=3B >=3B >=3B spinning around the longitudinal axis until it cr= ashed.
>=3B >=3B>=3B>=3B >=3B >=3B There was not as much dam= age done as I expected. These foamies
>=3B >=3B>=3B>=3B >=3B &= gt=3B are awesome. All RC components including Tiny and Xbee are OK.
>= =3B >=3B>=3B>=3B >=3B >=3B Except for the Lipo which is badly ben= t out of shape and will be
>=3B >=3B>=3B>=3B >=3B >=3B repla= ced for safety reasons.
>=3B >=3B>=3B>=3B >=3B >=3B Unfortun= ately I can't see much from the log as I had lost the
>=3B >=3B>= =3B>=3B >=3B >=3B link probably minutes before. I was in stage "HOME"= because I
>=3B >=3B>=3B>=3B >=3B >=3B had left the fly-too-= far circle before and came back manually.
>=3B >=3B>=3B>=3B >= =3B >=3B The switch was on manual so I probably tried to rescue. The Tiny=
>=3B >=3B>=3B>=3B >=3B >=3B was unplugged which can have ha= ppened at the crash or before.
>=3B >=3B>=3B>=3B >=3B >=3B O= ne aileron was ripped off and the horizontal IR was missing (I
>=3B &g= t=3B>=3B>=3B >=3B >=3B found it in the grass).
>=3B >=3B>= =3B>=3B >=3B >=3B So far=2C my report. The Minimag is already repaire= d and I'll keep
>=3B >=3B>=3B>=3B >=3B >=3B trying.
>= =3B >=3B>=3B>=3B >=3B >=3B Greetz=2C Martin
>=3B >=3B>= =3B>=3B >=3B >=3B
>=3B >=3B>=3B>=3B >=3B >=3B
>= =3B >=3B>=3B>=3B >=3B >=3B ______________________________________= _________
>=3B >=3B>=3B>=3B >=3B >=3B Paparazzi-devel mailin= g list
>=3B >=3B>=3B>=3B >=3B >=3B Paparazzi-devel@nongnu.or= g <=3Bmailto:Paparazzi-devel@nongnu.org>=3B
>=3B >=3B>=3B>= =3B >=3B >=3B http://lists.nongnu.org/mailman/listinfo/paparazzi-devel<= br>>=3B >=3B>=3B>=3B >=3B >=3B
>=3B >=3B>=3B>=3B >= =3B >=3B
>=3B >=3B>=3B>=3B >=3B >=3B
>=3B >=3B>= =3B>=3B >=3B >=3B
>=3B >=3B>=3B>=3B >=3B >=3B ________= _______________________________________
>=3B >=3B>=3B>=3B >=3B= >=3B Paparazzi-devel mailing list
>=3B >=3B>=3B>=3B >=3B &g= t=3B Paparazzi-devel@nongnu.org <=3Bmailto:Paparazzi-devel@nongnu.org>= =3B
>=3B >=3B>=3B>=3B >=3B >=3B http://lists.nongnu.org/mail= man/listinfo/paparazzi-devel
>=3B >=3B>=3B>=3B >=3B >=3B
= >=3B >=3B>=3B>=3B >=3B >=3B
>=3B >=3B>=3B>=3B >=3B= >=3B
>=3B >=3B>=3B>=3B >=3B >=3B
>=3B >=3B>=3B&g= t=3B >=3B >=3B --------------------------------------------------------= ----------------
>=3B >=3B>=3B>=3B >=3B >=3B
>=3B >= =3B>=3B>=3B >=3B >=3B _____________________________________________= __
>=3B >=3B>=3B>=3B >=3B >=3B Paparazzi-devel mailing list<= br>>=3B >=3B>=3B>=3B >=3B >=3B Paparazzi-devel@nongnu.org
&g= t=3B >=3B>=3B>=3B >=3B >=3B http://lists.nongnu.org/mailman/listi= nfo/paparazzi-devel
>=3B >=3B>=3B>=3B >=3B
>=3B >=3B>= =3B>=3B >=3B
>=3B >=3B>=3B>=3B >=3B ______________________= _________________________
>=3B >=3B>=3B>=3B >=3B Paparazzi-dev= el mailing list
>=3B >=3B>=3B>=3B >=3B Paparazzi-devel@nongnu.= org
>=3B >=3B>=3B>=3B >=3B http://lists.nongnu.org/mailman/lis= tinfo/paparazzi-devel
>=3B >=3B>=3B>=3B
>=3B >=3B>=3B&g= t=3B ________________________________
>=3B >=3B>=3B>=3B Stay in = the loop and chat with friends=2C right from your inbox! Learn how!
>= =3B >=3B>=3B>=3B _______________________________________________
&= gt=3B >=3B>=3B>=3B Paparazzi-devel mailing list
>=3B >=3B>= =3B>=3B Paparazzi-devel@nongnu.org
>=3B >=3B>=3B>=3B http://li= sts.nongnu.org/mailman/listinfo/paparazzi-devel
>=3B >=3B>=3B>= =3B
>=3B >=3B>=3B
>=3B >=3B>=3B
>=3B >=3B>=3B __= _____________________________________________
>=3B >=3B>=3B Papara= zzi-devel mailing list
>=3B >=3B>=3B Paparazzi-devel@nongnu.org>=3B >=3B>=3B http://lists.nongnu.org/mailman/listinfo/paparazzi-dev= el
>=3B >=3B>=3B
>=3B >=3B
>=3B >=3B
>=3B >= =3B _______________________________________________
>=3B >=3B Papara= zzi-devel mailing list
>=3B >=3B Paparazzi-devel@nongnu.org
>= =3B >=3B http://lists.nongnu.org/mailman/listinfo/paparazzi-devel
>= =3B >=3B
>=3B >=3B
>=3B
>=3B
>=3B _______________= ________________________________
>=3B Paparazzi-devel mailing list
= >=3B Paparazzi-devel@nongnu.org
>=3B http://lists.nongnu.org/mailman= /listinfo/paparazzi-devel


More storage. Better anti-spam and= antivirus protection. Hotmail makes it simple. = --_7f32844b-e9ab-4cb6-a7ab-373ecc379320_-- From MAILER-DAEMON Tue Aug 11 10:56:47 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MasmN-0001ca-9B for mharc-paparazzi-devel@gnu.org; Tue, 11 Aug 2009 10:56:47 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MasmM-0001aa-46 for paparazzi-devel@nongnu.org; Tue, 11 Aug 2009 10:56:46 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MasmH-0001TK-7A for paparazzi-devel@nongnu.org; Tue, 11 Aug 2009 10:56:45 -0400 Received: from [199.232.76.173] (port=42563 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MasmG-0001T3-UX for paparazzi-devel@nongnu.org; Tue, 11 Aug 2009 10:56:41 -0400 Received: from gwise-al5.server.gvsu.edu ([148.61.8.25]:47082 helo=gvsu.edu) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MasmG-00007g-BF for paparazzi-devel@nongnu.org; Tue, 11 Aug 2009 10:56:40 -0400 Received: from SMTPDOM-MTA by gvsu.edu with Novell_GroupWise; Tue, 11 Aug 2009 10:56:37 -0400 Message-Id: <4A814E58.BCAB.0027.0@gvsu.edu> X-Mailer: Novell GroupWise Internet Agent 7.0.2 HP Date: Tue, 11 Aug 2009 10:56:24 -0400 From: "John Koches" To: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="=__PartAD866B88.0__=" X-detected-operating-system: by monty-python.gnu.org: Novell Netware 6 SP3 Subject: [Paparazzi-devel] RE: Flying X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Aug 2009 14:56:46 -0000 --=__PartAD866B88.0__= Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Thanks Pascal. It helps to know that someone has tried it before...and it = works.=20 =20 I was concerned that the modems might have to be set up for mesh networking= or something special, but that doesn't seem to be the case. I would = guess that information from the plane is passed on to whoever is listening,= in this case the two gcs's. And there wouldn't be a problem until = someone at one end tried to send a flight plan change at the same time = someone for the other end was also sending an instruction. Hence, the = cell phones to make sure that doesn't happen. =20 I also noticed that your team always uses a patch antenna. At least that = is what I see in the pictures. I recently switched to a XBee Pro XSC = with a 900 MHZ base station antenna (2.1 dBi gain, 15 inch fiberglass). I = have had good results with my testing, but I probably haven't flow = farther that 5 kilometers. I wondered if you or anyone else has had = experience with this sort of set up? =20 Thanks again! =20 =20 --=__PartAD866B88.0__= Content-Type: text/html; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Content-Description: HTML
Thanks Pascal.  It helps to know that someone has tried it = before...and it works. 
 
I was concerned that the modems might have to be set up for mesh = networking or something special, but that doesn't seem to be the case. = ; I would guess that information from the plane is passed on to whoever is = listening, in this case the two gcs's.  And there wouldn't be a = problem until someone at one end tried to send a flight plan change at the = same time someone for the other end was also sending an instruction.  = Hence, the cell phones to make sure that doesn't happen.
 
I also noticed that your team always uses a patch antenna.  At = least that is what I see in the pictures.   I recently switched = to a XBee Pro XSC with a 900 MHZ base station antenna (2.1 dBi gain, 15 = inch fiberglass).  I have had good results with my testing, but  = I probably haven't flow farther that 5 kilometers.  I wondered if you = or anyone else has had experience with this sort of set up?
 
Thanks again!
 
 
--=__PartAD866B88.0__=-- From MAILER-DAEMON Tue Aug 11 13:06:01 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MaunR-0003GJ-BU for mharc-paparazzi-devel@gnu.org; Tue, 11 Aug 2009 13:06:01 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MaunP-0003Fd-O6 for paparazzi-devel@nongnu.org; Tue, 11 Aug 2009 13:05:59 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MaunL-0003DU-4S for paparazzi-devel@nongnu.org; Tue, 11 Aug 2009 13:05:59 -0400 Received: from [199.232.76.173] (port=38025 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MaunK-0003DN-S2 for paparazzi-devel@nongnu.org; Tue, 11 Aug 2009 13:05:54 -0400 Received: from mail-fx0-f207.google.com ([209.85.220.207]:36972) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MaunK-0003u2-Ax for paparazzi-devel@nongnu.org; Tue, 11 Aug 2009 13:05:54 -0400 Received: by fxm3 with SMTP id 3so899008fxm.8 for ; Tue, 11 Aug 2009 10:05:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=IIdL7rxuss2WS1LoglwfM8FywAQPEeHgUOko4JIRjvA=; b=MF3//YWXVeveRA6fwmNVXdqapnr/HVvY72eifgP3bUUtUJA2Kjsclp6srMK8Sm7v5a V/CntuSyBgn+8JKN3OJyJ4UsO0Sk9IThXL425UoxpDupl6AInukhvcQKUZrf5t8QdIlf VSTjXqmDKbuNQTk6ocwAq31c5Rn5ybR24hMiU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=A5/d6B+wGu/W8xsKlU+QvMnVfjYNL4mzzvH21gw+/WJTtDZtzC1Jxhz8ULIFG6t6m4 J75gb3xvdVbz9i2ywOmM89syT9Gpp/oYX0SsVNLgg4t0aqSqVop4spWUAwu6NzZYoaXY njrqwQrHnGxF1ezIsbpOZsJyH62s2JLeVrUjU= MIME-Version: 1.0 Received: by 10.204.63.208 with SMTP id c16mr7274015bki.131.1250010352980; Tue, 11 Aug 2009 10:05:52 -0700 (PDT) Date: Tue, 11 Aug 2009 17:05:52 +0000 Message-ID: <4d39daa50908111005g5836d3e7g2a2562133bc832a3@mail.gmail.com> From: Rui Costa To: paparazzi-devel@nongnu.org Content-Type: multipart/alternative; boundary=001636c5a2b30e13fe0470e0b717 X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) Subject: [Paparazzi-devel] Redundant System X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Aug 2009 17:06:00 -0000 --001636c5a2b30e13fe0470e0b717 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hello all, It would be very nice to implement a redundant system control for the paparazzi project. A system with for example two TWOGs. In case of a twog failure the other one assume the control. What do you think about it? It's difficult to design? Best Regards Rui Costa www.azoreanuav.com --001636c5a2b30e13fe0470e0b717 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hello all,
=A0
It would be very nice to implement a redundant system control for the = paparazzi project.
A system with for example two TWOGs.=A0In case of a twog failure the o= ther one assume the control.
=A0
What do you think about it? It's difficult to design?

Best Regards
Rui Costa
www.azoreanuav.com
--001636c5a2b30e13fe0470e0b717-- From MAILER-DAEMON Tue Aug 11 13:51:29 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MavVR-0002wA-Oh for mharc-paparazzi-devel@gnu.org; Tue, 11 Aug 2009 13:51:29 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MavVQ-0002va-FI for paparazzi-devel@nongnu.org; Tue, 11 Aug 2009 13:51:28 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MavVL-0002tX-IK for paparazzi-devel@nongnu.org; Tue, 11 Aug 2009 13:51:27 -0400 Received: from [199.232.76.173] (port=53082 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MavVL-0002tN-Dt for paparazzi-devel@nongnu.org; Tue, 11 Aug 2009 13:51:23 -0400 Received: from mail.gmx.net ([213.165.64.20]:41069) by monty-python.gnu.org with smtp (Exim 4.60) (envelope-from ) id 1MavVK-0001QU-MP for paparazzi-devel@nongnu.org; Tue, 11 Aug 2009 13:51:23 -0400 Received: (qmail 15063 invoked by uid 0); 11 Aug 2009 17:51:18 -0000 Received: from 77.116.91.77 by www037.gmx.net with HTTP; Tue, 11 Aug 2009 19:51:15 +0200 (CEST) Content-Type: text/plain; charset="us-ascii" Date: Tue, 11 Aug 2009 19:51:15 +0200 From: "Martin P" In-Reply-To: <4A7F3FB4.9010600@free.fr> Message-ID: <20090811175115.76460@gmx.net> MIME-Version: 1.0 References: <20090809074659.23250@gmx.net> <4A7EE64A.1030408@free.fr> <20090809190012.54660@gmx.net> <4A7F3FB4.9010600@free.fr> Subject: Re: [Paparazzi-devel] AGL and NavSetGroundReferenceHere() To: paparazzi-devel@nongnu.org X-Authenticated: #19891149 X-Flags: 0001 X-Mailer: WWW-Mail 6100 (Global Message Exchange) X-Priority: 3 X-Provags-ID: V01U2FsdGVkX19sxI42zj5szDyBGsEVGMjgThCfsZ+f2ip4RpVl8I JoaclFsLc/SG8i7KRmZtJ2u8ZEZuSfdOsfLA== Content-Transfer-Encoding: 7bit X-GMX-UID: p522fbdkbGInVLT1QmVnMAZvcmZ1Zlyo X-FuHaFi: 0.53 X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6, seldom 2.4 (older, 4) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Aug 2009 17:51:28 -0000 Thank you, I have put it into the WIKI under GCS. I hope this is the right place. I have tried it, now I am only 12m above ground. Greetz, Martin -------- Original-Nachricht -------- > Datum: Sun, 09 Aug 2009 23:29:24 +0200 > Von: Pascal Brisset > An: paparazzi-devel@nongnu.org > Betreff: Re: [Paparazzi-devel] AGL and NavSetGroundReferenceHere() > Hi, > > you need > > http://dds.cr.usgs.gov/srtm/version2_1/SRTM3/Eurasia/N47E016.hgt.zip > > in data/srtm/ > > --Pascal > > Martin P wrote: > > Hi, thanks for answering! > > > > What I call AGL: What is displayed in the GCS. > > SRTM: I have a file N47E011.hgt.bz2. > > I am at N47.82 and E16.88. Does this file cover my location? > > If yes, I would say it is available. > > If no, where do I get it from? I did a "Google Maps fill". Btw, the > terrain here is dead level. > > > > Greetings, Martin > > > > -------- Original-Nachricht -------- > > > >> Datum: Sun, 09 Aug 2009 17:07:54 +0200 > >> Von: Pascal Brisset > >> An: paparazzi-devel@nongnu.org > >> Betreff: Re: [Paparazzi-devel] AGL and NavSetGroundReferenceHere() > >> > > > > > >> Hi, > >> > >> what do you call AGL ? > >> - in the airborne code, NavSetGroundReferenceHere() sets ground_alt to > >> the current altitude (common_nav.c:84). > >> This variable is for example use in HOME mode (nav.c:370) or in the > >> Takeoff and Final block of the basic.xml flight plan. > >> - in the GCS, AGL is computed by subtracting the terrain altitude > (from > >> the SRTM model ... if the file is available in data/SRTM) from the > >> current altitude > >> > >> --Pascal > >> > >> Martin P wrote: > >> > >>> I use a flight plan with goround_alt=0 (derived from basic.xml). > >>> After calling NavSetGroundReferenceHere(), I would expect that the AGL > >>> > >> is 0. > >> > >>> Instead, it is the altitude above sea level. The GPS mode is 3D and > the > >>> > >> AGL varies within 3 or 4 meters. > >> > >>> Is this the way it should be? Should I set the ground_alt to the > actual > >>> > >> altitude? > >> > >>> _______________________________________________ > >>> Paparazzi-devel mailing list > >>> Paparazzi-devel@nongnu.org > >>> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > >>> > >>> > >> > >> _______________________________________________ > >> Paparazzi-devel mailing list > >> Paparazzi-devel@nongnu.org > >> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > >> > > > > > > _______________________________________________ > > Paparazzi-devel mailing list > > Paparazzi-devel@nongnu.org > > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > > > > > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel From MAILER-DAEMON Tue Aug 11 14:22:26 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MavzO-0004KH-40 for mharc-paparazzi-devel@gnu.org; Tue, 11 Aug 2009 14:22:26 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MavzM-0004Jz-3s for paparazzi-devel@nongnu.org; Tue, 11 Aug 2009 14:22:24 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MavzH-0004Jc-43 for paparazzi-devel@nongnu.org; Tue, 11 Aug 2009 14:22:23 -0400 Received: from [199.232.76.173] (port=54815 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MavzH-0004JZ-0T for paparazzi-devel@nongnu.org; Tue, 11 Aug 2009 14:22:19 -0400 Received: from mail-gx0-f220.google.com ([209.85.217.220]:60281) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MavzH-0007Qa-0d for paparazzi-devel@nongnu.org; Tue, 11 Aug 2009 14:22:19 -0400 Received: by gxk20 with SMTP id 20so12255111gxk.10 for ; Tue, 11 Aug 2009 11:22:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=Lz13nW9SWhcYc2rtvZJOARlR/E9VvoIrEUA8uQcHeHM=; b=nSoytxr6ZqEccc0AotFMm7P+ZA1F99MOLhU0nddZ+fdf3sJs+N2yTAyAvRPMG8mVKK JGqqjeF3WYyAJLbVwz9He+3Nhx+/wsPf2XZ6kfEcgz0ViWEakL2qcNgRzux0ZkRFGC32 o9uFGJA0QJQCSCZ9hRADpHlQbd9bvf1h2xW9U= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=Nsq2VzOqS+XjR5uk0opxxUMpEEwNCdYQzgnDD3ePLoHR4tO0WrkdakjMn5K1d71zci zqpIRdy7lCJbnQdHFlWOVZUmVGbz4At6DlbDRWTdmV1O06fe3MuojP0mcjrv6Cwygf9R lqaCfe35m/e099SX0vUo//vsB6w+dG25nVKqI= MIME-Version: 1.0 Received: by 10.151.142.12 with SMTP id u12mr3594225ybn.216.1250014937622; Tue, 11 Aug 2009 11:22:17 -0700 (PDT) In-Reply-To: <4d39daa50908111005g5836d3e7g2a2562133bc832a3@mail.gmail.com> References: <4d39daa50908111005g5836d3e7g2a2562133bc832a3@mail.gmail.com> Date: Tue, 11 Aug 2009 11:22:17 -0700 Message-ID: <727fedc40908111122v29953d40o32b64594198f86a0@mail.gmail.com> Subject: Re: [Paparazzi-devel] Redundant System From: antoine drouin To: paparazzi-devel@nongnu.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Aug 2009 18:22:24 -0000 Hello World If you're going to make a redundant system, you need at least 3 systems in order to be able to decide if one failed. You'll also need a way to switch actuators and other peripherals to the "good" instance of the autopilot. Regards Antoine On Tue, Aug 11, 2009 at 10:05 AM, Rui Costa wrote: > Hello all, > > It would be very nice to implement a redundant system control for the > paparazzi project. > A system with for example two TWOGs.=A0In case of a twog failure the othe= r one > assume the control. > > What do you think about it? It's difficult to design? > > Best Regards > Rui Costa > www.azoreanuav.com > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > > From MAILER-DAEMON Tue Aug 11 17:58:23 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MazMN-0006rg-83 for mharc-paparazzi-devel@gnu.org; Tue, 11 Aug 2009 17:58:23 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MazML-0006rX-0L for paparazzi-devel@nongnu.org; Tue, 11 Aug 2009 17:58:21 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MazMF-0006rL-MK for paparazzi-devel@nongnu.org; Tue, 11 Aug 2009 17:58:19 -0400 Received: from [199.232.76.173] (port=46717 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MazMF-0006rI-FR for paparazzi-devel@nongnu.org; Tue, 11 Aug 2009 17:58:15 -0400 Received: from mail-05.name-services.com ([69.64.155.197]:2525) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MazMF-0001s3-1q for paparazzi-devel@nongnu.org; Tue, 11 Aug 2009 17:58:15 -0400 Received: from [192.168.5.164] ([98.97.220.134]) by mail-05.name-services.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 11 Aug 2009 14:57:49 -0700 References: <4d39daa50908111005g5836d3e7g2a2562133bc832a3@mail.gmail.com> <727fedc40908111122v29953d40o32b64594198f86a0@mail.gmail.com> Message-Id: <9EDF03C6-600A-4610-B929-3DE49730F10A@me.com> From: David To: "paparazzi-devel@nongnu.org" In-Reply-To: <727fedc40908111122v29953d40o32b64594198f86a0@mail.gmail.com> Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit X-Mailer: iPhone Mail (7A400) Mime-Version: 1.0 (iPhone Mail 7A400) Subject: Re: [Paparazzi-devel] Redundant System Date: Tue, 11 Aug 2009 14:57:15 -0700 Cc: "paparazzi-devel@nongnu.org" X-OriginalArrivalTime: 11 Aug 2009 21:57:49.0432 (UTC) FILETIME=[C4699780:01CA1ACE] X-Sender: sales@ppzuav.com X-detected-operating-system: by monty-python.gnu.org: Windows XP/2000 (RFC1323+, w, tstamp+) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Aug 2009 21:58:21 -0000 Hello, I work daily with HA products used in business transactions (Oracle, Tibco). they get by with shared storage and state/heartbeat files etc...with two as a minimum. If both autopilots had a process that both could access the same shared file it's possible to reliably determine if the other is "alive"...the failover one could take over should the primary go down. So most apps I am familiar with require two and a shared file minimum so I am pretty sure it can be done with two. - David Conger On Aug 11, 2009, at 11:22 AM, antoine drouin wrote: > Hello World > > If you're going to make a redundant system, you need at least 3 > systems in order to be able to decide if one failed. > You'll also need a way to switch actuators and other peripherals to > the "good" instance of the autopilot. > > Regards > > Antoine > > On Tue, Aug 11, 2009 at 10:05 AM, Rui Costa > wrote: >> Hello all, >> >> It would be very nice to implement a redundant system control for the >> paparazzi project. >> A system with for example two TWOGs. In case of a twog failure the >> other one >> assume the control. >> >> What do you think about it? It's difficult to design? >> >> Best Regards >> Rui Costa >> www.azoreanuav.com >> >> _______________________________________________ >> Paparazzi-devel mailing list >> Paparazzi-devel@nongnu.org >> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel >> >> > > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel From MAILER-DAEMON Tue Aug 11 18:10:34 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MazYA-00044J-AV for mharc-paparazzi-devel@gnu.org; Tue, 11 Aug 2009 18:10:34 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MazY9-00043b-LD for paparazzi-devel@nongnu.org; Tue, 11 Aug 2009 18:10:33 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MazY5-000421-3f for paparazzi-devel@nongnu.org; Tue, 11 Aug 2009 18:10:33 -0400 Received: from [199.232.76.173] (port=51504 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MazY5-00041y-0t for paparazzi-devel@nongnu.org; Tue, 11 Aug 2009 18:10:29 -0400 Received: from mail-fx0-f207.google.com ([209.85.220.207]:60983) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MazY4-0004vl-C6 for paparazzi-devel@nongnu.org; Tue, 11 Aug 2009 18:10:28 -0400 Received: by fxm3 with SMTP id 3so1139681fxm.8 for ; Tue, 11 Aug 2009 15:10:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=UVaVpa6WW3/RUAHOGA++FitEiiXCXIywHhlmanOfAXc=; b=Yb8KD6HeGgk/nyneXagmB9sReWBnVahBreZvw29BPlQX852btAE0TbonPn8rlIHmnT tqzWZGnvFEpjdDWUv4j/168r8rlshxvg/7mi023QC8M+zt0rMgsGHDjLgKT6xBpUG960 0t28dIPkU0ogvJTkFt4w5sLdBtnmmlSFeljpM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=wIrJlv2wQFU3r441MwTZ0qIbLJRIn4cLpb5yEkxCISbKTugFuwn6u+7tssGEGlXdYg kkyjjTsW2VyctNMUWGB4ZVQud7jCWkwHFXd8Re2Tp7IyG7JtFFw3NuiwbapfXtvUh6tr jee+aG48VzHEm8lakShOb+jDY4apq1J4F8l68= MIME-Version: 1.0 Received: by 10.204.70.75 with SMTP id c11mr7428493bkj.128.1250028625320; Tue, 11 Aug 2009 15:10:25 -0700 (PDT) In-Reply-To: <9EDF03C6-600A-4610-B929-3DE49730F10A@me.com> References: <4d39daa50908111005g5836d3e7g2a2562133bc832a3@mail.gmail.com> <727fedc40908111122v29953d40o32b64594198f86a0@mail.gmail.com> <9EDF03C6-600A-4610-B929-3DE49730F10A@me.com> Date: Tue, 11 Aug 2009 22:10:25 +0000 Message-ID: <4d39daa50908111510v433119b3lf7b4a0413e31@mail.gmail.com> Subject: Re: [Paparazzi-devel] Redundant System From: Rui Costa To: paparazzi-devel@nongnu.org Content-Type: multipart/alternative; boundary=001636c5a90b2bdd710470e4f8f6 X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Aug 2009 22:10:33 -0000 --001636c5a90b2bdd710470e4f8f6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hello, Thanks for your replies. I was wondering, to simplify this, if we can make a second system to detect if the TWOG have a problem and make it reset. It's possible? Best regards Rui Costa On Tue, Aug 11, 2009 at 9:57 PM, David wrote: > Hello, > > I work daily with HA products used in business transactions (Oracle, > Tibco). they get by with shared storage and state/heartbeat files etc...with > two as a minimum. > > If both autopilots had a process that both could access the same shared > file it's possible to reliably determine if the other is "alive"...the > failover one could take over should the primary go down. > > So most apps I am familiar with require two and a shared file minimum so I > am pretty sure it can be done with two. > > - David Conger > > > On Aug 11, 2009, at 11:22 AM, antoine drouin wrote: > > Hello World >> >> If you're going to make a redundant system, you need at least 3 >> systems in order to be able to decide if one failed. >> You'll also need a way to switch actuators and other peripherals to >> the "good" instance of the autopilot. >> >> Regards >> >> Antoine >> >> On Tue, Aug 11, 2009 at 10:05 AM, Rui Costa wrote: >> >>> Hello all, >>> >>> It would be very nice to implement a redundant system control for the >>> paparazzi project. >>> A system with for example two TWOGs. In case of a twog failure the other >>> one >>> assume the control. >>> >>> What do you think about it? It's difficult to design? >>> >>> Best Regards >>> Rui Costa >>> www.azoreanuav.com >>> >>> _______________________________________________ >>> Paparazzi-devel mailing list >>> Paparazzi-devel@nongnu.org >>> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel >>> >>> >>> >> >> _______________________________________________ >> Paparazzi-devel mailing list >> Paparazzi-devel@nongnu.org >> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel >> > > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > -- Rui Costa www.azoreanuav.com --001636c5a90b2bdd710470e4f8f6 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hello,
=A0
Thanks for your replies. I was wondering, to simplify this, if we can = make a second system to detect if the TWOG have a problem and make it reset= . It's possible?
=A0
=A0
=A0
=A0
Best regards
Rui Costa


=A0
On Tue, Aug 11, 2009 at 9:57 PM, David <bmw330i@me.com> wrote:
Hello,

I work daily with = HA products used in business transactions (Oracle, Tibco). they get by with= shared storage and state/heartbeat files etc...with two as a minimum.

If both autopilots had a process that both could access the same shared= file it's possible to reliably determine if the other is "alive&q= uot;...the failover one could take over should the primary go down.

So most apps I am familiar with require two and a shared file minimum s= o I am pretty sure it can be done with two.

= - David Conger
=20


On Aug 11, 2009, at 11:22 AM, antoine drouin <= poinix@gmail.com&= gt; wrote:

Hello World

If you're= going to make a redundant system, you need at least 3
systems in order = to be able to decide if one failed.
You'll also need a way to switch actuators and other peripherals to
= the "good" instance of the autopilot.

Regards

Antoi= ne

On Tue, Aug 11, 2009 at 10:05 AM, Rui Costa<azoreanuav@gmail.com> wrote:=
Hello all,

It would be ve= ry nice to implement a redundant system control for the
paparazzi projec= t.
A system with for example two TWOGs. In case of a twog failure the other on= e
assume the control.

What do you think about it? It's diffic= ult to design?

Best Regards
Rui Costa
www.azoreanuav.com

_______________________________________________
Paparazzi-devel mail= ing list
Paparazzi-devel@nongnu.org
http://lists.nongnu.org/mail= man/listinfo/paparazzi-devel




______________________________________________= _
Paparazzi-devel mailing list
Paparazzi-devel@nongnu.org
htt= p://lists.nongnu.org/mailman/listinfo/paparazzi-devel


_______________________________________________
Pap= arazzi-devel mailing list
Paparazzi-devel@nongnu.org
http://list= s.nongnu.org/mailman/listinfo/paparazzi-devel



--
Rui Costa
ww= w.azoreanuav.com
--001636c5a90b2bdd710470e4f8f6-- From MAILER-DAEMON Tue Aug 11 18:23:49 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Mazkz-00084w-8L for mharc-paparazzi-devel@gnu.org; Tue, 11 Aug 2009 18:23:49 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mazkw-00084W-Lj for paparazzi-devel@nongnu.org; Tue, 11 Aug 2009 18:23:46 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mazks-00083s-5D for paparazzi-devel@nongnu.org; Tue, 11 Aug 2009 18:23:46 -0400 Received: from [199.232.76.173] (port=37677 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mazkr-00083p-Vt for paparazzi-devel@nongnu.org; Tue, 11 Aug 2009 18:23:42 -0400 Received: from mail-bw0-f227.google.com ([209.85.218.227]:60330) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Mazkr-0008IN-KR for paparazzi-devel@nongnu.org; Tue, 11 Aug 2009 18:23:41 -0400 Received: by bwz27 with SMTP id 27so3339123bwz.34 for ; Tue, 11 Aug 2009 15:23:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:content-type :content-transfer-encoding; bh=2Ix4vCAr+xbNhYhm9cQmhaLkV2wIf0+gcktN1oX4Y1M=; b=I++7F8LxMikgdNSzYkHckpW8CxbqfRnuKZNKpaBtacZ++GrRTI+8/cK+pNzKdvsIPz qUqseTIqEdpnnYpSI+MO93Yj7oUabaaweHzKOXsXjpLByDjT+lwbpVsZoACuet0oFX2u X3O0CGEIuYGyJqLjxtk5vWH7xWXN1GMxMU6gw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; b=EciZJ/HBcl5p6HuWmmR0M9qy6qQUPMRqJwU+1I3UuCNk8sponItbpI/NGwZxj0LZsx +OaJo/SNRtfpGM6bPdBfpR1GDthvmsbc6Qbtks3w7kuVF/c1xK3JrEA0BCFvIudK7lHl 4X/lNVwDVY6JXfYIvqyLwJCkh+/nYubDQjmgA= Received: by 10.204.68.207 with SMTP id w15mr392887bki.49.1250029418768; Tue, 11 Aug 2009 15:23:38 -0700 (PDT) Received: from ?192.168.1.2? ([88.218.149.158]) by mx.google.com with ESMTPS id f31sm8829881fkf.8.2009.08.11.15.23.36 (version=SSLv3 cipher=RC4-MD5); Tue, 11 Aug 2009 15:23:37 -0700 (PDT) Message-ID: <4A81EF67.4060600@gmail.com> Date: Wed, 12 Aug 2009 01:23:35 +0300 From: chris User-Agent: Thunderbird 2.0.0.22 (X11/20090608) MIME-Version: 1.0 To: paparazzi-devel@nongnu.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) Subject: [Paparazzi-devel] flight plan block activation from the rc tx X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Aug 2009 22:23:47 -0000 Does anyone knows a way to activate a specific flight plan block from the rc transmitter? Chris From MAILER-DAEMON Tue Aug 11 18:46:05 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Mb06X-0001pn-0M for mharc-paparazzi-devel@gnu.org; Tue, 11 Aug 2009 18:46:05 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mb06U-0001p7-Sm for paparazzi-devel@nongnu.org; Tue, 11 Aug 2009 18:46:02 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mb06Q-0001ny-FV for paparazzi-devel@nongnu.org; Tue, 11 Aug 2009 18:46:02 -0400 Received: from [199.232.76.173] (port=53340 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mb06Q-0001nv-8G for paparazzi-devel@nongnu.org; Tue, 11 Aug 2009 18:45:58 -0400 Received: from wf-out-1314.google.com ([209.85.200.170]:44155) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Mb06P-0004y8-MF for paparazzi-devel@nongnu.org; Tue, 11 Aug 2009 18:45:57 -0400 Received: by wf-out-1314.google.com with SMTP id 26so1494654wfd.4 for ; Tue, 11 Aug 2009 15:45:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=4AqZVgG2UofmiDG9ze4J8iIG77PHM1GsdDTnoIihqZw=; b=iNGPoeTzXcc8AOMJj2k59EilvbRSzjFcsd//Cy0LjaLR7VZDUbvzlrN1ump7t8O7x1 Q2C4qc4CIdEr8rn5GMYjHwA6PZN/+ePvaLywYfz8wPj9WIhQ9ZWHIJ9Y1Ghb/gBJHZl0 JzASVJ7pINqJgRU/XrnSzb5cSZfYETEfHgC70= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=lvt5G4nijkbI9VbL3rWGhsjsho4YKP/Y26R66HKTnAyeS91Rm6auGf+mF76Jj10LYw wPT9mSg95DqiM0nthCWjPIozoRCHezPaP7QN69lo0D7kgcyWizBqbl3Ys4n7MkuQca5d 72x2KhTTZPMB7Jv+Q8OmZrddnSv1d+3r7F3SY= MIME-Version: 1.0 Received: by 10.142.13.21 with SMTP id 21mr396153wfm.29.1250030756710; Tue, 11 Aug 2009 15:45:56 -0700 (PDT) In-Reply-To: <9EDF03C6-600A-4610-B929-3DE49730F10A@me.com> References: <4d39daa50908111005g5836d3e7g2a2562133bc832a3@mail.gmail.com> <727fedc40908111122v29953d40o32b64594198f86a0@mail.gmail.com> <9EDF03C6-600A-4610-B929-3DE49730F10A@me.com> Date: Wed, 12 Aug 2009 08:45:56 +1000 Message-ID: <8a0861de0908111545t4997fb44wf01b6ac19439b19a@mail.gmail.com> Subject: Re: [Paparazzi-devel] Redundant System From: Chris Gough To: paparazzi-devel@nongnu.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Aug 2009 22:46:03 -0000 I've seen a HA cluster go down when some networking gear failed. Storage could also be single points of failure shared semaphore fail-over design. I used to look after some HA servers with a 'watchdog' gadget that was also a potential single point of failure. I'm hazy on the details, but I think I remember Samba (SMB file server) having an 'election' protocol where if the primary domain controller disappeared from the network the other samba servers would quickly decide which one should take over. Basically each samba server was also a watchdog for the whole cluster. With a zigbee mesh network, might there be a pure software solution to multiple paparazzi autopilot fail-over (assuming servos on rails)? Chris Gough On Wed, Aug 12, 2009 at 7:57 AM, David wrote: > Hello, > > I work daily with HA products used in business transactions (Oracle, Tibco). > they get by with shared storage and state/heartbeat files etc...with two as > a minimum. > > If both autopilots had a process that both could access the same shared file > it's possible to reliably determine if the other is "alive"...the failover > one could take over should the primary go down. > > So most apps I am familiar with require two and a shared file minimum so I > am pretty sure it can be done with two. > > - David Conger > > On Aug 11, 2009, at 11:22 AM, antoine drouin wrote: > >> Hello World >> >> If you're going to make a redundant system, you need at least 3 >> systems in order to be able to decide if one failed. >> You'll also need a way to switch actuators and other peripherals to >> the "good" instance of the autopilot. >> >> Regards >> >> Antoine >> >> On Tue, Aug 11, 2009 at 10:05 AM, Rui Costa wrote: >>> >>> Hello all, >>> >>> It would be very nice to implement a redundant system control for the >>> paparazzi project. >>> A system with for example two TWOGs. In case of a twog failure the other >>> one >>> assume the control. >>> >>> What do you think about it? It's difficult to design? >>> >>> Best Regards >>> Rui Costa >>> www.azoreanuav.com >>> >>> _______________________________________________ >>> Paparazzi-devel mailing list >>> Paparazzi-devel@nongnu.org >>> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel >>> >>> >> >> >> _______________________________________________ >> Paparazzi-devel mailing list >> Paparazzi-devel@nongnu.org >> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > From MAILER-DAEMON Tue Aug 11 20:30:34 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Mb1je-0002EP-Cw for mharc-paparazzi-devel@gnu.org; Tue, 11 Aug 2009 20:30:34 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mb1jd-0002EI-76 for paparazzi-devel@nongnu.org; Tue, 11 Aug 2009 20:30:33 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mb1jX-0002E0-LW for paparazzi-devel@nongnu.org; Tue, 11 Aug 2009 20:30:31 -0400 Received: from [199.232.76.173] (port=43297 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mb1jX-0002Dx-Dn for paparazzi-devel@nongnu.org; Tue, 11 Aug 2009 20:30:27 -0400 Received: from wf-out-1314.google.com ([209.85.200.168]:54550) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Mb1jV-0004t3-TL for paparazzi-devel@nongnu.org; Tue, 11 Aug 2009 20:30:27 -0400 Received: by wf-out-1314.google.com with SMTP id 26so1510807wfd.4 for ; Tue, 11 Aug 2009 17:30:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=ap+SaCifXmdAdNEdJhkTwT1vwwJTBBwuhnoFrcsc4Ew=; b=FIr+hYFTMpgqd4+i6BK99YTak0lLo78tYsv1TnCRqpBVOJF+i4RzQ3KxNmqrpbLYEj VRgE1nT1bHOwXfGMD8fWBSy8pvYa8cFiw3QN/jS220QcjhWv43ETmuMdvWTXYalgdXFW xUkd9nVZiDtxlcJXoO/h3Oc3oFcuLtklFkOgw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=jOYoqb4AnCf0hKZ9vtGRXgNc0z0wFtkZ4BDkpjBeax1IAzJFdW7l+bianpeO1Oa2QM J43pvbv1Ux3XJ5xCZWnFmx3eMVHw8M5jQo1o23gBF9sTAJDvLbQL9e/e66M7KN6wDdI/ MDhXRnPGNKqmUGRist7WChWs18br6h/Kx22Dc= MIME-Version: 1.0 Received: by 10.142.155.17 with SMTP id c17mr348773wfe.207.1250037022705; Tue, 11 Aug 2009 17:30:22 -0700 (PDT) In-Reply-To: References: <20090809081748.23240@gmx.net> <4A7F09D7.8030601@u.washington.edu> <4A8043E1.4050107@u.washington.edu> <689b39d80908102242j7ddc6514mb475ad0ac80a6664@mail.gmail.com> <8a0861de0908110035h7e6649bkd762256d017cef40@mail.gmail.com> Date: Wed, 12 Aug 2009 10:30:22 +1000 Message-ID: <8a0861de0908111730v729af88dq2a034d37028a94af@mail.gmail.com> Subject: Re: [Paparazzi-devel] crashed, 5V supply overloading issue From: Chris Gough To: paparazzi-devel@nongnu.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Aug 2009 00:30:33 -0000 On Wed, Aug 12, 2009 at 12:33 AM, Yves Touchette wrote: >> It occurs to me that simply removing the aerial from the "main" part >> would turn it into a PPM demultiplexer that I could use with a BEC, if >> I needed to drive a collection of non-tiny servos. Would that be a >> (this) lazy-man's implementation of what are suggesting Yves, or have >> I misunderstood? > > Personally, I doubt that the main part is just a demux as it has an antenna, > etc... I assumed the main part also contained a receiver (it has an aerial :) and some facility for chosing which signal to use (it's own receiver or the satelite?), maybe based on which was getting the strongest signal. I figured that by removing the aerial from the main part, everything but the demux would become redundant becuase the unit would chose the "satelite" signal (paparazzi in this case) every time. It's a hack, literally. >> Is modulated output available from the tiny, instead of PWM (yes, I am >> that ignorant)? > > The connector for the receiver as 5 pins two of which are meant to connect > to an external demux. If I remember correctly, tiny1.3 had a little bug > where those pins weren't routed properly, but as far as I know, they are OK > on tiny 2.11. Cool, I'll check that out. Thanks. Chris Gough > > -yvest > >> -- >> Chris >> >> * Like this one (I'm not seller) >> >> http://cgi.ebay.com.au/RC-Turborix-2-4Ghz-6-Channel-Digital-Radio-Receiver-Rx_W0QQitemZ110406182895QQcmdZViewItemQQptZAU_Toys_Hobbies_Radio_Controlled_Vehicles?hash=item19b4b8a7ef&_trksid=p4634.c0.m14.l1262 >> >> On Tue, Aug 11, 2009 at 3:42 PM, Michel GORRAZ >> wrote: >> > Hi, >> > >> > Don't forget that "Tiny" means autopilot for small aircraft equipped >> > with....small servos. >> > >> > @+ >> > Michel >> > >> > 2009/8/11 Adam Spence <4x4Ninja@gmail.com> >> >> >> >> Sounds very good, anyone want to knock one up? I was going to do the >> >> half >> >> way house and still use the signals from PPZ but it may be cleaner to >> >> have >> >> the demux on board like you've suggested. >> >> >> >> 2009/8/10 Yves Touchette >> >>> >> >>> I personnally think that the best solution is not to power the servos >> >>> from the AP, period. >> >>> >> >>> How about designing a PCB that would contain a servo demux (like a >> >>> 4017), >> >>> be powered by the ESC BEC and have pads for both .1" connectors >> >>> (regular >> >>> servos) and for pico blade connectors? >> >>> >> >>> Many of the newer good quality ESC have switching BEC's that are more >> >>> then capable of driving a reasonable server load. >> >>> >> >>> Running of the BEC will also prevent power related crashs. The BEC is >> >>> already in most planes. Those that don't have one (glow engins, etc) >> >>> could >> >>> use an external BEC. >> >>> >> >>> This should be pretty easy to build without having to reroute a >> >>> complete >> >>> AP. >> >>> >> >>> The two sets of connectors would alow users to choose which they >> >>> prefer >> >>> and install only those. >> >>> >> >>> Does this sound good? >> >>> >> >>> -yvest >> >>> >> >>> > Date: Mon, 10 Aug 2009 08:59:29 -0700 >> >>> > From: quill@u.washington.edu >> >>> > To: paparazzi-devel@nongnu.org >> >>> > Subject: Re: [Paparazzi-devel] crashed, 5V supply overloading issue >> >>> > >> >>> > Yes, I am referring to the PPM signal from the RC receiver to PPZ. >> >>> > >> >>> > It was pretty clear that the fault was due to an overloaded 5V >> >>> > supply. >> >>> > On the ground I was able to faithfully re-create the AP crash >> >>> > conditions >> >>> > simply by rapidly exercising all the servos. I also did fairly >> >>> > extensive >> >>> > testing to debug this problem, including measuring current drain >> >>> > with >> >>> > all servos operating, which is what clarified the issue. >> >>> > >> >>> > I have suggested in the past that PPZ be updated with a higher >> >>> > capacity >> >>> > 5V converter, and given what you wrote below, it might also be a >> >>> > good >> >>> > thing to source the 3.3v line off the battery, rather than the 5V >> >>> > supply. However, the "temporary" solution is to simply use a >> >>> > separate >> >>> > 5V >> >>> > supply for external devices like servos, modems, etc. >> >>> > >> >>> > Adam Spence wrote: >> >>> > > John, what are you referring to with the RC RX cable? Is this the >> >>> > > PPM >> >>> > > cable attaching the receiver to PPZ? >> >>> > > >> >>> > > There's been a couple of crashes like this discussed on IRC >> >>> > > recently. >> >>> > > I'm not sure if the fault was identified but the overloading of >> >>> > > the >> >>> > > 5v >> >>> > > PSU was suggested. This could easily happen when the servos are >> >>> > > driven >> >>> > > to the limit and stall due to the hardware set up. Where ever >> >>> > > possible >> >>> > > the currents drawn by the servos need to be measured when all >> >>> > > control >> >>> > > surfaces are at the limit. If there are any stall conditions the >> >>> > > setup >> >>> > > needs to be adjusted either physically on the air frame or by >> >>> > > reducing >> >>> > > the control throws in the config file. >> >>> > > >> >>> > > The 5V PSU is not only responsible for supplying the servo power >> >>> > > but >> >>> > > also the 3v3 regulators power! Therefore if the 5v line drops due >> >>> > > to >> >>> > > too >> >>> > > much current being drawn then it may take out the main CPU. For my >> >>> > > particular setup with an 868 modem, the CPU, GPS and Modem can >> >>> > > take >> >>> > > upto >> >>> > > 500mA of current. The limit of the 5V PSU is 2.25A so roughly >> >>> > > there >> >>> > > may >> >>> > > be something in the region of 1.75A left for all of the servos. >> >>> > > That >> >>> > > only needs a couple of servos to stall and you could be in >> >>> > > trouble. >> >>> > > >> >>> > > Due to the above, I will be removing the 5V connection to the >> >>> > > servos >> >>> > > and >> >>> > > providing another regulated 5v directly from the battery. This >> >>> > > will >> >>> > > have >> >>> > > a limit of maybe 5-10A which is complete over kill. >> >>> > > >> >>> > > I've just noticed the current-limiting switch on the hardware, >> >>> > > this >> >>> > > means the servos can only draw 1A and then the switch kicks in and >> >>> > > notifies the CPU using GPIO. Does anyone know what the firmware >> >>> > > does >> >>> > > in >> >>> > > this instance? That therefore means that there's even less current >> >>> > > available for the servos and anything else which you may have >> >>> > > connected >> >>> > > on the 5v rail... hmmm. I see this can trigger from 0.5A to 1.25A, >> >>> > > anyone ever tested this? I'm wondering now what would happen if >> >>> > > this >> >>> > > were to fire, the servos would be left in their current position >> >>> > > (or >> >>> > > driven back slightly from mechanical pressure). The AP might >> >>> > > (depending >> >>> > > on what the GPIO signal does) try and keep driving the servos at >> >>> > > their >> >>> > > current position which would mean that when the current limiter >> >>> > > recovers >> >>> > > it then goes straight to the limit again? >> >>> > > >> >>> > > Anyway I've rambled enough this morning! >> >>> > > >> >>> > > Adam >> >>> > > >> >>> > > 2009/8/9 John Burt > >>> > > > >> >>> > > >> >>> > > Martin, >> >>> > > >> >>> > > I crashed an Easystar just like that during early flight testing. >> >>> > > The AP (Tiny 2.11) went nonresponsive and dived into the ground, >> >>> > > despite my having immediately flipped the switch to manual. It >> >>> > > would >> >>> > > seem that the AP processor just locked up - truly a worst case >> >>> > > scenario. The cause of the behavior was an undervoltage spike >> >>> > > condition due to sourcing the four servos and RC RX off the 5V >> >>> > > supply. In case you haven't already, you should always power your >> >>> > > hardware off a separate BEC (which begs the question of why the AP >> >>> > > has a 5V source anyway). >> >>> > > >> >>> > > AP generated noise on the ground wire was other cause of bad AP >> >>> > > behavior that I experienced. This causes glitching and reduced RC >> >>> > > range. It has been covered ad nauseam in other posts, but I'll >> >>> > > repeat it: it's especially helpful to put an RF choke on the RC RX >> >>> > > cable. Try to wrap the wire 4+ times around the choke. >> >>> > > >> >>> > > >> >>> > > Martin P wrote: >> >>> > > >> >>> > > Hello everyone! >> >>> > > Last weekend I had a good AUTO1 flight with my Minimag. It >> >>> > > reacted to pitch and roll commands, and I was able to control >> >>> > > the throttle. I had an attitude command in my flightplan which >> >>> > > was never left (as I know now). >> >>> > > Yesterday I tried again, without the attitude statement and >> >>> > > without a holding point block. >> >>> > > In AUTO1, it killed the throttle. Switched to manual and landed >> >>> > > to change battery because it was not fully charged. >> >>> > > Took off again. Switched to AUTO1 and it immediately stabilized >> >>> > > the plane. Strangely, this time it did not react to the roll >> >>> > > command. I flew around using the rudder. When I used the >> >>> > > elevator stick, the autopilot controlled the throttle. Good, so >> >>> > > far. >> >>> > > Suddenly the plane dived down vertically from an altitude of >> >>> > > roughly 40m. No reaction, just kept going vertical and slowly >> >>> > > spinning around the longitudinal axis until it crashed. >> >>> > > There was not as much damage done as I expected. These foamies >> >>> > > are awesome. All RC components including Tiny and Xbee are OK. >> >>> > > Except for the Lipo which is badly bent out of shape and will be >> >>> > > replaced for safety reasons. >> >>> > > Unfortunately I can't see much from the log as I had lost the >> >>> > > link probably minutes before. I was in stage "HOME" because I >> >>> > > had left the fly-too-far circle before and came back manually. >> >>> > > The switch was on manual so I probably tried to rescue. The Tiny >> >>> > > was unplugged which can have happened at the crash or before. >> >>> > > One aileron was ripped off and the horizontal IR was missing (I >> >>> > > found it in the grass). >> >>> > > So far, my report. The Minimag is already repaired and I'll keep >> >>> > > trying. >> >>> > > Greetz, Martin >> >>> > > >> >>> > > >> >>> > > _______________________________________________ >> >>> > > Paparazzi-devel mailing list >> >>> > > Paparazzi-devel@nongnu.org >> >>> > > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel >> >>> > > >> >>> > > >> >>> > > >> >>> > > >> >>> > > _______________________________________________ >> >>> > > Paparazzi-devel mailing list >> >>> > > Paparazzi-devel@nongnu.org >> >>> > > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel >> >>> > > >> >>> > > >> >>> > > >> >>> > > >> >>> > > >> >>> > > ------------------------------------------------------------------------ >> >>> > > >> >>> > > _______________________________________________ >> >>> > > Paparazzi-devel mailing list >> >>> > > Paparazzi-devel@nongnu.org >> >>> > > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel >> >>> > >> >>> > >> >>> > _______________________________________________ >> >>> > Paparazzi-devel mailing list >> >>> > Paparazzi-devel@nongnu.org >> >>> > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel >> >>> >> >>> ________________________________ >> >>> Stay in the loop and chat with friends, right from your inbox! Learn >> >>> how! >> >>> _______________________________________________ >> >>> Paparazzi-devel mailing list >> >>> Paparazzi-devel@nongnu.org >> >>> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel >> >>> >> >> >> >> >> >> _______________________________________________ >> >> Paparazzi-devel mailing list >> >> Paparazzi-devel@nongnu.org >> >> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel >> >> >> > >> > >> > _______________________________________________ >> > Paparazzi-devel mailing list >> > Paparazzi-devel@nongnu.org >> > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel >> > >> > >> >> >> _______________________________________________ >> Paparazzi-devel mailing list >> Paparazzi-devel@nongnu.org >> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > > ________________________________ > More storage. Better anti-spam and antivirus protection. Hotmail makes it > simple. > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > > From MAILER-DAEMON Wed Aug 12 02:43:45 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Mb7Yn-0005gU-1P for mharc-paparazzi-devel@gnu.org; Wed, 12 Aug 2009 02:43:45 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mb7Yk-0005eU-IG for paparazzi-devel@nongnu.org; Wed, 12 Aug 2009 02:43:42 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mb7Yg-0005cF-EV for paparazzi-devel@nongnu.org; Wed, 12 Aug 2009 02:43:42 -0400 Received: from [199.232.76.173] (port=52583 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mb7Yg-0005c7-71 for paparazzi-devel@nongnu.org; Wed, 12 Aug 2009 02:43:38 -0400 Received: from forward9.yandex.ru ([77.88.61.48]:32786) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Mb7Yf-0003lu-Hv for paparazzi-devel@nongnu.org; Wed, 12 Aug 2009 02:43:38 -0400 Received: from webmail133.yandex.ru (webmail133.yandex.ru [213.180.223.236]) by forward9.yandex.ru (Yandex) with ESMTP id EF02146808C for ; Wed, 12 Aug 2009 10:43:33 +0400 (MSD) Received: from localhost (localhost [127.0.0.1]) by webmail133.yandex.ru (Yandex) with ESMTP id E81943544137 for ; Wed, 12 Aug 2009 10:43:33 +0400 (MSD) X-Yandex-Spam: 1 X-Yandex-Front: webmail133 X-Yandex-TimeMark: 1250059413 Received: from [82.137.173.16] ([82.137.173.16]) by mail.yandex.ru with HTTP; Wed, 12 Aug 2009 10:43:33 +0400 From: Andrew S To: paparazzi-devel@nongnu.org In-Reply-To: <4d39daa50908111510v433119b3lf7b4a0413e31@mail.gmail.com> References: <4d39daa50908111005g5836d3e7g2a2562133bc832a3@mail.gmail.com> <727fedc40908111122v29953d40o32b64594198f86a0@mail.gmail.com> <9EDF03C6-600A-4610-B929-3DE49730F10A@me.com> <4d39daa50908111510v433119b3lf7b4a0413e31@mail.gmail.com> Subject: Re: [Paparazzi-devel] Redundant System MIME-Version: 1.0 Message-Id: <374781250059413@webmail133.yandex.ru> Date: Wed, 12 Aug 2009 10:43:33 +0400 X-Mailer: Yamail [ http://yandex.ru ] 5.0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Aug 2009 06:43:42 -0000 Hello
I think microcontroller board has enough reliability. The prob= lem can appear first of all in GPS receiver. I you want=C2=A0 increase su= rvival rate, you should double the GPS first. IMHO :)
Andrew
12.08.09, 02:10, "Rui Costa" <azoreanuav@gmail.com>:
Hello,
=C2=A0
Thanks for your replies. I was wondering, to simplify this, if we c= an make a second system to detect if the TWOG have a problem and make it = reset. It's possible?
=C2=A0
=C2=A0
=C2=A0
=C2=A0
Best regards
Rui Costa


=C2=A0
On Tue, Aug 11, 2009 at 9:57 PM, David <bmw330i@me.com> wrote:

So most apps I am familiar with require two and a shared file minim= um so I am pretty sure it can be done with two.

- David Conger
=20


On Aug 11, 2009, at 11:22 AM, antoine drou= in <poinix@gmail.com> wrote:


Regards

Antoi= ne

On Tue, Aug 11, 2009 at 10:05 AM, Rui Costa<azoreanuav@gmail.com> wrote:
www.azoreanuav.com

_______________________________________________
Paparazzi-deve= l mailing list
Paparazzi-deve= l@nongnu.org
http://lists.nongnu.org/mailman/listinf= o/paparazzi-devel




____________________________________= ___________
Paparazzi-devel mailing list
Paparazzi-devel@nongnu.org
http://l= ists.nongnu.org/mailman/listinfo/paparazzi-devel


_______________________________________________<= br />Paparazzi-devel mailing list
Paparazzi-devel@nongnu.org
http://lists.nongnu.= org/mailman/listinfo/paparazzi-devel



--
Rui Costa
www.azoreanuav.com


--
=D0=AF=D0=BD=D0=B4=D0=B5=D0=BA=D1=81.=D0= =9F=D0=BE=D1=87=D1=82=D0=B0. =D0=9F=D0=BE=D0=B8=D1=89=D0=B8=D1=82=D0=B5 =D1= =81=D0=BF=D0=B0=D0=BC =D0=B3=D0=B4=D0=B5-=D0=BD=D0=B8=D0=B1=D1=83=D0=B4=D1= =8C =D0=B5=D1=89=D0=B5 http://mail.yandex.ru/nospam/sign From MAILER-DAEMON Wed Aug 12 03:35:25 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Mb8Mn-0005iA-0z for mharc-paparazzi-devel@gnu.org; Wed, 12 Aug 2009 03:35:25 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mb8Ml-0005hf-K5 for paparazzi-devel@nongnu.org; Wed, 12 Aug 2009 03:35:23 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mb8Mg-0005fr-E9 for paparazzi-devel@nongnu.org; Wed, 12 Aug 2009 03:35:23 -0400 Received: from [199.232.76.173] (port=57201 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mb8Mg-0005fn-BQ for paparazzi-devel@nongnu.org; Wed, 12 Aug 2009 03:35:18 -0400 Received: from mx20.gnu.org ([199.232.41.8]:62950) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Mb8Mf-0004LS-Mm for paparazzi-devel@nongnu.org; Wed, 12 Aug 2009 03:35:17 -0400 Received: from forward14.yandex.ru ([95.108.130.92]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Mb8Me-0005Fb-8b for paparazzi-devel@nongnu.org; Wed, 12 Aug 2009 03:35:16 -0400 Received: from webmail102.yandex.ru (webmail102.yandex.ru [95.108.130.6]) by forward14.yandex.ru (Yandex) with ESMTP id 43AF32681073 for ; Wed, 12 Aug 2009 11:35:11 +0400 (MSD) Received: from localhost (localhost.localdomain [127.0.0.1]) by webmail102.yandex.ru (Yandex) with ESMTP id 2D444300405 for ; Wed, 12 Aug 2009 11:35:11 +0400 (MSD) X-Yandex-Spam: 1 X-Yandex-Front: webmail102 X-Yandex-TimeMark: 1250062511 Received: from [82.137.173.16] ([82.137.173.16]) by mail.yandex.ru with HTTP; Wed, 12 Aug 2009 11:35:10 +0400 From: Andrew S To: paparazzi-devel@nongnu.org In-Reply-To: <374781250059413@webmail133.yandex.ru> References: <4d39daa50908111005g5836d3e7g2a2562133bc832a3@mail.gmail.com> <727fedc40908111122v29953d40o32b64594198f86a0@mail.gmail.com> <9EDF03C6-600A-4610-B929-3DE49730F10A@me.com> <4d39daa50908111510v433119b3lf7b4a0413e31@mail.gmail.com> <374781250059413@webmail133.yandex.ru> MIME-Version: 1.0 Message-Id: <233501250062510@webmail102.yandex.ru> Date: Wed, 12 Aug 2009 11:35:10 +0400 X-Mailer: Yamail [ http://yandex.ru ] 5.0 Content-Transfer-Encoding: 7bit Content-Type: text/html X-Detected-Operating-System: by mx20.gnu.org: Genre and OS details not recognized. X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6, seldom 2.4 (older, 4) Subject: [Paparazzi-devel] AUTO2 flying, noise and another transmitters X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Aug 2009 07:35:23 -0000 Hello All
Now I fly quite far (within 3 km) and am afraid the following - what if somebody turn on transmitter on the same channel? Is there any way to temporarily block RC receiver at all from GCS after takeoff and unblock it before landing? I think this have to default function....
Anderw
From MAILER-DAEMON Thu Aug 13 02:50:32 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MbU8u-0003Pp-CC for mharc-paparazzi-devel@gnu.org; Thu, 13 Aug 2009 02:50:32 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MbU8s-0003Pe-Aa for paparazzi-devel@nongnu.org; Thu, 13 Aug 2009 02:50:30 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MbU8m-0003LY-QR for paparazzi-devel@nongnu.org; Thu, 13 Aug 2009 02:50:29 -0400 Received: from [199.232.76.173] (port=57282 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MbU8m-0003LN-Nm for paparazzi-devel@nongnu.org; Thu, 13 Aug 2009 02:50:24 -0400 Received: from mx20.gnu.org ([199.232.41.8]:11109) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MbU8m-0000tK-9U for paparazzi-devel@nongnu.org; Thu, 13 Aug 2009 02:50:24 -0400 Received: from smtp6-g21.free.fr ([212.27.42.6]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MbU8k-0003RO-JW for paparazzi-devel@nongnu.org; Thu, 13 Aug 2009 02:50:23 -0400 Received: from smtp6-g21.free.fr (localhost [127.0.0.1]) by smtp6-g21.free.fr (Postfix) with ESMTP id 92C4DE08068 for ; Thu, 13 Aug 2009 08:50:17 +0200 (CEST) Received: from [192.168.0.10] (uni31-1-82-234-59-180.fbx.proxad.net [82.234.59.180]) by smtp6-g21.free.fr (Postfix) with ESMTP id A78DDE080D6 for ; Thu, 13 Aug 2009 08:50:15 +0200 (CEST) Message-ID: <4A83B7A1.8050903@free.fr> Date: Thu, 13 Aug 2009 08:50:09 +0200 From: Pascal Brisset User-Agent: Thunderbird 2.0.0.22 (X11/20090608) MIME-Version: 1.0 To: paparazzi-devel@nongnu.org Subject: Re: [Paparazzi-devel] flight plan block activation from the rc tx References: <4A81EF67.4060600@gmail.com> In-Reply-To: <4A81EF67.4060600@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Detected-Operating-System: by mx20.gnu.org: GNU/Linux 2.6 (newer, 3) X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6, seldom 2.4 (older, 4) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Aug 2009 06:50:30 -0000 Hi, you can do a test on a fbw_state->channels[] element in a global exception of your flight plan: where GAIN1 is one channel of your radio file. Values are from -MAX_PPRZ to +MAX_PPRZ Unfortunately, because of the stupid lexical standard of XML, the character ">" is not allowed. So you have to define a macro somewhere else: #define GetRCChannel(_x) fbw_state->channels[_x] --Pascal chris wrote: > Does anyone knows a way to activate a specific flight plan block from > the rc transmitter? > Chris > > > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel From MAILER-DAEMON Thu Aug 13 03:43:04 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MbUxk-0001OC-2t for mharc-paparazzi-devel@gnu.org; Thu, 13 Aug 2009 03:43:04 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MbUxi-0001Mm-QR for paparazzi-devel@nongnu.org; Thu, 13 Aug 2009 03:43:02 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MbUxh-0001Ll-Vt for paparazzi-devel@nongnu.org; Thu, 13 Aug 2009 03:43:02 -0400 Received: from [199.232.76.173] (port=41189 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MbUxh-0001Le-M9 for paparazzi-devel@nongnu.org; Thu, 13 Aug 2009 03:43:01 -0400 Received: from mx20.gnu.org ([199.232.41.8]:14646) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MbUxg-0007Ew-Vh for paparazzi-devel@nongnu.org; Thu, 13 Aug 2009 03:43:01 -0400 Received: from ey-out-1920.google.com ([74.125.78.150]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MbUxf-0006hH-9A for paparazzi-devel@nongnu.org; Thu, 13 Aug 2009 03:42:59 -0400 Received: by ey-out-1920.google.com with SMTP id 5so137872eyb.4 for ; Thu, 13 Aug 2009 00:42:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=3InkAeB5GYcCfqozJ31GDjrKZK+IB6vk3WkKOFcO2NA=; b=RDREuRpOdDLW+916zWvN9SaUAZWjTv4LElSnw5aXWc0MCXYkvZs2RWzgwagQBx9GK1 TcyyB+/VSpsZdKXHfO4ekPWosZ3kXWJAbMoiK59VBlh4Fus2s3cjYWDQqLEaDS0zw5ta X8xO33GZLc7nLEACUK7+V6Ry0WnFnKw9K3GCA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=m2lB7COGMj2+lTOF9RPiknjFtQ3Wsd6cqkn0vvXpf4qlgZCOQEuLnb610y1g7p2POJ Ul1rb27YgTXYlRm3FyBHsd+DIfD8f2vhz7aPArAyuf2QDVQp3wjOFn6c4KU9v6NGNZz2 rwQKcErbou/DMhv4FXajuUyOzvw414VXMWs1w= MIME-Version: 1.0 Received: by 10.210.143.20 with SMTP id q20mr1243604ebd.45.1250149377161; Thu, 13 Aug 2009 00:42:57 -0700 (PDT) Date: Thu, 13 Aug 2009 09:42:57 +0200 Message-ID: <86b1e7960908130042xc9d8ad1he0276a70f7d18b2d@mail.gmail.com> From: Christophe De Wagter To: paparazzi-devel Content-Type: multipart/alternative; boundary=000e0cd1ea188ab96c0471011575 X-Detected-Operating-System: by mx20.gnu.org: GNU/Linux 2.6 (newer, 2) X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6, seldom 2.4 (older, 4) Subject: [Paparazzi-devel] Re: Redundant System X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Aug 2009 07:43:03 -0000 --000e0cd1ea188ab96c0471011575 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi Rui, On larger rotorcraft we considered 2 autopilots for fail safe purposes. A third system (usually a micro controller that also drives the servos) monitored the health of both systems using a "heart beat monitor" (a wire with pulses that are made by the main control loop software) and serial ports (to receive data from both flight computers). In practise several problems arise: -Sensors had one-way communication and could be routed to both computers so that part was solved easily. -But using something as simple as a heart beat monitor solves some problems like power problems etc but does not detect things like corrupted RAM etc, missing/wrong sensor data, broken (analog) wires in the sensor parts etc... -The communication with the ground is 2-way. Only one can be connected at the time while both flight computers need to have the full set of control gains, and preferably flight plan etc... If your protocol has something like retransmission upon missing acknowledgement this causes problems ... -Adding an extra system with copper wires also increases EMC/EMI problems considerably, not even talking about the weight increase and endurance decease. About the safety we have following considerations after looking back on 5 years of work while building over 15 aircraft/quads/helicopters from 30 cm to 350cm and ?? (I have no idea) hours of flying. Failure cases: 1) attitude determination: the problems that arise most often are always linked to attitude determination. Usually the attitude quality decreases below the required threshold for good flight and things like precision landings become a problem the higher the gliding ratio of the aircraft, the worse errors in pitch become... a) thermopile attitude (like paparazzi) -low IR contrast, temperature offsets between 2 thermopiles, thermopiles asymmetrically looking at hot fuselages, rain, clouds (we have flown in clouds with themopiles WITH success, believe it or not but there is(can be) a slight temperature difference between the bottom of the cloud and the top: you need to calibrate the thermopiles very well though and a backup system [magnetic/airspeed] is nice to have)... b) kalman filter convergence problems 2) EMI/EMC: 35MHz RC trouble, GPS quality decrease, reduced communication ranges, ... 3) Servos: after a few hundred hours of autopilot driven flight, especially cheap brushed servos DO die. Replace servos every few years and buy good quality. 4) Battery problems: after several hundred cycles LiPo batteries DO die... having 2 batteries with a diode? Usually 1) requires manual take-over, usually 2) is left as is accepting the consequences. Nr 4 is usually detected just-in-time for a precautionary landing. Clearly the worst case for us is nr 3. I can imagine that several other things can go wrong, but most are linked to a bad aircraft: using the tiny "TINY" power supply for driving several large servos simply is way beyond the capabilities and the intentions of the board. Conclusion: I am not convinced that 2 parallel processors will highly increase the safety of our MAV. I think they are more likely to add new failure cases. I personally see more benefits is a redesign of the power system for MINI UAV (dual power supply for servo/processor, possibility to add dual battery with e.g. 1 NiCd[low internal resistance] to survive servo short circuits, dual actuators for elevator/ailerons) and maybe the addition of a few extra sensors like pitot tube that can help the thermopiles. At least that is what we are working on. Christophe ---------- Forwarded message ---------- > From: Rui Costa > To: paparazzi-devel@nongnu.org > Date: Tue, 11 Aug 2009 17:05:52 +0000 > Subject: [Paparazzi-devel] Redundant System > Hello all, > > It would be very nice to implement a redundant system control for the > paparazzi project. > A system with for example two TWOGs. In case of a twog failure the other > one assume the control. > > What do you think about it? It's difficult to design? > > Best Regards > Rui Costa > www.azoreanuav.com > --000e0cd1ea188ab96c0471011575 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi Rui,

On larger = rotorcraft we considered 2 autopilots for fail safe purposes. A third syste= m (usually a micro controller that also drives the servos) monitored the he= alth of both systems using a "heart beat monitor" (a wire with pu= lses that are made by the main control loop software) and serial ports (to = receive data from both flight computers). In practise several problems aris= e:

-Sensors had one-way communication and could be routed = to both computers so that part was solved easily.
-But using some= thing as simple as a heart beat monitor solves some problems like power pro= blems etc but does not detect things like corrupted RAM etc, missing/wrong = sensor data, broken (analog) wires in the sensor parts etc...
-The communication with the ground is 2-way. Only one can be connected= at the time while both flight computers need to have the full set of contr= ol gains, and preferably flight plan etc... If your protocol has something = like retransmission upon missing acknowledgement this causes problems ...
-Adding an extra system with copper wires also increases EMC/EMI probl= ems considerably, not even talking about the weight increase and endurance = decease.

About the safety we have following consid= erations after looking back on 5 years of work while building over 15 aircr= aft/quads/helicopters from 30 cm to 350cm and ?? (I have no idea) hours of = flying.

Failure cases:

1) attitude det= ermination: the problems that arise most often are always linked to attitud= e determination. Usually the attitude quality decreases below the required = threshold for good flight and things like precision landings become a probl= em
=A0=A0 =A0the higher the gliding ratio of the aircraft, the worse erro= rs in pitch become...
=A0=A0 =A0a) thermopile attitude (like papa= razzi) -low IR contrast, temperature offsets between 2 thermopiles, thermop= iles asymmetrically looking at hot fuselages, rain, clouds (we have flown i= n clouds with themopiles WITH success, believe it or not but there is(can b= e) a slight temperature difference between the bottom of the cloud and the = top: you need to calibrate the thermopiles very well though and a backup sy= stem [magnetic/airspeed] is nice to have)...=A0
=A0=A0 b) kalman filter convergence problems

= 2) EMI/EMC: 35MHz RC trouble, GPS quality decrease, reduced communication r= anges, ...

3) Servos: after a few hundred hours of= autopilot driven flight, especially cheap brushed servos DO die. Replace s= ervos every few years and buy good quality.

4) Battery problems: after several hundred cycles LiPo = batteries DO die... having 2 batteries with a diode?
=A0
Usually 1) requires manual take-over, usually 2) is left as is accepting = the consequences. Nr 4 is usually detected just-in-time for a precautionary= landing. Clearly the worst case for us is nr 3.=A0

I can imagine that several other things can go wrong, b= ut most are linked to a bad aircraft: using the tiny "TINY" power= supply for driving several large servos simply is way beyond the capabilit= ies and the intentions of the board.=A0

Conclusion:

I am not convinced= that 2 parallel processors will highly increase the safety of our MAV. I t= hink they are more likely to add new failure cases. I personally see more b= enefits is a redesign of the power system for MINI UAV (dual power supply f= or servo/processor, possibility to add dual battery with e.g. 1 NiCd[low in= ternal resistance] to survive servo short circuits, dual actuators for elev= ator/ailerons) and maybe the addition of a few extra sensors like pitot tub= e that can help the thermopiles. At least that is what we are working on.

Christophe

---------- Forwarded message ----------
From:=A0Rui Costa <azoreanuav@gmail.com= >
To:=A0papar= azzi-devel@nongnu.org
Date:=A0Tue, 11 Aug 2009 17:05:52 +0000
Sub= ject:=A0[Paparazzi-devel] Redundant System
Hello all,
=A0
It would be very nice to implement a redundant system control for the = paparazzi project.
A system with for example two TWOGs.=A0In case of a twog failure the o= ther one assume the control.
=A0
What do you think about it? It's difficult to design?

Best Regards
Rui Costa
www.azoreanuav.com

--000e0cd1ea188ab96c0471011575-- From MAILER-DAEMON Thu Aug 13 04:36:10 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MbVn8-0006Mq-5a for mharc-paparazzi-devel@gnu.org; Thu, 13 Aug 2009 04:36:10 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MbVn6-0006Ma-4d for paparazzi-devel@nongnu.org; Thu, 13 Aug 2009 04:36:08 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MbVn1-0006Lh-4n for paparazzi-devel@nongnu.org; Thu, 13 Aug 2009 04:36:07 -0400 Received: from [199.232.76.173] (port=59651 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MbVn0-0006Le-OK for paparazzi-devel@nongnu.org; Thu, 13 Aug 2009 04:36:02 -0400 Received: from mail-bw0-f220.google.com ([209.85.218.220]:47504) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MbVmz-0007he-N5 for paparazzi-devel@nongnu.org; Thu, 13 Aug 2009 04:36:02 -0400 Received: by bwz20 with SMTP id 20so694272bwz.9 for ; Thu, 13 Aug 2009 01:35:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=FDGgX8B2Cr9Lgt8+E3g6SfTkhcZV5Ysyj5opypb6sdE=; b=e3+hb9AdnnvTRx1F4dsFvctyGS17nxiGSlY1ETShM2JRSZFKRtzY3pAPY0HO9tirDG WIRY5fs8V4ZYw8KmfWV8WXiVPR9nGwRgTvl+Uyd5SxffchN8kH8+m6GPKg1ZmvZeDsv3 ds/QhxPQFkXm3RTUA0kvRmlOHiapDXcQuBch4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=o+cmqpd94ZGOLJNb0ttkdqhgp81qSS9jHgdSHdeD7aHkIhUAu9qEwOo+K5AHTkme/M JE8YY3SiPfIprUg+xIECX6lJDDJDhwKSmqn2enqg9IN5WSvohT3DUPo9jQH5sIJecK8V K7XaLh/ZqkXR28og0kfcQH0VrG1nhPSeSGapA= MIME-Version: 1.0 Received: by 10.204.117.16 with SMTP id o16mr526272bkq.100.1250152557079; Thu, 13 Aug 2009 01:35:57 -0700 (PDT) In-Reply-To: <86b1e7960908130042xc9d8ad1he0276a70f7d18b2d@mail.gmail.com> References: <86b1e7960908130042xc9d8ad1he0276a70f7d18b2d@mail.gmail.com> Date: Thu, 13 Aug 2009 08:35:57 +0000 Message-ID: <4d39daa50908130135h6fcb01b5tcc72c37ecca6cea9@mail.gmail.com> Subject: Re: [Paparazzi-devel] Re: Redundant System From: Rui Costa To: paparazzi-devel@nongnu.org Content-Type: multipart/alternative; boundary=0016e6d7e9af146ea0047101d3ca X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Aug 2009 08:36:08 -0000 --0016e6d7e9af146ea0047101d3ca Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Thanks for the replies. I will have that info in account and think about the sual servos and dual batteries system. Best regards Rui Costa On Thu, Aug 13, 2009 at 7:42 AM, Christophe De Wagter wrote: > Hi Rui, > > On larger rotorcraft we considered 2 autopilots for fail safe purposes. A > third system (usually a micro controller that also drives the servos) > monitored the health of both systems using a "heart beat monitor" (a wire > with pulses that are made by the main control loop software) and serial > ports (to receive data from both flight computers). In practise several > problems arise: > > -Sensors had one-way communication and could be routed to both computers so > that part was solved easily. > -But using something as simple as a heart beat monitor solves some problems > like power problems etc but does not detect things like corrupted RAM etc, > missing/wrong sensor data, broken (analog) wires in the sensor parts etc... > -The communication with the ground is 2-way. Only one can be connected at > the time while both flight computers need to have the full set of control > gains, and preferably flight plan etc... If your protocol has something like > retransmission upon missing acknowledgement this causes problems ... > -Adding an extra system with copper wires also increases EMC/EMI problems > considerably, not even talking about the weight increase and endurance > decease. > > About the safety we have following considerations after looking back on 5 > years of work while building over 15 aircraft/quads/helicopters from 30 cm > to 350cm and ?? (I have no idea) hours of flying. > > Failure cases: > > 1) attitude determination: the problems that arise most often are always > linked to attitude determination. Usually the attitude quality decreases > below the required threshold for good flight and things like precision > landings become a problem > the higher the gliding ratio of the aircraft, the worse errors in pitch > become... > a) thermopile attitude (like paparazzi) -low IR contrast, temperature > offsets between 2 thermopiles, thermopiles asymmetrically looking at hot > fuselages, rain, clouds (we have flown in clouds with themopiles WITH > success, believe it or not but there is(can be) a slight temperature > difference between the bottom of the cloud and the top: you need to > calibrate the thermopiles very well though and a backup system > [magnetic/airspeed] is nice to have)... > b) kalman filter convergence problems > > 2) EMI/EMC: 35MHz RC trouble, GPS quality decrease, reduced communication > ranges, ... > > 3) Servos: after a few hundred hours of autopilot driven flight, especially > cheap brushed servos DO die. Replace servos every few years and buy good > quality. > > 4) Battery problems: after several hundred cycles LiPo batteries DO die... > having 2 batteries with a diode? > > Usually 1) requires manual take-over, usually 2) is left as is accepting > the consequences. Nr 4 is usually detected just-in-time for a precautionary > landing. Clearly the worst case for us is nr 3. > > I can imagine that several other things can go wrong, but most are linked > to a bad aircraft: using the tiny "TINY" power supply for driving several > large servos simply is way beyond the capabilities and the intentions of the > board. > > Conclusion: > > I am not convinced that 2 parallel processors will highly increase the > safety of our MAV. I think they are more likely to add new failure cases. I > personally see more benefits is a redesign of the power system for MINI UAV > (dual power supply for servo/processor, possibility to add dual battery with > e.g. 1 NiCd[low internal resistance] to survive servo short circuits, dual > actuators for elevator/ailerons) and maybe the addition of a few extra > sensors like pitot tube that can help the thermopiles. At least that is what > we are working on. > > Christophe > > ---------- Forwarded message ---------- >> From: Rui Costa >> To: paparazzi-devel@nongnu.org >> Date: Tue, 11 Aug 2009 17:05:52 +0000 >> Subject: [Paparazzi-devel] Redundant System >> Hello all, >> >> It would be very nice to implement a redundant system control for the >> paparazzi project. >> A system with for example two TWOGs. In case of a twog failure the other >> one assume the control. >> >> What do you think about it? It's difficult to design? >> >> Best Regards >> Rui Costa >> www.azoreanuav.com >> > > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > > -- Rui Costa www.azoreanuav.com --0016e6d7e9af146ea0047101d3ca Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Thanks for the replies. I will have that info=A0in account and think a= bout the sual servos and dual batteries system.
=A0
=A0
=A0
Best regards
Rui Costa

On Thu, Aug 13, 2009 at 7:42 AM, Christophe De W= agter <dewagter@= gmail.com> wrote:
Hi Rui,

On larger rotorcraft we considered 2 autopilots for fail safe purposes= . A third system (usually a micro controller that also drives the servos) m= onitored the health of both systems using a "heart beat monitor" = (a wire with pulses that are made by the main control loop software) and se= rial ports (to receive data from both flight computers). In practise severa= l problems arise:

-Sensors had one-way communication and could be routed to both compute= rs so that part was solved easily.
-But using something as simple as a heart beat monitor solves some pro= blems like power problems etc but does not detect things like corrupted RAM= etc, missing/wrong sensor data, broken (analog) wires in the sensor parts = etc...
-The communication with the ground is 2-way. Only one can be connected= at the time while both flight computers need to have the full set of contr= ol gains, and preferably flight plan etc... If your protocol has something = like retransmission upon missing acknowledgement this causes problems ...
-Adding an extra system with copper wires also increases EMC/EMI probl= ems considerably, not even talking about the weight increase and endurance = decease.

About the safety we have following considerations after looking back o= n 5 years of work while building over 15 aircraft/quads/helicopters from 30= cm to 350cm and ?? (I have no idea) hours of flying.

Failure cases:

1) attitude determination: the problems that arise most often are alwa= ys linked to attitude determination. Usually the attitude quality decreases= below the required threshold for good flight and things like precision lan= dings become a problem
=A0=A0 =A0the higher the gliding ratio of the aircraft, the worse erro= rs in pitch become...
=A0=A0 =A0a) thermopile attitude (like paparazzi) -low IR contrast, te= mperature offsets between 2 thermopiles, thermopiles asymmetrically looking= at hot fuselages, rain, clouds (we have flown in clouds with themopiles WI= TH success, believe it or not but there is(can be) a slight temperature dif= ference between the bottom of the cloud and the top: you need to calibrate = the thermopiles very well though and a backup system [magnetic/airspeed] is= nice to have)...=A0
=A0=A0 b) kalman filter convergence problems

2) EMI/EMC: 35MHz RC trouble, GPS quality decrease, reduced communicat= ion ranges, ...

3) Servos: after a few hundred hours of autopilot driven flight, espec= ially cheap brushed servos DO die. Replace servos every few years and buy g= ood quality.

4) Battery problems: after several hundred cycles LiPo batteries DO di= e... having 2 batteries with a diode?
=A0
Usually 1) requires manual take-over, usually 2) is left as is accepti= ng the consequences. Nr 4 is usually detected just-in-time for a precaution= ary landing. Clearly the worst case for us is nr 3.=A0

I can imagine that several other things can go wrong, but most are lin= ked to a bad aircraft: using the tiny "TINY" power supply for dri= ving several large servos simply is way beyond the capabilities and the int= entions of the board.=A0

Conclusion:

I am not convinced that 2 parallel processors will highly increase the= safety of our MAV. I think they are more likely to add new failure cases. = I personally see more benefits is a redesign of the power system for MINI U= AV (dual power supply for servo/processor, possibility to add dual battery = with e.g. 1 NiCd[low internal resistance] to survive servo short circuits, = dual actuators for elevator/ailerons) and maybe the addition of a few extra= sensors like pitot tube that can help the thermopiles. At least that is wh= at we are working on.

Christophe

---------- Forwarded message ---= -------
From:=A0Rui Costa <azoreanuav@gmail.com>
To:=A0papar= azzi-devel@nongnu.org
Date:=A0Tue, 11 Aug 2009 17:05:52 +0000
Sub= ject:=A0[Paparazzi-devel] Redundant System
Hello all,
=A0
It would be very nice to implement a redundant system control for the = paparazzi project.
A system with for example two TWOGs.=A0In case of a twog failure the o= ther one assume the control.
=A0
What do you think about it? It's difficult to design?

Best Regards
Rui Costa
www.azoreanuav.com


_______________________________________________
Paparazzi-deve= l mailing list
Paparazzi-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/paparazzi-devel




--
Rui Costa
ww= w.azoreanuav.com
--0016e6d7e9af146ea0047101d3ca-- From MAILER-DAEMON Thu Aug 13 08:09:50 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MbZ7u-0006nA-G0 for mharc-paparazzi-devel@gnu.org; Thu, 13 Aug 2009 08:09:50 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MbZ7s-0006mT-Ha for paparazzi-devel@nongnu.org; Thu, 13 Aug 2009 08:09:48 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MbZ7n-0006kC-FI for paparazzi-devel@nongnu.org; Thu, 13 Aug 2009 08:09:48 -0400 Received: from [199.232.76.173] (port=49511 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MbZ7n-0006k8-9F for paparazzi-devel@nongnu.org; Thu, 13 Aug 2009 08:09:43 -0400 Received: from bay0-omc3-s16.bay0.hotmail.com ([65.54.246.216]:28754) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MbZ7m-0007dd-I7 for paparazzi-devel@nongnu.org; Thu, 13 Aug 2009 08:09:42 -0400 Received: from BAY119-W13 ([207.46.9.48]) by bay0-omc3-s16.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 13 Aug 2009 05:09:41 -0700 Message-ID: Content-Type: multipart/alternative; boundary="_93bc60e8-fb2a-4280-8ab9-acf79f193a12_" X-Originating-IP: [24.202.93.123] From: Yves Touchette To: Subject: RE: [Paparazzi-devel] Re: Redundant System Date: Thu, 13 Aug 2009 08:09:41 -0400 Importance: Normal In-Reply-To: <4d39daa50908130135h6fcb01b5tcc72c37ecca6cea9@mail.gmail.com> References: <86b1e7960908130042xc9d8ad1he0276a70f7d18b2d@mail.gmail.com> <4d39daa50908130135h6fcb01b5tcc72c37ecca6cea9@mail.gmail.com> MIME-Version: 1.0 X-OriginalArrivalTime: 13 Aug 2009 12:09:41.0503 (UTC) FILETIME=[EFFE70F0:01CA1C0E] X-detected-operating-system: by monty-python.gnu.org: Windows 2000 SP4, XP SP1+ X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Aug 2009 12:09:48 -0000 --_93bc60e8-fb2a-4280-8ab9-acf79f193a12_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Instead of looking of a redundant system=2C you could look for a system to = revert back to manual control in case the AP locks. Here's how I see it: Build a servo encoder/demux/external powerboard that looks at the PPM signa= l coming from the AP. It could be simply checking that the PPM signal is t= here or look for a particular pattern in a spare channel. The fail safe boa= rd could then feed the servos directly from the RC signal if the AP locks u= p. That same board could allow you to manually override the AP with a spare= channel on your transmitter as well. I haven't look at all the details but the failsafe demux from diydrone look= s like a good start! It's not AP redundancy=2C but at least you can regain control is you experi= ence problems with the AP in flight! -yvest Date: Thu=2C 13 Aug 2009 08:35:57 +0000 Subject: Re: [Paparazzi-devel] Re: Redundant System From: azoreanuav@gmail.com To: paparazzi-devel@nongnu.org Thanks for the replies. I will have that info in account and think about th= e sual servos and dual batteries system. =20 =20 =20 Best regards Rui Costa On Thu=2C Aug 13=2C 2009 at 7:42 AM=2C Christophe De Wagter wrote: Hi Rui=2C On larger rotorcraft we considered 2 autopilots for fail safe purposes. A t= hird system (usually a micro controller that also drives the servos) monito= red the health of both systems using a "heart beat monitor" (a wire with pu= lses that are made by the main control loop software) and serial ports (to = receive data from both flight computers). In practise several problems aris= e: -Sensors had one-way communication and could be routed to both computers so= that part was solved easily. -But using something as simple as a heart beat monitor solves some problems= like power problems etc but does not detect things like corrupted RAM etc= =2C missing/wrong sensor data=2C broken (analog) wires in the sensor parts = etc... -The communication with the ground is 2-way. Only one can be connected at t= he time while both flight computers need to have the full set of control ga= ins=2C and preferably flight plan etc... If your protocol has something lik= e retransmission upon missing acknowledgement this causes problems ... -Adding an extra system with copper wires also increases EMC/EMI problems c= onsiderably=2C not even talking about the weight increase and endurance dec= ease. About the safety we have following considerations after looking back on 5 y= ears of work while building over 15 aircraft/quads/helicopters from 30 cm t= o 350cm and ?? (I have no idea) hours of flying. Failure cases: 1) attitude determination: the problems that arise most often are always li= nked to attitude determination. Usually the attitude quality decreases belo= w the required threshold for good flight and things like precision landings= become a problem the higher the gliding ratio of the aircraft=2C the worse errors in pit= ch become... a) thermopile attitude (like paparazzi) -low IR contrast=2C temperature= offsets between 2 thermopiles=2C thermopiles asymmetrically looking at hot= fuselages=2C rain=2C clouds (we have flown in clouds with themopiles WITH = success=2C believe it or not but there is(can be) a slight temperature diff= erence between the bottom of the cloud and the top: you need to calibrate t= he thermopiles very well though and a backup system [magnetic/airspeed] is = nice to have)...=20 b) kalman filter convergence problems 2) EMI/EMC: 35MHz RC trouble=2C GPS quality decrease=2C reduced communicati= on ranges=2C ... 3) Servos: after a few hundred hours of autopilot driven flight=2C especial= ly cheap brushed servos DO die. Replace servos every few years and buy good= quality. 4) Battery problems: after several hundred cycles LiPo batteries DO die... = having 2 batteries with a diode? =20 Usually 1) requires manual take-over=2C usually 2) is left as is accepting = the consequences. Nr 4 is usually detected just-in-time for a precautionary= landing. Clearly the worst case for us is nr 3.=20 I can imagine that several other things can go wrong=2C but most are linked= to a bad aircraft: using the tiny "TINY" power supply for driving several = large servos simply is way beyond the capabilities and the intentions of th= e board.=20 Conclusion: I am not convinced that 2 parallel processors will highly increase the safe= ty of our MAV. I think they are more likely to add new failure cases. I per= sonally see more benefits is a redesign of the power system for MINI UAV (d= ual power supply for servo/processor=2C possibility to add dual battery wit= h e.g. 1 NiCd[low internal resistance] to survive servo short circuits=2C d= ual actuators for elevator/ailerons) and maybe the addition of a few extra = sensors like pitot tube that can help the thermopiles. At least that is wha= t we are working on. Christophe ---------- Forwarded message ---------- From: Rui Costa To: paparazzi-devel@nongnu.org Date: Tue=2C 11 Aug 2009 17:05:52 +0000 Subject: [Paparazzi-devel] Redundant System Hello all=2C =20 It would be very nice to implement a redundant system control for the papar= azzi project. A system with for example two TWOGs. In case of a twog failure the other on= e assume the control. =20 What do you think about it? It's difficult to design? Best Regards Rui Costa www.azoreanuav.com _______________________________________________ Paparazzi-devel mailing list Paparazzi-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/paparazzi-devel --=20 Rui Costa www.azoreanuav.com _________________________________________________________________ Stay in the loop and chat with friends=2C right from your inbox! http://go.microsoft.com/?linkid=3D9671354= --_93bc60e8-fb2a-4280-8ab9-acf79f193a12_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Instead of looking of a redundant system=2C you could look for a system to = revert back to manual control in case the AP locks.

Here's how I see= it:

Build a servo encoder/demux/external powerboard that looks at t= he PPM signal coming from the AP. =3B It could be simply checking that = the PPM signal is there or look for a particular pattern in a spare channel= . The fail safe board could then feed the servos directly from the RC signa= l if the AP locks up. That same board could allow you to manually override = the AP with a spare channel on your transmitter as well.

I haven't l= ook at all the details but the failsafe demux from diydrone looks like a go= od start!

It's not AP redundancy=2C but at least you can regain cont= rol is you experience problems with the AP in flight!

 =3B-yvest=


Date: Thu=2C 13 Aug 2009 08:35:57 +0000
= Subject: Re: [Paparazzi-devel] Re: Redundant System
From: azoreanuav@gma= il.com
To: paparazzi-devel@nongnu.org

Thanks for the replies= . I will have that info =3Bin account and think about the sual servos a= nd dual batteries system.
 =3B
 =3B
 =3B
Best regards
Rui Costa

On Thu=2C Aug 13=2C 2009 at 7:42 AM=2C Christ= ophe De Wagter <=3Bdewagter@gmail.com>=3B wrote:
Hi Rui=2C

On larger rotorcraft we considered 2 autopilots for fail safe purposes= . A third system (usually a micro controller that also drives the servos) m= onitored the health of both systems using a "heart beat monitor" (a wire wi= th pulses that are made by the main control loop software) and serial ports= (to receive data from both flight computers). In practise several problems= arise:

-Sensors had one-way communication and could be routed to both compute= rs so that part was solved easily.
-But using something as simple as a heart beat monitor solves some pro= blems like power problems etc but does not detect things like corrupted RAM= etc=2C missing/wrong sensor data=2C broken (analog) wires in the sensor pa= rts etc...
-The communication with the ground is 2-way. Only one can be connected= at the time while both flight computers need to have the full set of contr= ol gains=2C and preferably flight plan etc... If your protocol has somethin= g like retransmission upon missing acknowledgement this causes problems ...=
-Adding an extra system with copper wires also increases EMC/EMI probl= ems considerably=2C not even talking about the weight increase and enduranc= e decease.

About the safety we have following considerations after looking back o= n 5 years of work while building over 15 aircraft/quads/helicopters from 30= cm to 350cm and ?? (I have no idea) hours of flying.

Failure cases:

1) attitude determination: the problems that arise most often are alwa= ys linked to attitude determination. Usually the attitude quality decreases= below the required threshold for good flight and things like precision lan= dings become a problem
 =3B =3B  =3Bthe higher the gliding ratio of the aircraft= =2C the worse errors in pitch become...
 =3B =3B  =3Ba) thermopile attitude (like paparazzi) -low = IR contrast=2C temperature offsets between 2 thermopiles=2C thermopiles asy= mmetrically looking at hot fuselages=2C rain=2C clouds (we have flown in cl= ouds with themopiles WITH success=2C believe it or not but there is(can be)= a slight temperature difference between the bottom of the cloud and the to= p: you need to calibrate the thermopiles very well though and a backup syst= em [magnetic/airspeed] is nice to have)... =3B
 =3B =3B b) kalman filter convergence problems

2) EMI/EMC: 35MHz RC trouble=2C GPS quality decrease=2C reduced commun= ication ranges=2C ...

3) Servos: after a few hundred hours of autopilot driven flight=2C esp= ecially cheap brushed servos DO die. Replace servos every few years and buy= good quality.

4) Battery problems: after several hundred cycles LiPo batteries DO di= e... having 2 batteries with a diode?
 =3B
Usually 1) requires manual take-over=2C usually 2) is left as is accep= ting the consequences. Nr 4 is usually detected just-in-time for a precauti= onary landing. Clearly the worst case for us is nr 3. =3B

I can imagine that several other things can go wrong=2C but most are l= inked to a bad aircraft: using the tiny "TINY" power supply for driving sev= eral large servos simply is way beyond the capabilities and the intentions = of the board. =3B

Conclusion:

I am not convinced that 2 parallel processors will highly increase the= safety of our MAV. I think they are more likely to add new failure cases. = I personally see more benefits is a redesign of the power system for MINI U= AV (dual power supply for servo/processor=2C possibility to add dual batter= y with e.g. 1 NiCd[low internal resistance] to survive servo short circuits= =2C dual actuators for elevator/ailerons) and maybe the addition of a few e= xtra sensors like pitot tube that can help the thermopiles. At least that i= s what we are working on.

Christophe

---------- Forwarded message ----= ------
From: =3BRui Costa <=3Bazoreanuav@gmail.com>=3B
To: =3Bpaparazzi-devel@no= ngnu.org
Date: =3BTue=2C 11 Aug 2009 17:05:52 +0000
Subject:&= nbsp=3B[Paparazzi-devel] Redundant System
Hello all=2C
 =3B
It would be very nice to implement a redundant system control for the = paparazzi project.
A system with for example two TWOGs. =3BIn case of a twog failure = the other one assume the control.
 =3B
What do you think about it? It's difficult to design?

Best Regards
Rui Costa
www.azoreanuav.com


________= _______________________________________
Paparazzi-devel mailing list
Paparazzi-devel@nongnu.org
h= ttp://lists.nongnu.org/mailman/listinfo/paparazzi-devel




--
Rui Costa
ww= w.azoreanuav.com


Stay in the loop and chat with friends= =2C right from your inbox! Learn how! = --_93bc60e8-fb2a-4280-8ab9-acf79f193a12_-- From MAILER-DAEMON Thu Aug 13 13:28:38 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Mbe6Q-0001AA-1m for mharc-paparazzi-devel@gnu.org; Thu, 13 Aug 2009 13:28:38 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mbe6M-000198-Uy for paparazzi-devel@nongnu.org; Thu, 13 Aug 2009 13:28:34 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mbe6I-00016z-Ao for paparazzi-devel@nongnu.org; Thu, 13 Aug 2009 13:28:34 -0400 Received: from [199.232.76.173] (port=58712 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mbe6I-00016s-5w for paparazzi-devel@nongnu.org; Thu, 13 Aug 2009 13:28:30 -0400 Received: from mail-bw0-f220.google.com ([209.85.218.220]:59165) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Mbe6H-0005X1-QY for paparazzi-devel@nongnu.org; Thu, 13 Aug 2009 13:28:29 -0400 Received: by bwz20 with SMTP id 20so1106232bwz.9 for ; Thu, 13 Aug 2009 10:28:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:content-type :content-transfer-encoding; bh=UQjJCqMqf+WJ8uc+WRWuml3PY6c4q2996oSSXfKh7cA=; b=NVIQ6zYqDtqwVGgTxt2Dk0TDg+ZfdP22snxc/algjltoPeH18FflGpejUMHdHljJn+ VGwXsKTpcvNUyJeNPLYo/lQQ9S/2wvv6Zf/SlCZG7XlggLA43z7ptFr67Mdz83p/ZhoT pBPAdBs/oybRJbQ1oy4rz2EliMHo1tKJkZ1Oc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; b=QHgf2trS9upfgndpB2dyKoMSwtRuIo0TBHWnKkILQWOGrX67ENX7yqJGdpyamZci5e 4fWfdKjxhd+ae5O+o5fy9NqypNrAyHFQpFTmJxmPy7lL4F8WU3KlvSuOYogiyCF/qMdO IZfF9JemmlwfPiWDxw0UTdJSbPmXGcbAtH5bg= Received: by 10.204.99.212 with SMTP id v20mr749352bkn.169.1250184508327; Thu, 13 Aug 2009 10:28:28 -0700 (PDT) Received: from ?192.168.1.2? ([88.218.149.158]) by mx.google.com with ESMTPS id 18sm745402fkq.29.2009.08.13.10.28.25 (version=SSLv3 cipher=RC4-MD5); Thu, 13 Aug 2009 10:28:26 -0700 (PDT) Message-ID: <4A844D38.6000706@gmail.com> Date: Thu, 13 Aug 2009 20:28:24 +0300 From: chris User-Agent: Thunderbird 2.0.0.22 (X11/20090608) MIME-Version: 1.0 To: paparazzi-devel@nongnu.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) Subject: [Paparazzi-devel] reply to "flight plan block activation from the rc tx (Pascal Brisset)" X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Aug 2009 17:28:35 -0000 Thank you Pascal That is exactly what i want. I have a flight plan that the only thing it does is a photo run and it includes a Standby block. I tested successfully an auto take off without the use of the transmitter (i throw away the aircraft after running in order to achieve 11 km/h and enable the motor) so i am searching for a way to eliminate the ground station for this simple flight plan. I know that there are hidden danger in it but i test in remote areas and controled areas. Chris From MAILER-DAEMON Thu Aug 13 13:33:02 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MbeAg-0002s6-Du for mharc-paparazzi-devel@gnu.org; Thu, 13 Aug 2009 13:33:02 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MbeAd-0002qx-W9 for paparazzi-devel@nongnu.org; Thu, 13 Aug 2009 13:33:00 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MbeAX-0002qh-NF for paparazzi-devel@nongnu.org; Thu, 13 Aug 2009 13:32:58 -0400 Received: from [199.232.76.173] (port=40088 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MbeAX-0002qe-Iw for paparazzi-devel@nongnu.org; Thu, 13 Aug 2009 13:32:53 -0400 Received: from imss-1.enac.fr ([195.220.159.36]:42252) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MbeAX-0006OX-53 for paparazzi-devel@nongnu.org; Thu, 13 Aug 2009 13:32:53 -0400 Received: from mauve.recherche.enac.fr (imss-1.imss.interne.enac [127.0.0.1]) by imss-1.enac.fr (Postfix) with ESMTP id EE88518B3A2 for ; Thu, 13 Aug 2009 19:32:50 +0200 (CEST) Received: from [10.31.1.82] (sepia.recherche.enac.fr [10.31.1.82])by mauve.recherche.enac.fr (Postfix) with ESMTP id CCE082FA822for ; Thu, 13 Aug 2009 19:32:50 +0200 (CEST) Message-ID: <4A844E42.6090605@free.fr> Date: Thu, 13 Aug 2009 19:32:50 +0200 From: Pascal Brisset User-Agent: Mozilla-Thunderbird 2.0.0.22 (X11/20090706) MIME-Version: 1.0 To: paparazzi-devel@nongnu.org Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-imss-version: 2.5 X-imss-result: Passed X-imss-scores: Clean:82.96589 C:22 M:1 S:5 R:5 X-imss-settings: Baseline:1 C:1 M:1 S:1 R:1 (0.0000 0.0000) X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.4-2.6 Subject: [Paparazzi-devel] New path instruction X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Aug 2009 17:33:00 -0000 Hi, answer to an old request (I cannot find it): A instruction has been added to the flight plan language to fly over a list of waypoints. It is simply preprocessed into a sequence of instructions. Example in basic.xml: The list separaror is the regular expression "[ \t,]+" (at least one space, tab or comma). Extra standard attributes are allowed. The translation produces here and it is what you will see in the GCS. --Pascal PS: No, it is not possible to dynamically define the waypoints list from the GCS during the flight :-) From MAILER-DAEMON Thu Aug 13 13:41:00 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MbeIO-0003Lg-AC for mharc-paparazzi-devel@gnu.org; Thu, 13 Aug 2009 13:41:00 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MbeIM-0003IM-Hj for paparazzi-devel@nongnu.org; Thu, 13 Aug 2009 13:40:58 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MbeIH-000390-S2 for paparazzi-devel@nongnu.org; Thu, 13 Aug 2009 13:40:58 -0400 Received: from [199.232.76.173] (port=51519 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MbeIH-00038r-K4 for paparazzi-devel@nongnu.org; Thu, 13 Aug 2009 13:40:53 -0400 Received: from mail-bw0-f220.google.com ([209.85.218.220]:43384) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MbeIH-0007Yx-79 for paparazzi-devel@nongnu.org; Thu, 13 Aug 2009 13:40:53 -0400 Received: by bwz20 with SMTP id 20so1116782bwz.9 for ; Thu, 13 Aug 2009 10:40:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=1+/xvTOFk71B7c4LAR+puxR06ydXIPEoiT8fCjc2IpM=; b=ku69X0jT3AN6JLQjqxgPI14O5gdcvgTwFHaaHxCsz2ajmdpM6yNNUsyR1OyM8l72TC LdG5dYyzTy6XX2rwFNYOrF/LQXweh/1EV49cCrTbIeuN4dJKWN2XF46QWfpoj4WtQrme UjJYbzG+xByJ4ZBrFaUmKYiu0PXNbny+wQNqg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=VJGjkMgQtM72zhcoagKtNe7ut77aru6ngSADr3c66990mjvagGxmyVRsRMqn/Y2EnZ yatWoi+YmDfhzxFsmZhIoOQjlGxKRuV8u6WM3rTfYszmlCG8HYv2p2znPiaxKjKibx1p ttKxnxQQxl6MgKj/+vOCaSJquJ16Qw7CzA+Ts= MIME-Version: 1.0 Received: by 10.204.143.153 with SMTP id v25mr752793bku.157.1250185251487; Thu, 13 Aug 2009 10:40:51 -0700 (PDT) Date: Thu, 13 Aug 2009 17:40:51 +0000 Message-ID: <4d39daa50908131040h118b1bdei96b0dde5d99e1009@mail.gmail.com> From: Rui Costa To: paparazzi-devel@nongnu.org Content-Type: multipart/alternative; boundary=0015175d031cd1812b0471096f39 X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) Subject: [Paparazzi-devel] CGS Programing Language X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Aug 2009 17:40:58 -0000 --0015175d031cd1812b0471096f39 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hello all, What's the programming language of the CGS? How can I modify and compile the CGS? Best regards Rui Costa --0015175d031cd1812b0471096f39 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hello all,
=A0
=A0
What's the programming language of the CGS? How can I modify and c= ompile the CGS?
=A0

=A0

Best regards=A0
Rui Costa --0015175d031cd1812b0471096f39-- From MAILER-DAEMON Fri Aug 14 04:28:58 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Mbs9i-0000FD-EZ for mharc-paparazzi-devel@gnu.org; Fri, 14 Aug 2009 04:28:58 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mbs9g-0000Dk-7E for paparazzi-devel@nongnu.org; Fri, 14 Aug 2009 04:28:56 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mbs9b-00009b-AZ for paparazzi-devel@nongnu.org; Fri, 14 Aug 2009 04:28:55 -0400 Received: from [199.232.76.173] (port=58637 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mbs9b-00009C-5M for paparazzi-devel@nongnu.org; Fri, 14 Aug 2009 04:28:51 -0400 Received: from blu0-omc2-s21.blu0.hotmail.com ([65.55.111.96]:40928) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Mbs9a-00034D-Kb for paparazzi-devel@nongnu.org; Fri, 14 Aug 2009 04:28:50 -0400 Received: from BLU149-W50 ([65.55.111.71]) by blu0-omc2-s21.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 14 Aug 2009 01:28:49 -0700 Message-ID: Content-Type: multipart/alternative; boundary="_840c2505-1b80-4a91-9618-472c77e71ac4_" X-Originating-IP: [134.96.163.226] From: =?big5?B?s6IgZmx5aW5nIHBpZw==?= To: Date: Fri, 14 Aug 2009 08:28:49 +0000 Importance: Normal MIME-Version: 1.0 X-OriginalArrivalTime: 14 Aug 2009 08:28:49.0231 (UTC) FILETIME=[3F6FF5F0:01CA1CB9] X-detected-operating-system: by monty-python.gnu.org: Windows 2000 SP4, XP SP1+ Subject: [Paparazzi-devel] Fly with IMU for fix wing aircraft and helicopter? X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Aug 2009 08:28:56 -0000 --_840c2505-1b80-4a91-9618-472c77e71ac4_ Content-Type: text/plain; charset="big5" Content-Transfer-Encoding: 8bit Hi there I am in the process of buliding up the Booz IMU, and i was wonering, does the current code allow to intergrate IMU to Tiny for fix wing and helicopter? We will try to fly with our helipoter with IR sesnor today (it has inbuid simple stabilisation hardware from the toy company), so we are just looking with using Tiny to control the PWM signal for coaxial heclicopter. I am not sure it wil work, but we will try, i will let you guys know. Regards Chen _________________________________________________________________ ¥Î³¡¸¨®æ¤À¨É·Ó¤ù¡B¼v­µ¡B½ì¨ý¤p¤u¨ã©M³Ì·R²M³æ¡AºÉ±¡¨q¥X§A¦Û¤v ¡X Windows Live Spaces http://home.spaces.live.com/?showUnauth=1&lc=1028 --_840c2505-1b80-4a91-9618-472c77e71ac4_ Content-Type: text/html; charset="big5" Content-Transfer-Encoding: 8bit Hi there
 
  I am in the process of buliding up the Booz IMU, and i was wonering, does the current code allow to intergrate IMU to Tiny for fix wing and helicopter?
 
  We will try to fly with our helipoter with IR sesnor today (it has inbuid simple stabilisation hardware from the toy company), so we are just looking with using Tiny to control the PWM signal for coaxial heclicopter.  I am not sure it wil work, but we will try, i will let you guys know.
 
 
 
 
Regards
 
                                                                                 Chen
 
 


¥Î³¡¸¨®æ¤À¨É·Ó¤ù¡B¼v­µ¡B½ì¨ý¤p¤u¨ã©M³Ì·R²M³æ¡AºÉ±¡¨q¥X§A¦Û¤v ¡X Windows Live Spaces --_840c2505-1b80-4a91-9618-472c77e71ac4_-- From MAILER-DAEMON Fri Aug 14 04:38:41 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MbsJ7-00051X-Hr for mharc-paparazzi-devel@gnu.org; Fri, 14 Aug 2009 04:38:41 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MbsJ6-00050g-9S for paparazzi-devel@nongnu.org; Fri, 14 Aug 2009 04:38:40 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MbsJ1-0004yJ-IJ for paparazzi-devel@nongnu.org; Fri, 14 Aug 2009 04:38:39 -0400 Received: from [199.232.76.173] (port=49718 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MbsJ1-0004yE-CJ for paparazzi-devel@nongnu.org; Fri, 14 Aug 2009 04:38:35 -0400 Received: from mail-bw0-f220.google.com ([209.85.218.220]:53625) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MbsJ0-0005hr-Tt for paparazzi-devel@nongnu.org; Fri, 14 Aug 2009 04:38:35 -0400 Received: by bwz20 with SMTP id 20so1645097bwz.9 for ; Fri, 14 Aug 2009 01:38:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=BJjcluPgJh6tnXknH2qf8cqzdX92huIaiDRrzYFGg44=; b=Z129k//e/Zra2xzSgCDJ0RBc9J9SQqIV3/4VxLemSG9aZLROzeuVwuRuoSAMRGeNDm Y2ntja0WHbpwi9BczI0Ydw0nZ5cRoyuS24lef4L2sPrp0VPWc8SsKfejJ/T0I+sJ6dNM gBAnWyUrIV8weCnPX7QSZZ/p+A8uYpG9guAo0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=XYjv0F3J73+6Iz1NtGaWAqqWPvZgatXKywnKSDgkiuSgFuq8NyeJCvPCItZ8hrO4gZ 7TNKI0Do4ww176shUH67qLnFCbKQCfzq+oTFpTaWWbKRnSUv3rchFTCIrSU6FTKcPOag CXUelNJKJbD8ZHLs6Q2BadqhHDiGBAIwrSIj4= MIME-Version: 1.0 Received: by 10.204.156.24 with SMTP id u24mr1035887bkw.172.1250239112303; Fri, 14 Aug 2009 01:38:32 -0700 (PDT) Date: Fri, 14 Aug 2009 08:38:32 +0000 Message-ID: <4d39daa50908140138of35bbfeq607ef90c3fca785e@mail.gmail.com> From: Rui Costa To: paparazzi-devel@nongnu.org Content-Type: multipart/alternative; boundary=0015175dda9a2c56eb047115fa03 X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) Subject: [Paparazzi-devel] New Autopilot - Tiny v3 X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Aug 2009 08:38:40 -0000 --0015175dda9a2c56eb047115fa03 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hello all, Let's talk about possible new features for the new Tiny. I think it's time to make a new autopilot based on experience acumulated from the others Tiny boards. We can discuss this new features by here, wiki, IRC channel or f=F3rum. *http://paparazzi.enac.fr/wiki/Tiny_v3* I will need some help with some new components and the implementation of th= e software part. Best regards Rui Costa --0015175dda9a2c56eb047115fa03 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hello all,
=A0
=A0
Let's talk about possible new features for the new Tiny. I think i= t's time to make a new autopilot based on experience acumulated from th= e others Tiny boards.
We can discuss this new features by here, wiki, IRC channel or f=F3rum= .
=A0

I will need some help with some new components and t= he implementation of the software part.
=A0

Best regards
Rui Costa
--0015175dda9a2c56eb047115fa03-- From MAILER-DAEMON Fri Aug 14 05:35:27 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MbtC3-0003by-CJ for mharc-paparazzi-devel@gnu.org; Fri, 14 Aug 2009 05:35:27 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MbtC1-0003bd-2c for paparazzi-devel@nongnu.org; Fri, 14 Aug 2009 05:35:25 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MbtBv-0003ZR-Nk for paparazzi-devel@nongnu.org; Fri, 14 Aug 2009 05:35:23 -0400 Received: from [199.232.76.173] (port=49153 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MbtBv-0003Z0-Dd for paparazzi-devel@nongnu.org; Fri, 14 Aug 2009 05:35:19 -0400 Received: from imss-1.enac.fr ([195.220.159.36]:46412) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MbtBu-0003hW-EY for paparazzi-devel@nongnu.org; Fri, 14 Aug 2009 05:35:19 -0400 Received: from mauve.recherche.enac.fr (imss-1.imss.interne.enac [127.0.0.1]) by imss-1.enac.fr (Postfix) with ESMTP id B45FC18B3A2 for ; Fri, 14 Aug 2009 11:35:04 +0200 (CEST) Received: from [10.31.1.82] (sepia.recherche.enac.fr [10.31.1.82])by mauve.recherche.enac.fr (Postfix) with ESMTP id 9DB732FA822for ; Fri, 14 Aug 2009 11:35:04 +0200 (CEST) Message-ID: <4A852FC8.3040801@free.fr> Date: Fri, 14 Aug 2009 11:35:04 +0200 From: Pascal Brisset User-Agent: Mozilla-Thunderbird 2.0.0.22 (X11/20090706) MIME-Version: 1.0 To: paparazzi-devel@nongnu.org Subject: Re: [Paparazzi-devel] Airframe debug problem,stop at ap.elf References: <2f88794c0908100114o177af4f2va83c7445d378b398@mail.gmail.com> In-Reply-To: <2f88794c0908100114o177af4f2va83c7445d378b398@mail.gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed X-imss-version: 2.5 X-imss-result: Passed X-imss-scores: Clean:36.96994 C:22 M:1 S:5 R:5 X-imss-settings: Baseline:1 C:1 M:1 S:1 R:1 (0.0000 0.0000) Content-Transfer-Encoding: quoted-printable X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.4-2.6 X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Aug 2009 09:35:25 -0000 You have to keep this line (not related to gyro): ap.srcs +=3D nav_survey_rectangle.c nav_line.c --Pascal =E7=AB=A5=E7=A3=8A wrote: > Hi, > I had problem when trying to remove lines of Gyro from the airframe=20 > file.Debuging always stopped at LD=20 > /home/mnw/paparazzi3/var/mnwAC/ap/ap.elf,I couldn't figure out why.I'v=20 > put the airframe file here http://pastebin.com/m6cb0a486. > Help me out. > > Thanks all. > -----------------------------------------------------------------------= - > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > =20 From MAILER-DAEMON Fri Aug 14 05:50:43 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MbtQp-0007yd-H2 for mharc-paparazzi-devel@gnu.org; Fri, 14 Aug 2009 05:50:43 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MbtQn-0007xf-Ln for paparazzi-devel@nongnu.org; Fri, 14 Aug 2009 05:50:41 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MbtQi-0007v4-K7 for paparazzi-devel@nongnu.org; Fri, 14 Aug 2009 05:50:40 -0400 Received: from [199.232.76.173] (port=42613 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MbtQi-0007un-2I for paparazzi-devel@nongnu.org; Fri, 14 Aug 2009 05:50:36 -0400 Received: from imss-1.enac.fr ([195.220.159.36]:46549) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MbtQh-0007JR-Bi for paparazzi-devel@nongnu.org; Fri, 14 Aug 2009 05:50:35 -0400 Received: from mauve.recherche.enac.fr (imss-1.imss.interne.enac [127.0.0.1]) by imss-1.enac.fr (Postfix) with ESMTP id 5860118B3A7 for ; Fri, 14 Aug 2009 11:50:24 +0200 (CEST) Received: from [10.31.1.82] (sepia.recherche.enac.fr [10.31.1.82])by mauve.recherche.enac.fr (Postfix) with ESMTP id 42F482FA822for ; Fri, 14 Aug 2009 11:50:24 +0200 (CEST) Message-ID: <4A853360.3050205@free.fr> Date: Fri, 14 Aug 2009 11:50:24 +0200 From: Pascal Brisset User-Agent: Mozilla-Thunderbird 2.0.0.22 (X11/20090706) MIME-Version: 1.0 To: paparazzi-devel@nongnu.org Subject: Re: [Paparazzi-devel] questions on flight plan References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-imss-version: 2.5 X-imss-result: Passed X-imss-scores: Clean:99.90000 C:21 M:2 S:5 R:5 X-imss-settings: Baseline:1 C:1 M:1 S:1 R:1 (0.0000 0.0000) X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.4-2.6 X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Aug 2009 09:50:42 -0000 Hi Steve, there is an "old" feature using procedures: http://paparazzi.enac.fr/wiki/Flight_Plans#Procedures But it will require a reflash of your autopilot. The NavSetGroundReferenceHere() function translates the waypoints around the current GPS location. It's easy to write a similar function to do a rotation (for example around HOME). You only need a way to specify the heading you want. You could use a specific waypoint. The procedure would be: - NavSetGroundReferenceHere() - set a waypoint (XX) - NavRotateAroundHOME(WP_XX) hth --Pascal Steve Ross wrote: > Most of the flight plans can be used in any places by using the > relative coordinates of the waypoints to the HOME location, one thing > I don't understand is how people aligned the fields in the flight > plans to the new flying fields. Suppose I have the "versatile.html" as > my flight plan in mind and arrive at a new field and choose one > location as my HOME waypoint and find a runway to take off. Do I have > to bring a *compass* to know the orientation of the field in the > flight plan to the current field I arrive at? Otherwise, it's likely > that my field will be a *rotation* of the field in the flight plan > around the waypoint HOME. I may think that the other waypoints in the > flight plan are located within the actual field but in actuality some > of the waypoints are out of the boundary of the actual field due to > the wrong assumption of the *rotation* on the field in the flight > plan. If I discover that my assumption is wrong after I arrive at that > field, is there any quick and easy way to rotate and create a new > flight plan at the field? (One command that rotate all of the > waypoints in the flight plan to allign with actual field around the > HOME?). > > Thanks a lot. > ------------------------------------------------------------------------ > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > From MAILER-DAEMON Fri Aug 14 05:51:56 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MbtRz-0000Ay-Qd for mharc-paparazzi-devel@gnu.org; Fri, 14 Aug 2009 05:51:55 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MbtRy-00009k-5r for paparazzi-devel@nongnu.org; Fri, 14 Aug 2009 05:51:54 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MbtRt-000063-Hg for paparazzi-devel@nongnu.org; Fri, 14 Aug 2009 05:51:53 -0400 Received: from [199.232.76.173] (port=42672 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MbtRt-00005n-30 for paparazzi-devel@nongnu.org; Fri, 14 Aug 2009 05:51:49 -0400 Received: from imss-1.enac.fr ([195.220.159.36]:46556) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MbtRs-0007dW-1q for paparazzi-devel@nongnu.org; Fri, 14 Aug 2009 05:51:48 -0400 Received: from mauve.recherche.enac.fr (imss-1.imss.interne.enac [127.0.0.1]) by imss-1.enac.fr (Postfix) with ESMTP id 1084618B3A7 for ; Fri, 14 Aug 2009 11:51:47 +0200 (CEST) Received: from [10.31.1.82] (sepia.recherche.enac.fr [10.31.1.82])by mauve.recherche.enac.fr (Postfix) with ESMTP id F01992FA822for ; Fri, 14 Aug 2009 11:51:46 +0200 (CEST) Message-ID: <4A8533B2.6080409@free.fr> Date: Fri, 14 Aug 2009 11:51:46 +0200 From: Pascal Brisset User-Agent: Mozilla-Thunderbird 2.0.0.22 (X11/20090706) MIME-Version: 1.0 To: paparazzi-devel@nongnu.org Subject: Re: [Paparazzi-devel] Mark Button References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-imss-version: 2.5 X-imss-result: Passed X-imss-scores: Clean:69.98158 C:22 M:1 S:5 R:5 X-imss-settings: Baseline:1 C:1 M:1 S:1 R:1 (0.0000 0.0000) X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.4-2.6 X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Aug 2009 09:51:54 -0000 Daniel Bedenko wrote: > Is there a way to activate the MARK button from the transmitter? No, this is a GCS feature: the autopilot does not know anything about it. --Pascal > > Daniel Bedenko > http://airsea.ucsd.edu/ > ------------------------------------------------------------------------ > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > From MAILER-DAEMON Fri Aug 14 06:03:14 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Mbtcv-0005Tm-FJ for mharc-paparazzi-devel@gnu.org; Fri, 14 Aug 2009 06:03:13 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mbtcs-0005R3-9m for paparazzi-devel@nongnu.org; Fri, 14 Aug 2009 06:03:10 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mbtcn-0005Md-OJ for paparazzi-devel@nongnu.org; Fri, 14 Aug 2009 06:03:09 -0400 Received: from [199.232.76.173] (port=43519 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mbtcn-0005MG-9J for paparazzi-devel@nongnu.org; Fri, 14 Aug 2009 06:03:05 -0400 Received: from imss-1.enac.fr ([195.220.159.36]:46693) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Mbtcm-0001PG-JB for paparazzi-devel@nongnu.org; Fri, 14 Aug 2009 06:03:04 -0400 Received: from mauve.recherche.enac.fr (imss-1.imss.interne.enac [127.0.0.1]) by imss-1.enac.fr (Postfix) with ESMTP id DA4C418B3A7 for ; Fri, 14 Aug 2009 12:02:51 +0200 (CEST) Received: from [10.31.1.82] (sepia.recherche.enac.fr [10.31.1.82])by mauve.recherche.enac.fr (Postfix) with ESMTP id BA1742FA822for ; Fri, 14 Aug 2009 12:02:51 +0200 (CEST) Message-ID: <4A85364B.8060007@free.fr> Date: Fri, 14 Aug 2009 12:02:51 +0200 From: Pascal Brisset User-Agent: Mozilla-Thunderbird 2.0.0.22 (X11/20090706) MIME-Version: 1.0 To: paparazzi-devel@nongnu.org Subject: Re: [Paparazzi-devel] throttle management in AUTO2 References: <4A6C0B4C.3050206@gmail.com> In-Reply-To: <4A6C0B4C.3050206@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-imss-version: 2.5 X-imss-result: Passed X-imss-scores: Clean:78.76621 C:18 M:1 S:5 R:5 X-imss-settings: Baseline:1 C:1 M:1 S:1 R:1 (0.0000 0.0000) X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.4-2.6 X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Aug 2009 10:03:10 -0000 Hi, not, there is no minimum throttle in AUTO2. You can hack main_ap.c (line 589), replacing ap_state->commands[COMMAND_THROTTLE] = v_ctl_throttle_slewed; by ap_state->commands[COMMAND_THROTTLE] = Min(MAX_PPRZ * MY_MIN_AUTO2_THROTTLE, v_ctl_throttle_slewed) --Pascal chris wrote: > Hi. > I have a hard time keeping the plane flying in a very difficult place > due to strong and very very > turbulent wind area. > Thermals are so strong that can crash the plane easily. > Yesterday i fell in to a microburst that was there for 2 or 3 minutes > and then vanished. > I almost lost the plane as it was sucked down at full throttle in > MANUAL mode. > Imagine seeing a plane flying straight at 60 -70 meters and suddenly > losing 50 meters without > changing attitude, it just sunk and everybody there said that they > have never experienced something like that again. > Is there any way to increase the minimum throttle in auto2? > I just don't want the plane to fly with anything lower than 60% > throttle except > when descending. > Chris > > > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel From MAILER-DAEMON Fri Aug 14 06:23:43 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Mbtwl-0001mw-Eg for mharc-paparazzi-devel@gnu.org; Fri, 14 Aug 2009 06:23:43 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mbtwi-0001ll-Iq for paparazzi-devel@nongnu.org; Fri, 14 Aug 2009 06:23:40 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mbtwd-0001j0-44 for paparazzi-devel@nongnu.org; Fri, 14 Aug 2009 06:23:40 -0400 Received: from [199.232.76.173] (port=45960 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mbtwc-0001ix-Ri for paparazzi-devel@nongnu.org; Fri, 14 Aug 2009 06:23:34 -0400 Received: from mail-ew0-f210.google.com ([209.85.219.210]:52703) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Mbtwb-0004pb-NC for paparazzi-devel@nongnu.org; Fri, 14 Aug 2009 06:23:34 -0400 Received: by ewy6 with SMTP id 6so1533086ewy.34 for ; Fri, 14 Aug 2009 03:23:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=RL++UUpsMKFnmSypjidxobeC7bbxfUtcdUxQnkyx7KM=; b=p3dEUbxoYjzwWE8YFlq4UQYPVZzc15vWtkpk/rkBcSOxgTUqNTzaLwZqaJYJWne7mU ebmpEpeW9fiQnIfHp87UDsgpKRVRADz6dpCnCbEJGSu9tGFU4HcO0uQB4jUu3LBM4xRy Bwd+JOVVAkVEJOohzzKCuekBtN+ziK2JGa+as= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=cMjdHBMfeHogz1KBy6fH9JHh4OCL1VfChxsO0Gl6sv2N0kqNP+Nh3bWI75X6ZT5NyV aDNGE/fgC9ctn12IVrL1ifTC2sR4waXo17AGw/owJUYX4mvTPZoBwtzpWY4Z6Kt+l7vJ mqxa65I34Ad7kTGCXK/Yl4cmiafsuSMRS2XMk= MIME-Version: 1.0 Received: by 10.216.35.69 with SMTP id t47mr344879wea.221.1250245411831; Fri, 14 Aug 2009 03:23:31 -0700 (PDT) In-Reply-To: <4a8536a5.8a53f10a.33f0.ffffa7ccSMTPIN_ADDED@mx.google.com> References: <4a8536a5.8a53f10a.33f0.ffffa7ccSMTPIN_ADDED@mx.google.com> Date: Fri, 14 Aug 2009 13:23:31 +0300 Message-ID: From: =?ISO-8859-9?Q?A=2E_Fatih_=DEenkul?= To: paparazzi-devel@nongnu.org Content-Type: multipart/alternative; boundary=0016367f9e54a78252047117718c X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) Subject: [Paparazzi-devel] Re: Paparazzi-devel Digest, Vol 65, Issue 22 X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Aug 2009 10:23:40 -0000 --0016367f9e54a78252047117718c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Re: throttle management in AUTO2 Hello all; I newly subscribed to this mail group. I want to know the configuration of throttle in AUTO2 mode, i.e how does it arrange the throttle percentage as the plane maneuvers in the sky. You can explain me showing the related code/s if possible. Thank you; Fisek 2009/8/14 > Send Paparazzi-devel mailing list submissions to > paparazzi-devel@nongnu.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > or, via email, send a message with subject or body 'help' to > paparazzi-devel-request@nongnu.org > > You can reach the person managing the list at > paparazzi-devel-owner@nongnu.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Paparazzi-devel digest..." > > > Today's Topics: > > 1. reply to "flight plan block activation from the rc tx (Pascal > Brisset)" (chris) > 2. New path instruction (Pascal Brisset) > 3. CGS Programing Language (Rui Costa) > 4. Fly with IMU for fix wing aircraft and helicopter? > (=3D?big5?B?s6IgZmx5aW5nIHBpZw=3D=3D?=3D) > 5. New Autopilot - Tiny v3 (Rui Costa) > 6. Re: Airframe debug problem,stop at ap.elf (Pascal Brisset) > 7. Re: questions on flight plan (Pascal Brisset) > 8. Re: Mark Button (Pascal Brisset) > 9. Re: throttle management in AUTO2 (Pascal Brisset) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 13 Aug 2009 20:28:24 +0300 > From: chris > Subject: [Paparazzi-devel] reply to "flight plan block activation from > the rc tx (Pascal Brisset)" > To: paparazzi-devel@nongnu.org > Message-ID: <4A844D38.6000706@gmail.com> > Content-Type: text/plain; charset=3DISO-8859-1; format=3Dflowed > > Thank you Pascal That is exactly what i want. > I have a flight plan that the only thing it does is a photo run and it > includes > a Standby block. > I tested successfully an auto take off without the use of the transmitte= r > (i throw away the aircraft after running in order to achieve 11 km/h and > enable the motor) > so i am searching for a way to eliminate the ground station for this simp= le > flight plan. > I know that there are hidden danger in it but i test in remote areas and > controled > areas. > Chris > > > > > ------------------------------ > > Message: 2 > Date: Thu, 13 Aug 2009 19:32:50 +0200 > From: Pascal Brisset > Subject: [Paparazzi-devel] New path instruction > To: paparazzi-devel@nongnu.org > Message-ID: <4A844E42.6090605@free.fr> > Content-Type: text/plain; charset=3DISO-8859-15; format=3Dflowed > > Hi, > > answer to an old request (I cannot find it): A instruction has > been added to the flight plan language to fly over a list of waypoints. > It is simply preprocessed into a sequence of instructions. Example > in basic.xml: > > (1,2,S1,S2,STDBY)" strip_icon=3D"path.png"> > > throttle=3D"0.4"/> > > > > The list separaror is the regular expression "[ \t,]+" (at least one > space, tab or comma). Extra standard attributes are allowed. > The translation produces here > > > > throttle=3D"0.4" pitch=3D"auto" wpts=3D"S1, S2 STDBY" no=3D"2"/> > throttle=3D"0.4" pitch=3D"auto" wpts=3D"S1, S2 STDBY" no=3D"3"/> > > and it is what you will see in the GCS. > > --Pascal > > PS: No, it is not possible to dynamically define the waypoints list from > the GCS during the flight :-) > > > > > ------------------------------ > > Message: 3 > Date: Thu, 13 Aug 2009 17:40:51 +0000 > From: Rui Costa > Subject: [Paparazzi-devel] CGS Programing Language > To: paparazzi-devel@nongnu.org > Message-ID: > <4d39daa50908131040h118b1bdei96b0dde5d99e1009@mail.gmail.com> > Content-Type: text/plain; charset=3D"iso-8859-1" > > Hello all, > > > What's the programming language of the CGS? How can I modify and compile > the > CGS? > > > > > Best regards > Rui Costa > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > http://lists.gnu.org/pipermail/paparazzi-devel/attachments/20090813/0205a= 9cd/attachment.html > > ------------------------------ > > Message: 4 > Date: Fri, 14 Aug 2009 08:28:49 +0000 > From: =3D?big5?B?s6IgZmx5aW5nIHBpZw=3D=3D?=3D > Subject: [Paparazzi-devel] Fly with IMU for fix wing aircraft and > helicopter? > To: > Message-ID: > Content-Type: text/plain; charset=3D"big5" > > > Hi there > > > > I am in the process of buliding up the Booz IMU, and i was wonering, doe= s > the current code allow to intergrate IMU to Tiny for fix wing and > helicopter? > > > > We will try to fly with our helipoter with IR sesnor today (it has inbui= d > simple stabilisation hardware from the toy company), so we are just looki= ng > with using Tiny to control the PWM signal for coaxial heclicopter. I am = not > sure it wil work, but we will try, i will let you guys know. > > > > > > > > > > Regards > > > > > Chen > > > > > > _________________________________________________________________ > =E7=94=A8=E9=83=A8=E8=90=BD=E6=A0=BC=E5=88=86=E4=BA=AB=E7=85=A7=E7=89=87= =E3=80=81=E5=BD=B1=E9=9F=B3=E3=80=81=E8=B6=A3=E5=91=B3=E5=B0=8F=E5=B7=A5=E5= =85=B7=E5=92=8C=E6=9C=80=E6=84=9B=E6=B8=85=E5=96=AE=EF=BC=8C=E7=9B=A1=E6=83= =85=E7=A7=80=E5=87=BA=E4=BD=A0=E8=87=AA=E5=B7=B1 =E2=80=94 Windows Live Spa= ces > http://home.spaces.live.com/?showUnauth=3D1&lc=3D1028 > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > http://lists.gnu.org/pipermail/paparazzi-devel/attachments/20090814/a722a= 16d/attachment.html > > ------------------------------ > > Message: 5 > Date: Fri, 14 Aug 2009 08:38:32 +0000 > From: Rui Costa > Subject: [Paparazzi-devel] New Autopilot - Tiny v3 > To: paparazzi-devel@nongnu.org > Message-ID: > <4d39daa50908140138of35bbfeq607ef90c3fca785e@mail.gmail.com> > Content-Type: text/plain; charset=3D"iso-8859-1" > > Hello all, > > > Let's talk about possible new features for the new Tiny. I think it's tim= e > to make a new autopilot based on experience acumulated from the others Ti= ny > boards. > We can discuss this new features by here, wiki, IRC channel or f=E9=8F=8E= um. > > *http://paparazzi.enac.fr/wiki/Tiny_v3* > > I will need some help with some new components and the implementation of > the > software part. > > > Best regards > Rui Costa > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > http://lists.gnu.org/pipermail/paparazzi-devel/attachments/20090814/7b2af= d1f/attachment.html > > ------------------------------ > > Message: 6 > Date: Fri, 14 Aug 2009 11:35:04 +0200 > From: Pascal Brisset > Subject: Re: [Paparazzi-devel] Airframe debug problem,stop at ap.elf > To: paparazzi-devel@nongnu.org > Message-ID: <4A852FC8.3040801@free.fr> > Content-Type: text/plain; charset=3DUTF-8; format=3Dflowed > > You have to keep this line (not related to gyro): > > ap.srcs +=3D nav_survey_rectangle.c nav_line.c > > --Pascal > > =E8=9D=A1=E4=BA=A6=EF=BF=BD wrote: > > Hi, > > I had problem when trying to remove lines of Gyro from the airframe > > file.Debuging always stopped at LD > > /home/mnw/paparazzi3/var/mnwAC/ap/ap.elf,I couldn't figure out why.I'v > > put the airframe file here http://pastebin.com/m6cb0a486. > > Help me out. > > > > Thanks all. > > -----------------------------------------------------------------------= - > > > > _______________________________________________ > > Paparazzi-devel mailing list > > Paparazzi-devel@nongnu.org > > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > > > > > > > > ------------------------------ > > Message: 7 > Date: Fri, 14 Aug 2009 11:50:24 +0200 > From: Pascal Brisset > Subject: Re: [Paparazzi-devel] questions on flight plan > To: paparazzi-devel@nongnu.org > Message-ID: <4A853360.3050205@free.fr> > Content-Type: text/plain; charset=3DISO-8859-1; format=3Dflowed > > Hi Steve, > > there is an "old" feature using procedures: > http://paparazzi.enac.fr/wiki/Flight_Plans#Procedures > But it will require a reflash of your autopilot. > > The NavSetGroundReferenceHere() function translates the waypoints around > the current GPS location. It's easy to write a similar function to > do a rotation (for example around HOME). You only need a way to specify > the heading you want. You could use a specific waypoint. The procedure > would be: > - NavSetGroundReferenceHere() > - set a waypoint (XX) > - NavRotateAroundHOME(WP_XX) > > hth > > --Pascal > > > > Steve Ross wrote: > > Most of the flight plans can be used in any places by using the > > relative coordinates of the waypoints to the HOME location, one thing > > I don't understand is how people aligned the fields in the flight > > plans to the new flying fields. Suppose I have the "versatile.html" as > > my flight plan in mind and arrive at a new field and choose one > > location as my HOME waypoint and find a runway to take off. Do I have > > to bring a *compass* to know the orientation of the field in the > > flight plan to the current field I arrive at? Otherwise, it's likely > > that my field will be a *rotation* of the field in the flight plan > > around the waypoint HOME. I may think that the other waypoints in the > > flight plan are located within the actual field but in actuality some > > of the waypoints are out of the boundary of the actual field due to > > the wrong assumption of the *rotation* on the field in the flight > > plan. If I discover that my assumption is wrong after I arrive at that > > field, is there any quick and easy way to rotate and create a new > > flight plan at the field? (One command that rotate all of the > > waypoints in the flight plan to allign with actual field around the > > HOME?). > > > > Thanks a lot. > > -----------------------------------------------------------------------= - > > > > _______________________________________________ > > Paparazzi-devel mailing list > > Paparazzi-devel@nongnu.org > > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > > > > > > > > ------------------------------ > > Message: 8 > Date: Fri, 14 Aug 2009 11:51:46 +0200 > From: Pascal Brisset > Subject: Re: [Paparazzi-devel] Mark Button > To: paparazzi-devel@nongnu.org > Message-ID: <4A8533B2.6080409@free.fr> > Content-Type: text/plain; charset=3DISO-8859-1; format=3Dflowed > > Daniel Bedenko wrote: > > Is there a way to activate the MARK button from the transmitter? > > No, this is a GCS feature: the autopilot does not know anything about it= . > > --Pascal > > > > > Daniel Bedenko > > http://airsea.ucsd.edu/ > > -----------------------------------------------------------------------= - > > > > _______________________________________________ > > Paparazzi-devel mailing list > > Paparazzi-devel@nongnu.org > > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > > > > > > > > ------------------------------ > > Message: 9 > Date: Fri, 14 Aug 2009 12:02:51 +0200 > From: Pascal Brisset > Subject: Re: [Paparazzi-devel] throttle management in AUTO2 > To: paparazzi-devel@nongnu.org > Message-ID: <4A85364B.8060007@free.fr> > Content-Type: text/plain; charset=3DISO-8859-1; format=3Dflowed > > Hi, > > not, there is no minimum throttle in AUTO2. You can hack main_ap.c (line > 589), replacing > > ap_state->commands[COMMAND_THROTTLE] =3D v_ctl_throttle_slewed; > > by > > ap_state->commands[COMMAND_THROTTLE] =3D Min(MAX_PPRZ * > MY_MIN_AUTO2_THROTTLE, v_ctl_throttle_slewed) > > --Pascal > > chris wrote: > > Hi. > > I have a hard time keeping the plane flying in a very difficult place > > due to strong and very very > > turbulent wind area. > > Thermals are so strong that can crash the plane easily. > > Yesterday i fell in to a microburst that was there for 2 or 3 minutes > > and then vanished. > > I almost lost the plane as it was sucked down at full throttle in > > MANUAL mode. > > Imagine seeing a plane flying straight at 60 -70 meters and suddenly > > losing 50 meters without > > changing attitude, it just sunk and everybody there said that they > > have never experienced something like that again. > > Is there any way to increase the minimum throttle in auto2? > > I just don't want the plane to fly with anything lower than 60% > > throttle except > > when descending. > > Chris > > > > > > > > _______________________________________________ > > Paparazzi-devel mailing list > > Paparazzi-devel@nongnu.org > > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > > > > > > ------------------------------ > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > > > End of Paparazzi-devel Digest, Vol 65, Issue 22 > *********************************************** > --0016367f9e54a78252047117718c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Re: throttle management in AUTO2


Hello all;

I newly subs= cribed to this mail group.
I want to know the configuration of throttle= in AUTO2 mode, i.e how does it arrange the throttle percentage as the plan= e maneuvers in the sky. You can explain me showing the related code/s if po= ssible.

Thank you;

Fisek



2009/= 8/14 <paparazzi-devel-request@nongnu.org>
Send Paparazzi-devel mailing list submissions to
=C2=A0 =C2=A0 =C2=A0 =C2=A0p= aparazzi-devel@nongnu.org

To subscribe or unsubscribe via the World Wide Web, visit
=C2=A0 =C2=A0 =C2=A0 =C2=A0http://lists.nongnu.org/mailman/lis= tinfo/paparazzi-devel
or, via email, send a message with subject or body 'help' to
=C2=A0 =C2=A0 =C2=A0 =C2=A0paparazzi-devel-request@nongnu.org

You can reach the person managing the list at
=C2=A0 =C2=A0 =C2=A0 =C2=A0paparazzi-devel-owner@nongnu.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Paparazzi-devel digest..."


Today's Topics:

=C2=A0 1. reply to "flight plan block activation from the =C2=A0 rc t= x (Pascal
=C2=A0 =C2=A0 =C2=A0Brisset)" (chris)
=C2=A0 2. New path instruction (Pascal Brisset)
=C2=A0 3. CGS Programing Language (Rui Costa)
=C2=A0 4. Fly with IMU for fix wing aircraft and helicopter?
=C2=A0 =C2=A0 =C2=A0(=3D?big5?B?s6IgZmx5aW5nIHBpZw=3D=3D?=3D)
=C2=A0 5. New Autopilot - Tiny v3 (Rui Costa)
=C2=A0 6. Re: Airframe debug problem,stop at ap.elf (Pascal Brisset)
=C2=A0 7. Re: questions on flight plan (Pascal Brisset)
=C2=A0 8. Re: Mark Button (Pascal Brisset)
=C2=A0 9. Re: throttle management in AUTO2 (Pascal Brisset)


----------------------------------------------------------------------

Message: 1
Date: Thu, 13 Aug 2009 20:28:24 +0300
From: chris <hendrixgr@gmail.com<= /a>>
Subject: [Paparazzi-devel] reply to "flight plan block activation from=
=C2=A0 =C2=A0 =C2=A0 =C2=A0the =C2=A0 =C2=A0 rc tx (Pascal Brisset)"<= br> To:
paparazzi-devel@nongnu.or= g
Message-ID: <4A844D38.6000= 706@gmail.com>
Content-Type: text/plain; charset=3DISO-8859-1; format=3Dflowed

Thank you Pascal That is exactly what i want.
I have a flight plan that the only thing it does is a photo run and it
includes
a Standby block.
I tested successfully an auto take off =C2=A0without the use of the transmi= tter
(i throw away the aircraft after running in order to achieve 11 km/h and enable the motor)
so i am searching for a way to eliminate the ground station for this simple=
flight plan.
I know that there are hidden danger in it but i test in remote areas and controled
areas.
Chris




------------------------------

Message: 2
Date: Thu, 13 Aug 2009 19:32:50 +0200
From: Pascal Brisset <pascal.b= risset@free.fr>
Subject: [Paparazzi-devel] New path instruction
To: paparazzi-devel@nongnu.or= g
Message-ID: <4A844E42.609060= 5@free.fr>
Content-Type: text/plain; =C2=A0 =C2=A0 =C2=A0 charset=3DISO-8859-15; =C2= =A0 =C2=A0format=3Dflowed

Hi,

answer to an old request (I cannot find it): A <path/> instruction ha= s
been added to the flight plan language to fly over a list of waypoints.
It is simply preprocessed into a sequence of <go/> instructions. Exam= ple
in basic.xml:

=C2=A0 =C2=A0<block name=3D"Path 1,2,S1,S2,STDBY" strip_butto= n=3D"Path
(1,2,S1,S2,STDBY)" strip_icon=3D"path.png">
=C2=A0 =C2=A0 =C2=A0<path wpts=3D"1,2 S1"/>
=C2=A0 =C2=A0 =C2=A0<path wpts=3D"S1, S2 STDBY" approaching_t= ime=3D"1" pitch=3D"auto"
throttle=3D"0.4"/>
=C2=A0 =C2=A0 =C2=A0<deroute block=3D"Standby"/>
=C2=A0 =C2=A0</block>

The list separaror is the regular expression "[ \t,]+" (at least = one
space, tab or comma). Extra standard attributes are allowed.
The translation produces here

=C2=A0 =C2=A0 =C2=A0 =C2=A0<go from=3D"1" hmode=3D"route= " wp=3D"2" wpts=3D"1,2 S1" no=3D"0"/>=
=C2=A0 =C2=A0 =C2=A0 =C2=A0<go from=3D"2" hmode=3D"route= " wp=3D"S1" wpts=3D"1,2 S1" no=3D"1"/>= ;
=C2=A0 =C2=A0 =C2=A0 =C2=A0<go from=3D"S1" hmode=3D"rout= e" wp=3D"S2" approaching_time=3D"1"
throttle=3D"0.4" pitch=3D"auto" wpts=3D"S1, S2 STD= BY" no=3D"2"/>
=C2=A0 =C2=A0 =C2=A0 =C2=A0<go from=3D"S2" hmode=3D"rout= e" wp=3D"STDBY" approaching_time=3D"1"
throttle=3D"0.4" pitch=3D"auto" wpts=3D"S1, S2 STD= BY" no=3D"3"/>

and it is what you will see in the GCS.

--Pascal

PS: No, it is not possible to dynamically define the waypoints list from the GCS during the flight :-)




------------------------------

Message: 3
Date: Thu, 13 Aug 2009 17:40:51 +0000
From: Rui Costa <azoreanuav@gmai= l.com>
Subject: [Paparazzi-devel] CGS Programing Language
To: paparazzi-devel@nongnu.or= g
Message-ID:
=C2=A0 =C2=A0 =C2=A0 =C2=A0<4d39daa50908131040h118b1bdei96b0dde5d99= e1009@mail.gmail.com>
Content-Type: text/plain; charset=3D"iso-8859-1"

Hello all,


What's the programming language of the CGS? How can I modify and compil= e the
CGS?




Best regards
Rui Costa
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.gnu.org/p= ipermail/paparazzi-devel/attachments/20090813/0205a9cd/attachment.html<= br>
------------------------------

Message: 4
Date: Fri, 14 Aug 2009 08:28:49 +0000
From: =3D?big5?B?s6IgZmx5aW5nIHBpZw=3D=3D?=3D <idf2b@hotmail.com>
Subject: [Paparazzi-devel] Fly with IMU for fix wing aircraft and
=C2=A0 =C2=A0 =C2=A0 =C2=A0helicopter?
To: <paparazzi-devel@nongn= u.org>
Message-ID: <BLU149-W50F92EBFC1348C75CBDC92F4020@phx.gbl>
Content-Type: text/plain; charset=3D"big5"


Hi there



=C2=A0I am in the process of buliding up the Booz IMU, and i was wonering,= does the current code allow to intergrate IMU to Tiny for fix wing and hel= icopter?



=C2=A0We will try to fly with our helipoter with IR sesnor today (it has i= nbuid simple stabilisation hardware from the toy company), so we are just l= ooking with using Tiny to control the PWM signal for coaxial heclicopter. = =C2=A0I am not sure it wil work, but we will try, i will let you guys know.=









Regards



=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Chen





_________________________________________________________________
=E7=94=A8=E9=83=A8=E8=90=BD=E6=A0=BC=E5=88=86=E4=BA=AB=E7=85=A7=E7=89=87=E3= =80=81=E5=BD=B1=E9=9F=B3=E3=80=81=E8=B6=A3=E5=91=B3=E5=B0=8F=E5=B7=A5=E5=85= =B7=E5=92=8C=E6=9C=80=E6=84=9B=E6=B8=85=E5=96=AE=EF=BC=8C=E7=9B=A1=E6=83=85= =E7=A7=80=E5=87=BA=E4=BD=A0=E8=87=AA=E5=B7=B1 =E2=80=94 Windows Live Spaces=
http://home.spaces.live.com/?showUnauth=3D1&lc=3D1028<= br> -------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.gnu.org/p= ipermail/paparazzi-devel/attachments/20090814/a722a16d/attachment.html<= br>
------------------------------

Message: 5
Date: Fri, 14 Aug 2009 08:38:32 +0000
From: Rui Costa <azoreanuav@gmai= l.com>
Subject: [Paparazzi-devel] New Autopilot - Tiny v3
To: paparazzi-devel@nongnu.or= g
Message-ID:
=C2=A0 =C2=A0 =C2=A0 =C2=A0<4d39daa50908140138of35bbfeq607ef90c3fca7= 85e@mail.gmail.com>
Content-Type: text/plain; charset=3D"iso-8859-1"

Hello all,


Let's talk about possible new features for the new Tiny. I think it'= ;s time
to make a new autopilot based on experience acumulated from the others Tiny=
boards.
We can discuss this new features by here, wiki, IRC channel or f=E9=8F=8Eum= .

*http:= //paparazzi.enac.fr/wiki/Tiny_v3* <paparazzi-devel@nongnu.org>

I will need some help with some new components and the implementation of th= e
software part.


Best regards
Rui Costa
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.gnu.org/p= ipermail/paparazzi-devel/attachments/20090814/7b2afd1f/attachment.html<= br>
------------------------------

Message: 6
Date: Fri, 14 Aug 2009 11:35:04 +0200
From: Pascal Brisset <pascal.b= risset@free.fr>
Subject: Re: [Paparazzi-devel] Airframe debug problem,stop at ap.elf
To: paparazzi-devel@nongnu.or= g
Message-ID: <4A852FC8.304080= 1@free.fr>
Content-Type: text/plain; =C2=A0 =C2=A0 =C2=A0 charset=3DUTF-8; =C2=A0forma= t=3Dflowed

You have to keep this line (not related to gyro):

ap.srcs +=3D nav_survey_rectangle.c nav_line.c

--Pascal

=E8=9D=A1=E4=BA=A6=EF=BF=BD wrote:
> Hi,
> I had problem when trying to remove lines of Gyro from the airframe > file.Debuging always stopped at LD
> /home/mnw/paparazzi3/var/mnwAC/ap/ap.elf,I couldn't figure out why= .I'v
> put the airframe file here http://pastebin.com/m6cb0a486.
> Help me out.
>
> Thanks all.
> ----------------------------------------------------------------------= --
>
> _______________________________________________
> Paparazzi-devel mailing list
> Paparazzi-devel@nongnu.o= rg
> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel
>





------------------------------

Message: 7
Date: Fri, 14 Aug 2009 11:50:24 +0200
From: Pascal Brisset <
pascal.b= risset@free.fr>
Subject: Re: [Paparazzi-devel] questions on flight plan
To: paparazzi-devel@nongnu.or= g
Message-ID: <4A853360.305020= 5@free.fr>
Content-Type: text/plain; =C2=A0 =C2=A0 =C2=A0 charset=3DISO-8859-1; =C2=A0= =C2=A0 format=3Dflowed

Hi Steve,

there is an "old" feature using procedures:
http://paparazzi.enac.fr/wiki/Flight_Plans#Procedures
But it will require a reflash of your autopilot.

The NavSetGroundReferenceHere() function translates the waypoints around the current GPS location. It's easy to write a similar function to
do a rotation (for example around HOME). You only need a way to specify
the heading you want. You could use a specific waypoint. The procedure
would be:
=C2=A0- NavSetGroundReferenceHere()
=C2=A0- set a waypoint =C2=A0(XX)
=C2=A0- NavRotateAroundHOME(WP_XX)

hth

--Pascal



Steve Ross wrote:
> Most of the flight plans can be used in any places by using the
> relative coordinates of the waypoints to the HOME location, one thing<= br> > I don't understand is how people aligned the fields in the flight<= br> > plans to the new flying fields. Suppose I have the "versatile.htm= l" as
> my flight plan in mind and arrive at a new field and choose one
> location as my HOME waypoint and find a runway to take off. Do I have<= br> > to bring a *compass* to know the orientation of the field in the
> flight plan to the current field I arrive at? Otherwise, it's like= ly
> that my field will be a *rotation* of the field in the flight plan
> around the waypoint HOME. I may think that the other waypoints in the<= br> > flight plan are located within the actual field but in actuality some<= br> > of the waypoints are out of the boundary of the actual field due to > the wrong assumption of the *rotation* on the field in the flight
> plan. If I discover that my assumption is wrong after I arrive at that=
> field, is there any quick and easy way to rotate and create a new
> flight plan at the field? (One command that rotate all of the
> waypoints in the flight plan to allign with actual field around the > HOME?).
>
> Thanks a lot.
> ----------------------------------------------------------------------= --
>
> _______________________________________________
> Paparazzi-devel mailing list
> Paparazzi-devel@nongnu.o= rg
> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel
>





------------------------------

Message: 8
Date: Fri, 14 Aug 2009 11:51:46 +0200
From: Pascal Brisset <
pascal.b= risset@free.fr>
Subject: Re: [Paparazzi-devel] Mark Button
To: paparazzi-devel@nongnu.or= g
Message-ID: <4A8533B2.608040= 9@free.fr>
Content-Type: text/plain; =C2=A0 =C2=A0 =C2=A0 charset=3DISO-8859-1; =C2=A0= =C2=A0 format=3Dflowed

Daniel Bedenko wrote:
> Is there a way to activate the MARK button from the transmitter?

=C2=A0No, this is a GCS feature: the autopilot does not know anything about= it.

--Pascal

>
> Daniel Bedenko
> http://airsea.uc= sd.edu/
> ----------------------------------------------------------------------= --
>
> _______________________________________________
> Paparazzi-devel mailing list
> Paparazzi-devel@nongnu.o= rg
> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel
>





------------------------------

Message: 9
Date: Fri, 14 Aug 2009 12:02:51 +0200
From: Pascal Brisset <
pascal.b= risset@free.fr>
Subject: Re: [Paparazzi-devel] throttle management in AUTO2
To: paparazzi-devel@nongnu.or= g
Message-ID: <4A85364B.806000= 7@free.fr>
Content-Type: text/plain; =C2=A0 =C2=A0 =C2=A0 charset=3DISO-8859-1; =C2=A0= =C2=A0 format=3Dflowed

Hi,

not, there is no minimum throttle in AUTO2. You can hack main_ap.c (line 589), replacing

=C2=A0 =C2=A0 ap_state->commands[COMMAND_THROTTLE] =3D v_ctl_throttle_s= lewed;

by

=C2=A0 =C2=A0ap_state->commands[COMMAND_THROTTLE] =3D Min(MAX_PPRZ * MY_MIN_AUTO2_THROTTLE, v_ctl_throttle_slewed)

--Pascal

chris wrote:
> Hi.
> I have a hard time keeping the plane flying in a very difficult place<= br> > due to strong and very very
> turbulent wind area.
> Thermals are so strong that can crash the plane easily.
> Yesterday i fell in to a microburst that was there for 2 or 3 minutes<= br> > and then vanished.
> I almost lost the plane as it was sucked down at full throttle in
> MANUAL mode.
> Imagine seeing a plane flying straight at 60 -70 meters and suddenly > losing 50 meters without
> changing attitude, it just sunk and everybody there said that they
> have never experienced something like that again.
> Is there any way to increase the minimum throttle in auto2?
> I just don't want the plane to fly with anything lower than 60% > throttle except
> when descending.
> Chris
>
>
>
> _______________________________________________
> Paparazzi-devel mailing list
> Paparazzi-devel@nongnu.o= rg
> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel





------------------------------

_______________________________________________
Paparazzi-devel mailing list
Paparazzi-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/paparazzi-devel

End of Paparazzi-devel Digest, Vol 65, Issue 22
***********************************************

--0016367f9e54a78252047117718c-- From MAILER-DAEMON Fri Aug 14 07:32:15 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Mbv14-0006w1-QN for mharc-paparazzi-devel@gnu.org; Fri, 14 Aug 2009 07:32:14 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mbv12-0006tZ-8R for paparazzi-devel@nongnu.org; Fri, 14 Aug 2009 07:32:12 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mbv0x-0006rV-RK for paparazzi-devel@nongnu.org; Fri, 14 Aug 2009 07:32:11 -0400 Received: from [199.232.76.173] (port=39759 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mbv0x-0006rS-KS for paparazzi-devel@nongnu.org; Fri, 14 Aug 2009 07:32:07 -0400 Received: from mail-ew0-f210.google.com ([209.85.219.210]:48656) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Mbv0w-0006qJ-Kr for paparazzi-devel@nongnu.org; Fri, 14 Aug 2009 07:32:07 -0400 Received: by ewy6 with SMTP id 6so1570329ewy.34 for ; Fri, 14 Aug 2009 04:32:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=K7TUiJiTR0bRlUVTlENowUemJJg8B9J/VmFTK5ZElIw=; b=Ga1KseQ0PtC8UfhlXVYR+TVCoVQb74EW6XV/sc/H+uMTlgRXM38gjZXOvNJXcpCqrG yfgrqZdMU3U9awIgcnGX8O57UUijhquT4I3pOI0YlQAhShd6PACPg6PpEAOWDgZ9xIgx t7YhWQd19LNGSHuQUgvayaxVJx4V3zqWjywJw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=EFefWp0eC4vopAyNQ70ygr+6FyX8wTKOTL7jq8WhuLmiiQJFdRkduYtmoLh2R3jeJF JFZPq0HpkmxfPVpNsiY4LPKa20lbH7zlMUdZdDxgS8cOE07fGq98m/OtyRTipFtmPjAN x1qfrHqnGkAVwn5mvSe96oOHJGq3gH5vShOrU= MIME-Version: 1.0 Received: by 10.216.11.137 with SMTP id 9mr402827wex.180.1250249525483; Fri, 14 Aug 2009 04:32:05 -0700 (PDT) Date: Fri, 14 Aug 2009 14:32:05 +0300 Message-ID: From: =?ISO-8859-9?Q?A=2E_Fatih_=DEenkul?= To: paparazzi-devel@nongnu.org Content-Type: multipart/alternative; boundary=0016364c7c07d8d7f5047118660a X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) Subject: [Paparazzi-devel] Throttle management in AUTO2 X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Aug 2009 11:32:12 -0000 --0016364c7c07d8d7f5047118660a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hello again; Just to make my quesiton clearer: For example, due to the code our throttle value should constantly stay at %70 when climbing in AUTO2 mode. What I wan= t to know is that how does the control mechanism work here? It can either onl= y focus on the value of %70 and give the necessary voltage to the motor or th= e code that runs this mode can work in calloboration with both keeping the %7= 0 value and/or keeping the stability (which may be hard to keep constant due to dolphin move and the outside effects on the plane) as it climbs to an intended altitude. 2009/8/14 A. Fatih =C5=9Eenkul > Re: throttle management in AUTO2 > > > Hello all; > > I newly subscribed to this mail group. > I want to know the configuration of throttle in AUTO2 mode, i.e how does = it > arrange the throttle percentage as the plane maneuvers in the sky. You ca= n > explain me showing the related code/s if possible. > > Thank you; > > Fisek > > > > 2009/8/14 > > Send Paparazzi-devel mailing list submissions to >> paparazzi-devel@nongnu.org >> >> To subscribe or unsubscribe via the World Wide Web, visit >> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel >> or, via email, send a message with subject or body 'help' to >> paparazzi-devel-request@nongnu.org >> >> You can reach the person managing the list at >> paparazzi-devel-owner@nongnu.org >> >> When replying, please edit your Subject line so it is more specific >> than "Re: Contents of Paparazzi-devel digest..." >> >> >> Today's Topics: >> >> 1. reply to "flight plan block activation from the rc tx (Pascal >> Brisset)" (chris) >> 2. New path instruction (Pascal Brisset) >> 3. CGS Programing Language (Rui Costa) >> 4. Fly with IMU for fix wing aircraft and helicopter? >> (=3D?big5?B?s6IgZmx5aW5nIHBpZw=3D=3D?=3D) >> 5. New Autopilot - Tiny v3 (Rui Costa) >> 6. Re: Airframe debug problem,stop at ap.elf (Pascal Brisset) >> 7. Re: questions on flight plan (Pascal Brisset) >> 8. Re: Mark Button (Pascal Brisset) >> 9. Re: throttle management in AUTO2 (Pascal Brisset) >> >> >> ---------------------------------------------------------------------- >> >> Message: 1 >> Date: Thu, 13 Aug 2009 20:28:24 +0300 >> From: chris >> Subject: [Paparazzi-devel] reply to "flight plan block activation from >> the rc tx (Pascal Brisset)" >> To: paparazzi-devel@nongnu.org >> Message-ID: <4A844D38.6000706@gmail.com> >> Content-Type: text/plain; charset=3DISO-8859-1; format=3Dflowed >> >> Thank you Pascal That is exactly what i want. >> I have a flight plan that the only thing it does is a photo run and it >> includes >> a Standby block. >> I tested successfully an auto take off without the use of the transmitt= er >> (i throw away the aircraft after running in order to achieve 11 km/h and >> enable the motor) >> so i am searching for a way to eliminate the ground station for this >> simple >> flight plan. >> I know that there are hidden danger in it but i test in remote areas and >> controled >> areas. >> Chris >> >> >> >> >> ------------------------------ >> >> Message: 2 >> Date: Thu, 13 Aug 2009 19:32:50 +0200 >> From: Pascal Brisset >> Subject: [Paparazzi-devel] New path instruction >> To: paparazzi-devel@nongnu.org >> Message-ID: <4A844E42.6090605@free.fr> >> Content-Type: text/plain; charset=3DISO-8859-15; format=3Dflowe= d >> >> Hi, >> >> answer to an old request (I cannot find it): A instruction has >> been added to the flight plan language to fly over a list of waypoints. >> It is simply preprocessed into a sequence of instructions. Example >> in basic.xml: >> >> > (1,2,S1,S2,STDBY)" strip_icon=3D"path.png"> >> >> > throttle=3D"0.4"/> >> >> >> >> The list separaror is the regular expression "[ \t,]+" (at least one >> space, tab or comma). Extra standard attributes are allowed. >> The translation produces here >> >> >> >> > throttle=3D"0.4" pitch=3D"auto" wpts=3D"S1, S2 STDBY" no=3D"2"/> >> > throttle=3D"0.4" pitch=3D"auto" wpts=3D"S1, S2 STDBY" no=3D"3"/> >> >> and it is what you will see in the GCS. >> >> --Pascal >> >> PS: No, it is not possible to dynamically define the waypoints list from >> the GCS during the flight :-) >> >> >> >> >> ------------------------------ >> >> Message: 3 >> Date: Thu, 13 Aug 2009 17:40:51 +0000 >> From: Rui Costa >> Subject: [Paparazzi-devel] CGS Programing Language >> To: paparazzi-devel@nongnu.org >> Message-ID: >> <4d39daa50908131040h118b1bdei96b0dde5d99e1009@mail.gmail.com> >> Content-Type: text/plain; charset=3D"iso-8859-1" >> >> Hello all, >> >> >> What's the programming language of the CGS? How can I modify and compile >> the >> CGS? >> >> >> >> >> Best regards >> Rui Costa >> -------------- next part -------------- >> An HTML attachment was scrubbed... >> URL: >> http://lists.gnu.org/pipermail/paparazzi-devel/attachments/20090813/0205= a9cd/attachment.html >> >> ------------------------------ >> >> Message: 4 >> Date: Fri, 14 Aug 2009 08:28:49 +0000 >> From: =3D?big5?B?s6IgZmx5aW5nIHBpZw=3D=3D?=3D >> Subject: [Paparazzi-devel] Fly with IMU for fix wing aircraft and >> helicopter? >> To: >> Message-ID: >> Content-Type: text/plain; charset=3D"big5" >> >> >> Hi there >> >> >> >> I am in the process of buliding up the Booz IMU, and i was wonering, do= es >> the current code allow to intergrate IMU to Tiny for fix wing and >> helicopter? >> >> >> >> We will try to fly with our helipoter with IR sesnor today (it has inbu= id >> simple stabilisation hardware from the toy company), so we are just look= ing >> with using Tiny to control the PWM signal for coaxial heclicopter. I am= not >> sure it wil work, but we will try, i will let you guys know. >> >> >> >> >> >> >> >> >> >> Regards >> >> >> >> >> Chen >> >> >> >> >> >> _________________________________________________________________ >> =E7=94=A8=E9=83=A8=E8=90=BD=E6=A0=BC=E5=88=86=E4=BA=AB=E7=85=A7=E7=89=87= =E3=80=81=E5=BD=B1=E9=9F=B3=E3=80=81=E8=B6=A3=E5=91=B3=E5=B0=8F=E5=B7=A5=E5= =85=B7=E5=92=8C=E6=9C=80=E6=84=9B=E6=B8=85=E5=96=AE=EF=BC=8C=E7=9B=A1=E6=83= =85=E7=A7=80=E5=87=BA=E4=BD=A0=E8=87=AA=E5=B7=B1 =E2=80=94 Windows Live Spa= ces >> http://home.spaces.live.com/?showUnauth=3D1&lc=3D1028 >> -------------- next part -------------- >> An HTML attachment was scrubbed... >> URL: >> http://lists.gnu.org/pipermail/paparazzi-devel/attachments/20090814/a722= a16d/attachment.html >> >> ------------------------------ >> >> Message: 5 >> Date: Fri, 14 Aug 2009 08:38:32 +0000 >> From: Rui Costa >> Subject: [Paparazzi-devel] New Autopilot - Tiny v3 >> To: paparazzi-devel@nongnu.org >> Message-ID: >> <4d39daa50908140138of35bbfeq607ef90c3fca785e@mail.gmail.com> >> Content-Type: text/plain; charset=3D"iso-8859-1" >> >> Hello all, >> >> >> Let's talk about possible new features for the new Tiny. I think it's ti= me >> to make a new autopilot based on experience acumulated from the others >> Tiny >> boards. >> We can discuss this new features by here, wiki, IRC channel or f=E9=8F= =8Eum. >> >> *http://paparazzi.enac.fr/wiki/Tiny_v3* >> >> I will need some help with some new components and the implementation of >> the >> software part. >> >> >> Best regards >> Rui Costa >> -------------- next part -------------- >> An HTML attachment was scrubbed... >> URL: >> http://lists.gnu.org/pipermail/paparazzi-devel/attachments/20090814/7b2a= fd1f/attachment.html >> >> ------------------------------ >> >> Message: 6 >> Date: Fri, 14 Aug 2009 11:35:04 +0200 >> From: Pascal Brisset >> Subject: Re: [Paparazzi-devel] Airframe debug problem,stop at ap.elf >> To: paparazzi-devel@nongnu.org >> Message-ID: <4A852FC8.3040801@free.fr> >> Content-Type: text/plain; charset=3DUTF-8; format=3Dflowed >> >> You have to keep this line (not related to gyro): >> >> ap.srcs +=3D nav_survey_rectangle.c nav_line.c >> >> --Pascal >> >> =E8=9D=A1=E4=BA=A6=EF=BF=BD wrote: >> > Hi, >> > I had problem when trying to remove lines of Gyro from the airframe >> > file.Debuging always stopped at LD >> > /home/mnw/paparazzi3/var/mnwAC/ap/ap.elf,I couldn't figure out why.I'v >> > put the airframe file here http://pastebin.com/m6cb0a486. >> > Help me out. >> > >> > Thanks all. >> > ----------------------------------------------------------------------= -- >> > >> > _______________________________________________ >> > Paparazzi-devel mailing list >> > Paparazzi-devel@nongnu.org >> > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel >> > >> >> >> >> >> >> ------------------------------ >> >> Message: 7 >> Date: Fri, 14 Aug 2009 11:50:24 +0200 >> From: Pascal Brisset >> Subject: Re: [Paparazzi-devel] questions on flight plan >> To: paparazzi-devel@nongnu.org >> Message-ID: <4A853360.3050205@free.fr> >> Content-Type: text/plain; charset=3DISO-8859-1; format=3Dflowe= d >> >> Hi Steve, >> >> there is an "old" feature using procedures: >> http://paparazzi.enac.fr/wiki/Flight_Plans#Procedures >> But it will require a reflash of your autopilot. >> >> The NavSetGroundReferenceHere() function translates the waypoints around >> the current GPS location. It's easy to write a similar function to >> do a rotation (for example around HOME). You only need a way to specify >> the heading you want. You could use a specific waypoint. The procedure >> would be: >> - NavSetGroundReferenceHere() >> - set a waypoint (XX) >> - NavRotateAroundHOME(WP_XX) >> >> hth >> >> --Pascal >> >> >> >> Steve Ross wrote: >> > Most of the flight plans can be used in any places by using the >> > relative coordinates of the waypoints to the HOME location, one thing >> > I don't understand is how people aligned the fields in the flight >> > plans to the new flying fields. Suppose I have the "versatile.html" as >> > my flight plan in mind and arrive at a new field and choose one >> > location as my HOME waypoint and find a runway to take off. Do I have >> > to bring a *compass* to know the orientation of the field in the >> > flight plan to the current field I arrive at? Otherwise, it's likely >> > that my field will be a *rotation* of the field in the flight plan >> > around the waypoint HOME. I may think that the other waypoints in the >> > flight plan are located within the actual field but in actuality some >> > of the waypoints are out of the boundary of the actual field due to >> > the wrong assumption of the *rotation* on the field in the flight >> > plan. If I discover that my assumption is wrong after I arrive at that >> > field, is there any quick and easy way to rotate and create a new >> > flight plan at the field? (One command that rotate all of the >> > waypoints in the flight plan to allign with actual field around the >> > HOME?). >> > >> > Thanks a lot. >> > ----------------------------------------------------------------------= -- >> > >> > _______________________________________________ >> > Paparazzi-devel mailing list >> > Paparazzi-devel@nongnu.org >> > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel >> > >> >> >> >> >> >> ------------------------------ >> >> Message: 8 >> Date: Fri, 14 Aug 2009 11:51:46 +0200 >> From: Pascal Brisset >> Subject: Re: [Paparazzi-devel] Mark Button >> To: paparazzi-devel@nongnu.org >> Message-ID: <4A8533B2.6080409@free.fr> >> Content-Type: text/plain; charset=3DISO-8859-1; format=3Dflowe= d >> >> Daniel Bedenko wrote: >> > Is there a way to activate the MARK button from the transmitter? >> >> No, this is a GCS feature: the autopilot does not know anything about i= t. >> >> --Pascal >> >> > >> > Daniel Bedenko >> > http://airsea.ucsd.edu/ >> > ----------------------------------------------------------------------= -- >> > >> > _______________________________________________ >> > Paparazzi-devel mailing list >> > Paparazzi-devel@nongnu.org >> > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel >> > >> >> >> >> >> >> ------------------------------ >> >> Message: 9 >> Date: Fri, 14 Aug 2009 12:02:51 +0200 >> From: Pascal Brisset >> Subject: Re: [Paparazzi-devel] throttle management in AUTO2 >> To: paparazzi-devel@nongnu.org >> Message-ID: <4A85364B.8060007@free.fr> >> Content-Type: text/plain; charset=3DISO-8859-1; format=3Dflowe= d >> >> Hi, >> >> not, there is no minimum throttle in AUTO2. You can hack main_ap.c (line >> 589), replacing >> >> ap_state->commands[COMMAND_THROTTLE] =3D v_ctl_throttle_slewed; >> >> by >> >> ap_state->commands[COMMAND_THROTTLE] =3D Min(MAX_PPRZ * >> MY_MIN_AUTO2_THROTTLE, v_ctl_throttle_slewed) >> >> --Pascal >> >> chris wrote: >> > Hi. >> > I have a hard time keeping the plane flying in a very difficult place >> > due to strong and very very >> > turbulent wind area. >> > Thermals are so strong that can crash the plane easily. >> > Yesterday i fell in to a microburst that was there for 2 or 3 minutes >> > and then vanished. >> > I almost lost the plane as it was sucked down at full throttle in >> > MANUAL mode. >> > Imagine seeing a plane flying straight at 60 -70 meters and suddenly >> > losing 50 meters without >> > changing attitude, it just sunk and everybody there said that they >> > have never experienced something like that again. >> > Is there any way to increase the minimum throttle in auto2? >> > I just don't want the plane to fly with anything lower than 60% >> > throttle except >> > when descending. >> > Chris >> > >> > >> > >> > _______________________________________________ >> > Paparazzi-devel mailing list >> > Paparazzi-devel@nongnu.org >> > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel >> >> >> >> >> >> ------------------------------ >> >> _______________________________________________ >> Paparazzi-devel mailing list >> Paparazzi-devel@nongnu.org >> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel >> >> >> End of Paparazzi-devel Digest, Vol 65, Issue 22 >> *********************************************** >> > > --0016364c7c07d8d7f5047118660a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hello again;

Just to make my quesiton clearer: For example, due to t= he code our throttle value should constantly stay at %70 when climbing in A= UTO2 mode. What I want to know is that how does the control mechanism work = here? It can either only focus on the value of %70 and give the necessary v= oltage to the motor or the code that runs this mode can work in calloborati= on with both keeping the %70 value and/or keeping the stability (which may = be hard to keep constant due to dolphin move and the outside effects on the= plane) as it climbs to an intended altitude.


2009/8/14 A. Fatih =C5=9Eenkul <xesfisek@gmail.com&g= t;
Re: throttle management in AUTO2


Hello = all;

I newly subscribed to this mail group.
I want to know the c= onfiguration of throttle in AUTO2 mode, i.e how does it arrange the throttl= e percentage as the plane maneuvers in the sky. You can explain me showing = the related code/s if possible.

Thank you;

Fisek



2009/= 8/14 <paparazzi-devel-request@nongnu.org><= div>

Send Paparazzi-devel mailing list submissions to
=C2=A0 =C2=A0 =C2=A0 =C2=A0paparazzi-devel@nongnu.org

To subscribe or unsubscribe via the World Wide Web, visit
=C2=A0 =C2=A0 =C2=A0 =C2=A0http://lists.nongnu.org/mailman/lis= tinfo/paparazzi-devel
or, via email, send a message with subject or body 'help' to
=C2=A0 =C2=A0 =C2=A0 =C2=A0paparazzi-devel-request@nongnu.org

You can reach the person managing the list at
=C2=A0 =C2=A0 =C2=A0 =C2=A0paparazzi-devel-owner@nongnu.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Paparazzi-devel digest..."


Today's Topics:

=C2=A0 1. reply to "flight plan block activation from the =C2=A0 rc t= x (Pascal
=C2=A0 =C2=A0 =C2=A0Brisset)" (chris)
=C2=A0 2. New path instruction (Pascal Brisset)
=C2=A0 3. CGS Programing Language (Rui Costa)
=C2=A0 4. Fly with IMU for fix wing aircraft and helicopter?
=C2=A0 =C2=A0 =C2=A0(=3D?big5?B?s6IgZmx5aW5nIHBpZw=3D=3D?=3D)
=C2=A0 5. New Autopilot - Tiny v3 (Rui Costa)
=C2=A0 6. Re: Airframe debug problem,stop at ap.elf (Pascal Brisset)
=C2=A0 7. Re: questions on flight plan (Pascal Brisset)
=C2=A0 8. Re: Mark Button (Pascal Brisset)
=C2=A0 9. Re: throttle management in AUTO2 (Pascal Brisset)


----------------------------------------------------------------------

Message: 1
Date: Thu, 13 Aug 2009 20:28:24 +0300
From: chris <he= ndrixgr@gmail.com>
Subject: [Paparazzi-devel] reply to "flight plan block activation from=
=C2=A0 =C2=A0 =C2=A0 =C2=A0the =C2=A0 =C2=A0 rc tx (Pascal Brisset)"<= br> To: paparaz= zi-devel@nongnu.org
Message-ID: <4A844D38.6000706@gmail.com>
Content-Type: text/plain; charset=3DISO-8859-1; format=3Dflowed

Thank you Pascal That is exactly what i want.
I have a flight plan that the only thing it does is a photo run and it
includes
a Standby block.
I tested successfully an auto take off =C2=A0without the use of the transmi= tter
(i throw away the aircraft after running in order to achieve 11 km/h and enable the motor)
so i am searching for a way to eliminate the ground station for this simple=
flight plan.
I know that there are hidden danger in it but i test in remote areas and controled
areas.
Chris




------------------------------

Message: 2
Date: Thu, 13 Aug 2009 19:32:50 +0200
From: Pascal Brisset <pascal.brisset@free.fr>
Subject: [Paparazzi-devel] New path instruction
To: paparaz= zi-devel@nongnu.org
Message-ID: <4A844E42.6090605@free.fr>
Content-Type: text/plain; =C2=A0 =C2=A0 =C2=A0 charset=3DISO-8859-15; =C2= =A0 =C2=A0format=3Dflowed

Hi,

answer to an old request (I cannot find it): A <path/> instruction ha= s
been added to the flight plan language to fly over a list of waypoints.
It is simply preprocessed into a sequence of <go/> instructions. Exam= ple
in basic.xml:

=C2=A0 =C2=A0<block name=3D"Path 1,2,S1,S2,STDBY" strip_butto= n=3D"Path
(1,2,S1,S2,STDBY)" strip_icon=3D"path.png">
=C2=A0 =C2=A0 =C2=A0<path wpts=3D"1,2 S1"/>
=C2=A0 =C2=A0 =C2=A0<path wpts=3D"S1, S2 STDBY" approaching_t= ime=3D"1" pitch=3D"auto"
throttle=3D"0.4"/>
=C2=A0 =C2=A0 =C2=A0<deroute block=3D"Standby"/>
=C2=A0 =C2=A0</block>

The list separaror is the regular expression "[ \t,]+" (at least = one
space, tab or comma). Extra standard attributes are allowed.
The translation produces here

=C2=A0 =C2=A0 =C2=A0 =C2=A0<go from=3D"1" hmode=3D"route= " wp=3D"2" wpts=3D"1,2 S1" no=3D"0"/>=
=C2=A0 =C2=A0 =C2=A0 =C2=A0<go from=3D"2" hmode=3D"route= " wp=3D"S1" wpts=3D"1,2 S1" no=3D"1"/>= ;
=C2=A0 =C2=A0 =C2=A0 =C2=A0<go from=3D"S1" hmode=3D"rout= e" wp=3D"S2" approaching_time=3D"1"
throttle=3D"0.4" pitch=3D"auto" wpts=3D"S1, S2 STD= BY" no=3D"2"/>
=C2=A0 =C2=A0 =C2=A0 =C2=A0<go from=3D"S2" hmode=3D"rout= e" wp=3D"STDBY" approaching_time=3D"1"
throttle=3D"0.4" pitch=3D"auto" wpts=3D"S1, S2 STD= BY" no=3D"3"/>

and it is what you will see in the GCS.

--Pascal

PS: No, it is not possible to dynamically define the waypoints list from the GCS during the flight :-)




------------------------------

Message: 3
Date: Thu, 13 Aug 2009 17:40:51 +0000
From: Rui Costa <azoreanuav@gmail.com>
Subject: [Paparazzi-devel] CGS Programing Language
To: paparaz= zi-devel@nongnu.org
Message-ID:
=C2=A0 =C2=A0 =C2=A0 =C2=A0<4d39daa50908131040h11= 8b1bdei96b0dde5d99e1009@mail.gmail.com>
Content-Type: text/plain; charset=3D"iso-8859-1"

Hello all,


What's the programming language of the CGS? How can I modify and compil= e the
CGS?




Best regards
Rui Costa
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.gnu.org/p= ipermail/paparazzi-devel/attachments/20090813/0205a9cd/attachment.html<= br>
------------------------------

Message: 4
Date: Fri, 14 Aug 2009 08:28:49 +0000
From: =3D?big5?B?s6IgZmx5aW5nIHBpZw=3D=3D?=3D <idf2b@hotmail.com>
Subject: [Paparazzi-devel] Fly with IMU for fix wing aircraft and
=C2=A0 =C2=A0 =C2=A0 =C2=A0helicopter?
To: <pap= arazzi-devel@nongnu.org>
Message-ID: <BLU149-W50F92EBFC1348C75CBDC92F4020@phx.gbl>
Content-Type: text/plain; charset=3D"big5"


Hi there



=C2=A0I am in the process of buliding up the Booz IMU, and i was wonering,= does the current code allow to intergrate IMU to Tiny for fix wing and hel= icopter?



=C2=A0We will try to fly with our helipoter with IR sesnor today (it has i= nbuid simple stabilisation hardware from the toy company), so we are just l= ooking with using Tiny to control the PWM signal for coaxial heclicopter. = =C2=A0I am not sure it wil work, but we will try, i will let you guys know.=









Regards



=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Chen





_________________________________________________________________
=E7=94=A8=E9=83=A8=E8=90=BD=E6=A0=BC=E5=88=86=E4=BA=AB=E7=85=A7=E7=89=87=E3= =80=81=E5=BD=B1=E9=9F=B3=E3=80=81=E8=B6=A3=E5=91=B3=E5=B0=8F=E5=B7=A5=E5=85= =B7=E5=92=8C=E6=9C=80=E6=84=9B=E6=B8=85=E5=96=AE=EF=BC=8C=E7=9B=A1=E6=83=85= =E7=A7=80=E5=87=BA=E4=BD=A0=E8=87=AA=E5=B7=B1 =E2=80=94 Windows Live Spaces=
http://home.spaces.live.com/?showUnauth=3D1&lc=3D1028<= br> -------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.gnu.org/p= ipermail/paparazzi-devel/attachments/20090814/a722a16d/attachment.html<= br>
------------------------------

Message: 5
Date: Fri, 14 Aug 2009 08:38:32 +0000
From: Rui Costa <azoreanuav@gmail.com>
Subject: [Paparazzi-devel] New Autopilot - Tiny v3
To: paparaz= zi-devel@nongnu.org
Message-ID:
=C2=A0 =C2=A0 =C2=A0 =C2=A0<4d39daa50908140138of35= bbfeq607ef90c3fca785e@mail.gmail.com>
Content-Type: text/plain; charset=3D"iso-8859-1"

Hello all,


Let's talk about possible new features for the new Tiny. I think it'= ;s time
to make a new autopilot based on experience acumulated from the others Tiny=
boards.
We can discuss this new features by here, wiki, IRC channel or f=E9=8F=8Eum= .

*http:= //paparazzi.enac.fr/wiki/Tiny_v3* <paparazzi-devel@nongnu.org>

I will need some help with some new components and the implementation of th= e
software part.


Best regards
Rui Costa
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.gnu.org/p= ipermail/paparazzi-devel/attachments/20090814/7b2afd1f/attachment.html<= br>
------------------------------

Message: 6
Date: Fri, 14 Aug 2009 11:35:04 +0200
From: Pascal Brisset <pascal.brisset@free.fr>
Subject: Re: [Paparazzi-devel] Airframe debug problem,stop at ap.elf
To: paparaz= zi-devel@nongnu.org
Message-ID: <4A852FC8.3040801@free.fr>
Content-Type: text/plain; =C2=A0 =C2=A0 =C2=A0 charset=3DUTF-8; =C2=A0forma= t=3Dflowed

You have to keep this line (not related to gyro):

ap.srcs +=3D nav_survey_rectangle.c nav_line.c

--Pascal

=E8=9D=A1=E4=BA=A6=EF=BF=BD wrote:
> Hi,
> I had problem when trying to remove lines of Gyro from the airframe > file.Debuging always stopped at LD
> /home/mnw/paparazzi3/var/mnwAC/ap/ap.elf,I couldn't figure out why= .I'v
> put the airframe file here http://pastebin.com/m6cb0a486.
> Help me out.
>
> Thanks all.
> ----------------------------------------------------------------------= --
>
> _______________________________________________
> Paparazzi-devel mailing list
> Papara= zzi-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel
>





------------------------------

Message: 7
Date: Fri, 14 Aug 2009 11:50:24 +0200
From: Pascal Brisset <
pascal.brisset@free.fr>
Subject: Re: [Paparazzi-devel] questions on flight plan
To: paparaz= zi-devel@nongnu.org
Message-ID: <4A853360.3050205@free.fr>
Content-Type: text/plain; =C2=A0 =C2=A0 =C2=A0 charset=3DISO-8859-1; =C2=A0= =C2=A0 format=3Dflowed

Hi Steve,

there is an "old" feature using procedures:
http://paparazzi.enac.fr/wiki/Flight_Plans#Procedures
But it will require a reflash of your autopilot.

The NavSetGroundReferenceHere() function translates the waypoints around the current GPS location. It's easy to write a similar function to
do a rotation (for example around HOME). You only need a way to specify
the heading you want. You could use a specific waypoint. The procedure
would be:
=C2=A0- NavSetGroundReferenceHere()
=C2=A0- set a waypoint =C2=A0(XX)
=C2=A0- NavRotateAroundHOME(WP_XX)

hth

--Pascal



Steve Ross wrote:
> Most of the flight plans can be used in any places by using the
> relative coordinates of the waypoints to the HOME location, one thing<= br> > I don't understand is how people aligned the fields in the flight<= br> > plans to the new flying fields. Suppose I have the "versatile.htm= l" as
> my flight plan in mind and arrive at a new field and choose one
> location as my HOME waypoint and find a runway to take off. Do I have<= br> > to bring a *compass* to know the orientation of the field in the
> flight plan to the current field I arrive at? Otherwise, it's like= ly
> that my field will be a *rotation* of the field in the flight plan
> around the waypoint HOME. I may think that the other waypoints in the<= br> > flight plan are located within the actual field but in actuality some<= br> > of the waypoints are out of the boundary of the actual field due to > the wrong assumption of the *rotation* on the field in the flight
> plan. If I discover that my assumption is wrong after I arrive at that=
> field, is there any quick and easy way to rotate and create a new
> flight plan at the field? (One command that rotate all of the
> waypoints in the flight plan to allign with actual field around the > HOME?).
>
> Thanks a lot.
> ----------------------------------------------------------------------= --
>
> _______________________________________________
> Paparazzi-devel mailing list
> Papara= zzi-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel
>





------------------------------

Message: 8
Date: Fri, 14 Aug 2009 11:51:46 +0200
From: Pascal Brisset <
pascal.brisset@free.fr>
Subject: Re: [Paparazzi-devel] Mark Button
To: paparaz= zi-devel@nongnu.org
Message-ID: <4A8533B2.6080409@free.fr>
Content-Type: text/plain; =C2=A0 =C2=A0 =C2=A0 charset=3DISO-8859-1; =C2=A0= =C2=A0 format=3Dflowed

Daniel Bedenko wrote:
> Is there a way to activate the MARK button from the transmitter?

=C2=A0No, this is a GCS feature: the autopilot does not know anything about= it.

--Pascal

>
> Daniel Bedenko
> http://airsea.uc= sd.edu/
> ----------------------------------------------------------------------= --
>
> _______________________________________________
> Paparazzi-devel mailing list
> Papara= zzi-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel
>





------------------------------

Message: 9
Date: Fri, 14 Aug 2009 12:02:51 +0200
From: Pascal Brisset <
pascal.brisset@free.fr>
Subject: Re: [Paparazzi-devel] throttle management in AUTO2
To: paparaz= zi-devel@nongnu.org
Message-ID: <4A85364B.8060007@free.fr>
Content-Type: text/plain; =C2=A0 =C2=A0 =C2=A0 charset=3DISO-8859-1; =C2=A0= =C2=A0 format=3Dflowed

Hi,

not, there is no minimum throttle in AUTO2. You can hack main_ap.c (line 589), replacing

=C2=A0 =C2=A0 ap_state->commands[COMMAND_THROTTLE] =3D v_ctl_throttle_s= lewed;

by

=C2=A0 =C2=A0ap_state->commands[COMMAND_THROTTLE] =3D Min(MAX_PPRZ * MY_MIN_AUTO2_THROTTLE, v_ctl_throttle_slewed)

--Pascal

chris wrote:
> Hi.
> I have a hard time keeping the plane flying in a very difficult place<= br> > due to strong and very very
> turbulent wind area.
> Thermals are so strong that can crash the plane easily.
> Yesterday i fell in to a microburst that was there for 2 or 3 minutes<= br> > and then vanished.
> I almost lost the plane as it was sucked down at full throttle in
> MANUAL mode.
> Imagine seeing a plane flying straight at 60 -70 meters and suddenly > losing 50 meters without
> changing attitude, it just sunk and everybody there said that they
> have never experienced something like that again.
> Is there any way to increase the minimum throttle in auto2?
> I just don't want the plane to fly with anything lower than 60% > throttle except
> when descending.
> Chris
>
>
>
> _______________________________________________
> Paparazzi-devel mailing list
> Papara= zzi-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel





------------------------------

_______________________________________________
Paparazzi-devel mailing list
Paparazzi-d= evel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/paparazzi-devel

End of Paparazzi-devel Digest, Vol 65, Issue 22
***********************************************


--0016364c7c07d8d7f5047118660a-- From MAILER-DAEMON Fri Aug 14 10:16:40 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MbxaC-0000ZF-95 for mharc-paparazzi-devel@gnu.org; Fri, 14 Aug 2009 10:16:40 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MbxaA-0000Z7-NX for paparazzi-devel@nongnu.org; Fri, 14 Aug 2009 10:16:38 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mbxa6-0000Yl-4j for paparazzi-devel@nongnu.org; Fri, 14 Aug 2009 10:16:38 -0400 Received: from [199.232.76.173] (port=57061 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mbxa5-0000Ye-Uo for paparazzi-devel@nongnu.org; Fri, 14 Aug 2009 10:16:34 -0400 Received: from fmail1.hs-bremen.de ([194.94.24.14]:35041) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Mbxa5-0008QK-8Y for paparazzi-devel@nongnu.org; Fri, 14 Aug 2009 10:16:33 -0400 Received: from localhost (fmail1 [127.0.0.1]) by fmail1.hs-bremen.de (Postfix) with ESMTP id F12D432FAB for ; Fri, 14 Aug 2009 16:14:59 +0200 (CEST) X-Virus-Scanned: by amavisd-new at fmail1.hs-bremen.de Received: from fmail1.hs-bremen.de ([127.0.0.1]) by localhost (fmail1.hs-bremen.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fkUp7nfIRfI6 for ; Fri, 14 Aug 2009 16:14:52 +0200 (CEST) Received: from mail.hs-bremen.de (mail.hs-bremen.de [194.94.24.31]) by fmail1.hs-bremen.de (Postfix) with ESMTP id EF61332E88 for ; Fri, 14 Aug 2009 16:14:51 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by mail.hs-bremen.de (Postfix) with ESMTP id DC68F78C0A9 for ; Fri, 14 Aug 2009 16:14:51 +0200 (CEST) X-Virus-Scanned: by amavisd-new at mail.hs-bremen.de Received: from mail.hs-bremen.de ([127.0.0.1]) by localhost (mail.hs-bremen.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hob-YKnRggXY for ; Fri, 14 Aug 2009 16:14:51 +0200 (CEST) Received: from hs-bremen.de (p5B107258.dip.t-dialin.net [91.16.114.88]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.hs-bremen.de (Postfix) with ESMTP id 41BAB78C0C2 for ; Fri, 14 Aug 2009 16:14:51 +0200 (CEST) Message-ID: <4A8570F9.1020305@hs-bremen.de> Date: Fri, 14 Aug 2009 16:13:13 +0200 From: "Prof. Dr.-Ing. Heinrich Warmers" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; de-DE; rv:1.4) Gecko/20030619 Netscape/7.1 (ax) X-Accept-Language: de-de, de MIME-Version: 1.0 To: paparazzi-devel@nongnu.org Subject: Re: [Paparazzi-devel] New Autopilot - Tiny v3 References: <4d39daa50908140138of35bbfeq607ef90c3fca785e@mail.gmail.com> In-Reply-To: <4d39daa50908140138of35bbfeq607ef90c3fca785e@mail.gmail.com> Content-Type: multipart/alternative; boundary="------------060504030706070504060502" X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 3) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Aug 2009 14:16:38 -0000 This is a multi-part message in MIME format. --------------060504030706070504060502 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Hello, you can use the IMU form the HB-Autopilot and the HB-Autopilot MCU for=20 most of the points. http://www.akaflieg.hs-bremen.de/trac/akaflieg/wiki/airborne/hw/autopilot It is also possible to use the booz2_IMU_HB witch was made by pione and=20 John. We added a pressure sensor and a connection for a difference pressure sensor. Al the IMUs are use the spi bus and the eagle files are free to use=20 (GPL3). Since there is a new magnetic sensor the HMC5843 this sensor may spend=20 a lot of money (17$ to 60$). Best regards Heinrich Warmers=20 HMC5843 Rui Costa schrieb: > Hello all, > =20 > =20 > Let's talk about possible new features for the new Tiny. I think it's=20 > time to make a new autopilot based on experience acumulated from the=20 > others Tiny boards. > We can discuss this new features by here, wiki, IRC channel or f=F3rum. > =20 > http://paparazzi.enac.fr/wiki/Tiny_v3 > > I will need some help with some new components and the implementation=20 > of the software part. > =20 > > Best regards > Rui Costa > >------------------------------------------------------------------------ > >_______________________________________________ >Paparazzi-devel mailing list >Paparazzi-devel@nongnu.org >http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > =20 > --------------060504030706070504060502 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Hello,
you can use the IMU form the HB-Autopilot and the HB-Autopilot MCU for most of the points.
http://www.akaflieg.hs-bremen.de/trac/akaflieg/wiki/airborne/hw/autopilot
It is also possible to use the booz2_IMU_HB witch was made by pione and John. We added  a pressure
sensor and a connection for a difference  pressure sensor.
Al the IMUs are  use the spi bus and the eagle files are free to use (GPL3).
Since there is a new  magnetic sensor the HMC5843 this sensor may spend a lot of money
(17$ to 60$).
Best regards

Heinrich Warmers 

HMC5843




Rui Costa schrieb:
Hello all,
 
 
Let's talk about possible new features for the new Tiny. I think it's time to make a new autopilot based on experience acumulated from the others Tiny boards.
We can discuss this new features by here, wiki, IRC channel or fórum.
 

I will need some help with some new components and the implementation of the software part.
 

Best regards
Rui Costa

_______________________________________________ Paparazzi-devel mailing list Paparazzi-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/paparazzi-devel
--------------060504030706070504060502-- From MAILER-DAEMON Fri Aug 14 10:27:53 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Mbxl3-0006bJ-1G for mharc-paparazzi-devel@gnu.org; Fri, 14 Aug 2009 10:27:53 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mbxl1-0006Zp-J5 for paparazzi-devel@nongnu.org; Fri, 14 Aug 2009 10:27:51 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mbxkw-0006UP-FN for paparazzi-devel@nongnu.org; Fri, 14 Aug 2009 10:27:51 -0400 Received: from [199.232.76.173] (port=55860 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mbxkw-0006UG-7z for paparazzi-devel@nongnu.org; Fri, 14 Aug 2009 10:27:46 -0400 Received: from mail-bw0-f220.google.com ([209.85.218.220]:34560) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Mbxkv-0002ZA-J5 for paparazzi-devel@nongnu.org; Fri, 14 Aug 2009 10:27:45 -0400 Received: by bwz20 with SMTP id 20so1865491bwz.9 for ; Fri, 14 Aug 2009 07:27:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=lP9ikWBFs6wiJ7SSBsaAqTOtdEbCwQ1i0qYC6UILAFQ=; b=qJsL0OsvljIwFMH9WOnmzZo6A2aLeZHcgD4jUk8KeMwCZltpqSo/V2PcJKcicByAol sKx31QWnuUQbTvj6sRoqN1zNGGwzavHGfCfs5OhtGxZl+QNRi9fMG0QSDk27SqjLOYT/ AfS0F/CzYV/idjFHcaGz64h77IRvslkNHslIo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=iEpSscpYLnXncGjaf/OWVYKq1Zm8iIf0wzYOrZnF2Z9eX9qsKFisdqTaXQlfVQFWtF y/WHk+Qusm5m/N4301RB7Is1l6e79NJApreoTzns+s4jHCnuekuULVFz/1Dp/sc/VSjF kizizV8j/w0ETtAmGFg5VKMg3zDn1iWHaPNU0= MIME-Version: 1.0 Received: by 10.204.72.15 with SMTP id k15mr1224264bkj.39.1250260064552; Fri, 14 Aug 2009 07:27:44 -0700 (PDT) In-Reply-To: <4A8570F9.1020305@hs-bremen.de> References: <4d39daa50908140138of35bbfeq607ef90c3fca785e@mail.gmail.com> <4A8570F9.1020305@hs-bremen.de> Date: Fri, 14 Aug 2009 14:27:44 +0000 Message-ID: <4d39daa50908140727g15b7b8a6ga6844d7e941da89d@mail.gmail.com> Subject: Re: [Paparazzi-devel] New Autopilot - Tiny v3 From: Rui Costa To: paparazzi-devel@nongnu.org Content-Type: multipart/alternative; boundary=001636c5be2d0645bd04711adb17 X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Aug 2009 14:27:51 -0000 --001636c5be2d0645bd04711adb17 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hello, Thank you for the reply. I'm studing the HB-Autopilot to make the base for the tiny v3. I have a lot of things to ask. Have the e-mail contact of Andreas Dei? Best regards Rui Costa On Fri, Aug 14, 2009 at 2:13 PM, Prof. Dr.-Ing. Heinrich Warmers < hwarmers@hs-bremen.de> wrote: > Hello, > you can use the IMU form the HB-Autopilot and the HB-Autopilot MCU for mo= st > of the points. > http://www.akaflieg.hs-bremen.de/trac/akaflieg/wiki/airborne/hw/autopilot > It is also possible to use the booz2_IMU_HB witch was made by pione and > John. We added a pressure > sensor and a connection for a difference pressure sensor. > Al the IMUs are use the spi bus and the eagle files are free to use > (GPL3). > Since there is a new magnetic sensor the HMC5843 this sensor may spend a > lot of money > (17$ to 60$). > Best regards > > Heinrich Warmers > HMC5843 > > > Rui Costa schrieb: > > Hello all, > > > Let's talk about possible new features for the new Tiny. I think it's tim= e > to make a new autopilot based on experience acumulated from the others Ti= ny > boards. > We can discuss this new features by here, wiki, IRC channel or f=F3rum. > > *http://paparazzi.enac.fr/wiki/Tiny_v3* > > I will need some help with some new components and the implementation of > the software part. > > > Best regards > Rui Costa > > ------------------------------ > > _______________________________________________ > Paparazzi-devel mailing listPaparazzi-devel@nongnu.orghttp://lists.nongnu= .org/mailman/listinfo/paparazzi-devel > > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > > --=20 Rui Costa www.azoreanuav.com --001636c5be2d0645bd04711adb17 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hello,
=A0
Thank you for the reply. I'm studing the HB-Autopilot to make the = base for the tiny v3. I have a lot of things to ask. Have the e-mail contac= t of Andreas Dei?
=A0
=A0
Best regards
Rui Costa
On Fri, Aug 14, 2009 at 2:13 PM, Prof. Dr.-Ing. = Heinrich Warmers <hwarmers@hs-bremen.de> wrote:
Hello,
you can use the IMU for= m the HB-Autopilot and the HB-Autopilot MCU for most of the points.
http://www.akaflieg.hs-bremen.de/trac/akaflieg/wik= i/airborne/hw/autopilot
It is also possible to use the booz2_IMU_HB witch was made by pione and Joh= n. We added=A0 a pressure
sensor and a connection for a difference=A0 p= ressure sensor.
Al the IMUs are=A0 use the spi bus and the eagle files = are free to use (GPL3).
Since there is a new=A0 magnetic sensor the HMC5843 this sensor may spend a= lot of money
(17$ to 60$).
Best regards

Heinrich Warmers=A0 <= br>

HMC5843




Rui Costa schrieb:
Hello all,
=A0
=A0
Let's talk about possible new features for the new Tiny. I think i= t's time to make a new autopilot based on experience acumulated from th= e others Tiny boards.
We can discuss this new features by here, wiki, IRC channel or f=F3rum= .
=A0

I will need some help with some new components and t= he implementation of the software part.
=A0

Best regards
Rui Costa

_______________________________________________ Paparazzi-devel mailing list Paparazzi-d= evel@nongnu.org http://lists.nongnu.org/mailman/listinfo/paparazzi-devel

____________________________________________= ___
Paparazzi-devel mailing list
Paparazzi-devel@nongnu.org
h= ttp://lists.nongnu.org/mailman/listinfo/paparazzi-devel




--
Rui Costa
www.azoreanuav.com
--001636c5be2d0645bd04711adb17-- From MAILER-DAEMON Fri Aug 14 14:18:49 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Mc1MX-0006tg-BB for mharc-paparazzi-devel@gnu.org; Fri, 14 Aug 2009 14:18:49 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mc1MV-0006ss-GP for paparazzi-devel@nongnu.org; Fri, 14 Aug 2009 14:18:47 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mc1MQ-0006rt-F3 for paparazzi-devel@nongnu.org; Fri, 14 Aug 2009 14:18:46 -0400 Received: from [199.232.76.173] (port=43047 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mc1MQ-0006rq-A4 for paparazzi-devel@nongnu.org; Fri, 14 Aug 2009 14:18:42 -0400 Received: from fmail1.hs-bremen.de ([194.94.24.14]:39756) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Mc1MP-0001RR-9Q for paparazzi-devel@nongnu.org; Fri, 14 Aug 2009 14:18:42 -0400 Received: from localhost (fmail1 [127.0.0.1]) by fmail1.hs-bremen.de (Postfix) with ESMTP id 62C3F32F6A for ; Fri, 14 Aug 2009 20:18:40 +0200 (CEST) X-Virus-Scanned: by amavisd-new at fmail1.hs-bremen.de Received: from fmail1.hs-bremen.de ([127.0.0.1]) by localhost (fmail1.hs-bremen.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fq5PN3pgiMyo for ; Fri, 14 Aug 2009 20:18:32 +0200 (CEST) Received: from mail.hs-bremen.de (mail.hs-bremen.de [194.94.24.31]) by fmail1.hs-bremen.de (Postfix) with ESMTP id 72AC432E59 for ; Fri, 14 Aug 2009 20:18:32 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by mail.hs-bremen.de (Postfix) with ESMTP id 6208978C08E for ; Fri, 14 Aug 2009 20:18:32 +0200 (CEST) X-Virus-Scanned: by amavisd-new at mail.hs-bremen.de Received: from mail.hs-bremen.de ([127.0.0.1]) by localhost (mail.hs-bremen.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 81Z+WBG+PwKT for ; Fri, 14 Aug 2009 20:18:32 +0200 (CEST) Received: from hs-bremen.de (p5B107258.dip.t-dialin.net [91.16.114.88]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.hs-bremen.de (Postfix) with ESMTP id DFD5F78C08B for ; Fri, 14 Aug 2009 20:18:31 +0200 (CEST) Message-ID: <4A85AA1E.1040309@hs-bremen.de> Date: Fri, 14 Aug 2009 20:17:02 +0200 From: "Prof. Dr.-Ing. Heinrich Warmers" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; de-DE; rv:1.4) Gecko/20030619 Netscape/7.1 (ax) X-Accept-Language: de-de, de MIME-Version: 1.0 To: paparazzi-devel@nongnu.org Subject: Re: [Paparazzi-devel] Andreas Dei E-mail Contact References: <4d39daa50908110045t23cc4afcwd7fb6d0d8429c85a@mail.gmail.com> In-Reply-To: <4d39daa50908110045t23cc4afcwd7fb6d0d8429c85a@mail.gmail.com> Content-Type: multipart/alternative; boundary="------------060808060005010900050401" X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 3) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Aug 2009 18:18:47 -0000 This is a multi-part message in MIME format. --------------060808060005010900050401 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Dear Rui Costa, his mail address is: andreas.dei@gmx.de If you have questions for the filter ask the students how work with it. Best regards Heinrich Warmers Rui Costa schrieb: > Hello, > > I would like to talk with Andreas Dei. What's your e-mail address and > nickname on IRC? > > Best Regards > Rui Costa > www.azoreanuav.com > >------------------------------------------------------------------------ > >_______________________________________________ >Paparazzi-devel mailing list >Paparazzi-devel@nongnu.org >http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > > --------------060808060005010900050401 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit
Dear Rui Costa,
his mail  address is:  andreas.dei@gmx.de

If you have questions for the filter ask the students how work with it.
Best  regards

Heinrich Warmers


Rui Costa schrieb:
Hello,
 
I would like to talk with Andreas Dei. What's your e-mail address and nickname on IRC?

Best Regards
Rui Costa
www.azoreanuav.com

_______________________________________________ Paparazzi-devel mailing list Paparazzi-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/paparazzi-devel
--------------060808060005010900050401-- From MAILER-DAEMON Fri Aug 14 17:08:45 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Mc40z-0001nn-Ps for mharc-paparazzi-devel@gnu.org; Fri, 14 Aug 2009 17:08:45 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mc40y-0001ms-3L for paparazzi-devel@nongnu.org; Fri, 14 Aug 2009 17:08:44 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mc40t-0001j0-31 for paparazzi-devel@nongnu.org; Fri, 14 Aug 2009 17:08:43 -0400 Received: from [199.232.76.173] (port=41447 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mc40s-0001ik-RN for paparazzi-devel@nongnu.org; Fri, 14 Aug 2009 17:08:38 -0400 Received: from basicbox10.server-home.net ([195.137.212.35]:57556) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Mc40s-0001dc-7a for paparazzi-devel@nongnu.org; Fri, 14 Aug 2009 17:08:38 -0400 Received: by basicbox10.server-home.net (Postfix, from userid 1141) id 587DAC85163; Fri, 14 Aug 2009 23:08:39 +0200 (CEST) To: paparazzi-devel@nongnu.org From: martin@pfump.org X-Priority: 3 Importance: Normal X-MSMail-Priority: Normal X-MimeOLE: Produced by Confixx WebMail X-Mailer: Confixx WebMail (like SquirrelMail) Cc: MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <20090814210839.587DAC85163@basicbox10.server-home.net> Date: Fri, 14 Aug 2009 23:08:39 +0200 (CEST) X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 3) Subject: [Paparazzi-devel] data logger, gpsd X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Aug 2009 21:08:44 -0000 Hi, there is some documentation for the on-board SD card data logger available. http://paparazzi.enac.fr/wiki/Data_Logger The GPSd tool exists for a while already - allows to display an external gps position on the gcs (e.g. from a Bluetooth gps mouse). http://paparazzi.enac.fr/wiki/GPSd_position Martin From MAILER-DAEMON Fri Aug 14 23:47:30 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1McAEr-0000up-Qs for mharc-paparazzi-devel@gnu.org; Fri, 14 Aug 2009 23:47:29 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1McAEq-0000ue-A7 for paparazzi-devel@nongnu.org; Fri, 14 Aug 2009 23:47:28 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1McAEm-0000uG-Tp for paparazzi-devel@nongnu.org; Fri, 14 Aug 2009 23:47:27 -0400 Received: from [199.232.76.173] (port=56555 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1McAEm-0000uD-Kc for paparazzi-devel@nongnu.org; Fri, 14 Aug 2009 23:47:24 -0400 Received: from smtpoutwbe04.prod.mesa1.secureserver.net ([208.109.78.206]:47696) by monty-python.gnu.org with smtp (Exim 4.60) (envelope-from ) id 1McAEm-0008DG-2R for paparazzi-devel@nongnu.org; Fri, 14 Aug 2009 23:47:24 -0400 Received: (qmail 22079 invoked from network); 15 Aug 2009 03:47:17 -0000 Received: from unknown (HELO p3plgemwbe01-04.prod.phx3.secureserver.net) (72.167.218.4) by smtpoutwbe04.prod.mesa1.secureserver.net with SMTP; 15 Aug 2009 03:47:15 -0000 Received: (qmail 3082 invoked by uid 99); 15 Aug 2009 03:47:15 -0000 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="utf-8" X-Originating-IP: 70.176.119.64 User-Agent: Web-Based Email 5.1.7 Message-Id: <20090814204715.e412a968f7f3915fb4f3361627e3fef7.137d8a414a.wbe@email01.secureserver.net> From: akochevar@miraterre.com To: paparazzi-devel@nongnu.org Subject: RE: [Paparazzi-devel] New Autopilot - Tiny v3 Date: Fri, 14 Aug 2009 20:47:15 -0700 Mime-Version: 1.0 X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.4-2.6 X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Aug 2009 03:47:29 -0000 Just a note for everyone reading.

The IMU would only be useful= if code existed to calculate the euler angles for a fixed wing vehicle typ= e.  At present the code doesnt exist(to my knowledge anyways).  <= br>
AJ

-------- Original Message --------
Subject: Re: [Paparazzi-devel] New Autopilot - Tiny v3
From: Rui Costa <azoreanuav@gmail.com>
Date: Fri, August 14, 2009 7:27 am
To: paparazzi-devel@nongnu.org

Hello,
 
Thank you for the reply. I'm studi= ng the HB-Autopilot to make the base for the tiny v3. I have a lot of thing= s to ask. Have the e-mail contact of Andreas Dei?
 
<= div> 
Best regards
Rui Costa
On Fri, Aug 14, 2009 at 2:13 PM, Prof. Dr.-Ing. Heinrich = Warmers <hwarmers@hs-brem= en.de> wrote:
Hello,
you can= use the IMU form the HB-Autopilot and the HB-Autopilot MCU for most of the= points.
http://www.akaflieg.hs= -bremen.de/trac/akaflieg/wiki/airborne/hw/autopilot
It is also poss= ible to use the booz2_IMU_HB witch was made by pione and John. We added&nbs= p; a pressure
sensor and a connection for a difference  pressure s= ensor.
Al the IMUs are  use the spi bus and the eagle files are fr= ee to use (GPL3).
Since there is a new  magnetic sensor the HMC58= 43 this sensor may spend a lot of money
(17$ to 60$).
Best regards
Heinrich Warmers 

HMC5843




Rui Costa schr= ieb:
Hello a= ll,
 
 
Let's talk about possibl= e new features for the new Tiny. I think it's time to make a new autopilot = based on experience acumulated from the others Tiny boards.
We c= an discuss this new features by here, wiki, IRC channel or f=C3=B3rum.
 
http://paparazzi.enac.fr/wiki/Tiny_v3

I will need some help with some new components = and the implementation of the software part.
 

Bes= t regards
Rui Costa

_______________________________________________ Paparazzi-devel mailing list Paparazzi-devel@nongnu.org<= /a> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel

____________________________________________= ___
Paparazzi-devel mailing list
Paparazzi-devel@nongnu.org
http://lists.nongnu.or= g/mailman/listinfo/paparazzi-devel




--
Rui Costa
www.= azoreanuav.com

_______________________________________________<= br> Paparazzi-devel mailing list
Paparazzi-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/paparazzi-devel
From MAILER-DAEMON Sat Aug 15 07:34:59 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1McHXH-0000ad-6O for mharc-paparazzi-devel@gnu.org; Sat, 15 Aug 2009 07:34:59 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1McHXE-0000aY-8M for paparazzi-devel@nongnu.org; Sat, 15 Aug 2009 07:34:56 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1McHX8-0000aD-Hn for paparazzi-devel@nongnu.org; Sat, 15 Aug 2009 07:34:54 -0400 Received: from [199.232.76.173] (port=38365 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1McHX8-0000a2-CF for paparazzi-devel@nongnu.org; Sat, 15 Aug 2009 07:34:50 -0400 Received: from mx20.gnu.org ([199.232.41.8]:58663) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1McHX7-0008NH-Rd for paparazzi-devel@nongnu.org; Sat, 15 Aug 2009 07:34:50 -0400 Received: from mail-bw0-f220.google.com ([209.85.218.220]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1McHX5-0006bW-LM for paparazzi-devel@nongnu.org; Sat, 15 Aug 2009 07:34:48 -0400 Received: by bwz20 with SMTP id 20so2454479bwz.9 for ; Sat, 15 Aug 2009 04:34:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type; bh=Kqiv3PPX9FzBVup94cRTD+u4f0QTmX1823IelI9KmsA=; b=se/PZFEeAMghxsZKoTXOdie+op2pupyJymZSscC4Wv9t6qDwrEIB/WRHlU0vK84kN+ SvpuSQnLxa2+QTUn9AI4C+7MZVPibzaroU+2h2tJgBOFeptD5SmjIILljfDOO8tdrmL6 wPnIaW6GNZxebQ7KKLnZ3Hggu510jhrh0xSug= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=t+mWFrYUN3TPM44Iu9enV3fwjBi4ZxR18uBJt4/mByToTK8jXkkCr3oY+aFZSUSJeV h8YSWBlaWfjYCrTCx48SUajRf+a8wydqXOvxpvcojgNPOGOQk5DBA5nr70Ovi6qYDlgb P4N2VZzFNtdcxlWEQ1j8fvyaW3J7dg09yHIx0= MIME-Version: 1.0 Sender: adam.spence@gmail.com Received: by 10.204.15.152 with SMTP id k24mr1636896bka.83.1250336083817; Sat, 15 Aug 2009 04:34:43 -0700 (PDT) In-Reply-To: <20090814204715.e412a968f7f3915fb4f3361627e3fef7.137d8a414a.wbe@email01.secureserver.net> References: <20090814204715.e412a968f7f3915fb4f3361627e3fef7.137d8a414a.wbe@email01.secureserver.net> Date: Sat, 15 Aug 2009 12:34:43 +0100 X-Google-Sender-Auth: 2c63b622b8bd8cbf Message-ID: Subject: Re: [Paparazzi-devel] New Autopilot - Tiny v3 From: Adam Spence <4x4Ninja@gmail.com> To: paparazzi-devel@nongnu.org Content-Type: multipart/alternative; boundary=00032555bd0620340204712c8e27 X-Detected-Operating-System: by mx20.gnu.org: GNU/Linux 2.6 (newer, 2) X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6, seldom 2.4 (older, 4) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Aug 2009 11:34:56 -0000 --00032555bd0620340204712c8e27 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Google translation isn't always the best, are there any English translation= s of the project? I've tried to download the pdf file but it requires a login for the trac project, I can't seem to find a registration page? 2009/8/15 > Just a note for everyone reading. > > The IMU would only be useful if code existed to calculate the euler angle= s > for a fixed wing vehicle type. At present the code doesnt exist(to my > knowledge anyways). > > AJ > > > -------- Original Message -------- > Subject: Re: [Paparazzi-devel] New Autopilot - Tiny v3 > From: Rui Costa > Date: Fri, August 14, 2009 7:27 am > To: paparazzi-devel@nongnu.org > > Hello, > > Thank you for the reply. I'm studing the HB-Autopilot to make the base fo= r > the tiny v3. I have a lot of things to ask. Have the e-mail contact of > Andreas Dei? > > > Best regards > Rui Costa > On Fri, Aug 14, 2009 at 2:13 PM, Prof. Dr.-Ing. Heinrich Warmers < > hwarmers@hs-bremen.de> wrote: > >> Hello, >> you can use the IMU form the HB-Autopilot and the HB-Autopilot MCU for >> most of the points. >> http://www.akaflieg.hs-bremen.de/trac/akaflieg/wiki/airborne/hw/autopilo= t >> It is also possible to use the booz2_IMU_HB witch was made by pione and >> John. We added a pressure >> sensor and a connection for a difference pressure sensor. >> Al the IMUs are use the spi bus and the eagle files are free to use >> (GPL3). >> Since there is a new magnetic sensor the HMC5843 this sensor may spend = a >> lot of money >> (17$ to 60$). >> Best regards >> >> Heinrich Warmers >> HMC5843 >> >> >> Rui Costa schrieb: >> >> Hello all, >> >> >> Let's talk about possible new features for the new Tiny. I think it's ti= me >> to make a new autopilot based on experience acumulated from the others T= iny >> boards. >> We can discuss this new features by here, wiki, IRC channel or f=F3rum. >> >> *http://paparazzi.enac.fr/wiki/Tiny_v3* >> >> I will need some help with some new components and the implementation of >> the software part. >> >> >> Best regards >> Rui Costa >> >> ------------------------------ >> >> _______________________________________________ >> Paparazzi-devel mailing listPaparazzi-devel@nongnu.orghttp://lists.nongn= u.org/mailman/listinfo/paparazzi-devel >> >> >> _______________________________________________ >> Paparazzi-devel mailing list >> Paparazzi-devel@nongnu.org >> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel >> >> > > > -- > Rui Costa > www.azoreanuav.com > ------------------------------ > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > > --00032555bd0620340204712c8e27 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Google translation isn't always the best, are there any English transla= tions of the project?

I've tried to download the pdf= file but it requires a login for the trac project, I can't seem to fin= d a registration page?

2009/8/15 <akochevar@miraterre.com>
<= blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px= #ccc solid;padding-left:1ex;">
Just = a note for everyone reading.

The IMU would only be useful if code e= xisted to calculate the euler angles for a fixed wing vehicle type.=A0 At p= resent the code doesnt exist(to my knowledge anyways).=A0

AJ


-------- Original Message --------
Subject: Re: [Paparazzi-devel] New Autopilot - Tiny v3
From: Rui Costa <azoreanuav@gmail.com>
Date: Fri, August 14, 2009 7:27 am
To: paparaz= zi-devel@nongnu.org

Hello,
=A0
Thank you for the reply. I'm stud= ing the HB-Autopilot to make the base for the tiny v3. I have a lot of thin= gs to ask. Have the e-mail contact of Andreas Dei?
=A0
=A0
Best regards
Rui Costa
On Fri, Aug 14, 2009 at 2:13 PM, Prof. Dr.-Ing. Heinrich Warmers= <hwarmers@hs-bremen.de> wrote:
Hello,
you can use the IMU form the HB-Autopilot an= d the HB-Autopilot MCU for most of the points.
http://www.akaflieg.hs-bremen.de/trac/akaflieg= /wiki/airborne/hw/autopilot
It is also possible to use the booz2_IM= U_HB witch was made by pione and John. We added=A0 a pressure
sensor and a connection for a difference=A0 pressure sensor.
Al the IMU= s are=A0 use the spi bus and the eagle files are free to use (GPL3).
S= ince there is a new=A0 magnetic sensor the HMC5843 this sensor may spend a = lot of money
(17$ to 60$).
Best regards

Heinrich Warmers=A0

HMC5843


Rui Costa schrieb:
<= div>
Hello all,
=A0
=A0
Let&#= 39;s talk about possible new features for the new Tiny. I think it's ti= me to make a new autopilot based on experience acumulated from the others T= iny boards.
We can discuss this new features by here, wiki, IRC channel or f=F3ru= m.
=A0

I will need some help with some new components and = the implementation of the software part.
=A0

Best regar= ds
Rui Costa


_______________________________________________ Paparazzi-devel mailing list Paparazzi-d= evel@nongnu.org http://lists.nongnu.org/mailman/listinfo/paparazzi-devel

____________________________________________= ___
Paparazzi-devel mailing list
Paparazzi-devel@nongnu.org
h= ttp://lists.nongnu.org/mailman/listinfo/paparazzi-devel




--
Rui Co= sta
www.azorean= uav.com

_______________________________________________
Paparazzi-devel mailing list
Paparazzi-d= evel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/paparazzi-devel

_______________________________________________
Paparazzi-devel mailing list
Paparazzi-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/paparazzi-devel

--00032555bd0620340204712c8e27-- From MAILER-DAEMON Sat Aug 15 17:51:00 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1McR9Q-0001Db-20 for mharc-paparazzi-devel@gnu.org; Sat, 15 Aug 2009 17:51:00 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1McR9O-0001DW-NJ for paparazzi-devel@nongnu.org; Sat, 15 Aug 2009 17:50:58 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1McR9J-0001DK-3y for paparazzi-devel@nongnu.org; Sat, 15 Aug 2009 17:50:57 -0400 Received: from [199.232.76.173] (port=45481 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1McR9I-0001DH-UB for paparazzi-devel@nongnu.org; Sat, 15 Aug 2009 17:50:52 -0400 Received: from mail-fx0-f206.google.com ([209.85.220.206]:39441) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1McR9I-00059H-6P for paparazzi-devel@nongnu.org; Sat, 15 Aug 2009 17:50:52 -0400 Received: by fxm2 with SMTP id 2so1773314fxm.28 for ; Sat, 15 Aug 2009 14:50:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=KjGNid4MF3pSP1lVqnXKsfWziyhku/pGn683elxm540=; b=K+ia8Gz765czg3qWneElmY4UhlLC0DJr1uEa4n21as14SSWTtaft0wZYFsPaCp/45L ASqfURc9quyjMAtZ2P3nf2jiZEDA+T89L5ei7G+u5AZvjGMchQNE62Fai4n3J6uVs9AG EDGkhkMMG4yRbqlFOIi9HHBQN5ebjb/WKG464= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=vM/oo8wwN0AVS6D6ccq59GSl9dLszwQCM+98Acnun8XedAYRCCz77WhExlZscE7jSW 48XGCbjMJ8ExuXqkK3zZjY1xP1WpZGNRwfn6edX9Tae5CYlcz0kqpwTSzYFkDdODFvBA cbpk5w3R5FT1Tr2Lz1DYL+NWwe0/XBOrMkKeA= MIME-Version: 1.0 Received: by 10.204.156.217 with SMTP id y25mr1804207bkw.182.1250373046656; Sat, 15 Aug 2009 14:50:46 -0700 (PDT) In-Reply-To: <20090814204715.e412a968f7f3915fb4f3361627e3fef7.137d8a414a.wbe@email01.secureserver.net> References: <20090814204715.e412a968f7f3915fb4f3361627e3fef7.137d8a414a.wbe@email01.secureserver.net> Date: Sat, 15 Aug 2009 21:50:46 +0000 Message-ID: <4d39daa50908151450y2b2720c8l6f620eabe52b6b92@mail.gmail.com> Subject: Re: [Paparazzi-devel] New Autopilot - Tiny v3 From: Rui Costa To: paparazzi-devel@nongnu.org Content-Type: multipart/alternative; boundary=0015175cdec6485f88047135296f X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Aug 2009 21:50:59 -0000 --0015175cdec6485f88047135296f Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I think the HB_Autopilot calculate the euler angles. We just need to deal with that information instead of IR sensors. Another thing. How can we detect that the tiny freezed with for example an ATMEGA328? What should the ATMEGA detect to consider that tiny have problems? And how should we reset the tiny? Power off and then on? Regards Rui Costa On Sat, Aug 15, 2009 at 3:47 AM, wrote: > Just a note for everyone reading. > > The IMU would only be useful if code existed to calculate the euler angle= s > for a fixed wing vehicle type. At present the code doesnt exist(to my > knowledge anyways). > > AJ > > > -------- Original Message -------- > Subject: Re: [Paparazzi-devel] New Autopilot - Tiny v3 > From: Rui Costa > Date: Fri, August 14, 2009 7:27 am > To: paparazzi-devel@nongnu.org > > Hello, > > Thank you for the reply. I'm studing the HB-Autopilot to make the base fo= r > the tiny v3. I have a lot of things to ask. Have the e-mail contact of > Andreas Dei? > > > Best regards > Rui Costa > On Fri, Aug 14, 2009 at 2:13 PM, Prof. Dr.-Ing. Heinrich Warmers < > hwarmers@hs-bremen.de> wrote: > >> Hello, >> you can use the IMU form the HB-Autopilot and the HB-Autopilot MCU for >> most of the points. >> http://www.akaflieg.hs-bremen.de/trac/akaflieg/wiki/airborne/hw/autopilo= t >> It is also possible to use the booz2_IMU_HB witch was made by pione and >> John. We added a pressure >> sensor and a connection for a difference pressure sensor. >> Al the IMUs are use the spi bus and the eagle files are free to use >> (GPL3). >> Since there is a new magnetic sensor the HMC5843 this sensor may spend = a >> lot of money >> (17$ to 60$). >> Best regards >> >> Heinrich Warmers >> HMC5843 >> >> >> Rui Costa schrieb: >> >> Hello all, >> >> >> Let's talk about possible new features for the new Tiny. I think it's ti= me >> to make a new autopilot based on experience acumulated from the others T= iny >> boards. >> We can discuss this new features by here, wiki, IRC channel or f=F3rum. >> >> *http://paparazzi.enac.fr/wiki/Tiny_v3* >> >> I will need some help with some new components and the implementation of >> the software part. >> >> >> Best regards >> Rui Costa >> >> ------------------------------ >> >> _______________________________________________ >> Paparazzi-devel mailing listPaparazzi-devel@nongnu.orghttp://lists.nongn= u.org/mailman/listinfo/paparazzi-devel >> >> >> _______________________________________________ >> Paparazzi-devel mailing list >> Paparazzi-devel@nongnu.org >> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel >> >> > > > -- > Rui Costa > www.azoreanuav.com > ------------------------------ > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > > --=20 Rui Costa www.azoreanuav.com --0015175cdec6485f88047135296f Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
I think the HB_Autopilot calculate the euler angles. We just need to d= eal with that information instead of IR sensors.
=A0
Another thing.=A0How can we detect that the tiny freezed with for exam= ple an ATMEGA328?
What should=A0the ATMEGA detect to consider that tiny = have problems?
And how should we reset the tiny? Power off and then on?
=A0
=A0
Regards
Rui Costa

On Sat, Aug 15, 2009 at 3:47 AM, <akochevar@miraterre.com> wrote:
= Just a note for everyone reading.

The IMU would only be useful if c= ode existed to calculate the euler angles for a fixed wing vehicle type.=A0= At present the code doesnt exist(to my knowledge anyways).=A0

AJ=20


-------- Original Message --------
Subject: Re: [Paparazzi-devel] N= ew Autopilot - Tiny v3
From: Rui Costa <
azoreanuav@gmail.com>
Date: Fri, Aug= ust 14, 2009 7:27 am
To: paparaz= zi-devel@nongnu.org

Hello,
=A0
Thank you for the reply. I'm studing the HB-Autopilot to make the = base for the tiny v3. I have a lot of things to ask. Have the e-mail contac= t of Andreas Dei?
=A0
=A0
Best regards
Rui Costa
On Fri, Aug 14, 2009 at 2:13 PM, Prof. Dr.-Ing. = Heinrich Warmers <hwarmers@hs-bremen.de> wrote:
Hello,
you can use the IMU for= m the HB-Autopilot and the HB-Autopilot MCU for most of the points.
http://www.akaflieg.hs-bremen.de/trac/akaflieg/wik= i/airborne/hw/autopilot
It is also possible to use the booz2_IMU_HB witch was made by pione and Joh= n. We added=A0 a pressure
sensor and a connection for a difference=A0 p= ressure sensor.
Al the IMUs are=A0 use the spi bus and the eagle files = are free to use (GPL3).
Since there is a new=A0 magnetic sensor the HMC5843 this sensor may spend a= lot of money
(17$ to 60$).
Best regards

Heinrich Warmers=A0 <= br>

HMC5843




Rui Costa schrieb:
Hello all,
=A0
=A0
Let's talk about possible new features for the new Tiny. I think i= t's time to make a new autopilot based on experience acumulated from th= e others Tiny boards.
We can discuss this new features by here, wiki, IRC channel or f=F3rum= .
=A0

I will need some help with some new components and t= he implementation of the software part.
=A0

Best regards
Rui Costa

_______________________________________________ Paparazzi-devel mailing list Paparazzi-d= evel@nongnu.org http://lists.nongnu.org/mailman/listinfo/paparazzi-devel

____________________________________________= ___
Paparazzi-devel mailing list
Paparazzi-devel@nongnu.org
h= ttp://lists.nongnu.org/mailman/listinfo/paparazzi-devel




--
Rui Costa
www.azoreanuav.com

_______________________________________________
Paparazzi-devel mailing = list
Pap= arazzi-devel@nongnu.org
http://lists.nongnu.org/mailman/= listinfo/paparazzi-devel

___________________________= ____________________
Paparazzi-devel mailing list
Paparazzi-devel@nongnu.org
ht= tp://lists.nongnu.org/mailman/listinfo/paparazzi-devel




--
Rui Costa
ww= w.azoreanuav.com
--0015175cdec6485f88047135296f-- From MAILER-DAEMON Sun Aug 16 05:03:30 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1McbeE-0005wr-5V for mharc-paparazzi-devel@gnu.org; Sun, 16 Aug 2009 05:03:30 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1McbeC-0005wh-Ri for paparazzi-devel@nongnu.org; Sun, 16 Aug 2009 05:03:28 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mcbe8-0005wU-RU for paparazzi-devel@nongnu.org; Sun, 16 Aug 2009 05:03:28 -0400 Received: from [199.232.76.173] (port=60574 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mcbe8-0005wR-Mb for paparazzi-devel@nongnu.org; Sun, 16 Aug 2009 05:03:24 -0400 Received: from fmail1.hs-bremen.de ([194.94.24.14]:53837) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Mcbe7-0001UC-Ll for paparazzi-devel@nongnu.org; Sun, 16 Aug 2009 05:03:24 -0400 Received: from localhost (fmail1 [127.0.0.1]) by fmail1.hs-bremen.de (Postfix) with ESMTP id 32E1B32EEF for ; Sun, 16 Aug 2009 11:01:46 +0200 (CEST) X-Virus-Scanned: by amavisd-new at fmail1.hs-bremen.de Received: from fmail1.hs-bremen.de ([127.0.0.1]) by localhost (fmail1.hs-bremen.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5czSoM31F68O for ; Sun, 16 Aug 2009 11:01:44 +0200 (CEST) Received: from mail.hs-bremen.de (mail.hs-bremen.de [194.94.24.31]) by fmail1.hs-bremen.de (Postfix) with ESMTP id E005B32E62 for ; Sun, 16 Aug 2009 11:01:44 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by mail.hs-bremen.de (Postfix) with ESMTP id C854578C0A8 for ; Sun, 16 Aug 2009 11:01:44 +0200 (CEST) X-Virus-Scanned: by amavisd-new at mail.hs-bremen.de Received: from mail.hs-bremen.de ([127.0.0.1]) by localhost (mail.hs-bremen.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KLgubMDkDh0y for ; Sun, 16 Aug 2009 11:01:44 +0200 (CEST) Received: from hs-bremen.de (p5B10727B.dip.t-dialin.net [91.16.114.123]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.hs-bremen.de (Postfix) with ESMTP id 70A7578C094 for ; Sun, 16 Aug 2009 11:01:43 +0200 (CEST) Message-ID: <4A87CA96.5020303@hs-bremen.de> Date: Sun, 16 Aug 2009 11:00:06 +0200 From: "Prof. Dr.-Ing. Heinrich Warmers" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; de-DE; rv:1.4) Gecko/20030619 Netscape/7.1 (ax) X-Accept-Language: de-de, de MIME-Version: 1.0 To: paparazzi-devel@nongnu.org Subject: Re: [Paparazzi-devel] New Autopilot - Tiny v3 References: <20090814204715.e412a968f7f3915fb4f3361627e3fef7.137d8a414a.wbe@email01.secureserver.net> In-Reply-To: <20090814204715.e412a968f7f3915fb4f3361627e3fef7.137d8a414a.wbe@email01.secureserver.net> Content-Type: multipart/alternative; boundary="------------040502040302060800040407" X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 3) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Aug 2009 09:03:29 -0000 This is a multi-part message in MIME format. --------------040502040302060800040407 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable Hello, you can download the kalman filter code to calculate the exact =20 attitude. We use them to fly quadrocopters. To implement them for normal plane configuration you have to exchange =20 the angles calculation with the IR sensors with the code to calculate with acceleration and rate sensors=20 signals as we do. We want to implement to fly normal planes with MEMS-sensors, but we=20 need a documentation (formulas, variables, algorithms)=20 of the current paparazzi code in a form of an technical report. We want to fly with MEMS-sensors since we want to fly in clouds, with=20 inversion weather conditions in frog and so on. Since low cost rate sensors like the lisy300al cost only about 45$ it=20 may be cheaper then the use of the IR sensors (about 90 $). Also with high end sensors like the adxrs610 the cost are about 102$. =20 The acelleraton sensor ADX330 cost 8$.=20 I and other worked on a overwiey for the sensors:=20 http://openmulticopter.org/wiki/Documentation/Hardware_Selection With a new tiny with added MES Sensors on the pcb it is more easy to fit the autopilot in very small MAVs. I want to have=20 one with a 250mm span and 130g mass. Currently a club menber has one with 290mm span and 87g mass with RC. Best reagrds Heinrich Warmers akochevar@miraterre.com schrieb: > Just a note for everyone reading. > > The IMU would only be useful if code existed to calculate the euler=20 > angles for a fixed wing vehicle type. At present the code doesnt=20 > exist(to my knowledge anyways).=20 > > AJ > > -------- Original Message -------- > Subject: Re: [Paparazzi-devel] New Autopilot - Tiny v3 > From: Rui Costa > Date: Fri, August 14, 2009 7:27 am > To: paparazzi-devel@nongnu.org > > Hello, > =20 > Thank you for the reply. I'm studing the HB-Autopilot to make the > base for the tiny v3. I have a lot of things to ask. Have the > e-mail contact of Andreas Dei? > =20 > =20 > Best regards > Rui Costa > On Fri, Aug 14, 2009 at 2:13 PM, Prof. Dr.-Ing. Heinrich Warmers > > wrote: > > Hello, > you can use the IMU form the HB-Autopilot and the HB-Autopilot > MCU for most of the points. > http://www.akaflieg.hs-bremen.de/trac/akaflieg/wiki/airborne/hw= /autopilot > It is also possible to use the booz2_IMU_HB witch was made by > pione and John. We added a pressure > sensor and a connection for a difference pressure sensor. > Al the IMUs are use the spi bus and the eagle files are free > to use (GPL3). > Since there is a new magnetic sensor the HMC5843 this sensor > may spend a lot of money > (17$ to 60$). > Best regards > > Heinrich Warmers=20 > > > HMC5843 > > > > > Rui Costa schrieb: > >> Hello all, >> =20 >> =20 >> Let's talk about possible new features for the new Tiny. I >> think it's time to make a new autopilot based on experience >> acumulated from the others Tiny boards. >> We can discuss this new features by here, wiki, IRC channel >> or f=C3=B3rum. >> =20 >> http://paparazzi.enac.fr/wiki/Tiny_v3 >> >> I will need some help with some new components and the >> implementation of the software part. >> =20 >> >> Best regards >> Rui Costa >> >>-----------------------------------------------------------------------= - >> >>_______________________________________________ >>Paparazzi-devel mailing list >>Paparazzi-devel@nongnu.org >>http://lists.nongnu.org/mailman/listinfo/paparazzi-devel >> =20 >> > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > > > > > --=20 > Rui Costa > www.azoreanuav.com > -------------------------------------------------------------------= ----- > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > >------------------------------------------------------------------------ > >_______________________________________________ >Paparazzi-devel mailing list >Paparazzi-devel@nongnu.org >http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > =20 > --------------040502040302060800040407 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hello,
you can download the kalman filter code to calculate the exact=C2=A0 attitude. We use them to fly quadrocopters.
To implement them for normal plane configuration you have to exchange=C2=A0 the angles calculation with the IR
sensors with the code to calculate with acceleration and rate sensors signals as we do.
We want to implement to fly normal planes=C2=A0 with MEMS-sensors,=C2=A0 = but we need a documentation (formulas, variables, algorithms)=C2=A0
of=C2=A0 the current=C2=A0 paparazzi code in a form of an technical repor= t.

We want to fly with MEMS-sensors since we want to fly in clouds, with inversion weather conditions in frog and so on.
Since low cost rate sensors like the lisy300al cost only about 45$=C2=A0 = it may be cheaper then the use of the IR sensors=C2=A0 (about=C2=A0 90 $). Also with high end sensors like the adxrs610 the cost are about=C2=A0 102= $.=C2=A0 The acelleraton sensor ADX330 cost 8$.=C2=A0
I=C2=A0 and other worked on a overwiey for the sensors: http://openmulticopter.org/wiki/Docum= entation/Hardware_Selection
With a new tiny with added MES Sensors on the pcb it
=C2=A0is=C2=A0 more easy to fit the autopilot in very small MAVs. I want = to have one=C2=A0 with=C2=A0 a 250mm span and 130g mass.
Currently a club menber has one with 290mm span and 87g mass with=C2=A0 R= C.


Best reagrds

Heinrich Warmers


akochevar@miraterre.com schrieb:
Ju= st a note for everyone reading.

The IMU would only be useful if code existed to calculate the euler angles for a fixed wing vehicle type.=C2=A0 At present the code doesnt exist(to my knowledge anyways).=C2=A0

AJ

-------- Original Message --------
Subject: Re: [Paparazzi-devel] New Autopilot - Tiny v3
From: Rui Costa <azoreanuav@gmail.com>
Date: Fri, August 14, 2009 7:27 am
To: paparazzi-devel@nongnu.org

Hello,
=C2=A0
Thank you for the reply. I'm studing the HB-Autopilot to make the base for the tiny v3. I have a lot of things to ask. Have the e-mail contact of Andreas Dei?
=C2=A0
=C2=A0
Best regards
Rui Costa
On Fri, Aug 14, 2009 at 2:13 PM, Prof. Dr.-Ing. Heinrich Warmers <hwarmers@hs-= bremen.de> wrote:
Hello,
you can use the IMU form the HB-Autopilot and the HB-Autopilot MCU for most of the points.
http://www.akaflieg.hs-bremen.de/trac/akaflieg/wiki/ai= rborne/hw/autopilot
It is also possible to use the booz2_IMU_HB witch was made by pione and John. We added=C2=A0 a pressure
sensor and a connection for a difference=C2=A0 pressure sensor.
Al the IMUs are=C2=A0 use the spi bus and the eagle files are free to use (GPL3).
Since there is a new=C2=A0 magnetic sensor the HMC5843 this sensor may sp= end a lot of money
(17$ to 60$).
Best regards

Heinrich Warmers=C2=A0

HMC5843




Rui Costa schrieb:
Hello all,
=C2=A0
=C2=A0
Let's talk about possible new features for the new Tiny. I think it's time to make a new autopilot based on experience acumulated from the others Tiny boards.
We can discuss this new features by here, wiki, IRC channel or f=C3=B3rum.
=C2=A0

I will need some help with some new components and the implementation of the software part.
=C2=A0

Best regards
Rui Costa

_______________________________________________ Paparazzi-devel mailing list Paparaz= zi-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/paparazzi-dev= el

_______________________________________________
Paparazzi-devel mailing list
Paparaz= zi-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/paparazzi-dev= el




--
Rui Costa
www.azoreanuav= .com

_______________________________________________
Paparazzi-devel mailing list
Paparazzi-devel@nongnu.org
ht= tp://lists.nongnu.org/mailman/listinfo/paparazzi-devel

_______________________________________________ Paparazzi-devel mailing list Paparazzi-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/papa= razzi-devel
--------------040502040302060800040407-- From MAILER-DAEMON Sun Aug 16 21:50:50 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1McrN4-0002Ez-II for mharc-paparazzi-devel@gnu.org; Sun, 16 Aug 2009 21:50:50 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1McrN2-0002EM-Lo for paparazzi-devel@nongnu.org; Sun, 16 Aug 2009 21:50:48 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1McrMx-0002Au-OP for paparazzi-devel@nongnu.org; Sun, 16 Aug 2009 21:50:47 -0400 Received: from [199.232.76.173] (port=39554 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1McrMx-0002Af-Fh for paparazzi-devel@nongnu.org; Sun, 16 Aug 2009 21:50:43 -0400 Received: from mail-ew0-f210.google.com ([209.85.219.210]:42348) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1McrMx-0007vo-1N for paparazzi-devel@nongnu.org; Sun, 16 Aug 2009 21:50:43 -0400 Received: by ewy6 with SMTP id 6so959004ewy.34 for ; Sun, 16 Aug 2009 18:50:41 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.89.195 with SMTP id c45mr931860wef.38.1250473841071; Sun, 16 Aug 2009 18:50:41 -0700 (PDT) In-Reply-To: <4A805A4D.8020404@gmail.com> References: <4A805A4D.8020404@gmail.com> Date: Sun, 16 Aug 2009 19:50:41 -0600 Message-ID: <5e20ac400908161850x15289dfbrc1293068ccaf2e39@mail.gmail.com> Subject: Re: [Paparazzi-devel] 5v onboard regulator From: Nicholas Wagner To: paparazzi-devel@nongnu.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Aug 2009 01:50:49 -0000 I am working on a board that has a separate 12V and 5V switching regulators for servos and an input for a battery for an autopilot and servo battery backup. Is this something that anyone else would want? Vin for the board is about 50V This would allow for the autopilot to be used for much larger planes.. is this something anyone else would be interested in? Nick On Mon, Aug 10, 2009 at 11:35 AM, chris wrote: > I never experienced a crash due to an autopilot problem until i connected > one servo directly to the autopilot. > After the incident i removed it and all flights have been perfect. > From the start i used an external 10A bec for powering the servos. > I think the onboard regulator be changed for a 3.3v @ 2A or more output > with the parallel removal =A0of the linear 3.3v regulator. > Even if the 5v regulator is upgraded to a high amperage one i don't think > that it is wise to run > high current and noisy lines from servos =A0inside the autopilot's pcb. > I keep the high current path for the servos well outside the autopilot's > pcb. > Chris > > > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > --=20 Nick Wagner Mechanical Engineering Colorado State University C: 970.631.2989 E: nawagner@rams.colostate.edu From MAILER-DAEMON Mon Aug 17 00:43:27 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Mcu47-0003VK-Fz for mharc-paparazzi-devel@gnu.org; Mon, 17 Aug 2009 00:43:27 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mcu44-0003Ui-VC for paparazzi-devel@nongnu.org; Mon, 17 Aug 2009 00:43:24 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mcu43-0003UW-6I for paparazzi-devel@nongnu.org; Mon, 17 Aug 2009 00:43:24 -0400 Received: from [199.232.76.173] (port=34668 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mcu43-0003UT-2H for paparazzi-devel@nongnu.org; Mon, 17 Aug 2009 00:43:23 -0400 Received: from forward9.yandex.ru ([77.88.61.48]:56496) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Mcu42-00075N-Iq for paparazzi-devel@nongnu.org; Mon, 17 Aug 2009 00:43:22 -0400 Received: from webmail134.yandex.ru (webmail134.yandex.ru [213.180.223.6]) by forward9.yandex.ru (Yandex) with ESMTP id 32104468487 for ; Mon, 17 Aug 2009 08:43:18 +0400 (MSD) Received: from localhost (localhost [127.0.0.1]) by webmail134.yandex.ru (Yandex) with ESMTP id 2903FA24209 for ; Mon, 17 Aug 2009 08:43:18 +0400 (MSD) X-Yandex-Spam: 1 X-Yandex-Front: webmail134 X-Yandex-TimeMark: 1250484198 Received: from [89.253.27.182] ([89.253.27.182]) by mail.yandex.ru with HTTP; Mon, 17 Aug 2009 08:43:17 +0400 From: Andrew S To: paparazzi-devel@nongnu.org In-Reply-To: <5e20ac400908161850x15289dfbrc1293068ccaf2e39@mail.gmail.com> References: <4A805A4D.8020404@gmail.com> <5e20ac400908161850x15289dfbrc1293068ccaf2e39@mail.gmail.com> Subject: Re: [Paparazzi-devel] 5v onboard regulator MIME-Version: 1.0 Message-Id: <402991250484197@webmail134.yandex.ru> Date: Mon, 17 Aug 2009 08:43:17 +0400 X-Mailer: Yamail [ http://yandex.ru ] 5.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Aug 2009 04:43:25 -0000 Hello, me interested. Max voltage I used at the moment was 4 lipo, and fu= ture problem would be insufficient power for servos. Also good thing abou= t backup battery. In case of larger autopilot i think you dont have to us= e micro molex connectors, especially for servos, and better would be a se= parate gps receiver. Also there is one thing for reliability - now 3v for MC is made from 5v f= or servos, and in case of overloading we have reset of board, this must b= e set right. I agree with Chris about high current lines near MK, it is a= cceptable for small system, but must be redesigned for larger. Also probl= em was with 5V modems. When I powered them from 5v line, they didnt work = because of noise from servos, and I had to put separate 7805 for it. 12v = bec is also good solution, it required in order for some payloads powerin= g, some videotransmitters needs it etc.=20 Andrew 17.08.09, 05:50, "Nicholas Wagner" : > I am working on a board that has a separate 12V and 5V switching > regulators for servos and an input for a battery for an autopilot and > servo battery backup. Is this something that anyone else would want? > Vin for the board is about 50V This would allow for the autopilot to > be used for much larger planes.. is this something anyone else would > be interested in? > Nick > On Mon, Aug 10, 2009 at 11:35 AM, chris wrote: > > I never experienced a crash due to an autopilot problem until i conne= cted > > one servo directly to the autopilot. > > After the incident i removed it and all flights have been perfect. > > From the start i used an external 10A bec for powering the servos. > > I think the onboard regulator be changed for a 3.3v @ 2A or more outp= ut > > with the parallel removal =C2=A0of the linear 3.3v regulator. > > Even if the 5v regulator is upgraded to a high amperage one i don't t= hink > > that it is wise to run > > high current and noisy lines from servos =C2=A0inside the autopilot's= pcb. > > I keep the high current path for the servos well outside the autopilo= t's > > pcb. > > Chris > > > > > > > > _______________________________________________ > > Paparazzi-devel mailing list > > Paparazzi-devel@nongnu.org > > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > > --=20 =D0=9D=D0=BE=D0=B2=D0=B0=D1=8F =D0=BF=D0=BE=D1=87=D1=82=D0=B0 =D0=BF=D1=80= =D0=B8=D1=88=D0=BB=D0=B0 http://mail.yandex.ru/promo/neo/welcome/sign From MAILER-DAEMON Mon Aug 17 01:08:31 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1McuSN-0004x1-H3 for mharc-paparazzi-devel@gnu.org; Mon, 17 Aug 2009 01:08:31 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1McuSL-0004ww-DJ for paparazzi-devel@nongnu.org; Mon, 17 Aug 2009 01:08:29 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1McuSG-0004wf-Su for paparazzi-devel@nongnu.org; Mon, 17 Aug 2009 01:08:28 -0400 Received: from [199.232.76.173] (port=53129 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1McuSG-0004wc-Ji for paparazzi-devel@nongnu.org; Mon, 17 Aug 2009 01:08:24 -0400 Received: from mail-gx0-f211.google.com ([209.85.217.211]:63666) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1McuSF-0002Tr-TQ for paparazzi-devel@nongnu.org; Mon, 17 Aug 2009 01:08:24 -0400 Received: by gxk7 with SMTP id 7so3523777gxk.8 for ; Sun, 16 Aug 2009 22:08:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=Ms724r+2/ZAG+9X0slKdkLLDmK5YOD8EzxfwlXo+/e4=; b=X074/OWA4pVE4NxCioX3j4IVXvM2E+P8pJRHJigAaNd9qAHpSz1iQYvMtXhOXmGlax VmfQNOX/+TQSBJaugpS66O67KEBlB2CUyIBqeKEoif6L5jIzIPNFpIggbjt7zFu43dhz shFy63939XgardY6gTtTOqNy3RkaWk/knF3IU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=tVcSQLXJkfstRhKV2AtM0qFn5E+6kbDILajWV4y0u+4tXX1+ZzUiQNNotvGeYA0uUE fkLfw0jUWbhnQdDvjFw77KsAfN0WpKcjAYrQ1fUDrhpXpcOgbY5Ybm6XrUvKx5LqEI0f la3XIUXaABqQ4Jz7JGVL5Rl/DIZj2+vkfmNVc= MIME-Version: 1.0 Received: by 10.151.143.14 with SMTP id v14mr4860892ybn.310.1250485702100; Sun, 16 Aug 2009 22:08:22 -0700 (PDT) In-Reply-To: <402991250484197@webmail134.yandex.ru> References: <4A805A4D.8020404@gmail.com> <5e20ac400908161850x15289dfbrc1293068ccaf2e39@mail.gmail.com> <402991250484197@webmail134.yandex.ru> Date: Sun, 16 Aug 2009 22:08:22 -0700 Message-ID: <727fedc40908162208w2ec3c434p2295f2f5410399e3@mail.gmail.com> Subject: Re: [Paparazzi-devel] 5v onboard regulator From: antoine drouin To: paparazzi-devel@nongnu.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Aug 2009 05:08:30 -0000 In a larger aircraft, servos are likely to be far apart from the autopilot. Why don't you guys use an external servo driver located close to clusters of servos and containing the adequate power supply. I made such a board some time ago for a specific application (http://poinix.org/images/csc_1_0.jpg) . It connect to the autopilot through CAN bus wich is more robust than PPM on longer wires. Regards Poine From MAILER-DAEMON Mon Aug 17 03:40:25 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1McwpN-0000gh-GB for mharc-paparazzi-devel@gnu.org; Mon, 17 Aug 2009 03:40:25 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1McwpL-0000g6-FI for paparazzi-devel@nongnu.org; Mon, 17 Aug 2009 03:40:23 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1McwpG-0000eP-H8 for paparazzi-devel@nongnu.org; Mon, 17 Aug 2009 03:40:22 -0400 Received: from [199.232.76.173] (port=33659 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1McwpF-0000eE-Ol for paparazzi-devel@nongnu.org; Mon, 17 Aug 2009 03:40:17 -0400 Received: from mx20.gnu.org ([199.232.41.8]:41998) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1McwpF-00076r-0Y for paparazzi-devel@nongnu.org; Mon, 17 Aug 2009 03:40:17 -0400 Received: from mail-bw0-f220.google.com ([209.85.218.220]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1McwpD-00024D-8N for paparazzi-devel@nongnu.org; Mon, 17 Aug 2009 03:40:15 -0400 Received: by bwz20 with SMTP id 20so3366511bwz.9 for ; Mon, 17 Aug 2009 00:40:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=wyvDQZlDch/cmozflttS3nb5g8M+o+ek4dbgqD0jzNk=; b=uIe0reArLBPqQfNKzU6LPuoKrc+wI0DjPjaJGRAfKHAikBEvDPCp82a4mFUnbm97S7 EchQm2r8CxLJvimQzSacDw7OwmWlnsr2ACajj6u0nmw3QUtAIk38Kt2/fT0Z7Ku/WN9g T40JmN/bRu3O4MiLFnlzX6/Ijifv0Gk0yMIBs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=kohhWPZ2dOFCBXm0rgygrtT2d8QekTEvSxJAzrx30lLZx2KizNysQhrlheJqurzsO/ iG/RIyjKCxaxSQzR5MBh/7HcH4jQAA6o8fklO6FvJD+UGr92ds7jxm3AarzgZFj38+rC 5DbfWQo+I9f0mRhnjE3O5NsasThcZpPgGFeLI= MIME-Version: 1.0 Received: by 10.204.156.24 with SMTP id u24mr2382488bkw.172.1250494806323; Mon, 17 Aug 2009 00:40:06 -0700 (PDT) In-Reply-To: <727fedc40908162208w2ec3c434p2295f2f5410399e3@mail.gmail.com> References: <4A805A4D.8020404@gmail.com> <5e20ac400908161850x15289dfbrc1293068ccaf2e39@mail.gmail.com> <402991250484197@webmail134.yandex.ru> <727fedc40908162208w2ec3c434p2295f2f5410399e3@mail.gmail.com> Date: Mon, 17 Aug 2009 07:40:06 +0000 Message-ID: <4d39daa50908170040i31d7d718x1c84ea1b31ac9e25@mail.gmail.com> Subject: Re: [Paparazzi-devel] 5v onboard regulator From: Rui Costa To: paparazzi-devel@nongnu.org Content-Type: multipart/alternative; boundary=0015175dda9ab9734f0471518278 X-Detected-Operating-System: by mx20.gnu.org: GNU/Linux 2.6 (newer, 2) X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6, seldom 2.4 (older, 4) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Aug 2009 07:40:23 -0000 --0015175dda9ab9734f0471518278 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hello all, Poine, can you explain in more detail how it works? Best regards RuI Costa On Mon, Aug 17, 2009 at 5:08 AM, antoine drouin wrote: > In a larger aircraft, servos are likely to be far apart from the > autopilot. Why don't you guys use an external servo driver located > close to clusters of servos and containing the adequate power supply. > I made such a board some time ago for a specific application > (http://poinix.org/images/csc_1_0.jpg) . It connect to the autopilot > through CAN bus wich is more robust than PPM on longer wires. > > Regards > > Poine > > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > -- Rui Costa www.azoreanuav.com --0015175dda9ab9734f0471518278 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hello all,
=A0
=A0
Poine, can you explain in more detail how it works?
=A0
=A0
Best regards
RuI Costa




--
Rui Costa
ww= w.azoreanuav.com
--0015175dda9ab9734f0471518278-- From MAILER-DAEMON Mon Aug 17 04:07:07 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1McxFD-0001pq-Nk for mharc-paparazzi-devel@gnu.org; Mon, 17 Aug 2009 04:07:07 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1McxFB-0001pl-MW for paparazzi-devel@nongnu.org; Mon, 17 Aug 2009 04:07:05 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1McxF7-0001op-2A for paparazzi-devel@nongnu.org; Mon, 17 Aug 2009 04:07:05 -0400 Received: from [199.232.76.173] (port=54611 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1McxF6-0001om-Tz for paparazzi-devel@nongnu.org; Mon, 17 Aug 2009 04:07:00 -0400 Received: from mx20.gnu.org ([199.232.41.8]:43548) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1McxF6-0001S4-3F for paparazzi-devel@nongnu.org; Mon, 17 Aug 2009 04:07:00 -0400 Received: from fmail2.hs-bremen.de ([194.94.24.15]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1McxF4-0003SS-TV for paparazzi-devel@nongnu.org; Mon, 17 Aug 2009 04:06:59 -0400 Received: from localhost (localhost [127.0.0.1]) by fmail2.hs-bremen.de (Postfix) with ESMTP id 2D41C330C0 for ; Mon, 17 Aug 2009 10:06:56 +0200 (CEST) X-Virus-Scanned: by amavisd-new at fmail2.hs-bremen.de Received: from fmail2.hs-bremen.de ([127.0.0.1]) by localhost (fmail2.hs-bremen.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZLquat6qtwDO for ; Mon, 17 Aug 2009 10:06:52 +0200 (CEST) Received: from mail.hs-bremen.de (mail.hs-bremen.de [194.94.24.31]) by fmail2.hs-bremen.de (Postfix) with ESMTP id D8F2D32EA3 for ; Mon, 17 Aug 2009 10:06:52 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by mail.hs-bremen.de (Postfix) with ESMTP id CA10D78C14A for ; Mon, 17 Aug 2009 10:06:52 +0200 (CEST) X-Virus-Scanned: by amavisd-new at mail.hs-bremen.de Received: from mail.hs-bremen.de ([127.0.0.1]) by localhost (mail.hs-bremen.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1Yscw5anC8-y for ; Mon, 17 Aug 2009 10:06:52 +0200 (CEST) Received: from hs-bremen.de (p5B105B93.dip.t-dialin.net [91.16.91.147]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.hs-bremen.de (Postfix) with ESMTP id 1ED5A78C149 for ; Mon, 17 Aug 2009 10:06:52 +0200 (CEST) Message-ID: <4A890F34.1010402@hs-bremen.de> Date: Mon, 17 Aug 2009 10:05:08 +0200 From: "Prof. Dr.-Ing. Heinrich Warmers" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; de-DE; rv:1.4) Gecko/20030619 Netscape/7.1 (ax) X-Accept-Language: de-de, de MIME-Version: 1.0 To: paparazzi-devel@nongnu.org Subject: Re: [Paparazzi-devel] 5v onboard regulator References: <4A805A4D.8020404@gmail.com> <5e20ac400908161850x15289dfbrc1293068ccaf2e39@mail.gmail.com> In-Reply-To: <5e20ac400908161850x15289dfbrc1293068ccaf2e39@mail.gmail.com> Content-Type: multipart/alternative; boundary="------------050007020804040406030500" X-Detected-Operating-System: by mx20.gnu.org: GNU/Linux 2.6 (newer, 3) X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6, seldom 2.4 (older, 4) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Aug 2009 08:07:05 -0000 This is a multi-part message in MIME format. --------------050007020804040406030500 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Hello Nick, for high power system it would be nice to have no dc current ways from the autopilot to the drive and servo system. A good way to eliminate EMC problems will be the use of opto couplers also for the servo counter. One for count and one for reset. Another free GPL autopilot project have also isolated the Servo systems with opto couplers to. Another good idea is to isolate the RC Receiver by a opto coupler to. Heinirch Nicholas Wagner schrieb: >I am working on a board that has a separate 12V and 5V switching >regulators for servos and an input for a battery for an autopilot and >servo battery backup. Is this something that anyone else would want? >Vin for the board is about 50V This would allow for the autopilot to >be used for much larger planes.. is this something anyone else would >be interested in? > >Nick > > >On Mon, Aug 10, 2009 at 11:35 AM, chris wrote: > > >>I never experienced a crash due to an autopilot problem until i connected >>one servo directly to the autopilot. >>After the incident i removed it and all flights have been perfect. >>From the start i used an external 10A bec for powering the servos. >>I think the onboard regulator be changed for a 3.3v @ 2A or more output >>with the parallel removal of the linear 3.3v regulator. >>Even if the 5v regulator is upgraded to a high amperage one i don't think >>that it is wise to run >>high current and noisy lines from servos inside the autopilot's pcb. >>I keep the high current path for the servos well outside the autopilot's >>pcb. >>Chris >> >> >> >>_______________________________________________ >>Paparazzi-devel mailing list >>Paparazzi-devel@nongnu.org >>http://lists.nongnu.org/mailman/listinfo/paparazzi-devel >> >> >> > > > > > --------------050007020804040406030500 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Hello Nick,

for high power system it would be nice to have no dc current  ways from the autopilot to the drive and servo system.
A good way to eliminate EMC problems will be the use of opto couplers also for the servo counter.
One for count and one for reset.
Another free GPL autopilot project have also isolated the Servo systems with opto couplers to.
Another good idea is to isolate the RC Receiver by a opto coupler to.

Heinirch



Nicholas Wagner schrieb:
I am working on a board that has a separate 12V and 5V switching
regulators for servos and an input for a battery for an autopilot and
servo battery backup.  Is this something that anyone else would want?
Vin for the board is about 50V  This would allow for the autopilot to
be used for much larger planes.. is this something anyone else would
be interested in?

Nick


On Mon, Aug 10, 2009 at 11:35 AM, chris<hendrixgr@gmail.com> wrote:
  
I never experienced a crash due to an autopilot problem until i connected
one servo directly to the autopilot.
After the incident i removed it and all flights have been perfect.
>From the start i used an external 10A bec for powering the servos.
I think the onboard regulator be changed for a 3.3v @ 2A or more output
with the parallel removal  of the linear 3.3v regulator.
Even if the 5v regulator is upgraded to a high amperage one i don't think
that it is wise to run
high current and noisy lines from servos  inside the autopilot's pcb.
I keep the high current path for the servos well outside the autopilot's
pcb.
Chris



_______________________________________________
Paparazzi-devel mailing list
Paparazzi-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/paparazzi-devel

    



  
--------------050007020804040406030500-- From MAILER-DAEMON Mon Aug 17 15:43:38 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Md87G-0005IK-9n for mharc-paparazzi-devel@gnu.org; Mon, 17 Aug 2009 15:43:38 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Md87E-0005Fc-0X for paparazzi-devel@nongnu.org; Mon, 17 Aug 2009 15:43:36 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Md87D-0005FQ-G9 for paparazzi-devel@nongnu.org; Mon, 17 Aug 2009 15:43:35 -0400 Received: from [199.232.76.173] (port=42061 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Md87D-0005FN-Ap for paparazzi-devel@nongnu.org; Mon, 17 Aug 2009 15:43:35 -0400 Received: from ey-out-1920.google.com ([74.125.78.145]:51566) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Md87C-0000h6-Rj for paparazzi-devel@nongnu.org; Mon, 17 Aug 2009 15:43:35 -0400 Received: by ey-out-1920.google.com with SMTP id 5so618361eyb.4 for ; Mon, 17 Aug 2009 12:43:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=3vycpkL45Iy75kvSoZTDAfRnVYjrHODuDD1ZkoXj4jo=; b=RCfzwUdajjfMtba+DYUenK6Lb39V/Gant4KODPV1DB84QCy0XSZHRWtmVVXs0P6PAd BNltiZemxJmvSc3pnRagPAsVCf5w+WCOyV5CYE5zywawoLO9C0uy721D4VjGGlPuK68z /cuz+O66dseetrQlf/wu7vtZLqBWm/+cLM1NM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=iSf/GFNRzJAAb8nV/0EfS1pdv3rWAvHseoBmFA9xLxcVmS0SSRVwGlB323eMIOLAGZ NbNvSy2J0/oZsIWAEDM6cX+YAjNa4+jM+74HyERosgJLoxHfTujDYIeiWLRSeU+TXcxj ch55PIajTJOPo7dtgquH4XB+PNJrc5cLeT720= MIME-Version: 1.0 Received: by 10.210.33.17 with SMTP id g17mr3646110ebg.79.1250538211276; Mon, 17 Aug 2009 12:43:31 -0700 (PDT) Date: Mon, 17 Aug 2009 21:43:31 +0200 Message-ID: <86b1e7960908171243j502792d9nf64f51777292a9aa@mail.gmail.com> From: Christophe De Wagter To: paparazzi-devel@nongnu.org Content-Type: multipart/alternative; boundary=0015174c190edc787704715b9d1d X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) Subject: [Paparazzi-devel] Re: 5v onboard regulator X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Aug 2009 19:43:36 -0000 --0015174c190edc787704715b9d1d Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit If I remember well, the 5V switching regulator was introduced in the Tiny 0.9 boards to reduce the heat of the linear BEC regulators often found in small motor controllers because servos often use more power in automatic flight flight than in manual flight. Nowadays several good motor controllers have beter power regulators than the tiny TINY board, especially in "not so tiny" aircraft. That is why we made a tiny board with only the 3.3V regulator. Servos (and the 6V compatible decade counter) are powered by the 6V motor controller BEC (in our case a 5LiPo 120Amp brushless controller with a 8Amp switching BEC). The 3.3V regulator is changed to a low dropout lt1963 that accepts much more than 6V and still works with 3.6V (unlike the 3940 on the tiny2.11!!). The board also has a serial optocoupler port to allow the RC and ADC to be located further away in case of problems. http://www.flickr.com/photos/dewagter/3830447907/ Christophe > ---------- Forwarded message ---------- > From: antoine drouin In a larger aircraft, servos are likely to be far apart from the > autopilot. Why don't you guys use an external servo driver located > close to clusters of servos and containing the adequate power supply. > I made such a board some time ago for a specific application > (http://poinix.org/images/csc_1_0.jpg) . It connect to the autopilot > through CAN bus wich is more robust than PPM on longer wires. > > Regards > > Poine > ---------- Forwarded message ---------- > From: "Prof. Dr.-Ing. Heinrich Warmers" > > for high power system it would be nice to have no dc current ways from the > autopilot to the drive and servo system. > A good way to eliminate EMC problems will be the use of opto couplers also > for the servo counter. > One for count and one for reset. > Another free GPL autopilot project have also isolated the Servo systems > with opto couplers to. > Another good idea is to isolate the RC Receiver by a opto coupler to. > > Heinirch > > --0015174c190edc787704715b9d1d Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
If I remember well, the 5V switching regula= tor was introduced in the Tiny 0.9 boards to reduce the heat of the linear = BEC regulators often found in small motor controllers because servos often = use more power in automatic flight flight than in manual flight.=A0

Nowadays several good motor controllers have beter powe= r regulators than the tiny TINY board, especially in "not so tiny"= ; aircraft.=A0That is why we made a tiny board with only the 3.3V regulator= . Servos (and the 6V compatible decade counter) are powered by the 6V motor= controller BEC (in our case a 5LiPo 120Amp brushless controller with a 8Am= p switching BEC). The 3.3V regulator is changed to a low dropout lt1963 tha= t accepts much more than 6V and still works with 3.6V (unlike the 3940 on t= he tiny2.11!!). The board also has a serial optocoupler port to allow the R= C and ADC to be located further away in case of problems.=A0http://www= .flickr.com/photos/dewagter/3830447907/

Christophe

=A0
---------- Forwarded message ----------
From:=A0ant= oine drouin <poini= x@gmail.com>=A0
In a larger aircraft, servos are likely to b= e far apart from the
autopilot. Why don't you guys use an external servo driver located
close to clusters of servos and containing the adequate power supply.
I made such a board some time ago for a specific application
(http://= poinix.org/images/csc_1_0.jpg) . It connect to the autopilot
through CAN bus wich is more robust than PPM on longer wires.

Regards

Poine

=A0
---------- Forwarded message ----------
From:=A0"Prof. Dr.-Ing. = Heinrich Warmers" <hwarmers@hs-bremen.de>

for high power system it would be nice to have no dc current=A0 ways from the autopilot to the drive and servo system.
A good way to eliminate EMC problems will be the use of opto couplers also for the servo counter.
One for count and one for reset.
Another free GPL autopilot project have also isolated the Servo systems with opto couplers to.
Another good idea is to isolate the RC Receiver by a opto coupler to.

Heinirch


--0015174c190edc787704715b9d1d-- From MAILER-DAEMON Mon Aug 17 16:29:03 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Md8pD-0004oQ-Ab for mharc-paparazzi-devel@gnu.org; Mon, 17 Aug 2009 16:29:03 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Md8pA-0004jK-Sm for paparazzi-devel@nongnu.org; Mon, 17 Aug 2009 16:29:00 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Md8p4-0004cu-2r for paparazzi-devel@nongnu.org; Mon, 17 Aug 2009 16:28:58 -0400 Received: from [199.232.76.173] (port=40074 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Md8p3-0004cK-RM for paparazzi-devel@nongnu.org; Mon, 17 Aug 2009 16:28:53 -0400 Received: from mail-bw0-f220.google.com ([209.85.218.220]:41438) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Md8p1-00026I-Dx for paparazzi-devel@nongnu.org; Mon, 17 Aug 2009 16:28:51 -0400 Received: by bwz20 with SMTP id 20so3878431bwz.9 for ; Mon, 17 Aug 2009 13:28:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=jQCi7AtbD4L3bkgWKFfQ4Hotwr7gZZ+7sy4QD96Bw8U=; b=jdMVPnutDZDzj+FcGzyQIXhmzpYHMyUb346s0jo6upNqiS+zHTurJEkT/4LXb0SUWy JNkC8j9TphjnM8x/bn83tHqpNBR+VwBzwz2+raxexZWuRs6p01FJDOX3QEhnGuxdltFA 3eq9dLm4PTFctP/1wieeuZ/xJ9kKK3s3zwNJo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=tw5w67QKsWkR7cTuugW4I12iqOdIaNIoBYoZcaFTjZ0ViIRUAuIBtu+dMFHxyW0sf7 M7TdImjgf6kDymQjNlAATal4kANZEwB1HEY5eubKKEykz4nnrldoudabdzRuL2X1E+CU hI+3a3+RZ0OkPwsBTY4nyVIr6i/eZOcEfs7WY= MIME-Version: 1.0 Received: by 10.204.8.13 with SMTP id f13mr3066977bkf.150.1250540928896; Mon, 17 Aug 2009 13:28:48 -0700 (PDT) In-Reply-To: <86b1e7960908171243j502792d9nf64f51777292a9aa@mail.gmail.com> References: <86b1e7960908171243j502792d9nf64f51777292a9aa@mail.gmail.com> Date: Mon, 17 Aug 2009 20:28:48 +0000 Message-ID: <4d39daa50908171328y7d6ee980p314d801457b18519@mail.gmail.com> Subject: Re: [Paparazzi-devel] Re: 5v onboard regulator From: Rui Costa To: paparazzi-devel@nongnu.org Content-Type: multipart/alternative; boundary=000e0cd30d76d80f3104715c3f8e X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Aug 2009 20:29:01 -0000 --000e0cd30d76d80f3104715c3f8e Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hello, That board is opensource? Can we know more about it? Regards Rui Costa On Mon, Aug 17, 2009 at 7:43 PM, Christophe De Wagter wrote: > If I remember well, the 5V switching regulator was introduced in the Tiny > 0.9 boards to reduce the heat of the linear BEC regulators often found in > small motor controllers because servos often use more power in automatic > flight flight than in manual flight. > > Nowadays several good motor controllers have beter power regulators than > the tiny TINY board, especially in "not so tiny" aircraft. That is why we > made a tiny board with only the 3.3V regulator. Servos (and the 6V > compatible decade counter) are powered by the 6V motor controller BEC (in > our case a 5LiPo 120Amp brushless controller with a 8Amp switching BEC). The > 3.3V regulator is changed to a low dropout lt1963 that accepts much more > than 6V and still works with 3.6V (unlike the 3940 on the tiny2.11!!). The > board also has a serial optocoupler port to allow the RC and ADC to be > located further away in case of problems. > http://www.flickr.com/photos/dewagter/3830447907/ > > Christophe > > > >> ---------- Forwarded message ---------- >> From: antoine drouin > > In a larger aircraft, servos are likely to be far apart from the >> autopilot. Why don't you guys use an external servo driver located >> close to clusters of servos and containing the adequate power supply. >> I made such a board some time ago for a specific application >> (http://poinix.org/images/csc_1_0.jpg) . It connect to the autopilot >> through CAN bus wich is more robust than PPM on longer wires. >> >> Regards >> >> Poine > > > > >> ---------- Forwarded message ---------- >> From: "Prof. Dr.-Ing. Heinrich Warmers" >> >> for high power system it would be nice to have no dc current ways from >> the autopilot to the drive and servo system. >> A good way to eliminate EMC problems will be the use of opto couplers also >> for the servo counter. >> One for count and one for reset. >> Another free GPL autopilot project have also isolated the Servo systems >> with opto couplers to. >> Another good idea is to isolate the RC Receiver by a opto coupler to. >> >> Heinirch >> >> > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > > -- Rui Costa www.azoreanuav.com --000e0cd30d76d80f3104715c3f8e Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hello,
=A0
That board is opensource? Can we know more about it?
=A0
=A0
Regards
Rui Costa

On Mon, Aug 17, 2009 at 7:43 PM, Christophe De W= agter <dewagter@= gmail.com> wrote:
If I remember well, the 5V switching regulator was introduced in the T= iny 0.9 boards to reduce the heat of the linear BEC regulators often found = in small motor controllers because servos often use more power in automatic= flight flight than in manual flight.=A0

Nowadays several good motor controllers have beter power regulators th= an the tiny TINY board, especially in "not so tiny" aircraft.=A0T= hat is why we made a tiny board with only the 3.3V regulator. Servos (and t= he 6V compatible decade counter) are powered by the 6V motor controller BEC= (in our case a 5LiPo 120Amp brushless controller with a 8Amp switching BEC= ). The 3.3V regulator is changed to a low dropout lt1963 that accepts much = more than 6V and still works with 3.6V (unlike the 3940 on the tiny2.11!!).= The board also has a serial optocoupler port to allow the RC and ADC to be= located further away in case of problems.=A0http://www.flickr.com/pho= tos/dewagter/3830447907/

Christophe

=A0
---------- Forwarded message ---= -------
From:=A0antoine drouin <poinix@gmail.com>=A0
In a larger aircraft, servos are= likely to be far apart from the
autopilot. Why don't you guys use a= n external servo driver located
close to clusters of servos and containing the adequate power supply.
I = made such a board some time ago for a specific application
(http://poinix.org/im= ages/csc_1_0.jpg) . It connect to the autopilot
through CAN bus wich is more robust than PPM on longer wires.

Regard= s

Poine

=A0


________________________________= _______________
Paparazzi-devel mailing list
Paparazzi-devel@nongnu.org
http://= lists.nongnu.org/mailman/listinfo/paparazzi-devel




--
Rui Costa
ww= w.azoreanuav.com
--000e0cd30d76d80f3104715c3f8e-- From MAILER-DAEMON Mon Aug 17 17:15:12 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Md9Xs-0000cE-Kg for mharc-paparazzi-devel@gnu.org; Mon, 17 Aug 2009 17:15:12 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Md9Xq-0000bF-EY for paparazzi-devel@nongnu.org; Mon, 17 Aug 2009 17:15:10 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Md9Xm-0000Wj-R5 for paparazzi-devel@nongnu.org; Mon, 17 Aug 2009 17:15:10 -0400 Received: from [199.232.76.173] (port=37514 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Md9Xm-0000Wg-MV for paparazzi-devel@nongnu.org; Mon, 17 Aug 2009 17:15:06 -0400 Received: from mail-ew0-f222.google.com ([209.85.219.222]:50875) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Md9Xm-00028W-4K for paparazzi-devel@nongnu.org; Mon, 17 Aug 2009 17:15:06 -0400 Received: by ewy22 with SMTP id 22so3175315ewy.28 for ; Mon, 17 Aug 2009 14:15:05 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.85.213 with SMTP id u63mr1146758wee.15.1250543703906; Mon, 17 Aug 2009 14:15:03 -0700 (PDT) In-Reply-To: <4d39daa50908171328y7d6ee980p314d801457b18519@mail.gmail.com> References: <86b1e7960908171243j502792d9nf64f51777292a9aa@mail.gmail.com> <4d39daa50908171328y7d6ee980p314d801457b18519@mail.gmail.com> Date: Mon, 17 Aug 2009 15:15:03 -0600 Message-ID: <5e20ac400908171415q63adba7bx6bfc70c0fc3d4578@mail.gmail.com> Subject: Re: [Paparazzi-devel] Re: 5v onboard regulator From: Nicholas Wagner To: paparazzi-devel@nongnu.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Aug 2009 21:15:10 -0000 All - The use of optocouplers would be a great addition to the servo board, however due to time constraints and other constraints of our project, rev1 of this board is to be delivered later this week. To briefly describe our project, we are working on the design of a fuel cell powered long endurance UAV. and Two challenges that come from this are weight and electrical efficiency (this may be an oversimplification). Original specifications of the fuel cell specified a Vin max of approximately 70VDC which made our electrical design process a little interesting. The latest specification dropped this down to 40V which is much more feasible. At this time, the board we are designing in house uses two switching regulators, LM5088 to provide high current output at 5V and 12V for use by our electronics and other peripherals. These two regulator circuits have been designed to limit EMI. It uses a high current 5V linear regulator and a diode drop (to 12V) for a 3C lipo battery backup. This board, due to the constraints of our funding source will not be Open source/GPL. However, I can personally design another version of this board for the Paparazzi community, if there is enough interest, that will be Open Source/GPL as an act of good will :). There is one drawback. I personally am a Mechanical Engineer, so there are many more, better qualified, people to do this. Once I have some time to put this together, I could make a preliminary design in eagle for the schematic and then open a 'design space' on the wiki for other contributors. Nick On Mon, Aug 17, 2009 at 2:28 PM, Rui Costa wrote: > Hello, > > That board is opensource? Can we know more about it? > > > Regards > Rui Costa > > On Mon, Aug 17, 2009 at 7:43 PM, Christophe De Wagter > wrote: >> >> If I remember well, the 5V switching regulator was introduced in the Tin= y >> 0.9 boards to reduce the heat of the linear BEC regulators often found i= n >> small motor controllers because servos often use more power in automatic >> flight flight than in manual flight. >> Nowadays several good motor controllers have beter power regulators than >> the tiny TINY board, especially in "not so tiny" aircraft.=A0That is why= we >> made a tiny board with only the 3.3V regulator. Servos (and the 6V >> compatible decade counter) are powered by the 6V motor controller BEC (i= n >> our case a 5LiPo 120Amp brushless controller with a 8Amp switching BEC).= The >> 3.3V regulator is changed to a low dropout lt1963 that accepts much more >> than 6V and still works with 3.6V (unlike the 3940 on the tiny2.11!!). T= he >> board also has a serial optocoupler port to allow the RC and ADC to be >> located further away in case of >> problems.=A0http://www.flickr.com/photos/dewagter/3830447907/ >> Christophe >> >>> >>> ---------- Forwarded message ---------- >>> From:=A0antoine drouin >>> >>> In a larger aircraft, servos are likely to be far apart from the >>> autopilot. Why don't you guys use an external servo driver located >>> close to clusters of servos and containing the adequate power supply. >>> I made such a board some time ago for a specific application >>> (http://poinix.org/images/csc_1_0.jpg) . It connect to the autopilot >>> through CAN bus wich is more robust than PPM on longer wires. >>> >>> Regards >>> >>> Poine >> >> >>> >>> ---------- Forwarded message ---------- >>> From:=A0"Prof. Dr.-Ing. Heinrich Warmers" >>> >>> for high power system it would be nice to have no dc current=A0 ways fr= om >>> the autopilot to the drive and servo system. >>> A good way to eliminate EMC problems will be the use of opto couplers >>> also for the servo counter. >>> One for count and one for reset. >>> Another free GPL autopilot project have also isolated the Servo systems >>> with opto couplers to. >>> Another good idea is to isolate the RC Receiver by a opto coupler to. >>> >>> Heinirch >>> >> >> >> _______________________________________________ >> Paparazzi-devel mailing list >> Paparazzi-devel@nongnu.org >> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel >> > > > > -- > Rui Costa > www.azoreanuav.com > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > > --=20 Nick Wagner Mechanical Engineering Colorado State University C: 970.631.2989 E: nawagner@rams.colostate.edu From MAILER-DAEMON Tue Aug 18 16:36:07 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MdVPa-0005M7-Sm for mharc-paparazzi-devel@gnu.org; Tue, 18 Aug 2009 16:36:06 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MdVPY-0005JN-LN for paparazzi-devel@nongnu.org; Tue, 18 Aug 2009 16:36:04 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MdVPT-0005DY-In for paparazzi-devel@nongnu.org; Tue, 18 Aug 2009 16:36:03 -0400 Received: from [199.232.76.173] (port=35652 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MdVPS-0005DT-SI for paparazzi-devel@nongnu.org; Tue, 18 Aug 2009 16:35:58 -0400 Received: from mail-yx0-f188.google.com ([209.85.210.188]:33804) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MdVPS-00082t-8F for paparazzi-devel@nongnu.org; Tue, 18 Aug 2009 16:35:58 -0400 Received: by yxe26 with SMTP id 26so5098553yxe.4 for ; Tue, 18 Aug 2009 13:35:45 -0700 (PDT) MIME-Version: 1.0 Sender: maik@zackbumm.biz Received: by 10.91.205.9 with SMTP id h9mr4123279agq.27.1250627743349; Tue, 18 Aug 2009 13:35:43 -0700 (PDT) From: =?UTF-8?B?TWFpayBIw7ZwZmVs?= Date: Tue, 18 Aug 2009 22:35:22 +0200 X-Google-Sender-Auth: 4a8804669565e7ed Message-ID: To: paparazzi-devel@nongnu.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) Subject: [Paparazzi-devel] Can't get XBee's to work with PPRZ X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Aug 2009 20:36:05 -0000 Good evening, I've spent all day trying to get my two XBee Pro 2.4 GHz modules to work with Paparazzi, but failed :( They're the ones CheBuzz sells, so one with a SparkFun USB board, the other one with the LadyAda breakout board. I flashed the newest firmware on them & have them on defaults (9600 baud and everything), just a custom network ID. I can send messages back and forth between them, from the same computer or two different ones. One modem is connected with a FTDI cable, obviously. I have the newest Paparazzi version from the repos, and am using the MJ5 A/C with funjet1.xml as aircraft config. I adapted the funjet1.xml to serial communication as described in http://paparazzi.enac.fr/wiki/Airframe_Configuration. That means I changed the DATALINK section and replaced the appropriate makefile part. I changed the baud rate to 9600 bauds and could connect to the TWOG with my SparkFun FTDI cable (the one I used for the modem as well). GCS was working well, I could move waypoints and it seems to have uploaded them. Then I hooked up the modem. I'm pretty sure I did it right, because I used the same cable between TWOG to modem as I did for TWOG to FTDI breakout board. The green LED blinks, so it all seems well. The other modem even flashes the RX led, and I do get a few scrambled characters every now and then when I listen in to the serial communication. But the GCS does not react, it just stays grey. When I write on the serial line, the receiving modem lights up the RSS light, which it also does when it's receiving something. I then commented out the "XBEE INIT" part in the funjet1.xml config, guessing that that might mess up things. I also toyed with the XBEE_NO_INIT flag, but to no avail. No reaction from the GCS. I then figured I might try the MaxStream API mode. So I reverted the funjet1.xml to its original state and tried connecting. But again, I did not get a reaction from the GCS. Am I right in assuming that PPRZ changes the settings on both XBees to API mode? The XBEE_INIT string seems to suggest that, as well as that the ground modem was in API mode after I started a Flight @ MaxBee ... session. I'm not sure that I tried every possible combination there, but it seems to be that API mode is not the recommended way to go anyhow if I'm getting started. So I'm completely at loss, and am hoping I'm missing something obvious. I'm very new to Paparazzi, so that could absolutely be the case. I powered the TWOG both from a 5V supply (which is not ideal, I know - but so convenient) and a 3S LiPo battery. I also checked for error messages, but there were none. When there's no reaction from the GCS, the data logs for that session are empty as well. And of course I reflashed the TWOG in between my different tries. - Maik I'm appending the two configs used: ===================== My try with serial communication
CONFIG = \"tiny_2_1.h\" include $(PAPARAZZI_SRC)/conf/autopilot/tiny.makefile FLASH_MODE=IAP ap.CFLAGS += -DFBW -DAP -DBOARD_CONFIG=$(CONFIG) -DLED -DTIME_LED=1 ap.srcs = sys_time.c $(SRC_ARCH)/sys_time_hw.c $(SRC_ARCH)/armVIC.c main_fbw.c main_ap.c main.c ap.srcs += commands.c ap.CFLAGS += -DACTUATORS=\"servos_4017_hw.h\" -DSERVOS_4017 ap.srcs += $(SRC_ARCH)/servos_4017_hw.c actuators.c ap.CFLAGS += -DRADIO_CONTROL ap.srcs += radio_control.c $(SRC_ARCH)/ppm_hw.c # Serial modem ap.CFLAGS += -DDOWNLINK -DUSE_UART1 -DDOWNLINK_TRANSPORT=PprzTransport -DDOWNLINK_FBW_DEVICE=Uart1 -DDOWNLINK_AP_DEVICE=Uart1 -DPPRZ_UART=Uart1 -DDATALINK=PPRZ -DUART1_BAUD=B9600 ap.srcs += downlink.c $(SRC_ARCH)/uart_hw.c datalink.c pprz_transport.c #TRANSPARENT #ap.CFLAGS += -DDOWNLINK -DUSE_UART1 -DDOWNLINK_TRANSPORT=PprzTransport -DDOWNLINK_FBW_DEVICE=Uart1 -DDOWNLINK_AP_DEVICE=Uart1 -DPPRZ_UART=Uart1 -DDATALINK=PPRZ -DUART1_BAUD=B9600 #ap.srcs += downlink.c $(SRC_ARCH)/uart_hw.c datalink.c pprz_transport.c ap.CFLAGS += -DINTER_MCU ap.srcs += inter_mcu.c ap.CFLAGS += -DADC -DUSE_ADC_0 -DUSE_ADC_1 -DUSE_ADC_2 -DUSE_ADC_3 ap.srcs += $(SRC_ARCH)/adc_hw.c ap.CFLAGS += -DGPS -DUBX -DUSE_UART0 -DGPS_LINK=Uart0 -DUART0_BAUD=B38400 # -DGPS_LED=2 ap.srcs += gps_ubx.c gps.c latlong.c ap.CFLAGS += -DINFRARED -DALT_KALMAN ap.srcs += infrared.c estimator.c ap.CFLAGS += -DNAV -DAGR_CLIMB -DLOITER_TRIM ap.srcs += nav.c fw_h_ctl_a.c fw_v_ctl.c ap.CFLAGS += -DGYRO -DADXRS150 ap.srcs += gyro.c nav_line.c ap.srcs += nav_survey_rectangle.c # chemotaxis.c anemotaxis.c discsurvey.c ########## Barometer (SPI) #ap.CFLAGS += -DUSE_SPI -DSPI_MASTER -DUSE_SPI_SLAVE0 -DUSE_BARO_MS5534A #ap.srcs += spi.c $(SRC_ARCH)/spi_hw.c $(SRC_ARCH)/baro_MS5534A.c ########## Chemo sensor (I2C) #ap.srcs += i2c.c $(SRC_ARCH)/i2c_hw.c #ap.CFLAGS += -DUSE_I2C -DUSE_I2C0 # Digital camera # Shutter: I2C SCL # Zoom: I2C SDA ap.CFLAGS += -DDIGITAL_CAM ap.srcs += dc.c ap.CFLAGS += -DUSE_MODULES sim.CFLAGS += -DUSE_MODULES # Config for SITL simulation #include $(PAPARAZZI_SRC)/conf/autopilot/sitl.makefile sim.ARCHDIR = $(ARCHI) sim.ARCH = sitl sim.TARGET = autopilot sim.TARGETDIR = autopilot sim.CFLAGS += -DSITL -DAP -DFBW -DRADIO_CONTROL -DINTER_MCU -DDOWNLINK -DDOWNLINK_TRANSPORT=IvyTransport -DINFRARED -DNAV -DLED -DWIND_INFO sim.srcs = latlong.c radio_control.c downlink.c commands.c gps.c inter_mcu.c infrared.c fw_h_ctl_a.c fw_v_ctl.c nav.c estimator.c sys_time.c main_fbw.c main_ap.c datalink.c $(SRC_ARCH)/ppm_hw.c $(SRC_ARCH)/sim_gps.c $(SRC_ARCH)/sim_ir.c $(SRC_ARCH)/sim_ap.c $(SRC_ARCH)/ivy_transport.c $(SRC_ARCH)/sim_adc_generic.c $(SRC_ARCH)/led_hw.c sim.CFLAGS += -DBOARD_CONFIG=\"tiny.h\" -DAGR_CLIMB -DLOITER_TRIM -DALT_KALMAN sim.srcs += nav_line.c nav_survey_rectangle.c # -DENOSE #sim.srcs += i2c.c $(SRC_ARCH)/i2c_hw.c #sim.CFLAGS += -DUSE_I2C -DUSE_I2C0 # chemotaxis.c anemotaxis.c discsurvey.c $(SRC_ARCH)/sim_enose.c chemo_detect.c sim.CFLAGS += -DDIGITAL_CAM -DPOWER_SWITCH_LED=4 sim.srcs += dc.c # a test program to setup actuators setup_actuators.ARCHDIR = $(ARCHI) setup_actuators.ARCH = arm7tdmi setup_actuators.TARGET = setup_actuators setup_actuators.TARGETDIR = setup_actuators setup_actuators.CFLAGS += -DFBW -DBOARD_CONFIG=\"tiny.h\" -DLED -DTIME_LED=1 -DACTUATORS=\"servos_4015_hw.h\" -DSERVOS_4015 -DUSE_UART1 -DUART1_BAUD=B9600 -DDATALINK=PPRZ -DPPRZ_UART=Uart1 setup_actuators.srcs += sys_time.c $(SRC_ARCH)/sys_time_hw.c $(SRC_ARCH)/armVIC.c pprz_transport.c setup_actuators.c $(SRC_ARCH)/uart_hw.c $(SRC_ARCH)/servos_4015_hw.c main.c
===================== My try with MaxStream API mode
CONFIG = \"tiny_2_1.h\" include $(PAPARAZZI_SRC)/conf/autopilot/tiny.makefile FLASH_MODE=IAP ap.CFLAGS += -DFBW -DAP -DBOARD_CONFIG=$(CONFIG) -DLED -DTIME_LED=1 ap.srcs = sys_time.c $(SRC_ARCH)/sys_time_hw.c $(SRC_ARCH)/armVIC.c main_fbw.c main_ap.c main.c ap.srcs += commands.c ap.CFLAGS += -DACTUATORS=\"servos_4017_hw.h\" -DSERVOS_4017 ap.srcs += $(SRC_ARCH)/servos_4017_hw.c actuators.c ap.CFLAGS += -DRADIO_CONTROL ap.srcs += radio_control.c $(SRC_ARCH)/ppm_hw.c ap.CFLAGS += -DDOWNLINK -DUSE_UART1 -DDOWNLINK_TRANSPORT=XBeeTransport -DXBEE_UART=Uart1 -DDATALINK=XBEE -DUART1_BAUD=B9600 ap.srcs += downlink.c $(SRC_ARCH)/uart_hw.c datalink.c xbee.c #TRANSPARENT #ap.CFLAGS += -DDOWNLINK -DUSE_UART1 -DDOWNLINK_TRANSPORT=PprzTransport -DDOWNLINK_FBW_DEVICE=Uart1 -DDOWNLINK_AP_DEVICE=Uart1 -DPPRZ_UART=Uart1 -DDATALINK=PPRZ -DUART1_BAUD=B9600 #ap.srcs += downlink.c $(SRC_ARCH)/uart_hw.c datalink.c pprz_transport.c ap.CFLAGS += -DINTER_MCU ap.srcs += inter_mcu.c ap.CFLAGS += -DADC -DUSE_ADC_0 -DUSE_ADC_1 -DUSE_ADC_2 -DUSE_ADC_3 ap.srcs += $(SRC_ARCH)/adc_hw.c ap.CFLAGS += -DGPS -DUBX -DUSE_UART0 -DGPS_LINK=Uart0 -DUART0_BAUD=B38400 # -DGPS_LED=2 ap.srcs += gps_ubx.c gps.c latlong.c ap.CFLAGS += -DINFRARED -DALT_KALMAN ap.srcs += infrared.c estimator.c ap.CFLAGS += -DNAV -DAGR_CLIMB -DLOITER_TRIM ap.srcs += nav.c fw_h_ctl_a.c fw_v_ctl.c ap.CFLAGS += -DGYRO -DADXRS150 ap.srcs += gyro.c nav_line.c ap.srcs += nav_survey_rectangle.c # chemotaxis.c anemotaxis.c discsurvey.c ########## Barometer (SPI) #ap.CFLAGS += -DUSE_SPI -DSPI_MASTER -DUSE_SPI_SLAVE0 -DUSE_BARO_MS5534A #ap.srcs += spi.c $(SRC_ARCH)/spi_hw.c $(SRC_ARCH)/baro_MS5534A.c ########## Chemo sensor (I2C) #ap.srcs += i2c.c $(SRC_ARCH)/i2c_hw.c #ap.CFLAGS += -DUSE_I2C -DUSE_I2C0 # Digital camera # Shutter: I2C SCL # Zoom: I2C SDA ap.CFLAGS += -DDIGITAL_CAM ap.srcs += dc.c ap.CFLAGS += -DUSE_MODULES sim.CFLAGS += -DUSE_MODULES # Config for SITL simulation #include $(PAPARAZZI_SRC)/conf/autopilot/sitl.makefile sim.ARCHDIR = $(ARCHI) sim.ARCH = sitl sim.TARGET = autopilot sim.TARGETDIR = autopilot sim.CFLAGS += -DSITL -DAP -DFBW -DRADIO_CONTROL -DINTER_MCU -DDOWNLINK -DDOWNLINK_TRANSPORT=IvyTransport -DINFRARED -DNAV -DLED -DWIND_INFO sim.srcs = latlong.c radio_control.c downlink.c commands.c gps.c inter_mcu.c infrared.c fw_h_ctl_a.c fw_v_ctl.c nav.c estimator.c sys_time.c main_fbw.c main_ap.c datalink.c $(SRC_ARCH)/ppm_hw.c $(SRC_ARCH)/sim_gps.c $(SRC_ARCH)/sim_ir.c $(SRC_ARCH)/sim_ap.c $(SRC_ARCH)/ivy_transport.c $(SRC_ARCH)/sim_adc_generic.c $(SRC_ARCH)/led_hw.c sim.CFLAGS += -DBOARD_CONFIG=\"tiny.h\" -DAGR_CLIMB -DLOITER_TRIM -DALT_KALMAN sim.srcs += nav_line.c nav_survey_rectangle.c # -DENOSE #sim.srcs += i2c.c $(SRC_ARCH)/i2c_hw.c #sim.CFLAGS += -DUSE_I2C -DUSE_I2C0 # chemotaxis.c anemotaxis.c discsurvey.c $(SRC_ARCH)/sim_enose.c chemo_detect.c sim.CFLAGS += -DDIGITAL_CAM -DPOWER_SWITCH_LED=4 sim.srcs += dc.c # a test program to setup actuators setup_actuators.ARCHDIR = $(ARCHI) setup_actuators.ARCH = arm7tdmi setup_actuators.TARGET = setup_actuators setup_actuators.TARGETDIR = setup_actuators setup_actuators.CFLAGS += -DFBW -DBOARD_CONFIG=\"tiny.h\" -DLED -DTIME_LED=1 -DACTUATORS=\"servos_4015_hw.h\" -DSERVOS_4015 -DUSE_UART1 -DUART1_BAUD=B9600 -DDATALINK=PPRZ -DPPRZ_UART=Uart1 setup_actuators.srcs += sys_time.c $(SRC_ARCH)/sys_time_hw.c $(SRC_ARCH)/armVIC.c pprz_transport.c setup_actuators.c $(SRC_ARCH)/uart_hw.c $(SRC_ARCH)/servos_4015_hw.c main.c
From MAILER-DAEMON Wed Aug 19 02:19:19 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MdeVy-0002i2-TO for mharc-paparazzi-devel@gnu.org; Wed, 19 Aug 2009 02:19:18 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MdeVw-0002dY-TH for paparazzi-devel@nongnu.org; Wed, 19 Aug 2009 02:19:16 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MdeVq-0002TO-R4 for paparazzi-devel@nongnu.org; Wed, 19 Aug 2009 02:19:15 -0400 Received: from [199.232.76.173] (port=55655 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MdeVq-0002TA-La for paparazzi-devel@nongnu.org; Wed, 19 Aug 2009 02:19:10 -0400 Received: from ey-out-1920.google.com ([74.125.78.145]:39702) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MdeVp-0005N0-N2 for paparazzi-devel@nongnu.org; Wed, 19 Aug 2009 02:19:10 -0400 Received: by ey-out-1920.google.com with SMTP id 5so783235eyb.4 for ; Tue, 18 Aug 2009 23:19:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=osHCROsuBRPCxff7QPBSpGdV8/GKZw0FPf6MShDghqk=; b=pGMp9wt+tWj4QRsyC8l10feU79jXQJMuJV3p6g1XVtX9hos2gFXIEb565JLTwSpql0 e7Mshdw2bm359KM/oyR2CeD8yU/aQ9Elqs+tpz7izpR0fNMMbkxWh7xQ0k5E4kXsN1Z6 1M4g1xXqJX039w3KgxoTzeWQRubDY72WHFj/k= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=hmZsMQK8m6MvgIdaZhAWZCPcpvzhG0a/6dj4IvXFv9fePAw/F7WTK39C5wP3H9f1KY 2NswzetfbV54QLzXabi9SaZcrslJbuNnJnncVAfGbHS+L8SMBwmh18AJprRSwhrKmFa7 DcJ2BuvJsnMuMo44RkJkGZXZ9P33Y3Bvl/CO4= Received: by 10.210.136.1 with SMTP id j1mr5397798ebd.74.1250662748082; Tue, 18 Aug 2009 23:19:08 -0700 (PDT) Received: from ?192.168.25.50? (213-238-236.netrun.cytanet.com.cy [213.7.238.236]) by mx.google.com with ESMTPS id 7sm2348689eyb.30.2009.08.18.23.19.05 (version=SSLv3 cipher=RC4-MD5); Tue, 18 Aug 2009 23:19:07 -0700 (PDT) Message-ID: <4A8B995A.90703@gmail.com> Date: Wed, 19 Aug 2009 09:19:06 +0300 From: David Carlson User-Agent: Thunderbird 2.0.0.22 (X11/20090608) MIME-Version: 1.0 To: paparazzi-devel@nongnu.org Subject: Re: [Paparazzi-devel] Can't get XBee's to work with PPRZ References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Aug 2009 06:19:17 -0000 Maik, The only thing I can think of is that you need to set one of the XBee units to coordinator (usually the ground modem). This can be done in XCTU or just on a serial port by issuing: "+++", it will say "OK". Then type "ATCE 1" and "ATWR". The only other thing is to make sure they are on the same PAN. This can be queried with "ATID" and set with "ATID 1234" or whatever PAN ID you want. If that doesn't work for you, let me know and we can dig deeper. Buzz Maik Höpfel wrote: > Good evening, > > I've spent all day trying to get my two XBee Pro 2.4 GHz modules to > work with Paparazzi, but failed :( They're the ones CheBuzz sells, so > one with a SparkFun USB board, the other one with the LadyAda breakout > board. > > I flashed the newest firmware on them & have them on defaults (9600 > baud and everything), just a custom network ID. I can send messages > back and forth between them, from the same computer or two different > ones. One modem is connected with a FTDI cable, obviously. > > I have the newest Paparazzi version from the repos, and am using the > MJ5 A/C with funjet1.xml as aircraft config. I adapted the funjet1.xml > to serial communication as described in > http://paparazzi.enac.fr/wiki/Airframe_Configuration. That means I > changed the DATALINK section and replaced the appropriate makefile > part. I changed the baud rate to 9600 bauds and could connect to the > TWOG with my SparkFun FTDI cable (the one I used for the modem as > well). GCS was working well, I could move waypoints and it seems to > have uploaded them. > Then I hooked up the modem. I'm pretty sure I did it right, because I > used the same cable between TWOG to modem as I did for TWOG to FTDI > breakout board. The green LED blinks, so it all seems well. The other > modem even flashes the RX led, and I do get a few scrambled characters > every now and then when I listen in to the serial communication. But > the GCS does not react, it just stays grey. When I write on the serial > line, the receiving modem lights up the RSS light, which it also does > when it's receiving something. > > I then commented out the "XBEE INIT" part in the funjet1.xml config, > guessing that that might mess up things. I also toyed with the > XBEE_NO_INIT flag, but to no avail. No reaction from the GCS. > > I then figured I might try the MaxStream API mode. So I reverted the > funjet1.xml to its original state and tried connecting. But again, I > did not get a reaction from the GCS. Am I right in assuming that PPRZ > changes the settings on both XBees to API mode? The XBEE_INIT string > seems to suggest that, as well as that the ground modem was in API > mode after I started a Flight @ MaxBee ... session. I'm not sure that > I tried every possible combination there, but it seems to be that API > mode is not the recommended way to go anyhow if I'm getting started. > > So I'm completely at loss, and am hoping I'm missing something > obvious. I'm very new to Paparazzi, so that could absolutely be the > case. > > I powered the TWOG both from a 5V supply (which is not ideal, I know - > but so convenient) and a 3S LiPo battery. I also checked for error > messages, but there were none. When there's no reaction from the GCS, > the data logs for that session are empty as well. And of course I > reflashed the TWOG in between my different tries. > > - Maik > > I'm appending the two configs used: > > ===================== My try with serial communication > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > >
> > > > > > > > > >
> > >
> >
> > > > > > > > >
> >
> > > > > > > > > > > > > > > > > > > >
> >
> > > > > > > value="3.3*1000./1024./(GYRO_ADXRS300_SENSITIVITY*GYRO_ADXRS300_RESISTOR_BRIDGE)" > unit="deg/s/adc_unit"/> > >
> >
> > > >
> >
> > > > > > > > > > > > > >
> >
> > > > > > > > > > > > > > unit="%/(m/s)"/> > > > > > > > > > > > > >
> >
> > > > > > > > > > > > > > > > > >
> >
> > >
> >
> > > > > > > > >
> > >
> > > > > > >
> >
> > > > > >
> >
> > >
> > >
> > > > > > > > > > > >
> > > CONFIG = \"tiny_2_1.h\" > > include $(PAPARAZZI_SRC)/conf/autopilot/tiny.makefile > > FLASH_MODE=IAP > > ap.CFLAGS += -DFBW -DAP -DBOARD_CONFIG=$(CONFIG) -DLED -DTIME_LED=1 > ap.srcs = sys_time.c $(SRC_ARCH)/sys_time_hw.c $(SRC_ARCH)/armVIC.c > main_fbw.c main_ap.c main.c > > ap.srcs += commands.c > > ap.CFLAGS += -DACTUATORS=\"servos_4017_hw.h\" -DSERVOS_4017 > ap.srcs += $(SRC_ARCH)/servos_4017_hw.c actuators.c > > ap.CFLAGS += -DRADIO_CONTROL > ap.srcs += radio_control.c $(SRC_ARCH)/ppm_hw.c > > # Serial modem > ap.CFLAGS += -DDOWNLINK -DUSE_UART1 -DDOWNLINK_TRANSPORT=PprzTransport > -DDOWNLINK_FBW_DEVICE=Uart1 -DDOWNLINK_AP_DEVICE=Uart1 > -DPPRZ_UART=Uart1 -DDATALINK=PPRZ -DUART1_BAUD=B9600 > ap.srcs += downlink.c $(SRC_ARCH)/uart_hw.c datalink.c pprz_transport.c > > > #TRANSPARENT > #ap.CFLAGS += -DDOWNLINK -DUSE_UART1 > -DDOWNLINK_TRANSPORT=PprzTransport -DDOWNLINK_FBW_DEVICE=Uart1 > -DDOWNLINK_AP_DEVICE=Uart1 -DPPRZ_UART=Uart1 -DDATALINK=PPRZ > -DUART1_BAUD=B9600 > #ap.srcs += downlink.c $(SRC_ARCH)/uart_hw.c datalink.c pprz_transport.c > > > ap.CFLAGS += -DINTER_MCU > ap.srcs += inter_mcu.c > > ap.CFLAGS += -DADC -DUSE_ADC_0 -DUSE_ADC_1 -DUSE_ADC_2 -DUSE_ADC_3 > ap.srcs += $(SRC_ARCH)/adc_hw.c > > ap.CFLAGS += -DGPS -DUBX -DUSE_UART0 -DGPS_LINK=Uart0 -DUART0_BAUD=B38400 > # -DGPS_LED=2 > ap.srcs += gps_ubx.c gps.c latlong.c > > ap.CFLAGS += -DINFRARED -DALT_KALMAN > ap.srcs += infrared.c estimator.c > > ap.CFLAGS += -DNAV -DAGR_CLIMB -DLOITER_TRIM > ap.srcs += nav.c fw_h_ctl_a.c fw_v_ctl.c > > > ap.CFLAGS += -DGYRO -DADXRS150 > ap.srcs += gyro.c nav_line.c > ap.srcs += nav_survey_rectangle.c > # chemotaxis.c anemotaxis.c discsurvey.c > > ########## Barometer (SPI) > #ap.CFLAGS += -DUSE_SPI -DSPI_MASTER -DUSE_SPI_SLAVE0 -DUSE_BARO_MS5534A > #ap.srcs += spi.c $(SRC_ARCH)/spi_hw.c $(SRC_ARCH)/baro_MS5534A.c > > ########## Chemo sensor (I2C) > #ap.srcs += i2c.c $(SRC_ARCH)/i2c_hw.c > #ap.CFLAGS += -DUSE_I2C -DUSE_I2C0 > > # Digital camera > # Shutter: I2C SCL > # Zoom: I2C SDA > ap.CFLAGS += -DDIGITAL_CAM > ap.srcs += dc.c > > ap.CFLAGS += -DUSE_MODULES > sim.CFLAGS += -DUSE_MODULES > > # Config for SITL simulation > #include $(PAPARAZZI_SRC)/conf/autopilot/sitl.makefile > sim.ARCHDIR = $(ARCHI) > sim.ARCH = sitl > sim.TARGET = autopilot > sim.TARGETDIR = autopilot > sim.CFLAGS += -DSITL -DAP -DFBW -DRADIO_CONTROL -DINTER_MCU -DDOWNLINK > -DDOWNLINK_TRANSPORT=IvyTransport -DINFRARED -DNAV -DLED -DWIND_INFO > sim.srcs = latlong.c radio_control.c downlink.c commands.c gps.c > inter_mcu.c infrared.c fw_h_ctl_a.c fw_v_ctl.c nav.c estimator.c > sys_time.c main_fbw.c main_ap.c datalink.c $(SRC_ARCH)/ppm_hw.c > $(SRC_ARCH)/sim_gps.c $(SRC_ARCH)/sim_ir.c $(SRC_ARCH)/sim_ap.c > $(SRC_ARCH)/ivy_transport.c $(SRC_ARCH)/sim_adc_generic.c > $(SRC_ARCH)/led_hw.c > > sim.CFLAGS += -DBOARD_CONFIG=\"tiny.h\" -DAGR_CLIMB -DLOITER_TRIM -DALT_KALMAN > > sim.srcs += nav_line.c nav_survey_rectangle.c > # -DENOSE > #sim.srcs += i2c.c $(SRC_ARCH)/i2c_hw.c > #sim.CFLAGS += -DUSE_I2C -DUSE_I2C0 > # chemotaxis.c anemotaxis.c discsurvey.c $(SRC_ARCH)/sim_enose.c chemo_detect.c > > sim.CFLAGS += -DDIGITAL_CAM -DPOWER_SWITCH_LED=4 > sim.srcs += dc.c > > > > # a test program to setup actuators > setup_actuators.ARCHDIR = $(ARCHI) > setup_actuators.ARCH = arm7tdmi > setup_actuators.TARGET = setup_actuators > setup_actuators.TARGETDIR = setup_actuators > > setup_actuators.CFLAGS += -DFBW -DBOARD_CONFIG=\"tiny.h\" -DLED > -DTIME_LED=1 -DACTUATORS=\"servos_4015_hw.h\" -DSERVOS_4015 > -DUSE_UART1 -DUART1_BAUD=B9600 -DDATALINK=PPRZ -DPPRZ_UART=Uart1 > setup_actuators.srcs += sys_time.c $(SRC_ARCH)/sys_time_hw.c > $(SRC_ARCH)/armVIC.c pprz_transport.c setup_actuators.c > $(SRC_ARCH)/uart_hw.c $(SRC_ARCH)/servos_4015_hw.c main.c > > >
> > ===================== My try with MaxStream API mode > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > >
> > > > > > > > > >
> > >
> >
> > > > > > > > >
> >
> > > > > > > > > > > > > > > > > > > >
> >
> > > > > > > value="3.3*1000./1024./(GYRO_ADXRS300_SENSITIVITY*GYRO_ADXRS300_RESISTOR_BRIDGE)" > unit="deg/s/adc_unit"/> > >
> >
> > > >
> >
> > > > > > > > > > > > > >
> >
> > > > > > > > > > > > > > unit="%/(m/s)"/> > > > > > > > > > > > > >
> >
> > > > > > > > > > > > > > > > > >
> >
> > >
> >
> > > > > > > > >
> > >
> > > > > > >
> >
> > > > > >
> > >
> > >
> > >
> > > > > > > > > > > >
> > > CONFIG = \"tiny_2_1.h\" > > include $(PAPARAZZI_SRC)/conf/autopilot/tiny.makefile > > FLASH_MODE=IAP > > ap.CFLAGS += -DFBW -DAP -DBOARD_CONFIG=$(CONFIG) -DLED -DTIME_LED=1 > ap.srcs = sys_time.c $(SRC_ARCH)/sys_time_hw.c $(SRC_ARCH)/armVIC.c > main_fbw.c main_ap.c main.c > > ap.srcs += commands.c > > ap.CFLAGS += -DACTUATORS=\"servos_4017_hw.h\" -DSERVOS_4017 > ap.srcs += $(SRC_ARCH)/servos_4017_hw.c actuators.c > > ap.CFLAGS += -DRADIO_CONTROL > ap.srcs += radio_control.c $(SRC_ARCH)/ppm_hw.c > > ap.CFLAGS += -DDOWNLINK -DUSE_UART1 -DDOWNLINK_TRANSPORT=XBeeTransport > -DXBEE_UART=Uart1 -DDATALINK=XBEE -DUART1_BAUD=B9600 > ap.srcs += downlink.c $(SRC_ARCH)/uart_hw.c datalink.c xbee.c > > #TRANSPARENT > #ap.CFLAGS += -DDOWNLINK -DUSE_UART1 > -DDOWNLINK_TRANSPORT=PprzTransport -DDOWNLINK_FBW_DEVICE=Uart1 > -DDOWNLINK_AP_DEVICE=Uart1 -DPPRZ_UART=Uart1 -DDATALINK=PPRZ > -DUART1_BAUD=B9600 > #ap.srcs += downlink.c $(SRC_ARCH)/uart_hw.c datalink.c pprz_transport.c > > > ap.CFLAGS += -DINTER_MCU > ap.srcs += inter_mcu.c > > ap.CFLAGS += -DADC -DUSE_ADC_0 -DUSE_ADC_1 -DUSE_ADC_2 -DUSE_ADC_3 > ap.srcs += $(SRC_ARCH)/adc_hw.c > > ap.CFLAGS += -DGPS -DUBX -DUSE_UART0 -DGPS_LINK=Uart0 -DUART0_BAUD=B38400 > # -DGPS_LED=2 > ap.srcs += gps_ubx.c gps.c latlong.c > > ap.CFLAGS += -DINFRARED -DALT_KALMAN > ap.srcs += infrared.c estimator.c > > ap.CFLAGS += -DNAV -DAGR_CLIMB -DLOITER_TRIM > ap.srcs += nav.c fw_h_ctl_a.c fw_v_ctl.c > > > ap.CFLAGS += -DGYRO -DADXRS150 > ap.srcs += gyro.c nav_line.c > ap.srcs += nav_survey_rectangle.c > # chemotaxis.c anemotaxis.c discsurvey.c > > ########## Barometer (SPI) > #ap.CFLAGS += -DUSE_SPI -DSPI_MASTER -DUSE_SPI_SLAVE0 -DUSE_BARO_MS5534A > #ap.srcs += spi.c $(SRC_ARCH)/spi_hw.c $(SRC_ARCH)/baro_MS5534A.c > > ########## Chemo sensor (I2C) > #ap.srcs += i2c.c $(SRC_ARCH)/i2c_hw.c > #ap.CFLAGS += -DUSE_I2C -DUSE_I2C0 > > # Digital camera > # Shutter: I2C SCL > # Zoom: I2C SDA > ap.CFLAGS += -DDIGITAL_CAM > ap.srcs += dc.c > > ap.CFLAGS += -DUSE_MODULES > sim.CFLAGS += -DUSE_MODULES > > # Config for SITL simulation > #include $(PAPARAZZI_SRC)/conf/autopilot/sitl.makefile > sim.ARCHDIR = $(ARCHI) > sim.ARCH = sitl > sim.TARGET = autopilot > sim.TARGETDIR = autopilot > sim.CFLAGS += -DSITL -DAP -DFBW -DRADIO_CONTROL -DINTER_MCU -DDOWNLINK > -DDOWNLINK_TRANSPORT=IvyTransport -DINFRARED -DNAV -DLED -DWIND_INFO > sim.srcs = latlong.c radio_control.c downlink.c commands.c gps.c > inter_mcu.c infrared.c fw_h_ctl_a.c fw_v_ctl.c nav.c estimator.c > sys_time.c main_fbw.c main_ap.c datalink.c $(SRC_ARCH)/ppm_hw.c > $(SRC_ARCH)/sim_gps.c $(SRC_ARCH)/sim_ir.c $(SRC_ARCH)/sim_ap.c > $(SRC_ARCH)/ivy_transport.c $(SRC_ARCH)/sim_adc_generic.c > $(SRC_ARCH)/led_hw.c > > sim.CFLAGS += -DBOARD_CONFIG=\"tiny.h\" -DAGR_CLIMB -DLOITER_TRIM -DALT_KALMAN > > sim.srcs += nav_line.c nav_survey_rectangle.c > # -DENOSE > #sim.srcs += i2c.c $(SRC_ARCH)/i2c_hw.c > #sim.CFLAGS += -DUSE_I2C -DUSE_I2C0 > # chemotaxis.c anemotaxis.c discsurvey.c $(SRC_ARCH)/sim_enose.c chemo_detect.c > > sim.CFLAGS += -DDIGITAL_CAM -DPOWER_SWITCH_LED=4 > sim.srcs += dc.c > > > > # a test program to setup actuators > setup_actuators.ARCHDIR = $(ARCHI) > setup_actuators.ARCH = arm7tdmi > setup_actuators.TARGET = setup_actuators > setup_actuators.TARGETDIR = setup_actuators > > setup_actuators.CFLAGS += -DFBW -DBOARD_CONFIG=\"tiny.h\" -DLED > -DTIME_LED=1 -DACTUATORS=\"servos_4015_hw.h\" -DSERVOS_4015 > -DUSE_UART1 -DUART1_BAUD=B9600 -DDATALINK=PPRZ -DPPRZ_UART=Uart1 > setup_actuators.srcs += sys_time.c $(SRC_ARCH)/sys_time_hw.c > $(SRC_ARCH)/armVIC.c pprz_transport.c setup_actuators.c > $(SRC_ARCH)/uart_hw.c $(SRC_ARCH)/servos_4015_hw.c main.c > > >
> > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > From MAILER-DAEMON Wed Aug 19 04:40:04 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MdgiC-0002b5-9I for mharc-paparazzi-devel@gnu.org; Wed, 19 Aug 2009 04:40:04 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MdgiA-0002Zd-4L for paparazzi-devel@nongnu.org; Wed, 19 Aug 2009 04:40:02 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mdgi5-0002Vk-GF for paparazzi-devel@nongnu.org; Wed, 19 Aug 2009 04:40:01 -0400 Received: from [199.232.76.173] (port=54707 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mdgi5-0002Vd-9b for paparazzi-devel@nongnu.org; Wed, 19 Aug 2009 04:39:57 -0400 Received: from mail-yx0-f188.google.com ([209.85.210.188]:51565) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Mdgi4-00085f-K8 for paparazzi-devel@nongnu.org; Wed, 19 Aug 2009 04:39:57 -0400 Received: by yxe26 with SMTP id 26so5466466yxe.4 for ; Wed, 19 Aug 2009 01:39:55 -0700 (PDT) MIME-Version: 1.0 Sender: maik@zackbumm.biz Received: by 10.91.177.15 with SMTP id e15mr4631053agp.74.1250671195215; Wed, 19 Aug 2009 01:39:55 -0700 (PDT) In-Reply-To: <4A8B995A.90703@gmail.com> References: <4A8B995A.90703@gmail.com> From: =?UTF-8?B?TWFpayBIw7ZwZmVs?= Date: Wed, 19 Aug 2009 10:39:35 +0200 X-Google-Sender-Auth: 7102dbc65766ae77 Message-ID: Subject: Re: [Paparazzi-devel] Can't get XBee's to work with PPRZ To: paparazzi-devel@nongnu.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Aug 2009 08:40:02 -0000 Hello David and dear Paparazzi community, I hate to say it, but setting the coordinator mode didn't make a difference. I also reconfirmed that serial really is not working by resetting the modems to default settings. They can talk to each other, but not between the TWOG and my computer. FTDI to TWOG still works. I also tried a baud rate of 57600 (set it in the modems and Paparazzi center, of course). And again, worked with FTDI, but not with the modems. I also tried sending binary files between the modems yesterday, via echo and cat. That worked to some extent, the files were never quite the right file size. I'm guessing there's some packet loss or it interprets some byte sequences as AT commands. Hope you can help, Maik 2009/8/19 David Carlson : > Maik, > > The only thing I can think of is that you need to set one of the XBee uni= ts > to coordinator (usually the ground modem). =C2=A0This can be done in XCTU= or just > on a serial port by issuing: "+++", it will say "OK". =C2=A0Then t= ype > "ATCE 1" and "ATWR". =C2=A0The only other thing is to make = sure > they are on the same PAN. =C2=A0This can be queried with =C2=A0"ATID" and set > with "ATID 1234" or whatever PAN ID you want. > > If that doesn't work for you, let me know and we can dig deeper. > > Buzz > > > Maik H=C3=B6pfel wrote: >> >> Good evening, >> I've spent all day trying to get my two XBee Pro 2.4 GHz modules to >> work with Paparazzi, but failed :( They're the ones CheBuzz sells, so >> one with a SparkFun USB board, the other one with the LadyAda breakout >> board. >> >> I flashed the newest firmware on them & have them on defaults (9600 >> baud and everything), just a custom network ID. I can send messages >> back and forth between them, from the same computer or two different >> ones. One modem is connected with a FTDI cable, obviously. >> >> I have the newest Paparazzi version from the repos, and am using the >> MJ5 A/C with funjet1.xml as aircraft config. I adapted the funjet1.xml >> to serial communication as described in >> http://paparazzi.enac.fr/wiki/Airframe_Configuration. That means I >> changed the DATALINK section and replaced the appropriate makefile >> part. I changed the baud rate to 9600 bauds and could connect to the >> TWOG with my SparkFun FTDI cable (the one I used for the modem as >> well). GCS was working well, I could move waypoints and it seems to >> have uploaded them. >> Then I hooked up the modem. I'm pretty sure I did it right, because I >> used the same cable between TWOG to modem as I did for TWOG to FTDI >> breakout board. The green LED blinks, so it all seems well. The other >> modem even flashes the RX led, and I do get a few scrambled characters >> every now and then when I listen in to the serial communication. But >> the GCS does not react, it just stays grey. When I write on the serial >> line, the receiving modem lights up the RSS light, which it also does >> when it's receiving something. >> >> I then commented out the "XBEE INIT" part in the funjet1.xml config, >> guessing that that might mess up things. I also toyed with the >> XBEE_NO_INIT flag, but to no avail. No reaction from the GCS. >> >> I then figured I might try the MaxStream API mode. So I reverted the >> funjet1.xml to its original state and tried connecting. But again, I >> did not get a reaction from the GCS. Am I right in assuming that PPRZ >> changes the settings on both XBees to API mode? The XBEE_INIT string >> seems to suggest that, as well as that the ground modem was in API >> mode after I started a Flight @ MaxBee ... session. I'm not sure that >> I tried every possible combination there, but it seems to be that API >> mode is not the recommended way to go anyhow if I'm getting started. >> >> So I'm completely at loss, and am hoping I'm missing something >> obvious. I'm very new to Paparazzi, so that could absolutely be the >> case. >> >> I powered the TWOG both from a 5V supply (which is not ideal, I know - >> but so convenient) and a 3S LiPo battery. I also checked for error >> messages, but there were none. When there's no reaction from the GCS, >> the data logs for that session are empty as well. And of course I >> reflashed the TWOG in between my different tries. >> >> - Maik >> >> I'm appending the two configs used: >> >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D My try w= ith serial communication >> >> >> >> >> >> >> =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 >> >> >> =C2=A0 >> =C2=A0 =C2=A0> max=3D"2000"/> >> =C2=A0 =C2=A0> max=3D"1880"/> >> =C2=A0 =C2=A0> max=3D"1170"/> >> =C2=A0 >> >> =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 >> >> =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 >> >> =C2=A0
>> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0
>> >> =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 >> >> =C2=A0
>> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0
>> >> =C2=A0
>> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> >> =C2=A0
>> >> =C2=A0
>> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0
>> >> =C2=A0
>> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0> >> value=3D"3.3*1000./1024./(GYRO_ADXRS300_SENSITIVITY*GYRO_ADXRS300_RESIST= OR_BRIDGE)" >> unit=3D"deg/s/adc_unit"/> >> =C2=A0 =C2=A0 >> =C2=A0
>> >> =C2=A0
>> =C2=A0 =C2=A0 >> >> =C2=A0 =C2=A0 >> =C2=A0
>> >> =C2=A0
>> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0
>> >> =C2=A0
>> >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0> unit=3D"%/(m/s)"/> >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> >> =C2=A0 >> >> =C2=A0
>> >> =C2=A0
>> =C2=A0 =C2=A0 >> >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> >> =C2=A0 =C2=A0 >> >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0
>> >> =C2=A0
>> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0
>> >> =C2=A0
>> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0
>> >> >> =C2=A0
>> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0
>> >> =C2=A0
>> =C2=A0 =C2=A0 =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 =C2=A0 =C2=A0 >>
>> >> =C2=A0
>> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0
>> >> >> =C2=A0
>> =C2=A0 =C2=A0 >> >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0
>> >> =C2=A0 >> CONFIG =3D \"tiny_2_1.h\" >> >> include $(PAPARAZZI_SRC)/conf/autopilot/tiny.makefile >> >> FLASH_MODE=3DIAP >> >> ap.CFLAGS +=3D =C2=A0-DFBW -DAP -DBOARD_CONFIG=3D$(CONFIG) -DLED -DTIME_= LED=3D1 >> ap.srcs =3D sys_time.c $(SRC_ARCH)/sys_time_hw.c $(SRC_ARCH)/armVIC.c >> main_fbw.c main_ap.c main.c >> >> ap.srcs +=3D commands.c >> >> ap.CFLAGS +=3D -DACTUATORS=3D\"servos_4017_hw.h\" -DSERVOS_4017 >> ap.srcs +=3D $(SRC_ARCH)/servos_4017_hw.c actuators.c >> >> ap.CFLAGS +=3D -DRADIO_CONTROL >> ap.srcs +=3D radio_control.c $(SRC_ARCH)/ppm_hw.c >> >> # Serial modem >> ap.CFLAGS +=3D -DDOWNLINK -DUSE_UART1 -DDOWNLINK_TRANSPORT=3DPprzTranspo= rt >> -DDOWNLINK_FBW_DEVICE=3DUart1 -DDOWNLINK_AP_DEVICE=3DUart1 >> -DPPRZ_UART=3DUart1 -DDATALINK=3DPPRZ -DUART1_BAUD=3DB9600 >> ap.srcs +=3D downlink.c $(SRC_ARCH)/uart_hw.c datalink.c pprz_transport.= c >> >> >> #TRANSPARENT >> #ap.CFLAGS +=3D -DDOWNLINK -DUSE_UART1 >> -DDOWNLINK_TRANSPORT=3DPprzTransport -DDOWNLINK_FBW_DEVICE=3DUart1 >> -DDOWNLINK_AP_DEVICE=3DUart1 -DPPRZ_UART=3DUart1 -DDATALINK=3DPPRZ >> -DUART1_BAUD=3DB9600 >> #ap.srcs +=3D downlink.c $(SRC_ARCH)/uart_hw.c datalink.c pprz_transport= .c >> >> >> ap.CFLAGS +=3D -DINTER_MCU >> ap.srcs +=3D inter_mcu.c >> >> ap.CFLAGS +=3D -DADC -DUSE_ADC_0 -DUSE_ADC_1 -DUSE_ADC_2 -DUSE_ADC_3 >> ap.srcs +=3D $(SRC_ARCH)/adc_hw.c >> >> ap.CFLAGS +=3D -DGPS -DUBX -DUSE_UART0 -DGPS_LINK=3DUart0 -DUART0_BAUD= =3DB38400 >> # -DGPS_LED=3D2 >> ap.srcs +=3D gps_ubx.c gps.c latlong.c >> >> ap.CFLAGS +=3D -DINFRARED -DALT_KALMAN >> ap.srcs +=3D infrared.c estimator.c >> >> ap.CFLAGS +=3D -DNAV -DAGR_CLIMB -DLOITER_TRIM >> ap.srcs +=3D nav.c fw_h_ctl_a.c fw_v_ctl.c >> >> >> ap.CFLAGS +=3D -DGYRO -DADXRS150 >> ap.srcs +=3D gyro.c nav_line.c >> ap.srcs +=3D nav_survey_rectangle.c >> # chemotaxis.c anemotaxis.c discsurvey.c >> >> ########## Barometer (SPI) >> #ap.CFLAGS +=3D -DUSE_SPI -DSPI_MASTER -DUSE_SPI_SLAVE0 -DUSE_BARO_MS553= 4A >> #ap.srcs +=3D spi.c $(SRC_ARCH)/spi_hw.c $(SRC_ARCH)/baro_MS5534A.c >> >> ########## Chemo sensor (I2C) >> #ap.srcs +=3D i2c.c $(SRC_ARCH)/i2c_hw.c >> #ap.CFLAGS +=3D -DUSE_I2C -DUSE_I2C0 >> >> # Digital camera >> # Shutter: I2C SCL >> # Zoom: I2C SDA >> ap.CFLAGS +=3D -DDIGITAL_CAM >> ap.srcs +=3D dc.c >> >> ap.CFLAGS +=3D -DUSE_MODULES >> sim.CFLAGS +=3D -DUSE_MODULES >> >> # Config for SITL simulation >> #include $(PAPARAZZI_SRC)/conf/autopilot/sitl.makefile >> sim.ARCHDIR =3D $(ARCHI) >> sim.ARCH =3D sitl >> sim.TARGET =3D autopilot >> sim.TARGETDIR =3D autopilot >> sim.CFLAGS +=3D -DSITL -DAP -DFBW -DRADIO_CONTROL -DINTER_MCU -DDOWNLINK >> -DDOWNLINK_TRANSPORT=3DIvyTransport -DINFRARED -DNAV -DLED -DWIND_INFO >> sim.srcs =3D latlong.c radio_control.c downlink.c commands.c gps.c >> inter_mcu.c infrared.c fw_h_ctl_a.c fw_v_ctl.c nav.c estimator.c >> sys_time.c main_fbw.c main_ap.c datalink.c $(SRC_ARCH)/ppm_hw.c >> $(SRC_ARCH)/sim_gps.c $(SRC_ARCH)/sim_ir.c $(SRC_ARCH)/sim_ap.c >> $(SRC_ARCH)/ivy_transport.c $(SRC_ARCH)/sim_adc_generic.c >> $(SRC_ARCH)/led_hw.c >> >> sim.CFLAGS +=3D -DBOARD_CONFIG=3D\"tiny.h\" -DAGR_CLIMB -DLOITER_TRIM >> -DALT_KALMAN >> >> sim.srcs +=3D nav_line.c nav_survey_rectangle.c >> # -DENOSE >> #sim.srcs +=3D i2c.c $(SRC_ARCH)/i2c_hw.c >> #sim.CFLAGS +=3D -DUSE_I2C -DUSE_I2C0 >> # chemotaxis.c anemotaxis.c discsurvey.c $(SRC_ARCH)/sim_enose.c >> chemo_detect.c >> >> sim.CFLAGS +=3D -DDIGITAL_CAM -DPOWER_SWITCH_LED=3D4 >> sim.srcs +=3D dc.c >> >> >> >> # a test program to setup actuators >> setup_actuators.ARCHDIR =3D $(ARCHI) >> setup_actuators.ARCH =3D arm7tdmi >> setup_actuators.TARGET =3D setup_actuators >> setup_actuators.TARGETDIR =3D setup_actuators >> >> setup_actuators.CFLAGS +=3D -DFBW -DBOARD_CONFIG=3D\"tiny.h\" -DLED >> -DTIME_LED=3D1 -DACTUATORS=3D\"servos_4015_hw.h\" -DSERVOS_4015 >> -DUSE_UART1 -DUART1_BAUD=3DB9600 -DDATALINK=3DPPRZ -DPPRZ_UART=3DUart1 >> setup_actuators.srcs +=3D sys_time.c $(SRC_ARCH)/sys_time_hw.c >> $(SRC_ARCH)/armVIC.c pprz_transport.c setup_actuators.c >> $(SRC_ARCH)/uart_hw.c $(SRC_ARCH)/servos_4015_hw.c main.c >> >> =C2=A0 >>
>> >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D My try w= ith MaxStream API mode >> >> >> >> >> >> >> =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 >> >> >> =C2=A0 >> =C2=A0 =C2=A0> max=3D"2000"/> >> =C2=A0 =C2=A0> max=3D"1880"/> >> =C2=A0 =C2=A0> max=3D"1170"/> >> =C2=A0 >> >> =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 >> >> =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 >> >> =C2=A0
>> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0
>> >> =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 >> >> =C2=A0
>> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0
>> >> =C2=A0
>> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> >> =C2=A0
>> >> =C2=A0
>> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0
>> >> =C2=A0
>> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0> >> value=3D"3.3*1000./1024./(GYRO_ADXRS300_SENSITIVITY*GYRO_ADXRS300_RESIST= OR_BRIDGE)" >> unit=3D"deg/s/adc_unit"/> >> =C2=A0 =C2=A0 >> =C2=A0
>> >> =C2=A0
>> =C2=A0 =C2=A0 >> >> =C2=A0 =C2=A0 >> =C2=A0
>> >> =C2=A0
>> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> >> =C2=A0 =C2=A0 >> >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0
>> >> =C2=A0
>> >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0> unit=3D"%/(m/s)"/> >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> >> =C2=A0 >> >> =C2=A0
>> >> =C2=A0
>> =C2=A0 =C2=A0 >> >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> >> =C2=A0 =C2=A0 >> >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0
>> >> =C2=A0
>> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0
>> >> =C2=A0
>> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0
>> >> >> =C2=A0
>> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0
>> >> =C2=A0
>> =C2=A0 =C2=A0 =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 =C2=A0 =C2=A0 >>
>> >> >> =C2=A0
>> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0
>> >> >> =C2=A0
>> =C2=A0 =C2=A0 >> >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> >> =C2=A0 =C2=A0 >> =C2=A0 =C2=A0 >> =C2=A0
>> >> =C2=A0 >> CONFIG =3D \"tiny_2_1.h\" >> >> include $(PAPARAZZI_SRC)/conf/autopilot/tiny.makefile >> >> FLASH_MODE=3DIAP >> >> ap.CFLAGS +=3D =C2=A0-DFBW -DAP -DBOARD_CONFIG=3D$(CONFIG) -DLED -DTIME_= LED=3D1 >> ap.srcs =3D sys_time.c $(SRC_ARCH)/sys_time_hw.c $(SRC_ARCH)/armVIC.c >> main_fbw.c main_ap.c main.c >> >> ap.srcs +=3D commands.c >> >> ap.CFLAGS +=3D -DACTUATORS=3D\"servos_4017_hw.h\" -DSERVOS_4017 >> ap.srcs +=3D $(SRC_ARCH)/servos_4017_hw.c actuators.c >> >> ap.CFLAGS +=3D -DRADIO_CONTROL >> ap.srcs +=3D radio_control.c $(SRC_ARCH)/ppm_hw.c >> >> ap.CFLAGS +=3D -DDOWNLINK -DUSE_UART1 -DDOWNLINK_TRANSPORT=3DXBeeTranspo= rt >> -DXBEE_UART=3DUart1 -DDATALINK=3DXBEE -DUART1_BAUD=3DB9600 >> ap.srcs +=3D downlink.c $(SRC_ARCH)/uart_hw.c datalink.c xbee.c >> >> #TRANSPARENT >> #ap.CFLAGS +=3D -DDOWNLINK -DUSE_UART1 >> -DDOWNLINK_TRANSPORT=3DPprzTransport -DDOWNLINK_FBW_DEVICE=3DUart1 >> -DDOWNLINK_AP_DEVICE=3DUart1 -DPPRZ_UART=3DUart1 -DDATALINK=3DPPRZ >> -DUART1_BAUD=3DB9600 >> #ap.srcs +=3D downlink.c $(SRC_ARCH)/uart_hw.c datalink.c pprz_transport= .c >> >> >> ap.CFLAGS +=3D -DINTER_MCU >> ap.srcs +=3D inter_mcu.c >> >> ap.CFLAGS +=3D -DADC -DUSE_ADC_0 -DUSE_ADC_1 -DUSE_ADC_2 -DUSE_ADC_3 >> ap.srcs +=3D $(SRC_ARCH)/adc_hw.c >> >> ap.CFLAGS +=3D -DGPS -DUBX -DUSE_UART0 -DGPS_LINK=3DUart0 -DUART0_BAUD= =3DB38400 >> # -DGPS_LED=3D2 >> ap.srcs +=3D gps_ubx.c gps.c latlong.c >> >> ap.CFLAGS +=3D -DINFRARED -DALT_KALMAN >> ap.srcs +=3D infrared.c estimator.c >> >> ap.CFLAGS +=3D -DNAV -DAGR_CLIMB -DLOITER_TRIM >> ap.srcs +=3D nav.c fw_h_ctl_a.c fw_v_ctl.c >> >> >> ap.CFLAGS +=3D -DGYRO -DADXRS150 >> ap.srcs +=3D gyro.c nav_line.c >> ap.srcs +=3D nav_survey_rectangle.c >> # chemotaxis.c anemotaxis.c discsurvey.c >> >> ########## Barometer (SPI) >> #ap.CFLAGS +=3D -DUSE_SPI -DSPI_MASTER -DUSE_SPI_SLAVE0 -DUSE_BARO_MS553= 4A >> #ap.srcs +=3D spi.c $(SRC_ARCH)/spi_hw.c $(SRC_ARCH)/baro_MS5534A.c >> >> ########## Chemo sensor (I2C) >> #ap.srcs +=3D i2c.c $(SRC_ARCH)/i2c_hw.c >> #ap.CFLAGS +=3D -DUSE_I2C -DUSE_I2C0 >> >> # Digital camera >> # Shutter: I2C SCL >> # Zoom: I2C SDA >> ap.CFLAGS +=3D -DDIGITAL_CAM >> ap.srcs +=3D dc.c >> >> ap.CFLAGS +=3D -DUSE_MODULES >> sim.CFLAGS +=3D -DUSE_MODULES >> >> # Config for SITL simulation >> #include $(PAPARAZZI_SRC)/conf/autopilot/sitl.makefile >> sim.ARCHDIR =3D $(ARCHI) >> sim.ARCH =3D sitl >> sim.TARGET =3D autopilot >> sim.TARGETDIR =3D autopilot >> sim.CFLAGS +=3D -DSITL -DAP -DFBW -DRADIO_CONTROL -DINTER_MCU -DDOWNLINK >> -DDOWNLINK_TRANSPORT=3DIvyTransport -DINFRARED -DNAV -DLED -DWIND_INFO >> sim.srcs =3D latlong.c radio_control.c downlink.c commands.c gps.c >> inter_mcu.c infrared.c fw_h_ctl_a.c fw_v_ctl.c nav.c estimator.c >> sys_time.c main_fbw.c main_ap.c datalink.c $(SRC_ARCH)/ppm_hw.c >> $(SRC_ARCH)/sim_gps.c $(SRC_ARCH)/sim_ir.c $(SRC_ARCH)/sim_ap.c >> $(SRC_ARCH)/ivy_transport.c $(SRC_ARCH)/sim_adc_generic.c >> $(SRC_ARCH)/led_hw.c >> >> sim.CFLAGS +=3D -DBOARD_CONFIG=3D\"tiny.h\" -DAGR_CLIMB -DLOITER_TRIM >> -DALT_KALMAN >> >> sim.srcs +=3D nav_line.c nav_survey_rectangle.c >> # -DENOSE >> #sim.srcs +=3D i2c.c $(SRC_ARCH)/i2c_hw.c >> #sim.CFLAGS +=3D -DUSE_I2C -DUSE_I2C0 >> # chemotaxis.c anemotaxis.c discsurvey.c $(SRC_ARCH)/sim_enose.c >> chemo_detect.c >> >> sim.CFLAGS +=3D -DDIGITAL_CAM -DPOWER_SWITCH_LED=3D4 >> sim.srcs +=3D dc.c >> >> >> >> # a test program to setup actuators >> setup_actuators.ARCHDIR =3D $(ARCHI) >> setup_actuators.ARCH =3D arm7tdmi >> setup_actuators.TARGET =3D setup_actuators >> setup_actuators.TARGETDIR =3D setup_actuators >> >> setup_actuators.CFLAGS +=3D -DFBW -DBOARD_CONFIG=3D\"tiny.h\" -DLED >> -DTIME_LED=3D1 -DACTUATORS=3D\"servos_4015_hw.h\" -DSERVOS_4015 >> -DUSE_UART1 -DUART1_BAUD=3DB9600 -DDATALINK=3DPPRZ -DPPRZ_UART=3DUart1 >> setup_actuators.srcs +=3D sys_time.c $(SRC_ARCH)/sys_time_hw.c >> $(SRC_ARCH)/armVIC.c pprz_transport.c setup_actuators.c >> $(SRC_ARCH)/uart_hw.c $(SRC_ARCH)/servos_4015_hw.c main.c >> >> =C2=A0 >>
>> >> >> _______________________________________________ >> Paparazzi-devel mailing list >> Paparazzi-devel@nongnu.org >> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel >> > > > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > From MAILER-DAEMON Wed Aug 19 08:46:56 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MdkZ5-0004XC-Uw for mharc-paparazzi-devel@gnu.org; Wed, 19 Aug 2009 08:46:55 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MdkZ4-0004Wh-Em for paparazzi-devel@nongnu.org; Wed, 19 Aug 2009 08:46:54 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MdkYy-0004Ux-Lh for paparazzi-devel@nongnu.org; Wed, 19 Aug 2009 08:46:52 -0400 Received: from [199.232.76.173] (port=59669 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MdkYy-0004Us-Fp for paparazzi-devel@nongnu.org; Wed, 19 Aug 2009 08:46:48 -0400 Received: from mail-fx0-f211.google.com ([209.85.220.211]:56423) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MdkYx-0005VK-EY for paparazzi-devel@nongnu.org; Wed, 19 Aug 2009 08:46:47 -0400 Received: by fxm7 with SMTP id 7so3607497fxm.34 for ; Wed, 19 Aug 2009 05:46:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=U1HTy7E68l9zhehbY9QhREzhkrBqQ9/QRtcoWkuuW44=; b=pGWtzW9XDHRin6/kusYlqL5PviNrPtYiYiO5qph9j7k9j9m/ZwQensvF9MdLOteYy8 1YFPSoYDjeJHuVZqmomdarfovjF5ujP6p5hqJtFwQPyO3AvhL97XD8XgkZpetjtFPEJc /jad8983+is7YKKKugs+AqokTAfuMdVZxZ0o8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=lPMGyV6Nf0TFyyrndlP4UcPguTIwrAyXrw6ZC/bmzDrCEdxAnkUx3/yaTxHMZCckqB jENfx6MJJQZnV2s8pB9iaAqSMslfkKmPt2wvZTnjuNKsf45anczSbmEVwVfewE8Mo8XA 2AZUC4tZzViwYXrihEff1ang4a5Mx0bXpkzYc= Received: by 10.204.141.4 with SMTP id k4mr4938127bku.28.1250686005205; Wed, 19 Aug 2009 05:46:45 -0700 (PDT) Received: from ?192.168.1.2? ([88.218.149.158]) by mx.google.com with ESMTPS id z10sm114825fka.35.2009.08.19.05.46.43 (version=SSLv3 cipher=RC4-MD5); Wed, 19 Aug 2009 05:46:44 -0700 (PDT) Message-ID: <4A8BF432.2020305@gmail.com> Date: Wed, 19 Aug 2009 15:46:42 +0300 From: chris User-Agent: Thunderbird 2.0.0.22 (X11/20090608) MIME-Version: 1.0 To: paparazzi-devel@nongnu.org References: <4a8bbac8.9f53f10a.39fb.0795SMTPIN_ADDED@mx.google.com> In-Reply-To: <4a8bbac8.9f53f10a.39fb.0795SMTPIN_ADDED@mx.google.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) Subject: [Paparazzi-devel] Reply to "Can't get XBee's to work " X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Aug 2009 12:46:54 -0000 If the modems talk to each other when you connect them at say two computers (loopback test) then there is something wrong with the configuration or the connection with the paparazzi. Can you check that the rx line of the modem goes to the tx line of the autopilot and that the modem tx goes to the autopilot's rx? Maybe the wires are wrongly connected at the molex connector. It has happened in the past. Chris From MAILER-DAEMON Wed Aug 19 13:09:12 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Mdoeu-0008CS-Af for mharc-paparazzi-devel@gnu.org; Wed, 19 Aug 2009 13:09:12 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mdoes-0008B3-Gp for paparazzi-devel@nongnu.org; Wed, 19 Aug 2009 13:09:10 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mdoen-0008Ar-41 for paparazzi-devel@nongnu.org; Wed, 19 Aug 2009 13:09:09 -0400 Received: from [199.232.76.173] (port=47351 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mdoem-0008Ao-Su for paparazzi-devel@nongnu.org; Wed, 19 Aug 2009 13:09:04 -0400 Received: from mail-fx0-f211.google.com ([209.85.220.211]:47898) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Mdoem-0003Mi-Ff for paparazzi-devel@nongnu.org; Wed, 19 Aug 2009 13:09:04 -0400 Received: by fxm7 with SMTP id 7so3773768fxm.34 for ; Wed, 19 Aug 2009 10:09:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:content-type :content-transfer-encoding; bh=DO7CtuGxaGMZ0Ag0a6EU0nnqZyYWQPNhzJQ9Z8mRs0Y=; b=O4KV+8Jh6FcLmbhASQMd6px60m1UX64wFlctCjO/6X7Ecpo4kGWhLA/oxaOb7li9B9 oHquUpCPa2qK7TUQbYp04mPMWczutIki/r4GUSs8la0MWyw1QuXajW2x72GdlaY65kvB kaFVMjq2ZlwU/Tia3BDR3aI6paFrckc98b65Q= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; b=CVXNw97B2282u82TJwDvOgnZu1FK/UUa8Rrq63zz/ul4jQj1oqQDNLWV9VE2fmJoWK tnFgAnAyYXDjIUdZFAjQz9yF8cxl2Pc9xuexcJ+97yliY7tByyojIYkJ1w2J5AH4+HfM /v0Mc9hizjjYFnOPbiGwxxka/KM/LgUYPcB+M= Received: by 10.204.7.198 with SMTP id e6mr5138355bke.148.1250701743621; Wed, 19 Aug 2009 10:09:03 -0700 (PDT) Received: from ?192.168.1.2? ([88.218.149.158]) by mx.google.com with ESMTPS id z10sm475505fka.35.2009.08.19.10.09.02 (version=SSLv3 cipher=RC4-MD5); Wed, 19 Aug 2009 10:09:03 -0700 (PDT) Message-ID: <4A8C31AD.8030003@gmail.com> Date: Wed, 19 Aug 2009 20:09:01 +0300 From: chris User-Agent: Thunderbird 2.0.0.22 (X11/20090608) MIME-Version: 1.0 To: paparazzi-devel@nongnu.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) Subject: [Paparazzi-devel] Reply to "Can't get XBee's to work " (chris) #2 X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Aug 2009 17:09:10 -0000 I forgot to mention that if you get garbled characters then try to change the 2.4 Ghz channel. Default is the "C" channel. I had to do it also (i went to "D") as it was messing with my Wifi. Chris From MAILER-DAEMON Wed Aug 19 15:01:15 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MdqPK-0001wF-VZ for mharc-paparazzi-devel@gnu.org; Wed, 19 Aug 2009 15:01:15 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MdqPJ-0001w2-HE for paparazzi-devel@nongnu.org; Wed, 19 Aug 2009 15:01:13 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MdqPE-0001ta-OD for paparazzi-devel@nongnu.org; Wed, 19 Aug 2009 15:01:12 -0400 Received: from [199.232.76.173] (port=33717 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MdqPE-0001tX-LD for paparazzi-devel@nongnu.org; Wed, 19 Aug 2009 15:01:08 -0400 Received: from mail-yx0-f188.google.com ([209.85.210.188]:55333) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MdqPE-00062V-3D for paparazzi-devel@nongnu.org; Wed, 19 Aug 2009 15:01:08 -0400 Received: by yxe26 with SMTP id 26so5876140yxe.4 for ; Wed, 19 Aug 2009 12:01:07 -0700 (PDT) MIME-Version: 1.0 Sender: maik@zackbumm.biz Received: by 10.90.216.7 with SMTP id o7mr5089704agg.45.1250708467555; Wed, 19 Aug 2009 12:01:07 -0700 (PDT) In-Reply-To: <4A8C31AD.8030003@gmail.com> References: <4A8C31AD.8030003@gmail.com> Date: Wed, 19 Aug 2009 21:01:06 +0200 X-Google-Sender-Auth: 18195eeb56a7e21b Message-ID: Subject: Re: [Paparazzi-devel] Reply to "Can't get XBee's to work " (chris) #2 From: =?UTF-8?B?TWFpayBIw7ZwZmVs?= To: paparazzi-devel@nongnu.org Content-Type: multipart/alternative; boundary=001636284dd4ed204d04718341d6 X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Aug 2009 19:01:13 -0000 --001636284dd4ed204d04718341d6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Well, I only get garbled characters when listening in to TWOG to PC, not when trying out communication between the modems. If I'm not mistaken, PPRZ uses a binary protocol, so getting garbled chars doesn't say much, right? But thanks, I'll give it a try and will also try disabling my wifi. 19. Aug 2009 7:09 nachm. schrieb am "chris" : I forgot to mention that if you get garbled characters then try to change the 2.4 Ghz channel. Default is the "C" channel. I had to do it also (i went to "D") as it was messing with my Wifi. Chris _______________________________________________ Paparazzi-devel mailing list Paparazzi-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/paparazzi-devel --001636284dd4ed204d04718341d6 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Well, I only get garbled characters when listening in to TWOG to PC, not= when trying out communication between the modems. If I'm not mistaken,= PPRZ uses a binary protocol, so getting garbled chars doesn't say much= , right? But thanks, I'll give it a try and will also try disabling my = wifi.

19. Aug 2009 7:09 nachm. schrieb am "chri= s" <hendrixgr@gmail.com&= gt;:

I forgot to mention that if you get garbled characters then try= to change the 2.4 Ghz channel.
Default is the "C" channel.
I had to do it also (i went to "D") as it was messing with my Wif= i.
Chris



_______________________________________________
Paparazzi-devel mailing list
Paparazzi-d= evel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/paparazzi-devel

--001636284dd4ed204d04718341d6-- From MAILER-DAEMON Thu Aug 20 04:32:00 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Me33w-0005uH-3B for mharc-paparazzi-devel@gnu.org; Thu, 20 Aug 2009 04:32:00 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Me33u-0005sG-FN for paparazzi-devel@nongnu.org; Thu, 20 Aug 2009 04:31:58 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Me33t-0005s2-UV for paparazzi-devel@nongnu.org; Thu, 20 Aug 2009 04:31:58 -0400 Received: from [199.232.76.173] (port=34137 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Me33t-0005rz-SC for paparazzi-devel@nongnu.org; Thu, 20 Aug 2009 04:31:57 -0400 Received: from ey-out-1920.google.com ([74.125.78.145]:60396) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Me33t-0000pk-CK for paparazzi-devel@nongnu.org; Thu, 20 Aug 2009 04:31:57 -0400 Received: by ey-out-1920.google.com with SMTP id 5so964965eyb.4 for ; Thu, 20 Aug 2009 01:31:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=hPyWWoHL77eik8eMOkzmpVEEouuNHDZgycOoyAwHTCU=; b=m9RMxv4O7USdzTmdb/d2Pel5mLhT1VFm49l+99b05yLQWCjTh0hkJDV+dQAd6lDAZH KVpOEf3lyDHBEFAPb4LJW+iiWjm6GoMecJ56HoDDIS2IcoraBGyp/iHIoqrB4S5/AwxG GkvtOQn4anhy1Cjt+6BMssHr/22DVkrFMxABo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=CBI3UAMJ0yeU+sTu08naOOO8dwLReXz5RGlbnY9/el3sMykehkPNGH0FKlFHyhSMXq kG9MXtw6WA19OfnyFgded21N0latauiAEgwQJ9xsgzfMwqCl5TVRxFTQk3J5czHIF3Hp bhPP4gVVcKNN9lij2thQkHP08DiYXedu8HsEM= MIME-Version: 1.0 Received: by 10.216.39.85 with SMTP id c63mr1759609web.103.1250757115650; Thu, 20 Aug 2009 01:31:55 -0700 (PDT) In-Reply-To: References: <4A8C31AD.8030003@gmail.com> Date: Thu, 20 Aug 2009 10:31:55 +0200 Message-ID: <9e34e1890908200131u5eccdd9evf19db078bd80c8dd@mail.gmail.com> Subject: Re: [Paparazzi-devel] Reply to "Can't get XBee's to work " (chris) #2 From: Gautier Hattenberger To: paparazzi-devel@nongnu.org Content-Type: multipart/alternative; boundary=0016365ee4769423a504718e95ee X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Aug 2009 08:31:58 -0000 --0016365ee4769423a504718e95ee Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hello Maik, If you are using the serial mode, the XBEE_INIT and NO_XBEE_API_INIT won't change anything and the DATALINK section is not even needed (default mode) so you can remove it. If the TWOG sends messages at the right speed (you can check that with an oscilloscope), then the problem can come from the parameters of the link agent. What is the speed of your ground modem ? What are the parameters of link ? Gautier 2009/8/19 Maik H=F6pfel > Well, I only get garbled characters when listening in to TWOG to PC, not > when trying out communication between the modems. If I'm not mistaken, PP= RZ > uses a binary protocol, so getting garbled chars doesn't say much, right? > But thanks, I'll give it a try and will also try disabling my wifi. > > 19. Aug 2009 7:09 nachm. schrieb am "chris" : > > > I forgot to mention that if you get garbled characters then try to change > the 2.4 Ghz channel. > Default is the "C" channel. > I had to do it also (i went to "D") as it was messing with my Wifi. > Chris > > > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > > --0016365ee4769423a504718e95ee Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hello Maik,

If you are using the serial mode, the XBEE_INIT and NO_X= BEE_API_INIT won't change anything and the DATALINK section is not even= needed (default mode) so you can remove it.
If the TWOG sends messages = at the right speed (you can check that with an oscilloscope), then the prob= lem can come from the parameters of the link agent. What is the speed of yo= ur ground modem ? What are the parameters of link ?

Gautier

2009/8/19 Maik H=F6pfel <maik.hoepfel@web.de= >
19. Aug 2009 7:09 nachm. schrieb am "= chris" <he= ndrixgr@gmail.com>:


I forgo= t to mention that if you get garbled characters then try to change the 2.4 = Ghz channel.
Default is the "C" channel.
I had to do it also (i went to "D") as it was messing with my Wif= i.
Chris



_______________________________________________
Paparazzi-devel mailing list
Paparazzi-d= evel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/paparazzi-devel

_______________________________________________
Paparazzi-devel mailing list
Paparazzi-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/paparazzi-devel

--0016365ee4769423a504718e95ee-- From MAILER-DAEMON Thu Aug 20 08:20:52 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Me6dQ-0000PE-6L for mharc-paparazzi-devel@gnu.org; Thu, 20 Aug 2009 08:20:52 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Me6dO-0000Oj-34 for paparazzi-devel@nongnu.org; Thu, 20 Aug 2009 08:20:50 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Me6dJ-0000KA-Ct for paparazzi-devel@nongnu.org; Thu, 20 Aug 2009 08:20:49 -0400 Received: from [199.232.76.173] (port=47220 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Me6dJ-0000Ju-7x for paparazzi-devel@nongnu.org; Thu, 20 Aug 2009 08:20:45 -0400 Received: from mail-yw0-f195.google.com ([209.85.211.195]:42339) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Me6dI-0002Xt-Ra for paparazzi-devel@nongnu.org; Thu, 20 Aug 2009 08:20:45 -0400 Received: by ywh33 with SMTP id 33so3020399ywh.18 for ; Thu, 20 Aug 2009 05:20:43 -0700 (PDT) MIME-Version: 1.0 Sender: maik@zackbumm.biz Received: by 10.90.255.1 with SMTP id c1mr5794731agi.115.1250770843344; Thu, 20 Aug 2009 05:20:43 -0700 (PDT) In-Reply-To: <9e34e1890908200131u5eccdd9evf19db078bd80c8dd@mail.gmail.com> References: <4A8C31AD.8030003@gmail.com> <9e34e1890908200131u5eccdd9evf19db078bd80c8dd@mail.gmail.com> From: =?UTF-8?B?TWFpayBIw7ZwZmVs?= Date: Thu, 20 Aug 2009 14:20:23 +0200 X-Google-Sender-Auth: 7194d53d3a3ab179 Message-ID: Subject: Re: [Paparazzi-devel] Reply to "Can't get XBee's to work " (chris) #2 To: paparazzi-devel@nongnu.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Aug 2009 12:20:50 -0000 Thanks everyone for the competent help, unfortunately it was just me being stupid. Because it worked via FTDI and talking to the modem worked, I assumed I must've wired correctly. Buzz could convince me of the opposite, and now everything is fine. I just had to switch the blue and the green wire ;) Happy flying, Maik 2009/8/20 Gautier Hattenberger : > Hello Maik, > > If you are using the serial mode, the XBEE_INIT and NO_XBEE_API_INIT won'= t > change anything and the DATALINK section is not even needed (default mode= ) > so you can remove it. > If the TWOG sends messages at the right speed (you can check that with an > oscilloscope), then the problem can come from the parameters of the link > agent. What is the speed of your ground modem ? What are the parameters o= f > link ? > > Gautier > > 2009/8/19 Maik H=C3=B6pfel >> >> Well, I only get garbled characters when listening in to TWOG to PC, not >> when trying out communication between the modems. If I'm not mistaken, P= PRZ >> uses a binary protocol, so getting garbled chars doesn't say much, right= ? >> But thanks, I'll give it a try and will also try disabling my wifi. >> >> 19. Aug 2009 7:09 nachm. schrieb am "chris" : >> >> I forgot to mention that if you get garbled characters then try to chang= e >> the 2.4 Ghz channel. >> Default is the "C" channel. >> I had to do it also (i went to "D") as it was messing with my Wifi. >> Chris >> >> >> >> _______________________________________________ >> Paparazzi-devel mailing list >> Paparazzi-devel@nongnu.org >> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel >> >> _______________________________________________ >> Paparazzi-devel mailing list >> Paparazzi-devel@nongnu.org >> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel >> > > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > > From MAILER-DAEMON Thu Aug 20 15:23:36 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MeDEW-0007kv-3b for mharc-paparazzi-devel@gnu.org; Thu, 20 Aug 2009 15:23:36 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MeDEU-0007hL-Uk for paparazzi-devel@nongnu.org; Thu, 20 Aug 2009 15:23:34 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MeDET-0007Xo-4L for paparazzi-devel@nongnu.org; Thu, 20 Aug 2009 15:23:34 -0400 Received: from [199.232.76.173] (port=52328 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MeDES-0007XR-Vz for paparazzi-devel@nongnu.org; Thu, 20 Aug 2009 15:23:33 -0400 Received: from qw-out-1920.google.com ([74.125.92.148]:11086) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MeDES-0007Na-L7 for paparazzi-devel@nongnu.org; Thu, 20 Aug 2009 15:23:32 -0400 Received: by qw-out-1920.google.com with SMTP id 5so90114qwc.4 for ; Thu, 20 Aug 2009 12:23:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=EElhwqWVyRoNPpFxdY/p42tpYUXJe/xETSyUeX/htho=; b=GbdrJsBY5Dy9u4jXSfTUS0WfWtlZBFHoiBJRII7xCLUQPc1zchBeh1QN7qC2jHsTlB vCfbF/4lTVrWgOgYW5cY2Z09Xx7AYSpmqsrMK9a4L+6e+VhCeQ2NBXNlLwRIKAYPnmW7 s9oRppatiqCTTPdVdk/QhtZnOQknHA+Cs1cfE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; b=D6qFpijEUzSD1zIUGwAd/HwHK2kTFhaDAi2Whk8S6TyeZxv3i3uwPLUjTBB06bO8Zj oTvaCtvsFNMcODY2IEldD158pE8oYYx0BAcxNmVOpDuLFBV+zO36y22p7PXnpPtHFjUY y4tPW5JWnbiHgD7Px4pluN1tNSDrs0AS8K8J8= MIME-Version: 1.0 Sender: bubbajobob@gmail.com Received: by 10.224.103.70 with SMTP id j6mr174891qao.208.1250796211029; Thu, 20 Aug 2009 12:23:31 -0700 (PDT) Date: Thu, 20 Aug 2009 13:23:30 -0600 X-Google-Sender-Auth: 738e96ce74c94e84 Message-ID: From: Austin Jensen To: paparazzi-devel@nongnu.org Content-Type: multipart/alternative; boundary=000feaee585bd8851f047197afce X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) Subject: [Paparazzi-devel] Updated PolySurvey function X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Aug 2009 19:23:35 -0000 --000feaee585bd8851f047197afce Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Just to let everyone know, we have updated the OSAMNav.c file with a more robust version of the PolySurvey routine. If anyone had troubles with special cases of polygons, it might be fixed now. Thanks, Austin ------------------------------------------------------------------ Austin Jensen, Research Engineer Utah Water Research Laboratory (UWRL) Utah State University, 8200 Old Main Hill Logan, UT, 84322-8200, USA E: Austin.Jensen@aggiemail.usu.edu T: (435)797-3315 --000feaee585bd8851f047197afce Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Just to let everyone know, we have updated the OSAMNav.c file with a more robust version of the PolySurvey routine. If anyone had troubles with special cases of polygons, it might be fixed now.

Thanks,
Austin

------------------------------------------------------------------
Austin Jensen, Research Engineer
Utah Water Research Laboratory (UWRL)
Utah State University, 8200 Old Main Hill
Logan, UT, 84322-8200, USA
E: Austin.Jensen@aggiemail.usu.edu
T: (435)797-3315
--000feaee585bd8851f047197afce-- From MAILER-DAEMON Sat Aug 22 04:02:08 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MelY8-0000MF-Dz for mharc-paparazzi-devel@gnu.org; Sat, 22 Aug 2009 04:02:08 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MelY6-0000Kx-Sj for paparazzi-devel@nongnu.org; Sat, 22 Aug 2009 04:02:06 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MelY0-0000CK-12 for paparazzi-devel@nongnu.org; Sat, 22 Aug 2009 04:02:06 -0400 Received: from [199.232.76.173] (port=34873 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MelXz-0000CH-U0 for paparazzi-devel@nongnu.org; Sat, 22 Aug 2009 04:01:59 -0400 Received: from mx20.gnu.org ([199.232.41.8]:36881) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MelXz-0003c2-6V for paparazzi-devel@nongnu.org; Sat, 22 Aug 2009 04:01:59 -0400 Received: from smtp6-g21.free.fr ([212.27.42.6]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MelXx-0002DQ-He for paparazzi-devel@nongnu.org; Sat, 22 Aug 2009 04:01:58 -0400 Received: from smtp6-g21.free.fr (localhost [127.0.0.1]) by smtp6-g21.free.fr (Postfix) with ESMTP id 26485E08092 for ; Sat, 22 Aug 2009 10:01:52 +0200 (CEST) Received: from [192.168.0.10] (uni31-1-82-234-59-180.fbx.proxad.net [82.234.59.180]) by smtp6-g21.free.fr (Postfix) with ESMTP id 371D2E080AC for ; Sat, 22 Aug 2009 10:01:50 +0200 (CEST) Message-ID: <4A8FA5EA.8050009@free.fr> Date: Sat, 22 Aug 2009 10:01:46 +0200 From: Pascal Brisset User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 To: paparazzi-devel@nongnu.org Subject: Re: [Paparazzi-devel] Paparazzicenter on Netbook 100 References: <41cdc6cc0907240311w79a84296pda96ca170f5ec0c3@mail.gmail.com> In-Reply-To: <41cdc6cc0907240311w79a84296pda96ca170f5ec0c3@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Detected-Operating-System: by mx20.gnu.org: GNU/Linux 2.6 (newer, 3) X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6, seldom 2.4 (older, 4) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Aug 2009 08:02:07 -0000 Hi, Franck Marchand wrote: > The only problem now is that some windows (like waypoint edition or > message) appear fullscreen when i launch them. I try to change the > camel code in MapWaypoint.ml but noting works (resize (), unfullscreen > ()...). It seems that the GTK lib is not well suit for miniPC. Does > somebody have the same problem? (and manage to solve it?) Fixed. The ~type_hint:`DIALOG option prevents it to be opened maximized on the netbook distribution. It is now set for waypoint edition, messages, simulator and real time plotter. --Pascal From MAILER-DAEMON Tue Aug 25 07:06:18 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Mftqx-0002kh-R9 for mharc-paparazzi-devel@gnu.org; Tue, 25 Aug 2009 07:06:15 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mftqo-0002jI-JD for paparazzi-devel@nongnu.org; Tue, 25 Aug 2009 07:06:06 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mftqj-0002ft-BX for paparazzi-devel@nongnu.org; Tue, 25 Aug 2009 07:06:05 -0400 Received: from [199.232.76.173] (port=52858 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mftqi-0002fk-Jf for paparazzi-devel@nongnu.org; Tue, 25 Aug 2009 07:06:00 -0400 Received: from mail-fx0-f211.google.com ([209.85.220.211]:39889) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Mftqi-0002Qf-2j for paparazzi-devel@nongnu.org; Tue, 25 Aug 2009 07:06:00 -0400 Received: by fxm7 with SMTP id 7so2243711fxm.34 for ; Tue, 25 Aug 2009 04:05:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=HncqELhPa2JDea1QpwbfZLa8N6ZcyaC25FcSr5KaE8o=; b=C+waaU9/XNaHpnwqZNMkOWF9DqxVc47rh5AZCRRTtVGJrDl4AYI8GiQnfuMVwN0GTj tAyJR9TP/ePZYVk69eNf8bUe7CroNX39+zHgw21KvNakOhxNngjcMtaBw61esXqLW64p yihPMSyn/PxV/BwuqEUha7/3wqrt7exzxANBA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=i8ZGtRATVEZgIKAszDmWTBYKDMuiG6d+wNcu05etZ4ULnAu6NGlfto3r/Kl0TNIbsh xZ8TGJP3geYXDc1NjRhcsNTQwW6h3HV7ChOubNQtqOB5N+Y7YEkAUMGJu6lWizthm8M8 c0R0dQnRjEwRIIpK/FNv/XozgZ12T47fq0KSc= MIME-Version: 1.0 Received: by 10.204.152.27 with SMTP id e27mr2341171bkw.192.1251198358052; Tue, 25 Aug 2009 04:05:58 -0700 (PDT) Date: Tue, 25 Aug 2009 13:05:58 +0200 Message-ID: <41cdc6cc0908250405l36cb9ec8if8c98f11fb570c69@mail.gmail.com> From: Franck Marchand To: paparazzi-devel@nongnu.org Content-Type: multipart/alternative; boundary=0015175d03a6acdf000471f55165 X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) Subject: [Paparazzi-devel] MTI on Twog problem X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Aug 2009 11:06:08 -0000 --0015175d03a6acdf000471f55165 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hello, I am trying to plug a MTI IMU on a TWOG for a fixed wing aircraft. The MTI is plug on the Uart0 and I am trying to use the module "INS_XSENS" as explain on the wiki. After the configuration of my airframe, I've got the following message when I built: ... /home/franck/paparazzi3/sw/airborne/modules/ins/ins_xsens.c:140: warning: nested extern declaration of `INS_LINKTransmit' /home/franck/paparazzi3/sw/airborne/modules/ins/ins_xsens.c:133: warning: redundant redeclaration of 'INS_LINKTransmit' /home/franck/paparazzi3/sw/airborne/modules/ins/ins_xsens.c:133: warning: previous implicit declaration of 'INS_LINKTransmit' was here LD /home/franck/paparazzi3/var/PLUME/ap/ap.elf /home/franck/paparazzi3/var/PLUME/ap//home/franck/paparazzi3/sw/airborne/modules/ins/ins_xsens.o: In function `ins_init': ins_xsens.c:(.text+0x50): undefined reference to `INS_LINKTransmit' ins_xsens.c:(.text+0x5c): undefined reference to `INS_LINKTransmit' Does somebody face the same problem and can help me ? Thank you very much for your answers. Franck --0015175d03a6acdf000471f55165 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hello,

I am trying to plug a MTI IMU on a TWOG for a fixed wing airc= raft. The MTI is plug on the Uart0 and I am trying to use the module "= INS_XSENS" as explain on the wiki. After the configuration of my airfr= ame, I've got the following message when I built:

...
/home/franck/paparazzi3/sw/airborne/modules/ins/ins_xsens.c:140:= warning: nested extern declaration of `INS_LINKTransmit'
/home/fran= ck/paparazzi3/sw/airborne/modules/ins/ins_xsens.c:133: warning: redundant r= edeclaration of 'INS_LINKTransmit'
/home/franck/paparazzi3/sw/airborne/modules/ins/ins_xsens.c:133: warning: p= revious implicit declaration of 'INS_LINKTransmit' was here
LD /= home/franck/paparazzi3/var/PLUME/ap/ap.elf
/home/franck/paparazzi3/var/P= LUME/ap//home/franck/paparazzi3/sw/airborne/modules/ins/ins_xsens.o: In fun= ction `ins_init':
ins_xsens.c:(.text+0x50): undefined reference to `INS_LINKTransmit'
= ins_xsens.c:(.text+0x5c): undefined reference to `INS_LINKTransmit'
=
Does somebody face the same problem and can help me ?

Thank you = very much for your answers.

Franck
--0015175d03a6acdf000471f55165-- From MAILER-DAEMON Wed Aug 26 02:22:46 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MgBuA-0008DJ-9d for mharc-paparazzi-devel@gnu.org; Wed, 26 Aug 2009 02:22:46 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MgBu8-0008Bo-Nk for paparazzi-devel@nongnu.org; Wed, 26 Aug 2009 02:22:44 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MgBu1-00080F-6D for paparazzi-devel@nongnu.org; Wed, 26 Aug 2009 02:22:43 -0400 Received: from [199.232.76.173] (port=37001 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MgBu1-000800-3Y for paparazzi-devel@nongnu.org; Wed, 26 Aug 2009 02:22:37 -0400 Received: from mta-2.ms.rz.rwth-aachen.de ([134.130.7.73]:40817) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MgBu0-0006cm-KE for paparazzi-devel@nongnu.org; Wed, 26 Aug 2009 02:22:36 -0400 MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=ISO-8859-1 Received: from ironport-out-1.rz.rwth-aachen.de ([134.130.5.40]) by mta-2.ms.rz.RWTH-Aachen.de (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008)) with ESMTP id <0KOZ007A60DLL4C0@mta-2.ms.rz.RWTH-Aachen.de> for paparazzi-devel@nongnu.org; Wed, 26 Aug 2009 08:22:33 +0200 (CEST) X-IronPort-AV: E=Sophos;i="4.44,277,1249250400"; d="scan'208";a="23685995" Received: from relay-1.ms.rz.rwth-aachen.de (HELO relay.rwth-aachen.de) ([134.130.7.74]) by ironport-in-1.rz.rwth-aachen.de with ESMTP; Wed, 26 Aug 2009 08:22:34 +0200 Received: from [134.130.150.40] (pc40.dynamik.RWTH-Aachen.DE [134.130.150.40]) by relay.rwth-aachen.de (8.13.8+Sun/8.13.8/1) with ESMTP id n7Q6MXbB028949 for ; Wed, 26 Aug 2009 08:22:33 +0200 (CEST) Message-id: <4A94D468.2070701@web.de> Date: Wed, 26 Aug 2009 08:21:28 +0200 From: Andreas Gaeb User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) To: paparazzi-devel@nongnu.org Subject: Re: [Paparazzi-devel] MTI on Twog problem References: <41cdc6cc0908250405l36cb9ec8if8c98f11fb570c69@mail.gmail.com> In-reply-to: <41cdc6cc0908250405l36cb9ec8if8c98f11fb570c69@mail.gmail.com> X-detected-operating-system: by monty-python.gnu.org: Solaris 10 (beta) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Aug 2009 06:22:45 -0000 Hi Franck, Franck Marchand schrieb: > Hello, > > I am trying to plug a MTI IMU on a TWOG for a fixed wing aircraft. The MTI > is plug on the Uart0 and I am trying to use the module "INS_XSENS" as > explain on the wiki. The module ins_xsens.xml seems to be incomplete, I use ins_xsens_MTiG_Uart0.xml instead which works fine. I hope you are using a level converter (MAX232 or the like), I fried my Uarts by not using one. > After the configuration of my airframe, I've got the > following message when I built: > > ... > /home/franck/paparazzi3/sw/airborne/modules/ins/ins_xsens.c:140: warning: > nested extern declaration of `INS_LINKTransmit' > [...] > ins_xsens.c:(.text+0x50): undefined reference to `INS_LINKTransmit' > ins_xsens.c:(.text+0x5c): undefined reference to `INS_LINKTransmit' This seems to be caused by INS_LINK not being defined. In the module xml file should be a line like which is in ins_xsens_MTiG_Uart0.xml but not in ins_xsens.xml. Btw, if you have an MTi-G and want to use its GPS, you'll have to add something like , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Aug 2009 06:43:55 -0000 --0-1950503918-1251269020=:42596 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi all=0Ai am just looking for some feedback on anyone that has got any pro= cedures to work properly. I have been working on some routines for payload = dropping and i wanted to put them in a procedure so that i could use the sa= me code over many flight plans. I am not sure how limited procedures are bu= t this is what i have written=0A=0AThanks for any help=0ATodd=0A=0A=0A
=0A #include "datalink.h"=0A #include "bomb.h"=0A =0A =0A =0A =0A =0A =0A =0A =0A =0A =0A =0A =0A =0A =0A =0A =0A =0A =0A =0A =0A =0A =0A =0A =0A =0A =0A = =0A =0A =0A =0A =0A =0A =0A =0A =0A =0A = =0A =0A=0A=0A=0A=0A _________________= _________________________________________________________________=0AFind lo= cal businesses and services in your area with Yahoo!7 Local.=0AGet started:= http://local.yahoo.com.au --0-1950503918-1251269020=:42596 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Hi all
i am just looking for some feedback on anyone that has go= t any procedures to work properly. I have been working on some routines for= payload dropping and i wanted to put them in a procedure so that i could u= se the same code over many flight plans. I am not sure how limited procedur= es are but this is what i have written

Thanks for any help
Todd
<procedure>
  <header>
    #inc= lude "datalink.h"
    #include "bomb.h"
  </he= ader>
  <param name=3D"alt" default_value=3D"ground_alt+50"/&= gt;
  <param name=3D"radius" default_value=3D"75"/>
 = <waypoints>
    <waypoint alt=3D"alt" name=3D"T= ARGET" x=3D"0" y=3D"0"/>
    <waypoint alt=3D"alt" = name=3D"START" x=3D"0" y=3D"-100"/>
    <waypoint name=3D"RELEASE= " x=3D"0" y=3D"-50"/>
    <waypoint name=3D"BLEG" x= =3D"100" y=3D"-100"/>
    <waypoint alt=3D"alt+50" = name=3D"BCLIMB" x=3D"0" y=3D"100"/>
    <waypoint = alt=3D"alt+50" name=3D"BFEIGHT" x=3D"100" y=3D"0"/>
  </waypo= ints>
  <blocks>
    <block name=3D"b= ombloiter" strip_button=3D"B Loiter">
      = <call fun=3D"NavSetWaypointHere(WP_TARGET)"/>
   &n= bsp;  <eight center=3D"WP_TARGET" radius=3D"radius" turn_around=3D"= WP_BEIGHT"/>
    </block>
    = <block name=3D"bombhere" strip_button=3D"B Here">
  &nbs= p;   <call fun=3D"NavSetWaypointHere(WP_TARGET)"/>
 = ;   </block>
    <block name=3D"bomb" strip_button=3D"Bomb">
      <!--<set= value=3D"WaypointX(WP_TARGET)" var=3D"WaypointX(WP_START)"/>
 &= nbsp;    <set value=3D"WaypointY(WP_TARGET) - 100" var=3D= "WaypointY(WP_START)"/>
      <set value= =3D"WaypointX(WP_TARGET)" var=3D"WaypointX(WP_CLIMB)"/>
  &= nbsp;   <set value=3D"WaypointY(WP_TARGET) + 100" var=3D"Waypo= intY(WP_CLIMB)"/>
      <set value=3D"Bom= bComputeApproach(WP_TARGET, WP_START, nav_radius)" var=3D"unit"/>--><= br>      <circle radius=3D"nav_radius" until=3D= "NavQdrCloseTo(DegOfRad(bomb_start_qdr)-10)" wp=3D"BLEG"/>
 &nbs= p;  </block>
    <block name=3D"align"><= br>      <exception cond=3D"BombUpdateRelease(W= P_TARGET)" deroute=3D"end"/>
      <go approaching_time=3D"bomb_trigger_delay" from=3D"START" hmode=3D"route" wp= =3D"RELEASE"/>
    </block>
   = ; <block name=3D"shoot">
      <set va= lue=3D"BombShoot()" var=3D"unit"/>
      <= ;go from=3D"RELEASE" hmode=3D"route" wp=3D"BCLIMB"/>
  &nbs= p;   <set value=3D"BombCloseHatch()" var=3D"unit"/>
&nbs= p;     <deroute block=3D"end"/>
  &n= bsp; </block>
    <block name=3D"close">
&= nbsp;     <set value=3D"BombCloseHatch()" var=3D"uni= t"/>
      <deroute block=3D"end"/>    </block>
  </blocks>
</proced= ure>

=0A=0A=0A=0A
=0AFind local bus= inesses and services in your area with Yahoo!7 Local. Get started. --0-1950503918-1251269020=:42596-- From MAILER-DAEMON Wed Aug 26 04:32:50 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MgDw2-0004mc-M7 for mharc-paparazzi-devel@gnu.org; Wed, 26 Aug 2009 04:32:50 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MgDw0-0004jd-Ix for paparazzi-devel@nongnu.org; Wed, 26 Aug 2009 04:32:48 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MgDvv-0004aJ-Jd for paparazzi-devel@nongnu.org; Wed, 26 Aug 2009 04:32:47 -0400 Received: from [199.232.76.173] (port=37839 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MgDvv-0004Zr-7r for paparazzi-devel@nongnu.org; Wed, 26 Aug 2009 04:32:43 -0400 Received: from web51501.mail.re2.yahoo.com ([206.190.38.193]:26642) by monty-python.gnu.org with smtp (Exim 4.60) (envelope-from ) id 1MgDvu-00072q-Gk for paparazzi-devel@nongnu.org; Wed, 26 Aug 2009 04:32:42 -0400 Received: (qmail 5418 invoked by uid 60001); 26 Aug 2009 08:32:39 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com.au; s=s1024; t=1251275559; bh=wuBfIm5JP7Nu/j22kvUltE1IiRSpF0O7HMUIIhObi0w=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=JmVcCdG9yKQGZHLd4MjI71BMoHep2IlxAuCNjVwA8I99Kjcri7vpeVzqGkNjMUVie0DuVfRcnf3tfKq1I++FE6OwgopDLDYZTHUa7hEfC2g0DC66EyAD71EsxzjtXeFT6kHqUrYwpYoolGEI1NNBaDtwt69FLe+tzkRbzDUei5Q= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com.au; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=drFx/5WGkw9ior7AbUloyOHyGUC7IH1YKodBpoDEf22Ii5HvNhbAAezd+7O7sRvrl/VDt6vzTxsK/aq/H6btbm6dZkGwnFcAaykn/7UaWBId5i/lIGRbDMpbnlBpI6Xr1IBgOI98fmHE5ij3I9VxUx4JSEID5BevUmk+LFPgRiI=; Message-ID: <468134.5413.qm@web51501.mail.re2.yahoo.com> X-YMail-OSG: TggYZ44VM1lDqxkODjF2FhgPxmRp7h9xsPmdXfj_rAKMbVQD_Kml_7wiNfMzVv4HlPdKom7J1UcgP2nkNr_bu9HVR.cOHAlReSwFe6EEibauYGdvRIvEkDYYrnnANXeJkbMRA5HjQ4T9f5O1YxHR.fJoe94Up7xfKE5CbBo1ivIVby1OJrp0.ZMhHF6fOXeXoRNlg7j3KRuwZosyX8rGVvOZ3mapENj5zLHo9Ak5apV3vei423YDxMLaRGk4MXHr5fpYR3YeOJZHbHA9s2AiAdrHjWFQaUifO30Meswf.R9OsfBU6LcbWO_Uztwo5a1FujQWNslpoNNg4TtsPBgnNzdWvJ5q8acan34- Received: from [121.45.133.91] by web51501.mail.re2.yahoo.com via HTTP; Wed, 26 Aug 2009 01:32:38 PDT X-Mailer: YahooMailRC/1358.27 YahooMailWebService/0.7.338.2 References: <538503.42596.qm@web51512.mail.re2.yahoo.com> Date: Wed, 26 Aug 2009 01:32:38 -0700 (PDT) From: Todd Sandercock Subject: Re: [Paparazzi-devel] Procedures To: paparazzi-devel@nongnu.org, Paparazzi Development In-Reply-To: <538503.42596.qm@web51512.mail.re2.yahoo.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-1341723278-1251275558=:5413" X-detected-operating-system: by monty-python.gnu.org: FreeBSD 6.x (1) Cc: X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Aug 2009 08:32:48 -0000 --0-1341723278-1251275558=:5413 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Oh and the stuff that i have written won't compile for some reason.=0A=0ATo= dd=0A=0A=0A=0A________________________________=0AFrom: Todd Sandercock =0ATo: Paparazzi Development =0ASent: Wednesday, 26 August, 2009 4:13:40 PM=0ASubject: [Paparazzi-d= evel] Procedures=0A=0A=0AHi all=0Ai am just looking for some feedback on an= yone that has got any procedures to work properly. I have been working on s= ome routines for payload dropping and i wanted to put them in a procedure s= o that i could use the same code over many flight plans. I am not sure how = limited procedures are but this is what i have written=0A=0AThanks for any = help=0ATodd=0A=0A=0A
=0A #include "datalink.h"=0A = #include "bomb.h"=0A
=0A =0A =0A =0A =0A = =0A =0A =0A =0A = =0A =0A =0A =0A =0A = =0A =0A =0A= =0A =0A =0A =0A= =0A =0A =0A = =0A = =0A =0A =0A <= set value=3D"BombShoot()" var=3D"unit"/>=0A =0A =0A =0A =0A =0A =0A =0A =0A =0A
=0A=0A____= ____________________________=0A Find local businesses and services in your = area with Yahoo!7 Local. Get started.=0A=0A=0A _______________________= ___________________________________________________________=0AFind local bu= sinesses and services in your area with Yahoo!7 Local.=0AGet started: http:= //local.yahoo.com.au --0-1341723278-1251275558=:5413 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Oh and the stuff that i have written won't compile for some reaso= n.

Todd


From: To= dd Sandercock <todd_soaring@yahoo.com.au>
To: Paparazzi Development <Paparazzi-devel@nong= nu.org>
Sent: Wednes= day, 26 August, 2009 4:13:40 PM
Su= bject: [Paparazzi-devel] Procedures

Hi all
i = am just looking for some feedback on anyone that has got any procedures to work properly. = I have been working on some routines for payload dropping and i wanted to p= ut them in a procedure so that i could use the same code over many flight p= lans. I am not sure how limited procedures are but this is what i have writ= ten

Thanks for any help
Todd

<procedure>
  &= lt;header>
    #include "datalink.h"
  &n= bsp; #include "bomb.h"
  </header>
  <param name= =3D"alt" default_value=3D"ground_alt+50"/>
  <param name=3D"r= adius" default_value=3D"75"/>
  <waypoints>
  = ;  <waypoint alt=3D"alt" name=3D"TARGET" x=3D"0" y=3D"0"/>
&n= bsp;   <waypoint alt=3D"alt" name=3D"START"=0A x=3D"0" y=3D"-1= 00"/>
    <waypoint name=3D"RELEASE" x=3D"0" y=3D"-= 50"/>
    <waypoint name=3D"BLEG" x=3D"100" y=3D"-1= 00"/>
    <waypoint alt=3D"alt+50" name=3D"BCLIMB" = x=3D"0" y=3D"100"/>
    <waypoint alt=3D"alt+50" n= ame=3D"BFEIGHT" x=3D"100" y=3D"0"/>
  </waypoints>
&nbs= p; <blocks>
    <block name=3D"bombloiter" strip= _button=3D"B Loiter">
      <call fun=3D"= NavSetWaypointHere(WP_TARGET)"/>
      <e= ight center=3D"WP_TARGET" radius=3D"radius" turn_around=3D"WP_BEIGHT"/><= br>    </block>
    <block name= =3D"bombhere" strip_button=3D"B Here">
     = <call fun=3D"NavSetWaypointHere(WP_TARGET)"/>
    = </block>
    <block name=3D"bomb"=0A strip_butto= n=3D"Bomb">
      <!--<set value=3D"Wa= ypointX(WP_TARGET)" var=3D"WaypointX(WP_START)"/>
   &= nbsp;  <set value=3D"WaypointY(WP_TARGET) - 100" var=3D"WaypointY(W= P_START)"/>
      <set value=3D"WaypointX= (WP_TARGET)" var=3D"WaypointX(WP_CLIMB)"/>
    &n= bsp; <set value=3D"WaypointY(WP_TARGET) + 100" var=3D"WaypointY(WP_CLIMB= )"/>
      <set value=3D"BombComputeAppro= ach(WP_TARGET, WP_START, nav_radius)" var=3D"unit"/>-->
 &nbs= p;    <circle radius=3D"nav_radius" until=3D"NavQdrCloseT= o(DegOfRad(bomb_start_qdr)-10)" wp=3D"BLEG"/>
    <= /block>
    <block name=3D"align">
 &nbs= p;    <exception cond=3D"BombUpdateRelease(WP_TARGET)" de= route=3D"end"/>
      <go=0A approaching_= time=3D"bomb_trigger_delay" from=3D"START" hmode=3D"route" wp=3D"RELEASE"/&= gt;
    </block>
    <block na= me=3D"shoot">
      <set value=3D"BombSho= ot()" var=3D"unit"/>
      <go from=3D"RE= LEASE" hmode=3D"route" wp=3D"BCLIMB"/>
     = <set value=3D"BombCloseHatch()" var=3D"unit"/>
   =    <deroute block=3D"end"/>
    </bloc= k>
    <block name=3D"close">
  &nb= sp;   <set value=3D"BombCloseHatch()" var=3D"unit"/>
&nb= sp;     <deroute block=3D"end"/>
  &= nbsp; </block>
  </blocks>
</procedure>

=0A=0A=0A=0A
=0AFind local businesses and = services in your area with Yahoo!7 Local. Get started.
<= /div>

=0A=0A=0A=0A
=0AFind local businesses and = services in your area with Yahoo!7 Local. Get= started. --0-1341723278-1251275558=:5413-- From MAILER-DAEMON Wed Aug 26 04:32:50 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MgDw2-0004mN-7p for mharc-paparazzi-devel@gnu.org; Wed, 26 Aug 2009 04:32:50 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MgDw0-0004ja-9K for paparazzi-devel@nongnu.org; Wed, 26 Aug 2009 04:32:48 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MgDvv-0004aW-K8 for Paparazzi-devel@nongnu.org; Wed, 26 Aug 2009 04:32:47 -0400 Received: from [199.232.76.173] (port=37840 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MgDvv-0004Zy-7s for Paparazzi-devel@nongnu.org; Wed, 26 Aug 2009 04:32:43 -0400 Received: from web51501.mail.re2.yahoo.com ([206.190.38.193]:26641) by monty-python.gnu.org with smtp (Exim 4.60) (envelope-from ) id 1MgDvu-00072o-Gv for Paparazzi-devel@nongnu.org; Wed, 26 Aug 2009 04:32:42 -0400 Received: (qmail 5418 invoked by uid 60001); 26 Aug 2009 08:32:39 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com.au; s=s1024; t=1251275559; bh=wuBfIm5JP7Nu/j22kvUltE1IiRSpF0O7HMUIIhObi0w=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=JmVcCdG9yKQGZHLd4MjI71BMoHep2IlxAuCNjVwA8I99Kjcri7vpeVzqGkNjMUVie0DuVfRcnf3tfKq1I++FE6OwgopDLDYZTHUa7hEfC2g0DC66EyAD71EsxzjtXeFT6kHqUrYwpYoolGEI1NNBaDtwt69FLe+tzkRbzDUei5Q= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com.au; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=drFx/5WGkw9ior7AbUloyOHyGUC7IH1YKodBpoDEf22Ii5HvNhbAAezd+7O7sRvrl/VDt6vzTxsK/aq/H6btbm6dZkGwnFcAaykn/7UaWBId5i/lIGRbDMpbnlBpI6Xr1IBgOI98fmHE5ij3I9VxUx4JSEID5BevUmk+LFPgRiI=; Message-ID: <468134.5413.qm@web51501.mail.re2.yahoo.com> X-YMail-OSG: TggYZ44VM1lDqxkODjF2FhgPxmRp7h9xsPmdXfj_rAKMbVQD_Kml_7wiNfMzVv4HlPdKom7J1UcgP2nkNr_bu9HVR.cOHAlReSwFe6EEibauYGdvRIvEkDYYrnnANXeJkbMRA5HjQ4T9f5O1YxHR.fJoe94Up7xfKE5CbBo1ivIVby1OJrp0.ZMhHF6fOXeXoRNlg7j3KRuwZosyX8rGVvOZ3mapENj5zLHo9Ak5apV3vei423YDxMLaRGk4MXHr5fpYR3YeOJZHbHA9s2AiAdrHjWFQaUifO30Meswf.R9OsfBU6LcbWO_Uztwo5a1FujQWNslpoNNg4TtsPBgnNzdWvJ5q8acan34- Received: from [121.45.133.91] by web51501.mail.re2.yahoo.com via HTTP; Wed, 26 Aug 2009 01:32:38 PDT X-Mailer: YahooMailRC/1358.27 YahooMailWebService/0.7.338.2 References: <538503.42596.qm@web51512.mail.re2.yahoo.com> Date: Wed, 26 Aug 2009 01:32:38 -0700 (PDT) From: Todd Sandercock Subject: Re: [Paparazzi-devel] Procedures To: paparazzi-devel@nongnu.org, Paparazzi Development In-Reply-To: <538503.42596.qm@web51512.mail.re2.yahoo.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-1341723278-1251275558=:5413" X-detected-operating-system: by monty-python.gnu.org: FreeBSD 6.x (1) Cc: X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Aug 2009 08:32:48 -0000 --0-1341723278-1251275558=:5413 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Oh and the stuff that i have written won't compile for some reason.=0A=0ATo= dd=0A=0A=0A=0A________________________________=0AFrom: Todd Sandercock =0ATo: Paparazzi Development =0ASent: Wednesday, 26 August, 2009 4:13:40 PM=0ASubject: [Paparazzi-d= evel] Procedures=0A=0A=0AHi all=0Ai am just looking for some feedback on an= yone that has got any procedures to work properly. I have been working on s= ome routines for payload dropping and i wanted to put them in a procedure s= o that i could use the same code over many flight plans. I am not sure how = limited procedures are but this is what i have written=0A=0AThanks for any = help=0ATodd=0A=0A=0A
=0A #include "datalink.h"=0A = #include "bomb.h"=0A
=0A =0A =0A =0A =0A = =0A =0A =0A =0A = =0A =0A =0A =0A =0A = =0A =0A =0A= =0A =0A =0A =0A= =0A =0A =0A = =0A = =0A =0A =0A <= set value=3D"BombShoot()" var=3D"unit"/>=0A =0A =0A =0A =0A =0A =0A =0A =0A =0A
=0A=0A____= ____________________________=0A Find local businesses and services in your = area with Yahoo!7 Local. Get started.=0A=0A=0A _______________________= ___________________________________________________________=0AFind local bu= sinesses and services in your area with Yahoo!7 Local.=0AGet started: http:= //local.yahoo.com.au --0-1341723278-1251275558=:5413 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Oh and the stuff that i have written won't compile for some reaso= n.

Todd


From: To= dd Sandercock <todd_soaring@yahoo.com.au>
To: Paparazzi Development <Paparazzi-devel@nong= nu.org>
Sent: Wednes= day, 26 August, 2009 4:13:40 PM
Su= bject: [Paparazzi-devel] Procedures

Hi all
i = am just looking for some feedback on anyone that has got any procedures to work properly. = I have been working on some routines for payload dropping and i wanted to p= ut them in a procedure so that i could use the same code over many flight p= lans. I am not sure how limited procedures are but this is what i have writ= ten

Thanks for any help
Todd

<procedure>
  &= lt;header>
    #include "datalink.h"
  &n= bsp; #include "bomb.h"
  </header>
  <param name= =3D"alt" default_value=3D"ground_alt+50"/>
  <param name=3D"r= adius" default_value=3D"75"/>
  <waypoints>
  = ;  <waypoint alt=3D"alt" name=3D"TARGET" x=3D"0" y=3D"0"/>
&n= bsp;   <waypoint alt=3D"alt" name=3D"START"=0A x=3D"0" y=3D"-1= 00"/>
    <waypoint name=3D"RELEASE" x=3D"0" y=3D"-= 50"/>
    <waypoint name=3D"BLEG" x=3D"100" y=3D"-1= 00"/>
    <waypoint alt=3D"alt+50" name=3D"BCLIMB" = x=3D"0" y=3D"100"/>
    <waypoint alt=3D"alt+50" n= ame=3D"BFEIGHT" x=3D"100" y=3D"0"/>
  </waypoints>
&nbs= p; <blocks>
    <block name=3D"bombloiter" strip= _button=3D"B Loiter">
      <call fun=3D"= NavSetWaypointHere(WP_TARGET)"/>
      <e= ight center=3D"WP_TARGET" radius=3D"radius" turn_around=3D"WP_BEIGHT"/><= br>    </block>
    <block name= =3D"bombhere" strip_button=3D"B Here">
     = <call fun=3D"NavSetWaypointHere(WP_TARGET)"/>
    = </block>
    <block name=3D"bomb"=0A strip_butto= n=3D"Bomb">
      <!--<set value=3D"Wa= ypointX(WP_TARGET)" var=3D"WaypointX(WP_START)"/>
   &= nbsp;  <set value=3D"WaypointY(WP_TARGET) - 100" var=3D"WaypointY(W= P_START)"/>
      <set value=3D"WaypointX= (WP_TARGET)" var=3D"WaypointX(WP_CLIMB)"/>
    &n= bsp; <set value=3D"WaypointY(WP_TARGET) + 100" var=3D"WaypointY(WP_CLIMB= )"/>
      <set value=3D"BombComputeAppro= ach(WP_TARGET, WP_START, nav_radius)" var=3D"unit"/>-->
 &nbs= p;    <circle radius=3D"nav_radius" until=3D"NavQdrCloseT= o(DegOfRad(bomb_start_qdr)-10)" wp=3D"BLEG"/>
    <= /block>
    <block name=3D"align">
 &nbs= p;    <exception cond=3D"BombUpdateRelease(WP_TARGET)" de= route=3D"end"/>
      <go=0A approaching_= time=3D"bomb_trigger_delay" from=3D"START" hmode=3D"route" wp=3D"RELEASE"/&= gt;
    </block>
    <block na= me=3D"shoot">
      <set value=3D"BombSho= ot()" var=3D"unit"/>
      <go from=3D"RE= LEASE" hmode=3D"route" wp=3D"BCLIMB"/>
     = <set value=3D"BombCloseHatch()" var=3D"unit"/>
   =    <deroute block=3D"end"/>
    </bloc= k>
    <block name=3D"close">
  &nb= sp;   <set value=3D"BombCloseHatch()" var=3D"unit"/>
&nb= sp;     <deroute block=3D"end"/>
  &= nbsp; </block>
  </blocks>
</procedure>

=0A=0A=0A=0A
=0AFind local businesses and = services in your area with Yahoo!7 Local. Get started.
<= /div>

=0A=0A=0A=0A
=0AFind local businesses and = services in your area with Yahoo!7 Local. Get= started. --0-1341723278-1251275558=:5413-- From MAILER-DAEMON Wed Aug 26 06:59:10 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MgGDd-00078W-Q2 for mharc-paparazzi-devel@gnu.org; Wed, 26 Aug 2009 06:59:09 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MgGDb-00074s-Jn for paparazzi-devel@nongnu.org; Wed, 26 Aug 2009 06:59:07 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MgGDV-0006uM-Ni for paparazzi-devel@nongnu.org; Wed, 26 Aug 2009 06:59:06 -0400 Received: from [199.232.76.173] (port=39669 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MgGDV-0006tr-EY for paparazzi-devel@nongnu.org; Wed, 26 Aug 2009 06:59:01 -0400 Received: from mx20.gnu.org ([199.232.41.8]:19173) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MgGDU-00047o-UW for paparazzi-devel@nongnu.org; Wed, 26 Aug 2009 06:59:01 -0400 Received: from mail-yw0-f192.google.com ([209.85.211.192]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MgGDT-0001C0-Cy for paparazzi-devel@nongnu.org; Wed, 26 Aug 2009 06:58:59 -0400 Received: by ywh30 with SMTP id 30so33786ywh.25 for ; Wed, 26 Aug 2009 03:58:57 -0700 (PDT) MIME-Version: 1.0 Sender: maik@zackbumm.biz Received: by 10.91.54.22 with SMTP id g22mr5959000agk.80.1251284337194; Wed, 26 Aug 2009 03:58:57 -0700 (PDT) From: =?UTF-8?B?TWFpayBIw7ZwZmVs?= Date: Wed, 26 Aug 2009 12:58:37 +0200 X-Google-Sender-Auth: 8c031ed170f0f6d4 Message-ID: To: paparazzi-devel@nongnu.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Detected-Operating-System: by mx20.gnu.org: GNU/Linux 2.6 (newer, 2) X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6, seldom 2.4 (older, 4) Subject: [Paparazzi-devel] Bug reports & minor annoyances for a newbie X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Aug 2009 10:59:08 -0000 Hello everyone, I finally reached the point where my plane's communicating over wireless, and everything seems to work. Now it's time for sensors and gains tuning! :) You have been wonderful and very helpful, but I thought I'd just share little issues I had as a newbie getting into the project. I know quite a few of those can be fixed by myself, and will eventually (I promise), but I just want to get this sent out before I proceed further. And of course it's always possible that I just missed something. In no particular order: - Creating a new A/C allows for a name with whitespace characters, but building it fails. Should be enforced by the GCS. - I have not found an explanation in the wiki about what AUTO1/AUTO2 actually do. I know by now, but it still should be in the wiki. - Python-lxml and python-wxgtk2.8 are not among the dependencies if you build from SVN, but they are required by the Python messages tool. - There's no public IRC logs, even though it's a very important form of communication for the project. I could set them up, if that's wanted. I think it would be very helpful. - Quite a few Important links are not in the wiki, and RCgroups seems to be the main forum, but is not linked either. I'm thinking of Mecevans build thread, Henrix/chris Easyglider airframe file, the Paparazzi thread, the documentation for the Encoder board... - The default for the GCS is the MJ5 aircraft, which I think is for a Tiny1.3. Should probably be changed, as most newbies are going to go with a Tiny2.11 or TWOG. So please, don't take this the wrong way, it's just meant as possible points for improvement from a beginners point of view. I think I will contribute a "Getting started with Paparazzi" page to the wiki eventually, and try to add some of my points from above as well. I'm thrilled to go on with my project and really love this community! Greetings from Berlin, enjoy your week, Maik From MAILER-DAEMON Wed Aug 26 12:03:44 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MgKyN-0000pm-Q5 for mharc-paparazzi-devel@gnu.org; Wed, 26 Aug 2009 12:03:43 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MgKyK-0000kJ-5z for paparazzi-devel@nongnu.org; Wed, 26 Aug 2009 12:03:40 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MgKyE-0000dk-2r for paparazzi-devel@nongnu.org; Wed, 26 Aug 2009 12:03:39 -0400 Received: from [199.232.76.173] (port=54196 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MgKyD-0000dW-LJ for paparazzi-devel@nongnu.org; Wed, 26 Aug 2009 12:03:33 -0400 Received: from imss-1.enac.fr ([195.220.159.36]:46669) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MgKyD-0001rl-34 for paparazzi-devel@nongnu.org; Wed, 26 Aug 2009 12:03:33 -0400 Received: from mauve.recherche.enac.fr (imss-1.imss.interne.enac [127.0.0.1]) by imss-1.enac.fr (Postfix) with ESMTP id 78E9118B3A3 for ; Wed, 26 Aug 2009 18:03:08 +0200 (CEST) Received: from [10.31.1.82] (sepia.recherche.enac.fr [10.31.1.82])by mauve.recherche.enac.fr (Postfix) with ESMTP id 5FD692FA822for ; Wed, 26 Aug 2009 18:03:08 +0200 (CEST) Message-ID: <4A955CBC.90509@free.fr> Date: Wed, 26 Aug 2009 18:03:08 +0200 From: Pascal Brisset User-Agent: Mozilla-Thunderbird 2.0.0.22 (X11/20090706) MIME-Version: 1.0 To: paparazzi-devel@nongnu.org Subject: Re: [Paparazzi-devel] Bug reports & minor annoyances for a newbie References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed X-imss-version: 2.5 X-imss-result: Passed X-imss-scores: Clean:99.90000 C:13 M:2 S:5 R:5 X-imss-settings: Baseline:1 C:1 M:1 S:1 R:1 (0.0000 0.0000) Content-Transfer-Encoding: quoted-printable X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.4-2.6 X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Aug 2009 16:03:41 -0000 Hi, thanks for these constructive remarks. Maik H=C3=B6pfel wrote: > - Creating a new A/C allows for a name with whitespace characters, but > building it fails. Should be enforced by the GCS. > =20 I've added a check on A/C name and id > - I have not found an explanation in the wiki about what AUTO1/AUTO2 > actually do. I know by now, but it still should be in the wiki. > =20 Pleeeeaase, add it > - Python-lxml and python-wxgtk2.8 are not among the dependencies if > you build from SVN, but they are required by the Python messages tool. > =20 added (python-wxgtk2.8 not available in Debian etch, python-wxgtk2.6=20 would work ?) > - There's no public IRC logs, even though it's a very important form > of communication for the project. I could set them up, if that's > wanted. I think it would be very helpful. > =20 Please, and add a reference in the wiki > - Quite a few Important links are not in the wiki, and RCgroups seems > to be the main forum, but is not linked either. I'm thinking of > Mecevans build thread, Henrix/chris Easyglider airframe file, the > Paparazzi thread, the documentation for the Encoder board... > =20 Since you've search for them, you probably know the best place to add=20 them :-) > - The default for the GCS is the MJ5 aircraft, which I think is for a > Tiny1.3. Should probably be changed, as most newbies are going to go > with a Tiny2.11 or TWOG. > =20 Changed for the Tiny2.11 > So please, don't take this the wrong way,=20 You are welcome --Pascal =20 From MAILER-DAEMON Wed Aug 26 12:59:28 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MgLqK-0006BS-E2 for mharc-paparazzi-devel@gnu.org; Wed, 26 Aug 2009 12:59:28 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MgLqI-0006AJ-7A for paparazzi-devel@nongnu.org; Wed, 26 Aug 2009 12:59:26 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MgLqD-00067q-Kn for paparazzi-devel@nongnu.org; Wed, 26 Aug 2009 12:59:25 -0400 Received: from [199.232.76.173] (port=47064 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MgLqD-00067d-Fa for paparazzi-devel@nongnu.org; Wed, 26 Aug 2009 12:59:21 -0400 Received: from mx20.gnu.org ([199.232.41.8]:36319) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MgLqC-0007OV-Ai for paparazzi-devel@nongnu.org; Wed, 26 Aug 2009 12:59:21 -0400 Received: from mail-bw0-f227.google.com ([209.85.218.227]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MgLq7-0002iF-62 for paparazzi-devel@nongnu.org; Wed, 26 Aug 2009 12:59:15 -0400 Received: by bwz27 with SMTP id 27so296750bwz.34 for ; Wed, 26 Aug 2009 09:59:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=87K6Fz570mxTSNEOEkj/RkBBjbhNuPNKcLJMrwkU8/M=; b=JpuI0cNqSddN88eL0a3h5aZsXiiuIhZqIxpaaZ/g1RxtX3yiD8Pxy1yMuN1COAGTZt giDfFW1aw/VPUbJbdLyE3KrxmEgg9IX5R/SdxAcgJPEkYdvTgSldbhAorly2dHJr7l8u 6PGFGmWbdR2qs2BiZ5m79dGPbmYhcnj+Uxk38= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=IHUBQGXe8nh53GxHfA74TrKjF8uFKLLWEMw4hl7K2JBBfH8ShjR7RY5bJJCQmtokpJ 8rPgoIUgkdX957RT9iyjZ8qhjTEwVr1Fc1inX5XJpS736luFYSPPT99tE0NlGsNX9qaD Sy7vCu6MqGCsXzo8gA+2iPBFT2dUeKXSMKCi0= MIME-Version: 1.0 Received: by 10.204.7.204 with SMTP id e12mr3815194bke.117.1251305951504; Wed, 26 Aug 2009 09:59:11 -0700 (PDT) Date: Wed, 26 Aug 2009 18:59:11 +0200 Message-ID: <41cdc6cc0908260959y7d28881eh318ffd59f613dee4@mail.gmail.com> From: Franck Marchand To: paparazzi-devel@nongnu.org Content-Type: multipart/alternative; boundary=0015174be03ebea9e504720e5e43 X-Detected-Operating-System: by mx20.gnu.org: GNU/Linux 2.6 (newer, 2) X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6, seldom 2.4 (older, 4) Subject: [Paparazzi-devel] Re: MTI on Twog problem X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Aug 2009 16:59:26 -0000 --0015174be03ebea9e504720e5e43 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi Andreas Indeed I am using a level converter on the MTI (not MTI-G, so no GPS for the moment). I was already using the ins_xsens_MTi_Uart0.xml and the line was there during my problem. However I add the following lines in the ins_xsens.c and it make the building work well : #ifndef INS_LINK #define INS_LINK Uart0 #endif After many tests, I still can't make the MTI working. It seems that I never enter into the function "parse_ins_msg" & "parse_ins_buffer" of ins_xsens.c Do I have to call them in the ins_xsens.xml? or in the ins_periodic_task (wich do a "XSENS_ReqGPSStatus" not usefull in a MTI, I think...)? or in the main_ap.c? Thank you for your help Regards, Franck --0015174be03ebea9e504720e5e43 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Andreas

Indeed I am using a level converter on the MTI (not MTI-G= , so no GPS for the moment). I was already using the ins_xsens_MTi_Uart0.xm= l and the line
<flag name=3D"INS_LINK" value=3D"Uart0= " />
was there during my problem.
However I add the following lines in the in= s_xsens.c and it make the building work well :
#ifndef INS_LINK
#define INS_LINK Uart0
#endif

After ma= ny tests, I still can't make the MTI working. It seems that I never ent= er into the function "parse_ins_msg" & "parse_ins_buffer= " of ins_xsens.c
Do I have to call them in the ins_xsens.xml? or in the ins_periodic_task (w= ich do a "XSENS_ReqGPSStatus" not usefull in a MTI, I think...)? = or in the main_ap.c?

Thank you for your help

Regards,
=A0=A0=A0=A0 Franck
--0015174be03ebea9e504720e5e43-- From MAILER-DAEMON Wed Aug 26 13:23:03 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MgMD9-0007ND-Jv for mharc-paparazzi-devel@gnu.org; Wed, 26 Aug 2009 13:23:03 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MgMD6-0007Ip-U3 for paparazzi-devel@nongnu.org; Wed, 26 Aug 2009 13:23:01 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MgMD2-0007DK-25 for paparazzi-devel@nongnu.org; Wed, 26 Aug 2009 13:23:00 -0400 Received: from [199.232.76.173] (port=45919 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MgMD1-0007D6-PQ for paparazzi-devel@nongnu.org; Wed, 26 Aug 2009 13:22:55 -0400 Received: from imss-1.enac.fr ([195.220.159.36]:47008) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MgLlT-00060j-Di for paparazzi-devel@nongnu.org; Wed, 26 Aug 2009 12:54:28 -0400 Received: from mauve.recherche.enac.fr (imss-1.imss.interne.enac [127.0.0.1]) by imss-1.enac.fr (Postfix) with ESMTP id EA83718B3A2 for ; Wed, 26 Aug 2009 18:54:12 +0200 (CEST) Received: from [10.31.1.82] (sepia.recherche.enac.fr [10.31.1.82])by mauve.recherche.enac.fr (Postfix) with ESMTP id CF8CD2FA822for ; Wed, 26 Aug 2009 18:54:12 +0200 (CEST) Message-ID: <4A9568B4.5000504@free.fr> Date: Wed, 26 Aug 2009 18:54:12 +0200 From: Pascal Brisset User-Agent: Mozilla-Thunderbird 2.0.0.22 (X11/20090706) MIME-Version: 1.0 To: paparazzi-devel@nongnu.org Subject: Re: [Paparazzi-devel] Procedures References: <538503.42596.qm@web51512.mail.re2.yahoo.com> In-Reply-To: <538503.42596.qm@web51512.mail.re2.yahoo.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-imss-version: 2.5 X-imss-result: Passed X-imss-scores: Clean:15.27046 C:21 M:1 S:5 R:5 X-imss-settings: Baseline:1 C:1 M:1 S:1 R:1 (0.0000 0.0000) X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.4-2.6 X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Aug 2009 17:23:01 -0000 Hi Todd, this feature has not been updated and tested ... for years. Some remarks: - you file should start with -
is currently not allowed (according to the dtd) in a procedure - the alt attribute of a waypoint must be a constant number. Anyway, it won't work :-( Currently, when a procedure is included, all the waypoints name of the procedure are prefixed with the name of the procedure by the preprocessing tool. So in your case, if I include your file with the TARGET waypoint would be renamed into drop.TARGET. This renaming is needed if you want to include several times the same procedure ( with different arguments). But, you are referencing directly the waypoint name from some C code (NavSetWaypointHere(WP_TARGET)) and the procedure preprocessor is not able to look at this C code (to replace WP_TARGET by WP_drop_TARGET). So ... I don't know. This preprocessor was written at a time when few C code was included in flight plans. Now it is common, and there is no way to preprocess it. A solution here would be to restrict procedure includes to one single instance and get rid of the waypoint prefixing. It probably requires deeper thinking --Pascal Todd Sandercock wrote: > Hi all > i am just looking for some feedback on anyone that has got any > procedures to work properly. I have been working on some routines for > payload dropping and i wanted to put them in a procedure so that i > could use the same code over many flight plans. I am not sure how > limited procedures are but this is what i have written > > Thanks for any help > Todd > > >
> #include "datalink.h" > #include "bomb.h" >
> > > > > > > > > > > > > > > > > > > > > until="NavQdrCloseTo(DegOfRad(bomb_start_qdr)-10)" wp="BLEG"/> > > > > hmode="route" wp="RELEASE"/> > > > > > > > > > > > > >
> > ------------------------------------------------------------------------ > Find local businesses and services in your area with Yahoo!7 Local. > Get started > <%20http://au.rd.yahoo.com/search/local/mailtagline/*http://local.yahoo.com.au>. > > ------------------------------------------------------------------------ > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > From MAILER-DAEMON Wed Aug 26 23:59:40 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MgW9E-0007pc-79 for mharc-paparazzi-devel@gnu.org; Wed, 26 Aug 2009 23:59:40 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MgW9C-0007ou-LP for paparazzi-devel@nongnu.org; Wed, 26 Aug 2009 23:59:38 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MgW97-0007mX-4y for paparazzi-devel@nongnu.org; Wed, 26 Aug 2009 23:59:38 -0400 Received: from [199.232.76.173] (port=37386 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MgW96-0007mQ-Sm for paparazzi-devel@nongnu.org; Wed, 26 Aug 2009 23:59:32 -0400 Received: from web51512.mail.re2.yahoo.com ([206.190.39.158]:36463) by monty-python.gnu.org with smtp (Exim 4.60) (envelope-from ) id 1MgW96-0000Wu-Ad for paparazzi-devel@nongnu.org; Wed, 26 Aug 2009 23:59:32 -0400 Received: (qmail 19507 invoked by uid 60001); 27 Aug 2009 03:59:31 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com.au; s=s1024; t=1251345571; bh=DEAjd4DYghzKTGPjkL4VYOVjqyPUbzRMxAxPvpq5t9Y=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=MGbL8V3Nt4h7LtRZehhz+c2wM/Q2XOeDchmTRiN/LTVpKdc2m1VqKCYSBr7x9kV2uvihoy4UfrEdQKOSkx6LriR7oCMXc5gAjOfmSR/0bvc98Ob2+4ZBEc7yMhUktj8uQnJ6HSKtciZD1RdvR7gIvkNRDjmPI2bq1hXTVN7p7zw= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com.au; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=lw9SwkWJBUAq4SH1EiDfg4FvIVVOS/Rw7Sz4Kv0BRkVAcggnH/8zSK+Qy1DBXghf+zgdvq6KckW5ZgSjGLILrzLnfY0MzicHqI0upq+4ELk/2FW7FKRfOlvtlWHiP3qeO1nM/zebJgxHLCDXFd610v9OFa29PogZ4cJb51qmQWY=; Message-ID: <867915.3994.qm@web51512.mail.re2.yahoo.com> X-YMail-OSG: dhRiKVkVM1k.4GYUAjW58JV0hfdOxz9AOvpVBXmDpM865nZkEstFYRddRG.dzZkOGo7s9dz503t2HsRQmP3RlMKtvpnQmn2QVnZTgscHRGq0Njki3FBcz6K2odUoxExSiVPalsFKD.ftXOHVIkg26j8Kmn350igwIx8jEHmIs3NDPzZGZ9pCF3LBON5gAtks3vjrrYI4NSRsb_nRBDBnAslV0Co3DuVEMKXP86EwXLveFqTUqih_FjDPW6pAwvPs2uHSES0smoys73qnc59xVMb4Ruxf8t1B54hPm9yIr7VJ3W8IhSnfnYC_ej3xzQpEvhq7EOZRXLOVyc.TRiluniQnekv8j2nPPgw- Received: from [192.43.227.18] by web51512.mail.re2.yahoo.com via HTTP; Wed, 26 Aug 2009 20:59:31 PDT X-Mailer: YahooMailRC/1358.27 YahooMailWebService/0.7.338.2 References: <538503.42596.qm@web51512.mail.re2.yahoo.com> <4A9568B4.5000504@free.fr> Date: Wed, 26 Aug 2009 20:59:31 -0700 (PDT) From: Todd Sandercock Subject: Re: [Paparazzi-devel] Procedures To: paparazzi-devel@nongnu.org In-Reply-To: <4A9568B4.5000504@free.fr> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-1017804026-1251345571=:3994" X-detected-operating-system: by monty-python.gnu.org: FreeBSD 6.x (1) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Aug 2009 03:59:38 -0000 --0-1017804026-1251345571=:3994 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Thanks Pascal=0A=0AMakes sense why it wasn't working then. I'll ditch that = idea for now.=0AIs there a way of including xml's in a flight plan? I don't= actually need the arguments and the position etc for the routines i want a= dd so just including an XML is what i was after=0A=0ATodd=0A=0A=0A=0A______= __________________________=0AFrom: Pascal Brisset = =0ATo: paparazzi-devel@nongnu.org=0ASent: Thursday, 27 August, 2009 2:24:12= AM=0ASubject: Re: [Paparazzi-devel] Procedures=0A=0AHi Todd,=0A=0Athis fea= ture has not been updated and tested ... for years. Some remarks:=0A- you f= ile should start with=0A=0A- <= header> is currently not allowed (according to the dtd) in a procedure=0A- = the alt attribute of a waypoint must be a constant number.=0AAnyway, it won= 't work :-(=0ACurrently, when a procedure is included, all the waypoints na= me of the procedure are prefixed with the name of the procedure by the=0Apr= eprocessing tool. So in your case, if I include your file with=0A=0A =0A =0A = =0A=0Athe TARGET waypoint would be renamed into drop.TARGET. This renaming = is needed if you want to include several times the same procedure ( with di= fferent arguments). But, you are referencing directly the waypoint name fro= m some C code (NavSetWaypointHere(WP_TARGET)) and the procedure preprocesso= r is not able to look at this C code (to replace WP_TARGET by WP_drop_TARGE= T).=0ASo ... I don't know.=0AThis preprocessor was written at a time when f= ew C code was included in flight plans. Now it is common, and there is no w= ay to preprocess it. A solution here would be to restrict procedure include= s to one single instance and get rid of the waypoint prefixing.=0AIt probab= ly requires deeper thinking=0A=0A--Pascal=0A=0A=0ATodd Sandercock wrote:=0A= > Hi all=0A> i am just looking for some feedback on anyone that has got any= procedures to work properly. I have been working on some routines for payl= oad dropping and i wanted to put them in a procedure so that i could use th= e same code over many flight plans. I am not sure how limited procedures ar= e but this is what i have written=0A> =0A> Thanks for any help=0A> Todd=0A>= =0A> =0A>
=0A> #include "datalink.h"=0A> #inc= lude "bomb.h"=0A>
=0A> =0A> =0A> =0A> = =0A> =0A> = =0A> =0A> =0A> =0A> =0A> =0A> =0A> =0A> =0A> =0A> =0A> =0A> =0A> =0A> =0A> = =0A> =0A> =0A> =0A> =0A> =0A> =0A> =0A> =0A> = =0A> =0A> =0A> =0A> =0A> = =0A> =0A> =0A>
= =0A> =0A> -----------------------------------------------------------------= -------=0A> Find local businesses and services in your area with Yahoo!7 Lo= cal. Get started <%20http://au.rd.yahoo.com/search/local/mailtagline/*http:= //local.yahoo.com.au>. =0A> -----------------------------------------------= -------------------------=0A> =0A> ________________________________________= _______=0A> Paparazzi-devel mailing list=0A> Paparazzi-devel@nongnu.org=0A>= http://lists.nongnu.org/mailman/listinfo/paparazzi-devel=0A> =0A=0A=0A=0A= _______________________________________________=0APaparazzi-devel mailing l= ist=0APaparazzi-devel@nongnu.org=0Ahttp://lists.nongnu.org/mailman/listinfo= /paparazzi-devel=0A=0A=0A=0A _________________________________________= _________________________________________=0AFind local businesses and servi= ces in your area with Yahoo!7 Local.=0AGet started: http://local.yahoo.com.= au --0-1017804026-1251345571=:3994 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Thanks Pascal

Makes sense why it wasn't = working then. I'll ditch that idea for now.
Is there a way of inc= luding xml's in a flight plan? I don't actually need the arguments and the = position etc for the routines i want add so just including an XML is what i= was after

Todd

=
From: Pasca= l Brisset <pascal.brisset@free.fr>
To: paparazzi-devel@nongnu.org
Sent: Thursday, 27 August, 2009 2:24:12 AM
= Subject: Re: [Paparazzi-devel] Pro= cedures

Hi Todd,

this feature has not been updated and= tested ... for years. Some remarks:
- you file should start with
<= ;!DOCTYPE procedure SYSTEM "flight_plan.dtd">
- <header> is cur= rently not allowed (according to the dtd) in a procedure
- the alt attri= bute of a waypoint must be a constant number.
Anyway, it won't work :-(<= br>Currently, when a procedure is included, all the waypoints name of the p= rocedure are prefixed with the name of the procedure by the
preprocessin= g tool. So in your case, if I include your file with

  <inc= lude name=3D"drop" procedure=3D"proc_drop.xml" x=3D"-100" y=3D"150" rotate= =3D"0">
    <arg name=3D"alt" value=3D"ground_alt+100"/&= gt;
  </include>

the TARGET waypoint would be renamed= into drop.TARGET. This renaming is needed if you want to include several t= imes the same procedure ( with different arguments). But, you are referencing direc= tly the waypoint name from some C code (NavSetWaypointHere(WP_TARGET)) and = the procedure preprocessor is not able to look at this C code (to replace W= P_TARGET by WP_drop_TARGET).
So ... I don't know.
This preprocessor w= as written at a time when few C code was included in flight plans. Now it i= s common, and there is no way to preprocess it. A solution here would be to= restrict procedure includes to one single instance and get rid of the wayp= oint prefixing.
It probably requires deeper thinking

--Pascal
=

Todd Sandercock wrote:
> Hi all
> i am just looking for= some feedback on anyone that has got any procedures to work properly. I ha= ve been working on some routines for payload dropping and i wanted to put t= hem in a procedure so that i could use the same code over many flight plans= . I am not sure how limited procedures are but this is what i have written
>
> Thanks for any help
> Todd
>
>= <procedure>
>  <header>
>    #inc= lude "datalink.h"
>    #include "bomb.h"
>  &l= t;/header>
>  <param name=3D"alt" default_value=3D"ground= _alt+50"/>
>  <param name=3D"radius" default_value=3D"75"= />
>  <waypoints>
>    <waypoint a= lt=3D"alt" name=3D"TARGET" x=3D"0" y=3D"0"/>
>    <w= aypoint alt=3D"alt" name=3D"START" x=3D"0" y=3D"-100"/>
>  &n= bsp; <waypoint name=3D"RELEASE" x=3D"0" y=3D"-50"/>
>  &n= bsp; <waypoint name=3D"BLEG" x=3D"100" y=3D"-100"/>
>  &n= bsp; <waypoint alt=3D"alt+50" name=3D"BCLIMB" x=3D"0" y=3D"100"/>>    <waypoint alt=3D"alt+50" name=3D"BFEIGHT" x=3D"100" = y=3D"0"/>
>  </waypoints>
>  <blocks>= ;
>    <block name=3D"bombloiter" strip_button=3D"B Loiter">
>    &nb= sp; <call fun=3D"NavSetWaypointHere(WP_TARGET)"/>
>  &nbs= p;   <eight center=3D"WP_TARGET" radius=3D"radius" turn_around=3D"= WP_BEIGHT"/>
>    </block>
>    = <block name=3D"bombhere" strip_button=3D"B Here">
>   = ;   <call fun=3D"NavSetWaypointHere(WP_TARGET)"/>
> =   </block>
>    <block name=3D"bomb" strip= _button=3D"Bomb">
>      <!--<set value=3D"W= aypointX(WP_TARGET)" var=3D"WaypointX(WP_START)"/>
>    =   <set value=3D"WaypointY(WP_TARGET) - 100" var=3D"WaypointY(WP_ST= ART)"/>
>      <set value=3D"WaypointX(WP_TARGE= T)" var=3D"WaypointX(WP_CLIMB)"/>
>      <set v= alue=3D"WaypointY(WP_TARGET) + 100" var=3D"WaypointY(WP_CLIMB)"/>
>= ;      <set value=3D"BombComputeApproach(WP_TARGET, WP_START, nav_radius)" var=3D"unit= "/>-->
>      <circle radius=3D"nav_radius" = until=3D"NavQdrCloseTo(DegOfRad(bomb_start_qdr)-10)" wp=3D"BLEG"/>
&g= t;    </block>
>    <block name=3D"ali= gn">
>      <exception cond=3D"BombUpdateReleas= e(WP_TARGET)" deroute=3D"end"/>
>      <go appr= oaching_time=3D"bomb_trigger_delay" from=3D"START" hmode=3D"route" wp=3D"RE= LEASE"/>
>    </block>
>    <= block name=3D"shoot">
>      <set value=3D"Bomb= Shoot()" var=3D"unit"/>
>      <go from=3D"RELE= ASE" hmode=3D"route" wp=3D"BCLIMB"/>
>      <se= t value=3D"BombCloseHatch()" var=3D"unit"/>
>      = <deroute block=3D"end"/>
>    </block>
>= ;    <block name=3D"close">
>      <set value=3D"BombClose= Hatch()" var=3D"unit"/>
>      <deroute block= =3D"end"/>
>    </block>
>  </bloc= ks>
> </procedure>
>
> ------------------------= ------------------------------------------------
> Find local busines= ses and services in your area with Yahoo!7 Local. Get started <%20http://au.rd.yahoo.com/search/local/mailtagline/*ht= tp://local.yahoo.com.au>.
> ---------------------------------= ---------------------------------------
>
> __________________= _____________________________
> Paparazzi-devel mailing list
> = Paparazzi-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel



______________________________________________= _
Paparazzi-devel mailing list
Paparazzi-devel@nongn= u.org
http://lists.nongnu.org/mailman/listinfo/paparazzi= -devel

=0A= =0A=0A=0A
=0AFind local businesses and services in your a= rea with Yahoo!7 Local. Get started. --0-1017804026-1251345571=:3994-- From MAILER-DAEMON Thu Aug 27 01:58:50 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MgY0Y-0001zg-8C for mharc-paparazzi-devel@gnu.org; Thu, 27 Aug 2009 01:58:50 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MgY0V-0001zC-CP for paparazzi-devel@nongnu.org; Thu, 27 Aug 2009 01:58:47 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MgY0T-0001z0-CP for paparazzi-devel@nongnu.org; Thu, 27 Aug 2009 01:58:46 -0400 Received: from [199.232.76.173] (port=35793 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MgY0T-0001yx-5X for paparazzi-devel@nongnu.org; Thu, 27 Aug 2009 01:58:45 -0400 Received: from smtp1.infomaniak.ch ([84.16.68.89]:55851) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MgY0S-0004ME-Fk for paparazzi-devel@nongnu.org; Thu, 27 Aug 2009 01:58:44 -0400 Received: from rome (247-232.77-83.cust.bluewin.ch [83.77.232.247]) (authenticated bits=0) by smtp1.infomaniak.ch (8.14.2/8.14.2) with ESMTP id n7R5wd9I015626 for ; Thu, 27 Aug 2009 07:58:40 +0200 From: =?iso-8859-1?Q?C=E9dric_Marzer?= To: Date: Thu, 27 Aug 2009 07:58:42 +0200 Message-ID: <008101ca26db$6ec97430$4c5c5c90$@marzer@mrsa.ch> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0082_01CA26EC.32524430" X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Acom222MadoHn22nSkqG4FFuQWj8mA== Content-Language: fr-ch X-Antivirus: Dr.Web (R) for Mail Servers on smtp1 host X-Antivirus-Code: 100000 X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6? (barebone, rare!) Subject: [Paparazzi-devel] Protocol for the downlink X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Aug 2009 05:58:48 -0000 This is a multi-part message in MIME format. ------=_NextPart_000_0082_01CA26EC.32524430 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi all, =20 I am currently working on an OSD board that I want to hook up at my = tinyV2 in parrallel with the modem. The idea is to decode the downlink telemetry going through the serial = port to the modem and print data on the video downlink. =20 I have been trying to understand the telemtry data but it isn't obvious = even with the code. If I understand well the code and structure for each = message is defined in the message.h file that is dynamicaly generated when compiling. What I didn't get so far is the exact structure of the = telemetry data going through the serial line. Could someone help me with this ? =20 Thanks in advance =20 C=E9dric =20 ------=_NextPart_000_0082_01CA26EC.32524430 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Hi all,

 

I am currently working on an OSD board that I want = to hook up at my tinyV2 in parrallel with the modem.

The idea is to decode the downlink telemetry going = through the serial port to the modem and print data on the video = downlink.

 

I have been trying to understand the telemtry data = but it isn't obvious even with the code. If I understand well the code and = structure for each message is defined in the message.h file that is dynamicaly = generated when compiling. What I didn't get so far is the exact structure of the telemetry data going through the serial line. Could someone help me with = this ?

 

Thanks in advance

 

C=E9dric

 

------=_NextPart_000_0082_01CA26EC.32524430-- From MAILER-DAEMON Thu Aug 27 02:02:20 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MgY3v-0005DP-Ud for mharc-paparazzi-devel@gnu.org; Thu, 27 Aug 2009 02:02:19 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MgY3s-0005Cc-Rt for paparazzi-devel@nongnu.org; Thu, 27 Aug 2009 02:02:17 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MgY3m-00059H-JP for paparazzi-devel@nongnu.org; Thu, 27 Aug 2009 02:02:14 -0400 Received: from [199.232.76.173] (port=36851 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MgY3m-000596-AL for paparazzi-devel@nongnu.org; Thu, 27 Aug 2009 02:02:10 -0400 Received: from mta-2.ms.rz.rwth-aachen.de ([134.130.7.73]:54836) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MgY3l-00054Z-IJ for paparazzi-devel@nongnu.org; Thu, 27 Aug 2009 02:02:09 -0400 MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=ISO-8859-1 Received: from ironport-out-1.rz.rwth-aachen.de ([134.130.5.40]) by mta-2.ms.rz.RWTH-Aachen.de (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008)) with ESMTP id <0KP000F7VU3K0Q50@mta-2.ms.rz.RWTH-Aachen.de> for paparazzi-devel@nongnu.org; Thu, 27 Aug 2009 08:02:08 +0200 (CEST) X-IronPort-AV: E=Sophos;i="4.44,284,1249250400"; d="scan'208";a="23814332" Received: from relay-1.ms.rz.rwth-aachen.de (HELO relay.rwth-aachen.de) ([134.130.7.74]) by ironport-in-1.rz.rwth-aachen.de with ESMTP; Thu, 27 Aug 2009 08:02:08 +0200 Received: from [134.130.150.40] (pc40.dynamik.RWTH-Aachen.DE [134.130.150.40]) by relay.rwth-aachen.de (8.13.8+Sun/8.13.8/1) with ESMTP id n7R627T4013928 for ; Thu, 27 Aug 2009 08:02:07 +0200 (CEST) Message-id: <4A96215F.9070103@web.de> Date: Thu, 27 Aug 2009 08:02:07 +0200 From: Andreas Gaeb User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) To: paparazzi-devel@nongnu.org Subject: Re: [Paparazzi-devel] Re: MTI on Twog problem References: <41cdc6cc0908260959y7d28881eh318ffd59f613dee4@mail.gmail.com> In-reply-to: <41cdc6cc0908260959y7d28881eh318ffd59f613dee4@mail.gmail.com> X-detected-operating-system: by monty-python.gnu.org: Solaris 10 (beta) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Aug 2009 06:02:17 -0000 Hi Franck, Franck Marchand schrieb: > Hi Andreas > > Indeed I am using a level converter on the MTI (not MTI-G, so no GPS for the > moment). I was already using the ins_xsens_MTi_Uart0.xml and the line > > was there during my problem. > However I add the following lines in the ins_xsens.c and it make the > building work well : > #ifndef INS_LINK > #define INS_LINK Uart0 > #endif Strange, this would indicate that something with the module processing does not work properly. Or maybe a typo somewhere? > After many tests, I still can't make the MTI working. It seems that I never > enter into the function "parse_ins_msg" & "parse_ins_buffer" of ins_xsens.c > Do I have to call them in the ins_xsens.xml? or in the ins_periodic_task > (wich do a "XSENS_ReqGPSStatus" not usefull in a MTI, I think...)? or in the > main_ap.c? You need to add a call manually to the event_task_ap() in main_ap.c. Basically it's the same as the GPS call I posted in the last mail. Something like #ifndef HITL if (InsBuffer()) { ReadInsBuffer(); } #endif if (ins_msg_received) { parse_ins_msg(); ins_msg_received = FALSE; do_something_with_INS_data(); } should do the trick. Regards, Andreas From MAILER-DAEMON Thu Aug 27 02:19:10 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MgYKE-0000fl-N4 for mharc-paparazzi-devel@gnu.org; Thu, 27 Aug 2009 02:19:10 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MgYKD-0000eh-2U for paparazzi-devel@nongnu.org; Thu, 27 Aug 2009 02:19:09 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MgYK7-0000bI-Fb for paparazzi-devel@nongnu.org; Thu, 27 Aug 2009 02:19:08 -0400 Received: from [199.232.76.173] (port=32866 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MgYK7-0000bD-7A for paparazzi-devel@nongnu.org; Thu, 27 Aug 2009 02:19:03 -0400 Received: from mail-yw0-f192.google.com ([209.85.211.192]:39392) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MgYK6-00078k-Sm for paparazzi-devel@nongnu.org; Thu, 27 Aug 2009 02:19:03 -0400 Received: by ywh30 with SMTP id 30so956711ywh.25 for ; Wed, 26 Aug 2009 23:19:01 -0700 (PDT) MIME-Version: 1.0 Received: by 10.101.59.17 with SMTP id m17mr9165630ank.13.1251353941101; Wed, 26 Aug 2009 23:19:01 -0700 (PDT) In-Reply-To: <4321767239366326187@unknownmsgid> References: <4321767239366326187@unknownmsgid> Date: Thu, 27 Aug 2009 00:19:01 -0600 Message-ID: <875d4d950908262319u5cd18b55l6a12029b8f30f0e5@mail.gmail.com> Subject: Re: [Paparazzi-devel] Protocol for the downlink From: Haiyang Chao To: paparazzi-devel@nongnu.org Content-Type: multipart/alternative; boundary=001636ed734f25cc400472198b89 X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Aug 2009 06:19:09 -0000 --001636ed734f25cc400472198b89 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi. You may want to check conf/messages.xml (the definition of all the telemetr= y messages/structures) and any data log file(e.g var/logs/date_time.data). Haiyang On Wed, Aug 26, 2009 at 11:58 PM, C=E9dric Marzer wr= ote: > Hi all, > > > > I am currently working on an OSD board that I want to hook up at my tinyV= 2 > in parrallel with the modem. > > The idea is to decode the downlink telemetry going through the serial por= t > to the modem and print data on the video downlink. > > > > I have been trying to understand the telemtry data but it isn't obvious > even with the code. If I understand well the code and structure for each > message is defined in the message.h file that is dynamicaly generated whe= n > compiling. What I didn't get so far is the exact structure of the telemet= ry > data going through the serial line. Could someone help me with this ? > > > > Thanks in advance > > > > C=E9dric > > > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > > --001636ed734f25cc400472198b89 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi.

You may want to check conf/messages.xml (the definition of all t= he telemetry messages/structures) and any data log file(e.g var/logs/date_t= ime.data).

Haiyang
On Wed, Aug 26, 200= 9 at 11:58 PM, C=E9dric Marzer <cedric.marzer@mrsa.ch> wrote:

Hi all,

=A0

I am currently working on an OSD board that I want to hook up at my tinyV2 in parrallel with the modem.

The idea is to decode the downlink telemetry going through the serial port to the modem and print data on the video downlink.

=A0

I have been trying to understand the telemtry data but it isn't obvious even with the code. If I understand well the code and str= ucture for each message is defined in the message.h file that is dynamicaly genera= ted when compiling. What I didn't get so far is the exact structure of the telemetry data going through the serial line. Could someone help me with th= is ?

=A0

Thanks in advance

=A0

C=E9dric

=A0


_______________________________________________
Paparazzi-devel mailing list
Paparazzi-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/paparazzi-devel
--001636ed734f25cc400472198b89-- From MAILER-DAEMON Thu Aug 27 03:15:53 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MgZD7-00061z-5N for mharc-paparazzi-devel@gnu.org; Thu, 27 Aug 2009 03:15:53 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MgZD5-0005zv-Aa for paparazzi-devel@nongnu.org; Thu, 27 Aug 2009 03:15:51 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MgZCz-0005vy-V8 for paparazzi-devel@nongnu.org; Thu, 27 Aug 2009 03:15:50 -0400 Received: from [199.232.76.173] (port=52071 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MgZCz-0005vv-QJ for paparazzi-devel@nongnu.org; Thu, 27 Aug 2009 03:15:45 -0400 Received: from mx20.gnu.org ([199.232.41.8]:16574) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MgZCz-0006vI-8i for paparazzi-devel@nongnu.org; Thu, 27 Aug 2009 03:15:45 -0400 Received: from basicbox10.server-home.net ([195.137.212.35]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MgZCx-00038N-HA for paparazzi-devel@nongnu.org; Thu, 27 Aug 2009 03:15:43 -0400 Received: by basicbox10.server-home.net (Postfix, from userid 1141) id ECB84C8451A; Thu, 27 Aug 2009 09:15:41 +0200 (CEST) To: paparazzi-devel@nongnu.org Subject: =?ISO-8859-1?Q?Re: [Paparazzi-devel]?= =?ISO-8859-1?Q? Protocol for the dow?= =?ISO-8859-1?Q?nlink?= From: martin@pfump.org X-Priority: 3 Importance: Normal X-MSMail-Priority: Normal X-MimeOLE: Produced by Confixx WebMail X-Mailer: Confixx WebMail (like SquirrelMail) Cc: MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <20090827071541.ECB84C8451A@basicbox10.server-home.net> Date: Thu, 27 Aug 2009 09:15:41 +0200 (CEST) X-Detected-Operating-System: by mx20.gnu.org: GNU/Linux 2.6 (newer, 3) X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6, seldom 2.4 (older, 4) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Aug 2009 07:15:51 -0000 Hi Cédric, > What I didn't get so far is the exact structure of the telemetry data going through > the serial line. Could someone help me with this ? the outer part is slightly different for transparent and xbee messages, they are shown at http://paparazzi.enac.fr/wiki/Messages_Format There is the logger code that parses the outer part of a message and some example code that generates a message and allows to print data from the serial port: sw/airborne/main_logger.c sw/in_progress/turbine/ Martin From MAILER-DAEMON Thu Aug 27 05:05:47 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MgavS-0007MX-P5 for mharc-paparazzi-devel@gnu.org; Thu, 27 Aug 2009 05:05:47 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MgavQ-0007LO-8Y for paparazzi-devel@nongnu.org; Thu, 27 Aug 2009 05:05:44 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MgavO-0007KV-CT for paparazzi-devel@nongnu.org; Thu, 27 Aug 2009 05:05:43 -0400 Received: from [199.232.76.173] (port=34113 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MgavO-0007KM-5c for paparazzi-devel@nongnu.org; Thu, 27 Aug 2009 05:05:42 -0400 Received: from smtp1.infomaniak.ch ([84.16.68.89]:55435) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MgavN-0007Fz-9x for paparazzi-devel@nongnu.org; Thu, 27 Aug 2009 05:05:41 -0400 Received: from rome (247-232.77-83.cust.bluewin.ch [83.77.232.247]) (authenticated bits=0) by smtp1.infomaniak.ch (8.14.2/8.14.2) with ESMTP id n7R95YL4015739 for ; Thu, 27 Aug 2009 11:05:38 +0200 From: =?iso-8859-1?Q?C=E9dric_Marzer?= To: References: <20090827071541.ECB84C8451A@basicbox10.server-home.net> In-Reply-To: <20090827071541.ECB84C8451A@basicbox10.server-home.net> Subject: RE: [Paparazzi-devel] Protocol for the downlink Date: Thu, 27 Aug 2009 11:05:38 +0200 Message-ID: <00b301ca26f5$8e36cec0$aaa46c40$@marzer@mrsa.ch> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Acom5j4eZ4zriodkR+ShBy2eV0dGsQADzuXw Content-Language: fr-ch X-Antivirus: Dr.Web (R) for Mail Servers on smtp1 host X-Antivirus-Code: 100000 X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6? (barebone, rare!) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Aug 2009 09:05:44 -0000 Thanks a lot. That is exactly what I was looking for. Cheers C=E9dric -----Message d'origine----- De=A0: paparazzi-devel-bounces+cedric.marzer=3Dmrsa.ch@nongnu.org [mailto:paparazzi-devel-bounces+cedric.marzer=3Dmrsa.ch@nongnu.org] De = la part de martin@pfump.org Envoy=E9=A0: jeudi, 27. ao=FBt 2009 09:16 =C0=A0: paparazzi-devel@nongnu.org Objet=A0: Re: [Paparazzi-devel] Protocol for the downlink Hi C=E9dric, > What I didn't get so far is the exact structure of the telemetry data going through > the serial line. Could someone help me with this ? the outer part is slightly different for transparent and xbee messages, they are shown at http://paparazzi.enac.fr/wiki/Messages_Format There is the logger code that parses the outer part of a message and some example code that generates a message and allows to print data from the serial port: sw/airborne/main_logger.c sw/in_progress/turbine/ Martin _______________________________________________ Paparazzi-devel mailing list Paparazzi-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/paparazzi-devel From MAILER-DAEMON Thu Aug 27 08:47:34 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MgeO2-0004LA-MQ for mharc-paparazzi-devel@gnu.org; Thu, 27 Aug 2009 08:47:31 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MgeNt-0004Io-LK for paparazzi-devel@nongnu.org; Thu, 27 Aug 2009 08:47:21 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MgeNm-0004Dj-Vu for Paparazzi-devel@nongnu.org; Thu, 27 Aug 2009 08:47:20 -0400 Received: from [199.232.76.173] (port=53815 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MgeNk-0004DP-Mr for Paparazzi-devel@nongnu.org; Thu, 27 Aug 2009 08:47:13 -0400 Received: from web51507.mail.re2.yahoo.com ([206.190.38.199]:35786) by monty-python.gnu.org with smtp (Exim 4.60) (envelope-from ) id 1MgeNk-0004GW-Bm for Paparazzi-devel@nongnu.org; Thu, 27 Aug 2009 08:47:12 -0400 Received: (qmail 98745 invoked by uid 60001); 27 Aug 2009 12:47:01 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com.au; s=s1024; t=1251377221; bh=FuhpmiLuMJ/HyyZoEp/HmzZnSgYb2Yrt0yGnD+6rYC4=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=nQaOZSbh/GwBE+I8/2nCg4829BJD06Z4ak6kCH6njXoPQ5YVEU2I4BV+T3y64j1nTa7PgyT9KRGs33axvp24i/h8EqZSWOQufzbdlc77imvlNoJ4yR0amwkLusKYoXiFxCw+H+jbR+EgSHsBM06ve3SvPpCkD8pyB5+3LHTBY58= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com.au; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=moWqGqWCP6T+qYkuV5WUReEFXSVgj/6ui+i0hHfOif2aLtl6ylNcImf/iLMQ65iPSy84sXyzWjtS2eyHT3Inrrz05ZjcEzvphDsSXakM7n6J8K5465ffE3J+TceP3qB3jjcm27jbc6A3bESNBsRTkeM8kCwGIOJY6yAvhin5MNg=; Message-ID: <263445.98393.qm@web51507.mail.re2.yahoo.com> X-YMail-OSG: 2vwOqK0VM1m5ZMdlL3TD.Bi620Vxu7TD5zkJX.AEvE9wAE6tTzRkKyoxOK5hQapLdUG46gbs.G7O6VYuq_TylwAY48OAX9z7PQ.dkB34fb0BM23gd7sFDniFmmnPFW0yl_DahnVpT5SJl53hPnUsj8xqS5SVr3ftMELsYK1g95J7C09LiQHzCUgs6kVOt8B3xLLhk4E.aX7x_nWsDjqdYkjRIus3l8ByjbMJp3_0vkj0CqkvNybBuIAiin12XGaIvx5UE2fq1d2oWwPLm6G2.kx71zyJS3vGqw7j0vLZ_zvYo3Zc2bsSbul5bXtRVkXG1H4HuyVbs9Kmt0mGp.VkcK1IzjSN0v2WNBXQ3aG_QZtp8Ed35MDOpSVPRqCQz66o7SHvAxEAeTJmdHAyxV8Fo2UC8pI- Received: from [121.45.214.22] by web51507.mail.re2.yahoo.com via HTTP; Thu, 27 Aug 2009 05:47:01 PDT X-Mailer: YahooMailRC/1358.27 YahooMailWebService/0.7.338.2 Date: Thu, 27 Aug 2009 05:47:01 -0700 (PDT) From: Todd Sandercock To: Paparazzi Development MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-1877513702-1251377221=:98393" X-detected-operating-system: by monty-python.gnu.org: FreeBSD 6.x (1) Cc: Subject: [Paparazzi-devel] Odd or even X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Aug 2009 12:47:22 -0000 --0-1877513702-1251377221=:98393 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi is there any quick way to work out if a number is odd or even in a fligh= t plan??=0Amy idea was "var % 2" but remainder is not supported=0AAnyone go= t any ideas?=0A=0AThanks=0ATodd=0A=0A=0A=0A __________________________= ________________________________________________________=0AFind local busin= esses and services in your area with Yahoo!7 Local.=0AGet started: http://l= ocal.yahoo.com.au --0-1877513702-1251377221=:98393 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Hi is there any quick way to work out if a number is odd or even in= a flight plan??
my idea was "var % 2" but remainder is not supportedAnyone got any ideas?

Thanks
Todd

=0A=0A=0A= =0A
=0AFind local businesses and services in your area wi= th Yahoo!7 Local. Get started. --0-1877513702-1251377221=:98393-- From MAILER-DAEMON Thu Aug 27 12:55:39 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MgiGB-00033d-IT for mharc-paparazzi-devel@gnu.org; Thu, 27 Aug 2009 12:55:39 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MgiGA-00031k-5W for paparazzi-devel@nongnu.org; Thu, 27 Aug 2009 12:55:38 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MgiG5-0002vQ-48 for paparazzi-devel@nongnu.org; Thu, 27 Aug 2009 12:55:37 -0400 Received: from [199.232.76.173] (port=45864 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MgiG4-0002uz-Rn for paparazzi-devel@nongnu.org; Thu, 27 Aug 2009 12:55:32 -0400 Received: from bay0-omc3-s33.bay0.hotmail.com ([65.54.246.233]:28166) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MgiG3-0001vE-Vy for paparazzi-devel@nongnu.org; Thu, 27 Aug 2009 12:55:32 -0400 Received: from BAY119-W35 ([207.46.9.70]) by bay0-omc3-s33.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 27 Aug 2009 09:55:30 -0700 Message-ID: Content-Type: multipart/alternative; boundary="_13759246-cb89-486b-92dc-210cd52a79e6_" X-Originating-IP: [206.47.249.252] From: Yves Touchette To: Subject: RE: [Paparazzi-devel] Protocol for the downlink Date: Thu, 27 Aug 2009 12:55:30 -0400 Importance: Normal In-Reply-To: <008101ca26db$6ec97430$4c5c5c90$@marzer@mrsa.ch> References: <008101ca26db$6ec97430$4c5c5c90$@marzer@mrsa.ch> MIME-Version: 1.0 X-OriginalArrivalTime: 27 Aug 2009 16:55:30.0463 (UTC) FILETIME=[2F5A92F0:01CA2737] X-detected-operating-system: by monty-python.gnu.org: Windows 2000 SP4, XP SP1+ X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Aug 2009 16:55:38 -0000 --_13759246-cb89-486b-92dc-210cd52a79e6_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable This won't help much=2C but... Why are you doing the OSD in the aircraft and not on the ground? To me=2C it makes more sens to have less hardware (because of the weight=2C= battery=2C etc) on board the airframe. If you want to do it from the ground=2C you could write an agent that conne= cts to the ivy bus to collect the required info and overlay it on the recei= ved video feed. -yvest From: cedric.marzer@mrsa.ch To: paparazzi-devel@nongnu.org Date: Thu=2C 27 Aug 2009 07:58:42 +0200 Subject: [Paparazzi-devel] Protocol for the downlink Hi all=2C =20 I am currently working on an OSD board that I want to hook up at my tinyV2 in parrallel with the modem. The idea is to decode the downlink telemetry going through the serial port to the modem and print data on the video downlink. =20 I have been trying to understand the telemtry data but it isn't obvious even with the code. If I understand well the code and structu= re for each message is defined in the message.h file that is dynamicaly genera= ted when compiling. What I didn't get so far is the exact structure of the telemetry data going through the serial line. Could someone help me with th= is ? =20 Thanks in advance =20 C=E9dric =20 _________________________________________________________________ More storage. Better anti-spam and antivirus protection. Hotmail makes it s= imple. http://go.microsoft.com/?linkid=3D9671357= --_13759246-cb89-486b-92dc-210cd52a79e6_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable This won't help much=2C but...

Why are you doing the OSD in the airc= raft and not on the ground?

To me=2C it makes more sens to have less= hardware (because of the weight=2C battery=2C etc) on board the airframe.<= br>
If you want to do it from the ground=2C you could write an agent tha= t connects to the ivy bus to collect the required info and overlay it on th= e received video feed.

-yvest


From: c= edric.marzer@mrsa.ch
To: paparazzi-devel@nongnu.org
Date: Thu=2C 27 A= ug 2009 07:58:42 +0200
Subject: [Paparazzi-devel] Protocol for the downl= ink

Hi all=2C

 =3B

I am currently working on an OSD board that I wan= t to hook up at my tinyV2 in parrallel with the modem.

The idea is to decode the downlink telemetry goin= g through the serial port to the modem and print data on the video downlink.

 =3B

I have been trying to understand the telemtry dat= a but it isn't obvious even with the code. If I understand well the code and structu= re for each message is defined in the message.h file that is dynamicaly genera= ted when compiling. What I didn't get so far is the exact structure of the telemetry data going through the serial line. Could someone help me with th= is ?

 =3B

Thanks in advance

 =3B

C=E9dric=

 =3B



More storage. Better anti-spam and antivirus protection. = Hotma= il makes it simple. = --_13759246-cb89-486b-92dc-210cd52a79e6_-- From MAILER-DAEMON Thu Aug 27 17:34:04 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Mgmbc-0002rz-QH for mharc-paparazzi-devel@gnu.org; Thu, 27 Aug 2009 17:34:04 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mgmbb-0002rZ-CC for paparazzi-devel@nongnu.org; Thu, 27 Aug 2009 17:34:03 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MgmbW-0002qv-3V for paparazzi-devel@nongnu.org; Thu, 27 Aug 2009 17:34:03 -0400 Received: from [199.232.76.173] (port=45222 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MgmbW-0002qj-1I for paparazzi-devel@nongnu.org; Thu, 27 Aug 2009 17:33:58 -0400 Received: from stoat.shef.ac.uk ([143.167.2.187]:40096) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_3DES_EDE_CBC_SHA1:24) (Exim 4.60) (envelope-from ) id 1MgmbV-0004iC-GG for paparazzi-devel@nongnu.org; Thu, 27 Aug 2009 17:33:57 -0400 Received: from 93-96-75-125.zone4.bethere.co.uk ([93.96.75.125] helo=[192.168.1.69]) by stoat.shef.ac.uk with esmtpsa (TLSv1:RC4-MD5:128) (Exim 4.68) (envelope-from ) id 1MgmbP-0006ji-Aw for paparazzi-devel@nongnu.org; Thu, 27 Aug 2009 22:33:51 +0100 Message-ID: <4A96FBBE.9040009@shef.ac.uk> Date: Thu, 27 Aug 2009 22:33:50 +0100 From: Gareth Roberts User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 To: paparazzi-devel@nongnu.org Subject: Re: [Paparazzi-devel] Protocol for the downlink References: <008101ca26db$6ec97430$4c5c5c90$@marzer@mrsa.ch> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-S0phie-Scan: no X-detected-operating-system: by monty-python.gnu.org: Solaris 10 (beta) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Aug 2009 21:34:03 -0000 I've written a couple of osd's, one python/gstreamer backend and one python/opencv. If you're interested, I can send you a tarball. --G From MAILER-DAEMON Fri Aug 28 03:15:32 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MgvgK-0007BF-PE for mharc-paparazzi-devel@gnu.org; Fri, 28 Aug 2009 03:15:32 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MgvgJ-0007B9-PO for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 03:15:31 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MgvgH-0007Ax-2c for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 03:15:30 -0400 Received: from [199.232.76.173] (port=36091 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MgvgG-0007Au-Uu for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 03:15:28 -0400 Received: from mx20.gnu.org ([199.232.41.8]:33005) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MgvgG-0003u1-9Z for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 03:15:28 -0400 Received: from smtp2.infomaniak.ch ([84.16.68.90]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MgvgD-0005NR-Bt for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 03:15:25 -0400 Received: from rome (217-88.77-83.cust.bluewin.ch [83.77.88.217]) (authenticated bits=0) by smtp2.infomaniak.ch (8.14.2/8.14.2) with ESMTP id n7S7FKFb019772 for ; Fri, 28 Aug 2009 09:15:21 +0200 From: =?iso-8859-1?Q?C=E9dric_Marzer?= To: References: <008101ca26db$6ec97430$4c5c5c90$@marzer@mrsa.ch> In-Reply-To: Subject: RE: [Paparazzi-devel] Protocol for the downlink Date: Fri, 28 Aug 2009 09:15:25 +0200 Message-ID: <004601ca27af$50db9b90$f292d2b0$@marzer@mrsa.ch> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0047_01CA27C0.14646B90" X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AconNzidsBFyXPr+TJqLC2JYeezr3gAdy5kw Content-Language: fr-ch X-Antivirus: Dr.Web (R) for Mail Servers on smtp2 host X-Antivirus-Code: 100000 X-Detected-Operating-System: by mx20.gnu.org: GNU/Linux 2.6? (barebone, rare!) X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6, seldom 2.4 (older, 4) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Aug 2009 07:15:32 -0000 This is a multi-part message in MIME format. ------=_NextPart_000_0047_01CA27C0.14646B90 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Yes it makes sense to have the OSD in the aircraft. It will only weighs = a few grams. The idea is for the pilot to have the choice to fly the plane like a regular RC plane or to fly it fpv (looking at the video feed) = with the help of video headset (http://www.gowiththeshark.com/). This way the pilot doesn't have to stay near the computer and will know in what phase = the autopilot is, allowing him to take control if something goes wrong. It = also opens the possibility to fly missions where no computer is required on = the field. =20 De : paparazzi-devel-bounces+cedric.marzer=3Dmrsa.ch@nongnu.org [mailto:paparazzi-devel-bounces+cedric.marzer=3Dmrsa.ch@nongnu.org] De = la part de Yves Touchette Envoy=E9 : jeudi, 27. ao=FBt 2009 18:56 =C0 : paparazzi-devel@nongnu.org Objet : RE: [Paparazzi-devel] Protocol for the downlink =20 This won't help much, but... Why are you doing the OSD in the aircraft and not on the ground? =20 ------=_NextPart_000_0047_01CA27C0.14646B90 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable ------=_NextPart_000_0047_01CA27C0.14646B90-- From MAILER-DAEMON Fri Aug 28 03:16:56 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Mgvhg-0007OS-HP for mharc-paparazzi-devel@gnu.org; Fri, 28 Aug 2009 03:16:56 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mgvhf-0007ON-4f for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 03:16:55 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MgvhZ-0007OB-To for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 03:16:54 -0400 Received: from [199.232.76.173] (port=36098 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MgvhZ-0007O8-NM for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 03:16:49 -0400 Received: from mx20.gnu.org ([199.232.41.8]:33274) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MgvhZ-00045Y-87 for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 03:16:49 -0400 Received: from mta-2.ms.rz.rwth-aachen.de ([134.130.7.73]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MgvhW-0005ZS-Sl for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 03:16:47 -0400 MIME-version: 1.0 Content-type: multipart/mixed; boundary="Boundary_(ID_x9yKloNsAEtg1AsVqNKQyA)" Received: from ironport-out-1.rz.rwth-aachen.de ([134.130.5.40]) by mta-2.ms.rz.RWTH-Aachen.de (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008)) with ESMTP id <0KP200M03S7W2K30@mta-2.ms.rz.RWTH-Aachen.de> for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 09:16:44 +0200 (CEST) X-IronPort-AV: E=Sophos; i="4.44,290,1249250400"; d="m'?scan'208"; a="23952165" Received: from relay-1.ms.rz.rwth-aachen.de (HELO relay.rwth-aachen.de) ([134.130.7.74]) by ironport-in-1.rz.rwth-aachen.de with ESMTP; Fri, 28 Aug 2009 09:16:43 +0200 Received: from [134.130.150.40] (pc40.dynamik.RWTH-Aachen.DE [134.130.150.40]) by relay.rwth-aachen.de (8.13.8+Sun/8.13.8/1) with ESMTP id n7S7Ghjh015374 for ; Fri, 28 Aug 2009 09:16:43 +0200 (CEST) Message-id: <4A978456.4010207@web.de> Date: Fri, 28 Aug 2009 09:16:38 +0200 From: Andreas Gaeb User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) To: paparazzi-devel@nongnu.org X-Detected-Operating-System: by mx20.gnu.org: Solaris 10 (beta) X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6, seldom 2.4 (older, 4) Subject: [Paparazzi-devel] Log parser for Matlab X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Aug 2009 07:16:55 -0000 This is a multi-part message in MIME format. --Boundary_(ID_x9yKloNsAEtg1AsVqNKQyA) Content-type: text/plain; charset=ISO-8859-15 Content-transfer-encoding: 7BIT Hello everybody, I've created a new Matlab log parser in case anybody is still working with that for reviewing logs. It is a bit faster than PprzLogReader_1_0, more flexible and can read any type of message present in a log file. It has been tested with Matlab 7.1 and R2009a, so it should also work with releases in between. Examples of usage are given in the file. I'll also be having a look at Roman Krashanitsa's log plotter GUI which seems to be broken with actual SVN log files. I tried to upload the script to the wiki, but this seems to accept only image files, so I'm attaching it here. Maybe someone can add it to the SVN. Regards, Andreas --Boundary_(ID_x9yKloNsAEtg1AsVqNKQyA) Content-type: text/plain; name=log2struct.m Content-transfer-encoding: 7BIT Content-disposition: inline; filename=log2struct.m function s = log2struct(logfilename) % parse a PPRZ log file %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% % function s = log2struct(logfilename) % Parses a log data file from the Paparazzi ground station into a % Matlab variable. The log is sorted by aircraft ID and message ID. % Parsing the log definition file (xx.log) is not required. % % Argument % The name of the log data file to be parsed. % May be omitted, in which case a file open dialog is used. % % Returns % A struct of dimension 1 x nAircraft % For each type of message received there is a substruct with the fields % timestamp and contents as arrays over time. The columns of the contents % array correspond to the message's data fields as defined in messages.xml. % % Example % >> % 3D plot of the trajectory of aircraft #1 % >> s = log2struct('09_08_26__14_18_29.data'); % >> plot3(s(1).GPS.content(:,2), s(1).GPS.content(:,3),s(1).GPS.content(:,5)) % >> % what did the servos do? % >> plot (s(1).ACTUATORS.timestamp, s(1).ACTUATORS.content) % % Known Bugs % The method fails when the number of data elements for one message type % changes during the log file, as may happen when the configuration file is % changed in between or with arrays of variable size. % %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% % % Author: Andreas Gaeb % Created: 27-Aug-2009 % $Id$ % % Copyright (C) 2009 Andreas Gaeb % % This file is part of paparazzi. % % paparazzi is free software; you can redistribute it and/or modify % it under the terms of the GNU General Public License as published by % the Free Software Foundation; either version 2, or (at your option) % any later version. % % paparazzi is distributed in the hope that it will be useful, % but WITHOUT ANY WARRANTY; without even the implied warranty of % MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the % GNU General Public License for more details. % % You should have received a copy of the GNU General Public License % along with paparazzi; see the file COPYING. If not, write to % the Free Software Foundation, 59 Temple Place - Suite 330, % Boston, MA 02111-1307, USA. % %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% persistent log2struct_old_working_dir % no arguments? open dialog if nargin < 1 [filename, pathname] = uigetfile(... {'*.data', 'Paparazzi log data files (*.data)'}, ... 'Open data file', ... log2struct_old_working_dir); if ~filename, return, end logfilename = fullfile(pathname, filename); log2struct_old_working_dir = pathname; % display the filename for copy/paste disp (['parsing ' logfilename '...']); end fid = fopen(logfilename); if fid == -1 error('File %s not found', logfilename); end try % read everything as timestamp, A/C ID, msg name and msg contents C = textscan(fid, '%f %u %s %[^\n]'); if isempty(C{1}) error ('File %s does not seem to be a Paparazzi log data file.', logfilename); end timestamp = C{1}; aircraftID = C{2}; msgName = C{3}; msgContent = C{4}; % find s which messages have been sent uniqueMsgs = unique(msgName); nMsg = size(uniqueMsgs,1); % find s which aircraft sent something uniqueAC = unique(aircraftID); nAC = size(uniqueAC,1); % distribute the messages to their sending aircraft for iAC = nAC:-1:1 % counting backwards eliminates preallocation % the ID of ith aircraft acID = uniqueAC(iAC); s(iAC).AIRCRAFT_ID = acID; % the indices of all messages send by ith aircraft allMsgsFromThisAircraft = (aircraftID == uniqueAC(iAC)); timestampFromThisAircraft = timestamp(allMsgsFromThisAircraft); msgNameFromThisAircraft = msgName(allMsgsFromThisAircraft); msgContentFromThisAircraft = msgContent(allMsgsFromThisAircraft); % for each message name for iMsg = 1:nMsg theMsgName = uniqueMsgs{iMsg}; % when was this special message sent by the ith aircraft? thisMsgFromThisAircraft = strmatch(... theMsgName, msgNameFromThisAircraft, 'exact'); % record with timestamp and contents s(iAC).(theMsgName).timestamp = ... timestampFromThisAircraft(thisMsgFromThisAircraft); [s(iAC).(theMsgName).content, status] = str2num(char(... msgContentFromThisAircraft(thisMsgFromThisAircraft))); %#ok if ~status && ~strcmp(theMsgName, 'PONG') warning('Paparazzi:log2struct:EmptyContent', ... 'Could not read contents of %s message from aircraft #%i', ... theMsgName, acID); continue; end end end fclose (fid); catch theError fclose(fid); rethrow(theError); end --Boundary_(ID_x9yKloNsAEtg1AsVqNKQyA)-- From MAILER-DAEMON Fri Aug 28 03:55:01 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MgwIX-0006Nu-7J for mharc-paparazzi-devel@gnu.org; Fri, 28 Aug 2009 03:55:01 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MgwIV-0006No-8M for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 03:54:59 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MgwIP-0006Na-Rc for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 03:54:57 -0400 Received: from [199.232.76.173] (port=49355 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MgwIP-0006NX-Mh for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 03:54:53 -0400 Received: from imss-1.enac.fr ([195.220.159.36]:33664) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MgwIP-0000eB-8J for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 03:54:53 -0400 Received: from mauve.recherche.enac.fr (imss-1.imss.interne.enac [127.0.0.1]) by imss-1.enac.fr (Postfix) with ESMTP id 81A1E18B3A4 for ; Fri, 28 Aug 2009 09:54:38 +0200 (CEST) Received: from [10.31.1.82] (sepia.recherche.enac.fr [10.31.1.82])by mauve.recherche.enac.fr (Postfix) with ESMTP id 6D0492FA822for ; Fri, 28 Aug 2009 09:54:38 +0200 (CEST) Message-ID: <4A978D3E.2020803@free.fr> Date: Fri, 28 Aug 2009 09:54:38 +0200 From: Pascal Brisset User-Agent: Mozilla-Thunderbird 2.0.0.22 (X11/20090706) MIME-Version: 1.0 To: paparazzi-devel@nongnu.org Subject: Re: [Paparazzi-devel] Odd or even References: <263445.98393.qm@web51507.mail.re2.yahoo.com> In-Reply-To: <263445.98393.qm@web51507.mail.re2.yahoo.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-imss-version: 2.5 X-imss-result: Passed X-imss-scores: Clean:42.50478 C:22 M:1 S:5 R:5 X-imss-settings: Baseline:1 C:1 M:1 S:1 R:1 (0.0000 0.0000) X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.4-2.6 X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Aug 2009 07:54:59 -0000 Hi Todd, the % operator has been added to the C expression parser (sw/tools/fp_lexer.mll and sw/tools/fp_parser.mly) --Pascal Todd Sandercock wrote: > Hi is there any quick way to work out if a number is odd or even in a > flight plan?? > my idea was "var % 2" but remainder is not supported > Anyone got any ideas? > > Thanks > Todd > > ------------------------------------------------------------------------ > Find local businesses and services in your area with Yahoo!7 Local. > Get started > <%20http://au.rd.yahoo.com/search/local/mailtagline/*http://local.yahoo.com.au>. > > ------------------------------------------------------------------------ > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > From MAILER-DAEMON Fri Aug 28 04:18:19 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Mgwf4-0000cn-Rq for mharc-paparazzi-devel@gnu.org; Fri, 28 Aug 2009 04:18:18 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mgwf3-0000cQ-0o for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 04:18:17 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mgwey-0000c4-B8 for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 04:18:16 -0400 Received: from [199.232.76.173] (port=51440 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mgwey-0000c1-8C for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 04:18:12 -0400 Received: from stoat.shef.ac.uk ([143.167.2.187]:43347) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_3DES_EDE_CBC_SHA1:24) (Exim 4.60) (envelope-from ) id 1Mgwex-0003yI-CV for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 04:18:11 -0400 Received: from 93-96-75-125.zone4.bethere.co.uk ([93.96.75.125] helo=[192.168.1.69]) by stoat.shef.ac.uk with esmtpsa (TLSv1:RC4-MD5:128) (Exim 4.68) (envelope-from ) id 1Mgwev-0002wr-AJ for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 09:18:09 +0100 Message-ID: <4A9792C0.9050906@shef.ac.uk> Date: Fri, 28 Aug 2009 09:18:08 +0100 From: Gareth Roberts User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 To: paparazzi-devel@nongnu.org Subject: Re: [Paparazzi-devel] Protocol for the downlink References: <008101ca26db$6ec97430$4c5c5c90$@marzer@mrsa.ch> <004601ca27af$50db9b90$f292d2b0$@marzer@mrsa.ch> In-Reply-To: <004601ca27af$50db9b90$f292d2b0$@marzer@mrsa.ch> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-S0phie-Scan: no X-detected-operating-system: by monty-python.gnu.org: Solaris 10 (beta) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Aug 2009 08:18:17 -0000 We used to do a lot of FPV flying - you still need a battery, the receiver, aerial and if you want to record you need something like an Archos anyway. The video link is going to go way before the datalink anyway if your setup is anything like ours :). What we do now is mirror the screen to the s-video port of the laptop and then plug video-goggles in - maybe this would be better for you? This way you get all the recording stuff, and others can also watch on the laptop screen. If you do still decide to go the aircraft route though, good luck! --G Cédric Marzer wrote: > > Yes it makes sense to have the OSD in the aircraft. It will only > weighs a few grams. The idea is for the pilot to have the choice to > fly the plane like a regular RC plane or to fly it fpv (looking at the > video feed) with the help of video headset > (http://www.gowiththeshark.com/). This way the pilot doesn't have to > stay near the computer and will know in what phase the autopilot is, > allowing him to take control if something goes wrong. It also opens > the possibility to fly missions where no computer is required on the > field. > > > > *De :* paparazzi-devel-bounces+cedric.marzer=mrsa.ch@nongnu.org > [mailto:paparazzi-devel-bounces+cedric.marzer=mrsa.ch@nongnu.org] *De > la part de* Yves Touchette > *Envoyé :* jeudi, 27. août 2009 18:56 > *À :* paparazzi-devel@nongnu.org > *Objet :* RE: [Paparazzi-devel] Protocol for the downlink > > > > This won't help much, but... > > Why are you doing the OSD in the aircraft and not on the ground? > > > > > ------------------------------------------------------------------------ > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > From MAILER-DAEMON Fri Aug 28 04:30:45 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Mgwr7-0001FF-J4 for mharc-paparazzi-devel@gnu.org; Fri, 28 Aug 2009 04:30:45 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mgwr5-0001Du-Gx for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 04:30:43 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mgwr0-0001Ad-E0 for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 04:30:42 -0400 Received: from [199.232.76.173] (port=47491 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mgwr0-0001AO-4B for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 04:30:38 -0400 Received: from web51508.mail.re2.yahoo.com ([206.190.38.200]:46532) by monty-python.gnu.org with smtp (Exim 4.60) (envelope-from ) id 1Mgwqz-0005pD-Pe for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 04:30:37 -0400 Received: (qmail 66500 invoked by uid 60001); 28 Aug 2009 08:30:37 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com.au; s=s1024; t=1251448237; bh=HD+4IwsDjN2w1n3zMei+J54WIyCuB1R9Dy11cF6ocCg=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=lYDIcVhhGyK7he+EErRL7H2AkEZ/pOcbD7JBho0WIXnAlQ9AEAqfJuUduEoKD3/DAWw87Ltvk0VgjH7L6RuGOyDEAOqJEYC5ZQc48kzIJEoSoG8alZyP3Ml/28wURfxTbMEugYWXHvE+uLFwq7PlJpstsTp1XQmhsf3Ws1BWw0s= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com.au; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=5aRobbDTZPgXYTF60BrsB52UCgX32LiBhiiHZ/kTY6GUjkkhR73ehr4YuiQCp8K2rifK6bbzWh+XgOnCDPC2ztW9Xgi0+zq3qDGzmoKbnNA4YsAIl9YHBljbEwzW+HspkI0A5LS48eZeYVk0Xt9ZzGjV+/3EL/E1akclwRy4iOE=; Message-ID: <106788.64989.qm@web51508.mail.re2.yahoo.com> X-YMail-OSG: 9PmLDCwVM1ncYbkO13gRescOnjBSslzop7RHug99pK.bJ4dRQZKrGzfGu5wXJkrJe8FXBx4L_5xz0yPubhY5bju88gIkEQH9bmYG3WASgpqosEFmjm5b_gfUrOUGv2X9PMNwopH5KEBco0_UzGk1PWBDgL6R5AmeSyl9i9yUHglmY8QN52_hCUF7I2uxdtrjpa7OA7Ui6IzS3mf5OZHjOi91d6YNbOEYUldA75VGx1sG55f9wwGWw1FZKKrV3X2rPnkXR7JNrSqlb0d2tblk2DUdwwFGHsYN_DjnyPKntu2HYlpmxvUkYxrjoAMEgAqr6AJBrxQelzCVSGOy3oDfrDrVW1UhWNa6qe0- Received: from [121.45.214.22] by web51508.mail.re2.yahoo.com via HTTP; Fri, 28 Aug 2009 01:30:36 PDT X-Mailer: YahooMailRC/1358.27 YahooMailWebService/0.7.338.2 References: <263445.98393.qm@web51507.mail.re2.yahoo.com> <4A978D3E.2020803@free.fr> Date: Fri, 28 Aug 2009 01:30:36 -0700 (PDT) From: Todd Sandercock Subject: Re: [Paparazzi-devel] Odd or even To: paparazzi-devel@nongnu.org In-Reply-To: <4A978D3E.2020803@free.fr> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-368103857-1251448236=:64989" X-detected-operating-system: by monty-python.gnu.org: FreeBSD 6.x (1) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Aug 2009 08:30:43 -0000 --0-368103857-1251448236=:64989 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Thanks again Pascal.=0A=0AWorks a treat=0A=0ATodd=0A=0A=0A=0A______________= __________________=0AFrom: Pascal Brisset =0ATo: pa= parazzi-devel@nongnu.org=0ASent: Friday, 28 August, 2009 5:24:38 PM=0ASubje= ct: Re: [Paparazzi-devel] Odd or even=0A=0AHi Todd,=0A=0Athe % operator has= been added to the C expression parser (sw/tools/fp_lexer.mll and sw/tools/= fp_parser.mly)=0A=0A--Pascal=0A=0ATodd Sandercock wrote:=0A> Hi is there an= y quick way to work out if a number is odd or even in a flight plan??=0A> m= y idea was "var % 2" but remainder is not supported=0A> Anyone got any idea= s?=0A> =0A> Thanks=0A> Todd=0A> =0A> --------------------------------------= ----------------------------------=0A> Find local businesses and services i= n your area with Yahoo!7 Local. Get started <%20http://au.rd.yahoo.com/sear= ch/local/mailtagline/*http://local.yahoo.com.au>. =0A> --------------------= ----------------------------------------------------=0A> =0A> _____________= __________________________________=0A> Paparazzi-devel mailing list=0A> Pap= arazzi-devel@nongnu.org=0A> http://lists.nongnu.org/mailman/listinfo/papara= zzi-devel=0A> =0A=0A=0A=0A_______________________________________________= =0APaparazzi-devel mailing list=0APaparazzi-devel@nongnu.org=0Ahttp://lists= .nongnu.org/mailman/listinfo/paparazzi-devel=0A=0A=0A=0A _____________= _____________________________________________________________________=0AFin= d local businesses and services in your area with Yahoo!7 Local.=0AGet star= ted: http://local.yahoo.com.au --0-368103857-1251448236=:64989 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Thanks again Pascal.

Works a treat
=

Todd


<= b>From: Pascal Brisset <pa= scal.brisset@free.fr>
To: paparazzi-devel@nongnu.org
S= ent: Friday, 28 August, 2009 5:24:38 PM
Subject: Re: [Paparazzi-devel] Odd or even
<= /font>
Hi Todd,

the % operator has been added to the C expression= parser (sw/tools/fp_lexer.mll and sw/tools/fp_parser.mly)

--Pascal<= br>
Todd Sandercock wrote:
> Hi is there any quick way to work out if a numbe= r is odd or even in a flight plan??
> my idea was "var % 2" but remai= nder is not supported
> Anyone got any ideas?
>
> Thanks=
> Todd
>
> --------------------------------------------= ----------------------------
> Find local businesses and services in = your area with Yahoo!7 Local. Get started <%20
http://au.rd.yahoo.com/search/local/mailtagline/*http://local.yahoo.com= .au>.
> -----------------------------------------------------= -------------------
>
> ______________________________________= _________
> Paparazzi-devel mailing list
> Pap= arazzi-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel



______________________________________________= _
Paparazzi-devel mailing list
Paparazzi-devel@nongn= u.org
http://lists.nongnu.org/mailman/listinfo/paparazzi= -devel

=0A= =0A=0A=0A
=0AFind local businesses and services in your a= rea with Yahoo!7 Local. Get started. --0-368103857-1251448236=:64989-- From MAILER-DAEMON Fri Aug 28 04:43:43 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Mgx3f-0003h1-Hv for mharc-paparazzi-devel@gnu.org; Fri, 28 Aug 2009 04:43:43 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mgx3e-0003fe-3N for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 04:43:42 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mgx3b-0003eA-EC for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 04:43:40 -0400 Received: from [199.232.76.173] (port=33853 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mgx3b-0003e2-AB for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 04:43:39 -0400 Received: from smtp1.infomaniak.ch ([84.16.68.89]:36350) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Mgx3a-0000jq-HT for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 04:43:38 -0400 Received: from rome (217-88.77-83.cust.bluewin.ch [83.77.88.217]) (authenticated bits=0) by smtp1.infomaniak.ch (8.14.2/8.14.2) with ESMTP id n7S8hajL018143 for ; Fri, 28 Aug 2009 10:43:36 +0200 From: =?iso-8859-1?Q?C=E9dric_Marzer?= To: References: <008101ca26db$6ec97430$4c5c5c90$@marzer@mrsa.ch> <004601ca27af$50db9b90$f292d2b0$@marzer@mrsa.ch> <4A9792C0.9050906@shef.ac.uk> In-Reply-To: <4A9792C0.9050906@shef.ac.uk> Subject: RE: [Paparazzi-devel] Protocol for the downlink Date: Fri, 28 Aug 2009 10:43:41 +0200 Message-ID: <006301ca27bb$a57b76a0$f07263e0$@marzer@mrsa.ch> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AconuBv1ko6zzS0iT6avBIqZGSt1/gAAaIPQ Content-Language: fr-ch X-Antivirus: Dr.Web (R) for Mail Servers on smtp1 host X-Antivirus-Code: 100000 X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6? (barebone, rare!) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Aug 2009 08:43:42 -0000 For long distance flight we have tested a high gain motorised antenna = and a 500mW video transmitter. We have tested it (without actual flying for = legal and security reason) at 45 km without problem. But for security reason, we tend to do more short distance flights (in = the volume where you would fly with a regular RC plane) and in that case we = can use the fat shark headset that is connected to the futaba tx : that = means that you don't need any battery, receiver or extra aerial. The OSD has two goals : I want to use it to do weather surveys like = Martin does : at the peak of the survey the airplane is too high and too small = to assure that you could fly it RC. The second goal is to help my friend Anthony which is a very productive = fpv pionneer (he was one of the first to developp OSD, headtrackers, = motorised antenna and such) to study a way to make fpv safer by adding some kind = of autopilot that would stabilize the plane and bring it back. The problem = is more to develop the man-machine interface and the procedure to keep it simple and cheap. All the hardware already exist. We have built so far graphical and not graphical OSD with several microcontrollers : pic16, = pic32 and LPC 2148. So it is just a question of choosing what info is relevant = to put on the screen and interface it with the paparazzi autopilot. I'll keep you informed and hope the make both the code and the hardware public. -----Message d'origine----- De=A0: paparazzi-devel-bounces+cedric.marzer=3Dmrsa.ch@nongnu.org [mailto:paparazzi-devel-bounces+cedric.marzer=3Dmrsa.ch@nongnu.org] De = la part de Gareth Roberts Envoy=E9=A0: vendredi, 28. ao=FBt 2009 10:18 =C0=A0: paparazzi-devel@nongnu.org Objet=A0: Re: [Paparazzi-devel] Protocol for the downlink We used to do a lot of FPV flying - you still need a battery, the=20 receiver, aerial and if you want to record you need something like an=20 Archos anyway.=20 The video link is going to go way before the datalink anyway if your=20 setup is anything like ours :). What we do now is mirror the screen to=20 the s-video port of the laptop and then plug video-goggles in - maybe=20 this would be better for you? This way you get all the recording stuff, = and others can also watch on the laptop screen. If you do still decide to go the aircraft route though, good luck! --G From MAILER-DAEMON Fri Aug 28 05:12:23 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MgxVP-0000ct-2p for mharc-paparazzi-devel@gnu.org; Fri, 28 Aug 2009 05:12:23 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MgxVM-0000bK-Vk for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 05:12:21 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MgxVH-0000UP-FD for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 05:12:20 -0400 Received: from [199.232.76.173] (port=47244 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MgxVH-0000U3-Ad for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 05:12:15 -0400 Received: from stoat.shef.ac.uk ([143.167.2.187]:54957) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_3DES_EDE_CBC_SHA1:24) (Exim 4.60) (envelope-from ) id 1MgxVG-0005Od-Ub for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 05:12:15 -0400 Received: from dcs02962.dcs.shef.ac.uk ([143.167.10.18]) by stoat.shef.ac.uk with esmtpsa (TLSv1:RC4-MD5:128) (Exim 4.68) (envelope-from ) id 1MgxVF-0005a9-B5 for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 10:12:13 +0100 Subject: RE: [Paparazzi-devel] Protocol for the downlink From: Gareth R To: paparazzi-devel@nongnu.org In-Reply-To: <006301ca27bb$a57b76a0$f07263e0$@marzer@mrsa.ch> References: <008101ca26db$6ec97430$4c5c5c90$@marzer@mrsa.ch> <004601ca27af$50db9b90$f292d2b0$@marzer@mrsa.ch> <4A9792C0.9050906@shef.ac.uk> <006301ca27bb$a57b76a0$f07263e0$@marzer@mrsa.ch> Content-Type: text/plain Date: Fri, 28 Aug 2009 10:12:13 +0100 Message-Id: <1251450733.4602.14.camel@gareth> Mime-Version: 1.0 X-Mailer: Evolution 2.26.1 Content-Transfer-Encoding: 7bit X-S0phie-Scan: no X-detected-operating-system: by monty-python.gnu.org: Solaris 10 (beta) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Aug 2009 09:12:21 -0000 Ahh, that makes more sense! Interfacing airside should be interesting...have you considered going down the I2C/SPI route rather than tapping the serial line? Also, I'm very jealous of your 500mW video transmitter, in Europe we are limited in law to 10mW! --G From MAILER-DAEMON Fri Aug 28 05:30:49 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MgxnF-0004AL-2Z for mharc-paparazzi-devel@gnu.org; Fri, 28 Aug 2009 05:30:49 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MgxnB-00049p-Mt for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 05:30:45 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mgxn6-000496-NN for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 05:30:45 -0400 Received: from [199.232.76.173] (port=52570 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mgxn6-000493-DR for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 05:30:40 -0400 Received: from blu0-omc2-s11.blu0.hotmail.com ([65.55.111.86]:30596) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Mgxn5-00006t-Qj for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 05:30:40 -0400 Received: from BLU149-W61 ([65.55.111.71]) by blu0-omc2-s11.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 28 Aug 2009 02:30:39 -0700 Message-ID: Content-Type: multipart/mixed; boundary="_ff70126a-7e33-400d-8b95-5bf1bbff75d2_" X-Originating-IP: [134.96.163.226] From: =?big5?B?s6IgZmx5aW5nIHBpZw==?= To: Date: Fri, 28 Aug 2009 09:30:39 +0000 Importance: Normal MIME-Version: 1.0 X-OriginalArrivalTime: 28 Aug 2009 09:30:39.0036 (UTC) FILETIME=[346FC7C0:01CA27C2] X-detected-operating-system: by monty-python.gnu.org: Windows 2000 SP4, XP SP1+ Subject: [Paparazzi-devel] droping paintball X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Aug 2009 09:30:46 -0000 --_ff70126a-7e33-400d-8b95-5bf1bbff75d2_ Content-Type: multipart/alternative; boundary="_b39ed9d8-a28f-4f93-ad3d-9f3b5e4da5a4_" --_b39ed9d8-a28f-4f93-ad3d-9f3b5e4da5a4_ Content-Type: text/plain; charset="big5" Content-Transfer-Encoding: 8bit Hi guys I am using the EMAV08 flight plan to try to see how the paint ball dropping will look like, so, i added the shoot into the flight plan, but it can not compiled (however, once i remote the shoot, it works ??) I have enclosed my airfram file (note, I am still using the old version of paaprazzi) and flight plan, can someone helps? bombing.xml is the aircraft bombingtest is flight plan i modifiy from EMAV08.xml Thanks Chen _________________________________________________________________ »´ÃP¤À¨É ¡V §Q¥Î Windows Live ¬Ûï¤À¨É¬Û¤ù http://download.live.com/toolbar --_b39ed9d8-a28f-4f93-ad3d-9f3b5e4da5a4_ Content-Type: text/html; charset="big5" Content-Transfer-Encoding: 8bit Hi guys
 
  I am using the EMAV08 flight plan to try to see how the paint ball dropping will look like, so, i added the shoot into the flight plan, but it can not compiled (however, once i remote the shoot, it works ??)
 
 
  I have enclosed my airfram file (note, I am still using the old version of paaprazzi) and flight plan, can someone helps?
 
 
bombing.xml is the aircraft
bombingtest is flight plan i modifiy from EMAV08.xml
 
Thanks
 
                                                                            Chen


Áo©ú·j´M©MÂsÄýºô¸ôªº§K¶O¤u¨ã¦C ¡X Windows Live ¤u¨ã¦C --_b39ed9d8-a28f-4f93-ad3d-9f3b5e4da5a4_-- --_ff70126a-7e33-400d-8b95-5bf1bbff75d2_ Content-Type: text/xml Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="bombing.xml" PCFET0NUWVBFIGFpcmZyYW1lIFNZU1RFTSAiYWlyZnJhbWUuZHRkIj4KCgo8YWlyZnJhbWUgbmFt ZT0iYm9tYmluZyI+Cgo8IS0tIGNvbW1hbmRzIHNlY3Rpb24gLS0+CiAgPHNlcnZvcz4KICAgIDxz ZXJ2byBuYW1lPSJNT1RPUiIgbm89IjAiIG1pbj0iMTAwMCIgbmV1dHJhbD0iMTAwMCIgbWF4PSIy MDAwIi8+CiAgICA8c2Vydm8gbmFtZT0iQUlMRVJPTiIgbm89IjEiIG1pbj0iMTkwMCIgbmV1dHJh bD0iMTUwMCIgbWF4PSIxMTAwIi8+CiAgICAgPHNlcnZvIG5hbWU9IkVMRVZBVE9SIiBubz0iMiIg bWluPSIxOTAwIiBuZXV0cmFsPSIxNTAwIiBtYXg9IjExMDAiLz4KICA8c2Vydm8gbmFtZT0iSEFU Q0giICAgICAgICAgbm89IjMiIG1pbj0iMTcyNSIgbmV1dHJhbD0iMTcyNSIgbWF4PSIxMDAwIi8+ IAogIDwvc2Vydm9zPgoKICA8Y29tbWFuZHM+CiAgICA8YXhpcyBuYW1lPSJUSFJPVFRMRSIgZmFp bHNhZmVfdmFsdWU9IjAiLz4KICAgIDxheGlzIG5hbWU9IlJPTEwiIGZhaWxzYWZlX3ZhbHVlPSIw Ii8+CiAgICA8YXhpcyBuYW1lPSJQSVRDSCIgZmFpbHNhZmVfdmFsdWU9IjAiLz4KICAgIDxheGlz IG5hbWU9IkhBVENIIiAgICBmYWlsc2FmZV92YWx1ZT0iMCIvPgogICAgCiAgPC9jb21tYW5kcz4K CiAgPHJjX2NvbW1hbmRzPgogICAgPHNldCBjb21tYW5kPSJUSFJPVFRMRSIgdmFsdWU9IkBUSFJP VFRMRSIvPgogICAgPHNldCBjb21tYW5kPSJST0xMIiB2YWx1ZT0iQFJPTEwiLz4KICAgIDxzZXQg Y29tbWFuZD0iUElUQ0giIHZhbHVlPSJAUElUQ0giLz4KICAgPHNldCBjb21tYW5kPSJIQVRDSCIg ICAgdmFsdWU9IkBHQUlOMSIvPgogIDwvcmNfY29tbWFuZHM+CgogIDwhLS0tPHNlY3Rpb24gbmFt ZT0iTUlYRVIiPgogICAgPGRlZmluZSBuYW1lPSJBSUxFVk9OX0FJTEVST05fUkFURSIgdmFsdWU9 IjAuNDUiLz4KICAgIDxkZWZpbmUgbmFtZT0iQUlMRVZPTl9FTEVWQVRPUl9SQVRFIiB2YWx1ZT0i MC44Ii8+CiAgPC9zZWN0aW9uPiAtLS0+CgogIDxjb21tYW5kX2xhd3M+CiAgICA8c2V0IHNlcnZv PSJBSUxFUk9OIiB2YWx1ZT0iQFJPTEwiLz4KICAgIDxzZXQgc2Vydm89IkVMRVZBVE9SIiB2YWx1 ZT0iQFBJVENIIi8+ICAKICAgIDxzZXQgc2Vydm89Ik1PVE9SIiB2YWx1ZT0iQFRIUk9UVExFIi8+ CiAgIDxzZXQgc2Vydm89IkhBVENIIiAgICAgICAgIHZhbHVlPSJASEFUQ0giLz4KICA8L2NvbW1h bmRfbGF3cz4KCiAgPHNlY3Rpb24gbmFtZT0iQVVUTzEiIHByZWZpeD0iQVVUTzFfIj4KICAgIDxk ZWZpbmUgbmFtZT0iTUFYX1JPTEwiIHZhbHVlPSIwLjgiLz4KICAgIDxkZWZpbmUgbmFtZT0iTUFY X1BJVENIIiB2YWx1ZT0iMC44Ii8+CiAgPC9zZWN0aW9uPgoKIDxzZWN0aW9uIG5hbWU9ImFkYyIg cHJlZml4PSJBRENfQ0hBTk5FTF8iPgogICAgPGRlZmluZSBuYW1lPSJJUjEiIHZhbHVlPSJBRENf MSIvPgogICAgPGRlZmluZSBuYW1lPSJJUjIiIHZhbHVlPSJBRENfMiIvPgogICAgPGRlZmluZSBu YW1lPSJJUl9UT1AiIHZhbHVlPSJBRENfMCIvPgogIDwvc2VjdGlvbj4KCiAgPHNlY3Rpb24gbmFt ZT0iSU5GUkFSRUQiIHByZWZpeD0iSVJfIj4KICAgIDxkZWZpbmUgbmFtZT0iQURDX0lSMV9ORVVU UkFMIiB2YWx1ZT0iNTE3Ii8+CiAgICA8ZGVmaW5lIG5hbWU9IkFEQ19JUjJfTkVVVFJBTCIgdmFs dWU9IjUxNiIvPgogICAgPGRlZmluZSBuYW1lPSJBRENfVE9QX05FVVRSQUwiIHZhbHVlPSI1MTYi Lz4KCiAgICA8ZGVmaW5lIG5hbWU9IkxBVEVSQUxfQ09SUkVDVElPTiIgdmFsdWU9IjAuMzQwMDAw MDAzNTc2Ii8+CiAgICA8ZGVmaW5lIG5hbWU9IkxPTkdJVFVESU5BTF9DT1JSRUNUSU9OIiB2YWx1 ZT0iMS4iLz4KICAgIDxkZWZpbmUgbmFtZT0iVkVSVElDQUxfQ09SUkVDVElPTiIgdmFsdWU9IjEu NSIvPgoKICAgIDxkZWZpbmUgbmFtZT0iSE9SSVpfU0VOU09SX1RJTFRFRCIgdmFsdWU9IjEiLz4K ICAgIDxkZWZpbmUgbmFtZT0iSVIxX1NJR04iIHZhbHVlPSIxIi8+CiAgICA8ZGVmaW5lIG5hbWU9 IklSMl9TSUdOIiB2YWx1ZT0iMSIvPgogICAgPGRlZmluZSBuYW1lPSJUT1BfU0lHTiIgdmFsdWU9 IjEiLz4KCiAgICA8ZGVmaW5lIG5hbWU9IlJPTExfTkVVVFJBTF9ERUZBVUxUIiB2YWx1ZT0iLTIu MjkxODMxMjU0OTYiIHVuaXQ9ImRlZyIvPgogICAgPGRlZmluZSBuYW1lPSJQSVRDSF9ORVVUUkFM X0RFRkFVTFQiIHZhbHVlPSIxMi4wODk0MDk4MjgyIiB1bml0PSJkZWciLz4KCiAgICA8ZGVmaW5l IG5hbWU9IkNPUlJFQ1RJT05fVVAiIHZhbHVlPSIxLiIvPgogICAgPGRlZmluZSBuYW1lPSJDT1JS RUNUSU9OX0RPV04iIHZhbHVlPSIxLiIvPgogICAgPGRlZmluZSBuYW1lPSJDT1JSRUNUSU9OX0xF RlQiIHZhbHVlPSIxLiIvPgogICAgPGRlZmluZSBuYW1lPSJDT1JSRUNUSU9OX1JJR0hUIiB2YWx1 ZT0iMS4iLz4KICA8L3NlY3Rpb24+CgoKCiAgPHNlY3Rpb24gbmFtZT0iQkFUIj4KICAgIDxkZWZp bmUgbmFtZT0iTUlMTElBTVBfUEVSX1BFUkNFTlQiIHZhbHVlPSIwLjg2Ii8+CiAgICA8ZGVmaW5l IG5hbWU9IlZPTFRBR0VfQURDX0EiIHZhbHVlPSIwLjAyNDczMTE4MjgiLz4KICAgIDxkZWZpbmUg bmFtZT0iVk9MVEFHRV9BRENfQiIgdmFsdWU9Ii0wLjE3MzYyNiIvPgogICAgPGRlZmluZSBuYW1l PSJWb2x0YWdlT2ZBZGMoYWRjKSIgdmFsdWU9IihWT0xUQUdFX0FEQ19BICogYWRjICsgVk9MVEFH RV9BRENfQikiLz4KICAgIDxkZWZpbmUgbmFtZT0iQ0FUQVNUUk9QSElDX0JBVF9MRVZFTCIgdmFs dWU9IjkuNCIgdW5pdD0iViIvPgogICAgPGRlZmluZSBuYW1lPSJNQVhfQkFUX0xFVkVMIiB2YWx1 ZT0iMTIuNSIgdW5pdD0iViIvPgogIDwvc2VjdGlvbj4KIAogICAgPHNlY3Rpb24gbmFtZT0iTUlT QyI+CiAgICA8ZGVmaW5lIG5hbWU9Ik5PTUlOQUxfQUlSU1BFRUQiIHZhbHVlPSI3LiIgdW5pdD0i bS9zIi8+CiAgICA8ZGVmaW5lIG5hbWU9IkNBUlJPVCIgdmFsdWU9IjUuIiB1bml0PSJzIi8+CiAg ICA8ZGVmaW5lIG5hbWU9IktJTExfTU9ERV9ESVNUQU5DRSIgdmFsdWU9IigxLjUqTUFYX0RJU1Rf RlJPTV9IT01FKSIvPgogICAgPGRlZmluZSBuYW1lPSJDT05UUk9MX1JBVEUiIHZhbHVlPSI2MCIg dW5pdD0iSHoiLz4KPGRlZmluZSBuYW1lPSJYQkVFX0lOSVQiIHZhbHVlPSImcXVvdDtBVFBMMlxy QVRSTjFcckFUV1JcciZxdW90OyIvPgo8IS0tICAgIDxkZWZpbmUgbmFtZT0iTk9fWEJFRV9BUElf SU5JVCIgdmFsdWU9IlRSVUUiLz4gLS0+CiAgICA8ZGVmaW5lIG5hbWU9IkFMVF9LQUxNQU5fRU5B QkxFRCIgdmFsdWU9IkZBTFNFIi8+CgogICAgPGRlZmluZSBuYW1lPSJUUklHR0VSX0RFTEFZIiB2 YWx1ZT0iMS4iLz4KICAgIDxkZWZpbmUgbmFtZT0iREVGQVVMVF9DSVJDTEVfUkFESVVTIiB2YWx1 ZT0iLTMwLiIvPgogICAgPGRlZmluZSBuYW1lPSJNSU5fQ0lSQ0xFX1JBRElVUyIgdmFsdWU9Ii0y MC4iLz4KICA8L3NlY3Rpb24+CiAKICA8c2VjdGlvbiBuYW1lPSJWRVJUSUNBTCBDT05UUk9MIiBw cmVmaXg9IlZfQ1RMXyI+CgogICAgPGRlZmluZSBuYW1lPSJQT1dFUl9DVExfQkFUX05PTUlOQUwi IHZhbHVlPSIxMS4xIiB1bml0PSJ2b2x0Ii8+CiAgICA8IS0tIG91dGVyIGxvb3AgcHJvcG9ydGlv bmFsIGdhaW4gLS0+CiAgICA8ZGVmaW5lIG5hbWU9IkFMVElUVURFX1BHQUlOIiB2YWx1ZT0iLTAu MDI0Ii8+CiAgICA8IS0tIG91dGVyIGxvb3Agc2F0dXJhdGlvbiAtLT4KICAgIDxkZWZpbmUgbmFt ZT0iQUxUSVRVREVfTUFYX0NMSU1CIiB2YWx1ZT0iMi4iLz4KCiAgICA8IS0tIGF1dG8gdGhyb3R0 bGUgaW5uZXIgbG9vcCAtLT4KICAgIDxkZWZpbmUgbmFtZT0iQVVUT19USFJPVFRMRV9OT01JTkFM X0NSVUlTRV9USFJPVFRMRSIgdmFsdWU9IjAuNTUiLz4KICAgIDxkZWZpbmUgbmFtZT0iQVVUT19U SFJPVFRMRV9NSU5fQ1JVSVNFX1RIUk9UVExFIiB2YWx1ZT0iMC40NCIvPgogICAgPGRlZmluZSBu YW1lPSJBVVRPX1RIUk9UVExFX01BWF9DUlVJU0VfVEhST1RUTEUiIHZhbHVlPSIwLjcwIi8+CiAg ICA8ZGVmaW5lIG5hbWU9IkFVVE9fVEhST1RUTEVfTE9JVEVSX1RSSU0iIHZhbHVlPSI1MCIvPgog ICAgPGRlZmluZSBuYW1lPSJBVVRPX1RIUk9UVExFX0RBU0hfVFJJTSIgdmFsdWU9Ii02MCIvPgog ICAgPGRlZmluZSBuYW1lPSJBVVRPX1RIUk9UVExFX0NMSU1CX1RIUk9UVExFX0lOQ1JFTUVOVCIg dmFsdWU9IjAuMiIgdW5pdD0iJS8obS9zKSIvPgogICAgPGRlZmluZSBuYW1lPSJBVVRPX1RIUk9U VExFX1BHQUlOIiB2YWx1ZT0iLTAuMDEyIi8+CiAgICA8ZGVmaW5lIG5hbWU9IkFVVE9fVEhST1RU TEVfSUdBSU4iIHZhbHVlPSIwLjAxIi8+CiAgICA8ZGVmaW5lIG5hbWU9IkFVVE9fVEhST1RUTEVf UElUQ0hfT0ZfVlpfUEdBSU4iIHZhbHVlPSIwLjA1Ii8+CgogICAgPCEtLSBhdXRvIHBpdGNoIGlu bmVyIGxvb3AgLS0+CiAgICA8ZGVmaW5lIG5hbWU9IkFVVE9fUElUQ0hfUEdBSU4iIHZhbHVlPSIt MC4wMyIvPgogICAgPGRlZmluZSBuYW1lPSJBVVRPX1BJVENIX0lHQUlOIiB2YWx1ZT0iMC4wIi8+ CiAgICA8ZGVmaW5lIG5hbWU9IkFVVE9fUElUQ0hfTUFYX1BJVENIIiB2YWx1ZT0iMC4zNSIvPgog ICAgPGRlZmluZSBuYW1lPSJBVVRPX1BJVENIX01JTl9QSVRDSCIgdmFsdWU9Ii0wLjM1Ii8+Cgog ICA8ZGVmaW5lIG5hbWU9IlRIUk9UVExFX1NMRVciIHZhbHVlPSIwLjEiLz4KCiAgPC9zZWN0aW9u PgoKICA8c2VjdGlvbiBuYW1lPSJIT1JJWk9OVEFMIENPTlRST0wiIHByZWZpeD0iSF9DVExfIj4K ICAgIDxkZWZpbmUgbmFtZT0iQ09VUlNFX1BHQUlOIiB2YWx1ZT0iLTAuNSIvPgogICAgPGRlZmlu ZSBuYW1lPSJST0xMX01BWF9TRVRQT0lOVCIgdmFsdWU9IjAuNSIgdW5pdD0icmFkaWFucyIvPgog ICAgPGRlZmluZSBuYW1lPSJQSVRDSF9NQVhfU0VUUE9JTlQiIHZhbHVlPSIwLjUiIHVuaXQ9InJh ZGlhbnMiLz4KICAgIDxkZWZpbmUgbmFtZT0iUElUQ0hfTUlOX1NFVFBPSU5UIiB2YWx1ZT0iLTAu NSIgdW5pdD0icmFkaWFucyIvPgogICAgPGRlZmluZSBuYW1lPSJST0xMX1BHQUlOIiB2YWx1ZT0i NjAwMC4iLz4KCiAgICA8ZGVmaW5lIG5hbWU9IlBJVENIX1BHQUlOIiB2YWx1ZT0iLTU1MDAuIi8+ CiAgICA8ZGVmaW5lIG5hbWU9IlBJVENIX0RHQUlOIiB2YWx1ZT0iMCIvPiAgPCEtLTAuNCAtLT4K CiAgICA8ZGVmaW5lIG5hbWU9IkVMRVZBVE9SX09GX1JPTEwiIHZhbHVlPSIxMjAwIi8+CgogICAg PCEtLWRlZmluZSBuYW1lPSJST0xMX0FUVElUVURFX0dBSU4iIHZhbHVlPSItNzUwMCIvPgogICAg PGRlZmluZSBuYW1lPSJST0xMX1JBVEVfR0FJTiIgdmFsdWU9Ii0xNTAwIi8tLT4KCiAgPC9zZWN0 aW9uPgoKICA8c2VjdGlvbiBuYW1lPSJOQVYiPgogICAgPGRlZmluZSBuYW1lPSJOQVZfUElUQ0gi IHZhbHVlPSIwLiIvPgogICAgPGRlZmluZSBuYW1lPSJOQVZfR0xJREVfUElUQ0hfVFJJTSIgdmFs dWU9IjAiLz4KICA8L3NlY3Rpb24+CgogIDxzZWN0aW9uIG5hbWU9IkFHR1JFU1NJVkUiIHByZWZp eD0iQUdSXyI+CiAgICA8ZGVmaW5lIG5hbWU9IkJMRU5EX1NUQVJUIiB2YWx1ZT0iNTAiLz48IS0t IEFsdGl0dWRlIEVycm9yIHRvIEluaXRpYXRlIEFnZ3Jlc3NpdmUgQ2xpbWIgQ0FOTk9UIEJFIFpF Uk8hIS0tPgogICAgPGRlZmluZSBuYW1lPSJCTEVORF9FTkQiIHZhbHVlPSIxNSIvPjwhLS0gQWx0 aXR1ZGUgRXJyb3IgdG8gQmxlbmQgQWdncmVzc2l2ZSB0byBSZWd1bGFyIENsaW1iIE1vZGVzICBD QU5OT1QgQkUgWkVSTyEhLS0+CiAgICA8ZGVmaW5lIG5hbWU9IkNMSU1CX1RIUk9UVExFIiB2YWx1 ZT0iMC42Ii8+PCEtLSBHYXogZm9yIEFnZ3Jlc3NpdmUgQ2xpbWIgLS0+CiAgICA8ZGVmaW5lIG5h bWU9IkNMSU1CX1BJVENIIiB2YWx1ZT0iMC4zIi8+PCEtLSBQaXRjaCBmb3IgQWdncmVzc2l2ZSBD bGltYiAtLT4KICAgIDxkZWZpbmUgbmFtZT0iREVTQ0VOVF9USFJPVFRMRSIgdmFsdWU9IjAuMSIv PjwhLS0gR2F6IGZvciBBZ2dyZXNzaXZlIERlY2VudCAtLT4KICAgIDxkZWZpbmUgbmFtZT0iREVT Q0VOVF9QSVRDSCIgdmFsdWU9Ii0wLjI1Ii8+PCEtLSBQaXRjaCBmb3IgQWdncmVzc2l2ZSBEZWNl bnQgLS0+CiAgICA8ZGVmaW5lIG5hbWU9IkNMSU1CX05BVl9SQVRJTyIgdmFsdWU9IjAuOCIvPjwh LS0gUGVyY2VudCBOYXZpZ2F0aW9uIGZvciBBbHRpdHVkZSBFcnJvciBFcXVhbCB0byBTdGFydCBB bHRpdHVkZSAtLT4KICAgIDxkZWZpbmUgbmFtZT0iREVTQ0VOVF9OQVZfUkFUSU8iIHZhbHVlPSIx LjAiLz4KICAgIDwvc2VjdGlvbj4KCiAgPHNlY3Rpb24gbmFtZT0iRkFJTFNBRkUiIHByZWZpeD0i RkFJTFNBRkVfIj4KCTxkZWZpbmUgbmFtZT0iREVMQVlfV0lUSE9VVF9HUFMiIHZhbHVlPSIxIiB1 bml0PSJzIi8+CiAgICAJPGRlZmluZSBuYW1lPSJERUZBVUxUX1RIUk9UVExFIiB2YWx1ZT0iMC4z IiB1bml0PSIlIi8+CiAgICAJPGRlZmluZSBuYW1lPSJERUZBVUxUX1JPTEwiIHZhbHVlPSIwLjMi IHVuaXQ9InJhZCIvPgogICAgCTxkZWZpbmUgbmFtZT0iREVGQVVMVF9QSVRDSCIgdmFsdWU9IjAu NSIgdW5pdD0icmFkIi8+Cgk8ZGVmaW5lIG5hbWU9IkhPTUVfUkFESVVTIiB2YWx1ZT0iMTAwIiB1 bml0PSJtIi8+CiAgICAgIDxkZWZpbmUgbmFtZT0iVEVMRU1FVFJZX01PREVfRkJXIiB2YWx1ZT0i MSIvPgo8L3NlY3Rpb24+Cgo8c2VjdGlvbiBuYW1lPSJEQVRBTElOSyIgcHJlZml4PSJEQVRBTElO S18iPgogICAgPGRlZmluZSBuYW1lPSJERVZJQ0VfVFlQRSIgdmFsdWU9IlhCRUUiLz4KICAgIDxk ZWZpbmUgbmFtZT0iREVWSUNFX0FERFJFU1MiIHZhbHVlPSIuLi4uIi8+CiAgPC9zZWN0aW9uPgog ICAgICAgCiA8IS0tPHNlY3Rpb24gbmFtZT0iREFUQUxJTksiIHByZWZpeD0iREFUQUxJTktfIj4K ICAgIDxkZWZpbmUgbmFtZT0iREVWSUNFX1RZUEUiIHZhbHVlPSJYQkVFIi8+CiAgICA8ZGVmaW5l IG5hbWU9IkRFVklDRV9BRERSRVNTIiB2YWx1ZT0iLi4uLiIvPiAKICA8L3NlY3Rpb24+IC0tPgog CiA8c2VjdGlvbiBuYW1lPSJTSU1VIj4KICAgIDxkZWZpbmUgbmFtZT0iWUFXX1JFU1BPTlNFX0ZB Q1RPUiIgdmFsdWU9IjAuNSIvPgogPC9zZWN0aW9uPgoKIDxtYWtlZmlsZT4KCkNPTkZJRyA9IFwi dGlueV8yXzEuaFwiCgppbmNsdWRlICQoUEFQQVJBWlpJX1NSQykvY29uZi9hdXRvcGlsb3QvdGlu eS5tYWtlZmlsZQoKRkxBU0hfTU9ERT1JQVAKCmFwLkNGTEFHUyArPSAgLURGQlcgLURBUCAtRENP TkZJRz0kKENPTkZJRykgLURMRUQgLURUSU1FX0xFRD0xCmFwLnNyY3MgPSBzeXNfdGltZS5jICQo U1JDX0FSQ0gpL3N5c190aW1lX2h3LmMgJChTUkNfQVJDSCkvYXJtVklDLmMgbWFpbl9mYncuYyBt YWluX2FwLmMgbWFpbi5jCgphcC5zcmNzICs9IGNvbW1hbmRzLmMKCmFwLkNGTEFHUyArPSAtREFD VFVBVE9SUz1cInNlcnZvc180MDE3X2h3LmhcIiAtRFNFUlZPU180MDE3CmFwLnNyY3MgKz0gJChT UkNfQVJDSCkvc2Vydm9zXzQwMTdfaHcuYyBhY3R1YXRvcnMuYwoKYXAuQ0ZMQUdTICs9IC1EUkFE SU9fQ09OVFJPTCAtRFJBRElPX0NPTlRST0xfVFlQRT1SQ19GVVRBQkEKYXAuc3JjcyArPSByYWRp b19jb250cm9sLmMgJChTUkNfQVJDSCkvcHBtX2h3LmMgIAoKYXAuQ0ZMQUdTICs9IC1ERE9XTkxJ TksgLURVU0VfVUFSVDEgLURET1dOTElOS19UUkFOU1BPUlQ9WEJlZVRyYW5zcG9ydCAtRFhCRUVf VUFSVD1VYXJ0MSAtRERBVEFMSU5LPVhCRUUgLURVQVJUMV9CQVVEPUI5NjAwCmFwLnNyY3MgKz0g ZG93bmxpbmsuYyAkKFNSQ19BUkNIKS91YXJ0X2h3LmMgZGF0YWxpbmsuYyB4YmVlLmMKCiNUUkFO U1BBUkVOVAojYXAuQ0ZMQUdTICs9IC1ERE9XTkxJTksgLURVU0VfVUFSVDEgLURET1dOTElOS19U UkFOU1BPUlQ9UHByelRyYW5zcG9ydCAtRERPV05MSU5LX0ZCV19ERVZJQ0U9VWFydDEgLURET1dO TElOS19BUF9ERVZJQ0U9VWFydDEgLURQUFJaX1VBUlQ9VWFydDEgLUREQVRBTElOSz1QUFJaIC1E VUFSVDFfQkFVRD1CNTc2MDAKI2FwLnNyY3MgKz0gZG93bmxpbmsuYyAkKFNSQ19BUkNIKS91YXJ0 X2h3LmMgZGF0YWxpbmsuYyBwcHJ6X3RyYW5zcG9ydC5jCgoKYXAuQ0ZMQUdTICs9IC1ESU5URVJf TUNVCmFwLnNyY3MgKz0gaW50ZXJfbWN1LmMgCgphcC5DRkxBR1MgKz0gLURURUxFTUVUUllfTU9E RV9GQlc9MQoKYXAuQ0ZMQUdTICs9IC1EQURDIC1EVVNFX0FEQ18wIC1EVVNFX0FEQ18xIC1EVVNF X0FEQ18yIC1EVVNFX0FEQ183CmFwLnNyY3MgKz0gJChTUkNfQVJDSCkvYWRjX2h3LmMKCmFwLkNG TEFHUyArPSAtREdQUyAtRFVCWCAtRFVTRV9VQVJUMCAtREdQU19MSU5LPVVhcnQwIC1ER1BTX1VT RV9MQVRMT05HIC1EVUFSVDBfQkFVRD1CMzg0MDAKIyAtREdQU19MRUQ9MgphcC5zcmNzICs9IGdw c191YnguYyBncHMuYyBsYXRsb25nLmMKCmFwLkNGTEFHUyArPSAtRElORlJBUkVEIC1EQUxUX0tB TE1BTiAtRFdJTkRfSU5GTyAtRFdJTkRfSU5GT19SRVQKYXAuc3JjcyArPSBpbmZyYXJlZC5jIGVz dGltYXRvci5jCgphcC5DRkxBR1MgKz0gLUROQVYgLURBR1JfQ0xJTUIgLURMT0lURVJfVFJJTQph cC5zcmNzICs9IG5hdi5jIGZ3X2hfY3RsLmMgZndfdl9jdGwuYwphcC5zcmNzICs9IG5hdl9saW5l LmMgbmF2X3N1cnZleV9yZWN0YW5nbGUuYwphcC5zcmNzICs9IGJvbWIuYwoKCgojYXAuc3JjcyAr PSBodW1pZF9zaHQuYwojYXAuQ0ZMQUdTICs9IC1EVVNFX0hVTUlEX1NIVCAtRERBVF9QSU49MyAg LURTQ0tfUElOPTIKCiNhcC5zcmNzICs9IGJhcm9fc2NwLmMKI2FwLkNGTEFHUyArPSAtRFVTRV9C QVJPX1NDUAoKIyBDb25maWd1cmF0aW9uIGZvciBIYXJkd2FyZSBJbiBUaGUgTG9vcAojYXAuQ0ZM QUdTICs9IC1ESElUTCAtVUdQU19DT05GSUdVUkUgLVVVQVJUMV9CQVVEIC1EVUFSVDFfQkFVRD1C NTc2MDAKCiMgQ29uZmlnIGZvciBTSVRMIHNpbXVsYXRpb24KaW5jbHVkZSAkKFBBUEFSQVpaSV9T UkMpL2NvbmYvYXV0b3BpbG90L3NpdGwubWFrZWZpbGUKc2ltLkNGTEFHUyArPSAtRENPTkZJRz1c InRpbnkuaFwiIC1EQUdSX0NMSU1CIC1ETE9JVEVSX1RSSU0gLURBTFRfS0FMTUFOCnNpbS5zcmNz ICs9IG5hdl9saW5lLmMgbmF2X3N1cnZleV9yZWN0YW5nbGUuYwoKCiAgPC9tYWtlZmlsZT4KPC9h aXJmcmFtZT4KCg== --_ff70126a-7e33-400d-8b95-5bf1bbff75d2_ Content-Type: text/xml Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="bombingtest.xml" PCFET0NUWVBFIGZsaWdodF9wbGFuIFNZU1RFTSAiZmxpZ2h0X3BsYW4uZHRkIj4KCjxmbGlnaHRf cGxhbiBhbHQ9IjE0MCIgZ3JvdW5kX2FsdD0iNTUiIGxhdDA9IjUyLjUyMzg4NiIgbG9uMD0iMTAu NDYzNzY0IiBtYXhfZGlzdF9mcm9tX2hvbWU9IjI1MDAiIG5hbWU9ImJvbWJpbmd0ZXN0IiBxZnU9 Ii05MCIgc2VjdXJpdHlfaGVpZ2h0PSI4MSI+CiAgPGhlYWRlcj4KI2luY2x1ZGUgImRhdGFsaW5r LmgiCiNpbmNsdWRlICJuYXZfbGluZS5oIgojaW5jbHVkZSAiYm9tYi5oIgo8L2hlYWRlcj4KICA8 d2F5cG9pbnRzPgogICAgPHdheXBvaW50IG5hbWU9IkhPTUUiIHg9IjE2LjkiIHk9Ii0wLjQiLz4K ICAgIDx3YXlwb2ludCBhbHQ9IjE0MC4wIiBuYW1lPSJTVERCWSIgeD0iMzAuMiIgeT0iMTA0LjYi Lz4KICAgIDx3YXlwb2ludCBhbHQ9IjE2MC4wIiBuYW1lPSIxIiB4PSItNTcuMSIgeT0iMjI1Ljgi Lz4KICAgIDx3YXlwb2ludCBhbHQ9IjE2MC4wIiBuYW1lPSIyIiB4PSItMTE3LjEiIHk9IjIyNS44 Ii8+CiAgICA8d2F5cG9pbnQgbmFtZT0iTU9CIiB4PSIyNTkuMyIgeT0iLTM1My43Ii8+CiAgICA8 d2F5cG9pbnQgbmFtZT0iUzEiIHg9Ii0yNTAuMyIgeT0iLTI3OS45Ii8+CiAgICA8d2F5cG9pbnQg bmFtZT0iUzIiIHg9Ii0zNTkuNyIgeT0iLTM1MC44Ii8+CiAgICA8d2F5cG9pbnQgYWx0PSI5NS4w IiBuYW1lPSJBRiIgeD0iMjAwIiB5PSI4Ii8+CiAgICA8d2F5cG9pbnQgYWx0PSI3MC4wIiBuYW1l PSJURCIgeD0iLTIzLiIgeT0iMTAuIi8+CiAgICA8d2F5cG9pbnQgYWx0PSIxMDAuMCIgbmFtZT0i QkFTRUxFRyIgeD0iNjIuMyIgeT0iLTgwLjUiLz4KICAgIDx3YXlwb2ludCBhbHQ9IjE2MC4wIiBu YW1lPSJDTElNQiIgeD0iLTMwMCIgeT0iNjAiLz4KICAgIDx3YXlwb2ludCBhbHQ9IjE0MC4wIiBu YW1lPSJmYXJtIiB4PSIxNjQuMiIgeT0iLTQ4OS4zIi8+CiAgICA8d2F5cG9pbnQgYWx0PSIxNDAu MCIgbmFtZT0iZ2FyYWdlIiB4PSItNDA3LjEiIHk9Ii00OTMuMyIvPgogICAgPHdheXBvaW50IGFs dD0iMTQwLjAiIG5hbWU9InNsb29wIiB4PSItNzQuNiIgeT0iLTQ5MS43Ii8+CiAgICA8d2F5cG9p bnQgYWx0PSIxMTAuMCIgbmFtZT0iU1RBUlQiIHg9IjIwMC4wIiB5PSItMjIuNiIvPgogICAgPHdh eXBvaW50IGxhdD0iNTIuNTI2MDg2IiBsb249IjEwLjQ2MjI3OCIgYWx0PSIxMjAuMCIgbmFtZT0i Q0FSIiB4PSItOTcuMSIgeT0iMjI1LjgiLz4KICAgIDx3YXlwb2ludCBsYXQ9IjUyLjUyMzg4NiIg bG9uPSIxMC40NjM3NjQiIGFsdD0iMTAwLjAiIG5hbWU9IkRST1AiIHg9Ijk3LjYiIHk9Ii0xOC4w Ii8+CiAgICA8d2F5cG9pbnQgbGF0PSI1Mi41MjUyNzQiIGxvbj0iMTAuNDU1MDI4IiBuYW1lPSJB IiB4PSItNTk0LjciIHk9IjE1Mi4yIi8+CiAgICA8d2F5cG9pbnQgbGF0PSI1Mi41MjI5MjAiIGxv bj0iMTAuNDU1ODU1IiBuYW1lPSJCIiB4PSItNTMwLjkiIHk9Ii0xMDUuNCIvPgogICAgPHdheXBv aW50IGxhdD0iNTIuNTI0ODUzIiBsb249IjEwLjQ2OTgyMyIgbmFtZT0iQyIgeD0iNDEzLjUiIHk9 IjExMS40Ii8+CiAgICA8d2F5cG9pbnQgbGF0PSI1Mi41MjI5NTYiIGxvbj0iMTAuNDcwMzc2IiBu YW1lPSJEIiB4PSI0MzkuOCIgeT0iLTgyLjkiLz4KICAgIDx3YXlwb2ludCBsYXQ9IjUyLjUyNDEw MyIgbG9uPSIxMC40NjM5MjQiIG5hbWU9ImFyY2gxIiB4PSItMTE0LjEiIHk9IjExNC4yIi8+CiAg ICA8d2F5cG9pbnQgbGF0PSI1Mi41MjQxMDMiIGxvbj0iMTAuNDY0NjYxIiBuYW1lPSJhcmNoMiIg eD0iLTk3LjEiIHk9IjEwOS40Ii8+CiAgICA8d2F5cG9pbnQgbGF0PSI1Mi41MjQ1NTMiIGxvbj0i MTAuNDY0NzA4IiBuYW1lPSJhcmNoMyIgeD0iLTc5LjciIHk9IjEwNC4wIi8+CiAgICA8d2F5cG9p bnQgbGF0PSI1Mi41MjM5NjAiIGxvbj0iMTAuNDYzNDAwIiBuYW1lPSJMYW5kMSIgeD0iLTEzLjYi IHk9IjE3LjUiLz4KICAgIDx3YXlwb2ludCBsYXQ9IjUyLjUyMzk2MCIgbG9uPSIxMC40NjE5MzAi IG5hbWU9IkxhbmQyIiB4PSItMTQzLjEiIHk9IjI3LjEiLz4KICAgIDx3YXlwb2ludCBhbHQ9Ijc4 LjAiIG5hbWU9IlNGIiB4PSI5MC4yIiB5PSI5Ii8+CiAgPC93YXlwb2ludHM+CiAgPHNlY3RvcnMv PgogIDxleGNlcHRpb25zPgogICAgPGV4Y2VwdGlvbiBjb25kPSJkYXRhbGlua190aW1lID4gNjAi IGRlcm91dGU9IlN0YW5kYnkiLz4KICA8L2V4Y2VwdGlvbnM+CiAgPGJsb2Nrcz4KICAgIDxibG9j ayBuYW1lPSJXYWl0IEdQUyI+CiAgICAgIDxzZXQgdmFsdWU9IjEiIHZhcj0ia2lsbF90aHJvdHRs ZSIvPgogICAgICA8d2hpbGUgY29uZD0iIUdwc0ZpeFZhbGlkKCkiLz4KICAgIDwvYmxvY2s+CiAg ICA8YmxvY2sgbmFtZT0iSG9sZGluZyBwb2ludCI+CiAgICAgIDxzZXQgdmFsdWU9IjEiIHZhcj0i a2lsbF90aHJvdHRsZSIvPgogICAgICA8YXR0aXR1ZGUgcm9sbD0iMCIgdGhyb3R0bGU9IjAiIHZt b2RlPSJ0aHJvdHRsZSIvPgogICAgPC9ibG9jaz4KICAgIDxibG9jayBuYW1lPSJUYWtlb2ZmIiBz dHJpcF9idXR0b249IlRha2VvZmYgKHdwIENMSU1CKSIgc3RyaXBfaWNvbj0idGFrZW9mZi5wbmci PgogICAgICA8ZXhjZXB0aW9uIGNvbmQ9ImVzdGltYXRvcl96ID4gZ3JvdW5kX2FsdCs0MCIgZGVy b3V0ZT0iU3RhbmRieSIvPgogICAgICA8c2V0IHZhbHVlPSIwIiB2YXI9ImtpbGxfdGhyb3R0bGUi Lz4KICAgICAgPGdvIHdwPSJDTElNQiIvPgogICAgPC9ibG9jaz4KICAgIDxibG9jayBuYW1lPSJT dGFuZGJ5IiBzdHJpcF9idXR0b249IlN0YW5kYnkiIHN0cmlwX2ljb249ImhvbWUucG5nIj4KICAg ICAgPGNpcmNsZSByYWRpdXM9Im5hdl9yYWRpdXMiIHdwPSJTVERCWSIvPgogICAgPC9ibG9jaz4K ICAgIDxibG9jayBuYW1lPSJGaWd1cmUgOCBhcm91bmQgd3AgMSIgc3RyaXBfYnV0dG9uPSJGaWd1 cmUgOCAod3AgMS0yKSIgc3RyaXBfaWNvbj0iZWlnaHQucG5nIj4KICAgICAgPGVpZ2h0IGNlbnRl cj0iMSIgcmFkaXVzPSJuYXZfcmFkaXVzIiB0dXJuX2Fyb3VuZD0iMiIvPgogICAgPC9ibG9jaz4K ICAgIDxibG9jayBuYW1lPSJPdmFsIDEtMiIgc3RyaXBfYnV0dG9uPSJPdmFsICh3cCAxLTIpIiBz dHJpcF9pY29uPSJvdmFsLnBuZyI+CiAgICAgIAogICAgICA8b3ZhbCBwMT0iMSIgcDI9IjIiIHJh ZGl1cz0ibmF2X3JhZGl1cyIvPgogICAgPC9ibG9jaz4KICAgIDxibG9jayBuYW1lPSJNT0IiIHN0 cmlwX2J1dHRvbj0iVHVybiBhcm91bmQgaGVyZSIgc3RyaXBfaWNvbj0ibW9iLnBuZyI+CiAgICAg IDxjYWxsIGZ1bj0iTmF2U2V0V2F5cG9pbnRIZXJlKFdQX01PQikiLz4KICAgICAgPGNpcmNsZSBy YWRpdXM9IjEwMCIgd3A9Ik1PQiIvPgogICAgPC9ibG9jaz4KICAgIDxibG9jayBuYW1lPSJMaW5l IDEtMiIgc3RyaXBfYnV0dG9uPSJMaW5lICh3cCAxLTIpIiBzdHJpcF9pY29uPSJsaW5lLnBuZyI+ CiAgICAgIDxleGNlcHRpb24gY29uZD0iZGF0YWxpbmtfdGltZSA+IDIyIiBkZXJvdXRlPSJTdGFu ZGJ5Ii8+CiAgICAgIDxjYWxsIGZ1bj0ibmF2X2xpbmVfaW5pdCgpIi8+CiAgICAgIDxjYWxsIGZ1 bj0ibmF2X2xpbmUoV1BfMSwgV1BfMiwgbmF2X3JhZGl1cykiLz4KICAgIDwvYmxvY2s+CiAgICA8 YmxvY2sgbmFtZT0iU3VydmV5IFMxLVMyIiBzdHJpcF9idXR0b249IlN1cnZleSAod3AgUzEtUzIp IiBzdHJpcF9pY29uPSJzdXJ2ZXkucG5nIj4KICAgICAgPHN1cnZleV9yZWN0YW5nbGUgZ3JpZD0i MTUwIiB3cDE9IlMxIiB3cDI9IlMyIi8+CiAgICA8L2Jsb2NrPgogICAgPGJsb2NrIG5hbWU9Ikxh bmQgUmlnaHQgQUYtVEQiIHN0cmlwX2J1dHRvbj0iTGFuZCByaWdodCAod3AgQUYtVEQpIiBzdHJp cF9pY29uPSJsYW5kLXJpZ2h0LnBuZyI+CiAgICAgIDxzZXQgdmFsdWU9IkRFRkFVTFRfQ0lSQ0xF X1JBRElVUyIgdmFyPSJuYXZfcmFkaXVzIi8+CiAgICAgIDxkZXJvdXRlIGJsb2NrPSJsYW5kIi8+ CiAgICA8L2Jsb2NrPgogICAgPGJsb2NrIG5hbWU9IkxhbmQgTGVmdCBBRi1URCIgc3RyaXBfYnV0 dG9uPSJMYW5kIGxlZnQgKHdwIEFGLVREKSIgc3RyaXBfaWNvbj0ibGFuZC1sZWZ0LnBuZyI+CiAg ICAgIDxzZXQgdmFsdWU9Ii1ERUZBVUxUX0NJUkNMRV9SQURJVVMiIHZhcj0ibmF2X3JhZGl1cyIv PgogICAgICA8ZGVyb3V0ZSBibG9jaz0ibGFuZCIvPgogICAgPC9ibG9jaz4KICAgIDxibG9jayBu YW1lPSJsYW5kIj4KICAgICAgPGNhbGwgZnVuPSJuYXZfY29tcHV0ZV9iYXNlbGVnKFdQX0FGLCBX UF9URCwgV1BfQkFTRUxFRywgbmF2X3JhZGl1cykiLz4KICAgICAgPGNpcmNsZSByYWRpdXM9Im5h dl9yYWRpdXMiIHVudGlsPSJOYXZRZHJDbG9zZVRvKERlZ09mUmFkKGJhc2VsZWdfb3V0X3Fkcikt MTApICYmIDE1ID4gZmFicyhlc3RpbWF0b3JfeiAtIFdheXBvaW50QWx0KFdQX0JBU0VMRUcpKSIg d3A9IkJBU0VMRUciLz4KICAgIDwvYmxvY2s+CiAgICA8YmxvY2sgbmFtZT0iZmluYWwiPgo8IS0t ICAgICAgPGV4Y2VwdGlvbiBjb25kPSJncm91bmRfYWx0ICsgNiA+IGVzdGltYXRvcl96IiBkZXJv dXRlPSJmbGFyZSIvPiAtLT4KICAgICAgPGdvIGFwcHJvYWNoaW5nX3RpbWU9IjAiIGZyb209IkFG IiBobW9kZT0icm91dGUiIHdwPSJTRiIvPgogICAgPC9ibG9jaz4KICAgIDxibG9jayBuYW1lPSJz aG9ydGZpbmFsIj4KPCEtLSAgICAgIDxleGNlcHRpb24gY29uZD0iZ3JvdW5kX2FsdCArIDYgPiBl c3RpbWF0b3JfeiIgZGVyb3V0ZT0iZmxhcmUiLz4gLS0+CiAgICAgIDxnbyBhcHByb2FjaGluZ190 aW1lPSIwIiBmcm9tPSJTRiIgaG1vZGU9InJvdXRlIiB3cD0iVEQiLz4KICAgIDwvYmxvY2s+CiAg ICA8YmxvY2sgbmFtZT0iZmxhcmUiPgogICAgICA8Z28gYXBwcm9hY2hpbmdfdGltZT0iMCIgZnJv bT0iVEQiIGhtb2RlPSJyb3V0ZSIgdGhyb3R0bGU9IjAuMCIgdm1vZGU9InRocm90dGxlIiB3cD0i Q0xJTUIiLz4KICAgICAgPGRlcm91dGUgYmxvY2s9ImZsYXJlIiAvPgo8IS0tICAgICAgPGF0dGl0 dWRlIHJvbGw9IjAuMCIgdGhyb3R0bGU9IjAuMCIgdW50aWw9IkZBTFNFIiB2bW9kZT0idGhyb3R0 bGUiLz4gLS0+CiAgICA8L2Jsb2NrPgogICAgPGJsb2NrIG5hbWU9IlRlc3QgZGF0YWxpbmsgKGdv IHRvIHdwIDIpIj4KICAgICAgPGV4Y2VwdGlvbiBjb25kPSJkYXRhbGlua190aW1lID4gMjIiIGRl cm91dGU9IlN0YW5kYnkiLz4KICAgICAgPGdvIGZyb209IlNUREJZIiBobW9kZT0icm91dGUiIHdw PSIyIi8+CiAgICAgIDxnbyBmcm9tPSIyIiBobW9kZT0icm91dGUiIHdwPSJTVERCWSIvPgogICAg PC9ibG9jaz4KICAgIDxibG9jayBuYW1lPSJWaXNpdCBGYXJtIj4KICAgICAgPGdvIGFwcHJvYWNo aW5nX3RpbWU9Ii0zIiBmcm9tPSJTVERCWSIgaG1vZGU9InJvdXRlIiB3cD0iZmFybSIvPgogICAg PC9ibG9jaz4KICAgIDxibG9jayBuYW1lPSJWaXNpdCBHYXJhZ2UiPgogICAgICA8Z28gYXBwcm9h Y2hpbmdfdGltZT0iLTMiIGZyb209ImZhcm0iIGhtb2RlPSJyb3V0ZSIgd3A9ImdhcmFnZSIvPgog ICAgICA8Z28gYXBwcm9hY2hpbmdfdGltZT0iLTMiIGZyb209ImdhcmFnZSIgaG1vZGU9InJvdXRl IiB3cD0ic2xvb3AiLz4KICAgICAgPGRlcm91dGUgYmxvY2s9IlN0YW5kYnkiLz4KICAgIDwvYmxv Y2s+CiAgICA8YmxvY2sgbmFtZT0iQ2lyY2xlIDEiPgogICAgICA8ZXhjZXB0aW9uIGNvbmQ9ImRh dGFsaW5rX3RpbWUgPiAyNSIgZGVyb3V0ZT0iU3RhbmRieSIvPgogICAgICA8Y2lyY2xlIGFsdD0i V2F5cG9pbnRBbHQoV1BfMSkiIHJhZGl1cz0ibmF2X3JhZGl1cyIgdW50aWw9IjE1ID4gZmFicyhl c3RpbWF0b3JfeiAtIFdheXBvaW50QWx0KFdQXzEpKSIgd3A9IlNUREJZIi8+CiAgICAgIDxnbyBh bHQ9IldheXBvaW50QWx0KFdQXzEpIiBhcHByb2FjaGluZ190aW1lPSItMTUiIGZyb209IlNUREJZ IiBobW9kZT0icm91dGUiIHdwPSIxIi8+CiAgICAgIDxjaXJjbGUgcmFkaXVzPSJuYXZfcmFkaXVz IiB1bnRpbD0iTmF2Q2lyY2xlQ291bnQoKSA+IDAuNyIgd3A9IjEiLz4KICAgICAgPGdvIGFsdD0i V2F5cG9pbnRBbHQoV1BfMSkiIGFwcHJvYWNoaW5nX3RpbWU9Ii0xNSIgZnJvbT0iMSIgaG1vZGU9 InJvdXRlIiB3cD0iU1REQlkiLz4KICAgICAgPGRlcm91dGUgYmxvY2s9IlN0YW5kYnkiLz4KICAg IDwvYmxvY2s+CiAgICA8YmxvY2sgbmFtZT0iQm9tYiBSaWdodCIgc3RyaXBfYnV0dG9uPSJCb21i Ij4KICAgICAgPHNldCB2YWx1ZT0iREVGQVVMVF9DSVJDTEVfUkFESVVTIiB2YXI9Im5hdl9yYWRp dXMiLz4KICAgICAgPGRlcm91dGUgYmxvY2s9ImJvbWIiLz4KICAgIDwvYmxvY2s+CiAgICA8Ymxv Y2sgbmFtZT0iQm9tYiBMZWZ0Ij4KICAgICAgPHNldCB2YWx1ZT0iLURFRkFVTFRfQ0lSQ0xFX1JB RElVUyIgdmFyPSJuYXZfcmFkaXVzIi8+CiAgICAgIDxkZXJvdXRlIGJsb2NrPSJib21iIi8+CiAg ICA8L2Jsb2NrPgogICAgPGJsb2NrIG5hbWU9ImJvbWIiPgogICAgICA8Y2FsbCBmdW49Im5hdl9j b21wdXRlX2Jhc2VsZWcoV1BfU1RBUlQsIFdQX0RST1AsIFdQX0JBU0VMRUcsIG5hdl9yYWRpdXMp Ii8+CiAgICAgIDxjaXJjbGUgcmFkaXVzPSJuYXZfcmFkaXVzIiB1bnRpbD0iTmF2UWRyQ2xvc2VU byhEZWdPZlJhZChiYXNlbGVnX291dF9xZHIpLTEwKSIgd3A9IkJBU0VMRUciLz4KICAgIDwvYmxv Y2s+CiAgICA8YmxvY2sgbmFtZT0iYWxpZ24iPgogICAgICA8Z28gYXBwcm9hY2hpbmdfdGltZT0i MCIgZnJvbT0iU1RBUlQiIGhtb2RlPSJyb3V0ZSIgd3A9IkRST1AiLz4KICAgIDwvYmxvY2s+CiAg ICA8YmxvY2sgbmFtZT0ic2hvb3QiPgogICAgIDxzZXQgdmFsdWU9IkJvbWJTaG9vdCgpIiB2YXI9 InVuaXQiLz4KICAgICAgPGdvIGZyb209IkRST1AiIGhtb2RlPSJyb3V0ZSIgd3A9IkNMSU1CIi8+ CiAgICAgIDxzZXQgdmFsdWU9IkJvbWJDbG9zZUhhdGNoKCkiIHZhcj0idW5pdCIvPgogICAgICA8 ZGVyb3V0ZSBibG9jaz0ic3RhbmRieSIvPgogICAgICA8IS0tIFB1dCB5b3VyIHNob290IGNvZGUg aGVyZSAtLT4KICAgICAgPCEtLTxkZXJvdXRlIGJsb2NrPSJUYWtlb2ZmIi8+IC0tPgogICAgPC9i bG9jaz4KICAgICA8YmxvY2sgbmFtZT0iY2xvc2UiPgogICAgICA8c2V0IHZhbHVlPSJCb21iQ2xv c2VIYXRjaCgpIiB2YXI9InVuaXQiLz4KICAgICAgPGRlcm91dGUgYmxvY2s9InN0YW5kYnkiLz4K ICAgIDwvYmxvY2s+CiAgICA8YmxvY2sgbmFtZT0iQm9tYiBSaWdodCBGYWtlIiBzdHJpcF9idXR0 b249IkZha2UiPgogICAgICA8c2V0IHZhbHVlPSJERUZBVUxUX0NJUkNMRV9SQURJVVMiIHZhcj0i bmF2X3JhZGl1cyIvPgogICAgICA8ZGVyb3V0ZSBibG9jaz0iYm9tYmZha2UiLz4KICAgIDwvYmxv Y2s+CiAgICA8YmxvY2sgbmFtZT0iQm9tYiBMZWZ0IEZha2UiPgogICAgICA8c2V0IHZhbHVlPSIt REVGQVVMVF9DSVJDTEVfUkFESVVTIiB2YXI9Im5hdl9yYWRpdXMiLz4KICAgICAgPGRlcm91dGUg YmxvY2s9ImJvbWJmYWtlIi8+CiAgICA8L2Jsb2NrPgogICAgPGJsb2NrIG5hbWU9ImJvbWJmYWtl Ij4KICAgICAgPGNhbGwgZnVuPSJuYXZfY29tcHV0ZV9iYXNlbGVnKFdQX1NUQVJULCBXUF9EUk9Q LCBXUF9CQVNFTEVHLCBuYXZfcmFkaXVzKSIvPgogICAgICA8Y2lyY2xlIHJhZGl1cz0ibmF2X3Jh ZGl1cyIgdW50aWw9Ik5hdlFkckNsb3NlVG8oRGVnT2ZSYWQoYmFzZWxlZ19vdXRfcWRyKS0xMCki IHdwPSJCQVNFTEVHIi8+CiAgICA8L2Jsb2NrPgogICAgPGJsb2NrIG5hbWU9ImFsaWduZmFrZSI+ CiAgICAgIDxnbyBhcHByb2FjaGluZ190aW1lPSIwIiBmcm9tPSJTVEFSVCIgaG1vZGU9InJvdXRl IiB3cD0iRFJPUCIvPgogICAgPC9ibG9jaz4KICAgIDxibG9jayBuYW1lPSJzaG9vdGZha2UiPgog ICAgICA8ZGVyb3V0ZSBibG9jaz0iVGFrZW9mZiIvPgogICAgPC9ibG9jaz4KICA8L2Jsb2Nrcz4K PC9mbGlnaHRfcGxhbj4K --_ff70126a-7e33-400d-8b95-5bf1bbff75d2_-- From MAILER-DAEMON Fri Aug 28 05:38:37 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Mgxun-0003F5-Ip for mharc-paparazzi-devel@gnu.org; Fri, 28 Aug 2009 05:38:37 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mgxuk-0003El-BX for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 05:38:34 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mgxui-0003EU-RE for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 05:38:32 -0400 Received: from [199.232.76.173] (port=59650 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mgxui-0003EP-Eo for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 05:38:32 -0400 Received: from smtp1.infomaniak.ch ([84.16.68.89]:42004) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Mgxuh-0003S0-So for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 05:38:32 -0400 Received: from rome (217-88.77-83.cust.bluewin.ch [83.77.88.217]) (authenticated bits=0) by smtp1.infomaniak.ch (8.14.2/8.14.2) with ESMTP id n7S9cUgm021382 for ; Fri, 28 Aug 2009 11:38:30 +0200 From: =?iso-8859-1?Q?C=E9dric_Marzer?= To: References: <008101ca26db$6ec97430$4c5c5c90$@marzer@mrsa.ch> <004601ca27af$50db9b90$f292d2b0$@marzer@mrsa.ch> <4A9792C0.9050906@shef.ac.uk> <006301ca27bb$a57b76a0$f07263e0$@marzer@mrsa.ch> <1251450733.4602.14.camel@gareth> In-Reply-To: <1251450733.4602.14.camel@gareth> Subject: RE: [Paparazzi-devel] Protocol for the downlink Date: Fri, 28 Aug 2009 11:38:35 +0200 Message-ID: <008201ca27c3$50e0dba0$f2a292e0$@marzer@mrsa.ch> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Aconv8yy/wTV8N1LTnyNRfEzJdDAVAAAk7xQ Content-Language: fr-ch X-Antivirus: Dr.Web (R) for Mail Servers on smtp1 host X-Antivirus-Code: 100000 X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6? (barebone, rare!) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Aug 2009 09:38:34 -0000 Interfacing airside should be interesting...have you considered going down the I2C/SPI route rather than tapping the serial line? I guess tapping the serial line is easier as a start. It would be possible to avoid to use a second microcontroller by just connecting a MAX dedicated OSD chip to the spi, but for now I will be using the board with an LPC and a MAX that I already have. I might develop later a graphical OSD that uses either the LCP2148 or a PIC32 (cheaper). In this case you need a dedicated microcontroller because the timing is important, but you don't need the relatively expensive MAX chip. From MAILER-DAEMON Fri Aug 28 08:04:30 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Mh0Bx-0001LV-Qq for mharc-paparazzi-devel@gnu.org; Fri, 28 Aug 2009 08:04:29 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mh0Bu-0001Id-Qj for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 08:04:26 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mh0Bq-0001ET-1o for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 08:04:26 -0400 Received: from [199.232.76.173] (port=60103 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mh0Bp-0001EJ-S0 for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 08:04:21 -0400 Received: from mx20.gnu.org ([199.232.41.8]:48883) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Mh0Bp-0003s0-9e for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 08:04:21 -0400 Received: from imss-1.enac.fr ([195.220.159.36]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Mh0Bo-0007J3-Mw for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 08:04:20 -0400 Received: from mauve.recherche.enac.fr (imss-1.imss.interne.enac [127.0.0.1]) by imss-1.enac.fr (Postfix) with ESMTP id 47B6018B3A4 for ; Fri, 28 Aug 2009 14:04:18 +0200 (CEST) Received: from [10.31.1.82] (sepia.recherche.enac.fr [10.31.1.82])by mauve.recherche.enac.fr (Postfix) with ESMTP id 2ABB42FA825for ; Fri, 28 Aug 2009 14:04:18 +0200 (CEST) Message-ID: <4A97C7C2.40401@free.fr> Date: Fri, 28 Aug 2009 14:04:18 +0200 From: Pascal Brisset User-Agent: Mozilla-Thunderbird 2.0.0.22 (X11/20090706) MIME-Version: 1.0 To: paparazzi-devel@nongnu.org Subject: Re: [Paparazzi-devel] droping paintball References: In-Reply-To: Content-Type: text/plain; charset=Big5 X-imss-version: 2.5 X-imss-result: Passed X-imss-scores: Clean:99.90000 C:15 M:2 S:5 R:5 X-imss-settings: Baseline:1 C:1 M:1 S:1 R:1 (0.0000 0.0000) Content-Transfer-Encoding: quoted-printable X-Detected-Operating-System: by mx20.gnu.org: GNU/Linux 2.4-2.6 X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6, seldom 2.4 (older, 4) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Aug 2009 12:04:27 -0000 Hi, the error message is not explicit enough ? /users/brisset/pprz/savannah/paparazzi3/conf/flight_plans/bombingtest.xml= : Unknown block: 'standby' You block is named "Standby"; If you want to simulate, you also have to add sim.srcs +=3D bomb.c to your airframe file Maybe not related: there is an EMAV09.xml flight plan commited in the svn. It contains the communicated waypoints and areas coordinates ... (I'm so disappointed that the organizers did not provide these coordinates using the Paparazzi syntax :-) ) --Pascal =B3=A2 flying pig wrote: > Hi guys > > I am using the EMAV08 flight plan to try to see how the paint ball > dropping will look like, so, i added the shoot into the flight plan, > but it can not compiled (however, once i remote the shoot, it works ??) > > > I have enclosed my airfram file (note, I am still using the old > version of paaprazzi) and flight plan, can someone helps? > > > bombing.xml is the aircraft > bombingtest is flight plan i modifiy from EMAV08.xml > > Thanks > > Chen > > -----------------------------------------------------------------------= - > =C1o=A9=FA=B7j=B4M=A9M=C2s=C4=FD=BA=F4=B8=F4=AA=BA=A7K=B6O=A4u=A8=E3=A6= C =A1X Windows Live =A4u=A8=E3=A6C > > -----------------------------------------------------------------------= - > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel From MAILER-DAEMON Fri Aug 28 08:42:34 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Mh0mn-0000O8-6I for mharc-paparazzi-devel@gnu.org; Fri, 28 Aug 2009 08:42:33 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mh0mg-0000KO-Gt for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 08:42:27 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mh0mZ-0000HL-8w for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 08:42:24 -0400 Received: from [199.232.76.173] (port=43235 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mh0mY-0000Gi-6G for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 08:42:18 -0400 Received: from blu0-omc2-s20.blu0.hotmail.com ([65.55.111.95]:28948) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Mh0mX-0005x5-RR for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 08:42:18 -0400 Received: from BLU149-W2 ([65.55.111.72]) by blu0-omc2-s20.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 28 Aug 2009 05:42:17 -0700 Message-ID: Content-Type: multipart/alternative; boundary="_88237e72-73de-42d6-a6e8-af07e9f93f29_" X-Originating-IP: [134.96.163.226] From: =?big5?B?s6IgZmx5aW5nIHBpZw==?= To: Subject: RE: [Paparazzi-devel] droping paintball Date: Fri, 28 Aug 2009 12:42:17 +0000 Importance: Normal In-Reply-To: <4A97C7C2.40401@free.fr> References: <4A97C7C2.40401@free.fr> MIME-Version: 1.0 X-OriginalArrivalTime: 28 Aug 2009 12:42:17.0415 (UTC) FILETIME=[FA012D70:01CA27DC] X-detected-operating-system: by monty-python.gnu.org: Windows 2000 SP4, XP SP1+ X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Aug 2009 12:42:28 -0000 --_88237e72-73de-42d6-a6e8-af07e9f93f29_ Content-Type: text/plain; charset="big5" Content-Transfer-Encoding: 8bit Hi there when i compile, the screen just freeze, didn't even give me any feedback, but I think i really need to check my eye shortly... anywa, thanks for the quick response, it really helps me alot. Thank you very much :) Chen > Date: Fri, 28 Aug 2009 14:04:18 +0200 > From: pascal.brisset@free.fr > To: paparazzi-devel@nongnu.org > Subject: Re: [Paparazzi-devel] droping paintball > > Hi, > > the error message is not explicit enough ? > > /users/brisset/pprz/savannah/paparazzi3/conf/flight_plans/bombingtest.xml: > Unknown block: 'standby' > > You block is named "Standby"; > > If you want to simulate, you also have to add > sim.srcs += bomb.c > to your airframe file > > Maybe not related: there is an EMAV09.xml flight plan commited in the > svn. It contains the communicated waypoints and areas coordinates ... > (I'm so disappointed that the organizers did not provide these > coordinates using the Paparazzi syntax :-) ) > > --Pascal > > > ³¢ flying pig wrote: > > Hi guys > > > > I am using the EMAV08 flight plan to try to see how the paint ball > > dropping will look like, so, i added the shoot into the flight plan, > > but it can not compiled (however, once i remote the shoot, it works ??) > > > > > > I have enclosed my airfram file (note, I am still using the old > > version of paaprazzi) and flight plan, can someone helps? > > > > > > bombing.xml is the aircraft > > bombingtest is flight plan i modifiy from EMAV08.xml > > > > Thanks > > > > Chen > > > > ------------------------------------------------------------------------ > > Áo©ú·j´M©MÂsÄýºô¸ôªº§K¶O¤u¨ã¦C ¡X Windows Live ¤u¨ã¦C > > > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > Paparazzi-devel mailing list > > Paparazzi-devel@nongnu.org > > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > > > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel _________________________________________________________________ »P±z³ßÅwªº¤H¦b½u¤W¤À¨É¦^¾Ð¡C http://www.microsoft.com/taiwan/windows/windowslive/products/photos-share.aspx?tab=1 --_88237e72-73de-42d6-a6e8-af07e9f93f29_ Content-Type: text/html; charset="big5" Content-Transfer-Encoding: 8bit Hi there
 
 
 when i compile, the screen just freeze, didn't even give me any feedback, but  I think i really need to check my eye shortly... anywa, thanks for the quick response, it really helps me alot.
 
 
 
 
Thank you very much :)
 
 
 
                                                                                              Chen
 
> Date: Fri, 28 Aug 2009 14:04:18 +0200
> From: pascal.brisset@free.fr
> To: paparazzi-devel@nongnu.org
> Subject: Re: [Paparazzi-devel] droping paintball
>
> Hi,
>
> the error message is not explicit enough ?
>
> /users/brisset/pprz/savannah/paparazzi3/conf/flight_plans/bombingtest.xml:
> Unknown block: 'standby'
>
> You block is named "Standby";
>
> If you want to simulate, you also have to add
> sim.srcs += bomb.c
> to your airframe file
>
> Maybe not related: there is an EMAV09.xml flight plan commited in the
> svn. It contains the communicated waypoints and areas coordinates ...
> (I'm so disappointed that the organizers did not provide these
> coordinates using the Paparazzi syntax :-) )
>
> --Pascal
>
>
> ³¢ flying pig wrote:
> > Hi guys
> >
> > I am using the EMAV08 flight plan to try to see how the paint ball
> > dropping will look like, so, i added the shoot into the flight plan,
> > but it can not compiled (however, once i remote the shoot, it works ??)
> >
> >
> > I have enclosed my airfram file (note, I am still using the old
> > version of paaprazzi) and flight plan, can someone helps?
> >
> >
> > bombing.xml is the aircraft
> > bombingtest is flight plan i modifiy from EMAV08.xml
> >
> > Thanks
> >
> > Chen
> >
> > ------------------------------------------------------------------------
> > Áo©ú·j´M©MÂsÄýºô¸ôªº§K¶O¤u¨ã¦C ¡X Windows Live ¤u¨ã¦C
> > <http://download.live.com/toolbar>
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > Paparazzi-devel mailing list
> > Paparazzi-devel@nongnu.org
> > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel
>
>
>
> _______________________________________________
> Paparazzi-devel mailing list
> Paparazzi-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel


»P±z³ßÅwªº¤H¦b½u¤W¤À¨É¦^¾Ð »P±z³ßÅwªº¤H --_88237e72-73de-42d6-a6e8-af07e9f93f29_-- From MAILER-DAEMON Fri Aug 28 09:16:49 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Mh1Jx-00017i-0w for mharc-paparazzi-devel@gnu.org; Fri, 28 Aug 2009 09:16:49 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mh1Ju-00014f-S0 for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 09:16:46 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mh1Jt-00012J-9o for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 09:16:45 -0400 Received: from [199.232.76.173] (port=48883 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mh1Jt-00011x-3T for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 09:16:45 -0400 Received: from ey-out-1920.google.com ([74.125.78.145]:58912) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Mh1Jr-0008MI-92 for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 09:16:44 -0400 Received: by ey-out-1920.google.com with SMTP id 26so30596eyw.2 for ; Fri, 28 Aug 2009 06:16:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=rn/aDHWeUdLSexoSNd9eLRM8VLh2DH2Mbz18XiAoRik=; b=kUozdvdjSiBmQOl0eRffd8Wwv2+GPf3O/VX8vsThv6HTJ50cdS5ZYwd85s4wU7POts a4AQipchENzY7qVKwYkBAuOsg3XFw9UJPv60oJhJReuitNn9WkE8b1Ldgx+QIIIMjlIR O2K3+liKwVh/xhmSLgRvGBkqoxWNyha+f/eDU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=nNxa3NodWnJ08LidEL1htix93FvsJkz+SkFX1FBG6jBx8quxUEfkQRY8lG9eKhcG5e fZZLHJJUFJn+z9koGW4hQWNx8el0DJ04R8VuWTbl3wMhgK371585WH5vf6KNb+dzX+/j 8qgigG2T+n49WnEbdpHFahQgne7oJbP1mq2Og= MIME-Version: 1.0 Received: by 10.216.93.16 with SMTP id k16mr211737wef.33.1251465401384; Fri, 28 Aug 2009 06:16:41 -0700 (PDT) In-Reply-To: <4A978456.4010207@web.de> References: <4A978456.4010207@web.de> Date: Fri, 28 Aug 2009 13:16:41 +0000 Message-ID: <4d39daa50908280616t6b82bbb2tdfff26195c66646a@mail.gmail.com> Subject: Re: [Paparazzi-devel] Log parser for Matlab From: Rui Costa To: paparazzi-devel@nongnu.org Content-Type: multipart/alternative; boundary=0016e6d6495cb2bf330472337e5c X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Aug 2009 13:16:47 -0000 --0016e6d6495cb2bf330472337e5c Content-Type: text/plain; charset=ISO-8859-1 Good. Can you publish that information on wiki? Best regards Rui Costa On Fri, Aug 28, 2009 at 7:16 AM, Andreas Gaeb wrote: > Hello everybody, > > I've created a new Matlab log parser in case anybody is still working > with that for reviewing logs. It is a bit faster than PprzLogReader_1_0, > more flexible and can read any type of message present in a log file. It > has been tested with Matlab 7.1 and R2009a, so it should also work with > releases in between. Examples of usage are given in the file. > > I'll also be having a look at Roman Krashanitsa's log plotter GUI which > seems to be broken with actual SVN log files. > > I tried to upload the script to the wiki, but this seems to accept only > image files, so I'm attaching it here. Maybe someone can add it to the SVN. > > Regards, > Andreas > > function s = log2struct(logfilename) > % parse a PPRZ log file > %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% > % function s = log2struct(logfilename) > % Parses a log data file from the Paparazzi ground station into a > % Matlab variable. The log is sorted by aircraft ID and message ID. > % Parsing the log definition file (xx.log) is not required. > % > % Argument > % The name of the log data file to be parsed. > % May be omitted, in which case a file open dialog is used. > % > % Returns > % A struct of dimension 1 x nAircraft > % For each type of message received there is a substruct with the fields > % timestamp and contents as arrays over time. The columns of the contents > % array correspond to the message's data fields as defined in messages.xml. > % > % Example > % >> % 3D plot of the trajectory of aircraft #1 > % >> s = log2struct('09_08_26__14_18_29.data'); > % >> plot3(s(1).GPS.content(:,2), > s(1).GPS.content(:,3),s(1).GPS.content(:,5)) > % >> % what did the servos do? > % >> plot (s(1).ACTUATORS.timestamp, s(1).ACTUATORS.content) > % > % Known Bugs > % The method fails when the number of data elements for one message type > % changes during the log file, as may happen when the configuration file is > % changed in between or with arrays of variable size. > % > %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% > % > % Author: Andreas Gaeb > % Created: 27-Aug-2009 > % $Id$ > % > % Copyright (C) 2009 Andreas Gaeb > % > % This file is part of paparazzi. > % > % paparazzi is free software; you can redistribute it and/or modify > % it under the terms of the GNU General Public License as published by > % the Free Software Foundation; either version 2, or (at your option) > % any later version. > % > % paparazzi is distributed in the hope that it will be useful, > % but WITHOUT ANY WARRANTY; without even the implied warranty of > % MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the > % GNU General Public License for more details. > % > % You should have received a copy of the GNU General Public License > % along with paparazzi; see the file COPYING. If not, write to > % the Free Software Foundation, 59 Temple Place - Suite 330, > % Boston, MA 02111-1307, USA. > % > %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% > > persistent log2struct_old_working_dir > > % no arguments? open dialog > if nargin < 1 > [filename, pathname] = uigetfile(... > {'*.data', 'Paparazzi log data files (*.data)'}, ... > 'Open data file', ... > log2struct_old_working_dir); > if ~filename, return, end > logfilename = fullfile(pathname, filename); > log2struct_old_working_dir = pathname; > % display the filename for copy/paste > disp (['parsing ' logfilename '...']); > end > > fid = fopen(logfilename); > if fid == -1 > error('File %s not found', logfilename); > end > > try > % read everything as timestamp, A/C ID, msg name and msg contents > C = textscan(fid, '%f %u %s %[^\n]'); > > if isempty(C{1}) > error ('File %s does not seem to be a Paparazzi log data file.', > logfilename); > end > > timestamp = C{1}; > aircraftID = C{2}; > msgName = C{3}; > msgContent = C{4}; > > % find s which messages have been sent > uniqueMsgs = unique(msgName); > nMsg = size(uniqueMsgs,1); > > % find s which aircraft sent something > uniqueAC = unique(aircraftID); > nAC = size(uniqueAC,1); > > % distribute the messages to their sending aircraft > for iAC = nAC:-1:1 % counting backwards eliminates preallocation > % the ID of ith aircraft > acID = uniqueAC(iAC); > s(iAC).AIRCRAFT_ID = acID; > > % the indices of all messages send by ith aircraft > allMsgsFromThisAircraft = (aircraftID == uniqueAC(iAC)); > timestampFromThisAircraft = timestamp(allMsgsFromThisAircraft); > msgNameFromThisAircraft = msgName(allMsgsFromThisAircraft); > msgContentFromThisAircraft = msgContent(allMsgsFromThisAircraft); > > % for each message name > for iMsg = 1:nMsg > theMsgName = uniqueMsgs{iMsg}; > > % when was this special message sent by the ith aircraft? > thisMsgFromThisAircraft = strmatch(... > theMsgName, msgNameFromThisAircraft, 'exact'); > > % record with timestamp and contents > s(iAC).(theMsgName).timestamp = ... > timestampFromThisAircraft(thisMsgFromThisAircraft); > [s(iAC).(theMsgName).content, status] = str2num(char(... > msgContentFromThisAircraft(thisMsgFromThisAircraft))); %#ok > if ~status && ~strcmp(theMsgName, 'PONG') > warning('Paparazzi:log2struct:EmptyContent', ... > 'Could not read contents of %s message from aircraft #%i', ... > theMsgName, acID); > continue; > end > end > > end > > fclose (fid); > > catch theError > fclose(fid); > rethrow(theError); > end > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > > -- Rui Costa www.azoreanuav.com --0016e6d6495cb2bf330472337e5c Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Good. Can you publish that information on wiki?
=A0
=A0
Best regards
Rui Costa

On Fri, Aug 28, 2009 at 7:16 AM, Andreas Gaeb <a.gaeb@web.de><= /span> wrote:
Hello everybody,

I've= created a new Matlab log parser in case anybody is still working
with t= hat for reviewing logs. It is a bit faster than PprzLogReader_1_0,
more flexible and can read any type of message present in a log file. Ithas been tested with Matlab 7.1 and R2009a, so it should also work withreleases in between. Examples of usage are given in the file.

I'= ;ll also be having a look at Roman Krashanitsa's log plotter GUI which<= br> seems to be broken with actual SVN log files.

I tried to upload the = script to the wiki, but this seems to accept only
image files, so I'= m attaching it here. Maybe someone can add it to the SVN.

Regards, =A0 =A0 =A0 =A0Andreas

function s =3D= log2struct(logfilename)
% parse a PPRZ log file
%%%%%%%%%%%%%%%%%%%%= %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% function s =3D= log2struct(logfilename)
% Parses a log data file from the Paparazzi ground station into a
% Matl= ab variable. The log is sorted by aircraft ID and message ID.
% Parsing = the log definition file (xx.log) is not required.
%
% Argument
% The name of the log data file to be parsed.
% May be omitted, in which= case a file open dialog is used.
%
% Returns
% A struct of dimens= ion 1 x nAircraft
% For each type of message received there is a substru= ct with the fields
% timestamp and contents as arrays over time. The columns of the contents% array correspond to the message's data fields as defined in message= s.xml.
%
% Example
% >> % 3D plot of the trajectory of aircr= aft #1
% >> s =3D log2struct('09_08_26__14_18_29.data');
% >&g= t; plot3(s(1).GPS.content(:,2), s(1).GPS.content(:,3),s(1).GPS.content(:,5)= )
% >> % what did the servos do?
% >> plot (s(1).ACTUATOR= S.timestamp, s(1).ACTUATORS.content)
%
% Known Bugs
% The method fails when the number of data elements fo= r one message type
% changes during the log file, as may happen when the= configuration file is
% changed in between or with arrays of variable s= ize.
%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%= %%%%%
%
% Author: Andreas Gaeb
% Created: =A027-Aug-2009
% $Id$=
%
% Copyright (C) 2009 Andreas Gaeb
%
% This file is part of p= aparazzi.
%
% paparazzi is free software; you can redistribute it and/or modify% it under the terms of the GNU General Public License as published by
= % the Free Software Foundation; either version 2, or (at your option)
% any later version.
%
% paparazzi is distributed in the hope that it= will be useful,
% but WITHOUT ANY WARRANTY; without even the implied wa= rranty of
% MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. =A0See = the
% GNU General Public License for more details.
%
% You should have re= ceived a copy of the GNU General Public License
% along with paparazzi; = see the file COPYING. =A0If not, write to
% the Free Software Foundation= , 59 Temple Place - Suite 330,
% Boston, MA 02111-1307, USA.
%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%= %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

persistent log2struct_old_wor= king_dir

% no arguments? open dialog
if nargin < 1
=A0[file= name, pathname] =3D uigetfile(...
=A0 =A0{'*.data', 'Paparazzi log data files (*.data)'}, ...=
=A0 =A0'Open data file', ...
=A0 =A0log2struct_old_working_d= ir);
=A0if ~filename, return, end
=A0 =A0 =A0 =A0logfilename =3D full= file(pathname, filename);
=A0log2struct_old_working_dir =3D pathname;
=A0% display the filename fo= r copy/paste
=A0disp (['parsing ' logfilename '...']);end

fid =3D fopen(logfilename);
if fid =3D=3D -1
=A0error(&#= 39;File %s not found', logfilename);
end

try
=A0% read everything as timestamp, A/C ID, msg name and m= sg contents
=A0C =3D textscan(fid, '%f %u %s %[^\n]');

= =A0if isempty(C{1})
=A0 =A0error ('File %s does not seem to be a Pap= arazzi log data file.', logfilename);
=A0end

=A0timestamp =3D C{1};
=A0aircraftID =3D C{2};
=A0msgNa= me =3D C{3};
=A0msgContent =3D C{4};

=A0% find s which messages h= ave been sent
=A0uniqueMsgs =3D unique(msgName);
=A0nMsg =3D size(uni= queMsgs,1);

=A0% find s which aircraft sent something
=A0uniqueAC =3D unique(aircraftID);
=A0nAC =3D size(uniqueAC,1);

= =A0% distribute the messages to their sending aircraft
=A0for iAC =3D nA= C:-1:1 % counting backwards eliminates preallocation
=A0 =A0% the ID of = ith aircraft
=A0 =A0acID =3D uniqueAC(iAC);
=A0 =A0s(iAC).AIRCRAFT_ID =3D acID;
=A0 =A0% the indices of all messages send by ith aircraft
=A0 =A0allMs= gsFromThisAircraft =3D (aircraftID =3D=3D uniqueAC(iAC));
=A0 =A0timesta= mpFromThisAircraft =3D timestamp(allMsgsFromThisAircraft);
=A0 =A0msgNameFromThisAircraft =3D msgName(allMsgsFromThisAircraft);
=A0= =A0msgContentFromThisAircraft =3D msgContent(allMsgsFromThisAircraft);
=
=A0 =A0% for each message name
=A0 =A0for iMsg =3D 1:nMsg
=A0 =A0= =A0theMsgName =3D uniqueMsgs{iMsg};

=A0 =A0 =A0% when was this special message sent by the ith aircraft?=A0 =A0 =A0thisMsgFromThisAircraft =3D strmatch(...
=A0 =A0 =A0 =A0theM= sgName, msgNameFromThisAircraft, 'exact');

=A0 =A0 =A0% reco= rd with timestamp and contents
=A0 =A0 =A0s(iAC).(theMsgName).timestamp =3D ...
=A0 =A0 =A0 =A0timestam= pFromThisAircraft(thisMsgFromThisAircraft);
=A0 =A0 =A0[s(iAC).(theMsgNa= me).content, status] =3D str2num(char(...
=A0 =A0 =A0 =A0msgContentFromT= hisAircraft(thisMsgFromThisAircraft))); %#ok<ST2NM>
=A0 =A0 =A0if ~status && ~strcmp(theMsgName, 'PONG')
=A0= =A0 =A0 =A0warning('Paparazzi:log2struct:EmptyContent', ...
=A0= =A0 =A0 =A0 =A0'Could not read contents of %s message from aircraft #%= i', ...
=A0 =A0 =A0 =A0 =A0theMsgName, acID);
=A0 =A0 =A0 =A0continue;
=A0 =A0 =A0end
=A0 =A0end

=A0end
<= br>=A0fclose (fid);

catch theError
=A0fclose(fid);
=A0rethrow(= theError);
end

_______________________________________________Paparazzi-devel mailing list
Paparazzi-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/paparazzi-devel




--
Rui Costa
ww= w.azoreanuav.com
--0016e6d6495cb2bf330472337e5c-- From MAILER-DAEMON Fri Aug 28 09:58:25 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Mh1yD-0006cc-8d for mharc-paparazzi-devel@gnu.org; Fri, 28 Aug 2009 09:58:25 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MgH3N-0001VP-2A for paparazzi-devel@nongnu.org; Wed, 26 Aug 2009 07:52:37 -0400 Received: from mailman by lists.gnu.org with local (Exim 4.43) id 1MgH3M-0001VG-MF for paparazzi-devel@nongnu.org; Wed, 26 Aug 2009 07:52:36 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MgGzY-0006g5-KV for paparazzi-devel@nongnu.org; Wed, 26 Aug 2009 07:48:49 -0400 Received: from [199.232.76.173] (port=33678 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MgGzY-0006g2-H3 for paparazzi-devel@nongnu.org; Wed, 26 Aug 2009 07:48:40 -0400 Received: from n7.bullet.re3.yahoo.com ([68.142.237.92]:37595) by monty-python.gnu.org with smtp (Exim 4.60) (envelope-from ) id 1MgGzY-000450-75 for paparazzi-devel@nongnu.org; Wed, 26 Aug 2009 07:48:40 -0400 Received: from [68.142.237.88] by n7.bullet.re3.yahoo.com with NNFMP; 26 Aug 2009 11:48:30 -0000 Received: from [67.195.9.82] by t4.bullet.re3.yahoo.com with NNFMP; 26 Aug 2009 11:48:30 -0000 Received: from [67.195.9.106] by t2.bullet.mail.gq1.yahoo.com with NNFMP; 26 Aug 2009 11:48:30 -0000 Received: from [127.0.0.1] by omp110.mail.gq1.yahoo.com with NNFMP; 26 Aug 2009 11:48:30 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 263119.53078.bm@omp110.mail.gq1.yahoo.com Received: (qmail 96131 invoked by uid 60001); 26 Aug 2009 11:48:30 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1251287309; bh=jk9KJ/+lH//EyFwitcm1V0I2PHgoYWyCqOCeBdTUbVM=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=i7pq318pmpiYufq6/n/4j+Dokihoyluy+Jg/+/9W+tg93Sc+LHoobbWspcLw3sU+kvMNGRdEf7j+d9wxBJaFCWkB8CIvaWSexDblfDfDTKU76l77ZYFgtfHVZ+zPaJAI6+d06fu93Xpy2QdHrKjODUYXFusoU5WFYqzFTLpxvBM= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=gkZxU8xvN2n4GQBlDnFNVzv5b8aAvfLwi98Jy8nj4u90IPm93QvpkEUPMXosvxgrLEbM9E26G9pVQB58kDg5Cd1fWZztSzXYuNHEDk8iXqfRAOyu8Fz44/N9+BIdSzuq/P68QkxbWYXCNup7XcPCvY7O8SisNSj/XoiRkX0YjqU=; Message-ID: <960569.39333.qm@web111612.mail.gq1.yahoo.com> X-YMail-OSG: K_gJhDsVM1lPiPcIt1p_DkoGrKgaF2nm_QAh.GhspZpk53Mmhg4ZhxDCY2hSy0y0E.WyTJXpmpiLrQgbjNAGbmHqIJsK4ApeyAAePhxP4oTJy7RNIX.L0Ycwp169FiWKIZ84J40QjEVEo.ImZnJnoxAn5_Tye.ggwOorfankXCWmDrESVY20rIlHy.MidpEjS61j09gvIMkc6lAuVUDlCQQ2349k3EcviJvNd1z23gLUnHSt7zCOOVO.98y8zkq_sq9xzoglbvz6OXnOTjgdq.I- Received: from [188.26.171.74] by web111612.mail.gq1.yahoo.com via HTTP; Wed, 26 Aug 2009 04:48:29 PDT X-Mailer: YahooMailRC/1358.27 YahooMailWebService/0.7.338.2 Date: Wed, 26 Aug 2009 04:48:29 -0700 (PDT) From: Marian Cristina To: paparazzi-devel@nongnu.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-989073930-1251287309=:39333" X-detected-operating-system: by monty-python.gnu.org: FreeBSD 4.7-5.2 (or MacOS X 10.2-10.4) (2) X-TMDA-Confirmed: Wed Aug 26 07:52:36 EDT 2009 X-Mailman-Approved-At: Fri, 28 Aug 2009 09:58:23 -0400 Subject: [Paparazzi-devel] Hello X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Aug 2009 11:52:37 -0000 --0-989073930-1251287309=:39333 Content-Type: text/plain; charset=us-ascii I would like to ask if it is possible to write a letter by poste to an paparazzi.And i would like an addresse to where to write to.Thanks' --0-989073930-1251287309=:39333 Content-Type: text/html; charset=us-ascii
I would like to ask if it is possible to write a letter by poste to an paparazzi.And i would like an addresse to where to write to.Thanks'

--0-989073930-1251287309=:39333-- From MAILER-DAEMON Fri Aug 28 12:32:05 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Mh4Mu-0003Em-RC for mharc-paparazzi-devel@gnu.org; Fri, 28 Aug 2009 12:32:04 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mh4Ms-0003Bk-C2 for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 12:32:02 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mh4Mn-00035U-Es for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 12:32:01 -0400 Received: from [199.232.76.173] (port=40708 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mh4Mn-00035C-Am for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 12:31:57 -0400 Received: from imss-1.enac.fr ([195.220.159.36]:39017) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Mh4Mm-000507-ON for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 12:31:57 -0400 Received: from mauve.recherche.enac.fr (imss-1.imss.interne.enac [127.0.0.1]) by imss-1.enac.fr (Postfix) with ESMTP id 8FD3618B3A7 for ; Fri, 28 Aug 2009 18:31:55 +0200 (CEST) Received: from [10.31.1.82] (sepia.recherche.enac.fr [10.31.1.82])by mauve.recherche.enac.fr (Postfix) with ESMTP id 7A62C2FA825for ; Fri, 28 Aug 2009 18:31:55 +0200 (CEST) Message-ID: <4A98067B.6090704@free.fr> Date: Fri, 28 Aug 2009 18:31:55 +0200 From: Pascal Brisset User-Agent: Mozilla-Thunderbird 2.0.0.22 (X11/20090706) MIME-Version: 1.0 To: paparazzi-devel@nongnu.org Subject: Re: [Paparazzi-devel] Procedures References: <538503.42596.qm@web51512.mail.re2.yahoo.com> <4A9568B4.5000504@ free.fr> <867915.3994.qm@web51512.mail.re2.yahoo.com> In-Reply-To: <867915.3994.qm@web51512.mail.re2.yahoo.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-imss-version: 2.5 X-imss-result: Passed X-imss-scores: Clean:31.40811 C:8 M:1 S:5 R:5 X-imss-settings: Baseline:1 C:1 M:1 S:1 R:1 (0.0000 0.0000) X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.4-2.6 X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Aug 2009 16:32:02 -0000 Hi, so I've fixed the include procedure feature. The wiki is updated and the conf/flight_plans/landing.xml example can be used with (to be put after the section in your flight plan) --Pascal Todd Sandercock wrote: > Thanks Pascal > > Makes sense why it wasn't working then. I'll ditch that idea for now. > Is there a way of including xml's in a flight plan? I don't actually > need the arguments and the position etc for the routines i want add so > just including an XML is what i was after > > Todd > > ------------------------------------------------------------------------ > *From:* Pascal Brisset > *To:* paparazzi-devel@nongnu.org > *Sent:* Thursday, 27 August, 2009 2:24:12 AM > *Subject:* Re: [Paparazzi-devel] Procedures > > Hi Todd, > > this feature has not been updated and tested ... for years. Some remarks: > - you file should start with > > -
is currently not allowed (according to the dtd) in a procedure > - the alt attribute of a waypoint must be a constant number. > Anyway, it won't work :-( > Currently, when a procedure is included, all the waypoints name of the > procedure are prefixed with the name of the procedure by the > preprocessing tool. So in your case, if I include your file with > > rotate="0"> > > > > the TARGET waypoint would be renamed into drop.TARGET. This renaming > is needed if you want to include several times the same procedure ( > with different arguments). But, you are referencing directly the > waypoint name from some C code (NavSetWaypointHere(WP_TARGET)) and the > procedure preprocessor is not able to look at this C code (to replace > WP_TARGET by WP_drop_TARGET). > So ... I don't know. > This preprocessor was written at a time when few C code was included > in flight plans. Now it is common, and there is no way to preprocess > it. A solution here would be to restrict procedure includes to one > single instance and get rid of the waypoint prefixing. > It probably requires deeper thinking > > --Pascal > > > Todd Sandercock wrote: > > Hi all > > i am just looking for some feedback on anyone that has got any > procedures to work properly. I have been working on some routines for > payload dropping and i wanted to put them in a procedure so that i > could use the same code over many flight plans. I am not sure how > limited procedures are but this is what i have written > > > > Thanks for any help > > Todd > > > > > >
> > #include "datalink.h" > > #include "bomb.h" > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > until="NavQdrCloseTo(DegOfRad(bomb_start_qdr)-10)" wp="BLEG"/> > > > > > > > > hmode="route" wp="RELEASE"/> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > ------------------------------------------------------------------------ > > Find local businesses and services in your area with Yahoo!7 Local. > Get started > <%20http://au.rd.yahoo.com/search/local/mailtagline/*http://local.yahoo.com.au>. > > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > Paparazzi-devel mailing list > > Paparazzi-devel@nongnu.org > > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > > > > > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > > ------------------------------------------------------------------------ > Find local businesses and services in your area with Yahoo!7 Local. > Get started > <%20http://au.rd.yahoo.com/search/local/mailtagline/*http://local.yahoo.com.au>. > > ------------------------------------------------------------------------ > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > From MAILER-DAEMON Fri Aug 28 12:32:07 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Mh4Mx-0003HU-4L for mharc-paparazzi-devel@gnu.org; Fri, 28 Aug 2009 12:32:07 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mh4Mv-0003FX-AT for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 12:32:05 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mh4Mq-000391-4P for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 12:32:04 -0400 Received: from [199.232.76.173] (port=40710 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mh4Mp-00038d-RG for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 12:31:59 -0400 Received: from mail-fx0-f211.google.com ([209.85.220.211]:50464) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Mh4Mp-00050T-FW for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 12:31:59 -0400 Received: by fxm7 with SMTP id 7so1784401fxm.34 for ; Fri, 28 Aug 2009 09:31:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:content-type :content-transfer-encoding; bh=8i4dEpS5opK5RlZdA/lZ6MMBJNHq2hijzBLNFfGxfrg=; b=ow4+pG/ttjVYYvEHNVINyw73GllhjqgRP3grzGRdVJzKq9OEphopJ8cj8Vur4qm/5h mcfga4JcwiWL9YxjfWEuaMkvZJBK5nG3y1a4Y3RN2dDklYZEnY0vY39xUJgMz4TZ/FXT yGgTX6QQTcyGNRSwOy2P/AT7iTQZahm/SVc2o= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; b=wxZqkBUm3rePmpRXL3OjmYG3IuFGm6dcqckUuPNvk83PpJyxOFYdeqUqK8NEneuVn0 uXz0PN4OQFBsyWGCRfPFqmMCpCQKA65Q335mb8H/cSCLNiDcJ2S3bas2J1bf+f3oOFVN cprqaaoqGjkwdJfGNLDvngcK/Ci6+Ec3a2C3M= Received: by 10.103.81.35 with SMTP id i35mr389715mul.43.1251477114704; Fri, 28 Aug 2009 09:31:54 -0700 (PDT) Received: from ?192.168.1.2? ([88.218.151.67]) by mx.google.com with ESMTPS id 23sm6519093mum.35.2009.08.28.09.31.52 (version=SSLv3 cipher=RC4-MD5); Fri, 28 Aug 2009 09:31:53 -0700 (PDT) Message-ID: <4A980675.6060409@gmail.com> Date: Fri, 28 Aug 2009 19:31:49 +0300 From: chris User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 To: paparazzi-devel@nongnu.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) Subject: [Paparazzi-devel] Reply to "Hello (Marian Cristina)" X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Aug 2009 16:32:06 -0000 >>I would like to ask if it is possible to write a letter by poste to an paparazzi.And i would like an addresse to where to write to.Thanks' ???????????????????????????????????????????????????????????? I am sorry but i don't understand what you say maybe i am missing something? Chris From MAILER-DAEMON Fri Aug 28 12:43:42 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Mh4YA-0005Et-ES for mharc-paparazzi-devel@gnu.org; Fri, 28 Aug 2009 12:43:42 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mh4Y9-0005EP-1Y for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 12:43:41 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mh4Y4-00059q-4e for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 12:43:40 -0400 Received: from [199.232.76.173] (port=60429 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mh4Y3-00059d-SW for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 12:43:36 -0400 Received: from mail-bw0-f227.google.com ([209.85.218.227]:54302) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Mh4Y3-0008LQ-6P for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 12:43:35 -0400 Received: by bwz27 with SMTP id 27so1784449bwz.34 for ; Fri, 28 Aug 2009 09:43:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:content-type :content-transfer-encoding; bh=pteeIH/iY9TWgNKT44nvmFKk41wiIKrKr6oA7n7yp5A=; b=Bog0Lswj3V6NfAHon9cqN8sFiXVHdGZaNABOcfvoSimvt+xbTfWUoUZXCR1v9IuVd1 Ws4hYFOYALnoqiYx7IZ7Kk29paJT2ghxZ9pkbAi6K3JS1bOXOWMcCQa27ElG603RpRR6 DZuqppue+Z7LoXqWUgcsQ/0+qCBv4snQ0LhBU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; b=YkzZgXSCIQLJp+BfcBsBPpEYTZG9S7e89yJBrsd8svNmZXQ3uW9w2haAAlUFuRY8r4 iNhmF1df8V3C2un14APQUYMRYgPdIRM3ubQ0FKpwnTKY2TWAhFwYqf3BYolwAtQUar/r SBEijS08GadtoGrWVL9So8Yyw3xpQRd8Mj8Bo= Received: by 10.103.126.7 with SMTP id d7mr398893mun.115.1251477813819; Fri, 28 Aug 2009 09:43:33 -0700 (PDT) Received: from ?192.168.1.2? ([88.218.151.67]) by mx.google.com with ESMTPS id 7sm6403925mup.49.2009.08.28.09.43.32 (version=SSLv3 cipher=RC4-MD5); Fri, 28 Aug 2009 09:43:32 -0700 (PDT) Message-ID: <4A980932.9030206@gmail.com> Date: Fri, 28 Aug 2009 19:43:30 +0300 From: chris User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 To: paparazzi-devel@nongnu.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) Subject: [Paparazzi-devel] How to descent faster? X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Aug 2009 16:43:41 -0000 Hi. I am having a peculiar problem where due to strong thermals the plane does not want to descent :-) even with the motor off and even when it does it does that very slowly. Any ideas? From MAILER-DAEMON Fri Aug 28 12:57:39 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Mh4lf-00019Q-Nt for mharc-paparazzi-devel@gnu.org; Fri, 28 Aug 2009 12:57:39 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mh4le-00019L-DP for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 12:57:38 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mh4la-000197-SK for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 12:57:38 -0400 Received: from [199.232.76.173] (port=43512 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mh4la-000194-Oj for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 12:57:34 -0400 Received: from mail-qy0-f203.google.com ([209.85.221.203]:35866) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Mh4la-0004VS-7U for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 12:57:34 -0400 Received: by qyk41 with SMTP id 41so1375644qyk.18 for ; Fri, 28 Aug 2009 09:57:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type; bh=mmkvX1HJm2+JDO6CyMCOGb8kcw/pa30SquwDg1aYWzA=; b=LqfEdjQyAIZu43N1FwHPozqgoP9sg+ZPI0sY40AIBKbgNOMOU8HO/niiViHSvRxhea UtclnjkzFxe5u4OrqY1kaA93Zp+4PG5i02I/zis34eMS2vzRRi/9CeDPkj3Vrzj3RUNr tjvY4Ic+pkCeHgRjGyq6LS7zy47dE7weUpOZg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=HUAsbcxec7fOmi/W+SDpOSSF2Lc0SDxue5kH9xqmX80ngr3Vb+jIhgLf2Ohw6cQdkJ gOVR+GKbAm8UJjPdHJTKT4uWNhb8znI+gWaANA3kErZfj43VKhOD7hcUuPkjcVZBxqkM h+1c5kn48lEuKwEY3WPPrc1q84eHO0FxzS65M= MIME-Version: 1.0 Sender: bubbajobob@gmail.com Received: by 10.224.71.233 with SMTP id i41mr1305277qaj.89.1251478652477; Fri, 28 Aug 2009 09:57:32 -0700 (PDT) In-Reply-To: <4A980932.9030206@gmail.com> References: <4A980932.9030206@gmail.com> Date: Fri, 28 Aug 2009 10:57:32 -0600 X-Google-Sender-Auth: 215af8edea734112 Message-ID: Subject: Re: [Paparazzi-devel] How to descent faster? From: Austin Jensen To: paparazzi-devel@nongnu.org Content-Type: multipart/alternative; boundary=00c09f8a4fe1866fcd04723694a7 X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Aug 2009 16:57:38 -0000 --00c09f8a4fe1866fcd04723694a7 Content-Type: text/plain; charset=ISO-8859-1 Were you loitering over a waypoint? We had this issue before and at the time we just sat and waited for it to decend (which took a really long time)! Afterwards, I thought that it would have been smart to just move the waypoint to either get the plane moving in a different pattern or to get it out of the thermal. Of course it didn't dawn on me when it mattered most... Austin ------------------------------------------------------------------ Austin Jensen, Research Engineer Utah Water Research Laboratory (UWRL) Utah State University, 8200 Old Main Hill Logan, UT, 84322-8200, USA E: Austin.Jensen@aggiemail.usu.edu T: (435)797-3315 On Fri, Aug 28, 2009 at 10:43 AM, chris wrote: > Hi. > I am having a peculiar problem where due to strong thermals the plane does > not want to > descent :-) even with the motor off and even when it does it does that very > slowly. > Any ideas? > > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > --00c09f8a4fe1866fcd04723694a7 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Were you loitering over a waypoint? We had this issue before and at the tim= e we just sat and waited for it to decend (which took a really long time)! = Afterwards, I thought that it would have been smart to just move the waypoi= nt to either get the plane moving in a different pattern or to get it out o= f the thermal. Of course it didn't dawn on me when it mattered most...<= br>
Austin

-------------------------------------------= -----------------------
Austin Jensen, Research Engineer
Utah Water R= esearch Laboratory (UWRL)
Utah State University, 8200 Old Main Hill
Logan, UT, 84322-8200, USA
E: Austin.Jensen@aggiemail.usu.edu
T: (435)797-3315


On Fri, Aug 28, 2009 at 10:43 AM, chris = <hendrixgr@gmai= l.com> wrote:
Hi.
I am having a peculiar problem where due to strong thermals the plane does = not want to
descent :-) even with the motor off and even when it does it does that very= slowly.
Any ideas?


_______________________________________________
Paparazzi-devel mailing list
Paparazzi-d= evel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/paparazzi-devel

--00c09f8a4fe1866fcd04723694a7-- From MAILER-DAEMON Fri Aug 28 13:13:25 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Mh50v-0000tO-C5 for mharc-paparazzi-devel@gnu.org; Fri, 28 Aug 2009 13:13:25 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mh50s-0000og-Pu for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 13:13:22 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mh50n-0000ge-Mv for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 13:13:22 -0400 Received: from [199.232.76.173] (port=45508 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mh50n-0000gD-EL for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 13:13:17 -0400 Received: from mail-gx0-f211.google.com ([209.85.217.211]:35423) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Mh50m-0007I8-I2 for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 13:13:17 -0400 Received: by gxk7 with SMTP id 7so3045962gxk.8 for ; Fri, 28 Aug 2009 10:13:14 -0700 (PDT) MIME-Version: 1.0 Sender: maik@zackbumm.biz Received: by 10.91.122.11 with SMTP id z11mr1079390agm.111.1251479594121; Fri, 28 Aug 2009 10:13:14 -0700 (PDT) In-Reply-To: <4A980675.6060409@gmail.com> References: <4A980675.6060409@gmail.com> From: =?UTF-8?B?TWFpayBIw7ZwZmVs?= Date: Fri, 28 Aug 2009 19:12:54 +0200 X-Google-Sender-Auth: 4afd6be8efc5eed7 Message-ID: Subject: Re: [Paparazzi-devel] Reply to "Hello (Marian Cristina)" To: paparazzi-devel@nongnu.org Content-Type: text/plain; charset=UTF-8 X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Aug 2009 17:13:23 -0000 Err, he or she wants to write snailmail to the Paparazzi project? Whatever it could be, it's probably interesting :) 2009/8/28 chris : >>>I would like to ask if it is possible to write a letter by poste to an >>> paparazzi.And i would like an addresse to where to write to.Thanks' > > ???????????????????????????????????????????????????????????? > I am sorry but i don't understand what you say maybe i am missing something? > Chris > > > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > From MAILER-DAEMON Fri Aug 28 15:04:32 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Mh6kR-0001Z7-PJ for mharc-paparazzi-devel@gnu.org; Fri, 28 Aug 2009 15:04:31 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mh6kO-0001SU-3Z for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 15:04:28 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mh6kJ-0001Lq-Dt for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 15:04:27 -0400 Received: from [199.232.76.173] (port=36936 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mh6kJ-0001LS-5S for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 15:04:23 -0400 Received: from mail-iw0-f175.google.com ([209.85.223.175]:62646) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Mh6kI-0008FD-FH for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 15:04:22 -0400 Received: by iwn5 with SMTP id 5so1116230iwn.4 for ; Fri, 28 Aug 2009 12:04:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=tW/LdrRzOEOImJag6IUisacTly2sCEQv/IhvzmvNBNI=; b=M4+LVZdchMHSq0sZ+BIv4wDby7k9fn9kyc5OspmsiFWO3hhQ3GLJRkBcjMskUhiBBm eIXGtx6iSMEAfDx3AroN0L4KoatXMRhwAmMRC58jqA1jghbcio15lNfHnRKgvi4HNMD0 bOIzI4v//w3foZtV/RO1EjHkT7mSKB8IrF948= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=j4K9I3uMO5PD/jO++wu7asS9IrFEQe023cLMnzVowTzaLZ43TiSqE6UJ/iF3CrtyDH fpVjpobVCw3/W35CdqkO6U1sz8Rt5BT0WXrcT45AOQvsoliD/BgDqNMj+oYot8qCsM2d hMWPbOD2wdCCPzmi1froZ56jHC/ymHzu+Zr/c= MIME-Version: 1.0 Received: by 10.231.83.75 with SMTP id e11mr956060ibl.11.1251486261466; Fri, 28 Aug 2009 12:04:21 -0700 (PDT) In-Reply-To: <4A978456.4010207@web.de> References: <4A978456.4010207@web.de> Date: Fri, 28 Aug 2009 12:04:21 -0700 Message-ID: Subject: Re: [Paparazzi-devel] Log parser for Matlab From: Roman Krashanitsa To: paparazzi-devel@nongnu.org Content-Type: multipart/alternative; boundary=000e0cd6aa060e55570472385a9f X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Aug 2009 19:04:28 -0000 --000e0cd6aa060e55570472385a9f Content-Type: text/plain; charset=ISO-8859-1 Hey Andreas, Nice job, very sleek and compact. I will try to repair the log parser on svn. Mine has a bit different scope, it has a gui and plotting/import/export capabilities. Roman 2009/8/28 Andreas Gaeb > Hello everybody, > > I've created a new Matlab log parser in case anybody is still working > with that for reviewing logs. It is a bit faster than PprzLogReader_1_0, > more flexible and can read any type of message present in a log file. It > has been tested with Matlab 7.1 and R2009a, so it should also work with > releases in between. Examples of usage are given in the file. > > I'll also be having a look at Roman Krashanitsa's log plotter GUI which > seems to be broken with actual SVN log files. > > I tried to upload the script to the wiki, but this seems to accept only > image files, so I'm attaching it here. Maybe someone can add it to the SVN. > > Regards, > Andreas > > function s = log2struct(logfilename) > % parse a PPRZ log file > %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% > % function s = log2struct(logfilename) > % Parses a log data file from the Paparazzi ground station into a > % Matlab variable. The log is sorted by aircraft ID and message ID. > % Parsing the log definition file (xx.log) is not required. > % > % Argument > % The name of the log data file to be parsed. > % May be omitted, in which case a file open dialog is used. > % > % Returns > % A struct of dimension 1 x nAircraft > % For each type of message received there is a substruct with the fields > % timestamp and contents as arrays over time. The columns of the contents > % array correspond to the message's data fields as defined in messages.xml. > % > % Example > % >> % 3D plot of the trajectory of aircraft #1 > % >> s = log2struct('09_08_26__14_18_29.data'); > % >> plot3(s(1).GPS.content(:,2), > s(1).GPS.content(:,3),s(1).GPS.content(:,5)) > % >> % what did the servos do? > % >> plot (s(1).ACTUATORS.timestamp, s(1).ACTUATORS.content) > % > % Known Bugs > % The method fails when the number of data elements for one message type > % changes during the log file, as may happen when the configuration file is > % changed in between or with arrays of variable size. > % > %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% > % > % Author: Andreas Gaeb > % Created: 27-Aug-2009 > % $Id$ > % > % Copyright (C) 2009 Andreas Gaeb > % > % This file is part of paparazzi. > % > % paparazzi is free software; you can redistribute it and/or modify > % it under the terms of the GNU General Public License as published by > % the Free Software Foundation; either version 2, or (at your option) > % any later version. > % > % paparazzi is distributed in the hope that it will be useful, > % but WITHOUT ANY WARRANTY; without even the implied warranty of > % MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the > % GNU General Public License for more details. > % > % You should have received a copy of the GNU General Public License > % along with paparazzi; see the file COPYING. If not, write to > % the Free Software Foundation, 59 Temple Place - Suite 330, > % Boston, MA 02111-1307, USA. > % > %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% > > persistent log2struct_old_working_dir > > % no arguments? open dialog > if nargin < 1 > [filename, pathname] = uigetfile(... > {'*.data', 'Paparazzi log data files (*.data)'}, ... > 'Open data file', ... > log2struct_old_working_dir); > if ~filename, return, end > logfilename = fullfile(pathname, filename); > log2struct_old_working_dir = pathname; > % display the filename for copy/paste > disp (['parsing ' logfilename '...']); > end > > fid = fopen(logfilename); > if fid == -1 > error('File %s not found', logfilename); > end > > try > % read everything as timestamp, A/C ID, msg name and msg contents > C = textscan(fid, '%f %u %s %[^\n]'); > > if isempty(C{1}) > error ('File %s does not seem to be a Paparazzi log data file.', > logfilename); > end > > timestamp = C{1}; > aircraftID = C{2}; > msgName = C{3}; > msgContent = C{4}; > > % find s which messages have been sent > uniqueMsgs = unique(msgName); > nMsg = size(uniqueMsgs,1); > > % find s which aircraft sent something > uniqueAC = unique(aircraftID); > nAC = size(uniqueAC,1); > > % distribute the messages to their sending aircraft > for iAC = nAC:-1:1 % counting backwards eliminates preallocation > % the ID of ith aircraft > acID = uniqueAC(iAC); > s(iAC).AIRCRAFT_ID = acID; > > % the indices of all messages send by ith aircraft > allMsgsFromThisAircraft = (aircraftID == uniqueAC(iAC)); > timestampFromThisAircraft = timestamp(allMsgsFromThisAircraft); > msgNameFromThisAircraft = msgName(allMsgsFromThisAircraft); > msgContentFromThisAircraft = msgContent(allMsgsFromThisAircraft); > > % for each message name > for iMsg = 1:nMsg > theMsgName = uniqueMsgs{iMsg}; > > % when was this special message sent by the ith aircraft? > thisMsgFromThisAircraft = strmatch(... > theMsgName, msgNameFromThisAircraft, 'exact'); > > % record with timestamp and contents > s(iAC).(theMsgName).timestamp = ... > timestampFromThisAircraft(thisMsgFromThisAircraft); > [s(iAC).(theMsgName).content, status] = str2num(char(... > msgContentFromThisAircraft(thisMsgFromThisAircraft))); %#ok > if ~status && ~strcmp(theMsgName, 'PONG') > warning('Paparazzi:log2struct:EmptyContent', ... > 'Could not read contents of %s message from aircraft #%i', ... > theMsgName, acID); > continue; > end > end > > end > > fclose (fid); > > catch theError > fclose(fid); > rethrow(theError); > end > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > > --000e0cd6aa060e55570472385a9f Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hey Andreas,
=A0
Nice job, very sleek and compact.
I will try to repair the log parser on svn. Mine has a bit different s= cope, it has a gui and plotting/import/export capabilities.
=A0
Roman

2009/8/28 Andreas Gaeb <a.gaeb@web.de>
Hello everybody,

I've= created a new Matlab log parser in case anybody is still working
with t= hat for reviewing logs. It is a bit faster than PprzLogReader_1_0,
more flexible and can read any type of message present in a log file. Ithas been tested with Matlab 7.1 and R2009a, so it should also work withreleases in between. Examples of usage are given in the file.

I'= ;ll also be having a look at Roman Krashanitsa's log plotter GUI which<= br> seems to be broken with actual SVN log files.

I tried to upload the = script to the wiki, but this seems to accept only
image files, so I'= m attaching it here. Maybe someone can add it to the SVN.

Regards, =A0 =A0 =A0 =A0Andreas

function s =3D= log2struct(logfilename)
% parse a PPRZ log file
%%%%%%%%%%%%%%%%%%%%= %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% function s =3D= log2struct(logfilename)
% Parses a log data file from the Paparazzi ground station into a
% Matl= ab variable. The log is sorted by aircraft ID and message ID.
% Parsing = the log definition file (xx.log) is not required.
%
% Argument
% The name of the log data file to be parsed.
% May be omitted, in which= case a file open dialog is used.
%
% Returns
% A struct of dimens= ion 1 x nAircraft
% For each type of message received there is a substru= ct with the fields
% timestamp and contents as arrays over time. The columns of the contents% array correspond to the message's data fields as defined in message= s.xml.
%
% Example
% >> % 3D plot of the trajectory of aircr= aft #1
% >> s =3D log2struct('09_08_26__14_18_29.data');
% >&g= t; plot3(s(1).GPS.content(:,2), s(1).GPS.content(:,3),s(1).GPS.content(:,5)= )
% >> % what did the servos do?
% >> plot (s(1).ACTUATOR= S.timestamp, s(1).ACTUATORS.content)
%
% Known Bugs
% The method fails when the number of data elements fo= r one message type
% changes during the log file, as may happen when the= configuration file is
% changed in between or with arrays of variable s= ize.
%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%= %%%%%
%
% Author: Andreas Gaeb
% Created: =A027-Aug-2009
% $Id$=
%
% Copyright (C) 2009 Andreas Gaeb
%
% This file is part of p= aparazzi.
%
% paparazzi is free software; you can redistribute it and/or modify% it under the terms of the GNU General Public License as published by
= % the Free Software Foundation; either version 2, or (at your option)
% any later version.
%
% paparazzi is distributed in the hope that it= will be useful,
% but WITHOUT ANY WARRANTY; without even the implied wa= rranty of
% MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. =A0See = the
% GNU General Public License for more details.
%
% You should have re= ceived a copy of the GNU General Public License
% along with paparazzi; = see the file COPYING. =A0If not, write to
% the Free Software Foundation= , 59 Temple Place - Suite 330,
% Boston, MA 02111-1307, USA.
%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%= %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

persistent log2struct_old_wor= king_dir

% no arguments? open dialog
if nargin < 1
=A0[file= name, pathname] =3D uigetfile(...
=A0 =A0{'*.data', 'Paparazzi log data files (*.data)'}, ...=
=A0 =A0'Open data file', ...
=A0 =A0log2struct_old_working_d= ir);
=A0if ~filename, return, end
=A0 =A0 =A0 =A0logfilename =3D full= file(pathname, filename);
=A0log2struct_old_working_dir =3D pathname;
=A0% display the filename fo= r copy/paste
=A0disp (['parsing ' logfilename '...']);end

fid =3D fopen(logfilename);
if fid =3D=3D -1
=A0error(&#= 39;File %s not found', logfilename);
end

try
=A0% read everything as timestamp, A/C ID, msg name and m= sg contents
=A0C =3D textscan(fid, '%f %u %s %[^\n]');

= =A0if isempty(C{1})
=A0 =A0error ('File %s does not seem to be a Pap= arazzi log data file.', logfilename);
=A0end

=A0timestamp =3D C{1};
=A0aircraftID =3D C{2};
=A0msgNa= me =3D C{3};
=A0msgContent =3D C{4};

=A0% find s which messages h= ave been sent
=A0uniqueMsgs =3D unique(msgName);
=A0nMsg =3D size(uni= queMsgs,1);

=A0% find s which aircraft sent something
=A0uniqueAC =3D unique(aircraftID);
=A0nAC =3D size(uniqueAC,1);

= =A0% distribute the messages to their sending aircraft
=A0for iAC =3D nA= C:-1:1 % counting backwards eliminates preallocation
=A0 =A0% the ID of = ith aircraft
=A0 =A0acID =3D uniqueAC(iAC);
=A0 =A0s(iAC).AIRCRAFT_ID =3D acID;
=A0 =A0% the indices of all messages send by ith aircraft
=A0 =A0allMs= gsFromThisAircraft =3D (aircraftID =3D=3D uniqueAC(iAC));
=A0 =A0timesta= mpFromThisAircraft =3D timestamp(allMsgsFromThisAircraft);
=A0 =A0msgNameFromThisAircraft =3D msgName(allMsgsFromThisAircraft);
=A0= =A0msgContentFromThisAircraft =3D msgContent(allMsgsFromThisAircraft);
=
=A0 =A0% for each message name
=A0 =A0for iMsg =3D 1:nMsg
=A0 =A0= =A0theMsgName =3D uniqueMsgs{iMsg};

=A0 =A0 =A0% when was this special message sent by the ith aircraft?=A0 =A0 =A0thisMsgFromThisAircraft =3D strmatch(...
=A0 =A0 =A0 =A0theM= sgName, msgNameFromThisAircraft, 'exact');

=A0 =A0 =A0% reco= rd with timestamp and contents
=A0 =A0 =A0s(iAC).(theMsgName).timestamp =3D ...
=A0 =A0 =A0 =A0timestam= pFromThisAircraft(thisMsgFromThisAircraft);
=A0 =A0 =A0[s(iAC).(theMsgNa= me).content, status] =3D str2num(char(...
=A0 =A0 =A0 =A0msgContentFromT= hisAircraft(thisMsgFromThisAircraft))); %#ok<ST2NM>
=A0 =A0 =A0if ~status && ~strcmp(theMsgName, 'PONG')
=A0= =A0 =A0 =A0warning('Paparazzi:log2struct:EmptyContent', ...
=A0= =A0 =A0 =A0 =A0'Could not read contents of %s message from aircraft #%= i', ...
=A0 =A0 =A0 =A0 =A0theMsgName, acID);
=A0 =A0 =A0 =A0continue;
=A0 =A0 =A0end
=A0 =A0end

=A0end
<= br>=A0fclose (fid);

catch theError
=A0fclose(fid);
=A0rethrow(= theError);
end

_______________________________________________Paparazzi-devel mailing list
Paparazzi-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/paparazzi-devel


--000e0cd6aa060e55570472385a9f-- From MAILER-DAEMON Fri Aug 28 17:17:43 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Mh8pL-00075T-GS for mharc-paparazzi-devel@gnu.org; Fri, 28 Aug 2009 17:17:43 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mh8pJ-00074Z-FJ for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 17:17:41 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mh8pE-00072e-PK for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 17:17:41 -0400 Received: from [199.232.76.173] (port=43911 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mh8pE-00072a-Ln for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 17:17:36 -0400 Received: from mail-bw0-f227.google.com ([209.85.218.227]:61206) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Mh8pE-00083K-AU for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 17:17:36 -0400 Received: by bwz27 with SMTP id 27so1918653bwz.34 for ; Fri, 28 Aug 2009 14:17:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:content-type :content-transfer-encoding; bh=gOx1swXtKFzaWmPtbNhDzNxEmIJAcas4WpS2KRenB8c=; b=fsp0G7V7l8qA25Tn6V2eGvFDIWxQK5cZnbVbKLHWOsXzazw6SC6THMDd7lnmPJ8jBL TQ5vkfeQtdfVPu4kGckkQHTGI82ADTnJ69PLZvuEGQYzaJF5N3AlmRGP0X250IYdgPfq 0c6rtO1sHMAdSjmep86oih/LhZNTxV8h9D57M= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; b=r/5IhzKjjiQ1Nr+o6Gew7KRc87lFgWCSy3xK5/gafzMOj9aixceC1Cr3Sq0Zmxiy71 P/7A16HeIS0OpvX7DzO34oHgybEd9Wa6/H1A1eQIUaH9+S2IIHXHRSszroOSzZ7O7bP3 v37nDktiCEujLfojd6pBrVjfjO4T9EkLUW5Jg= Received: by 10.102.235.5 with SMTP id i5mr573202muh.36.1251494255118; Fri, 28 Aug 2009 14:17:35 -0700 (PDT) Received: from ?192.168.1.2? ([88.218.151.67]) by mx.google.com with ESMTPS id s11sm9010976mue.11.2009.08.28.14.17.33 (version=SSLv3 cipher=RC4-MD5); Fri, 28 Aug 2009 14:17:34 -0700 (PDT) Message-ID: <4A98496C.9090105@gmail.com> Date: Sat, 29 Aug 2009 00:17:32 +0300 From: chris User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 To: paparazzi-devel@nongnu.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) Subject: [Paparazzi-devel] reply to " Re: How to descent faster? (Austin Jensen)" X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Aug 2009 21:17:41 -0000 That is exactly what i experienced also so i am trying to find a workable solution for the plane to handle descent when a thermal is present. Actually where i now fly thermals are the normal situation, there is nowhere to hide... The code does aggressive climb when the altitude error is big but it does not compensate for a plane that does not want to come down :-) Chris From MAILER-DAEMON Fri Aug 28 18:05:23 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Mh9ZT-0004rU-Iq for mharc-paparazzi-devel@gnu.org; Fri, 28 Aug 2009 18:05:23 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mh9ZR-0004n2-Qb for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 18:05:21 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mh9ZN-0004cm-SZ for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 18:05:21 -0400 Received: from [199.232.76.173] (port=46789 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mh9ZN-0004cW-OR for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 18:05:17 -0400 Received: from mailout05.t-online.de ([194.25.134.82]:53566) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Mh9ZN-0001gV-0k for paparazzi-devel@nongnu.org; Fri, 28 Aug 2009 18:05:17 -0400 Received: from fwd00.aul.t-online.de by mailout05.t-online.de with smtp id 1Mh9ZK-0006e9-02; Sat, 29 Aug 2009 00:05:14 +0200 Received: from cap10.localnet (TtqgzMZFrhpHvizfA--CriHFDf+ubyawI22K8vZAwVqO8B2IvFL4WXlQmlryYcLQfA@[217.227.8.146]) by fwd00.aul.t-online.de with esmtp id 1Mh9ZG-0YRmrY0; Sat, 29 Aug 2009 00:05:10 +0200 From: "Famille Chateauvieux-Hellwig" To: paparazzi-devel@nongnu.org Subject: Re: [Paparazzi-devel] reply to " Re: How to descent faster? (Austin Jensen)" Date: Sat, 29 Aug 2009 00:05:08 +0200 User-Agent: KMail/1.11.2 (Linux/2.6.28-15-generic; KDE/4.2.2; x86_64; ; ) References: <4A98496C.9090105@gmail.com> In-Reply-To: <4A98496C.9090105@gmail.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200908290005.09127.chawig@t-online.de> X-ID: TtqgzMZFrhpHvizfA--CriHFDf+ubyawI22K8vZAwVqO8B2IvFL4WXlQmlryYcLQfA X-TOI-MSGID: 8d055590-db16-4e19-b795-8da8a89b4747 X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 3) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Aug 2009 22:05:22 -0000 Le vendredi 28 ao=FBt 2009 23:17:32 chris, vous avez =E9crit : > That is exactly what i experienced also so i am trying to find a > workable solution > for the plane to handle descent when a thermal is present. > Actually where i now fly thermals are the normal situation, there is > nowhere to hide... > The code does aggressive climb when the altitude error is big but it > does not compensate > for a plane that does not want to come down :-) > Chris > > > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel Probably the safest way to come down is to stall. Stop the engine and pull = the=20 rudder 100%. It looks a bit wild, but the model won't accelerate so much th= at=20 it could break. That's the solution I use with 2 axis gliders not having ai= r=20 brakes. If you have yaw control you can engage a tail spin by adding full side rudd= er. To recover, just release the controls to 0%, or even push the elevator 100%= =20 for a second or so. first rengage the IR stabilisation when the GPS speed=20 (ideally pitot) is reasonable again. Take into account that recovering from= =20 the stall will cost you an extra 10-20m altitude. Martial From MAILER-DAEMON Sat Aug 29 06:10:07 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MhKsp-0006VJ-7u for mharc-paparazzi-devel@gnu.org; Sat, 29 Aug 2009 06:10:07 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MhKso-0006Uw-0D for paparazzi-devel@nongnu.org; Sat, 29 Aug 2009 06:10:06 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MhKsj-0006Se-6P for paparazzi-devel@nongnu.org; Sat, 29 Aug 2009 06:10:05 -0400 Received: from [199.232.76.173] (port=42433 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MhKsi-0006SO-Pm for paparazzi-devel@nongnu.org; Sat, 29 Aug 2009 06:10:00 -0400 Received: from mail-fx0-f211.google.com ([209.85.220.211]:35128) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MhKsi-0003Oh-GD for paparazzi-devel@nongnu.org; Sat, 29 Aug 2009 06:10:00 -0400 Received: by fxm7 with SMTP id 7so2129521fxm.34 for ; Sat, 29 Aug 2009 03:09:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:content-type :content-transfer-encoding; bh=EuAlmmfPlszbJ68P1CHGIRrkwEucj7K8Y4cZ3wNbbGs=; b=cSC+GhscuQbeIsM4yWnN3YHypbD38+kHvqeKmtnTXWwaPTf1OL+OvDiGgDHI9p4GE0 TN8T2CPc7+Tiq8JGC2oVF4dazzoRpTDraGyIAL+VXkApamxC2zGL6EtoxO9dJlJXltLI YyRmQtgAzFs9dPJhuczyt4Vb+jFocwEvnHnIg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; b=JikgkkVrwvDhl0LYXmmlJU4Id1fnYWYNujRtfdZC3P39HApc7aXbe4MyhPdU/bQDhC pp6GSnutU0oWELJ7qXn1wdQ6uc/hiBd4rXFI58FKxGUSszsbrCNkcOJGbO1n7cEEiIt9 y0wCSsjhh5+MQal41joUYqZOD9IVi5FgvAq0k= Received: by 10.103.202.3 with SMTP id e3mr889465muq.55.1251540599294; Sat, 29 Aug 2009 03:09:59 -0700 (PDT) Received: from ?192.168.1.2? ([88.218.151.67]) by mx.google.com with ESMTPS id t10sm10790136muh.30.2009.08.29.03.09.56 (version=SSLv3 cipher=RC4-MD5); Sat, 29 Aug 2009 03:09:58 -0700 (PDT) Message-ID: <4A98FE73.1030509@gmail.com> Date: Sat, 29 Aug 2009 13:09:55 +0300 From: chris User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 To: paparazzi-devel@nongnu.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) Subject: [Paparazzi-devel] constant speed navigation mode? X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Aug 2009 10:10:06 -0000 Hi. I was thinking if there is or can be done a navigation mode where the user can set a constant speed. What i want to do is to have the throttle automatically adjusted in order to keep a desired ground speed enroute to a waypoint. Chris From MAILER-DAEMON Sat Aug 29 06:16:35 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MhKz5-0000nr-P7 for mharc-paparazzi-devel@gnu.org; Sat, 29 Aug 2009 06:16:35 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MhKz2-0000mH-Vs for paparazzi-devel@nongnu.org; Sat, 29 Aug 2009 06:16:33 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MhKyx-0000j1-OP for paparazzi-devel@nongnu.org; Sat, 29 Aug 2009 06:16:32 -0400 Received: from [199.232.76.173] (port=59124 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MhKyx-0000ix-JB for paparazzi-devel@nongnu.org; Sat, 29 Aug 2009 06:16:27 -0400 Received: from mta-1.ms.rz.rwth-aachen.de ([134.130.7.72]:44395) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MhKyx-0004NU-72 for paparazzi-devel@nongnu.org; Sat, 29 Aug 2009 06:16:27 -0400 MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=ISO-8859-1 Received: from ironport-out-2.rz.rwth-aachen.de ([134.130.5.41]) by mta-1.ms.rz.RWTH-Aachen.de (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008)) with ESMTP id <0KP40048JV7C8Y00@mta-1.ms.rz.RWTH-Aachen.de> for paparazzi-devel@nongnu.org; Sat, 29 Aug 2009 12:16:24 +0200 (CEST) X-IronPort-AV: E=Sophos;i="4.44,296,1249250400"; d="scan'208";a="13146672" Received: from relay-1.ms.rz.rwth-aachen.de (HELO relay.rwth-aachen.de) ([134.130.7.74]) by ironport-in-2.rz.rwth-aachen.de with ESMTP; Sat, 29 Aug 2009 12:16:24 +0200 Received: from [134.130.150.40] (pc40.dynamik.RWTH-Aachen.DE [134.130.150.40]) by relay.rwth-aachen.de (8.13.8+Sun/8.13.8/1) with ESMTP id n7TAGO7A027877 for ; Sat, 29 Aug 2009 12:16:24 +0200 (CEST) Message-id: <4A98FFF1.4000408@web.de> Date: Sat, 29 Aug 2009 12:16:17 +0200 From: Andreas Gaeb User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) To: paparazzi-devel@nongnu.org Subject: Re: [Paparazzi-devel] Log parser for Matlab References: <4A978456.4010207@web.de> <4d39daa50908280616t6b82bbb2tdfff26195c66646a@mail.gmail.com> In-reply-to: <4d39daa50908280616t6b82bbb2tdfff26195c66646a@mail.gmail.com> X-detected-operating-system: by monty-python.gnu.org: Solaris 10 (beta) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Aug 2009 10:16:34 -0000 Rui Costa schrieb: > Good. Can you publish that information on wiki? Just did so, see at the bottom of http://paparazzi.enac.fr/wiki/Logs Regards, Andreas From MAILER-DAEMON Sat Aug 29 06:25:08 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MhL7M-0004y6-BN for mharc-paparazzi-devel@gnu.org; Sat, 29 Aug 2009 06:25:08 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MhL7K-0004xn-Rf for paparazzi-devel@nongnu.org; Sat, 29 Aug 2009 06:25:06 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MhL7F-0004wj-PK for paparazzi-devel@nongnu.org; Sat, 29 Aug 2009 06:25:06 -0400 Received: from [199.232.76.173] (port=47328 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MhL7F-0004wc-Dn for paparazzi-devel@nongnu.org; Sat, 29 Aug 2009 06:25:01 -0400 Received: from mx20.gnu.org ([199.232.41.8]:53315) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MhL7F-0006PM-2I for paparazzi-devel@nongnu.org; Sat, 29 Aug 2009 06:25:01 -0400 Received: from mta-2.ms.rz.rwth-aachen.de ([134.130.7.73]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MhL7D-0005KG-NB for paparazzi-devel@nongnu.org; Sat, 29 Aug 2009 06:24:59 -0400 MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=ISO-8859-1 Received: from ironport-out-1.rz.rwth-aachen.de ([134.130.5.40]) by mta-2.ms.rz.RWTH-Aachen.de (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008)) with ESMTP id <0KP400KC9VLKHZ00@mta-2.ms.rz.RWTH-Aachen.de> for paparazzi-devel@nongnu.org; Sat, 29 Aug 2009 12:24:56 +0200 (CEST) X-IronPort-AV: E=Sophos;i="4.44,296,1249250400"; d="scan'208";a="24069908" Received: from relay-1.ms.rz.rwth-aachen.de (HELO relay.rwth-aachen.de) ([134.130.7.74]) by ironport-in-1.rz.rwth-aachen.de with ESMTP; Sat, 29 Aug 2009 12:24:57 +0200 Received: from [134.130.150.40] (pc40.dynamik.RWTH-Aachen.DE [134.130.150.40]) by relay.rwth-aachen.de (8.13.8+Sun/8.13.8/1) with ESMTP id n7TAOu2X007149 for ; Sat, 29 Aug 2009 12:24:56 +0200 (CEST) Message-id: <4A9901F1.6070208@web.de> Date: Sat, 29 Aug 2009 12:24:49 +0200 From: Andreas Gaeb User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) To: paparazzi-devel@nongnu.org Subject: Re: [Paparazzi-devel] Log parser for Matlab References: <4A978456.4010207@web.de> In-reply-to: X-Detected-Operating-System: by mx20.gnu.org: Solaris 10 (beta) X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6, seldom 2.4 (older, 4) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Aug 2009 10:25:07 -0000 Hi Roman, Roman Krashanitsa schrieb: > I will try to repair the log parser on svn. Mine has a bit different scope, > it has a gui and plotting/import/export capabilities. I've already started adopting your GUI to use my parser and got the basic functions working again. I think I should have the whole thing converted within a week or so, so if you don't object, I'll go ahead with it and we don't have to do the same work twice. Regards, Andreas From MAILER-DAEMON Sat Aug 29 17:20:25 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MhVLU-00083h-VE for mharc-paparazzi-devel@gnu.org; Sat, 29 Aug 2009 17:20:24 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MhVLS-00082U-TB for paparazzi-devel@nongnu.org; Sat, 29 Aug 2009 17:20:22 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MhVLN-0007ye-Ca for paparazzi-devel@nongnu.org; Sat, 29 Aug 2009 17:20:21 -0400 Received: from [199.232.76.173] (port=56444 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MhVLN-0007yN-5N for paparazzi-devel@nongnu.org; Sat, 29 Aug 2009 17:20:17 -0400 Received: from mail-ew0-f223.google.com ([209.85.219.223]:37694) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MhVLM-0005ua-Sl for paparazzi-devel@nongnu.org; Sat, 29 Aug 2009 17:20:17 -0400 Received: by ewy23 with SMTP id 23so3397581ewy.8 for ; Sat, 29 Aug 2009 14:20:14 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.45.207 with SMTP id p57mr647237web.94.1251580814543; Sat, 29 Aug 2009 14:20:14 -0700 (PDT) Date: Sat, 29 Aug 2009 15:20:14 -0600 Message-ID: <5e20ac400908291420p1370debch126b28e3051ff38e@mail.gmail.com> From: Nicholas Wagner To: paparazzi-devel Content-Type: text/plain; charset=ISO-8859-1 X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) Subject: [Paparazzi-devel] Maiden Flight!! X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Aug 2009 21:20:23 -0000 Never happened. I was all set and ready to go and flipped the switch and burned out the switching regulator on the board... all of the servos are currently powered off of an ESC. What gives? 4S lipo 3580mah. Any ideas? Nick -- Nick Wagner Mechanical Engineering Colorado State University C: 970.631.2989 E: nawagner@rams.colostate.edu From MAILER-DAEMON Sat Aug 29 19:42:27 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MhXYx-0004Ou-OT for mharc-paparazzi-devel@gnu.org; Sat, 29 Aug 2009 19:42:27 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MhXYw-0004Op-O1 for paparazzi-devel@nongnu.org; Sat, 29 Aug 2009 19:42:26 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MhXYr-0004O8-Hy for paparazzi-devel@nongnu.org; Sat, 29 Aug 2009 19:42:25 -0400 Received: from [199.232.76.173] (port=39761 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MhXYr-0004O5-Eq for paparazzi-devel@nongnu.org; Sat, 29 Aug 2009 19:42:21 -0400 Received: from mail-fx0-f211.google.com ([209.85.220.211]:64071) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MhXYr-0001II-4u for paparazzi-devel@nongnu.org; Sat, 29 Aug 2009 19:42:21 -0400 Received: by fxm7 with SMTP id 7so2372397fxm.34 for ; Sat, 29 Aug 2009 16:42:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:content-type :content-transfer-encoding; bh=cawa0wibQo4mt/3VnL0pZR0a6SiL8XI3/aWizQ+QpkE=; b=u6FCiXNLayBSOVbq+Ac3UeO4GA4fwNMVg6L+XTH3yw+E3Qo0cxOTLyiITIdBR6XE3K nheKA3Rizz8GpfZMNpX+KjBPznzWWLDhBhYH4LkLZ3DZXnDUKcltUsgaCVxEAM1d/Cry J1MTWzGWUXtTxZjdTlw0KVR/aMjNDTQHAjj3I= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; b=NA2joA6EbzfczjRTpx1UA1f0u6CcQ6y/Ka2I5UIq0ecTfq0qHJg6TxoT0mAG34tzcK ZyszqKd0Ilx7f0KwqvrTcukGg8HYeqDQqFYk2gJ8LMEp27ktBngzI03BCXAmR+I5OnMe zR6r5WNaTT0n1lWquXP0tfVl72fYaXFldJsyY= Received: by 10.103.127.7 with SMTP id e7mr1216909mun.117.1251589339404; Sat, 29 Aug 2009 16:42:19 -0700 (PDT) Received: from ?192.168.1.2? ([88.218.148.2]) by mx.google.com with ESMTPS id u26sm15071999mug.54.2009.08.29.16.42.17 (version=SSLv3 cipher=RC4-MD5); Sat, 29 Aug 2009 16:42:18 -0700 (PDT) Message-ID: <4A99BCD8.40505@gmail.com> Date: Sun, 30 Aug 2009 02:42:16 +0300 From: chris User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 To: paparazzi-devel@nongnu.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) Subject: [Paparazzi-devel] Reply to "How to descent faster? (Famille Chateauvieux-Hellwig)" X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Aug 2009 23:42:27 -0000 That looks very interesting i will try it. You mean that during the full rudder the IR stabilization should be off if i understood correctly. How can i do this in the flight plan? Chris From MAILER-DAEMON Sat Aug 29 22:32:39 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MhaDf-00070z-O9 for mharc-paparazzi-devel@gnu.org; Sat, 29 Aug 2009 22:32:39 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MhaDd-0006w0-8e for paparazzi-devel@nongnu.org; Sat, 29 Aug 2009 22:32:37 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MhaDY-0006pf-Oa for paparazzi-devel@nongnu.org; Sat, 29 Aug 2009 22:32:36 -0400 Received: from [199.232.76.173] (port=43501 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MhaDY-0006pc-Hj for paparazzi-devel@nongnu.org; Sat, 29 Aug 2009 22:32:32 -0400 Received: from mail-yw0-f178.google.com ([209.85.211.178]:46850) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MhaDY-00020z-7o for paparazzi-devel@nongnu.org; Sat, 29 Aug 2009 22:32:32 -0400 Received: by ywh8 with SMTP id 8so3052956ywh.14 for ; Sat, 29 Aug 2009 19:32:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=2O533rVfvmdV5dZgsDFBzdxs3rancZvjT3a1xwrUGUI=; b=jqZFyBoHPa2YNKr8pFERO61J8Pky4Ut1hjyLGnkN+4JgW8Bi518cCkwlNeOrFytFPh BJ3W0S2hRpC4C3R8Xh5MoYq2QV3Vi5jpoKzkVVFRccwrzLCjHrIgtjKSMRRnAe812R9g mXuty/tW/SHHUOQeDli/52Fg+ViTEsXX38H2g= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=VjdYbJkeCiZLZTqCRd7iGNtlQSKrruCSedYBzSXFdhiSYG6o2pKI6gR0C9H0vUdLKp 4540eAuOvcmK6RuzkjawwYL1wpjV9lVi4AiC4p4LeE2/b9hxQfBhaf/ycC/5YRIM786O LBmGzt6tlu1SYQnvGNeW7GeEMHBrrTICxJTNg= MIME-Version: 1.0 Received: by 10.150.42.1 with SMTP id p1mr5638906ybp.15.1251599550937; Sat, 29 Aug 2009 19:32:30 -0700 (PDT) In-Reply-To: <4A9901F1.6070208@web.de> References: <4A978456.4010207@web.de> <4A9901F1.6070208@web.de> Date: Sat, 29 Aug 2009 19:32:30 -0700 Message-ID: Subject: Re: [Paparazzi-devel] Log parser for Matlab From: Roman Krashanitsa To: paparazzi-devel@nongnu.org Content-Type: multipart/alternative; boundary=00151743f922a27b89047252ba5f X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Aug 2009 02:32:38 -0000 --00151743f922a27b89047252ba5f Content-Type: text/plain; charset=ISO-8859-1 Sure, I don't mind. After all, this is an open project. 2009/8/29 Andreas Gaeb > Hi Roman, > > Roman Krashanitsa schrieb: > > I will try to repair the log parser on svn. Mine has a bit different > scope, > > it has a gui and plotting/import/export capabilities. > I've already started adopting your GUI to use my parser and got the > basic functions working again. I think I should have the whole thing > converted within a week or so, so if you don't object, I'll go ahead > with it and we don't have to do the same work twice. > > Regards, > Andreas > > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > --00151743f922a27b89047252ba5f Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Sure, I don't mind. After all, this is an open project.

2009/8/29 Andreas Gaeb <a.gaeb@web.de>
Hi Roman,

Roman Krashanit= sa schrieb:
> I will try to repair the log parser on svn. Mine has= a bit different scope,
> it has a gui and plotting/import/export cap= abilities.
I've already started adopting your GUI to use my pa= rser and got the
basic functions working again. I think I should have the whole thing
con= verted within a week or so, so if you don't object, I'll go aheadwith it and we don't have to do the same work twice.

Regards,<= br> =A0 =A0 =A0 =A0Andreas


_______________________________________________Paparazzi-devel mailing list
Paparazzi-devel@nongnu.org
http://lists.nongnu.org/= mailman/listinfo/paparazzi-devel

--00151743f922a27b89047252ba5f-- From MAILER-DAEMON Sun Aug 30 03:41:06 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Mhf29-0004Yk-Sj for mharc-paparazzi-devel@gnu.org; Sun, 30 Aug 2009 03:41:05 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mhf28-0004Xs-AZ for paparazzi-devel@nongnu.org; Sun, 30 Aug 2009 03:41:04 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mhf23-0004UU-Nc for paparazzi-devel@nongnu.org; Sun, 30 Aug 2009 03:41:03 -0400 Received: from [199.232.76.173] (port=35499 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mhf23-0004UR-HR for paparazzi-devel@nongnu.org; Sun, 30 Aug 2009 03:40:59 -0400 Received: from mx20.gnu.org ([199.232.41.8]:55565) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Mhf23-0004do-0N for paparazzi-devel@nongnu.org; Sun, 30 Aug 2009 03:40:59 -0400 Received: from mailout11.t-online.de ([194.25.134.85]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Mhf21-0006zE-3Z for paparazzi-devel@nongnu.org; Sun, 30 Aug 2009 03:40:57 -0400 Received: from fwd04.aul.t-online.de by mailout11.t-online.de with smtp id 1Mhf1y-0004bv-01; Sun, 30 Aug 2009 09:40:54 +0200 Received: from cap10.localnet (ZZ0paaZ1rhU3OKu5s3pF7AMEBHouIscLaMP2QZZ8Yz0sY9A5DOBL4QtLsD-OUSbgnX@[217.227.8.91]) by fwd04.aul.t-online.de with esmtp id 1Mhf1v-1cNOs40; Sun, 30 Aug 2009 09:40:51 +0200 From: "Famille Chateauvieux-Hellwig" To: paparazzi-devel@nongnu.org Subject: Re: [Paparazzi-devel] Reply to "How to descent faster? (Famille Chateauvieux-Hellwig)" Date: Sun, 30 Aug 2009 09:40:49 +0200 User-Agent: KMail/1.11.2 (Linux/2.6.28-15-generic; KDE/4.2.2; x86_64; ; ) References: <4A99BCD8.40505@gmail.com> In-Reply-To: <4A99BCD8.40505@gmail.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200908300940.50086.chawig@t-online.de> X-ID: ZZ0paaZ1rhU3OKu5s3pF7AMEBHouIscLaMP2QZZ8Yz0sY9A5DOBL4QtLsD-OUSbgnX X-TOI-MSGID: a05d6afa-13d0-4117-b363-5e24dd6360e2 X-Detected-Operating-System: by mx20.gnu.org: GNU/Linux 2.6 (newer, 3) X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6, seldom 2.4 (older, 4) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Aug 2009 07:41:04 -0000 Le dimanche 30 ao=FBt 2009 01:42:16 chris, vous avez =E9crit : > That looks very interesting i will try it. > You mean that during the full rudder the IR stabilization should be off > if i understood correctly. Yes, do not try to stablize anything during the descent. The model will=20 probably do wild figures. That's ok. The point is that it will fly very=20 inefficiently. My be you should expect a loss of GPS fix. It might be clever to keep this= =20 configuration olny for a fixed time (30-60s), then check where you are agai= n. > How can i do this in the flight plan? > Chris No clue. You'll probably have to define somtething new for paparazzi. I use= d=20 this method on regular gliders. My Horus (http://www.horus-uav-systems.de) = is=20 not good enough that I've had this kind of problems before... Another technique that works well for planes with elevators is to fly on th= e=20 back. It works if you have an asymetrical airfoil (Twinstar, easyglider,=20 Cularis...). On a paparazzi system this sould be only a question of exchang= ing=20 what is up and what is down... Here again, expect to loose GPS signal if yo= u=20 use a patch Antenna... Martial > > > > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel From MAILER-DAEMON Sun Aug 30 09:52:26 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MhkpW-0001Zx-KU for mharc-paparazzi-devel@gnu.org; Sun, 30 Aug 2009 09:52:26 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MhkpS-0001XG-KJ for paparazzi-devel@nongnu.org; Sun, 30 Aug 2009 09:52:22 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MhkpJ-0001RY-Ug for paparazzi-devel@nongnu.org; Sun, 30 Aug 2009 09:52:20 -0400 Received: from [199.232.76.173] (port=44352 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MhkpJ-0001Qv-7V for paparazzi-devel@nongnu.org; Sun, 30 Aug 2009 09:52:13 -0400 Received: from mail-fx0-f211.google.com ([209.85.220.211]:42103) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MhkpG-0004R2-TS for paparazzi-devel@nongnu.org; Sun, 30 Aug 2009 09:52:12 -0400 Received: by fxm7 with SMTP id 7so2581691fxm.34 for ; Sun, 30 Aug 2009 06:52:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:content-type :content-transfer-encoding; bh=veXTcFTnMNOFsg5gXD7AHLWlERM0fAk9xO2kNl0Wg0s=; b=nviCNOU1E6xt2rC6ds1P945mJSwIU3QhSJSFSIPKCbLWnxIRls6UDViMFT140Htzs8 C05JcP8LjhzLP+6CfuuEBFW0XBpXQd8yyHPpeE+8H2ZUvPFN1wZ7uGsnTZS7IuSptiU9 EbUEt+49KIKtthrpecbsLT/MNSJm5veoPhUgU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; b=Ypk/dHnsSQU+UiK40W3mIXucmmsiZgOqceEKywAa6Ptkrb1d/22X6lZ+shlxZApi16 usTboU4x5kqTzqs6JSOzUv1o1Jdv6E6RKrI1QcmDRq6zOZLn9b1698QVH8hsopre5PTj iUFVsa6kuUL8gOZjYsD6KmjTeRZMZGrNMZqBc= Received: by 10.103.76.34 with SMTP id d34mr1528489mul.31.1251640320448; Sun, 30 Aug 2009 06:52:00 -0700 (PDT) Received: from ?192.168.1.2? ([88.218.148.2]) by mx.google.com with ESMTPS id u9sm14132547muf.7.2009.08.30.06.51.57 (version=SSLv3 cipher=RC4-MD5); Sun, 30 Aug 2009 06:51:59 -0700 (PDT) Message-ID: <4A9A83FA.208@gmail.com> Date: Sun, 30 Aug 2009 16:51:54 +0300 From: chris User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 To: paparazzi-devel@nongnu.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) Subject: [Paparazzi-devel] auto take off and payload drop from 100m X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Aug 2009 13:52:23 -0000 How easier can be? http://www.youtube.com/watch?v=7B_F1CzGToM Payload drop, precision according to flight plan ~= 10m max. Release altitude = 100m AGL Of course if you spot the little red thing you can tell me also where to look :-) http://www.youtube.com/watch?v=lZ-zMzjKliI Have fun Chris From MAILER-DAEMON Sun Aug 30 12:13:12 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Mhn1k-0006dT-1L for mharc-paparazzi-devel@gnu.org; Sun, 30 Aug 2009 12:13:12 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mhn1d-0006a1-Sx for paparazzi-devel@nongnu.org; Sun, 30 Aug 2009 12:13:05 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mhn1Q-0006Pl-OM for paparazzi-devel@nongnu.org; Sun, 30 Aug 2009 12:13:00 -0400 Received: from [199.232.76.173] (port=41473 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mhn1Q-0006Pf-GI for paparazzi-devel@nongnu.org; Sun, 30 Aug 2009 12:12:52 -0400 Received: from smtp6-g21.free.fr ([212.27.42.6]:35705) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Mhn1N-00026N-Bj for paparazzi-devel@nongnu.org; Sun, 30 Aug 2009 12:12:52 -0400 Received: from smtp6-g21.free.fr (localhost [127.0.0.1]) by smtp6-g21.free.fr (Postfix) with ESMTP id 22FA7E080BD for ; Sun, 30 Aug 2009 18:12:31 +0200 (CEST) Received: from [192.168.0.10] (uni31-1-82-234-59-180.fbx.proxad.net [82.234.59.180]) by smtp6-g21.free.fr (Postfix) with ESMTP id CC222E08133 for ; Sun, 30 Aug 2009 18:12:28 +0200 (CEST) Message-ID: <4A9AA4ED.1070702@free.fr> Date: Sun, 30 Aug 2009 18:12:29 +0200 From: Pascal Brisset User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 To: paparazzi-devel@nongnu.org Subject: Re: [Paparazzi-devel] Reply to "How to descent faster? (Famille Chateauvieux-Hellwig)" References: <4A99BCD8.40505@gmail.com> <200908300940.50086.chawig@t-online.de> In-Reply-To: <200908300940.50086.chawig@t-online.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 3) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Aug 2009 16:13:09 -0000 Hi, this kind of procedure is available in=20 conf/flight_plans/grosslobke_demo.xml (from Martin): ground_alt + 220"/> stage_time"/> The trick is to set the h_ctl_disabled variable to disable=20 stabilization, put the aircraft in a spiral ... and restart the autopilot high enough from the ground. Of course, your=20 airframe has to handle it (it was the cause of one of the first crash=20 with Paparazzi: switching from a manual dive to auto1; Twinstar's wings=20 did not support the strong resulting pull) --Pascal Famille Chateauvieux-Hellwig wrote: > Le dimanche 30 ao=FBt 2009 01:42:16 chris, vous avez =E9crit : > =20 >> That looks very interesting i will try it. >> You mean that during the full rudder the IR stabilization should be of= f >> if i understood correctly. >> =20 > > Yes, do not try to stablize anything during the descent. The model will= =20 > probably do wild figures. That's ok. The point is that it will fly very= =20 > inefficiently. > > My be you should expect a loss of GPS fix. It might be clever to keep t= his=20 > configuration olny for a fixed time (30-60s), then check where you are = again. > > =20 >> How can i do this in the flight plan? >> Chris >> =20 > > No clue. You'll probably have to define somtething new for paparazzi. I= used=20 > this method on regular gliders. My Horus (http://www.horus-uav-systems.= de) is=20 > not good enough that I've had this kind of problems before... > > Another technique that works well for planes with elevators is to fly o= n the=20 > back. It works if you have an asymetrical airfoil (Twinstar, easyglider= ,=20 > Cularis...). On a paparazzi system this sould be only a question of exc= hanging=20 > what is up and what is down... Here again, expect to loose GPS signal i= f you=20 > use a patch Antenna... > > Martial > =20 >> >> >> _______________________________________________ >> Paparazzi-devel mailing list >> Paparazzi-devel@nongnu.org >> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel >> =20 > > > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > =20 From MAILER-DAEMON Sun Aug 30 12:32:40 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MhnKa-0001GD-7k for mharc-paparazzi-devel@gnu.org; Sun, 30 Aug 2009 12:32:40 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MhnKY-0001Fj-VY for paparazzi-devel@nongnu.org; Sun, 30 Aug 2009 12:32:39 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MhnKU-0001Es-4C for paparazzi-devel@nongnu.org; Sun, 30 Aug 2009 12:32:38 -0400 Received: from [199.232.76.173] (port=42423 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MhnKT-0001Ep-VO for paparazzi-devel@nongnu.org; Sun, 30 Aug 2009 12:32:34 -0400 Received: from basicbox10.server-home.net ([195.137.212.35]:55215) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MhnKS-0005XK-Qd for paparazzi-devel@nongnu.org; Sun, 30 Aug 2009 12:32:33 -0400 Received: by basicbox10.server-home.net (Postfix, from userid 1141) id 3C591C84974; Sun, 30 Aug 2009 18:32:27 +0200 (CEST) To: paparazzi-devel@nongnu.org Subject: =?ISO-8859-1?Q?Re: Re: [Paparazzi-de?= =?ISO-8859-1?Q?vel] Reply to "How to?= =?ISO-8859-1?Q? descent faster? (Fam?= =?ISO-8859-1?Q?ille Chateauvieux-Hel?= =?ISO-8859-1?Q?lwig)"?= From: martin@pfump.org X-Priority: 3 Importance: Normal X-MSMail-Priority: Normal X-MimeOLE: Produced by Confixx WebMail X-Mailer: Confixx WebMail (like SquirrelMail) Cc: MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <20090830163227.3C591C84974@basicbox10.server-home.net> Date: Sun, 30 Aug 2009 18:32:27 +0200 (CEST) X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 3) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Aug 2009 16:32:39 -0000 Hi, this spiral was used for two things. First thing is to get down fast in case the air traffic control tells you to (e.g. if the rescue helicopter on Svalbard would have to take off). The other thing was to get the aircraft down in a controlled way if the IR sensors would have failed. This procedure is intended for flying wings only (the Funjet). A "regular" aircraft like the Twinstar will go into rolls. Most important: make sure that you go through the "down_end" block if you want to leave and fly normal again. Otherwise the control loop will stay off even if leaving the block! There are gcs icons downdown and downdownend available. Martin Am 30.08.2009 um Uhr haben Sie geschrieben: > Hi, > > this kind of procedure is available in > conf/flight_plans/grosslobke_demo.xml (from Martin): > > > > > > > > > > > > > > > > > > > > > The trick is to set the h_ctl_disabled variable to disable > stabilization, put the aircraft in a spiral ... and > restart the autopilot high enough from the ground. Of course, your > airframe has to handle it (it was the cause of one of the first crash > with Paparazzi: switching from a manual dive to auto1; Twinstar's wings > did not support the strong resulting pull) > > --Pascal > > > > Famille Chateauvieux-Hellwig wrote: > > Le dimanche 30 août 2009 01:42:16 chris, vous avez écrit : > > > >> That looks very interesting i will try it. > >> You mean that during the full rudder the IR stabilization should be off > >> if i understood correctly. > >> > > > > Yes, do not try to stablize anything during the descent. The model will > > probably do wild figures. That's ok. The point is that it will fly very > > inefficiently. > > > > My be you should expect a loss of GPS fix. It might be clever to keep this > > configuration olny for a fixed time (30-60s), then check where you are > again. > > > > > >> How can i do this in the flight plan? > >> Chris > >> > > > > No clue. You'll probably have to define somtething new for paparazzi. I used > > > this method on regular gliders. My Horus (http://www.horus-uav-systems.de) is > > > not good enough that I've had this kind of problems before... > > > > Another technique that works well for planes with elevators is to fly on the > > > back. It works if you have an asymetrical airfoil (Twinstar, easyglider, > > Cularis...). On a paparazzi system this sould be only a question of > exchanging > > what is up and what is down... Here again, expect to loose GPS signal if you > > > use a patch Antenna... > > > > Martial > > > >> > >> > >> _______________________________________________ > >> Paparazzi-devel mailing list > >> Paparazzi-devel@nongnu.org > >> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > >> > > > > > > > > _______________________________________________ > > Paparazzi-devel mailing list > > Paparazzi-devel@nongnu.org > > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > > > > > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > > > From MAILER-DAEMON Sun Aug 30 12:49:44 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Mhnb6-0001rA-G1 for mharc-paparazzi-devel@gnu.org; Sun, 30 Aug 2009 12:49:44 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mhnb5-0001qt-55 for paparazzi-devel@nongnu.org; Sun, 30 Aug 2009 12:49:43 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mhnaz-0001oj-LX for paparazzi-devel@nongnu.org; Sun, 30 Aug 2009 12:49:41 -0400 Received: from [199.232.76.173] (port=52983 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mhnaz-0001og-FL for paparazzi-devel@nongnu.org; Sun, 30 Aug 2009 12:49:37 -0400 Received: from mailout02.t-online.de ([194.25.134.17]:40064) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Mhnay-0001Fg-QN for paparazzi-devel@nongnu.org; Sun, 30 Aug 2009 12:49:37 -0400 Received: from fwd02.aul.t-online.de by mailout02.t-online.de with smtp id 1Mhnax-0000B7-06; Sun, 30 Aug 2009 18:49:35 +0200 Received: from cap10.localnet (XdR2DTZJghzkLuWhB-KiJs85hs2YRXVivvAObXyXGaFUoNRbGfLUfB07K633DYhwEu@[217.227.11.226]) by fwd02.aul.t-online.de with esmtp id 1Mhnao-198ANM0; Sun, 30 Aug 2009 18:49:26 +0200 From: "Famille Chateauvieux-Hellwig" To: paparazzi-devel@nongnu.org Subject: Re: [Paparazzi-devel] Reply to "How to descent faster? ( =?iso-8859-1?q?Famille=09Chateauvieux-Hellwig?=)" Date: Sun, 30 Aug 2009 18:49:25 +0200 User-Agent: KMail/1.11.2 (Linux/2.6.28-15-generic; KDE/4.2.2; x86_64; ; ) References: <4A99BCD8.40505@gmail.com> <200908300940.50086.chawig@t-online.de> <4A9AA4ED.1070702@free.fr> In-Reply-To: <4A9AA4ED.1070702@free.fr> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200908301849.25438.chawig@t-online.de> X-ID: XdR2DTZJghzkLuWhB-KiJs85hs2YRXVivvAObXyXGaFUoNRbGfLUfB07K633DYhwEu X-TOI-MSGID: f52256df-24c2-467a-93ff-354dccabb831 X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 3) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Aug 2009 16:49:43 -0000 Le dimanche 30 ao=FBt 2009 18:12:29 Pascal Brisset, vous avez =E9crit : > Hi, > > this kind of procedure is available in > conf/flight_plans/grosslobke_demo.xml (from Martin): > > > > > > > > ground_alt + 220"/> > > > > > > > > stage_time"/> > > > > > The trick is to set the h_ctl_disabled variable to disable > stabilization, put the aircraft in a spiral ... and > restart the autopilot high enough from the ground. Of course, your > airframe has to handle it (it was the cause of one of the first crash > with Paparazzi: switching from a manual dive to auto1; Twinstar's wings > did not support the strong resulting pull) > > --Pascal > Hi Pascal, I'm not sure what the paparazzi command are. You probably do not need the=20 ailerons. Is 0.9*max_pprz pushing or pulling ? I would put the rudder to 100% right or left, and elevator up 100%. I mean= =20 100% of the servo range, not just the max pprz... a twinstar definitely sta= nds=20 this treatment, but you really want to have the "sticks in the corner" Martial From MAILER-DAEMON Mon Aug 31 02:49:09 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Mi0hR-0000Mv-7j for mharc-paparazzi-devel@gnu.org; Mon, 31 Aug 2009 02:49:09 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mi0hP-0000MJ-1V for paparazzi-devel@nongnu.org; Mon, 31 Aug 2009 02:49:07 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mi0hK-0000KG-A3 for paparazzi-devel@nongnu.org; Mon, 31 Aug 2009 02:49:06 -0400 Received: from [199.232.76.173] (port=44727 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mi0hJ-0000K1-Qg for paparazzi-devel@nongnu.org; Mon, 31 Aug 2009 02:49:01 -0400 Received: from mail-ew0-f223.google.com ([209.85.219.223]:40296) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Mi0hJ-00079F-6r for paparazzi-devel@nongnu.org; Mon, 31 Aug 2009 02:49:01 -0400 Received: by ewy23 with SMTP id 23so4183186ewy.8 for ; Sun, 30 Aug 2009 23:48:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=GUz8KOJANced5JcRguKjwwP+vBw7nPlXzTQRUqfOESI=; b=GMYG4esMHF3/Q8x6SkePcdJPVYBhlf8L4WOlv6/nP5eFxs84TjsFWqDbnUKyseuJwI v96SmPymgFsPJ/TlzkMyzlYk4bS5z7hJBDA+f7/wwMGOO5jsqRcvTEYr5Wg7bQhKRgYc tYClMUGRajt/DEHbSaefEP8uzq6Hk2Sb/AsAU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=GFZfSJ9dNQZGsauZ9/Kbpjv6+KfwPePocG+ZW2JauB3XAokBx9CNq8K+InMO6tDCae oicKtoCyMJbAaj3IkU/zberPLF7FKzOXfXsbdZGbcpCYGRF35BLKyySNelRmmzf0HC6h UZuyVJNr/BA9PnpDQUdoRjXmMBYFSpORNheZw= Received: by 10.216.1.81 with SMTP id 59mr996546wec.155.1251701338832; Sun, 30 Aug 2009 23:48:58 -0700 (PDT) Received: from ?192.168.1.11? (13-46.li.cytanet.com.cy [81.4.129.174]) by mx.google.com with ESMTPS id j8sm20302218gvb.5.2009.08.30.23.48.56 (version=SSLv3 cipher=RC4-MD5); Sun, 30 Aug 2009 23:48:58 -0700 (PDT) Message-ID: <4A9B72C2.4060300@gmail.com> Date: Mon, 31 Aug 2009 09:50:42 +0300 From: David Carlson User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 To: paparazzi-devel@nongnu.org Subject: Re: [Paparazzi-devel] Reply to "How to descent faster? ( Famille Chateauvieux-Hellwig)" References: <4A99BCD8.40505@gmail.com> <200908300940.50086.chawig@t-online.de> <4A9AA4ED.1070702@free.fr> <200908301849.25438.chawig@t-online.de> In-Reply-To: <200908301849.25438.chawig@t-online.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Aug 2009 06:49:07 -0000 If you do have a powered glider, the best way to lose a lot of altitude in a hurry without getting too much airspeed is to side-slip your airframe. This is actually really easy to do if you have a rudder (which most powered gliders do). Simply go into a loiter circle at a decent roll angle (> 30 degrees) and apply full opposite rudder. This is normally how I lose altitude if I don't have spoilers on my powered gliders and it works like a charm without the danger of snapping the wings. Buzz Famille Chateauvieux-Hellwig wrote: > Le dimanche 30 août 2009 18:12:29 Pascal Brisset, vous avez écrit : > >> Hi, >> >> this kind of procedure is available in >> conf/flight_plans/grosslobke_demo.xml (from Martin): >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> The trick is to set the h_ctl_disabled variable to disable >> stabilization, put the aircraft in a spiral ... and >> restart the autopilot high enough from the ground. Of course, your >> airframe has to handle it (it was the cause of one of the first crash >> with Paparazzi: switching from a manual dive to auto1; Twinstar's wings >> did not support the strong resulting pull) >> >> --Pascal >> >> > Hi Pascal, > > I'm not sure what the paparazzi command are. You probably do not need the > ailerons. Is 0.9*max_pprz pushing or pulling ? > I would put the rudder to 100% right or left, and elevator up 100%. I mean > 100% of the servo range, not just the max pprz... a twinstar definitely stands > this treatment, but you really want to have the "sticks in the corner" > Martial > > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > From MAILER-DAEMON Mon Aug 31 09:35:31 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Mi72h-0000kg-22 for mharc-paparazzi-devel@gnu.org; Mon, 31 Aug 2009 09:35:31 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mi72f-0000kQ-KH for paparazzi-devel@nongnu.org; Mon, 31 Aug 2009 09:35:29 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mi72Z-0000jL-Rf for paparazzi-devel@nongnu.org; Mon, 31 Aug 2009 09:35:28 -0400 Received: from [199.232.76.173] (port=46644 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mi72Z-0000jI-Ni for paparazzi-devel@nongnu.org; Mon, 31 Aug 2009 09:35:23 -0400 Received: from mta-2.ms.rz.rwth-aachen.de ([134.130.7.73]:60478) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Mi72Z-0005BE-36 for paparazzi-devel@nongnu.org; Mon, 31 Aug 2009 09:35:23 -0400 MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=ISO-8859-15 Received: from ironport-out-1.rz.rwth-aachen.de ([134.130.5.40]) by mta-2.ms.rz.RWTH-Aachen.de (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008)) with ESMTP id <0KP800LPZTQWPN80@mta-2.ms.rz.RWTH-Aachen.de> for paparazzi-devel@nongnu.org; Mon, 31 Aug 2009 15:35:20 +0200 (CEST) X-IronPort-AV: E=Sophos;i="4.44,305,1249250400"; d="scan'208";a="24232536" Received: from relay-1.ms.rz.rwth-aachen.de (HELO relay.rwth-aachen.de) ([134.130.7.74]) by ironport-in-1.rz.rwth-aachen.de with ESMTP; Mon, 31 Aug 2009 15:35:21 +0200 Received: from [134.130.150.40] (pc40.dynamik.RWTH-Aachen.DE [134.130.150.40]) by relay.rwth-aachen.de (8.13.8+Sun/8.13.8/1) with ESMTP id n7VDZKdC019918 for ; Mon, 31 Aug 2009 15:35:20 +0200 (CEST) Message-id: <4A9BD18B.5030107@web.de> Date: Mon, 31 Aug 2009 15:35:07 +0200 From: Andreas Gaeb User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) To: paparazzi-devel@nongnu.org X-detected-operating-system: by monty-python.gnu.org: Solaris 10 (beta) Subject: [Paparazzi-devel] Special characters in the log files X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Aug 2009 13:35:29 -0000 Hello everybody, I am trying to parse the log structure xml files (*.log in $PAPARAZZI_HOME/var/logs/) with Matlab's standard xml parser, which is basically an instance of the standard Java parser javax.xml.parsers.DocumentBuilderFactory. This parser fails with non-recoverable errors because the characters &, < and > show up inside attributes like e.g. in the lines or As a workaround it is of course possible to edit the *.log files by hand, but would it be possible for the future to replace these characters by & < and >, respectively? Thanks in advance. Regards, Andreas From MAILER-DAEMON Mon Aug 31 13:05:36 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MiAK0-0005m0-Pz for mharc-paparazzi-devel@gnu.org; Mon, 31 Aug 2009 13:05:36 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MiAJy-0005lI-Sn for paparazzi-devel@nongnu.org; Mon, 31 Aug 2009 13:05:34 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MiAJu-0005fZ-Dc for paparazzi-devel@nongnu.org; Mon, 31 Aug 2009 13:05:34 -0400 Received: from [199.232.76.173] (port=37792 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MiAJt-0005fH-II for paparazzi-devel@nongnu.org; Mon, 31 Aug 2009 13:05:29 -0400 Received: from mail-yx0-f178.google.com ([209.85.210.178]:41021) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MiAJt-0005RR-1g for paparazzi-devel@nongnu.org; Mon, 31 Aug 2009 13:05:29 -0400 Received: by yxe8 with SMTP id 8so905171yxe.19 for ; Mon, 31 Aug 2009 10:05:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=zr1J3vQmjkuWiH13Ga+2oFE7PTrqBI1JqHhtxAKO5kg=; b=CdlNV7rD1HgqzXl87sWHY+NRj+k5PBmaWdhNZQ5yJQkHm1jQJEQ/uz85/3Jv/tz+gq 7FUwy78xDn419hO3WMIcoJpwrHnKeH8gdXVTdGLYZP/P4UiBv8vBkdiXApaJEq/J8c2L HJqWtVBaTDIYuWdWUiTS53kkO306RREworZa4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=Mvo9yGGvSQh9vsYkLHBP11J6Vszzi3jYxMeV6LNgSxsZ8ncLwsRUe8JkGpAv2300R+ O+87j1M+9VdHWvi0VLUUd4MJNQfi4GhUf4e3ORsxvlv+fYfbMhLF/FTEpesf7DMrfsmX S6WpYm54tew9HJBxcIxFrkuSXhhRA44bqaG1Y= MIME-Version: 1.0 Received: by 10.150.100.12 with SMTP id x12mr8320395ybb.119.1251738328219; Mon, 31 Aug 2009 10:05:28 -0700 (PDT) In-Reply-To: <4A9BD18B.5030107@web.de> References: <4A9BD18B.5030107@web.de> Date: Mon, 31 Aug 2009 10:05:28 -0700 Message-ID: Subject: Re: [Paparazzi-devel] Special characters in the log files From: Roman Krashanitsa To: paparazzi-devel@nongnu.org Content-Type: multipart/alternative; boundary=000e0cd28a0a67c0b90472730a7a X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Aug 2009 17:05:35 -0000 --000e0cd28a0a67c0b90472730a7a Content-Type: text/plain; charset=ISO-8859-1 Andreas, try to just cut that part off, find the actual log in that file before parsing. Thats what I would do anyway. Roman 2009/8/31 Andreas Gaeb > Hello everybody, > > I am trying to parse the log structure xml files (*.log in > $PAPARAZZI_HOME/var/logs/) with Matlab's standard xml parser, which is > basically an instance of the standard Java parser > javax.xml.parsers.DocumentBuilderFactory. > This parser fails with non-recoverable errors because the characters &, > < and > show up inside attributes like e.g. in the lines > > UNTIL="NavQdrCloseTo(DegOfRad(baseleg_out_qdr)-10) && 10 > > fabs(estimator_z - WaypointAlt(WP__BASELEG))"/> > > or > > STRIP_BUTTON="Standby"> > > As a workaround it is of course possible to edit the *.log files by > hand, but would it be possible for the future to replace these > characters by & < and >, respectively? > > Thanks in advance. > > Regards, > Andreas > > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel > --000e0cd28a0a67c0b90472730a7a Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Andreas, try to just cut that part off, find the actual log in that fi= le before parsing.
=A0
Thats what I would do anyway.
=A0
Roman

2009/8/31 Andreas Gaeb <a.gaeb@web.de>
Hello everybody,

I am try= ing to parse the log structure xml files (*.log in
$PAPARAZZI_HOME/var/l= ogs/) with Matlab's standard xml parser, which is
basically an instance of the standard Java parser
javax.xml.parsers.Docu= mentBuilderFactory.
This parser fails with non-recoverable errors becaus= e the characters &,
< and > show up inside attributes like e.g= . in the lines

<circle WP=3D"_BASELEG" RADIUS=3D"nav_radius"UNTIL=3D"NavQdrCloseTo(DegOfRad(baseleg_out_qdr)-10) && 10 &g= t;
fabs(estimator_z - WaypointAlt(WP__BASELEG))"/>

or
=
<block NAME=3D"Standby" KEY=3D"<Control>a" STR= IP_ICON=3D"home.png"
STRIP_BUTTON=3D"Standby">
As a workaround it is of course possible to edit the *.log files byhand, but would it be possible for the future to replace these
characters by &amp; &lt; and &gt;, respectively?

Thanks = in advance.

Regards,
=A0 =A0 =A0 =A0Andreas


__________= _____________________________________
Paparazzi-devel mailing list
Paparazzi-devel@nongnu.org<= br> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel

--000e0cd28a0a67c0b90472730a7a-- From MAILER-DAEMON Mon Aug 31 16:35:00 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MiDad-0005Qx-KI for mharc-paparazzi-devel@gnu.org; Mon, 31 Aug 2009 16:34:59 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MiDaa-0005Ko-Ul for paparazzi-devel@nongnu.org; Mon, 31 Aug 2009 16:34:57 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MiDaW-0005AN-Nd for paparazzi-devel@nongnu.org; Mon, 31 Aug 2009 16:34:56 -0400 Received: from [199.232.76.173] (port=43295 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MiDaW-00059v-Fr for paparazzi-devel@nongnu.org; Mon, 31 Aug 2009 16:34:52 -0400 Received: from giove.ghostnet.de ([217.69.160.150]:36945 helo=adversum-it.de) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MiDaW-0003rK-1e for paparazzi-devel@nongnu.org; Mon, 31 Aug 2009 16:34:52 -0400 Received: from [192.168.200.49] (g230049114.adsl.alicedsl.de [92.230.49.114]) by adversum-it.de (Postfix) with ESMTP id 584204C4023 for ; Mon, 31 Aug 2009 22:34:33 +0200 (CEST) Message-ID: <4A9C33DA.1080903@drick.de> Date: Mon, 31 Aug 2009 22:34:34 +0200 From: Timo Drick User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 To: paparazzi-devel@nongnu.org Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) Subject: [Paparazzi-devel] Current sensor X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Aug 2009 20:34:57 -0000 Hi everybody, i am new to paparazzi and finally was able to get my twinstar flying with gps and all the autopilot stuff. I am very pleased with the system. Now i was able to connect a current sensor with one of the example airframe configuration and get this working and used for energy consumption measurement. I would like to display the actual current consumption of the plain at the GCS so i added the current to the BAT messages. Ok theoretically we can calculate the current consumption on the difference between energy messages and the time but i do not know how to implement this in the system any suggestions? Or i would propose to add the current to the BAT message in the SVN. If no current sensor is available the system returns the calculated current cosumption based on the throttle. I didn't find documentation for the integration of a current sensor on the wikipages. I will add the information but i am not sure to make a new page or should i just add the information to the airframe configuration wikipage at the BAT section. regards Timo From MAILER-DAEMON Mon Aug 31 21:19:56 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MiI2O-0001r0-7z for mharc-paparazzi-devel@gnu.org; Mon, 31 Aug 2009 21:19:56 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MiI2M-0001oW-9K for paparazzi-devel@nongnu.org; Mon, 31 Aug 2009 21:19:54 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MiI2G-0001jH-Ot for paparazzi-devel@nongnu.org; Mon, 31 Aug 2009 21:19:53 -0400 Received: from [199.232.76.173] (port=39689 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MiI2G-0001jE-LZ for paparazzi-devel@nongnu.org; Mon, 31 Aug 2009 21:19:48 -0400 Received: from eth2503.sa.adsl.internode.on.net ([150.101.238.198]:52346 helo=loki.acres.com.au) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MiI2G-0000eS-4f for paparazzi-devel@nongnu.org; Mon, 31 Aug 2009 21:19:48 -0400 Received: from localhost (localhost [127.0.0.1]) by loki.acres.com.au (Postfix) with ESMTP id C7BABF6B0 for ; Tue, 1 Sep 2009 10:50:21 +0930 (CST) Received: from loki.acres.com.au ([127.0.0.1]) by localhost (loki.acres.com.au [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Lk04x6yzNb6n for ; Tue, 1 Sep 2009 10:50:16 +0930 (CST) Received: from [192.0.2.159] (unknown [192.0.2.159]) by loki.acres.com.au (Postfix) with ESMTP id F338FA902 for ; Tue, 1 Sep 2009 10:50:15 +0930 (CST) Message-ID: <4A9C76A9.5090800@acres.com.au> Date: Tue, 01 Sep 2009 10:49:37 +0930 From: Steven Wawryk User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 To: paparazzi-devel@nongnu.org Subject: Re: [Paparazzi-devel] Special characters in the log files References: <4A9BD18B.5030107@web.de> In-Reply-To: <4A9BD18B.5030107@web.de> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. X-BeenThere: paparazzi-devel@nongnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paparazzi-devel@nongnu.org List-Id: paparazzi-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Sep 2009 01:19:54 -0000 Yeh, there don't seem to be many xml tools that parse these because they're not "well formed". Personally I try to use the LessThan(), And(), Or(), etc macros rather than <, >=, &&, ||, etc for this reason. Andreas Gaeb wrote: > Hello everybody, > > I am trying to parse the log structure xml files (*.log in > $PAPARAZZI_HOME/var/logs/) with Matlab's standard xml parser, which is > basically an instance of the standard Java parser > javax.xml.parsers.DocumentBuilderFactory. > This parser fails with non-recoverable errors because the characters &, > < and > show up inside attributes like e.g. in the lines > > UNTIL="NavQdrCloseTo(DegOfRad(baseleg_out_qdr)-10) && 10 > > fabs(estimator_z - WaypointAlt(WP__BASELEG))"/> > > or > > STRIP_BUTTON="Standby"> > > As a workaround it is of course possible to edit the *.log files by > hand, but would it be possible for the future to replace these > characters by & < and >, respectively? > > Thanks in advance. > > Regards, > Andreas > > > _______________________________________________ > Paparazzi-devel mailing list > Paparazzi-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel