A lot of JNIOR applications log information about what they are doing. This information can be about different things. Sometimes the application is purposely creating log files to keep track of data such as water levels or I/O changes. Logs can also be used to keep track of information about the application itself and if its run into any errors. Here is a quick post on how to look at Logs on a JNIOR.
To access information on a Series 4 JNIOR, you’ll first need to open the JNIOR WebUI. Once the on the JNIOR WebUI, you’ll then access the folder tab. Here you can see a list of all the files located on the JNIOR. Navigating through the folder shows the different files you can view, including log files.
Another way to access files on either a Series 3 or 4 JNIOR, you can open the File Transfer Protocol from the Support Tool. To start you’ll open the Support Tool, then in the beacon tab you’ll right click on the JNIOR and select Tools/Open FTP. You’ll then see a dialog open asking for the JNIOR’s username and password. Once you enter that, you should see all the available files on the JNIOR, including log files.
Tasker allows control over many different aspects of the JNIOR, including expansion modules. This post will explain how and what you use Tasker to control the Control Panel.
To start, you’ll want to make sure that your Control Panel is properly connected to the JNIOR. You’ll start by plugging the Control Panel into the JNIOR using the sensor port. Once the Control Panel is plugged in, you’ll then access the JNIOR WebUI and go to the Console Tab. There you’ll login into the JNIOR and type extern -r. This will remove any previously connected expansion modules from the JNIOR so only the connected Control Panel will be a recognized external device on the JNIOR.
Once that is done, we’ll now open the Task application. Once on Tasker’s web page, if you don’t already have a workspace created, you’ll want to create one. After you have a workspace, you’ll want to add a Task to the workspace, which Tasker will promptly ask you to name. Once the Task is created, you’ll then want to add an action to the Task, which once you click the add action button the action dialog will appear. Here we find the Control Panel actions.
Here we can add Control Panel actions to the Task, so that when its executed it can control different parts of the Control Panel. Currently in Tasker there are three different Control Panel actions, Set LED, Play Alarm, and Silence Alarm. The first action, Set LED, allows you to change the status of the LED next to a switch on the Control Panel. The options for the LED are off, slow, medium, fast, and on. The next action, Play Alarm, allows you to activate the alarm on the Control Panel. The actions lets you control the sound, duration, and interval of the alarm. The last action, Silence Alarm, simply silences an alarm on the Control Panel if an alarm is active at that time, and doesn’t require any addtional values.
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. NOTE: You need to have installed the DMX application on your JNIOR to start configuration.
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. NOTE: You need to have installed the DMX application on your JNIOR to start configuration.
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. NOTE: You need to have installed the DMX application on your JNIOR to start configuration.
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 the JNIOR to be able to send/receive commands to control or be controlled by external devices. In the registry of the JNIOR, Cinema’s registry contains the CinemaServerClient and PreshowClient registries. These are what can be configured to establish those connections to external devices.
While accessing the JNIOR WebUI when Cinema is installed, you can access the AppData/Cinema/CinemaServerClient or 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 registry key is where you can set the port number for an Ethernet connection to other devices. (We recommend using the port number 9600). 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/X/Serial (X is for CinemaServerClient or Client) and set the serial connection to whatever serial setting you want the JNIOR and your external Device to connect on. NOTE: You cannot have both a Preshow Client and Cinema Server connection at the same time.
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.
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 want to download the JNIOR Support Tool. This application allows you to update JNIOR’s with INTEG software that you’ll need to let you send the text command.
Once you’ve downloaded the JNIOR Support Tool, you’ll need to download two update projects from our site and update them to your JNIOR. The first update project is the Series 4 All-In-One update project. Its recommended for any new Series 4 JNIOR, as the update project gives JNIORs the most recent OS, along with some basic applications. The second update project is the Cinema update project. This is the application you’ll use to execute a macro, which will send a command from the JNIOR to a device.
To update your JNIOR with an update project, here is a link to a post on our site that shows how to install Cinema. NOTE: Though the post shows how to install Cinema, its recommended you install the Series 4 All-In-One first, using the steps in that post.
Once the update projects have 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 that the JNIOR has a macro we created that will send the text command to your specified device, now all we need to do is configure the JNIOR so that it will send this macro when DIN1 goes ON. First thing we’ll want to do is go to the JNIOR Web UI by selecting the JNIOR in the beacon tab of the support tool. There you’ll right click it, and go to tools/open web page. Once on the JNIOR web page, you’ll go to the registry tab. On the registry tab, you’ll select AppData/Cinema/Triggers. Once there, you’ll go to Input1Macro and enter the name of the macro we created in the support tool. We named it ExampleMacro, but if you named it something different you’ll enter that name here. This should set the JNIOR so that when DIN1 on the JNIOR goes ON, the macro will activate.
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!
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.
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 email@example.com or calling the office at 724-933-9350.
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.
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
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!
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.
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.
One of the useful things about Tasker, is that it can include communicating with other devices within its tasks. This is possible by including a networks action, but before those actions can be used devices need to be added to a Tasker application. This post will explain how to create devices to be used in actions for tasks.
To start, we’ll begin by going to the devices tab of the Tasker application.
Here we can select the “Add Device” button which brings up a dialog box to add a device to the current workspace.
In this dialog, two things need to be defined to create the device. This first value needed is the name of the device. The second value needed is the device type, which can either be an Ethernet or SNMP Device. Depending which Device type you choose changes the what information you can configure for the device after creating it.
Creating an Ethernet Device
If the Ethernet Device type was selected, the configurable option for the created device should look like this:
Two values of the Ethernet Device need configured in order to use it in a Task action, the IP Address and the TCP Port values. These need to be set to the IP Address and TCP Port values on the device, so that when they are used in actions, the JNIOR can properly communicate with the device. Another post has an example of using a TCP Send with an Ethernet Device.
Creating an SNMP Device
If the SNMP Device type was selected, the configurable option for the created device should look like this:
Three values of the SNMP Device need configured in order to use it in a Task action which are, the IP Address, the UDP Port, and the Community Name. These are needed for the JNIOR to connect to the SNMP Device and you obtain them from the SNMP Device. A different post shows how to use a SNMP Device with an SNMP Trap.
With this, you should have created devices in Tasker that can be implemented in actions.
Schedules add functionality to task created in Tasker because it gives them the ability to place a time for when the tasks should occur. This post will explain the different types of schedules that can be created, and how they can configured.
Creating a Schedule
To start, we’ll go to the Schedule tab of the Tasker application in order to create a schedule.
After going to the Schedule tab, the first thing to do is add a schedule in the Schedule tab. After giving it a name, the new schedule will have 3 parts to it, the name, the rules, and the task to be executed from it.
The Name section already has the name you gave it when it was created, but that section also gives you the options to edit the name, have the schedule enabled or not by checking the checkbox, or delete the schedule.
The Task Name section allow you to select a task from a drop down list or manual enter the name of a task that will execute at when the schedule is set.
Adding Rules to a Schedule
The Schedule Rules section is what allows the schedule to determine the times that which the Task selected in the Task Name section will execute. Clicking the “Add Rule” button opens the rules dialog box.
When adding rules to a schedule, there are 4 types of rules you can add, reboot, sunrise, sunset, and schedule. The first three are similar, where you simply click on the Schedule Type and select sunrise, sunset, or reboot from the drop down list. This will make it so that the task you set with that schedule will run at either sunrise, sunset, or on reboot, depending on which one you picked and no other options need to be selected.
Picking the Schedule option in the Schedule Type, lets you set the custom options for creating a schedule. The first option after the Schedule Type is the Start On option. This lets you select what day the schedule will begin to activate. Once the date reaches the day you selected it will run that schedule from then on.
After that is the Start Time option. This allows you to select from the hours and minutes in a 24 hour format when the scheduled task will begin.
Next is the Repeat Every option, which lets you how often in a time interval you want the task to reoccur. It adds a End Time option once a value has been added to the Repeat Every option. It can be set similar to the Start Time option that will decide when the Task will stop repeating by.
After that is the Date Selection Type option, which lets you choose between letting the task execute None (Which is one time), Daily, Weekly, or Monthly. Depending on what option you choose, this changes the Recur Every option. Picking the None option will make the task only run on the Start On date you picked. The Daily option will let you choose how many days between the task should run. The Weekly option will let you choose what days of the week the task should run. The Monthly option will let you choose what days of month the task should run.
With this, you should be able to assign schedules for any task you have created.
The Tasker Application has a lot of different functionality built into its actions, but it also can handle logic too. One of those actions that you can create in Tasker is the If block action. This post will create two If blocks in Tasker, one being the If block and the other being the If/else block.
Create an If Block
To start, create a new workspace by going to the File Drop-Down and selecting new. After that, go into the Task tab of Tasker and select the “Add Task” button. Once you name your Task, you’ll click on it and select the “Add Action” button. This will bring up the Action Dialog box. Here we need to select the If block action in the Control Structures section of the Action Dialog box. Once we have our If block in the task, we’ll want to add one more action inside of the If block by selecting the “Add Action” button inside of the If block. Here we’ll also select the Pulse Output Relay action.
Setting the If Block Actions
Now that our actions have been added to the Task, we can now configure them to do what we want. For this example, we are going to configure the if statement to activate when Input 1 goes high. To check if the input is high, for the If block value field we’ll enter din.state == 1.
With this, the If block will Pulse Output Relay 1 for 1 second if Input 1 is high.
Create an If/Else Block
In the workspace, go into the Task tab of Tasker and select the “Add Task” button. Once you name your Task, you’ll click on it and select the “Add Action” button. This will bring up the Action Dialog box. Here we need to select the If/else block action in the Control Structures section of the Action Dialog box. Once we have our If block in the task, we’ll want to add two more actions inside of the If/else block by selecting the “Add Action” button inside of the If/else block. Here we’ll select the Pulse Output Relay action inside the conditional part of the If/else block , and the Pulse Output Relay action inside for the “else” part of the If/else block.
Setting the If/Else Block Actions
With the actions being added to the Task, we can now configure them to do what we want. For this example, we are going to configure the If block to Pulse Output Relay 1 when Input 1 goes high, and Pulse Output Relay 2 when Input 1 isn’t high. For the If/else block value field, to check if the input is high we’ll enter din.state == 1. For the first Pulse Output Relay, we’ll set the channel to 1, and for the other pulse relay we’ll set the channel to 2.
With this, the If/else block should Pulse Output Relay 1 for 1 second when Input 1 is high, and Pulse Output Relay 2 for 1 second when Input 1 is not high.
The Tasker application has been made to handle lots of different types of functionality. This post will go into looking at the Set Variable action and then a logic example using the set variable to send fire alarm macros to different devices. Doing this example requires the environmental or temperature sensor to be completed.
The Set Variable Action
The Set Variable Action allows you to create a variable in the first value field of the action, and then assign it a value in the second value field. This is useful when using other control structure actions, such as loops or if blocks.
Fire Alarm Example
In this Example, before we create the Fire Alarm Task, we need to create the devices that will receive the macro we send for the fire alarm, like shown above. You’ll also need to the have the Cinema application updated to your JNIOR. To start, go to the device tab and click the “Add Device” button. Add as many Devices as you have JNIORs you plan to send a Fire Alarm macro to. Each device you’ll enter its IP address, and TCP Port number from the Cinema Server Client Registry Key. The Registry Key is under AppData/Cinema/CinemaServerClient/TcpPort in the registry tab of the JNIOR’s webpage.
After creating the devices to send macros to, you’ll start creating the task. It starts with the Set Variable actions. These actions are used to define the values of two temperatures received from a temperature sensor or environmental sensor, and the variable used to know when to end the Task. We define the two Temp variables to values our temperature or environmental sensors are picking up, and the other variable will be set to true as our conditional until the macros get sent. Once these values are defined, a while loop is added to the task. This will check if the conditional of the variable we created is true, which is how we set it so that it will always be looping. After that, we add an if block and set the conditional of it. This is to determine if the movie theater’s screen room is a lot more hotter then the rest of the movie theater, indicating a possible fire. When the temperature difference is above 20 degrees (indicating a possible fire), using as many TCP send actions for devices you have, it sends to those JNIORs to run their FireAlarm macros. It also sets the conditional for the while loop to false, so the task no longer loops, and ends.
With this, you should have a task that constantly monitors the temperatures of two temperature/environmental sensors, and when the difference between them is greater then 20, sends out the fire alarm macros and ends the task.