APRS Packet Errors for SV4LAD (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
20190922112950	SV4LAD>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4LAD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz
20190922114501	SV4LAD>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4LAD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz
20190922120016	SV4LAD>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4LAD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz
20190922121526	SV4LAD>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4LAD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz
20190922123037	SV4LAD>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4LAD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz
20190922124550	SV4LAD>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4LAD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz
20190922130104	SV4LAD>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4LAD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz
20190922131613	SV4LAD>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4LAD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz
20190922133124	SV4LAD>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4LAD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz
20190922134635	SV4LAD>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4LAD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz