I tried it with the default sample.phc configuration. It produced only
few SOCK samples. Is the validation too strict? In the log I have seen few
of these:
"could not derive offset from PHC" err="phcsample: wallClock median residual 50.465527ms exceeds limit 50ms
but mostly it was silent and produced no samples. The offset of the
PHC and system clock to GPS was less than 100 nanoseconds, not clear
where that 50ms is coming from.
Looks like the config defaults are too strict. I pushed a change to put in some looser ones.
But I still need put in some proper logging for when things go wrong: the code is very raw at the moment.
It's receiving messages now, but there is some issue with
configuration (or transmitting messages in general?):
level=WARN msg="GPS configuration failed" err="GPS receiver sent NACK for request CFG-VALSET"
level=INFO msg="GPS configuration" cfg="map[mode:map[static:false] signalsEnabled:map[] timeGNSS:GPS]"
level=INFO msg="GPS receiver" vendor=u-blox hardware=ZED-F9T firmware="TIM 2.20 PROTVER 29.20" gnss=GPS,GAL,BDS,GLO,QZSS,NAVIC,SBAS
I think this is because the module is connected using its I2C port and I wasn't generating the right port-dependent config key in one case. I have pushed a fix that I hope will fix it.
Both the fixes are on phc-sample. If these fixes don't solve either problem, please enable the packet log and event log:
[log]
packet=true
event=true
James