Larry N9JY wrote... > Passall is off. Installed firmware is 55076. I'm seeing the garbled > data in the form of call signs having letters changed or dropped and > also flakey positions (e.g., out to sea many miles in the worst case). > I have been running it as a kiss TNC into UI-View-32. I see the > position issues on UI-View and APRS.FI but only the funny call signs > on APRS.FI.
OK, so the TNC for N9JY-1 is the Tracker 2. Are you seeing the garbled data right in the UI-View terminal window with the filter set to exclude Internet traffic? > The corrupted call signs are visible on APRS.FI in the 'stations near > N9JY-1' and I'm assuming my machine is the culprit although I don't > see any indication on the local UI-View logs. Also have seen some > sporatic fairly long delays in digipeating (a minute or two), which I > think might be an OS/Uiview issue. I know that the KPC3+ in KISS mode introduces delays after a week or two. I've witnessed it, but have been for ages been trying to document it properly for Kantronics who is supposedly testing it themselves. It is possible that the problem is not "KPC3+ specific" but anecdotally, and in my own observations so far, it would appear to be. > Here's a config dump from the OT2m: > ALIAS 1:WIDE1 2:WIDE2 3:TEMP > COMMENT - PSJ Fill-in > DIGI ON > DIGIID 1:ON 2:ON 3:ON 4:ON 5:ON 6:ON 7:ON 8:ON > DUPETIME 10 > HOPLIMIT 1:1 2:1 3:5 4:0 5:0 6:0 7:0 8:0 > INTERVAL 0 > MYCALL N9JY-1 > PASSALL OFF > POSITION 2829.07N 08048.17W > PREEMPT 1:OFF 2:OFF 3:OFF 4:OFF 5:OFF 6:OFF 7:OFF 8:OFF > PATH WIDE2-2 > SWDCD ON > SYMBOL /# > USEALIAS 1:ON 2:OFF 3:OFF 4:OFF 5:OFF 6:OFF 7:OFF 8:OFF So the T2 is acting as a WIDE1-1 fill-in digi, isn't beaconing itself, and that UI-View is running as an IGate. Again, I would ask if you see the corrupted data right in the terminal window. You could even take UI-View right out of the loop and just run it with a plain jane terminal program connected to the T2 to see you can see any corrupted callsigns or other data. How much RF is floating around near the T2? Any chance it's getting swamped with RF? All the antennas have a good SWR and are physically away from the T2 some distance? Looking at aprs.fi, I see 0WJY-9 near you and gated by N9JY-1. I presume this is one of the garbled callsigns. Also RLOV, 44OOV and K40S4M. 0WJY-9 is useful because you hear it direct. The others that I looked at had gone through a digi before they got to you, so the corruption could have taken place elsewhere. You need to prove whether the errors are being caused by your equipment / software or if it's taking place before it gets to you. There's also the possibility of corruption taking place before the data is transmitted by the originating station, but it would be quite a coincidence to see multiple stations with the same problem all in the same geographic area. 73 es cul - Keith VE7GDH -- "I may be lost, but I know exactly where I am!"
