I created my main source selection panel under devices, this panel has a button for tv on, dvd, vcr, etc. All of the commands for these buttons are stored in my macro group section under macros and i just alias those buttons. The properties for all of these macro groups i enabled RF. My question is since i enabled RF already in the Macro does it matter if the RF is enabled for the home panel i created in the devices section? Sorry if this question has already been asked, but i did not see anything that adressed this exact question.

This message was edited by SEEKONE on 06/04/03 11:26.

yes

for RF to work it has to be set in home

Im sorry, maybe i said that wrong. It's not the home panel i was refering to it was just a panel i created under devices that i called home.

SEEKONE,

In order for RF to work, you need the SYSTEM Properties RF tab set to RF (the properties under home), and Device Properties WHERE THE ACTUAL IR CODES are located set to RF. Note, I mean the actual codes, aliases don't count. You also need the RF extender set to the same Channel and ID as is set in System and Device Properties.

As far as your macro is concerned, the answer is it depends. How is your macro constructed? If you built it using aliases (in the software) then just enabling RF in the macros device properties won't cut it. If you constructed the macro by learning the codes directly into the macro, then you'll be just fine.

I'm curious as to why you ask. Does the setup not work? One thing for certain is that the setting of the device properties for YOUR home panel will no effect on the transmission method of your macros.

Jim L

bomberjim,

The reason I ask this is because I was having problems with all of my equipment responding with the RF setting. So i have been reading through some of these threads and found some different ways of maybe getting this thing to work. I do not have all the equipment here and when i go to the site i just wanted to be sure that this was not an issue. I learned most of these commands directly in the devices and then copy and pasted them in my macros so i could then alias these commands back in to all my devices that used these same commands. I know thats kind of screwed up but thats how i have it. Is this going to cause me problems?

SEEKONE,

I think we have a semantics problem. Using the software, you can't copy and paste multiple codes into a single button in order to construct a macro. All you can do is alias to other buttons to build a macro. And yes, based on your description, I think you'll have problems.

Let's say you have a device labled DVD and you set device properties to IR. In another device labled macros you set device properties to RF. In the macros device you create a macro by aliasing to the buttons in the DVD device. All commands will still be sent in IR, because it's where the source (actual) codes are located, and it's device properties setting, that determines the transmission method. Since device properties of the source codes is IR (the DVD device), the transmission is in IR.

There are two probable "best" methods for using the extender and RF. In EITHER method only learn/copy paste the codes ONCE. Anyplace else you need them, just use aliases.

1) If you will ALWAYS control say a DVD device via either RF or IR: learn the DVD codes only to this device and set device properties accordingly. Everywhere else in your ccf, just alias to these codes.

2) You want to have a choice for the transmission method. Create a device called IR Codes, and set device properties to IR. Create simple buttons and learn/copy & paste every single code onto these buttons. Make another device and call it RF Codes. Copy all the IR Codes panels into this device. Elsewhere in your ccf, if you want transmission in IR, alias to the button in IR Codes. If you want transmission in RF, aliase to the button in RF codes. Again only learn/copy and paste codes one time, everywhere else, use alias.

The system seems overly complicated, but was designed that way (I assume) to enable a macro to have mixed transmission methods. Some codes IR and some RF in the same macro.

Hope this helps,
Jim L

bomberjim,

So let me see if I got tis right. If I want to mix IR and RF commands in the same device i must create two seperate panels, one for those codes i want to send IR and another for those to be sent RF and just alias those buttons? If this is the case what is the point of using the section labeled macros? This is where Im confused, actully in my set up I want all of my equipment to respond RF. I have enabled the RF in my macros aswell as in my devices and in my system properties, do you think this will work?

Not quite. Now I'm only talking LEARNED CODES here, not aliases. You can't set a PANEL to be RF or IR, only a device. So if you set this device to RF, both panels will be sent RF. Again, this is true ONLY of the actual codes in that device. If you have an alias on one of these panels, transmission method will be the setting of the DEVICE that you aliased too.


Ok, if you want EVERYTHING to go RF (no IR will be sent at all), it's simple. Set system properties (under home) to RF, and then set EVERY single device and macro group in the ccf to RF as well. Sounds like this is what you've done, so it will work. Make sure the Channel and Extender ID's agree with what's set on the Extender itself.

What's the purpose of the Macro side? It was designed to allow you to build a macro on the remote without using the software. Originally, the remote was released without a software package - that came later. With the software, any button anywhere can be a macro. Without the software they can only be constucted on the Macro side. If you're using the software, essentially the Macro side has no purpose. There are some relatively minor differences (which I won't go into), but essentially it serves little purpose.

Jim L

Hi SEEKONE forget about the labels called devices and Macros. This are called that way because of archaic reasons that make no difference when you use PE. When we talk about macros here we mean one button that sends multiple commands.

so for RF to work
1) home (system properties need to be set to RF
2) any button that has a learnt/pasted or UDB code needs to be in a group (device or macro group) that is set to RF
3) if you want to build a button that is a macro, then the best way is to alias other buttons in your CCF. The commands in the macro will be sent in the format (IR/RF) that the command you are aliasing

Thank you both, I have a much better understanding now. Im going to set things up as you explained and later today i will be testing it out.

Thanx again!
SEEKONE