AVPro Edge MXnet Universal

Driver Details

By: RTI

Updated: Sept. 18, 2026

Version: 1.05

Download Driver

Rating: 0.0 (0 ratings)

The AVPro Edge MXnet Universal driver has been developed by Janus Technology for controlling the MXnet 1G, 10G and USP product ranges. This one driver handles all standard matrix routing together with model three product ranges dependent features such as Multi media playback and image streams.

Version History:

v1.00 - Initial Release

v1.01 - Updated commands with multiple encoder/decoder parameters to handle sustained presses that could crash controllers; added MXnet 1G V1 encoder/decoder snapshots; clarified alias naming.

v1.02 - Completed documentation. Some small fixes to tags.

v1.03 - Fixed a glitch in the table of contents when PDF version generated.

v1.04 - Fixed a glitch in the table of contents when PDF version generated.

v1.05 - Added Offline configuration

AVPRO EDGE|MXNET 1G/10G/USP|IP|1.05

Installer Setup Guide

This is the simplified embedded version of the instructions for this driver. A fully-formatted version of these instructions is available in Instructions.pdf under Additional Files.

Part 1 – Getting Started

About the Driver

The AVPro Edge MXnet Universal driver has been developed by Janus Technology for controlling the MXnet 1G, 10G and USP product ranges. This one driver handles all three product ranges. The driver provides standard matrix routing together with model-dependent features such as Multi-View, video walls/mosaics, media playback and image streams.

Driver Features

• Video routing

• Audio routing (Analog / HDMI)

• Gain control for encoders and decoders

• Video routing presets

• Video and Mosaic wall controls

• Multi viewer controls

• Media player

• Image preview

• Encoders and Decoders Settings

• CEC, RS232 and IR passthrough

• Hot plug status

System Requirements & Prerequisites

• Integration Designer: Apex ID11, Version 11.13.6 minimum stated in the supplied guide

• RTI XP processor firmware: 25.1.27 or later

• MXnet 1G: Firmware V4.32.3

• MXnet 10G: Firmware V5.06

• MXnet USP: Firmware V3.42.4

Before You Start

Complete these checks before opening the driver configuration. They prevent the most common commissioning failures and make the later discovery steps predictable.

Network requirements

• The MXnet controller must already have an IP address. A static address or DHCP reservation is strongly recommended.

• The MXnet controller and RTI processor must be reachable across the required network path.

• The commissioning PC running Integration Designer must also be able to reach the MXnet controller directly. Initial configuration of the system is done through Integration Designer directly querying the MXnet controller.

• Record the MXnet control-interface IP address before you begin.

MXnet preparation

• Power and connect the required encoders and decoders.

• Create any video walls or mosaics in Mentor before discovery if they are required by the project.

• For USP media-player projects, ensure the required playlists already exist on the USP device before discovery.

• Check the firmware/software versions against the requirements above.

Part 2 – Commissioning

Add the Driver to Integration Designer

This section establishes the driver and the connection settings before any project-specific UI programming is attempted.

From Add Workspace Item -> Drivers, choose the AVPro Edge MXnet Universal driver from the Official list. Integration Designer installs the driver with a single placeholder source called MXnet Settings.

Open the driver Configuration / Config Settings page.

Enter the MXnet controller control-interface IP address in the driver IP Address setting.

Save the project before running discovery or alias-management actions.

This driver has two configuration flows. An online mode which connects to the MXnet and gathers its configuration and an offline mode which can be used without need to connect to the device.

Offline Mode

As mentioned previously, this mode can be used to pre-program the MXnet integration before the equipment is set up. This allows installers to create a program before visiting the site. This method requires more configuration input and you need to ensure what is entered in the driver is replicated exactly in Mentor to ensure the system works as expected. Below we will go through the configuration settings in the driver and how to set up a system in offline mode.

System Settings

This allows you to select either online or offline mode. Select offline mode.

Model

Select the model of the MXnet you are going to connect to. It is important to select the correct model as this provides you with feature and functionality of the specific device.

System Status

This shows whether your configuration has been synced with your program. It allows you to make multiple configuration changes and then sync them with your program in a single operation. If this window indicates that an update is required, press Apply Changes Settings to update the functions, variables and tags in your program.

Connection

Enter the IP address of the device that you will eventually connect to.

Switcher Size

Enter the number of encoders and decoders of your configuration along with the number of switching presets you require.

Input and Output Names

Enter the input and output names of the TX and RX devices. These names must be replicated exactly in Mentor. See Moving from Offline RTI settings to Online.

Multi-View Settings

MXnet 1G – MV41V2

• Enter the number of MV41V2s in the system.

• Enter the port number for each MV41V2. These normally start at port 50000. See Moving from Offline RTI settings to Online to find the correct ports when you connect to the live system.

• Enter the output port numbers of the MV41V2.

MXnet 10G and USP

• Enter a comma-separated list of outputs that you would like to use as Multi-Viewers.

• Enter the resolution of the Multi-Viewer output.

Video Wall Settings

• Enter the number of video walls to be created.

• For each Video Wall add the following:

• Video Wall Name

• Each layout name that will be associated with the wall

• The maximum number of windows for the wall.

Mosaic Settings

• Enter the number of mosaics to be created.

• For each mosaic add the following:

• Mosaic name

• Each layout name that will be associated with the mosaic

• The maximum number of windows for the mosaic.

Media Player (USP Only)

• Enter the number of playlists to be created on the USP.

• Enter the name of each playlist.

Offline mode – Mentor Setup

The In / Out alias setup

To transfer the names created in the RTI program to the Mentor software, we need to add a prefix to the name so the system knows which input or output number we are dealing with. In the highlighted image below we have entered IN7-Roku. In the RTI configuration Input 7 would have the name Roku. So for all inputs and outputs in Mentor, the friendly name needs an IN or OUT prefix followed by the input or output number.

Multi-View Settings (1G and MV41V2)

You need to ensure that the correct MV41V2 ports are entered in your RTI program, you can do this by running the ‘config get mv41list’ API command in the System Log section of the MXnet CBOX web page. This command returns a JSON response; use it to find your MV41 port numbers. Compare the MAC addresses with the information on the configuration page of the CBOX, then ensure the correct port number is set up in your RTI program.

Multi-View Settings (USP and 10G)

No additional configuration is required for USP and 10G Multi Viewers. When the system runs for the first time, Multi-View layouts will be generated for each output if required.

Video Wall Settings

Create video walls to match the video wall name and layouts in the RTI program. In Mentor, go to the Video Wall / Multi Viewer menu and select VIDEO WALL.

Click Add VW and fill in the information shown in the screenshot below. The Video Wall Name should be the same as in the RTI program. The Layout Name should be one of the layouts you specified in the RTI program.

If you need to add additional video wall layouts, select the video wall, expand Layouts, then click Add Layout to display the following menu.

Enter the video wall layout name and click Save. Do this for all video wall layouts. Please follow the Mentor video wall documentation to fully configure the video wall.

Mosaic Settings

Create a mosaic to match the mosaic name and layouts in the RTI program. In mentor go to the Video Wall / Multi Viewer menu and select MOSAIC.

Click add vw and fill in the information in the screen shot below. Video Wall Name should be the same as in the mosaic name in the RTI program.

If you need to add additional mosaic layouts, select the mosaic, expand Layouts, then click Add Layout to display the following menu.

Enter the mosaic layout name and click Save. Do this for all mosaic layouts. Please follow the Mentor mosaic documentation to fully configure the mosaic.

Media Player Settings (USP)

Create playlists for each playlist defined in the RTI program. To do this in Mentor, select Media Player, then Playlists. Click “Create New Playlist” and enter the playlist name.

Moving from Offline RTI settings to Online

Once an offline configuration is complete, it can be downloaded to an RTI processor and used as normal. It is also possible to move from an offline configuration to an online configuration. If the system is set up and working via the RTI driver, you can select online mode and query the processor. The configuration gathered from the MXnet will match your offline setup and will work in the same way. You may see more entries in the tags if you did not define all video walls, mosaics or playlists in your offline configuration.

Online Mode - Prepare the MXnet System

The IN/Out alias rule

Every encoder and decoder on the MXnet box has an alias field. To be recognized, that alias must start with IN (for an encoder) or OUT (for a decoder), immediately followed by the port number — e.g. IN1, OUT12. This is the number that appears everywhere else in the driver: as the Select Input / Select Output parameter on switching functions, and in every numbered tag and variable (Input [x] Name, Output [x] Volume, and so on).

You can optionally add a hyphen and a friendly name after the number, e.g. IN1-Roku or OUT3-Kitchen. Leave the friendly name off and the driver falls back to calling the device "Input 1" / "Output 1" (using the port number) until you give it a better one.

Recommended method: Auto-Configure Aliases

Use Auto-Configure Aliases when you want the driver to establish a valid numbering scheme automatically. Existing valid aliases are preserved; other devices are assigned aliases in ascending sequence, filling gaps. The action then re-reads the system automatically.

Run Auto-Configure Aliases from the driver menu in Integration Designer.

Review the completion message showing how many input and output aliases were assigned.

If friendly names are required, rename them later in Mentor or in the driver Input Names / Output Names settings.

Alternative method: name ports in Mentor

If you'd rather set alias names directly on the hardware — you can name each port by hand from Mentor, the MXnet web configuration interface.

Open the Configure page in the Mentor web UI as shown above. For each encoder or decoder, enter the Custom Name using the IN#/OUT# convention, for example: IN1-Roku or OUT3-Kitchen. Note that Mentor aliases are limited to 12 characters total, with no spaces or special punctuation. For longer, readable display names, use the driver Input Names and Output Names settings after discovery.

Start over: Clear All Aliases

If you have an already configured MXnet system but wish to start afresh, you can use Clear All Aliases. This removes every custom alias on the MXnet system and returns configuration names to the factory defaults. Use it only when you intentionally want to rebuild the naming scheme.

Discover the MXnet System

With the IP address entered and aliases prepared, run Query MXnet. This is the central discovery action for the driver.

Wait for discovery to complete before editing the dynamic configuration fields or building controls that depend on the discovered system.

What Query MXnet discovers

• MXnet model

• Available inputs and outputs and their names

• Video walls and mosaics created in Mentor

• 1G MV41v2 multi-view devices where applicable

• USP playlists where applicable

When to run Query MXnet again

• After adding or removing MXnet devices

• After correcting hardware aliases

• After adding, removing or renaming a video wall, mosaic or layout in Mentor

• After USP playlists are added, removed or renamed

• Whenever a project no longer matches the current MXnet configuration

Check the Discovered System

After a successful query, check the read-only discovery results before proceeding. This is the point where you confirm that the RTI project reflects the real installation.

• Model: The detected MXnet model is the model expected on site.

• Number Of Inputs: The discovered count matches the connected/usable encoders.

• Number Of Outputs: The discovered count matches the connected/usable decoders.

• Number Of Presets: Default is 16; reduce only if the project needs fewer generated preset choices.

Name Inputs and Outputs

Once Query MXnet has completed, the driver exposes Input Names and Output Names settings for the discovered devices. These names are used throughout sources, generated functions, tags and runtime feedback.

Add the names

Edit the required values under Input Names and Output Names.

Run Apply Changes from the driver menu.

Confirm the renamed choices appear in the relevant function parameters and generated tags.

Add RTI Sources

Once the names have been configured and applied, the driver will create an additional RTI Source for each output. You can now return to Add Workspace Item, find the driver under Add To Existing Driver and add these Sources to the project.

The RTI Sources assist with tag programming. If you set the Source of a controller page or layer or a page to be the Source for a given output, tags associated with assigning output features will automatically use that output on that page. For example, you define one of your outputs as Living Room. This creates an RTI Source called Living Room. You set that as the Source for a Controller page. If you then tag a button on the page with Single-Switch: Select Input: Input BluRay (3), then the button will be set up to switch the BluRay input to the Living Room output.

Prove Basic Routing

Before building multi-switch, presets or advanced pages, prove one simple AV route. This validates discovery, aliases, network communication and basic feedback in one test.

Create a test button and assign the Output Routing function Switch Output (AV).

Choose one known input and one known output.

Download/run the project and press the button once. The route should change immediately.

Bind a label or diagnostic object to Output x Current Input (Name). Confirm that it reports the friendly name of the source now routed to the output.

Part 3 – Common Programming Tasks

Standard Source Routing

Combined video and audio

Tag: Single-Switch: Select Input: <name> (<number>)

Use Switch Output (AV) in the Output Routing category when video and audio from one source should be routed together to one output. The command is one-shot: a single press performs the route immediately. Using the tag will assign the correct switch command for the current RTI Source representing the output and will label the button with the name of the input.

• Input: Configured input names plus Disable

• Input: Source to route. Disable blanks the output rather than routing a source.

• Output: Configured output names

• Output: Destination to switch.

Feedback

Use Output x Current Input (Name), a String variable, to show which source is currently routed to an output.

Independent breakaway routing

Where a display's picture and its sound (or USB) need to come from different sources at the same time — for example, video from a satellite TV feed but audio from local PA system — use Switch Output (Breakaway), also found in the Output Routing category.

• Input: Configured input names plus Disable

• Input: Source for this call.

• Output: Configured output names

• Output: Destination for this call.

• Mode: Video, Audio, USB; (10G only) Analog Audio

• Mode: Path changed by this call.

Switch Output (Breakaway) only switches one path per press, whichever path you set with the Mode parameter. To give a display fully independent video and audio, wire one button with Mode set to Video (and the video source as Input), and a second button with Mode set to Audio (and the audio source as Input), both pointing at the same Output. Add a third button with Mode set to USB if that path also needs to be broken away.

Multi-Switch

Multi-Switch lets the user route one source to multiple outputs. Choose the interaction model first; the available functions, tags and feedback depend on the selected mode.

Choose the user workflow

• In to Out (Instant): Choose switching type (1) -> choose input (2) -> tap outputs (3)

• In to Out (Instant): Each output switches as it is tapped.

• In to Out (Synchronized): Choose type (1) -> choose input (2) -> select outputs (3) -> Apply Selection (4)

• In to Out (Synchronized): Nothing switches until Apply Selection.

• Out to In: Choose type (1) -> select outputs (3) -> choose input (2)

• Out to In: All selected outputs switch when the input is chosen.

Note that if breakaway switching is never required in your project, you can call Select Switching Type: Combined once as a project or page start-up function call to set the default rather than exposing the choices as buttons.

Which of these three workflows you want the user to use is a project-wide design-time choice. Set Multi-Switch Mode in Driver Configuration to make your choice. Then proceed to wire up the user interface. The following sections explain how to do this for each mode.

UI Programming: In to Out (Instant)

Select the switching type, then the input. Outputs already showing that input highlight automatically. Tapping an unhighlighted output switches it immediately. Selecting another input refreshes the output highlighting. Select All, Clear All and Apply Selection are not used in this mode.

Tag: Multi-Switch: Select Type: <type>

Use these tags to set up the switching type buttons with the appropriate Select Switching Type function calls. It will also auto-name the button and set reversed feedback to show when the corresponding mode is selected..

Tag: Multi-Switch: Input <name>

Use these tags to set up the input selection buttons with the appropriate Select Input functions and to auto-name the button with the input name. It also sets up feedback to show that this is the currently selected input.

Tag: Multi-Switch: Output <name>

Use these tags to set up the output selection buttons with the appropriate Switch Output To Selected Input functions and to auto-name the button with the output name. Feedback will be set up to show the button as reversed if that output is currently switched to the selected input.

Functions and variables, in sub-section Multi-Switch (For Current Remote)

• Select Switching Type: Mode

• Select Switching Type: Selects Video, Audio, USB, Combined or the 10G Analog Audio option.

• Select Input: Input

• Select Input: Select the input to apply.

• Switch Output To Selected Input: Output

• Switch Output To Selected Input: Switches immediately

• Select Switching Type <name>: Boolean. True when the current switching type is the named type

• <input> Selected: Boolean. True when the given input is selected for multi-switching

• <output> Selected: Boolean. True when the given output’s current input is the selected input

In to Out (Synchronized)

Select the switching type and input. Select or deselect outputs to build the pending set. Outputs that are already on the given input are pre-selected. Press Apply Selection to route the selected input to every highlighted output. Select All and Clear All are available.

Tag: Multi-Switch: Select Type: <type>

Tag: Multi-Switch: Input <name>

Tag: Multi-Switch: Output <name>

Use these tags to set up the output selection buttons with the appropriate Select Output functions and to auto-name the button with the output name. Feedback will be set up to show the button as reversed if that output is currently selected.

Tag: Multi-Switch: Apply Selection

Use this tag to assign the Apply Selection function to a button. The naming of the button is left to the installer.

Tag: Multi-Switch: Select All Outputs

Use this tag to assign the Select All Outputs function to a button. The naming of the button is left to the installer.

Tag: Multi-Switch: Clear All Outputs

Use this tag to assign the Clear All Outputs function to a button. The naming of the button is left to the installer.

Functions and variables, in sub-section Multi-Switch (For Current Remote)

• Select Switching Type: Mode

• Select Switching Type: Selects Video, Audio, USB, Combined or the 10G Analog Audio option.

• Select Input: Input

• Select Input: Select the input to apply.

• Select Output: Output

• Select Output: Selects an output to which the input should be routed

• Apply Selection: Routes the input to all selected outputs

• Select All Outputs: Selects all outputs as destinations for the input.

• Clear All Outputs: Clears all outputs as destinations for the input

• <input> Selected: Boolean. True when the given input is selected for multi-switching

• <output> Selected: Boolean. True when the given output is selected for multi-switching

• Select Switching Type <name>: Boolean. True when the current switching type is the named type

Out to In

Select the switching type, select one or more outputs, then choose an input. The selected outputs switch immediately. In this mode output feedback reflects the user-selected set rather than automatically mirroring live routing.

Tag: Multi-Switch: Select Type: <type>

Tag: Multi-Switch: Output <name>

Tag: Multi-Switch: Input <name>

Use these tags to set up the input selection buttons with the appropriate Switch Input To Selected Outputs functions and to auto-name the button with the input name.

Functions and variables, in sub-section Multi-Switch (For Current Remote)

• Select Switching Type: Mode

• Select Switching Type: Selects Video, Audio, USB, Combined or the 10G Analog Audio option.

• Select Output: Output

• Select Output: Selects an output to which the input should be routed

• Switch Input To Selected Outputs: Input

• Switch Input To Selected Outputs: Routes the selected outputs to the given input

• <output> Selected: Boolean. True when the given output is selected for multi-switching

• Select Switching Type <name>: Boolean. True when the current switching type is the named type

Routing Presets

A switching preset stores a snapshot of routing for a group of outputs, so that exact combination can be recalled later with a single button press.

Before You Start

The number of preset slots available is controlled by the Number Of Presets setting in the driver's configuration properties. Adjust this to match the number of presets you want your system to support.

User workflow

Step 1: Select the outputs whose routing you want to save.

Step 2: Press a save preset button to save the routing. It is possible to save either all routing for the output (audio, video and USB) or just a sub-selection. This is determined by a parameter of the function assigned to the button.

Step 3: Press a recall preset button to recall the saved routing. Only those outputs and the type of routing that were saved will be recalled; all other routing will be unaffected.

UI Programming

Tag: Switching Presets: Output <name>

Use these tags to set up the output selection buttons with the appropriate Toggle Output functions and to auto-name the button with the output name. Feedback will be set up to show the button as reversed if that output is currently selected.

Tag: Switching Presets: Option: Select All Outputs

Use this tag, if desired, to set up a short-cut button to call Select All Outputs to select all the outputs. The button will need to be named manually.

Tag: Switching Presets: Option: Clear Selected Outputs

Use this tag, if desired, to set up a short-cut button to call Clear All Outputs to clear any currently selected the outputs. The button will need to be named manually.

Tag: Switching Presets: Preset Save: <number>

Use this tag to assign the Save Preset (Selected Outputs) function to a button. The button will need to be named manually. Note that by default the assigned function will save all routing. Adjust the PresetType parameter if you only want to save specific types of routing.

Tag: Switching Presets: Preset Recall: <number>

Use this tag to assign the Recall Preset function to a button. The button will need to be named manually.

Functions and variables, in sub-section Switching Presets (For Current Remote)

• Toggle Output: Output

• Toggle Output: Select or deselects an output to be saved in a preset

• Select All Outputs: Select all outputs to be saved in the preset

• Clear All Outputs: Clears all currently selected outputs

• Save Preset (Selected Outputs): PresetId, PresetType

• Save Preset (Selected Outputs): Saves the routing of the currently selected outputs in preset number PresetId. PresetType defines what sort of routing information (Video, Audio, USB or some combination) is saved.

• Recall Preset: PresetId

• Recall Preset: Recalls the given preset number.

• <output> Selected: Boolean. True when the given output is selected for preset saving

Volume and Mute

All systems offer control of the output volume of the receiver units. Additionally, the 1G and 10G systems can control the gain on input extracted audio.

Output volume

Output volume can be controlled as a slider through directly setting the value with Set Volume or through stepping buttons with Volume Step. There is a Mute function that sets volume to zero when switched on and restores the previous level when switched off. Note that this is applied directly to the volume level – there is no separate mute status; mute is volume level zero and vice-versa.

Output volume functions and variables are associated with their corresponding output RTI Sources, so if the UI page has an RTI Source associated with it, the programming will automatically choose the right output.

Tag: Volume

Use this tag to initialize volume selection sliders (Set Volume function) and feedback of the current volume level. ( <output-name> Volume variable).

Tag: Volume Up

Use this tag to initialize volume step up buttons (Volume Step – Up function).

Tag: Volume Down

Use this tag to initialize volume step down buttons (Volume Step – Down function).

Tag: Mute

Use this tag for mute toggle buttons (Set Mute - Toggle function) and feedback of the current mute state. ( <output-name> Volume variable).

Tag: Mute On

Use this tag for mute on buttons (Set Mute – Mute function).

Tag: Mute Off

Use this tag for mute on buttons (Set Mute – Unmute function).

Functions, in sub-section <output-name> Volume

• Volume Step: Direction Up/Down

• Volume Step: Step output volume by one increment

• Set Volume: Level 0 – 100

• Set Volume: Set an exact output level; useful for sliders or macros

• Set Mute: Mute / Unmute / Toggle

• Set Mute: Set or toggle mute state

Variables in sub-sections Output Volume and Output Mute Status

• <output-name> Volume: Number. The current volume level of the output

• <output-name> Muted: Boolean. True if the output’s current volume level is zero

Input extracted-audio volume

Each input can also expose extracted-audio gain control (except on USP systems). This is separate from output volume and applies to audio extracted from the encoder input signal. There are no tags for input volume control.

Functions, in sub-section <input-name> Extracted Audio Volume

• Volume Step: Direction Up/Down

• Volume Step: Step output volume by one increment

• Set Volume: Level 0 – 100

• Set Volume: Set an exact output level; useful for sliders or macros

Variables in sub-section Input Extracted Audio Volume

• <input-name> Volume: Number. The current volume level of the input

Part 4 - Multi-View, Video Walls and Mosaics

Common User Interface Style

Multi-views, video walls and mosaics share the same user interface control flow, providing a simple common approach to managing all of them. The user first establishes the target being controlled, then chooses a layout to show, chooses a window within the layout, and finally assigns an input to the window.

The key difference is that all multi-view devices in the system share a common set of pre-defined layouts (which also means that they can share a single UI page definition) whereas walls and mosaics and their layouts are queried dynamically from the system and will require individual UI pages to be designed to match each one.

Multi-View

Model differences

Multi-view is supported on all MXnet systems, however there are variations in how it is provided.

• 1G: Multi-view is provided through external AC-MXNET-1G-MV41V2 devices. These are selectable as sources and then the contents of that source feed can then be configured as a multi-view. All outputs showing that source will see the same multi-view and it is possible to have several MV41V2 devices in the system to support having different multi-view configurations available simultaneously.

• 10G and USP: Every receiver has the ability to support multi-view, however as enabling an output for multi-view adds extra tags and other overheads to the driver, the installer specifies the outputs on which they actually want to have multi-views in order to keep these overheads to a minimum.

Configure Multi-View

1G systems

Ensure the MV41v2 device(s) are present and correctly aliased on the MXnet system.

Run Query MXnet.

Confirm the driver has created the Multi-View Device controls for the discovered unit(s). If you check the list of tags for the driver, you should see a tag Multi-View: <name> for each discovered MV41v2 device.

10G / USP systems

In the driver configuration, under the Multi-View category, enter the output numbers that should act as multi-viewers in Outputs Configured As Multi-View. The field accepts comma/range syntax such as 1,3-5.

Set the per-output Multi-Viewer Resolution to match the resolution of the display device being used for that output. This ensures that the multi-view is generated correctly.

For 10G systems, Multi-View Frame Rate is adjustable to tune for the best overall performance. It affects all the multi-view outputs.

Confirm the driver has created the Multi-View Output controls for the discovered unit(s). If you check the list of tags for the driver, you should see a tag Multi-View: <name> for each output that has been requested to be configured for multi-view.

Select the Target for a Controller

To allow a single UI page to be shared between all the multi-views and to avoid a proliferation of functions and variables, the multi-view functions work by first telling the driver which multi-view is being controlled and then using a common set of functions and variables from that point on.

So, before a controller can use the multi-view functions, the driver must know which multi-view that controller is currently operating. This is done by calling the function Select Multi-View Device (1G) or Select Multi-View Output (10G/USP). Note that this is a per-view function, so each controller in the system can independently control different multi-views without interfering with each other.

The Select Multi-View … function can only be placed in one of the following:

• A Room Selection Event

• A Source's Activity Start event

• A Source's Activity Ready event

• A button wired directly on the Controller UI (pressed by hand on that panel, not driven by another driver's macro or event). The Multi-View: <name> tag can be used to assign the function in this case.

• If you try to call the function from anywhere else — a global macro, another device's event, a timed event — the driver will not know the controller to associate with and all the subsequent multi-view functions will not work as expected.

Once the target is selected correctly for that controller, the rest of the multi-view functions and variables inherit that current target context.

Build the Multi-View UI

User Experience

Step 1: Select the layout to show on the multi-view.

Step 2: Select the window of the layout to control, or the special audio “window” to control audio output.

Step 3: Press an input button to switch that input to be displayed (or audio played, for the audio “window”) in the target window.

Step 4: Multi-view also supports presets, where the current combination of layout and inputs can be stored in a preset and recalled later. Presets are shared across all multi-views (as their layouts are all the same), so a preset saved on one multi-view device or output can be recalled on another. Multi-view presets are distinct from switching presets, so saving multi-view preset 1 will not overwrite switching preset 1.

UI Programming

Tag: Multi-View: Layout: <name>

Use these tags to set up the layout selection buttons with the appropriate Activate Layout functions. Feedback will be set up to show the button as reversed if that layout is currently selected. To allow the installer the choice of using visuals to represent the layouts (as shown in the screenshot above), the buttons are not automatically named, so if text labels are wanted these will have to be added manually.

Tag: Multi-View: Window: <name>

Use these tags to set up the window selection buttons, including the audio “window”, with the appropriate Select Window functions. Feedback will be set up to show the button as reversed if that window is currently selected and to fill in the name of the current input for that window as the text label.

Tag: Multi-View: Input: <name>

Use these tags to set up the input selection buttons to call the corresponding Switch Input To Selected Window functions. Feedback will be set up to show the button as reversed if that window is currently selected and to fill in the name of the current input for that window as the text label.

Tag: Multi-View: Preset Save: <number>

Use this tag to assign the Save Preset function to a button. The button will need to be named manually..

Tag: Multi-View: Preset Recall: <number>

Use this tag to assign the Recall Preset function to a button. The button will need to be named manually.

In addition to the tag-based programming, multi-views offer a couple of function that are designed for use in timed programming or macros: Recall Preset for Multi-View Device/Output and Select Input For Multi-View Device/Output Window. These are described in the table below.

Functions and variables, in sub-section Multi-View Device/Output Control (For Current Remote)

• Select Multi-View Device/Output: Device/Output

• Select Multi-View Device/Output: Chooses which multi-viewer will be controlled by all the other functions in this category.

• Activate Layout: Layout

• Activate Layout: Choose which layout to use on the multi-view

• Select Window: Window

• Select Window: Choose which layout window of the layout to control

• Select Audio Window: Selects the audio “window” for control

• Switch Input To Selected Window: Input

• Switch Input To Selected Window: Switches the given input to the currently selected window

• Save Preset: Preset Position

• Save Preset: Saves the current layout and its inputs, including audio, as the given multi-view preset number.

• Recall Preset: Preset Position

• Recall Preset: Recalls the given preset number.

• Recall Preset For Multi-View Device/Output: Preset Position, Multi-View Device/Output

• Recall Preset For Multi-View Device/Output: Recalls a multi-view preset directly onto a multi-viewer without having to use Select Multi-View Device/Output to set the context. Intended for use in macros or timed programming.

• Select Input for Multi-View Device/Output Window: Multi-View Device/Output, Layout, Input, Window

• Select Input for Multi-View Device/Output Window: Switches a multi-viewer to a specific layout (if not already on it) and then switches an input to a window on that layout. Intended for use in macros or timed programming.

• Current Multi-View: Integer. The numeric identifier of the multi-view device or output being managed by the current controller.

• Current Multi-View Name: String. The name of the multi-view device or output being managed by the current controller.

• Current Selected Layout: String. The name of the currently selected layout.

• <layout name> Selected: Boolean. True when the given layout is selected.

• Current Multi-View Window: Integer. The number of the currently selected window (audio is 0).

• Audio Window Selected: Boolean. True if the audio “window” is selected.

• Audio Current Input Name: String. Name of the input currently supplying audio.

• Window <n> Selected: Boolean. True if the given window is selected.

• Window <n> Current Input Name: String. Name of the input currently shown on the given window.

• Current Selected Input: String. Name of the currently selected input

• <input name> Selected: Boolean. True if the given input is the one currently selected.

Video Walls and Mosaics

Video walls and mosaics are created in Mentor, not in the RTI driver. Once they exist, run Query MXnet so Integration Designer can create the controls that mirror the Mentor configuration, for example a 2x2 wall like the one below:

If additional walls or mosaics, or layouts within them, are created, running Query MXnet again will add matching functions and variables to the driver without affecting existing programming. However, if walls, mosaics or layouts are removed or renamed, this will break existing programming. You will need to treat any renamed walls, mosaics or layouts as completely new and re-do the programming appropriately.

After running Query MXnet, the driver will then have a set of functions and variables for each wall and mosaic discovered. You can verify this has worked correctly by checking the tag list for Video Wall: <name>: Layout: <name> and Mosaic: <name>: Layout: <name> tags for each wall or mosaic layout that you expect to exist.

Select the Target for a Controller

Unlike multi-views, because each wall or mosaic can be unique in its construction and layouts, each has its own set of functions and variables and so they cannot share a single UI page. However we still need to inform the driver of which wall or mosaic a controller is controlling in order for it to know which set of variables it needs to keep up-to-date. So again, we first tell the driver which wall or mosaic is being controlled before showing the UI on the controller. This is done by calling the function Select Video Wall <name> or Select Mosaic <name>. Note that this is a per-view function, so each controller in the system can independently control different walls without interfering with each other.

The Select … function can only be placed in one of the following:

• A Room Selection Event

• A Source's Activity Start event

• A Source's Activity Ready event

• A button wired directly on the Controller UI (pressed by hand on that panel, not driven by another driver's macro or event). The Video Wall: <name> or Mosaic: <name> tag can be used to assign the function in this case.

Build the Wall or Mosaic UI

User Experience

Step 1: Select the layout to show on the wall or mosaic.

Step 2: Select the window of the layout to control.

Step 3: Press an input button to switch that input to be displayed in the target window.

Step 4: Walls and mosaics also supports presets, where the current combination of layout and inputs can be stored in a preset and recalled later. Presets are specific to each wall and mosaic and also distinct from switching and multi-view presets, so saving preset 1 for wall X will not overwrite preset 1 for any other wall or mosaic, or the multi-view or switching presets.

Note that unlike the multi-view UI, a separate custom UI will need to be built for each wall or mosaic.

UI Programming

In this section, the tags for mosaics are the same except with Mosaic replacing Video Wall.

Tag: Video Wall: <name>: Layout: <name>

Tag: Video Wall: <name>: Window: <name>

Use these tags to set up the window selection buttons the appropriate Select Window functions. Feedback will be set up to show the button as reversed if that window is currently selected and to fill in the name of the current input for that window as the text label.

Tag: Video Wall: <name>: Input: <name>

Tag: Video Wall: <name>: Preset Save: <number>

Use this tag to assign the Save Preset function to a button. The button will need to be named manually..

Tag: Video Wall: <name>: Preset Recall: <number>

Use this tag to assign the Recall Preset function to a button. The button will need to be named manually.

Functions and variables, in sub-section Wall/Mosaic <name> Control (For Current Remote)

• Select Video Wall/Mosaic <name>: Chooses which wall or mosaic is being controlled to ensure variables are kept up-to-date for this controller

• Activate Layout: Layout

• Activate Layout: Choose which layout to use on the wall/mosaic

• Select Window: Window

• Select Window: Choose which layout window of the layout to control

• Switch Input To Selected Window: Input

• Switch Input To Selected Window: Switches the given input to the currently selected window

• Save Preset: Preset Position

• Save Preset: Saves the current layout and its inputs, as the given preset number for this wall/mosaic

• Recall Preset: Preset Position

• Recall Preset: Recalls the given preset number.

• Current Selected Video Wall/Mosaic: String. The name of the wall or mosaic being controlled.

• Current Selected Layout: String. The name of the currently selected layout.

• Layout <layout name> Selected: String. The name of the given layout (for auto-naming buttons).

• Layout <layout name> Selected: Boolean. True when the given layout is selected.

• Current Wall/Mosaic Window: Integer. The number of the currently selected window.

• Window <n> Selected: Boolean. True if the given window is selected.

• Window <n> Name: String. Name of the input currently shown on the given window.

• Current Selected Input: String. Name of the currently selected input

• <input name> Selected: Boolean. True if the given input is the one currently selected.

Part 5 - Advanced Features

USP Media Player

The USP system supports a built-in media player that has a simple set of functions: play a playlist from a built-in list of playlists configured on the system and stop playlist playback.

Before you start

The driver queries the available playlists when Query MXnet is run and creates the appropriate functions to match.

User Experience

Functions are provided to allow for three different styles of user experience:

• Each known playlist has a specific button to start playing it on a defined output and there is a stop button to stop playback on that output. This suits a UI where the playlists are hard-coded as named buttons on the page that corresponds to the output on which the playlist is being played. Only the playlists that were known and defined as buttons during the UI design will ever be available.

• A dynamic list shows the currently available playlists and the end user chooses one for playback on a defined output. The list can be refreshed and there is a stop button to stop playback on that output. This again would be hard-coded on the page corresponding to the output.

• A dynamic list and stop button as above, but the output is pre-selected using a “current output” function. This then allows a single user interface to be shared between multiple outputs.

UI Programming – Fixed Buttons

Tag: Media Player: Play: Playlist <name>

These tags can be assigned to buttons to set them up to call Play Playlist for the named playlist and will also auto-name the button with the name of the playlist. The output parameter needs to be set, but if the page has the corresponding RTI Source for the output set as its source then this will be auto-programmed too.

Tag: Media Player: Stop: Output <name>

Pick the appropriate stop output tag to initialize the stop playback button for the output.

UI Programming – Dynamic List for a Fixed Output

Tag: Media Player: List: Fixed Output

Drag this onto a list object and it will initialise it to have a dynamic list of available playlists for a given output. If the RTI Source for the page is one created by the driver to represent an output then this will automatically initialize the output parameter. Selecting a playlist from the list will play it.

Tag: Media Player: List: Refresh

Drag this onto a button to create a button to refresh the list of available playlists.

Tag: Media Player: Stop: Output <name>

Pick the appropriate stop output tag to initialize the stop playback button for the output.

UI Programming – Dynamic List for a Selected Output

Choose the output for which the list will work by calling the Select Playlist Output function. This can only be placed in one of the following:

• A Room Selection Event

• A Source's Activity Start event

• A Source's Activity Ready event

• A button wired directly on the Controller UI (pressed by hand on that panel, not driven by another driver's macro or event).

• If you try to call the function from anywhere else — a global macro, another device's event, a timed event — the driver will not know the controller to associate with and subsequent use of functions and variables may not work as expected. Once this has been done for each output, they can then share the UI, which is configured using the following tags.

Tag: Media Player: List: Selected Output

Drag this onto a list object and it will initialise it to have a dynamic list of available playlists for the selected output.

Tag: Media Player: List: Refresh

Drag this onto a button to create a button to refresh the list of available playlists.

Tag: Media Player: Stop: Selected Output

Pick the appropriate stop output tag to initialize the stop playback button for the selected output.

Functions and variables, in sub-section Media Player Control

• Play Playlist: Output, Playlist name

• Play Playlist: Plays the named playlist on the given output

• Select Playlist: Output, Playlist index

• Select Playlist: For use with lists. Plays the playlist at the given index on the given output

• Refresh Playlists: Refreshes the contents of the list of playlists.

• Stop: Output

• Stop: Stops the playlist playback on the given output

• Select Playlist Output: Output

• Select Playlist Output: Choose an output for “selected” functions to use

• Select Playlist For Selected Output: Playlist index

• Select Playlist For Selected Output: For use with lists. Plays the playlist at the given index on the currently selected output.

• Stop Playlist For Selected Output: Stops playlist playback on the selected output

• Playlist List: List. The list of available playlists

• Playlist <name> Name: String. The name of each playlists, for auto-naming buttons

RS232, IR and CEC Passthrough

These commands are pass-through functions. The driver forwards the supplied string/code to the selected MXnet input(s) and/or output(s) and does not interpret or acknowledge the equipment response.

Port/range syntax

• Single number: 3

• Comma list: 1,2,3,4

• Range: 1-4

• Mixed: 1,2,3-4

Send RS232

• Inputs: Numbers/range; 0 if unused

• Inputs: Target encoder RS232 ports

• Outputs: Numbers/range; 0 if unused

• Outputs: Target decoder RS232 ports

• String: ASCII with supported escapes

• String: The outgoing string

Supported escapes:

• \r - Carriage Return (character code 13)

• \n - Line Feed (10)

• \t - Tab (9)

• \b - Backspace (8)

• \f - Form Feed (12)

• \\ - a literal backslash

• \x.. - send a single raw byte by its two-digit hex code, e.g. \x41 sends byte 0x41

Examples:

• Hello\r\n

• \x48\x65\x6c\x6c\x6f\x0d\x0a (same result as above, sent entirely as hex bytes)

• He\x6c\x6co\r\n (mixing plain text and hex escapes in the same string)

Send IR

• Inputs: Numbers/range; 0 if unused

• Inputs: Target encoder IR ports

• Outputs: Numbers/range; 0 if unused

• Outputs: Target decoder IR ports

• String: Format accepted by MXnet blaster

• String: The exact format of the string will be defined by the IR blaster connected to the MXnet unit

CEC

Functions and variables, in sub-section Media Player Control

• Send CEC Output (Power): Output, Power On/Off

• Send CEC Output (Power): Send a CEC power command to a single output

• Send Multiple CEC (Power): Output range, Power On/Off

• Send Multiple CEC (Power): Send a CEC power command to multiple outputs

• Send CEC (Hex): Output range, Hex command

• Send CEC (Hex): Raw CEC hex, e.g. 0036

• Send CEC Output (Power): Output + Power On/Off

• Send CEC Output (Power): Single named output; MV41v2 outputs are not offered in the dropdown.

• Send Multiple CEC (Power): Outputs ranges + Power On/Off

• Send Multiple CEC (Power): Same command to multiple outputs.

• Send CEC (Hex): Outputs ranges + hex command

• Send CEC (Hex): Raw CEC hex, e.g. source placeholder 0036.

Take care when any of Send IR, Send RS232 or the CEC functions above are wired to a button with Sustain enabled, i.e. the command keeps re-sending while the button is held down, as on an Apex-style panel.

Each press of one of these functions can already fire off more than one command in sequence - one per input and one per output resolved from your Inputs/Outputs range. If Sustain then re-sends that same batch on every repeat tick, a low Sustain interval combined with a wide port range can queue commands onto the controller faster than it can process them, which can overload the system and crash the controller.

Set the Sustain value according to the number of inputs/outputs being controlled. More ports generally require a longer Sustain time.

Live Image Streams and Snapshots

MXnet supports both full-motion Video Image Streams and periodically refreshed Snapshot Image Streams. This task covers both streaming methods, snapshot settings, and the Image Stream Selector, which can assign any input or output to one of four configurable live-view slots.

Video Image Stream vs Snapshot Image Stream

Every configured input and output has two possible live-picture variables: a Video Image Stream and a Snapshot Image Stream (subject to range availability, below). Both are "Image" type variables whose value is a stream URL — you don't need to read the URL yourself, you simply point the right RTI object at the variable and RTI does the rest. Your choice of which to use will be based on availability on the system you are configuring and the load imposed; streams impose much more load than a periodic snapshot. Availability is as follows:

• MXnet 1G — Video Image Stream and Snapshot Image Stream both available, plus the quality/refresh-cycle settings below and the Image Stream Selector.

• MXnet 10G — None Supported.

• MXnet USP — Video Image Stream and the Image Stream Selector are available. No Snapshot Image Stream

Video Image Stream is a real-time MJPEG feed. Wire it to an RTI Generic MJPEG Viewer object. A live MJPEG feed uses meaningful processing power and bandwidth per stream, so keep no more than around four Video Image Streams live at any one time (on one page, or across pages that could realistically be open together).

Snapshot Image Stream is a still picture that updates on a rolling cycle rather than streaming continuously — effectively a JPEG grabbed from the source and refreshed periodically. Wire it to an RTI Dynamic Image object. Because it's an occasional image swap rather than a live stream, there is no practical limit on how many Snapshot Image Streams you can put on screen at once.

A compromise is available on 1G and USP systems called the Image Stream Selector. This allows a dynamic choice of up to four inputs or outputs to have their live video routed to a “slot” and then these four slots can then each be linked to a Generic MJPEG viewer.

Wiring a Single Input's or Output's Live Picture

Tag: Image Stream: Input Snapshot: <input name>

Drag this onto a Dynamic Image Object to get a snapshot image stream for the input.

Tag: Image Stream: Input Video: <input name>

Drag this onto a Generic MPEG Viewer to get a video image stream for the input.

Tag: Image Stream: Output Snapshot: <input name>

Drag this onto a Dynamic Image Object to get a snapshot image stream for the output.

Tag: Image Stream: Output Video: <input name>

Drag this onto a Generic MPEG Viewer to get a video image stream for the output.

Variables in the Image Streams section

• <input name> Snapshot Image Stream: String. Contains the URL of the snapshot image stream for the input

• <input name> Video Image Stream: String. Contains the URL of the video image stream for the input

• <output name> Snapshot Image Stream: String. Contains the URL of the snapshot image stream for the output

• <output name> Video Image Stream: String. Contains the URL of the video image stream for the output

Image Stream Settings: Quality and the Snapshot Refresh Cycle

These are in the driver’s Config Settings under the category Image Stream Settings. They are only present on ranges that support them — currently just the MXnet 1G range.

Snapshot Refresh Cycle sets how long it takes to cycle through and refresh every Snapshot Image Stream on the system once — it divides that one total cycle time across all your encoder/decoder snapshots. For example, with the cycle set to 30 seconds and 15 encoders/decoders on the system, each individual snapshot updates roughly once every 2 seconds, with a full pass through all of them completing every 30 seconds.

A 1-second floor is enforced, so no single snapshot can refresh faster than once per second no matter how low you set this value. If you have a lot of snapshots on screen and want to reduce system load, increase this setting.

Video Stream Quality sets the quality and frame rate of the Video Image Stream. Choices are: Low, Medium or High.

Snapshot Quality sets the quality of the Snapshot Image Stream. Choices are: Low, Medium or High.

Snapshot Refresh Cycle is the time in seconds to cycle through and update every Snapshot Image Stream once, as described above.

Image Stream Selector

The Image Stream Selector, in the Image Stream Controller category, lets you route any configured input or output into one of four numbered live-feed slots on demand, instead of wiring every possible source to its own fixed object. It is available on the 1G and USP ranges; it is not present on 10G, where you should use the direct per-input/output Video Image Stream variables above instead.

Tag: None

The Image Stream Selector function has no tag. Add it to buttons of your choice, specifying input or output feed to select and the slot 1-4 to send it to. One possible UI layout for this could be a matrix of buttons with inputs and outputs listed vertically and slot number horizontally.

Tag: Image Stream: Dynamic Video: Stream <slot>

Drag this onto an MJPEG viewer to have it display the feed from slot <slot>.

Functions and variables, in sub-section Image Streams

• Image Stream Selector: Image Stream Slot, Source

• Image Stream Selector: Routes the source (input or output video) to the given slot.

• Dynamic Video Image Stream <n>: URL. The URL of dynamic video feed slot <n>

Device Maintenance and Output Controls

These are miscellaneous functions for performing various maintenance and configuration operations. Some have tags for simplifying programming:

Tag: Configuration: Device: Reboot All

Assigns Reboot All Devices to a button.

Tag: Configuration: OSD: All on

Assigns Set All Outputs OSD (On) to a button.

Tag: Configuration: OSD: All off

Assigns Set All Outputs OSD (Off) to a button.

Tag: Configuration: Set Receiver: Display Image <n>

1G only. Assigns Set Receiver Display Image for the given index to the button. If the RTI Source for the page is set to one of the Output sources for the driver, that will be automatically chosen as the output.

Tag: Configuration: Set Receiver: IP Video Stream

1G only. Reverts to the source video feed after having shown a stored image on the display.

Tag: Configuration: Set Receiver: ExAudioType <type>

USP only. Sets the extracted audio type for an output. If the RTI Source for the page is set to one of the Output sources for the driver, that will be automatically chosen as the output.

Tag: Configuration: Set Receiver: HDMI Type <type>

USP only. Sets the HDMI audio type for an output. If the RTI Source for the page is set to one of the Output sources for the driver, that will be automatically chosen as the output.

Functions in sub-section Configuration

• Set Device Lights: State, Inputs, Outputs

• Set Device Lights: Sets the indicator lights on the given input and output devices to normal (On), darkened (Off) or flashing (Flash) for identification. Inputs and Outputs are the usual range specifications. Always specify 0 for Inputs or Outputs if not used, otherwise an invalid command will be sent.

• Reboot Devices: Inputs, Outputs

• Reboot Devices: Reboots the specified devices. Inputs and Outputs are the usual range specifications. Always specify 0 for Inputs or Outputs if not used, otherwise an invalid command will be sent.

• Reboot All Devices: Reboots all the devices.

• Set Output OSD: State, Outputs

• Set Output OSD: 1G only. State is On/Off to switch the on-screen display on or off. Outputs is a range specification of outputs.

• Set All Outputs OSD: State

• Set All Outputs OSD: 1G only. Sets the on-screen display On or Off for all outputs.

• Set Receiver Display Image: Output, Image

• Set Receiver Display Image: 1G only. Assigns a stored image to be shown on the given receiver, or reverts to the source video feed.

• Input HotPlug Reset: Input

• Input HotPlug Reset: Resets hot plug detection on an input. If a source isn't being detected properly by an encoder, or a display isn't receiving picture from a decoder, resetting the hot-plug signal is the standard first fix — it forces the port to re-run its HDMI hot-plug/EDID handshake

• Output HotPlug Reset: Output

• Output HotPlug Reset: Resets hot plug detection on an output.

• Set ExAudioType: Output, Type

• Set ExAudioType: USP only. Sets the extracted audio type on an output, one of TX’s Audio, Dante Audio, ARC Audio or Loop Out Audio.

• Set HDMI Audio Out Type: Output, Type

• Set HDMI Audio Out Type: USP only. Sets the HDMI Audio Output type to TX or Dante.

• Generic API Command: Command

• Generic API Command: Sends a raw API command to the MXnet system

• <input> Hot Plug Detected: Boolean. True if a device has been detected connected to the input.

• <output> Hot Plug Detected: Boolean. True if a device has been detected connected to the output.

USP External Devices

This feature is available only when the driver is connected to an MXnet USP unit. It lets you register a third-party, IP-controllable device with the matrix — for example a device with a network address the matrix firmware needs to know about — and, separately, set login credentials the matrix should use when talking to it. The three functions below (Add External Device, External Device Security, Remove External Device) work together: you add the device first, optionally secure it, and can remove it later. There is no on-screen confirmation or feedback variable for any of these actions in the driver — see the gap notes below before relying on this in the field.

Add External Device

Use to register an external device with the USP controller.

• ID: String

• ID: Unique external device identifier; check the MXnet documentation for the requirements for the specific device.

• Model Name: String

• Model Name: Device model name.

• URL: String

• URL: Device address, for example rtsp://192.168.1.10/11

• Network: AV or Control

• Network: The MXnet control box has two network ports for the AV Network or Control Network. Specify which is used to communicate with the device.

External Device Security

Use to set or update the login credentials the matrix uses for a previously added external device. It uses the same ID you used when adding the device, so make sure it matches exactly.

• ID: String

• ID: Select registered device.

• Enable Security: Enable / Disable

• Enable Security: Turn credential-based security on/off.

• Username: String

• Username: Login username.

• Password: String

• Password: Login password.

Remove External Device

Use to remove a previously added device.

• ID: String

• ID: Select registered device.

Part 6 - Troubleshooting and Support

Troubleshooting

Symptom: nothing in the driver works

If none of the driver's functions or feedback work at all - not just one switch or one preset - the fault is almost always in the network path between the RTI processor and the MXnet system, or in the IP address configured in the driver, rather than in any per-input or per-output setup.

• Confirm the MXnet network switch/uplink reaches the same control network as the RTI processor.

• Confirm the driver IP Address is the MXnet control-interface IP, not another device address.

• Monitor CBOX - Connection Status (Boolean). False indicates the driver cannot reach the configured IP.

• Monitor CBOX - Online Status (String). The source guide says a healthy system reports All Devices Online. If Connection Status is true but the Online Status indicates a problem, check individual MXnet devices for power/network issues.

Symptom: switching/preset/multi-view commands fail but connection is healthy

If the connection looks healthy (per the checks above) but a switching, preset or multi-view button doesn't do what you expect, the most common cause is a device alias in Mentor that doesn't match the naming pattern the driver relies on to identify inputs and outputs.

The driver expects each device's alias to start with "IN" or "OUT" followed by its port number, optionally followed by a dash and a friendly name - for example "IN1-Laptop" or "OUT3-Bedroom". Any alias that doesn't match this pattern is skipped when the driver reads the device list from the switch, which is why a device can be present in Mentor but missing from the driver's inputs/outputs.

• Check every device alias follows IN# or OUT#, optionally followed by -Friendly Name.

• Run Query MXnet to re-read device names, walls and mosaics.

• If Integration Designer warns about invalid aliases, run Auto-Configure Aliases or correct them in Mentor.

• If names were edited in the driver, run Apply Changes.

• Check <Output Name> Current Input (Name) after a test route. If it does not update, re-check alias recognition and discovery.

Symptom: driver configuration actions time out

Remember that Query MXnet, Apply Changes, Auto-Configure Aliases and Clear All Aliases connect from the Integration Designer PC directly to the MXnet IP. Check the PC network path as well as the RTI processor path.

Symptom: Multi-View controls are missing

• 1G: verify the MV41v2 exists and is correctly aliased, then run Query MXnet.

• 10G/USP: verify the output is listed in Outputs Configured As Multi-View.

Symptom: wall/mosaic controls are missing

• Verify the wall/mosaic and required layouts exist in Mentor.

• Run Query MXnet after any wall/mosaic create, remove or rename operation.

Symptom: USP playlist is missing

• Verify the playlist exists on the USP device.

• Run Query MXnet again to refresh the playlist list.

• Reconfigure buttons that referenced a playlist name that has since changed.

Advanced Diagnostics

Use driver debug logging when the normal checks above do not explain the problem or when support requests detailed traces.

• Debug Enable: Off / Boolean

• Debug Enable: Enable detailed driver debug output.

• Debug Subsystems: *

• Debug Subsystems: Limit logging to selected driver subsystem(s); * means all.

Debug is sent to RTI’s TraceViewer tool. All debug lines are prefixed MXnet_Universal followed by the relevant subsystem tag. Support may also request you to use the Support: Dump XML command on the driver. This will write out copies of all the configuration XML files that define the driver’s current configuration. These will be written to a folder called xml-logs that will be created under whichever folder the driver was installed from.

Part 7 - Reference

Appendix A - Driver Actions and Function Quick Reference

• Commissioning: Query MXnet

• Commissioning: Discover model, devices and dynamic configuration.

• Commissioning: Auto-Configure Aliases

• Commissioning: Assign valid IN#/OUT# aliases while preserving valid existing aliases.

• Commissioning: Clear All Aliases

• Commissioning: Reset custom aliases to defaults.

• Commissioning: Apply Changes

• Commissioning: Apply configuration edits.

• Output Routing: Switch Output (AV)

• Output Routing: Route combined video/audio to an output.

• Output Routing: Switch Output (Breakaway)

• Output Routing: Route one path: Video, Audio, USB or supported analog audio.

• Multi-Switch: Select Output

• Multi-Switch: Switch immediately or toggle output selection according to mode.

• Multi-Switch: Select Input

• Multi-Switch: Select input or switch selected outputs according to mode.

• Multi-Switch: Select Switching Type

• Multi-Switch: Choose Video/Audio/USB/Combined/10G analog option.

• Multi-Switch: Select All Outputs

• Multi-Switch: Select every output where available.

• Multi-Switch: Clear All Outputs

• Multi-Switch: Clear output selections where available.

• Multi-Switch: Apply Selection

• Multi-Switch: Commit pending synchronized route.

• Switching Presets: Toggle Output

• Switching Presets: Add/remove output from preset operation.

• Switching Presets: Save Preset (Selected Outputs)

• Switching Presets: Save current routing for selected outputs.

• Switching Presets: Recall Preset

• Switching Presets: Restore a stored routing preset.

• Volume: Volume Step

• Volume: Increment/decrement output or extracted-input volume in the relevant category.

• Volume: Set Volume

• Volume: Set exact output or extracted-input level.

• Volume: Set Mute

• Volume: Mute/unmute/toggle output.

• Multi-View: Select Multi-View Output / Device

• Multi-View: Set current Multi-View target.

• Multi-View: Activate Layout

• Multi-View: Recall Multi-View layout.

• Multi-View: Select Window

• Multi-View: Select window 1-4.

• Multi-View: Select Audio Window

• Multi-View: Select audio window, 10G/USP.

• Multi-View: Switch Input To Selected Window

• Multi-View: Assign input to selected window.

• Multi-View: Save Preset / Recall Preset

• Multi-View: Store/restore layout and source assignments.

• Multi-View: Recall Preset For Multi-View Output / Device

• Multi-View: Explicit-target recall for macros/scenes.

• Multi-View: Select Input For Multi-View Output / Device Window

• Multi-View: One-shot target/layout/input/window assignment.

• Video Wall/Mosaic: Select Video Wall / Select Mosaic

• Video Wall/Mosaic: Set wall/mosaic target for current controller.

• Video Wall/Mosaic: Activate Layout / Activate Mosaic

• Video Wall/Mosaic: Recall Mentor-defined design.

• Video Wall/Mosaic: Select Window

• Video Wall/Mosaic: Select target window.

• Video Wall/Mosaic: Switch Input To Selected Window

• Video Wall/Mosaic: Assign input to selected window.

• Video Wall/Mosaic: Select Input For Window

• Video Wall/Mosaic: One-shot macro assignment.

• Video Wall/Mosaic: Save Preset / Recall Preset

• Video Wall/Mosaic: Store/restore wall layout and assignments.

• Media Player: Play Playlist

• Media Player: Play discovered USP playlist on output.

• Media Player: Stop

• Media Player: Stop playback and restore prior route per source guide.

• Media Player: Refresh Playlists

• Media Player: Refresh browse-list data.

• Media Player: Select Playlist Output

• Media Player: Set controller playlist target output.

• Media Player: Select Playlist

• Media Player: Select by output + index.

• Media Player: Select Playlist For Selected Output

• Media Player: Apply indexed playlist to current output.

• Media Player: Stop Playlist For Selected Output

• Media Player: Stop current selected output playlist.

• Passthrough: Send RS232

• Passthrough: Forward RS232 string.

• Passthrough: Send IR

• Passthrough: Forward IR code.

• Passthrough: Send CEC Output (Power)

• Passthrough: Single-output CEC power.

• Passthrough: Send Multiple CEC (Power)

• Passthrough: Multi-output CEC power.

• Passthrough: Send CEC (Hex)

• Passthrough: Raw CEC hex.

• Image Streams: Image Stream Selector

• Image Streams: Assign source to dynamic stream 1-4.

• Configuration: Set Device Lights

• Configuration: On/Off/Flash selected devices.

• Configuration: Reboot Devices / Reboot All Devices

• Configuration: Restart selected/all devices.

• Configuration: Set Output OSD / Set All Outputs OSD

• Configuration: 1G OSD control.

• Configuration: Set Receiver Display Image

• Configuration: 1G stored-image/live-video choice.

• Configuration: Input HotPlug Reset / Output HotPlug Reset

• Configuration: Force HDMI hot-plug/EDID handshake.

• Configuration: Set ExAudioType

• Configuration: USP external-audio source.

• Configuration: Set HDMI Audio Out Type

• Configuration: USP HDMI audio source.

• Configuration: Generic API Command

• Configuration: One-way raw MXnet command.

• USP External Devices: Add External Device

• USP External Devices: Register external device.

• USP External Devices: External Device Security

• USP External Devices: Set credentials/security.

• USP External Devices: Remove External Device

• USP External Devices: Deregister external device.

Appendix B - Variable Reference

• Connection Status: CBOX - Connection Status

• Connection Status: Boolean

• Connection Status: CBOX connection status.

• Connection Status: CBOX - Online Status

• Connection Status: String

• Connection Status: CBOX online status; source example Online.

• Connection Status: MV41v2 - [x] Status

• Connection Status: Boolean

• Connection Status: MV41v2 status.

• Naming: Output [x] Name

• Naming: String

• Naming: Output display name.

• Naming: Output [x] Current Input (name)

• Naming: String

• Naming: Current source name on output; source example Roku.

• Naming: Input [x] Name

• Naming: String

• Naming: Input display name.

• Audio: Input [x] Volume

• Audio: Integer 0-100

• Audio: Extracted input audio volume.

• Audio: Output [x] Volume

• Audio: Integer 0-100

• Audio: Output volume.

• Audio: Output [x] Muted

• Audio: Boolean

• Audio: Output mute state.

• Image Streams: Input [x] Video Image Stream

• Image Streams: Image

• Image Streams: Input video stream URL.

• Image Streams: Input [x] Snapshot Image Stream

• Image Streams: Image

• Image Streams: Input snapshot URL.

• Image Streams: Output [x] Video Image Stream

• Image Streams: Image

• Image Streams: Output video stream URL.

• Image Streams: Output [x] Snapshot Image Stream

• Image Streams: Image

• Image Streams: Output snapshot URL.

• Image Streams: Dynamic Video Image Stream [x]

• Image Streams: Image

• Image Streams: Dynamic stream URL.

• Multi-Switch: Current Selected Input

• Multi-Switch: Integer

• Multi-Switch: Current selected input.

• Multi-Switch: Input [x] Selected

• Multi-Switch: Boolean

• Multi-Switch: Input selected state.

• Multi-Switch: Output [x] Selected

• Multi-Switch: Boolean

• Multi-Switch: Output selected state.

• Multi-Switch: Selected Switching Type

• Multi-Switch: String

• Multi-Switch: Current switching type; source example video.

• Multi-Switch: Selected Switching Type [Video|Audio|USB|Combined|Analog] Name

• Multi-Switch: String

• Multi-Switch: Switching type display names.

• Multi-Switch: Selected Switching [Video|Audio|USB|Combined|Analog]

• Multi-Switch: Boolean

• Multi-Switch: Switching type selected state.

• Switching Presets: Output [x] Selected

• Switching Presets: Boolean

• Switching Presets: Output selected for preset saving.

• Hot Plug: Output [x] Hot Plug Detected

• Hot Plug: Boolean

• Hot Plug: Decoder hot-plug detect.

• Hot Plug: Input [x] Hot Plug Detected

• Hot Plug: Boolean

• Hot Plug: Encoder hot-plug detect.

• Multi-View: Current Multi-View

• Multi-View: String

• Multi-View: Current selected Multi-View identifier.

• Multi-View: Current Multi-View Name

• Multi-View: String

• Multi-View: Current selected Multi-View name.

• Multi-View: Current Selected Layout

• Multi-View: String

• Multi-View: Selected layout.

• Multi-View: [Layout] Selected

• Multi-View: Boolean

• Multi-View: Layout selected state.

• Multi-View: Current Multi-View Window

• Multi-View: Integer

• Multi-View: Selected window.

• Multi-View: Audio Window Selected

• Multi-View: Boolean

• Multi-View: Audio-window selection state.

• Multi-View: Audio Current Input Name

• Multi-View: String

• Multi-View: Audio-window source name.

• Multi-View: Window [x] Selected

• Multi-View: Boolean

• Multi-View: Window selection state.

• Multi-View: Window [x] Current Input Name

• Multi-View: String

• Multi-View: Input name assigned to window.

• Multi-View: Fullscreen Selected

• Multi-View: Boolean

• Multi-View: Fullscreen selected.

• Multi-View: PIP Bottom Left Selected

• Multi-View: Boolean