APRS Packet Errors for N2XGL-6 (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
20260928002930N2XGL-6>APRARX,TCPIPC,T2BC,qAR,AE7AF:;RSONDE-CO*002928h3917.53N/1N2XGL-6>APR,TCPIP2BC:;RSONDE-CR*h3949437.64WO000/00016 IMET-E40 Clb=0.0m/s t=-03.997 MHz Typeadiosonde !w
20260928003430N2XGL-6>AARX,TCPAC,T2BC,qAR,AE7AF:;RSONDE-CO3428h3917N/10742.38WO1013/A=853 DFM-26040991 Cm/s t=.6C 404.410 MHz Type=DFM09 Rnde !wMa!
20260928005930N2XGL-6>APRCPIP,A,qAR,AE7AF:;RCR*9440413WO000/A=07228MET78EA40 Clb=0.0m/s t=-59.403T R
20260928013200N2XGL-6>APRARX,TCPIP*,qAS,AE7AF:;RSONDE-CR*013946.9304.69WO000/0001581 ID78EA4=0.0m/17.9C 97 MHz=IMET sonde
20260928013700N2XGL-6>APRX,TCPIPAC,T2BC,qAS,AE7AF:;RSO013715h4123.83043O000/00/A=035 IMET-BA0B Clb=0.0m/s 46.3C 402.999 MHz TypMT Radi !wYb!
20260928013800N2XGL-6>APTC,qAR,AE7AF:;RSONDE-CR*01381.61N/15WO000=011627 IMET-AD78EA40 Cl/s t=53.997 pe=IMEosonde