>From: lirc@... (Christoph Bartelmus)
>Subject: Re: MyHD serial IR Receiver - MyIRC
>Date: 04 Jan 2006 23:03:00 +0100
>Received: from lists-outbound.sourceforge.net ([18.104.22.168]) by
>bay0-mc9-f11.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 4
>Jan 2006 14:05:03 -0800
>Received: from sc8-sf-list1-b.sourceforge.net
>(sc8-sf-list1-b.sourceforge.net [10.3.1.7])by sc8-sf-spam2.sourceforge.net
>(Postfix) with ESMTPid C5E97127D9; Wed, 4 Jan 2006 14:05:01 -0800 (PST)
>Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91]
>helo=mail.sourceforge.net)by sc8-sf-list1.sourceforge.net with esmtp (Exim
>4.30)id 1EuGjm-0001xH-Qjfor lirc-list@...; Wed, 04 Jan
>2006 14:04:06 -0800
>Received: from moutng.kundenserver.de ([22.214.171.124])by
>mail.sourceforge.net with esmtp (Exim 4.44)id 1EuGjm-0001pR-AWfor
>lirc-list@...; Wed, 04 Jan 2006 14:04:06 -0800
>Received: from [126.96.36.199] (helo=localhost)by mrelayeu.kundenserver.de
>(node=mrelayeu6) with ESMTP (Nemesis),id 0ML29c-1EuGjj0aPe-0001Pi; Wed, 04
>Jan 2006 23:04:04 +0100
>Received: by bartelmus.de (OpenXP/3.8.16-95-200410050432f (Linux)); 04 Jan
>2006 23:04:01 +0100
>User-Agent: OpenXP/3.8.16-95-200410050432f (Linux)
>X-Provags-ID: kundenserver.de abuse@...
>X-Spam-Score: 0.0 (/)
>X-Spam-Report: Spam Filtering performed by sourceforge.net.See
>http://spamassassin.org/tag/ for more details.Report problems to
>List-Id: LIRC mailing list <lirc-list.lists.sourceforge.net>
>X-Original-Date: 04 Jan 2006 23:03:00 +0100
>X-OriginalArrivalTime: 04 Jan 2006 22:05:03.0066 (UTC)
>Mike Bourgeous "i_am_nitrogen@..." wrote:
> > 1. After lowering and raising the serial control lines by closing and
> > opening /dev/ttyS0, the receiver sends an 'X' before I transmit the
> > 'I' 'R' and receive 'O' 'K' with my test application.
>This is not uncommon. The libirman code should already handle this.
> > 2. All codes received from all of my remotes are bit-reversed. In other
> > words, the bit order of each byte is reversed, so 0x01 becomes 0x80,
> > etc. This makes it impossible to use any existing remote definition
> > files for my remotes, and also makes it impossible for anyone else to
> > use any definitions I could create and upload for my remotes.
>You can't use config files created with a home-brew receiver with the
>Irman and vice versa anyway. When using the Irman while creating the
>config file, you are missing the timing values of the IR protocol.
>Also you don't know the real code length, so all Irman config files have
>64 bit code length.
> > 3. When using the MyHD remote, if I hold down a button instead of
> > repeating the code for that button the receiver sends
> > 01 00 00 00 00 00 hex. I don't think that the remote is doing this.
> > All of my other remotes repeat the code identically or with some
> > bits toggled each time.
>I think the libirman library currently filters out all repeat events
> > 4. All codes received look like this (which I believe is the standard
> > protocol):
> > 3A 5D 1A 4B 01 00
> > prefix code 01 00
>This probably is highly dependent on the remote control used.
> > Here is my proposition to solve this problem:
> > If no other irman device sends an 'X' before receiving anything,
> > then the 'X' could be used to detect a MyHD/MyIRC serial receiver.
> > Otherwise, the user would have to specify the type of receiver.
> > Should the fix be in lirc or in libirman?
>I would ignore this altogether as long as your receiver works.
>This SF.net email is sponsored by: Splunk Inc. Do you grep through log
>for problems? Stop! Download the new AJAX search engine that makes
>searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
Express yourself instantly with MSN Messenger! Download today - it's FREE!