APRS Packet Errors for ZS1OA-4 (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
20200920114128ZS1OA-4>APU25N,WIDE2-2,qAO,ZS1OSS-1:=0,LOC_CNT=6 (EYWinGate v6.3)
20200920122940ZS1OA-4>APU25N,WIDE2-2,qAO,ZS1OSS-1:=000010RNG0001 440 Voice 438.60000MHz -7.6000MHz
20200920130347ZS1OA-4>APU25N,WIDE2-2,qAO,ZS1OSS-1:=005293 42C 0Mv 0000.0km If 12.89V 0kmh
20200920132318ZS1OA-4>APU25N,WIDE2-2,qAO,ZS1OSS-1:/A=004711 SATS09 HDOP1.0 MTN-SA
20200920154053ZS1OA-4>APU25N,WIDE2-2,qAO,ZS1OSS-1:/02749.86E>000/000/GPS INVLD 40C 0159.4km If 12.29V 0kmh