#557 xastir_udp_client: Extra char, "}", is added
Hi
When sending a message using xastir_udp_client:
xastir_udp_client localhost 2023 OZ1BV-4 23546 -to_rf "=5500.80N/01154.37E413.89V"
I found this on aprs.fi when looking on the raw data:
2014-11-23 18:30:04 CET: OZ1BV-4>APX207,OZ8SMA-2,OZ4DIA-2,WIDE2-1,qAS,DO0SOC:}=5500.80N/01154.37E413.89V [Unsupported packet format]
As far as I can see the error is the "}" just before the "=5500....." ect.
I have been using wireshark to figure out if the "}" is coming from the xastir_udp_client and it does not seems to be the case, please see attached screendump.
I have also been looking in the xastir_udp_client source code and could not find some code inserting a "}".
My conclusion is that the character, "}", is added by xastir and it might be a bug.
Best 73 de OZ1BV, Brian
I am encountering this issue as well. I have the additional information that Direwolf (the TNC I am using for Xastir) is printing this out as well, so it is almost certainly being added by Xastir.
Note that other people are encountering this as well: https://s55ma.radioamater.si/2017/07/27/send-aprs-datatelemetry-via-xastir-command-line/
Aha, not sure if this is "correct" behavior on part of Xastir, but it does seem to be intentional. Xastir is treating the packet as a THIRD PARTY packet. The format is described here: http://www.aprs.org/APRS-docs/PROTOCOL.TXT - just search for THIRD PARTY FORMAT.
FYI, the code that does this in Xastir is here: https://github.com/Xastir/Xastir/blob/8e065909a2edbefe98e5bcf2cfcce5272f27874b/src/main.c#L13518
The comments discuss making a determination as to treat the packet as "first-person" or "third-party" and then just seems to ignore that and treat it as "third-party" no matter what.
The Xastir project no longer uses sourceforge for tracking issues. We use only github.
This issue is in fact already discussed in github issue 189, https://github.com/Xastir/Xastir/issues/189
You appear to be doing the same thing that was identified there, injecting only the payload of an APRS packet instead of the complete packet.
As a result of that issue report, the documentation for xastir_udp_client was updated to be more clear that one must inject a fully formed APRS packet, not just the payload part.