how to program a rti apex button with out driviers

We will add an Xfinity X1 cable box to the Family Room. You may add a device from the driver, Infrared or RS-232 tab. Next, change the name of the default “imported devices” to a room name, in this case the family room.Ĭlick the “add workspace” button on in the workspace area and add a device to the room or global area, depending on the functionality of your system file. You will lose all your functionality in the template due to the lack of button tagging, but the graphics will port over without any compromise.Ĭlick the “add workspace” icon in the upper left of the workspace and add a control processor to the global area in your system file. Apex will create a room named “imported devices” with a single page group of all your ID9.x pages. Next, toggle the file type to All Files (*.*) and click on your ID9.x file to open it in Apex.Īs you can see, your control processor will be missing from the global area. Launch Apex, navigate to the directory where your ID9.x file is located, and select File/Open from the top left toolbar. Apex will group all your pages in a single room called “imported devices” and again, will not retain your master control processor in the global area. For this reason, you will not retain your control processor, page links or any functionality as it relates to driver, IR or any other command structure.

It is important to know that Apex follows a room structure and tagging methodology that is not a standard in ID9.x. Converting a custom interface project originally programmed in Integration Designer 9.x can be converted to an Apex file and used for future projects, taking full advantage of the tags utilized in Apex. Many dealers have devoted time to creating and refining graphical interfaces over the years using RTI’s Integration Designer software. Solution home RTI FAQ Converting Custom UI from ID9 to Apex

How to program a rti apex button with out driviers