Re: BUG: ubxtool enable/disable RAWX fails

[John Ackermann N8UR]

On 4/28/20 5:07 PM, Gary E. Miller wrote:

> And here is the big one:
> 
> Note the rcvTow:  245122.993.  NRCan wants measurements on the top of
> the second.  So this will not work with NRCan.  This has been known
> for a while.  No known workaround.
> 
> All good RINEX files we have tested have rcvTow very close to the top
> of the second.  This have been much discussed recently here.

As mentioned, I've been in touch with one of the NRCan people and I
raised the question about timetags with him.  Here's his reply:*

"
I'm not sure if this is really an issue. Many receivers output
non-integer time tags. This is taken into consideration when computing
the signal's time of transmission. As long as the measurements are
consistent with the time tag, everything usually works fine.
"

So it may be that the uBx measurements aren't consistent with the time
tag, but the fractional part of the timetag isn't in itself a problem.

On 4/28/20 3:13 PM, Gary E. Miller wrote:

> So, beyond the known bad epoch, any other problem would have to be in
> the drive_ubx.c decode of the new L2 signals.

But the problem occurs with the single-freq M8P, so while it may be
something changed in the RAWX message format, it's not (solely) related
to L2.

John

* I'm not posting his name or contact info because it's been a private
email exchange and I know some of these folks get inundated with help
requests and try to keep a low profile.