Man these things are touchy. Is there a set of codes that are 100% good for these RNG150N boxes? I couldn't even get codes I had learned in from another job that DID work to work on one I was working on today.

Maybe with all the dumb things they're doing with boxes (cable companies in general) they don't bother to keep the IR codes the same.

Buy a Pronto. That way you can learn the codes quickly and you can easily copy and paste them into the RTI software.

What's odd is I was using codes I had learned into a C4 system that I know for a fact worked with the exact same model X1 box. I was trying to update an old Sonance K2 keypad (which is RTI software) and I couldn't even paste some of the codes into the IR library. A few of them kicked out some error about "too many timing signals" which I had never seen before in all the years we did RTI.

I think that some of the X1 boxes are sensitive to the rate that codes are delivered.

I had a recent experience with an Arris X1 box after converting an iPad to iOS 8. iOS 8 is a little faster at IP communication and my channel selection codes were arriving too fast. I also ran into some out of order command execution issues, but this is probably not the X1's fault.

If you are having issues when sending multiple commands in a macro, add some delay between commands.

On the Arris X1 I noticed that I should delay commands long enough for a channel change digit to be acknowledged on screen before sending the next digit. I can imagine that the optimum delay would also be dependent on the mount of partial string search data that is displayed. Sending a digit while the search result is being populated is probably a bad idea. (but I have no proof of this)

Oh, also, this was a cable box only used for music, so there was no TV hooked to it and I could not see what the box was doing. No channel display on the front either. After an hour I cut my losses and told them it wasn't worth their time (or money) for me to be here guessing at what it's doing, especially with how finicky those boxes are.

I've noticed that the main box is not touchy at all. It is the slave units that are problematic.

I've used IR, RF ... it doesn't matter. No consistent response.

This is EXACTLY why I spent $115 for a TV and $50 for a case for it. It shows me default 1080i from new BD Players on old systems that have 720P only TVs; I can see VGA, composite, component... and the DW guys were jazzed to see someone on top of a ladder adjusting one of their cameras using a 15" monitor!

There is still a TV around $115 at Best Buy and I'm sure you can find them on line, too. Think of it as being like a butt set: you feed it signals that your brain cannot directly understand and it translates them to something you can work with.

I can not see dragging around a 15" TV all the time.
About three years ago I bought a Field Monitor. They are more or less
sold as camera monitors and a quick search and I came up with
this one.
[Link: lcdracks.com]

Not the one I have, but you get the idea.
Mine came with two batteries and a power supply.
Has composite, component and HDMI inputs.
Thing is awesome and use it way more than I thought.

I would love to carry this thing around, we've been talking about getting one:

[Link: atlona.com]

I felt the same way about a Sawzall for more than a dozen years. I now "drag one around" (like the monitor, most of the time it's just in its container in the van) and when I need exactly that to solve a problem, it's there.

How much did you pay for the Field Monitor you bought?


I can see how you'd be willing to get out something small like this way more than I get out my 15" TV, but I don't run into the need very often.

24/7,

Before getting too excited, reboot the boxes. I was wrestling with a progressively worsening audio dropout issue yesterday with the customer claiming that his brand new TV's were defective. We would have a dropout about once a minute. The dropouts stopped, at least for a while, after I rebooted one of the boxes. The drops were not part of the broadcast because I could play a recorded program, rewind after a drop, and the rewind play would not drop at that spot. The XFINITY rep suggested that I reboot the boxes once or twice a month -- and was perfectly happy with this sort of solution and went on to brag how much they are improving the boxes, sometimes every night, and that the software update reboots the box. I guess his message was "reboot often".

Maybe a timer switch would be an answer to our problems.

I hate those x1 boxes. Had a similar experience with c4 trying to use multiple x1 drivers I had used before and just couldnt get it to respond right. I managed to weasel my way out of it. Used those same drivers on other x1's and they worked OK

I believe URC has a couple different codesets for those depending if it's straight IR(195) or through an MRF(202)

Just picked one up a couple of weeks ago - it's fantastic Jim. I am planning on grabbing another one and dedicating it to my test rack.

Just went through the same X1 client box (RNG150N) nonsense. Tried codes that worked in a previous Control4 job, no worko. Tried 4 different Control4 IR drivers (older, newer, custom) -- nothing. I even tried the direct connect flasher input on the back of the box with a mono cord. Nope.

It seems like it's an IR receiver issue. When moving the flasher around the front I was able to do a channel change when I covered up the flasher with my hand in certain spots, but was unable to get this to consistently work.

In reading other messages here, it seems that the RNG150N is made by two companies: Arris and Pace. Apparently, the Pace boxes are the ones with the issues.