| |
VK7AX > UIDIGI 11.11.07 10:24l 52 Lines 1501 Bytes #999 (0) @ VKNET
BID : VK7AX-1111LD
Read: GUEST
Subj: [uidigi] Digest Number 699
Path: ON0AR<7M3TJZ<CX2SA<ZL2BAU<VK7NW
Sent: 071111/0905Z @:VK7NW.#ULV.TAS.AUS.OC #:29423 [NWTARIG] FBB7.00g $:VK7AX-1
From: VK7AX@VK7NW.#ULV.TAS.AUS.OC
To : UIDIGI@VKNET
There is 1 message in this issue.
Topics in this digest:
1a. APRS Freqeuency AMbiguity
From: Robert Bruninga
Message
________________________________________________________________________
1a. APRS Freqeuency AMbiguity
Posted by: "Robert Bruninga" bruninga@usna.edu wb4apr
Date: Thu Nov 8, 2007 5:27 pm ((PST))
>> >> My beacon announces a 2m/70cm crossband repeater
>> >> 145.250 MHz <-> 434.400 MHz
> >
> > Interesting question. I wonder what the D710 radio
> > TUNE button will do if the packet has an object name
> > of 145.250 and in its text it has 434.400MHz.
> > Interesting question.
What do people on APRS forsee as the most probable occurrence of
such an object? My thinking is that the OBJECT name would have
priority. Since it seems to be the more important... One thing
it could to is be used to announce repeaters with non-standard
splits. That way, the radio could tune the RECEIVER to the
OBJECT NAME frequency and the TX to the text frequency field...
Problem is, if that it not what the OBJECT intended, then the
radio would have done the wrong thing. So probably best to
recommend that TUNE simply take precedence on the object name...
And continue to let it get the TX frequency from the assumed
offset.
Bob
Messages in this topic (19)
________________________________________________________________________
________________________________________________________________________
Read previous mail | Read next mail
| |
