| |
ZL3AI > APRDIG 06.08.06 23:57l 247 Lines 9383 Bytes #999 (0) @ WW
BID : 8521-ZL3AI
Read: DO3MCA GUEST
Subj: [APRSSIG] Vol 26 #4, 1/3
Path: DB0FHN<DB0FOR<DB0SIF<DB0EA<DB0RES<TU5EX<SR1BSZ<IW2OAZ<ZL2BAU
Sent: 060806/2154Z @:ZL2BAU.#87.NZL.OC #:62443 [Waimate] $:8521-ZL3AI
From: ZL3AI@ZL2BAU.#87.NZL.OC
To : APRDIG@WW
Today's Topics:
1. Re: Anyone know what DISABL is? (Patrick Green)
2. Re: Auto. Emailing by a D7A (Tyson S.)
3. Fw: [wl2kemcomm] Fw: [aprssig] Anyone know what DISABL is? (Mike Nettles)
4. Labels for Objects (Eric Weber)
5. "Packet Radio USB micro TNC" (Earl Needham)
6. RE: "Packet Radio USB micro TNC" (Edwards, Chris)
7. RE: "Packet Radio USB micro TNC" (Earl Needham)
8. Re: Labels for Objects (Robert Bruninga)
9. Replacing Lithium Battery in PK-900 (Matthew Stennett)
10. Re: Replacing Lithium Battery in PK-900 (Anna M Reeves)
11. Re: Replacing Lithium Battery in PK-900 (Anna M Reeves)
12. Re: Replacing Lithium Battery in PK-900 (Mark Earle)
13. Re: Replacing Lithium Battery in PK-900 (Dale Blanchard)
14. "Perhaps"; Replacing Lithium Battery in PK-900 (Matthew Stennett)
15. Re: Replacing Lithium Battery in PK-900 (Matthew Stennett)
16. Re: Replacing Lithium Battery in PK-900 (Matthew Stennett)
17. REF: Perhaps it's DEAD (Matthew Stennett)
18. Re: "Packet Radio USB micro TNC" (Lance Cotton)
19. Re: "Packet Radio USB micro TNC" (Bill Vodall)
20. Re: "Packet Radio USB micro TNC" (Earl Needham)
21. Re: "Packet Radio USB micro TNC" (Jason Winningham)
22. Re: "Packet Radio USB micro TNC" (Amateur Radio WB8NUT)
23. Re: Fw: [wl2kemcomm] Fw: [aprssig] Anyone know what DISABL is?
(Patrick Green)
24. Re: "Packet Radio USB micro TNC" (Curt, WE7U)
----------------------------------------------------------------------
Message: 1
Date: Thu, 3 Aug 2006 14:56:39 -0500
From: "Patrick Green" <pagreen_at_gmail.com>
Subject: Re: [aprssig] Anyone know what DISABL is?
Actually, this is interesting. Using the raw data, it appears that the
station is north and east of me. KD8CAO seems to pick it up regularly which
is a station call I recognize here. I'll try to probe further the next time
the band is open to Michigan.
73 de Pat --- KA9SCF.
On 8/1/06, VE7GDH <ve7gdh_at_rac.ca> wrote:
>
>Pat KA9SCF wrote...
>
>>I wouldn't be able to hear a UT station in IL terrestrially. I'm guessing
>>there are bunches of these if it's a standard config in a KPC3.
>
>You're right... Utah would be some pretty good DX! Thanks to Steve for
>suggesting the raw data at www.findu.com/cgi-bin/raw.cgi?call=disabl
>
>You might be able to run down the list and see if you recognize any of the
>stations that gated it narrow it down a bit geographically.
>
>>Would actually be interesting to hunt it down. I think I determined
>>it's north of me because stations that were south of me couldn't
>>digi through it. I can compel it to transmit because it digipeats on
>>the DISABL call as well.
>
>That's a good idea to attempt digipeating through it. If you went mobile
>with a laptop you could try driving in various directions and observe if the
>signal gets stronger or weaker. On the other hand, if you could get others
>to try from their home QTHs and either listen or try digipeating through it,
>you might be able to narrow it down without going anywhere. Guess that would
>be what Bob calls Omni DFing. A directional antenna could also be used to
>try and narrow down the direction.
>
>Good luck in tracking it/them down. Hmmm... that could make it interesting
>if there was more than one DISABL in your vicinity. It would just make it a
>bit trickier to track it down.
>
>73 es cul - Keith VE7GDH
>--
>"I may be lost, but I know exactly where I am!"
------------------------------
Message: 2
Date: Thu, 3 Aug 2006 15:31:30 -0700 (PDT)
From: "Tyson S." <timbercutter_at_yahoo.com>
Subject: Re: [aprssig] Auto. Emailing by a D7A
It is done, it is located at, http://w9if.net/iweb/perlaprs/ I tried to get
it running on my computer at home to provide the service but my knowledge
of perl is weak at best. I asked for help on it but got no response last
year. I would love to have this application running for certain reasons.
Mostly because I do not always sit and watch my computer, but if I could
set the thing to email my cell phone with the information I am looking for
then I could go to the computer and see what I want to see.
------------------------------
Message: 3
Date: Thu, 3 Aug 2006 17:48:25 -0500
From: "Mike Nettles" <Mike_Nettles_at_centurytel.net>
Subject: Fw: [wl2kemcomm] Fw: [aprssig] Anyone know what DISABL is?
Guys, I forwarded the DISABL post to the wl2k yahoo group and got this
reply. Now that the problem has been made aware(most telpac node operators
are on that list) they will start looking into it. We had the same problem
with our telpac node and it was a new kpc3+ too. We ended up using agw and
agwterm with the telpac node so it all runs together and that network
feature is turned off since it is in kiss mode.
73
Mike kb5wbh
----- Original Message -----
From: kg4vub
Sent: Thursday, August 03, 2006 4:59 PM
Subject: Re: [wl2kemcomm] Fw: [aprssig] Anyone know what DISABL is?
I discovered this a few months ago and am sorry I haven't yet shared what I
found. I can see where it can affect other applications like APRS if the
TNC is used for both Telpac and the other packet apps.
A few of us ran into this issue when we purchased KPC3+ V9.1 last November.
Someone was quick to blame Winlink on this "Phantom Beacon" and I assured
that the Winlink apps were not the cause. Well, not directly as I later
found out.....
The beacon comes from the setting for NETCALL. The default factory value is
lowercase "disabled" >> NETCALL disabled <<
When Telpac initializes and reads the original TNC settings, it saves that
setting in the registry as "disabled". If you select "restore TNC settings
on exit" in the Telpac settings, then Telpac will issue the cmd "NETCALL
DISABLED" when you close the program (along with restoring all the other
saved settings.) The TNC sees the value "DISABLED" for the NETCALL cmd and
sets that value, thinking its a node alias. This turns on the NET feature
in the TNC and results in the automatic beacon DISABL. I guess it only
holds 6 chars for the alias.
According to a phone call with Kantronics, the only way to turn it off is
with a hard reset. cmd: restore -d
In Telpac I just make sure "restore TNC settings on exit" is unchecked.
Maybe Rick can find a way to code around this issue in a future release.
But it's not his fault this happens. I am unaware of any other applications
that restore settings on exit like this though. Personally, I don't think
the firmware should require a hard reset to turn off any feature in the
TNC, and I don't know if this is the case with the 9612 or other units.
There are other settings where you could set the value to null by using %,
but I haven't tried it with NETCALL yet.
-Tom
On 8/3/06, Mike Nettles <Mike_Nettles_at_centurytel.net> wrote:
Those running a KPC3 Plus might want to check their Network Node alias. We
had the default DISABL in our Telpac node when we first set it up and it
took us a while to figure out we needed to turn off the Network Node to
keep it from ID'ing. From the APRS list it looks like some have telpac
nodes that are sending out the node broadcast. I'm guessing some have a
telpac node on the aprs frequency or other local packet frequency. Maybe
this could be added to the telpac initialization file for the kpc3+ to
automatically turn it off when it starts up telpac? Might be something to
check out,
73
Mike kb5wbh
------------------------------
Message: 4
Date: Thu, 3 Aug 2006 16:03:04 -0700 (PDT)
From: Eric Weber <webmanou812_at_yahoo.com>
Subject: [aprssig] Labels for Objects
I have a question for the group:
How would you go about labeling an object along an interstate?
I stopped and got 2 rest areas around my immediate
area, and want to put a label/id on it to reflect
where it is
One guess I had was `I-80 EAST'.. `East Bound Rest Area/Visitor Info'
But it did not tell the location except for the lat/long
Then I tried this one:'I-80 381E'.'#381 East Bound Rest Area/Visitor Info'
Where as I-80 = Interstate 80.and `381E' means mile marker 381 and `E'
equals East bound lanes.
I am guessing I am putting too much thought into this, and there is already
an easy, short way of doing this right.
Any input would be appreciated.
73's
Eric
kc0ahk
------------------------------
Message: 5
Date: Thu, 03 Aug 2006 18:07:53 -0600
From: Earl Needham <needhame1_at_plateautel.net>
Subject: [aprssig] "Packet Radio USB micro TNC"
What's the consensus on the TNCs found at http://www.elcom.gr/ and using
them with APRS? I'm thinking it might be time to replace my oldest TNC.
Thanks,
Earl
Earl Needham, KD5XB, Clovis, New Mexico DM84jk
------------------------------
Message: 6
Date: Thu, 3 Aug 2006 20:13:11 -0500
From: "Edwards, Chris" <cedwards_at_trane.com>
Subject: RE: [aprssig] "Packet Radio USB micro TNC"
i been using them for about 8 months with aprs+sa and winlink. Works well if
your aprs uses agwpe....
chris
------------------------------
Message: 7
Date: Thu, 03 Aug 2006 19:17:18 -0600
From: Earl Needham <needhame1_at_plateautel.net>
Subject: RE: [aprssig] "Packet Radio USB micro TNC"
At 07:13 PM 8/3/2006, Edwards, Chris wrote:
>i been using them for about 8 months with aprs+sa and winlink. Works well if
>your aprs uses agwpe....
I've been using AGWPE to interface "regular" TNCs for several years now --
great program.
Thanks!
Earl
Earl Needham, KD5XB, Clovis, New Mexico DM84jk
------------------------------
Read previous mail | Read next mail
| |
