I went through the Tracker2 source code (assuming it is basically the
same as the GTRANS) and cannot readily detect any reason for
alpha-overlay characters to not make it out as a waypoint. The way it
is coded, anything but \ will be assumed to the be primary table (not
correct), so the symbol might be wrong, but it shouldn't interfere with
waypoint output. At least, not to my eyes.
As was asked before, are you sure it's close enough to not get caught in
a range-type of filter? (again, possibly exposing my ignorance of the
GTRANS cable)...
Wait, a light-bulb just went off....the GTRANS goes the OTHER way,
doesn't it? It accepts NMEA waypoints and translates them to Garmin for
the Nuvi. Have you tried hooking up a serial cable and terminal program
to make sure the NMEA waypoint is being emitted from whatever you have
feeding the GTRANS? That's where the filtering would be done, not in
the GTRANS. It's possible that THAT source has parsing problems with
alphabetic overlay characters and is then suppressing (what it deems to
be invalid) waypoint output.
Lynn (D) - KJ4ERJ
Lynn W. Deffenbaugh (Mr) wrote:
>
>
> Taking these one at a time...
>
> K7EK-7>T7PVVR,WIDE1-1*,WIDE2-2:'2=.l":k/]"4q}
> This one, I understand, shows up. It should. it's a MIC-E encoded
> position.
>
> K7EK-5>WL2KUS-5,VBALDI*,WIDE2-1:K7EK-5 RMS/TELPAC NODE - 144.35 mhz 9600
> baud.
> No coordinates in this one to pass on as a waypoint
>
> TACOMA>APU25N,VBALDI*,WIDE2-1:=4704.21NI12220.88W#- K7EK 144.35 9600
> BAUD APRS {UIV32N}
> Coordinates here, but a non-numeric overlay character of I (eye) symbol
> #. This may be the problem here.
>
> VBALDI>APU25N,WIDE2-1,14435:!4713.14NS12150.61W#PHG5830/N7FSP (VBALDI
> WIDE) 144.35mhz 9600 BAUD
> Ditto the non-numeric overlay character on this one.
>
> VBALDI>APU25N,WIDE2-1,14435:!4713.14NS12150.61W#PHG5830/N7FSP (VBALDI
> WIDE) 144.35mhz 9600 BAUD
> And a non-numeric overlay of S on this one. Same # symbol.
>
> TACOMA>APU25N,VBALDI*,WIDE2-1:>300701z= 144.35 MHZ 9600 BAUD IGATE =
> No coordinates on this one.
>
> TACOMA>APU25N,VBALDI*,WIDE2-1:<IGATE,MSG_CNT=0,LOC_CNT=5
> And no coordinates on this one.
>
> The only ones I'd expect to show up are the ones with the non-standard
> overlay character. I suspect this is an oversight in the T2 source code
> which I assume was adopted into the GTRANS. I'll see if I can dig it up
> and comment definitively on that.
>
> Lynn (D) - KJ4ERJ
>
> Of these, the only one that shows up in the Nuvi is K7EK-7.
>
> Tom Hayward wrote:
> >
> >
> > K7EK-7>T7PVVR,WIDE1-1*,WIDE2-2:'2=.l":k/]"4q}
> >
>
> > K7EK-5>WL2KUS-5,VBALDI*,WIDE2-1:K7EK-5 RMS/TELPAC NODE - 144.35 mhz
> > 9600 baud.
> > TACOMA>APU25N,VBALDI*,WIDE2-1:=4704.21NI12220.88W#- K7EK 144.35 9600
> > BAUD APRS {UIV32N}
> > VBALDI>APU25N,WIDE2-1,14435:!4713.14NS12150.61W#PHG5830/N7FSP (VBALDI
> > WIDE) 144.35mhz 9600 BAUD
> > VBALDI>APU25N,WIDE2-1,14435:!4713.14NS12150.61W#PHG5830/N7FSP (VBALDI
> > WIDE) 144.35mhz 9600 BAUD
> > TACOMA>APU25N,VBALDI*,WIDE2-1:>300701z= 144.35 MHZ 9600 BAUD IGATE =
> > TACOMA>APU25N,VBALDI*,WIDE2-1:<IGATE,MSG_CNT=0,LOC_CNT=5
> >
> > Of these, the only one that shows up in the Nuvi is K7EK-7.
> >
> > Tom KD7LXL
> >
> > On Mon, Jun 29, 2009 at 9:06 PM, Scott Miller<[email protected]
> <mailto:scott%40opentrac.org>
> > <mailto:scott%40opentrac.org>> wrote:
> > >
> > >
> > > It shouldn't be filtering anything. Can you send me some examples of
> > > the packets as they appear on the air? I'll see if I can duplicate the
> > > problem.
> > >
> > > Scott
> > >
> > > Tom Hayward wrote:
> > >>
> > >>
> > >>
> > >> I noticed today (well, a few days ago actually, but I've been
> > >> monitoring it more since...) that I'm not seeing tactical calls on my
> > >> Nuvi 350. It's connected to a D710 via GTRANS cable. The Nuvi's
> > >> Favorites list has a number of ham calls in it, but I tried to
> > >> navigate to another ham's home the other day and his station wasn't
> > >> listed in the Nuvi. The tactical call for his home WIDE1-1 digipeater
> > >> is USEA. I noticed I'm not seeing the digipeater VBALDI, or local
> > >> repeater objects on the Nuvi 350 either. These are all listed in the
> > >> D710, so I know they decoded and should have been sent to the GTRANS
> > >> cable. I have filtering disabled in the D710.
> > >>
> > >> So, what's going on? Is the GTRANS cable filtering these? The
> Nuvi 350
> > >> can't accept four- or six-letter waypoints? Does the D710 not output
> > >> waypoints if the position has not changed (should I clear the list on
> > >> the D710)?
> > >>
> > >> Thanks
> > >>
> > >> Tom KD7LXL
> > >>
> > >>
> > >
> > >
> >
> >
>
>
