From: Daniel R. <di...@gm...> - 2010-12-09 18:00:11
|
Howdy all, I'm very new to LIRC, so I'd appreciate some troubleshooting advice. I'm having trouble receiving signals from my Streamzap PC remote. I'm using Ubuntu 10.10 Maverick Meerkat. Here's my steps so far: 1) sudo apt-get install lirc (installs 0.8.7~pre3-0ubuntu1) 2) sudo dpkg-reconfigure lirc (select "Streamzap PC Remote" for remote option and "None" for transmitter option) 3) sudo /etc/init.d/lirc restart (response is "Starting remote control daemon(s) : LIRC [ OK ]") 4) Plug in USB receiver for Streamzap remote 5) The light on the top receiver flashes when I press buttons on the remote 6) irw (no response when pressing buttons on remote) I'm obviously missing a step somewhere. Any advice? Avast! Daniel Roesler di...@gm... |
From: Nick M. <kno...@gm...> - 2010-12-09 20:19:50
|
On 9 December 2010 17:59, Daniel Roesler <di...@gm...> wrote: > Howdy all, > > I'm very new to LIRC, so I'd appreciate some troubleshooting advice. > I'm having trouble receiving signals from my Streamzap PC remote. I'm > using Ubuntu 10.10 Maverick Meerkat. > > Here's my steps so far: > 1) sudo apt-get install lirc (installs 0.8.7~pre3-0ubuntu1) > 2) sudo dpkg-reconfigure lirc (select "Streamzap PC Remote" for remote > option and "None" for transmitter option) > 3) sudo /etc/init.d/lirc restart (response is "Starting remote control > daemon(s) : LIRC [ OK ]") > 4) Plug in USB receiver for Streamzap remote > 5) The light on the top receiver flashes when I press buttons on the remote > 6) irw (no response when pressing buttons on remote) > > I'm obviously missing a step somewhere. Any advice? Try reversing the order of steps 3 and 4. You want to start the LIRC daemon _after_ your receiver has been made available to the system. Cheers, Nick -- Nick Morrott MythTV Official wiki: http://mythtv.org/wiki/ MythTV users list archive: http://www.gossamer-threads.com/lists/mythtv/users "An investment in knowledge always pays the best interest." - Benjamin Franklin |
From: Jarod W. <ja...@wi...> - 2010-12-09 20:33:25
|
On Dec 9, 2010, at 3:19 PM, Nick Morrott wrote: > On 9 December 2010 17:59, Daniel Roesler <di...@gm...> wrote: >> Howdy all, >> >> I'm very new to LIRC, so I'd appreciate some troubleshooting advice. >> I'm having trouble receiving signals from my Streamzap PC remote. I'm >> using Ubuntu 10.10 Maverick Meerkat. >> >> Here's my steps so far: >> 1) sudo apt-get install lirc (installs 0.8.7~pre3-0ubuntu1) >> 2) sudo dpkg-reconfigure lirc (select "Streamzap PC Remote" for remote >> option and "None" for transmitter option) >> 3) sudo /etc/init.d/lirc restart (response is "Starting remote control >> daemon(s) : LIRC [ OK ]") >> 4) Plug in USB receiver for Streamzap remote >> 5) The light on the top receiver flashes when I press buttons on the remote >> 6) irw (no response when pressing buttons on remote) >> >> I'm obviously missing a step somewhere. Any advice? > > Try reversing the order of steps 3 and 4. You want to start the LIRC > daemon _after_ your receiver has been made available to the system. Generally, yes, but it actually *should* work either way. The daemon should simply wait for the device to show up and connect when its finally there. Works over here, anyway. Including with streamzap hardware, no less. Not sure why Daniel's hardware apparently isn't working though. My suggestion would be to turn on ir-core debugging (echo 1 into /sys/modules/ir_cor/parameters/debug and see what pops up in dmesg after that). -- Jarod Wilson ja...@wi... |
From: Daniel R. <di...@gm...> - 2010-12-10 00:26:40
|
Ok, I've done some messing around, it's some strange stuff is going on. I've attached a picture of the remote for reference. First, I turned on debugging for /sys/modules/ir_cor/parameters/debug. Then I isolated the dmesg output in /var/log/syslog when I pressed a button on the remote. I've attached two outputs from two buttons (the OK button and the red button). I'm not sure how to interpret this output. Second, I tried irw again, and the bottom four buttons (red, green, yellow, blue) on the remote actually produce an output for irw! Here's the output for red, green, yellow, and blue: 00000000000028c1 00 1 Streamzap_PC_Remote 00000000000028c2 00 2 Streamzap_PC_Remote 00000000000028c4 00 4 Streamzap_PC_Remote 00000000000028c7 00 7 Streamzap_PC_Remote None of the other buttons display an output from irw. Why is that? I'm receiving a signal in the dmesg, but I guess it's not being picked up as a valid signal? Avast! Daniel Roesler di...@gm... On Thu, Dec 9, 2010 at 2:33 PM, Jarod Wilson <ja...@wi...> wrote: > On Dec 9, 2010, at 3:19 PM, Nick Morrott wrote: > >> On 9 December 2010 17:59, Daniel Roesler <di...@gm...> wrote: >>> Howdy all, >>> >>> I'm very new to LIRC, so I'd appreciate some troubleshooting advice. >>> I'm having trouble receiving signals from my Streamzap PC remote. I'm >>> using Ubuntu 10.10 Maverick Meerkat. >>> >>> Here's my steps so far: >>> 1) sudo apt-get install lirc (installs 0.8.7~pre3-0ubuntu1) >>> 2) sudo dpkg-reconfigure lirc (select "Streamzap PC Remote" for remote >>> option and "None" for transmitter option) >>> 3) sudo /etc/init.d/lirc restart (response is "Starting remote control >>> daemon(s) : LIRC [ OK ]") >>> 4) Plug in USB receiver for Streamzap remote >>> 5) The light on the top receiver flashes when I press buttons on the remote >>> 6) irw (no response when pressing buttons on remote) >>> >>> I'm obviously missing a step somewhere. Any advice? >> >> Try reversing the order of steps 3 and 4. You want to start the LIRC >> daemon _after_ your receiver has been made available to the system. > > Generally, yes, but it actually *should* work either way. The > daemon should simply wait for the device to show up and connect > when its finally there. Works over here, anyway. Including with > streamzap hardware, no less. Not sure why Daniel's hardware > apparently isn't working though. My suggestion would be to turn > on ir-core debugging (echo 1 into > /sys/modules/ir_cor/parameters/debug and see what pops up in > dmesg after that). > > -- > Jarod Wilson > ja...@wi... > > > > > ------------------------------------------------------------------------------ > |
From: Daniel R. <di...@gm...> - 2010-12-14 16:41:04
|
Ok, since the default configuration for the streamzap is not working. I am currently trying irrecord to create a new custom streamzap config, but I'm running into an error when I try to start irrecord. Here's the error: ~$irrecord streamzap2 irrecord - application for recording IR-codes for usage with lirc Copyright (C) 1998,1999 Christoph Bartelmus(li...@ba...) irrecord: could not get file information for /dev/lirc irrecord: default_init(): No such file or directory irrecord: could not init hardware (lircd running ? --> close it, check permissions) I looked in /dev for some lirc devices and I have two listings: ~$ ls /dev/lirc* -l crw------- 1 root root 249, 0 2010-12-14 10:07 /dev/lirc0 lrwxrwxrwx 1 root root 19 2010-12-14 10:07 /dev/lircd -> /var/run/lirc/lircd So I tried each in irrecord. /dev/lirc0 an error: ~$ irrecord -d /dev/lirc0 streamzap2 irrecord - application for recording IR-codes for usage with lirc Copyright (C) 1998,1999 Christoph Bartelmus(li...@ba...) irrecord: could not open /dev/lirc0 irrecord: default_init(): Permission denied irrecord: could not init hardware (lircd running ? --> close it, check permissions) /dev/lircd actually started but will not respond for any buttons except the four bottom colored ones. When I press those, irrecord exits with an error: irrecord: error reading from /dev/lircd irrecord: No such file or directory irrecord: no data for 10 secs, aborting irrecord: gap not found, can't continue So, I'm stuck on how to get irrecord to capture the button presses for this streamzap remote. My question: If I'm seeing output with /sys/modules/ir_cor/parameters/debug and the receiver light is flashing when I press buttons on the remote, why am I not seeing output with irw or irrecord? The only exception is the four color buttons at the bottom, which appear to be functioning. Avast! Daniel Roesler di...@gm... On Thu, Dec 9, 2010 at 6:25 PM, Daniel Roesler <di...@gm...> wrote: > Ok, I've done some messing around, it's some strange stuff is going > on. I've attached a picture of the remote for reference. > > First, I turned on debugging for /sys/modules/ir_cor/parameters/debug. > Then I isolated the dmesg output in /var/log/syslog when I pressed a > button on the remote. I've attached two outputs from two buttons (the > OK button and the red button). I'm not sure how to interpret this > output. > > Second, I tried irw again, and the bottom four buttons (red, green, > yellow, blue) on the remote actually produce an output for irw! Here's > the output for red, green, yellow, and blue: > 00000000000028c1 00 1 Streamzap_PC_Remote > 00000000000028c2 00 2 Streamzap_PC_Remote > 00000000000028c4 00 4 Streamzap_PC_Remote > 00000000000028c7 00 7 Streamzap_PC_Remote > > None of the other buttons display an output from irw. Why is that? I'm > receiving a signal in the dmesg, but I guess it's not being picked up > as a valid signal? > > Avast! > Daniel Roesler > di...@gm... > > On Thu, Dec 9, 2010 at 2:33 PM, Jarod Wilson <ja...@wi...> wrote: >> On Dec 9, 2010, at 3:19 PM, Nick Morrott wrote: >> >>> On 9 December 2010 17:59, Daniel Roesler <di...@gm...> wrote: >>>> Howdy all, >>>> >>>> I'm very new to LIRC, so I'd appreciate some troubleshooting advice. >>>> I'm having trouble receiving signals from my Streamzap PC remote. I'm >>>> using Ubuntu 10.10 Maverick Meerkat. >>>> >>>> Here's my steps so far: >>>> 1) sudo apt-get install lirc (installs 0.8.7~pre3-0ubuntu1) >>>> 2) sudo dpkg-reconfigure lirc (select "Streamzap PC Remote" for remote >>>> option and "None" for transmitter option) >>>> 3) sudo /etc/init.d/lirc restart (response is "Starting remote control >>>> daemon(s) : LIRC [ OK ]") >>>> 4) Plug in USB receiver for Streamzap remote >>>> 5) The light on the top receiver flashes when I press buttons on the remote >>>> 6) irw (no response when pressing buttons on remote) >>>> >>>> I'm obviously missing a step somewhere. Any advice? >>> >>> Try reversing the order of steps 3 and 4. You want to start the LIRC >>> daemon _after_ your receiver has been made available to the system. >> >> Generally, yes, but it actually *should* work either way. The >> daemon should simply wait for the device to show up and connect >> when its finally there. Works over here, anyway. Including with >> streamzap hardware, no less. Not sure why Daniel's hardware >> apparently isn't working though. My suggestion would be to turn >> on ir-core debugging (echo 1 into >> /sys/modules/ir_cor/parameters/debug and see what pops up in >> dmesg after that). >> >> -- >> Jarod Wilson >> ja...@wi... >> >> >> >> >> ------------------------------------------------------------------------------ >> > |
From: Nick M. <kno...@gm...> - 2010-12-14 17:00:01
|
CC'ing the list with reply to Daniel... On 14 December 2010 16:40, Daniel Roesler <di...@gm...> wrote: > Ok, since the default configuration for the streamzap is not working. > I am currently trying irrecord to create a new custom streamzap > config, but I'm running into an error when I try to start irrecord. > Here's the error: > ~$irrecord streamzap2 > irrecord - application for recording IR-codes for usage with lirc > Copyright (C) 1998,1999 Christoph Bartelmus(li...@ba...) > irrecord: could not get file information for /dev/lirc > irrecord: default_init(): No such file or directory > irrecord: could not init hardware (lircd running ? --> close it, check > permissions) > > I looked in /dev for some lirc devices and I have two listings: > ~$ ls /dev/lirc* -l > crw------- 1 root root 249, 0 2010-12-14 10:07 /dev/lirc0 Look at the permissions of the /dev/lirc0 device above ... > lrwxrwxrwx 1 root root 19 2010-12-14 10:07 /dev/lircd -> /var/run/lirc/lircd > > So I tried each in irrecord. /dev/lirc0 an error: > ~$ irrecord -d /dev/lirc0 streamzap2 > irrecord - application for recording IR-codes for usage with lirc > Copyright (C) 1998,1999 Christoph Bartelmus(li...@ba...) > irrecord: could not open /dev/lirc0 > irrecord: default_init(): Permission denied ... you are running irrecord as a non-root user, but /dev/lirc0 can only be accessed by root with its current settings. > irrecord: could not init hardware (lircd running ? --> close it, check > permissions) > > /dev/lircd actually started but will not respond for any buttons > except the four bottom colored ones. When I press those, irrecord > exits with an error: > irrecord: error reading from /dev/lircd > irrecord: No such file or directory > irrecord: no data for 10 secs, aborting > irrecord: gap not found, can't continue Never run irrecord with /dev/lircd (or /var/run/lirc/lircd). These are not LIRC devices but sockets that the LIRC device nodes communicate through. > So, I'm stuck on how to get irrecord to capture the button presses for > this streamzap remote. Try again after adjusting the permissions on the /dev/lirc0 device. You may need to try running irrecord in raw mode if it doesn't detect the protocol being used, or if you don't provide a protocol header for irrecord to use in /etc/lircd.conf (this is discussed in the LIRC docs). > My question: If I'm seeing output with > /sys/modules/ir_cor/parameters/debug and the receiver light is > flashing when I press buttons on the remote, why am I not seeing > output with irw or irrecord? The only exception is the four color > buttons at the bottom, which appear to be functioning. I'll defer to Jarod on this as I've no experience with this hardware. It's entirely possible that the physical IR receiving device is flashing simply because it's detecting IR signals in its hardware. I don't think you can rely in the LED flashes to determine whether the whole IR chain from hardware to lircd is working correctly. Cheers, Nick |
From: Daniel R. <di...@gm...> - 2010-12-14 17:45:15
|
Ok, I changed the lirc0 permissions (sudo chmod 666 /dev/lirc0) and tried irrecord again. When the irrecord started, it asked to press random buttons to find the protocol. Here's the result output from that step: RC-5 remote control found. No header found. No lead pulse found. No repeat code found. Signals are biphase encoded. Signal length is 14 Then, it asked to start naming buttons. After I input the name of the button (e.g. KEY_POWER), I pressed and held the button. However, this resulted in an error every time. I tried several buttons, but all gave the same response: irrecord: no data for 10 secs, aborting The last button did not seem to generate any signal. Here's what's in the config file that was generated: -------------- name streamzap2 bits 14 flags RC5 eps 30 aeps 100 one 864 864 zero 864 864 gap 25472 toggle_bit_mask 0x0 -------------- This differs from the default streamzap remote file (lircd.conf.streamzap): -------------- name Streamzap_PC_Remote bits 6 flags RC5|CONST_LENGTH eps 30 aeps 100 one 889 889 zero 889 889 plead 889 pre_data_bits 8 pre_data 0xA3 gap 108344 toggle_bit 2 -------------- Has anyone experienced the irrecord failing during the button definition step? Is this a sign that there is a problem in the remote, or is it a sign that there is a problem in the receiver? Avast! Daniel Roesler di...@gm... On Tue, Dec 14, 2010 at 10:58 AM, Nick Morrott <kno...@gm...> wrote: > On 14 December 2010 16:40, Daniel Roesler <di...@gm...> wrote: >> Ok, since the default configuration for the streamzap is not working. >> I am currently trying irrecord to create a new custom streamzap >> config, but I'm running into an error when I try to start irrecord. >> Here's the error: >> ~$irrecord streamzap2 >> irrecord - application for recording IR-codes for usage with lirc >> Copyright (C) 1998,1999 Christoph Bartelmus(li...@ba...) >> irrecord: could not get file information for /dev/lirc >> irrecord: default_init(): No such file or directory >> irrecord: could not init hardware (lircd running ? --> close it, check >> permissions) >> >> I looked in /dev for some lirc devices and I have two listings: >> ~$ ls /dev/lirc* -l >> crw------- 1 root root 249, 0 2010-12-14 10:07 /dev/lirc0 > > Look at the permissions of the /dev/lirc0 device above ... > >> lrwxrwxrwx 1 root root 19 2010-12-14 10:07 /dev/lircd -> /var/run/lirc/lircd >> >> So I tried each in irrecord. /dev/lirc0 an error: >> ~$ irrecord -d /dev/lirc0 streamzap2 >> irrecord - application for recording IR-codes for usage with lirc >> Copyright (C) 1998,1999 Christoph Bartelmus(li...@ba...) >> irrecord: could not open /dev/lirc0 >> irrecord: default_init(): Permission denied > > ... you are running irrecord as a non-root user, but /dev/lirc0 can > only be accessed by root with its current settings. > >> irrecord: could not init hardware (lircd running ? --> close it, check >> permissions) >> >> /dev/lircd actually started but will not respond for any buttons >> except the four bottom colored ones. When I press those, irrecord >> exits with an error: >> irrecord: error reading from /dev/lircd >> irrecord: No such file or directory >> irrecord: no data for 10 secs, aborting >> irrecord: gap not found, can't continue > > Never run irrecord with /dev/lircd (or /var/run/lirc/lircd). These are > not LIRC devices but sockets that the LIRC device nodes communicate > through. > >> So, I'm stuck on how to get irrecord to capture the button presses for >> this streamzap remote. > > Try again after adjusting the permissions on the /dev/lirc0 device. > > You may need to try running irrecord in raw mode if it doesn't detect > the protocol being used, or if you don't provide a protocol header for > irrecord to use in /etc/lircd.conf (this is discussed in the LIRC > docs). > >> My question: If I'm seeing output with >> /sys/modules/ir_cor/parameters/debug and the receiver light is >> flashing when I press buttons on the remote, why am I not seeing >> output with irw or irrecord? The only exception is the four color >> buttons at the bottom, which appear to be functioning. > > I'll defer to Jarod on this as I've no experience with this hardware. > > It's entirely possible that the physical IR receiving device is > flashing simply because it's detecting IR signals in its hardware. I > don't think you can rely in the LED flashes to determine whether the > whole IR chain from hardware to lircd is working correctly. > > Cheers, > Nick > |
From: Daniel R. <di...@gm...> - 2010-12-14 21:43:38
|
After some more troubleshooting, I think it might be the receiver. I have a universal remote control (URC-R7) that has the codes for Windows MCE (AUX code 261). I set the universal remote to that and reconfigured lirc to use "Windows Media Center Transceivers/Remotes (all)". I'm assuming I can still use the streamzap receiver with the MCE remote, right? I am unable to get and output from irw when I press buttons. I have also tried using irrecord to see if the protocol is RC-6. Sometimes it returns RC-6, sometimes RC-5, sometimes it just has a length of 66 or some other number. It varies. I think the receiver is sending inconsistent readings to the computer. Am I correct in assuming that the receiver is broken? Avast! Daniel Roesler di...@gm... On Tue, Dec 14, 2010 at 11:44 AM, Daniel Roesler <di...@gm...> wrote: > Ok, I changed the lirc0 permissions (sudo chmod 666 /dev/lirc0) and > tried irrecord again. > > When the irrecord started, it asked to press random buttons to find > the protocol. Here's the result output from that step: > RC-5 remote control found. > No header found. > No lead pulse found. > No repeat code found. > Signals are biphase encoded. > Signal length is 14 > > Then, it asked to start naming buttons. After I input the name of the > button (e.g. KEY_POWER), I pressed and held the button. However, this > resulted in an error every time. I tried several buttons, but all gave > the same response: > irrecord: no data for 10 secs, aborting > The last button did not seem to generate any signal. > > Here's what's in the config file that was generated: > -------------- > name streamzap2 > bits 14 > flags RC5 > eps 30 > aeps 100 > one 864 864 > zero 864 864 > gap 25472 > toggle_bit_mask 0x0 > -------------- > > This differs from the default streamzap remote file (lircd.conf.streamzap): > -------------- > name Streamzap_PC_Remote > bits 6 > flags RC5|CONST_LENGTH > eps 30 > aeps 100 > one 889 889 > zero 889 889 > plead 889 > pre_data_bits 8 > pre_data 0xA3 > gap 108344 > toggle_bit 2 > -------------- > > Has anyone experienced the irrecord failing during the button > definition step? Is this a sign that there is a problem in the remote, > or is it a sign that there is a problem in the receiver? > > Avast! > Daniel Roesler > di...@gm... > > On Tue, Dec 14, 2010 at 10:58 AM, Nick Morrott > <kno...@gm...> wrote: >> On 14 December 2010 16:40, Daniel Roesler <di...@gm...> wrote: >>> Ok, since the default configuration for the streamzap is not working. >>> I am currently trying irrecord to create a new custom streamzap >>> config, but I'm running into an error when I try to start irrecord. >>> Here's the error: >>> ~$irrecord streamzap2 >>> irrecord - application for recording IR-codes for usage with lirc >>> Copyright (C) 1998,1999 Christoph Bartelmus(li...@ba...) >>> irrecord: could not get file information for /dev/lirc >>> irrecord: default_init(): No such file or directory >>> irrecord: could not init hardware (lircd running ? --> close it, check >>> permissions) >>> >>> I looked in /dev for some lirc devices and I have two listings: >>> ~$ ls /dev/lirc* -l >>> crw------- 1 root root 249, 0 2010-12-14 10:07 /dev/lirc0 >> >> Look at the permissions of the /dev/lirc0 device above ... >> >>> lrwxrwxrwx 1 root root 19 2010-12-14 10:07 /dev/lircd -> /var/run/lirc/lircd >>> >>> So I tried each in irrecord. /dev/lirc0 an error: >>> ~$ irrecord -d /dev/lirc0 streamzap2 >>> irrecord - application for recording IR-codes for usage with lirc >>> Copyright (C) 1998,1999 Christoph Bartelmus(li...@ba...) >>> irrecord: could not open /dev/lirc0 >>> irrecord: default_init(): Permission denied >> >> ... you are running irrecord as a non-root user, but /dev/lirc0 can >> only be accessed by root with its current settings. >> >>> irrecord: could not init hardware (lircd running ? --> close it, check >>> permissions) >>> >>> /dev/lircd actually started but will not respond for any buttons >>> except the four bottom colored ones. When I press those, irrecord >>> exits with an error: >>> irrecord: error reading from /dev/lircd >>> irrecord: No such file or directory >>> irrecord: no data for 10 secs, aborting >>> irrecord: gap not found, can't continue >> >> Never run irrecord with /dev/lircd (or /var/run/lirc/lircd). These are >> not LIRC devices but sockets that the LIRC device nodes communicate >> through. >> >>> So, I'm stuck on how to get irrecord to capture the button presses for >>> this streamzap remote. >> >> Try again after adjusting the permissions on the /dev/lirc0 device. >> >> You may need to try running irrecord in raw mode if it doesn't detect >> the protocol being used, or if you don't provide a protocol header for >> irrecord to use in /etc/lircd.conf (this is discussed in the LIRC >> docs). >> >>> My question: If I'm seeing output with >>> /sys/modules/ir_cor/parameters/debug and the receiver light is >>> flashing when I press buttons on the remote, why am I not seeing >>> output with irw or irrecord? The only exception is the four color >>> buttons at the bottom, which appear to be functioning. >> >> I'll defer to Jarod on this as I've no experience with this hardware. >> >> It's entirely possible that the physical IR receiving device is >> flashing simply because it's detecting IR signals in its hardware. I >> don't think you can rely in the LED flashes to determine whether the >> whole IR chain from hardware to lircd is working correctly. >> >> Cheers, >> Nick >> > |
From: Jarod W. <ja...@wi...> - 2010-12-20 20:42:23
|
On Dec 14, 2010, at 4:43 PM, Daniel Roesler wrote: > After some more troubleshooting, I think it might be the receiver. I > have a universal remote control (URC-R7) that has the codes for > Windows MCE (AUX code 261). I set the universal remote to that and > reconfigured lirc to use "Windows Media Center Transceivers/Remotes > (all)". I'm assuming I can still use the streamzap receiver with the > MCE remote, right? > > I am unable to get and output from irw when I press buttons. I have > also tried using irrecord to see if the protocol is RC-6. Sometimes it > returns RC-6, sometimes RC-5, sometimes it just has a length of 66 or > some other number. It varies. I think the receiver is sending > inconsistent readings to the computer. Am I correct in assuming that > the receiver is broken? My own streamzap receiver does not work at all well with lirc decode and mce (RC6) remote signals. Oddly though, it works fine with the in-kernel RC6 decoder. Same receiver works fine with the stock remote though. So its a known issue, I suppose, but not one I have time to look into right now. > On Tue, Dec 14, 2010 at 11:44 AM, Daniel Roesler <di...@gm...> wrote: >> Ok, I changed the lirc0 permissions (sudo chmod 666 /dev/lirc0) and >> tried irrecord again. >> >> When the irrecord started, it asked to press random buttons to find >> the protocol. Here's the result output from that step: >> RC-5 remote control found. >> No header found. >> No lead pulse found. >> No repeat code found. >> Signals are biphase encoded. >> Signal length is 14 >> >> Then, it asked to start naming buttons. After I input the name of the >> button (e.g. KEY_POWER), I pressed and held the button. However, this >> resulted in an error every time. I tried several buttons, but all gave >> the same response: >> irrecord: no data for 10 secs, aborting >> The last button did not seem to generate any signal. >> >> Here's what's in the config file that was generated: >> -------------- >> name streamzap2 >> bits 14 >> flags RC5 >> eps 30 >> aeps 100 >> one 864 864 >> zero 864 864 >> gap 25472 >> toggle_bit_mask 0x0 >> -------------- >> >> This differs from the default streamzap remote file (lircd.conf.streamzap): >> -------------- >> name Streamzap_PC_Remote >> bits 6 >> flags RC5|CONST_LENGTH >> eps 30 >> aeps 100 >> one 889 889 >> zero 889 889 >> plead 889 >> pre_data_bits 8 >> pre_data 0xA3 >> gap 108344 >> toggle_bit 2 >> -------------- >> >> Has anyone experienced the irrecord failing during the button >> definition step? Is this a sign that there is a problem in the remote, >> or is it a sign that there is a problem in the receiver? >> >> Avast! >> Daniel Roesler >> di...@gm... >> >> On Tue, Dec 14, 2010 at 10:58 AM, Nick Morrott >> <kno...@gm...> wrote: >>> On 14 December 2010 16:40, Daniel Roesler <di...@gm...> wrote: >>>> Ok, since the default configuration for the streamzap is not working. >>>> I am currently trying irrecord to create a new custom streamzap >>>> config, but I'm running into an error when I try to start irrecord. >>>> Here's the error: >>>> ~$irrecord streamzap2 >>>> irrecord - application for recording IR-codes for usage with lirc >>>> Copyright (C) 1998,1999 Christoph Bartelmus(li...@ba...) >>>> irrecord: could not get file information for /dev/lirc >>>> irrecord: default_init(): No such file or directory >>>> irrecord: could not init hardware (lircd running ? --> close it, check >>>> permissions) >>>> >>>> I looked in /dev for some lirc devices and I have two listings: >>>> ~$ ls /dev/lirc* -l >>>> crw------- 1 root root 249, 0 2010-12-14 10:07 /dev/lirc0 >>> >>> Look at the permissions of the /dev/lirc0 device above ... >>> >>>> lrwxrwxrwx 1 root root 19 2010-12-14 10:07 /dev/lircd -> /var/run/lirc/lircd >>>> >>>> So I tried each in irrecord. /dev/lirc0 an error: >>>> ~$ irrecord -d /dev/lirc0 streamzap2 >>>> irrecord - application for recording IR-codes for usage with lirc >>>> Copyright (C) 1998,1999 Christoph Bartelmus(li...@ba...) >>>> irrecord: could not open /dev/lirc0 >>>> irrecord: default_init(): Permission denied >>> >>> ... you are running irrecord as a non-root user, but /dev/lirc0 can >>> only be accessed by root with its current settings. >>> >>>> irrecord: could not init hardware (lircd running ? --> close it, check >>>> permissions) >>>> >>>> /dev/lircd actually started but will not respond for any buttons >>>> except the four bottom colored ones. When I press those, irrecord >>>> exits with an error: >>>> irrecord: error reading from /dev/lircd >>>> irrecord: No such file or directory >>>> irrecord: no data for 10 secs, aborting >>>> irrecord: gap not found, can't continue >>> >>> Never run irrecord with /dev/lircd (or /var/run/lirc/lircd). These are >>> not LIRC devices but sockets that the LIRC device nodes communicate >>> through. >>> >>>> So, I'm stuck on how to get irrecord to capture the button presses for >>>> this streamzap remote. >>> >>> Try again after adjusting the permissions on the /dev/lirc0 device. >>> >>> You may need to try running irrecord in raw mode if it doesn't detect >>> the protocol being used, or if you don't provide a protocol header for >>> irrecord to use in /etc/lircd.conf (this is discussed in the LIRC >>> docs). >>> >>>> My question: If I'm seeing output with >>>> /sys/modules/ir_cor/parameters/debug and the receiver light is >>>> flashing when I press buttons on the remote, why am I not seeing >>>> output with irw or irrecord? The only exception is the four color >>>> buttons at the bottom, which appear to be functioning. >>> >>> I'll defer to Jarod on this as I've no experience with this hardware. >>> >>> It's entirely possible that the physical IR receiving device is >>> flashing simply because it's detecting IR signals in its hardware. I >>> don't think you can rely in the LED flashes to determine whether the >>> whole IR chain from hardware to lircd is working correctly. >>> >>> Cheers, >>> Nick >>> >> > > ------------------------------------------------------------------------------ > Lotusphere 2011 > Register now for Lotusphere 2011 and learn how > to connect the dots, take your collaborative environment > to the next level, and enter the era of Social Business. > http://p.sf.net/sfu/lotusphere-d2d -- Jarod Wilson ja...@wi... |
From: Daniel R. <di...@gm...> - 2010-12-28 16:15:02
|
Just to provide some conclusion to this thread. I contacted Streamzap about the problem, and they sent me a new streamzap remote and receiver. I just received the new remote and it appears to be functioning normally. I get the correct responses in irw when using the default streamzap configuration in lirc. So it appears this was a hardware problem. One note for Ubuntu 10.10, though, is that I only have to have lirc installed from the repositories. If I have lirc-modules-source installed, the streamzap remote does not work and no /dev/lirc0 is created when I plug in the usb IR receiver. Avast! Daniel Roesler di...@gm... On Mon, Dec 20, 2010 at 2:42 PM, Jarod Wilson <ja...@wi...> wrote: > On Dec 14, 2010, at 4:43 PM, Daniel Roesler wrote: > >> After some more troubleshooting, I think it might be the receiver. I >> have a universal remote control (URC-R7) that has the codes for >> Windows MCE (AUX code 261). I set the universal remote to that and >> reconfigured lirc to use "Windows Media Center Transceivers/Remotes >> (all)". I'm assuming I can still use the streamzap receiver with the >> MCE remote, right? >> >> I am unable to get and output from irw when I press buttons. I have >> also tried using irrecord to see if the protocol is RC-6. Sometimes it >> returns RC-6, sometimes RC-5, sometimes it just has a length of 66 or >> some other number. It varies. I think the receiver is sending >> inconsistent readings to the computer. Am I correct in assuming that >> the receiver is broken? > > My own streamzap receiver does not work at all well with lirc decode > and mce (RC6) remote signals. Oddly though, it works fine with the > in-kernel RC6 decoder. Same receiver works fine with the stock remote > though. So its a known issue, I suppose, but not one I have time to > look into right now. > > >> On Tue, Dec 14, 2010 at 11:44 AM, Daniel Roesler <di...@gm...> wrote: >>> Ok, I changed the lirc0 permissions (sudo chmod 666 /dev/lirc0) and >>> tried irrecord again. >>> >>> When the irrecord started, it asked to press random buttons to find >>> the protocol. Here's the result output from that step: >>> RC-5 remote control found. >>> No header found. >>> No lead pulse found. >>> No repeat code found. >>> Signals are biphase encoded. >>> Signal length is 14 >>> >>> Then, it asked to start naming buttons. After I input the name of the >>> button (e.g. KEY_POWER), I pressed and held the button. However, this >>> resulted in an error every time. I tried several buttons, but all gave >>> the same response: >>> irrecord: no data for 10 secs, aborting >>> The last button did not seem to generate any signal. >>> >>> Here's what's in the config file that was generated: >>> -------------- >>> name streamzap2 >>> bits 14 >>> flags RC5 >>> eps 30 >>> aeps 100 >>> one 864 864 >>> zero 864 864 >>> gap 25472 >>> toggle_bit_mask 0x0 >>> -------------- >>> >>> This differs from the default streamzap remote file (lircd.conf.streamzap): >>> -------------- >>> name Streamzap_PC_Remote >>> bits 6 >>> flags RC5|CONST_LENGTH >>> eps 30 >>> aeps 100 >>> one 889 889 >>> zero 889 889 >>> plead 889 >>> pre_data_bits 8 >>> pre_data 0xA3 >>> gap 108344 >>> toggle_bit 2 >>> -------------- >>> >>> Has anyone experienced the irrecord failing during the button >>> definition step? Is this a sign that there is a problem in the remote, >>> or is it a sign that there is a problem in the receiver? >>> >>> Avast! >>> Daniel Roesler >>> di...@gm... >>> >>> On Tue, Dec 14, 2010 at 10:58 AM, Nick Morrott >>> <kno...@gm...> wrote: >>>> On 14 December 2010 16:40, Daniel Roesler <di...@gm...> wrote: >>>>> Ok, since the default configuration for the streamzap is not working. >>>>> I am currently trying irrecord to create a new custom streamzap >>>>> config, but I'm running into an error when I try to start irrecord. >>>>> Here's the error: >>>>> ~$irrecord streamzap2 >>>>> irrecord - application for recording IR-codes for usage with lirc >>>>> Copyright (C) 1998,1999 Christoph Bartelmus(li...@ba...) >>>>> irrecord: could not get file information for /dev/lirc >>>>> irrecord: default_init(): No such file or directory >>>>> irrecord: could not init hardware (lircd running ? --> close it, check >>>>> permissions) >>>>> >>>>> I looked in /dev for some lirc devices and I have two listings: >>>>> ~$ ls /dev/lirc* -l >>>>> crw------- 1 root root 249, 0 2010-12-14 10:07 /dev/lirc0 >>>> >>>> Look at the permissions of the /dev/lirc0 device above ... >>>> >>>>> lrwxrwxrwx 1 root root 19 2010-12-14 10:07 /dev/lircd -> /var/run/lirc/lircd >>>>> >>>>> So I tried each in irrecord. /dev/lirc0 an error: >>>>> ~$ irrecord -d /dev/lirc0 streamzap2 >>>>> irrecord - application for recording IR-codes for usage with lirc >>>>> Copyright (C) 1998,1999 Christoph Bartelmus(li...@ba...) >>>>> irrecord: could not open /dev/lirc0 >>>>> irrecord: default_init(): Permission denied >>>> >>>> ... you are running irrecord as a non-root user, but /dev/lirc0 can >>>> only be accessed by root with its current settings. >>>> >>>>> irrecord: could not init hardware (lircd running ? --> close it, check >>>>> permissions) >>>>> >>>>> /dev/lircd actually started but will not respond for any buttons >>>>> except the four bottom colored ones. When I press those, irrecord >>>>> exits with an error: >>>>> irrecord: error reading from /dev/lircd >>>>> irrecord: No such file or directory >>>>> irrecord: no data for 10 secs, aborting >>>>> irrecord: gap not found, can't continue >>>> >>>> Never run irrecord with /dev/lircd (or /var/run/lirc/lircd). These are >>>> not LIRC devices but sockets that the LIRC device nodes communicate >>>> through. >>>> >>>>> So, I'm stuck on how to get irrecord to capture the button presses for >>>>> this streamzap remote. >>>> >>>> Try again after adjusting the permissions on the /dev/lirc0 device. >>>> >>>> You may need to try running irrecord in raw mode if it doesn't detect >>>> the protocol being used, or if you don't provide a protocol header for >>>> irrecord to use in /etc/lircd.conf (this is discussed in the LIRC >>>> docs). >>>> >>>>> My question: If I'm seeing output with >>>>> /sys/modules/ir_cor/parameters/debug and the receiver light is >>>>> flashing when I press buttons on the remote, why am I not seeing >>>>> output with irw or irrecord? The only exception is the four color >>>>> buttons at the bottom, which appear to be functioning. >>>> >>>> I'll defer to Jarod on this as I've no experience with this hardware. >>>> >>>> It's entirely possible that the physical IR receiving device is >>>> flashing simply because it's detecting IR signals in its hardware. I >>>> don't think you can rely in the LED flashes to determine whether the >>>> whole IR chain from hardware to lircd is working correctly. >>>> >>>> Cheers, >>>> Nick >>>> >>> >> >> ------------------------------------------------------------------------------ >> Lotusphere 2011 >> Register now for Lotusphere 2011 and learn how >> to connect the dots, take your collaborative environment >> to the next level, and enter the era of Social Business. >> http://p.sf.net/sfu/lotusphere-d2d > > -- > Jarod Wilson > ja...@wi... > > > > |