| |
ZL3AI > APRDIG 06.05.07 05:04l 264 Lines 10501 Bytes #999 (0) @ WW
BID : 10113-ZL3AI
Read: GUEST
Subj: [APRSSIG] Vol 34 #26, 1/4
Path: DB0FHN<DB0MRW<DK0WUE<7M3TJZ<ZL2BAU
Sent: 070506/0249Z @:ZL2BAU.#79.NZL.OC #:46481 [Waimate] $:10113-ZL3AI
From: ZL3AI@ZL2BAU.#79.NZL.OC
To : APRDIG@WW
Today's Topics:
1. UP Steam Train 3985/844 (Curt, WE7U)
2. Re: RE: "Local Info" confusion... (Keith VE7GDH)
3. Functional path to hit both WIDE and WIDEn-n digis? (Alex Carver)
4. Re: Functional path to hit both WIDE and WIDEn-n digis? (Robert Rochte)
5. Re: UP Steam Train 3985/844 (Jim Duncan)
6. Re: UP Steam Train 3985/844 (Curt, WE7U)
7. RE: UP Steam Train 3985/844 (Bogdan, Rick)
8. RE: UP Steam Train 3985/844 (Bogdan, Rick)
9. Re: Functional path to hit both WIDE and WIDEn-n digis? (Keith VE7GDH)
10. RE: Functional path to hit both WIDE and WIDEn-n digis? (Robert Bruninga)
11. Re: Functional path to hit both WIDE and WIDEn-n digis? (Doug Ferrell)
12. RE: Functional path to hit both WIDE and WIDEn-n digis? (Robert Bruninga)
13. Best TNC for use as portable digi? (Robert Rochte)
14. Re: Best TNC for use as portable digi? (Curt, WE7U)
15. RE: Best TNC for use as portable digi? ('Scott Miller')
16. Re: Best TNC for use as portable digi? (Robert Rochte)
17. RE: Best TNC for use as portable digi? ('Scott Miller')
18. Re: Functional path to hit both WIDE and WIDEn-n digis? (Jason D. Triolo)
19. Re: Functional path to hit both WIDE and WIDEn-n digis? (Bob Bruninga )
20. HamHud Documentation (kc2lsb)
21. Re: HamHud Documentation (Jason Rausch)
22. Re: HamHud Documentation (kc2lsb)
23. TCM3101 (vk4tec_at_people.net.au)
24. Re: Best TNC for use as portable digi? (Stephen H. Smith)
25. Re: Best TNC for use as portable digi? (Jason Winningham)
26. Signal Locator WEB page (Robert Bruninga)
27. Re: Signal Locator WEB page (Curt, WE7U)
28. Re: Signal Locator WEB page (Jason Winningham)
29. Re: Signal Locator WEB page (Richard Amirault)
30. Re: Signal Locator WEB page (J. Lance Cotton)
31. RE: Signal Locator WEB page (Robert Bruninga)
32. Re: RE: "Local Info" confusion... (Ron Tonneson)
33. RE: Signal Locator WEB page (Robert Bruninga)
----------------------------------------------------------------------
Message: 1
Date: Wed, 25 Apr 2007 10:28:49 -0700 (PDT)
From: "Curt, WE7U" <archer_at_eskimo.com>
Subject: [aprssig] UP Steam Train 3985/844
Some of you may have been watching the UP3985 Steam Train object steaming
along on your maps. Based on which engine they use it's sometimes engine
UP844 instead.
Because I can't easily discern which engine is being used I've changed the
name of the object to "STEAM".
If any of you are train-chasers and have set up igates to gate the object
to RF, gate the "STEAM" object now instead.
Ron in OR gated "UP3985" to RF a while back then chased the train through
part of OR using his D700A. He handed me a _wonderful_ videotape of the
train and was able to intercept it multiple times using this technique.
--
Curt, WE7U. APRS Client Comparisons: http://www.eskimo.com/~archer
"Lotto: A tax on people who are bad at math." -- unknown
"Windows: Microsoft's tax on computer illiterates." -- WE7U
"The world DOES revolve around me: I picked the coordinate system!"
------------------------------
Message: 2
Date: Wed, 25 Apr 2007 10:29:11 -0700
From: "Keith VE7GDH" <ve7gdh_at_rac.ca>
Subject: Re: [aprssig] RE: "Local Info" confusion...
Richard KB4YTM wrote...
>The KPC-3 tnc's that we use here as digipeaters also showed up as
>Igates using the third party beacon settings, so its not limited to just
>the UIDIGI tnc's. We switched back to Tim's recommendations.
I'm still trying to understand this. There is a stand-alone KPC-3+ digi
sitting right beside me. It has been beaconing an object for the local
repeater for a couple of months or so now. With UI-View running as an IGate
(different TNC than the digi) and on a another machine running UI-View with
a TCPIP only connection, the digi sending the object doesn't show up on the
map in UI-View as an IGate. What am I doing different from the digis that
you are observing?
And bob WB4APR just wrote...
>Its not a UIDIGI ROM issue. Its UI-View that interprets
>any source of a 3rd party packet as being an IGate. And since
>we initially suggested using 3rd party packets for these
>objects, this began to cover the map in UI-View with digipeaters
>that then were marked as IGates.
>
>So that is why we are abandoning 3rd party format and now
>recommending the original APRS object format instead. Hope
>that helps. Bob
I went back and looked at the BT in my digi:
BTEXT }147.320+>APOBJ:!4846.05N/12330.38WrPHG5730 Salt Spring Island, BC
Looking at the APRS spec, it is the "}" that makes it a third party packet.
I hear what you are saying, but in practise, the digi right beside me that
is putting out the object does NOT show up as an IGate on the map in
UI-View. Yes, I do have "highlight IGates" enabled in UI-View.
73 es cul - Keith VE7GDH
--
"I may be lost, but I know exactly where I am!"
------------------------------
Message: 3
Date: Wed, 25 Apr 2007 10:33:02 -0700 (PDT)
From: Alex Carver <kf4lvz_at_yahoo.com>
Subject: [aprssig] Functional path to hit both WIDE and WIDEn-n digis?
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 and I get digipeated by my own unit
and once in a great while when I'm driving. I don't even make it to the
APRS-IS because I have Xastir back at my place showing tracks and it only
shows a couple posits for me even after a 100 mile round trip. The posits
happen only when I was in range of a WIDEn-n digi.
When I'm mobile, I hear plenty of other position beacons coming in but mine
never seem to get anywhere.
------------------------------
Message: 4
Date: Wed, 25 Apr 2007 13:58:29 -0400
From: "Robert Rochte" <rochte_at_gmail.com>
Subject: Re: [aprssig] Functional path to hit both WIDE and WIDEn-n digis?
I'm thinking that the situation is much the same around here (the Detroit
area) as well... On my last APRS-carrying balloon flight, the digis in the
immediate area completely ignored the packets. It took a digi about 25
miles away to get the balloon on the Internet.
My guess is that this happened because we used the WIDE2-2 path (actually,
WIDE1-1,WIDE2-1 at low altitude) and the digis here didn't understand the
path.
So I second the question - how to get them all to listen??
------------------------------
Message: 5
Date: Wed, 25 Apr 2007 12:59:51 -0500
From: Jim Duncan <jdbandman_at_earthlink.net>
Subject: Re: [aprssig] UP Steam Train 3985/844
Curt:
Is the train itself transmitting the tracking information or is this
someone uplinking an object? Being a railfan and knowing that 3985 is
heading this way later this Spring I'd like to be able to track it locally.
Thanks!
Jim Duncan, KU0G
------------------------------
Message: 6
Date: Wed, 25 Apr 2007 11:12:10 -0700 (PDT)
From: "Curt, WE7U" <archer_at_eskimo.com>
Subject: Re: [aprssig] UP Steam Train 3985/844
On Wed, 25 Apr 2007, Jim Duncan wrote:
>Is the train itself transmitting the tracking information or is this
>someone uplinking an object? Being a railfan and knowing that 3985 is
>heading this way later this Spring I'd like to be able to track it locally.
It must be transmitting the info via some other system 'cuz their UP web
page gets updated pretty regularly.
I just web-scrape their page via Perl, create an APRS object, then inject
it into Firenet and/or APRS-IS (don't recall which, perhaps both).
--
Curt, WE7U. APRS Client Comparisons: http://www.eskimo.com/~archer
"Lotto: A tax on people who are bad at math." -- unknown
"Windows: Microsoft's tax on computer illiterates." -- WE7U
"The world DOES revolve around me: I picked the coordinate system!"
------------------------------
Message: 7
Date: Wed, 25 Apr 2007 14:19:56 -0400
From: "Bogdan, Rick" <rbogdan_at_ursinus.edu>
Subject: RE: [aprssig] UP Steam Train 3985/844
What is the web page for the 3985?
Rick ka1udx
Rick
------------------------------
Message: 8
Date: Wed, 25 Apr 2007 14:22:03 -0400
From: "Bogdan, Rick" <rbogdan_at_ursinus.edu>
Subject: RE: [aprssig] UP Steam Train 3985/844
Duh, never mind, I just figured it out.
Rick ka1udx
------------------------------
Message: 9
Date: Wed, 25 Apr 2007 11:25:16 -0700
From: "Keith VE7GDH" <ve7gdh_at_rac.ca>
Subject: Re: [aprssig] Functional path to hit both WIDE and WIDEn-n digis?
Alex KF4LVZ wrote...
>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.
73 es cul - Keith VE7GDH
--
"I may be lost, but I know exactly where I am!"
------------------------------
Read previous mail | Read next mail
| |
