From owner-freebsd-multimedia@FreeBSD.ORG Sat Mar 17 08:07:10 2007 Return-Path: X-Original-To: freebsd-multimedia@freebsd.org Delivered-To: freebsd-multimedia@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9124E16A403 for ; Sat, 17 Mar 2007 08:07:10 +0000 (UTC) (envelope-from akm@theinternet.com.au) Received: from mail25.syd.optusnet.com.au (mail25.syd.optusnet.com.au [211.29.133.166]) by mx1.freebsd.org (Postfix) with ESMTP id 2D39E13C44B for ; Sat, 17 Mar 2007 08:07:09 +0000 (UTC) (envelope-from akm@theinternet.com.au) Received: from camelot.theinternet.com.au (c211-30-133-243.carlnfd4.nsw.optusnet.com.au [211.30.133.243]) by mail25.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id l2H872Tw031612; Sat, 17 Mar 2007 19:07:04 +1100 Received: by camelot.theinternet.com.au (Postfix, from userid 1000) id CC6106246; Sat, 17 Mar 2007 19:07:01 +1100 (EST) Date: Sat, 17 Mar 2007 19:07:01 +1100 From: Andrew Milton To: Joe Auty Message-ID: <20070317080701.GI11506@camelot.theinternet.com.au> Mail-Followup-To: Joe Auty , Torfinn Ingolfsen , freebsd-multimedia@freebsd.org References: <45F77267.9080403@netmusician.org> <20070314054117.GB6688@wantadilla.lemis.com> <7BADB2D8968E702424EAE969@ganymede.hub.org> <45F88A52.7000809@netmusician.org> <20070315080854.5232bb9b.torfinn.ingolfsen@broadpark.no> <20070315095424.GE11506@camelot.theinternet.com.au> <45FABCE8.20400@netmusician.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <45FABCE8.20400@netmusician.org> User-Agent: Mutt/1.5.9i Cc: freebsd-multimedia@freebsd.org Subject: Re: LIRC guide for FreeBSD X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Mar 2007 08:07:10 -0000 +-------[ Joe Auty ]---------------------- | | Cool, so this is just a matter of software configuration then? You need some strobing code.. this is assuming you don't have something neat like a niveus IR blaster. | Any | ideas how I can setup LIRC to do this? For your device that you want to send to, you need to know two things (other than the codes). Pulse width, and the carrier frequency. The pulse usually consists of an on then an off period, so a '1' is an on/off period, and a '0' is an all off period. +---+ | | -+ +---+-------- | | | | | |- 1 -|- 0 -| OK, now inside the part of the pulse that's high, you need to strobe the correct control line at the carrier frequency. These are normally in the range of 37Khz - 40Khz for consumer infrared. You need to find out the remote codes for your device, there's plenty of remote sites out there that have CCF files or whatever (if there's no LIRC config that has them), that should give you what you need to send. Once you have that you simply set up your lirc config to run your 'send' app when ever it receives your incoming button and tell it to send the write code. You can also then use this to directly send commands to it etc from the commandline or whatever. I used to have code to handle all this (as well as an IR receiver app that had dvico USB receiver code, it had a LIRC output mode, so that applications that used the LIRC lib could work with it). I had a look on a few DLT cartridges, but, I can't find it. I basically had learnt codes for heaps of remotes that I had lying around, TV Remotes, DVD Remotes, XBOX, PS2. I guess I should make a better effort to find it. It's not really rocket science to build a receiver / sender system. The "hard" problem is if you want to learn codes from remotes in some sane fashion. -- Andrew Milton akm@theinternet.com.au