Has anyone interfaced the URC MX-3000 and a Niles Intellicontrol MSU? I am going to give it a try and was just wondering if anyone had any advice. I want to take advantage of the Niles syncing properties but hate the big hard button remote. Any input would be appreciated. Thanks.

We have done dozens of Intellicontrols with Pronto remotes and here is what I recommend:
Get the MSU programming/macros up and running 100% before starting the touch-screen. This can save you alot of time later.
If you are usiing the MX in RF mode, test it first by switching the remote to RF and see if it will talk to the MSU without the RF station. In the case of the pronto remotes, the RFX-6000 worked worse than just letting the remote talk to the MSU.
If you are using IR into the MSU from the RF extender or from an IR repeater, remember that the MSU will pass all IR from the IR in port to all IR outputs and is not routable. When we do a remote this way, we use the MSU for macros/management only and have all of the channel codes, number codes etc, in the touchscreen.
There are a few bad commands on the .ccf file from niles and in Niles library. These include some of the number commands under master key four and a few others. If you are using the MSU for all of the programming, Test the MSU first from the intellifile software, then as you put each ir code into the 3000, test it as well. You will find a few codes that do not work and have to move the commands in the intellifile software. We find the best way around this is to keep the MSU as simple as possible and keep as much programming as possible in the touch-screen.
Back-up your niles files and leave a copy on-site(in the back of the cabinet is a good place, or with the homeowner, but that is another topic). Niles software will allow someone to upoad a file from a MSU, but when you do, every command is shown as "command" with no name. If you have more than one person in your company who may work on this systm in the future, you will save a lot of grief by making sure that there is a copy of the original file available on-site.
Other than those things, it is a pretty simple system to set-up.
Let me know if you have any other questions and I will be be glad to help.

Jason

Thanks Jason. We will be using the RF but I am waiting on our MX demo to try it. I was thinking of the MSU as macros/management only so it was nice to see I was on the right track. Thanks again.

We have done exactly that with the MX-3000. Same deal: put the source macros and "system off" on the IntelliControl MSU and the rest directly on the MX-3000. Works great.

You just use one IR output from the MX-250 base station to the IntelliControl MSU.

George P.

I assume then that the MX-3000 will not communicate directly with the MSU, that is why the MX base station is required. Thanks George, I am looking forward to setting this up, it should offer more simplicity to the end user.

how could two remotes simplify a system???

I'm with you beerock, it does seem a "little convoluted" for a remote control system.
You must do "a+b+c, then go back to "b" if "c" doesn't work, or do "a" if "b" doesn't work??

I understand what your trying to do, I have done several of these exact systems, however many years ago. Why don't you use a system like an RTI with a bulletproof RF system and all those other features you are trying to accomplish? They must be giving away MX3000's and Niles Intellicontrol MSU's.

The biggest advantages to this system is managing turn-on status, warm-up delays, long macros, and other odd variables.
Take a simple system with a toggle power cable box, a Samsung DLP with a 26 second initial warm-up delay, and DVD player with a "Play..Delay...Delay..Power Toggle" sequence for discrete power off.
-With the MSU in place and programmed, you get sync capability which makes sure the cable box is always on when you need it to be.
-With the MSU in place, the system waits for the TV to warm-up when it is first turned on. If the TV is already on and you switch a source, there is no delay. This saves you from having an "ALL ON" button in the system. All the customer does is push "Cable" and everything comes on and goes to the right inputs. The delay is only added on initial start up. This can save a lot of time in programming by not having multiple power command sequences depending on where you are in the remote.
-With the MSU in place, there are no missed commands in macros. I know with RF, you should never miss one, but it does happen. All the MX does is send a .5 second command to the MSU and te MSU takes care of everything else.
-With the MSU in place, commands are only sent when needed. If you do not need the Cable box, DSS, CD, VCR, etc on to watch DVD, they do not come on. This speeds up your macros quite a bit and can make equipment last longer.
-With the MSU in place, you can set a volume reset even if your equipment does not have it discretely.
MSRP of both units is @ $1750.00 + programming. If you are doing a full blown control system, then there are better options, but this is a good middle of the road stand alone solution that is reliable. The entry level of course would be a cheaper remote ie TSU-3000/MSU for @ $1000.00.

Jason

Jason,

I completely agree with you, and sell lots of IC's, but in gwilly's defense, the RTI is supposed to have the sync and macro capabilities of the Niles, and we're going to look into using them... just a friendly FYI... Might want to check them out too, just to see...

Elan also makes a similiar solution, but the Niles is still easier to use at this point. The Elan system has the advantage of having rs-232 however and we are starting to use them as well.

Jason