From: Alan Pearce <kiwiantipodean@googlemail.com>
To: "piclist@mit.edu" <piclist@mit.edu>
Sender: "piclist-bounces@mit.edu" <piclist-bounces@mit.edu>
Date: Sat, 16 Jan 2021 16:09:41 -0800
Subject: Re: [EE] Lossy bandwidth compression with analog circutry?
Thread-Topic: [EE] Lossy bandwidth compression with analog circutry?
Thread-Index: AdbsZlK1LtvV6DECRO2ED6JCV8M6CQ==
Message-ID: <20210117000941.3f40efcc@raspberry>
References:
 <CAOFvGD7f2=o8fKR7HBdC1K-DinziwzASmE4=JKFjDv8MnfK4CQ@mail.gmail.com>
In-Reply-To:
 <CAOFvGD7f2=o8fKR7HBdC1K-DinziwzASmE4=JKFjDv8MnfK4CQ@mail.gmail.com>
Reply-To: Microcontroller discussion list - Public. <piclist@mit.edu>
Accept-Language: en-US
X-MS-Exchange-Organization-SenderIdResult: Pass
X-MS-Exchange-Organization-PRD: mit.edu
X-MS-TNEF-Correlator:
received-spf: Pass (protection.outlook.com: domain of googlemail.com
	designates 209.85.221.44 as permitted sender)
	receiver=protection.outlook.com; client-ip=209.85.221.44;
	helo=mail-wr1-f44.google.com;
dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed;	d=googlemail.com;
 s=20161025;
	h=from:date:to:subject:message-id:in-reply-to:references:organization
	:mime-version:content-transfer-encoding;
	bh=ADXK0lhdCf2AJMhfx5qNQXPbiYaO2eMDa+UTXq/HJ48=;
	b=KFJgNz3AcMAChQ1SGDRoj2Va4KprY/RAbyVaJBlST3ibcCt2FMFw55mVTe9xJtpYWT
	KK7vhvnhQBKH6SphoC+QFpKgz3y4kB4Ynkkyy0PsG+lASYm6sCdTHtB1ry2+A/CkL5pP
	AMT195Wk5ifaWi6pn6ey080pzB4PfYy3SmRnTC/YM5MhU+V6U7EGeq1c7rfqhf2X+3Xh
	zAzne/pSqlGrcViKiQ3/xw+9M1ZUwfcpw/e0Ec2GouF8GDNQ3eND1HAHXvz5w7BcGSK4
	WIsE55SbEtbHCaOO+JJVZ85n/G9oHFSezW9R00diKCSCLr+9LOiz5XZV1YHSZ0K+G5Tu	Nldg==
authentication-results: spf=pass (sender IP is 209.85.221.44)
	smtp.mailfrom=googlemail.com; mit.edu;	dkim=pass (signature was verified)
	header.d=googlemail.com;mit.edu; dmarc=pass action=none
	header.from=googlemail.com;
errors-to: piclist-bounces@mit.edu
list-id: "Microcontroller discussion list - Public." <piclist.mit.edu>
list-post: <mailto:piclist@mit.edu>
x-beenthere: piclist@mit.edu
x-mailman-version: 2.1.6
x-received: by 2002:adf:a34d:: with SMTP id
 d13mr19822301wrb.194.1610842183711;	Sat, 16 Jan 2021 16:09:43 -0800 (PST)
x-topics: [EE]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Isn't this what Software Defined Radio does?
In effect you can look at the frequency binning and select the
bandwidth you want to monitor. It doesn't compress the frequency range,
but does allow automatic monitoring.

Have a prowl around the KiwiSDR web site http://kiwisdr.com/ and see
what add-ons people have added to process the frequency binning (some
of them take you to external sites). KiwiSDR only does it for 0-30MHz,
but I believe there are others that can do it for higher frequencies
(the main limitation is the ADC).


On Sat, 16 Jan 2021 18:14:54 -0500
Jason White <whitewaterssoftwareinfo@gmail.com> wrote:

> Hi everyone,
>=20
> Is it possible to "compress" the bandwidth/frequency spectrum of a
> signal using an analog circuit? (with or without loss of information)
> For example taking 100Mhz of radio spectrum and shrinking it
> (preferably without involvement of digital electronics) into a 1Mhz
> span for monitoring purposes. Specifically to look at received power
> vs frequency vs time in order to identify approximately when and at
> what frequency transmissions occur at over a long period.
>=20
> I think the closest equivalent of this would be having a receiver scan
> "quickly" and looking at each "slice."
> A second might be to do some sort of "frequency binning" in the analog
> domain.
>=20
> Are there other ways?

--=20
http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.