APRS Packet Errors for UR4FY-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
20251013091109UR4FY-4>APRS,TCPIP*,qAC,HB1LNK-11:!000.00N/0000.00ErConnesso ad HBLINK RX: 432.600000 TX: 432.600000
20251013092609UR4FY-4>APRS,TCPIP*,qAC,HB1LNK-11:!000.00N/0000.00ErConnesso ad HBLINK RX: 432.600000 TX: 432.600000
20251013101109UR4FY-4>APRS,TCPIP*,qAC,HB1LNK-11:!000.00N/0000.00ErConnesso ad HBLINK RX: 432.600000 TX: 432.600000
20251013102609UR4FY-4>APRS,TCPIP*,qAC,HB1LNK-11:!000.00N/0000.00ErConnesso ad HBLINK RX: 432.600000 TX: 432.600000
20251013121109UR4FY-4>APRS,TCPIP*,qAC,HB1LNK-11:!000.00N/0000.00ErConnesso ad HBLINK RX: 432.600000 TX: 432.600000
20251013122609UR4FY-4>APRS,TCPIP*,qAC,HB1LNK-11:!000.00N/0000.00ErConnesso ad HBLINK RX: 432.600000 TX: 432.600000
20251013124109UR4FY-4>APRS,TCPIP*,qAC,HB1LNK-11:!000.00N/0000.00ErConnesso ad HBLINK RX: 432.600000 TX: 432.600000
20251013125609UR4FY-4>APRS,TCPIP*,qAC,HB1LNK-11:!000.00N/0000.00ErConnesso ad HBLINK RX: 432.600000 TX: 432.600000
20251013131109UR4FY-4>APRS,TCPIP*,qAC,HB1LNK-11:!000.00N/0000.00ErConnesso ad HBLINK RX: 432.600000 TX: 432.600000