[patched] | Novastar H Series Api

For environments where network connectivity is unavailable or serial communication is preferred (e.g., legacy control systems), the H Series can be controlled via RS232. The pinout for the RJ45 to RS232 connection is as follows:

Query status:

The H Series acknowledges each command with a response string containing the original command and an "Ok" acknowledgment appended.

Module mapping & calibration:

"jsonrpc": "2.0", "method": "input/crop", "params": "token": "session_token_abc123", "x": 1920, "y": 0, "width": 1920, "height": 1080 , "id": 6

If you have an 8K source driving multiple H9 units, you must crop the source.

The is a network-based protocol designed for intelligent, automated control of NovaStar H-series splicers. Using a RESTful HTTP/HTTPS approach (commonly utilizing POST requests), it allows external control software (like Crestron, Q-SYS, or custom applications) to interact directly with the device. Key Benefits of the API: novastar h series api

Reboot & basic control:

Before integrating into production systems, thoroughly test API calls using tools such as (for HTTP API) or MIB Browser (for SNMP). The COEX API website integrates an Apifox plugin that allows direct testing of API endpoints. The official API test environment can be accessed at https://api-coex150-novastar.apifox.cn/en .

The VNNOX API is a RESTful interface designed for managing screens, publishing content, and monitoring status. It requires an Enterprise/Developer account with Novastar. The is a network-based protocol designed for intelligent,

Timing/refresh parameters:

The NovaStar H Series breaks the traditional mold of LED controllers by utilizing a modular, card-based design that combines video processing and display control into a single chassis. It is specifically engineered to handle fine-pitch LED displays, supporting massive pixel capacities.