From: Anselmo L. <an...@da...> - 2009-02-24 20:01:32
|
Hi everyone, I landed here as i can't make it working! So, i've a iMON OEM Type B, IR, LCD, Volume KNOB, RM200 remote. 15c2:0038 I've compiled lirc from cvs without problem. When I load the drivers i got lcd0, lcd1, lirc0, lirc1, devices. The lcd works. With irrecord the remote seems to work but.... Half of the keys appear in lirc0 and the other half on lirc1. If you start irrecord only on one of the devices (for example lirc0) and you press any key that user the other device (say lirc1) you will definetly not be able to get any output on irrecord until you don't start it in the second device too. May be you have to flush something to get the next key? So the better solution was to start two irrecord on both the devices at the same time. Now to get all the events i've to start two istance of lircd lircd -H default -d /dev/lirc1 -l lircd.conf lircd -H default -d /devlirc0 -c localhost lircd.conf (i've omitted some option) but irw doesn't show any events. I've made some errors? Anselmo |
From: Jarod W. <ja...@wi...> - 2009-02-24 20:30:10
|
On Tue, 2009-02-24 at 20:44 +0100, Anselmo Luginbühl wrote: > Hi everyone, > > I landed here as i can't make it working! > > So, i've a iMON OEM Type B, IR, LCD, Volume KNOB, RM200 remote. 15c2:0038 > > > > I've compiled lirc from cvs without problem. When I load the drivers i got > lcd0, lcd1, lirc0, lirc1, devices. The lcd works. With irrecord the remote > seems to work but.... > > Half of the keys appear in lirc0 and the other half on lirc1. > > If you start irrecord only on one of the devices (for example lirc0) and you > press any key that user the other device (say lirc1) you will definetly not be > able to get any output on irrecord until you don't start it in the second > device too. May be you have to flush something to get the next key? > > So the better solution was to start two irrecord on both the devices at the > same time. > > Now to get all the events i've to start two istance of lircd > > lircd -H default -d /dev/lirc1 -l lircd.conf lircd -H default -d /devlirc0 -c > localhost lircd.conf > > (i've omitted some option) but irw doesn't show any events. > > I've made some errors? This one is a FAQ. The multiple devices is expected, and there are a few hoops to jump through to properly configure them. Search the list archives, its been covered (even as recently as a few days ago). -- Jarod Wilson ja...@wi... |
From: Anselmo L. <an...@da...> - 2009-02-24 22:58:29
|
On Tue, Feb 24, 2009 at 03:29:49PM -0500, Jarod Wilson wrote: > On Tue, 2009-02-24 at 20:44 +0100, Anselmo Luginbühl wrote: > > Hi everyone, > > > > I landed here as i can't make it working! > > > > So, i've a iMON OEM Type B, IR, LCD, Volume KNOB, RM200 remote. 15c2:0038 > > > > > > > > I've compiled lirc from cvs without problem. When I load the drivers i got > > lcd0, lcd1, lirc0, lirc1, devices. The lcd works. With irrecord the remote > > seems to work but.... > > > > Half of the keys appear in lirc0 and the other half on lirc1. > > > > If you start irrecord only on one of the devices (for example lirc0) and you > > press any key that user the other device (say lirc1) you will definetly not be > > able to get any output on irrecord until you don't start it in the second > > device too. May be you have to flush something to get the next key? > > > > So the better solution was to start two irrecord on both the devices at the > > same time. > > > > Now to get all the events i've to start two istance of lircd > > > > lircd -H default -d /dev/lirc1 -l lircd.conf lircd -H default -d /devlirc0 -c > > localhost lircd.conf > > > > (i've omitted some option) but irw doesn't show any events. > > > > I've made some errors? > > This one is a FAQ. The multiple devices is expected, and there are a few > hoops to jump through to properly configure them. Search the list > archives, its been covered (even as recently as a few days ago). I'm sorry but I've already done a research on the archives and founded nothing usefull in the past two months. The suggested web pages are not more usefull as the presented methods are not working, or at least partially. The problem here is that irrecord seems to work but irw doesn't. And the volume knob doesn't work at all. I know multiple device is expected and i've to use two istance of lircd. Any idea of why irrecord works and lircd doesn't ? > > > -- > Jarod Wilson > ja...@wi... > > |
From: Jarod W. <ja...@wi...> - 2009-02-25 03:56:55
|
On Tue, 2009-02-24 at 22:48 +0100, Anselmo Luginbühl wrote: > On Tue, Feb 24, 2009 at 03:29:49PM -0500, Jarod Wilson wrote: > > On Tue, 2009-02-24 at 20:44 +0100, Anselmo Luginbühl wrote: > > > Hi everyone, > > > > > > I landed here as i can't make it working! > > > > > > So, i've a iMON OEM Type B, IR, LCD, Volume KNOB, RM200 remote. 15c2:0038 > > > > > > > > > > > > I've compiled lirc from cvs without problem. When I load the drivers i got > > > lcd0, lcd1, lirc0, lirc1, devices. The lcd works. With irrecord the remote > > > seems to work but.... > > > > > > Half of the keys appear in lirc0 and the other half on lirc1. > > > > > > If you start irrecord only on one of the devices (for example lirc0) and you > > > press any key that user the other device (say lirc1) you will definetly not be > > > able to get any output on irrecord until you don't start it in the second > > > device too. May be you have to flush something to get the next key? > > > > > > So the better solution was to start two irrecord on both the devices at the > > > same time. > > > > > > Now to get all the events i've to start two istance of lircd > > > > > > lircd -H default -d /dev/lirc1 -l lircd.conf lircd -H default -d /devlirc0 -c > > > localhost lircd.conf > > > > > > (i've omitted some option) but irw doesn't show any events. > > > > > > I've made some errors? > > > > This one is a FAQ. The multiple devices is expected, and there are a few > > hoops to jump through to properly configure them. Search the list > > archives, its been covered (even as recently as a few days ago). > > I'm sorry but I've already done a research on the archives and founded nothing > usefull in the past two months. Apologies, didn't read carefully enough. > The suggested web pages are not more usefull as > the presented methods are not working, or at least partially. The problem here > is that irrecord seems to work but irw doesn't. And the volume knob doesn't > work at all. > > I know multiple device is expected and i've to use two istance of lircd. Your two instances don't look correct though. > Any idea of why irrecord works and lircd doesn't ? The first lircd needs to be started w/a --listen=<port #> option, the second needs to connect to it using a --connect=<port #> option. How to do so *is* covered in a few places that are linked in the list archives. My 0x0045 device (more or less identical to the 0x0038, but Antec-branded) isn't currently fired up, or I'd cut-n-paste the config files here. I believe irrecord may still not work, due to the two devices using a shared buffer, not sure. (Making it a single device is on the TODO list, but not a particularly high priority at the moment). But lircd definitely works. -- Jarod Wilson ja...@wi... |
From: Anselmo L. <an...@da...> - 2009-02-25 09:43:49
|
> > I know multiple device is expected and i've to use two istance of lircd. > > Your two instances don't look correct though. > > > Any idea of why irrecord works and lircd doesn't ? > > The first lircd needs to be started w/a --listen=<port #> option, the > second needs to connect to it using a --connect=<port #> option. How to > do so *is* covered in a few places that are linked in the list archives. > My 0x0045 device (more or less identical to the 0x0038, but > Antec-branded) isn't currently fired up, or I'd cut-n-paste the config > files here. Mine is in an Antec case too, a Fusion Remote Black. I've used the more detailed command but nothing changed: lircd -H default -d /dev/lirc0 -o /dev/lircd0 --listen=8765 /etc/lircd.conf lircd -H default -d /dev/lirc1 -o /dev/lircd --connect=localhost:8765 /etc/lircd.conf irw continue to show nothing, but the log says: Feb 25 11:17:33 pingus lircd-0.8.5-CVS[3601]: accepted new client on /dev/lircd Feb 25 11:17:33 pingus kernel: [ 1901.030951] IR port opened Feb 25 11:17:48 pingus kernel: [ 1920.177653] 2a <6>81 <6>15 <6>b7 <6>00 <6>00 <6>02 <6>01 <6> Feb 25 11:17:48 pingus kernel: [ 1920.370024] 2a <6>81 <6>55 <6>b7 <6>00 <6>00 <6>02 <6>01 <6> Feb 25 11:17:50 pingus kernel: [ 1922.792161] 28 <6>81 <6>95 <6>b7 <6>00 <6>00 <6>02 <6>01 <6> Feb 25 11:17:50 pingus kernel: [ 1922.920321] 28 <6>81 <6>d5 <6>b7 <6>00 <6>00 <6>02 <6>01 <6> Feb 25 11:17:53 pingus kernel: [ 1928.261840] 02 <6>00 <6>00 <6>1f <6>00 <6>00 <6>00 <6>00 <6> Feb 25 11:17:53 pingus kernel: [ 1928.440980] 02 <6>00 <6>00 <6>00 <6>00 <6>00 <6>00 <6>00 <6> Feb 25 11:18:11 pingus kernel: [ 1952.461681] 02 <6>00 <6>00 <6>28 <6>00 <6>00 <6>00 <6>00 <6> Feb 25 11:18:11 pingus kernel: [ 1952.661726] 02 <6>00 <6>00 <6>00 <6>00 <6>00 <6>00 <6>00 <6> The first two keys are the KEY_EXIT and KEY_POWER from lirc1 The last two keys are KEY_ENTER and KEY_1 from lirc0 so both devices seems to work (who write to te log?) and output on lircd, the logs appears only if irw is opened, but irw itself continue to show nothing. > > I believe irrecord may still not work, due to the two devices using a > shared buffer, not sure. (Making it a single device is on the TODO list, > but not a particularly high priority at the moment). But lircd > definitely works. > > > -- > Jarod Wilson > ja...@wi... > |
From: Jarod W. <ja...@wi...> - 2009-02-25 14:26:50
|
On Wednesday 25 February 2009 04:43:36 Anselmo Luginbühl wrote: > > > I know multiple device is expected and i've to use two istance of lircd. > > > > Your two instances don't look correct though. > > > > > Any idea of why irrecord works and lircd doesn't ? > > > > The first lircd needs to be started w/a --listen=<port #> option, the > > second needs to connect to it using a --connect=<port #> option. How to > > do so *is* covered in a few places that are linked in the list archives. > > My 0x0045 device (more or less identical to the 0x0038, but > > Antec-branded) isn't currently fired up, or I'd cut-n-paste the config > > files here. > > Mine is in an Antec case too, a Fusion Remote Black. The 0038 is the OEM iMON that is in multiple vendors cases, the 0045 is a stand-alone add-on product, Antec-branded, but its really neither here nor there, they *should* be basically the same thing as far as lirc cares. > I've used the more detailed command but nothing changed: > > lircd -H default -d /dev/lirc0 -o /dev/lircd0 --listen=8765 /etc/lircd.conf > lircd -H default -d /dev/lirc1 -o /dev/lircd --connect=localhost:8765 /etc/lircd.conf The '-o /dev/lircd0' in the first line doesn't look correct. Both should be outputting to /dev/lircd. > irw continue to show nothing, but the log says: > > Feb 25 11:17:33 pingus lircd-0.8.5-CVS[3601]: accepted new client on /dev/lircd > Feb 25 11:17:33 pingus kernel: [ 1901.030951] IR port opened > Feb 25 11:17:48 pingus kernel: [ 1920.177653] 2a <6>81 <6>15 <6>b7 <6>00 <6>00 <6>02 <6>01 <6> > Feb 25 11:17:48 pingus kernel: [ 1920.370024] 2a <6>81 <6>55 <6>b7 <6>00 <6>00 <6>02 <6>01 <6> > Feb 25 11:17:50 pingus kernel: [ 1922.792161] 28 <6>81 <6>95 <6>b7 <6>00 <6>00 <6>02 <6>01 <6> > Feb 25 11:17:50 pingus kernel: [ 1922.920321] 28 <6>81 <6>d5 <6>b7 <6>00 <6>00 <6>02 <6>01 <6> > Feb 25 11:17:53 pingus kernel: [ 1928.261840] 02 <6>00 <6>00 <6>1f <6>00 <6>00 <6>00 <6>00 <6> > Feb 25 11:17:53 pingus kernel: [ 1928.440980] 02 <6>00 <6>00 <6>00 <6>00 <6>00 <6>00 <6>00 <6> > Feb 25 11:18:11 pingus kernel: [ 1952.461681] 02 <6>00 <6>00 <6>28 <6>00 <6>00 <6>00 <6>00 <6> > Feb 25 11:18:11 pingus kernel: [ 1952.661726] 02 <6>00 <6>00 <6>00 <6>00 <6>00 <6>00 <6>00 <6> > > The first two keys are the KEY_EXIT and KEY_POWER from lirc1 > The last two keys are KEY_ENTER and KEY_1 from lirc0 > > so both devices seems to work (who write to te log?) and output on lircd, the logs appears only if irw > is opened, but irw itself continue to show nothing. I suspect once you've got the two lircd instances starting up correctly, irw will be perfectly happy. I'll spin up my 0045-equipped box tonight and double-check my config there. -- Jarod Wilson ja...@wi... |
From: Drew F. <dre...@gm...> - 2009-02-25 14:50:10
|
On Wed, Feb 25, 2009 at 4:43 AM, Anselmo Luginbühl <an...@da...> wrote: > > Mine is in an Antec case too, a Fusion Remote Black. > > I've used the more detailed command but nothing changed: > > lircd -H default -d /dev/lirc0 -o /dev/lircd0 --listen=8765 /etc/lircd.conf > lircd -H default -d /dev/lirc1 -o /dev/lircd --connect=localhost:8765 /etc/lircd.conf > I have a different Antec IR receiver, but I'm also using the imon driver and just got everything working last week. The thing that leaps out at me here is that it appears you're using the same lircd.conf file for each lircd instance. For my configuration I ended up having to use two separate configuration files. Are the config files you are using ones you created using irrecord, or did you get them from somewhere else on the 'net? You might try to find a known good config for your control and use those instead of one created using irrecord -- in my case one of the config files I created worked fine, except for the need to set the toggle_bit_mask to 0, the other was hopeless, and I ended up using one I found for a similar device that worked. FWIW, I start up lircd using: lircd -L/root/lircd0.log --driver=default -d/dev/lirc/0 -o/dev/lircd0 -P/root/lircd0.pid -l9998 ./lirc0.conf lircd -L/root/lircd1.log --driver=default -d/dev/lirc/1 -o/dev/lircd -P/root/lircd1.pid --connect=localhost:9998 ./lirc1.conf It works fine with irw. >From what I understand different -o devices should be fine, and the connect/listen arguments take care of routing events between the two instances and irw/irexec talks to /dev/lircd -- but I could be wrong about that. Drew |
From: Jarod W. <ja...@wi...> - 2009-02-25 15:18:55
|
On Wednesday 25 February 2009 09:50:05 Drew Farris wrote: > On Wed, Feb 25, 2009 at 4:43 AM, Anselmo Luginbühl > <an...@da...> wrote: > > > > Mine is in an Antec case too, a Fusion Remote Black. > > > > I've used the more detailed command but nothing changed: > > > > lircd -H default -d /dev/lirc0 -o /dev/lircd0 --listen=8765 /etc/lircd.conf > > lircd -H default -d /dev/lirc1 -o /dev/lircd --connect=localhost:8765 /etc/lircd.conf > > > > I have a different Antec IR receiver, but I'm also using the imon > driver and just got everything working last week. The thing that leaps > out at me here is that it appears you're using the same lircd.conf > file for each lircd instance. For my configuration I ended up having > to use two separate configuration files. I use mine just fine with a single configuration file, which is included in remotes/imon/<something antec-veris>. > FWIW, I start up lircd using: > > lircd -L/root/lircd0.log --driver=default -d/dev/lirc/0 -o/dev/lircd0 > -P/root/lircd0.pid -l9998 ./lirc0.conf > lircd -L/root/lircd1.log --driver=default -d/dev/lirc/1 -o/dev/lircd > -P/root/lircd1.pid --connect=localhost:9998 ./lirc1.conf Hm, is /dev/lircd0 a symlink to /dev/lircd? I'm pretty sure I start one of the two lircd instances w/o a -o param at all, and the other points to /dev/lircd, never had any /dev/lircd0 anywhere... -- Jarod Wilson ja...@wi... |
From: Drew F. <dre...@gm...> - 2009-02-25 15:59:19
|
On Wed, Feb 25, 2009 at 10:24 AM, Jarod Wilson <ja...@wi...> wrote: > I use mine just fine with a single configuration file, which is included > in remotes/imon/<something antec-veris>. Ahh, good point. That should be the first place I looked, and it seems that a single config file for my remote was available there. I'll give it a try. FWIW, it looks quite different from the one generated automatically using irrecord -- Anselmo, you probably want to see if a config for your remote is available in there (if you haven't already). >> I start up lircd using: >> >> lircd -L/root/lircd0.log --driver=default -d/dev/lirc/0 -o/dev/lircd0 >> -P/root/lircd0.pid -l9998 ./lirc0.conf >> lircd -L/root/lircd1.log --driver=default -d/dev/lirc/1 -o/dev/lircd >> -P/root/lircd1.pid --connect=localhost:9998 ./lirc1.conf > I'm pretty sure I start one of the two lircd instances w/o a -o param at all, and the other points > to /dev/lircd, never had any /dev/lircd0 anywhere... You're absolutely correct, I removed the -o/dev/lircd0 the first invocation of lircd, and it works perfectly fine without it. Drew |
From: Anselmo L. <an...@da...> - 2009-02-25 23:21:16
|
I finally found the problem with a vimdiff between a conf from lirc and the one generated with irrecord. I changed the original because not all the key where in the namespace accepted by irrecord. It was a stupid error in "post_data_bits" and "post_data". But to thank's all of you for your help, I made some checks as it seems that there are some doubt about the use of lircd. 1 - you can use the same lirc.conf for all your lircd istance even if you use a different remote as you can insert all of them in the same conf file. 2 - You can call the two instance of lirc without specifing the output device (if they are connected togheter), they will use both lircd (or at least the second one) but to avoid logical conflict i think specifing the first to be a different one (for example /dev/lircd1) would be a good idea. And that let you the possibility to use irw only to log what come from that device. 3 - If you have to use two devices, or probably any number of devices, say you have a star of three device lirc0 lirc1 lirc2, so the first two listen (--listen) and only the third one output on lircd (--connect). And you want to use irw to listen only one of the "partial" output, say lircd0, you have anyway to start a lecture on lircd. lircd -Hdefault -d /dev/lirc0 -l 8765 -o /dev/lircd0 -P... lircd -Hdefault -d /dev/lirc1 -l 8766 -o /dev/lircd1 -P... lircd -Hdefault -d /dev/lirc2 -c localhost:8765 -c locahost:8766 -P (this one will output on lircd) irw /dev/lircd0 AND irw /dev/lircd because if you press a key that doesn't output on lircd0, say it exit on lircd1, and you listen only lircd0, you will not get any subsequent key, even if it shuold output on the device you're listening, until you flush the queue. For example listening on the "total" device too (/dev/lircd or any other you've specified on the last lircd invocation). Hope that could be usefull fore someone. Now I have to made the knob working as i got absolutely no output from it. Is your volume knob working? Thank's for your help Anselmo |
From: Anselmo L. <an...@da...> - 2009-02-27 09:51:03
|
Hi, did your volume knob (antec fusion black, device 0038) simply works? My remote works perfectly, lcd works (i've still problem with lcdproc), but i see no events from the Volume knob. There is something specific to get it working? Anselmo |