paparazzi-devel
[Top][All Lists]
Advanced

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

Re: [Paparazzi-devel] execution


From: Felix Ruess
Subject: Re: [Paparazzi-devel] execution
Date: Mon, 14 Jun 2010 20:58:49 +0200

and that you have the correct autopilot set in your airframe file!!
Maybe you missed that.
In the makefile section, e.g.
CONFIG = \"tiny_2_1_1.h\"

On Mon, Jun 14, 2010 at 8:55 PM, Felix Ruess <address@hidden> wrote:
> Roman,
>
> I meant in the messages tool... (Tools -> messages)
> Your Xbees are not correctly set up it seems.
> Stick with one airframe and REALLY make sure your xbee baud rate
> settings are correct.
>
> Felix
>
> On Mon, Jun 14, 2010 at 8:48 PM, Roman Nikitin <address@hidden> wrote:
>> Felix,
>>
>> no, I have no messages in my GCS window which opens after I push the button 
>> "execute". Just a black window as I described before. I tried to flash 
>> another aircrafts they also didn't work. I have no idea where the problem 
>> is. The wires seems to be not damaged and the connections are also proved, 
>> everything on the places. The single point worrying me is that the "data In" 
>> light on the stand-alone modem (with usb connection) is never blinking. It 
>> means no incoming data to the stand-alone modem from air-born modem (board).
>>
>> Tomorrow I can try to prove the wires on the signals.
>>
>> I can´t believe that just me have such kind of problem.
>>
>> GUYS, some ideas?
>>
>> Regards,
>>
>> Roman
>>
>>
>> -----Ursprüngliche Nachricht-----
>> Von: address@hidden [mailto:address@hidden Im Auftrag von Felix Ruess
>> Gesendet: Montag, 14. Juni 2010 18:35
>> An: address@hidden
>> Betreff: Re: [Paparazzi-devel] execution
>>
>> Roman,
>>
>>> message tool says that everything is running.
>>
>> so you can see the messages coming in and changing, lots of green
>> blinking thingies?
>>
>>> The modems were set up to 9600 baud rate. The data in airframe file looks 
>>> like this
>>>
>>> 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.CFLAGS += -DGPS -DUBX -DUSE_UART0 -DGPS_LINK=Uart0 -DUART0_BAUD=B38400
>>>
>>> I tried to change the baud from 38400 to 9600, but it is still not working.
>>
>> You should be fine with 9600 baud then...
>> The GPS is configured for 38400 baud as you can see in the last line...
>>
>>> The same picture as I described it before. As I tried to load google map I 
>>> got the error
>>> Thread 1 killed on uncaught exception Failure("#of_world:no georef")
>>
>> It seems you still don't get messages in the gcs, are you really sure?
>>
>>> My sensors and my GPS are not arranged yet. Can it influence the process?
>>
>> No.
>>
>>
>>> -----Ursprüngliche Nachricht-----
>>> Von: address@hidden [mailto:address@hidden Im Auftrag von Felix Ruess
>>> Gesendet: Montag, 14. Juni 2010 16:39
>>> An: address@hidden
>>> Betreff: Re: [Paparazzi-devel] execution
>>>
>>> Roman,
>>>
>>> check with the messages tool if you receive any messages.
>>> But it sounds like your xbee configuration on the aircraft side is
>>> wrong, maybe wrong baud rate? Check that the baudrate in the airframe
>>> file you flashed matches the one you set your aircraft side xbee to.
>>>
>>> Felix
>>>
>>>
>>>
>>> _______________________________________________
>>> 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]