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
20191114181706SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20191114183220SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20191114184732SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20191114190247SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20191114191809SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20191114193326SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20191114194841SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20191114200358SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20191114201924SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20191114203442SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20191114205000SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20191114210515SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20191114212034SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20191114213549SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20191114215106SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20191114220621SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20191114222138SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20191114223652SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20191114225207SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20191114230724SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20191114232244SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20191114233801SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20191114235313SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20191115000827SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz