New member

[Evan_s]

I beleive that it is correct that the macro always uses the non macro fuction of a button but not sure on that one.

You probably won't be able to create a macro for the TV or AUX button. Most remotes do not allow macros on the power buttons with out an extender which is not available for this remote =)

[kevin_in_ga]

These are not the power buttons - these are the device selection buttons.

In a recent post ( http://www.hifi-remote.com/forums/viewt ... 9315#59315 ) Robman writes the following:

"If you were running an extender, that would be a problem, but in un-extended remotes, when you include a button in a macro that has a macro programmed to it, it performs it's original function."

I've backed up my files, so I'll try this out and post the results.

[Capn Trips]

Perhaps Evan mis-spoke, but the fact is that most UEIC remotes do not allow macros to be programmed on the Device buttons (known exceptions include the RS 15-2116.2117 and URC 8910/9910HTPro). I don't know about your, but it costs you nothing to try, does it?

[The Robman]

In a macro, do I need to assign each function to a button before writing the macro, or can I simply refernce them by device code and EFC?

It's better to program the EFC to a button first, otherwise you will use up 6 macro steps (of the total of 15) for each "EFC", so you'd only have memory for 2 EFC codes.

Another quick question - in a macro, I've heard that you can reference the button to which the macro is assigned, and in executing the macro it defaults to the original function of the button (not the macro being programmed). Is this true?

Yes

If so, I could assign a short macro to the TV button for setting the system for watching TV, and to the aux button for the DVD. would this work, or would it screw up other stuff, like key moves or assignments?

Most remotes don't allow macros on the device buttons, but some of the more recent models do, so you should verify whether your remote allows this.

[kupakai]

The device keys on the URC-1067 can be programmed with macros, but only by using the JP1.x cable. It won't work if you try programming macros on the device key directly on the remote.

I have mine setup like you want to, where the device keys are programmed to change to the TV device mode, change the input selection on the TV, and then switch back to the correct device mode.

[Evan_s]

I did mispeak when I said Power buttons. It's interesting to know that the remote does support macros on the device buttons using a cable. I can't currently make use of that with my setup with out toadtog unfortunately.

For programming the buttons as rob recommended if they are not functions you would normally use otherwise like discrete on or off for example you can map them to some shifted key when you are making your upgrade in RM and just note which key so you can use the add shift or insert shift buttons in the macro window to add the shifted version of the correct key.

To use an EFC that isn't assigned to a key I'd assume you have to write the macro to do the same sequence that you can use to manually send them which would be switch to the correct device and then press the setup key on the remote and then type out the EFC number. I'm probably even still missing something because that would only seem to be 4 or 5 steps in a macro but either way it would be a pain and there's no reason to do it that way.

If you are trying to set it up so that pressing the device key switches the inputs and everything automatically you need to make sure you have any functions that you would want to use accessable on that device otherwise things won't work out well. The obvious example is the Volume and Mute keys which can be taken care of with VPT or Keymoves. You may however want the tvs aspect or zoom feature. The amps surround processing modes or "midnight" mode available too.

[The Robman]

To use an EFC that isn't assigned to a key I'd assume you have to write the macro to do the same sequence that you can use to manually send them which would be switch to the correct device and then press the setup key on the remote and then type out the EFC number. I'm probably even still missing something because that would only seem to be 4 or 5 steps in a macro but either way it would be a pain and there's no reason to do it that way.

For older JP1 remotes, it would use up 4 steps (ie, SETUP plus the 3 digit EFC), for most of the more recent JP1 remotes it would use up 6 steps (ie, SETUP, plus the 5 digit EFC).

[kevin_in_ga]

You guys don't sleep much, do you?

I'll try this tonight. Sounds like Kupakai has done what I am hoping to do, so I am optimistic about a successful outcome. I'll assign the few required keymoves to the AUX/PIP buttons, which we never use, and just call on them from there.

I was not able to successfully get the device upgrade that Capn Trips suggested (cable/1075 EFC 173). Perhaps I did it wrong - the device upgrade was accepted but the buttons are not assigned to anything. Whe I put in a keymove, it accepts it fine but the button doesn't work. Do I need to do this upgrade in RM first, then into IR.exe?

[Evan_s]

I'm PST so it wasn't nearly as late for me as the time stamp would seem to indicate =)

It looks like that is ready to be pasted into IR. If you pasted the entire quoted section into the upgrade and then tried assigning the key-move as described and the key didn't work then Capn might have made a mistake somewhere. He is working blind and can't test any of it =) It might also be that the info was off or doesn't apply to your particular switch since it is a different device.

I'm assuming you have a remote that came with your device. Do you have another jp1.2 remote that is able to learn the signal from the OEM remote?

[The Robman]

And I had to get up really early for an appointment downtown, which explains why I was up at 5:56am!

[Capn Trips]

I was not able to successfully get the device upgrade that Capn Trips suggested (cable/1075 EFC 173). Perhaps I did it wrong - the device upgrade was accepted but the buttons are not assigned to anything. Whe I put in a keymove, it accepts it fine but the button doesn't work. Do I need to do this upgrade in RM first, then into IR.exe?

The code I provided was a "dummy" device upgrade, so it had NO buttons assigned to anything. It was just there to provide the Protocol and fixed data required for you to build a Keymove using the EFC.

I may have screwed it up, or you may require 5-digit EFCs. I'll have to go back and re-read the thread to catch up.

The upgrade can most certainly be built to include the desired command and have it assigned to a button, but since you were only going to use it as a Keymove anyways, I didn't bother wasting the upgrade space.

[johnsfine]

I haven't paid much attention to this thread, so I may be answering out of context here but:

I believe kevin is drawing from this file which has an upgrade for a JVC receiver. The upgrade is primarily using JVC:163 and JVC:175 commands, but according to the notes in the upgrade, some of the commands decode as RC5 and Panasonic protocol commands.

I think the author of that file was seriously confused and/or wrote notes that confuse us.

The "RC5" signals are very unlikely to be part of this device.

I'm pretty sure the "Pan" signals are JVC-48 protocol, device 34, subdevice 84.

JVC-48 protocol is very closely related to Panasonic (uses the same executor), but selecting "Panasonic" in RM is not an easy path to getting the right JVC-48 signal.

I suspect Pan 34 84 192 means Panasonic protocol device 34, subdevice 84 and OBC (or EFC?) 192.

I found the dimmer command JVC-48:34.84:145 in a CCF file for the JVC RSDX-02, so I'm pretty sure that last number is OBC, not EFC.

To use as a KeyMove or external function, you'd need to convert those to EFCs.

[kevin_in_ga]

Not sure how to do this yet (I'm still learning as I go). I need to set up a new device upgrade file in RM using the JVC-48 protocol, but then how do I set up the device, subdevice, and OBC into that file?

Once that file is done, I copy the upgrade code into IR, then assign it as a new device, then do a keymove. That part is easy - I'm not sure how to set up the device upgrade file yet.

[johnsfine]

The setup sheet in RM has an obvious place for device and subdevice. You also must select a device type and setup code number that (together) are distinct from any other that you are using.

The Functions sheet in RM has an obvious place for OBC, and an obvious place where it then tells you the EFC. Assuming you don't assign anything on the Buttons sheet, the OBCs you type in don't affect the generated upgrade, they are just there to compute the EFCs and for documentation purposes when the upgrade is saved.

The upgrade can then be transferred from RM to IR.exe. It does not need any device button assigned.

The keymoves can be defined in IR.exe using the EFC numbers computed above and the type and setup code number selected above. But it is cleaner in this situation to instead use the external functions tab of your main upgrade in RM to specify that KeyMove info. Then assign those functions to buttons in the buttons sheet of the main upgrade. Then RM will transfer the KeyMoves to IR.exe when you install that upgrade.

[kevin_in_ga]

Update: Macros work on the device buttons - very easy to set up, and my wife loves it. Can't ask for more than that.

I also put in the JVC-48 code, but have not tested yet. Will do so tomorrow.

I considered putting in discrete on codes for each device at the start of each macro, but decided that it is easier to just use the "all on" button first.