All my macros work fine when tested through the PC to the MSC400. All components work fine with the MX3000. When I drag Macros from MSC400 to the macro window of the MX3000 only part of the components work. I've reprogammed the macros in MSC and Deleted contents in MX3000 and reinstalled macros for hours and am not getting anywhere. This is not the first time I've set one of these up but this one is kicking my rear end. HELP!!

In your MX-3000 editor / RF Setup have you verified that you have selected the same IR Receiver and IR Output Lines as in your MSC-400?

Yes Iv'e double checked

Hi Wade,

If I understand correctly, the trigger command that you drag to the MX-3000 starts the macro but not all of the commands are executed? Do all of the individual commands in a macro work via the MSC-400 when sent from the MX-3000?

Mike

Yes it starts the command but some components do not respond. The entire macro works perfect when sent by the PC that is hooked to the MSC. Individual command work via the MX3000.

I started each room with a simple macro of about 3 to 4 components and then started adding things such as lutron light control and makita drapery control and a bluray player. The odd thing is the components that were first set up all still work and all of the ones I added are not. I even completely deleted the original macro and programmed a new one with all 8 or 9 components and I get the exact same results.

Is it the components on ports 1 through 6 that work and the others dont work? You have to use a secondary RFID with an MX3000. The primary ID is the address for ports 1 through 6 and thesecondary is for ports 7 through 12 (that is if you are using ports 7 through 12 for IR)

No I'm using 7-12 for serial and have 5 components on 1-6 and3 of them work the other two do not. I tried chaning the IR level with no luck either

ever figure this out because I"m having the same problem

I am having the same problem too... anyone out there have a solution... pretty please :)

scratch that... just figured it out.

For some reason although all my main Configuration settings properly reflected the Master and Slave devices... everything under "connect devices" was still showing "Master"

-Open up MSC-400 Editor
-Right on device under "Connected Devices"
-Select Properties
-Modify the settings to Master if for Master devices, and Slave for Slave devices.
-Repeat for all devices

Aaargh! I'm stuck on this too but cannot seem to get around it. *None* of my triggers work. Testing the macros from the MSC-400 editor (version 1.50.005) work just fine, but attempting to trigger them from the MX-3000 does nothing but blink the MSC-400's Status light indicating that it's receiving something. In the MSC-400 editor I have double-clicked on each device's "Configuration" within "Connected devices" as well as tried the right-click on the device name and selected "Property" which pops up the same window as double-clicking on "Configuration" for each device. Therein I verified the MSC appropriately as "Master" and the Port value. I have tried both the device's exact port number as well as 'ALL', but to no avail. I've also checked and re-checked the master "Configuration" for the MSC Basestation ID "Master" has a valid RF-ID (of '1' -- not '0'). Finally, I've also tried right-clicking "Properties" for each smart-macro and under IR de-selecting the Use Parent Setting enabling me to explicitly set the MSC and port (again, when applicable, tried single port numbers as well as 'ALL'). I've been playing with this for hours and it's become extremely frustrating. I'm only using ports 1-6 on the MSC. IR's issued from the MX-3000 editor and device work fine. All IR-emitters are firmly inserted. I have RF-only selected in the MX-3000. I have in the MX-3000 editor deleted-contents from each triggered button and re-copied/pasted from the Universal Browser ad nauseam. Any other ideas???

Eureka!!! Finally found the source of the problem. After putting the equipment away and returning to it for a fresh look, I spotted the issue. There appears to be a bug (in my opinion). Somehow the MSC400 editor *duplicated* Multizone Codes for different macros. Interestingly and thankfully, the multizone code that is auto-generated is editable in the Properties for the macro, each of which must be unique across the entire project; i.e. not just within each smart macro group. So, I edited the multizone code for each macro in the MSC400 editor ensuring they all had a unique value. Voila. Problem fixed.

Interestingly, while editing the multizone code if YOU try to update it manually to a value that another macro is already using, you will receive an error message.