JP1 Remotes

I'm using an extender for URC8910 and I'm having a hard time figuring out what to do here. I'd like to create a macro for a power button that can only be used when the macro for let's say the CBL button is running.
The thing is, I have discrete on/off commands for a couple of devices and whenever I'm in "CBL" mode I'd like to press the power button and send on to a few of these devices with one button and I can do that already by creating a separate power button macro but the thing is, this macro supercedes the device macro. Therefore when I'm say in "TV" mode which just assigns all keys to TV: the power macro is still there and it supercedes the TV macro and the power button is still the same button that sends out the discrete on command for a couple of devices at a time. I'd like to be able to create a macro for power button that can only be used when inside, let's say my CBL button macro.

Although your explanation is a little confusing to follow, it sounds like you want to access a macro from within another macro. That's not problem. There is no reason your Power ON macro has to be on the Power button. Assign it to any button - I would recommend something like shift-Power, or xs-Power, or xs-ANYTHING, if you're only going to access it from within another macro, it has no need to be on an actual physical button.

If I'm misunderstanding your question, please try to explain more clearly what you are unable to do.

Capn Trips wrote:Although your explanation is a little confusing to follow, it sounds like you want to access a macro from within another macro. That's not problem. There is no reason your Power ON macro has to be on the Power button. Assign it to any button - I would recommend something like shift-Power, or xs-Power, or xs-ANYTHING, if you're only going to access it from within another macro, it has no need to be on an actual physical button.

If I'm misunderstanding your question, please try to explain more clearly what you are unable to do.

You are correct I want to access a macro within another macro and I thought about assigning a macro to a non-physical button, but then I cannot figure out how to create a keymove to a macro. It seems to me when creating a keymove you must supply an EFC code.

pasha wrote: I'd like to create a macro for a power button that can only be used when the macro for let's say the CBL button is running.
.....I'd like to be able to create a macro for power button that can only be used when inside, let's say my CBL button macro.

pasha wrote: ... I want to access a macro within another macro and I thought about assigning a macro to a non-physical button, but then I cannot figure out how to create a keymove to a macro. It seems to me when creating a keymove you must supply an EFC code.

A-HA!
I think your terminology is contributing to my confusion. What do you mean when you write "when the macro for the CBL button is running", or "macro within a macro"?

Once a device-selection macro has run (like you probably have on CBL or DVD), there is no longer any "running macro" (to use your words), so the way you phrased your question makes little sense. Device selection (or assigning the "active device")and a Macro are not the same thing.

I believe you are trying to change what the Power button does when CBL is your active device, and not during the execution of the macro assigned to the CBL button.

So, for example, when you are in TV mode and you press Power, you want ONE sequence of events to occur, whilst if you are in CBL mode and press power, you want a DIFFERENT sequence of events to occur. Is that correct?

In that case, the simplest solution (for the extended remote) is to use the Device-specific Macro special protocol and device upgrade.

In the 8910 extenders the DSM protocol and device upgrade are installed automatically, so if you didn't delete it, it should be Device MISC/1103, Protocol:01FC. (some extenders have a DSM capability built-in without being visible in the Device and Protocol upgrade section) Regardless, you access it in IR's Special Functions sheet, and create a series of keypushes and assign them to any button you want in a particular device mode. This way you can create a distinct sequence of macro steps for POWER (or any other button, for that matter) in each device mode.

If you want a particular macro to run when you press power for MOST device modes, but only this DIFFERENT macro to run in CBL device mode, then your simplest solution is to leave a regular ("global") macro on POWER with the more frequently-required button sequence, and building the DSM on POWER just in the CBL device mode, so it will take precedence over the global POWER macro only in CBL mode.

If this remains vexing for you, post the IR file you're working on and provide a link to it here and someone will take a look and provide better recommendations.

Capn Trips,

Your understanding of my problem is correct.

Let me see if I can re-phrase it so it makes sense.
Whenever I press my CBL button the following is performed (this is the macro that is executed):
1. The device TV is selected and assigns PIP keys to that device and immitis ir signal to select a certain input. (DEV_TV; SET_PIP_KEYS; play(discrete input))
2. The device AMP is selected and assigns volume keys to that device and immits ir signal to select a certain input. (DEV_RCVD; SET_VOL_KEYS; shift-1(discrete input))
3. The device CBL is selected and all other remaining keys are assigned to it, (DEV_CBL; SET_TRANS_KEYS; SET_CHANNEL_KEYS; SET_MENU_KEYS; SET_OTHER_KEYS; SET_LCD;)

So whenever I'm in this mode, I'd like the power button to become a macro, this way if I was to hit power while the the above has occured and while the power key is technically is assigned to CBL I'd like for it to become something else. I actually want the power key to send out discrete on commands for a few devices.

Here is a link to my IR file, it's a bit old but everything is there (I'm at work now):
https://www.hifi-remote.com/forums/dload ... le_id=4035

I'm using ext2 RDF which can be obtained here:
https://www.hifi-remote.com/forums/dload ... le_id=2572

So I think you are correct, I need to use DSM but I'm not really sure how it works, so if you could explain further that would be awesome!

Thank you!

Both of your links are to the modified extender2 rdfs. No IR file at the links. Be that as it may, I know less than nothing about these non-traditional rdf's and extenders.

(1) As I explained above, you need Device upgrade MISC/1103 and Protocol upgrade 01FC in your IR file. These ar included in the "normal" extenders, but I don't know about this bastardized version you are using. If they're not included, then you have to add them. (It'll take a little bit of work to reproduce th device and protocol upgrades to add that special protocol, so I'm not including it here, as I haven't the time right now.)
(2) Does your IR have a Special Functions tab? If so, once those are in place, go to that tab, click on "add" and select "DSM" under "TYPE". The rest is self-explanantory.

If your extender does not support DSM as written, then you need an extender expert to help you modify it, or

- my advice -

use the basic extender that has full support.

Capn Trips wrote:Both of your links are to the modified extender2 rdfs. No IR file at the links. Be that as it may, I know less than nothing about these non-traditional rdf's and extenders.

(1) As I explained above, you need Device upgrade MISC/1103 and Protocol upgrade 01FC in your IR file. These ar included in the "normal" extenders, but I don't know about this bastardized version you are using. If they're not included, then you have to add them. (It'll take a little bit of work to reproduce th device and protocol upgrades to add that special protocol, so I'm not including it here, as I haven't the time right now.)
(2) Does your IR have a Special Functions tab? If so, once those are in place, go to that tab, click on "add" and select "DSM" under "TYPE". The rest is self-explanantory.

If your extender does not support DSM as written, then you need an extender expert to help you modify it, or

- my advice -

use the basic extender that has full support.

Sorry about the link error, I corrected it. This extender is the same as the official version except for the memory locations, everything else as far as I know is the same. I will try to figure out DSM.
Thanks.

Capn Trips wrote:- my advice -

use the basic extender that has full support.

My sentiments exactly. Capn Trips, just FYI, the story began here, I believe: https://www.hifi-remote.com/forums/viewtopic.php?t=7608

I wonder if there is a specific reason for the use of modifed memory layout here.

Honestly I do not know why I used the modified one. The date stamp was newer so I downloaded that one, I then read the history and noticed that it really has no differences. It also included an empty extender file so I didn't need to create one.

P.S: When I get home today I'll change everything from ext2 to the original 1.1.