GPS rework: Please test and report on software fix prior to attempting any hardware fix

Andy Green andy at
Wed Aug 6 08:44:22 CEST 2008

Hash: SHA1

Somebody in the thread at some point said:
| Al Johnson wrote:
|> For a bit more consistency of timing, less manual intervention, and
|> readings to get an idea of the run to run variation in that location,
can I
|> suggest a script? It could do with a timeout when waiting for a fix since
|> with deivestrength 3 and idleclk 1 this can take a _very_ long time,
|> forever in some locations!
| I was just about to write a similar script when I saw yours hit my
| inbox... other than a couple of assumptions, I like yours better than
| what I had in mind

These are really interesting, thanks.

| d i   min /  avg / max
| 0 0  35.20/ 55.33/144.30   <===
| 0 1  37.39/ 77.76/315.76

| 3 0  36.07/ 42.07/ 47.82   <===
| 3 1  97.46/173.09/359.69

These relative numbers are a bit counterintuitive... it might be worth
trying it again from a "very cold boot" but with the script

for DRIVESTRENGTH in 3 2 1 0

and seeing if the bias to a worse max moves accordingly.

- -Andy
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora -


More information about the community mailing list