APRS Packet Errors for SZ1RSF (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
20190419191531SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190419193216SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190419194901SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190419200544SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190419202230SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190419203911SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190419205555SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190419211241SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190419212922SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190419214558SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190419220239SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190419221922SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190419223616SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190419225301SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190419230944SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190419232620SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190419234300SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190419235934SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190420001610SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190420003255SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190420004950SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz