MenuSpatial Technologies

Our Team

Preparing for Leap Second: Part II How does Leap Second affect your Leica Geosystems instrument?


This is part 2 of a 3 part series about Leap Second 2016, scheduled to take place 31 December 2016.

In our last Leap Second 2016 post, we discussed what a leap second is and how it affects you. In this post, we’ll provide all the information you need to ensure your Leica Geosystems GNSS/GPS solutions works seamlessly throughout the event.

First and foremost, it is critical that you have updated your instrument with all the latest updates. You should be receiving automatic notifications when these updates are available. To check that you have the latest update, please contact Spatial Technologies.

“We have carefully prepared for the upcoming leap second, and we are confident all our GNSS/GPS solutions will work throughout the event,” said Markus Roland, Leica Geosystems product manager GNSS Networks and Reference Stations. “All our latest released product versions have been tested to work properly before, during and after the event of leap second introduction with multi-GNSS constellations, including GLONASS. We have also supplied detailed information to our local representatives for legacy instruments.”

Leica GRX1200 Series (System 1200)

 

With the recommended firmware version, the tracking behavior for GPS and Galileo of all Leica GRX1200 Series receivers will not be affected over the leap second change. GLONASS tracking will lose lock briefly and recover a few seconds later.

If a Leica GRX1200 Series was turned off during the leap second change and is used after the leap second switch, the receiver will have trouble tracking GLONASS signals until a new almanac is downloaded, which can take up to a few minutes. A measurement engine reset (initialisation) will resolve the problem faster and enable you to track GLONASS satellites again.

Leica GX1200 Series (System 1200)

With the defined SW and ME FW version, the tracking behavior for GPS and Galileo of all Leica System 1200 and GPS 900 receivers will not be affected over the leap second change. GLONASS tracking will lose lock briefly and recover a few seconds later.

If a Leica System 1200 or GPS 900 receiver is used after the leap second switch, the receiver should have no trouble tracking GLONASS signals. If there are nevertheless problems tracking GLONASS satellites, an ME reset will resolve the problem faster. In order to perform an ME reset press 5 Config → 2 Instrument Settings → 2 Satellite Settings → shift F4 INIT.

Leica Viva GS Series – SmartWorx and Captivate

captivateCollageNafta_Height_445

With the defined SW and ME FW version (6.402 for GS08, GS12 amd GS08plus; 1.13(46) for GS05 and GS06; 2.127 for the GX1200; 3.823 for ATX1200; 6.112 for GPS900 and GS09), the tracking behavior for GPS, Galileo and BeiDou of all Leica Geosystems GS receivers will not be affected over the leap second change. GLONASS tracking will lose lock briefly and recover a few seconds later.

If a Leica GS receiver is used after the leap second switch, the receiver should  have no trouble tracking GLONASS signals. If there are nevertheless problems tracking GLONASS satellites, restart the receiver.

Leica Infinity and Geo OfficeLeica Infinity


 

 

 

 

Infinity retrieves and automatically stores  the information about new leap seconds as soon as mdb or RINEX are imported. No extra work is required by the user.

Geo Office retrieves and automatically stores the information about new leap seconds as soon as mdb are imported. No extra work is required if you import an mdb data set at least once. If you only use RINEX data, the new leap second will not be considered automatically. In this case, your must install a registry key file to make this information available to LGO (download this file here, copy to the LGO machine, unzip and double-click on the *.reg file).

If data are correctly acquired, stored and exported from the receiver, the post processing will not be impacted by the introduction of the new leap second.

 

Leica Zeno

Zeno 20 HW

With the defined SW and ME FW version (3.3 for Zeno 5; 1.13(46) for Zeno 10 and Zeno 15; 6.403 for Zeno 20, CS25, CS35 plus, CS25 GNSS plus ad GG02), the tracking behavior for GPS and Galileo of all Leica Zeno devices will not be affected over the leap second change. GLONASS tracking will lose lock briefly and recover a few seconds later.

If a Leica Zeno device is used after the leap second switch, the receiver will have trouble tracking GLONASS signals until a new almanac is downloaded, which can take up to a few minutes. A receiver reset will resolve the problem faster and enable users to track GLONASS satellites again.

 

Leica iCON

Leica iCON gps 60

With the defined SW and ME FW version (3.0.4 for iCON gps 60 and iCON gps 80), the tracking behavior for GPS, Galileo and BeiDou of all Leica iCON receivers will not be affected over the leap second change. GLONASS tracking will lose lock briefly and recover a few seconds later.

If a Leica iCON receiver is used after the leap second switch, the receiver will have trouble tracking GLONASS signals until a new almanac is downloaded, which can take up to a few minutes. A Reset Almanac will resolve the problem faster and enable users to track GLONASS satellites again.

In case of tracking issues, Settings > System Configuration > Reset options > Reset Almanac on the receiver to clear almanacs and track GPS only until a new almanac has been received.

 

Leica Redline

With the defined SW and ME FW version (6.80 for Redline PowerBox; 3.823 for Redline PowerAntenna), the tracking behavior for GPS, Galileo and BeiDou of all Leica Redline receivers will not be affected over the leap second change. GLONASS tracking will lose lock briefly and recover a few seconds later.

If a Leica Redline receiver is used after the leap second switch, the receiver will have trouble tracking GLONASS signals until a new almanac is downloaded, which can take up to a few minutes. A ME reset will resolve the problem faster and enable users to track GLONASS satellites again.

In case of tracking issues, initialise the almanac to clear almanacs and track GPS only until a new almanac has been received.