None of my L-Band Facet Units (V3.9) are receiving PP Corrections for several days now, located in the Southeast US.
Is there a website to check the PP System Status ?
None of my L-Band Facet Units (V3.9) are receiving PP Corrections for several days now, located in the Southeast US.
Is there a website to check the PP System Status ?
https://thingstream.statuspage.io/
How old are your keys? Do you see the triple satellite dish icon indicating L-Band decryption? What version of the firmware are you running?
Last set of L-Band keys would have expired Oct 7, current set are good Oct 8 - Nov 11
The problem was an issue with the FacetLB’s not using the 2’nd Month’s Key.
u-Blox / ThingStream issue the L-Band keys in pairs, so typically got 5-8 weeks usage per query.
The time of validity is scoped in the u-center / json configuration scripts.
The keys can be cached. I think you can push both into the receiver, and it will discard the stale one from the first slot once it expires.
The keys can be tested, the SPARTN GAD packets being ones that are particularly easy to walk / check due to form and repetition.
I had an issue today on a new Facet L-band. It worked fine last week. This morning it said the keys were still good for 24 days, but it never once tried to go into RTK Float or Fix. Best it ever got was .250ish accuracy, DGPS Fix type.
After about 30 minutes of trying I saw this post and I ended up resetting it to force it to download new keys. Luckily I had service for my hotspot because the reason I got an L-band is I’m almost never in a good cell coverage area when I work. Once I got that all set back up and rebooted it it got new keys again and was in RTK Fix within a minute. Actually got the best fix I’ve gotten since I had it at .015 (I’m also almost always in the woods) so that was nice. But I can’t really come to any other conclusion other than it’s just not using the second key once the first expired.
I’m on the newest firmware I believe (3.9).
jothite:
I’m on the newest firmware I believe (3.9).
It’s my understanding that this was corrected in 3.10
I see… that firmware has been out longer than I’ve had the unit. I could have sworn I tried to update it when I first used it too. Well, still glad it’s fixed. Thanks.