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
20180218220815VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180218220854VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180218222355VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180218223857VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180218225358VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180218230900VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180218230942VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180218232444VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180218233945VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180218235447VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180219000951VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180219001032VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180219002535VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180219004036VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180219005541VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180219011045VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180219011124VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180219012628VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180219014129VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180219015630VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180219021133VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180219021214VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180219022716VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180219024217VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180219025719VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180219031221VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180219031258VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180219032800VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180219035803VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz