I have had two owners of Sokkia/Ashtech Locus GPS receivers contact me within the last 10 days or so saying that their receivers appear to be working perfectly in the field but when they bring the data from the receivers into the post processing software, the files show that they were collected in 1997.
I do not know exactly when this issue first manifest but correlating the Julian dates on the files from Locus receivers with the date problem and Promark2 receivers without the problem, it would appear that the GPS second counter reached its maximum capacity and reset around September 11, 2016.
if you have Locus receivers and have experienced this problem, I do not have a fix like the one posted on here for the older Trimble receivers. But there is a solution. If you have a Promark2 or Promark3 receiver, you can include one of those units in the sessions you are running with the Locus receivers. After you have downloaded the data from the Locus and the Promark units, duplicate one of the "e" files from the Promark, making as many copies as Locus files you have. Replace the "e" file for each Locus session with one of the copies you made, being careful to exactly duplicate the name of the file you are replacing. Then process as normal.
Should it be the case that you only have Locus receivers, you cause is not lost. Go on line to the NGS CORS download page and download CORS data for the day of your GPS occupations. Using the RINEX converter, make Ashtech format files from the CORS files. Then do the same operation as outlined above for replacing the "e" files for each Locus session with a copy of the "e" file from the CORS data.
JerryS, post: 402417, member: 205 wrote: I have had two owners of Sokkia/Ashtech Locus GPS receivers contact me within the last 10 days or so saying that their receivers appear to be working perfectly in the field but when they bring the data from the receivers into the post processing software, the files show that they were collected in 1997.
I do not know exactly when this issue first manifest but correlating the Julian dates on the files from Locus receivers with the date problem and Promark2 receivers without the problem, it would appear that the GPS second counter reached its maximum capacity and reset around September 11, 2016.
if you have Locus receivers and have experienced this problem, I do not have a fix like the one posted on here for the older Trimble receivers. But there is a solution. If you have a Promark2 or Promark3 receiver, you can include one of those units in the sessions you are running with the Locus receivers. After you have downloaded the data from the Locus and the Promark units, duplicate one of the "e" files from the Promark, making as many copies as Locus files you have. Replace the "e" file for each Locus session with one of the copies you made, being careful to exactly duplicate the name of the file you are replacing. Then process as normal.
Should it be the case that you only have Locus receivers, you cause is not lost. Go on line to the NGS CORS download page and download CORS data for the day of your GPS occupations. Using the RINEX converter, make Ashtech format files from the CORS files. Then do the same operation as outlined above for replacing the "e" files for each Locus session with a copy of the "e" file from the CORS data.
Jerry,
I processed 13 Locus (3 units and 6 sessions) observations run on Friday with the 97 in the file names. They processed fine with the E-files that were downloaded. To check, I did the CORS download, converted to Ashtech rinex, renamed the files, overwrote the old files, and reprocessed. Same end coordinates.
Mitch
Mitch, post: 402554, member: 7176 wrote: They processed fine with the E-files that were downloaded
As long as all the files share the same nominal date (and the date is correct except for the 1024 truncation), I think they'll always process without incident. The trouble comes in when you mix nominal dates between receivers.
Thank you. I still have 2 of them.
Thanks, Jerry! I ran into that a couple of days ago and thought I was going crazy.
Craig, glad to hear that those Rx's are still making you money !
I should have noted that this will only matter if:
1: you are attempting to process Locus receiver files with files from other receivers collected at the same time, or if not mixing with other receiver files,
2. you actually care if the dates are correct.
If you do not care that you are being transported back to 1997 to a time shortly after whenever the Locus clock began, it will be no problem whatsoever. But if you are using CORS data, for example, to constrain your processing to known control, then you will have to account for the date issue. The fix is not as elegant as the fix for the Trimble 4400(?) units that were manifesting a similar condition but it does work.
My Trimble 5700 started doing that the other day. Makes no difference in the post processing on this end.
Interesting. I may have to fire up my Hiper Lites this weekend, and see if anything wired happens. They are 2002 era if I remember correctly.
Dale, post: 402622, member: 6246 wrote: Craig, glad to hear that those Rx's are still making you money !
Hi Dale,
They're working great. I've got a full-time position with another company now, so I don't use them much any more, but I've never had any problems with them. I hope you're keeping warm up there in the great white north!
JerryS, post: 402699, member: 205 wrote: I should have noted that this will only matter if:
1: you are attempting to process Locus receiver files with files from other receivers collected at the same time, or if not mixing with other receiver files,
2. you actually care if the dates are correct.
If you do not care that you are being transported back to 1997 to a time shortly after whenever the Locus clock began, it will be no problem whatsoever. But if you are using CORS data, for example, to constrain your processing to known control, then you will have to account for the date issue. The fix is not as elegant as the fix for the Trimble 4400(?) units that were manifesting a similar condition but it does work.
I was processing mine with an X-90 receiver and realized my data didn't work with the total station shots by about 3 feet. When I saw the 1997 date on the file, I thought I had the wrong one; but after checking again and realizing it was the correct file, I thought it must have been corrupted. I'm happy to know there is a fix for the problem.
PM3s worked superfantastic yesterday.
Try this utility "FixRnxDate"; it should fix the date automatically
www.geomatics.us/products/fixrnx/
Sent from my iPad using Tapatalk
