I'll admit to not having studied your whole post in detail, but the Nuvi only displays your station on the screen if it hears a waypoint from the T2-135. The T2-135 only generates such a waypoint for successfully decoded packets. This means that for your own station to show up on the screen, the T2-135 needs to have transmitted a packet that was decoded by a digi which decided to repeat the packet, then your T2-135 needs to hear and decode that digipeat which will then be formatted and sent to the Nuvi.
I've found that the complete circle actually rarely completes for my KJ4ERJ-9 T2-135/Nuvi combination. However, if I watch my track via an APRS-IS client, there's lots of packets there that didn't update on the Nuvi screen. This is WAD (Working As Designed) most likely. Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32 PS. Having APRSISCE running on my cellphone makes it really easy to see where my beacons were heard, but the digipeat didn't come back to update the Nuvi. It's LOTS of times! Pete Lilja 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 > > >
