I don't know about the rest of you, but so far it's been my experience that the safest way to accurately calculate the potential cost of a repair done by a professional (as opposed to by me) is to take the estimate and double it.

As for the Gulfstar, MMO increased fuel efficiency by between 8 and 10 percent and I estimated it cut in half the amount of exhaust smoke resulting from powering up after extended idling in navigation locks. Without doing the calculations, I estimate I'm getting similar results on the AT-34 and the vehicles.

Received Signal Strength *always* relative to some signal model, incorporating considered bandwidth, assumptions on the modulation scheme, duration of transmission, generally: It's a *estimation* of received signal strength based on *some* property of the received signal. If that estimator fits your signal well depends on your signal!

As a completely unnecessary but fun side effect, you can use this knowledge to estimate your location in space if you see enough satellites.

There's no way to phase-sync the TX and RX LOs on the E310, but they are inherently frequency synced, so a simple cross-correlation timing offset estimator should do the trick.

Error Estimate Nr. of visible Satellites Nr. of tracked Satellites Locked State Health State With a space between every item.

With only 20,000 or so phase values the estimator OADEV degrades considerably in accuracy for tau > ~2000 sec or so, TOTDEV is better in this respect. THEO_1 and its variants are even better estimators in that they make more effective use of the available data. Bruce

The handheld receivers also allow you to set the variation manually, if you know its value more accurately than the estimate the receiver calculates. Even the Garmin board-level receivers (e.g. GPS 25) output variation, probably because Garmin already has the model for their other receivers.

Since it (hopefully) is predictable, it's just another thing to feed into the signal estimation side of the process.