On 12/9/18 6:27 PM, Keith VE7GDH ve7gdh@... [ui-view] wrote:
Kip AE5IB wrote...
> The UI-View system is AE5IB-13
> So in the ALIAS is it AE5IB, or AE5IB-13?
If you are using AE5IB-13 in the station setup, I would use the same
SSID in the SUBST_ALIAS setting. Having your callsign in the alias list
will allow you can digipeat when someone uses your actual callsign in
the path. If you had an alias of AE5IB-13, you would digipeat a beacon
if the first un-used path was AE5IB-13. This might be useful sometimes
for selective digipeating. For most mobile stations, they would be
better off starting their path with WIDE1-1.
> Same question with the SUBST_ALIAS is it
> AE5IB, or AE5IB-13?
By entering your callsign in the Aliase(s) section, your station will
disigipeat on the station callsign. No one will be using a path of
AE5IB-13 unless they have specifically entered it. It won't hurt
anything if you enter it and no one uses it. However, adding WIDE1-1
will digipeat if the beacon heard has a path that starts off with an
un-used WIDE1-1, in other words you would be acting as a fill-in digi.
If Alias Substitution is checked, beacons digipeated by your station
will have the alias entered in SUBST_ALIAS embedded in the digipeated
beacon, making it traceable, showing that it was digipeated by you.
Out of the box, UI-View was set up for an untraceable WIDEn-N and a
traceable TRACEn-N. The changes I suggested for the the [DIGI_OPTIONS]
section set UI-View up so the user can enable or disable a traceable
WIDEn-N and help with state or province flooding... e.g. TXn-N for
Texas. The old TRACEn-N has been deprecated.
For someone wanting to do "state flooding", it would be good if they
used a path starting with WIDE1-1... e.g. WIDE1-1,WIDE7-7. This will
make the first hop traceable. It would be an 8 hop path. Someone would
only use it if they had something urgent that they needed to spread such
as an emergency bulletin. Of course, a path including TXn-N won't go
anywhere unless there are digipeaters in the area supporting it.
Thanks for the help from everyone.
I thought I would let people know what happened, as a follow up. This was for the Dallas Marathon, which was Sunday, December 9, 2018
We had a debate about i-gating. On one side we had the purists who thought everything should be RF only (because in a real emergency you might not have Internet). And others who thought use all the tools at your disposal, and if that included getting data from the Internet that was O.K.
I set up the fill-in digi/i-gate at a house in an area that was known to have problems last year on Saturday.? I found them by asking my facebook friends if anyone lived on that street. And a friend knew someone, and made the connection, and they said yes.? So I put a 1/4 wave VHF antenna on a 30' mast in their back yard with an old XP laptop running UI-View. Their WiFi router was on a desk on the other side of a window about 50 feet from my setup so we had a good connection for Internet.
I set it up to be a Wide1-1 repeater and i-gated everything it heard. All the trackers were set up as Wide1-1,Wide2-1 because Dallas normally has a lot of traffic and digipeaters.? We had another hole near White Rock Lake, and one of my friends who was manning a Water Stop there set up an i-gate and Wide1-1 digi there also.
Saturday night I looked at aprs-fi and discovered the i-gate had not seen anything. I called the people and they looked at it and everything seemed O.K.? So at 4:00 a.m. the next morning I drove 45 minutes down to see what was wrong. I had a tracker in my truck, and when I got there the gate to the back yard was locked. But I was able to see that aprs-fi showed my digi / i-gate had relayed my truck tracker, so it was working after all. It must not have seen anything in the previous 16 hours. I was able to get back to the NCS by 6:00 a.m. for setup.
We had some problems. 4 of the 8 SAG wagons did not have APRS, despite them telling us they had them, and not taking up the offer to loan them one the week before. The trackers with the police with the lead runner, and the tracker with the Turtle (or tail-end-Charlie) with the last runner, worked well. A number of other vehicles had them also.
We did have a problem with an intermittent dead carrier on the band, sometimes it would be on for about 5 minutes, then go quiet for a few minutes.? This caused problems for trackers that listened before they transmitted, so they would not transmit. The trackers that just transmitted in many cases were able to overcome the carrier, and the i-gates were able to route the signals to the Internet. So we could track them.
So we were glad we use the Internet. Next year we are thinking of using a different frequency for the APRS than 144.39. It means we have to put up maybe 4 digipeaters/i-gates but that is only two more than we had this year. I have already started searching for high locations with good course coverage, and checking permissions.
Kip
AE5IB
