Armed with the hardware (MX-3000 and MSC-400) and editor software, respectively, I sat down and "played" a bit trying out different things to improve my understanding of the documentation. Granted, I may have skimmed too quickly (or lost a page?), but I'm trying to understand what seems like "magic" in how IR commands get mapped to RF ones. Actually, "mapping" isn't the best word to use. I gather that the first step is to create the devices specifying the precise mfg/model in the MX-3000 editor. Then, moving on to the MSC-400 editor, one imports the devices by specifying the file created and saved by the MX-3000 editor. After making the proper assignments in the configuration for each device and creating smart macro groups and macros in the MSC-400 editor and saving that file, one then returns to the MX-3000 editor, opens the Universal Browser and specifies the saved MSC-400 file, and drags from therein a MSC-400 macro to the macro-window corresponding to a desired button in the MX-3000 editor. This is where the "magic" seems to appear:

1. I assume that for each MSC-400 macro that is created, a corresponding unique RF-code is generated. Is that right?

2. Presuming so, I guess that if one is relying 100% on RF (i.e. all A/V equipment is out of view and connected to the MSC-400 via IR-emitters), then one must create a smart macro for each and every IR function which one desires to send from the MX-3000 by way of RF activation (i.e. "trigger") from a button. Right? Hence, each MX-3000 button for which any IR activity is desired -- even a single IR code -- must be programmed as a MSC-400 macro which appears as a "trigger": 'T' by the button in the MX editor and listed in the respective macro window. I guess technically, within the realm of the MX editor, it is not necessarily *just* a trigger but truly a "macro", because one can perform multiple actions within a single macro step (e.g. Delay, Jump, Sound, etc.). *whew*

3. I note that each smart macro group created results in the sequential generation (albeit apparently available to override with value between 0 and 255) of a "Multizone Code". Then, macros created within each smart macro group get sequentially numbered, beginning with '1', which can be seen in a greyed-out box (i.e. non-editable) alongside the multizone code. May I conclude that the combination of these values (and others, e.g. the RF ID) is what "produces" the unique RF code with which the MX-3000 gets assigned by dragging the macro into the MX-3000's macro windows?

4. To ensure "RF transmission" of a trigger from the MX-3000 to the MSC-400 (by way of the RFX-250) one must verify that minimally "RF" (or "IR & RF") is selected as the Signal in the MX-3000's "RF Setup/Control" window.

If any of these assumptions are wrong or could benefit from further clarification/explanation, I would be very grateful if anyone would followup with replies. Ditto for any sage words of wisdom (and/or warning).

1. Yes

2. I don't know if I fully understand what you are saying, but the codes you don't have as smart macros (single codes) will be routed through the MCS-400 via RF. Make shure the remote is set to RF only.

3. Yes, but since you drag the smart-macro into the 3000 editor it is of less importance.

4. I would go with RF only just to minimize the risk of confusion with other devices, especially when just routing commands through the basestation (not sending a trigger code). Specially important if you actually is within line of sight, otherwise you could end up with double actions.