Difference between revisions of "FAQ"
Jump to navigation
Jump to search
Line 22: | Line 22: | ||
==What equipment and components are suggested== | ==What equipment and components are suggested== | ||
:Linux (Debian or Ubuntu) compatible or Apple Macintosh notebook computer, preferably with a very bright screen for outdoor use. | :Linux (Debian or Ubuntu) compatible or Apple Macintosh notebook computer, preferably with a very bright screen for outdoor use. | ||
:Most any airframe that will accommodate | :Most any airframe that will accommodate a Paparazzi Autopilot and some extra weight and wiring - ''brushless motors are strongly suggested.'' See the [[Gallery|User's Gallery]] for some airframe examples. | ||
:[[Autopilots | :one of the [[Autopilots]] from one of the [[Get_Hardware|Paparazzi vendors]] or build your own from the downloadable plans/gerbers | ||
: | :if it is not already on the AP a external [[IMU]] | ||
:2.4 GHz R/C Transmitter and Receiver with a 3-position switch and PPM output for selecting Manual/Stabilized/Auto. | |||
:R/C Transmitter with a 3-position switch for selecting Manual/Stabilized/Auto. | |||
:A pair of [[Modems]] along with any enclosures and antennas | :A pair of [[Modems]] along with any enclosures and antennas | ||
:[http://www.mouser.com/search/ProductDetail.aspx?R=TTL-232R-3V3virtualkey62620000virtualkey626-DLP-TTL-232R-3V3 FTDI USB-TTL] cable for connecting the modem to your USB port and/or for serial flashing of bootloader code or tunnel access to the GPS receiver | :[http://www.mouser.com/search/ProductDetail.aspx?R=TTL-232R-3V3virtualkey62620000virtualkey626-DLP-TTL-232R-3V3 FTDI USB-TTL] cable for connecting the modem to your USB port and/or for serial flashing of bootloader code or tunnel access to the GPS receiver | ||
:A standard | :A standard Mini-B and Micro-B USB cable | ||
:Lots of [[Other_Hardware#Wiring|very durable wire, crimpers, and molex pins or pre-crimped wire.]] | :Lots of [[Other_Hardware#Wiring|very durable wire, crimpers, and molex pins or pre-crimped wire.]] | ||
Line 40: | Line 38: | ||
==Will the autopilot provide enough 5V power for many/large/digital servos as well as a modem, video TX, etc.?== | ==Will the autopilot provide enough 5V power for many/large/digital servos as well as a modem, video TX, etc.?== | ||
:Depends on the Autopilot, compare the maximum output of the AP and the needed power | |||
:The [[Tiny]] includes a high capacity and high efficiency switching voltage regulator intended to power servos, modems, video systems and other payloads. This regulator should be preferred to power the servos rather than a linear regulator. While linear regulators may be rated for several amps, they require a great deal of cooling and can easily overheat with only a few hundred milliamps of continuous current without cooling. By comparison, the switching regulator included on the Tiny can work continuously at 2A with little or no cooling. Be careful using high power or digital servos consuming a lot of current. If you use four or more of them on your airframe it is recommended to supply them separately. It is important to realize that the servos in any stabilized aircraft will operate continuously. Therefore a power supply that powers the servos reliably in manual flight may easily overheat or produce critical voltage drops in autonomous flight. | :The [[Tiny]] includes a high capacity and high efficiency switching voltage regulator intended to power servos, modems, video systems and other payloads. This regulator should be preferred to power the servos rather than a linear regulator. While linear regulators may be rated for several amps, they require a great deal of cooling and can easily overheat with only a few hundred milliamps of continuous current without cooling. By comparison, the switching regulator included on the Tiny can work continuously at 2A with little or no cooling. Be careful using high power or digital servos consuming a lot of current. If you use four or more of them on your airframe it is recommended to supply them separately. It is important to realize that the servos in any stabilized aircraft will operate continuously. Therefore a power supply that powers the servos reliably in manual flight may easily overheat or produce critical voltage drops in autonomous flight. | ||
Line 46: | Line 45: | ||
==Can I use a Sirf, Trimble, etc. instead of the u-Blox GPS receiver?== | ==Can I use a Sirf, Trimble, etc. instead of the u-Blox GPS receiver?== | ||
:Yes, but it would require a tremendous amount of work as some of the navigation code is dependent on some of the UBX messages. NMEA does not provide messages in the desired form and substantial calculation would be required for conversion. Any of the other proprietary protocols would work but you would need to write your own protocol handler. | :Yes, but it would require a tremendous amount of work as some of the navigation code is dependent on some of the UBX messages. NMEA does not provide messages in the desired form and substantial calculation would be required for conversion. Any of the other proprietary protocols would work but you would need to write your own protocol handler. u-Blox (starts at 20€) offers great performance, size, and speed as well as the ability to easily configure the internal Kalman filter parameters to expect significant acceleration in 3-D space - a very important feature. If you find a more capable receiver, let the group know about it, but this is not the place to save $40. | ||
==Does Paparazzi use DGPS, WAAS, EGNOS, or MSAS?== | ==Does Paparazzi use DGPS, WAAS, EGNOS, or MSAS?== | ||
Line 58: | Line 57: | ||
==Are PCM or 2.4GHz R/C systems compatible with Paparazzi?== | ==Are PCM or 2.4GHz R/C systems compatible with Paparazzi?== | ||
:Yes. | :Yes. Most good 2.4Ghz receivers can directly output a PPM signal on one servo pin. A general rule of thumb is that if you see any type of demultiplexer on your R/C receiver, you can look up the data sheet for it and likely tap into the input pin with success. Some information on compatible R/C receivers and how to find the PPM signal of your own receiver is given in the [[Other_Hardware#R.2FC_Receiver|RC receiver]] section. | ||
:If that's not possible, you can use the available PPM encoder board, to re-multiplex the servo channels into one PPM signal. This seems to be a common solution. | :If that's not possible, you can use the available PPM encoder board, to re-multiplex the servo channels into one PPM signal. This seems to be a common solution. | ||
Line 74: | Line 73: | ||
==What Electronic Speed Controllers (ESC) are compatible?== | ==What Electronic Speed Controllers (ESC) are compatible?== | ||
:Any controller can be used, the exact PWM value that is sent to the controller for 0-100% throttle is completely configurable in the airframe file so all controllers are compatible and any controller will arm properly with or without the use of an R/C transmitter. Upon each boot, the autopilot immediately sends whatever you have defined as 0% throttle (typically around 1200ms) and maintains that signal until a manual or autonomous command is given. Most modern controllers are "auto calibrating" which is an undesirable feature for R/C pilots and even more so for autonomous systems but can be dealt with. The calibration is done by defining the PWM value at boot to be 0% power and then defining some initial arbitrary mid-range value such as 1500ms to be 100% until a higher value is seen. The net result of this behavior is that the motor is given full power at any command above 50% throttle until 100% throttle has actually been commanded at least once. This is not an issue for planes that routinely take off at 100% throttle but can disrupt the throttle tuning and altitude control on any flights where 100% throttle has never been commanded. [http://www.castlecreations.com/products/products_fly.html Castle Creations Electronic Speed Controllers] can be configured for "fixed endpoints" so the ESC does not need to "learn" the endpoints at first takeoff this providing a consistent and predictable throttle response. By default this range 1250-1850ms but can be set at different values where needed. | :Any controller can be used, the exact PWM value that is sent to the controller for 0-100% throttle is completely configurable in the airframe file so all controllers are compatible and any controller will arm properly with or without the use of an R/C transmitter. Upon each boot, the autopilot immediately sends whatever you have defined as 0% throttle (typically around 1200ms) and maintains that signal until a manual or autonomous command is given. Most modern controllers are "auto calibrating" which is an undesirable feature for R/C pilots and even more so for autonomous systems but can be dealt with. The calibration is done by defining the PWM value at boot to be 0% power and then defining some initial arbitrary mid-range value such as 1500ms to be 100% until a higher value is seen. The net result of this behavior is that the motor is given full power at any command above 50% throttle until 100% throttle has actually been commanded at least once. This is not an issue for planes that routinely take off at 100% throttle but can disrupt the throttle tuning and altitude control on any flights where 100% throttle has never been commanded. [http://www.castlecreations.com/products/products_fly.html Castle Creations Electronic Speed Controllers] can be configured for "fixed endpoints" so the ESC does not need to "learn" the endpoints at first takeoff this providing a consistent and predictable throttle response. By default this range 1250-1850ms but can be set at different values where needed. | ||
: For quadrocopters a ESc with a very low latency is highly recomendet. That can be a cheap standard ESC with a upgraded firmware (which uses I2C as input) or a high quality esc (mocrocopter ESC) | |||
==Can traditional throttle stick programming be done on the ESC once connected to the autopilot?== | ==Can traditional throttle stick programming be done on the ESC once connected to the autopilot?== | ||
Line 84: | Line 86: | ||
==Can I solder wires directly to the autopilot instead of using the molex connectors?== | ==Can I solder wires directly to the autopilot instead of using the molex connectors?== | ||
: | :Depends on AP. Tiny: All of the molex headers are thru-hole and you can easily solder small gauge wire directly to the pins that protrude from these headers on the back of the board. It's important to note that '''standard servo wire cannot be soldered reliably''' in this fashion - you must use only high-grade wire intended for soldering (no vinyl insulation!). Direct soldering is not recommended, but it is possible ofcourse. See the [[Other_Hardware#Wiring|Wiring]] section for suggested wire types and sources. If you want to go the direct soldering path, be sure to you have '''excellent soldering skills''' and use high quality wiring. | ||
==What are the paparazzi failsafe features and how do I configure them?== | ==What are the paparazzi failsafe features and how do I configure them?== |
Revision as of 13:42, 3 October 2013
General Paparazzi FAQ
Is it possible to __________?
How can I contribute?
How do I check which Paparazzi Version I'm using
What equipment and components are suggested
Are internal combustion engines supported?
Can Paparazzi fly a glider?
Will the autopilot provide enough 5V power for many/large/digital servos as well as a modem, video TX, etc.?
Do I need a separate battery or regulator to isolate the autopilot, servos, video, modem, etc. from one another?
Can I use a Sirf, Trimble, etc. instead of the u-Blox GPS receiver?
Does Paparazzi use DGPS, WAAS, EGNOS, or MSAS?
How does the R/C receiver interface with the autopilot?
Why does Paparazzi tap directly into the R/C receiver instead of using individual servo signals?
Are PCM or 2.4GHz R/C systems compatible with Paparazzi?
What R/C transmitters are compatible?
Can a gamepad/joystick be used to control the aircraft through the modem?
What do MANUAL/AUTO1/AUTO2 stand for?
What Electronic Speed Controllers (ESC) are compatible?
Can traditional throttle stick programming be done on the ESC once connected to the autopilot?
Does Paparazzi support digital servos?
Can I solder wires directly to the autopilot instead of using the molex connectors?
What are the paparazzi failsafe features and how do I configure them?See Failsafe Why do I only get a blank (black) GCS
Why do I get a Failure("#of_world:no georef") when trying to load map tiles
How do I check if my telemetry is working?
Why don't I get a GPS position?
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 <subsystem name="gps" type="ublox_utm"/> in your airframe file, this will occur because the 5H module does not support UTM position.
Why do I get a CRITICAL **: murrine_style_draw_box: assertion `width >= -1' failed error message on starting the GCS
It is triggered by a bug in the Murrine GTK engine in combination with the default theme which Ubuntu uses, as detailed here: https://bugs.launchpad.net/ubuntu/+source/light-themes/+bug/538499 Do Paparazzi autopilots support onboard datalogging with an uSD or SD card?
Telemetry not working
|