APRS Packet Errors for ZR6AGS-9 (last 24 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
20260909111432ZR6AGS-9>APCLEY,TCPIP*,qAC,APRS-ZA:/091114z0.00000S/00.00000E>000/000/A=000000 25C 1Mv 4.09V In 13.74V 0kmh
20260909111816ZR6AGS-9>APCLEY,TCPIP*,qAC,APRS-ZA:/091118z0.00000S/00.00000E>000/000/A=000000 26C 1Mv 4.14V In 13.74V 0kmh
20260909111826ZR6AGS-9>APCLEY,TCPIP*,qAC,APRS-ZA:/091118z0.00000S/00.00000E>246/555/A=000000 26C 1Mv 4.17V In 13.74V 106kmh
20260909111846ZR6AGS-9>APCLEY,TCPIP*,qAC,APRS-ZA:/091118z0.00000S/00.00000E>072/003/A=000000 26C 1Mv 4.10V In 13.73V 13kmh
20260909111907ZR6AGS-9>APCLEY,TCPIP*,qAC,APRS-ZA:/091119z0.00000S/00.00000E>062/004/A=000000 26C 1Mv 4.14V In 13.74V 32kmh
20260909111946ZR6AGS-9>APCLEY,TCPIP*,qAC,APRS-ZA:/091119z0.00000S/00.00000E>281/002/A=000000 26C 1Mv 4.10V In 13.73V 6kmh
20260909113948ZR6AGS-9>APCLEY,TCPIP*,qAC,APRS-ZA:/091139z0.00000S/00.00000E>000/000/A=000000 29C 1Mv 4.07V In 13.39V 0kmh