APRS Packet Errors for SV1HBS (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
20191017025113SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20191017030629SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20191017032141SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20191017033651SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20191017035200SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20191017040734SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20191017042246SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20191017043754SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20191017045304SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20191017050818SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20191017052327SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20191017053836SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20191017055346SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20191017060858SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20191017062408SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20191017063917SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20191017065428SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20191017070941SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20191017072450SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20191017073959SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20191017075509SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20191017081021SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20191017082533SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz