Notifications
Clear all

GPS y2k problem

136 Posts
42 Users
0 Reactions
14 Views
(@geo_xxl)
Posts: 33
Registered
 

90 days for battery ... is it internal? How much it cost to change it?

I heard that this is the best available from the Trimble Clone family 🙂

 
Posted : 24/02/2016 12:35 am
(@geo_xxl)
Posts: 33
Registered
 

MISSOURIMULE, post: 359225, member: 9473 wrote: I don't have a 5700 but if you download into a data logger like the TSC-2 the current date in the data logger may eliminate the problem.

Try to get the winflash from unavco ...

 
Posted : 24/02/2016 9:10 am
(@mightymoe)
Posts: 9920
Registered
 

Here's what I know so far, the 5700's work as a base for base rover, been a while since I've used one as a rover for topo, but they are great on a four-wheeler. They don't work as a static unit now, I haven't used my 4700 yet, but I assume it also works as a base for a base rover set up, as far as static I assume it's also trashed, the dealer is getting slammed with irate users,,,,,,,,,, so I hear,,,,,,,,,,, maybe, just maybe this time they will help.

 
Posted : 24/02/2016 9:45 am
(@dan-patterson)
Posts: 1272
Registered
 

MightyMoe, post: 359460, member: 700 wrote: Here's what I know so far, the 5700's work as a base for base rover, been a while since I've used one as a rover for topo, but they are great on a four-wheeler. They don't work as a static unit now, I haven't used my 4700 yet, but I assume it also works as a base for a base rover set up, as far as static I assume it's also trashed, the dealer is getting slammed with irate users,,,,,,,,,, so I hear,,,,,,,,,,, maybe, just maybe this time they will help.

I've already bailed.....going with a different static receiver. I also was a long time user of the 5600 series robot, but I switched over to Leica a couple years back. It seems like Leica is VERY popular around here, and I am seeing fewer and fewer Trimble users. I used to really love their gear, but I've gotten tired of all the BS and being nickel and dimed over and over.

 
Posted : 24/02/2016 10:02 am
(@kent-mcmillan)
Posts: 11419
 

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?

I'd been tied up with other things and just today had a chance to test my 4600 receivers. Interestingly, by the GPS week rollover to a date in 1996, the date glitch that prevented GPSurvey and TGO from doing baseline processing is now fixed. The baseline processor thinks it is 1996 again and generates solutions perfectly well.

I'll have to check the 4000ssi units to see whether they also think its now 1996. Odds are they do and, if so, they'll need to have the GPS week in their files corrected for submission to OPUS. All in all, there are much worse problems to have.

 
Posted : 24/02/2016 1:04 pm
(@john-evers)
Posts: 144
Registered
 

Kent,

Thanks to your discovery regarding TGO and GPSurvey, they will probably hurry up and offer a firmware update to correct the date fields so OPUS submissions work again.

Of course that would nullify your nice little discovery. I have never before heard of "dead" software coming to life again.

You made my day.

 
Posted : 24/02/2016 3:08 pm
(@kent-mcmillan)
Posts: 11419
 

John Evers, post: 359549, member: 467 wrote: I have never before heard of "dead" software coming to life again.
You made my day.

Yes, it's pretty great to have the baseline processor in GPSurvey and TGO working without needing to backdate the dat files. Christ Lambrecht's RinexDate software has been an excellent workaround, but it's still slicker (until shown otherwise) to just run the dat files right from the receivers.

 
Posted : 24/02/2016 3:47 pm
(@jimmy-cleveland)
Posts: 2812
 

Dan Patterson, post: 359294, member: 1179 wrote: Just ordered a CHC X-90 OPUS from iGage. I just need something very simple to run OPUS & OPUS-RS as network RTN checks

Dan,

I have two of these units, and they are awesome. I get great results with them. The download utility is simple to use, and Mark Silver is great for customer support. I bought my first one back in December of 2013, and my second one in April of 2014. If you have any questions, feel free to contact me.

I use them in conjunction with my two Topcon Hiper Lite units for static pairs, and also while running RTK for setting static points while collecting static data with my RTK base.

Jimmy

 
Posted : 24/02/2016 3:55 pm
 ddsm
(@ddsm)
Posts: 2229
 

Jimmy Cleveland, post: 359561, member: 91 wrote: Mark Silver is great for customer support.

:good::good:

DDSM:beer:

 
Posted : 24/02/2016 5:38 pm
(@in-the-sandpit)
Posts: 50
 

Kent McMillan, post: 359508, member: 3 wrote:
I'll have to check the 4000ssi units to see whether they also think its now 1996. Odds are they do and, if so, they'll need to have the GPS week in their files corrected for submission to OPUS. All in all, there are much worse problems to have.

For some reason (probably because they hadn't considered planned obsolescence as a sales strategy at the time), the 4000 series are working perfectly. At least a 4000SSE I tested was, so I expect the SSi units will.

 
Posted : 24/02/2016 9:46 pm
(@timyoung)
Posts: 12
Registered
 

I am not getting FixWeek to install under XP - it tells me that system files need updating and offers me the opportunity to do so and reboot (I assume it is msvbvm60.dll that is the issue, since it stops on the last file). When I do so and try to install again it just takes me round the same route again. Is it just a case of installing that file manually?

 
Posted : 25/02/2016 4:00 am
(@timyoung)
Posts: 12
Registered
 

TimYoung, post: 359597, member: 9639 wrote: I am not getting FixWeek to install under XP - it tells me that system files need updating and offers me the opportunity to do so and reboot (I assume it is msvbvm60.dll that is the issue, since it stops on the last file). When I do so and try to install again it just takes me round the same route again. Is it just a case of installing that file manually?

Installed FixWeek on another machine to work around this problem - and it appears to have worked fine.
Move the converted file back to my XP field computer.
Used Trimble convert to rinex on the ammended file.
Used Rinexdates on the rinex files generated and the Ordnance Survey network Rinex file downloads
Imported those in TGO - Rinex files imported and showed the appropriate same time range in 2010
Tried to process GPS baselines - failed, no wave solutions generated. The error messages simply say the baselines were not solved.

So - a piece of the jigsaw is still missing? A problem with the navigation file maybe?

I know it is all convoluted, but buying new hardware is simply not an option right now...

 
Posted : 25/02/2016 4:32 am
(@kent-mcmillan)
Posts: 11419
 

In The Sandpit, post: 359591, member: 99 wrote: For some reason (probably because they hadn't considered planned obsolescence as a sales strategy at the time), the 4000 series are working perfectly. At least a 4000SSE I tested was, so I expect the SSi units will.

Well, that's very encouraging. I have three 4000ssi units to test and will mention what the results are.

 
Posted : 25/02/2016 5:19 am
(@bill93)
Posts: 9834
 

I couldn't get FixWeek to install on my XP either - it just keeps saying it needs to update and apparently never succeeds. Maybe the path name may be different between Win versions? I haven't tried on the Win7 machine yet.

As a more manual workaround, see the notes I linked earlier in this thread for the editing steps in the Rinex file. That method works for me on the 4000sst and should have a good chance for other models as well. It DOES require editing the nav file also.

 
Posted : 25/02/2016 6:20 am
(@radiored)
Posts: 46
Registered
 

Will the fix program work with older Sokkia Receivers, such as the Radian, Radian IS and GSR2600?
Thanks,
Doug

 
Posted : 25/02/2016 8:17 am
(@timyoung)
Posts: 12
Registered
 

Bill93, post: 359612, member: 87 wrote: I couldn't get FixWeek to install on my XP either - it just keeps saying it needs to update and apparently never succeeds. Maybe the path name may be different between Win versions? I haven't tried on the Win7 machine yet.

As a more manual workaround, see the notes I linked earlier in this thread for the editing steps in the Rinex file. That method works for me on the 4000sst and should have a good chance for other models as well. It DOES require editing the nav file also.

TimYoung, post: 359600, member: 9639 wrote: Installed FixWeek on another machine to work around this problem - and it appears to have worked fine.
Move the converted file back to my XP field computer.
Used Trimble convert to rinex on the ammended file.
Used Rinexdates on the rinex files generated and the Ordnance Survey network Rinex file downloads
Imported those in TGO - Rinex files imported and showed the appropriate same time range in 2010
Tried to process GPS baselines - failed, no wave solutions generated. The error messages simply say the baselines were not solved.

So - a piece of the jigsaw is still missing? A problem with the navigation file maybe?

I know it is all convoluted, but buying new hardware is simply not an option right now...

Update: I discovered that the GPS week had not been changed in the navigation file by FixWeek - so I made that change manually and the files now process correctly.

 
Posted : 25/02/2016 9:05 am
(@missourimule)
Posts: 30
Registered
Topic starter
 

Kent McMillan, post: 359508, member: 3 wrote: I'd been tied up with other things and just today had a chance to test my 4600 receivers. Interestingly, by the GPS week rollover to a date in 1996, the date glitch that prevented GPSurvey and TGO from doing baseline processing is now fixed. The baseline processor thinks it is 1996 again and generates solutions perfectly well.

I'll have to check the 4000ssi units to see whether they also think its now 1996. Odds are they do and, if so, they'll need to have the GPS week in their files corrected for submission to OPUS. All in all, there are much worse problems to have.

So the old TGO software is working again? What a fiasco.

 
Posted : 25/02/2016 9:49 am
(@paul-in-pa)
Posts: 6044
Registered
 

Navigation files do not have to be repaired, they can be replaced.

Any receiver originated N file can be replaced by the daily 24 hour "N" file find on the RINEX ftp site. Often another receiver N file also has sufficient coverage. Simply download and rename that file to match the name of the "O" file before the "." . If I download 3 CORS files from the ftp site, I copy the daily N file 3 times into my folder and then match the 3 O file names before bringing into my post processor. OPUS and OPUS-RS software does not need this to be done as the software is written to use the daily N file for all.

Paul in PA.

 
Posted : 25/02/2016 9:54 am
(@kent-mcmillan)
Posts: 11419
 

MISSOURIMULE, post: 359652, member: 9473 wrote: So the old TGO software is working again? What a fiasco.

Yes, the inconvenience, of course, is that the dat files have dates in 1996 with day numbers that don't correspond with the present, but the software generates fixed baseline solutions that otherwise are perfectly fine.

My 4000ssi units all know that it's still 02/25/2016. So their dat files should still process just fine via OPUS.

The problem, comes in trying to get baseline solutions when think-it's-1996 receivers are mixed with know-it's-2016 receivers.

 
Posted : 25/02/2016 2:33 pm
(@geo_xxl)
Posts: 33
Registered
 

Fixit using the FixWeek ... and you will get the mix working.

 
Posted : 25/02/2016 11:38 pm
Page 5 / 7