APRS Packet Errors for CA2SR (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
20260717001417CA2SR>APRS,TCPIP*,qAC,HB1LNK-11:!000.00N/0000.00ErConnesso ad HBLINK RX: 462.550000 TX: 462.550000
20260717002917CA2SR>APRS,TCPIP*,qAC,HB1LNK-11:!000.00N/0000.00ErConnesso ad HBLINK RX: 462.550000 TX: 462.550000
20260717004416CA2SR>APRS,TCPIP*,qAC,HB1LNK-11:!000.00N/0000.00ErConnesso ad HBLINK RX: 462.550000 TX: 462.550000
20260717005917CA2SR>APRS,TCPIP*,qAC,HB1LNK-11:!000.00N/0000.00ErConnesso ad HBLINK RX: 462.550000 TX: 462.550000
20260717011417CA2SR>APRS,TCPIP*,qAC,HB1LNK-11:!000.00N/0000.00ErConnesso ad HBLINK RX: 462.550000 TX: 462.550000
20260717012916CA2SR>APRS,TCPIP*,qAC,HB1LNK-11:!000.00N/0000.00ErConnesso ad HBLINK RX: 462.550000 TX: 462.550000
20260717014416CA2SR>APRS,TCPIP*,qAC,HB1LNK-11:!000.00N/0000.00ErConnesso ad HBLINK RX: 462.550000 TX: 462.550000
20260717015917CA2SR>APRS,TCPIP*,qAC,HB1LNK-11:!000.00N/0000.00ErConnesso ad HBLINK RX: 462.550000 TX: 462.550000
20260717021417CA2SR>APRS,TCPIP*,qAC,HB1LNK-11:!000.00N/0000.00ErConnesso ad HBLINK RX: 462.550000 TX: 462.550000
20260717022917CA2SR>APRS,TCPIP*,qAC,HB1LNK-11:!000.00N/0000.00ErConnesso ad HBLINK RX: 462.550000 TX: 462.550000
20260717024416CA2SR>APRS,TCPIP*,qAC,HB1LNK-11:!000.00N/0000.00ErConnesso ad HBLINK RX: 462.550000 TX: 462.550000