Hi Curt, Thank you for the reply. I'll have to double check the version when I get home, but I believe it's FC5. It had been working great up until recently (I updated it to one of the Jun builds a couple weeks ago but not sure TBH when it started acting up.) It's also just not the first character knocked off, but also seeing garbage characters as well where it would be some odd ASCII non-numeric code, several spaces and then the callsign followed by the rest of the message. After looking at it a bit yesterday I noticed it was intermittent, as well as always on the igated messages and never on the incoming message. In the mean time I rewrote my app to throw out bad/invalid callsigns.
-Mike KB1MTS On 7/18/07, Curt, WE7U <[EMAIL PROTECTED]> wrote:
On Tue, 17 Jul 2007, Mike Loebl wrote: > I had written a piece of software to parse out packets via the > Xastir server port on 2023. I noticed I was getting some strange decoding > coming in to my app and traced it back to the server port. If I telnet into > port 2023, here's an example of what I'm seeing: > > N8VIM>APRS,RELAY:$ULTW000000000369147627BBFFFC88830001017C00C5032800000000 > VIM>APRS,RELAY,KB1MTS,I:$ULTW000000000369147627BBFFFC88830001017C00C5032800000000 > KB1MKZ>APX184,WIDE2-2:=4233.78N/07116.28WxXASTIR-Linux > 1MKZ>APX184,WIDE2-2,KB1MTS,I:=4233.78N/07116.28WxXASTIR-Linux What OS? I'm running three Xastir instances here, one of which is connected to a full-tilt Firenet feed and has the server ports enabled. Telnetting to "localhost 2023" on Linux here shows lots of packets flying by and the first two characters aren't missing on any of them near as I can tell. -- Curt, WE7U. APRS Client Comparisons: http://www.eskimo.com/~archer "Lotto: A tax on people who are bad at math." -- unknown "Windows: Microsoft's tax on computer illiterates." -- WE7U "The world DOES revolve around me: I picked the coordinate system!"
_______________________________________________ Xastir mailing list [email protected] http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
