Jump to content

PDOP's

+Charter Members
  • Posts

    3766
  • Joined

  • Last visited

Posts posted by PDOP's

  1. PDOP's: You might also like the Google Earth viewer: WaasClient.kmz.

    Thanks. I had found that one at

    http://www.nstb.tc.faa.gov/index.htm which was linked to in another thread. The notice on that page is new today:

     

    NOTICE: On December 23, 2010 Intelsat regained control of the Galaxy 15 spacecraft that hosts the L-band transponder that is used to transmit the WAAS GEO PRN 135 (CRW) signal. The FAA began transmitting from the re-activated payload at 16:30 UTC on 6 January 2011. The signal is in GEO Test mode per RTCA DO-229d. The FAA will be evaluating the performance of the signal prior to taking the signal out of GEO Test mode. The satellite is currently being maneuvered to orbital slot 93W where Intelsat will perform testing on the communications transponders. Once that testing is complete, the satellite is expected to be maneuvered back to an orbital slot that provides coverage to both Alaska and CONUS.

     

    I sent an email to the guy at FAA who first pointed these out to me -- asked if the drawing glitch you noticed has always been like that, or if it's just something that's cropped up since they started jockeying 135 around. If I get a reply I'll let you know.

    IIRC it's been that way since 135 started to drift east in April. It's the same on the WAAS Geo Footprint page too (link).

  2. PRN 135 / WAAS 48 may return.www.intelsat.com

    Galaxy 15 Status Update

    On 23 December, the power from the Galaxy 15 battery completely drained during its loss of earth lock and the Baseband Equipment (BBE) command unit reset, as it was designed to do. Shortly thereafter Galaxy 15 began accepting commands and Intelsat engineers began receiving telemetry in our Satellite Operations center. We have placed Galaxy 15 in safe mode, and at this time, we are pleased to report it no longer poses any threat of satellite interference to either neighboring satellites or customer services.

     

    After completing initial diagnostic tests, we will load updated commanding software to the satellite. We expect to relocate the satellite to an Intelsat orbital location where engineers at our Satellite Operations Control Center will initiate extensive in-orbit testing to determine the functionality of every aspect of the spacecraft. We will provide an update through normal sales channels, and MyIntelsat, if and when the satellite recovery mission is successful.

  3. I should fix FizzyCalc to let you input the current location of the WAAS birds, shouldn't I?
    Or... you could have it pull all of the sats positions live from the web... http://www.nstb.tc.faa.gov/incoming/Waas_SV_Status.txt

     

    Hmm... I haven't had FizzyCalc use networking to keep it simple, but I think I'll put out a new tool to locate the WAAS satellites. It'll give me a chance to try Python package deployment...

    Now that the WAAS satellite situation has settled down any chance for an update to FizzyCalc to handle the current location of the WAAS birds?

     

    GEO_Coverage12_2010.jpg

     

    Image above represents the broadcast footprints of the geostationary satellites in December 2010.

  4. ... We're driving through town the other day and I notice that the Oregon is showing our path is about 15 metres parallel to the road.

    Depending on the view of the sky at the time that's not an unreasonable error. For road navigation you might want to selcct "Lock on road" (setup=>routing=>Lock On Road=>Yes) but that can be confusing when finding caches off road.

  5. I think you meant to post your question in an existing topic but instead started a new one.

     

    The only way to remove geocaches is to connect the unit to your computer and delete the gpx files containing the geocache(s).

×
×
  • Create New...