- Jul 09, 2012
-
-
Lorenz Meier authored
Uas checks
-
Lorenz Meier authored
NMEA library and all references to NMEA have been removed.
-
- Jun 30, 2012
-
-
Jessica authored
-
- Jun 28, 2012
- Jun 12, 2012
-
-
Lorenz Meier authored
-
Lorenz Meier authored
-
Lorenz Meier authored
-
- Jun 07, 2012
-
-
Lorenz Meier authored
-
Lorenz Meier authored
-
Lorenz Meier authored
fixed waypoints with APM
-
- Jun 05, 2012
-
-
Andrew Tridgell authored
as long as the waypoint comes from the right systemID there is no point rejecting it based on component ID. The current_partner_compid is also completely wrong in the code, so checking it makes no sense anyway
-
- May 31, 2012
- May 30, 2012
-
-
pixhawk authored
-
- May 29, 2012
-
-
LM authored
-
- May 23, 2012
-
-
pixhawk authored
- May 15, 2012
-
-
Lorenz Meier authored
-
Lorenz Meier authored
Replaced the autopilot-specific inclusion of MAVLink to be more generic
-
- Apr 28, 2012
-
-
Lorenz Meier authored
-
Lorenz Meier authored
-
Lorenz Meier authored
-
Lorenz Meier authored
-
- Apr 27, 2012
-
-
LM authored
-
- Apr 26, 2012
-
-
Lorenz Meier authored
Unittesting fix
-
Lorenz Meier authored
Datalogger refactoring
-
- Apr 24, 2012
-
-
LM authored
-
- Apr 23, 2012
-
-
LM authored
-
- Apr 20, 2012
- Apr 19, 2012
-
-
James Goppert authored
-
James Goppert authored
-
Bryant Mairs authored
-
Bryant Mairs authored
-
Bryant Mairs authored
I had to update some method calls in UASUnitTest.cc. I'd bet that some of the tests are wrong now because of it.
-
Bryant Mairs authored
TODO: This should be altered to reuse stuff from qgroundcontrol.pro by including it instead of copy/paste.
-
- Apr 18, 2012
-
-
Bryant Mairs authored
Refactored the LogCompressor. It wasn't properly handling certain message logging files that mixed messages (Issue #70). One note is that this logger should work correctly as I've tested it, but could have some edge cases. It is pickier about the file format that it will sparse, but I don't know if the error-checking stuff from the old code would have actually worked. This can also be easily re-added. This code is also much faster than the old stuff. From what I could tell it scanned through the log file at least twice, I think three times. It also copied a lot of data into memory instead of reading, processing, and writing one line at a time, so memory use should be much lower. Some memory leaks from the old code were also refactored out, so lifetime memory use should be down.
-