JNIOR Application Note INTEG Process Group, Inc.

1

Configuring the JNIOR for use with the Christie IMB

Last updated: April 1, 2013

The following information describes how to use the JNIOR with the Christie IMB server. Please contact INTEG via e-mail at rshulkosky@integpg.com or via phone at 724-933-9350 extension 20 with any questions. Overview The Christie IMB can interact with the JNIOR two ways –

1) Sending Serial(ASCII) commands to the JNIOR via the Cinema Server Client port

2) Sending HEX (binary) strings to the JNIOR via the JNIOR protocol (server) port

In order to use method 1 above and to run macros on the JNIOR, Cinema.JNIOR will have to be installed. Technically speaking, for method 2, basic control of the JNIOR relay outputs can be done without Cinema.JNIOR being installed, but Cinema.JNIOR is required to execute macros on the JNIOR. For simplicity sake, it is always recommended to install Cinema.JNIOR. Installing Cinema.JNIOR Cinema.JNIOR is installed using the JNIOR Support Tool. The JNIOR Support Tool can be downloaded from the INTEG website at the following link. Please download the file and double click to install. http://www.integpg.com/jnior/ethernet_io.aspx#page=downloads_content.aspx The latest Cinema.JNIOR ‘update project’ can be found on our Cinema downloads page at the following link. http://www.integpg.com/cinema/cinema.aspx#page=downloads_content.aspx Please download the zip file, but do NOT unzip it. Go to the Update tab in the JNIOR Support Tool and click on the Open Project link and then navigate to where you saved the update project. The JNIOR Support Tool will unzip the project. Then click Publish Update to JNIOR and select your JNIOR. NOTE: If this is the first time you are installing Cinema.JNIOR on your JNIOR, it is recommended that you leave all the steps checked and then you can configure Cinema.JNIOR for your application. If you have already installed Cinema.JNIOR, then you only want the first and last steps checked. Please see the examples below.

JNIOR Application Note INTEG Process Group, Inc.

2

Installing Cinema.JNIOR the first time (typical)

Updating Cinema.JNIOR (typical)

JNIOR Application Note INTEG Process Group, Inc.

3

Method 1 – Configuring the Cinema Server Client for sending Serial commands The Christie IMB can send serial (ASCII) commands to the Cinema Server Client to control the JNIOR relay outputs and to run macros on the JNIOR. Serial command actions can be added to Christie IMB macros by adding an activity with the following parameters: Automation Device: IMB Automation Activity Type: Serial String Output Typical commands are as follows (please see the Cinema.JNIOR manual for a complete explanation of all the commands available): run macroname where macroname is the name of the macro stored on the JNIOR and the word run must be in lowercase ::c1 close relay output 1 ::o1 open relay output 1 ::c1p=1000 pulse closed relay output 1 for 1000 milliseconds Please note:

‐ The ‘incoming’ termination string for the Cinema Server Client as part of Cinema.JNIOR must match the termination string being added to each outgoing message sent by the Christie

o \r = 0D = carriage return o \n = 0A = line feed

The ‘default’ setting in Cinema Server Client is \r\n so you must add \0D\0A

‐ The TcpPort can be any port not already being used (9600 is an example) and must be the same on both the Christie and JNIOR

In the Christie Serial String set-up, the following is an example command: run show start\0D\0A (where show start is the macro on the JNIOR) ::c1p=1000\0D\0A

JNIOR Application Note INTEG Process Group, Inc.

4

The Cinema Server Client is configured from the main JNIOR web page. Please go to the Registry tab and then the AppData – Cinema – Cinema Server folder. The screen picture below shows the recommended settings for the Cinema Server Client to work properly with the Christie IMB. The most important settings are circled in red.

JNIOR Application Note INTEG Process Group, Inc.

5

Method 2 – Sending HEX (binary) strings via the JNIOR Protocol (Server) Port The Christie IMB can also send HEX (binary) strings to the JNIOR protocol (server) port. The Christie can run macros stored on the JNIOR and control individual relays by sending the appropriate HEX (binary) string. NOTE: The default setting for this port is 9200 and it is recommended that this port number be used. A variety of JNIOR applications use this port and most of them will ‘auto detect’ the actual port number, but to be safe, it is best to leave it at 9200 for any custom applications that do not auto detect the port number. The user can change this port number from the main JNIOR web page by going to the Configuration tab and then the Misc. tab as shown in the screen picture below. NOTE: To control macros on the JNIOR, the Christie does NOT have to login to the JNIOR. The HEX string can be sent without logging in. However, to have the Christie control individual relays (or other actions on the JNIOR), the Christie has to login. Since the Christie does not currently have the ability to login to the JNIOR when it sends a HEX string for individual relay control, the user must ‘disable login’ on the JNIOR. The user can disable login from the main JNIOR web page by going to the Configuration tab and then the Misc. tab and unchecking the box as shown in the screen picture below.

JNIOR Application Note INTEG Process Group, Inc.

6

Triggering a macro on the JNIOR In order to trigger a macro on the JNIOR from the Christie IMB, the correct HEX string must be created. The HEX string can be created using the Macro Execution tool which is part of the JNIOR Support Tool. The Macro Execution tool can be launched by ‘right-clicking’ on your JNIOR in the Beacon tab and selecting Macro Execution or by going to the Tools pull down at the top and selecting Macro Execution.

The Macro Execution tool is shown below. Type the name of your macro in the box (it is NOT case sensitive) and the HEX string will be created in the box. You can test your macro on the JNIOR by clicking on the Connect button and the Send button. The Macro Execution tool will send the execute macro command to the JNIOR. On the Christie IMB, HEX commands must be “escaped” with backslashes. Therefore the following Hex command:

010008ffff0a070101000001f4 needs to be entered in the Serial String field of the macro Activity on the IMB as follows:

\01\00\08\ff\ff\0a\07\01\01\00\00\01\f4\0D NOTE: The \0D that is added to the end of the string to ensure the string is followed by a carriage return.

JNIOR Application Note INTEG Process Group, Inc.

7

Macro Name Sender Tool

Controlling the relays on the JNIOR Individual or multiple relays can be controlled (pulsed, opened, closed) on the JNIOR by sending a HEX string. The HEX string to control the relays is created using the HEX String tool which is also included as part of the JNIOR Support Tool. Go to Tools – Advanced – Hex String Sender as shown below:

JNIOR Application Note INTEG Process Group, Inc.

8

When the tool is opened, please select the command you want to use in the left window box and select or enter any additional information required. For example, in the Pulse Single Output command you have to select the channel (i.e. output number) and enter a pulse duration. Below is a screen picture of the command for pulsing relay output 1 for 1000 milliseconds. Note that you can ‘uncheck’ login required to make sure this feature is disabled on the JNIOR.

NOTE: The HEX string sender tool only works when the JNIOR protocol port is set to 9200. The current version does NOT ‘auto detect’ the JNIOR protocol port number. You can click on the Test button and the application will send the HEX string to the JNIOR to be executed. The tool will ‘login’ to the JNIOR first, if the Login Required box is checked. The tool is only capable of using the standard default JNIOR username and password.

JNIOR Application Note INTEG Process Group, Inc.

9

Miscellaneous Information If you want the JNIOR to be able to Start and Stop the Christie player, then you have to do the following. Configure the Christie IMB as a RAW ETHERNET device in the Cinema.JNIOR devices file. The JNIOR will communicate with port 5111 on the Christie IMB.

Link your Devices file to the Macro file and then add actions that will send the appropriate string of text to the Christie. In the example below, the actions to send the strings IN1=1 and IN2=1 were created and added to two different macros. NOTE: You will have to configure the Christie IMB to recognize these two strings so that when the Christie receives IN1=1 it will Play the Show and when it receives IN2=1 it will Stop the Show. NOTE: You can select any text that you want for these actions. The strings are only sent to port 5111 when the macro is executed. Although the example message (IN1=1) is created when input 1 goes ‘on’, the message is not automatically sent to port 5111.

JNIOR Application Note INTEG Process Group, Inc.

10

Sample Screen Pictures from the Christie The screen picture below shows the Christie Serial String to trigger a macro on the JNIOR using the “run macro name” command. NOTE: The \0D\0A string is added to the end of the Serial String.

The screen picture below shows the HEX Serial String entered into the Christie.

JNIOR Application Note INTEG Process Group, Inc.

11

Below is screen picture showing the JNIOR Protocol HEX String Sender tool (part of the JNIOR Support Tool) being used to create the HEX string to Open Output 1 and the corresponding Serial String entered into the Christie.

JNIOR Application Note INTEG Process Group, Inc.

12

Example Christie IP Configuration Scheme The Christie requires multiple IP addresses. It is very important that you configure the Christie correctly so that it can properly communicate with the JNIOR. The JNIOR must communicate with the Christie Management Port. Below is an example of Christie and JNIOR IP configuration scheme. IP Solaria One:   192.168.1.110 / 255.255.255.0 (Management Port)  IP JNIOR:         192.168.1.115 / 255.255.255.0  

  IP QNAP Server:   192.168.100.100 / 255.255.255.0 (Saves content)   IP Solaria One NAS 1:   192.168.100.101 / 255.255.255.0 (Communicates to a Content Server e.g. QNAP, iOMEG)  IP Solaria ONE NAS 2:   192.168.200.101 / 255.255.255.0 (Communicates to another Solaria One to transfer content: trailer, features, etc.) 

  Screen Picture of the Management Port

JNIOR Application Note INTEG Process Group, Inc.

13

Screen Picture of the NAS Settings