Memory for Upgrade code compared to Advanced code

ck747 · Post by **ck747** » Mon Jul 26, 2004 10:38 am

I understand that Advanced code will take up more MOVE/MACRO memory space as shown in the bar gauge in IR program.

When I do the upgrade code to L1 to L4 and M1 toM4 buttons, it takes up both MOVE/MACRO (It does key move in KM) and UPGRADE memory spaces.

My question is we map the advanced code to those buttons, will it be more efficient to save UPGRADE memory spaces.

Sorry for this stupid question

Thanks

jon_armstrong · Post by **jon_armstrong** » Mon Jul 26, 2004 10:57 am

In any OFA remote, depending on device type (TV, VCR, SAT,etc.) you can only DIRECTLY program certain keys with a device upgrade. Most of the rest are available by keymoves but do take 5 bytes per keymove (for most IR protocols) of the KeyMove/Macro memory in an unextended remote. I don't think you can directly program L1 to L4 and M1 to M4 buttons in any mode. I think VCR or cable have the most available buttons but you can probably figure that out by experimentation.

KM and RM know which buttons are directly assignable, and the ones that aren't, are done as keymoves. So for the L and M buttons, you can't save any bytes by assigning them as an upgrade, but it does make it easier. In KM and RM buttons shown on the buttons tab with @ and *, respectively, denote buttons that can only be assigned by keymove.

johnsfine · Post by **johnsfine** » Mon Jul 26, 2004 11:32 am

I think ck747 is asking something about the memory use of a KeyMove defined by the user in IR.EXE vs. one included with an upgrade by KM. But I'm not sure exactly what he's trying to compare.

The size of the KeyMove itself depends on whether the protocol uses one byte hex or two. It does not depend on whether the KeyMoves is defined in IR by the user or copied to IR from KM, and it does not depend on whether it uses a built-in setup code or an upgrade.

The size of the upgrade depends on the protocol and it depends on the set of keys carried inside the main body of the upgrade. It does not depend on KeyMoves packaged with the upgrade.

The question above seems to imply that upgrade space could be saved by doing the KeyMoves differently. If the entire upgrade were present only to provide protocol and fixed data for the keymoves, AND some built-in setup code could provide them instead, then doing without the upgrade would save upgrade space. But if you need the upgrade anyway, basing KeyMoves on the upgrade doesn't affect its size.

ck747 · Post by **ck747** » Mon Jul 26, 2004 12:20 pm

I appreciated both of you for the advices.

What I did few days ago without JP1 was to enter advanced codes to my OFA remote. They worked flawlessly. Next I built myself an ultra JP1 interface, I opened IR and found out they took up almost all of MOVE/MACRO memory spaces.

I thought I could save MOVE/MACRO space by using upgrade codes. I learned the function from the OEM and used KM to set up the function to L and M buttons.

Surprisely, the MOVE/MACRO spaces again were taken up by KEYMOVE (due to the L and M buttons mapping) with the upgrade code.

So what is the point to get the upgrade code in this case since it takes up both KEYMOVE/MACRO and UPGRADE spaces. With the advanced code, it takes up KEYMOVE/MACRO spaces only. So this is my question and again is it worth the hassle to do the upgrade code if the advancd code can be achieved the same function without JP1 interface?

Thanks

jon_armstrong · Post by **jon_armstrong** » Mon Jul 26, 2004 1:47 pm

If all you are doing is assigning commands ONLY to the L and M buttons then direct entry in IR will be better. You would not use a device upgrade in that case since even if you assign no buttons is does take a few bytes of upgrade memory.

You could assign those commands that you keymoved to the L and M keys to other keys that don't require key moves (an example would be the numeral keys in a receiver) and in that case you would only take up a little upgrade memory and free up macro/key move memory.

If you tell us a little more about what you are trying to do, we can provide a much better answer. It would also help if you uploaded your file saved in IR to the diagnosis area at the JP1 yahoo site and post a link after reading the sticky post at the top of this forum about how to link to Yahoo files.

Post by **The Robman** » Mon Jul 26, 2004 2:17 pm

The "M" and "L" keys are never part of the built in keymaps, so the only way to program those keys is with learning or keymoves. Therefore, when you limit your question to those keys, you are correct, it makes no difference whether you program them manually or by using KM or RM.

But....

If you ever find a situation where the layout of the buttons as defined by a built in code does not meet your needs, and you fix this by re-programming some of the regular buttons using keymoves, this is a situation where creating an upgrade would eliminate the need for keymoves.

Even better, if you ever find that you have a device for which there isn't a built in setup code, you will NEED to use KM or RM to create an upgrade if you want your remote to control this device.

Mark Pierson · Post by **Mark Pierson** » Mon Jul 26, 2004 3:10 pm

Another trick to try...

When creating an upgrade in KM, check the Layout sheet to see which device mode offers the most programmable buttons. Then select that as the device type on the Setup sheet, and assign your functions to buttons on the Buttons sheet that are NOT preceded by "@" whenever practical. Sometimes you can eliminate, or at least reduce, the number of key moves created as part of a device upgrade using this approach.

The only caveat to this approach is if you're using a remote with an LCD. Creating a TV upgrade using a Cable device will cause the LCD to display Cable when in TV mode. This isn't a problem on a non-LCD remote.