NovaStar: USB and network connections on MX, NovaPro UHD, and Taurus

Before changing anything: which unit, port, and software are you using?

Start with a photo of the label and connected port. Record full model, revision, firmware, operating system, and software version. “Does not connect” can mean the computer does not detect the device, the software cannot find it, or it finds the unit but rejects login. Save the exact message.

The COEX–VMP 1.5.0 notes, §2.2 include MX20, MX30, MX40 Pro, MX2000 Pro, and MX6000 Pro. That list establishes compatibility with that version; each connector’s function must be checked in its model’s manual.

These help pages describe the cited versions. If the unit or menus differ, record that difference before continuing. Record the check results in the setup you will use.

MX40 Pro: responds to ping but does not appear in VMP

Being able to ping the MX40 does not mean VMP can find it. Record VMP detection separately from the network response.

The MX40 Pro V1.5.0 manual, pp. 5 and 10 distinguishes the two control Ethernet ports from the LED outputs. Connect the computer to a control port to use VMP. The documented front USB port exports diagnostics to a flash drive; it is not a computer USB control connection.

The VMP 1.5.0 manual, §§4.1 and 4.3.2 specifies a direct connection with manual IP and the same network segment, or a router connection with Auto mode. Apply the configuration. If it does not appear, use Add Controller with the known IP address and verify name and model before accepting.

Page 108 requires pairing VMP 1.5.0 with controller 1.5.0 and describes intermediate updates for older versions. Compare the installed pairing with its documentation before deciding on an update.

We suggest first recording how the connection reaches the computer: Ethernet, Wi-Fi, adapter, or switch. Identify the interface that reaches that IP address and repeat the search without changing the rest. If you test a switch during the rehearsal, keep the results for both topologies. Do not treat a successful ping as proof of operational control.

If VMP already connects but there is still no image, continue with black screen diagnosis. The control connection and video output require separate checks.

NovaPro UHD: what to check when switching between USB and LAN

The NovaPro UHD V1.1.0 manual identifies USB Type B for PC communication; Type A ports serve other purposes. In Communication Mode (§5.11), select USB Preferred or LAN Preferred according to the connection you want to prioritize. These are communication preferences.

For LAN, check Manual/Auto and a nonconflicting IP address on the same LAN as the PC. Master VI allows browser access using the unit’s IP address (§7.1). Page 11 describes loading RCFGx from a flash drive and excludes import through a direct NovaLCT connection.

We suggest saving a photo of the communication mode and first testing a single path outside show operation. For USB, compare operating system detection with software detection. For LAN, record whether search, browser access, or login fails. Use the credentials assigned to the unit and record the error without including the password.

This guide applies to NovaPro UHD. If the label says UHD Jr, review its manual before applying these steps. The specific software and driver on the installed computer still need checking: a USB Type B port does not establish compatibility with any software.

Taurus TB60: the control USB and USB flash drive ports are different

Select the PC, network, or USB path based on the model’s documented functions. Check publishing, control, and playback as separate tasks.

The TB60 V1.2.2 specifications, pp. 3, 5–6 assign USB Type B to computer connection for content publishing and screen control; USB Type A is for flash drive, updates, and storage. Ethernet also serves publishing and control. LED OUT identifies the outputs to the screen.

For a DPinst error and missing USB connection, the NovaLCT Multimedia Player 5.7.1 manual, §12.1.4 refers to the official driver under Downloads → Software → Driver and to support if it persists. That section does not identify a universal driver for all NovaStar units.

We suggest photographing the connector and recording whether the device appears in the operating system. During the rehearsal, test a known data cable and another direct computer connection, changing one element at a time. If a driver error appears, save its text and device details to select the corresponding official package. Do not use a cable between two USB Type A ports instead of the control port.

Taurus over a network: detect the player, log in, and read the screen configuration

The ViPlex Express Async 2.25.0 manual, §§2.3–2.5 separates a disconnected terminal, one detected without login, and a connected one. Check Async mode. For a direct Ethernet connection, it documents player DHCP and the ViPlex DHCP service with the local IP selected; over LAN, PC and player share the network.

We suggest using ViPlex DHCP only on an isolated test link you administer. On the hotel network, coordinate address assignment with its technician before activating services. If a protection blocks communication, request a review of the rules needed for that software and network; keep protections active.

The TB60 V1.0.7 specifications, p. 2 distinguish its own AP from STA connected to the router. Check which one the computer joined.

TB60 revision V1.2.2 describes simultaneous AP and STA on p. 4, but its table on p. 6 still refers to switching. Confirm revision and firmware with support before promising both modes together.

In NovaLCT Multimedia Player 5.7.1, §4, open Terminal List → Refresh, select the player, and Connect System. Specify IP → Search lets you search for a reachable IP even in another segment. “No Screen” (§12.2.1) may mean the configuration has not been read: if it already exists, use Read from HW in Screen Connection.

Detecting the player and reading its configuration are different steps. We suggest keeping screenshots of both states and checking that the selected unit is the expected one. Before writing mapping, request the current configuration from the screen lead. A factory reset is not an initial connection test.

Connection worksheet: what to record for the next test

Use the blank NovaStar connection worksheet. Separate what was observed from what you plan to test. A test is closed when you can repeat the result and restore the initial setting; encountering a different menu is useful information too.

Record the function you verified: detection, login, configuration reading, or control. “It worked” without that detail leaves questions for whoever resumes the setup. Keep the record local and remove passwords, other parties’ network addresses, and personal data before sharing it.

To prepare the show signal, connect this worksheet with video and screens and our video processing service. Send us the model, versions, and error message to review the scope of assistance.

MX20 and MX30: control port and VMP detecting only from another PC

To compare computers, record the software, version, and connection used. The following connectors apply specifically to MX20 and MX30.

The MX20 V1.5.0 manual, §§2.1–2.2, pp. 5–7 (PDF 6–8) assigns the front USB port only to exporting diagnostics to a flash drive. It documents two ETHERNET control ports for VMP, with the same function and no priority between them. Numbered outputs 1–6 belong to the screen.

The MX30 V1.5.0 manual, §§2.1–2.2, pp. 5–8 (PDF 6–9) distinguishes the same front USB use and two equivalent ETHERNET control ports. On this model, numbered outputs are 1–10. Identify the control block label before connecting the computer.

In MX20, §7.2, pp. 26–27 (PDF 27–28) and MX30, §7.2, pp. 28–29 (PDF 29–30), Communication Settings > Network Settings offers Manual or Auto. For Manual, enter IP Address, Subnet Mask, and Default Gateway, then select Apply. Record the initial values before changing them.

The VMP 1.5.0 manual, §4.1, pp. 5–6 (PDF 9–10) describes a direct link with static IP on the same segment, or a router with Auto; it uses MX40 Pro as an example. In §4.3.2, pp. 8–9 (PDF 12–13), Add Controller allows searching by IP on the same LAN even with different subnets. Verify state, name, and model before accepting. An IP search does not by itself resolve a block on the computer.

Suggested comparison with the IT lead: record operating system, VMP, firmware, interface, and exact message from each PC. During a rehearsal, keep the controller and control cable unchanged and connect one computer at a time to the same network point. Record ping, automatic search, and IP search separately. If only the VMP response changes, take those screenshots to IT and NovaStar support to determine what to review.

Common error: interpreting a successful ping as proof that VMP is operational. Also, do not connect the PC to numbered outputs in an attempt to resolve detection. This comparison aims to locate the difference; it does not identify a blocked TCP/UDP port or recommend removing computer policies.

Complete the NovaStar worksheet. If control already works but there is no image, continue with black screen. To prepare the event processor, connect the record with video processing. Tip: attach a photo of the connector used as well as the software screenshot.

COEX: VMP disconnects when using Wi-Fi

The figure 4-2 in VMP 1.5.0, §4.1, p. 6 (PDF 10) shows the PC connected to a router over Wi-Fi or Ethernet, and the controller over Ethernet. This is a diagram with MX40 Pro, not a guarantee of wireless stability. For MX20/MX30, use the control ports identified in the connection guide.

Suggested test: keep processor, project, VMP version, and computer unchanged. Record router, connection point, wireless band, and interface used. First test the computer wired to the router and then over Wi-Fi for a comparable period; record duration, time of each dropout, and VMP state. Change only one condition at a time and also record any address change that appears.

Separate loss of control from image changes: ask the screen operator to record what they saw at the same instant. Record whether VMP stopped listing the controller, showed disconnection, or rejected an operation. Save a screenshot and time. A short session without dropouts remains an observation from that test; it needs checking throughout the event’s intended use.

Record what remains accessible if the mobile connection is interrupted and how the local operator takes control.

The difference between wired and Wi-Fi helps guide the next test. If both fail, keep versions, times, and screenshots for support; if only Wi-Fi fails, review the link with the network technician before changing software or firmware. Restore the test settings and identify a control station the operator can use.

Use the NovaStar worksheet and coordinate the control path with video and screens and video processing. Tip: write “VMP lost connection at this time; the screen showed this.” Complete the record with your test observations.