RTI Novastar VX Series Driver
π Early AccessNovaStar is a Chinese manufacturer of LED display control systems: sending cards, receiving cards, video processors and all-in-one controllers used on LED video walls in venues, retail, houses of worship and broadcast. The VX Series are all-in-one LED controllers that combine a video processor and sending card in one box, with several inputs, layers, presets and test patterns.
π Early Access: an untested release. It may have bugs or missing features and will change before 1.0. Sales are final. Your license includes 1.0 and every later update.
Screenshots
VX Series Pro Test
Overview
cards, video processors and all-in-one controllers used on LED video walls in venues, retail,
houses of worship and broadcast. The VX Series are all-in-one LED controllers that combine a
video processor and sending card in one box, with several inputs, layers, presets and test
patterns.
This driver controls a VX Series controller from an RTI XP processor over the network, using
NovaStar's binary control protocols. One driver covers two protocols, chosen by the Model
setting: the VX400, VX600 and VX1000 (NovaStar's VX1000 Control Protocol, TCP port 5200)
and the VX Pro series (NovaStar's VX Pro Series Control Protocol, TCP port 15200). It sets
brightness, the display mode and test patterns, loads and saves presets, switches the source
on each layer, reads each input's signal and resolution, and reports or switches the primary /
backup mode.
Features
NovaStar VX Series RTI Driver β Key Features
Version 0.9 Beta
RTI XP control driver for NovaStar VX Series All-in-One LED Controllers via the binary VX control protocols over TCP.
Models
- One driver, two NovaStar protocols, chosen by the Model setting:
- VX400 / VX600 / VX1000 β VX1000 Control Protocol V1.0, TCP port 5200
- VX400 Pro / VX600 Pro / VX1000 Pro and VX2000 Pro β VX Pro Series Control Protocol V1.0.5 (controller firmware V1.2.0 or later), TCP port 15200
- TCP Port 0 uses the model's port; a different port is named in the diagnostics.
Display Control
- Brightness: 0β100% or the native 0β255, broadcast to every receiving card. Changes made faster than the controller answers collapse into the latest.
- Display Mode: Normal, Freeze, and Black (fade to black).
- Test Patterns: each model's documented set β the VX1000 protocol's codes 0β39 on the VX400 / VX600 / VX1000; 22 patterns (solid colours, lines, checkerboard, gradients, grids) plus Off on the VX Pro series β and the patterns every model has from one function.
Presets & Layers
- Presets: load, save and delete Presets 1β10.
- Layer Sources: input source switching for Layers 1β3, by source or by the model's input number (Set Layer Input, the same on every model):
- VX400 / VX600 / VX1000: HDMI 1, HDMI 2, DVI 1, DVI 2, SDI, OPT 1, OPT 2, MOSAIC
- VX400 / 600 / 1000 Pro: HDMI 1β3, SDI, OPT 1-1, OPT 1-2, USB (input rows in the controller's order, HDMI 1 first)
- VX2000 Pro: DP, HDMI 1β7, SDI, OPT 1-1, OPT 1-2, USB
Input Status (Polled)
- Per input: name, signal presence, resolution, interlace flag and frame rate, in the model's input order.
- Summary: active input count and list.
Redundancy
- VX400 / VX600 / VX1000: Primary / Backup switching, using the protocol's required three-frame sequence.
- VX Pro series: the controller's mode (Independent, Primary or Backup) read back on every poll; the VX Pro protocol has no switching command.
Diagnostics
- Device: Model, Device Address (IP and port) and Mode ID as System Variables, to tell instances apart.
- Wrong model named: a VX Pro run on the VX400 / VX600 / VX1000 setting is recognised by its Mode ID, and Status Message says so.
- Refused commands logged by name, with the bytes sent and received.
- Link Diagnostics variable and a full report in TraceViewer, with Enable Trace off.
Control-System Integration
- Headless RTI Model: every operation exported as a System Function for buttons, macros and sliders.
- Status Feedback: connection, device, display, preset, layer, input and licence status as System Variables; connection, licence and display-mode events.
- Sample Project: a ready-made panel in every RTI panel size that works with every model: display mode, a brightness slider, layer sources, input signal and resolution, presets, test patterns and the controller's details.
- Licensed: 30-minute trial with online (Vault) or offline (activation code) licensing; per-processor (MAC) or unlimited keys.
Version history
A beta.
Changed
- The sample project: every license message fits. License Status has a line of its own across the page: across the Device card in portrait, and along the bottom of the page, beside the maker line, in landscape. Its longest message ("TRIAL EXPIRED - Per-Core - assign this processor's MAC in Vault, then re-activate") now shows in full on every panel and orientation; before, it shared a half-width column with its label and was cut off. Every control and variable on the page is as it was. Status Message has a row of its own too, in portrait.
- Status Message says "Control blocked - not licensed" when the license stops control; License Status gives the reason. It repeated the whole license message before, up to 99 characters.
No change to how the driver controls the LED controller. No configuration changes are needed; update the driver as usual with Update Driver.
A beta.
Fixed
- Online activation with a license key now completes. The processor never ran the steps of the activation request, so a license key entered in License Key timed out and the driver stayed in its trial. Offline activation codes were not affected.
No change to how the driver controls the LED controller. No configuration changes are needed; update the driver as usual with Update Driver.
A beta. One panel for every model, as the Q-SYS version of this driver has.
Added
- Set Layer Input routes the selected model's input 1-8 to a layer: the input the Input 1-8 Name variable of the same number names. A button labelled with that variable sends what it says on every model.
- Test Pattern (Any Model) shows a pattern every model has (Black, Red, Green, Blue, White, Checkerboard, White Gradient (H) and (V), Grid) in the selected model's form, or Off.
Changed
- The sample project works with every model. Its source buttons are labelled from the controller's own input names and its test patterns are the ones every model has; the Inputs card shows all eight inputs. Up to 0.8 those cards were the VX Pro series' only.
VX Pro series support. Up to 0.5 this driver spoke only the VX1000's commands, which a VX Pro answers for brightness and status and refuses for layers, display mode and test patterns. The VX Pro commands here are the ones the Q-SYS version of this driver sends to a customer's VX1000 Pro, and what that controller showed on the way is built in.
Added
- VX Pro series. A new Model setting selects the controller: VX400 / VX600 / VX1000, VX400 Pro / VX600 Pro / VX1000 Pro, or VX2000 Pro. With a VX Pro model selected every function uses the VX Pro commands (NovaStar VX Pro Series Control Protocol V1.0.5, controller firmware V1.2.0).
- On a VX Pro model:
- Test Pattern (VX Pro) lists the VX Pro's 22 patterns, plus Off.
- Set Layer Source gains the VX Pro inputs as sources 9-17 (HDMI 3-7, DP, OPT 1-1, OPT 1-2, USB). Sources 1-8 keep their numbers.
- Redundancy is read from the controller on every poll (Independent, Primary or Backup). The VX Pro protocol has no command to switch it, so Set Primary and Set Backup log that and send nothing.
- The input rows follow the model's input order (SDI, HDMI 1, HDMI 2, HDMI 3, OPT 1-1, OPT 1-2, U-Disk on a VX400/600/1000 Pro).
- Input 1-8 Name variables say which input each status row is.
- Model and Device Address variables, so each instance in a project can be told apart on a panel.
- TCP Port 0, the default for a new instance, uses the port NovaStar documents for the model: 5200 for the VX400 / VX600 / VX1000, 15200 for the VX Pro series. A different port is named in the diagnostics.
- A VX Pro on the VX400 / VX600 / VX1000 setting is named. A VX Pro also answers on port 5200, where it looks connected and working. When its Mode ID is one known to be a VX Pro, Status Message ends "this is a VX Pro: set the Model setting", and the log says the same.
Changed
- Refused commands are read the moment they arrive. A VX1000 Pro sends a
refusal shorter than a normal reply, and its input status shorter than it
declares. Each is now read as the controller sends it, rather than waited
on for the 2-second reply timeout and dropped. A refusal is logged as
"Controller refused
" with the bytes sent and received, and on the VX400 / VX600 / VX1000 setting suggests checking the Model setting. A status read refused once is logged once, not every poll. Link Diagnostics counts refusals ( refused=). - Brightness follows a slider. Brightness changes waiting behind another command now collapse into the latest value, so the wall goes where the slider stopped rather than replaying every step late.
- The input variables are named Input 1-8 Signal / Resolution instead of the VX1000's input names, because each model orders its inputs differently. Their system variables are unchanged, so existing bindings keep working.
- An input with a signal whose format has not been reported yet reads "Signal, format not reported", and its Signal variable is on. Rows past a model's inputs read "Not on this model".
Fixed
- The Get Info help text, the feature list and the user manual described a different NovaStar product (the TU Series). They now describe this driver.
Note
- Existing projects keep the VX400 / VX600 / VX1000 model and their TCP port, and send the same commands as 0.5.
- On a VX1000 Pro the Q-SYS version of these commands set brightness, display mode and layer sources. Test patterns were acknowledged but have not yet been seen on the wall. This driver itself has not yet run on a VX Pro, and the VX2000 Pro has not been seen at all.
Beta
