Crestron cen-oem User Manual
Crestron eServer™
Ethernet
OEM
Module
Crestron Control
Crestron control is defined as an interface to a Crestron Ethernet device.
Implementation of this method is necessary for a device to communicate with a
Crestron control system. Use of this interface method does not place design
limitations on the project. For example, a device can implement a Crestron control
system interface, have a web interface, and have a custom PC application
communicating to the same eServer. Refer to configuration # "2. Crestron Control
System Control of a Device Through the eServer" on page 8 for details of this
interface method.
Implementation of this method is necessary for a device to communicate with a
Crestron control system. Use of this interface method does not place design
limitations on the project. For example, a device can implement a Crestron control
system interface, have a web interface, and have a custom PC application
communicating to the same eServer. Refer to configuration # "2. Crestron Control
System Control of a Device Through the eServer" on page 8 for details of this
interface method.
Non-Crestron Control
Non-Crestron control is defined as control and monitoring of equipment through any
web browser or custom application. Since the eServer has many applications outside
the audio-video industry, a designer can use the device without other Crestron
devices. As a result, the only interface necessary is a web browser or a custom
application built by an OEM designer. Use of this interface method does not place
design limitations on the project. For example, Crestron tools such as VisionTools™
Pro-e, the e-control™ Software Development Kit (SDK), and SIMPL+ can be
utilized to build the project, but no Crestron device or software is needed to
communicate with the box. Refer to the next section for multiple configuration
possibilities of this interface. Only one (configuration # "2. Crestron Control System
Control of a Device Through the eServer" on page 8) of the five configurations
presented does not apply.
web browser or custom application. Since the eServer has many applications outside
the audio-video industry, a designer can use the device without other Crestron
devices. As a result, the only interface necessary is a web browser or a custom
application built by an OEM designer. Use of this interface method does not place
design limitations on the project. For example, Crestron tools such as VisionTools™
Pro-e, the e-control™ Software Development Kit (SDK), and SIMPL+ can be
utilized to build the project, but no Crestron device or software is needed to
communicate with the box. Refer to the next section for multiple configuration
possibilities of this interface. Only one (configuration # "2. Crestron Control System
Control of a Device Through the eServer" on page 8) of the five configurations
presented does not apply.
Choose the Configuration
The second question to answer when deciding to incorporate an eServer into a
development project is which configuration should be used. The configuration
depends on the application. Any combination of the configurations listed below are
permissible with the eServer. Although most projects would probably utilize only
one configuration to simplify development, using more than one configuration at the
same time is generally allowed. The only exception is #5. Opening a TCP connection
while utilizing #1, 2, 3, or 4 temporarily suspends configuration 1, 2, 3, or 4 until the
TCP connection is closed.
development project is which configuration should be used. The configuration
depends on the application. Any combination of the configurations listed below are
permissible with the eServer. Although most projects would probably utilize only
one configuration to simplify development, using more than one configuration at the
same time is generally allowed. The only exception is #5. Opening a TCP connection
while utilizing #1, 2, 3, or 4 temporarily suspends configuration 1, 2, 3, or 4 until the
TCP connection is closed.
1 Web browser control of a device through the eServer
2 Crestron control system control of a device through the eServer
3 Web browser control of a device through the eServer utilizing PC-
based web server and Crestron CNX gateway software
4 Custom application control of a device through the eServer utilizing
Crestron ActiveCNX control
5 Custom application control of a device through the eServer utilizing
standard TCP/IP sockets.
Implement the Chosen Configuration
1.Web Browser Control of a Device Through the eServer
This configuration permits any standard web browser to become the interface for the
device. For example, the IP address for the eServer dedicated to the switcher can be
entered into a web browser. If designed properly, the resultant screen shows the
current state of the device. The device interface on the web page can allow real-time
device. For example, the IP address for the eServer dedicated to the switcher can be
entered into a web browser. If designed properly, the resultant screen shows the
current state of the device. The device interface on the web page can allow real-time
Operations Guide - DOC. 8148
Ethernet OEM Module: eServer™
• 7