| |
ZL3AI > APRDIG 04.05.03 18:28l 280 Lines 9771 Bytes #999 (0) @ WW
BID : 1215-ZL3AI
Read: GUEST
Subj: TAPR Digest, Apr 23, 1/4
Path: DB0FHN<DB0ZWI<DB0CHZ<DB0ERF<DB0MRW<OK0PKL<OK0PPL<RZ6HXA<SP7MGD<ON0BEL<
ON0AR<VK6HGR<ZL2BAU<ZL3VML
Sent: 030425/1331Z @:ZL3VML.#80.NZL.OC #:64547 [Chch-NZ] FBB7.00i $:1215-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
TAPR APRS Special Interest Group Digest for Wednesday, April 23, 2003.
1. Re: A bad feeling...
2. Re: A bad feeling...
3. Re: [ Steve Dimse ] Re: A bad feeling...
4. Servers down??
5. Re: Servers down??
6. What when wrong here?
7. Re: Deluo GPS WAS: Radio SHack/DeLorme GPS Unit on CLEARANCE
8. RE: What when wrong here?
9. Re: A bad feeling...
10. Just trying to understand.
11. Re: Just trying to understand.
12. Re: Just trying to understand.
13. KISS mode PIC / stamp controller?
14. RE: KISS mode PIC / stamp controller?
15. Re: software to track aprs equiped buggy
16. Re: KISS mode PIC / stamp controller?
17. Re: KISS mode PIC / stamp controller?
18. Re: KISS mode PIC / stamp controller?
19. Re: KISS mode PIC / stamp controller?
20. RE: KISS mode PIC / stamp controller?
21. Re: KISS mode PIC / stamp controller?
22. Re: KISS mode PIC / stamp controller?
23. WinAPRS Docs
24. A suggestion
25. Re: KISS mode PIC / stamp controller?
26. Re: WinAPRS Docs
27. Re: Predatory Packets
28. Re: KISS mode PIC / stamp controller?
29. Re: KISS mode PIC / stamp controller?
30. PCsat doing fine
31. Re: WinAPRS Docs
32. APRS Client Capabilities Chart (APRS-CCC?)
33. Re: WinAPRS Docs
34. Re: Predatory Packets
35. Re: WinAPRS Docs
36. Re: WinAPRS Docs
37. Re: WinAPRS Docs
38. Re: WinAPRS Docs
39. More doc stuff
40. Re: More doc stuff - APRSPLUS
41. TM-D700A Problems...
42. Re: TM-D700A Problems...
43. Re: More doc stuff - APRSPLUS
----------------------------------------------------------------------
[commercial content deleted]
----------------------------------------------------------------------
Subject: What when wrong here?
From: "Ramon F. Kolb" <ramon@ieee.org>
Date: Wed, 23 Apr 2003 08:27:57 -0400
X-Message-Number: 6
http://kx1t.webhop.org/n1qpr.jpg
See the URL for a screenshot... I'm 100% sure it's not Bill N1QPR-7 who sent
out a garbled packet, because I've seen it before from other stations. I
suspect someone in the digipeater path is doing a 8-bit to 7-bit translation
that goes wrong. It doesn't look like a bad Mic-E conversion to me, since
the packet as received still looks like it is Mic-E. Also, I've seen this
before: his Jeep symbol turns into a "dot" symbol. A POSIT or so later, he
came through a different digi/i-gate, and everything was back to normal.
Any clue what/where went wrong and how to fix it?
Thanks, 73
-Ramon
Ramon F. Kolb, KX1T, PA3EUG, Boston, MA, USA [FN42KI]
ICQ:77117744; MSNMGR:legalalien30@hotmail.com
http://kx1t.webhop.org
----------------------------------------------------------------------
[commercial content deleted]
----------------------------------------------------------------------
Subject: RE: What when wrong here?
From: "AE5PL Lists" <HamLists@ametx.com>
Date: Wed, 23 Apr 2003 09:31:26 -0500
X-Message-Number: 8
In all likelihood, probably a TNC with FILTER set to ON causing the loss
of characters less than a space. Mic-E doesn't use 8-bit characters
(only 7-bit ASCII) so that would not be a problem.
Talk to N2PGD (the IGate, in this case) and see if his TNC
initialization file has FILTER set to ON.
73,
Pete Loveall AE5PL
pete@ae5pl.net
----------------------------------------------------------------------
[commercial content deleted]
----------------------------------------------------------------------
Subject: Just trying to understand.
From: "Bruce Martin, KQ4TV" <aprssig@almostanywhere.com>
Date: Wed, 23 Apr 2003 11:19:58 -0500
X-Message-Number: 10
This morning I got a message from a friend that is active in APRS in
the nashville area but does not subscribe to the APRSsig list.
On Wednesday, April 23, 2003, at 07:33 AM, Sean wrote:
>on my D700. Saw a comment about Dayton:
>
>W8APR>APZ020,N8EMZ-3,W8MAP-4*,TRACE6-
>5,qAO,KC8OBZ:=3940.78NN08409.61W#PHG5360/DIGI_NED:
>W8APR (MVFMA) Dayton, Ohio
>
>That's right baby! Trace 6-6! And there is someone out there running
>DigiNed ! My money on the packet above is RELAY,WIDE,TRACE6-6. Can
>you
>imagine the fun that'll ensue when we all show up to Dayton and people
>are
>running mobile wides? There'll still be packets hanging around next
>year.
>
>joy.
>
>Sean...
A little investigation shows:
CLub Call -> N8EMZ-3 is a UIdigi. With an unproto of WIDE2-2. Contact
info is n8orj@arrl.net.
W8MAP-4 is a KPC3 or + with 8.2 or better. With an unproto of WIDE5-5
and is also running a WX station.
CLub Call -> W8APR is probably running WIDE,TRACE6-6. W8MAP-4
decrimented the TRACE count. Contact is jra@febo.com. This is also
showing as a KPC3 or + with 8.2 or better digi.
I had heard that the Tri-State working group recommends an unproto of
RELAY,WIDE4-4 for mobiles and WIDE4-4 for fixed stations. A look at my
xastir map with a internet feed seems to show plenty of fixed stations
(most with WX capability) and a good number of Digis in a pretty fair
distribution.
I'm not sure what the goal is but WIDE4-4 seems excessive for local
tactical communications and WIDE6-6 is way overboard.
I am not trying to be an APRS cop about this. I am just trying to
understand the reasoning for this kind of setup in the OH-IN-KY area.
Several of us have been working for years to get/keep APRS going in the
Middle Tennessee area and now that we are seeing some growth and want
to be sure that we make suggestions to newcomers that make sense for
our area.
--
Bruce W. Martin, KQ4TV
116 Beechwood Dr.
Burns, TN 37029
----------------------------------------------------------------------
Subject: Re: Just trying to understand.
From: "John R. Ackermann N8UR" <jra@febo.com>
Date: Wed, 23 Apr 2003 13:19:13 -0400
X-Message-Number: 11
Hi --
I'm responsible for W8APR. It's running DigiNED on Linux (not using a
KPC-3, but talking KISS to an MFJ-1270B) and has been using the same
configuration for over two years. In that time this is the first comment
from anyone about anything squirrely in the setup (and I'm not exactly hard
for anyone with a complaint to find), so I'm a little surprised at this.
I don't have the config file handy, but I am virtually certain that it does
not have anything like TRACE-6 in the W8APR path, probably more like
WIDE2-2 or 3-3. The config is only minimal changes to whatever the
recommended default was at the time we put it together; I didn't have the
energy to be creative.
But anyway, I'll check it out in case an error slipped through in the
config file.
73,
John N8UR
jra@febo.com
----------------------------------------------------------------------
Subject: Re: Just trying to understand.
From: "Bruce Martin, KQ4TV" <aprssig@almostanywhere.com>
Date: Wed, 23 Apr 2003 12:48:50 -0500
X-Message-Number: 12
It would seem that something may have gone wrong somewhere or just my
misunderstanding.
W8APR>APZ020,N8EMZ-3,W8MAP-4*,TRACE6-
5,qAO,KC8OBZ:=3940.78NN08409.61W#PHG5360/DIGI_NED:W8APR (MVFMA) Dayton,
Ohio
The TRACE6-5 looks suspiciously like it started as TRACE6-6
W8MAP-4* looks like it did callsign substitution and decremented the
TRACE counter.
N8EMZ-3 looks like it did callsign substitution on some other generic
call or it's own.
Hope you can find out what happened.
Bruce
----------------------------------------------------------------------
Subject: KISS mode PIC / stamp controller?
From: wes@johnston.net
Date: Wed, 23 Apr 2003 13:54:33 -0400 (EDT)
X-Message-Number: 13
I'm working on an idea (at this point, we'll call it proof of concept instead
of calling it practical).
Whereas I can't hold as much beer as I used to,
whereas TV the brightness knob on my TV doesn't help the content of
programming,
I was thinking about making a simple (emphasis on simple) digipeater which
would simply pass any and all packets heard from one frequency to another. We
all know that hooking two KISS tncs back to back (serial ports) will pass data
from one radio channel to another. This is the digipeater I'm talking about.
Problems with this include:
1 potential loops when the HID flags are not modified
2 digipeater never IDs.
I'm not too worried about loops at this point. My input will be the input
frequency of our local repeater, the output will be 144.39. The only real
issue I'm worried about at this point would be making the two TNCs ID on
144.39. For this, I'm considering a PIC processor (or basic stamp) which
will use an HSP type device to wedge it's way inbetween the two TNCs and
insert an ID. With this in mind, has anyone got any basic stamp code which
will produce an ID as a KISS Frame? If not, I'll just record an ID from my
home station in kiss and play it back on a basic stamp.
Eventually, it would be nice to have callsign substitution and real
digipeater functions, but for this proof of concept, I just want to keep it
simple. My desire at this point is to check the coverage range of our
local repeater when receiving 9600 vs 1200 bauds on it's input frequency.
Wes
----------------------------------------------------------------------
Subject: RE: KISS mode PIC / stamp controller?
From: Miller Scott Contr 30SCS/FTI <Scott.Miller@vandenberg.af.mil>
Date: Wed, 23 Apr 2003 18:17:40 -0000
X-Message-Number: 14
Haven't done it on a PIC, but it was a piece of cake to do for the HC08. I
initially built some KISS frames by hand in a binary editor, tested them by
copying them to the serial port with the TNC, and then wrote a quick program
on the HC08 to spit out the pre-built frames.
I think there are some PICs out there with dual serial interfaces. Some of
the HC08's have two SCIs, but just the big ones. For the small ones I use
(KX8), it's easiest to use the dual timer channels to do a quasi bit-banged
port.
Scott
----------------------------------------------------------------------
Read previous mail | Read next mail
| |
