APRS Packet Errors for VE7KWK-1 (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
20190420160631VE7KWK-1>WIDE1-1,WIDE2-1,qAO,WA7LA-10:@201606z/5[K2/JHW_c)bg002t048r000p000P000h98b10173
20190420160748VE7KWK-1>WIDE1-1,WIDE2-1,qAR,VE7PKE:@201607z/5[K2/JHW_e)bg002t048r000p000P000h98b10173
20190420162747VE7KWK-1>WIDE1-1,WIDE2-1,qAR,VE7PKE:@201627z/5[K2/JHW_e)bg004t049r000p000P000h95b10173
20190420164749VE7KWK-1>WIDE1-1,WIDE2-1,qAR,VE7PKE:@201647z/5[K2/JHW_g)bg003t051r000p000P000h88b10173
20190420170748VE7KWK-1>WIDE1-1,WIDE2-1,qAR,VE7PKE:@201707z/5[K2/JHW_e!bg004t052r000p000P000h85b10173
20190420172750VE7KWK-1>WIDE1-1,WIDE2-1,qAR,VE7PKE:@201727z/5[K2/JHW_g!bg003t054r000p000P000h82b10173
20190420174747VE7KWK-1>WIDE1-1,WIDE2-1,qAR,VE7PKE:@201747z/5[K2/JHW_])bg007t056r000p000P000h77b10173
20190420180748VE7KWK-1>WIDE1-1,WIDE2-1,qAO,WA7LA-10:@201807z/5[K2/JHW_a)bg008t056r000p000P000h74b10174
20190420182750VE7KWK-1>WIDE1-1,WIDE2-1,qAO,WA7LA-10:@201827z/5[K2/JHW_b2bg009t057r000p000P000h74b10173
20190420184747VE7KWK-1>WIDE1-1,WIDE2-1,qAR,VE7PKE:@201847z/5[K2/JHW_f)bg007t058r000p000P000h73b10173