APRS Packet Errors for N2VEN-3 (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
20250703192931N2VEN-3>APLRT1,WIDE1-1,WIDE2-1,qAO,N2VEN-10:!/9nEV<#S/_ ZQ.../...g...t083h32b10091
20250703193935N2VEN-3>APLRT1,WIDE1-1,WIDE2-1,qAO,N2VEN-10:!/9nG[<#S(_ SQ.../...g...t082h32b10081
20250703204439N2VEN-3>APLRT1,WIDE1-1,WIDE2-1,qAO,N2VEN-10:!/9nFK<#Ru_ ]Q.../...g...t082h32b10129
20250703205443N2VEN-3>APLRT1,WIDE1-1,WIDE2-1,qAO,N2VEN-10:!/9nFa<#Rc_ tQ.../...g...t082h32b10133
20250703210447N2VEN-3>APLRT1,WIDE1-1,WIDE2-1,qAO,N2VEN-10:!/9nFP<#RT_ *Q.../...g...t082h32b10135
20250703211452N2VEN-3>APLRT1,WIDE1-1,WIDE2-1,qAO,N2VEN-10:!/9nG6<#Ry_ 4Q.../...g...t081h32b10092
20250703212455N2VEN-3>APLRT1,WIDE1-1,WIDE2-1,qAO,N2VEN-10:!/9nHZ<#RT_ mQ.../...g...t081h32b10115
20250703213459N2VEN-3>APLRT1,WIDE1-1,WIDE2-1,qAO,N2VEN-10:!/9nH)<#Rq_ FQ.../...g...t081h32b10109
20250703214503N2VEN-3>APLRT1,WIDE1-1,WIDE2-1,qAO,N2VEN-10:!/9nFI<#Ri_ AQ.../...g...t082h32b10108