Novastar H Series Api Link

Disclaimer: This paper is based on general knowledge of Novastar H Series architecture. For production environments, developers must obtain the official SDK or Protocol Document from Novastar, as command codes (Hex values) may change between firmware versions (V1.0 vs V2.0).

NovaStar H Series API (specifically for H2, H5, H9, and H15 splicers) allows third-party control systems like Crestron, AMX, or custom software to manage video wall functions remotely. 1. Connectivity & Communication

The H Series supports two primary communication methods for external control: EZ LED Visual UDP Communication

: The most common method. Send JSON-formatted commands to the device's IP address on UDP Port 6000 Serial (RS232) : Connect via the physical COM port. Default settings are 9600 Baud Rate , 8 Data Bits, 1 Stop Bit, and no parity. EZ LED Visual 2. API Authentication & Security For newer firmware, NovaStar uses an framework that may require encryption: OpenAPI Management : Enable this in the device Web GUI under Settings > Open API Management to create a "Project" and obtain a Secret Key Request Format : Messages consist of a . If encryption is enabled, you must use an MD5-based signature

(Sign) combining the body ciphertext, timestamp, Project ID (pId), and Secret Key. 3. Command Protocol (JSON)

All instructions follow a specific JSON structure. Each command must be enclosed in square brackets and can contain multiple sub-commands in curly braces EZ LED Visual Common Command Parameters: : The specific instruction code (e.g., for presets). for a single unit. : The ID of the screen being controlled (starting from : The ID of the saved preset to be recalled. 4. Key Control Functions Description Save, clear, or load pre-configured screen layouts. is used to load a specific Layer Management Open, close, move, or resize windows on the wall. Source Switching Switch which physical input is displayed in a layer. to map a connector to a Brightness/Color Adjust global or screen-specific visual settings. Read/write instructions added in protocol version 1.0.3. 5. Testing Your Integration

To verify your API calls without writing a full script immediately:

Novastar H Series Splicers Control Protocol V1.0.7 - FlipHTML5

At its core, the H Series API is a communication protocol that allows external software applications to communicate directly with NovaStar’s H Series receiving cards over a network (typically TCP/IP). Unlike traditional systems that rely solely on a dedicated controller or a PC-based application like SmartLCT, the API exposes a set of programmable endpoints. These endpoints allow developers to query status, adjust parameters, and execute diagnostic routines.

The H Series cards themselves are intelligent slave devices. Through the API, a master system (e.g., a show control PC, a building management system, or a Python script) can send structured commands—often in JSON or binary protocol format—to read temperature sensors, monitor voltage levels, adjust gamma curves, or apply coefficients for specific LED modules. The API operates at a low enough level to affect hardware states but is abstracted enough to prevent catastrophic damage (critical parameters like voltage thresholds are typically read-only or require authentication).

This paper is a technical synthesis based on publicly documented NovaStar specifications and common industry integration patterns. Always refer to the official manual for your exact firmware version.

NovaStar H Series video wall splicers (models H2, H5, H9, H15) support two primary methods for third-party control: TCP/UDP-based JSON protocol HTTP-based OpenAPI

. Because specific protocol details are often restricted by NDA, it is highly recommended to contact NovaStar Support directly to request the latest full documentation. 1. Enabling API Access novastar h series api

Before you can send commands, you must enable and configure the API connector through the device's web-based management interface.

: Access the web console by entering the device's IP address into a web browser. Default credentials are typically Enable OpenAPI : Navigate to Settings > OpenAPI Management Create Project

to create a new third-party control project. The system will generate a (Requestor ID) and a 2. Communication Methods

The H Series supports multiple communication layers depending on your integration needs: HTTP OpenAPI : Uses standard requests with

formatting. This is ideal for web-based controllers or high-level software integration. UDP Protocol

by default. Commands are formatted as JSON strings enclosed in square brackets

: Standard TCP communication is used for more persistent connections with the control software. RS232/Serial : Physical control is possible via the port on the H_Control card. 3. Command Structure (JSON Example)

Most commands use a structured JSON packet. A typical execution command looks like this: "CommandName" "deviceId" : value }] Use code with caution. Copied to clipboard Successful Execution : The device returns "ack": "Ok" "ack": "Error" if the format is incorrect or unsupported. 4. Common API Capabilities

The API allows for real-time control of the following functions: Novastar H series open API control options?

The NovaStar H Series Open API is a critical software interface that allows third-party developers to integrate flagship video wall splicers—such as the H2, H5, H9, H15, and H20—into custom control platforms, building automation systems, or professional AV environments. 1. Integration and Authentication

To begin using the API, administrators must first enable it within the H Series web console.

Key Credentials: The system generates a pId (Requestor ID) and a secretKey. These credentials are required to authenticate every request, ensuring secure communication between the third-party controller and the video processor. Disclaimer: This paper is based on general knowledge

Encryption: The H Series supports both encrypted and unencrypted transmission of request parameters, providing flexibility for different security requirements. 2. Core Functional Capabilities

The Open API provides granular control over the H Series' powerful hardware features, which can handle up to 520 million pixels on the high-end H20 model.

Preset Management: Developers can use the API to recall up to 2,000 saved presets, enabling instant scene changes during live events or in control rooms.

Layer and Source Control: The API allows for the dynamic manipulation of video layers. Users can adjust layerId, inputId (signal source), and cropId (signal cropping) programmatically.

Monitoring and Management: Integrated support for SNMP (Simple Network Management Protocol) allows for real-time monitoring of device health, such as temperature, voltage, and signal status. 3. Multi-Protocol and Environmental Support

Beyond the core RESTful API, the H Series is designed for broad interoperability:

Protocol Support: It supports RS232 and TCP/IP for central control systems, as well as IP camera protocols like RTSP, ONVIF, and GB28181 for surveillance integration.

Intelligent Control: It is compatible with hardware like the Stream Deck, allowing API commands to be mapped to physical buttons for functions like screen blackouts or OSD (On-Screen Display) toggling. 4. Technical Resource Access

While some high-level instructions are public, specific control protocols are often protected by an NDA. Developers should contact NovaStar Support to obtain the latest version of the detailed interface documents and the H Series User Manual. H Series Video Wall Splicers User Manual - NovaStar

The blue glow of the server room was the only light in the arena as Elias sat huddled over his laptop. In six hours, the World Championship opening ceremony would begin, but the massive 360-degree LED wrap—the centerpiece of the show—was dark.

He wasn’t just dealing with a simple screen; he was managing a massive cluster of NovaStar H-Series processors. The hardware was capable of handling tens of millions of pixels, but the creative team had just thrown a curveball: they wanted the visuals to react in real-time to the crowd’s noise levels.

"Manual switching won't work," Elias muttered. "I need the API." At its core, the H Series API is

He pulled up the H-Series API documentation. He needed to bridge the arena’s sound sensors with the H-Series' powerful layer management. Using a simple Python script, he targeted the H-Series IP address and crafted the JSON payloads. POST /api/v1/scene/switch

His first attempt failed. Connection refused. He checked his port—8000. Correct. He realized he hadn't authenticated the session. He quickly wrapped the request with the proper headers.

The fan noise of the processors hummed in sync with his heartbeat. He wrote a logic loop: if decibels exceeded 90, the API would trigger Scene 2—a high-energy "Voltage" preset. If they hit 110, Scene 3—the "Champion’s Gold" layer—would activate. He hit "Run."

High above, a single pixel line flickered. Then, like a digital sunrise, the entire H9 processor chassis responded. The API command slid the layers into place with zero latency. Elias clapped his hands near the sensor.

Immediately, the massive screen shifted from a deep blue to a pulsing electric violet. "It's alive," he whispered.

When the gates opened and 50,000 fans roared, Elias didn't touch a single button. The H-Series API caught the wave of sound, switching scenes and adjusting brightness automatically. The arena didn't just show a video; it breathed with the crowd, all thanks to a few lines of code and a very powerful processor.

If you'd like to turn this into a technical guide or a specific project, let me know: Which H-Series model are you using (H2, H5, H9, H15)?

| Interface | Protocol | Port | Use Case | |-----------|----------|------|-----------| | TCP Raw | ASCII commands | 5000 | Low-latency control, scripting | | HTTP | REST-like | 80 | Web UI integration, status polling | | Serial (RS-232) | Same ASCII set | - | Legacy or isolated systems |

Connection:

Cause: Your firmware is too old or the syntax is for the wrong H model. Fix: Upgrade to H series v1.8.2+. The H2 does not support cropping; the H9 does.

CMD: 0x30
Data: scene index (1-based)
Load scene 3: AA AA AA 03 30 03 30 BB BB BB