Peter Barker
74670a77be
GCS_MAVLink: avoid allocating a GCS_MAVLINK per mavlink channel
2019-08-14 18:25:43 +10:00
Pierre Kancir
b1506ca652
GCS_MAVLink: pass mavlink_message_t by const reference
2019-07-16 20:51:42 +10:00
Peter Barker
c11da6a85d
GCS_MAVLink: routing example: use GCS_Dummy in place of custom GCS
2019-06-20 11:41:19 +10:00
Peter Barker
0963957b31
GCS_MAVLink: correct GCS_Dummy firmware version
2019-06-18 10:54:01 +10:00
Peter Barker
e6653f42dd
GCS_MAVLink: correct examples with override keyword
2019-04-30 09:29:59 +10:00
Michael du Breuil
8cafbe394f
GCS_MAVLink: Fix includes
2019-04-05 20:12:53 +11:00
Peter Barker
ab1c42696c
GCS_MAVLink: move FRsky telemetry up into common GCS telemetry class
2019-03-19 14:39:14 +11:00
Peter Barker
74702b8688
GCS_MAVLink: make sending of send_pid_tuning up
2019-03-05 10:41:56 +11:00
Peter Barker
cb33f290a7
GCS_MAVLink: move sensor flags to be a GCS thing rather than a GCS_MAVLINK thing
...
These are a per-vehicle thing, not a per-mavlink-backend thing.
2019-02-19 14:09:59 +11:00
Peter Barker
de615ee11d
GCS_MAVLink: move try_send_message of nav_controller_output up
2019-02-19 10:08:00 +11:00
Peter Barker
d8847a6192
GCS_MAVLink: move handling of command-int MAV_CMD_DO_SET_HOME up
2019-02-13 09:42:26 +11:00
Peter Barker
120f0822ae
GCS_MAVLink: move sending of sys_status message up
2019-02-05 11:07:39 +11:00
Michael du Breuil
27d461348e
GCS_MAVLink: Use rally singleton
2019-01-08 10:39:50 +11:00
Peter Barker
dfd0ecd2bd
GCS_MAVLink: use mission singleton
2018-12-13 10:52:52 +09:00
Peter Barker
ef46acda71
GCS_MAVLink: support MAV_CMD_SET_MESSAGE_INTERVAL
2018-12-10 12:52:41 +09:00
Peter Barker
26e7abe6c4
GCS_MAVLink: use camera singleton to get camera rather than callback
2018-08-31 15:48:56 +10:00
Peter Barker
d5f6911db7
GCS_MAVLink: use compass singleton instead of subclass callback
2018-08-31 15:48:56 +10:00
Peter Barker
c333a905df
GCS_MAVLink: use AP_FWVersion singleton
2018-06-18 19:10:37 +01:00
Peter Barker
fc1775df75
GCS_MAVLink: handle setting of ekf origin in GCS_MAVLink
2018-05-17 10:13:42 +10:00
Peter Barker
417e9e9aaf
GCS_MAVLink: move data stream send up
2018-05-09 16:15:38 +10:00
Peter Barker
682679c68d
GCS_MAVLink: use AP_ServoRelayEvents singleton
2018-04-18 20:31:55 +09:00
Peter Barker
4fd2ec1cef
GCS_MAVLink: factor vehicle's mavlink send_heartbeat
2018-04-03 13:05:19 +01:00
Peter Barker
269294754f
GCS_MAVLink: use gps singleton
2017-11-15 13:43:03 +00:00
Peter Barker
d0c2898ebc
GCS_MAVLink: move handling of SET_GPS_GLOBAL_ORIGIN up
2017-09-19 15:44:23 +09:00
Peter Barker
add1743c12
GCS_MAVLink: move send_autopilot_request calls up to GCS base class
2017-08-30 15:54:46 +01:00
Peter Barker
2a07a077d9
GCS_MAVLink: use GCS_MAVLINK subclasses to handle set_mode
2017-08-16 11:05:37 +10:00
Peter Barker
1fc82442a0
GCS_MAVLink: remove dummy functions; examples are linked with all libs
2017-08-09 16:18:22 +01:00
Peter Barker
b4688bd3d4
GCS_MAVLink: move common mavlink camera handling up
2017-07-28 14:32:58 +01:00
Peter Barker
85a0da6178
GCS_MAVLink: handle common GPS messages in base GCS_MAVLINK class
2017-07-25 14:00:45 +01:00
Peter Barker
bd28bdd907
GCS_MAVLink: move handling of MAG_CAL command longs up
2017-07-17 14:17:19 +01:00
Peter Barker
318861e824
GCS_MAVLink: move mavlink support for servo/relay up
2017-07-16 23:56:00 +01:00
Peter Barker
ebe3dcef6f
GCS_MAVLink: move rally-point handling up
2017-07-14 01:28:05 +01:00
Peter Barker
129d7220e6
GCS_MAVLink: move handling of incoming statutext messages up
2017-07-12 16:52:24 +01:00
Peter Barker
6cc19fee35
GCS_MAVLink: GCS_Dummy and GCS_routing get get_mission
2017-07-11 23:47:52 +01:00
Pierre Kancir
b2c8bc8074
GCS_MAVLink: example fix travis warning
...
missing function declaration
implicit cast
some style fix
2017-04-13 19:56:16 +01:00
Peter Barker
cc28ff49e9
GCS_MAVLink: support for a singleton
2017-02-13 09:32:01 +11:00
murata
4a60850558
GCS_MAVLink: Unify from print or println to printf.
2017-01-27 18:20:22 +11:00
Mathieu OTHACEHE
152edf7189
Global: remove mode line from headers
...
Using a global .dir-locals.el file is a better alternative than
reincluding the same emacs header in every file of the project.
2016-10-24 09:42:01 -02:00
Andrew Tridgell
a331542958
GCS_MAVLink: fixed typo
2016-07-01 15:35:49 +10:00
Peter Barker
1e146256cc
GCS_MAVLink: move telemetry_delayed up into base class
2016-05-31 08:46:09 +10:00
Peter Barker
43fed65f37
GCS_MAVLink: move adjust_rate_for_stream up
2016-05-29 19:38:49 +10:00
Peter Barker
03ded35d7c
GCS_MAVLink: update routing example for mavlink namespacing
2016-05-29 16:21:21 +10:00
Ricardo de Almeida Gonzaga
3f92a64b99
GCS_MAVLink: Fix typos
2016-05-13 19:20:05 -03:00
Lucas De Marchi
831d8acca5
Remove use of PROGMEM
...
Now variables don't have to be declared with PROGMEM anymore, so remove
them. This was automated with:
git grep -l -z PROGMEM | xargs -0 sed -i 's/ PROGMEM / /g'
git grep -l -z PROGMEM | xargs -0 sed -i 's/PROGMEM//g'
The 2 commands were done so we don't leave behind spurious spaces.
AVR-specific places were not changed.
2015-10-30 14:35:16 +09:00
Caio Marcelo de Oliveira Filho
09579cb6e3
GCS_MAVLink: remove unnecessary includes
2015-10-21 09:16:10 +11:00
Caio Marcelo de Oliveira Filho
2e464a53c2
AP_HAL: make code not depend on concrete HAL implementations
...
The switching between different AP_HAL was happening by giving different
definitions of AP_HAL_BOARD_DRIVER, and the programs would use it to
instantiate.
A program or library code would have to explicitly include (and depend)
on the concrete implementation of the HAL, even when using it only via
interface.
The proposed change move this dependency to be link time. There is a
AP_HAL::get_HAL() function that is used by the client code. Each
implementation of HAL provides its own definition of this function,
returning the appropriate concrete instance.
Since this replaces the job of AP_HAL_BOARD_DRIVER, the definition was
removed.
The static variables for PX4 and VRBRAIN were named differently to avoid
shadowing the extern symbol 'hal'.
2015-10-21 09:16:07 +11:00
Gustavo Jose de Sousa
d7a2ef3e35
GCS_MAVLink: standardize inclusion of libaries headers
...
This commit changes the way libraries headers are included in source files:
- If the header is in the same directory the source belongs to, so the
notation '#include ""' is used with the path relative to the directory
containing the source.
- If the header is outside the directory containing the source, then we use
the notation '#include <>' with the path relative to libraries folder.
Some of the advantages of such approach:
- Only one search path for libraries headers.
- OSs like Windows may have a better lookup time.
2015-08-11 16:38:25 +10:00
Andrew Tridgell
3b48f68cce
GCS_MAVLink: convert example from .pde to .cpp
2015-06-01 17:07:07 +10:00