User manual

Phoenix
32
User Manual www.RealmCtrl.com
8
impact on the behavior of the control system.
If you choose to enter information into the Text Fields, you should first change
the generic “Text Field 1,” “Text Field 2,” and “Text Field 3” labels to indicate
exactly what information you are entering. This can be accomplished by
clicking [Defaults] and entering new labels for the Text Fields. This is also
true of the Room Attributes and Numeric Fields.
4.1.1.2. The six Room Attributes are also for general use in managing your facility.
However, they may be used to alter the behavior of your control system as
well. Whereas the information that you enter within the Text Fields is not
transmitted to the NetLinx control system, the settings of the Room Attributes
are known by NetLinx. This can be used to cause customized behavior that
can be enabled and disabled via the Phoenix
32
interface. For example, you
might label “Attribute 1” to read “Radia Lighting Control” (See Section 4.1.1.1
for instructions regarding re-labeling of the Room Attributes). A RealmCtrl
Software Engineer could then author custom NetLinx code to enable Radia
lighting control in only those rooms that have Attribute 1 checked. Thereafter,
should you add Radia lighting control to a room that did not formerly include
that capability, you could accomplish this by simply checking Attribute 1 for
the destination. This would allow you to add the capability for any room
without requiring custom code authored room-by-room. I.e., once a custom
capability is added by RealmCtrl to be enabled or disabled contingent on a
Room Attribute, you can then add or remove the associated control system
capabilities without even contacting RealmCtrl or requiring any NetLinx code
modifications whatsoever.
Aside from using the Attributes to enable/disable custom room control
behavior, they may also be used simply to track room information. For
example, you may change the label on Attribute 1 to read, “Video Conference
System”, then use it to track those rooms that contain video conferencing
hardware.
4.1.1.3. Much like the Room Attributes, the Numeric Fields can serve a dual purpose.
On the one hand, they can be used simply as an organizational tool to help
you manage your facility. An example would be changing one of the labels to
read “Seating Count”. The Numeric Fields are also transmitted to the NetLinx
control system. Therefore, if your facility included several different “cookie
cutter” room configurations, you could use the fields to cause varied behavior
by the NetLinx control system based off their settings. I.e., during the course
of the system design process, it may be determined that Room Configuration
1 contains a projector, two plasma screens, and lighting control. Room
Configuration 2 might contain only one standard television and so on.
RealmCtrl could then author code to control the rooms differently, and present
different controls to the end users via their XGen web client interface or in-
room touch panel(s) if applicable. This would allow you to add rooms in the
future that adhere to the template and define them in Phoenix without
requiring additional NetLinx code modifications.
4.1.1.4. A Default Channel is the RF channel or baseband crosspoint that a
destination will tune to when no event is active, or when an end user enters
Local Mode while an event is active (see section 10.1.3). Phoenix allows
configuration of Default Channels by room or by Distribution Group. If you do
not specify an overridden Default Channel via the [Default Channel…] button
then the room will automatically adopt the Default Channel of the Distribution
Group that it is connected to (see section 4.3). To override the Default