APRS Packet Errors for VE2RHK (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
20171216090802VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171216092311VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171216095404VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171216100912VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171216102422VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171216103931VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171216104007VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171216105516VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171216111023VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171216112532VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171216114039VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171216114113VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171216115622VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171216121129VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171216122638VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171216124146VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171216124219VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171216125728VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171216131236VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171216132745VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171216134253VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171216134329VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171216135838VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171216141346VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171216142857VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171216144407VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171216144441VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz