APRS Packet Errors for MB7UMA (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
20260208201341MB7UMA>APX210,TCPIP*,qAC,FIRST:=5124.95N/00145.45W#Xastir IGate on RPi 3a
20260208204342MB7UMA>APX210,TCPIP*,qAC,FIRST:=5124.95N/00145.45W#Xastir IGate on RPi 3a
20260208211343MB7UMA>APX210,TCPIP*,qAC,FIRST:=5124.95N/00145.45W#Xastir IGate on RPi 3a
20260208214344MB7UMA>APX210,TCPIP*,qAC,FIRST:=5124.95N/00145.45W#Xastir IGate on RPi 3a
20260208221345MB7UMA>APX210,TCPIP*,qAC,FIRST:=5124.95N/00145.45W#Xastir IGate on RPi 3a
20260208224346MB7UMA>APX210,TCPIP*,qAC,FIRST:=5124.95N/00145.45W#Xastir IGate on RPi 3a
20260208231347MB7UMA>APX210,TCPIP*,qAC,FIRST:=5124.95N/00145.45W#Xastir IGate on RPi 3a
20260208234348MB7UMA>APX210,TCPIP*,qAC,FIRST:=5124.95N/00145.45W#Xastir IGate on RPi 3a
20260209001349MB7UMA>APX210,TCPIP*,qAC,FIRST:=5124.95N/00145.45W#Xastir IGate on RPi 3a
20260209004350MB7UMA>APX210,TCPIP*,qAC,FIRST:=5124.95N/00145.45W#Xastir IGate on RPi 3a
20260209011351MB7UMA>APX210,TCPIP*,qAC,FIRST:=5124.95N/00145.45W#Xastir IGate on RPi 3a
20260209014352MB7UMA>APX210,TCPIP*,qAC,FIRST:=5124.95N/00145.45W#Xastir IGate on RPi 3a