| |
ZL3AI > APRDIG 27.12.00 15:46l 200 Lines 6885 Bytes #999 (0) @ WW
BID : 35195_ZL3AI
Read: GUEST
Subj: TAPR Digest, Dec 22, 3/6
Path: DB0ABH<DB0RGB<OK0PPL<OK0POK<9A0YRB<HA5OB<HA3PG<PP5BLU<PY3KW<ZL2TZE<
ZL2TZE<ZL2WA<ZL2TCX<ZL2BAU<ZL3VML
Sent: 001224/0336Z @:ZL3VML.#80.NZL.OC #:51482 [Chch-NZ] FBB7.00g25 $:35195_ZL3
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
> LOCATION (10 sec time increments for xmit)
> LPATH (outgoing path)
> LTEXT
> GBAUD (GPS baud rate)
> LTMON/LTMHEAD (optional)
>
> GPS data strings interpreted are GPGGA, GPVTG, GPZDA, GPRMC, PNTS. Similar
> to other systems, you can operate fixed without a GPS by putting static
> position info in the LTXT buffer.
>
> Sections 4.5 and 5.0 have the info. I don't have an Alinco so I can't try
> it, but hope this helps.
>
> 73's,
> Skip/K3FOR
>
> ---
> You are currently subscribed to aprssig as: bruninga@usna.edu
> To unsubscribe send a blank email to leave-aprssig-18700I@lists.tapr.org
> Questions regarding the SIG go to the SIG administrator: wa1lou@tapr.org
>
>
de WB4APR@amsat.org, Bob
See my APRS LIVE pages http://web.usna.navy.mil/~bruninga/aprs.html
See APRS SATELLITES http://web.usna.navy.mil/~bruninga/astars.html
See MIM/Mic-E/Mic-Lite http://www.tapr.org/tapr/html/mic-e.html
----------------------------------------------------------------------
Subject: Re: DR-135
From: Bob Bruninga <bruninga@usna.edu>
Date: Fri, 22 Dec 2000 12:16:22 -0500 (EST)
X-Message-Number: 15
On Fri, 22 Dec 2000, wes johnston wrote:
> Can anyone tell me if the Dr135 has the same 195byte lockup problem as
> the kenwood? It is my understanding that the kenwood d700 locks up.
The 195 byte problem is an APRS PARSING error, not related to the packet
side of things. THus the Kenwoods work just fine with full size 256 byte
packets in PACKET mode, just NOT in APRS stand-alone-mode (where there is
no such thing as a legal/valid APRS packet longer than about 63 data bytes
anyway)
I believe the ALINCO uses the identical packet chip set. But it
doesn't have any internal APRS parsing (no front panel displays or
keyboard) so it will not have this problem.
de WB4APR, Bob
----------------------------------------------------------------------
Subject: GPS for D700A
From: "Bill Buckles" <bbuckles@as.net>
Date: Fri, 22 Dec 2000 11:20:48
X-Message-Number: 16
I am new to APRS.
I have just installed KENWOOD TM-D7OOA in my truck and would like
suggestions as to best GPS unit to buy for APRS use.
Any reading references would be much appreciated.
Thanks,
Bill Buckles, KG6AOC
----------------------------------------------------------------------
Subject: Re: GPS question
From: tarnerich@in-situ.com (Tony Arnerich)
Date: Fri, 22 Dec 2000 10:26:21 -0700
X-Message-Number: 17
Ray Vaughan <ray@rayvaughan.com>
>Unlike the 3+, other APRS stations don't show up on the screen.
>In Garmin's eyes, saying your hardware is >NEMA compatiable
>is something you can pick and choose from as it's convenient.
>It outputs NEMA, but has not >interest in inbound NEMA.
There is no requirement in the NMEA spec that all devices must support all
the possible sentences associated with their device family. Look up the
on-line documentation of anything Garmin sells - they list all the supported
sentences for each model. It's up to the prospective buyer to do the research
before one makes a huge purchase.
Since the SP's NMEA outputs are in compliance, I see no place where Garmin
lied to you. I do see a question you might have failed to ask, or a false
assumption you might have made.
>There's a slight hope they'll add this in a future firmware release.
One can always hope that they will respond to constructive requests because
the track record on some models is impressive. But I really doubt that it
will get supported in that model. Look at the revision history on the eMap to
see how much they do with a product that has enough room to add the requested
features. Consult the archives of sci.geo.satellite-nav (where it was settled
a long time ago) for Garmin's rationale about not being able to include WPL
support in the SP. Maybe if they come out with a new hardware platform for
it, there might be a chance. (There's precedent - the 12XL went through at
least 3 hardware platforms, each one having a clearly defined limit of the
feature sets. Mine will never have a city database or get 24 hour battery
life like the current production 12XL's have. So it goes.)
>I hope all APRS Street Pilot users have complained to Garmin about this.
Well, they've been hearing this for a l--o--n--g time now. Seeing how quick
they are to upgrade the other models, there sure seems to be something
holding them back on the SP.
73,
Tony KD7TA
----------------------------------------------------------------------
Subject: KISS mode w/KPC-3 in WinAPRS
From: tarnerich@in-situ.com (Tony Arnerich)
Date: Fri, 22 Dec 2000 11:01:40 -0700
X-Message-Number: 18
I'm trying to use a W2FS KISS TNC with WinAPRS 2.4.7, running under Win95.
Since that wasn't working (except for receive) I decided to try using my
KPC-3/5.0 as a reality check. That's not working either, beyond one or two
transmissions (queries, posits, or messages). It receives OK as long as I
don't TX. Then it jams.
When I open up the terminal window I see the KPC-3 has gone through a hard
reset, and it's sending out the "press * to set baud rate" message at all the
different baud rates.
I had set INTFACE KISS on the KPC-3;
I had done a power cycle on the KPC to activate the new INTFACE setting;
I had activated KISS mode in WinAPRS;
I had a matching ABAUD rate between the KPC and WinAPRS;
After the above, I did an "open VHF TNC" in WinAPRS;
I then started trying to TX and things jammed.
Did I leave anything out?
On another PC I've successfully run a KAM in KISS mode with WinAPRS, and it
performs flawlessly for weeks at a time.
73,
Tony KD7TA
----------------------------------------------------------------------
Subject: Re: [Re: KPC3+ Jumpers]
From: Bill Vodall <wa7nwp@yahoo.com>
Date: Fri, 22 Dec 2000 10:06:19 -0800 (PST)
X-Message-Number: 19
--- Roy Bost <rbost@itexas.net> wrote:
> If I remember correctly, on the KPC-3 the DC power comes in\out pin
> 25 on
> the DB-25 connector and on the KPC-3+ the DC power comes in\out pin
> 13 on
> the DB-25. The DC in\out on the DB-9 seems to be the same - pin 7.
This non-standardization is exactly why I'll put up with having
a separate cable for power. I'm not going to risk frying my
hardware (even if the firmware source code isn't available) by
putting accidently connecting the wrong cable.
There must be one of the multitudes of variants on Murphey's
law that relates to connecting a cable where it'll do the most
damage.
Bill - WA7NWP
----------------------------------------------------------------------
Subject: RE: GPS for D700A
From: "Ciemon G0TRT" <g0trtlists@btinternet.com>
Date: Fri, 22 Dec 2000 18:29:23 -0000
X-Message-Number: 20
I've just ordered an iGPS from
http:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
If you're not bothered about a display it's perfect.
73.....Ciemon Dunville GØTRT Sysop MB7UPG IGate
Read previous mail | Read next mail
| |