GNSS Issues October 1 2019
Several reports of anomalies yesterday (Monday 30 Sept 2019) and today (Tuesday 1 October 2019).
- SP80: these receivers track, then loose tracking, then reset engines if running firmware prior to 3.39. So firmware update is mandatory and fixes issue.
- Some Trimble Engines: we have observed BD970 engines with older (~5.25) not floating or fixing. An engine reset with new ephemeris download appears to fix these and they continue working well.
- ProMark 500’s (in USA and South America) are seeing a ‘215’ error after booting. There is a chance that turning off GLONASS tracking (in SurvCE see ‘Equip: GPS Rover: Receiver (tab): Advanced’) will fix this issue.
- More than two, and probably all Spider based network servers, are reporting GLONASS related issues with advisories to switch to GPS only.
I can’t find any buzz online yet, but enough direct complaints to know there is an issue.
We reach peak complexity again.
Interesting, thanks for the update. No issues with the other constellations?
I am not smart enough to put my finger on anything other than my email and phone getting hot. I believe it is GLONASS ephemeris related, however there are not notices on the GLO status page (at least that I understand.)
I was able to personally verify the SP80 behavior because I had a head that had not been updated. After update works great. Verified on 5 other heads by customers, so far.
I got reports from 3 users in the USA and one in SA about the ProMark 500 215 error. I have not had a working PM500 for a very long time so I can't verify or offer any assistance.
Hopefully putting this note here and on my [ blog] will shake out some smart guys who know what is up. Or someone will tell me nothing is wrong and I can delete it all.
Thank you Mark, for who you are and what you do for all of us.
I was running Trimble R10's today as base/rover, for about an hour no problems but these are only about 4 months old.
I can speak a little to the Leica "Spider" (Network software) side of things.
Our network (ReIL-NET) went "down" at 10am central time yesterday. The issue was with the GLONASS Ephemeris. All networks have received a "fix" from Leica today.
I personally don't know the details of what caused the problem yet, just the solution.
Base and Rover Leica instruments were not affected.
We run a spider server and noticed a Glonass ephemeris issue with 4 sv's in our logs starting yesterday. My field crew did not tell me it was a problem but then we also use galileo.
(I know that @gshrock will disagree with this statement 😀 ):
"When ever anyone has a bad day, they always blame the equipment (and the equipment dealer). Nobody ever expects that it is the network or interference on the UHF frequency or some external problem."
In this case I got essentially simultaneous calls from network users in four states, plus a 1/2 dozen SP80 users, plus a few customers running 4+ year old OEM Firmware. Like I said, if I were smarter I would have immediately figured out what all the underlying things were and tied this up in a neat little ball. But when the calls start, they dribble in. And we get calls every day, all the time. So you have to have a feel for 'more than usual.'
I should have mentioned that all of the network bases and network check stations that I am running were just fine. (So you can read that as "equipment based on T OEM engines with current firmware had no issues. I should mention that I am quite liking the 5.43 release?)
I was having some issues this morning getting a fix, of any kind (when it did fix, it was a poor fix). I should note that I have the Carlson BRx6+ GPS unit, should I be looking for a firmware update or just be patient on GLONASS?
I was using a base rover Trimble R10 today and it seemed like I was tracking less satellites today, its not uncommon to have 18 to 21 and today it was more like 9 to 12. I didn't bother to figure out what if anything was missing as it was still working fine.