Mapping and GIS Solutions Community

 View Only
Expand all | Collapse all

Pathfinder Office Differential Correction - Cannot update base provider list

  • 1.  Pathfinder Office Differential Correction - Cannot update base provider list

    Posted 02-07-2025 05:30

    Hello, I've encountered an issue where I am not able to update the base provider list in the Differential Correction Wizard. I receive the following message when i click "Update List"-

    "Download failed!", "Failed to download Trimble base provider list. The FTP server may be down; please try again later."

    At first I thought maybe the correction files weren't available for download yet and that I just needed to wait and try later. However, this has now been an issue for me for several weeks for multiple different data files. Any tips for how I should proceed? 



    ------------------------------
    Leah C
    ------------------------------


  • 2.  RE: Pathfinder Office Differential Correction - Cannot update base provider list

    Posted 02-07-2025 05:39

    Hi Leah

    The Trimble FTP that hosts the CBS list has been shut down - take a look at the support bulletin here for more details including how you can continue to update the CBS list manually - Community Base Station List Distribution Update for  Trimble GPS Pathfinder Office Software

    In summary 

    NB - GPS Pathfinder Office was declared end of life in September 2022 so we recommend you look at the modern solutions we offer such as Terraflex  and Terra Office which have tools to Import your existing Terrasync/PFO Data Dictionaries to greatly simplify the transition. You can reach out to your local Trimble reseller for more deatails



    ------------------------------
    Tom Harrison
    ------------------------------



  • 3.  RE: Pathfinder Office Differential Correction - Cannot update base provider list

    Posted 02-07-2025 07:42

    Hi Tom, thank you so much for your quick reply. I intend to look into the Pathfinder Office alternatives that you recommended, but am working on using the manual CBS list download you shared in the meantime. I've saved the .csv into the folder you directed me to, but I'm still not sure how to get the Differential Correction Wizard to utilize this list. 

    In the past, I have always used the "Base Provider Search" for base data during corrections. Am I supposed to select "Folder Search" now? If so, do I replace the Folder Search file pathway with the location of where I saved the .csv file? 

    Finally, do I need to regularly re-download an updated CBS list from the URL https://downloads.trimblegeospatial.com/CBSList/pfo/cbs_list.csv  or is that a one-and-done action?

    Thank you again for your help!



    ------------------------------
    Leah C
    ------------------------------



  • 4.  RE: Pathfinder Office Differential Correction - Cannot update base provider list

    Posted 02-07-2025 08:06

    Hi Leah

    The CBS list is updated more often these days so It's something you may need to update again IF the stations you are using are affected. Your local Trimble reseller would be the best point of contact to check in on CBS updates

    • For now all you have to do is overwrite the OLD CBS list in the folder directory the support note gives.
    • Then when you run the Differential correction wizard the base provider list will be using the most up to date version

    There's nothing you need to do in PFO, just carry on as normal



    ------------------------------
    Tom Harrison
    ------------------------------



  • 5.  RE: Pathfinder Office Differential Correction - Cannot update base provider list

    Posted 02-10-2025 14:28

    Hi Tom, thanks for your reply. I'm still a bit confused about how to carry on with the PFO portion after manually updating the CBS list. When I go to select the Base Provider like I used to, I only see question marks in the integrity index column of the provider list. How should I select my provider if I cannot see their integrity indices? Should I just select the station at the closest distance? 

    I also reached out to my local Trimble reseller as you recommended to discuss modern solutions/workflows which seem promising. Unfortunately they were not able to provide any input regarding CBS updates to help me get by with the deprecated Terrasync/PFO workflow in the meantime.



    ------------------------------
    Leah C
    ------------------------------



  • 6.  RE: Pathfinder Office Differential Correction - Cannot update base provider list

    Posted 02-10-2025 11:11

    Hi, thanks for this!  I hadn't tried to update lately.  Just a note that I did NOT already have a "cbs_list.csv" under Program Files (x86)\Common Files\Trimble\Config, but I DID have one under C:\ProgramData\Trimble\Config.  I just copied the new file to both locations - not sure which one worked.  (You may have to 'show hidden files and folders' to see your ProgramData folder.)

    The ProgramData location is where we have had to update "user_list.xml" in the past, a list of user-defined base stations that our reseller (Duncan-Parnell) provided. Worth a shot if the other location doesn't seem to help! 



    ------------------------------
    Alicia Jackson
    ------------------------------



  • 7.  RE: Pathfinder Office Differential Correction - Cannot update base provider list

    Posted 02-10-2025 14:21

    Hi Alicia, thank you so much for this. I was confused before because I also wasn't seeing the old cbs list in the folder location that the support note directed us to, but it was in the ProgramData folder that you shared! 

    Now that I've replaced the cbs_list.csv with the new one, I'm still not completely sure how to proceed. In the past, I've always used the "Base Provider Search" in the Base Data field for the Differential Correction Wizard. When I go to select the base provider now, I'm still not seeing any integrity indices listed. Is that normal or is it a sign that I didn't properly update the cbs list in my files? How do I decide which Provider to select if I can't see their integrity index?



    ------------------------------
    Leah C
    ------------------------------



  • 8.  RE: Pathfinder Office Differential Correction - Cannot update base provider list

    Posted 02-11-2025 08:43

    Oh... I hope someone else answers. I probably shouldn't admit this, but I never look at the integrity index! :/ I always use the distance, plus I thought we were supposed to try to match the coordinate system the data was collected in? I don't fully understand that part though. Really, if I have a high percentage of locations >1 m off, I try the next base station on the list... but that probably isn't the proper way!



    ------------------------------
    Alicia Jackson
    ------------------------------



  • 9.  RE: Pathfinder Office Differential Correction - Cannot update base provider list

    Posted 02-11-2025 08:58

    Alicia, Leah,

    Integrity index was useful years ago, but likely due to the deprecation, and last update to PFO in or around 2017, this has gone by the wayside.

    Here is what I would recommend for "what to select".   

    1. Good field procedures, mean if 10-20cm matter, then pole mounted antennas keep the data "honest"
    2. Your trying to tie to the CORS reference position, so choose the closest CORS with the highest return of corrected data. Thats why its important to check the box and look at percentages of the file corrected.  There may be differences due to base station collection (thats beyond your control).
    3. Your obviously using Post Processing to "tie" to the datum NAD83 (2011) epoch 2010.  Hence, every CORS stations (not so true for other sites like UNAVCO or PBO) stores the NAD83 position in the rinex header, so always use the upper button and never, ever use the lower check box.  Heaven and Hell.   Hell would mean using an out of date, non Federal reference position and your going to be 1meter or more off.
    4. Accuracy, thats what this is all about means you'll need to occupy a survey control in NAD83(2011) and at least "check in".  This means in a GIS, you export (thats the other half of the story after DIFF correction), you see if you hit the bullesye.  If your 1 or more meters off with a well placed antenna over a control, your getting bit with a datum mismatch.

    So, combine a survey check (NGS ArcGIS Web Application ) with a modern control, and use closest CORS.  

    Export to shapefile, ensuring your using NO shift (NAD83 (CONUS), and assign a PRJ that is correct (say UTM Zone X nAD83(2011).  All these steps combine to pull your data to truth.   No other way to know your doing things right without checking in on control.

    Good luck.



    ------------------------------
    Joel Cusick
    ------------------------------



  • 10.  RE: Pathfinder Office Differential Correction - Cannot update base provider list

    Posted 02-11-2025 10:03

    Hi Joel, thank you so much for your reply. I think I have seen your posts in the past because I recognize your Heaven vs Hell annotation and have been checking "use position for downloaded base files" for some time thanks to you!

    I attempted to follow your recommended workflow with my existing .ssf and am still struggling. After clicking "Start" with the settings you recommended, I receive the following message: 

    Searching for base files... 
    Unable to transfer files.
    Unable to download file from url https://geodesy.noaa.gov/UFCORS/ufcors?newstart=15&starttime=15:00&duration=5&timezone=UTC&year=2025&dayOfYear=036&siteselection=sthl&epochInterval=As+Is&coordinatefile=no&metfile=no&datasheets=no&orbits=no&compress=P&observables=gnss&SUBMIT=SUBMIT.
    Successfully found or downloaded 0 of 1 files.
    Search complete.

    What am I missing?

    Also, the closest base provider was almost 1200 miles away from the site where I collected data which makes me think that my base provider list isn't updating despite having replaced the CBS list manually in my C: drive...



    ------------------------------
    Leah C
    ------------------------------



  • 11.  RE: Pathfinder Office Differential Correction - Cannot update base provider list

    Posted 02-11-2025 09:04

    I really appreciate you replying again, good to know I'm not the only one confused by some of this! 

    So to clarify, when you are using the manually downloaded CBS list saved to your computer hard drive, when you do the differential corrections do you use the "Base Provider Search" function or the "Folder Search" or "Browse" options to select your base data? Historically I always used the Base Provider Search, but that was when Trimble still hosted the FTP that automatically updated the CBS list. Are we still supposed to use that same Base Data workflow or is it completely outdated now? I was thinking in made more sense to use the "Browse" option and select the cbs_list.csv file that we saved to the C:, but when I select the .csv, I get an error message "One or more base files could not be loaded.  Please check the base files, restart Differential Correction, and try again". I have no idea what to do and unfortunately can't find any help materials online that show manually downloaded data, they all use the Trimble FTP that no longer exists...



    ------------------------------
    Leah C
    ------------------------------



  • 12.  RE: Pathfinder Office Differential Correction - Cannot update base provider list

    Posted 02-14-2025 05:58

    Hi Leah, 

    We have been getting the same PFO errors here in NZ. What I found is that LINZ and Geonet have upgraded their base station format to RINEX v3.xx as of December 1, 2024, fully deprecating v2.11 in November. Pathfinder only supports RINEX v2.11 and below. 

    You might want to check with your base provider if RINEX v2.11 (or below) are still available. 

    In the meantime, our workaround is to manually download the RINEX v2.11 base data from Trimble VRSNow. Once downloaded, use the Browse option - see below: 



    ------------------------------
    Mary
    ------------------------------



  • 13.  RE: Pathfinder Office Differential Correction - Cannot update base provider list

    Posted 02-14-2025 19:57

    There are ways of converting RINEX 3 or 4 to 2.11 for PFO and continue using your local CORS for free.

    I use the following command file and three utilities to automate the process. I keep these ready together in a folder and each time simply drop the downloaded RINEX into the same folder and double click the command file....and voila, there's the 2.11 with GPS & Glonass only ready to go for PFO.

    Move the RINEX out before the next conversion, and select them in PFO with the browse or folder search options. 

    This example is for Geoscience Australia files but its easily adapted, for example if your download files don't use the same compression techniques you may be able to delete one or two steps and utilities. The content below needs to be copied and pasted into a text file and renamed to [your own name].cmd 

    I'm happy to help with any tweaks needed.

    prompt $g
    rem
    rem     30Jun24 updated for gfzrnx V2.1.9 
    rem
    rem     ************************************************************************
    rem     **                                                                                                                                                **
    rem     **            Prepare Geoscience Australia GNSS Base Files for Pathfinder Office            **
    rem     **                                                                                                                                               **
    rem     ************************************************************************
    rem
    rem     Included options:
    rem        7-Zip decompression
    rem        Decompress Hatanaka Observation File
    rem        Output only GPS & Glonass as Rinex 2.11 for PFO
    rem
    rem     This command file expects the following utilites in the same folder:
    rem        7z.EXE                      7-Zip file archiver for decompression           https://www.7-zip.org/
    rem        7z.dll                         "          "         "          "            "
    rem        crx2rnx.exe             Decompress Hatanaka compressed files     https://terras.gsi.go.jp/ja/crx2rnx.html
    rem        gfzrnx_2.1.9_win10_64.exe    Convert Rinex 4 & 3.04 to 2.1        https://gnss.gfz.de/services/gfzrnx
    rem
    rem
     
    rem     Unzip downloaded GA base file package
    7z e *.zip
     
    rem     Unzip individual compressed .gz files
    forfiles /m "*.gz" /c "cmd /c 7z e @file"
     
    rem     Decompress Hatanaka Observation File
    forfiles /m "*.crx" /c "cmd /c crx2rnx.exe @file"
     
    rem     Convert Rinex V3 to V2 files including only GPS & Glonass
    gfzrnx_2.1.9_win10_64 -finp *MO.rnx -fout ::RX2:: -satsys GR -vo 2
    gfzrnx_2.1.9_win10_64 -finp *RN.rnx -fout ::RX2:: -vo 2
    gfzrnx_2.1.9_win10_64 -finp *GN.rnx -fout ::RX2:: -vo 2
     
    rem     Optional - delete unwanted interim files
    Del *.crx
    Del *.gz
    Del *.rnx
     
    pause
     



    ------------------------------
    John Winkler
    ------------------------------



  • 14.  RE: Pathfinder Office Differential Correction - Cannot update base provider list

    Posted 02-21-2025 07:46

    Hi John, thank you for your reply and offer of assistance with coding tweaks. My organization has decided to go the route of upgrading our equipment and workflow to avoid PFO entirely by using ESRI FieldMaps on a TDC6 Trimble device connected to a DA2 Catalyst receiver. By going this route, we should still achieve our sub-meter accuracy goal using real-time corrections, and can save time by eliminating the post-processing step in our workflow. Thanks again for your input, I really appreciate your time. 



    ------------------------------
    Leah C
    ------------------------------



  • 15.  RE: Pathfinder Office Differential Correction - Cannot update base provider list

    Posted 02-14-2025 05:58

    Hi Leah,

    I'm based in NZ, and we've been encountering the same errors in PFO related to base file searches. It turns out that LINZ and Geonet upgraded their base station format to RINEX v3.xx as of December 1, 2024, fully deprecating v2.11 in November. Unfortunately, Pathfinder only supports RINEX v2.11 and earlier.

    As a workaround, we manually download the older RINEX v2.11 base files from Trimble VRSNow (note: a subscription is required to access the reference shop). Once downloaded, you can use the "Browse" option in Base Data, select the base file from VRSNow, and then choose "Use position from downloaded base list" under the Reference Position.

    Hope this helps!


    Post-processing report: 



    ------------------------------
    Mary Angelie Pasion
    ------------------------------



  • 16.  RE: Pathfinder Office Differential Correction - Cannot update base provider list

    Posted 02-14-2025 10:36
    Yes, many vendors have switched to Rinex 3.X.  Here in US, NGS adopted stations that make up CORS are still all Rinex 2.1 though, wllowing PFO to still run properly with differential correction.

    In areas with NGS adopted CORS, stick to selecting the nearest CORS (as identified as "CORS") in the CBS list.   This also keeps your solution in "NAD83(2011) when using the Select Base Provider.   

    By default, the list is sorted by Distance from the first position in the SSF.  Hence, when you see a base station "twin", a CORS and say, a SOPAC or UNAVCO, or any other twin alongside the same station with the CORS leading acronym, pick the CORS twin.  

    Also due diligence would suggest check the ref. position from base data against the CORS position which you are correcting against.  Once you checked the box for "confirm base data before processing" , stare at the Base Data details in the wizard window.  Open up the NGS CORS reference position via the site info  popup for that same station ( NGS Map) open Position and Velocity.

    At top of the ARP section, stare and compare the NAD_83 position in LAT/LONG with the Position exposed in the Diff. wizard.  They must match.

    This ensures your resultant CORS solution is therefore in NAD83 (2011) and exporting can proceed when you DON"T double shift during Export.  Always, in this case do "Nothing" on export, selecting the datum that uses the Molendesky transrformer "0,0,0".  result is a GIS dataset coming out as NAD83 (2011) in that case.


    PFO will not accept Rinex 3.x - that is correct.   



    Joel Cusick
    GIS Specialist
    Region 11 - Alaska Regional Office
    240 W. Fifth Ave. Anchorage, AK 99501
    cell:907 280-9724  wk:907 644-3549 





  • 17.  RE: Pathfinder Office Differential Correction - Cannot update base provider list

    Posted 02-21-2025 07:54

    Hi Joel, thank you for your reply. My organization has decided to go the route of upgrading our equipment and workflow to avoid PFO entirely by using ESRI FieldMaps on a TDC6 Trimble device connected to a DA2 Catalyst receiver. By going this route, we should still achieve our sub-meter accuracy goal using real-time corrections, and can save time by eliminating the post-processing step in our workflow. Thanks again for your input, I really appreciate your time. 



    ------------------------------
    Leah C
    ------------------------------



  • 18.  RE: Pathfinder Office Differential Correction - Cannot update base provider list

    Posted 02-21-2025 07:48

    Hi Mary, thank you for your reply! My organization has decided to go the route of upgrading our equipment and workflow to avoid PFO entirely by using ESRI FieldMaps on a TDC6 Trimble device connected to a DA2 Catalyst receiver. By going this route, we should still achieve our sub-meter accuracy goal using real-time corrections, and can save time by eliminating the post-processing step in our workflow. Thanks again for your input, I really appreciate your time. 



    ------------------------------
    Leah C
    ------------------------------