HDANYWHERE MHUB44100A Integrated Smart Home Solution User Guide

HDANYWHERE MHUB44100A Integrated Smart Home Solution

Specifications

• Product Models: MHUB (4×4) 100A, MHUB (6×6) 100A
• Product Code: MHUB44100A / MHUB66100A
• Revision: 1.1 – 29/11/2023

FAQ

Q: How can I access the uControl OS for configuration?

A: You can access the uControl OS by visiting your MHUB’s IP address from a web browser.

Q: What is stacking in relation to the MHUB system?

A: Stacking refers to connecting multiple MHUBs together to create a larger integrated system.

Q: Is surge protection necessary for the MHUB system?

A: Surge protection is recommended to protect the system from electrical spikes and ensure its longevity.

Box. Features. Specs

Glossary of terms

In the box

IMPORTANT

For optimum performance and safety, please read these instructions carefully before connecting, operating or configuring this product. Please keep this manual for future reference.

Surge protection is recommended
This MHUB system contains sensitive electrical components that may be damaged by electrical spikes, surges, electric shock, lightening strikes, etc. The usage of surge protection systems is recommended in order to protect and extend the life of your system.

This product is protected by International Patents:
GB 2548668
US 10587822
HK 1238827
CN 108259784
AU 201711363118 (PENDING)

Fans & noise:
MHUB44100A contains cooling fans that generate noise as it ventilates the system. If possible, avoid installing in places where this noise might be unwanted or could be amplified to an unacceptable level (e.g hollow/closed cupboards in living or quiet spaces).

Features

Specification

• Only Dolby Vision Low Latency Mode is supported at 60Hz over Video TPC output.
• CEC is dependent on source/display compatibility level. Our implementation is standard but we can not guarantee that the device being integrated is compliant.

IO Control IR Cabling

MHUB (6×6) 100A front panel

• A. Power: Indicator light. If this light is on and solid then MHUB has power and is on.
• B. Source Selector: Tapping this button will cycle through HDMI inputs (1-6) sequentially for each corresponding output (A-F).
• C. Service Port: Service port for local updates and basic control of MHUB.

MHUB (4×4) 100A front panel

• A. Power: Indicator light. If this light is on and solid then MHUB has power and is on.
• B. Source Selector: Tapping this button will cycle through HDMI inputs (1-6) sequentially for each corresponding output (A-F).
• C. Service Port: Service port for local updates and basic control of MHUB.

MHUB (6×6) 100A rear panel

MHUB (4×4) 100A rear panel

Rear panel descriptions (both models)

1. Source (IN): HDMI video input ports indicated by numbers.
2. Source IR (OUT): Connect an IR TX to control corresponding HDMI inputs.
3. AVR IR (OUT): Connect an IR TX to enable remote (IR) control of an AVR
4. Display IR (IN): Connect an IR RX to send a remote (IR) control command through MHUB to the corresponding display receiver’s “IR (OUT)” port.
5. All IR (IN): Connect an IR RX to this port to send a remote (IR) control command to all display receiver “IR (OUT)” ports.
6. Hub IR (IN): Connect an IR RX to enable remote (IR) control of MHUB.
7. Control (IP): Enables TCP/IP control of MHUB over Ethernet.
8. RS232: Enables a PC or control system to control MHUB over serial. Wired (A/GND/B).
9. Video (OUT): HDBaseT (RJ45) & HDMI video mirror output ports. These ports connect to MHUB display receivers via Category cable. The HDMI “Mirror (OUT)” outputs mirror the HDBaseT port (A & B only) and are not switchable independently. The HDBaseT port has two indicator lights. Left (orange) light: solid means HDCP is detected. Flashing means there is no HDCP. Off means no HDMI signal is detected. Right (green) light: solid means connection between MHUB and display receiver is good. Flashing means that the connection is poor. Off means that there is no connection detected.
10. Audio (OUT): Paired 3.5mm stereo and optical audio output ports. These ports support two modes of operation (follow source or follow output/zone) which can be configured from the “System Settings” page on uOS. Once set, the configuration will apply to all Audio (OUT) ports. The 3.5mm ports are pre-out, meaning that volume can be controlled from uOS and fed to an external amplifier. These ports do not downmix.
11. Power: Connect the power supply to provide power to MHUB.

MHUB display receiver diagram & description

1. Power LED: Indicator light. If this light is on and solid then the display receiver has power.
2. Firmware Update: Micro USB port for firmware updates via PC software.
3. RS232 (OUT): Will output a serial command sent to MHUB via API or control system command (IP > RS232) only.
4. IR IN: Connect an IR RX to send a remote (IR) control command from the display receiver to MHUB’s active “Source IR (OUT)” port. IR OUT: Connect an IR TX to this port to control displays using remote (IR) control commands.
5. Audio (OUT): Outputs 2ch stereo (not down-mixed) from video input.
6. HDMI (OUT): HDMI video output. Connect to your display to provide a picture and audio.
7. Video: HDBaseT link between MHUB and display receiver. This port has two indicator lights. Left light: solid means connection between MHUB and display receiver is good. Flashing means that the connection is poor. Off means that there is no connection detected. Right light: solid means HDCP is detected. Flashing means there is no HDCP. Off means no HDMI signal is detected.
8. Power: DC24V / 1A. The display receiver is powered via Power over Cat (PoC) from MHUB and this port is not used.

IR (Infrared) control
MHUB can manage IR signals and route them to sources, AVRs or displays. Using this feature will allow you to use a remote control and pass that IR command from your display location to MHUB or vice-versa.

Sending IR commands from a display ‘back’ to MHUB
This will enable backwards IR control (the most common form of IR control) where IR signals from a remote in any one of your zones is sent back to MHUB and your source device.

1. Connect an IR TX to port labelled “Source IR (OUT)” on MHUB. Ensure that the port number matches the port number of the corresponding video source input, labelled “Source (IN)”. For example, if you have Apple TV plugged in to port 3, then the IR TX cable should also be connected to Source IR (OUT) port 3.
2. Place the IR TX bud (small tear drop part) in front of the IR window of the source. Repeat for each source device you wish to control.
3. Connect an IR RX to port labelled “IR IN” on the display receiver.
4. Place IR RX head in line-of-sight of the remote control.

Sending IR commands to a display

1. Connect an IR TX to port labelled “IR OUT” on the display receiver.
2. Place the IR TX bud (small tear drop part) in front of the IR window of the display. Repeat for each display you wish to control.
3. Connect an IR RX to port labelled “Display IR (IN)” on MHUB. Ensure that the port letter matches the port letter routed to the display receiver.
4. Place IR RX head in line-of-sight of the remote control.
   

Using the Master & Room remote

Example of MHUB Master and Room remote controls (8×8 model shown)

MHUB comes with two types of native remote control.

1. A Master Remote control
2. A Room Remote control

Both remote controls are limited to video switching operations only. HDANYWHERE does not recommend that these remote controls are used as a primary controlling device for MHUB (see section: “MHUB control methods”).
The Master Remote control provides video switching control regardless of the room or zone that the command comes from. This is useful if MHUB is installed in an environment like a bar where you might want to switch all TVs from one source to another.
The Room Remote control uses ‘contextual’ IR which means that it will only switch video sources for the zone or room that you’re in.

Testing that IR control works

This section aims to verify that your MHUB’s IR control system is setup correctly and assumes that your MHUB has been wired as per the instructions laid out in this manual. Please refer to the MHUB wiring diagrams in this document to ensure that your setup matches that before proceeding with the verification below.

Testing basic operation from a display ‘back’ to MHUB
To verify that IR control is working correctly proceed to any display receiver location with an IR RX connected to it. Use the MHUB Room Remote to select a source with an IR TX connected to it at the MHUB end. You should notice that the MHUB switches to that source on your display. Now pick up your source remote control for the source you just switched to and attempt to control the source using the native remote control. If both work then you have setup IR control correctly. Repeat this step for all display receiver locations.

Testing commands from MHUB to a display
To verify that control commands from MHUB to your display are working you will need to use uControl, or test using the following method. 1) select a display that you wish to test 2) connect an IR RX to the corresponding Display IR (IN) input 3) ensure that the display receiver has an IR TX connected and that it is pointed to the display IR receiving window 4) take the display remote control to the MHUB location and point the remote at the IR RX, test the on/off command. The display should turn on or off. This will confirm that IR can pass from MHUB to your display successfully.

Working with identical source devices (discrete IR)
MHUB can work with multiple source devices that are identical due to its discrete IR function. Discrete IR avoids IR clashes that result in unwanted operation of all identical devices. MHUB manages this by targeting IR commands specifically to the source device being watched on the display. When using two or more identical source devices, take measures to avoid IR transmission leaks that could cause the identical source devices to respond in error. This includes simple measures like placing identical sources on different shelves or attempting to ‘hood’ the IR TX so that IR signals can not leak.

Cabling
Currently you can use Cat6, Cat6a, Cat7 or Cat7a with MHUB. Cat5e may work, but is not recommended, due to bandwidth requirements required by the system.

Note:
DO NOT USE COPPER CLAD ALUMINIUM/STEEL (CCA/CCS ) Cat CABLE.

Optimum performance
Whichever network cable type you choose, ensure that the main wiring architecture is ‘solid core’ and not stranded ‘patch’ cabling. Patch cabling can be used for the last few metres of a run (e.g wallplate) but should be avoided over longer runs as signal transfer over stranded cores is significantly impacted. The use of pre-made leads is not recommended unless you can be absolutely sure of their construction credentials (i.e. solid core 568B). For optimum performance, use a single piece of Cat cable terminated directly at the transmitter and the receiver ends. Make sure to use the correct connector types (i.e. RJ45 solid core) crimp connectors.

Shielded cables
Shielded FTP cable is not a stipulation. However, if you are using this type of cable ensure compatible shielded accessories are used. Failure to terminate cable screen at all points can induce interference rather than eliminate it.

Patch panels and wall plates
If patch panels are terminated correctly then there is a minimal loss of distance. The use of wallplates and patch panels has the potential to cause increased resistance on the cable introducing pinch points for signal transmission and could reduce transmission lengths. TIP: Instead of using RJ45 wallplates search for “brush plates” this will yield many results.

HDMI cabling
HDANYWHERE recommends using suitably robust and good-quality HDMI cables. It is not advised to use passive HDMI cables over 5 metres in length either on the inputs or the outputs of MHUB or its display receivers. Where HDMI cables longer than 5 metres are required, HDA recommends utilizing it own brand of long-distance HDMI cables or suitable alternative. A good video demonstrating this can be found here: https://youtu.be/EbWAEndiCuU

References

• HDANYWHERE (HDA) Worldwide Support Site | User manuals, help, support and drivers for all HDA devices and multiroom systems
• HDANYWHERE END-USER LICENCE AGREEMENT (EULA) FOR MHUB-OS
• uControl is a universal control and automation system for unifying audio-visual (AV) devices

Read User Manual Online (PDF format)

Download This Manual (PDF format)

Download this manual  >>