detritalgeo, post: 417545, member: 8326 wrote: So unless Trimble responds with a complimentary code
"Complimentary" isn't in the Trimble vocabulary.
detritalgeo, post: 417545, member: 8326 wrote: If the log file is for a static points, to be converted to RINEX, I have tried out the Teqc program from Unavco to force the correct week to be applied in the RINEX conversion and it works fine.
So unless Trimble responds with a complimentary code to allow me to bump from 2.26 to 2.30, that's what I will be doing.
I have been past the Unavco site many times and looked at teqc but being dos based I have kept going. Looks like you've found something very useful here. Able to run through the process?
mattb, post: 417673, member: 8629 wrote: looked at teqc but being dos based I have kept going
You might appreciate Winteqc, a GUI wrapper for teqc. I don't have a link handy, but it's out there.
Just so I understand... you have a 5700 that was manufactured prior to 2004 - in other words over 13 years ago - that no one found it advisable to keep the firmware current in, and now it's Trimble's fault and due to a conspiracy to force their equipment into obsolescence that they didn't foresee every eventuality at that time? They made firmware - 2.32 - that fixes this; keeping firmware up to date is just part of the cost of doing business.
Trimble wasn't the only company to have these issues; I know for a fact that the Leica 500 systems (same vintage) have had these issues over the years. If Leica chose to provide free fixes kudos to them, but there's nothing inherently wrong with a company charging for their product, labor, and R & D.
Regarding the TGO - TBC issues, everything I've seen posted on that is a massive oversimplification of what really transpired. You can contact me privately if you want the real story on that rather than the "Trimble is evil" rhetoric.
I had 13 years' experience with Leica before I started with Trimble; they were a great company that made (makes, presumably) great products. But they've had plenty of their own issues.
Lee D, post: 417676, member: 7971 wrote: now it's Trimble's fault and due to a conspiracy to force their equipment into obsolescence that they didn't foresee every eventuality at that time? They made firmware - 2.32 - that fixes this; keeping firmware up to date is just part of the cost of doing business.
Will Trimble will sell 2.32 to customers for a reasonable price? If not, then the intentional obsolescence charge is warranted.
I guess that depends on what you consider reasonable. I can tell you that it would have been one heck of a lot less 12 years ago.
But even if it's the $750 number I've seen tossed around, that still seems to me to be a lot less money than you could buy another receiver for.
Lee D, post: 417699, member: 7971 wrote: But even if it's the $750 number I've seen tossed around, that still seems to me to be a lot less money than you could buy another receiver for.
Given the cost of maintaining EOL firmware files (basically $0), that's not what I would call a reasonable fee or good customer service. It's clearly intended to discourage purchase of the firmware, and is also clearly not an effort to recoup the R&D cost of that firmware. So, yeah, planned obsolescence.
I certainly don't begrudge Trimble its right to determine its own business model, but I speak with my checkbook by buying as little from Trimble as I can.
Jim, I haven't stepped back into this argument because you have completely echoed my sentiments. I was Trimble's number 1 supporter until a couple of years ago when I decided to head back to leica for TS and topcon for gnss. As far as I'm concerned Trimble are the apple of surveying. Buzzy cool looking stuff that is awesome and works seamless as long as you expect it to only be the case for a couple of years and then get prepared to cash out again.
Lee, this may not be completely fair to trimble and to be honest as a consumer that's not my problem. Like Jim and many others, if it seems unfair, we walk.
mattb, post: 417673, member: 8629 wrote: I have been past the Unavco site many times and looked at teqc but being dos based I have kept going. Looks like you've found something very useful here. Able to run through the process?
Sure thing.
- Download teqc, unzip the folder.
- for DOS ease of use, I made a folder on the C: root called "UNAVCO" (C:UNAVCO), you can name what you want.
- Move teqc.exe file to the new UNAVCO folder
- Click start, search CMD.exe in the start menu and run.
- Get to the root C: (type: "cd.." and hit enter if needed)
- Type: "cd UNAVCO" and hit enter to enter the folder.
- Download your trimble log files, you will need to move only the .DAT file to the UNAVCO folder that teqc.exe is in.
- Back in the DOS window, enter the following command: "C:UNAVCO>teqc -week XXXX Demo.DAT> Demo.obs" and hit enter
- You will need to replace "XXXX" with the GPS week that you collected the file in, and replace "Demo" with your actual log file name.
- This will generate an RINEX observation file in the UNAVCO folder, that you can move wherever you want.
- For my PPP service, I have a habit of renaming the RINEX file as a .17o file instead of .obs, but that may not be required.
**I recommend opening the file and confirming the date is indeed correct and the antenna model is correct.
**I bookmarked the NOAA GPS calendar for convenience.. https://www.ngs.noaa.gov/CORS/Gpscal.shtml
Thankyou very much for that. I'll be sure to try it in the next couple of days.
John Hamilton, post: 417338, member: 640 wrote: Shelby: I was not aware that the Trimmark II was ever available as a 12.5. I have an OLD Trimmark II that I don't use anymore. I think you may be right, the manual for the Trimmark III says either/or, but does not say that it is changeable. But my rep at the dealer says it can be done, I guess I will find out.
Be interested in hearing the outcome.
SHG
Lee D, post: 417676, member: 7971 wrote: Regarding the .... "Trimble is evil" rhetoric. ... I had 13 years' experience with Leica ....they've had plenty of their own issues.
Leica has regular software/firmware upgrades which they charge plenty for, just as Trimble does.
Maybe not so much for Topcon? I don't know. But IMO there is a big performance downgrade if using Topcon. You get what you pay for.
John Hamilton, post: 417338, member: 640 wrote: Shelby: I was not aware that the Trimmark II was ever available as a 12.5. I have an OLD Trimmark II that I don't use anymore. I think you may be right, the manual for the Trimmark III says either/or, but does not say that it is changeable. But my rep at the dealer says it can be done, I guess I will find out.
Did you find out anything on converting the TrimMark II to 12.5? I still have one in the attic that I would love to use. In my opinion they were the best radio made.
It is at the dealer now, I will ask about it and update here.
Trimble's got a program that was made for the 4700/4800 when this problem popped up for them, it's called FIXDATWEEK. We've got an old 5800 with the same problem, warranty period is out and we're not gonna fork out any cash for that receiver. I ran a very short static .dat file from the 5800 through the program and the date appears to have been fixed, so presumably the .dat format didn't change with the hardware generation. I have yet to submit anything to OPUS with it though, so it's not completely proven yet.
Link to the Trimble Support download page: http://www.trimble.com/support_trl.aspx?Nav=Collection-3583&pt=4800
It will work, the only thing wrong with the dat files from the 4700's and older firmware version of the 5700 is that the wrong week number is in the file, all of the observations are tagged with seconds of the week. So it is only necessary to change the week number and then it is correct.
