NovaStar TB30 is a Taurus-series LED multimedia player that stores content, plays scheduled media and sends image data to compatible LED receiving cards without a continuously connected PC. This guide covers NovaStar TB30 specifications, manual downloads, software, setup, buying questions and troubleshooting.

The key purchasing detail is its loading limit: NovaStar’s V1.2.4 specification, dated 31 July 2026, lists 1,300,000 pixels, while older documentation and the manufacturer’s comparison page list 650,000. Confirm the applicable configuration before ordering. Its 4K decoding capability describes source files, not a 4K LED output canvas.

• Device type: Taurus-series asynchronous multimedia player — media playback and LED screen sending in one unit
• Loading capacity: up to 1,300,000 pixels in specification V1.2.4; earlier V1.2.1 and some NovaStar web pages state 650,000 pixels
• Outputs: 2x Gigabit Ethernet (both primary by default, one can be set as backup) plus 1x 3.5 mm audio output
• Processing: quad-core ARM A55 at 1.8 GHz, 1 GB RAM, 32 GB internal storage, Android 11
• Simultaneous playback: 1x 4K, 2x 1080p, 5x 720p, 6x 480p or 6x 360p video (V1.2.4)
• Control software: ViPlex Handy (mobile), ViPlex Express (Windows), VNNOX (cloud)
• Multi-screen sync: NTP, GPS or RF time synchronization
• Environment and size: -20 °C to +60 °C, IP20, 274.3 x 139.0 x 40.0 mm, 1,228.9 g net weight

The NovaStar TB30 is made by Xi’an NovaStar Tech Co., Ltd. for full-color LED signage. Also called the NovaStar Taurus TB30, it combines the functions of a media player and an LED sending device. The playback program resides on the player, so a laptop is used for commissioning or content updates rather than continuous operation.

In a typical NovaStar TB30 installation, LED OUT connects to receiving cards inside the cabinets, while the separate ETHERNET management port connects to the control network. ViPlex publishes playlists and schedules; compatible receiving-card parameters determine how pixels map onto the physical modules. The controller cannot compensate for an incorrect cabinet map or an incompatible receiving card.

Choose this architecture for scheduled advertising, menus and notices. The NovaStar TB30 has no listed physical HDMI input, so a live laptop or camera feed requires a suitable alternative controller. Time-synchronized playback between players is a separate function from live HDMI video input.

The NovaStar TB30 specifications below retain the version context needed for procurement. Hardware and media figures follow NovaStar’s TB30 V1.2.4 PDF; the loading discrepancy is explained in section 3. Maximum dimensions, total pixels and decoding limits are separate constraints.

For a NovaStar TB30 using two primary outputs, calculate the pixel load and cable route for each port. If redundancy is required, ask the supplier to verify the permitted loading in backup mode and test the fallback wiring. A second cable alone does not prove that recovery is configured.

The listed NovaStar TB30 playback combinations are alternatives, not simultaneous totals. Videos between 2K and 4K count as 4K internally, and synchronized playback reduces the simultaneous video allowance. Test the actual codec, bitrate, frame rate and complete playlist; a file extension such as MP4 does not identify its codec.

The NovaStar TB30 network priority is wired, then Wi-Fi, then 4G when multiple routes are available. LED OUT carries screen data; the management ETHERNET connector handles the LAN or internet connection. Keep these paths distinct when diagnosing discovery or cloud-access problems.

The NovaStar TB30 is IP20 and must be protected from water. In an outdoor display, place it in a suitable cabinet compartment with moisture protection and managed cooling. Check the temperature around the player under sunlight and full screen load, rather than relying only on the outdoor air temperature.

Check both total pixels and the supported operating mode. The NovaStar TB30 V1.2.4 PDF states 1,300,000 pixels and two primary outputs. The V1.2.1 PDF and NovaStar’s comparison page state 650,000 pixels with primary/backup outputs. Those documents establish a discrepancy; they do not establish that every older unit can be upgraded to the higher capacity.

Request written confirmation of firmware, output mode and usable capacity for the actual NovaStar TB30 supplied. Calculate width in pixels × height in pixels, then check each port and receiving-card chain. Screen area alone is insufficient: finer pixel pitch increases the required pixel count.

For example, a 3.2 m × 1.6 m display at P2.5 has a nominal 1280 × 640 matrix, or 819,200 pixels. Confirm the actual module and cabinet matrix before using that estimate. This installation exceeds the older total and cannot be approved solely because the source video is 4K-decodable.

Use NovaStar TB30 software according to the task: publishing content and configuring the LED hardware are different jobs.

NovaStar’s NovaLCT multimedia-player manual documents this connection workflow. It is incorrect to say that NovaLCT cannot configure Taurus players. Use ViPlex for playlists and the appropriate screen-configuration tool for receiving-card parameters; obtain the cabinet supplier’s validated configuration file before changing hardware settings.

For first commissioning, connect the management network, discover the NovaStar TB30, authenticate, confirm the cabinet map, then publish a simple test image at the screen’s native matrix. Check orientation, seams, colors and every cabinet before adding video. Save a working configuration and test scheduled playback after a restart.

For a NovaStar TB30 manual download, start with the document matching the job. The specification explains limits and ports; the quick start covers connections and login; software manuals explain operation. A specification sheet alone is not a complete commissioning procedure.

• NovaStar TB30 specifications V1.2.4, 31 July 2026 (official PDF)
• Taurus third-generation quick start V1.0.2 (PDF)
• Taurus synchronized playback instructions V1.6.7 (PDF)
• NovaLCT multimedia-player configuration manual V5.6.0 (official PDF)
• Official Taurus software, firmware and document downloads

Keep the document version with the project handover. Older instructions may show different menus or credentials. Follow the label and documentation applicable to the unit rather than assuming that a password or screenshot from another Taurus generation applies.

Before a NovaStar TB30 firmware update, record the installed version, export available configuration and confirm the package with the supplier or NovaStar. Read its release notes and maintain stable power throughout installation. Updating firmware should follow a diagnosed need; it is not the first response to a disconnected cable or an incorrect network setting.

NovaStar TB30 synchronous playback coordinates locally stored content across multiple players. NovaStar’s implementation instructions require compatible platforms, synchronized clocks and the same playback plan without random media or transitions.

• NTP: useful for players sharing a managed network; the guide recommends a LAN time server.
• RF: requires the specified RF module and antenna, with master and group settings configured.
• GPS: requires the specified module and antenna arrangement; follow the documented installation requirements, including the SIM configuration where applicable.

To configure NTP on a NovaStar TB30 network:

1. Provide a reachable NTP server and record its address.
2. Connect and log in to each player with ViPlex.
3. Enable synchronous playback and select NTP time synchronization.
4. Apply the same server and check time settings on every player.
5. Publish an identical, non-random playback plan, then test several complete loops and scheduled starts.

The older implementation guide has additional media restrictions, including a single media item per solution page in its documented scenario. Validate current firmware requirements before using complex layouts. Matching clocks alone does not guarantee that different playlists will stay visually aligned.

The existing illustrations below and above identify software and optional modules. Confirm the exact RF or cellular accessory before purchase. For NovaStar TB30 commissioning, test synchronization after a restart and after restoring network access; record the results with the final playlist.

Compare input requirements, confirmed pixel capacity and redundancy before choosing a Taurus model. Model numbers alone do not establish that one unit is a direct replacement.

The TB50/TB60 figures are from the manufacturer’s comparison, which still lists the older TB30 value. Read current model-specific PDFs before procurement. See our TB30 vs TB50 comparison and TB60 guide for related selection questions.

The NovaStar TB30 suits scheduled signage where content is updated periodically and played locally:

• Retail and chain stores: distribute campaigns centrally while keeping each screen’s playlist on its player.
• Menus and information boards: schedule content by time of day and test readability at the real viewing distance.
• Street-side signs: provide suitable environmental protection and verify network coverage inside the cabinet.
• Sensor-controlled installations: use compatible accessories and check actual brightness behavior during commissioning.

For an LED project, agree on pixel pitch, viewing distance, brightness and cabinet service access before selecting the controller. The indoor LED screen range, outdoor LED screen guide and screen buying guide explain those decisions. A controller’s loading capacity does not establish whether a screen will be bright enough for its location.

For a NovaStar TB30 price, request a dated quotation for the exact configuration. A bare-player listing cannot establish the installed project cost. Compare currency, shipping, taxes, warranty, optional modules and commissioning support on the same basis. No verified current HonghaiLED selling price is stated in this guide.

The NovaStar TB30 specification lists the player and these standard accessories:

• 1x TB30 multimedia player
• 1x Wi-Fi omnidirectional antenna
• 1x AC power cord
• 1x QR code and 1x certificate of approval

When you buy, confirm three things in writing: which specification version applies to the unit, whether the firmware is current, and who provides technical support for configuration.

Receiving-card compatibility must be verified by model and firmware; RJ45 connectors do not make every LED control system interchangeable. Send the screen matrix, cabinet arrangement, receiving-card model and publishing requirements to the HonghaiLED project team. Ask for the confirmed NovaStar TB30 loading mode, configuration files, optional-module list and recovery procedure with the quotation.

When reporting a NovaStar TB30 fault, include firmware, software version, screen matrix, receiver model, indicator behavior and the last change made. Separate discovery, cloud connectivity, content playback and LED mapping; each points to a different part of the system.

These NovaStar TB30 FAQs answer specification, software, connection and buying questions. Open a question to read the answer.

The NovaStar TB30 combines storage, scheduled playback and LED sending for unattended signage. Start selection with the real screen matrix and content workflow, then confirm pixel loading, port allocation, receiving-card compatibility and environmental protection.

Resolve the 650,000-versus-1,300,000 specification discrepancy with the supplier before approving a design. Use ViPlex for content, the appropriate NovaLCT multimedia-player workflow for screen configuration, and a tested synchronization plan when multiple players must match.

For live-source alternatives, compare the MCTRL300 sending-controller guide and VX4S video-controller guide. For a NovaStar TB30 proposal, provide the cabinet matrix and operating requirements so the complete system can be checked.

Source review: checked on 9 October 2026 against NovaStar’s linked TB30 V1.2.4 specification, earlier V1.2.1 specification, Taurus comparison, quick start and software instructions. Conflicting specifications are identified explicitly. Screen-sizing examples are calculations, not claims of a tested installation.