paparazzi-devel
[Top][All Lists]
Advanced

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

Re: [Paparazzi-devel] Missing Makefile.arm7 ?


From: David Conger
Subject: Re: [Paparazzi-devel] Missing Makefile.arm7 ?
Date: Fri, 08 Oct 2010 13:00:54 -0700

Hi Martin,

Thank you. I apologize for being lazy and not digging more. I really appreciate 
yours and Felix help with it. 

Guess what? My friend Urivan and I flew yesterday a near perfect flight. He 
setup a complex flight plan with auto take-off, line navigation between points, 
holding circles, survey, figure 8 and auto landing. It flew amazingly. Takeoff 
and the entire flight was flawless. Only on the last turn for landing I wanted 
to manually land as we were in a very tight on space for the landing. If left 
alone we both agreed quite likely it would have landed just fine. 

I'm so impressed with Paparazzi. Just how once you get it setup on the bench 
properly it just flies so precisely. On the GCS replay it was so precisely on 
the lines and curves exactly. Our turns were 50m radius which it did easily. It 
did lose some altitude during sharp turns but recovered quickly. The terrain 
was not flat at all and IR worked just fine. I'm glad it did on replay I saw i 
lost RC signal many times during the flight. RC is really not needed anymore 
for us. I completely trust the autopilot now after that flight. 

Thank you everyone who wrote and contribute to this incredible autopilot. To 
imagine it is free and open is a dream come true. 

-David
On Oct 8, 2010, at 11:31 AM, Martin Mueller wrote:

> Hi David,
> 
> the conf/autopilot/tiny.makefile still had the arm7 instead of the lpc21 for 
> ARCHI. That made the command line building of tunnel and usb_tunnel_X fail. 
> Maybe the tunnel should be made in a different way now? Changed it to lpc21 
> and the command line works again.
> 
> Martin
> 
> On 08.10.2010 20:01, David Conger wrote:
>> Hi Felix,
>> 
>> Ah, ok. I did not realize that. So if I moved the conf.xml and had SVN bring 
>> down a new one this should solve it?
>> 
>> David
>> On Oct 7, 2010, at 7:44 AM, Felix Ruess wrote:
>> 
>>> Hi David,
>>> 
>>> the default airframes should be up to date. They are in
>>> conf.xml.example. But they only get copied to conf.xml if you don't
>>> already have one. Meaning it will work if you just made a new checkout
>>> and hence don't have your own conf.xml with old airframes.
>>> 
>>> So you should update your conf.xml and through out the old ones and
>>> replace them with the up-to-date examples. Or just delete your
>>> conf.xml, let it be created again and then add your own airframes
>>> again...
>>> 
>>> Maybe we could change it so that the conf.xml.example is included
>>> automatically and you only put your own airframes in conf.xml which is
>>> not under version control. Then the examples would always be up to
>>> date.
>>> 
>>> Cheers, Felix
>>> 
>>> On Thu, Oct 7, 2010 at 4:32 PM, David Conger<address@hidden>  wrote:
>>>> Hello,
>>>> 
>>>> This is interesting. I was using the commands I always use and that are on 
>>>> the WIki for programming the u-blox using the tunnel. I run make at the 
>>>> command line but used the MJ5 airframe which is one of the default ones. I 
>>>> guess the fault is in the MJ5 airframe file?
>>>> 
>>>> It would be nice to have a default airframe files and custom airframe 
>>>> files. The defaults always being updated when the code changes. Although 
>>>> I'm not new and will make the changes required for someone new we should 
>>>> make an experience where following the commands on the Wiki or choosing 
>>>> defaults in the menu just work. I suppose it means when changes like this 
>>>> are made someone also changes the defaults as well.  With so many airframe 
>>>> files now that's not practical hence my suggestion to limit or separate 
>>>> them into default and custom or other or ?
>>>> 
>>>> Thank you Felix for helping. I will make the changes. To quickly solve my 
>>>> issue I just reverted SVN using: svn update -r 5920
>>>> 
>>>> -David
>>>> On Oct 7, 2010, at 3:58 AM, Felix Ruess wrote:
>>>> 
>>>>> Hi David,
>>>>> 
>>>>> the Makefile.arm7 is obsolete, we now have the more consistent
>>>>> Makefile.lpc21 for the tiny.
>>>>> 
>>>>> are you still using the old makefile section or did you switch to the
>>>>> new firmware/subsystems already?
>>>>> That sounds like you still use the old way and then you would have to
>>>>> adapt your makefile section.
>>>>> 
>>>>> If you use firmware/subsystems you should have something like this in
>>>>> your airframe file:
>>>>> 
>>>>>  <firmware name="setup">
>>>>>    <target name="tunnel"   board="tiny_2.11"/>
>>>>>  </firmware>
>>>>> 
>>>>> When you set the board it will automatically call the right Makefile
>>>>> for that architecture.
>>>>> (In this case $(TARGET).ARCHDIR is set to lpc21 in the
>>>>> tiny_2.11.makefile and then the correct Makefile.lpc21 will be called)
>>>>> 
>>>>> Cheers, Felix
>>>>> 
>>>>> On Thu, Oct 7, 2010 at 6:30 AM, David Conger<address@hidden>  wrote:
>>>>>> I tried to program the tunnel into a Tiny2.11 tonight and get:
>>>>>> make[1]: Entering directory `/home/dconger/paparazzi3/sw/airborne'
>>>>>> Makefile:38: ../../conf/Makefile.arm7: No such file or direct
>>>>>> 
>>>>>> Sure enough the file isn't found anywhere. I did see it in a backup SVN 
>>>>>> and a change 2 weeks ago from flixr saying "moved arm7 directory to 
>>>>>> arch/lpc21 and set most makefiles accordingly" ...
>>>>>> 
>>>>>> Do I need to fix a Makefile somewhere?
>>>>>> 
>>>>>> -David
>>>>>> 
>>>>>> _______________________________________________
>>>>>> Paparazzi-devel mailing list
>>>>>> address@hidden
>>>>>> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel
>>>>>> 
>>>>> 
>>>>> _______________________________________________
>>>>> Paparazzi-devel mailing list
>>>>> address@hidden
>>>>> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel
>>>> 
>>>> 
>>>> _______________________________________________
>>>> Paparazzi-devel mailing list
>>>> address@hidden
>>>> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel
>>>> 
>>> 
>>> _______________________________________________
>>> Paparazzi-devel mailing list
>>> address@hidden
>>> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel
>> 
>> 
>> _______________________________________________
>> Paparazzi-devel mailing list
>> address@hidden
>> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel
> 
> 
> _______________________________________________
> Paparazzi-devel mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel




reply via email to

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