OpenBCM V1.13 (Linux)

Packet Radio Mailbox

DB0FHN

[JN59NK Nuernberg]

 Login: GUEST





  
ZL3AI  > APRDIG   25.01.07 00:04l 282 Lines 9678 Bytes #999 (0) @ WW
BID : 9614-ZL3AI
Read: GUEST
Subj: [APRSSIG] Vol 31 #25, 3/3
Path: DB0FHN<DB0MRW<OK0PPL<DB0RES<F5GOV<F4BWT<IW2OAZ<ZL2BAU
Sent: 070124/2237Z @:ZL2BAU.#79.NZL.OC #:29013 [Waimate] $:9614-ZL3AI
From: ZL3AI@ZL2BAU.#79.NZL.OC
To  : APRDIG@WW

Message: 18
Date: Mon, 22 Jan 2007 17:32:57 -0600
From: "Alan P. Biddle" <APBIDDLE_at_UNITED.NET>
Subject: RE: [aprssig] Tiny Tracker III loading?

Bob,

Except for the path issue, the symptoms you describe could also be caused
by RF problems into the TinyTrak.  Neither version II or III have much RF
immunity.  I have seen EXACTLY those symptoms with mine, including the
stretched TXD, which is a good reason to put it where the TX LED is
visible. There are any number of fixes, such as a metal case and/or better
shielding and chokes.  All of which just underlines your advice to stop,
look and sometimes listen!

Alan
WA4SCA

------------------------------

Message: 19
Date: Mon, 22 Jan 2007 16:27:55 -0800 (PST)
From: Curt Mills <archer_at_eskimo.com>
Subject: Re: [aprssig] Weather station AAG 1 wire

On Tue, 23 Jan 2007, Phillip wrote:

>AAG 1 Wire TAI 8515 with the DS9097u-SO9 comport adaptor.
>  
>I am having a problem with the RJ 11 female  at the comport adaptor and
>would like to know which pins in the RJ 11 are used.
>  
>I have 2 lots of conflicting information on the Pin outs of the RJ 11 the
>one from AAG has pin 1 on the left hand side looking from the back of the
>plug with the lock tab down and Dallas pin 1 on the right

I have borrowed a Dallas 1-wire in the past for testing.  As of a week or
two ago I now own that unit, but I haven't hooked it up yet.

Could it be that the AAG-supplied and Dallas-supplied RJ-11 cables were
crimped differently?  That's what I would expect.  Some RJ cables line up
pin 1 with pin 1, some flip one end.

-- 
Curt, WE7U.				archer at eskimo dot com
http://www.eskimo.com/~archer
Lotto:  A tax on people who are bad at math. - unknown
Windows:  Microsoft's tax on computer illiterates. - WE7U.
The world DOES revolve around me:  I picked the coordinate system!"

------------------------------

Message: 20
Date: Mon, 22 Jan 2007 16:24:38 -0800 (PST)
From: Curt Mills <archer_at_eskimo.com>
Subject: Re: [aprssig] aprs event next weekend.

On Sun, 21 Jan 2007, Wes Johnston, AI4PX wrote:

>By the way, the reason I'm using "emergency" mic-e packet is to make darned
>sure that the kenwood d700's running around mobile get everyone's
>attention.  Does anyone know if the d700 will beep for "priority" type
>packet?  What about xastir?

A very sweet use of the existing technology Wes...

Xastir should center the map and bring up a popup, but I don't think it
issues any voice or audio.

-- 
Curt, WE7U.				archer at eskimo dot com
http://www.eskimo.com/~archer
Lotto:  A tax on people who are bad at math. - unknown
Windows:  Microsoft's tax on computer illiterates. - WE7U.
The world DOES revolve around me:  I picked the coordinate system!"

------------------------------

Message: 21
Date: Mon, 22 Jan 2007 19:34:28 -0500
From: Stan Horzepa <stanzepa_at_sbcglobal.net>
Subject: [aprssig] PSR Deadline

The deadline for the next issue of TAPR's quarterly newsletter, Packet
Status Register (PSR), is approaching fast (it's next Monday), so if you
have anything you would like to contribute to the newsletter, please e-mail
it to me as soon as you can.

Remember, if you are a TAPR member, each published contribution to PSR
automatically extends your TAPR membership by three months.

Thanks and 73,

Stan, WA1LOU, PSR Editor

------------------------------

Message: 22
Date: Mon, 22 Jan 2007 22:15:10 -0600
From: "Tim Cunningham" <tim_cunningham_at_mindspring.com>
Subject: Re: [aprssig] New Local Info Initiative

>Though, I have not fully digested how one would do this in a non
>KPC-3+ TNC...  I'd like to see someone suggest how best to do it
>on a UIDIGI ROM?

Since proportional beaconing/pathing  cannot be accomplished on the UIDIGI 
with the BeaconOffset not working properly, you only have 3 BeaconText 
settings that can be utilized inclusively of themselves to be proportional. 
Right now we have Beacon1Text set to fire at Beacon1Interval of 10 minutes 
using a local path or no path. Then we have Beacon2Text set to fire at 
Beacon2Interval of 29 minutes using a one hop path so it does not get 
bunched with Beacon1Text.

Now it seems to me that I would want to use Beacon3Text for the local info 
initiative rather than spamming my neighbors 2 hops away at a 59 minute rate 
to avoid colliding with the 10 and 29 minute interval of the previous 2 
beacons. Actually, it only makes sense to end Beacon3Text and use it for 
something more practical and useful for the local area rather than spamming 
the neighbors every hour.

However, you are not going to get UIDIGI to fill the time slot so it will 
need to be hard coded with something like 000000 as shown below:

Beacon3Text = ;146.940- *000000zDDMM.hhN/DDDMM.hhWrPHG7660-600 PL100 Net 
Thur 730PM
Beacon3Path =     <== nothing required for local path unless you want LOCAL 
to appear in the path
Beacon3Interval = 600

73's,

Tim - N8DEU
Huntsville, Alabama
http://www.qsl.net/n8deu/uidigi_eprom_settings.htm

------------------------------

Message: 23
Date: Mon, 22 Jan 2007 21:55:00 -0800
From: "Cap Pennell" <cap_at_cruzio.com>
Subject: RE: [aprssig] New Local Info Initiative

See below.

>-----Original Message-----
>From: aprssig-bounces_at_lists.tapr.org
>[mailto:aprssig-bounces_at_lists.tapr.org]On Behalf Of Tim Cunningham
>Sent: Monday, January 22, 2007 20:15 PM
>To: bruninga_at_usna.edu; TAPR APRS Mailing List
>Subject: Re: [aprssig] New Local Info Initiative
>
>>Though, I have not fully digested how one would do this in a non
>>KPC-3+ TNC...  I'd like to see someone suggest how best to do it
>>on a UIDIGI ROM?
>
>Since proportional beaconing/pathing  cannot be accomplished on
>the UIDIGI
>with the BeaconOffset not working properly, you only have 3 BeaconText
>settings that can be utilized inclusively of themselves to be
>proportional.
>Right now we have Beacon1Text set to fire at Beacon1Interval of
>10 minutes
>using a local path or no path. Then we have Beacon2Text set to fire at
>Beacon2Interval of 29 minutes using a one hop path so it does not get
>bunched with Beacon1Text.
>
>Now it seems to me that I would want to use Beacon3Text for the
>local info
>initiative rather than spamming my neighbors 2 hops away at a 59
>minute rate
>to avoid colliding with the 10 and 29 minute interval of the previous 2
>beacons. Actually, it only makes sense to end Beacon3Text and use it for
>something more practical and useful for the local area rather
>than spamming
>the neighbors every hour.
>
>However, you are not going to get UIDIGI to fill the time slot so it will
>need to be hard coded with something like 000000 as shown below:
>
>Beacon3Text = ;146.940- *000000zDDMM.hhN/DDDMM.hhWrPHG7660-600 PL100 Net
>Thur 730PM
>Beacon3Path =     <== nothing required for local path unless you
>want LOCAL
>to appear in the path
>Beacon3Interval = 600

Yes, and to setup those 3 Beacons by REMOTE access (while the TNC is still
up on the mountaintop), or local access, the sysop's command syntax could
be:

BT 1 !3424.30NS08648.02W#PHG5670/W3,ALn Wilson Mtn A=001360
BDL 1        ;NONE
BE 1 600     ;10 minutes

BT 2 !3424.30NS08648.02W#PHG5670/W3,ALn Wilson Mtn A=001360
BDL 2 WIDE2-1
BE 2 1740    ;29 minutes

BT 3 ;146.760- *111111zDDMM.hhN/DDDMM.hhWrPHG7660-600 PL100 Net Thur730PM
BDL 3        ;NONE
BE 3 600     ;10 minutes

(Sysop command syntax abbreviations as shown in the UIDIGIE.DOC file that
comes within the UIDIGI software's.zip file)
73, Cap

------------------------------

[commercial content deleted]

------------------------------

Message: 25
Date: Tue, 23 Jan 2007 07:54:19 -0800
From: "Eric Goforth" <eric_at_goforthtech.com>
Subject: RE: [aprssig] Homage To Bob / Kenwood Specialized Manual

Julien;

How can I obtain this manual?  Thanks.

Eric J. Goforth, N6GOF

www.APRSDEPOT.com <http://www.aprsdepot.com/> 

------------------------------

Message: 26
Date: Tue, 23 Jan 2007 07:59:31 -0800
From: "Eric Goforth" <eric_at_goforthtech.com>
Subject: RE: [aprssig] aprs event next weekend.

Hi Wes;

What event is this for?  I love following APRS events and was just
curious... Thanks.

Eric J. Goforth, N6GOF

www.APRSDEPOT.com <http://www.aprsdepot.com/> 

>From: aprssig-bounces_at_lists.tapr.org
>[mailto:aprssig-bounces_at_lists.tapr.org] On Behalf Of Wes Johnston, AI4PX
>Sent: Sunday, January 21, 2007 7:49 PM
>To: TAPR APRS Mailing List
>Subject: [aprssig] aprs event next weekend.
>
>Next sunday, Jan 28th we will be using APRS to track the last rider in a
>motocross enduro race.  I have programmed a tinytrak with a pushbutton
>such that it will squawk an ambulance and a mic-e emergency packet when
>pushed.  The callsign will be ai4px-11.  We will be running the event on
>144.99mhz and setting up temporary digi's around the course.  It may be
>that these packets get gated to 144.39 and onto the network feed, so if
>you see an emergency packet from ai4px-11, don't worry, we've got it
>covered.  I've programmed the beacon text with "this is a test" so
>people won't get too wound up trying to respond....  we'll have 15
>some-odd hams on site helping.
>
>Last year we used this same tracker to report 7 or 8 bikes that had
>brokendown and even had to airlift a guy out who broke his femur.
>
>By the way, the reason I'm using "emergency" mic-e packet is to make
>darned sure that the kenwood d700's running around mobile get everyone's
>attention.  Does anyone know if the d700 will beep for "priority" type
>packet?  What about xastir?
>
>Wes
>ai4px

------------------------------

aprssig mailing list
aprssig_at_lists.tapr.org
https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig

End of aprssig Digest, Vol 31, Issue 25



Read previous mail | Read next mail


 04.02.2026 18:46:39lGo back Go up