| |
ZL3AI > APRDIG 28.01.07 14:16l 244 Lines 8987 Bytes #999 (0) @ WW
BID : 9636-ZL3AI
Read: GUEST
Subj: [APRSSIG] Vol 31 #31, 1/4
Path: DB0FHN<DB0FOR<DB0SIF<DB0EA<DB0RES<F5GOV<F4BWT<IW2OAZ<ZL2BAU
Sent: 070128/0611Z @:ZL2BAU.#79.NZL.OC #:29606 [Waimate] $:9636-ZL3AI
From: ZL3AI@ZL2BAU.#79.NZL.OC
To : APRDIG@WW
Today's Topics:
1. Re: Long messages (Joel Maslak)
2. Re: Long messages (VE7GDH)
3. Digi's Still Using Relay When Should Be Using Bob's New Format
(Richard N. Piper IV)
4. RE: Local Repeater Displays on Mobiles (Richard N. Piper IV)
5. RE: Local Repeater Displays on Mobiles (Richard N. Piper IV)
6. Re: Long messages (Chris Howard)
7. Re: Long messages (A.J. Farmer (AJ3U))
8. RE: Long messages (Scott Miller)
9. Re: Digi's Still Using Relay When Should Be Using Bob's New Format
(A.J. Farmer (AJ3U))
10. RE: Local Repeater Displays on Mobiles (VE7GDH)
11. RE: Local Repeater Displays on Mobiles (Robert Bruninga)
12. RE: Local Repeater Displays on Mobiles (VE7GDH)
13. RE: Local Repeater Displays on Mobiles (Earl Needham)
14. RE: 220KISS (Dave Baxter)
15. Re: Digi's Still Using Relay When Should Be Using Bob's New Format
(R. Crockett)
16. Re: Digi's Still Using Relay When Should Be Using Bob's New Format
(Bruce W. Martin)
17. PIC and telemetry question (Andrew Rich)
18. Re: PIC and telemetry question (KA8VIT)
19. RE: PIC and telemetry question (Robert Bruninga)
20. Re: Digi's Still Using Relay When Should Be Using Bob's New Format
(richard.piper_at_media4god.org)
21. Re: PIC and telemetry question (John Hansen)
22. Re: Local Repeater Displays on Mobiles (Jan T. Pharo)
23. Local Repeater objects on Uiview digipeaters (Robert Bruninga)
24. Re: Digi's Still Using Relay When Should Be Using Bob's New Format
(Richard Montgomery)
25. Re: Local Repeater objects on Uiview digipeaters
(richard.piper_at_media4god.org)
26. Re: Local Repeater objects on Uiview digipeaters (Jan T. Pharo)
27. Re: Local Repeater objects on Uiview digipeaters (Kai Gunter Brandt)
28. RE: Stuck KPC3+ serial port? (Alex Carver)
29. DIGIpeater - Network performance (Robert Bruninga)
30. Re: PIC and telemetry question (Ben Jackson)
----------------------------------------------------------------------
Message: 1
Date: Thu, 25 Jan 2007 19:52:08 -0700
From: Joel Maslak <jmaslak-aprs_at_antelope.net>
Subject: Re: [aprssig] Long messages
On Jan 25, 2007, at 7:39 PM, VE7GDH wrote:
>What sends to "APK101"? That might help track what down is sending
>the long messages.
I think that's a Kenwood. But I'm going from memory (too lazy to look it
up!)
------------------------------
Message: 2
Date: Thu, 25 Jan 2007 19:01:55 -0800
From: "VE7GDH" <ve7gdh_at_rac.ca>
Subject: Re: [aprssig] Long messages
Scott N1VG wrote...
>KD5YOV-14>APU25N,TCPIP*,qAC,AHUBSWE::KC4JGC :5.3 miles northeast of
>Norfolk, VA --- Report received 15 minutes 59 seconds ago {21
>
>The spec gives a maximum length of 67 characters for a message. That one
>is 81 characters, counting the trailing space....
Further to my comment on your post...
the above appears to have been sent by UI-View32 (version 2.03) but the
text field for entry in UI-View limits the text entered to 67 characters
unless you choose "D7" in which case it limits entry to 45 characters.
Hmmm...I wonder if KD5YOV has UI-View set for "enable UI-View32 extensions"
which would make it incompatible with messages in standard APRS format? The
UI-View32 extensions are something which I have known exists, but have
never used it because I would always want to remain compatible with those
around me. However, I just tried enabling the extensions and the message
window then allowed for 67 characters in APRS mode, 55 when not in APRS
mode and 45 characters when sending to a D7 (and presumably a D700 but
someone might want to correct me on that). It was worth a look, but it
doesn't look like the UI-View32 extensions allow for messages longer than
67 characters. Something doesn't add up.
73 es cul - Keith VE7GDH
--
"I may be lost, but I know exactly where I am!"
------------------------------
Message: 3
Date: Thu, 25 Jan 2007 22:11:37 -0600
From: "Richard N. Piper IV" <richard.piper_at_media4god.org>
Subject: [aprssig] Digi's Still Using Relay When Should Be Using Bob's
New Format
First off I know the subject is long, but we still have Digi's that are
using RELAY when they should be using Bob's New Format for APRS. I noticed
a station that for some reason has it's settings set to Wide/Relay/Trace as
noted in it's becon comment (Station is LTRock) and in the becon coment it
says that callsign is K5SCD.
* I don't live close the AK and am hering this staion in MO
* The Digi path is N5HU,KA4BNI-3,KC9FIQ-7,WIDE3 (3 or more hops)
Ok I in Missouri live in a "Rural Area" and have my station set up 2
WIDE3-3 but I thought that Relay was not to be used on 144.39 APRS anymore.
KC0RNP
Richard N. Piper IV
------------------------------
Message: 4
Date: Thu, 25 Jan 2007 22:52:47 -0600
From: "Richard N. Piper IV" <richard.piper_at_media4god.org>
Subject: RE: [aprssig] Local Repeater Displays on Mobiles
>The FREQ-ID method I propose, displays the frequency on the
>front panel station LIST all the time. If the driver has pressed
>his LIST button once, from then on, for the rest of the trip,
>the 5 most recent objects/stations will always be on his front
>panel LIST. If one of them is a voice repeater frequency, then
>that user can see it at any time hand's free. Without being
>interrupted by the flash and without having to push any buttons
>to read it.
Bob's FREQ-ID works better then having the callsign because I don't know a
repeater by it's call sign and for the most part in my area could not tell
you the callsign's of the other repeaters I use. (Side Note - most of use
don't program our radios with K0QOD, W0QMF, Ect. we program this wigh the
freq to display)
>But I know how they -are-supposed-to-work-. I know that the
>APRS spec specifically states that the originating callsign of
>an OBJECT should be retained along with the object itself so
>that ownership of an object is unambiguous. This is required
>for data integrity of the APRS system. If clients have not
>properly implemented OBJECTS according to the spec, then they
>need to be fixed.
The origination callsing needs to be retained so we know who is making the
transmission. (Ok I am not with the FCC but remember we are to ID our
stations transmissions)
>That's too bad. Here we have an opportunity to provide for
>object permanence in APRS, and I think we should consider it.
Bob, if they are not doing to change APRSIS then does this meen that when
we come up with new ideas that will not work with APRSIS they will not work
with "FindU?"
>2) I took your input about the RNGxxxx as the better way to
>display repeater range on these objects and added it to the
>recommendation. That is, until it was tested and found not to
>work on the D7 and D700.
What Local Repeater Display as I take it is for people who are Moble and
most that are Moble use a D7 or D700. Yes, some use a laptop but I think
what Bob was getting at when he came up with this was trying to give a D7
and D700 user a way to see a Repeater "Quickly"
>That is too bad. It is really a great concept and makes the
>APRS mobile travler enjoy his trip by seeing the operating
>frequency of the locally recommended repeater show up on this
>radio front panel hands-free. And this only shows up when he is
>in range. Thus it is useful, pertinent, timely, real-time
>information, which is exactly what APRS is all about. I think
>it is a great feature for APRS mobiles. And is trivial to
>implement by any local sysop in his digipeater.
If this is used "correctly" then in some areas the APRS mobile would not
need to look something up in a Repeater "Look Up Book" thus keeping his
eyes on the road and the trip
========
Ok question about how this would be set up using the UI-View Digi?
------------------------------
[duplicate]
------------------------------
Message: 6
Date: Thu, 25 Jan 2007 22:04:13 -0700
From: Chris Howard <w0ep_at_frii.com>
Subject: Re: [aprssig] Long messages
>Scott N1VG wrote...
>
>>KD5YOV-14>APU25N,TCPIP*,qAC,AHUBSWE::KC4JGC :5.3 miles northeast of
>>Norfolk, VA --- Report received 15 minutes 59 seconds ago {21
Isn't that message odd? Everything starting with '5.3 miles...' looks
like findu text.
Chris
w0ep
------------------------------
Message: 7
Date: Fri, 26 Jan 2007 00:14:54 -0500
From: "A.J. Farmer (AJ3U)" <farmer.aj_at_gmail.com>
Subject: Re: [aprssig] Long messages
On 1/25/07, VE7GDH <ve7gdh_at_rac.ca> wrote:
>What sends to "APK101"? That might help track what down is sending the long
>messages.
APK101 is a D-700. Here is the list of to-calls:
http://web.usna.navy.mil/%7Ebruninga/aprs/tocalls.txt
--
A.J. Farmer, AJ3U
http://www.aj3u.com
------------------------------
Message: 8
Date: Thu, 25 Jan 2007 21:17:32 -0800
From: "Scott Miller" <scott_at_opentrac.org>
Subject: RE: [aprssig] Long messages
>Isn't that message odd? Everything starting with '5.3 miles...' looks
>like findu text.
It does appear to be findu text. Automated or manually pasted, I'm not
sure.
Scott
N1VG
------------------------------
Read previous mail | Read next mail
| |
