I have 2 GPS-RTK2 modules, I configured one as a base station and I’m using rtk2go as my NTRIP caster. In rtk2go monitoring, I can see that it is receiving 1005, 1074, 1077, 1084, 1087, and 1230 RTCM3 messages. I am connecting my rover GPS-RTK2 module directly to my laptop running u-center 20.01 as an NTRIP client.
On the rover I have selected USB output and input to both be UBX + NMEA + RTCM, I have made sure the baudrate of my base station and my rover are both 115200, both have a GPS rate of 1hz, AND when I start the u-center NTRIP client, pointing it to my custom mountpoint, I can see in UBX - RXM - RTCM that it is receiving all 6 of my RTCM3 messages every second, all are being labeled as valid.
Here is my problem, even with all of that, I still cannot enter any fix mode other than 3D, (no RTK Float or RTK fix) and, more concerningly, the RTK LED on the GPS-RTK2 module remains in its steady on state, the same as when no NTRIP client is running.
I can provide any additional information or debugging steps that could help with this issue. I am completely stuck here and I feel like I have tried everything.
Do your antennas have a totally clear view of the sky? Are both your antennas dual-band (L1 plus L2)?
I often struggle to get a fixed solution, and sometimes struggle to even get a floating solution, with a good-quality dual-band antenna that can see approx. 60% of the sky…
Both antennas are dual-band, additionally they are the same antenna on the rover and base station.
Each antenna has excellent sky view too.
What is more bizarre is that I have achieved RTk fix easily in this location with this set up a few months ago, then the base station was moved around quite a bit and now, even though I have set them both up in what I thought was the same way as before, in the same locations, I cannot get an rtk fix or even float
I have hit this a few times when I assume a setting is in place but it’s not. For example, the other day I could not get a lock from me ZED even though I had 30+ satellites. It was because it was set to fixed base mode; the unit was far away from the coordinates I told it it was at, and so the ZED was just not locking. The solve: reset the ZED to default config. Immediately it locked.
You have a slightly different issue, but I suggest you look at the MON-COMM message and verify that the unit that is receiving RTCM is in fact seeing valid RTCM packets. I suspect you have a baud rate mis-config. The packets are arriving at the ZED port but they are being corrupted.