More TGO problems

I am mostly using a windows 7 machine now. But, I still have an XP machine running, which has TGO. I occasionally have that problem, with various programs, can't remember if TGO is one of them, but I think it has done that. Started in the last few months. Reboot fixes it.

I am having a problem with the Rinex converter bombing out with an error message of GPS week out of range. Is this related to Trimble's issues? I am using an R8-2...the inititial position in the receiver was all zeroes, I have set that to something more reasonable and it is gathering data right now to see if it is resolved. I am supposed to run a static session in a few hours but if I cant get the data out it will be a waste of 6 hours.

The problem with TGO is not due to an incorrect week number in the file, nor are there any other problems with dat files, the problem is with the way TGO handles dates after 9/16/11.

Try using teqc from UNAVCO. You can specifically set the week number. For example, the current week is 1660. So, you could use the following command line:

teqc -tr d -week 1660 xxxxddds.dat >xxxxddds.11o (replace xxxxddds with whatever your file name is). -tr d tells it that it is a trimble dat file (downloaded).

John,
I am not using TGO, I am just trying to convert a rinex file. Thanks for the tip. I will try that

I open my old version of TGO and close all the projects and use the convert2rinex utility and it works well. I did it just yesterday.

I'd try the trimble website and see if the convert2rinex utility has been updated or if yours has been corrupted and simply download it again.

In any case I would strongly recommend teqc for any users, Trimble or otherwise. It can do many other things besides a simple translation. NGS uses teqc to create rinex files for the CORS.

Loyal has posted some tips here in the past on how to do some of the other things teqc does.