User manual

Phoenix
32
User Manual www.RealmCtrl.com
2
example: “Click {Server}.”
Dialog and tab names are shown in bold and italicized. For example, “Rooms are
configured using the Destinations tab.
2. Installation
2.1. Groundwork
2.1.1. Installation of Phoenix
32
should be implemented by a qualified AMX NetLinx
Installer who has experience with distributed control systems and a general aptitude
for audio/visual control system support. Due to the inherent complexities present in
any distributed control system like Phoenix
32
, installation by uncertified persons is
discouraged.
2.1.2. A solid infrastructure is paramount. Because Phoenix
32
communicates with the
industry standard TCP/IP protocol, it is absolutely imperative that the Phoenix
32
Server application can reach the NetLinx control system hardware at all times.
Also, the NetLinx control system must have connectivity back to the Phoenix
32
Server at all times. If this communication path between the two “sides” of the
application is not present at any time then the entire system will be unreliable and
may fail entirely, depending on what demands are being placed on it at the time of
the communication failure. For this reason, it is the strong recommendation of
RealmCtrl that a dedicated router be installed in the Head End to facilitate TCP/IP
communication. Should you choose instead to utilize the existing campus LAN as
the communication mechanism, you should understand that the stability of the
Phoenix
32
application will be entirely dependent on the stability of the campus
network. It is also important to understand that any communication failures that can
be attributed to a faulty TCP/IP communication mechanism would fall outside the
scope of support provided by RealmCtrl.
2.2. Basic Installation Procedure
The following basic installation procedure explains how to install and validate turnkey
Phoenix
32
. Because some facilities will have need of multiple NetLinx and/or AXcess
control systems, and possibly some customization to suit the specialized needs of the
campus, this summation should be considered as a general guideline, not a concrete
procedure to follow at every installation. Therefore, the Basic Installation Procedure
should be considered an “initiation” to the world of Phoenix
32
. Proficiency in the many
facets of system installation and support can only be gained with experience. RealmCtrl
recommends that any Dealer who wishes to resell Phoenix first work closely with a
RealmCtrl Installation Support Technician to complete at least one successful
installation. Thereafter, installations may be accomplished without on-site support from
RealmCtrl if the Dealer Technicians feel confident that the overall procedure is well
understood.
2.2.1. Step 1: Install the NetLinx Head End control system.
Installation of the NetLinx control system hardware should be accomplished
according to the requirements of AMX Corp. in terms of mounting, cabling, power
requirements, etc. Phoenix
32
will work with any of the NetLinx central controller
products including the NI series integrated controllers and the standalone ME-
260/64 NetLinx Controller. Which NetLinx control system is right for a campus
depends on the needs of the facility.
If the site is upgrading from the predecessor to Phoenix
32
, known as Synergy
32
,