If true, I hope it's not my own digi.. UIView and Kiss TNC, can't be. I don't think this is the case, because I don't see the bad callsigns on my home digi or anywhere else, only on the nuvi. Here's two I didn't delete, K#0LXL-7 and KC0FXL-7. (Correct call is KC0LXL-7) I tried looking them up on aprs.fi and found nothing.
--- In [email protected], "Lynn W. Deffenbaugh (Mr)" <ldeff...@...> wrote: > > n0rxd wrote: > > I have the OT2m, nuvi 350 and FMI cable, all working as advertised. But > > occasionally, the nuvi plots a callsign with letter error (M0RXD), number > > error (N(RXD) or loses a letter (N0RX). These plots stay in favorites > > until I delete them. > > For RX, I use unsquelched audio from the radio mic connector and selected > > software DCD in the OT2m. I thought packets had a crc check that prevents > > such errors. Is there a setting or command (such as kantronics PASSALL) > > that I have set wrong? > > I didn't break open the T2 documentation, but if there's a digi in your > area that is running PASSALL (or the equivalent), your setting won't > matter. The digi will hear the bad packet and retransmit it with a > "corrected" checksum making everyone that hears the digipeated packet > believe it is correct. > > Lynn (D) - KJ4ERJ >
