AI Assistant
Notifications
Clear all

Correct syntax for teqc 2019 WNRO fix?

1 Posts
1 Users
0 Reactions
1,530 Views
millerjs
(@millerjs)
Posts: 14
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 All,

I have an Ashtech ProFlex 800 that has not yet had the 2019-WNRO-correcting firmware update applied (looking for a USB drive adapter... let me know if you've got one!). It is slated to (temporarily) replace another unit that was acting as a CORS station and recently stopped working. I am doing some testing with the working-but-wrong unit and would like to send off some observations to OPUS.

 

I would like to use teqc to correct the obs files gathered from it, I know using find and replace is also possible but teqc should be easier to integrate into a script. Problem is, using the -week 2048 command isn't doing anything. The output file has the exact same start/stop dates/times as the input file. 

 

I'm using the Feb2019 version of teqc, and am seeing the same results on windows and linux. 

$ teqc +qc syif037l00.06o | grep Time
Time of start of window : 2006 Feb  6  11:00:00.000
Time of  end  of window : 2006 Feb  6  13:59:55.000

$ teqc -week 2385 syif037l00.06o > syif037l00.25o

$ teqc +qc syif037l00.25o | grep Time
Time of start of window : 2006 Feb  6  11:00:00.000
Time of  end  of window : 2006 Feb  6  13:59:55.000

I feel like I'm missing something obvious here, but no matter what value I put in for the week offset, the dates never change. I've also tried using +week as well as specifying output observables, but the dates never change.

 

Thank you!

John


 
Posted : September 23, 2025 3:01 pm