Hi @sparky,
Just clarifying some minor things to avoid misunderstandings:
-
I’m now trying a different and better SD card formatted with the official “SD Association” formatting tool just to rule out other causes for the bootloop. I’ll report the issue to GitHub if it continues.
-
I’m able to turn off GSV, but there are a few others that don’t turn off. One of the proprietary NMEA messages that won’t turn off is PQTMPVT, which contains the number of satellites in use. That might be able to replace GSVs number of satellites in view ? PQTMPVT also contains date and time. The SD card file name doesn’t give the correct date if I disable RMC. In other words, PQTMPVT (which is already forced on) can replace the need for GSV and RMC. Just an idea.
-
For me it’s not necessarily about disabling the NMEA output internally, but disabling the writing of NMEA to the SD card. Even better would be to write NMEA to one file and RTCM to another file. They use different encodings/types but are written to the same file. That creates problems in many file readers. Example trying to read NMEA from a file that also contains binary RTCM in Python:
f = open("input.txt", "r")
Output: UnicodeDecodeError: 'charmap' codec can't decode byte 0x90 in position 1850: character maps to <undefined>
f = open("input.txt", "r", encoding="utf8")
Output: UnicodeDecodeError: 'utf-8' codec can't decode byte 0xd3 in position 1821: invalid continuation byte
f = open("input.txt", "r", encoding="utf8", errors="ignore")
Output: $GNTXT,01,01,00,ESP_RST_POWERON*1C
Is there a future possibility of separating NMEA and RTCM output to two different files written in parallel?