Author Archives for Kevin Cloutier

















  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.

MODBUS client is not able to connect to the JNIOR

The MODBUS server running on the JNIOR is a separate application from the Operating System. It does not run by default when the JNIOR is shipped. It is installed by default. It must be activated by the end user before the the MODBUS connection can be successful.

To activate it go to the DCP, click on the Configuration tab. Half way down the left side click on Applications. You will see a list of applications that are loaded on the JNIOR. Check the box next to Modbus Server. This will tell the JNIOR to run the application when the JNIOR boots up. You will need to reboot the JNIOR at this point to get the MODBUS Server to start.

To verify that the MODBUS server is running we can list the listening network sockets using the netstat command.

Lastly, you can change a few configuration parameters for the MODBUS server under the registry tab.

Port 502 is the default MODBUS port. Most likely this will NOT need to be changed. The Timeout setting is the number of milliseconds to wait for a MODBUS client to poll the server. If a request is not made within this amount of time then the JNIOR will close the connection. If any configuration needs to be changed it will probably be the Login setting. Not very many MODBUS clients implement a login. If they dont log in then you will see the following in the Modbus Server log…

Setting the Login key to false will allow this device to connect successfully.

The problem: You get the following screen when trying to go to the DCP or any web page on the JNIOR.

In this image we tried to go to the IP Address of the JNIOR.  This should present us with the DCP web page.  In this case we are presented with the “Page not found” response page.

This means that the file cannot be found in the filesystem for this page resource.

To troubleshoot this we need to look at the filesystem.  Since the DCP is not available we need to use FTP or a telnet session.

Using FTP

Open Windows Explorer. In the address bar type ftp://IP ADDRESS. You might see the message that Windows Explorer cannot access your folder.

Most likely this is because you need to provide credentials. To do that you need to right click in the white-space in the window and select Login As…

Once you log in navigate to the flash directory.

If the the DCP or default web page is missing then all of the following must be met:

  • www.zip is missing
  • public.zip is missing
  • www/ directory is missing or there is not an index.php file in the www/ directory
  • public/ directory is missing or there is not an index.php file in the public/ directory

Using Telnet

We can use Telnet to look at the filesystem as well. To do this, open your favorite Telnet application. Make a connection to the JNIOR. Log in. You will then use either the dir command or the ls command. Both commands are the same and will list the directory contents.

Use the command of your choice, whichever command is easier to remember, and add “flash” as a parameter. This wil cause the command to list the contents of the flash directory. If the the DCP or default web page is missing then all of the following must be met:

  • www.zip is missing
  • public.zip is missing
  • www/ directory is missing or there is not an index.php file in the www/ directory
  • public/ directory is missing or there is not an index.php file in the public/ directory

Security is a good thing. It is also hard. The IpConfig/Allow registry key will help you filter the connections permitted by the JNIOR.

The documentation for the use of the IpConfig/Allow key is as follows…

The IpConfig/Allow Registry key when present defines specific IP addresses and IP address subnets that are to be granted access to the JNIOR. All others are ignored. If undefined then all routable clients have access. For example, to restrict access only to your IP address (say 50.197.34.73) and your entire local subnet (10.0.0.x with mask 255.255.255.0) you would define the following:

reg IpConfig/Allow = “10.0.0.0/24, 50.197.34.73” 

In this case you, using that specific address, and everyone on the local subnet would be able to see the JNIOR and access its functions while everyone else is blocked.

This therefore is a list of IP address/subnet specifications of the form:

nnn.nnn.nnn.nnn/dd 

Here the 4 octet IP address for IPv4 is specified and ‘/dd’ if present indicates the number of bits from the left that must match. If the ‘/dd’ parameter is omitted it is the same as specifying ‘/32’ and as if you used a subnet mask of 255.255.255.255. In other words that IP address must match in its entirety.

Changes to this configuration setting take effect on reboot.

The IpConfig/Allow registry key can be powerful to help secure your JNIOR.  It can successfully thwart unauthorized access and prevent DOS attacks.

The danger comes in when the registry key is mis-configured. It can be a typo or not fully configured, something simple, but when this happens it can prevent legitimate attempts to access the unit.

If this happens a USB-to-Serial cable is needed to access the unit via the RS-232 port. Make sure to use the correct serial settings of 115200, 8 data bits, 1 stop bit and no parity. Once connected you can issue the reg command.

Above you can see that the IpConfig/Allow key is set for 10.0.0.0/24. This states that the first 24 bits of the address must match for a network connection to be accepted. If, for some reason, this was mistyped then legitimate connections would not be allowed. This would basically render the network port useless. The user might not have noticed what the error was.

Using the Serial to USB cable is the only way to access the unit. The key can then either be fixed or removed to regain access over the network.

If you experience issues with your Dolby IMS Cinema Server connecting to or executing commands on the JNIOR you may need to follow the procedure below. There are two issues that I have seen.

A Dolby may not even try to connect to a JNIOR when it should.

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

If there is not then remove the JNIOR device, reboot, and reconnect.

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

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. Reenter the JNIOR password
  3. Reboot the Dolby IMS

You can now re-test the JNIOR connection to see if this is resolved.

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!

It is always a good idea to take backups of devices. Personal pictures, work documents, and even the JNIOR. There is another aspect of taking a backup of the JNIOR that can prove very useful. That is that a backup can become an update project. The update project can then be used to restore the same unit to a point in time or to clone a JNIOR. This means that you can take a backup and then make one or more other JNIORs appear and behave exactly the same.

Where can I find the backup feature?

The Backup feature is under the Snapshot tab.

How is a Backup different than a Snapshot?

The backup differs from a snapshot in a two ways. The most important difference is that an update project will be created. The other difference is that log files are not captured. A snapshot is used to capture log files to submit to INTEG to help debug any issue you may be having.

The Backup procedure

Click ‘Take Backup’ in the Snapshot Tab

You will be shown a prompt that lets you know what is about to happen and to make sure you want to continue.

Clicking ‘Yes’ will provide you with a dialog allowing you to select which unit you want to backup.

When the backup has finished you will be prompted for a name. Give the backup a meaningful name. That name might be the unit name followed by a date string or it may be a name describing the job function that the JNIOR is performing.

Lastly you will be prompted to open the Backup or Update Project in the Update Tab.

If you click ‘No’, you can open the Update Project at any future point in time. Just go to the Update tab and click ‘open project’ and select the backup.

The following is the backup update project that was created.

That, is the backup procedure. Congratulations, you can now use this backup to restore this unit back to this point in time or use it to configure other JNIORs to perform the same task.

  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.

When we want to reboot the JNIOR from our Java application we call the command line reboot command.  To call to the command line we use the ConsoleProcess class.  Since there will not be any user to confirm the reboot we need to use the -f command to force the reboot.

        try {
ConsoleProcess consoleProcess = new ConsoleProcess("reboot -f");
consoleProcess.waitPrompt();
} catch (Exception ex) {
throw new IOException("Error rebooting").initCause(ex);
}

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.

Sometimes you need to find out what the IP Address of the JNIOR is that is sitting on your network.  Sometimes someone else set it up and are no longer working with you or maybe you programmed it but years have passed and you haven’t needed to access the JNIOR because it is performing its job and no attention has been needed.

There are a couple of different ways to find out the IP Address.

By far the easiest way to find the JNIOR IP Address is the use the JNIOR Support Tool.  The JNIOR Support Tool only works on Windows systems.  http://jnior.com/category/news/support-tool/ will have links to the latest, as well as previous, versions of the JNIOR Support Tool.  Once loaded and started you will be presented with the Beacon tab.  The Beacon tab will show all the JNIORs that are present on your LOCAL network that have reported.  When the Support Tool launches a broadcast is sent out asking for all the JNIORs to report their information.  Some network configurations can either help or hinder this operation.  In most cases it works as intended.  Here is a picture of the Beacon screen.  If you have more than one JNIOR shown you can use the Serial Number of the JNIOR to identify which row corresponds to your unit or you can use the identify feature to pulsate the amber LED next to the power indicator.  To perform that function you can right click on a row and select either Query | Identify or Configure | Identify from the menu.

The other way to determine the IP Address of a unit is to directly connect a serial cable to the RS-232 port.  Computers do not come with serial ports anymore so a USB to Serial adapter will be needed.  You can find them at Amazon.  Once the cable is connected, select your favorite terminal application or use the Command Line application included with the Support Tool.  The serial settings must be 115200, 8, 1, none for the baud rate, data bits, stop bits and parity respectively.  Now that the connection is set up you can press enter and the login prompt will be presented.  The default credentials are username: jnior and password : jnior.  You can now enter ipconfig to see the current network setup.

 

 

 

 

 

 

 

 

Lastly, for those who know Morse code, you can unplug the network cable and the status LED will flash Morse code representing the value of the last octet.  You must know the first 3 octets of your network.

    0 --- --- --- --- ---
    1 - --- --- --- ---
    2 - - --- --- ---
    3 - - - --- ---
    4 - - - - ---
    5 - - - - -
    6 --- - - - -
    7 --- --- - - -
    8 --- --- --- - -
    9 --- --- --- --- -

  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!