APRS Packet Errors for VE1UHF (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
20180222083034VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF-DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20180222084544VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF-DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20180222084619VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF-DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20180222090130VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF-DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20180222091640VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF-DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20180222093151VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF-DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20180222094701VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF-DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20180222094737VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF-DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20180222100248VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF-DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20180222101758VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF-DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20180222103310VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF-DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20180222104820VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF-DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20180222104855VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF-DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20180222110406VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF-DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20180222111916VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF-DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20180222113428VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF-DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20180222114937VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF-DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20180222115012VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF-DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20180222120524VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF-DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20180222122034VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF-DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20180222123545VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF-DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20180222125055VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF-DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20180222125130VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF-DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20180222130641VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF-DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20180222132151VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF-DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20180222133702VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF-DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20180222135212VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF-DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20180222135248VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF-DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz
20180222140759VE1UHF>APDG02,TCPIP*,qAU,DMRAPRS:)VE1UHF-DP!4600.00N/184467440&RNG0034 IPSC2 DMRplus 443.3000MHz