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
20180217153902VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180217153941VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180217155447VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180217160952VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180217162458VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180217164003VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180217164042VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180217165548VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180217172602VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180217174108VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180217174147VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180217175654VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180217181159VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180217182706VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180217184212VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180217184250VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180217185757VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180217191303VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180217201523VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180217203026VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180217204530VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180217204609VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180217210113VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180217211617VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz