Received: from PCH.mit.edu (18.7.21.50) by mail.efplus.com (192.168.0.8) with Microsoft SMTP Server (TLS) id 8.3.485.1; Mon, 18 Jan 2021 15:28:29 -0800 Received: from PCH.MIT.EDU (localhost.localdomain [127.0.0.1]) by PCH.mit.edu (8.14.7/8.12.8) with ESMTP id 10INIVTh006975; Mon, 18 Jan 2021 18:19:19 -0500 Received: from outgoing-exchange-7.mit.edu (OUTGOING-EXCHANGE-7.MIT.EDU [18.9.28.58]) by PCH.mit.edu (8.14.7/8.12.8) with ESMTP id 10INIUtG006971 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for ; Mon, 18 Jan 2021 18:18:30 -0500 Received: from oc11exedge1.exchange.mit.edu (OC11EXEDGE1.EXCHANGE.MIT.EDU [18.9.3.17]) by outgoing-exchange-7.mit.edu (8.14.7/8.12.4) with ESMTP id 10INI4Wb025731 for ; Mon, 18 Jan 2021 18:18:30 -0500 Received: from w92expo16.exchange.mit.edu (18.7.74.70) by oc11exedge1.exchange.mit.edu (18.9.3.17) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Mon, 18 Jan 2021 18:18:16 -0500 Received: from oc11exhyb6.exchange.mit.edu (18.9.1.111) by w92expo16.exchange.mit.edu (18.7.74.70) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Mon, 18 Jan 2021 18:18:24 -0500 Received: from NAM10-MW2-obe.outbound.protection.outlook.com (104.47.55.102) by oc11exhyb6.exchange.mit.edu (18.9.1.111) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Mon, 18 Jan 2021 18:18:24 -0500 Received: from BN6PR03CA0053.namprd03.prod.outlook.com (2603:10b6:404:4c::15) by BY5PR01MB5956.prod.exchangelabs.com (2603:10b6:a03:1b9::24) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3763.10; Mon, 18 Jan 2021 23:18:21 +0000 Received: from BN8NAM11FT020.eop-nam11.prod.protection.outlook.com (2603:10b6:404:4c:cafe::fe) by BN6PR03CA0053.outlook.office365.com (2603:10b6:404:4c::15) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3763.10 via Frontend Transport; Mon, 18 Jan 2021 23:18:21 +0000 Received: from mail-lj1-f182.google.com (209.85.208.182) by BN8NAM11FT020.mail.protection.outlook.com (10.13.176.223) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3763.12 via Frontend Transport; Mon, 18 Jan 2021 23:18:21 +0000 Received: by mail-lj1-f182.google.com with SMTP id f11so19912804ljm.8 for ; Mon, 18 Jan 2021 15:18:21 -0800 (PST) From: Sean Breheny To: Microcontroller discussion list - Public. Sender: "piclist-bounces@mit.edu" Date: Mon, 18 Jan 2021 15:18:09 -0800 Subject: Re: [EE] Lossy bandwidth compression with analog circutry? Thread-Topic: [EE] Lossy bandwidth compression with analog circutry? Thread-Index: Adbt8aFuMwy04V6QQ3WMabrsrSA9qw== Message-ID: References: List-Help: List-Subscribe: , List-Unsubscribe: , In-Reply-To: Reply-To: Microcontroller discussion list - Public. Accept-Language: en-US X-MS-Exchange-Organization-AuthAs: Anonymous X-MS-Exchange-Organization-AuthSource: TS500.efplus4.local X-MS-Has-Attach: X-Auto-Response-Suppress: All 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 gmail.com designates 209.85.208.182 as permitted sender) receiver=protection.outlook.com; client-ip=209.85.208.182; helo=mail-lj1-f182.google.com; dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cornell.edu; s=g.20171207; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=ZVabX9hjtvcrPcqF7oaT5FWPKOxVu5vNvWinsxwsvHs=; b=iN1FIicHeZkk+4IqTBCM9M54ecVyE67UidLmHC9MNi3rQJj+kyyeRlPF8jQnZ9qXK2 6ePfMiS3bTwMbb4GYG6wSz7aDdvJ/h0hrmqa76EMxnuIdpEHPQBsvtz7lT+f5nAT3+K7 MeAD1TbGHUmRg0q9CBkQdEunIbLdewWeD4kpXbd7OSo+B9VCHge3LMk3vP/j3A3YfYw5 w5py+jwzVqcuLf/pdkAbZt4bTca2+tiqjwbfIoczDK8tLrfnU1pOxGPgBCqKmaKfpLtp RCL5BpH/w8C64URRfEhteOgGBGrdfy8UTO/v9Btx8Jb+NTlZVwV4AtiF3q1rsBLDHqDz Y3iQ== authentication-results: spf=pass (sender IP is 209.85.208.182) smtp.mailfrom=gmail.com; mit.edu; dkim=pass (signature was verified) header.d=cornell.edu; mit.edu; dmarc=pass action=none header.from=cornell.edu; errors-to: piclist-bounces@mit.edu list-id: "Microcontroller discussion list - Public." list-post: x-beenthere: piclist@mit.edu x-mailman-version: 2.1.6 x-received: by 2002:a2e:7212:: with SMTP id n18mr696552ljc.399.1611011900016; Mon, 18 Jan 2021 15:18:20 -0800 (PST) x-topics: [EE] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Hi Jason, There are many ways to do what you are asking. One way (maybe not the most practical) is to use a length of highly-dispersive transmission line (or dispersive delay line or SAW structure). This would convert frequency-domain into time-domain (in other words, if you put a 1 millisecond burst of the entire radio spectrum in one end, you'd get a longer (let's say 10 milliseconds) burst out the other end where the lower frequencies would come out first and the higher frequencies later, or vice-versa. You could then use a demodulator to produce a power vs frequency output which was represented as a voltage vs time. Some old radars did things like this and so did early spectrum analyzers. The section of transmission line needed would be very long - probably at least 10s of meters even when made of very special ultra-low velocity factor materials. Of course another, simpler way would be a wideband tunable filter which you sweep across the spectrum. This would produce a similar output (frequency vs time). This may be easier to do if you first upconvert your 0-100MHz to, say, 1 GHz to 1.1GHz and then use a YIG-tuned filter (YTF) or dielectric resonator filter. Could also be done with clever use of a comb filter and undersampling. In other words, you intentionally produce a highly-aliased version of the signal but preceed the sampler with a comb filter which selects out several narrow ranges of frequency so that the aliased copies don't overlap in the frequency domain. Tough to make sure everything lines up with no gaps or unintentional overlaps. All of the above, though, would be harder to implement today than a digital solution. They would require careful tweaking and quite possibly temperature compensation to make them workable. I've seen 1970s microwave test gear where a large part of the system consisted of arrays of op-amps and multi-turn pots to create complex calibration curves (e.g. for linearizing the tuning of a VCO) in an analog circuit, which all had to be hand-tuned for each unit at the factory. Sean On Sat, Jan 16, 2021 at 6:17 PM Jason White wrote: > > Hi everyone, > > Is it possible to "compress" the bandwidth/frequency spectrum of a signal > using an analog circuit? (with or without loss of information) For exampl= e > 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. > > 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. > > Are there other ways? > -- > Jason White > -- > http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive > View/change your membership options at > http://mailman.mit.edu/mailman/listinfo/piclist --=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 .