Modernize any scale without replacing it

A lightweight messaging protocol used to send scale data efficiently to cloud platforms, IoT systems, or private brokers. With Neutron, MQTT is ideal for continuous, real-time data publishing with low bandwidth usage.

Neutron supports:

• MQTT
  Simple broker connection without transport encryption. Suitable for local networks, internal systems, and environments where TLS is not required.

• MQTTS with username/password
  Encrypted MQTT communication over TLS using broker authentication with username and password. Suitable for secure connection to standard MQTT brokers and cloud platforms.

• MQTTS with client certificate (mTLS)
  Encrypted MQTT communication with mutual TLS authentication using client certificate and private key. Suitable for high-security deployments such as AWS IoT Core and enterprise-grade broker environments.

• MQTTS with CA certificate validation
  Server certificate validation using uploaded CA certificate to ensure the broker identity is trusted. Important for production-grade secure deployments.

• Azure IoT Hub via MQTTS
  Secure MQTT connection using SAS token authentication, suitable for direct integration with Microsoft Azure IoT environments.

• WSS transport for secure cloud communication
  MQTT communication over secure WebSocket transport. Useful when MQTT must pass through firewalls, proxies, or web-based infrastructures that prefer WebSocket connections.

Typical usage:

MQTT-based cloud ingestion, secure broker connectivity, AWS IoT deployments, Azure IoT Hub integrations, and bidirectional command/data exchange with weighing devices. 

A persistent two-way communication channel between Neutron and a server or web application. It is used when live, instant data exchange is needed, such as real-time dashboards, monitoring, or direct browser-based communication.

Neutron supports:

• WS (WebSocket)
  Persistent bidirectional communication without encryption. Suitable for local dashboards, internal applications, and real-time device communication on trusted networks.

• WSS (Secure WebSocket)
  Encrypted bidirectional WebSocket communication over TLS. Suitable for browser-based applications, cloud platforms, and secure real-time integrations.

• WSS with CA certificate validation
  Validates the server certificate against an uploaded CA certificate, ensuring trusted and secure communication with remote servers.

• Optional Basic Authentication
  Supports HTTP Basic Authentication during WebSocket handshake for environments requiring simple access control in addition to transport security.

A request-response communication method based on HTTP/HTTPS. With Neutron, REST is used when external systems need to read scale data, send commands, or integrate weighing information into business software, apps, or cloud APIs.

Neutron supports:

• HTTP REST API
  Simple unencrypted REST access for sending commands to serial devices and receiving responses over IP. Suitable for internal networks and testing environments.

• HTTPS REST API
  Encrypted REST communication using TLS. Recommended when accessing Neutron from external systems, cloud services, or security-sensitive environments.

• REST-to-serial bridge
  Converts HTTP/HTTPS GET or POST requests into serial communication over UART / RS-232 / RS-485 and returns the serial response in the HTTP reply. Ideal for integrating serial scales into modern IT systems without custom gateway development.

• Custom TLS certificate support
  The built-in web server can use its own uploaded certificate and key, allowing integration into corporate PKI or trusted HTTPS environments.

Typical usage:
Node.JS calls https://192.168.10.34/S1/?=cmd=SI and gets response SI S 1992.3 g

A direct network communication method for sending and receiving data over Ethernet or Wi-Fi. Neutron uses TCP/IP for simple point-to-point or server-based integrations where custom software, local systems, or industrial applications need raw communication access.

Neutron supports:

• TCP server mode
  Neutron listens for incoming socket connections from external systems. Suitable when software or equipment needs to initiate the connection to the device.

• TCP client mode
  Neutron actively connects to a remote TCP server. Suitable for installations where the external system expects the scale gateway to initiate communication.

• TCP client with auto-reconnect
  Automatically restores the connection if the remote host becomes unavailable or the network drops. Important for robust industrial and unattended deployments.

• Simultaneous TCP server and client operation
  Supports both listening for inbound connections and maintaining an outbound connection, depending on deployment requirements.

• TCP-to-cloud bridging
  Enables TCP-only devices to be connected into cloud environments without changing their existing communication protocol.