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
20180425235425VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180426000933VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180426001033VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180426002542VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180426004049VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180426005557VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180426011106VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180426011206VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180426012715VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180426014224VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180426015733VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180426021240VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180426021408VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180426022916VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180426024423VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180426025932VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180426031444VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180426031544VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180426033052VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180426034559VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180426040108VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180426041618VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180426041713VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180426043221VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180426044729VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180426050237VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180426051745VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180426051841VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz
20180426053350VE2RHK>APDG02,TCPIP*,qAU,DMRAPRS:)VE2RHK-DP!4500.00N/184467440&RNG0034 IPSC2 DMRplus 448.6250MHz