APRS Packet Errors for SV2MCZ (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
20190524150626SV2MCZ>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV2MCZ-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.9500 MHz
20190524152314SV2MCZ>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV2MCZ-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.9500 MHz
20190524154006SV2MCZ>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV2MCZ-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.9500 MHz
20190524155649SV2MCZ>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV2MCZ-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.9500 MHz
20190524161337SV2MCZ>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV2MCZ-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.9500 MHz
20190524163017SV2MCZ>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV2MCZ-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.9500 MHz
20190524164701SV2MCZ>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV2MCZ-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.9500 MHz
20190524170347SV2MCZ>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV2MCZ-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.9500 MHz
20190524172041SV2MCZ>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV2MCZ-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.9500 MHz
20190524173731SV2MCZ>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV2MCZ-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.9500 MHz
20190524175422SV2MCZ>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV2MCZ-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.9500 MHz
20190524181112SV2MCZ>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV2MCZ-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.9500 MHz
20190524183414SV2MCZ>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV2MCZ-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.9500 MHz
20190524192324SV2MCZ>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV2MCZ-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.9500 MHz
20190524195131SV2MCZ>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV2MCZ-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.9500 MHz
20190524200816SV2MCZ>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV2MCZ-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.9500 MHz
20190524203113SV2MCZ>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV2MCZ-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.9500 MHz
20190524204803SV2MCZ>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV2MCZ-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.9500 MHz