As I suppose a few other 4600LS users discovered, Trimble Business Center didn't process DAT files from those receivers. I just got a note from Trimble support today that a patch has been issued that fixes that bug. Haven't tested it yet, but they did on some data I had sent, so there is every reason to think that it works.
Good to know. Are they posting it to the website, or just emailing it as needed?
Looks like version 2.60.2 is on the Trimble support site.
Looks like they updated the Trimble Configuration Utility on Oct 17. Probably need that too.
WOW. I just upgraded a few days ago. Guess I know what I'll be doing Monday.
Thanks for the heads up here!
You should also be able to click on 'Check for Updates' under the Help menu in TBC and you can install patches from there.
Kent,
Did you upgrade to the full version of TBC? I think I had read that you had purchased a limited version. Do you now run the full version? Are you happy with it?
Al
> Did you upgrade to the full version of TBC? I think I had read that you had purchased a limited version. Do you now run the full version? Are you happy with it?
I just bought the Standard version of TBC. The upgrade special that Trimble was offering was for owners of TGO licenses, which let me out since I'm still running GPSurvey. When I get a chance to actually try TBC after the patch is installed, I'll be able to tell you what I think. The next hurdle is to figure out how to export vectors from TBC to Star*Net, which I'll continue to use for adjustments. I really have no plans to use TBC for anything other than vector processing.
Kent are you able to process 4600 files now on TBC with the patch?
> Kent are you able to process 4600 files now on TBC with the patch?
I don't know yet. I was out in the field today and went out this evening. This weekend I should find out for certain. I do know that Trimble support emailed me some screen shots of the processing output from the DAT files I sent them that was stop-and-go aka PPK. The DAT files that give good quality fixed integer solutions in GPSurvey looked as if they gave ... good quality fixed integer solutions in TBC.
Thanks for responding. I don't have TGO but my Trimble rep said I would qualify for the upgrade pricing (I have TSO). I'm thinking I might do it.
Well, I thought I'd be able to report on how well Trimble Business Center processes DAT files from my 4600LS and 4000ssi receivers. Unfortunately, the Trimble software saga continues. Slightly over a month ago, I bought TBC from the local Trimble dealer. So, I got a CD and a hardware lock for TBC Survey Standard (which I had purchased). A bug prevented it from importing DAT files from my receivers, much less processing them. Now I discover that the fresh CD I bought from Trimble had Version 2.50.something on it. Not a problem, just download the update files from Trimble, right?
Well, after updating 2.50.something to 2.60.something and trying to run the newly patched software, I'm told that my software is now out of warranty! The so-called License Manager thinks in fact that the warranty on the software I just bought (from Trimble) went out of warranty last May!
It may well be that I'll need to close my surveying practice in order to devote all my time to getting the newest Trimble software to actually do what the oldest Trimble software did effortlessly for years. Actually, I think that the root problem here is inherent in all complex systems.
Something definitely went wrong. I just bought and installed TBC advanced on Friday. I also had to go through the update process to get from the 2.5x version on the DVD to the current 2.6x version. When I look at the same page that you posted my warranty date is 10/28/2012. I know that the hardware lock is prone to be fried if installed prior to software installation, but I would think the software would prompt you to remove the lock during an update if necessary. For the record, I completed the install and all updates prior to inserting the lock.
> I just bought and installed TBC advanced on Friday. I also had to go through the update process to get from the 2.5x version on the DVD to the current 2.6x version. When I look at the same page that you posted my warranty date is 10/28/2012.
It may be that the hardware lock was shipped with a goofy date. I don't know. What I do know is that this system has more moving parts than evidently can be managed by the folks who produced it. That is a characteristic of complex systems.
amen to that. For what its worth, my key seemed to set the warranty date exactly 1yr into the future from the date of installation.