|Series 4 All-In-One Update Project||v2.1||Aug 10 2021||1.7 MB||dc43e487b691897c0a0876e402a783f9|
The bundled software is easy to start and stop from the main JNIOR web page. Just go to the Applications tab, check the box for the application you want to run, click the save button and then say ok to reboot. When the JNIOR is done rebooting, the bundled application will be running.
The JNIOR is capable of executing multiple applications at the same time. More than one of the bundled software applications can be running as long as they do not conflict with the serial port.
Add-on applications and custom applications can be utilized at the same time.
MODBUS – Communicate with registries in MODBUS
MODBUS allows the user to interact with external devices by communicating with them using JNIOR I/O via MODBUS TCP communications over the Ethernet network. MODBUS Registry Connections made with MODBUS are usually on port 502. The JNIOR can act as a MODBUS Slave and/or a MODBUS Master. MODBUS is widely used in many applications.
- Communicates with serial devices
- PLUS integrates via the Ethernet
- Simple ASCII text commands
- Controls the relay outputs
- Digital Inputs status feedback
Serial Control Plus – Uses simple text commands
Serial Control Plus runs on the JNIOR and allows the user to interact with the JNIOR I/O via the serial port and/or the Ethernet port using simple ASCII commands. The user can control the relay outputs (on, off, pulse) and receive the status of the digital inputs and relay outputs (on, off) and counters via the serial port and/or Ethernet port.
Example commands include:
C1 - Close relay output 1 O234 - Open relays 2, 3 and 4 DIN1=1 - Input 1 is 'on' ROUT1=1 - Relay output 1 is 'on'
The Serial Control Plus functionality can be used in applications where the user’s external device cannot communicate over the Ethernet, but can communicate via an RS232 port. The user’s device must be able to utilize the command structure for the JNIOR defined in the Serial Control Plus manual. Utilization of the serial port can be used in conjunction with another application utilizing the Ethernet port. To see how to setup the serial connection for Serial Control Plus, click here.
- Connects serial devices to the Ethernet network via the JNIOR
- Bidirectional communications
- Configurable via the JNIOR web page
Serial-to-Ethernet Server – Connect to serial devices
The Serial-to-Ethernet Server application runs on the JNIOR and allows the JNIOR to act as a converter between a serial device connected to one of the JNIOR serial ports and a remote application communicating to the JNIOR via the Ethernet network using TCP/IP. The Serial-to-Ethernet conversion is bi-directional, meaning that the serial device can communicate to the PC application and the PC application can communicate to the serial device. The JNIOR acts as a converter between the serial device and the PC, sending and receiving packets of information between the two devices.
The Serial-to-Ethernet function can be used for a variety of applications and adds more value than stand-alone serial converters because of the digital and analog I/O available with the JNIOR. The user can integrate serial devices as well as utilize the JNIOR I/O and standard JNIOR functionality. To see how to setup the serial connection for Serial-to-Ethernet, click here.
- Allows JNIOR to be queried for Model Information
- Can utilize standard traps to for notices when the JNIOR performs something
- Can implement custom traps created to monitor specific events or information
SNMP – Monitor JNIOR data with an MIB
SNMP allows you to view system information from an SNMP browser. The SNMP application uses the JNIOR MIB in order to query its data. Once you’ve opened the JNIOR MIB in an SNMP browser, you can enter its IP address to begin searching for different information from that JNIOR.
SNMP has a variety of data you can pull from the JNIOR such as:
- Serial Number
- OS Version
- Object ID
- How long its been running since last reboot
You can also set standard or custom traps to receive notices when events occur on the JNIOR, for example:
- When the JNIOR is rebooting
- If the JNIOR rebooted successfully
- When an application begins running
- When a log file is backed up
- When a log file is compressed
- Control I/O states using other I/O states
- I/O on a JNIOR can be slaved to local I/O or I/O of other JNIORs
- Default states of I/O can be set when connection to a slaving JNIOR is lost
Slaving – Control the I/O of one JNIOR using another
Slaving allows you to assign an Input or Output on a JNIOR to another Input or Output. The amount of I/O you can slave to is the equal to the standard I/O of a Series 410 JNIOR, meaning it can be applied up to 8 Inputs and 8 Outputs.
The I/O can be slaved to local I/O, or the I/O of one or more JNIORs. This allows chains of I/O that can be created in case user implemented control of one JNIOR is desired to be used among other JNIORs across an network. The I/O can also have a default state in case connection to a JNIOR that was being slaved to is lost.