I cranked up my Topcon Hiper Lite Rover this morning and collected a point while connected to the FDOT RTN without a problem. However, when I set up my Base unit to do some RTK observation, the data collector kept saying no GPS position at the base. I then noticed that it was having problems tracking on the base unit. It was indicating that it was only tracking 3 sats while the rover was tracking 8-9 at the same time right next to it. I cleared the NVRAM on the base and let it run for 20 minutes to get a new almanac. After that it was fine. Strange that both my units are the same model running the same firmware, but only the base had a problem.
Cleared the NVRAM out of my ancient of days HIPER GGD, downloaded an new almanac and checked on a few few published monuments, now I'm good to go!
You know, for some reason, I fell out of bed about that time . Do you think that it's related?
We have a HiperII system with our own base and it wouldn't work on Jan. 4th. It wouldn't fix even though I had 12 sats and 100% radio link with the base. I cleared the NVRAM and turned Glonass off. I then set them outside for a half hour, turned Glonass back on and everything is fine. I first tried loading new firmware but couldn't get that to load.
MightyMoe, post: 407144, member: 700 wrote: I wouldn't expect to see anything at all, I can't see how this could mess with a GPS receiver.
Leap seconds are like Y2k bugs. Mostly fear. There are more problems still lurking with collecting at weeksecond roll over than a leap second. Gps week number roll over (wk 1024) didn't seem crash things.
