Scott KB8NUM wrote...
> When I send --version
> I get a message :Tracker2 Build 54680
That was the build I was using for probably some months, and was the
build I was using when I first got my Nuvi. Other than the "ack" problem
it should work OK, except some incoming messages will be garbled if the
sending callsign-ssid is over 8 characters in length.
> When I send -KB8NUM
> I don't see the radio or the tracker indicating a transmit.
Sorry - I should have said something like "-KB8NUM message" where
"message" is the message you are sending. Mine doesn't transmit either
if I don't actually enter a message after the callsign. It looks like
KB8NUM-8 is the T2 with a three hop path of WIDE1-1,WIDE2-2 and I see
that KB5NUM is running UI-View also with the same three hop path, and
that your OT+ is KB8NUM-9 with the recommended two hop path. Fixed
stations should not use WIDE1-1. On either of them, don't use a three
hop path unless you really need it. The recommended path for mobiles is
WIDE1-1,WIDE2-1. The recommended path for fixed stations is WIDE2-2
unless you can get by with a one hop WIDE2-1 instead. It really depends
on the digis around you. It appears that KB8NUM-8 is making it to IGates
direct without using any path... e.g. to KB2CEV, WC4J and to WX1H. It
also appears that KB8NUM-8 is beaconing very often too, probably
I see messages sent to KB8NUM-8, but none from it.
73 es cul - Keith VE7GDH
"I may be lost, but I know exactly where I am!"