and 
Troubles in ramp-up base station with F9P board – RTK2go
forum asked 2 months ago
started with a F9P board and installed antenna on the rooftop. With u-center from uBlox, I configured the F9P as “stationary” with “survey-in” mode and activated ALL RTCM messsages. I followed this video indeed:
The F9P is connected finally to an Ubuntu server with RTKLib 2.4.3 installed, I wanted to transfer the GPS information to RTK2go with str2str as following:
str2str -in serial://ttyACM0:115200:8:n:1:off -out ntrips://:<PASSWORd>@rtk2go.com:2101/baerndorf -msg “1005(5),1077(5),1084(5),1087(5),1094(5),1097(5),1124(5),1127(5),1230(5)”
Data transfer seems to happen and the base station is registered with RTK2Go, however, the status of RTK2go shows no GPS data so far:
http://rtk2go.com:2101/SNIP::MOUNTPT?baseName=baerndorf
When I redirect the output of str2str into Linux txt file, it looks like that, However I have no idea if the output is correct or s.th. is wrong, maybe you can help me with that details at least:
$GNRMC,115544.00,A,4854.84524,N,01243.43529,E,0.004,,260323,,,A,V*19
$GNVTG,,T,,M,0.004,N,0.007,K,A*3E
$GNGGA,115544.00,4854.84524,N,01243.43529,E,1,12,0.50,336.3,M,45.5,M,,*4A
$GNGSA,A,3,18,20,11,12,25,28,29,31,02,26,05,,0.84,0.50,0.67,1*06
$GNGSA,A,3,78,81,77,79,87,88,,,,,,,0.84,0.50,0.67,2*0D
$GNGSA,A,3,02,07,36,25,11,12,30,,,,,,0.84,0.50,0.67,3*0C
$GNGSA,A,3,08,12,29,35,26,13,24,,,,,,0.84,0.50,0.67,4*0A
$GPGSV,4,1,13,02,55,148,48,04,03,342,32,05,10,099,39,11,23,044,42,1*6A
$GPGSV,4,2,13,12,24,107,43,18,20,184,43,20,17,072,39,22,,,37,1*5A
$GPGSV,4,3,13,25,56,110,47,26,25,295,43,28,56,254,46,29,86,035,49,1*6A
$GPGSV,4,4,13,31,52,282,47,1*58
$GPGSV,3,1,12,02,55,148,,04,03,342,35,05,10,099,39,11,23,044,43,6*61
$GPGSV,3,2,12,12,24,107,39,18,20,184,41,20,17,072,,25,56,110,47,6*6D
$GPGSV,3,3,12,26,25,295,41,28,56,254,47,29,86,035,49,31,52,282,45,6*63
$GLGSV,3,1,09,69,03,294,35,70,09,350,32,71,01,035,,77,34,135,38,1*75
$GLGSV,3,2,09,78,83,333,52,79,28,317,47,81,20,209,47,87,49,040,48,1*7B
$GLGSV,3,3,09,88,73,185,51,1*4D
$GLGSV,3,1,09,69,03,294,36,70,09,350,,71,01,035,,77,34,135,42,3*78
$GLGSV,3,2,09,78,83,333,52,79,28,317,48,81,20,209,46,87,49,040,,3*7B
$GLGSV,3,3,09,88,73,185,51,3*4F
$GAGSV,3,1,12,02,67,302,47,07,12,312,36,08,10,263,37,10,35,049,44,7*72
$GAGSV,3,2,12,11,55,080,45,12,14,036,36,14,60,074,50,24,05,114,34,7*7B
$GAGSV,3,3,12,25,58,110,47,30,14,296,40,34,03,197,37,36,46,167,46,7*7C
$GAGSV,3,1,12,02,67,302,52,07,12,312,44,08,10,263,42,10,35,049,48,2*78
$GAGSV,3,2,12,11,55,080,47,12,14,036,42,14,60,074,54,24,05,114,41,2*79
$GAGSV,3,3,12,25,58,110,52,30,14,296,43,34,03,197,41,36,46,167,50,2*78
$GBGSV,3,1,09,02,03,104,,05,19,126,,08,35,062,42,12,14,220,42,1*7D
Please login or Register to submit your answer
replied 2 months ago
>>However I have no idea if the output is correct or something is wrong..
Well ASCII NMEA Sentences are definitely not RTCM3 packets.
Look at what you’re enabling on the ZED-F9P side, the clients don’t want your NMEA data, so probably want to disable that entirely, and then enable the RTCM3 MSM7, 1005, and 1230, and make sure they’re coming out.
replied 2 months ago
Thanks! Indeed there was a misconfiguration in the output of the RTCM3. Which I fixed now. The RTCM3 package seem to be binary, I cannot read anything, how can I anlyze the output.
I configured the 1005 message too in u-center, but it seems not to come to RTK2GO.
Can you give me a hint why the 1005 is maybe not coming out or how I can analyze my RTCM3 output….
Here is the current output to RTK2Go:
http://rtk2go.com:2101/SNIP::MOUNTPT?baseName=baerndorf
replied 2 months ago
Correct, not human readably ASCII, if you can code, or inspect the packet headers in hex you can extract the numbers. Packets start with an 0xD3 sync byte.
If the content goes to a different ZED-F9P the packet numbers can be seen via UBX-RXM-RTCM
If you can handle files/streams you can decode the message number and size
https://github.com/cturvey/RandomNinjaChef/blob/main/RTCM3Wrapper.c
replied 2 months ago
Okay, the problem was obviously that the base station was never going to stop the survey-in and fix it. That is why no 1005-message was sent. I fixed this now with the ublox configuration.