Driver Details

RTI Miravue VIP-1

By: RTI
Updated: Nov. 8, 2019
Version: 1.70

Description:

IP Control driver for the RTI Miravue VIP-1

Version History:

Version 1.0 Initial release for Miravue TRN-HD units

Version 1.5 Initial release for RTI Miravue VIP-1 units.

Version 1.51 Improved APEX support.

Version 1.52 Added Close Player routine prior to sending source changes.

Version 1.53 Added additional debugging and Diagnostic print statements.

Version 1.54 Fixed connectivity issues when using static IP and reconnect issues when VIP-1 goes offline.

Version 1.55 Added the ability to set the OSD Sharing Messages during the configuration process

Version 1.56 Defaulted OSD Sharing Message configuration to disabled in driver configuration.

Version 1.57 Added Force Reboot driver commands.

Version 1.58 Adjusted XPDiagnostics parsing print statements.

Version 1.59 Adjusted additional XPDiagnostics print statements.

Version 1.60 Adjusted display name print statements

Version 1.61 Test Http Obj Changes

Version 1.62 Added XPDiagnostics prints to Http Obj code

Version 1.63 Added response exceptions to Http Obj code

Version 1.64 Adjusted to using ID calls instead of name calls

Version 1.65 Extended heartbeat out to 30 seconds per unit.

Version 1.66 Merge experimental code with released code for testing.

Version 1.67 Adjusted response failure mechanism for HTTP connections.

Version 1.68 Made response failure mechanism in HTTP object dynamic.

Version 1.69 Added connection and response failure logging to XPDiagnostic prints.

Version 1.70 Cleaned up XPDiagnostics print log info.

Miravue Transceiver

This driver was designed and tested with the Miravue Transceiver TRN-HD to allow for IP control. Versions 1.5-1.54 were tested with the RTI Miravue VIP-1

Revision History

1.0 The original release of the driver for the Miravue
1.5 Supports the RTI VIP-1
1.51 Improved APEX support

1.52 Added Close Player routine prior to sending source changes

1.53 Added additional debugging and Diagnostic print statements

1.54 Fixed connectivity issues when using Static IP

Fixed reconnect issues if VIP-1 device goes offline

1.55 Added the ability to set the OSD Sharing Messages during the configuration process

1.56 Defaulted OSD Sharing Message configuration to disabled in driver configuration.

1.57 Added Force Reboot driver commands.

1.58 Adjusted XPDiagnostics parsing print statements.

1.59 Adjusted additional XPDiagnostics print statements.

1.60 Adjusted display name print statements

1.61 Test Http Obj Changes

1.62 Added XPDiagnostics prints to Http Obj code

1.63 Added response exceptions to Http Obj code

1.64 Adjusted to using ID calls instead of name calls

1.65 Extended heartbeat out to 30 seconds per unit.

1.66 Merge experimental code with released code for testing.

1.67 Adjusted response failure mechanism for HTTP connections.

1.68 Made response failure mechanism in HTTP object dynamic.

1.69 Added connection and response failure logging to XPDiagnostic prints.

1.70 Cleaned up XPDiagnostics print log info.

Connection

Connection Type: Network (TCP)

Network: User has the option of UPnP (Serial Number), UPNP (Friendly Name), or Static Entry

TCP Port: Default is set to 80. Change as necessary.

Transceiver Count

Count: The total number of Transceivers used. May be up to 64, however limitations of the

network being used will usually keep the count less than 64 in most situations.

Transceiver Data

Send Configuration To Device: This checkbox allows the integrator to decide if sending an update to a particular VIP-1 is necessary. In the event an update is needed for only one VIP-1, this will prevent all other units from needing to reboot.

Display Name: Name that is to appear in web application, in the main Miravue screen, as well as the name that is associated to the variable “Name”.

Source Connected: This checkbox asserts that a source is connected to the “IN” connection of the VIP-1 when checked.

Source Name: Source name that is to appear in web application, in the main Miravue screen, as well as the name that is associated to the variable “Local Source Name”.

Transmit Mode: User may choose between “Unicast” and “Multicast” depending on the system configuration. Unicast mode is generally recommended and is useful for small networks or for wireless video distribution. Multicast mode is useful for larger networks, especially when each VIP-1 is used for a single purpose, i.e. only for source or display purposes, not both.

• Unicast Mode: In this mode, the VIP-1 delivers a separate video stream from a source to each display (displays do not share video streams). If a source is not being viewed, there is no stream on the network for that source. Each video stream occupies up to 15Mb of network bandwidth, this needs to be considered when setting up the network as coupling this load with streaming services etc. may require a very robust system. The maximum number of simultaneous streams from a single video source is four. If more than four simultaneous connections to a single video source are required, use multicast mode.

Multicast Mode: In this mode, the VIP-1 delivers one shared video stream from each video source to multiple displays. Caution must be taken in this mode because the video stream is delivered to every device on the network and may negatively affect network performance. Therefore, multicast mode should be used in a network with IGMP snooping with query. IGMP snooping with query will allow only the desired stream to be sent to the corresponding network port so the network isn’t flooded with unwanted packets. In addition, a VLAN or a separate network is typically necessary.

Visit the RTI dealer portal (www.rticorp.com/dealer) for additional information transmit modes.

Transmit Group ID: Make sure all VIP-1 units in the system use the same ID. This becomes increasingly important when multiple systems are in the same network.

Receive Group ID: Make sure all VIP-1 units in the system use the same ID. This becomes increasingly important when multiple systems are in the same network.

OSD Sharing Messages: Allows the enabling or disabling or OSD sharing messages. This becomes increasingly important when large number of transceivers are used.

Connection Number: The option presented here is dependent on what was selected in the “Network” portion of the configuration under “Connection”. If “Serial Number” then enter the serial number. If “Friendly Name” then enter the friendly name. If “Static Entry” then enter that IP Address assigned to the VIP-1 unit.

Additional Notes

• Set up the driver configuration before programming with it. In the event changes are made to names or other information used in variable feedback, those variables will need to be reassigned (one at a time) for the changes to be reflected in Integration Designer.