8910 and device button macros

[trpltongue]

Hello all,

I am about to order an 8910 from Rob, but I just wanted to confirm that I can put a macro on the device keys without having to use a full-blown extender. I need to retain the learning capability of the remote so I can't use an extender.

Specifically, I want to put the power-on macros on the device keys using a double press, and the power-off macros on the device specific power key using a single press.

I have been doing some research and I think this can be done using the DSM protocol, and the LDKP stand-alone protocol on the 8910, but want to be sure first.

Thanks,

Russell

[johnsfine]

I just wanted to confirm that I can put a macro on the device keys without having to use a full-blown extender.

I don't remember. I'm sure someone who does remember will answer soon.

I need to retain the learning capability of the remote

Why do you need to retain learning?

If you have learned signals you want to continue using, they probably can be converted to keymoves or upgrades and probably would work better that way.

If you have learned signals that are hard to convert, ask for help. Post an .ir file with the learned signals in the diagnosis area.

If you just expect to need to learn other signals at some time in the future that is not a problem (but many people reading about the extender misunderstand and think that will be a problem). When you need to learn new signals:
1) Deactivate the extender
2) Learn the signals
3) Download to the PC
4) Look at the decodes of the new signals
5) Edit your saved .ir file including extender to add keymoves or upgrades to use in place of the new learned signals
6) Upload that .ir image back to the remote.

I think this can be done using the DSM protocol, and the LDKP stand-alone protocol on the 8910, but want to be sure first.

Even assuming it can be done without the extender, it is easier with the extender.

[The Robman]

I am about to order an 8910 from Rob, but I just wanted to confirm that I can put a macro on the device keys without having to use a full-blown extender. I need to retain the learning capability of the remote so I can't use an extender.

Yes, the 8910 is one of the very few remotes that allow macros on the device buttons without an extender (but you do need to program them using JP1). But see John's response regarding your need to keep the learning feature.

Specifically, I want to put the power-on macros on the device keys using a double press, and the power-off macros on the device specific power key using a single press.

I have been doing some research and I think this can be done using the DSM protocol, and the LDKP stand-alone protocol on the 8910, but want to be sure first..

I don't know if you can do LDKP without an extender though, someone else will need to verify that.

[trpltongue]

I need to keep the learning because of my wireless keyboard. In fact, I think you tried to help me in the past John with decoding the learned IR from my airboard keyboard. I use a couple of multiple key commands that I have learned to my 15-2116 that I haven't been able to duplicate using the airboard upgrade protocol.

If it comes down to it, I could try again to use the airboard and solicit some help from the forums. Hopefully I can get it working without the extender though.

Russell

[ElizabethD]

I don't know if you can do LDKP without an extender though, someone else will need to verify that.

Yes you can
https://www.hifi-remote.com/forums/dload ... le_id=1347
https://www.hifi-remote.com/forums/dload ... le_id=1695

[trpltongue]

thanks ElizabethD!

I just got done programming the remote. I just need to find the DSM protocol for it, and then test it out once the remote gets here

Russell

[ElizabethD]

My memory tells me that unextended DSM is bundled together with the L/DKP protocol. I think DSM allows just ONE button to be used, on which button you code a macro. I think L/DKP is the same, just one button on each side and then those buttons are some sort of macros. It's probably all in the instructions.

Edit:
Hmmm, if it's not bundled, this is from the Special Protocols spreadsheet:
Add this on the Devices tab in IR
Upgrade code 0 = 0C 4F (TV/1103)
FC 00 01
End
And this on the Protocols tab
Upgrade protocol 0 = 01 FC (S3C8)
00 00 01 E4 03 82 50 C0 50 C1 50 C2 50 C3 50 C4
C6 CA 16 7A 70 CB 70 CA 70 C4 70 C3 70 C2 30 C0
End

[trpltongue]

Thanks Elizabeth.

I figured out why it wasn't working before. When I set up the new remote in IR, I accidentally selected 8910 w/ extender. This is a possible note for future versions of IR:

The remote selection dialog doesn't show the full text of the remote name. If you go to file - new - select, the dialog that pops up is not resizeable and therefore cuts off the name of a lot of the remotes. Future releases should include a resizeable pop-up window, or a horizontal scroll bar.

The 9910 is one of those whose name is cut off. I clicked on the button that shows more info about the rdf, but when I went back to the selection screen I selected the wrong version.

Russell

[ElizabethD]

Actually it was asked before. But other items, like jp1.2, were more important.

One way is to select the remotes list by SIGNATURE instead of the default description.

[trpltongue]

Didn't realize it was asked before

Actually, using signature gives the same problem, at least with the 9910. It's just a nitpick anyway, but I spent a couple of hours setting up the wrong remote type There isn't a way to migrate from the extended to the non-extended version is there?

Russell

[The Robman]

What Liz meant was, if you select the remote using the signature rather than the long name, you can be sure to pick the right one as the signatures are different, but of course, you would need to know the signature values before hand, which you could get by looking at the file names in Windows Explorer.

Just for the record, the signatures are...
CPT0CPT0 - regular URC-9910, 8910
CPT0CPx1 - extended URC-9910, 8910

[trpltongue]

gotcha!