Mark Weiss
Second Officer
United States
Offline
|
Apparently one person here has never used an in-dash automobile GPS, because in reality, there is no "operator error" because it is a turnkey system. The time to acquire satellites is dependent on the quality of the receiver, antenna and weather conditions. The operator simply puts the key in the ignition switch and drives the car. The GPS satellite acquisition is automatic and not subject to "user error".
That was a very interesting read and backs up what I have already said about atmospheric conditions. A quality receiver will make weather conditions transparent, as it's AGC on the analog side of receiving the RF signals, as well as the algorithms that compensate for the various delay factors, handle all the heavy lifting and in the end, you have GPS information. That may not be the case for the one in our SUV. As I have observed, it acquires in about a minute on a clear day, in my driveway, with trees around, but on heavy overcast and rainy days, I have driven as long as 45 minutes on the open highway before the vehicle's position finally updated and enough satellites were acquired. Someday, we need to buy a newer vehicle, though our impending move to Japan is holding off vehicle purchases.
Aardvark correctly points out that this is really a display problem. What needs to be discovered is why the Crystal Sky Ultra has been consistently failing to provide a flight path in the map window and a home point after takeoff. The times I have flown on clear days, this always happened just after motor start, before takeoff. My last three flights have been under overcast conditions with light precipitation starting and none of those flights displayed a flight path nor a home point on the map window. I'm waiting for another clear day to see if the flight path displays, but so far with have been stuck in a perpetual rain cloud since August.
I have a hunch it's a timing issue. The tablet might not update it's flight map if GPS isn't acquired within a certain window of time and if the acquisition happens just outside that limited window, it never updates the display. That's my postulate for what may be causing this behavior. Unfortunately, nothing in the logs reports on how the tablet device behaves with regard to displaying or not the flight path. |
|