Nope, that's not what I'm saying.... Earlier today I was out of digi range for the HT but in range for the mobile T2. I planned that to see if the T2 was, in fact, digipeating the signal from the HT. It was and the HT (with a different SSID) appeared on the Nuvi as a waypoint as expected aftert being digipeated by my mobile T2. However, the T2, while transmitting my mobile's ID did not appear on the Nuvi as a waypoint. At least it did not an unknown percentage of the time but did on occasion. The T2 Smart Beaconed appropriately some of the time as well but not always. It appears as though the communication between the Nuvi and the T2 is intermittent.
That's still may not be clear. And all of that said I was messing with the Nuvi while in the garage earlier and accidentally hit a button which asked if I wanted to reset the factory settings. Without too much thinking I did with the fleeting thought that was the problem. I can't say it was the answer but immediately after I reset the Nuvi I drove and the Nuvi / T2-135 worked flawlessly Smart beaconing away my position. Perhaps I had enabled some function in the Nuvi the APRS stuff didn't like. I can't explain it but seems now to be working! One more question - I have a vague recollection of a 'proper' order for powering onthe Nuvi / T2. Does it matter which is powered on first? Pete KC0GPB On Mon, Apr 19, 2010 at 1:51 PM, gsdatplace <[email protected]> wrote: > > > From what you posted, what your saying is that when your not in range of a > Digi, that your position isn't showing up on the nuvi, but when you are in > range of a digi you're showing up on the nuvi fine? is that correct? > If thats what your saying then thats the normal and proper operation of a > nuvi attached to a OT2. > When the T2 decodes a packet, it sends that packet as a waypoint to the > nuvi to be displayed, its not actually updating "your" position on the nuvi, > its only displaying packets it recieves on the nuvi. So unless your packet > gets digi'd back and the OT2 decodes it you won't show up on the nuvi. > I thought initially like you that it was placing my waypoint on the nuvi as > it beaconed seperately, so when I wasn't showing up I thought it was a issue > with my setup, turns out it was a issue with a extra digi someone setup that > was clobbering packets. Turned into a feature I like now, if I don't show up > than I know I'm not getting digi'd. > > Garrett > VE6RKY > > > --- In [email protected] <tracker2%40yahoogroups.com>, Pete Lilja > <pli...@...> wrote: > > > > Recently I'd noticed a deterioration in my APRS 'trail' (or the ability > to > > be digipeated or I'gated) while using my T2-135 and a Garmin Nuvi 350. I > > thought I had a problem with my deviation setting so played with and > > adjusted that (by ear) and that didn't seem to help. I tried a new > antenna > > and that didn't help either with my problem either (although I found out > the > > new one has an SWR of 1.6:1 at 144.39 and the old one that I had damaged > was > > nearly 4:1 at 144.39). I've talked to my friend that operates the I'gate > > nearby and he said things seem to be running OK on his end. That left me > > with few other options... > > > > Until I had an idea. I drove out to a park where I cannot hit a digi with > > my Kenwood D7 HT on EL power. Connected to my D7 is a GPSr that works > just > > fine as a position reporter over the APRS network. I confirmed that I > > couldn't hit a digi in my location this morning and then turned on the > > DR-135 with the T2-135 acting as a digi. It worked just fine. However, my > > mobile DR-135 was not showing my position on the Nuvi. I cycled the power > > and got back the mobile position just briefly. It appears that the Nuvi > is > > not always communicating properly with the T2-135. The T2 is working fine > > and even seems to smart beacon while turning (sometimes, but not always) > as > > I can see my call and the message that goes out with the mobile rig on my > D7 > > - it just wasn't displaying the position on the Nuvi. > > > > The Nuvi to T2-135 appears to be intact and connected properly. This > > problem is intermittent. I'd say a forced beacon through the Nuvi works > > about 20% of the time. > > > > I hope I've described the problem adequately. It appears the T2 is > working > > as designed and set-up. I think I'm having an issue with the Nuvi and / > or > > the communication between the Nuvi and the T2. > > > > Any ideas / help? > > > > Pete > > KC0GPB-7 mobile > > KC0GPB-5 with the Kenwood d7 HT > > > > >
