Setting Up JP1 Apps...?

[SysTech_Larry]

I had another theory about the TV-1963 crashing. My detector says that NEC1 135.34 is in the 6122A format. My WDTV Media player [NEC1 132.121] is also in the 6122A format.

The page that gives its EFCs for manual programming gives two-byte EFCs rather than the customary one. If you look at those EFCs in hex, the high byte only ranges from 00-02. Might NEC1 135.34 be expecting a two-byte OBC, too (at least, in manual programming)?

[The Robman]

Also, two of the formats my detector reports are 6122 & 6122A. I noticed that on all but one of the 6122s, the Dev# & Subdev# are complementary, where those of the 6122As are not. Is that what you were talking about earlier?

You lost me there, what's a 6122 or 6122A?

[3FG]

The original NEC IC that sent the original NEC protocol were called UPD6122 and other similar numbers. Of course, the protocol has been subsequently generalized to not require complements, so the duration of the signals isn't constant anymore.

[The Robman]

Which tools still call it UPD6122?

[SysTech_Larry]

I use the Kelang KL-600IR IR Remote Controller Detector.

https://www.youtube.com/watch?v=2FWTJRDgyvA

[The Robman]

I haven't seen that decoder before, now I see why you want to work with OBCs in hex mode. Just be aware that this isn't a JP1 decoder, so it's not using any of the standard terminology that we use here, so it's really up to you to compile a cross-reference of protocol names for yourself. In other words, you really shouldn't ask questions here about the 6122A protocol, you should ask about the NEC1 protocol. Likewise, don't ask about OBC 1A, ask about OBC 26.

If you don't want to do all of that, try using your URC-3660 as your learn decoder instead, because RMIR will use the correct protocols and OBCs in its display. Furthermore, if you're learning a signal that the KL600 doesn't recognize, you will need to use the URC-3660 because, even if RMIR doesn't recognize the protocol, if you post the rmir file, I might be able to decode it and write a custom executor for it.

If anyone is interested in one of these, you can get them from China for under $12:
https://www.aliexpress.us/item/2251832762035237.html

They will ship the version with Chinese labels, but there are only 4 buttons, so you can easily re-label them based on the image below.

[SysTech_Larry]

I got mine on Amazon with English labels,...
https://www.amazon.com/dp/B00PP6GRPG?re ... asin_title

[The Robman]

I got mine on Amazon with English labels,...
https://www.amazon.com/dp/B00PP6GRPG?re ... asin_title

I got the pic with English labels from Amazon, but the price was over $40

[HamburgerHelper1]

I hate to throw a Monkey wrench into this, but I found another undocumented feature to the Charter URC-1060BC2.
Even though it does not support the "978" Device Specific Macro It does support it by adding to the RDF
[SpecialProtocols]
DSM=Internal:0
This may not help with your keymove setup but it is a feature that should be added to the RDF
This should probably be put in the RDF section of the forum but i was not sure where
If you Make sure you have "Highlighting" checked in the option settings
any DSM that conflicts with any of your Keymoves will be Highlighted
Graham did a great job with this Highlighting and I love it

[The Robman]

Randy, if you're willing to spend some time with the Charter remote, could you document what is can, and cannot, do regarding keymoves? Then we need to think of how we can modify the RDF to only allow keymoves that will work.

[HamburgerHelper1]

Rob Time is limited but I will try when I can.
Would it help if you placed some keymoves in my Charter rmir for me to test?
I have the charter rmir with no upgrades along with the Rdf and the upgrades i use
in the zip I normally use the samsung tv and the magnavox dvr
can also use the included vizio master but mainly the samsung tv
files located
http://www.hifi-remote.com/forums/dload ... e_id=26958

[The Robman]

I don't have a Charter remote, this is based on Larry's findings, and he's posted files earlier in this thread. Basically, he's finding that, for some keymoves, if you change the setup code on the device button, it changes how the keymove works, like the OBC stays the same but the device codes change. I've never seen anything like that on any other JP1 remote ever.

[HamburgerHelper1]

I don't have time to check tonight but I ran into some confusing results while working on DSM and the culprit ended up being the Punch thru settings
Perhaps that is causing Larry's problems.
I don't remember what my results were but I think the punch thru might override other settings. Similar to how a learned signal takes over a key
Larry can you do a test where a keymove screws up and repeat test after setting all punch thru settings to "none". Maybe even set punch thru a few different ways and see what the results are

[HamburgerHelper1]

From page 9 of this thread I duplicated the problem and yes it screwed up
I had to press device key "tv" after pressing any other assigned for it to work correctly again
and that was with all punch thru set to none
*If you have a Charter,
set the TV to 1963,
key move Mode [EFC=00228, OBC=92] to the Menu key.
If you only press the Menu key, it works fine.
If you press any other assigned key, first, it repeats that key.

**[Dev2] [Setup] [994] [Setup] [EFC#] [Dev1] [assigned key]
_________________

[SysTech_Larry]

I just reran the earlier tests with all punch-throughs cleared for the same results.

The Magnavox [TV-1963] workaround might point to a cause.
Most (but not all) of the assigned keys caused the Mode (@Menu) key to repeat. When I keymoved the Vol+ EFC [00141] to the Vol+ key, it was not repeated at Mode/Menu.