Outdoor Adventure USA

No space works for me, (AGW Tracker)

cruiserlarry wrote: A: APRS, WIDE2,2, WIDE2,1
or
B: APRS,WIDE2,2,WIDE2,1

I'm sure this was just for illustration purposes, but I don't think you want to put two wides in the path like that (exception being Wide1-1 first).

Mine has separate entries for multiple path entries so I just set DIGI1=Wide1-1 and DIGI2=Wide2-2. Sorry I can't help you with your Kenwood.

sdnative wrote:

cruiserlarry wrote: A: APRS, WIDE2,2, WIDE2,1
or
B: APRS,WIDE2,2,WIDE2,1

I'm sure this was just for illustration purposes, but I don't think you want to put two wides in the path like that (exception being Wide1-1 first).

Mine has separate entries for multiple path entries so I just set DIGI1=Wide1-1 and DIGI2=Wide2-2. Sorry I can't help you with your Kenwood.

STOP STOP STOP. . . .

there should be dashes not commas. The Commas go between digipeater or station elements.

Wide1-1 like the formerly used relay if used should always be in the first link in the digipath. Wide1-1 is a low level digipeater and there are many in the Los Angeles Basin. If you use a wide1-1 after a high level Wide2-anything you will activate an absolute mess of low level digipeaters and create havoc with no real benefit.

If you think of it, you want to start small and increase from there. Simplex (APRS), Low Level (Wide1-1), High Level (Wide2-whatever) you could go to whatever number but there are some stations the filter anything over Wide3.

the Wide#-# is the number sou start with. smart Digipeaters will take the Wide#-# and subtract the second number then sent your packet to be digipeated to the digipeater in range. If you start Wide2-2 it will be digipeated with Wide2-1 then digipeated again as Wide2.

This is part of a scheme to eliminate duplicate packet trransmissions. wide1-1 is a dumb digipeater and Wide2-# is a smart digipeater that remembers packets that it has digipeated so that it will not digipeat a packet it has already digipeated. I am sorry this is so difficult to explain in a post.

There is a difference in uiview in that the path selection is nonstandard.

Uiview the path selection is APRS,WIDE2-2 no spaces if you are nor being reliably digipeated then you should use the low level dumb digipeaters APRS,WIDE1-1,WIDE2-2 again no spaces.

Most other trackers and aprs software will use APRS VIA WIDE2-2 or if a fill in is neeeded APRS VIA WIDE1-1,WIDE2-2

hmfigueroa wrote:there should be dashes not commas. The Commas go between digipeater or station elements.

Thank you again, Hector. It seems while reloading UIview32 for other reasons I must have put commas where dashes beong, and that is likely my problem with messaging and aprs.fi

hmfigueroa wrote:Wide1-1 like the formerly used relay if used should always be in the first link in the digipath. Wide1-1 is a low level digipeater and there are many in the Los Angeles Basin. If you use a wide1-1 after a high level Wide2-anything you will activate an absolute mess of low level digipeaters and create havoc with no real benefit.

If you think of it, you want to start small and increase from there. Simplex (APRS), Low Level (Wide1-1), High Level (Wide2-whatever) you could go to whatever number but there are some stations the filter anything over Wide3.

the Wide#-# is the number you start with. Smart Digipeaters will take the Wide#-# and subtract the second number then sent your packet to be digipeated to the digipeater in range. If you start Wide2-2 it will be digipeated with Wide2-1 then digipeated again as Wide2.

This is part of a scheme to eliminate duplicate packet transmissions.

There is a difference in UIview32 in that the path selection is nonstandard.

UiIview32 the path selection is APRS,WIDE2-2 no spaces. If you are not being reliably digipeated then you should use the low level dumb digipeaters APRS,WIDE1-1,WIDE2-2; again, no spaces.

This explanation is very helpful in making sense to me of the differences in the digipeater designations and path choices. While I'm still a bit confused, I feel better informed. I'd love to see a flow chart of the command hierarchy for digipeater paths - that I can follow...

cruiserlarry wrote:

hmfigueroa wrote:there should be dashes not commas. The Commas go between digipeater or station elements.

Thank you again, Hector. It seems while reloading UIview32 for other reasons I must have put commas where dashes beong, and that is likely my problem with messaging and aprs.fi

hmfigueroa wrote:Wide1-1 like the formerly used relay if used should always be in the first link in the digipath. Wide1-1 is a low level digipeater and there are many in the Los Angeles Basin. If you use a wide1-1 after a high level Wide2-anything you will activate an absolute mess of low level digipeaters and create havoc with no real benefit.

If you think of it, you want to start small and increase from there. Simplex (APRS), Low Level (Wide1-1), High Level (Wide2-whatever) you could go to whatever number but there are some stations the filter anything over Wide3.

the Wide#-# is the number you start with. Smart Digipeaters will take the Wide#-# and subtract the second number then sent your packet to be digipeated to the digipeater in range. If you start Wide2-2 it will be digipeated with Wide2-1 then digipeated again as Wide2.

This is part of a scheme to eliminate duplicate packet transmissions.

There is a difference in UIview32 in that the path selection is nonstandard.

UiIview32 the path selection is APRS,WIDE2-2 no spaces. If you are not being reliably digipeated then you should use the low level dumb digipeaters APRS,WIDE1-1,WIDE2-2; again, no spaces.

This explanation is very helpful in making sense to me of the differences in the digipeater designations and path choices. While I'm still a bit confused, I feel better informed. I'd love to see a flow chart of the command hierarchy for digipeater paths - that I can follow...

There is a pretty good animation on Steve's website. http://wa8lmf.net/DigiPaths/NNNN-Digi-Demo.htm that goes a long way toward explaining how it works. Although I really think you need to go through and read through his site, as it contains a lot of really good information I think it bears being placed here as well

THanks Hector. I'll have to go to his site and do my homework...

And, with Ollie's assistance, I got APRS working 100% now on UI-View 32 - messaging is working, and I'm being tracked on aprs.fi, too. I changed the unproto address from the one suggested by UI View 32' s suggestion (took out "APRS" from the beginning of the address), and, viola !!! - all is good again !!!