That could also be a TNC in KISS mode. The data portion of the packet is displayable ASCII but the header is binary and shows up as control characters...
On Fri, Jul 27, 2012 at 1:55 AM, Stefano Sinagra <[email protected]> wrote: > Hi Bill*, > *thanks for the suggestion: I'll check it out just in case, but I > strongly doubt this can be the cause, as the "mistake" always happens > at the same point of the string. > What here appear as garbled characters are rather "non visible" > control characters as represented in the copy and paste from the > terminal. > On my Ubuntu window they show up as a little boxes containing the > char's ascii code. > * > *73 > Stefano* > >>Bill Vodall* >> *Thu Jul 26 19:44:05 EDT 2012* >>>On Thu, Jul 26, 2012 at 1:53 PM, Stefano Sinagra <sinageruk at gmail.com >>><http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir>> wrote:**>>* CMD: >>>MYCALL IZ0MJE*>>* CMD: UNPROTO APX200 VIA WIDE2-2*>>* CMD: CONV*>>* CMD: >>>/�&=4151.1 N/01225.4 ExXASTIR-Linux*>>*X:2< /�&=4151.1 N/01225.4 >>>ExXASTIR-Linux*> >>Garbled characters on the serial connection? Perhaps this: >>... >>I've replaced caps on 2 KAM's so far... >> >>73 >>Bill - WA7NWP > _______________________________________________ > Xastir mailing list > [email protected] > http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir _______________________________________________ Xastir mailing list [email protected] http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
