| |
ZL3AI > APRDIG 06.05.07 04:57l 243 Lines 10306 Bytes #999 (0) @ WW
BID : 10117-ZL3AI
Read: GUEST
Subj: [APRSSIG] Vol 34 #27, 1/6
Path: DB0FHN<DB0FOR<DB0MRW<DK0WUE<DB0RES<DB0GOS<ON0AR<7M3TJZ<ZL2BAU
Sent: 070506/0249Z @:ZL2BAU.#79.NZL.OC #:46463 [Waimate] $:10117-ZL3AI
From: ZL3AI@ZL2BAU.#79.NZL.OC
To : APRDIG@WW
Today's Topics:
1. RE: RE: "Local Info" confusion... (Robert Bruninga)
2. Re: Functional path to hit both WIDE and WIDEn-n digis? (Alex Carver)
3. Re: Functional path to hit both WIDE and WIDEn-n digis? (Alex Carver)
4. Re: Re: Functional path to hit both WIDE and WIDEn-n digis? (Robert Rochte)
5. Re: Signal Locator WEB page (R. Simmons)
6. RE: Re: Functional path to hit both WIDE and WIDEn-n digis?
(Robert Bruninga)
7. Re: Signal Locator WEB page (Curt, WE7U)
8. Re: Re: Functional path to hit both WIDE and WIDEn-n digis?
(William McKeehan)
9. RE: Re: Functional path to hit both WIDE and WIDEn-n digis?
(Robert Bruninga)
10. Re: Re: Functional path to hit both WIDE and WIDEn-n digis? (Keith VE7GDH)
11. Re: Signal Locator WEB page (Robbie, wa9inf)
12. Re: Re: Functional path to hit both WIDE and WIDEn-n digis?
(Robbie, wa9inf)
13. Broken digis (W0APR-3, for example) (J T)
14. RE: Broken digis (W0APR-3, for example) (Robert Bruninga)
15. APRS Coverage in Key West (Eric Christensen)
16. Big Sur APRS this Sunday morning April 29 (Cap Pennell)
17. RE: APRS Coverage in Key West (Robert Bruninga)
18. RE: Broken digis (W0APR-3, for example) (Charles Doughtie)
19. RE: Signal Locator WEB page (Robert Bruninga)
20. Re: lowest common denominator (was: Signal Locator WEB page)
(Jason Winningham)
21. RE: Broken digis (W0APR-3, for example) (jdbandman_at_earthlink.net)
22. RE: Signal Locator WEB page (Robert Bruninga)
23. Re: Signal Locator WEB page (Robbie, wa9inf)
24. Re: APRS Coverage in Key West (John)
25. Re: APRS Coverage in Key West (John)
26. Re: Broken digis (W0APR-3, for example) (Jan T. Pharo)
27. Re: Signal Locator WEB page (Curt, WE7U)
28. Traffic Speed Monitoring on APRS (Robert Bruninga)
29. Re: APRS Coverage in Key West (Steve Dimse)
30. Re: APRS Coverage in Key West (Steve Dimse)
31. Re: Traffic Speed Monitoring on APRS (M J)
32. Portable IGate (Joel Maslak)
33. RE: Signal Locator WEB page (Robert Bruninga)
34. RE: Signal Locator WEB page (Keith VE7GDH)
35. Obsolete RELAY mobile Digipeaters? (Robert Bruninga)
----------------------------------------------------------------------
Message: 1
Date: Thu, 26 Apr 2007 13:14:30 -0400
From: "Robert Bruninga" <bruninga_at_usna.edu>
Subject: RE: [aprssig] RE: "Local Info" confusion...
>Are the object examples [for Voice Repeater Freqs] at
><http://www.ew.usna.edu/~bruninga/localinfo.html> up to date?
Yes, and thanks for taking a look... Sometimes it seems I am preaching to
the choir (though sometimes I wonder how many may be listening to IPODS
under their robes...)
Yes, it is finally resolved and every last quirk of Uiview, the D7, and
D700 have been accounted for (we hope).
Spread the word. I think this is a fantastic service to the mobile APRS
traveler... And what better time to get it implemented than the Great
Dayton Pilgrimage... Just since Monday, I see we picked up 10 more. Up to
85 out of 440 voice repeaters so far.
Bob
------------------------------
Message: 2
Date: Thu, 26 Apr 2007 10:33:15 -0700 (PDT)
From: Alex Carver <kf4lvz_at_yahoo.com>
Subject: [aprssig] Re: Functional path to hit both WIDE and WIDEn-n digis?
>From: "Keith VE7GDH" <ve7gdh_at_rac.ca>
>
>>A significant number of the digis in my area are using
>>WIDE or RELAY and not WIDEn-n. I don't think any
>>amount of email is going to convince them to change so
>>I'd like to find out if anyone has a path suggestion
>>for my D7/700 that will hit both types.
>>Right now I have just WIDE1-1,WIDE2-1...
>
>That's a tough question. You could be part of the solution and not part of
>the problem and just not use RELAY or WIDE, but if you are trying to make it
>to an IGate the only real solution is probably to go back to using the
>obsolete settings. It depends also on how many digis there are in your area
>that respond to RELAY and/or WIDE, but if the frequency isn't very busy, the
>impact wouldn't be as much as if it was very busy.
>There isn't any dupe checking on RELAY or WIDE, so could be lots of
>ping-ponging going on. You could try use specific callsigns in your path, but
>then you would have to change it any time you moved out of your area.
>
>Can the D7/D700 alternate digi paths like the TT3 or would you have to press
>buttons each time to change the path?
>
>I hear what you are saying about some digi operators being slow or reluctant
>to upgrade their settings. In some instances where they can't re-program
>them remotely, waiting for snow to melt in spring could be a factor. An
>option would be to put your own "new paradigm" digi(s) in but the preferable
>solution would be to get the obsolete digis to update their settings. All
>you can do is ask and suggest. If the operators either just don't care about
>the impact on the rest of the APRS network or are too lazy to change their
>settings, there isn't much you can do except hope for a (lucky) lightning
>strike to take them out, and for someone to replace them with digis using
>up-to-date settings. I would like to think that if the reason why the
>changes are so important was explained to them, more of the "hold-outs"
>would get on the band-wagon and do their part to improve things.
Well, we don't really have snow to worry about in Atlanta so that shouldn't
be an issue for them. :)
The question has been asked of them before and none of them have really
changed. There are a lot of digis using RELAY and WIDE and not many using
anything else. I certainly can't afford to add my own digis everywhere and
neither can the club station here hence the reason for asking about a
one-fits-all path. There is quite a bit of traffic already (as observed by
the club digi) but when I'm out mobile, I very rarely get digipeated using
W1,W2.
------------------------------
Message: 3
Date: Thu, 26 Apr 2007 10:38:35 -0700 (PDT)
From: Alex Carver <kf4lvz_at_yahoo.com>
Subject: [aprssig] Re: Functional path to hit both WIDE and WIDEn-n digis?
>From: "Robert Bruninga" <bruninga_at_usna.edu>
>>significant number of the digis in my area are using
>>WIDE or RELAY and not WIDEn-n. I don't think any
>>amount of email is going to convince them to change...
>
>It is incumbent on everyone of us as users of the APRS system to
>provide encouragement, and assistance to all sysops to get these
>things changed. These old legacy systems have held us back for
>now 15 years, and about 3 years ago, we decided it was time to
>move on. Then New-N Paradigm resulted.
>
>The improvments to the system have been *dramatic*.
>
>See
>http://www.ew.usna.edu/~bruninga/aprs/fix14439.html
>
>If the existing sysops don't want to do anything, we must still
>get these legacy systems set to the new paramters or new
>volunteers will just have to put up alternate digis.
>And users will have to stop using RELAY,WIDE to discourage
>their existance.
>
>While we are at it, have the SYSOPS add the locally-recommended
>VOICE repeater objects to their digis, so that travelers see
>these reeommendations on the front panel of their radios as they
>drive through.
>
>See http://www.ew.usna.edu/~bruninga/localinfo.html
>
>Bob, WB4APR
Yes, I understand all this but explain to me how to convince a sysop to add
something to a digipeater when they don't want to change the thing in the
first place. I asked the question about the path because, as of right now,
APRS is completely useless if I don't even get digipeated when I'm out and
about. I can hear plenty of traffic but my own posits never go anywhere,
APRS-IS or otherwise. The digis aren't going to change overnight and
emails to the owners have gone unanswered. So all I can do is stop using
APRS completely or adjust my path to make it functional even if it's not in
the way you want.
------------------------------
Message: 4
Date: Thu, 26 Apr 2007 13:44:13 -0400
From: "Robert Rochte" <rochte_at_gmail.com>
Subject: Re: [aprssig] Re: Functional path to hit both WIDE and WIDEn-n digis?
Short of transmitting packets and seeing which are digipeated and which are
not, is there any way to easily produce a list or map showing which paradigm
(old or new) the digipeaters in a particular area are using?
------------------------------
Message: 5
Date: Thu, 26 Apr 2007 10:57:40 -0700
From: "R. Simmons" <pelican2_at_silcom.com>
Subject: Re: [aprssig] Signal Locator WEB page
From an outsider : IMHO I agree the DF abilities of APRS have not been
cultivated and are largely dormant. I have long salivated over the prospect
of an effective web-based display with multi-hunter APRS inputs. Last year
I succeeded in making a simple PIC-based device that generates
APRS-compliant DF messages, and tested it successfully. It was detected and
plotted on FINDU.com, but with no DF bearing line. I could pursue it
further and easily offer it as a finished product, but without a means of
display, it would be pretty pointless.
Furthermore, I think hams generally don't co-operate on hunts, they compete
against each other, ( = social hunts for fun ) so the skills ( and
technology ) required for a co-ordinated "team hunt" never really get
developed.
Bob S.
------------------------------
Message: 6
Date: Thu, 26 Apr 2007 14:08:25 -0400
From: "Robert Bruninga" <bruninga_at_usna.edu>
Subject: RE: [aprssig] Re: Functional path to hit both WIDE and WIDEn-n digis?
>Short of transmitting packets and seeing which are
>digipeated and which are not, is there any way to
>esily produce a list or map showing which paradigm
>(old or new) the digipeaters in a particular area
>are using?
Sure, inherent in the New Paradigm was the idea to make sure ALL
digipeaters reported their capabilities so that we would never have this
ambiguity in the future. Just choose any APRS system map of the area.
* If the DIGI's have an overlay "S" then they are definitely New-N.
* If they have "N" overlay, then they are old-N, but should support the
recommended WIDE2-2 used by balloons with no problems.
* a rare few might show an overlay "P" and they also are a limited New-N
and should support up to WIDE2-2.
If they have none of the above, then they are obsolete.
If your client software does not display overlays on the smbols, then your
client is obsolete...
Hope that helps.
Bob, WB4APR
------------------------------
Read previous mail | Read next mail
| |
