APRS Packet Errors for DG0SD-10 (last 6 hours)

This table contains packets in which findU has detected an error. This is an automated system, no manual checking of these packets has been done. Most common cause of this is mistakes in entering the latitude/longitude into hard-coded digis, or positions of 0/0. If packets of yours appear here, and you have looked at it carefully and cannot find the error, look again. I've been watching these error messages in my log, and believe my parser is reasonably correct. Go get the APRS spec to be sure. If you have done that, and are CERTAIN the packet is a legal APRS packet, then it is possible that there is an error in my my parser. Only email me if you are absolutely, positively certain...ask yourself, would I bet $100!

time (UTC)	Packet
20260208165526	DG0SD-10>APRX29,TCPIP*,qAC,T2PERTH:@081655z5411.30N/01208.38E_000/000g000t032r000p000P000h89b10159
20260208173733	DG0SD-10>APRX29,TCPIP*,qAC,T2PERTH:@081737z5411.30N/01208.38E_000/000g000t032r000p000P000h89b10162
20260208181746	DG0SD-10>APRX29,TCPIP*,qAC,T2PERTH:@081817z5411.30N/01208.38E_000/000g000t031r000p000P000h88b10163
20260208190241	DG0SD-10>APRX29,TCPIP*,qAC,T2PERTH:@081902z5411.30N/01208.38E_000/000g000t031r000p000P000h88b10165
20260208193921	DG0SD-10>APRX29,TCPIP*,qAC,T2PERTH:@081939z5411.30N/01208.38E_000/000g000t031r000p000P000h88b10163
20260208201911	DG0SD-10>APRX29,TCPIP*,qAC,T2PERTH:@082018z5411.30N/01208.38E_000/000g000t031r000p000P000h89b10164
20260208205631	DG0SD-10>APRX29,TCPIP*,qAC,T2PERTH:@082056z5411.30N/01208.38E_000/000g000t031r000p000P000h89b10163
20260208214031	DG0SD-10>APRX29,TCPIP*,qAC,T2PERTH:@082140z5411.30N/01208.38E_000/000g000t031r000p000P000h90b10164