AVProEdge MXNet

RTI Driver User Guide

Introduction

AVProEdge MXNet is a driver by Janus Technology for configuring and controlling the MXNet AVoIP system from AVProEdge

MXNet provides scalable AVoIP distribution from small to very large (hundreds of source and displays) systems, whilst also providing a rich feature set including video wall functionality.

Although the MXNet system comes with a Web Interface on its controller, it is not required to use this. Instead it is possible to fully configure the system from an RTI panel using the supplied test harness.

Configuration

The MXNet controller must be configured with a static IP address in the same range as the RTI processor in order for the two to communicate.

In order to map between the physical MXNet devices, and virtual port numbers it is necessary to assign Alias names to the devices. By conventions these will be 'IN1', 'OUT1' etc, designation Input / Output device and port number.

Out of the box, the MXNet devices will not have these Alias names configured, so it is necessary to configured these as a first step.

The following Functions are provided in the driver to assist in configuration of the matrix, and made accessible from the supplied test panel:

Clear All Aliases - resets configuration names to factory default. Note use with caution.

Auto-Configure Aliases - automatically configures aliases. If any devices already have valid alias names configured, then these will remain unaltered. All other devices will be assigned alias names in ascending sequence, filling in any gaps in the numbering sequence.

Rediscover Devices - forces rediscovery of devices

Set Device Light - sets state of LED indicators on specified devices

- On - normal operation, lights on

- Flash - lights flashing - useful for identifying physical device

- Off - lights off, useful in situations where the light may be visible in a darkened room

Reboot Device - reboots specified input and output devices

Reboot All Devices - reboots all devices

OSD Command - switches OSD on/off on selected receivers

OSD All Outputs Command - switches OSD on/off on all receivers

Driver Installation & Configuration

Open your RTI Integration Designer system file or demo programming file.

The driver features a number of configuration properties that must first be completed. Note that the Serial Port Settings Types provide a way of defining the settings for a serial port, which can then be applied to the serial ports of multiple inputs and outputs.

Connection

• Connection Type - this option defaults to "Network (TCP)".

• IP Address - The IP address on the LAN for the Controller Interface.

Switch Size

• Number of Inputs - the number of transmitters in the system.

• Number of Outputs - the number of receivers in the system.

•

Multiswitch Mode:

• Select Outputs, then Input - selects the order of switching to be outputs first

• Select Input, then Outputs - selects the order of switching to be input first

Input/Output Names

• Allows for custom naming of inputs and outputs. Changing the names here will modify them in the Driver Commands too.

Serial Port Settings type x

• Baud Rate - the baud rate in bits per second.

• Bits - the number of data bits.

• Parity - the parity bit setting.

• Stop Bits - the number of stop bits.

• Inputs - the inputs to which this setting type is to be applied, specified as a comma-separated ranged list eg 1,2, 3-6 (note, if none are required, enter “none” – do not just leave the field empty)

• Outputs - the outputs to which this setting type is to be applied – configured as per inputs

Driver Commands

The driver features a number of commands used for control:

Switch Output (AV) - Switch a specific input to a specific output (combined AV switching).

Switch Output (Breakaway) - Switch a specific input to a specific output (serparate switching for Video/Audio/USB).

Clear Output Selection - When multi switching outputs, or creating presets, this command clears all currently selected outputs.

Select All Outputs - When multi switching outputs, or creating presets, this command is used to select all outputs.

Select Output - This command is used to select individual outputs for subsequent multi switching, or creating presets.

Toggle Output
- This command is used to select or de-select individual outputs for subsequent multi switching, or creating presets.

Select Input (AV)
- This command is used to select an input to which previously selected outputs should be switched (combined AV switching).

Store Preset (All Outputs)
- Store the current configuration of all outputs as a preset (with an ID of 1-16).

Store Preset (Selected Outputs)
- Store the current configuration of all currently selected outputs as a preset (with an ID of 1-16).

Recall Preset Selection
- Recall a preset by ID.

Volume Step - Output volume step up/down by 1.

Set Volume - Set output volume to a specified level.

Set Mute - Mute or unmute an output

Set Input Volume - Set extracted input volume to a specified level.

RS232 Output
~~Inputs - the inputs to which the string is to be sent. These can be comma separated (e.g. "1,2,3,4") or defined as a range (e.g. "1-4"), or a combination of the two (e.g. "1,2-4") if no inputs are being used set the value to 0.
~~Outputs - the outputs to which the string is to be sent. These can be comma separated (e.g. "1,2,3,4") or defined as a range (e.g. "1-4"), or a combination of the two (e.g. "1,2-4") if no Outputs are being used set the value to 0.
~~String - the serial string to be sent. The String field takes printable ASCII characters.
~~~~If you wish to send Binary data, then these characters must be sent as the following supported escape sequences:
~~~~~~\r carriage return (13)
~~~~~~\n line feed (10)
~~~~~~\t tab (9)
~~~~~~\b bell (7)
~~~~~~\f form feed (12)
~~~~~~\\ send the '' character
~~~~~~\x.. send the character specified by the following 2 hex characters
There is no space after any escape characters, and it's permitted to freely mix printable ASCII and escaped characters. For example, the following strings send the exact same sequence out of the RS232 port:
~~Hello\r\n
~~\x48\x65\x6c\x6c\x6f\x0d\x0a
~~He\x6c\x6co\r\n

IR Output
~~Inputs - the inputs to which the string is to be sent. These can be comma separated (e.g. "1,2,3,4") or defined as a range (e.g. "1-4"), or a combination of the two (e.g. "1,2-4") if no inputs are being used set the value to 0.
~~Outputs - the outputs to which the string is to be sent. These can be comma separated (e.g. "1,2,3,4") or defined as a range (e.g. "1-4"), or a combination of the two (e.g. "1,2-4") if no Outputs are being used set the value to 0.
~~Code – the Code sent must be an IR code in either Pronto or Global Cache Format

Video Wall Create

• Define a video wall.

• Wall Name - Choose a wall name (this is important as other commands refer to this name).

• Input - The input to show on the wall.

• Size - The video wall screen configuration selection from the following options 2x2, x2 (top-row inverted), 3x3

• Outputs - The output numbers used to create the video wall. This field must contain a number of outputs equal to the amount defined in the Size field.

Video Wall Switching

• Switch a video wall to show a new input.

• Wall Name - The wall to switch.

• Input - The new input to shown on the wall.

Video Wall Mosaic Layout Active

• Recalls a mosaic layout.

• Wall Name - The wall to update.

• Layout - The layout to recall

Bezel Gap

• Define the size of the TV frame (video edge) to correct for large bezel screens in video wall mode.

• Wall Name - The wall to configure.

• Overall Width, Height – the overall size of the television in mm (e.g. “600,550”).

• Screen Image Width, Height – the size of the actual screen in mm (e.g. “550,500”).

Set Transmitter EDID
- Configure the encoder (input) EDID setting.

Set Transmitter Audio Source
- Configure the encoder (input) audio source.

Set Receiver Resolution
- Configure the decoder (output) resolution.

CEC

• Send a CEC command to specified outputs.

• Outputs – the output number(s) to which the command should be sent. These can be comma separated (e.g. “1,2,3,4”) or defined as a range (e.g. “1-4”), or a combination of the two (e.g. “1,2-4”).

• Control – choose a CEC command to send.

Output xxx Hotplug reset
- Resets Hotplug on Output xxx

Input xxx Hotplug reset
- Resets Hotplug on Input xxx

IMPORTANT NOTE
There is a bug in existing Integration Designer that means that empty command parameters are not passed - they are simply ignored and all non-empty parameters are shuffled up. This leads to incorrect parameter being assigned in the driver.
The workaround is to ensure that all parameters contain non-empty values.
This is particularly important for RS232 Output command, where you may wish to send commands to inputs, or outputs, but not both. In this case set the input / output fields you don't wish to use to 0 or “none” (rather than leaving blank). This is an invalid port and is silently ignored by the driver.

Driver Variables

The driver features a number of variables, providing feedback from the MXNet system.

Operational Mode - Reports the current connection status.

Model Number - Reports the model number of the MXNet IP controller.

OUTxxx Current Input (integer) - Reports the number of the input currently routed to the given output.

OUTxxx Current Input (name) - Reports the name of the input currently routed to the given output.

INxxx Name - The name defined for a particular input in the MXNet system.

OUTxxx Name - The name defined for a particular output in the MXNet system.

Output xx Selected - A Boolean variable reporting the selection status of the given output.

Output xxx Hotplug Detected - A Boolean variable reporting the current Hotplug status of output xxx

Input xxx Hotplug Detected - A Boolean variable reporting the current Hotplug status of input xxx

Driver Events

The driver features a number of Events, Used for Programming

Output x Hotplug Connected - Event fires when Output x hotplug is connected

Output x Hotplug Disconnected - Event Fires when Output x hotplug is Disconnected

Input x Hotplug Connected - Event fires when Input x hotplug is connected.

Input x Hotplug Disconnected - Event Fires when Output x hotplug is Disconnected.

Test Harness

Included with the driver package is an RTI Integration Designer file, containing a demonstration Virtual Panel design, the intention of which is to exercise the functionality of the driver, in order to aid integration with your project.

Choose to display the Test Harness design in Integration Designer and select Communications, then Export to Virtual Panel File. You may now save and run the Virtual Panel in the usual way.

Troubleshooting

The driver cannot control the MXNet system

Confirm the Ethernet switch used by the MXNet system is correctly uplinked to the same network as the RTI processor.

Confirm that the correct IP address is defined in the RTI driver properties for the MXNet control interface.

Switching commands are failing

Ensure that the device alias names are configured correctly – the configuration Status variable gives useful information. Read the section of this guide entitled "Configuration" for more information.