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
20171218144712VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171218144747VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171218150258VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171218151808VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171218153319VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171218154829VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171218154905VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171218160416VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171218161926VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171218163437VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171218164947VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171218165024VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171218170535VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171218172045VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171218173557VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171218175107VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171218175141VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171218180652VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171218182202VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171218183714VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171218185224VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171218190807VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171218192317VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171218193829VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171218195338VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171218195413VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171218200924VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20171218202436VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz