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
20190319105207SV2MCZ>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV2MCZ-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.9500 MHz
20190319110834SV2MCZ>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV2MCZ-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.9500 MHz
20190319112501SV2MCZ>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV2MCZ-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.9500 MHz
20190319114131SV2MCZ>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV2MCZ-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.9500 MHz
20190319115801SV2MCZ>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV2MCZ-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.9500 MHz
20190319121431SV2MCZ>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV2MCZ-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.9500 MHz
20190319123103SV2MCZ>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV2MCZ-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.9500 MHz
20190319124736SV2MCZ>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV2MCZ-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.9500 MHz
20190319130409SV2MCZ>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV2MCZ-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.9500 MHz
20190319132042SV2MCZ>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV2MCZ-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.9500 MHz
20190319133717SV2MCZ>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV2MCZ-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.9500 MHz
20190319135348SV2MCZ>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV2MCZ-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.9500 MHz
20190319141014SV2MCZ>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV2MCZ-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.9500 MHz
20190319142641SV2MCZ>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV2MCZ-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.9500 MHz
20190319144308SV2MCZ>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV2MCZ-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.9500 MHz
20190319145936SV2MCZ>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV2MCZ-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.9500 MHz
20190319151602SV2MCZ>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV2MCZ-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.9500 MHz
20190319153227SV2MCZ>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV2MCZ-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.9500 MHz
20190319154853SV2MCZ>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV2MCZ-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.9500 MHz
20190319160523SV2MCZ>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV2MCZ-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.9500 MHz
20190319162149SV2MCZ>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV2MCZ-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.9500 MHz
20190319163814SV2MCZ>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV2MCZ-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.9500 MHz