Rinexdates 1.8

I haven't done a session since December, but for some years I have been converting 4000sse files to Rinex using TEQC. It doesn't work without specifying the week using that option, but no problem with it.

Thanks for that info, I downloaded TEQC a year or so back but never needed to learn how to?ÿ use it but I will give it a look.?ÿ This is GPS Week 2099 and my trimbles defaulted to week 1075 which is a difference of 1024 weeks.

1.8 is still available right here on RPLS Today. ?????ÿ

https://surveyorconnect.com/community/software-cad-mapping/rinexdates-1-8/

I have sent a PM to Christof to see if he has any plans of releasing a 2020 version.

Hello Robert,

Still alive and kicking here.

Normally the date offset of 22 yrs (used in RD 1.7) should do the trick again, so if you stille have a copy of that version give that a try and let us know how that works.

If it does not work then I will need some data to work with and have a look if the old laptop is still operational. I have no longer a TGO version myself so I won't be able to do some testing.

?ÿ

Stay Safe!!

?ÿ

Hi Christ,

Good to hear from you, hope you are safe and staying isolated.?ÿ I am going to look at this more tomorrow but I'm not sure it is a rinex date problem.?ÿ The unit started up with the correct gps week and date but after a few minutes changed to Aug 2000. The change was from GPS week 2099 to week 1075 which is exactly 1024 weeks or 19.69 years.?ÿ I'm thinking the problem maybe with the internal battery going out but just not sure.?ÿ Even with the bad date it?ÿ properly tracked satellites and gave a 3d nav. position.

This was a survey for a single control point so is no big deal to redo with one of our newer receivers except that I have always preferred collecting static data with the 4000.

RinexDates 1.7 is still available here at RPLS Today as well. ?????ÿ

https://surveyorconnect.com/community/postid/323285/

For anyone interested, I've pulled all previous versions of RinexDates from the BeerLeg archives and am providing them here in a single archive. ?????ÿ

Thanks Wendell

Posted by: @bill93

I haven't done a session since December, but for some years I have been converting 4000sse files to Rinex using TEQC. It doesn't work without specifying the week using that option, but no problem with it.

In processing the sessions I did yesterday I find that things are a little different since December.?ÿ Topcon Tools won't process my .dat files like it used to; I think formerly getting nav information out of the .dat file or associated files and no longer able to.

Even by specifying the correct week I don't get TEQC to extract a good nav file.?ÿ It will still create a RINEX that reads into Topcon Tools for the antenna experiment I just posted about, but have to get TT to download the orbit information in order to process.

I haven't tried sending the RINEX to OPUS yet, but don't expect a problem.

For what it's worth, on 28 April I collected static data with two Trimble 4000SSi receivers (which for years now have been confused about the GPS weeks), and I used teqc to easily produce week-adjusted RINEX observation files which OPUS-S, OPUS-RS, and OPUS Projects happily accepted. I also produced a RINEX navigation file for an experiment with rtklib. The version of teqc is 2019Feb25.

@robert-ellis you can also try the trimble web site for "fixdatweek" , a small program that updates the date.