I think this has been discussed before, but I'm wondering when a fix will be available?


1. Drag codes from Universal Browser (Pronto .ccf) into the MX3000 software onto a button and the codes work fine when downloaded

2. Drag the same codes from the same Universal Browser (Pronto .ccf) into the MX850 software and the codes do NOT work when downloaded

3. LEARN the same codes from that MX3000 into the MX850 and the codes work FINE
when downloaded


Obviously the codes are good, and obviously the problem is the MX850 software and importing directly from Universal Browser...does anybody know if this is being fixed or looked at, or know an easier and more efficient workaround that LEARNING a million codes?

RobZ

Don't know what to tell you, Rob. I haven't had that problem with the 850 editor with any of the recent updates.

Mike
www.SurfRemoteControl.com

The codes are ProntoPro codes for controlling Crestron. I have had issues "learning" these codes to an MX850 before, but now they learn fine (at least from an MX3000) but those same codes don't work when dragged in from Universal Browser.

Crestron reports a faint RF signal from the MX850 when it's firing these codes, but does not respond to them. Those same codes when learned are recieved fine by Crestron (reports a strong RF signal)

I agree it's odd, but it's definitely the case. Any other codes so far that I've dragged in via Universal Remote have worked fine.

PS: although there is an "infrared" component that can be learned from remote to remote, these codes are NEVER utilized by Crestron as IR flashes. Crestron recieves RF from it's own remotes...the Pronto codes duplicate the data that would normally be broadcast via RF...one would think that learning them would only serve to corrupt the code further, not clean it up

I guess what I mean is: there will probably never be a "fix" since this isn't an issue with actual IR codes, just this special case using Crestron codes. If all the other Universal Browser issues are fixed, it's not fair for me to assume that fix for MY issue is in the future LOL.

I don't recall the thread, and I haven't retested with a more recent 850 editor. But in a thread a while back, someone reported a very similar problem and I investigated and determined that the universal browser was systematically distorting certain signals when importing from Pronto Hex. I managed to generate Pronto Hex with MakeHex that precompensated for the distortion, so the imported signal ended up correct.

I don't have time now to search for details in that thread, but you might do so.

Thanks John, at least it gives me a direction to go in.