APRS Packet Errors for VE1UHF (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
20180420083307VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF-DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20180420083358VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF-DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20180420084908VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF-DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20180420090416VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF-DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20180420091926VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF-DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20180420093434VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF-DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20180420093527VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF-DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20180420095037VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF-DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20180420100545VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF-DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20180420102055VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF-DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20180420103603VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF-DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20180420103656VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF-DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20180420105205VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF-DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20180420110714VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF-DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20180420112224VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF-DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20180420113734VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF-DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20180420113826VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF-DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20180420115339VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF-DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20180420120849VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF-DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20180420122402VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF-DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20180420123912VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF-DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20180420124004VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF-DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20180420125517VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF-DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20180420131028VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF-DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20180420132540VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF-DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20180420134052VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF-DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20180420134145VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF-DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20180420135657VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF-DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20180420141208VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF-DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz