| |
ZL3AI > APRDIG 07.02.04 13:08l 254 Lines 11065 Bytes #999 (0) @ WW
BID : 2783-ZL3AI
Read: GUEST
Subj: TAPR Digest, Feb 04, 1/4
Path: DB0FHN<DB0FOR<DB0SIF<DB0CWS<DB0ZDF<DB0GE<DB0GH<F6KMO<ON0AR<ON0AR<
VK3TE<ZL2BAU<ZL3VML
Sent: 040207/1051Z @:ZL3VML.#80.NZL.OC #:18561 [Chch-NZ] FBB7.00i $:2783-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
TAPR APRS Special Interest Group Digest for Wednesday, February 04, 2004.
1. Re: What the heck happened to Canada?
2. Garmin GPSmap C60 First Impressions
3. simple question - KPC-3 to TM-V7 wiring
4. Re: simple question - KPC-3 to TM-V7 wiring
5. Re: APRS Symbols update
6. findu and us mapping
7. Re: findu and us mapping
8. Re: findu and us mapping
9. Re: findu and us mapping
10. Re: findu and us mapping
11. Re: 9612, digipeating and kiss
12. Re: findu and us mapping
13. Re: findu and us mapping
14. Re: findu and us mapping
15. Re: findu and us mapping
16. Re: findu and us mapping
17. Speaker
18. Re: findu and us mapping
19. Re: findu and us mapping
20. Re: findu and us mapping
21. findu and mapping issues
22. Re: APRS Symbols update
23. FindU maps
24. NWS server woes
25. RE: NWS server woes
26. RE: NWS server woes
27. APRS data into mapping programs
----------------------------------------------------------------------
Subject: Re: What the heck happened to Canada?
From: James Jefferson <jj@aprsworld.net>
Date: Tue, 3 Feb 2004 22:59:58 -0600
X-Message-Number: 1
Steve -
You're welcome to use maps.aprsworld.net as you see fit. As we have discussed
in some length, it's only the US I have street level mapping for. With some
effort I can get australian and european highways online.
The format of the icon attribute for map.php has changed. It is now
symbol_table underscore symbol_code where symbol table is a three digit (zero
padded) number representing the ASCII code of the symbol table and
symbol_code is the three digit (zero padded) number representing the ASCII
code of the symbol code.
-Jim
>The evil empire bought MapBlast about 18 months ago, and shortly thereafter
>encrypted the map URL on mapblast.com, referring everything else to the
>microsoft mapping site. However, the old mapbast server was alive and well
>on vicinity.com, which was the parent of mapblast.
----------------------------------------------------------------------
Subject: Garmin GPSmap C60 First Impressions
From: "Bruce Prior" <n7rr@hotmail.com>
Date: Wed, 04 Feb 2004 06:07:32 +0000
X-Message-Number: 2
I bought the GPSmap 60C because my eTrex Vista was experiencing some
periodic mechanical problems with the toggle lever and it was time to
upgrade. The considerable increase in map capacity was especially
attractive. I had trouble removing it from the box, since the receiver was
attached to the belt clip. Garmin should have included an attached
instruction to depress the vertical lever on the belt clip to detach it
from the receiver. I was immediately impressed with the speed of
acquisition and all other functions. It must used greased chips!
Perhaps I should explain why I chose the GPSmap 60C rather than waiting for
the GPSmap 60CS model. The more expensive version includes an internal
magnetic compass and an aneroid barometer, which interfaces in some
mysterious way with the GPS altitude calculations. I have used the eTrex
Vista very extensively hiking on trails and cross-country. I found that I
used the battery-draining internal compass very rarely. I always carry a
separate compass anyway. While underway, I can create a
true-north-pointing compass by defining the North Pole (N 89° 59.999' and
any longitude) as a waypoint. The 60C has a number of features which are
lacking on the Vista, including waypoint averaging and automatic time
recording of waypoints. If it is important that I know my elevation very
accurately, I can simply define a waypoint and perform a waypoint averaging
operation for several minutes.
The screen color and resolution on the GPSmap 60C is stunning. I decided
to cover the screen with some clear plastic tape, but it left some tiny air
bubbles. I'll live with them for now. I want to protect the screen from
scuffing. I tend to use a GPS receiver in rough terrain.
I had to glance at the quick start guide to find the power on button, but
otherwise, I found the 60C quite intuitive to operate right out of the box.
A Status Bar icon labels 3D and 2D navigation -- a significant and logical
improvement over the Vista. Vertical elevation calculations require data
from four GPS satellites. I like the availability of an external antenna
connector, although I haven't acquired a separate antenna yet. Sometimes
in the dense forests of Western Washington I lose satellite tracking.
The alphanumeric keyboard is nicely done, with different sections
color-coded. I discovered the shift key on the keyboard, which toggles
between upper and lower case letters and numerals and symbols, allows for a
wide variety of characters. Waypoint labels have to be all upper case,
however. I had just one problem with using the alphanumeric keyboard. I
couldn't figure out how to erase text which I'd entered. Stephanie at
Garmin tech support solved that for me. She taught me to use the "Back"
portion on the alphanumeric keyboard, which decrements one space and
deletes the previous character or space.
Is there a complete key to the waypoint symbols somewhere? I found a
partial list available on the C60 for the waypoints to which I'd already
assigned symbols. I was amused to find that the summit of Mt. Rainier now
sports a museum! Funny, the last time I visited Columbia Crest, I saw not
one curator in residence.
J. Bruce Prior N7RR
Kairos Research
853 Alder Street
Blaine, WA 98230-8030
360-332-6046
----------------------------------------------------------------------
Subject: simple question - KPC-3 to TM-V7 wiring
From: Derek Koonce <derek@dkoonce.com>
Date: Wed, 04 Feb 2004 00:08:09 -0800
X-Message-Number: 3
I apologize for posting this here, but...
I am trying to find the wiring diagram for a KPC-3+ to a Kenwood TM-V7
data connector. The Kenwood manual says the TNC is connected into the
data connector and not the microphone connector. However, I cannot quite
figure out how the two connect. I have a rough idea, but I am not
confident about it. I have searched the web and could not find the
proper source. What I have figured out is as follows.
TM-V7 KPC-3+
1 (PKD) 1 (TXA)
6 (SQC) 2 (XCD, external CD)
3 (PKS) 3 (PTT)
4 (PR9) 5 (RXA)
2 (DE) 6 (GND)
Is this correct?
Derek
KE6JTP
----------------------------------------------------------------------
Subject: Re: simple question - KPC-3 to TM-V7 wiring
From: "Stephen H. Smith" <WA8LMF2@aol.com>
Date: Wed, 4 Feb 2004 00:52:01 -0800
X-Message-Number: 4
Full details on the MiniDIN 6-pin "DATA" connector follow. This is yet
another reprint of a post I have made many times on various groups and
mailing lists about this issue.....
====== PASTE ========
The 6-Pin MiniDIN "DATA" or "PACKET" connector is an industry standard
adopted by all the Japanese ham mfrs. It is now superseding the various
proprietary 7, 8 and 13-pin full-sized DIN connectors used by various
manufacturers. The contacts on this connector provide access to:
1) TWO kinds of receive audio:
Raw non-deemphasized discriminator output sometimes labeled "9600
Baud Receive".
De-emphasized squelched audio similar to what come out the speaker,
but at a fixed level unaffected by the volume control. It is sometimes
labled "1200 Baud Receive" or "RXD".
On multi-mode radios (Yaesu FT-817, Yaesu FT-100, Icom 706, etc),
only the "1200 baud" output will be live on AM, SSB or CW since the 9600
baud output is associated only with the discriminator of FM receivers.
2) TX audio input (sometimes misleadingly labeled "TX Data Input" or
"TXD") In some radios, a menu setting for "1200" vs "9600" baud will
determine if this input goes either into the same channel as the mic
input (but at a higher audio level) for 1200 baud packet, SSTV,
EchoLink, AFSK RTTY, etc, or is DC-coupled directly into the TX
modulator (for 9600 baud packet).
3) TX PTT (confusingly labeled "Standby" by Kenwood) -- normal
ground-to-transmit line just like most mic inputs.
4) Receiver Squelch status line (normally no sig-squelch-closed = 0V,
signal active-squelch open = 5V). Sometimes labled "COR" (Carrier
Operated Relay - an archaic term from the early days of FM repeaters),
"COS" (Carrier Operated Switch), "RX", "CD" (Carrier Detect), "Activity"
or "Busy".
5) Common/Ground.
Note that despite the misleading labels referring to data input and
output, the jack only carries AUDIO, AUDIO, AUDIO! THERE IS NO ACTUAL
RXD or TXD DATA in the sense of RS-232 or TTL-level streams of 1s and 0s
anywhere on this connector!!!
This connector is the perfect point to connect packet TNCs, soundcard
interfaces, phone patches, IRLP/EchoLink controllers, APRS trackers,
paging encoders, or any other device that needs access to the transmit
and receive audio of a radio.
These audio inputs and outputs are high-level (100-300mV), similar to
home stereo "LINE" input level seen at RCA jacks on tuners, amps, tape
decks, etc, rather the the 5-10mV level seen at most mic input jacks.
NOTE that this means that you have to set the audio output
("TRANSMIT") level of sound card interfaces, TNCs, data controllers,
APRS trackers, etc to a MUCH higher level than you would for a normal
connection into the mic jack. With some devices you will have to shift
internal jumpers, or exercise software menu commands to increase output
level (recent Kantronics TNCs for example).
On most radios with this port, grounding the DIN-6 PTT line mutes the
front panel mic input to prevent extraneous shack noises from getting
mixed with whatever you feed into the transmit audio input.
You can connect a TinyTrak here very effectively if you:
1) Change R5 (220K resistor) on the TT to about 27-33K to boost the TX
audio level from mic level to line level.
2) Connect the direct DC-coupled "CARRIER DET" line of the TT to the
MiniDIN "SQUELCH" or "COR" line.
An annotated pinout diagram of this connector, useful as a worksheet for
making up cables, is on my website at:
http://members.aol.com/wa8lmf/miscinfo
Click through the link on this page which will take you to a directory
of assorted downloadable files, not a web page. Look for the file
MiniDIN6-Packet.pdf
Note that this connector is exactly the same one used on PS/2 keyboard
and mouse cables. A PS/2 keyboard extension cable is an excellent
source of a plug and cable assembly to mate with the jack on the radio.
[at a fraction of the cost of the optional Kenwood or Yaesu cable
assemblies! ] Cut the female end off, strip the bare end and connect the
bare leads to the appropriate pins of whatever mates with your tracker,
TNC, or soundcard interface.
Stephen H. Smith wa8lmf (at) aol.com
Home Page: http://wa8lmf.com
Ham Radio/Mobile SSTV page: http://members.aol.com/wa8lmf/ham
APRS Stuff
http://members.aol.com/wa8lmf/aprs
----------------------------------------------------------------------
Read previous mail | Read next mail
| |
