News

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:

  1. Go to the DCP for the JNIOR
  2. Click on the Console tab
  3. Click ‘Start Session’
  4. Log in when prompted
  5. enter the netstat command
  6. 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:

  1. Go to the DCP for the JNIOR
  2. Click on the Console tab
  3. Click ‘Start Session’
  4. Log in when prompted
  5. Enter the cat protocol.log command

If you see the failed login then do the following:

  1. Go to the JNIOR Device Configuration on the Dolby IMS
  2. Remove the JNIOR device
  3. Reboot the Dolby IMS
  4. Add the JNIOR as a device but DO NOT enter the password
  5. 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 it is not resolved you can try to analyze the network capture or contact INTEG for additional support.

I hope this article helped you out. Please contact us to let us know!

There has been an update to the Update Project for OS 4.8.

  Series 3 All-In-One v4.8 [ Nov 11 2019, 252 KB, MD5: ef6a2613188b70725b155c9c026064b3 ]

Browsers no longer support Java Applets.  Therefore, the web files have been removed from the JNIOR in this update. This fixes flash space issues. The applets can still be loaded from within the JNIOR Support Tool.  To load the Applets, right click on the JNIOR  in the Beacon Tab.  Then go to Tools -> Open Classic Monitor, Configure, Control Application.

If the JNIOR series 4, models 410, 412 or 414, is not working with the GDC then check to make sure MODBUS is enabled. The built-in library for the JNIOR on the GDC server uses MODBUS.

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

Run Linux or Mac?

The JNIOR Support Tool has always been a Windows application. There have been ways to get the Support Tool to run on a Mac but I am not sure anyone has been successful on a Linux box.

Well work has begun to supply the features of the Support Tool in a cross-platform Java application. The thought will be to implement the Beacon and Snapshot functionality first and then the Update tab.

This project is in its infancy. Please let us know if we should continue working on it and prioritze it.

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.

2. Take a Snapshot of the series 3 JNIOR to wish to replace

3. Extract the Snapshot

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. Upload the configuration

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. 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.

6. Reboot the JNIOR again.

You new Series 4 should be running the Cinema application with the configuration and settings from your previous series 3 JNIOR.

  Grapher v4.0 [ Aug 22 2019, 783 KB, MD5: a7967fd9878171af565ff1faf677ae14 ]

Several changes affecting how you navigate in time.

Added the ability to change the configured duration view of the graph. Previously the default was a hard-coded 4 hours. Once you brought up the graph you could have used the mouse wheel to zoom out or zoom in. The graph would always load showing the past 4 hours.

In this version we removed the ability to zoom in and out using the mouse wheel. We also removed dragging the graph in the future or past using the mouse. This was done because it was noted that too often the mouse is accidentally being used to modify the graph view.

Since the mouse interaction was removed to zoom and pan, we added buttons below the graph the facilitate the ability to move forward and backward in time.

The fast step buttons move the graph forward or backward by the entire duration. If you are looking at today, as shown below, pressing the fast backwards button will show you yesterday. The single step buttons move by 1/4 the duration. Looking at 24 hours and pressing the single step buttons will move the graph by 6 hours.

Bruce and Kevin will be in Vegas at CinemaCon.  If you want to set-up an appointment to meet with us at the show email support@integpg.com or visit INTEG at booth number 2306A and meet the people actually responsible for the product hardware, firmware and application development.  We also want to meet you, answer your questions and to thank you for your ongoing business.

Follow INTEG on Twitter for updates: @integpg

See you in Vegas!

  Snap v2.3 [ Aug 02 2019, 1 MB, MD5: 602fd3bfef09d34772b6f368d15abc94 ]

We are excited to semi-release a project that was started 3 years ago but has been on the back burner until recently.

The Blockly implementation should provide greater control over your process and custom logic without the need to write code. While writing a Java application will provide the greatest level of customization, SNAP should be able to handle a large part of what you are trying to do. If there is something that SNAP does not do, but you want please feel free to contact us.

This application is in BETA. Changes will happen often. If you notice that we break some functionality please let us know.

Here is a simple exmaple of monitoring power on an input. This requires the JNIOR to be on a UPS, or using a JNIOR 412DMX with ride-through power supply. When input 2 changes it will send an email!

Here is an example logging two temperatures once a minute. Notice that the filename has date formatting involved. This will cause a new file to get created every day. Additional logic can be used to clean up files that are old so that the flash file system does not get full.

The integpg.com Website has been merged with jnior.com. We had to do this because our hosting provider was shutting down on August 1, 2019.

This will hopefully make the knowledge-base and news more visible.

We still have more work to do to bring you the best JNIOR information possible. If there are any comments, suggestions or if you have issues finding what you are looking for under the new format please contact us.

QSC released a plug-in to enable quick and easy integration with the INTEG JNIOR for the Q-SYSCore!  You can install the plug-in using the Q-SYS Designer Asset Manager.  This is a QSC Managed plug-in so the Author has a “Q” icon.

Please provide feedback so that INTEG and QSC can enhance the plug-in to give our users the best experience!

The plug-in requires JNIORs to be running JANOS 1.8 or greater.

Release Notes

We have released JANOS v1.8 which adds the JMP Protocol. The JANOS Management Protocol (JMP) is essentially the JSON message interface utilized by JANOS Websockets. The JMP Protocol has been exposed on its own TCP/IP port. This encloses the JSON messaging in a JSON array along with the JSON Object length making reception of the messages easy. The JMP Protocol will be used by the QSC Q-SYS JNIOR component.

  • Implements the JANOS Management Protocol JMP
  • Adds “Block” command to JSON interfaces
  • Web Server limits the effects of extremely slow connections.

  JANOS - UPD v1.8 [ Jun 17 2019, 874 KB, MD5: 11d1af6e80acfdcae637edb27e23a6f2 ]

  Series 4 All-In-One v1.8 [ Jun 27 2019, 2 MB, MD5: 2962d0d6fd2b9659e5e5956ed40549f9 ]

JANOS 1.7.1 (Released 3 December 2018)

Release Notes

  • Watchdog no longer causes reboot from foreground execution
  • REGEX Alternation '|' has been corrected to properly work in Group
  • Corrected NULL Pointer write issue when a Group which employs alternation appears at the start of a REGEX expression
  • Resolved message pump memory issue relating to process termination
  • Expand the channel range for setOutputRelay() from 0-11 to 0-15
  • Corrected network capture filtering when an IP address is to be excluded
  • Supports networks using Jumbo Frames
  • Eliminated assertion associated with improper use of '%n' in System.out.printf.

  JANOS - UPD v1.7.1 [ Dec 03 2018, 870 KB, MD5: 70bc5f3d4ec311786fe304c4e447595b ]

  Series 4 All-In-One v1.7.1 [ Dec 03 2018, 2 MB, MD5: b88a8d86302d867835a50e8f699edcad ]

JANOS 1.7 (Released 26 July 2018)

Release Notes

  • Added ability to load single CA Certificate to be supplied on TLS connection
  • Support TLS Client Certificate Verification on outgoing connections
  • Added legacy PKCS1 support for externally generated certificates
  • Corrected array issue with processing of deferred email transmissions
  • Corrected memory issue with TAB use on the Command Line

  Utility v3.0 [ Jun 14 2019, 1 MB, MD5: de6971f1462c6b8237b7096f92c90e4e ]

Utility version 3.0 has been released

  • + Added cycleevents.dat log for each input in flash/utility/storage/by-hours/
    The format of this line will be:
TIMESTAMP of cycle completion, TOTAL CYCLE TIME, HIGH TIME, LOW TIME

For example, the following file contains the cycle events ending in the 8am hour on July 23rd, 2019. Only the first 5 minutes are shown.

  Cinema.jar - Update Project v3.5 [ Jun 02 2019, 327 KB, MD5: 57a834f2c5ac177b7b19b6dec52350ce ]

  • Released June 02 2019

+ Added HTTP POST method to Macro Actions.

+ Added the ability the use HTTPS for GETs and POSTs

 

 

Cinema.jar 3.4.1

  Cinema.jar - Update Project v3.4.1 [ May 28 2019, 320 KB, MD5: 74f51ea7ccb40962eb2118bf16457c50 ]

  • Released May 28 2019

! Fixed a bug where the watchdog was no longer working. In the Cinema application crashed it would not be restarted.

 

 

Cinema.jar 3.4.0

  Cinema.jar - Update Project v3.4 [ May 16 2019, 320 KB, MD5: 63b627ede9c8a79710ddb3d7fd3ca852 ]

  • Released May 16 2019

+ 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.

  Cinema.jar - Update Project v3.4.1 [ May 28 2019, 320 KB, MD5: 74f51ea7ccb40962eb2118bf16457c50 ]

  • Released May 28 2019

! Fixed a bug where the watchdog was no longer working. In the Cinema application crashed it would not be restarted.

 

 

Cinema.jar 3.4.0

  Cinema.jar - Update Project v3.4 [ May 16 2019, 320 KB, MD5: 63b627ede9c8a79710ddb3d7fd3ca852 ]

  • Released May 16 2019

+ 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.

  Cinema.jar - Update Project v3.4 [ May 16 2019, 320 KB, MD5: 63b627ede9c8a79710ddb3d7fd3ca852 ]

  • Released May 16 2019

+ 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.

There is a known issue in Support Tool 7.8 for new installs. Click below to download 7.9. If you have trouble launching Support Tool 7.8 it is likely because the INTEG directory was not created at the root level of your drive. If you wish to stay with 7.8 you can create a C:\INTEG\JNIOR Support Tool directory and try to launch the Support Tool again. Sorry for the inconvenience.

Check the Support Tool News Section to get the latest update!

  • Fixed a bug that stopped the serial port from being read if an Ethernet connection was disconnected. This appears to be a bug that was introduced in version 5.3.
  • Moved the serial configuration to take advantage of the AUXSerial and COMSerial settings that JANOS uses.

Release Date: May 10 2019

  Serial to Ethernet 6.0 - Update Project v6.0 [ May 17 2019, 41 KB, MD5: d06bd5279d05546652b56faf427cc676 ]

  Serial To Ethernet 6.0 - Application File v6.0 [ May 14 2019, 44 KB, MD5: fd897cf50763a56e7f4828dac566b933 ]