In a MSC-400 all executed commands are macros from as short as 1 step to 255 steps in length.

The Convert to Smart Macro option takes the Command Library in the Connected Device tree and makes those commands into macros. It's just a shortcut.

The Hotkey triggers _only_ link macros to the buttons on the handset. You cannot link commands within the connected devices, that is just a pool of data that the macros are built from.

Who's doing this? Every command on the controller being a trigger command to the MSC. More reliable this way or ??? I'm trying to understand the benefit of this when it only involves one command anyway...

No, every command in the MSC being a hot trigger mapped to the remote handset. You have to do that for every action you want the MSC to take, whether it is a single action or a 10 step macro.

As a rule I make the MSC400 do everything possible _except_ in the case where I'm using IR for volume control in which case I will program those commands to the handset and pass it through the IR ports as though it were a MRF base.

So, even your digit keys, directional pad, etc. are triggers on the MSC? What is the benefit of this?

It has to be if you're controlling something with RS232. Otherwise in an IR system the RF gateway is open for a much shorter period of time for the MSC trigger regardless of what key you are pressing which does increase the robustness of the control system. If you're going to pass a majority of your commands through from the remote handset what's the point of using the MSC anyway? MRF350 is half the price.

I also make a lot of use of the relays and the 12v on the back of the MSC. I never use the sensors.

I understand how this works, we only install the MSC-400 with any URC system and they all utilize at least one serial device. I'm just not sure why people are issuing trigger commands for a single IR command via the MSC. Seems to me there is no benefit of this...

For IR commands that do not need to have immediate response like 10-key, cursor, channel, menu, etc. the advantage is that the RF gateway is open a fraction of the time for the MSC trigger than it would be for the RF signal from the remote. The remote's RF signal includes the preamble and the command at least once (sometimes 3 or more times) and the entire time that RF command is being received the gateway is open. The longer the gateway is open the more chance there is for local RF noise to cause the command to fail.

For commands that need high performance and response time like volume up, down and mute then that can be passed directly through as the MSC will impart a slight but perceptible latency that is kind of annoying. The chance that you will have RF noise and failure is greater because the gateway is open during the entire time that button is pressed, but to have failure on every command (like number pad) is more annoying.

Besides, why would you double your work and build macros inside the MSC and build macros from the remote? That seems like a lot of extra work and program management when almost everything you need to do with the system can be executed by the MSC.

^^^ this is the reasoning I was looking for, thank you for that. This is the first I've heard this despite being present in about a dozen URC trainings over the years.


That's what I do, macros are always on the MSC side activated by triggers commands on the remote. I was merely confused about the reasoning for single IR commands to exist as trigger commands...your explanation makes sense. Thanks again.

Another issue with running macros from the remote and the MSC 400 is that the MSC is unaware of what the remote is doing and vice versa. The MSC only has a single IR engine and if it is executing a long macro via a hot trigger a macro that is being executed by the remote will be ignored. The problem will be magnified if you are using sensors to check state and the macros in the MSC are delayed until the state is confirmed.

The whole point of the MSC is to offload all of your macros to a standalone "macro player" which can be fired off with 4, 5, 6-bit or whatever RF triggers.

I try to force the MSC to do everything it possibly can and massage all the macro delays, IR repeats, etc. to work in the tightest tolerances for snappiest system performance.

The only issue I've encountered with trigger everything to the MSC-400 is variables (on the remote itself) can get "dicey".

Yep, because outside of the RF communication between the two devices they otherwise don't know anything about each other. A remote using variables to track page changes or users of whatever can get out of sync with what the MSC is doing. There is not checksum between the two, it's point and pray and hope they remain in sync.

I have dozens and dozens of 980s in the field, and I have one that I can think of with this possible problem.

It only is an issue when using favorite channel macros on a DirecTV HR21-200 receiver. The digits show on the TV screen with totally random delays between them. Sometimes they fire in a quick shot, one after the other, then next try, a long delay between a couple... It's odd but makes the macros unreliable. Using RF.

I thought it was the DTV receiver. Yesterday this HR21 subbed for the existing HR22 (I know, going backwards, but that's what the client was sent). After installing this new receiver, I thought it was better, but now I am not sure.

I chalked it up to slow response of the DTV receiver but I just don't know - anyone seen this? I didn't have the most recent CCP update yesterday when I was out at the house to test.

If I get a chance to go back after the family returns from vacation, I may try another remote (this one is probably 2 years old) and updated CCP.

I'll be watching the thread to see if you indeed think the problem is solved.