APRS Packet Errors for ND7L-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
20260209103453ND7L-10>APSN01,TCPIP*,qAC,T2USANE:=4334.72N/11628.90W#/A=002635CSN iGate & Digi via ND7L-10
20260209110456ND7L-10>APSN01,TCPIP*,qAC,T2USANE:=4334.72N/11628.90W#/A=002630CSN iGate & Digi via ND7L-10
20260209113458ND7L-10>APSN01,TCPIP*,qAC,T2MCI:=4334.72N/11628.90W#/A=002629CSN iGate & Digi via ND7L-10
20260209120501ND7L-10>APSN01,TCPIP*,qAC,T2MCI:=4334.72N/11628.90W#/A=002634CSN iGate & Digi via ND7L-10
20260209123502ND7L-10>APSN01,TCPIP*,qAC,T2BC:=4334.72N/11628.89W#/A=002625CSN iGate & Digi via ND7L-10
20260209130506ND7L-10>APSN01,TCPIP*,qAC,T2BC:=4334.72N/11628.90W#/A=002630CSN iGate & Digi via ND7L-10
20260209133508ND7L-10>APSN01,TCPIP*,qAC,T2RDU:=4334.72N/11628.90W#/A=002627CSN iGate & Digi via ND7L-10
20260209140511ND7L-10>APSN01,TCPIP*,qAC,T2RDU:=4334.72N/11628.89W#/A=002630CSN iGate & Digi via ND7L-10
20260209143512ND7L-10>APSN01,TCPIP*,qAC,T2CAEAST:=4334.72N/11628.90W#/A=002628CSN iGate & Digi via ND7L-10
20260209150516ND7L-10>APSN01,TCPIP*,qAC,T2CAEAST:=4334.72N/11628.90W#/A=002631CSN iGate & Digi via ND7L-10
20260209153519ND7L-10>APSN01,TCPIP*,qAC,T2TEXAS:=4334.72N/11628.90W#/A=002629CSN iGate & Digi via ND7L-10
20260209160522ND7L-10>APSN01,TCPIP*,qAC,T2MCI:=4334.72N/11628.90W#/A=002626CSN iGate & Digi via ND7L-10