lirc-list

Austar (Austel) Flinders STB - Cannot Learn

[<si...@bi...>]

Hi All,

After searching what seems to be the entire web I cannot find any useful information in relation to the IR codes for an Austar (paytv) Flinders satellite set top box.

I have a MCEUSB sender/receiver, irrecord is unable to learn the codes (something went wrong always pops up when attempting to learn). If I learn in raw mode and use irw its all messed up. Pressing the number two will sometimes show two, sometimes three, sometimes nothing at all!

When blasting these raw codes the STB doesn't respond. When blasting lirc config files I have found nothing happens. I know the sender is working because I have tested it with another device that CAN learn.

Any help would be appreciated!

Thanks!

usb reset

[Josu L. <jos...@gm...>]

Hello all, I am having some problems with my IR receiver:

$ lsusb
Bus 004 Device 002: ID 0471:0815 Philips (or NXP) eHome Infrared Receiver

I am using Debian Squeeze with lirc 0.8.3-5. The problem is that
sometimes it stop to execute some irexec commands, this is what I get
on dmesg:

# cat /var/log/messages
Mar 18 22:16:39 htpc2 kernel: [684278.076486] usb 1-2: reset high
speed USB device using ehci_hcd and address 2
Mar 18 23:23:22 htpc2 kernel: [688281.240953] usb 4-1: USB disconnect, address 6
Mar 18 23:23:22 htpc2 kernel: [688281.242050] lirc_mceusb2[6]: usb
remote disconnected
Mar 18 23:23:22 htpc2 kernel: [688281.548543] usb 4-1: new full speed
USB device using ohci_hcd and address 7
Mar 18 23:23:23 htpc2 kernel: [688281.763917] usb 4-1: New USB device
found, idVendor=0471, idProduct=0815
Mar 18 23:23:23 htpc2 kernel: [688281.763931] usb 4-1: New USB device
strings: Mfr=1, Product=2, SerialNumber=3
Mar 18 23:23:23 htpc2 kernel: [688281.763940] usb 4-1: Product: eHome
Infrared Transceiver
Mar 18 23:23:23 htpc2 kernel: [688281.763947] usb 4-1: Manufacturer: Philips
Mar 18 23:23:23 htpc2 kernel: [688281.763954] usb 4-1: SerialNumber: PH00W3Up
Mar 18 23:23:23 htpc2 kernel: [688281.764224] usb 4-1: configuration
#1 chosen from 1 choice
Mar 18 23:23:23 htpc2 kernel: [688281.944037] usb 4-1: reset full
speed USB device using ohci_hcd and address 7
Mar 18 23:23:23 htpc2 kernel: [688282.138920] lirc_dev:
lirc_register_plugin: sample_rate: 0
Mar 18 23:23:23 htpc2 kernel: [688282.144902] lirc_mceusb2[7]: Philips
eHome Infrared Transceiver on usb4:7
Mar 20 09:16:39 htpc2 kernel: [810278.090098] usb 1-2: reset high
speed USB device using ehci_hcd and address 2
Mar 20 12:16:39 htpc2 kernel: [821078.089043] usb 1-2: reset high
speed USB device using ehci_hcd and address 2
Mar 20 14:16:39 htpc2 kernel: [828278.091844] usb 1-2: reset high
speed USB device using ehci_hcd and address 2
Mar 21 09:16:39 htpc2 kernel: [896678.088038] usb 1-2: reset high
speed USB device using ehci_hcd and address 2
Mar 21 21:16:39 htpc2 kernel: [939878.076565] usb 1-2: reset high
speed USB device using ehci_hcd and address 2
Mar 22 07:26:54 htpc2 kernel: [976492.755507] usb 4-1: USB disconnect, address 7
Mar 22 07:26:54 htpc2 kernel: [976492.756612] lirc_mceusb2[7]: usb
remote disconnected
Mar 22 07:26:54 htpc2 kernel: [976493.061041] usb 4-1: new full speed
USB device using ohci_hcd and address 8
Mar 22 07:26:54 htpc2 kernel: [976493.275468] usb 4-1: New USB device
found, idVendor=0471, idProduct=0815
Mar 22 07:26:54 htpc2 kernel: [976493.275477] usb 4-1: New USB device
strings: Mfr=1, Product=2, SerialNumber=3
Mar 22 07:26:54 htpc2 kernel: [976493.275484] usb 4-1: Product: eHome
Infrared Transceiver
Mar 22 07:26:54 htpc2 kernel: [976493.275489] usb 4-1: Manufacturer: Philips
Mar 22 07:26:54 htpc2 kernel: [976493.275494] usb 4-1: SerialNumber: PH00W3Up
Mar 22 07:26:54 htpc2 kernel: [976493.275719] usb 4-1: configuration
#1 chosen from 1 choice
Mar 22 07:26:54 htpc2 kernel: [976493.440035] usb 4-1: reset full
speed USB device using ohci_hcd and address 8
Mar 22 07:26:54 htpc2 kernel: [976493.647460] lirc_dev:
lirc_register_plugin: sample_rate: 0
Mar 22 07:26:54 htpc2 kernel: [976493.653453] lirc_mceusb2[8]: Philips
eHome Infrared Transceiver on usb4:8

Is possible to fix this?

When this happens, it receive well, but it does not transmit nothing
with "irsend" command.

I will appreciate any help.

Thanks and best regards.

-- 
Josu Lazkano

[Peppino I. <pep...@ho...>]

http://kantors.org/coppermine/albums/userpics/docs.php?nearby138.png 		 	   		  

LIRC won't restart on Oneiric

[Michael W. <wi...@gm...>]

Hi!

I'm having a strange problem on xbmcbuntu where LIRC won't reload.
It's running lirc 0.9.0 x86, and when I stop the lirc daemon and start
it back up again, it says this....


 * Loading LIRC modules
                                                             [ OK ]
 * Unable to load LIRC kernel modules. Verify your
 * selected kernel modules in /etc/lirc/hardware.conf


When the machine first boots, it works fine and loads lircd.  If I
restart the service with the init.d script is when it fails, but I can
manually start it back up with this....

/usr/sbin/lircd --output=/var/run/lirc/lircd --device=/dev/lirc0

If I mod the /etc/init.d/lirc script so it looks like this at the beginning....

	if $MODULES_MISSING; then
		log_failure_msg "Unable to load LIRC kernel modules. Verify your"
		log_failure_msg "selected kernel modules in /etc/lirc/hardware.conf"
		START_LIRCMD=true
		START_LIRCD=true
	fi

instead of the original two original "=false" lines, it seems like
things work better.

Has anybody run into this problem?  I found an old bugtraq for ubuntu,
but this was going back to the 10.04 (possibly) lirc client, and not
the Oneiric 11.10 one.


Thanks,
Mike

Lirc 0.9 with Kernel 3.2.11

[Kraus P. <phi...@fl...>]

Hello,

I would like to use lirc 0.9 under a Gentoo Linux x86_64 on a 3.2.11 kernel. I try to build lirc with emerge and I have set the LIRC_DEVICES to "hauppauge", because I would like to connect to the IR receiver on a HVR 1900 (usb). Module-unloading, event interface and the i2c componentes are buld into the kernel as modules, but the emerge creates a compiler error:

/var/tmp/portage/app-misc/lirc-0.9.0/work/lirc-0.9.0/drivers/lirc_i2c/lirc_i2c.c: In function 'ir_probe':
/var/tmp/portage/app-misc/lirc-0.9.0/work/lirc-0.9.0/drivers/lirc_i2c/lirc_i2c.c:559:13: error: 'struct i2c_adapter' has no member named 'id'
/var/tmp/portage/app-misc/lirc-0.9.0/work/lirc-0.9.0/drivers/lirc_i2c/lirc_i2c.c: At top level:
/var/tmp/portage/app-misc/lirc-0.9.0/work/lirc-0.9.0/drivers/lirc_i2c/lirc_i2c.c:232:12: warning: 'add_to_buf_pvr2000' defined but not used
make[5]: *** [/var/tmp/portage/app-misc/lirc-0.9.0/work/lirc-0.9.0/drivers/lirc_i2c/lirc_i2c.o] Error 1

How I can solve the build problem?

Thanks a lot

Phil

Lirc with Xubuntu 11.10

[Alexandre A. <aar...@gm...>]

Hi, I have a problem finishing up my Lirc config on a Xubuntu 11.10 
fresh install.

It seems to work but only for volume control - any other action seems to 
fail.

I understand the lirc_i2c module is now deprecated (I run a 3.0 kernel: 
Ubuntu 11.10 (GNU/Linux 3.0.0-16-generic i686)), and if I activate the 
lirc-kbd-i2c module then inputs are interpreted as keystrokes from a 
keyboard. And if I only activate the lirc_dev module, nothing happens.

Below are my info, included an irw output when I press any button on my 
remote (except the volume, which is correctly understood by my system).

Any idea will be welcome. Thanks in advance!

Alex


alex@ALEX:~$ ls /dev/lir*
/dev/lircd

alex@ALEX:~$ cat /proc/bus/input/devices
(relevant parts only)
I: Bus=0018 Vendor=0000 Product=0000 Version=0000
N: Name="i2c IR (Hauppauge)"
P: Phys=i2c-1/1-0018/ir0
S: Sysfs=/devices/virtual/rc/rc0/input4
U: Uniq=
H: Handlers=kbd event4
B: PROP=0
B: EV=100013
B: KEY=10afc312 2142017 0 0 0 0 118000 41a8 4801 9e16c0 0 0 10000ffc
B: MSC=10

The hardware.conf file shows:

# /etc/lirc/hardware.conf
#
#Chosen Remote Control
REMOTE="Hauppauge TV card"
REMOTE_DRIVER=""
REMOTE_MODULES="lirc_dev ir-kbd-i2c"
#REMOTE_DEVICE="/dev/lirc0"
#REMOTE_DEVICE="/dev/lircd"
REMOTE_DEVICE="/dev/input/event4"
REMOTE_SOCKET=""

REMOTE_LIRCD_CONF="/etc/lirc/lircd.conf"
#REMOTE_LIRCD_CONF="hauppauge/lircd.conf.hauppauge"
REMOTE_LIRCD_ARGS=""

#Chosen IR Transmitter
TRANSMITTER="None"
TRANSMITTER_MODULES=""
TRANSMITTER_DRIVER=""
TRANSMITTER_DEVICE=""
TRANSMITTER_SOCKET=""
TRANSMITTER_LIRCD_CONF=""
TRANSMITTER_LIRCD_ARGS=""

#Enable lircd
START_LIRCD="true"

#Don't start lircmd even if there seems to be a good config file
#START_LIRCMD="false"

#Try to load appropriate kernel modules
LOAD_MODULES="true"

# Default configuration files for your hardware if any
LIRCMD_CONF=""

FORCE_NONINTERACTIVE_RECONFIGURATION="false"
START_LIRCMD=""


#This configuration has been automatically generated via
#the Ubuntu LIRC package maintainer scripts.
#
#It includes the default configuration for the remote and/or
#transmitter that you have selected during package installation.
#
#Feel free to add any custom remotes to the configuration
#via additional include directives or below the existing
#Ubuntu include directives from your selected remote and/or
#transmitter.

#Configuration for the Hauppauge TV card remote:
#include 
"/usr/share/lirc/extras/more_remotes/hauppauge/lircd.conf.hauppauge"

begin remote

   name  Hauppauge
   bits           13
   flags SHIFT_ENC
   eps            30
   aeps          100

   one           950   830
   zero          950   830
   plead         960
   gap          89584
   repeat_bit      2

       begin codes
           TV                       0x000000000000100F
           RADIO                    0x000000000000100C
           FULL_SCREEN              0x000000000000102E
           CH+                      0x0000000000001020
           CH-                      0x0000000000001021
           VOL-                     0x0000000000001011
           VOL+                     0x0000000000001010
           MUTE                     0x000000000000100D
           SOURCE                   0x0000000000001022
           1                        0x0000000000001001
           2                        0x0000000000001002
           3                        0x0000000000001003
           4                        0x0000000000001004
           5                        0x0000000000001005
           6                        0x0000000000001006
           7                        0x0000000000001007
           8                        0x0000000000001008
           9                        0x0000000000001009
           0                        0x0000000000001000
           RESERVED                 0x000000000000101E
           MINIMIZE                 0x0000000000001026
       end codes

end remote


alex@ALEX:~$ irw
é&'(-ç_èà^C

alex@ALEX:~$ lsmod | grep ir
ir_kbd_i2c             12993  0
ir_lirc_codec          12770  0
lirc_dev               18700  1 ir_lirc_codec
ir_sony_decoder        12493  0
ir_jvc_decoder         12490  0
ir_rc6_decoder         12490  0
ir_rc5_decoder         12490  0
ir_nec_decoder         12490  0
rc_core                25797  10 
rc_hauppauge,ir_kbd_i2c,ir_lirc_codec,ir_sony_decoder,ir_jvc_decoder,ir_rc6_decoder,bttv,ir_rc5_decoder,ir_nec_decoder
firewire_ohci          35854  0
firewire_core          56937  1 firewire_ohci
crc_itu_t              12627  1 firewire_core

Re: recycle the IR LED from old remote controls?

[JimMH <jsk...@sb...>]

Brian J. Murrell wrote:
> 
> 
> 
> So is an IR LED an IR LED is an IR LED (i.e. are they all generally the
> same) or will I have to adjust my circuit depending on the particular IR
> LED that I salvage from an old remote control?
> 
> Cheers,
> b.
> 
> 
> 
In general, yes.  They have slightly different characteristics but the
differences should be minor for what you are wanting to do, especially since
they are all for remote control to start with.  I don't think any circuit
adjustments should be needed.
-- 
View this message in context: http://old.nabble.com/recycle-the-IR-LED-from-old-remote-controls--tp33491900p33499011.html
Sent from the LIRC mailing list archive at Nabble.com.

Re: pronto2lirc errors

[Bengt M. <bu...@be...>]

On 03/13/12 21:08, JimMH wrote:
> 
> 
> 
> Bengt Martensson-2 wrote:
>>
>>> RepeatableSequence
>>>   File "/usr/bin/pronto2lirc", line 47, in CreatePulses
>>>     raise "Number of actual codes does not match the header information!"
>>
>> As the error message sort-of says, the header is not consistent with the
>> length of the message. It says that there are 0x0000 + 0x009c = 0 + 156
>> = 156 burst pairs; but in fact there are only 38. If this is Greek to
>> you: The program fails since the alleged Pronto signal is nonsensical.
>>
>> Greetz,
>>
>> Bengt
>>
>>
> The data is from here:
> http://www.remotecentral.com/cgi-bin/codes/hunter_douglas/power_rise/
> 
> and they say these are pronto codes.
...

These signals still are incorrect in the said sense. You may like to
complain to the poster.

Of course, you can try just adjusting the length in the header: Just
change the forth number from "009c" to "0026". Rationale: there are 38 =
0x26 burst pairs (two numbers make a burst pair, not counting the first
four). But it is not exactly plausible that the poster had perfect
signals, just that the length got screwed up?

Re: pronto2lirc errors

[JimMH <jsk...@sb...>]

Bengt Martensson-2 wrote:
> 
>> RepeatableSequence
>>   File "/usr/bin/pronto2lirc", line 47, in CreatePulses
>>     raise "Number of actual codes does not match the header information!"
> 
> As the error message sort-of says, the header is not consistent with the
> length of the message. It says that there are 0x0000 + 0x009c = 0 + 156
> = 156 burst pairs; but in fact there are only 38. If this is Greek to
> you: The program fails since the alleged Pronto signal is nonsensical.
> 
> Greetz,
> 
> Bengt
> 
> 
The data is from here:
http://www.remotecentral.com/cgi-bin/codes/hunter_douglas/power_rise/

and they say these are pronto codes.  I don't know much about IR formats. 
What am I missing?
-- 
View this message in context: http://old.nabble.com/pronto2lirc-errors-tp33491824p33497213.html
Sent from the LIRC mailing list archive at Nabble.com.

Re: recycle the IR LED from old remote controls?

[Brian J. M. <br...@in...>]

On 12-03-13 03:15 PM, Bengt Martensson wrote:
> 
> Yes, it is possible, but why?

Accessibility?

> IR LEDs are cheap (fraction of dollar/euro
> in quantities of 1),

If you can buy them locally.  If not, you are paying many times their
cost in shipping.  If I'm going to have to eat (and wait for) shipping I
may as well just buy a whole ready made product.

b.

Re: pronto2lirc errors

[Bengt M. <bu...@be...>]

On 03/13/12 03:35, JimMH wrote:
> 
> I am trying to run pronto2lirc python script ver 1.11 on Fedora 12 on the
> following:
> 
> [code]
> Open1:0000 0063 0000 009c 0070 0070 002a 002a 002a 0070 002a 002a 002a 0070
> 0070 0070 002a 002a 002a 0070 002a 002a 002a 0070 0070 0070 002a 002a 002a
> 0070 002a 002a 002a 0070 0070 0070 002a 002a 002a 0070 002a 002a 002a 0070
> 0070 0070 002a 002a 002a 0070 002a 002a 002a 0070 0070 0070 002a 002a 002a
> 0070 002a 002a 002a 0070 0070 0070 002a 002a 002a 0070 002a 002a 002a 0070
> 0070 0070 002a 002a 002a 004e
...
> RepeatableSequence
>   File "/usr/bin/pronto2lirc", line 47, in CreatePulses
>     raise "Number of actual codes does not match the header information!"

As the error message sort-of says, the header is not consistent with the
length of the message. It says that there are 0x0000 + 0x009c = 0 + 156
= 156 burst pairs; but in fact there are only 38. If this is Greek to
you: The program fails since the alleged Pronto signal is nonsensical.

Greetz,

Bengt

Re: recycle the IR LED from old remote controls?

[Bengt M. <bu...@be...>]

On 03/13/12 04:14, Brian J. Murrell wrote:
> Surely I must be able to recycle the IR LED from an old remote control
> into an IR blaster, yes? 

Yes, it is possible, but why? IR LEDs are cheap (fraction of dollar/euro
in quantities of 1), AND you can get a well defined model, with data
sheet download-able from internet. (Just Google for "IR LED 950nm").

Bengt

Re: recycle the IR LED from old remote controls?

[Brian J. M. <br...@in...>]

On 12-03-13 12:47 PM, JimMH wrote:
> 
> Yes, the IR LEDs in remotes can be easily reused,

So is an IR LED an IR LED is an IR LED (i.e. are they all generally the
same) or will I have to adjust my circuit depending on the particular IR
LED that I salvage from an old remote control?

Cheers,
b.

Re: recycle the IR LED from old remote controls?

[JimMH <jsk...@sb...>]

Yes, the IR LEDs in remotes can be easily reused, especially if they have
longer leads.  I pulled a couple from a IR repeater that quit working too. 
If you don't mind how it looks you can just solder wires on and bend them so
the LED shines across the face of the device to be controlled.  Because it
is so close it doesn't need to be aimed directly at the unit.  

These could be hooked up to a serial port or with the appropriate plug, used
in place of a stick on emitter with a USB transciever.  Here is a link to
something similar:

http://mightyohm.com/blog/2009/04/diy-tivo-ir-blaster/

-- 
View this message in context: http://old.nabble.com/recycle-the-IR-LED-from-old-remote-controls--tp33491900p33495273.html
Sent from the LIRC mailing list archive at Nabble.com.

recycle the IR LED from old remote controls?

[Brian J. M. <br...@in...>]

Surely I must be able to recycle the IR LED from an old remote control
into an IR blaster, yes?  I don't really care about range and I can but
my blaster's IR right up against the receiver's IR sensor.

Given the average remote control is it more or less than likely that
it's IR LED can be recycled like this?

Cheers,
b.

pronto2lirc errors

[JimMH <jsk...@sb...>]

I am trying to run pronto2lirc python script ver 1.11 on Fedora 12 on the
following:

[code]
Open1:0000 0063 0000 009c 0070 0070 002a 002a 002a 0070 002a 002a 002a 0070
0070 0070 002a 002a 002a 0070 002a 002a 002a 0070 0070 0070 002a 002a 002a
0070 002a 002a 002a 0070 0070 0070 002a 002a 002a 0070 002a 002a 002a 0070
0070 0070 002a 002a 002a 0070 002a 002a 002a 0070 0070 0070 002a 002a 002a
0070 002a 002a 002a 0070 0070 0070 002a 002a 002a 0070 002a 002a 002a 0070
0070 0070 002a 002a 002a 004e
Close1:0000 0063 0000 009c 0070 0070 002a 002a 002a 0070 002a 0070 002a 002a
0070 0070 002a 002a 002a 0070 002a 0070 002a 002a 0070 0070 002a 002a 002a
0070 002a 0070 002a 002a 0070 0070 002a 002a 002a 0070 002a 0070 002a 002a
0070 0070 002a 002a 002a 0070 002a 0070 002a 002a 0070 0070 002a 002a 002a
0070 002a 0070 002a 002a 0070 0070 002a 002a 002a 0070 002a 0070 002a 002a
0070 0070 002a 002a 002a 004e
Open2:0000 0063 0000 009c 0070 0070 002a 0070 002a 002a 002a 002a 002a 0070
0070 0070 002a 0070 002a 002a 002a 002a 002a 0070 0070 0070 002a 0070 002a
002a 002a 002a 002a 0070 0070 0070 002a 0070 002a 002a 002a 002a 002a 0070
0070 0070 002a 0070 002a 002a 002a 002a 002a 0070 0070 0070 002a 0070 002a
002a 002a 002a 002a 0070 0070 0070 002a 0070 002a 002a 002a 002a 002a 0070
0070 0070 002a 0070 002a 004f
Close2:0000 0063 0000 009c 0070 0070 002a 0070 002a 002a 002a 0070 002a 002a
0070 0070 002a 0070 002a 002a 002a 0070 002a 002a 0070 0070 002a 0070 002a
002a 002a 0070 002a 002a 0070 0070 002a 0070 002a 002a 002a 0070 002a 002a
0070 0070 002a 0070 002a 002a 002a 0070 002a 002a 0070 0070 002a 0070 002a
002a 002a 0070 002a 002a 0070 0070 002a 0070 002a 002a 002a 0070 002a 002a
0070 0070 002a 0070 002a 004f
[/code]

I get the following errors:

[code]
[jimmyth@myth Desktop]$ pronto2lirc Hunterdouglaspronto.txt
Traceback (most recent call last):
  File "/usr/bin/pronto2lirc", line 173, in <module>
    p=RemoteFilesParser(sys.argv[1])
  File "/usr/bin/pronto2lirc", line 141, in __init__
    device.ProcessHEX(f,sLine)
  File "/usr/bin/pronto2lirc", line 94, in ProcessHEX
    self.AddCodes(sCodeName,sHexCodes)
  File "/usr/bin/pronto2lirc", line 84, in AddCodes
    finalgap=seq.AnalyzeCode(sCodeName,sHexCodes)
  File "/usr/bin/pronto2lirc", line 63, in AnalyzeCode
    self.CreatePulses(sHexTable[4:])    # The rest are OnceSequence +
RepeatableSequence
  File "/usr/bin/pronto2lirc", line 47, in CreatePulses
    raise "Number of actual codes does not match the header information!"
TypeError: exceptions must be classes or instances, not str
[jimmyth@myth Desktop]$ 
[/code]
-- 
View this message in context: http://old.nabble.com/pronto2lirc-errors-tp33491824p33491824.html
Sent from the LIRC mailing list archive at Nabble.com.

Re: How to learn remote that only has 4 buttons/convert pronto codes?

[JimMH <jsk...@sb...>]

Here are the codes I found:
(from http://www.remotecentral.com/cgi-bin/codes/hunter_douglas/power_rise/)

Open1

0000 0063 0000 009c 0070 0070 002a 002a 002a 0070 002a 002a 002a 0070 0070
0070 002a 002a 002a 0070 002a 002a 002a 0070 0070 0070 002a 002a 002a 0070
002a 002a 002a 0070 0070 0070 002a 002a 002a 0070 002a 002a 002a 0070 0070
0070 002a 002a 002a 0070 002a 002a 002a 0070 0070 0070 002a 002a 002a 0070
002a 002a 002a 0070 0070 0070 002a 002a 002a 0070 002a 002a 002a 0070 0070
0070 002a 002a 002a 004e

Close1
0000 0063 0000 009c 0070 0070 002a 002a 002a 0070 002a 0070 002a 002a 0070
0070 002a 002a 002a 0070 002a 0070 002a 002a 0070 0070 002a 002a 002a 0070
002a 0070 002a 002a 0070 0070 002a 002a 002a 0070 002a 0070 002a 002a 0070
0070 002a 002a 002a 0070 002a 0070 002a 002a 0070 0070 002a 002a 002a 0070
002a 0070 002a 002a 0070 0070 002a 002a 002a 0070 002a 0070 002a 002a 0070
0070 002a 002a 002a 004e

Open2
0000 0063 0000 009c 0070 0070 002a 0070 002a 002a 002a 002a 002a 0070 0070
0070 002a 0070 002a 002a 002a 002a 002a 0070 0070 0070 002a 0070 002a 002a
002a 002a 002a 0070 0070 0070 002a 0070 002a 002a 002a 002a 002a 0070 0070
0070 002a 0070 002a 002a 002a 002a 002a 0070 0070 0070 002a 0070 002a 002a
002a 002a 002a 0070 0070 0070 002a 0070 002a 002a 002a 002a 002a 0070 0070
0070 002a 0070 002a 004f

Close2
0000 0063 0000 009c 0070 0070 002a 0070 002a 002a 002a 0070 002a 002a 0070
0070 002a 0070 002a 002a 002a 0070 002a 002a 0070 0070 002a 0070 002a 002a
002a 0070 002a 002a 0070 0070 002a 0070 002a 002a 002a 0070 002a 002a 0070
0070 002a 0070 002a 002a 002a 0070 002a 002a 0070 0070 002a 0070 002a 002a
002a 0070 002a 002a 0070 0070 002a 0070 002a 002a 002a 0070 002a 002a 0070
0070 002a 0070 002a 004f
-- 
View this message in context: http://old.nabble.com/How-to-learn-remote-that-only-has-4-buttons-convert-pronto-codes--tp33482582p33483462.html
Sent from the LIRC mailing list archive at Nabble.com.

How to learn remote that only has 4 buttons/convert pronto codes?

[JimMH <jsk...@sb...>]

I have a Hunter Douglas Power Rise remote that has only 4 outputs - up and
down for units 1 and 2.  I tried to learn it but wasn't able to.  I suspect
it is because it has so few buttons.  I found what I think are pronto codes
but am not sure how to convert them to lirc.

BTW, this is an early HD remote that only uses IR, not like the new ones
that also have RF.
-- 
View this message in context: http://old.nabble.com/How-to-learn-remote-that-only-has-4-buttons-convert-pronto-codes--tp33482582p33482582.html
Sent from the LIRC mailing list archive at Nabble.com.

Running lirc on Mac OS X - pointers needed

[Matt W. <ma...@ma...>]

Hi,

I've bought a Mac Mini which I'm trying to set up as a MythTV box. I have a Hauppague remote which I've used with lirc / MythTV before on another machine running Ubuntu, and I'd like to use it with the Mac. I realise that I could install Ubuntu on the Mac but I'd rather stick with OS X if possible since that's a more familiar operating system to the other members of the family.

I've seen a few articles or threads that make reference to using lirc with a Mac, but none of them seem very up to date. For example this [1] which seems to recommend using MacPorts - I'd really rather not install MacPorts unless I have to.

I'm reasonably comfortable building things from source, but before I set out on that I'd like to get an idea of whether it's even possible, or whether there's a simpler route. 

Any advice? Thanks very much in advance.

[1] http://www.gossamer-threads.com/lists/mythtv/users/326150

cheers,
Matt

Hauppage HD PVR blaster - need help over the finish line

[Don D. <dou...@lo...>]

I've been trying to integrate the following components:

Dish Network 211k receiver
Hauppage HD PVR
Mythbuntu, kernel 3.0.0-12-generic
Antec Fusion Remote case
VDPAU-capable video card

The HD PVR has been the problem child.  I'm able to get it to capture 
silent video using "cat /dev/video0 > test.ts" and view it with "vlc 
test.ts" after some reading and fiddling.*  Now I'm working on getting 
it to change channels using the IR blaster.  After quite a bit more 
fiddling, irsend is able to send codes---somewhere---without an error 
message.

There are two apparent problems.  The send_power_new script runs to 
completion without ever turning off the receiver.  And there's no 
visible flash from the LED on the blaster, contrary to how I've heard it 
behaves.  My camera can't see an infrared flash either.  Perhaps I'm 
sending to the wrong device?


My hardware.conf:

# /etc/lirc/hardware.conf
#
#Chosen Remote Control
#REMOTE="Soundgraph iMON IR/LCD"
#REMOTE_MODULES="lirc_dev lirc_imon"
#REMOTE_DRIVER=""
#REMOTE_DEVICE="/dev/lirc"
#REMOTE_SOCKET=""
#REMOTE_LIRCD_CONF="imon/lircd.conf.imon"
#REMOTE_LIRCD_ARGS=""

#Chosen IR Transmitter
TRANSMITTER="HD-PVR"
TRANSMITTER_MODULES="lirc_dev lirc_zilog"
TRANSMITTER_DRIVER=""
TRANSMITTER_DEVICE="/dev/lirc0"
TRANSMITTER_SOCKET="/var/run/lirc/lircd"
TRANSMITTER_LIRCD_CONF=""
TRANSMITTER_LIRCD_ARGS=""

#Enable lircd
START_LIRCD="true"

#Don't start lircmd even if there seems to be a good config file
#START_LIRCMD="false"

#Try to load appropriate kernel modules
LOAD_MODULES="true"

# Default configuration files for your hardware if any
LIRCMD_CONF=""

#Forcing noninteractive reconfiguration
#If lirc is to be reconfigured by an external application
#that doesn't have a debconf frontend available, the noninteractive
#frontend can be invoked and set to parse REMOTE and TRANSMITTER
#It will then populate all other variables without any user input
#If you would like to configure lirc via standard methods, be sure
#to leave this set to "false"
FORCE_NONINTERACTIVE_RECONFIGURATION="false"
START_LIRCMD=""


My lircd.conf is taken from here:
http://www.blushingpenguin.com/mark/lmilk/lircd.conf


Relevant-looking stuff from dmesg:
...
[   10.550528] hdpvr 3-3:1.0: firmware version 0x15 dated Jun 17 2010 
09:26:53
[   10.556206] lirc_dev: IR Remote Control driver registered, major 250
[   10.556414] IR LIRC bridge handler initialized
[   10.576075] Registered IR keymap rc-imon-pad
[   10.576276] input: iMON Remote (15c2:0038) as 
/devices/pci0000:00/0000:00:13.0/usb5/5-4/5-4:1.0/rc/rc0/input5
[   10.576384] rc0: iMON Remote (15c2:0038) as 
/devices/pci0000:00/0000:00:13.0/usb5/5-4/5-4:1.0/rc/rc0
[   10.584140] imon 5-4:1.0: iMON device (15c2:0038, intf0) on usb<5:2> 
initialized
[   10.584163] imon 5-4:1.1: iMON device (15c2:0038, intf1) on usb<5:2> 
initialized
[   10.584175] usbcore: registered new interface driver imon
[   10.603604] r8169 0000:01:00.0: eth0: link down
[   10.603618] r8169 0000:01:00.0: eth0: link down
[   10.603983] ADDRCONF(NETDEV_UP): eth0: link is not ready
[   10.626140] EXT4-fs (sda2): re-mounted. Opts: errors=remount-ro
[   10.741264] hdpvr 3-3:1.0: device now attached to video0
[   10.741281] usbcore: registered new interface driver hdpvr
...
[   12.951745] lirc_zilog: module is from the staging directory, the 
quality is unknown, you have been warned.
[   12.951955] init: tty6 main process (1178) terminated with status 2
[   12.951992] init: tty6 main process ended, respawning
[   12.952119] lirc_zilog: Zilog/Hauppauge IR driver initializing
[   12.954171] lirc_zilog: probing IR Tx on Hauppage HD PVR I2C (i2c-1)
[   12.956180] init: tty6 main process (1194) terminated with status 2
[   12.956216] init: tty6 main process ended, respawning
[   12.957381] i2c i2c-1: lirc_dev: driver lirc_zilog registered at 
minor = 0
[   12.957385] lirc_zilog: IR unit on Hauppage HD PVR I2C (i2c-1) 
registered as lirc0 and ready
[   12.957388] lirc_zilog: probe of IR Tx on Hauppage HD PVR I2C (i2c-1) 
done
[   12.957412] lirc_zilog: initialization complete


* I had to turn off autostarting of the MythTV frontend during testing. 
  Once MythTV has been at the HD PVR, you can't get "cat /dev/video0" to 
work.  Hope that saves someone some pain.

Links:
http://www.blushingpenguin.com/mark/lmilk/send_power_new
http://www.blushingpenguin.com/mark/lmilk/IRcodesets.html

Re: irw didn't receive input from my remote

[Matthias M. <Mat...@gm...>]

Am Sonntag 11 März 2012 schrieben Sie:
> On 03/10/2012 11:44 AM, Matthias Meyer wrote:
> > I've running Debian Wheezy with kernel 3.2.0 and lirc 0.9.
> > I've tried to run thre remote of my (old) Haupauge PVR350 but it doesn't
> > work.
> >
> > ls /dev/lir*
> > /dev/lircd
> >
> > cat /proc/bus/input/devices
> >   :
> > I: Bus=0019 Vendor=0000 Product=0000 Version=0000
> > N: Name="Eee PC WMI hotkeys"
> > P: Phys=eeepc-wmi/input0
> > S: Sysfs=/devices/platform/eeepc-wmi/input/input5
> > U: Uniq=
> > H: Handlers=kbd event5 rfkill
> > B: PROP=0
> > B: EV=100013
> > B: KEY=7e40000 0 0 0 0 0 0 0 0 114008 100000 3000800 1100000 e0000 0 0 0
> > B: MSC=10
> >   :
> > I: Bus=0018 Vendor=0000 Product=0000 Version=0000
> > N: Name="i2c IR (Hauppauge WinTV PVR-350"
> > P: Phys=i2c-0/0-0018/ir0
> > S: Sysfs=/devices/virtual/rc/rc0/input8
> > U: Uniq=
> > H: Handlers=kbd event8
> > B: PROP=0
> > B: EV=100013
> > B: KEY=10afc312 2142017 0 0 0 0 118000 41a8 4801 9e16c0 0 0 10000ffc
> > B: MSC=10
> >
> > /etc/lirc/hardware.conf contains:
> > # Run "lircd --driver=help" for a list of supported drivers.
> > DRIVER="devinput"
> > # usually /dev/lirc0 is the correct setting for systems using udev
> > DEVICE="/dev/input/event8"
> > MODULES="ir-kbd-i2c"
> >
> > /etc/lirc/lircmd.conf
> > #UNCONFIGURED
> >
> > /etc/lirc/lircd.conf
> > ->  is a copy of /usr/share/lirc/remotes/hauppauge/lircd.conf.hauppauge
> >
> > If I use "/dev/input/event5" in /etc/lirc/hardware.conf I get the 
numbers
> > 0-9 within a terminal if pressed on the remote. But nothing for the 
other
> > keys.
> > If I run irw in another terminal nothing changed. I get the numbers 
within
> > the active terminal but nothing in irw.
> >
> > If I use "/dev/input/event8" in /etc/lirc/hardware.conf I get nothing in 
the
> > terminal and nothing in irw.
> >
> > It seems that the input from my remote doesn't reach lirc.
> >
> > Thanks in advance for any advice.
> >
> 
> I had the same problem discussed in this thread:
> 
> http://www.gossamer-threads.com/lists/mythtv/users/507773
> 
> The breadth and depth of knowledge available through this list never 
> ceases to amaze me. My problem was nailed in minutes.
> 
> The problem is with the 3.2 kernel and lirc. Read the thread for more 
info.
> 
> Revert to 3.1 and things will work. That is what I have done, pending 
> testing a new build of the imon.ko module. But your having the problem 
> points to lirc-9 and the kernel.
> 
> Geoff
> 
Thanks, unfortunately whether debian nor ubuntu provides an 3.1 image at 
this time :-(

Relevant modules loaded in my system are:
ir_lirc_codec          12631  0 
lirc_dev               12807  1 ir_lirc_codec
ir_mce_kbd_decoder     12551  0 
ir_sony_decoder        12403  0 
ir_jvc_decoder         12401  0 
ir_rc6_decoder         12401  0 
ir_rc5_decoder         12401  0 
rc_hauppauge           12382  0 
ir_nec_decoder         12401  0 
ir_kbd_i2c             12680  0 
rc_core                17918  10 
ir_lirc_codec,ir_mce_kbd_decoder,ir_sony_decoder,ir_jvc_decoder,ir_rc6_decoder,ir_rc5_decoder,rc_hauppauge,ir_nec_decoder,ir_kbd_i2c
evdev                  17225  12 

After "rmmod ir_kbd_i2c" I never get the 0-9 within a terminal if pressed on 
the remote. But as before not within irw.

-- 
Don't Panic

irw didn't receive input from my remote

[Matthias M. <Mat...@gm...>]

I've running Debian Wheezy with kernel 3.2.0 and lirc 0.9.
I've tried to run thre remote of my (old) Haupauge PVR350 but it doesn't 
work.

ls /dev/lir*
/dev/lircd

cat /proc/bus/input/devices
 :
I: Bus=0019 Vendor=0000 Product=0000 Version=0000
N: Name="Eee PC WMI hotkeys"
P: Phys=eeepc-wmi/input0
S: Sysfs=/devices/platform/eeepc-wmi/input/input5
U: Uniq=
H: Handlers=kbd event5 rfkill 
B: PROP=0
B: EV=100013
B: KEY=7e40000 0 0 0 0 0 0 0 0 114008 100000 3000800 1100000 e0000 0 0 0
B: MSC=10
 :
I: Bus=0018 Vendor=0000 Product=0000 Version=0000
N: Name="i2c IR (Hauppauge WinTV PVR-350"
P: Phys=i2c-0/0-0018/ir0
S: Sysfs=/devices/virtual/rc/rc0/input8
U: Uniq=
H: Handlers=kbd event8 
B: PROP=0
B: EV=100013
B: KEY=10afc312 2142017 0 0 0 0 118000 41a8 4801 9e16c0 0 0 10000ffc
B: MSC=10

/etc/lirc/hardware.conf contains:
# Run "lircd --driver=help" for a list of supported drivers.
DRIVER="devinput"
# usually /dev/lirc0 is the correct setting for systems using udev 
DEVICE="/dev/input/event8"
MODULES="ir-kbd-i2c"

/etc/lirc/lircmd.conf
#UNCONFIGURED

/etc/lirc/lircd.conf
-> is a copy of /usr/share/lirc/remotes/hauppauge/lircd.conf.hauppauge

If I use "/dev/input/event5" in /etc/lirc/hardware.conf I get the numbers 
0-9 within a terminal if pressed on the remote. But nothing for the other 
keys.
If I run irw in another terminal nothing changed. I get the numbers within 
the active terminal but nothing in irw.

If I use "/dev/input/event8" in /etc/lirc/hardware.conf I get nothing in the 
terminal and nothing in irw.

It seems that the input from my remote doesn't reach lirc.

Thanks in advance for any advice.

br
Matthias
-- 
Don't Panic

Re: lirc_serial

[Manfred Schmidt-V. <man...@ma...>]

On 09.03.2012 09:52, Manfred Schmidt-Voigt wrote:
> On 07.03.2012 17:44, Manfred Schmidt-Voigt wrote:
>> Hello List,
>>
>> I just jumped to kernel 3.2.7 on my Debian Sid system and tried to
>> reconfigure LIRC for that again. But I got the following problems:
>>
>>
>> mannitec02:/usr/local/src/lirc-0.9.0-pre1# uname -a
>> Linux mannitec02 3.2.7.20120307 #1 SMP Wed Mar 7 15:05:35 CET 2012 i686
>> GNU/Linux
>>
>> mannitec02:/usr/local/src/lirc-0.9.0-pre1# modprobe lirc_dev
>>
>> mannitec02:/usr/local/src/lirc-0.9.0-pre1# modprobe lirc_serial
>> ERROR: could not insert 'lirc_serial': Exec format error
>>
>> mannitec02:/usr/local/src/lirc-0.9.0-pre1# modinfo lirc_serial
>> filename:       /lib/modules/3.2.7.20120307/misc/lirc_serial.ko
>> license:        GPL
>> author:         Ralph Metzler, Trent Piepho, Ben Pfaff, Christoph
>> Bartelmus, Andrei Tanas
>> description:    Infra-red receiver driver for serial ports.
>> depends:        lirc_dev
>> vermagic:       2.6.37.20110219.1 SMP mod_unload modversions CORE2
>> parm:           type:Hardware type (0 = home-brew, 1 = IRdeo, 2 = IRdeo
>> Remote, 3 = AnimaX, 4 = IgorPlug) (int)
>> parm:           io:I/O address base (0x3f8 or 0x2f8) (int)
>> parm:           irq:Interrupt (4 or 3) (int)
>> parm:           share_irq:Share interrupts (0 = off, 1 = on) (bool)
>> parm:           sense:Override autodetection of IR receiver circuit (0 =
>> active high, 1 = active low ) (bool)
>> parm:           txsense:Sense of transmitter circuit (0 = active high, 1
>> = active low ) (bool)
>> parm:           softcarrier:Software carrier (0 = off, 1 = on) (bool)
>> parm:           debug:Enable debugging messages (bool)
>>
>>
>> It seems so that everything is in the right place but I cannot get it
>> working. Any clues?
>>
>> Thanks
>> Manfred
>>
>>
>
> Hi,
> I have now installed the latest lirc version (lirc-0.9.0.tar.bz2).
>
> Now I get this result:
>
> mannitec02:/usr/local/src/lirc-0.9.0# modprobe -v lirc_serial
> insmod /lib/modules/3.2.7.20120307/misc/lirc_serial.ko
> ERROR: could not insert 'lirc_serial': Invalid argument
>
>
> and out of dmesg:
>
> lirc_dev: IR Remote Control driver registered, major 250
> lirc_serial: disagrees about version of symbol lirc_dev_fop_ioctl
> lirc_serial: Unknown symbol lirc_dev_fop_ioctl (err -22)
> lirc_serial: disagrees about version of symbol lirc_register_driver
> lirc_serial: Unknown symbol lirc_register_driver (err -22)
> lirc_serial: disagrees about version of symbol lirc_dev_fop_read
> lirc_serial: Unknown symbol lirc_dev_fop_read (err -22)
> lirc_serial: disagrees about version of symbol lirc_dev_fop_poll
> lirc_serial: Unknown symbol lirc_dev_fop_poll (err -22)
> lirc_serial: disagrees about version of symbol lirc_dev_fop_open
> lirc_serial: Unknown symbol lirc_dev_fop_open (err -22)
> lirc_serial: disagrees about version of symbol lirc_dev_fop_close
> lirc_serial: Unknown symbol lirc_dev_fop_close (err -22)
>
>
> Is the lirc Software not compatible to the new kernel or have I missed
> something else? During the ./setup.sh of the lirc software there has has
> nothing changed in my /etc/lirc directory. Should it with the new Version?
>
> I'm a little bit lost....
>
> regards
> Manfred
>

Ok, its me again. I've got it now by my own. I use now the staging 
drivers and they worked for me.

bye

-- 
-------                   Manfred Schmidt-Voigt                  -------
-----                        www.mannitec.de                       -----
-------          mailto:man...@ma...        -------

Re: lirc_serial

[Manfred Schmidt-V. <man...@ma...>]

On 07.03.2012 17:44, Manfred Schmidt-Voigt wrote:
> Hello List,
>
> I just jumped to kernel 3.2.7 on my Debian Sid system and tried to
> reconfigure LIRC for that again. But I got the following problems:
>
>
> mannitec02:/usr/local/src/lirc-0.9.0-pre1# uname -a
> Linux mannitec02 3.2.7.20120307 #1 SMP Wed Mar 7 15:05:35 CET 2012 i686
> GNU/Linux
>
> mannitec02:/usr/local/src/lirc-0.9.0-pre1# modprobe lirc_dev
>
> mannitec02:/usr/local/src/lirc-0.9.0-pre1# modprobe lirc_serial
> ERROR: could not insert 'lirc_serial': Exec format error
>
> mannitec02:/usr/local/src/lirc-0.9.0-pre1# modinfo lirc_serial
> filename:       /lib/modules/3.2.7.20120307/misc/lirc_serial.ko
> license:        GPL
> author:         Ralph Metzler, Trent Piepho, Ben Pfaff, Christoph
> Bartelmus, Andrei Tanas
> description:    Infra-red receiver driver for serial ports.
> depends:        lirc_dev
> vermagic:       2.6.37.20110219.1 SMP mod_unload modversions CORE2
> parm:           type:Hardware type (0 = home-brew, 1 = IRdeo, 2 = IRdeo
> Remote, 3 = AnimaX, 4 = IgorPlug) (int)
> parm:           io:I/O address base (0x3f8 or 0x2f8) (int)
> parm:           irq:Interrupt (4 or 3) (int)
> parm:           share_irq:Share interrupts (0 = off, 1 = on) (bool)
> parm:           sense:Override autodetection of IR receiver circuit (0 =
> active high, 1 = active low ) (bool)
> parm:           txsense:Sense of transmitter circuit (0 = active high, 1
> = active low ) (bool)
> parm:           softcarrier:Software carrier (0 = off, 1 = on) (bool)
> parm:           debug:Enable debugging messages (bool)
>
>
> It seems so that everything is in the right place but I cannot get it
> working. Any clues?
>
> Thanks
> Manfred
>
>

Hi,
I have now installed the latest lirc version (lirc-0.9.0.tar.bz2).

Now I get this result:

mannitec02:/usr/local/src/lirc-0.9.0# modprobe -v lirc_serial
insmod /lib/modules/3.2.7.20120307/misc/lirc_serial.ko
ERROR: could not insert 'lirc_serial': Invalid argument


and out of dmesg:

lirc_dev: IR Remote Control driver registered, major 250
lirc_serial: disagrees about version of symbol lirc_dev_fop_ioctl
lirc_serial: Unknown symbol lirc_dev_fop_ioctl (err -22)
lirc_serial: disagrees about version of symbol lirc_register_driver
lirc_serial: Unknown symbol lirc_register_driver (err -22)
lirc_serial: disagrees about version of symbol lirc_dev_fop_read
lirc_serial: Unknown symbol lirc_dev_fop_read (err -22)
lirc_serial: disagrees about version of symbol lirc_dev_fop_poll
lirc_serial: Unknown symbol lirc_dev_fop_poll (err -22)
lirc_serial: disagrees about version of symbol lirc_dev_fop_open
lirc_serial: Unknown symbol lirc_dev_fop_open (err -22)
lirc_serial: disagrees about version of symbol lirc_dev_fop_close
lirc_serial: Unknown symbol lirc_dev_fop_close (err -22)


Is the lirc Software not compatible to the new kernel or have I missed 
something else? During the ./setup.sh of the lirc software there has has 
nothing changed in my /etc/lirc directory. Should it with the new Version?

I'm a little bit lost....

regards
Manfred

-- 
-------                   Manfred Schmidt-Voigt                  -------
-----                        www.mannitec.de                       -----
-------          mailto:man...@ma...        -------

setup additional buttons on programmable remote?

[Jim S. <jsk...@sb...>]

I am probably overthinking this but wondering what the cleanest way to set up some extra buttons on a learning remote.  One thing I want to do is control a matrix switch.  For the DVD player I want to make the unused a/b (input) switch execute a script to switch the input to the DVD.  I have the script working.  My question is what code to learn for the a/b button.  I could just pick up a old remote from a different brand and learn a key but that means I need to learn the remote and setup a new section for it in my conf file.  But then the button wouldn't be grouped with the DVD buttons in the conf file and could get lost.  I could use an obscure button from the DVD remote - it has tons of buttons and I have to set up a conf for it already.  Or I suppose I could look at the DVD codes and make up something similar but different from all the rest, have LIRC send it out and capture it with the learning remote.
 
BTW, the remote is JP1 capable by adding a connector but I haven't messed with JP1 (yet).  Would prefer a non-JP1 solution.