I am on site at a customer with equipment that was existing when he purchased his house. I am adding a MRF350 among other things. The issues I am having is with the power codes not aliasing properly. Everything is programmed as it should, macros looks proper, but when I run a macro, certain codes do not fire. I have the emitters assigned, not on address 0, and no interference present. When I test the codes from within the device (i.e. go into the Receiver device and test the power on or off commands directly), the codes work fine. When I enter those same codes into the macros, they do not even fire, as evidenced by the emitters not flashing. I rearranged the codes within the macro, and the receiver codes were firing, but now the TV codes were not. Added .1 second delays between commands, removed delays, added multiple power commands, all with no effect. I also checked and the remotes battery is fully charged. Not sure what is going on, anyone have any thoughts?

I haven't opened the software for a month or so, so I forget the exact name here, but are the codes you're putting into those macros set to go out of the remote out as RF?

Just set the emitter IR output to ALL instead of assigning them to their specific device, and everything works fine. Very weird. Everything works when all emitters flash. Everything works from within the device pages and the proper emitters flash for each device. As soon as I enter those commands that work from within the devices into macros, certain commands do not work. I am going to leave it set to ALL since it is working, but would love to know why it is doing this.

Ernie, not sure what you mean. I know of no such way to assign specific codes to IR or RF, only the devices themselves. If there is a way that I never knew of, please let me know. I have never had this issue before though, on any of the URC remotes.

Edit the properties of the commands. I'll be back in a sec after I open the software and look for it.

Here is one that I did over the weekend, hopefully it helps.

insert longer delays on your macros.  i find that .3 seconds between commands works best with the mx980.

Add a .5 ( or .3) sec delay in between each "IR" step in the macro. This is a known bug in CCP or the MRF. Every 980/350 combo I have to do this. I personally don't like using delays unless I have to. Keeps the macros quick. Having to use a delay to fix a "bug" is not what I want to call...."a fix".

What happens without the delay is all the codes get sent to IR out #1 instead of routing properly.

MacrossZero. That is assigning the devices ir outputs, which is what I was referring to above. When I assigned the IR outputs here for their corresponding devices, that is when I have the issue. Set them to ALL, and everything works. However, when I do set the IR outputs to the specific devices, the codes DO work from within those devices, just not from within the macros. If there is a way to assign RF for specific codes, and that supercedes the settings above, perhaps that is the problem. However, I am not aware of such a setting so I have to wait to see what Ernie comes up with.

My bad. I closed my eyes and saw the RTI software. Yup, you can assign or unassign IR and RF in the RF step of programming, not anywhere else.

For some unknown reason, I often set it to IR AND RF... maybe that would help? If nothing else, you could check the IR with the door open, then verify if it's getting RF with the door closed. I'm just vamping now, though.

Is this specific to the 980? I don't work with it all that much to be honest, but work with the 780, 880, and 900 a LOT and have never had an issue. In fact, without any delays all three of those remotes work perfectly everytime.

Only the 980 and 350 combo. At least I haven't run into this with other remotes.

Have you tried a different zone code on the remote and base station.  I am using A in my application.

So... what made it work?

This is a widespread problem with the 980/350 combo. URC does not take it seriously and will not fix it. I have had to work around it about a half dozen times by putting .5 second delays between all commands in the macros. Some have said that if you do not assign the ir ports and send everything out of ask the emitters, it works as well but I always route my ir so I never tested that theory. There is a thread on the urc forum about it that is quite long.