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
20171217021514VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171217023022VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171217024531VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171217030039VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171217030113VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171217031622VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171217033130VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171217034638VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171217040146VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171217040225VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171217041734VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171217043241VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171217044750VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171217050257VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171217050331VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171217051840VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171217053347VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171217054856VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171217060403VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171217060439VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171217061947VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171217063456VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171217065005VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171217070514VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171217070548VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171217072057VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171217073605VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171217075114VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171217080621VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz