Just had a fellow Surveyor that uses 4600's and TGO call me to pick my brain on the recent issue of non-support. Has anybody resolved this and at what cost? Thanks!
Trimble 4600's TGO resolution? Workaround ...
Dave,
don't know about the 4600 but there is a workaround for the 1 billion second problem, it was explained by Dario Canosa
[msg=94125]TGO Processing issue[/msg]
1. You convert all your data files to Rinex.
2. Edit the date/time stamps. - Set the date before 14th of sept.
3. Import your edited files in TGO
4. Process baslines
if needed
5. change your dates in the generated reports.
I'm currently writing some pieces of code -with the help of some SurveyorConnect-friends- to automate the process of changing the dates in the Rinex files. John Minor is test driver and Dario Canosa is guiding me in the wonderful Rinex world. I have something that works on some small files on win XP, but am currently working on the larger files and Win7 support.
I'll post more if this works.
Chr.
Trimble 4600's TGO resolution? Workaround ...
I tried the change-date-to-earlier-year workaround for the first time yesterday. I was pleased by the results.
My TGO results from tweaked RINEX files matched TBC Ver 2.40 results from unedited DAT files within a very few millimeters on an 8-minute observation over about 5400 feet.
If someone is postprocessing only a few files every week this could be a viable workaround.
Then I took this workaround one step farther and tweaked a precise-orbit file back to 2005, that worked fine as well. Started with an SP3 from NGS, changed the date records to 2005. The GPS week also appears in the second line of the SP3 file, so changed that to 313 weeks earlier.
These were simple files - only one occupation per file. I am curious as to how this will work when the files have more than one occupation per file. One thing I am pretty sure of there is that one will need to use the manufacturer's RINEX converter to convert to RINEX. TEQC cannot be expected to handle all the proprietary details that may be found in multi-point files.
GB
Trimble 4600's TGO resolution? Workaround ...
Is this viewed as a permanent fix or will the solutions degrade as we go farther from the September 14th dysfunction date?
Trimble 4600's TGO resolution? Workaround ...
Jef,
it's a permanent workaround for the 1 billion sec overflow bug,
time will tell if other overflows are on the way.
chr.
Trimble 4600's TGO resolution? Workaround ...
So is the problem only with TGO processing, i.e. are the RINEX files created by the Trimble software usable with other processing software without tweaking said files?
Trimble 4600's TGO resolution? Workaround ...
> So is the problem only with TGO processing, i.e. are the RINEX files created by the Trimble software usable with other processing software without tweaking said files?
Yes, I continue to use Trimble Rinex files in Ashtech software without tweaking.
Trimble 4600's TGO resolution? Workaround ...
Excellent. I'm fluent with Ashtech software, he's getting less affluent everyday with his Trimble hardware.:-|
buy TBC standard edition, around 500 bucks
Trimble 4600's TGO resolution? Workaround ...
I am still using GPSurvey. It doesn't have the Rinex conversion utility. Where can I get it? Thanks
Trimble 4600s TGO resolution? Workaround ...
You can get Trimble's latest RINEX converter from the Trimble web site at www.trimble.com
Follow the hyperlink path Support & Training > Support A-Z List > RINEX.
Also check the hyperlink path Support & Training > Support A-Z List > GPSurvey > Downloads.
Unless you are using receivers that collect L2C data it may be easiest to stay with RINEX Ver 2.10.
You can also use UNAVCO's TEQC utility to convert to RINEX but the command-line interface scares most folks in 2011.
Your GPSurvey probably came with a RINEX converter named DAT2RIN.exe, may want to check for that as well.
GB
Trimble 4600's TGO resolution? Workaround ...
> I am still using GPSurvey. It doesn't have the Rinex conversion utility.
Just for the record, the RINEX conversion utility in GPSurvey is the executable DAT2RIN.exe that should be in the GPSURVEY/BIN directory. There is some documentation with the same prefix in the file name.
The newest Trimble RINEX conversion software looks to be much more useful and worth having until it blows up with no warning as happened to GPSurvey and TGO. :>
Trimble 4600s TGO resolution? Earlier overflow
The main thing is that even with this workaround TGO will become less useful as the GNSS constellation evolves.
It seems the vast majority of TGO users never noticed TGO's earlier overflow. That one struck in February 2008 when PRN32 was set usable. Apparently TGO only allocates five bits for PRN numbers, so the highest allowable number was and is 31.
TGO does not use data from PRN32.
The PRN32 information shows up in TGO's Timeline display (SV 32), but check the "GPS Baseline Processing Report" and you will see that PRN32 does not show up in the processed phase segments or in the residual plots.
Windows Vista was released in January 2007 and Trimble made it more than clear they were not going to support TGO on Windows Vista. That was more than 4-1/2 years before the billion-second overflow hit.
GB
> Just had a fellow Surveyor that uses 4600's and TGO call me to pick my brain on the recent issue of non-support. Has anybody resolved this and at what cost? Thanks!
I learned from Trimble support today that they are about to release a version of TBC that fixes the bug that prevented it from being able to process many DAT files from older equipment, including the 4600LS units. If so, buying Trimble Business Center Standard for $495 ought to mostly fix the problem.
Trimble 4600's TGO resolution? Workaround ...
Kent,
Did you upgrade to TBC or are you still demo-ing the software?
Al
Thanks Kent, "ought to mostly" would be fine as we'd settle for "pertnear".:-|
