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
20180221052049VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180221053550VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180221055052VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180221055129VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180221060630VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180221062132VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180221063633VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180221065135VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180221065210VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180221070712VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180221072214VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180221073721VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180221075222VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180221075258VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180221080800VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180221082301VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180221083802VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180221085305VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180221085341VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180221090843VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180221092344VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180221093846VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180221095347VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180221095425VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180221100926VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180221102427VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180221103929VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180221105430VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180221105507VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz