I’ve looked a few different versions of Daniels TSU 6000 ccf and one area that I can’t seem to understand is the power section. It’s set up in the Macro section in his case but not in other versions.

Each frame in a ccf will have that little power plug graphic. These seem to alias the power panel/device. This is where everything gets a little hazy for me.

The power panel will be laid out with a center descriptor button like DVD then on either side it will have the power on and off. The center button is learned in any that I’ve looked at, and in one case the on and off power has some strange code in it like [c] RC5 18 46 or RC5x

How do these work? Can you cycle on and off codes through these "power" panels?
I've always had the power on and off on the panel that I'm using.

And why put it in the Macro section?

Thanks

F

How about emailing Daniel directly? You might change the title of this thread to "Question for Daniel Tonks about 6000 config" to get him to respond.

Lyndel

Actually no, the power plug icon on each frame is... the regular power command for that device.

If you go Home -> Other -> Device Power you get the page you're talking about, but it's mainly there to store codes (regular power and discrete on/off where available).

Thanks for the replies folks.

I understand that the power panel is simply a place to store the power codes. But say for example you’re on the DVD device and you tap the power icon. Will it turn the DVD player On or Off ? It other words if you have discrete power codes can you use either one or do you have to access the power panel directly. Or does each power button only perform On or Off ?

On some of my early ccf designs I had the same basic idea. Only difference was that when you touched a power icon it would be a jump to the power panel. Taping the On or Off icon for the device would jump you back to that or a different device. For example if I turn off the DVD player my jump would be to my DSS panel. I would also alias that panel for my system on and system off main.

This is the part of the ccf that you built and other have copied that I don’t quite get. Each On or Off button has a code assigned to. That makes sense, but why does each device descriptor also have a learned code?

I never even considered it as a Macro

Sorry for all the questions Daniel it’s just that I’m interested in the way you set it up but need to understand it’s structure and how it’s layout in the Macro section makes it all work.

Thanks
F

My system designs use discrete codes wherever possible. Most devices are fully automatic and have macros that will power them on when you select them. A couple devices do *not* have discrete codes and I have to turn them on manually. The power button on *all* pages is a normal power toggle for manual devices and even for normally discrete devices "just in case".

I came to understand POWER panels, and decided never to use them.

I also use discrete codes wherever possible, but I program for clients and I have a different approach.

I create a ccf for each product with just dumb black and white buttons with no graphics, and then label each button and teach a command to each button. That panel is hidden in the finished remote. Then I add panels (or steal them) with the graphics that I want to use and alias each button of these panels to the master panel. That way, I have complete component files that I can merge with other component files to build a ccf.

The home page then has icons or buttons where, for instance, "DVD" would turn on the TV, switch its input, turn on the A/V amp, switch its input, turn on the DVD player, hit PLAY, then jump the remote to the main DVD panel.

There is never any need for a separate power panel because a device's power commands are already in a panel of the device. As a result, I never have anything on the macro side except for my phone number under a HELP sign, and if I decide to lift one component out of that ccf later, I don't have to worry about losing commands aliased from other devices or from the macro side.

I guess it was the toggle idea that I was interested in Daniel.

I’d like to be able to touch power and have the DVD player turn on and then touch the same power graphic again and have the player turn off. Just like a regular factory remote. I have discrete codes for my DVD, VCR, AVR, and TV.

But it sounds like the toggle idea isn’t a possibility. I’m not crazy about doing a page jump to the power panel and selecting the on or off button directly.

Ernie,
I've got mine set up in much the same way on the home panel. haveing discrete power codes makes this very easy to do.

I think I understand your design Ernie, So you have on and off power buttons that alias the hidden power panel? I had my original desin on my 2000 laid out like that.

Are yours on the Macro side as well?

I need to get some teaching on the Macro thing. I had thought about having a window open after touching the power plug on a panel that asked if you wanted to turn the power on or off? Then the reply would determine the next step in the Macro

Frank

There is no power panel at all. Instead, each component has a hidden panel (or more, for A/V receivers) with all of the commands on them, and I alias to these panels any time the codes are needed, whether it is the normal PLAY from the DVD transport page, or it is POWER ON as part of a home page macro.



My remotes have no macro side. I see no reason to have the client have to go to another place for any macro. HOME has all the macros. The component select macros (DVD, CD, etc) contain all the commands to turn the system on and switch things properly, and one grand OFF macro.

Other than that, what macros are needed? (nobody records anything, so stop thinking that)


If your power commands are not all toggles, this can help. It is called "activity-based," and you can find some examples in the files section. I usually only have one or two components that do not have discrete power, and I just put a POWER button on the main page, then tell (with words spoken out loud) the user to turn the thing on if it is off. No Macro page, no Power page to go to...it's all right there.