* Updated aggie air configs
* Updated configs and some small compilation fixes
* Added layouts and control_panel updates
* An example with a new flight plan. Note the plane doesn't fly very well because of the model mismatch.
* Adding bebop to my own conf file
* Added Bebop 2 OF to my conf file
* Introducing an exponentially decaying gain and a rework of the optical flow landing module
* Fixed code style, set parameters to standard optical flow control, tested everything on Bebop 2.
* Implemented all remarks, placing function definitions in the c-file, getting the state properly, getting the time properly, making div_factor a setting.
* Set minimum of D-gain to 0
* [rtcm] RTK with UBlox8 modules
based on #1902, with fragmentation of packets to fit in RF modems if
necessary
* fix warnings
* [pprzlink] update pprzlink for RXMRTCM message
* [rtcm] add missing files
* [sdlog] update sdlog for chibios
- fix several small bugs
- update to fatfs 0.12b
- add status report
* calculate mass storage thread size accordingly to ffconf choice for _USE_LFN and _FS_EXFAT
* [sdlog] improved documentation
* [nps] add angle of attack and sideslip to NPS
* [module] extra_dl can work with nps
* [module] add sideslip sensor to aoa_pwm module and fix apogee board file
* [module] add wind estimation module
This module is an experimental wind estimation filter based on UKF that
aims at estimating all 3 local wind components in real-time.
It is based on ChibiOS as the algorithm runs in a dedicated thread.
The algorithm itself is generated from a Matlab/Simulink model.
* [tool] read Meso-NH meteo data and feed NPS with wind information
* [module] remove nps target from extra_dl, uart not well supported on FW
* [mesonh] remove unused UDP interface
* [chibios] add compilation error message for wind estimator module
* update INDI tu use full control effecitvens matrix
Instead of using commands (roll, pitch, yaw, thrust), give the
controller direct control over all actuators.
This allows for online individual actuator control effectiveness
estimation and inversion, as well as better saturation handling.
The INDI controller as it was previous is renamed to 'simple'.
* Made INDI more flexible wrt number of actuators
- 4x4 matrix inverse to accomodate the thrust axis as well
- support for more actuators
- cleanup of code
* Change filters guidance indi to butterworth
* Added body acceleration to state interface
* Better adaptation and guidance thrust increment
- Adaptation flexible wrt. number of actuators.
- Added adaptation of the specific force effectiveness of the actuators.
- Added connection to guidance INDI through ABI. The thrust increment is
caclulated in guidance INDI and sent to the stabilization.
* lower case variables
* change filter of indi to butterworth
* INDI fix array index & no declarations in for loop
- Also added doxygen comments
* Added actuators_pprz
the array actuators is used to drive the servos, so a new array to store
the command to the actuators in pprz scale is needed
* Removed hardcoded scaling
Fixed the velocity messages (using the correct variables)
Works for PX4FLOW mounted as described here: https://pixhawk.org/modules/px4flow
Option to use i2c or UART to get data from PX4FLOW
Sends debug messages (maybe make optional if needed).
* pprzlink updated to master
* guidance vector field module
* sin trajectory, forgot a minus sign...
* xml files for GVF
* control/gvf.xml not needed anymore
* added some structs for settings and placing gvf_variables into structs
* demo flight plan for testing the settings of the GVF
* style fixed
* trigonometry calculations made only once
* syntax fixed
* pprzlink updated
* added defines and improved description in the module .xml
* module only works for fixedwing (so far)
* FlighGear and Ivy thread working
* Main loop replaced with main_thread
* Cleaned up nps_main
* HITL main - test TX with Vectornav
* Added AggieAir control panel
* [modules] Flight logger module added
* [fixedwing] Airframe configuration updated
* [hitl] Proof Of Concept - IO and simulation running
* [nps] Minor changes in main hitl
* [nps] Performance Test with Pthread library
* [hitl] Working with pthreads instead of glib threads
* [hitl] Minor updates
* [nps] Refactoring to get rid of Gthreads
* [nps] Minor changes, added mutex guards
* [nps] Minor Ivy fix
* [nps] Threads working properly
[hitl] Ins separated
* [hitl] Check for launch variable
* [nps] Refactoring makefile into common and hitl/sitl specific
* [hitl] Hitl works, sitl too
* [hitl] ins_vectornav comments
* [hitl] Updated launch routine
* [nps_hitl Cleaned up version of NPS/HITL
- added support for ACTUATORS message (Rotorcraft)
- resolved start issue for Fixedwing (works fine now)
- minor improvements in threads (fg_thread, ap_init)
* [nps] Minor fixes to save current work
* [nps] Minor fixes
* Update to latest pprzlink
* FlighGear and Ivy thread working
* Main loop replaced with main_thread
* Cleaned up nps_main
* HITL main - test TX with Vectornav
* Added AggieAir control panel
* [modules] Flight logger module added
* [fixedwing] Airframe configuration updated
* [hitl] Proof Of Concept - IO and simulation running
* [nps] Minor changes in main hitl
* [nps] Performance Test with Pthread library
* [hitl] Working with pthreads instead of glib threads
* [hitl] Minor updates
* [nps] Refactoring to get rid of Gthreads
* [nps] Minor changes, added mutex guards
* [nps] Minor Ivy fix
* [nps] Threads working properly
[hitl] Ins separated
* [hitl] Check for launch variable
* [nps] Refactoring makefile into common and hitl/sitl specific
* [hitl] Hitl works, sitl too
* [hitl] ins_vectornav comments
* [hitl] Updated launch routine
* [nps_hitl Cleaned up version of NPS/HITL
- added support for ACTUATORS message (Rotorcraft)
- resolved start issue for Fixedwing (works fine now)
- minor improvements in threads (fg_thread, ap_init)
* [nps] Minor fixes to save current work
* [nps] Minor fixes
* Update to latest pprzlink
* Fixed the feed function
* Compilation fixes
* More compilation fixes
* Last compilation fixes
* Added a simple automated flight plan (auto take off and landing)
* Fixes in NPS
* Removed SBUS fakerator
* Removed superfluous "else"
* Renamed "flight recorder" to "xgear"
* Fixed formatting
* Updated extra_dl module
* Initial support for extra_dl to run over USB serial
* Fixed usb_serial for extra_dl
* extra_dl_periodic() called at TELEMETRY_FREQUENCY
This pull request is for the guidance algorithms used to control hybrid drones like the Quadshot and MavShot. It supports autonomous waypoint navigation as well as "forward-flight". The code was flight tested in autonomous waypoint navigation mode, including autonomous landing (using sonar).
The module attribute for a message was used to only include that message in the generated periodic telemetry if that module was loaded.
This is not needed anymore with the register_periodic_telemetry() funtions as unregistered messages are simply not sent.
see #1674
First PR for getting Pixhawk to play nice with PPRZ.
The Pixhawk can be flashed without external tools (i.e. no JTAG interface is needed). Instead, the PX4 bootloader is kept in place and used by pprz to flash both the AP (stm32f4) and FBW (stm32f1) devices. One important remark is that for the FBW device, currently the computer needs to be connected to the Telem2 port using a FTDI cable. This is because pprz does not support serial communication over USB, or so I've heard.
In any case, the Iris+ drone factory equipped with a Pixhawk flies both on INDI and PID in ATT mode. However, PPRZ currently uses the MPU6000 IMU, which was broken in my Iris+ (and there are indications that maybe in others Iris' and X8's as well). I had to replace it with a fresh Pixhawk.
Also tested with a Pixhawk clone: seems to work just as well.
closes#1551
- if a mavlink process is specified in the telemetry file, use that, otherwise fall back to fixed message periods
- print warning if telemety file has no mavlink process
- fix code style
in the telemetry xml file a type can be specified for the process (default is "pprz").
You can also set "mavlink" and use mavlink messages, which will be sent as specified if the mavlink module is loaded and that mavlink message is registered there.
This module provides a tool for high-speed logging where weight- and size-limitations play part.
It only requires a micro-SD card which is soldered directly to the SPI-bus, for example on a lisa/s.
The logger is activated by flipping a switch on the transmitter. Up to 42 logs can be recorded during one session (battery kept connected). The data remains on the card when the battery is disconnected, so that you can replace the battery before downloading data to the computer. Previous logs will be overwritten as soon as the first log is initiated after boot.
The messages to be logged can be selected in the telemetry config file, under the Logger process. Next to that, it is possible to call pprz_msg_send_xxx from anywhere in the code, using a reference to the sdlogger.
See also http://wiki.paparazziuav.org/wiki/SDLogger_SPI_Direct