AVPro Edge MXnet Dante CBOX | IP Control | Version 1.10

Introduction

This driver has been designed to provide two-way control of the MXnet Dante CBOX, via Ethernet.

Version History

Version 1.10 – 21 August 2026

• Added multi-switching commands

• Demo UI and documentation updated to latest standards

• Note – with FW 25.1.27, setting input Off may sometimes fail

• Note – with ID 11.2, Multi-Switch: Output: <name> tags can incorrectly assign the Boolean variable instead of the String variable as the button name; this needs to be corrected manually.

Version 1.0 – 20 May 2025

• Initial release

Driver Features

• Dante switching

• Multi-switching UI, including presets

System Requirements & Prerequisites

RTI System Requirements

• Integration Designer: 11.2 or later.

• XP FW: 25.1.27 or later.

Supported models

• AC-MXNET-DANTE-CBOX

Driver Configuration

System Configuration

• IP Address: Enter the device’s IP address.

• Number of Inputs: The maximum Dante input channel number to be managed by this driver

• Number of Outputs: The maximum Dante output channel number to be managed by this driver

• Number of Presets: How many presets the driver should be capable of storing

• Multi-Switch Mode: How the multi-switch UI should work

• In to Out (Instant): An input is selected and then each time an output is selected, the output is instantly switched to the currently chosen input. Output selection state reflects whether the input is currently chosen on that output.

• In to Out (Synchronized): An input is selected and then multiple outputs are selected. When all desired outputs have been selected, an Apply button is pressed and they are all changed to that input at the same time.

• Out to In: One or more outputs are selected and then an input is selected. All the selected outputs are switched to the input when the input is selected.

• Preset Mode: How the preset UI should work

• Use Buttons To Choose Outputs: The preset UI will have a button per output. The user chooses one or more of these and then presses Save Preset <n>. The state of the chosen outputs will be saved and only those outputs will be restored when Recall Preset <n> is selected.

• Save All Outputs: Only the save and recall buttons will be shown and pressing the save button will save the state of all outputs and recall will recall the state of all outputs. A simpler interface for when the complexity of saving the state of subsets of outputs is not required.

• Input Names: Used to assign friendly names to the inputs. These will be used in tags, function parameter drop-downs and variable names. Use Apply Name Changes once all are defined.

• Output Names: Used to assign friendly names to the outputs. These will be used in tags, function parameter drop-downs and variable names. Use Apply Name Changes once all are defined.

• Debug Enable: Enable debug tracing. Use under instruction from technical support.

• Debug Subsystems: Filter the debug output. Use under instruction from technical support.

Configuration Actions

• Apply Name Changes: Run this action once Input and Output names have all been set up. This causes the driver to generate matching tags, functions and variables.

• Support: Dump XML: This saves a copy of the driver’s current configuration files in a folder called xml-logs underneath the folder from which the driver was originally installed. If you raise a support issue, you may be requested to run this and send back the files.

Large Matrix Handling

This driver is designed to cope with systems that have large and possibly sparse switching matrixes. There are two important strategies to be aware of.

Input and output naming

When the maximum input and output numbers have been set, the driver will create the corresponding number of Input and Output Name configuration fields. By default these will be blank and the installer should assign names to all the input and outputs channels that are in use. To reduce the clutter of tags, functions and variables, the driver only generates them for those inputs and outputs that have names assigned.

Note: You must run Apply Name Changes whenever the input or output names are changed, otherwise the correct programming tags, functions and variables will not be available.

Feedback variables

For smaller switches, there will be individual Boolean variables to show the switching state, e.g. Output 1 – Input 3 Selected. These are generally used to control the highlighting of switch selection buttons. However the number of these variables required increases dramatically as the size of the switch increases as it corresponds to the number of inputs times the number of outputs. Past a certain point, this could overload the processor. For this reason, if the number of variables exceeds 256 (i.e. a 16x16 switch) then these variables and their corresponding Selected events will not be generated. This means that although individual switch selection is still possible in larger switches and the Current Input variables are available to give feedback of the current selection, button highlighting will not be possible.

Driver Commands

Switching Commands

Switch Output

Selects an input for a given output.

Parameters:

• Input – Any of the Dante inputs in the system.

• Output – The output to which to connect the input.

Multi-Switch

These functions are provided to allow the creation of user interfaces that can select multiple outputs to be switched to a given input at the same time. The user interface can operate in one of three ways as described above under the Multi-Switch Mode setting. Which of these functions are made available depends on which mode has been selected.

• Multi-Switch \ Select Input – Selects an input for use as the source for a multi-switch.

• Multi-Switch \ Select Output – Selects or deselects an output for inclusion in a multi-switch.

• Multi-Switch \ Switch Output To Selected Input – Immediately switches an output to the currently selected input.

• Multi-Switch \ Switch Selected Outputs To Input – Switches the currently selected outputs to a chosen input.

• Multi-Switch \ Clear All Outputs – Deselects all currently selected multi-switch outputs.

• Multi-Switch \ Apply Selection – Switch all currently selected outputs to the selected input.

Presets

These functions are provided to save and restore the switching state of the device(s). The user interface can operate in one of two ways as described above, under the Preset Mode setting. Which of these functions are made available depends on which mode has been selected.

• Presets \ Toggle Output – Selects or deselects an output for inclusion in a preset.

• Presets \ Clear All Outputs – Deselects all currently selected outputs.

• Presets \ Select All Outputs – Selects all outputs.

• Presets \ Save Preset – Saves the switching state of all selected (or all) outputs as a preset.

• Presets \ Recall Preset – Recalls the switching state stored in the preset.

Configuration Commands

Generic API Command

Send a command string directly to the device using its API. This can be used to send specific control commands to the device in the case where the driver provides no other corresponding function.

Parameters:

• Command – The API command to send, e.g. SET IN2 EDID 0

Driver Variables

Status

Connection Status (Boolean)

Indicates whether the unit is currently connected.

Operational Mode (String)

Reports the current operational/connection mode of the unit.

Dante Connection Status (Boolean)

Indicates whether the Dante network is connected.

Dante Operational Mode (String)

Reports the current operational/connection mode of the Dante network.

Routing

Names come from the friendly names given in the configuration.

<Output name> Current Input (integer) (Integer)

The number of the input currently selected on the given output.

<Output name> Current Input (name) (String)

The name of the input currently selected on the given output.

<Output name> - <Input name> Selected (Boolean)

True if the given input is currently selected on the given output. Note: these variables are only available if there are 256 or fewer possible output – input combinations.

Multi-Switch (for current remote)

Names come from the friendly names given in the configuration.

Current Selected Input (Integer)

The number of the input currently selected as the source for a multi-switch.

<Input name> Selected (Boolean)

True if the given input is currently selected for multi-switch.

<Output name> Selected (Boolean)

True if the given output is currently selected for multi-switch.

Presets (for current remote)

Names come from the friendly names given in the configuration. These variables are only present if the Preset Mode in configuration settings is Use Buttons To Choose Outputs.

<Output name> Selected (Boolean)

True if the given output is currently selected for saving its state in a preset.

Input names

Names come from the friendly names given in the configuration.

<Input name> Custom Name (String)

The name of the input as a variable, for use in automatically naming buttons etc.

Output names

Names come from the friendly names given in the configuration.

<Output name> Custom Name (String)

The name of the output as a variable, for use in automatically naming buttons etc.

Tags

This driver uses the following non-standard tags. For default tags, reference the master tag list.

Multi-Switch: Apply Selection (M)

• Function usage: Request the multi-switch that has been set up using input and output selections.

Multi-Switch: Clear All Outputs (M)

• Function usage: Clear all the outputs currently selected for a multi-switch.

Multi-Switch: Input: <name> (M/V/T)

• Function usage: Select the given input for multi-switching

• Variable usage: Name and selection state of the input.

Multi-Switch: Output <name> (M/V/T)

• Function usage: Select the given output for multi-switching

• Variable usage: Name and selection state of the output

Multi-Switch: Select All Outputs (M)

• Function usage: Select all the outputs to be included in a multi-switch

Single Switch: Output Name (T)

• Variable usage: The name of the output defined by the current Integration Designer Source

Single Switch: Current Input (T)

• Variable usage: The name of the input routed to the output defined by the current Integration Designer Source

Single-Switch: Input: <name> (M/V/T)

• Function usage: Switch the given input to the output defined by the current Integration Designer Source

• Variable usage: The name of the input and a flag to indicate if it is the current input for that output.

Switching Presets: Clear All Outputs (M)

• Function usage: Clear all the outputs currently selected for storing in a preset.

Switching Presets: Output: <name> (M)

• Function usage: Select the given output for storing in a preset.

• Variable usage: Name and selection state of the output

Switching Presets: Recall: <n> (M)

• Function usage: Recall the switching state stored in the preset

Switching Presets: Save: <n> (M)

• Function usage: Save the switching state of the selected (or all) outputs in the preset

Events

This driver supports the following events.

Connection Status Changed

• Event trigger: Triggers when Connection Status changes

Dante Connection Status Changed

• Event trigger: Triggers when Dante Connection Status changes

<Output Name> Input Changed

• Event trigger: Triggers when the source for the given output changes

<Output Name> Off

• Event trigger: Triggers when the given output is turned off

<Output Name> <Input Name> Selected

• Event trigger: Triggers when the given input has been selected on the given output

• Notes: Only available if 256 or fewer possible combinations

System Testing

Integration Designer: 11.15

XP Processor Model: XP-8v

XP Processor Firmware: 25.9.24

Device Model(s): AC-MXNET-DANTE-CBOX

Support Contact

If you encounter any issues with the driver, please contact us at https://support.avproglobal.com/portal/en/home and we will be happy to assist however needed.

Disclaimer of liability

The company shall not be liable for any issues, damages, or costs that may arise from the use of our driver software. While we strive to ensure that all versions of our driver are backward compatible, we cannot guarantee that this will always be the case. Users are advised to thoroughly test the driver in their specific environments and configurations before deployment to ensure compatibility and proper functionality. The company makes every effort to provide a reliable and functional product, but the driver is provided “as is” without warranties of any kind, either express or implied. The user assumes full responsibility for any loss, damage, or disruption caused using our driver, including, but not limited to, hardware malfunctions, data loss, or system failures. By using our driver, you acknowledge that you have read and understood this disclaimer, and you agree to release and hold harmless the company from all liabilities associated with its use.