From: Sandell, A. <and...@lo...> - 2009-11-16 22:48:55
|
Hi, just got an IMON Knob IR receiver together with a fancy remote, actually i just wanted the receiver and got the remote at the same time. I have connected it to my fresh system (ASRock ION330) with Ubuntu 9.10 (2.6.31) which is going to run XBMC. After installing LIRCD 0.8.6, running the setup tool (using the correct driver), compiling and installing according to the documentation i get a strange problem. Each time i press a key on my remote i get a different code, which of course makes it hard for lirc to decode it. if i press the play button on the imon remote three times i get the following from mode2 --raw -d/dev/lirc0 (i have inserted a newline after each keypress to make it easier to see): code: 0x2a8115b7008d2101 code: 0x2a8155b700742101 code: 0x2a8115b700252101 code: 0x2a8155b7007d2101 code: 0x2a8115b700262101 code: 0x2a8155b7007a2101 And if i press the button 1 three times i get (once again inserted newlines): code: 0x28b595b700202101 code: 0x28b5d5b700fb2101 code: 0x28b595b700b12101 code: 0x28b5d5b700f22101 code: 0x28b595b700a72101 code: 0x28b5d5b700f42101 If i take my samsung remote (BN59-00937A) and press the red button three times i get: code: 0x03ef6676009e2101 code: 0xd997bb3700162101 code: 0x36ffffff00d32101 code: 0x03ef6cde008c2101 code: 0x7337bb3700032101 code: 0x76ffffff00ce2101 code: 0x03ef66fe00912101 code: 0xd337bb3700022101 code: 0x33ffffff00dc2101 This is obviously hard for lircd to decode. What am i doing wrong here??? I have attached some additional info below. Output from starting lirc-imon with modprobe lirc-imon -v -debug=1: Nov 16 22:02:24 anders-desktop kernel: [48171.444483] lirc_dev: IR Remote Control driver registered, major 61 Nov 16 22:02:24 anders-desktop kernel: [48171.515304] lirc_imon: Driver for SoundGraph iMON MultiMedia IR/Display, v0.6 Nov 16 22:02:24 anders-desktop kernel: [48171.515364] lirc_imon: imon_probe: found iMON device (15c2:ffdc, intf0) Nov 16 22:02:24 anders-desktop kernel: [48171.515372] lirc_imon: imon_probe: found IR endpoint Nov 16 22:02:24 anders-desktop kernel: [48171.515378] lirc_imon: imon_probe: found display endpoint Nov 16 22:02:24 anders-desktop kernel: [48171.515386] lirc_imon: imon_probe: ir_onboard_decode: 1 Nov 16 22:02:24 anders-desktop kernel: [48171.515392] lirc_imon: imon_probe: vfd_proto_6p: 1 Nov 16 22:02:24 anders-desktop kernel: [48171.515405] lirc_dev: lirc_register_driver: sample_rate: 0 Nov 16 22:02:24 anders-desktop kernel: [48171.515542] lirc_imon: Registered iMON driver (lirc minor: 0) Nov 16 22:02:24 anders-desktop kernel: [48171.515696] input: iMON PAD IR Mouse (15c2:ffdc) as /devices/pci0000:00/0000:00:04.0/usb2/2-5/2-5:1.0/input/input11 Nov 16 22:02:24 anders-desktop kernel: [48171.515895] lirc_imon: imon_probe: Registering iMON display with sysfs Nov 16 22:02:24 anders-desktop kernel: [48171.518615] lirc_imon: Configuring IR receiver for iMON protocol Nov 16 22:02:24 anders-desktop kernel: [48171.526606] lirc_imon: iMON device (15c2:ffdc, intf0) on usb<2:4> initialized Nov 16 22:02:24 anders-desktop kernel: [48171.526721] usbcore: registered new interface driver lirc_imon Nov 16 22:04:28 anders-desktop kernel: [48295.787618] lirc_imon: IR port opened Output from lsusb: Bus 002 Device 004: ID 15c2:ffdc SoundGraph Inc. iMON PAD Remote Controller Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x15c2 SoundGraph Inc. idProduct 0xffdc iMON PAD Remote Controller bcdDevice 0.00 iManufacturer 0 iProduct 0 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 41 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 0 (Defined at Interface level) bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 ** UNRECOGNIZED: 09 21 00 01 00 01 22 25 00 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 10 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 10 cannot read device status, Operation not permitted (1) Regards, Anders |
From: Jarod W. <ja...@wi...> - 2009-11-17 02:19:47
|
On 11/16/2009 04:58 PM, Sandell, Anders wrote: > Hi, > > just got an IMON Knob IR receiver together with a fancy remote, actually i just wanted the receiver and got the remote at the same time. > > I have connected it to my fresh system (ASRock ION330) with Ubuntu 9.10 (2.6.31) which is going to run XBMC. After installing LIRCD 0.8.6, running the setup tool (using the correct driver), compiling and installing according to the documentation i get a strange problem. Each time i press a key on my remote i get a different code, which of course makes it hard for lirc to decode it. > > if i press the play button on the imon remote three times i get the following from mode2 --raw -d/dev/lirc0 (i have inserted a newline after each keypress to make it easier to see): > > code: 0x2a8115b7008d2101 > code: 0x2a8155b700742101 > > code: 0x2a8115b700252101 > code: 0x2a8155b7007d2101 > > code: 0x2a8115b700262101 > code: 0x2a8155b7007a2101 > > And if i press the button 1 three times i get (once again inserted newlines): > > code: 0x28b595b700202101 > code: 0x28b5d5b700fb2101 > > code: 0x28b595b700b12101 > code: 0x28b5d5b700f22101 > > code: 0x28b595b700a72101 > code: 0x28b5d5b700f42101 That all looks sane. The Knob config only uses 32-bit values, only the first half of those strings is matched. The first code in each pair is "button pressed", the second is "button released". > If i take my samsung remote (BN59-00937A) and press the red button three times i get: > > code: 0x03ef6676009e2101 > code: 0xd997bb3700162101 > code: 0x36ffffff00d32101 > > code: 0x03ef6cde008c2101 > code: 0x7337bb3700032101 > code: 0x76ffffff00ce2101 > > code: 0x03ef66fe00912101 > code: 0xd337bb3700022101 > code: 0x33ffffff00dc2101 > > This is obviously hard for lircd to decode. What am i doing wrong here??? You're trying to use a non-imon remote with an imon receiver. They don't work well with anything but imon remotes or mce remotes (if the receiver supports being put into mce mode), because the decoding is done onboard the receiver, and then it passes hex values out to userspace. -- Jarod Wilson ja...@wi... |
From: <li...@ba...> - 2009-11-17 16:32:04
|
Hi! Jarod Wilson "ja...@wi..." wrote: > On 11/16/2009 04:58 PM, Sandell, Anders wrote: >> just got an IMON Knob IR receiver together with a fancy remote, actually i >> just wanted the receiver and got the remote at the same time. [...] >> code: 0x28b595b700a72101 >> code: 0x28b5d5b700f42101 > That all looks sane. The Knob config only uses 32-bit values, only the > first half of those strings is matched. If you're referring to the lircd.conf.imon-knob config file, then yes, this only uses 32 bit. But the driver obviously emits 64-bit values, i.e. if you use the lircd.conf.imon-knob config file it won't work at all. Christoph |
From: Jarod W. <ja...@wi...> - 2009-11-17 17:02:13
|
On Nov 17, 2009, at 2:58 AM, Christoph Bartelmus wrote: > Hi! > > Jarod Wilson "ja...@wi..." wrote: >> On 11/16/2009 04:58 PM, Sandell, Anders wrote: >>> just got an IMON Knob IR receiver together with a fancy remote, actually i >>> just wanted the receiver and got the remote at the same time. > [...] >>> code: 0x28b595b700a72101 >>> code: 0x28b5d5b700f42101 > >> That all looks sane. The Knob config only uses 32-bit values, only the >> first half of those strings is matched. > > If you're referring to the lircd.conf.imon-knob config file, then yes, > this only uses 32 bit. But the driver obviously emits 64-bit values, i.e. > if you use the lircd.conf.imon-knob config file it won't work at all. D'oh. So it does. Hm, I thought I looked, and it was still the case that only a few newer receivers were emitting 64-bit values. So a 64-bit config with the last 32 bits masked out would work here... /me needs to completely resync between cvs and git one of these days... -- Jarod Wilson ja...@wi... |
From: Sandell, A. <and...@lo...> - 2009-11-17 17:15:32
|
> -----Ursprungligt meddelande----- > Från: Jarod Wilson [mailto:ja...@wi...] > Skickat: den 17 november 2009 18:02 > Till: lir...@li... > Ämne: Re: problems with IMON Knob IR receiver > > On Nov 17, 2009, at 2:58 AM, Christoph Bartelmus wrote: > > > Hi! > > > > Jarod Wilson "ja...@wi..." wrote: > >> On 11/16/2009 04:58 PM, Sandell, Anders wrote: > >>> just got an IMON Knob IR receiver together with a fancy remote, > actually i > >>> just wanted the receiver and got the remote at the same time. > > [...] > >>> code: 0x28b595b700a72101 > >>> code: 0x28b5d5b700f42101 > > > >> That all looks sane. The Knob config only uses 32-bit values, only > the > >> first half of those strings is matched. > > > > If you're referring to the lircd.conf.imon-knob config file, then > yes, > > this only uses 32 bit. But the driver obviously emits 64-bit values, > i.e. > > if you use the lircd.conf.imon-knob config file it won't work at all. > > D'oh. So it does. Hm, I thought I looked, and it was still the case > that only a few newer receivers were emitting 64-bit values. So a 64- > bit config with the last 32 bits masked out would work here... > > /me needs to completely resync between cvs and git one of these days... > Please forgive me for a maybe stupid question, but how do I create a 64-bit config that masks out the last 32 bits? Anders |
From: Sandell, A. <and...@lo...> - 2009-11-17 13:07:09
|
> -----Ursprungligt meddelande----- > Från: Jarod Wilson [mailto:ja...@wi...] > Skickat: den 17 november 2009 03:24 > Till: Sandell, Anders > Kopia: lir...@li... > Ämne: Re: problems with IMON Knob IR receiver > > On 11/16/2009 04:58 PM, Sandell, Anders wrote: > > Hi, > > > > just got an IMON Knob IR receiver together with a fancy remote, > actually i just wanted the receiver and got the remote at the same > time. > > > > I have connected it to my fresh system (ASRock ION330) with Ubuntu > 9.10 (2.6.31) which is going to run XBMC. After installing LIRCD 0.8.6, > running the setup tool (using the correct driver), compiling and > installing according to the documentation i get a strange problem. Each > time i press a key on my remote i get a different code, which of course > makes it hard for lirc to decode it. > > > > if i press the play button on the imon remote three times i get the > following from mode2 --raw -d/dev/lirc0 (i have inserted a newline > after each keypress to make it easier to see): > > > > code: 0x2a8115b7008d2101 > > code: 0x2a8155b700742101 > > > > code: 0x2a8115b700252101 > > code: 0x2a8155b7007d2101 > > > > code: 0x2a8115b700262101 > > code: 0x2a8155b7007a2101 > > > > And if i press the button 1 three times i get (once again inserted > newlines): > > > > code: 0x28b595b700202101 > > code: 0x28b5d5b700fb2101 > > > > code: 0x28b595b700b12101 > > code: 0x28b5d5b700f22101 > > > > code: 0x28b595b700a72101 > > code: 0x28b5d5b700f42101 > > That all looks sane. The Knob config only uses 32-bit values, only the > first half of those strings is matched. The first code in each pair is > "button pressed", the second is "button released". Ok, that explains it, thanks. > > > If i take my samsung remote (BN59-00937A) and press the red button > three times i get: > > > > code: 0x03ef6676009e2101 > > code: 0xd997bb3700162101 > > code: 0x36ffffff00d32101 > > > > code: 0x03ef6cde008c2101 > > code: 0x7337bb3700032101 > > code: 0x76ffffff00ce2101 > > > > code: 0x03ef66fe00912101 > > code: 0xd337bb3700022101 > > code: 0x33ffffff00dc2101 > > > > This is obviously hard for lircd to decode. What am i doing wrong > here??? > > You're trying to use a non-imon remote with an imon receiver. They > don't > work well with anything but imon remotes or mce remotes (if the > receiver > supports being put into mce mode), because the decoding is done onboard > the receiver, and then it passes hex values out to userspace. > > -- > Jarod Wilson > ja...@wi... Ok, I guess I will have to try to learn my Harmony One the imon remote codes and then use those in VDR/XBMC. After what I have seen that might be a challenge though... Thanks, Anders |
From: Jarod W. <ja...@wi...> - 2009-11-17 13:55:10
|
On Nov 17, 2009, at 8:06 AM, Sandell, Anders wrote: >> -----Ursprungligt meddelande----- >> Från: Jarod Wilson [mailto:ja...@wi...] >> Skickat: den 17 november 2009 03:24 >> Till: Sandell, Anders >> Kopia: lir...@li... >> Ämne: Re: problems with IMON Knob IR receiver >> >> On 11/16/2009 04:58 PM, Sandell, Anders wrote: >>> Hi, >>> >>> just got an IMON Knob IR receiver together with a fancy remote, ... >>> If i take my samsung remote (BN59-00937A) and press the red button >> three times i get: >>> >>> code: 0x03ef6676009e2101 >>> code: 0xd997bb3700162101 >>> code: 0x36ffffff00d32101 >>> >>> code: 0x03ef6cde008c2101 >>> code: 0x7337bb3700032101 >>> code: 0x76ffffff00ce2101 >>> >>> code: 0x03ef66fe00912101 >>> code: 0xd337bb3700022101 >>> code: 0x33ffffff00dc2101 >>> >>> This is obviously hard for lircd to decode. What am i doing wrong >> here??? >> >> You're trying to use a non-imon remote with an imon receiver. They >> don't >> work well with anything but imon remotes or mce remotes (if the >> receiver >> supports being put into mce mode), because the decoding is done onboard >> the receiver, and then it passes hex values out to userspace. > > Ok, I guess I will have to try to learn my Harmony One the imon remote codes and then use those in VDR/XBMC. After what I have seen that might be a challenge though... Not really. I use a Logitech Harmony 880 with an iMON receiver here, no problem. I chose the Antec Veris remote profile in the Harmony database, and it works quite well (the Antec Veris series is basically all rebranded iMON stuff). -- Jarod Wilson ja...@wi... |
From: Jarod W. <ja...@wi...> - 2009-11-17 20:02:01
|
On Nov 17, 2009, at 12:12 PM, Sandell, Anders wrote: >> -----Ursprungligt meddelande----- >> Från: Jarod Wilson [mailto:ja...@wi...] >> Skickat: den 17 november 2009 18:02 >> Till: lir...@li... >> Ämne: Re: problems with IMON Knob IR receiver >> >> On Nov 17, 2009, at 2:58 AM, Christoph Bartelmus wrote: >> >>> Hi! >>> >>> Jarod Wilson "ja...@wi..." wrote: >>>> On 11/16/2009 04:58 PM, Sandell, Anders wrote: >>>>> just got an IMON Knob IR receiver together with a fancy remote, >> actually i >>>>> just wanted the receiver and got the remote at the same time. >>> [...] >>>>> code: 0x28b595b700a72101 >>>>> code: 0x28b5d5b700f42101 >>> >>>> That all looks sane. The Knob config only uses 32-bit values, only >> the >>>> first half of those strings is matched. >>> >>> If you're referring to the lircd.conf.imon-knob config file, then >> yes, >>> this only uses 32 bit. But the driver obviously emits 64-bit values, >> i.e. >>> if you use the lircd.conf.imon-knob config file it won't work at all. >> >> D'oh. So it does. Hm, I thought I looked, and it was still the case >> that only a few newer receivers were emitting 64-bit values. So a 64- >> bit config with the last 32 bits masked out would work here... >> >> /me needs to completely resync between cvs and git one of these days... >> > Please forgive me for a maybe stupid question, but how do I create a 64-bit config that masks out the last 32 bits? Take a look at remotes/imon/lircd.conf.imon-knob in cvs as of just a minute ago, I just hacked together what is hopefully a working config... -- Jarod Wilson ja...@wi... |
From: Sandell, A. <and...@lo...> - 2009-11-18 07:27:59
|
> -----Ursprungligt meddelande----- > Från: Jarod Wilson [mailto:ja...@wi...] > Skickat: den 17 november 2009 21:02 > Till: Sandell, Anders > Kopia: lir...@li... > Ämne: Re: SV: problems with IMON Knob IR receiver > > On Nov 17, 2009, at 12:12 PM, Sandell, Anders wrote: > > >> -----Ursprungligt meddelande----- > >> Från: Jarod Wilson [mailto:ja...@wi...] > >> Skickat: den 17 november 2009 18:02 > >> Till: lir...@li... > >> Ämne: Re: problems with IMON Knob IR receiver > >> > >> On Nov 17, 2009, at 2:58 AM, Christoph Bartelmus wrote: > >> > >>> Hi! > >>> > >>> Jarod Wilson "ja...@wi..." wrote: > >>>> On 11/16/2009 04:58 PM, Sandell, Anders wrote: > >>>>> just got an IMON Knob IR receiver together with a fancy remote, > >> actually i > >>>>> just wanted the receiver and got the remote at the same time. > >>> [...] > >>>>> code: 0x28b595b700a72101 > >>>>> code: 0x28b5d5b700f42101 > >>> > >>>> That all looks sane. The Knob config only uses 32-bit values, only > >> the > >>>> first half of those strings is matched. > >>> > >>> If you're referring to the lircd.conf.imon-knob config file, then > >> yes, > >>> this only uses 32 bit. But the driver obviously emits 64-bit > values, > >> i.e. > >>> if you use the lircd.conf.imon-knob config file it won't work at > all. > >> > >> D'oh. So it does. Hm, I thought I looked, and it was still the case > >> that only a few newer receivers were emitting 64-bit values. So a > 64- > >> bit config with the last 32 bits masked out would work here... > >> > >> /me needs to completely resync between cvs and git one of these > days... > >> > > Please forgive me for a maybe stupid question, but how do I create a > 64-bit config that masks out the last 32 bits? > > Take a look at remotes/imon/lircd.conf.imon-knob in cvs as of just a > minute ago, I just hacked together what is hopefully a working > config... > Thanks, works like a charm! Anders |
From: mnrdk <mik...@th...> - 2009-12-15 20:33:31
|
Jarod Wilson wrote: > > On Nov 17, 2009, at 12:12 PM, Sandell, Anders wrote: > > Take a look at remotes/imon/lircd.conf.imon-knob in cvs as of just a > minute ago, I just hacked together what is hopefully a working config... > > -- > Jarod Wilson > ja...@wi... > YES! I have been trying to get my IMON-PAD remote to work for weeks! Everybody writes about patching. Now almost every button works, except the pad. I have the following keys in /usr/share/lirc/remotes/imon/lircd.conf.imon-knob Mouse_N 0x6902F9B7 Mouse_S 0x6882C1B7 Mouse_W 0x6AFA81B7 Mouse_E 0x68A281B7 These seem popular in most posts. I have added the file /etc/modprobe.d/lirc_imon.conf with the following line: options lirc_imon nomouse=1 (same problem without the line though). Do I need to do anything else to make the pad work? I use lirc 0.8.6 btw Mikkel -- View this message in context: http://old.nabble.com/problems-with-IMON-Knob-IR-receiver-tp26381164p26801308.html Sent from the LIRC mailing list archive at Nabble.com. |
From: Jarod W. <ja...@wi...> - 2009-12-28 06:12:43
|
On Dec 15, 2009, at 3:33 PM, mnrdk wrote: > Jarod Wilson wrote: >> >> On Nov 17, 2009, at 12:12 PM, Sandell, Anders wrote: >> >> Take a look at remotes/imon/lircd.conf.imon-knob in cvs as of just a >> minute ago, I just hacked together what is hopefully a working config... >> > > YES! I have been trying to get my IMON-PAD remote to work for weeks! > Everybody writes about patching. No, no patching needed these days, hasn't been any needed for several months now, if I'm thinking clearly... > Now almost every button works, except the pad. I have the following keys in > /usr/share/lirc/remotes/imon/lircd.conf.imon-knob > > Mouse_N 0x6902F9B7 > Mouse_S 0x6882C1B7 > Mouse_W 0x6AFA81B7 > Mouse_E 0x68A281B7 > > These seem popular in most posts. > > I have added the file /etc/modprobe.d/lirc_imon.conf with the following > line: > options lirc_imon nomouse=1 (same problem without the line though). > > Do I need to do anything else to make the pad work? I use lirc 0.8.6 btw Those are the wrong codes, you need: KEY_UP 0x01008000 # Pad Up KEY_DOWN 0x01007f00 # Pad Down KEY_LEFT 0x01000080 # Pad Left KEY_RIGHT 0x0100007f # Pad Right or possibly: KEY_UP 0x2aa515b7 # Pad Up KEY_DOWN 0x289515b7 # Pad Down KEY_LEFT 0x29a515b7 # Pad Left KEY_RIGHT 0x2ba515b7 # Pad Right The Cursor{Up,Down,Left,Right} values in the config aren't valid anymore. I'll fix that now. What was in there before (and still is, just in case), was for the fabricated values generated by an old pad2keys patch, iirc. We now use some more standardized filtering and pseudo-code generating stuff (the first group of 4 above) and there are some imon remotes that actually have distinct arrow keys (the second group of 4 above). -- Jarod Wilson ja...@wi... |
From: mnrdk <mik...@th...> - 2010-01-05 13:51:10
|
Jarod Wilson wrote: > > Those are the wrong codes, you need: > > KEY_UP 0x01008000 # Pad Up > KEY_DOWN 0x01007f00 # Pad Down > KEY_LEFT 0x01000080 # Pad Left > KEY_RIGHT 0x0100007f # Pad Right > > or possibly: > > KEY_UP 0x2aa515b7 # Pad Up > KEY_DOWN 0x289515b7 # Pad Down > KEY_LEFT 0x29a515b7 # Pad Left > KEY_RIGHT 0x2ba515b7 # Pad Right > > The Cursor{Up,Down,Left,Right} values in the config aren't valid anymore. > I'll fix that now. What was in there before (and still is, just in case), > was for the fabricated values generated by an old pad2keys patch, iirc. We > now use some more standardized filtering and pseudo-code generating stuff > (the first group of 4 above) and there are some imon remotes that actually > have distinct arrow keys (the second group of 4 above). > Sry for the late reply to this. Xmas and all... I actually managed to make the pad work, but have not tried the codes you have supplied. Will do that shortly. What I did was to use irrecord to record the pad-keys, and I only touched the pad while going through the recording process (well, had to use another key for the last step). I then appended the resulting file to the lircd.conf.imon-knob file. The header of this configuration is very different from the header of the original header in the lircd.conf.imon-knob file. I wonder if that did the trick (havent tried the above codes mind you...) begin remote name IMON_KNOB_64 bits 16 eps 30 aeps 100 one 0 0 zero 0 0 pre_data_bits 16 pre_data 0x100 post_data_bits 32 post_data 0x0 gap 71989 toggle_bit_mask 0x2A9795B700CE2101 begin codes KEY_UP 0x8000 KEY_DOWN 0x7F00 KEY_LEFT 0x0080 KEY_RIGHT 0x007F end codes end remote Mikkel -- View this message in context: http://old.nabble.com/problems-with-IMON-Knob-IR-receiver-tp26381164p27026614.html Sent from the LIRC mailing list archive at Nabble.com. |
From: Jarod W. <ja...@wi...> - 2010-01-06 22:51:56
|
On Jan 5, 2010, at 8:50 AM, mnrdk wrote: > Jarod Wilson wrote: >> >> Those are the wrong codes, you need: >> >> KEY_UP 0x01008000 # Pad Up >> KEY_DOWN 0x01007f00 # Pad Down >> KEY_LEFT 0x01000080 # Pad Left >> KEY_RIGHT 0x0100007f # Pad Right >> >> or possibly: >> >> KEY_UP 0x2aa515b7 # Pad Up >> KEY_DOWN 0x289515b7 # Pad Down >> KEY_LEFT 0x29a515b7 # Pad Left >> KEY_RIGHT 0x2ba515b7 # Pad Right >> >> The Cursor{Up,Down,Left,Right} values in the config aren't valid anymore. >> I'll fix that now. What was in there before (and still is, just in case), >> was for the fabricated values generated by an old pad2keys patch, iirc. We >> now use some more standardized filtering and pseudo-code generating stuff >> (the first group of 4 above) and there are some imon remotes that actually >> have distinct arrow keys (the second group of 4 above). >> > > Sry for the late reply to this. Xmas and all... > > I actually managed to make the pad work, but have not tried the codes you > have supplied. Will do that shortly. > > What I did was to use irrecord to record the pad-keys, and I only touched > the pad while going through the recording process (well, had to use another > key for the last step). > > I then appended the resulting file to the lircd.conf.imon-knob file. The > header of this configuration is very different from the header of the > original header in the lircd.conf.imon-knob file. I wonder if that did the > trick (havent tried the above codes mind you...) > > begin remote > name IMON_KNOB_64 > bits 16 > eps 30 > aeps 100 > > one 0 0 > zero 0 0 > pre_data_bits 16 > pre_data 0x100 > post_data_bits 32 > post_data 0x0 > gap 71989 > toggle_bit_mask 0x2A9795B700CE2101 > > begin codes > KEY_UP 0x8000 > KEY_DOWN 0x7F00 > KEY_LEFT 0x0080 > KEY_RIGHT 0x007F > end codes > end remote That should be equivalent to the first set of codes I added. -- Jarod Wilson ja...@wi... |