I've seen this too when chasing a balloon.  I did discover in testing 
that creating a waypoint with the same name but a different symbol will 
cause it to be created with a " 1" suffix.  I assumed that somehow the 
received packet got corrupted or something and it changed the symbol.

I, too, chased the wrong one (on the side of a mountain in the Mojave 
desert, by moonlight) but it was not more than 1/4 mile from the right one.

Scott

Pete Lilja wrote:
>  
> 
> I, too, have had my Nuvi connected to an T2-135 display multiples of the 
> same call.  To be more specific this has happened 3 times all while 
> chasing a high altitude balloon with my call sign but a different SSID.  
> What I'd see on the Nuvi is KC0GPB-11 and KC0GPB-11 1 showing two 
> different locations (but close to eachother.  And, inviariably, I'd pick 
> the wrong one in recovering the balloon's payload.)  My SSID from the 
> chase car is -7, BTW.
>  
> Since this is the only time I've ever seen the two locations with the 
> one added to the SSID I'd assumed (probably incorrectly) that one packet 
> was digipeated and the other heard directly and the Nuvi wasn't sure 
> what to do with the info and added the 1 behind the SSID.
>  
> Pete
> KC0GPB
> 
> On Thu, Jul 29, 2010 at 10:40 AM, Bob Poortinga 
> <[email protected] <mailto:bobp%[email protected]>> wrote:
> 
>      
> 
>     Scott Miller <[email protected] <mailto:scott%40opentrac.org>> writes:
> 
>      > The T2 does indeed use a hash when creating D607 waypoints.
> 
>     Are you blank padding the name to 31 bytes when in FMI mode? I
>     actually got
>     my Nuvi 350 to display a duplicate waypoint by accident. I had set the
>     Waypoint Output to 8 characters by accident, used it like this for a day
>     or two, and then changed it to 9 characters when I reconfigured it
>     later.
>     I had two waypoints 'K9SQL-10' and 'K9SQL-10 1'.
> 
>     It seems to me that the Waypoint Output # of characters should only
>     apply to
>     NMEA output and FMI output should be blank padded to 31 bytes.
> 
>     Have you considered sending an A607 Delete Waypoint FMI command
>     *before*
>     sending a Create Waypoint FMI command?
> 
>     BTW, I'd still like to have a copy of the FMI Protocol version 1
>     specification.
>     Anybody got a copy?
> 
> 
>     -- 
>     Bob Poortinga K9SQL <http://www.linkedin.com/in/bobpoortinga
>     <http://www.linkedin.com/in/bobpoortinga>>
>     Bloomington, Indiana US
> 
> 
> 



------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/tracker2/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/tracker2/join
    (Yahoo! ID required)

<*> To change settings via email:
    [email protected] 
    [email protected]

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/

Reply via email to