Novastar H Series Api [new]

Technical Paper: Control and Integration of NovaStar H Series LED Processors via API

5. Example: minimal Python TCP wrapper

(Structure you’ll implement; adapt commands to your firmware.)

import socket, time
class NovaHClient:
    def __init__(self, ip, port=5005, timeout=5):
        self.ip, self.port = ip, port
        self.sock = socket.create_connection((ip, port), timeout=timeout)
def send(self, cmd):
        self.sock.sendall((cmd + "\r\n").encode())
        return self.sock.recv(4096).decode(errors='ignore')
def get_brightness(self):
        return self.send("GET_BRIGHTNESS")
def set_brightness(self, value):
        return self.send(f"SET_BRIGHTNESS int(value)")
def reboot(self):
        return self.send("REBOOT")

3) Discovery & addressing

• Discovery is commonly done via UDP broadcast to a controller-specific port. Devices reply with identity payload including model, firmware version, MAC, and current IP.
• Fallback: SNMP-like queries or reading ARP table + HTTP probe.
• Once discovered, use device IP for TCP/UDP commands or HTTP requests to the web UI.

4.2 Example cURL

curl -X POST http://192.168.0.10/api/v1/input/set \
  -H "Content-Type: application/json" \
  -d '"input": 2'

2.2 Communication Protocol

The API relies on a proprietary binary protocol transported over a TCP socket. Communication is stateful; a persistent connection is recommended for monitoring status, though "one-shot" connections (connect, send command, receive response, disconnect) are supported for simple control tasks. novastar h series api

• Protocol Type: TCP Stream.
• Encoding: Binary (Big Endian).
• Session Management: The controller acts as the server; the control system (client) initiates the connection.

4.1 Input and Output Management

• Input Switching: Select the active input source (HDMI 1, HDMI 2, SDI, DVI, USB). This is the most common integration requirement.
• Resolution Read: Query the current input signal resolution to validate signal integrity.
• Output Resolution: Query the output load resolution.

The NovaStar H Series API: Bridging Proprietary Hardware and Custom Integration

In the rapidly evolving landscape of LED display technology, the ability to interface directly with hardware has shifted from a luxury to a necessity. As display systems grow more complex—spanning stadiums, broadcast studios, and fine-pitch corporate lobbies—the demand for automation, remote monitoring, and third-party integration has surged. NovaStar, a dominant force in LED control systems, addresses this need through the H Series API. Designed for their flagship H Series receiving cards, this API represents a critical evolution: moving from manual, front-panel configuration to software-defined, automated display management. Technical Paper: Control and Integration of NovaStar H

1. Executive Summary

Novastar’s H Series (including H2, H5, H7, H9, and H15 models) represents the company’s high-performance line of LED display controllers and video processors. Unlike the older "S Series" sending cards which relied heavily on proprietary software (NovaLCT), the H Series is designed with modern integration in mind. 3) Discovery & addressing

This report details the API capabilities of the H Series. The primary method of programmatic control is the Novastar Control Platform (VNNOX) via cloud APIs, though local control via TCP/IP socket communication is also supported for specialized implementations. The transition to the H Series marks a shift from monolithic local software to web-based and network-programmable management.

Part 5: Critical API Methods for the H Series

Here are the most valuable endpoints for developers working with the H series API. Use these to control your LED wall programmatically.