| |
ZL3AI > APRDIG 23.12.03 19:27l 114 Lines 4208 Bytes #999 (0) @ WW
BID : 2541-ZL3AI
Read: GUEST
Subj: TAPR Digest, Dec 20, 3/3
Path: DB0FHN<DB0FOR<DB0SIF<DB0EA<DB0RES<ON0AR<VE2PAK<N1UAN<ZL2BAU<ZL2BAU<
ZL3VML
Sent: 031223/1039Z @:ZL3VML.#80.NZL.OC #:15172 [Chch-NZ] FBB7.00i $:2541-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
Subject: Re: Holiday Traveling = 144.39 CTCSS 100
From: "Dale E. Reed" <w8abz@core.com>
Date: Sat, 20 Dec 2003 20:48:55 -0500
X-Message-Number: 20
SIG,
I won't bother quoting the ongoing discussion. Just wanted to say that I've
always liked the way the RS HTX-202 did tone. There's an "Rc" selection for
the receive (squelch) tone (including "none"), and an independent "Tc"
selection for the transmit tone (also including "none"). I never thought
about setting it to receive one tone and transmit another, but it'll do it.
The FT-847, FT-817 and TH-F6A all have a single selection for WHICH tone to
use on a channel, but they can all be set to not use tone, only send tone,
or send tone are require it to receive. I don't think any of them can NOT
send tone while requiring it to receive, nor can they send one tone while
receiving another without setting up split. However, the TH-F6A, having
dual receive, can use one tone selection on the "A" VFO (for transmit) and a
separate tone selection on the "B" VFO (for receive).
Guess I'll keep my old 202s!
73,
Dale, W8ABZ
----------------------------------------------------------------------
Subject: Re: aprssig digest: December 19, 2003
From: "Scott Miller" <scott@3xf.com>
Date: Sat, 20 Dec 2003 19:29:51 -0800
X-Message-Number: 21
I've been thinking about doing just that, but that's still 8 bytes per fix.
I've only got 192 to work with, and I think I'd better get the critical
stuff working first before I use up the rest of it. But it's a perfect
application for opentrac's multi-sequence capability... instead of a full
AX.25 frame header, you've only got two bytes overhead between fixes.
Scott
N1VG
-----Original Message-----
From: bounce-aprssig-31505@lists.tapr.org
[mailto:bounce-aprssig-31505@lists.tapr.org]On Behalf Of Jeff King
Sent: Saturday, December 20, 2003 3:06 PM
To: TAPR APRS Special Interest Group
Subject: [aprssig] Re: aprssig digest: December 19, 2003
One fix for this would be to "store the pegs" and only send them at a
predetermined time, reporting the current position of the object as well as
significant vector changes that occured in the past. If they where all
queued together, this would also save on transmission time.
BTW, thanks for the steak dinner Dale! (you must have told AP circuits I
referred you to them)
----------------------------------------------------------------------
Subject: Re: IGATE indication
From: JD Erskine <VA7OTC@rac.ca>
Date: Sat, 20 Dec 2003 18:40:20 -0800
X-Message-Number: 22
>What turns on the indication that a particular station is an IGATE? Is it
>a position report from an IGATE, or something else?
Simplest answer I can think of is that like all other stations the operator
can choose what symbol to display and what other characteristics to display
(transmit). All of these are included in either the POSition or Status
report from each station including any self designated IGATES.
Is that what you were after?
Cheers es 73, JD
John D. Erskine
mailto:VA7OTC@rac.ca or mailto:sailargh@victoria.tc.ca
Victoria Nautical Song Circle http://victoria.tc.ca/Culture/Vnsc/
Island Thyme Morris http://www.islandnet.com/~jcarver/is_thyme.html
----------------------------------------------------------------------
Subject: Re: aprssig digest: December 19, 2003
From: Jeff King <jeff@aerodata.net>
Date: Sat, 20 Dec 2003 22:47:35 -0500
X-Message-Number: 23
Yes, but only one callsign and one txd preamble, would save some time, but
more to the point, if you grew up where I did (an island), a 5 minute trip
to the store would have sent 25 position reports just based on 45 degree
vector changes!
--
Jeff King, jeff@aerodata.net on 12/20/2003
On Sat, 20 Dec 2003 19:29:51 -0800, Scott Miller wrote:
>I've been thinking about doing just that, but that's still 8 bytes
>per fix. I've only got 192 to work with, and I think I'd better get
>the critical stuff working first before I use up the rest of it.
>But it's a perfect application for opentrac's multi-sequence
>capability... instead of a full AX.25 frame header, you've only got
>two bytes overhead between fixes.
>
>Scott N1VG
---
END OF DIGEST
Read previous mail | Read next mail
| |
