the SRTM download page now redirects to https
so enable support for TLS
needs the Debian/Ubuntu package libocamlnet-ssl-ocaml-dev
only load tls lib if netclient version > 4
The function quat_from_rpy_cmd_i does not seem to act as desired.
The quat_int controller uses simple conversion from eulers, which works
intuitively on a test case, so this one is preferred.
- dedicated swing without mag
- strip code before upload
- read battery and baro from sysfs
- read power button by hand and restart
- needs to be plugged to enable telnet, can be disconnected after upload
Implement trilateration algorithm for positionning using the
UltraWideBand modules DW1000 from Decawave.
The interface with the modules is done with an arduino using the low
level library https://github.com/thotro/arduino-dw1000 with some
modifications.
The data extraction and trilateration are working, calibration and real
flight have not been done at the moment.
* WLS control allocation
* comments, and configure preferred act values
* keep option open to use pseudo-inverse
* add link to burkardt
* Simplify input reset if not flying
* qr solve in math folder
Use INDI_NUM_ACT and INDI_OUTPUTS instead of hardcoded numbers.
Fix code style
* Removed hardcoded number of actuators
precompute number of thrusters
* 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.
* [GVF] more functions exposed to the user
* [GVF] gvf_line_xy1_xy2 added
* [GVF] segment msg added for the GCS
* poly survey with GVF
* [GVF] segment primitive added
* integrating gvf and poly survey
* [GVF] each trajectory has its own gains now
* updated settings (gains) for the GVF trajectories
* [GVF] nav_survey_polygon integrated with GVF
* [GVF] python scripts updated for the new GVF msg format
* pprz c code style
* [GVF] updated demo
* gvf demo includes poly survey
* [GVF] gvf poly survey moved to gvf module
* [GVF] nav module not necessary anymore for gvf demo
* [GVF] _gvf added for being different from others nav functions from other modules
* [GVF] description about employing gvf here has been removed
* gvf_ for not conflict with former nav module
* These definitions now have to be done in the airframe conf
* [GVF] kn is not used anymore by the gvf visualization
* [GVF] better description msg for the formation script
* [GVF] Doxygen doc
* print for python 3
* correct style
* we set up correctly the vertical control
* Doxygen
* Only for auto2. If we are in auto1, do not override the roll set point
* Circular formation now also works for counter-clockwise direction
* update pprzlink
* Gautier comments
* [GVF] more functions exposed to the user
* [GVF] gvf_line_xy1_xy2 added
* [GVF] segment msg added for the GCS
* poly survey with GVF
* [GVF] segment primitive added
* integrating gvf and poly survey
* [GVF] each trajectory has its own gains now
* updated settings (gains) for the GVF trajectories
* [GVF] nav_survey_polygon integrated with GVF
* [GVF] python scripts updated for the new GVF msg format
* pprz c code style
* [GVF] updated demo
* gvf demo includes poly survey
* [GVF] gvf poly survey moved to gvf module
* [GVF] nav module not necessary anymore for gvf demo
* [GVF] _gvf added for being different from others nav functions from other modules
* [GVF] description about employing gvf here has been removed
* gvf_ for not conflict with former nav module
* These definitions now have to be done in the airframe conf
* [GVF] kn is not used anymore by the gvf visualization
* [GVF] better description msg for the formation script
* [GVF] Doxygen doc
* print for python 3
* correct style
* we set up correctly the vertical control
* Doxygen
* Only for auto2. If we are in auto1, do not override the roll set point
* Circular formation now also works for counter-clockwise direction
* update pprzlink
* Gautier comments
* PPRZ_MODE_AUTO2 is now AP_MODE_AUTO2
* new functions for the GVF demo
* Primitives for tracking lines, segments and segment_loops
* Poly survey track the proper segment function
- Corners are now detected in the previous frame(instead of the new one) and tracked to the new one
- A feature management method is available where corners are kept in memory for as long as they are tracked
- Corners can be weighted against the number of times they have been tracked
- Fast9 detection will be performed again after the number of tracked corners drops below a threshold is met and
only in the regions of the image that have the less corners (optional)
Gautier Hattenberger
Kirk Scheper
kevindehecker
OpenUAS
Michal Podhradsky
HooperFly
Felix Ruess
Ewoud Smeur
Hector Garcia de Marina
Manos Kyriakakis