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
20190917012403SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190917013912SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190917015421SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190917020930SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190917022443SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190917023956SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190917025506SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190917031014SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190917032526SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190917034034SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190917035543SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190917041053SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190917042607SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190917044116SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190917045626SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190917051136SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190917052650SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190917054200SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190917055710SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190917061220SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190917062733SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190917064244SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190917065754SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190917071307SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz