User manual

Phoenix
32
User Manual www.RealmCtrl.com
95
Figure 45: The Help Ticket Service Page.
11. Understanding Remote Systems
Phoenix allows use of standalone NetLinx and Axcess control systems that communicate
with the Head End control system via TCP/IP or RS-232. A Remote topology is employed
when the distance to the destination exceeds the capabilities of the Axlink bus, or when
advanced in-room control capabilities are required that fall outside the scope of the turnkey
Phoenix feature set.
The preferred method of communication is TCP/IP when using a Remote NetLinx system.
However, Phoenix also supports RS-232 communication with Remote Axcess systems, for
sake of backward compatibility with Synergy. Whereas the RS-232/Axcess solution requires
dedicated connectivity from the Head End to the Remote destination, the TCP/IP version
utilizes the campus LAN/WAN. This means that destinations can be controlled that may be
off campus – even across the world if the Remote NetLinx system can be reached from the
Head End control system via TCP/IP.
Regardless of the type of Remote system, code must be loaded into the Remote NetLinx
control system in order to enable integration with Phoenix. Any room that is connected to the
Remote system will behave just as if it were connected to the Head End, although it may
have other custom features available as well. Each Remote system may support multiple
rooms or only one room if the required customization warrants a dedicated system.
Remote Axcess (RS-232) and NetLinx (TCP/IP) systems can be used within the same
system. Therefore, if your facility already incorporates remote Axcess systems, you may
move forward with remote NetLinx systems without having to replace your existing hardware.
Examples of the two topologies are shown on the following pages. Again, although the two