AI Assistant
Calendar woes with ...
 
Notifications
Clear all

Calendar woes with Trimble 4000 SSi

8 Posts
5 Users
0 Reactions
337 Views
Dave RR
(@dave-rr)
Posts: 3
Member
Topic starter
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

Greetings all,
I've quite a problem with one 4000 receptor as the calendar list the year 1995, and no amount of hard resetting will make the receptor take the correct date, anyone else had a similar problem? if so what could I do to fix it.


 
Posted : June 22, 2015 10:17 am
loyal
(@loyal)
Posts: 3735
Member
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

I have the same "problem" with my OLD Novatel Receivers.

I simply open the RINEX file in NOTEPAD:

94 2 18 14 21 40.0000000 0 7 1 17 26 7 8 9 11
122120414.6910 95158791.8670 23238742.180 23238749.109

Use the "replace" function

Change 94 2 18
to 13 10 04

which returns

13 10 04 14 21 40.0000000 0 7 1 17 26 7 8 9 11
122120414.6910 95158791.8670 23238742.180 23238749.109

Ya have to pay attention to files crossing GPS Midnight, and the process is NOT idiot proof (what is), but it works for me. I also place a "COMMENT" line in the header to record what I did.

edit
Be sure to change the file extension from .94o to .13o

Loyal


 
Posted : June 22, 2015 10:39 am
Dave RR
(@dave-rr)
Posts: 3
Member
Topic starter
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

I see, so nothing short of editing the rinex to present the correct date? is that hexadecimal? I tried to convert it to decimal but it doesn't show up as a current date.


 
Posted : June 22, 2015 11:44 am
jhframe
(@jim-frame)
Posts: 7465
Member
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

Dave RR, post: 323756, member: 10082 wrote: Greetings all,
I've quite a problem with one 4000 receptor as the calendar list the year 1995, and no amount of hard resetting will make the receptor take the correct date, anyone else had a similar problem? if so what could I do to fix it.

What firmware version are you using? It sounds like something that predates the week rollover update. Updated firmware is available at the UNAVCO page for the Trimble 4000: http://facility.unavco.org/kb/questions/476/Trimble+4000+Resource+Page


 
Posted : June 22, 2015 11:50 am
loyal
(@loyal)
Posts: 3735
Member
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

Hmmm...

A RINEX file is a highly formatted ASCII text file (nothing more, nothing less).

The line:

94 2 18 14 21 40.0000000 0 7 1 17 26 7 8 9 11

"translates" to:

1994 February 2nd 14h 21m 40.0000000s 0 7birds prn1 prn17 prn26 prn7 prn8 prn9 prn11

prn = Pseudorandom noise, which is the unique identifier assigned to a each [active] "bird" in the constellation at any given time. Different birds will "share" the same prn over time, but never simultaneously.

The line:
122120414.6910 95158791.8670 23238742.180 23238749.109

Contains the L1 L2 C1 P2 values.

Editing an entire RINEX file should only take a couple of minutes regardless of it's size. Obviously a file crossing GPS midnight will take a minute or so longer.

It all gets back to the GPS rollover a few years ago. You can figure out the shift using various information online, or just KNOW what day you actually collected the data (my preference).

Edit...

Or you could update your firmware as Jim pointed out above.

Of course this will probably NOT solve the problem for files collected BEFORE the firmware update.

Loyal


 
Posted : June 22, 2015 12:05 pm

david-livingstone
(@david-livingstone)
Posts: 1136
Member
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

I know we had 2 4000 units when the Y2K thing hit the fan and we had to pay Trimble some money at the time.


 
Posted : June 22, 2015 2:20 pm
astrodanco
(@astrodanco)
Posts: 149
Member
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

Please do what Jim suggests and update your firmware. It's a free download. If I recall correctly, it needs to be done from within a Windows XP 32-bit virtual machine.

Also if your receiver hasn't already needed its internal solder tail style batteries replaced, it will soon. It's not difficult. I think UNAVCO has instructions available for that too.


 
Posted : June 22, 2015 2:25 pm
Dave RR
(@dave-rr)
Posts: 3
Member
Topic starter
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

I'll try updating the firmware, thanks all.


 
Posted : June 23, 2015 7:02 am