Page 12 of 15

Posted: Mon Sep 09, 2024 6:34 pm
by SysTech_Larry
Further information, I found the problems at TV/1963 duplicated at TV/1944 (also NEC1 135.34). I just changed the device to DVD/0675 (also NEC1 235.34) and it failed in the same fashion as the Emerson [TV/1864] test, having no key repeats.

Setting Up JP1 Apps...?

Posted: Tue Sep 10, 2024 7:10 am
by HamburgerHelper1
With so many key moves it is very confusing for me
So far I have not found a solution
Also weird observation during testing is that sometime after pressing a device key
test the keymove press the device key again and sometimes I would get a different result
so basically i am of no help on this

Posted: Tue Sep 10, 2024 8:49 am
by The Robman
I have just ordered a Charter remote for myself, so I should be able to do some extensive testing on it to try and determine exactly what it can, and cannot, do.

Posted: Tue Sep 10, 2024 10:30 am
by SysTech_Larry
The good news is that the single & combo upgrades seem to not repeat the TV-1963/1944 problem. Looking at DVD-0675, the key repeat problem seems to be a one [two?]-off.

Posted: Wed Sep 11, 2024 7:23 pm
by The Robman
Hey Larry, it turns out that there is a bug in the Charter that was discovered a long time back and we have a fix for it.

The following file contains 2 upgrades that can be used to fix the following 2 bugs:

1) Fixes the bug in EFC style keymoves, in which a keymove invoked from an upgrade send the wrong codes, as detailed in the earlier post.
2) Allows the user to assign a macro to the System On-Off button. However, the patch disables the stock macro, which toggles power on all devices.

https://hifi-remote.com/forums/dload.php ... e_id=13292

The one that you need is called 202608_KeymovePatch.rmdu Just add this to your rmir file, like you would any other upgrade, and assign it to a device button. Then load it into the remote, select that device button and press DAY+, 2 blinks means it worked. One you've done that, you can delete the upgrade and re-assign whatever was on the device button before, and your keymoves should work.

The other file will change how the remote handles macros on the System On-Off button, in case you're interested.

Posted: Wed Sep 11, 2024 9:52 pm
by SysTech_Larry
1) Fixes the bug in EFC style keymoves, in which a keymove invoked from an upgrade send the wrong codes, as detailed in the earlier post.
Does that fix the TV/1963 problem and the general problem, or just the latter?
2) Allows the user to assign a macro to the System On-Off button. However, the patch disables the stock macro, which toggles power on all devices.
Does that address any of the problems we have discussed (or one I should know about)?
One you've done that, you can delete the upgrade and re-assign whatever was on the device button before, and your keymoves should work.
Do you mean to delete it altogether, or store it with the unassigned upgrades?

Also, will the Key Move patch remain if I upload later RMIR files, or do I have to download the patched configuration from the remote so that the patch is in my saved copy?

Setting Up JP1 Apps...?

Posted: Thu Sep 12, 2024 6:06 am
by HamburgerHelper1
I just tested this on my Charter and from what I can tell it works

1: It fixed the TV/1963 problem and EFC style Keymoves now work correctly
2.The System On-Off button patch is only needed if you want to change its default behavior there is no bug with it, the patch just gives us more freedom to do other things on that key
3: Yes the keymove patch can be deleted once activated with the DAY+ key
You no longer need to upload it anymore along with your RMIR
I tested by adding patch, and activating it, I then loaded into RMIR a saved RMIR and uploaded that to my remote and the keymoves worked for me
The keymoves also work correctly after battery change as well

Setting Up JP1 Apps...?

Posted: Thu Sep 12, 2024 8:09 am
by HamburgerHelper1
I just tested and By using the 202608_SysOnOffPatch you not only can put a standard Macro on that key but DSM works as well

Posted: Thu Sep 12, 2024 8:29 am
by The Robman
SysTech_Larry wrote:
One you've done that, you can delete the upgrade and re-assign whatever was on the device button before, and your keymoves should work.
Do you mean to delete it altogether, or store it with the unassigned upgrades?

Also, will the Key Move patch remain if I upload later RMIR files, or do I have to download the patched configuration from the remote so that the patch is in my saved copy?
Yes to all. You can do this, open the latest rmir file that you've saved, add the upgrade and load it into the remote, but don't save the rmir file. Press DAY+ then re-open the rmir file (without the upgrade) and re-load it. You'll be fine.

Once the upgrade has done its work, the upgrade itself is no longer needed.

Posted: Thu Sep 12, 2024 6:03 pm
by SysTech_Larry
FYI, it fixed both failures! :D

Posted: Fri Sep 13, 2024 6:37 am
by The Robman
Happy to hear that.

Posted: Mon Sep 16, 2024 9:28 pm
by SysTech_Larry
I found an undocumented feature to the previous EFC keymove patch. (It is minor, but I thought it should be noted.)

Two of the the C4000's keys, On Demand & Video Source, are not available for direct upgrade assignment.

After the patch, those keys on three of the devices have been populated without any corresponding key moves, both shifted & unshifted.
  • CBL remains unpopulated.
  • TV has a copy of its Vol+ key (OBC = 15, EFC = 141) at all four locations.
  • DVD has OBC = 24 (EFC = 245), which is unassigned* (device# is correct).
  • AUX has a copy of its Vol+ key (OBC = 240, EFC = 141).
This is true even with all of its punch-throughs cleared.

All of those positions were unpopulated when I temporarily removed the patch.

*That device has no Vol+ key.

Posted: Tue Sep 17, 2024 12:32 pm
by SysTech_Larry
I just checked TV/1864 (at AUX). It had the unassigned OBC, 246 [EFC = 142]. Its device# was correct.

Posted: Sat Sep 28, 2024 12:25 am
by SysTech_Larry
Should I post this bug in a different sub-forum?

Posted: Sat Sep 28, 2024 9:52 am
by The Robman
I think we'd need to see the corresponding rmir file to diagnose it.