Trimble 5700 / R7 date log file is 2004, not 2023. how to set receiver time and date?

I always thought the receiver's data/time stamp was part of the data stream from the atomic clocks in the satellite system.  The local time should be in your TSC2 settings.

Could it be that the firmware for the 5700 is outdated?  I remember some discussion about that several years ago.

You cannot set the date and time, it is decoded from the satellite stream. The data in the 5700 is week number (since 1/1/1980) and then seconds of the week. The week number in older receivers "rolls over", so the date is wrong but the time is correct. I created a program to fix the dat file by changing the week number to the correct value, but I think Trimble did as well sometime later. 

One easy solution is to convert the file to rinex and change the date there using a text editor (not a word processor). 

The 5700 probably has a small battery inside that is no longer functional. It's purpose is to keep the settings when you turn off the unit. Without the battery, you turn off the unit and the year reverts to the year it was manufactured.

@cerolli I don't believe it would do that, once it locks on to the SV's it knows the week number mod 1024. And that is the problem, it is not sure what 1024 week sequence it is in. If it were to reset to week 0 it would be Jan 1980

One easy solution is to convert the file to rinex and change the date there using a text editor (not a word processor). 

This will most likely work. I have a similar date issue with old Ashtech units and this is how I fix the data file.  Easy search and replace of the date; the times are accurate. 

Search “gps time rollover” for more info. 

I use a gps time calculator (search for one) to confirm that the incorrect date is 1024 weeks (or a multiple of 1024) off from the date I collected the data. 

When converting to RINEX you can use the option as -week 2345  or whatever the correct week number is, and not have to do any editing. When editing it is easy to mess up tje critical spacing.

@bill93 Thanks for that tip, Bill. I had never tried that. 

I still have some older receivers that have this issue (2 4700's, 2 5700's), but have not used them for at least a couple of years since I built up my stock of newer receivers. 

John,

I tried to convert the collected file, with the wrong date and it failed. See Below.

"Cannot convert file Z:Static GPS Data - 2023223304tbm.t01 Unsupported raw-data file format, or file reserved by another process. Adding file 223310tbm.t01...Error Cannot convert file Z:Static GPS Data - 2023223310tbm.t01 Unsupported raw-data file format, or file reserved by another process."

I got with NEI from Lafayette and they are working with Trimble to see if they can correct the files. I have my doubts. You mentioned a program that corrects the file. Is it available for me to try?

Thanks,

george@collinslandsurveyors.com

You don't say what software gave you that error, but I assume it was when you tried to convert to rinex using teqc or something similar. You can use the trimble free utility converttorinex, or you will need to first convert the .t01 file to a .dat file using runpkr00 (also free from Trimble).

My program only works with .dat files. At the time I wrote it, that was fine because it handles GPS and GLONASS and that was all I was tracking. So it is OK to do that with a 5700 file. My program will not work with .t01, .T02, or .T04 files because I do not have the schema for those files and Trimble does not release that info.

Your best option is to use convertorinex and then edit the dates. Or, if you want to use my program after converting to .dat, here is a link... https://we.tl/t-tyL6b1JLgp. Unzip and run setup, then run fixweek.exe

I did some digging and found an article from 2019 by UNAVCO that outlines this issue. It also has a solution info for the 5700

https://kb.unavco.org/article/preparing-gps-gnss-receivers-and-hardware-for-the-april-6-2019-gps-week-number-rollover-wnro-867.html

But I am experiencing this same thing with my R8 Model 2's and TSC2 running Survey Controller. I understand the workaround but it seems the only way to address the issue with the receiver is to update the firmware.

Does anyone know where to obtain firmware for these models? I'm currently running 3.30. I tried the dealer but they've told me that they are outside of their usable life. Although I know they have a lot of life left in them!

john-hamilton puede volver a dar link de descarga porque caduco

He said,

Can you give the download link again because it has expired?

I had the same issue with my R8 Model 2's, it is related to the GPS rollover. The fix is to upgrade to firmware version 4.43 if your warranty date is April 2011 or later. My warranty date wasn't current so my Trimble representative provide me an activation code so I could update my firmware.