| |
ZL3AI > APRDIG 03.02.03 14:28l 326 Lines 11030 Bytes #999 (0) @ WW
BID : 765-ZL3AI
Read: GUEST
Subj: TAPR Digest, Jan 22, 4/5
Path: DB0FHN<DB0RGB<DB0FSG<I4UKI<IW5CWB<IK5CKL<IK1ZNW<IR0NET<VK3TE<ZL2TZE<
ZL3VML
Sent: 030125/1018Z @:ZL3VML.#80.NZL.OC #:58084 [Chch-NZ] FBB7.00i $:765-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
Subject: [aprssig] UI-View32 question
>Does the program allow you to edit what port you can connect to?
>I know that the Win aprs Igate dosent and it would be nice to connect to the
>local port here instead of another state. But besides the port for the Win
>aprs fails in the connect attempt anyways. The old version of Win aprs you
>could edit the server list to choose your connection, can you do that with
>this program?
>
>Thanks
>Peter N0WRE
Yes...but so does WinAPRS.
UI-VIEW32 is a very stable program, great support, etc.
Jim, WA6OFT
----------------------------------------------------------------------
Subject: Re: new IGATE on the way!
From: "Rich Garcia" <k4gps@bellsouth.net>
Date: Wed, 22 Jan 2003 19:12:05 -0500
X-Message-Number: 31
That sounds like a way cool application for dense areas. But to take it one
further if it hears it on one but not the other then send it on the one that
missed it. We talk about smart digi's but this would be a smart gate!
No time to learn and far from up to speed to do any programing that is
useful. BUT there was a 3 part article that started this month in QST about
programing that has peaked my interest. Maybe in the future but I am sure
someone will have done it by the time I get to that level.
Rich
----------------------------------------------------------------------
Subject: Re: Findu and Icons
From: Steve Dimse <k4hg@tapr.org>
Date: Wed, 22 Jan 2003 19:42:19 -0500
X-Message-Number: 32
On 1/22/03 at 11:47 AM mwrobertson@attbi.com (Robbie) sent:
>I have been noticing that packets on Findu from cars, with the SSID of
>-9 and USING GPSMV, but not having ">/", are being displayed as a House,
>not the little red car.
>
>Does this mean these TNC's need to include a Symbol as well as GPSMV, or
>is there another issue?
Thanks for pointing this out, I had thought I was parsing the icons for all
GPSxyz, but turns out I was only looking for the X that signified
x-no-archive. I have it parsing GPSCnn, GPSEnn, and GPSMyz now, I'll be
adding the others shortly.
Steve K4HG
----------------------------------------------------------------------
Subject: WX directional antenna options
From: Miller Scott Contr 30SCS/FTI <Scott.Miller@vandenberg.af.mil>
Date: Thu, 23 Jan 2003 01:01:40 -0000
X-Message-Number: 33
Ok, so I've got my DJ-S11 on the way, ready to be disembodied and integrated
into a solar-powered weather station. For my first proposed wx site, I'm
not far at all from the digi, with a good line of sight. With luck, I ought
to be able to hit it on low power (~50mW), but I'd like to increase my
chances with a directional antenna. Anything that can yeild a few dB would
help, but I really don't want a full-size 2 meter Yagi on the pole if I can
avoid it. I think someone here mentioned corner reflectors awhile back -
can they be made a reasonable size a 144.39?
Here's a plot of the line-of-sight to the digi:
http://home.miller.org/wx-1.jpg
Digi's on the left, wx site is on the right. Tower height of the digi is
exaggerated a bit.
Scott / N6UQE
----------------------------------------------------------------------
Subject: Re: new IGATE on the way! (CQ AA3JY)
From: Bob Bruninga <bruninga@usna.edu>
Date: Wed, 22 Jan 2003 20:03:09 -0500 (EST)
X-Message-Number: 34
On Wed, 22 Jan 2003, Rich Garcia wrote:
>You can't tell if a station is a IGATE or not unless they have the proper
>ICON for it and still that is not 100%. With some detective work on the path
>statements you see on findu you can get a good idea who is the IGATE.
One thing we want is for all PERMANENT Igates to use the "I&" ICON which is
the GATEWAY ICON but with an "I" overlay. If we can get people to do
that, then we can get a much better idea of the reliability of our APRS
network.
I think WinAPRS and others default to using the "TCPIP" callsign. I used
to want everyone to change to the proper IGATE ICON (as notedd above), but
now I think it is better to let casual Igates use the default, and those
permanent 24/7 IGates to make the change so that we can see the
difference...
Bob
----------------------------------------------------------------------
Subject: Change in APRSEast Configuration (APRS IS)
From: "Mark A. Foley" <na4v@cox.net>
Date: Wed, 22 Jan 2003 20:07:56 -0500
X-Message-Number: 35
In order to better server my connected clients, I have reconfigured the
APRSEast server. Although I will continue my commitiment to the
CW/APRSWX ports, (along with with my fellow bretheren, APRSWest and
APRSCA), I have dramitically scaled back my available ports to make room
(bandwidth) for the 14580 User-definable port. UI-View, and just
recently, APRS SA+ now support this new feed...that lets the user
decided what kind of APRS IS feed he/she desires.
I'm sorry if this causes some folks grief...if you really need that full
feed, there are plenty of other servers to choose from...see
http://www.ahubswe.net/aprs_stat.asp
I want to be able to provide the best feed/with the fewest
interuptions/and still have money for my other toys....
Mark A. Foley, NA4V
APRSEast
www.na4v.com
----------------------------------------------------------------------
Subject: Re: ID Digipeaters
From: Bob Bruninga <bruninga@usna.edu>
Date: Wed, 22 Jan 2003 20:08:36 -0500 (EST)
X-Message-Number: 36
FIXING the Network (ID digis):
Back in November we did a FINDU search and generated a list of digipeaters
that appeared to be incorrectly set to UIFLOOD, "ID" instead of the
correct, UIFLOOD, NOID. As requested, users conducted the simple
local test on their local digis and reported some results.
- if a digi tested as NOID, it was removed from the list
- if it tested as "ID" it was confirmed as such and remains on the list
- if the sysop insists on leaving it as "ID" and it is not using the
DIGI ICON with the "I" overlay to idenfity itself, so that users
can konw how to interpret path data corrupted by those digis, then
it remains on the list.
Here is the new list of suspect digis which reflects that user feedback.
As you can see, we still need the test on a number of digis... and/or
either fixing them to NOID or changing their OVERLAY character from "N" to
"I" to reflect their configuration.
>If you can hear any of these digis DIRECT, you can easily confirm if
>they have ID set or not by sending a packet with only the path of
>"WIDE2-2" (the 2 is not important). If the packet comes back in the
>form of DIGIx,WIDE2-x then the DIGIx is an ID digi, and we need to know
>that so we can tell where the national APRS network is broken.
>
>If it comes back as just WIDE2-x, then it is properly set as a NOID digi
>and users are welcome then to use the normal path of WIDE,WIDEn-N so
>that the digis can then do callsign substitution and then PATHS on APRS
>will always show where a packet entered the network.. by arriving
>everywhere as DIGIa,WIDEn-N.
>
>This list is sorted from WEST to EAST in Longitude, so it should be easy
>to find your local digi, do the test, and report privately to me and I
>will clean up the list and repost...
>
>Thanks! de WB4APR, Bob
>
WIDEn DIGI Hits LAT LON
---------- ---- --- ---
VE7SLC-7 2 48 -123
VE7VAN-3 353 49 -123
BEAR 8 44 -123
VE7RQM 6 53 -123
VE7RES 4 54 -123
VE7IPB-10 244 49 -122
N6CP-1 7 36 -121 Confirmed as ID, but SYSOP will fix
VE7KIG 4 51 -121
VE7OG-12 255 49 -120
VE7TUK 4 50 -120
VE7SFX 56 50 -120
JOJ 3 46 -120
N7KMJ-10 12 45 -119
WA6YLB-4 10 35 -118
K6TVI-1 4 34 -117
W5NVH-10 17 33 -117
WA7RVV-8 186 48 -117
N7ZEV-3 7 36 -116 a HIGH digi, probably NOID, just hearing DX...
VE7PAC-12 2 49 -115
WA7RAT-12 4 35 -115
W7DXJ-1 7 35 -115
KJ7KY-15 6 34 -115
W7MOT-14 33 35 -114
WHTNKS 2 34 -113
K7MT-10 2 47 -113
RCHFLD 43 39 -113
SHEPRD 12 41 -112
N7XYR-1 9 37 -111
KD7DR-3 29 33 -111
LEMMON 2 32 -111
MULE 3 31 -110
WA5IHL-10 2 34 -108
WB5EKP-1 4 35 -108
WA5IHL-14 4 35 -107
W5SF-1 4 36 -106
KK7CN-8 14 41 -106
WA0BAG-5 38 41 -106 confirmed as "ID" but SYSOP will fix
KB0UUR 3 39 -105 confirmed as "ID" but not showing "I" overlay
WB0JRG-7 100 38 -105 confirmed as "ID" but not showing "I" overlay
KB5WIO-7 6 35 -102 confirmed as "ID" but not showing "I" overlay
KC5MVZ-3 5 34 -102
AI5TX-3 44 31 -102
N5LTC-3 5 31 -101
WD5IYT-1 41 31 -99
WD5IYT-2 152 30 -98
VE4GIL-3 20 50 -98
KE0VN-2 10 47 -97
W5EEY-11 5 33 -97
KD5MID-5 9 30 -96
K5WH-2 3 30 -96
AI5TX-2 21 30 -96
WV0T-9 3 39 -95
LTROCK 125 35 -93
KM0R-3 13 39 -93
KC0IRJ-3 8 39 -93
KG5KS-3 3 36 -92
KD4TJN-3 3 35 -90
W9GSS 5 41 -90
K9HGX 2 40 -90
WB0NOO-2 53 36 -87
W4BS-3 4 37 -87
WB0NOO-1 4 36 -86
N4KMJ-7 3 33 -86
KB8GVQ-15 59 46 -86
W8LRC 3 43 -86
W9INX-7 6 41 -86
N8RGC 2 43 -84
W4TL-3 13 35 -84
N4NEQ-3 2 35 -84
N4SEM-12 64 21 -83
AG4PX-10 2 30 -83
KF4JEX-4 27 32 -82
WC4PEM-10 8 28 -82
VE3WZL 16 44 -82
AA4QI-1 69 30 -82
KF4JEX-3 11 32 -82
N1NFC-1 15 31 -82
N4WYK-2 59 36 -82
W8GK-5 4 38 -82
W4HF-2 5 36 -82
KA4YMY-9 23 35 -82
WA4SAS-9 2 35 -82
KA4KMA-5 22 35 -81
KA4KMA-6 26 36 -81
W4APE-9 5 35 -81
K4EME-3 4 38 -80
KD4PBS-3 7 36 -79
KF4UCI-3 2 38 -79
K8SDG-6 9 40 -79
WX3P 2 43 -78
N3XBO-4 10 40 -78
KV3B-1 17 39 -78
KB3BLS-1 25 40 -77
N4EVA-11 15 37 -77
K2AMB-3 2 43 -77
KB2EAR-1 16 40 -75
VE2RTS-3 2 45 -74
IW2GUR-11 50 46 -10
CT0XCA 4 37 -8
EB5JGM-15 2 38 -2
F6KPH-14 2 43 0
F5ISQ-10 7 43 2
EA3ANS-15 37 41 2
F5KCS-2 3 50 2
EA3F-15 2 42 2
F1BIV-2 2 48 2
EA3CWQ-14 4 42 2
EA3CWQ-15 17 42 3
F5KIS-2 2 44 4
DB0KX-2 73 51 6
DB0QT 2 50 7
DB0DBU-2 16 51 7
IW1ELO-11 25 45 8
DB0DXM 4 51 8
IK1LWK-11 34 44 8
DB0GPS 4 52 9
OZ2DIH 7 55 9
IR4PC-11 8 45 9
IA5TMF-11 66 43 10
IW5BFZ-11 4 44 10
IZ4BEQ-11 5 44 10
OZ4DIX 6 55 10
IK4XQC-11 8 44 10
IR3UT 4 46 11
DB0LWL-1 2 53 11
IR3BL1 3 46 12
OZ4DIB 3 56 12
DB0ZWI 5 51 12
IR6PS 8 44 12
IW0RED 2 43 12
IR9SMB 7 38 13
IR9AAD 35 38 13
DB0AJW 5 53 13
OE8XDR-11 2 47 13
OE3XGU 3 48 15
HG5PBD-2 3 48 18
SV2EDE-11 2 41 21
SZ1RKE 2 39 22
J41VAE 5 38 23
----------------------------------------------------------------------
Read previous mail | Read next mail
| |