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
20171218145315VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20171218150829VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20171218150901VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20171218152416VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20171218153930VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20171218155444VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20171218160957VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20171218161029VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20171218162543VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20171218164056VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20171218165611VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20171218171124VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20171218171156VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20171218172710VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20171218174221VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20171218175733VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20171218181244VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20171218181317VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20171218182829VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20171218184340VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20171218185852VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20171218191403VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20171218191436VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20171218192952VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20171218194505VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20171218201552VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20171218203106VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz