From: Spencer F. <fow...@gm...> - 2009-07-08 16:01:24
|
I purchased an MCE receiver a while back (works great using the mceusb2 driver). On another computer I have Windows running and I installed EventGhost (http://www.eventghost.org/) which did a great job in windows of picking up the receiver. However, I noticed that EventGhost also picked up the commands my Pioneer remote sent to my home audio receiver (not plugged into the computer). Turns out if I point the Pioneer remote at the MCE receiver and push buttons, I get valid responses (EventGhost shows them as things like: MceRemote:A802 instead of MceRemote:Up, etc...) So I was easily able to update my EventGhost configuration to accept responses from either the MCE remote or the Pioneer remote. I'd like do to the same with LIRC. I know the MCE module receives the commands from the Pioneer remote because I've seen it work in Windows, but how can I figure out which driver LIRC needs so that irw, or mode2, or irrecord will detect and print out the commands received from the Pioneer remote -- --Spencer Fowers ----Fowie dot Com - Home of SF Designs ----http://www.fowie.com |
From: Spencer F. <fow...@gm...> - 2009-07-08 16:17:36
|
I purchased an MCE receiver a while back (works great using the mceusb2 driver). On another computer I have Windows running and I installed EventGhost (http://www.eventghost.org/) which did a great job in windows of picking up the receiver. However, I noticed that EventGhost also picked up the commands my Pioneer remote sent to my home audio receiver (not plugged into the computer). Turns out if I point the Pioneer remote at the MCE receiver and push buttons, I get valid responses (EventGhost shows them as things like: MceRemote:A802 instead of MceRemote:Up, etc...) So I was easily able to update my EventGhost configuration to accept responses from either the MCE remote or the Pioneer remote. I'd like do to the same with LIRC. I know the MCE module receives the commands from the Pioneer remote because I've seen it work in Windows, but how can I figure out which driver LIRC needs so that irw, or mode2, or irrecord will detect and print out the commands received from the Pioneer remote? Spencer |
From: Jarod W. <ja...@wi...> - 2009-07-08 16:07:31
|
On Jul 8, 2009, at 12:01 PM, Spencer Fowers wrote: > I purchased an MCE receiver a while back (works great using the > mceusb2 > driver). On another computer I have Windows running and I installed > EventGhost (http://www.eventghost.org/) which did a great job in > windows > of picking up the receiver. However, I noticed that EventGhost also > picked up the commands my Pioneer remote sent to my home audio > receiver > (not plugged into the computer). Turns out if I point the Pioneer > remote at the MCE receiver and push buttons, I get valid responses > (EventGhost shows them as things like: MceRemote:A802 instead of > MceRemote:Up, etc...) So I was easily able to update my EventGhost > configuration to accept responses from either the MCE remote or the > Pioneer remote. I'd like do to the same with LIRC. I know the MCE > module receives the commands from the Pioneer remote because I've seen > it work in Windows, but how can I figure out which driver LIRC needs It still needs the mceusb driver. The driver is for the receiver, not the remote. > so > that irw, or mode2, or irrecord will detect and print out the commands > received from the Pioneer remote All you need is another remote definition (or expand the current one) for your Pioneer remote in your lircd.conf. -- Jarod Wilson ja...@wi... |
From: Spencer F. <fow...@gm...> - 2009-07-08 17:48:16
|
I tried running irrecord and mode2. mode2 doesn't show anything, is there some lower-level method I could use to see what the IR receiver actually gets, regardless of what driver/remote is installed? On Wed, 2009-07-08 at 13:32 -0400, Jarod Wilson wrote: > Try running mode2 then, I guess, see if it sees anything. I'm not > really all that familiar with creating remote configs, I've only had > to do it once or twice myself, and that was long ago. Most everything > I've got Just Works(tm) using configs already available. > > > On Jul 8, 2009, at 1:30 PM, Spencer Fowers wrote: > > > That's my problem--irrecord doesn't output anything when I push > > buttons > > on the Pioneer remote? > > > > On Wed, 2009-07-08 at 13:24 -0400, Jarod Wilson wrote: > >> Look and see if there's already one in http://lirc.org/remotes/ > >> pioneer/ that'll work, and if not, 'man irrecord'. > >> > >> > >> On Jul 8, 2009, at 12:10 PM, Spencer Fowers wrote: > >> > >>> Could you point me towards a how-to or something similar to create > >>> that > >>> remote definition? > >>> > >>> Thanks > >>> > >>> Spencer > >>> > >>> On Wed, 2009-07-08 at 12:06 -0400, Jarod Wilson wrote: > >>>> On Jul 8, 2009, at 12:01 PM, Spencer Fowers wrote: > >>>> > >>>>> I purchased an MCE receiver a while back (works great using the > >>>>> mceusb2 > >>>>> driver). On another computer I have Windows running and I > >>>>> installed > >>>>> EventGhost (http://www.eventghost.org/) which did a great job in > >>>>> windows > >>>>> of picking up the receiver. However, I noticed that EventGhost > >>>>> also > >>>>> picked up the commands my Pioneer remote sent to my home audio > >>>>> receiver > >>>>> (not plugged into the computer). Turns out if I point the Pioneer > >>>>> remote at the MCE receiver and push buttons, I get valid responses > >>>>> (EventGhost shows them as things like: MceRemote:A802 instead of > >>>>> MceRemote:Up, etc...) So I was easily able to update my > >>>>> EventGhost > >>>>> configuration to accept responses from either the MCE remote or > >>>>> the > >>>>> Pioneer remote. I'd like do to the same with LIRC. I know the > >>>>> MCE > >>>>> module receives the commands from the Pioneer remote because I've > >>>>> seen > >>>>> it work in Windows, but how can I figure out which driver LIRC > >>>>> needs > >>>> > >>>> It still needs the mceusb driver. The driver is for the receiver, > >>>> not > >>>> the remote. > >>>> > >>>>> so > >>>>> that irw, or mode2, or irrecord will detect and print out the > >>>>> commands > >>>>> received from the Pioneer remote > >>>> > >>>> All you need is another remote definition (or expand the current > >>>> one) > >>>> for your Pioneer remote in your lircd.conf. > >>>> > >>>> > >>> > >> > > > |
From: <li...@ba...> - 2009-07-08 18:04:13
|
Hi! Spencer Fowers "fow...@gm..." wrote: > I tried running irrecord and mode2. mode2 doesn't show anything, is > there some lower-level method I could use to see what the IR receiver > actually gets, regardless of what driver/remote is installed? There is no lower-level method. If mode2 does not show anything, the receiver is not getting anything. But I'd be very surprised if you get something with the original MCE remote and get nothing with the Pioneer remote. Either both should work or none. Well, actually both should work if everything is set up right. Christoph |
From: Spencer F. <fow...@gm...> - 2009-07-09 04:16:59
|
Ok, I can get output into irrecord and using mode2, but it doesn't seem to find any codes? I perform all of the steps of irrecord and get this: bits: 32 flags SPACE_ENC eps 30 aeps 100 header 8483 4224 one 551 1553 zero 551 507 ptrail 548 toggle_bit_mask 0x0 begin codes 1 0xD52A3CC3 2 0xD52A3CC3 3 0xD52A3CC3 4 0xD52A3CC3 5 0xD52A3CC3 6 0xD52A3CC3 ... basically all of the number buttons showed the same code? I've noticed in EventGhost that all of the buttons show the first half of the same code (i.e. EventGhost will show that I pressed Remote.A7B3 and Remote.B389 where A7B3 will show up for every button that I press, but B389 will be unique for each button. Make sense?) Any other help with this? How can I find out more information? mode2 showed a LOT of information, but I"m not sure how to make sense of it all. On Wed, 2009-07-08 at 20:03 +0200, Christoph Bartelmus wrote: > Hi! > > Spencer Fowers "fow...@gm..." wrote: > > > I tried running irrecord and mode2. mode2 doesn't show anything, is > > there some lower-level method I could use to see what the IR receiver > > actually gets, regardless of what driver/remote is installed? > > There is no lower-level method. If mode2 does not show anything, the > receiver is not getting anything. > But I'd be very surprised if you get something with the original MCE > remote and get nothing with the Pioneer remote. Either both should work or > none. Well, actually both should work if everything is set up right. > > Christoph > > ------------------------------------------------------------------------------ > Enter the BlackBerry Developer Challenge > This is your chance to win up to $100,000 in prizes! For a limited time, > vendors submitting new applications to BlackBerry App World(TM) will have > the opportunity to enter the BlackBerry Developer Challenge. See full prize > details at: http://p.sf.net/sfu/Challenge |
From: Jarod W. <ja...@wi...> - 2009-07-09 15:01:04
|
On Jul 9, 2009, at 12:16 AM, Spencer Fowers wrote: > Ok, I can get output into irrecord and using mode2, but it doesn't > seem > to find any codes? I perform all of the steps of irrecord and get > this: > bits: 32 > flags SPACE_ENC > eps 30 > aeps 100 > > header 8483 4224 > one 551 1553 > zero 551 507 > ptrail 548 > toggle_bit_mask 0x0 > > begin codes > 1 0xD52A3CC3 > 2 0xD52A3CC3 > 3 0xD52A3CC3 > 4 0xD52A3CC3 > 5 0xD52A3CC3 > 6 0xD52A3CC3 > ... > basically all of the number buttons showed the same code? I've noticed > in EventGhost that all of the buttons show the first half of the same > code (i.e. EventGhost will show that I pressed Remote.A7B3 and > Remote.B389 where A7B3 will show up for every button that I press, but > B389 will be unique for each button. Make sense?) > > Any other help with this? How can I find out more information? mode2 > showed a LOT of information, but I"m not sure how to make sense of it > all. That all actually sounds rather similar to this: http://lirc.sourceforge.net/remotes/pioneer/AXD-7381 I'm not completely sure how to make sense of the double-entries for most of the buttons there, but it seems quite relevant... -- Jarod Wilson ja...@wi... |
From: Spencer F. <fow...@gm...> - 2009-07-09 15:41:54
|
Wow, that got it exactly. Remote works! Thanks for the help! On Thu, 2009-07-09 at 11:00 -0400, Jarod Wilson wrote: > On Jul 9, 2009, at 12:16 AM, Spencer Fowers wrote: > > > Ok, I can get output into irrecord and using mode2, but it doesn't > > seem > > to find any codes? I perform all of the steps of irrecord and get > > this: > > bits: 32 > > flags SPACE_ENC > > eps 30 > > aeps 100 > > > > header 8483 4224 > > one 551 1553 > > zero 551 507 > > ptrail 548 > > toggle_bit_mask 0x0 > > > > begin codes > > 1 0xD52A3CC3 > > 2 0xD52A3CC3 > > 3 0xD52A3CC3 > > 4 0xD52A3CC3 > > 5 0xD52A3CC3 > > 6 0xD52A3CC3 > > ... > > basically all of the number buttons showed the same code? I've noticed > > in EventGhost that all of the buttons show the first half of the same > > code (i.e. EventGhost will show that I pressed Remote.A7B3 and > > Remote.B389 where A7B3 will show up for every button that I press, but > > B389 will be unique for each button. Make sense?) > > > > Any other help with this? How can I find out more information? mode2 > > showed a LOT of information, but I"m not sure how to make sense of it > > all. > > That all actually sounds rather similar to this: > > http://lirc.sourceforge.net/remotes/pioneer/AXD-7381 > > I'm not completely sure how to make sense of the double-entries for > most of the buttons there, but it seems quite relevant... > |
From: Jarod W. <ja...@wi...> - 2009-07-08 17:57:40
|
Load the module with the added param 'debug=1', and you should see lines in dmesg similar to 'lirc_mceusb[x]: data received: xx xx xx xx (length=x)' On Jul 8, 2009, at 1:48 PM, Spencer Fowers wrote: > I tried running irrecord and mode2. mode2 doesn't show anything, is > there some lower-level method I could use to see what the IR receiver > actually gets, regardless of what driver/remote is installed? > > > > On Wed, 2009-07-08 at 13:32 -0400, Jarod Wilson wrote: >> Try running mode2 then, I guess, see if it sees anything. I'm not >> really all that familiar with creating remote configs, I've only had >> to do it once or twice myself, and that was long ago. Most everything >> I've got Just Works(tm) using configs already available. >> >> >> On Jul 8, 2009, at 1:30 PM, Spencer Fowers wrote: >> >>> That's my problem--irrecord doesn't output anything when I push >>> buttons >>> on the Pioneer remote? >>> >>> On Wed, 2009-07-08 at 13:24 -0400, Jarod Wilson wrote: >>>> Look and see if there's already one in http://lirc.org/remotes/ >>>> pioneer/ that'll work, and if not, 'man irrecord'. >>>> >>>> >>>> On Jul 8, 2009, at 12:10 PM, Spencer Fowers wrote: >>>> >>>>> Could you point me towards a how-to or something similar to create >>>>> that >>>>> remote definition? >>>>> >>>>> Thanks >>>>> >>>>> Spencer >>>>> >>>>> On Wed, 2009-07-08 at 12:06 -0400, Jarod Wilson wrote: >>>>>> On Jul 8, 2009, at 12:01 PM, Spencer Fowers wrote: >>>>>> >>>>>>> I purchased an MCE receiver a while back (works great using the >>>>>>> mceusb2 >>>>>>> driver). On another computer I have Windows running and I >>>>>>> installed >>>>>>> EventGhost (http://www.eventghost.org/) which did a great job in >>>>>>> windows >>>>>>> of picking up the receiver. However, I noticed that EventGhost >>>>>>> also >>>>>>> picked up the commands my Pioneer remote sent to my home audio >>>>>>> receiver >>>>>>> (not plugged into the computer). Turns out if I point the >>>>>>> Pioneer >>>>>>> remote at the MCE receiver and push buttons, I get valid >>>>>>> responses >>>>>>> (EventGhost shows them as things like: MceRemote:A802 instead >>>>>>> of >>>>>>> MceRemote:Up, etc...) So I was easily able to update my >>>>>>> EventGhost >>>>>>> configuration to accept responses from either the MCE remote or >>>>>>> the >>>>>>> Pioneer remote. I'd like do to the same with LIRC. I know the >>>>>>> MCE >>>>>>> module receives the commands from the Pioneer remote because >>>>>>> I've >>>>>>> seen >>>>>>> it work in Windows, but how can I figure out which driver LIRC >>>>>>> needs >>>>>> >>>>>> It still needs the mceusb driver. The driver is for the receiver, >>>>>> not >>>>>> the remote. >>>>>> >>>>>>> so >>>>>>> that irw, or mode2, or irrecord will detect and print out the >>>>>>> commands >>>>>>> received from the Pioneer remote >>>>>> >>>>>> All you need is another remote definition (or expand the current >>>>>> one) >>>>>> for your Pioneer remote in your lircd.conf. >>>>>> >>>>>> >>>>> >>>> >>> >> > -- Jarod Wilson ja...@wi... |
From: Spencer F. <fow...@gm...> - 2009-07-08 22:20:48
|
Ok, thanks. When I press the "up" key on my MCE remote I get: lirc_mceusb2[2]: data received 81 79 (length=2) lirc_mceusb2[2]: data received 81 b6 (length=2) lirc_mceusb2[2]: data received 81 11 (length=2) lirc_mceusb2[2]: data received 83 89 09 89 (length=4) lirc_mceusb2[2]: data received 84 09 89 11 8a (length=5) lirc_mceusb2[2]: data received 81 11 (length=2) lirc_mceusb2[2]: data received 84 9b 12 89 08 (length=5) lirc_mceusb2[2]: data received 84 89 09 89 09 (length=5) lirc_mceusb2[2]: data received 85 89 09 89 08 89 (length=6) lirc_mceusb2[2]: data received 84 09 89 09 89 (length=5) lirc_mceusb2[2]: data received 85 09 89 08 89 09 (length=6) lirc_mceusb2[2]: data received 83 92 09 89 (length=4) lirc_mceusb2[2]: data received 84 09 89 08 89 (length=5) lirc_mceusb2[2]: data received 84 12 89 09 89 (length=5) lirc_mceusb2[2]: data received 85 08 8a 08 89 09 (length=6) lirc_mceusb2[2]: data received 82 92 12 (length=3) lirc_mceusb2[2]: data received 85 89 08 89 09 89 (length=6) lirc_mceusb2[2]: data received 83 09 89 08 (length=4) lirc_mceusb2[2]: data received 85 92 09 89 09 89 (length=6) lirc_mceusb2[2]: data received 83 09 89 12 (length=4) lirc_mceusb2[2]: data received 81 88 (length=2) and then I just get the same codes when I don't press anything: lirc_mceusb2[2]: data received 81 7f (length=2) lirc_mceusb2[2]: data received 81 7f (length=2) lirc_mceusb2[2]: data received 81 7f (length=2) lirc_mceusb2[2]: data received 81 7f (length=2) lirc_mceusb2[2]: data received 81 7f (length=2) lirc_mceusb2[2]: data received 81 7f (length=2) lirc_mceusb2[2]: data received 81 7f (length=2) lirc_mceusb2[2]: data received 81 7f (length=2) lirc_mceusb2[2]: data received 81 7f (length=2) lirc_mceusb2[2]: data received 81 7f (length=2) lirc_mceusb2[2]: data received 81 7f (length=2) lirc_mceusb2[2]: data received 81 7f (length=2) lirc_mceusb2[2]: data received 81 7f (length=2) lirc_mceusb2[2]: data received 81 7f (length=2) lirc_mceusb2[2]: data received 81 7f (length=2) lirc_mceusb2[2]: data received 81 5f 80 (length=3) ... but when I look at the /usr/share/lirc/remotes/mceusb/lircd.conf.mceusb the definition for up is: Up 0x00007be1 how do I make sense of all this output? On Wed, 2009-07-08 at 13:56 -0400, Jarod Wilson wrote: > Load the module with the added param 'debug=1', and you should see > lines in dmesg similar to 'lirc_mceusb[x]: data received: xx xx xx xx > (length=x)' > > > On Jul 8, 2009, at 1:48 PM, Spencer Fowers wrote: > > > I tried running irrecord and mode2. mode2 doesn't show anything, is > > there some lower-level method I could use to see what the IR receiver > > actually gets, regardless of what driver/remote is installed? > > > > > > > > On Wed, 2009-07-08 at 13:32 -0400, Jarod Wilson wrote: > >> Try running mode2 then, I guess, see if it sees anything. I'm not > >> really all that familiar with creating remote configs, I've only had > >> to do it once or twice myself, and that was long ago. Most everything > >> I've got Just Works(tm) using configs already available. > >> > >> > >> On Jul 8, 2009, at 1:30 PM, Spencer Fowers wrote: > >> > >>> That's my problem--irrecord doesn't output anything when I push > >>> buttons > >>> on the Pioneer remote? > >>> > >>> On Wed, 2009-07-08 at 13:24 -0400, Jarod Wilson wrote: > >>>> Look and see if there's already one in http://lirc.org/remotes/ > >>>> pioneer/ that'll work, and if not, 'man irrecord'. > >>>> > >>>> > >>>> On Jul 8, 2009, at 12:10 PM, Spencer Fowers wrote: > >>>> > >>>>> Could you point me towards a how-to or something similar to create > >>>>> that > >>>>> remote definition? > >>>>> > >>>>> Thanks > >>>>> > >>>>> Spencer > >>>>> > >>>>> On Wed, 2009-07-08 at 12:06 -0400, Jarod Wilson wrote: > >>>>>> On Jul 8, 2009, at 12:01 PM, Spencer Fowers wrote: > >>>>>> > >>>>>>> I purchased an MCE receiver a while back (works great using the > >>>>>>> mceusb2 > >>>>>>> driver). On another computer I have Windows running and I > >>>>>>> installed > >>>>>>> EventGhost (http://www.eventghost.org/) which did a great job in > >>>>>>> windows > >>>>>>> of picking up the receiver. However, I noticed that EventGhost > >>>>>>> also > >>>>>>> picked up the commands my Pioneer remote sent to my home audio > >>>>>>> receiver > >>>>>>> (not plugged into the computer). Turns out if I point the > >>>>>>> Pioneer > >>>>>>> remote at the MCE receiver and push buttons, I get valid > >>>>>>> responses > >>>>>>> (EventGhost shows them as things like: MceRemote:A802 instead > >>>>>>> of > >>>>>>> MceRemote:Up, etc...) So I was easily able to update my > >>>>>>> EventGhost > >>>>>>> configuration to accept responses from either the MCE remote or > >>>>>>> the > >>>>>>> Pioneer remote. I'd like do to the same with LIRC. I know the > >>>>>>> MCE > >>>>>>> module receives the commands from the Pioneer remote because > >>>>>>> I've > >>>>>>> seen > >>>>>>> it work in Windows, but how can I figure out which driver LIRC > >>>>>>> needs > >>>>>> > >>>>>> It still needs the mceusb driver. The driver is for the receiver, > >>>>>> not > >>>>>> the remote. > >>>>>> > >>>>>>> so > >>>>>>> that irw, or mode2, or irrecord will detect and print out the > >>>>>>> commands > >>>>>>> received from the Pioneer remote > >>>>>> > >>>>>> All you need is another remote definition (or expand the current > >>>>>> one) > >>>>>> for your Pioneer remote in your lircd.conf. > >>>>>> > >>>>>> > >>>>> > >>>> > >>> > >> > > > |
From: Jarod W. <ja...@wi...> - 2009-07-09 14:26:14
|
On Jul 8, 2009, at 6:20 PM, Spencer Fowers wrote: > Ok, thanks. > When I press the "up" key on my MCE remote I get: > lirc_mceusb2[2]: data received 81 79 (length=2) > lirc_mceusb2[2]: data received 81 b6 (length=2) > lirc_mceusb2[2]: data received 81 11 (length=2) > lirc_mceusb2[2]: data received 83 89 09 89 (length=4) > lirc_mceusb2[2]: data received 84 09 89 11 8a (length=5) > lirc_mceusb2[2]: data received 81 11 (length=2) > lirc_mceusb2[2]: data received 84 9b 12 89 08 (length=5) > lirc_mceusb2[2]: data received 84 89 09 89 09 (length=5) ... > but when I look at the /usr/share/lirc/remotes/mceusb/ > lircd.conf.mceusb > the definition for up is: > > Up 0x00007be1 > > how do I make sense of all this output? For the most part, you don't. What you see in dmesg is more or less raw IR data, which gets fed to lircd, which then decodes it. However, the format of the stuff there is this: The 0x8x part is a header packet that says 'this is a relevant data packet, of length x (excluding it itself). So for example, 0x84 followed by 4 additional bytes of actual IR data for a length=5 receive. If the actual data is 0x7f, its a space byte, else its a pulse byte (if I'm thinking clearly). Then at the end of the transmission, there should be an 0x9f header byte that signals "you have received all IR data for this button press". The 0x9f is followed by 0x01 0x01 0x9f 0x15 0x00 0x00 0x80 (not sure exactly what their relevance is, but they're always there). -- Jarod Wilson ja...@wi... |