- 28 Mar, 2015 1 commit
-
-
Don Gagne authored
Link ids were being used interchangeably with the mavlink channel for the link. Link ids handed out as a numerically increasing integer. Once the counter went past MAVLINK_COMM_NUM_BUFFERS all hell would break loose and cause memory corruption.
-
- 22 Mar, 2015 1 commit
-
-
Don Gagne authored
Also many LinkManager API changes to further isolate all link management inside LinkManager.
-
- 25 Feb, 2015 1 commit
-
-
dogmaphobic authored
Also fixed a typo (copy/paste error) in the TCP link settings loading where it was using the UDP port as the default value instead of the TCP port.
-
- 18 Feb, 2015 1 commit
-
-
dogmaphobic authored
-
- 14 Feb, 2015 1 commit
-
-
dogmaphobic authored
I noticed that some times, the disconnect signal would get to the updateConnect button (tool bar) before the link was physically disconnected. That would cause it to count it as a still connected link and get the connect button logic out of sync. While at it, added an interface to the UDP link to return its configuration instance. That allows the LinkManager to unlink it when disconnecting it.
-
- 13 Feb, 2015 1 commit
-
-
dogmaphobic authored
The goal of this first installment is to organize the code a bit so it's more readable, clean up a bit of left over cruft, and manage link configurations (and links in general).
-
- 24 Nov, 2014 1 commit
-
-
Don Gagne authored
Centralize all connecting and disconnecting of links through LinkManager::[Connect|Disconnect]Link api. Connect/Disconnect no longer allowed through LinkInterface. This allows creation of new LinkManager::setConnections[Suspended|Allowed] methods to disallow connections as needed.
-
- 03 Nov, 2014 1 commit
-
-
Don Gagne authored
This api doesn’t make any sense given the fact that LinkInterface signals bytesReceived with the bytes in the signal. Also the reason why it is never called!
-
- 01 Jul, 2014 1 commit
-
-
Bryant Mairs authored
-
- 22 Dec, 2013 1 commit
-
-
Bryant Mairs authored
Renamed getNominalDataRate to getConnectionSpeed. Also added upstream/downstream data rate functions to all Link classes.
-
- 07 Dec, 2013 1 commit
-
-
Don Gagne authored
Removed LinkInterface methods which were never being called. Updated various LinkInterface implementation classes to remove the methods. Some methods such as the ones which measure data rates or bits sent/received were implemented in only some of the implementation classes, and in some cases implemented incorrectly. If they were called, the values returned would be incorrect. Although there was some partial implementation for these I removed them as well since in all case they were never being called by any code. In checking Blame, these came across in 2010 and have remained unimplemented since them, so I figure better to clean up than leave crufty, unused, half finished stuff in.
-
- 13 Jun, 2013 1 commit
-
-
Michael Carpenter authored
Addition of requestReset to LinkInterface, to allow MavLinkProtocol to detect when connected, but at the wrong baud rate, request a reset.
-
- 10 Jun, 2013 1 commit
-
-
Bryant authored
Changed many functions in the abstract *Link classes to be const. This facilitates setting other functions as const. The metadata for specific links are reset when the links are added.
-
- 09 Jun, 2013 1 commit
-
-
Bryant authored
Changed many functions in the abstract *Link classes to be const. This facilitates setting other functions as const. The metadata for specific links are reset when the links are added.
-
- 18 Sep, 2011 1 commit
-
-
oberion authored
-
- 30 Mar, 2011 1 commit
-
-
James Goppert authored
-
- 19 Mar, 2011 1 commit
-
-
lm authored
-
- 08 Feb, 2011 1 commit
-
-
pixhawk authored
-
- 27 Oct, 2010 1 commit
-
-
pixhawk authored
-
- 24 Oct, 2010 1 commit
-
-
pixhawk authored
-
- 19 Aug, 2010 1 commit
-
-
pixhawk authored
Cleaned up communication structure significantly, should now be easier to add new links. Signal bytesReceived(link, QByteArray) is now only way to pass on newly received data
-
- 03 Apr, 2010 1 commit
-
-
pixhawk authored
-