APRS Packet Errors for EA1EME-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
20260209105208EA1EME-10>APLX00,TCPIP*,qAC,T2PERTH:!4333.15NL00555.18W&LoRa APRS/IGate | B5V0:4.28V
20260209113212EA1EME-10>APLX00,TCPIP*,qAC,T2PERTH:!4333.15NL00555.18W&LoRa APRS/IGate | B5V0:4.34V
20260209121216EA1EME-10>APLX00,TCPIP*,qAC,T2PERTH:!4333.15NL00555.18W&LoRa APRS/IGate | B5V0:4.27V
20260209125220EA1EME-10>APLX00,TCPIP*,qAC,T2PERTH:!4333.15NL00555.18W&LoRa APRS/IGate | B5V0:4.45V
20260209133224EA1EME-10>APLX00,TCPIP*,qAC,T2PERTH:!4333.15NL00555.18W&LoRa APRS/IGate | B5V0:4.41V
20260209141229EA1EME-10>APLX00,TCPIP*,qAC,T2PERTH:!4333.15NL00555.18W&LoRa APRS/IGate | B5V0:4.44V
20260209145233EA1EME-10>APLX00,TCPIP*,qAC,T2PERTH:!4333.15NL00555.18W&LoRa APRS/IGate | B5V0:4.37V
20260209153237EA1EME-10>APLX00,TCPIP*,qAC,T2PERTH:!4333.15NL00555.18W&LoRa APRS/IGate | B5V0:4.25V
20260209161243EA1EME-10>APLX00,TCPIP*,qAC,T2PERTH:!4333.15NL00555.18W&LoRa APRS/IGate | B5V0:4.36V