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
20180420083338VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180420084852VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180420090406VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180420091919VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180420092015VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180420093529VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180420095041VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180420100555VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180420102107VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180420102203VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180420103722VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180420105233VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180420110746VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180420112258VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180420112355VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180420113913VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180420115425VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180420120944VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180420122454VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180420122550VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180420124102VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180420125614VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180420131127VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180420132639VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180420132734VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180420134245VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180420135755VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180420141306VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz