GEO_XXL, post: 359801, member: 8981 wrote: Fixit using the FixWeek ... and you will get the mix working.
Yes, but after correcting the GPS week, then you have to convert the dat files to RINEX and backdate them using RinexDate if you want to process the baselines in the WAVE processor that earlier Trimble software, GPSurvey and TGO use. It's workable, but suboptimal in how antenna heights and descriptors are handled in the backdated RINEX files.
What would actually be cool would be a version of FixWeek that BACKDATED the GPS week so that the 4000ssi dat files would have the same date as dat files from the receivers that now think its 1996. Those would all run in both GPSurvey and TGO and the solution would be simplest for those (like me) who are using the 4000ssi/sse units as just a base receiver and to connect to NAD83 via OPUS, using other lighter, more compact units as rovers.
@ Dan Patterson,
Dan, that 5700 is still good to go. You have old Firmware on it. You need to go to Trimble's website and download version 2.32. Once that version is installed your 5700 will be bullet proof as it always was.
One note, if you're running old firmware you may need to purchase a firmware update. You won't be able to install 2.32 if your warranty has expired and If I remember reading your post above, it was pretty old. I'd give you local dealer a call and see what they can do. My bet is Trimble is watching this thread and will simply provide a code to get you up and running.
they have the link ... What they will do with .... it is another story!!!
Coveyleader, post: 359967, member: 11339 wrote: @ Dan Patterson,
I'd give you local dealer a call and see what they can do. My bet is Trimble is watching this thread and will simply provide a code to get you up and running.
I believe the last time Trimble gave something away for free, some guy called Moses was playing as a running back for Jerusalem...!
They want to sell new receivers, not keep the old ones going. No revenue in that!
Bottom line, 2.32 will fix the issue. No need to purchase another receiver.
In The Sandpit, post: 359976, member: 99 wrote: the last time Trimble gave something away for free
As I recall, when TGO broke, Trimble offered a substantial discount on TBC.
They will do nothing about the 4700 receivers. They have made a mistake making them indestructible. Ok TRIMBLE I'll give my receivers back to you in exchange for a new R10 (no extra money) ... how about this deal ?????? 😀
Observations logged to my 4000ssi using a Microcentered L1/L2 antenna are not displaying any symptoms of this problem. I checked an observation I ran two weeks ago and one I ran yesterday. All the dates appear to be in order.
Kevin Samuel, post: 360004, member: 96 wrote: Observations logged to my 4000ssi using a Microcentered L1/L2 antenna are not displaying any symptoms of this problem. I checked an observation I ran two weeks ago and one I ran yesterday. All the dates appear to be in order.
Yes, all of my 4000ssi units are working perfectly, generating dat files that OPUS processes normally. Whew!
Older receivers are working better 🙂
John Hamilton, post: 358870, member: 640 wrote: Here is a fix for this problem. I am offering a program to fix the problem, similar to the fixdat program I wrote for the TGO date problem.
This problem is a bit different in that you cannot fix it by going to TBC.
FixWeek (zip file)
or
FixWeek (self extracting executable)
If you click on the first link, it will download a zip file. Unzip it, and run setup to install the program. During the installation it should create FixWeek in the start menu. The other link will download a self extracting setup.
When you run the program, navigate to a directory with the dat files. Once it finds dat files, it will display them in a box with check marks. Uncheck any dat files you do not want processed. It does check to see if the week number is greater than 1024, so it shouldn't change any files that are correct. Note that it does make backups of the original file.
I can assure you this does not contain anything malicious, no viruses, etc. I don't know of any easier way to distribute it, but there are probably some out there who are not able to install it due to company or agency IT policies. Nothing I can do about that.
I just made this, so please let me know if it does not install correctly, or if there are any problems or bugs.
Thanks John for your priceless Help! your fix works like a charm! I fixed data for 2 days of observations with my 5700 and 5800 receivers.
Too late, I am already running the X90 OPUS. Maybe I will try to get the 5700 back up and running so I can have two static receivers. I was pretty upset that it would stop working over something so stupid when the unit is still solid. There's no reason that thing shouldn't work. I've always had issues with this particular 5700 getting it connected to a PC. I've instead had to remove the card and transfer the data that way. Attempting to update the firmware was giving me trouble.
All that being said, the X90 is a pretty cool unit for the price. It also doesn't have the annoying pole bracket that the 5700 has and cables, etc. Like I said, I do still like the 5700, and would love to get it working so I can collect simultaneous static observations.
Our local dealer is selling the receiver in just one configuration ROVER RTK.
Bad luck for him.
I made a revision to the program...it now has the option (default) to rename the file with the correct day of the year. The old file (unedited) is preserved.
This makes it easier to know what day the file was from when you have multiple dat files
If you have already installed the program, just put this new executable into the fixdat program files directory. The install programs linked above are updated with the new version.
New executable (if already installed)
John Hamilton, post: 360731, member: 640 wrote:
New executable (if already installed)
I cannot thank you enough, you literally saved me 4 hours tomorrow.
Question for you. The runpkr00 command line program is create by Trimble and can be found here:
https://www.unavco.org/software/data-processing/preprocessing/preprocessing.html
It allows for conversion of T files to DAT through a command line exectuion such as "runpkr00 -d filename.t01" This command takes the filename.t01 and creates filename.dat.
If you could link this program and yours, a user would be able to convert and fix a Tfile directly. My old firmware 5800 is currently producing such a worthless file.
Either way, thank you very much.
If you're not running firmware version 2.32 for your 5700, 5800, R8 Model 1, or R7 Model 1, you're gonna have a bad time. This is the final firmware release for these receivers.
SurveyAK, post: 361269, member: 9968 wrote: you're gonna have a bad time.
You can say that again. Any idea where one can download said firmware?
geopro_consultants, post: 361270, member: 9959 wrote: You can say that again. Any idea where one can download said firmware?
You can download it from the trimble website easily enough, however if your firmware warranty date isn't Aug 2004 or later it won't install. Trimble will update them for a fee if you are in that situation.
I was not aware that any receiver using the T01 format was affected. I know for sure that 4700's are, but that is because I have a couple, and they only supply .dat files upon download. I have a 5700, and have not yet tried it to see if it is affected. It has its own problem, which is that sometimes it won't recognize the CF card as being present, so it won't start a survey under those circumstances (no internal memory). No rhyme or reason, just seems to randomly not recognize it. We never remove the card to download (download over USB), but when this happens it seems to help if I take the card out and re-insert it. I can use a DC to collect the data, but usually I want the 5700 to be on a point all day would rather log internal.
Anyway, as to your point...I do have a "batchmaker" program that I use. It reads a directory with .t01 or .t02 files, and creates a batch file (dos...remember that?). It translates the file(s) to .tgd and .dat using runpkr00, and then to rinex using teqc. The .tgd file is multi-constellation, and therefore the rinex file is as also. However, .dat files are GPS only. Here is a sample batch file created...there was one .T01 and one .T02 file in this particular directory.
runpkr00 -g -d 07620630.T01
runpkr00 -d 07620630.T01
teqc.exe -tr d 07620630.tgd >07620630.16o
runpkr00 -g -d 54320630.T02
runpkr00 -d 54320630.T02
teqc.exe 54320630.tgd >54320630.16o
That saves me a lot of typing. One of many programs I have written which I use daily that my former business partner called HAT (Hamilton Analysis Tools).
So, I could put in an option to create the batch file, and then run it before correcting the dat file. I will try to do that when I have time.
Unfortunately I have no knowledge of the .T01 or .T02 formats, so I cannot "fix" those files directly.
I would be interested to hear what receivers are actually affected. My original 4700 that I bought in 1998 was stolen many years ago. I have two other 4700's that I bought rather cheap that still work great. When I convert to rinex, one says NP 1.20/SP 1.43 and the other says just 1.3 in the receiver version field of the rinex header.
I followed with attention the publication "GPS y2k problem".
the solutions are to .DAT
I have a Trimble GeoExplorer 3
he thinks today is July 24, 1996
now I can not make the differential correction with permanent stations in my city.
5 months ago acquired the receiver to begin GPS measurements.
I understand that the receiver I can not change the date.
as I can do to change the .ssf file, and to make differential correcion?
use the pathfinder office software 4.0
thanks
