| |
ZL3AI > APRDIG 25.06.03 10:59l 249 Lines 9354 Bytes #999 (0) @ WW
BID : 1524-ZL3AI
Read: GUEST
Subj: TAPR Digest, Jun 22, 2/4
Path: DB0FHN<DB0RGB<DB0MRW<OK0PPL<DB0RES<ON0AR<VK6HGR<ZL2BAU<ZL3VML
Sent: 030624/1338Z @:ZL3VML.#80.NZL.OC #:2979 [Chch-NZ] FBB7.00i $:1524-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
Subject: IPaq Pocket PC and APRS/CE
From: "Barry Read" <barry@camelot.demon.co.uk>
Date: Sun, 22 Jun 2003 8:34:58
X-Message-Number: 7
I have installed version 1.02 of APRS/CE on my IPaq. It works fine except
for the verbal announcements of call signs as they are recognised by the
programme. I have copied the .WAV files over into a folder of their own
but when it comes to setting up the programme it will only load one letter
file, say an A or the B file, it is therefore not possible for the call
sign to be announced. I have tried putting the .WAV files as a folder in
the programme folder but this did not make any difference.
Has anyone been able to get the spoken call signs to work on an IPaq?
Thanks
Barry
M0EWG
----------------------------------------------------------------------
Subject: RE: Kantronics KPC-3 Manual
From: "Herb Gerhardt" <hgerhardt@charter.net>
Date: Sun, 22 Jun 2003 07:21:10 -0700
X-Message-Number: 8
Thanks to all who replied.
Yes, I got the info in just minutes after the post, made the mod and it
works great. For those who asked why, to keep it simple. Want to keep the
number of wires to a minimum. This is a portable tracker that will only
have one 12 VDC connection and the GPS plug in. As soon as those two
connectors are connected, the tracker will come alive. Yes, both the TNC
and GPS will be powered from this one 12 V connection.
Thanks again,
Herb, KB7UVC
NW APRS Group, West Sound Coordinator
Our WEB Site: www.nwaprs.org
----------------------------------------------------------------------
Subject: Re: APRS and IRLP
From: Bob Bruninga <bruninga@usna.edu>
Date: Sun, 22 Jun 2003 11:53:00 -0400 (EDT)
X-Message-Number: 9
On Sat, 21 Jun 2003, Adi Linden wrote:
>I am working away at marrying my IRLP node with APRS...
>Could someone clarify what an IRLP node should send to the APRS-IS?
In my humble opinion, it shouldn't send anything to the APRS-IS (Internet
system). The ONLY value of the IRLP information to APRS users is to
the MOBILE or portable APRS operator within simplex range of the IRLP node
letting him know via APRS what there is an IRLP node in range and what is
the frequency and current status of that node.
THat is why you only add a TNC and small HT to your serial port to
accomplish this. Sending it into the APRS-IS is practically useless in my
mind because IRLP already has all of its info LIVE on the internet, and
there is no need to QRM the APRS-IS with information that is useless to
users all over the planet.
Now, that said, here are my comments on yoru real question:
>The aprs_status script for irlp nodes does this:
>
> The format of the beacon is as follows (From the APRS Protocol Spec):
> !DDMM.mmSIDDDMM.mmE0PHGphgdFFFFFF/TTTyyyyyyyyyyzzzzzzzz
> Where:
> DD/DDDMM.mm (N/S/E/W) is the LAT/LONG
> PHGD is the power-height-gain and directivity
> FFFFFF = Node Frequency in kHz
> TTT = Node PL tone frequency
> yyyyyyyyyy = Node Status
> zzzzzzzz = Additional Info
That was the idea a long time ago. We have improved on that to better
match the particluar front panel displays of the Kenwoods...
>Then there is the message format described at
>http://www.ew.usna.edu/~bruninga/avrs.html:
>
> IRLP-####!DDMM.hhN/DDDMM.hhWLCCCCCC 44X.XXX PL YYY
>
>And from some saved email from one of the irlp or aprs groups:
>
> ;MDannap.*3859.11N/07629.11W&IRLP#12345 on 147.555 PL156
>
> Where: ;...*... is the standard APRS object format
> MDannap is the 8 char node name (Human readable, Annapolis MD)
> . The "." means IDLE. "=" is connected. "?" is down etc
> LAT/LONG is the position..
> IRLP#12345 identifies the node
> 147.555 is the frequency and PL
That also is an older, but ULTIMATE idea. I have always felt that we
need to refer to IRLP nodes by a recognizable NOUN NAME instead of
numbers. But UNTIL the noun names catch on, and we can get everyone to
choose a noun name and a DTMF digit string that matches it, then the best
thing to do these days is to make the OBJECT name be the node type and
number as in IRLP7070 or ECHO12345
Ill try to update my AVRS web page above today, if that is not clear.
Thanks
Bob, WB4APR
----------------------------------------------------------------------
Subject: RE: [amsat-bb] PCsat Test
From: Bob Bruninga <bruninga@usna.edu>
Date: Sun, 22 Jun 2003 12:08:41 -0400 (EDT)
X-Message-Number: 10
On Sat, 21 Jun 2003, James C. Hall, M.D. wrote:
>I happened to look at my UI-View and saw W3ADO show up "via PCSAT" way down
>here in TN (EM56). That intrigued me enough to look up PCsat on the AMSAT
>site. I have never used it. I do have a TH-D7 ...
PCsat is nearly dead, but 6 times a day for the last 18 months, it flies
over and sends a few packets down on 144.39. Only a few wilderness
travelers rarely use that downlink, but it was part of the design.
PCsat will re-enter full sun on July 15th or so. FOr about 2 weeks it
will come over you 6 times a day like a National Walike-Talkie DIgipeatr
in the sky. Just be on 145.825 and it will work just like 144.39 for
you...
Just a long whip on the TH-D7 APRS ht, and you can send and receive
positions, status, messages and Email... ANd check the results on your HT
or on pcsat.aprs.org where all downlinks captured are fed LIVE.
TNX for the QSL.
I listend to a 20 deg pass of PCsat this weekend on a camping trip and did
not decode one of the several packets I could hear. I could tell it was
digipeating me, but the batteries were so shot, that the packets were too
weak. But if it lasts till 15 July, she will be just fine!
Bob, WB4APR
----------------------------------------------------------------------
Subject: Re: New RINO data.
From: "Scott Miller" <scott@home.miller.org>
Date: Sun, 22 Jun 2003 09:57:38 -0700
X-Message-Number: 11
I've been worried about this too. From the Rino 120 software update license
agreement:
You acknowledge that this Software is the property of Garmin and is
protected under United States of America copyright laws and international
copyright treaties. You further acknowledge that the structure,
organization, and code of the Software are valuable trade secrets of Garmin
and that the Software in source code form remains a valuable trade secret of
Garmin. You agree not to decompile, disassemble, modify, reverse assemble,
reverse engineer, or reduce to human readable form the Software or any part
thereof or create any derivative works based on the Software.
There's probably something along the same lines shrink-wrapped with the
retail package.
Scott
N1VG
----------------------------------------------------------------------
Subject: Re: Garbage Packets -- HELP?
From: "Sean \\The RIMBoy\\" <sean@rimboy.com>
Date: Sun, 22 Jun 2003 12:08:10 -0500 (CDT)
X-Message-Number: 12
Are only the calls being distorted or are the posits being distorted too?
The posits don't appear to be distorted (at least I'm not able to see
anything jumping out at me)
However, here's some more fuel for your thouughts on K5ZRO:
http://www.findu.com/cgi-bin/find.cgi?call=W1AQN-1
The call should be W1ARN-1. Thus, another call mangled as it would appear
by K5ZRO.
>How can this happen? Could a digi be passing packets that don't have a
>valid check-sum? Are they being received properly but being distorted
>inside by the digi?
>
>Has anybody seen anything like this before? If so, give me any insight you
>have so I can pass it on to the K5ZRO trustee.
We saw something similar in Nashville, although it was also mangling
posits too (Try explaining to the XYL how you drove to Siberia). In our
case, once we finally figured out the igate owner (pre q constructs) it
turned out to be a bad serial cable. I don't know what was bad about it,
but once he turned the igate off all was well. When he brought it back
online with a new serial cable, all was well again.
For starters I would check the serial cable. From there it's then a
question of whether or not the TNC went bad or if there's a problem with
the computer. It could be a serial port gone bad. I'd start with the
cable first.
Cheers,
Sean...
----------------------------------------------------------------------
Subject: Re: Garbage Packets -- HELP?
From: Tim Schall <grover@fortgirlfriend.com>
Date: Sun, 22 Jun 2003 11:43:57 -0700
X-Message-Number: 13
Saw the same problem here in Seattle once to. Turned out to be an old 82xx
series UART in an older computer that was choking on the 19200bps speed the
TNC was spitting out. Slowed things down to 2400 baud out of the TNC and
life was good again. Serial cable is a good theory to.
Point is that it sounds, almost for certain, like data getting hammered
somewhere between a TNC and a computer. Good luck. There are a lot of
chances for things to get screwed up here.
----------------------------------------------------------------------
Subject: Re: Garbage Packets -- HELP?
From: "Scott Miller" <scott@home.miller.org>
Date: Sun, 22 Jun 2003 12:01:46 -0700
X-Message-Number: 14
So now the question is, what are the alternatives to KISS if you want error
correction? What devices support SMACK? What about 6PACK? Or is it time
for a completely new interface?
Scott
N1VG
----------------------------------------------------------------------
Read previous mail | Read next mail
| |
