APRS Packet Errors for DG7MEU-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
20260209134506DG7MEU-10>APLRG1,TCPIP*,qAC,T2PERTH:!L6Iv3Q(1g& GLoRa APRS
20260209141506DG7MEU-10>APLRG1,TCPIP*,qAC,T2PERTH:!L6Iv3Q(1g& GLoRa APRS
20260209144506DG7MEU-10>APLRG1,TCPIP*,qAC,T2PERTH:!L6Iv3Q(1g& GLoRa APRS
20260209151506DG7MEU-10>APLRG1,TCPIP*,qAC,T2PERTH:!L6Iv3Q(1g& GLoRa APRS
20260209154506DG7MEU-10>APLRG1,TCPIP*,qAC,T2PERTH:!L6Iv3Q(1g& GLoRa APRS
20260209161506DG7MEU-10>APLRG1,TCPIP*,qAC,T2PERTH:!L6Iv3Q(1g& GLoRa APRS
20260209164506DG7MEU-10>APLRG1,TCPIP*,qAC,T2PERTH:!L6Iv3Q(1g& GLoRa APRS
20260209171506DG7MEU-10>APLRG1,TCPIP*,qAC,T2PERTH:!L6Iv3Q(1g& GLoRa APRS
20260209174506DG7MEU-10>APLRG1,TCPIP*,qAC,T2PERTH:!L6Iv3Q(1g& GLoRa APRS
20260209181506DG7MEU-10>APLRG1,TCPIP*,qAC,T2PERTH:!L6Iv3Q(1g& GLoRa APRS
20260209184506DG7MEU-10>APLRG1,TCPIP*,qAC,T2PERTH:!L6Iv3Q(1g& GLoRa APRS
20260209191507DG7MEU-10>APLRG1,TCPIP*,qAC,T2PERTH:!L6Iv3Q(1g& GLoRa APRS