OpenBCM V1.13 (Linux)

Packet Radio Mailbox

DB0FHN

[JN59NK Nuernberg]

 Login: GUEST





  
ZL3AI  > APRDIG   27.07.06 21:14l 153 Lines 5828 Bytes #999 (0) @ WW
BID : 8448-ZL3AI
Read: GUEST
Subj: [APRSSIG] Vol 25 #25, 2/2
Path: DB0FHN<DB0MRW<DK0WUE<7M3TJZ<ZL2BAU
Sent: 060727/1913Z @:ZL2BAU.#87.NZL.OC #:60678 [Waimate] $:8448-ZL3AI
From: ZL3AI@ZL2BAU.#87.NZL.OC
To  : APRDIG@WW

Message: 11
Date: Mon, 24 Jul 2006 19:58:41 -0700 (PDT)
From: Matthew Stennett <wa4tkg_at_yahoo.com>
Subject: [aprssig] Mounting 2M Xcvr in '05 Toyota Camry

Has anyone had any RFI trouble with mounting any of the new model 2M
transceivers in a late model Toyota Camry ? I am considering buying a used
car, and specifically, the sales guy told me ANY aftermarket Electronics
that cause any malfunctions/failures in the vehicle are of course NOT
COVERED under warranty. So, if my 50W FT-1802M BURNS UP the car's computer,
I get to pay for it MYSELF (needless to say). Is there any history of rigs
BURNING UP the electrical/electronics in peoples' cars lately ?

Matt; WA4TKG
(don't need to BURN UP my new investment, right off the LOT!)

------------------------------

Message: 12
Date: Mon, 24 Jul 2006 20:39:57 -0700
From: "Frank Keeney" <kg6jve_at_gmail.com>
Subject: RE: [aprssig] Mounting 2M Xcvr in '05 Toyota Camry

I've been running a laptop and two mobile radios in my 05 Tundra. No
problems. My neighbor runs much more in his 06 Prius.

Frank
KG6JVE

------------------------------

Message: 13
Date: Mon, 24 Jul 2006 22:10:58 -0700
From: "Todd Springer" <toddsp2_at_earthlink.net>
Subject: RE: [aprssig] Mounting 2M Xcvr in '05 Toyota Camry

I used to rent vehicles for work. I installed a temporary D700 setup in all
of them and had no problems except for the occasional dash light that would
glow. I could usually solve this by moving the ground. 
As for my personal cars they all have radios and have no trouble in any of
them the oldest is a 88 toyota PU and the newest a 03 Ford Excursion.
If you are really worried have them professionally installed at a reputable
2 way shop. 
Todd
K6TJS 

------------------------------

Message: 14
Date: Mon, 24 Jul 2006 22:38:42 -0700
From: <scott_at_opentrac.org>
Subject: [aprssig] OpenTracker !DAO! support and enhanced resolution

Finally managed to get a couple of items off of my to-do list... the latest
OpenTracker firmware (53940) supports the !DAO! enhanced position resolution
format described in the APRS 1.2 draft spec.

The !DAO! extension adds 5 bytes to the position report and gets you an
extra digit for latitude and longitude.  I'm not sure what programs, if any,
support the extension so far.  I tried it in Xastir and couldn't see any
difference.

The extra digit is also being used in Base91 calculations now, so you have
another option that's better-supported and more compact.  Works great in
Xastir, more than adequate to handle a WAAS-capable GPS receiver.

I had to cut some stuff out to make room, but I realized that all along it's
been parsing the month and year from the GPS date, and I've never found
anything to do with that data.  So that's gone, and now I've got a whopping
97 bytes of free program space to burn!  Woohoo!

Anyway, the firmware's available for download now, just hit the 'load
firmware from web' button in the config program.  Base91 will take advantage
of the extra resolution automatically, but to turn on DAO you'll need to get
the new config program at http://n1vg.net/opentracker/downloads.php.  It
adds a DAO checkbox on the right side, next to the compressed option.  Yeah,
the screen's getting crowded... I'm going to rework it as soon as I have
time.

Scott
N1VG

------------------------------

Message: 15
Date: Mon, 24 Jul 2006 23:21:49 -0700
From: "Cap Pennell" <cap_at_cruzio.com>
Subject: RE: [aprssig] using beacon text to advertise voice repeaters

I agree, Jim.  A digipeater blasting it's Position packet out everywhere all
the time is not an efficient use of our limited available airtime on the
North American VHF APRS frequency ("reducing throughput" is not courteous to
the other users of the popular frequency).  Sure, a digipeater should send
it's Position once every 10 minutes or so DIRECT, to assist travelers just
arriving within it's coverage area.  But beyond that, a digipeater using
digipeaters itself just to show off, does not have much practical use.  I'd
think a "W1,fill-in" digi could use a one hop path every once in a while,
using WIDE2-1 or "SS1-1" (NCA1-1 in Northern California), especially if
that's needed to reach the internet.  But why would a "W1,fill-in" digi need
to send it's Position using a "two high digi hops in all directions" path of
WIDE2-2 ?  Conservative VHF digipath and transmission interval settings are
courteous VHF settings.
73, Cap KE6AFE

------------------------------

Message: 16
Date: Tue, 25 Jul 2006 17:08:25 +1000
From: "Andrew Rich" <vk4tec_at_tech-software.net>
Subject: RE: [aprssig] OpenTracker !DAO! support and enhanced resolution

Kewl

Andrew Rich
Amateur radio callsign VK4TEC
email: vk4tec_at_tech-software.net <mailto:vk4tec_at_tech-software.net>
web: http://www.tech-software.net
Brisbane AUSTRALIA

------------------------------

Message: 17
Date: Tue, 25 Jul 2006 09:18:19 -0700 (PDT)
From: Vince Walton <rradiohham232_at_sbcglobal.net>
Subject: Re: [aprssig] Mounting 2M Xcvr in '05 Toyota Camry

Matthew,

I have an Yaesu FT-8100 in my 2000 Camry, I placed it in when the car was
still very new, and never had any problems, even at 50 watts. The first
time that tried it out, I started at the low power setting and moved up the
power while driving the car, expecting something maybe happen, but it has
been in the car for several years now and never had any problems.

I would be sure to route any RF cables away from any wires in the car, I
mounted the radio in the trunk, with just the remote head up front, this
way, most of the RF will be away from computers and sensors.

GL and 73
Vince, K6BIR  

------------------------------

aprssig mailing list
aprssig_at_lists.tapr.org
https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig

End of aprssig Digest, Vol 25, Issue 25



Read previous mail | Read next mail


 27.02.2026 08:40:07lGo back Go up