OpenBCM V1.13 (Linux)

Packet Radio Mailbox

DB0FHN

[JN59NK Nuernberg]

 Login: GUEST





  
ZL3AI  > APRDIG   15.12.03 21:09l 268 Lines 9522 Bytes #999 (0) @ WW
BID : 2489-ZL3AI
Read: GUEST
Subj: TAPR Digest, Dec 12, 2/3
Path: DB0FHN<DB0FOR<DB0SIF<DB0MRW<DB0RGB<OK0PPL<DB0RES<ON0AR<7M3TJZ<SP7MGD<
      ZL2TZE<ZL3VML
Sent: 031215/1844Z @:ZL3VML.#80.NZL.OC #:14704 [Chch-NZ] FBB7.00i $:2489-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To  : APRDIG@WW

Subject: Re: Using PSK31
From: "JBCrafts" <jbcraft@adelphia.net>
Date: Fri, 12 Dec 2003 10:42:23 -0500
X-Message-Number: 8

Bob said:
But the PSK-31 crowd is so anti-APRS that they cannot see how simple this
is and how it does NOTHING different thanwaht they are already doing, but
just uses a satndard GRID notation so the receiving software can capture
it...

Bob, WB4APR

HUH??? I do not think that the PSK31 crowd is ANTI-APRS (I am a dedicated
PSK31 user AND an APRS user!). I think that what you  MEANT to say was that
PSK31 users are ANTI-UNATTENDED PACTOR BBS. Pactor BBS's that pop up on the
air with listening to the frequency first...

Bob K8YS

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

Subject: Re: Using PSK31
From: Bob Bruninga <bruninga@usna.edu>
Date: Fri, 12 Dec 2003 11:47:46 -0500 (EST)
X-Message-Number: 9

On Fri, 12 Dec 2003, JBCrafts wrote:

>Bob said:
>But the PSK-31 crowd is so anti-APRS that they cannot see how simple this
>is and how it does NOTHING different thanwaht they are already doing, but
>just uses a satndard GRID notation so the receiving software can capture
>it...
>
>Bob, WB4APR
>
>HUH??? I do not think that the PSK31 crowd is ANTI-APRS (I am a dedicated
>PSK31 user AND an APRS user!). I think that what you  MEANT to say was that
>PSK31 users are ANTI-UNATTENDED PACTOR BBS. Pactor BBS's that pop up on the
>air with listening to the frequency first...

Yes, I too abhor any unattended ops on the PSK-31 band segments and I am
all for Human communications (Remember, that's what APRS was supposed to
be, a tactical-real-time.... etc (which means a HUMAN operator) <GRIN>...
In that sense we share the same frustrations...

Bob

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

Subject: Re: Using PSK31
From: "Scott Miller" <scott@3xf.com>
Date: Fri, 12 Dec 2003 09:04:39 -0800
X-Message-Number: 10

Isn't there a PSK31 relative that's intended for binary - i.e., that doesn't
use varicode?

OpenTrac would get you a position with excellent resolution in 10 bytes, but
really you'd probably be better off developing a special-purpose frame to
include a CRC (or FEC) and do away with the OpenTrac element header
overhead.  6 bytes can still give you position down to < 10 feet, I think.
Even four would be more than enough for propagation study purposes.

With ID and everything I'm sure you could fit a complete report into 20
bytes.  Say 6 seconds on-air time?  That still seems pretty slow.

Scott
N1VG

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

Subject: Holiday Traveling = 144.39 CTCSS 100
From: Bob Bruninga <bruninga@usna.edu>
Date: Fri, 12 Dec 2003 12:42:38 -0500 (EST)
X-Message-Number: 11

Remember, during holiday travels, your BEST chance of hearing
a fellow traveler DIRECT, is monitoring 144.39 CTCSS 100.

On the interstates, we typically pass another ham about once every 20
minutes, yet may go for hours without finding a QSO on 146.52.

144.39 CTCSS 100 works far better than listening to 146.52, because on 52,
someone has  to be calling CQ every 2 minutes so that there is any chance
of someone in range hearing them.  Most dont, thus many QSO's are lost.

Think of 144.39 as a RADAR ping.  The vast majority of APRS mobile
operators are pinging away once every minute or so with a PL 100 packet
position report.  This serves as an automatic "in-range" signal probe.
But, not only are they transmitting with PL 100, they also have their
speakers MUTED with CTCSS 100 so that they can then HEAR a voice call from
ANYONE that calls them using PL 100.

Thus, if you hear a PL 100 signal on 144.39, you know the following:

1) He is in SIMPLEX range
2) He is LISTENING with his speaker for a voice call.

In APRS lingo, we call this "VOICE ALERT" since we are all driving around
with one radio permanently on 144.39 anyway, we may as well use its
speaker and "pings" on those rare occassions when someone wants to get our
attention for voice by using PL 100.

CAUTION! WARNING!!!

1)  VOICE ALERT is only for CALLING or ALERTING the other station by
voice to QSY to your chosen voice frequency (usually 52)... Do not QSO
on 144.39 or you are interferring with other traffic.

2)  When you call someone on 144.39 PL 100, you MUST say "voice Alert" or
he won't know you are on 144.39.  Voice Alert calls are rare, and without
giving him a clue, he will assume your voice came on his other band... and
he will answer you there, but you dont know what other band he is on, so
you dont hear him and we have another "two-cars-passing-in-the-night"...
with no communications established.


SO, Even if you never have used APRS, don't overlook this simple "radar
detector" for travelers in simplex range.  It works.  Maybe only a few
times a day on a long trip, but it works better than waiting for someone
within 5 miles of you to call CQ on 52...

Happy Holidays...

de WB4APR, Bob

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

Subject: Re: Holiday Traveling = 144.39 CTCSS 100
From: wes@johnston.net
Date: Fri, 12 Dec 2003 12:57:48 -0500 (EST)
X-Message-Number: 12

Around here we jokingly refer to voice alert as "the hailing frequency"
(from star trek).

Wes

ham callsign: kd4rdb
find me: http://wesvan.zapto.org

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

Subject: Re: Holiday Traveling = 144.39 CTCSS 100
From: K8DNE <wh.reynolds@verizon.net>
Date: Fri, 12 Dec 2003 12:11:13 -0600
X-Message-Number: 13

And then there is the "nerd" who runs the digi near Siloam Springs, AR, 
who has the 100.0hz tone on the output of his digi.  <grins>

73 and be safe y'all.
bill

-- 
W. H. (Bill) Reynolds,  K8DNE
A.R.R.L. Liaison F.C.C. Examiner
8821 Willowbrook Dr.
Rowlett, TX  75088-4614
Phone:  972-475-3854
E-Mail = <wh.reynolds@verizon.net>
Rowlett, TX RACES Radio Officer, Unit 801R

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

Subject: Re: Holiday Traveling = 144.39 CTCSS 100
From: Earl Needham <needhame1@yucca.net>
Date: Fri, 12 Dec 2003 11:21:58 -0700
X-Message-Number: 14

At 12:11 PM 12/12/2003 -0600, K8DNE wrote:
>And then there is the "nerd" who runs the digi near Siloam Springs, AR, 
>who has the 100.0hz tone on the output of his digi.  <grins>

He ain't the only one, either!  There seems to be a GROUP of digis near
Dallas that also have 100 Hz PL on their signals, and some more around the
country.  I found some when I was on the road, but can't remember them all.
I wonder if somehow a rumor got started that mandated 100 Hz for ALL of
APRS?  Incorrect, of course...

Earl

Earl Needham, KD5XB, Clovis, New Mexico  DM84jk
KD5XB-2>APW251,PCSAT-1%:=3425.83N/10313.55W-PHG7150/WinAPRS 2.5.1 
-EARL_CLOVIS -251-<630>
SETI@Home: 11150WU/7.23yrs!

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

Subject: Re: Tracker behavior with invalid GPS
From: "Scott Miller" <scott@opentrac.org>
Date: Fri, 12 Dec 2003 13:50:25 -0800
X-Message-Number: 15

Discussion on the EOSS list has added a couple more potential options...

- Beacon last good fix at exponentially decaying rate
- Switch on DF beacon for x seconds after loss of signal for y minutes

Other ideas?  I'm not saying I'll implement all of them, but I'll try to do
whatever's practical.

Scott
N1VG

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

Subject: Re: Holiday Traveling = 144.39 CTCSS 100
From: Richard Garcia <k4gps@bellsouth.net>
Date: 12 Dec 2003 18:05:50 -0500
X-Message-Number: 16

OK I am game...since my Kenwood has died on VHF I am programming up a
Motorola Maxtrac or GM300 whatever I grab out of the closet and entering
APRS, .52 and all the NWS frequencies. With repeater directories almost
worthless (90% paper repeaters) and PL tones changing the ability to
pre-program a radio for a 1100 mile trip is impossible.

I am going to wire up the motorola for the TNC this weekend but if I
enter a PL on RX of 100.0 then how will the DCD work properly ? 

I guess if I set a PL of 100.0 on transmit then if someone on the road
hears my packet they will have an idea that I know of the "hailing
channel" principal and try to call me back with a PL of 100.

I just don't understand how if I set RX PL to 100 how the DCD will work.

Rich

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

Subject: Re: Holiday Traveling = 144.39 CTCSS 100
From: Bob Bruninga <bruninga@usna.edu>
Date: Fri, 12 Dec 2003 19:03:55 -0500 (EST)
X-Message-Number: 17

On 12 Dec 2003, Richard Garcia wrote:

>I am going to wire up the motorola for the TNC this weekend but if I
>enter a PL on RX of 100.0 then how will the DCD work properly ?

You can only run Voice Alert if the TNC is connected to the discriminator
PRIOR to the Squelch or CTCSS circuit.  Then the TNC is always listening,
but the SPEAKER is muted...

>I guess if I set a PL of 100.0 on transmit then if someone on the road
>hears my packet they will have an idea that I know of the "hailing
>channel" principal and try to call me back with a PL of 100.

Yes, but DONT send PL100 if you arent *listening* because it is violating
the purpose.  Only send PL 100 if you are also listening and the volumne
is up so you can hear it...
>
>I just don't understand how if I set RX PL to 100 how the DCD will work.

You are right.   But it just depends on where y ou hook  up the TNC...

Bob

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




Read previous mail | Read next mail


 20.10.2026 22:14:44lGo back Go up