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
20191120075203SV2MCZ>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV2MCZ-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.9500 MHz
20191120080718SV2MCZ>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV2MCZ-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.9500 MHz
20191120082232SV2MCZ>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV2MCZ-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.9500 MHz
20191120083745SV2MCZ>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV2MCZ-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.9500 MHz
20191120085258SV2MCZ>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV2MCZ-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.9500 MHz
20191120090810SV2MCZ>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV2MCZ-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.9500 MHz
20191120092327SV2MCZ>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV2MCZ-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.9500 MHz
20191120093841SV2MCZ>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV2MCZ-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.9500 MHz
20191120095354SV2MCZ>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV2MCZ-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.9500 MHz
20191120100906SV2MCZ>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV2MCZ-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.9500 MHz
20191120102423SV2MCZ>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV2MCZ-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.9500 MHz
20191120103934SV2MCZ>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV2MCZ-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.9500 MHz
20191120105447SV2MCZ>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV2MCZ-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.9500 MHz
20191120110959SV2MCZ>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV2MCZ-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.9500 MHz
20191120112516SV2MCZ>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV2MCZ-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.9500 MHz
20191120114028SV2MCZ>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV2MCZ-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.9500 MHz
20191120115539SV2MCZ>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV2MCZ-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.9500 MHz
20191120121052SV2MCZ>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV2MCZ-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.9500 MHz
20191120122611SV2MCZ>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV2MCZ-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.9500 MHz
20191120124120SV2MCZ>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV2MCZ-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.9500 MHz
20191120125631SV2MCZ>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV2MCZ-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.9500 MHz
20191120131145SV2MCZ>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV2MCZ-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.9500 MHz
20191120132701SV2MCZ>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV2MCZ-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.9500 MHz
20191120134215SV2MCZ>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV2MCZ-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.9500 MHz