I am programming a MX-1200.  Transferring a setup from a MX-980 and MSC-400.  I used the transporter function so I didn't have to rebuild some devices that I had corrected errors in teh RS232 database, and some custom (hex code) devices.  I rebuilt the macros exactly like they were on the MX-980 but couldn't get them to work. 

After several hours of tedious troubleshooting I found the issue.  I found that if I have a "regular" command coming before a smart macro command, the smart macro won't fire.

Example that works:
Smart Macro: Watch Tivo
Alias: CineSlide On

Example that does not work:
Alias: CineSlide On
Smart Macro: Watch Tivo

In both cases the CineSlide command is executed.  Only the first one will fire the smart macro.

The same macros work on the MX-980 in any order, as they should.

Any idea what coudl be wrong?  Is this a bug with the MX-1200?  Can anyone try it on theirs?

Thanks,
Scott

Scott, send the file to my profile address and I will take a look at it.

Done. Thank you.

TCR suggested I add delays between the commands I was having trouble with.  Didn't help.  I added a 2 second delay, smart macro last, made no difference.

I found that if the smartmacro came last, the RF light never blinks on the antenna module, and no blue blink happens on the 400.  If it's not first, the remote doesn’t send RF, apparently.

So I had a theory which I tested and it appears to be correct.  Theory was IR device commands can't come before RF based comands.  Taking Smart Macros out of the original theory as the problem.  I moved to IR vs RF as the culprit.   


Theory test:

Place 2 commands, seperated by a 2 second delay to be sure delay was not the issue.

Case 1:
1. Command that is a direct IR command, with the device's signal set to IR (only) in the RF control window (e.g. CineSlide IR).  
2. SmartMacro (RF based) command
FAILS. Smartmacro is NOT executed.  No RF signal transmitted, no blink of antenna module

Case 2:
1. SmartMacro (RF) command
2. Command that is a direct IR command, with the device's signal set to IR (only) in the RF control window (e.g. CineSlide IR).  
Excutes properly

Case 3:
1. Individual button press command from a device set as RF in the RF control window (e.g. Oppo ON).  MSC-400 sends IR command.  Not a smartmacro.
2. SmartMacro (RF based) command
3. Command that is a direct IR command, with the device's signal set to IR(only) in the RF control window.  
Excutes properly.  

Case 4:
Same as failing case #1 above, only this time set the same IR (only) device to "IR & RF" in the RF control window
1. Command that is a direct IR command, with the device's signal set to IR & RF in the RF control window (e.g. CineSlide IR, edited to send IR and RF).  
2. SmartMacro (RF) command
Executes properly.

Conclusion:  Devices with IR only settings before a RF based command casue subesquent RF commands to fail.  At least within a macro, my MX-1200 will not swith back to RF once a IR (only) device command is executed.

Fix:  Set all IR only devices to IR and RF.  I set the RF output port to Blaster to avoid unneeded static on other output ports.

Shouldn't have to, but there it is.  I'd be very interested if anyone can duplicate.  The MX-980 in the same CC file did not have this issue, so I can only assume the bug/problem is with the MX-1200.

Scott, please forward your findings to URC - would be interested in seeing what the story is. I have found many quirks in the MSC-400 especially when nesting macros and mixing IR & RF commands.

Will do.  I'll post on their dealer forum.

I have duplicated this very same condition with my MSC400 and MX880. It didn't used to do that but I think a recent CCP update borked it.

We just ran into the something similar on a job. We had two MX980's, a MX780, and an MSC400. And had the same kind of thing happen with the 780. Had to come up with workaround to finish the job.