Hello! thanks it works for me! i only calculated the number of weks with chat gpt and can predict the correct weks! , and it looks like! the same error about not collected on an H-Star receiver, but the presicion look good! better that nothing, but realy i thing that is necessay that trimble support give a update solution to trimble gps, my example is Geoexplorer 2008 series. Regards and thanks !
Original Message:
Sent: 11-02-2023 14:44
From: Norman Smart
Subject: Trimble 5800 GPS week number rollover in September 2023.
Great work-around, but it got me thinking about SSF files so I fired up a Geo 2008 with TerraSync 5.41 and played around. Here's a slightly-improved process for collecting data (no frantic file creation) as well as a process for post-processing recent Geo-2008 SSF files using PFO 5.90. There's something a bit flakey with the post-processing though.
To collect TerraSync data on a Geo 2008:
- Start your Geo2008
- Run TerraSync
- Disconnect from the GNSS receiver
- If the OS date and time are not right:
- Close TerraSync (I don't think this is needed)
- Set the OS date and time
- Run TerraSync if you closed it
- Create a new TerraSync data file
- Connect to the GNSS receiver
- Once GNSS is giving positions, log your features as normal
- Close the data file and transfer to PC
To Fix the dates in a Geo2008 SSF file to allow post-processing (flawed):
- Open the data file in PFO
- PFO will show (Feature Properties / First) that Logging Started on the current date, Logging stopped (Feature Properties / Last) in 2004
- Make a trivial change (for example, change the comment on a feature then save the feature) then do "Save As", give a new file name
- Close the original file, open the modified file, Logging Started and Logging Ended will both be 2004
- In PFO, run Utilities / Other / Check SSF file
- Turn on Fix Corrupt Records
- Turn on Alter GPS Week Number
- Select manually and enter the correct GPS Week number for your data (e.g. 2286 for 3 Nov 2023)
- Click OK - it should fix the file dates and save the file with a new name starting with "_"
Post-process the fixed file as normal
When I post-processed a half-hour Geo2008 SSF file I had just collected and fixed, I got messages that:
28 (1.63%) of 1723 selected positions were code corrected by post-processing
28 (1.63%) of 1723 selected positions were carrier corrected by post-processing
Looking at the COR file using SSF Record Editor, there are a lot of POS records with the same time tag (about one unique position per minute)! I also noticed that the fixed SSF file is shown as not collected on an H-Star receiver, while the original SSF shows as collected on an H-Star receiver, but this doesn't appear to be the cause of the post-processing issues.
Update: Got it! Looking at the original SSF file using SSF Record Editor, this also has the repeated time stamps for the POS records. The OBS records have good time stamps. I've seen something similar when you start a TerraSync file on a Geo with a system date a couple of years old, then the date gets updated and POS (with some repeated time tags) and OBS (with normal time tags) get recorded. I guess there's no fixing the POS time tags.
------------------------------
Norman Smart
Original Message:
Sent: 10-30-2023 16:24
From: Joe Gouthro
Subject: Trimble 5800 GPS week number rollover in September 2023.
I've been dealing with this issue as well. A whole fleet of working 2008 GeoXH's suddenly became bricks. I am not impressed. Trimble would have us throw our fully functional electronics into landfills because they want to use this rollover as an excuse to milk the cow. Imagine Ford telling you they won't fix your car because it's 19.7 years old. Sorry, buy a new one. What a slap in the face. I've been using Trimble products for 30 years because of the durability of the instruments. The cost of replacement of my (fully functional) units, upgrades in mapping software, and upgrades in office software would run me 60-70K. No thanks Trimble. I'm done.
That being said, I've found a solution that works for my Terrasync Geo 2008 units. 1. Set the clock on the unit to the correct time. 2. Start Terrasync. 3. Within 10 seconds or so (before the unit reverts to the 2004 almanac and changes the clock)(If you see 'Almanac received', it's too late), open a new data collection file. Use the default, because there's no time to type anything in anything else. A file will open, and the unit will allow data collection and transfer to pathfinder office. As far as I understand, there will be no longer be any capacity for differential correction due to the forced date stamps of 2004. WAAS-corrected field data is all you get. I've tried some test points and the accuracy seems to be the same as before. Good enough for me. That goes for the Geo units, not sure it's much help to anyone else.
------------------------------
Joe Gouthro
Original Message:
Sent: 09-13-2023 04:33
From: Diego Paul Herrera Castillo
Subject: Trimble 5800 GPS week number rollover in September 2023.
Hello,
As said in the title, I have 2 Trimble gps 5800 wich firmware version is the latest available for those devices 2.32. Trimble in 2019 said with this fm version devices can pass the WNRO, but at this month, september of 2023 it started again. Both gps are showing UTC date in january of 2004.
Trimble hasn't said anything about it. And I noticed that this matter is happening to other models since the past year.
Is there a way to fix that already?
Thanks a lot for the help.
------------------------------
Diego Paul Herrera Castillo
------------------------------