Jump to content

GPSlug

+Premium Members
  • Posts

    388
  • Joined

  • Last visited

Posts posted by GPSlug

  1. You might now also see a new WAAS satellite (46) in North America.

     

    A notification on the FAA website dated 2010/01/19 is shown below (link - you might have to scroll down). :

     

    New WAAS GEO to Begin Broadcasting in Test Mode in March

     

    January 19, 2010 – Beginning in March, the FAA will begin testing a third geostationary satellite (GEO) for WAAS. The test will be conducted using a newly-leased transponder on the Inmarsat 4F3 GEO (broadcasting on PRN-133). During the test period, the navigation signal will be unusable for navigation purposes. The test will run from March to December 2010 at which time the broadcast signal is expected to be certified as operational and usable for navigation.

     

    Note that there are two numerical designations for each WAAS satellite. PRN numbers identify the code transmitted by the satellite while the NMEA designation is simply the PRN minus 87. Garmin uses the NMEA number.

    I checked just now and 133(46) is transmitting now, but it's only sending out message type 0 full of zeros. So, not even close to usable.

  2. The oscillator could be drifting out of spec with age. That would make it take longer to get its first batch of satellites because it wouldn't be looking in the right frequency window before it solved for its own clock drift.

     

    Another option is that the real-time clock is giving out, and it doesn't know the right time when its first turned on. Is the set of satellites you eventually get more or less the same as it first started looking for?

     

    Either way, there's probably not much you can do about it for a reasonable cost.

  3. Just a clarification, there is only one unit of length, the meter, kilo, mega, centi, micro ... are just a way to represent factor of 10 but do not define "new" units (we use a decimal based numbering system) !

     

    This is not often understood. Lack of proper education in science and technology.

    Even Garmin eng. as they let you set the GPS to display in meter or kilometer ! This is a non sense, they should always try to display with the maximum number of significant digits and adjust the display accordingly to show km or m !

    It's a matter of semantics, but I would say that if there is any conversion necessary, no matter how trivial, the units have changed. If you are recording distances in a list, and they are all the same unit, you can specify that unit at the top of the column. You can't do that if some are in m and some in km. If you need to specify it, it's a different unit.

     

    It is annoying for ex. for distance as you really loose accuracy if you set the display to km then come closer to your target.

    But if you are driving and need to glance at the display to know how far the next turn is, you may not want to need to squint at the units identifier.

     

    Of course one can't beat the screwing up of using imperial units !

    They can be annoying, but they keep you on your toes. You always need to be rigorous about your units. You can't just get lazy because it's all "metric". If you're told a vehicle is going "35", you'd better know whether that's in km/h or m/s. It's not that big of a leap from there to imperial units.
  4. Hate to ask a question in the middle of a thread but...How do Solar Anomalies such as Solar Flares effect GPS signal Receptions? I know they can jack with other wireless signals and the news media use to report these occurences frequently.

    The ionosphere can become more active and cause both ranging errors and, in extreme cases, tracking problems. These are more frequent around solar max, but they can happen anywhere in the 11-year cycle. NOAA has a space weather site that predicts and monitors these storms. I don't see that anything significant happened this last weekend.

     

    WAAS helps a lot to correct for iono errors, and gives an indication of the amount of remaining error that your receiver can use to bump up its EPE if things are bad.

  5. Well, EGNOS hasn't "recently gone active" in that sense of the idea. It's more like it's "come out of beta".

    Heck, not even that. It's still running in "test mode" (transmitting message type 0 = not usable for safety-of-live/aviation), so the signal hasn't changed at all. As far as I can tell, the only thing this announcement meant is that someone was able to check off a milestone. The timing of it probably has to do with there being a European space conference this week.

     

    Use for safety of life is supposed to happen later this year.

  6. My 60Cx was slowing down more and more.

     

    Between the accumulated gpx track files and the different map sets I had on it for quick swapping, I figured the micro-SD was getting fragmented. So I pulled all the files off of it, re-formatted, and put just one map file back on it.

     

    It loads a heck of a lot faster now using the same map set I was before. That set isn't really large, but it isn't tiny (~300 MB between CNNA-NT, Ibycus Topo, Calgary Trail Maps, and Florida Topo).

  7. Degrees, Minutes and Seconds

    DDD° MM' SS.S"

    N 32° 18' 23.1" W 122° 36' 52.5"

    Ok, I checked it again. The format I'm looking for has 6 digits after degrees, not 5.

    That's just an extra decimal place.

     

    It's the same as

    Degrees, Minutes and Seconds

    DDD° MM' SS.SS"

    N 32° 18' 23.10" W 122° 36' 52.50"

  8. There's no inherent bias between a WAAS-corrected position and an uncorrected position. So you don't need to worry about that.

     

    It's important to keep in mind that over the last several years, users become experienced with how their units behave during solar minimum. Now that we are slowly moving into a period of higher solar activity and increased ionospheric errors, people might find that WAAS becomes more important for them. But even that will be sometimes no big improvement, and sometimes a lot.

  9. Since when is the "typical" GPS signal accurate to "about two feet" ???

    Well it did say "air force" officials.

     

    "Typical" could mean "as present in the existing system", which could include the P(Y) signal.

    I think it's "typical" for "when it leaves the satellite". I.e. not including atmospheric errors and multipath.

     

    Civilians don't have access to it, but it IS there and always has been. This article could be saying that the new L5 signal is interfering with the classic L1 and L2 P(Y) signals.

     

    I find it strange that the L5 signal is interfering. It would make more sense that the new signals being added (such as L2C) on the L1 and L2 frequencies would be more likely to cause a problem.

    The article doesn't explain it very well, but this is one of the existing batch of satellites (block IIR-M) that was modified to add on the L5 signal for test purposes. It was a little rushed compared to the rigorous testing that a satellite design normally goes through. Apparently there's a problem with the signal combiner that's throwing off the other frequencies in a way they may not be able to compensate for because it seems to vary with angle.

     

    The satellites with L5 designed in (block IIF) wouldn't have the same problem, but they aren't ready yet.

  10. Here's the full report and subcommittee hearing.

     

    This is largely about delays and budget overruns from the contractors making the next generation of satellites. It's gotten to where they'll be cutting it a little close to get them up as the older ones wind down.

     

    In some ways, the satellite deployment has been a victim of it's own success. Historically, the satellites have operated much longer and much more reliably than they were designed for. This has always meant that their budget gets cut and the launch schedules stretched out.

     

    So there could be a gap where the constellation isn't full. I don't think there's much risk of the system not meeting its specs. But there's some chance it could take a hit on how much it's been outperforming those specs.

  11. Looks like they're testing the L5 band on prn01. I think L5 is a commercial band. As far as I can tell it's not broadcasting on L1/L2 yet.

    It started transmitting L5 on April 10. I don't have an L5 antenna feed at my desk, but I am tracking L1 & L2 on it right now. Since it's unhealthy, I have to force the receiver to do so.

  12. This is just speculation, but given the wide area, it sounds like they are picking up some data they can't handle.

     

    Once in a great while, satellites that are set "unhealthy" can put out some funky nav data. It shouldn't be anything the receiver can't ignore, but it can expose bugs; like buffer overruns.

     

    There is a new prn 01 that isn't set healthy yet, but started transmitting on the 28th. I'll try to capture some data to see if there's anything noticeably weird. But it might be too late now.

  13. I don't think so. I still see WAAS satellites; there is just no D.

    I agree, I had a solid lock on 51 with 3.90, but no "D"'s. Does that mean the unit was using the corrections, but just not displaying the "D''s? I am not expert enough to answer that question, just wondering if anyone knows.

    If you have a serial cable, you can look at the $GPGGA messages coming out. If the quality field is '2' or higher, it should be correcting.

  14. They were originally defined to be essentially the same. But as time has gone on, the actual measurement of WGS84 or NAD83 has been done by different entities with different priorities (e.g. more global consistency vs. better alignment with existing benchmarks), and they aren't quite the same any more.

     

    For a handheld, it doesn't really matter and the old NGA table that says the difference is basically zero. When you really need an absolute position within the accuracy where it matters, you need to be more specific than just "WGS84" or "NAD83" and specify which realization (which time the big set of measurements was done to define it) is relevant.

  15. And being within a few hundred miles of a station will only impact your IONO corrections, you still can get FAST and LONG corrections, no matter where you are, and those can help improve position accuracy.
    Like EraSeek said, as long as you are inside the iono grid, the distance to the nearest station doesn't really matter. Local affects get washed out in the network.

     

    I wonder if anyone has a reference of the contributions of those individual 3 kinds of WAAS corrections (vs no corrections) to ones PDOP, HDOP or VDOP?
    It's zero, zero, and zero. Errors are not a part of the DOP calculation.

     

    1. On later model Garmins, the impact of WAAS on battery life is negligible, as my own current consumption tests on a Summit HC show. (No measurable difference in battery current whether WAAS was turned on or off.)
    I think the difference from older models is that the error correction algorithm went from being done in software to being done on the tracking chip. FEC is a CPU hog.
×
×
  • Create New...