APRS Packet Errors for 4O0VBA (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
20250316224709	4O0VBA>BEACON,WIDE1-1,WIDE2-1,qAO,4O7JAZ:/000000z0000.00N/00000.00E>PLXTracker.
20250316231711	4O0VBA>BEACON,WIDE1-1,WIDE2-1,qAO,4O7JAZ:/000000z0000.00N/00000.00E>PLXTracker.
20250316234713	4O0VBA>BEACON,WIDE1-1,WIDE2-1,qAO,4O7JAZ:/000000z0000.00N/00000.00E>PLXTracker.
20250317001714	4O0VBA>BEACON,WIDE1-1,WIDE2-1,qAO,4O7JAZ:/000000z0000.00N/00000.00E>PLXTracker.
20250317004716	4O0VBA>BEACON,WIDE1-1,WIDE2-1,qAO,4O7JAZ:/000000z0000.00N/00000.00E>PLXTracker.
20250317011718	4O0VBA>BEACON,WIDE1-1,WIDE2-1,qAO,4O7JAZ:/000000z0000.00N/00000.00E>PLXTracker.
20250317014719	4O0VBA>BEACON,WIDE1-1,WIDE2-1,qAO,4O7JAZ:/000000z0000.00N/00000.00E>PLXTracker.
20250317021721	4O0VBA>BEACON,WIDE1-1,WIDE2-1,qAO,4O7JAZ:/000000z0000.00N/00000.00E>PLXTracker.
20250317024723	4O0VBA>BEACON,WIDE1-1,WIDE2-1,qAO,4O7JAZ:/000000z0000.00N/00000.00E>PLXTracker.
20250317031724	4O0VBA>BEACON,WIDE1-1,WIDE2-1,qAO,4O7JAZ:/000000z0000.00N/00000.00E>PLXTracker.
20250317034726	4O0VBA>BEACON,WIDE1-1,WIDE2-1,qAO,4O7JAZ:/000000z0000.00N/00000.00E>PLXTracker.
20250317041728	4O0VBA>BEACON,WIDE1-1,WIDE2-1,qAO,4O7JAZ:/000000z0000.00N/00000.00E>PLXTracker.