GPS Autonomous Only

RTK, presumably? What dc software, make, model?

There was a leap second added to the end of the year. You may need a firmware upgrade, or maybe just collect long enough to download a new emphemeris.

He is using Topcon gear and works for local gov't (county), more than likely they did NOT upgrade the firmware.

Seems like MNDOT VRS is having problems, they are going to reboot their system at 11:30.

Problem resolved by changing from multiple base solution to single base solution. Why? I don't know. Someone else figured it out.

I don't think there is a switch for that. When the software finds multiple base radios on the same radio frequency and protocol this option will prompt the end user to make a selection.

What model GPS and radio type were you using?

I think he was talking about a single baseline vs. VRS

leegreen, post: 407302, member: 2332 wrote: What model GPS and radio type were you using?

Topcon HIPER SR. I don't know what radio type we use. We use L-Net ( a TopNET GNSS Network) for our RTK network.

You have no radio. You are using a modem to get corrections from a network. Must of had multiple mount points, and selected wrong one.

Did you upgrade the firmware for leap second correction?

Topcon strongly urged that everyone with late model receivers install the new firmware update to accommodate the leap(extra) second added before 2016 GPS time officially became 2017 GPS time. This is not a new phenomenon, the most recent previous having occurred at the end of June, 2015, I believe I read.

The official word was that you HAD to do the firmware update. I have started multiple different models of Topcon receivers without doing the firmware update. The seem to got to work pretty quickly with clearing the NVRAM and resetting RTK.

There are probably other reasons to do the firmware update. But it seems to not have been as essential as was suggested. I have not tested for positional accuracy but others have.

JerryS, post: 407379, member: 205 wrote: Topcon strongly urged that everyone with late model receivers install the new firmware update to accommodate the leap(extra) second added before 2016 GPS time officially became 2017 GPS time. This is not a new phenomenon, the most recent previous having occurred at the end of June, 2015, I believe I read.

JerryS,

Have you seen any leap second issues with Topcon Hiper Lites, that no longer have firmware updates?

JerryS, post: 407379, member: 205 wrote: The seem to got to work pretty quickly with clearing the NVRAM and resetting RTK.

How do you clear the NVRAM?

leegreen, post: 407369, member: 2332 wrote: Must of had multiple mount points, and selected wrong one.

I'm pretty sure MAGNET automatically selects the correct mount points. Will check tomorrow.

leegreen, post: 407369, member: 2332 wrote: Did you upgrade the firmware for leap second correction?

No. Will discuss with my Field Crew Supervisor tomorrow.

We had the same problem here in the Springfield, Missouri area. MoDOT added the Leap second and everyone was shut down. Went ahead and gitvthe firmware update fron my dealer. MoDOT reset the system and the problem seems to get fixed.

Good luck.

leegreen, post: 407385, member: 2332 wrote: Have you seen any leap second issues with Topcon Hiper Lites

One of my Hiper Lites refused to light up Tuesday morning. I took it into service today. The service guy at PPI said that there were no Firmware issues with the Hiper Lites related to the leap second or anything else. Still, it's quite a coincidence after all these years.

leegreen, post: 407171, member: 2332 wrote: He is using Topcon gear and works for local gov't (county), more than likely they did NOT upgrade the firmware.

The firmware has now been upgraded. MAGNET has been upgraded too. We are able to quickly connect to the network. No more frustration!

The firmware has now been upgraded. I don't know what the upgrade was. MAGNET has been upgraded from version 3 to version 4. We are able to quickly connect to the network. No more frustration!