Frequently Asked Questions

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

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

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

11 ounces (312 grams).

2 years. Here is the JNIOR Warranty

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

When the JNIOR is loaded on the network they have DHCP enabled, which checks the network the JNIOR is on and assigns it an IP available. If your network doesn’t support DHCP your JNIOR will default to the address 10.0.0.201. If another device on the network has 10.0.0.201, then the JNIOR will forgo the IP address and set itself to 0.0.0.0 to avoid an IP conflict. Even if no other unit has the same IP as your JNIOR, this issue can also be caused by your JNIOR’s IP address not being compatible with your computer’s IP address. To fix this, you need to change the IP address of the JNIOR, which a post explains here.

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

When this happens it’s typically when a connection is initially being made to the JNIOR during setup. Give your system connecting to the JNIOR a reboot and the connection should establish itself. You can check which ports the JNIOR is listening on using the netstat command.

Something that commands need to include when being sent to the JNIOR is the termination string. For example, if you’re connecting to the JNIOR using Cinema the default termination string is \r\n. So when you send the JNIOR a command in Cinema, make sure the command ends with \r\n. To check what termination string you need for your connection, based on the application you’re using on the JNIOR, you can check the application registry keys in the registry of a JNIOR’s web page. (appdata/application name). If it’s a TCP connection, you may want to also check and make sure the JNIOR is listening on the port you are sending to. You can check which ports the JNIOR is listening on using the netstat command.