Communication Protocols

A Variety of Communication Methods – At the same time!

The JNIOR can be integrated into a variety of applications via several communication methods. Because the JNIOR can have multiple connections, you can have several connections via the same method or you can use a variety of methods with separate connections, all at the same time.

Built-in Protocols

• JNIOR Web Server – the JNIOR contains its own web server for launching various monitoring, control and configuration web pages. The JNIOR web pages consist of HTML And JavaScript files. The web pages communicate through a WebSocket interface.
• JMP Protocol – The JMP Protocol is an Ethernet protocol that uses the JSON format for messages. JMP stands for JANOS Management Protocol. The JMP Protocol can be used directly on default port 9220. The JMP Protocol messages are used by the WebSocket interface. JSON has an advantage of being human readable versus a binary format.
• JNIOR Protocol with Websockets – Using WebSockets and the Web Server you can monitor, control and configure the JNIOR via JSON formatted JNIOR Protocol packets. This is how the DCP works. The DCP is open source. More information on Websocket access with the JNIOR is here. Connecting to the JNIOR via WebSockets has many advantages:
  • Bidirectional real-time TCP connection. IO State is sent to from the JNIOR when it occurs without the need to poll. Less overhead!
  • Uses JSON for message format. Easy to read and implement.
  • Uses wss:// over port 443 to be secure! TLS v1.0 AES/256 SHA1
  • Monitor, Control, Configure as well as File System, Command Line, and Syslog functionality. Replaces JNIOR protocol, FTP and Telnet.
• JNIOR Protocol – the JNIOR Protocol is a binary formatted protocol. The JNIOR Protocol can be used directly on default port 9200. By implementing the JNIOR protocol communications within their application directly, the user can establish an efficient communications link with the JNIOR to take advantage of all the JNIOR functionality. This is not recommended for new development. Please refer to the JMP protocol for the latest protocol features.
• Beacon – The Beacon Protocol is for discovery and initial configuration. It utilizes UDP. Discovery is performed via UDP broadcasts while configuration is done using UDP point-to-point. Uses UDP port 4444.
• Windows DLL – the JNIOR Windows DLL allows the user to access the JNIOR functions through easy to use API calls. By taking advantage of these predefined API calls, the user can easily design custom applications which access all available JNIOR data and functionality without having to know the details behind the JNIOR protocol communications structure. There are many functions in the DLL to accommodate the needs of the software developer.
• Custom Communications Methods – have your own communication method for your application? You, or INTEG, can develop a custom application that will run on the JNIOR and interface with the JNIOR I/O via our standard Java Class for the JNIOR OS. Your custom application can then convert the JNIOR I/O commands to your protocol for integrating with your application. Contact INTEG for more information to learn how we have already done this for several customers. 

Add-on Protocols

• SNMP – the JNIOR supports SNMP (Simple Network Management Protocol) for querying the JNIOR I/O status, controlling the relay outputs and configuring the I/O to be ‘traps’. The JNIOR MIB and SNMP application notes are available for download in the Support section of our web site.
• MQTT – The JNIOR has an application for communicating with MQTT brokers to publish and receive messages.
• Serial-to-Ethernet Server – Serial-to-Ethernet is a software application that runs on the JNIOR that allows the JNIOR to act as a converter between a serial device connected to the JNIOR serial port and a remote application. Communication to the JNIOR is via the Ethernet network using TCP/IP.
• Modbus/TCP Slave and Master – supports access to the JNIOR I/O via Modbus TCP communications over the Ethernet network. The JNIOR can act as a Modbus Slave and/or a Modbus Master. MODBUS is widely used in many applications.
• ASCII Commands – the Serial Control Plus/Cinema programs allow the user to interact with the JNIOR I/O via simple ASCII commands. The connection can be made via the JNIOR serial port and/or the Ethernet port. The user can control the relay outputs (on, off, pulse) and receive the status of the digital inputs (on, off) and counters via simple ASCII commands such as C1 (close output 1) or C1p=1000 (pulse relay output 1 for 1000 milliseconds).
• DMX – DMX stands for Digital Multiplex, and is the standard digital communication protocol that is used to remotely control intelligent lighting fixtures. DMX communication consists of 512 channels to control lighting fixtures, and the DMX application allows the JNIOR to manipulate them using scripts. Scripts can be executed remotely by sending commands using an Ethernet connection to the JNIOR via port 10000. To execute scripts, you send the command go SCRIPTNAME\r\n.
• Tasker – Tasker is an application for Series 4 JNIORs that can automate JNIOR functionality. Tasker can be directly be communicated with by sending commands to the JNIOR via an Ethernet connection to port 9210. This can be used to execute tasks by sending the ‘task.execute’ command to the JNIOR.