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
20171214224458VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171214230006VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171214230049VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171214231558VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171214233106VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171214234615VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171215000124VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171215000201VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171215001711VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171215003219VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171215004728VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171215010235VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171215010316VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171215011824VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171215013332VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171215014841VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171215020349VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171215020425VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171215021932VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171215023438VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171215024944VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171215030450VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171215030525VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171215032032VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171215033538VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171215035044VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171215040551VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171215040625VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171215042132VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz