APRS Packet Errors for ZS4BMX-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
20260429150124ZS4BMX-9>APCLEY,TCPIP*,qAC,APRS-ZA:/091501z0.00000S/00.00000Ev000/000/A=000000 24C 1Mv 4.19V In 14.26V 0kmh
20260429163508ZS4BMX-9>APCLEY,TCPIP*,qAC,APRS-ZA:/091635z0.00000S/00.00000Ev000/000/A=000000 19C 1Mv 4.16V In 13.78V 0kmh
20260429183335ZS4BMX-9>APCLEY,TCPIP*,qAC,APRS-ZA:/091833z0.00000S/00.00000Ev000/000/A=000000 18C 1Mv 4.15V In 13.49V 0kmh
20260430053258ZS4BMX-9>APCLEY,TCPIP*,qAC,APRS-ZA:/100532z0.00000S/00.00000Ev000/000/A=000000 17C 1Mv 4.12V In 14.30V 0kmh