7e1ea35571
mavlink receiver: in hil use map_projection_timestamp for hil_local_pos.ref_timestamp
2014-04-25 09:43:19 +02:00
f5d9023b10
navigator: set home_pos timestamp as map projection reference timestamp
2014-04-25 09:42:28 +02:00
9ebd6b3486
geo: interface to get reference lat lon, option to set reference timestamp on initialization
2014-04-25 09:41:46 +02:00
22aaae197b
Merge branch 'rc_timeout' into mpc_rc
2014-04-24 22:40:46 +02:00
63c50676f9
MISSION switch renamed to LOITER
2014-04-24 22:38:19 +02:00
4e30784d6c
rename map_projection_inited to map_projection_initialized
2014-04-24 17:16:20 +02:00
b249d04e52
geo: get function for timestamp of map projection
2014-04-24 17:13:06 +02:00
618ac319e6
pos estimator inav: check if map projection is initialized
2014-04-24 17:06:10 +02:00
9f2da53f08
mc pos control: map projection init not needed anymore
2014-04-24 17:05:30 +02:00
35d15720ef
geo: add timestamp and function to get init state
2014-04-24 17:04:27 +02:00
7e5b684f8c
Merge pull request #860 from PX4/vicongpssimulation
...
Indoor gps simulation mode
2014-04-24 16:36:24 +02:00
fbd782ff06
remove tags file
2014-04-24 16:32:56 +02:00
cfe346ddfa
Merge remote-tracking branch 'upstream/master' into mtecs
2014-04-24 16:19:42 +02:00
5d6e2a1939
Merge remote-tracking branch 'private_swissfang/mtecs' into mtecs
...
Conflicts:
src/modules/fw_pos_control_l1/fw_pos_control_l1_main.cpp
2014-04-24 16:19:21 +02:00
be0824c207
Merge remote-tracking branch 'upstream/master' into geo
2014-04-24 16:17:16 +02:00
8102c5a460
Merge pull request #862 from thomasgubler/gitignore_tags
...
add tags file to .gitignore
2014-04-24 16:13:21 +02:00
8bb1b39399
mavlink receiver: hil: local pos reference lat lon from first data
2014-04-24 16:12:28 +02:00
496cba0855
add tags file to .gitignore
2014-04-24 16:03:36 +02:00
fbcb248bc3
navigator: init map projection on home pos update
2014-04-24 15:59:49 +02:00
6517c201f7
geo: add missing return, make map projection reference static
2014-04-24 15:59:13 +02:00
3a898e54ad
towards a global map projection instance, WIP: need to remove local updates of the reference and add a global map update
2014-04-24 14:30:29 +02:00
db474072a7
Merge branch 'rc_timeout' into mpc_rc
2014-04-23 19:03:03 +02:00
56592ec77d
commander: don't start RTL on failsafe if landed
2014-04-23 19:01:05 +02:00
d7d6a3d3b7
filter gps simulation hil gps message with sysid
2014-04-23 16:26:44 +02:00
a2940182ef
add parameter to mavlink app to allow parsing of HIL GPS message even if not in HIL mode
...
Conflicts:
src/modules/mavlink/mavlink_receiver.cpp
2014-04-23 15:53:48 +02:00
34597599fc
navigator: merging bug fixed
2014-04-23 15:26:24 +02:00
dc8a0b291a
Merge branch 'mpc_local_pos' into mpc_rc
2014-04-23 15:25:13 +02:00
320c97c498
navigator: check if mission reached on vehicle_status updates
2014-04-23 15:24:45 +02:00
2998685a3a
Merge branch 'mpc_local_pos' into mpc_rc
2014-04-23 14:22:52 +02:00
60554c8a56
navigator: publish global_position_setpoint on vehicle_status updates
2014-04-23 14:15:59 +02:00
971e8fc4ff
Made failsafe more intuitive. Default (0) maps to whatever channel is throttle. If a non-zero value is entered, a direct channel map is used so use
2014-04-22 23:19:04 -07:00
81c03154b9
Added ASSISTED, AUTO, EASY, RETURN, & LOITER programmable thresholds to enable various user mode switch configs (orig., 2x3, 1x6, etc).
2014-04-22 21:49:29 -07:00
831a7c4a83
Added RC_MAP_FAILSAFE parameter for customizing failsafe channel. Default to THROTTLE
2014-04-22 20:53:07 -07:00
7e621070ca
renamed mission_switch to loiter_switch and assisted_switch to easy_switch
2014-04-22 18:23:27 -07:00
d6e6ee3440
Merge branch 'rc_timeout' of https://github.com/TickTock-/Firmware into rc_merged
2014-04-22 17:43:36 -07:00
a1cf8801bb
sdlog2: add failsafe state logging
2014-04-22 11:36:25 +02:00
e4a4430f9f
Merge branch 'master' into rc_timeout
2014-04-22 11:18:07 +02:00
302233a34f
Merge branch 'master' into mpc_local_pos
2014-04-22 11:13:11 +02:00
fd56c15a20
Merge remote-tracking branch 'px4/master' into navigator_cleanup
...
Conflicts:
ROMFS/px4fmu_common/init.d/rcS
src/modules/mavlink/mavlink_main.cpp
src/modules/mavlink/mavlink_messages.cpp
src/modules/mavlink/module.mk
src/modules/sdlog2/sdlog2_messages.h
2014-04-22 11:10:48 +02:00
a30411e9f2
Fixed printing in attitude control
2014-04-22 11:02:53 +02:00
4585df1182
Robustified filter init / sequencing
2014-04-22 11:02:31 +02:00
1e80e62491
ekf: Better variable zeroing
2014-04-22 10:26:44 +02:00
bd637697e4
Removed verbose print
2014-04-22 10:26:26 +02:00
2ecaab98f9
Merge branch 'master' of github.com:PX4/Firmware into ekf_params
2014-04-22 09:58:07 +02:00
aefea1a95d
Merge pull request #850 from PX4/mavlink_startup_cleanup
...
mavlink: Start the same in HIL mode as in normal mode. Requires all HIL ...
2014-04-22 09:57:56 +02:00
af56e65a37
Merge branch 'master' into ekf_params
2014-04-22 09:57:28 +02:00
f0e28a60ca
Revert "HIL: Increased MAVLink link wait time based on previous experience that this is timing sensitive."
...
This reverts commit 78bf7ed969
2014-04-22 09:57:16 +02:00
5b7209639d
Revert "HIL: Increased MAVLink link wait time based on previous experience that this is timing sensitive."
...
This reverts commit 78bf7ed969
2014-04-22 09:56:38 +02:00
5481b91ed1
Merge pull request #854 from jean-m-cyr/master
...
Reduce data manager SD card wear and tear
2014-04-22 09:39:13 +02:00
bf4558c31b
Reduce data manager SD card wear and tear
...
When the data manager was first designed each file record contained a 2
byte header and an 126 byte data section, resulting in a record length
of 128 bytes. Along the way it was decided to add 2 spare bytes to the
record header, but regrettably the data section was not correspondingly
reduced in size so we end up with a record length of 130 bytes. This is
bad since it does not align with SD card flash sectors and results in
more erase/write flash cycles than necessary thus reducing the SD cards
life.
This update reduced the data section of the data manager to 124,
resulting in an optimal record length of 128 bytes.
In order to avoid the reuse of data previously written data in the old
format, which could result in catastrophic misinterpretation, the data
manager file is checked at startup. If it is found to be in the old
format, it is deleted and recreated with in the new record length. In
this case previously stored data is lost, but that is far safer than the
unpredictable result of using the old file.
2014-04-22 01:19:01 -04:00
Thomas Gubler