[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[paparazzi-commits] [paparazzi/paparazzi] 0d1248: [gps] fix ubx ucenter
From: |
GitHub |
Subject: |
[paparazzi-commits] [paparazzi/paparazzi] 0d1248: [gps] fix ubx ucenter autobaud and autoconf |
Date: |
Fri, 18 Dec 2015 07:18:59 -0800 |
Branch: refs/heads/master
Home: https://github.com/paparazzi/paparazzi
Commit: 0d124875a97592399d6008fb34a6e2e343985fc5
https://github.com/paparazzi/paparazzi/commit/0d124875a97592399d6008fb34a6e2e343985fc5
Author: Gautier Hattenberger <address@hidden>
Date: 2015-12-15 (Tue, 15 Dec 2015)
Changed paths:
M sw/airborne/modules/gps/gps_ubx_ucenter.c
M sw/airborne/modules/gps/gps_ubx_ucenter.h
Log Message:
-----------
[gps] fix ubx ucenter autobaud and autoconf
Commit: ce5cd4d5993c17622ceb2246ee4150689fe8bdab
https://github.com/paparazzi/paparazzi/commit/ce5cd4d5993c17622ceb2246ee4150689fe8bdab
Author: Gautier Hattenberger <address@hidden>
Date: 2015-12-15 (Tue, 15 Dec 2015)
Changed paths:
M sw/airborne/modules/gps/gps_ubx_ucenter.c
Log Message:
-----------
[gps] fix wrong macro
Commit: cc354c6a3cf605b88f29cd246c2cff84179ac9da
https://github.com/paparazzi/paparazzi/commit/cc354c6a3cf605b88f29cd246c2cff84179ac9da
Author: Felix Ruess <address@hidden>
Date: 2015-12-18 (Fri, 18 Dec 2015)
Changed paths:
M sw/airborne/modules/gps/gps_ubx_ucenter.c
M sw/airborne/modules/gps/gps_ubx_ucenter.h
Log Message:
-----------
Merge pull request #1480 from paparazzi/fix_ubx_ucenter
[gps] fix ubx ucenter autobaud and autoconf
The reason it is not working (at least one of the reasons...) is that the
autobaud function is not working. Or exactly it is not very robust to properly
catch the ACK. And if it happens to work (either it found the correct value
while testing them or it falls back to the default and it is the correct one),
it will not set the uart to the "new" value. It will send the message to set
the baudrate to the last tested rate. This is because UBX_GPS_BAUD is defined
to GPS_LINK.baudrate which is set to the last value, not the initial one.
The end result in most cases is that the modules are saturated with messages at
9600 bauds and that the reply of the version request fails, and then the NAV
config is sent instead of NAV5.
I'm going to try this patch:
- save target baudrate at init
- use NAV5 by default if version couldn't be fetched
Compare:
https://github.com/paparazzi/paparazzi/compare/c401793cf025...cc354c6a3cf6