Trimble 5700 / R7 date log file is 2004, not 2023. how to set receiver time and date?
Quote from alnairtuleon on August 30, 2023, 2:28 amhello,
i have trimble 5700,
when doing static logging, the file log date is 2004.
i have tried to connect to receiver via GPS CONFIGURATOR, TSC2 Controller software, but I cannot find the menu to change time and date for receiver local time.
[attach]21510[/attach]
any idea how to change receiver time and date?
thanks
hello,
i have trimble 5700,
when doing static logging, the file log date is 2004.
i have tried to connect to receiver via GPS CONFIGURATOR, TSC2 Controller software, but I cannot find the menu to change time and date for receiver local time.
any idea how to change receiver time and date?
thanks
Quote from kevin-hines on August 30, 2023, 12:24 pmI 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.
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.
Quote from T Ford on August 30, 2023, 12:37 pmCould it be that the firmware for the 5700 is outdated? I remember some discussion about that several years ago.
Could it be that the firmware for the 5700 is outdated? I remember some discussion about that several years ago.
Quote from john-hamilton on August 30, 2023, 12:55 pmYou 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).
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).
Quote from cerolli on August 30, 2023, 11:07 pmThe 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.
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.
Quote from john-hamilton on August 31, 2023, 1:02 am@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
@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
Quote from toeknee on August 31, 2023, 2:41 am[quote data-userid="550" data-postid="624511"]
One easy solution is to convert the file to rinex and change the date there using a text editor (not a word processor).
[/quote]
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.
Posted by: john-hamiltonOne 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.
Quote from bill93 on August 31, 2023, 11:40 amWhen 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.
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.
Quote from john-hamilton on August 31, 2023, 12:59 pm@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.
@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.
Quote from George2 on September 14, 2023, 6:51 pmJohn,
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,
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,