| |
ZL3AI > APRDIG 31.07.03 18:28l 287 Lines 11218 Bytes #999 (0) @ WW
BID : 1701-ZL3AI
Read: GUEST
Subj: TAPR Digest, Jul 28, 1/2
Path: DB0FHN<DB0RGB<OK0PPL<OK0PKL<OK0PCC<OM0PBC<SR7BBS<SP7MGD<SR3BGN<WB0TAX<
KD7HAH<VK6HGR<ZL2BAU<ZL3VML
Sent: 030730/1324Z @:ZL3VML.#80.NZL.OC #:5424 [Chch-NZ] FBB7.00i $:1701-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
TAPR APRS Special Interest Group Digest for Monday, July 28, 2003.
1. Re: NMEA 0183 version and kenwood
2. Re: Fwd: SEA digi operations
3. Re: NMEA 0183 version and kenwood
4. Pocket APRS
5. Re: Path
6. Virginia APRS Working Group??? (MORE UNBELIEVABLE PATHS)
7. LAPTOPS, PATHS, AND TRAVEL - 1 of 3
8. LAPTOPS, PATHS, AND TRAVEL - 2 of 3
9. APRS -> NMEA gadget?
10. TEST MESSAGE
11. Looking for Mike K4MQF
12. LAPTOPS, PATHS, AND TRAVEL - 3 of 3
13. Question
14. Re: LAPTOPS, PATHS, AND TRAVEL - 3 of 3
15. Re: Question
16. Re: Question
17. RE: Question
18. Re: 30 Meter Heard List from West Coast
----------------------------------------------------------------------
Subject: Re: NMEA 0183 version and kenwood
From: "Wes Johnston" <wes@johnston.net>
Date: Mon, 28 Jul 2003 00:21:30 -0400
X-Message-Number: 1
3.0 has an extra field in the GPRMC sentance. Not sure if a gps putting out
3.0 will work when connected directly to a kenwood, but I do know that my
kenwood d700 will not decode packets which are sent by a NMEA 3.0 GPS via
"dumb tracker". I see more and more stations popping up on my display with
?? and their callsign. It is likely they are running dumb trackers such as
KPC3 or alinco types and are unaware that the kenwoods around them are not
able to decode.
Wes
----- Original Message -----
From: "Andrew Rich" <vk4tec@hotmail.com>
To: "TAPR APRS Special Interest Group" <aprssig@lists.tapr.org>
Sent: Thursday, July 24, 2003 7:06 PM
Subject: [aprssig] NMEA 0183 version and kenwood
>Gents,
>
>I have seen some emails about concerns about using THD7A or D700A and the
>newer
>NMEA0183 standard version 3.0.
>
>I would like to purchase a GARMIN Geko 201, which has version 3.0.
>
>1. Does the kenwood rigs work with 3.0 ?
>2. What is the difference between NMEA0183 Vxx and V3.0 ?
>
>Cheers
>
>Andrew VK4TEC
----------------------------------------------------------------------
Subject: Re: Fwd: SEA digi operations
From: Tim Schall <ka7pbi@fortgirlfriend.ampr.org>
Date: Sun, 27 Jul 2003 23:20:20 -0700
X-Message-Number: 2
Sort of. Problem is that it looks like VE7IPB-10 did the trimming. Which it
did not. SEA did the trimming. I'm gonna have SEA massage packets so that
they'd look more like:
aprs: fm Va7CC to 4YPSSW via VE7IPB-10* SEA* WAS5-3* WIDE3....
That way there is no question that the SEA digi touched the packet and is
probablly the culprit that altered it. Of course if some other digi altered
it then their call would be placed where the SEA* is.
On Sunday 27 July 2003 05:40, Bob Bruninga wrote:
>On Sat, 26 Jul 2003, Tim Schall wrote:
>>aprs: fm VA7CC to 4YPSSW via VE7IPB-10* WAS5-3* WIDE3 ctl UI
>>pid=F0(Text) len 13
>>
>>>From this packet we see that VE7IPB-10 trimmed the packet down from
>>>WIDE5-3
>>
>>(Which is what it WAS...) to WIDE3...... BUT WAIT! That's not what
>>happened boss! SEA trimmed that packet. This is a programming error at
>>the SEA digi that will be corrected soon.
>
>Isn't that a proper response? WIDE5-3 has already used up two. Your
>algorithm limits it to 3, so it converts to WAS5-3 AND then assumes it is
>equivalent to WIDE3-1 which it digipeats and decrements to WIDE3-0 which
>shows as WIDE3.
>
>de WB4APR@amsat.org, Bob
>
>THinking some more about it, I may have been over zealous, and although we
>encourage 3-3, maybe we out to allow 4-4 sometimes.
>
>Meaning, since we are finally puting some smarts in the network to police
>paths, (the 7-7's are the ones that dirve us crazy)... maybe we should
>just TRUNCATE to 4-4 and sitll continue with education to encourage 3-3?
>
>Isnt Washington State for example want to bring in some packets from the
>under populated hinterlands? Only locals can decide?
>Bob
----------------------------------------------------------------------
Subject: Re: NMEA 0183 version and kenwood
From: "Andrew VK4TEC" <vk4tec@hotmail.com>
Date: Mon, 28 Jul 2003 17:15:47 +1000
X-Message-Number: 3
Gents,
Depends on which parts of the $GPRMC string you use for you TNC/tracker.
If you only use the first few variables, and the rest can change as much as
it wants as far as versions go.
eg, I use a basic stamp for a parser and I only car about the time, lat and
long. and A/V
Can anyone dump me some NMEA version 3.0 $GPRMC sentences ?
Check your manual your book will say what it does.
Andrew vk4tec
----------------------------------------------------------------------
Subject: Pocket APRS
From: "Ken Patterson" <kenp@etex.net>
Date: Mon, 28 Jul 2003 07:15:38 -0000
X-Message-Number: 4
If Mike Musick is receiving this list, would you please reply to this
posting?
I have some questions regarding PocketAPRS's involvement in the North Texas
APRS Workshop.
Thanks.
de Ken, N5EQT
North Texas APRS Workshop Development Community Coordinator
----------------------------------------------------------------------
Subject: Re: Path
From: "Eric Christensen" <kf4otn@earthlink.net>
Date: Mon, 28 Jul 2003 13:32:49 -0400
X-Message-Number: 5
Tim,
I think if you read what some of the network experts out there have
written you will find out that x7-7 is a completely unreliable path
simply because of the QRM that your own packet is creating AND the
fact that you are placing your own packet through so many LANs with
the possibility of collisions that there is no way to guarantee your
packet made it through. My recommendation is that if you have to use
a long path to make it out of a valley, then you specify the
digipeaters that you wish to go through instead of using WIDE or
TRACE. It better defines where your packet will go and will reduce
the QRM.
73s,
Eric KF4OTN
----------------------------------------------------------------------
Subject: Virginia APRS Working Group??? (MORE UNBELIEVABLE PATHS)
From: "Eric Christensen" <kf4otn@earthlink.net>
Date: Mon, 28 Jul 2003 13:55:08 -0400
X-Message-Number: 6
Hey, is there a Virginia APRS Working Group that can help some of
your guys out? I have seen at least six digipeaters throwing out
HUGE paths that shouldn't be. Below is a packet (edited to attempt
to keep the owner from being known) that I received while mobile
through Virginia earlier. I know he has another digipeater (-1) that
is using the same path. He is not alone. There are two or three
with the same callsign going up the eastern edge of VA towards
Delaware that I see constantly down here in NC. Can someone help
these guys???
K4___-2>APRS,RELAY*,WIDE4-4,TRACE4-3 <UI>:!3811.19NN07746.02W#PHG8440
K4___-2 voice ###.775- tne 79.7
----------------------------------------------------------------------
Subject: LAPTOPS, PATHS, AND TRAVEL - 1 of 3
From: Gonzales Andy <agonzales@arc.nasa.gov>
Date: Mon, 28 Jul 2003 12:21:51 -0700
X-Message-Number: 7
From last Tuesday, 7/22 through Saturday, I travelled between Sunnyvale, CA
and Grover Beach, CA with a major stop at Cal Poly, San Luis Obispo with my
18 year old son. I used US 101. I have just caught up on the "sig" traffic
and would like to report on my use of APRS which may cover several items in
one post ( KG6RWO-1).
My rig consists of a Kenwood D7-THA HT, a Dell Latitude laptop, and a
Magellan 310 GPS. I also have a USB hub that is powered from the Dell. The
D7 passes connection through the USB hub. The power for these units was
supplied by adapters built for each unit and obtained commercially from
various internet sources. The adapters were all supplied from the front
console power port on my Ford Escape. The port is always hot and protected
with a 20 A fuse at the main vehicle power block. I used a two-way
connector with a third connector spliced in for the Magellan. There is an
additional 10 A fuse in series so it will go before the pwer block fuse.
The data cables were either hand-built or moified versions of commercial
units. I also had another adapter for the backup cell-phone which I ran
off the lighter plug. I assume all of these adapters have some level of
power conditioning.
I have an earpiece with a boom microphone for the D7. The drawback is that
my son can't hear the voice traffic. I am working on a way to hack around
this. I have a separate microphone / headphone for the laptop's voice
system, more on that below. I can disconnect the earphone so my son can
hear.
When I drive, I just have the D7 going and have my son make occasional
adjustments. When I bring up the computer, my son drives. It takes me
about 5 minutes to change modes.
--
Andy Gonzales
NASA / Ames Research Center
Moffett Field, CA 94035-1000
Bldg. N-244, Rm. 240
MS 244-19
agonzales@arc.nasa.gov
650-604-0309
----------------------------------------------------------------------
Subject: LAPTOPS, PATHS, AND TRAVEL - 2 of 3
From: Gonzales Andy <agonzales@arc.nasa.gov>
Date: Mon, 28 Jul 2003 12:23:17 -0700
X-Message-Number: 8
I set my path to RELAY, WIDE3-3 but after some gentle queries from Cap
Pennel, KE6AFE, changed it to WIDE3-3. My objectives were to 1) Reach an
IGATE so my wife back home could follow us on FINDU, 2) Try to reach
Tillamook, OR to see if a station there could track me. I wasn't sure
whether I needed RELAY on a long trip, but I was fine without it. Right
now, my path is WIDE, my Escape is sitting in a parking lot at Moffett
Field, CA, but I haven't hear from it since I parked it two hours ago.
Maybe I'm blocked.
Using the D7 console and later WinAPRS,I received and sent some messages
from Cap in Santa Cruz while I was stopped in Salinas changing setups. He
saw exactly where I was. I was able to send short EMAILS back to my wife. I
also sent cell phone text messages via EMAIL. On Friday, 7/25, I sent a
bunch of short messages from Grover Beach from 7:00 PM to 9:00 PM.
During long traverese I ran WinAPRS 2.7.2 and Street Atlas 2003 in
parallel. (SA 03 won't work with APRS+SA). SA 03 has its own GPS which also
connects through the USB hub. My son says that riding in the vehicle is
like being in the cockpit of the space shuttle (I work for NASA). He kicked
the USB hub at least once. On the first day, both worked great, including
the Voice Nav feature of SA. You ask "Where am I" and it replies that "your
are on United States One Hundred One, in Salinas ... ". It also tells you
when the next stop is. If you apporaching a critical off-ramp, the warning
time is not a lot..The laptop tends to run hot whether it is on internal
batteries, AC adapter, or car adapter. The metal case really transmits the
heat to your lap so I use an old hotpad from the kitchen. On other
attempts to use both, the fan on the laptop kicks in when I bring up SA.
The fan impacts the voice recognition software and SA 03 stutters on a long
time constant. If I trun voice nav off and use keyboard prompts the
directions come out fine. I can also read the routing and be the voice
myself. In general, whole voice nav is neat, it really isn't highly
reliable right now The heat issue with the laptop bothers me and I'll watch
it but I amusing purpose-built adpaters.
-- Andy Gonzales NASA / Ames Research Center Moffett Field, CA 94035-1000
Bldg. N-244, Rm. 240
MS 244-19
agonzales@arc.nasa.gov
650-604-0309
----------------------------------------------------------------------
Read previous mail | Read next mail
| |
