The JNIOR has a strong list of methods that allow you to monitor, control and configure the unit.

JNIOR Web Server

The JNIOR Web Server implements multiple features. HTTP, HTTPS, PHP and WebSockets. WebSocket allow for bidirectional, real-time communication. This allows our DCP (Dynamic Configuration Page) to work. Use the DCP for manual monitoring, control and configuration.

JMP Protocol

The JMP Protocol is available in JANOS 1.8!  JMP utilizes the same JSON messaging format that the websockets protocol has used.  So there is consistency.  Actually the websockets now just wrap the JMP protocol in websocket envelopes for delivery.  Click here for more information!

  JMP Protocol Manual v2.0 [ Mar 14 2024, 230.04 KB, MD5: 905f124811e438ea93ccd542bdd66f41 ]

JNIOR Protocol via 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.

This is recommended for new development

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.

  Websocket Access v72 [ Mar 01 2024, 145.23 KB, MD5: 7bb665495c1731f24e4aa0066be7c205 ]

A quick example using java-script in client browser
View Example »

C# WebSocket Example using the JniorWebSocket Library
View Example »

JNIOR Protocol

This is NOT recommended for new development
Using WebSockets and the Web Server you can monitor, control and configure the JNIOR. This is a binary protocol. This is carried over from the Series 3.
This is NOT recommended for new development. Please use the JNIOR Protocol via WebSockets

  JNIOR-Protocol.pdf [ Jul 25 2018, 834.68 KB, MD5: 745465d75bcc8319607da1e5336a953f ]


MODBUS is a master / slave protocol. That means that the master is responsible to polling the JNIOR frequently to get data. There are a few variations of MODBUS that are implemented on the JNIOR; MODBUS RTU, MODBUS ASCII and MODBUS TCP.

  Modbus_Protocol.pdf [ Jul 25 2018, 123.36 KB, MD5: 9faa9832028e4df6bd44ec2f07a109f7 ]


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.


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.

Beacon Protocol

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.

  BEACON-UDP-packets.pdf [ Jul 25 2018, 103.78 KB, MD5: 34336c16f961fcebce79ce23b8df3983 ]