I have 4 MX-880s and a msc-400. About every 1.5 months, weird things start happening. First, it may be long delay times in getting devices connected to the MSC-400 to respond to the remotes. Example, go to change the channel on the cable box and there is a 5 second delay before it does anything vs. almost instant on a normal day. Very quickly the problem degrades into the MSC-400 controlling nothing. Strangely enough, I can see the emitters firing when I hit the buttons on the remote, but none of the components respond. Usually, I just unplug it for a minute and then it is okay. However this weekend, that didn't work. I re-loaded the programming and then it was fine. I'm just wondering with all you professionals out there whether or not this Is this typical or do I have a bad box?

Actually, it sounds like you've got RF issues. All the intermittent problems you've described can be caused by RF interference. You may want to re-locate the antenna. Also, next time this happens just disconnect the antenna for a minute and then test again--if the problem goes away you have RF problems.

Jeff

I have seen this happen as well and unplugging the RFX-250 is all it took. I did some RF troubleshooting and relocated the antenna and all was well.

are you running more then 1 antenna? if so you cannot use the standard plug for the RFX-250 at the same time as you are using the phoenix connector, i believe it greatly shortens the RF signal when both connections are used at the same time, make sure all antennas are plugged in from the phoenix, i think it supports enough power for 3 antennas.

I never considered RF interference. Although, why would unplugging it or reloading the software fix that problem? I only have one antenna, but I will check next time it happens.

There is a second possibiliy...Are you going between RS-232 and Ir devices? If so, I have found the MSC-400 can get "confused" if multiple RS-232 commands are fired from a macro too quickly before or after Ir commands.

Most of the time I see this as a problem with the slave MSC-400 hanging-up and have to reboot the slave unit. The more permanent fix was to add some delay time between the commands in the macros (0.1 seconds for instance).

I should point out that I have never had one of the units hang with just "simple" commands (Ch+ / Ch-) going out the MSC-400, so I don't think this fits your first problem (the long delay times), but might fit the description of the second problem.

EDIT:
Let me add a few more things to check (maybe this will help someone setup master/slave MSC-400s in the future, as well):

1) For the newer remotes (I know MX-6000, MX-5000 & MX-980 are "newer"), make sure the msc-400 has a RF ID >= 10 (Hex) - I use 11x. If you don't do this you will be unable to see the higher ports (above 6) when programming which port to use on the remotes (but you can still see them when programming the MSC-400s).

2) For increased reliability, make sure the Master MSC-400 and Slave MSC-400 don't have the same RF ID. I am using RF ID=12x for the slave.

The interesting thing is that if you use the same RF ID on both, the system will work for simple commands. The more interaction between the two MSC-400s there are, the less chance they will work completely. Many times having the slave with the same RF ID as the master will cause the slave to temporarily hang-up. The funny thing is that by sending the slave a few simple commands, it seems to recover. For the system to work properly different RF IDs must be used with the Master and with the Slave units. This is set under CCP in "Program" --> "Configure Home" (then select either Master or Slave MSC-400 from the tree).

3) Finally, I replaced the URC supplied 3.5mm stereo plug for RF between Master and Slave with a 1-foot long cable with 3.5mm stereo plugs. Connect Master MSC-400 RF out to Slave RF in. That seems to work properly so far. You could use Cat-6 instead using the supplied three-screw terminal connectors. In this case wire Master RF in to Slave RF in and don't wire the +5V to the slave. In any case use either the 3.5mm cable *or* the supplied connectors but not both.

Hope that helps, along with adding the proper delays. Sorry about the earlier incomplete answer.

As a matter of fact, I have a HDMI matrix that I control via RS-232, but the receivers and sources are all controlled via IR. I'll have to watch out for that. It would be really nice if URC had a reboot command I could send to save me the trouble of having to go down into the basement to the A/V closet when I have issues.

Added a few more items in the above apend from 3/11/10.

Old thread, I know. But hopefully someone can answer this question about the MSC-400 operation: when a delay is inserted into a macro, does the MSC "stop" executing all other portions of the macro while it waits for the delay to finish?

if you are talking about macros built within the MSC400, yes, it waits for that delay to finish before sending the rest of the macro.

if you are talking about the macros built on the remote, then it will only respond to the smart trigger. The msc400 doesn't know that you have added any delays within the macro on the remote, so it will just run its own macro no matter what the remote is doing.