APRS Packet Errors for SV1LJS (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
20191113150804SV1LJS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1LJS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 433.3000 MHz
20191113150804SV1LJS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1LJS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.2000 MHz
20191113152318SV1LJS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1LJS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 433.3000 MHz
20191113152318SV1LJS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1LJS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.2000 MHz
20191113153832SV1LJS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1LJS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 433.3000 MHz
20191113153832SV1LJS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1LJS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.2000 MHz
20191113155347SV1LJS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1LJS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 433.3000 MHz
20191113155348SV1LJS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1LJS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.2000 MHz
20191113160901SV1LJS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1LJS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 433.3000 MHz
20191113160901SV1LJS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1LJS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.2000 MHz
20191113162418SV1LJS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1LJS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 433.3000 MHz
20191113162419SV1LJS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1LJS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.2000 MHz
20191113163933SV1LJS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1LJS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 433.3000 MHz
20191113163933SV1LJS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1LJS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.2000 MHz
20191113165451SV1LJS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1LJS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 433.3000 MHz
20191113165451SV1LJS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1LJS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.2000 MHz
20191113171004SV1LJS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1LJS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 433.3000 MHz
20191113171005SV1LJS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1LJS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.2000 MHz
20191113172517SV1LJS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1LJS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.2000 MHz
20191113174029SV1LJS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1LJS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.2000 MHz
20191113175547SV1LJS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1LJS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.2000 MHz
20191113181102SV1LJS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1LJS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.2000 MHz
20191113182615SV1LJS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1LJS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.2000 MHz
20191113184127SV1LJS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1LJS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.2000 MHz
20191113185643SV1LJS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1LJS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.2000 MHz
20191113191155SV1LJS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1LJS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.2000 MHz
20191113192709SV1LJS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1LJS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.2000 MHz
20191113194222SV1LJS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1LJS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.2000 MHz
20191113195736SV1LJS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1LJS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.2000 MHz
20191113201248SV1LJS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1LJS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.2000 MHz
20191113202802SV1LJS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1LJS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.2000 MHz
20191113204315SV1LJS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1LJS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.2000 MHz
20191113205832SV1LJS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1LJS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.2000 MHz