OpenBCM V1.08-5-g2f4a (Linux)

Packet Radio Mailbox

IZ3LSV

[San Dona' di P. JN]

 Login: GUEST





  
VK7AX  > APRS     31.12.07 00:15l 119 Lines 3838 Bytes #999 (0) @ VKNET
BID : GCHON0AR_04G
Read: GUEST
Subj: [APRS] Digest Number 1438
Path: IZ3LSV<IW2OAZ<F4BWT<I0TVL<HG8LXL<VE2PKT<ZL2BAU<VK6HGR<ON0AR
Sent: 071216/0033z @:ON0AR.#AN.BEL.EU [BBS Antwerpen] OBcm1.07b3
From: VK7AX @ ON0AR.#AN.BEL.EU
To:   APRS @ VKNET
X-Info: Sent with login password

R:071216/0015Z @:VK7NW.#ULV.TAS.AUS.OC #:32625 [NWTARIG] FBB7.00g $:VK7AX-1612AL



From: VK7AX@VK7NW.#ULV.TAS.AUS.OC
To  : APRS@VKNET



There are 3 messages in this issue.

Topics in this digest:

1. DIGI suggestions    
    From: Rod Bartlett

2a. Objects identified by frequency    
    From: Rodney
2b. Re: Objects identified by frequency    
    From: Scott Miller


Messages
________________________________________________________________________

1. DIGI suggestions
    Posted by: "Rod Bartlett" rbartlett@cablelynx.com n8qvr
    Date: Fri Dec 14, 2007 2:48 pm ((PST))


If you could use any equipment you wanted for a digi, what would it be?

I am setting up some remote digis, but I am also thinking about using
them as crossband repeaters during an emergency. I like the built in
APRS of the D700 but I prefer the FT-8800 for crossband.

I will be using Diamond X500HNA dual band antennas.

Towers will be 100 - 180 foot.

I am looking for all thoughts and suggestions.

Thanks

Rod - N8QVR


http://home.cablelynx.com/~rbartlett
<http://home.cablelynx.com/~rbartlett>



Messages in this topic (1)
________________________________________________________________________
________________________________________________________________________

2a. Objects identified by frequency
    Posted by: "Rodney" rodpadmore@ns.sympatico.ca fn84ep
    Date: Fri Dec 14, 2007 4:47 pm ((PST))

I find my Garmin III+ has recently been receiving "invalid waypoint" 
identifiers which are caused by the the decimal point when using the 
frequency as identifier of objects such as repeaters. This freezes my 
receiver and I have to hit the 'enter' button to override this-most 
cumbersome and dangerous when driving at speed. The NWAPRS site 
suggests that the owner of the object simply omit the decimal point and 
write out the whole frequency=e.g. 146.715 becomes 146715. The same 
information is conveyed but it saves Garmin receivers from freezing up. 
I also found, however, that there is some resistance to this suggestion 
so I would like to see a discussion that would resolve the issue for 
all and eliminate a problem for many Garmin users. Thank You es 73 de 
Rod,VE1BSK.



Messages in this topic (2)
________________________________________________________________________

2b. Re: Objects identified by frequency
    Posted by: "Scott Miller" scott@opentrac.org n1vg
    Date: Fri Dec 14, 2007 5:03 pm ((PST))

If you're using an OpenTracker+ or Tracker2 it should automatically 
strip any invalid characters from the waypoint name.

If you're using a Kenwood, you're probably stuck.

Hmm... I guess I could make an inline filter, but it seems like a lot of 
trouble to work around Kenwood's problems.

Scott
N1VG

Rodney wrote:
> > 
> > 
> > I find my Garmin III+ has recently been receiving "invalid waypoint"
> > identifiers which are caused by the the decimal point when using the
> > frequency as identifier of objects such as repeaters. This freezes my
> > receiver and I have to hit the 'enter' button to override this-most
> > cumbersome and dangerous when driving at speed. The NWAPRS site
> > suggests that the owner of the object simply omit the decimal point and
> > write out the whole frequency=e.g. 146.715 becomes 146715. The same
> > information is conveyed but it saves Garmin receivers from freezing up.
> > I also found, however, that there is some resistance to this suggestion
> > so I would like to see a discussion that would resolve the issue for
> > all and eliminate a problem for many Garmin users. Thank You es 73 de
> > Rod,VE1BSK.




Messages in this topic (2)
________________________________________________________________________
________________________________________________________________________



Read previous mail | Read next mail


 22.09.2024 04:07:38lGo back Go up