MXnet Endpoints User Manual

MXnet Endpoints User Manual

Supported Products

Evolution I Endpoints

  1. AC-MXNET-1G-E
  2. AC-MXNET-1G-D
  3. AC-MXNET-1G-AVDM-E
  4. AC-MXNET-1G-DANTE-E
  5. AC-MXNET-1G-EWP

Evolution II Endpoints

  1. AC-MXNET-1G-EV2
  2. AC-MXNET-1G-DV2
  3. AC-MXNET-1G-AVDM-EV2
  4. AC-MXNET-1G-DANTE-EV2
  5. AC-MXNET-1G-DANTE-DV2
  6. AC-MXNET-1G-EV2WP
  7. AC-MXNET-1G-MV41V2
  8. AC-MXNET-1G-HEX-UV2
  9. AC-MXNET-1G-DEX-UV2

USP Endpoints

  1. AC-MXNET-USP-ES
  2. AC-MXNET-USP-PL
  3. AC-MXNET-USP-PR

10G Endpoints

  1. AC-MXNET-10G-TCVR
  2. AC-MXNET-10G-TCVR-AVDM
  3. AC-MXNET-10G-TCVR-PRO
  4. AC-MXNET-10G-TCVR-USBX

Control Box

  1. AC-MXNET-CBOX-HA

Important Safety Instructions

Prior to installing, configuring, and operating all MXnet devices and other vendor equipment, AVPro recommends that each dealer, integrator, installer, and all other necessary personnel access and read all the required technical documentation, which can be located by visiting avproglobal.com.

Read and understand all safety instructions, cautions, and warnings in this document and the labels on the equipment.

Safety Classifications in this Document

Info
NOTE
Provides information related to system design, caveats or limitations of equipment.
Idea
TIP
Provides suggestions and considerations for installing, configuring and operating devices.
Alert
IMPORTANT/CAUTION
Provides important information for installing or operating the equipment.
Warning
WARNING
Provides critical information for situations that may cause physical damage to the equipment, installer or user.

Electrical Shock Prevention

Alert
ELECTRICAL SHOCK
The source power poses an electrical shock hazard that can potentially cause serious injury to installers and end users.
Alert
ELECTRICAL DISCONNECT
The source power outlet and power supply input power sockets should be easily accessible to disconnect power in the event of an electrical hazard or malfunction.

Weight Injury Prevention

Alert
WEIGHT INJURY
Installing some of the MXnet devices requires two installers to ensure safe handling during installation. Failure to use two installers may result in injury.

Safety Statements

Follow all of the safety instructions listed below and apply them accordingly. Additional safety information will be included where applicable.
  1. Read and keep these instructions.
  2. Heed all warnings and follow all instructions.
  3. Do not use these devices near water.
  4. Clean only with a dry cloth.
  5. Do not block any ventilation openings. Install in accordance with the manufacturer’s instructions.
  6. Do not install near any heat sources such as radiators, heat registers, stoves, or other apparatus (including amplifiers) that produce heat.
  7. Do not defeat the safety purpose of the polarized or grounding-type plug. A polarized plug has two blades with one wider than the other. A grounding-type plug has two blades and a third grounding prong. The wide blade or third prong are provided for your safety. If the provided plug does not fit into your outlet, consult an electrician for replacement of the obsolete outlet.
  8. Protect the power cord from being walked on or pinched particularly at plugs, convenience receptacles, and the point where they exit from the devices.
  9. Only use attachments and accessories specified by the manufacturer.
  10. Unplug these devices during lightning storms or when unused for long periods of time.
  11. To reduce the risk of electric shock or damage to these devices, never handle or touch the devices and power cord if your hands are wet or damp. Do not expose these devices to rain or moisture.
  12. Refer all servicing to qualified service personnel. Servicing is required when the devices have been damaged in any way, such as power supply cord or plug is damaged, liquid has been spilled, objects have fallen into the devices, the devices have been exposed to rain or moisture, does not operate normally as intended, or has been dropped.
  13. The devices and their accessories should never be exposed to open flames or excessive heat.

Introduction

MXnet is an ecosystem of several series of AV over IP products that use standard networking infrastructure to route video, audio, and control signals throughout large scale systems with an unlimited number of sources and displays, all switching independently and seamlessly. Designed and developed by AVPro Edge, MXnet provides the complete end-to-end solution for stability, interoperability, and easy deployment of the entire system.

The diagram below shows a generalized system topology that incorporates the essential components for building an MXnet system. This includes an MXnet AV switch, encoders, decoders and a CBOX.

Definitions

Endpoint

A generalized term used to describe an encoder, decoder or transceiver.

Encoders

Encoders are devices that connect to a source device such as a media player, game console, computer etc...and convert (or encode) a signal onto the network.

Decoders

Decoders are devices that connect to a sink device such as a television or projector and receive (or decode) signals generated by MXnet encoders.

Transceivers

Transceivers are devices designed to encode and/or decode. This allows them to connect to a source device or sink device and in some cases both simultaneously (based on model).

Audio Downmixing

Certain MXnet models provide the capability of downmixing multi-channel audio signals to stereo. These models contain the identifier of 'AVDM' in their part number. Audio downmixing is only available on models with this identifier.

Control Box (CBOX)

The control box or 'CBOX' is the device used to communicate and configure MXnet endpoints, and is where the system logic is stored and the commands are processed. The API utilized by the Mentor web interface and third-party control systems are centralized to the CBOX to provide multipoint AV over IP distribution. 

Mentor

Mentor is the web-based setup and control interface that is hosted on the CBOX.

Network Switches

A network switch is a device that connects multiple devices within a local area network (LAN) and enables them to communicate efficiently. MXnet endpoints requires the use of certain network switch protocols to properly route AV traffic to its destination. 

For details on MXnet network switches, view the MXnet Network Switch User Manual.
  1. MXnet Firmware
  2. How To Configure High Availability on the CBOX-HA
  3. CBOX-HA Dante Controller Overview
  4. MXnet 1G API
  5. MXnet 10G API
To view more How-To articles and to find additional MXnet-related guides visit the MXnet Knowledge Base.

Before You Begin

MXnet does not require the encoders and decoders to be connected in any specific order on the network switch, meaning they can be placed on adjacent ports right next to each other and the system will function without issue. However, for best results (especially when managing highly complex systems with dozens of endpoints) a certain degree of design and planning is highly recommended and can save precious time when it comes to installing, testing, and implementing features on the system.

Read through this document in its entirety and ensure that the following required items are available:
  1. MXnet Encoder or Transceiver
  2. MXnet Decoder or Transceiver
  3. MXnet CBOX
  4. MXnet Network Switch or a 3rd-party model that meets MXnet requirements (see section: Third-Party Network Switch Requirements)
  5. Source devices, displays, and any other devices that will be used in the system

Some Helpful Suggestions

  1. Make a list of all the devices in the system, including the sources and displays, model numbers and SKU’s, MAC addresses and assigned IP addresses, along with any accessories such as rack equipment, power sources, cable types and lengths.
  2. Create a diagram or flow chart to indicate the starting and end points of the network cable runs, as well as any schematics, diagrams, and other supporting documentation for easy future reference.
  3. Label the connections in the rack to their corresponding endpoints or ports on the network switch.
  4. For larger projects, consider grouping the encoder cables next to each other on the network switch and likewise for the decoders.

Network Cabling Tips

Everything about a successful MXnet installation revolves around the network cabling itself. Keep in mind that the quality, distance, and handling of the cable can all affect the signal speed and data stream. Generally speaking, the higher the video resolution and the longer the run, the better the cabling should be.

When terminating network cables, do not untwist the wires unnecessarily. Make sure to not untwist more than ½ inch, preferably ¼ inch. Wires are twisted for good reasons:
  1. Cancels out EMI (Electromagnetic Interference)
  2. Cancels out crosstalk from neighboring conductors
For most applications, Cat5e (or better) is recommended for MXnet.

  1. Terminate with standard RJ-45 connectors. Avoid using push-through or “EZ” type ends, as these have exposed copper wiring at the tips that can cause signal interference.
  2. Cable terminations should be consistent with T568A or T568B. Avoid mixing terminations such as going from T568A to T568B, and vice versa.
  3. Remove as little of the sheath as possible.
  4. Handle cables with care. If you need to pull, don’t pull too hard as this may cause the wire pairs to untwist and can degrade cable performance.
  5. Use zip ties to neatly, but loosely, bundle the cable runs together to reduce tangling. Avoid tight zip ties, clamps, and staples.
  6. Stay organized, label each cable run on both ends to indicate the location of the inputs and outputs.
  7. Do not overbend cables. ¼ inch cable ratio = 2” bend radius.
  8. Keep network cables away from power sources. 

Third-Party Control Systems

MXnet supports third-party control systems with drivers readily available to download, allowing for further customizable programming and commands to integrate with MXnet. Be sure to successfully install and connect your MXnet system to the network first before integrating it with a third-party control system.

Supported drivers for third-party control system can be located at support.avproedge.com.

Product Overviews

MXnet contains several different series/ecosystems of endpoints. Each with varying hardware specifications and AV processing capabilities. 

Hardware I/O

Info
NOTE
MXnet Evolution I and Evolution II devices may coexist on the same network but AV signals are not interoperable.(i.e. routing a AC-MXNET-1G-EV2 to a AC-MXNET-1G-D or vice versa is not supported).

Evolution I Series

AC-MXNET-1G-E, AVDM
AC-MXNET-1G-DANTE-E
AC-MXNET-1G-EWP
AC-MXNET-1G-D
AC-MXNET-1G-E, AVDM
Front Panel

Rear Panel


ID
Connector
Description
1
Power Status
Flashing: device is booting
Solid: device is operating normally
2
Link Status
Flashing: no input source detected
Solid: input detected and/or source routed to a decoder
3
EDID Copy
Press to copy the EDID of the sink device connected to the HDMI loop out
4
RS-232
3-Pin Phoenix terminal block. Supports sending encapsulated serial over IP commands to peripheral equipment for control.
5
IR-Pass
3.5mm TRS IR receive port. Connects to an  IR generation devices such as a control system to passthrough IR to desired endpoints
6
IR Eye
3.5mm TRS IR receive port. Supports capture of IR signals from control system or handheld remote control to route to desired endpoints
7
IR Out
3.5mm TRS IR transmit port. Supports sending encapsulated IR over IP commands to peripheral equipment for control
8
Info Screen
Provides key information about the endpoint including:
  1. IP address
  2. MAC address
  3. Custom name
9
EDID Switches
Use to configured specific EDIDs on the encoder

10
USB Mode
FPGA/MCU toggle switch. Used for advanced debugging/updating.
11
USB Debug
Type-B Micro port. Used for advanced debugging/updating.
12
LAN
  1. 8-Pin RJ-45 Female connector, 1000Base-T
  2. 802.3af 15.4w PoE (average consumption ~6.5W; AVDM ~9.5W)
  3. Maximum distance of 100m over Cat5e or higher
13
SFP 
  1. Bidirectional 1Gbps SFP port
  2. SSM: LC to LC 1310nm, up to 40km
  3. MMF: LC to LC 850nm, up to 550m
14
HDMI Loop
19-pin HDMI 1.4 Type A female connector
15
HDMI In
19-pin HDMI 1.4 Type A female connector
16
Audio Out
Balanced 5-Pin Phoenix Terminal Block. Extracts up to 2CH analog PCM audio.
17
Audio In
Unbalanced 3.5mm TRS connector. Embeds 2CH audio onto the network, overrides HDMI audio.
18
USB Host
1.1 Type B connector. Supports USB extension of HID compliant devices
19
Reset
Press and hold for 7 seconds to factory default unit.
20
DC Power
12V 1A locking barrel connector. Optional power method if not using PoE

AC-MXNET-1G-DANTE-E

ID
ConnectorDescription
1Power Status
Flashing: device is booting
Solid: device is operating normally
2Link Status
Flashing: no input source detected
Solid: input detected and/or source routed to a decoder
3EDID Copy
Press to copy the EDID of the sink device connected to the HDMI loop out.
4RS232
3-Pin Phoenix terminal block. Supports sending encapsulated serial over IP commands to peripheral equipment for control.
5IR-Pass
3.5mm TRS IR receive port. Connects to an  IR generation devices such as a control system to passthrough IR to desired endpoints.
6IR Eye
3.5mm TRS IR receive port. Supports capture of IR signals from control system or handheld remote control to route to desired endpoints.
7IR Out
3.5mm TRS IR transmit port. Supports sending encapsulated IR over IP commands to peripheral equipment for control.
8Info Screen
Provides key information about the endpoint including:
  1. IP address
  2. MAC address
  3. Custom name
9EDID Switches
Use to configured specific EDIDs on the encoder.

10USB Mode
FPGA/MCU toggle switch.
11USB Debug
Type-B Micro. Used for advanced debugging
12MXnet LAN
  1. 8-Pin RJ-45 Female connector, 1000Base-T
  2. 802.3af 15.4w PoE (average consumption ~6.5W)
  3. Maximum distance of 100m over Cat5e or higher
13
Dante LAN
  1. 8-Pin RJ-45 Female connector, 1000Base-T
  2. Maximum distance of 100m over Cat5e or higher
14SFP 
  1. Bidirectional 1Gbps SFP port
  2. SSM: LC to LC 1310nm, up to 40km
  3. MMF: LC to LC 850nm, up to 550m
15HDMI Loop
19-pin HDMI 1.4 Type A female connector

16
HDMI In
19-pin HDMI 1.4 Type A female connector
17Audio Out
Balanced 5-Pin Phoenix Terminal Block. Extracts up to 2CH analog PCM audio.
18Audio In
Unbalanced 3.5mm TRS connector. Embeds 2CH audio onto the network, overrides HDMI audio
19USB Host
1.1 Type B connector. Supports USB extension of HID compliant devices.
20Reset
Press and hold for 7 seconds to factory default unit
21DC Power
12V 1A locking barrel connector. Optional power method if not using PoE.

AC-MXNET-1G-EWP

ID
Connector
Description
1
USB Host
USB 1.1 Type B connector. Used for USB extension of HID compliant devices.
2
RS232
3.5mm TRS connector. Supports sending encapsulated RS232 over IP to control peripheral equipment.
3
HDMI In
19-pin HDMI 1.4 Type A female connector
4
VGA In
15-pin VGA female connector
5
Audio In
3.5mm TRS connector
Embed audio onto the network, overrides HDMI audio
6
Input LED
Solid: when VGA active input is detected
Off: when HDMI active input is detected
7
Link LED
Solid: when active video input signal is detected


IDConnectorDescription
1EDID Dial
Used to configure specific EDIDs on the encoder.

2USB Switch
FPGA/MCU toggle switch
3USB 
Type B Micro connector
Used for advanced system debugging
4LAN
  1. 8-Pin RJ-45 Female connector, 1000Base-T
  2. 802.3af 15.4w PoE (average consumption ~6.5W)
  3. Maximum distance of 100m over Cat5e or higher



AC-MXNET-1G-D
Front Panel

Rear Panel


ID
ConnectorDescription
1Power Status
Flashing: device is booting
Solid: device is operating normally
2Link Status
Flashing: no output/sink device detected
Solid: sink device detected
3EDID Copy
Press to copy the EDID of the sink device connected to the HDMI out
4RS232
3-Pin Phoenix terminal block. Supports sending encapsulated serial over IP commands to peripheral equipment for control.
5IR-Pass
3.5mm TRS IR receive port
Connects to an  IR generation devices such as a control system to passthrough IR to desired endpoints
6IR Eye
3.5mm TRS IR receive port
Supports capture of IR signals from control system or handheld remote control to route to desired endpoints
7IR Out
3.5mm TRS IR transmit port
Supports sending encapsulated IR over IP commands to peripheral equipment for control
8Info Screen
Provides key information about the endpoint including:
  1. IP address
  2. MAC address
  3. Custom name
9/10USB  Device
USB 1.1 Type A connectors
Used to connect and extend USB HID compliant peripherals
11USB Switch
FPGA/MCU toggle switch.
12USB Debug
Type-B Micro. Used for advanced debugging/updating.
13LAN
  1. 8-Pin RJ-45 Female connector, 1000Base-T
  2. 802.3af 15.4w PoE (average consumption ~6.5W)
  3. Maximum distance of 100m over Cat5e or higher
14SFP 
  1. Bidirectional 1Gbps SFP port
  2. SSM: LC to LC 1310nm, up to 40km
  3. MMF: LC to LC 850nm, up to 550m
15HDMI Out
19-pin HDMI 1.4 Type A female connector.
16Audio Out
Balanced 5-Pin Phoenix Terminal Block. Extracts up to 2CH analog PCM audio.
17Reset
Press and hold for 7 seconds to factory default unit.
18DC Power
12V 1A locking barrel connector. Optional power method if not using PoE.

Evolution II Series

AC-MXNET-1G-EV2, AVDM-EV2, DANTE-EV2
AC-MXNET-1G-EV2WP
AC-MXNET-1G-DV2, DANTE-DV2
AC-MXNET-1G-MV41V2
AC-MXNET-1G-HEX-UV2
AC-MXNET-1G-DEX-UV2
AC-MXNET-1G-EV2, AVDM-EV2, DANTE-EV2

ID
ConnectorDescription
1Power Status
Flashing: device is booting
Solid: device is operating normally
2Link Status
Flashing: no input source detected
Solid: input detected and/or source routed to a decoder
3EDID Copy
Press to copy the EDID of the sink device connected to the HDMI loop out
4RS2323-Pin Phoenix terminal block. Supports sending encapsulated serial over IP commands to peripheral equipment for control.
5IR-Pass3.5mm TRS IR receive port. Connects to an  IR generation devices such as a control system to passthrough IR to desired endpoints
6IR Eye3.5mm TRS IR receive port. Supports capture of IR signals from control system or handheld remote control to route to desired endpoints
7IR Out3.5mm TRS IR transmit port. Supports sending encapsulated IR over IP commands to peripheral equipment for control
8Info Screen
Provides key information about the endpoint including:
  1. IP address
  2. MAC address
  3. Custom name
9EDID Switches
Use to configured specific EDIDs on the encoder
10Toggle SwitchFPGA/MCU toggle switch.
11USB DebugType-C port. Used for advanced debugging/updating.
12LAN
  1. 8-Pin RJ-45 Female connector, 1000Base-T
  2. 802.3af 15.4w PoE (average consumption ~6.5W; AVDM ~9.5W)
  3. Maximum distance of 100m over Cat5e or higher
13SFP 
  1. Bidirectional 1Gbps SFP port
  2. SSM: LC to LC 1310nm, up to 40km
  3. MMF: LC to LC 850nm, up to 550m
14HDMI Loop19-pin HDMI 2.0b Type A female connector
15HDMI In19-pin HDMI 2.0b Type A female connector
16Audio OutBalanced 5-Pin Phoenix Terminal Block. Extracts up to 2CH analog PCM audio.
17
Digital Audio Out
Toslink connector. Extracts up to 6CH digital audio formats.
17Audio InUnbalanced 3.5mm TRS connector. Embeds 2CH audio onto the network, overrides HDMI audio.
18USB Host2.0 Type B connector. Supports USB extension of HID and isochronous devices.
19ResetPress and hold for 7 seconds to factory default unit.
20DC Power12V 1A locking barrel connector. Optional power method if not using PoE.
AC-MXNET-1G-EV2WP

ID
Connector
Description
1
Input LEDs
Solid: indicates the selected input (USB-C or HDMI)
Off: unit is not powered on
2
Link LED
Solid: active video input detected
Flashing: no active video input detected
3
USB-C In
2.0 Type C connector. Supports USB data host and DisplayPort Alt-mode.
4
HDMI In
19-pin HDMI 2.0b Type A female connector.
5
Audio In
Unbalanced 3.5mm TRS connector. Embeds 2CH audio onto the network, overrides USB-C/HDMI audio.
6
RS232
3.5mm TRS connector. Supports sending encapsulated serial over IP commands to peripheral equipment for control.
7
Input Select Button
Momentary push button. Switches between USB-C and HDMI inputs.
8
USB Host
2.0 Type B connector. Supports USB extension of HID and isochronous devices.
9
EDID Dial
Use to configured specific EDIDs on the encoder.
10
Toggle Switch
FPGA/MCU toggle switch.
11
USB Debug
Type-C port. Used for advanced debugging/updating.
12
Reset
Press and hold for 7 seconds to factory default unit.
13
LAN
  1. 8-Pin RJ-45 Female connector, 1000Base-T
  2. 802.3af 15.4w PoE (average consumption ~6.5W; AVDM ~9.5W)
  3. Maximum distance of 100m over Cat5e or higher


AC-MXNET-1G-DV2, DANTE-DV2

ID
ConnectorDescription
1Power Status
Flashing: device is booting
Solid: device is operating normally
2Link Status
Flashing: no output/sink device detected
Solid: sink device detected
3EDID CopyPress to copy the EDID of the sink device connected to the HDMI out
4RS2323-Pin Phoenix terminal block. Supports sending encapsulated serial over IP commands to peripheral equipment for control.
5IR-Pass
3.5mm TRS IR receive port. Connects to an  IR generation devices such as a control system to passthrough IR to desired endpoints
6IR Eye
3.5mm TRS IR receive port. Supports capture of IR signals from control system or handheld remote control to route to desired endpoints
7IR Out
3.5mm TRS IR transmit port. Supports sending encapsulated IR over IP commands to peripheral equipment for control
8Info Screen
Provides key information about the endpoint including:
  1. IP address
  2. MAC address
  3. Custom name
9USB Device
USB 2.0 Type A connectors. Used to connect and extend USB HID and isochronous compliant peripherals.
10Toggle SwitchFPGA/MCU toggle switch.
11USB DebugType-C connector. Used for advanced debugging/updating.
12LAN
  1. 8-Pin RJ-45 Female connector, 1000Base-T
  2. 802.1af 15.4w PoE (average consumption ~6.5W)
  3. Maximum distance of 100m over Cat5e or higher
13SFP 
  1. Bidirectional 1Gbps SFP port
  2. SSM: LC to LC 1310nm, up to 40km
  3. MMF: LC to LC 850nm, up to 550m
14HDMI Out19-pin HDMI 2.0b Type A female connector.
15Digital Audio InToslink connector. Ingests up to 6CH digital audio formats.
16
Analog Audio Out
Unbalanced 3.5mm TRS connector. Extracts up to 2CH analog PCM audio.
17ResetPress and hold for 7 seconds to factory default unit.
18DC Power12V 1A locking barrel connector. Optional power method if not using PoE.

AC-MXNET-1G-MV41V2
ID
Connector
Description
1
Info Screen
Provides matrix switching and network configuration options.
2
Navigation Buttons
Used to navigate through the front panel info screen menus.
3
Input Buttons
Used to manually route video between the four inputs.
4
Preset Buttons
Used to activate the four default multiview presets.
5
LAN
4x 8-pin RJ-45 connections, 1000Base-T for video decoding.
6
LAN
8-pin RJ-45 connection, 1000Base-T for video encoding.
7
HDMI Out
19-pin HDMI 2.0b Type A female connector
8
DC Power
12V 5A DC locking barrel connector.




AC-MXNET-1G-HEX-UV2
ID
Connector
Description
1
Info Screen
Provides key information about the endpoint including:
  1. IP address
  2. MAC address
  3. Custom name
2
USB-C Host2.0 Type C connector. Used for connecting to a USB host device. Supports receiving 5V power through USB as alternate method to PoE.
3
Reset
Press and hold for 7 seconds to factory default unit.

4
USB-C Debug
Type-C connector. Used for advanced debugging/updating.

5
Toggle Switch
MCU/FPGA toggle switch.
6
LAN
  1. 8-Pin RJ-45 Female connector, 1000Base-T
  2. 802.3af 15.4w PoE (average consumption ~6.5W)
  3. Maximum distance of 100m over Cat5e or higher
7
SFP
  1. Bidirectional 1Gbps SFP port
  2. SSM: LC to LC 1310nm, up to 40km
  3. MMF: LC to LC 850nm, up to 550m
8
Status LEDs
Link LED:
  1. Flashing: no route.
  2. Solid: route is made
Act LED:
  1. Solid: device operating as normal
  2. Off: device is powered off



AC-MXNET-1G-DEX-UV2
IDConnectorDescription
1USB Device Ports
2.0 Type A. Used for connecting HID or isochronous USB peripherals.
2USB Device Ports2.0 Type C. Used for connecting HID of isochronous USB peripherals.
3Info Screen
Provides key information about the endpoint including:
  1. IP address
  2. MAC address
  3. Custom name

4
Push ButtonUsed to cycle between various information on the front panel screen

5
ResetMCU/FPGA toggle switch.
6
DC Power
12V 1A DC locking barrel connector. Optional power method if not using PoE.
7
USB Debug
Type C connector. Used for advanced debugging/updating.
8
Toggle Switch
MCU/FPGA toggle switch.
9
Toggle Switch
5V On: 5V is always available to USB devices
5V Host : 5V is only available when a host device is connected to a routed HEX
10LAN
  1. 8-Pin RJ-45 Female connector, 1000Base-T
  2. 802.3af 15.4w PoE (average consumption ~6.5W)
  3. Maximum distance of 100m over Cat5e or higher
11SFP
  1. Bidirectional 1Gbps SFP port
  2. SSM: LC to LC 1310nm, up to 40km
  3. MMF: LC to LC 850nm, up to 550m
12Status LEDs
Link LED:
  1. Flashing: no route.
  2. Solid: route is made
Act LED:
  1. Solid: device operating as normal
  2. Off: device is powered off

USP Series

AC-MXNET-USP-ES
AC-MXNET-USP-PL
AC-MXNET-USP-PR
AC-MXNET-USP-ES

ID
ConnectorDescription
1Status LEDs
Solid: device is operating normally
Off: device is not powered on or has a fault
2Info Screen
Provides key information about the endpoint including:
  1. IP address
  2. MAC address
  3. Custom name
3ISP/RebootPress to reboot the endpoint.
4Toggle SwitchMCU/FPGA toggle switch.
5USB DebugType C connector. Used for advanced debugging/updating.
6DC Power12V 2A locking barrel connector. Optional power method if PoE is not used.
7RS2323-Pin Phoenix terminal block. Supports sending encapsulated serial over IP commands to peripheral equipment for control.
8IR-Pass3.5mm TRS IR receive port. Connects to an  IR generation devices such as a control system to passthrough IR to desired endpoints
9IR Eye3.5mm TRS IR receive port. Supports capture of IR signals from control system or handheld remote control to route to desired endpoints
10IR Out3.5mm TRS IR transmit port. Supports sending encapsulated IR over IP commands to peripheral equipment for control
11Analog Audio InUnbalanced 3.5mm TRS connector. Embeds 2CH audio onto the network, overrides HDMI audio.
12HDMI In19-pin HDMI 2.0b Type A female connector
13HDMI Out19-pin HDMI 2.0b Type A female connector
14Analog Audio OutBalanced 5-Pin Phoenix Terminal Block. Extracts up to 2CH analog PCM audio.
15LAN
  1. 8-Pin RJ-45 Female connector, 1000Base-T
  2. 802.3af 15.4w PoE (max consumption 13.3W)
  3. Maximum distance of 100m over Cat5e or higher

AC-MXNET-USP-PL

ID
ConnectorDescription
1Status LEDs
Solid: device is operating normally
Off: device is not powered on or has a fault
2USB Device Ports1.1 Type A. Used for connecting HID compliant peripherals.
3Info Screen
Provides key information about the endpoint including:
  1. IP address
  2. MAC address
  3. Custom name
4USB-C Host1.1 Type C connector. Supports to connecting to USB 1.1 host equipment.
5ISP/RebootPress to reboot the endpoint.
6USB DebugType C connector. Used for advanced debugging/updating.
7DC Power12V 2A locking barrel connector. Optional power method if PoE is not used.
8RS2323-Pin Phoenix terminal block. Supports sending encapsulated serial over IP commands to peripheral equipment for control.
9IR-Pass3.5mm TRS IR receive port. Connects to an  IR generation devices such as a control system to passthrough IR to desired endpoints
10IR Eye3.5mm TRS IR receive port. Supports capture of IR signals from control system or handheld remote control to route to desired endpoints
11IR Out3.5mm TRS IR transmit port. Supports sending encapsulated IR over IP commands to peripheral equipment for control
12Analog Audio InUnbalanced 3.5mm TRS connector. Embeds 2CH audio onto the network, overrides HDMI audio.
13HDMI In19-pin HDMI 2.0b Type A female connector
14HDMI Out19-pin HDMI 2.0b Type A female connector
15Analog Audio OutBalanced 5-Pin Phoenix Terminal Block. Extracts up to 2CH analog PCM audio.
16LAN
  1. 8-Pin RJ-45 Female connector, 1000Base-T
  2. 802.3af 15.4w PoE (max consumption 14.2W)
  3. Maximum distance of 100m over Cat5e or higher

AC-MXNET-USP-PR

ID
ConnectorDescription
1Status LEDs
Solid: device is operating normally
Off: device is not powered on or has a fault
2USB Device Ports
1.1 Type A. Used for connecting HID compliant peripherals.
3Info Screen
Provides key information about the endpoint including:
  1. IP address
  2. MAC address
  3. Custom name
4
USB-C In
Supports USB host and DisplayPort Alt-mode. 60W power delivery available when endpoint is powered through DC power supply.
5
ISP/Reboot
Press to reboot the endpoint.
6
Toggle Switch
MCU/FPGA toggle switch.
7
USB Debug
Type C connector. Used for advanced debugging/updating.
8
DC Power
24V 5A locking barrel connector. Optional power method if PoE is not used. Is required for USB-C power delivery.
9RS2323-Pin Phoenix terminal block. Supports sending encapsulated serial over IP commands to peripheral equipment for control.
10IR-Pass3.5mm TRS IR receive port. Connects to an  IR generation devices such as a control system to passthrough IR to desired endpoints
11IR Eye3.5mm TRS IR receive port. Supports capture of IR signals from control system or handheld remote control to route to desired endpoints
12IR Out3.5mm TRS IR transmit port. Supports sending encapsulated IR over IP commands to peripheral equipment for control
13
Analog Audio In
Unbalanced 3.5mm TRS connector. Embeds 2CH audio onto the network, overrides HDMI audio.
14
HDMI In
19-pin HDMI 2.0b Type A female connector
15
HDMI Out
19-pin HDMI 2.0b Type A female connector
16
Analog Audio Out
Balanced 5-Pin Phoenix Terminal Block. Extracts up to 2CH analog PCM audio.
17LAN
  1. 8-Pin RJ-45 Female connector, 1000Base-T
  2. 802.3at 25w PoE+ (max consumption 22.8W)
  3. Maximum distance of 100m over Cat5e or higher

10G Series

AC-MXNET-10G-TCVR, AVDM, PRO, USBX
AC-MXNET-10G-TCVR, AVDM, PRO, USBX


ID
Connector
Description
1
Toggle Switch
Switches endpoint between encoder or decoder mode. Reboot required.
2
Status LED
Off: Decoder mode
Solid: Encoder mode
3
Status LED
LED 1 Solid: HDMI signal is detected on the transceiver
LED 2 Flashing: Transceiver is transmitting data
LED 3 Flashing: Transceiver is receiving data
4
Info Screen
Provides key information about the endpoint including:
  1. IP address
  2. MAC address
  3. Custom name
5
USB Host
1.1 Type B connector on TCVR & AVDM. Used for connecting to a 1.1 USB host device.
2.0 Type B connector on PRO & USBX. Used for connecting to a 2.0 USB host device.
6
USB Device
1.1 Type A connectors on TCVR & AVDM. Used for connecting to USB HID compliant devices.
2.0 Type A connectors on PRO & USBX. Used for connecting to USB HID or isochronous devices.
7
IR I/O
IR Eye, Out & Passthrough. Used for encapsulating IR signals over IP to control peripherals equipment.
8
Reset
Press and hold for 7 seconds to reset endpoint to factory default.
9
USB Debug
Type C connector. Used for advanced debugging/updating.
10
DC Power
12V 1A DC locking barrel connecting.
11
RS232
3-pin Phoenix terminal block. Used for encapsulating RS232 signals over IP to control peripherals.
12
Analog Audio Out
3-pin Phoenix terminal block. Extracts up to 2CH analog audio signals.
13
Digital Audio Out
Toslink connector. Extracts up to 6CH digital audio signals.
14
HDMI In
19-pin HDMI 2.0b Type A female connector.
15
HDMI Out
19-pin HDMI 2.0b Type A female connector.
16
Audio In/Out
3.5mm TRS connector. Can be be used to ingest or extract analog audio signals.
17
LAN
Main SDVoE 10G network output.
  1. 8-Pin RJ-45 Female connector, 10GBase-T
  2. 802.3af 15.4w PoE
    1. TCVR: max consumption 9.2W
    2. AVDM: max consumption: 10.1W
    3. PRO: max consumption 14.2W
  3. Maximum distance of 100m over Cat6a or higher
18
Toggle Switch
Switches between RJ-45 or SFP+ as the active network connection.
19
SFP+
  1. Bidirectional 10Gbps SFP+ port
  2. SSM: LC to LC 1310nm, up to 20km
  3. MMF: LC to LC 850nm, up to 550m
20
Toggle Switch 
Switches between 10G or 1G LAN ports as the active PoE port.
21
LAN
Auxiliary 1G "courtesy" port. Does not support AV output. 
  1. 8-Pin RJ-45 Female connector, 1000Base-T
  2. 802.1af 15.4w PoE (selectable)
  3. Maximum distance of 100m over Cat6a or higher

 CBOX

AC-MXNET-CBOX-HA
AC-MXNET-CBOX-HA


ID
Connector
Description
1
Status LED
Flashing: booting or operating as normal
2
Push Button
Press to cycle between information on status monitor "A"
3
Info Screen
Provides key information for the "control port" including:
  1. IP mode (static or DHCP)
  2. IP address
  3. Firmware version
4
Push Button
Press to cycle between information on status monitor "B"
5
Info Screen
Provides key information for the "AV port" including:
  1. IP address
  2. Current online TXs and RXs
  3. Total TXs and RXs discovered
6
Push Button
Press and hold for 5 seconds to change the Control port between a DHCP or static IP address.
7
Reset
Press and hold for 7 seconds to factory default the unit.
8
Button"Triggers" behavior based on adjacent toggle switch position. 
9
Toggle Switch
Update/debug toggle switch
10
USB Debug
Type C connector. Used for advanced debugging/updating.
11
Control LAN
Used for connecting to Control or I.T. networks.
  1. 8-Pin RJ-45 Female connector, 1000Base-T
  2. Maximum distance of 100m over Cat6a or higher
12
Peripheral LAN
Used for connecting to MXnet Switch MGMT ports for Mentor web access or for simple control of IP-peripherals. Not intended for use with high-bandwidth devices or streaming.
  1. 6x 8-Pin RJ-45 Female connector, 1000Base-T
  2. Maximum distance of 100m over Cat6a or higher
13
AV LAN
Used for connecting to AV networks and communicating to MXnet endpoints.
  1. 8-Pin RJ-45 Female connector, 1000Base-T
  2. 802.1af 15.4w PoE (average consumption ~4.5W)
  3. Maximum distance of 100m over Cat6a or higher
14
RS232
3-pin Phoenix terminal block. Used as alternative method for API control.
15
HA Link
8-Pin RJ-45 Female connector, 1000Base-T. Used for establishing a high availability link between two CBOX-HAs. 
16
DC Power
12V 1A DC locking barrel connector. Optional power method.

 Spec Table

USP SeriesUSP SeriesEvolution I SeriesEvolution II Series
10G Series
Max Input Resolution4K60 4:4:4 8b*
4K30 4:4:4 8b
4K60 4:4:4 8b
4K60 4:2:2 12b
4K60 4:4:4 8b
4K60 4:2:2 12b
Max Output Resolution8K30 4:4:4 8b*4K30 4:4:4 8b
4K60 4:4:4 8b
4K60 4:2:2 12b
4K60 4:4:4 8b
4K60 4:2:2 12b
Compression CodecH.265/264JPEG-basedJPEG-based
SDVoE
Encode Bandwidth60Mbps800Mbps800Mbps
8.4Gbps
HDCP2.3*2.32.3
2.3
HDR10/DVNot SupportedNot Supported✔
✔
Preview StreamLive MJPEGImage SnapshotsLive MJPEG
Not Supported
Stream EncryptionAES-256AES-128AES-256
AES-128
AVPro Flow✔Not SupportedNot Supported
Not Supported
Audio Formats2CH PCMUp to 6CH, including Dolby/DTS
Up to 8CH, including Dolby/DTS
Up to 8CH, including Dolby/DTS
Analog Audio Breakout✔✔✔
✔
Analog Audio Input✔✔✔
✔
Dante/AES67Both (2x2)Dante Transmit (2ch)Both (2x2)
Both (2x2)
Audio DownmixingNot Supported6CH -> 2CH*8CH -> 2CH*
8CH ->2CH*
End-to-End Latency≤75ms16ms @ 60FPS
Standard: 16ms @ 60FPS
ULLM: 4-6ms @ 60FPS
Genlock: 100µs
Fast Switch: 16-32ms
PoE
802.3af 15.4w (ES/PL)
802.3at 25W (PR)
802.3af 15.4w802.3af 15.4w
802.3af 15.4w
Mentor Auto Discovery✔✔✔
✔
Custom Idle Screen✔✔✔
Not Supported
Multiview
Up to 16 windows*Not SupportedUp to 4 windows*
Up to 16 windows
Standard Video WallsUp to 8x8Up to 8x8Up to 16x16
Up to 8x8
Mosaic Video WallsNot SupportedNot Supported✔
Not Supported
Output Rotation✔✔✔
✔
IR Routing✔✔✔
✔
Serial Routing✔✔✔
✔
CEC Control✔✔✔
✔
USB1.11.12.0
Up to 2.0*
Network Type1G1G1G
10G
Warranty10 Years10 Years10 Years
10 Years
TAA ModelsN/A✔✔
✔
*Available only on specific series models.

Wiring and Connections

Ethernet

Evolution I, Evolution II, USP and the CBOX include an 8-pin RJ-45 connection capable of full duplex 1000Base-T. MXnet 10G series include an 8-pin RJ-45 connection capable of full duplex 10GBase-T. The recommended termination is based on TIA/EIA T568A or T568B standards for the wiring of the twisted pair cables: 

SFP and SFP+


SFP (small form-factor pluggable) transceivers are compact, hot-pluggable devices that act as an interface between networking equipment (network switches, routers, network cards, etc.) and interconnecting cabling (copper or fiber). While SFP and SFP+ transceivers are both similar in size and appearance, the main difference is that SFP+ can be used in 10 Gigabit network applications, while SFP is for 100/1000BASE applications. SFP complies with standards of IEEE 802.3 and SFF-8472, while SFP+ is based on SFF-8431.

MXnet can send many gigabytes of data per second with either copper or fiber connections. RJ-45 copper connections are cost-effective, but when security and stability are critical, the SFP module is recommended.
Info
SFP and SFP+ modules are not included with endpoints. However, they can be purchased directly from AVPro as a separate item.



SFP and SFP+ Module Installation

The procedure for installing SFP and SFP+ transceiver modules is shown below:
  1. Put on an ESD wrist strap (or antistatic gloves).
  2. Insert the SFP or SFP+ transceiver to the guide rail inside the fiber interface line card. Do not put in the SFP or SFP+ transceiver upside down.
  3. Push the SFP or SFP+ transceiver along the guide rail gently until you feel the transceiver snap into place at the bottom of the line card.

Idea
The SFP and SFP+ transceiver modules are hot-swappable, meaning that they can be inserted or removed while power is still present in the system.
Warning
Do not look directly into the two fiber bores inside the SFP or SFP+ transceiver module while the network switch is operating as the laser may harm the eyes.

Short Reach (SR) or Long Reach (LR) SFP

Single mode SFP transceivers can transmit anywhere from 2km up to 80km in distance. Standard single mode SFPs may transmit up to 10km, while extended single mode SFPs can be up to 80km.

Multimode SFPs are an ideal solution for shorter distances and are more cost-effective. Standard multimode SFPs can transmit up to 550m, while extended multimode SFPs can go up to 2km.

HDMI Cables

The MXnet devices use standard 19-pin HDMI female connector ports for the inputs and outputs.

Some important things to consider when planning or installing MXnet devices:
  1. Ensure all HDMI cables and devices can support the signal being sent. For most use cases, a High-Speed HDMI cable with Ethernet rated for 18Gbps will be more than sufficient to satisfy signal transport if every device can handle the signal.
  1. Ensure your HDMI cable is the correct length. The current HDMI specification calls for cables to be between 2 to 10 meters (6.6 to 33 feet). Smaller wire cables may be unable to transmit higher bandwidth signals like 4K60 over distances of even 5 meters (16 feet).

USB Ports

MXnet endpoints contain various USB ports types based on model and series. The same port type can also be rated for various speeds based on the intended hardware design. View the USB Performance section for additional details.

DisplayPort Alt-Mode

A subset of MXnet encoders are equipped with a USB-C connector that is capable of DisplayPort Alt-Mode. This allows the USB-C connection to operate as both a USB data host connection and simultaneously receive AV from compatible source devices to be encoded over the network. DisplayPort Alt-Mode capability is listed in individual endpoint specification sheets.

Not every source device equipped with USB-C connections is capable of DisplayPort Alt-Mode. Be sure to verify this functionality through the source device's user manual or specification sheet.

USB Power Delivery

A subset of MXnet encoders are equipped with a USB-C connector that is capable of providing power to compatible source devices. Available power will vary based on the particular endpoint. Verify this through MXnet endpoint's specification sheet.

Not every source device is capable of receiving power through its USB-C connections. Additionally, source device power and charging requirements may vary. Be sure to verify this information through the source device's user manual or specification sheet and cross reference with the capability of the MXnet endpoint's available wattage availability for power delivery.

RS-232

Serial control connections are made using the provided 3-pin terminal block or 3.5mm TRS connector.

Terminal Block Wiring


3.5mm TRS Wiring


Infrared

IR connections are made using the provided 3.5mm IR Emitter and IR Eye (receiver).

Analog Audio

Based on endpoint model, a 3.5mm TRS and/or a 5-pin terminal block are used for audio input and output. Theses connections support up to 2CH PCM analog audio signals. The signal must be a native 2CH PCM format from a source device or a downmixed signal via an AVDM endpoint.



AC Power Connections

Alert
Surge Protection
Use a surge-protected circuit for all components and power supplies.
Alert
Electrical Disconnect
The power source outlet and power supply input sockets should be easily accessible to disconnect power in the event of an electrical hazard or malfunction.

Installation

Mounting

For high-density endpoint installation, it is recommended to use an MXnet rack mounting kit to properly secure endpoints and allow for adequate heat dissipation. Rack mounting hardware and accessories included with the rack kit. All MXnet endpoints also support surface mounting and include the necessary brackets in their individual product box. 


System Cooling and Airflow

Poor thermal management can greatly shorten the lifespan of electronic devices. It’s important to use effective cooling methods—whether passive or active—to draw heat away from internal components and keep them operating within their specified temperature range. Heat buildup can also occur due to poor layout or cable placement, which can block airflow and create localized hotspots. To avoid this, ensure cables and nearby equipment do not obstruct ventilation around the components.

MXnet rack-mount kits are engineered to provide secure mounting and efficient cooling when installing MXnet units in an AV rack. Using these kits helps maintain a clean, organized setup while ensuring consistent thermal performance. In cases where rack-mounting isn’t possible, encoders and decoders should not be stacked or placed directly on solid surfaces. Maintain at least 1 inches of clearance on all sides of the device to promote proper airflow and prevent overheating.

Physical Connections

Info
Before connecting any MXnet endpoints to a network switch, ensure the switch has been configured per the Third-Party Network Switch Requirements. If using an MXnet switch, these come pre-configured with the necessary multicast/IGMP settings enabled. For more information on network topologies and design view the MXnet Network Switch Manual.

Ethernet/SFP

Endpoints
Connect an ethernet cable to the endpoint's RJ-45 connection and to a network switch. If the switch is PoE enabled, the device will power. Otherwise, the use of a DC power connection is required.


(Alternative) Connect a fiber SFP module to the endpoint's SFP slot and to a network switch. SFP will not power the endpoint, so an additional DC power connection is required.


CBOX
  1. Connect an ethernet cable to the port labeled "AV Network" and to the switch that contains the MXnet endpoints.
  2. Connect an ethernet cable to the port labeled "Port 1 Mentor" and to the switch/network that will contain a control system.

Optionally, you can also connect the CBOX to the MGMT port of MXnet switches to enable management and configuration of certain switch features from the Mentor web interface. Make this connection using ports 2-7 on the CBOX. Multiple switches can be connected using these ports for management.

High availability is a function of the CBOX that allows two physical units to work together to create a redundant management system. This can be accomplished over the LAN without any additional physical connections necessary, just through software enablement via Mentor. Alternatively, the port labeled "HA" on the CBOX can be used to directly connect two CBOX's together achieving similar results, albeit an "offline" method. View this How To Configure High Availability guide for additional details. 


HDMI

Connect an HDMI source device to the endpoint's HDMI Input port.

Connect an HDMI sink device to the endpoint's HDMI Output port.

USB

Option A: Connect a USB host device to the USB port labeled "Host".

Option B: Connect a USB host device to the USB port labeled "Host" or "USB-C In". If the MXnet endpoint and source device both support DisplayPort Alt-mode the USB connection can also be used to encode AV.


Connect USB peripheral devices to an endpoint's Type A ports.

Point to Point Mode

Evolution I and Evolution II endpoints support transmitting audio, video, USB and control signals in a direct point-to-point (unicast) mode without using a network switch. This allows the endpoints to work similar to an HDBaseT/UTP extender. Signals can be extended up to 100m (328ft) through Ethernet cabling or up to 40km through single-mode fiber.

Evolution I and Evolution II endpoints operate in unicast mode by factory default but will automatically be set to multicast mode by the CBOX when connected to the network switch. Once set to multicast mode, the encoders and decoders must be set back to unicast mode again prior to point-to-point installation.

The diagram below shows the connections of the AC-MXNET-1G-E encoder and AC-MXNET-1G-D decoder in a point-to-point application.

Encoder Preview Streams

All MXnet encoders (with the exception of 10G series) have a preview stream that can be accessed. For Evolution II and USP this is a low resolution low framerate stream and for Evolution I is a image snapshot. These are most commonly used with control system user interfaces. 

Since in most applications, the control system does not have direct access to encoders, the CBOX is used to proxy preview streams from the AV network into the control network. Below are the URLs used to access preview streams for each MXnet product series through the CBOX.
Series
URL
Parameters
MXnet Evolution I
http://<CBOX_Control_IP>:10085/capture.bmp?dev=<Encoder_MAC>&ip=<Encoder_IP>&port=80&t=<EpochTimeStamp>
N/A
MXnet Evolution II
http://<CBOX_Control_IP>:10085/?action=stream&w=x&h=x&fps=x&bw=x&as=x&dev=<Encoder_MAC>&ip=<Encoder_IP>&port=8080
  1. w: width.
  2. h: height.
  3. fps: frame rate.
  4. bw: bandwidth.
  5. as: aspect ratio configuration.
  6. mq: minimum encode quality number.
MXnet USP
http://<CBOX_Control_IP>:10085/?ip=<Encoder_IP>&port=10004
N/A

Additionally MXnet Evolution II series support accessing the preview stream directly from encoders. This is accomplished using the URLs below.
SeriesURL
Parameters
Evolution II Snapshots
http://<Encoder_IP>:8080/?action=snapshot&w=x&h=x&q=x&as=x
  1. w: width.
  2. h: height.
  3. q: quality.
  4. as: aspect ratio configuration.
Evolution II Live Substream
http://<Encoder_IP>:8080/?action=stream&w=x&h=x&fps=x&bw=x&as=x&mq=x
  1. w: width.
  2. h: height.
  3. fps: frame rate.
  4. bw: bandwidth.
  5. as: aspect ratio configuration.
  6. mq: minimum encode quality number.

Multiview

Multiview processing is a software feature within many MXnet endpoints. Multiview processing capability varies by model. Details are below.
Product
Max Windows
Grid Layouts
Window Layering
Image Cropping
AC-MXNET-USP-ES
4 @ 1080p
Supported
Supported
Not Supported
AC-MXNET-USP-PL
7 @ 1080p
Supported
Supported
Not Supported
AC-MXNET-USP-PR
16 @ 1080p
Supported
Supported
Not Supported
AC-MXNET-1G-MV41V2
4 @ 1080p
Supported
Supported
Supported
AC-MXNET-10G-TCVR*
16 @ 540p
Supported
Supported
Supported
*All 10G TCVR models support the same multiview processing capabilities


Alert
Multiview Bandwidth Limitations
When creating multiview layouts on either USP series or 10G series it is important to consider bandwidth limitations of endpoints.

Each endpoint has a total resolution throughput that is supported.
  1. USP-ES: 4K 60Hz or 498 MPixels/sec
  2. 10G-TCVR: 4K 60Hz or 498 MPixels/sec
  3. USP-PL: 4K 120Hz or 996 MPixels/sec
  4. USP-PR: 8K 60Hz or 1,990 MPixels/sec
When decoding multiple streams through a single endpoint, each stream is added towards the total throughput capacity.

For example, on USP-PR with a total throughput of 1,990 MPixels/sec that equates to:
  1. 1x 8K 60Hz stream
  2. 4x 4K 60Hz streams
  3. 16x 1080p 60Hz streams
With 10G series, multiview uses a sub-stream generated from encoders. This sub-stream is scaled based on the size of the window in the multiview layout. The main stream and scaled stream combined cannot exceed a total video throughput limitation of 4K60 4:4:4 8bit (498 MPixels/sec). Additionally, if the design is using multiple decoders to process different multiview layouts, sources shared between these layouts must be the same resolution.

Video Walls

Video wall processing is a software feature within many MXnet endpoints. Video wall processing capability varies by model. Details are below.

Evolution I Series
Evolution II Series
USP Series
10G Series
Max Row/Columns
8x8
16x16
8x8
8x8
Bezel Correction
Supported
Supported
Supported
Supported
Mosaic Style
Not Supported
Supported
Not Supported
Not Supported
Image Rotation
Not Supported
Not Supported
Not SupportedNot Supported

Dante & AES67 Audio

Dante is a technology developed by Audinate that allows audio signals to be transmitted digitally over standard IP networks. Instead of running analog cables or point-to-point digital connections, Dante lets devices such as encoders, mixers, microphones, amplifiers, and speakers share audio over a local area network.

AES67 is an audio over IP standard created by the Audio Engineering Society. AES67 serves a similar purpose to Dante but is an open standard and isn’t a proprietary system like Dante.

See below for models that support Dante/AES67.


AC-MXNET-USP-PL
AC-MXNET-USP-PR
AC-MXNET-1G-DANTE-E
AC-MXNET-1G-DANTE-EV2AC-MXNET-1G-DANTE-DV2
AC-MXNET-10G-TCVR-PRO
Dante
Supported
Supported
Supported
Supported
Supported
Supported
AES67
Supported
Supported
Supported
Not Supported
Not Supported
Supported
Max TX Channels
2
2
2
2
2
2
Max RX Channels
2
2
0
2
2
2

When designing MXnet systems that are using Dante or AES67-enabled endpoints it is a best practice to isolate video streams from Dante/AES67 audio streams when possible. The most common way to isolate traffic is through the use of VLANs. VLANs are a way to divide a physical network into multiple logical or "virtual" networks, all using the same switch hardware.

Dante & AES67 rely on precise timing via PTP clocking and very low jitter. Using VLANs prevents video traffic from interfering with audio traffic and ensures cleaner network timing with low-risk for dropped packets. Below is a example system design that incorporates an MXnet VLAN and a Dante VLAN. The MXnet Dante encoder is connected to a Trunk port which separates MXnet video and Dante audio traffic into two VLANs.


For a step-by-step guide on configuring MXnet switches for Dante, view the articles below:
  1. Configure an MXnet Switch for DANTE-EV2 and DANTE-DV2
  2. Configure an MXnet Switch for AV and Dante in the same VLAN

USB Performance

USB extension and routing is a feature that is available on several MXnet series. USB performance and hardware is not shared across all endpoints, therefore there are varying USB data rates that can be achieved. The below table outlines USB performance across all MXnet endpoints.

Evolution I
Evolution II;
HEX & DEX
USP-PL/PR
10G-TCVR, AVDM10G-TCVR-PRO, USBX
USB Version
1.1
2.0
1.1
1.1
2.0
Max Read/Write
HID Use Only
*Read: 158Mbps
*Write: 228Mbps
HID Use Only
HID Use Only
Read: 50Mbps
Write: 70Mbps
Max Devices Per Host
7
7
4
7
7
*Requires FPGA firmware 9.19.4 or newer

Mentor Web Interface

Mentor is the web-based management interface that is hosted on the CBOX. It is used to discover, setup and maintain all MXnet endpoints. To access Mentor, you must type the IP address of either the CBOX Control or AV port into your web browser based on which LAN your computer is physically connected to. By default, the CBOX Control port is set to DHCP and the AV port is set to link-local APIPA. If a DHCP server is not available, the control port will fallback to a link-local APIPA address within 169.254/16. The front panel of the CBOX-HA features a "DHCP" button. Press and hold this button to force the control port to a static IP address of 192.168.1.239/24. IP addresses of the CBOX can be found on the front panel info display. 



View the Mentor User Manual for a full walkthrough of the software environment.

AVPro Flow

AVPro Flow is an AV distribution technology that leverages open-standard H.265 and H.264 codecs to provide interoperability between AVPro devices and 3rd-party hardware or software products.

AVPro Flow products use the open standards developed and maintained by the ITU-T Video Coding Experts Group (VCEG) in collaboration with ISO/IEC’s Moving Picture Experts Group (MPEG). As open standards, these codecs are widely adopted across industries because they ensure interoperability between devices and systems from different manufacturers. This openness allows hardware and software developers to implement the codecs without relying on proprietary technologies, making integration across platforms such as broadcast, streaming, and professional AV more seamless and cost-effective.

AVPro Flow Enabled Products
  1. AC-MXNET-USP-ES
  2. AC-MXNET-USP-PL
  3. AC-MXNET-USP-PR
USP endpoints conform to several open-standard H.26x encoding/decoding profiles. This includes:
  1. Main & Main10 Profiles for H.265 (HEVC)
  2. Baseline, Main & High Profiles for H.264 (AVC)
  3. Bitrate tier level 6.1 or lower
USP endpoints support the following network streaming protocols
  1. RTP - used for the private stream between other USP endpoints. Is encrypted using AES-256.
  2. RTSP - used for streaming to 3rd-party devices. Is not encrypted and does not support HDCP content
  3. RTMP - used for streaming to internet streaming services. Is not encrypted and does not support HDCP content.
For more information on AVPro Flow read the AVPro Flow: How to Build a Hybrid AV System white paper.

Network Switch Requirements

Third-party (non-MXnet) network switches must support the following features and functionalities and enable or disable some settings in order to support the AVPro MXnet AV over IP system.

Verify that your third-party network switch has all of the following requirements for running MXnet:
  1. IGMP Version 2 for snooping, queries, Immediate-Leave, and unknown multicast data dropping
  2. MTU Size to support jumbo Ethernet frames
  3. PoE Budget to power the MXnet endpoint devices
  4. Disable EEE functionality for system optimization 

IGMPv2 Snooping

IGMP snooping is a method that network switches use to identify multicast groups, which are groups of devices (decoders) that all receive the same network traffic, such as video, audio, and control streams. It enables the switches to forward IP packets to the correct devices (decoders) in their network. 

IGMPv2 Querier

The IGMP querier is responsible for sending out IGMP group membership queries at a timed interval, retrieving IGMP membership reports from active members, and allowing updates to the IGMP group tables

IGMPv2 Immediate-Leave

When Immediate-Leave is enabled, the device immediately removes a port when it detects the IGMPv2 Leave message on that port. Immediate-Leave is only supported on IGMPv2 hosts and should be enabled for every port on the VLAN.

Unknown Multicast Drop (Unregistered Multicast Flooding)

Unknown multicast data refers to multicast data for which no forwarding entries exist in the IGMP snooping forwarding table. This feature enables the device to forward unknown multicast data to the router port only. If the device does not have a router port, unknown multicast data will then be dropped. If this feature is not enabled, the unknown multicast data will flood the VLAN to which the data belongs and may severely interfere with normal network operations. 

MTU Settings

The MTU (Maximum Transmission Unit) size needs to be changed to over 9000 bytes to support jumbo Ethernet frames on the AVPro MXnet AV over IP Ecosystem. The MTU is the maximum payload length for a particular transmission media and is typically 1500 bytes.

A jumbo frame is an Ethernet frame with a payload greater than the standard MTU of 1500 bytes. Jumbo frames are used on LANs that support at least 1Gbps and can be as large as 9000 bytes, or even bigger. Since jumbo frames are not defined in the IEEE 802.3 specifications for Ethernet, vendor support for jumbo frames and their maximum MTU sizes may vary.

Jumbo frames provide a large number of benefits over the traditional IEEE 802.3 Ethernet MTU’s. These include:
  1. The amount of frames sent across the network is reduced 
  2. The number of Ethernet headers is reduced as a result of fewer frames. 
  3. The reduction in frames results in fewer required headers. 
  4. The CPU cycles are reduced at the sender and receiver side due to fewer headers needing to be built and read.
  5. Network bandwidth is reduced due to the reduction in headers.

PoE Budget

PoE network switches will power the MXnet endpoint devices (encoders and decoders), as each endpoint device consumes 6 to 9 Watts of power. Be sure to correctly identify the PoE budget of the third-party network switch before purchasing.

Example: a 24-port switch with a PoE budget of 370 Watts can supply up to 15.4 Watts of power per port on all 24 ports, meaning you can connect 24 MXnet endpoint devices on the 24-port switch. Likewise, a 48-port switch with a PoE budget of 740 Watts can power up to 48 MXnet endpoint devices.

Disabling EEE

EEE (Energy Efficient Ethernet) is an IEEE 802.3az standard that is designed to reduce power consumption in Ethernet networks during idle periods.

If the third-party network switch supports EEE, be sure to disable the EEE function as it may cause issues with system optimization in some cases.

Warranty

All MXnet products are covered under AVPro Edge's 10 year warranty.


For details visit the Warranty Page.

    • Related Articles

    • MXnet Switch Hardware User Manual

      Supported Products MXnet Switches 1G Switches AC-MXNET-SW10 AC-MXNET-SW12 AC-MXNET-SW24 AC-MXNET-SW48 AC-MXNET-1G-SW24E AC-MXNET-1G-SW48E 10G Switches AC-MXNET-10G-SW12C AC-MXNET-10G-SW24C AC-MXNET-10G-SW24Q AC-MNXET-10G-SW48Q AC-MXNET-10G-SW48HQ ...

    • MXnet 1G API ~ V1.26.1

      Kevin Wang, Director of Product Management, goes through using the MXNET API to control and configure the MXNet CBOX Direct. Current API Version: V1.26.1 Control Box Version: 2.71 && V4.21 and above Instructions and API attached

    • How To: Change MXNet endpoints and Cbox to DHCP

      Overview To meet the commercial market requirements, DHCP support was added to the MXNET 1G system. This means all MXNET 1G ecosystem components support DHCP including encoders, decoders, control box (CBOX), and MXNET switches. This process applies ...

    • How to: Setup and Configure an MXnet Network Switch for AC-MXNET-1G-DANTE-EV2 and AC-MXNET-1G-DANTE-DV2 Devices.

      Overview This will be a configuration guide for configuring an MXnet network switch to work in tandem with the AC-MXNET-1G-DANTE-EV2 and AC-MXNET-1G-DANTE-DV2 devices. The new AC-MXNET-1G-DANTE-EV2/DV2 products use tagged traffic to allow for MXnet ...

    • How To: Determine the Appropriate Firmware to Use with an MXnet 1G System

      How To: Determine the Appropriate Firmware to Use with an MXnet 1G System MXnet 1G is a diverse ecosystem that is periodically evolving to provide customers with the latest features desired in the AVoIP market. Because of the diverse portfolio of ...