APRS Packet Errors for EA2CW-13 (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
20260220140648EA2CW-13>APLWX1,WIDE1-1,qAR,EA2CW-10:!4315.56N/00255.60W_.../...g...tnanr...p...P...hnanbnanL026 Lux:2746_WX_APRS_LoRa
20260220142224EA2CW-13>APLWX1,WIDE1-1,qAR,EA2CW-10:!4315.56N/00255.60W_.../...g...tnanr...p...P...hnanbnanL025 Lux:2591_WX_APRS_LoRa
20260220143800EA2CW-13>APLWX1,WIDE1-1,qAR,EA2CW-10:!4315.56N/00255.60W_.../...g...tnanr...p...P...hnanbnanL017 Lux:1833_WX_APRS_LoRa
20260220145336EA2CW-13>APLWX1,WIDE1-1,qAR,EA2CW-10:!4315.56N/00255.60W_.../...g...tnanr...p...P...hnanbnanL016 Lux:1721_WX_APRS_LoRa
20260220150912EA2CW-13>APLWX1,WIDE1-1,qAR,EA2CW-10:!4315.56N/00255.60W_.../...g...tnanr...p...P...hnanbnanL015 Lux:1639_WX_APRS_LoRa
20260220155554EA2CW-13>APLWX1,WIDE1-1,qAR,EA2CW-10:!4315.56N/00255.60W_.../...g...tnanr...p...P...hnanbnanL034 Lux:3572_WX_APRS_LoRa
20260220161130EA2CW-13>APLWX1,WIDE1-1,qAR,EA2CW-10:!4315.56N/00255.60W_.../...g...tnanr...p...P...hnanbnanL036 Lux:3744_WX_APRS_LoRa