I followed the manual in the link attached under the section “RTK configuration protocols with u-center“ to enable RTCM message types and confirmed that survey in process is successful but no RTCM messages are ever generated on the base side, only NMEA sentences. Has anyone had any issues following the manual instructions or have links to other configs I could try to enable RTCM messages?
You have an F9P and not and F9R ?
Mechanics should work, check UBX-CFG-PRT indicates the output interface has RTCM3 protocol enabled for Output. Check UBX-NAV-PVT reports fix type as TIME.
RTCM3 messages are in binary, not Text / ASCII.
Suggest saving a log file. Use record button on uCenter Classic, and opt to output the debug/diagnostic messages, attach resultant .UBX file.
You could try the NTRIP Caster function in PyGPSClient, which is available for Windows, MacOS and Linux - see GitHub - semuconsulting/PyGPSClient: Python Graphical GPS Client Application supporting NMEA, UBX, SBF, RTCM3, NTRIP & SPARTN Protocols.
It supports both FIXED and SURVEY-IN timing options for a range of RTK receivers including the ZED_F9P, ZED_X20, Septentrio Mosaic X5 and Quectel LG290P.
Yes F9P. My output interface has UBX+NMEA+RTCM3 enabled for output. I am currently using RXM →RTCM to check if my base station module is generating RTCM messages but nothing is showing up; is this the right way to check if my base station is generating rtcm messages? I currently only have a ublox antenna and F9P module attached to my laptop to u center to debug. Also, I am able to confirm that my module can complete survey in. Also, I don’t see an option to opt to output the debug/diagnostic messages.
I cannot use NTRIP caster because where the base station and rover will be deployed will have no wifi so I will be using radios to have the base station send the rover rtcm data.
UBX-RXM-RTCM is a ROVER side reporting method, indicating it is getting the messages and they are intact.
From the BASE side, confirm the receiver is in TIME mode, using UBX-NAV-PVT/STATUS, enable the RTCM3 messages 1005, 1077, 1087, 1097, 1127 and 1230. Check the output stream, with perhaps something like SNIP or use UBX-MON-TXBUF, IO or COMM to observe output bytes / messages.