June 30, 2015 · 9:16 pm
I came back to the office after 7:00 pm tonight to test the pile of receivers that I had set out earlier in the day. I figured I should get a head start on any problems that the leap second might generate.
I used my ProFlex 500 at the house (3 KM baseline to office) to test the following receivers:
ProMark 220 (which reflects on the ProMark 120 and MobileMapper 120)
ProMark 200 (which reflects on the ProMark 100 and MobileMapper 100)
I am happy to report that they all tracked GLONASS (except for the ZMax of course), got fixed solutions, got the correct position and had the usual elevation range. (If there were any big failures, I was going to take the next couple of weeks off .)
All of the receivers just started tracking and fixed. I did not need to do a reset, or wait for new ephemeris on any of them (even the ZMax!) They seemed to just work.
I also collected 1.5 hours of static data with a X90-OPUS and a X900S-OPUS. They too just turned on and started tracking SV’s.
I was able to succesfully process the baseline between the two receivers using GNSS Solutions.
I also was unable to process any of the files in SPSO which claimed there were no ephemeris for the occupations.
June 29, 2015 · 8:22 am
You probably have already figured out that GNSS Solutions is not being maintained anymore. But I know there are a lot of folks using it for processing single and dual frequency Static and Stop&Go occupations.
I wanted to warn everyone that there is a ‘known’ bug when importing standard RINEX files into ‘GNSS Solutions’:
If a RINEX file contains an HI, or if you enter an HI for an imported RINEX occupation; and the HI is non-zero; then you need to push the ‘Apply to All’ button before you ‘Process Baselines’.
Here is a picture showing the dialog and the button:
You get to the ‘Occupations’ tab by selecting the ‘Files’ tab on the workbook:
Then double-clicking in the left-hand-column of the file:
If you don’t do this, then the instrument height that is embedded in the RINEX file (or that you hand enter) may not be recognized and the job is effectively processed with a 0.0 HI. Which will make all derived heights too high.
The latest revision of GNSS Solutions 3.80 is now three years old and it may be time to update. But the update path is not yet totally clear to me. But I am working with a product manager on what I think will be a spectacular alternative. I will post a note if I find anything.