Thank you for the excellent explanation.
My sole concern with digipeating other packets is running down the car battery in a remote area. ?Especially since most of these summits are up very high and I would be running the transmit at full power in many places, so I would expect it to hear a lot
of traffic and function as a high level digipeater. I figured I¡¯d be safe with only a few transmissions from us but couldn¡¯t control anything else.
Maybe I should look at using a secondary battery for the transceiver instead of running it off the main one, and/or using solar power, as your explanation makes a lot of sense.
Rick
toggle quoted message
Show quoted text
On Apr 5, 2021, at 6:59 AM, Rob Giuliano via groups.io <kb8rco@...> wrote:
?
I don't remember seeing a response to this, so I will respond.
In general, it is polite to setup a DIGI for all to use - especially in remote areas.
If you set it up to be private, you are kinf of being a 'stingy HAM'.
The whole concept of fill-in DIGIs is that they may be temporary (moving through).
However, I believe you can set the TT4 to DIGIMY TRUE and your group MUST change their first path element to match.
Example (TT4 mycall N0NE-9)
?? PATH1 N0NE-9
?? PATH2 WIDE2-2
The catches:
?? * to this is that if the element is not used (your vehicle never hears and DIGIs the packet) that element
????? would not be used up and your packet 'may not' be DIGIed at all.? Other DIGIs that hear it would have
????? to have PREEMPT TRUE (or thier version) in order to handle the packet.
?? * You would need to change your path elements back to the default when not using the HT in this manner.
???? This would be most important for the other group members as they are NOW kind of relying on your station.
If you set ALIAS1 WIDE1, and change to
PATH1 WIDE1-1, PATH2 WIDE2-2 you get the following advantages:
?? * Your path is consistent with almost all APRS networks
????? So you never never have to change your path.
?? * It will be unlikely your other group members will need to do anything
?? * Not only do you handle your packets in earshot of the vehicle, you will also help your fellow HAMs in the area.
On Saturday, April 3, 2021, 8:43:35 PM EDT, Rick Dexter <rick@...> wrote:
Hi - new to the list and the TT4, and APRS in general.
A friend and I have been activating SOTA summits.? We are finding that APRS with our HT's is hit and miss.? Some summits have APRS coverage, some don't.? Even if we can hear a digi, it often can't hear our HT's, or can only hear them on high power and we'd
rather conserve batteries.? In general, we don't care that much about tracking/beaconing, but we want to be able to send out SOTA spots and get spots using the APRS SOTA gateway (address a text to SOTA and receive texts from the SOTA gateway).
I thought it would be nice if I could configure my higher powered mobile to digipeat our HT's while we are at the summits, assuming the HT is within simplex reach.? Most of the configurations I've tried also make it digipeat other packets as well.? I don't
really want it to do that.
I did try a configuration using a special alias that will digipeat our HT's if we set the path to include that alias, but we cannot receive any packets back from the gateway (spot acknowledgements, for example).
Maybe I am barking up the wrong tree here, but is something like this possible?? In essence, I want the mobile digi (with the TT4) to repeat packets from our two callsigns going out to the SOTA callsign, and also repeat anything it receives from the SOTA callsign
(or anything destined to our two callsigns).? I want to be able to park the car in any remote or busy area and not worry about messing up the network.
Thanks,
Rick
W5RJD
