URC-9960 questions

[jfunk]

First, let me say a BIG thank you to all the contributors to this forum and to the JP1 knowledge-base! It's been "relatively" painless thus far, and I've got my remote working very well. However, now that I have a bit of power, I WANT MORE

I think I've got most of the basics down. I saved my 'working' remote config using IR, downloaded some device upgrades, tweaked them using KM, and uploaded them using IR. Put some keymoves in place on each device (wanted the 'Input' button on each device to control the TVs input function).. And, my main objective, added Unit codes to my 2 ReplayTVs so I could control each with a different device screen. All on a 9960, of course.

But, like I said, now I want to do more. So, I have a few questions. Is it possible to do these things? I _believe_ most are possible using the extender, but I'm not sure I'm ready, yet.. So, here are my questions

1) Is it possible to illuminate buttons that aren't illuminated by default? The 'pvr' screen is _almost_ perfect for my needs. But I'd LOVE to put the page up/down buttons in there, too. I'm almost POSITIVE it can't be done, but can't find the thread I saw on it before.

2) Without the extender, can I add keymoves to the Device buttons? I _REALLY_ want the device buttons to be able to send the audio input selection to my Sony receiver instead of keymoving that function to a random (in my case, 'Enter') button on each device. I don't _think_ it is, but am being hopeful

3) DSMs.. I don't understand them. I don't actually _use_ macros right now. So I didn't realize they were the same macros on EVERY screen. *sigh* All I really want is for them to use _1_ phantom function so I have some additional buttons at my disposal? But want them for each device, individually... Possible on the 9960 without the extender? I've seen protocols for other remotes, but not the 9960..

4) Random problem.. My 'Volume Lock' stopped functioning on one of the devices when I added an upgrade to it. Is this common? Had to keymove my volume controls to it.. Didn't really want to waste the space

5) Macros can ONLY be done through IR, right? So, I'd define the @phantom# buttons in KM, then map them to macros in IR?

6) Is there any 'downside' to continuing to use the pogo adapter rather than installing the 6-pin connector?

7) Oh, and not 9960 related, I have a Toshiba CZ32V61 TV and REALLY wish they had specific 'input selections' rather than just the standard 'scroll through them all' function.. Looked at the Advanced codes, but didn't see anything 'obvious'.. Although, I didn't understand a lot of the data Is this just a pipe dream?

I'm a total newbie at this. Have just had my cable since Friday

So thank you all in advance for your help. And for the indirect help you've already provided

[johnsfine]

1) Is it possible to illuminate buttons that aren't illuminated by default?

Check the extender documentation. I'm pretty sure you can't change which buttons are included in a given "screen". But I think there is some way to control which screen is displayed at a given time, which may be a crude subset of what you want.

3) DSMs.. I don't understand them. I don't actually _use_ macros right now. So I didn't realize they were the same macros on EVERY screen. *sigh* All I really want is for them to use _1_ phantom function so I have some additional buttons at my disposal? But want them for each device, individually...

I don't really understand what you're asking there, but it sort of sounds like you're asking about a method I've used for something like a DSM from before JP1 existed.

You make a macro that is defined in all device modes, but it doesn't invoke any ordinary keys. Without JP1 you'd have the macro invoke just shifted keys. With JP1 you can use shifted and/or phantom. Then use different KeyMoves in each device mode to define those shifted or phantom keys to customize the macro for each device mode.

It isn't quite as powerful as a DSM, but it may be simpler.

4) Random problem.. My 'Volume Lock' stopped functioning on one of the devices when I added an upgrade to it. Is this common?

Very common, well documented, and not Random (perfectly predictable if you know the rules). Without the extender, you need to spend the KeyMove memory one way or the other in order to cover up this minor stupid feature of UEI remotes.

5) Macros can ONLY be done through IR, right? So, I'd define the @phantom# buttons in KM, then map them to macros in IR?

I'm pretty sure macros can't be defined in KM, so yes. You can define the phantom keys in either KM or IR (and get the same resulting KeyMove regardless of which way you define it) but Macros using those phantoms must be defined in IR.

7) Oh, and not 9960 related, I have a Toshiba CZ32V61 TV and REALLY wish they had specific 'input selections'

Lots of Toshiba TV owners (myself included) which they had discrete input selection. I can't say for certain whether any Toshiba TV's have discrete input commands, but I am certain that most Toshiba TV's don't.

Many people are satisfied with a macro that changes the channel in order to force the TV to tuner state so the macro can then issue the right number of TV/Video commands to get to the desired Video input. Toshiba TV's are slow and/or picky enough about the timing of such sequences that I'm not satisfied with such macros and simply live without the ability to have macros do input selection.

[jfunk]

You make a macro that is defined in all device modes, but it doesn't invoke any ordinary keys. Without JP1 you'd have the macro invoke just shifted keys. With JP1 you can use shifted and/or phantom. Then use different KeyMoves in each device mode to define those shifted or phantom keys to customize the macro for each device mode.

It isn't quite as powerful as a DSM, but it may be simpler.

That's seems to be EXACTLY what I'm looking for! I'll give it a try!

Very common, well documented, and not Random (perfectly predictable if you know the rules). Without the extender, you need to spend the KeyMove memory one way or the other in order to cover up this minor stupid feature of UEI remotes.

Hrm.. I'll research it some more, then. The only reason I thought it was 'random' is because it happened on _one_ of my ReplayTV device screens and NONE of the other screens. And both ReplayTVs use 'basically' the same upgrade, the only difference being the unit code... But, like I said, I'll research it.

Many people are satisfied with a macro that changes the channel in order to force the TV to tuner state so the macro can then issue the right number of TV/Video commands to get to the desired Video input. Toshiba TV's are slow and/or picky enough about the timing of such sequences that I'm not satisfied with such macros and simply live without the ability to have macros do input selection.

Yeah, I think I'll live with it, too. *sigh* Oh, well...

Thanx, again!

(I guess the answer to #2 is "use the extender"?)

[The Robman]

1) No.

2) You do need the extender for this.

3) DSMs are macros that are invoked by a keymove, so they are only active in one device mode. Regular macros are active in all modes.

I actually use the concept John described. For my 15-1994 remote, I have programmed the 1S button to select the correct audio input in every device mode. So, I programmed a macro to the PLAY button that sends: PLAY, 1S. This macro ensures that the correct audio input is selected (just in case someone changed it).

4) VPT (volume punch thru) gets broken when you change the device mode of a device button. For example, if you program a "CABLE" code to the VCR button, you will break VPT.

5) Yes, or manually on the remote.

6) The only downside is that it's inconvenient. If you don't mind the hassle of lining up the pogo-pin adapter each time, don't worry about it. Personally, it's too fiddly for me so I solder!

7) I also have a Toshiba CZ32 and just FYI, I created a totally complete KM file for it, which includes all the service modes and some discrete menu codes. It's in the file section.

I use the CH+ button combined with TV/VCR to get to the correct input and so far I've had 100% success with it. My various "power on" macros all turn on the TV, and the global "power off" macro turns it off, so as long as someone doesn't manually turn it on or off, I don't suffer for the lack of discrete power codes (though I would obviously prefer to have them).

[jfunk]

4) VPT (volume punch thru) gets broken when you change the device mode of a device button. For example, if you program a "CABLE" code to the VCR button, you will break VPT.

THAT definitely explains it. Set up my Cable button to show the PVR screen

6) The only downside is that it's inconvenient. If you don't mind the hassle of lining up the pogo-pin adapter each time, don't worry about it. Personally, it's too fiddly for me so I solder!

Just wanted to make sure I wouldn't damage the remote/contacts or anything using it too much

7) I also have a Toshiba CZ32 and just FYI, I created a totally complete KM file for it, which includes all the service modes and some discrete menu codes. It's in the file section.

I could've SWORN I looked for it and didn't see it, but I'll look again That's one of the only upgrades I'm currently missing

Thanx again for all the help. I can definitely see this getting addicting. Although, I can see my wife getting annoyed that the remote is always in a different configuration or by the computer when she wants to use it

HA!

[The Robman]

I hid it in the TV folder: Toshiba-CZ32V51-TV.txt!

[jfunk]

I hid it in the TV folder: Toshiba-CZ32V51-TV.txt!

Heh. I guess V61 vs V51 doesn't matter? Maybe I was very 'single-minded' in my search

Thanx!

[mr_d_p_gumby]

4) VPT (volume punch thru) gets broken when you change the device mode of a device button. For example, if you program a "CABLE" code to the VCR button, you will break VPT.

THAT definitely explains it. Set up my Cable button to show the PVR screen

With "normal" JP1 remotes, you have two choices, and you pick the one that results in the fewest keymoves:

A) Use the device mode that results in the fewest keymoves, and if this breaks VPT then add the three kemoves for volume & mute function.

B) Use the button's native device mode and accept the required keymoves.

The Kameleon remotes (like the 9960) impose another restriction, as is the case with your Replay on the Cable button. In this case, you must break VPT in order to get the correct set of button screens for the device.

JP1 remotes with LCD displays will usually display the device mode, not the device button, so this may also influence your choice when using one of these remotes.

I use the CH+ button combined with TV/VCR to get to the correct input and so far I've had 100% success with it. My various "power on" macros all turn on the TV, and the global "power off" macro turns it off, so as long as someone doesn't manually turn it on or off, I don't suffer for the lack of discrete power codes (though I would obviously prefer to have them).

I too have a Toshiba TV, and have suffered the same fate. One thing you might need to watch out for if you create any power-on-do-a-bunch-of-stuff macros is that the Toshiba TVs usually have a significant dead-time (unresponsive to IR commands) when first powered up. The fix for this usually involves adding delays to the macro.

Although, I can see my wife getting annoyed that the remote is always in a different configuration or by the computer when she wants to use it

The only known cure for this side of JP1 addiction is to get a second remote!

[The Robman]

I too have a Toshiba TV, and have suffered the same fate. One thing you might need to watch out for if you create any power-on-do-a-bunch-of-stuff macros is that the Toshiba TVs usually have a significant dead-time (unresponsive to IR commands) when first powered up. The fix for this usually involves adding delays to the macro.

True, but you probably won't need to add much delay. If you look at my config file, using the shift-CBL macro as an example, you'll see that I only needed to put 3 steps between the TV's POWER button and the CH+, TV/VCR buttons, and this macro works every time.

I did add a meaningless step ("MUTE") between TV and POWER, this was to give the user a fraction more time to get the remote lined up with the system. I did this because often when my wife would use the remote, she would take too long between pressing the macro button and aiming the remote at the system, so the TV-POWER would often not take.

[mr_d_p_gumby]

I did add a meaningless step ("MUTE") between TV and POWER, this was to give the user a fraction more time to get the remote lined up with the system. I did this because often when my wife would use the remote, she would take too long between pressing the macro button and aiming the remote at the system, so the TV-POWER would often not take.

The problem I have is that my wife waves the remote around like she was conducting an orchestra during the macro sequence. (Let me know if you find a cure for this! ) The best I could do was construct it so it could be pressed a second time and still work.

[The Robman]

I actually do something similar when I use the global "power off" macro, I kind of point the remote at each of the devices as they turn off!

My significant other (or "her that must be obeyed" as we used to say back in the UK) used to point the remote at the system, press the relevant macro button, then drop the remote onto the couch (with the LED still flashing), then wonder why some of the devices didn't power on!

[jfunk]

Yeah, the WAF (wife-approval-factor) is high on my priority list. That's why I'm trying to avoid overly-complex setups.. Adding the audio-input-selection to the device buttons will be ok. Adding macros that require 'patience' will not

She's comfortable with the setup, now, so I'm trying not to do anything too crazy

Thanx again for the help! The 'DSM workaround' you describe worked perfectly! JUST what I wanted.

Hope to finish tweaking a 'base setup' and then jump into the extender docs

THANX!