I have a situation that is stumping me. I have a number of systems with this same or similar configuration and all but one work perfectly fine.

I have RTI remotes utilizing Crestron 433 trigger codes into a Crestron Pro3 processor.

The codes when issued will trigger 2-6 times. I even designed a skip mitigation module that limits the code issue duration which completely solved the issue for a while and then it returned. It uses the same code set that works perfectly in other jobs.

The only observation I have is that this system uses a NON-DVR main box (XG2V2-P) and not a DVR box like all of the other jobs like it.

Anyone dealt with something similar?

In general I find the Xfinity boxes are sensitive to the code spacing. I create favorite channel macros and I need to adjust the timing between digits. I try to trim this to a minimum in order to create a remote that seems to execute commands swiftly, but this will burn me sometimes after Xfinity updates their boxes and changes the timing. In my case this results in skipped digits.

The boxes are also sensitive to stray IR. Check your RTI program to make sure that the handheld remote is not also issuing cable box IR commands that will hit the cable box along with the processor issued commands. This could cause the multiple digit response.

In the worst case, you may need to trim the spacing between repeats. This will be messy because you'll need to edit the codes.

If you have the RTI learner, it is nearly painless to start with an existing code set and generate a new code set by replacing all the codes using the native remote.

I am way past that...
No IR being issued by the remote... 433 Crestron RF trigger codes only. I am aware of the pitfalls of X1. The major point here being that this Crestron IR module works flawlessly in other systems. Only this one with a Non-DVR has the multiple skips.

The timing on this box is likely different. As a reality check use a phone or pad camera to display the IR. Is the digit count correct?

Is that a Moto box?

Or does anyone know if the same codes for Fios work on xFinity?

I have a clean IR driver for Fios that fixed the timing issues.

What happens when you issue the IR command from debugger? Do you get the same response with the box as you do with the remote? Have you also tried from your learner using device learner? Again does the cable box respond the same as when using the remote?

Have you tried swapping in another Crestron processor temporarily? Could be hardware related issue.

Debugger... same.
Learner... X1 codes never learn correctly.
Remote... works fine.

Possible but not likely.

will you share so I can test?

It's kinda nasty to say you have it but not suggest you might help. I'm sure that wasn't your intention, but???

I just tried to submit it to the Files Section but I have no idea how long that will take to go through. You have another way you want me to get it to you?





But what? I asked two questions and said if the answer was Yes to either I had a file that could be tried.

I just saw the answer to the question and am providing the file.

X1 is brutal. What works on one box might not work on the next. Problem being is they have 4 manufactures for the same box so things get wonky. On top of that sometimes box updates botch the commands do you get these skips. Contorl4 released a driver this year that seems to fix it.

I know your not using IR but I figured it was worth mentioning.

The ONLY box that I have had consistent luck with is the rack mount box. That one seems to be the most solid and consistent!

Here is the link: [Link: files.remotecentral.com]

I've solved a similar problem, but it's been years so I don't remember the exact behavior.

I turned each command into a two step macro. The macro consisted of the command I wanted followed by a command from a brand of equipment not used in the system. It seemed that this made the component I was trying to control recognize that the wanted command had finished, so the equipment stopped responding to the wanted command.