> > "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.
The reasoning here is standards. All of the digipeaters I'm familiar with respond to their own call. For instance, I can use a path of BALDI to go specifically through the digipeater BALDI, instead of using WIDE2-1 which every digipeater in the area would respond to. digi on is useful if someone wants to send a packet with a specific path. If someone can hear your mobile, they may want to see if you are in range by changing their path to the callsign of your mobile. If they get digipeated, they know they are within simplex range of your mobile. In short, people expect a digipeater to respond to its own callsign, so it's good to leave this feature turned 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. For 144.39, DIGIID should always be on. This allows for traceability of the packet. If you are doing a special event, and using paths like SAR7-7, it may be useful to turn off DIGIID to keep the packets short (with DIGIID on, you'd get all seven digipeaters listed in the packet--that's a long packet!). Tom KD7LXL
