The Cinema Migration Tool is an application that copies a Cinema Setup from a Series 3 JNIOR and loads it on a Series 4 JNIOR. All that’s needed is a snapshot from the Series 3 JNIOR, and the Cinema Migration Tool will use the configuration files inside it to format that Series 3 JNIOR’s Cinema setup on a Series 4 JNIOR. This tool should make moving Cinema setups from Series 3 JNIORs to Series 4 JNIORs much easier. Here is a brief walkthrough on how to use the Cinema Migration Tool.
To start, once you’ve downloaded the zip file, you’ll want to open it and run the cinema-series3-upgrade.exe application within it. (Don’t unzip). Then as mentioned previously, the Cinema Migration Tool requires that you take a Snapshot of the Series 3 JNIOR whose configuration you are trying to copy over. Once you have the snapshot, you’ll then select the Open Series 3 Snapshot button, where you’ll navigate to the snapshot on your PC and open it in the Cinema Migration Tool.
NOTE: When opened, the device file, macro file, and jnior.ini file should say they are found in the Cinema Migration Tool. If they are not found, this means the pathing to the files in the snapshot isn’t incorrect. Make sure not to unzip or alter snapshots after they’ve been taken.
Publish Configuration to Target Series 4 JNIOR
Once the snapshot is loaded, next you’ll want to enter the IP of the JNIOR you are trying to publish this configuration to. Make sure this JNIOR is on the same network as your PC. Once entered, hitting run will start the Cinema Migration Tool in publishing the Cinema configuration to the Series 4 JNIOR.
The Cinema Migration Tool will state when it is done at the bottom of its dialog. Once finished, the Cinema Migration Tool can be immediately run again to publish to another JNIOR.
Confirm Your Setup
To make sure this has worked, you can check by going to your Series 4 JNIOR’s web page and navigating to the Folder tab. Once there, check that your root folder contains the device and macro file from your Series 3 Snapshot, along with making sure the Cinema.jar application exists in the flash folder. If this is the case, then you’ve successfully moved your configuration from the Series 3 to the Series 4 JNIOR! If this isn’t the case, INTEG support would like to help you out. You can reach out to us by joining our online chat, or by emailing our support at support@integpg.com.
JNIOR, a Network I/O Resource utilizing the JAVA™ platform, is a cost-effective automation controller that communicates over a network using TCP/IP via an Ethernet Port or via its serial port. The JNIOR is a general-purpose automation controller and I/O device that is easily configurable for controlling and monitoring your equipment or process via the built-in web pages, by enabling the built-in software applications, interaction with an application running on another computer, or by adding your own applications.
Currently, there are 4 different Models of the Series 4 JNIOR, each very similar to the other with a few differences.
JNIOR Model
Catalog Number
I/O Count
Serial/DMX Ports
410
JNR-100-004B
8 Inputs, 8 Outputs
COM Port (RS232), AUX Port (RS232 / RS485)
412
JNR-200-004B
4 Inputs, 12 Outputs
COM Port (RS232) , AUX Port (RS232)
414
JNR-300-004B
12 Inputs, 4 Outputs
COM Port (RS232) , AUX Port (RS232)
412DMX
JNR-200-004D
4 Inputs, 12 Outputs
COM Port (RS232), DMX 512 (5-pin XLR connector)
Each JNIOR Model links to their web page, where more detailed information can be found for them (like their data sheets)
Powering Your JNIOR
The JNIOR uses a 2-piece terminal connector system for all power and I/O wiring connections allowing for easy installation and/or removal of the JNIOR. Additional installation information and drawings are provided on our website.
The JNIOR can be powered with 12 to 24 volts AC or DC. An optional, wall transformer (AC power converter) for North American outlets is available from INTEG that can be used for converting 120/240 VAC to 12 VDC @ 1 amp. International models are also available as Euro and UK plugs.
The Power Connector is located along the upper left edge of the JNIOR. Note that this is a 4-pin connector. If numbered from one (1) through four (4) from left to right power is always connected to positions 2 and 3 (middle two connectors). The polarity is irrelevant although it is recommended that the positive (+) lead be connected to position 2.
The left two positions (1 & 2) are internally connected together, as are the right two positions (3 & 4). This is to facilitate the interconnection of the supplied power to other devices and circuits such as input or output devices. If you power the I/O circuits with your JNIOR power supply, please make sure the power supply is sized appropriately.
WARNING: Do not connect the transformer leads both to Positions 1 & 2 or both to positions 3 & 4. This will short the transformer and possibly damage it and/or the JNIOR. Always use a fused/protected power source.
When a proper power source is connected and turned on the leftmost LED adjacent to the power connector will glow BLUE continuously. The LED to the right may glow ORANGE for several seconds. This orange STATUS LED remains on through most of the JNIOR boot sequence. Later it will flash whenever an external connection is made to the JNIOR via the Ethernet port.
Wiring JNIOR I/O
JNIOR Inputs
The JNIOR is equipped with optically isolated digital inputs. Each digital input can accept AC or DC voltage sources in the 0 – 30 V range. An LED associated with each digital input displays the current electrical status of the input (off or on). Isolation of each digital input allows you to connect input signals to different voltage sources without the addition of isolation devices. The input voltage must be greater than 2 VDC for the input to register as “on” and then less than 1 VDC to register as “off”. A typical connection would be as follows:
JNIOR Outputs
The JNIOR is equipped with Relay Outputs with most of them being a Form A SPST relay (1 Normally Open Contact) and two of them being a Form C SPST relay (1 Normally Open Contact and 1 Normally Closed Contact – jumper selectable as to which one is available on the JNIOR terminals by removing the lid and changing the jumper setting. Normally Open is the default.) Each relay output is independent and isolated from the other relay output. Each relay contact rating is 1A @ 24VDC and the voltage source must be in the range of 5 – 30V AC or DC. A typical connection would be configured as follows:
Setting the JNIOR’s IP
Starting with JANOS 2.0, the JNIOR is shipped with DHCP enabled for dynamic setting of the JNIOR IP address by a network server. More information is here on finding your JNIOR’s IP address.
If DHCP does not work on your network, then there are two ways to configure your JNIOR IP settings:
By using the JNIOR Support Tool (Beacon tab) provided on our website at the following link: https://www.integpg.com/jnior-support-tool/. You can use the JNIOR Support Tool to configure the JNIOR’s IP by right-clicking the JNIOR and selecting Configure -> IP Configuration. A dialog will appear to edit the JNIOR’s IP after that.
Via the RS232 Serial Port and a command line window available via the JNIOR Support Tool: http://www.integpg.com/support/jnior/. You can use this command line to set the IP by doing the ipconfig -a IP -m MASK command, replacing ‘IP’ with the IP you want for the JNIOR, and ‘MASK’ with the subnet you want for the JNIOR. For example, on a private network, the IP address may be something like 192.168.1.10. A common mask would be 255.255.255.0. The command would then look as follows:
ipconfig -a 192.168.1.10 -m 255.255.255.0
JNIOR Web Pages
The JNIOR Series 4 contains the JNIOR web page which is a web page used for a variety of functions including monitoring and manually controlling the I/O, changing various configuration items, opening a Telnet/Console session, and several other functions. The JNIOR web page works with Microsoft Internet Explorer, Google Chrome, Firefox, and other browsers.
PLEASE NOTE: The dynamic web page requires a ‘modern web browser’ which is defined as Internet Explorer 10 or greater, Google Chrome or Firefox.
You can launch the JNIOR web page from the Beacon tab in the JNIOR Support Tool by right-clicking on your JNIOR and going to Tools – Open web page or by manually entering the JNIOR IP address in your browser address line. To manually launch the JNIOR web page, open your browser and in the address line of the browser type your JNIOR IP address or serial number, for example: http://10.0.0.146 or jr616010235
After the JNIOR web page is loaded, the user is asked to log in with a valid username and password. You can use the default username (jnior) and default password (junior).
The JNIOR web page will be launched in your browser as shown below.
There are two tools to choose from when working with the JNIOR.
Why two tools?
The JNIOR Support Tool has been around for more than ten years. For much of that time, it has remained unchanged and has been a staple for configuring and maintaining the JNIORs. Within the past few years, we have seen more and more customers using non-Microsoft Windows computers and we wanted to offer a cross-platform alternative—that’s where the JNIOR Supporter comes in. We chose to develop the new cross-platform tool in JAVA. This requires you to have a Java Runtime Environment loaded.
Why not move to the new tool altogether?
The JNIOR Support Tool allows Cinema users to configure devices and macro files. There is A LOT of functionality that we are not ready to replicate. We wanted to get the tool released and not delay while the cinema functionality was being implemented.
Which one should I use?
If you are running a non-Windows environment then you will need to load the new Supporter. If you are looking to use the Cinema application then you will need to use the Support Tool. Beyond that, it is up to you. We try to ensure that they both have the same basic functionality.
The JNIOR is a very reliable device. I’m sure many devices claim that but as of this writing, in October 2023 we have spoken with customers that are still running Series 3 units from 2005. The first run of Series 4 units are still operational from 2012.
There are basically two components that would have any endurance data.
The mechanical relays should be able to see a minimum of 100,000 closures.
The battery should have a life of around 6 years. The JNIOR only relies on the battery to maintain the SRAM and the internal clock when external power is not present. The JNIOR can operate without a working battery. The 410, 412, or 414 battery can be replaced in the field. It is a CR2032 coin-cell battery.
The concept of using a watchdog is to ensure that the application continues to run as expected. JANOS provides a Watchdogclass that has a couple of options. A sample of how to use that class can be found here.
Single Instance
Most times we only want one instance of an application running at a given time. Use the JANOS.registerProcess() method to check to make sure there is not another instance running. Here is an example of using the registerProcess() method.
String applicationName = "TestApp";
if (1 < JANOS.registerProcess(applicationName)) {
JANOS.syslog("Another instance of " + applicationName + " is running");
System.exit(-1);
}
Versioning
A great way to be certain that specific code is running is to implement versioning. If the application is going to be released or there are going to be multiple releases then versioning is nearly a must. Many times versioning takes the form of major.minor.build. This is not always the case. Sometimes you will see version numbers that start with the year that it was released. For example, Ubuntu uses year.month to get 22.04. The format you use is completely up to you.
Model and I/O Count
One issue that your application can have is handling the different models of JNIORs and the differing input and output count. The following code can help you with that.
/**
* @return the number of inputs based on the model of jnior
*/
public static int getInputCount() {
// if a 412 or 412 DMX then return 4. If not then check if a 414 and return 12. If not
// then return 8.
String modelString = JANOS.getRegistryString("$Model", "");
return (modelString.startsWith("412")) ? 4 : (modelString.equals("414")) ? 12 : 8;
}
/**
* @return the number of outputs based on the model of jnior
*/
public static int getOutputCount() {
// if a 412 or 412 DMX then return 12. If not then check if a 414 and return 4. If not
// then return 8.
String modelString = JANOS.getRegistryString("$Model", "");
return (modelString.startsWith("412")) ? 12 : (modelString.equals("414")) ? 4 : 8;
}
We recommend that all applications are saved in the /flash directory. There are multiple ways to upload a file to the JNIOR. How you decide to do that is up to you but the WebUI is a great tool for accomplishing this task.
Open the WebUI and go to the Folders tab. Click on the /flash directory in the tree view on the left. You can now drag and drop your JAR file to the view on the right.
Once you drop the file you will see the transfer progress bar.
Great, the application is on the JNIOR. We now need to decide how and when it should be executed.
Running the Application in the Foreground
When should we run an application in the foreground?
Answer, when we are developing, debugging or when an application needs to interact with the user from a command prompt. Notice I said from a command prompt. There are other ways to interact with the user. For example, a web interface. But that will be discussed later.
To execute an application from the command line we can enter java APPLICATION_NAME.jar or simply APPLICATION_NAME. if only the application name is entered then JANOS will look for a JAR file. If the file is found then it is executed.
Running the Application in the Background
When would we want to execute an application in the background?
Answer, when we have an application that we are running that we will not interact with but we still want to be able to interact with the command line. To do this we will append a “&” to the end of the command we use to launch the application. The command line prompt will be returned immediately.
Setting an Application to Run on Boot
When do we want to execute an application on boot?
Answer, when we have a production application that should always be running. To set this up we will make a run/ registry key. The name of the registry key can be anything you want. The content of the key is the way that you would execute the program from the command line as we did above. This is the same as executing an application in the background but without the user having to start the application manually.
The JANOS Runtime Library should be installed as a Library in your IDE. Here is how to do that in the Apache NetBeans IDE.
Open Libraries Dialog
Open the IDE and select Libraries from the Tools menu.
Create New Library
Click New Library…
Give the Library a name. We suggest JanosRuntime_2.0
Add JAR to Library
On the right side of the dialog you will new click Add JAR/Folder…
Navigate and select the location where the Janos Runtime JAR file was saved.
Adding in the sources
Now that the JanosRuntime library has been created, we want to add the sources so that we can reference them while working with our code. We do not distribute source code but the method stubs are still extremely helpful.
To do this we will click on the Sources tab and then repeat the steps to Add JAR/Folder as you did when creating the library.
Add Javadoc
Adding the javadoc will enable the NetBeans intellisense. To do this we will click on the Javadoc tab and then repeat the steps to Add JAR/Folder as you did when creating the library.
So you’re looking to write your own code to run on the JNIOR? You have come to the right place. Writing code for the JNIOR is as easy as writing code for your PC. The JNIOR will run the JAR that is created by your favorite IDE. There are almost limitless possibilities when it comes to what you can program on the JNIOR. Most of the applications that we have written have come from customer requests over the years.
This section of our website is not meant to teach you how to code but rather to show you how to enable your IDE to write JNIOR code that is targeted for the JNIOR.
Note: Additional Libraries cannot be used with JNIOR applications.
Prerequisites
Java JDK
Java IDE (We use Apache NetBeans)
JANOS Runtime Library
Understanding of Java Programming
Check for Java
Type java -version at a Command Prompt
JANOS Runtime Library
Applications targeted to run under JANOS must be built against the JANOS Class Library. This library can be found in the etc/ folder on your JNIOR Model 410. This file is OS version dependent although it is likely not to change dramatically from release to release. You might note the date and before you update or finish an application for your JNIOR make sure that you are using the latest version that you have available. INTEG can also send you a copy of JanosClasses.jar on request.
The JANOS Runtime Library does not contain the full JVM that you might be used to programming against. It is close but to save code space we have omitted some classes and methods. Take a look at the JANOS Runtime Javadoc to see what classes and methods are available.
To create a new project go to the File | New Project… menu item. This will open the New Project dialog. In the New Project dialog box, you can select Java with Ant under Categories, and Java Application under Projects.
Hit next, and then give the Project a name. In this example the project is named ‘ExampleProject’. After naming it the application can set to where its saved to. This is useful as projects can all be saved in the same location, making them easy to find in one directory. Once a name and location are given to the project a name and a location on your computer, hit finish.
Add JANOS Runtime
Now that the project is created, the JANOS Runtime library needs to be added to the project so its classes can be used in the application. To do this, go up to the file drop-down and select ‘Project Properties’.
In the Project Properties dialog box, select the Libraries option under the Category section. Under to the compile tab, select the plus icon next to Classpath and select ‘Add JAR/Folder’. Then select the JANOS Runtime Library.
Give JANOS Runtime precedence
In order to ensure that the classes stored in the JANOS Class Library take precedence over any that might be also present in the JDK you can modify the project properties.
Open the ../nbproject/project.properites file.
Locate the endorsed.classpath property and set it equal to ${file.reference.JanosClasses.jar} which should be the same as the javac.classpath property setting if you had properly added JanaosClasses.jar above.
This will insure that the JanosClasses.jar file is searched before any other library. As of the time of this writing we do not know of a way to prevent the Java Compiler from referencing the installed platform libraries.
Debug Information
Debugging information is extremely useful if some error arises. The debug information in the Stack Trace will pinpoint exactly where the bug lies in your code. The stack trace will show you the call stack containing source file names along with line numbers. You can enable debug information in the Project Properties dialog.
We offerSeries 4 JNIORs that are made to be a great drop-in replacement for Series 3 JNIORs.
If you have a Series 3 JNIOR and are looking for a replacement, they unfortunately hit the end of life in 2015 and we no longer offer them. Series 4 JNIORs are essentially an improved version of the Series 3 JNIOR that offer improved hardware, more applications, and more built-in functionality. Most Series 3 applications have been modified to run on the Series 4 JNIORs as well, but the dimensions and footprint of the Series 3 JNIOR are the same as the Series 4 though.
Here are just a few of the improvements implemented from the Series 3 to Series 4:
A faster processor allows for quicker responses from applications running on the JNIOR and quicker reboots for the JNIOR.
The Model 410 JNIORs have RS-485 capabilities for their serial connections.
Applications such as Tasker, Analog Presets, MQTT, Grapher, and DMX provide new functionality for the JNIOR to use.
Easy-to-use configuration pages through web browsers provide more ways to make customizing your JNIOR simpler, such as a folder tab to view files on the JNIOR.
Series 4 JNIORs can capture network traffic between the JNIOR and other devices to help investigate and troubleshoot all data being communicated with it.
If you have a Series 3 JNIOR and are looking to replace or upgrade to a Series 4 JNIOR, let us know and we’ll help you transition your setup!
Web Pages have been added for the Cinema application! These web pages have been implemented to make configuring cinema easier. This post will go over the different tabs the Cinema Web Pages have. To start, there are 7 tabs available on the Cinema Web Page. Other then the home page, each tab should display different registry settings to configure for the Cinema application.
Home Tab
The home tab is the opening tab when the cinema web pages are loaded. Unlike the other tabs, this page allows you extra functionality over the cinema application besides editing the registry keys. The first section allows you to enable/disable the cinema application to run on boot. Keep in mind that when changing this setting a reboot is need for it to take effect.
The second section allows you to test the communication settings of an external device. This allows you to test the communication between the JNIOR and an external device before having to create it in the macro and devices files. Below is a quick explanation for each field.
Command – This section is where you enter the command you wish to try sending to the external device.
IP – This is where you enter the IP address of the device you wish to send to.
Port – This is where you enter the Port number of the device you wish to send to.
Hex or ASCII – This sets weather the command you send is in ASCII (text), or hexadecimal format.
The third section displays the current connection status of the cinema application, and allows you to test macros that have been published to the JNIOR. Clicking execute will run the macros across from it. If Cinema doesn’t have a successful connection setup, it will display what isn’t setup correctly to create a connection to the Cinema application. It will also display if macros haven’t been loaded on the JNIOR yet.
Cinema Server Tab
Cinema.JAR can accept one or more connections from an external device using the Cinema Server Client port and this connection can be over the serial port and/or the Ethernet port. The Cinema Server tab allows you to edit the settings of the Cinema Server Client from the web page. Below is a quick explanation for each field.
TCP Port – Sets the TCP port that the Cinema Server connects on.
Serial Port – Sets the serial connection that the Cinema Server connects on.
Send Unsolicited I/O Alerts – Determines if any Alert such as I/O Counts or Date Stamps should be allowed through the Cinema Server Connection.
Send Ack – Determines if the Cinema Server Connection allows responses to be returned from the external device through the Cinema Server Connection.
Send Counts – Determines if the JNIOR reports each time an input changes to the external device connected through the Cinema Server Connection.
Send Date Stamp – Determines if each report of an I/O change on the JNIOR reported through the Cinema Server Connection gets appended with the current data and time.
Incoming Termination String – Sets the string that Cinema looks for at the end of each message sent to it to know if that is the end of message being sent.
Outgoing Termination String – Sets the string that Cinema adds to the end of each message it sends. The external device being sent to needs to know to look for this Outgoing Termination String.
Enable Serial Commands – Enables commands to be sent in Serial Control Format. This allows commands to be sent through that can close or open outputs on the JNIOR.
Control Panel
The JNIOR Control Panel Switches can be configured to trigger a macro to execute whenever the switch is pressed. The Control Panel tab allows you to assign macros to execute on the 12 control panel switches that are available. This requires you to own the control panel and have it connected to the JNIOR through the JNIOR’s sensor port.
Fire Alarm
The JNIOR can be assigned inputs to activate and release a fire alarm macro. The Fire alarm tab allows you to assign the inputs and the names of the macros that activate when the fire alarm is triggered and released.
Logic and Schedule
Cinema can setup logic statements and time events to determine when macros should be executed. The Logic Tab allows you to run macros based off of the current values of the JNIOR’s I/O as well as when other macros execute. The Schedule Tab allows you to set the time of day, the date, and the reoccurrence of when a macro is executed.
Triggers
Cinema can allow I/O to trigger macros similar to how the control panel works. The Triggers tab lets you assign what macros execute off specific I/O. The I/O in the triggers tab will reflect the type of JNIOR you are configuring.
While JNIOR 412DMX units may be unavailable, JNIOR 410s can be made to work as a substitute. Note that this does NOT work for JNIOR 412s and 414s, as 410s RS-485 compatibility is the reason why it can be used as a 412DMX substitute.
Cabling
When trying to connect to a 410 with DMX, the cabling will need to be corrected as you need to go from an AUX port to a male/female 5-pin XLR connector. By splicing into an existing DMX cable, you can attach a DB9 adapter with screw terminals to the end of the cable. It should look something like the picture below.
Here is the pin numbering for splicing the adapter on. Note the wire colors vary.
Signal XLR DB-9 Male
-------------------- --------- -----------
Signal Ground (GND) 1 5
Data (D-) 2 3
Data (D+) 3 7
Not Used (NC) 4,5 1,2,4,6,8,9
This cable allows the JNIOR to be a DMX FIXTURE. THE RESULTING DMX CONNECTION IS NOT ISOLATED. We recommend using an isolated power supply for the JNIOR and not sharing that voltage with other circuits. Take great care in making ground connections. Note that the JNIOR relay outputs are naturally isolated.
Aux Port Application
Below is an application you’ll need to update and install on the JNIOR. This is required for the JNIOR to interpret DMX communication on the JNIOR.
The serial settings of the JNIOR need to be configured so the AUX port output doesn’t disrupt the DMX communications. Below are the settings you need to set for the AUX Port. This is located on the JNIOR\’s Webpage, in the Serial I/O section under the Configuration Tab.
Once the cabling has been created, the DMX Port application is on the JNIOR, and the Serial Settings have been set, DMX communication should be possible on the JNIOR 410.
If you have any questions about this, contact our support to get help with this setup using pure chat or our email: support@integpg.com.
The DMX 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. NOTE: The DMX link below is for new installations only. If you already have the DMX application on your JNIOR and only need to update to a newer version, visit our DMX page to download our other update project for DMX that isn’t for new installs.
After installing both the JNIOR Support Tool and the DMX 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 DMX Update Project you just downloaded. When you open the DMX Update Project in the Support Tool you will see the following.
In the DMX application you can create fixtures, scripts and triggers to control the 512 DMX channels for your external lighting device.
The JNIOR Supporter is the new cross-platform version of the JNIOR Support Tool. Being cross-platform allows the JNIOR Supporter to run on any Desktop with a valid Java Runtime Environment loaded. Windows, Linux or Mac machines can now run the JNIOR Supporter tool.
Many of the same features have been implemented that current users of the JNIOR Support Tool are used to. The Beacon, Snapshot and Update tabs have all been ported over. There are a few tweaks to appearance and functionality but current users should have a good level of comfort.
Beacon
The Beacon Tab allows you to view the JNIORs that are connected to your local segment of your network. This works using UDP broadcasts to find JNIORs that may not have the same IP scheme as the host machine that is running the JNIOR Supporter tool. In this case TCP connections do not work but the JNIOR Supporter will help you to set up the correct network configuration settings needed for your network.
Snapshot
Snapshots largely work as the did before with the exception being that multiple Snapshots can be performed at the same time. This saves time. Lots of time. There is also new ways to view the Snapshots you have in your library. Your Snapshots will be categorized by Serial Number, By Hostname and by Date.
Update
Updates also work much like they did before. Updates can be published to multiple JNIORs as they did before as well. But, now you can open multiple Update Projects at the same time.
Once you have installed the JNIOR Support Tool, open it and go to the Update tab. Here we will open the Tasker update project that was downloaded. Do not unzip the update project file. You should see the following…
This image shows the Update project for Tasker version 3.1 from May 5th 2020
Click Publish and select the JNIOR or JNIORs that you wish the load the Tasker Application on to. The Update project will run until all of the selected JNIORs have been updated.
Once complete, you can go to the Tasker Web Application in your browser. Simply go to http://JNIOR_IP_ADDRESS/tasker.
To build dynamic messages you will use the text replacer syntax. Using {{ }} will allow the message engine to find the appropriate portion of the text and replace it with the value of the evaluated text that is contained within the {{ }} syntax.
temp[#].fahrenheit or temp[#].f for short temp[#].celsius or temp[#].c for short
Environmental Sensor
env[#].fahrenheit or env[#].f for short env[#].celsius or env[#].c for short env[#].humidity
Registry
registry("key_name")or reg("key_name") for short. Just replace key_name with the registry key name.
Date
date.currentmillis where the value is the number of milliseconds since January 1st 1970. date.format("format_string") where the format_string is of the following format:
MM two digit month dd two digit day yy two digit year yyyy four digit year HH two digit 24 hour hh two digit 12 hour mm two digit minute fff milliseconds aa am / pm zzz timezone string
for example. date.format("MM-dd-yyyy HH:mm:ss.fff")
Tasker is an application that runs on the JNIOR allowing Tasks to be executed manually, triggered, scheduled, or via remote connection. Tasks are a series of actions. Those actions can be I/O related, logging, email or network based.
Tasker is not loaded on the JNIOR when it is manufactured. It is an add-on application. Please follow the Installing Tasker guide to get Tasker installed and running on your JNIOR.
No Code, No Programming Necessary. Just configure it and go!
Writing JAVA code on the JNIOR is great and the perfect way to achieve the functionality you want. But, sometime you either don’t have the knowledge, expertise or time and want something out-of-the-box that you can just configure to get the job done. Tasker is the application for you!
Tasker is an update to the Task Manager application that was first created for the JNIOR Series 3 in 2007. It was ported to the JNIOR Series 4 but the core code was kept the same. A rewrite allows us to implement many new features. A comparison page between Tasker and Task Manager highlights many of those changes.
Here is a high level list of the features in Tasker
Workspace – Workspaces are different configurations of Tasker users can create that can be loaded, edited, and deleted.
Tasks – Tasks, or series of actions, can be created that can be executed in a variety of ways. Tasks can now be executed manually, triggered, scheduled, or via remote connection.
Devices – Some Actions used in Tasks may depend on Devices. Devices are names given to connections. The names are then used to make configuration easier.
Signals – A name given to an I/O point or sensor to make using it in an Action, Trigger or Logger easier.
Triggers – A set of conditions to watch for and when met a Task is executed. The signals that are configured will be used.
Schedule – Scheduling a Task to execute One Time, Daily, Weekly or by event has never been easier. Events that can cause a Task to be executed are On Boot, Sunrise and Sunset.
Loggers – Configuration to make logging easier to use in Task Actions. Loggers ask you to provide a file path, the information to be logged to the file and the retention count. The retention count is the number of files for that specific logger that will be kept.
Upgrading from Task Manager or previous version of Tasker
This version of Tasker uses a different configuration file layout. It is NOT compatible with Task Manager or the previous version of Tasker.
We are here to help. we can help you configure the new version of Tasker to work with your older configuration.
If you have any suggestions or a need for Tasker please Contact Us!
To update JANOS, the JNIOR Series 4 Operating System, you will need to do two things.
Get the UPD file on the JNIOR in the /temp directory.
Execute the jupdate command. To force the update to happen immediately upon entering this command we will type jrupdate -fup /temp/janos_filename.upd
The easiest way to update the unit remotely is using the DCP The DCP is most likely to be available on a remote JNIOR because it uses a single port for all of the features. Without the DCP you might need port 23 for telnet, port 21 for FTP commands, and many other ports for FTP data.
If the DCP is available follow this procedure.
Once the DCP is open, navigate to the Console tab.
Login to the command console.
Drag and drop the JANOS .upd file into the console window. This automatically stores the file in the /temp directory.
Issue the jrupdate command. Like above, to force the update to happen immediately upon entering this command we will type jrupdate -fup /temp/janos_filename.upd
The DMX application has multiple tabs: fixture types, physical fixtures, scripts, triggers, tools, help.
Each tab helps the DMX application create a script for fixtures on certain channels:
In the fixture type tab, you create fixture types that you can select from the physical fixtures, which defines for them the amount of channels that fixture uses.
In the physical fixtures tab you set the initial channel and fixture type of that physical fixture.
The scripts tab let you create a script that sets the addresses of DMX channels.
The triggers tab activates scripts based off if inputs or outputs are toggled.
Scripts are what is used to control the functionality of you fixtures through the DMX application.
When creating a script, you’ll have you’ll be given a dialog box to type your script, along with a bunch of help options to the right of the script to show you what is possible in the DMX script. You can also click the link on the right to automatically add that feature into your script! An example script below changes all the channels to zero, and then after waiting for .5 seconds sets channels 1,3,and 5 to 125.
You can set triggers to activate your scripts.
When setting the triggers, each line corresponds with a number for the inputs and outputs located on the JNIOR. You can set any script you created to run from an input/output being activated, running either one, multiple, or an infinite number of times (until an abort is called). The picture below is for a 412 JNIOR so it will only have 4 inputs triggers and 12 outputs triggers.
Clicking the drop down of the tools bar lets you access either the DCP web page, or the DMX panel which displays all 512 DMX channels that lets you view in real time all the channels in their current state and while running through a script.
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.
NOTE: This link for the Cinema Update Project is Cinema.jar, if you are using a Series 3 JNIOR you need Cinema.jnior instead. This can be retrieved from the legacy section of our downloads on our site.
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.
@integpg