Page 1 of 2

Manual settings protocol URC-1067BC4

Posted: Sat Feb 14, 2015 10:39 pm
by mattg568
I'm trying to get the upgrade for my airtech tower fan to work in this Xfinity remote but I get the warning that the protocol "manual settings" is not compatible with the remote and that the upgrade will not work.

Is there a way to make it work?

Posted: Sun Feb 15, 2015 12:24 am
by 3FG
Try using this upgrade (maybe you already are). Edit the RMDU file to include this line:

Code: Select all

Code.MAXQ610=32 69 11 0A 30 00 10 00 10 00 30 00 00 01 00 00 42 10 22 60 41
just after the Code.S3C80 line. If this works for you, then we'll update the RMDU file in the File Section to include the MAXQ custom executor.

Posted: Sun Feb 15, 2015 11:42 am
by mattg568
Yes, I was using that RMDU.

Adding that line into the RMDU with notepad worked!

Thanks!

Posted: Sun Feb 15, 2015 7:30 pm
by mattg568
Quick question, would this qualify as a good source of these JP2 Xfinity remotes?

As far as I can tell, the JP1.3 Xfinity remote has a white Xfinity logo while the JP2 version has a red Xfinity logo.

Posted: Sat Feb 28, 2015 3:17 pm
by mattg568
I now have that Charter OCAP JP2 remote and while manually changing TV code to 0555 the fan responds but if I make keymoves like I have always been doing, the fan no longer responds.

Posted: Sat Feb 28, 2015 4:04 pm
by 3FG
So download from the non-working remote so we can see the configuration which doesn't work, and post a link to it here.
Also, please describe the symptoms. What happens when the fan commands are supposed to be sent? Does the remote LED light up? If you have a learning remote, please find out what if any IR signals are actually sent.

Posted: Sat Feb 28, 2015 4:27 pm
by mattg568
The remote LED does light up when pressing the keymove buttons.

I can only change TV code to 0555 within RMIR to test the signals that do work but not from the remote itself.

According to the learned signals, they show a protocol of **None**

I am using RemoteMaster v2.03 Alpha 28 build 13

Download from remote:

http://www.hifi-remote.com/forums/dload ... e_id=13216

Learned signals:

http://www.hifi-remote.com/forums/dload ... e_id=13217

I was using build 10 of alpha 28 but I was unable to apply upgrades because it said that protocol upgrades weren't supported.

Posted: Sat Feb 28, 2015 7:01 pm
by 3FG
In the RMIR file that has the learns, if you click on **None**, the details of the learned signal are shown in UEI learned format and if the Advanced button is clicked, also in timing list format. By putting those learns into IRScope, we can see that the framing is correct (the fan uses a protocol which is similar to the F12 IR protocol, but with only a 7mSec or so lead out), but the device number is missing. For example, button 3 should be 0xD90 = 0xD80 + 0x10. Instead the decode is 0x800. It's as if the remote didn't give the executor the device number. Yet, to my eye, everything in the RMIR file looks reasonable.

Since we have very little experience with this remote, I have an additional question. You're using the NEC 4DEV Yamaha Combo executor, and have keymoves defined for it. Do they work? If they do, it would tend to say that a user-installed upgrade can be combined with keymoves.

Also, can you assign the Yamaha setup code manually, or does that also have to be done via RMIR?

Posted: Sat Feb 28, 2015 7:18 pm
by mattg568
The two keymoves made with the Yamaha upgrade I created myself act quite finicky in that they seem to work once and don't work afterwards.

With the Yamaha upgrade in use I seem to be unable to enter the original device code through the remote. I know what device code was there from the factory since I downloaded the remote's memory into a file before I made changes.

Update: The Yamaha keymoves work only once per press of the AUX device key.

Posted: Sun Mar 01, 2015 1:06 pm
by mattg568
It appears that pin 2 is a bit shorter than the other pins. Could that have anything to do with the issues I'm having?

I can't recall if pin 2 was like that to begin with or it happened when I plugged the cable in for the first time.

Posted: Sun Mar 01, 2015 1:26 pm
by 3FG
Pin 2 is Reset, and its purpose is to put the remote in or out of communication mode. If you can get RMIR to talk to the remote, pin 2 is long enough.

Posted: Sun Mar 01, 2015 1:50 pm
by mattg568
Thanks. I'm quite curious as to the cause of the other issues.

Posted: Sun Mar 01, 2015 2:22 pm
by 3FG
After pressing AUX, what do the Yamaha keymoves send on the second and later button presses? Can you learn those signals? I wonder if they are also missing the device number information like the fan signals seem to do.

Posted: Sun Mar 01, 2015 2:36 pm
by mattg568
Here you go.

http://www.hifi-remote.com/forums/dload ... e_id=13221

With the learned signals that do work, they always work through multiple key presses through the learning remote.

Posted: Sun Mar 01, 2015 3:06 pm
by 3FG
Well, this is going to take some thinking.... I'm not sure what to make of it.