I have a couple of gps receivers (Trimble 4600 & 4700's) and for some reason they think today is 1996. Does anyone know what's going on?
Mr. Serling might know....
[MEDIA=youtube]If3SXJeZzMQ[/MEDIA]
Feb 17, 1996 was the last day of the Deep Blue vs. Kasparov chess matches, Kasparov winning 4-3. The machines are still apparently upset about this.
No, Mr. Serling doesn't know but I bet Jim Frame might know something. It appears that all old Trimble receivers might have a Y2K problem similar to their TGO office software. If that's the case I have quite a few electronic boat anchors in my office.
That is not a Y2K problem.
GPS week 0 began on 1/5-6/1980, there are 1024 weeks in the cycle, 0-1023.
On 8/21-21/1999 your receivers rolled over from week 1023 to week 0, because software was not replaced or was irreplaceable.. Your receivers are giving you a current date assuming 8/21-22/1999 was actually 1/5-6/1980. Assuming your receivers are still running on 4/28-29/2018 it will again revert back to 1/5-6-1980.
I am unsure if your data is affected by the increase in leap seconds or not, but the date is easily correctable.
Go to the Software & CAD forum and check out RINEX dates, that should do the trick for you.
Paul in PA
When you mentioned the Rinex files you're referring to the Post processing software, correct?
Paul, the problem isn't with the post processing software it's with the receiver itself. When I download the file that was stored in the receiver it shows a date of 1996, therefore it won't communicate with the CORS Stations. And it's not with just one receiver or one data collector. BTW I'm using TBC software not TGO.
Convert the downloaded file to RINEX, then correct the date. Then you can send it to OPUS or put it in your TBC. That means post processing only. You will definitely not get Trimble to upgrade your old receivers.
Paul in PA
Okay, I'll give it a try. Thanks for the input, Paul.
"Go to the Software & CAD forum and check out RINEX dates, that should do the trick for you."
The RinexDates will be off no help here, that's only for backdating date for TGO.
When you need to modify dates I suppose Teqc may do the trick, but I'm not sure about that.
If I understand well you have 2 receivers that act that way at the same moment ... strange ... excludes some possibilities: no death backup battery in the receiver.
Can you reset the date in the receiver using Trimble Winflash? Some other way to reset?
We'll probably will hear from more users with the same problem.
About RinexDates and the fast approaching leap day. Some people are currently testing version 1.8 because a new date offset is needed for processing data past 29th of febr. or 1st of march in TGO. New version will be available here in the RinexDates post on the Software & CAD Forum.
Christof.
If the prior suggestions don't get you going, look at the notes I made up for the Trimble 4000sst, including manually editing the RINEX file to fix the 1024 week problem.
https://dl.dropboxusercontent.com/u/25124076/Trimble4000sst_Notes.doc
What's weird about this is that it affects all three of my L1 4600LS receivers using a recon data collector. It also affects L1/L2 4700 receivers using the TSC-2 data collector. We get the same year in all four receivers, 1996. This happens when storing the files in the receivers. I have people in the field collecting data into the data recorders instead of the receivers and we'll see how that works. Our theory is that the recorders have the correct date and since the files are being downloaded they should work out okay.
If it affects my receivers than it must be affecting all Trimble receivers of a certain age.
With computers and circuit boards, most date problems occur because of an internal battery needing replaced.
A Harris, post: 358326, member: 81 wrote: With computers and circuit boards, most date problems occur because of an internal battery needing replaced.
While that is generally true, this particular problem is a rollover of the count of weeks at the power-of-two number 1024 because not enough bits were allocated to represent anything larger.
Okay, the latest news is that my receivers reverted to GPS week 0. However as a fix, when I use the data collector as a data logger (not logging in the receiver) the data comes in clean and I'm able to use it. I was wondering about changing the date in the receivers themselves but on second thought the receiver software probably can't handle a current date.
So, what we've found out is that in order to store the files in the receiver we would have download the files and than run the files through a rinex conversion program that changes the date on the sessions. Would rinexdates do that?
Hi,
No the RinexDates won't do that for you,
It reads the date/time stamp of the observations and in the navigation file and wil substract 6 years from the found date in the file.
You cannot specify the date offset.
RinexDates is a utility to fool the Trimble processor by backdating all files to be processed to a date before 16 september 2011.
Christof.
Bill93, post: 358312, member: 87 wrote: If the prior suggestions don't get you going, look at the notes I made up for the Trimble 4000sst, including manually editing the RINEX file to fix the 1024 week problem.
https://dl.dropboxusercontent.com/u/25124076/Trimble4000sst_Notes.doc
Trimble 4000SST! Holy Crap!
This is the service announcement from Trimble
TRIMBLE 4700/4800 GPS RECEIVERS
WILL STOP WORKING PROPERLY STARTING FEBRUARY 14, 2016
Summary
On February 14, 2016, Trimble 4700 and 4800 GPS receivers, that are long obsolete and end of service, will start
experiencing erratic and unreliable behavior for time and date reporting. As those receivers will interpret the GPS
time in error by 1024 weeks, receiver data outputs will have the wrong time reference. This will negatively impact
subsequent systems that are communicating with that receiver, including the rejection of data packages. Real-Time
Kinematic operation (RTK) operation is not expected to continue working properly.
Newer Trimble GPS/GNSS receivers types, including Trimble 5700/R5/R7/NetR9 Geospatial/NetRS/NetR5, Trimble
5800/R2/R4/R6/R8/R8s/R10/R10LT with current firmware are not impacted by this.
Resolution
Unfortunately, there is no technical solution available for for Trimble 4700 and 4800 GPS receivers to correct this
issue. For Trimble 4700/4800 GPS receivers still in use, please work with the end-user on a receiver replacement
solution towards a new or more recent GNSS receiver system.
MISSOURIMULE, post: 358242, member: 9473 wrote: I have a couple of gps receivers (Trimble 4600 & 4700's) and for some reason they think today is 1996. Does anyone know what's going on?
TRIMBLE 4700/4800 GPS RECEIVERS
WILL STOP WORKING PROPERLY STARTING FEBRUARY 14, 2016
Summary
On February 14, 2016, Trimble 4700 and 4800 GPS receivers, that are long obsolete and end of service, will start
experiencing erratic and unreliable behavior for time and date reporting. As those receivers will interpret the GPS
time in error by 1024 weeks, receiver data outputs will have the wrong time reference. This will negatively impact
subsequent systems that are communicating with that receiver, including the rejection of data packages. Real-Time
Kinematic operation (RTK) operation is not expected to continue working properly.
Newer Trimble GPS/GNSS receivers types, including Trimble 5700/R5/R7/NetR9 Geospatial/NetRS/NetR5, Trimble
5800/R2/R4/R6/R8/R8s/R10/R10LT with current firmware are not impacted by this.
Resolution
Unfortunately, there is no technical solution available for for Trimble 4700 and 4800 GPS receivers to correct this
issue. For Trimble 4700/4800 GPS receivers still in use, please work with the end-user on a receiver replacement
solution towards a new or more recent GNSS receiver system.
