-
Notifications
You must be signed in to change notification settings - Fork 8
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
seeing problems decoding aprs packets from direwolf #11
Comments
|
Okay, seems those APRS message types aren't implemented, shouldn't be a difficult problem to solve. |
How about I make a test-case out of this then see if we can fix the problem. |
ok that sounds good |
Okay, so I dug into the APRS specs on position reporting… and man, what a can of worms… I think I've got something that should recognise and hopefully not mangle position reports. It's worth noting that, the code as it stands now should pass through unrecognised frames as generic AX.25 UI frames, so other code should be able to pick them up and parse them as needed, but handling of position frames certainly fits within the purview of this library, so it should handle it. On the to-do list:
|
So… had a chance to look at this today. Unit conversion is supported… basically natively it still uses imperial units, but there's alternate versions that use Uncompressed and compressed position report formats are supported. Of course timestamps are basically using a dedicated class rather than the standard NOT supported at this time, but maybe I'll get a chance to add that in later, is MicE support. Those packets use a slightly different format, I'll have to research how that all works. I'll have to see if I can gather more frame types to test the decoder and encoder out, but things are looking pretty good so far. |
|
I've merged the position reporting stuff for now… but I'll leave this open as there's MIC-e stuff to be added. |
I have aprsd using tcpkiss socket to direwolf. Each packet that is seen by aioax25 results in this.
The text was updated successfully, but these errors were encountered: