Path: ...!news.mixmin.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Don Y Newsgroups: sci.electronics.design Subject: Re: Ir remotes Date: Mon, 20 May 2024 00:15:52 -0700 Organization: A noiseless patient Spider Lines: 19 Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Date: Mon, 20 May 2024 09:15:55 +0200 (CEST) Injection-Info: dont-email.me; posting-host="5d80f1dc6dc80e940061abf9488d5484"; logging-data="4071826"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19lWkJA5Uu6I5scC4cQqCf5" User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.2.2 Cancel-Lock: sha1:u2jBg+kJBvWzOuLueuT7yrsgcSI= In-Reply-To: Content-Language: en-US Bytes: 1871 On 5/20/2024 12:01 AM, Don Y wrote: > My understanding is that Ir remotes modulate an Ir "carrier" signal > in a particular pattern to express a particular "code" corresponding to > the key pressed/held. > > And, that different "chipsets" use different carriers and encodings. > > Is there a front-end that is tuned to the particular carrier > in the receiver?  Or, is all of this done "digitally"? > > I.e., with a fast-enough (Ir) photodetector, should I be able to > decode ANY signal from ANY "remote"? And, before anyone mentions the obvious, I've already looked at lircd which is the reason behind this post; why do they claim they can handle ALMOST all remotes? Is this a limitation of their hardware implementation? Or, timing problems in the way they try to process the raw video signal?