Crestron NovaStar TU Series
🚀 Early AccessCrestron SIMPL+ module for NovaStar TU Series LED playback processors: standby and wake, screen on/off, source, volume, effect modes, program playback and the unit's status over TCP.
🚀 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
Overview
Put the unit in standby, wake it or power it off; turn the screen on and off; select Android or HDMI 1 to 3; set volume and mute, LED brightness and the effect mode; send the ten remote-control keys; and play, pause, resume and step through programs by number. The relay output and Wi-Fi, hotspot and Bluetooth switching are there for commissioning. The module sends nothing by itself at program start or on a reconnect.
Every poll reads the system status, the current source, volume and mute, HDMI signals, the USB drive, Wi-Fi and wired network state, the receiving card's brightness, temperature and voltage, and the link state of up to 20 Ethernet outputs. A refused or unanswered command is named, and the connection retries by itself five seconds after it drops.
The download includes the SIMPL+ module (.usp and .ush), a sample SIMPL Windows program, an HTML5 touch panel, a join reference and the manual. Built for 3-Series and 4-Series processors. The TU needs firmware V1.6.0 or later and a fixed address, preferably on a wired connection. RS-232 control is not supported in this release. A 30-minute trial runs on every program start, and activation uses an offline code, so the processor needs no internet connection.
Features
A SIMPL+ module for NovaStar TU Series LED playback control processors - the Android-based units that drive an LED screen - over NovaStar's TU Series Control Protocol V3.0.2 on TCP port 5201: standby and wake, screen on and off, the source, volume and mute, effect modes, the unit's remote-control keys, program playback, the relay, and Wi-Fi, hotspot and Bluetooth, with the unit's status read back (the hotspot's state is not read). NovaStar lists the TU15 Pro, TU20 Pro and TU4K Pro in this line; the protocol document names no model, and none has been tested. One module per TU.
Untested on any NovaStar TU. The module is built from NovaStar's protocol document and tested off-processor against test cases taken from it and from an emulator AchKayEm wrote; no AchKayEm driver has yet been connected to a TU (see the change log).
Control
- Standby, wake and power off - each with a warning: how a TU is started again after power off is not documented, and whether a TU in standby still answers the network is not known
- Screen on and off
- Source: Android, HDMI 1, HDMI 2, HDMI 3 (the TU15 Pro and TU20 Pro have two HDMI inputs)
- Volume 0-100, the unit's own volume keys, mute on, off and toggle
- Brightness of the LED screen on the protocol's 0-255 value (what full brightness is has not been confirmed)
- Effect mode: the document's standard, meeting, vivid, skin (the TU15 Pro's sheet names other modes)
- The ten remote-control keys: home, back, menu, power, source, the arrows and confirm
- Program playback: play by number (from 1), pause, resume, previous, next, exit; the program list initialised and counted with the first play of a connection or on request - never at connect
- The relay output; Wi-Fi, hotspot and Bluetooth on and off, for commissioning - switching off the network the processor uses to reach the TU ends the connection for good
- Commands go out in the order they were made; the module sends no command by itself, at program start or on a reconnect
Feedback
- Read from the TU at every poll: system status, the current source, volume and mute, HDMI signals, USB drive, Wi-Fi state and signal, wired network, Bluetooth state, the first receiving card's brightness, temperature and voltage, and the link state of up to 20 Ethernet outputs (the byte layout not yet checked on a unit)
- Screen on / off, effect mode and the relay: the last value this module sent and the TU accepted - NovaStar's protocol document has no read for them, so a change made with the unit's remote or menu is not seen
- When the connection drops, feedback keeps its last value; valid flags say when the card and link readings are current
- A refused or unanswered command is named
Connection
- Local network only.
- One TCP connection, kept open and polled; tries again by itself 5 seconds after it drops, and reports a TU that stops answering after about 20 seconds.
- Diagnostics on the module's own signals: connection status, last command, last response, last error, and traffic counters.
Licensing
- 30-minute trial on every program start; no code needed to evaluate.
- Activation with an offline activation code from the AchKayEm licensing portal (product
novastar-tu-series-crestron). The processor needs no internet connection. - A stored license wins over a newly entered code. A code names the control processor by its MAC address; the module checks that only if a Console symbol is wired, otherwise it works on any processor.
- The license is meant to be stored on the processor and checked again on every start; storage on a processor is still to be confirmed.
Requirements. A NovaStar TU Series unit that implements TU Series Control Protocol V3.0.2 (NovaStar's document names no model and none has been tested; it says "The new features require TU series V1.6.0 and later"), with a fixed address, reachable from the processor on TCP port 5201, by cable preferably. A Crestron control system programmed in SIMPL Windows; the module is built for 3-Series and 4-Series (compiled for both; run on a 4-Series processor, an RMC4, against an emulator; not yet run on a 3-Series). RS-232 control is not supported in this release.
Version history
Beta Pre-release
