Linux iMON Pad - Need Reliable Info

(2012-03-30 15:32)David1977 Wrote:  No Problem....tell me what you need

This is the cat....

cat /proc/bus/input/devices


I hope it may help

The type of the receiver is a "Soundgraph iMon-Pad VFD/IR"

And if you need....

Greetings

Your receiver is the 'old' receiver.

I: Bus=0003 Vendor=15c2 Product=ffdc Version=0000
N: Name="iMON Panel, Knob and Mouse(15c2:ffdc)"

The FFDC portion is how you tell. You no longer need lirc to manage this. Run apt-get install ir-keytable, and then run ir-keytable you should see an output similar to this:


That tells me that I am using the rc-imon-pad key configuration from /lib/udev/rc_keymaps (the file is named imon_pad) inside of there it's pretty similar to an lirc configuration file. e.g.:


Running ir-keytable -t should display something for each button that you hit
Running ir-keytable -r should display the current keymapping for each key.

I'm still working on fixing both of mine (I have both the 'old' and the 'new' receivers and each is being a colossal pain in the ass)

Okay....

I installed ir-keytable .... everything's ok

running ir-keytable gives an output like you said:


That means to me, that I'm using the imon-mce file in /lib/udev/rc-keymaps, right?


ir-keymaps -t doesn't show anything while I hit a button on my remote
ir-keymaps -r displays the mapping like you've said


Did I do something wrong or what is the fault because ir-keymaps -t won't display anything?

(2012-03-30 19:10)David1977 Wrote:  Okay....

I installed ir-keytable .... everything's ok

running ir-keytable gives an output like you said:

Code:

david@david-xbmc:~$ ir-keytable
Found /sys/class/rc/rc0/ (/dev/input/event5) with:
        Driver imon, table rc-imon-mce

That means to me, that I'm using the imon-mce file in /lib/udev/rc-keymaps, right?


ir-keymaps -t doesn't show anything while I hit a button on my remote
ir-keymaps -r displays the mapping like you've said

Did I do something wrong or what is the fault because ir-keymaps -t won't display anything?

yes, you are using the imon-mce config file in /lib/udev/rc-keymaps which from what I can tell is wrong. I have that exact setup, here's what I did to fix it (mostly):

dpkg-reconfigure lirc
Select Linux input layer (/dev/input/eventX)
Select None (unless you have a remote extender for a satellite dish or something)
In the next list, it's going to give you a complete listing of /dev/input/ you're looking for the one that ends in usb-15c2_ffdc-even-if00
There will actually be 3 of them, one ends in mouse, another ends in something else. You want the one that ends in if00

Once that is completed, it will start lirc using the drivers from the kernel rather than lirc drivers.

Now, I created my own configuration file in /etc/rc_keymaps named imon-pad so...
nano /etc/rc_keymaps/imon-pad


Paste all that into it and save it

then run ir-keytable -w /etc/rc_keymaps/imon-pad
that will write the configuration to the keytable, and if you run irw or ir-keytable -t pressing a button on the remote should cause something to appear on screen.

Note ... this is still a work in progress for me ... as not all the remote buttons work as they used to, but I figure helping you get to the point I'm at is better than nothing

You don´t know how correct this is ...better than nothing!!!

I´m gonna check this later or maybe tomorrow morning and tell if I´ve got luck

thx for your help!

I have the same problems, tyring to get MCE remote via Soundgraph imon to work with EDEN. My config is this:


I have the same hardware.conf as dave with the exception that I use lircd.conf.imon-mceusb".
Also before in Dharma to get any keys recognized I had to create a lirc_imon.conf file in /etc/modprobe.d containing just one line:
options lirc_imon ir_protocol=1
So dave, you could try this but I guess then you can't start the lirc daemon cause that's what's happening to me now. First I got unrecognized option then I got broken configuration, check hardware.conf.

Everything worked fine under Dharma where I also had to configure quite a few things, but now it seems hopeless. Mythbuntu forum users are talking about some broken lirc_imon drivers/modules in newer linux kernels, I hope that's not the case with xbmcbunte but my best guess is now that in fact it is the problem we are experiencing right now
See also http://forum.xbmc.org/showthread.php?tid=127098 . There were three steps mentioned to somehow downgrade to the good old working lirc_imon, but I don't know how to exactly do the mentioned steps to test if it works.

BTW I tried the way with inputlirc, too, but that's not really bearable for me. I got all the old problems with buttons responding kind of sluggish or too quick etc. , that's why I bought a MCE remote in the first place and put the imon remote in the dumpster.

Well, if nothing else comes up I guess we have to downgrade and wait till some linux experts figure out a way...if ever. I hope there are enough experienced users with the soundgraph IR product else we will all end up like me with a certain WLAN USB stick that will never EVER work under linux because no one cares. I really like the whole concept of linux and OpenSource in general but sometimes it gets frustrating. Well, shouldn't complain really because it's all for free.

N: Name="iMON Panel, Knob and Mouse(15c2:0038)"

You have the 'new' version of the receiver. You don't need lirc involved at all. And it should function out of the box. With the exception of a few keys not working at all. That's what the 0038 means.

Disable lirc -> service stop lirc
Install ir-keytable -> apt-get install ir-keytable
Run ir-keytable -> ir-keytable -t

Press some buttons on the remote, and make sure it responds.

---

Quote:Well, if nothing else comes up I guess we have to downgrade and wait till some linux experts figure out a way...if ever. I hope there are enough experienced users with the soundgraph IR product else we will all end up like me with a certain WLAN USB stick that will never EVER work under linux because no one cares. I really like the whole concept of linux and OpenSource in general but sometimes it gets frustrating. Well, shouldn't complain really because it's all for free.

If you want to downgrade you need to disable the devinput modules:
- Add this blacklist to /etc/modprobe.d/blacklist-imon.conf:

blacklist ir_core
blacklist ir_lirc_codec
blacklist ir_sony_decoder
blacklist ir_jvc_decoder
blacklist ir_rc6_decoder
blacklist ir_rc5_decoder
blacklist ir_nec_decoder
blacklist rc_imon_pad
blacklist imon

- Add this entry to /etc/modules:
lirc_imon

However, I haven't even been able to get that working.

The issue you're experiencing is directly related to remote input being included in the kernel now through devinput and no longer needing lirc to handle anything in between.

BTW I noticed just right now that even with inputlirc and customized Lircmap I didn't even get keys like home and 'OK', so really not an option.

Ok, now I tried sparkies hints. Did revert any config files I changed so far, did purge inputlirc.

Then:

>service stop lirc
stop: unrecognized service

installed ir-keytable again (after purging first)

sudo ir-keytable -t

..and it worked, at least in testing mode, thank you so much!

Power-on via remote power button worked after shutdown in the console. To do above steps I did leave xbmc. Now, after rebooting all the way up to xbmc however the power-on-remote function of my Antec box however stopped working, again, like xbmc is causing a switch to another IR channel in the firmware or something.. And no remote keys are recognized in xbmc, too. I guess I have to create a Lircmap.xml from scratch now to get the keys recognized? Or did I miss some other things? Back in dharma my mce remote worked with the standard Lircmap.xml that's why I'm wondering.

(2012-03-31 00:01)gokudo Wrote:  Power-on via remote power button worked after shutdown in the console. To do above steps I did leave xbmc. Now, after rebooting all the way up to xbmc however the power-on-remote function of my Antec box however stopped working, again, like xbmc is causing a switch to another IR channel in the firmware or something.. And no remote keys are recognized in xbmc, too. I guess I have to create a Lircmap.xml from scratch now to get the keys recognized? Or did I miss some other things? Back in dharma my mce remote worked with the standard Lircmap.xml that's why I'm wondering.

The power on via remote is handled on the hardware level. There's a header that runs to the motherboard in between the power supply and receiver. That's what handles your power on. It's not dependent on software.

If it's not working after a reboot, run ir-keytable with no flags to see what it's using for a driver. With the 0038 you should get this:

With ffdc:

Let me know what you get.

ir-keytable -t should dump any input the remote sends the receiver. I think the relationship between the devinput drivers, lirc, Lircmap.xml etc is getting all confused. My understanding thus far is that lirc modules are now included directly into the kernel, that driver translates the scancode received from the remote, into an event key. So lets say I hit 'right' on the stick. The kernel receives scancode 0x100007f and maps that to KEY_RIGHT (0xa006a) which is in turn interpreted by the operating system as you hitting the right arrow on any regular input device (keyboard).

(2012-03-29 21:17)sparkie2640 Wrote:  

(2012-03-28 02:11)TwiztedIndian Wrote:  UGH! I'm at my wits end... I've tried everything I can to the point that now I have buttons on my remote that did work that no longer work....

/cry

I just want this stoopid thing to work...

If you run:

cat /proc/bus/input/devices

Look for something on one of the N: lines that includes "iMon Panel" and show me what's on the I: lines above those. There are two different types of iMon receivers. One 'old' and one 'new' and they are both handled differently in XBMCuntu as compared to previous versions.

Sorry it took so long to reply... been a busy week.

I've completely removed LIRC now and I have ir-keytable

ir-keytable spits out

and I get output from buttons on the remote if i run with a -t flag....

There are still lots of buttons that do not function on the Pad remote like the 'menu' button.

---

Also, is it at all possible to use the ol'green button MCE remote with the iMON receiver or would I -have- to use the USB receiver?


The reason I ask is because the Pad remote is super sensitive to the point of being more than a little annoying...