APRS Packet Errors for ZS4BMX-9 (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
20260523104028ZS4BMX-9>APCLEY,TCPIP*,qAC,APRS-ZA:/121040z0.00000S/00.00000Ev000/000/A=000000 35C 1Mv 4.13V In 14.26V 0kmh
20260523104129ZS4BMX-9>APCLEY,TCPIP*,qAC,APRS-ZA:/231041z0.00000S/00.00000Ev284/008/A=000000 36C 1Mv 4.12V In 14.21V 15kmh
20260523115236ZS4BMX-9>APCLEY,TCPIP*,qAC,APRS-ZA:/231152z0.00000S/00.00000Ev000/000/A=000000 32C 1Mv 4.10V In 13.98V 0kmh
20260523123543ZS4BMX-9>APCLEY,TCPIP*,qAC,APRS-ZA:/231235z0.00000S/00.00000Ev014/007/A=000000 33C 1Mv 4.09V If 12.52V 13kmh
20260523123547ZS4BMX-9>APCLEY,TCPIP*,qAC,APRS-ZA:/231235z0.00000S/00.00000Ev014/007/A=000000 33C 1Mv 4.14V In 13.35V 13kmh
20260523123618ZS4BMX-9>APCLEY,TCPIP*,qAC,APRS-ZA:/231236z0.00000S/00.00000Ev014/008/A=000000 33C 1Mv 4.10V In 14.05V 16kmh
20260523123657ZS4BMX-9>APCLEY,TCPIP*,qAC,APRS-ZA:/231236z0.00000S/00.00000Ev014/013/A=000000 33C 1Mv 4.09V In 14.08V 25kmh