When using the Cinema application, you’ll want the JNIOR to be able to send/receive commands to control or be controlled by external devices. In the registry of the JNIOR, Cinema’s registry contains the CinemaServerClient and PreshowClient registries. These are what can be configured to establish those connections to external devices.
While accessing the JNIOR WebUI when Cinema is installed, you can access the AppData/Cinema/CinemaServerClient or AppData/Cinema/Client registry folders to configure the connections made using Cinema. The PreshowClient and CinemaServerClient are connections made to either a Preshow System or Cinema Server through TCP or Serially that allow control of outputs, I/O feedback, and the ability to interact with various devices using macros.
Inside both registry folders are multiple registry keys. The TcpPort registry key is where you can set the port number for an Ethernet connection to other devices. (We recommend using the port number 9600). For serial connections, you need to set the Method key to serial and the SerialCommandsEnabled key to true. You’ll then need to go to the AppData/Cinema/X/Serial (X is for CinemaServerClient or Client) and set the serial connection to whatever serial setting you want the JNIOR and your external Device to connect on. NOTE: You cannot have both a Preshow Client and Cinema Server connection at the same time.
When using the control panel, you might want to have the switches trigger macros you created in the support tool. This post will explain how to do just that. To start you’ll need to have created a macro in the support tool. If you haven’t done that already and don’t know how, here is a post on how to do it. You’ll also need to have installed cinema on your JNIOR as well.
Next, you’ll want to makes sure that your control panel is properly connected. You can check what external devices have been connected to the sensor port by opening the JNIOR’s WebUI, going to the Console tab, and after logging in entering “extern” into the console. If you have left-over information from previous external devices that you’d wish to get rid of, then you can remove devices no longer present by typing the extern -r command.
Once you have your macros created and published to a JNIOR along with your control panel being connected, you can now hook up the macros to the control panel using the JNIOR’s registry. Open your JNIOR’s WebUI and go to the registry tab. Once there, you’ll then go to AppData/Cinema/Panel.
Once here, you’ll simply enter the macro name on whichever switch trigger you want to activate the command. Now the macros you created will send a command when you hit a switch on the control panel.
As long as the device you are sending to can create TCP or serial connections, the JNIOR should be able to send commands to it.
If you are starting from scratch with a JNIOR, you’ll want to download the JNIOR Support Tool. This application allows you to update JNIOR’s with INTEG software that you’ll need to let you send the text command.
Once you’ve downloaded the JNIOR Support Tool, you’ll need to download two update projects from our site and update them to your JNIOR. The first update project is the Series 4 All-In-One update project. Its recommended for any new Series 4 JNIOR, as the update project gives JNIORs the most recent OS, along with some basic applications. The second update project is the Cinema update project. This is the application you’ll use to execute a macro, which will send a command from the JNIOR to a device.
To update your JNIOR with an update project, here is a link to a post on our site that shows how to install Cinema. NOTE: Though the post shows how to install Cinema, its recommended you install the Series 4 All-In-One first, using the steps in that post.
Once the update projects have been published to your JNIOR, we’ll now need to create a device in the support tool to send to. In the support tool, you’ll go to the device tab and select add. You can select the device and rename it. After that you’ll now configure the settings of the device so we can send macros to it. To start you’ll select your device type, and if you see the device you want to send to there you’ll select it. If not you’ll select Raw Ethernet for a TCP connection or Raw Serial for a serial connection. You’ll then set the rest of the device configuration according to the device’s TCP or serial settings.
Once you finish setting the device information, you’ll then want to save the device file by clicking the Save As button. After that you’ll then publish the file to the JNIOR you are using by clicking the Publish to JNIOR button.
After you’ve done that, we’ll now create the macro that will be sent to the device that will contain the text command. Going back to the support tool, you’ll go to the macro tab.
The first thing we’ll want to do here is click the “Link Devices” button at the top. Here we’ll select the device file we just created, so we can reference it in our action for the macro we are going to create.
After completing that, at the bottom left corner of the macro view and you’ll select add/macro. A new macro should populate the macro view, and you can then click on it and rename it. I’m going to name it ExampleMacro.
Once you’ve done that you’ll now go to the action view and select the add button there. A new action should appear in the action view. You can rename this if you’d like, and then we’ll want to select the device we previously created in the Support Tool to send to. Lastly, in the data field you’ll want to enter the text command you wish to send to the device. If you are using a Raw Serial/Raw Ethernet device, make sure you include the termination string at the end of your text command for the device you are sending to.
Once that is finished, make sure you add the action we created to the macro we created. You do this by selecting the macro, then the action, followed by the arrow between the macro and action view.
Lastly, like we did with the device file, we’ll save this using the Save As button, followed by publishing it to the correct JNIOR using the Publish to JNIOR button.
Now that the JNIOR has a macro we created that will send the text command to your specified device, now all we need to do is configure the JNIOR so that it will send this macro when DIN1 goes ON. First thing we’ll want to do is go to the JNIOR Web UI by selecting the JNIOR in the beacon tab of the support tool. There you’ll right click it, and go to tools/open web page. Once on the JNIOR web page, you’ll go to the registry tab. On the registry tab, you’ll select AppData/Cinema/Triggers. Once there, you’ll go to Input1Macro and enter the name of the macro we created in the support tool. We named it ExampleMacro, but if you named it something different you’ll enter that name here. This should set the JNIOR so that when DIN1 on the JNIOR goes ON, the macro will activate.
The Tasker application has been made to handle lots of different types of functionality. This post will go into looking at the Set Variable action and then a logic example using the set variable to send fire alarm macros to different devices. Doing this example requires the environmental or temperature sensor to be completed.
The Set Variable Action
The Set Variable Action allows you to create a variable in the first value field of the action, and then assign it a value in the second value field. This is useful when using other control structure actions, such as loops or if blocks.
Fire Alarm Example
Note: Values in this example will most likely differ from your.
In this Example, before we create the Fire Alarm Task, we need to create the devices that will receive the macro we send for the fire alarm, like shown above. You’ll also need to the have the Cinema application updated to your JNIOR. To start, go to the device tab and click the “Add Device” button. Add as many Devices as you have JNIORs you plan to send a Fire Alarm macro to. Each device you’ll enter its IP address, and TCP Port number from the Cinema Server Client Registry Key. The Registry Key is under AppData/Cinema/CinemaServerClient/TcpPort in the registry tab of the JNIOR’s webpage.
After creating the devices to send macros to, you’ll start creating the task. It starts with the Set Variable actions. These actions are used to define the values of two temperatures received from a temperature sensor or environmental sensor, and the variable used to know when to end the Task. We define the two Temp variables to values our temperature or environmental sensors are picking up, and the other variable will be set to true as our conditional until the macros get sent. Once these values are defined, a while loop is added to the task. This will check if the conditional of the variable we created is true, which is how we set it so that it will always be looping. After that, we add an if block and set the conditional of it. This is to determine if the movie theater’s screen room is a lot more hotter then the rest of the movie theater, indicating a possible fire. When the temperature difference is above 20 degrees (indicating a possible fire), using as many TCP send actions for devices you have, it sends to those JNIORs to run their FireAlarm macros. It also sets the conditional for the while loop to false, so the task no longer loops, and ends.
With this, you should have a task that constantly monitors the temperatures of two temperature/environmental sensors, and when the difference between them is greater then 20, sends out the fire alarm macros and ends the task.
Sometimes you may want something to occur at a specific time of day or sometimes you may want something to occur with certain events during the day. The “events” in this case are the Sunrise and Sunset events. These events occur at different times during the day based on the time of year and your geographic location. Tasker grabs the location from the JNIOR registry, and uses it to calculate the time of sunrise and sunset for that day.
We had written a custom application called the SunEquation Application to accomplish the following before implementing the logic in Tasker. You may ask, “What is the SunEquation application and can Tasker handle the same logic?” The answer is that Tasker is a heavyweight application that uses more processing power than a simple custom application that was designed to do one thing. The SunEquation application was written for someone that was already running two other applications and the addition of Tasker might slow those other applications down. Specifically the DMX application is sensitive to performance and that application is one of the two applications that were in use.
Below is an example to send commands to the Cinema Server Client in Cinema to run macros. This requires having the support tool downloaded along with the applications Tasker and Cinema updated on to your JNIOR. There are several steps that will need to be configured to get this to work.
Create Macros in the Support Tool that you wish to have run at Sunrise and Sunset.
Create a Task that will perform the action of requesting that the macros get run in Cinema. The action in these Tasks will depend on a Device object that will need to be created as well.
Create Schedules that will execute the Tasks based on Sunrise and Sunset.
Create the Macros
To start, we need to create the macros in the support tool that will be run in Cinema as requested by Tasker. Opening the Support tool, under the macro tab, we can create a macro for sunrise and sunset, and we’ll rename them to that as well, adding whatever actions the macros should perform. This then needs to be published to the JNIOR.
Create a Device
After creating the macros, we need to create a device in Tasker. We first need to create a new workspace using the File Drop-Down before creating a device. After that we’ll go to the device tab in Tasker, and click on the “Add Device” button. This will add a device in Tasker. Now all you need to do is set the IP Address of the JNIOR and the Tcp port number to the same value as the Cinema Server Client port number registry key under AppData/Cinema/CinemaServerClient.
This is an example picture, the values required differ between JNIORs
Create Tasks
The next thing needed to have the macro request sent to the Cinema application is to create TCP send tasks. To create a task you go to the Task tab in Tasker, and select “Add Task”. Once you’ve named the task, you’ll click on the task and select “Add Action”. This will make the action dialog box appear, which contains all the actions you can make your task perform. There you’ll select the TCP Send action. You will then add the device that was just created, and the message should be “run” followed by the name of the macro that was created in the support tool. The macro names also have an \r\n on the end of them to signal where the end of the command is when its being sent. Since we created two macros in the support tool for sunrise and sunset, we’ll create two tasks for them, one for sunrise, and one for sunset. Both of these tasks will be using the same device.
Create a Schedule
To setup macros to run at sunrise and sunset, you’ll now want to go to the schedule tab of the Tasker application. Once you add a schedule, name it, and select the task to run in that schedule, you’ll want to click on “Add Rule”button . As in the example below, since we previously created two tasks for sunrise and sunset, we’ll want two schedules for those tasks, one for sunrise and one for sunset.
Once you’ve clicked “Add Rule”, the Rule Dialog box will open. Here we’ll want to select the Schedule Type option, which will present 4 options. Two of those options will be Sunrise and Sunset.
After selecting the sunrise option for the sunrise task, and the sunset option for the sunset task, those tasks will now run at those times.
Once this is all done, whenever it is sunrise/sunset for the day, Tasker will send commands to Cinema that will execute the macros created in the support tool.
Analog Presets is an application that lets you control and automate expansion modules such as 4-20ma Module, the 10v Module, or the 3 channel LED module. To get started, you’ll want to download the analog presets application from the all downloads page on integpg.com. After updating your JNIOR with the application, you’ll want to go to the URL containing the IP of your JNIOR with /analogpresets after it to access the application on your JNIOR. Here you can add levels containing different commands you want to create for your modules. You can name the command, what you want it to do, how long it should last, and if you want other commands to start once it starts or finishes. You can also use these as macros by defining a port number and termination string on the general tab.
To send a macro to the analog presets application, first we’ll configure the analog presets application. Here is an example using the 3 Channel LED Dimmer. We’ll start by adding a new level at the bottom middle of the first tab in analog presets, and giving it a name. (For this example we named ours MacroTest) Once that is added, we’ll want to go to setting level and add the brightness of each output we want set. For this example, since the 3 Channel LED Dimmer has 3 outputs, we’ll set each of them to 100 by typing in the field 100,100,100. We’ll also want to go the 3 Channel LED Output Channel field and type 1,2,3 to represent the channels we want to set the brightness of. If in the setting level field we set the brightness to 50,75,100, and the 3 Channel LED Output Channel was still 1,2,3, then channel 1’s brightness would 50, 2’s would be 75, and 3’s would be 100. For this example though, we’ll set them all to 100. If you have the 3 Channel LED Dimmer plugged into your JNIOR and the 3 Channel LED Output Channel field is still grayed out, then reboot your JNIOR and it then should be configurable.
We’ll then click on the General tab of the Analog Presets application. Here we can set the TCP port that the macro will send to. (In this example we have 9700) Make sure the Termination string is \r\n.
After that you’ll need the cinema application. You’ll download the Cinema.jar application and using the update tab in the support tool load it onto your JNIOR. Once its on your JNIOR, we’ll want to go to the support tool and create a device in the device tab. We need to do this so that the macro will know what information to send. At the bottom of the Device tab, click add Device. From there, we’ll want to name our device (You can name it anything), set the device type to RAW ETHERNET, set the IP Address to the JNIOR you are using, and the port number to the one you set above in the analog presets application. (Mine for this example is 9700).
Once you have set this up, you’ll want to click “publish to JNIOR” and it will prompt you to save the device configuration as a file. Once this is done, select the JNIOR you are using as the one to publish to. Once its published, you’ll then go to the Macro tab. The first thing we’ll do here is click “link devices”, and select the device file we previously created. After this we will go to the Action view and add a new action. Here you’ll name your action (It can have any name), the device we’ll set the to the one we previously created, the action should be send, and the data should be formatted as follows:
trigger “Name of level from analog presets application”\r\n.
Once this is done, we will then add a Macro in the Macro view. First we name the macro and then we can add the action to this macro, by selecting the Macro we created, the action we created, and then clicking <- button.
Once you have done this, you’ll want to click “publish to JNIOR” like we did previously for the device tab, and create a macro file. Once that is created select the JNIOR you are using as the one to publish to. Now to test this, we’ll want to go to the tools tab of the support tool and click command line.
Once the command line is open, we need to configure the command line to create the right connection, at the bottom of the command line we’ll set the values to our IP and then the TcpPort value in our JNIOR’s Registry. You’d find this by opening the JNIOR’s web page in beacon, and then after going to the registry tab look for the path: AppData/Cinema/CinemaServerClient/TcpPort
Make sure that the value is not -1 like it is above. If it is, change that registry key. (An example value to change it to is 5000). Once you find this value, set it as the port number next to the IP address at the bottom your command line. The IP address should be the one your JNIOR has.
Also, go the options drop down list and check each option.
Now all you should have to do is click the connect button at the bottom right and type:
run “Name of macro from support tool”
This will run the macro you wanted to send to the 3 Channel LED Dimmer!
Sometimes an application wont run on a JNIOR Series 3 unit. This issue may be due to “insufficient heap“.
This error message means that there was not enough contiguous space in “heap” or the SRAM memory for the application. The application must find contiguous memory of at least the file size of the application. Once the application finds that space it will stay in that same space until the application is updated. The memory can become fragmented over time since the SRAM is used for application executables, application memory and the root file system.
Most likely this error condition will occur after updating to a new version of an application. If the new application is larger than the old application it cannot occupy the same contiguous block in memory. It must find a new contiguous block. That space may not be available depending on the fragmentation of the memory. Even if there is a contiguous block of memory large enough when the file is updated, it still might give you an “insufficient heap” error. This might happen because until its run as an executable, the file doesn’t know it needs to be stored as contiguous space and fragment its memory anyways, which would then cause the error.
The fragmentation is caused by file blocks that have become scattered throughout memory over time. To clear up the fragmentation we could delete a file at a time until a contiguous block has become available. This would be a very slow approach. You would not know which file gives you the best chance of finding a contiguous block. Since the root of the file system contains mostly log files we can just clear the heap on a reboot. In order to that we execute the reboot -a command.
What about my cinema devices and macros files?
The cinema files are automatically backed up to flash/cinema_backup. This location is not affected by the reboot -a. The cinema files will be restored next time cinema runs.
If you experience issues with your Dolby IMS2000 Cinema Server connecting to or executing commands on the JNIOR you may need to follow one of the procedures below. There are two issues that I have seen.
Dolby has resolved the issue for the IMS3000.
A Dolby may not even try to connect to a JNIOR when it should.
Make sure you have rebooted the Dolby IMS after adding the JNIOR as a device.
To determine if this is the issue:
Go to the DCP for the JNIOR
Click on the Console tab
Click ‘Start Session’
Log in when prompted
enter the netstat command
There should be a connection to 9200 with the Dolby Server IP Address for the Remote IP
The Dolby is connected but nothing happens on the JNIOR when the Dolby sends the command.
When Dolby tries to connect to the JNIOR it may not be able to log in to the JNIOR due to a bad password. The highlighted bytes below are corrupted.
The bytes should represent the password like this…
The previous images are screenshots for the WireShark application when analyzing a network capture. This capture is included in a JNIOR Support Tool Snapshot. I have been told by Dolby that this is likely due to the browser auto-fill.
To determine if this is the issue you should check the protocol.log on the JNIOR
To do that:
Go to the DCP for the JNIOR
Click on the Console tab
Click ‘Start Session’
Log in when prompted
Enter the cat protocol.log command
If you see the failed login then do the following:
Go to the JNIOR Device Configuration on the Dolby IMS
Remove the JNIOR device
Reboot the Dolby IMS
Add the JNIOR as a device but DO NOT enter the password
Reboot the Dolby IMS
You can now re-test the JNIOR connection to see if this is resolved.
If it is not resolved then make sure your browser is not using auto-fill for the site. The procedure differs per browser. Follow one of the links below for your browser.
If the JNIOR series 4, models 410, 412 or 414, is not working with the GDC Cinema Server then check to make sure MODBUS is enabled. The built-in library for the JNIOR on the GDC server uses MODBUS.
MODBUS communicates on port 502.
The series 3 enabled the MODBUS server by default. The MODBUS server is an optional application that needs to be enabled on the series 4. You can look at the following links for more information
The iBoot device from dataprobe is a Web Enabled Power Switch. We can command the devices by issuing HTTP Requests. To do this we will add an iBoot device to the Devices file and add “Power On” and “Power Off” actions to the Macro file. We then associate the actions with macros. We might want separate macros for power on, power off and power cycle.
To create the iBoot device in the devices file go to the Devices tab in the JNIOR Support Tool. Then in the lower left click ‘Add’. Then fill out the information as follows. This device can be added to an existing devices file or a new one. We are going to use the HTTP Request device type.
Then click over to the Macro tab and click on Link Devices. This will link the devices file so that the configured devices are available to create macro actions.
Now click ‘Add’ below the Macro Action View. You can rename the action. Click in the Device column for the new Action and scroll to the bottom to select your linked device. Select the iBoot device. Now click on Action and select “GET”. In the data field enter the resource portion of the URL””. It should look like this… Remember to enter the username and password if needed.
You can now add the action to any macro by selecting both the macro you wish to add it to and the new iBoot action.s Then use the <- button between the two views like this…
We can command the Nagra myCinema player to start playing its content. To do this we will add a myCinema device to the Devices file and a “Play” action to the Macro file. We then associate the “Play” Action with a macro. It’s that easy!
To create the myCinema device in the devices file go to the Devices tab in the JNIOR Support Tool. Then in the lower left click ‘Add’. Then fill out the information as follows. This device can be added to an existing devices file or a new one. We are going to use a RAW ETHERNET device so that we can send any command we want. The command is a simple text string.
Then click over to the Macro tab and click on Link Devices. This will link the devices file so that the configured devices are available to create macro actions. Now click ‘Add’ below the Macro Action View. You can rename the action. Click in the Device column for the new Action and scroll to the bottom to select your linked device. Select the myCinema device. Now click on Action and select Send. In the data field enter “play”. It should look like this…
You can now add the action to any macro by selecting both the macro you wish to add it to and the new myCinema action. Then use the <- button between the two views like this…
The Cinema application for the JNIOR enhances the JNIOR capabilities. While the JNIOR can be used in its most basic form, the Cinema application provides the ability to execute macros, sequence of actions.
The Cinema application does not ship preinstalled. You MUST obtain the application from our website. There is a download on the website that will be opened in the JNIOR Support Tool and published to the JNIOR. This is called an Update Project.
Here are links to latest versions of the JNIOR Support Tool and the Cinema application.
After installing both the JNIOR Support Tool and the Cinema Update Project, you’ll want to open the Support Tool and click on the Update Tab. Once there, the first thing you’ll want to do is select the Open Project button, and select the Cinema Update Project you just downloaded. When you open the Cinema Update Project in the Support Tool you will see the following.
Click Publish and select the JNIOR you want to update. Once the update is complete the JNIOR will have rebooted and the application will be ready to configure. Configuration is largely dependent on what you are trying to do.
Within the Support Tool you can configure devices and macros. Devices are outbound connections from the Cinema application. For example, a projector, sound processor, or lighting system. Those devices can be serial or Ethernet. We have not implemented very many devices but the ones that are implemented satisfy a very large majority of the installations. If you need a device that is not implemented, you can use the “Raw Serial” or “Raw Ethernet” device. This will allow you to send commands that you define to those devices. Even if you pick a device that we have implemented, you may need to add a new command. You can use the Send action and define the bytes that need to be sent.
You can use the Cinema application to execute DMX scripts. Those scripts can be on the same JNIOR or on another JNIOR. Both situations require making a TCP or Raw Ethernet connection to port 10000.
To execute a script once you will send go SCRIPTNAME\r\n
To execute a script a certain number of times you will send the same command but with a repeat parameter. For example, to execute 3 times we would send go SCRIPTNAME -r 3\r\n
To execute a script and have it repeat forever, until you abort it or reboot the JNIOR, you will send the -f parameter. For example, go SCRIPTNAME -f\r\n
Create a DMX device to use in the Macro
Create a Macro to call a DMX script with the Device we just created
As of Cinema version 2.9 you can use the scheduling in Cinema.jar to schedule macros daily, weekly or monthly.
When Cinema.jar is installed and executed for the first time it will create 3 default keys. They will look like this in the registry.
The configuration is a multi-part registry key. There are three parts. The type, the time of day, and the macro to execute.
Here are examples of the different scheduling types
Daily
You can define a macro to execute at a specific time every day. To do this we use the daily type. An example of executing a macro daily at 3:30pm with the name test would be:
daily, 15:30, test
Weekly
You can define a macro to execute on certain days of the week. To do this we use the 2 character day abbreviations in place of the type field. The 2 character day abbreviations are Su, Mo, Tu, We, Th, Fr and Sa. An example of executing a macro every day of the week at 3:30pm with the name test would be:
sumotuwethfrsa, 15:30, test
Monthly
Macros can be defined to execute on a certain date of the month, every month. To do this we use the monthly type followed the day of the month inside the parenthesis. An example of executing a macro with the name test would be:
montly(15), 15:30, test
You can also select to only execute the macro on certain months. Do do this we use 3 character month abbreviations. Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov and Dec. Only one month can be selected at a time.
There are many reasons to upgrade a series 3 JNIOR to a series 4. While we believe the experience and reliability are much better with the newer hardware and software we understand that in most cases the “if it isn’t broke, don’t fix it” rule applies.
When you are ready, use the following steps to help the transition go smoothly.
Can I just perform a backup from the series 3 and restore onto the series 4?
You can perform a backup and restore. BUT, this will copy over the cinema.jnior application. This file will not run on the series 4. There is a specific cinema file, cinema.JAR, that will run on the series 4.
If the cinema.jnior file gets copied over there will only be one small issue. A restore will set that file to run on boot. Every time the JNIOR boots it will throw an error regarding the cinema.jnior file being there and being the incorrect format.
The procedure
1. Update the Series 4 Operating System
Make sure the new series 4 JNIOR’s Operating System and Cinema application are up to date. You can find those applications on the All Downloads page.
The Cinema update will ensure that the Cinema application is present that will run on the Series 4. The version of the application that is loaded on the Series 3 will NOT run on the Series 4.
Open the Snapshot zip file and extract the macro file, devices file and flash/jnior.ini file.
4. Upload the macro and devices files to the destination series 4 JNIOR
5. Edit the jnior.ini file
The configuration is stored in the flash/jnior.ini file. Before you upload it we will need to remove two sections from the file. We will remove the [ipConfig] section so that the IP Address remains and the [run] section so that cinema.jnior does not try to start on boot.
6. Upload the updated jnior.ini file
To upload the file you have two options. You can use your favorite FTP client or use the DCP. If you use the DCP you will want to go to the Folders Tab. From there you can simply drag and drop your ini file to the temp/ folder. I recommend the temp/ folder for the upload so the file gets cleaned up after a reboot.
7. Ingesting the new configuration
To ingest the new configuration we will run the reg -i command from a command-line connection. Again you have multiple options for making the command-line connection. You can use an application like Putty, The JNIOR Command Line tool that is part of the JNIOR Support Tool or the Console tab in the DCP. If you use the DCP your command will look like this.
8. Enable MODBUS Server (If you are using a GDC Cinema Server)
The MODBUS server ran by default in the series 3 operating system. It is a separate application on the Series 4 that must be enabled to provide MODBUS connectivity.
You can enable MODBUS via the DCP. http://JNIOR_IP_ADDRESS in your browser.
9. Reboot the JNIOR again.
Your new Series 4 should be running the Cinema application with the configuration and settings from your previous series 3 JNIOR.
+ Allow you to query the temperature sensor via a HTTP Request. A JSON representation of the device will be returned.
As of now the only available devices are Type28 and Type7E...
Type28 is the temperature probe and Type7E is the environmental sensor.
To enable this you will need to set the AppData/Cinema/WebServer/Port registry key. The JNIOR will need to be rebooted after this key has been changed. In this example I chose 8081. Port 80 or 443 is normally the default web server port. This web server port is an additional web server that cinema is hosting to handle these types of requests.
MODBUS is a communications protocol used to communicate between a master and a slave or several slaves. The JNIOR implements MODBUS TCP. MODBUS TCP is the form for this protocol over the Ethernet network. The JNIOR acts as a slave by accepting requests and forming responses. Since Ethernet networks call devices clients or servers, the JNIOR is a server. Therefore the JNIOR has an application called MODBUS Server to handle the MODBUS TCP requests.
The MODBUS Server application is NOT enabled by default. It must be enabled before MODBUS masters or clients can send requests to the JNIOR. Once enabled the JNIOR will begin listening to TCP connections on port 502.
To enable the MODBUS Server you should go to the DCP (Dynamic Configuration Page).
Then navigate to the ‘Configuration’ tab.
Now, select ‘Applications’ halfway down the left side. Make sure the MODBUS Server application is checked
Reboot the JNIOR.
You can then optionally make a telnet connection to verify. The ps command to make sure the modbusserver application is running. Then you can use the netstat command to see that port 502 is listening.
@integpg