APRS Packet Errors for SV9RPL (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
20190217141556SV9RPL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9RPL-DP!25425.79N/35123.40rRNG0034 IPSC2-GR-DMO MMDVM 438.8850 MHz
20190217143224SV9RPL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9RPL-DP!25425.79N/35123.40rRNG0034 IPSC2-GR-DMO MMDVM 438.8850 MHz
20190217144845SV9RPL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9RPL-DP!25425.79N/35123.40rRNG0034 IPSC2-GR-DMO MMDVM 438.8850 MHz
20190217150506SV9RPL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9RPL-DP!25425.79N/35123.40rRNG0034 IPSC2-GR-DMO MMDVM 438.8850 MHz
20190217152123SV9RPL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9RPL-DP!25425.79N/35123.40rRNG0034 IPSC2-GR-DMO MMDVM 438.8850 MHz
20190217153741SV9RPL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9RPL-DP!25425.79N/35123.40rRNG0034 IPSC2-GR-DMO MMDVM 438.8850 MHz
20190217155404SV9RPL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9RPL-DP!25425.79N/35123.40rRNG0034 IPSC2-GR-DMO MMDVM 438.8850 MHz
20190217161021SV9RPL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9RPL-DP!25425.79N/35123.40rRNG0034 IPSC2-GR-DMO MMDVM 438.8850 MHz
20190217162641SV9RPL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9RPL-DP!25425.79N/35123.40rRNG0034 IPSC2-GR-DMO MMDVM 438.8850 MHz
20190217164259SV9RPL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9RPL-DP!25425.79N/35123.40rRNG0034 IPSC2-GR-DMO MMDVM 438.8850 MHz
20190217165924SV9RPL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9RPL-DP!25425.79N/35123.40rRNG0034 IPSC2-GR-DMO MMDVM 438.8850 MHz
20190217171541SV9RPL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9RPL-DP!25425.79N/35123.40rRNG0034 IPSC2-GR-DMO MMDVM 438.8850 MHz
20190217173214SV9RPL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9RPL-DP!25425.79N/35123.40rRNG0034 IPSC2-GR-DMO MMDVM 438.8850 MHz
20190217174832SV9RPL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9RPL-DP!25425.79N/35123.40rRNG0034 IPSC2-GR-DMO MMDVM 438.8850 MHz
20190217180454SV9RPL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9RPL-DP!25425.79N/35123.40rRNG0034 IPSC2-GR-DMO MMDVM 438.8850 MHz
20190217182112SV9RPL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9RPL-DP!25425.79N/35123.40rRNG0034 IPSC2-GR-DMO MMDVM 438.8850 MHz
20190217183729SV9RPL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9RPL-DP!25425.79N/35123.40rRNG0034 IPSC2-GR-DMO MMDVM 438.8850 MHz
20190217185349SV9RPL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9RPL-DP!25425.79N/35123.40rRNG0034 IPSC2-GR-DMO MMDVM 438.8850 MHz
20190217191010SV9RPL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9RPL-DP!25425.79N/35123.40rRNG0034 IPSC2-GR-DMO MMDVM 438.8850 MHz
20190217192630SV9RPL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9RPL-DP!25425.79N/35123.40rRNG0034 IPSC2-GR-DMO MMDVM 438.8850 MHz
20190217194252SV9RPL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9RPL-DP!25425.79N/35123.40rRNG0034 IPSC2-GR-DMO MMDVM 438.8850 MHz
20190217195909SV9RPL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9RPL-DP!25425.79N/35123.40rRNG0034 IPSC2-GR-DMO MMDVM 438.8850 MHz