When using Cinema, Serial PLUS, or Serial-To-Ethernet applications people will be generally using the serial port to talk to other devices or send commands. Knowing what registry keys need to be set to when communicating on them is important. This tutorial is for setting the registry keys up for the Serial Control Plus application.
To start, when using Serial Control, the connection that will be set up is accessed through the command line once all the registry keys have been set. So first thing is to go to the support tool and go to applications. Once there make sure that the Serial Control application is checked, otherwise check it and reboot.
Once the JNIOR reboots, go to the console tab and type “ps” to see if the application is running.
If it is then next go to the registry tab and in the section App-Data find the Serial Control program.
Here is where all the information for creating the serial connection is contained. If you are connecting through COM3 at the command line, make sure that the SerialPort value is set to AUX if the port being used is the Auxiliary port and not the RS-232 port. If you want to connect through TCP, make sure you set a TcpServerPortNumber value set, a good example one is 9202. Now all the values should be set to connect serially to the JNIOR. Go to the JNIOR support tool and select tools –> command line. This will bring up the command line to give serial commands to the JNIOR.
When using Cinema, Serial PLUS, or Serial-To-Ethernet applications people will be generally using the serial port to talk to other devices or send commands. Knowing what registry keys need to be set to when communicating on them is important. This tutorial is for setting the registry keys up for the Serial-to-Ethernet application.
To start, when using Serial-to-Ethernet, the connection that will be set up is accessed through the command line once all the registry keys have been set. So first thing is to go to the support tool and go to applications. Once there make sure that the Serial-to-Ethernet application is checked, otherwise check it and reboot.
Once the JNIOR reboots, go to the console tab and type “ps” to see if the application is running.
If it is then next go to the registry tab and in the section App-Data find the Serial-to-Ethernet program.
Here is where all the information for creating the serial connection is contained. Make sure that the SerialPort value is set to AUX if the port being used is the Auxiliary port and not the RS-232 port. Now all the values should be set to connect serially to the JNIOR. Go to the JNIOR support tool and select tools –> command line. This will bring up the command line to give serial commands to the JNIOR.
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.
In the DMX application, you create scripts to change the 512 DMX channels. Once you have a script, you’ll then want to be able to activate it. One way to set up a script to activate is by giving it a trigger. This post will explain how to create a trigger for a script.
Open the DMX application, and go to the Triggers tab. Once there, you’ll see the I/O layout for your JNIOR, showing how many inputs and outputs are on it. To setup a script to trigger on one of the I/Os, you’ll simply enter “script (SCRIPT_NAME)” into one of the I/O spots. You can additionally enter -f or -r after the script name to add additional effects to the script running. You can also enter “abort” into one of the I/O spots to make any script stop running when that I/O value occurs.
Once you’ve entered and saved a script name value in an I/O slot, you should now have a script set to run when the selected I/O value activates.
When you have a fixture that you want to control through the DMX application, you use a script. This post will explain how to create one.
To start, you’ll open the DMX application and go to the scripts tab and click the add script button which the application will then prompt you what you want to name the new script. After entering the new script’s name, you’ll go to it in the script tab and select the green pencil icon under the script column. The Edit Actions dialog box will open, where you can then enter actions for the script to perform. The 3 main actions are the delay, set, and fade. How you enter those actions in the script, and the different parameters an action can use, are shown on the right side of the dialog box.
After you’ve entered your actions in the script, you’ll click set at the bottom right of the dialog. Now when the script runs it’ll edit the channels referenced in the script actions.
In the DMX application, you create fixtures that pick how many channels of the 512 DMX channels will get set along with where the starting channel for that fixture is.
To start, you’ll need to create a DMX fixture type. In the Fixture Types tab, you’ll click the add fixture type button. You’ll then get the New Fixture Type Dialog, where you can set the amount of channels the fixture will use of the 512 DMX channels, and what they are named.
Once you have the fixture type created, you’ll the go to the Physical Fixtures tab and create a fixture of that type. Click on the add fixture button, which will open the New Fixture Dialog, where you can set the Fixture Type (you use the one you just created), name of the fixture, and the starting channel for the fixture.
Once you’ve created the fixture, you should now have a fixture that uses the amount of channels set in the fixture type settings, and starts on the channel set in the physical fixture settings.
When using the Cinema application, you’ll want it to be able to receive commands from other devices so its macros can be trigger. In the registry of the JNIOR, Cinema’s registry contains the CinemaServerClient and PreshowClient registries. These are what can be configured to listen for those connections to external devices.
While accessing the JNIOR WebUI when Cinema is installed, you can access the AppData/Cinema/CinemaServerClient or the AppData/Cinema/Client registry folders to configure the connections made using Cinema. The PreshowClient and CinemaServerClient are connections made to either a Preshow System or Cinema Server through TCP or Serially that allow control of outputs, I/O feedback, and the ability to interact with various devices using macros.
Inside both registry folders are multiple registry keys. The TcpPort key is where you can set the port number for an Ethernet connection to other devices. (Any valid TCP Port number will work, but we set it to -1 by default so it will not listen for TCP connections until its set). For serial connections, you need to set the Method key to serial and the SerialCommandsEnabled key to true. You’ll then need to go to the AppData/Cinema/CinemaServerClient/Serial for the CinemaServerClient or AppData/Cinema/Serial for the Preshow Client, and set the serial connection to whatever serial setting you want the JNIOR and your external Device to connect on.
NOTE: You can have both the Preshow Client AND the Cinema Server Client active at the same time. Each one can have a Serial Connection and a TCP connection active. You can have multiple devices connect to the same Cinema TCP port to control Cinema. Therefore, while you can have more then four devices connect to Cinema at the same time, it can listen for at most four different types of connections at the same time:
Cinema Server Client Serial Connection (1 connection)
Cinema Server Client TCP Connection (Multiple connections)
Just keep in mind that if both are using TCP then they can’t use the same Port Number, and if both are using a Serial Connection, they can’t use the same Serial Port.
When using the control panel, you might want to have the switches trigger macros you created in the support tool. This post will explain how to do just that. To start you’ll need to have created a macro in the support tool. If you haven’t done that already and don’t know how, here is a post on how to do it. You’ll also need to have installed cinema on your JNIOR as well.
Next, you’ll want to makes sure that your control panel is properly connected. You can check what external devices have been connected to the sensor port by opening the JNIOR’s WebUI, going to the Console tab, and after logging in entering “extern” into the console. If you have left-over information from previous external devices that you’d wish to get rid of, then you can remove devices no longer present by typing the extern -r command.
Once you have your macros created and published to a JNIOR along with your control panel being connected, you can now hook up the macros to the control panel using the JNIOR’s registry. Open your JNIOR’s WebUI and go to the registry tab. Once there, you’ll then go to AppData/Cinema/Panel.
Once here, you’ll simply enter the macro name on whichever switch trigger you want to activate the command. Now the macros you created will send a command when you hit a switch on the control panel.
This application will monitor the digital inputs. The corresponding output is set when an input pulsed. That output remains active until a different input is pulsed. This application effectively latches the output to represent the last input that transitioned from low to high.
package com.integ.latchrelays;
import com.integpg.system.IoEvent;
import com.integpg.system.Iolog;
import com.integpg.system.JANOS;
import java.io.IOException;
import java.util.Date;
/**
* This application will monitor the digital inputs. The corresponding output is set
* when an input pulsed. That output remains active until a different input is pulsed.
* This application effectively latches the output to represent the last input that
* transitioned from low to high.
*/
public class LatchRelaysMain {
public static void main(String[] args) throws InterruptedException, IOException {
// create an Iolog instance and a timestamp representing the last time an
// event occurred. we will start with a value of zero indicating only new events
Iolog iolog = new Iolog();
long timestamp = 0;
// loop forever
while (true) {
// refresh the oilog with the timestamp of the last input event
iolog.refresh(timestamp);
IoEvent[] inputEvents = iolog.getInputEvents();
// only process if there are events
if (0 != inputEvents.length) {
System.out.println("inputEvents.length = " + inputEvents.length);
// loop through the input events
for (int i = 0; i < inputEvents.length; i++) {
IoEvent inputEvent = inputEvents[i];
timestamp = inputEvent.timestamp;
System.out.println("timestamp = " + new Date(timestamp));
int highTransitions = inputEvent.mask & inputEvent.states;
boolean isTransitionHigh = (0 != highTransitions);
System.out.println("isTransitionHigh = " + isTransitionHigh);
// if the event was a transition high then set the outputs to
// represent the state of the inputs that transitioned from
// low to high. we will use all outputs here
if (isTransitionHigh) {
JANOS.setOutputStates(highTransitions, 0xff);
// we are only looking to process the most recent inpput
// transition from low to high. so once we find one we
// can abort the loop.
break;
}
}
}
// sleep for a little bit of time to not monopolize the CPU
Thread.sleep(50);
}
}
}
As long as the device you are sending to can create TCP or serial connections, the JNIOR should be able to send commands to it. If you are starting from scratch with a JNIOR, you’ll need to download the JNIOR Support Tool and the Cinema update project. The JNIOR Support Tool allows you to install update projects on JNIORs, and the Cinema update project installs the Cinema application, which is what listens for commands to activate JNIOR macros.
To update your JNIOR with an update project, here is a link to a post on our site that shows how to install Cinema.
Once the Cinema update project has been published to your JNIOR, we’ll now need to create a device in the support tool to send to. In the support tool, you’ll go to the device tab and select add. You can select the device and rename it. After that you’ll now configure the settings of the device so we can send macros to it. To start you’ll select your device type, and if you see the device you want to send to there you’ll select it. If not you’ll select Raw Ethernet for a TCP connection or Raw Serial for a serial connection. You’ll then set the rest of the device configuration according to the device’s TCP or serial settings.
Once you finish setting the device information, you’ll then want to save the device file by clicking the Save As button. After that you’ll then publish the file to the JNIOR you are using by clicking the Publish to JNIOR button.
After you’ve done that, we’ll now create the macro that will be sent to the device that will contain the text command. Going back to the support tool, you’ll go to the macro tab.
The first thing we’ll want to do here is click the “Link Devices” button at the top. Here we’ll select the device file we just created, so we can reference it in our action for the macro we are going to create.
After completing that, at the bottom left corner of the macro view and you’ll select add/macro. A new macro should populate the macro view, and you can then click on it and rename it. I’m going to name it ExampleMacro.
Once you’ve done that you’ll now go to the action view and select the add button there. A new action should appear in the action view. You can rename this if you’d like, and then we’ll want to select the device we previously created in the Support Tool to send to. Lastly, in the data field you’ll want to enter the text command you wish to send to the device. If you are using a Raw Serial/Raw Ethernet device, make sure you include the termination string at the end of your text command for the device you are sending to.
Once that is finished, make sure you add the action we created to the macro we created. You do this by selecting the macro, then the action, followed by the arrow between the macro and action view.
Lastly, like we did with the device file, we’ll save this using the Save As button, followed by publishing it to the correct JNIOR using the Publish to JNIOR button.
Now the JNIOR has a macro created that will send the text command to your specified device!
For a while now, we wanted to provide a cross-platform version of the JNIOR support tool to allow all users to access their JNIOR’s easily. There are also several aspects of the Support Tool that we wanted to improve upon. With that said, we are happy to release the JNIOR Supporter!
Features
Cross-Platform – The JNIOR Supporter provides cross-platform functionality. All users will enjoy the same experience regardless of the platform that they are using. The only requirement is that you have a valid Java Runtime Environment. .
New Interface – While looking familiar to the JNIOR support tool, the JNIOR Supporter has a new interface making it easier to view and interact with your JNIORs on the network. Information is displayed more openly to see issues or notices from JNIORs, and menus have been simplified to enhance ease of use.
Updated Features – The JNIOR Supporter introduces improved features such as sorted snapshots making them easier to find and more displayed information to for JNIOR’s on the network.
View Logs – Users can now view logs from the support tool in a pop-up dialog by right clicking on a JNIOR in the Beacon tab instead of needing to reach the JNIOR’s web page
Sorted Snapshots – Snapshots are shown in a tree view and are shown in each of three categories allowing the user to easily find snapshots that we taken for a certain JNIOR based on serial number or hostname or based on when snapshots were taken by day.
Simultaneous Snapshots – Multiple Snapshots can now be taken simultaneously to speed up the process of backing up your site’s JNIOR ecosystem.
Multiple Update Projects – Multiple Update Projects can be opened at the same time so no longer have to close one Update Project to open another. Care must be taken to not push conflicting updates to the same JNIOR.
Feedback
We want to know what you think of this new support tool. We know that change is not always easily accepted. Please let us know what you think of it and how we can add/improve to this application. If you have questions or assistance with the application, feel free to contact us. You can do so by joining our support chat on our website, emailing us at support@integpg.com or calling the office at 724-933-9350.
JANOS has implemented a set of time zones that are available but in no means is this a complete list. There are many territories in the world that either do not observe the time zone that they geographically belong to or they have different rules. Some locations differ the time zone rules by 30 or even just 15 minutes. Sometimes governments alter their policies and change the rules that have been in place for years or decades.
This article will describe how to create a new time zone with a DST rule as described in the JANOS Registry Documentation under section 9.2.
The clock subsystem is generally configured using the DATE command. JANOS defines a set of time zones for use in displaying local time. These time zones may or may not utilize Daylight Savings Time (DST).
As there are 24 hours on our clock one might expect that there needs to be only 24 time zones. This however is not the case as some areas offset their clocks by just 30 minutes. In addition, some areas utilize DST while others do not. The following is the default set of time zones. This can be displayed at any time using the DATE -T command.
This default list of time zones is likely incorrect for some areas across the globe. INTEG encourages users to let us know when a correction to the timezone tables might be appropriate. JANOS does provide a means by which you may define new time zones with or without DST rules. You may even correct an existing timezone. This is accomplished using one or more Time zones/<name> Registry entries.
Use of a website like timeanddate.com is very helpful for the validation and creation of time zones.
Here I will show you how to create a new Time Zone for Aukland New Zealand. Timeanddate.com gives us all the information we need in this screenshot.
We see that they are currently observing Daylight Savings Time and will be throughout the beginning of next year since New Zealand is in the Southern Hemisphere. So now we can follow the following format to build a registry key for the new time zone we will create.
We will need to use the full format in order to get the daylight savings time rules implemented. To do this we can enter the following at the command line.
The registry tab could also have been used to create the key. That would look like this…
In either case we get the same result. We can now issue the date -t command to see our newly created time zone.
A reboot is needed to complete the registration of our newly created time zone. After the reboot there is only one more thing to do. Tell the JNIOR to use it. For example, date NZST.
There you go! The new time zone has been created and the JNIOR is now using it. As mentioned above, it is recommended to tell INTEG of missing or incorrect time zones so that we can put it in the JNIOR but creating a custom time zone will get your JNIOR to start using the new rules immediately.
The Beacon tab shows you information about the JNIORs that were found. The Beacon technology uses UDP over port 4444. A UDP broadcast is used when discovering JNIORs on the network. UDP broadcasts are usually blocked by routers therefore restricting the UDP broadcast to the local segment of the network.
Right-click for options
Right-clicking presents you with actions that can be taken for the selected JNIOR.
Query All – Broadcasts the Query message to the Network to ask JNIORs to report back
Query – Broadcasts a query message to only the selected JNIOR on the network.
Identify – This will flash the amber status LED on the selected JNIOR for a few seconds.
Set Hostname – A prompt will be presented asking for the new Hostname. The current Hostname will be pre-filled.
Enable DHCP – Enables Dynamic Host Configuration Protocol (DHCP). Rather then manually setting the IP of the JNIOR, if the network the JNIOR is connected to has DHCP enabled, it scans the network for valid IP addresses that aren’t already taken and assigns one to the JNIOR.
Configuration – The Network Configuration dialog will be displayed. The choice between DHCP and static addressing. If a static IP Address is chosen then you will have the ability to enter IP Address, Subnet Mask, Gateway Address and DNS Servers.
Reset Attention Flag – Attention flags are messages that are displayed in the Message column of Beacon. Selecting this will clear all messages in the Message column of Beacon. (If errors are being thrown they will re-populate until they are dealt handled.)
Reboot – This will reboot the JNIOR. Rebooting will make the JNIOR disappear from Beacon for a brief moment.
Launch WebUI- This will launch the main web user interface for monitoring and controlling the I/O as well as general JNIOR configuration.
Open Telnet – Opens a telnet session for console level access. Here is a link to different telnet commands a JNIOR can be given.
Task a Snapshot – Initiates the Snapshot process. A snapshot is a copy of a JNIOR configuration, downloaded as a Zip File. These can be used to move configuration from one JNIOR to another, or to debug/troubleshoot JNIORs.
Show jniorsys.log – Loads the jniorsys.log.bak and jniorsys.log files into a dialog for real-time viewing.
Show/Remove errors.log – With these options you can either load the errors.log.bak and errors.log files into a dialog for real-time viewing, or remove them from the JNIOR. This option is only enabled if the Attention flag indicates that there is an errors file.
Show/Remove dump.log – With these options you can either load the dump.log.bak and dump.log files into a dialog for real-time viewing, or remove them from the JNIOR. This option is only enabled if the Attention flag indicates that there is a dump file.
Copy Field – Copies the data inside the field that is selected in Beacon. This is to easily grab values from the Beacon tab if needed.
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.
Serial Control Plus is an application that comes pre-installed on all JNIORs. It allows you to connect either serially or through TCP to a JNIOR, and give it commands to activate the JNIOR’s I/O. This post will explain how to setup and use Serial Control Plus on your JNIOR.
As mentioned before Serial Control Plus is already pre-installed on all JNIORs. To activate it, you need to go to the JNIOR DCP. This can be accessed by either right clicking the JNIOR in the JNIOR Support Tool and going to Tools/Open Web Page, or by typing the JNIOR’s IP address into the URL of your computer’s web browser. Once on the DCP, you’ll go to the applications section on the configuration tab and click the checkbox next to Serial Control Plus and reboot your JNIOR. This will allow you to use Serial Control Plus on that JNIOR.
Once you have activated the Serial Control Plus application on your JNIOR, you can now send commands to the JNIOR through it. We are going to open the command line from the support tool to activate commands on this JNIOR for this example. To open the command line from the Support Tool, you’ll go to the Tools bar at the top of the Support Tool and select Command Line.
Once you have the command line open, you’ll need to configure the settings of the command line to send commands to the JNIOR. To have the right settings to communicate with the JNIOR, we need to select how we communicate to the JNIOR. Serial Control Plus can communicate with the JNIOR two ways. Either you can connect to the JNIOR with a serial connection or a TCP connection.
To connect serially with the JNIOR, you need to plug a serial cable into the Aux Port of the JNIOR. Once you do that we need to select the correct settings in the command line window. As in the picture below, next to the connect button for the connection type you’ll select COM, baud type is 9600, Data bits is 8, Stop bits is 1, Parity is none, and hardware/software is set to none. For the Option drop-down, select all the choices.
To connect through TCP, you just need the JNIOR to be on the network to connect. As in the picture below next to the connect button for the connection type you’ll select TCP/IP, you’ll set the JNIOR’s IP, and the Port to connect on is 9202. For the Option drop-down, select all the choices.
Once you’ve decided on your connection type and configured the command line accordingly, you should be able to send commands to the JNIOR. Here are commands for controlling and monitoring I/O.
Controlling I/O
The following commands can be used to close, open and pulse outputs.
cX: Close the output (relay is “on” closing the contact) where x = 1 through 8 for the internal relay outputs on the JNIOR and x = +1 through +8 for the external relay outputs on the 4 Relay Output Expansion Modules
oX: Open the output (relay is “off” opening the contact) where x = 1 through 8 for the internal relay outputs on the JNIOR and x = +1 through +8 for the external relay outputs on the 4 Relay Output Expansion Modules
p=yyy Pulse duration (milliseconds) and is used in conjunction with the ‘close’ or ‘open’ command
Examples: c2p=1000 close output 2 for 1 second and then open again c+2p=1000 close output 10 for 1 second and then open again o3p=10000 open output 3 for 10 seconds and then close again c* Close all outputs at the same time (includes internal and external) o* Open all outputs at the same time (includes internal and external)
These commands can be abbreviated and used in combination, such as: c1 close relay output 1 c+1 close relay output 9 (first output on first expansion module) c+5 close relay output 13 (first output on second expansion module) c1+1+5 combination of the above all in one command c1234 close relay outputs 1 through 4 c1368 close relay outputs 1, 3, 6, 8 o125 open relay outputs 1, 2, 5 c1+1p=1000 close relay outputs 1, 9 and pulse each for 1 second simultaneously
Monitoring I/O
Whenever an input (or output) changes status (low-to-high or high-to-low), the following is sent out by the JNIOR:
INx=1 Input x (1 – 8) has gone high (on) OUTx=1 Output x (1 – 16) has gone high (on) INx=0 Input x (1 – 8) has gone low (off) OUTx=1 Output x (1 – 16) has gone low (off)
The default setting for the Registry Key AppData/Serial_Control/SendCounts is false. If you change this key to true and reboot, with each message stating the input status, a count value will also be included. Whenever an input changes status (low-to-high or high-to-low), the following is sent out by the JNIOR:
INx=1,yyy Input x (1 – 8) has gone high (on), counter value = yyy INx=0,yyy Input x (1 – 8) has gone low (off), counter value = yyy
Note: These monitoring messages are sent out individually over the serial port or Ethernet. The JNIOR does not report the status of more than one input/counter in the same message.
With this, you should now be able to use Serial Control Plus to control and monitor a JNIOR’s I/O!
It has been a while since Tasker was released. Tasker was a quick attempt at making a replacement for the Task Manager application that has been around for more than a decade, starting on the Series 3.
Ample time has now been taken to create a fully capable application that will be every bit as functional as Task Manager but offer the benefits of a rewrite, using configuration files and the latest web technology.
Some of the changes and new features are as follows:
Faster– The tasks are executed much faster and the triggers and schedule are monitored in real-time instead of once every 5 – 10 seconds.
Workspaces - Separate configuration logic into multiple workspaces. Then multiple workspaces can be loaded on the JNIOR at the same time.
Tasks are now separate from triggers. In Task Manager a Task was created and a Trigger was configured to get the Task to execute. In Tasker 3.0 Tasks are a separate entity that can be executed several different way including manual execution from the configuration page and being requested via an ASCII TCP connection.
Tasks can now send data via an Ethernet connection. To do this, a Device must be created so that the action can specify which device to send the data to. Multiple devices can be configured.
New Actions – We implemented actions that were previously available in Task Manager but are introducing many new actions like external module control, TCP communication and control structures.
Drag n Drop – Drag and Drop functionality makes it easier to design your Task logic.
Signals are now created to assign a specific property of a I/O point or sensor a name. The name can then be used in Tasks, Triggers or Loggers.
Loggers can be created to define the file name and schema or what data should be logged to that file. Each line in a Logger will be prepended with a timestamp followed by a comma. Loggers also allow you to define the number of files that should be kept with the given naming pattern. Name patterns can include date patterns. This will help you create a file per day for example.
Schedule – The schedule has additional options.
JSON Configuration files are used now instead of registry keys. Registry keys were limiting in size. The Series 3 could only store 255 characters in a registry key. It is much easier to upload configuration files to other JNIORs to replicate setups.
User Interface – The User Interface is now a native HTML application that uses the latest web technology. The latest web technology uses native HTML controls and Web-sockets to communicate with the JNIOR from your browser. This will allow accessibility over remote connections as long as port 80 is available. This is now consistent with the communication method used by the DCP. Task Manager had always used Java Applets. The Java Applets have not been able to launch in browsers for several years as they became frowned upon as security vulnerabilities.
This was just a short list of changes and new features. The documentation for Tasker should explain these topics as well as many others. If there is anything you don't understand please reach out to us for help. Additionally, if you have any suggestions or need the JNIOR to do something specific for you, please let us know.
The series 3 JNIORs used the Java Applet as a GUI. Years ago the browsers stopped supporting Java Applets due to security concerns. You are no longer able to open the series 3 Java Applet GUI in most browsers. You can still access it by launching it locally since it is installed as part of the JNIOR Support Tool. The security concerns over java applets are not present when launching the Java Application locally. Here is how to access the Java Applet for a JNIOR.
NOTE: The Java Applet GUI should only be used with series 3 JNIORs. The Java Applet GUI requires that your computer has Java installed. You can check if your computer has java by opening you command line and entering java -version. Here is a link to different JDK options.
First, make sure you have the JNIOR support tool downloaded. Here is a link for it.
Once you have downloaded the Support Tool, you’ll want to open it and find the JNIOR you wish to access the Java Applet for in the Beacon tab. Then by right clicking it, you’ll then go to Tools/Classic Monitor, Configuration, Control Application option and select it.
After selecting this for, the Java Applet for your JNIOR should open.
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.
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.
We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you are happy with it.OK
@integpg