From: Bengt N. <ben...@sp...> - 2011-02-06 11:21:36
|
Reading an older thread (Re: iMON Remote repeating issue), I realize that the problem is in the imon driver. A patch seems to be available, but it is beyond my current competence to apply it. Can someone guide me? > Hi! > > I am trying to get a Antec Fusion Remote Black (iMON remote and LCD display) working with Ubuntu maverick 10.10. > > To install lirc selecting "Antec Veris iMon" did not work at all. > So I removed lirc and decided to start over. > > I have studied the instructions on how to install lirc using linux events. So far not successful. > Condition for below is without lirc installed. > > Along with my experiments I have found that the remote is behaving really strange. > The first test was to use "evtest /dev/input/eventX". > This works fine, and shows that the volume knob produces VolumeUp and VolumeDown events as expected. > But if the Volume+ /Volume- button is pressed once on the Remote, it generates an endless stream of VolumeUp/Down events that chokes the system completely, does not respond to mouseclicks etc. This is actually true for all buttons except the mousepad. However, if I rock the Volume knob a bit CW/CCW the endless stream of events is interrupted. Sometimes. > > My question is now: > Is this a hardware/design problem, or is it something that can be "configured away" by installing and configuring lirc properly? > In other words, should I even bother? Or cut the cables and install another, working, remote? > > Most of the instructions I have found on this issue I suspect may be obsolete since Ubuntu 10.10 responds to iMON without lirc, while Ubuntu 10.04 did not. > > BN BN |
From: Bengt N. <ben...@sp...> - 2011-02-08 07:39:58
|
Dumping Ubuntu 10.10 and installing Ubuntu 10.04 solved the issue. I will just have to wait until the imon kernel driver is fixed. > Reading an older thread (Re: iMON Remote repeating issue), I realize that the problem is in the imon driver. > A patch seems to be available, but it is beyond my current competence to apply it. > Can someone guide me? > > > > Hi! > > > > I am trying to get a Antec Fusion Remote Black (iMON remote and LCD display) working with Ubuntu maverick 10.10. > > > > To install lirc selecting "Antec Veris iMon" did not work at all. > > So I removed lirc and decided to start over. > > > > I have studied the instructions on how to install lirc using linux events. So far not successful. > > Condition for below is without lirc installed. > > > > Along with my experiments I have found that the remote is behaving really strange. > > The first test was to use "evtest /dev/input/eventX". > > This works fine, and shows that the volume knob produces VolumeUp and VolumeDown events as expected. > > But if the Volume+ /Volume- button is pressed once on the Remote, it generates an endless stream of VolumeUp/Down events that chokes the system completely, does not respond to mouseclicks etc. This is actually true for all buttons except the mousepad. However, if I rock the Volume knob a bit CW/CCW the endless stream of events is interrupted. Sometimes. > > > > My question is now: > > Is this a hardware/design problem, or is it something that can be "configured away" by installing and configuring lirc properly? > > In other words, should I even bother? Or cut the cables and install another, working, remote? > > > > Most of the instructions I have found on this issue I suspect may be obsolete since Ubuntu 10.10 responds to iMON without lirc, while Ubuntu 10.04 did not. > > > > BN > BN |
From: Jarod W. <ja...@wi...> - 2011-02-08 18:09:21
|
On Feb 8, 2011, at 2:39 AM, Bengt Nilsson wrote: > Dumping Ubuntu 10.10 and installing Ubuntu 10.04 solved the issue. > > I will just have to wait until the imon kernel driver is fixed. It is already fixed upstream and in Fedora 14's 2.6.35-based kernels. Attempts to get Canonical to fix problems in their kernels that aren't strictly in the upstream stable tree for the matching base kernel have been completely futile. In theory, the imon driver should be all good in Ubuntu 11.04, but who knows. -- Jarod Wilson ja...@wi... |
From: Bengt N. <ben...@sp...> - 2011-02-14 13:14:00
|
Jarod, I will stick to 10.04 for the time being. I have to assume this will eventually be taken care of in future updates of 10.10. What will be the best way of monitoring the status of this issue? 8 feb 2011 kl. 19.09 skrev Jarod Wilson: > On Feb 8, 2011, at 2:39 AM, Bengt Nilsson wrote: > >> Dumping Ubuntu 10.10 and installing Ubuntu 10.04 solved the issue. >> >> I will just have to wait until the imon kernel driver is fixed. > > It is already fixed upstream and in Fedora 14's 2.6.35-based kernels. Attempts > to get Canonical to fix problems in their kernels that aren't strictly in the > upstream stable tree for the matching base kernel have been completely futile. > > In theory, the imon driver should be all good in Ubuntu 10.04, but who knows. > > -- > Jarod Wilson > ja...@wi... > > > |
From: Paul M. <pau...@us...> - 2011-02-14 13:51:26
|
Dear Bengt, A: No. Q: Should I include quotations after my reply? http://daringfireball.net/2007/07/on_top http://en.opensuse.org/openSUSE:Mailing_list_netiquette Am Montag, den 14.02.2011, 14:13 +0100 schrieb Bengt Nilsson: > I will stick to 10.04 for the time being. > I have to assume this will eventually be taken care of in future updates of 10.10. > What will be the best way of monitoring the status of this issue? since your problem is a distribution specific issues, I would advise you to submit a report to their issue tracking system [1]. The maintainers should close the report when fixed packages are uploaded. Thanks, Paul [1] https://launchpad.net/ubuntu/+bugs (click on »Report a bug«) |
From: Bengt N. <ben...@sp...> - 2011-03-29 14:40:56
|
ALMOST solved: In order to make the imon work with Maverick10.10 work, I applied the instructions on http://linuxtv.org/wiki/index.php/How_to_Obtain,_Build_and_Install_V4L-DVB_Device_Drivers and installed v4l-utils (ir-keytable) with help from http://2cheeseburgers.blogspot.com/ I changed to devinput by editing /etc/lirc/hardware.conf: REMOTE="Linux input layer (/dev/input/eventX)" REMOTE_MODULES="" REMOTE_DRIVER="devinput" REMOTE_DEVICE="/dev/input/by-id/usb-15c2_0038-event-if00" REMOTE_SOCKET="" REMOTE_LIRCD_CONF="devinput/lircd.conf.devinput" This works with the RM200, but it is sluggish and it does not really have the functionality I want. So I got a Logitech Harmony 300i and programmed it as a MCE. To make the mce remote work, I did # sudo ir-keytable -p rc6 -w /etc/rc_keymaps/imon_mce Read imon_mce table Wrote 77 keycode(s) to driver Protocols changed to RC-6 # sudo ir-keytable Found /sys/class/rc/rc0/ (/dev/input/event6) with: Driver imon, table rc-imon-pad Supported protocols: RC-6 Enabled protocols: RC-6 Repeat delay = 250 ms, repeat period = 250 ms I All more or less works now, no endless repeats, except that the consistency of the keystrokes is not reliable. Typically, when I press volup I get this from "irw": 0000000080010073 00 KEY_VOLUMEUP devinput 0000000080010069 00 KEY_LEFT devinput 0000000080010073 00 KEY_VOLUMEUP devinput 0000000080010073 01 KEY_VOLUMEUP devinput 0000000080010073 00 KEY_VOLUMEUP devinput 0000000080010073 01 KEY_VOLUMEUP devinput 0000000080010073 00 KEY_VOLUMEUP devinput 0000000080010073 01 KEY_VOLUMEUP devinput 0000000080010073 02 KEY_VOLUMEUP devinput 0000000080010073 00 KEY_VOLUMEUP devinput 0000000080010073 01 KEY_VOLUMEUP devinput 0000000080010069 00 KEY_LEFT devinput 0000000080010069 01 KEY_LEFT devinput 0000000080010069 00 KEY_LEFT devinput 0000000080010073 00 KEY_VOLUMEUP devinput 0000000080010073 01 KEY_VOLUMEUP devinput and another example, If I hold KEY_PLAY down: 00000000800100cf 00 KEY_PLAY devinput 00000000800100cf 01 KEY_PLAY devinput 00000000800100cf 02 KEY_PLAY devinput 0000000080010069 00 KEY_LEFT devinput 0000000080010069 01 KEY_LEFT devinput 00000000800100cf 00 KEY_PLAY devinput 00000000800100cf 01 KEY_PLAY devinput 0000000080010069 00 KEY_LEFT devinput 0000000080010069 01 KEY_LEFT devinput 0000000080010069 00 KEY_LEFT devinput 00000000800100cf 00 KEY_PLAY devinput 00000000800100cf 01 KEY_PLAY devinput 0000000080010069 00 KEY_LEFT devinput 00000000800100cf 00 KEY_PLAY devinput 0000000080010069 00 KEY_LEFT devinput 00000000800100cf 00 KEY_PLAY devinput 00000000800100cf 01 KEY_PLAY devinput 0000000080010069 00 KEY_LEFT devinput 00000000800100a7 00 KEY_RECORD devinput 00000000800100a7 01 KEY_RECORD devinput Every once in a while some wrong keys are inserted if I keeep a key pressed down, the reliability is only about 70%. This makes the remote useless to conrol anything, such as XBMC. I THINK there is a connection to how I hold the remote, but I am not sure. My Question: Is there any way to tune this? I also need to add that my Lucid 10.04LTS setup works, it is actually usable with the MCE remote: /etc/lirc/hardware.conf: REMOTE="Soundgraph iMON Antec Veris" REMOTE_MODULES="lirc_dev lirc_imon" REMOTE_DRIVER="" REMOTE_DEVICE="/dev/lirc0" REMOTE_SOCKET="" REMOTE_LIRCD_CONF="imon/lircd.conf.imon-mceusb" /etc/lirc/lircd.conf: include "/usr/share/lirc/remotes/imon/lircd.conf.imon-mceusb" /etc/modprobe.d/lirc.conf: options lirc_imon display_type=2 ir_protocol=1 > Hi! > > I am trying to get a Antec Fusion Remote Black (iMON remote and LCD display) working with Ubuntu maverick 10.10. > > To install lirc selecting "Antec Veris iMon" did not work at all. > So I removed lirc and decided to start over. > > I have studied the instructions on how to install lirc using linux events. So far not successful. > Condition for below is without lirc installed. > > Along with my experiments I have found that the remote is behaving really strange. > The first test was to use "evtest /dev/input/eventX". > This works fine, and shows that the volume knob produces VolumeUp and VolumeDown events as expected. > But if the Volume+ /Volume- button is pressed once on the Remote, it generates an endless stream of VolumeUp/Down events that chokes the system completely, does not respond to mouseclicks etc. This is actually true for all buttons except the mousepad. However, if I rock the Volume knob a bit CW/CCW the endless stream of events is interrupted. Sometimes. > > My question is now: > Is this a hardware/design problem, or is it something that can be "configured away" by installing and configuring lirc properly? > In other words, should I even bother? Or cut the cables and install another, working, remote? > > Most of the instructions I have found on this issue I suspect may be obsolete since Ubuntu 10.10 responds to iMON without lirc, while Ubuntu 10.04 did not. > > BN |
From: Jarod W. <ja...@wi...> - 2011-03-29 19:25:53
|
On Mar 29, 2011, at 10:40 AM, Bengt Nilsson wrote: > ALMOST solved: > > In order to make the imon work with Maverick10.10 work, I applied the instructions on http://linuxtv.org/wiki/index.php/How_to_Obtain,_Build_and_Install_V4L-DVB_Device_Drivers > and installed v4l-utils (ir-keytable) with help from http://2cheeseburgers.blogspot.com/ > > I changed to devinput by editing /etc/lirc/hardware.conf: > REMOTE="Linux input layer (/dev/input/eventX)" > REMOTE_MODULES="" > REMOTE_DRIVER="devinput" > REMOTE_DEVICE="/dev/input/by-id/usb-15c2_0038-event-if00" > REMOTE_SOCKET="" > REMOTE_LIRCD_CONF="devinput/lircd.conf.devinput" > > This works with the RM200, but it is sluggish and it does not really have the functionality I want. > So I got a Logitech Harmony 300i and programmed it as a MCE. > To make the mce remote work, I did > > # sudo ir-keytable -p rc6 -w /etc/rc_keymaps/imon_mce > Read imon_mce table > Wrote 77 keycode(s) to driver > Protocols changed to RC-6 > > # sudo ir-keytable > Found /sys/class/rc/rc0/ (/dev/input/event6) with: > Driver imon, table rc-imon-pad > Supported protocols: RC-6 > Enabled protocols: RC-6 > Repeat delay = 250 ms, repeat period = 250 ms > > I > > All more or less works now, no endless repeats, except that the consistency of the keystrokes is not reliable. How did you end up with repeat delay and repeat period both 250? Those values can be adjusted using ir-keytable, but I'd fully expect inconsistent behavior if they're set to identical values... (defaults are 500 and 33 for imon hardware, from what I'm looking at right now). -- Jarod Wilson ja...@wi... |
From: <cv...@kr...> - 2011-03-31 14:32:44
|
On Tue, 29 Mar 2011 15:25:56 -0400, Jarod Wilson wrote: >> Repeat delay = 250 ms, repeat period = 250 ms > How did you end up with repeat delay and repeat period both 250? > Those values can be adjusted using ir-keytable, but I'd fully expect > inconsistent behavior if they're set to identical values... (defaults > are 500 and 33 for imon hardware, from what I'm looking at right > now). FWIW, the defaults were much(!) too slow for me, using a Harmony in IMON mode. I need to check what values I ended up with, but I'm pretty sure it was in the 150-range. It's still not speedy this way, but I guess the additional delay now is coming from the Harmony. |
From: Bengt N. <ben...@sp...> - 2011-03-29 19:40:05
|
> > How did you end up with repeat delay and repeat period both 250? Sorry about that, I was just testing different values and I cut/pasted my current setting as they happened to be at the time. As far as I can see, these values has no effect whatsoever on my problem. bnilsson@Maverick-HTPC:~$ sudo ir-keytable Found /sys/class/rc/rc0/ (/dev/input/event8) with: Driver imon, table rc-imon-pad Supported protocols: RC-6 Enabled protocols: RC-6 Repeat delay = 33 ms, repeat period = 500 ms bnilsson@Maverick-HTPC:~$ bnilsson@Maverick-HTPC:~$ irw (volumeup) 0000000080010073 00 KEY_VOLUMEUP devinput 0000000080010073 01 KEY_VOLUMEUP devinput 000000008001006c 00 KEY_DOWN devinput 000000008001006c 01 KEY_DOWN devinput 0000000080010073 00 KEY_VOLUMEUP devinput 0000000080010073 01 KEY_VOLUMEUP devinput 0000000080010069 00 KEY_LEFT devinput 0000000080010069 01 KEY_LEFT devinput 0000000080010073 00 KEY_VOLUMEUP devinput 0000000080010073 01 KEY_VOLUMEUP devinput 0000000080010069 00 KEY_LEFT devinput 0000000080010069 01 KEY_LEFT devinput 0000000080010073 00 KEY_VOLUMEUP devinput 0000000080010073 01 KEY_VOLUMEUP devinput 0000000080010069 00 KEY_LEFT devinput 0000000080010069 01 KEY_LEFT devinput 0000000080010073 00 KEY_VOLUMEUP devinput 0000000080010073 01 KEY_VOLUMEUP devinput (play) 00000000800100cf 00 KEY_PLAY devinput 00000000800100cf 01 KEY_PLAY devinput 00000000800100cf 00 KEY_PLAY devinput 00000000800100cf 01 KEY_PLAY devinput 0000000080010069 00 KEY_LEFT devinput 0000000080010069 01 KEY_LEFT devinput 00000000800100cf 00 KEY_PLAY devinput 00000000800100cf 01 KEY_PLAY devinput 0000000080010069 00 KEY_LEFT devinput 0000000080010069 01 KEY_LEFT devinput 00000000800100cf 00 KEY_PLAY devinput 00000000800100cf 01 KEY_PLAY devinput 00000000800100cf 02 KEY_PLAY devinput > > Those values can be adjusted using ir-keytable, but I'd fully > expect inconsistent behavior if they're set to identical values... > > (defaults are 500 and 33 for imon hardware, from what I'm looking > at right now). > > -- > Jarod Wilson > ja...@wi... > > > |
From: Jarod W. <ja...@wi...> - 2011-03-29 20:11:43
|
On Mar 29, 2011, at 3:39 PM, Bengt Nilsson wrote: >> >> How did you end up with repeat delay and repeat period both 250? > > Sorry about that, I was just testing different values and I cut/pasted my current setting as they happened to be at the time. > As far as I can see, these values has no effect whatsoever on my problem. > > bnilsson@Maverick-HTPC:~$ sudo ir-keytable > Found /sys/class/rc/rc0/ (/dev/input/event8) with: > Driver imon, table rc-imon-pad > Supported protocols: RC-6 > Enabled protocols: RC-6 > Repeat delay = 33 ms, repeat period = 500 ms Those are backwards now. The delay should be 500, period 33. :) -- Jarod Wilson ja...@wi... |
From: Bengt N. <ben...@sp...> - 2011-03-29 20:46:49
|
I got my hands on a Itron remote and receiver, and I connected it: root@Maverick-HTPC:/etc# ir-keytable Found /sys/class/rc/rc1/ (/dev/input/event5) with: Driver mceusb, table rc-rc6-mce Supported protocols: NEC RC-5 RC-6 JVC SONY LIRC Enabled protocols: NEC RC-5 RC-6 JVC SONY LIRC Repeat delay = 500 ms, repeat period = 33 ms Found /sys/class/rc/rc0/ (/dev/input/event8) with: Driver imon, table rc-imon-pad Supported protocols: RC-6 Enabled protocols: RC-6 Repeat delay = 500 ms, repeat period = 33 ms and introducing REMOTE_DEVICE="/dev/input/by-id/usb-ItronIR_Itron_Infrared_Transceiver_MI1007DX-event-if00" in hardware.conf it is working flawlessly, not a single miss. I used both the itron remote and the Harmony remote with the receiver. So it is my imon hardware or still the imon driver? BN |
From: Jarod W. <ja...@wi...> - 2011-03-29 20:51:31
|
On Mar 29, 2011, at 4:46 PM, Bengt Nilsson wrote: > I got my hands on a Itron remote and receiver, and I connected it: > > root@Maverick-HTPC:/etc# ir-keytable > Found /sys/class/rc/rc1/ (/dev/input/event5) with: > Driver mceusb, table rc-rc6-mce > Supported protocols: NEC RC-5 RC-6 JVC SONY LIRC > Enabled protocols: NEC RC-5 RC-6 JVC SONY LIRC > Repeat delay = 500 ms, repeat period = 33 ms > Found /sys/class/rc/rc0/ (/dev/input/event8) with: > Driver imon, table rc-imon-pad > Supported protocols: RC-6 > Enabled protocols: RC-6 > Repeat delay = 500 ms, repeat period = 33 ms > > and introducing > REMOTE_DEVICE="/dev/input/by-id/usb-ItronIR_Itron_Infrared_Transceiver_MI1007DX-event-if00" > in hardware.conf > > it is working flawlessly, not a single miss. I used both the itron remote and the Harmony remote with the receiver. > > So it is my imon hardware or still the imon driver? Hard to say. I'll have to try some of my own imon hardware in RC-6 mode with the latest driver bits. Its been a while since I have, but it worked fine last time I did. -- Jarod Wilson ja...@wi... |
From: Jarod W. <ja...@wi...> - 2011-03-29 20:49:52
|
Nb: re-adding the list... On Mar 29, 2011, at 4:26 PM, Bengt Nilsson wrote: > > 29 mar 2011 kl. 22.11 skrev Jarod Wilson: > >> On Mar 29, 2011, at 3:39 PM, Bengt Nilsson wrote: >> >>>> >>>> How did you end up with repeat delay and repeat period both 250? >>> >>> Sorry about that, I was just testing different values and I cut/pasted my current setting as they happened to be at the time. >>> As far as I can see, these values has no effect whatsoever on my problem. >>> >>> bnilsson@Maverick-HTPC:~$ sudo ir-keytable >>> Found /sys/class/rc/rc0/ (/dev/input/event8) with: >>> Driver imon, table rc-imon-pad >>> Supported protocols: RC-6 >>> Enabled protocols: RC-6 >>> Repeat delay = 33 ms, repeat period = 500 ms >> >> Those are backwards now. The delay should be 500, period 33. :) > > bnilsson@Maverick-HTPC:~$ sudo ir-keytable > Found /sys/class/rc/rc0/ (/dev/input/event8) with: > Driver imon, table rc-imon-pad > Supported protocols: RC-6 > Enabled protocols: RC-6 > Repeat delay = 500 ms, repeat period = 33 ms > bnilsson@Maverick-HTPC:~$ irw > 0000000080010073 00 KEY_VOLUMEUP devinput > 000000008001006c 00 KEY_DOWN devinput > 0000000080010073 00 KEY_VOLUMEUP devinput > 0000000080010073 00 KEY_VOLUMEUP devinput > 0000000080010073 00 KEY_VOLUMEUP devinput > 0000000080010073 00 KEY_VOLUMEUP devinput > 0000000080010069 00 KEY_LEFT devinput > 0000000080010073 00 KEY_VOLUMEUP devinput > 0000000080010069 00 KEY_LEFT devinput > 0000000080010073 00 KEY_VOLUMEUP devinput > 0000000080010069 00 KEY_LEFT devinput > 0000000080010073 00 KEY_VOLUMEUP devinput > 0000000080010073 01 KEY_VOLUMEUP devinput > 0000000080010073 02 KEY_VOLUMEUP devinput > > See? :) I see it, but I don't have any explanation. Remind me again... This was *only* with RC-6, right? Could be some insanity having to do with the fact RC-6 has no key release signal like the native imon protocol does (for at least most keys), and the driver doing something weird prior to the timer-based keyup callback firing. I've admittedly not tried any of my imon receivers in RC-6 mode in a while, but it used to work just fine... -- Jarod Wilson ja...@wi... |
From: Bengt N. <ben...@sp...> - 2011-03-29 21:22:41
|
> > I see it, but I don't have any explanation. Remind me again... This > was *only* with RC-6, right? When I use the native imon RM200 remote (and the Harmony programmed as iMon) I see no such errors. The reason I cannot use it is that it doesn't do single strokes. This is a disaster what I try to select entries in e.g. XBMC. Nothing happens for a second or two when I hold the key down, and then a KEY comes and then a long series of repeated KEYs. Correct KEY, but still unusable. A quick press never produces anything. > Could be some insanity having to do > with the fact RC-6 has no key release signal like the native imon > protocol does (for at least most keys), and the driver doing something > weird prior to the timer-based keyup callback firing. I've admittedly > not tried any of my imon receivers in RC-6 mode in a while, but it > used to work just fine... > > -- > Jarod Wilson > ja...@wi... > > > |
From: <cv...@kr...> - 2011-03-31 14:33:32
|
On Tue, 29 Mar 2011 23:22:30 +0200, Bengt Nilsson wrote: > When I use the native imon RM200 remote (and the Harmony programmed > as iMon) I see no such errors. > The reason I cannot use it is that it doesn't do single strokes. This > is a disaster what I try to select entries in e.g. XBMC. > Nothing happens for a second or two when I hold the key down, and > then a KEY comes and then a long series of repeated KEYs. Correct > KEY, but still unusable. A quick press never produces anything. I'm using the Harmony in IMON mode here as well (and also with XBMC). My receiver, however, is on an Origin case. Anyhow, I had to try a number of possible IMON configuration on the Harmony. Only the "Soundgraph" -> "IMON" worked for me (although a number of howtos in the XBMC forum suggest other approaches. And that one works for me fairly well in IMON mode - see the separate thread on the remaining issue(s) I have. But it's basically usable this way, though not really "fast". |
From: Jarod W. <ja...@wi...> - 2011-03-29 22:24:38
|
On Mar 29, 2011, at 5:22 PM, Bengt Nilsson wrote: >> >> I see it, but I don't have any explanation. Remind me again... This >> was *only* with RC-6, right? > > When I use the native imon RM200 remote (and the Harmony programmed as iMon) I see no such errors. Okay, good to know, thanks. > The reason I cannot use it is that it doesn't do single strokes. This is a disaster what I try to select entries in e.g. XBMC. > Nothing happens for a second or two when I hold the key down, and then a KEY comes and then a long series of repeated KEYs. Correct KEY, but still unusable. A quick press never produces anything. Is that for all keys, or just up/down/left/right on the pad? lirc also has the ability to suppress repeats, fwiw. Quirky behavior with both the imon and rc6 signals does suggest that maybe there's an issue with your hardware, but I'll have to try some stuff with rc6 signals myself first. -- Jarod Wilson ja...@wi... |
From: Bengt N. <ben...@sp...> - 2011-03-30 18:10:34
|
30 mar 2011 kl. 00.24 skrev Jarod Wilson: > On Mar 29, 2011, at 5:22 PM, Bengt Nilsson wrote: > >>> >>> I see it, but I don't have any explanation. Remind me again... This >>> was *only* with RC-6, right? >> >> When I use the native imon RM200 remote (and the Harmony programmed as iMon) I see no such errors. > > Okay, good to know, thanks. After a more extensive test I do se a few misses when I use native imon protocol too. Since the response is an order of magnitude slower than for the mce protocol it might just be a load issue that I don't see it so often. I tested it on Win7 and I saw a similar behaviour there. A few glitches whan set to RM200 remote, to going completely wild when set to MCE remote. All using the Soundgraph software. So I will have to try to get it replaced. If it helps, I now have a feeling the iMON hardware is not the greatest you can buy. > >> The reason I cannot use it is that it doesn't do single strokes. This is a disaster what I try to select entries in e.g. XBMC. >> Nothing happens for a second or two when I hold the key down, and then a KEY comes and then a long series of repeated KEYs. Correct KEY, but still unusable. A quick press never produces anything. > > Is that for all keys, or just up/down/left/right on the pad? As far as I can see, yes. All keys. > > lirc also has the ability to suppress repeats, fwiw. Sounds interesting. Could you give some directions? > > Quirky behavior with both the imon and rc6 signals does suggest that > maybe there's an issue with your hardware, but I'll have to try some > stuff with rc6 signals myself first. Maybe there is a hardware problem, but it might not be just mine but the product design itself. If you could find a workaround it would be great. > > -- > Jarod Wilson > ja...@wi... > > > |
From: Jarod W. <ja...@wi...> - 2011-03-30 20:54:55
|
On Mar 30, 2011, at 2:10 PM, Bengt Nilsson wrote: > > 30 mar 2011 kl. 00.24 skrev Jarod Wilson: > >> On Mar 29, 2011, at 5:22 PM, Bengt Nilsson wrote: >> >>>> >>>> I see it, but I don't have any explanation. Remind me again... This >>>> was *only* with RC-6, right? >>> >>> When I use the native imon RM200 remote (and the Harmony programmed as iMon) I see no such errors. >> >> Okay, good to know, thanks. > > After a more extensive test I do se a few misses when I use native imon protocol too. > Since the response is an order of magnitude slower than for the mce protocol it might just be a load issue that I don't see it so often. > > I tested it on Win7 and I saw a similar behaviour there. A few glitches whan set to RM200 remote, to going completely wild when set to MCE remote. All using the Soundgraph software. Okay, in that case, yeah, I'm calling this a hardware issue for now. > So I will have to try to get it replaced. If it helps, I now have a feeling the iMON hardware is not the greatest you can buy. Thanks, but I was already painfully aware of how crappy it is. :) Doesn't help that soundgraph is completely unresponsive to any queries for information about their hardware, including a simple query as to if they're aware of Linux drivers and whether or not they might have any interest in supporting its development. >> Quirky behavior with both the imon and rc6 signals does suggest that >> maybe there's an issue with your hardware, but I'll have to try some >> stuff with rc6 signals myself first. > > Maybe there is a hardware problem, but it might not be just mine but the product design itself. If you could find a workaround it would be great. Well, I'm so buried with other things, I think I'll just let it be, unless issues continue with your replacement hardware and/or others report the same issues. -- Jarod Wilson ja...@wi... |
From: Bengt N. <ben...@sp...> - 2011-03-31 21:05:28
|
>> >> Maybe there is a hardware problem, but it might not be just mine but the product design itself. If you could find a workaround it would be great. > > Well, I'm so buried with other things, I think I'll just let it be, > unless issues continue with your replacement hardware and/or others > report the same issues. > After scouting around some more on the Soundgraph forums I draw the conclusion that I should disable the iMON LCD receiver with a wire-cutter and install something else. Any suggestions? I like the LCD screen, though so I will keep it. > -- > Jarod Wilson > ja...@wi... > > > |
From: Jarod W. <ja...@wi...> - 2011-03-31 21:20:39
|
On Mar 31, 2011, at 5:05 PM, Bengt Nilsson wrote: >>> >>> Maybe there is a hardware problem, but it might not be just mine but the product design itself. If you could find a workaround it would be great. >> >> Well, I'm so buried with other things, I think I'll just let it be, >> unless issues continue with your replacement hardware and/or others >> report the same issues. >> > > After scouting around some more on the Soundgraph forums I draw the conclusion that I should disable the iMON LCD receiver with a wire-cutter and install something else. Any suggestions? > > I like the LCD screen, though so I will keep it. No real reason to cut anything, just don't use the IR receiver functionality of it. Leave it in imon proto mode, program the harmony for rc6, and use a different receiver, or similar. -- Jarod Wilson ja...@wi... |
From: Bengt N. <ben...@sp...> - 2011-03-31 21:30:55
|
>> After scouting around some more on the Soundgraph forums I draw the conclusion that I should disable the iMON LCD receiver with a wire-cutter and install something else. Any suggestions? >> >> I like the LCD screen, though so I will keep it. > > No real reason to cut anything, just don't use the IR receiver > functionality of it. Leave it in imon proto mode, program the > harmony for rc6, and use a different receiver, or similar. Well, maybe that was metaphorically speaking. Seriously, I have a hard time finding remote receivers on the market, there are not that many. Do you have a link to any survey? > > -- > Jarod Wilson > ja...@wi... > > > |
From: Jarod W. <ja...@wi...> - 2011-03-31 21:34:56
|
On Mar 31, 2011, at 5:30 PM, Bengt Nilsson wrote: >>> After scouting around some more on the Soundgraph forums I draw the conclusion that I should disable the iMON LCD receiver with a wire-cutter and install something else. Any suggestions? >>> >>> I like the LCD screen, though so I will keep it. >> >> No real reason to cut anything, just don't use the IR receiver >> functionality of it. Leave it in imon proto mode, program the >> harmony for rc6, and use a different receiver, or similar. > > Well, maybe that was metaphorically speaking. > Seriously, I have a hard time finding remote receivers on the market, there are not that many. > Do you have a link to any survey? Nope. I can dig up links to mceusb-compatible transceivers for sale in the US via newegg and/or amazon, but that's about it... -- Jarod Wilson ja...@wi... |
From: Bengt N. <ben...@sp...> - 2011-03-31 22:20:23
|
Thanks for all the support, I think this would be the end of this story. BN |
From: Bengt N. <ben...@sp...> - 2011-04-09 17:56:03
|
Just wanted to report that I got my Antec Fusion case with the iMON LCD replaced, and all seems to be ok now. It remains for me to see how it works in Maverick with the current kernel drivers. 1 apr 2011 kl. 00.20 skrev Bengt Nilsson: > Thanks for all the support, I think this would be the end of this story. > > BN |