Hey,
I’m receiving RTCM3 correction data using a TTGO T-CALL that works very stable. I’m providing the correction data to the ZED-F9P using I2C (also tried Uart2 - same behavior).
When I send the correction data to the F9P, it goes into RTK floating fix after few seconds. The accuracy jumps from round about 1.50m to 0.60m. it more or less stays there for some minutes (sometimes it goes down to 0.30m - bit no final fix). But than, after some minutes, it goes straight back to “RTK no fix” and accuracy of 1.XXm. that happens for I2C and Serial connection. Type doesn’t matter. The GSM is still connected and the incoming RTCM3 “looks” valid.
What can go wrong? Is there some way how I can debug it? Is this somehow a known behavior?
Greetings and thanks,
André