- Jun 25, 2014
-
-
Bryant Mairs authored
-
Bryant Mairs authored
-
Bryant Mairs authored
-
Bryant Mairs authored
-
- Jun 23, 2014
-
-
Lorenz Meier authored
-
Lorenz Meier authored
-
- Jun 21, 2014
-
-
Lorenz Meier authored
-
- Jun 20, 2014
-
-
Lorenz Meier authored
Fix HIL link reconnect issues due to missing threading flag usage, warn user about missing config and take him to config view if necessary
-
- Jun 19, 2014
-
-
Lorenz Meier authored
-
Lorenz Meier authored
-
- Jun 16, 2014
-
-
Thomas Gubler authored
espeak: provide string length with 0 character, fixes problems with qgc reading out strange values/chars at the end of the sentence
-
Don Gagne authored
This way the delete happens on the right thread.
-
Don Gagne authored
-
Don Gagne authored
-
- Jun 15, 2014
-
-
Don Gagne authored
-
Bryant Mairs authored
-
Bryant Mairs authored
Current version was not as clear as it could be.
-
Bryant Mairs authored
Most math and backend storage was floats anyways, so most of these changes just half the data copied during function calls without reducing precision.
-
Bryant Mairs authored
Otherwise MANUAL_CONTROL messages are still sent at the regular 50Hz. This reduces transmission bandwidth from 0.9kbps when the joystick is used continuously to 0.1kbps when it's idle. To prevent possible issues from the last high-bandwidth message being lost and the system then not responding for .1s, the last messsage is double-transmit which should prevent those issues.
-
Thomas Gubler authored
-
Don Gagne authored
This allows other threads to signal
-
Don Gagne authored
-
- Jun 14, 2014
- Jun 13, 2014
-
-
Koen Kooi authored
Signed-off-by:
Koen Kooi <koen@dominion.thruhere.net>
-
Koen Kooi authored
Signed-off-by:
Koen Kooi <koen@dominion.thruhere.net>
-
treymarc authored
-
treymarc authored
-
- Jun 11, 2014
-
-
Bryant Mairs authored
-
Bryant Mairs authored
-
Bryant Mairs authored
-
Bryant Mairs authored
-
Bryant Mairs authored
-
Bryant Mairs authored
-
- Jun 10, 2014
-
-
Bryant Mairs authored
-
Bryant Mairs authored
Replaced with only 1 output message with the result of the first serial port scan.
-
Bryant Mairs authored
In the logplayer, the data stream is read ahead for messages, which is used to determine the size of the output bytearrays. Previously, this wasn't done correctly resulting in non-ideal behavior. Now, the next message is scanned properly, so the only bytearrays that are emitted from QGCMAVLinkLogPlayer are MAVLink messages in their entirety. This also has the benefit of skipping invalid/corrupted messages in the log that's being played back.
-
Bryant Mairs authored
-
- Jun 06, 2014
-
-
Don Gagne authored
-
- Jun 05, 2014
-
-
Don Gagne authored
-