@gpsfan - My current
static tests are using (L1 only) Samsung A71 on a surveyed control point and GnssLogger v3.0.0.1 but at this point, I'm just trying to see if the RINEX files that GnssLogger are producing can even be post-processed.
I've always involved
NRCAN's CRSR-PPP in all of my experiments
ever since I first learned their service 20 years ago;
L1 only (Ashtech) and L1/L2 (Javad). And a number of these last
smartphone RINEX tests produced by Google's GNSSLogger (shared
Drive folder
here,
in case you want a peak) were submitted to NRCAN's CRSR-PPP
service, but none of them were processed and the results returned
to me; not even a notice of failure. That led me first to trying to check on the validity of the
RINEX files'
formatting.
Javad has a very old tool,
Rinex
Files Viewer (beta version 1.0.6), which is no longer
supported, but still seems to work. It showed errors in the sample
RINEX file, but not in any fashion I care to share with the Google
developers. That was a good thing as it next led me to
GFZRNX
(Windows 64-bit cmd line program that's wholly contained in
gfzrnx_1.15_-8044_win64.exe)
(
gfzrnx_1.15-8044_manual.pdf),
a wonderful tool box that not only can report errors, but can fix
them. The bummer was the repaired RINEX file sent to CRSR-PPP never
returned any results either. I've written to the kind folks at NRCAN
asking if smartphone RINEX files were permissible. I'm guessing
that it's the poor smartphone antenna that will preclude such
submissions from being processed, but for now, that's only a
hunch. And while I await their response I tried using my ancient
GNSS Solutions from back in the Ashtech days, but it needs the
observation's (2) accompanying PM2 files (met and nav). Thus my
bugging this group for a more contemporary solution.
@val - Thank you for the link. Might you be willing to see if the attached log will even work with RtkLib?