The page cannot be found

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
By | On August 20, 2019 9:19 am | No Comments |

Cinema.jar 3.6
Name Version Release Date Size MD5
Cinema.jar - Update Project v3.6 Aug 14 2019 334.6 KB d96d4ae9b9adc4f0b8cdaf9bd87518f3

+ Adding web handlers for getDevice without a device for internal io getAll.

Cinema.jar 3.5 June 2, 2019

Name Version Release Date Size MD5
Cinema.jar - Update Project v3.5 Jun 02 2019 327.0 KB 57a834f2c5ac177b7b19b6dec52350ce

+ Added HTTP POST method to Macro Actions.

+ Added the ability the use HTTPS for GETs and POSTs

Cinema.jar 3.4.1 May 29, 2019

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

  • Released May 28 2019

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

 

Cinema.jar 3.4.0 May 16, 2019

  Cinema.jar - Update Project v3.4 [ May 16 2019, 320.36 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.

By | On August 14, 2019 3:27 pm | No Comments |

IpConfig/Allow

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.

By | On August 14, 2019 8:54 am | No Comments |

The dangers of IpConfig/Allow

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.

By | On August 13, 2019 2:25 pm | No Comments |

JNIOR Support Tool Backup

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

Take Backup Button

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

Backup Confirm Info

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

JNIOR selection dialog box

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.

Backup Naming dialog box

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

Open Backup as Update Project

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.

Edit Update Project

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.

NOTE: After successfully cloning a JNIOR configuration, since it will copy the EXACT configuration of the other JNIOR, make sure you go through and change any settings that shouldn’t be the same. This means any references to external devices should be checked for IP changes.

By | On July 31, 2019 8:22 pm | No Comments |

Frequently Asked Questions

While we are always available one-on-one to answer any questions and/or discuss how JNIOR can help your company, we wanted to answer some of the more frequently asked questions.

Contact INTEG Process Group for additional assistance with your Technical Questions and General Questions.

General Questions

Where is the JNIOR manufactured?

The JNIORs and Expansion Modules are made in the USA. We purchase the PCBs from a company a company in the US. The components are sourced globally. The PCB and components go through surface mount assembly here in the office. Programming and testing is also performed in our office.

What does “JNIOR” stand for?

JNIOR (pronounced “junior”) is a Network I/O Resource utilizing the Java™ platform.

What are the JNIOR Certifications?

TUV Safety Mark (IEC, EN 60950), CE Mark, FCC Class B, CB Scheme Available, RoHS Compliant. A copy of the TUV Certification PDF can be obtained from the All Downloads page.

How much does the JNIOR weigh?

11 ounces (312 grams).

What is the warranty on JNIOR?

2 years. Here is the JNIOR Warranty

How do I submit an RMA?

If you want to return your JNIOR via an RMA, make sure you contact INTEG support first. They will try and review your JNIOR and if it is defective will help you with the RMA process. They can be contacted at support@integpg.com or through our chat on our website.

How does the JNIOR internal time clock keep current?

The JNIOR has NTP (Network Time Protocol) capability.  You can enter an IP address (or URL) and the JNIOR will sync its time when it boots up with that computer. It will continue to sync it every 4 hours.

Do JNIOR Expansion Modules need power?

No. The modules draw their power via the Sensor Port on the JNIOR.

How many Expansion Modules can be connected to one JNIOR?

Multiple plug-and-play expansion modules can be daisy-chained to the JNIOR via the Sensor Port.  The exact number of modules that can be connected is a function of the mix of expansion modules being used.  Each module draws differing amounts of current. Please contact INTEG with your proposed mix of expansion modules.

What programming language do I use to program the JNIOR?

The applications on the JNIOR are developed using Java, but we have standard applications included with each JNIOR that meet a variety of needs so 99% of our customers do not actually do any programming on the JNIOR! But if you want to add your own software, we would be glad to help you get started.

What is the recommended power for the JNIOR?

We recommend 12 Volts DC at 1 Amp.  Although the JNIOR can handle 12 – 24 VDC or AC for the JNIOR power supply. The JNIOR digital inputs and relay outputs handle 0 – 60 volts DC or AC. 

Support Questions

How do you take a Snapshot?

To take a snapshot, you open the support tool and go to the snapshot tab. There you’ll click “take snapshot” and select the JNIOR you want to take a snapshot of.

How do you control external modules with a macro?

To control an external module with a macro command, you’ll create a macro in the support tool and send it to the analog presets program using cinema.

How do you close or pulse an output when the JNIOR boots?

In order to close an output on boot, you can open the support tool and go to the configuration page. On the configuration page in the outputs section, you can set the initial action of any channel to 0 which will close that output on boot. If any positive number is set in the initial action, that output will pulse for that many milliseconds on boot.

How do you invert an input?

Inputs can be digitally inverted on JNIORs to help test when they are triggered. Inverting an input can be done via the JNIOR Web Page, or by setting the ‘Inversion’ registry key through the command line.

How do you view the Environmental Monitoring Module data?

To view data from an environmental monitoring module in a graph, you use the Grapher and Tasker applications. You configure Grapher to read data from logs that will be created by Tasker. You then configure Tasker to log the data from the environmental monitoring module.

Can the JNIOR use the MQTT protocol?

The JNIOR can use the MQTT protocol. You can use the MQTT application to send information through the JNIOR message pump. You configure the MQTT application to a public broker and then send messages from another application on the message pump.

Why can’t the JNIOR connect to a MODBUS server?

The JNIOR can connect to a MODBUS server, but you need the MODBUS application. This application is separate from the Operating System and needs to be activated or else you can’t connect to a MODBUS server. You can do this by going to the application section of the configuration tab in the JNIOR’s WebUI, and clicking the checkbox next to the MODBUS server application.

How do I reboot my JNIOR?

One way you can reboot a JNIOR is simply by pulling the power and plugging it back in. You can also go to the command line from the support tool or JNIOR web page and type “reboot” and then type “y”. This will initiate a reboot as well.

How do I reset my JNIOR back to its factory default?

WARNING: Doing this wipes all data on your JNIOR, be sure this is what you want to do before executing a factory reset. To do a factory reset, its similar to a normal reboot from the command line, but the full command is “reboot -eraseall” followed by “y”. This will NOT work for the Series 3 JNIOR. There is a post explaining how to factory reset a Series 3 JNIOR.

How do I transition from a Series 3 to a Series 4 JNIOR?

Series 4 JNIORS were made to be a drop in replacement for Series 3 JNIORs. While some applications are only usable on Series 3 JNIORs, typically Series 4 JNIORs have an application that provides the same functionality and can be switched to. While different setups may require different steps to upgrade, you can always reach out to JNIOR support for help performing said upgrade.

How do I look at the connections on my JNIOR?

In the command line of the JNIOR, if you type “netstat” a list of connections on the JNIOR will be displayed. A post about the netstat command is in the knowledge base.

How do I use the JNIOR’s WebUI?

The JNIOR’s WebUI (Previously called the DCP) allows you to access and control tons of setting on your JNIOR. It can be accessed by right clicking your JNIOR in the support tool and opening its web page or by typing its IP into a web browser’s URL.

How do I update a JNIOR with an application?

To put an application on the JNIOR, you’ll need to download the application from our website, then open it (Don’t Unzip) in the update tab of the Support Tool. You’ll select ‘publish’ and the JNIOR to update the application to, and once it completes your JNIOR should have that application on it. There is an example post on updating Cinema to a JNIOR as well.

How do I access a JNIOR application that has a webpage?

There are two ways to usually access an application on a JNIOR. One way is by opening the JNIOR’s WebUI and under the configuration tab, in the application section, clicking its pop-out link. If the application doesn’t have a pop-out link, it you can also be accessed by opening a web browser, and typing in the URL your JNIOR’s IP Address followed by /”application name”.

How do I set the time on my JNIOR?

To set the JNIOR’s date and time, you’ll want to access either command line from the support tool or JNIOR web page and login in. You can then enter “date” followed by the date and time you want on the JNIOR formatted as “MMDDYYYYHHMMSS”.

How do I take a backup of my JNIOR?

To take a backup of the JNIOR, you’ll need the support tool. In the Snapshot tab of the support tool, you can select the Take Backup button which can will copy the configurations and files from a JNIOR and create a backup of it that can be transferred to other JNIORs to clone the configuration or to revert to an older configuration if a mistake is made.

Why won’t my JNIOR’s web page load, or show in the support tool?

When the JNIOR is loaded on the network they have DHCP enabled, which checks the network the JNIOR is on and assigns it an IP available. If your network doesn’t support DHCP then your JNIOR will default to the address 10.0.0.201. If another device on the network has 10.0.0.201, then the JNIOR will forgo the IP address and set itself to 0.0.0.0 to avoid an IP conflict. To fix this, you need to change the IP address of the JNIOR, which a post explains here.

Whats the difference between Tasker and Task Manager?

Tasker is a new application that was made to replace the Task Manager application. Task Manager was made for Series 3 JNIORs, and aren’t able to use Tasker. Tasker on the other hand was made for Series 4 JNIORs, which has improved functionality and is easier to configure. For more information, click here.

I have a system that declares the JNIOR as a device and connects on port 9200. Why is it not connecting?

When this happens its typically when a connection is initially being made to the JNIOR during setup. Give your system connecting to the JNIOR a reboot and the connection should establish itself.

I’m sending a command to the JNIOR via a TCP/Serial connection, but why isn’t the JNIOR doing anything?

Something that commands need to include when being sent to the JNIOR is the termination string. For example, if your connecting to the JNIOR using Cinema the default termination string is \r\n. So when you send the JNIOR a command in Cinema, make sure the command ends with \r\n. To check what termination string you need for your connection, based off the application your using on the JNIOR, you can check in the application registry keys in the JNIOR registry of a JNIOR’s web page. (appdata/application name).

If your question wasn’t answered here, check out our knowledge base to see if it’s answered there.

By | On July 19, 2019 7:59 pm | No Comments |

QSC has released a plug-in for the JNIOR and the Q-SYS Core!

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.

By | On July 1, 2019 1:12 pm | No Comments |

Perform a reboot from Java Application

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 {
            // the -f option forces the reboot without the need for user confirmation
            ConsoleProcess consoleProcess = new ConsoleProcess("reboot -f");
            consoleProcess.waitPrompt();
        } catch (Exception ex) {
            throw new IOException("Error rebooting").initCause(ex);
        }
By | On June 17, 2019 10:23 pm | No Comments |

JANOS 1.8 Released

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 1.7.1 Released December 3, 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 1.7 Released July 26, 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

JANOS 1.6.5 Released May 22, 2018

  • Corrected FTP listing issue created by the v1.6.4 release
  • Corrected getRegistryList method memory leak
  • Corrected 412DMX light Flickering
  • Corrected 412DMX NAND Flash processing issue
  • Corrected FTP transfer restart issue
By | On June 17, 2019 8:31 pm | No Comments |

Utility 3.0 Released

  Utility.Jar v3.0 [ Jun 14 2019, 1.32 MB, MD5: ]

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.

By | On June 14, 2019 9:51 am | No Comments |

Finding the JNIOR IP Address

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 --- --- --- --- -
By | On June 14, 2019 8:41 am | No Comments |

Cinema.jar 3.5
Name Version Release Date Size MD5
Cinema.jar - Update Project v3.5 Jun 02 2019 327.0 KB 57a834f2c5ac177b7b19b6dec52350ce

+ Added HTTP POST method to Macro Actions.

+ Added the ability the use HTTPS for GETs and POSTs

Cinema.jar 3.4.1 May 29, 2019

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

  • Released May 28 2019

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

 

Cinema.jar 3.4.0 May 16, 2019

  Cinema.jar - Update Project v3.4 [ May 16 2019, 320.36 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.

By | On June 2, 2019 9:58 am | No Comments |

Cinema.jar 3.4.1

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

  • Released May 28 2019

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

 

Cinema.jar 3.4.0 May 16, 2019

  Cinema.jar - Update Project v3.4 [ May 16 2019, 320.36 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.

By | On May 29, 2019 12:37 pm | No Comments |

JMP Protocol

Available in JANOS 1.8.

Name Version Release Date Size MD5
JMP Protocol Manual v1.0 Sep 17 2019 238.9 KB 4cee8456dda492f936551c04541797f1

The JMP protocol shares the messaging JSON structure that is used by the DCP (Dynamic Configuration Page) and the web-socket protocol but on port 9220, by default.

To make processing easier we wrapped the JSON message in a two element JSON Array.

[ number, object ]

Where number is the size in bytes/characters of the JSON object that follows.

Doing this relieves us of needing to count braces to see when an entire JSON message was received. To parse the structure we can do the following:

  1. Look for the opening ‘[‘.
  2. Then process numeric values until a ‘,’ is found. White-space is ignored.
  3. White-space is again ignored and N bytes are read.
  4. Finally remaining white-space is ignored and the trailing ‘]’ confirmed.

If the numeric value is invalid, the comma missing or the trailing ‘]’ bracket not found, the entire message is to be ignored. The extracted JSON Object can then be validated as well.


Wireshark example from JNIOR network capture
By | On May 22, 2019 11:11 am | No Comments |

Cinema.jar 3.4.0

  Cinema.jar - Update Project v3.4 [ May 16 2019, 320.36 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.

By | On May 16, 2019 2:58 pm | No Comments |

JNIOR Support Tool 7.9
  • The JNIOR Support Tool version 7.9 addresses an issue with new installs.  The C:\INTEG\JNIOR Support Tool directory was not getting created upon install.  This would prevent the Support Tool from opening.
  • Also in this update is a selection for the new Barco Series 4 projector.
By | On May 16, 2019 2:01 pm | No Comments |

Support Tool 7.8 bug affecting New Installs

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!

By | On May 16, 2019 8:34 am | No Comments |

Serial to Ethernet 6.0
  • 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.08 KB, MD5: d06bd5279d05546652b56faf427cc676 ]

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

By | On May 10, 2019 10:26 am | No Comments |