APRS Packet Errors for DL2MAI-N (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
20190219083248DL2MAI-N>APDG03,TCPIP*,qAC,T2NUERNBG:!481245.00ND111015.60E&/A=000000440 MMDVM Voice 433.62500MHz +0.0000MHz, DL2MAI_Pi-Star
20190219085248DL2MAI-N>APDG03,TCPIP*,qAC,T2NUERNBG:!481245.00ND111015.60E&/A=000000440 MMDVM Voice 433.62500MHz +0.0000MHz, DL2MAI_Pi-Star
20190219091248DL2MAI-N>APDG03,TCPIP*,qAC,T2NUERNBG:!481245.00ND111015.60E&/A=000000440 MMDVM Voice 433.62500MHz +0.0000MHz, DL2MAI_Pi-Star
20190219093258DL2MAI-N>APDG03,TCPIP*,qAC,T2NUERNBG:!481245.00ND111015.60E&/A=000000440 MMDVM Voice 433.62500MHz +0.0000MHz, DL2MAI_Pi-Star
20190219095258DL2MAI-N>APDG03,TCPIP*,qAC,T2NUERNBG:!481245.00ND111015.60E&/A=000000440 MMDVM Voice 433.62500MHz +0.0000MHz, DL2MAI_Pi-Star
20190219101308DL2MAI-N>APDG03,TCPIP*,qAC,T2NUERNBG:!481245.00ND111015.60E&/A=000000440 MMDVM Voice 433.62500MHz +0.0000MHz, DL2MAI_Pi-Star
20190219103308DL2MAI-N>APDG03,TCPIP*,qAC,T2NUERNBG:!481245.00ND111015.60E&/A=000000440 MMDVM Voice 433.62500MHz +0.0000MHz, DL2MAI_Pi-Star
20190219105308DL2MAI-N>APDG03,TCPIP*,qAC,T2NUERNBG:!481245.00ND111015.60E&/A=000000440 MMDVM Voice 433.62500MHz +0.0000MHz, DL2MAI_Pi-Star
20190219111308DL2MAI-N>APDG03,TCPIP*,qAC,T2NUERNBG:!481245.00ND111015.60E&/A=000000440 MMDVM Voice 433.62500MHz +0.0000MHz, DL2MAI_Pi-Star
20190219113308DL2MAI-N>APDG03,TCPIP*,qAC,T2NUERNBG:!481245.00ND111015.60E&/A=000000440 MMDVM Voice 433.62500MHz +0.0000MHz, DL2MAI_Pi-Star
20190219115309DL2MAI-N>APDG03,TCPIP*,qAC,T2NUERNBG:!481245.00ND111015.60E&/A=000000440 MMDVM Voice 433.62500MHz +0.0000MHz, DL2MAI_Pi-Star
20190219121319DL2MAI-N>APDG03,TCPIP*,qAC,T2NUERNBG:!481245.00ND111015.60E&/A=000000440 MMDVM Voice 433.62500MHz +0.0000MHz, DL2MAI_Pi-Star
20190219123319DL2MAI-N>APDG03,TCPIP*,qAC,T2NUERNBG:!481245.00ND111015.60E&/A=000000440 MMDVM Voice 433.62500MHz +0.0000MHz, DL2MAI_Pi-Star
20190219125319DL2MAI-N>APDG03,TCPIP*,qAC,T2NUERNBG:!481245.00ND111015.60E&/A=000000440 MMDVM Voice 433.62500MHz +0.0000MHz, DL2MAI_Pi-Star
20190219131319DL2MAI-N>APDG03,TCPIP*,qAC,T2NUERNBG:!481245.00ND111015.60E&/A=000000440 MMDVM Voice 433.62500MHz +0.0000MHz, DL2MAI_Pi-Star
20190219133319DL2MAI-N>APDG03,TCPIP*,qAC,T2NUERNBG:!481245.00ND111015.60E&/A=000000440 MMDVM Voice 433.62500MHz +0.0000MHz, DL2MAI_Pi-Star
20190219135329DL2MAI-N>APDG03,TCPIP*,qAC,T2NUERNBG:!481245.00ND111015.60E&/A=000000440 MMDVM Voice 433.62500MHz +0.0000MHz, DL2MAI_Pi-Star
20190219141329DL2MAI-N>APDG03,TCPIP*,qAC,T2NUERNBG:!481245.00ND111015.60E&/A=000000440 MMDVM Voice 433.62500MHz +0.0000MHz, DL2MAI_Pi-Star