开云体育

The UI-View Group is very active. Most already do so,
but here are some some guidelines to follow.

1. Civility... this is practiced well by our members!

2. Sign your messages with your name and callsign.

3. Only post messages and responses that are relevant to UI-View.

4. Use plain text for messages sent to the UI-View support list.
When you address some 5000 recipients, you cannot know what their
email readers do with HTML formatted messages. Some will experience
unreadability.

5. IMPORTANT: When replying to a posting (message), kindly delete
all unnecessary text including the trailing text. Only leave the
poster's name, callsign and the time stamp, and the text from
the prior message about which you are commenting, and then trim
the rest. When viewing messages in the Yahoo web based interface,
the command [Up Thread] at the top of the message can be used, and
many email clients can group messages by thread also. Some members
have slow connections or pay for bandwidth. Brevity can often
also improve the clarity of your message. Do not top post... i.e.
do not type your reply above the quoted text.

6. When replying to a post, please decide if your comment should
go to the entire group of about 5000 or directly to the author.
Please think before replying to the group... replies like "I sure
do agree with that" do not add much to the group. Send thoughts
like those directly to the poster please.

7. Postings of sale or swapping of items are not wanted.

8. New members are all moderated for a number of postings. If the
messages follow the guidelines, they are approved and the member
is changed to un-moderated status.

This is a partially moderated list, i.e., only the user's first
messages are moderated, but all messages are monitored after posting.
If an un-moderated posting is found by the moderators to have a
problem, then the poster is changed to moderated status and in
most cases also contacted directly to resolve whatever has caused
the problem.

Actions are taken against those that chronically violate the rules.
The reason for this form of moderation is to block spammers from the
list and it is working well.

9. Do not add disclaimers to your posts that (1) restrict the ability
of other members to use the information you post, (2) claim a copyright
to your post, or (3) to claim any type of "rights" as a consequence of
another member replying to your post either directly to you or to the group.

10. Do not use anti-spam tools like challenge/response; the moderators
will not respond, and since messages to you then will bounce, you most
probably will be removed as a user of the group.

This message is sent to all new members, and to all members
every now and then. It has been revised as bounce reports have
changed a bit.

Any of us could experience no longer receiving email from the
UI-View support list. You might want to print this message and
review it if you stop receiving messages from the UI-View list.

If you stop receiving messages from the UI-View list, suspect
that either...

1) this or some other Yahoo group that you are a member of is
sending email which some spamblocker system regard as spam or
junk mail (quite a lot of these reports since summer 2009).

2) it may be that your email account has filled up with unread
messages or that the account on your mail server has ran out of
storage space. Read or delete the old messages on your mail server.

3) Some MSN or Hotmail accounts, and others such as arrl.net,
qsl.net which are used as a forwarding address from time to time
cannot forward to your primary address. When this hapens, the
Yahoo group receives an error message with something like
"impossible to relay to xxx" and you are then in the "bounced"
list. There are increasing numbers of bounces from some service
providers about messages which are blocked by them for policy
reasons.

4) You or your email provider have set up a challenge-and-response
system for those sending e-mail to you. The moderators will not
send replies to such challenges. You should select another
address for your list membership(s).

Sorry, but we cannot investigate every one of these blockings.
Please be aware that if you haven't received list messages
for some days, and reactivation requests are not reaching
you, or not answered by you, your account at the UI-View
list may be deleted. It may deleted if several bounces occur
in less than a week or two. It will also be deleted if the
bounce report says that your address is invalid, discontinued,
or unknown. Be aware that the bounce can relate to messages
from other lists than the UI-View list if you are a member
of other Yahoo groups.

If your membership is deleted, you will not be able to log
into the Yahoo group. If you try and send email to the group,
it will be rejected. However, you can subscribe again with a
valid and working email account by sending an empty email to
ui-view-subscribe@....

If you are away for some time, you might want to set your
account to temporarily receive only special messages or
even no email at all, but we recommend that still receive
special messages. You can log into the Yahoo group when you
return and change it back to daily digest or normal email.

Note: A member may send reactivation requests to himself/herself
from the Email Preferences section of My Groups.

73 and good luck - your UI-View group moderators

Stephen,
I do not have 60M but you should be in range of my 30M station most of the way. I have improved my reception by eliminating some sources of noise. The 30M band has really been strange the last couple of days. My station was copied about 100 miles from my QTH yesterday at 9 PM.
Have a good and safe trip.


Wayne
WA5LUY


---In ui-view@..., <wa8lmf@...> wrote :

I will be departing from central Michigan to the New Orleans area on 5 Feb
2019. Once again, I will be experimenting with 60-meters APRS enroute.

The outbound trip will be Feb 5th through the 7th. The return trip will be Feb
10th through the 12th. The 8fh and 9th will be in Versailles, Louisiana (far
northeastern corner of New Orleans) attempting to photograph the annual Tet
Festival with my new Autel EVO camera drone. (Tet is the Vietnamese version of
the Chinese New Years - there is a sizable Vietnamese community in New Orleans.)

The return trip will take a different itinerary. I intend to stop at MFJ in
Starkville, MS, on the way to metro Chicago. I will pick up my sister at
O'Hare, who will be returning from 6 weeks in Argentina the same day. Then we
will drive back to central Michigan.

- At home, I have TWO Yaesu FT-891 transceivers connected to two copies of
UIview monitoring, mapping, and igating 60 meters and 30 meters simultaneously.
[As I have mentioned previously, these inexpensive HF rigs are ideally suited
for HF APRS operation. The FT-891's continuously-variable DSP IF system can be
screwed down to the ideal bandwidth for both APRS modes simultaneously - about
800 Hz.]

On the outbound trip, I will beacon on 60 meters until Internet mapping shows I
am no longer being heard on 60 meters, and will then switch to the usual 30
meters APRS channel while in New Orleans. On the return trip, I will start
beaconing on 60 M again, as soon as I depart the New Orleans area, so there may
be nothing heard for the first day of the return trip.

Last summer's test from Michigan to Colorado along I-80 showed very consistent
results out to about 500 miles/800 km (Des Moines, Iowa area) going west. I
have no sense how the north-south 60M propagation to "NoLA" (the locals'
abbreviation for New Orleans, Louisiana) will compare with the east-west path
last year.

A dedicated 60 Meter APRS UI-webserver/igate is now operating at
< > .

The details are the same as last year:

- US 60-meters "Chanel 5" 5.403.5 MHz USB

- Standard tones of 1600/1800 Hz for AX.25 and 2100 for MFSK16


______________________________________________________

Stephen H. Smith wa8lmf (at) aol.com
Skype: WA8LMF
EchoLink: Node # 14400 [Think bottom of the 2-meter band]
Home Page:

Live Off-The-Air APRS Activity Maps
< >

Long-Range APRS on 30 Meters HF
< >

I will be departing from central Michigan to the New Orleans area on 5 Feb
2019.?? Once again, I will be experimenting with 60-meters APRS enroute.

The outbound trip will be Feb 5th through the 7th.? The return trip will be Feb
10th through the 12th.? The 8fh and 9th will be in Versailles, Louisiana (far
northeastern corner of New Orleans) attempting to photograph the annual Tet
Festival with my new Autel EVO camera drone.? (Tet is the Vietnamese version of
the Chinese New Years - there is a sizable Vietnamese community in New Orleans.)

The return trip will take a different itinerary. I intend to stop at MFJ in
Starkville, MS, on the way to metro Chicago. I will? pick up my sister at
O'Hare, who will be returning from 6 weeks in Argentina the same day. Then we
will drive back to central Michigan.

-?? At home, I have TWO Yaesu FT-891 transceivers connected to two copies of
UIview monitoring, mapping, and igating 60 meters and 30 meters simultaneously.
[As I have mentioned previously, these inexpensive HF rigs are ideally suited
for HF APRS operation.? The FT-891's continuously-variable DSP IF system can be
screwed down to the ideal bandwidth for both APRS modes simultaneously - about
800 Hz.]

On the outbound trip, I will beacon on 60 meters until Internet mapping shows I
am no longer being heard on 60 meters, and will then switch to the usual 30
meters APRS channel while in New Orleans.?? On the return trip, I will start
beaconing on 60 M again, as soon as I depart the New Orleans area, so there may
be nothing heard for the first day of the return trip.

Last summer's test from Michigan to Colorado along I-80 showed very consistent
results out to about 500 miles/800 km (Des Moines, Iowa area) going west.?? I
have no sense how the north-south 60M propagation to "NoLA" (the locals'
abbreviation for New Orleans, Louisiana)? will compare with the east-west path
last year.

A dedicated 60 Meter APRS UI-webserver/igate is now operating at
<> .

The details are the same as last year:

-? US 60-meters "Chanel 5"?? 5.403.5 MHz USB

-? Standard tones of 1600/1800 Hz for AX.25 and 2100 for MFSK16


______________________________________________________

Stephen H. Smith??? wa8lmf (at) aol.com
Skype:??????? WA8LMF
EchoLink:? Node #? 14400? [Think bottom of the 2-meter band]
Home Page:?????????

Live Off-The-Air APRS Activity Maps
?? <>

Long-Range APRS on 30 Meters HF
?? <>



[Non-text portions of this message have been removed]

I have noticed that the METAR stations I used to see on the firenet server are now gone. Also have not seen much of any weather related warnings.
Has there been a change that has stopped this information?


73
Mike - N7ZEF

Over the holidays, I completely re-did my UIview APRS webserver setup.?? It's
now ready to be hammered by a bunch of users to see how the new setup handles
the load.

I have replaced the 2012-vintage Acer AO756? "netbook" mini-laptop that has
been doing APRS Webserver duty for over 6 years,

.???? [Reviewed here? <> ]

with a later generation E3-111 netbook. ?? I maxed-out the new one with 8GB ram
and replaced the 500 GB mechanical HDD with a Samsung 1TB SSD.? The thing now
boots in about 15 seconds instead of two minutes.?? (You don't get the full
benefit of the blazing speed of the SSD since the motherboard and drive
controller interface of the Celeron-based netbook are relatively low
performance.? But is still far faster than the rotating hard disk.)

The SSD has another benefit:? Since this machine runs server duty 24/7/365, I
like to get the power consumption as low as possibile.? Running the mechanical
hard disk, the machine consumed 10 watts. With the SSD, the power drain dropped
to 8 watts.

A Rosewill 10-port powered USB hub is now connecting THREE of the Behringer
external soundcards,

.???? [Reviewed here:? <> ]

two USB<-->serial dongles (for the Echolink interface and for CAT of the FT-100
used for the IARU beacon monitor), and the USB-interfaced X10 controller. It's
now running THREE VMware virtual machines + 4 apps on the host. Between the
Win7-64 host and the 3 Win2003 VMs, it is now running EIGHT copies of UIview
simultaneously with only about a 35% CPU load.

The host runs the 30M HF UIwebserver, APRS Messenger, the BeaconSee IARU beacon
monitor, and Echolink + the three VMs. VM#1 runs 4 copies of UIview? on 2
meters - they show off-air activity for all of lower Michigan, the greater
Lansing area, the metro Detroit area, and the Michigan State Univ? campus.?
VM#2 runs the ISS SatGate.? VM#3 runs the "Special Events Server" which is
currently setup for the Livonia (greater Detroit area) hamfest coming on 17
Feb.? (The special events server uses two instances of UIview to produce a
regional area view and a close-up aerial photo view of the venue.)

It's all at <> as before.

On this gateway page, there is a link to yet another UI-Webserver for 60
meters.? On 5 Feb, I will be going on a road trip to New Orleans and will be
testing 60-meters APRS again.

-------------------------------------------------------------------------------
Stephen H. Smith??? wa8lmf (at) aol.com
Skype:??????? WA8LMF
EchoLink:? Node #? 14400? [Think bottom of the 2-meter band]
Home Page:?????????

Live Off-The-Air APRS Activity Maps
?? <>

Long-Range APRS on 30 Meters HF
?? <>

Thanks Keith for the instructions. They will be a big help in trying to get connected. I know the Yaesu won't transmit with ui view so maybe I should be trying this with my Kenwood 710.?
I'll try to set it up tomorrow and let you know how I do.
73,? Terry.? W8NJR



Sent from my Verizon, Samsung Galaxy smartphone

Terry W8NJR wrote…

I am using UI-View with a Yaesu FTM-400. How do I connect to APRS-IS?

Is your question about how to connect your FTM-400 (receive only) to UI-View, or how to connect UI-View to the APRS-IS?

To connect the FTM-400 to UI-View, go into menu and tap on DATA. In the Com Port settings, set the speed to match what UI-View is set for (e.g. 4800 bps or 9600 bps) and set the output to PACKET. In DATA BAND SELECT set it to B-Band Fixed for both APRS & DATA. I’m assuming you would want to reserve the A band for C4FM. In DATA SPEED set both for 1200 bps… unless you are actually using 9600 bps on the air. It will be RX only.

To connect UI-View, in the APRS Server Setup, just connect to e.g. noam.aprs2.net on port 14580. Enter your APRS validated number. Enter any desired filter in the EXTRA Logon Text. You can open the gateway, gate objects, & insert station call sign.

It’s pointless enabling anything in “Gate Internet to RF” as the TNC in the “400” will be RX only for UI-View.

Basically, you will be able to gate whatever you hear to whatever server you connect to, but you won’t be able to transmit anything to RF from UI-View. The FTM-400 itself can continue to beacon to RF if you wish.

--
73 Keith VE7GDH
“I may be lost, but I know exactly where I am!”

I am using UI-View with a Yaesu FTM-400. How do I connect to APRS-IS?


Terry, W8NJR

It's probably a filter set from the APRS Server Setup Screen. You get there from the Setup pull down menu. The field that holds the filter value is call Extra log-on text.


Tom -W1TG

For some reason I am not receiving any of the CWOP weather stations. I think I set a filter quite some time back but can’t find it, does anyone have any idea why I can’t receive them? I am on RF and internet.

Thanks for your advice,

Jim, N8JE

The UI-View Group is very active. Most already do so,
but here are some some guidelines to follow.

1. Civility... this is practiced well by our members!

2. Sign your messages with your name and callsign.

3. Only post messages and responses that are relevant to UI-View.

4. Use plain text for messages sent to the UI-View support list.
When you address some 5000 recipients, you cannot know what their
email readers do with HTML formatted messages. Some will experience
unreadability.

5. IMPORTANT: When replying to a posting (message), kindly delete
all unnecessary text including the trailing text. Only leave the
poster's name, callsign and the time stamp, and the text from
the prior message about which you are commenting, and then trim
the rest. When viewing messages in the Yahoo web based interface,
the command [Up Thread] at the top of the message can be used, and
many email clients can group messages by thread also. Some members
have slow connections or pay for bandwidth. Brevity can often
also improve the clarity of your message. Do not top post... i.e.
do not type your reply above the quoted text.

6. When replying to a post, please decide if your comment should
go to the entire group of about 5000 or directly to the author.
Please think before replying to the group... replies like "I sure
do agree with that" do not add much to the group. Send thoughts
like those directly to the poster please.

7. Postings of sale or swapping of items are not wanted.

8. New members are all moderated for a number of postings. If the
messages follow the guidelines, they are approved and the member
is changed to un-moderated status.

This is a partially moderated list, i.e., only the user's first
messages are moderated, but all messages are monitored after posting.
If an un-moderated posting is found by the moderators to have a
problem, then the poster is changed to moderated status and in
most cases also contacted directly to resolve whatever has caused
the problem.

Actions are taken against those that chronically violate the rules.
The reason for this form of moderation is to block spammers from the
list and it is working well.

9. Do not add disclaimers to your posts that (1) restrict the ability
of other members to use the information you post, (2) claim a copyright
to your post, or (3) to claim any type of "rights" as a consequence of
another member replying to your post either directly to you or to the group.

10. Do not use anti-spam tools like challenge/response; the moderators
will not respond, and since messages to you then will bounce, you most
probably will be removed as a user of the group.

This message is sent to all new members, and to all members
every now and then. It has been revised as bounce reports have
changed a bit.

Any of us could experience no longer receiving email from the
UI-View support list. You might want to print this message and
review it if you stop receiving messages from the UI-View list.

If you stop receiving messages from the UI-View list, suspect
that either...

1) this or some other Yahoo group that you are a member of is
sending email which some spamblocker system regard as spam or
junk mail (quite a lot of these reports since summer 2009).

2) it may be that your email account has filled up with unread
messages or that the account on your mail server has ran out of
storage space. Read or delete the old messages on your mail server.

3) Some MSN or Hotmail accounts, and others such as arrl.net,
qsl.net which are used as a forwarding address from time to time
cannot forward to your primary address. When this hapens, the
Yahoo group receives an error message with something like
"impossible to relay to xxx" and you are then in the "bounced"
list. There are increasing numbers of bounces from some service
providers about messages which are blocked by them for policy
reasons.

4) You or your email provider have set up a challenge-and-response
system for those sending e-mail to you. The moderators will not
send replies to such challenges. You should select another
address for your list membership(s).

Sorry, but we cannot investigate every one of these blockings.
Please be aware that if you haven't received list messages
for some days, and reactivation requests are not reaching
you, or not answered by you, your account at the UI-View
list may be deleted. It may deleted if several bounces occur
in less than a week or two. It will also be deleted if the
bounce report says that your address is invalid, discontinued,
or unknown. Be aware that the bounce can relate to messages
from other lists than the UI-View list if you are a member
of other Yahoo groups.

If your membership is deleted, you will not be able to log
into the Yahoo group. If you try and send email to the group,
it will be rejected. However, you can subscribe again with a
valid and working email account by sending an empty email to
ui-view-subscribe@....

If you are away for some time, you might want to set your
account to temporarily receive only special messages or
even no email at all, but we recommend that still receive
special messages. You can log into the Yahoo group when you
return and change it back to daily digest or normal email.

Note: A member may send reactivation requests to himself/herself
from the Email Preferences section of My Groups.

73 and good luck - your UI-View group moderators

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

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.

--
73 Keith VE7GDH
"I may be lost, but I know exactly where I am!"

Keep in mind that very few stations will change their protopath when they see a new digipeater call sign as they travel. We mostly use the wideN-N path and depend on active stations within range to digipeat our signals.

Having your fill in station beacon every 10 minutes or even more often seems to me to be more of an ego issue. Some users are compelled to be seen, beaconing at absurdly shorty intervals and clogging the air with unneeded signals.

I have my fill in digi set to beacon once per hour with no repeating, once every three hours with wide1-1, and only once in eight hours with a wide2-2. And those settings have absolutely no effect on which passing travelers have their APRS beacons digipeated. That is governed by the travelers protopath.

Mike?? KB7WUK
NW Oregon

Thank you very much two questions:

Close UI-View and edit the uiview32.ini file in the UI-View installation folder with a text editor. Look for the [DIGI_OPTIONS] section. Change it as follows, assuming you are in Texas.

[DIGI_OPTIONS]

DIGI_ENABLED=TRUE

UI_ONLY=TRUE

ALIAS_SUBSTITUTION=TRUE

DUPE_SUPPESS_SECONDS=30

ALIAS=AE5IB,WIDE1-1

UIFLOOD=TX

UITRACE=WIDE

WIDEN-N=TRUE

TRACEN-N=FALSE

SUBST_ALIAS=VE7GDH

EXCLUDED=""

The UI-View system is AE5IB-13

So in the ALIAS is it AE5IB, or AE5IB-13?

Same question with the SUBST_ALIAS is it AE5IB, or AE5IB-13?

This part made lots of changes to my section.? I was a ways off.

About 20 miles away I will be at net control with another UI-VIEW set to AE5IB (AE5IB-0) listening with both RF and the server.

Go into the APRS SERVER SETUP. Select a suitable server... e.g. noam.aprs.net:14580. Make sure APRS SERVER LOG ON REQUIRED is enabled. Enter your APRS validation number. Enable aujto connect. Enter whatever filter you want if you want he server to send anything back to you... e..g filter m/250 if you wanted to get everything within 250 km of your location. Enable OPEN THE GATEWAY, GATE OBJECTS, INSERT STATION CALLSIGN, GATE LOCAL MESSAGES, and TRANSMIT IGATE STATUS. Set MAX SILENCE to 1 minute. It will gate everything that it hears, and it will gate messages to local stations... ones that it has heard.

Super. I had missed TRANSMIT IGATE STATUS

Every 30 minutes will lessen the load on the RF frequency, but setting at 10 minutes would increase the changes of stations coming into your area of knowing you were there. Do NOT use a path of WIDE1-1,WIDE2-1. Fixed stations should not use a path of WIDE1-1. Consider if you really need a two hop path. If you do, use WIDE2-2. You might find that a one hop WIDE2-1 is more than enough, but it really depends on the geography around you and how many digipeaters there are and how well they are placed. Of course, if there aren't any fill-in digis around you, using WIDE1-1 isn't really going to do any harm. However, if you were in a populated area with a number of fill-in digis around you, you could be triggering all of them and increasing the load on the local RF network. Consider a one hop path, but use a two hop if you must. Don't use WIDE1-1 if you are fixed station, or if you are flying.

You are right. I was thinking how I normally set my trackers. WIDE2-1 is sufficient. If I cannot hit a WIDE-2 repeater, my digi is pretty useless as a digi.

We have no fill in digis in this area which is why I am setting it up for the Dallas Marathon in one of the RF holes this weekend.? Dallas Metroplex is pretty well covered generally. I have two RF holes in the Marathon course that are low compared to the average in Dallas. And vehicles disappear when they are in that are in those areas.? I am getting fill-in digis in those two places.

The minutes do not bother me one way or another. I do not care if other people know where I am or not. It will be operating for less than 48 hours, and the vehicles in the Marathon do not care where the digi is, we only care they can be seen everywhere on the course.? I will compromise and go with 20 minutes.

Thank you very much.

Kip
AE5IB

Kip AE5IB wrote...

I want my UI-View to be a fill-in digi
so it should only digi a WIDE1-1

Close UI-View and edit the uiview32.ini file in the UI-View installation folder with a text editor. Look for the [DIGI_OPTIONS] section. Change it as follows, assuming you are in Texas.

[DIGI_OPTIONS]
DIGI_ENABLED=TRUE
UI_ONLY=TRUE
ALIAS_SUBSTITUTION=TRUE
DUPE_SUPPESS_SECONDS=30
ALIAS=AE5IB,WIDE1-1
UIFLOOD=TX
UITRACE=WIDE
WIDEN-N=TRUE
TRACEN-N=FALSE
SUBST_ALIAS=VE7GDH
EXCLUDED=""

The above will digipeat on your call sign and WIDE1-1. It will also respond to TXn-N for "state flooding". If you ever had a need to respond to WIDEn-N, you would just have to enable WIDEn-N (assuming you made the changes as above) and remove the WIDE1-1 alias. It also will do alias substitution.

I want it to i-gate everything it hears.

Go into the APRS SERVER SETUP. Select a suitable server... e.g. noam.aprs.net:14580. Make sure APRS SERVER LOG ON REQUIRED is enabled. Enter your APRS validation number. Enable aujto connect. Enter whatever filter you want if you want he server to send anything back to you... e..g filter m/250 if you wanted to get everything within 250 km of your location. Enable OPEN THE GATEWAY, GATE OBJECTS, INSERT STATION CALLSIGN, GATE LOCAL MESSAGES, and TRANSMIT IGATE STATUS. Set MAX SILENCE to 1 minute. It will gate everything that it hears, and it will gate messages to local stations... ones that it has heard.

When it transmits its position every 30
minutes, I want it to transmit WIDE1-1,WIDE2-1

Every 30 minutes will lessen the load on the RF frequency, but setting at 10 minutes would increase the changes of stations coming into your area of knowing you were there. Do NOT use a path of WIDE1-1,WIDE2-1. Fixed stations should not use a path of WIDE1-1. Consider if you really need a two hop path. If you do, use WIDE2-2. You might find that a one hop WIDE2-1 is more than enough, but it really depends on the geography around you and how many digipeaters there are and how well they are placed. Of course, if there aren't any fill-in digis around you, using WIDE1-1 isn't really going to do any harm. However, if you were in a populated area with a number of fill-in digis around you, you could be triggering all of them and increasing the load on the local RF network. Consider a one hop path, but use a two hop if you must. Don't use WIDE1-1 if you are fixed station, or if you are flying.

--
73 Keith VE7GDH
"I may be lost, but I know exactly where I am!"

Generally, a WIDE1-1 fill-in digi should not then need to send its own
packets out via WIDE1-1,WIDE2-1 because that implies that it cannot hit a
WIDEn-N on its own. And if it cannot do that, then it is pretty useless.
So it should send out via WIDE2-2. Somel reasons:

1) It causes all its packets to be 7 to 14 bytes shorter (and more
successful) because the complex path is reduced to just two fields.
2) It avoids keying up unnecessary surrounding WIDE1-1's which in my case
(my home) gives me an un-needed Blitz on the TV every time my home digi
keys up

Just some thoughts

On Sat, Dec 8, 2018 at 12:26 AM Kipton Moravec kip@... [ui-view] <
ui-view@...> wrote:

I am a little confused by the documentation.

Here is what I want:

I want my UI-View to be a fill-in digi so it should only digi a WIDE1-1

I want it to i-gate everything it hears.

When it transmits its position every 30 minutes, I want it to transmit
WIDE1-1,WIDE2-1

Can I set it up this way? How and which screens? If not how close can I
get?

Kip

AE5IB



------------------------------------
Posted by: Kipton Moravec <kip@...>
------------------------------------

Please do not top post, and trim quoted text as much as possible.

UI-View website:

UI-View Registration:
Select language & fill in your name and call sign. Return later to collect
your registration.

APRS Server List: To update the APRS Server List, change the download URL
to... aprs2.net/APRServe2.txt

For North American users, PMap 9 (Precision Mapping 9.0) along with
PMapServer 9 can provide street level mapping for all of North America.
They can be installed without hassle on Windows 7 & 8. PMapServer is
available for download on the UI-View website. However, Undertow Software
is no longer selling new copies of PMap 9, but existing owners can continue
to use it as long as they can get it registered.

Users of anything newer than Windows XP should not install UI-View below
Program Files. Instead, create a folder elsewhere. To view UI-View's
built-in context sensitive help file, download and install WinHlp32.exe.


Stephen WA8LMF has many useful hints and tips about setting up and using
UI-View on website:
------------------------------------

Yahoo Groups Links

I am a little confused by the documentation.

Here is what I want:

I want my UI-View to be a fill-in digi so it should only digi a WIDE1-1

I want it to i-gate everything it hears.

When it transmits its position every 30 minutes, I want it to transmit WIDE1-1,WIDE2-1

Can I set it up this way? How and which screens? If not how close can I get?

Kip

AE5IB