Yes, that is correct.I received an email that topcon users must arrange for an additional update to accommodate the end of year leap second correction.
I presume that J-Field has updated for this problem...Is that correct?
I have revised the work with leap seconds in J-Field and found that it was done in an unreliable way. It uses almanac data to read the number of leap seconds. It should work OK if you start the LS device after midnight January 1 GPS time. But J-Field will have a wrong (+1 sec) UTC time for some period of time if the device is already running. So I have improved the logic related to leap seconds. Now J-Field is using internal algorithm instead of GPS almanac to calculate the leap seconds. PreRelease version with the fix is 2.0.5.667. If the version is OK we will Release it today.Do we need to do anything, ie download, and update firmware, or is it already taken care of automaticly?
If we need to do something, then, what should we do, and when?
Thamks, and keep up the good work!
Nate
It is better to wait a little. We are double checking the version now. We will release the version soon.PreRelease version with the fix is 2.0.5.667.
So, move to this version, and we are good?
Does this version also fix the tilt sensor calibration bug?
PreRelease GNSS 3.6.9.161229 fixes the calibration bug. We will move the GNSS FW version to release together with J-Field.Does this version also fix the tilt sensor calibration bug?