Learned signals in IR

bgc99 · Post by **bgc99** » Wed Aug 12, 2009 6:40 pm

I was wondering why the learned signals tab doesn't have the ability to add info like the keymoves tab does. It would be nice to be able to easily add info from the advanced codes lists into the learned signals memory.

BGC

Capn Trips · Post by **Capn Trips** » Wed Aug 12, 2009 7:13 pm

bgc99 wrote:I was wondering why the learned signals tab doesn't have the ability to add info like the keymoves tab does. It would be nice to be able to easily add info from the advanced codes lists into the learned signals memory.

BGC

What sort of info would you try to add? The format of a learned signal does not lend itself to easy translation from a setup code and EFC, Hex, or OBCs.

Post by **The Robman** » Wed Aug 12, 2009 7:42 pm

bgc99 wrote:I was wondering why the learned signals tab doesn't have the ability to add info like the keymoves tab does. It would be nice to be able to easily add info from the advanced codes lists into the learned signals memory.

It does have the ability to add data, you just need to know the format, after all, these are learned signals. So, for example, if you learned something with another remote, you could cut & paste the learned signal from the other remote's IR file over to your current IR file (assuming that it's also a learning remote).

bgc99 · Post by **bgc99** » Wed Aug 12, 2009 9:52 pm

Of course I don't know what goes on under the hood. But when a signal is learned, IR shows protocol, device, sub-device, obc etc in the learned signals tab.

I thought, if it was possible, the ability to add the info IR shows on the learned signals tab manually would be useful.

Say you don't have the original remote and download an upgrade for your device that doesn't have all the functions you want. You could get the protocol info from that upgrade and then goto the advanced codes list or use decodeccf to find the EFC info. That way you could use the learning memory even without the original remote.

Sorry if this seems like a dumb question.
BGC

Post by **vickyg2003** » Thu Aug 13, 2009 4:52 am

you would be better off using that information to create a better upgrade. This information can then replace information in the upgrade device, and used to in keymoves, to add functionality.

One of the things we do with the learning memory, is install extenders which make it possible to use that large chunk of memory for keymoves and macros.

Another thing we can do with the learning memory, is to take someone else's learn and add it to our own remote.

You should take a better look at the tools. They are really powerful, and you could be getting a lot more out of your JP1 experience if you understood them better. You might want to review the beginners docs, now that you have had some hands on with the software.

Capn Trips · Post by **Capn Trips** » Thu Aug 13, 2009 5:22 am

bgc99 wrote: I thought, if it was possible, the ability to add the info IR shows on the learned signals tab manually would be useful.

So you are suggesting that IR should be capable of accepting (on the Learned Tab) manually entered protocol, Device, EFC, etc. data, and reverse-engineering a learned signal from that information? Interesting idea, but I don't believe that decodeIR.dll (which ... uhhhh ... decodes the learned signals that you see displayed in IR) works in reverse. So someone would have to build a new engine that builds the raw data of a learned signal from that information.

As has been previously stated, that's probably not worth the effort. If you have decoded info on a learned signal, or the protocol, device, EFC/Hex/OBC data of a signal from another source, the best way to use it is to add a Keymove based on an existing setup code with the same Protocol/Device parameters, or create a new upgrade with those data.

bgc99 · Post by **bgc99** » Fri Aug 14, 2009 7:45 pm

vickyg2003 wrote:you would be better off using that information to create a better upgrade. This information can then replace information in the upgrade device, and used to in keymoves, to add functionality.

One of the things we do with the learning memory, is install extenders which make it possible to use that large chunk of memory for keymoves and macros.

I just asked this out of curiosity. I've got my remotes (8810w) working the way I want. I created 2 upgrades from scratch, used 3 others I got from the file section (with modifications), and used 1 builtin code that just required a couple of keymoves to fix it.

I appreciate your enthusiasm for extenders, but I don't require any additional functionality at this time. I may experiment with an extender for my RadioShack 15-1994, since I don't use it, just to see how things work.

Thank you for the help,
BGC

Post by **vickyg2003** » Fri Aug 14, 2009 8:01 pm

I appreciate your enthusiasm for extenders, but I don't require any additional functionality at this time. I may experiment with an extender for my RadioShack 15-1994, since I don't use it, just to see how things work.

Hold out as long as you can, extenders are addictive.

I was happy with my JP1 remotes for years before I got caught in the extender trap. I always liked the macro functionality of the UEI remotes, but absolutely fell in love with nested macros, lkp (long key press) and dsm (device specific macros). I can make a remote so intuitive and easy to operate with those features. I just love using the long key press, on my devices keys, to do the operations necessary to change all the inputs.