| |
ZL3AI > APRDIG 27.01.07 06:08l 255 Lines 8884 Bytes #999 (0) @ WW
BID : 9627-ZL3AI
Read: GUEST
Subj: [APRSSIG] Vol 31 #29, 2/3
Path: DB0FHN<DB0RGB<DB0MRW<DK0WUE<I0TVL<TU5EX<ZS0MEE<GB7FCR<ZL2BAU
Sent: 070127/0455Z @:ZL2BAU.#79.NZL.OC #:29416 [Waimate] $:9627-ZL3AI
From: ZL3AI@ZL2BAU.#79.NZL.OC
To : APRDIG@WW
Message: 8
Date: Wed, 24 Jan 2007 14:20:37 -0600
From: Jason Winningham <jdw_at_eng.uah.edu>
Subject: Re: [aprssig] APRS telemetry and the PIC 16F877A
I found working with the PIC to be like hitting myself with a hammer - it
feels good when you stop. Architecture is RISC enough to make assembly
programming painful for a project of any size, compilers all cost $$.
I'm playing with the Atmel AVRs, in particular the ATmega8 on the Arduino.
http://www.arduino.cc/ It's got an IDE that's free, high level, and cross
platform (including Mac OS X). It's built on avrlib, so you can disregard
their GUI and use it instead if that cranks your tractor.
The Arduino NG has 6 pins that can be analog inputs or digital IO, plus a
bunch more digital IO (total of 20 I/Os). It includes a built- in RS232 to
USB adapter.
US$32 at www.sparkfun.com
Just a satisfied user, standard disclaimers apply.
-Jason
kg4wsv
------------------------------
Message: 9
Date: Wed, 24 Jan 2007 17:07:40 -0500
From: KA8VIT <ka8vit_at_ka8vit.com>
Subject: Re: [aprssig] APRS telemetry and the PIC 16F877A
Hi all,
I use the Atmel AT89S8252.. it is an 8051 variant with 8-kb of in-circuit
programmable flash, 2-kb of EEPROM, 256-bytes of ram... serial port, 3-16
bit timers... dual data pointers and more...
Even when you add a $1.10 for a crystal they are cheaper than the pics and
way out class them.
I have been playing around with them and using a 4-bit R2R ladder and a
20-bit phase accumulator to generate tones used for packet, RTTY, DTMF and
more.
http://ka8vit.com/dds
The Atmel AVRs are also an excellent choise with many of the same features
as the 8252.
73
Bill KA8VIT
--
Bill Chaikin, KA8VIT
USS COD Amateur Radio Club - W8COD
WW2 Submarine USS COD SS-224 (NECO)
ka8vit_at_ka8vit.com
http://ka8vit.com
http://www.usscod.org
QRP-L NBR: 2596
FP#-1043
------------------------------
Message: 10
Date: Wed, 24 Jan 2007 15:20:04 -0800 (PST)
From: Alex Carver <agcme2002_at_yahoo.com>
Subject: [aprssig] Stuck KPC3+ serial port?
Has anyone ever had one of their KPC3+ TNC's get stuck as far as
communicating with it via the serial port? It's set up as a digipeater
right now and is working just fine but I can't seem to connect to it. This
problem only recently cropped up but I didn't do anything special to the
TNC (as far as I know). It is unresponsive to both Hyperterm and Minicom.
The cable does work as I unplugged it from a working KAM98.
I've restarted the KPC3+ several times though I haven't used the factory
reset pins (I was hoping to avoid that so I wouldn't have to reprogram the
whole thing).
------------------------------
Message: 11
Date: Wed, 24 Jan 2007 18:28:39 -0500
From: "Robert Bruninga" <bruninga_at_usna.edu>
Subject: RE: [aprssig] Stuck KPC3+ serial port?
It could be stuck in Transparent mode or GPS mode. Hook up there serial
port and enter three ^C's preceeded and folowed by 3 seconds of nothing.
That will get it back to command mode.
Bob
Wb4APR
------------------------------
Message: 12
Date: Wed, 24 Jan 2007 15:42:02 -0800 (PST)
From: Ron <ve1aic_at_yahoo.com>
Subject: Re: [aprssig] Local Repeater Displays on Mobiles
Thanks for the update Jan. I downloaded the new symbol set from Steve's
site. I had to edit the node symbol (now green star w/overlay). It looked
too much like the Green Maple Leaf for highway route numbers on my Streets
maps which was hard to see. So I changed it back to yellow star with black
(shadow) on the tips.
73, Ron VE1AIC
>Date: Wed, 24 Jan 2007 10:01:54 +0100
>From: "Jan T. Pharo" <la2bba_at_jpharo.net>
>Subject: Re: [aprssig] Local Repeater Displays on Mobiles
>To: TAPR APRS Mailing List <aprssig_at_lists.tapr.org>
>Message-ID: <sa7er21h66bdv3fq9en0ho0b3ari10p88v_at_4ax.com>
>Content-Type: text/plain; charset=us-ascii
>
>Ron <ve1aic_at_yahoo.com>, Tue, 23 Jan 2007 16:58:33 -0800 (PST):
>
>>Hi Bob, I suspect many people (like me) were sending
>>the repeater objects from their client station. In
>>UI-View the REPEATER object is /m, whereas the ANTENNA
>>is /r so thats why so many are using /m.
>
>There is no symbol named "repeater" in the recent station setup menu
>of UI-View. There _is_ a "Mic-E Rptr" symbol. You (they) might have an
>old symbol set. The recent one can be found at
><http://wa8lmf.net/aprs/APRS_symbols.htm>
>
>--
>73 de Jan, LA2BBA
>Hvaler, Norway
------------------------------
Message: 13
Date: Wed, 24 Jan 2007 17:47:36 -0600
From: Mike Heskett <mheskett_at_mindspring.com>
Subject: Re: [aprssig] Stuck KPC3+ serial port?
At 05:20 PM 1/24/2007, you wrote:
>Has anyone ever had one of their KPC3+ TNC's get stuck
>as far as communicating with it via the serial port?
>It's set up as a digipeater right now and is working
>just fine but I can't seem to connect to it.
I had something similar to that on one recently. It appeared to be
working, but when I hooked up the computer to run an APRS Client program, I
kept getting the power on messages, as if it was doing a reset every time
it transmitted. I suspected the wall wort wasn't delivering enough power
all the sudden. I changed the wall wort but still received the same
message. I did a hard reset and it corrected the problem. I do think the
original wall wort was a problem. I wish I had tried the RESET command (a
softer reset) first, because of the problems getting all the parameters
changed from the default. I am pretty sure mine wasn't in transparent mode.
Mike Heskett
WB5QLD
Hurst, TX
O-
------------------------------
Message: 14
Date: Wed, 24 Jan 2007 16:25:27 -0800 (PST)
From: Ron <ve1aic_at_yahoo.com>
Subject: RE: [aprssig] Local Repeater Displays on Mobiles
Thanks for more input Pete. I like the callsign-R but I was considering
some other angles too. Not only how it displays on my D7, but also how it
appears on my GPS (Fortrex201). With callsign-R the '-R' is truncated on
the GPS which is not so bad but the use of the rptr freq really shows up
better than just another callsign on the little screen. In order to get the
freq to fit I had to drop the decimal point and then add the '-R' to make
it work right. So here's what I'm using for now:
;146670-R *111111z4612.74N/06320.46WrVE1CRA R60km IR2030
and
;146715-R *111111z4620.59N/06325.50WrVE1UHF Rng60km
In the first one I wanted to include IRLP info so I shortened both the
Range and IRLP to the minimum and it looks good on my D7 now. I don't think
you meant that the RNGxxxx was actually decoded as much as it was easy to
compare that range 'number' to the next screen which shows the actual
direction and distance to the object. In my case I added the 'km' to the
number to indicate km.
On D7 it shows as:
146670-R
OBJECT
VE1CRA R60
km IR2030
FN86HF
/r 9.7km <-
On my Fortex201 it shows up as Waypoint '146670'.
73, Ron
VE1AIC
------------------------------
Message: 15
Date: Thu, 25 Jan 2007 04:42:30 -0600
From: "AE5PL Lists" <HamLists_at_ametx.com>
Subject: RE: [aprssig] Local Repeater Displays on Mobiles
Yes, some older GPSs don't handle 9 character waypoints (the newer Garmins
do but you must have the D7/D700 set to send 9 character names as well).
To program for the least common denominator, IMO, leaves a lot to be
desired. You get all the info by looking up on the D7/D700 where it is
easy to see the -R (Bob, if you are doing lookups while you are in motion
behind the wheel, you are spending way too much time with your eyes off of
the road). I find it interesting that Bob has been a big proponent of
IRLP, EchoLink, and Winlink objects to use the SSID or the first two
letters of the object name as a visual identifier that it is that type of
object, yet he doesn't like that idea for voice repeaters.
Bob's refusal to say "OK" to adding,TCPIP* to the third-party path is odd
too: it takes care of APRS-IS being a factor in this discussion with
minimal effort. APRS-IS is not going to start handling certain objects
based on their names or symbols in certain ways out of the millions of
packets sent each day.
Yes, propagation in the DFW area where these objects can collide is almost
a daily issue. It must be nice for Bob to live in an isolated area where
he can pass down his pronouncements with a "I don't care if it doesn't work
for you 'cuz we don't have that problem here" attitude.
As far as the RNG number goes, yes I was talking about the range number
being visible on a D7/D700 (in nm, true, but at least it gets you close).
It also lets those clients that properly decode the 7 character extension
properly map the coverage circle. This, too, has been used for some time
by the Winlink guys in their Telpac node objects. This part about properly
coded clients mapping the range circle is something to consider when
creating these objects.
73,
Pete Loveall AE5PL
pete at ae5pl.net
------------------------------
Read previous mail | Read next mail
| |
