I just started it back up about an hour ago. I'll let it run overnight and dump it to see what we get. I actually found a corroded RF ground on the antenna mast and replaced it before the restart. I'm curious to see if that makes any difference. At any rate I'll see if I can work out a way to record some of the traffic too.
Larry On 10/25/09 5:59 PM, "Scott Miller" <[email protected]> wrote: > Larry, > > It'd be very useful to have some recordings of the traffic you hear > that's getting garbled. Also, the output of the INFO command would be > helpful - in particular, if the stack overflow flag is set. > > Scott > > Larry Ewan wrote: >> >> >> Keith, >> 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 UIview-32. I see the position issues on >> UIview and APRS.FI but only the funny call signs on APRS.FI. >> >> 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 UIview logs. Also have seen some sporatic fairly >> long delays in digipeating (a minute or two), which I think might be an >> OS/Uiview issue. >> >> Here's a config dump from the OT2m: >> display >> 1WIREWX OFF >> ABAUD 4800 >> ALIAS 1:WIDE1 2:WIDE2 3:TEMP >> ALTITUDE OFF >> ALTPATH OFF >> AMODE AUTO >> AUTHLIST >> AUTOBAUD OFF >> AUTOSAVE OFF >> BBAUD 4800 >> BMODE FLOW >> CDINVERT OFF >> CLIMB OFF >> CNTRESET OFF >> COMMENT - PSJ Fill-in >> COMPRESS OFF >> COUNTER OFF >> CUSTSYM OFF >> DAO OFF >> DIGI ON >> DIGIID 1:ON 2:ON 3:ON 4:ON 5:ON 6:ON 7:ON 8:ON >> DUPETIME 10 >> DOUBLE OFF >> EXTSQL OFF >> EXTTEMP OFF >> FAHRENHT OFF >> FILTER OFF >> GPSDATA OFF >> HALFSLOT OFF >> HBAUD 1200 >> HEADERLN OFF >> HOPLIMIT 1:1 2:1 3:5 4:0 5:0 6:0 7:0 8:0 >> INTERVAL 0 >> LVINHIBIT 0 >> MAXRANGE 0 >> MONITOR ON >> MYCALL N9JY-1 >> NICE 0 >> OUTPUT1 OFF >> PASSALL OFF >> POSITION 2829.07N 08048.17W >> POWER ON >> PREEMPT 1:OFF 2:OFF 3:OFF 4:OFF 5:OFF 6:OFF 7:OFF 8:OFF >> PTTINPUT OFF >> PATH WIDE2-2 >> PROPWPT OFF >> PWAUTH OFF >> QUIET 16 >> REARM 250 >> RETRIES 6 >> RETRYTIME 7 >> REQALL OFF >> RING OFF >> SCRIPT OFF >> SECRET 0 >> SHAREDPTT OFF >> SLOT 0 >> SMARTBCON OFF >> SWDCD ON >> STATUS 0 >> SYMBOL /# >> TELEMETRY 0 >> TEMP OFF >> TEMPADJ 0 >> TIMEHMS OFF >> TIMESLOT OFF >> TIMESTAMP OFF >> TRACE OFF >> TXDELAY 25 >> TXLEVEL 199 >> TXNOFIX ON >> TXONCHG OFF >> USEALIAS 1:ON 2:OFF 3:OFF 4:OFF 5:OFF 6:OFF 7:OFF 8:OFF >> VELOCITY OFF >> VOLTAGE OFF >> WAYPOINTS OFF >> WPTLEN 9 >> >> See anything I missed? >> >> Larry N9JY >> >> On 10/25/09 8:48 AM, "Keith VE7GDH" <[email protected] >> <mailto:ve7gdh%40yahoo.com>> wrote: >> >>> Larry N9JY wrote... >>> >>>> I'm getting a lot (maybe as many as 10%) garbled call sign decodes >>>> using three different radios on my OT2m... >>> >>> Garbled? Do you by any chance have PASSALL turned on? What are >>> you using to view the garbled decodes? Perhaps you could post a few >>> examples. Have you tried upgrading to the latest firmware? >>> >>> 73 es cul - Keith VE7GDH >>> -- >>> "I may be lost, but I know exactly where I am!" >> >> > > > > ------------------------------------ > > Yahoo! Groups Links > > >
