User manual

Phoenix
32
User Manual www.RealmCtrl.com
97
12. Understanding Hub Systems
Hub Systems are similar to Remote systems but with a very important distinction: Hubs allow
duplication of device IDs across multiple systems. Because the AMX AXcess devices must
be addressed with unique IDs that range from 1-255, a mechanism must be in place for those
facilities that need to control more than 255 rooms while using the AMX AXlink Television
Managers. With the advent of the NetLinx Television Manager, this need will be lessened
(should that day ever come). However, due to cost and legacy equipment in place, there will
be a need for such a solution for years to come. When using Hub Systems, each standalone
NetLinx master is considered a Hub, with the Head End being Hub 1. In Phoenix, on the
Destinations Tab, the Television Managers are addressed with a System ID that corresponds
to the Hub that they are connected to. For example, if a system were to include three Hubs,
the TMs on the AXlink of the Head End would be addressed as Device:1:1. Those on the
AXlink of Hub 2 would be addressed as Device:1:2, and those on the AXlink of Hub 3 would
be addressed as Device:1:3. The same AXlink bus ID may be used as the Device ID.
Phoenix distinguishes between them according to the System that they are connected to.
When the Television Manager IDs are entered on the Destinations Tab, any TM ID with a
System ID greater than 1 will cause the field labeled “Remote IP” to change to a field labeled
“Hub IP”. This is where the IP address of the Hub System is entered (note that the Hub must
be configured with a static IP address). An example of a Hub System topology is shown