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
20171216091224VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20171216091300VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20171216092819VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20171216095856VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20171216101413VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20171216103004VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20171216104522VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20171216110042VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20171216111600VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20171216111632VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20171216113153VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20171216114710VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20171216120230VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20171216121749VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20171216121820VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20171216123343VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20171216124903VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20171216130426VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20171216131945VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20171216132017VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20171216133537VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20171216135055VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20171216140615VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20171216142134VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20171216142207VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20171216143728VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20171216145250VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz