1a9d402feb
mavlink receiver: fix topic handle initialization of manual control topic
2015-05-27 15:36:05 -07:00
4565f57468
Merged release_v1.0.0 into master
2015-05-27 15:28:41 -07:00
31923c3add
On more fixup for orb_advert_t changed to void *
...
Reviewed all changes in pull request and made sure all cpp files
check orb_advert_t types against nullptr and c files check against
NULL.
Signed-off-by: Mark Charlebois <charlebm@gmail.com >
2015-05-27 14:42:49 -07:00
a452478ef9
More fixups for orb_advert_t changed to void *
...
Signed-off-by: Mark Charlebois <charlebm@gmail.com >
2015-05-27 14:42:49 -07:00
1ca05aaa64
orb_advert_t changed to void * and checks changed to nullptr
...
The existing orb_advert_t use thoughout the code sometimes tries
to treat it as a file descriptor and there are checks for < 0
and ::close calls on orb_advert_t types which is an invalid use
of an object pointer, which is what orb_advert_t really is.
Initially I had changed the -1 initializations to 0 but it was
suggested that this should be nullptr. That was a good recommendation
but the definition of orb_advert_t had to change to void * because
you cannot initialize a uintptr_t as nullptr.
Signed-off-by: Mark Charlebois <charlebm@gmail.com >
2015-05-27 14:42:49 -07:00
b990d9fa7e
Missed a check for < 0
...
Signed-off-by: Mark Charlebois <charlebm@gmail.com >
2015-05-27 14:41:33 -07:00
a734fc96d1
extensive orb_advert_t fixes
...
The calls to orb_advertise were being mishandled throughout the code.
There were ::close() calls on memory pointers, there were checks
against < 0 when it is a pointer to a object and values larger than
0x7ffffffff are valid. Some places orb_advert_t variables were
being initialized as 0 other places as -1.
The orb_advert_t type was changed to uintptr_t so the pointer value
would not be wrapped as a negative number. This was causing a failure
on ARM.
Tests for < 0 were changed to == 0 since a null pointer is the valid
representation for error, or uninitialized.
Signed-off-by: Mark Charlebois <charlebm@gmail.com >
2015-05-27 14:41:33 -07:00
9a67303416
Merge pull request #2231 from jgoppert/lidar_lite_pwm_fix
...
Lidar lite driver fixes.
2015-05-27 10:54:59 -07:00
96bfe85ceb
fw_att_control: another ugly way to prevent a newline
2015-05-26 23:05:26 -07:00
d3fe6fd256
fw_att_control: whitespace
2015-05-26 23:05:18 -07:00
e2277bbe2d
fw_att_control: don't brag about being running
2015-05-26 23:05:11 -07:00
a7902c02a9
position_estimator_inav: be a bit more informative about this ominous offs
2015-05-26 23:05:04 -07:00
11f80ceb64
land_detector: get rid of one dot at a time
2015-05-26 23:04:17 -07:00
43d22619f6
mavlink: no need to shout about disabling hardware flow control
2015-05-26 23:03:14 -07:00
321e1c1f7b
navigator: stop complaining about some geofence not cleared
2015-05-26 23:00:44 -07:00
57f5db544c
Distance sensor log precision fix.
2015-05-27 00:01:24 -04:00
3cc84b1a15
Correct ll40ls param enable length.
2015-05-26 21:20:18 -04:00
cbc169af2f
Merge branch 'll40ls_startup' of https://github.com/mhkabir/Firmware into mhkabir-ll40ls_startup
...
Conflicts:
ROMFS/px4fmu_common/init.d/rc.sensors
2015-05-26 20:08:11 -04:00
6f309ba625
Distance sensor log fix.
2015-05-26 20:03:33 -04:00
853a22db18
ll40ls : conditional startup param
2015-05-26 21:44:55 +05:30
0b703096e7
Fixed distance sensor log error.
2015-05-26 02:48:24 -04:00
613b50b14f
IO firmware: Support pwm reversal
2015-05-25 16:42:46 +02:00
3883b71132
pwm handler: Support channel reversal
2015-05-25 16:42:46 +02:00
c6fe4fd35a
mavlink: rename field for RC input mode
2015-05-25 16:34:57 +02:00
6253f6154f
commander: rename field for RC input mode
2015-05-25 16:34:42 +02:00
b399469477
Merge pull request #2240 from TSC21/mavlink_multiadvertise
...
mavlink: added multi advertise for distance_sensor in mavlink receiver
2015-05-26 23:32:50 -07:00
a14b020d63
Merge pull request #2203 from NaterGator/mavlink_usbfix
...
Fix MAVLink USB UART detection
2015-05-26 23:22:27 -07:00
9fce6dd8ba
Merge pull request #2230 from bansiesta/fix_startup_printfs
...
Cosmetic startup fixes
2015-05-26 23:02:56 -07:00
0d1bc2cd0b
mavlink: added multi advertise for distance_sensor in mavlink receiver
2015-05-26 23:35:45 +01:00
4cf8ce30ba
fw_att_control: another ugly way to prevent a newline
2015-05-25 19:10:05 +01:00
d36b65aab5
fw_att_control: whitespace
2015-05-25 19:09:45 +01:00
38412993d6
fw_att_control: don't brag about being running
2015-05-25 19:09:28 +01:00
c56a9ce965
position_estimator_inav: be a bit more informative about this ominous offs
2015-05-25 19:08:51 +01:00
87f41855fb
land_detector: get rid of one dot at a time
2015-05-25 19:01:34 +01:00
40e9c83ed6
mavlink: no need to shout about disabling hardware flow control
2015-05-25 18:28:27 +01:00
3c39e85fdf
navigator: stop complaining about some geofence not cleared
2015-05-25 18:09:01 +01:00
81240d6040
commander: Initial RC detection is only an info string
2015-05-24 23:31:58 +02:00
c5f14ef785
Merge pull request #2224 from bansiesta/lidarlite_merge
...
Lidarlite merge and bringup
2015-05-24 23:18:52 +02:00
009815deb0
Improve config and mapping
2015-05-24 20:11:51 +02:00
2bb655c46c
mavlink app: Improved mapping to RC input
2015-05-24 20:11:51 +02:00
01fd84e4dc
mavlink and commander app: Add support for manual input, either directly or via remote control
2015-05-24 20:11:50 +02:00
af546def91
mavlink: use 'buttons' field of MANUAL_CONTROL message as mode switches
2015-05-24 20:11:50 +02:00
bed746c213
commander: Add param and mode to disable RC input in general and required validation / setup.
2015-05-24 20:11:50 +02:00
77bd36aa33
Fix opendir failure handling
2015-05-24 20:11:00 +02:00
4206b030bf
Fix opendir failure handling
2015-05-24 10:40:52 -07:00
2fb999674b
Merge remote-tracking branch 'px4/pr/2200' into lidarlite_merge
2015-05-24 16:30:02 +01:00
72e9390985
distance_sensor: minor changes
2015-05-24 16:03:01 +01:00
cf39e8c721
mavlink: adapted to change in distance_sensor msg
2015-05-24 15:58:44 +01:00
13a4cdd05e
ekf_att_pos_estimator: adapted to change in distance_sensor msg
2015-05-24 15:58:15 +01:00
a0011d2163
Merge remote-tracking branch 'px4/pr/2200' into lidarlite_merge
2015-05-24 13:59:18 +01:00
Lorenz Meier