Happy Monday to all. I'm trying to help out our Crestron programmer. He is having a extremely difficult time getting a CP2 processor to control the U-verse, but I can control it w/ URC remotes/ codes just fine. Us URC people are just pampered, aren't we?

He has learned OEM codes into DEAL (once learned, they appear as multicodes if this helps) and no matter what he does, they just aren't reliable...they miss, then you get a double press and so on. He has tried different IR emitters, positioned in different places on the box, he has compared IR data from DEAL and observed varying frequencies between buttons on the remote, but doesn't know enough about raw IR data to conclude much else, other than we did notice that I can dump codes from URC's database into URC remotes all day and they control ALL of the boxes prefectly. When he learns these same codes into DEAL, the data is almost identical to codes as learned from the OEM. Still, they will not work with any consistency.

Has he tried adjusting the number of repeats in Deal?

Yes.

I think there is a Uverse file posted on the Yahoo Crestron group. Worth a try.

He said he tried all three files there. What could be going on where he isn't even able to successfully use learned codes from OEM remote?

Has he successfully learned any codes for any product before?

When you say "our programmer" what does it mean? Is it an installer with system builder? Sales guy who is teaching himself crestron programming?

My response may be worthless to a seasoned programmer but might be valuable to the new guy.

When hes learning commands into deal he should have the remote on the table in front of the learner. Do not try and hold it in your hand. Quick taps on the buttons are better than full presses. Try and keep the timing of your quick taps the same. FYI there is a test feature in DEAL. He can move a uverse box right to his desk and test each command as he learns them.

Next thing, this is for system builder. Make sure that when he drags a command in that he changes it to 0.1s for the length of time the command needs to be sent. It defaults to "while event is active" which will typically give you problems like the ones you are describing because it sends out a continuous pulse of the command. In one case my discrete ON was turning a TV off because sending on twice looked like an OFF command to an LG. I am sure there are similar settings in simpl but i cant comment.

He has been using SIMPL windows for years, rarely any errors.

Yes he has successfully learned for hundreds of other products.


He has tried all of that. He is a very seasoned programmer, but of course like anyone, he can make mental errors, but I'm sure he has checked and double-checked things like this.

At this point, I would be satisfied just to hear someone say that they have successfully used Crestron to control U-verse.

I am using a u-verse box and crestron. Learning the remote did however cause me some issues, but I got codes from the rti database (copy and paste the hex into deal). I can post my .ir file for you if you need it. I believe somebody has a"fixed" pronto file on here somewhere you could probably use. I think I may have mixed and matched a few sources before I got a good driver.