SP Controls PX2-NRC-1142 - Manual (Page 8)

Customization is how you map exactly which command or commands are sent with each button press
or other event. Most of this will have already been set automatically in previous steps, but here you
can fine-tune it all. First, a brief glossary of terms that we’ll use in this section:
Node: A node is always an SP Controls product in the PixiePro family. Nodes are numbered sequen-
tially as you add them to the bus. The NRC is itself a node, and it will always be numbered 0. Other
possible nodes are the Modular Panel and the different flavors of Control Puck.
Action: An action is a single device control command sent by the NRC to one and only one port.
They come in three flavors: RS-232 command, IR command, and relay opening or closure.
Action List: Just what it sounds like: a list of actions sent sequentially to any number of different
ports on the NRC (or attached Control Pucks, which will be discussed in Advanced Configuration).
Event: An event initiates an action list. These are the possible events that can trigger NRC actions:
• a button pressed by a user on the Modular Panel or in the Web-based controller
• a scheduled timer event
• the opening or closing of a relay detected by one of the sense ports
• receipt of an RS-232 communication from a device (or failure of communication)
Each button will have an action list assigned to it. Action lists may contain multiple actions or just a
single action. You’ll notice that many of the button-press events have already been populated with ac-
tion lists. That was done when you told the NRC which display driver to use, and which input selec-
tion commands you wanted to send.
In this step you tell the NRC which commands to send to your various devices in order to switch in-
puts and you specify which device will control system volume. (In this chapter, we’ll deal with just a
single display device. In the Advanced Configuration chapter, you’ll find out about switching more
complex systems.) In Step 2, you told the NRC which display device to control by assigning a display
driver. Now you’ll map the selection commands from that driver to specific input selection buttons.
Selection 1 is the source selection button in the upper-left hand corner, Selection 2 is in the upper-
right hand corner, Selection 3 is second down on the left, et cetera.
For Advanced Configuration information for this step, go to page 23.
Mouse over any button to see its action
list; some buttons will have action lists
assigned from previous configuration
screens, while some buttons will start
blank and need action lists configured
The tabs indicate which device the TCM Menu but-
ton module section will control (in this example,
there’s just one device, the projector); “Hidden” tab
shows which buttons have been assigned action
lists that are active while in Hidden mode (many dis-
play drivers contain pre-configured hidden functions)
13
By default, the NRC will send the input selection
command of the last-selected input to your dis-
play at power on. You can change this so it al-
ways sends the same command after startup if
you always want the startup selection to always
be one particular input.
Choose the input selection commands
from the pull-down menus. Selection
numbers correspond to selection buttons
on the Modular Panel.
Lets you select different TCM profiles/remote
control codes from drivers you selected in
Step 3 above. See Advanced Configuration
for more information.
“Volume Control On” tells the system
which device handles volume control.
Change this when your audio will be con-
trolled by something besides your display
device (e.g. SP3-AFVP+, external amplifier,
switcher-scaler).
12