RAM Memory Reset – Series 4 JNIOR

In rare instances, Series 4 JNIORs can become unresponsive. This can happen for example when a JNIOR is interrupted when their OS is being updated, or when the JNIOR has a network lockup. When this happens, their is an unconventional way to get the JNIOR working. Here are the steps to potentially get your Series 4 JNIOR operating again. This process requires you to physically have the JNIOR near you, along with a business card (or something similar and non-conductive) and a Phillip screw driver.

Take Off Lid of the JNIOR Case

To start, we need to remove power from the JNIOR, as we are going to open the JNIOR case. Once the JNIOR has no power, we need to remove the lid of the JNIOR case to access the JNIOR’s coin battery on its circuit board. There are 4 screws that keep the JNIOR lid on, and they can be removed with a Phillip’s screw driver. Once removed, the case’s lid should easy come off.

Find the Coin Battery

Once the lid is removed, you should see the coin battery at the top middle of the JNIOR’s circuit board. Notice there is a metal contact plate on top of the battery. The metal contact plate and the coin battery need physically interrupted from touching each other.

Separate Coin Battery from the JNIOR

Slip the business card between the coin battery and metal contact plate. This will disconnect the JNIOR’s RAM from the battery. Once the business card is in place, power up the JNIOR for 30 seconds, giving the JNIOR enough time to reset the RAM memory. After 30 seconds, remove power from the JNIOR again, remove the business card, re-attach lid to the JNIOR, and then power up the JNIOR again. Hopefully with this, the JNIOR should be working properly!

NOTE: If you don’t have a business card or something similar, you can also just remove the coin battery as well.

To re-iterate the steps taken:

  1. Power down the JNIOR
  2. Remove JNIOR’s case lid
  3. Locate coin battery
  4. Insert business card between coin battery and metal contact plate
  5. Power on JNIOR for 30 seconds
  6. Power down the JNIOR
  7. Remove business card
  8. Re-attach JNIOR’s case lid
  9. Power on the JNIOR
By | On October 20, 2023 10:01 am | No Comments |

Updating a JNIOR’s Operating System

On every JNIOR is JANOS (JNIOR Automation Network Operating System). This is installed when the JNIOR is being made. Overtime, the operating system gets older, while here at INTEG we are always creating newer versions that improve upon the last. With each release we typically fix bugs and add functionality. To avoid running into issues with older JANOS OS versions, we typically tell customers to stay up-to-date with each JNIOR’s JANOS OS version. Below is how you update your JNIOR with the latest OS.

Below are the downloads for the JNIOR Support Tool, and two separate Update Projects that will install the latest JANOS OS version on your JNIOR. The Support Tool is needed in order to update a JNIOR with an update project. As for the update projects, there is the All-in-one Update Project and the Core Update Project. The All-in-one Update Project updates the JANOS OS, but it also updates a few applications that come bundled with the All-in-one Update Project such as, Modbus, Serial Control, Serial-to-Etherent, SNMP, and Slaving. The Core Update Project just updates the JANOS OS. Both will work for updating the JNIOR’s OS, so choose one that you’ll use to update the JNIOR.

Name Version Release Date Size MD5
JNIOR Support Tool v7.16 Jun 12 2024 6.2 MB c960367efcc4628a8d909e5861ea20b6
Series 4 All-In-One Update Project v2.4.2 Jan 18 2024 1.8 MB 293c415caba1ff6d9b9a404be3430cc2
Core JANOS Update Project v2.5 Jun 21 2024 1.3 MB d3783d7ec82ed4ee34bfc356d0953a56

After installing the JNIOR Support Tool application and downloading one of the Update Projects, 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 Update Project you downloaded. When you open one of the Update Projects in the Support Tool you will see something similar to the following:

Click Publish and select the JNIOR you want to update. Once the update is complete the JNIOR will have rebooted and the JANOS OS should be up to date. 

By | On October 20, 2023 10:00 am | No Comments |

Updating a JNIOR with the Support Tool

One of the features of the Support Tool is being able to use it to update JNIORs with software. This is done with update projects, which load files and configuration settings onto the JNIOR in a step-by-step order. This post will go over how to Open, Create/Edit, Close, and Publish/Cancel update projects to the JNIOR.  

Opening an Update Project

In order to update your JNIOR with an update project, you first need to have an update project downloaded to use. For this example, we’ll use the JNIOR Core update project, which will update your JNIOR with the latest JANOS OS available onto your JNIOR. Here is a download for the update project. NOTE: Update Projects are zip files, do not unzip it once its downloaded. 

Name Version Release Date Size MD5
Core JANOS Update Project v2.5 Jun 21 2024 1.3 MB d3783d7ec82ed4ee34bfc356d0953a56

Once you have downloaded this update project, we then need to open it in the Support Tool. You do this by clicking the Open Project button in the Update tab of the Support Tool. This will open your computers file explorer, and you’ll navigate to the update project that you just downloaded. Select it and hit open in the file explorer, and you should now see the update project and its steps displayed in the JNIOR Support Tool Update tab. This means you’ve successfully opened an update project.

Creating/Editing an Update Project

While our website has tons of update projects for different applications already made, you may want to create your own or edit one that already exists. To create a new update project, go to the Update tab of the support tool and select Edit Project Configuration while no update project is open in the Update tab. Once selected, you’ll now see a new window open for editing/creating projects. To create a new project, you have to give it a name in the Title field before you can begin adding steps. Once a title is given, you can steps using the Add Step button at the bottom left. Steps in an update project are executed from top to bottom. Selecting a step and clicking the UP or DN buttons shifts that step up or down in the execution order. When you are done, you can select the Package button to generate your update project.

To edit an existing update project, you open it in the Support Tool, and then select the Edit Project Configuration button. Once selected, you’ll now the new window open for editing/creating projects, but this time with all the steps that are currently inside the opened update project.

Update Project Steps

Update Projects can perform a multitude of actions on a JNIOR. The following are the available steps that can be added for an update project:

  • Registry Key
  • Update Registry
  • Delete File
  • Make Remote Directory
  • Reboot
  • Load Application
  • Transfer File
  • Clean Up
  • Preserve Files
  • Restore Files
  • Telnet Command
  • Transfer Zip
  • Update Series 3 OS
  • Update Series 4 OS

Publishing an Update Project

Once an update project has been opened or created, it can now be loaded on to a JNIOR by publishing it. While the update project is open in the support tool, you’ll click on the Publish button. This will open a new dialog box to select which JNIORs you want to apply your update project to. You can select as many JNIORs as are available in the Beacon tab to publish to. The update project will publish to whichever JNIOR’s you select the checkbox next to. Once you have selected the JNIORs you want to publish to, hit OK. You’ll then see the Support Tool begin to follow the steps inside the update project for each JNIOR selected.

Cancelling an Update Project

While an update project is being published to, you can cancel it if needed. While an update project is publishing, select the Cancel button to stop the update project from being applied to JNIORs.

By | On October 20, 2023 10:00 am | No Comments |

Accessing JNIORs Using The Support Tool’s Beacon Tab

When interacting with the JNIOR, the easiest way to see which ones are on your network and access them is through the Beacon tab of the JNIOR Support Tool. The Beacon tab shows all the JNIORs on the network that respond to the Beacon protocol, which is a UDP message sent on port 4444. When JNIORs report back to Beacon, they provide useful information about themselves in the Beacon tab such as their Serial Number, Hostname, IP Address, OS Version and more.

Each column of data presented in the Beacon tab can be sorted, alternating from ascending and descending, by clicking on the column header.

JNIOR Dropdown Options

Right clicking a JNIOR in the Beacon tab opens a dropdown menu that allows you to access or configure  JNIORs in many ways. Below are all the options in the dropdown menu:

Query

  • Identify – causes the amber LED to rapidly flash for 5 seconds on the JNIOR.
  • Query – sends a Beacon request to the selected JNIOR .
  • Query All – sends a request to all JNIORs on the network and those that have Beacon enabled will respond.
  • Query New – sends a request to all JNIORs on the network and only those that have Beacon enabled and set as ‘new’ (default setting) will respond.
  • Query Range – define a range of IP Addresses to directly send a beacon request to. Similar to the JNIOR list, but doesn’t save the IP Addresses as a file for future requests.
  • Auto Query – allows you to set an automatic sending of a Query All or Query New at a user defined time period
  • Send Query To… – opens a new dialog, and sends a Beacon request to the JNIOR with the IP you define in the dialog.

Configure

  • Identify – causes the amber LED to rapidly flash for 5 seconds on the JNIOR.
  • Set Hostname – allows you to enter the hostname for the JNIOR and will be displayed in the Beacon window.
  • IP Configuration – allows you to configure the IP address of the selected JNIOR and set its Time zone.
  • Registry Editor – opens the Registry Editor tab in the support tool.
  • Reset Attention Flag – clears the message field for a JNIOR in Beacon if it is caused by a flag.

Tools

  • Open Web Page – opens the JNIOR Web Page for the selected JNIOR.
  • Open Telnet – launches a window that allows you to make a command line connection to the JNIOR using a TCP or Serial connection. Here is a link to different telnet commands a JNIOR can be given.
  • Open FTP – Opens the file explorer for a JNIOR, allowing you to access files on it like you would on your PC.
  • Open Classic Monitor, Configure, Control Application – Opens the Java applet for the selected JNIOR (This opens the Java Applet Configuration Page, and is only available for Series 3 JNIORs. Use the JNIOR Web Pages to configure Series 4 JNIORs.)
  • Open Task Manager Application – opens the Task Manager application for the selected JNIOR.
  • Macro Execution – Opens the Macro Executor and enters the selected JNIORs IP into it. Allows you to test macros you created for the JNIOR.
  • Show JniorSysLog – displays the JNIOR’s system log.
  • Set Time – sets the current time for the JNIOR.

JNIOR List

NOTE: The JNIOR List is an unfinished feature, designed to target an IP Address with the Beacon Protocol, rather then it typically broadcasting it to the entire network.

  • Create New – Create a file that contains the IP Addresses of JNIORs you wish to target with the Beacon Protocol.
  • Open – Open an already created JNIOR List file.
  • Edit – Edit an existing JNIOR List file.
  • Close – Close an already open JNIOR List file.
  • Preview – View an already created JNIOR List File.

Reboot

This will reboot the selected unit. After a few seconds, the JNIOR will drop out of Beacon as it will briefly turn off. Once it reboots, it will respond to the Beacon Protocol and return to the Beacon tab.

JNIOR Support Tool Footer

Some useful information is displayed at the bottom of the Beacon Tab. On the left is the JNIOR count, showing the total amount of connected JNIORs and their model types. On the right is the currently opened JNIOR list. This can be useful to quickly check if all your units are connected on the network or not.

By | On October 20, 2023 10:00 am | No Comments |

Taking Snapshots and Backups in the Support Tool

JNIORs have the ability to backup their configurations in update projects and zip files using the Snapshot tab. This is useful when wanting to copy a JNIOR configuration across multiple other JNIORs, or as a failsafe incase a JNIOR loses its configuration or needs to revert to a previous one.

Snapshots

Starting with Snapshots, a Snapshot is a copy of your JNIOR’s configuration saved as a .zip file. Snapshots are used as a debugging tool by INTEG, and should be submitted on our website when you need support. You can take one by selecting the Take Snapshot button at the top left of the Snapshot tab. When this button is selected, a small dialog window will pop up, explaining what a Snapshot is and prompting if you want to continue. Clicking yes will bring up a JNIOR selection screen, where the selectable JNIORs are all ones that are appearing in the Beacon tab. Once one or more JNIORs are selected, pressing okay will start the Snapshots for each JNIOR. The window on the right side of the Snapshot tab will display the progress for the Snapshots being taken. Click here for a more in-depth walkthrough for taking a Snapshot.

Backups

A Backup is similar to a Snapshot, but the difference is that Backups can be opened in the Update tab and published to other JNIORs, copying their configuration to them. Since Backups are similar to Snapshots, taking a Backup has a similar process to Snapshots as well, where and you can take one by selecting the Take Backup button at the top of the Snapshot tab. When this button is selected, a small dialog window will pop up, explaining what a Backup is and prompting if you want to continue. Clicking yes will bring up a JNIOR selection screen, where the selectable JNIORs are all ones that are appearing in the Beacon tab. Once one or more JNIORs are selected, pressing okay will start the Backups for each JNIOR. The window on the right side of the Snapshot tab will display the progress for the Snapshots being taken. When the Backup has finished, it will ask you what you want to name the Backup. Once a name is given, it will then ask if you want to open the Backup that was just taken as an update project in the Update tab.

Filter

The Filter defines particular files to be grabbed when generating a Snapshot or Backup, specifically defining what file extensions should be included. To set a Filter, you’ll select Filter button at the top of the Snapshots tab. When selected, a dropdown appears for a few pre-defined file extensions. At the bottom of the dropdown is a custom filter, which opens a separate dialog and allows you to add whatever extensions you are looking to grab when generating a Snapshot/Backup. While this filter is active, any files without the file extensions you include in the filter will not be grabbed when your Snapshots/Backups are created.

Cancel

There may be a time when you want to stop a Snapshot or Backup from being taken. You can select the Cancel button at the top of the Snapshot tab to do this.

By | On October 20, 2023 9:59 am | No Comments |

Editing a JNIOR Registry from the Support Tool

A JNIOR’s registry can be edited from the JNIOR Support Tool using the Registry tab. The Support Tool Registry Editor uses a JNIOR Protocol connection to do this. To start, you’ll need to go to the top left of the Registry tab and select Add JNIOR. This will open a JNIOR selection screen, where the selectable JNIORs are all ones that are appearing in the Beacon tab.

Once you’ve selected your JNIORs by clicking the checkbox next to each, you’ll hit Okay and see that each JNIOR’s registry will be displayed in the Registry tab of the Support Tool. Each JNIOR’s Registry Editor will have its own separate tab with its IP as its label. To close a Registry Editor, simply select the Remove JNIOR button while on that JNIOR’s tab.

Depending on what you have selected, different configuration options will be available in the JNIOR Registry tab. The following is what each option does:

  • Disconnect – Disconnects the JNIOR Protocol connection for the Registry Editor and closes its tab.
  • Add a Registry Key – Can be used when a Registry Key or Registry Folder is selected. Adds a Registry Key in the selected directory location.
  • Edit a Registry Key – Can be used when a Registry Key is selected. Edits the value of a Registry Key.
  • Remove Registry Key – Can be used when a Registry Key is selected. Removes the Selected Registry Key.
  • Add Registry Folder – Can be used when a Registry Key or Registry Folder is selected. Adds a Registry Folder in the selected directory location.
  • Delete Registry Folder – Can be used when a Registry Folder is selected. Deletes the Registry Folder.
  • Refresh Folder – Refreshes the selected Folder, making it display the current status of all Registry Keys and Folders within it.
By | On October 20, 2023 9:59 am | No Comments |

Grabbing Logs Using the Support Tool

Sometimes when trying to get reports from your JNIORs, rather then going through their logs one at a time, you could aggregate them together and view them all at once. The Logs tab in the JNIOR Support Tool does just that.

There are two locations you can aggregate logs from. One location you can aggregate logs from is your computer, which can be done by selecting the Aggregate Saved Logs button at the top left of the Logs tab in the Support Tool. You can also aggregate logs directly from a JNIOR by selecting the Aggregate Logs from JNIOR button at the top of the Logs tab in the Support Tool. Once the JNIOR or location on the PC is selected, the Support Tool then shows all the logs it finds there and allows you choose which ones are included or not when aggregated. After that, the Support Tool then combines all time-stamped data from the selected logs into one, adding the data in chronological order.

Once the aggregated log is generated, additional options become available at the top of the Logs tab:

  • Save Current View – Save the aggregated log.
  • Print Preview – Open the print preview of the aggregated log.
  • Print – Print the aggregated log.
  • Filter – Adds a filter to search for data in the aggregated log between a specified time frame.
  • Clear Filter – Clears any filter set.
  • Close – Close the aggregated log.
By | On October 20, 2023 9:59 am | No Comments |

Disabling the RS-232/COM Serial Ports Boot Dialog

When doing Serial Communication on the JNIOR, there are two serial ports that you can can choose from. The AUX port and the RS-232/COM port. We always recommend using the AUX port, because while you can use the RS-232/COM port, its primarily used for diagnostic and debugging use. The RS-232/COM port has a boot dialog enabled by default for this, and in order to send serial data out the RS-232/COM port without issues, it needs to be disabled. If not disabled, the boot dialog will get sent out along with your data. Below is how to disable the boot dialog for the RS-232/COM Serial port.

NOTE: This is for Series 4 JNIORs, Series 3 JNIORs cannot disable the boot dialog. As mentioned previously, the RS-232/COM port can still receive data while the boot dialog is on, but cannot send data out without encountering issues.

In the JNIOR Web Page, navigate to the Serial I/O section in the Configuration tab. Under the RS-232/COM Serial port settings, you’ll uncheck the Enabled option for Boot Dialog. After this change, you’ll need to reboot for it to take effect.

By | On October 13, 2023 2:18 pm | No Comments |

Creating Devices in the Support Tool Device Tab

The Support Tool has a Device tab, which allows you to declare ethernet and serial devices, and once linked to your macro file, allows you to include them in your macros. This post will go over the Device tab, and how to create/open Device files that your macros can use to send commands to them. 

Creating a Device File

Once on the Device tab, you should see an empty window, with columns representing the different data that can be filled out for each device. At the bottom of the Device tab should be an empty table. The Device and Macros files that are created from these tabs are CSV (comma separated values) files. The table at the bottom reflects the devices you create in the window above it. To add a new device, you can select the Add button at the bottom left of the empty window. Once the device is added you can define the following settings for each device:

  • Device Name – Name of device that will be used when referencing it in the Macro file. NOTE: Cannot contain spaces.
  •  Device Type – Contains predefined devices that can be sent to from the JNIOR. Selecting a predefined device will populate other device settings for you for easier setup. If the device you are using isn’t listed, that’s okay! You can define a general device type yourself by using a Raw Ethernet, Raw UDP, or Raw Serial device depending on the type of connection you need to use to communicate to the device.
  • IP Address – For Ethernet or UDP devices only. Enter the IP Address of the device you are trying to communicate with here.
  • Port – Changes depending on if its a Ethernet/UDP device versus a Serial Device. If its a Ethernet or UDP device, enter the Port Number of the device you are trying to communicate with here. If its a Serial Device, select which Serial port on the JNIOR you are using. (We recommend using the AUX port. You can use the RS-232/COM port, but this is typically used for diagnostic and debugging use. If you’re not using the AUX port, you’ll need to disable the boot dialog for the RS-232/COM port to send data out of it. )
  • Baud – For Serial devices only. Enter the Baud Rate for the Serial device you are using.
  • Data Bits – For Serial devices only. Enter the Data Bits for the Serial device you are using.
  • Parity – For Serial devices only. Enter the Parity for the Serial device you are using.
  • Stop Bits – For Serial devices only. Enter the Stop Bits for the Serial device you are using.
  • Termination String – This is optional, and should be used if your device expects a termination string at the end of each command it receives.

Once you’ve filled out your Device’s settings. You then need to save and publish your Device file. Right under the Support Tool tabs at the top of the Device tab, you’ll want to select the Save As button. This will open your file explorer, and you need to save this file anywhere inside the files folder of your Support Tool Directory (This is where the file explorer should automatically open to, so you can save right where the file explorer opens to.)

Once the file is saved on your computer, you’ll then need to publish the file you save to the JNIOR. Right next to the Save As button is the Publish to JNIOR button. This will bring up a JNIOR selection screen, where you can select any JNIOR appearing in Beacon to publish to. Once the JNIORs have been published to, the device file should now be loaded onto the JNIOR, and can be linked to a JNIOR macro file.

Opening a Device File

Instead of creating a Device file, you can open one that has already been created and saved. Selecting the Open Local File button will open your file explorer to where Device files are saved on your PC. Here you can select one you wish to open, and it will populate into the Support Tool Device tab. You can also select the Open Remote File button, which will open a JNIOR selection screen and allow you to open a Device file that is loaded on a JNIOR.

By | On October 13, 2023 1:39 pm | No Comments |

Update Project Steps

Registry Key

Create and/or set a registry key on the JNIOR with a value. The RegKey cell must contain the exact text and capitalization needed for the Registry key. The RegValue cell must contain an acceptable value for the Registry key. The RebootRequired cell can be set to false or true to indicate if a reboot is required as a result of this step. A Reboot Step must also be included in the Project to trigger a reboot after this step is executed. The user can edit the Name cell for
display purposes in the Step list window on the left.

Update Registry

Grabs an .ini file from you PC and uploads it to the selected JNIOR. This will update the registry with the one saved as the .ini file.

Delete File

Delete a file on the JNIOR. The user must enter the file name in the RemoteFile cell and any folder name where the file is stored (besides the root directory) in the RemoteFolder cell. The user can edit the Name cell for display purposes in the Step list window on the left.

Make Remote Directory

Create a new folder (directory) on the JNIOR for storing an application or other file. The user must enter the folder name and any path in the RemoteFolder cell. The user can edit the Name cell for display purposes in the Step list window on the left.

Reboot

Reboot the JNIOR during the execution of the project. A reboot must occur to update the JNIOR OS, or stop and start an application or for some Registry setting changes to take effect. If any of the steps require a reboot, then a Reboot step must be included in the project to respond to the reboot flag set by one of the other steps. The user can also set the ClearSystemMemory to true to clear the RAM memory on reboot. This deletes all the logs and some other temporary files, but does not delete anything in the flash memory (same as a reboot –a command). The user can also set the MustReboot option to true to force a reboot regardless of the previous steps. The user can edit the Name cell for display purposes in the Step list window on the left.

Load Applications

Can be used to load any application. You do NOT need to have a version or version location registry key (location) defined. If a version number is available, the Load Application Step will check it and compare the version numbers. You can also use the Generic File Transfer Step to transfer an application besides a standard INTEG application.

Transfer

There are several types of file transfer functions available. There is a generic File Transfer Step and two specific steps for use with the Cinema.JNIOR application.

  • File Transfer – Allows the user to transfer a file to the JNIOR. The location of the file on the PC must be selected via the LocalFile cell and the location for the file on the JNIOR must be entered in the RemoteFile cell. The file can be transferred to a specific folder on the JNIOR by entering the complete path in the RemoteFolder cell.
    NOTE: The folder on the JNIOR must exist or must be created with a Make Remote Folder Step prior to this step. The user can rename the file and the Support Tool will change the name of the file before it is transferred to the JNIOR. A file on the JNIOR with the same name will be removed before transferring the new file (RemoveFirst). The user can edit the Name cell for display purposes in the Step list window on the left.
  • Cinema Macro File – Allows the user to transfer a Macro file used by Cinema.JNIOR. This step is different than a Generic File Transfer because it will first check the JNIOR to see if a macro file exists with the same name or a different name. In either case, it will delete the macro file so that only one macro file exists on the JNIOR. The location of the file on the PC must be selected via the LocalFile cell. The name for the file on the JNIOR must be entered in the RemoteFile cell and must be macro_xxx.csv (where xxx can be anything) to be recognized by the
    Cinema.JNIOR program. The file can only be transferred to the root directory. The user can edit the Name cell for display purposes in the Step list window on the left.
  • Cinema Device File – Allows the user to transfer a Devices file used by Cinema.JNIOR. This step is different than a Generic File Transfer because it will first check the JNIOR to see if a devices file exists with the same name or a different name. In either case, it will delete the devices file so that only one devices file exists on the JNIOR. The location of the file on the PC must be selected via the LocalFile cell. The name for the file on the JNIOR must be entered in the RemoteFile cell and must be devices_xxx.csv (where xxx can be anything) to be recognized by the Cinema.JNIOR program. The file can only be transferred to the root directory.

Clean Up

Allows you to delete one or more files on the JNIOR. When the user clicks in the Remote Files cell, a window will pop-up allowing the user to enter the file names and/or folder/filenames of the files to be deleted. The user can edit the Name cell for display purposes in the Step list window on the left. 

Preserve/Restore Files

These steps should be used together. The preserve will save certain files from you JNIOR to keep and then the Restore will reset the JNIOR then load the files saved back onto that JNIOR.

Telnet Command

Allows you send a telnet command through the command line, allowsing for example a “reboot” command to reboot the JNIOR or a “ps” command that will show you which process on the JNIOR are running.

Transfer Zip

Allows you to send the contents of a zip file to a JNIOR.

Update Series 4 OS

Allows the user to transfer a upd update file to the JNIOR operating system. This file is provided by INTEG, as needed. When the user clicks in the Local File cell, clicking on the icon with three dots will allow the user to navigate to the location of this file. The Support Tool will pull this file from the remote location and put it in a local folder. The JNIOR OS version is automatically detected and displayed in the Version cell. The Option to reboot the JNIOR is set as true by default. This causes the JNIOR to reboot immediately after the file is transferred. The user could set this to false and utilize the Reboot Step later in the project. The user can edit the Name cell for display purposes in the Step list window on the left.

Update Series 3 OS

Allows the user to transfer a jr310.upd file to update the JNIOR operating system. This file is provided by INTEG, as needed. When the user clicks in the Local File cell, clicking on the icon with three dots will allow the user to navigate to the location of this file. The Support Tool will pull this file from the remote location and put it in a local folder. The JNIOR OS version is automatically detected and displayed in the Version cell. The Option to reboot the JNIOR is set as true by default. This causes the JNIOR to reboot immediately after the file is transferred. The user could set this to false and utilize the Reboot Step later in the project. The user can edit the Name cell for display purposes in the Step list window on the left.

By | On October 11, 2023 3:43 pm | No Comments |

All-In-One Releases
Name Version Release Date Size MD5
JNIOR Support Tool v7.16 Jun 12 2024 6.2 MB c960367efcc4628a8d909e5861ea20b6
Series 4 All-In-One Update Project v2.4.2 Jan 18 2024 1.8 MB 293c415caba1ff6d9b9a404be3430cc2

August 10, 2021

  • Core
    • JANOS 2.1
    • DCP (WebUI) 3.1.0
    • Manpages
  • Bundled
    • FTP Client
    • JBakup [ADDED]
    • MODBUS Server 1.7
    • Serial Control 7.0
    • Serial To Ethernet 6.1
    • Slaving Service 2.0
    • SNMP 3.1
    • Tasker 6.0
    • Task Manager 7.0

March 4, 2021

  • Core
    • JANOS 2.0 build 1.0
    • DCP 3.0.1
  • Bundled
    • FTP Client
    • MODBUS Server 1.7
    • Serial Control 7.0
    • Serial To Ethernet 6.0
    • Slaving Service 2.0
    • SNMP 3.1
    • Tasker 6.0
    • Task Manager 7.0

February 3, 2021

  • Core
    • JANOS 2.0 build 1.0
    • DCP 3.0.1   (Moved to flash/www/config.zip)
  • Bundled
    • FTP Client
    • MODBUS Server 1.7
    • Serial Control 7.0
    • Serial To Ethernet 6.0
    • Slaving Service 2.0
    • SNMP 3.1
    • Tasker 5.0
    • Task Manager 7.0

February 2, 2021

  • Core
    • JANOS 2.0
    • DCP 2.4
  • Bundled
    • FTP Client
    • MODBUS Server 1.7
    • Serial Control 7.0
    • Serial To Ethernet 6.0
    • Slaving Service 2.0
    • SNMP 3.1
    • Tasker 5.0   [ADDED]
    • Task Manager 7.0

May 1, 2020

  • Core
    • JANOS 1.9
    • DCP 2.4
  • Bundled
    • FTP Client
    • MODBUS Server 1.7
    • Serial Control 5.0
    • Serial To Ethernet 6.0
    • Slaving Service 1.5
    • SNMP 2.6 – UPDATED
    • Task Manager 7.0

February 3, 2020

  • Core
    • JANOS 1.9 – UPDATED
    • DCP 2.4 – UPDATED
  • Bundled
    • FTP Client
    • MODBUS Server 1.7
    • Serial Control 5.0
    • Serial To Ethernet 6.0
    • Slaving Service 1.5
    • SNMP 2.4.1
    • Task Manager 7.0

June 18, 2019

  • Core
    • JANOS 1.8
    • DCP 2.3
  • Bundled
    • FTP Client
    • MODBUS Server 1.7
    • Serial Control 5.0
    • Serial To Ethernet 6.0
    • Slaving Service 1.5
    • SNMP 2.4.1
    • Task Manager 7.0
By | On October 10, 2023 1:38 pm | No Comments |

Mean Time Between Failures – MTBF

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.

  1. The mechanical relays should be able to see a minimum of 100,000 closures.
  2. 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.
By | On October 10, 2023 10:02 am | No Comments |

Snapshots – JNIOR Supporter

A panel on the right side of the JNIOR Supporter is for taking snapshots and issuing update projects. Snapshots are copies of JNIOR configurations, which can be used to either debug issues a JNIOR may be having or as an update project to duplicate its configuration to other JNIORs. Below is how to take Snapshots.

When selecting the Snapshots tab, snapshots are displayed in groupings based on different filters. The filters sort by the following: Serial Number, Hostname, Date, and Other. Selecting the ‘Take Snapshot’ button lets you select which JNIOR you want to generate a snapshot of. Once selected, each snapshot will populate inside the Snapshot Progress tab in the lower display panel, and notify you when completed. Selecting the ‘Open Snapshots Directory’ tab will open the file directory in your file explorer where Snapshots are saved locally on your PC. This can also be done by right clicking a snapshot in the Snapshot tab and selecting ‘Show in Folder’.

By | On September 28, 2023 2:56 pm | No Comments |

Update Projects – JNIOR Supporter

A panel on the right side of the JNIOR Supporter is for taking snapshots and issuing update projects. Update Projects are zip files that contain instructions to Update/Install applications or settings to a JNIOR. Below is how to take/distribute Update projects and Snapshots.

When selecting the Update Projects tab, there are two sections of Update Projects: Official Updates from Jnior.com and Local Update Projects. The first section is populated with the most recent Update Projects on INTEG’s website. When viewing the Update Projects for a specific application, the name of the Update Project may or may not be grayed out. Grayed out Update Projects are still selectable, but just represent whether or not the Update Project has been downloaded locally. A grayed out name means it is already downloaded locally. Opening an update project that isn’t grayed out will automatically download it from our website to open it, granted you have an internet connection. The Local Update Project section is for Update Projects that are custom made (either by yourself or from INTEG), or an older version of an official release on INTEG website. When one or multiple Update Projects are selected, you can hit the ‘Open Selected’ button at the top of the Update Projects tab to launch the Update Projects in the bottom panel of the JNIOR Supporter. Hitting the ‘Open Updates Directory’ will open the file directory in your file explorer where Update Projects are saved locally on your PC.

Once an Update Project is opened and displayed in the bottom panel of the JNIOR Supporter, you can then close, edit, publish, or abort the Update Project. Closing the Update Project will simply remove it from the bottom panel of the Java Supporter, and can be opened again from the Update Projects tab on the right panel. Editing the Update Project will allow you to view in detail each step of the Update Project, and change it as needed. Aborting an Update Project can only be selected once an Update Project begin publishing to a JNIOR, and simply cancels the Update Project where its currently at. Lastly, publishing an Update Project lets you select which JNIORs from the Beacon Tab you wish to publish to. (If they are on the network and not displaying in Beacon, you can manually enter in there IPs to publish to them.) Then once selected, the Update Project goes through each step and performs it on the selected JNIOR(s). These steps range from loading applications on the JNIOR, changing registry keys, rebooting, and more. Progress on publishing the Update Projects is shown in the Update Progress Tab, will notify you when completed.

By | On September 28, 2023 1:57 pm | No Comments |

Beacon Customization – JNIOR Supporter

When using the JNIOR Supporter, you may notice that not all the information from the Beacon tab can be displayed at once. To make specific JNIOR data easier to view, you can modify the Beacon tab to change the order and width each column has, or remove columns all together. When on the Beacon tab of the JNIOR Supporter, while clicking and holding on the left or right border of a column header, you can drag how much or how little each columns width is. If you hold down on the middle of the column header, you can drag where you want the column to be between the other columns. If you don’t want a column displayed, under the Beacon tab is the ‘Select Columns’ option. Unchecking a columns checkbox and selecting OK removes the column from Beacon. Any changes made to Beacon are persistent, so you don’t need to reset them every time you launch the JNIOR supporter.

By | On September 28, 2023 12:55 pm | No Comments |

Support Tool 7.15 Minor Update
Name Version Release Date Size MD5
JNIOR Support Tool v7.16 Jun 12 2024 6.2 MB c960367efcc4628a8d909e5861ea20b6

[!] Minor update to the JNIOR Support Tool to restore Series 3 functionality. There was a bug that prevented a user from being able to set the Hostname, Configure the IP Address, and Reboot a series 3

JNIOR Support Tool 7.15 Release September 8, 2023

[!] Rolls back the .NET requirement to .NET version 4.0. 7.14 required an upgraded version of .NET, version 4.8. Some people reported being unable to install .NET 4.8 on older computers.

The initial upgrade to .NET 4.8 was due requirement for TLS 1.2. It turns out that .NET 4.0 has the ability to use TLS 1.2 but it needs to be enabled a special way.

[!] Fixed an issue preventing the Support Tool from closing completely. Instances would continue to run in the background.

JNIOR Support Tool 7.14 Release May 17, 2023

[+] Can now select multiple JNIORs to Identify or Reboot at once.

[+] Added the ability for the Support Tool to check our website for the latest Series 4 All In One.  This will help you stay up to date.

+ Added the ability to submit to INTEG without having to go to our website and select the snapshot.  Form will be available in the Support Tool

! Minor Bug Fixes

JNIOR Support Tool 7.10 July 15, 2020

! Corrected an issue where opening an update project would encounter a non-empty temp folder.

+ Added the ability to open multiple Device files

+ Added the ability to open multiple Macro files

+ Added the ability to open multiple Update Projects

! addresses an issue where the Update Notification was always being shown at startup, even when the most recent version was on the JNIOR.

JNIOR Support Tool 7.9 May 16, 2019

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

JNIOR Support Tool 7.15 Release

[!] Rolls back the .NET requirement to .NET version 4.0. 7.14 required an upgraded version of .NET, version 4.8. Some people reported being unable to install .NET 4.8 on older computers.

The initial upgrade to .NET 4.8 was due requirement for TLS 1.2. It turns out that .NET 4.0 has the ability to use TLS 1.2 but it needs to be enabled a special way.

[!] Fixed an issue preventing the Support Tool from closing completely. Instances would continue to run in the background.

JNIOR Support Tool 7.14 Release May 17, 2023

[+] Can now select multiple JNIORs to Identify or Reboot at once.

[+] Added the ability for the Support Tool to check our website for the latest Series 4 All In One.  This will help you stay up to date.

+ Added the ability to submit to INTEG without having to go to our website and select the snapshot.  Form will be available in the Support Tool

! Minor Bug Fixes

JNIOR Support Tool 7.10 July 15, 2020

! Corrected an issue where opening an update project would encounter a non-empty temp folder.

+ Added the ability to open multiple Device files

+ Added the ability to open multiple Macro files

+ Added the ability to open multiple Update Projects

! addresses an issue where the Update Notification was always being shown at startup, even when the most recent version was on the JNIOR.

JNIOR Support Tool 7.9 May 16, 2019

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

JANOS 2.4.1 Release
  • Resolved HELP manual generation paging issue
  • Enhanced TAB auto-fill to work when editing a line
  • Allow you to force context for auto-fill using Ctrl-F and Ctrl-R
  • Fix memory ownership issue with cstring_t
  • Fixed DATE command problem introduced with v2.4
  • Increased ARP database size
  • Corrected issue with Thread.interrupt use before the thread starts
  • Added network performance information to NETSTAT
  • Added bandwidth information to NETSTAT -A
  • Added PS -H showing a history of operation.
  • Added shutdown messages to the system log file.

JANOS 2.4 Release May 3, 2023

  • Added hysteresis to garbage collection to eliminate GC storming
  • Fixed web server memory leak
  • Enhanced command line RM/DEL command to override confirmation on wildcard use
  • Allow multiple commands on a single command line using separators like ';'
  • Implemented command line '|' piping capability
  • Enhanced CAT command with HEAD and TAIL usage to support piping
  • Implemented command line conditional execution && and || syntax
  • Enhanced GC -M and GC -B memory analysis to report Java class information
  • Applications can optionally log to external SYSLOG server
  • Hostname in SYSLOG report includes jrS/N Birthname
  • Corrected direct JMP connection not forwarding console output
  • Corrected direct JMP connection File Read failure
  • Fixed issue with Java Sockets SoTimeout exceptions
  • Improved inter-process messaging to avoid queue assertions
  • Added command line real-time network sniffer with filtering
  • Added Email queue management
  • Corrected REGEX matching issue
  • Eliminated memory leak with JSON decode
  • Fixed Web Authentication. No longer gets stuck in loop.
  • Expanded command line history to 200 commands
  • Eliminated dormant message queue issues
  • Fixed FTPClient class issue with retrieving data
  • Corrected buffer overrun by command line parameters
  • Eliminated null pointer issue in network race condition
  • Enhanced MANIFEST to use optional database
  • Prevent illegal IP address settings blocking network use
  • Corrected buffer overrun caused by security scanners
  • Eliminated Resource Deadlock after assertion

JANOS 2.3 Release February 2, 2023

The release fixed an issue with the Ethernet becoming "locked up". The JNIOR could become unresponsive while servicing the network on busy networks.

Build 1.0

  • Corrected memory issue with KILL and message loop use
  • Corrected garbage collection issue with static classes in the JVM
  • Corrected memory issue with serial port buffer resizing
  • Delayed Java Thread startup to insure completion of initialization
  • Added KILL -A feature to terminate all applications

 

Initial (January 25 2023)

  • Initialized the Working Directory for command line scripting
  • Increased network frame buffers to improve throughput
  • Increased number of available application watchdogs from 8 to 16
  • Added WDT_SILENT so watchdogs can be used to schedule programs and not logged as triggered
  • Updated PS process listings to display pending watchdogs as scheduled execution
  • Improved PING statistics
  • Eliminated assertion in loading classes using InvokeDynamic
  • Eliminated memory leak in JVM class caching
  • Corrected IO signature performance with IO changes
  • Corrected TAB auto-complete issue with second parameter
  • PHP Registry lists now sorted by name
  • Eliminated chance of socket deadlock that would require a hard reboot
  • Added check for network during boot logging to avoid reboot loop

JANOS 2.2 Release June 28, 2022

This release was issued to support manufacturing and component changes forced by supply chain issues. Because of this, an update to the OS was required to handle this change. Units made June 22nd, 2022 or later will NOT be able to roll back to earlier version of JANOS.

  • Corrected bug in creating multidimensional arrays
  • Improved DEFLATE compression performance with binary files
  • Corrected issue with '%' sign when logging to the syslog
  • Fixed dropped serial character when port is closed
  • Added experimental debugging tools

JANOS 2.1.1 Release December 15, 2021

  • This release was issued to support manufacturing and component changes forced by supply chain issues and COVID

JANOS 2.1 Release August 10, 2021

All New Help system. Use the [Help Search] link in the lower right on the JNIOR Web UI.

  • Eliminated external SYSLOG Server related memory leak
  • Corrected Regex issue with the OR operation
  • Corrected PHP ereg() and eregi() functions
  • Implemented a greatly expanded Help System
  • Added PDF MIME type to the WebServer and Email systems
  • Corrected JRMON latched input [R]eset command, no longer affects relays
  • PHP read file access expanded to include ZIP virtual folders
  • Corrected PHP issues with JSON arrays
  • Corrected Order of Precedence issue with PHP mathematical expressions
  • Corrected the operation of Regex '*' and '+' quantifiers when used following a group
  • Corrected RENAME behavior when attempting to alter case of a filename
  • Enabled PHP logical string comparisons ==, !=, <, <=, >, and >=
  • Enhanced security for JANOS-Session-Id cookies
  • Corrected JANOS-Session-Id handling when multiple cookies are present
  • Improved non-volatile aspect of command line history
  • Corrected issue with network capture completion
  • Fixed issue introduced in v2.0 with IpConfig/Allow
  • Corrected issue with using EXIT in the Console tab of the WebUI
  • Added SHA256 (SHA2) to the MANIFEST database
  • Fixed issue resulting in blank Registry keys being displayed
  • Introduced new expanded Help System

JANOS 2.0 Release March 4, 2021

  • Improved serial diagnostics during boot
  • Added DST rules for New Zealand timezones
  • Added File Sharing. Disabled by default
  • Logs prior Registry key values along with changes
  • Enabled NetBIOS name resolution and disabled LLMNR
  • Allow product "Birthname" such as jr817120068 to be always valid in name resolution
  • Corrected Websockets login issue
  • Fixed issue with HTML Email content
  • Added SHA384 and SHA512
  • Added text form of IP address to certificate to appease Microsoft IE
  • Enhanced Registry key settings to inform as to reboot requirements
  • Improved Email error reporting
  • Added Galois/Counter Mode (GCM) to TLS security suites
  • Removed legacy Registry editor
  • JANOS renews its own self-signed certificates
  • Added JSON support to PHP
  • Added Command Line text editor
  • Added Elliptic Curve TLS suites
  • Added BAT file enhancements and scripting support
  • Added the ability to retrieve files from remote servers to JRUPDATE
  • IP address filtering overridden by SAFE MODE
  • Add capture filter information to pcapng capture file
  • PHP scandir() changed to return absolute file path
  • Issue with /etc folder content in scandir() corrected
  • Corrected issue with nested PHP foreach loops
  • Added PHP date and time formatting function date()
  • Console command line history search and selection enhancements
  • Added PING Flood Mode and addressing validation option
  • Corrected issue with ZIP/JAR decompression failing with some large binary files
  • Added support for the standard loopback address range
  • Default WebServer/Path is now /flash/www/config allowing relocation of the default configuration pages
  • Corrected Registry issue with of Type 10 temperature sensors
  • Batch parameter %0 now returns the command from the command line
  • Corrected runtime issue with PHP replacing existing array content
  • Addressed differences in Linux based terminal sessions
  • Extended the ECHO command for use in scripting
  • Added JMP Protocol port for use in defining capture filters
  • Added JMP port and BuildTag to Beacon protocol
  • Corrected PHP @strrpos()@ and syntax shortcomings
  • Enhanced ARC/ZIP/JAR command
  • Improved compatibility with Linux terminal emulators

JANOS 1.9 Release February 3, 2020

Release Notes

We have released JANOS v1.9 which has several changes and bug fixes. Most notably with TCP packet generation. While it is not wrong to send data in multiple TCP packets, many devices incorrectly implement TCP clients and fail when this case arises. This version adjusted the release of socket data to reduce the chances that a message might be split across separate TCP packets. This had been a recent issue with some MODBUS client devices.

  • Added support for Reverse LLMNR allowing network scanners to label IP addresses with hostnames
  • Adjusted the release of socket data to reduce the chances that a message might be split across separate TCP packets
  • Corrected Sockets race condition that caused occasional reception delays and blocking
  • Fixed the incorrect signed display of large input counter values in JRMON and JMP Protocol
  • Adds a BEACON announcement in the event of an IP conflict
  • Improved NONCE management eliminating possible issues in the presence of port scanners
  • Eliminated chance of buffer overrun occurring in FTP transfer
  • Beacon REBOOT now works in all cases
  • Eliminated potential difficulty in obtaining network capture file

JANOS 1.8 Released June 17, 2019

Release Notes

We have released JANOS v1.8 which adds the JMP Protocol. The JANOS Management Protocol (JMP) is essentially the JSON message interface utilized by JANOS Websockets. The JMP Protocol has been exposed on its own TCP/IP port. This encloses the JSON messaging in a JSON array along with the JSON Object length making reception of the messages easy. The JMP Protocol will be used by the QSC Q-SYS JNIOR component.

  • Implements the JANOS Management Protocol JMP
  • Adds "Block" command to JSON interfaces
  • Web Server limits the effects of extremely slow connections.

JANOS 1.7.1 Released December 3, 2018

Release Notes

  • Watchdog no longer causes reboot from foreground execution
  • REGEX Alternation '|' has been corrected to properly work in Group
  • Corrected NULL Pointer write issue when a Group which employs alternation appears at the start of a REGEX expression
  • Resolved message pump memory issue relating to process termination
  • Expand the channel range for setOutputRelay() from 0-11 to 0-15
  • Corrected network capture filtering when an IP address is to be excluded
  • Supports networks using Jumbo Frames
  • Eliminated assertion associated with improper use of '%n' in System.out.printf.

JANOS 1.7 Released July 26, 2018

Release Notes

  • Added ability to load single CA Certificate to be supplied on TLS connection
  • Support TLS Client Certificate Verification on outgoing connections
  • Added legacy PKCS1 support for externally generated certificates
  • Corrected array issue with processing of deferred email transmissions
  • Corrected memory issue with TAB use on the Command Line

JANOS 1.6.5 Released May 22, 2018

  • Corrected FTP listing issue created by the v1.6.4 release
  • Corrected getRegistryList method memory leak
  • Corrected 412DMX light Flickering
  • Corrected 412DMX NAND Flash processing issue
  • Corrected FTP transfer restart issue
By | On September 1, 2023 10:58 am | No Comments |

All-In-One 230901
Name Version Release Date Size MD5
JNIOR Support Tool v7.16 Jun 12 2024 6.2 MB c960367efcc4628a8d909e5861ea20b6
Series 4 All-In-One Update Project v2.4.2 Jan 18 2024 1.8 MB 293c415caba1ff6d9b9a404be3430cc2 
--- Core ---
  JANOS                2.4.1   UPDATED
  DCP (WebUI)          3.2.2   UPDATED
  MANPAGES                     UPDATED

--- Bundled ---
  FTP Client
  JBakup
  MODBUS Server        1.9.268
  Serial Control       7.2.61
  Serial To Ethernet   6.2.70
  Slaving Service      3.2.156
  SNMP                 3.1.667
  Bundled Web Pages

All-In-One 230511 May 11, 2023 

--- Core ---
  JANOS                2.4 build 1.0   UPDATED
  DCP (WebUI)          3.2.1
  MANPAGES

--- Bundled ---
  FTP Client
  JBakup
  MODBUS Server        1.9.268
  Serial Control       7.2.61
  Serial To Ethernet   6.2.70
  Slaving Service      3.2.156
  SNMP                 3.1.667
  Bundled Web Pages

All-In-One 230504 May 4, 2023 

--- Core ---
  JANOS                2.4 build 0.2   UPDATED
  DCP (WebUI)          3.2.1
  MANPAGES

--- Bundled ---
  FTP Client
  JBakup
  MODBUS Server        1.9.268
  Serial Control       7.2.61
  Serial To Ethernet   6.2.70
  Slaving Service      3.2.156
  SNMP                 3.1.667
  Bundled Web Pages

All-In-One 230503 May 3, 2023 

--- Core ---
  JANOS                2.4       UPDATED
  DCP (WebUI)          3.2.1
  MANPAGES                       UPDATED

--- Bundled ---
  FTP Client
  JBakup
  MODBUS Server        1.9.268
  Serial Control       7.2.61
  Serial To Ethernet   6.2.70
  Slaving Service      3.2.156   UPDATED
  SNMP                 3.1.667
  Bundled Web Pages

All-In-One 230202 February 2, 2023 

--- Core ---
  JANOS                2.3 build 1.0    UPDATED
  DCP (WebUI)          3.2.1
  MANPAGES

--- Bundled ---
  FTP Client
  JBakup                                UPDATED
  MODBUS Server        1.9.268
  Serial Control       7.2.61
  Serial To Ethernet   6.2.70
  Slaving Service      3.1.133
  SNMP                 3.1.667
  Bundled Web Pages

All-In-One 230125 January 25, 2023 

--- Core ---
  JANOS                2.3 build 0.2    UPDATED
  DCP (WebUI)          3.2.1
  MANPAGES

--- Bundled ---
  FTP Client
  JBakup                       
  MODBUS Server        1.9.268
  Serial Control       7.2.61
  Serial To Ethernet   6.2.70
  Slaving Service      3.1.133
  SNMP                 3.1.667
  Bundled Web Pages

All-In-One 220628 June 28, 2022 

--- Core ---
  JANOS                2.2       UPDATED
  DCP (WebUI)          3.2.1     UPDATED
  MANPAGES                       UPDATED

--- Bundled ---
  FTP Client
  JBakup                       
  MODBUS Server        1.9.268   UPDATED
  Serial Control       7.2.47    UPDATED
  Serial To Ethernet   6.2.70    UPDATED
  Slaving Service      3.1.120   UPDATED
  SNMP                 3.1.498   UPDATED
  Bundled Web Pages              ADDED

All-In-One 211215 December 15, 2021

This Update was pushed to support manufacturing and the supply chain issues brought on by COVID-19.  Component workarounds were needed and a bump to the OS was required to support those component changes.  Units built after this date will not be able to roll back to previous versions of the OS.

--- Core ---
  JANOS                2.1.1   UPDATED
  DCP (WebUI)          3.1.0
  MANPAGES

--- Bundled ---
  FTP Client
  JBakup
  MODBUS Server        1.7.236
  Serial Control       7.0.31
  Serial To Ethernet   6.1.53
  Slaving Service      2.0.104
  SNMP                 3.1.667

All-In-One 210810 August 10, 2021 

--- Core ---
  JANOS                2.1       UPDATED
  DCP (WebUI)          3.1.0     UPDATED
  MANPAGES                       ADDED

--- Bundled ---
  FTP Client
  JBakup                         ADDED
  MODBUS Server        1.7.236
  Serial Control       7.0.31
  Serial To Ethernet   6.1.53    UPDATED
  Slaving Service      2.0.104
  SNMP                 3.1.667
  Tasker                         REMOVED [Has its own installer]

All-In-One 210304 March 4, 2021 

--- Core ---
  JANOS                2.0 build 1.0   UPDATED
  DCP                  3.0.1           UPDATED (moved from flash/www.zip to flash/www/config/zip)

--- Bundled ---
  FTP Client
  MODBUS Server        1.7.236
  Serial Control       7.0.31
  Serial To Ethernet   6.0.48
  Slaving Service      2.0.104
  SNMP                 3.1.667
  Tasker               6.0.1601
  Task Manager         7.0.351

All-In-One 210202 February 2, 2021 

--- Core ---
  JANOS                2.0        UPDATED
  DCP                  2.4

--- Bundled ---
  FTP Client
  MODBUS Server        1.7.236
  Serial Control       7.0.31     UPDATED
  Serial To Ethernet   6.0.48
  Slaving Service      2.0.104    UPDATED
  SNMP                 3.1.667    UPDATED
  Tasker               5.0.1505   ADDED
  Task Manager         7.0.351

All-In-One 200501 May 1, 2020 

--- Core ---
  JANOS                1.9            UPDATED
  DCP                  2.4

--- Bundled ---
  FTP Client
  MODBUS Server        1.7.236
  Serial Control       5.0.122.1501
  Serial To Ethernet   6.0.48
  Slaving Service      1.5.1810.225
  SNMP                 2.6.532        UPDATED
  Task Manager         7.0.351

All-In-One 200203 February 3, 2020 

--- Core ---
  JANOS                1.9   UPDATED
  DCP                  2.4   UPDATED

--- Bundled ---
  FTP Client
  MODBUS Server        1.7.236
  Serial Control       5.0.122.1501
  Serial To Ethernet   6.0.48
  Slaving Service      1.5.1810.225
  SNMP                 2.4.1.494
  Task Manager         7.0.351

All-In-One 190618 June 18, 2019 

--- Core ---
  JANOS                1.8
  DCP                  2.3

--- Bundled ---
  FTP Client
  MODBUS Server        1.7.236
  Serial Control       5.0.122.1501
  Serial To Ethernet   6.0.48
  Slaving Service      1.5.1810.225
  SNMP                 2.4.1.494
  Task Manager         7.0.351
By | On September 1, 2023 9:42 am | No Comments |

Using the DMX Panel

Under the Help tab when on the DMX Web Page, there is an option called ‘Launch Panel’. This opens the DMX panel in a different tab, the DMX Panel being a visual representation of the 512 channels that DMX controls. In the DMX Panel, highlighted squares will surround numbers, showing what channels are within a fixtures range. On the right side of the Panel, if any scripts have been created and saved, they will appear here as buttons to execute them from the DMX Panel. Numbers in the DMX Panel will represent the current 512 channels the DMX application is controlling. Clicking on any of the numbers within the DMX Panel allows you to edit that channels value. The pop-up for editing channel values changes depending on if you are selecting channels within a fixture or not. If the number isn’t located within a fixture, it simply prompts what value to set it to with a text field. If you select channels inside a fixture, then the prompt it provides allows all the channels inside the fixture to be edited, and include not only a text field to edit them, but a slider as well. 

By | On August 16, 2023 1:01 pm | No Comments |