-
Notifications
You must be signed in to change notification settings - Fork 104
UBX_Integrity_Checker : incorrect error detection #94
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi @Eric-FR , Thank you for reporting this. The code was using a maximum NMEA length (
But, from your data, I can see that the PUBX (u-blox proprietary NMEA messages) can exceed that. I have updated the tool: I have increased the maximum length to 128; and also record the longest NMEA message length. Enjoy! |
Do you have any reason to believe that NMEA sentences length will not be higher than 128?
|
128 is just an "educated guess"! If you see PUBX messages longer than this, please let me know. Thanks! |
Although I can't find the official source of NMEA standard (that may not be freely available), it is commonly stated like in wikipedia that: Messages have a maximum length of 82 characters, including the $ or ! starting character and the ending So, PUBX don't comply with NMEA standard, isn't it? Should we have a soft warning for sentences exceeding 82 characters and stronger action over a higher limit like 128 characters? |
I just found classical sentences exceeding the official limit:
|
Is that with high precision turned on? |
UBX_Integrity_Checker is reporting a lot of errors on my ubx log files recorded since 21/12/17.
Sparkfun RTK Express with RTK_Surveyor_Firmware_v110-RCDec-13.zip. Logging on the µSD card.
Static recording with or without RTK correction.
UBX_Integrity_Checker is complaining about:
Panic!! Excessive NMEA message length!
Sample log (without RTK correction):
SFE_Express_211221_122914.zip
No problem with ubx_convert, u-center or rtklib (RTKPlot and RTKConv).
RTK Express settings:
SFE_Express_Settings.txt
The text was updated successfully, but these errors were encountered: