Common problems - Revision history

Flixr: redirect to FAQ

2011-01-29T02:07:35Z

redirect to FAQ

← Older revision		Revision as of 20:07, 28 January 2011
Line 1:		Line 1:
	~~<noinclude>~~		#REDIRECT [[FAQ]]
	~~{\| width="100%" style="border: solid 2px~~ #~~A3B1BF; background: #F5FAFF" \|~~
	\|-
	\|
	~~<h2 style="background-color:#cedff2; border-bottom:0px; border: 1px solid #a3b0bf; text-align:center; padding-top:4px;">Paparazzi FAQ - Common problems and solutions~~
	~~</h2></noinclude>~~
	~~<br/><!--TOC spacing-->~~
	~~__NOTOC__ __TOC__~~

	~~==I only get a blank (black) GCS==~~
	:The GCS stays blank until you get telemetry messages (either from the real aircraft or simulated) with the correct MD5 checksum meaning the autopilot has the correct and up to date flightplan/airframe/... programmed in it (in case of an MD5 problem you constantly get a lot of warnings in paparazzi center).
	~~:'''Solution''': Probably your telemetry is not set up correctly, this is most likely a~~ [[~~XBee configuration~~]] ~~issue.~~

	~~==I get a Failure("#of_world:no georef") when trying to load map tiles==~~
	~~:You get the georef error because the location is not initialized (probably GCS still blank and no aircraft are present). You can't get map tiles for nowhere...~~
	~~:'''Solution''': Set up your telemetry properly so you get messages from the aircraft OR start a simulation with the appropriate coordinates then load the map tiles.~~

	~~==How do I check if my telemetry is working?==~~
	~~:'''Solution''': Launch the link and messages tools in the Paparazzi Center. You should see the the messages coming in (blinking green) in the messages window.~~
	~~: You might need to adjust the device and baud-rate of the link according to your setup, e.g. <tt>link -d /dev/ttyUSB0 -s 57600</tt>~~
	~~: If you're stuck you can make ''link'' very verbose by setting the ''PPRZ_DEBUG'' environment variable to '' '*' ''~~

	~~==No GPS position==~~
	:'''Problem''': Your GPS seems to be working, but you cannot get a valid position fix. Speed and course are displayed correctly, though. Possibly you also see Invalid_argument("Latlong.of_utm") errors on the GCS log.

	~~This may happen if you have configured the wrong GPS subsystem for your Tiny board.~~
	~~If you have the LEA-5H module on your Tiny board, but have configured~~
	~~<tt><subsystem name="gps" type="ublox_lea4p"/></tt>~~
	~~in your airframe file, this will occur because the 5H module does not support UTM position.~~

	~~:'''Solution''': Change the gps type to "<tt>ublox_lea5h</tt>" or add a <tt><define name="GPS_USE_LATLONG"/></tt> flag.~~

	\|}

Agaeb: Added No GPS position item

2011-01-11T11:52:52Z

Added No GPS position item

← Older revision		Revision as of 05:52, 11 January 2011
Line 18:		Line 18:
	==How do I check if my telemetry is working?==		==How do I check if my telemetry is working?==
	:'''Solution''': Launch the link and messages tools in the Paparazzi Center. You should see the the messages coming in (blinking green) in the messages window.		:'''Solution''': Launch the link and messages tools in the Paparazzi Center. You should see the the messages coming in (blinking green) in the messages window.
	: You might need to adjust the device and baud-rate of the link according to your setup, e.g. link -d /dev/ttyUSB0 -s 57600		: You might need to adjust the device and baud-rate of the link according to your setup, e.g. <tt>link -d /dev/ttyUSB0 -s 57600</tt>
	: If you're stuck you can make ''link'' very verbose by setting the ''PPRZ_DEBUG'' environment variable to '' '*' ''		: If you're stuck you can make ''link'' very verbose by setting the ''PPRZ_DEBUG'' environment variable to '' '*' ''

			==No GPS position==
			:'''Problem''': Your GPS seems to be working, but you cannot get a valid position fix. Speed and course are displayed correctly, though. Possibly you also see Invalid_argument("Latlong.of_utm") errors on the GCS log.

			This may happen if you have configured the wrong GPS subsystem for your Tiny board.
			If you have the LEA-5H module on your Tiny board, but have configured
			<tt><subsystem name="gps" type="ublox_lea4p"/></tt>
			in your airframe file, this will occur because the 5H module does not support UTM position.

			:'''Solution''': Change the gps type to "<tt>ublox_lea5h</tt>" or add a <tt><define name="GPS_USE_LATLONG"/></tt> flag.

	\|}		\|}

Cdewagter: /* I only get a blank (black) GCS */

2010-08-12T07:08:09Z

I only get a blank (black) GCS

← Older revision		Revision as of 01:08, 12 August 2010
Line 9:		Line 9:

	==I only get a blank (black) GCS==		==I only get a blank (black) GCS==
	:The GCS stays blank until you get telemetry messages (either from the real aircraft or simulated).		:The GCS stays blank until you get telemetry messages (either from the real aircraft or simulated) with the correct MD5 checksum meaning the autopilot has the correct and up to date flightplan/airframe/... programmed in it (in case of an MD5 problem you constantly get a lot of warnings in paparazzi center).
	:'''Solution''': Probably your telemetry is not set up correctly, this is most likely a [[XBee configuration]] issue.		:'''Solution''': Probably your telemetry is not set up correctly, this is most likely a [[XBee configuration]] issue.

Poine: added

2010-08-10T17:59:20Z

added

← Older revision		Revision as of 11:59, 10 August 2010
Line 19:		Line 19:
	:'''Solution''': Launch the link and messages tools in the Paparazzi Center. You should see the the messages coming in (blinking green) in the messages window.		:'''Solution''': Launch the link and messages tools in the Paparazzi Center. You should see the the messages coming in (blinking green) in the messages window.
	: You might need to adjust the device and baud-rate of the link according to your setup, e.g. link -d /dev/ttyUSB0 -s 57600		: You might need to adjust the device and baud-rate of the link according to your setup, e.g. link -d /dev/ttyUSB0 -s 57600
			: If you're stuck you can make ''link'' very verbose by setting the ''PPRZ_DEBUG'' environment variable to '' '*' ''
	\|}		\|}

Flixr: /* I only get a blank (black) GCS */

2010-08-10T16:57:10Z

I only get a blank (black) GCS

← Older revision		Revision as of 10:57, 10 August 2010
Line 10:		Line 10:
	==I only get a blank (black) GCS==		==I only get a blank (black) GCS==
	:The GCS stays blank until you get telemetry messages (either from the real aircraft or simulated).		:The GCS stays blank until you get telemetry messages (either from the real aircraft or simulated).
	:'''Solution''': Probably your telemetry is not set up correctly, this is most likely a XBee configuration issue.		:'''Solution''': Probably your telemetry is not set up correctly, this is most likely a [[XBee configuration]] issue.

	==I get a Failure("#of_world:no georef") when trying to load map tiles==		==I get a Failure("#of_world:no georef") when trying to load map tiles==

Flixr: added problems faq

2010-08-10T16:52:00Z

added problems faq

New page

<noinclude>
{| width="100%" style="border: solid 2px #A3B1BF; background: #F5FAFF" |
|-
|
<h2 style="background-color:#cedff2; border-bottom:0px; border: 1px solid #a3b0bf; text-align:center; padding-top:4px;">Paparazzi FAQ - Common problems and solutions
</h2></noinclude>
<br/>
__NOTOC__ __TOC__

==I only get a blank (black) GCS==
:The GCS stays blank until you get telemetry messages (either from the real aircraft or simulated).
:'''Solution''': Probably your telemetry is not set up correctly, this is most likely a XBee configuration issue.

==I get a Failure("#of_world:no georef") when trying to load map tiles==
:You get the georef error because the location is not initialized (probably GCS still blank and no aircraft are present). You can't get map tiles for nowhere...
:'''Solution''': Set up your telemetry properly so you get messages from the aircraft OR start a simulation with the appropriate coordinates then load the map tiles.

==How do I check if my telemetry is working?==
:'''Solution''': Launch the link and messages tools in the Paparazzi Center. You should see the the messages coming in (blinking green) in the messages window.
: You might need to adjust the device and baud-rate of the link according to your setup, e.g. link -d /dev/ttyUSB0 -s 57600

|}