Closed dborden0 closed 1 year ago
Hi @dborden0
Could I please ask you to use the Issue template when raising issues, as advised in the README.
To help me diagnose your issue, I need to have:
pyubx2
you're using (if not the latest 1.2.17, advise upgrading and retrying)Thanks in advance
Hi @dborden0,
In the absence of further information (Python script, full traceback) I can't really give you a definitive answer to your issue, but I would make the following general observations.
ubxreader.py
read
method, the quitonerror
flag will only capture unknown or unsupported protocols (i.e. something other than NMEA, UBX or RTCM3). It won't necessarily capture more general errors.ubxreader.py
provides a dedicated iterate
method which does allow you to use the quitonerror
flag to specify whether such errors are ignored, logged or re-raised. See the /examples/ubxfile.py
example by way of illustration.True
.You could of course simply add a suitable try...except
construct around your own read loop to capture any specific exception types you wish to handle or ignore.
Hope this helps. I'm closing this issue for now.
I am using bluetooth with my GPS receiver, and I believe that is why I am getting some parsing errors. I don't get any when hard wired. When nmeamessage.py _do_attributes raises an error, I can't figure out any way to continue operation and just ignoring the corrupt message without modifying the library. It seems like there should be a graceful way to just drop the bad data and continue.