GPS only, Glonass only, Galileo only, or a mix of all three. It gets more complex than that, as with good visibility, a GPS-only receiver is typically better than a multi-GNSS receiver for timing purposes.
Someone replied to one of my replies on the nanog list pointing out that GPS PRN (satellite number) 29 emitted an odd message starting at 20:39:47 UTC for about an hour where a parameter which typically only increments went backwards. I need to do some more research to figure out if this parameter never goes backwards or rarely goes backwards. I also need to dig deeper into the messages about that time to see if there were any other anomalies. After some sleep tonight, my project for tomorrow will be to dig through various archives and also possibly run the actual transmitted messages through the GPS sim to determine if I can replicate this on the bench. I'm hopeful that I can reliably On Wed, Jan 1, 2020 at 1:49 AM <ch...@wbmfg.com> wrote: > Curious, cannot you generate sync with GLONASS only? > > *From:* Ken Hohhof > *Sent:* Tuesday, December 31, 2019 5:01 PM > *To:* 'AnimalFarm Microwave Users Group' > *Subject:* Re: [AFMUG] mass GPS issues > > > Are you power cycling the whole Rack Injector? Doing a reboot? Or power > cycling the GPS source per Forrest’s instructions? > > > > I assume power cycling the whole Rack Injector would also drop power to > the GPS source. Not sure about a reboot. > > > > The ones I have fixed seem to be staying fixed. I had a Rack Injector > that was seeing only GLONASS satellites until its Syncbox was power > cycled, now it seems fine. Some people are reporting the problem seems to > be resolving itself over time, but I’ve seen no evidence of that. > > > > The cnPulse (Cambium Sync UGPS) that I had to power cycle is also doing > fine now, no recurrence. I’m attaching the GPS Sync information from the > AP. Some of the GPS Receiver information like model and software rev might > be useful to Forrest for comparison. > > > > > > > > *From:* AF <af-boun...@af.afmug.com> *On Behalf Of *Andreas Wiatowski > *Sent:* Tuesday, December 31, 2019 7:29 PM > *To:* AnimalFarm Microwave Users Group <af@af.afmug.com> > *Subject:* Re: [AFMUG] mass GPS issues > > > > Thanks Forrest, let us know what you find. I can confirm that I have done > the power cycle on the Rack injectors....we have seen the same issue occur > again...feels like interference. > > It has been suggested by some to switch to Autosync+Freerun to avoid loss > of client use...I guess it really depends on your networks reuse scheme. > > > *Internet.*** > ** > *Phone.****TV.* > > *Andreas Wiatowski* > > CEO/Founder > > Silo > > *1-866-727-4138, ext 600* <1-866-727-4138,%20ext%20600> > > | > > *andr...@silo.ca* > > *silo.ca* <http://www.silo.ca/> > > > > > > > > > On Dec 31, 2019, at 8:05 PM, Forrest Christian (List Account) < > li...@packetflux.com> wrote: > > > > [EXTERNAL] > > Just an update/random informational message, a lot of which is pretty > obvious from this thread: > > > > 1) As is pretty obvious at this point, something happened either with > the GPS constellation or with the firmware which runs in the GPS module, or > some combination of those. What many of you might not be aware of is that > many vendors use the same GPS modules from the same vendor. Generally a > certain portion of the uGPS, PacketFlux, ePMP all will use the same module, > along with other vendors. Each of the vendors (including PacketFlux) has > changed the exact model of the module over the years, for instance the > GPS+glonass modules are in newer devices, and GPS only are in older ones. > I'm working through determining whether this is just the GPS+GLONASS > modules which are affected (it seems like it might be the case), or if it's > a few different types. Note that because this seems like it might be > confined to a certain type (or types) of module, that it might turn out to > be only certain date/model ranges of each type of gear which are affected. > > > > 2) Restart of the module seems to clear the issue. For PacketFlux gear, > anyone with a SiteMonitor or RackInjector should be able to do this > remotely. In the SiteMonitor, the row on the binary tab is labeled > something like 'SyncPipe power'. There might be multiple rows depending on > how many SyncInjector/PowerInjectors you have - this corresponds to the > power port on each injector, so you'll have to turn off the row which is > for the unit which the GPS receiver is attached to. In the RackInjector, > it's a bit simpler since it's just a button on the GPS page. > > > > 3) I'm currently working through trying to find anyone who really knows > what went on here. None of the usual notification locations seem to have > any data. Probably too early to tell. I might luck out and be able to get a > GPS constellation recording I can replay here to replicate. > > > > One thing which might be helpful is for those of you who log this stuff, > if you can provide a pretty close UTC time that this occurred, along with > the approximate LAT/LONG, I might be able to correlate this with a specific > event. > > > > - Forrest > > -- > > AF mailing list > > AF@af.afmug.com > > http://af.afmug.com/mailman/listinfo/af_af.afmug.com > > ------------------------------ > -- > AF mailing list > AF@af.afmug.com > http://af.afmug.com/mailman/listinfo/af_af.afmug.com > > -- > AF mailing list > AF@af.afmug.com > http://af.afmug.com/mailman/listinfo/af_af.afmug.com > -- - Forrest
-- AF mailing list AF@af.afmug.com http://af.afmug.com/mailman/listinfo/af_af.afmug.com
