Download Crestron e-Schedule Specifications
Transcript
Crestron e-Schedule Programmer’s Guide Since the CN-TVAV in Classroom 1 does not support Cresnet peripherals, the local touchpanel and CNECI-4 must be wired directly to the Cresnet network and bridged to Ethernet by the head end control system. Thus the control signals for this hardware must also be routed through ISC symbols. InterSystem Communications Symbol An ISC, or InterSystem Communications symbol is used to pass digital, analog and serial signals between control systems. An ISC symbol is programmed identically to an ActiveCNX Interface and its definitions are determined by whether it is a 1) Source or 2) Destination. CEN-TVAV The CEN-TVAV units that control Classrooms 2 and 3 of the sample system are loaded with the same program, since they both have the same configuration. Here a “Destination” ActiveCNX Interface and a “Source” ActiveCNX Interface (for the local VCR source) will be programmed into the CEN-TVAV. The touchpanel and CNECI-4 will communicate with the CEN-TVAV through Cresnet, as usual, and the MRHC transmitter will control settings for Power, Mute, Volume, Source Control and View Channel. Points to Remember • All components of an e-Schedule system—the Web Server, Real-Time Engine, CNX Gateway(s), and Crestron control systems—must have static IP addresses. • e-Schedule defines three ActiveCNX Interfaces, each with different signals for 1) Sources 2) Switchers and 3) Destinations. • An ActiveCNX Interface is considered an Ethernet "device," and therefore gets an IP ID and an entry in the IP Table, which must reference the IP Address of the CNX Gateway. • An Ethernet enabled control system must serve as a bridge from any non-Ethernet Cresnet-based hardware to the Ethernet network. The programming is as follows: 1. In the bridge control system, include a “Destination” ActiveCNX Interface for the non-Ethernet controller, and a “Source” Active CNX Interface for each local source (if any). 2. Use InterSystem Communication symbols to pass signals back and forth from the bridge to the nonEthernet hardware. Programmer’s Guide • An ISC is programmed identically to an ActiveCNX Interface. • Avoid tiered switching, i.e., any environment where resource allocation problems may arise. e-Schedule – DOC. 5919 • 36