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
20260208165015EA1EME-10>APLX00,TCPIP*,qAC,T2PERTH:!4333.15NL00555.18W&LoRa APRS/IGate | B5V0:4.47V
20260208173019EA1EME-10>APLX00,TCPIP*,qAC,T2PERTH:!4333.15NL00555.18W&LoRa APRS/IGate | B5V0:4.25V
20260208181024EA1EME-10>APLX00,TCPIP*,qAC,T2PERTH:!4333.15NL00555.18W&LoRa APRS/IGate | B5V0:4.47V
20260208185028EA1EME-10>APLX00,TCPIP*,qAC,T2PERTH:!4333.15NL00555.18W&LoRa APRS/IGate | B5V0:4.25V
20260208193032EA1EME-10>APLX00,TCPIP*,qAC,T2PERTH:!4333.15NL00555.18W&LoRa APRS/IGate | B5V0:4.46V
20260208201036EA1EME-10>APLX00,TCPIP*,qAC,T2PERTH:!4333.15NL00555.18W&LoRa APRS/IGate | B5V0:4.48V
20260208205040EA1EME-10>APLX00,TCPIP*,qAC,T2PERTH:!4333.15NL00555.18W&LoRa APRS/IGate | B5V0:4.30V
20260208213044EA1EME-10>APLX00,TCPIP*,qAC,T2PERTH:!4333.15NL00555.18W&LoRa APRS/IGate | B5V0:4.38V
20260208221048EA1EME-10>APLX00,TCPIP*,qAC,T2PERTH:!4333.15NL00555.18W&LoRa APRS/IGate | B5V0:4.45V