OpenBCM V1.13 (Linux)

Packet Radio Mailbox

DB0FHN

[JN59NK Nuernberg]

 Login: GUEST





  
ZL3AI  > APRDIG   04.02.03 10:06l 267 Lines 9833 Bytes #999 (0) @ WW
BID : 828-ZL3AI
Read: GUEST
Subj: TAPR Digest, Jan 30, 2/8
Path: DB0FHN<DB0RGB<DB0FSG<DB0GAP<DB0GPP<DB0LX<DB0RBS<DB0SEL<DB0ZDF<DB0GE<
      F6KFT<LX0PAC<LX0HST<HA3PG<KD4GBA<ZL2BAU<ZL3VML
Sent: 030203/0841Z @:ZL3VML.#80.NZL.OC #:58721 [Chch-NZ] FBB7.00i $:828-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To  : APRDIG@WW

Subject: APRS and Civil Air Patrol
From: Peter Devanney <pdevanney@sympatico.ca>
Date: Thu, 30 Jan 2003 10:11:34 -0500
X-Message-Number: 10

If there is someone on this list that is a member of the CAP and
knowledgable of the  CAP communication policies as they relate to APRS or
comms in general please email me off list. 

Thanks,

Peter
VA3YOW
pdevanney@sympatico.ca

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

Subject: Re: EMAIL
From: "Joe Della Barba" <joe@dellabarba.com>
Date: Thu, 30 Jan 2003 10:15:38 -0500
X-Message-Number: 11

Considering that you are all a technical group, passing the 35 (+ or -)
relatively easy multiple choice test to get licensed for the VHF and above
spectrum should be quite easy.
Sign all your buddies up!
73 de N3HGB
Joe

----- Original Message -----
From: "Gonzales Andy" <agonzales@arc.nasa.gov>
To: "TAPR APRS Special Interest Group" <aprssig@lists.tapr.org>
Sent: Wednesday, January 29, 2003 6:10 PM
Subject: [aprssig] EMAIL

>I am fascinated by the possibilities and how they might be useful for
>my project. Right now, anything we do in the RF world is under the
>supervision of a licensed HAM.
>--
>Andy Gonzales
>NASA / Ames Research Center
>Moffett Field, CA  94035-1000
>Bldg. N-244, Rm. 240
>
>MS 244-19
>agonzales@arc.nasa.gov
>650-604-0309

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

Subject: RE: New spec - working notes
From: Miller Scott Contr 30SCS/FTI <Scott.Miller@vandenberg.af.mil>
Date: Thu, 30 Jan 2003 16:51:56 -0000
X-Message-Number: 12

For the time being, yes, this would only be on backbones, but it's intended
to be usable throughout the whole system.  I'm still thinking about how
compatibility might be dealt with on 144.39.  Digis set up to handle this
format over a backbone could be configured to accept incoming traffic on
144.39 with the new format, and retransmit it in the old format.  That might
allow trackers and things to be implemented without breaking existing
clients.

I've also been thinking about the possibility of a small KISS-mode
translator that might be plugged into a TNC to provide this sort of
translation.  Someone who knows more about digi implementations could
probably figure out if this is feasible.  If it can be done cheaply, it'd
help the transition while you're waiting for TNC firmware to be updated.
I'm thinking a $5-10 PIC-based unit that could fit in a DB-25 connector
shell.

Here's another question for those with more AX.25 experience:  should a new
format continue to use UNPROTO, or should it have its own layer-3 protocol
designation?  After all, it IS a layer-3 protocol, it'd help distinguish it
from legacy traffic, and my understanding is that UNPROTO was only used for
compatibility with existing TNCs that didn't know anything about APRS.

But you can relax for now, Bob, any implementation is going to be strictly a
backbone thing for some time while the bugs are worked out.

Scott / N1VG

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

Subject: Input needed
From: Miller Scott Contr 30SCS/FTI <Scott.Miller@vandenberg.af.mil>
Date: Thu, 30 Jan 2003 17:14:11 -0000
X-Message-Number: 13

Some questions for the list regarding a new spec:

Should it continue to use UNPROTO or should it be a true layer 3 protocol?

Should station speeds be in km/hr or m/sec?
(Don't even think about MPH - the spec will be strictly SI units.)

What about wind speeds?

What precision should temperatures support?  (i.e. 1/10 degree, 1/100
degree)

Are maidenhead reports still used/needed?

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

Subject: GPS 111 pin outs
From: eboyett@pcsonline.com (Ed Boyett)
Date: Thu, 30 Jan 2003 12:44:02 -0500
X-Message-Number: 14

I have a Garmin GPS 111, does anyone have the pin outs for the DB9 on the
data/power cable? Looking to connect it to my D700 I just purchased.

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

Subject: Re: GPS Jammed by junk consumer electronics...
From: "JB Crafts" <jbcraft@adelphia.net>
Date: Thu, 30 Jan 2003 13:18:09 -0500
X-Message-Number: 15

I seem to recall from the archives deep in the back of my memory, that in
about 1978 or so, some one (Winegard perhaps) had a problem with installers
of mast mounted pre-amps. What was happening was the IN was being connected
to the OUT and thus radiating all over the place via the TV antenna.

This caused havoc with VHF/UHF Ham and Public Service agencies...

Could this be the event that is being discussed here?

Bob K8YS

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

Subject: WinAPRS-Deleting tracks
From: "Germino" <mgermino@inreach.com>
Date: Thu, 30 Jan 2003 10:29:11 -0800
X-Message-Number: 16

Is there an easy way to clear the tracks in WinAPRS, without clearing all
the stations?

Mike
73, AD6AA

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

Subject: RE: Input needed
From: Miller Scott Contr 30SCS/FTI <Scott.Miller@vandenberg.af.mil>
Date: Thu, 30 Jan 2003 18:53:20 -0000
X-Message-Number: 17

Another question:  I'm working on a Station Capabilities bitmap field.
It'll be probably 16 or 32 bits, and should provide simple yes/no flags for
capabilities.  IGATE/HF/UHF gateway capability will be a single bit, since
I've already defined another message type to list available gateway
networks.

Some example fields so far:

1 - Station has gateway capability
2 - Station is a mobile
3 - Has weather data
4 - Station is a satellite

What else should go here?  This doesn't have to cover every possible future
contingency - we can leave spare bits, and when those are used up we can
just define an 'extended capabilities' field with more bits.  This is for
information about what a station IS, or what it CAN DO, not what its status
is.  Things like emergency status or 'responding' and 'off-duty' messages
are going in seperate flags.

The document's getting big already, so I think I'll put it on a website and
whoever wants to work on it can check it out and provide input.  I'd still
like to get the input of the wider APRS community on issues like this,
though.

Scott / N1VG

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

Subject: Re: GPS Jammed by junk consumer electronics...
From: "Mark Fellhauer" <sparkfel@qwest.net>
Date: Thu, 30 Jan 2003 13:19:22 -0600
X-Message-Number: 18

At 12:18 PM 1/30/2003, JB Crafts wrote:

>Could this be the event that is being discussed here?

No.    If you'd read the links you'd see the antennas in question are units 
where the pre-amp is integrated into the antenna itself.   I and others 
have provided those links to the SIG.

Furthermore, there are a few people here who seem intent on blaming 
Winegard, when again the FCC and USCG have only identified, IN PRINT, 
antennas manufactured by and for Tandy/Radio Shack and Shakespeare that 
have been known to cause GPS fix failure or GPS innacuracies.  The title of 
this thread is "GPS Jammed by junk consumer electronics..." and not "I 
don't like Winegard..."

And, according to Shakespeare, who has issued a voluntary recall on certain 
antennas, states that the problem only exists in a few hundred 
units.   Winegard products, OTOH, have not been linked to GPS JAMMMING by 
the FCC or the US Coast Guard.   And there has only been anecdotal evidence 
that a particular current model of Winegard antenna MAY cause interference 
on frequencies of 400 to 500 MHz.   Any speculation by people on this SIG 
that Winegard products are causing a problem with GPS reception is just 
that - sheer speculation.   Winegard has not issued a recall on any of it's 
current products for interference to GPS reception nor have they been named 
by various federal agencies as causing or suspected as causing a problem.

Let's try to be accurate and fair.   And no, I don't for Winegard nor do I 
own any of their products.

73,

Mark
KC7BXS

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

Subject: RE: New spec - working notes
From: Bob Bruninga <bruninga@usna.edu>
Date: Thu, 30 Jan 2003 14:25:20 -0500 (EST)
X-Message-Number: 19

On Thu, 30 Jan 2003, Miller Scott Contr 30SCS/FTI wrote about this
totally new binary "APRS" specification that several people seem to be
working on:

>For the time being, yes, it would only be on backbones, but it's
>intended to be usable throughout the whole system.  I'm still thinking
>about compatibility ... on 144.39.  Digis... could... accept incoming
>traffic on 144.39 with the new format, and retransmit it in the old
>format.

Hummh... Sounds like that would DOUBLE the load on a system that is
already overladed by a factor of 10 in some areas...?

>also thinking about... a small KISS-mode translator that might be
>plugged into a TNC to provide this sort of translation.

I guess I dont know what problem it is that you are trying to solve with
a whole new "APRS" protocol?
The big problem with APRS is total overload on the national user channel,
and I dont see that any of that is a significant "protocol" problem.  It
is more of a user  education, digipeater set-up, backbone design, Internet
interface problem...

>Here's another question for those with more AX.25 experience:  should a
>new format continue to use UNPROTO, or should it have its own layer-3
>protocol designation?  After all, it IS a layer-3 protocol, it'd help
>distinguish it from legacy traffic, and my understanding is that UNPROTO
>was only used for compatibility with existing TNCs that didn't know
>anything about APRS.

I'm not meaning to squish any volunteer initiatives, but I'm not sure what
problem you are trying to solve?

Bob

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



Read previous mail | Read next mail


 16.11.2026 06:50:48lGo back Go up