I cannot get IR routing to work

I bring up the properties/IR routing screen by right clicking on a button with a command on the T2+ device and I can check/uncheck each of the 6 ports on the RP-6: the help screen says: check this box to send the commands on this button out of IR out 1 on control system

So I check/uncheck buttons so commands are sent only out of assignable ports of the RP-6

Trouble is as soon as I exit the menu, it adds check marks back to all 6 boxes no matter what I do

V2.0

Mark, I actually had this same dilemma earlier this week. With experimentation and calling RTI, I hopefully have an answer.

Open up a new system and add a RP-6 and a T2+. The next step is important, IR commands need to be on each button already in each device (basically your remote needs all the commands pasted to buttons already).!!! Also remember that tools on top bar only apply to whatever device is active. My example below is using port 6 and high out IR ports.

Click on Red Select Tool in bottom left of toolbar and then start at top of remote just below home icon and select all buttons below it to bottom of remote, while they are red, hover over any button and right click, select properties and the box will be titled "mulitiple buttons " properties. This highlighting and selecting applies to the LCD screen also but has to be done on each subpage and it does not apply to macros.

Unclick any ports and if you get to only one box checked and high output it will ask if you want this code sent "always" you need to check yes or else use a power sensor. If you only check high output , the "always" box will not come up. This is a great port to use, and it does not need a mini jack plug end to use it.

Other items to note: If you add a code to a page that has been already been programmed to route to 6 and high out (example chan down) . The new code will not have the original properties to route to 6 and high out, the chan down command will have all boxes checked. You will then need to change that code individually to route to 6 and high out again. Or you can select all buttons again and change back to port 6 and high out, this is tricky because the checkmarks are greyed out but still there, you need to make sure they are gone completely!! or it will not work.

To answer your original question, since I am talking about making whole device pages go to a certain port or ports, the only way that I could tell was to delete the command on the button and make a macro of it with the command that was originally there. Then right click the command in the macro and steer it to the correct port. This way you can visually see a black M on that button to let you know something is different about it.

Other things that need refining in the software 2.0 is to have a page forced to a certain port or ports by a global command instead of the clusterf*** way that it has to be done now, especially if you change commands on a page frequently. I understand that the software is flexible to do anything but sometimes you want a whole device to route only to one port and there needs to be an easier way to do this. Also macros are a problem because each line of code has to be routed manually by right clicking each command to get it to the right port. The method above to select all and change the routing characteristics is ok but it does not apply to buttons that have macros.

Hopefully this helps...Gary

Gary

Much appreciated: I was beginning to think I was the only one seeing software issues

Hi,

I originally set up my T2 to do IR routing to the one device only. Now that I have the T2+ and it imported it correctly so I'm not seeing the problem you are, however, I always wondered why not just send to all 6 ports as long as each port has unique devices on them I can't see that being a problem. I'm guessing it would be a problem if port 1 and 4 had the same device. Is this logic correct? Is there some other reason you wouldn't want to send to all 6?

Thanks,
David

the feature is useful to me: 2 examples:

-Gefen DVI switches had numerous conflicts where they would respond to other remote commands, particularly Tivo commands: putting a covered IR emitter on the switch and sending it codes through an assignable port was a work around for this

-More than one of the same stb: lets assume you have two DSS boxes and want to use common IR codes; you could set them up on assignable ports

All high end remotes have this feature and it comes in very handy as a workaround when a problem/conflict is discovered.

I do agree in the majority of cases you may be able to send the same command to all 7 ports and not have a problem

Thanks for the informative reply.