diff options
| author | Eric S. Raymond <esr@thyrsus.com> | 2014-05-21 09:53:11 -0400 |
|---|---|---|
| committer | Eric S. Raymond <esr@thyrsus.com> | 2014-05-21 09:53:11 -0400 |
| commit | e23fbfdee2931b9d2c918b258a1dc50645a151b5 (patch) | |
| tree | 337a2dc32cab81f2b62c7067a8cae7f32de0da0a /TODO | |
| parent | afee9fd8f7ed8507f009abecf4986d0d92fbb454 (diff) | |
| download | gpsd-e23fbfdee2931b9d2c918b258a1dc50645a151b5.tar.gz | |
More on a to-do item.
Diffstat (limited to 'TODO')
| -rw-r--r-- | TODO | 8 |
1 files changed, 7 insertions, 1 deletions
@@ -114,7 +114,13 @@ Anthony Stirk <upuaut@gmail.com> writes on Wed May 21 06:09:00 2014: need to put the module back in max performance mode as soon as the satellites drops below 4. -A possibility: drop the chip to low-power modewhen it can see > 4 + I'm not sure for most applications the low power mode needs to be used at + all on the newer ublox modules. The values for the MAX-7Q are 22mA (6Q + 50mA) under acquire, tracking (i.e locked and in max performance) current + at is 17mA (39mA 6Q) and power saving reduces this to 5mA or less (15mA on + the 6Q). We've observed the issue on the 6 and 7 series. + +A possibility: drop the chip to low-power mode when it can see > 4 sats, revert to normal otherwise. *** Dispatcher/network issues |