APRS Packet Errors for EA2DXR-10 (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
20260209132444EA2DXR-10>APLRG1,WIDE1-1,QA7L8,qAR,ED2ZAD-10:!L8X]jMdLV# G. Batt=4.08V
20260209133944EA2DXR-10>APLRG1,WIDE1-1,QA8L8,qAR,ED2ZAD-10:!L8X]jMdLV# G. Batt=4.04V
20260209135445EA2DXR-10>APLRG1,WIDE1-1,QB2M1,qAR,ED2ZAD-10:!L8X]jMdLV# G. Batt=4.05V
20260209142445EA2DXR-10>APLRG1,WIDE1-1,QB1M1,qAR,ED2ZAD-10:!L8X]jMdLV# G. Batt=4.02V
20260209160945EA2DXR-10>APLRG1,WIDE1-1,QB9M0,qAR,ED2ZAD-10:!L8X]jMdLV# G. Batt=4.10V
20260209163946EA2DXR-10>APLRG1,WIDE1-1,QB4M0,qAR,ED2ZAD-10:!L8X]jMdLV# G. Batt=4.08V
20260209165446EA2DXR-10>APLRG1,WIDE1-1,QB3L8,qAR,ED2ZAD-10:!L8X]jMdLV# G. Batt=4.03V
20260209170946EA2DXR-10>APLRG1,WIDE1-1,QB4L8,qAR,ED2ZAD-10:!L8X]jMdLV# G. Batt=4.07V
20260209172446EA2DXR-10>APLRG1,WIDE1-1,QB9M3,qAR,ED2ZAD-10:!L8X]jMdLV# G. Batt=4.08V
20260209173946EA2DXR-10>APLRG1,WIDE1-1,qAR,EA2BHE-10:!L8X]jMdLV# G. Batt=4.03V
20260209175446EA2DXR-10>APLRG1,WIDE1-1,qAR,EA2BHE-10:!L8X]jMdLV# G. Batt=4.04V
20260209180946EA2DXR-10>APLRG1,WIDE1-1,qAR,EA2BHE-10:!L8X]jMdLV# G. Batt=4.07V
20260209182446EA2DXR-10>APLRG1,WIDE1-1,qAR,EA2BHE-10:!L8X]jMdLV# G. Batt=4.06V