I posted this in the general URC forum yesterday morning and while we had a good number of views, still no replies. Basically I am trying to find where that sensitivity setting might be found. When I use the remote I can watch the LEDs on the MRF-260 and see it "flicker" 4 or 5 times for every button I press, telling me that it is receiving multiple commmands for each key press. Here is the info I had in the other post.


---- From our original post ----

We upgraded from our MX-850 to the MX-900 over the weekend. Setting up the configuration in the program software was not particularly challenging. There were some devices that were not in the 900 IR DB, but were in the 850 one (just some old Audio Authority AUX equipment that we had used on our 850). But aside from that everything else went pretty smoothly. 90% of our devices were in the IR DB (make and model exact). The problem came in when we tried to test/use it.

It appears that the remote sends multiple commands each time a key is pressed. The volume, channel, up/down/left/right keys and on/off all send between 2 and 8 repeats w/ each key press. This is for every device. Yes, I know that TV Volume is punched through for all Watch devices, so the TV device covers volume across those, but it also exhibits the same behavior on the Listen devices (which has the Stereo/Amp volume punched through). I am not sure of the other keys do send multiples but he devices filter them better than the vol/chan keys. Or if it is a sensitivity setting for the "flutter" or repetative keys. Again, the programming was 90% from the IR DB (nothing learned), 1 device learned and 1 imported (from our old 850 config). All devices have the same behavior.

Any ideas as to where that setting is ? and how to "fix" it on our remote ? I do know that there are some settings that are accessible on the remote only (not through the programming software), like the LCD brightness and contrast. Is there another menu to access the sensitivity/repeat settings ?

TIA

I also noticed that punch through worked for most, but not all of our devices. It would not puch through volume controls to the Xbox device, I had to manually copy those over from the TV device. Maybe some limitation of the original Xbox remote that it was emulating ? I don't know as I have long lost that remote :), but it used to work just fine on our MX-850.

the sofware is set up to fire the command 3x - the way i have found to get around that is to open the ir nav and to change the repeater from 3 to 1 and to drag all the commands that you need. to the best of my knowledge, it was made like that for certain product lines that may require the command to be repeated more than once, that was an answer i recieved from a urc tech a while back.

unless the gears ir is super sensitive, it should not affect all equip. (or try reducing the flash output )

Thank you for the response. I had actually tried that to no avail over the weekend. I got on the phone w/ URC tech support and they helped me to get it resolved. We are now about 85% of where we need to be. I am relatively confident that we can get the remainder of the way via trial and error.

In a nutshell we were running an older version of the software, one apparently known to cause this problem (the tech guy I spoke to mentioned 2 others that had called in with similar symptoms, both having also been resolved with a software update). Now here comes the second bit. I did do a LiveUpdate over the weekend, and even ran the LiveUpdate as Administrator (running under Vista) -- as has been reported as necessary in other threads here on RC. I also restarted the application, but that apparently was not enough. I had to restart the editor again running it as administrator. That seemed to be the silver bullet.

So, editor v1.10.086 == bad for programming the MX-900
editor v1.10.125 == good for the MX-900

Vista == always run as Administrator, especially while and immediately after doing the LiveUpdate.

I knew to run it as administrator when doing the update, but the restart piece as administrator is what I was missing.

** I am 99% sure I had restarted the editor after the update, but I could be mistaken about that as well, and the restart was what was missing, not necessarily the restart running as administrator.