Open dillonbuhl opened 1 year ago
Yeah I guess the parse errors are simple enough that they are worth fixing. I think What you're seeing is typical for having never gotten a position fix that it can parse. Once you get a fix, the zeroes will be something valid.
Can you tell if the parse errors seem like they're coming from pynmea or my code?
parse errors look like
WARNING:root:Parse error: ('could not parse data', '22,3.8,E,A*0F\n')
your code?...
that one in particular was probably on instantiation; it throws an error on the first, partially-received nmea msg
Ok no that one's not me, that's pynmea so you'll have to live with that message coming out. The exception I'll have to do something to deal with.
that's totally fine. good to have visibility if it's having trouble parsing messages. like I said above, your code seems to still be sending out data after throwing that exception related to the speed calculation. Do you think it's still "working correctly" at that point?...
No, it's probably stopped parsing at that point. But I'll have it not throw the exception so it can continue and not stop unnecessarily.
If there is an unhandled exception, I guess I can try to figure out how to signal to the other thread in the server to stop, so the whole server stops. I may or may not get to this, since it'll be obvious to you if this happens (your gui will stop "flying"), and your response to it happening is the same either way -- restart the server and report to me the unhandled exception.
I'll also change the default listen port to 4063
Things should be better now. Feel free to reopen if new git revision doesn't help NMEA messages. Open a new issue if it's related to parsing of Javad/Topcon binary data (they are compatible formats) or Novatel data.
Basically got server.py working
when I tried running it in the office with incomplete GPS data (ie, Garmin has no sv's, no position, etc but still spitting out messages), server.py gives the error
But was still sending out data that looks like:
I don't know if you/we care... Just mentioning since it might behave similarly with momentary interrupts in data quality or something...
Note: it's also sending out occasional Parse Errors, seeing messages it thinks are ' ', but that's probably ok... didn't happen more than once or twice in a minute or so.