Hi Tom, > > After reading the WIKI, I have determined that I need to enter these > > commands: > > 1. alias 1 wide <-- makes it a WIDE1 fill-in > > 2. digi on <-- enables the digipeater function > > > > Leave this alone: > > 1. hoplimit <-- maintains n = N (WIDE1-1) > > > > Have I missed anything?
> A few misconceptions here... > "digi on" turns on digipeating on your callsign only. For alias digipeating, the command is "usealias 1 on". I will this off then. I don't need to digi my own. At least I don't see a reason. > I would expect hoplimit n to limit on n and N for WIDEn-N, but it seems to only limit on N. This means that with "alias 1 WIDE" and "hoplimit 1 1", you will be digipeating WIDE3-1, WIDE2-1, and WIDE1-1. To solve this, use "alias 1 WIDE1" and "hoplimit 1 1". Now you will only digipeat WIDE1-1 (for alias 1). I did miss: alias 1 wide1 So I know that hoplimit is set: hoplimit 1 1 Additional settings: usealias 1 <-- forgot to turn it on! dupetime 30 <-- no ping pong effects wanted > > Now for an operational question, does the 'high' digi give the station hops > > based on the WIDE2-1 at that point? > If the HT is using WIDE1-1,WIDE2-1, and the mobile digipeats the > WIDE1-1, yes, the high level digipeater will digipeat the WIDE2-1 hop. I thought that was the case. Thanks for verifying! As a recap, these are the changes I will make then to add a fill-in dig to the tracker: alias 1 wide1 hoplimit 1 1 usealias 1 <-- forgot to turn it on! dupetime 30 <-- no ping pong effects wanted digiid 1 on The last command is DIGIID. Since the tracker is set to beacon based on movement only (SB) I imagine the ID should be inserted. > Tom KD7LXL Thanks! Best regards, Fred
