AI Assistant
Notifications
Clear all

TBC - Date & Time Way Off

6 Posts
4 Users
0 Reactions
943 Views
bene1
(@bene1)
Posts: 37
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
 

Hi. I'm having an issue with TBC (v. 3.40) when importing GNSS data. When I import a T01 file of static data, the date and time are way off. Like 136 years off. The 'Receiver Raw Data Check In' dialogue box shows that the occupation start and end time are from the year 1880. Suffice to say, I'm skeptical.

Outside of TBC, I've converted the T01 to a RINEX and the dates and times are accurate (2016). The data was logged to the receiver, no data collector involved, and I'm seeing this same behavior with other T01 files too, not just one. Seems like there's a setting tripped up somewhere in TBC but I haven't been able to track it down. Anyone seen this before? Thanks.


 
Posted : April 22, 2016 4:19 pm
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
 

Yeah... the constellation was a little weak at that point!

Seriously though, try converting to RINEX and take a look at the data (or post the "header" data here)

Loyal


 
Posted : April 22, 2016 6:56 pm
Alan Chyko
(@alan-chyko)
Posts: 159
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
 

Probably a software update issue. Take a look at https://surveyorconnect.com/threads/opus-a-new-to-me-receiver.322531/page-2#post-334942&apos ;">this thread.


 
Posted : April 25, 2016 12:03 pm
lee-d
(@lee-d)
Posts: 2382
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
 

Download and run the Trimble Configuration Utility, that should fix it. But I'd also install the latest version that you're eligible for - they just released 3.70 but 3.50, 3.60, and 3.61 would all be better than 3.40..

http://www.trimble.com/Infrastructure/trimbleconfiguration_ts.aspx


 
Posted : April 25, 2016 1:28 pm
lee-d
(@lee-d)
Posts: 2382
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 should have looked at Alan's thread before I posted; obviously this has come up before.


 
Posted : April 25, 2016 1:32 pm

bene1
(@bene1)
Posts: 37
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
 

Thanks for the links, guys.


 
Posted : April 25, 2016 8:47 pm