On 08/13/2009 02:17 PM, Broncus wrote: > > In this particular case, where you know the call of the first digi you > > wanted to hit, and the path you know it needs to get out, couldn't you > > set a path (in the HT) of: > > > > N7FMH-9,WIDE1-1,WIDE2-1 > > > > Even better yet: > > > > N7FMH-9,PNRDVL,WIDE2-1 > > > > That may be a three hop path, but is unlikely to cause much in the way > > of noise to anyone based on it's path, I would think. > > > > - michael > > > I like the first option. I think it should work regardless of where > PNRDVL is (in range or not). So as I commute to work, I leave the PNRDVL > area and enter areas with WIDEn-N digipeaters, it should be heard. With > that setting, does N7FMH-9 have to always be in the loop? I am > understanding that it does. It is easy to add/delete in the D7 so it > doesn't matter too much.
Yes, it would always have to be in the loop, which would be useful in the context of the trip your making with the HT and the mobile. In general, the usual path you want when mobile is WIDE1-1,WIDE2-1. _Maybe_ WIDE1-1,WIDE2-2 if you need to hit two wide area digis to get to an iGate. When you're at home and not moving, it may make sense to use N7FMH-9 as an additional hop to get out to a WIDE1 or WIDE2. In this case using the explicit call makes sense and doesn't generate a whole bunch of QRM. However, WIDE1-2 doesn't make a whole lot of sense. Any WIDE1 digi you hit should be able to get you to a WIDE2 digi on the next hop, otherwise it's not really much of a fill-in digi. If you were to use WIDE1-2, you end up either spamming other fill-in digis, or end up with a three hop path you don't need, or have some similar effect generating QRM. - michael > > Thanks! > > Best regards, > Fred > >
