I've been experimenting with using pre-programmed discrete power codes rather than learned discrete power codes and have run into a problem. I'm trying to utilize the pre-programmed codes because of the MX-3000's current inability to accept hex codes directly into it's editor (hopefully this will be fixed in the near future). The learned hex codes, imported from a pronto ccf file, all work flawlessly.

I've found discrete power codes in the database for my TV, receiver, DVD player and VCR (my HD Tivos don't have discrete power codes). What's strange is that while they all work correctly when initiated as individual codes the ones for the DVD player and VCR don't work at all when included in a macro. I've even simply added a .10 second delay to the individual codes thereby changing them into macros and then they don't work. Does anyone have any idea what's going on here?

Bob

bump

IR codes in a macro are problematic especially if you are using RF. If you are executing the IR code in the macro via an alias, try replacing the alias by copying the IR code directly into the macro IR Data field. And if using RF, make sure your RF Control is set up properly for the device.

You don't quite get what I did. I have codes for the two devices (DVD and VCR) which are working fine via RF as simple non-macro on and off buttons. I included them in macros via alias' and they no longer worked. As a test I also simply added a .10 delay to each of the actual codes (not the macros) and this immediately stopped them from working so in this case no alias is involved. Any other ideas?

Bob

I don't know for sure regarding an MX-3000, but with other brands of universal the difference between a single signal and that signal plus .10 delay is duration of the signal itself.

With just the signal assigned to a button, the transmitted duration of the signal depends on the duration of the button press used to send it.

With a signal plus a .10 delay assigned to a button, the transmitted duration of the signal does not depend on the duration of the button press used to send it.

I don't know enough about the MX-3000 to know what duration will be used under those conditions nor what you can do to take control of that detail.

You may be able to verify that you have a duration problem by using the working button (without the .10 delay) in a very short press. It should be possible to press and release fast enough to match the fraction of a second that a macro would use. We expect that to fail to operate the device (because the macro fails).


Do those work even with the .10 delay attached?

If so then it should be possible to contruct Pronto Hex for the discrete codes that will work equally well. Then ProntoEdit or IrPanels is needed to get those codes into a ccf so the universal browser can access them.

Do you have a url for the ccf file you used? And which device/panel within that ccf had the working codes? Once I get a look at those details I can give you better advice on how to get the discrete codes working.