Ashtech locus

[land butcher]

Yeah I know but we use them 2 or 3 times a year and they have worked fine until today

Instead of todays date the file date is 4-17-1997 and it don't like that. Anyone have a suggestion

Thanks

[laveyb24]

Your firmware is out of date and needs to be upgraded. There are a few previous threads on this forum if you search.

[land butcher]

Yes, the date code is the issue.
Searching for Ashtech doesn't find any threads that mention this issue, if you know of one I would appreciate the link. Or if anyone knows how to upgrade the date code that would help too. Ashtech dropped support for these years ago and Ashtech was absorbed by Trimble.

[Johnston]

I don't know about your specific issue, but I've seen a fair amount about making older gear function at this site:

https://rplstoday.com/community/

[land butcher]

Thanks, I think my son searched that site.

Kind of ticks me off as these are great units for what we do. Just download and hit solve, no weighing of vectors, and before I bought them I tested them on some OCS gps points with spot on results with one hour of static. They get 100 hours of use on 4 d cells so no $100 special battery every few years and if it needs a battery they are readily available.

[laveyb24]

Hope this is helpful. I had the same issue with some of trimbles older units.

http://clsaforum.californiasurveyors.or ... f=6&t=6614

[Jim Frame]

Even if there's no fix for the file as collected by the receiver, you can always convert to RINEX and edit the dates. It may also be possible to modify the RINEX file using teqc and the -week option, but I haven't verified this.

[land butcher]

Thanks we will check that out.

[Jim Frame]

Jerry Shearon of Hays Instrument posted this on the RPLS Today board:

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.

Here's a link to the thread, though I don't know if it'll work if you're not logged into the board:

https://rplstoday.com/community/threads ... us.328997/

[land butcher]

Thanks. My son went into the files and changed the date and it worked, but that was a lot of work as there are numerous places the date shows up in each file.