| |
ZL3AI > APRDIG 05.01.07 23:55l 341 Lines 9822 Bytes #999 (0) @ WW
BID : 9487-ZL3AI
Read: GUEST
Subj: [APRSSIG] Vol 31 #4, 3/4
Path: DB0FHN<DB0MRW<DK0WUE<7M3TJZ<ON0AR<ZL2BAU
Sent: 070105/2239Z @:ZL2BAU.#79.NZL.OC #:25292 [Waimate] $:9487-ZL3AI
From: ZL3AI@ZL2BAU.#79.NZL.OC
To : APRDIG@WW
Message: 15
Date: Wed, 03 Jan 2007 15:18:20 -0700
From: Earl Needham <needhame1_at_plateautel.net>
Subject: RE: [aprssig] Help with Interfacing a GPS to Kantronics KPC-3
At 03:06 PM 1/3/2007, EXT-Maetta, John wrote:
><snip>
>md:beacon e 1
>BEACON was EVERY 0 (disabled)
>cmd:N6VMO>BEACON: <UI>:
>n6vmo
>
>N6VMO>BEACON: <UI>:
>N6vmo
>
>The LED illuminates every minute to Tx the beacon.
OK, that's a good start.
At 03:01 PM 1/3/2007, EXT-Maetta, John wrote:
><snip>
>GPSHEAD
>1 $GPGGA
>2 $GPRMC
>
>LTP
>1 GPS VIA DIGI
>2 GPS VIA DIGI
>3 GPS
>4 GPS
>
>BLT
>1 EVERY 00:00:10
>2 EVERY 00:00:20
>3 EVERY 00:00:00
>4 EVERY 00:00:00
>
>LTRACK 1 LT1 LT2
Going from memory, I think the GPSHEAD and LTP commands are the only ones
that make GPS operation work. IIRC, the four BLT's are just like the
original BEACON, and I don't know what LTRACK does at all.
Put the TNC in GPS mode and connect the GPS. Let it sit there for maybe 10
or 15 minutes. Next, disconnect the GPS and connect the TNC to your laptop
and do a DISP G. That should get a list of the GPS commands -- when you do
that, copy them to us here. That's probably the best way to get this
going.
7 3
Earl
KD5XB
Clovis, New Mexico DM84jk
http://groups.yahoo.com/group/cw_bugs
"Just say NO to DHL"
------------------------------
Message: 16
Date: Wed, 3 Jan 2007 14:19:30 -0800
From: "EXT-Maetta, John" <john.maetta_at_boeing.com>
Subject: RE: [aprssig] Help with Interfacing a GPS to Kantronics KPC-3
Hi Richard,
Thanks for the reply and suggestions.
I can communicate with the TNC via my laptop. So, I know that text is
getting into it OK.
My laptop also displays GPS data from the GPS, so I know the GPS is
sending data.
73,
John N6VMO
------------------------------
Message: 17
Date: Wed, 03 Jan 2007 15:22:20 -0700
From: Earl Needham <needhame1_at_plateautel.net>
Subject: RE: [aprssig] Help with Interfacing a GPS to Kantronics KPC-3
At 03:19 PM 1/3/2007, EXT-Maetta, John wrote:
>I can communicate with the TNC via my laptop. So, I know that text is
>getting into it OK.
>My laptop also displays GPS data from the GPS, so I know the GPS is
>sending data.
But you still have to ensure that the TNC is "hearing" the GPS...
Earl
KD5XB
Clovis, New Mexico DM84jk
http://groups.yahoo.com/group/cw_bugs
"Just say NO to DHL"
------------------------------
Message: 18
Date: Wed, 3 Jan 2007 14:24:32 -0800
From: "EXT-Maetta, John" <john.maetta_at_boeing.com>
Subject: RE: [aprssig] Help with Interfacing a GPS to Kantronics KPC-3
Earl,
From what I understand from the KPC manual is that the LTRACK sets the
LTx buffer size to 1Kb.
md:disp gps
BLT
1 EVERY 00:00:10 STARTING AT 00:00:00
2 EVERY 00:00:10 STARTING AT 00:00:05
3 EVERY 00:06:00 STARTING AT 00:02:00
4 EVERY 00:12:00 STARTING AT 00:05:00
GPSHEAD
1 $GPGLL
2 $GPRMC
3 $GPRMC
4 $GPRMC
GPSINIT $pgrmo,gpgga,1
LT
1
2
3
4
LTP
1 GPSLK
2 GPSLK VIA WIDE1-1
3 GPSLK VIA WIDE1-1,WIDE2-1
4 GPSLK VIA WIDE1-1,WIDE2-2
LTRACK 1 LT1 LT2
John
------------------------------
Message: 19
Date: Wed, 03 Jan 2007 15:32:02 -0700
From: Earl Needham <needhame1_at_plateautel.net>
Subject: RE: [aprssig] Help with Interfacing a GPS to Kantronics KPC-3
At 03:24 PM 1/3/2007, EXT-Maetta, John wrote:
>LT
>1
>2
>3
>4
Somebody help me out here -- aren't the LT strings where the GPS info is
stored for transmission? If so, then the TNC isn't "hearing" the GPS.
Earl
KD5XB
Clovis, New Mexico DM84jk
http://groups.yahoo.com/group/cw_bugs
"Just say NO to DHL"
------------------------------
Message: 20
Date: Wed, 3 Jan 2007 16:37:07 -0600
From: "Michael Huslig" <mhuslig_at_kantronics.com>
Subject: Re: [aprssig] Help with Interfacing a GPS to Kantronics KPC-3
Before connecting the GPS to the KPC3, enter "INTFACE GPS". If I remember
right, 3 Ctrl-Cs will get you back into command mode, but you may want to
check the manual first.
Mike
------------------------------
Message: 21
Date: Wed, 3 Jan 2007 14:38:42 -0800
From: "EXT-Maetta, John" <john.maetta_at_boeing.com>
Subject: RE: [aprssig] Help with Interfacing a GPS to Kantronics KPC-3
Hi Mike,
Yes, I have been using this method. You are correct. I can tell it works
because I can view the GPSINIT string on my laptop as the KPC powers up.
John
-----Original Message-----
>From: Michael Huslig [mailto:mhuslig_at_kantronics.com]
>Sent: Wednesday, January 03, 2007 2:37 PM
>To: TAPR APRS Mailing List
>Subject: Re: [aprssig] Help with Interfacing a GPS to Kantronics KPC-3
>
>Before connecting the GPS to the KPC3, enter "INTFACE GPS". If I
>remember right, 3 Ctrl-Cs will get you back into command mode, but you
>may want to check the manual first.
>
>Mike
------------------------------
Message: 22
Date: Wed, 3 Jan 2007 14:41:24 -0800
From: "EXT-Maetta, John" <john.maetta_at_boeing.com>
Subject: RE: [aprssig] Help with Interfacing a GPS to Kantronics KPC-3
Earl,
I use my laptop's serial port with Hyperterminal and cable to 'simulate
the GPS' by sending the captured GPS $GPxxx strings to the KPC.
This is the same cable, laptop and terminal program I use to set the KPC
up.
The KPC still does not see the strings. The only thing I did not verify
is the data actually reaching the KPC using an o'scope. But it must,
because I can configure the KPC. There may be some querk with
Hyperterminal, but that is the only terminal program I have on the
laptop.
I should be able to send the string
$GPGGA,202153.53,3449.9685,N,12026.9276,W,1,04,2.0,00032,M,,,,*30 to the
KPC and have it parse and send it to the radio. It should also store it
in the LT buffer.
This string is what my GPS just sent to my laptop.
$GPGGA,202153.53,3449.9685,N,12026.9276,W,1,04,2.0,00032,M,,,,*30
John
------------------------------
Message: 23
Date: Wed, 03 Jan 2007 15:48:10 -0700
From: Earl Needham <needhame1_at_plateautel.net>
Subject: RE: [aprssig] Help with Interfacing a GPS to Kantronics KPC-3
At 03:41 PM 1/3/2007, EXT-Maetta, John wrote:
>I use my laptop's serial port with Hyperterminal and cable to 'simulate
>the GPS' by sending the captured GPS $GPxxx strings to the KPC.
>This is the same cable, laptop and terminal program I use to set the KPC
>up.
But what I'm trying to say, and it may be more basic than what is needed
here, is that the TNC is configured the same as a modem -- what do they
call that??? DCE or something? And it appears your GPS is configured the
same way, because you can see the data from the TNC (the "sign on message")
and you can also see the strings from the GPS. This means that data FROM
each is on the same pin, when it should, in fact, be on different pins.
The GPS should emulate your computer, not the TNC.
Somebody jump in here, I know what I'm trying to say, but I don't have the
right words to say it!
7 3
Earl
KD5XB
Clovis, New Mexico DM84jk
http://groups.yahoo.com/group/cw_bugs
"Just say NO to DHL"
------------------------------
Message: 24
Date: Wed, 3 Jan 2007 17:46:23 -0500
From: "Robert Bruninga" <bruninga_at_usna.edu>
Subject: RE: [aprssig] Help with Interfacing a GPSto Kantronics KPC-3
>I have put together the TAPR PIC-E 'dumb tracker'. The PIC-E does not
>transmit the GPS data correctly, even though the PIC-E Diags run
>correctly. It does appear to parse or recognize the $GPRMC
>string, but sends erroneous GPS characters to the radio
>(off air testing).
Be sure you are expecting the right thing. The Mic-E Format consists of
only a few bytes. The entire APRS position report in Mic-E format is only
9 bytes long and ususlly looks like gyberish, just like any TH-D7 or D700
looks.
Could that be it?
Bob
------------------------------
Message: 25
Date: Wed, 3 Jan 2007 18:03:34 -0500
From: "Robert Bruninga" <bruninga_at_usna.edu>
Subject: RE: [aprssig] Help with Interfacing a GPSto Kantronics KPC-3
>The transmitting of raw NMEA strings over the air...
>... is highly discouraged in California. Raw NMEA
>... occupy up to TEN times more air time than the
>most compact encoding format for APRS (Mic-E).
A little caution and explanation with that advice...
1) True, it is 10 times longer, but when you include the packet overhead
this is more like only a factor of 2 longer.
2) The KPC-3+ TNC tracker that sends raw NMEA can actually produce less
QRM, because it can be set to PROPORTIONAL PATHING.
Here is an example in an area where each digi can hear 5 other digis. Lets
compare a Mic-E tracker at one minute and a KPC-3+ properly set for
proportinal pathing at 1 minute and compare the total packets after 6
minutes:
Mic-E generates, 6 direct, 30 at first hop, 90 at second hop for a total of
126 packets
A KPC-3+ TNC set for proportional pathing at a 1 minute rate will generate
6 direct, 4 at first hop and 1 at second hop for a total of 11 packets.
Now these are TWICE as long due to the long NMEA string, so lets say these
take the equivalent air time of 22 packets if they were Mic-E.
SO bottom line is that a raw NMEA tracker running Proportional Pathing will
actually produce 5 times LESS qrm than a much shorter Mic-E tracker while
giving exactly the same performance locally.
I agree, that NMEA packets are LONG, but since they are mostly from KPC-3+
trackers that are the ONLY devices that can implement Proportional Pathing,
they more than make up for it in reduced QRM to everyone else. I'd
recommend using a KPC-3+ tracker with proportional pathing in most routine
applications if it is going to be a dumb tracker. Of course, other
trackers may also be efficient by using smart beaconing as implemented in
the HAM-HUD, but that is another topic since that is not a dumb tracker.
See the web page on setting up the KPC-3+ tracker for proportinal pathing:
http://www.ew.usna.edu/~bruninga/aprs/P-Pathing-kpc3.txt
Bob, WB4APR
------------------------------
Read previous mail | Read next mail
| |
