| |
ZL3AI > APRDIG 03.02.03 10:04l 259 Lines 9583 Bytes #999 (0) @ WW
BID : 815-ZL3AI
Read: GUEST
Subj: TAPR Digest, Jan 29, 2/6
Path: DB0FHN<DB0ZWI<DB0HST<ON0DXC<WA7V<RZ6HXA<SP7MGD<VK3KAY<VK3TE<VK4TUB<
ZL2BAU<ZL3VML
Sent: 030202/0859Z @:ZL3VML.#80.NZL.OC #:58657 [Chch-NZ] FBB7.00i $:815-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
Subject: Re: GPS Jammed by junk consumer electronics...
From: Gerry Creager <gerry.creager@tamu.edu>
Date: Wed, 29 Jan 2003 07:39:01 -0600
X-Message-Number: 11
And, mostlikely, labelled, "Wingard." These things have provided a lot
of t-hunting experience to me and friends in the past, when they start
jamming UHF repeater systems. There's virtually no doubt they will
radiate at L1 AND L2.
I don't make a statement like this very often, but I'd like to see the
FCC go to a type-acceptance requirement for TV preamps. The cheap
designs implemented now are evil and dirty.
Gerry
----------------------------------------------------------------------
Subject: Bad Mic-E translation
From: "Ramon F. Kolb" <ramon@ieee.org>
Date: Wed, 29 Jan 2003 09:53:46 -0500
X-Message-Number: 12
Sigh.... another one....
PA3EUG-9>APRS,TCPIP,PA3EUG*,qAS,N1UEC:
@291418z4214.66NW07101.48W/034/000/Mic-E/M2/In Service>/W1/PA3EUG, Red
VW Golf, Ramon - home QTH Boston, MA
Would it be N1UEC who does the translation? This puts my car about 20
miles south of where I am...
I heard that certain versions of WinAPRS do these kind of things. Since
I'm not a WinAPRS user, could someone please tell me:
1) which version(s) is/are affected
2) how do you switch off the Mic-E translation in this/these version?
Just so I can help the operator get his station in getter shape...
Thanks, 73s,
--Ramon
Ramon F. Kolb, W1/PA3EUG, Boston, MA, USA [FN42KI]
ICQ:77117744; MSNMGR:legalalien30@hotmail.com
http://kolb.webhop.org
----------------------------------------------------------------------
[commercial content deleted]
----------------------------------------------------------------------
Subject: RE: Homemade GPS jammers raise concerns
From: larry Also <larrytooalso@yahoo.com>
Date: Wed, 29 Jan 2003 08:37:29 -0800 (PST)
X-Message-Number: 14
And you can buy one from eastern europe, I'm told.
Darryl Smith <Darryl@radio-active.net.au> wrote:
Unfortunately the articles in the magazines are not that accurate. They
have overestimated the cost by about 10x...
All that is needed for a GPS Jammer is a MMIC liks a MAR-6 from
Minicircuits, some CoAx and a power source... That is all... Thanks to
the link budget of GPS...
Darryl
----------------------------------------------------------------------
Subject: Re: GPS Jammed by junk consumer electronics...
From: "Mark Fellhauer" <sparkfel@qwest.net>
Date: Wed, 29 Jan 2003 11:18:47 -0600
X-Message-Number: 15
At 07:39 AM 1/29/03, Gerry Creager wrote:
>And, mostlikely, labelled, "Wingard." These things have provided a lot of
>t-hunting experience to me and friends in the past, when they start
>jamming UHF repeater systems. There's virtually no doubt they will
>radiate at L1 AND L2.
>
>I don't make a statement like this very often, but I'd like to see the FCC
>go to a type-acceptance requirement for TV preamps. The cheap designs
>implemented now are evil and dirty.
I believe the offending brand was Shakespeare. They make a line of marine
TV antennas and I believe I saw something on their web site about a recall,
due to this problem.
73,
Mark
KC7BXS
----------------------------------------------------------------------
Subject: RE: Homemade GPS jammers raise concerns
From: "Mark Fellhauer" <sparkfel@qwest.net>
Date: Wed, 29 Jan 2003 11:21:58 -0600
X-Message-Number: 16
At 10:37 AM 1/29/03, larry Also wrote:
>All that is needed for a GPS Jammer is a MMIC liks a MAR-6 from
>Minicircuits, some CoAx and a power source... That is all... Thanks to
>the link budget of GPS...
Or apparently you can just buy a marine TV antenna with a built-in
pre-amp...
73,
Mark
KC7BXS
----------------------------------------------------------------------
Subject: Re: GPS Jammed by junk consumer electronics...
From: k5qq@juno.com
Date: Wed, 29 Jan 2003 10:50:52 -0700
X-Message-Number: 17
On Wed, 29 Jan 2003 11:18:47 -0600 "Mark Fellhauer" <sparkfel@qwest.net>
writes:
>At 07:39 AM 1/29/03, Gerry Creager wrote:
>
>>And, mostlikely, labelled, "Wingard." These things have provided a
>>lot of t-hunting experience to me and friends in the past, when they start
>>jamming UHF repeater systems.
>I believe the offending brand was Shakespeare. They make a line of
>marine TV antennas and I believe I saw something on their web site about a
>recall, due to this problem.
>
>73,
>
>Mark
>KC7BXS
I have not seen anything about Shakespeare but the following from the
ARRL awhile back had the Winegard units as the culprits as well as
referencing their recall program.
-----------
Oscillating RV Preamplifers
The ARRL Letter, Vol 20, No 7
* Oscillating preamps generate rash of interference complaints: The FCC
reports it's gotten word of a rash of interference problems created by
oscillating preamplifiers built into Winegard TV antennas used primarily on
RVs, campers and motor homes. The oscillations generally appear in the
400-500 MHz range--and sometimes elsewhere--and have caused interference
problems to public safety and Amateur Radio operation at distances of
several miles away. The FCC's Gary Hendrickson says Winegard has
acknowledged the problem and estimates that there may be as many as 40,000
defective units in the field, which it has agreed to replace at no charge.
Owners, RV dealers or repair shops that might have new, but defective,
units in stock should contact the factory at Burlington, Iowa, at
319-754-0600.
-------------
Jim
----------------------------------------------------------------------
Subject: Future spec
From: Miller Scott Contr 30SCS/FTI <Scott.Miller@vandenberg.af.mil>
Date: Wed, 29 Jan 2003 18:47:31 -0000
X-Message-Number: 18
Ok, I'm not even going to touch the user interface spec... for my reasons,
see the Dilbert strip about the effects of user interfaces designed by
engineers. =]
As people have pointed out before, if there's going to be a new message
spec, it'll have to start out on APRS-IS or a UHF backbone, or some other
APRS adjunct. From there, if it works, it'll eventually make the transition
to general on-air use.
A new spec should be independent of the underlying transport (AX.25, TCP,
UDP), not using the AX.25 address fields for carrying anything but
addressing information. All data is packaged in simple atomic message
units, consisting of a message ID byte, length byte, and payload.
Everything is in pure 8-bit binary, with a single data type standard for all
primitives - e.g., all positions in WGS84 decimal degrees, represented as
IEEE single-precision floating point. These atomic message units will be
simple building blocks for things like position, timestamp, course/speed,
comments, URLs, P/H/G, Wind speed/direction, supported gateways advertised
(APRS-IS, UHF, etc), and so on. No more 'position with timestamp',
'position without timestamp', 'position with timestamp, course, speed, spam,
spam, antenna gain, and spam' message formats. Over backbones the message
groups might be encapsulated in an 'envelope' layer that would carry the
same sort of origin and routing information as the AX.25 src/dest/digi
fields.
Message parsing would be a piece of cake. Fixed-length messages would be
directly compatible with C-style data structures. The length byte would let
a simple (or outdated) client skip over any message formats it doesn't know.
New messages could be added very easily, with a subset reserved for
experimental use. If I wanted to add a Geiger counter reading to my tracker
(something I'm working on for another project), I'd just build a new message
format with an experimental ID. It'd be passed through the system, ignored
by anything that didn't care about it, and logged in the databases or parsed
in real time by something like my APRSListener service.
The next step would be adding a control layer to handle things like
announcing to APRS-IS servers or UHF backbone sites what messages you're
interested in. I'll leave that one open for now, but I think it's a
distinct function from the message spec. Like the relationship between ICMP
and TCP, for example.
This applies equally to on-air, RF backbone, satellite, and APRS-IS
operation, so I'm posting it here for everyone's input rather than to the
backbone list or spec list.
To get this going, we'd need to first:
- Define message units to handle all existing APRS message components
- Choose standard units and number formats
I'm ready to start coding now. Who's with me, and where should we take the
discussion? Here, spec list, backbone spec list, or a new forum? I don't
mean to seem hasty, but as people keep pointing out, nothing ever gets done
unless someone just goes out and does it.
Scott / N1VG
----------------------------------------------------------------------
Subject: Re: Future spec
From: James Jefferson <jjeffers@aprsworld.net>
Date: Wed, 29 Jan 2003 12:58:33 -0600
X-Message-Number: 19
>I'm ready to start coding now. Who's with me, and where should we take the
>discussion? Here, spec list, backbone spec list, or a new forum? I don't
>mean to seem hasty, but as people keep pointing out, nothing ever gets done
>unless someone just goes out and does it.
Scott,
I agree with the ideas you proposed. They make a lot of sense. Having a
universal data transport mechanism (internet, UHF 9600, whatever) with
intelligent gateways that could convert the binary data to whatever is
needed would improve upon many of the problems we are having now.
All for it, Scott!
-Jim
----------------------------------------------------------------------
Read previous mail | Read next mail
| |