[aprssig] bad Mic-e packets
Wes johnston wes at kd4rdb.comFri Apr 21 23:06:44 UTC 2006
- Previous message: [aprssig] bad Mic-e packets
- Next message: [aprssig] bad Mic-e packets
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
You'll have to leave the path info in there for us to decode them.... kd4rdb v XXXXX , wide2-2:YYYYYYYYYY is the approximate format.... we need to see the XXXX part as well. Wes ----- Original Message ----- From: "Doug Ferrell" <kd4moj at kd4moj.org> To: "TAPR APRS Mailing List" <aprssig at lists.tapr.org> Sent: Friday, April 21, 2006 6:42 PM Subject: [aprssig] bad Mic-e packets > Greets: > > I'm seeing bad mic-e packets (er...reported to me as being bad) at my > Igate > station with the "]" bracket. At first I thought it was aprsd but I went > into terminal mode and I see the same thing. So I guess this is a TNC > setup > problem? Below is a snippet that I edited to eliminate the callsigns so > it > starts after the colon. > > :`p0\l v/]"42} > :`p0]l v/]"46} > :`p0]l v/]"46} > :`p0]l v/]"48} > :`p0]l v/]"41} > :`p0]l v/]"47} > > ...DOUG > KD4MOJ > > > > _______________________________________________ > aprssig mailing list > aprssig at lists.tapr.org > https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig >
- Previous message: [aprssig] bad Mic-e packets
- Next message: [aprssig] bad Mic-e packets
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the aprssig mailing list
