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
20190923094550SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190923100100SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190923101618SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190923103127SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190923104640SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190923110149SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190923111702SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190923113210SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190923114720SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190923120231SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190923121743SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190923123253SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190923124803SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190923130311SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190923131825SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190923133333SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190923134843SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190923140351SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190923141906SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190923143415SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190923144924SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190923150434SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190923151948SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190923153458SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz